Multi-user (MU) communications in wireless mesh networks

Abstract

The present disclosure provides systems, methods, and apparatus, including computer programs encoded on computer storage media, for implementing multi-user (MU) communications in a wireless mesh network. A first mesh node or a network management unit can collect information from various mesh nodes and form MU association groups based on the information. The MU association groups can include a MU group leader that coordinates MU group communications to or from member mesh nodes in the MU association group. For example, the MU group leader can coordinate orthogonal frequency division multiple access (OFDMA) resource unit allocations, or MU multiple-input multiple-output (MU-MIMO) spatial stream configurations, among others. Different MU association groups can be formed for uplink traffic or downlink traffic. The creation of MU association groups can enable the wireless mesh network to realize the benefits of MU group communications within the flexible topology of a mesh environment.

Description

[0001] Cross-reference to related applications

[0002] This patent application claims priority to Indian Provisional Patent Application No. 202021028332, filed on July 3, 2020, entitled “MULTI-USER (MU) COMMUNICATION INA WIRELESS MESH NETWORK”, which has been assigned to the assignee of this application. The disclosure of that earlier application is considered part of this patent application and is incorporated herein by reference. Technical Field

[0003] Various aspects of this disclosure generally relate to wireless communications, including multi-user (MU) communications in a wireless mesh network.

[0004] Related technical descriptions

[0005] A Wireless Local Area Network (WLAN) can be formed by one or more wireless access points (APs) that provide a shared wireless communication medium for use by multiple client devices (also known as wireless stations (STAs)). The basic building block of a WLAN conforming to the IEEE 802.11 family of standards is the Basic Service Set (BSS). The infrastructure BSS (IBSS) is managed by an AP that provides distribution and access functions to associated STAs. The AP periodically broadcasts beacon frames to enable any STA within the AP's wireless range to establish or maintain a communication link with the WLAN. Multiple APs can form an Extended Service Set (ESS), which is a collection of infrastructure BSSs managed by multiple APs.

[0006] The IEEE 802.11 standard family also supports the creation of wireless mesh networks. Wireless mesh networks can offer advantageous attributes in terms of quality of service, robustness, range extension, and density. A wireless mesh network comprises mesh nodes forming a mesh BSS (MBSS). The difference between an MBSS and an IBSS is that each mesh node provides distribution and access functions to other associated mesh nodes within the wireless mesh network. Each mesh node can include a mesh STA, which is a logical architectural component that implements the mesh protocol to communicate with other mesh STAs in the MBSS. For example, a mesh STA establishes a wireless link with neighboring mesh STAs to form a mesh topology, where these mesh STAs can communicate with each other via a wireless communication medium.

[0007] Overview

[0008] The systems, methods, and apparatus disclosed herein each have several innovative aspects, and no single aspect is solely responsible for the desired properties disclosed herein.

[0009] One innovative aspect of the subject matter described in this disclosure can be implemented as a method for wireless communication. The method may include: communicating in a wireless mesh network comprising a plurality of mesh nodes. The method may include: establishing at least a first multi-user (MU) association group, the first MU association group comprising a first mesh node and one or more peer mesh nodes among the plurality of mesh nodes. The first MU association group enables the first mesh node to act as an MU group leader to allocate wireless channel resources for MU communication between the first mesh node forming the first MU association group and at least a subset of the one or more peer mesh nodes.

[0010] Another innovative aspect of the subject matter described in this disclosure can be implemented as a method for wireless communication by a first mesh node in a wireless mesh network. The method may include: the first mesh node operating as a MU group leader in a first MU association group, the first MU association group including the first mesh node and one or more peer mesh nodes in the wireless mesh network. The method may also include: the first mesh node allocating wireless channel resources for MU group communication between the first mesh node forming the first MU association group and at least a subset of the one or more peer mesh nodes.

[0011] Another innovative aspect of the subject matter described in this disclosure can be implemented as a method performed by a first mesh node in a wireless mesh network. The method may include: communicating with multiple mesh nodes in the wireless mesh network. The method may include: receiving configuration for at least a first MU association group, the first MU association group including a second mesh node acting as the MU group leader and at least the first mesh node. The method may include: using wireless channel resources managed by the second mesh node to transmit a portion of the first MU group communication to the second mesh node. The first MU group communication may include transmissions from one or more mesh nodes.

[0012] Another innovative aspect of the subject matter described in this disclosure can be implemented as a first mesh node. The first mesh node may include at least one modem configured to communicate in a wireless mesh network comprising a plurality of mesh nodes. The first mesh node may include a processing system configured to establish at least a first MU association group, the first MU association group comprising the first mesh node and one or more peer mesh nodes among the plurality of mesh nodes. The first MU association group enables the first mesh node to act as an MU group leader to allocate wireless channel resources for MU communication between the first mesh node forming the first MU association group and at least a subset of the one or more peer mesh nodes.

[0013] Another innovative aspect of the subject matter described in this disclosure can be implemented as a first mesh node. The first mesh node may include at least one modem configured to operate as a MU group leader in a first MU association group, which includes the first mesh node and one or more peer mesh nodes in the wireless mesh network. The first mesh node may include a processing system configured to allocate wireless channel resources for MU group communication between the first mesh node forming the first MU association group and at least a subset of the one or more peer mesh nodes.

[0014] Another innovative aspect of the subject matter described in this disclosure can be implemented as a first mesh node. The first mesh node may include at least one modem configured to communicate with a plurality of mesh nodes in the wireless mesh network. The at least one modem may be configured to obtain a configuration for at least a first MU association group, the first MU association group including a second mesh node acting as a MU group leader and at least the first mesh node. The first mesh node may include a processing system configured to manage the first MU group communication of the at least one modem according to the configuration. The at least one modem may be configured to output a portion of the first MU group communication for transmission to the second mesh node using wireless channel resources managed by the second mesh node. The first MU group communication may include transmissions from one or more mesh nodes.

[0015] Details of one or more aspects of the subject matter described in this disclosure are set forth in the accompanying drawings and the following description. However, the drawings illustrate only some typical aspects of this disclosure and are therefore not intended to limit its scope. Other features, aspects, and advantages will become apparent from the description, drawings, and claims. Brief description of the attached diagram

[0017] Figure 1 A system diagram of an example wireless mesh network is shown.

[0018] Figure 2 A system diagram is shown in which mesh nodes of an example wireless mesh network can achieve connectivity with non-mesh networks.

[0019] Figure 3A An example conceptual diagram of Orthogonal Frequency Division Multiplexing (OFDM) is shown.

[0020] Figure 3B An example conceptual diagram of multi-user (MU) orthogonal frequency division multiple access (OFDMA) is shown.

[0021] Figure 3C An example conceptual diagram of a MU-MIMO (Multiple-Input Multiple-Output) is shown.

[0022] Figure 4 This illustrates an example MU role that a mesh node might have in a wireless mesh network.

[0023] Figure 5 An example wireless mesh network and an example MU associated group are shown.

[0024] Figure 6 An overview of an example process for forming MU association groups is shown.

[0025] Figure 7 This illustrates a detailed example process by which mesh nodes or network management units can form different MU association groups.

[0026] Figure 8 Example traffic conditions in an example wireless mesh network are shown, and these example traffic conditions are used to describe different considerations when forming MU association groups.

[0027] Figure 9 An example wireless mesh network is shown, where MU association groups can be associated with hop counts to the mesh gate.

[0028] Figure 10 Another example wireless mesh network and an example MU association group associated with hop counts to mesh gating are shown.

[0029] Figure 11 A conceptual diagram of an example MU association group setup or configuration message is shown.

[0030] Figure 12 A block diagram of an example wireless communication device is shown.

[0031] Figure 13 A block diagram of an example mesh node is shown.

[0032] Figure 14 A flowchart illustrating an example process for implementing MU communication in a wireless mesh network is shown.

[0033] Figure 15 A flowchart illustrating an example process for a mesh node used to support MU communication in a wireless mesh network is shown.

[0034] Figure 16 A flowchart illustrating another example process for a mesh node used to support MU communication in a wireless mesh network is shown.

[0035] Figure 17 A block diagram of an example electronic device for implementing various aspects of this disclosure is shown.

[0036] Similar reference numerals and naming conventions in the various figures indicate similar elements.

[0037] Detailed description

[0038] The following description is directed to certain specific examples in order to illustrate the innovative aspects of this disclosure. However, those skilled in the art will readily recognize that the teachings herein can be applied in many different ways. Some or all of the examples described can be applied in accordance with 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). The described implementation can be implemented in any device, system, or network capable of transmitting and receiving radio frequency (RF) signals according to one or more of the following standards, or those published by the 3rd Generation Partnership Project (3GPP): Long Term Evolution (LTE), 3G, 4G, or 5G (New Radio (NR)). The described implementation can be implemented in any device, system, or network capable of transmitting 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 implementation can also be implemented using other wireless communication protocols or RF signals suitable for use in one or more of Wireless Personal Area Networks (WPANs), Wireless Local Area Networks (WLANs), Wireless Wide Area Networks (WWANs), or Internet of Things (IoT) networks.

[0039] Some examples in this disclosure may be based on mesh nodes that implement wireless mesh protocols, such as those specified in the IEEE 802.11s revision incorporated into the IEEE 802.11-2016 specification. However, this disclosure is not limited to any particular wireless mesh protocol. Furthermore, the description of a mesh node may refer to any type of device operating a mesh station (STA), including high-efficiency (HE) mesh STAs, extremely high-throughput (EHT) mesh STAs, or next-generation mesh STAs, among others. An HE mesh STA is a type of mesh node that can implement the IEEE 802.11ax revision of the IEEE 802.11 family of standards. An EHT mesh STA is a type of mesh node that can implement the IEEE 802.11be revision of the IEEE 802.11 family of standards. For brevity, the examples in this disclosure may simply refer to mesh nodes to include all such devices and apply to all such standards. Mesh nodes may include mesh STAs configured to participate in wireless mesh networks, such as Mesh Basic Services Set (MBSS) In some scenarios, mesh nodes may also include other logical architectural components, such as access points (APs) providing Infrastructure Basic Services Set (IBSS) for non-mesh STAs, mesh gating for translating traffic between MBSS and IBSS, mesh portals for translating traffic between MBSS and non-802.11 networks, or any combination thereof. According to wireless mesh protocols, mesh nodes can perform path selection and forwarding within the mesh topology.

[0040] This disclosure provides systems, methods, and apparatus for implementing multi-user (MU) group communication within a wireless mesh network, including a computer program encoded on a computer-readable medium. MU group communication enables concurrent transmission of different data (such as data distinct for each receiving device) from one device to each of a number of devices (e.g., multiple simultaneous downlink (DL) communications from an AP to a corresponding STA), or concurrent transmission of different data from multiple devices to a single device (e.g., multiple simultaneous uplink (UL) transmissions from a corresponding STA to an AP). MU group communication differs from conventional multicast communication (where the data sent to all receivers is identical). MU group communication from a source (such as a MU group leader) to multiple receivers (such as selected MU group members) can include bundled data for concurrent transmission, distinct for each receiver. To support MU group transmission, APs and STAs can utilize multi-user multiple-input multiple-output (MU-MIMO) and multi-user orthogonal frequency division multiple access (MU-OFDMA or more commonly abbreviated as "OFDMA") technologies. OFDMA enables MU group communication by subdividing the wireless channel into resource units (RUs) that can be allocated to different devices. MU-MIMO allows MU communication by allocating different spatial streams to different devices. The use of MU group communication provides greater flexibility in managing resource allocation within a wireless network. The IEEE 802.11ax and IEEE 802.11be revisions of the IEEE 802.11 standard family provide technical specifications for MU communication in IBSS. Implementing MU group communication capabilities in wireless mesh networks can offer advantages such as improved wireless channel utilization, better quality of service, and efficiency in managing wireless channel resources.

[0041] In some respects, mesh nodes or network management units can form one or more MU association groups for individual mesh nodes in a wireless mesh network. An MU association group can refer to a group of mesh nodes that can be included in MU group communications managed by an MU group leader. The MU group leader manages radio channel resources by allocating portions of radio channel resources to the respective mesh nodes that will participate in the MU group communications. The MU group leader can act as a regulator for the MU association group and can determine which mesh nodes (among the mesh nodes in the MU association group) should be included in the MU group communications. For example, the MU group leader can send DL MU group communications to one or more mesh nodes within the MU association group, or can trigger UL MU group communications from one or more mesh nodes within the MU association group. Each MU group communication can include all mesh nodes or a subset of mesh nodes in the MU association group guided by the MU group leader.

[0042] In some aspects, the mesh nodes in a MU association group can be assigned the same Association ID (AID) by the MU group leader. The MU group leader can operate as a Multi-User Access Point (MU-AP) in the MU association group. Other mesh nodes in the MU association group can operate as Multi-User Stations (MU-STAs) in the MU association group. Some aspects more specifically involve determining the MU group leader and selecting a type of MU group communication (such as OFDMA or MU-MIMO) for the MU association group. Furthermore, some aspects specifically involve determining the MU association group based on the wireless mesh routing topology, hop count, traffic type, traffic direction, link capacity, routing topology-based weights, operational constraints of mesh nodes, or any combination thereof.

[0043] Mesh nodes can form peer-to-peer relationships, where one mesh node can temporarily act as an access point (AP) for another mesh node (acting as a STA), and vice versa. In some implementations, two mesh nodes can periodically alternate between AP and STA roles based on their peer relationship. A wireless mesh network with several mesh nodes organized by peer relationships is called a multi-hop network because communication can traverse several "hops" (several mesh nodes) in the path from the source device to the destination device. Each hop can refer to a specific direction (from the source mesh node to the next mesh node) and can have a specific traffic pattern (such as traffic load, traffic type, or airtime utilization). By observing the traffic flow and collecting information from multiple mesh nodes, the network management unit or mesh node can identify some MU association groups to optimize the wireless channel utilization for a specific hop.

[0044] Mesh nodes or network management units can form one or more MU association groups to more efficiently handle traffic flows between mesh nodes belonging to the MU association group. MU association groups may differ based on incoming and outgoing traffic. For example, a mesh node sending a large amount of outgoing traffic can act as a MU group leader (assuming the MU-AP role) to concurrently transmit outgoing traffic to multiple mesh nodes in MU group communication (as DL MU group communication). Similarly, a mesh node receiving a large amount of traffic from multiple mesh nodes can be assigned as a MU group leader (assuming the MU-AP role) to schedule trigger-based (TB) UL MU group communication from multiple mesh nodes. This disclosure includes a description of various roles (such as MU-AP or MU-STA) that mesh nodes can assume within MU association groups.

[0045] In some implementations, the formation of MU association groups can be based on MU participation constraints. Each MU participation constraint can limit the number of MU association groups in which a mesh node can be a member. Each MU participation constraint can limit the number of MU association groups in a wireless mesh and prioritize the formation of those MU association groups that are efficient for MU group communication in terms of utilizing channel resources.

[0046] Specific implementations of the subject matter described in this disclosure can achieve one or more of the following potential advantages: Wireless mesh networking technology can be improved to support updates in communication methods and efficient sharing of channel resources. MU association groups can improve the utilization of wireless channels. MU group leaders can manage MU group communications for UL or DL ​​traffic, enabling the concurrent service of multiple mesh nodes using OFDMA or MU-MIMO. The use of MU group communications can improve the overall performance and capacity of the wireless mesh network. The techniques of this disclosure can be used to form MU association groups for those mesh nodes whose performance impact on MU group communications is most significant. This may be useful, for example, when mesh nodes can join a limited number of MU association groups.

[0047] Figure 1 A system diagram of an example wireless mesh network is shown. Wireless mesh networks may also be referred to as ad hoc networks, wireless ad hoc networks, or peer-to-peer (P2P) networks. A wireless mesh network can be a network that implements at least one of the IEEE 802.11 wireless communication protocol standard family (such as standards defined by the IEEE 802.11-2016 specification or its amendments (including, but not limited to, 802.11s)). In some cases, mesh STAs may form a network without an access point (AP) or other equipment besides the mesh STA itself. For simplicity, the terms mesh node and mesh STA are used interchangeably when referring to devices participating in a wireless mesh network. A mesh STA participates in a wireless mesh network by establishing a new wireless mesh network and authorizing other mesh STAs to join it. Additionally or alternatively, a mesh STA can participate in a wireless mesh network by joining an existing wireless mesh network already established by another mesh STA. In some implementations, each mesh STA in a wireless mesh network may have the ability to authorize other mesh STAs to join the wireless mesh network.

[0048] Figure 1The example wireless mesh network 100 shown includes several example mesh STAs 110, 112, 114, 116, 118, and 122 participating in the wireless mesh network. The wireless mesh network 100 may also be associated with a Mesh Basic Services Set (MBSS) 150 that includes all mesh STAs 110, 112, 114, 116, 118, and 122 participating in the wireless mesh network 100. The MBSS 150 is formed as a result of a set of peer relationships between the various peer mesh STAs sharing a compatible configuration for the wireless mesh network. The MBSS 150 may be associated with an MBSS identifier (such as a mesh ID) that distinguishes the MBSS 150 from other potentially neighboring wireless mesh networks (not shown). The formation of peer relationships may involve several messages (such as establishing a group key for each peer relationship, a unique association ID, etc.). Figure 1 In this diagram, the first mesh STA 110 and the second mesh STA 112 have a peering relationship 130. A wireless link 132 exists between the first mesh STA 110 and the second mesh STA 112. Wireless link 132 is shown as a single link, but in some respects it may be considered a combination of two unidirectional relationships. For example, the first mesh STA 110 can act as an access point (AP) and can have an association ID (AID) indicating the wireless link 132 to the second mesh STA 112 (acting as a STA). Simultaneously, the second mesh STA 112 can act as an AP for the first mesh STA 110 (acting as a STA in this instance) and can have its own AID indicating the wireless link 132 to the first mesh STA 110. Therefore, wireless link 132 represents a bidirectional combination of the peering relationships (shown as peering relationship 130) that the first mesh STA 110 and the second mesh STA 112 have with each other. For simplicity, peering relationships for other mesh STA pairs are not shown. However, wireless links 138, 134, 136, 142, 144, 146 and 148 are interpreted as illustrating the topology of wireless mesh network 100.

[0049] The wireless mesh network 100 can route traffic from one peer mesh STA to another via a multi-hop network. For example, a second mesh STA 112 can communicate with other networks 180 by relaying traffic to a first mesh STA 110 via wireless link 132, and the first mesh STA 110 can relay communication to a third mesh STA 114 via wireless link 134. The routing of data frames can be coordinated using a path selection protocol used by mesh STAs 110, 112, 114, 116, 118, and 122. For example, the path selection protocol could be the Hybrid Wireless Mesh Protocol (HWMP). HWMP is defined in IEEE 802.11-2016 and is inspired by a combination of on-demand self-organizing routing and tree-based routing. Figure 1 As can be seen, communication in a multi-hop wireless mesh network involves coordinating the airtime used by mesh STAs 110, 112, 114, 116, 118, and 122. Mesh STAs 110, 112, 114, 116, 118, and 122 can implement the Mesh Coordination Function (MCF) Controlled Channel Access (MCCA) protocol to manage congestion and media reservation.

[0050] Figure 2 A system diagram is shown in which mesh nodes of an example wireless mesh network can achieve connectivity with non-mesh networks. Figure 2 MBSS 250 in the text can be similar to reference Figure 1 The MBSS 150 described herein. The MBSS 250 may include multiple mesh nodes 210, 212, and 218. Each of the mesh nodes 210, 212, and 218 may include a mesh STA (such as referenced). Figure 1 The described mesh STAs are 110, 112, 114, 116, 118, and 122. Mesh nodes 210, 212, and 218 may function and communicate (via appropriate peers) in accordance with the IEEE 802.11 wireless communication protocol standard family (such as standards defined by the IEEE 802.11-2016 specification or its revisions, including but not limited to 802.11s).

[0051] Figure 2 The text explains some examples where mesh nodes can also include mesh gating or mesh portals. Figure 2 An example mesh node 218 includes a mesh STA 214 and a mesh portal 282. For example, the mesh portal 282 may be co-located, integrated, or communicatively coupled with the mesh node 218. The mesh portal 282 can provide connectivity 284 for traffic between the MBSS 250 and another network 280 (such as a non-IEEE 802.11 network, a local area network, a home network, or the Internet, etc.). The mesh portal 282 can be a logical architectural component of the mesh node 218 and can translate packets between the MBSS 250 and other networks 280. Although... Figure 2 Only one mesh node 218 has been described with a mesh portal 282, but it is possible for multiple mesh nodes to have mesh portals (not shown) to other networks.

[0052] Figure 2The example mesh node 210 includes a mesh STA 214, a mesh gating 242, and an AP 202. AP 202 can be co-located, integrated, or communicatively coupled with mesh node 210. Mesh gating 242 can provide connectivity between MBSS 250 and Infrastructure BSS (IBSS) 230. Mesh gating 242 can be a logical architectural component of mesh node 210 and can translate packets between MBSS 250 and IBSS 230. Although... Figure 2 Only one mesh node 210 with mesh gating 242 has been described, but it is possible for multiple mesh nodes to have mesh gating and AP (not shown). Mesh node 210 may also be referred to as mesh AP or mesh point (MP) because it includes AP 202 for operating IBSS 230 and mesh STA 214 for communicating with MBSS 250.

[0053] AP 202 manages IBSS 230, in which multiple non-mesh STAs (referred to as STA 204 for simplicity) can communicate with each other or with mesh gating 242 via AP 202. Each STA 204 may also be referred to as a mobile station (MS), mobile device, mobile handheld device, wireless handheld device, access terminal (AT), user equipment (UE), subscriber station (SS), or subscriber unit, and other examples. STA 204 may represent a variety of devices, such as mobile phones, personal digital assistants (PDAs), other handheld devices, netbooks, laptops, tablets, laptops, display devices (e.g., TVs, computer monitors, navigation systems, etc.), music or other audio or stereo devices, remote control devices (“remote controllers”), printers, kitchen or other household appliances, key fobs (e.g., for passive keyless entry and start (PKES) systems), and other examples.

[0054] A single AP 202 and its associated group of STAs 204 may be referred to as an Infrastructure Basic Service Set (IBSS) (or, when not referring to a wireless mesh, a Basic Service Set (BSS)), which is managed by the respective AP 202. The IBSS 230 can be identified to users by a Service Set Identifier (SSID) and to other devices by a Basic Service Set Identifier (BSSID), which may be the Media Access Control (MAC) address of the AP 202. The AP 202 periodically broadcasts a beacon frame (“beacon”) including the BSSID, enabling any STA 204 within the wireless range of the AP 202 to “associate” or reassociate with the AP 202 to establish a corresponding communication link 208 with the AP 202 (also referred to hereinafter as a “Wi-Fi link”) or maintain a communication link 208 with the AP 202. For example, the beacon may include an identifier of the primary channel used by the respective AP 202 and a timing synchronization function for establishing or maintaining timing synchronization with the AP 202.

[0055] In order to establish a communication link 208 with AP 202, each STA 204 is configured to perform a passive or active scanning operation (“scan”) on a frequency channel in one or more frequency bands (e.g., 2.4 GHz, 5 GHz, 6 GHz, or 60 GHz bands). To perform a passive scan, STA 204 listens for beacons transmitted by the corresponding AP 202 at periodic time intervals (referred to as Target Beacon Transmission Time (TBTT) (measured in units of time (TU), where one TU can be equal to 2024 microseconds (μs)). To perform an active scan, STA 204 generates probe requests and transmits these probe requests sequentially on each channel to be scanned, and listens for probe responses from AP 202. Each STA 204 can be configured to identify or select an AP 202 to associate with based on scan information obtained through passive or active scanning, and perform authentication and association operations to establish a communication link 208 with the selected AP 202. At the end of the association operation, AP 202 assigns an Association Identifier (AID) to STA 204, which AP 202 uses to track STA 204.

[0056] As wireless networks become increasingly prevalent, STA 204 has the opportunity to select from one of many BSSs within its range or from multiple APs 212 (potentially co-located or integrated with one or more mesh nodes 212). STA 204 can be covered by more than one AP and can be associated with different APs at various times for different transmissions. Additionally, after being associated with AP 202, STA 204 can also be configured to periodically scan its surroundings to find a more suitable AP 202 to associate with. For example, STA 204 moving relative to its associated AP 202 can perform a "roaming" scan to find another AP 202 with more suitable network characteristics, such as a larger Received Signal Strength Indicator (RSSI) or reduced traffic load.

[0057] AP 202 and STA 204 function and communicate (via the corresponding communication link 208) according to the IEEE 802.11 wireless communication protocol standard family (such as standards defined by the IEEE 802.11-2016 specification or its revisions, including but not limited to 802.11ay, 802.11ax, 802.11az, 802.11ba, and 802.11be, etc.). These standards define WLAN radio and baseband protocols for the PHY and Media Access Control (MAC) layers. AP 202 and STA 204 transmit and receive wireless communications (hereinafter also referred to as "Wi-Fi communication") to and from each other in the form of PHY Protocol Data Units (PPDUs) (or Physical Layer Convergence Protocol (PLCP) PDUs). AP 202 and STA 204 in WLAN 200 can transmit PPDUs on unlicensed spectrum, which can be a portion of the spectrum including bands traditionally used by Wi-Fi technologies, such as the 2.4 GHz band, 5 GHz band, 60 GHz band, 3.6 GHz band, and 1,100 MHz band. Some implementations of AP 202 and STA 204 described herein can also communicate in other bands, such as the 6 GHz band, that can support both licensed and unlicensed communication. AP 202 and STA 204 can also be configured to communicate on other bands, such as shared licensed bands, where multiple operators may have licenses to operate in one or more identical or overlapping bands. Each PPDU is a composite structure including a payload in the form of a PHY preamble and a PHY Service Data Unit (PSDU). The information provided in the preamble can be used by the receiving device to decode subsequent data in the PSDU.

[0058] In traditional WLAN deployments, single-user (SU) access mode is based on contention-based access, where a station gains access to the entire channel in the form of a transmission opportunity (TXOP) when it wins the contention. Different priorities and access classes can be used by the WLAN to prioritize traffic. Recently, the IEEE draft 802.11ax standard implemented support for more efficient use of wireless channels in MU communications (such as OFDMA and MU-MIMO) using scheduled access mode or MU EDCA access mode. Using OFDMA and scheduled access mode, AP 202 can schedule airtime availability for different stations.

[0059] Figure 3A An example conceptual diagram of OFDM 301 is shown. The OFDM channel width can include multiple subcarriers. WLAN packets (also known as PPDUs) consist of data encoded using subcarriers with the channel bandwidth. For example, a first STA may transmit a first PPDU 310 during a first time period. During a second time period, a second STA may transmit a second PPDU 320. PPDUs 310 and 320 can have different time lengths. Typically, the first and second STAs (and any other STAs in the BSS) will contend for access to the channel. Once a STA wins the contention, it can use the channel to transmit PPDUs. Figure 3A As shown, the different shades on the PPDU indicate that different STAs can utilize the radio channels sequentially, one channel at a time. However, if the STA does not have sufficient data to justify using the full channel width, this communication structure may be inefficient.

[0060] Figure 3B An example conceptual diagram of MU-OFDMA 302 is shown. Using OFDMA, an AP can allocate portions of the channel bandwidth to different users. These portions of the channel bandwidth can be referred to as Resource Units (RUs). Each RU can include a different number of subcarriers (also called “frequency modulations”). Different RUs can be allocated by the AP at specific times or assigned to different STAs. The size and distribution of RUs can be referred to as RU allocation. In some implementations, RUs can be allocated in 2MHz intervals, and thus, the smallest RU can include 26 frequency modulations, comprising 24 data frequency modulations and 2 pilot frequency modulations. Therefore, in a 20MHz channel, up to 9 RUs (such as 2MHz, 26-frequency-modulation RUs) can be allocated (because some frequency modulations are reserved for other purposes). Similarly, in a 160MHz channel, up to 74 RUs can be allocated. Larger RUs of 52, 106, 242, 484, and 996 frequency modulations can also be allocated. Adjacent RUs can be separated by empty subcarriers (such as DC subcarriers) to reduce interference between adjacent RUs, reduce receiver DC offset, and avoid leakage of the transmit center frequency.

[0061] Using OFDMA, an AP can concurrently transmit downlink (DL) data to different STAs. DL data can be signaled in different RUs assigned to different STAs and indicated in the header of the DL OFDMA PPDU. For example, the DLOFDMA PPDU 350 may include different RUs assigned to a first STA, a second STA, a third STA, and a fourth STA. One RU 340 is assigned in the PPDU 350 for downlink data to a STA, while other RUs are assigned to different STAs.

[0062] RU allocation can also be used to schedule uplink (UL) channel access. For example, an AP can transmit trigger frames to initiate and synchronize UL OFDMA transmissions from multiple STAs to the AP. Such trigger frames thus enable multiple STAs to concurrently send UL traffic to the AP in time. The trigger frame can address one or more STAs via a corresponding associated identifier (AID), and one or more RUs can be assigned to each AID (and thus each STA), which can be used to send UL traffic to the AP. UL trigger-based PPDUs can be aggregations of UL transmissions of different data (also referred to as dissimilar data or node-specific data). In MU group communication, UL transmissions can be concurrently signaled by multiple STAs transmitting UL data in their respective RU allocations.

[0063] Figure 3C A sample conceptual diagram of multi-user (MU) multiple-input multiple-output (MIMO) (MU-MIMO) is shown. APs and STAs, including multiple antennas, can support beamforming and spatial multiplexing. Beamforming refers to focusing transmitted energy in the direction of the target receiver. Beamforming can be used in single-user environments (e.g., to improve the signal-to-noise ratio (SNR)) as well as in multi-user (MU) environments (e.g., to achieve MU-MIMO transmission (also known as spatial division multiple access (SDMA))). To achieve spatial multiplexing, the transmitting device divides the data stream into N segments. SS Each spatial stream is a separate, independent spatial stream. The spatial streams are encoded individually and transmitted in parallel via multiple transmit antennas. A WLAN device 303 (such as an AP with multiple transmit antennas) can assign the different spatial streams to different receiver devices 362, 364, and 366.

[0064] Figure 4 This illustrates an example MU role that mesh node 410 might have in a wireless mesh network. See references respectively. Figure 3B and 3CThe OFDMA and MU-MIMO technologies described for MU group communication have been implemented in BSS infrastructures consisting of APs and multiple STAs. However, in wireless mesh networks, mesh nodes can alternate between AP and STA roles. Therefore, mesh nodes can flexibly assume different types of roles for MU group communication in wireless mesh networks. The concepts of uplink (UL) and downlink (DL) directionality are fluid in wireless mesh networks because any given mesh node can act as either an AP or STA for a peer mesh node and can alternate roles based on traffic conditions and wireless mesh network configuration. Nevertheless, using the concepts of UL and DL directionality is helpful in characterizing traffic entering and leaving mesh nodes. Figure 4 In the example, mesh nodes 410 and 420 are referred to as peer mesh nodes based on their peer-to-peer relationship of direct communication with each other. Similarly, mesh nodes 410 and 440 are peer mesh nodes.

[0065] For reference Figure 4 As described, the concepts of UL and DL directionality can refer to the direction of traffic to or from a mesh node that operates as a MU-AP for another mesh node (operating as a MU-STA). For example, DL directionality can refer to the direction of traffic transmitted from mesh node 410 to one or more mesh nodes 440 (acting as MU-STAs), and can refer to the direction of traffic received by mesh node 410 from one or more mesh nodes 420 (acting as MU-APs). Figure 4 The left side illustrates the potential roles that mesh node 410 can assume for DL ​​traffic. For DL ​​traffic, wireless mesh node 410 can assume the role of MU-AP when sending DL MU transmissions to one or more mesh nodes 440 (assuming the role of MU-STA). Wireless mesh node 410 can assume the role of MU-STA when receiving DL MU transmissions from one or more mesh nodes 420 (assuming the role of MU-AP). UL directivity can refer to the direction of traffic transmitted from mesh node 410 to one or more mesh nodes 420 (assuming the role of MU-AP), and can also refer to the direction of traffic received by mesh node 410 from one or more mesh nodes 440 (assuming the role of MU-STA). Figure 4 The right side illustrates the potential roles that mesh node 410 can assume for UL traffic. For UL traffic, wireless mesh node 410 can assume the role of MU-STA when sending UL MU transmissions to one or more mesh nodes 420 (assuming the role of MU-AP). Wireless mesh node 410 can assume the role of MU-AP to trigger and receive UL MU transmissions from one or more mesh nodes 440 (assuming the role of MU-STA).

[0066] It is evident that mesh node 410 can have different roles for receiving MU transmissions from multiple mesh nodes. For example, mesh node 410 can act as a MU-STA to receive MU inbound transmissions as DL traffic (on the left) and as a MU-AP to receive MU inbound transmissions as UL traffic (on the right). While both the MU-AP and MU-STA roles enable mesh node 410 to receive MU inbound transmissions, there may be scenarios where mesh node 410 is preferably operated as either a MU-AP or a MU-STA. This disclosure includes various considerations influencing which role is preferred for a particular mesh node.

[0067] Each mesh node (such as mesh node 410) may have a MU participation constraint that limits how many MU relationships (which may be referred to as peer MU relationships) each mesh node can have for UL or DL ​​traffic. Examples of MU participation constraints include the maximum number of other mesh nodes that can operate as MU-APs or MU-STAs for its mesh node 410. The MU participation constraints for each mesh node may differ based on manufacturer configuration, user configuration, or system configuration. Furthermore, the MU participation constraints may differ for UL and DL traffic. As an example, mesh node 410 as a MU-STA for DL ​​MU traffic from one or more mesh nodes 420 may support up to eight (8) MU connections. The same mesh node 410 as a MU-STA for UL MU traffic to one or more mesh nodes 420 may support up to two (2) MU connections. In some implementations, the MU participation constraint may be based on the number of intermediate hops at the mesh node or the size of the wireless mesh. For example, the MU participation constraint for a specific mesh node could be the percentage of the total number of mesh nodes with which that specific mesh node has established a peer relationship.

[0068] In some implementations, the role (MU-AP or MU-STA) selected for UL or DL ​​traffic may depend on the traffic volume to or from the mesh node. For example, when most (volume-based) traffic is coming from multiple other mesh nodes, it may be preferable for mesh node 410 to operate as a MU-AP so that it can more efficiently schedule and trigger incoming transmissions. Alternatively, when mesh node 410 is one of many mesh nodes directing a large amount of traffic to a destination mesh node, it may be preferable for mesh node 410 to operate as a MU-STA so that the destination mesh node can operate as a MU-AP to manage its incoming traffic. A mesh node operating as a MU-AP can allocate radio channel resources for MU group communications to or from MU-STAs. In some implementations, the terms "allocating" or "in the process of allocating" may also refer to managing radio channel resources for MU group communications.

[0069] In some implementations, the role (MU-AP or MU-STA) selected for UL or DL ​​traffic may depend on the number of incoming or outgoing peer MU relationships in the routing topology used for the wireless mesh network. When mesh node 410 has multiple incoming peer MU relationships, it may be preferred for mesh node 410 to operate as a MU-AP. Conversely, when mesh node 410 is one of multiple mesh nodes sending traffic to the same destination mesh node, it may be preferred for mesh node 410 to operate as a MU-STA. The number of incoming and outgoing peer MU relationships can be discoverable based on the wireless mesh network's routing protocol or logical topology.

[0070] In some implementations, the role (MU-AP or MU-STA) selected for UL or DL ​​traffic may depend on the effective link capacity or bottleneck in the path from or to another mesh node. In addition to the different potential roles of mesh node 410, various roles can be used in conjunction with different MU communication types (such as OFDMA or MU-MIMO). The selection of the MU communication type may depend on the type of traffic to or from the mesh node. For example, it may be preferred for mesh node 410 (as MU-AP or MU-STA) to use OFDMA for latency-sensitive traffic. It may be preferred for mesh node 410 (as MU-AP or MU-STA) to use MU-MIMO for capacity-sensitive traffic.

[0071] In some implementations, the role selection (MU-AP or MU-STA) for UL or DL ​​traffic may depend on the number of hops from the mesh node to the mesh gating or mesh portal that connects the wireless mesh to another network. Mesh node 410 may be preferred to operate as a MU-AP when it has fewer hops compared to multiple peer mesh nodes. Mesh nodes with higher hop counts may be preferred to operate as MU-STAs compared to MU-APs.

[0072] Furthermore, each mesh node can operate as a MU-STA for some peer mesh nodes and as a MU-AP for others. This disclosure introduces the concept of a MU association group, which defines a set of mesh nodes including mesh nodes operating as MU-APs and multiple mesh nodes operating as MU-STAs. MU association groups can be determined by the network management unit based on the mesh node's traffic pattern, traffic type, and MU constraints. A mesh node can operate within multiple MU association groups. MU association groups do not restrict a mesh node from transmitting or receiving single-user (SU) communications with any of its peer mesh nodes. However, by optimizing MU association groups, wireless mesh networks can benefit from the advantages of MU group communications, including spectral efficiency, fair distribution of channel resources, and coordinated scheduling of concurrent transmissions, etc.

[0073] Figure 5 An example wireless mesh network 500 and an example MU association group are shown. The example wireless mesh network 500 includes six mesh nodes, labeled mesh node A, mesh node B, mesh node C, mesh node D, mesh node E, and mesh node F. Mesh node D has a mesh portal for enabling communication with another network 581. Mesh node F has a mesh portal for enabling communication with another network 582.

[0074] As previously described, wireless mesh networks can use path selection protocol messages to determine, obtain, or generate routing topologies. In some implementations, path selection protocols may also be referred to as routing protocols. Although sometimes called routing protocols or routing topologies, routes / paths in a wireless mesh network can be determined based on MAC layer (Layer 2) forwarding rather than Internet Protocol (IP) layer (Layer 3) routing. Path selection protocols can determine paths in a wireless mesh network for a variety of destinations, including mesh portals at mesh nodes D and F. IEEE 802.11-2016 describes the mandatory path selection protocol HWMP based on on-demand self-organizing routing and tree-based routing schemes. In some implementations, routing topologies can be obtained, selected, or determined by a network management unit or mesh node that can use the routing topologies to form MU association groups. In some implementations, a network management unit or mesh node can forward routing topologies to another mesh node to help that other mesh node form MU association groups.

[0075] Reference Figure 5 In the example wireless mesh network 500, the arrows between mesh nodes A and F indicate the next-hop path determined by the path selection protocol. For example, mesh node A can send traffic to mesh nodes B and F. Mesh node B can send traffic to mesh nodes A, C, and E. Mesh node C can send traffic to mesh nodes B and D. Mesh node D can send traffic to mesh nodes C, E, and other networks 581. Mesh node E can send traffic to mesh nodes A, D, and F. And mesh node F can send traffic to mesh nodes A, E, and other networks 582. Using the next-hop path, a mesh node can "route" traffic from itself to any other mesh node in wireless mesh network 500 or other networks 581 and 582. The next hop can be referred to as an intermediate hop in the routing topology used in a wireless mesh network. In some implementations, each mesh node can be a mesh point and may include mesh gating and APs, such that they can provide IBSS for use with a legacy STA (not shown) in the vicinity of the wireless mesh network 500. A mesh path can refer to the path between mesh nodes and mesh gating, and based on the routing topology, may include a number of hops through the wireless mesh network.

[0076] As an example only, consider a conventional STA (not shown) connected to an IBSS operated by an AP in mesh node A. This STA may have a session for sending or receiving transmissions to or from a host (not shown) in another network 581. The STA can forward traffic to mesh node A, which can choose between its available next-hop destinations (mesh node F or mesh node B). Those mesh nodes can then forward the traffic to the next hop, and so on, until the traffic traverses a path from mesh node A to mesh node D, where it can be translated and forwarded to the other network 581.

[0077] Figure 5 An example MU association group is also shown that can facilitate MU group communication between mesh nodes. For example, a first MU association group 510 may include mesh node D, mesh node C, and mesh node E. Mesh node D may be designated as the MU group leader of the first MU association group 510, and mesh nodes C and E may be members of the first MU association group 510. Therefore, mesh node D can assume the role of MU-AP, and mesh nodes C and E can assume the role of MU-STA. Figure 5 In the example shown, mesh node D can operate as a MU-AP for downlink transmission of different data (such as dissimilar data or node-specific data) in MUDL group communications to other mesh nodes C and E in the first MU association group 510. Therefore, mesh node D can efficiently manage radio channel resources to concurrently transmit "downlink" traffic to mesh nodes C and E. In one scenario, mesh node D can receive a large amount of "uplink" traffic from mesh nodes C and E, and thus can also operate as a MU-AP to allocate radio channel resources for uplink transmissions of different data (such as dissimilar data or node-specific data) in MU UL group communications. It should be apparent that the device can operate as a MU-AP for one direction (such as UL or DL) and as a MU-STA for traffic in the other direction. Figure 5In the example shown, the formation of the first MU association group 510 can be based on traffic information between mesh node D and mesh nodes C and E, link information about the links between the mesh nodes, or a combination thereof. For example, traffic information (also referred to as traffic flow information) may include one or more of traffic direction, traffic type (such as whether the traffic is time-sensitive or capacity-sensitive), or traffic volume, etc. Link information may include one or more of the number of incoming or outgoing links from each mesh node, or the effective capacity of various links, etc. In some implementations, the traffic information or link information may be obtained, selected, or determined by a network management unit or mesh node that can use the information during the formation of the MU association group. In some implementations, the network management unit or mesh node may forward the traffic information or link information to another mesh node to help that other mesh node form the MU association group.

[0078] The second MU related group 520 is in Figure 5 As shown in the diagram. The second MU association group 520 may include mesh nodes A, B, E, and F. The second MU association group 520 is shown to illustrate another example factor that can be considered when forming the MU management group. Mesh node A receives data from several mesh nodes B, E, and F, while other mesh nodes in the second MU association group 520 receive data from a smaller number of other mesh nodes. Therefore, a potential factor in the formation of the MU association group could be the number of mesh nodes that send traffic from a source mesh node to a destination mesh node, or the number of destination mesh nodes to which a specific mesh node sends traffic. Figure 5 In the example, mesh node A can be the MU group leader of the second MU association group 520 and can act as a MU-AP to manage UL MU group communication for traffic from peer mesh nodes B, E and F.

[0079] like Figure 5 As shown in the example, a mesh node can concurrently exist in multiple MU association groups. For example, mesh node E can be a member (as a MU-STA) for the first MU association group 510 and the second MU association group 520. A mesh node can also concurrently act as a MU group leader (MU-AP) for one or more MU association groups and as a member (MU-STA) for one or more other MU association groups. For simplicity, Figure 5 Two MU association groups are shown, but there may be more MU association groups (not shown) depending on the traffic conditions and topology of the wireless mesh network.

[0080] Several factors can be considered when forming a MU association group for a wireless mesh network. For example, the MU association group can be based on the network topology (such as the location of the mesh portal providing ingress and egress links), hop count, traffic direction, traffic type (such as whether the traffic is latency-sensitive or capacity-sensitive), the number of incoming and outgoing links from each mesh node, traffic volume, or the effective capacity of various links, etc. A network management unit 590 (or a mesh node operating as a network management unit) can form the MU association group for the wireless mesh network. The network management unit 590 can collect information from the mesh nodes before forming the MU association group.

[0081] The network management unit 590 may be located outside the mesh nodes or may be included within one of the mesh nodes. In some implementations, each mesh node may be able to perform the functionality of the network management unit 590. One of the mesh nodes may be selected as the root mesh node. In some implementations, the wireless mesh protocol may include message passing for selecting the root mesh node, and the mesh node may activate its network management unit to control various settings of the wireless mesh (including the determination of MU association groups). In some implementations, the network management unit 590 may be a centralized resource external to the mesh nodes in the wireless mesh network 500.

[0082] Figure 6 An overview of an example process 600 for forming a MU association group is shown. The operation of process 600 can be implemented by a network management unit, mesh nodes, centralized resources, or any component thereof, as described herein. For example, process 600 can be implemented by a network management unit (such as reference...) Figure 5 The described network management unit 590) is used to execute this process. In some implementations, process 600 (or parts thereof) can be executed by mesh nodes, such as those referring to... Figure 2 , 4 The mesh node 210, 212, 218, 410, mesh node AF, mesh node 1300, or mesh node 1700 described in 5, 8, 13, and 17. In some implementations, process 600 may be performed by a component of the mesh node, such as the one described in reference 5. 8. 8. 9. 17. Figure 1 One of the described mesh STAs 110, 112, 114, 116, 118, and 122. For the sake of brevity, example process 600 is described as being performed by a device that can be any of the network management unit, mesh node, mesh STA, or components thereof indicated above.

[0083] In block 610, the device can determine the traffic types and patterns among the mesh nodes. For example, the device can send requests or queries to mesh nodes to request traffic information from each mesh node's perspective. In some implementations, mesh nodes can be configured to periodically or upon request communicate traffic information to other mesh nodes or the network management unit. In some implementations, the device can query those mesh nodes that act as traffic entry points for the wireless mesh network. The traffic information can indicate the source and destination of traffic traversing intermediate hops based on the wireless mesh network's routing topology. The traffic information can also indicate whether traffic on a particular intermediate hop is time-sensitive or capacity-sensitive. In some implementations, the device can notify mesh nodes about the traffic information they collect or aggregate. In some implementations, the operation at block 610 can be omitted when the network management unit is configured to ignore traffic information as a factor when creating MU association groups.

[0084] In box 620, the device can determine candidate MU association groups suggested by the mesh nodes. For example, each mesh node capable of operating as a MU-AP can determine the MU technology type (OFDMA or MU-MIMO) and potential MU-STAs for its DL and UL traffic based on one or more criteria. These criteria can be based on traffic type and traffic volume. For example, a first candidate MU association group may include MU-STA mesh nodes with throughput-sensitive traffic and high traffic load from or to shared MU-AP mesh nodes. The MU technology used for the first candidate MU association group can be specified as MU-MIMO. A second candidate MU association group may include a group of MU-STA mesh nodes with latency-sensitive traffic and low traffic load from or to shared MU-AP mesh nodes. The MU technology used for the second candidate MU association group can be specified as OFDMA. Thresholds for high and low traffic loads can be based on threshold amounts, the average traffic load across all hops in the wireless mesh, the average traffic load at the entry and exit points, or the average traffic load for intermediate hops. In some implementations, the threshold can be a offset or range of any of the above averages. To obtain candidate MU association groups suggested by the mesh nodes, the device can query the mesh nodes, or the mesh nodes can be configured to report candidate MU association groups periodically or after a network change event or a query from the device.

[0085] In box 630, the device can determine the MU participation constraints of mesh nodes. For example, the device can query mesh nodes to determine their MU participation constraints, or mesh nodes can be configured to report their MU participation constraints.

[0086] In box 640, the device can determine the MU association group based on one or more potential factors. These factors may include criteria based on traffic type, MU participation constraints, wireless mesh topology or routing topology, etc. For example, the device can determine the MU technology type as OFDMA for latency-sensitive traffic or MU-MIMO for capacity-sensitive traffic. The device can select mesh nodes with a higher number of outgoing intermediate hops to the target mesh node and designate those mesh nodes as MU group leaders (as MU-APs) of the MU association group to manage DL MU group communication to one or more mesh nodes within that MU association group. The device can also select mesh nodes with a higher number of incoming intermediate hops from the source mesh node and designate those mesh nodes as MU group leaders (as MU-APs) of the MU association group to manage UL MU group communication from one or more mesh nodes within that MU association group. The device can select mesh nodes with higher outgoing traffic to the target mesh node and designate those mesh nodes as MU group leaders (as MU-APs) for MU association groups to manage DL MU group communication to one or more mesh nodes within the MU association group. The device can also select mesh nodes with higher traffic from the source mesh node and designate those mesh nodes as MU group leaders (as MU-APs) for MU association groups to manage ULMU group communication from one or more mesh nodes within that MU association group. In some implementations, the selection of MU group leaders and MU association groups can be based on capacity. For example, the device can select mesh nodes with a higher total traffic volume relative to available capacity and designate those mesh nodes as MU group leaders (as MU-APs) for UL or DL ​​traffic. After selecting the MU group leader for the MU association group, the device can designate member mesh nodes (as MU-STAs) for each MU association group. The designation of member mesh nodes can be restricted based on the MU participation constraints of each mesh node. Figure 7 Example process 700 is shown, which uses the potential factors described in box 640 to determine the MU association group.

[0087] In box 650, the device can notify the mesh nodes of MU association group assignments. For example, the device can send a message indicating a list of MU group leaders and members for a specific MU association group identified in box 640.

[0088] Figure 7 A detailed example process is shown where mesh nodes or network management units can form different MU association groups. The operation of process 700 can be implemented by a network management unit, mesh nodes, centralized resources, or any component thereof, as described herein. For example, process 700 can be implemented by a network management unit (such as referenced...) Figure 5 The network management unit 590 described herein is used for execution. In some implementations, process 700 (or parts thereof) can be executed by mesh nodes, such as those referring to... Figure 1 , 2 The mesh node 210, 212, 218, 410, mesh node AF, mesh node 1300, or mesh node 1700 described in 4, 5, 8, 13, and 17. In some implementations, process 700 may be performed by a component of the mesh node, such as the one described in reference 4.5 ... Figure 1 One of the described mesh STAs 110, 112, 114, 116, 118, and 122. For the sake of brevity, example process 700 is described as being performed by a device that can be any of the network management unit, mesh node, mesh STA, or components thereof indicated above.

[0089] In box 710, the device can collect information from the mesh nodes. For example, the device can perform actions such as referencing... Figure 6 The operations described in boxes 610, 620 and 630.

[0090] In box 720, the device can select the mesh nodes to operate as MU group leaders (MU-APs) for MU-MIMO-using MU-associated groups. These mesh nodes may be referred to as MU-APs suitable for MU-MIMO. The device can select the first MU group leader based on routing topology, traffic patterns, or capacity bottlenecks, as shown in reference... Figure 8-10 As described. In the routing topology example, the device can select a first mesh node with the fewest hops to mesh gating as a MU-AP operation for a MU association group associated with UL traffic. In the traffic load example, the device can select a first mesh node with high traffic load as a MU-AP operation for a MU association group using MU-MIMO. In the capacity bottleneck example, the device can select a first mesh node that applies the highest traffic backpressure as a MU-AP operation for a MU association group using MU-MIMO.

[0091] In block 730, the device can assign mesh nodes to the MU association group based on the peering relationship between each mesh node in block 720 and the first mesh node. Ideally, MU-STA mesh nodes are those MU-STA mesh nodes that can use MU-MIMO with the MU-AP selected in block 720. It should be noted that the device can suppress the assignment of mesh nodes to the MU association group if the assignment would exceed its MU participation constraints.

[0092] In block 740, the device can determine whether there is another suitable MU-AP for a MU-MIMO that has not exceeded its MU participation constraints. If so, process 700 can return to block 710 to begin assignment for another MU association group. If there are no other suitable MU-MIMOs for MU-APs, or if they have exceeded their respective MU participation constraints, process 700 can continue to block 750.

[0093] In box 750, the device can select mesh nodes to operate as MU group leaders (MU-APs) for MU associated groups using OFDMA. These mesh nodes may be referred to as suitable OFDMA MU-APs. The device can select the first mesh node with the most intermediate hops to the MU-STA mesh node as the first MU group leader.

[0094] In block 760, the device can assign mesh nodes to the MU association group based on the peering relationship between each mesh node in block 750 and the first mesh node. Ideally, MU-STA mesh nodes are those MU-STA mesh nodes that can use OFDMA with the selected MU-AP in block 750. It should be noted that the device can suppress the assignment of mesh nodes to the MU association group if the assignment would exceed its MU participation limit.

[0095] In block 770, the device can determine whether there is another suitable OFDMA MU-AP that has not exceeded its MU participation constraints. If so, process 700 can return to block 750 to begin assignment for another MU association group. If there are no other suitable OFDMA MU-APs, or if they have exceeded their respective MU participation constraints, process 700 can continue to block 780.

[0096] In box 780, the device can notify the mesh nodes of the MU association group and their assigned roles in that MU association group.

[0097] Figure 8 Example traffic conditions in an example wireless mesh network are shown, and these example traffic conditions are used to describe different considerations when forming MU association groups. Wireless Mesh Network 800 Topology and Reference Figure 5 The same as described in the Wireless Mesh 500. Figure 8 This includes example traffic information (such as traffic flow information) for each intermediate hop. For example, mesh node A might send outgoing traffic to mesh node B in intermediate hop 814. The traffic in intermediate hop 814 could be represented as a metric "50". Figure 8In some examples, the metric can represent traffic volume, such as 50 Mbps. However, the metric can be based on a weighted or other representation that relatively describes the traffic on hop 814 compared to the other hops 812, 816, 818, 820, 822, 824, 826, 828, 830, 832, 834, 836, and 838. For simplicity, the source and destination of each hop, along with their corresponding metrics representing traffic load, are combined in Table 1 below.

[0098]

[0099]

[0100] Table 1. Summary of intermediate jumps

[0101] For reference Figure 5 As described, Figure 8 The wireless mesh network 800 includes mesh nodes D and F as entry / exit points for connecting to other networks 581 and 582, respectively. Figure 8 The example traffic load suggests that these nodes have more outgoing traffic flowing from mesh nodes D and F to their respective peer mesh nodes A, E, and C. Figure 8 Figure 801 (also reproduced as Table 2 below) includes a summary of traffic load metrics as a matrix. Each row represents the outgoing (transmitting) view of traffic from each mesh node to its peer mesh node. Each column represents the incoming (receiving) view of traffic received by each mesh node from its peer mesh node.

[0102]

[0103]

[0104] Table 2. Matrix Summary of Call Load Metrics

[0105] Example traffic in the example wireless mesh 800 has been described, and this example traffic will be used to describe some example techniques for determining MU association groups.

[0106] Example based on call load

[0107] Devices (such as network management units or mesh nodes) can observe the network or collect traffic information to determine traffic load metrics (such as those described in Table 2). In some implementations, traffic can be observed during periods when MU association groups are not used, such as during the initialization of MU mesh configuration, during configured measurement periods, or as part of a reconfiguration period. In some implementations, traffic can be observed after the initial assignment of MU association groups has been performed. The device can determine the MU groups used for UL and DL traffic based on the collected traffic information.

[0108] As an example of forming MU (Multi-Mesh) clusters for DL ​​(Digital Traffic) traffic, the device can start by grouping mesh nodes that transmit a large amount of traffic (or traffic above average or above a threshold) with those mesh nodes in their receiver lists, beginning with the mesh nodes with the highest weights. For example, mesh nodes D and F can be designated as MU group leaders because they both have the highest traffic metric (250) in the table. The designation of MU group leaders can be based on mesh nodes with the largest outgoing traffic or mesh nodes with the largest number of packets. Figure 8 As in the examples in Table 2, mesh nodes D and F can be selected as MU group leaders for MU association groups supporting DL MU-MIMO. In the first MU association group (for DL ​​MU-MIMO), mesh node D can be the MU group leader, and mesh nodes C and E can be members. In the second MU association group (for DL ​​MU-MIMO), mesh node F can be the MU group leader, and mesh nodes A and E can be members.

[0109] As an example of forming MU (Multi-Use Group) clusters for UL (Upper-Level) traffic, the device can start by grouping mesh nodes receiving a large amount of traffic (or traffic above average or above a threshold) with those mesh nodes in its source list, beginning with those mesh nodes with the highest weights. For example, mesh nodes A and E can be designated as MU cluster leaders because they both have the highest incoming traffic metrics in the table (mesh node E has 245, while mesh node A has 195). Therefore, in Figure 8 As in the examples in Table 2, mesh nodes A and E can be selected as MU group leaders to manage UL MU group communication from one or more mesh nodes within a MU association group supporting UL MU-MIMO. Therefore, in the third MU association group (for UL MU-MIMO), mesh node A can be the MU group leader, and mesh nodes B, E, and F can be members (because they send traffic to mesh node A). In the fourth MU association group (for UL MU-MIMO), mesh node E can be the MU group leader, and mesh nodes B, D, and F can be members.

[0110] Alternatively or additionally, the formation of MU association groups can be based on the number of incoming or outgoing hops. For example, mesh node B sends traffic to 3 target mesh nodes, which is more than some other mesh nodes sending traffic to 2 target mesh nodes. Therefore, the device can form a fifth MU association group (for DL ​​traffic), which includes mesh node B as the MU group leader and mesh nodes A, C, and E as members. Mesh nodes A and E each receive traffic from 3 source mesh nodes. Since mesh nodes A and E have already been designated as MU group leaders for UL traffic (the third and fourth MU association groups described in the previous paragraph), the device may not create additional MU association groups that would be redundant with an already created MU association group. However, if they have not yet been designated as MU group leaders for UL traffic, the device can create a new MU association group.

[0111] As described in this article, MU association groups can be formed based on traffic volume or the number of incoming or outgoing links. Other criteria based on traffic conditions can be used to select the MU group leader and designate the members of the MU association group.

[0112] Example based on capacity bottleneck

[0113] Another technique for forming MU association groups can be based on detecting mesh nodes performing at full capacity and assigning them as MU group leaders for MU association groups supporting MU-MIMO. For example, the device can compare the total traffic handled by the mesh nodes with the radio channel capacity. The capacity can be related to the physical layer (PHY) transmission rate of the radio channel between the mesh nodes and their peer mesh nodes. Equation (1) shows an example calculation for determining the effective capacity. In Equation (1),

[0114]

[0115] PHYRate indicates the physical layer transmission rate of the wireless channel, airTimeOccupied represents the amount of airtime occupied within the totalTimeofMeasurement period, and overheadDiscount can be derived from empirical data and can be used as an adjustment factor in formula (1).

[0116] This device can select the mesh node to act as the MU group leader based on a comparison of the corresponding effective capacity and actual utilization of the mesh nodes. Equation (2) shows an example comparison. In Equation (2),

[0117] effectiveCapacity(i)<=ActualServicedRate(i) (2)

[0118] The ActualServicedRate can be based on measured actual UL or DL ​​traffic, and i represents an index so that the formula can be calculated for i mesh nodes.

[0119] Besides formula (2), other criteria can be used to select the leader of the MU group. For example, formula (3) includes another criterion that can be used in conjunction with formula (1). In formula (3),

[0120] ChannelIdleTime <ThresholdPercentageOfTotalTime (3)

[0121] ChannelIdleTime indicates the amount of time a wireless channel is idle, and ThresholdPercentageOfTotalTime can be a threshold parameter. In some implementations, ThresholdPercentageOfTotalTime can be based on experiments after discounting the average expected contention backoff time (e.g., 2%). ChannelIdleTime can serve as an indicator of the activity level (such as load) in a mesh network. If ChannelIdleTime is large (e.g., 5% of the total observation window) and one of the mesh nodes has a capacity bottleneck, then a high ChannelIdleTime may be due to capacity-constrained burst traffic. Using Equation (2), burst traffic typically does not indicate a capacity bottleneck. Potential capacity bottlenecks can be identified by optionally using Equation (3). A combination of Equations (2) and (3) can indicate those mesh nodes that are generating capacity bottlenecks and will benefit from using MU association groups to utilize constrained wireless channel resources more efficiently.

[0122] In some implementations, in addition to the capacity comparisons shown in equations (1)-(3), the device can also use the number of serving mesh nodes. For example, the device can select a mesh node as the MU group leader when the mesh node's ActualServicedRate(i)*NumberOfNodesServiced(i) (actual service rate (i)*number of serving nodes (i)) is the largest among the contending nodes (referred to as Condition 1). NumberofNodesServiced(i) can represent the number of mesh nodes receiving traffic from the i-th mesh node.

[0123] In some implementations, the device can select a MU group leader when equations (2) and (3) hold and condition 1 is satisfied. Members of the MU association group can be assigned based on their corresponding peer relationships with the mesh nodes selected as MU group leaders.

[0124] Weight-based examples

[0125] Another technique for forming MU (Mesh Association) groups can be based on weights to determine the mesh nodes that will benefit most from using MU group communication. For example, mesh parameters can be used to identify mesh nodes that form potential bottlenecks or experience high traffic loads. In some implementations, candidate mesh nodes can be identified even if there is no ongoing active traffic in the mesh. Example parameters that can be used to identify such mesh nodes could be based on proximity to the mesh portal or on routing topology.

[0126] Mesh nodes that are located in the same area or connected to a mesh portal (such as a WAN interface) can be assigned higher weights. Similarly, mesh nodes adjacent to mesh nodes with WAN interfaces can be assigned higher weights compared to mesh nodes not adjacent to a mesh portal. See reference. Figure 8 For example, mesh nodes D and F can be assigned the highest weight values ​​because they are connected to other networks 581 and 582. Mesh nodes A, C, and E can be assigned weight values ​​lower than mesh nodes D and F but higher than mesh node B because mesh nodes A, C, and E are one hop away from mesh nodes D and F. Therefore, in some implementations, weight values ​​can be based on the number of hops to the mesh portal, so that the highest weight is assigned to those mesh nodes with the fewest hops.

[0127] Weight values ​​can be based on routing topology. Mesh nodes that form traffic routing points for more mesh nodes can be assigned higher weights compared to other mesh nodes that provide traffic routing for a smaller number of mesh nodes. A mesh node's weight can increase proportionally to how many routes are directed to or from that mesh node. In some implementations, mesh nodes can exchange routing table or route entry counts to determine which mesh nodes provide a higher degree of routing within the mesh.

[0128] Although example weighting considerations are described in this paper, other parameters can be used to determine weight values. For example, weight values ​​can be based on routing topology, resource utilization, congestion, processor speed, or the number of client STAs served, etc. After determining the weight values ​​for mesh nodes in a mesh network, the network management unit can select those mesh nodes with higher weight values ​​as candidate MU group leaders.

[0129] Figure 9An example wireless mesh network 900 is shown, where MU association groups can be associated with hop counts to a mesh gate. The wireless mesh network 900 includes three mesh nodes, labeled Mesh Node A, Mesh Node B, and Mesh Node C. All Mesh Nodes A, B, and C are peers and can communicate directly with any of the other Mesh Nodes A, B, and C. Mesh Node A has a mesh portal (or mesh gate) to enable communication with another network 980. The wireless mesh network 900 can be referred to as a single-hop (or 1-hop) network because each mesh node can have at most one hop to reach the mesh portal at Mesh Node A.

[0130] When forming a MU association group, the mesh nodes (or network management units) can determine the routing topology, such as the hop count from each mesh node A, B, and C to the mesh portal. Because mesh node A has the fewest hops (zero) to reach the mesh portal, mesh node A can be selected as the MU group leader (as UL MU-AP) of MU association group 910 for UL traffic from peer mesh nodes B and C (as UL MU-STA). This enables mesh node A to trigger and receive MU UL group communications from mesh nodes B and C.

[0131] In addition to MU Association Group 910 (for UL traffic), one or more other MU Association Groups (not shown) may exist to support MU DL communication. In some implementations, each mesh node A, B, and C may be the MU group leader for the MU Association Group for DL ​​traffic. For example, mesh node A may also be the MU group leader (as MU-AP) for MU DL communication to transmit data to mesh node B or mesh node C (as DL MU-STA operation). Mesh node B may be the MU group leader (as MU-AP) for MU DL communication to transmit data to mesh node A or mesh node C (as DL MU-STA operation). Mesh node C may be the MU group leader (as MU-AP) for MU DL communication to transmit data to mesh node A or mesh node B (as DL MU-STA operation).

[0132] In some implementations, the formation of MU association groups can be constrained to avoid conflicts between MU association groups for DL ​​MU communication and UL MU communication. For example, when certain preconditioning conditions are met, mesh nodes may include peer mesh nodes with smaller hop counts to the mesh portal in their DL MU communication. Consider Figure 9In the example, a transmission from mesh node B to mesh node A can be sent as UL MU communication (triggered by mesh node A in MU association group 910) or as DL MU communication (scheduled by mesh node B in a different MU association group). Utilizing UL MU communication is preferred because mesh node A provides services as a mesh portal to multiple mesh nodes in the wireless mesh network 900. Therefore, mesh node B can conditionally limit the use of DL MU communication. Example conditions may include: mesh node A not frequently triggering UL MU communication (or not frequently enough to meet traffic load), mesh node B having sufficient traffic for both mesh node A and mesh node C, or a combination of both.

[0133] Furthermore, as described elsewhere, some communications can occur regardless of the MU association group. For example, UL OFDMA block acknowledgments or other control frames can be transmitted between peer mesh nodes, regardless of the MU association group. Single-user acknowledgments or data frame types can be transmitted or triggered separately by peer mesh nodes in communication with the MU group.

[0134] Figure 10 Another example wireless mesh network 1000 and an example MU association group associated with hop counts to a mesh gate are shown. Wireless mesh network 1000 includes seven mesh nodes, labeled mesh node A, mesh node B, mesh node C, mesh node D, mesh node E, mesh node F, and mesh node G. Mesh nodes A, B, and C are peers and can communicate directly with any of the other mesh nodes A, B, and C. Mesh nodes B, D, and E are peers and can communicate directly with any of the other mesh nodes B, D, and E. Mesh nodes C, G, and F are peers and can communicate directly with any of the other mesh nodes C, G, and F. Mesh node A has a mesh portal (or mesh gate) to enable communication with another network 1080. Wireless mesh network 1000 may be referred to as a multi-hop network because some mesh nodes D, E, F, and G may have more than one hop to reach the mesh portal at mesh node A.

[0135] Mesh nodes (or network management units) can determine the routing topology, such as the hop count from each mesh node A, B, C, D, E, F, and G to the mesh portal. Because mesh node A has the fewest hops (zero) to reach the mesh portal, mesh node A can be selected as the MU group leader (as UL MU-AP) of the first MU association group 1010 for UL traffic from peer mesh nodes B and C (as UL MU-STAs). Continuing with the mesh nodes having the fewest hops to the mesh portal, mesh nodes B and C can also be selected as MU group leaders of the second MU association group 1020 and the third MU association group 1030, respectively. Example MU association groups 1010, 1020, and 1030 are designated for UL MU communication such that the corresponding MU group leaders (mesh nodes A, B, and C, respectively) can trigger and receive UL MU communication from their respective peer mesh nodes in MU association groups 1010, 1020, and 1030.

[0136] In addition to MU association groups 1010, 1020, and 1030 (for UL traffic), one or more other MU association groups (not shown) may exist to support MU DL communication. In some implementations, each mesh node A, B, C, D, E, F, and G can be a MU group leader for the MU association group for DL ​​traffic to its corresponding peer mesh node. When two nodes are members of overlapping UL MU association groups and DL MU association groups, refer to... Figure 9 The same constraints described can be used to determine whether to use the DL MU association group or the UL MU association group.

[0137] The routing topology of a wireless mesh network may change occasionally, such as when a new mesh node joins the wireless mesh or when an existing mesh node leaves the wireless mesh. Each mesh node can determine its hop count to the mesh portal and the corresponding hop count of each peer mesh node to the mesh portal. For example, each mesh node can use discovery or announcement messages (such as those defined in the IEEE 1905 specification) to indicate its hop count. A mesh node can determine which of its peer mesh nodes has the fewest hops to the mesh portal and select that peer mesh node as its UL MU-AP. In some implementations, a mesh node can send a message to the selected UL MU-AP requesting to join a UL MU association group in which the UL MU-AP is the MU group leader. The selected UL MU-AP can approve the request to join the UL MU association group and send the mesh node an acknowledgment message confirming that the mesh node is in a UL MU association group managed by that UL MU-AP. In some implementations, each mesh node can select a single peer mesh node as its UL MU-AP to enable traffic optimization over UL MU associated groups via a wireless mesh network.

[0138] Figure 11 A conceptual diagram of an example MU association group setup or configuration message 1100 is shown. For example, this message could be an example of an MU association group setup or configuration message 1100 transmitted from one mesh node to another or to a network management unit. The message format may depend on the sender and receiver. Different fields or information elements may be included in the frame body 1110 of the MU association group setup or configuration message 1100 at various stages of organizing the MU association group.

[0139] The MU association group setup or configuration message 1100 can be used to convey parameters that can be used to determine the MU association group in a wireless mesh network. Figure 11 This includes example data frame 1120. Data frame 1120 may include a preamble 1122, a frame header 1124, a frame body 1110, and a frame check sequence (FCS) 1126. The preamble 1122 may include one or more bits used to establish synchronization. The frame header 1124 may include source and destination network addresses (such as the network address of a mesh node or network management unit), the length of the data frame, or other frame control information. The frame body 1110 may be organized in a message format and may include various fields or information elements 1132, 1136, and 1138. In some implementations, data frame 1120 may be an IEEE 802.11s configuration frame, a management frame, an IEEE 1905 policy configuration message, or an IEEE 802.11k message, etc.

[0140] Example information element in Figure 11 As shown in the figure. Some example information elements 1160 may be included in report messages from one mesh node to another or to the network management unit. Example information elements 1160 may include traffic information 1161, candidate MU association group 1162, current MU association group 1164, MU participation constraints 1166, topology or routing information 1168, or effective capacity 1172. For example, effective capacity 1172 may be calculated by each mesh node according to example formula (1) and reported to the network management unit.

[0141] Some example information elements 1180 may be included in control messages from the network management unit to the mesh nodes. Example information element 1180 may include aggregated traffic or topology information 1181 to assist mesh nodes in identifying candidate MU association groups. Example information element 1180 may include MU group assignment 1182. MU group assignment 1182 may be sent to all mesh nodes in the wireless mesh network or to those mesh nodes that have already been assigned to MU association groups in MU group assignment 1182. MU group assignment 1182 may indicate the MU technology type (OFDMA or MU-MIMO), MU group leader, and member list in each MU association group.

[0142] Figure 12 A block diagram of an example wireless communication device 1200 is shown. In some implementations, the wireless communication device 1200 may be an example of a device for use in a mesh node, such as those described above. Figure 1 , 2 Any of the network STAs 110, 112, 114, 116, 118, 122, 210, 212, 218 and 410 described in 4, or refer to Figure 5 and 8 Any of the mesh nodes AF described. The wireless communication device 1200 is capable of transmitting and receiving wireless communications, for example, in the form of wireless packets. For example, the wireless communication device may be configured to transmit and receive packets in the form of Physical Layer Convergence Protocol (PLCP) Protocol Data Units (PPDUs) and Media Access Control (MAC) Protocol Data Units (MPDUs) conforming to IEEE 802.11 wireless communication protocol standards (such as those defined by the IEEE 802.11-2016 specification or its amendments, including but not limited to 802.11s, 802.11ay, 802.11ax, 802.11az, 802.11ba, and 802.11be).

[0143] Wireless communication device 1200 may be or may include a chip, system-on-a-chip (SoC), chipset, package, or device that includes one or more modems 1202 (e.g., a Wi-Fi (compliant with IEEE 802.11) modem). In some implementations, the one or more modems (collectively referred to as "Modem 1202") additionally include a WWAN modem (e.g., a 3GPP 4G LTE or 5G compliant modem). In some implementations, wireless communication device 1200 also includes a processing system. The processing system may also be referred to as processor 1204 and may include one or more processors, processing blocks, or processing elements coupled to modem 1202, and one or more memories, memory blocks, or memory elements. In some implementations, wireless communication device 1200 additionally includes one or more radios (collectively referred to as "Radio 1206") coupled to modem 1202. In some implementations, wireless communication device 1200 further includes one or more memory blocks or elements (collectively referred to as "Memory 1208") coupled to processor 1204 or modem 1202.

[0144] Modem 1202 may include intelligent hardware blocks or devices (e.g., application-specific integrated circuits (ASICs)). Modem 1202 is generally configured to implement the PHY layer, and in some implementations also implements a portion of the MAC layer (e.g., the hardware portion of the MAC layer). For example, modem 1202 is configured to modulate packets and output modulated packets to radio 1206 for transmission over a wireless medium. Similarly, modem 1202 is configured to receive modulated packets received by radio 1206 and demodulate these packets to provide demodulated packets. In addition to modulators and demodulators, modem 1202 may further include digital signal processing (DSP) circuitry, automatic gain control (AGC) circuitry, encoders, decoders, multiplexers, and demultiplexers. For example, when in transmission mode, data obtained from processor 1204 may be provided to an encoder, which encodes the data to provide encoded bits. The encoded bits may be mapped to several (N) SS (N) spatial flows for spatial reuse or several (N) STS( ) space-time streams for space-time block coding (STBC). The encoded bits in each stream can be mapped (using a selected MCS) to points in a modulation constellation to provide modulated symbols. The modulated symbols in the corresponding space or space-time stream can be multiplexed, transformed via an inverse fast Fourier transform (IFFT) block, and subsequently fed to a DSP circuitry (e.g., for Tx windowing and filtering). The digital signal can be fed to a digital-to-analog converter (DAC). The resulting analog signal can be fed to an upconverter and ultimately to radio 1206. In implementations involving beamforming, the modulated symbols in the corresponding space streams are pre-coded via a guiding matrix before being fed to the IFFT block.

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

[0146] Radio 1206 generally includes at least one radio frequency (RF) transmitter (or “transmitter chain”) and at least one RF receiver (or “receiver chain”), which may be combined into one or more transceivers. For example, each of the RF transmitter and receiver may include various analog circuitry systems, including at least one power amplifier (PA) and at least one low-noise amplifier (LNA), respectively. The RF transmitter and receiver may further be coupled to one or more antennas. For example, in some implementations, wireless communication device 1200 may include or be coupled to multiple transmit antennas (each with a corresponding transmit chain) and multiple receive antennas (each with a corresponding receive chain). Symbols output from modem 1202 are provided to radio 1206, which transmits the symbols via the coupled antennas. Similarly, symbols received via the antennas are acquired by radio 1206, which provides the symbols to modem 1202.

[0147] Processor 1204 may include intelligent hardware blocks or devices designed to perform the functions described herein, such as, for example, processing cores, processing blocks, central processing units (CPUs), microprocessors, microcontrollers, digital signal processors (DSPs), application-specific integrated circuits (ASICs), programmable logic devices (PLDs) (such as field-programmable gate arrays (FPGAs)), discrete gate or transistor logic, discrete hardware components, or any combination thereof. Processor 1204 processes information received via radio 1206 and modem 1202, and processes information to be output via modem 1202 and radio 1206 for transmission over a wireless medium. For example, processor 1204 may implement a control plane and at least a portion of a MAC layer configured to perform various operations related to the generation, transmission, reception, and processing of MPDUs, frames, or packets. In some implementations, the MAC layer is configured to: generate MPDUs for encoding by a PHY layer, and receive decoded information bits from the PHY layer for processing as MPDUs. The MAC layer may be further configured to allocate time and frequency resources, for example, for OFDMA, or other operations or techniques. In some implementations, processor 1204 can typically control modem 1202 to cause the modem to perform the various operations described above.

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

[0149] Figure 13 A block diagram of an example mesh node 1300 is shown. In some implementations, the example mesh node 1300 may be an example of a mesh node, such as those referred to respectively. Figure 1 , 2 Any one of the mesh STAs 110, 112, 114, 116, 118, 122, and 214 described in section 4, or any one of the mesh nodes 210, 212, 218, 410, 420, and 440, or refer to Figure 5 and 8 Any of the mesh nodes AF described herein. Mesh node 1300 includes wireless communication device (WCD) 1310 (although mesh node 1300 itself may also be referred to as wireless communication device, as used herein). For example, wireless communication device 1310 may be a reference Figure 12 The described wireless communication device 1200 is an example implementation. Mesh node 1300 may also include a plurality of antennas 1320 coupled to wireless communication device 1310 for transmitting and receiving wireless communications. In some implementations, mesh node 1300 additionally includes an application processor 1330 coupled to wireless communication device 1310, and a memory 1340 coupled to application processor 1330.

[0150] In some implementations, mesh node 1300 may include an external network interface (not shown) that enables mesh node 1300 to communicate with a core network or backhaul network to obtain access to external networks, including the Internet. For example, the external network interface may include one or both of a wired (e.g., Ethernet) network interface and a wireless network interface (such as a WWAN interface). Components of the foregoing can communicate directly or indirectly with other components of these components on at least one bus. Mesh node 1300 further includes a housing that encloses at least portions of wireless communication device 1310, application processor 1330, memory 1340, and antenna 1320.

[0151] Figure 14A flowchart illustrating an example process 1400 for implementing MU group communication in a wireless mesh network is shown. The operation of process 1400 can be implemented by the network management unit, mesh nodes, centralized resources, or any component thereof, as described herein. For example, process 1400 can be implemented by a network management unit (such as referenced...) Figure 5 The described network management unit 590) is used to execute this process. In some implementations, process 1400 (or parts thereof) can be executed by mesh nodes, such as those referring to... Figure 1 , 2 The mesh node 210, 212, 218, 410, mesh node AF, mesh node 1300, or mesh node 1700 described in 4, 5, 8, 13, and 17. In some implementations, process 1400 may be performed by a component of the mesh node, such as the one described in reference 4.5 ... Figure 1 One of the described mesh STAs 110, 112, 114, 116, 118, and 122. For the sake of brevity, example process 1400 is described as being performed by a device that can be any of the network management unit, mesh node, mesh STA, or components thereof indicated above.

[0152] In block 1410, the device can communicate in a wireless mesh network comprising multiple mesh nodes. In block 1420, the device can establish at least a first multi-user (MU) association group, the first MU association group comprising a first mesh node and one or more peer mesh nodes among the plurality of mesh nodes. The first MU association group enables the first mesh node to act as an MU group leader to allocate wireless channel resources for MU communication between the first mesh node forming the first MU association group and at least a subset of the one or more peer mesh nodes.

[0153] Figure 15 A flowchart illustrating another example process 1500 for a mesh node used to support MU group communication in a wireless mesh network is shown. The operation of process 1500 can be implemented by a mesh node or any of its components as described herein. For example, process 1500 can be implemented by referring to [reference to...] Figure 1 , 2 The process 1500 may be executed by any of the mesh nodes 210, 212, 218, 410, mesh node AF, mesh node 1300, or mesh node 1700 described in 4, 5, 8, 13, and 17. In some implementations, the process 1500 may be executed by a component of the mesh node, such as the one described in reference 4.5.8.8.8.8.8.8.8.9 ... Figure 1 One of the described mesh STAs 110, 112, 114, 116, 118, and 122. For the sake of brevity, example process 1500 is described as being performed by a device that can be any of the mesh nodes, mesh STAs, or components thereof indicated above.

[0154] In block 1510, the device can operate as a MU group leader for a first multi-user (MU) association group, which includes the device (first mesh node) and one or more peer mesh nodes in the wireless mesh. In block 1520, the device can allocate radio channel resources for MU group communication between the first mesh node forming the first MU association group and at least a subset of the one or more peer mesh nodes.

[0155] Figure 16 A flowchart illustrating another example process 1600 for a mesh node used to support MU group communication in a wireless mesh network is shown. The operation of process 1600 can be implemented by a mesh node or any of its components as described herein. For example, process 1600 can be implemented by referring to [reference to...] Figure 1 , 2 The process 1600 may be executed by any of the mesh nodes 210, 212, 218, 410, mesh node AF, mesh node 1300, or mesh node 1700 described in 4, 5, 8, 13, and 17. In some implementations, the process 1600 may be executed by a component of the mesh node, such as the one described in reference 4.5.8.8.8.8.8.8.8.8.9 ... Figure 1 One of the described mesh STAs 110, 112, 114, 116, 118, and 122. For the sake of brevity, example process 1600 is described as being performed by a device that can be any of the mesh nodes, mesh STAs, or components thereof indicated above.

[0156] In block 1610, the device can communicate with multiple mesh nodes in a wireless mesh network. In block 1620, the device can receive configuration for at least a first multi-user (MU) association group, which includes a second mesh node acting as the MU group leader and at least a first mesh node. In block 1630, the device can use wireless channel resources managed by the second mesh node to transmit a portion of the first MU group communication to the second mesh node, the first MU group communication including transmissions from one or more mesh nodes.

[0157] Figure 17A block diagram of an example electronic device for implementing various aspects of this disclosure is shown. In some implementations, electronic device 1700 may be a WLAN device, including any of the WLAN devices described herein. Electronic device 1700 may include a processing system 1702 (potentially including a single processor, multiple processors, multiple cores, multiple nodes, or implementing multithreading, etc.). Electronic device 1700 may also include memory 1706. Memory 1706 may be system memory or any of the possible implementations of the computer-readable media described herein. In some implementations, processing system 1702 may include memory 1706. Electronic device 1700 may also include a bus 1710 (such as PCI, ISA, PCI-Express, Hyper-...). AHB, AXI, etc.) and network interface 1704, the network interface 1704 may include wireless network interface (such as WLAN interface, ... interface, interface, The device 1700 may have at least one of a network interface (such as a wireless USB interface, etc.) and a wired network interface (such as an Ethernet interface, a powerline communication interface, etc.). In some implementations, the device 1700 may support multiple network interfaces—each of which is configured to couple the device 1700 to a different communication network.

[0158] Electronic device 1700 may include a mesh STA module 1760 configured to establish or join an MBSS with peer mesh nodes. Electronic device 1700 may include a mesh MU communication module 1770 configured to operate network management functions or communicate with another mesh node operating external network management functions. Mesh MU communication module 1770 may determine MU association groups or may provide information to external network management functions to help determine MU association groups. In some implementations, electronic device 1700 may include a mesh point module 1780. Mesh point module 1780 may be configured to establish an IBSS and operate as an access point for non-mesh STAs in the IBSS. Mesh point module 1780 may include mesh gating or other functionality to translate communication between the MBSS and the IBSS. Although described as separate components, mesh STA module 1760, mesh MU communication module 1770, mesh point module 1780, or any combination thereof may be implemented within network interface 1704, memory 1706, or processing system 1702.

[0159] Memory 1706 may include computer instructions that can be executed by processing system 1702 to implement... Figures 1 to 16The functionality of each implementation described herein. Any of these functionalities may be implemented partially (or entirely) in hardware or on the processing system 1702. For example, the functionality may be implemented using an application-specific integrated circuit, in logic implemented in the processing system 1702, in a coprocessor on a peripheral device or card, etc. Furthermore, each implementation may include fewer components or include Figure 15 Additional components not described herein (such as video cards, audio cards, additional network interfaces, peripheral devices, etc.). Processing system 1702, memory 1706, and network interface 1704 are coupled to bus 1710. Although described as coupled to bus 1710, memory 1706 may also be coupled to processing system 1702.

[0160] Figure 1-17 The operations described herein are examples intended to aid in understanding the exemplary implementations and should not be used to limit potential implementations or the scope of the claims. Some implementations may perform additional operations, perform fewer operations, perform operations in parallel or in a different order, or perform some operations differently.

[0161] The foregoing disclosure provides explanations and descriptions, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the foregoing disclosure or may be obtained through practice of the aspects. While aspects of this disclosure have been described by way of various examples, any combination of aspects from any of these examples is also within the scope of this disclosure. The examples in this disclosure are provided for illustrative purposes. As a replacement or supplement to the other examples described herein, the examples include any combination of the following implementation options (enumerated as terms for brevity).

[0162] Clause 1. A method for wireless communication, comprising: communicating in a wireless mesh network including a plurality of mesh nodes; and establishing at least a first multi-user (MU) association group, the first MU association group including a first mesh node among the plurality of mesh nodes and one or more peer mesh nodes, the first MU association group enabling the first mesh node to act as an MU group leader to allocate wireless channel resources for MU communication between the first mesh node forming the first MU association group and at least a subset of one or more peer mesh nodes.

[0163] Clause 2. The method of Clause 1, wherein establishing the at least first MU association group includes transmitting instructions to the one or more peer mesh nodes regarding their roles as members of the first MU association group.

[0164] Clause 3. The method of any of Clauses 1-2, wherein establishing the at least first MU association group includes selecting a first mesh node as the MU group leader of the first MU association group based on the routing topology of the wireless mesh network.

[0165] Clause 4. The method of Clause 3, wherein establishing the at least first MU association group further comprises: selecting a first mesh node as the leader of the MU group to manage the first MU association group based on the routing topology and traffic flow information; and selecting the one or more peer mesh nodes as members of the first MU association group based on the corresponding peering relationship between the one or more peer mesh nodes and the first mesh node.

[0166] Clause 5. The method of Clause 4, wherein establishing the at least first MU association group further comprises: obtaining the routing topology of the wireless mesh network based on path selection protocol messages; and obtaining traffic flow information regarding traffic between the first mesh node and the one or more peer mesh nodes.

[0167] Clause 6. The method of Clause 5, wherein obtaining the traffic flow information comprises: sending a request to each of the one or more peer mesh nodes for a traffic report message; and receiving the traffic report message from each of the one or more peer mesh nodes in response to the request, the traffic report message comprising the traffic flow information measured by each of the one or more peer mesh nodes.

[0168] Clause 7. The method of any of Clauses 3-6, wherein selecting a first mesh node as the MU group leader comprises: selecting the first mesh node as the MU group leader of the first MU associated group based on at least one condition from a group comprising: determining that the first mesh node has the highest traffic load among the plurality of mesh nodes not yet assigned as MU group leaders; determining that the first mesh node generates the highest capacity bottleneck in the radio mesh network among the plurality of mesh nodes not yet assigned as MU group leaders; determining that the first mesh node receives traffic from the highest number of source mesh nodes among the plurality of mesh nodes not yet assigned as MU group leaders; determining that the first mesh node has the highest weight value among the weight values ​​for the plurality of mesh nodes; and any combination thereof.

[0169] Clause 8. The method of any one of Clauses 3-6, wherein selecting the first mesh node as the MU group leader comprises: selecting the first mesh node as the MU group leader of the first MU associated group based on at least one condition from a group comprising: the first mesh node having the lowest hop count to the mesh portal compared to the hop count between the first mesh node and each of the plurality of mesh nodes, the first mesh node having the highest number of incoming or outgoing routes compared to the number of incoming or outgoing routes for each of the plurality of mesh nodes in the routing table for the wireless mesh network, and a weighted combination thereof.

[0170] Clause 9. The method of any one of Clauses 1-8 further comprises: receiving candidate MU association groups determined by each mesh node of the wireless mesh network; and selecting a first mesh node as the MU group leader of the first MU association group based on the candidate MU association groups.

[0171] Clause 10. The method of any one of Clauses 1-9 further includes: determining multiple MU association groups based on traffic flow information and the routing topology of the wireless mesh network, each MU association group having a corresponding MU group leader and one or more corresponding member mesh nodes.

[0172] Clause 11. The method of any one of Clauses 1-10 further comprises: determining a MU participation constraint for each of the plurality of mesh nodes, the MU participation constraint limiting the number of mesh nodes that the mesh node can manage as a MU group leader or limiting the number of MU association groups that the mesh node can participate in as a member; and selecting the plurality of MU association groups based on the MU participation constraint for each of the plurality of mesh nodes.

[0173] Clause 12. The method of any of Clauses 1-11, wherein the first mesh node operates as a network management unit of the wireless mesh network or is located in the same place as the network management unit.

[0174] Clause 13. A method for wireless communication by a first mesh node of a wireless mesh network, comprising: operating as a MU group leader of a first multi-user (MU) association group, the first MU association group including the first mesh node and one or more peer mesh nodes in the wireless mesh network; and allocating wireless channel resources by the first mesh node for MU group communication between the first mesh node forming the first MU association group and at least a subset of the one or more peer mesh nodes.

[0175] Clause 14. The method of Clause 13, wherein managing these wireless channel resources includes allocating these wireless channel resources based on multi-user communication technologies different from wireless mesh protocols.

[0176] Clause 15. The method of any one of Clauses 13-14, wherein managing these radio channel resources includes: transmitting the MU group communication from a first mesh node to the at least one subset of the one or more peer mesh nodes, the MU group communication including: concurrent downlink transmission of dissimilar data for each peer mesh node in the at least one subset of the one or more peer mesh nodes.

[0177] Clause 16. The method of any one of Clauses 13-15, wherein managing the radio channel resources comprises: allocating the radio channel resources to the at least one subset of the one or more peer mesh nodes, wherein uplink transmissions of dissimilar data are to be received concurrently from each peer mesh node in the at least one subset of the one or more peer mesh nodes; and receiving the MU group communication having the dissimilar data via the allocated radio channel resources corresponding to each peer mesh node in the at least one subset of the one or more peer mesh nodes.

[0178] Clause 17. The method of any one of Clauses 13-16 further includes: formatting the MU group communication between the first mesh node and a subset of the one or more peer mesh nodes as MU multiple-input multiple-output (MU-MIMO) transmission or orthogonal frequency division multiple access (OFDMA) transmission.

[0179] Clause 18. The method of Clause 17, wherein when the traffic type of the first MU associated group is capacity sensitive, the MU group communication is MU-MIMO transmission, and wherein when the traffic type of the first MU associated group is latency sensitive, the MU group communication is OFDMA transmission.

[0180] Clause 19. A method performed by a first mesh node in a wireless mesh network, comprising: communicating with a plurality of mesh nodes in the wireless mesh network; receiving configuration for at least a first multi-user (MU) association group, the first MU association group including a second mesh node as a MU group leader and at least the first mesh node; and using wireless channel resources managed by the second mesh node to transmit a portion of the first MU group communication to the second mesh node, the first MU group communication including transmissions from one or more mesh nodes.

[0181] Clause 20. The method of Clause 19 further includes: receiving a request for a traffic report message from a network management unit; and sending the traffic report message to the network management unit in response to the request, the traffic report message including traffic flow information measured by the first mesh node, and the traffic flow information being usable by the network management unit to assign the first mesh node to the first MU association group.

[0182] Clause 21. The method of any one of Clauses 19-20 further comprises: sending one or more candidate MU association groups from a first mesh node to a network management unit based on traffic flow information and the routing topology of the wireless mesh network, wherein the configuration for the first MU association group is based on the one or more candidate MU association groups.

[0183] Clause 22. The method of any one of Clauses 19-21 further includes: receiving configuration for a second MU association group including a first mesh node; using radio channel resources managed by the second mesh node to communicate traffic associated with the first MU association group via the first MU group; and using radio channel resources managed by the MU group leader of the second MU association group to communicate traffic associated with the second MU association group via the second MU group.

[0184] Clause 23. The method of Clause 22, wherein the first mesh node is the MU group leader of the second MU association group, the method further comprising: the first mesh node, as the MU group leader of the second MU association group, managing the radio channel resources associated with second MU group communication between the first mesh node and one or more peer mesh nodes in the second MU association group.

[0185] Clause 24. A first mesh node, comprising: at least one modem configured to communicate in a wireless mesh network including a plurality of mesh nodes; and a processing system configured to: establish at least a first multi-user (MU) association group, the first MU association group including the first mesh node and one or more peer mesh nodes among the plurality of mesh nodes, the first MU association group enabling the first mesh node to act as an MU group leader to allocate wireless channel resources for MU communication between the first mesh node forming the first MU association group and at least a subset of the one or more peer mesh nodes.

[0186] Clause 25. The first mesh node as in Clause 24, wherein the at least one modem is configured to output an indication of the role of the one or more peer mesh nodes as members of the first MU association group for transmission to the one or more peer mesh nodes.

[0187] Clause 26. The first mesh node as described in any of Clauses 24-25, wherein the processing system is configured to select the first mesh node as the MU group leader of the first MU association group based on the routing topology of the wireless mesh network.

[0188] Clause 27. The first mesh node as in Clause 26, wherein the processing system is further configured to: select the first mesh node as the MU group leader to manage the first MU association group based on the routing topology and the traffic flow information; and select the one or more peer mesh nodes as members of the first MU association group based on the corresponding peering relationship between the one or more peer mesh nodes and the first mesh node.

[0189] Clause 28. The first mesh node as described in Clause 27, wherein the processing system is further configured to: obtain the routing topology of the wireless mesh network based on path selection protocol messages obtained by the at least one modem; and determine traffic flow information regarding traffic between the first mesh node and the one or more peer mesh nodes.

[0190] Clause 29. The first mesh node as described in Clause 28, wherein the at least one modem is configured to: output a request for a traffic report message to each of the one or more peer mesh nodes; and, in response to the request, obtain the traffic report message from each of the one or more peer mesh nodes, the traffic report message including traffic flow information measured by each of the one or more peer mesh nodes.

[0191] Clause 30. A first mesh node as described in any of Clauses 26-29, wherein the processing system is configured to: select a first mesh node as the MU group leader of a first MU associated group based on at least one condition from a group comprising: determining that the first mesh node has the highest traffic load among the plurality of mesh nodes not yet assigned as MU group leaders; determining that the first mesh node generates the highest capacity bottleneck in the wireless mesh network among the plurality of mesh nodes not yet assigned as MU group leaders; determining that the first mesh node receives traffic from the highest number of source mesh nodes among the plurality of mesh nodes not yet assigned as MU group leaders; determining that the first mesh node has the highest weight value among the weight values ​​for the plurality of mesh nodes; and any combination thereof.

[0192] Clause 31. A first mesh node as described in any of Clauses 26-29, wherein the processing system is configured to select the first mesh node as the MU group leader of the first MU association group based on at least one condition from a group comprising: the first mesh node having the lowest hop count to the mesh portal compared to the hop count between the first mesh node and each of the plurality of mesh nodes; the first mesh node having the highest number of incoming or outgoing routes in the routing table for the wireless mesh network compared to the number of incoming or outgoing routes for each of the plurality of mesh nodes, and a weighted combination thereof.

[0193] Clause 32. The first mesh node as described in any of Clauses 24-31, wherein the at least one modem is configured to: obtain candidate MU association groups determined by the respective mesh nodes from the wireless mesh network; and wherein the processing system is configured to select the first mesh node as the MU group leader of the first MU association group based on the candidate MU association groups.

[0194] Clause 33. The first mesh node as in any of Clauses 24-32, wherein the processing system is configured to: determine multiple MU association groups based on traffic flow information and the routing topology of the wireless mesh network, each MU association group having a corresponding MU group leader and one or more corresponding member mesh nodes.

[0195] Clause 34. The first mesh node as described in any of Clauses 24-33, wherein the processing system is configured to: determine a MU participation constraint for each of the plurality of mesh nodes, the MU participation constraint limiting the number of mesh nodes that the mesh node can manage as a MU group leader or limiting the number of MU association groups that the mesh node can participate in as a member; and select the plurality of MU association groups based on the MU participation constraint for each of the plurality of mesh nodes.

[0196] Clause 35. The first mesh node as described in any of Clauses 24-34, wherein the first mesh node operates as the network management unit of the wireless mesh network or is located in the same place as the network management unit.

[0197] Clause 36. The first mesh node of any of Clauses 24-35 further comprises: at least one transceiver coupled to the at least one modem; at least one antenna coupled to the at least one transceiver to wirelessly transmit signals output from the at least one transceiver and wirelessly receive signals to be input to the at least one transceiver; and a housing that encloses at least a portion of the processing system, the at least one modem, the at least one transceiver and the at least one antenna.

[0198] Clause 37. A first mesh node comprising: at least one modem configured to operate as a MU group leader of a first multi-user (MU) association group, the first MU association group including the first mesh node and one or more peer mesh nodes in the wireless mesh network; and a processing system configured to allocate wireless channel resources for MU group communication between the first mesh node forming the first MU association group and at least a subset of the one or more peer mesh nodes.

[0199] Clause 38. The method of Clause 37, wherein the processing system is configured to allocate these wireless channel resources based on a multi-user communication technology different from the wireless mesh network protocol.

[0200] Clause 39. A first mesh node as described in any of Clauses 37-38, wherein the at least one modem is configured to output the MU group communication from the first mesh node to the at least one subset of the one or more peer mesh nodes, the MU group communication comprising concurrent downlink transmissions of dissimilar data for each peer mesh node in the at least one subset of the one or more peer mesh nodes.

[0201] Clause 40. A first mesh node as described in any of Clauses 37-39, wherein the processing system is configured to: allocate radio channel resources to the at least one subset of the one or more peer mesh nodes, in which uplink transmissions of dissimilar data are to be received concurrently from each peer mesh node in the at least one subset of the one or more peer mesh nodes; and wherein the at least one modem is configured to obtain the MU group communication having the dissimilar data via the allocated radio channel resources corresponding to each peer mesh node in the at least one subset of the one or more peer mesh nodes.

[0202] Clause 41. The first mesh node as described in any of Clauses 37-40, wherein the at least one modem is configured to format the MU group communication between the first mesh node and a subset of the one or more peer mesh nodes as MU multiple-input multiple-output (MU-MIMO) transmission or orthogonal frequency division multiple access (OFDMA) transmission.

[0203] Clause 42. The first mesh node as in Clause 41, wherein when the traffic type of the first MU associated group is capacity sensitive, the MU group communication is MU-MIMO transmission, and wherein when the traffic type of the first MU associated group is latency sensitive, the MU group communication is OFDMA transmission.

[0204] Clause 43. The first mesh node of any of Clauses 37-42 further comprises: at least one transceiver coupled to the at least one modem; at least one antenna coupled to the at least one transceiver to wirelessly transmit signals output from the at least one transceiver and wirelessly receive signals to be input to the at least one transceiver; and a housing that encloses at least a portion of the processing system, the at least one modem, the at least one transceiver and the at least one antenna.

[0205] Clause 44. A first mesh node comprising: at least one modem configured to: communicate with a plurality of mesh nodes in the wireless mesh network; and obtain a configuration for at least a first multi-user (MU) association group, the first MU association group including a second mesh node as a MU group leader and at least the first mesh node; and a processing system configured to manage the first MU group communication of the at least one modem according to the configuration; and the at least one modem configured to output a portion of the first MU group communication for transmission to the second mesh node using wireless channel resources managed by the second mesh node, the first MU group communication including transmissions from one or more mesh nodes.

[0206] Clause 45. The first mesh node as described in Clause 44, wherein the at least one modem is configured to: receive a request for a traffic report message from a network management unit; and, in response to the request, output the traffic report message for transmission to the network management unit, the traffic report message including traffic flow information measured by the first mesh node, and the traffic flow information being usable by the network management unit to assign the first mesh node to a first MU association group.

[0207] Clause 46. The first mesh node as described in any of Clauses 44-45, wherein the at least one modem is configured to output one or more candidate MU association groups to the network management unit based on traffic flow information and the routing topology of the wireless mesh network, and wherein the configuration for the first MU association group is based on the one or more candidate MU association groups.

[0208] Clause 47. The first mesh node as described in any of Clauses 44-46 further comprises: the at least one modem configured to obtain a configuration for including a second MU association group; and the processing system configured to: cause the at least one modem to use radio channel resources managed by the second mesh node, which operates as the MU group leader of the first MU association group, to transmit traffic associated with the first MU association group via the first MU group communication; and cause the at least one modem to use radio channel resources managed by the MU group leader of the second MU association group to transmit traffic associated with the second MU association group via the second MU group communication.

[0209] Clause 48. The first mesh node as in Clause 47, wherein the first mesh node is the MU group leader of the second MU association group, and wherein the processing system is configured as the MU group leader of the second MU association group to manage the radio channel resources associated with second MU group communication between the first mesh node and one or more peer mesh nodes in the second MU association group.

[0210] Clause 49. The first mesh node of any of Clauses 44-48 further comprises: at least one transceiver coupled to the at least one modem; at least one antenna coupled to the at least one transceiver to wirelessly transmit signals output from the at least one transceiver and wirelessly receive signals to be input to the at least one transceiver; and a housing that encloses at least a portion of the processing system, the at least one modem, the at least one transceiver, and the at least one antenna.

[0211] Clause 50. A method performed by a network management unit of a wireless mesh network, comprising: determining a routing topology of the wireless mesh network; determining one or more characteristics of traffic among a plurality of mesh nodes in the wireless mesh network; selecting, by the network management unit, at least a first mesh node among the plurality of mesh nodes as a MU group leader of a first multi-user (MU) association group based on the determined one or more characteristics of the traffic and the determined routing topology; and assigning, by the network management unit, one or more other mesh nodes to the first MU association group based on the determined one or more characteristics of the traffic, the first MU association group enabling the MU group leader to manage MU group communication between the MU group leader and the one or more other mesh nodes, the MU group communication using MU multiple-input multiple-output (MU-MIMO) or orthogonal frequency division multiple access (OFDMA) in the wireless mesh network.

[0212] Clause 51. The method of Clause 50 further includes: notifying the first mesh node and the one or more other mesh nodes about their respective roles in the first MU association group.

[0213] Clause 52. The method of any of Clauses 50-51, wherein determining the one or more characteristics of the traffic includes receiving traffic report messages from each of the plurality of mesh nodes.

[0214] Clause 53. The method of Clause 52 further includes: sending a request for the traffic report message from the network management unit to each of the plurality of mesh nodes.

[0215] Clause 54. The method of any of Clauses 50-53 further comprises: receiving from at least a first mesh node an instruction for a first candidate MU association group in which the first mesh node is a MU group leader, wherein the selection of the first mesh node as the MU group leader of the first MU association group is further based on the instruction for the first candidate MU association group.

[0216] Clause 55. The method of any one of Clauses 50-54 further comprises: determining a plurality of MU association groups based on the one or more characteristics of the traffic and the routing topology, each of the plurality of MU association groups having an MU group leader and one or more member mesh nodes, wherein the plurality of MU association groups includes a first MU association group and at least a second MU association group, the first MU association group having a first mesh node as an MU group leader and the second MU association group having a second mesh node as an MU group leader.

[0217] Clause 56. The method of any one of Clauses 50-55 further comprises: determining a MU participation constraint for each of the plurality of mesh nodes, the MU participation constraint limiting the number of mesh nodes that the mesh node can support as a MU group leader or limiting the number of MU association groups that the mesh node can join as a member; and determining the plurality of MU association groups based on the MU participation constraint for each of the plurality of mesh nodes.

[0218] Clause 57. The method of any one of Clauses 50-56, wherein determining the plurality of MU association groups comprises: selecting a first mesh node as the MU group leader of the first MU association group based on: determining that the first mesh node has the highest traffic load among the plurality of mesh nodes that have not yet been assigned as the MU group leader, or determining that the first mesh node generates the highest capacity bottleneck in the wireless mesh network among the plurality of mesh nodes that have not yet been assigned as the MU group leader; and assigning the one or more other nodes to the first MU association group based on the corresponding peering relationship between the one or more other nodes and the first mesh node.

[0219] Clause 58. The method of any one of Clauses 50-57 further includes: determining the MU communication type of the first MU association group, wherein the MU communication type of the first MU association group is MU-MIMO based on the capacity sensitivity of the traffic of the first MU association group.

[0220] Clause 59. The method of any one of Clauses 50-58 further comprises: selecting the second mesh node as the MU group leader of the second MU association group based on: determining that the second mesh node receives traffic from the highest number of source mesh nodes among the plurality of mesh nodes not yet assigned as MU group leaders, or determining that the second mesh node generates the highest capacity bottleneck in the radio mesh network among the plurality of mesh nodes not yet assigned as MU group leaders; and assigning the source mesh node to the second MU association group based on the corresponding peering relationship between the source mesh node and the second mesh node.

[0221] Clause 60. The method of any one of Clauses 50-59 further includes: determining the MU communication type of the second MU association group, wherein the MU communication type of the second MU association group is OFDMA based on the latency sensitivity of traffic in the second MU association group.

[0222] Clause 61. The method of any one of Clauses 50-60, wherein determining the plurality of MU association groups comprises: selecting a first mesh node as the MU group leader of the first MU association group based on determining that the first mesh node has the highest weight value among the weight values ​​of the plurality of mesh nodes; and assigning the one or more other nodes to the first MU association group based on the corresponding peer relationship between the one or more other nodes and the first mesh node.

[0223] Clause 62. The method of Clause 61, wherein the weight value is based on an inverse relationship with the number of hops from each of the plurality of mesh nodes to the mesh portal, based on the number of incoming or outgoing routes for each of the plurality of mesh nodes in the routing table of the wireless mesh network, or a combination thereof.

[0224] Clause 63. The method of any of Clauses 50-62, wherein the network management unit is located in the same place as the first mesh node or the root mesh node.

[0225] Clause 64. A method performed by a first mesh node in a wireless mesh network having multiple mesh nodes, comprising: providing a network management unit with one or more characteristics of traffic between the first mesh node and one or more other mesh nodes in the wireless mesh network; and receiving from the network management unit a configuration for at least a first multi-user (MU) association group, the first MU association group including an MU group leader and one or more other mesh nodes, the first MU association group enabling the MU group leader to manage MU group communication between the MU group leader and the one or more other mesh nodes, the MU group communication using MU multiple-input multiple-output (MU-MIMO) or orthogonal frequency division multiple access (OFDMA) in the wireless mesh network.

[0226] Clause 65. The method of Clause 64 further includes: receiving a request for a traffic report message from the network management unit; and, in response to the request, sending one or more characteristics of the traffic to the network management unit in the traffic report message.

[0227] Clause 66. The method of any one of Clauses 64-65 further comprises: determining, by the first mesh node, a first candidate MU association group in which the first mesh node is a MU group leader based on one or more characteristics of the traffic and the routing topology of the wireless mesh network; and sending an instruction to the network management unit for the first candidate MU association group.

[0228] Clause 67. The method of any one of Clauses 64-66, wherein the first mesh node is a member of the first MU association group.

[0229] Clause 68. The method of any of Clauses 64-67, wherein the first mesh node is the MU group leader of the first MU associated group.

[0230] Clause 69. An apparatus for a network management unit, comprising: an interface configured to communicate with one or more mesh nodes of a wireless mesh network; and a processing system configured to: determine a routing topology of the wireless mesh network; determine one or more characteristics of traffic among a plurality of mesh nodes in the wireless mesh network; select at least a first mesh node among the plurality of mesh nodes as a MU group leader of a first multi-user (MU) association group based on the determined one or more characteristics of the traffic and the determined routing topology; and assign one or more other mesh nodes to the first MU association group based on the determined one or more characteristics of the traffic, the first MU association group enabling the MU group leader to manage MU group communication between the MU group leader and the one or more other mesh nodes, the MU group communication using MU multiple-input multiple-output (MU-MIMO) or orthogonal frequency division multiple access (OFDMA) in the wireless mesh network.

[0231] Clause 70. The apparatus of Clause 69, wherein the processing system is further configured to notify the first mesh node and the one or more other mesh nodes via the output of the interface about their respective roles in the first MU association group.

[0232] Clause 71. An apparatus as described in any of Clauses 69-70, wherein the interface is configured to: receive a traffic report message from each of the plurality of mesh nodes, the traffic report message including one or more characteristics of the traffic.

[0233] Clause 72. The apparatus of Clause 71, wherein the interface is configured to output a request for the traffic report message to each of the plurality of mesh nodes.

[0234] Clause 73. An apparatus of any of Clauses 69-72, wherein the interface is configured to: receive an indication from at least a first mesh node of a first candidate MU association group, wherein the first mesh node is a MU group leader, wherein the processing system is configured to select the first mesh node as the MU group leader of the first MU association group based on the indication of the first candidate MU association group.

[0235] Clause 74. An apparatus as described in any of Clauses 69-73, wherein the processing system is further configured to: determine a plurality of MU association groups based on the one or more characteristics of the traffic and the routing topology, each of the plurality of MU association groups having an MU group leader and one or more member mesh nodes, wherein the plurality of MU association groups includes a first MU association group and at least a second MU association group, the first MU association group having a first mesh node as an MU group leader and the second MU association group having a second mesh node as an MU group leader.

[0236] Clause 75. An apparatus as described in any of Clauses 69-74, wherein the processing system is further configured to: determine a MU participation constraint for each of the plurality of mesh nodes, the MU participation constraint limiting the number of mesh nodes that the mesh node can support as a MU group leader or limiting the number of MU association groups that the mesh node can join as a member; and determine the plurality of MU association groups based on the MU participation constraint for each of the plurality of mesh nodes.

[0237] Clause 76. An apparatus as described in any of Clauses 69-75, wherein the processing system is further configured to: select a first mesh node as the MU group leader of the first MU association group based on: determining that the first mesh node has the highest traffic load among the plurality of mesh nodes that have not yet been assigned as the MU group leader, or determining that the first mesh node generates the highest capacity bottleneck in the wireless mesh network among the plurality of mesh nodes that have not yet been assigned as the MU group leader; and assigning the one or more other nodes to the first MU association group based on the corresponding peering relationship between the one or more other nodes and the first mesh node.

[0238] Clause 77. An apparatus as described in any of Clauses 69-76, wherein the processing system is further configured to: determine the MU communication type of a first MU association group, wherein the MU communication type of the first MU association group is MU-MIMO based on the capacity sensitivity of traffic in the first MU association group.

[0239] Clause 78. An apparatus as described in any of Clauses 69-77, wherein the processing system is further configured to: select a second mesh node as the MU group leader of the second MU association group based on: determining that the second mesh node receives traffic from the highest number of source mesh nodes among the plurality of mesh nodes not yet assigned as MU group leaders, or determining that the second mesh node generates the highest capacity bottleneck in the wireless mesh network among the plurality of mesh nodes not yet assigned as MU group leaders; and assigning the source mesh node to the second MU association group based on the corresponding peering relationship between the source mesh node and the second mesh node.

[0240] Clause 79. An apparatus as described in any of Clauses 69-78, wherein the processing system is further configured to: determine the MU communication type of a second MU association group, wherein the MU communication type of the second MU association group is OFDMA based on the latency sensitivity of traffic in the second MU association group.

[0241] Clause 80. An apparatus as described in any of Clauses 69-79, wherein the network management unit is located in the same place as the first mesh node or the root mesh node.

[0242] Clause 81. An apparatus for a mesh node, comprising: an interface configured to: communicate with a network management unit of a wireless mesh network; output one or more characteristics of traffic between a first mesh node and one or more other mesh nodes in the wireless mesh network for transmission to the network management unit; and obtain a configuration for at least a first multi-user (MU) association group, the first MU association group including an MU group leader and one or more other mesh nodes, the first MU association group enabling the MU group leader to manage MU group communication between the MU group leader and the one or more other mesh nodes, the MU group communication using MU multiple-input multiple-output (MU-MIMO) or orthogonal frequency division multiple access (OFDMA) in the wireless mesh network.

[0243] Clause 82. The apparatus of Clause 81, wherein the interface is further configured to: receive a request for a traffic report message from the network management unit; and, in response to the request, output the one or more characteristics of the traffic to the network management unit in the traffic report message.

[0244] Clause 83. An apparatus as described in any of Clauses 81-82, wherein the interface is further configured to: determine a first candidate MU association group in which the first mesh node is the MU group leader based on one or more characteristics of the traffic and the routing topology of the wireless mesh network; and output an indication of the first candidate MU association group to the network management unit.

[0245] Clause 84. An apparatus as described in any of Clauses 81-83, wherein the first mesh node is a member of the first MU associated group.

[0246] Clause 85. The apparatus of any of Clauses 81-84, wherein the first mesh node is the MU group leader of the first MU associated group.

[0247] Another innovative aspect of the subject matter described in this disclosure can be implemented as a computer-readable medium storing instructions that, when executed by a processor, cause the processor to perform any of the methods described above.

[0248] Another innovative aspect of the subject matter described in this disclosure can be implemented as a device having an interface for communication with a processor via a wireless local area network. The processor can be configured to perform any of the methods described above.

[0249] Another innovative aspect of the subject matter described in this disclosure can be implemented as a system including means for implementing any of the methods described above.

[0250] The foregoing disclosure provides explanations and descriptions, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the foregoing disclosure or may be obtained through practice.

[0251] As used herein, the term "component" is intended to be interpreted broadly as hardware, firmware, or a combination of hardware and software. As used herein, a processor is implemented using hardware, firmware, or a combination of hardware and software. As used herein, the phrase "based on" is intended to be interpreted broadly as "at least partially based on".

[0252] Some aspects are described in conjunction with thresholds in this paper. As used herein, depending on the specific context, satisfying a threshold can mean a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0253] As used herein, the term "determine" or "determine" encompasses a wide variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, searching (such as by searching in a table, database, or other data structure), ascertainment, and so on. Additionally, "determine" can include receiving (such as receiving information), accessing (such as accessing data in memory), or obtaining, and so on. Furthermore, "determine" can include parsing, selecting, choosing, building, and other similar actions.

[0254] As used herein, the phrase “at least one” or “one or more of” in a list of items refers to any combination of those items, including individual items of those items. For example, “at least one of a, b, or c” is intended to cover the following possibilities: 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.

[0255] The various illustrative components, logic, logic blocks, modules, circuits, operations, and algorithmic processes described in conjunction with the implementations disclosed herein can 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. This interchangeability of hardware, firmware, and software has been generally described in terms of its functionality and is illustrated in the various illustrative components, blocks, modules, circuits, and processes described above. Whether such functionality is implemented in hardware, firmware, or software depends on the specific application and the design constraints imposed on the overall system.

[0256] Hardware and data processing means for implementing the various illustrative components, logic, logic blocks, modules, and circuits described in conjunction with the aspects disclosed herein may be implemented or executed using a general-purpose single-chip or multi-chip processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof. A general-purpose processor may be a microprocessor, or any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration). In some implementations, specific processes, operations, and methods may be performed by a circuit system dedicated to a given function.

[0257] As described above, in some aspects, implementations of the subject matter described herein can be implemented as software. For example, the functions of the various components disclosed herein, or the blocks or steps of the methods, operations, processes, or algorithms disclosed herein, can be implemented as one or more modules of one or more computer programs. Such computer programs may include non-transient processor or computer-executable instructions encoded on one or more tangible processors or computer-readable storage media for execution by or control of the operation of a data processing apparatus including components of the devices described herein. By way of example and not limitation, such storage media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store program code in the form of instructions or data structures. Combinations of the above should also be included within the scope of storage media.

[0258] Various modifications to the implementations described in this disclosure may be apparent to those skilled 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 granted the broadest scope consistent with this disclosure, the principles disclosed herein, and the novel features.

[0259] Furthermore, the various features described in this specification in the context of separate implementations may also be implemented in combination in a single implementation. Conversely, the various features described in the context of a single implementation may also be implemented separately or in any suitable sub-combination in multiple implementations. Thus, although features may be described above as operating in a particular combination and even initially claimed in this way, one or more features from the claimed combination may be removed from that combination in some cases, and the claimed combination may be for sub-combinations or variations thereof.

[0260] Similarly, although the operations are depicted in a specific order in the accompanying drawings, this should not be construed as requiring such operations to be performed in the specific order shown or sequentially, or requiring the performance of all explained operations to achieve the desired result. Furthermore, the drawings may schematically depict one or more example processes in the form of flowcharts or diagrams. However, other operations not depicted may be incorporated into the schematically explained example processes. For example, one or more additional operations may be performed before, after, simultaneously with, or between any explained operation. In some environments, multitasking and parallel processing may be advantageous. Moreover, the separation of the various system components in the implementations described above should not be construed as requiring such separation in all implementations, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products. Additionally, other implementations also fall within the scope of the appended claims. In some cases, the actions recited in the claims may be performed in a different order and still achieve the desired result.

Claims

1. A method for wireless communication, comprising: Communication is conducted in a wireless mesh network comprising multiple mesh nodes; as well as At least a first multi-user (MU) association group is established, the first MU association group comprising a first mesh node and one or more peer mesh nodes from the plurality of mesh nodes, the first MU association group enabling the first mesh node to operate as a multi-user access point (MU-AP) in the MU association group to allocate radio channel resources for MU communication between the first mesh node forming the first MU association group and at least a subset of the one or more peer mesh nodes, wherein the one or more peer mesh nodes operate as multi-user stations (MU-STA). Establishing the at least first MU association group includes selecting the first mesh node as the MU group leader of the first MU association group based at least in part on the routing topology of the wireless mesh network, and The selection of the first mesh node as the MU group leader includes selecting the first mesh node as the MU group leader of the first MU association group based on at least one condition from a group including: The first mesh node is determined to have the highest traffic load among the plurality of mesh nodes that have not yet been assigned as the MU group leader. The first mesh node is identified as generating the highest capacity bottleneck in the wireless mesh network among the plurality of mesh nodes that have not yet been assigned as MU group leaders. Determine that the first mesh node receives traffic from the highest number of source mesh nodes among the plurality of mesh nodes that have not yet been assigned as MU group leaders, or Any combination thereof.

2. The method of claim 1, wherein establishing the at least first MU association group comprises transmitting instructions to the one or more peer mesh nodes regarding their roles as members of the first MU association group.

3. The method of claim 1, wherein establishing the at least first MU association group further comprises: The first mesh node is selected as the MU group leader to manage the first MU associated group, at least in part based on the routing topology and traffic flow information. as well as The one or more peer-to-peer mesh nodes are selected as members of the first MU association group based on their corresponding peer relationships with the first mesh node.

4. The method of claim 3, wherein establishing the at least first MU association group further comprises: The routing topology of the wireless mesh network is obtained at least in part based on path selection protocol messages; as well as Obtain traffic flow information regarding the communication between the first mesh node and the one or more peer mesh nodes.

5. The method of claim 4, wherein obtaining the traffic flow information includes: A request to send a traffic report message to each of the one or more peer mesh nodes; as well as In response to the request, the traffic report message is received from each of the one or more peer mesh nodes, the traffic report message including the traffic flow information measured by each of the one or more peer mesh nodes.

6. A method performed by a first mesh node of a wireless mesh network, comprising: Communicating with multiple mesh nodes in the wireless mesh network; Receive configuration for at least a first multi-user (MU) association group, the first MU association group including a second mesh node as the MU group leader and at least the first mesh node; A portion of the first MU group communication, which includes transmissions from one or more mesh nodes, is transmitted to the second mesh node using wireless channel resources managed by the second mesh node. as well as Based on traffic flow information or the routing topology of the wireless mesh network, one or more candidate MU association groups are sent from the first mesh node to the network management unit. The configuration used for the first MU association group is at least partially based on the one or more candidate MU association groups.

7. The method of claim 6, further comprising: Receive a request for a traffic report message from the network management unit; as well as In response to the request, the network management unit sends the traffic report message, which includes traffic flow information measured by the first mesh node, and the traffic flow information can be used by the network management unit to assign the first mesh node to the first MU association group.

8. The method of claim 6, further comprising: Receive configuration for a second MU association group including the first mesh node; Traffic associated with the first MU-associated group is transmitted via the first MU group communication using the wireless channel resources managed by the second mesh node; as well as Traffic associated with the second MU group is transmitted via the second MU group communication using radio channel resources managed by the MU group leader of the second MU group.

9. The method of claim 8, wherein the first mesh node is the MU group leader of the second MU association group, the method further comprising: The first mesh node, which acts as the MU group leader of the second MU association group, manages the radio channel resources associated with the second MU group communication between the first mesh node and one or more peer mesh nodes in the second MU association group.

10. A first mesh node, comprising: A processing system, comprising one or more processors and one or more memories coupled to the processors, is configured to cause the first mesh node to: Communication is conducted in a wireless mesh network comprising multiple mesh nodes; Establish at least a first multi-user (MU) association group, the first MU association group including the first mesh node and one or more peer mesh nodes from the plurality of mesh nodes, the first MU association group enabling the first mesh node to operate as a MU group leader as a multi-user access point (MU-AP) in the MU association group to allocate radio channel resources for MU communication between the first mesh node forming the first MU association group and at least a subset of the one or more peer mesh nodes, wherein the one or more peer mesh nodes operate as multi-user stations (MU-STA); as well as The first mesh node is selected as the MU group leader of the first MU association group, at least in part based on the routing topology of the wireless mesh network, and The selection of the first mesh node as the MU group leader includes selecting the first mesh node as the MU group leader of the first MU association group based on at least one condition from a group including: The first mesh node is determined to have the highest traffic load among the plurality of mesh nodes that have not yet been assigned as the MU group leader. The first mesh node is identified as generating the highest capacity bottleneck in the wireless mesh network among the plurality of mesh nodes that have not yet been assigned as MU group leaders. Determine that the first mesh node receives traffic from the highest number of source mesh nodes among the plurality of mesh nodes that have not yet been assigned as MU group leaders, or Any combination thereof.

11. The first mesh node of claim 10, wherein the processing system is further configured to cause the first mesh node to: output an indication of the role of the one or more peer mesh nodes as members of the first MU association group for transmission to the one or more peer mesh nodes.

12. The first mesh node of claim 10, wherein the processing system is further configured to cause the first mesh node to: The first mesh node is selected as the MU group leader to manage the first MU association group, at least in part based on the routing topology and traffic flow information; and The one or more peer-to-peer mesh nodes are selected as members of the first MU association group based on their corresponding peer relationships with the first mesh node.

13. The first mesh node of claim 12, wherein the processing system is further configured to cause the first mesh node to: The routing topology of the wireless mesh network is obtained, at least in part, based on path selection protocol messages; and Obtain traffic flow information regarding the communication between the first mesh node and the one or more peer mesh nodes.

14. The first mesh node of claim 13, wherein the processing system is further configured to cause the first mesh node to: Output a request for a traffic report message to each of the one or more peer mesh nodes; and In response to the request, the traffic report message is obtained from each of the one or more peer mesh nodes, the traffic report message including the traffic flow information measured by each of the one or more peer mesh nodes.

15. The first mesh node of claim 10, wherein the processing system is further configured to cause the first mesh node to: The first mesh node is selected as the MU group leader of the first MU association group based on at least one condition from a group including the following: The first mesh node has the lowest hop count to the mesh portal compared to the hop count between each of the plurality of mesh nodes and the mesh portal. The first mesh node has the highest number of incoming or outgoing routes in the routing table for the wireless mesh network compared to the number of incoming or outgoing routes for each of the plurality of mesh nodes. Its weighted combination.

16. The first mesh node of claim 10, wherein the processing system is further configured to cause the first mesh node to: Obtain the candidate MU association groups determined by each mesh node from the wireless mesh network; and The first mesh node is selected as the MU group leader of the first MU group, at least in part based on the candidate MU association groups.

17. The first mesh node of claim 10, wherein the processing system is further configured to enable the first mesh node to: determine a plurality of MU association groups based on traffic flow information and the routing topology of the wireless mesh network, each MU association group having a corresponding MU group leader and one or more corresponding member mesh nodes.

18. The first mesh node of claim 17, wherein the processing system is further configured to cause the first mesh node to: Determine MU participation constraints for each of the plurality of mesh nodes, wherein the MU participation constraints limit the number of mesh nodes that the mesh node can manage as a MU group leader or limit the number of MU association groups that the mesh node can participate in as a member; and The plurality of MU association groups are selected at least in part based on the MU participation constraints for each of the plurality of mesh nodes.

19. The first mesh node as claimed in claim 10, wherein the first mesh node operates as a network management unit of the wireless mesh network or coexists with the network management unit in the same location.

20. The first mesh node as described in claim 10, further comprising: At least one transceiver; At least one antenna, coupled to the at least one transceiver, for wirelessly transmitting signals output from the at least one transceiver and wirelessly receiving signals for input to the at least one transceiver; as well as A housing that encloses at least a portion of the processing system, at least one modem, at least one transceiver, and at least one antenna.

21. A first mesh node, comprising: A processing system, comprising one or more processors and one or more memories coupled to the processors, is configured to cause the first mesh node to: Communicating with multiple mesh nodes in a wireless mesh network; as well as Obtain the configuration for at least a first multi-user (MU) association group, the first MU association group including a second mesh node as the MU group leader and at least the first mesh node; Manage the first MU group communication according to the configuration described; A portion of the first MU group communication is output for transmission to the second mesh node using wireless channel resources managed by the second mesh node, the first MU group communication including transmissions from one or more mesh nodes; as well as Based on traffic flow information or the routing topology of the wireless mesh network, one or more candidate MU association groups are output to the network management unit. The configuration used for the first MU association group is at least partially based on the one or more candidate MU association groups.

22. The first mesh node of claim 21, wherein the processing system is further configured to cause the first mesh node to: Requests to obtain traffic report messages from the network management unit; and In response to the request, the traffic report message is output for transmission to the network management unit. The traffic report message includes traffic flow information measured by the first mesh node, and the traffic flow information can be used by the network management unit to assign the first mesh node to the first MU association group.

23. The first mesh node of claim 21, wherein the processing system is further configured to cause the first mesh node to: obtain a configuration for a second MU association group including the first mesh node; Traffic associated with the first MU association group is transmitted via the first MU group communication using radio channel resources managed by the second mesh node, which operates as the MU group leader of the first MU association group. as well as Traffic associated with the second MU group is transmitted via the second MU group communication using radio channel resources managed by the MU group leader of the second MU group.

24. The first mesh node as described in claim 23, The first mesh node is the MU group leader of the second MU association group, and The processing system is further configured to enable the first mesh node to act as the MU group leader of the second MU association group, managing the radio channel resources associated with the second MU group communication between the first mesh node and one or more peer mesh nodes in the second MU association group.

25. The first mesh node as described in claim 21, further comprising: At least one transceiver; At least one antenna, coupled to the at least one transceiver, for wirelessly transmitting signals output from the at least one transceiver and wirelessly receiving signals for input to the at least one transceiver; as well as A housing that encloses at least a portion of the processing system, at least one modem, at least one transceiver, and at least one antenna.

Images