Local Maximum Transmit Power Control for Trigger Based Transmissions

Abstract

A station (STA) receives, from an access point (AP), a first frame indicating a local maximum transmit power level for use by the STA. The STA transmits, to the AP, a second frame using a first transmit power level based on the local maximum transmit power level. The STA receives, from the AP, a third frame instructing the STA to ignore the local maximum transmit power level for determining a second transmit power level for transmitting a fourth frame to the AP. The STA transmits, to the AP, the fourth frame using the second transmit power level, wherein based on the fourth frame being in response to the third frame, the second transmit power level is greater than the local maximum transmit power level.

Description

Docket No.: 24-3039PCTTITLELocal Maximum Transmit Power Control for Trigger Based Transmissions CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 690,358, filed September4, 2024, which is hereby incorporated by reference in its entirety.BRIEF DESCRIPTION OF THE DRAWINGS

[0002] Examples of several of the various embodiments of the present disclosure are described herein with reference to the drawings.

[0003] FIG. 1 illustrates example wireless communication networks in which embodiments of the present disclosure may be implemented.

[0004] FIG. 2 is a block diagram illustrating example implementations of a station (STA) and an access point (AP).

[0005] FIG. 3 illustrates an example format of a physical layer (PHY) protocol data unit (PPDU).

[0006] FIG. 4 illustrates an example of a Medium Access Control (MAC) frame format.

[0007] FIG. 5 illustrates an example of a transmit power (TP) envelope element.

[0008] FIG. 6 illustrates an example control frame which may be used as a trigger frame.

[0009] FIG. 7 illustrates an example data frame which may be used as a quality of service (QoS) null frame.

[0010] FIG. 8 shows an example that illustrates use of a trigger based (TB) PPDU.

[0011] FIG. 9 illustrates an example of uplink (UL) TP headroom reporting in the presence of an uplink transmit power constraint due to the STA.

[0012] FIG. 10 illustrates an example that highlights a problem that may arise in TB transmission using a local max TP.

[0013] FIG. 11 illustrates an example operation according to an embodiment.

[0014] FIG. 12 illustrates a further example operation, according to an embodiment.

[0015] FIG. 13 illustrates another further example operation, according to an embodiment.

[0016] FIG. 14 illustrates an example of enhanced uplink power headroom (UPH) control, according to an embodiment.

[0017] FIG. 15 illustrates an example management frame information element (IE), according to an embodiment.

[0018] FIG. 16 illustrates an example process according to an embodiment of the present disclosure.

[0019] FIG. 17 illustrates an example process according to an embodiment of the present disclosure.

[0020] FIG. 18 illustrates an example of an operation using resource units.

[0021] FIG. 19 illustrates an example of an operation using distributed resource units (DRUs).

[0022] FIG. 20 illustrates an example of an operation using distributed resource units.Docket No.: 24-3039PCTDETAILED DESCRIPTION

[0023] In the present disclosure, various embodiments are presented as examples of how the disclosed techniques may be implemented and / or how the disclosed techniques may be practiced in environments and scenarios. It will be apparent to persons skilled in the relevant art that various changes in form and detail can be made therein without departing from the scope. After reading the description, it will be apparent to one skilled in the relevant art how to implement alternative embodiments. The present embodiments may not be limited by any of the described exemplary embodiments. The embodiments of the present disclosure will be described with reference to the accompanying drawings. Limitations, features, and / or elements from the disclosed example embodiments may be combined to create further embodiments within the scope of the disclosure. Any figures which highlight the functionality and advantages, are presented for example purposes only. The disclosed architecture is sufficiently flexible and configurable, such that it may be utilized in ways other than that shown. For example, the actions listed in any flowchart may be re-ordered or only optionally used in some embodiments.

[0024] Embodiments may be configured to operate as needed. The disclosed mechanism may be performed when certain criteria are met, for example, in a station, an access point, a radio environment, a network, a combination of the above, and / or the like. Example criteria may be based, at least in part, on for example, wireless device or network node configurations, traffic load, initial system set up, packet sizes, traffic characteristics, a combination of the above, and / or the like. When the one or more criteria are met, various example embodiments may be applied. Therefore, it may be possible to implement example embodiments that selectively implement disclosed protocols.

[0025] In this disclosure, "a” and "an” and similar phrases are to be interpreted as "at least one” and "one or more.” Similarly, any term that ends with the suffix “(s)” is to be interpreted as "at least one” and “one or more.” In this disclosure, the term “may” is to be interpreted as “may, for example.” In other words, the term “may” is indicative that the phrase following the term “may” is an example of one of a multitude of suitable possibilities that may, or may not, be employed by one or more of the various embodiments. The terms “comprises” and “consists of’, as used herein, enumerate one or more components of the element being described. The term “comprises” is interchangeable with “includes” and does not exclude unenumerated components from being included in the element being described. By contrast, “consists of’ provides a complete enumeration of the one or more components of the element being described. The term “based on”, as used herein, may be interpreted as “based at least in part on” rather than, for example, “based solely on”. The term “and / or” as used herein represents any possible combination of enumerated elements. For example, “A, B, and / or C” may represent A; B; C; A and B; A and C; B and C; or A, B, and C.

[0026] If A and B are sets and every element of A is an element of B, A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, possible subsets of B = {STA1 , STA2] are: {STA1 }, {STA2}, and {STA1 , STA2}. The phrase “based on” (or equally “based at least on”) isDocket No.: 24-3039PCT indicative that the phrase following the term “based on” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “in response to” (or equally “in response at least to”) is indicative that the phrase following the phrase “in response to” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “depending on” (or equally “depending at least to”) is indicative that the phrase following the phrase “depending on" is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “employing / using” (or equally “employing / using at least”) is indicative that the phrase following the phrase “employing / using” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments.

[0027] The term configured may relate to the capacity of a device whether the device is in an operational or non-operational state. Configured may refer to specific settings in a device that effect the operational characteristics of the device whether the device is in an operational or non-operational state. In other words, the hardware, software, firmware, registers, memory values, and / or the like may be “configured" within a device, whether the device is in an operational or nonoperational state, to provide the device with specific characteristics. Terms such as “a control message to cause in a device” may mean that a control message has parameters that may be used to configure specific characteristics or may be used to implement certain actions in the device, whether the device is in an operational or non-operational state.

[0028] In this disclosure, parameters (or equally called, fields, or Information elements: lEs) may comprise one or more information objects, and an information object may comprise one or more other objects. For example, if parameter (IE) N comprises parameter (IE) M, and parameter (IE) M comprises parameter (IE) K, and parameter (IE) K comprises parameter (information element) J. Then, for example, N comprises K, and N comprises J. In an example embodiment, when one or more messages / frames comprise a plurality of parameters, it implies that a parameter in the plurality of parameters is in at least one of the one or more messages / frames but does not have to be in each of the one or more messages / frames.

[0029] Many features presented are described as being optional through the use of “may” or the use of parentheses. For the sake of brevity and legibility, the present disclosure does not explicitly recite each and every permutation that may be obtained by choosing from the set of optional features. The present disclosure is to be interpreted as explicitly disclosing all such permutations. For example, a system described as having three optional features may be embodied in seven ways, namely with just one of the three possible features, with any two of the three possible features or with three of the three possible features.

[0030] Many of the elements described in the disclosed embodiments may be implemented as modules. A module is defined here as an element that performs a defined function and has a defined interface to other elements. The modules described in this disclosure may be implemented in hardware, software in combination with hardware, firmware, wetware (e.g. hardware with a biological element) or a combinationDocket No.: 24-3039PCT thereof, which may be behaviorally equivalent. For example, modules may be implemented as a software routine written in a computer language configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, Matlab or the like) or a modeling / simulation program such as Simulink, Stateflow, GNU Octave, or LabVIEWMathScript. It may be possible to implement modules using physical hardware that incorporates discrete or programmable analog, digital and / or quantum hardware. Examples of programmable hardware comprise: computers, microcontrollers, microprocessors, application-specific integrated circuits (ASICs); field programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs). Computers, microcontrollers and microprocessors are programmed using languages such as assembly, C, C++ or the like. FPGAs, ASICs and CPLDs are often programmed using hardware description languages (HDL) such as VHSIC hardware description language (VHDL) or Verilog that configure connections between internal hardware modules with lesser functionality on a programmable device. The mentioned technologies are often used in combination to achieve the result of a functional module.

[0031] FIG. 1 illustrates example wireless communication networks in which embodiments of the present disclosure may be implemented.

[0032] As shown in FIG. 1 , the example wireless communication networks may include an Institute of Electrical and Electronic Engineers (IEEE) 802.11 (WLAN) infra-structure network 102. WLAN infra-structure network 102 may include one or more basic service sets (BSSs) 1 10 and 120 and a distribution system (DS) 130.

[0033] BSS 110-1 and 110-2 each includes a set of an access point (AP or AP STA) and at least one station (STA or non-AP STA). For example, BSS 110-1 includes an AP 104-1 and a STA 106-1 , and BSS 1 10-2 includes an AP 104-2 and STAs 106-2 and 106-3. The AP and the at least one STA in a BSS perform an association procedure to communicate with each other.

[0034] DS 130 may be configured to connect BSS 110-1 and BSS 110-2. As such, DS 130 may enable an extended service set (ESS) 150. Within ESS 150, APs 104-1 and 104-2 are connected via DS 130 and may have the same service set identification (SSID).

[0035] WLAN infra-structure network 102 may be coupled to one or more external networks. For example, as shown in FIG. 1 , WLAN infra-structure network 102 may be connected to another network 108 (e.g., 802.X) via a portal 140. Portal 140 may function as a bridge connecting DS 130 of WLAN infra-structure network 102 with the other network 108.

[0036] The example wireless communication networks illustrated in FIG. 1 may further include one or more ad-hoc networks or independent BSSs (IBSSs). An ad-hoc network or IBSS is a network that includes a plurality of STAs that are within communication range of each other. The plurality of STAs are configured so that they may communicate with each other using direct peer-to-peer communication (i.e., not via an AP).

[0037] For example, in FIG. 1 , STAs 106-4, 106-5, and 106-6 may be configured to form a first IBSS 112- 1. Similarly, STAs 106-7 and 106-8 may be configured to form a second IBSS 112-2. Since an IBSS doesDocket No.: 24-3039PCT not include an AP, it does not include a centralized management entity. Rather, STAs within an IBSS are managed in a distributed manner. STAs forming an IBSS may be fixed or mobile.

[0038] A STA as a predetermined functional medium may include a medium access control (MAC) layer that complies with an IEEE 802.11 standard. A physical layer interface for a radio medium may be used among the APs and the non-AP stations (STAs). The STA may also be referred to using various other terms, including mobile terminal, wireless device, wireless transmit / receive unit (WTRU), user equipment (UE), mobile station (MS), mobile subscriber unit, or user. For example, the term "user” may be used to denote a STA participating in uplink Multi-user Multiple Input, Multiple Output (MU MIMO) and / or uplink Orthogonal Frequency Division Multiple Access (OFDMA) transmission.

[0039] A physical layer (PHY) protocol data unit (PPDU) may be a composite structure that includes a PHY preamble and a payload in the form of a PHY Convergence Protocol (PLCP) service data unit (PSDU). For example, the PSDU may include a PLCP preamble and header and / or one or more MAC protocol data units (MPDUs). The information provided in the PHY preamble may be used by a receiving device to decode the subsequent data in the PSDU. In instances in which PPDUs are transmitted over a bonded channel (channel formed through channel bonding), the preamble fields may be duplicated and transmitted in each of the multiple component channels. The PHY preamble may include both a legacy portion (or "legacy preamble”) and a non-legacy portion (or "non-legacy preamble”). The legacy preamble may be used for packet detection, automatic gain control and channel estimation, among other uses. The legacy preamble also may generally be used to maintain compatibility with legacy devices. The format of, coding of, and information provided in the non-legacy portion of the preamble is based on the particular IEEE 802.1 1 protocol to be used to transmit the payload.

[0040] A frequency band may include one or more sub-bands or frequency channels. For example, PPDUs conforming to the IEEE 802.11 n, 802.11ac, 802.11 ax and / or 802.11 be standard amendments may be transmitted over the 2.4 GHz, 5 GHz, and / or 6 GHz bands, each of which may be divided into multiple 20 MHz channels. The PPDUs may be transmitted over a physical channel having a minimum bandwidth of 20 MHz. Larger channels may be formed through channel bonding. For example, PPDUs may be transmitted over physical channels having bandwidths of 40 MHz, 80 MHz, 160 MHz, or 520 MHz by bonding together multiple 20 MHz channels.

[0041] FIG. 2 is a block diagram illustrating example implementations of a STA 210 and an AP 260. As shown in FIG. 2, STA 210 may include at least one processor 220, a memory 230, and at least one transceiver 240. AP 260 may include at least one processor 270, a memory 280, and at least one transceiver 290. Processor 220 / 270 may be operatively connected to memory 230 / 280 and / or to transceiver 240 / 290.

[0042] Processor 220 / 270 may implement functions of the PHY layer, the MAC layer, and / or the logical link control (LLC) layer of the corresponding device (STA 210 or AP 260). Processor 220 / 270 may include one or more processors and / or one or more controllers. The one or more processors and / or one or moreDocket No.: 24-3039PCT controllers may comprise, for example, a general-purpose processor, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a logic circuit, or a chipset, for example.

[0043] Memory 230 / 280 may include a read-only memory (ROM), a random-access memory (RAM), a flash memory, a memory card, a storage medium, and / or other storage unit. Memory 230 / 280 may comprise one or more non-transitory computer readable mediums. Memory 230 / 280 may store computer program instructions or code that may be executed by processor 220 / 270 to carry out one or more of the operations / embodiments discussed in the present application. Memory 230 / 280 may be implemented (or positioned) within processor 220 / 270 or external to processor 220 / 270. Memory 230 / 280 may be operatively connected to processor 220 / 270 via various means known in the art.

[0044] Transceiver 240 / 290 may be configured to transmit / receive radio signals. In an embodiment, transceiver 240 / 290 may implement a PHY layer of the corresponding device (STA 210 or AP 260). In an embodiment, STA 210 and / or AP 260 may be a multi-link device (MLD), that is a device capable of operating over multiple links as defined by the IEEE 802.11 standard. As such, STA 210 and / or AP 260 may each implement multiple PHY layers. The multiple PHY layers may be implemented using one or more of transceivers 240 / 290.

[0045] FIG. 3 illustrates an example format of a PPDU 300. As shown, the PPDU 300 may include a PHY preamble, a PHY header, a PSDU, and tail and padding bits.

[0046] The PSDU may include one or more MPDUs, such as a QoS data frame, a MAC management protocol data unit (MMPDU), a MAC control frame, or a QoS null frame. In the case of an MPDU carrying a QoS data frame, the frame body of the MPDU may include a MAC service data unit (MSDU) or an aggregated MSDU (A-MSDU).

[0047] By default, MSDU transport is on a best-effort basis. That is, there is no guarantee that a transmitted MSDU will be delivered successfully. However, the QoS facility uses a traffic identifier (TID) to specify differentiated services on a per-MSDU basis.

[0048] A STA may differentiate MSDU delivery according to designated traffic category (TC) or traffic stream (TS) of individual MSDUs. The MAC sublayer entities determine a user priority (UP) for an MSDU based on a TID value provided with the MSDU. The QoS facility supports eight UP values. The UP values range from 0 to 7 and form an ordered sequence of priorities, with 1 being the lowest value, 7 the highest value, and 0 falling between 2 and 3.

[0049] An MSDU with a particular UP is said to belong to a traffic category with that UP. The UP may be provided with each MSDU at the medium access control service access point (MAC SAP) directly in a UP parameter. An A-MPDU may include MPDUs with different TID values.

[0050] A STA may deliver buffer status reports (BSRs) to assist an AP in allocating UL MU resources. The STA may either implicitly deliver BSRs in the QoS control field or BSR control subfield of any frameDocket No.: 24-3039PCT transmitted to the AP (unsolicited BSR) or explicitly deliver BSRs in a frame sent to the AP in response to a BSRP Trigger frame (solicited BSR).

[0051] The buffer status reported in the QoS control field includes a queue size value for a given TID. The buffer status reported in the BSR control field includes an ACI bitmap, delta TID, a high priority AC, and two queue sizes.

[0052] A STA may report buffer status to the AP, in the QoS control field, of transmitted QoS null frames and QoS data frames and, in the BSR control subfield (if present), of transmitted QoS null frames, QoS data frames, and management frames as defined below.

[0053] The STA may report the queue size for a given TID in the queue size subfield of the QoS control field of transmitted QoS data frames or QoS null frames; the STA may set the queue size subfield to 255 to indicate an unknown / unspecified queue size for that TID. The STA may aggregate multiple QoS data frames or QoS null frames in an A-MPDU to report the queue size for different TIDs.

[0054] The STA may report buffer status in the BSR control subfield of transmitted frames if the AP has indicated its support for receiving the BSR control subfield.

[0055] A High-Efficiency (HE) STA may report the queue size for a preferred AC, indicated by the ACI high subfield, in the queue size high subfield of the BSR control subfield. The STA may set the queue size high subfield to 255 to indicate an unknown / unspecified queue size for that AC.

[0056] A HE STA may report the queue size for ACs indicated by the ACI bitmap subfield in the queue size all subfield of the BSR control subfield. The STA may set the queue size all subfield to 255 to indicate an unknown / unspecified BSR for those ACs.

[0057] FIG. 4 illustrates an example format of a MAC frame 400. In operation, a STA may construct a subset of MAC frames for transmission and may decode a subset of received MAC frames upon validation. The particular subsets of frames that a STA may construct and / or decode may be determined by the functions supported by the STA. A STA may validate a received MAC frame using the frame check sequence (FCS) contained in the frame and may interpret certain fields from the MAC headers of all frames.

[0058] As shown in FIG. 4, a MAC frame 400 includes a MAC header, a variable length frame body, and a frame check sequence (FCS).

[0059] The MAC header includes a frame control field, an optional duration / ID field, address fields, an optional sequence control field, an optional QoS control field, and an optional HT control field.

[0060] The frame control field includes the following subfields: protocol version, type, subtype, "To DS”, “From DS”, “More Fragments”, retry, power management, “More Data , protected frame, and +HTC.

[0061] The protocol version subfield is invariant in size and placement across all revisions of the IEEE 802.11 standard. The value of the protocol version subfield is 0 for MAC frames.Docket No.: 24-3039PCT

[0062] The type and subtype subfields together identify the function of the MAC frame 400. There are three frame types: control, data, and management. Each of the frame types has several defined subtypes. Bits within the subtype subfield are used to indicate a specific modification of the basic data frame (subtype 0). For example, in data frames, the most significant bit (MSB) of the subtype subfield, bit 7 (B7) of the frame control field, is defined as the QoS subfield. When the QoS subfield is set to 1 , it indicates a QoS data frame, which is a data frame that contains a QoS control field in its MAC header. The second MSB of the subtype field, bit 6 (B6) of the frame control field, when set to 1 in data subtypes, indicates a data frame that contain no frame body field.

[0063] The “To DS” subfield indicates whether a data frame is destined to the distribution system (DS). The “From DS” subfield indicates whether a data frame originates from the DS.

[0064] The “More Fragments” subfield is set to 1 in all data or management frames that have another fragment to follow the MSDU or MMPDU carried by the MAC frame. The “More Fragments” subfield is set to 0 in all other frames in which the “More Fragments” subfield is present.

[0065] The retry subfield is set to 1 in any data or management frame that is a retransmission of an earlier frame. It is set to 0 in all other frames in which the retry subfield is present. A receiving STA uses this indication to aid it in the process of eliminating duplicate frames. These rules do not apply for frames sent by a STA under a block agreement.

[0066] The power management subfield is used to indicate the power management mode of a STA.

[0067] The “More Data” subfield indicates to a STA in power save (PS) mode that bufferable units (BUs) are buffered for that STA at the AP. The “More Data" subfield is valid in individually addressed data or management frames transmitted by an AP to a STA in PS mode. The “More Data” subfield is set to 1 to indicate that at least one additional buffered BU is present for the STA.

[0068] The protected frame subfield is set to 1 if the frame body field contains information that has been processed by a cryptographic encapsulation algorithm.

[0069] The +HTC subfield indicates that the MAC frame contains an HT control field.

[0070] The duration / ID field of the MAC header indicates various contents depending on the frame type and subtype and the QoS capabilities of the sending STA. For example, in control frames of the power save poll (PS-Poll) subtype, the duration / ID field carries an association identifier (AID) of the STA that transmitted the frame in the 14 least significant bits (LSB), with the 2 most significant bits (MSB) set to 1 . In other frames sent by STAs, the duration / ID field contains a duration value (in microseconds) which is used by a recipient to update a network allocation vector (NAV). The NAV is a counter that indicates to a STA an amount of time during which the STA must defer from accessing the shared medium.

[0071] Up to four address fields may be present in the MAC frame format. The address fields are used to indicate the basic service set identifier (BSSID), source address (SA), destination address (DA), transmitting address (TA), and receiving address (RA). Certain frames may not contain some of the address fields. CertainDocket No.: 24-3039PCT address field usage may be specified by the relative position of the address field (1-4) within the MAC header, independent of the type of address present in that field . Specifically, the address 1 field always identifies the intended receiver(s) of the frame, and the address 2 field, where present, always identifies the transmitter of the frame.

[0072] The sequence control field includes two subfields, a sequence number subfield and a fragment number subfield. The sequence number subfield in data frames indicates the sequence number of the MSDU (if not in an A-MSDU) or A-MSDU. The sequence number subfield in management frames indicates the sequence number of the frame. The fragment number subfield indicates the number of each fragment of an MSDU or MMPDU. The fragment number is set to 0 in the first or only fragment of an MSDU or MMPDU and is incremented by one for each successive fragment of that MSDU or MMPDU. The fragment number is set to 0 in a MPDU containing an A-MSDU, or in an MPDU containing an MSDU or MMPDU that is not fragmented. The fragment number remains constant in all retransmissions of the fragment.

[0073] The QoS control field identifies the traffic category (TC) or traffic stream (TS) to which the MAC frame belongs. The QoS control field may also indicate various other QoS related, A-MSDU related, and mesh- related information about the frame. This information can vary by frame type, frame subtype, and type of transmitting STA. The QoS control field is present in all data frames in which the QoS subfield of the subtype subfield is equal to 1.

[0074] The HT control field is present in QoS data, QoS null, and management frames as determined by the +HTC subfield of the frame control field.

[0075] The frame body field is a variable length field that contains information specific to individual frame types and subtypes. The frame body may include one or more MSDUs or MMPDUs. The minimum length of the frame body is 0 octets.

[0076] The FCS field contains a 32-bit Cyclic Redundancy Check (CRC) code. The FCS field value is calculated over all of the fields of the MAC header and the frame body field.

[0077] FIG. 5 illustrates an example of a transmit power envelope element 500. An AP or a group of APs may indicate a local transmit power constraint for each of their clients (e.g., for controlling spatial reuse properties of a network) using transmit power envelope element 500. For example, an AP may send transmit power envelope element 500 in a beacon, association response, or probe response frames to its clients. Transmit power envelope element 500 can convey to the clients the local or regulatory maximum transmit powers for various transmission bandwidths or channels within the bandwidth of the BSS. Low client transmit power typically results in lower reliability or lower throughput for the respective clients, but allows other clients from other BSSs to access the channel in parallel. Higher client transmit power will typically result in higher reliability and / or higher throughput for the respective clients, but can cause a busy indication (e.g., a clear channel assessment (CCA) BUSY indication) to other STAs in other BSSs, resulting in fewer parallel transmissions.Docket No.: 24-3039PCT

[0078] As shown in FIG. 5, transmit power envelope element 500 includes an Element ID field, a Length Field, a Transmit Power Information field, and a Maximum Transmit Power field. The Element ID field includes a value that identifies element 500 as a transmit power envelope element The Length field indicates a length of transmit power envelope element 500. The transmit power information field includes a maximum transmit power count subfield, a maximum transmit power interpretation subfield, and a maximum transmit power category subfield. As discussed further below, the maximum transmit power count subfield indicates a number of subfields in the maximum transmit power field. The maximum transmit power interpretation subfield indicates the contents of the maximum transmit power field. For example, different values in the maximum transmit power interpretation subfield indicate different interpretations for the contents of the maximum transmit power field. Values of 0 or 1 in the maximum transmit power interpretation subfield can indicate a local maximum transmit power setting. For example, a value of 0 can indicate that the maximum transmit power field describes local effective isotropic radiated power (El RP), while a value of 1 can indicate that the maximum transmit power field describes local EIRP power spectral density (PSD).

[0079] Values of 2, 3, 4, or 5 in the maximum transmit power interpretation subfield can indicate a regulatory maximum transmit power setting. For example, a value of 2 in the maximum transmit power interpretation subfield can indicate that the maximum transmit power field describes regulatory client EIRP, while a value of 3 in the maximum transmit power interpretation subfield can indicate that the maximum transmit power field describes regulatory client EIRP PSD. A value of 4 in the maximum transmit power interpretation subfield can indicate that the maximum transmit power field describes additional regulatory client EIRP, while a value of 5 in the maximum transmit power interpretation subfield can indicate that the maximum transmit power field describes additional regulatory client EIRP PSD. In the illustrated example, the values of 6 and 7 are reserved.

[0080] The maximum transmit power category subfield can indicate a category for which the maximum transmit powers apply. A value of 0 can indicate the default category, while a value of 1 can indicate a subordinate device (e.g. , a device that operates under the control of an AP (e.g., an indoor AP) with additional requirements specified by the regulatory domain in which the AP is operating). In this example values 2-3, for the maximum transmit power category subfield, are reserved.

[0081] If the maximum transmit power interpretation subfield Is O, 2 or 4 (e.g. indicating EIRP), the maximum transmit power count subfield can indicate a number of subfields in the maximum transmit power field (e.g., subfields indicating the maximum transmit power for X MHz where / equals any of 20, 40, 80, or 160 / 80+80) minus one. For example, in this scenario a maximum transmit power count subfield value of 0 can indicate maximum transmit power is present for 20 MHz, a maximum transmit power count subfield value of 1 can indicate maximum transmit power is present for 20 MHz and 40 MHz, a maximum transmit power count subfield value of 2 can indicate maximum transmit power is present for 20 MHz, 40 MHz, and 80 MHz, and a maximum transmit power count subfield value of 3 can indicate maximum transmit power is present for 20Docket No.: 24-3039PCTMHz, 40 MHz, 80 MHz, and 160 / 80+80 MHz. In these examples a first octet of the maximum transmit power field can indicate maximum transmit power for 20 MHz, a second octet can indicate maximum transmit power for 40 MHz, a third octet can indicate maximum transmit power for 80 MHz, and a fourth octet can indicate maximum transmit power for 160 / 80+80 MHz.

[0082] Maximum transmit power for X MHz fields (e.g., where X = 20, 40, 80, or 160 / 80+80) can define the local maximum transmit power limit of X MHz PPDUs, except for an HE TB PPDU where X MHz is the bandwidth of the pre-HE modulated fields of the HE TB PPDU transmitted by a STA. Each maximum transmit power for X MHz field can be encoded, for example, as an 8-bit 2s complement signed integer (e.g., in the range -64 dBm to 63 dBm with a 0.5 dB step). Setting this field to 63.5 dBm can indicate 63.5 dBm or higher (e.g., no local maximum transmit power constraint).

[0083] If the maximum transmit power interpretation subfield is 1 , 3 or 5 (e.g., indicating EIRP PSD), the maximum transmit power field can have a format in which a first octet indicates a maximum transmit PSD 1 , and subsequent octets (e.g., 2-W) indicate maximum transmit power for a respective corresponding PSD (e.g., a PSD 2-N). In this scenario the maximum transmit power count subfield can determine the value of an integer N according to defined rules. For example, if N is 0, then the maximum transmit power field can contain one maximum transmit PSD subfield that represents the maximum transmit PSD for a PPDU of any bandwidth within the BSS bandwidth. If N is greater than 0, then the maximum transmit power field can have N octets, with N representing the number of 20 MHz channels for which a maximum transmit PSD is indicated. Thehoctet (e.g., where Xequals an integer ranging from 1 to N) of the maximum transmit power field can be the maximum transmit PSD subfield, which can indicate the maximum transmit PSD for the Xh20 MHz channel.

[0084] If the BSS bandwidth is 20, 40, 80, or 160 MHz, then the maximum transmit PSD 1- / V subfields can correspond to 20 MHz channels (e.g., from lowest to highest frequency, respectively), within the indicated bandwidth. If N is equal to 1 , 2, 4, or 8 for 20, 40, 80, or 160 MHz BSS bandwidth, respectively, the indicated bandwidth can be the BSS bandwidth. If N is greater than 0 and less than 2, 4, or 8 for 40, 80, or 160 MHz BSS bandwidth, respectively, then the indicated bandwidth can be the primary 20 MHz, primary 40 MHz, or primary 80 MHz channel for N equal to 1 , 2, or 4, respectively. If N is greater than 1 , 2, or 4 for 20, 40, or 80 MHz BSS bandwidth, respectively, then the indicated bandwidth can be wider than the BSS bandwidth. In this case, the maximum transmit PSD 1-M subfields can correspond to the 20 MHz channels (e.g., from lowest to highest frequency, respectively), within the BSS bandwidth where M is 1 , 2, or 4 for 20, 40, or 80 MHz BSS bandwidth, respectively.

[0085] If the BSS bandwidth is 80+80 MHz, N can be less than or equal to 8. If N is equal to 8 and the BSS bandwidth is 80+80 MHz, the maximum transmit PSD 1-4 subfields can correspond to the 20 MHz channels (e.g., from lowest to highest frequency, respectively), within the 80 MHz segment lower in frequency. The maximum transmit PSD 5-8 subfields can correspond to the 20 MHz channels (e.g., from lowest to highestDocket No.: 24-3039PCT frequency, respectively), within the 80 MHz segment higher in frequency. If N is greater than 0 and less than 8 for 80+80 MHz BSS bandwidth, then the bandwidth indicated by the Maximum Transmit PSD 1- / V subfields can be the primary 20 MHz, primary 40 MHz, or primary 80 MHz channel for Nequal to 1 , 2, or 4, respectively. In this case, the maximum transmit PSD 1 -N subfields correspond to 20 MHz channels (e.g ., from lowest to highest frequency, respectively, within the indicated bandwidth).

[0086] Values of the maximum transmit power count field between 5 and 7 can be reserved for future use to indicate values of N greater than 8. If N is greater than 8, the maximum transmit PSD 1 -8 subfields can correspond to the 20 MHz channels from lowest to highest frequency, respectively, within the 160 MHz channel containing the primary 20 MHz channel.

[0087] The maximum transmit PSD X subfield can be encoded as an 8-bit 2s complement signed integer. The value of -128 can indicate that the corresponding 20 MHz channel cannot be used for transmission. The value of +127 can indicate that no maximum PSD limit is specified for the corresponding 20 MHz channel. For all other values Y of the subfield (e.g., -127 to +126, inclusive), the maximum transmit PSD in the corresponding 20 MHz channel can be Y / 2 dBm / MHz (e.g., ranging from -63.5 to +63 dBm / MHz). If an allowed PSD for the Xth20 MHz channel is known with finer resolution than 20 MHz, the maximum transmit PSD X subfield is set to the lowest allowed PSD within theth20 MHz channel.

[0088] A STA may select a transmit power for transmissions in a channel using one or more constraints. For example, a STA may determine a regulatory maximum transmit power and a local maximum transmit power for a channel in the current regulatory domain using transmit power envelope element 500, among other criteria, before transmitting in the channel. An AP may use a transmit power less than or equal to the regulatory maximum transmit power level for the channel, while also meeting any regulatory mitigation requirement(s). A non-AP STA may use a transmit power less than or equal to the minimum of the local maximum transmit power level and the regulatory maximum transmit power for the channel.

[0089] FIG. 6 illustrates an example control frame which may be used as a trigger frame 600. Trigger frame 600 may be used by an AP to allocate resources for and solicit one or more TB PPDU transmissions from one or more STAs. Trigger frame 600 may also carry other information required by a responding STA to transmit a TB PPDU to the AP.

[0090] As shown in FIG. 6, trigger frame 600 includes a Frame Control field, a Duration field, a receiver address (RA) field, a transmitter address (TA) field, a Common Info field, a User Info List field, a Padding field, and an FCS field.

[0091] The Frame Control field includes the following subfields: protocol version, type, subtype, To DS, From DS, more fragments, retry, power management, more data, protected frame, and +HTC.

[0092] The Duration field indicates various contents depending on frame type and subtype and the QoS capabilities of the sending STA. For example, in control frames of the power save poll (PS-Poll) subtype, the Duration field carries an association identifier (AID) of the STA that transmitted the frame in the 14 leastDocket No.: 24-3039PCT significant bits (LSB), and the 2 most significant bits (MSB) are both set to 1 . In other frames sent by STAs, the Duration field contains a duration value (in microseconds) which is used by a recipient to update a network allocation vector (NAV)

[0093] The RA field is the address of the STA that is intended to receive the incoming transmission from the transmitting station. The TA field is the address of the STA transmitting trigger frame 600 if trigger frame 600 is addressed to STAs that belong to a single BSS. The TA field is the transmitted BSSID if trigger frame 600 is addressed to STAs from at least two different BSSs of the multiple BSSID set.

[0094] The Common Info field specifies a trigger frame type of trigger frame 600, a transmit power of trigger frame 600 in dBm, and several key parameters of a TB PPDU that is transmitted by a STA in response to trigger frame 600. The trigger frame type of a trigger frame used by an AP to receive QoS data using UL MU operation is referred to as a basic trigger frame. A non-EHT non-AP HE STA interprets the Common Info field as HE variant. A non-AP EHT STA interprets the Common Info field as HE variant if B54 and B55 in the Common Info field are equal to 1 ; and interprets the Common Info field as EHT variant otherwise. The HE variant Common Info field and the EHT variant Common Info field use the same encoding method for the Trigger Type, UL Length, More TF, CS Required, LDPC Extra Symbol Segment, AP TX Power, Pre-FEC Padding Factor, PE Disambiguity, and Trigger Dependent Common Info subfields.

[0095] The User Info List field contains zero or more User Info fields. There are three variants for the User Info field, which are the Special User Info field, the EHT variant User Info field, and the HE variant User Info field.

[0096] The Special User Info field is a User Info field that does not carry the user specific information but carries the extended common information not provided in the Common Info field. If the Special User Info field is included in the Trigger frame, then the Special User Info Field Flag subfield of the EHT variant Common Info field is set to 0, otherwise it is set to 1 . The Special User Info field is identified by an AID12 value of 2007 and is optionally present in a Trigger frame that is generated by an EHT AP. The Special User Info field, if present, is located immediately after the Common Info field of the Trigger frame and carries information for the U-SIG field of a solicited EHT TB PPDU. The PHY Version Identifier subfield indicates the PHY version of the solicited TB PPDU that is not an HE TB PPDU. The PHY Version Identifier subfield is set to 0 for EHT. Other values from 1 to 7 are reserved. The UL Bandwidth (BW) Extension subfield, together with the UL BW subfield in the Common Info field, indicates the bandwidth of the solicited TB PPDU from the addressed EHT STA (i.e , the bandwidth in the U-SIG field of the EHT TB PPDU). The EHT Spatial Reuse n subfield carries the values to be included in the corresponding Spatial Reuse n subfield in the U-SIG field of the EHT TB PPDU. The U-SIG Disregard And Validate subfield carries the values to be included in the Disregard and Validate subfields of the U-SIG field of the solicited EHT TB PPDUs. The presence and length of the Trigger Dependent User Info subfield in the Special User Info field depends on the variant of the Trigger frame.Docket No.: 24-3039PCT

[0097] The EHT variant User Info field contains a User Info field per STA addressed in trigger frame 600. The per STA User Info field includes, among others, an AID12 subfield, an RU Allocation subfield, a UL FEC Coding Type subfield, a UL extremely high throughput (EHT) modulation and coding scheme (MCS) (EHT- MCS) subfield, a Reserved subfield, a Spatial Stream (SS) Allocation / RA-RU information subfield, a UL Target Receive Power subfield, and a Power Save (PS) 160 subfield to be used by a STA in a TB PPDU transmitted in response to trigger frame 600, and a Trigger Dependent User Info subfield. The RU Allocation subfield in an EHT variant User Info field in a Trigger frame that is not an MU-RTS Trigger frame, along with the UL BW subfield in the Common Info field, the UL BW Extension subfield in the Special User Info field, and the PS160 subfield in the EHT variant User Info field, identifies the size and the location of the RU or MRU. The values of PS160 subfield and B0 of RU Allocation subfield indicate the 80 MHz frequency subblock in which the RU or MRU is located for 26-tone RU, 52-tone RU, 106-tone RU, 242-tone RU, 484-tone RU, 996-tone RU, 52+26-tone RU, and 106+26-tone RU. The values of PS160 subfield indicates the 160 MHz segment in which the RU or MRU is located for 2®96-tone RU, 996+484-tone MRU, and 996+484+242-tone MRU. The UL FEC Coding Type subfield of the User Info field indicates the code type of the solicited EHT TB PPDU. The UL FEC Coding Type subfield is set to 0 to indicate BCC and set to 1 to indicate LDPC. The UL EHT-MCS subfield of the User Info field indicates the EHT-MCS of the solicited EHT TB PPDU. The SS Allocation subfield of the EHT variant User Info field indicates the spatial streams of the solicited EHT TB PPDU. The UL Target Receive Power subfield indicates the expected receive signal power, measured at the AP’s antenna connector and averaged over the antennas, for the EHT portion of the EHT TB PPDU transmitted on the assigned RU. The Trigger Dependent User Info subfield can be used by an AP to specify a preferred access category (AC) per STA. The preferred AC sets the minimum priority AC traffic that can be sent by a participating STA. The AP determines the list of participating STAs, along with the BW, MCS, RU allocation, SS allocation, Tx power, preferred AC, and maximum duration of the TB PPDU per participating STA. The RA-RU Information subfield is reserved in the EHT variant User Info field.

[0098] The Padding field is optionally present in management frame 400 to extend the frame length to give recipient STAs enough time to prepare a response for transmission one SIFS after the frame is received. The Padding field, if present, is at least two octets in length and is set to all 1s.

[0099] The FCS field is used by a STA to validate a received frame and to interpret certain fields from the MAC headers of a frame.

[0100] FIG. 7 illustrates an example data frame 700 which may be used as a QoS null frame. A QoS null frame refers to a QoS data frame with an empty frame body. QoS null frame includes a QoS control field and an optional HT control field which may contain a buffer status report (BSR) control subfield. A QoS null frame indicating buffer status information may be transmitted by a STA to an AP.Docket No.: 24-3039PCT

[0101] The QoS control field may include a traffic identifier (TID) subfield, an acknowledgment (Ack) policy indicator subfield, and a queue size subfield (or a transmission opportunity (TXOP) duration requested subfield).

[0102] The TID subfield identifies the TC or TS of traffic for which a TXOP is being requested, through the setting of the TXOP duration requested or queue size subfield. The encoding of the TID subfield depends on the access policy (e.g., Allowed value 0 to 7 for enhanced distributed channel access (EDCA) access policy to identify user priority for either TC or TS).

[0103] The ack policy indicator subfield, together with other information, identifies the Ack policy followed upon delivery of the MPDU (e.g., normal Ack, implicit block Ack request, no Ack, block Ack, etc.)

[0104] The queue size subfield is an 8-bit field that indicates the amount of buffered traffic for a given TC or TS at the STA for transmission to the AP identified by the receiver address of the frame containing the subfield. The queue size subfield is present in QoS null frames sent by a STA when bit 4 of the QoS control field is set to 1. The AP may use information contained in the queue size subfield to determine the TXOP duration assigned to the STA or to determine the uplink (UL) resources assigned to the STA.

[0105] In a frame sent by or to a non-high efficiency (non-HE) STA, the following rules may apply to the queue size value:

[0106] The queue size value is the approximate total size, rounded up to the nearest multiple of 256 octets and expressed in units of 256 octets, of all MSDUs and A-MSDUs buffered at the STA (excluding the MSDU or A-MSDU contained in the present QoS Data frame) in the delivery queue used for MSDUs and A-MSDUs with TID values equal to the value indicated in the TID subfield of the QoS Control field.

[0107] A queue size value of 0 is used solely to indicate the absence of any buffered traffic in the queue used for the specified TID.

[0108] A queue size value of 254 is used for all sizes greater than 64 768 octets.

[0109] A queue size value of 255 is used to indicate an unspecified or unknown size.

[0110] In a frame sent by an HE STA to an HE AP, the following rules may apply to the queue size value.

[0111] The queue size value, QS, is the approximate total size in octets, of all MSDUs and A-MSDUs buffered at the STA (including the MSDUs or A-MSDUs contained in the same PSDU as the frame containing the queue size subfield) in the delivery queue used for MSDUs and A-MSDUs with TID values equal to the value indicated in the TID subfield of the QoS control field.

[0112] The queue size subfield includes a scaling factor subfield in bits B14-B15 of the QoS control field and an unsealed value, UV, in bits B8-B13 of the QoS control field. The scaling factor subfield provides the scaling factor, SF.

[0113] A STA obtains the queue size, QS, from a received QoS control field, which contains a scaling factor, SF, and an unsealed value, UV, as follows:

[0114] QS =Docket No.: 24-3039PCT

[0115] 16 xL / V, if SF is equal to 0;

[0116] 1024 + 256 x UV, if SF is equal to 1 ;

[0117] 17408 + 2048 x L / V, if SF is equal to 2;

[0118] 148 480 + 32 768 x UV, if SF is equal to 3 and (JVis less than 62;

[0119] > 2 147 328, if SF equal to is 3 and (A / is equal to 62;

[0120] Unspecified or Unknown, if SF is equal to 3 and UV is equal to 63.

[0121] The TXOP duration requested subfield, which may be included instead of the queue size subfield, indicates the duration, in units of 32 microseconds (us), that the sending STA determines it needs for its next TXOP for the specified TID. The TXOP duration requested subfield is set to 0 to indicate that no TXOP is requested for the specified TID in the current service period (SP). The TXOP duration requested subfield is set to a nonzero value to indicate a requested TXOP duration in the range of 32 us to 8160 us in increments of 32 us.

[0122] The HT control field may include an aggregated control (A-Control) subfield. The A-Control subfield may include a control list subfield including one or more control subfields. A control subfield (of the one or more control subfields) may be a UL power headroom (UPH) control subfield, which as shown in FIG. 7 may include a UL Power Headroom subfield, a Minimum Transmit Power Flag subfield, and two reserved bits. The UL Power Headroom subfield may contain the UPH used for power precorrection. In an example, the UL power headroom subfield may indicate the available UPH (e.g., in units of dB), for the current MCS (e.g ., for a current HE-MCS). For example, the UL power headroom subfield can carry a value 0 to 31 that maps to 0 dB to 31 dB. The minimum transmit power flag subfield may be set to 1 to indicate that the minimum transmit power for the current MCS (e.g., HE-MCS) is reached by the STA, and may be set to 0 otherwise.

[0123] Further, a STA that transmits an HE TB PPDU may transmit the decibel value of its UL power headroom, HRSTA, in the UPH Control subfield of frames (e.g., frames that can carry an HE-variant HT Control field) carried in the HE TB PPDU (e.g., to assist in the AP’s HE-MCS selection). The UL power headroom for an assigned HE-MCS can be defined in the equation below:where Tx^ f represents the maximum UL transmit power of an HE TB PPDU with the assigned HE-MCS (e.g , after considering hardware capability, regulatory requirements, and local maximum transmit power levels, as well as non-IEEE-802.11 in-device coexistence requirements), Tx ™. represents the current UL transmit power of the HE TB PPDU for the assigned HE-MCS (e.g., determined by power control and subject to the non-AP STA's capabilities and other requirements such as power precorrection), and HRSTAis the UL power headroom, in dB, of the HE TB PPDU.

[0124] In an example, if the Minimum Transmit Power Flag subfield in the UPH Control subfield is 1 , then the non-AP STA is transmitting the HE TB PPDU at its minimum Tx ™ for the assigned HE-MCS. The ULDocket No.: 24-3039PCT power headroom may be calculated for the assigned HE-MCS and is independent of transmit operating mode (TOM) parameters provided in any operating mode (OM) control field contained in the same A-Control subfield. Further, in an example the UL power headroom is not normalized to 20 MHz bandwidth (e g., unlike the value in the AP Tx Power subfield).

[0125] As a further example, a non-AP STA may include an HE variant HT Control field containing the UPH Control subfield in frames carried in the A-MPDU of the HE TB PPDU, with the following exceptions. First, a UPH Control subfield may not be included in any frame if the remaining space in the A-MPDU, after inclusion of solicited frames that are required to be included in the A-MPDU but cannot contain an HE variant HT control field, is not sufficient to contain a frame that can be included in the AMPDU and can contain an HE variant HT control field. Second, a UPH control subfield may not be included in a frame if the frame contains control subfields other than UPH control and ONES control subfields and the remaining space in the HE variant HT control field of the frame is not sufficient to contain a UPH control subfield as well. Third, a UPH control subfield may not be included in a frame that is a control frame.

[0126] FIG. 8 shows an example 800 that illustrates use of a TB PPDU. As shown in FIG. 8, example 800 includes an AP 802 and a plurality of STAs 804-1 to 804-8. In an example, AP 802 may transmit a trigger frame (TF) 810 to STAs 804-1 to 804-8 to solicit UL frames from STAs 804-1 to 804-8. STAs 804-1 to 804-8 may respond simultaneously to TF 810 by each transmitting a TB PPDU 820. In an example, TB PPDU 820 may have an 80 MHz bandwidth. As shown in FIG. 8, a STA 804 may duplicate four times over frequency each of the fields L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and EHT-STF to fill out the 80 MHz bandwidth. EHT- LTFs 840 and a data field 850 of PPDU 820 may fill out the entire 80 MHz bandwidth and are not duplicated over frequency. The number of EHT-LTFs transmitted by the STA (in time) is based on the maximum number of spatial streams across all RUs contained in the TB PPDU 820. In example 800, TB PPDU 820 includes eight EHT-LTFs 840-1 to 840-8. AP 802 may acknowledge TB PPDU 820 by transmitting a multi-user block acknowledgment frame M-BA 830.

[0127] As TB PPDUs 820 transmitted by STAs 804-1 to 804-8 are transmitted simultaneously in response to TF 810, precorrection of time, frequency, sampling clock, and power (in the case of a High Efficiency (HE) TB PPDU or extremely high throughput (EHT) TB PPDU) by STAs 804-1 to 804-8 may be necessary to mitigate synchronization and interference issues at AP 802. Specifically, frequency and sampling clock precorrections are needed to prevent inter-carrier interference. Power precorrection is necessary to control interference between TB PPDUs 820.

[0128] In an implementation, TF 810 includes in a User Info field an uplink (UL) Target Receive Power subfield that indicates whether a STA among STAs 804-1 to 804-8 is to transmit TB PPDU 820 at a maximum transmit power. The maximum transmit power may correspond to the STA’s maximum transmit power for the assigned HE-MCS. The STA transmits TB PPDU 820 at the maximum transmit power when the UL TargetDocket No.: 24-3039PCTReceive Power subfield indicates that the maximum transmit power is to be used. Otherwise, the STA calculates the transmit power, Txp™, of TB PPDU 820 for the assigned HE-MCS using the equation:Tx ™ = PLDL+ TargetRxpwrwhere PLDLis the downlink pathloss and TargetRxpwris the expected receive signal power, in units of dBm, as indicated by the UL Target Receive Power subfield in the User Info field of TF 810. If the STA applies beamforming to TB PPDU 820, the STA may take into account the beamforming gain when calculating the transmit power.

[0129] In an implementation, the STA computes PLDLusing the equation:where Txp ris the AP’s transmit power, in units of dBm / 20 MHz, as indicated by an AP Tx Power subfield of a Common Info field of TF 810 and Rxpwris the receive signal power, in units of dBm / 20MHz, of TF 810 at an antenna connector of the STA. Rxpwrmay be an average of the receive signal power over the antennas on which the average PLDLis being computed.

[0130] Due to the finite accuracy of clock generating circuits of an AP and a STA, an AP and an associated STA tuned to the same carrier frequency may have errors in their generated carrier frequencies in reference to the ideal carrier frequency. When an AP receives a TB PPDU as in example 800, the AP may observe a baseband signal whose center frequency has an offset (i.e. carrier frequency offset or CFO) from the DC subcarrier. Similarly, an AP receiving the symbols of a TB PPDU sampled using its own clock may observe that the TB PPDU signal is generated at a clock offset (i.e. symbol clock offset or SCO) from its own sampling clock. Both SCO and CFO may result in receive errors when not properly mitigated. In order to limit the effects of CFO and SCO, a STA compensates for carrier frequency offset (CFO) error and symbol clock error with respect to TF 810 when TB PPDU 820 is a TB PPDU or a non-HT or non-HT duplicate PPDU with the TXVECTOR parameter TRIGGER_RESPONDING set to true. After compensation, the absolute value of residual CFO error with respect to TF 810 shall not exceed the following levels when measured at the 10% point of a complementary cumulative distribution function (CCDF) of CFO errors in Additive White Gaussian Noise (AWGN) at a received power of -60 dBm in the primary 20 MHz channel: 350 Hz for the data subcarriers of a TB PPDU; 2 kHz for a non-HT PPDU or non-HT duplicate PPDU. The residual CFO error measurement on an HE TB PPDU shall be made after the HE-SIG-A field. The residual CFO error measurement on an EHT TB PPDU shall be made after the U-SIG field. The residual CFO error measurement on a non-HT or non-HT duplicate PPDU shall be made after the L-STF field. The symbol clock error shall be compensated by the same ppm amount as the CFO error.

[0131] In a trigger based transmission, an AP transmits a TF to a STA. The TF can indicate an implied UL transmit power (TP) to be used by the STA for an uplink transmission to the AP. This value included in the trigger frame is referred to as an implied UL TP because the actual UL TP is known to the STA, but not theDocket No.: 24-3039PCTAP. The STA can compute the actual value of the UL TP based on a received power of the TF by the STA, an AP TX power parameter in the TF, and an UL target receive power that is also in the TF. This is discussed further, above, in relation to FIG. 8.

[0132] The STA can have multiple TP constraints (e.g., maximum and / or minimum TP levels). These constraints may include regulatory constraints (e.g., dependent on the country in which the STA is operating) and local transmit power constraints set by the AP (e.g., in a beacon and other management frames). The STA may further be constrained to a maximum TP depending on the MCS used by the STA for the uplink transmission (hereinafter referred to as STA maximum TP). A higher TP typically causes more non-linearities in the power amplifiers. Because a higher MCS is generally more sensitive to non-linearities, a higher MCS tends to have a lower STA maximum TP constraint. It is noted that the STA maximum TP may be the same for one or more MCSs. This may happen if a local maximum transmit power constraint or regulatory constraint is lower than the MCS dependent constraint.

[0133] If the implied UL TP is lower than the STA maximum TP of the STA, the STA uses the implied UL TP for the MCS as the uplink transmit power (UL TP) for the uplink transmission. The STA then indicates the difference between the STA maximum TP and the implied TP in an UL TP headroom report included in the uplink transmission. The AP may use this UL TP headroom report to increase the implied UL TP setting for higher reliability, higher throughput, or both. If the implied UL TP is greater than the STA maximum TP, the STA uses the STA maximum TP as the UL TP for the uplink transmission. The STA then indicates 0 in the UL TP headroom report.

[0134] FIG. 9 illustrates an example 900 of UL TP headroom reporting in the presence of an uplink transmit power constraint due to the STA. As illustrated, AP 910 transmits TF 912 to STA 920. TF 912 indicates an implied UL TP with a value B. STA 920 has a STA maximum TP with a value A. In an example, the maximum TP with the value A may be a local maximum TP signaled by AP 910 to STA 920 prior to the sequence of frames shown in example 900. The signaling may be done by AP 910 by transmitting a frame (not shown in FIG. 9) including a transmit power envelope element (e.g. transmit power envelope element 500). In this example, B < A. Based on receiving TF 912, STA 920 transmits a data frame 922 with an UL TP of B. Because the actual UL TP used by STA 920 for data frame 922 is 8, which is less than the STA maximum TP of A of STA 920, STA 920 includes in data frame 922 an indication that the UL TP headroom is A-B.

[0135] On receiving data frame 922 with a positive UL TP headroom of A-B, AP 910 may decide to increase the implied uplink TP (e.g., to increase reliability, throughput, or both) and transmits another TF 914 to STA 920. TF 914 indicates an implied UL TP of A, matching the STA maximum TP of STA 920. STA 920 receives the implied UL TP with the value A in the TF 914 and computes an UL TP headroom of 0 (e.g., because the implied UL TP of A matches the STA maximum TP of A). STA 920 transmits data frame 924 using the UL TP of A, and indicating a UL TP headroom of 0.Docket No.: 24-3039PCT

[0136] If the implied UL TP indicated by an AP to a STA in a TP is greater than a TP constraint (e.g. local max TP, regulatory max TP, STA max TP for the MCS), the STA reports 0 in the UL TP headroom. Generally, an AP may avoid instances in which the UL TP Headroom is zero because such instances may indicate that the implied UL TP is set incorrectly. For example, the AP may set the MCS to a lower value to increase the UL TP Headroom.

[0137] FIG. 10 illustrates an example 1000 that highlights a problem that may arise in TB transmission using a local maximum transmit power TP (local max TP). As shown in FIG. 10, example 1000 includes an AP 1010 and a STA 1020. STA 1020 may be associated with AP 1010. As illustrated, example 1000 may begin with STA 1020 having (or operating using) a local max TP with a value B. For example, AP 1010 may have previously provided to STA 1020 an indication of the local max TP value B (e.g. using a transmit power envelope, such as transmit power envelope element 500 illustrated in FIG. 5, with a maximum transmit power constraint set to B). Subsequently, AP 1010 transmits to STA 1020 a frame 1012 (e.g , a beacon or other management frame) indicating that no local max TP constraint is to be applied by STA 1020. For example, AP 1010 may transmit frame 1012 (e.g., a beacon frame) with a transmit power envelope element (e.g. transmit power envelope element 500 illustrated in FIG. 5) that does not contain a maximum transmit power constraint, or that contains a maximum transmit power constraint equal to the regulatory maximum transmit power constraint, or that indicates a local max TP of 63.5 dBm or higher (i.e., no local maximum transmit power constraint).

[0138] The “no local maximum transmission constraint” indication in frame 1012 ensures that transmit power control from STA 1020 to AP 1010 (e.g., as part of uplink TB transmissions) is not limited by a local max TP constraint. For example, as shown in FIG. 10, in response to AP 1010 transmitting a TF 1014 indicating an implied UL TP of A, where A > B, STA 1020 responds with a data frame 1022 using an UL TP of A (e.g., the implied UL TP) because STA 1020 is not constrained by a local max TP after receiving frame 1012. AP 1010 may indirectly use the implied UL TP (e.g., A) to constrain the TP of STA 1020, in the absence of a local max TP constraint, to limit the interference to other BSSs from transmission of data frame 1022. As the actual value of the implied UL TP is not available to AP 1010, AP 1010 may instead reduce the UL Target Receive Power used by STA 1020 to limit the transmit power of STA 1020.

[0139] However, because STA 1020 does not have a local max TP constraint, STA 1020 may transmit a subsequent data frame 1024 (e.g., as a transmit opportunity holder and not in response to a trigger frame, such as TF 1014) using an UL TP of C, where C is greater than A. Because STA 1020 transmits data frame 1024 independently from a trigger frame, STA 1020 does not use the implied UL TP of A and does not limit the UL TP for data frame 1024 to A. Further, because STA 1020 received frame 1012 removing the local max TP constraint of B, STA 1020 does not use the local max TP of B to limit the UL TP for data frame 1024. This transmission of data frame 1024 using the higher UL TP of C can cause higher interference to otherDocket No.: 24-3039PCTBSSs compared to transmissions of STA 1020 prior to the reception of frame 1012, i.e. because STA 1020 does not use the implied UL TP of A and is not constrained by a local max TP.

[0140] As illustrated, after STA 1020 transmits data frame 1024, AP 1010 transmits another frame 1016 (e.g., a beacon or other management frame) to STA 1020 indicating a local max TP of B that STA 1020 should use for UL transmissions. After receiving frame 1016, STA 1020 may begin using the local max TP constraint, but this does not change the earlier transmission by STA 1020 of data frame 1024 using the higher UL TP of C, potentially causing increased interference with neighboring BSSs and resulting in lower network throughput.

[0141] Embodiments of the present disclosure, as further described below, address the above-described problem associated with existing technologies. In an aspect, a STA receives from an AP a first frame indicating a local max TP level for use by the STA. The STA transmits to the AP a second frame using a first TP level based on the local max TP level. The STA receives from the AP a third frame instructing the STA to ignore the local max TP level for determining a second TP level for transmitting a fourth frame to the AP. The STA transmits to the AP the fourth frame using the second TP level. In an embodiment, based on the fourth frame being in response to the third frame, the second transmit power level is greater than the local maximum TP level. As described further below, this facilitates the STA transmitting a frame (e.g., a data frame as part of a TB PPDU transmission) without being constrained by a local max TP (e.g., for the data frame transmitted in response to a TF). This allows the AP to effectively instruct the STA when to ignore a local max TP for a TB PPDU transmission.

[0142] FIG. 1 1 illustrates an example 1100 of an example operation according to an embodiment. As shown in FIG. 11 , example 1100 includes an AP 1 110 and a STA 1120. STA 1120 may be associated with AP 11 10. As illustrated, example 1 100 may begin with AP 1 110 transmitting a frame 11 12 to STA 1120. Frame 1112 (e.g., a beacon or other management frame) indicates a local max TP of B for STA 1120. For example, frame 1112 may include a transmit power envelope (e.g., transmit power envelope element 500 illustrated in FIG. 5) with a maximum transmit power constraint set to B. This is merely an example, and the local max TP for STA 1120 may be set using any suitable technique (e.g., an earlier transmission from AP 1110). Subsequently, STA 1120 may transmit a data frame 1121 to AP 11 10. Based on frame 1112 indicating a local max TP of 8, STA 1120 may use a UL TP of 8 to transmit data frame 1121. In an example, STA 1 120 may use EDCA to transmit data frame 1 121 .

[0143] Next, AP 1 110 transmits a TF 1 114 to STA 1120. In an embodiment TF 1 114 may indicate an implied UL TP of A, where A>8. In an embodiment, TF 11 14 indicates that STA 1 120 may ignore the local max TP for TB PPDU transmission to AP 1 110. For example, TF 11 14 may include an instruction from AP 1 110 to STA 1120 to ignore the local max TP for a response to TF 1114 (e.g., one or more frames transmitted using TB PPDUs). In one embodiment, this instruction is mandatory and requires the STA 1120 to honor (or apply) the instruction. Alternatively, this instruction is optional and the STA 1120 determines whether to honor (orDocket No.: 24-3039PCT apply) the instruction. AP 11 10 may include the instruction in any suitable portion of TF 11 14, including a common info field, a user info field (e.g., a user info field that further includes an association identifier (AID) of STA 1120), or any other suitable field. As one example, as discussed above in relation to FIG. 5, the local max TP may relate to a maximum PSD, and so the instruction may indicate that STA 1 120 may ignore (e.g., modify) a maximum PSD for transmissions. Further, in an embodiment, the instruction may indicate that STA 1120 may ignore (e.g., modify) a maximum PSD if the transmission uses distributed resource units (DRUs), as discussed below in relation to FIGS. 18-20. As one example, ignoring the maximum PSD for transmission using DRUs may include using a different maximum PSD for transmission using DRUs.

[0144] In example 1100, the instruction in TF 1114 to ignore the local max TP applies to only the response from STA 1 120 to TF 11 14. STA 1 120 honors (or applies) this instruction (e.g., the instruction is mandatory or the STA 1120 determines to honor (or apply) the instruction) and responds to TF 11 14 by transmitting data frame 1122 using a UL TP of A (e.g., the implied UL TP indicated by the TF 1114), which is greater than the local max TP of B. AP 1110 may indicate the implied UL TP to STA 1 120 to constrain the TP for STA 1 120, separately from the local max TP, so that the interference to other BSSs is minimized.

[0145] Subsequently, STA 1 120 may transmit another data frame 1 124 to AP 1110. For example, STA 1120 may transmit data frame 1124 after obtaining a TXOP on the channel. In an embodiment, as data frame 1124 is not in response to TF 1114, STA 1120 may transmit data frame 1124 with an UL TP of B (e.g., honoring the local max TP of B indicated in frame 11 12).

[0146] While FIG. 1 1 illustrates an AP indicating in a TF that a STA should ignore a local max TP for a TB PPDU, this is merely an example. An AP may use any suitable technique to indicate that the STA should ignore a local max TP for a TB PPDU, and this indication can serve as a mandatory instruction or an optional instruction. For example, as discussed below in relation to FIGS. 12-13 the AP may indicate in a management frame an instruction (e.g., an optional or mandatory instruction) that the STA may ignore a local max TP for a TB PPDU transmission.

[0147] Further, indicating that STA 1120 may ignore the local max TP for TB PPDU transmission to AP 11 10 is also merely an example. Alternatively, or in addition, AP 1110 may indicate to STA 1 120 (e.g., provide an instruction to STA 1120) to ignore the local max TP for transmission of any PPDU, transmission for a time duration, transmission for a number of intervals (e.g., a number of beacon intervals), or using any other suitable technique.

[0148] FIG. 12 illustrates a further example 1200 of an example operation, according to an embodiment. As shown in FIG. 12, example 1200 includes an AP 1210 and a STA 1220. STA 1220 may be associated with AP 1210. As illustrated, example 1200 may begin with AP 1210 transmitting a frame 1212 to STA 1220 indicating that STA 1220 is to ignore the local max TP on TB PPDU transmissions.

[0149] In an embodiment, prior to the transmission of frame 1212, STA 1220 may be configured to honor a local max TP of B. In an example, AP 1210 may transmit a frame (e.g., a beacon or other managementDocket No.: 24-3039PCT frames not shown in the figure) indicating a local max TP of B for STA 1220. For example, the frame may include a transmit power envelope (e.g., transmit power envelope element 500 illustrated in FIG. 5) with a maximum transmit power constraint set to 8. This is merely an example, and the local max TP for STA 1220 may be set using frame 1212 (e.g. by including a transmit power envelope element) or using any suitable technique (e.g., an earlier transmission from AP 1210). The STA 1220 may transmit one or more data frames (not shown in FIG. 12) to the AP 1210 using the local max TP of 8 as the UL TP.

[0150] In an embodiment, frame 1212 indicates that STA 1220 may ignore the local max TP for TB PPDU transmission to AP 1210. For example, frame 1212 may include an instruction (e.g., IE 1500 illustrated in FIG. 15, below, or any other suitable instruction) from AP 1210 to STA 1220 to ignore the local max TP for a TB response. In one embodiment, this instruction is mandatory and requires the STA 1220 to honor (or apply) the instruction. Alternatively, this instruction is optional and the STA 1220 determines whether to honor (or apply) the instruction. AP 1210 then transmits TF 1214 to STA 1220, indicating an implied UL TP of A, where A>B. As one example, as discussed above in relation to FIG. 5, the local max TP may relate to a maximum PSD, and so the instruction may indicate that STA 1220 may ignore (e.g., modify) a maximum PSD for transmissions. Further, in an embodiment, the instruction may indicate that STA 1220 may ignore (e.g., modify) a maximum PSD if the transmission uses distributed resource units (DRUs), as discussed below in relation to FIGS. 18-20. As one example, ignoring the maximum PSD for transmission using DRUs may include using a different maximum PSD for transmission using DRUs.

[0151] In an embodiment, the instruction in frame 1212 (e.g., an optional or mandatory instruction) to ignore the local max TP applies to the response from STA 1220 to TF 1214 (e.g., one or more frames transmitted using TB PPDUs). STA 1220 honors (or applies) this instruction (e.g., the instruction is mandatory or the STA 1220 determines to honor (or apply) the instruction) and responds to TF 1214 by transmitting data frame 1222 using a UL TP of A (e.g., the implied UL TP indicated by the TF 1214), which is greater than the local max TP of 8. AP 1210 may indicate the implied UL TP to STA 1220 to constrain the TP for STA 1220, separately from the local max TP, so that the interference to other BSSs is minimized.

[0152] In one embodiment, the instruction in frame 1212 to ignore the local max TP applies to only the response from STA 1220 to TF 1214, and not subsequent PPDUs transmitted by STA 1220. In this embodiment, as illustrated in example 1200, STA 1220 may transmit another data frame 1224 to AP 1210. For example, STA 1220 may transmit data frame 1224 after obtaining a TXOP on the channel. In an embodiment, as the instruction in frame 1212 does not apply to data frame 1224, STA 1220 may transmit data frame 1224 with an UL TP of 8 (e.g., honoring the local max TP of 8).

[0153] Alternatively, or in addition, the instruction in frame 1212 to ignore the local max TP applies to both the response from STA 1220 to TF 1214, and additional TB PPDUs (e.g., where each of the additional TB PPDU may be transmitted in response to additional respective TFs). In one example, the instruction in frame 1212 can apply to all subsequent TB PPDUs transmitted by STA 1220 after receiving frame 1212. In anotherDocket No.: 24-3039PCT example, the instruction in frame 1212 can apply to a fixed number N of subsequent TB PPDUs transmitted by STA 1220 after receiving frame 1212. In another example, the instruction in frame 1212 can apply to any suitable subset of TB PPDUs transmitted by STA 1220 after receiving frame 1212. Further, in an embodiment, the frame 1212 can indicate the TB PPDUs for which the instruction applies (e.g., using a duration field for an IE 1500 illustrated in FIG. 15, below, or any other suitable field).

[0154] As discussed above in relation to FIG. 1 1 , indicating that STA 1220 may ignore the local max TP for TB PPDU transmission to AP 1210 is merely an example. Alternatively, or in addition, AP 1210 may indicate to STA 1220 (e.g., provide an instruction to STA 1220) to ignore the local max TP for transmission of any PPDU, transmission for a time duration, transmission for a number of intervals (e.g., a number of beacon intervals), or using any other suitable technique.

[0155] FIG. 13 illustrates an example 1300 of an example operation, according to an embodiment. As shown in FIG. 13, example 1300 includes an AP 1310 and a STA 1320. STA 1320 may be associated with AP 1310. As illustrated, example 1300 may begin with AP 1310 transmitting a frame 1312 to STA 1320 indicating that STA 1320 may optionally ignore the local max TP on TB PPDU transmissions.

[0156] In an embodiment, prior to the transmission of frame 1312, STA 1320 may be configured to honor a local max TP of B. In an example, AP 1310 may transmit a frame (e.g., a beacon or other management frames not shown in the figure) indicating a local max TP of B for STA 1320. For example, the frame may include a transmit power envelope (e.g., transmit power envelope element 500 illustrated in FIG. 5) with a maximum transmit power constraint set to B. This is merely an example, and the local max TP for STA 1320 may be set using frame 1312 (e.g. by including a transmit power envelope element) or using any suitable technique (e g., an earlier transmission from AP 1310). The STA 1320 may transmit one or more data frames to the AP 1310 using the local max TP of B as the UL TP.

[0157] In an embodiment, frame 1312 further indicates that STA 1320 may optionally ignore the local max TP for TB PPDU transmission to AP 1310. For example, frame 1312 may include an instruction (e.g., IE 1500 illustrated in FIG. 15, below, or any other suitable instruction) from AP 1310 to STA 1320 to optionally ignore the local max TP for a TB response. AP 1310 then transmits TF 1314 to STA 1320, indicating an implied UL TP of A, where A>B. As one example, as discussed above in relation to FIG. 5, the local max TP may relate to a maximum PSD, and so the instruction may indicate that STA 1320 may ignore (e.g., modify) a maximum PSD for transmissions. Further, in an embodiment, the instruction may indicate that STA 1320 may ignore (e.g , modify) a maximum PSD if the transmission uses distributed resource units (DRUs), as discussed below in relation to FIGS. 18-20. As one example, ignoring the maximum PSD for transmission using DRUs may include using a different maximum PSD for transmission using DRUs.

[0158] In an embodiment, the instruction in frame 1312 to optionally ignore the local max TP applies to the response from STA 1320 to TF 1314 (e.g., one or more frames transmitted using TB PPDUs). STA 1320 honors (or applies) this instruction and, optionally, determines to respond to TF 1314 by transmitting dataDocket No.: 24-3039PCT frame 1322 using a UL TP of A (e.g., the implied UL TP indicated by the TF 1314), which is greater than the local max TP of B. Further, STA 1320 indicates in data frame 1322 that it ignored the local max TP. For example, STA 1320 can use an enhanced UPH control subfield (e.g., enhanced UPH control subfield 1400 as illustrated in FIG. 14), or any other suitable technique, to indicate to AP 1310 that STA 1320 optionally determined to ignore the local max TP. AP 1310 may further indicate the implied UL TP to STA 1320 to constrain the TP for STA 1320, separately from the local max TP and regardless of whether STA 1320 determines to optionally ignore the local max TP, so that the interference to other BSSs is minimized, with an UL TP of B (e.g., honoring the local max TP of B).

[0159] In one embodiment, the instruction in frame 1312 to optionally ignore the local max TP applies to only the response from STA 1320 to TF 1314, and not subsequent PPDUs transmitted by STA 1320. In this embodiment, as illustrated in example 1300, STA 1320 may transmit another data frame 1324 to AP 1310. For example, STA 1320 may transmit data frame 1324 after obtaining a TXOP on the channel. In an embodiment, as the instruction in frame 1312 does not apply to data frame 1324, STA 1320 may transmit data frame 1324 with an UL TP of B (e.g., honoring the local max TP of B).

[0160] Alternatively, or in addition, the instruction in frame 1312 to optionally ignore the local max TP applies to both the response from STA 1320 to TF 1314, and additional TB PPDUs (e.g., where each of the additional TB PPDU may be transmitted in response to additional respective TFs). In one example, the instruction in frame 1312 can apply to all subsequent TB PPDUs transmitted by STA 1320 after receiving frame 1312. In another example, the instruction in frame 1312 can apply to a fixed number N of subsequent TB PPDUs transmitted by STA 1320 after receiving frame 1312. In another example, the instruction in frame 1312 can apply to any suitable subset of TB PPDUs transmitted by STA 1320 after receiving frame 1312 Further, in an embodiment, the frame 1312 can indicate the TB PPDUs for which the instruction applies (e.g., using a duration field for an IE 1500 illustrated in FIG. 15, below, or any other suitable field).

[0161] As discussed above in relation to FIGS. 11 -12, indicating that STA 1320 may ignore the local max TP for TB PPDU transmission to AP 1310 is merely an example. Alternatively, or in addition, AP 1310 may indicate to STA 1320 (e.g., provide an instruction to STA 1320) to ignore the local max TP for transmission of any PPDU, transmission for a time duration, transmission for a number of intervals (e.g., a number of beacon intervals), or using any other suitable technique.

[0162] FIG. 14 illustrates an example of enhanced UPH control, according to an embodiment. In an embodiment, a STA (e.g., STA 1320 illustrated in FIG. 13) can use an enhanced UPH control subfield 1400 to report whether the STA ignored the local max TP in a TB PPDU transmission. As discussed above in relation to FIG. 7, a data frame 700 can include a UPH control subfield with a UL power headroom subfield, a minimum transmit power flag subfield, and two reserved bits. A data frame (e.g., frame 1322 illustrated in FIG. 13) can instead, or in addition, include enhanced UPH control subfield 1400.Docket No.: 24-3039PCT

[0163] In an embodiment, enhanced UPH control subfield 1400 includes a local max transmit power ignored subfield (e.g a one bit flag using one of the two reserved bits in the UPH control subfield). In an embodiment, if the local max transmit power ignored subfield is set to 0, this indicates that the STA determined to honor the local max TP, rather than ignoring the local max TP, for transmission of the relevant data frame. If the local max transmit power ignored subfield is set to 1 , this indicates that the STA determined to ignore the local max TP for transmission of the relevant data frame.

[0164] FIG. 15 illustrates an example management frame IE 1500, according to an embodiment. In an embodiment, an AP (e.g., AP 1210 illustrated in FIG. 12 or AP 1310 illustrated in FIG. 13) can use IE 1500 to indicate an instruction (e.g., a mandatory instruction as illustrated in FIG. 12 or an optional instruction as illustrated in FIG. 13) to a STA to ignore a local max TP for a TB upload. The IE 1500 can be carried in any suitable frame (e.g., frame 1212 illustrated in FIG. 12 or frame 1312 illustrated in FIG. 13), including a beacon frame, a probe response frame, or an action frame. Further, the AP may transmit the IE 1500 to a single STA or broadcast the IE 1500 to all STAs (e.g., all STAs in a BSS associated with the AP).

[0165] In an embodiment, IE 1500 includes an element ID field, a length field, an ignore local maximum transmit power field, and a duration field. The element ID field can indicate that the IE 1500 includes the instruction to ignore local max TP, and the length field can indicate the length of the IE 1500. The ignore local maximum transmit power field can be a single bit flag or a multi-bit field. Further, the ignore local maximum transmit power field can be combined with other information fields (e.g., for other lEs used for other purposes) for efficiency (e.g., to reduce transmission size of a frame including the ignore local maximum transmit power field).

[0166] In an embodiment, the duration / number of beacon intervals field can indicate how long the STA may ignore the local maximum transmit power after receiving the IE 1500. In one embodiment, the ignore local maximum transmit power instruction applies to a TB PPDU (e.g., one or more frames transmitted by a STA using TB PPDUs in response to a TF from an AP). Alternatively, or in addition, the ignore local maximum transmit power instruction can apply to multiple TB PPDU transmissions (e.g., responses to multiple TFs from an AP), multiple data frames, or any other suitable PPDU transmissions. The duration field can indicate a number of TB PPDU transmissions for which the STA may ignore local maximum transmit power, a number of data frames for which the STA may ignore local maximum transmit power, a duration in time for which the STA may ignore local maximum transmit power, a number of beacon intervals for which the STA may ignore local maximum transmit power, or any other suitable duration.

[0167] As would be understood by a person of skill in the art based on the teachings herein, the embodiments as described by the above examples may be readily extended to implementations including more than one STA.Docket No.: 24-3039PCT

[0168] As would be understood by a person of skill in the art based on the teachings herein, the embodiments as described by the above examples may be readily extended to implementations including more than one AP.

[0169] As would be understood by a person of skill in the art based on the teachings herein, the embodiments as described by the above examples may be readily extended to scenarios in which any of the APs or any of the STAs may comprise a MLD, comprising at least one affiliated AP or affiliated STA.

[0170] FIG. 16 illustrates an example process 1600 according to an embodiment of the present disclosure. Example process 1600 may be performed by a suitable STA, such as STA 1120 illustrated in FIG. 11 , STA 1220 illustrated in FIG. 12, or STA 1320 illustrated in FIG. 13. As shown in FIG. 16, process 1600 may include steps 1602 and 1604.

[0171] Step 1602 includes receiving, by a station (STA) from an access point (AP), one or more first frames indicating: (i) a local maximum transmit power level for use by the STA, and (II) that the STA is to ignore the local maximum transmit power level for determining a first transmit power level for transmitting a second frame to the AP. In an embodiment the AP includes any suitable AP, such as AP 1110 illustrated in FIG. 1 1 , AP 1210 illustrated in FIG. 12, or AP 1310 illustrated in FIG. 13, for example.

[0172] Step 1604 includes transmitting, by the STA to the AP, the second frame using the first transmit power level.

[0173] In an embodiment, a third frame of the one or more first frames indicates the local maximum transmit power level.

[0174] In an embodiment, the third frame includes a management frame.

[0175] In an embodiment, the third frame includes a beacon frame, an association response frame, or a probe response frame.

[0176] In an embodiment, the local maximum transmit power level is provided in a transmit power envelope element of the third frame.

[0177] In an embodiment, based on the second frame being in response to a fourth frame, the first transmit power level is greater than the local maximum transmit power level.

[0178] In an embodiment, the fourth frame includes a trigger frame.

[0179] In an embodiment, transmitting the second frame includes transmitting the second frame using a trigger based physical layer protocol data unit (TB PPDU).

[0180] In an embodiment, the one or more first frames include the fourth frame.

[0181] In an embodiment, the one or more first frames indicating that the STA is to ignore the local maximum transmit power level includes the trigger frame indicating that the STA is to ignore the local maximum transmit power level.

[0182] In an embodiment, the trigger frame includes an indication that the STA is to ignore the local maximum transmit power, and the indication is provided in a common info field of the trigger frame.Docket No.: 24-3039PCT

[0183] In an embodiment, the trigger frame includes an indication that the STA is to ignore the local maximum transmit power, and the indication is provided in a user info field of the trigger frame, the user info field including an association identifier (AID) of the STA

[0184] In an embodiment, the one or more frames indicating that the STA is to ignore the local maximum transmit power level includes a fifth frame of the one or more frames indicating that the STA is to ignore the local maximum transmit power level.

[0185] In an embodiment, the fifth frame includes a management frame.

[0186] In an embodiment, the fifth frame includes a beacon frame, an association response frame, or a probe response frame.

[0187] In an embodiment, the fifth frame includes an indication that the STA is to ignore the local maximum transmit power level, and the indication is provided in an information element (IE) of the fifth frame .

[0188] In an embodiment, the second frame includes an indication that the first transmit power level is greater than the local maximum transmit power level.

[0189] In an embodiment, the indication is provided in an uplink power headroom (UPH) control field of the second frame.

[0190] In an embodiment, the example process 1600 further includes transmitting, by the STA to the AP, a sixth frame using a second transmit power level, where the second transmit power level is based on the local maximum transmit power level.

[0191] In an embodiment, the second transmit power level includes a transmit power level adapted to a path loss of an uplink channel between the STA and AP.

[0192] In an embodiment, the second transmit power level is equal to the local maximum transmit power level when a transmit power level adapted to a path loss of an uplink channel between the STA and AP exceeds the local maximum transmit power level.

[0193] FIG. 17 illustrates an example process 1700 according to an embodiment of the present disclosure. Example process 1700 may be performed by a suitable AP, such as such as AP 1 110 illustrated in FIG. 11 , AP 1210 illustrated in FIG. 12, or AP 1310 illustrated in FIG. 13. As shown in FIG. 17, process 1700 may include steps 1702 and 1704.

[0194] Step 1702 includes transmitting, by an access point (AP) to a station (STA), one or more first frames indicating: (i) a local maximum transmit power level for use by the STA, and (ii) that the STA is to ignore the local maximum transmit power level for determining a first transmit power level for transmitting a second frame to the AP. In an embodiment the STA includes a suitable non-AP STA, such as STA 1 120 illustrated in FIG. 11 , STA 1220 illustrated in FIG. 12, or STA 1320 illustrated in FIG. 13, for example.

[0195] Step 1704 includes receiving, by the AP from the STA, the second frame transmitted by the STA using the first transmit power level.Docket No.: 24-3039PCT

[0196] In an embodiment, a third frame of the one or more first frames indicates the local maximum transmit power level.

[0197] In an embodiment, the third frame includes a management frame.

[0198] In an embodiment, the third frame includes a beacon frame, an association response frame, or a probe response frame.

[0199] In an embodiment, the local maximum transmit power level is provided in a transmit power envelope element of the third frame.

[0200] In an embodiment, based on the second frame being in response to a fourth frame, the first transmit power level is greater than the local maximum transmit power level.

[0201] In an embodiment, the fourth frame includes a trigger frame.

[0202] In an embodiment, the STA transmitting the second frame includes the STA transmitting the second frame using a trigger based physical layer protocol data unit (TB PPDU).

[0203] In an embodiment, the one or more first frames include the fourth frame.

[0204] In an embodiment, the one or more first frames indicating that the STA is to ignore the local maximum transmit power level includes the trigger frame indicating that the STA is to ignore the local maximum transmit power level.

[0205] In an embodiment, the trigger frame includes an indication that the STA is to ignore the local maximum transmit power level, and wherein the indication is provided in a common info field of the trigger frame.

[0206] In an embodiment, the trigger frame includes an indication that the STA is to ignore the local maximum transmit power level, and the indication is provided in a user info field of the trigger frame, the user info field including an association identifier (AID) of the STA.

[0207] In an embodiment, the one or more frames indicating that the STA is to ignore the local maximum transmit power level includes a fifth frame of the one or more frames indicating that the STA is to ignore the local maximum transmit power level.

[0208] In an embodiment, the fifth frame includes a management frame.

[0209] In an embodiment, the fifth frame includes a beacon frame, an association response frame, or a probe response frame.

[0210] In an embodiment, the fifth frame includes an indication that the STA is to ignore the local maximum transmit power level, and the indication is provided in an information element (IE) of the fifth frame .

[0211] In an embodiment, the second frame includes an indication that the first transmit power level is greater than the local maximum transmit power level.

[0212] In an embodiment, the indication is provided in an uplink power headroom (UPH) control field of the second frame.Docket No.: 24-3039PCT

[0213] In an embodiment, the example process 1700 further includes receiving, by the AP from the STA, a sixth frame transmitted by the STA using a second transmit power level, where the second transmit power level is based on the local maximum transmit power level.

[0214] In an embodiment, the second transmit power level includes a transmit power level adapted to a path loss of an uplink channel between the STA and AP.

[0215] In an embodiment, the second transmit power level is equal to the local maximum transmit power level when a transmit power level adapted to a path loss of an uplink channel between the STA and AP exceeds the local maximum transmit power level.

[0216] FIG. 18 illustrates an example 1800 of an operation using RUs. Tables 27-7, 27-8, and 27-9 of the IEEE 802.1 1 standard provide RU indices and subcarrier ranges for RUs, for different RU type and PPDU bandwidth combinations. For example, for a 52-tone RU and a 20 MHz PPDU bandwidth, the PPDU may have four RUs, indexed RU 1 , RU 2, RU 3, and RU 4. RU 1 corresponds to the subcarrier range [-121 :-70], RU 2 corresponds to the subcarrier range [-68:-17], RU 3 corresponds to the subcarrier range [17:68], and RU 4 corresponds to the subcarrier range [70:121], For example, an allocation comprising RU 1 , RU 2, RU 3, and RU 4 may be as illustrated in FIG. 18. As shown, RU 1 , RU 2, RU 3, and RU 4 each include a contiguous set of tones over a respective part of the PPDU bandwidth. The respective parts of the PPDU bandwidth covered by different RUs are non-overlapping and may be separated from one another by one or more null tones. In an example where a PPDU comprises a single RU, the set of tones of the RU may cover the entire PPDU bandwidth. The RUs described in FIG. 18 may be referred to as regular RUs (RRUs).

[0217] FIG. 19 illustrates an example 1900 of an operation using distributed RUs (DRUs). The existing IEEE 802 1 1 standard defines only RUs including contiguous sets of tones (e.g., as illustrated in FIG. 13). Such RUs are hereinafter referred to as non-distributed RUs (non-DRUs). U.S. Patent 11 ,044,057 proposes an RU, called distributed RU (DRU), that includes a non-contiguous set of tones spread over the PPDU bandwidth. An example allocation of distributed RUs is shown in FIG. 19. As shown, rather than an RU being composed of a contiguous set of tones that cover a respective part only of the PPDU bandwidth, a DRU may include a non-contiguous set of tones that may be spread over the entire bandwidth of the PPDU.

[0218] Spreading the RU over the entire PPDU bandwidth may significantly decrease the power spectral density (PSD) of the PPDU. This may enable the device (e.g., an AP or STA) transmitting the PPDU to operate in spectrum parts having more stringent PSD requirements. For example, expanded unlicensed use of the 6 Gigahertz Band permits operation over an additional 1 .2 GHz of bandwidth (operating bands U-NII- 5 (5.925-6.425 GHz), U-NII-6 (6.425-6.525 GHz), U-NII-7 (6.525-6.875 GHz), and U-NII-8 (6.875-7.125 GHz)) under low power indoor (LPI) PSD requirements (5 dBm / MHz for an AP and -1dBm / MHz for a STA). Alternatively, or additionally, a device that spreads an RU over the entire PPDU bandwidth may leverage the lower PSD resulting from the use of distributed RUs to increase the transmit power of the PPDU. This may be particularly useful in UL MU OFDMA as it may allow each transmitting STA to boost its transmit power,Docket No.: 24-3039PCT thereby resulting in higher received powers for all tones and a significantly enhanced overall spectrum efficiency.

[0219] FIG. 20 illustrates an example 2000 of an operation using distributed RUs. As shown in FIG. 20, example 2000 includes APs 2002, and STAs 2004 and 2006. STAs 2004 and 2006 may be associated with AP 2002.

[0220] Example 2000 begins with AP 2002 transmitting a trigger frame 2010. In example 2000, trigger frame 2010 may solicit an uplink MU transmission from STAs 2004 and 2006. The uplink MU transmission may comprise simultaneous transmissions by STAs 2004 and 2006 of respective TB PPDUs 2012 and 2014. The uplink MU transmission may be associated with a frequency channel bandwidth over which TB PPDUs 2012 and 2014 are transmitted. Trigger frame 2010 may thus comprise an RU allocation for STAs 2004 and 2006 to transmit TB PPDUs 2012 and 2014 to AP 2002, e.g . , a distributed RU (DRU) allocation. The DRU allocation may allocate one or more DRUs to each of STAs 2004 and 2006. In example 2000, the DRU allocation may allocate a first DRU (DRU 1) to STA 2004 and a second DRU (DRU 2) to STA 2006. DRU 1 and DRU 2 may be as illustrated in FIG. 19 described above. Specifically, each of DRU 1 and DRU 2 may comprise a noncontiguous set of tones that may be spread over the entire frequency channel bandwidth associated with the uplink MU transmission.

[0221] In response to trigger frame 2010, STAs 2004 and 2006 may transmit TB PPDUs 2012 and 2014, respectively. In an example, as shown in FIG. 20, TB PPDUs 2012 and 2014 may each comprise a non-DRU portion and a distributed resource portion (DRU portion). The non-DRU portion of TB PPDU 2012 (or TB PPDU 2014) may comprise a preamble portion of TB PPDU 2012 (or TB PPDU 2014). The DRU portion of TB PPDU 2012 (or TB PPDU 2014) may comprise a data portion (comprising a data field) of TB PPDU 2012 (or TB PPDU 2014). In an example, TB PPDUs 2012 and 2014 may be UHR TB PPDUs used by UHR devices according to the IEEE 802.1 1 standard. In an example, TB PPDUs 2012 and 2014 may have a format similar to an HE TB PPDU or an EHT TB. The non-DRU of TB PPDU 2012 (or TB PPDU 2014) may correspond to L-STF, L-LTF, L-SIG, RL-SIG, HE-SIG-A and L-STF, L-LTF, L-SIG, RL-SIG, U-SIG of an HE TB PPDU and an EHT TB PPDU respectively. Similarly, the DRU of TB PPDU 2012 (or TB PPDU 2014) may correspond to HE-STF, HE-LTF and DATA and EHT-STF, EHT-LTF and DATA of an HE TB PPDU and an EHT TB PPDU respectively.

[0222] In an example, the DRU portions of TB PPDUs 2012 and 2014 may be transmitted over respectively DRU 1 and DRU 2 as indicated by trigger frame 2010. In an example, the non-DRU portion of TB PPDU 2012 (and / or TB PPDU 2014) may be transmitted over one or more non-DRUs. The one or more non-DRUs may correspond respectively to one or more contiguous sets of resources that may cover respectively one or more parts of the frequency channel bandwidth of the uplink MU transmission. For example, the one or more non-DRUs may be as illustrated in FIG. 18 described above. In an example, the non-DRU portions of TB PPDUs 2012 and 2014 may be transmitted over the same or frequency overlapping non-DRUs. In anotherDocket No.: 24-3039PCT example, the non-DRU portions of TB PPDUs 2012 and 2014 may be transmitted over different or frequency non-overlapping non-DRUs. In an example, trigger frame 2010 may indicate the one or more non-DRUs for transmission of the non-DRU portions of TB PPDUs 2012 and 2014. In another example, the non-DRU portions of TB PPDUs 2012 and 2014 may be transmitted over the entire frequency channel bandwidth of the uplink MU transmission.

Claims

Docket No.: 24-3039PCTCLAIMSWhat is claimed is:

1. A method comprising: receiving, by a station (STA) from an access point (AP), a first frame indicating a local maximum transmit power level for use by the STA; transmitting, by the STA to the AP, a second frame using a first transmit power level based on the local maximum transmit power level; receiving, by the STA from the AP, a third frame instructing the STA to ignore the local maximum transmit power level for determining a second transmit power level for transmitting a fourth frame to the AP; and transmitting, by the STA to the AP, the fourth frame using the second transmit power level, wherein based on the fourth frame being in response to the third frame, the second transmit power level is greater than the local maximum transmit power level.

2. A method comprising: receiving, by a station (STA) from an access point (AP), one or more first frames indicating: a local maximum transmit power level for use by the STA; and that the STA is to ignore the local maximum transmit power level for determining a first transmit power level for transmitting a second frame to the AP; and transmitting, by the STA to the AP, the second frame using the first transmit power level.

3. The method of claim 2, wherein a third frame of the one or more first frames indicates the local maximum transmit power level.

4. The method of claim 3, wherein the third frame comprises a management frame.

5. The method of any of claims 3-4, wherein the third frame comprises a beacon frame, an association response frame, or a probe response frame.

6. The method of any of claims 3-5, wherein the local maximum transmit power level is provided in a transmit power envelope element of the third frame.

7. The method of any of claims 2-6, wherein based on the second frame being in response to a fourth frame, the first transmit power level is greater than the local maximum transmit power level.

8. The method of claim 7, wherein the fourth frame comprises a trigger frame.

9. The method of any of claims 2-8, wherein transmitting the second frame comprises transmitting the second frame using a trigger based physical layer protocol data unit (TB PPDU).

10. The method of any of claims 7-9, wherein the one or more first frames comprises the fourth frame.11 . The method of any of claims 8-10, wherein the one or more first frames indicating that the STA is to ignore the local maximum transmit power level comprises the trigger frame indicating that the STA is to ignore the local maximum transmit power level.Docket No.: 24-3039PCT12. The method of claim 11 , wherein the trigger frame comprises an indication that the STA is to ignore the local maximum transmit power level, and wherein the indication is provided in a common info field of the trigger frame.

13. The method of claim 11 , wherein the trigger frame comprises an indication that the STA is to ignore the local maximum transmit power level, and wherein the indication is provided in a user info field of the trigger frame, the user info field comprising an association identifier (AID) of the STA.

14. The method of any of claims 2-10, wherein the one or more first frames indicating that the STA is to ignore the local maximum transmit power level comprises a fifth frame of the one or more first frames indicating that the STA is to ignore the local maximum transmit power level.

15. The method of claim 14, wherein the fifth frame comprises a management frame.

16. The method of any of claims 14-15, wherein the fifth frame comprises a beacon frame, an association response frame, or a probe response frame.

17. The method of any of claims 15-16, wherein the fifth frame comprises an indication that the STA is to ignore the local maximum transmit power level, and wherein the indication is provided in an information element (IE) of the fifth frame.

18. The method of any of claims 2-17, wherein the second frame comprises an indication that the first transmit power level is greater than the local maximum transmit power level.

19. The method of claim 18, wherein the indication is provided in an uplink power headroom (UPH) control field of the second frame.

20. The method of any of claims 2-19, further comprising transmitting, by the STA to the AP, a sixth frame using a second transmit power level, wherein the second transmit power level is based on the local maximum transmit power level.21 . The method of claim 20, wherein the second transmit power level comprises a transmit power level adapted to a path loss of an uplink channel between the STA and AP.

22. The method of claim 20, wherein the second transmit power level is equal to the local maximum transmit power level when a transmit power level adapted to a path loss of an uplink channel between the STA and AP exceeds the local maximum transmit power level.

23. A method comprising: transmitting, by an access point (AP) to a station (STA), a first frame indicating a local maximum transmit power level for use by the STA; receiving, by the AP from the AP, a second frame transmitted by the STA using a first transmit power level based on the local maximum transmit power level; transmitting, by the AP to the STA, a third frame instructing the STA to ignore the local maximum transmit power level for determining a second transmit power level for transmitting a fourth frame to the AP; andDocket No.: 24-3039PCT receiving, by the AP from the STA, the fourth frame transmitted by the STA using the second transmit power level, wherein based on the fourth frame having been transmitted by the STA in response to the third frame, the second transmit power level is greater than the local maximum transmit power level.

24. A method comprising: transmitting, by an access point (AP) to a station (STA), one or more first frames indicating: a local maximum transmit power level for use by the STA; and that the STA is to ignore the local maximum transmit power level for determining a first transmit power level for transmitting a second frame to the AP; and receiving, by the AP from the STA, the second frame transmitted by the STA using the first transmit power level.

25. The method of claim 24, wherein a third frame of the one or more first frames indicates the local maximum transmit power level.

26. The method of claim 25, wherein the third frame comprises a management frame.

27. The method of any of claims 25-26, wherein the third frame comprises a beacon frame, an association response frame, or a probe response frame.

28. The method of any of claims 25-27, wherein the local maximum transmit power level is provided in a transmit power envelope element of the third frame.

29. The method of any of claims 24-28, wherein based on the second frame being in response to a fourth frame, the first transmit power level is greater than the local maximum transmit power level.

30. The method of claim 29, wherein the fourth frame comprises a trigger frame.31 . The method of any of claims 24-30, wherein the STA transmitting the second frame comprises the STA transmitting the second frame using a trigger based physical layer protocol data unit (TB PPDU).

32. The method of any of claims 29-31 , wherein the one or more first frames comprises the fourth frame.

33. The method of any of claims 30-32, wherein the one or more first frames indicating that the STA is to ignore the local maximum transmit power level comprises the trigger frame indicating that the STA is to ignore the local maximum transmit power level.

34. The method of claim 33, wherein the trigger frame comprises an indication that the STA is to ignore the local maximum transmit power level, and wherein the indication is provided in a common info field of the trigger frame.

35. The method of claim 33, wherein the trigger frame comprises an indication that the STA is to ignore the local maximum transmit power level, and wherein the indication is provided in a user info field of the trigger frame, the user info field comprising an association identifier (AID) of the STA.Docket No.: 24-3039PCT36. The method of any of claims 24-32, wherein the one or more first frames indicating that the STA is to ignore the local maximum transmit power level comprises a fifth frame of the one or more first frames indicating that the STA is to ignore the local maximum transmit power level.

37. The method of claim 36, wherein the fifth frame comprises a management frame.

38. The method of any of claims 36-37, wherein the fifth frame comprises a beacon frame, an association response frame, or a probe response frame.

39. The method of any of claims 37-38, wherein the fifth frame comprises an indication that the STA is to ignore the local maximum transmit power level, and wherein the indication is provided in an information element (IE) of the fifth frame.

40. The method of any of claims 24-39, wherein the second frame comprises an indication that the first transmit power level is greater than the local maximum transmit power level.41 . The method of claim 40, wherein the indication is provided in an uplink power headroom (UPH) control field of the second frame.

42. The method of any of claims 24-41 , further comprising receiving, by the AP from the STA, a sixth frame transmitted by the STA using a second transmit power level, wherein the second transmit power level is based on the local maximum transmit power level.

43. The method of claim 42, wherein the second transmit power level comprises a transmit power level adapted to a path loss of an uplink channel between the STA and AP.

44. The method of claim 42, wherein the second transmit power level is equal to the local maximum transmit power level when a transmit power level adapted to a path loss of an uplink channel between the STA and AP exceeds the local maximum transmit power level.

45. A device comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the device to perform a method according to any of claims 1-44.

46. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method according to any of claims

Images