Method for exchanging signaling information in a wireless short-range network and communication device

Abstract

Embodiments of the present application provide a communication method and related apparatus applicable to a multi-link device in a wireless local area network WLAN, for example, applicable to a WLAN supporting 802.11be. The method comprises the step of a reporting access point AP transmitting a management frame to a station. The reporting AP belongs to a first AP multi-link device MLD, and the reporting AP belongs to a multi-BSSID set. The management frame contains MLD information. The MLD information carries, for example, information regarding other APs within the MLD to which the AP belongs, information regarding the multi-BSSID set to which the AP belongs, and information regarding APs within the multi-BSSID set including other APs within the MLD to which the AP belongs, using different types of MLD elements such as canonical MLD elements, virtual MLD elements, and multi-BSSID elements. Based on the management frame, the station obtains information regarding the reporting AP and other information regarding the reported AP. In this way, the station can select a corresponding AP or AP multi-link device to establish an association.

Description

Technology Field

[0001] The present application relates to the field of communication technology, and in particular, to a method for exchanging signaling information and a communication device in a wireless short-range network. Background Technology

[0002] To significantly improve the service transmission speed of WLAN systems, the Institute of Electrical and Electronics Engineers (IEEE) 802.11ax standard additionally uses Orthogonal Frequency Division Multiple Access (OFDMA) technology based on the existing Orthogonal Frequency Division Multiplexing (OFDM) technology. OFDMA technology supports multiple nodes that simultaneously transmit and receive data to achieve multi-station diversity gain. During the formalization process of 802.11ax in 2017, the U.S. Federal Communications Commission (FCC) announced a new free frequency band of 5925-7125 MHz, hereinafter referred to as 6 GHz. Accordingly, 802.11ax standards makers extend the operating range of 802.11ax-compliant devices from 2.4GHz and 5GHz to 2.4GHz, 5GHz, and 6GHz in 802.11ax Project Authorization Requests (PARs).

[0003] IEEE 802.11 next-generation Wi-Fi protocol (extremely high throughput, EHT) devices need to be forward compatible. Therefore, these devices also support the operating spectrums of 802.11ax-compliant devices, specifically supporting the 2.4 GHz, 5 GHz, and 6 GHz frequency bands. Channel splitting is performed based on the newly opened free 6 GHz frequency band, and the bandwidth that can be supported may exceed the maximum bandwidth of 160 MHz supported at 5 GHz, for example, 320 MHz. In the IEEE 802.11ax next-generation Wi-Fi extremely high throughput protocol, peak throughput can also be increased by using more streams in addition to using ultra-high bandwidth, for example, through cooperation with multiple frequency bands (2.4 GHz, 5 GHz, and 6 GHz), or by increasing the number of streams to 16. On the same frequency band, peak throughput can be further increased through the cooperation of multiple channels or in other ways. This reduces service transmission delay. Hereinafter, multiple frequency bands or multiple channels are collectively referred to as multiple links. Multiple links are configured in 802.11ax and earlier Wi-Fi standards having the same operating frequency band as 802.11ax, but different Basic Service Sets (BSS) are generally established for each of the multiple links. Communication with stations within the BSS to which a link belongs can only be performed simultaneously on one link.

[0004] The key feature of 802.11ax and earlier Multiple Basic Service Set Identifier (BSSID) technologies is the virtualization of a single physical AP into multiple logical APs, that is, the formation of multiple virtual networks. Each virtual network is used to manage different stations. Similar to AP products in current Wi-Fi scenarios, an AP can be virtualized into a home AP and a guest AP.

[0005] The method of applying multiple BSSID technologies to multi-link devices to provide the functions of multiple virtual networks is a technical problem being studied by those skilled in the art. means of solving the problem

[0006] The embodiments of the present application disclose a method for exchanging signaling information in a WLAN and a related apparatus.

[0007] According to a first aspect, an embodiment of the present application provides a method for exchanging signaling information in a WLAN, the method comprising: an access point AP generating a management frame. The AP belongs to a first AP multi-link device MLD. The management frame includes MLD information. The MLD information includes a first MLD element. A sub-element of the first MLD element is used to carry information regarding another AP within the first MLD to which the AP belongs. The first MLD element includes type information indicating the type of the MLD element. The access point transmits the management frame.

[0008] According to a second aspect, an embodiment of the present application provides a method for exchanging signaling information in a WLAN, the method comprising: a station receiving a management frame transmitted by an access point AP. The AP belongs to a first AP multi-link device MLD. The management frame contains MLD information. The MLD information includes a first MLD element. A sub-element of the first MLD element is used to carry information regarding another AP within the first MLD to which the AP belongs. The MLD element includes type information indicating the type of the MLD element. Based on the management frame, the station obtains information regarding another AP within the first MLD to which the AP belongs.

[0009] According to a third embodiment, a communication device in a wireless local area network (WLAN) is provided, the communication device comprising: a processing unit configured to generate a management frame—wherein the AP belongs to a first AP multi-link device MLD, the management frame contains MLD information, the MLD information contains a first MLD element, the sub-elements of the first MLD element are used to carry information regarding other APs within the first MLD to which the AP belongs, and the first MLD element contains type information indicating the type of the MLD element—; and a transceiver unit configured to receive and transmit the management frame.

[0010] According to a fourth embodiment, a communication device in a wireless local area network (WLAN) is provided, the communication device comprising: a transceiver unit configured to receive a management frame transmitted by an access point AP, wherein the AP belongs to a first AP multi-link device MLD, the management frame contains MLD information, the MLD information contains a first MLD element, the sub-elements of the first MLD element are used to carry information regarding another AP within the first MLD to which the AP belongs, and the MLD element contains type information indicating the type of the MLD element; and a processing unit configured to obtain information regarding another AP within the first MLD to which the AP belongs based on the management frame.

[0011] According to a fifth embodiment, a communication device is provided, which includes a processor and a memory. The memory stores instructions, and when the instructions are executed by the processor, the communication device: generates a management frame—where the AP belongs to a first AP multi-link device MLD, the management frame includes MLD information, the MLD information includes a first MLD element, the sub-elements of the first MLD element are used to carry information regarding another AP within the first MLD to which the AP belongs, and the first MLD element further includes type information indicating the type of the MLD element—; and becomes capable of transmitting the management frame.

[0012] According to a sixth embodiment, a communication device is provided, which includes a processor and a memory. The memory stores instructions, and when the instructions are executed by the processor, the communication device receives a management frame transmitted by an access point AP—where the AP belongs to a first AP multi-link device MLD, the management frame contains MLD information, the MLD information contains a first MLD element, the sub-elements of the first MLD element are used to carry information about another AP within the first MLD to which the AP belongs, and the MLD element contains type information indicating the type of the MLD element—; based on the management frame, information about another AP within the first MLD to which the AP belongs can be obtained.

[0013] According to the flexible signaling structure provided in this application, one or more MLD elements included in multiple BSSID elements and the MLD elements are used to describe information regarding one or more APs within a multi-AP multi-link device to help a station select an appropriate AP or AP MLD for association. The signaling structure of the MLD information provided in this embodiment of the application is simple and flexible.

[0014] In an implementation of the method or apparatus in any one of the aforementioned embodiments, the MLD element further comprises a common control field. The common control field comprises type information indicating the element type of the MLD element. In this embodiment of the present application, type information indicating the MLD element type is carried in the MLD element, so that the station can determine the type of the MLD based on the information to determine the relationship between all MLDs and the structure of the MLD in a multi-AP multi-link device.

[0015] In the implementation of the method or apparatus in any one of the aforementioned embodiments, the element type includes a canonical MLD element and a virtual MLD element. Specifically, the type information includes a virtual MLD field indicating whether the MLD element is a virtual MLD element.

[0016] In the implementation of the method or device in any one of the aforementioned embodiments, the virtual MLD field includes 1 bit.

[0017] If the MLD element is a virtual MLD element, the virtual MLD field is set to the first value.

[0018] If the MLD element is a canonical MLD element, the virtual MLD field is set to the second value.

[0019] In an implementation of a method or apparatus in any of the aforementioned embodiments, the element type includes a canonical MLD element, a virtual MLD element, and a special MLD element. The type information includes a virtual MLD field indicating whether the MLD element is a virtual MLD element, and a special MLD resource indicating whether the MLD element is a special MLD element.

[0020] In an implementation of the method or apparatus in any of the aforementioned embodiments, the virtual MLD field comprises 1 bit. The special MLD field comprises 1 bit. If the MLD element is a virtual MLD element, the virtual MLD field is set to a first value and the special MLD field is set to a second value. If the MLD element is a special MLD element, the virtual MLD field is set to a second value and the special MLD field is set to a first value. If the MLD element is a canonical MLD element, the virtual MLD field is set to a second value and the special MLD field is set to a second value.

[0021] In an implementation of the method or apparatus in any of the aforementioned embodiments, the MLD element further comprises an MLD common information field. The common control field further comprises an MLD address presence field indicating whether an MLD address field exists in the MLD common information field. The MLD address field carries an identifier of the first MLD.

[0022] In an implementation of a method or device in any of the aforementioned embodiments, where type information indicates that the MLD element is a virtual MLD element, the MLD common information field includes an MLD address field. Where type information indicates that the MLD element is a canonical MLD element, the MLD common information field includes an MLD address field.

[0023] In the implementation of the method or device in any of the aforementioned embodiments, where the type information indicates that the MLD element is a special MLD element, the MLD common information field does not include an MLD address field.

[0024] In an implementation of a method or apparatus in any of the aforementioned embodiments, if another AP in the first MLD belongs to a second multiple BSSID set and another AP in the second multiple BSSID set belongs to the second MLD, the MLD information further includes a second MLD element. A sub-element of the second MLD element carries information regarding an AP in the second MLD.

[0025] In an implementation of a method or device in any one of the aforementioned embodiments, if the AP belongs to a first multiple BSSID set, the MLD information further includes a first multiple BSSID element. The first multiple BSSID element includes information regarding a non-transmitting AP within the first multiple BSSID set.

[0026] In an implementation of the method or apparatus in any of the aforementioned embodiments, if a non-transmitting AP in the first multi-BSSID set belongs to the third MLD, the multi-BSSID element further comprises a third MLD element. A sub-element of the third MLD element carries information regarding another AP in the third MLD.

[0027] In an implementation of the method or apparatus in any of the aforementioned embodiments, if another AP in the first MLD belongs to the third multiple BSSID set and the AP in the third multiple BSSID set does not belong to the MLD, the MLD information further includes a fourth MLD element. The sub-elements of the fourth MLD element carry information regarding the AP.

[0028] In the implementation of the method or apparatus in any one of the aforementioned embodiments, the first MLD element is a formal MLD element, and type information within the first MLD element indicates that the first MLD element is a formal MLD element.

[0029] In the implementation of the method or device in any one of the aforementioned embodiments, the second MLD element is a virtual MLD element, and type information within the second MLD element indicates that the second MLD element is a virtual MLD element.

[0030] In the implementation of the method or apparatus in any one of the aforementioned embodiments, the third MLD is a formal MLD element, and the type information within the second MLD element indicates that the second MLD element is a formal MLD element.

[0031] In the implementation of the method or apparatus in any one of the aforementioned embodiments, the fourth MLD element is a special MLD element, and type information within the fourth MLD element indicates that the fourth MLD element is a special MLD element.

[0032] The communication device in the third, fourth, fifth, and sixth embodiments may be a chip. The processing unit may be a processing circuit of the chip. The transceiver unit may be an input / output interface circuit. The processing circuit may be configured to process signaling or data information provided by the input / output interface circuit. The input / output interface circuit may be configured to input / output data or signaling information to the chip.

[0033] According to a seventh aspect of the embodiments of the present application, a computer-readable storage medium is provided. The computer-readable storage medium stores computer program code. When the computer program code is executed on a processor, the processor is able to perform possible implementations corresponding to the method in either the first aspect or the second aspect.

[0034] According to the eighth aspect of the embodiments of the present application, a computer program product is provided. The program product stores a computer program (instructions) executed by the aforementioned processor. When the computer program is executed on the processor, the processor is able to perform possible implementations corresponding to the method in either the first aspect or the second aspect.

[0035] According to a ninth aspect of the embodiments of the present application, a communication device is provided. The device comprises a processor and may further comprise a transceiver and a memory. The transceiver is configured to receive and transmit information or to communicate with other network elements. The memory is configured to store a computer program (instructions). The processor is configured to execute a computer program to support a communication device for implementing possible implementations corresponding to the method in either the first or second aspect.

[0036] According to the tenth aspect of the embodiments of the present application, a communication device is provided. The device may exist in the form of a chip product. The structure of the device may include a processor and may further include memory. The memory is coupled to the processor and configured to store programs (instructions) and data required by the device. The processor is configured to execute a computer program stored in the memory to support the communication device in performing possible implementations corresponding to the method in either the first aspect or the second aspect. Optionally, the memory may be located in the processor and is internal storage. Alternatively, the processor may be located outside the processor, coupled to the processor, and is external storage.

[0037] According to the first aspect of the embodiments of the present 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 configured to communicate with another device through a receiving circuit so as to enable the device to perform possible implementations corresponding to the method in either the first aspect or the second aspect.

[0038] According to the 12th aspect of the embodiments of the present application, a communication device is provided and configured to perform possible implementations corresponding to the method in either the first aspect or the second aspect. Brief explanation of the drawing

[0039] The following describes the attached drawings used in the embodiments of the present application. FIG. 1 is a schematic diagram of the structure of a communication system according to an embodiment of the present application; FIG. 2a is a schematic diagram of the structure of a multi-link device according to an embodiment of the present application; FIG. 2b is a schematic diagram of another structure of a multi-link device according to an embodiment of the present application; FIG. 2c is a schematic diagram of another structure of a multi-link device according to an embodiment of the present application; FIG. 3a is a schematic diagram of multi-link communication according to an embodiment of the present application; FIG. 3b is another schematic diagram of multi-link communication according to an embodiment of the present application; FIG. 4 is a schematic diagram of the interaction of a communication method applied to a multi-link device in a WLAN according to an embodiment of the present application; FIG. 5 is a schematic diagram of the structure of a multi-AP multi-link device according to an embodiment of the present application; FIG. 6a is a schematic diagram of the structure of an MLD element according to an embodiment of the present application; FIG. 6b is a schematic diagram of the structure of another MLD element according to an embodiment of the present application; FIG. 6c is a schematic diagram of the structure of another MLD element according to an embodiment of the present application; FIG. 7 is a schematic diagram of the structure of a sub-element of an MLD element according to an embodiment of the present application; FIG. 8a is a schematic diagram of the structure of another multi-AP multi-link device according to an embodiment of the present application; FIG. 8b is a schematic diagram of the structure of another multi-AP multi-link device according to an embodiment of the present application; FIG. 9a is a schematic diagram of the structure of a management frame according to an embodiment of the present application; FIG. 9b is a schematic diagram of the structure of another management frame according to an embodiment of the present application; FIG. 9c is a schematic diagram of the structure of another management frame according to an embodiment of the present application; FIG. 9d is a schematic diagram of the structure of another management frame according to an embodiment of the present application; FIG. 10a is a schematic flowchart of a signaling information exchange method for a multi-AP multi-link device according to an embodiment of the present application; FIG. 10b is a schematic flowchart of another signaling information exchange method for a multi-AP multi-link device according to an embodiment of the present application; FIG. 11 is a schematic flowchart of a signaling information exchange method for a multi-AP multi-link device according to an embodiment of the present application; FIG. 12 is a schematic diagram of the structure of a multiple BSSID element according to an embodiment of the present application; FIG. 13a is a schematic diagram of the structure of another management frame according to an embodiment of the present application; FIG. 13b is a schematic diagram of the structure of another management frame according to an embodiment of the present application; FIG. 14a is a schematic diagram of the structure of a reduced neighbor reporting RNR element according to an embodiment of the present application; FIG. 14b is a schematic diagram of the structure of a TBTT information field in an RNR element according to an embodiment of the present application; FIG. 14c is a schematic diagram of the structure of another TBTT information field in an RNR element according to an embodiment of the present application; FIG. 15 is a schematic diagram of the composition of a communication device according to an embodiment of the present application; FIG. 16 is a schematic diagram of the composition of another communication device according to an embodiment of the present application. Specific details for implementing the invention

[0040] Hereinafter, the relevant technologies of the present application will be described first, and then embodiments of the present application will be described with reference to the attached drawings.

[0041] Embodiments of the present application provide a communication method applicable to a wireless communication system. The wireless communication system may be a wireless local area network (WLAN) or a cellular network. The method may be implemented by a communication device within the wireless communication system or by a chip or processor within the communication device. The communication device may be a wireless communication device that supports simultaneous transmission performed over a plurality of links. For example, the communication device is referred to as a multi-link device or a multi-band device. For example, in a wireless local area network, the communication device supports communication performed using IEEE 802.11 series protocols, and the IEEE 802.11 series protocols include 802.11be, 802.11ax, or 802.11a / b / g / n / ac.

[0042] 1. Multi-link device (MLD), also referred to as a multi-band device

[0043] A multi-link device MLD comprises one or more affiliated stations, and the affiliated stations are logical stations. The phrase “that the multi-link device comprises affiliated stations” is also briefly described in the embodiments of this application as “that the multi-link device comprises stations.” The affiliated stations may be Access Points (AP) or non-Access Point Stations (non-AP STA). For ease of explanation, in this application, a multi-link device in which the affiliated station is an AP may be referred to as a multi-link AP, a multi-link AP device, or an AP multi-link device, and a multi-link device in which the affiliated station is a non-AP STA may be referred to as a multi-link STA, a multi-link STA device, or an STA multi-link device.

[0044] A multi-link device MLD can implement wireless communication in accordance with 802.11 series protocols, for example, in accordance with the Extremely High Throughput (EHT) protocol, or in accordance with 802.11be-based or 802.11be-compatible protocols, and thereby implement communication with other devices. Of course, other devices may be multi-link devices or may not be multi-link devices.

[0045] Each logical station may operate on a single link, and multiple logical stations are permitted to operate on the same link. The link identifier mentioned below represents a single station operating on a single link. That is, if more than one logical station exists on a single link, more than one link identifier is required to represent the logical stations. The link mentioned below sometimes also indicates a station operating on the link. When data transmission is performed between a multi-link device and another multi-link device, prior to communication, the multi-link device and the other multi-link device may first negotiate or communicate with each other regarding the link identifier and the correspondence between the link or the station on the link, or the AP multi-link device indicates the correspondence between the link identifier and the link or the station on the link through a broadcast management frame, for example, a beacon frame. Therefore, during data transmission, the link identifier is carried without transmitting a large amount of signaling information to indicate the link or the station on the link. This reduces signaling overhead and improves transmission efficiency.

[0046] For the sake of explanation, an example is used where one of the aforementioned multi-link devices is an AP multi-link device and the other of the aforementioned multi-link devices is an STA multi-link device. For example, when the AP multi-link device establishes a BSS, a management frame transmitted by the AP multi-link device, such as a beacon frame, carries an element containing multiple link identifier information fields. Each link identifier information field may indicate a correspondence between a link identifier and a station operating on the link. Each link identifier information field includes a link identifier and additionally includes one or more of a MAC address, an operation class, and a channel number. One or more of the MAC address, operation class, and channel number may identify the link. As another example, in the multi-link association establishment process, the AP multi-link device and the STA multi-link device negotiate multiple link identifier information fields. In subsequent communication, the AP multi-link device or the STA multi-link device uses the link identifier to identify a station in the multi-link device. The link identifier may additionally indicate one or more attributes of the station's MAC address, operation class, and channel number. Alternatively, the MAC address may be an association identifier of the associated AP multi-link device. Optionally, where multiple stations operate on a single link, the meaning represented by the link identifier (which is a numeric ID) includes the channel number and operation class where the link is located, as well as the identifier of the station operating on the link, e.g., the station's MAC address or AID.

[0047] FIG. 1 is a diagram of an application scenario of an embodiment of the present application using a wireless short-range network as an example. The application scenario includes a first station (101) and a second station (102). The first station (101) communicates with the second station (102) through a plurality of links to achieve the effect of improving throughput. The first station may be a multi-link device, and the second station may be a single-link device, a multi-link device, etc. In one scenario, the first station (101) is an AP multi-link device, and the second station (102) is an STA multi-link device or a station (e.g., a single-link station). In another scenario, the first station (101) is an STA multi-link device, and the second station (102) is an AP (e.g., a single-link AP) or an AP multi-link device. In yet another scenario, the first station (101) is an AP multi-link device, and the second station (102) is an AP multi-link device or an AP. In another scenario, the first station (101) is an STA multi-link device, and the second station (102) is an STA multi-link device or a STA. Of course, the wireless short-range network may additionally include other devices. The quantities and types of devices shown in FIG. 1 are merely examples.

[0048] FIGS. 2a and 2b illustrate schematic diagrams of the structures of AP multi-link devices and STA multi-link devices participating in communication. 802.11 standards focus on the 802.11 Physical layer (PHY) and Media Access Control (MAC) layer portions of AP multi-link devices and STA multi-link devices (e.g., mobile phones and laptop computers).

[0049] As shown in FIG. 2a, a plurality of APs included in an AP multi-link device are independent of each other in the Low MAC layer and PHY layer, and are also independent of each other in the High MAC layer. A plurality of STAs included in an STA multi-link device are independent of each other in the Low MAC layer and PHY layer, and are also independent of each other in the High MAC layer.

[0050] As shown in FIG. 2b, multiple APs included in an AP multi-link device are independent of each other in the Low MAC layer and PHY layer, and share the High MAC layer. Multiple STAs included in an STA multi-link device are independent of each other in the Low MAC layer and PHY layer, and share the High MAC layer.

[0051] Of course, STA multi-link devices can use a structure where the high MAC layers are independent of each other, and AP multi-link devices can use a structure where the high MAC layers are shared. Alternatively, STA multi-link devices can use a structure where the high MAC layers are shared, and AP multi-link devices can use a structure where the high MAC layers are independent of each other. For example, the high MAC layer or the low MAC layer can be implemented by a single processor within the chip system of the multi-link device, or by different processing modules within the chip system.

[0052] For example, the multi-link device in the embodiments of the present application may be a single-antenna device or a multi-antenna device. For example, the multi-link device may be a device having more than two antennas. The number of antennas included in the multi-link device is not limited in the embodiments of the present application. For example, FIG. 2c illustrates an example where the AP multi-link device is a multi-antenna device and the STA multi-link device is a single-antenna device. In the embodiments of the present application, the multi-link device may allow services of the same access type to be transmitted over different links, or even allow the same data packets to be transmitted over different links. Alternatively, the multi-link device may not allow services of the same access type to be transmitted over different links, but may allow services of different access types to be transmitted over different links.

[0053] The frequency bands in which the multi-link device operates may include, but are not limited to, 1 GHz or lower, 2.4 GHz or lower, 5 GHz or lower, 6 GHz or lower, and high frequency 60 GHz or lower. FIGS. 3a and 3b illustrate two schematic diagrams of communication between a multi-link device and another device through multiple links in a wireless short-range network.

[0054] FIG. 3a illustrates a scenario in which an AP multi-link device (101) communicates with an STA multi-link device (102). The AP multi-link device (101) includes an affiliated AP (101-1) and an affiliated AP (101-2), and the STA multi-link device (102) includes an affiliated STA (102-1) and an affiliated STA (102-2), and the AP multi-link device (101) communicates with the STA multi-link device (102) in parallel via link 1 and link 2.

[0055] FIG. 3b illustrates a scenario in which an AP multi-link device (101) communicates with an STA multi-link device (102), an STA multi-link device (103), and an STA (104). The AP multi-link device (101) includes affiliated APs (101-1) through (101-3). The STA multi-link device (102) includes two affiliated STAs: STA (102-1) and STA (102-2). The STA multi-link device (103) includes two affiliated STAs: STA (103-1) and STA (103-2). STA (103-3) and STA (104) are each single-link devices. The AP multi-link device can communicate individually with the STA multi-link device (102) via links 1 and 3, communicate with the STA multi-link device (103) via links 2 and 3, and communicate with the STA (104) via link 1. For example, the STA (104) operates on the 2.4 GHz frequency band. The STA multi-link device (103) includes STA (103-1) and STA (103-2), wherein STA (103-1) operates on the 5 GHz frequency band and STA (103-2) operates on the 6 GHz frequency band. The STA multi-link device (102) includes STA (102-1) and STA (102-2), wherein STA (102-1) operates in the 2.4 GHz frequency band and STA (102-2) operates in the 6 GHz frequency band. In the AP multi-link device, the AP (101-1) operating in the 2.4 GHz frequency band can perform uplink or downlink data transmission with STA (104) and STA (102-2) within the STA multi-link device (102) via Link 1.An AP (101-2) operating in the 5GHz frequency band of an AP multi-link device can transmit uplink or downlink data to a STA (103-1) operating in the 5GHz frequency band of an STA multi-link device (103) via Link 2. An AP (101-3) operating in the 6GHz frequency band of an AP multi-link device (101) can transmit uplink or downlink data to a STA (102-2) operating in the 6GHz frequency band of an STA multi-link device (102) via Link 3, and can also transmit uplink or downlink data to a STA (103-2) operating in the STA multi-link device via Link 3.

[0056] It should be noted that FIG. 3a illustrates an AP multi-link device supporting only two frequency bands, FIG. 3b illustrates an AP multi-link device supporting three frequency bands (2.4 GHz, 5 GHz, and 6 GHz), each frequency band corresponding to one link, and that only an example is used in which the AP multi-link device (101) can operate on one or more of Link 1, Link 2, and Link 3 for illustrative purposes. On the AP side or the STA side, a link in this specification may also be understood as a station operating on a link. In actual applications, the AP multi-link device and the STA multi-link device may additionally support more or fewer frequency bands. That is, the AP multi-link device and the STA multi-link device may operate on more or fewer links. This is not limited to this embodiment of the application.

[0057] For example, a multi-link device is a device having wireless communication capabilities. This device may be a device of the entire system, or a chip, processing system, etc. installed in a device of the entire system. A device on which a chip or processing system is installed may be controlled by the chip or processing system to implement the methods and functions in the embodiments of the present application. For example, a multi-link STA in the embodiments of the present application may have wireless transceiver capabilities, may support 802.11 series protocols, and may communicate with a multi-link AP, another multi-link STA, or a single-link device. For example, a multi-link STA is any user communication device that enables a user to communicate with an AP and then communicate with a WLAN. For example, a multi-link STA may be user equipment capable of accessing a network, for example, a tablet computer, a desktop computer, a laptop computer, a notebook computer, an Ultra-mobile Personal Computer (UMPC), a handheld computer, a netbook, a Personal Digital Assistant (PDA), or a mobile phone; Alternatively, it may be an Internet of Things node within the Internet of Things, a vehicle-in-vehicle communication device within the Vehicle Internet, etc. The multi-link STA may alternatively be a chip or processing system in the aforementioned terminals. The multi-link AP in the embodiments of this application is a device that provides services to the multi-link STA and may support 802.11 series protocols. For example, the multi-link AP may be a communication entity such as a communication server, router, switch, or network bridge, or the multi-link AP may include various forms of macro base stations, micro base stations, relay stations, etc. Of course, the multi-link AP may be a chip and processing system in various forms of devices to implement the methods and functions in the embodiments of this application.In addition, multi-link devices can support high-speed and low-latency transmission. With the continuous evolution of application scenarios for wireless short-range networks, multi-link devices may be additionally applied to more scenarios, e.g., sensor nodes in smart cities (e.g., smart water meters, smart electric meters, and smart air detection nodes), smart devices in smart homes (e.g., smart cameras, projectors, displays, televisions, stereos, refrigerators, and washing machines), nodes in the Internet of Things, entertainment terminals (e.g., wearable devices such as AR and VR), smart devices in smart offices (e.g., printers or projectors), vehicle Internet of Things devices in the Internet of Vehicles, and some infrastructure in daily life scenarios (e.g., vending machines, self-service navigation consoles, self-service cash registers, and self-service ordering machines in supermarkets). Specific forms of multi-link STAs and multi-link APs are not specifically limited in the embodiments of this application and are merely examples for the purpose of description in this specification. 802.11 series protocols may include 802.11be, 802.11ax, 802.11a / b / g / n / ac, etc.

[0058] 2. Multiple Basic Service Set Identifier (BSSID) Mode

[0059] A multiple BSSID set is a combination of some cooperative APs, and all cooperative APs use the same operating class, the same channel number, and the same antenna port. In a multiple BSSID set, there is only one transmitted BSSID AP, and the other APs are non-transmitted BSSID APs. Information regarding the multiple BSSID set (i.e., multiple BSSID elements) is carried in beacon frames, probe response frames, or neighbor reports transmitted by the transmitted BSSID AP. Information regarding the BSSID of the non-transmitted BSSID APs is derived from the aforementioned received beacon frames, probe response frames, or neighbor reports based on the multiple BSSID elements, etc.

[0060] In multi-BSSID technology, a single physical AP can be virtualized into multiple logical APs to form a multi-BSSID set. Each virtualized AP manages a single BSS, and the different logical APs generally have different SSIDs and permissions, such as security mechanisms or transmission opportunities. In a multi-BSSID set, the BSSID of an AP consists of a transmitted BSSID, referred to as the transmitted AP, and the BSSIDs of the other APs consist of non-transmitted BSSIDs, referred to as the non-transmitted AP. Generally, multiple APs within a multi-BSSID set can also be understood as multiple cooperative AP devices obtained by virtualizing a single AP device. Only the AP whose BSSID is the transmitted BSSID can transmit management frames, such as beacon frames and probe response frames. If a Probe Request frame transmitted by an STA is directed at an AP whose BSSID is a non-transmitted BSSID in a set of multiple BSSIDs, the AP whose BSSID is a transmitted BSSID needs to assist in responding to the Probe Response frame. A Beacon frame transmitted by an AP whose BSSID is a transmitted BSSID contains multiple BSSID elements, and APs whose BSSID is a non-transmitted BSSID cannot transmit Beacon frames. The association identifiers (AID association identifiers) assigned by multiple virtual APs to stations managed by multiple virtual APs share a single space; that is, the AIDs assigned to stations managed by multiple virtual BSSs cannot be identical.

[0061] In the example, as shown in Table 1, the multiple BSSID element includes an element ID, a length, a maximum BSSID indicator, and a sub-element. The maximum BSSID indicator indicates that the maximum number of BSSIDs included in the aforementioned multiple BSSID set is n, and the optional sub-element includes information regarding each non-transmitted BSSID. The receiver can calculate the value of each BSSID within the multiple BSSID set based on the reference BSSID, the maximum BSSID indicator, and the BSSID index. Each BSSID includes 48 bits. The value of the most significant (48-n) bits of each BSSID within the multiple BSSID set is the same as the value of the most significant (48-n) bits of the reference BSSID, and the value of the least significant n bits of each BSSID within the multiple BSSID set is obtained by performing a modulo operation on the sum of the least significant n bits of the reference BSSID and the value of BSSID index x using 2n. The reference BSSID (i.e., the transmitted BSSID) is carried in the BSSID field within the MAC header of a frame (e.g., a beacon frame) containing multiple BSSID elements. For specific calculation methods, refer to the 802.11-2016 standard.

[0062] Element ID length Maximum BSSID indicator Optional sub-elements byte 1 1 6 variable

[0063] Table 1 Multiple BSSID elements

[0064] Table 2 may represent the "optional sub-elements" of Table 1.

[0065] Child element ID designation Scalable 0 Non-transmitted BSSID profile no 1-220 hold 221 Vendor-specific Vendor-Definition 222-255 hold

[0066] Table 2 Optional sub-elements

[0067] In Table 2, a non-transmitted BSSID profile comprises one or more elements of an AP or DMG STA having a non-transmitted BSSID, and the non-transmitted BSSID profile comprises, but is not limited to, the following elements:

[0068] 1. Multiple other elements within the beacon and non-transmitted BSSID capability-related elements that need to be included in each non-transmitted BSSID;

[0069] 2. SSID element and multiple BSSID-index elements;

[0070] 3. An additional FMS descriptor element included when multiple BSSID elements are carried from a beacon;

[0071] 4. Not any of the following elements: the Timestamp and Beacon Interval fields, DSSS Parameter Set, IBSS Parameter Set, Country, Channel Switch Announcement, Extended Channel Switch Announcement, Wide Bandwidth Channel Switch, Transmit Power Envelope, Supported Operating Classes, IBSS DFS, ERP Information, HT Capabilities, HT Operation, VHT Capabilities, VHT Operation, SIG Beacon Compatibility, Short Beacon Interval, SIG Capabilities, SIG Operation (11ah), and other elements—these elements are generally identical to the AP corresponding to the transmitted BSSID. Having element values ​​-; and

[0072] 5. Optional Non-Inheritance Element: This element is the last element within the non-transmitted BSSID profile. The non-inheritance element includes a series of element ID numbers and element ID extension numbers that exist in the non-transmitted BSSID and cannot be inherited from the transmitted BSSID. It should be noted that the specific details of the element are omitted from this specification. Specifically, as shown in Table 3, the non-inheritance element includes an element ID, a length, an element ID extension, a list of element IDs, and a list of element ID extensions. The element ID extension number exists only when the value of the element ID is 255.

[0073] 1 byte 1 byte 1 byte 1 byte or more 1 byte or more Element ID length Element ID extension List of element IDs Element ID expansion list

[0074] Table 3 Non-inherited elements

[0075] In general multi-BSSID technology, multiple BSSID sets are virtualized based solely on single-link devices. The method of applying multi-BSSID technology to multi-link devices to provide the functions of multiple virtual networks is a technical problem being studied by those skilled in the art.

[0076] Example 1

[0077] FIG. 4 illustrates a method for displaying information based on a multi-link device and multiple BSSIDs according to an embodiment of the present application. The method may be applied between stations, between an access point and a station, and between access points. For ease of explanation, communication between an access point and a station is used as an example in this embodiment of the present application.

[0078] For ease of explanation, an AP within a BSS identified by a transmitted BSSID within a multi-BSS set is referred to as a transmitted AP (transmitted BSSID AP), and an AP within a BSS identified by a non-transmitted BSSID is referred to as a non-transmitted AP (non-transmitted BSSID AP). Additionally, an AP transmitting a management frame carrying information about other APs is referred to as a reporting AP, and other APs within the management frame are referred to as reported APs. In this embodiment of the present application, an AP multi-link device and a device comprising an AP within a multi-BSSID set where the AP within the AP multi-link device is located are referred to as a multi-AP multi-link device. Of course, other names may exist. This is not limited to the present application. The present method involves one AP within the multi-AP multi-link device transmitting information about all other APs within the multi-AP multi-link device to a neighboring station, and designing a signaling structure for the information about the other APs.

[0079] The method includes, but is not limited to, the following steps.

[0080] Step S101: The access point transmits MLD information to the station.

[0081] The access point is an AP within a multi-link device. The station receiving the MLD information may be a station within a multi-link station device or a single-link station. Of course, the MLD information may also be transmitted by a station, and the station belongs to the MLD. The MLD information may also be received by an access point, and the access point belongs to the MLD or is a single-link access point. The following descriptions are explained using an example where an access point transmits MLD information to a station.

[0082] The AP transmitting MLD information is included in the MLD, and the MLD additionally includes one or more other APs; that is, the AP transmitting MLD information and other APs belong to the MLD. Optionally, the AP additionally belongs to a multiple BSSID set, and the multiple BSSID set additionally includes the transmitting AP and one or more non-transmitting APs. Optionally, other APs within the MLD may alternatively belong to a different multiple BSSID set.

[0083] In this embodiment of the present application, an AP multi-link device and a device containing an AP in a multi-BSID set in which the AP within the AP multi-link device is located are referred to as a multi-AP multi-link device. Of course, other names may exist. This is not limited to the present application. It should be noted that in this embodiment of the present application, an AP transmitting MLD information may be referred to as a reporting AP, and other APs displayed in the MLD information in the multi-AP multi-link device are referred to as reported APs. For example, the multi-AP multi-link device includes an MLD to which the reporting AP belongs, and optionally, additionally includes another MLD. The AP in the MLD to which the reporting AP belongs and the AP in the other MLD belong to a multi-BSID set.

[0084] MLD information displays information about other APs within a multi-AP multi-link device.

[0085] Other APs may be one or more of the following:

[0086] 1. Other APs may include APs belonging to the same AP MLD as the reported AP.

[0087] 2. If an AP belonging to the same AP MLD as the reporting AP belongs to a multiple BSSID set, the other AP additionally includes other APs within the multiple BSSID set.

[0088] 3. If a reporting AP belongs to a multi-BSSID set, other APs additionally include other APs that belong to the same multi-BSSID set as the reporting AP.

[0089] MLD information can be carried in one or more MLD elements, or optionally, MLD information can be additionally carried in multiple BSSID elements.

[0090] In addition, management frames transmitted by the reporting AP carry additional information about the reporting AP. For example, current 802.11 beacon frames carry information about the reporting AP.

[0091] A station receiving MLD information can determine, based on the MLD information, each reported AP included in a multi-AP multi-link device, the MLD to which each reported AP belongs, and which reported APs and reporting APs belong to the same multi-BSSID set. Additionally, the station can establish an association with the appropriate AP or AP MLD.

[0092] Optionally, MLD information may be carried in management frames, e.g., beacon frames, association response frames, probe response frames, authentication frames, or neighbor reports.

[0093] An AP multi-link device comprises n logical APs operating on multiple links. Thus, link identifiers Link 1, Link 2, ..., and Link n can be used to represent n logical APs. The MAC addresses of the APs are distinct, where n is 2 or greater. An AP multi-link device is identified using the MAC address of the MLD. That is, the MAC address is used to identify the AP multi-link device management entity. The MAC address of an AP multi-link device may be identical to one MAC address of the n logical APs included in the multi-link AP, or it may be distinct from all MAC addresses of the n logical APs. For example, the MAC address of an AP multi-link device may be a common MAC address and can identify the AP multi-link device.

[0094] In an example, one or more logical APs within an AP multi-link device may belong to one or more sets of multiple Basic Service Set Identifiers (BSSIDs). In an example, the logical APs within an AP multi-link device belong to different sets of multiple BSSIDs. In another example, multiple logical APs within an AP multi-link device may belong to the same set of multiple BSSIDs. For example, if two logical APs within an AP multi-link device operate on a single link, the two logical APs may belong to the same set of multiple BSSIDs.

[0095] For example, as illustrated in FIG. 5, the MAC address of the AP multi-link device is, for example, MLD 1. The multi-link device includes three logical APs, denoted as AP 11, AP 21, and AP 31. AP 11, AP 21, and AP 31 operate on link 1, link 2, and link 3, respectively. The MAC addresses of AP 11, AP 21, and AP 31 are BSSID-11, BSSID-21, and BSSID-31, respectively (before 802.11ax was established, the BSSID of the BSS established by the AP was the MAC address of the AP, and may subsequently be changed. For ease of explanation, an example in which the MAC address of the AP is the BSSID of the BSS established by the AP is used herein). AP 11 is a member of multi-BSSID set 1, and multi-BSSID set 1 additionally includes AP 13, whose MAC address is BSSID-13. AP 21 is a member of multi-BSSID set 2, and multi-BSSID set 2 additionally includes AP 22, whose MAC address is BSSID-22, and AP 23, whose MAC address is BSSID-23. AP 31 is a member of multi-BSSID set 3, and multi-BSSID set 3 additionally includes AP 32, whose MAC address is BSSID-32, and AP 33, whose MAC address is BSSID-33. Hereinafter, a device including an AP and an AP multi-link device within the same multi-BSSID set as an AP within a multi-link device is referred to as a multi-AP multi-link device. For example, AP 11, AP 21, AP 31, AP 22, AP 32, AP 13, AP 23, and AP 33 form a multi-AP multi-link device.

[0096] Step S102: The station receives MLD information transmitted by the access point AP.

[0097] Specifically, after receiving MLD information broadcast or unicast by an AP, the station parses the contents within the MLD information. Based on the contents parsed from the MLD information, the station can obtain the structure of multiple BSSID sets based on AP multi-link devices and information regarding each reported AP.

[0098] Specifically, the station parses a management frame transmitted by the reporting AP to obtain MLD information regarding the reporting AP. The MLD information includes one or more MLD elements and optionally includes multiple BSSID elements. Specifically, the MLD elements include information regarding multiple APs of the same MLD. If the reporting AP belongs to a multiple BSSID set, the MLD information additionally includes multiple BSSID elements. The multiple BSSID elements include information regarding other APs belonging to the same multiple BSSID set as the reporting AP, and additionally include information regarding APs within the same AP MLD as the other APs. The station understands that, based on the content parsed from the MLD information, it can obtain information regarding other APs within the multi-AP multi-link device where the reported AP is located.

[0099] The station receives the AP's management frame and obtains information regarding the reporting AP and other APs within the multi-AP multi-link device where the reporting AP is located. In this way, the station can establish an association with the corresponding AP or AP multi-link device.

[0100] Optionally, after acquiring information regarding a multi-AP multi-link device, the station may perform one or more of the following operations:

[0101] (1) A reporting AP is associated with one or more APs within an MLD located on a single link. For example, in FIG. 5, after a station receives MLD information transmitted by AP 11 with MAC address BSSID-11 on link 1, the station may choose to associate AP 11 with MAC address BSSID-11 and AP 31 with MAC address BSSID-31 in an AP multi-link device MLD 1 where AP 11 with MAC address BSSID-11 is located.

[0102] (2) Associate the reported AP with APs in other MLDs other than the MLD to which the AP belongs, and with other APs on one link. The APs in other MLDs to which the transmitted AP belongs and other APs in the MLD belong to the same multiple BSSID set. For example, in FIG. 5, after a station receives MLD information transmitted by AP 11 with MAC address BSSID-11 on Link 1, the station may choose to associate AP 22 with MAC address BSSID-22 and AP 32 with MAC address BSSID-32 in the AP multi-link device MLD 2. AP 22 with MAC address BSSID-22 and AP 21 with MAC address BSSID-21 belong to the same multiple BSSID set 2. AP 32 with MAC address BSSID-32 and AP 31 with MAC address BSSID-31 belong to multiple BSSID set 3.

[0103] Optionally, association in this specification refers to the exchange of one or more of a probe request frame and a probe response frame, an authentication request frame and an authentication response frame, and an association request frame or an association response frame.

[0104] In this embodiment of the present application, multiple BSSID technology is applied to a multi-link device to provide the functions of multiple virtual networks. Additionally, information regarding an AP within a multi-link device to which multiple BSSID technology is applied can be transmitted to a station using MLD information. Based on the MLD information, the station enhances the flexibility of station association by selecting an appropriate AP or AP multi-link device for association.

[0105] Example 2

[0106] This embodiment of the present application further describes a specific implementation of a signaling structure for MLD information. According to the flexible signaling structure provided in this embodiment, one or more MLD elements included in multiple BSSID elements and the MLD elements are used to describe information regarding one or more APs within a multi-AP multi-link device to help a station select an appropriate AP or AP MLD for association. The signaling structure for MLD information provided in this embodiment of the present application is simple and flexible.

[0107] First MLD Signaling Structure: In this embodiment of the present application, MLD information comprises one or more MLD elements. One MLD element is used to represent one MLD in a multi-AP multi-link device. The MLD element comprises a common control field, an MLD common information field, and one or more optional sub-elements. Optionally, the MLD common information field comprises an MLD address field and optionally comprises a field, e.g., an authentication algorithm field. The MLD address field represents the address of the MLD represented by the MLD element, and the address is used to identify one MLD. Optionally, the address of the MLD is the MAC address of the MLD. That is, the MAC address is used to identify the AP multi-link device management entity. The MAC address of the AP multi-link device may be the same as one MAC address of n APs included in the multi-link AP, or may be different from all MAC addresses of n APs. For example, the MAC address of the AP multi-link device is a common MAC address and can identify the AP multi-link device. Optionally, the common control field includes an MLD address presence field (or referred to as the MLD address presence field or MLD address presence identifier) ​​to indicate whether an MLD address field exists in the MLD common information field. Optionally, the common control field further includes an authentication algorithm presence field to indicate whether an authentication algorithm field exists within the MLD common information field. Optionally, the "current field" may include 1 bit. A first value indicates that a corresponding field exists, and a second value indicates that a corresponding field does not exist. For example, the first value is 1, and the second value is 0.Optionally, if the reporting AP belongs to a multi-BSSID set, the MLD information additionally includes a multi-BSSID element.

[0108] Optionally, MLD elements may include the following three types:

[0109] Type 1: Canonical MLD Element: A Canonical MLD Element carries information regarding all or some other APs belonging to the same MLD as the Reporting AP. A Canonical MLD Element includes at least one sub-element, and each sub-element carries information regarding other APs belonging to the same MLD as the Reporting AP. Of course, a Canonical MLD Element may be referred to as a Reporting MLD Element or may have other names. This is not limited to this embodiment of the application. For ease of explanation, a Type 1 MLD Element is referred to as a Canonical MLD Element hereinafter. The common information field of a Canonical MLD Element includes an MLD address field.

[0110] Type 2: Virtual MLD Element: A virtual MLD element carries information regarding all or some of the APs in another MLD within the multi-AP multi-link device where the reporting AP is located. Since multiple APs included in the MLD to which the reporting AP belongs belong to multiple sets of multiple BSSIDs, other APs within multiple sets of multiple BSSIDs may form different MLDs. A virtual MLD element includes at least one sub-element that indicates information regarding the APs included in the other MLD. It is understood that a virtual MLD element refers to a different MLD distinct from the MLD to which the reporting AP belongs. Of course, a virtual MLD element may alternatively have a different name. This is not limited to this embodiment of the application. For convenience of explanation, a Type 2 MLD element is referred to as a virtual MLD element below. A common information field of a virtual MLD element includes an MLD address field.

[0111] Type 3: Special MLD Element: This MLD element carries information regarding a single-link AP within a multi-AP multi-link device where the reporting AP is located. Since multiple APs included in the MLD to which the reporting AP belongs belong to multiple sets of multiple BSSIDs, other APs within multiple sets of multiple BSSIDs may form different MLDs. Of course, other APs within multiple sets of multiple BSSIDs may not belong to any MLD but are single-link APs. For example, the common information field of the special MLD element does not include an MLD address field. As another example, the special MLD element can also be considered a virtual MLD element, and the common information field of the special MLD element also includes an MLD address field. In this case, the MLD address within the MLD element is the MAC address of the single-link AP or the BSSID of the single-link AP.

[0112] In order to distinguish the three types of MLD elements described above, and to help the station determine which MLD element in the MLD information is for the MLD where the AP is located, which MLD element is for another MLD, and which element is for a single-link AP, type information indicating the type of MLD element is carried in the MLD element in this embodiment of the present application, so that the station can determine the type of MLD to determine the structure and relationship between all MLDs within a multi-AP multi-link device based on this information.

[0113] Type information indicating MLD element types may include, but is not limited to, the following implementations:

[0114] First implementation: A virtual MLD field is carried from an MLD element to indicate whether the MLD element is a virtual MLD element. For example, the virtual MLD field is an indicator bit and contains a 1-bit that indicates whether the MLD element is a virtual MLD element. For example, if the value of the 1-bit is a first value (e.g., 1), it indicates that the MLD element is a virtual MLD element. If the value of the 1-bit is a second value (e.g., 0), it indicates that the MLD element is not a virtual MLD element.

[0115] Additionally, a special MLD field is carried in the MLD element to indicate whether the MLD element is a special MLD element. For example, the special MLD field is an indicator bit and contains a 1-bit that indicates whether the MLD element is a special MLD element. For example, if the value of the 1-bit is a first value (e.g., 1), it indicates that the MLD element is a special MLD element. If the value of the 1-bit is a second value (e.g., 0), it indicates that the MLD element is not a special MLD element.

[0116] Optionally, if a virtual MLD field indicates that the MLD element is not a virtual MLD element, and a special MLD field indicates that the MLD element is not a special MLD element, this implicitly indicates that the MLD element is a canonical MLD element.

[0117] For example, if the MLD element is a canonical MLD element, the MLD address presence field in the common control field is set to a first value, e.g., 1, which indicates that there is an MLD address field in the MLD common information field. The virtual MLD field is set to a second value, e.g., 0, which indicates that the MLD is not a virtual MLD. The special MLD field is set to a second value, e.g., 0, which indicates that the MLD is not a special MLD.

[0118] If the MLD element is a virtual MLD element, the MLD address presence field within the common control field is set to a first value, e.g., 1, which indicates that there is an MLD address field within the MLD common information field. The virtual MLD field is set to a first value, e.g., 1, which indicates that the MLD is a virtual MLD. The special MLD field is set to a second value, e.g., 0, which indicates that the MLD is not a special MLD.

[0119] If the MLD element is a special MLD element, the MLD address presence field within the common control field is set to a second value, e.g., 0, which indicates that there is no MLD address field within the MLD common information field, or that there is no MLD common information field. The virtual MLD field is set to a second value, e.g., 0, which indicates that the MLD is not a virtual MLD. The special MLD field is set to a first value, e.g., 1, which indicates that the MLD is a special MLD.

[0120] Second implementation: An MLD type indicator field is carried in the MLD element to indicate the type of the MLD element. For example, the MLD type indicator field contains 2 bits. The first value indicates that the MLD element is a canonical MLD element, the second value indicates that the MLD element is a virtual MLD element, and the third value indicates that the MLD element is a special MLD element.

[0121] Of course, it should be noted that MLD elements can contain only two types: canonical MLD elements and virtual MLD elements. Special MLD elements can be considered virtual MLD elements. In this case, information indicating the type of the MLD element may include a virtual MLD field, but not a special MLD field. If the value of the virtual MLD field is the first value, it indicates that the MLD element where the MLD field is located is a virtual MLD element. If the value of the virtual MLD field is the second value, it indicates that the MLD element where the MLD field is located is a canonical MLD element. For example, the virtual MLD field contains 1 bit, where 1 indicates that the MLD element is a virtual MLD element and 0 indicates that the MLD element is a canonical MLD element. Of course, optionally, the type information within the MLD element may be a canonical MLD field to indicate whether the MLD element is a canonical MLD element. For example, if the value of the canonical MLD field is the first value, it indicates that the MLD element is a canonical MLD element. If the value of the canonical MLD field is the second value, this indicates that the MLD element is a virtual MLD element. For example, the canonical MLD field is 1 bit, the first value is 1, and the second value is 0.

[0122] FIG. 6a is a schematic diagram of the structure of an MLD element. An MLD element includes an element identifier, a length, an element identifier extension field, a common control field, an MLD common information field, and one or more optional sub-elements. The common control field includes a virtual MLD field and a special MLD field. Optionally, the common control field further includes an MLD address presence field. The MLD common information field includes an MLD address field. Optionally, the common control field further includes an authentication algorithm presence field to indicate whether an authentication algorithm field exists in the MLD common information field.

[0123] FIG. 6b is a schematic diagram of the structure of another MLD element. The MLD element includes an element identifier, a length, an element identifier extension field, a common control field, an MLD common information field, and one or more optional sub-elements. The common control field includes an MLD type indicator. Optionally, the MLD common control field further includes an MLD address presence field. The MLD common information field includes an MLD address field. Optionally, the common control field further includes an authentication algorithm presence field to indicate whether an authentication algorithm field exists in the MLD common information field.

[0124] Optionally, one MLD element additionally includes one or more sub-elements, and one sub-element describes information regarding one AP within a multi-AP multi-link device. For the sub-elements of a canonical MLD element, information regarding other APs belonging to the same MLD as the reported AP is described. For the sub-elements of a virtual MLD element, information regarding an AP within the MLD indicated by the MLD address field is described. For the sub-elements of a special MLD element, information regarding a single-link AP within a plurality of multiple BSSID sets containing APs within an AP multi-link device is described.

[0125] The content of each sub-element includes the AP's link identifier. Optionally, each sub-element additionally includes AP-related fields such as an SSID field, a timestamp field, a beacon interval field, and AP elements. The AP elements are, for example, a BSS load element, an EHT capability element, or an EHT operation element.

[0126] For example, the inheritance principle is applied to fields or elements carried from sub-elements describing information about the AP. The details are as follows: If a field or element carried from a sub-element is identical to a field or element of the reporting AP, the corresponding field or element of the reported AP does not need to be carried from the corresponding sub-element of the reported AP. If a field or element carried from a sub-element is different from a field or element of the reporting AP, the corresponding field or element of the reported AP needs to be carried from the corresponding sub-element of the reported AP.

[0127] As another example, a non-inherited element is used as a field or element carried in a sub-element describing information about the AP. The non-inherited element is the last element within the sub-element. The non-inherited element includes ID numbers and element ID extension numbers of a series of elements that cannot be inherited from the reported AP. It should be noted that the specific details of the element are omitted in this specification. Specifically, as shown in Table 3, the non-inherited element includes an element ID, a length, an element ID extension, an element ID list, and an element ID extension list. The element ID extension number exists only when the value of the element ID is 255.

[0128] The link identifier of the AP has a one-to-one correspondence with the operating class where the AP is located, the channel number, and the BSSID (MAC address) of the AP, and the one-to-one correspondence can be carried by other elements, for example, the reduced neighbor report (RNR) element described in Example 3.

[0129] FIG. 7 is a schematic diagram of the structure of a sub-element according to an embodiment of the present application. The sub-element includes a sub-element ID, a length, and a content field. The content field includes a link identifier of the AP corresponding to the sub-element. There is a correspondence between the link identifier and the operating class where the AP is located, the channel number, and the BSSID (MAC address) of the AP; that is, a station parsing the sub-element can learn the AP's operating class, channel number, and BSSID based on the link identifier and the correspondence between the link identifier and the three parameters. The content field further includes field 1, ..., field n, e.g., an SSID field, a timestamp field, and a beacon interval field. The content field further includes element 1, ..., element n, e.g., a BSS load element, an EHT capability element, and an EHT operation element. The last element may be a non-inherited element. The non-inherited element includes ID numbers of a series of elements that cannot be inherited from the reporting AP and element ID extension numbers.

[0130] For example, if the reporting AP belongs to a multi-BSID set, the management frame transmitted by the reporting AP, which carries MLD information, is in the multi-BSID element (only the transmitting BSSID AP can transmit the management frame) and additionally carries information indicating non-transmitting BSSID APs belonging to the same multi-BSID set as the reporting AP. The information in the multi-BSID element indicating non-transmitting BSSID APs within the multi-BSID set is referred to as a non-transmitting profile. If one of the non-transmitting BSSID APs belongs to an AP MLD, the non-transmitting profile additionally carries an MLD element. The MLD element is a canonical MLD element, as illustrated in FIG. 6a, 6b, or 6c. Each sub-element in the MLD element carries information regarding other APs belonging to the same AP MLD as the non-transmitting BSSID AP. The aforementioned inheritance principle is used in the fields or elements carried in the sub-elements describing information regarding other APs. In this case, there are two ways for the purpose of the inheritance principle. Method 1: As described above, the inherited object is still a reporting AP. Method 2: The inherited object is changed to a non-transmitting BSSID AP.

[0131] The first signaling structure of MLD information is applicable to multiple multi-AP multi-link devices.

[0132] Solution 1: Structure of a multi-AP multi-link device.Transmitted BSSID APs within multiple multiple BSSID sets do not originate from the same AP multi-link device. That is, the same AP multi-link device may include one transmitted BSSID AP belonging to a multiple BSSID set and additionally include one non-transmitted BSSID AP belonging to another multiple BSSID set. For example, AP 1 within one AP multi-link device (MLD 1) is a transmitted BSSID AP within multiple BSSID set 1, and AP 2 within the AP multi-link device (MLD 1) is a non-transmitted BSSID AP within multiple BSSID set 2. In this case, the network formed by the multiple BSSIDs of the multi-link device is more flexible and better suited to the service requirements of different stations.

[0133] According to the first signaling structure and multi-AP multi-link device described above in Solution 1, the present embodiment of the application provides a method for exchanging signaling information for a multi-AP multi-link device. For example, as illustrated in FIG. 10a, the present method comprises the following steps.

[0134] Step S201: The access point transmits a management frame to the station. The management frame carries MLD information. The MLD information includes one canonical MLD element and at least one virtual MLD element, optionally includes one additional multiple BSSID element, and optionally includes additional special MLD elements.

[0135] An access point belongs to an access point MLD. For example, an access point is an AP within an AP multi-link device, and the access point is referred to as a reporting AP. The station receiving the management frame may be a station within a multi-link station device or a single-link station.

[0136] Management frames are, for example, beacon frames, association response frames, probe response frames, authentication frames, or neighbor reports. MLD information carries information about other APs (referred to as reported APs) that share devices with the reporting AP. The reported AP may be at least one of the following:

[0137] 1. The reported AP may include other APs belonging to the same AP MLD as the reporting AP.

[0138] 2. If other APs belonging to the same AP MLD as the reporting AP belong to multiple BSSID sets, the reported AP additionally includes other APs within the multiple BSSID sets.

[0139] 3. If the reporting AP belongs to a multi-BSSID set, the reported AP additionally includes other APs that belong to the same multi-BSSID set as the reporting AP.

[0140] In the first signaling structure of the MLD information, the MLD information includes a canonical MLD element and a virtual MLD element, and optionally includes a special MLD element. The canonical MLD element includes information regarding one or more other APs within the first MLD to which the reporting AP belongs; that is, the canonical MLD element includes sub-elements, and one sub-element carries information regarding other APs within the first MLD. Optionally, if the reporting AP belongs to the first multi-BSSID set, the MLD information additionally includes a multi-BSSID element. Optionally, the multi-BSSID element includes information regarding one or more or all other APs within the first multi-BSSID set to which the reporting AP belongs. If other APs within the first MLD belong to the second multi-BSSID set, and the APs included in the second multi-BSSID set belong to the second MLD, the MLD information additionally includes one virtual MLD element. The virtual MLD element includes information regarding APs within the second MLD, for example, the virtual MLD element includes sub-elements, and one sub-element carries information regarding one AP within the second MLD. If another AP within the first MLD belongs to the third multiple BSSID set, and the AP included in the third multiple BSSID set does not belong to any MLD, the MLD information includes a special MLD element or a virtual MLD element. The MLD element includes a sub-element that carries information regarding the AP that does not belong to any MLD. Additionally, if a non-transmitting AP within the first multiple BSSID set additionally belongs to the third MLD, the multiple BSSID element additionally includes a fourth MLD element. The fourth MLD element may be a formal MLD element that carries information regarding another AP within the third MLD. That is, the MLD information may be carried in one or more MLD elements, or optionally, information regarding the reported AP may be additionally carried in a multiple BSSID element.

[0141] In addition, management frames transmitted by the reporting AP carry additional information about the reporting AP. For example, current 802.11 beacon frames carry information about the reporting AP.

[0142] It should be noted that MLD information may also be referred to as MLD multiple BSSID information, etc. Of course, MLD information may have other names. This is not specifically limited to this embodiment of the present application.

[0143] Step S202: The station receives a management frame transmitted by the access point.

[0144] Specifically, the station parses a management frame transmitted by the reporting AP to obtain MLD information regarding the reporting AP. The MLD information includes one or more MLD elements and optionally includes multiple BSSID elements. Specifically, if the reporting AP belongs to a first set of multiple BSSIDs, the MLD information additionally includes multiple BSSID elements. The multiple BSSID elements include information regarding other APs belonging to the same first set of multiple BSSIDs as the reporting AP, and optionally, additionally include information regarding APs within a third AP MLD that are the same as the other APs.

[0145] Optionally, the present method may learn that step S203: the station can additionally include a step of learning the structure of multiple BSSID sets based on AP multi-link devices and information regarding each reported AP based on the content parsed from MLD information.

[0146] The station receives a management frame and, based on the management frame, learns information about the reporting AP and information about other APs that share devices with the reporting AP. In this way, the station can select a corresponding AP or AP multi-link device to establish an association.

[0147] This embodiment of the present application provides signaling information. The signaling information carries information regarding each AP within a multi-link device to which multiple BSSID technology is applied. The signaling structure is simple and, for example, can carry information regarding all other APs in a multi-AP multi-link device. Furthermore, the signaling structure provided in this embodiment of the present application is applicable to a multi-AP multi-link device comprising a plurality of multi-link devices to which multiple BSSID technology is applied. The signaling structure is very flexible and simple.

[0148] The following describes the architecture of the multi-AP multi-link device in Solution 1. Figure 8a is a schematic diagram of the structure of the multi-AP multi-link device in Solution 1. An AP whose MAC address identifier ends in x is a transmitted BSSID AP, and an AP whose MAC address identifier ends in y or z is a non-transmitted BSSID AP. For example, a transmitted BSSID AP in a multi-BSSID set 1 is AP 1x with a MAC address identifier of BSSID-1x, and a non-transmitted BSSID AP in a multi-BSSID set 1 is AP 1y with a MAC address identifier of BSSID-1y. A transmitted BSSID AP in a multi-BSSID set 2 is AP 2x with a MAC address identifier of BSSID-2x, and non-transmitted BSSID APs in a multi-BSSID set 2 include AP 2y with an address identifier of BSSID-2y and AP 2z with a MAC address identifier of BSSID-2z. The transmitted BSSID AP in multiple BSSID sets 3 is AP 3x, whose MAC address identifier is BSSID-3x, and the non-transmitted BSSID APs in multiple BSSID sets 3 include AP 3y, whose MAC address identifier is BSSID-3y, and AP 3z, whose MAC address identifier is BSSID-3z. From FIG. 8a, it can be seen that the transmitted BSSID APs (i.e., transmitted APs) from different multiple BSSID sets are distributed across different AP multi-link devices, for example, AP 1x, whose MAC address is BSSID-1x, and AP 2x, whose MAC address is BSSID-2x, are located in AP multi-link device MLD 1 and AP multi-link device MLD 2, respectively.

[0149] For ease of understanding, in this embodiment of the present application, FIG. 8a is used as an example to explain signaling structures of MLD information in various cases.

[0150] Example 1: AP 1x within AP MLD 1 illustrated in FIG. 8a transmits a management frame, e.g., a beacon frame or a probe response frame. The transmission method may be broadcast or unicast. Thus, AP 1x is a reporting AP. As illustrated in FIG. 9a, the MLD information carried in the management frame includes three MLD elements. The first MLD element is a canonical MLD element, the common information field contains the address of AP MLD 1, the canonical MLD element carries two sub-elements, the first sub-element carries information regarding AP 2y, and the second sub-element carries information regarding AP 3x. The second MLD element is a virtual MLD element, the common information field contains the address of AP MLD 2, the virtual MLD element carries two sub-elements, the first sub-element carries information regarding AP 2x, and the second sub-element carries information regarding AP 3y. The third MLD element is a special MLD element, and the common information field does not exist or the MLD address field does not exist. The special MLD element carries one sub-element, and the sub-element carries information regarding AP 3z. Additionally, since the reported AP 1x belongs to multiple BSSID set 1, the MLD information of the management frame needs to additionally carry multiple BSSID elements. The element carries a non-transmitted BSSID profile, and the non-transmitted BSSID profile is information regarding AP 1y. Additionally, since AP 1y belongs to AP MLD 3, the non-transmitted BSSID profile additionally carries a fourth MLD element. The fourth MLD element may be a canonical MLD element, and the canonical MLD element implies that AP 2z and AP 1y belong to the same MLD. The common information field of the MLD element contains the address of AP MLD 3. The MLD element carries one sub-element, and the sub-element carries information regarding AP 2z.Accordingly, a station receiving a management frame can learn information regarding each AP within a multi-AP multi-link device and the relationships between the APs based on three MLD elements and multiple BSSID elements carried in the MLD information. For example, based on the first MLD element, the station can learn that AP 1x, AP 2y, and AP 3x all belong to MLD 1. Based on the second MLD element, the station can learn that both AP 2x and AP 3y belong to MLD 2. Based on the third MLD element, the station can learn that AP 3z is a single-link device. Based on the multiple BSSID elements, the station can learn that AP 1y and AP 1x belong to a single set of multiple BSSIDs. Based on the MLD elements included in the multiple BSSID elements, the station can learn that both AP 1y and AP 2z belong to MLD 3.

[0151] Example 2: AP 1x within AP MLD 1 illustrated in FIG. 8a transmits a management frame, e.g., a beacon frame or a probe response frame. The transmission method may be broadcast or unicast. As illustrated in FIG. 9b, the management frame carries MLD information. The MLD information includes three MLD elements. The first MLD element is a canonical MLD element, the common information field of the first MLD element contains the address of AP MLD 1, and two sub-elements are carried, the first sub-element carries information regarding AP 2y, and the second sub-element carries information regarding AP 3x. The second MLD element is a virtual MLD element, the common information field of the second MLD element contains the address of AP MLD 2, and two sub-elements are carried, the first sub-element carries information regarding AP 2x, and the second sub-element carries information regarding AP 3y. The third MLD element is a virtual MLD element, and the common information field of the third MLD element contains the address of AP 3z and carries one sub-element, and the sub-element carries information regarding AP 3z. Since the reported AP 1x belongs to a multiple BSSID set, the MLD information of the management frame needs to additionally carry multiple BSSID elements. The element carries a non-transmitted BSSID profile, and the non-transmitted BSSID profile is information regarding AP 1y. Also, since AP 1y belongs to AP MLD 3, the non-transmitted BSSID profile additionally carries a canonical MLD element. The common information field of the canonical MLD element contains the address of AP MLD 3 and carries one sub-element, and the sub-element carries information regarding AP 2z. It should be noted that in this example, no special MLD elements exist.Accordingly, a station receiving a management frame can learn information regarding each AP within a multi-AP multi-link device and the relationships between the APs based on three MLD elements and multiple BSSID elements carried in the MLD information. For example, based on the first MLD element, the station can learn that AP 1x, AP 2y, and AP 3x all belong to MLD 1. Based on the second MLD element, the station can learn that both AP 2x and AP 3y belong to MLD 2. Based on the third MLD element, the station can learn that AP 3z within the third MLD element is a single-link device. Based on the multiple BSSID elements, the station can learn that AP 1y and AP 1x belong to a single set of multiple BSSIDs. Based on the MLD elements contained in the multiple BSSID elements, the station can learn that both AP 1y and AP 2z belong to MLD 3.

[0152] Example 3: AP 2x within AP MLD 2 shown in FIG. 8a transmits a management frame, e.g., a beacon frame or a probe response frame. The transmission method may be broadcast or unicast. As shown in FIG. 9c, the management frame carries MLD information. The MLD information carries two MLD elements. One MLD element is a canonical MLD element, the common information field in the canonical MLD element contains the address of AP MLD 2, one sub-element is carried, and the sub-element carries information regarding AP 3y. The other MLD element is a special MLD element, the common information field is absent, one sub-element is carried, and the sub-element carries information regarding AP 3z. Since the reporting AP 2x belongs to a multi-BSID set, the MLD information in the management frame needs to additionally carry multiple BSSID elements. This element carries two non-transmitted BSSID profiles. One non-transmitted BSSID profile is information regarding AP 2y. Additionally, since AP 2y belongs to AP MLD 1, the non-transmitted BSSID profile of AP 2y additionally carries a canonical MLD element. The common information field of the canonical MLD element contains the address of AP MLD 1. The canonical MLD element carries two sub-elements. One sub-element carries information regarding AP 1x, and the other sub-element carries information regarding AP 3x. The other non-transmitted BSSID profile is information regarding AP 2z. Additionally, since AP 2z belongs to AP MLD 3, the non-transmitted BSSID profile of AP 2z additionally carries a canonical MLD element. The common information field of the canonical MLD element contains the address of AP MLD 3 and carries one sub-element, and the sub-element carries information regarding AP 1y.Accordingly, a station receiving a management frame can learn information regarding each AP within a multi-AP multi-link device and the relationships between the APs based on two MLD elements and multiple BSSID elements carried in the MLD information. For example, based on MLD element 1, the station can learn that both AP 2x and AP 3y belong to MLD 2. Based on MLD element 2, the station can learn that AP 3z is a single-link device. Based on multiple BSSID elements, the station can learn that AP 2x, AP 2y, and AP 2z all belong to a single set of multiple BSSIDs. Based on the MLD elements carried in the non-transmitted BSSID profile of AP 2y in the multiple BSSID elements, it can be determined that AP 1x, AP 2y, and AP 3x belong to MLD 1. Based on the MLD elements carried in the non-transmitted BSSID profile of AP 2z in multiple BSSID elements, it can be determined that AP 1y and AP 2z belong to MLD 3.

[0153] It should be noted that the positions of MLD elements and multiple BSSID elements are merely examples and are not limited to the order shown in FIGS. 9a through 9c in the embodiments of the present application. Since each MLD element includes a type identifier, it can be understood that the station can determine the type of the MLD element based on the type identifier. Accordingly, the positions of multiple MLD elements may also be arbitrary. Additionally, based on the element ID within the multiple BSSID element, the station can also identify that the element is a multiple BSSID element. Accordingly, the multiple BSSID element may also be placed before the MLD element.

[0154] Additionally, optionally, the management frame transmitted by the reporting AP needs to additionally carry the link identifier of the reporting AP, for example, a common information field carried in an EHT action element or an MLD element, for example, a common information field carried in an MLD element shown in FIG. 6a or FIG. 6b.

[0155] Optionally, information regarding all APs (including reporting APs and reported APs) additionally includes, but is not limited to, one or more of AP capability information, AP operation information, and AP link identifier. Optionally, information regarding APs may additionally include the AP's MAC address (BSSID), which includes some other fields or elements carried in a beacon in the current 802.11 protocol (e.g., 802.11-2016 protocol), e.g., a timestamp field, a beacon interval field, and an SSID element and a BSS load element. AP capability information includes an HT capability element, a VHT capability element, an HE capability element, and an EHT capability element. AP operation information includes an HT operation element, a VHT operation element, an HE operation element, and an EHT operation element. If the AP is a 6GHz AP, the AP capability elements do not include an HT capability element or a VHT capability element, but include an HE capability element and an EHT capability element. The action elements of AP do not include HT action elements or VHT action elements, but include HE action elements and EHT action elements.

[0156] Information regarding the reporting AP is carried in a management frame transmitted by the AP, e.g., a beacon frame or a probe response frame. Information regarding the AP sharing the device with the reporting AP is carried in an MLD element or a multiple BSSID element within the management frame transmitted by the AP. Device sharing means that the AP and the reporting AP are in a single multi-AP multi-link device. Of course, the first signaling structure of the MLD information provided in this embodiment of the present application may be additionally applicable to other multi-AP multi-link device structures. FIG. 8a is merely an example. For example, the signaling information provided in this embodiment of the present application may be additionally applicable to the multi-AP multi-link device structure in Solution 2, e.g., the multi-AP multi-link device structure illustrated in FIG. 8b. Also, in FIG. 8a and FIG. 8b, only three links are used as examples for illustrative purposes. The signaling information provided in this embodiment of the present application may be additionally applicable to the structure of a multi-AP multi-link device having more links.

[0157] In other possible implementations, the MLD information may additionally include only one MLD element. Optionally, if the reporting AP belongs to a first multi-BSSID set, the MLD information additionally includes a multi-BSSID element carrying information about other APs within the first multi-BSSID set. If other APs additionally belong to a second MLD, the multi-BSSID element additionally includes information about other APs within the second MLD. This MLD element carries other APs within the multi-AP multi-link device, excluding the reported AP carried in the multi-BSSID element. That is, in the multi-AP multi-link device where the reporting AP is located, all other reported APs not indicated in the multi-BSSID element are carried in a single MLD element, where the MLD element carries multiple sub-elements, and one sub-element carries information about one of the other reported APs. Specifically, the common information field within the MLD element carries one or more combinations of MLD identifiers and MLD addresses. The quantity of combinations is indicated in the common control field. Additionally, in addition to the link identifier of the reporting AP and information regarding the AP, the sub-element representing each reported AP needs to additionally carry the MLD identifier of the MLD where the AP is located. Optionally, the identifier of the MLD where the reported AP is located is the same as the MLD identifier corresponding to the reported AP in the RNR. For details regarding the RNR carrying the MLD identifier of the MLD where the reported AP is located, refer to the last embodiment. Optionally, when the reported AP is a single-link AP, the MLD address corresponding to the reported AP in the common field is the MAC address (BSSID) of the single-link AP. In this implementation, there are no virtual MLD elements, special MLD elements, etc.

[0158] Example 4: AP 1x within AP MLD 1 illustrated in FIG. 8a transmits a management frame, e.g., a beacon frame or a probe response frame. The transmission method may be broadcast or unicast. The management frame carries MLD information. The MLD information includes a single MLD element. The common information field of the MLD element contains three combinations of MLD identifiers and MLD addresses, which are: combination 1 of the identifier of MLD 1 and the address of MLD 1, combination 2 of the identifier of MLD 2 and the address of MLD 2, and combination 3 of the identifier of AP 3z and the address of AP 3z. Additionally, the MLD element carries five sub-elements, each carrying information regarding AP 2y, AP 3x, AP 2x, AP 3y, and AP 3z. Since the reported AP 1x belongs to a multi-BSID set, the MLD information of the management frame needs to additionally carry multiple BSSID elements. The element carries a non-transmitted BSSID profile, and the non-transmitted BSSID profile is information regarding AP 1y. Additionally, since AP 1y belongs to AP MLD 3, the non-transmitted BSSID profile additionally carries an MLD element. The common information field of the MLD element contains the address of AP MLD 3 and carries one sub-element, and the sub-element carries information regarding AP 2z. Accordingly, a station receiving a management frame can learn information regarding each AP within a multi-AP multi-link device and the relationships between the APs based on one MLD element and one multi-BSSID element carried in the MLD information. For example, based on the MLD identifier within the sub-element and the combination within the MLD element, the station can learn that AP 1x, AP 2y, and AP 3x all belong to MLD 1, that both AP 2x and AP 3y belong to MLD 2, and that AP 3z within the third MLD element is a single-link device.Based on the multiple BSSID elements, the station can determine that AP 1y and AP 1x belong to one set of multiple BSSIDs, and based on the MLD elements included in the multiple BSSID elements, the station can learn that both AP 1y and AP 2z belong to MLD 3.

[0159] The structure of the multi-AP multi-link device in Solution 2 is described below.

[0160] Solution 2:

[0161] Transmitted BSSID APs within multiple multiple BSSID sets belong to the same AP multi-link device. That is, if one or more APs within an AP multi-link device belong to multiple BSSID sets, all transmitted BSSID APs within multiple BSSID sets belong to a single AP multi-link device. For example, transmitted BSSID AP 1 within multiple BSSID set 1 and transmitted BSSID AP 2 within multiple BSSID set 2 belong to two different APs within AP multi-link device MLD 1. In this case, the multi-BSSID network configured based on the AP multi-link device is simpler, and the signaling MLD information overheads are lower.

[0162] Based on the structure of the multi-AP multi-link device in Solution 2, this embodiment of the present application provides a second signaling structure of MLD information.

[0163] In the second signaling structure of the MLD information, the MLD information includes one MLD element. Optionally, if the reporting AP belongs to the first multi-BSSID set, the MLD information additionally includes a multi-BSSID element. Optionally, the multi-BSSID element includes information regarding one or more or all other APs (non-transmitted BSSID APs) within the first multi-BSSID set to which the reporting AP belongs. The MLD element includes information regarding one or more other APs within the first MLD to which the reporting AP belongs, that is, the MLD element includes sub-elements, and one sub-element carries information regarding another AP within the first MLD. Regarding the other AP within the first MLD, the other AP within the first MLD is also a transmitted AP for the structure in Solution 2. If the other AP within the first MLD additionally belongs to a second multi-BSSID set, the sub-element of the other AP within the first MLD additionally includes a multi-BSSID element to indicate information regarding another AP (non-transmitted BSSID AP) within the second multi-BSSID set.

[0164] In the second signaling structure of the MLD information, the MLD information also includes MLD elements and optionally additionally includes multiple BSSID elements. Compared to the first signaling structure of the MLD information, the second signaling structure of the MLD information may not include various types of MLD elements, and the types are not distinguished. The MLD element includes a common control field and an MLD common information field, and optionally includes one or more sub-elements. One sub-element displays information regarding the reported AP. For example, the structure of the MLD element within the second signaling structure of the MLD information is illustrated in FIG. 6c, and the signaling structure of one sub-element is illustrated in FIG. 7.

[0165] According to the second signaling structure described above, this embodiment of the present application provides a different signaling information exchange method for a multi-AP multi-link device. For example, as illustrated in FIG. 10b, the present method comprises the following steps.

[0166] Step S301: The access point transmits a management frame to the station. The management frame carries MLD information. The MLD information includes MLD elements. Optionally, the sub-elements of the MLD elements include multiple BSSID elements.

[0167] An access point belongs to an access point MLD. For example, an access point is an AP within an AP multi-link device, and the access point is referred to as a reporting AP. The station receiving the management frame may be a station within a multi-link station device or a single-link station.

[0168] Management frames are, for example, beacon frames, association response frames, probe response frames, authentication frames, or neighbor reports. MLD information carries information about other APs (referred to as reported APs) that share the reporting AP and the device (a multi-AP multi-link device where the reporting AP is located). Reported APs are as follows:

[0169] 1. The reported AP includes other APs belonging to the same AP MLD as the reporting AP.

[0170] 2. If other APs belonging to the same AP MLD as the reporting AP belong to multiple BSSID sets, the reported AP additionally includes APs within the multiple BSSID sets.

[0171] 3. If the reporting AP belongs to a multi-BSSID set, the reported AP additionally includes other APs that belong to the same multi-BSSID set as the reporting AP.

[0172] MLD information may use MLD elements. If the reported AP described by the sub-elements of the MLD element belongs to a multiple BSSID set, the sub-elements additionally include multiple BSSID elements to indicate information regarding other APs (non-transmitting BSSID APs) within the same multiple BSSID set where the reported AP is located. For the signaling design and structure in MLD elements, refer to the descriptions in the preceding paragraphs. For the signaling design and structure in multiple BSSID elements, refer to the descriptions in the preceding paragraphs.

[0173] In addition, management frames transmitted by the reporting AP carry additional information about the reporting AP. For example, current 802.11 beacon frames carry information about the reporting AP.

[0174] It should be noted that MLD information may also be referred to as MLD multiple BSSID information, etc. Of course, MLD information may have other names. This is not specifically limited to this embodiment of the present application.

[0175] Step S302: The station receives a management frame transmitted by the access point.

[0176] Specifically, the station parses a management frame transmitted by the reporting AP to obtain MLD information regarding the reporting AP. The MLD information includes a single MLD element. Optionally, a sub-element of the MLD element includes multiple BSSID elements. Specifically, if the reporting AP belongs to a multiple BSSID set, the MLD information additionally includes multiple BSSID elements. The multiple BSSID elements include information regarding other APs belonging to the same multiple BSSID set as the reporting AP. If an AP belonging to the same MLD as the reporting AP additionally belongs to a transmitted AP within a second multiple BSSID set, a sub-element of the transmitted AP within the MLD element additionally includes multiple BSSID elements and carries information regarding a non-transmitted AP within the second multiple BSSID set.

[0177] Optionally, the present method may be understood to further include the step S303: the station can learn the structure of multiple BSSID sets based on AP multi-link devices and information regarding each reported AP based on the content parsed from MLD information.

[0178] The station receives the AP's management frame and, based on the management frame, learns information about the reporting AP and information about other APs that share devices with the reporting AP. In this way, the station can select a corresponding AP or AP multi-link device to establish an association.

[0179] The following describes the architecture of the multi-AP multi-link device in Solution 2. Figure 8b is a schematic diagram of the structure of the multi-AP multi-link device in Solution 2. An AP whose MAC address identifier ends in x is a transmitted BSSID AP, and an AP whose MAC address identifier ends in y or z is a non-transmitted BSSID AP. For example, a transmitted BSSID AP in a multi-BSSID set 1 is AP 1x with a MAC address identifier of BSSID-1x, and a non-transmitted BSSID AP in a multi-BSSID set 1 is AP 1y with a MAC address identifier of BSSID-1y. A transmitted BSSID AP in a multi-BSSID set 2 is AP 2x with a MAC address identifier of BSSID-2x, and non-transmitted BSSID APs in a multi-BSSID set 2 include AP 2y with a MAC address identifier of BSSID-2y and AP 2z with a MAC address identifier of BSSID-2z. The transmitted BSSID AP in multiple BSSID set 3 is AP 3x, whose MAC address identifier is BSSID-3x. From FIG. 8b, it can be seen that the transmitted BSSID APs from different multiple BSSID sets (i.e., the transmitted APs) are all in the AP multi-link device MLD 1.

[0180] For ease of understanding, in this embodiment of the present application, FIG. 8b is used as an example to explain signaling structures of MLD information in various cases.

[0181] Example 1: AP 1x within AP MLD 1 illustrated in FIG. 8b transmits a management frame, e.g., a beacon frame or a probe response frame. The transmission method may be broadcast or unicast. For example, as illustrated in FIG. 9d, the management frame carries MLD elements. The MLD common information field contains the address of AP MLD 1 and carries two sub-elements, the first sub-element carries information regarding AP 2x, and the second sub-element carries information regarding AP 3x. Since AP 2x carried in the first sub-element belongs to a multi-BSSID set, the sub-element needs to additionally carry one multi-BSSID element 2. The element carries two non-transmitted BSSID profiles describing information regarding AP 2y and AP 2z, respectively. Since the reporting AP 1x belongs to a multi-BSSID set, the MLD information in the management frame needs to additionally carry a multi-BSSID element 1. The element carries a non-transmitted BSSID profile, and the non-transmitted BSSID profile is information regarding AP 1y. Accordingly, a station receiving a management frame can learn information regarding each AP within a multi-AP multi-link device and the relationships between the APs based on the MLD information. For example, the station can learn that AP 1x, AP 2x, and AP 3x all belong to MLD 1 based on the MLD element. The station can learn that AP 2x, AP 2y, and AP 2z all belong to multi-BSSID set 2 based on the multi-BSSID element 2 within the first sub-element. The station can learn that both AP 1x and AP 1y belong to multi-BSSID set 1 based on the multi-BSSID element 1.

[0182] It should be noted that the positions of MLD elements and multiple BSSID elements are merely examples and are not limited to the order shown in FIG. 9d in the embodiments of the present application. Since each MLD element includes a type identifier, it can be understood that the station can determine the type of the MLD element based on the type identifier. Therefore, the positions of multiple MLD elements may also be arbitrary. Additionally, based on the element ID within the multiple BSSID element, the station can also identify that the element is a multiple BSSID element. Therefore, the multiple BSSID element may also be placed before the MLD element.

[0183] In this embodiment, regarding the flexible structure of a multi-AP multi-link device, a signaling structure of MLD information is designed to represent the flexible structure of the multi-AP multi-link device. The MLD information describes information regarding one or more APs within the multi-AP multi-link device using one or more MLD elements included in multiple BSSID elements and MLD elements. The signaling structure of the MLD information is simple and flexible, and information regarding APs included in the structure of the multi-AP multi-link device can be represented flexibly and completely. Additionally, the access point represents a multi-BSID set structure based on the AP multi-link device to the station based on the MLD information. Based on the MLD information, the station obtains information regarding each AP within the multi-AP multi-link device, which can assist the station in selecting an appropriate AP or AP MLD for association. This enhances the flexibility of the station in selecting an AP for association.

[0184] Example 3

[0185] Embodiments of the present application provide another signaling information exchange method (including a transmitting method and a receiving method) for a multi-AP multi-link device. In this embodiment, an RNR element, an MLD element, and multiple BSSID elements are used together to prevent a reporting AP from broadcasting information regarding one or more or all APs within the multi-AP multi-link device where the reporting AP is located. This reduces signaling overheads. Additionally, to avoid repeated parameters such as the AP's operation class, channel number, and BSSID in subsequent multi-link operations, the AP's link identifier is added to the RNR element and multiple BSSID elements. A correspondence exists between the AP's link identifier and parameters such as the AP's operation class, channel number, and BSSID. In subsequent transmission or communication, parameters such as the AP's operation class, channel number, and BSSID do not need to be carried. This reduces signaling overheads. In addition, since the operation class and channel number of the non-transmitted BSSID in a multi-BSID element are the same as the operation class and channel number of the transmitted BSSID in a multi-BSID element, the two parameters, namely the operation class and channel number, do not appear in the non-transmitted BSSID profile of the multi-BSID element. This further reduces signaling overheads.

[0186] This embodiment of the present application provides another information exchange method for a multi-AP multi-link device. As illustrated in FIG. 11, the present method further comprises the following steps.

[0187] Step S401: The access point transmits a management frame. The management frame includes a reduced neighbor report element, an RNR element, and multiple BSSID elements, and optionally includes an MLD element.

[0188] The access point belongs to the access point MLD. For example, the access point is an AP within an AP multi-link device, the management frame is transmitted by the access point, and the access point is referred to as the reporting AP. The station receiving the management frame may be a station within a multi-link station device or a single-link station. The reporting AP belongs to a multi-BSSID set, the reporting AP is a transmitted AP within the multi-BSSID set, and the multi-BSSID set additionally includes a non-transmitting AP. Accordingly, the management frame includes a multi-BSSID element. The multi-BSSID element includes the non-transmitting AP's non-transmitting BSSID profile to identify the non-transmitting AP.

[0189] Optionally, the management frame is a beacon frame, association response frame, probe response frame, authentication frame, or neighbor report.

[0190] The RNR element, MLD element, and multiple BSSID element carry information about other APs (referred to as the reported AP) that share the device with the reporting AP.

[0191] Step S402: The station receives a management frame transmitted by the access point.

[0192] Specifically, the station parses the management frame transmitted by the reporting AP to obtain RNR elements and multiple BSSID elements, and optionally obtains MLD elements to obtain a multiple BSSID set structure based on the AP multi-link device.

[0193] Optionally, the present method further comprises step S403: determining, based on a management frame, a multi-BSSID set structure based on an AP multi-link device and information regarding each AP. Additionally, the station may further select an appropriate AP or AP MLD for association based on the structure and information regarding each AP.

[0194] Based on this solution, the station can obtain information regarding the reporting AP and information regarding other APs that share devices with the reporting AP, based on the management frame. In this way, the station can select an appropriate AP or AP multi-link device to establish an association.

[0195] The RNR element, MLD element, and multiple BSSID element carry information about other APs (referred to as the reported AP) that share the device with the reporting AP.

[0196] The reported AP is as follows:

[0197] 1. The reported AP includes other APs belonging to the same AP MLD as the reporting AP.

[0198] 2. If other APs belonging to the same AP MLD as the reporting AP belong to multiple BSSID sets, the reported AP additionally includes APs within the multiple BSSID sets.

[0199] 3. If the reporting AP belongs to a multi-BSSID set, the reported AP additionally includes other APs that belong to the same multi-BSSID set as the reporting AP.

[0200] In addition, management frames transmitted by the reporting AP carry additional information about the reporting AP. For example, current 802.11 beacon frames carry information about the reporting AP.

[0201] Additionally, to avoid repeated parameters such as the AP's operation class, channel number, and BSSID in subsequent multi-link operations, in this embodiment of the present application, the AP's link identifier is added to the RNR element and multiple BSSID elements so that parameters such as the AP's operation class, channel number, and BSSID have a one-to-one correspondence.

[0202] The following describes in detail, with reference to the RNR element, MLD element, and multiple BSSID element, the aforementioned multiple BSSID set structure based on an AP multi-link device, information regarding the APs within the structure, and how the relationships between the APs are represented.

[0203] Part 1: RNR Factors

[0204] First, the RNR element contains simplified information regarding other APs belonging to the same MLD as the reporting AP, and information regarding other APs belonging to the same multiple BSSID set as the other AP. Optionally, simplified information regarding non-transmitting APs belonging to the same multiple BSSID set as the reporting AP is not carried. For example, the multiple BSSID set structure of the AP multi-link device illustrated in FIG. 8a is used as an example. The RNR element transmitted by the reporting AP carries simplified information regarding AP 2y, AP 3x, AP 2x, AP 3y, AP 3z, and AP 2z, and does not carry simplified information regarding AP 1y. Since both AP 1x and AP 1y belong to a single multiple BSSID, AP 1y is a non-transmitting BSSID AP and is carried in the multiple BSSID element transmitted by AP 1x. AP 1x acts as the reporting AP, and information regarding AP 1x is carried in the management frame. In this case, simplified information regarding non-transmitting BSSID APs within the multiple BSSID sets where the reporting AP is located does not need to be carried in the RNR element. This reduces signaling overhead caused by carrying repeated signaling.

[0205] Second, in order to avoid repeated occurrences of parameter information of each AP, such as operation class, channel number, and BSSID, in other multi-link operation interaction processes, the RNR element additionally carries the link identifier of each reported AP and can indicate the correspondence between the link identifier of the reported AP and three parameters such as the operation class, channel number, and BSSID of the reported AP.

[0206] Additionally, optionally, the RNR element further carries information indicating the relationship between the reported AP and the reporting AP.

[0207] For example, an RNR element may additionally include signaling information indicating one or more of the following three relationships:

[0208] 1. Whether the reported AP and the reporting AP came from the same MLD;

[0209] 2. Whether any other AP and the reported AP within the MLD where the reporting AP is located originated from the same multiple BSSID; and

[0210] 3. Whether the reported AP and the reporting AP are in the same MLD, or whether the reported AP belongs to the same set of multiple BSSIDs as a member of the MLD to which the reporting AP belongs.

[0211] For example, the three aforementioned relationships are individually indicated using 1 bit. In the example, information is carried in the BSS parameter field within the TBTT information field in the RNR element to indicate one or more of the aforementioned relationships. For example, the co-MLD field is carried in the BSS parameter field. The co-MLD field indicates whether the reported AP and the reporting AP are in the same MLD, or whether the member AP of the MLD to which the reporting AP belongs and the reported AP belong to the same set of multiple BSSIDs. In another example, the co-MLD multiple BSSID field is carried in the BSS parameter field to indicate whether any other AP in the MLD where the reporting AP is located and the reported AP come from the same set of multiple BSSIDs. For example, the co-MLD bit in FIG. 14c is used to indicate a third relationship. Its specific form is not limited in the present invention.

[0212] In another example, the RNR element can indicate one or more of the following two types:

[0213] Signaling 1: whether multiple reported APs are from the same MLD; and

[0214] Signaling 2: Whether multiple reported APs are from the same multiple BSSID set.

[0215] Signaling 1 can be implemented by adding an MLD identifier to the information regarding the reported AP. If the MLD identifiers of multiple reported APs are identical, this indicates that multiple reported APs come from the same MLD. Signaling 2 can be implemented by adding a multiple BSSID set identifier to the information regarding the reported AP. If the multiple BSSID set identifiers of multiple reported APs are identical, this indicates that multiple reported APs come from the same multiple BSSID set. Optionally, if the MLD identifier carried in the information regarding the reported AP is a special value, e.g., 0, this indicates that the reported AP and the reporting AP belong to the same MLD. Optionally, if the multiple BSSID set carried in the information regarding the reported AP is set to a special value, this indicates that the reported AP and the reporting AP belong to the same multiple BSSID set.

[0216] Based on the aforementioned signaling, the RNR can indicate the relationship between the reported AP and the reporting AP and the relationship between multiple reported APs, so that the station can obtain the relationship between the reported AP and the reporting AP and the relationship between multiple reported APs based on the aforementioned signaling in the RNR element.

[0217] Additionally, since information regarding the reported APs further includes link identifiers, the relationships between APs can be determined based on link identifiers and the relationships between link identifiers and MLD identifiers and / or multiple BSSID set identifiers. For example, Fig. 8a is used as an example. The link ID of the reported AP 2y is 2, and the MLD identifier is 1. The link ID of the reported AP 3x is 4, and the MLD identifier is 1. It can be learned that AP 2y and AP 3x have the same MLD identifier and belong to the same MLD. It can also be learned that the AP with link ID 2 and the AP with link ID 4 belong to the same MLD. Therefore, because the link identifiers of the reported APs are unique, the relationships between the reported AP and the reporting AP, and the relationships between multiple reported APs, do not need to be further indicated in the MLD element. This avoids repeated signaling indicators.

[0218] In other implementations, signalings indicating the relationship between APs (e.g., signaling 1 and signaling 2) may not be carried in the RNR element but may be carried in the MLD element. The signalings are carried in the sub-elements of each MLD element.

[0219] Part 2: MLD Elements

[0220] For the type of MLD element transmitted by the reporting AP and the structure of the transmitted MLD element, the description in Example 2 may be referenced. Details are not described again here.

[0221] Part 3: Multiple BSSID Elements

[0222] If the reporting AP belongs to a single set of multiple BSSIDs, the management frame additionally includes multiple BSSID elements. The multiple BSSID elements contain information regarding one or more non-transmitting APs within the set of multiple BSSIDs to which the reporting AP belongs, and are referred to as non-transmitting BSSID profiles. The non-transmitting BSSID profiles carry information regarding the non-transmitting APs and additionally include the link IDs of the non-transmitting APs. This avoids high signaling overhead and signaling redundancy caused by carrying multiple parameter information, such as the operation class, channel number, and BSSID.

[0223] Methods for carrying link identifiers in multiple BSSID elements include, but are not limited to, the following two methods:

[0224] In the first method, if a non-transmitting AP indicated by a non-transmitting BSSID profile in a multi-BSSID element additionally belongs to one MLD and the non-transmitting BSSID profile of the non-transmitting AP additionally includes one MLD element, a sub-element in the MLD element indicates information regarding other APs in the MLD to which the non-transmitting AP belongs. In this case, the link identifier of the non-transmitting AP may be carried in the MLD element, for example, in the common information field of the MLD element. Optionally, the common control field of the MLD element additionally includes a link identifier (link ID) presence field to indicate whether a link ID field appears or exists. Optionally, the structure of the multi-BSSID element is illustrated in FIG. 12. In another example, the virtual MLD field and special MLD field in FIG. 12 may be replaced with an MLD type indicator as a second structure of the multi-BSSID element.

[0225] In the second method, the link identifier of the non-transmitting AP may be carried in the non-transmitting AP's non-transmitting BSSID profile, but not in the MLD element. In the second implementation, the non-transmitting BSSID profile may include an MLD element or may not include an MLD element.

[0226] Since simplified information regarding a non-transmitting AP is not carried in the RNR element, to determine the relationship between a non-transmitting AP and another reported AP, this embodiment of the present application provides the following two implementations:

[0227] Method 1: If a non-transmitting AP belongs to a single MLD, one MLD element may be carried from the non-transmitting BSSID profile. The MLD element includes a sub-element to indicate information about other APs within the MLD to which the non-transmitting AP belongs, in order to indicate that the non-transmitting AP and the reported AP belong to the same MLD. For example, as illustrated in FIG. 8a, AP 1x transmits a management frame. Both AP 1x and AP 1y belong to multiple BSS set 1. The RNR element may not carry information about AP 1y. The multiple BSSID elements within the management frame carry the non-transmitting BSSID profile of AP 1y. The non-transmitting BSSID profile additionally carries one MLD element. The sub-element in the MLD element carries information about AP 2z. A station receiving a management frame can determine the relationship between AP 1y and other APs based on the RNR element and the multiple BSSID element: AP 1y and AP 1x belong to multiple BSS set 1, and AP 1y and AP 2z belong to MLD 3.

[0228] Method 2: The non-transmitted BSSID profile does not carry an MLD element. The non-transmitted BSSID profile needs to carry an MLD identifier, which is used together with the MLD identifier in the information regarding the reported AP within the RNR to indicate whether the non-transmitted BSSID AP carried in the RNR and the reported AP come from the same MLD. For example, as illustrated in Fig. 8a, AP 1x transmits a management frame. Both AP 1x and AP 1y belong to multiple BSS set 1. The RNR element may not carry information regarding AP 1y. The information regarding the reported AP in the RNR element carries an MLD identifier; that is, the information regarding AP 2z carries the identifier of MLD 3. The multiple BSSID element within the management frame carries the non-transmitted BSSID profile of AP 1y and the identifier of the MLD to which AP 1y belongs. A station receiving a management frame can determine the relationship between AP 1y and another AP based on the MLD identifier carried in the information about AP 2z in the RNR element and the MLD identifier of AP 1y carried in the multiple BSSID element: AP 1y and AP 1x belong to multiple BSSID set 1, and AP 1y and AP 2z belong to MLD 3.

[0229] Next, Figure 8a is used as an example to explain the signaling structure of a management frame. AP 1x within AP MLD 1 transmits a management frame, for example, a beacon frame, in a broadcast manner. As illustrated in Figure 13a, the management frame includes one RNR element. The RNR element carries simplified information regarding AP 2y, AP 3x, AP 2x, AP 3y, and AP 3z. The simplified information includes a one-to-one correspondence between the link identifier of the AP and parameters such as the AP's operation class, channel number, and BSSID. The management frame additionally carries three MLD elements. The first MLD element is a canonical MLD element, the common information field contains the address of AP MLD 1, and two sub-elements are carried, the first sub-element carries information regarding AP 2y, and the second sub-element carries information regarding AP 3x. The second MLD element is a virtual MLD element, the common information field contains the address of AP MLD 2, and two sub-elements are carried; the first sub-element carries information regarding AP 2x, and the second sub-element carries information regarding AP 3y. The third MLD element is a special MLD element, the common information field does not exist, and one sub-element is carried, which carries information regarding AP 3z. The link identifiers included in the information regarding AP 2y, AP 3x, AP 2x, and AP 3z carried in the three MLD elements are identical to the link identifiers of these APs in the RNR elements. Therefore, MLD elements do not repeatedly carry one or more of the parameters carried in the RNR, such as the operation class, channel number, and BSSID. This avoids signaling redundancy and reduces signaling overhead. Since the reported AP 1x belongs to a multi-BSID set, the management frame needs to additionally carry multiple BSSID elements.The element carries a non-transmitted BSSID profile, and the non-transmitted BSSID profile is information regarding AP 1y. Additionally, because AP 1y belongs to AP MLD 3, the non-transmitted BSSID profile additionally carries a canonical MLD element. The common information field contains the address of AP MLD 3 and carries one sub-element, and the sub-element carries information regarding AP 2z. The link identifier included in the information regarding AP 2z is identical to the link identifier of AP 2z in the RNR element. Optionally, simplified information regarding AP 1y may not appear in the RNR element. Parameters such as the operation class and channel number in the simplified information regarding AP 1y are identical to those of reported AP 1x. Information regarding the BSSID of AP 1y may be carried from the non-transmitted BSSID profile of AP 1y. In response, the station can learn information regarding AP 1x, AP 1y, AP 2y, AP 3x, AP 2x, AP 3y, and AP 3z, and can further determine the relationships between the APs based on RNR elements, three MLD elements, and multiple BSSID elements within the management frame. Specifically, the station can determine simplified information regarding the reported AP carried in the RNR and other information regarding the reported AP carried in the MLD elements based on the matching of link IDs carried in the RNR elements and MLD elements. As illustrated in FIG. 13a, the link ID of AP 2y carried in the information regarding AP 2y in the RNR is 2, and the link ID carried in the first sub-element of the first MLD element is also 2. The station can determine simplified information regarding AP 2y in the RNR based on the matching of link IDs and can determine other information regarding AP 2y based on the first sub-element of the first MLD element.Additionally, the station may further determine that AP 1x and AP 1y belong to multiple BSSID set 1, AP 1x, AP 2y, and AP 3x belong to MLD 1, AP 2x and AP 3y belong to MLD 2, AP 3z is a single-link device, AP 2y, AP 2x, and AP 2z belong to multiple BSSID set 2, and AP 3x, AP 3y, and AP 3z belong to multiple BSSID set 3.

[0230] Next, Fig. 8a is used as an example to explain a different signaling structure of a management frame. AP 1x within AP MLD 1 transmits a management frame, e.g., a beacon frame, in a broadcast manner. As illustrated in Fig. 13b, the management frame includes one RNR element. The RNR element carries simplified information regarding AP 2y, AP 3x, AP 2x, AP 3y, and AP 3z. The simplified information includes a one-to-one correspondence between the link identifier of the AP and parameters such as the AP's operation class, channel number, and BSSID. The information regarding each AP in the RNR element further includes an MLD identifier and / or a multiple BSSID set identifier. Optionally, the management frame further carries three MLD elements. The first MLD element is a canonical MLD element, the common information field contains the address of AP MLD 1, and two sub-elements are carried, the first sub-element carries information regarding AP 2y, and the second sub-element carries information regarding AP 3x. The second MLD element is a virtual MLD element, the common information field contains the address of AP MLD 2, and two sub-elements are carried; the first sub-element carries information regarding AP 2x, and the second sub-element carries information regarding AP 3y. The third MLD element is a special MLD element, the common information field does not exist, and one sub-element is carried; the sub-element carries information regarding AP 3z. The link identifiers included in the information regarding AP 2y, AP 3x, AP 2x, and AP 3z carried in the three MLD elements are identical to the link identifiers of these APs in the RNR element. Therefore, the MLD elements do not repeatedly carry one or more of the parameters carried in the RNR, such as the operation class, channel number, and BSSID. This avoids signaling redundancy and reduces signaling overhead.Because the reporting AP 1x belongs to a multi-BSSID set, the management frame needs to additionally carry a multi-BSSID element. The element carries a non-transmitted BSSID profile, which is information regarding AP 1y and includes the link identifier of AP 1y. Optionally, the MLD identifier of the MLD to which AP 1y belongs is additionally included. Optionally, simplified information regarding AP 1y may not appear in the RNR element. Parameters such as the operation class and channel number in the simplified information regarding AP 1y are identical to those of the reporting AP 1x. Information regarding the BSSID of AP 1y may be carried from the non-transmitted BSSID profile of AP 1y. Specifically, the parameter is calculated based on the reference BSSID (transmitted BSSID) and the multi-BSSID-index element within the non-transmitted BSSID profile. For the calculation method, refer to Draft P802.11REVmd_D3.0. Accordingly, based on the RNR element, three MLD elements, and multiple BSSID elements within the management frame, the station can learn information regarding AP 1x, AP 1y, AP 2y, AP 3x, AP 2x, AP 3y, and AP 3z, and can further determine the relationships between the APs. Specifically, based on the matching of link IDs carried in the RNR element and the MLD element, the station can determine simplified information regarding the reported AP carried in the RNR and other information regarding the reported AP carried in the MLD element. As illustrated in FIG. 13b, the link ID of AP 2y carried in the information regarding AP 2y in the RNR is 2, and the link ID carried in the first sub-element of the first MLD element is also 2. The station can determine simplified information regarding AP 2y in the RNR based on the matching of link IDs and can determine other information regarding AP 2y based on the first sub-element of the first MLD element.Additionally, the station may determine that AP 1x and AP 1y belong to multi-BSSID set 1. Based on MLD identifiers, the station may determine that AP 1x, AP 2y, and AP 3x belong to MLD 1, AP 2x and AP 3y belong to MLD 2, and AP 3z is a single-link device. Based on multi-BSSID set identifiers, it may be determined that AP 2y, AP 2x, and AP 2z belong to multi-BSSID set 2, and AP 3x, AP 3y, and AP 3z belong to multi-BSSID set 3.

[0231] The following describes the implementation of the RNR element.

[0232] Reduced Neighbor Report element: The AP carries a reduced neighbor report element within a management frame, for example, a beacon frame or a probe response frame. During scanning, the station receives the management frame transmitted by the AP, obtains information about nearby APs based on the reduced neighbor report element within the management frame, and then selects an appropriate AP for association.

[0233] Specifically, the Reduced Neighbor Report element generally carries one or more Neighbor AP Information fields to describe information regarding one or more Neighbor APs and BSSs to which the Neighbor APs belong. The Neighbor AP is also referred to as the Reported AP, and the AP transmitting the RNR element is referred to as the Reporting AP below. The Neighbor AP Information field carries simplified information regarding the Neighbor AP, that is, simplified information regarding the Reported AP. FIG. 14a illustrates a schematic diagram of the RNR element. From FIG. 14b, it can be seen that the Neighbor AP Information field of the simplified Neighbor Report element may include the following fields.

[0234] The TBTT information header (target beacon transmission time (TBTT) information header) field carries the following information:

[0235] A TBTT information field type field that indicates the type of TBTT information and the format of the TBTT information field together with a TBTT information length field;

[0236] A filtered neighbor AP field indicating whether all SSIDs of BSSs carried in the neighbor AP information fields match the SSID in the probe request frame;

[0237] Hold field (1 bit);

[0238] A TBTT information count field indicating the quantity of TBTT information fields included in the TBTT information set; and

[0239] The TBTT information length field, which indicates the length of each TBTT information field. Table 4 shows the formats of specific information carried with different lengths.

[0240] TBTT information length (bytes) Content carried in the TBTT information field 1 Neighbor AP's TBTT offset field 2 Neighbor AP's TBTT offset field and BSS parameter field 5 Neighbor AP's TBTT offset field and short SSID field 6 Neighbor AP's TBTT offset field, short SSID field, and BSS parameter field 7 Neighbor AP's TBTT offset field and BSSID field 8 Neighbor AP's TBTT offset field, BSSID field, and BSS parameter field 11 Neighbor AP's TBTT offset field, BSSID field, and short SSID field 12 Neighbor AP's TBTT offset field, BSSID field, short SSID field, and BSS parameter field 0, 9-10 hold 13-255 Although reserved, the information regarding the first 12 bytes is the same as the fields carried when the TBTT information length is 12.

[0241] When the TBTT information length is 12 bytes, the TBTT information field contains the following:

[0242] Neighbor AP TBTT offset (neighbor AP target beacon transmission time offset) field indicating the offset between the neighbor AP's beacon transmission time and the reporting AP's beacon transmission time;

[0243] BSSID (BSS identifier) ​​field indicating the BSS identifier corresponding to the neighboring AP;

[0244] A short SSID (short service set identifier) ​​field indicating the service set identifier to which the neighboring AP belongs; and

[0245] As illustrated in FIG. 14b, the BSS parameter field indicating the relevant parameters of neighboring APs includes the following information:

[0246] OCT recommendation (on-channel tunneling mechanism recommended) field indicating that a neighboring AP is expected to report a managed type MPDU and exchange it with the AP according to the OCT mechanism;

[0247] Same SSID (same service set identifier) ​​field indicating whether the neighbor AP and the reporting AP have the same SSID;

[0248] Multiple BSSID (multiple basic service set identifier) ​​fields indicating whether neighboring APs are part of multiple BSSID sets;

[0249] A transmitted BSSID (transmitted basic service set identifier) ​​field indicating whether the neighbor AP is a transmitted BSSID or a non-transmitted BSSID when the neighbor AP is part of a multi-BSSID set;

[0250] A field for a member of an ESS having a 2.4 / 5GHz co-located AP (member of an extended service set having a 2.4 / 5GHz co-located AP) indicating whether the neighbor AP is a member of an extended service set having a 2.4 / 5GHz co-located AP (i.e., whether the neighbor AP is a 6GHz-only AP); and

[0251] Unsolicited probe response active field indicating whether neighboring APs enable active probe responses.

[0252] Optionally, the TBTT information field additionally includes a co-located AP field indicating whether the neighboring AP and the reporting AP are co-located.

[0253] Optionally, the TBTT information field additionally includes a Co-MLD (Co-MLD) field indicating whether neighboring APs and reporting APs belong to the same MLD.

[0254] FIG. 14b is a schematic diagram of the format of the TBTT information field. FIG. 14c is another schematic diagram of the format of the TBTT information field.

[0255] In this embodiment, to prevent the reporting AP from broadcasting information regarding one or more or all APs within the multi-AP multi-link device where the reporting AP is located, an RNR element and a multi-BSSID element are used together, and optionally, an MLD element is also used. To avoid repeated parameters such as the AP's operation class, channel number, and BSSID in subsequent multi-link operations, the AP's link identifier is added to the RNR element and the multi-BSSID element. A correspondence exists between the AP's link identifier and parameters such as the AP's operation class, channel number, and BSSID. In subsequent transmission or communication, parameters such as the AP's operation class, channel number, and BSSID do not need to be carried. This reduces signaling overhead. Additionally, because the operation class and channel number of the non-transmitted BSSID in the multi-BSSID element are the same as the operation class and channel number of the transmitted BSSID in the multi-BSSID element, the two parameters do not appear in the non-transmitted BSSID profile of the multi-BSSID element. This further reduces signaling redundancy.

[0256] The apparatus provided in the embodiments of the present application will be described in detail below.

[0257] FIG. 15 illustrates a communication device (1500) according to an embodiment of the present application. The device may be an access point AP (e.g., a reporting AP within an AP multi-link device) or a station in the aforementioned embodiments, or a chip or processing system in an access point AP (e.g., a reporting AP within an AP multi-link device) or a station. The device may implement the method and function in any one of the embodiments of the present application. Due to differences in integration density, the communication device may include one or more of the components illustrated in FIG. 15. The components illustrated in FIG. 15 may include at least one processor (1501), memory (1502), transceiver (1503), and communication bus (1504).

[0258] Next, the components of the communication device (1500) will be described in detail with reference to FIG. 15.

[0259] The processor (1501) is the control center of the communication device (1500) and may be a single processor or a collective term for a plurality of processing elements. For example, the processor (1501) may be a central processing unit (CPU) or an Application Specific Integrated Circuit (ASIC), or may be configured as one or more integrated circuits for implementing embodiments of the present application, for example, one or more digital signal processors (DSPs) or one or more field programmable gate arrays (FPGAs). The processor (1501) can implement various functions of the communication device by driving or executing a software program stored in memory (1502) and calling data stored in memory (1502). In a particular implementation, in the embodiment, the processor (1501) may include one or more CPUs, for example, CPU 0 and CPU 1 as shown in FIG. 15.

[0260] During a specific implementation, in an embodiment, the communication device (1500) may include a plurality of processors, for example, the processor (1501) and the processor (1505) shown in FIG. 15. Each of these processors may be a single-core processor (single-CPU) or a multi-core processor (multi-CPU). A processor in this specification may be one or more communication devices, circuits, or processing cores configured to process data (e.g., computer program instructions).

[0261] The memory (1502) may be a read-only memory (ROM), or another type of static storage communication device capable of storing static information and instructions, or a random access memory (RAM) or another type of dynamic storage communication device capable of storing information and instructions, or an electrically eraseable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other compact disc storage, an optical disc storage (including compact discs, laser discs, optical discs, digital multifunction discs, Blu-ray discs, etc.), a magnetic disc storage medium or other magnetic storage communication device, or any other medium that can be configured to carry or store program code expected in the form of instructions or data structures and can be accessed by a computer. However, the memory (1502) is not limited thereto. The memory (1502) may exist independently or may be connected to the processor (1501) via a communication bus (1504). Alternatively, the memory (1502) may be integrated with the processor (1501). The memory (1502) is configured to store a software program for executing the solution of the present application, and the processor (1501) controls the execution.

[0262] The transceiver (1503) is configured to communicate with another device (e.g., a station in the embodiment illustrated in FIG. 1). Of course, the transceiver (1503) may be additionally configured to communicate with a communication network, e.g., Ethernet, a radio access network (RAN), or a wireless local area network (WLAN). The transceiver (1503) may include a receiving unit that implements a receiving function and a transmitting unit that implements a transmitting function.

[0263] The communication bus (1504) may be an Industry Standard Architecture (ISA) bus, a Peripheral Component (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, etc. The bus may be classified into an address bus, a data bus, a control bus, etc. For ease of representation, only a single bold line is used to represent the bus in FIG. 15, but this does not mean that there is only one bus or only one type of bus.

[0264] For example, the communication device (1500) is a complete device. The communication device may include a processor (1501), memory (1502), a transceiver (1503), and a communication bus (1504). Optionally, the communication device may additionally include other components, for example, a display.

[0265] Optionally, the communication device (1500) is an access point AP (e.g., a reporting AP within an AP multi-link device) and may be configured to implement the methods and functions related to the AP in the embodiments described above. For example, memory stores a computer program (instructions). When the processor calls the computer program, the methods and functions described above are implemented. For example, the processor is configured to generate a signaling or frame (carrying MLD information), and the transceiver is configured to transmit the signaling or frame (carrying MLD information). For example, the processor is configured to control the transceiver to perform step S101. Of course, the process of generating MLD information in step S101 may also be completed by the processor. As another example, the processor is configured to control the transceiver to perform step S201. Of course, the process of generating a management frame in step S201 may also be completed by the processor. As yet another example, the processor is configured to control the transceiver to perform step S301. Of course, the process of generating a management frame in step S301 can also be completed by a processor. As another example, the processor is configured to control the transceiver to perform step S401. Of course, the process of generating a management frame in step S401 can also be completed by a processor.

[0266] Optionally, the communication device (1500) is a station and may be configured to implement the methods and functions of the station in the embodiments described above. For example, memory stores a computer program. When the processor calls the computer program, the methods and functions described above are implemented. For example, the processor is configured to generate a signaling or frame (e.g., a probe response frame), and the transceiver is configured to transmit the signaling or frame (e.g., receive a probe request frame). In one example, the processor is configured to control the transceiver to receive MLD information in step S102, and then the processor determines the structure of the multi-AP multi-link device and information regarding each AP based on the MLD information, and may further determine the APs for association. In another example, the processor is configured to control the transceiver to receive a management frame in step S202, and then the processor determines the structure of the multi-AP multi-link device and information regarding each AP based on the management frame, and may further determine the APs for association. In another example, the processor is configured to control the transceiver to receive a management frame in step S302, and then the processor determines the structure of the multi-AP multi-link device and information regarding each AP based on the management frame, and can further determine the APs for association. In another example, the processor is configured to control the transceiver to receive a management frame in step S402, and then the processor determines the structure of the multi-AP multi-link device and information regarding each AP based on the management frame, and can further determine the APs for association.

[0267] As another example, the communication device (1500) is a chip system or processing system within an access point AP (e.g., a reporting AP within an AP multi-link device), and thus the device on which the chip system or processing system is installed implements the methods and functions related to the AP in the embodiments described above. In this case, the communication device (1500) may include some components illustrated in FIG. 15. For example, the communication device (1500) includes a processor. The processor may be coupled to memory, call instructions within memory, and execute instructions so that the device configured or installed with the chip system or processing system can implement the methods and functions in the embodiments described above. Optionally, the memory may be a component within the chip system or processing system, or a coupled / connected component outside the chip system or processing system. In the example, the chip system or processing system is installed in an access point AP (e.g., a reporting AP within an AP multi-link device), so that the access point AP can perform step S101 in the embodiments described above. In another example, the chip system or processing system is installed in the access point AP, so that the access point AP can perform step S201 of the above-described embodiment. In yet another example, the chip system or processing system is installed in the access point AP, so that the access point AP can perform step S301 of the above-described embodiment, and, for example, the access point displays step S401.

[0268] As another example, the communication device (1500) is a chip system or processing system within a station, and thus the device on which the chip system or processing system is installed implements the methods and functions related to the station in the aforementioned embodiments. In this case, the communication device (1500) may include some components illustrated in FIG. 15. For example, the communication device (1500) includes a processor. The processor may be coupled to memory, call instructions within memory, and execute instructions so that the device configured or installed as the chip system or processing system can implement the methods and functions in the aforementioned embodiments. Optionally, the memory may be a component within the chip system or processing system, or a coupled / connected component outside the chip system or processing system. In an example, the chip system or processing system is installed in a station, so the station can perform step S102 in the aforementioned embodiment. In another example, the chip system or processing system is installed in a station, so the station can perform step S202 in the aforementioned embodiment. In another example, the chip system or processing system is installed at a station, and the station can perform step S302 of the above-described embodiment. In another example, the chip system or processing system is installed at a station, and the station can perform step S402 of the above-described embodiment.

[0269] The chip system or processing system may support communication according to 802.11 series protocols, e.g., 802.11be, 802.11ax, and 802.11ac. The chip system may be installed in devices in various scenarios that support WLAN transmission. Devices in WLAN transmission scenarios are described at the beginning of this specification, and details are not described in this specification.

[0270] In the embodiments of the present application, an access point AP (e.g., a reporting AP within an AP multi-link device) or a station may be divided into functional modules based on the aforementioned method examples. For example, functional modules may be obtained through division based on corresponding functions, or two or more functions may be integrated into a single processing module. The integrated module may be implemented in the form of hardware or in the form of a software functional module. It should be noted that in the embodiments of the present application, module division is an example and is merely a logical functional division. In actual implementation, other division methods may be used.

[0271] When an integrated unit is used, FIG. 16 is a possible schematic diagram of the structure of a communication device (1600). The communication device (1600) may be a multi-link device, or a chip or processing system within a multi-link device. The communication device (1600) may perform the operations of a multi-link device in the aforementioned method embodiments. The communication device (1600) includes a processing unit (1601) and a transceiver unit (1602).

[0272] For example, the communication device (1600) is the aforementioned access point AP (e.g., a reporting AP within an AP multi-link device) or station.

[0273] For example, the communication device (1600) is an access point or a chip within the access point.

[0274] The processing unit (1601) may be configured to control and manage the actions of the communication device (1600), for example, to generate MLD information, or, as another example, to control the operations of the transceiver unit (1602). Optionally, if the communication device (1600) includes a storage unit, the processing unit (1601) may additionally execute programs or instructions stored in the storage unit, so that the communication device (1600) implements the methods and functions of any one of the aforementioned embodiments.

[0275] For example, the processing unit (1601) can and / or is used to control the transceiver unit to perform step S101 of FIG. 4, S201 of FIG. 10a, S301 of FIG. 10b, or S401 of FIG. 11. All relevant details of the steps in the aforementioned method embodiments may be cited in the functional descriptions of the corresponding functional modules. Details are not described again herein.

[0276] For example, the processing unit (1601) can control the transceiver unit to perform, for example, step S102 of FIG. 4, S202 of FIG. 10a, S302 of FIG. 10b, or S402 of FIG. 11, and / or is used in other processes of the technology described herein. All relevant details of the steps in the above-described method embodiments may be cited in the functional descriptions of the corresponding functional modules. Details are not described again herein.

[0277] For example, the transceiver unit (1602) may transmit and receive data or signaling transmitted over a single link, or transmit and receive data or signaling transmitted over multiple links. Optionally, the transceiver unit (1602) may be a single transceiver module or may include multiple transceiver modules. When the transceiver unit (1602) is a single transceiver module, the transceiver module may transmit and receive data over multiple links. For example, when the first multi-link device operates over two links, and the transceiver unit (1602) includes two transceiver modules, one transceiver module operates over one link and the other transceiver module operates over the other link. For example, the transceiver unit (1602) may be configured to perform, for example, step S101 of FIG. 4, step S201 of FIG. 10a, step S301 of FIG. 10b, or step S401 of FIG. 11, and / or is used in other processes of the technology described herein. All relevant details of the steps in the aforementioned method embodiments may be cited in the functional descriptions of the corresponding functional modules. Details are not described again herein.

[0278] For example, the communication device (1600) may be the communication device illustrated in FIG. 15, the processing unit (1601) may be the processor (1501) of FIG. 15, and the transceiver unit (1602) may be the transceiver (1503) of FIG. 15. Optionally, the communication device (1600) may additionally include memory. The memory is configured to store corresponding program code and data for the communication device (1600) to perform any communication method between the multi-link devices provided above. Descriptions of all relevant contents of the components of FIG. 15 may be cited in the functional descriptions of the corresponding components of the communication device (1600), and details are not described again here.

[0279] For example, the communication device (1600) may alternatively be a chip or a processor, the processing unit (1603) may be a processing circuit within the chip or processor, the transceiver unit (1602) may be an input / output circuit within the chip or processor, and the input / output circuit is an interface for mutual communication or data exchange between the chip or processor and other combined components. It may be ensured that signaling or data information or program instructions are input to the chip or processor for processing, that the processed data or signaling is output to other combined components, and that the first multi-link device on which the chip or processor is installed is controlled to implement the functions.

[0280] As another example, the communication device (1600) is a chip in the station or in the station.

[0281] The processing unit (1601) may be configured to control and manage the actions of the communication device (1600), for example, to process MLD information, or, as another example, to control the operations of the transceiver unit (1602). Optionally, if the communication device (1600) includes a storage unit, the processing unit (1601) may additionally execute programs or instructions stored in the storage unit, so that the communication device (1600) implements the methods and functions of any one of the aforementioned embodiments.

[0282] For example, the processing unit (1601) may be configured to process MLD information. For example, the MLD information in step S102 of FIG. 4 may be processed by the processing unit (1601), or the management frame in S202 of FIG. 10a, the management frame in S302 of FIG. 10b, or the management frame in S402 of FIG. 11 may be processed by the processing unit (1601) and / or the processing unit (1601) may be used in other processes of the technology described herein. All relevant details of the steps in the aforementioned method embodiments may be cited in the functional descriptions of the corresponding functional modules. Details are not described again herein.

[0283] For example, the transceiver unit (1602) may transmit and receive data or signaling transmitted over a single link, or transmit and receive data or signaling transmitted over multiple links. Optionally, the transceiver unit (1602) may be a single transceiver module or may include multiple transceiver modules. When the transceiver unit (1602) is a single transceiver module, the transceiver module may transmit and receive data over multiple links. For example, when the first station operates over two links, and the transceiver unit (1602) includes two transceiver modules, one transceiver module operates over one link and the other transceiver module operates over the other link. For example, the transceiver unit (1602) may be configured to perform, for example, step S102 of FIG. 4, or S202 of FIG. 10a, or S302 of FIG. 10b, or S402 of FIG. 11, or is used in other processes of the technology described herein. All relevant details of the steps in the aforementioned method embodiments may be cited in the functional descriptions of the corresponding functional modules. Details are not described again herein.

[0284] For example, the communication device (1600) may be the communication device illustrated in FIG. 15, the processing unit (1601) may be the processor (1501) of FIG. 15, and the transceiver unit (1602) may be the transceiver (1503) of FIG. 15. Optionally, the communication device (1600) may additionally include memory. The memory is configured to store corresponding program code and data for the communication device (1600) to perform any method provided above. Descriptions of all relevant contents of the components of FIG. 15 may be cited in the functional descriptions of the corresponding components of the communication device (1600), and details are not described again here.

[0285] For example, the communication device (1600) may alternatively be a chip or a processor, the processing unit (1603) may be a processing circuit within the chip or processor, the transceiver unit (1602) may be an input / output circuit within the chip or processor, and the input / output circuit is an interface for mutual communication or data exchange between the chip or processor and other combined components. It may be ensured that signaling or data information or program instructions are input to the chip or processor for processing, that the processed data or signaling is output to other combined components, and that the device on which the chip or processor is installed is controlled to implement the functions.

[0286] In the section on device embodiments, it should be noted that regarding the signaling structure of MLD information and the structure of the management frame, reference is made to the descriptions in the aforementioned embodiments.

[0287] Embodiments of the present application further provide a computer-readable storage medium. The computer-readable storage medium stores computer program code. When the aforementioned processor executes the computer program code, the electronic device (e.g., AP or station) on which the processor is located becomes capable of performing the method in any one of the embodiments.

[0288] Embodiments of the present application further provide a computer program product. When the computer program product is executed on a computer, the computer (e.g., AP or station) is able to perform the method in any one of the embodiments.

[0289] Embodiments of the present application further provide a communication device. 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 configured to communicate with another device through a receiving circuit so as to enable the device to perform the method in any one of the embodiments.

[0290] Embodiments of the present application further provide a communication system. The communication system includes the access point AP (e.g., a reporting AP within an AP multi-link device) and a station. The access point AP (e.g., a reporting AP within an AP multi-link device) and the station may perform the method in any one of the embodiments described above (e.g., the method in FIG. 4, FIG. 10a, FIG. 10b, or FIG. 11). The method or algorithm steps described in combination with the contents disclosed in the present application may be implemented by hardware or by a processor by executing software instructions. Software instructions may include corresponding software modules. Software modules may 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, mobile hard disks, Compact Disc Read-Only Memory (CD-ROM), or any other form of storage medium well known in the art. For example, a storage medium may be coupled to a processor, allowing the processor to read information from or write information to the storage medium. Of course, the storage medium may alternatively be a component of the processor. The processor and the storage medium may be placed within an ASIC. Additionally, the ASIC may be located within a core network interface device. Of course, the processor and the storage medium may exist within the core network interface device as individual components.

[0291] A person skilled in the art should recognize that in one or more of the examples described above, the functions described in this application may be implemented by hardware, software, firmware, or any combination thereof. When the functions are implemented by software, the functions described above may be stored on a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. A computer-readable medium includes a computer-readable storage medium and a communication medium, wherein the communication medium includes any medium that facilitates the transmission of a computer program from one place to another. The storage medium may be any available medium accessible by a general-purpose or special-purpose computer.

[0292] In the specific embodiments described above, the objectives, technical solutions, and beneficial effects of the present application have been described in more detail. It should be understood that the foregoing descriptions are merely specific embodiments of the present application and are not intended to limit the scope of protection of the present application. Any modification, equivalent substitution, improvement, etc., made based on the technical solutions of the present application will be within the scope of protection of the present application.

Claims

Claim 1 A communication device in a wireless local area network (WLAN), comprising: a processing unit configured to generate a management frame—the AP belongs to a first AP multi-link device (MLD), said management frame includes MLD information, said MLD information includes a first MLD element representing said first AP MLD and a second MLD element representing a different AP MLD different from said first AP MLD—; and a transceiver unit configured to transmit said management frame. Claim 2 A communication device in a wireless local area network (WLAN), comprising: a transceiver unit configured to receive a management frame from an access point (AP)—wherein the AP belongs to a first AP multi-link device (MLD), and the management frame includes MLD information, wherein the MLD information includes a first MLD element representing the first AP MLD and a second MLD element representing a different AP MLD distinct from the first AP MLD—; and a processing unit configured to obtain information regarding the other AP within the first MLD based on the management frame. Claim 3 A communication device according to claim 1 or 2, wherein the first MLD element includes a common control field, and the common control field includes type information indicating the element type of the first MLD element. Claim 4 In paragraph 3, the element type includes a formal MLD element and a virtual MLD element, and the type information includes: a communication device including a virtual MLD field indicating whether the MLD element is a virtual MLD element. Claim 5 A communication device according to claim 4, wherein the virtual MLD field comprises 1 bit; and if the MLD element is the virtual MLD element, the virtual MLD field is set to a first value, or if the MLD element is a formal MLD element, the virtual MLD field is set to a second value. Claim 6 In paragraph 3, the first MLD element is a formal MLD element, and the type information within the first MLD element is a communication device indicating that the first MLD element is the formal MLD element. Claim 7 A communication device according to claim 1 or 2, wherein, if the field or element relating to the other AP is identical to the field or element relating to the AP, the identical field or element relating to the other AP is not carried in the sub-element of the first MLD element. Claim 8 In claim 1 or 2, if the field or element regarding the other AP is different from the field or element regarding the AP, the same field or element regarding the other AP is a communication device carried in the sub-element of the first MLD element. Claim 9 A communication device according to claim 1 or 2, wherein the management frame further comprises a reduced neighbor reporting (RNR) element. Claim 10 In paragraph 9, in the RNR element, the MLD identifiers of the plurality of reported APs are the same communication device when the plurality of reported APs come from the same MLD. Claim 11 In claim 1 or 2, where the other AP in the first MLD belongs to a second set of multiple basic service set identifiers (BSSID) and the other AP in the second set of multiple BSSIDs belongs to a second MLD, the sub-element of the second MLD element is a communication device that carries information about the AP in the second MLD. Claim 12 A communication device according to claim 1 or 2, wherein if the AP belongs to a first multiple BSSID set, the MLD information further includes a first multiple BSSID element, and the first multiple BSSID element includes information regarding a non-transmitting AP within the first multiple BSSID set. Claim 13 In paragraph 12, if the non-transmitting AP within the first multi-BSSID set belongs to the third MLD, the first multi-BSSID element further comprises the third MLD element, and the sub-element of the third MLD element carries information regarding other APs within the third MLD. Claim 14 In paragraph 1 or 2, the management frame is a beacon frame, an association response frame, a probe response frame, an authentication frame, or a neighbor report communication device. Claim 15 A method for exchanging signaling information in a wireless local area network (WLAN), comprising the steps of: generating a management frame by an access point (AP)—wherein the AP belongs to a first AP multi-link device (MLD) and the management frame includes MLD information, wherein the MLD information includes a first MLD element representing the first AP MLD and a second MLD element representing a different AP MLD different from the first AP MLD—; and transmitting the management frame by the access point. Claim 16 A method for exchanging signaling information in a wireless local area network (WLAN), comprising the steps of: receiving a management frame from an access point (AP) by a station, wherein the AP belongs to a first AP multi-link device MLD, and the management frame includes MLD information, wherein the MLD information includes a first MLD element representing the first AP MLD and a second MLD element representing a different AP MLD distinct from the first AP MLD; and obtaining information regarding another AP within the first MLD by the station based on the management frame. Claim 17 A method according to claim 15 or 16, wherein the first MLD element includes a common control field, and the common control field includes type information indicating the element type of the first MLD element. Claim 18 In paragraph 17, the first MLD element is a formal MLD element, and the type information within the first MLD element is a method of indicating that the first MLD element is the formal MLD element. Claim 19 In paragraph 17, the element type includes a formal MLD element and a virtual MLD element, and the type information includes: a virtual MLD field indicating whether the MLD element is a virtual MLD element. Claim 20 A method according to claim 19, wherein the virtual MLD field comprises 1 bit; and if the MLD element is the virtual MLD element, the virtual MLD field is set to a first value, or if the MLD element is a formal MLD element, the virtual MLD field is set to a second value. Claim 21 A method according to claim 15 or 16 in which, if the field or element regarding the other AP is identical to the field or element regarding the AP, the same field or element regarding the other AP is not carried in the sub-element of the first MLD element. Claim 22 In paragraph 15 or 16, a method in which, if the field or element regarding the other AP is different from the field or element regarding the AP, the same field or element regarding the other AP is carried in the sub-element of the first MLD element. Claim 23 A method according to paragraph 15 or 16, wherein the management frame further includes a reduced neighbor reporting (RNR) element. Claim 24 In paragraph 23, in the above RNR element, the MLD identifiers of the plurality of reported APs are in the same way when the plurality of reported APs come from the same MLD. Claim 25 In paragraph 15 or 16, where the other AP in the first MLD belongs to a second set of multiple basic service set identifiers (BSSIDs) and the other AP in the second set of multiple BSSIDs belongs to the second MLD, the sub-elements of the second MLD elements carry information regarding the AP in the second MLD. Claim 26 A method according to claim 15 or 16, wherein if the AP belongs to a first multiple BSSID set, the MLD information further comprises a first multiple BSSID element, and the first multiple BSSID element comprises information regarding a non-transmitting AP within the first multiple BSSID set. Claim 27 In paragraph 26, where the non-transmitting AP in the first multi-BSSID set belongs to the third MLD, the first multi-BSSID element further comprises the third MLD element, and the sub-element of the third MLD element carries information regarding other APs in the third MLD. Claim 28 In paragraph 15 or 16, the management frame is a beacon frame, an association response frame, a probe response frame, an authentication frame, or a neighbor report method. Claim 29 An access point (AP) comprising a processor and memory, wherein the memory is configured to store instructions, and when the instructions are executed by the processor, the AP is capable of performing the method according to claim 15. Claim 30 A station comprising a processor and memory, wherein the memory is configured to store instructions, and when the instructions are executed by the processor, the station is capable of performing the method according to claim 16. Claim 31 A chip comprising an input / output interface circuit and a processing circuit, wherein the input / output interface circuit is configured to input / output data or signaling information, and the processing circuit is configured to process the data or signaling information provided by the input / output interface circuit so as to enable a device comprising the chip to perform the method according to claim 15 or 16. Claim 32 A computer-readable storage medium, wherein the computer-readable storage medium stores computer program code or instructions, and when the computer program or the instructions are executed on a processor, a device including the processor is able to perform the method according to claim 15 or 16. Claim 33 A computer program stored on a computer-readable storage medium, wherein when the computer program is executed on a processor, a device including the processor is able to perform the method according to claim 15 or 16. Claim 34 A communication system, wherein the communication system comprises an access point according to claim 29 and a station according to claim 30. Claim 35 delete Claim 36 delete Claim 37 delete Claim 38 delete Claim 39 delete Claim 40 delete Claim 41 delete Claim 42 delete Claim 43 delete

Images