Apparatus and method for wireless communication in a network

Abstract

A communication circuit and protocol for a wireless local area network (WLAN) using CSMA / CA and single EDCA and / or multi-user (MU) EDCA. The EDCA function is configured to operate by providing a plurality of sets of operating parameters of a range of priority levels to dynamically alter the nominal access time for a STA to transmit prioritized packets. The STA must then switch to a lower priority set of parameters as compensation so that channel usage remains fair.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to and the benefit of U.S. Patent Application Serial No. 17 / 468,888, filed September 8, 2021, which is incorporated by reference herein in its entirety. This application also claims priority to and the benefit of U.S. Provisional Patent Application Serial No. 63 / 126,585, filed December 17, 2020, which is incorporated by reference herein in its entirety.

[0003] STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

[0004] NOT APPLICABLE

[0005] NOTICE OF COPYRIGHTED MATERIAL

[0006] A portion of the material in this patent document can be subject to copyright protection under the laws of the United States and of other countries. The owner of the copyright rights has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the United States Patent and Trademark Office publicly available files or records, but otherwise reserves all copyright rights whatsoever. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the United States Patent and Trademark Office publicly available files or records, but otherwise reserves all copyright rights whatsoever. The copyright owner hereby makes the disclaimer of any and all copyright rights to this patent document. TECHNICAL FIELD

[0007] The technology of the present disclosure relates generally to wireless local area networks under IEEE 802.11, and more specifically to CSMA / CA networks using EDCA in a manner that supports Real-Time Application (RTA) traffic. BACKGROUND

[0008] Current wireless technologies using CSMA / CA focus on high throughput performance of the network but lack low latency capability. However, an increasing number of applications, such as Real-Time Applications (RTAs), require low latency; thus, a technology gap has emerged.

[0009] RTAs require low latency communication and use best effort communication. Data generated from an RTA is referred to as RTA traffic and will be packetized as an RTA packet at the sender STA. Also, data generated from a non-time sensitive application is referred to as non-RTA traffic and will be packetized as a non-RTA packet at the sender STA.

[0010] RTA packets require low latency due to their high timeliness requirement for packet delivery. An RTA packet is valid when delivered within a certain time period.

[0011] The enhanced distributed channel access (EDCA) function of 802.11e defines multiple access categories (ACs) with contention window (CW) sizes, arbitration interframe space (AIFS) values, and transmission opportunity (TXOP) limits specific to the ACs to support MAC level QoS and prioritization.

[0012] However, RTA operations are often compromised under EDCA type protocols, and RTA based protocols can be unfair to non-RTA wireless devices.

[0013] Thus, there is a need for an EDCA based protocol that provides improved RTA performance without unduly compromising non-RTA throughput levels. The present disclosure overcomes these problems and provides additional benefits over the prior art. SUMMARY

[0014] This IEEE 802.11 WLAN protocol is configured to allow a device to maintain multiple sets of enhanced distributed channel access (EDCA) and multi-user (MU) EDCA parameters. By changing the parameters of an access category (AC), the nominal channel access time for that AC can be increased or decreased compared to its priority using the default parameter settings. A wireless device can switch between the EDCA and MU EDCA parameter settings according to time to increase or decrease the nominal channel access time for each AC.

[0015] The changes to the nominal channel access time for an AC are primarily driven in at least one embodiment based on considerations for fairness issues. More specifically, when the access time for an AC of a wireless device is shortened for a period of time, then its channel access time should also be increased for another period of time, which is a form of yielding. When an AC of a wireless device shortens its channel access time, another AC of the same wireless device can simultaneously increase their channel access.

[0016] Other aspects of the technology described herein will be presented in the following detailed description of the technology and, particularly, in the DETAILED DESCRIPTION, which is intended to make fully apparent the preferred embodiments of the technology, and is made for the purpose of the full disclosure of the technology. BRIEF DESCRIPTION OF DRAWINGS

[0017] The technology described herein will be more fully understood by reference to the following drawings, which are for illustrative purposes only:

[0018] FIG. 1 is a data field diagram of an EDCA parameter set element as defined in IEEE 802.11.

[0019] FIG. 2 is a data field diagram of a QoS info field as defined in IEEE 802.11 when sent by an AP.

[0020] Figure 3 is a data field diagram of the AC_X parameter record field as defined in IEEE 802.11.

[0021] Figure 4 is a data field diagram of the MU EDCA parameter set element defined in IEEE 802.11.

[0022] Figure 5 is a data field diagram of the MU AC_X parameter record field as defined in IEEE 802.11.

[0023] FIG. 6 is a hardware block diagram of a wireless station hardware in accordance with at least one embodiment of the present disclosure.

[0024] FIG. 7 is a hardware block diagram of a station configuration such as contained in a multi-link device hardware in accordance with at least one embodiment of the present disclosure.

[0025] FIG. 8 is a topology of a WLAN with six STAs and two APs spanning two BSSs in accordance with at least one example of the present disclosure.

[0026] FIG. 9 is a flow diagram of a STA with priority capability (with P capability) contending for the channel and obtaining a transmission opportunity (TXOP) of an AC in accordance with at least one example of the present disclosure.

[0027] FIG. 10 is a flow diagram of a STA with P capability contending for the channel and obtaining a TXOP of an AC during a prioritized period in accordance with at least one example of the present disclosure.

[0028] FIG. 11 is a flow diagram of a STA contending for channel access and obtaining a TXOP for a prioritized packet transmission during a prioritized period in accordance with at least one example of the present disclosure.

[0029] FIG. 12 is a communication diagram of an AP transmitting a priority EDCA parameter set update frame or a multi-link parameter set update frame in accordance with at least one example of the present disclosure.

[0030] FIG. 13 is a data field diagram of a priority EDCA parameter set element in accordance with at least one example of the present disclosure.

[0031] FIG. 14 is a data field diagram of a high priority (HP) parameter record subfield for an AC in accordance with at least one example of the present disclosure.

[0032] FIG. 15 is a data field diagram of a low priority (LP) parameter record subfield for an AC in accordance with at least one example of the present disclosure.

[0033] FIG. 16 is a data field diagram of beacon frame contents including an EDCA parameter set element, a MU EDCA parameter set element, and a priority EDCA parameter set element according to at least one example of the present disclosure.

[0034] FIG. 17 is a data field diagram of a Neighbor AP information field according to at least one example of the present disclosure.

[0035] FIG. 18 is a data field diagram of an MLD parameters subfield of TBTT information according to at least one example of the present disclosure, which is used to carry a prioritized EDCA field, an EDCA parameter set element, a MU EDCA parameter set element, and a priority EDCA parameter set element in a TBTT information set subfield.

[0036] FIG. 19 is a data field diagram of a non-transmitted BSSID profile field for carrying a prioritized EDCA field, an EDCA parameter set field, a MU EDCA parameter set field, and a priority EDCA parameter set field according to at least one example of the present disclosure.

[0037] FIG. 20 is a data field diagram of a multi-link element according to at least one example of the present disclosure, which is used to carry a prioritized EDCA element, an EDCA parameter set element, a MU EDCA parameter set element, and a priority EDCA parameter set field in each STA profile subfield thereof.

[0038] FIG. 21 is a data field diagram of a priority parameter set update frame according to at least one example of the present disclosure.

[0039] FIG. 22 is a data field diagram of a multi-link parameter update frame according to at least one example of the present disclosure.

[0040] FIG. 23 is a communication sequence diagram using different EDCA parameter settings according to at least one embodiment of the present disclosure.

[0041] FIG. 24 is a communication sequence diagram using low priority EDCA parameter settings to disable channel contention for an AC according to at least one embodiment of the present disclosure.

[0042] FIG. 25 is a communication sequence diagram of a STA starting a non-priority period after a prioritized period for an AC according to at least one embodiment of the present disclosure.

[0043] FIG. 26A communication sequence diagram of a STA delaying between two prioritized periods for ACs according to at least one embodiment of the disclosure.

[0044] FIG. 27 A communication sequence diagram of a STA using different EDCA parameters for non-priority packets during a prioritized period according to at least one embodiment of the disclosure.

[0045] FIG. 28 A communication timing diagram of a STA setting different period modes for multiple ACs simultaneously according to at least one embodiment of the disclosure.

[0046] FIG. 29 A communication sequence diagram of a STA using priority EDCA parameters for multiple ACs during a prioritized period according to at least one embodiment of the disclosure.

[0047] FIG. 30 A communication sequence diagram of one AC of a STA using backoff slot duration for one AC's LP EDCA parameters during a prioritized period according to at least one embodiment of the disclosure.

[0048] FIG. 31 A communication sequence diagram of one STA using backoff slot duration for LP EDCA parameters during a prioritized period according to at least one embodiment of the disclosure.

[0049] FIG. 32 A communication sequence diagram of a STA using priority EDCA parameters for MU EDCA parameters during a prioritized period according to at least one embodiment of the disclosure.

[0050] FIG. 33 A communication sequence diagram of a STA switching to use low priority (LP) MU EDCA parameters for MU EDCA parameters during a prioritized period according to at least one embodiment of the disclosure.

[0051] FIG. 34 A communication sequence diagram of a STA using multiple EDCA functions (EDCAFs) for single packet transmission according to at least one embodiment of the disclosure.

[0052] FIG. 35 A communication sequence diagram of a STA using multiple EDCAFs to transmit packets from one AC according to at least one embodiment of the disclosure.

[0053] FIG. 36A and FIG. 36B A communication sequence diagram of a STA using priority EDCA and multiple EDCAFs to transmit packets from one AC according to at least one embodiment of the disclosure.

[0054] FIG. 37A and FIG. 37B is a communication sequence diagram of a STA using priority EDCA and multiple EDCAF to transmit packets from one AC according to at least one embodiment of the present disclosure.

[0055] FIG. 38 is a communication sequence diagram of using different AIFS during the backoff procedure according to at least one embodiment of the present disclosure. DETAILED DESCRIPTION

[0056] 1. INTRODUCTION

[0057] It can not be possible to achieve both high throughput and low latency in a given network. To meet the different requirements of RTA and non-RTA packets, the disclosed protocol utilizes some features to improve its low latency performance when transmitting RTA packets, and other features to maximize throughput when transmitting non-RTA packets.

[0058] To achieve these goals, the sender station (STA) is required to be able to distinguish between RTA and non-RTA traffic. In some cases, the receiver STA can also benefit from distinguishing between RTA and non-RTA packets, for example to allow the network to choose between different features to meet the requirements of RTA and non-RTA traffic, respectively.

[0059] Most commonly, RTA generates traffic episodically as connection-oriented communications. A connection-oriented RTA communication established between STAs by an application is referred to as an RTA session. A STA can have multiple RTA sessions in the network, and it is important for the STA to properly manage those RTA sessions.

[0060] 2. IEEE 802.11 Parameter Set Element

[0061] 2.1. EDCA Parameter Set Element

[0062] Figure 1 illustrates the format of the EDCA Parameter Set element defined in IEEE 802.11. The "Element ID" and "Element ID Extension" fields provide the identity of the element to indicate that this element is the EDCA Parameter Set element. The "Length" field indicates the length of the element. The "QoS Info" field is defined in IEEE 802.11 as shown in Figure 2. The "Updated EDCA Info" field is defined in IEEE 802.11 and is reserved for non-sub-1 GHz (non-S1G STA). The next four fields have the subfield format as shown in Figure 3. The "AC_BE Parameter Record" field carries the EDCA parameters for AC_BE. The "AC_BK Parameter Record" field carries the EDCA parameters for AC_BK. The "AC_VI Parameter Record" field carries the EDCA parameters for AC_VI. The "AC_VO Parameter Record" field carries the EDCA parameters for AC_VO.

[0063] Figure 2 illustrates the format of the "QoS Info" field when sent by an AP as defined in IEEE 802.11. The "EDCA Parameter Set Update Count" field indicates the version of the EDCA Parameter Set. If a non-AP STA receives this and it is different from the value the non-AP STA has stored, then the STA preferably updates the EDCA parameters according to the most recently received EDCA Parameter element. The "Q-ACK" field is set to a first state (e.g., "1") when dot11QAckOptionImplemented is set to a first state (e.g., "1"), otherwise it is set to a second state (e.g., "0"). It should be noted that dot11QAckOptionImplemented is a capability variable in IEEE P802.11REVmd_D5.0. Its value is determined by the device capabilities. When this attribute is true, it indicates that the station implementation is capable of interpreting the CF-ACK bit in received frames where the "Type" subfield is equal to "Data", even if the frame is not directed to a QoS station. Otherwise, the capability is disabled. If a STA is the recipient of a "Data" frame, then that station is capable of interpreting the CF-ACK bit in received "Data" frames, regardless of the value of this MIB attribute.

[0064] The "Queue Request" field is set to a first state (e.g., "1") if the AP can handle a non-zero "Queue Size" subfield in the "QoS Control" field in QoS Data frames; otherwise it is set to a second state (e.g., "0"). The "TXOP Request" field is set to a first state (e.g., "1") if the AP can handle a non-zero "TXOP Duration Request" subfield in the "QoS Control" field in QoS Data frames; otherwise it is set to a second state (e.g., "0").

[0065] Figure 3 illustrates the format of the "AC_x Parameter Record" field as defined in IEEE 802.11. The "AC / AIFSN" field indicates the parameter set of access category (AC) and AIFSN for this field. The "ECWmin / ECWmax" field indicates the minimum contention window (CW) size and the maximum CW size for the AC. The "TXOP Limit" field indicates the TXOP limit for the AC.

[0066] 2.2. Multi-User EDCA Parameter Set Element

[0067] Figure 4 illustrates the format of the MU EDCA Parameter Set element defined in IEEE 802.11. The "Element ID" and "Element ID Extension" fields provide the identification of the element to indicate that this element is the MU EDCA Parameter Set element. The "Length" field indicates the length of the element. The "QoS Info" field is defined in IEEE 802.11 as shown in Figure 2. The subfield format of the remaining fields is shown in Figure 5. The "MU AC_BE Parameter Record" field carries the MU EDCA parameters for AC_BE. The "MU AC_BK Parameter Record" field carries the MU parameters for AC_BK. The "MU AC_VI Parameter Record" field carries the MU EDCA parameters for AC_VI. The "MU AC_VO Parameter Record" field carries the MU EDCA parameters for AC_VO.

[0068] Figure 5 illustrates the format of the MU AC_x Parameter Record field as defined in IEEE 802.11. The "AC / AIFSN" field indicates the parameter set of access category (AC) and AIFSN for this field during the MU_EDCA Timer. The "ECWmin / ECWmax" field indicates the minimum contention window (CW) size and the maximum CW size for the AC during the MU_EDCA Timer. The "MU_EDCA Timer" field indicates the duration that the STA is to use the MU EDCA parameters for the AC.

[0069] 2. Problem Statement

[0070] Current IEEE 802.11 devices use a single set of EDCA and MU EDCA parameters for channel contention. The priority of channel access for each access category (AC) is statically set. For a STA, a higher priority AC can access the channel earlier than a lower priority AC with a higher probability. However, a STA can need to shorten the nominal channel access time of a given AC for a period of time to transmit special traffic, such as traffic for real-time applications (RTA). For example, when an AC contends for the channel for transmitting RTA traffic, its nominal channel access time should be shortened to meet its timeliness requirement. When an AC has no RTA traffic to transmit, it has no special requirement for speeding up the channel access time. That is, a wireless device can dynamically change the EDCA and MU EDCA parameters of an AC over time, which cannot be achieved using a single set of EDCA or MU EDCA parameters.

[0071] 3. Contributions of the disclosure

[0072] The proposed technique allows each IEEE 802.11 device (STA) to maintain multiple sets of EDCA and MU EDCA parameters. By changing the parameters of an AC, the nominal channel access time of that AC can be increased or decreased relative to its priority set using the default parameters. Thus, a wireless device is able to switch between EDCA and MU EDCA parameter settings over time to increase or decrease the nominal channel access time of each AC. From here on the term nominal access time will be used, and it should be recognized that this value

[0073] The proposed technique takes into account the fairness issue of shortening the nominal channel access time of an AC. There are multiple choices to address the fairness issue, the following are two examples.

[0074] In the first choice, when an AC of a wireless device shortens its channel access time for a period of time, then its channel access time should be increased towards fairness (equality) in another period of time.

[0075] In the second option, when an AC of a wireless device shortens its channel access time, then another AC of the same wireless device should increase its channel access time towards fairness (equality).

[0076] 4. Embodiments

[0077] 4.1. Station hardware configuration

[0078] FIG. 6An example embodiment 10 of STA hardware configured to perform the protocol of the present disclosure is illustrated. External I / O connections 14 are preferably coupled to an internal bus 16 on which a CPU 18 and memory (e.g., RAM) 20 are connected for executing program(s) implementing the communication protocol. The host machine houses at least one modem 22 to support communications coupled to at least one RF module 24, 28, each connected to one or more antennas 29, 26a, 26b, 26c through 26n. RF modules with multiple antennas (e.g., antenna arrays) allow beamforming to be performed during transmission and reception. In this way, the STA can use multiple sets of beam patterns to transmit signals.

[0079] Bus 14 allows various devices to be connected to the CPU, such as to sensors, actuators, etc. Instructions from memory 20 are executed on processor 18 to perform programs implementing the communication protocol, which are executed to allow the STA to perform the functions of an access point (AP) station or a regular station (non-AP STA). It should also be recognized that the programming is configured to operate in different modes (TXOP holder, TXOP sharing participant, source, intermediate, destination, first AP, other AP, stations associated with the first AP, stations associated with the other AP, coordinator, coordinated, etc.), depending on the role it plays in the current communication context. Thus, the STA HW is shown configured with at least one modem and associated RF circuitry for providing communications over at least one frequency band, such as sub-6 GHz bands.

[0080] Further, it will be noted that multiple instances of the station hardware as illustrated can be combined into a multi-link device (MLD), which will typically have a processor and memory for coordinating activities, while a separate CPU and memory are not always needed for each STA within the MLD.

[0081] FIG. 7 An example embodiment 40 of a multi-link device (MLD) hardware configuration is illustrated. Multiple STAs are affiliated to one MLD, each operating on a link of a different frequency. The MLD has external I / O 41 access to applications, which is connected to an MLD management entity 48 with CPU 62 and memory (e.g., RAM) 64 to allow execution of program(s) implementing the communication protocol at the MLD level. The MLD can assign tasks to each of the affiliated STAs 1 42, STA 2 44 through STA N 46 to which it is connected and gather information from them and share information among the affiliated STAs.

[0082] In at least one embodiment, each STA of the MLD has its own CPU 50 and memory (RAM) 52, which are coupled through a bus 58 to at least one modem 54, which connects to at least one RF circuit 56 with one or more antennas 60a, 60b, 60c through 60n. The present disclosure is primarily interested in sub-6 GHz bands with omni-directional antennas. The modem, along with the RF circuit and associated antenna(s), transmits / receives data frames with neighboring STAs. In at least one implementation, the RF module includes frequency converters, array antenna controllers, and other circuitry for interfacing with its antennas.

[0083] It should be recognized that each STA of the MLD does not necessarily require its own processor and memory, as the STAs can share resources with each other and / or with the MLD management entity, depending on the specific MLD implementation. It should be recognized that the above MLD diagram is given by way of example and not limitation, and that the present disclosure can operate using a wide range of MLD implementations.

[0084] 4.2. STAs topology for consideration

[0085] FIG. 8 An example embodiment 70 of a topology (network scenario) is illustrated, which is given by way of example and not limitation. The topology is provided only for the purpose of explaining the goal of the proposed technology, and not to limit it to a specific STA configuration. In this example case topology, it is assumed that there are 6 STAs and 2 APs across two BSSs of a given space (e.g., a conference room). Each STA and its associated AP can communicate with each other. Note that since the two APs of the two BSSs belong to the same MLD, it is also possible to consider the two BSSs as one BSS.

[0086] An MLD is a device with more than one affiliated STA and with one MAC service access point (SAP) to a logical link control (LLC) that includes one MAC data service. In this example case, it is assumed that there are four STAs that constitute two MLDs in a local area. STA1 80 and STA4 82 belong to non-AP multi-link device (MLD) #1 74, and AP1 76 and AP2 78 belong to AP MLD #2 72. STA1 and STA4 are associated with AP1 and AP2 through link 1 and link 2, respectively. STA2 84 and STA3 86 are shown as connecting to AP1 76 for MLD2 72. STA5 88 is shown as having link 1 to AP1 76, and STA6 90 is shown as having link 1 to AP2 78.

[0087] All STAs use CSMA / CA for random channel access. When a STA has P-capability, it is able to use multiple sets of EDCA parameters at different times; otherwise, it is considered as legacy device. As shown, two APs and STAs 1-4 have P-capability, while only STAs 5 88 and 6 90 are considered as legacy devices.

[0088] 4.3. Prioritized Channel Access

[0089] The disclosed technology defines multiple EDCA and MU-EDCA parameter settings at the STA. This multiple set of parameters provides a range of priority levels, such as a regular set of parameters and one or more sets at higher priority and one or more sets at lower priority. By way of example and not limitation, multiple sets of operating parameters are exemplified herein as regular (Reg), high priority (HP), and low priority (LP) settings.

[0090] A STA sets the regular EDCA and MU-EDCA parameter settings to the single EDCA and MU-EDCA parameter settings in normal use.

[0091] A STA sets the high priority (HP) EDCA and MU-EDCA parameter settings to speed up channel access compared to using the regular EDCA and MU-EDCA parameter settings.

[0092] A STA sets the low priority (LP) EDCA and MU-EDCA parameter settings to slow down channel access compared to the regular EDCA and MU-EDCA parameter settings. The low priority settings are mainly used to keep channel access fair among stations in the network.

[0093] A STA can dynamically switch between the EDCA and MU-EDCA parameter settings listed above to change the channel access parameters for each AC. It should be noted that the EDCA parameter settings and MU-EDCA parameter settings can be used / controlled independently.

[0094] In at least one embodiment, the disclosed technology also considers the fairness issue of changing the EDCA and MU-EDCA parameters of an AC. When a STA uses the high priority (HP) EDCA and MU-EDCA parameter settings of an AC to shorten its nominal channel access time by a period of time, for its previously reduced channel access time, it should (or is constrained to) also use the LP EDCA and MU-EDCA parameter settings of that AC to increase the nominal channel access time of that AC by another period of time towards providing compensation (fairness return). Furthermore, in at least one embodiment, the duration that a STA can continuously use the HP EDCA and MU-EDCA parameter settings of an AC is limited.

[0095] It should also be recognized that in at least one embodiment, the above-described "compensation" includes the ability to perform "pre-compensation" in which a lower priority set of operating parameters is used prior to a higher priority set of operating parameters being pre-compensated in whole or in part.

[0096] The disclosed technology uses HP EDCA and MU-EDCA parameter settings to shorten the nominal channel access time for certain types of traffic represented as prioritized traffic. When a packet carries prioritized traffic, it is represented herein as a prioritized packet.

[0097] 4.3.1. Channel access for STAs with P capability

[0098] The proposed technology represents the following period patterns (e.g., regular period, prioritized period, non-priority period) for each AC.

[0099] A regular period for an AC is considered to be a time when a STA uses regular EDCA and MU-EDCA parameter settings for that AC's channel access to access the channel. Those parameters can be set by elements as shown in FIG. 1 and FIG. 4.

[0100] A prioritized period for an AC is considered to be a time when a STA uses HP EDCA and MU-EDCA parameter settings to shorten that AC's nominal channel access time. In at least some cases, a prioritized period for an AC can be scheduled by an AP or a STA, such as periodically or dynamically. In at least some cases, during a prioritized period, a STA uses only HP EDCA and MU-EDCA parameters to transmit prioritized packets, while using regular or LP EDCA and MU-EDCA parameters to transmit other packets.

[0101] A non-priority period for an AC is considered to be a time when a STA uses LP EDCA and MU-EDCA parameter settings to increase that AC's nominal channel access time. In at least some cases, a non-prioritized period for an AC can be scheduled by an AP or a STA, such as periodically or dynamically.

[0102] It should be noted that the period patterns (e.g., regular period, prioritized period, non-priority period) for each AC can be different at a particular point in time. For example, a STA can have a prioritized period for AC_VO, a non-priority period for AC_VI, and regular periods for AC_BE and AC_BK at the same time.

[0103] 4.3.1.1. Flowchart

[0104] FIG. 9An example embodiment 110 is illustrated in which a P-capable STA contends for a channel toward gaining a TXOP for an AC. Execution begins 112 and a check 114 determines what type of period the P-capable STA is in for the AC. If the STA is in a regular period, then at block 116 the STA contends for the channel and gains a TXOP for that AC using regular EDCA and MU-EDCA parameters. If the STA is in a prioritized period, then at block 118 the STA contends for the channel and gains a TXOP for that AC using high priority EDCA and MU-EDCA parameters. And if the STA is in a non-priority period, then at block 120 the STA contends for the channel and gains a TXOP for that AC using low priority EDCA and MU-EDCA parameters. Thereafter, execution ends.

[0105] It should be recognized that a STA can contend and gain a TXOP for a prioritized packet transmission using only high priority EDCA and MU-EDCA parameters. For other packets, the STA can contend for the channel using regular or low priority EDCA and MU-EDCA parameters. More details are described in FIG. 10

[0106] FIG. 10 An example embodiment 130 is illustrated in which a P-capable STA contends for a channel and gains a TXOP for an AC during a prioritized period.

[0107] Execution begins 132 and a check 134 is made to determine whether the P-capable STA has prioritized traffic to transmit. If it is determined that the STA intends to transmit prioritized traffic, then at block 136 the STA contends for and gains a TXOP for the AC for the prioritized traffic using high priority EDCA and MU-EDCA parameters. If it is determined at block 134 that the P-capable STA does not have prioritized traffic to transmit, then execution proceeds to block 138 and the STA contends for and gains a TXOP for the AC using low priority or regular EDCA and MU-EDCA parameters.

[0108] It can thus be seen that a P-capable STA uses only high priority EDCA and MU-EDCA parameters for prioritized traffic. It will be noted that, FIG. 9 and FIG. 10 may be used in combination, or a STA can follow either FIG. 9 or FIG. 10 to contend for a channel.

[0109] FIG. 11 ​An example embodiment 150 is illustrated in which a STA contends for channel access and obtains a TXOP for a prioritized packet transmission during a prioritized period. Execution begins 152 and a STA contends 154 for the channel using multiple EDCAFs and obtains a TXOP for the same prioritized packet transmission.

[0110] It should be appreciated that throughout this disclosure, the terms AC_x and or AC_y are used to represent any one of the access categories (AC).

[0111] For example, the EDCAFs of AC_x and AC_y can contend for the channel at the same time to transmit a packet from AC_x. Or either AC_x or AC_y obtains the TXOP and transmits a packet from AC_x even though there are packets in the transmission queue of AC_y. It should be noted that AC_y can contend for the channel even though there are no packets from AC_y to transmit. The priority of AC_y can have to be lower than that of AC_x.

[0112] This approach can be used in this disclosure only for prioritized packets in a prioritized period. This approach provides a mechanism to allow the EDCA function of an AC to be used to contend for the channel and obtain a TXOP to transmit a packet from another AC.

[0113] 4.3.1.2. Priority EDCA Parameter Set Update

[0114] FIG. 12 An example embodiment 170 is illustrated in which an AP 172 sends 176 a priority EDCA parameter set update frame or a multi-link parameter set update frame to update the priority EDCA parameters of a recipient STA 174. If the recipient STA belongs to an MLD, then other STAs belonging to the same MLD can also update their priority EDCA parameters according to the context in the multi-link parameter set update frame. The format of the priority EDCA parameter set update frame and the multi-link parameter set update frame are shown in FIG. 21 and FIG. 22 respectively.

[0115] It should be noted that the multi-link parameter set update frame can also be used to update generic multi-link parameters such as the default EDCA parameters and the MU EDCA parameters of all STAs belonging to an MLD.

[0116] It should be noted that it is also possible for the AP to send a beacon frame, a (ML) probe response frame or an (re)association response frame as shown in FIG. 16 to update the priority EDCA parameters of the recipient STA.

[0117] 4.3.1.3. Frame Format

[0118] The priority EDCA parameter set element can be used by an AP to set high priority EDCA and MU-EDCA parameters and low priority EDCA and MU-EDCA parameters for its associated STAs.

[0119] The priority EDCA parameter set element can be carried by a frame carrying an EDCA parameter set element as shown in Figure 1 and a MU EDCA parameter set element as shown in Figure 4. For example, the priority EDCA parameter set element can be included in a beacon frame, a probe response frame or an (re)association response frame to indicate the high priority and low priority EDCA and MU-EDCA parameters that should be set at its associated STAs. In addition, the priority EDCA parameter set element can possibly be carried in the “per STA profile” field of the Multi-BSSID element, the Reduced Neighbor Report (RNR) element and the Multi-Link element defined in IEEE 802.11be to indicate the high priority and low priority EDCA and MU-EDCA parameters settings of its collocated APs. An AP can send a priority EDCA parameter set update frame to update the priority EDCA parameters at the STAs.

[0120] FIG. 13 The format of the priority EDCA parameter set element is illustrated. The “Element ID” and “Element ID extension” fields provide the identification of the element to indicate that this element is a priority EDCA parameter set element. The “Length” field indicates the length of the element. The “QoS Info” field is defined in IEEE 802.11 as shown in Figure 2.

[0121] The “Updated EDCA Info” field is defined in IEEE 802.11 and reserved for non-S1G STAs. The “HP Parameter Record” field carries the HP parameter record subfield for all ACs.

[0122] The format of the HP parameter record subfield is described in the following FIG. 14 The “HP Parameter Record” field is set by an AP to indicate the high priority EDCA and MU EDCA parameters that should be set at the corresponding STA. If a STA receives it in a priority EDCA parameter set update frame, a multi-link parameter set update frame, a beacon frame, a (ML) probe response frame or an (re)association response frame, the STA should update the high priority EDCA parameters for that AC on its side.

[0123] It should be noted that the “HP Parameter Record” field can only carry the high priority parameter record subfield for some ACs. If the priority EDCA parameter set element is carried by a priority EDCA parameter set update frame or a multi-link parameter set update frame, the corresponding STAs only update the high priority EDCA and MU EDCA parameters for the ACs carried by this element.

[0124] If the priority EDCA parameter set element is carried by a beacon frame, a (ML) probe response frame, or an (re)association response frame, the corresponding STA sets the high priority EDCA and MU EDCA parameters of the ACs carried by this element. For those high priority EDCA and MU EDCA parameters of the ACs which are not carried by this element, the corresponding STA can set them to the default EDCA and MU-EDCA parameters of those ACs.

[0125] FIG. 13 The "LP parameter record" field carries the LP parameter record subfields of all ACs. The format of the LP parameter record subfield of an AC is shown in FIG. 15 The "LP parameter record" field is set by the AP to indicate the low priority EDCA and MU EDCA parameters which should be set at the corresponding STA. If a STA receives it in a priority EDCA parameter set update frame, a multi-link parameter set update frame, a beacon frame, a (ML) probe response frame, or an (re)association response frame, the STA should update the low priority EDCA and MU EDCA parameters at its side.

[0126] It should be noted that this field can only carry the low priority parameter record subfields of some ACs. If the priority EDCA parameter set element is carried by a priority EDCA parameter set update frame or a multi-link parameter set update frame, the corresponding STA only updates the low priority EDCA and MU EDCA parameters of the ACs carried by this element.

[0127] If the priority EDCA parameter set element is carried by a beacon frame, a (ML) probe response frame, or an (re)association response frame, the corresponding STA sets the low priority EDCA and MU EDCA parameters of the ACs carried by this element. For those low priority EDCA and MU EDCA parameters of the ACs which are not carried by this element, the corresponding STA can set them to the default EDCA and MU-EDCA parameters of those ACs.

[0128] FIG. 13 The "AC HP indication" field in indicates which ACs are included in the "HP parameter record" field. This field can contain a list of bits, where each bit represents an AC. If this bit is set to the first state (e.g., "1"), the high priority EDCA and MU EDCA parameters of the corresponding AC are included in the "HP parameter record" field; otherwise, the high priority EDCA and MU EDCA parameters of the corresponding AC are not included in the "HP parameter record" field.

[0129] The order of the high priority EDCA and MU EDCA parameters of the ACs should follow the order of the ACs in this field. For example, if the AC HP indicates that there are four bits. From left to right, the first bit indicates the presence of the high priority EDCA and MU EDCA parameters of AC_VO. The second bit indicates the presence of the high priority EDCA and MU EDCA parameters of AC_VI. The third bit indicates the presence of the high priority EDCA and MU EDCA parameters of AC_BE. The fourth bit indicates the presence of the high priority EDCA and MU EDCA parameters of AC_BK. If this field is set to "1010", then it indicates that there are high priority EDCA and MU EDCA parameters of AC_VO and AC_BE in the "HP parameter record".

[0130] From left to right, the first "HP parameter record" subfield in the "HP parameter record" is the high priority EDCA and MU EDCA parameters of AC_VO that the corresponding STA needs to set. The second "HP parameter record" subfield in the "HP parameter record" is the high priority EDCA and MU EDCA parameters of AC_BE that the corresponding STA needs to set.

[0131] FIG. 13 The "AC LP indication" field in the "LP parameter record" field indicates which ACs are included in the "LP parameter record" field. This field can for example include a list of bits, where each bit represents an AC. If this bit is set to a first state (e.g., "1"), then the low priority EDCA and MU EDCA parameters of the corresponding AC are included in the "LP parameter record" field; otherwise the low priority EDCA and MU EDCA parameters of the corresponding AC are not included in the "LP parameter record" field.

[0132] The order of the low priority EDCA and MU EDCA parameters of the ACs should follow the order of the ACs in this field. For example, if the AC LP indicates four bits. From left to right, the first bit indicates the presence of the low priority EDCA and MU EDCA parameters of AC_VO. The second bit indicates the presence of the low priority EDCA and MU EDCA parameters of AC_VI. The third bit indicates the presence of the low priority EDCA and MU EDCA parameters of AC_BE. The fourth bit indicates the presence of the low priority EDCA and MU EDCA parameters of AC_BK. If this field is set to "1010", then it indicates the presence of the low priority EDCA and MU EDCA parameters of AC_VO and AC_BE in the "LP parameter record". From left to right, the first "LP parameter record" subfield in the "HP parameter record" is the low priority EDCA and MU EDCA parameters of AC_VO that the corresponding STA needs to set. The second "LP parameter record" subfield in the "LP parameter record" is the low priority EDCA and MU EDCA parameters of AC_BE that the corresponding STA needs to set.

[0133] FIG. 14 Figure 8 illustrates an example embodiment 210 showing the format of the "HP parameter record" subfield for an AC. AC_x in the figure represents an AC; for example, it can be AC_VI, AC_VO, AC_BE, AC_BK, or other newly added AC in EDCA.

[0134] The "AC_x parameter record" field indicates the high priority EDCA parameters that should be set by the corresponding STA. The format of this field can be the same as shown in Figure 3.

[0135] The "MU AC_x parameter record" field indicates the high priority MU EDCA parameters that should be set by the corresponding STA. The format of this field can be the same as shown in Figure 5.

[0136] The "AC_x HP-EDCA timer" field indicates the maximum time that the STA can use the high priority EDCA and MU EDCA parameters to continuously contend for the AC_x, e.g., the maximum prioritized period time. When its value is non-zero, the non-AP STA should uniformly and without pause count down the LP-EDCA timer of AC_x to 0.

[0137] FIG. 15 Figure 8 illustrates an example embodiment 210 showing the format of the "HP parameter record" subfield for an AC. AC_x in the figure represents an AC; for example, it can be AC_VI, AC_VO, AC_BE, AC_BK, or other newly added AC in EDCA.

[0138] The "AC_x Parameter Record" field indicates the low priority EDCA parameters of AC_x that should be set by the corresponding STA. The format of this field is shown in FIG. 3.

[0139] The "MU AC_x Parameter Record" field indicates the low priority MU EDCA parameters of AC_x that should be set by the corresponding STA. The format of this field is shown in FIG. 5.

[0140] The "AC_x LP-EDCA Timer" field indicates the time, e.g., a non-priority period of time after a prioritized period of time, that a STA must use the low priority EDCA and MU EDCA parameters of AC_x to contend for the channel for AC_x after it has used the high priority EDCA and MU EDCA parameters of AC_x. When the value of the LP-EDCA timer of AC_x has a non-terminal, e.g., non-zero, value, it is uniformly decremented to a terminal count, e.g., zero, without suspension by the non-AP STA.

[0141] The "AC_x Backoff Slot Duration" field indicates the backoff slot duration of AC_x used by the STA during the non-priority period.

[0142] FIG. 16 An example embodiment 250 of the contents of a beacon frame including an EDCA parameter set element, a MU EDCA parameter set element, and a priority EDCA parameter set element is illustrated.

[0143] The "Frame Control" field indicates the type of frame. The "Duration" field contains the NAV information for CSMA / CA channel access. The "RA" field contains the address of the recipient of the frame. The "TA" field contains the address of the STA that transmitted the frame. The BSSID is a tag that identifies the BSS from others. The "Sequence Control" field contains the fragment number and sequence number of the packet.

[0144] The "Beacon Frame Body" field can have the same contents as the frame body in the beacon frame of IEEE 802.11, some example subfields are listed below. The RNR (Reduced Neighbor Report) element contains channel and other information related to neighbor APs as defined in IEEE 802.11be. In addition, this element can possibly carry the default EDCA, default MU EDCA, and priority EDCA parameter sets of the neighbor APs.

[0145] The Element ID provides the identification of the element to indicate that this element is the RNR element. The "Length" field indicates the length of the element.

[0146] The "Neighbor AP Information" field includes one or more neighbor AP information fields, such as FIG. 17Each Neighbor AP information field can carry the default EDCA, default MU EDCA, and priority EDCA parameter set of the neighbor AP and other APs belonging to the same MLD as the neighbor AP on different links.

[0147] The "priority EDCA" field is set to indicate whether the priority EDCA parameter set is used by the AP sending the beacon frame. As an example and not by way of limitation, this field can be implemented with a one-bit indication. If the bit is set to a first state (e.g., "1"), then the priority EDCA parameter set is used; otherwise it is set to a second state (e.g., "0"). In at least one embodiment, a predetermined procedure / method can be utilized to determine / compute the priority EDCA parameters based on the default EDCA and MU EDCA parameters. For example, the TXOP limit of the low priority EDCA parameters of AC_VI is always set to half of the TXOP limit of the default EDCA parameters of AC_VI. When a STA is associated with the AP to which the priority EDCA field belongs, it shall use the priority EDCA parameters.

[0148] The "EDCA parameter set" field indicates the default EDCA parameters that the recipient STAs of the beacon frame shall set when they are associated with the sender AP of the beacon frame. The format of this field is shown in FIG. 1.

[0149] The "MU EDCA parameter set" field indicates the default MU EDCA parameters that the recipient STAs of the beacon frame shall set when they are associated with the sender AP of the beacon frame. The format of this field is shown in FIG. 4.

[0150] The "priority EDCA parameter set" field indicates the priority EDCA parameters that the recipient STAs of the beacon frame shall set when they are associated with the sender AP of the beacon frame. The format of this field is shown in FIG. 13

[0151] The Multiple BSSID element defined in IEEE 802.11be is used to indicate information about all the untransmitted BSSs supported by the AP device. The information of each untransmitted BSS is carried by the "untransmitted BSSID profile" field. The "untransmitted BSSID profile" field can possibly include the priority EDCA field, the EDCA parameter set element, the MU EDCA parameter set element, and the priority EDCA parameter set element. If the AP device of the untransmitted BSS belongs to an MLD, the multi-link element can be included in the corresponding "untransmitted BSSID profile" field. The EDCA and MU EDCA parameter settings on each link of the MLD can be carried by the multi-link element, as shown in FIG. 20

[0152] ​​The Multi-Link element indicates information of the AP on multiple links belonging to the non-transmitted BSSID profile (as defined in IEEE 802.11be) indicated in the non-transmitted BSSID. In FIG. 20 The possibility for the Multi-Link element to carry the "Prioritized EDCA" field, the "EDCA Parameter Set" field, the "MU EDCA Parameter Set" field and the "Priority EDCA Parameter Set" field for each AP on multiple links belonging to the non-transmitted BSSID is explained in

[0153] It should be noted that if the Priority EDCA Parameter Set element does not carry the parameters for all ACs, then the priority EDCA parameters for those ACs not carried by the Priority EDCA Parameter Set element can possibly be inherited (i.e. set to the same value) from those in the EDCA Parameter Set element and the MU EDCA Parameter Set element carried by the same Beacon frame body field as the Priority EDCA Parameter Set element. For example, if the high priority EDCA parameters for AC_BK are not included in the Priority EDCA Parameter Set element as shown in FIG. 16 , then those parameters can be set to the same as the regular EDCA parameters for AC_BK as shown in the EDCA Parameter Set element as shown in FIG. 16

[0154] FIG. 17 An example embodiment 270 of the Neighbor AP Information field defined in IEEE 802.11be is illustrated, here configured to carry the "Prioritized EDCA" field, the "EDCA Parameter Set" field, the "MU EDCA Parameter Set" field and the "Priority EDCA Parameter Set" field in its "TBTT Information Set" subfield in order to set those parameters at the STAs associated with the AP of the "TBTT Information Set" subfield.

[0155] The "TBTT Information Length" subfield in the "TBTT Information Header" field is set to indicate the presence of the "Prioritized EDCA" field, the "EDCA Parameter Set" field, the "MU EDCA Parameter Set" field and the "Priority EDCA Parameter Set" field in its "TBTT Information Set" subfield.

[0156] The "TBTT Information Set" field can then carry the "Prioritized EDCA" field, the "EDCA Parameter Set" field, the "MU EDCA Parameter Set" field and the "Priority EDCA Parameter Set" field as shown in FIG. 18

[0157] FIG. 18 ​​An example embodiment 290 of the MLD Parameter subfield illustrating the TBTT information as defined in IEEE 802.11be, and here configured to carry a “Prioritized EDCA” field, an EDCA Parameter Set element, an MU EDCA Parameter Set element, and a Priority EDCA Parameter Set element in its “TBTT Information Set” subfield, in order to set those parameters at STAs associated with the AP related to the “TBTT Information Set” subfield.

[0158] The MLD ID indicates the identity of the MLD to which the AP belongs. The Link ID provides the identity of the link on which the AP is operating. These two fields identify the AP to which the MLD parameters belong.

[0159] The “Change Sequence” indicates the version number of the MLD parameters. The value of this Change Sequence field is updated each time the MLD parameters of the AP to which the MLD parameters belong are updated, such as by incrementing by 1.

[0160] The “Prioritized EDCA” field is set to indicate whether the Priority EDCA Parameter Set is used by the AP to which the MLD parameters belong. In at least one embodiment, this field can be configured to use one bit indication. If the bit is set to a first state (e.g., “1”), then the Priority EDCA Parameter Set is used; otherwise set to a second state (e.g., “0”). In at least one embodiment, a predetermined procedure / method is used to determine / compute the Priority EDCA parameters based on the default EDCA and MU EDCA parameters. For example, the TXOP limit of the low priority EDCA parameters of AC_VI is always set to half of the TXOP limit of the default EDCA parameters of AC_VI. The Priority EDCA parameters should be used when a STA is associated with the AP to which the Priority EDCA field belongs.

[0161] The “EDCA Parameter Set” field indicates the default EDCA parameters. When a STA is associated with the AP to which the MLD parameters belong, it should set the default EDCA parameters as indicated by the most recently received “EDCA Parameter Set” field. The format of this field is shown in FIG. 1.

[0162] The “MU EDCA Parameter Set” field indicates the default MU EDCA parameters. When a STA is associated with the AP to which the MLD parameters belong, it should set the default MU EDCA parameters as indicated by the most recently received “MU EDCA Parameter Set” field. The format of this field is shown in FIG. 4.

[0163] The Priority EDCA Parameter Set element indicates the priority EDCA parameters. When a STA is associated with the AP to which the MLD parameters belong, it shall set the priority EDCA parameters as indicated in the most recently received "Priority EDCA Parameter Set" field. The format of this field is shown in FIG. 13

[0164] It should be noted that if the Priority EDCA Parameter Set element does not carry the parameters for all ACs, then the priority EDCA parameters for those ACs not carried by the Priority EDCA Parameter Set element can possibly be inherited (i.e., set the same value) from those in the EDCA Parameter Set element and the MU EDCA Parameter Set element carried by the same MLD parameter field as the Priority EDCA Parameter Set element. For example, if the high priority EDCA parameters for AC_BK are not included in the Priority EDCA Parameter Set element as shown in FIG. 18 FIG. 18

[0165] If there is no EDCA Parameter Set element, MU EDCA Parameter Set element, or Priority EDCA Parameter Set element, then these parameters can be inherited from those shown in the receiver or beacon frame body of the beacon frame as shown in FIG. 16

[0166] FIG. 19 Figure illustrates an example embodiment 310 of the Untransmitted BSSID Profile field as defined in IEEE 802.11be and is here configured to carry the "Prioritized EDCA" field, the "EDCA Parameter Set" field, the "MU EDCA Parameter Set" field, and the "Priority EDCA Parameter Set" field in order to set those parameters in the STAs associated with the AP to which the Untransmitted BSSID Profile field belongs.

[0167] The "Prioritized EDCA" field is set to indicate whether the priority EDCA parameter set is used by the AP to which the Untransmitted BSSID Profile field belongs. This field can be implemented using one bit indication. For example, if the bit is set to a first state (e.g., "1"), then the priority EDCA parameter set is used; otherwise it is set to a second state (e.g., "0"). In at least one implementation, a predetermined procedure / method is used to determine / compute the priority EDCA parameters based on the default EDCA and MU EDCA parameters. For example, the TXOP limit for the low priority EDCA parameters for AC_VI is always set to half of the TXOP limit for the default EDCA parameters for AC_VI.

[0168] ​​​​The "EDCA Parameter Set" field indicates the default EDCA parameters. When a STA is associated with the AP to which the "Untransmitted BSSID Profile" field belongs, it shall set the default EDCA parameters as indicated in the "EDCA Parameter Set" field. The format of this field is shown in Figure 1.

[0169] The MU EDCA Parameter Set element indicates the default MU EDCA parameters. When a STA is associated with the AP to which the "Untransmitted BSSID Profile" field belongs, it shall set the default MU EDCA parameters as indicated in the "MU EDCA Parameter Set" field. The format of this field is shown in Figure 4.

[0170] The Priority EDCA Parameter Set element indicates the priority EDCA parameters. When a STA is associated with the AP to which the "Untransmitted BSSID Profile" field belongs, it shall set the priority EDCA parameters as indicated in the "Priority EDCA Parameter Set" field. The format of this field is shown in FIG. 13 When a STA is associated with the AP to which the Priority EDCA field belongs, it shall use the priority EDCA parameters.

[0171] The Multi-Link element indicates information of the APs on multiple links belonging to the Untransmitted BSSID as indicated in the Untransmitted BSSID Profile (as defined in IEEE 802.1 lbe). FIG. 20 It is illustrated that in some cases, the Multi-Link element can be used to carry the "Prioritized EDCA" field, the "EDCA Parameter Set" field, the "MU EDCA Parameter Set" field, and the "Priority EDCA Parameter Set" field for each AP on multiple links belonging to the Untransmitted BSSID.

[0172] It should be noted that if the Priority EDCA Parameter Set element does not carry the parameters for all ACs, then the priority EDCA parameters for those ACs not carried by the Priority EDCA Parameter Set element can possibly inherit their values (i.e., set the same values) from those in the EDCA Parameter Set element and the MU EDCA Parameter Set element carried by the same Untransmitted BSSID Profile field as the Priority EDCA Parameter Set element. For example, if the high priority EDCA parameters for AC_BK are not included in the Priority EDCA Parameter Set element as shown in FIG. 19 FIG. 19

[0173] ​​If the “EDCA Parameter Set” field, the “MU EDCA Parameter Set” field, or the “Priority EDCA Parameter Set” field is not present, those parameters can be inherited by the STA from those fields shown in the beacon frame’s receiver or beacon frame’s subject as shown in FIG. 16 FIG. 20 Figure illustrates an example embodiment 330 of the Multi-Link element defined in IEEE 802.11be and is here configured to carry in its “Per STA Profile” subfield the Prioritized EDCA element, the EDCA Parameter Set element, the MU EDCA Parameter Set element, and the “Priority EDCA Parameter Set” field in order to set those parameters on the STAs associated with the AP of the “Per STA Profile” subfield.

[0174] The “Link ID” field indicates the link on which the AP operates. This field identifies the AP to which the parameters indicated in the “Prioritized EDCA” field, the EDCA Parameter Set element, the MU EDCA Parameter Set element, and the Priority EDCA Parameter Set element belong.

[0175] The “Prioritized EDCA” field is set to indicate whether the priority EDCA parameter set is used by the AP to which the MLD parameters belong. This field can be implemented using a one-bit indication. For example, if the bit is set to a first state (e.g., “1”), the priority EDCA parameter set is used; otherwise it is set to a second state (e.g., “0”). In at least one implementation, a predetermined procedure / method is used to determine / compute the priority EDCA parameters based on the default EDCA and MU EDCA parameters. For example, the TXOP limit of the low-priority EDCA parameters of AC_VI is always set to half of the TXOP limit of the default EDCA parameters of AC_VI. When a STA is associated with the AP to which the “Priority EDCA” field belongs, it shall use the priority EDCA parameters.

[0176] The “EDCA Parameter Set” field indicates the default EDCA parameters. When a STA is associated with the AP to which the MLD parameters belong, it shall set the default EDCA parameters as indicated in the “EDCA Parameter Set” field. The format of this field is shown in Figure 1.

[0177] The “MU EDCA Parameter Set” field indicates the default MU EDCA parameters. When a STA is associated with the AP to which the MLD parameters belong, it shall set the default MU EDCA parameters as indicated in the “MU EDCA Parameter Set” field as depicted in Figure 4.

[0178] The “Priority EDCA Parameter Set” field indicates the priority EDCA parameters. When a STA is associated with the AP to which the MLD parameters belong, it shall set the priority EDCA parameters as indicated in the “Priority EDCA Parameter Set” field as depicted in Figure 5. FIG. 13 ​The priority EDCA parameters shown in the "Priority EDCA Parameter Set" field.

[0179] It will be noted that if the priority EDCA parameter set element does not carry the parameters for all ACs, the priority EDCA parameters for those ACs not carried by the priority EDCA parameter set element can possibly be inherited (i.e., set to the same value) from those in the EDCA parameter set element and the MU EDCA parameter set element carried by the same "Per STA Profile" field as the priority EDCA parameter set element. For example, if the high priority EDCA parameters for AC_BK are not included in the priority EDCA parameter set element, those parameters can be set to the same value as the regular EDCA parameters for AC_BK indicated in the EDCA parameter set element.

[0180] If the "EDCA Parameter Set" field, the "MU EDCA Parameter Set" field, or the "Priority EDCA Parameter Set" field are not present, those parameters can be inherited from those shown in those fields of the STA or the unscheduled BSSID profile to which the unscheduled BSSID profile belongs, as shown in FIG. 19 .

[0181] FIG. 21 The format of the priority parameter set update frame is illustrated. The "Frame Control" field indicates the type of frame. The "Duration" field contains the NAV information for CSMA / CA channel access. The "Address 1" field contains the address of the recipient of the frame. The "Address 2" field contains the address of the STA that transmitted the frame. The "Address 3" field contains the BSSID. The "Sequence Control" field indicates the sequence number of the frame. The "HT Control" field indicates the additional control information for HT or VHT or HE or EHT frames. The "Action" field indicates the action to be performed when it is a priority parameter set update frame. The "Category" field and the "QoS Action" field indicate the type of the action field. In this case, it indicates that the action field is in a priority parameter set update frame. The "Priority EDCA Parameter Set" field indicates the priority EDCA parameters that the recipient STA should set to update. The format of this field is shown in FIG. 13 .

[0182] FIG. 22 The format of the multi-link parameter update frame is illustrated. The "Frame Control" field indicates the type of frame. The "Duration" field contains the NAV information for CSMA / CA channel access. The "Address 1" field contains the address of the recipient of the frame. The "Address 2" field contains the address of the STA that transmitted the frame. The "Address 3" field contains the BSSID. The "Sequence Control" field indicates the sequence number of the frame. The "HT Control" field indicates the additional control information for HT or VHT or HE or EHT frames.

[0183] The "Action" field indicates the action to be performed when it is a multi-link parameter update frame. The "Category" field and the "QoS / ML Action" field indicate the type of the Action field; in this case, it indicates that the Action field is a multi-link parameter update frame. The "MLD Parameters" field indicates the parameters to be set on the multiple links. The "MLD ID" indicates the identification of the MLD to which the AP belongs. The "Link ID" indicates the link on which the AP operates. Those two fields identify the AP to which the MLD parameters belong (i.e., the AP whose information the MLD parameters carry).

[0184] The "Change Sequence" indicates the version number of the MLD parameters. Each time the MLD parameters of the AP to which the MLD parameters belong are updated, the value of this field is updated, such as by being incremented by 1.

[0185] The "Prioritized EDCA" field is set to indicate whether the set of prioritized EDCA parameters is used by the AP to which the MLD parameters belong. This field can be implemented using a one-bit indication. For example, if the bit is set to a first state (e.g., "1"), then the set of prioritized EDCA parameters is used; otherwise it is set to a second state (e.g., "0"). In at least one implementation, a predetermined procedure / method is used to determine / compute the prioritized EDCA parameters based on the default EDCA and MU EDCA parameters. For example, the TXOP limit of the low-priority EDCA parameters of AC_VI is always set to half of the TXOP limit of the default EDCA parameters of AC_VI. When a STA is associated with the AP to which the "Prioritized EDCA" field belongs, it shall use the prioritized EDCA parameters.

[0186] The "EDCA Parameter Set" field indicates the default EDCA parameters. When a STA is associated with the AP to which the MLD parameters belong, it shall set the default EDCA parameters as indicated by the "EDCA Parameter Set" field as depicted in FIG. 1.

[0187] The "MU EDCA Parameter Set" element indicates the default MU EDCA parameters. When a STA is associated with the AP to which the MLD parameters belong, it shall set the default MU EDCA parameters as indicated by the "MU EDCA Parameter Set" field as depicted in FIG. 4.

[0188] The prioritized EDCA parameter set element indicates the prioritized EDCA parameters. When a STA is associated with the AP to which the MLD parameters belong, it shall set the prioritized EDCA parameters as indicated by the "Prioritized EDCA Parameter Set" field as depicted in FIG. 1.

[0189] It should be noted that if the priority EDCA parameter set element does not carry the parameters for all ACs, the priority EDCA parameters for those ACs not carried by the priority EDCA parameter set element can possibly inherit their values (i.e., be set to the same values) from those carried in the EDCA parameter set element and the MU EDCA parameter set element by the same MLD parameter field as the priority EDCA parameter set element. For example, if the high priority EDCA parameters for AC_BK are not included in the priority EDCA parameter set element as shown in FIG. 22 , then these parameters can be set to the same as the regular EDCA parameters for AC_BK as indicated in the EDCA parameter set element as shown in FIG. 22

[0190] 4.3.1.4. Examples of parameter settings

[0191] Tables 1A to 1C illustrate examples of regular / high / low priority EDCA / MU-EDCA parameter settings. Each AP and STA can set the EDCA and MU EDCA parameters as shown in the tables. It should be noted that some parameters can not be shown in this table.

[0192] When a STA starts contending for the channel for an AC, it preferably generates a random backoff count for an additional defer time before transmitting a packet for that AC, which is defined in IEEE 802.11. It should be recognized that the random backoff count must be greater than or equal to 1 (backoff slot) when generated, especially in the case of AIFSN = 1. That is, each time a STA contends for the channel for an AC, it must count down at least one backoff slot before accessing the channel. For example, the random backoff count can be drawn from a uniform distribution over the interval [1, CW+1] instead of [0, CW], where CW is the contention window size.

[0193] FIG. 23 An example embodiment 390 using different EDCA parameter settings is illustrated. The network topology is illustrated in FIG. 8 . The example AC used is AC_x, which in this example and the following examples represents any AC in EDCA.

[0194] During the regular period for AC_x, STA1 represents a STA affiliated with an MLD, while STA2 represents a single (non-MLD) STA. Station 392 can represent either STA1 or STA2, both of which have P capability. STA1 and STA2 in this example can also be replaced by an AP.

[0195] ​During the regular period 394 for AC_x, the station 392 can contend for the channel using the default EDCA parameters and obtain a TXOP for packet transmissions 398. For example, the backoff 396 (regular BO as shown in the figure) can be generated by the regular / default contention window for AC_x. The TXOP reservation should follow the constraints of the regular / default TXOP limits for AC_x.

[0196] During the prioritized period 400 for AC_x, the station 392 can contend 402 for the channel using the high priority EDCA parameters and obtain a TXOP for packet transmissions 404. For example, the backoff (HP BO as shown in the figure) can be generated by the contention window for the high priority EDCA parameters for AC_x. The TXOP reservation should follow the constraints of the TXOP limits for the high priority EDCA parameters for AC_x.

[0197] During the non-priority period 406 for AC_x, the station 392 can contend 408 for the channel using the low priority EDCA parameters and obtain a TXOP for packet transmissions 410. For example, the backoff (LH BO as shown in the figure) can be generated by the contention window for the low priority EDCA parameters for AC_x. The TXOP reservation should follow the constraints of the TXOP limits for the low priority EDCA parameters for AC_x.

[0198] FIG. 24 An example embodiment 430 is illustrated that disables channel contention for an AC using low priority EDCA parameter settings. The topology, STAs, and regular and prioritized periods shown are the same as for FIG. 23 the example embodiment 430.

[0199] However, during the non-priority period 432 for AC_x, if the station 392 sets the CWmin or CWmax for the low priority EDCA parameters for AC_x to a particular value, such as to the maximum value, then it can indicate that the AC_x for STA1 or STA2 does not contend for the channel. Alternatively, in an example embodiment, if the station 392 sets the CWmin and CWmax for the low priority EDCA parameters for AC_x to the same value, then it can also indicate that the AC_x for STA1 or STA2 does not contend for the channel.

[0200] FIG. 25 An example embodiment 450 is illustrated where a STA has a non-priority period after a prioritized period for an AC. The topology and STAs, and regular and prioritized periods are the same as in FIG. 23 the example embodiment 430.

[0201] However, looking to the right of the figure, a non-priority period 452 is seen before the LP-EDCA time for AC_x expires. Thus, at the end of the prioritized period for AC_x, the station 392 should set the LP-EDCA timer for AC_x and immediately start the non-priority period for AC_x. The non-priority period for AC_x is maintained until the LP-EDCA timer for AC_x counts down to an end value (e.g., zero) indicating expiration. Contention is shown using low priority backoff 454 and gaining the channel for transmission 456.

[0202] FIG. 26 An example embodiment 470 is shown in which the STA delays between two prioritized periods for AC. The STA and network topology are the same as shown in FIG. 23 to FIG. 25

[0203] A prioritized period for AC_x is shown 476 in which the station 392 can contend 478 for the channel using high priority EDCA parameters and gain a TXOP and perform prioritized packet transmission 480. The figure also indicates a minimum time 474 between two successive prioritized periods for AC_x. It will be noted that block 482 represents channel time between a prioritized period and a non-priority period. For example, a backoff (HP BO as shown) can be generated by the high priority contention window for AC_x. TXOP reservation should follow the constraints of the high priority TXOP limits for AC_x.

[0204] After the prioritized period for AC_x ends, the STA1 or STA2 can not need to immediately switch to the non-priority period for AC_x. The non-priority period for AC_x 484 can be scheduled at any time before the next prioritized period for AC_x 490 begins. When the non-priority period for AC_x begins, the station 392 sets the LP-EDCA timer for AC_x and counts down in contention 486 for the channel. In this example, the channel is gained and packet transmission 488 is performed. When the LP-EDCA timer for AC_x 484 counts down to zero, the non-priority period ends.

[0205] Another prioritized period 490 can then begin with high priority backoff 492 and prioritized packet transmission 494.

[0206] FIG. 27 An example embodiment 510 is shown in which the STA uses different EDCA parameters for non-priority packets during a prioritized period. The STA and network topology are the same as shown in FIG. 23 to FIG. 25

[0207] ​​When the STA transmits a packet that is not a prioritized packet during the prioritized period, it can also use the regular or LP EDCA parameters for channel contention.

[0208] During the regular period 514 for AC_x, the station 392 can use the default EDCA parameters to contend 516 for the channel and obtain a TXOP for packet transmission 518. For example, the backoff (regular BO as shown in the figure) can be generated by the regular / default contention window for AC_x. The TXOP reservation should follow the constraints of the regular / default TXOP limits for AC_x.

[0209] Then during the prioritized period 520 for AC_x, the station 392 can use the high priority EDCA parameters 522 to contend for the channel to obtain a TXOP for transmission 524 of prioritized packets. For example, the backoff (HP BO as shown in the figure) can be generated by the contention window of the high priority EDCA parameters for AC_x. The TXOP reservation should follow the constraints of the TXOP limits of the high priority EDCA parameters for AC_x.

[0210] During the same prioritized period, the STA has a packet to transmit that is not a prioritized packet. The station 392 can use the low priority EDCA parameters to contend 526 for the channel and obtain a TXOP for regular packet transmission 528. For example, the backoff (LH BO as shown in the figure) can be generated by the low priority contention window for AC_x. The TXOP reservation should follow the constraints of the low priority TXOP limits for AC_x. The station 392 can also use the regular EDCA parameters to contend 526 for the channel and obtain a TXOP for regular packet transmission 528.

[0211] FIG. 28 An example embodiment 530 is illustrated where a STA sets different period modes for multiple ACs at the same time. The network topology is as shown in FIG. 8 The example ACs used are AC_x and AC_y, which represent any AC in EDCA in these examples. STA 1 has P capability, and the depicted procedure remains the same if STA 1 is replaced by an AP. It will also be noted that the station 532 can also be STA 2, which is the same as in the previous example.

[0212] STA1 is shown to transmit and receive on link 1. STA1 can set a regular duration 534 for both AC_x and AC_y at the same time. During the regular period, STA1 can use the default EDCA parameters to contend for the channel and gain TXOP. For example, the regular BO (backoff) for AC_y 538 and AC_x 536 shown in the figure are generated by the regular / default contention window of AC_y and AC_x, respectively. When AC_x and AC_y reserve TXOP, their TXOP duration should follow the constraints of the regular / default TXOP limits of AC_x and AC_y, respectively. In the figure, AC_x is shown to gain the channel first and perform packet transmission 540, after which AC_y gains the channel and performs packet transmission 542.

[0213] STA1 can also set a period 544 that includes both a prioritized period for AC_x and a non-priority period for AC_y. During this time, STA1 contends 546 for TXOP using the high priority EDCA parameters of AC_x and contends 548 for TXOP using the low priority EDCA parameters of AC_y. As shown, the LP BO of AC_y represents the backoff created by the contention window of the low priority EDCA parameters of AC_y. In the example figure, AC_x gains the channel first and performs prioritized packet transmission 550, after which (one or more) packet transmission(s) 552 are performed for AC_y.

[0214] The TXOP duration of AC_y should not last longer than the TXOP limit in the low priority EDCA parameters of AC_y. The HP BO of AC_x represents the backoff created by the contention window of the high priority EDCA parameters of AC_x. The TXOP duration of AC_x should not last longer than the TXOP limit in the high priority EDCA parameters of AC_x.

[0215] It should be noted that in such examples, STA 532 can not have to schedule a non-priority period for AC_x after the prioritized period for AC_x.

[0216] FIG. 29 An example embodiment 570 is illustrated in which a STA uses the priority EDCA parameters of multiple ACs during a prioritized period. The network topology is shown as in FIG. 8 It should be noted that AC_x and AC_y are used to represent any AC in EDCA, and AC_x and AC_y can be the same AC. STA1 572 and STA2 574 have P capability and can also be replaced by APs. STA1 and STA2 can not be associated with the same AP.

[0217] During the regular period, STAl and STA2 can contend 578, 580 for the channel and gain TXOP using the default EDCA parameters. For example, the regular BO (backoff) for AC_y and AC_x shown in the figure are generated by the regular / default contention window for AC_y and AC_x, respectively. When AC_x and AC_y reserve TXOP, their TXOP durations should follow the constraints of the regular / default TXOP limits for AC_x and AC_y, respectively. In the figure, STAl for AC_x first gains the channel and performs packet(s) transmission 582, then STA2 for AC_y performs packet(s) transmission 584.

[0218] A period is then entered 586 where there is a prioritized period for AC_x at STAl and a non-priority period for AC_y at STA2. During this time, STAl performs backoff 588 using the high priority EDCA parameters for AC_x, and STA2 contends for the channel under backoff 590 using the low priority EDCA parameters for AC_y. As shown, the LP BO for AC_y represents the backoff created at STA2 by the contention window for the low priority EDCA parameters for AC_y. The TXOP duration for AC_y should not be longer than the TXOP limit in the low priority EDCA parameters for AC_y. The HP BO for AC_x represents the backoff created at STAl by the contention window for the high priority EDCA parameters for AC_x. The TXOP duration for AC_x should not be longer than the TXOP limit in the high priority EDCA parameters for AC_x. The figure depicts that STAl first gains the channel for AC_x and performs prioritized packet(s) transmission 592, after which STA2 gains the channel for AC_y and packet transmission 594.

[0219] FIG. 30 An example embodiment 610 is illustrated where one AC of a STA uses the backoff slot duration of the LP EDCA parameters during a prioritized period. The network topology is the same as shown in FIG. 8 The notation AC_i and AC_j represents any AC in the EDCA. During the regular period for AC_i and AC_j, STAl 612 has P capability. STAl can also be replaced by any type of STA without changing the example.

[0220] During the regular period 614, the arbitration interframe space (AIFS) is depicted as AIFS[i] 616 and AIFS[j] 618. When contending for the channel for any AC, it is seen that STAl uses the default backoff slot duration. The duration of the AIFS for an AC can be calculated by the AIFSN number for that AC in that period and the backoff slot duration.

[0221] See entering period 620, which includes a prioritized period for AC_i (which ends before the HP-EDCA timer expires) and is a non-priority period for AC_j. During the non-priority period for AC_j, STAl utilizes the backoff slot duration found in the low-priority EDCA parameters to contend for the channel to gain a TXOP for AC_j. For example, the duration of each of backoff slots 7 and 6 (622) is twice the duration of a regular backoff slot as seen in slots 8 through 12 for AC_j, and used by AC_i 624. In view of this disparity, AC_i has a higher probability of gaining the channel more easily than AC_j. STAl gains the channel and transmits its prioritized packet 628, while AC_j finds the idle channel assessment (CCA) busy 626.

[0222] FIG. 31 An example embodiment 630 is illustrated in which one of the STAs uses the backoff slot duration of the LP EDCA parameters during the prioritized period. The network topology is as shown in FIG. 8 STA1 632 and STA2 634 with P-capability are depicted here. STAl can also be replaced by any type of STA. Again, note that AC_i and AC_j can represent any AC in EDCA. AC_i and AC_j can be the same AC.

[0223] During the regular period for AC_i and AC_j 636, STAl or STA2 can use the default backoff slot duration to contend 642, 644 for the channel and gain a TXOP. See AIFS[i] 638 and AIFS[j] 640 before backoff.

[0224] A new period is then entered 646, which is a prioritized period for AC_i for STA2 (which ends before the HP-EDCA timer expires), but is a non-priority period for AC_j for STAl. During the non-priority period for AC_j, STAl should use the backoff slot duration in the low-priority EDCA parameters to contend 647 for the channel and gain a TXOP for AC_j. For example, the duration of each of backoff slots 7 and 6 (647) is twice the duration of regular backoff slots 8 through 12 for AC_j. Thus, AC_i has a higher probability of gaining channel access more quickly than AC_j. During the prioritized period for AC_i for STA2, the backoff slot duration can be set the same as in the regular period. In the figure, STA2 gains channel access for AC_i after backoff 648 and transmits a prioritized packet 652, while STAl finds the CCA busy 650 after backoff.

[0225] FIG. 32 An example embodiment 670 is illustrated in which a STA uses the MU EDCA parameters of the priority EDCA parameters during a prioritized period. The network topology is as shown in FIG. 8 As shown in the middle, AP1 672, STA1 674, STA2 676, and STA3 678 are shown, all of which have P capability. Again, the notation AC_x and AC_y can represent any AC in EDCA.

[0226] A regular period 680 is shown in which AP1 performs backoff 682 and gains the channel for a trigger frame (TF) 684. In response to the TF, each station (STA1, STA2, and STA3) performs an uplink transmission, sending their respective data 686, 688, and 690 to AP1, which responds with a block acknowledgement (BA) 692.

[0227] STA1, STA2, and STA3 can then use their default MU EDCA parameters to contend for the channel after the trigger-based uplink transmission under IEEE 802.11 has completed.

[0228] A period 720 is entered, which is a prioritized period for STA1's AC_x and STA2's AC_y, but a non-priority period for STA3's AC_y. AP1 performs backoff (BO) 700, gains the channel, and sends a trigger frame 702.

[0229] During the prioritized period for AC_x at STA1, a data frame 704 is sent in response to the TF 702, after which the AP sends a BA 710. STA1 then starts counting down the MU EDCA timer for AC_x using the MU EDCA parameters of AC_x in the high priority (HP) MU EDCA parameters 712. The EDCA timer for AC_x is also set by the high priority MU EDCA parameters of AC_x.

[0230] During the prioritized period for AC_y at STA2, a data frame 706 is sent in response to the TF 702, after which the AP sends a BA 710. STA2 then starts counting down the MU EDCA timer for AC_y using the MU EDCA parameters of AC_y in the high priority (HP) MU EDCA parameters 714. The EDCA timer for AC_y is also set by the high priority MU EDCA parameters of AC_y.

[0231] During the non-priority period for AC_y at STA3, data frame 708 is sent in response to TF 702, after which the AP sends BA 710. STA3 then starts counting down the MU EDCA timer for AC_y using the MU EDCA parameters for AC_y in the low priority (LP) MU EDCA parameters 716. The MU EDCA timer for AC_y is also set by the low priority EDCA parameters for AC_y. The remaining time of the period is represented by 718.

[0232] FIG. 33 An example embodiment 730 is illustrated in which a STA switches to using the low priority MU EDCA parameters during a prioritized period. The network topology, symbols, and stations are the same as for FIG. 32

[0233] This figure depicts the same regular period actions on data frames 704, 706, and 708 from STAl, STA2, and STA3, respectively.

[0234] However, in this figure, after STAl sends data frame 704 for AC_x, it starts counting down the MU EDCA timer for AC_x. If STAl has more prioritized traffic to transmit, then it is seen using the MU EDCA parameters for AC_x in the high priority (HP) MU EDCA parameters 732 during the time it is counting down the MU EDCA timer for AC_x. The MU EDCA timer for AC_x is also set by the high priority MU EDCA parameters for AC_x.

[0235] During the prioritized period for AC_x at STA2, after sending data frame 706, STA2 starts counting down the MU EDCA timer for AC_x. If STA2 does not have any more prioritized traffic to transmit, then it can use the MU EDCA parameters for AC_x in the low priority (LP) MU EDCA parameters 734 during the time it is counting down the MU EDCA timer for AC_x. The MU EDCA timer for AC_x is also set by the low priority MU EDCA parameters for AC_x. It should be noted that STA2 can also use the regular MU EDCA parameters instead of the low priority MU EDCA parameters.

[0236] ​During the non-priority period for AC_y at STA3, after transmitting data frame 708, STA3 uses the MU EDCA parameters for AC_y in the low priority (LP) EDCA parameters 736 during its countdown of the EDCA timer for AC_y. The EDCA timer for AC_y is also set by the MU EDCA parameters for AC_y in the low priority EDCA parameters. The remaining time of the period is 738.

[0237] FIG. 34 An example embodiment 750 is illustrated where a STA uses multiple EDCA functions (EDCAFs) for a single packet transmission. The network topology is the same as in FIG. 8 where STA1 with P capability has AC_x 752 and AC_y 754, which can represent any AC in EDCA.

[0238] STA1 uses the EDCAFs for AC_x and AC_y to contend for the channel to transmit packet 1. STA1 performs backoff for AC_y 756 and sees backoff for AC_x 758 start subsequently. After the backoff, it first gets TXOP for AC_x and then it transmits initial transmission of packet 1 760. However, the initial transmission of packet 1 fails and STA1 starts backoff for AC_x 762.

[0239] During this time, it sees that AC_y first gets TXOP and retransmits packet 1 764. If the first retransmission of packet 1 fails and AC_x gets the next TXOP, it retransmits packet 1 for the second time 766.

[0240] FIG. 35 An example embodiment 770 is illustrated where a STA uses multiple EDCAFs to transmit packets from one AC. The network topology and STA1 with AC_x and AC_y are the same as in FIG. 34 It should be noted that this example case can only occur when AC_x has higher priority than AC_y.

[0241] STA1 uses the EDCAFs for AC_x and AC_y to contend for the channel to transmit packets from AC_x. As shown, backoff for AC_x 774 starts when there can not be any packets to transmit in AC_y. STA1 first gets TXOP for AC_x and transmits packet 776. Next, after its backoff 772, AC_y gets TXOP and it transmits packets from AC_x only 780. At this time AC_x is performing backoff 778 and if AC_x gets the next TXOP, it continues to transmit packets from AC_x 782.

[0242] It is possible that if there are no packets from AC_y to transmit, then the EDCAF of AC_y starts contending for the channel to transmit packets from AC_x. If there are packets from AC_x to transmit, then the EDCAF of AC_y starts contending for the channel to transmit packets from AC_x.

[0243] FIG. 36A and FIG. 36B Figure illustrates an example embodiment 790 where a STA transmits packets from one AC using priority EDCA and multiple EDCAFs. The network topology is as shown in FIG. 8 and AC_x and AC_y can again represent any AC in EDCA.

[0244] In this example, STA1 is contending for the channel using the EDCAFs of AC_x and AC_y. It should be recognized that STA1 can also contend for the channel using the EDCAFs of more ACs.

[0245] During the regular period of AC_x and AC_y as seen in FIG. 36A , the EDCAFs of AC_x and AC_y perform their regular backoff 794, 796 to separately contend for the channel and gain TXOP for packets from AC_x and AC_y, respectively. The figure shows a packet 798 sent from AC_x, then after the backoff for AC_y, it gains TXOP and sends its packet 800.

[0246] During the prioritized period 801 for AC_x and AC_y as seen in FIG. 36B , there are only prioritized packets from AC_x. STA1 contends for the channel using the EDCAFs of AC_x and AC_y to transmit packets from AC_x. The backoff (BO) 802 and 804 for AC_x and AC_y are created by using high priority (HP) EDCA parameters. As shown, after the backoff, AC_x first gains TXOP and it transmits a packet 806 from AC_x. Next, AC_y gains TXOP and it transmits a packet 808 from AC_x only.

[0247] For the non-priority period 809 for AC_x and AC_y, the EDCAFs of AC_x and AC_y separately perform backoff 810 and 812 to contend for the channel and gain TXOP for packets from AC_x and AC_y, respectively. In this case, the backoff (BO) for AC_x and AC_y are created by using low priority (LP) EDCA parameters. It is seen that STA1 transmits a packet 814 from AC_x and after BO 812, it transmits a packet 816 from AC_y.

[0248] FIG. 37A andFIG. 37B Figure illustrates an example embodiment 830 where a STA transmits packets from one AC using priority EDCA and multiple EDCAFs. This network topology and STAs are the same as in FIG. 36A and FIG. 36B Again, note that it is also possible for STA1 to use the EDCAFs of more ACs to contend for the channel.

[0249] FIG. 37A The regular period seen in FIG. 36A is the same as seen in

[0250] The next period 832 seen in FIG. 37B is a prioritized period for AC_x and a non-priority period for AC_y while only prioritized packets from AC_x are present. STA1 contends for the channel using the EDCAFs of AC_x and AC_y to transmit packets from AC_X. The backoffs (BO) 834 and 836 for AC_x and AC_y are created by using the high priority (HP) EDCA parameters and the low priority (LP) EDCA parameters, respectively. As shown, the backoff for AC_x gets the TXOP first and then transmits packets 838 from AC_x. Next, AC_y gets the TXOP and it transmits packets 840 from AC_x only.

[0251] The next period 842 is a non-priority period for AC_x. The EDCAFs of AC_x and AC_y perform their backoffs 844 and 846 separately to contend for the channel and get the TXOP for packets from AC_x and AC_y. The backoffs (BO) for AC_x and AC_y (as shown) are created by using the low priority (LP) EDCA parameters for AC_x and the regular EDCA parameters for AC_y. STA1 gets the TXOP for AC_x first and transmits packets 848, then after the regular backoff 846 for AC_y, it transmits packets 850 from AC_y.

[0252] Note that the non-priority period for AC_y can be any type of period.

[0253] FIG. 38 Figure illustrates an example embodiment 870 of using different AIFS during the backoff process, such as in the case where the backoff process spans different periods of EDCA parameter settings. For example, consider an ongoing backoff process where the STA can continue the countdown process using different AIFS. The AIFS can be determined by the EDCA parameter settings at the time the STA continues the backoff. The network topology is as in FIG. 8The figure depicts operation during the regular period 874 for AC_x on a P-capable station (e.g., STA1 or STA2) 392. STA1 / STA2 represents a P-capable STA that is either affiliated with an MLD or not. STA1 or STA2 can also be replaced by an AP.

[0254] During the regular period 874 for AC_x, STA1 or STA2 invokes the backoff procedure 882 and starts contending 880 for the channel for AC_x. The backoff can set the backoff counter for AC_x using the default EDCA parameters for AC_x. It can then start counting down the backoff 886 using the AIFSN 884 in the default EDCA parameters for AC_x.

[0255] The backoff counter does not count down to zero during the regular period and it is paused by a period of CCA busy 888 that spans the regular period 874 for AC_x and enters the prioritized period 876 for AC_x. The STA 890, where the AIFSN 892 in the high priority EDCA parameters for AC_x, continues counting down the backoff 894 for AC_x during the prioritized period for AC_x.

[0256] If the backoff counter does not reach zero in the prioritized period 876 for AC_x, such as because of CCA busy 896, then the station can continue 898 counting down the backoff during the non-priority period 878 for AC_x. Since there was CCA busy during the prioritized period for AC_x, the STA can continue the backoff counting 902 process using the AIFSN 900 in the low priority EDCA parameters for AC_x after the CCA busy. The STA is then seen to perform its packet transmission 904.

[0257] 5. General Embodiment

[0258] Embodiments of the present technology can be described herein with reference to flowchart illustrations of methods and systems according to embodiments of the present technology, and / or can also be implemented as processes, algorithms, steps, operations, formulas, or other computational depictions of a computer program product. In this regard, each block of the flowchart illustrations of the methods, combinations of blocks of the flowchart illustrations, and any processes, algorithms, steps, operations, formulas, or computational depictions can be implemented by various means, such as hardware, firmware, and / or software including one or more computer program instructions embodied in computer-readable program code. As will be realized, any of the computer program instructions can be executed on one or more computer processors, including without limitation a general purpose computer or special purpose computer, or other programmable processing apparatus to produce a machine, such that the computer program instructions which execute on the computer processor(s) or other programmable processing apparatus create means for implementing the functions specified in the flowchart block(s) or other computational depictions.

[0259] Accordingly, the blocks of the flowchart illustrations described herein, and the processes, algorithms, steps, operations, formulas, or computational depictions supporting same, support combinations of the means for performing the specified functions, combinations of the steps for performing the specified functions, and computer program instructions (such as embodied in computer-readable program code logic means) for performing the specified functions. It will also be understood that each block of the flowchart illustrations described herein, and any processes, algorithms, steps, operations, formulas, or computational depictions thereof, and combinations thereof, can be implemented by a special purpose computer system or a combination of special purpose hardware and computer-readable program code that performs the specified functions or steps.

[0260] Further, these computer program instructions such as embodied in computer-readable program code, can also be stored in one or more computer-readable memory or memory devices that can direct a computer processor or other programmable processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory or memory devices produce an article of manufacture including instruction means which implement the function specified in the block(s) of the flowchart(s). The computer program instructions can also be executed by a computer processor or other programmable processing apparatus to cause a series of operational steps to be performed on the computer processor or other programmable processing apparatus to produce a computer-implemented process such that the instructions which execute on the computer processor or other programmable processing apparatus provide steps for implementing the functions specified in the block(s) of the flowchart(s), the process(es), the algorithm(s), the step(s), the operation(s), the formula(s), or the computational depiction(s).

[0261] It will also be appreciated that the term "programmed" or "programmable" as used herein refers to one or more instructions that can be executed by one or more computer processors to perform one or more functions as described herein. The instructions can be implemented as software, firmware, or a combination of software and firmware. The instructions can be stored locally to the device in non-transitory media, or can be stored remotely, such as on a server, or can store all or part of the instructions locally and remotely. Instructions stored remotely can be downloaded (pushed) to the device by user initiation or automatically based on one or more factors.

[0262] It will also be appreciated that the terms processor, hardware processor, computer processor, central processing unit (CPU), and computer are used synonymously herein to mean a device capable of executing instructions and communicating with input / output interfaces and / or peripheral devices, and that the terms processor, hardware processor, computer processor, CPU, and computer are intended to include single or multiple devices, single core and multicore devices, and variations thereof.

[0263] From the description herein, it will be appreciated that the disclosure encompasses a variety of implementations of the technology, including but not limited to the following:

[0264] An apparatus for wireless communication in a network, the apparatus comprising: (a) wireless communication circuitry to wirelessly communicate with other wireless stations (STAs) as an access point (AP) or a non-AP STA over a channel on a wireless local area network (WLAN) in which carrier sense multiple access / collision avoidance (CSMA / CA) is applied; (b) a processor coupled to the wireless communication circuitry to operate as a STA on the WLAN; (c) a non-transitory memory storing instructions executable by the processor to communicate with the other STAs; and (d) wherein the instructions, when executed by the processor, perform one or more steps comprising:

[0265] (d)(i) configuring EDCA functionality to operate with a single EDCA or multi-user (MU) EDCA operating parameter of a plurality of sets providing a range of priority levels, wherein each set of operating parameters provides a different level of nominal access time for the STA to use at different time periods when contending for at least one of the channels; (d)(ii) utilizing a higher priority set of single EDCA or multi-user (MU) EDCA operating parameters when the STA needs to speed up channel access; and (d)(iii) utilizing a lower priority set of EDCA operating parameters when the STA needs to slow down channel access.

[0266] An apparatus for wireless communication in a network, the apparatus comprising: (a) wireless communication circuitry to wirelessly communicate with other wireless stations (STAs) as an access point (AP) or a non-AP STA over a channel on a wireless local area network (WLAN) in which carrier sense multiple access / collision avoidance (CSMA / CA) is applied; (b) a processor coupled to the wireless communication circuitry to operate as a STA on the WLAN; (c) a non-transitory memory storing instructions executable by the processor to communicate with the other STAs; and (d) wherein the instructions, when executed by the processor, perform one or more steps comprising:

[0267] (d)(i) configuring EDCA functionality to operate with a series of priority levels of single-EDCA or multi-user (MU) EDCA operating parameters in multiple sets, wherein each set of operating parameters provides a different level of nominal access time for the STA to use at different time periods when contending for at least one of the channels; (d)(ii) the multiple sets of single-EDCA or MU-EDCA operating parameters include a backoff slot duration parameter, thereby allowing for dynamic setting of backoff slot duration in response to changes between the multiple sets of single-EDCA or MU-EDCA operating parameters; (d)(iii) utilizing a higher priority set of single-EDCA or multi-user (MU) EDCA operating parameters when the STA needs to speed up channel access by shortening the nominal channel access time; (d)(iv) utilizing a lower priority set of EDCA operating parameters when the STA needs to slow down channel access to provide compensation for utilizing a higher priority set of EDCA operating parameters; (d)(v) wherein the STA is configured to simultaneously utilize single-EDCA or MU-EDCA operating parameters of different priority levels for backoff on different ACs; and (d)(vi) limiting the duration that the STA can continuously use a higher priority set of single-EDCA or MU-EDCA operating parameters for an access category (AC).

[0268] A method of wireless communication in a network, the apparatus comprising: (a) a wireless communication circuit having a processor configured to execute a protocol for a wireless station (STA) to communicate over a channel with other wireless stations (STAs) as APs or non-AP STAs on a wireless local area network (WLAN) in which carrier sense multiple access / collision avoidance (CSMA / CA) is applied; (b) configuring an EDCA function to operate by providing a plurality of sets of single-EDCA or multi-user (MU) EDCA operating parameters of a range of priority levels, wherein each set of operating parameters provides a different level of nominal access time for the STA to use at different time periods when contending for at least one of the channels; (c) utilizing a higher priority set of single-EDCA or multi-user (MU) EDCA operating parameters when the STA needs to speed up channel access; and (d) utilizing a lower priority set of EDCA operating parameters when the STA needs to slow down channel access.

[0269] A wireless communication apparatus performing transmission of packets in which CSMA / CA is applied, wherein a STA has one default set of EDCA parameters, comprising: (a) the STA having a plurality of sets of EDCA parameters and using them at different time periods; (b) the STA using a high priority set of EDCA parameters when the STA needs to speed up channel access compared to the default set; and (c) the STA using a low priority set of EDCA parameters when the STA needs to slow down channel access compared to the default set.

[0270] The apparatus or method of any preceding embodiment, wherein the higher priority set of single-EDCA or multi-user (MU) EDCA operating parameters shortens the nominal channel access time for prioritized traffic transmission.

[0271] The apparatus or method of any preceding embodiment, wherein the instructions, when executed by the processor, further perform steps comprising: the STA switching to a lower priority set of single-EDCA or MU-EDCA operating parameters to provide compensation for utilizing the higher priority set of EDCA operating parameters.

[0272] The apparatus or method of any preceding embodiment, wherein the instructions, when executed by the processor, further perform steps comprising: limiting the duration of time that the STA can continuously use the higher priority set of single-EDCA or MU-EDCA operating parameters for an access category (AC).

[0273] The apparatus or method of any preceding embodiment, wherein the plurality of sets of operating parameters comprises a regular set of operating parameters having a default priority, a high priority (HP) set of operating parameters, and a low priority (LP) set of operating parameters.

[0274] The apparatus or method of any preceding embodiment, wherein the set of regular operating parameters is loaded to match the default single EDCA and multi-user (MU) EDCA parameter settings of the IEEE 802.1 lax protocol.

[0275] The apparatus or method of any preceding embodiment, wherein the multiple sets of single EDCA or MU-EDCA operating parameters are set from received communications associated with the STA.

[0276] The apparatus or method of any preceding embodiment, wherein the multiple sets of single EDCA or MU-EDCA operating parameters are set by communications from an AP to which the STA is associated using a beacon frame, a probe response frame, or an (re)association response frame.

[0277] The apparatus or method of any preceding embodiment, wherein the instructions, when executed by the processor, further perform steps comprising: the multiple sets of single EDCA or MU-EDCA operating parameters include a backoff slot duration parameter, thereby allowing backoff slot duration to be set dynamically in response to changes between the multiple sets of single EDCA or MU-EDCA operating parameters.

[0278] The apparatus or method of any preceding embodiment, wherein the multiple sets of single EDCA or MU-EDCA operating parameters are set in response to receiving a frame in a communication.

[0279] The apparatus or method of any preceding embodiment, wherein the instructions, when executed by the processor, further perform steps comprising: the STA uses single EDCA or MU-EDCA operating parameters of different priority levels simultaneously for backoff on different ACs.

[0280] The apparatus or method of any preceding embodiment, wherein the instructions, when executed by the processor, further perform steps comprising: the STA operating as an AP utilizes one set of single EDCA or MU-EDCA operating parameters during periods in which it contends for the channel with multiple EDCA functions and gains a TXOP for transmission of packets from a single AC.

[0281] The apparatus or method of any preceding embodiment, wherein the instructions, when executed by the processor, further perform steps comprising: forcing the STA that has utilized a higher priority set of single EDCA or MU-EDCA operating parameters to use a lower priority set of operating parameters for a period of time to compensate for its previous higher priority usage.

[0282] The apparatus or method of any preceding embodiment, wherein a STA with multiple sets of EDCA parameters can be set by its associated AP via a beacon frame.

[0283] The apparatus or method of any preceding embodiment, wherein the STA with multiple sets of EDCA parameters can be set by the AP via a probe response frame.

[0284] The apparatus or method of any preceding embodiment, wherein the STA with multiple sets of EDCA parameters can be set by its associated AP via an (re)association response frame.

[0285] The apparatus or method of any preceding embodiment, wherein the STA with multiple sets of EDCA parameters can dynamically set the backoff slot duration.

[0286] The apparatus or method of any preceding embodiment, wherein the STA with multiple sets of EDCA parameters can be set by frames transmitted over other links.

[0287] The apparatus or method of any preceding embodiment, wherein the STA with multiple sets of EDCA parameters can use a low priority set of EDCA parameters of one AC and a high priority set of EDCA and MU EDCA parameters of another AC simultaneously.

[0288] The apparatus or method of any preceding embodiment, wherein a STA using a high priority set of EDCA parameters can be forced to use a low priority set of EDCA parameters for a period of time after it uses the high priority set of EDCA parameters.

[0289] The apparatus or method of any preceding embodiment, wherein an AP using one set of EDCA parameters during a period of time can use multiple EDCAFs to contend for the channel and gain TXOP for transmission of packets from only one AC.

[0290] As used herein, the term “implementation” is intended to encompass, without limitation, embodiments, examples, or other forms of practice of the technology described herein.

[0291] As used herein, the singular terms “a,” “an,” and “the” can include plural referents unless the context clearly dictates otherwise. References to objects with the meaning of “one of’ or “one” does not imply that only a single object is intended to be invoked, but rather “one or more.”

[0292] The phrase construction “A, B, and / or C” in this disclosure describes situations in which A, B, or C, or any combination of items A, B, and C can be present. Phrase constructions such as “at least one” followed by a listing of elements indicate that there is at least one of the listed elements present, including any possible combination of the listed elements (as applicable).

[0293] Reference within this disclosure to “an embodiment,” “at least one embodiment,” or similar language indicates that a particular feature, structure, or characteristic described in connection with the described embodiment is included in at least one embodiment of the present disclosure. The various

[0294] 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.

[0295] Relative terms such as first and second, top and bottom, and the like can be used herein to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions.

[0296] The terms “comprises,” “comprising,” “has,” “having,” “includes,” “including,” “contains,” “containing,” “includes,” “including,” or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises, has, includes, or contains a list of elements does not include only those elements but can also include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without more restriction, no element preceding “comprises...”, “has...”, “includes...”, “packs...” excludes the presence of additional identical elements in a process, method, article, or apparatus that includes the element.

[0297] As used herein, the terms “approximately,” “about,” “substantially,” “essentially,” and “around” or any variation thereof, are used to describe and account for small variations. When used in connection with an event or circumstance, the term can refer to instances in which the event or circumstance occurs exactly, as well as instances in which the event or circumstance occurs to a similar instance. When used in connection with a numerical value, the term can refer to a range of variation of less than or equal to ±10% of the numerical value, such as less than or equal to ±5%, less than or equal to ±4%, less than or equal to ±3%, less than or equal to ±2%, less than or equal to ±1%, less than or equal to ±0.5%, less than or equal to ±0.1%, or less than or equal to ±0.05%. For example, “substantially” aligned can refer to a range of angular variation of less than or equal to ±10°, such as less than or equal to ±5°, less than or equal to ±4°, less than or equal to ±3°, less than or equal to ±2°, less than or equal to ±1°, less than or equal to ±0.5°, less than or equal to ±0.1°, or less than or equal to ±0.05°.

[0298] Further, amounts, ratios, and other numerical values can sometimes be presented herein in a range format. It is to be understood that such range format is used for convenience and brevity and that one or both of the numbers defining the range is intended to be significant. Therefore, this description includes that language limiting the scope of at least one claim to the exact scope of the ranges set forth. For example, a ratio ranging from 1 to 200 is intended to include "1 to 200" as well as individual ratios such as 2, 3, 4, 10, 20, 30, 40, 50, 60, 70, 80, 90, 100, 1 10, 120, 130, 140, 150, 160, 170, 180, 190, and 200.

[0299] The term "coupled" as used herein is defined as connected, although not necessarily directly, and not necessarily mechanically. A device or structure that is "configured" in a certain way is configured in at least that way, but can also be configured in ways that are not listed.

[0300] The benefits, advantages, solutions to problems, and any one or more elements of any of the aspects or examples that can effect any benefit, advantage, or solution, should not be construed as being critical, essential, or

[0301] Further, in the foregoing disclosure, various features can be grouped together in various embodiments. This should not be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Inventive subject matter can lie in fewer than all features of a single disclosed embodiment.

[0302] The abstract of the disclosure is provided 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 the meaning of the claims.

[0303] It will be recognized that the practices of some jurisdictions can require that one or more parts of the disclosure be deleted from the application after it is submitted. Accordingly, readers should seek to determine the original content of the application from the application as submitted. Any deletion of content from the disclosure should not be interpreted as a concession that any subject matter is not claimed in any application.

[0304] The following claims are hereby incorporated into the disclosure, each claim as a separate claimed subject matter.

[0305] While the description herein contains many specifics, these should not be construed as limiting the scope of the disclosure but as merely providing illustrations of some of the presently preferred embodiments. Thus, it will be appreciated that the scope of the disclosure encompasses other embodiments not expressly shown or described herein.

[0306] All structural and functional equivalents to the elements of the disclosed embodiments with known functions described herein are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, none of the elements of the disclosure are intended to be dedications to the public regardless of whether the element is explicitly recited in the claims. No claim element is to be construed as a “means plus function” element, unless the element is expressly recited using the phrase “means for.” No claim element is to be construed as a “step plus function” element, unless the element is expressly recited using the phrase “step for.”

[0307] Table 1A Example of regular EDCA / MU EDCA parameter settings

[0308]

[0309] “BO” - backoff slot duration in uS; “TXOP” - TXOP timer in mS

[0310] Table 1B Example of high priority EDCA / MU EDCA parameter settings

[0311]

[0312] “BO” - backoff slot duration in uS; “TXOP” - TXOP timer in mS

[0313] Table 1C Example of low priority EDCA / MU EDCA parameter settings

[0314]

[0315] “BO” - backoff slot duration in uS; “TXOP” - TXOP timer in mS

Claims

1. An apparatus for wireless communication in a network, the apparatus comprising: (a) A wireless communication circuit, acting as a wireless station (STA), operating as an access point (AP) or a non-AP STA, is configured to wirelessly communicate with other wireless stations (STAs) acting as APs or non-AP STAs via a channel on a wireless local area network (WLAN) in which carrier sense multiple access / collision avoidance (CSMA / CA) is applied. (b) A processor coupled to the wireless communication circuitry operating as a STA on a WLAN; (c) Non-transitory memory storing instructions that can be executed by the processor to communicate with other STAs; and (d) The instructions described, when executed by the processor, include the following steps: (i) Configure the Enhanced Distributed Channel Access (EDCA) function to operate by providing multiple sets of single EDCA or multi-user (MU) EDCA operation parameters of a series of priority levels, wherein each set of operation parameters provides a different level of nominal access time for STAs to use at different time periods when competing for at least one of the channels, wherein the multiple sets of single EDCA or MU-EDCA operation parameters include a backoff slot duration parameter, thereby allowing the backoff slot duration to be dynamically set in response to changes between the multiple sets of single EDCA or MU-EDCA operation parameters, and wherein the STA is configured to use single EDCA or MU-EDCA operation parameters of different priority levels simultaneously for backoff on different access classes (ACs); (ii) When the STA needs accelerated channel access, utilize single EDCA or multiple users. (MU)EDCA operation parameters are a higher priority set; as well as (iii) When the STA needs to slow down channel access, it utilizes the lower priority set of EDCA operation parameters. The instructions, when executed by the processor, also perform the following steps: limiting the duration for which the STA can continuously use a higher-priority single EDCA or MU-EDCA set of operating parameters for the access class (AC).

2. The apparatus of claim 1, wherein the nominal channel access time is shortened by using a higher priority set of single EDCA or multi-user (MU) EDCA operation parameters for prioritized traffic transmission.

3. The apparatus of claim 1, wherein the instructions, when executed by the processor, further perform the step of: the STA switching to a lower priority set of single EDCA or MU-EDCA operation parameters to provide compensation for utilizing a higher priority set of EDCA operation parameters.

4. The apparatus of claim 1, wherein the plurality of sets of operating parameters includes a set of regular operating parameters with default priority, a set of high-priority (HP) operating parameters, and a set of low-priority (LP) operating parameters.

5. The apparatus of claim 4, wherein the set of conventional operating parameters is loaded to match the default single EDCA and multi-user (MU) EDCA parameter settings of the IEEE 802.11ax protocol.

6. The apparatus of claim 1, wherein the plurality of sets of single EDCA or MU-EDCA operating parameters are set by communication received from the AP associated with the STA.

7. The apparatus of claim 1, wherein the plurality of sets of single EDCA or MU-EDCA operating parameters are set by communication from the AP associated with the STA via beacon frames, probe response frames, association response frames, or reassociation response frames.

8. The apparatus of claim 1, wherein the plurality of sets of single EDCA or MU-EDCA operating parameters can be set in response to receiving a frame in communication.

9. The apparatus of claim 1, wherein the instructions, when executed by the processor, further perform the step of: forcing the STA, which has already utilized a higher priority set of single EDCA or MU-EDCA operating parameters, to use a lower priority set of operating parameters for a period of time to compensate for its previous higher priority usage.

10. An apparatus for wireless communication in a network, the apparatus comprising: (a) A wireless communication circuit, acting as a wireless station (STA), operating as an access point (AP) or a non-AP STA, is configured to wirelessly communicate with other wireless stations (STAs) acting as APs or non-AP STAs via a channel on a wireless local area network (WLAN) in which carrier sense multiple access / collision avoidance (CSMA / CA) is applied. (b) A processor coupled to the wireless communication circuitry operating as a STA on a WLAN; (c) Non-transitory memory storing instructions that can be executed by the processor to communicate with other STAs; and (d) The instruction, when executed by the processor, performs one or more of the following steps: (i) Configure the Enhanced Distributed Channel Access (EDCA) function to operate by providing multiple sets of single EDCA or multi-user (MU) EDCA operation parameters with a series of priority levels, wherein each set of operation parameters provides a different level of nominal access time for STAs to use at different time periods when competing for at least one of the channels; (ii) The plurality of sets of single EDCA or MU-EDCA operating parameters include a backoff slot duration parameter, thereby allowing the backoff slot duration to be dynamically set in response to changes among the plurality of sets of single EDCA or MU-EDCA operating parameters. (iii) When the STA needs to accelerate channel access by shortening the nominal channel access time, it utilizes the higher priority set of single EDCA or multi-user (MU) EDCA operation parameters. (iv) When the STA needs to slow down channel access to provide compensation for the higher priority set of EDCA operating parameters, the lower priority set of EDCA operating parameters is used. (v) wherein the STA is configured to simultaneously utilize single EDCA or MU-EDCA operating parameters of different priority levels for backoff on different access classes (ACs); and (vi) Limit the duration for which the STA can continuously use a higher priority single EDCA or MU-EDCA operation parameter set for the access class (AC).

11. The apparatus of claim 10, wherein the plurality of sets of operating parameters includes a set of regular operating parameters with default priority, a set of high-priority (HP) operating parameters, and a set of low-priority (LP) operating parameters.

12. The apparatus of claim 11, wherein the set of conventional operating parameters is loaded to match the default single EDCA and multi-user (MU) EDCA parameter settings of the IEEE 802.11ax protocol.

13. The apparatus of claim 10, wherein the plurality of sets of single EDCA or MU-EDCA operating parameters are set by communication received from the AP associated with the STA.

14. The apparatus of claim 10, wherein the plurality of sets of single EDCA or MU-EDCA operating parameters are set by communication from the AP associated with the STA via beacon frames, probe response frames, association response frames, or reassociation response frames.

15. The apparatus of claim 10, wherein the plurality of sets of single EDCA or MU-EDCA operating parameters can be set in response to receiving a frame in communication.

16. A method for conducting wireless communication in a network, the method comprising: (a) A wireless communication circuit having a processor configured to execute a protocol for a wireless station (STA) to communicate via a channel with other wireless stations (STAs) acting as APs or non-AP STAs on a wireless local area network (WLAN) in which carrier sense multiple access / collision avoidance (CSMA / CA) is applied. (b) Configure the Enhanced Distributed Channel Access (EDCA) function to operate by providing multiple sets of single EDCA or multi-user (MU) EDCA operation parameters of a series of priority levels, wherein each set of operation parameters provides a different level of nominal access time for STAs to use at different time periods when competing for at least one of the channels, wherein the multiple sets of single EDCA or MU-EDCA operation parameters include a backoff slot duration parameter, thereby allowing the backoff slot duration to be dynamically set in response to changes between the multiple sets of single EDCA or MU-EDCA operation parameters, and wherein the STA is configured to use single EDCA or MU-EDCA operation parameters of different priority levels simultaneously for backoff on different access classes (ACs); (c) When the STA needs accelerated channel access, use the higher priority set of single EDCA or multi-user (MU) EDCA operation parameters; as well as (d) When the STA needs to slow down channel access, it utilizes the lower priority set of EDCA operating parameters. The method further includes limiting the duration for which the STA can continuously use a higher-priority single EDCA or MU-EDCA operation parameter set, based on the access class (AC).

Images