System and method for calculating uplink path loss in WLAN

By calculating the uplink path loss between client devices and access points (APs) in WLANs and grouping them based on path loss and device category, the problem of calculating uplink path loss in wireless LANs is solved, improving the transmission efficiency and reliability of UL MU-MIMO and UL OFDMA.

CN110784890BActive Publication Date: 2026-11-17HEWLETT PACKARD ENTERPRISE DEV LP
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN201910687441.6
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2018-07-26
Filing Date
2019-07-25
Publication Date
2026-11-17
Estimated Expiration
2039-07-25

AI Technical Summary

Technical Problem

In existing technologies, the calculation of uplink path loss in wireless local area networks (WLANs) has not been effectively solved, resulting in low uplink multi-user transmission efficiency. Furthermore, the lack of a mechanism to determine UL path loss affects the application of UL MU-MIMO and UL OFDMA.

Method used

By receiving the maximum transmit power capability of client devices at the access point (AP), the effective maximum transmit power and uplink power margin are calculated. Combined with the Received Signal Strength Indicator (RSSI) and antenna gain, the uplink path loss between the client devices and the AP is calculated. Based on the path loss and device category, the client devices are grouped to select an appropriate modulation and coding scheme and target received signal strength.

Benefits of technology

It realizes efficient uplink path loss calculation in WLAN, improves the efficiency of uplink multi-user transmission, supports the application of UL MU-MIMO and UL OFDMA, and enhances the success rate and reliability of data transmission.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN110784890B_ABST
    Figure CN110784890B_ABST
Patent Text Reader

Abstract

A system and method are provided for calculating uplink path loss in a wireless local area network (WLAN). The uplink path loss between a client device operating in the WLAN and an access point can be calculated based on a determined effective maximum transmit power. The current transmit power of the client device can be determined based on the effective maximum transmit power and a known uplink power margin. The uplink path loss can be determined based on the current transmit power of the client device. The uplink path loss can be reassessed if operating conditions and / or the characteristics of the client device and / or the WLAN change.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Embodiments of this disclosure generally relate to the field of wireless communication, and more specifically to systems and methods for calculating uplink path loss in a wireless local area network. Background Technology

[0002] Wireless digital networks are becoming ubiquitous in enterprises, providing secure and cost-effective access to resources. These networks typically have one or more controllers, each supporting multiple access points (APs) deployed across the enterprise. WiFi networks operating according to the IEEE 802.11 standard are an example of such networks. For instance, wireless network communication devices (also known as stations or client devices) such as personal computers and mobile phones transmit data across wireless digital networks to both WiFi APs and cellular network APs.

[0003] WLAN infrastructure elements or components in a WiFi network provide services to WLAN devices. When providing this service, the RF characteristics of the link between the access point (AP) and client devices can be determined to optimize data transmission and / or reception. These RF characteristics may include, for example, path loss and channel coefficients. Summary of the Invention

[0004] In a first aspect, a non-transitory machine-readable storage medium is provided, encoded with instructions executable by a hardware processor of a computing component. The machine-readable storage medium includes instructions that cause the hardware processor to: at an access point (AP) in a wireless local area network (WLAN), receive a maximum transmit power for operating channels of a client device communicating with the AP; at the AP or its controller, aggregate the maximum transmit power capabilities of the client device received over a period of time from multiple APs communicating with the client device; at the AP or its controller, calculate the effective maximum transmit power of the client device across multiple radio channels operated by the client device, based on the client device's maximum transmit power capability; at the AP, receive an uplink power margin of the client device communicating with the AP; and at the AP or its controller, calculate the uplink path loss between the client device and the AP using the effective maximum transmit power, the uplink power margin, the AP's antenna gain, and a Received Signal Strength Indicator (RSSI) measured by the AP for the client device.

[0005] In a second aspect, an access point (AP) operating in a wireless local area network (WLAN) is provided, comprising a non-transitory machine-readable storage medium encoded with instructions executable by a hardware processor, the machine-readable storage medium including instructions that cause the hardware processor to: determine a plurality of client devices having data to be transmitted to the AP, each of the plurality of client devices being associated with at least one of a device class and one or more access class identifiers; create a group of client devices from the plurality of client devices for uplink multi-user transmission, the group of client devices being identified as being associated with at least one of the same access class identifier and the same or similar device class; calculate, for each client device in the group of client devices, an uplink path loss from each client device to the AP; create a subgroup of client devices from the group of client devices including client devices having similar uplink path losses to the AP; and, for each of the client devices in the subgroup of client devices, select and assign a target modulation and coding scheme (MCS) to be used during data transmission from each of the client devices in the subgroup of client devices, and a target received signal strength at the AP that each of the client devices in the subgroup of client devices can satisfy.

[0006] In a third aspect, a method is provided, comprising: identifying one or more client devices associated with at least one of the same access class identifier and the same or similar device class at an access point (AP) or a controller of the AP, wherein the AP operates in a wireless local area network (WLAN); grouping the client devices associated with the same access class identifier and the same or similar device class together for uplink transmission purposes; calculating, for each client device in the client device group, an uplink path loss from each client device to the AP; creating a client device subgroup from the client device group, the client device subgroup comprising client devices having similar uplink path losses to the AP; and, for each client device in the client device subgroup, selecting and assigning a target modulation and coding scheme (MCS) to be used during uplink transmission of data from each client device in the client device subgroup and a target received signal strength at the AP that each client device in the client device subgroup can satisfy. Attached Figure Description

[0007] The present disclosure is described in detail with reference to the following accompanying drawings, which illustrate one or more various embodiments. The drawings are provided for illustrative purposes only and depict only typical or exemplary embodiments. These drawings are provided to help the reader understand the various embodiments and should not be considered as limiting the breadth, scope, or applicability of the disclosure. It should be noted that these drawings are not necessarily drawn to scale for clarity and ease of illustration.

[0008] Figure 1A This is a schematic block diagram illustrating an example network configuration in which the techniques described herein can be implemented.

[0009] Figure 1B The illustration depicts an example uplink multi-user (UL MU) transmission scenario according to various embodiments.

[0010] Figure 2A This is a block diagram of an example computing component, according to various embodiments, for grouping client devices together to schedule simultaneous UL MU transmissions based on UL service compatibility.

[0011] Figure 2B This is a block diagram of an example computing component, according to various embodiments, for grouping client devices together based on device class to schedule simultaneous UL MU transmissions.

[0012] Figure 3A This is a block diagram of an example computing component for calculating path loss between an AP and a client device, according to various embodiments.

[0013] Figure 3B An example table illustrating the maximum transmit power capabilities of client devices across channels and regulatory domains is provided.

[0014] Figure 4A This is a block diagram of an example calculation component for selecting a UL modulation coding scheme (MCS) and target received signal strength indication (RSSI) according to various embodiments.

[0015] Figure 4B It is a sample table containing the received RSSI, the corresponding MCS rate, the UPH value of the client device, and the calculated maximum achievable RSSI and maximum achievable MCS rate.

[0016] Figure 5A This is a block diagram of an example computing component for creating a group of UL MU client devices, according to various embodiments.

[0017] Figure 5B This is a block diagram of an example calculation component for adjusting a UL MCS for a client device in a UL MU group, according to various embodiments.

[0018] Figure 6Examples of computing components that can be used in conjunction with various embodiments of this disclosure.

[0019] The accompanying drawings are not intended to be exhaustive or to limit the various embodiments to the precise forms disclosed. It should be understood that various embodiments can be practiced with modifications and variations. Detailed Implementation

[0020] Multi-User, Multiple-Input, Multiple-Output (MU-MIMO) provides a mechanism for a wireless network device to transmit simultaneously to multiple client devices. The wireless network device can be a network device providing wireless connectivity to the network, such as an access point (AP). Without MU-MIMO enabled, the network device may have to transmit one to each associated client device at a time. With MU-MIMO, because the wireless network device can transmit to multiple client devices simultaneously, it can transmit more data more frequently. This can increase the rate at which data is transmitted to some or all of the associated client devices. MU-MIMO is defined in the Institute of Electrical and Electronics Engineers (IEEE) 802.11 specification.

[0021] When using MU-MIMO, wireless network devices can group two or more client devices and transmit beamformed signals to each group. MU-MIMO can be more efficient when a group of client devices receiving MU-MIMO transmissions is also receiving frames with similar service characteristics. Because the network device is transmitting to all client devices simultaneously, transmission can be more efficient when the frames being transmitted are of similar size. Furthermore, the interval between MU-MIMO transmissions can be minimized when the network device receives incoming frames almost simultaneously.

[0022] In the upcoming 802.11ax high-efficiency WLAN standard, one way to achieve the aforementioned efficiency is through scheduling MU transmissions for both downstream (from the AP) and upstream (from the client device) transmissions. Downstream MU transmission scheduling has already been addressed in the context of the 802.11ac solution, which uses MU channel sensing and beamforming to minimize interference between different client devices that are part of the same MU transmission.

[0023] However, in the upstream or uplink (UL) direction, within the context of a WLAN network, the grouping of client devices and the selection of the MCS (Physical (PHY) layer rate) and target RSSI values ​​at the AP for each client device remain unresolved issues. It should be understood that RSSI can refer to a value representing the received signal strength or power level received by the AP's receiving radio after antenna and possible path losses.

[0024] Various embodiments of this disclosure relate to systems and methods for grouping compatible client devices for UL MU (simultaneous) services based on one or more criteria that can be used to define the grouping of compatible client devices. For example, the grouping of client devices may be based on one or more criteria, including: the compatibility of services to be transmitted from the client device; and the similarity of device classes or the capabilities of the client device. In some embodiments, further refinement of the grouping can be achieved by grouping client devices with the same or similar path loss to the AP together. It should be noted that in some cases, the UL and downlink (DL) path losses may be the same or similar, while in others they may be different. Therefore, in some embodiments, the calculation of the path loss between the client device and the AP may be independent of the transmission direction.

[0025] Once the client device is grouped, the aforementioned issues regarding MCS and target RSSI selection can be resolved. Specifically, various embodiments of this disclosure also relate to determining, when the client device is part of a MU group, the MCS and target transmit power to be used by the client device for upstream transmission of its data to (multiple) APs in order to achieve the desired RSSI at the APs.

[0026] In some embodiments, the UL MCS can be updated based on feedback from each client device in the group that has already transmitted packets in the UL MU transmission regarding successful packet reception at the AP. For example, the AP can maintain / adjust the UL packet delivery and / or UL MCS rate based on the packet data rate or packet error rate. For example, the AP can adjust the UL MCS based on the DL single-user (SU) / MU rate and UL channel quality.

[0027] Returning to the grouping of client devices based on path loss, it should be understood that within the context of a WLAN infrastructure providing services to WLAN devices, it is important for the network to determine the fundamental RF characteristics of the link between the access point (AP) and the client device. Path loss is an example of this RF characteristic.

[0028] Traditional systems and methods infer path loss on the downstream or deep link / channel between the access point (AP) and client devices. For example, 802.11k beacon reporting allows the access point (AP) to receive feedback on the signal-to-noise ratio (SNR) of received beacon frames heard by the client devices. Using explicit channel sensing regarding the transmission of empty data packets, the AP can also obtain the SNR of different subcarriers heard by the client devices. While these techniques are useful for determining appropriate channel weights for downstream transmissions, they have drawbacks. For example, beacon reporting is not implemented by most client devices because it is an optional feature, and implementing channel sensing feedback can be expensive. Furthermore, the path loss of the link between the AP and client devices can be asymmetric due to differences in the transmitter RF circuitry of the client devices and the AP, as well as the different multipath properties of the link. To date, there are no known mechanisms / techniques for determining UL path loss.

[0029] Therefore, various embodiments involve determining or calculating the UL path loss between the AP and the client device. In some embodiments, the maximum transmit power capability across different operating channels and across regulatory domains is determined. From this maximum power capability, the effective maximum transmit power capability can be derived. The client device reports its UL power margin value to the AP. Therefore, at the lowest MCS rate (selected to remain within the transmitter error vector magnitude (EVM) limit), the current transmit power of the client device can be calculated by subtracting the uplink power margin value from the maximum effective transmit power of the client device. The path loss in the uplink (from the client device to the AP) can then be calculated by subtracting the target RSSI value and the AP receive antenna gain from the current transmit power of the client device.

[0030] As mentioned above, UL path loss can be used as a basis for grouping client devices together for applications such as UL Multi-User Multiple-Input Multiple-Output (MU-MIMO) and UL Orthogonal Frequency Division Multiple Access (OFDMA) in the upcoming 802.11ax standard, where matching the received RSSI at the AP improves the probability of detection. Other applications where UL path loss may be useful include, but are not limited to, AP-to-client-device UL MCS determination, ranging, and client-device manipulation.

[0031] Figure 1A The illustration depicts one embodiment of a network configuration 100 that can be implemented for a multi-user organization, such as a business, educational institution, government entity, or any other organization with multiple users and potentially multiple physical or geographic sites. Network configuration 100 may include a main office 102 communicating with network 120. Network configuration 100 may also include one or more remote sites 132, 142 communicating with network 120.

[0032] Main office 102 may include a primary network, which may be referred to as a corporate network or a home network. The main office 102 network may also be a private network. A private network can refer to a network that includes security and access controls, such that only certain users are authorized to access the private network. Authorized users may include, for example, employees of the company located in main office 102.

[0033] In the illustrated example, main office 102 includes a controller 104 that communicates with network 120. Controller 104 may provide communication between main office 102 and network 120, although it may not be the only communication point between main office 102 and network 120. A single controller 104 is illustrated, but the main office may include multiple controllers and / or multiple communication points with network 120. In some embodiments, controller 104 communicates with network 120 via a router (not shown). In other embodiments, controller 104 provides router functionality to devices in main office 102.

[0034] Controller 104 may be operable to configure and manage network devices such as those at main office 102, and may also manage network devices at remote sites 132, 134. Controller 104 may be operable to configure and / or manage switches, routers, access points, and / or client devices connected to the network. Controller 104 itself may be, or may provide, access point functionality.

[0035] Controller 104 can communicate with one or more switches 108 and / or wireless access points (APs) 106a-c. Switches 108 and wireless APs 106a-c provide network connectivity to various client devices 110a-j. Using the connection to switch 108 or AP 106a-c, client devices 110a-j can access network resources, including other devices on the (main office 102) network and network 120.

[0036] Examples of client devices include, but are not limited to: desktop computers, laptop computers, servers, web servers, authentication servers, authentication-authorization-accounting (AAA) servers, domain name system (DNS) servers, dynamic host configuration protocol (DHCP) servers, internet protocol (IP) servers, virtual private network (VPN) servers, network policy servers, mainframes, tablet computers, netbook computers, televisions and similar monitors, content receivers, set-top boxes, personal digital assistants (PDAs), mobile phones, smartphones, smart terminals, dumb terminals, virtual terminals, video game consoles, etc.

[0037] Within main office 102, switch 108 is included as an example of an access point for wired client devices 110i-j to establish a network within main office 102. Client devices 110i-j can connect to switch 108 and, through switch 108, can access other devices within network configuration 100. Client devices 110i-j can also access network 120 through switch 108. Client devices 110i-j can communicate with switch 108 over a wired connection 112. In the illustrated example, switch 108 communicates with controller 104 over a wired connection 112, but this connection could also be wireless.

[0038] Wireless APs 106a-c are included as another example of access points for client devices 110a-h to establish a network in main office 102. Each of the APs 106a-c can be a combination of hardware, software, and / or firmware configured to provide wireless network connectivity to wireless client devices 110a-h. In the illustrated example, the APs 106a-c can be managed and configured by controller 104. The APs 106a-c communicate with controller 104 and the network via wired connection 112 or wireless connection 114.

[0039] Network configuration 100 may include one or more remote sites 132. Remote sites 132 may be located in a different physical or geographical location than the main office 102. In some cases, remote sites 132 may be in the same geographical location as the main office 102 or possibly in the same building, but lack a direct connection to the network located within the main office 102. Instead, remote sites 132 may utilize connections on a different network (e.g., network 120). Remote sites 132, such as... Figure 1A The remote site illustrated could be, for example, a satellite office. Remote site 132 may include a gateway device 134 for communicating with network 120. Gateway device 134 may be a router, analog-digital modem, cable modem, digital subscriber line (DSL) modem, or some other network device configured to communicate with network 120. Remote site 132 may also include a switch 138 and / or an access point (AP) 136 communicating with gateway device 134 over a wired or wireless connection. Switch 138 and AP 136 provide connectivity to the network for various client devices 140a-d.

[0040] In various embodiments, remote station 132 communicates directly with main office 102, enabling client devices 140a-d at remote station 132 to access network resources at main office 102 as if they were located at main office 102. In such embodiments, remote station 132 is managed by controller 104 at main office 102, and controller 104 provides the necessary connectivity, security, and accessibility for remote station 132 to communicate with main office 102. Once connected to main office 102, remote station 132 can function as part of a private network provided by main office 102.

[0041] In various embodiments, network configuration 100 may include one or more smaller remote sites 142, which consist only of a gateway device 144 and a wireless access point 146 for communicating with network 120, through which various client devices 150a-b access network 120. Such a remote site 142 may represent, for example, the home of an individual employee or a temporary remote office. The remote site 142 may also communicate with the main office 102, enabling the client devices 150a-b at the remote site 142 to access network resources at the main office 102 as if they were located at the main office 102. The remote site 142 may be managed by a controller 104 at the main office 102 to enable this transparency. Once connected to the main office 102, the remote site 142 can function as part of a private network provided by the main office 102.

[0042] Network 120 may be a public network, such as the Internet. A public network is a network including the illustrated network configuration 100 that can be shared by any number of entities. A public network may have unrestricted access, allowing any user to connect to it. Network 120 may include third-party telecommunications lines, such as telephone lines, broadcast coaxial cables, fiber optic cables, satellite communications, cellular communications, etc. Network 120 may include any number of intermediate network devices, such as switches, routers, gateways, servers, and / or controllers, which are not directly part of network configuration 100 but facilitate communication between the various parts of network configuration 100 and between network configuration 100 and other network-connected entities. Network 120 may include various content servers 160a-b. Content servers 160a-b may include various providers of multimedia downloadable and / or streaming content, including audio, video, graphics, and / or text content or any combination thereof. Examples of content servers 160a-b include, for example, web servers, streaming radio and video providers, and cable and satellite television providers. Client devices 110a-j, 140a-d, and 150a-b can request and access multimedia content provided by content server 160a-b.

[0043] As mentioned above, in order to transmit UL data to an AP such as AP 106c, client devices in the network can be grouped together, such as the client devices represented by network configuration 100.

[0044] OFDM symbols can be considered the fundamental building blocks of WiFi transmission. That is, an OFDM symbol is a small temporal segment of the modulated waveform of a subcarrier carrying information. In 802.11ax, the subcarrier spacing is varied to allow OFDMA to extend to small subchannels (defined in the standard), each with at least one (but typically two) pilot subcarriers. With a minimum subchannel size of 2 MHz, the smaller subcarrier spacing results in a smaller percentage of total bandwidth loss due to pilot loss. Furthermore, the number of guard and empty subcarriers across channels can be reduced to a percentage of the available subcarriers, which in turn increases the effective data rate for a given channel.

[0045] OFDMA operates by partitioning transmissions across a frequency dimension, where devices are assigned to transmit and receive in sub-channels or resource units (RUs) of a primary RF channel. This allows an AP (in the downlink) to bundle multiple frames together in a single transmit opportunity, on different sub-channels, while client devices associated with the AP tune their respective radios to different sub-channels to receive their respective transmissions. Specifically, the AP can assemble a number of frames for different client devices and modulate them on the assigned set of sub-channels. Padding can be added to frames shorter than the longest frame in the bundle. In the uplink context, as mentioned above, the AP determines or calculates the grouping of client devices. The AP then signals each client device when it should transmit and which sub-channel should be used for its transmission.

[0046] DL MU-MIMO was introduced in 802.11ac, and it extends the concepts of spatial diversity and beamforming to support simultaneous transmission from an AP to multiple client devices. MU-MIMO is typically possible when propagation characteristics allow the AP to identify that a transmission optimized for one client device or a grouping of client devices will not be heard by some other client devices with significant signal strength, and vice versa. Both multi-user mode MU-MIMO and OFDMA allow simultaneous bidirectional communication between an AP and multiple client devices. However, unlike DL MU-MIMO or DL ​​OFDMA, UL MU-MIMO / OFDMA mode uses trigger frames, which allow the AP to allocate MU-MIMO groups and OFDMA RUs to its associated client devices. The AP notifies the client devices of this allocation. The AP then polls its associated client devices for their UL service requests.

[0047] Figure 1B The illustration depicts example UL MU scenarios according to various embodiments. As noted above, operating in UL MU mode involves using trigger frames to allow the AP to allocate MU-MIMO groups and OFDMA RUs to client devices associated with the AP. Once allocation is made, the AP (such as...) Figure 1A The AP 106b) or AP controller (such as AP controller 104) transmits a trigger frame 180, which seeks transmissions of UL MU PHY Protocol Data Units (PPDUs) 182a-c from multiple client devices (e.g., client devices 110a-110c). That is, the trigger frame 180 is used to inform the client devices 110a-c that they are part of a specific MU group scheduled for upstream transmission, as well as the selected MCS and target RSSI (to be received at AP 106).

[0048] Therefore, trigger frame 180 can be used for time synchronization purposes between relevant MU client devices (in this case, client devices 110a-c) based on the end of trigger frame 180. Additionally, frequency offset correction can be based on a common AP reference from trigger frame 180. Furthermore, trigger frame 180 can provide information about the appropriate duration and PPDU length of the expected UL MU transmission from client devices 110a-c, as well as information identifying the client devices (in this case, client devices 110a-c) permitted to transmit. In response to trigger frame 180, client devices 110a-c transmit their respective data packets, i.e., UL MU (OFDMA or MU-MIMO) PPDUs 182a-c, to AP 106b using appropriate / identified MCS, and transmit with the power required to achieve the target RSSI. This maximizes the probability of successful data packet reception at AP 106b. In response to the UL MU PPDUs 182a-c received from client devices 110a-c, AP 106b transmits acknowledgment frame 184.

[0049] In order to group client devices together for simultaneous UL MU transmission, various embodiments may take into account the service compatibility and / or UL compatibility of the client devices based on the device class of the client devices.

[0050] Regarding service compatibility, multiple client devices used for UL MU transmission can be grouped together based on upstream service compatibility. To determine whether a client device has compatible upstream services, the AP (e.g., AP 106b) or AP controller (e.g., AP controller 104) can utilize information contained in buffer status reports (BSRs) periodically sent from client devices (e.g., client devices 110a-c) to the AP or AP controller. According to the 802.11ax standard, the information contained in the BSR can include queued services for each Access Class (AC) (i.e., queued UL data buffered in each corresponding client device). In other words, each client device can transmit the status of its UL buffer queue and the service identifier (TID) to which the queued data belongs, for example, to the AP or AP controller. It should be understood that data can be assigned to one of four ACs—AC0-AC3. Highest priority data (such as audio data that cannot tolerate certain delays / latencies) can be assigned to the first AC, such as AC0. The next highest priority data (such as video data) can be assigned to AC1. Data associated with another priority level (such as best-effort Quality of Service (QoS)) can be assigned to AC2, and data associated with the remaining priority levels (such as background data) can be assigned to AC3. Of course, it should be understood that the various priority levels can vary and / or other assignments to those various priority levels and the corresponding AC levels can vary.

[0051] Figure 2A This is a block diagram of an example computing component or device 200 used to group client devices together based on access category to schedule simultaneous UL MU transmissions. Computing component 200 can be, for example, a server computer, a controller, or any other similar computing component capable of processing data. Figure 2A In an example implementation, computing component 200 includes a hardware processor 202 and a machine-readable storage medium 204. In some embodiments, computing component 200 may be an embodiment of an AP or an AP controller, for example... Figure 1A The AP 106b or AP controller 104.

[0052] Hardware processor 202 may be one or more central processing units (CPUs), semiconductor-based microprocessors, and / or other hardware devices suitable for retrieving and executing instructions stored in machine-readable storage medium 204. Hardware processor 202 may fetch, decode, and execute instructions such as instructions 206-212 to control processes or operations for grouping client devices based on business compatibility. As an alternative or additional step in retrieving and executing instructions, hardware processor 202 may include one or more electronic circuits comprising functional electronic components for executing one or more instructions, such as field-programmable gate arrays (FPGAs) or application-specific integrated circuits (ASICs).

[0053] Machine-readable storage media, such as machine-readable storage medium 304, can be any electrical, magnetic, optical, or other physical storage device that contains or stores executable instructions. Therefore, machine-readable storage medium 204 can be, for example, random access memory (RAM), non-volatile RAM (NVRAM), electrically erasable programmable read-only memory (EEPROM), storage devices, optical discs, etc. In some embodiments, machine-readable storage medium 202 can be a non-transitory storage medium, wherein the term "non-transitory" does not cover transient propagation signals. As described in detail below, machine-readable storage medium 202 can be encoded with executable instructions (e.g., instructions 206-212) for client device grouping.

[0054] Hardware processor 200 can execute instructions 206 to determine which AC is associated with the maximum buffer queue size for each client device. For example, as noted above, hardware processor 200 could be an AP or AP controller receiving a BSR from each client device. Hardware processor 200 can analyze or extract information from the BSR frame to determine which AC (or AC identifier, ACI) associated with the client device corresponds to the maximum UL buffer queue for that client device, and what the UL buffer queue size is.

[0055] Hardware processor 200 can execute instruction 208 to create a set of client devices. This set of client devices can be created by including those client devices whose maximum buffer queue size is associated with the same AC / ACI. That is, client devices are filtered based on a corresponding BSR indicating the maximum UL buffer queue size associated with the same AC / ACI. For example, a first client device may have a maximum UL buffer queue size of 5, which is associated with data assigned to AC0 (highest priority level). A second client device may have a maximum buffer queue size of 8, which is also associated with data assigned to AC0. A third client device may have a maximum buffer queue size of 7, which is also associated with data assigned to AC0. After executing instruction 208, hardware processor 200 can create a set of client devices that includes each of the first, second, and third client devices, provided that each of their respective maximum UL buffer queues maintains data corresponding to the same AC / ACI (AC0 in this case).

[0056] Hardware processor 200 can execute instruction 210 to select one or more subsets of client devices from the aforementioned set of client devices, whose maximum UL buffer queue sizes are within each other's threshold variance level. That is, the threshold variance level can be determined to capture or allow client devices whose maximum UL buffer queue sizes are within a value of 1. In the example above, execution of instruction 210 can cause hardware processor 200 to select the second and third client devices (whose maximum UL buffer queue sizes are 8 and 7, respectively) as a subset of client devices. Because the first client device (whose maximum UL buffer queue size is 5) falls outside the threshold variance level, the first client device is not included as part of the selected subset.

[0057] Hardware processor 210 can execute instruction 212 to schedule each of one or more subsets in a single UL MU group. That is, based on the result of executing instruction 210, hardware processor 210 (which may be an AP or an AP controller) schedules second and third client devices to simultaneously transmit their respective queued data to the AP.

[0058] Regarding UL compatibility, multiple client devices used for UL MU transmissions can be grouped together based on device class compatibility. That is, client devices can be specified by class. It should be understood that, in the context of the 802.11 standard, a class can refer to the fidelity of the client device's transmitter in terms of error vector magnitude (EVM) and / or frequency characteristics during transmission at a certain effective isotropic radiated power (EIRP). Frequency characteristics may include, but are not limited to, frequency drift and phase noise. Client devices can advertise their capabilities (in terms of fidelity) to the AP regarding the client device's initial association request message. In the 802.11 standard, client device capabilities can be identified as "Class A" or "Class B". Generally, Class A devices have higher accuracy in EIRP and RSSI measurements at the AP. Alternatively, the device class of a client device can be determined based on the AP's knowledge (e.g., history or others) of the client device's model, type, and / or other information not necessarily received from the client device in the initial association request.

[0059] Figure 2B This is a block diagram of an example computing component 200 used to group client devices together based on device class compatibility to schedule simultaneous UL MU transmissions. Computing component 200 can be used with... Figure 2A The same as or similar to that shown. Figure 2B As illustrated, hardware processor 200 can execute instructions 214 to determine the device class associated with each client device. As noted above, in some embodiments, a client device may be associated with one or two device classes that indicate the transmitter fidelity of the client device.

[0060] Hardware processor 200 can execute instruction 216 to create a set of client devices. This set of client devices can be created by including those client devices associated with the same device class. Hardware processor 200 can execute instruction 218 to schedule the set of client devices to transmit data within a single UL MU group.

[0061] For example, and according to some embodiments, a type of "broad" filtering based on the client device class can cover client device classes known to lack high fidelity, such as Class B client devices. In some embodiments, client devices that do not have / utilize high-fidelity transmitters can be transformed into situations where the AP cannot expect deterministic signals from the client device, particularly when attempting to receive / synchronize all received signals at the AP. That is, in order to successfully decode UL transmissions at the AP, the client device should be matched in terms of its transmit EVM, frequency drift, and other transmission distortions.

[0062] Therefore, based on this broad filtering, the AP can selectively ignore client devices that do not possess high fidelity (or sufficiently high fidelity) from UL transmissions. That is, these devices are not grouped with other client devices and can be degraded to a single UL transmission. In other embodiments, these Class B or "lower" fidelity client devices can be grouped together. Furthermore, those client devices with the necessary fidelity, such as those characterized as Class A client devices, can be grouped together for simultaneous UL MU transmissions.

[0063] It should be noted that grouping of client devices based on service compatibility or class compatibility can be used specifically. For example, the AP can schedule simultaneous UL MU transmissions for client devices that have compatible services to transmit upstream or for client devices that have a compatibility class designation. However, in some embodiments, the AP can schedule simultaneous UL MU transmissions for a group of client devices based on both service compatibility and client device class. For example, hardware processor 200 can determine a first grouping of client devices based on service compatibility, and hardware processor 200 can further determine a second grouping of client devices (a subset of the first grouping) from that first grouping based on class designation, and vice versa. In some embodiments, a weighting scheme can be used, where one grouping consideration can be given a heavier weight than another grouping consideration, for example, given a priority. For example, weighting can be based on the number of unprocessed packets queued for a client device. If the number of unprocessed packets in the transmission queue of a client device is greater than a given threshold, then service compatibility can be given a heavier weight than device class, i.e., service compatibility among client device groups takes precedence over device class-based grouping.

[0064] In some embodiments, to align upstream data packet transmissions from multiple client devices, it is advantageous for those client devices to have similar path losses to the AP. In this way, similar or strictly constrained MCS (regarding receive EVM, guard interval, spatial flow, etc.) at the desired RSSI level, as specified by the AP, can be maintained. Therefore, the initial grouping of client devices selected based on service compatibility and / or client device class can be further refined; for example, a subset of initial groups can be identified / selected based on similar path loss characteristics. For example, client devices with path losses to the AP less than a certain defined path loss threshold can be grouped together. In some embodiments, multiple path loss thresholds can be defined and used as the basis for grouping client devices. It should be understood that the path loss can be calculated for each client device in the initial grouping of client devices that are part of the current UL MU group.

[0065] Determine the various operating characteristics of the AP and client devices and use them to calculate the UL path loss between the AP and client devices. Figure 3A This is a block diagram of an example computing component or device 200 for calculating path loss between an AP and a client device. In some embodiments, computing component 200 may be the same computing component shown in FIG. 2 and described above. However, in some embodiments, different computing components or partitions / parts of computing component 200 may be used to determine the path loss as described herein. In some embodiments, hardware processor 202 is the same hardware processor 202 shown in FIG. 2, or in other embodiments, a different hardware processor or a portion of hardware processor 202 may be used. In some embodiments, machine-readable storage medium 204 is the same machine-readable storage medium shown in FIG. 2, but in other embodiments, a different machine-readable storage medium or a portion of machine-readable storage medium 204 may be used to store instructions 220-230.

[0066] like Figure 3A As illustrated, hardware processor 202 can execute instruction 220, enabling the AP (in a WLAN) to receive the maximum transmit power capability of client devices communicating with the AP for operating channels. That is, and according to one embodiment, the maximum transmit power capability of client devices across different operating channels and across regulatory domains (referred to as TX_Max_EIRP) 11h channel The transmit power capability of a client device can be determined by the power capability information it reports to the access point (AP).

[0067] For example, when spectrum management features (introduced in the 802.11h extension of the 802.11 standard) are enabled on an AP, client devices can advertise their respective power capabilities to the AP. The advertising of the client device's maximum (and minimum) transmit power capabilities can occur in the frame of an association request sent by the client device to the AP. It should be understood that the client device's maximum transmit power capability can vary depending on one or more of the following: the channel on which the client device may be operating; the unlicensed National Information Infrastructure (U-NII) band on which the client device may be operating; and the regulatory domain in which the client device may be operating. In some embodiments, the maximum transmit power may be limited by the client device's hardware limitations. Therefore, hardware processor 202 can execute instructions 222 to aggregate, at the AP or the AP's controller, the maximum transmit power capabilities received from multiple APs communicating with the client device over a period of time for the client device.

[0068] WLAN infrastructure can use tables or other data structures to maintain a record or list of the maximum transmit power capabilities of client devices across different channels, frequency bands, and / or regulated domains, as seen by multiple access points (APs). Such a record or list of the maximum transmit power capabilities of client devices can be built for all relevant regulated domains, channels, and / or frequency bands, and can be created and / or maintained at the AP, AP controller, and / or some other, such as centralized data storage.

[0069] Figure 3B The illustration shows an example table of maximum transmit power capabilities for client devices across channels and regulatory domains. For instance, a client device, such as client device 110a in Figure 1, can have a maximum transmit power of 19W (denoted as Max EIRP) when transmitting through channel 36 in a domain regulated by the U.S. Federal Communications Commission (FCC). On channel 149 in an FCC-regulated domain, client device 110a can have a maximum transmit power of 21W.

[0070] return Figure 3A The hardware processor 202 can execute instructions 224 to calculate the effective maximum transmit power of the client device at the AP or the AP's controller based on the client device's maximum transmit power capability across multiple radio channels on which the client device operates. That is, (in this example) using the client device's set of maximum transmit power capabilities per channel / per supervisory domain, the effective maximum transmit power capability of the client device can be calculated according to the following equation:

[0071] TX_Max_EIRP 11h =Min{Tx_Max_EIRP 11h channel}

[0072] It should be noted that, in this example, selecting the minimum maximum transmit power from the set of maximum transmit power capabilities is a convenient method for determining the effective maximum transmit power of the client device. However, other methods can be used to determine the effective maximum transmit power. For example, the average or mean maximum transmit power of the set of maximum transmit power capabilities of the client device can be calculated and considered as representing the effective maximum transmit power of the client device across channel / band / regulatory domain.

[0073] Hardware processor 202 can execute instruction 226 to receive uplink power margin at the AP for client devices communicating with the AP.

[0074] In the 802.11ax standard, client devices use the High Efficiency (HE) variable in the High Throughput (HT) control field of frames sent to the Access Point (AP) to report UL Power Headroom (UPH). This HE variable in the HT control field is typically requested by the AP to coordinate its MU UL transmissions with other client devices. UPH values ​​can be described as a range within which a client device can increase its EIRP for the currently used MCS or increase its EIRP to that range. In this way, the AP can be informed of the UPH (referred to as UL_Headroom) relative to the client device's current transmit power for its current MCS rate (MCS_x). CD,MCS x The following equation can be used to reflect UPH:

[0075] UL_Headroom CD,MCS =TX_MAX_EIRP CD,MCS -TX_CURRENT_EIRP CD

[0076] It can be assumed that, given an MCS(TX_MAX_EIRP) CD,MCS=0 The maximum transmit power of the client device at the specified location is compared with the maximum transmit power capability of the client device advertised in the client device's association request (TX_MAX_EIRP). 11h The same applies as described above. This is a reasonable assumption, as it is anticipated that client devices will primarily use the maximum allowed transmit power at their lowest MCS rate to remain within the specified transmit EVM limits, as also mentioned above. Therefore, Equation 1 can be simplified as follows:

[0077] UL_Headroom CD,MCS =TX_MAX_EIRP 11h -TX_CURRENT_EIRP CD

[0078] For a given client device, using MCS 0, the current EIRP of the client device is calculated as follows:

[0079] TX_CURRENT_EIRP CD =TX_MAX_EIRP 11h -UL_Headroom CD,MCS=0

[0080] It should be understood that client devices may have different EIRP and UL margins for each MCS value or rate. As indicated above, a minimum MCS can be assumed to remain within the specified transmit EVM limits.

[0081] As illustrated in the following equation, the RSSI at the AP is a function of the client device's current EIRP, the AP's receive antenna gain, and the path loss between the client device and the AP, where G_ANT AP The receive antenna gain of the AP (known at the AP):

[0082] RSSI AP =TX_CURRENT_EIRP CD +G_ANT AP –PathLoss

[0083] Therefore, since the current EIRP of the client device has been determined above, and the target RSSI and receive antenna gain are known, the path loss between the client device and the AP can be calculated as follows:

[0084] PathLoss CD-AP =TX_MAX_EIRP 11h -UL_Headroom CD,MCS=0 ,-RSSI AP +G_ANT AP

[0085] Therefore, the hardware processor 202 can execute instruction 228 to calculate the UL path loss between the client device and the AP using the RSSI value measured at the AP for the client device, the effective maximum transmit power, the uplink margin, and the AP's antenna gain.

[0086] It should be understood that the path loss determination described above can be performed for each of multiple client devices. As also noted above, path loss can be used as part of client device packet determination to support simultaneous ULMU-MIMO or UL OFDMA transmissions. Therefore, the determined path loss can be used to generate datasets across multiple APs, which can be “data-mined” and merged across various geographical areas. It should also be noted that the advantage of the described method for determining path loss is that it can be implemented using 802.11ax compliant devices, as 802.11ax client devices simultaneously support UPH feedback and power capability reporting.

[0087] In some embodiments, it may be beneficial to reassess the path loss between client devices and access points (APs). That is, a particular path loss is related to a certain amount of time. Therefore, it may be beneficial to reassess the path loss involving APs based on differences involving, but not limited to, client device type, traffic flow, upstream signal-to-noise ratio (SNR), virtual beacon reporting variations (e.g., variations in upstream SNR to multiple APs and / or classifying client devices as mobile rather than non-mobile external inputs, etc.). Similarly, path loss determinations can be collected to create a dataset that can be data mined and used to optimize certain transmission modes, such as UL MU-MIMO / OFDMA, network performance, etc.

[0088] Therefore, hardware processor 202 can execute instruction 230 to re-evaluate path loss based on one or more changes regarding the operational characteristics of the network (i.e., WLAN) and at least one of the client devices. For example, when the upstream SNR from the client device changes by an amount equal to or exceeding a certain upstream SNR threshold, the AP or AP controller embodied by hardware processor 204 can re-initiate path loss determination by re-executing instructions 220-228.

[0089] Once the AP or AP controller (based on one or more of UL service compatibility, client device class, and path loss similarity) determines the grouping of client devices that will simultaneously transmit their queued data, the AP or AP controller can determine link or PHY compatibility. In other words, the received power from each client device at the AP should be balanced so that the AP can successfully decode each transmission from each client device in the group, even though the transmissions are sent to the AP simultaneously.

[0090] According to various embodiments, the UL MCS and target RSSI can be selected to further segment or generate subgroups of client devices based on PHY compatibility. That is, the UL MCS rate can be selected for each client device for its triggered UL transmission, and the target transmit power for each client device can be selected to achieve the target RSSI at the AP. Once the UL MCS rate and target RSSI are selected for each client device, the information can be transmitted to the appropriate client device.

[0091] Figure 4A This is a block diagram of an example calculation component or device 200 for selecting UL MCS and target RSSI according to various embodiments. As previously noted, in some embodiments, the calculation component 200 may be the same as that shown in Figure 2 and / or Figure 3AThe same computing components are shown and described above. However, in some embodiments, different computing components or partitions / partitions of computing component 200 may be used to determine the path loss as described herein. In some embodiments, hardware processor 202 is the same as that shown in Figure 2 and / or Figure 3A The same hardware processor 202 shown, or in other embodiments, may be used, or a portion thereof, of hardware processor 202. In some embodiments, machine-readable storage medium 204 is associated with FIG2 and / or Figure 3A The same machine-readable storage medium is shown, but in other embodiments, another machine-readable storage medium or a portion of machine-readable storage medium 204 may be used to store instructions 232-240.

[0092] In some embodiments, the hardware processor 202 may execute instructions 232 to determine the available UPH at each of the plurality of client devices. To make this determination, the AP may begin an initial path loss estimation by requesting a UL transmission at an MCS rate of 0. By requesting a UL transmission at the lowest MCS rate, the AP may determine the available UPH at the client device (i.e., the amount by which the transmit power of the client device can be increased).

[0093] In some embodiments, hardware processor 202 may execute instructions 234 to (at the AP) construct a dataset including the available UPH for each of the multiple client devices upon receiving an upstream packet from each of the multiple client devices. For example, the AP (or AP controller) may construct a table of UPH values ​​per MCS rate based on each client device associated with the AP.

[0094] In some embodiments, the hardware processor 202 may execute instructions 236 to calculate the maximum achievable RSSI and the maximum achievable MCS rate at the AP based on the RSSI received at the AP from each of the plurality of client devices and the available UPH at each of the plurality of client devices. That is, for each client device associated with the AP, the AP or AP controller may calculate the difference between the RSSI received at the AP and the UPH to achieve the maximum achievable RSSI. The maximum achievable MCS rate (i.e., when receiving the aforementioned upstream packets from each client device at each MCS rate) may be determined based on the maximum achievable RSSI, and the AP (or AP controller) may calculate the maximum MCS that can be supported by the maximum achievable RSSI. It should be understood that the calculated maximum achievable RSSI corresponds to the aforementioned target RSSI at the AP.

[0095] Figure 4BThis is an example list (in table form) of the RSSI received at the AP, the corresponding MCS rate 0, the UPH value of the client device, the calculated maximum reachable RSSI, and the maximum reachable MCS rate. In this example, for the first client device CS 1, at MCS rate 0, based on the upstream packet transmission sent by CS 1 to the AP (at the AP's request), the received RSSI at the AP is -65dBm. If the UPH of CD 1 is 15dB, then the maximum reachable RSSI is -65dBm + 15dB, which equals -50dBm. Similar calculations can be performed for all associated client devices (client devices CD 2-6 in this example).

[0096] like Figure 4B As illustrated in the diagram, the calculated maximum achievable RSSI results in a range of maximum achievable (supported) MCS rates from MCS 11 to MCS 7. It can be understood that if the AP or AP controller selects a target RSSI of -54dBm (high enough to decode MCS rates 10 or higher), the AP or AP controller can consider its respective UPH capabilities to determine which client devices can achieve this RSSI. In this way, client devices can be further grouped (after considering, for example, UL service compatibility, client device class, and / or UL path loss) and assigned target RSSI and MCS rates.

[0097] return Figure 4AThe hardware processor 202 can execute instructions 238 to select client devices from a plurality of client devices that have sufficient UPH to accommodate transmit power variations in order to achieve the target RSSI at the AP. For example, the AP or AP controller can select an MCS rate of 10 and a target RSSI of -54 dBm (i.e., the minimum achievable in the group). Based on the above calculations, the AP / AP controller can select client devices CD1-3 as part of a first UL MU group. In some embodiments, the AP / AP controller can select an MCS rate of 9 and a target RSSI of -54 dBm to allow for some signal margin, e.g., a resilience of approximately 3 dB). Similarly, client devices CD1-3 can be selected. The AP / AP controller can select an MCS rate of 7 and a target RSSI of -63 dBm. Therefore, the AP / AP controller can select client devices CD4-6 as part of a second UL MU group. The target RSSI can be derived based on the desired MCS, and for each desired MCS, a specific SNR budget for the receiver is required. If a client device is unable to increase its power level due to its UPH being less than the desired transmit power level, it may be excluded from the UL MU group. One or more such client devices may be scheduled as part of another group (as noted above), or one or more client devices may be degraded to single-user transmission mode.

[0098] It should be noted that in the case of UL MU-MIMO, the entire bandwidth is used, while in the case of UL OFDMA, the AP / AP controller can further consider which subcarrier group to assign to the client device group. It should also be noted that, generally, client devices assigned a higher MCS can be scheduled first, while those assigned a lower MCS can be scheduled later. Generally, a higher MCS rate is preferred from the perspective of reducing airtime on the radio channel. Even so, this can depend on the UPH, and the MCS rate can be scaled down to any MCS achievable for the desired signal level at the AP.

[0099] As noted above, client devices can be grouped based on one or more of UL service compatibility, client device class, and / or UL path loss. Upon determining or reaching such a group, those client devices in the group can be further filtered or subdivided into one or more other subgroups based on MCS rate and target RSSI. Therefore, hardware processor 202 can execute instructions 240 to set the target RSSI and MCS for the selected client devices, i.e., assigning the target RSSI and MCS rate to one or more client devices in that subgroup.

[0100] Figure 5A This is a block diagram of an example computing component or device 200 for creating a group of UL MU client devices according to various embodiments. In some embodiments, computing component 200 may be... Figure 2A , Figure 2B , Figure 3A and / or Figure 4A The same computing components shown and described above. However, in some embodiments, different computing components or partitions / partitions of computing component 200 may be used to determine the path loss as described herein. In some embodiments, hardware processor 202 is... Figure 2A , Figure 2B , Figure 3A and / or Figure 4A The same hardware processor 202 shown may be used in other embodiments, or a different hardware processor or a portion thereof. In some embodiments, the machine-readable storage medium 204 is... Figure 2A , Figure 2B , Figure 3A and / or Figure 4A The same machine-readable storage medium is shown, but in other embodiments, another machine-readable storage medium or a portion of machine-readable storage medium 204 may be used to store instructions 500-504.

[0101] In some embodiments, hardware processor 202 may execute instructions 500 to identify a plurality of client devices having data to be transmitted to an AP, each of the plurality of client devices being associated with at least one of one or more ACIs and client device classes. Hardware processor 202 may execute instructions 502 to create a client device group from the plurality of client devices, the client device group being identified as being associated with at least one of the same ACI and the same or similar client device classes. As noted above, UL service compatibility can be determined using the ACI associated with the client devices, and UL compatibility based on the type (class) of the client devices under consideration, predicated on the fidelity of the client device transmitter, can be determined. Hardware processor 202 may execute instructions 504 to select a target MCS to be used during data transmission for each client device in the client device group, and a target RSSI that each client device in the client device group can satisfy.

[0102] Similar to the reassessment of path loss described above, the UL MCS rate used by client devices grouped together for simultaneous UL MU transmission can also be reassessed and adjusted. That is, once the AP or AP controller establishes a client device grouping, successful packet reception at the AP can be monitored, and the applicable MCS rate assessment for each client device in the group can be adjusted to maintain a specific UL packet delivery rate.

[0103] Figure 5B This is a block diagram of an example computing component or device 200 for adjusting client devices in a UL MU group, according to various embodiments. Machine-readable storage medium 204 may be used to store additional instructions 506-508.

[0104] For example, after selecting the target MCS rate and target RSSI (as described above), the hardware processor 202 can execute instruction 506 to monitor UL MU packet reception at the AP from each grouped client device. That is, after the AP / AP controller has made a decision on one or more groups as described above, and has assigned UL transmit power (EIRP) to meet the target RSSI and MCS selected by each client device as described above, the AP can monitor successful packet reception from each client device participating in UL MU transmission to the AP.

[0105] Because UL MU transmissions are triggered by the AP, the AP / AP controller knows which client devices will send UL frames in the next UL MU transmission within a Short Interframe Spacing (SIFS) time interval. The SIFS time interval can refer to the amount of time required for the wireless interface to process the received frames and respond with appropriate response frames (e.g., the aforementioned trigger and acknowledgment frames).

[0106] Hardware processor 202 can execute instruction 508 to adjust the UL MCS rate based on the success of UL MU packet reception. That is, the AP can maintain a desired or initial UL packet delivery rate for each client device and adjust the UL MCS rate for subsequent UL MU transmissions from each client device based on the packet delivery rate (or conversely, the packet error rate). In other embodiments, the AP can alternatively use a combination of the DL SU / MU transmission rate used by the AP to send data to a particular client device and the UL Channel Quality Indicator (CQI) received from that client device. For example, the packet delivery rate / packet error rate can be maintained at the MCS rate and used to calculate the expected actual throughput (e.g., application-level throughput or the number of useful information bits delivered per unit time) if that MCS rate is used with those specific packet delivery rates / packet error rates. A combination of the packet delivery rate / packet error rate and the MCS rate that maximizes actual throughput can be used as a target rate. For example, CQI can be used as a filtering criterion. For instance, if the CQI is above a certain threshold, a higher MCS rate can be started, while if the CQI is below a certain threshold, a higher MCS rate can be avoided.

[0107] Figure 6 An example computational component 600 is illustrated that can be used to implement various features of the methods disclosed herein. Computational component 200 may be an embodiment of computational component 600.

[0108] In one embodiment where the components of this application are implemented in whole or in part using software, these software elements may be implemented to operate in conjunction with computing or processing components capable of performing the functionality described herein. However, after reading this specification, those skilled in the art will understand how to implement this application using other computing components or architectures.

[0109] As noted above regarding computing component 200, computing component 600 may represent computing or processing power found, for example, within a mainframe, supercomputer, workstation, or server, or any other type of dedicated or general-purpose computing device that may be desired or appropriate for a given application or environment. Computing component 600 may also represent computing power embedded within a given device or otherwise available to a given device.

[0110] Computing component 600 may include, for example, one or more processors, controllers, control components, or other processing devices, such as processor 604 (an example embodiment of which is hardware processor 202). Processor 604 may be implemented using general-purpose or special-purpose processing engines, such as, for example, microprocessors, controllers, or other control logic. In the illustrated example, processor 604 is connected to bus 602, but any communication medium may be used to facilitate interaction with or external communication with other components of computing component 600.

[0111] The computing component 600 may also include one or more memory components, referred to herein as main memory 608 (an embodiment of which is machine-readable memory 204). For example, preferably, random access memory (RAM) or other dynamic memory may be used to store information and instructions to be executed by the processor 604. Main memory 608 may also be used to store temporary variables or other intermediate information during the execution of instructions to be executed by the processor 604. The computing component 600 may also include read-only memory (“ROM”) or other static storage devices coupled to bus 602 for storing static information and instructions for the processor 604.

[0112] The computing component 600 may also include one or more forms of information storage mechanisms 610, which may include, for example, a media drive 612 and a storage unit interface 620. The media drive 612 may include a drive or other mechanism to support a fixed or removable storage medium 614. For example, a hard disk drive, a solid-state drive, an optical disc drive, a CD, DVD, or Blu-ray drive (R or RW), or other removable or fixed media drive may be provided. Therefore, the storage medium 614 may include, for example, a hard disk drive, a solid-state drive, a magnetic tape cassette, an optical disc, a CD, DVD, Blu-ray, or other fixed or removable media that is read from, written to, or accessed by the media drive 612. As illustrated in these examples, the storage medium 614 may include a computer-usable storage medium in which computer software or data is stored.

[0113] In an alternative embodiment, the information storage mechanism 610 may include other similar tools for allowing computer programs or other instructions or data to be loaded into the computing component 600. Such tools may include, for example, fixed or removable storage units 622 and interfaces 620. Examples of such storage units 622 and interfaces 620 may include removable memory (e.g., flash memory or other removable memory components) and memory slots, or other fixed or removable storage units 622 and interfaces 620 that allow software and data to be transferred from storage unit 622 to computing component 600.

[0114] The computing component 600 may also include a communication interface 624. The communication interface 624 can be used to allow the transfer of software and data between the computing component 600 and external devices. Examples of the communication interface 624 may include a modem or softmodem, a network interface (such as Ethernet, a network interface card, WiMedia, IEEE 802.XX, or other interfaces), and a communication port (such as, for example, a USB port, an IR port, or an RS232 port). (An interface or other port) or other communication interface. Software and data transmitted via communication interface 624 can typically be carried on signals, which can be electrical, electromagnetic (including optical), or other signals that can be exchanged by a given communication interface 624. These signals can be provided to communication interface 624 via channel 628. Channel 628 can carry signals and can be implemented using wired or wireless communication media. Some examples of channels are RF links, network interfaces, local area networks or wide area networks, and other wired or wireless communication channels.

[0115] In this document, the terms “computer-readable medium,” “computer-usable medium,” and “computer program medium” are generally used to refer to non-transitory, volatile, or non-volatile media, such as, for example, memory 608, storage cell 622, and medium 614. These and other various forms of computer program media or computer-usable media may involve carrying one or more sequences of one or more instructions onto a processing device for execution. Such instructions embodied on the medium are generally referred to as “computer program code” or “computer program product” (which may be grouped into a computer program or other grouping). When executed, such instructions enable computing component 600 to perform the features or functions of this application discussed herein.

[0116] Unless otherwise expressly stated, the terms and phrases used in this document and their variations should be interpreted as open-ended rather than restrictive. As examples of the foregoing: the term “comprising” should be interpreted as meaning “including, but not limited to”, etc.; the term “example” is used to provide exemplary instances of the items under discussion, not an exhaustive or restrictive list thereof; the terms “a” or “an” should be interpreted as meaning “at least one,” “one or more,” etc.; and adjectives such as “conventional,” “traditional,” “normal,” “standard,” “known,” and similar terms should not be interpreted as limiting the described items to a given time period or to items available at a given time, but should be interpreted as encompassing conventional, traditional, normal, or standard technologies that may be available or known at any time now or in the future. Similarly, where this document relates to technologies that are obvious or known to a person skilled in the art, such technologies encompass technologies that are obvious or known to a person skilled in the art at any time now or in the future.

[0117] The use of the term "component" does not mean that the elements or functionalities described or claimed as part of a component are configured in a common package. In fact, any one or all of the various components of a component, whether control logic or other components, can be combined in a single package or can be kept separately and further distributed across multiple groups or packages or across multiple locations.

[0118] While various embodiments of this disclosure have been described above, it should be understood that they are presented by way of example only and not limitation. Similarly, various figures may depict exemplary architectures or other configurations for use in this disclosure, which are provided to aid in understanding the features and functionality that may be included in this disclosure. This disclosure is not limited to the illustrated exemplary architectures or configurations, but various alternative architectures and configurations may be used to achieve the desired features. Furthermore, regarding flowcharts, descriptions of operation and instructions, or method claims, unless the context otherwise indicates, the order in which the steps are presented herein should not force the various embodiments to perform the described functionality in the same order.

[0119] Although this disclosure has been described above with reference to various exemplary embodiments and implementations, it should be understood that the various features, aspects, and functionalities described in one or more individual embodiments are not limited to their applicability to the particular embodiments described herein, but may be applied individually or in various combinations to one or more other embodiments of this disclosure, whether such embodiments are described or whether such features are presented as part of the described embodiments. Therefore, the breadth and scope of this disclosure should not be limited to any of the exemplary embodiments described above.

Claims

1. A non-transitory machine-readable storage medium encoded with instructions executable by a hardware processor of a computing component, the machine-readable storage medium including the instructions for causing the hardware processor to: At an access point (AP) in a wireless local area network (WLAN), the maximum transmit power capability of the client device communicating with the AP for operating the channel is received; At the AP or the controller of the AP, the maximum transmit power capability of the client device received from multiple APs communicating with the client device over a period of time is aggregated. At the AP or the controller of the AP, the effective maximum transmit power of the client device is calculated across multiple radio channels operated by the client device, based on the maximum transmit power capability of the client device. At the AP, the uplink power margin of the client device communicating with the AP is received; as well as At the AP or the AP's controller, the uplink path loss between the client device and the AP is calculated using the effective maximum transmit power, the uplink power margin, the AP's antenna gain, and the Received Signal Strength Indicator (RSSI) measured by the AP for the client device.

2. The non-transitory machine-readable storage medium of claim 1, wherein the instructions further cause the hardware processor to: determine the maximum transmit power capability for the operation channel based on an association request frame transmitted from the client device to the AP.

3. The non-transitory machine-readable storage medium of claim 1, wherein the instruction causing the hardware processor to calculate the effective maximum transmit power capability further causes the hardware processor to determine one of the following: a minimum maximum transmit power capability for the operating channel, an average maximum transmit power capability for the operating channel, and an average maximum transmit power capability for the operating channel.

4. The non-transitory machine-readable storage medium of claim 1, wherein the instructions further cause the hardware processor to: obtain the uplink power margin from a high-efficiency variable of the high-throughput control field in a frame transmitted from the client device to the AP.

5. The non-transitory machine-readable storage medium according to claim 4, wherein the uplink power margin includes: With an uplink power margin at the lowest modulation and coding scheme (MCS) rate commensurate with the transmit error vector magnitude (EVM) limit, the uplink power margin is requested from the client device to transmit to the AP when using the lowest MCS rate.

6. The non-transitory machine-readable storage medium of claim 1, wherein the instructions further cause the hardware processor to re-evaluate the uplink path loss based on one or more variations of at least one of the following: each of the plurality of client devices, and the operating characteristics of the WLAN.

7. The non-transitory machine-readable storage medium of claim 6, wherein the one or more variations relating to each of the plurality of client devices include: At least one of the changes in uplink signal-to-noise ratio (SNR) associated with the AP.

8. The non-transitory machine-readable storage medium of claim 7, wherein the instruction further causes the hardware processor to: initiate a reassessment of the uplink path loss upon experiencing a change in the uplink SNR that meets or exceeds an uplink SNR threshold.

9. The non-transitory machine-readable storage medium of claim 6, wherein the one or more variations relating to the operational characteristics of the WLAN include at least one of the following: variations in uplink SNR to a plurality of APs within the WLAN, variations in the type of client devices associated with the APs, and variations in traffic flows within the WLAN.

10. The non-transitory machine-readable storage medium of claim 1, wherein the instructions further cause the hardware processor to: at the AP, calculate the uplink path loss between the AP and an additional client device associated with the AP.

11. The non-transitory machine-readable storage medium of claim 10, wherein the instructions further cause the hardware processor to: select a subset of client devices from the group of client devices, including the client devices and the additional client devices, the selection being based on at least one of: uplink service compatibility of data to be transmitted from the subset of client devices to the AP, and the device category to which each client device in the subset of client devices belongs.

12. An access point (AP) operating in a wireless local area network (WLAN) includes a non-transitory machine-readable storage medium encoded with instructions executable by a hardware processor, the machine-readable storage medium including the instructions that cause the hardware processor to: A plurality of client devices are identified having data to be transmitted to the AP, each of the plurality of client devices being associated with at least one of a device class and one or more access class identifiers; A client device group for uplink multi-user transmission is created from the plurality of client devices, the client device group being identified as being associated with at least one of the same access class identifier and the same or similar device class; For each client device in the client device group, calculate the uplink path loss from each client device to the AP; Create a subgroup of client devices from the client device group, including those with similar uplink path loss to the AP; For each client device in the client device subgroup, a target modulation and coding scheme (MCS) to be used during data transmission from each client device in the client device subgroup, and a target received signal strength at the AP that each client device in the client device subgroup can satisfy are selected and assigned.

13. The AP of claim 12, wherein the instruction causing the hardware processor to calculate the uplink path loss from each client device in the client device subgroup to the AP further causes the hardware processor to: Based on the maximum transmit power capability per channel of each client device in the client device subgroup, the effective maximum transmit power is calculated across multiple radio channels operated by each of the client devices; and At the AP, the uplink path loss between each client device in the client device subgroup and the AP is calculated. The uplink path loss is a function of the following: the effective maximum transmit power of each client device, the uplink power margin of each client device, the received signal strength at the AP for each client device, and the antenna gain of the AP.

14. The AP of claim 13, wherein the instruction causing the hardware processor to calculate the effective maximum transmit power capability of each client device further causes the hardware processor to determine one of the following: minimum maximum transmit power capability per channel, average maximum transmit power capability per channel, and average maximum transmit power capability per channel.

15. The AP of claim 12, wherein the instructions further cause the hardware processor to reassess the uplink path loss based on one or more changes in the operating characteristics of the WLAN and at least one client device in the client device subgroup.

16. A method comprising: At the access point (AP) or the controller of the AP, one or more client devices are identified as being associated with at least one of the same access class identifier and the same or similar device class, wherein the AP operates in a wireless local area network (WLAN). For uplink transmission purposes, the client devices associated with the same access class identifier and at least one of the same or similar device classes are grouped together; For each client device in the client device group, calculate the uplink path loss from each client device to the AP; Create a client device subgroup from the client device group, the client device subgroup including client devices with similar uplink path loss to the AP; For each client device in the client device subgroup, a target modulation and coding scheme (MCS) to be used during uplink transmission of data from each client device in the client device subgroup, and a target received signal strength at the AP that each client device in the client device subgroup can satisfy are selected and assigned.

17. The method of claim 16, wherein calculating the uplink path loss from each client device in the client device subgroup to the AP comprises: The effective maximum transmit power is calculated across multiple radio channels operated by each client device, based on the maximum transmit power capability per channel of each client device in the client device subgroup.

18. The method of claim 17, wherein the uplink path loss is a function of: the effective maximum transmit power of each of the client devices, the uplink power margin of each of the client devices, the received signal strength at the AP for each client device, and the antenna gain of the AP.

19. The method of claim 18, wherein calculating the effective maximum transmit power capability of each client device includes determining one of the following: a minimum maximum transmit power capability per channel, a mean maximum transmit power capability per channel, and an average maximum transmit power capability per channel.

20. The method of claim 16, further comprising: The uplink path loss is reassessed based on the operational characteristics of the WLAN and one or more changes to at least one client device in the client device subgroup.

Citation Information

Patent Citations

  • Apparatus and method for uplink power control for a wireless transmitter / receiver unit utilizing multiple carriers

    CN102308640A

  • Uplink power control for wireless communication

    CN103997777A