Communication methods and devices for multi-link devices in wireless local area networks

Abstract

This application provides a communication method and related apparatus for multi-link devices in a Wireless Local Area Network (WLAN), such as a WLAN supporting 802.11be. The method includes: receiving a probe request frame; the station receiving the probe request frame is included in a multi-link device (MLD); determining whether to respond to the probe request frame based on preset conditions, the preset conditions including at least: the reference identifier in the probe request frame does not match the reference identifier of each station in the MLD; if the preset conditions are met, then no probe response frame is sent in response to the probe request frame. Using this application embodiment can reduce the number of probe request frames sent by stations in the channel, improve station association efficiency, and enhance communication efficiency.

Description

[0001] This application is a divisional application. The original application has the application number 202010240296.X and the original application date is March 27, 2020. The entire contents of the original application are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and in particular to communication methods and apparatus used in multi-link devices in wireless local area networks. Background Technology

[0003] To significantly improve the service transmission rate of WLAN systems, the Institute of Electrical and Electronics Engineers (IEEE) 802.11ax standard further adopts Orthogonal Frequency Division Multiple Access (OFDMA) technology on top of the existing Orthogonal Frequency Division Multiplexing (OFDM) technology. OFDMA technology supports multiple nodes simultaneously transmitting and receiving data, thereby achieving multi-site diversity gain. In 2017, the year 802.11ax was finalized, the U.S. Federal Communications Commission (FCC) opened a new free frequency band, 5925-7125MHz, hereinafter referred to as the 6GHz band. Consequently, the 802.11ax standard developers extended the operating range of 802.11ax devices from 2.4GHz and 5GHz to 2.4GHz, 5GHz, and 6GHz in the Project Authorization Requests (PAR).

[0004] IEEE 802.11 next-generation WiFi protocol (extremely high throughput, EHT) devices, due to backward compatibility, will also support the operating spectrum of 802.11ax devices, namely the 2.4GHz, 5GHz, and 6GHz bands. Based on the newly opened and free 6GHz band, channel allocation within this band can support bandwidth exceeding the maximum bandwidth of 160MHz supported in 5GHz, for example, 320MHz. Besides ultra-high bandwidth, IEEE 802.11ax next-generation WiFi – extremely high throughput – can also improve peak throughput through increased stream counts, such as up to 16 streams, and cooperation across multiple frequency bands (2.4GHz, 5GHz, and 6GHz). On the same frequency band, peak throughput can also be improved and service transmission latency reduced through multiple channels cooperating. Hereinafter, multiple frequency bands or multiple channels are collectively referred to as multi-link. Although WiFi networks operating on the same frequency band, such as 802.11ax and earlier, are configured with multiple links, each link typically establishes a different Basic Service Set (BSS). At any given time, a network can only communicate with stations within the BSS to which that link belongs.

[0005] 802.11ax and earlier versions introduced the Multiple Basic Service Set Identifier (BSSID) technology. Its main function is to virtualize multiple logical APs on a single physical AP, that is, to form multiple virtual networks. Each virtual network is used to manage different sites, similar to how an AP in a current WIFI scenario can virtualize a reporting AP (home AP) and a guest AP.

[0006] How to apply Multiple BSSID technology to multi-link devices to provide multiple virtual network functions is a technical problem that those skilled in the art are researching. Summary of the Invention

[0007] This application discloses a communication method and related apparatus for multi-link devices in a wireless local area network (WLAN), which can reduce the number of probe request frames sent by stations in the channel and improve station association efficiency.

[0008] In a first aspect, embodiments of this application provide a communication method for multi-link devices in a WLAN, the method comprising:

[0009] The site receives a probe request frame; the site belongs to a multi-link device.

[0010] The site determines whether to respond to the probe request frame based on preset conditions, which at least include:

[0011] The reference identifier in the probe request frame does not match the reference identifier of each of the multi-link stations;

[0012] If the preset conditions are met, a probe response frame in response to the probe request frame will not be sent.

[0013] In the above method, stations in a multi-link system are allowed to help other stations in the same multi-link device reply with probe response frames. This reduces the number of probe request frames sent by stations in the channel, increases air interface efficiency, and improves station association efficiency.

[0014] Secondly, embodiments of this application provide a communication method for multi-link devices in a WLAN, the method comprising:

[0015] A site receives a probe request frame; the site belongs to a multi-link device; the sites in the multi-link device belong to a set of multiple BSSIDs.

[0016] The site determines whether to respond to the probe request frame based on preset conditions, which at least include:

[0017] The reference identifier in the probe request frame does not match the reference identifier of each station in the multi-link device, and the reference identifier in the probe request frame does not match the reference identifier of each station in the multi-BSSID set to which each station in the multi-link device belongs.

[0018] If the preset conditions are met, a probe response frame in response to the probe request frame will not be sent.

[0019] In the above method, stations in a multi-link device are allowed to assist other stations in the same multi-link device in replying to probe response frames, and can also assist any member in the Multiple BSSID set to which other stations in the same multi-link device belong in replying to probe response frames. This reduces the number of probe request frames sent by stations in the channel, increases air interface efficiency, and improves station association efficiency.

[0020] Thirdly, embodiments of this application provide a communication device in a WLAN, the device being applied in a multi-link device, the device comprising:

[0021] The transceiver unit is used to receive probe request frames;

[0022] A processing unit is configured to determine whether to respond to the probe request frame based on preset conditions, wherein the preset conditions include at least:

[0023] The reference identifier in the probe request frame does not match the reference identifier of each station in the multi-link device;

[0024] The processing unit is further configured to control the transceiver unit not to send a probe response frame in response to the probe request frame if the preset condition is met.

[0025] In the above method, stations of a multi-link device are allowed to help other stations in the same multi-link device reply with probe response frames, which reduces the number of probe request frames sent by stations in the channel, increases air interface efficiency, and improves station association efficiency.

[0026] Fourthly, embodiments of this application provide a communication device in a WLAN, the device being applied in a multi-link device, the device comprising:

[0027] The transceiver unit is used to receive probe request frames; the stations in the multi-link device belong to a set of multiple BSSIDs.

[0028] A processing unit is configured to determine whether to respond to the probe request frame based on preset conditions, wherein the preset conditions include at least:

[0029] The reference identifier in the probe request frame does not match the reference identifier of each station in the multi-link device, and the reference identifier in the probe request frame does not match the reference identifier of each station in the multi-BSSID set to which each station in the multi-link device belongs.

[0030] The processing unit is further configured to control the transceiver unit not to send a probe response frame in response to the probe request frame if the preset condition is met.

[0031] In the above method, stations in a multi-link device are allowed to assist other stations in the same multi-link device in replying to probe response frames, and can also assist any member in the Multiple BSSID set to which other stations in the same multi-link device belong in replying to probe response frames. This reduces the number of probe request frames sent by stations in the channel, increases air interface efficiency, and improves station association efficiency.

[0032] In one possible implementation of the first, second, third, or fourth aspect, the probe request frame includes a receiving address;

[0033] The reference identifier in the probe request frame is the Media Access Control (MAC) address carried in the receiving address;

[0034] The reference identifier for the site is the site's MAC address.

[0035] In one possible implementation of the first, second, third, or fourth aspect:

[0036] The reference identifier in the probe request frame is either the Service Set Identifier (SSID) field in the probe request frame, or the SSID included in the SSID list element in the probe request frame, or the SSID corresponding to the short SSID included in the short SSID list element in the probe request frame.

[0037] The reference identifier for the site is the site's SSID.

[0038] In one possible implementation of the first, second, third, or fourth aspect:

[0039] The reference identifier in the probe request frame is carried in the Basic Service Set Identifier (BSSID) field of the probe request frame;

[0040] The reference identifier for the site is the site's BSSID.

[0041] In one possible implementation of the first, second, third, or fourth aspect, one or more sites in the multi-link device belong to a multi-BSSID set.

[0042] In one possible implementation of the first, second, third, or fourth aspect, the one or more sites are transport BSSID sites in the multiple BSSID set.

[0043] In one possible implementation of the first, second, third, or fourth aspect, the one or more sites include non-transmitting BSSID sites in the multiple BSSID set.

[0044] Fifthly, embodiments of this application provide a communication method for multi-link devices in a WLAN, the method comprising:

[0045] The reporting access point (AP) sends multi-link device (MLD) information to the site, wherein the reporting AP belongs to an AP multi-link device; the AP multi-link device includes the reporting AP and the reported AP;

[0046] The MLD information includes information about the reporting AP and information about the reported AP. The information about the reporting AP is used to instruct the reporting AP; the information about the reported AP is used to instruct the reported AP.

[0047] In the aforementioned device, the reporting access point indicates the MultipleBSSID set structure based on AP multi-link devices to the site through MLD information. This enables multiple APs in multiple link AP devices and multiple STAs in STA multi-link devices to communicate synchronously (such as establishing associations), increasing the throughput of the wireless network, transmission robustness, and reducing transmission latency.

[0048] Sixthly, embodiments of this application provide a communication method for multi-link devices in a WLAN, the method comprising:

[0049] The site receives multi-link device (MLD) information sent by the reporting access point (AP), wherein the reporting AP belongs to an AP multi-link device; the AP multi-link device includes the reporting AP and the reported AP;

[0050] The MLD information includes information about the reporting AP and information about the reported AP. The information about the reporting AP is used to instruct the reporting AP; the information about the reported AP is used to instruct the reported AP.

[0051] The information of the reporting AP and the reported AP are obtained by parsing the multi-link MLD information.

[0052] In the aforementioned device, the reporting access point indicates the MultipleBSSID set structure based on AP multi-link devices to the site through MLD information. This enables multiple APs in multiple link AP devices and multiple STAs in STA multi-link devices to communicate synchronously (such as establishing associations), increasing the throughput of the wireless network, transmission robustness, and reducing transmission latency.

[0053] Seventhly, embodiments of this application provide a communication device for use in a multi-link device in a WLAN, which is applied to a reporting access point (AP), the communication device comprising:

[0054] The processing unit is used to generate MLD information for multi-link devices;

[0055] The transceiver unit is used to send the MLD information of the multi-link device to the site, wherein the reporting AP belongs to an AP multi-link device; the AP multi-link device includes the reporting AP and the reported AP;

[0056] The MLD information includes information about the reporting AP and information about the reported AP. The information about the reporting AP is used to instruct the reporting AP; the information about the reported AP is used to instruct the reported AP.

[0057] In the aforementioned device, the reporting access point indicates the MultipleBSSID set structure based on AP multi-link devices to the site through MLD information. This enables multiple APs in multiple link AP devices and multiple STAs in STA multi-link devices to communicate synchronously (such as establishing associations), increasing the throughput of the wireless network, transmission robustness, and reducing transmission latency.

[0058] Eighthly, embodiments of this application provide a communication device for multi-link devices in a WLAN, applied to a site, the device comprising:

[0059] The transceiver unit is used to receive multi-link device (MLD) information sent by the reporting access point (AP), wherein the reporting AP belongs to an AP multi-link device; the AP multi-link device includes the reporting AP and the reported AP;

[0060] The MLD information includes information about the reporting AP and information about the reported AP. The information about the reporting AP is used to instruct the reporting AP; the information about the reported AP is used to instruct the reported AP.

[0061] The processing unit is used to parse the multi-link MLD information to obtain the information of the reporting AP and the reported AP.

[0062] In the aforementioned device, the reporting access point indicates the MultipleBSSID set structure based on AP multi-link devices to the site through MLD information. This enables multiple APs in multiple link AP devices and multiple STAs in STA multi-link devices to communicate synchronously (such as establishing associations), increasing the throughput of the wireless network, transmission robustness, and reducing transmission latency.

[0063] In one possible implementation of the fifth, sixth, seventh, or eighth aspect, the AP in the AP multi-link device belongs to a multi-BSSID set, and the information of the reporting AP is further used to indicate the multi-BSSID set to which the reporting AP belongs; the information of the reported AP is further used to indicate the multi-BSSID set to which the reported AP belongs.

[0064] In one possible implementation of the fifth, sixth, seventh, or eighth aspect, the information of the reporting AP includes multiple BSSID elements of the multiple BSSID set to which the reporting AP resides.

[0065] In one possible implementation of the fifth, sixth, seventh, or eighth aspect, the information of the reported AP includes multiple BSSID elements of the multiple BSSID set to which the reported AP resides.

[0066] In one possible implementation of the fifth, sixth, seventh, or eighth aspect, the information of the reporting AP may also include the BSSID of the BSS to which the reporting AP belongs.

[0067] In one possible implementation of the fifth, sixth, seventh, or eighth aspect, the information of the reported AP also includes the transmission BSSID in the set of multiple BSSIDs to which the reported AP is located.

[0068] In one possible implementation of the fifth, sixth, seventh, or eighth aspect, after the reporting access point (AP) sends the multi-link device (MLD) information to the site, the method further includes:

[0069] Receive a probe request frame, an authentication request frame, or an association request frame sent by the site based on the MLD information.

[0070] In one possible implementation of the fifth, sixth, seventh, or eighth aspect, one or more APs in the AP multi-link device belong to a set of multiple BSSIDs.

[0071] In one possible implementation of the fifth, sixth, seventh, or eighth aspect, the one or more stations are transport BSSID APs in the multiple BSSID set.

[0072] In one possible implementation of the fifth, sixth, seventh, or eighth aspect, the reporting AP is a transport BSSID AP in a set of multiple BSSIDs to which the reporting AP belongs, and the reported AP is a transport BSSID AP in a set of multiple BSSIDs to which the reported AP belongs.

[0073] In one possible implementation of the fifth, sixth, seventh, or eighth aspect, the information of the reported AP further includes multi-BSSID related information of the reported AP, which is used for:

[0074] Indicate whether the reported AP belongs to a multi-BSSID set; or,

[0075] Indicate whether the reported AP is a non-transmitting BSSID AP; or,

[0076] Indicates whether the reported AP belongs to a set of multiple BSSIDs and whether the reported AP is a transmission BSSID AP.

[0077] In one possible implementation of the fifth, sixth, seventh, or eighth aspect, the multi-BSSID related information of the reported AP is included in the multi-BSSID element of the multi-BSSID set to which the reported AP belongs.

[0078] In one possible implementation of the fifth, sixth, seventh, or eighth aspect, the one or more APs include non-transport BSSID APs in the multiple BSSID set.

[0079] In one possible implementation of the fifth, sixth, seventh, or eighth aspect, the MLD information further includes information about a virtual AP, which is used to indicate the virtual AP; wherein the virtual AP is not in the same AP multilink device as the reporting AP, belongs to the same AP multilink device as a non-transport AP in the Multiple BSSID set where the reporting AP is located, and there is no member AP belonging to the AP multilink device where the reporting AP is located on the link where the virtual AP is operating, or there is a member AP belonging to the AP multilink device where the reporting AP is located on the link where the virtual AP is operating but is not in the same Multiple BSSID set as the virtual AP.

[0080] In one possible implementation of the fifth, sixth, seventh, or eighth aspect, the information of the virtual AP is used to indicate the set of multiple BSSIDs in which the virtual AP resides.

[0081] In one possible implementation of the fifth, sixth, seventh, or eighth aspect, the information of the virtual AP includes multiple BSSID elements of the multiple BSSID set to which the virtual AP resides.

[0082] In one possible implementation of the fifth, sixth, seventh, or eighth aspect, the information of the virtual AP includes the information of the transport BSSID AP in the multi-BSSID set to which the virtual AP resides.

[0083] In one possible implementation of the fifth, sixth, seventh, or eighth aspect, the BSSID of the BSS to which the virtual AP belongs is used as the transport BSSID in the set of multiple BSSIDs to which the virtual AP belongs.

[0084] In one possible implementation of the fifth, sixth, seventh, or eighth aspect, the information of the virtual AP includes multiple BSSID related information of the virtual AP, which is used for:

[0085] Indicate whether the virtual AP belongs to a set of multiple BSSIDs; or,

[0086] Indicate whether the virtual AP is a non-transport BSSID AP; or,

[0087] Indicates whether the virtual AP belongs to a set of multiple BSSIDs and indicates whether the reported AP is a transmission BSSID AP.

[0088] In one possible implementation of the fifth, sixth, seventh, or eighth aspect, the multi-BSSID related information of the virtual AP is contained in the multi-BSSID element of the multi-BSSID set to which the virtual AP belongs.

[0089] In one possible implementation of the fifth, sixth, seventh, or eighth aspect, the MLD information further includes common information, which includes one or more of the MAC address of the AP multi-link device and the number of information fields of the reported AP carrying information about the reported AP.

[0090] In one possible implementation of the fifth, sixth, seventh, or eighth aspect, the common information further includes a distinguishing field, which is used to indicate the field where the information of the reported AP is located and the field where the information of the virtual AP is located.

[0091] The communication device in the third, fourth, seventh and eighth aspects mentioned above can be a chip, the processing unit can be the processing circuit of the chip, the transceiver unit can be an input / output interface circuit, the processing circuit can be used to process signaling or data information provided by input / output, and the input / output interface circuit can be used to input and output data or signaling information to the chip.

[0092] A ninth aspect of this application provides a computer-readable storage medium storing computer program code that, when executed on a processor, causes the processor to perform the methods of any one of the first, second, fifth, and sixth aspects and their corresponding possible implementations.

[0093] A tenth aspect of this application provides a computer program product storing a computer program (instructions) that is executed by the processor. When the computer program is run on the processor, it causes the processor to execute the methods in any one of the first, second, fifth, and sixth aspects and their corresponding possible implementations.

[0094] According to the eleventh aspect of the embodiments of this application, a communication device is provided. The device includes a processor and may further include a transceiver and a memory. 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 in implementing the methods in any one of the first, second, fifth, and sixth aspects and their corresponding possible implementations.

[0095] A twelfth aspect of this application provides a communication device that can exist in the form of a chip. The device includes a processor and a memory coupled to the processor to store necessary programs (instructions) and data. The processor executes the computer program stored in the memory to support the communication device in performing the methods in any of the first, second, fifth, and sixth aspects and their corresponding possible implementations. Optionally, the memory can be located within the processor (internal storage), or it can be located outside the processor but coupled to it (external storage).

[0096] According to a thirteenth aspect of this application, a communication device is provided. The device may 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 methods in any one of the first, second, fifth, and sixth aspects and their corresponding possible implementations. Attached Figure Description

[0097] The accompanying drawings used in the embodiments of this application are described below.

[0098] Figure 1 This application provides a schematic diagram of the structure of a communication system according to an embodiment of the present application.

[0099] Figure 2(a) is a schematic diagram of the structure of a multi-link device provided in an embodiment of this application;

[0100] Figure 2(b) is a schematic diagram of another multi-link device provided in an embodiment of this application;

[0101] Figure 2(c) is a schematic diagram of another multi-link device provided in an embodiment of this application;

[0102] Figure 3(a) is a schematic diagram of a multi-link communication provided in an embodiment of this application;

[0103] Figure 3(b) is a schematic diagram of another multi-link communication provided in an embodiment of this application;

[0104] Figure 4This application provides an information indication method based on multiple link devices and Multiple BSSIDs.

[0105] Figure 5 A schematic diagram of a Multiple BSSID collection framework based on MLD provided in this application embodiment;

[0106] Figure 6 A schematic diagram of another MLD-based Multiple BSSID collection framework provided in this application embodiment;

[0107] Figure 7 A schematic diagram of another MLD-based Multiple BSSID collection framework provided in this application embodiment;

[0108] Figure 8 This application provides an information indication method based on multiple link devices and Multiple BSSIDs.

[0109] Figure 9 A schematic diagram of another MLD-based Multiple BSSID collection framework provided in this application embodiment;

[0110] Figure 10 This is a schematic diagram of the composition of a communication device provided in an embodiment of this application;

[0111] Figure 11 This is a schematic diagram illustrating the composition of another communication device provided in an embodiment of this application. Detailed Implementation

[0112] The relevant technologies involved in this application will be introduced first, and then the embodiments of this application will be described in conjunction with the accompanying drawings.

[0113] This application provides a communication method applied to a wireless communication system. The wireless communication system can be a wireless local area network (WLAN) or a cellular network. The method can be implemented by a communication device in the wireless communication system or a chip or processor within that device. This communication device can be a wireless communication device that supports parallel transmission across multiple links, for example, a multi-link device or a multi-band device. For instance, in a WLAN, 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.

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

[0115] A multi-link device (MLD) includes one or more affiliated sites. The affiliated sites are logical sites. In this embodiment, "multi-link device includes affiliated sites" is also briefly described as "multi-link device includes sites." The affiliated site can be an access point (AP) or a non-access point station (non-APSTA). For ease of description, this application refers to a multi-link device whose affiliated site is an AP as a multi-link AP or AP multi-link device, and a multi-link device whose affiliated site is a non-AP STA as a multi-link STA or multi-link STA device or STA multi-link device.

[0116] Multi-link devices (MLDs) can implement wireless communication by following the 802.11 series of protocols, such as Extremely High Throughput (EHT) or 802.11be-based or compatible with 802.11be, thereby enabling communication with other devices, which may or may not be multi-link devices.

[0117] Each logical station can operate on one link, but multiple logical stations are allowed to operate on the same link. The link identifier mentioned below represents a station operating on a single link. That is, if there are more than one logical station on a link, more than one link identifier is needed to represent them. Sometimes, the link mentioned below also refers to a station operating on that link. When a multi-link device transmits data with another multi-link device, before communication, the two devices can negotiate or communicate the mapping between link identifiers and a link or stations on a link. Alternatively, the AP multi-link device can indicate the mapping between link identifiers and a link or stations on a link through broadcast management frames, such as beacon frames. Therefore, during data transmission, it is not necessary to transmit a large amount of signaling information to indicate links or stations on links; carrying the link identifier is sufficient, reducing signaling overhead and improving transmission efficiency.

[0118] The following example illustrates the process using one of the aforementioned multi-link devices as an AP multi-link device and the other as a STA multi-link device. In one example, when the AP multi-link device establishes a BSS, the management frame it sends, such as a beacon frame, carries an element containing multiple link identification information fields. Each link identification information field suggests a correspondence between a link identifier and a station operating on that link. Each link identification information field includes a link identifier, as well as one or more of the following: MAC address, operation set, and channel number. The MAC address, operation set, and channel number can indicate a single link. In another example, during the multi-link association establishment process, the AP multi-link device and the STA multi-link device negotiate multiple link identification information fields. In subsequent communications, the AP or STA multi-link device will use the link identifier to represent a station within the multi-link device. The link identifier can also represent one or more attributes of that station, including its MAC address, operating operation set, and channel number. The MAC address can also be replaced with the association identifier of the AP multi-link device after association. Optionally, if multiple stations are operating on a single link, the link identifier (a numeric ID) represents not only the operation set and channel number of the link, but also the identifier of the station operating on that link, such as the station's MAC address or AID.

[0119] Figure 1 Taking a wireless local area network (WLAN) as an example, an application scenario diagram of an embodiment of this application is introduced. This application scenario includes a first site 101 and a second site 102. The first site 101 can communicate with the second site 102 using multiple links, thereby 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 (e.g., 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 (e.g., a single-link AP) or an AP multi-link device. In yet another scenario, the first site 101 is an AP multi-link device, and the second site 102 is an AP multi-link device or an AP; in yet another scenario, the first site 101 is a STA multi-link device, and the second site 102 is a STA multi-link device or a STA. Of course, the WLAN may also include other devices 103. Figure 1 The number and type of devices shown are merely illustrative.

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

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

[0122] As shown in Figure 2(b), the multiple APs in an AP multi-link device are independent in the low MAC layer and PHY layer, but share the high MAC layer. The multiple STAs in a STA multi-link device are independent in the low MAC layer and PHY layer, but share the high MAC layer.

[0123] Of course, STA multi-link devices can adopt an independent high MAC layer structure, while AP multi-link devices adopt a shared high MAC layer structure; alternatively, STA multi-link devices can adopt a shared high MAC layer structure, while AP multi-link devices adopt an independent high MAC layer structure. For example, either the high MAC layer or the low MAC layer can be implemented by a processor in the chip system of the multi-link device, or they can be implemented by different processing modules in a single chip system.

[0124] For example, the multi-link device in this application embodiment can be a single-antenna device or a multi-antenna device. For instance, it can be a device with two or more antennas. This application embodiment does not limit the number of antennas included in the multi-link device. Figure 2(c) illustrates this with an AP multi-link device having multiple antennas and a STA multi-link device having a single antenna. In the embodiments of this 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; alternatively, it can disallow 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.

[0125] Multi-link devices can operate in frequency bands including, but not limited to, sub-1GHz, 2.4GHz, 5GHz, 6GHz, and high-frequency 60GHz. Figures 3(a) and 3(b) illustrate two schematic diagrams of multi-link devices communicating with other devices through multiple links in a wireless local area network.

[0126] Figure 3(a) illustrates a scenario of communication between an AP multi-link device 101 and a STA multi-link device 102. The AP multi-link device 101 includes AP101-1 and AP101-2, and the STA multi-link device 102 includes STA102-1 and STA102-2. The AP multi-link device 101 and the STA multi-link device 102 communicate in parallel using link 1 and link 2.

[0127] Figure 3(b) illustrates a scenario where AP multi-link device 101 communicates with STA multi-link devices 102, STA multi-link devices 103, and STA 104. AP multi-link device 101 includes subordinate AP101-1 to AP101-3. STA multi-link device 102 includes two subordinate STA102-1 and STA102-2. STA multi-link device 103 includes two subordinate STA103-1, STA103-2, and STA103-3. STA 104 is a single-link device. AP multi-link devices can communicate with STA multi-link device 102 using link 1 and link 3, communicate with multi-link device 103 using link 2 and link 3, and communicate with STA 104 using link 1. In one example, STA104 operates in the 2.4 GHz band; STA multi-link device 103 includes STA103-1 and STA103-2, with STA103-1 operating in the 5 GHz band and STA103-2 operating in the 6 GHz band; STA multi-link device 102 includes STA102-1 and STA102-2, with STA102-1 operating in the 2.4 GHz band and STA102-2 operating in the 6 GHz band. AP101-1, operating in the 2.4 GHz band, can transmit uplink or downlink data with STA104 and STA102-2 in STA multi-link device 102 via link 1. AP101-2, operating in the 5 GHz band, can transmit uplink or downlink data with STA103-1, operating in the 5 GHz band, in STA multi-link device 103 via link 2. AP101-3, operating in the 6GHz band in AP multi-link device 101, can transmit uplink or downlink data with STA102-2, operating in the 6GHz band in STA multi-link device 102, via link 3. It can also transmit uplink or downlink data with STA103-2 in STA multi-link device 102 via link 3.

[0128] It should be noted that Figure 3(a) only shows that the AP multi-link device supports two frequency bands, and Figure 3(b) only illustrates the case where the AP multi-link device supports three frequency bands (2.4GHz, 5GHz, 6GHz), with each frequency band corresponding to one link. The AP multi-link device 101 can operate on one or more links of link 1, link 2, or link 3. On the AP side or STA side, the link here can also be understood as the station operating on that link. In practical 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 operate on more or fewer links. This application embodiment does not limit this.

[0129] For example, a multi-link device is a device with wireless communication capabilities. This device can be a complete machine or a chip or processing system installed in a complete machine. Devices with these chips or processing systems installed can implement the methods and functions of the embodiments of this application under the control of these chips or processing systems. For example, the multi-link STA in the embodiments of this application has wireless transceiver capabilities, can support the 802.11 series protocols, and can communicate with multi-link APs or other multi-link STAs or single-link devices. For example, a multi-link STA is any user communication device that allows users to communicate with APs and then with WLANs. For example, a multi-link STA can be a user device that can connect to the Internet, such as a tablet, desktop, laptop, notebook computer, ultra-mobile personal computer (UMPC), handheld computer, netbook, personal digital assistant (PDA), or mobile phone, or an IoT node in the Internet of Things, or an in-vehicle communication device in the Internet of Vehicles, etc. A multi-link STA can also be a chip and processing system in these terminals. The multi-link AP in the embodiments of this application provides services to the multi-link STA and can support the 802.11 series protocols. For example, a multi-link AP can be a communication entity such as a communication server, router, switch, or bridge. Alternatively, the multi-link AP can include various forms of macro base stations, micro base stations, and relay stations. Of course, a multi-link AP can also be the chip and processing system within these various types of devices, thereby implementing the methods and functions of the embodiments of this application. Furthermore, multi-link devices can support high-speed, low-latency transmission. With the continuous evolution of wireless LAN application scenarios, multi-link devices can be applied to more scenarios, such as sensor nodes in smart cities (e.g., smart water meters, smart electricity meters, smart air quality monitoring nodes), smart devices in smart homes (e.g., smart cameras, projectors, displays, televisions, audio equipment, refrigerators, washing machines, etc.), nodes in the Internet of Things (IoT), entertainment terminals (e.g., AR, VR, and other wearable devices), smart devices in smart offices (e.g., printers, projectors, etc.), vehicle-to-everything (V2X) devices, and some infrastructure in daily life scenarios (e.g., vending machines, supermarket self-service navigation kiosks, self-service checkout machines, self-service ordering machines, etc.). The specific forms of multi-link STAs and multi-link APs in the embodiments of this application are not specifically limited; they are merely illustrative examples. The 802.11 series of protocols may include: 802.11be, 802.11ax, 802.11a / b / g / n / ac, etc.

[0130] II. Multiple Basic Service Set Identifier (BSSID) mode.

[0131] A Multiple BSSID set is a group of cooperating APs that use the same operation set, channel number, and antenna interface. Within the Multiple BSSID set, only one AP has a Transmitted BSSID; the others are Nontransmitted BSSIDs. Information about the Multiple BSSID set (i.e., the Multiple BSSID elements) is carried in beacon frames, probe response frames, or neighbor reports sent by the Transmitted BSSID APs. The BSSID information for Nontransmitted BSSID APs is derived by receiving the Multiple BSSID elements from the aforementioned beacon frames, probe response frames, or neighbor reports.

[0132] In Multiple BSSID technology, a single physical AP can virtualize multiple logical APs. Each virtualized AP manages a BSS (Browser Service Provider). Different virtualized APs typically have different SSIDs and permissions, such as security mechanisms or transmission opportunities. Among the multiple virtualized APs, one virtual AP's BSSID is configured as a Transmitted BSSID; this virtual AP can be called a Transmitted AP. The other virtual APs' BSSIDs are configured as non-transmitted BSSIDs; these virtual APs can be called non-transmitted APs. Generally speaking, the multiple APs in Multiple BSSID can also be understood as one AP device virtualizing multiple cooperating AP devices. Only the AP with the Transmitted BSSID can send beacon frames and probe response frames. If the probe request frame sent by the STA is addressed to an AP with a Non-transmitted BSSID in the Multiple BSSID set, then the AP with the Transmitted BSSID needs to respond to the probe response frame. Beacon frames sent by APs with Transmitted BSSIDs include the Multiple BSSID element, while APs with Nontransmitted BSSIDs cannot send beacon frames. Multiple virtual APs share a common space for the association identifiers (AIDs) assigned to the sites they manage; that is, the AIDs assigned to sites across multiple virtual BSSs cannot overlap.

[0133] Optionally, the MultipleBSSID element, as shown in Table 1, includes an element ID, length, maximum BSSID indicator, and sub-elements. The maximum BSSID indicator is the maximum number of BSSIDs contained in the Multiple BSSID set, which is n. The optional sub-elements include information about each non-transmitted BSSID. The receiving end can calculate the value of each BSSID in the multiple BSSID set based on the reference BSSID, the maximum BSSID indicator, and the sequence number of the BSSID. Each BSSID consists of 48 bits. The high (48-n) bits of each BSSID in the multiple BSSID set are the same as the high 48-n bits of the reference BSSID. The low n bits of each BSSID in the multiple BSSID set are the sum of the low n bits of the reference BSSID and the sequence number x of the BSSID, and then modulo 2n. The reference BSSID (i.e., the Transmitted BSSID) is carried in the BSSID field of the MAC header of the frame containing this Multiple BSSID element (such as a beacon frame). For specific calculation methods, please refer to the 802.11-2016 standard protocol.

[0134] Table 1 MultipleBSSID elements

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

[0136] The "optional sub-elements" in Table 1 can be as shown in Table 2.

[0137] Table 2 Optional Sub-elements

[0138] Child element ID name expand 0 Nontransmitted BSSID profile Non-expandable 1-220 reserve 221 Manufacturer proprietary Manufacturer definition 222-255 reserve

[0139] In Table 2, the Nontransmitted BSSID profile (configuration) includes one or more APs or DMGSTAs with Nontransmitted BSSIDs. The Nontransmitted BSSID profile (configuration) includes, but is not limited to, the following elements:

[0140] 1. For each Nontransmitted BSSID, the Nontransmitted BSSID capability element, as well as several other elements in the beacon, must be included.

[0141] 2. The SSID element, and the Multiple BSSID-Index element.

[0142] 3. If the MultipleBSSID element is carried in the beacon, it also includes the FMS Descriptor element.

[0143] 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, WideBandwidth Channel Switch, Transmit Power Envelope, Supported Operating Classes, IBSS DFS, ERP Information, HT Capabilities, HT Operation, VHT Capabilities, VHT Operation, S1G Beacon Compatibility, ShortBeacon Interval, S1G Capabilities, and S1G Operation(11ah) etc. These elements are usually the same as the element values ​​of the transmitted BSSID AP.

[0144] 5. Optional elements include NonInheritance elements, which are the last elements in the Nontransmitted BSSID profile. Non-inheritance elements include the IDs and extension numbers of a series of elements that Nontransmitted BSSIDs cannot inherit from transmitted BSSIDs. Note that the specific content of the elements is omitted here; as shown in Table 3, it includes the element ID, length, element ID extension, list of element IDs, and list of element ID extensions. The element ID extension number only appears when the element ID value is 255.

[0145] Table 3 Non-inherited elements

[0146] 1 byte 1 byte 1 byte One or more bytes One or more bytes Element ID length Element ID extension Element ID List Element ID Extended List

[0147] How to apply Multiple BSSID technology to multi-link devices to provide multiple virtual network functions is a technical problem that those skilled in the art are researching.

[0148] Please see Figure 4 , Figure 4 This application provides an information indication method based on multi-link devices and Multiple BSSIDs. This method can be applied between sites, between access points, and between access points. For ease of description, this application uses communication between access points and sites as an example for detailed description. The method includes, but is not limited to, the following steps:

[0149] Step S401: The access point sends MLD information to the site.

[0150] An access point belongs to an MLD (Multi-Link Device), for example, it is an AP in an AP multi-link device. The site receiving MLD information can be either a site in a multi-link site device or a single-link site. In other types of BSS (Browser Service System), the sender of MLD information can be a site belonging to an MLD; the receiver of MLD information can be an access point belonging to an MLD or a single-link access point. The following description uses the example of an access point sending MLD information to a site for illustration.

[0151] In an AP multi-link device, the AP that sends this MLD information can be called a reporting AP. The information fields of the reported AP include information about other APs in the MLD to which the reporting AP belongs.

[0152] The MLD information includes information about the reporting AP and information about the reported AP. The information about the reporting AP is used to instruct the reporting AP; the information about the reported AP is used to instruct the reported AP.

[0153] Optionally, the AP in the AP multi-link device belongs to a multi-BSSID set, and the information of the reporting AP is also used to indicate the multi-BSSID set to which the reporting AP belongs; the information of the reported AP is also used to indicate the multi-BSSID set to which the reported AP belongs.

[0154] The MLD information carries information used by a site to establish an association with an AP multi-link device, enabling the site that receives the information to establish an association with the corresponding AP. Optionally, the MLD information can be carried in management frames, such as beacon frames, association response frames, probe response frames, authentication frames, or neighbor reports.

[0155] It should be noted that the MLD information may also include Multiple BSSID information, etc. Of course, the MLD information may also have other names, and this application embodiment does not specifically limit it.

[0156] An AP multi-link device comprises n logical APs, each operating on a different link. These can be represented by link identifiers: link1, link2, ..., linkn. Each AP has a unique MAC address. An AP multi-link device is identified by the MAC address of an MLD (Multi-Link Device), which can also be said to identify the management entity of that AP multi-link device. The MAC address of this AP multi-link device can be the same as one of the MAC addresses of the n logical APs included in the multi-link AP, or it can be different from all of the MAC addresses of the n logical APs. For example, the MAC address of the AP multi-link device can be a common MAC address that identifies the AP multi-link device.

[0157] In one example, one or more logical APs in an AP multi-link device may belong to one or more sets of Multiple Basic Service Set Identifiers (BSSIDs). In another example, the multiple BSSID sets to which the logical APs in an AP multi-link device belong may be different. In yet another example, multiple logical APs in an AP multi-link device may belong to the same multiple BSSID set; for instance, if two logical APs in an AP multi-link device are operating on a single link, these two logical APs may belong to the same multiple BSSID set.

[0158] For example, such as Figure 5As shown, the MAC address of a multi-link AP device is, for example, MLD1. This multi-link device includes three logical APs, represented as AP1, AP2, and AP3. AP1, AP2, and AP3 operate on link 1, link 2, and link 3, respectively. The MAC addresses of AP1, AP2, and AP3 are BSSID_11, BSSID_21, and BSSID_31, respectively. (Prior to 802.11ax, the BSSID of the BSS established by the AP was the AP's MAC address; this may have changed later. For ease of description, we will use the AP's MAC address as the BSSID of the BSS established by the AP.) AP1 belongs to the Multiple BSSID set 1, which also includes AP4 with MAC address BSSID_13. AP2 belongs to the Multiple BSSID set 2. BSSID set 2 also includes AP5 with MAC address BSSID_22 and AP6 with MAC address BSSID_23; AP3 is a member of Multiple BSSID set 3, which also includes AP7 with MAC address BSSID_32 and AP8 with MAC address BSSID_33.

[0159] Step S402: The site receives the MLD information sent by the access point (AP).

[0160] Specifically, after receiving MLD information broadcast or unicast by the AP, the station parses out the content of the MLD information, such as information about the reporting AP and the reported AP. If the MLD information contains shared information or virtual AP information, the station will also parse out the shared information and the virtual AP information. It can be understood that the station can obtain the aforementioned Multiple BSSID set structure based on the content parsed from the MLD information. After obtaining the Multiple BSSID set structure based on the AP multi-link device, one or more of the following operations can be performed:

[0161] 1) It can be associated with one or more APs in the MLD where the AP is located on a single link. For example, in Figure 6 In this process, after a station receives the MLD information sent by the AP with MAC address BSSID-1x on link 1, the station can choose to associate with the AP with MAC address BSSID-1x and the AP with MAC address BSSID-3x in the AP multi-link device MLD1 where the AP with MAC address BSSID-1x is located.

[0162] 2) It can associate with APs in other MLDs besides the reporting AP on a single link. These other MLDs contain APs belonging to the Multiple BSSID set of the MLD containing the reporting AP. For example, in... Figure 6 In the process, after a station receives the MLD information sent by the AP with MAC address BSSID-1x on link 1, the station can choose to associate with the AP with MAC address BSSID-2x and the AP with MAC address BSSID-3y in the AP multi-link device MLD2.

[0163] Optionally, association here refers to one or more of the following: interactive probe request frame and probe response frame, interactive authentication request frame and authentication response frame, interactive association request frame or association response frame.

[0164] The following are two optional Multiple BSSID set architecture schemes for AP multi-link devices.

[0165] The APs in the BSS identified by the Transmitted BSSID are referred to as Transmitted APs (Transmitted BSSID AP), and the APs in the BSS identified by the nontransmitted BSSID are referred to as Nontransmitted APs (nontransmitted BSSID AP).

[0166] Option 1:

[0167] The APs with Transmitted BSSIDs in multiple Multiple BSSID sets do not originate from the same AP multi-link device. This means that a single AP multi-link device may include one Transmitted BSSID from one Multiple BSSID set, and possibly another Nontransmitted BSSID from a different Multiple BSSID set. For example, AP1 in an AP multi-link device (MLD1) is a Transmitted BSSID from Multiple BSSID set 1, while AP2 in the same AP multi-link device (MLD1) is a Nontransmitted BSSID from Multiple BSSID set 2. In this scenario, the network constructed using Multiple BSSIDs from multiple link devices is more flexible and better suited to the service needs of different sites.

[0168] Figure 6This diagram illustrates an architecture where APs identified by Transmitted BSSIDs in multiple Multiple BSSID sets are not located in the same AP multi-link device. APs with MAC address ending in 'x' are Transmitted BSSID APs, while APs with MAC address ending in 'y' or 'z' are Non-Transmitted BSSID APs. For example, in Multiple BSSID set 1, the Transmitted BSSID AP is AP1 with MAC address BSSID_1x, and the Non-Transmitted BSSID AP is AP4 with MAC address BSSID_1y; in Multiple BSSID set 2, the Transmitted BSSID AP is AP5 with MAC address BSSID_2x, and the Non-Transmitted BSSID APs include AP2 with address BSSID_2y and AP6 with MAC address BSSID_2z; in Multiple BSSID set 3, the Transmitted BSSID AP is AP3 with MAC address BSSID_3x, and so on. The non-transmitted BSSID APs in BSSID set 3 include 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., transmission APs) from different Multiple BSSID sets are distributed in different AP multi-link devices. For example, the AP with MAC address BSSID-1x and the AP with MAC address BSSID-2x are in AP multi-link device MLD1 and AP multi-link device MLD2, respectively.

[0169] In this embodiment, a virtual AP also exists. This virtual AP is not in the same AP multi-link device as the reporting AP, but belongs to the same AP multi-link device as a non-transmission AP in the Multiple BSSID set where the reporting AP resides. Furthermore, there are no member APs belonging to the AP multi-link device where the reporting AP resides on the link where the virtual AP operates, or there are member APs belonging to the AP multi-link device where the reporting AP resides on the link where the virtual AP operates, but they are not in the same Multiple BSSID set as the virtual AP. For example... Figure 6As shown, the reporting AP in Multiple BSSID set 2 is AP5 (also a transport AP) with MAC address BSSID_2x. AP1 with MAC address BSSID_1x is not in the same multi-link device as AP5, but it is in the same AP multi-link device (MLD1) as AP5 with MAC address BSSID_2y, a non-transport AP in Multiple BSSID set 2. Furthermore, there are no member APs belonging to the AP multi-link device where the reporting AP is located on the link where AP1 is operating. Therefore, for AP5, which is the reporting AP, AP1 can be considered a virtual AP. Of course, "virtual AP" here can have other names, but its essence should be the same as that of a virtual AP.

[0170] In this embodiment, the AP that sends the MLD information in the AP multi-link device can be called the reporting AP, and the AP that does not send the MLD information can be called the reported AP. Optionally, the reported AP and the reporting AP are located in the same AP multi-link device; alternatively, the reported AP and the reporting AP are not located in the same AP multi-link device. In one example, there is currently one reporting AP and at least one reported AP in the AP multi-link device (if the number of reported APs is 0, it can be regarded as a special AP multi-link device); the reported AP and the reporting AP are in the same multi-link AP. In another example, the AP multi-link device may also include a logical AP, which switches between multiple links. When sending MLD information, the logical AP is the reporting AP. The management frame can be a beacon frame, a probe response frame, or an association response frame. The MLD information is carried in the management frame or other pre-specified frames. Therefore, the above-mentioned access point sending MLD information to the site can specifically be: the reporting AP sends MLD information to the site. The MLD information is used to indicate to the site the information on the distribution of multi-link devices and multiple BSSID sets within the site, so that the site can know the information of the MLD where the first site is located.

[0171] The MLD information can be carried in the aforementioned management frame. The MLD information may include the following: information of the reporting AP, information of the reported AP, and optionally, information of the virtual AP and shared information.

[0172] The reporting AP information includes the BSSID (usually the AP's MAC address) of the BSS to which it belongs. Additionally, if the reporting AP is a member of a Multiple BSSID set, its information must also include the Multiple BSSID element from that set. The Multiple BSSID element within this set carries further AP information, which can be referred to as the second type of AP information.

[0173] Optionally, the reporting AP information may also include first-type AP information, which refers to the information of the reporting AP itself. This first-type AP information may include, but is not limited to, one or more of the following: reporting AP capability information, reporting AP operation information, reporting AP MAC address, and reporting AP link identifier. Optionally, if the aforementioned MLD information is carried in a beacon frame, the reporting AP information may also include other fields or elements carried in the beacon according to current 802.11 protocols (e.g., 802.11-2016), such as a timestamp field, beacon interval field, SSID element, etc. Optionally, if the aforementioned MLD information is carried in a probe response frame, the reporting AP may also include other fields or elements carried in the beacon according to current 802.11 protocols (e.g., 802.11-2016), such as a timestamp field, beacon interval field, SSID element, etc. Optionally, if the aforementioned MLD information is carried in the association request frame, the information of the reporting AP may also include other fields or elements carried in the association request frame in the current 802.11 protocol (such as the 802.11-2016 protocol), such as the association identifier (AID) field, Enhanced Distributed Channel Access (EDCA) parameter set elements, etc.

[0174] The reported AP information, in method 1, includes first-type AP information, which includes AP information related to other APs in the MLD where the reported AP resides. If the reported AP indicated in the reported AP information is a member of the Multiple BSSID set, the reported AP information may optionally also include the Multiple BSSID element of the Multiple BSSID set to which the reported AP resides. Optionally, the reported AP information may also include Multiple BSSID-related information, which can indicate whether the reported AP belongs to the Multiple BSSID set through a first preset bit. For example, the first preset bit includes 1 bit, indicating whether the reported AP belongs to the Multiple BSSID set. The Multiple BSSID element of the Multiple BSSID set to which the reported AP resides carries some AP information, which can be referred to as the second-type AP information of the reported AP.

[0175] If the reported AP information indicates that the reported AP is a nontransmitted BSSID AP, then the Multiple BSSID related information also includes information about Transmitted BSSID APs in the Multiple BSSID set to which the reported AP belongs, or the Transmitted BSSID, or the sequence number of the Transmitted BSSID in the Multiple BSSID set. Optionally, the Transmitted BSSID AP information may also include one or more of the following: Transmitted BSSID AP capability information, operational information, MAC address, link identifier, and the MAC address of the AP multi-link device to which the Transmitted BSSID AP belongs.

[0176] Optionally, the information related to the Multiple BSSID to which the reported AP belongs can also be indicated by a second preset bit to indicate the AP type of the reported AP in the set of Multiple BSSIDs. For example, the second preset bit is 2 bits, which are used to indicate whether the AP is a member of the set of Multiple BSSIDs and whether it is a Transmitted BSSID AP; or the second preset bit is 1 bit, which is used to indicate whether the reported AP is a nontransmitted BSSID AP.

[0177] Optionally, the Multiple BSSID information can also use two bits to indicate both whether the reported AP belongs to the Multiple BSSID set and its type within that set. For example, one bit could indicate whether the reported AP belongs to the Multiple BSSID set, and the other bit could indicate its type within that set, such as whether it is a Transmitted BSSID AP or a nontransmitted BSSID AP.

[0178] It should be noted that if the reported AP information contains a Multiple BSSID element, the nontransmitted BSSID profile of that Multiple BSSID element can also carry the MAC address of the MLD where the nontransmitted BSSID AP resides. Specifically, if the nontransmitted BSSID AP belongs to a certain MLD, the MAC address of the MLD where the AP resides should be added to the nontransmitted BSSID profile; otherwise, it can be omitted. The MAC address of the MLD to which the nontransmitted BSSID AP belongs can be used by other sites to associate with APs within that MLD.

[0179] Optionally, the Multiple BSSID related information included in the reported AP's information can be placed in the Multiple BSSID element within the reported AP's information field, such as in an optional sub-element field within the Multiple BSSID element.

[0180] Optionally, the information related to Multiple BSSID included in the reported AP can be placed in other fields of the reported AP (not in the Multiple BSSID element).

[0181] Method 2: Case 1: If the reported AP does not belong to the Multiple BSSID set, then the first type of AP information in the reported AP's information field is the information of APs belonging to the same MLD as the reporting AP. Case 2: If the reported AP belongs to the Multiple BSSID set, then the first type of AP information is the information of the Transmitted BSSID AP in the Multiple BSSID set. The reported AP's information field also includes the Multiple BSSID element, in which case the Multiple BSSID carries the information of the second type of AP. Case 2 is further divided into two categories: Case 2.1: The Transmitted BSSID AP and the reporting AP are in the same MLD; Case 2.2: The Transmitted BSSID AP and the reporting AP are not in the same MLD.

[0182] For case 2.2, the reported AP information field also includes information about APs that meet the following conditions.

[0183] 1) The AP and the reporting AP are located in the same AP multi-link device.

[0184] 2) The AP and the AP whose information was reported are located in the same Multiple BSSID set.

[0185] The information for an AP that meets the conditions is either its BSSID or the MultipleBSSID-Index in the Multiple BSSID set.

[0186] In this method 2, the reported AP information field includes 1 bit indicating whether the reported AP belongs to the MultipleBSSID set, and also includes 1 bit indicating whether the reported AP is in the same MLD as the reporting AP.

[0187] In Method 2, if the reported AP belongs to a set of multiple BSSIDs, the first type of AP information contained in the information field of the reported AP is the information of the transmitted BSSID AP, and the signaling has the same structure as the information field of the virtual AP.

[0188] Optionally, for example, the information of the first type of AP includes one or more of the following: the capability elements of the reported AP, the operational information of the reported AP, the MAC address of the reported AP, and the link identifier of the AP. The link identifier can be an identifier number, or it can be the operation class and channel number of the reported AP, or it can be the MAC address of the reported AP, or it can be a combination of at least two of these (such as the identifier number, the operation class, the channel number, and the MAC address of the reported AP). The reporting AP can pre-determine a one-to-one correspondence between the identifier number and the operation class and channel number, or a one-to-one correspondence between the identifier number and the MAC address of the reported AP, or a one-to-one correspondence between the identifier number and a combination of at least two of the above in the MLD information it sends. Of course, the correspondence can also be determined in advance through negotiation between the reporting AP and the site.

[0189] The information of a virtual AP, if the AP indicated in the virtual AP information is a member of the Multiple BSSID set, includes: first-type AP information, i.e., information of a Transmitted BSSID AP (that is, the virtual AP is regarded as a Transmitted BSSID AP in the Multiple BSSID set to which the virtual AP belongs), and the Multiple BSSID element of the Multiple BSSID set to which the virtual AP belongs. Optionally, the information of the virtual AP also includes information related to the Multiple BSSID to which the virtual AP belongs. This information can be indicated by a third preset bit, such as 1 bit, to indicate whether the virtual AP belongs to the Multiple BSSID set.

[0190] Among them, the Multiple BSSID elements in the Multiple BSSID set where the virtual AP is located will carry some AP information, which can be called the second type of AP information of the virtual AP.

[0191] If the AP indicated in the virtual AP's information is not a member of the Multiple BSSID set, then the virtual AP's information fields include: first-class AP information, specifically the information of the virtual AP itself.

[0192] Optionally, the information related to the Multiple BSSID to which the virtual AP belongs can also be indicated by a fourth preset bit to indicate the AP type of the virtual AP in the set of Multiple BSSIDs. For example, the fourth preset bit is 2 bits, which are used to indicate whether the AP is a member of the set of Multiple BSSIDs and whether it is a Transmitted BSSID AP; or the fourth preset bit is 1 bit, which is used to indicate whether the virtual AP is a nontransmitted BSSID AP.

[0193] Optionally, the Multiple BSSID information can also use two bits to indicate both whether the virtual AP belongs to the Multiple BSSID set and its type within that set. For example, one bit could indicate whether the virtual AP belongs to the Multiple BSSID set, and the other bit could indicate its type within that set, such as whether it is a Transmitted BSSID AP or a nontransmitted BSSID AP.

[0194] It should be noted that if the virtual AP information contains a Multiple BSSID element, the nontransmitted BSSID profile of that Multiple BSSID element can also carry the MAC address of the MLD where the nontransmitted BSSID AP resides. Specifically, if the nontransmitted BSSID AP belongs to a certain MLD, the MAC address of the MLD where the AP resides is added to the nontransmitted BSSID profile; otherwise, it can be omitted. The MAC address of the MLD to which the nontransmitted BSSID AP belongs can be used by other sites to associate with APs within that MLD.

[0195] Optionally, the information related to Multiple BSSID in the virtual AP's information can be placed in the Multiple BSSID element within the virtual AP's information field, such as in an optional sub-element field within the Multiple BSSID element.

[0196] Optionally, for example, the information of the first type of AP may include one or more of the following: the virtual AP's capability elements, the virtual AP's operational information, the virtual AP's MAC address, the virtual AP's link identifier, and the MAC address of the AP multi-link device (MLD) to which the virtual AP resides. The link identifier may be an identifier number, an operation set and a channel number, the virtual AP's MAC address, or a combination of at least two of these. The reporting AP may pre-determine a one-to-one correspondence between the identifier number and the virtual AP's operation set and channel number, or between the identifier number and the virtual AP's MAC address, or between the identifier number and a combination of at least two of these in the MLD information it sends. Of course, this correspondence may also be determined in advance through negotiation between the reporting AP and the site.

[0197] The first type of AP information mentioned above is carried outside the Multiple BSSID element of the Multiple BSSID set, while the second type of AP information mentioned above is carried within the Multiple BSSID element of the Multiple BSSID set.

[0198] Shared information specifically includes at least two pieces of information shared by the reporting AP, the reported AP, and the virtual AP. For example, if the reporting AP and the reported AP are located in the same AP multi-link device MLD2, they both have the MAC address of MLD2, so the shared information can include the MAC address of MLD2. Additionally, the number of reported APs and the number of virtual APs can also be considered shared information. It should be noted that when certain shared information is not carried in the shared information, it can be carried in the information of the reporting AP, the reported AP, or the virtual AP. For example, the MAC address of MLD2, the AP multi-link device shared by the reporting AP and the reported AP, can be carried in the information of the reporting AP, and / or in the information of the reported AP.

[0199] Optionally, the shared information may not be included in the MLD information. In this case, some of the information contained in the shared information listed here may be carried in the information of the reporting AP, the reported AP, or the virtual AP.

[0200] Optionally, in this embodiment, the information fields of the reported AP and the information fields of the virtual AP can be distinguished in the following ways:

[0201] In one example: the number of reported APs and the number of virtual APs are implicitly indicated by the number of reported APs in the common information field. In this case, the information fields of one or more reported APs are consecutive, and the information fields of one or more virtual APs are consecutive. In one example, when the above MLD information includes the information of the reported APs, the reported APs, the virtual APs, and the common information, the field structure of the MLD information can be as shown in Table 4.

[0202] Table 4

[0203]

[0204] As shown in Table 4 above, if the shared information indicates that the number of reported APs is 2 and the number of virtual APs is 3, then the two information fields following the shared information each contain information about the two reported APs, and the three information fields following these two fields each contain information about the three virtual APs. Subsequent stations receiving MLD information will know that the two information fields following the shared information represent reported AP information, and that the three information fields following these two fields represent virtual AP information.

[0205] In another example: Preset bit information is included in the information field to indicate whether the current information field belongs to a reported AP or a virtual AP. This preset bit information can be 1 bit; for example, a value of 1 indicates the current information field belongs to a reported AP, and a value of 0 indicates the current information field belongs to a virtual AP. Alternatively, the preset bit information can be a special value of a field, where one part of the field's value (e.g., 1100) indicates the current information field belongs to a reported AP, and another part (0011) indicates the current information field belongs to a virtual AP. Therefore, the specific value of this field can be used to determine whether the information belongs to a reported AP or a virtual AP. Using this method, the number of reported APs and virtual APs does not need to be indicated in the MLD information, saving signaling overhead. Furthermore, it does not require one or more reported AP information fields to be consecutive, or one or more virtual AP information fields to be consecutive, allowing for more flexible placement of reported AP and virtual AP information fields in the MLD information. Of course, the MLD information in this example can also adopt the structure shown in Table 2.

[0206] The following combination Figure 6 The illustrated structure describes the information of the reporting AP, the reported AP, and the virtual AP carrying transmitted BSSID information, as well as an example of the Multiple BSSID element, as follows:

[0207] Example 1: If the reporting AP is the AP with MAC address BSSID-2x, then a reported AP is the AP with MAC address BSSID-3y, and a virtual AP is the AP with MAC address BSSID-1x.

[0208] Since the reporting AP with MAC address BSSID-2x is a member of Multiple BSSID set 2, and the AP with MAC address BSSID-2x is a transmitted BSSID AP in Multiple BSSID set 2, the information of the reporting AP includes first-type AP information and second-type AP information. The first-type AP information includes MAC address BSSID-2x (i.e., transmitted BSSID), and the second-type AP information includes Multiple BSSID elements in Multiple BSSID set 2. These Multiple BSSID elements include information about the AP with MAC address BSSID-2y and information about the AP with MAC address BSSID-2z.

[0209] Since the reported AP with MAC address BSSID-3y is a member of Multiple BSSID set 3, and the MultipleBSSID related information indicates that the AP with MAC address BSSID-3y is a nontransmitted BSSID AP, the information of the reported AP includes information of the first type of AP, information of the second type of AP, and information of a Transmitted BSSID AP in MultipleBSSID set 3 where the AP with MAC address BSSID-3y is located, that is, information of the AP with MAC address BSSID-3x. Among them, the information of the first type of AP includes information such as the MAC address of the reported AP with MAC address BSSID-3y, and the information of the second type of AP carries the Multiple BSSID element of Multiple BSSID set 3 where the AP with MAC address BSSID-3y is located. This Multiple BSSID element carries information of the AP with MAC address BSSID-3z.

[0210] Since the virtual AP with MAC address BSSID-1x is a member of Multiple BSSID set 1, and the AP with MAC address BSSID-1x is a transmitted BSSID AP in Multiple BSSID set 1, the information of the virtual AP includes information of the first type of AP and information of the second type of AP. The information of the first type of AP includes the MAC address BSSID-1x, and the information of the second type of AP includes the Multiple BSSID element of Multiple BSSID set 1, which includes the information of the AP with MAC address BSSID-1y.

[0211] Example 2: If the reporting AP is the AP with MAC address BSSID-1x, then one reported AP is the AP with MAC address BSSID-2y, and another reported AP is the AP with MAC address BSSID-3x. Furthermore, the AP with MAC address BSSID-1x does not have a corresponding virtual AP.

[0212] Since the reporting AP with MAC address BSSID-1x is a member of Multiple BSSID set 1, and the AP with MAC address BSSID-1x is a transmitted BSSID AP in Multiple BSSID set 1, the information of the reporting AP includes first-type AP information and second-type AP information. The first-type AP information includes MAC address BSSID-1x (i.e., transmitted BSSID), and the second-type AP information includes Multiple BSSID elements in Multiple BSSID set 1. The Multiple BSSID elements include information about the AP with MAC address BSSID-1y.

[0213] Since the reported AP with MAC address BSSID-2y is a member of Multiple BSSID set 3, and the MultipleBSSID related information indicates that the AP with MAC address BSSID-2y is a nontransmitted BSSID AP, the reported AP information includes the first type of AP information, the second type of AP information, and the information of a Transmitted BSSID AP in MultipleBSSID set 2 where the AP with MAC address BSSID-2y is located, that is, the information of the AP with MAC address BSSID-2x. Among them, the first type of AP information includes the MAC address of BSSID-2y, etc., and the second type of AP information includes the Multiple BSSID element in Multiple BSSID set 2 where the AP with MAC address BSSID-2y is located. This Multiple BSSID element includes the information of the AP with MAC address BSSID-2y and the information of the AP with MAC address BSSID-2z.

[0214] Since the reported AP with MAC address BSSID-3x is a member of Multiple BSSID set 3, and the MultipleBSSID related information indicates that the AP with MAC address BSSID-3x is a transmitted BSSID AP, the information of the reported AP includes information of the first type of AP, information of the second type of AP, and the MAC address BSSID-3x (i.e., Transmitted BSSID) of the AP with MAC address BSSID-3x. Among them, the information of the first type of AP includes the MAC address of the reported AP with MAC address BSSID-3x, etc., and the information of the second type of AP includes the Multiple BSSID element of Multiple BSSIDset3 where the AP with MAC address BSSID-3x is located. This Multiple BSSID element includes the information of the AP with MAC address BSSID-3y and the information of the AP with MAC address BSSID-3z.

[0215] Since there is no corresponding virtual AP when the AP with MAC address BSSID-1x is used as the reporting AP, the MLD information does not contain information about the virtual AP. Understandably, for the two examples above, the MLD information may optionally include shared information; the content of the shared information can be found in the preceding description and will not be repeated here.

[0216] Option 2:

[0217] Transmitted BSSID APs in multiple Multiple BSSID sets belong to the same AP multilink device. That is, if one or more APs in an AP multilink device belong to a Multiple BSSID set, then all Transmitted BSSID APs in that set belong to the same AP multilink device. For example, Transmitted BSSID AP1 in Multiple BSSID set 1 and Transmitted BSSID AP2 in Multiple BSSID set 2 belong to two different APs in AP multilink device MLD1. In this case, the Multiple BSSID network built on top of the AP multilink device is simpler and has less signaling MLD information overhead.

[0218] Figure 7 This illustrates that APs identified by Transmitted BSSIDs in multiple Multiple BSSID sets originate from the same AP multi-link device within a BSS. APs with MAC address ending in 'x' are Transmitted BSSIDs, while APs with MAC address ending in 'y' or 'z' are Non-Transmitted BSSIDs. For example, in Multiple BSSID set 1, the Transmitted BSSID is AP1 with MAC address BSSID_1x, and the Non-Transmitted BSSID is AP4 with MAC address BSSID_1y. In Multiple BSSID set 2, the Transmitted BSSID is AP2 with MAC address BSSID_2x, and the Non-Transmitted BSSIDs include AP5 with MAC address BSSID_2y and AP6 with MAC address BSSID_2z. In Multiple BSSID set 3, the Transmitted BSSID is AP3 with MAC address BSSID_3x. The non-transmitted BSSID APs in BSSID set 3 include AP7 with MAC address BSSID_3y and AP8 with MAC address BSSID_3z. Figure 7 It can be seen that the Transmitted BSSIDAPs (i.e., transmission APs) from different Multiple BSSID sets are all in the AP multi-link device MLD1.

[0219] In this embodiment, the AP that sends the MLD information in the AP multi-link device can be called the reporting AP, and the AP that does not send the MLD information can be called the reported AP. The reported AP and the reporting AP are located in the same AP multi-link device. In one example, there is currently one reporting AP and at least one reported AP in the AP multi-link device (when the number of reported APs is 0, it can be regarded as a special AP multi-link device); the reported AP and the reporting AP are in the same multi-link AP. In another example, the AP multi-link device may also include a logical AP, which switches between multiple links. When sending MLD information, the logical AP is the reporting AP. The management frame can be a beacon frame, a probe response frame, or an association response frame. The MLD information is carried in the management frame or other pre-specified frames. Therefore, the above-mentioned access point sending MLD information to the site can be specifically: the reporting AP sends MLD information to the site. The MLD information is used to indicate to the site the information on the distribution of multi-link devices and multiple BSSID sets within the site, so that the site can know the information of the MLD where the first site is located.

[0220] The MLD information can be carried in the aforementioned management frame. The MLD information may include the following: information of the reporting AP, information of the reported AP, and optionally, information of the virtual AP and shared information.

[0221] The reporting AP information includes the BSSID (usually the AP's MAC address) of the BSS to which it belongs. Additionally, if the reporting AP is a member of a Multiple BSSID set, its information must also include the Multiple BSSID element from that set. The Multiple BSSID element within this set carries further AP information, which can be referred to as the second type of AP information.

[0222] Optionally, the reporting AP information may also include first-type AP information, which refers to the reporting AP itself. This first-type AP information may include one or more of the following: reporting AP capability information, reporting AP operation information, reporting AP MAC address, and reporting AP link identifier. Optionally, if the aforementioned MLD information is carried in a beacon frame, the reporting AP information may also include other fields or elements carried in the beacon according to current 802.11 protocols (e.g., 802.11-2016), such as a timestamp field, beacon interval field, SSID element, etc. Optionally, if the aforementioned MLD information is carried in a probe response frame, the reporting AP may also include other fields or elements carried in the beacon according to current 802.11 protocols (e.g., 802.11-2016), such as a timestamp field, beacon interval field, SSID element, etc. Optionally, if the aforementioned MLD information is carried in the association request frame, the information of the reporting AP may also include other fields or elements carried in the association request frame in the current 802.11 protocol (such as the 802.11-2016 protocol), such as the association identifier (AID) field, Enhanced Distributed Channel Access (EDCA) parameter set elements, etc.

[0223] The reported AP information includes the BSSID (typically the AP's MAC address) of the BSS to which the reported AP belongs. Additionally, if the reported AP's information indicates it is a member of a Multiple BSSID set, then the reported AP's information includes the Multiple BSSID element of that set. Under this architecture, the reported AP is essentially a Transmitted BSSID AP. Optionally, the reported AP's information also includes information related to the Multiple BSSID to which the reported AP belongs. This Multiple BSSID information can be indicated by a first preset bit, such as 1 bit, to determine whether the reported AP belongs to the Multiple BSSID set. The Multiple BSSID element of the Multiple BSSID set to which the reported AP belongs carries some AP information; this AP information can be referred to as the second type of AP information of the reported AP.

[0224] It should be noted that if the reported AP information contains a Multiple BSSID element, the nontransmitted BSSID profile of that Multiple BSSID element can also carry the MAC address of the MLD where the nontransmitted BSSID AP resides. Specifically, if the nontransmitted BSSID AP belongs to a certain MLD, the MAC address of the MLD where the AP resides should be added to the nontransmitted BSSID profile; otherwise, it can be omitted. The MAC address of the MLD to which the nontransmitted BSSID AP belongs can be used by other sites to associate with APs within that MLD.

[0225] Optionally, the Multiple BSSID related information included in the reported AP's information can be placed in the Multiple BSSID element within the reported AP's information field, such as in an optional sub-element field within the Multiple BSSID element.

[0226] Optionally, the information related to Multiple BSSID included in the reported AP can be placed in other fields of the reported AP (not in the Multiple BSSID element).

[0227] Optionally, the information of the reported AP may also include first-type AP information, which refers to the information of the reported AP itself. For example, this first-type AP information may include one or more of the following: the reported AP's capability elements, its operational information, its MAC address, and a link identifier from the AP. The link identifier can be a single identifier, or it can be the reported AP's operation class and channel number, or it can be the reported AP's MAC address, or it can be a combination of at least two of these (such as the identifier, the reported AP's operation class, channel number, and MAC address). The reporting AP may pre-determine a one-to-one correspondence between the identifier and the operation class and channel number, or between the identifier and the reported AP's MAC address, or between the identifier and a combination of at least two of these in the transmitted MLD information. Alternatively, the correspondence may be pre-negotiated and determined by the reporting AP and the station.

[0228] The shared information specifically includes at least two pieces of information shared by the reporting AP and the reported AP. For example, if the reporting AP and the reported AP are located in the same AP multi-link device MLD2, they both have the MAC address of the AP multi-link device MLD2. Therefore, the shared information can include the MAC address of the multi-link device MLD2. Additionally, the number of reported APs can be considered shared information. It should be noted that when some shared information is not carried in the shared information, it can be carried in the information of the reporting AP or the reported AP. For example, the MAC address of the AP multi-link device MLD2, which is shared by the reporting AP and the reported AP, can be carried in the information of the reporting AP, and / or in the information of the reported AP.

[0229] Optionally, the shared information may also carry the number of reported AP information fields.

[0230] Optionally, the shared information may not be included in the MLD information. In this case, some of the information contained in the shared information listed here may be carried in the information of the reporting AP or the information of the reported AP.

[0231] Optionally, when the above MLD information includes the information of the reporting AP, the information of the reported AP, and common information, the field structure of the MLD information can be as shown in Table 5.

[0232] Table 5

[0233]

[0234] The following combination Figure 7 The illustrated structure describes the information of the reporting AP, the information of the reported AP carrying the transmitted BSSID, and an example of the Multiple BSSID element, as follows:

[0235] If the reporting AP is an AP with MAC address BSSID-1x, then one reported AP is an AP with MAC address BSSID-2x, and another reported AP is an AP with MAC address BSSID-3x.

[0236] Since the reporting AP with MAC address BSSID-1x is a member of Multiple BSSID set 1, and the AP with MAC address BSSID-1x is a transmitted BSSID AP in Multiple BSSID set 1, the information of the reporting AP includes first-type AP information and second-type AP information. The first-type AP information includes MAC address BSSID-1x (i.e., transmitted BSSID), and the second-type AP information includes Multiple BSSID elements in Multiple BSSID set 1. The Multiple BSSID elements include information about the AP with MAC address BSSID-1y.

[0237] Since the BSSID of the reported AP with MAC address BSSID-2x is a transmitted BSSID and a member of the Multiple BSSID set 2, the reported AP information includes first-type AP information and second-type AP information. The first-type AP information includes MAC address BSSID-2x (i.e., transmitted BSSID), and the second-type AP information includes Multiple BSSID elements from Multiple BSSID set 2. The Multiple BSSID elements include information about the AP with MAC address BSSID-2y and information about the AP with MAC address BSSID-2z.

[0238] Since the reported AP with MAC address BSSID-3x does not belong to any Multiple BSSID set, the information of the reported AP does not need to carry the relevant Multiple BSSID set information for MAC address BSSID-3x.

[0239] In an alternative approach, in Schemes 1 and 2 above, the information field of the reported AP includes information about the reported AP, and the information field of the virtual AP includes information about the virtual AP. Furthermore, the approach also incorporates a method of inheriting the information fields of the reporting AP. This inheritance principle is similar to the method in prior art 1 where a Non-Transmitted BSSID AP inherits parameters from a Transmitted BSSID AP.

[0240] Specifically, the reporting AP's information field includes a comprehensive set of parameters, encompassing various elements found in current 802.11 beacon frames. If some information from the reported AP is identical to some information from the reporting AP, and this identical information is carried in the reporting AP's information field, then the element corresponding to this identical information need not appear in the reported AP's information field. If some information from the reported AP is different from some information from the reporting AP, then the element corresponding to the different information can appear in the reported AP's information field, or the non-inherited elements shown in Table 3 above can be used for indication. If the reported AP's information field indicates that the reported AP belongs to the Multiple BSSID set, then some information from nontransmitted BSSID APs in the Multiple BSSID set can inherit from the reporting AP's information field, or inherit some information from Transmitted BSSID APs in the Multiple BSSID set. The inheritance principle can refer to the method for inheriting the reported AP's information field mentioned earlier.

[0241] If some information of the virtual AP is the same as some information of the reporting AP, and this same information is carried in the information field of the reporting AP, then the element corresponding to the same information does not need to appear in the information field of the virtual AP. If some information of the virtual AP is different from some information of the reporting AP, then the element corresponding to the different information can appear in the information field of the virtual AP, or the non-inherited elements shown in Table 3 above can be used to indicate this. If the information field of the virtual AP indicates that the virtual AP belongs to the Multiple BSSID set, then some information of the nontransmitted BSSID AP in the Multiple BSSID set can inherit the information field of the reporting AP, or inherit some information of the Transmitted BSSID AP in the Multiple BSSID set. The inheritance principle can refer to the method of inheriting the information field of the reported AP mentioned above.

[0242] Optionally, under the premise of the above scheme one, in step S402, the method by which the site determines the Multiple BSSID set structure is as follows:

[0243] Regarding the Multiple BSSID set to which the reporting AP belongs: Since the reporting AP is usually a transmitted BSSID AP when it is a member of the Multiple BSSID set, the BSSID of the reporting AP included in the above reporting AP information is actually a transmitted BSSID. Furthermore, since the reporting AP information needs to carry the Multiple BSSID element of the Multiple BSSID set to which the reporting AP belongs, the receiving end can determine the nontransmitted BSSID in the Multiple BSSID set to which the reporting AP belongs based on the transmitted BSSID and the Multiple BSSID element (specifically using the maximum BSSID indicator and nontransmitted BSSID profile in the element) within the Multiple BSSID set to which the reporting AP belongs, thus obtaining the structure of the Multiple BSSID set to which the reporting AP belongs.

[0244] Regarding the Multiple BSSID set to which the reported AP belongs: Since the information of the reported AP carries information related to the transmitted BSSID in the Multiple BSSID set to which the reported AP belongs (such as the information of the Transmitted BSSID AP, the Transmitted BSSID, and the sequence number of the Transmitted BSSID in the Multiple BSSID set) and the Multiple BSSID element, the receiving end can determine the nontransmitted BSSID in the Multiple BSSID set to which the reported AP belongs based on the transmitted BSSID and the Multiple BSSID element (specifically, the maximum BSSID indication and nontransmitted BSSID profile in the element will be used) in the Multiple BSSID set to which the reported AP belongs, thereby obtaining the structure of the Multiple BSSID set to which the reported AP belongs.

[0245] Optionally, if a virtual AP information field exists, then regarding the Multiple BSSID set to which the virtual AP resides: Since the information of the virtual AP carries the information of the transmitted BSSID AP and the Multiple BSSID element in the Multiple BSSID set to which the virtual AP resides, the receiving end can determine the nontransmitted BSSID in the Multiple BSSID set to which the virtual AP resides based on the transmitted BSSID and the Multiple BSSID element in the Multiple BSSID set to which the virtual AP resides (specifically, the maximum BSSID indicator and nontransmitted BSSID profile in the element will be used), thereby obtaining the structure of the Multiple BSSID set to which the virtual AP resides.

[0246] Optionally, the reporting AP, the reported AP, and the virtual AP may not belong to the Multiple BSSID set.

[0247] Optionally, the structure of the Multiple BSSID elements in the Multiple BSSID set where the reporting AP, the reported AP, and the virtual AP each belong can be as shown in Tables 1 and 2 above. Of course, it can also be in other forms, such as adding some fields, removing some fields, or changing the structural order of some fields based on the structures shown in Tables 1 and 2.

[0248] Optionally, under the premise of the above-mentioned Scheme 2, in step S402, the method by which the site determines the Multiple BSSID set structure can be:

[0249] Regarding the Multiple BSSID set to which the reporting AP belongs: Since the reporting AP is usually a transmitted BSSID AP when it is a member of the Multiple BSSID set, the BSSID of the reporting AP included in the above reporting AP information is actually a transmitted BSSID. Furthermore, since the reporting AP information needs to carry the Multiple BSSID element of the Multiple BSSID set to which the reporting AP belongs, the receiving end can determine the nontransmitted BSSID in the Multiple BSSID set to which the reporting AP belongs based on the transmitted BSSID and the Multiple BSSID element (specifically using the maximum BSSID indicator and nontransmitted BSSID profile in the element) within the Multiple BSSID set to which the reporting AP belongs, thus obtaining the structure of the Multiple BSSID set to which the reporting AP belongs.

[0250] Regarding the Multiple BSSID set to which the reported AP belongs: Since the information of the reported AP carries the BSSID of the BSS to which the reported AP belongs, and the reported AP is a transmitted AP, the BSSID of the BSS to which the reported AP belongs is the Transmitted BSSID in the Multiple BSSID set mentioned by the reported AP. Therefore, the receiving end can determine the nontransmitted BSSID in the Multiple BSSID set to which the reported AP belongs based on the transmitted BSSID and the Multiple BSSID element (specifically, the maximum BSSID indicator and nontransmitted BSSID profile in the element will be used) in the Multiple BSSID set to which the reported AP belongs, thereby obtaining the structure of the Multiple BSSID set to which the reported AP belongs.

[0251] Optionally, the reporting AP, the reported AP, and the virtual AP may not belong to the Multiple BSSID set.

[0252] Optionally, the structure of the MultipleBSSID element in the Multiple BSSID set where the reporting AP and the reported AP each belong can be as shown in Tables 1 and 2 above. Of course, it can also be in other forms, such as adding some fields, removing some fields, or changing the structural order of some fields based on the structures shown in Tables 1 and 2.

[0253] In this embodiment, after a site learns the Multiple BSSID set structure based on the AP multi-link device, it can perform many operations based on this structure. For example, it can use this structure to simultaneously associate multiple STAs in the site with multiple APs on the aforementioned AP multi-link device. This allows the AP multi-link device to serve multiple STA devices simultaneously, increasing throughput, transmission robustness, and reducing transmission latency.

[0254] It should be noted that Schemes 1 and 2 described above construct MLD information in the order of APs within the MLD device. For example, MLD information includes information about the reporting APs and the reported APs within the MLD device. The scheme described below constructs MLD information in the order of APs in the Multiple BSSID set. For example, MLD information includes information about the reporting APs in the Multiple BSSID set and information about the member APs in the Multiple BSSID set.

[0255] In an alternative approach, the MLD information mentioned above may also include the following:

[0256] The information reported regarding the AP is the same as that reported regarding the AP in Solution 1.

[0257] Optionally, if the reporting AP is located in an MLD, the information of the reporting AP includes information about each AP in the MLD where the reporting AP resides. For example, such as Figure 6 As shown, if the reporting AP is the AP with MAC address BSSID-1x, then the APs in the MLD where the MLD is located, in addition to the reporting AP, also include the AP with BSSID-2y and the AP with MAC address BSSID-3x.

[0258] Information about member APs, wherein a member AP is an AP that belongs to the same set of Multiple BSSIDs as the reporting AP; the information of the member AP is the same as the information of the reported AP in Scheme 1.

[0259] Optionally, if the member AP is in an MLD, the information of the member AP includes the information of each AP in the MLD where the member AP is located. For example, as shown in Figure 6, if the AP with MAC address BSSID-1x is the reporting AP, then the member AP is the AP with MAC address BSSID-1y, and the APs in the MLD where the member AP is located include the AP with MAC address BSSID-2z.

[0260] Information about virtual APs, wherein the virtual AP is not located in the Multiple BSSID set of the reporting AP, and the AP meets the following limiting conditions, which at least two of the following conditions exist:

[0261] Scenario 1: The reporting AP does not belong to the same MLD, but it shares the same Multiple BSSID as a member AP within the MLD to which the reporting AP belongs. For example, such as... Figure 6 As shown, assuming the reporting AP is BSSID-1x, and the MAC addresses are BSSID-2x, BSSID-3y, and BSSID-2z, none of the four APs with BSSID-3z are located in the Multiple BSSID set where the reporting AP is located, and they do not belong to the same MLD as the reporting AP. Therefore, relative to the reporting AP with MAC address BSSID-1x, the three APs with MAC addresses BSSID-2x, BSSID-3y, and BSSID-2z are all virtual APs.

[0262] Scenario 2: The reported AP is not in the same MLD as any member in the Multiple BSSID set, but it shares the same Multiple BSSID as a member AP in the MLD to which the reported AP belongs. For example, ... Figure 6 As shown, assuming the reporting AP is BSSID-1x, the two APs with MAC addresses BSSID-2x and BSSID-3y are not located in the Multiple BSSID set where the reporting AP is located, and are not in the same MLD as each member in the Multiple BSSID set where the reporting AP is located. Therefore, relative to the reporting AP with MAC address BSSID-1x, the two APs with MAC addresses BSSID-2x and BSSID-3y are virtual APs.

[0263] In this case, the information of the virtual AP is the same as that of the virtual AP in Scheme 1.

[0264] Generally, the MAC address of an AP is also the BSSID of the BSS established by that AP, and all embodiments in this application follow this principle. Optionally, if the MAC address of an AP is different from the BSSID of the BSS established by that AP, the information of the AP (e.g., reporting AP, reported AP, virtual AP) may also carry the BSSID field of the BSS established by that AP.

[0265] It should be noted that, Figure 6 and Figure 7 The number of MLDs and the number of Multiple BSSID sets shown are merely exemplary. For other structures, the method shown in the embodiments of this application can also be used to construct and report MLD information.

[0266] exist Figure 4 In the method shown, the access point indicates the Multiple BSSID set structure based on the AP multi-link device to the site through MLD information, which can support synchronous communication (such as establishing association) between multiple APs in multiple link AP devices and multiple STAs in STA multi-link devices, thereby increasing the throughput of the wireless network, transmission robustness and reducing transmission latency.

[0267] Please see Figure 8 , Figure 8 This application provides an information indication method based on multi-link devices and Multiple BSSIDs. This method can be applied between sites, between access points, and between access points. The method includes, but is not limited to, the following steps:

[0268] Step S801: The first station receives a probe request frame sent by the second station.

[0269] Specifically, after receiving the probe response frame, the first station replies with an Ack frame.

[0270] The first site is a site of a multi-link device (MLD), for example, the MLD is an AP multi-link device; or, more specifically, the MLD is a STA multi-link device. Optionally, "the first site receives the probe request frame sent by the second site" can also be expressed as "the multi-link device receives the probe request frame sent by the second site".

[0271] The second site is either a site of a multi-link device (MLD) or a single-link site. For example, the MLD may be an AP multi-link device or a STA multi-link device.

[0272] In one example, the first site is the AP in an AP multi-link device, and the second site is either a site or a site in a STA multi-link device. The following explanation uses the example of the first site being the AP in an AP multi-link device.

[0273] The first site's multi-link device (MLD) comprises n logical access points (APs), each operating on a different link. These can be represented by link identifiers: link1, link2, ..., linkn. Each AP has a unique MAC address. A multi-link device is identified by the MAC address of an MLD, which also identifies the management entity of that device. This MAC address can be the same as or different from the MAC addresses of any of the n logical APs within the MLD. Furthermore, one or more logical APs within a multi-link device may belong to different sets of Basic Service Set Identifiers (BSSIDs). Typically, the BSSID sets for each logical AP within a multi-link device are different. However, it's also possible for two logical APs within the same multi-link device to operate on the same link; in this case, these two logical APs may belong to the same BSSID set.

[0274] For example, such as Figure 5As shown, the MAC address of a multi-link device is, for example, MLD1. This multi-link device includes three logical APs, represented as AP1, AP2, and AP3. AP1, AP2, and AP3 operate on link 1, link 2, and link 3, 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 was the MAC address of the AP, which may have changed later). AP1 belongs to the Multiple BSSID set 1, which also includes AP4 with MAC address BSSID_13; AP2 belongs to the Multiple BSSID set 2, which also includes AP5 with MAC address BSSID_22 and AP6 with MAC address BSSID_23; AP3 belongs to the Multiple BSSID set 2. Members of BSSID set 3, MultipleBSSID set 3 also includes AP7 with MAC address BSSID_32 and AP8 with MAC address BSSID_33.

[0275] Figure 6This illustrates an architecture where the APs in the BSS identified by the Transmitted BSSID in multiple sets of BSSIDs are not in the same AP multi-link device. For ease of description, the APs in the BSS identified by the Transmitted BSSID can be called Transmitted APs (Transmitted BSSID APs), and the APs in the BSS identified by the nontransmitted BSSID can be called Nontransmitted APs (nontransmitted BSSID APs). In this set of multiple BSSIDs, APs whose MAC address ends in 'x' are Transmitted BSSIDs, and APs whose MAC address ends in 'y' or 'z' are Non-Transmitted BSSIDs. For example, in Multiple BSSID set 1, the Transmitted BSSID is AP1 with MAC address BSSID_1x, and the Non-Transmitted BSSID is AP4 with MAC address BSSID_1y. In Multiple BSSID set 2, the Transmitted BSSID is AP5 with MAC address BSSID_2x, and the Non-Transmitted BSSID includes AP2 with address BSSID_2y and AP6 with MAC address BSSID_2z. In Multiple BSSID set 3, the Transmitted BSSID is AP3 with MAC address BSSID_3x, and the Non-Transmitted BSSID is AP6 with MAC address BSSID_3x. BSSIDAP includes AP7 with MAC address BSSID_3y and AP8 with MAC address BSSID_3z. From Figure 6 It can be seen that the Transmitted BSSID APs (i.e., transmission APs) from different Multiple BSSID sets are distributed in different AP multi-link devices. For example, the AP with MAC address BSSID-1x and the AP with MAC address BSSID-2x are in AP multi-link device MLD1 and AP multi-link device MLD2, respectively.

[0276] Figure 7This illustrates that APs in BSSs identified by Transmitted BSSIDs in multiple sets of Multiple BSSIDs originate from the same AP multi-link device. For ease of description, APs in BSSs identified by Transmitted BSSIDs can be called Transmitted APs (Transmitted BSSID APs), and APs in BSSs identified by Nontransmitted BSSIDs can be called Nontransmitted APs (nontransmitted BSSID APs). In this set of multiple BSSIDs, APs whose MAC address ends in 'x' are Transmitted BSSIDAPs, and APs whose MAC address ends in 'y' or 'z' are Non-Transmitted BSSIDAPs. For example, in Multiple BSSID set 1, the Transmitted BSSIDAP is AP1 with MAC address BSSID_1x, and the Non-Transmitted BSSIDAP in Multiple BSSID set 1 is AP4 with MAC address BSSID_1y; in Multiple BSSID set 2, the Transmitted BSSIDAP is AP2 with MAC address BSSID_2x, and the Non-Transmitted BSSIDAPs in Multiple BSSID set 2 include AP5 with MAC address BSSID_2y and AP6 with MAC address BSSID_2z; in Multiple BSSID set 3, the Transmitted BSSIDAP is AP3 with MAC address BSSID_3x, and the Non-Transmitted BSSIDAPs in Multiple BSSID set 3 include AP5 with MAC address BSSID_2y and AP6 with MAC address BSSID_2z. BSSIDAP includes AP7 with MAC address BSSID_3y and AP8 with MAC address BSSID_3z. From Figure 7 It can be seen that the Transmitted BSSIDAPs (i.e., transmission APs) from different Multiple BSSID sets are all in the AP multi-link device MLD1.

[0277] Typically, when the second station needs to associate with a certain station, it actively scans for nearby stations (such as access points) and then associates with one of the suitable stations. During the active scanning process, the second station sends a probe request frame on the channel. If a nearby station receives the probe request frame, it replies with an acknowledgment (Ack) frame. Therefore, in this embodiment, the first station will also reply with an Ack frame upon receiving the probe request frame.

[0278] The MAC header of an 802.11 management frame includes a Frame Control field, a Receive Address (Address 1), a Send Address (Address 2), and a BSSID field (Address 3). The probe request frame described above is an 802.11 management frame; therefore, it includes the Frame Control field, Receive Address (Address 1), Send Address (Address 2), and BSSID field (Address 3). In addition, it includes a Service Set Identifier (SSID) field, which may optionally include one or more of the following: an SSID list element and a Short SSID list element.

[0279] In this embodiment of the application, the decision on whether to reply with a probe response frame is made through the following step S802 or step S803.

[0280] Step S802: If the preset conditions are met, the first station sends a probe response frame to the second station.

[0281] Whether the preset conditions are met can be determined by the multi-link device to which the first site belongs, or by a site in the multi-link device. This site can be the site that received the probe request frame.

[0282] The preset conditions include satisfying both the first condition and the second condition, wherein:

[0283] The first condition is: none of the following conditions ak are true. The first condition is as described in standard protocols such as 802.11-2016, 802.11Revmd_D3.0, and 802.11ax_D6.0. The conditions may be modified (or added) in the future as new technologies or application scenarios emerge, and this application does not impose any restrictions on them.

[0284] a) This site does not match any of the following:

[0285] 1) This site is an access point.

[0286] 2) This site is an Independent Basic Services Set (IBSS) site.

[0287] 3) This site is a network of sites.

[0288] 4) This site is a directional multi-gigabit (DMG) site that does not belong to the Personal Basic Services Set (PBSS) and is being actively scanned.

[0289] 5) This site is a PCP.

[0290] b) The address field contained in the probe request frame above carries a unicast address, and one of the following conditions is met:

[0291] 1) The site does not belong to a set of multiple BSSIDs, and the unicast address is not the site's medium access control (MAC) address.

[0292] 2) The site belongs to a set of multiple BSSIDs, and the unicast address does not match any BSS in the set of multiple BSSIDs.

[0293] c) The site is a non-access site, and the address of the probe request frame carries a broadcast address.

[0294] d) The site is a non-PCP site in a PBSS, and the address of the probe request frame carries a broadcast address.

[0295] e) The site is an IBSS and has not transmitted any ordinary beacon frames or DMG beacon frames since the last target beacon transmission time (TBTT).

[0296] f) The site is a network site, and all of the following conditions are met:

[0297] 1) The probe request frame does not contain a mesh ID element.

[0298] 2) The probe request frame contains a mesh ID element, but the element does not carry a wildcard mesh ID and does not match the mesh ID of the mesh basic service set (mesh BSS, MBSS) connected to the site.

[0299] g) This site is not a network site and does not meet any of the following conditions:

[0300] 1) The SSID in the probe request is a wildcard SSID.

[0301] 2) The SSID in the probe request frame is the same as the SSID of the BSS where the site is located.

[0302] 2a) The site is an AP that belongs to the same co-located AP set as a 6GHz AP. The SSID in the Probe Request frame matches the SSID of the 6GHz AP, and the STA reports the co-located 6GHz AP in Beacon and Probe Response frames (see 26.17.2.4).

[0303] 3) The site is a member of a multi-BSSID set, and the SSID in the probe request frame is the same as the SSID of a member in the multi-BSSID set.

[0304] 4) The probe request frame contains a list of SSIDs, and the list contains the SSIDs of the BSS where the site is located.

[0305] 5) If dot11SSIDListImplemented is true, the STA is an AP that is in the same co-located AP set as a 6GHz AP. The SSID List element is present in the ProbeRequest frame and includes the SSID corresponding to the co-located 6GHz AP. The AP reports the co-located 6GHz AP in Beacon and Probe Response frames. (See 26.17.2.4 (Out of band discovery of a 6GHz BSS)).

[0306] 6) if dot11ShortSSIDListImplemented is true, the Probe Request frame contains a Short SSID and this Short SSID can be mapped to the BSSID of the STA's BSS.

[0307] 7) If dot11ShortSSIDListImplemented is true, the STA is an AP that is in the same co-located AP set as a 6GHz AP. The Short SSID List element is present in the Probe Request frame and includes the Short SSID field corresponding to the SSID of the 6GHz AP. The AP reports this 6GHz AP in its Beacon and Probe Response frames. (See 26.17.2.4 (Out of band discovery of a 6GHz BSS)).

[0308] h) The site is not a mesh site, and address 3 in the probe request frame does not contain a wildcard BSSID, and one of the following conditions is met:

[0309] 1) The site is not a member of a multi-BSSID set, and the address 3 in the probe request frame does not match the BSSID of the BSS where the site is located.

[0310] 2) The site is a member of a multi-BSSID set, and the address in the probe request frame does not match the ID of any BSS in the multi-BSSID set.

[0311] i) The dot11InterworkingServiceActivated flag of the site is true, and the probe request frame contains an Interworking element and an extension capability element containing 1 in the Interworking field, and at least one of the following conditions is met:

[0312] 1) The homogeneous extended service set identifier (HESSID) field in the Interworking element is missing, or the HESSID field exists but contains a wildcard HESSID or matches the HESSID field of the InterworkingInfo parameter in the source language of the previous MLME-START or MLME-JOIN request.

[0313] 2) The access network type field in the Interworking element contains a wildcard access network type or matches the access network type of the site.

[0314] j) The probe request frame contains a DSSS parameter set element, in which the current channel field contains a value different from...

[0315] The value of dot11CurrentChannel.

[0316] k) The site is a DMG site, and the transmit antenna of the site is not tuned to a state where the transmitter is the source of the probe request frame. "The site" refers to the first site of the received probe request frame, or the site identified by the receive address (address 1) in the probe request frame.

[0317] If a station receives a probe request frame but does not belong to a set of multiple BSSIDs, the station will send a probe response frame according to the first condition above. If a station that receives a probe request frame belongs to a set of multiple BSSIDs, the station corresponding to the Transmitted BSSID will send a probe response frame according to the first condition above; Nontransmitted stations in the set of multiple BSSIDs are not allowed to send probe response frames.

[0318] In this embodiment of the application, the second condition has at least two optional cases: Optional Case 1 and Optional Case 2, wherein:

[0319] Optional Case 1: The reference identifier in the probe request frame matches the reference identifier of any station in the MLD.

[0320] Optional Case 2: The reference identifier in the probe request frame matches the reference identifier of any station in the MLD, or the receive address (address 1) in the received probe request frame matches the MAC address of any station in the MLD.

[0321] Optionally, the reference identifier here can be information that can serve an identification purpose, such as MAC address, BSSID, SSID, etc.

[0322] To facilitate understanding, the second condition will be illustrated below using Scheme 1, Scheme 2, and Scheme 3 as examples.

[0323] Option 1, the second condition's alternative cases 1 and 2 are as follows:

[0324] Optional Case 1: The first station is a member of a Multi-Link Device (MLD). The receive address (address 1) in the received probe request frame matches the MAC address of any station in the MLD, or the receive address (address 1) in the probe request frame matches the MAC address of any station in the Multiple BSSID set to which any station in the MLD belongs. Optionally, the first station has reported to the aforementioned second station via management frames, such as beacon frames and / or probe response frames, the stations in the MLD that can match the receive address in the probe request frame.

[0325] Optional Case 2: The first station is a member of a multi-link device (MLD), and the receive address (address 1) in the received probe request frame matches the MAC address of any station in the MLD. Optionally, the first station has reported to the aforementioned second station via management frames, such as beacon frames and / or probe response frames, the stations in the MLD that can match the receive address in the probe request frame.

[0326] For example, such as Figure 9 As shown, the AP with MAC address BSSID_1x receives a probe request frame. The receive address of this probe request frame is BSSID_2y. Since the AP with MAC address BSSID_2y and the AP with MAC address BSSID_1x come from the same MLD, the second condition mentioned above is satisfied. At this time, the AP with MAC address BSSID_1x replies with a probe response frame.

[0327] For example, an AP with MAC address BSSID_1x receives a probe request frame. The receiver address of this probe request frame is BSSID_2z. Since the AP with MAC address BSSID_2z and the AP with MAC address BSSID_2y belong to the same Multiple BSSID, and the AP with MAC address BSSID_2y and the AP with MAC address BSSID_1x belong to the same MLD, the second condition mentioned above is satisfied. In this case, the AP with MAC address BSSID_1x replies with a probe response frame.

[0328] For example, an AP with MAC address BSSID_1y receives a probe request frame with a receive address of BSSID_2z. Since the AP with MAC address BSSID_2z and the AP with MAC address BSSID_2y belong to the same Multiple BSSID set, and the AP with MAC address BSSID_2y and the AP with MAC address BSSID_1x belong to the same MLD, the second condition mentioned above is satisfied. Furthermore, since the AP with MAC address BSSID_1x and the AP with the probe request frame receive address BSSID_1y belong to the same Multiple BSSID set, and the AP with MAC address BSSID_1x is a Transmitted BSSID AP, the AP with MAC address BSSID_1x will reply with a probe response frame.

[0329] Option 2, the optional cases 1 and 2 for the second condition are as follows:

[0330] Optional Case 1: The first site is a member of a Multi-Link Device (MLD). The SSID field in the received probe request frame, or the SSIDs included in the SSID list element, or the SSIDs mapped to the Short SSIDs included in the Short SSID list element, matches the SSID of any site in the MLD. Alternatively, the SSID field in the probe request frame, or the SSIDs included in the SSID list element, or the SSIDs mapped to the Short SSIDs included in the Short SSID list element, matches the SSID of any site in the Multiple BSSID set to which any site in the MLD belongs. Optionally, the first site has reported to the aforementioned second site via management frames, such as beacon frames and / or probe response frames, the sites in the MLD that can match the SSID field in the probe request frame, or the SSIDs included in the SSID list element, or the SSIDs mapped to the Short SSIDs included in the Short SSID list element.

[0331] Optional Case 2: The first site is a member of a multi-link device (MLD). The SSID field in the received probe request frame, or the SSID included in the SSID list element, or the SSID mapped to a Short SSID included in the Short SSID list element, matches the SSID of any site within that MLD. Optionally, the first site has reported to the aforementioned second site via management frames, such as beacon frames and / or probe response frames, which sites within the MLD can match the SSID field in the probe request frame, or the SSID included in the SSID list element, or the SSID mapped to a Short SSID included in the Short SSID list element. For example, such as... Figure 9 As shown, the AP with BSSID_1x receives a probe request frame with SSID_2y. The AP with SSID_2y also has BSSID_2y, and both the AP with BSSID_2y and the AP with BSSID_1x originate from the same MLD, thus satisfying the second condition mentioned above. At this point, the AP with MAC address BSSID_1x replies with a probe response frame.

[0332] For example, an AP with BSSID_1x receives a probe request frame with SSID_2z. The AP with SSID_2z also has BSSID_2z. Furthermore, the AP with BSSID_2z and the AP with BSSID_2y originate from the same Multiple BSSID, and the AP with BSSID_2y and the AP with BSSID_1x originate from the same MLD. Therefore, the second condition mentioned above is satisfied. In this case, the AP with MAC address BSSID_1x replies with a probe response frame.

[0333] Option 3, the optional cases 1 and 2 for the second condition are as follows:

[0334] Optional Case 1: The first station is a member of a Multi-Link Device (MLD). The BSSID field (address 3) in the received probe request frame matches the BSSID of any station in the MLD, or the BSSID field (address 3) in the probe request frame matches the BSSID of any station in the Multiple BSSID set belonging to any station in the MLD. Optionally, the first station has managed frames, such as beacon frames and / or probe response frames, to report to the second station the stations in the MLD that can match the BSSID field in the probe request frame.

[0335] Optional Case 2: The first station is a member of a multi-link device (MLD), and the BSSID field (address 3) in the received probe request frame matches the BSSID of any station within that MLD. Optionally, the first station has managed frames, such as beacon frames and / or probe response frames, to report to the aforementioned second station the stations within the MLD that can match the BSSID field in the probe request frame. For example, such as... Figure 9 As shown, the AP with BSSID_1x receives a probe request frame. The receive address of this probe request frame is BSSID_2y. Since the AP with receive address BSSID_2y and the AP with BSSID_1x come from the same MLD, the second condition mentioned above is satisfied. At this time, the AP with MAC address BSSID_1x replies with a probe response frame.

[0336] For example, an AP with BSSID_1x receives a probe request frame with a receive address of BSSID_2z. Since the APs with BSSID_2z and BSSID_2y originate from the same MultipleBSSID, and the APs with BSSID_2y and BSSID_1x originate from the same MLD, the second condition mentioned above is satisfied. In this case, the AP with MAC address BSSID_1x replies with a probe response frame.

[0337] Another perspective on step S802 above: If any one of the third conditions is true, then the first station will not send a probe response frame to the second station.

[0338] In this embodiment of the application, the condition obtained by combining the first condition with the second condition in optional scheme one can be called the first preset condition, the condition obtained by combining the first condition with the second condition in optional scheme two can be called the second preset condition, and the condition obtained by combining the first condition with the second condition in optional scheme three can be called the third preset condition. Three optional third conditions are provided below. The first type of third condition is equivalent to the reverse description of the first preset condition, the second type of third condition is equivalent to the reverse description of the second preset condition, and the third type of third condition is equivalent to the reverse description of the third preset condition.

[0339] It is understandable that, based on the third condition, except in the case where no probe response frame is sent to the second station, a probe response frame needs to be sent to the second station in all other cases.

[0340] The first type of third condition includes at least one of the following conditions ag (where condition b is modified relative to condition b in the first condition above):

[0341] a) This site does not match any of the following:

[0342] 1) This site is an access point.

[0343] 2) This site is an IBSS site.

[0344] 3) This site is a network of sites.

[0345] 4) This site is a DMG site that is not part of PBSS and is conducting an active scan.

[0346] 5) This site is a PCP.

[0347] b) Condition b can be either condition b1 or condition b2.

[0348] b1) The address field contained in the probe request frame above carries a unicast address, and one of the following conditions is met:

[0349] 1) The site does not belong to any MLD, does not belong to any set of multiple BSSIDs, and the unicast address is not the MAC address of the site.

[0350] 2) The site belongs to a multi-BSSID set, any member of the multi-BSSID set is not an MLD, and the unicast address does not match any BSS in the multi-BSSID set.

[0351] 3) The site belongs to an MLD, no member of which belongs to a multi-BSSID set, and the unicast address does not match the MAC address of any site in that MLD. Optionally, the first site has reported to the second site mentioned above, via management frames, such as beacon frames and / or probe response frames, the sites in the MLD that can match the receive address in the probe request frame.

[0352] 4) The site belongs to an MLD, one of the members of which is a multi-BSSID set, and the unicast address does not match the MAC address of any site in the MLD, or any BSS in the multi-BSSID set to which any member of the MLD belongs. Optionally, the first site has reported to the second site mentioned above, via management frames, such as beacon frames and / or probe response frames, the sites in the MLD that can match the receive address in the probe request frame.

[0353] b2) The address field contained in the probe request frame above carries a unicast address, and one of the following conditions is met:

[0354] 1) The site does not belong to any MLD, does not belong to any set of multiple BSSIDs, and the unicast address is not the MAC address of the site.

[0355] 2) The site belongs to a multi-BSSID set, any member of the multi-BSSID set is not an MLD, and the unicast address does not match any BSS in the multi-BSSID set.

[0356] 3) The site belongs to a certain MLD, and the unicast address does not match the MAC address of any site in that MLD. Optionally, the first site has reported to the second site mentioned above, via management frames, such as beacon frames and / or probe response frames, the sites in the MLD that can match the receive address in the probe request frame.

[0357] c) The site is a non-access site, and the address of the probe request frame carries a broadcast address.

[0358] d) The site is a non-PCP site in a PBSS, and the address of the probe request frame carries a broadcast address.

[0359] e) The site is an IBSS and has not transmitted any ordinary communication beacon frames or DMG beacon frames since the last TBTT.

[0360] f) The site is a network site, and all of the following conditions are met:

[0361] 1) The probe request frame does not contain a mesh ID element.

[0362] 2) The probe request frame contains a mesh ID element, but the element does not carry a wildcard mesh ID and does not match the mesh ID of the MBSS connected to the site.

[0363] g) This site is not a network site and does not meet any of the following conditions:

[0364] 1) The SSID in the probe request is a wildcard SSID.

[0365] 2) The SSID in the probe request frame is the same as the SSID of the BSS where the site is located.

[0366] 2a) The site is an AP that belongs to the same co-located AP set as a 6GHz AP. The SSID in the Probe Request frame matches the SSID of the 6GHz AP, and the STA reports the co-located 6GHz AP in Beacon and Probe Response frames (see 26.17.2.4).

[0367] 3) The site is a member of a multi-BSSID set, and the SSID in the probe request frame is the same as the SSID of a member in the multi-BSSID set.

[0368] 4) The probe request frame contains a list of SSIDs, and the list contains the SSIDs of the BSS where the site is located.

[0369] 5) If dot11SSIDListImplemented is true, the STA is an AP that is in the same co-located AP set as a 6GHz AP, the SSID List element is present in the ProbeRequest frame and includes the SSID corresponding to the co-located 6GHz AP, and the AP reports the co-located 6GHz AP in Beacon and Probe Response frames (see 26.17.2.4 (Out of band discovery of a 6GHz BSS)).

[0370] 6) if dot11ShortSSIDListImplemented is true, the Probe Request frame contains a Short SSID and this Short SSID can be mapped to the BSSID of the STA's BSS.

[0371] 7) If dot11ShortSSIDListImplemented is true, the STA is an AP that is in the same co-located AP set as a 6GHz AP. The Short SSID List element is present in the Probe Request frame and includes the Short SSID field corresponding to the SSID of the 6GHz AP. The AP reports this 6GHz AP in its Beacon and Probe Response frames. (See 26.17.2.4 (Out of band discovery of a 6GHz BSS)).

[0372] h) The site is not a mesh site, and address 3 in the probe request frame does not contain a wildcard BSSID, and one of the following conditions is met:

[0373] 1) The site is not a member of a multi-BSSID set, and the address 3 in the probe request frame does not match the BSSID of the BSS where the site is located.

[0374] 2) The site is a member of a multi-BSSID set, and the address in the probe request frame does not match the ID of any BSS in the multi-BSSID set.

[0375] i) The dot11InterworkingServiceActivated flag of the site is true, and the probe request frame contains an Interworking element and an extension capability element containing 1 in the Interworking field, and at least one of the following conditions is met:

[0376] 1) The HESSID field in the Interworking element is missing, or the HESSID field exists but contains a wildcard HESSID or matches the HESSID field of the InterworkingInfo parameter in the source of the previous MLME-START or MLME-JOIN request.

[0377] 2) The access network type field in the Interworking element contains a wildcard access network type or matches the access network type of the site.

[0378] j) The probe request frame contains a DSSS parameter set element, in which the current channel field contains a value different from...

[0379] The value of dot11CurrentChannel.

[0380] k) The site is a DMG site, and the site's transmit antenna is not tuned to a state where the transmitter is the source of the probe request frame.

[0381] It should be noted that the detailed conditions included in the third condition can be deleted, added, or modified according to the needs of a specific scenario, and this application does not impose any restrictions.

[0382] The term "the site" as used above refers to the first site of the received probe request frame, or the site identified by the receiving address (address 1) in the probe request frame.

[0383] The second type of third condition includes at least one of the following conditions ag (where condition g is modified relative to condition g in the first condition above):

[0384] a) This site does not match any of the following:

[0385] 1) This site is an access point.

[0386] 2) This site is an IBSS site.

[0387] 3) This site is a network of sites.

[0388] 4) This site is a DMG site that is not part of PBSS and is conducting an active scan.

[0389] 5) This site is a PCP.

[0390] b) The address field contained in the probe request frame above carries a unicast address, and one of the following conditions is met:

[0391] 1) The site does not belong to a set of multiple BSSIDs, and the unicast address is not the MAC address of the site.

[0392] 2) The site belongs to a set of multiple BSSIDs, and the unicast address does not match any BSS in the set of multiple BSSIDs.

[0393] c) The site is a non-access site, and the address of the probe request frame carries a broadcast address.

[0394] d) The site is a non-PCP site in a PBSS, and the address of the probe request frame carries a broadcast address.

[0395] e) The site is an IBSS and has not transmitted any ordinary communication beacon frames or DMG beacon frames since the last TBTT.

[0396] f) The site is a network site, and all of the following conditions are met:

[0397] 1) The probe request frame does not contain a mesh ID element.

[0398] 2) The probe request frame contains a mesh ID element, but the element does not carry a wildcard mesh ID and does not match the mesh ID of the MBSS connected to the site.

[0399] g) Condition g is specifically condition g1 below, or condition g is specifically condition g2 below.

[0400] g1) This site is not a network site and does not meet any of the following conditions:

[0401] 1) The SSID in the probe request is a wildcard SSID.

[0402] 2) The site does not belong to MLD, and the SSID in the probe request frame is the same as the SSID of the BSS where the site is located.

[0403] 2a) The site is an AP that belongs to the same co-located AP set as a 6GHz AP. The SSID in the Probe Request frame matches the SSID of the 6GHz AP, and the STA reports the co-located 6GHz AP in Beacon and Probe Response frames (see 26.17.2.4).

[0404] 3) The site is a member of a multi-BSSID set, and no member of the multi-BSSID set belongs to an MLD, and the SSID in the probe request frame is the same as the SSID of a member of the multi-BSSID set.

[0405] 3a) The site is a member of a multi-BSSID set, and none of the members of the multi-BSSID set belong to MLD. dot11SSIDListImplemented is true, the probe request frame contains an SSID list, and the SSID list includes the SSID of a member of the multi-BSSID set.

[0406] 3b) The site is a member of a multi-BSSID set, where none of the members of the multi-BSSID set belong to an MLD, dot11SSIDListImplemented is true (i.e., dot11ShortSSIDListImplemented is true), the probe request frame contains a ShortSSID list, and the Short SSIDs included in the ShortSSID list can be mapped to the SSID of a member in the multi-BSSID set.

[0407] 4) The site does not belong to MLD, dot11ShortSSIDListImplemented is true, the probe request frame contains a list of SSIDs, and the list contains the SSID of the BSS where the site is located.

[0408] 5) If dot11SSIDListImplemented is true, the STA is an AP that is in the same co-located AP set as a 6GHz AP. The SSID List element is present in the ProbeRequest frame and includes the SSID corresponding to the co-located 6GHz AP. The AP reports the co-located 6GHz AP in Beacon and Probe Response frames. (See 26.17.2.4 (Out of band discovery of a 6GHz BSS)).

[0409] 6) This site does not belong to MLD, dot11ShortSSIDListImplemented is true, the Probe Request frame contains a Short SSID, and this Short SSID can be mapped to the BSSID of the BSS where the STA is located.

[0410] 7) If dot11ShortSSIDListImplemented is true, the STA is an AP that is in the same co-located AP set as a 6GHz AP. The Short SSIDs included in the Probe Request frame can be mapped to the SSID of the 6GHz AP, and the STA reports the aforementioned co-located 6GHz AP in its Beacon and Probe Response frames. (See 26.17.2.4 (Out of band discovery of a 6GHz BSS)).

[0411] 8) The site belongs to an MLD, and no member of that MLD belongs to a multi-BSSID set. The SSID in the probe request frame matches the SSID of any BSS belonging to any site within that MLD. Optionally, the first site has reported to the second site via management frames, such as beacon frames and / or probe response frames, sites within that MLD that match the SSID field in the probe request frame, or the SSIDs included in the SSID list element, or the SSIDs mapped to the Short SSIDs included in the Short SSID list element.

[0412] 9) The site belongs to an MLD, and none of its members belong to a multi-BSSID set. `dot11SSIDListImplemented` is true, meaning the probe request frame contains an SSID list that includes the SSID of the BSS containing any of the sites in the MLD. Optionally, the first site has reported to the second site via management frames, such as beacon frames and / or probe response frames, sites within the MLD that match the SSID field in the probe request frame, or the SSIDs included in the SSID list element, or the SSIDs mapped to the Short SSIDs included in the Short SSID list element.

[0413] 10) The site belongs to an MLD, and none of its members belong to a multi-BSSID set. `dot11ShortSSIDListImplemented` is true, meaning the probe request frame contains a ShortSSID list, and the ShortSSIDs included in this list can be mapped to the SSID of any BSS containing any site within the MLD. Optionally, the first site has reported to the second site via management frames, such as beacon frames and / or probe response frames, sites within the MLD that match the SSID field in the probe request frame, or the SSIDs included in the SSID list element, or the SSIDs mapped to by the Short SSIDs included in the Short SSID list element.

[0414] 11) The site belongs to an MLD, and this MLD has a member belonging to a multi-BSSID set. The SSID in the probe request frame matches the SSID of any BSS belonging to any site in this MLD, or matches the SSID of any BSS in the multi-BSSID set belonging to any member of the MLD. Optionally, the first site has reported to the second site via management frames, such as beacon frames and / or probe response frames, the sites in this MLD that can match the SSID field in the probe request frame, or the SSIDs included in the SSID list element, or the SSIDs mapped to the Short SSIDs included in the Short SSID list element.

[0415] 12) This site belongs to an MLD, and this MLD has a member belonging to a set of multiple BSSIDs. `dot11SSIDListImplemented` is true, meaning the probe request frame contains an SSID list, and this list includes the SSID of any BSS belonging to any site within the MLD.

[0416] This includes the SSID of any BSS in the multi-BSSID set to which any member of the MDL resides. Optionally, the first station has reported to the second station via management frames, such as beacon frames and / or probe response frames, the stations in the MLD that can match the SSID field in the probe request frame, or the SSIDs included in the SSID list element, or the SSIDs mapped to the ShortSSIDs included in the Short SSID list element.

[0417] 13) The site belongs to an MLD, and this MLD has a member belonging to a multi-BSSID set. `dot11ShortSSIDListImplemented` is true, meaning the probe request frame contains a ShortSSID list, and the ShortSSIDs included in this list can be mapped to the SSID of any BSS in the MLD, or to the SSID of any BSS in the multi-BSSID set belonging to any member of the MLD. Optionally, the first site has reported to the second site via management frames, such as beacon frames and / or probe response frames, sites in the MLD that match the SSID field in the probe request frame, or the SSIDs included in the SSID list element, or the SSIDs mapped to by the Short SSIDs included in the Short SSID list element.

[0418] g2) This site is not a network site and does not meet any of the following conditions:

[0419] 1) The SSID in the probe request is a wildcard SSID.

[0420] 2) The site does not belong to MLD, and the SSID in the probe request frame is the same as the SSID of the BSS where the site is located.

[0421] 2a) The site is an AP that belongs to the same co-located AP set as a 6GHz AP. The SSID in the Probe Request frame matches the SSID of the 6GHz AP, and the STA reports the co-located 6GHz AP in Beacon and Probe Response frames (see 26.17.2.4).

[0422] 3) The site is a member of a multi-BSSID set, and no member of the multi-BSSID set belongs to an MLD, and the SSID in the probe request frame is the same as the SSID of a member of the multi-BSSID set.

[0423] 3a) The site is a member of a multi-BSSID set, and no member of the multi-BSSID set belongs to an MLD. dot11SSIDListImplemented is true, indicating that there is an SSID list in the probe request frame, and the SSID list includes the SSID of a member of the multi-BSSID set.

[0424] 3b) The site is a member of a multi-BSSID set, and none of the members of the multi-BSSID set belong to MLD. dot11ShortSSIDListImplemented is true, the probe request frame contains a ShortSSID list, and the Short SSIDs included in the ShortSSID list can be mapped to the SSID of a member in the multi-BSSID set.

[0425] 4) This site does not belong to MLD. dot11SSIDListImplemented is true, indicating that there is an SSID list in the probe request frame, and the list contains the SSID of the BSS where this site is located.

[0426] 5) If dot11SSIDListImplemented is true, the STA is an AP that is in the same co-located AP set as a 6GHz AP. The SSID List element is present in the ProbeRequest frame and includes the SSID corresponding to the co-located 6GHz AP. The AP reports the co-located 6GHz AP in Beacon and Probe Response frames. (See 26.17.2.4 (Out of band discovery of a 6GHz BSS)).

[0427] 6) This site does not belong to MLD. dot11ShortSSIDListImplemented is true, the Probe Request frame contains a Short SSID, and this Short SSID can be mapped to the BSSID of the BSS where the STA is located.

[0428] 7) If dot11ShortSSIDListImplemented is true, the STA is an AP that is in the same co-located AP set as a 6GHz AP. The Short SSID List element is present in the Probe Request frame and includes the Short SSID field corresponding to the SSID of the 6GHz AP. The AP reports this 6GHz AP in its Beacon and Probe Response frames. (See 26.17.2.4 (Out of band discovery of a 6GHz BSS)).

[0429] 8) The site belongs to an MLD, and the SSID in the probe request frame matches the SSID of any BSS belonging to any site within that MLD. Optionally, the first site has reported to the second site via management frames, such as beacon frames and / or probe response frames, the sites within the MLD that can match the SSID field in the probe request frame, or the SSIDs included in the SSID list element, or the SSIDs mapped to the Short SSIDs included in the ShortSSID list element.

[0430] 9) The site belongs to the MLD, the probe request frame contains an SSID list, and this list includes the SSID of the BSS to which any site in the MLD resides. Optionally, the first site has reported to the second site via management frames, such as beacon frames and / or probe response frames, sites in the MLD that can match the SSID field in the probe request frame, or the SSIDs included in the SSID list element, or the SSIDs mapped to the Short SSIDs included in the Short SSID list element.

[0431] 10) The site belongs to an MLD, the probe request frame contains a ShortSSID list, and the ShortSSIDs included in this list can be mapped to the SSID of any BSS where any site in the MLD resides. Optionally, the first site has reported to the aforementioned second site via management frames, such as beacon frames and / or probe response frames, sites in the MLD that can match the SSID field in the probe request frame, or the SSIDs included in the SSID list element, or the SSIDs mapped to by the ShortSSIDs included in the ShortSSID list element.

[0432] h) The site is not a mesh site, and address 3 in the probe request frame does not contain a wildcard BSSID, and one of the following conditions is met:

[0433] 1) The site is not a member of a multi-BSSID set, and the address 3 in the probe request frame does not match the BSSID of the BSS where the site is located.

[0434] 2) The site is a member of a multi-BSSID set, and the address in the probe request frame does not match the ID of any BSS in the multi-BSSID set.

[0435] i) The dot11InterworkingServiceActivated flag of the site is true, and the probe request frame contains an Interworking element and an extension capability element containing 1 in the Interworking field, and at least one of the following conditions is met:

[0436] 1) The HESSID field in the Interworking element is missing, or the HESSID field exists but contains a wildcard HESSID or matches the HESSID field of the InterworkingInfo parameter in the source of the previous MLME-START or MLME-JOIN request.

[0437] 2) The access network type field in the Interworking element contains a wildcard access network type or matches the access network type of the site.

[0438] j) The probe request frame contains a DSSS parameter set element, in which the current channel field contains a value different from dot11CurrentChannel.

[0439] k) The site is a DMG site, and the site's transmit antenna is not tuned to a state where the transmitter is the source of the probe request frame.

[0440] It should be noted that the detailed conditions included in the third condition can be deleted, added, or modified according to the needs of a specific scenario, and this application does not impose any restrictions.

[0441] The term "the site" as used above refers to the first site of the received probe request frame, or the site identified by the receiving address (address 1) in the probe request frame.

[0442] The third condition includes at least one of the following conditions (where condition h is modified compared to condition h in the first condition above): a) The site does not match any of the following:

[0443] 1) This site is an access point.

[0444] 2) This site is an IBSS site.

[0445] 3) This site is a network of sites.

[0446] 4) This site is a DMG site that is not part of PBSS and is conducting an active scan.

[0447] 5) This site is a PCP.

[0448] b) The address field contained in the probe request frame above carries a unicast address, and one of the following conditions is met:

[0449] 1) The site does not belong to a set of multiple BSSIDs, and the unicast address is not the MAC address of the site.

[0450] 2) The site belongs to a set of multiple BSSIDs, and the unicast address does not match any BSS in that set of multiple BSSIDs. c) The site is a non-access site, and the address of the probe request frame carries a broadcast address.

[0451] d) The site is a non-PCP site in a PBSS, and the address of the probe request frame carries a broadcast address.

[0452] e) The site is an IBSS and has not transmitted any ordinary communication beacon frames or DMG beacon frames since the last TBTT.

[0453] f) The site is a network site, and all of the following conditions are met:

[0454] 1) The probe request frame does not contain a mesh ID element.

[0455] 2) The probe request frame contains a mesh ID element, but the element does not carry a wildcard mesh ID and does not match the mesh ID of the MBSS connected to the site.

[0456] g) This site is not a network site and does not meet any of the following conditions:

[0457] 1) The SSID in the probe request is a wildcard SSID.

[0458] 2) The SSID in the probe request frame is the same as the SSID of the BSS where the site is located.

[0459] 2a) The site is an AP that belongs to the same co-located AP set as a 6GHz AP. The SSID in the Probe Request frame matches the SSID of the 6GHz AP, and the STA reports the co-located 6GHz AP in Beacon and Probe Response frames (see 26.17.2.4).

[0460] 3) The site is a member of a multi-BSSID set, and the SSID in the probe request frame is the same as the SSID of a member in the multi-BSSID set.

[0461] 4) The probe request frame contains a list of SSIDs, and the list contains the SSIDs of the BSS where the site is located.

[0462] 5) If dot11SSIDListImplemented is true, the STA is an AP that is in the same co-located AP set as a 6GHz AP. The SSID List element is present in the ProbeRequest frame and includes the SSID corresponding to the co-located 6GHz AP. The AP reports the co-located 6GHz AP in Beacon and Probe Response frames. (See 26.17.2.4 (Out of band discovery of a 6GHz BSS)).

[0463] 6) if dot11ShortSSIDListImplemented is true, the Probe Request frame contains a Short SSID and this Short SSID can be mapped to the BSSID of the STA's BSS.

[0464] 7) If dot11ShortSSIDListImplemented is true, the STA is an AP that is in the same co-located AP set as a 6GHz AP. The Short SSID List element is present in the Probe Request frame and includes the Short SSID field corresponding to the SSID of the 6GHz AP. The AP reports this 6GHz AP in its Beacon and Probe Response frames. (See 26.17.2.4 (Out of band discovery of a 6GHz BSS)).

[0465] h) Condition h is specifically condition h1 below, or, specifically condition h2 below.

[0466] h1) The site is not a mesh site, and address 3 in the probe request frame does not contain a wildcard BSSID, and one of the following conditions is met:

[0467] 1) The site does not belong to MLD, is not a member of a multi-BSSID set, and the address in the probe request frame does not match the BSSID of the BSS where the site is located.

[0468] 2) The site is a member of a multi-BSSID set, and no member of the multi-BSSID set belongs to an MLD, and the address in the probe request frame does not match the ID of any BSS in the multi-BSSID set.

[0469] 3) The site belongs to a certain MLD, no member of which belongs to a multi-BSSID set, and the unicast address does not match the BSSID of any BSS in which any site in the MLD resides. Optionally, a first site may have pre-managed frames, such as beacon frames and / or probe response frames, reporting to the second site the sites in the MLD that can match the BSSID field in the probe request frame.

[0470] 4) The site belongs to a certain MLD, which has a member belonging to a multi-BSSID set, and the unicast address does not match the BSSID of any BSS in the MLD, or the BSSID of any BSS in the multi-BSSID set to which any member of the MLD belongs. Optionally, a first site has pre-managed frames, such as beacon frames and / or probe response frames, to report to the second site the sites in the MLD that can match the BSSID field in the probe request frame.

[0471] h2) The site is not a mesh site, and address 3 in the probe request frame does not contain a wildcard BSSID, and one of the following conditions is met:

[0472] 1) The site does not belong to MLD, is not a member of a multi-BSSID set, and the address in the probe request frame does not match the BSSID of the BSS where the site is located.

[0473] 2) The site is a member of a multi-BSSID set, and no member of the multi-BSSID set belongs to an MLD, and the address in the probe request frame does not match the ID of any BSS in the multi-BSSID set.

[0474] 3) The site belongs to a certain MLD, and the unicast address does not match the BSSID of any BSS in that MLD. Optionally, there is a first site that has pre-managed frames, such as beacon frames and / or probe response frames, to report to the second site the sites in the MLD that can match the BSSID field in the probe request frame.

[0475] i) The dot11InterworkingServiceActivated flag of the site is true, and the probe request frame contains an Interworking element and an extension capability element containing 1 in the Interworking field, and at least one of the following conditions is met:

[0476] 1) The HESSID field in the Interworking element is missing, or the HESSID field exists but contains a wildcard HESSID or matches the HESSID field of the InterworkingInfo parameter in the source of the previous MLME-START or MLME-JOIN request.

[0477] 2) The access network type field in the Interworking element contains a wildcard access network type or matches the access network type of the site.

[0478] j) The probe request frame contains a DSSS parameter set element, in which the current channel field contains a value different from...

[0479] The value of dot11CurrentChannel.

[0480] k) The site is a DMG site, and the site's transmit antenna is not tuned to a state where the transmitter is the source of the probe request frame.

[0481] It should be noted that the detailed conditions included in the third condition can be deleted, added, or modified according to the needs of a specific scenario, and this application does not impose any restrictions.

[0482] The term "the site" as used above refers to the first site of the received probe request frame, or the site identified by the receiving address (address 1) in the probe request frame.

[0483] Step S803: The second station receives the probe response frame.

[0484] Specifically, if the first site or its associated multi-link device determines that a probe response frame can be sent based on the aforementioned conditions or rules, the first site or its associated multi-link device sends the probe response frame. Upon receiving the probe response frame, the second site may optionally reply with an Ack frame, thereby establishing an association with the site it requested to associate with in the probe request frame (i.e., the site identified by the receiving address). Optionally, the second site may also be a single-link device.

[0485] exist Figure 8 The method shown allows stations within an MLD to assist other stations within the same MLD in responding to probe response frames, and also allows them to assist any member of the Multiple BSSID set containing other stations within the same MLD in responding to probe response frames. This reduces the number of probe request frames sent by stations in the channel, increases air interface efficiency, and improves station association efficiency.

[0486] Optionally, the above Figure 4 The method embodiments shown are similar to Figure 8The illustrated method embodiments can be executed independently of each other or in combination. For example, the AP (referring to the reporting AP) can be implemented through... Figure 4 The illustrated method embodiment indicates the architecture of the MLD-based Multiple BSSID set to the site. The site can then select the APs to be associated with based on the MLD's Multiple BSSID set architecture and establish the association. Optionally, this can be specifically achieved through... Figure 8 The method embodiments shown are used to establish association relationships.

[0487] The apparatus provided in the embodiments of this application is described in detail below, which can reduce the number of probe request frames sent by stations in the channel and improve station association efficiency.

[0488] Figure 10 This application illustrates a communication device 1000 provided in an embodiment of the present application. This device can be an access point (AP) (e.g., a reporting AP in an AP multi-link device), a first station, or a second station as described in the above embodiments. It can also be a chip or processing system within the access point (AP) (e.g., a reporting AP in an AP multi-link device), the first station, or the second station, capable of implementing the above-described... Figure 4 The methods and functions of the embodiments shown, or the implementations of the above... Figure 8 The methods and functions of the illustrated embodiments. Due to differences in integration levels, the communication device may include, for example... Figure 10 One or more of the components shown. Figure 10 The components shown may include at least one processor 1001, a memory 1002, a transceiver 1003, and a communication bus 1004.

[0489] The following combination Figure 10 The various components of the communication device 1000 are described in detail below:

[0490] Processor 1001 is the control center of communication device 1000. It can be a single processor or a collective term for multiple processing elements. For example, processor 1001 can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this application, such as one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs). Processor 1001 can perform various functions of the communication device by running or executing software programs stored in memory 1002 and calling data stored in memory 1002. In a specific implementation, as one embodiment, processor 1001 may include one or more CPUs, for example... Figure 10 CPU0 and CPU1 are shown in the diagram.

[0491] In a specific implementation, as one example, the communication device 1000 may include multiple processors, for example... Figure 10 The processors 1001 and 1005 shown are illustrated. Each of these processors can be a single-core processor (SCPU) or a multi-core processor (Multi-CPU). Here, "processor" can refer to one or more communication devices, circuits, and / or processing cores used for processing data (e.g., computer program instructions).

[0492] The memory 1002 may be a read-only memory (ROM) or other type of static storage communication device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage communication device capable of storing information and instructions, or it may be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage communication device, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but is not limited thereto. The memory 1002 may exist independently and be connected to the processor 1001 via the communication bus 1004. The memory 1002 may also be integrated with the processor 1001. The memory 1002 is used to store the software program that executes the solution of this application, and the execution is controlled by the processor 1001.

[0493] Transceiver 1003 is used for communication with other devices (e.g., Figure 4 The site in the illustrated embodiment, or Figure 8 Communication between the second station in the illustrated embodiment and other stations. Of course, the transceiver 1003 can also be used to communicate with a communication network, such as Ethernet, a radio access network (RAN), or a wireless local area network (WLAN). The transceiver 1003 may include a receiving unit to implement the receiving function and a transmitting unit to implement the transmitting function.

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

[0495] In one example, the communication device 1000 is a complete device, which may include: a processor 1001, a memory 1002, a transceiver 1003, and a communication bus 1004. Optionally, it may also include other components, such as a display screen.

[0496] Optionally, the communication device 1000 is an access point (AP) (e.g., a reporting AP in an AP multi-link device), which can be used to implement the aforementioned... Figure 4 The methods and functions in the illustrated embodiments are as follows. For example, a computer program (instructions) is stored in the memory. When the processor calls the computer program, it implements the above-mentioned methods and functions. For instance, the processor is used to generate signaling or frames (carrying MLD information), and the transceiver is used to send signaling or frames (carrying MLD information). For example, the processor is used to control the transceiver to execute step S401. Of course, the process of generating MLD information involved in step S401 can also be performed by the processor.

[0497] Optionally, the communication device 1000 is a first station and can be used to implement the aforementioned... Figure 8 The illustrated embodiment relates to methods and functions of a first station. For example, a computer program is stored in a memory, and when a processor calls the computer program, it implements the above-described methods and functions. For instance, the processor is used to generate signaling or frames (such as probe response frames), and the transceiver is used to send signaling or frames (such as receiving probe request frames). For example, the processor is used to control the transceiver to receive the probe request frame in step S801, and then the processor determines whether a probe response frame needs to be replied to based on relevant conditions. If a reply is needed, a probe response frame is generated and sent through the transceiver.

[0498] In another example, the communication device 1000 is the chip system or processing system in the access point (AP) (e.g., the reporting AP in an AP multi-link device), the first site, or the second site, enabling the device with the chip system or processing system installed to perform the aforementioned functions. Figure 4 or Figure 8 The methods and functions in the illustrated embodiments. Therefore, the communication device 1000 may include, for example... Figure 10 Some of the components shown, such as the communication device 1000, include a processor that can be coupled to a memory, call instructions from the memory, and execute them, thereby configuring the device on which the chip system or processing system is installed to implement the aforementioned functionality. Figure 4 or Figure 8The methods and functions of the illustrated embodiments are as follows. Optionally, the memory may be a component in a chip system or a processing system, or it may be a component externally coupled to the chip system or processing system. In one example, the chip system or processing system is installed in the access point (AP) (e.g., the reporting AP in an AP multi-link device) or the first or second site, enabling the access point (AP) (e.g., the reporting AP in an AP multi-link device) or the first or second site to implement the corresponding methods and functions in the foregoing embodiments.

[0499] This chip system or processing system supports communication using the 802.11 series protocols, such as 802.11be, 802.11ax, and 802.11ac. This chip system can be installed in various devices that support WLAN transmission. Devices in WLAN transmission scenarios have been described at the beginning of this manual and will not be repeated here.

[0500] This application embodiment can divide the access point (AP) (e.g., the reporting AP in an AP multi-link device), the first site, or the second site into functional modules according to the above method example. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0501] When using integrated units, Figure 11 A possible structural schematic diagram of a communication device 1100 is shown. The communication device 1100 can be a chip or processing system in a link device or a multi-link device. The communication device 1100 can perform the operations of the multi-link device in the above method embodiments. The communication device 1100 includes a processing unit 1101 and a transceiver unit 1102.

[0502] In one example, the communication device 1100 is the aforementioned access point AP (e.g., the reporting AP in an AP multi-link device), or a first site, or a second site.

[0503] The processing unit 1101 can be used to control and manage the operation of the communication device 1100. For example, it can generate MLD information, or determine whether to reply with a probe response frame based on relevant conditions upon receiving a probe request frame. Another example is controlling the operation of the transceiver unit 1102. Optionally, if the communication device 1100 includes a storage unit, the processing unit 1101 can also execute programs or instructions stored in the storage unit to enable the communication device 1100 to implement the methods and functions involved in any of the above embodiments.

[0504] For example, the processing unit 1101 described above can control the transceiver unit to perform, for example... Figure 4 Step S401, or Figure 8 Step S801 and / or other processes used in the technology described herein. All relevant content regarding each step in the above method embodiments can be referenced to the functional description of the corresponding functional module, and will not be repeated here.

[0505] For example, the transceiver unit 1102 described above can transmit and receive data or signaling transmitted on one link, or it can transmit and receive data or signaling transmitted on multiple links. Optionally, the transceiver unit 1102 can be a single transceiver module, or it can include multiple transceiver modules. When the transceiver unit 1102 is a single transceiver module, that module can transmit and receive data on multiple links. For example, if the first multi-link device operates on two links, then when the transceiver unit 1102 includes two transceiver modules, one module operates on one link, and the other module operates on the other link. For example, the transceiver unit 1102 can be used to perform, for example... Figure 4 Step S401, or, Figure 8 Step S801 in the above method embodiments, and / or other processes used in the technology described herein. All relevant content regarding each step in the above method embodiments can be referenced to the functional description of the corresponding functional module, and will not be repeated here.

[0506] For example, the communication device 1100 can be Figure 10 The communication device shown, the processing unit 1101 can be Figure 10 The processor 1001 and transceiver unit 1102 in the middle can be Figure 10 The transceiver 1003 is included. Optionally, the communication device 1100 may further include a memory for storing program code and data corresponding to the communication device 1100 executing any of the multi-link device communication methods provided above. Figure 10 All descriptions of the relevant components can be found in the functional descriptions of the corresponding components of the communication device 1100, and will not be repeated here.

[0507] For example, the communication device 1100 may also be a chip or processor, wherein the processing unit 1101 is a processing circuit in the chip or processor, and the transceiver unit 1102 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 or exchange data with other coupled components, which can ensure that signaling or data information or program instructions are input into the chip or processor for processing, and output the processed data or signaling to other coupled components, and control the first multi-link device on which the chip or processor is installed to perform functions.

[0508] In another example, the communication device 1100 is the aforementioned access point AP (e.g., the reporting AP in an AP multi-link device) or a chip in the first or second site.

[0509] For example, the processing unit 1101 described above can be used to generate MLD information or to detect response frames, for example, Figure 4 The MLD information in step S401 is generated by processing unit 1101, or Figure 8 The probe response frame in S802 is generated by processing unit 1101 and / or used in other processes of the technology described herein. All relevant content regarding each step in the above method embodiments can be referenced to the functional description of the corresponding functional module, and will not be repeated here.

[0510] For example, the transceiver unit 1102 described above can transmit and receive data or signaling transmitted on one link, or it can transmit and receive data or signaling transmitted on multiple links. Optionally, the transceiver unit 1102 can be a single transceiver module, or it can include multiple transceiver modules. When the transceiver unit 1102 is a single transceiver module, that module can transmit and receive data on multiple links. For example, if the first station operates on two links, then when the transceiver unit 1102 includes two transceiver modules, one transceiver module operates on one link, and the other transceiver module operates on the other link. For example, the transceiver unit 1102 described above can be used to perform, for example... Figure 4 Step S401, or, Figure 8 Steps S801 and S802, and / or other processes used in the technology described herein. All relevant content regarding each step in the above method embodiments can be referenced to the functional description of the corresponding functional module, and will not be repeated here.

[0511] For example, the communication device 1100 can be Figure 10 The communication device shown, the processing unit 1101 can be Figure 10 The processor 1001 and transceiver unit 1102 in the middle can be Figure 10The transceiver 1003 is included. Optionally, the communication device 1100 may further include a memory for storing program code and data corresponding to the execution of any of the methods provided above by the communication device 1100. Figure 10 All descriptions of the relevant components can be found in the functional descriptions of the corresponding components of the communication device 1100, and will not be repeated here.

[0512] For example, the communication device 1100 may also be a chip or processor, wherein the processing unit 1101 is a processing circuit in the chip or processor, and the transceiver unit 1102 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 or exchange data with other coupled components, which can ensure that signaling or data information or program instructions are input into the chip or processor for processing, and output the processed data or signaling to other coupled components, and control the device on which the chip or processor is installed to perform its functions.

[0513] This application also provides a computer-readable storage medium storing computer program code. When the processor executes the computer program code, it causes the electronic device (such as an access point, a first station, or a second station) in which the processor resides to perform... Figure 4 ,or Figure 8 The method of any of the embodiments.

[0514] This application also provides a computer program product that, when run on a computer, causes the computer (such as an AP, a first site, or a second site) to perform... Figure 4 ,or Figure 8 The method of any of the embodiments.

[0515] This application also provides a communication device, which can exist in the form of a chip. The device includes a processor and an interface circuit. The processor is used to communicate with other devices through a receiving circuit, enabling the device to perform the aforementioned actions. Figure 4 , Figure 8 The method in any of the embodiments.

[0516] This application also provides a communication system, which includes the aforementioned access point (AP) (e.g., a reporting AP in an AP multi-link device) and a station. The access point (AP) (e.g., a reporting AP in an AP multi-link device) and the station can perform the above-mentioned... Figure 4 The method described in the embodiments. Alternatively, the communication system may include the aforementioned first station and second station, which can perform the above-described... Figure 8The methods described in the embodiments. The steps of the methods or algorithms described in conjunction with the disclosure of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in random access memory (RAM), flash memory, erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disks, portable hard disks, read-only optical discs (CD-ROMs), or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor, enabling the processor to read information from 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. Alternatively, the ASIC can be located in a core network interface device. Of course, the processor and the storage medium can also exist as discrete components in the core network interface device.

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

[0518] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of this application. It should be understood that the above description is only a specific embodiment of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made on the basis of the technical solution of this application should be included within the scope of protection of this application.

Claims

1. A communication method, characterized in that, include: The reporting access point (AP) generates multi-link device (MLD) information, wherein the MLD information includes information of the reporting AP, information of the reported AP, and common information. The common information includes the Media Access Control (MAC) address of the MLD. The reporting AP and the reported AP are contained in the MLD. The information of the reported AP includes 1 bit, which is used to indicate whether the reported AP is a Transmission Basic Service Set Identifier (BSSID) AP. The reporting AP sends the MLD information.

2. The method according to claim 1, characterized in that, The MLD information also includes the Multiple BSSID element of the Multiple Basic Service Set Identifier (MBSID) set to which the reporting AP is located.

3. The method according to claim 1, characterized in that, The MLD information also includes the MultipleBSSID element of the Multiple Basic Service Set Identifier (MBSID) set to which the reported AP is located.

4. The method according to claim 2 or 3, characterized in that, The Multiple BSSID element includes a nontransmitted BSSID profile, which includes the MAC address of the MLD where the nontransmitted BSSID AP is located.

5. The method according to any one of claims 1-3, characterized in that, The information of the reported AP also includes 1 bit, which is used to indicate whether the reported AP is a member of the Multiple BSSID set.

6. The method according to any one of claims 1-3, characterized in that, The shared information also includes the number of reported APs.

7. The method according to any one of claims 1-3, characterized in that, The reporting AP sends the MLD information, including: The reporting AP sends a management frame, which includes the MLD information.

8. The method according to claim 7, characterized in that, The management frame is one of the following: beacon frame, association response frame, or probe response frame.

9. A communication device, characterized in that, The communication device includes a processor and a memory, wherein: The memory configuration is used to store computer programs; The processor is configured to execute the computer program to enable the communication device to implement the method as described in any one of claims 1 to 8.

10. A chip, characterized in that, The chip includes a processor and a memory, the memory being configured to be coupled to the processor and to store computer programs and data required for the processor to run, and the processor being configured to execute the computer programs stored in the memory to enable a communication device containing the chip to implement the method as described in any one of claims 1 to 8.

11. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store a computer program that, when run on a processor, enables a communication device containing the processor to perform the method described in any one of claims 1 to 8.

Images