Triggered TXOP sharing with AC restrictions

Abstract

A wireless protocol is provided that allows an AP to allocate time within a transmission opportunity (TXOP) to non-AP stations. This allocation is made under the condition that the non-AP STA meets the Access Class (AC) requirements signaled in a frame such as an MU RTS TXS trigger frame transmitted by the AP STA. When the non-AP receives the frame, it responds whether it can meet the conditions such as in a Clear to Send (CTS) message. If the non-AP can meet the conditions, it transmits the data (to the AP or a peer non-AP). On the other hand, if the non-AP cannot meet the conditions, the AP can communicate the allocation to another non-AP STA. There are also conditions on how the non-AP aggregates data units into an A-MSDU.

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to and the benefit of U.S. Provisional Patent Application Serial No. 63 / 367,389, filed June 30, 2022, which is incorporated herein by reference in its entirety.

[0002] STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT N / A

[0003] Notification of copyrighted material Portions of the material in this patent document may be subject to copyright protection under the copyright laws of the United States and other countries. The copyright owner has no objection to the copying by any third party of the patent document or the patent disclosure as it appears in the U.S. Patent and Trademark Office public files or records, but otherwise reserves all copyright rights. The copyright owner does not hereby waive any of its rights to have this patent document maintained in secrecy, including, but not limited to, the right pursuant to 37 CFR §1.14.

[0004] The techniques of this disclosure relate generally to wireless network communications and sharing of transmission opportunities (TXOPs), and more specifically to triggered TXOP sharing while controlling transmissions by access category (AC) and aggregation of non-AP transmissions. [Background technology]

[0005] IEEE802.11be is the next-generation mainstream standard and is the successor to IEEE802.11ax / Wi-Fi6 currently available on the market. This standard was formed based on several candidate technologies, such as Multi-Link Operation (MLO) and Restricted Target Wake Time (R-TWT). MLO is a technology that enables the simultaneous use of multiple links (frequency bands). For example, the 5 GHz band and the 6 GHz band can be used simultaneously, and the throughput can be increased in proportion to the number of links. In the architectural structure of MLO, each link has a corresponding physical layer and a lower MAC layer that are bundled by a common upper MAC layer. In this structure, traffic handed over from the application layer can be directed to either link (TID-to-Link mapping). For example, this structure can reduce the latency caused by waiting for transmission by mapping traffic to a link that is available for transmission or a link with less congestion. R-TWT is a technology that enables the prioritized transmission of low-latency traffic through scheduling. R-TWT is based on a low-power feature called TWT (Target Wake Time) defined in the previous generation 11ax. In TWT, the communication period between the access point and the terminal is predetermined, the terminal enters a doze state during the remaining period, and when the period starts, the access point triggers the terminal to start communication. In R-TWT, the access point collects information about the traffic handled by the terminal and periodically allocates communication periods to prioritize terminals handling low-latency traffic.

[0006] The triggered TXOP sharing procedure is one of the candidate techniques for 802.11be / Wi-Fi7 (EHT) devices to access the channel, and can be applied during the R-TWT service period. The triggered TXOP sharing procedure allows an AP to allocate a portion of the acquired TXOP to one associated non-AP EHT STA for transmitting one or more non-TB PPDUs. The AP can send a MU-RTS TXS trigger frame to the associated non-AP EHT STA to indicate the allocation time. The intention of sharing TXOP is to help associated non-AP EHT STAs easily transmit Real-Time Application (RTA) traffic, which is time-critical and usually has high traffic priority, without contending for channel access rights. However, there is no rule that the shared TXOP should be allocated first to the priority traffic other than the low priority traffic from the associated non-AP EHT STA. Summary of the Invention [Problem to be solved by the invention]

[0007] Thus, there exists a need for an enhanced TXOP sharing protocol that overcomes this shortcoming. The present disclosure fulfills these needs and provides further advantages over existing systems. [Means for solving the problem]

[0008] A wireless communication protocol in which an Access Point (AP) station (STA) that gets a transmission opportunity (TXOP) can allocate time in the TXOP to one or more non-AP STAs that can meet the Access Class (AC) requirements set by the AP in the frame transmitted by the AP. When the non-AP station receives this frame, it sends back a response indicating whether it can meet the requested AC requirements. If the non-AP STA can meet the requested AC requirements, it accesses the network and transmits data that meets the requested AC requirements. If the response to the AP indicates that the non-AP cannot meet the conditions, the AP can try to allocate time to another non-AP STA. The protocol / device can also control the aggregation of data units into A-MSDUs.

[0009] Further aspects of the technology described herein will become apparent in the following portions of this specification, and this detailed description is intended to fully disclose preferred embodiments of the technology without limiting them.

[0010] The techniques described herein will be better understood with reference to the following drawings, which are for illustrative purposes only. [Brief description of the drawings]

[0011] [Figure 1] FIG. 2 is a block diagram of communication station hardware in accordance with at least one embodiment of the present disclosure. [Diagram 2] FIG. 1 is a block diagram of a multi-link device (MLD) hardware in accordance with at least one embodiment of the present disclosure. [Diagram 3] FIG. 13 is a data field diagram of the Required AC subfield and the Traffic Identifier (TID) Aggregation Restriction subfield that are added in both High Efficiency (HE) and Very High Throughput (EHT) variants of the User Information field, such as in the MU RTS TXS trigger frame, in accordance with at least one embodiment of the present disclosure. [Figure 4]FIG. 13 is a data field diagram of the Required AC subfield and the Traffic Identifier (TID) Aggregation Restriction subfield that are added in both High Efficiency (HE) and Very High Throughput (EHT) variants of the User Information field, such as in the MU RTS TXS trigger frame, in accordance with at least one embodiment of the present disclosure. [Diagram 5] FIG. 1 is a communication diagram using a MU RTS TXS trigger frame with a TXOP shared mode subfield in accordance with at least one embodiment of the present disclosure. [Figure 6] 1 is a communication diagram using a MU RTS TXS trigger frame with a TXOP shared mode subfield including a non-AP transmission to a peer non-AP STA, in accordance with at least one embodiment of the present disclosure. [Figure 7] 1 is a communication diagram using a MU RTS TXS trigger frame with a TXOP shared mode subfield in which a non-AP STA transmits one or more non-trigger based (non-TB) data units within a time allocation, in accordance with at least one embodiment of the present disclosure. [Figure 8] FIG. 13 is a communication diagram using a MU RTS TXS trigger frame with a TXOP shared mode subfield in which a non-AP STA transmits one or more non-trigger-based (non-TB) data units within a time allocation after first responding to the AP with a clear to send (CTS), in accordance with at least one embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] 1. Problem Statement The Triggered TXOP Sharing procedure described in Section 35.2.1.2 of the draft specification P802.11be_D2.0 states that "The Triggered TXOP Sharing procedure enables an AP to allocate a portion of the time within an acquired TXOP to associated non-AP EHT STAs for the transmission of one or more non-TB PPDUs."

[0013] However, this specification does not state which associated non-AP STAs the AP should select to share a portion of the acquired TXOP time, and therefore the AP lacks control over the transmission and cannot fully control the Quality of Service (QoS) instance in one or more Access Classes (ACs) of data waiting in Enhanced Distributed Channel Access (EDCA).

[0014] Therefore, the current specification does not allow for TXOP sharing, which is intended to help non-AP STAs with high priority AC traffic (e.g., time-sensitive traffic) transmit using a shared TXOP. Under these conditions, it is not reasonable for the AP to transmit a MU RTS TXS frame to a non-AP STA that does not have buffered data units that meet the AC limit.

[0015] Note that this MU-RTS TXS trigger frame is used by the EHT AP to allocate time in the acquired TXOP to associated non-AP EHT STAs and share this allocated time with the non-AP EHT STAs.

[0016] 2. Contribution of this Disclosure In the current provisional specification P802.11be_D2.0, the MU RTS TXS trigger frame only indicates the allocated time in the acquired TXOP for the associated non-AP STAs, and no AC restrictions are specified on how the associated non-AP STAs may use the allocated time.

[0017] The present disclosure provides the following mechanisms to address the above shortcomings.

[0018] In addition to allocating time in the acquired TXOP to associated non-AP STAs, the AP may also indicate Access Class (AC) restrictions on how scheduled non-AP EHT STAs should use the allocated channel time. In at least one embodiment, this AC restriction information is carried by the MU RTS TXS trigger frame, but may also be carried through other types of communication frames without departing from the teachings of this disclosure.

[0019] A non-AP STA that receives an MU RTS TXS trigger frame addressed to it should not use a shared TXOP if it does not have data units to transmit that meet the AC limit. Thus, the AP can schedule other STAs that may have buffered units with AC equal to or higher than this AC limit within the allocated time of the acquired TXOP.

[0020] 3. Embodiments of the present disclosure 3.1. Communication Station (STA and MLD) Hardware FIG. 1 illustrates an example embodiment 10 of STA hardware configured to execute the protocol of the present disclosure. An external I / O connection 14 couples to an internal bus 16 of the circuitry 12 on which a CPU 18 and memory (e.g., RAM) 20 are preferably connected for executing a program(s) implementing the communication protocol. The host machine contains at least one modem 22 supporting communications coupled to at least one RF module 24, 28 each coupled to one or more antennas 29, 26a, 26b, 26c-26n. RF modules with multiple antennas (e.g., antenna arrays) allow for beamforming to be performed during transmission and reception. In this manner, the STA can transmit signals using multiple sets of beam patterns.

[0021] The bus 14 can connect various devices such as sensors and actuators to the CPU. On the processor 18, instructions are executed from the memory 20 to execute a program implementing a communication protocol that is executed to enable the STA to perform the functions of an Access Point (AP) station or a normal station (non-AP STA). It is also understood that this programming is configured to operate in different modes (TXOP owner, TXOP sharing participant, source, intermediate, destination, first AP, other AP, station associated with first AP, station associated with other AP, coordinator, coordinatee, AP in OBSS, STA in OBSS, etc.) depending on what role it plays in the current communication situation.

[0022] Thus, the illustrated STA HW is comprised of at least one modem and associated RF circuitry for providing communication on at least one band. It should be understood that the present disclosure may be configured using multiple modems 22, each coupled to any number of RF circuits. In general, the more RF circuits used, the greater the coverage of the antenna beam directions. It should be understood that the number of RF circuits and antennas utilized is determined by the hardware constraints of a particular device. Some of the RF circuits and antennas may be disabled when a STA determines that it does not need to communicate with neighboring STAs. In at least one embodiment, the RF circuitry includes a frequency converter and an array antenna controller, etc., and is connected to multiple antennas that are controlled to perform beamforming for transmission and reception. In this manner, a STA may transmit signals using a set of multiple beam patterns, with each beam pattern direction considered an antenna sector.

[0023] It should also be understood that multiple instances of station hardware such as that shown in this figure may be combined into a multi-link device (MLD), which typically has a processor and memory for coordinating activity, but does not necessarily require a separate CPU and memory for each STA within the MLD; these resources may be shared.

[0024] FIG. 2 shows an embodiment 40 of a multi-link device (MLD) hardware configuration. Note that a "soft AP MLD" is an MLD consisting of one or more affiliated STAs operating as an AP. The soft AP MLD should support multiple radio operation on, for example, 2.4 GHz, 5 GHz, and 6 GHz. The basic link set among the multiple radios is a link pair that satisfies simultaneous transmit / receive (STR) mode, such as basic link set (2.4 GHz and 5 GHz), basic link set (2.4 GHz and 6 GHz), etc.

[0025] A conditional link is a link that forms a non-simultaneous transmit / receive (NSTR) link pair with some fundamental link. For example, these link pairs can include a 6 GHz link as a conditional link corresponding to the 5 GHz link when the 5 GHz is the fundamental link, and can include a 5 GHz link as a conditional link corresponding to the 6 GHz link when the 6 GHz is the fundamental link. Soft APs are used in different scenarios including Wi-Fi hotspots and tethering.

[0026] A MLD has multiple STAs, each operating on a different frequency link. The MLD has external I / O access to applications, which connects to an MLD management entity 48 having a CPU 62 and memory (e.g., RAM) 64 to allow the execution of program(s) that implement the communication protocol at the MLD level. The MLD can distribute tasks to its associated stations, illustrated here as STA1 42, STA2 44 through STA N 46, to collect information from them and share the information among its associated STAs.

[0027] In at least one embodiment, each STA in the MLD has its own CPU 50 and memory (RAM) 52, which are coupled over a bus 58 to at least one modem 54 connected to at least one RF circuit 56 having one or more antennas. In this example, the RF circuit has multiple antennas 60a, 60b, 60c-60n, such as in the form of an antenna array. The modem in combination with the RF circuit and associated antenna(s) transmits / receives data frames to / from nearby STAs. In at least one implementation, the RF module includes a frequency converter, an array antenna controller, and other circuitry for interfacing with the antennas.

[0028] It should be understood that each STA in an MLD does not necessarily require its own processor and memory, as they may share resources with each other and / or with an MLD management entity depending on the particular MLD implementation. It should be understood that the above MLD diagram is provided by way of example and not limitation, and that the present disclosure can work with a wide variety of MLD implementations.

[0029] 4.MU RTS TXS trigger frame format Example embodiments 70, 90 of the Multiple-User (MU) Ready-To-Send (RTS) Transmission (TXS) trigger frame format are shown in Figures 3 and 4. As shown in these figures, the High Efficiency (HE) and Extra-High Throughput (EHT) variants of the User Information field in the MU RTS TXS trigger frame have the Requested AC and TID Aggregation Limit subfields added.

[0030] The requested AC subfield indicates a requested AC Index (ACI) that must be met before a non-AP STA can access the allocated time in the portion of the TXOP obtained by the AP.

[0031] The TID Aggregation Limit subfield indicates the maximum number of MAC Protocol Data Units (MPDUs) allowed in an Aggregated-MPDU (A-MPDU) carried in an EHT or HE PLCP Protocol Data Unit (PPDU) and the maximum number of Traffic Identifiers (TIDs) that a STA can aggregate in an A-MPDU.

[0032] A non-AP EHT / HE STA transmitting multiple TID A-MPDUs within the allocated time should aggregate data frames in the following order: (i) first transmit any and all MPDUs corresponding to the requested AC subfield of the User Information field of the MU RTS TXS trigger frame addressed to the STA, (ii) then transmit any and all MPDUs corresponding to any AC with a higher priority than the requested AC, and (iii) note that the STA should not aggregate MPDUs corresponding to ACs with a lower priority than the requested AC.

[0033] A non-AP EHT / HE STA transmitting a single TID A-MPDU in an EHT / HE PPDU within the allocated time should aggregate data units in the following order: (i) the TID corresponding to the requested AC subfield of the User Information field of the MU RTS TXS trigger frame addressed to the STA, (ii) otherwise, the TID corresponding to any AC with a higher priority than the requested AC, (iii) the STA should not aggregate MPDUs corresponding to ACs with a lower priority than the requested AC.

[0034] As an alternative to the above, the Trigger Dependent User Info subfield in the User Information field of the MU RTS TXS trigger frame can be enabled. The Trigger Dependent User Info subfield should include the required AC subfields described above and the TID aggregation restriction subfield.

[0035] Note that in the current specification, there is no trigger-dependent user information subfield in the MU-RTS trigger frame.

[0036] The Triggered TXOP Sharing Mode subfield in the Common Info field is set to a first state (e.g., “1”) when the EHT AP transmits an MU-RTS trigger frame intending to allocate time in an acquired TXOP to associated non-AP EHT STAs to transmit one or more non-TB PPDUs addressed sequentially to the associated AP only, the Triggered TXOP Sharing Mode subfield in the Common Info field is set to a second state (e.g., “2”) when the EHT AP transmits an MU-RTS trigger frame intending to allocate time in an acquired TXOP to associated non-AP EHT STAs to transmit one or more non-TB PPDUs addressed sequentially to the associated AP or addressed to another STA, and the Triggered TXOP Sharing Mode subfield in the Common Info field is set to a fourth state (e.g., “0”).

[0037] 5. Example of operation 5.1. Example 1 5 illustrates an example embodiment 110 using a MU RTS TXS trigger frame with a TXOP sharing mode subfield. This example illustrates the interaction between the AP 112 and non-AP STAs 114, particularly with regard to sharing of the TXOP 118, specifically the time allocation 122 given to a particular AC in the MU RTS TXS trigger frame.

[0038] By way of example and not limitation, the TXOP Sharing Mode subfield value is equal to a first state (e.g., “1”), meaning (indicating) that the MU-RTS has initiated the MU-RTS TXOP Sharing procedure and the scheduled STA may only transmit MPDU(s) addressed to its associated AP, and the Requested AC subfield value is equal to a third state (e.g., “3”) when requesting a UL PPDU for AC3.

[0039] It can be seen that the AP has performed a Clear to Send (CTS) 116 to itself to reserve the channel. The EHT AP can allocate time in the acquired TXOP to the non-AP STA1 to request a UL PPDU of a certain AC level, such as AC3 or higher, by sending a MU RTS TXS trigger frame 120 to the non-AP STA1.

[0040] After receiving the MU RTS TXS trigger frame 120 addressed to it, the non-AP STA1 sends a CTS 124 to the AP. The non-AP STA1 can then transmit one or more non-trigger-based (non-TB) Physical Layer Protocol Data Units (PPDUs) that satisfy the requested AC (i.e., AC3) within the time allocation signaled in the MU RTS TXS trigger frame, illustrated as 126 and 130. The AP acknowledges receipt of these PPDUs. The non-AP STA1 has buffered data units with ACs equal to or higher than the requested AC so that it can satisfy the requested AC.

[0041] The EHT AP receives the CTS from the non-AP STA1 and therefore recognizes the successful transmission of the MU RTS TXS trigger frame 120. The AP may also transmit a Block Ack 128 to the non-AP STA1 as an immediate response to receiving the UL DATA 126 within the allotted time specified in the MU RTS TXS trigger frame.

[0042] The non-AP STA1 can then continue to transmit one or more non-TB PPDUs 130 that satisfy the requested AC (i.e., AC3) within the allocated time signaled in the MU RTS TXS trigger frame, and the non-AP should receive a Block Ack 132 in response from the AP.

[0043] After the AP sends Block Ack 132 to the non-AP STA1, the CS mechanism indicates that the medium is idle at the TxPIFS 134 slot boundary as indicated by the PIFS, so that the EHT AP can send another PPDU 136 in the acquired TXOP.

[0044] 5.2. Example 2 6 illustrates an example embodiment 210 using a MU RTS TXS trigger frame with a TXOP sharing mode subfield. This example illustrates communication between an AP 212, non-AP STA1 214, and non-AP STA2 216 regarding the sharing of a TXOP 220, specifically the time 224 allocated to a particular AC in the MU RTS TXS trigger frame.

[0045] After the EHT AP executes CTS 218 to itself to reserve the TXOP, it starts allocating time in the TXOP 220 to non-AP STA1 to request UL PPDUs at or above a certain AC level, exemplified here as AC3, by sending an MU RTS TXS trigger frame 222.

[0046] After receiving the MU RTS TXS trigger frame 222 addressed to it, non-AP STA1 first responds with a CTS 226 to the AP during allocation period 224. Because non-AP STA1 does not have any buffered units with an AC equal to or higher than the requested AC, it does not transmit a non-TB PPDU within the time allocation signaled in the MU RTS TXS trigger frame.

[0047] The EHT AP receives the CTS from non-AP STA1 and determines that the transmission of the MU RTS TXS trigger frame was successful. However, after receiving the CTS from non-AP STA1, the CS mechanism indicates that the medium is idle at the boundary of the TxPIFS slot as indicated by PIFS 227. The EHT AP can then allocate time in the acquired TXOP to non-AP STA2 to request a UL PPDU at or above a certain AC level, exemplified here as AC3, by transmitting a MU RTS TXS trigger frame 228 to non-AP STA2.

[0048] When non-AP STA2 receives the MU RTS TXS trigger frame 228 addressed to it, it first responds to the AP with a CTS 230. The non-AP STA2 can then transmit one or more non-TB PPDUs 232 that satisfy the requested AC (i.e., AC3) within the time allocation signaled in the MU RTS TXS trigger frame.

[0049] The AP may transmit a Block Ack 234 to the non-AP STA 2 as an immediate response to receiving the UL DATA within the allotted time specified in the MU RTS TXS trigger frame.

[0050] After the AP sends an Ack 234 to the blocking non-AP STA2, the CS mechanism indicates that the medium is idle at the TxPIFS slot boundary as indicated by the PIF 236. This allows the EHT AP to send another PPDU 238 in the acquired TXOP.

[0051] 5.3. Example 3 7 illustrates an example embodiment 310 of a MU RTS TXS trigger frame with a TXOP sharing mode subfield. Again, this figure illustrates communication between an AP 312, non-AP STA1 314, and non-AP STA2 316 regarding the sharing of a TXOP 320, specifically the time 324 allocated to a particular AC in the MU RTS TXS trigger frame.

[0052] In this example, a MU RTS TXS trigger frame with a TXOP sharing mode subfield value equal to 2 and an AC subfield required equal to 3 schedules STA1.

[0053] After obtaining a TXOP 320 with a CTS 318 for itself, the EHT AP allocates time 324 in this TXOP to the non-AP STA1 to request a UL PPDU of AC3 or to allow the transmission of a PPDU of AC3 to another non-AP STA2 by sending an MU RTS TXS trigger frame 322 to the non-AP STA1.

[0054] After receiving the MU RTS TXS trigger frame 322 addressed to it, non-AP STA1 first responds to the AP with a CTS 326. Non-AP STA1 can then transmit one or more non-TB PPDUs 328 satisfying the requested AC, exemplified as AC3, within the time allocation signaled in the MU RTS TXS trigger frame.

[0055] The EHT AP receives a CTS 326 from the non-AP STA1 indicating successful transmission of the MU RTS TXS trigger frame, and can transmit a Block Ack 330 to the non-AP STA1 as an immediate response to receiving the UL DATA within the allocated time 324 specified in the MU RTS TXS trigger frame.

[0056] When the TXOP sharing mode subfield value is set to a second state (e.g., “2”) to indicate that an MU-RTS TXOP sharing procedure is initiated by the MU-RTS in which the scheduled STA can transmit MPDU(s) addressed to its associated AP or another STA, the non-AP EHT STA1 can transmit one or more non-TB PPDUs 332 that satisfy the requested AC value (AC3) to another non-AP STA2 during the time allocated by the EHT AP.

[0057] Non-AP STA2 receives DATA 332 from non-AP STA1 and should respond with block Ack 334 .

[0058] After the non-AP STA2 transmits the Block Ack frame, the CS mechanism indicates that the medium is idle at the TxPIFS slot boundary as indicated by PIFS 336. This allows the EHT AP to transmit another PPDU 338 in the acquired TXOP.

[0059] 5.4. Example 4 8 illustrates an example embodiment 410 of a MU RTS TXS trigger frame with a TXOP sharing mode subfield. Again, this figure illustrates communication between an AP 412, non-AP STA1 414, and non-AP STA2 416 regarding the sharing of a TXOP 420, specifically the time allocation 424 directed to a particular AC as indicated in the MU RTS TXS trigger frame.

[0060] By way of example and not limitation, an MU RTS TXS trigger frame illustrated with a TXOP sharing mode subfield value equal to 2 and a required AC subfield value equal to 3 schedules STA1 and STA2.

[0061] After first acquiring the channel with a CTS 418 for itself, the EHT AP allocates time 424 in the TXOP 420 to non-AP STA1 414 to request a UL PPDU of AC3 or to allow it to transmit a PPDU of AC3 to another non-AP STA2 by sending a MU RTS TXS trigger frame 422 to non-AP STA1.

[0062] After receiving the MU RTS TXS trigger frame addressed to it, non-AP STA1 first responds to the AP with a CTS 426. Then, non-AP STA1 can transmit one or more non-TB PPDUs 428 to the AP that satisfy the requested AC, exemplified as AC3, within the time allocation signaled in the MU RTS TXS trigger frame.

[0063] The EHT AP receives the CTS and data unit from the non-AP STA1 and determines that the transmission of the MU RTS TXS trigger frame is successful. The AP can transmit a Block Ack 430 to the non-AP STA1 as an immediate response to the reception of the UL DATA 428 within the allocated time specified in the MU RTS TXS trigger frame.

[0064] If the TXOP sharing mode subfield value is 2, the non-AP EHT STA1 indicates to another non-AP STA2 that it does not have any more non-TB PPDUs that meet the required AC value (AC3) during the time allocated by the EHT AP 424. As a result, the non-AP EHT STA1 does not transmit a PPDU after receiving a Block Ack from the EHT AP.

[0065] After sending the Block Ack to the non-AP STA1, the CS mechanism indicates that the medium is idle at the boundary of a TxPIFS slot, shown as PIFS 432. The EHT AP can then allocate time in the TXOP to the non-AP STA2 to request a UL PPDU of AC3 or to allow it to transmit a PPDU of AC3 to another non-AP STA1 by sending an MU RTS TXS trigger frame 434 to the non-AP STA2.

[0066] After receiving the MU RTS TXS trigger frame addressed to itself, the non-AP STA2 first responds with a CTS 436. At this time, if the buffered units to the AP cannot satisfy the requested AC (i.e., AC3) within the time allocation signaled in the MU RTS TXS trigger frame, the non-AP STA2 does not transmit a non-TB PPDU to the EHT AP. The non-AP STA2 can transmit one or more non-TB PPDUs 438 that satisfy the requested AC (i.e., AC3) to another non-AP STA1 within the time allocation signaled in the MU RTS TXS trigger frame.

[0067] Non-AP STA1 receives data unit 438 from non-AP STA2 and should respond with block Ack 440 to non-AP STA2.

[0068] After the non-AP STA1 transmits the Block Ack frame, the CS mechanism indicates that the medium is idle at the TxPIFS slot boundary as indicated by PIFS 442. As a result, the EHT AP can transmit another PPDU 444 in the acquired TXOP.

[0069] 6. General Scope of the Embodiments Embodiments of the present technology may be described herein with reference to flowcharts of methods and systems according to embodiments of the present technology, and / or procedures, algorithms, steps, operations, formulas, or other computational expressions, which may also be implemented as computer program products. In this regard, each block or step of the flowchart, and combinations of blocks (and / or steps) of the flowchart, and any procedures, algorithms, steps, operations, formulas, or computational expressions, may be implemented by various means, such as hardware, firmware, and / or software that includes one or more computer program instructions embodied in a computer readable program code. As will be appreciated, any such computer program instructions may be executed by one or more computer processors, including, but not limited to, a general purpose computer or a special purpose computer, or any other programmable processing device to produce a machine, such that the computer program instructions executing on the computer processor or other programmable processing device produce means for performing the specified function(s).

[0070] Thus, the blocks of the flowcharts and procedures, algorithms, steps, operations, formulas, or computational expressions described herein support combinations of means for performing a particular function(s), combinations of steps for performing a particular function(s), and computer program instructions for performing a particular function(s) as embodied in computer readable program code logic means. It will also be understood that each block of the flowcharts described herein and any procedures, algorithms, steps, operations, formulas, or computational expressions, and combinations thereof, can also be implemented by a dedicated hardware-based computer system that performs the particular function(s) or step(s), or a combination of dedicated hardware and computer readable program code.

[0071] Moreover, these computer program instructions, embodied in computer readable program code or the like, may be stored in one or more computer readable memories or memory devices capable of directing a computer processor or other programmable processing device to function in a particular manner, such that the instructions stored in these computer readable memories or memory devices produce an article of manufacture including instruction means for performing the functions specified in the flowchart(s). The computer program instructions may be executed by the computer processor or other programmable processing device to generate a computer-implemented process by causing a series of operational steps to be performed on the computer processor or other programmable processing device, such that the instructions executing on the computer processor or other programmable processing device provide steps for performing the function specified in the flowchart(s) block(s), procedure(s), algorithm(s), step(s), operation(s), mathematical formula(s), or computational expression(s).

[0072] Additionally, the terms "program" or "program executable" as used herein will be understood to mean one or more instructions executable by one or more computer processors to perform one or more functions described herein. The instructions may be embodied in software, firmware, or a combination of software and firmware. The instructions may be stored locally on a non-transitory medium of the device or remotely, such as on a server, or all or a portion of the instructions may be stored locally or remotely. Remotely stored instructions may be downloaded (pushed) to the device upon user initiation or automatically based on one or more factors.

[0073] Furthermore, as used herein, the terms processor, hardware processor, computer processor, central processing unit (CPU), and computer are used synonymously to indicate a device capable of executing instructions and communicating with input / output interfaces and / or peripheral devices, and it will be understood that the terms processor, hardware processor, computer processor, CPU, and computer are intended to include single or multiple devices, single-core devices and multi-core devices, and variations thereof.

[0074] From the description herein, it will be understood that the present disclosure encompasses multiple technology implementations, including but not limited to the following.

[0075] An apparatus for wireless communication in a network, comprising: (a) a wireless communication station (STA) operating as either a normal STA or an access point (AP) STA that performs transmission of frames over a channel between a medium access control (MAC) layer of an IEEE 802.11 network as an independent communication station (STA) or as an STA in a multilink device (MLD) and wirelessly communicates with other wireless STAs using a carrier sense multiple access with collision avoidance (CSMA / CA) mechanism on a wireless local area network (WLAN) in which enhanced distributed channel access (EDCA) is utilized for random channel access on all links; (b) a processor coupled to wireless communication circuitry and operating on the WLAN; and (c) a non-transitory memory storing instructions executable by the processor for communicating with other STAs, wherein (d) the instructions, when executed by the processor, are configured to: (i) transmit a transmission opportunity (TXOP) by the STA operating as an AP STA; and (ii) receive an access class (AC) from one or more non-AP STAs in response to the STA obtaining an access class (AC) requirement; (d)(iii) the AP STA transmitting a frame indicating requested AC requirements that one of the one or more non-AP STAs must meet in order to utilize the allocated time in the TXOP; and (d)(iv) receiving a response from one of the one or more non-AP STAs that received the frame indicating the requested AC requirements transmitted by the AP STA, (d)(v) the response received by the AP STA indicates whether the non-AP STA meets the requested AC requirements, and (d)(vi) if the non-AP STA meets the requested AC requirements, the non-AP STA proceeds to access the network and transmit data having the requested AC requirements.

[0076] An apparatus for wireless communication in a network, comprising: (a) a wireless communication station (STA) operating as either a normal STA or an access point (AP) STA that performs transmission of frames between a medium access control (MAC) layer of an IEEE 802.11 network as an independent communication station (STA) or as an STA in a multilink device (MLD) and wirelessly communicates with other wireless STAs using a carrier sense multiple access with collision avoidance (CSMA / CA) mechanism on a wireless local area network (WLAN) in which enhanced distributed channel access (EDCA) is utilized for random channel access on all links; (b) a processor coupled to wireless communication circuitry and operating on the WLAN; and (c) a non-transitory memory storing instructions executable by the processor for communicating with other STAs, wherein (d) the instructions, when executed by the processor, are configured to: (i) transmit a transmission opportunity (TXOP) by the STA operating as an AP STA; and (ii) receive an access class (AC) from one or more non-AP STAs in response to the STA obtaining an access class (AC) requirement; (d)(iii) the AP STA transmitting a frame indicating requested AC requirements that one of the one or more non-AP STAs must meet in order to utilize the allocated time in the TXOP; and (d)(iv) receiving a response from one of the one or more non-AP STAs that received the frame indicating requested AC requirements transmitted by the AP STA; (d)(v) the response received by the AP STA indicating whether the non-AP STA meets the requested AC requirements; (d)(vi) if the non-AP STA meets the requested AC requirements, the non-AP STA proceeds to access the network and transmit data having the requested AC requirements; and (d)(vii) the frame transmitted by the AP STA indicating requested AC requirements is in accordance with (A) IEEE 802.11 standard, (d)(viii) the response received by the AP STA from one or more non-AP STAs receiving the frame indicating the requested AC requirements includes a clear to send (CTS) frame indicating whether the requested AC requirements can be met by the non-AP STA, and (d)(ix) if the requested AC requirements are not met by the non-AP STA, the AP STA communicates the frame indicating the requested AC requirements to a different non-AP STA to provide it with allocated time in the TXOP if it can meet the requested AC requirements.

[0077] 1. A method for performing wireless communication in a network, comprising: (a) transmitting frames between a medium access control (MAC) layer of an IEEE 802.11 network having independent communication stations (STAs) and / or STAs in a multilink device (MLD) and performing communication on the wireless network having a station (STA) operating as either a normal STA or an access point (AP) STA that wirelessly communicates with other wireless STAs using a carrier sense multiple access with collision avoidance (CSMA / CA) mechanism on a wireless local area network (WLAN) in which enhanced distributed channel access (EDCA) is utilized for random channel access on all links; (b) a STA operating as an AP STA obtaining a transmission opportunity (TXOP); (c) in response to satisfying an access class (AC) requirement, the AP STA allocating time in the TXOP to one or more non-AP STAs; (d) the AP STA transmitting a frame indicating a required AC requirement that must be satisfied in order for one of the one or more non-AP STAs to utilize the allocated time in the TXOP; and (e) the AP STA transmitting a frame indicating a required AC requirement that must be satisfied in order for one of the one or more non-AP STAs to utilize the allocated time in the TXOP. (f) receiving a response from one of one or more non-AP STAs that received the frame transmitted by the STA indicating the requested AC requirements; (g) the response received by the AP STA indicates whether the non-AP STA meets the requested AC requirements; and (g) if the non-AP STA meets the requested AC requirements, the non-AP STA proceeds to access the network and transmit data having the requested AC requirements.

[0078] The apparatus or method of any preceding implementation, wherein the frame transmitted by the AP STA indicating the required AC requirements includes a trigger frame that can be configured to meet High Efficiency (HT) and / or Very High Throughput (EHT) according to the IEEE 802.11 standard.

[0079] The apparatus or method of any preceding implementation, wherein the frame transmitted by the AP STA indicating the requested AC requirements comprises a multi-user (MU) request to send (RTS) TXOP shared (TXS) trigger frame.

[0080] The apparatus or method of any preceding implementation, wherein the response from one or more non-AP STAs to the frame received by the AP STA indicating the requested AC requirements includes a clear to send (CTS) frame indicating whether the requested AC requirements are met by the non-AP STAs.

[0081] An apparatus or method of any preceding implementation, wherein if the requested AC requirements are not met by the non-AP STA, the AP STA communicates a frame indicating the requested AC requirements to a different non-AP STA and provides the allocated time in the TXOP if the requested AC requirements can be met.

[0082] The apparatus or method of any preceding implementation, wherein the data transmitted by a non-AP STA includes data uploaded to an AP STA or data transmitted to another non-AP STA.

[0083] The apparatus or method of any preceding implementation, wherein a waiting data packet of the non-AP STA is deemed to satisfy the AC requirement if one or more data packets in an EDCA queue have an AC value equal to or higher than the requested AC requirement transmitted by the AP STA.

[0084] The apparatus or method of any preceding implementation, wherein waiting data packets of the non-AP STA are deemed to not meet the AC requirement if these data packets in the EDCA queue have an AC value lower than the requested AC requirement transmitted by the AP STA.

[0085] An apparatus or method of any preceding implementation, wherein if in a frame indicating required AC requirements, the TXOP sharing mode subfield value is indicated to be equal to a value indicating that sharing of the TXOP by the AP STA is not permitted, sharing of the TXOP by the AP STA is prevented.

[0086] An apparatus or method of any preceding implementation, wherein a non-AP STA accesses a channel during a shared TXOP and transmits an MPDU to an associated AP that satisfies the requested AC requirements indicated in a frame indicating the requested AC requirements only if the TXOP shared mode subfield value is equal to a first state, and transmits to an associated AP or another STA if the TXOP shared mode subfield value is equal to a second state.

[0087] The apparatus or method of any preceding implementation, further comprising: conveying a multiple transmission identification (TID) aggregation-MAC protocol data unit (A-MPDU) limit subfield in a frame transmitted by an AP STA indicating the requested AC requirements, the TID A-MPDU limit subfield indicating the number of MPDUs allowed in an A-MPDU and the maximum number of TIDs that a non-AP STA can aggregate in an A-MPDU.

[0088] An apparatus or method of any preceding implementation, in which a non-AP STA transmitting multiple TID A-MPDUs within an allocated time indicated by a frame including an indicated requested AC value should aggregate data units in the following order: (i) first, any and all MPDUs corresponding to the requested AC subfield of the user information field of the frame addressed to the non-AP STA including the requested AC value, (ii) then any and all MPDUs corresponding to any AC having a higher priority than the requested AC, and (iii) the non-AP STA does not aggregate MPDUs corresponding to an AC having a lower priority than the requested AC.

[0089] An apparatus or method of any preceding implementation, wherein a non-AP STA transmitting a single TID A-MPDU within the allocated time indicated by a frame including the requested AC value aggregates data frames in the following order: (i) aggregating TIDs corresponding to the requested AC subfields addressed to the non-AP STA; and (ii) if condition (i) cannot be satisfied, aggregating data frames having TIDs corresponding to any AC having a higher priority than the requested AC; and (iii) the non-AP STA does not aggregate MPDUs corresponding to ACs having a lower priority than the requested AC.

[0090] The apparatus or method of any preceding implementation, wherein the required AC subfield and the TID aggregation restriction subfield are carried in a trigger-dependent user information subfield that is not present in a user information field of a trigger frame.

[0091] The term "implementation" as used herein is intended to include, without limitation, embodiments, examples, or other forms for practicing the techniques described herein.

[0092] As used herein, the singular forms "a," "an," and "the" include plural referents unless the context clearly indicates otherwise. Reference to an object in the singular does not mean "the only one" unless expressly stated otherwise, but rather means "one or more."

[0093] In this disclosure, constructs such as "A, B and / or C" indicate that either A, B or C, or any combination of items A, B and C, may be present. Constructs such as "at least one of" followed by a group of listed elements indicate that at least one of those group elements is present, including possible combinations of any of those listed elements, where applicable.

[0094] References in this disclosure to "an embodiment," "at least one embodiment," or similar embodiment language indicate that a particular feature, structure, or characteristic described in connection with the described embodiment is included in at least one embodiment of the disclosure. Thus, these references to various embodiments do not necessarily refer to all the same embodiment, or to a specific embodiment that is different from all other embodiments described. References to embodiments should be interpreted to mean that the particular features, structures, or characteristics of a given embodiment can be combined in any suitable manner in one or more embodiments of the disclosed devices, systems, or methods.

[0095] As used herein, the term "set" refers to a collection of one or more objects. Thus, for example, a set of objects can include a single object or multiple objects.

[0096] Relative terms such as first and second, top and bottom, upper and lower, and left and right in this document are used merely to distinguish one entity or action from another entity or action, and do not necessarily require or imply any such actual relationship or ordering between such entities or actions.

[0097] The terms "comprises, comprising, has, having, includes, including, contains, containing," or any other variations of these terms, are intended to cover non-exclusive inclusions, such that a process, method, article, or apparatus that comprises, has, or includes a list of elements does not include only those elements, but may also include other elements not expressly listed or that are inherent to such process, method, article, or apparatus. An element following "comprises ... a, has ... a, includes ... a, contains ... a" does not exclude, without further constraints, the presence of additional identical elements in the process, method, article, or apparatus that comprises, has, or includes that element.

[0098] As used herein, the terms "approximately", "approximate", "substantially", "essentially" and "about", or any variation thereof, are used to describe and explain slight variations. When used in relation to events or circumstances, these terms can mean that the events or circumstances will definitely occur and that the events or circumstances are highly likely to occur. When used in relation to a numerical value, these terms can mean a variation range of ±10% or less, such as ±5% or less, ±4% or less, ±3% or less, ±2% or less, ±1% or less, ±0.5% or less, ±0.1% or less, or ±0.05% or less of the numerical value. For example, being "substantially" aligned can mean an angle variation range of ±10° or less, such as ±5° or less, ±4° or less, ±3° or less, ±2° or less, ±1° or less, ±0.5° or less, ±0.1° or less, or ±0.05° or less.

[0099] In addition, amounts, ratios, and other numerical values ​​may be expressed in range format in this specification. Such range formats are used for convenience and simplification, and include numerical values ​​explicitly specified as the limits of the range, but should be understood to include all individual numerical values ​​or subranges within the range as if each of these numerical values ​​and subranges were explicitly stated. For example, a ratio within the range of about 1 to about 200 should be understood to include the explicitly recited limits of about 1 and about 200, but also include individual ratios such as about 2, about 3, about 4, and subranges such as about 10 to about 50, about 20 to about 100, etc.

[0100] The term "coupled," as used herein, is defined as connected, but not necessarily in a direct mechanical connection. A device or structure that is "configured" in a particular way is configured in at least that way, but may also be configured in other ways not listed.

[0101] Benefits, advantages, solutions to problems, and any element(s) that cause or make any advantage, advantage, or solution more pronounced are not to be construed as critical, necessary, or essential features or elements of the technology described herein, or of any or all of the claims.

[0102] Also, in the foregoing disclosure, various features may be grouped together in various embodiments for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Inventive subject matter may be embodied in less than all features of a single disclosed embodiment.

[0103] The Abstract of the Disclosure is presented to allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims.

[0104] It is understood that some jurisdictions have a practice of requiring the deletion of one or more portions of the present disclosure after filing. Thus, the reader should refer to the application as of its filing date for the original content of the present disclosure. The deletion of any of the disclosed content should not be construed as an abandonment, forfeiture, or dedication to the public of any subject matter of the application as originally filed.

[0105] The following claims are hereby incorporated into this disclosure, with each claim standing on its own as a separate inventive subject matter.

[0106] Although the description herein contains many details, these should not be construed as limiting the scope of the disclosure, but merely as exemplifying some of the presently preferred embodiments, and therefore the scope of the disclosure will be understood to fully embrace other embodiments that may become apparent to those skilled in the art.

[0107] Structural and functional equivalents of elements of the embodiments of the present disclosure known to those skilled in the art are also expressly incorporated herein by reference and are intended to be included in the scope of the claims. Moreover, no element, component, or method step of the present disclosure is intended to be publicly disclosed, regardless of whether they are explicitly recited in the claims. No claim element herein should be construed as a "means-plus-function" element unless the element is explicitly recited using the phrase "means for". No claim element herein should be construed as a "step-plus-function" element unless the element is explicitly recited using the phrase "step for". [Explanation of symbols]

[0108] 110 Embodiments 112 AP 114 Non-AP STA1 116 CTS to own aircraft 118 TXOP 120 MU RTS TXS trigger frame to STA1 (TXOP sharing mode = 1, AC requested = 3) 122 MU RTS Time allocated for a specific AC in a TXS trigger frame 124 CTS response to AP 126 Data to AP in non-TB PPDU (AC3) 128 Block Ack to STA1 130 Data to AP in non-TB PPDU (AC3) 132 Block Ack to STA1 134 PIFS 136 Data to another non-AP STA

Claims

1. An apparatus for wireless communication in a network, comprising: (a) a wireless communication station (STA), which operates as either a normal STA or an access point (AP) STA, performing frame transmission over a channel between a medium access control (MAC) layer of an IEEE 802.11 network as an independent communication station (STA) or as an STA in a multi-link device (MLD), and wirelessly communicating with other wireless STAs using a carrier sense multiple access / collision avoidance (CSMA / CA) mechanism on a wireless local area network (WLAN) in which enhanced distributed channel access (EDCA) is utilized for random channel access on all links; (b) a processor coupled to the wireless communication circuitry for operating on the WLAN; (c) a non-transitory memory storing instructions executable by said processor for communicating with other STAs; Equipped with (d) the instructions, when executed by the processor, (i) a STA acting as an AP STA obtains a transmission opportunity (TXOP); (ii) in response to meeting an Access Class (AC) requirement, the AP STA allocating time within the TXOP to one or more non-AP STAs; (iii) the AP STA transmitting a frame indicating a required AC requirement that one of the one or more non-AP STAs must meet in order to utilize an allocated time within the TXOP; (iv) receiving a response from one of the one or more non-AP STAs that received the frame transmitted by the AP STA indicating requested AC requirements; and performing steps of a wireless communication protocol including: (v) the response received by the AP STA indicates whether the non-AP STA meets the requested AC requirements; (vi) if the non-AP STA meets the required AC requirements, the non-AP STA proceeds to access the network and transmit data having the required AC requirements; An apparatus comprising:

2. The frame transmitted by the AP STA indicating the required AC requirements includes a trigger frame that can be configured to meet high efficiency (HT) and / or very high throughput (EHT) according to the IEEE 802.11 standard.

2. The apparatus of claim 1.

3. The frame transmitted by the AP STA indicating the requested AC requirements includes a multi-user (MU) request to send (RTS) TXOP shared (TXS) trigger frame; 2. The apparatus of claim 1.

4. the response received by the AP STA from one or more non-AP STAs receiving the frame indicating the requested AC requirements includes a clear to send (CTS) frame indicating whether the requested AC requirements are met by the non-AP STA.

2. The apparatus of claim 1.

5. If the requested AC requirements are not met by the non-AP STA, the AP STA transmits a frame indicating the requested AC requirements to a different non-AP STA, and provides an allocation time within the TXOP if the requested AC requirements can be met.

2. The apparatus of claim 1.

6. The data transmitted by the non-AP STA includes data to be uploaded to the AP STA or data to be transmitted to another non-AP STA.

2. The apparatus of claim 1.

7. A waiting data packet of the non-AP STA is deemed to satisfy the AC requirement if one or more data packets in an EDCA queue have an AC value equal to or higher than the requested AC requirement sent by the AP STA.

2. The apparatus of claim 1.

8. The waiting data packets of the non-AP STA are deemed not to meet the AC requirement if these data packets in the EDCA queue have an AC value lower than the requested AC requirement sent by the AP STA; 2. The apparatus of claim 1.

9. If the frame indicating the required AC requirement indicates that the TXOP sharing mode subfield value is equal to a value indicating that the AP STA is not allowed to share the TXOP, the AP STA is prevented from sharing the TXOP; 2. The apparatus of claim 1.

10. The non-AP STA accesses a channel during a shared TXOP to transmit an MPDU satisfying the requested AC requirement indicated in the frame indicating the requested AC requirement to an associated AP only when the TXOP shared mode subfield value is equal to a first state, and transmits to an associated AP or another STA when the TXOP shared mode subfield value is equal to a second state.

2. The apparatus of claim 1.

11. and conveying a multiplexing identification (TID) aggregation-MAC protocol data unit (A-MPDU) limit subfield in a frame transmitted by the AP STA indicating the requested AC requirements, the TID A-MPDU limit subfield indicating the number of MPDUs allowed in an A-MPDU and the maximum number of TIDs that a non-AP STA may aggregate in an A-MPDU.

2. The apparatus of claim 1.

12. A non-AP STA transmitting multiple TID A-MPDUs within the allocated time indicated by a frame containing an indicated requested AC value should aggregate data units in the following order: (i) first, any and all MPDUs corresponding to the requested AC subfields of the user information field of the frame addressed to the non-AP STA containing the requested AC value, (ii) second, any and all MPDUs corresponding to any AC having a higher priority than the requested AC, and (iii) the non-AP STA shall not aggregate MPDUs corresponding to ACs having a lower priority than the requested AC.

12. The apparatus of claim 11.

13. A non-AP STA transmitting a single TID A-MPDU within the allocated time indicated by a frame including the requested AC value aggregates data frames in the following order: (i) aggregates TIDs corresponding to the requested AC subfields addressed to the non-AP STA; (ii) if condition (i) cannot be satisfied, aggregates data frames having TIDs corresponding to any AC having a higher priority than the requested AC; and (iii) the non-AP STA does not aggregate MPDUs corresponding to ACs having a lower priority than the requested AC.

12. The apparatus of claim 11.

14. the required AC subfield and the TID A-MPDU limit subfield are carried in a trigger-dependent user information subfield that is not present in a user information field of a trigger frame; 12. The apparatus of claim 11.

15. An apparatus for wireless communication in a network, comprising: (a) a wireless communication station (STA), which operates as either a normal STA or an access point (AP) STA, performing frame transmission between a medium access control (MAC) layer of an IEEE 802.11 network as an independent communication station (STA) or as an STA in a multi-link device (MLD), and wirelessly communicating with other wireless STAs using a carrier sense multiple access / collision avoidance (CSMA / CA) mechanism on a wireless local area network (WLAN) in which enhanced distributed channel access (EDCA) is utilized for random channel access on all links; (b) a processor coupled to the wireless communication circuitry for operating on the WLAN; (c) a non-transitory memory storing instructions executable by said processor for communicating with other STAs; Equipped with (d) the instructions, when executed by the processor, (i) a STA acting as an AP STA obtains a transmission opportunity (TXOP); (ii) in response to meeting an Access Class (AC) requirement, the AP STA allocating time within the TXOP to one or more non-AP STAs; (iii) the AP STA transmitting a frame indicating a required AC requirement that one of the one or more non-AP STAs must meet in order to utilize an allocated time within the TXOP; (iv) receiving a response from one of the one or more non-AP STAs that received the frame transmitted by the AP STA indicating requested AC requirements; and performing steps of a wireless communication protocol including: (v) the response received by the AP STA indicates whether the non-AP STA meets the requested AC requirements; (vi) if the non-AP STA meets the required AC requirements, the non-AP STA proceeds to access the network and transmit data having the required AC requirements; (vii) the frame transmitted by the AP STA indicating the required AC requirements comprises either (A) a trigger frame configurable to meet high efficiency (HT) and / or very high throughput (EHT) according to the IEEE 802.11 standard, or a multi-user (MU) request to send (RTS) TXOP sharing (TXS) trigger frame; (viii) the response received by the AP STA from one or more non-AP STAs receiving the frame indicating the requested AC requirements includes a clear to send (CTS) frame indicating whether the requested AC requirements are met by the non-AP STA; (ix) if the requested AC requirement is not met by the non-AP STA, the AP STA transmits a frame indicating the requested AC requirement to a different non-AP STA, and provides an allocation time within the TXOP if the requested AC requirement can be met; An apparatus comprising:

16. The data transmitted by the non-AP STA includes data to be uploaded to the AP STA or data to be transmitted to another non-AP STA.

16. The apparatus of claim 15.

17. A waiting data packet of the non-AP STA is deemed to satisfy the AC requirement if one or more data packets in an EDCA queue have an AC value equal to or higher than the requested AC requirement sent by the AP STA.

16. The apparatus of claim 15.

18. The waiting data packets of the non-AP STA are deemed not to meet the AC requirement if these data packets in the EDCA queue have an AC value lower than the requested AC requirement sent by the AP STA; 16. The apparatus of claim 15.

19. If the frame indicating the requested AC requirement indicates that the TXOP sharing mode subfield value is set to indicate that sharing is prevented, the AP STA is prevented from sharing the TXOP.

16. The apparatus of claim 15.

20. The non-AP STA accesses a channel during a shared TXOP to transmit an MPDU satisfying the requested AC requirement indicated in the frame indicating the requested AC requirement to an associated AP only when the TXOP shared mode subfield value is equal to a first state, and transmits to an associated AP or another STA when the TXOP shared mode subfield value is equal to a second state.

16. The apparatus of claim 15.

21. and conveying a multiplexing identification (TID) aggregation-MAC protocol data unit (A-MPDU) limit subfield in a frame transmitted by the AP STA indicating the requested AC requirements, the TID A-MPDU limit subfield indicating the number of MPDUs allowed in an A-MPDU and the maximum number of TIDs that a non-AP STA may aggregate in an A-MPDU.

16. The apparatus of claim 15.

22. A non-AP STA transmitting multiple TID A-MPDUs within the allocated time indicated by a frame containing an indicated requested AC value should aggregate data units in the following order: (i) first, any and all MPDUs corresponding to the requested AC subfields of the user information field of the frame addressed to the non-AP STA containing the requested AC value, (ii) second, any and all MPDUs corresponding to any AC having a higher priority than the requested AC, and (iii) the non-AP STA shall not aggregate MPDUs corresponding to ACs having a lower priority than the requested AC.

22. The apparatus of claim 21.

23. A non-AP STA transmitting a single TID A-MPDU within the allocated time indicated by a frame including the requested AC value aggregates data frames in the following order: (i) aggregates TIDs corresponding to the requested AC subfields addressed to the non-AP STA; (ii) if condition (i) cannot be satisfied, aggregates data frames having TIDs corresponding to any AC having a higher priority than the requested AC; and (iii) the non-AP STA does not aggregate MPDUs corresponding to ACs having a lower priority than the requested AC.

22. The apparatus of claim 21.

24. the required AC subfield and the TID A-MPDU limit subfield are carried in a trigger-dependent user information subfield that is not present in a user information field of a trigger frame; 22. The apparatus of claim 21.

25. 1. A method for conducting wireless communication in a network, comprising: (a) transmitting frames between a medium access control (MAC) layer of an IEEE 802.11 network having independent communication stations (STAs) and / or STAs in a multi-link device (MLD), and performing communication on a wireless network having stations (STAs) operating as either normal STAs or access point (AP) STAs that communicate wirelessly with other wireless STAs using a carrier sense multiple access / collision avoidance (CSMA / CA) mechanism on a wireless local area network (WLAN) in which enhanced distributed channel access (EDCA) is utilized for random channel access on all links; (b) a STA acting as an AP STA obtains a transmission opportunity (TXOP); (c) in response to meeting an Access Class (AC) requirement, the AP STA allocating time within the TXOP to one or more non-AP STAs; (d) the AP STA transmitting a frame indicating a required AC requirement that one of the one or more non-AP STAs must meet in order to utilize an allocated time within the TXOP; (e) receiving a response from one of the one or more non-AP STAs that received the frame transmitted by the AP STA indicating requested AC requirements; Including, (f) the response received by the AP STA indicates whether the non-AP STA meets the requested AC requirements; (g) if the non-AP STA meets the required AC requirements, the non-AP STA proceeds to access the network and transmit data having the required AC requirements; A method comprising:

Images