Multi-link operation (MLO) for simple networking

Abstract

A first multi-AP device configured as a multi-AP proxy transmits a device pre-configuration protocol (DPP) configuration request message indicating a multi-link operation (MLO) capability of the first multi-AP device over a first communication link to a second multi-AP device configured as a multi-AP controller. A first multi-AP device receives a DPP configuration response message from a second multi-AP device through a first communication link, the DPP configuration response message indicating MLO association information in response to the indicated MLO capability, and establishing a backhaul path with a third multi-AP device configured as a second multi-AP proxy on the first communication link and the one or more second communication links according to the MLO association information. The MLO capability may be indicated in a DPP configuration object of the DPP configuration request message, and the MLO association information may be indicated in a multilink device (MLD) address field of the DPP configuration object of the DPP configuration response message.

Description

Cross-references

[0001] This patent application claims priority to U.S. patent application No. 17 / 946,855, filed by HUANG et al. on September 16, 2022, and entitled “MULTI-LINK OPERATION (MLO) FOR EASY MESH,” which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0002] The present disclosure generally relates to wireless communications including implementing multi-link operations (MLO) over a multiple access point (AP) network. Background Art

[0003] Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, etc. A wireless local area network (WLAN) may be formed by one or more access points (APs) that provide a shared wireless communication medium for use by client devices such as stations (STAs). The basic building block of a WLAN that complies with the Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards is the Basic Service Set (BSS), which is managed by an AP. Each BSS is identified by a Basic Service Set Identifier (BSSID), which is advertised by the AP.

[0004] Mesh networks may be used in a variety of environments including home entertainment systems, home automation, factory automation, etc. In a mesh network, wireless devices operating as mesh nodes may be connected to each other in a non-hierarchical network topology via mesh links, and may cooperate with each other to propagate data and other information from a source to a destination through one or more mesh links established during a path discovery process.

[0005] The mesh network including multiple AP devices can be called a multi-AP network. Each multi-AP device constituting a multi-AP network may include a multi-AP controller, a multi-AP agent, or both. The multi-AP controller implements logic for controlling the fronthaul AP and backhaul links associated with the multi-AP network. The multi-AP controller also implements functions for loading (onboard) and pre-configuring (provision) multiple AP devices to multiple AP networks. The multi-AP agent implements the following logic: executes commands received from the multi-AP controller, reports measurement results and device capabilities to the multi-AP controller, and connects to the Wi-Fi subsystem of the fronthaul AP and backhaul STA associated with the multi-AP device. Summary of the invention

[0006] The systems, methods and devices of the disclosure each have several innovative aspects, no single one of which is solely responsible for the desirable attributes disclosed herein.

[0007] An innovative aspect of the subject matter described in the present disclosure may be implemented in a first multi-access point (Multi-AP) device. The first multi-AP device may include a processing system and one or more interfaces coupled to the processing system. The one or more interfaces may be configured to output a device pre-configuration protocol (DPP) configuration request message to a second multi-AP device via a first communication link, and the DPP configuration request message indicates the multi-link operation (MLO) capability of the first multi-AP device. The one or more interfaces may be configured to obtain a DPP configuration response message from the second multi-AP device via the first communication link, and the DPP configuration response message indicates the MLO association information in response to the indicated MLO capability. The processing system may be configured to establish a return path with a third multi-AP device on the first communication link and one or more second communication links according to the MLO association information. In some instances, the MLO capability of the first multi-AP device may be indicated in the DPP configuration object of the DPP configuration request message. In some other instances, the MLO association information may be indicated in the multi-link device (MLD) address field of the DPP configuration object of the DPP configuration response message.

[0008] In some aspects, the first multi-AP device may be a first multi-AP agent, the first multi-AP agent includes a backhaul station (STA) MLD configured to communicate with the third multi-AP device via the first communication link or the second communication link. The second multi-AP device may be a multi-AP controller, and the multi-AP controller is configured to load the first multi-AP device and the third multi-AP device according to the multi-AP communication protocol. The third multi-AP device may be a second multi-AP agent, and the second multi-AP agent includes a fronthaul AP MLD configured to communicate with the first multi-AP agent via the first communication link or the second communication link.

[0009] In some aspects, the one or more interfaces may also be configured to output a basic service set (BSS) configuration request message to the second multi-AP device via the first communication link, the BSS configuration request message indicates the MLO capability of the BSS associated with the first multi-AP device. The one or more interfaces may also be configured to obtain a BSS configuration response message from the second multi-AP device via the first communication link, and the BSS configuration response message indicates one or more BSSs associated with a public MLD identifier (ID). In some instances, the MLO capability of the BSS associated with the first multi-AP device may be indicated in the DPP configuration object of the BSS configuration request message. In some other instances, one or more BSSs associated with the public MLD ID may be indicated in the MLD address field of the DPP configuration object of the BSS configuration response message.

[0010] In some aspects, the one or more interfaces may also be configured to obtain AP capability query messages from the multi-AP controller, and the AP capability report message is output to the multi-AP controller, the AP capability report message includes a second AP MLD for indicating the fronthaul AP MLO capability of the multi-AP proxy MLO support type - length - value (TLV). In some other implementations, the one or more interfaces may also be configured to obtain AP capability query messages from the multi-AP controller, and the backhaul STA capability report message is output to the multi-AP controller, the backhaul STA capability report message includes an indication of the first multi-AP proxy backhaul STA MLD MLO capability MLO support TLV.

[0011] In some aspects, the one or more interfaces may also be configured to obtain AP metrics from the multi-AP controller query message, and output AP metric response message to the multi-AP controller, the AP metric response message includes non-AP operation TLV associated with each STA for the first multi-AP proxy backhaul STA MLD. In some aspects, the non-AP operation TLV associated with the backhaul STA MLD of each STA may indicate the MLO configuration between the respective STA and the respective AP of the first multi-AP proxy fronthaul AP MLD. In some other aspects, the non-AP operation TLV associated with the backhaul STA MLD may indicate the backhaul STA MLD of the first multi-AP proxy and the first multi-AP proxy fronthaul AP MLD associated with the first multi-AP traffic identifier (TID) to link mapping.

[0012] Another innovative aspect of the subject matter described in the present disclosure may be implemented as a method for wireless communication by a first multi-AP device. In some implementations, the method includes sending a DPP configuration request message to a second multi-AP device via a first communication link, and the DPP configuration request message indicates the MLO capability of the first multi-AP device. The method includes receiving a DPP configuration response message from the second multi-AP device via the first communication link, and the DPP configuration response message indicates the MLO association information in response to the indicated MLO capability. The method includes establishing a return path with a third multi-AP device on the first communication link, and establishing one or more second communication links according to the MLO association information. In some instances, the MLO capability of the first multi-AP device may be indicated in the DPP configuration object of the DPP configuration request message. In some other cases, the MLO association information may be indicated in the MLD address field of the DPP configuration object of the DPP configuration response message of the DPP configuration response message.

[0013] In some aspects, the first multi-AP device may be a first multi-AP agent, the first multi-AP agent includes a backhaul STA MLD configured to communicate with the third multi-AP device via the first communication link or the second communication link. The second multi-AP device may be a multi-AP controller, and the multi-AP controller is configured to load the first multi-AP device and the third multi-AP device according to the multi-AP communication protocol. The third multi-AP device may be a second multi-AP agent, and the second multi-AP agent includes a fronthaul AP MLD configured to communicate with the first multi-AP agent via the first communication link or the second communication link.

[0014] In some aspects, the method may also include sending a BSS configuration request message to the second multi-AP device via the first communication link, the BSS configuration request message indicates the MLO capability of the BSS associated with the first multi-AP device. The method may also include receiving a BSS configuration response message from the second multi-AP device via the first communication link, and the BSS configuration response message indicates one or more BSSs associated with a public MLD ID. In some instances, the MLO capability of the BSS associated with the first multi-AP device may be indicated in the DPP configuration object of the BSS configuration request message. In some other instances, one or more BSSs associated with the public MLD ID may be indicated in the MLD address field of the DPP configuration object of the BSS configuration response message.

[0015] In some aspects, the method may further include receiving an AP capability query message from the multi-AP controller, and sending an AP capability report message to the multi-AP controller, the AP capability report message includes an MLO capability MLO support TLV for indicating the second multi-AP agent fronthaul AP MLD. In some other implementations, the method may also include receiving an AP capability query message from the multi-AP controller, and sending a backhaul STA capability report message to the multi-AP controller, the backhaul STA capability report message includes an MLO capability MLO support TLV for indicating the first multi-AP agent backhaul STA MLD.

[0016] In some aspects, the method may also include receiving an AP metric query message from the multi-AP controller, and sending an AP metric response message to the multi-AP controller, the AP metric response message includes an associated non-AP operation TLV for each STA of the first multi-AP proxy backhaul STA MLD. In some aspects, the non-AP operation TLV associated with the backhaul STAMLD of each STA may indicate the MLO configuration between the respective STA and the respective AP of the first multi-AP proxy fronthaul AP MLD. In some other aspects, the non-AP operation TLV associated with the backhaul STA MLD may indicate the TID associated with the first multi-AP proxy backhaul STA MLD and the first multi-AP proxy fronthaul APMLD associated with the link mapping.

[0017] Details of one or more implementations of the subject matter described in this disclosure are set forth in the accompanying drawings and the following description. Other features, aspects, and advantages will become apparent from the specification, drawings, and claims. Note that the relative dimensions in the drawings may not be drawn to scale. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 An example multi-AP network is shown.

[0019] Figure 2 A block diagram of an example wireless communication device is shown.

[0020] Figure 3A A block diagram of an example multi-AP controller is shown.

[0021] Figure 3B A block diagram showing an example multi-AP proxy.

[0022] Figure 4A A block diagram of an example access point (AP) is shown.

[0023] Figure 4B A block diagram of an example station (STA) is shown.

[0024] Figure 5 An example communication system including an AP multi-link device (MLD) and a non-AP MLD is shown.

[0025] Figure 6 An example multi-AP network supporting multi-link operation (MLO) is shown.

[0026] Figure 7 An example sequence diagram is shown for wireless communications supporting MLO in a multi-AP network.

[0027] Figure 8 Another example sequence diagram is shown for wireless communications supporting MLO in a multi-AP network.

[0028] Fig. 9 – Fig.15 A flow diagram illustrating example operations for wireless communications supporting MLO in a multi-AP network.

[0029] Fig.16 A block diagram of an example wireless communication device is shown.

[0030] Fig.17 A block diagram of another example wireless communication device is shown.

[0031] Fig.18A An example MLD Configuration Report Type-Length-Value (TLV) suitable for use in a Basic Service Set (BSS) Configuration Result message is shown.

[0032] Fig.18B An example MLO support TLV suitable for use in an AP capability report message, a backhaul STA capability report message, or a client capability report message is shown.

[0033] Fig.18C An example associated non-AP MLD Operation TLV suitable for use in an AP Metrics Response message or an associated STA Link Metrics Response message is shown.

[0034] Fig.18D An example backhaul multilink steering request TLV suitable for use in a backhaul steering request message is shown.

[0035] Fig.18E Shown suitable for use in a multi-AP policy configuration request message example AP MLD flow identifier (TID) to link mapping request TLV.

[0036] The same reference numbers and designations in different drawings represent the same elements. DETAILED DESCRIPTION

[0037] For the purpose of describing the innovative aspects of the present disclosure, the following description is directed to some specific implementations. However, one of ordinary skill in the art will readily recognize that the teachings herein can be applied in a variety of different ways. The described implementations can be implemented in any device, system, or network capable of sending and receiving radio frequency (RF) signals according to one or more of the following: Long Term Evolution (LTE), 3G, 4G, or 5G (New Radio (NR)) standards issued by the Third Generation Partnership Project (3GPP), the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, the IEEE 802.15 standard, or as defined by the Bluetooth Special Interest Group (SIG). Standards, etc. The described implementations may be implemented in any device, system, or network capable of sending and receiving RF signals according to one or more of the following technologies or techniques: code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single carrier FDMA (SC-FDMA), single user (SU) multiple input multiple output (MIMO), and multi-user (MU)-MIMO. The described implementations may also be implemented using other wireless communication protocols or RF signals suitable for use in one or more of a wireless wide area network (WWAN), a wireless local area network (WPAN), a wireless personal area network (WLAN), or an Internet of Things (IOT) network.

[0038] Various implementations generally relate to implementing multi-link operation (MLO) in a multi-AP network, and specifically, to implementing multi-link operation (MLO) in a multi-AP network configured according to Wi-Fi EasyMesh (Simple Mesh) provided by the Wi-Fi Alliance (WFA). TM Standard to operate multiple AP devices to establish multiple communication links between. In various implementations, each multi-AP device may include a fronthaul AP MLD and a backhaul STA MLD. The fronthaul AP MLD of each multi-AP device may include multiple APs that establish a corresponding BSS on multiple communication links of a multi-AP network. Client devices, downstream multi-AP devices or other devices associated with the fronthaul AP MLD may communicate with their respective multi-AP devices via multiple communication links of a multi-AP network. The backhaul STA MLD of each multi-AP device may include multiple STAs that may be associated with the corresponding BSS established by the upstream multi-AP device on multiple communication links.

[0039] In some implementations, a multi-AP device in a multi-AP device can be configured to operate as a multi-AP controller, and other multi-AP devices can be configured to operate as multi-AP proxy. Multi-AP controller can be loaded according to the device pre-configuration protocol (DPP) or multi-AP communication protocol multi-AP agent, to join the multi-AP agent multi-AP network.

[0040] Aspects of the present disclosure recognize that the use of AP MLD and STA MLD in multiple AP devices to implement multi-link operation (MLO) in a multi-AP network can be associated with the exchange of MLO association information, capabilities, and configuration information between multiple AP devices. Specifically, although MLO is supported in infrastructure WLANs operating according to the IEEE 802.11be amendment to the IEEE 802.11 wireless standard, it is currently available in Wi-Fi EasyMesh provided by the Wi-Fi Alliance. TM MLO is not supported in a mesh network configured by the AP specification or multi-AP specification. In addition, IEEE 1905.1 management frames and messages transmitted by a multi-AP network may not be configured to carry MLO association information, MLO capabilities, or MLO configuration information.

[0041] In various implementations, at least one of the IEEE 1905.1 frames or messages that carry data and other information in a multi-AP network may be modified to carry or indicate one or more of the following: MLO association information, MLO capabilities and MLO configuration information of respective multi-AP devices, respective fronthaul AP MLD of multi-AP devices, or respective backhaul STA MLD of multi-AP devices, and other examples. For example, in some implementations, one or more first IEEE 1905.1 frames or messages may include one or both of the MLD address fields of the DPP configuration object or DPP configuration object that may carry MLO association information, MLO capabilities and MLO configuration information. In some other implementations, one or more second IEEE 1905.1 frames or messages may include MLO support type-length-value (TLV) for indicating the MLO capabilities of one or both of the fronthaul AP MLD or backhaul STA MLD of the respective multi-AP devices. In some cases, one or more third IEEE 1905.1 frames or messages may include or indicate traffic identifiers (TIDs) associated with the fronthaul AP MLD and backhaul STA MLD of the respective multi-AP devices to link mappings.

[0042] Specific implementations of the subject matter described in the present disclosure may be performed to achieve one or more of the following potential advantages. By modifying the IEEE 1905.1 management frames and messages exchanged between multiple AP devices to carry multiple AP devices in a multi-AP network as a multi-AP agent to operate MLO capabilities, MLO association information and MLO configuration information, various aspects of the present disclosure can be implemented between multiple AP devices associated with a multi-AP network. MLO. Specifically, by using APMLD and STA MLD as the fronthaul AP and backhaul STA of multiple AP devices, respectively, various aspects of the present disclosure can allow multiple AP devices to communicate with each other on multiple communication links, thereby increasing the effective bandwidth of the multi-AP network (such as compared to a conventional single-link multi-AP network). Increasing the effective bandwidth of the multi-AP network can reduce latency, and can increase the throughput associated with the multi-AP network.

[0043] Figure 1 1 shows a block diagram of an example multi-AP network 100. In some cases, the multi-AP network 100 can be based on the Wi-Fi EasyMesh protocol published by the Wi-Fi Alliance. TM Specifications to operate. Multi-AP network 100 is shown as including a multi-AP network 100 through one or more hops in the tree topology connected to each other in the four multi-AP devices 110, 120, 130 and 140. The tree topology can ensure that a single return path can be established between any pair of multi-AP devices in the multi-AP network 100. Although not shown for simplicity, it can be defined between multi-AP devices 110, 120, 130 and 140 by which to perform the configuration and control functions for the fronthaul AP and backhaul link logic multi-AP control interface. Multi-AP control interface may exist in the multi-AP network 100 associated with the multi-AP controller and multi-AP agent between.

[0044] exist Figure 1 In the example, the first multi-AP device 110 is configured to operate as a multi-AP controller, and is shown as including a multi-AP controller 111, a fronthaul AP 112, and a backhaul STA 113. The fronthaul AP 112 can facilitate communication between the multi-AP controller 111 and one or more downstream devices. In some instances, the fronthaul AP 112 can establish a multi-AP network 100 through which one or more associated client devices (such as STA0) can access the first BSS on a wireless channel. In some aspects, the backhaul STA of the respective downstream multi-AP device can be associated with the first multi-AP device 110 through a wireless channel based on the IEEE 802.11 wireless standard. 112. In this way, the first multi-AP device 110 and the respective downstream multi-AP device can communicate with each other through the wireless channel of the first BSS. In Figure 1In the example, the first multi-AP device 110 of the fronthaul AP 112 can be associated with the first BSS through the wireless channel and the client device STA0, the second multi-AP device 120 and the third multi-AP device 130 to communicate.

[0045] The multi-AP controller 111 can control the fronthaul AP 112 through its first multi-AP device 110 and one or more downstream multi-AP devices to communicate with each other. Multi-AP controller 111 can also control the backhaul STA 113 and various operations of the backhaul link associated with the first multi-AP device 110 and one or more upstream devices on which to communicate. In some instances, the multi-AP controller 111 can facilitate the multi-AP device added to the multi-AP network 100 loading and pre-configuration process.

[0046] The second multi-AP device 120 is configured to operate as a multi-AP proxy, and is shown as including a multi-AP proxy 121, a fronthaul AP 122, and a backhaul STA 123. The fronthaul AP 122 can facilitate communication between the second multi-AP device 120 and one or more downstream devices. In some instances, the fronthaul AP 112 can establish a second BSS through which one or more associated client devices (such as STA1 and STA2) can access the multi-AP network 100 through a wireless channel. The backhaul STA of each downstream multi-AP device can be associated with the fronthaul AP 122 of the second multi-AP device 120 based on the IEEE 802.11 wireless standard through a wireless channel, thereby allowing the second multi-AP device 120 and the respective downstream multi-AP device to communicate with each other through the wireless channel of the second BSS. In Figure 1 In the example, the second multi-AP device 120 of the fronthaul AP 122 can communicate with the client device STA1-STA2 and the fourth multi-AP device 140 through the wireless channel associated with the second BSS.

[0047] Backhaul STA 123 can facilitate the communication between the second multi-AP device 120 and one or more upstream devices (such as the first multi-AP device 110) through the multi-AP network 100 backhaul link. Multi-AP agent 121 can execute the command received from the multi-AP controller 111, and can report the multi-AP controller 111 fronthaul AP 122, client device STA1-STA2, backhaul STA 123 and backhaul link measurement results and capability information. Multi-AP controller 111 can use the reported measurement results and capability information to the second multi-AP device 120 pre-configured or re-pre-configured multi-AP network 100 of the various wireless resources.

[0048] The third multi-AP device 130 is configured to operate as a multi-AP proxy, and is shown as including a multi-AP proxy 131, a fronthaul AP 132, and a backhaul STA 133. The fronthaul AP 132 can facilitate communication between the third multi-AP device 130 and one or more downstream devices. In some instances, the fronthaul AP 132 can be established on which one or more associated client devices (such as STA3) can access the multi-AP network 100 through a wireless channel. The third BSS. In some instances, the backhaul STA of the respective downstream multi-AP device (not shown for simplicity) can be associated with the third multi-AP device 130 through a wireless channel based on the IEEE 802.11 wireless standard, thereby allowing the third multi-AP device 130 and the respective downstream multi-AP device to communicate with each other through a wireless channel associated with a third BSS.

[0049] Backhaul STA 133 can facilitate communication between the third multi-AP device 130 and one or more upstream devices (such as multi-AP controller 111) through the multi-AP network 100 backhaul link. Multi-AP agent 131 can execute commands received from the multi-AP controller 111, and can report to the multi-AP controller 111 fronthaul AP 132, client device STA3, backhaul STA133 and backhaul link measurement results and capability information. Multi-AP controller 111 can use the reported measurement results and capability information to the third multi-AP device 130 pre-configured or re-pre-configured multi-AP network 100 of various wireless resources.

[0050] The fourth multi-AP device 140 is configured to operate as a multi-AP proxy, and is shown as including a multi-AP proxy 141, a fronthaul AP 142, and a backhaul STA 143. The fronthaul AP 142 can facilitate the communication between the fourth multi-AP device 140 and one or more downstream devices. In some instances, the fronthaul AP 142 can be established on which one or more associated client devices (such as STA4 and STA5) can access the multi-AP network 100 through a wireless channel. The fourth BSS. In some instances, the backhaul STA of the respective downstream multi-AP device (not shown for simplicity) can be associated with the fourth multi-AP device 140 through a wireless channel based on the IEEE 802.11 wireless standard, thereby allowing the fourth multi-AP device 140 and the respective downstream multi-AP device to communicate with each other through the wireless channel associated with the fourth BSS. In Figure 1 In the example of FIG. 4 , fronthaul AP 142 may facilitate communications with client devices STA4 - STA5 over a wireless channel associated with a fourth BSS.

[0051] Backhaul STA 143 can facilitate the communication between the fourth multi-AP device 140 and one or more upstream devices (such as multi-AP controller 111 and multi-AP agent 121) through the multi-AP network 100 backhaul link. Multi-AP agent 141 can execute the command received from the multi-AP controller 111, and can report the measurement results and capability information of the backhaul link of the multi-AP controller 111, the client device STA4-STA5, the backhaul STA 143 and the backhaul link to the multi-AP controller 111. Multi-AP controller 111 can use the reported measurement results and capability information to the fourth multi-AP device 140 pre-configured or re-pre-configured multi-AP network 100 of the various wireless resources.

[0052] In various implementations, the multi-AP controller 111 can use one or more multi-AP devices reported measurement results and capability information to the respective multi-AP devices 120, 130 and 140 associated with the multi-AP agent 121, 131 and 142 pre-configured or re-pre-configured multi-AP network 100 of various wireless resources. In some implementations, the multi-AP controller 111 can be multi-AP devices 120, 130 and 140 loaded and pre-configured to the multi-AP network 100, and can facilitate the multi-AP agent 121, 131 and 141 for their respective multi-AP network 100 to the layer -2 connection of the wireless channel. In some instances, the multi-AP controller 111 can use the device pre-configuration protocol (DPP), multi-AP communication protocol, or push button configuration (PBC) backhaul STA loading process to load multi-AP devices 120, 130 and 140. Multi-AP communication protocol may include IEEE 1905.1 communication protocol and defined by other standards bodies for 1905.1 communication protocol extensions. PBC backhaul STA loading process allows the registrant backhaul STA to use the extension of the PBC process to register the multi-AP agent to inform the registrant backhaul STA is a backhaul STA.

[0053] DPP (which can include Wi-Fi EasyMesh TM Specifications define pre-configuration protocol) can be used to implement layer -2Wi-Fi connection for the backhaul STA, and via multi-AP controller 111 in the multi-AP network 100 in the registrant multi-AP agent and the registered multi-AP agent 1905- layer security. In some instances, DPP can be remotely executed by the network operator during the pre-loading process before deploying multiple AP devices (not shown for simplicity). In some other instances, DPP can be executed by the network operator during the deployment and installation of multiple AP devices. In some aspects, the network operator may be the owner of the multi-AP device, and can provide network services and other multimedia services to users.

[0054] In some implementations, the network operator can delegate the configurator role or capability to the multi-AP controller 111 for preloading process, and can configure multi-AP agent 121, 131 and 141 in one or more as DPP registrants. During the preloading process, the multi-AP controller 111 can obtain configuration information from multi-AP agent 121, 131 and 141, and multi-AP agent 121, 131 and 141 in each exchange one or more IEEE 1905.1 packets to establish a multi-AP network 100 without user participation.

[0055] Figure 2 2 shows a block diagram of an example wireless communication device 200. In some implementations, the wireless communication device 200 may be a device for use in a STA (such as a reference Figure 1 In other implementations, the wireless communication device 200 may be an example of a device used in an AP (such as one of the backhaul STAs 123, 133, and 143 described in the reference). Figure 1 An example of a device used in one of the fronthaul APs 112, 122, and 132 described herein.

[0056] The wireless communication device 200 is capable of sending (or outputting for transmission) and receiving wireless communications (e.g., in the form of wireless packets). For example, the wireless communication device 200 may be configured to send and receive packets in the form of physical layer convergence protocol (PLCP) protocol data units (PPDUs) and medium access control (MAC) protocol data units (MPDUs) that comply with IEEE 802.11 standards (such as those defined by the IEEE 802.11-2016 specification or its amendments, including but not limited to 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba, and 802.11be).

[0057] The wireless communication device 200 may be or may include a chip, a system on a chip (SoC), a chipset, a package, or a device including one or more modems 202, such as a Wi-Fi (IEEE 802.11 compliant) modem. One or more modems 202 (collectively referred to as "modems 202") may also include a WWAN modem (e.g., a modem compliant with 3GPP4G LTE or 5G). In some instances, the wireless communication device 200 may also include one or more radio units 204 (collectively referred to as "radio units 204"). In some aspects, the wireless communication device 200 may also include one or more processors, processing blocks, or processing elements (collectively referred to as "processors 206"), and may also include one or more memory blocks or elements (collectively referred to as "memory 208").

[0058] The modem 202 may include an intelligent hardware block or device such as, for example, an application specific integrated circuit (ASIC) and other possibilities. The modem 202 is configured to implement a PHY layer that can modulate packets and output the modulated packets to the radio unit 204 for transmission over a wireless medium. The modem 202 is configured to obtain modulated packets received by the radio unit 204 and demodulate the packets to provide demodulated packets. In addition to the modulator and demodulator, the modem 202 may also include digital signal processing (DSP) circuits, automatic gain control (AGC), encoders, decoders, multiplexers, and demultiplexers. For example, when in a transmission mode, data obtained from the processor 206 is provided to an encoder, which encodes the data to provide encoded bits. The encoded bits are mapped to points in a modulation constellation (using a selected MCS) to provide modulated symbols. The modulated symbols can be mapped to a number N SS spatial streams or a number N STS The modulated symbols in the respective spatial streams or space-time streams may be multiplexed, transformed via an inverse fast Fourier transform (IFFT) block, and provided to the DSP circuit for Tx windowing and filtering. The digital signal may be provided to a digital-to-analog converter (DAC). The resulting analog signal may be provided to a frequency up-converter and the radio unit 204. In an implementation involving beamforming, the modulated symbols in the respective spatial streams are precoded via a steering matrix before they are preconfigured into the IFFT block.

[0059] When in receive mode, a digital signal received from the radio unit 204 is provided to a DSP circuit configured to acquire the received signal, for example, by detecting the presence of a signal and estimating an initial timing and frequency offset. The DSP circuit is further configured to digitally condition the digital signal, for example, using channel (narrowband) filtering, analog impairment conditioning (such as correction for I / Q imbalance), and applying digital gain to obtain a narrowband signal. The output of the DSP circuit can be fed to an AGC configured to use information extracted from the digital signal (e.g., in one or more received training fields) to determine an appropriate gain. The output of the DSP circuit is also coupled to a demodulator configured to extract modulated symbols from the signal and, for example, calculate a log-likelihood ratio (LLR) for each bit position of each subcarrier in each spatial stream. The demodulator is coupled to a decoder, which can be configured to process the LLRs to provide decoded bits. The decoded bits from all spatial streams are fed to a demultiplexer for demultiplexing. The demultiplexed bits may be descrambled and provided to the MAC layer (processor 206) for processing, evaluation, or interpretation.

[0060] The radio unit 204 includes at least one radio frequency (RF) transmitter (or "transmitter chain") and at least one RF receiver (or "receiver chain"), which can be combined into one or more transceivers. For example, the RF transmitter and receiver can include various DSP circuits, each of which includes at least one power amplifier (PA) and at least one low noise amplifier (LNA). The RF transmitter and receiver can in turn be coupled to one or more antennas. For example, in some implementations, the wireless communication device 200 can include or be coupled to multiple transmit antennas (each with a corresponding transmit chain) and multiple receive antennas (each with a corresponding receive chain). The symbols output from the modem 202 are provided to the radio unit 204, which transmits the symbols via the coupled antennas. Similarly, the symbols received via the antennas are obtained by the radio unit 204, which provides the symbols to the modem 202.

[0061] The processor 206 may include an intelligent hardware block or device designed to perform the functions described herein (such as, for example, a processing core, a processing block, a central processing unit (CPU), a microprocessor, a microcontroller, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD) (such as a field programmable gate array (FPGA)), discrete gate or transistor logic, discrete hardware components, or any combination thereof). The processor 206 processes information received through the radio unit 204 and the modem 202, and processes information to be output by the modem 202 and the radio unit 204 for transmission through a wireless medium. For example, the processor 206 may implement a control plane and MAC layer configured to perform various operations related to the generation and transmission of MPDUs, frames, or packets. The MAC layer is configured to perform or facilitate encoding and decoding of frames, spatial multiplexing, space-time block coding (STBC), beamforming, and OFDMA resource allocation, as well as other operations or techniques. In some implementations, the processor 206 may control the modem 202 so that the modem performs the various operations described herein.

[0062] The memory 208 may include a tangible storage medium, such as a random access memory (RAM) or a read-only memory (ROM), or a combination thereof. The memory 208 may also store non-transitory processor or computer executable software (SW) code containing instructions that, when executed by the processor 206, cause the processor to perform various operations for wireless communication described herein, including generation, transmission, reception, and interpretation of MPDUs, frames, or packets. For example, various functions of the components disclosed herein, or various blocks or steps of the methods, operations, processes, or algorithms described herein may be implemented as one or more modules of one or more computer programs.

[0063] In some implementations, the processor 206 and the memory 208 may be components of a processing system. A processing system may generally refer to a system or series of machines or components that receives input and processes the input to produce a set of outputs that may be passed to other systems or components of the wireless communication device 200. For example, the processing system of the wireless communication device 200 may refer to a system that includes various other components or subcomponents of the wireless communication device 200.

[0064] Figure 3ABlock diagram showing an example multi-AP controller 302. In some instances, the multi-AP controller 302 may be an example of a multi-AP controller 111 implemented within each multi-AP device disclosed herein. Multi-AP controller 302 includes a DPP unit 310, a multi-link device (MLD) 320, one or more wired interfaces 330, and one or more wireless interfaces 340. DPP unit 310 may implement DPP to load or pre-configure one or more multi-AP agents to a multi-AP network (such as a reference Figure 1 Described multi-AP network 100) associated with one or more communication links or channels. In some instances, the DPP unit 310 can be operated according to a specific network role defined in the DPP specification. For example, in some aspects, the DPP unit 310 can be operated based on the DPP configuration, and perform operations associated with the DPP configurator.

[0065] MLD 320 is shown as including AP MLD 321 and STA MLD 322. AP MLD 321 may include multiple APs operating on respective multiple different communication links (or may be associated with multiple APs operating on respective multiple different communication links). For example, in some implementations, AP MLD 321 may include a first AP operating on one or more wireless channels in the 2.4 GHz band, may include a second AP operating on one or more wireless channels in the 5 GHz band, and may include a third AP operating on one or more wireless channels in the 6 GHz band. In some aspects, AP MLD 321 may operate in accordance with IEEE 802.11be or subsequent amendments to the IEEE 802.11 wireless standard, and may be associated with IEEE 1905.1 communication protocol, EasyMesh TM Communication protocol or multi-AP communication protocol in one or more compatible. In some implementations, AP MLD 321 can be used as a fronthaul AP of one or more multi-AP devices disclosed herein.

[0066] The STA MLD 322 may include (or may be associated with) a plurality of STAs operating on respective plurality of different communication links. For example, in some implementations, the STA MLD 322 may include a first STA operating on one or more wireless channels in the 2.4 GHz band, may include a second STA operating on one or more wireless channels in the 5 GHz band, and may include a third STA operating on one or more wireless channels in the 6 GHz band. In some aspects, the STA MLD 322 may operate in accordance with IEEE 802.11be or subsequent amendments to the IEEE 802.11 wireless standard, and may be associated with IEEE 1905.1 communication protocols, EasyMesh TM Communication protocol or multi-AP communication protocol in one or more compatible. In some implementations, STA MLD 322 can be used as a backhaul STA of one or more multi-AP controllers disclosed herein.

[0067] Wired interface 330 may be used to communicate with a user through a wired medium such as, but not limited to, Ethernet, coaxial cable, power line communication (PLC), or multimedia over coaxial cable. and other examples) to communicate with other devices via wired interfaces. Wireless interface 340 may be used to communicate via wireless media such as, but not limited to, one or more Wi-Fi channels, link or cellular channel, among other examples) to communicate wirelessly with other devices.

[0068] Figure 3B Block diagram showing an example multi-AP agent 304. In some instances, the multi-AP agent 304 may be an example of a multi-AP agent implemented within each multi-AP device disclosed herein. Multi-AP agent 304 includes a DPP unit 315, MLD 325, one or more wired interfaces 335, and one or more wireless interfaces 345. DPP unit 315 may be based on DPP registration 316 to operate, and may be configured to perform multi-AP agent 304 associated with the DPP registrant. In some implementations, the DPP unit 315 may provide a multi-AP controller (such as a reference) having capabilities, parameters, configuration files, or one or more of the measurement results Figure 3ADescribed multi-AP controller 302), and multi-AP controller can be multi-AP agent 304 registered to the multi-AP network. In some instances, the multi-AP controller can use a wireless medium or wired connection for multi-AP agent 304 pre-configured to multi-AP network layer -2 connection. Once the multi-AP agent 304 obtains a multi-AP network layer -2 connection, multi-AP agent 304 can begin to find multiple AP controllers or other multi-AP agents nearby. In some aspects, the multi-AP controller can be multi-AP agent 304 pre-configured fronthaul BSS and backhaul BSS to access multiple AP networks.

[0069] MLD 325 is shown as including AP MLD 326 and STA MLD 327. AP MLD 326 may include (or may be associated with) multiple APs operating on respective multiple different communication links. For example, in some implementations, AP MLD 326 may include a first AP operating on one or more wireless channels in the 2.4 GHz band, may include a second AP operating on one or more wireless channels in the 5 GHz band, and may include a third AP operating on one or more wireless channels in the 6 GHz band. In some aspects, AP MLD 326 may operate in accordance with IEEE 802.11be or subsequent amendments to the IEEE 802.11 wireless standard, and may be associated with IEEE 1905.1 communication protocols, EasyMesh TM One or more of the communication protocol or multi-AP communication protocol are compatible.

[0070] The STA MLD 327 may include (or may be associated with) a plurality of STAs operating on respective plurality of different communication links. For example, in some implementations, the STA MLD 327 may include a first STA operating on one or more wireless channels in the 2.4 GHz band, may include a second STA operating on one or more wireless channels in the 5 GHz band, and may include a third STA operating on one or more wireless channels in the 6 GHz band. In some aspects, the STA MLD 322 may operate in accordance with IEEE 802.11be or subsequent amendments to the IEEE 802.11 wireless standard, and may be associated with IEEE 1905.1 communication protocols, EasyMesh TM Communication protocol or multi-AP communication protocol in one or more compatible. In some implementations, STA MLD 327 can be used as a backhaul STA disclosed herein one or more multi-AP proxy.

[0071] Wired interface 335 may be used to communicate with a user through a wired medium such as, but not limited to, Ethernet, coaxial cable, power line communication (PLC), or multimedia over coaxial cable. and other examples) to communicate with other devices via wired communication. The wireless interface 345 may be used to communicate via wireless media (such as, but not limited to, one or more Wi-Fi channels, link or cellular channel, among other examples) to communicate wirelessly with other devices.

[0072] Figure 4A 4 shows a block diagram of an example AP 402. In some implementations, the AP 402 may be a Figure 1 The fronthaul APs 112, 122, 132, and 142 described herein may be within or in conjunction with one or more of the fronthaul APs 112, 122, 132, and 142. Figure 1 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 67, Figure 2 An example implementation of the wireless communication device 200 described herein. The AP 402 includes a plurality of antennas 420 coupled to the wireless communication device 410 to send and receive wireless communications. The AP 402 includes an application processor 430 coupled to the wireless communication device 410, and includes a memory 440 coupled to the application processor 430. The AP 402 also includes at least one external network interface 450, which enables the AP 402 to communicate with a core network or a backhaul network to obtain access to an external network including the Internet. For example, the external network interface 450 may include one or both of a wired (e.g., Ethernet) network interface and a wireless network interface (such as a WWAN interface). Components in the above components may communicate directly or indirectly with other components in the components through at least one bus. The AP 402 may also include a housing that surrounds the wireless communication device 410, the application processor 430, the memory 440, and at least portions of the antennas 420 and the external network interface 450. In some implementations, the application processor 430 and the memory 440 may be components of the processing system. As discussed, a processing system may generally refer to a system or series of machines or components that receive inputs and process the inputs to produce a set of outputs that may be passed to other systems or components of the AP 402. For example, the processing system of the AP 402 may refer to a system that includes various other components or subcomponents of the AP 402.

[0073] The processing system of AP 402 may be connected to other components of AP 402, and may process information (such as input or signals) received from other components, output information to other components, etc. For example, a chip or modem of AP 402 may include a processing system, a first interface for receiving or obtaining information, and a second interface for outputting or sending information. In some instances, the first interface may refer to an interface between a processing system of the chip or modem and a receiver, so that AP 402 may receive information or signal input, and information may be passed to the processing system. In some instances, the second interface may refer to an interface between a processing system of the chip or modem and a transmitter, so that AP 402 may send information output from the chip or modem. One of ordinary skill in the art will readily recognize that the second interface may also obtain or receive information or signal input, and the first interface may also output, send, or provide information.

[0074] Figure 4B 404. In some implementations, STA 404 may be a Figure 1 One or more backhaul STA MLDs in the backhaul STA MLD described or with reference Figure 1 4. The STA 404 includes a wireless communication device 415. In some examples, the wireless communication device 415 may be a reference to the example of one or more STAs in the backhaul STA MLD associated with one or more backhaul STA MLDs. Figure 2An example implementation of the wireless communication device 200 described herein. The STA 404 includes one or more antennas 425 coupled to the wireless communication device 415 to send and receive wireless communications. The STA 404 includes an application processor 435 coupled to the wireless communication device 415, and includes a memory 445 coupled to the application processor 435. The STA 404 may also include a user interface (UI) 455 (such as a touch screen or keyboard) and a display 465, which may be integrated with the UI 455 to form a touch screen display. In some implementations, the STA 404 may also include one or more sensors 475, such as, for example, one or more inertial sensors, accelerometers, temperature sensors, pressure sensors, or altitude sensors. Components of the above components may communicate directly or indirectly with other components of the components through at least one bus. The STA 404 may also include a housing that surrounds the wireless communication device 415, the application processor 435, the memory 445, and at least portions of the antenna 425, the UI 455, and the display 465. In some implementations, the application processor 435 and the memory 445 may be components of the processing system. As discussed, a processing system may generally refer to a system or series of machines or components that receives input and processes the input to produce a set of outputs that may be passed to other systems or components, such as STA 404. For example, a processing system of STA 404 may refer to a system that includes various other components or subcomponents of STA 404.

[0075] The processing system of STA 404 may be connected to other components of STA 404, and may process information (such as input or signal) received from other components, output information to other components, etc. For example, a chip or modem of STA 404 may include a processing system, a first interface for receiving or obtaining information, and a second interface for outputting or sending information. In some instances, the first interface may refer to an interface between a processing system of a chip or modem and a receiver, so that STA 404 can receive information or signal input, and information can be passed to the processing system. In some instances, the second interface may refer to an interface between a processing system of a chip or modem and a transmitter, so that STA404 can send information output from a chip or modem. Those of ordinary skill in the art will readily recognize that the second interface may also obtain or receive information or signal input, and the first interface may also output, send, or provide information.

[0076] Figure 5 An example communication system 500 is shown, which includes an AP MLD 510 and a non-AP MLD 520. The AP MLD 510 may be Figure 2 A wireless communication device 200, Figure 3A AP MLD 321 Figure 3B AP MLD 326 or Figure 4A The non-AP MLD 520 may be an example of an AP 402. Figure 2 A wireless communication device 200, Figure 3A STA MLD322, Figure 3B STA MLD 327 or Figure 4A An example of STA 404. In some implementations, AP MLD 510 and STA MLD 520 may be implemented in a multi-AP device forming a multi-AP network. For example, in some aspects, AP MLD510 may be implemented as a fronthaul AP in a multi-AP controller or multi-AP proxy, and non-AP MLD 520 may be implemented as a backhaul STA in a multi-AP controller or multi-AP proxy. In this way, multiple AP devices including AP MLD 510 as a fronthaul AP may be able to communicate with one or more downstream devices (such as a client device or a downstream multi-AP device backhaul STA) through multiple communication links, and multiple AP devices including STA MLD 520 as a backhaul STA may be able to communicate with one or more upstream devices (such as a client device or an upstream multi-AP device fronthaul AP) through multiple communication links. Therefore, according to various aspects of the subject matter disclosed herein, multiple AP devices including fronthaul AP MLD and backhaul STA MLD can implement multi-link operation (MLO) in a multi-AP network (or other suitable mesh network).

[0077] exist Figure 5 In the example of FIG. 5 , the AP MLD 510 includes three APs 511-513 associated with (or operating on) respective communication links 501-503. In some other implementations, the AP MLD 510 may include Figure 5 501-503. Although APs 511-513 may share a common association context (via AP MLD 510), each of APs 511-513 may establish a respective BSS over the AP's associated communication link. APs 511-513 may also establish their respective communication links 501-503 over different frequency bands. For example, AP 511 may operate over a 2.4 GHz band, AP 512 may operate over a 5 GHz band, and AP 513 may operate over a 6 GHz band.

[0078] The non-AP MLD 520 includes three STAs 521-523, which can be configured to communicate on communication links 501-503, respectively. Specifically, STA 521 can operate on the 2.4 GHz band, STA 522 can operate on the 5 GHz band, and STA 523 can operate on the 6 GHz band. Figure 5 In the example of FIG. 5 , the non-AP MLD 520 is shown as including only three STAs. In some other implementations, the non-AP MLD 520 may include Figure 5 Those depicted in the figure have fewer or more STAs than those depicted in the figure.

[0079] The IEEE 802.11be revision of the IEEE 802.11 standard defines several modes in which non-AP MLDs can operate. The various operating modes depend on the number of wireless radios associated with the non-AP MLD and the ability of the non-AP MLD to communicate (such as by sending or receiving) on ​​multiple communication links simultaneously. In some implementations, the non-AP MLD 520 may include a single radio, or may be otherwise capable of communicating on only one link at a time. In such an implementation, the non-AP MLD 520 may operate in a multi-link single radio (MLSR) mode or an enhanced MLSR (EMLSR) mode. A non-AP MLD operating in the EMLSR mode may simultaneously listen to a specific type of communication (such as a buffer status report poll (BSRP) frame or a multi-user request to send (MU-RTS) frame) on multiple communication links, but may only send or receive on one communication link at any given time. For example, STAs 521 and 522 may simultaneously listen to their respective links 501 and 502 during the listening interval. However, if STA 521 detects a BSRP frame on link 501, non-AP MLD 520 then tunes each of the antennas of the non-AP MLD (including the antenna used by STA 522 during the listening interval) to operate on link 501. In contrast, a non-AP MLD operating in MLSR mode can only listen to one communication link at any given time, and transmit or receive on one communication link. For example, during the time during which STA 522 is active, STA 521 must be in power saving mode.

[0080] In some other implementations, the non-AP MLD 520 may include multiple radios and may be capable of concurrent communication on each of the links 501-503. In such implementations, the non-AP MLD 520 may operate in a multi-link multi-radio (MLMR) simultaneous transmit and receive (STR) mode or a multi-link multi-radio non-STR (NSTR) mode. A non-AP MLD operating in the MLMR STR mode may transmit and receive simultaneously (or concurrently) on multiple communication links. For example, STA 521 may transmit or receive on link 501, while STA 522 may asynchronously transmit or receive concurrently on link 502. In contrast, a non-AP MLD operating in the MLMR NSTR mode may transmit and receive concurrently on multiple communication links only when such communications are synchronous. For example, STAs 522 and 523 may transmit concurrently on links 502 and 503, and may receive concurrently on links 502 and 503. However, when STA 523 is receiving on link 503, STA 522 cannot transmit on link 502.

[0081] Further, a non-AP MLD may include multiple radios, but may be capable of concurrent communication on only a subset of links. In such an implementation, the non-AP MLD 520 may operate in an enhanced MLMR (EMLMR) mode or a hybrid EMLSR mode. A non-AP MLD operating in the EMLMR mode supports MLMR STR operation between certain communication link pairs. For example, STAs 521 and 522 may communicate concurrently on their respective links 501 and 502 according to the MLMR STR operation mode.

[0082] Figure 6 A block diagram of an example multi-AP network 600 supporting multi-link operation is shown. In various implementations, the multi-AP network 600 may be based on the Wi-Fi EasyMesh protocol published by the Wi-Fi Alliance. TM Standard or Multi-AP TM In some implementations, multi-AP network 600 may also be capable of multi-link operation (MLO) as defined in IEEE 802.11be or a later amendment to the IEEE 802.11 wireless standard.

[0083] Multi-AP network 600 is shown as including one or more multi-link hops associated with the multi-AP network 600 in a tree topology interconnected with four multi-AP devices 610, 620, 630 and 640. The tree topology ensures that a single return path can be established between any pair of multi-AP devices in the multi-AP network 600. Although Figure 6 The example shows four multi-AP devices 610, 620, 630 and 640, but in some other implementations, the multi-AP network 600 may include other number of multi-AP devices. In some cases, the logic multi-AP control interface (for simplicity, not shown) may be defined between multi-AP devices 610, 620, 630 and 640, through the logic multi-AP control interface to perform configuration and control functions for the fronthaul AP and backhaul link. In addition, the multi-AP control interface (for simplicity, not shown) may exist in a multi-AP controller and a multi-AP network 600 associated with the multi-AP agent between.

[0084] Multi-AP device 610, 620, 630 and 640 may be capable of operating as a multi-AP controller or multi-AP agent, and may also establish multiple communication links between each other to form a mesh or other ad hoc network capable of MLO. Any suitable wireless communication device. In various implementations, each of the multi-AP devices 610, 620, 630 and 640 may include an AP MLD and a STA MLD. In some implementations, each AP MLD may be a reference Figure 5 The example of the AP MLD 510 described herein may include a first AP associated with a first communication link and one or more second APs associated with one or more respective second communication links. Each STA MLD may be a reference Figure 5 An example of a non-AP MLD 520 is described, and may include a first STA (or "non-AP STA") associated with a first communication link and one or more second STAs associated with one or more respective second communication links. In some aspects, each of the plurality of communication links may include one or more wireless channels in a respective frequency band of the 2.4 GHz band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.

[0085] exist Figure 6In the example, the first multi-AP device 610 is configured to operate as a multi-AP controller, and is shown as including a multi-AP controller 611, a fronthaul AP MLD 612, and a backhaul STA MLD 613. The fronthaul AP MLD 612 can facilitate communication between the multi-AP controller 611 and one or more downstream devices, and may include multiple APs associated with the respective multiple communication links of the multi-AP network 600. In some implementations, each AP associated with the fronthaul AP MLD 612 can establish its own BSS through which one or more downstream devices (such as client devices and multi-AP devices) can access the multi-AP network 600. Figure 6 In the example, the fronthaul AP MLD 612 provides a plurality of communication links on which the client device STA10 and the second multi-AP device 620 can be associated with the fronthaul AP MLD 612 based on the IEEE 802.11 wireless standard. In this way, the fronthaul AP MLD 612 can communicate with the client device STA10 and the second multi-AP device 620 simultaneously through multiple communication links of the multi-AP network 600.

[0086] Backhaul STA MLD 613 can facilitate the communication between the first multi-AP device 610 and one or more upstream devices (not shown for simplicity) through one or more backhaul links of the multi-AP network 600. Multi-AP controller 611 can control the fronthaul AP MLD 612, backhaul STA MLD 613 and each operation of one or more corresponding backhaul links. In some instances, the multi-AP controller 611 can facilitate the loading and pre-configuration process of adding other multi-AP devices to the multi-AP network 600.

[0087] The second multi-AP device 620 is configured to operate as a first multi-AP proxy, and is shown as including a multi-AP proxy 621, a fronthaul AP MLD 622, and a backhaul STA MLD 623. The fronthaul AP MLD 622 can facilitate communication between the first multi-AP proxy 621 and one or more downstream devices, and may include multiple APs associated with each of the multiple communication links. In some implementations, each AP associated with the fronthaul AP MLD 622 can establish an AP through which one or more downstream devices (such as client devices and multi-AP devices) can access multiple AP networks 600 through multiple communication links to their respective BSS. In Figure 6In the example, the fronthaul AP MLD 622 provides a plurality of communication links through which the client device STA11-STA12 and the fourth multi-AP device 640 can be associated with the fronthaul AP MLD 622 based on the IEEE 802.11 wireless standard. In this way, the fronthaul AP MLD 622 can communicate with the client device STA11-STA12 and the fourth multi-AP device 640 simultaneously through the multiple communication links of the multi-AP network 600.

[0088] Backhaul STA MLD 623 can facilitate the communication between the second multi-AP device 620 and one or more upstream devices (such as multi-AP controller 611) through the multi-AP network 600 of one or more backhaul links. The first multi-AP agent 621 can execute commands received from the multi-AP controller 611, and can report to the multi-AP controller 611 front AP MLD 622, client device STA11-STA12, backhaul STA MLD 623 and one or more backhaul link measurement results and capability information. The first multi-AP agent 621 can also perform various operations and processes in response to instructions or commands provided by the multi-AP controller 611 (or by one or more multi-AP network 600 associated with the agent) .

[0089] The third multi-AP device 630 is configured to operate as a second multi-AP proxy, and is shown as including a multi-AP proxy 631, a fronthaul AP MLD 632, and a backhaul STA MLD 633. The fronthaul AP MLD 632 can facilitate communication between the second multi-AP proxy 631 and one or more downstream devices, and may include multiple APs associated with respective multiple communication links. In some implementations, each AP associated with the fronthaul AP MLD 632 can establish its own BSS through which one or more downstream devices (such as client devices and multi-AP devices) can access the multi-AP network 600. Figure 6 In the example, the fronthaul AP MLD 632 provides a plurality of communication links through which the client device STA13 and one or more downstream multi-AP devices (not shown for simplicity) can be associated with the fronthaul AP MLD 632 based on the IEEE 802.11 wireless standard. In this way, the fronthaul AP MLD 632 can be simultaneously with the client device STA13 and one or more downstream multi-AP devices through multiple communication links of the multi-AP network 600.

[0090] Backhaul STA MLD 633 can facilitate communication between the third multi-AP device 630 and one or more upstream devices (such as multi-AP controller 611) through one or more backhaul links of the multi-AP network 600. The second multi-AP agent 631 can execute commands received from the multi-AP controller 611, and can report the measurement results and capability information of the fronthaul AP MLD 632, the client device STA13, the backhaul STA MLD 633, and one or more backhaul links to the multi-AP controller 611. The second multi-AP agent 631 can also perform various operations and processes in response to instructions or commands provided by the multi-AP controller 611 (or by one or more multi-AP agents associated with the multi-AP network 600).

[0091] The fourth multi-AP device 640 is configured to operate as a third multi-AP proxy, and is shown as including a multi-AP proxy 641, a fronthaul AP MLD 642, and a backhaul STA MLD 643. The fronthaul AP MLD 642 can facilitate communication between the third multi-AP proxy 641 and one or more downstream devices, and may include multiple APs associated with respective multiple communication links. In some implementations, each AP associated with the fronthaul AP MLD 642 can establish its own BSS through which one or more downstream devices (such as client devices and multi-AP devices) can access the multi-AP network 600. Figure 6 In the example, the fronthaul AP MLD 642 provides a plurality of communication links through which the client device STA14-STA15 and one or more downstream multi-AP devices (not shown for simplicity) can be associated with the fronthaul AP MLD 642 based on the IEEE 802.11 wireless standard. In this way, the fronthaul AP MLD 642 can communicate with the client device STA14-STA15 and one or more downstream multi-AP devices through multiple communication links of the multi-AP network 600 simultaneously.

[0092] Backhaul STA MLD 643 can facilitate the communication between the third multi-AP device 640 and one or more upstream devices (such as multi-AP controller 611 and the first multi-AP agent 621) through the multi-AP network 600 of one or more backhaul links. The third multi-AP agent 641 can execute commands received from the multi-AP controller 611, and can report to the multi-AP controller 611 fronthaul AP MLD 642, client device STA14-STA15, backhaul STA MLD 643 and one or more backhaul link measurement results and capability information. The third multi-AP agent 641 can also perform various operations and processes in response to instructions or commands provided by the multi-AP controller 611 (or by one or more multi-AP network 600 associated with the agent) .

[0093] In various implementations, the multi-AP controller 611 (or one or more multi-AP agents) can use the multi-AP devices 620, 630 and 640 reported measurement results and capability information to the respective multi-AP agent 621, 631 and 641 pre-configured or re-configured multi-AP network 600 of various wireless resources. In some implementations, the multi-AP controller 611 can be established by the respective multi-AP agent 621, 631 and 641 to the multi-AP network 600 associated with a plurality of communication links in each communication link layer -2 connection, the multi-AP device 620, 630 and 640 loaded and pre-configured to the multi-AP network 600. In some instances, the multi-AP controller 611 can use DPP, multi-AP communication protocol or PBC backhaul STA loading process one or more to load multi-AP devices 620, 630 and 640.

[0094] As discussed, the multi-AP communication protocol may include IEEE 1905.1 communication protocol and extensions to the 1905.1 communication protocol defined by other standards bodies. PBC backhaul STA loading process allows the registrant backhaul STA to use the extensions to the PBC process to register the multi-AP agent to notify the registrant backhaul STA is the backhaul STA MLD. DPP may include Wi-FiEasyMesh TM Specifications define the pre-configuration protocol, and can be used to implement the backhaul STA layer -2Wi-Fi connection, and via the multi-AP controller 611 in the multi-AP network 600 of the registrant multi-AP agent and the registered multi-AP agent 1905- layer security.

[0095] In various implementations, the multi-AP controller 611 can be loaded by using DPP and multi-AP communication protocols (such as 1905.1 communication protocol) both multi-AP agent 621, 622 and 623 to establish a multi-AP network. In some cases, the network operator (for simplicity, not shown) can be multi-AP controller 611 and multi-AP agent 621, 631 and 641 deployed to the destination before the remote execution of the DPP during the pre-loading process. For example, in the pre-loading process, the network operator can serve as the role of the DPP configurator network, as well as multi-AP controller 611 and multi-AP agent 621, 631 and 641 perform DPP.

[0096] In some other implementations, for each of the multi-AP controller 611 and multi-AP agent 621, 631 and 641 configuration information (such as DPP configuration information) can be generated by the network operator during the DPP process and stored. In some cases, the network operator can store DPP configuration information in the database associated with the corresponding multi-AP network (in a home, office or other location). DPP configuration information can be used by the network operator to remotely manage multi-AP devices 610, 620, 630 and 640. During the pre-loading process, the network operator can also be configured before the deployment of the multi-AP controller 611 DPP unit is configured as a DPP configurator, to the configurator role or ability to delegate to the multi-AP controller 611. Multi-AP agent 621, 631 and 641 can be configured as a DPP registrant (after the loading process, which can be called a DPP peer).

[0097] As discussed, aspects of the present disclosure recognize that the use of AP MLD and STA MLD in multiple AP devices to implement multi-link operation (MLO) in a multi-AP network can be associated with the exchange of MLO association information, capabilities, and configuration information between multiple AP devices. Specifically, although MLO is supported in an infrastructure WLAN operating according to the 802.11be revision of the IEEE 802.11 wireless standard, in accordance with Wi-Fi EasyMesh provided by the Wi-Fi Alliance TM Mesh networks configured with the AP specification or multi-AP specification do not currently support MLO. In addition, IEEE 1905.1 management frames and messages transmitted through a multi-AP network may not be configured to carry MLO association information, MLO capabilities, or MLO configuration information.

[0098] In various implementations, at least one of the IEEE 1905.1 frames or messages that carry data and other information in a multi-AP network may be modified to carry or indicate one or more of the following: MLO association information, MLO capabilities and MLO configuration information of respective multi-AP devices, respective fronthaul AP MLD of multi-AP devices, or respective backhaul STA MLD of multi-AP devices, and other examples. For example, in some implementations, one or more first IEEE 1905.1 frames or messages may include one or both of the MLD address fields of the DPP configuration object or DPP configuration object that may carry MLO association information, MLO capabilities and MLO configuration information. In some other implementations, one or more second IEEE 1905.1 frames or messages may include MLO support type-length-value (TLV) for indicating the MLO capabilities of one or both of the fronthaul AP MLD or backhaul STA MLD of the respective multi-AP devices. In some cases, one or more third IEEE 1905.1 frames or messages may include or indicate traffic identifiers (TIDs) associated with the fronthaul AP MLD and backhaul STA MLD of the respective multi-AP devices to link mappings.

[0099] By modifying the IEEE 1905.1 management frame and the messages exchanged between multiple AP devices, to carry multiple AP devices in a multi-AP network as multiple AP agents operating MLO capabilities, MLO association information, and MLO configuration information, various aspects of the present disclosure can be implemented in a multi-AP network associated with multiple AP devices MLO between. Specifically, by using APMLD and STA MLD as the fronthaul AP and backhaul STA of multiple AP devices, respectively, various aspects of the present disclosure allow multiple AP devices to communicate with each other on multiple communication links, thereby increasing the effective bandwidth of the multi-AP network (such as compared to a conventional single-link multi-AP network).

[0100] Figure 7 Shown is a sequence diagram of an example wireless communication 700 supporting multi-link operation in a multi-AP network. Wireless communication 700 may be performed between a multi-AP controller 705, a first multi-AP agent 710 and a second multi-AP agent 720. Multi-AP controller 705 may be Figure 2 A wireless communication device 200, Figure 3A The multi-AP controller 302 or Figure 6 An example of a first multi-AP device 610. The first multi-AP proxy 710 and the second multi-AP proxy 720 may be Figure 2 A wireless communication device 200, Figure 3B Multi-AP proxy 304, or Figure 6An example of one or more of the multi-AP proxy 620, 630 or 640. In some instances, the multi-AP network can be Figure 6 An example of a multi-AP network 600 is shown.

[0101] The multi-AP controller 705 may include a fronthaul AP MLD and a backhaul STA MLD (not shown for simplicity). The fronthaul AP MLD may include multiple APs operating on multiple communication links, and the backhaul STA MLD may include multiple STAs operating on respective multiple communication links. Each AP included in the fronthaul AP MLD may establish a corresponding first BSS on its respective communication link to implement multi-link communication with one or more downstream devices associated with the first BSS. Each STA included in the backhaul STA MLD may be associated with the respective BSS established by the fronthaul AP MLD of the upstream device (not shown for simplicity). In some implementations, the multi-AP controller 705 may be configured to load a first multi-AP agent 710 and a second multi-AP agent 720 according to the DPP. In some other implementations, the multi-AP controller 705 may be configured to load a first multi-AP agent 710 and a second multi-AP agent 720 according to the multi-AP communication protocol.

[0102] The first multi-AP agent 710 may include a fronthaul AP MLD, the fronthaul AP MLD includes a plurality of APs that can establish a corresponding BSS on each of the plurality of communication links, and may include a backhaul STA MLD, the backhaul STA MLD includes a plurality of STAs that can be associated with the respective BSS established by the multi-AP controller 705 of the fronthaul AP MLD. In this way, the first multi-AP agent 710 of the fronthaul AP MLD can be implemented with one or more downstream devices (such as the second multi-AP agent 720) for multi-link communication, and the first multi-AP agent 710 of the backhaul STA MLD can be implemented with one or more upstream devices (such as multi-AP controller 705) for multi-link communication.

[0103] The second multi-AP agent 720 may include a fronthaul AP MLD, the fronthaul AP MLD includes a plurality of APs that can establish a corresponding BSS on each of the plurality of communication links, and may include a backhaul STA MLD, the backhaul STA MLD includes a plurality of STAs that can be associated with the respective BSS established by the first multi-AP agent 710 of the fronthaul AP MLD. In this way, the second multi-AP agent 720 of the fronthaul AP MLD can implement multi-link communication with one or more downstream devices (for simplicity, not shown), and the second multi-AP agent 720 of the backhaul STA MLD can implement multi-link communication with one or more upstream devices (such as the first multi-AP agent 720).

[0104] In some implementations, the first multi-AP agent 710 can establish a backhaul connection with the second multi-AP agent 720. For example, at 731, the first multi-AP agent 710 obtains the MLO capability information for each STA of the first multi-AP agent 710 backhaul STA MLD. At 732, the first multi-AP agent 710 sends a device pre-configuration protocol (DPP) configuration request message to the multi-AP controller 705 via a multi-AP network first communication link. The DPP configuration request message may indicate the MLO capability of all STAs associated with the first multi-AP agent 710 backhaul STA MLD. In some aspects, the MLO capability may be indicated in the DPP configuration object carried in the DPP configuration request message.

[0105] At 733, the multi-AP controller 705 receives a DPP configuration request message, the DPP configuration request message carries the MLO capability for the first multi-AP agent 710 of the backhaul STA MLD, and based on the received MLO capability to obtain the MLO association information for the first multi-AP agent 710. At 734, the multi-AP controller 705 sends a DPP configuration response message to the first multi-AP agent 710 via a first communication link. The DPP configuration response message may indicate the MLO association information for the first multi-AP agent 710. In some aspects, the MLO association information may be indicated in the MLD address field of the DPP configuration object carried in the DPP configuration response message. At 735, the first multi-AP agent 710 is based on the MLO association information provided by the multi-AP controller 705, and the multi-AP network establishes a return path with the second multi-AP agent 720 on multiple communication links.

[0106] In some other implementations, the first multi-AP agent 710 can also configure one or more BSS on one or more respective communication links of the multi-AP network. For example, at 741, the first multi-AP agent 710 obtains the MLO capability of the BSS established by the first multi-AP agent 710 of the backhaul STA MLD. At 742, the first multi-AP agent 710 sends a basic service set (BSS) configuration request message to the multi-AP controller 705 via a first communication link. The BSS configuration request message may indicate the first multi-AP agent 710 of the backhaul STA MLD MLO capability. At 743, the multi-AP controller 705 receives a BSS configuration request message, which indicates the first multi-AP agent 710 of the backhaul STA MLD MLO capability, and obtains a list of BSSs having the same or public MLD ID. In some aspects, the list of BSSs may be indicated in the DPP configuration object carried in the BSS configuration request message. At 744, the multi-AP controller 705 sends a BSS configuration response message to the first multi-AP agent 710 via a first communication link. The BSS configuration response message may indicate one or more BSSs associated with the same or public MLD ID. In some aspects, one or more BSSs associated with a public MLD ID may be indicated in the MLD address field of the DPP configuration object carried in the BSS configuration response message. In some other aspects, the multi-AP controller 705 may send a BSS configuration result message to the first multi-AP agent 710 via a first communication link. The BSS configuration result message may include an MLD configuration report TLV, which indicates the number of MLDs reported in the BSS configuration result message, MLD MAC address, the number of BSSs operating within the MLD, and the MAC address of the BSS, as well as other examples.

[0107] In some other implementations, the first multi-AP agent 710 can provide its fronthaul AP MLD or backhaul STA MLD in response to the request from the multi-AP controller 705 MLO capability information. For example, at 751, the multi-AP controller 705 generates one or more queries for the MLO capability information associated with the first multi-AP agent 710. At 752, the multi-AP controller 705 sends an AP query message to the first multi-AP agent 710 via a first communication link. In some instances, the AP capability query message may include a request for the first multi-AP agent 710 MLO capability of the fronthaul AP MLD. For example, at 753, the first multi-AP agent 710 receives the request, and obtains the MLO capability information for each AP associated with the first multi-AP agent 710 fronthaul AP MLD. At 754, the first multi-AP agent 710 sends a multi-AP capability report message to the multi-AP controller 705 via a first communication link. AP capability report message may indicate the MLO capability of the AP associated with the first multi-AP agent 710 fronthaul AP MLD. In some aspects, the MLO capability may be indicated in an MLO support type-length-value (TLV) of the AP Capability Report message. The MLO Support TLV may indicate a MAC address of the fronthaul AP MLD, IEEE 802.11be EML capabilities of the fronthaul AP MLD, IEEE 802.11be MLD capabilities of the fronthaul AP MLD, the number of links associated with the fronthaul AP MLD, link IDs, MAC addresses of the links, an operation category of the fronthaul AP MLD, and a channel number of the fronthaul AP MLD, among other examples.

[0108] In some other instances, the AP capability query message may include a request for the first multi-AP agent 710 backhaul STAMLD MLO capability. For example, at 755, the first multi-AP agent 710 receives the request, and obtains the MLO capability information for each STA in the backhaul STA MLD associated with the first multi-AP agent 710. At 756, the first multi-AP agent 710 sends a backhaul STA capability report message indicating the MLO capability of the backhaul STA MLD to the multi-AP controller 705 via the first communication link. In some aspects, the MLO capability may be indicated in the backhaul STA capability report message MLO support TLV. MLO support TLV may indicate the backhaul STA MLD MAC address, the backhaul STA MLD IEEE 802.11be EML capability, the backhaul STA MLD IEEE 802.11be MLD capability, the number of links associated with the backhaul STA MLD, the link ID, the MAC address of the link, the backhaul STA MLD operation category, and the backhaul STA MLD channel number, and other examples.

[0109] Figure 8 A sequence diagram showing another example wireless communication 800 supporting multi-link operation in a multi-AP network. The wireless communication 800 may be in reference to Figure 7 Described multi-AP controller 705, the first multi-AP proxy 710 and the second multi-AP proxy 720 performed between. In various implementations, and Figure 8 The first multi-AP proxy 710 establishes operations 731-735 associated with the second multi-AP proxy 720 backhaul link can be with reference Figure 7 The described operations 731 - 735 are the same or at least similar.

[0110] In some implementations, the first multi-AP agent 710 can provide its front AP MLD, in response to the request from the multi-AP controller 705 MLO configuration information. For example, at 811, the multi-AP controller 705 generates a query for the first multi-AP agent 710 MLO configuration information of the front AP MLD. At 812, the multi-AP controller 705 sends an AP metric query message to the first multi-AP agent 710 via a first communication link. AP metric query message may include a request for the first multi-AP agent 710 to provide or indicate its front AP MLD MLO configuration information. At 813, the first multi-AP agent 710 receives the request, and obtains the MLO configuration information for its front AP MLD. At 814, the first multi-AP agent 710 sends an AP metric response message to the multi-AP controller 705 via a first communication link. AP metric response message may indicate the first multi-AP agent 710 front AP MLD MLO configuration information. In some aspects, the MLO configuration information may be indicated in an MLO Support TLV of an AP Metrics Response message.

[0111] In various implementations, the AP metric query message may also include a request for the first multi-AP agent 710 to provide or indicate the MLO configuration information of its backhaul STA MLD. For example, at 823, the first multi-AP agent 710 receives the request, and obtains the MLO configuration information for its backhaul STA MLD. At 824, the first multi-AP agent 710 sends an AP metric response message to the multi-AP controller 705 via a first communication link. In some implementations, the AP metric response message may include one or more associated non-AP operation TLVs for one or more respective STAs of the first multi-AP agent 710 STA MLD. In some instances, each associated non-AP operation TLV may include or indicate the MLO configuration information of the respective STA of the backhaul STA MLD. For example, each associated non-AP operation TLV may indicate the MAC address of the multi-AP controller 705, the MAC address of the backhaul STA MLD of the respective multi-AP agent, the number of links, the link ID, the operation category of the respective multi-AP agent backhaul STA MLD, the channel number, the presence of a bitmap, a TID bitmap, and the number of TIDs, and other examples. In some other instances, each associated non-AP operation TLV may include or indicate the respective AP in the fronthaul AP MLD and the first multi-AP proxy 710 of the backhaul STA MLD respective STA configuration between. In some other instances, each associated non-AP operation TLV may include or indicate the first multi-AP proxy 710 of the fronthaul AP MLD and backhaul STA MLD associated traffic identifier (TID) to link mapping.

[0112] In some implementations, the first multi-AP agent 710 can be in response to a request from the multi-AP controller 705 to reconfigure one or more TID to link mapping. For example, at 831, the multi-AP controller 705 obtains MLO association information based on the indicated MLO capability. At 832, the multi-AP controller 705 sends a multi-AP policy configuration request message to the first multi-AP agent 710 via a first communication link. Multi-AP policy configuration request message may include an AP MLD TID to link mapping request TLV, the AP MLD TID to link mapping request TLV triggers the multi-link selection process for the first multi-AP agent 710 of the fronthaul AP MLD or the backhaul STA MLD of one or both. In some aspects, the AP MLD TID to link mapping request TLV may indicate the multi-AP controller 705 fronthaul AP MLD MAC address, the first multi-AP agent 710 of the backhaul STA MLD MAC address, the number of links, link ID, and TID bitmap, and other examples. At 833, the first multi-AP agent 710 receives a multi-AP policy configuration request message, the AP MLD TID to link mapping request TLV is decoded, and the first multi-AP agent 710 for the fronthaul AP MLD or backhaul STA MLD TID to link mapping of one or both. At 834, the first multi-AP agent 710 in response to the AP MLD TID to link mapping request TLV, to reconfigure the first multi-AP agent 710 fronthaul APMLD or backhaul STA MLD TID to link mapping of one or both.

[0113] Fig. 9 A flowchart illustrating an example operation 900 of wireless communication for supporting multi-link operation in a multi-AP network is shown. Operation 900 may be performed by a wireless device operating as a multi-AP proxy. In some instances, the multi-AP proxy may be Figure 2 A wireless communication device 200, Figure 3B Multi-AP proxy 304, Figure 6 Multi-AP proxy 620, 630 or 640, or Figure 7Examples of multi-AP proxy 710 and 720. In various implementations, the multi-AP proxy may include a fronthaul AP MLD and a backhaul STA MLD. The fronthaul AP MLD may include multiple APs operating on multiple communication links of a multi-AP network, and the backhaul STA MLD may include multiple STAs operating on multiple communication links of the multi-AP network. In some instances, the fronthaul AP MLD may communicate with the backhaul STAMLD of the downstream multi-AP device through multiple communication links associated with the multi-AP network, and the backhaul STA MLD may communicate with the fronthaul AP MLD of the upstream multi-AP device through multiple communication links associated with the multi-AP network.

[0114] For example, at 902, the multi-AP device sends a device pre-configuration protocol (DPP) configuration request message to the second multi-AP device via a first communication link, and the DPP configuration request message indicates the multi-link operation (MLO) capability of the first multi-AP device. At 904, the multi-AP device receives a DPP configuration response message from the second multi-AP device via a first communication link, and the DPP configuration response message indicates the MLO association information in response to the indicated MLO capability. At 906, the multi-AP device establishes a return path with a third multi-AP device on the first communication link and one or more second communication links based on the MLO association information.

[0115] In some implementations, the MLO capability of the first multi-AP device may be indicated in the DPP configuration object of the DPP configuration request message, and the MLO association information may be indicated in the MLD address field of the DPP configuration object of the DPP configuration response message. In some instances, the first multi-AP device may be a first multi-AP agent, the first multi-AP agent includes a backhaul STAMLD configured to communicate with a third multi-AP device via a first communication link or a second communication link, and the second multi-AP device may be configured to load the first multi-AP device and the third multi-AP device according to the multi-AP communication protocol. AP controller. In some aspects, the third multi-AP device may be a second multi-AP agent, and the second multi-AP agent includes a fronthaul AP MLD configured to communicate with the first multi-AP agent via a first communication link or a second communication link in one or more of the first multi-AP agent STAMLD.

[0116] Fig.10 A flowchart illustrating an example operation 1000 of wireless communication for supporting multi-link operation in a multi-AP network is shown. Operation 1000 may be performed by a wireless device operating as a multi-AP proxy. In some instances, the multi-AP proxy may be Figure 2 A wireless communication device 200, Figure 3B Multi-AP proxy 304, Figure 6 Multi-AP proxy 620, 630 or 640, or Figure 7 Examples of multi-AP proxy 710 and 720. In various implementations, the multi-AP proxy may include a fronthaul AP MLD and a backhaul STA MLD. The fronthaul AP MLD may include multiple APs operating on multiple communication links of a multi-AP network, and the backhaul STA MLD may include multiple STAs operating on multiple communication links of a multi-AP network. In some implementations, the operation 1000 may be performed by reference Fig. 9 Described multi-AP proxy to perform.

[0117] For example, at 1002, the multi-AP device sends a basic service set (BSS) configuration request message to the second multi-AP device via a first communication link, and the BSS configuration request message indicates the MLO capability of the BSS associated with the first multi-AP device. At 1004, the multi-AP device receives a BSS configuration response message from the second multi-AP device via a first communication link, and the BSS configuration response message indicates one or more BSSs associated with a public MLD ID. In some implementations, the MLO capability of the BSS associated with the first multi-AP device may be indicated in the DPP configuration object of the BSS configuration request message, and one or more BSSs associated with a public MLD ID may be indicated in the MLD address field of the DPP configuration object of the BSS configuration response message.

[0118] Fig.11 A flowchart illustrating an example operation 1100 of wireless communication for supporting multi-link operation in a multi-AP network is shown. Operation 1100 may be performed by a wireless device operating as a multi-AP proxy. In some instances, the multi-AP proxy may be Figure 2 A wireless communication device 200, Figure 3B Multi-AP proxy 304, Figure 6 Multi-AP proxy 620, 630 or 640, or Figure 7 Examples of multi-AP proxy 710 and 720. In various implementations, the multi-AP proxy may include a fronthaul AP MLD and a backhaul STA MLD. The fronthaul AP MLD may include multiple APs operating on multiple communication links of a multi-AP network, and the backhaul STA MLD may include multiple STAs operating on multiple communication links of a multi-AP network. In some implementations, the operation 1000 may be performed by reference Fig. 9 Described in the multi-AP proxy to perform.

[0119] For example, at 1102, multiple AP devices receive AP capabilities query messages from multiple AP controllers. At 1104, multiple AP devices send AP capabilities report messages to multiple AP controllers, the AP capabilities report message includes multi-link operation (MLO) support type - length - value (TLV), the MLO supports TLV instructions second multi-AP agent fronthaul AP MLD MLO capabilities.

[0120] Fig.12 A flowchart illustrating an example operation 1200 of wireless communication for supporting multi-link operation in a multi-AP network is shown. Operation 1200 may be performed by a wireless device operating as a multi-AP proxy. In some instances, the multi-AP proxy may be Figure 2 A wireless communication device 200, Figure 3B Multi-AP proxy 304, Figure 6 Multi-AP proxy 620, 630 or 640, or Figure 7 Examples of multi-AP proxy 710 and 720. In various implementations, the multi-AP proxy may include a fronthaul AP MLD and a backhaul STA MLD. The fronthaul AP MLD may include multiple APs operating on multiple communication links of a multi-AP network, and the backhaul STA MLD may include multiple STAs operating on multiple communication links of a multi-AP network. In some implementations, the operation 1000 may be performed by reference Fig. 9 Described multi-AP proxy to perform.

[0121] For example, at 1202, the multi-AP device receives an AP capability query message from a multi-AP controller. At 1204, the multi-AP device sends a backhaul STA capability report message to the multi-AP controller, the backhaul STA capability report message includes an MLO support TLV for indicating the MLO capability of the first multi-AP proxy backhaul STA MLD.

[0122] Fig.13 A flowchart illustrating an example operation 1300 of wireless communication for supporting multi-link operation in a multi-AP network is shown. Operation 1300 may be performed by a wireless device operating as a multi-AP proxy. In some instances, the multi-AP proxy may be Figure 2 A wireless communication device 200, Figure 3B Multi-AP proxy 304, Figure 6 Multi-AP proxy 620, 630 or 640, or Figure 7Examples of multi-AP proxy 710 and 720. In various implementations, the multi-AP proxy may include a fronthaul AP MLD and a backhaul STA MLD. The fronthaul AP MLD may include multiple APs operating on multiple communication links of a multi-AP network, and the backhaul STA MLD may include multiple STAs operating on multiple communication links of a multi-AP network. In some implementations, the operation 1000 may be performed by reference Fig. 9 Described multi-AP proxy to perform.

[0123] For example, at 1302, multiple AP devices receive AP metrics query messages from multiple AP controllers. At 1304, multiple AP devices send AP metrics response messages to multiple AP controllers, the AP metrics response message includes non-AP operation type associated with each STA for the first multi-AP proxy MLD MLD - length - value (TLV). In some implementations, the non-AP operation TLV associated with the respective STA of the backhaul STA MLD may indicate the MLO configuration between the respective STA and the respective AP of the first multi-AP proxy fronthaul AP MLD. In some other implementations, the non-AP operation TLV associated with the backhaul STA MLD may indicate the first multi-AP proxy backhaul STA MLD and the first multi-AP proxy fronthaul AP MLD associated with the first multi-AP traffic identifier (TID) to link mapping.

[0124] Fig.14 1400 is a flowchart illustrating an example operation of wireless communication for supporting multi-link operation in a multi-AP network. Operation 1400 may be performed by a wireless device operating as a multi-AP proxy. In some instances, the multi-AP proxy may be Figure 2 A wireless communication device 200, Figure 3B Multi-AP proxy 304, Figure 6 Multi-AP proxy 620, 630 or 640, or Figure 7 Examples of multi-AP proxy 710 and 720. In various implementations, the multi-AP proxy may include a fronthaul AP MLD and a backhaul STA MLD. The fronthaul AP MLD may include multiple APs operating on multiple communication links of a multi-AP network, and the backhaul STA MLD may include multiple STAs operating on multiple communication links of a multi-AP network. In some implementations, the operation 1000 may be performed by reference Fig. 9 Described multi-AP proxy to perform.

[0125] For example, at 1402, multiple AP devices receive multiple AP policy configuration request messages from multiple AP controllers, the multiple AP policy configuration request message includes AP MLD TID to link mapping request TLV, the AP MLD TID to link mapping request TLV triggers the multi-link selection process for the first multi-AP proxy backhaul STA MLD. At 1404, multiple AP devices respond to APMLD TID to link mapping request TLV to reconfigure TID to link mapping.

[0126] Fig.15 A flowchart illustrating an example operation 1500 of wireless communication for supporting multi-link operation in a multi-AP network is shown. Operation 1500 may be performed by a wireless device operating as a multi-AP proxy. In some instances, the multi-AP proxy may be Figure 2 A wireless communication device 200, Figure 3B Multi-AP proxy 304, Figure 6 Multi-AP proxy 620, 630 or 640, or Figure 7 Examples of multi-AP proxy 710 and 720. In various implementations, the multi-AP proxy may include a fronthaul AP MLD and a backhaul STA MLD. The fronthaul AP MLD may include multiple APs operating on multiple communication links of a multi-AP network, and the backhaul STA MLD may include multiple STAs operating on multiple communication links of a multi-AP network. In some implementations, the operation 1000 may be performed by reference Fig. 9 Described multi-AP proxy to perform.

[0127] For example, at 1502, multiple AP devices receive a query message associated with the STA link metric from the AP controller. At 1504, multiple AP devices send a query response message associated with the STA link metric to the AP controller, the STA link metric query response message associated with the first multi-AP agent fronthaul AP MLD associated with each non-AP MLD client associated non-AP operation type - length - value (TLV).

[0128] Fig.16 A block diagram of an example wireless communication device 1600 is shown. The wireless communication device 1600 may be configured to perform respective references Fig. 9 , Fig.10 , Fig.11 , Fig.12 , Fig.13 , Fig.14 and Fig.15 The operations 900, 1000, 1100, 1200, 1300, 1400, and 1500 described above may be performed by the wireless communication device 1600. In some implementations, the wireless communication device 1600 may be Figure 6In some other implementations, the wireless communication device 1600 may be Figure 3A Multi-AP controller 302 or Figure 7 and Figure 8 Example implementation of a multi-AP controller 705. More specifically, the wireless communication device 1600 may be a chip, a SoC, a chipset, a package, or a device including at least one processor and at least one modem (eg, a Wi-Fi (IEEE 802.11) modem or a cellular modem).

[0129] The wireless communication device 1600 includes a receiving component 1610, a communication manager 1620, and a sending component 1630. The communication manager 1620 includes a multi-link operation (MLO) component 1621, a multi-AP controller component 1622, and a loading component 1623. Portions of one or more components of the components 1621-1623 may be implemented at least in part in hardware or firmware. In some implementations, one or more components of the components 1621-1623 are implemented at least in part as stored in a memory (such as Figure 2 For example, portions of one or more of components 1621-1623 may be implemented as software that can be executed by a processor such as Figure 2 Non-transitory instructions (or “codes”) executed by the processor 206 of the processor to perform the functions or operations of the respective components.

[0130] The receiving component 1610 is configured to receive an RX signal from one or more multi-AP agents, and the transmitting component 1630 is configured to send a TX signal to one or more multi-AP agents. The communication manager 1620 is configured to manage wireless communications with one or more multi-AP agents. The MLO component 1621 can establish or set MLO on multiple communication links associated with a multi-AP network. In some cases, the MLO component 1621 may also insert one or more of the MLO capabilities, MLO association information, or MLO configuration information into a multi-AP message (such as IEEE 1905.1 management frame or message) exchanged through multiple communication links of a multi-AP network.

[0131] Multi-AP controller component 1622 can perform various operations associated with the multi-AP network, including (but not limited to) finding multiple AP agents near the multi-AP agent configuration, obtain measurement results from the multi-AP agent near the multi-AP agent, and obtain reports from the multi-AP agent near the multi-AP agent.

[0132] Loading component 1623 can be found on a multi-AP network multi-AP agent. In some implementations, the loading component 1623 can be loaded according to the DPP found multi-AP agent. In some other implementations, the loading component 1623 can be loaded according to the multi-AP protocol found multi-AP agent.

[0133] Fig.17 A block diagram of an example wireless communication device 1700 is shown. The wireless communication device 1700 may be configured to perform respective references to Fig. 9 , Fig.10 , Fig.11 , Fig.12 , Fig.13 , Fig.14 and Fig.15 The operations 900, 1000, 1100, 1200, 1300, 1400, and 1500 described above may be performed in a manner similar to the operations 900, 1000, 1100, 1200, 1300, 1400, and 1500 described above. In some implementations, the wireless communication device 1700 may be Figure 6 In some other implementations, the wireless communication device 1700 may be Figure 3B Multi-AP proxy 304, Figure 7 and Figure 8 The first multi-AP proxy 710, or Figure 7 and Figure 8 The example implementation of the second multi-AP proxy 720. More specifically, the wireless communication device 1700 may be a chip, a SoC, a chipset, a package, or a device including at least one processor and at least one modem (eg, a Wi-Fi (IEEE 802.11) modem or a cellular modem).

[0134] The wireless communication device 1700 includes a receiving component 1710, a communication manager 1720, and a sending component 1730. The communication manager 1720 includes a multi-link operation (MLO) component 1721, a multi-AP proxy component 1722, and a TID to link mapping component 1723. Portions of one or more components in the components 1721-1723 may be implemented at least in part in hardware or firmware. In some implementations, one or more components in the components 1721-1723 are implemented at least in part as stored in a memory (such as Figure 2 For example, portions of one or more of components 1721-1723 may be implemented as software that can be executed by a processor such as Figure 2 Non-transitory instructions (or “codes”) executed by the processor 206 of the processor to perform the functions or operations of the respective components.

[0135] The receiving component 1710 is configured to receive an RX signal from a multi-AP controller or one or more other multi-AP agents, and the transmitting component 1730 is configured to send a TX signal to a multi-AP controller or one or more other multi-AP agents. The communication manager 1720 is configured to manage wireless communications with multiple AP controllers and one or more other multi-AP agents. The MLO component 1721 can establish or set a multi-link operation on a communication link associated with a multi-AP network. In some instances, the MLO component 1721 may also insert one or more of the MLO capabilities, MLO association information, or MLO configuration information into a multi-AP message (such as an IEEE 1905.1 management frame or message) exchanged through one or more communication links of a multi-AP network.

[0136] Multi-AP proxy component 1722 can perform various operations associated with the multi-AP network, including (but not limited to) with one or more other multi-AP agent to establish a backhaul link capable of MLO, provide a measurement result in response to a request from a multi-AP controller, and provide a report in response to a request from a multi-AP controller.

[0137] TID to link mapping component 1723 can determine or obtain the business flow associated with each multi-AP proxy TID and multi-AP network is preconfigured or assigned to the respective multi-AP proxy multiple communication links between the mapping. In some instances, TID to link mapping component 1723 can also be based on changes in the preconfigured or assigned to the respective multi-AP proxy communication link to update the mapping.

[0138] Fig.18A An example MLD Configuration Report TLV 1800A suitable for use in a BSS Configuration Result message is shown. The MLD Configuration Report TLV 1800A is shown to include fields for indicating at least the number of MLDs reported in the BSS Configuration Result message, the MLD MAC address, the number of BSSs under the control of the MLD, and the MAC address of the BSS, among other examples.

[0139] Fig.18B An example MLO Support TLV 1800B suitable for use in an AP Capability Report message, a backhaul STA Capability Report message, or a Client Capability Report message is shown. The MLO Support TLV 1800B is shown to include fields indicating at least the following: MLD MAC address, IEEE 802.11be EML capability, IEEE 802.11be MLD capability, the number of links associated with the MLD, link ID, MAC address of the link, operation class, and channel number, among other examples.

[0140] Fig.18CAn example associated non-AP MLD operation TLV 1800C suitable for use in an AP metric response message or an associated STA link metric response message is shown. The associated non-AP MLD operation TLV 1800C is shown to include fields indicating at least the following: an AP MLD MAC address, an associated non-AP MLD MAC address, a number of links associated with the AP MLD, a link ID, a MAC address of an associated non-AP MLD corresponding to a link, an operation class, a channel number, a presence bitmap, a TID bitmap, and a number of TIDs, as well as other examples.

[0141] Fig.18D An example backhaul multi-link steering request TLV1800D suitable for use in a backhaul steering request message is shown. Backhaul multi-link steering request TLV 1800D is shown to include at least one field indicating the following items: a MAC address of a non-AP MLD associated with a backhaul operated by a multi-AP proxy, a MAC address for an associated AP MLD, a MAC address of an AP MLD attached to an AP for association, the number of links, a link ID, a MAC address of an AP corresponding to a link, an operation category, a channel number, a bitmap, a TID bitmap, and the number of TIDs, and other examples.

[0142] Fig.18E An example AP MLD TID to link mapping request TLV 1800E is shown for use in a multi-AP policy configuration request message. AP MLD TID to link mapping request TLV 1800E is shown to include fields indicating at least the following items: AP MLD MAC address, non-AP MLD MAC address, the number of links, link ID, and TID bitmap, as well as other examples.

[0143] Examples of implementations are described in the following example aspects: 1. A first multi-access point (Multi-AP) device, comprising: One or more interfaces, which are configured as: Output device pre-configuration protocol (DPP) to the second multi-AP device through a first communication link to configure a request message, the DPP configuration request message indicates the multi-link operation (MLO) capability of the first multi-AP device; and Obtaining a DPP configuration response message from the second multi-AP device via the first communication link, the DPP configuration response message indicating the MLO association information in response to the indicated MLO capability; and a processing system coupled to the one or more interfaces, the processing system configured to: According to the MLO association information, a return path with a third multi-AP device is established on the first communication link and one or more second communication links. 2. The first multi-AP device according to aspect 1, wherein: The MLO capability of the first multi-AP device is indicated in the DPP configuration object of the DPP configuration request message; and The MLO association information is indicated in a multi-link device (MLD) address field of a DPP configuration object of the DPP configuration response message. 3. According to any one or more aspects of aspect 1-aspect 2, the first multi-AP device, wherein the one or more interfaces are further configured as: Output basic service set (BSS) configuration request message to the second multi-AP device through the first communication link, the BSS configuration request message indicates the MLO capability of the BSS associated with the first multi-AP device; and Obtain a BSS configuration response message from the second multi-AP device through the first communication link, the BSS configuration response message indicates one or more BSSs associated with a public multi-link device (MLD) identifier (ID). 4. The first multi-AP device according to aspect 3, wherein: The MLO capability of the BSS associated with the first multi-AP device is indicated in the DPP configuration object of the BSS configuration request message; and One or more BSSs associated with a common MLD ID are indicated in the MLD Address field of the DPP Configuration object of the BSS Configuration Response message. 5. The first multi-AP device according to any one or more aspects of aspect 1 to aspect 4, wherein: The first multi-AP device is a first multi-AP proxy, the first multi-AP proxy includes a backhaul station (STA) MLD configured to communicate with the third multi-AP device through one or more of the first communication link or the second communication link; The second multi-AP device is a multi-AP controller, the multi-AP controller is configured to load the first multi-AP device and the third multi-AP device according to the multi-AP communication protocol; and The third multi-AP device is a second multi-AP proxy, the second multi-AP proxy includes a fronthaul AP MLD configured to communicate with the first multi-AP proxy backhaul STA MLD through one or more of the first communication link or the second communication link. 6. The first multi-AP device according to aspect 5, wherein the one or more interfaces are further configured as: Get AP capability query message from the multi-AP controller; and The AP capability report message is output to the multi-AP controller, the AP capability report message includes MLO support type - length - value (TLV) for indicating the MLO capability of the second multi-AP agent fronthaul AP MLD. 7. According to any one or more aspects of aspect 5-aspect 6, the first multi-AP device, wherein the one or more interfaces are further configured as: Get AP capability query message from the multi-AP controller; and Output backhaul STA capability report message to the multi-AP controller, the backhaul STA capability report message includes MLO support TLV for indicating the MLO capability of the backhaul STA MLD of the first multi-AP agent. 8. According to any one or more aspects of aspect 5-aspect 6, the first multi-AP device, wherein the one or more interfaces are further configured to: Obtain AP metric query message from the multi-AP controller; and Output AP measurement response message to the multi-AP controller, the AP measurement response message includes the first multi-AP proxy backhaul STAMLD associated non-AP operation type of each STA - length - value (TLV). 9. According to aspect 8, the first multi-AP device, wherein the non-AP operation TLV associated with the respective STA of the backhaul STA MLD indicates the respective STA of the first multi-AP agent fronthaul AP MLD MLO configuration between the respective STA and the respective AP. 10. According to aspect 8, the first multi-AP device, wherein the non-AP operation TLV associated with the backhaul STA MLD indicates the backhaul STAMLD of the first multi-AP proxy and the first multi-AP proxy fronthaul AP MLD associated traffic identifier (TID) to link mapping. 11. The first multi-AP device according to aspect 10, wherein the one or more interfaces are further configured to: Get more AP policy configuration request message from the multi-AP controller, the multi-AP policy configuration request message includes AP MLD TID to link mapping request TLV, the AP MLD TID to link mapping request TLV trigger for the first multi-AP proxy backhaul STA MLD multi-link selection process. 12. The first multi-AP device according to aspect 11, wherein the processing system is further configured to: The TID-to-link mapping is reconfigured in response to the AP MLD TID-to-link mapping request TLV. 13. According to any one or more aspects of aspect 5-aspect 12, the first multi-AP device, wherein the one or more interfaces are further configured to: Obtaining the associated STA link metric query message from the multi-AP controller; and To the multi-AP controller output associated STA link metric query response message, the associated STA link metric query response message includes a non-AP operation type associated with each non-AP MLD client associated with the first multi-AP agent forward AP MLD - length - value (TLV). 14, according to aspect 13 of the first multi-AP device, wherein the non-AP MLD client associated with the respective non-AP operation TLV instructions in the respective non-AP MLD client and the first multi-AP agent fronthaul MLO configuration between AP MLD. 15, according to any one or more aspects of aspect 12-aspect 14 of the first multi-AP device, wherein the non-AP MLD client associated with the respective non-AP operation TLV indication and the respective non-AP MLD client and the first multi-AP agent fronthaul AP MLD associated traffic identifier (TID) to link mapping. 16. The first multi-AP device according to aspect 15, wherein the one or more interfaces are further configured to: Get more AP policy configuration request message from the multi-AP controller, the multi-AP policy configuration request message includes AP MLD TID to link mapping request TLV, the AP MLD TID to link mapping request TLV triggers the multi-link selection process for the first multi-AP agent fronthaul AP MLD. 17. The first multi-AP device according to any one or more of aspects 15 to 16, wherein the processing system is further configured to: The TID-to-link mapping is reconfigured in response to the AP MLD TID-to-link mapping request TLV. 18. According to any one or more aspects of aspect 5-aspect 17, the first multi-AP device, wherein the one or more interfaces are further configured to: From the multi-AP controller to obtain one or more link identifiers (ID), each link ID indicates the first multi-AP proxy backhaul STA MLD and the first multi-AP proxy fronthaul AP MLD for multi-link communication between the respective communication links. 19. A method for wireless communication by a first multi-AP device, comprising: Send a device pre-configuration protocol (DPP) configuration request message to the second multi-AP device via a first communication link, the DPP configuration request message indicates the multi-link operation (MLO) capability of the first multi-AP device; Receiving a DPP configuration response message from the second multi-AP device via the first communication link, the DPP configuration response message indicates the MLO association information in response to the indicated MLO capability; and According to the MLO association information, a return path with a third multi-AP device is established on the first communication link and one or more second communication links. 20. The method according to aspect 19, wherein: The MLO capability of the first multi-AP device is indicated in the DPP configuration object of the DPP configuration request message; and The MLO association information is indicated in a multi-link device (MLD) address field of a DPP configuration object of the DPP configuration response message. 21. The method according to any one or more of aspects 19 to 20, further comprising: Send a basic service set (BSS) configuration request message to the second multi-AP device through the first communication link, the BSS configuration request message indicates the MLO capability of the BSS associated with the first multi-AP device; and The BSS configuration response message is received from the second multi-AP device through the first communication link, and the BSS configuration response message indicates one or more BSSs associated with a public multi-link device (MLD) identifier (ID). 22. The method according to claim 21, wherein: The MLO capability of the BSS associated with the first multi-AP device is indicated in the DPP configuration object of the BSS configuration request message; and One or more BSSs associated with a common MLD ID are indicated in the MLD Address field of the DPP Configuration object of the BSS Configuration Response message. 23. The method according to any one or more of aspects 19 to 22, wherein: The first multi-AP device is a first multi-AP proxy, the first multi-AP proxy includes a backhaul station (STA) MLD configured to communicate with the third multi-AP device through one or more of the first communication link or the second communication link; The second multi-AP device is a multi-AP controller, the multi-AP controller is configured to load the first multi-AP device and the third multi-AP device according to the multi-AP communication protocol; and The third multi-AP device is a second multi-AP proxy, the second multi-AP proxy includes a fronthaul AP MLD configured to communicate with the first multi-AP proxy backhaul STA MLD through one or more of the first communication link or the second communication link. 24. The method according to aspect 23, further comprising: Receiving an AP metric query message from the multi-AP controller; and The AP metric response message is sent to the multi-AP controller, the AP metric response message includes the associated non-AP operation type - length - value (TLV) for each STA of the first multi-AP proxy backhaul STA MLD. 25. The method according to aspect 24, wherein the non-AP operation TLV associated with the respective STA of the backhaul STA MLD indicates the MLO configuration between the respective STA and the respective AP of the fronthaul AP MLD associated with the first multi-AP agent. 26, according to aspect 25 of the method, wherein the backhaul STA MLD associated non-AP operation TLV indication and the first multi-AP proxy backhaul STA MLD and the first multi-AP proxy fronthaul AP MLD associated traffic identifier (TID) to link mapping. 27. The method according to aspect 26, further comprising: Receives multiple AP policy configuration request message from the multi-AP controller, the multi-AP policy configuration request message includes AP MLD TID to link mapping request TLV, the AP MLD TID to link mapping request TLV triggers the multi-link selection process for the first multi-AP proxy backhaul STA MLD. 28. The method according to aspect 27, further comprising: The TID-to-link mapping is reconfigured in response to the AP MLD TID-to-link mapping request TLV. 29. The method according to any one or more of aspects 23 to 28, further comprising: Receive the associated STA link metric query message from the multi-AP controller; and Sends an associated STA link metric query response message to the multi-AP controller, the associated STA link metric query response message includes an associated non-AP operation type - length - value (TLV) for each non-AP MLD client associated with the first multi-AP agent forward AP MLD. 30. The method according to aspect 29, wherein the non-AP MLD client associated with the respective non-AP operation TLV indicates the MLO configuration between the respective non-AP MLD client and the first multi-AP agent fronthaul AP MLD. 31. An apparatus for wireless communication, comprising means for performing the method according to any one or more of aspects 19 to 30. 32. A non-transitory computer-readable storage medium storing instructions, which, when executed by a processing system of a device, cause the device to perform operations according to any one or more of aspects 19 to 30.

[0144] As used herein, a phrase referencing "at least one of" or "one or more of" a list of items refers to any combination of those items, including single members. For example, "at least one of a, b, or c" is intended to cover the possibilities of: only a, only b, only c, a combination of a and b, a combination of a and c, a combination of b and c, and a combination of a, b, and c. As used herein, "based on" is intended to be interpreted in an inclusive sense unless expressly indicated otherwise. For example, "based on" may be used interchangeably with "based at least in part on," unless expressly indicated otherwise. Specifically, unless a phrase refers to "based only on 'a'" or an equivalent in context, whether "based on 'a'" or "based at least in part on 'a'" may be based on "a" alone or on a combination of "a" and one or more other factors, conditions, or information.

[0145] The various illustrative components, logic, logic blocks, modules, circuits, operations, and algorithmic processes described in connection with the implementations disclosed herein may be implemented as electronic hardware, firmware, software, or a combination of hardware, firmware, or software, including the structures disclosed in this specification and their structural equivalents. The interchangeability of hardware, firmware, and software has been generally described in terms of functionality, as well as in the various illustrative components, blocks, modules, circuits, and processes described herein. Whether such functionality is implemented in hardware, firmware, or software depends on the specific application and the design constraints imposed on the overall system.

[0146] Various modifications to the implementations described in this disclosure may be apparent to those of ordinary skill in the art, and the general principles defined herein may be applied to other implementations without departing from the spirit or scope of this disclosure. Therefore, the claims are not intended to be limited to the implementations shown herein, but are to be given the widest scope consistent with this disclosure, the principles disclosed herein, and the novel features.

[0147] In addition, various features described in this specification in the context of separate implementations may also be implemented in combination in a single implementation. Conversely, various features described in the context of a single implementation may also be implemented in multiple implementations separately or in any suitable sub-combination. Thus, although features may be described herein as functioning in a particular combination, and even initially claimed as such, one or more features from a claimed combination may in some cases be deleted from the combination, and a claimed combination may be directed to a sub-combination or a variation of a sub-combination.

[0148] Similarly, although operations are depicted in a specific order in the figure, this should not be understood as requiring such operations to be performed in the specific order shown or in a sequential order, or to perform all operations shown to achieve the desired result. Further, the accompanying drawings can schematically depict one or more example operations in the form of a flow chart or a program schematic diagram. However, other operations not depicted can be incorporated into the example process not shown in the figure. For example, one or more additional operations can be performed before, after, simultaneously or between any operations in the operations shown. In some cases, multitasking and parallel processing may be advantageous. In addition, the separation of each system component in the implementation described above should not be understood as requiring such separation in all implementations, and it should be understood that the described program components and system can usually be integrated together in a single software product, or be encapsulated in multiple software products.

Claims

1. A first multi-access point (multi-AP) device, comprising: One or more interfaces, which are configured as: Output device pre-configuration protocol (DPP) to the second multi-AP device through a first communication link to configure a request message, the DPP configuration request message indicates the multi-link operation (MLO) capability of the first multi-AP device; as well as Obtaining a DPP configuration response message from the second multi-AP device through the first communication link, the DPP configuration response message indicating the MLO association information in response to the indicated MLO capability; as well as a processing system coupled to the one or more interfaces, the processing system configured to: According to the MLO association information, a return path with a third multi-AP device is established on the first communication link and one or more second communication links.

2. The first multi-AP device according to claim 1, wherein: The MLO capability of the first multi-AP device is indicated in the DPP configuration object of the DPP configuration request message; and The MLO association information is indicated in a multi-link device (MLD) address field of a DPP configuration object of the DPP configuration response message.

3. The first multi-AP device according to claim 1, wherein: The one or more interfaces are further configured to: Output basic service set (BSS) configuration request message to the second multi-AP device through the first communication link, the BSS configuration request message indicates the MLO capability of the BSS associated with the first multi-AP device; as well as Obtain a BSS configuration response message from the second multi-AP device through the first communication link, the BSS configuration response message indicates one or more BSSs associated with a public multi-link device (MLD) identifier (ID).

4. The first multi-AP device according to claim 3, wherein: The MLO capability of the BSS associated with the first multi-AP device is indicated in the DPP configuration object of the BSS configuration request message; as well as One or more BSSs associated with a common MLD ID are indicated in the MLD Address field of the DPP Configuration object of the BSS Configuration Response message.

5. The first multi-AP device according to claim 1, wherein: The first multi-AP device is a first multi-AP proxy, the first multi-AP proxy includes a backhaul station (STA) MLD configured to communicate with the third multi-AP device through one or more of the first communication link or the second communication link; The second multi-AP device is a multi-AP controller, the multi-AP controller is configured to load the first multi-AP device and the third multi-AP device according to the multi-AP communication protocol; and The third multi-AP device is a second multi-AP proxy, the second multi-AP proxy includes a fronthaul AP MLD configured to communicate with the first multi-AP proxy backhaul STA MLD through one or more of the first communication link or the second communication link.

6. The first multi-AP device according to claim 5, wherein: The one or more interfaces are further configured to: Obtaining AP capability query message from the multi-AP controller; and The AP capability report message is output to the multi-AP controller, the AP capability report message includes MLO support type - length - value (TLV) for indicating the MLO capability of the second multi-AP agent fronthaul AP MLD.

7. The first multi-AP device according to claim 5, wherein: The one or more interfaces are further configured to: Obtaining AP capability query message from the multi-AP controller; and Output backhaul STA capability report message to the multi-AP controller, the backhaul STA capability report message includes MLO support TLV for indicating the MLO capability of the backhaul STA MLD of the first multi-AP agent.

8. The first multi-AP device according to claim 5, wherein: The one or more interfaces are further configured to: Obtaining an AP metric query message from the multi-AP controller; as well as Output AP measurement response message to the multi-AP controller, the AP measurement response message includes the first multi-AP proxy backhaul STAMLD associated non-AP operation type of each STA - length - value (TLV).

9. The first multi-AP device according to claim 8, wherein: For the backhaul STA MLD respective STA associated non-AP operation TLV instructions in the first multi-AP agent fronthaul AP MLD respective STA and respective AP MLO configuration between.

10. The first multi-AP device according to claim 8, wherein: For the backhaul STA MLD associated non-AP operation TLV instructions and the first multi-AP proxy of the backhaul STAMLD and the first multi-AP proxy fronthaul APMLD associated traffic identifier (TID) to link mapping.

11. The first multi-AP device according to claim 10, wherein: The one or more interfaces are further configured to: Get more AP policy configuration request message from the multi-AP controller, the multi-AP policy configuration request message includes APMLD TID to link mapping request TLV, the AP MLD TID to link mapping request TLV trigger for the first multi-AP proxy backhaul STA MLD multi-link selection process.

12. The first multi-AP device according to claim 11, wherein: The processing system is also configured to: The TID-to-link mapping is reconfigured in response to the AP MLD TID-to-link mapping request TLV.

13. The first multi-AP device according to claim 5, wherein: The one or more interfaces are further configured to: Obtaining the associated STA link metric query message from the multi-AP controller; as well as To the multi-AP controller output associated STA link metric query response message, the associated STA link metric query response message includes a non-AP operation type associated with each non-AP MLD client associated with the first multi-AP agent forward AP MLD - length - value (TLV).

14. The first multi-AP device according to claim 13, wherein: For each non-AP MLD client associated with the non-AP operation TLV instructions respective non-AP MLD client and the MLO configuration between the first multi-AP agent fronthaul AP MLD.

15. The first multi-AP device according to claim 13, wherein: For each non-AP MLD client associated with the non-AP operation TLV instructions and the respective non-AP MLD client and the first multi-AP proxy traffic identifier (TID) associated with the fronthaul AP MLD to link mapping.

16. The first multi-AP device according to claim 15, wherein: The one or more interfaces are further configured to: Get more AP policy configuration request message from the multi-AP controller, the multi-AP policy configuration request message includes APMLD TID to link mapping request TLV, the AP MLD TID to link mapping request TLV triggers the multi-link selection process for the first multi-AP agent fronthaul AP MLD.

17. The first multi-AP device according to claim 16, wherein: The processing system is also configured to: The TID-to-link mapping is reconfigured in response to the AP MLD TID-to-link mapping request TLV.

18. The first multi-AP device according to claim 5, wherein: The one or more interfaces are further configured to: From the multi-AP controller to obtain one or more link identifiers (ID), each link ID indicates the first multi-AP proxy backhaul STA MLD and the first multi-AP proxy fronthaul AP MLD for multi-link communication between the respective communication links.

19. A method for wireless communication by a first multi-AP device, comprising: Send a device pre-configuration protocol (DPP) configuration request message to the second multi-AP device via a first communication link, the DPP configuration request message indicates the multi-link operation (MLO) capability of the first multi-AP device; Receiving a DPP configuration response message from the second multi-AP device via the first communication link, the DPP configuration response message indicates the MLO association information in response to the indicated MLO capability; and According to the MLO association information, a return path with a third multi-AP device is established on the first communication link and one or more second communication links.

20. The method of claim 19, wherein: The MLO capability of the first multi-AP device is indicated in the DPP configuration object of the DPP configuration request message; and The MLO association information is indicated in a multi-link device (MLD) address field of a DPP configuration object of the DPP configuration response message.

21. The method of claim 19, further comprising: Send a basic service set (BSS) configuration request message to the second multi-AP device through the first communication link, the BSS configuration request message indicates the MLO capability of the BSS associated with the first multi-AP device; as well as The BSS configuration response message is received from the second multi-AP device through the first communication link, and the BSS configuration response message indicates one or more BSSs associated with a public multi-link device (MLD) identifier (ID).

22. The method of claim 21, wherein: The MLO capability of the BSS associated with the first multi-AP device is indicated in the DPP configuration object of the BSS configuration request message; and One or more BSSs associated with the common MLD ID are indicated in the MLD Address field of the DPP Configuration object of the BSS Configuration Response message.

23. The method of claim 19, wherein: The first multi-AP device is a first multi-AP proxy, the first multi-AP proxy includes a backhaul station (STA) MLD configured to communicate with the third multi-AP device through one or more of the first communication link or the second communication link; The second multi-AP device is a multi-AP controller, the multi-AP controller is configured to load the first multi-AP device and the third multi-AP device according to the multi-AP communication protocol; and The third multi-AP device is a second multi-AP proxy, the second multi-AP proxy includes a fronthaul AP MLD configured to communicate with the first multi-AP proxy backhaul STA MLD through one or more of the first communication link or the second communication link.

24. The method according to claim 23, further comprising: Receiving an AP metric query message from the multi-AP controller; as well as AP measurement response message is sent to the multi-AP controller, the AP measurement response message includes the associated non-AP operation type - length - value (TLV) for each STA of the backhaul STA MLD of the first multi-AP proxy.

25. The method according to claim 24, wherein: For the backhaul STAMLD respective STA associated non-AP operation TLV instructions in the first multi-AP proxy associated fronthaul AP MLD respective STA and respective AP MLO configuration between.

26. The method according to claim 25, wherein: For the backhaul STA MLD associated non-AP operation TLV instructions and the first multi-AP proxy of the backhaul STAMLD and the first multi-AP proxy fronthaul AP MLD associated traffic identifier (TID) to link mapping.

27. The method according to claim 26, further comprising: Receives multiple AP policy configuration request message from the controller, the multi-AP policy configuration request message includes APMLD TID to link mapping request TLV, the AP MLD TID to link mapping request TLV triggers the multi-link selection process for the first multi-AP proxy backhaul STA MLD.

28. The method according to claim 27, further comprising: The TID-to-link mapping is reconfigured in response to the AP MLD TID-to-link mapping request TLV.

29. The method of claim 23, further comprising: Receive the associated STA link metric query message from the multi-AP controller; as well as Sends an associated STA link metric query response message to the multi-AP controller, the associated STA link metric query response message includes an associated non-AP operation type - length - value (TLV) for each non-AP MLD client associated with the first multi-AP agent forward AP MLD.

30. The method of claim 29, wherein: For each non-AP MLD client associated with the non-AP operation TLV instructions in the respective non-AP MLD client and the first multi-AP agent MLO configuration between the fronthaul AP MLD.

Images