Priority Channel Access

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 using multiple operating parameter sets that provide a range of priority levels that change on the fly the nominal access time at which a STA transmits prioritized packets. The STA must then switch to a lower priority parameter set as compensation so that channel usage remains fair.

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to and the benefit of U.S. Provisional Patent Application Serial No. 63 / 126,585, filed December 17, 2020, which is incorporated herein by reference in its entirety.

[0002] STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT Not applicable

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

[0004] The techniques of this disclosure relate generally to IEEE 802.11 based wireless local area networks, and more particularly to CSMA / CA networks that use EDCA in a manner that supports real-time application (RTA) traffic. [Background technology]

[0005] Current wireless technologies using CSMA / CA focus on high network throughput performance but lack low latency capabilities. However, applications requiring low latency, such as real-time applications (RTA), are increasing, thus creating a technology gap.

[0006] RTA requires low latency communication and uses best-effort communication. Data generated from RTA is called RTA traffic and is packetized as RTA packets at the sending STA. Data generated from non-time-sensitive applications is called non-RTA traffic and is packetized as non-RTA packets at the sending STA.

[0007] RTA packets require low latency due to the high timeliness requirements for packet delivery: RTA packets are valid if delivered within a certain period of time.

[0008] The Enhanced Distributed Channel Access (EDCA) feature of 802.11e defines multiple Access Categories (ACs) with AC-specific contention window (CW) sizes, arbitration interframe space (AIFS) values, and transmission opportunity (TXOP) limits to support MAC-level QoS and prioritization. Summary of the Invention [Problem to be solved by the invention]

[0009] However, RTA-based protocols can be disadvantageous to non-RTA wireless devices, while RTA operation is often compromised under EDCA-type protocols.

[0010] Therefore, there is a need for an EDCA-based protocol that improves RTA performance without unduly compromising non-RTA throughput levels. The present disclosure addresses these issues and provides additional advantages over previous techniques. [Means for solving the problem]

[0011] The IEEE 802.11 WLAN protocol is configured to allow devices to maintain multiple Enhanced Distributed Channel Access (EDCA) and Multi-User (MU) EDCA parameter sets. By changing the parameters of an Access Category (AC), the nominal channel access time for that AC can be increased or decreased relative to the priority using the default parameter settings. A wireless device can switch over time between EDCA and MU EDCA parameter settings to increase or decrease the nominal channel access time for each AC.

[0012] In at least one embodiment, changes to the nominal channel access time of an AC are primarily driven by fairness considerations. Specifically, if the access time of an AC of a wireless device is reduced for a certain period of time, that channel access time should be increased for another period of time, thus creating a kind of give-and-take. If an AC of a wireless device reduces its channel access time, the channel access time of another AC of the same wireless device can be increased at the same time.

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

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

[0015] [Figure 1] FIG. 1 is a data field diagram of an EDCA parameter set element defined in IEEE 802.11. [Figure 2] FIG. 11 is a data field diagram of a QoS information field when transmitted by an AP, as defined in IEEE 802.11. [Figure 3]FIG. 1 is a data field diagram of an AC_X parameter record field defined in IEEE 802.11. [Figure 4] FIG. 1 is a data field diagram of an MU EDCA parameter set element defined in IEEE 802.11. [Figure 5] FIG. 10 is a data field diagram of the MU AC_X parameter record field defined in IEEE 802.11. [Figure 6] FIG. 2 is a hardware block diagram of radio station hardware in accordance with at least one embodiment of the present disclosure. [Figure 7] FIG. 2 is a hardware block diagram of a station configuration, such as that included in multilink device hardware, in accordance with at least one embodiment of the present disclosure. [Figure 8] 1 is a topology of a WLAN with six STAs across two BSSs and two APs, in accordance with at least one embodiment of the present disclosure. [Figure 9] 1 is a flow diagram of a priority-capable (P-capable) STA contending for a channel to obtain a transmission opportunity (TXOP) of an AC, in accordance with at least one embodiment of the present disclosure. [Figure 10] 1 is a flow diagram for a P-capable STA to contend for a channel during a priority period to obtain a TXOP of an AC, in accordance with at least one embodiment of the present disclosure. [Figure 11] 1 is a flow diagram of a STA contending for channel access rights to obtain a TXOP for prioritized packet transmission during a priority period, in accordance with at least one embodiment of the present disclosure. [Figure 12] FIG. 2 is a communication diagram in which an AP transmits a preferred EDCA parameter set update frame or a multilink parameter set update frame, in accordance with at least one embodiment of the present disclosure. [Figure 13] FIG. 10 is a data field diagram of a preferred EDCA parameter set element in accordance with at least one embodiment of the present disclosure. [Figure 14]FIG. 10 is a data field diagram of a high priority (HP) parameter record subfield of an AC, in accordance with at least one embodiment of the present disclosure. [Figure 15] FIG. 10 is a data field diagram of a low priority (LP) parameter record subfield of an AC in accordance with at least one embodiment of the present disclosure. [Figure 16] 1 is a data field diagram of a beacon frame content including an EDCA parameter set element, an MU EDCA parameter set element, and a preferred EDCA parameter set element, in accordance with at least one embodiment of the present disclosure. [Figure 17] FIG. 10 is a data field diagram of a Neighbor AP Information field in accordance with at least one embodiment of the present disclosure. [Figure 18] FIG. 10 is a data field diagram of a preferred EDCA field, an EDCA parameter set element, an MU EDCA parameter set element, and an MLD parameter subfield of TBTT information used to convey a preferred EDCA parameter set element of the TBTT information set subfield, in accordance with at least one embodiment of the present disclosure. [Figure 19] FIG. 10 is a data field diagram of a non-transmitting BSSID profile field used to convey a Preferred EDCA field, an EDCA parameter sets field, an MU EDCA parameter sets field, and a Preferred EDCA parameter sets field, in accordance with at least one embodiment of the present disclosure. [Figure 20] FIG. 10 is a data field diagram of a multilink element utilized to convey a Preferred EDCA element, an EDCA Parameter Sets element, an MU EDCA Parameter Sets element, and a Preferred EDCA Parameter Sets field in a Per-STA Profile subfield, in accordance with at least one embodiment of the present disclosure. [Figure 21] FIG. 10 is a data field diagram of a preferred parameter set update frame in accordance with at least one embodiment of the present disclosure. [Figure 22] FIG. 10 is a data field diagram of a multilink parameter update frame in accordance with at least one embodiment of the present disclosure. [Figure 23] 10A-10C are communication sequence diagrams using different EDCA parameter settings in accordance with at least one embodiment of the present disclosure. [Figure 24] FIG. 10 is a communication sequence diagram for defeating channel contention for an AC using low-priority EDCA parameter settings, in accordance with at least one embodiment of the present disclosure. [Figure 25] FIG. 10 is a communication sequence diagram in which a STA begins a non-priority period after a priority period of an AC, in accordance with at least one embodiment of the present disclosure. [Figure 26] FIG. 10 is a communication sequence diagram in which a STA delays between two priority periods of an AC, in accordance with at least one embodiment of the present disclosure. [Figure 27] FIG. 10 is a communication sequence diagram in which a STA uses different EDCA parameters for non-priority packets during a priority period, in accordance with at least one embodiment of the present disclosure. [Figure 28] FIG. 10 is a communication sequence diagram in which a STA simultaneously configures different mode periods for multiple ACs, in accordance with at least one embodiment of the present disclosure. [Figure 29] FIG. 10 is a communication sequence diagram in which a STA uses preferred EDCA parameters of multiple ACs during a preferred period, in accordance with at least one embodiment of the present disclosure. [Figure 30] 1 is a communication sequence diagram in which one AC of a STA uses the backoff slot duration of the LP EDCA parameters of the one AC during a priority period, in accordance with at least one embodiment of the present disclosure. [Figure 31] FIG. 10 is a communication sequence diagram in which one STA uses a backoff slot duration of LP EDCA parameters during a priority period, in accordance with at least one embodiment of the present disclosure. [Figure 32] FIG. 10 is a communication sequence diagram in which a STA uses MU EDCA parameters of preferred EDCA parameters during a preferred period, in accordance with at least one embodiment of the present disclosure. [Figure 33]1 is a communication sequence diagram in which a STA switches to using MU EDCA parameters of low priority (LP) MU EDCA parameters during a priority period, in accordance with at least one embodiment of the present disclosure. [Figure 34] FIG. 1 is a communication sequence diagram in which a STA uses multiple EDCA Functions (EDCAFs) for a single packet transmission, in accordance with at least one embodiment of the present disclosure. [Figure 35] FIG. 10 is a communication sequence diagram in which a STA uses multiple EDCAFs to transmit packets from one AC, in accordance with at least one embodiment of the present disclosure. [Figure 36A] FIG. 1 is a communication sequence diagram in which a STA uses Priority EDCA and multiple EDCAFs to transmit packets from one AC, in accordance with at least one embodiment of the present disclosure. [Figure 36B] FIG. 1 is a communication sequence diagram in which a STA uses Priority EDCA and multiple EDCAFs to transmit packets from one AC, in accordance with at least one embodiment of the present disclosure. [Figure 37A] FIG. 1 is a communication sequence diagram in which a STA uses Priority EDCA and multiple EDCAFs to transmit packets from one AC, in accordance with at least one embodiment of the present disclosure. [Figure 37B] FIG. 1 is a communication sequence diagram in which a STA uses Priority EDCA and multiple EDCAFs to transmit packets from one AC, in accordance with at least one embodiment of the present disclosure. [Figure 38] FIG. 10 is a communication sequence diagram using different AIFSs during a backoff procedure, in accordance with at least one embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0016] 1. Introduction In a given network, it may not be possible to obtain both high throughput and low latency simultaneously. To meet the different requirements of RTA and non-RTA packets, the disclosed protocol utilizes some features to improve low latency performance when transmitting RTA packets and other features to maximize throughput when transmitting non-RTA packets.

[0017] To achieve these goals, a transmitting station (STA) needs the ability to distinguish between RTA and non-RTA traffic. In some cases, a receiving STA may also benefit from distinguishing between RTA and non-RTA packets, for example, allowing the network to select from different characteristics that meet the requirements of RTA and non-RTA traffic separately.

[0018] Most typical RTAs generate traffic periodically as connection-oriented communication. An RTA connection-oriented communication established between STAs by an application is called an RTA session. An STA can have multiple RTA sessions within a network, so it is important to manage these RTA sessions correctly.

[0019] 2. IEEE 802.11 Parameter Set Elements 2.1 EDCA Parameter Set Elements Figure 1 shows the format of an EDCA parameter set element defined in IEEE 802.11. The Element ID and Element ID Extension fields identify the element and indicate that it is an 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 STAs). The next four fields have the subfield format shown in Figure 3. The AC_BE Parameter Record field carries EDCA parameters for AC_BE. The AC_BK Parameter Record field carries EDCA parameters for AC_BK. The AC_VI Parameter Record field carries EDCA parameters for AC_VI. The AC_VO Parameter Record field carries EDCA parameters for AC_VO.

[0020] Figure 2 shows the format of the QoS information field when transmitted 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 this field is received by a non-AP STA and differs from the value stored by the non-AP STA, the STA preferably updates the EDCA parameters according to the most recently received EDCA parameter elements. The Q-ACK field is set to a first state (e.g., "1") if dot11QAckOptionImplemented is set to a first state (e.g., "1"), and is set to a second state (e.g., "0") otherwise. Note that dot11QAckOptionImplemented is a capability variable in IEEE P802.11REVmd_D5.0. Its value depends on the device's capabilities. When true, this attribute indicates that the station implementation can interpret the CF-ACK bit in received frames whose Type subfield is equal to Data, even if the frame is not intended for the QoS station. Otherwise, this capability is disabled. If a STA is the recipient of a data frame, it can interpret the CF-ACK bit in a received data frame regardless of the value of this MIB attribute.

[0021] The Queue Request field is set to a first state (e.g., "1") if the AP can process a non-zero Queue Size subfield of the QoS Control field in the QoS data frame, and is set to a second state (e.g., "0") otherwise. The TXOP Request field is set to a first state (e.g., "1") if the AP can process a non-zero TXOP Duration Request subfield of the QoS Control field in the QoS data frame, and is set to a second state (e.g., "0") otherwise.

[0022] Figure 3 shows the format of the AC_x parameter record field defined in IEEE 802.11. The AC / AIFSN field indicates the Access Category (AC) and AIFSN parameter set of this field. The ECWmin / ECWmax fields indicate the minimum and maximum contention window (CW) sizes of the AC. The TXOP limit field indicates the TXOP limit of the AC.

[0023] 2.2 Multi-User EDCA Parameter Set Elements Figure 4 shows the format of an MU EDCA parameter set element defined in IEEE 802.11. The Element ID and Element ID extension fields identify the element and indicate that it is an MU EDCA parameter set element. The Length field indicates the length of the element. The QoS Information (Info) field is defined in IEEE 802.11 as shown in Figure 2. The subfield formats of the remaining fields are 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.

[0024] Figure 5 shows the format of the MU AC_X parameter record field defined in IEEE 802.11. The AC / AIFSN field indicates the Access Category (AC) and AIFSN parameter set for this field in the MU_EDCA timer. The ECWmin / ECWmax fields indicate the minimum and maximum contention window (CW) sizes for the AC in the MU_EDCA timer. The MU_EDCA Timer field indicates the timer period for the STA to use the MU EDCA parameters for the AC.

[0025] 2. Problem statement Current IEEE 802.11 devices use a single EDCA and MU EDCA parameter set for channel contention. The channel access priority for each access category (AC) is statically configured. STAs have a higher probability of accessing the channel earlier with a higher priority AC than with a lower priority AC. However, a STA may need to shorten the nominal channel access time of a given AC for a certain period of time to transmit special traffic, such as real-time application (RTA) traffic. For example, if an AC contends for the channel to transmit RTA traffic, it should shorten the nominal channel access time to meet its timeliness requirements. An AC does not have a special requirement to advance its channel access time if it does not have RTA traffic to transmit. That is, wireless devices can dynamically change the EDCA and MU EDCA parameters of an AC over a certain period of time, but this cannot be achieved using a single EDCA or MU EDCA parameter set.

[0026] 3. Contributions of this Disclosure The proposed technique allows each IEEE 802.11 device (STA) to maintain multiple EDCA and MU EDCA parameter sets. By changing the parameters of an AC, the nominal channel access time for that AC can be increased or decreased compared to the preference using the default parameter settings. Thus, a wireless device can switch between EDCA and MU EDCA parameter settings over a period of time to increase or decrease the nominal channel access time for each AC. Hereinafter, the term nominal access time will be used, but its value should be understood as _.

[0027] The proposed technique considers the fairness issue of reducing the nominal channel access time of AC. There are several options to solve the fairness issue, and two examples are given below.

[0028] In the first option, if the wireless device's AC reduces its channel access time for a period of time, it should increase it for another period of time to ensure fairness (equity).

[0029] In the second option, if an AC of a wireless device reduces its channel access time, another AC of the same wireless device should increase its channel access time to ensure fairness (equity).

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

[0031] The bus 14 can connect various devices, such as sensors and actuators, to the CPU. Instructions from memory 20 execute on the processor 18 to execute a program implementing a communication protocol that enables the STA to perform the functions of an access point (AP) station or a regular station (non-AP STA). It should also be understood that this programming is configured to operate in different modes (TXOP owner, TXOP sharing participant, source, intermediate, destination, first AP, other AP, station associated with first AP, station associated with other AP, coordinator, coordinated, etc.) depending on the role it plays in the current communication situation. Accordingly, the illustrated STA HW is configured with at least one modem and associated RF circuitry for providing communications over at least one band, such as the sub-6 GHz band.

[0032] Multiple instances of station hardware such as that shown can also be combined to form a multi-link device (MLD), which typically has a processor and memory to coordinate activities, although separate CPUs and memory are not always required for each STA within an MLD.

[0033] FIG. 7 illustrates an example embodiment 40 of a multi-link device (MLD) hardware configuration. The MLD serves multiple STAs, each operating on a different frequency link. The MLD has external I / O 41 access for applications, which connects to an MLD management entity 48 having a CPU 62 and memory (e.g., RAM) 64 to enable execution of program(s) that implement communication protocols at the MLD level. The MLD can distribute tasks to and collect information from its associated stations, STA1 42, STA2 44 through STA N 46, and share that information among its associated STAs.

[0034] In at least one embodiment, each STA in the MLD has its own CPU 50 and memory (RAM) 52, which are coupled via a bus 58 to at least one modem 54 connected to at least one RF circuit 56 having one or more antennas 60a, 60b, 60c-60n. This disclosure is primarily concerned with the sub-6 GHz band with omnidirectional antennas. The modem, in combination with the RF circuitry and associated antenna(s), transmits / receives data frames to / from nearby STAs. In at least one implementation, the RF module includes a frequency converter, an array antenna controller, and other circuitry for interfacing with the antennas.

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

[0036] 4.2. STA Topology Considered FIG. 8 illustrates an example topology (network scenario) 70 by way of example and not limitation. This topology is shown merely to illustrate the goal of the proposed technology and is not intended to limit it to a specific STA configuration. In this example topology, it is assumed that there are six STAs and two APs across two BSSs in a given space (e.g., a conference room). Each STA and its associated AP can communicate with each other. Note that the two APs in the two BSSs belong to the same MLD, so the two BSSs can also be considered the same BSS.

[0037] An MLD is a device with multiple associated STAs and one MAC Service Access Point (SAP) to a Logical Link Control (LLC) containing one MAC data service. In this example, assume there are four STAs in a local area, comprising two MLDs. STA1 80 and STA4 82 belong to non-AP Multilink Device (MLD) #1 74, while AP1 76 and AP2 78 belong to AP MLD #2 72. STA1 and STA4 are associated with AP1 and AP2 via Link 1 and Link 2, respectively. STA2 84 and STA3 86 are shown connected to AP1 76 in MLD2 72. STA5 88 is shown connected to AP1 76 via Link 1, and STA6 90 is shown connected to AP2 78 via Link 1.

[0038] All STAs use CSMA / CA for random channel access. A STA can use multiple EDCA parameter sets at different times if it is P-capable; otherwise, it is considered a legacy device. As shown, the two APs and STA1-STA4 are P-capable; only STA5 88 and STA6 90 are considered legacy devices.

[0039] 4.3. Priority Channel Access The disclosed technology defines multiple EDCA and MU-EDCA parameter settings for a STA. These multiple parameter sets provide a range of priority levels, including not only a normal parameter set, but also one or more higher priority levels and one or more lower priority sets. By way of example and not limitation, the multiple operational parameter sets are illustrated herein as a normal (Reg) setting, a high priority (HP) setting, and a low priority (LP) setting.

[0040] During normal use, the STA sets the normal EDCA and MU-EDCA parameter settings as the single EDCA and MU-EDCA parameter settings.

[0041] The STA configures high priority (HP) EDCA and MU-EDCA parameter settings to expedite channel access compared to using normal EDCA and MU-EDCA parameters.

[0042] The STA sets the low priority (LP) EDCA and MU-EDCA parameter settings to slow down channel access compared to the normal EDCA and MU-EDCA parameter settings. The low priority setting is primarily used to maintain fairness in channel access among stations in the network.

[0043] The STA can dynamically switch between the EDCA parameter setting and the MU-EDCA parameter setting to change the channel access parameters of each AC. Note that the EDCA parameter setting and the MU-EDCA parameter setting can be used / controlled independently.

[0044] In at least one embodiment, the disclosed technology also considers fairness issues when changing the EDCA and MU-EDCA parameters of an AC. If a STA shortens its nominal channel access time for a certain period of time using the high-priority (HP) EDCA and MU-EDCA parameter settings of an AC, it should (or be limited to) increase the nominal channel access time for that AC for another period of time using the low-priority EDCA and MU-EDCA parameter settings of that AC to compensate (fairly refund) the shortened channel access time. Also, in at least one embodiment, the period of time that a STA can continuously use the HP EDCA and MU-EDCA parameter settings of an AC is limited.

[0045] It should also be understood that in at least one embodiment, the above-mentioned "compensation" includes the ability to perform "pre-compensation" by utilizing a lower priority operating parameter set before a higher priority operating parameter set to fully or partially pre-compensate for the higher priority operating parameter set.

[0046] The disclosed technology uses HP EDCA and MU-EDCA parameter settings to reduce the nominal channel access time for certain types of traffic, designated as priority traffic. If a packet carries priority traffic, it is referred to herein as a priority packet.

[0047] 4.3.1.Channel Access for P-Capable STAs The proposed technique indicates the following period modes for each AC (e.g., normal period, preferred period, non-preferred period).

[0048] The normal period of an AC is considered to be the time when the STA accesses the channel using the normal EDCA and MU-EDCA parameter settings for channel access of this AC. These parameters can be set by the elements shown in Figures 1 and 4.

[0049] The priority period of an AC is considered to be a time during which a STA uses HP EDCA and MU-EDCA parameter settings to reduce the nominal channel access time for that AC. In at least some cases, the priority period of an AC can be scheduled by an AP or STA, e.g., periodically or dynamically. In at least some cases, during the priority period, a STA uses only HP EDCA and MU-EDCA parameters for transmitting priority packets and uses regular or LP EDCA and MU-EDCA parameters for transmitting other packets.

[0050] The non-priority period of an AC is considered to be a time during which a STA uses LP EDCA and MU-EDCA parameter settings to increase the nominal channel access time for that AC. In at least some cases, the non-priority period of an AC can be scheduled by the AP or STA, for example, periodically or dynamically.

[0051] Note that the period mode (e.g., normal period, priority period, non-priority period) of each AC can be different at a particular time. For example, a STA can simultaneously have a priority period of AC_VO, a non-priority period of AC_VI, and a normal period of AC_BE and AC_BK.

[0052] Flow Diagram 9 illustrates an example embodiment 110 of a P-capable STA contending for a channel to obtain a transmission opportunity (TXOP) for an AC. Execution begins 112 with a check 114 in which the P-capable STA determines what type of period it is in for the AC. If it is in the normal period, the STA contends for the channel and obtains a TXOP using normal EDCA and MU-EDCA parameters for that AC in block 116. If it is in the preferred period, the STA contends for the channel and obtains a TXOP using high-priority EDCA and MU-EDCA parameters for that AC in block 118. If it is in the non-priority period, the STA contends for the channel and obtains a TXOP using low-priority EDCA and MU-EDCA parameters for that AC in block 120. Execution then terminates.

[0053] It should be understood that STAs can contend for and obtain TXOPs using only high-priority EDCA and MU-EDCA parameters for prioritized packet transmissions. For other packets, STAs can use regular or low-priority EDCA and MU-EDCA parameters for channel contention. Further details are provided in FIG. 10.

[0054] FIG. 10 illustrates an example embodiment 130 in which P-capable STAs contend for a channel during a priority period to obtain a TXOP of an AC.

[0055] Execution begins (132) with a check 134 to determine whether the P-capable STA plans to transmit prioritized traffic. If it is determined that the STA plans to transmit prioritized traffic, then the STA contends for and obtains the TXOP of the AC using high-priority EDCA and MU-EDCA parameters for the prioritized traffic in block 136. If it is determined in block 134 that the P-capable STA does not have prioritized traffic to transmit, execution reaches block 138, where the STA contends for and obtains the TXOP of the AC using low-priority or regular EDCA and MU-EDCA parameters.

[0056] Therefore, it can be seen that P-capable STAs use only high-priority EDCA and MU-EDCA parameters for priority traffic. Note that Figures 9 and 10 can be used in combination, or STAs can contend for the channel according to either Figure 9 or Figure 10.

[0057] 11 illustrates an example embodiment 150 in which a STA contends for channel access and obtains a TXOP for a prioritized packet transmission during a priority period. Execution begins (152) and the STA contends for the channel using multiple EDCAFs for the same prioritized packet transmission (154) and obtains a TXOP.

[0058] It should be understood that throughout this disclosure, the terms AC_x and / or AC_y are each used to represent any one of the Access Classes (ACs).

[0059] For example, the EDCAFs of AC_x and AC_y can simultaneously contend for the channel to transmit packets from AC_x. Either AC_x or AC_y can get the TXOP to transmit packets from AC_x, even if there are packets in AC_y's transmit queue. Note that AC_y can contend for the channel even if it does not have packets from AC_y to transmit. AC_y must have a lower priority than AC_x.

[0060] In this disclosure, this method can be used for priority packets only within a priority period. This method provides a mechanism that allows packets from one AC to transmit using the EDCA capabilities of another AC to contend for a channel and obtain a TXOP.

[0061] 4.3.1.2. Updating Preferred EDCA Parameter Sets Figure 12 shows an example embodiment 170 in which an AP 172 sends 176 a Preferred EDCA Parameter Set Update frame or a Multilink Parameter Set Update frame to update the preferred EDCA parameters of a receiving STA 174. If the receiving STA belongs to an MLD, other STAs belonging to the same MLD may also update their preferred EDCA parameters according to the context in the Multilink Parameter Set Update frame. The formats of the Preferred EDCA Parameter Set Update frame and the Multilink Parameter Set Update frame are shown in Figures 21 and 22, respectively.

[0062] In addition, the multilink parameter set update frame can also be used to update general multilink parameters, such as default EDCA parameters and MU EDCA parameters, of all STAs belonging to the MLD.

[0063] It is also possible for the AP to send a beacon frame, a (ML) probe response frame, or a (re)association response frame as shown in FIG. 16 to update the preferred EDCA parameters of the receiving STA.

[0064] Frame Format The Priority EDCA Parameter Set element can be used by an AP to set the high-priority EDCA and MU-EDCA parameters and the low-priority EDCA and MU-EDCA parameters of its associated STAs.

[0065] The Preferred EDCA parameter set element can be carried by a frame carrying the EDCA parameter set element shown in Figure 1 and the MU EDCA parameter set element shown in Figure 4. For example, the Preferred EDCA parameter set element can be included in a beacon frame, a probe response frame, or a (re)association response frame to indicate the high-priority and low-priority EDCA and MU-EDCA parameters to be configured in its associated STA. The Preferred EDCA parameter set element can also be carried in the Per-STA Profile field of the Multilink element, the Reduced Neighbor Report (RNR) element, and the Multiple BSSID element defined in IEEE 802.11be to indicate the high-priority and low-priority EDCA and MU-EDCA parameter settings of its collocated APs. An AP can transmit a Preferred EDCA Parameter Set Update frame to update the preferred EDCA parameters in a STA.

[0066] Figure 13 shows the format of a preferred EDCA parameter set element. The Element ID and Element ID extension fields identify the element and indicate that it is a preferred 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.

[0067] The Updated EDCA Info field is defined in IEEE 802.11 and is reserved for non-S1G STAs. The HP Parameter Records field carries the HP Parameter Records subfields of all ACs.

[0068] The format of the HP Parameter Record subfield is described later in Figure 14. The HP Parameter Record field is set by the AP to indicate the high-priority EDCA parameters and MU EDCA parameters that should be configured in the corresponding STA. When a STA receives this field in a Priority EDCA Parameter Set Update frame, a Multilink Parameter Set Update frame, a Beacon frame, a (ML) Probe Response frame, or a (Re)Association Response frame, it should update the high-priority EDCA parameters for that AC on its own side.

[0069] It is also possible that the HP parameter record field carries only the high priority parameter record subfields of some ACs. When a Preferred EDCA parameter set element is carried by a Preferred EDCA parameter set update frame or a Multilink parameter set update frame, the corresponding STA updates only the high priority EDCA and MU EDCA parameters of the ACs carried by this element.

[0070] If the Preferred EDCA Parameter Setting element is carried by a beacon frame, a (ML) probe response frame, or a (re)association response frame, the corresponding STA sets the high-priority EDCA and MU-EDCA parameters of the ACs carried by this element. For the high-priority EDCA and MU-EDCA parameters of ACs not carried by this element, the corresponding STA can set them to the default EDCA and MU-EDCA parameters of these ACs.

[0071] The LP Parameter Records field in Figure 13 carries the LP Parameter Records subfields of all ACs. The format of the LP Parameter Records subfield of an AC is shown in Figure 15. The LP Parameter Records field is set by the AP to indicate the low-priority EDCA and MU EDCA parameters that should be configured in the corresponding STA. When a STA receives this field in a Priority EDCA Parameter Set Update frame, a Multilink Parameter Set Update frame, a Beacon frame, a (ML) Probe Response frame, or a (Re)Association Response frame, it should update its own low-priority EDCA and MU EDCA parameters.

[0072] It is also possible that this field carries only the low-priority parameter record subfields of some ACs. When a Preferred EDCA parameter set element is carried by a Preferred EDCA parameter set update frame or a Multilink parameter set update frame, the corresponding STA updates only the low-priority EDCA and MU EDCA parameters of the ACs carried by this element.

[0073] If the Priority EDCA Parameter Setting element is carried by a beacon frame, a (ML) probe response frame, or a (re)association response frame, the corresponding STA sets the low-priority EDCA and MU-EDCA parameters of the ACs carried by this element. For the low-priority EDCA and MU-EDCA parameters of ACs not carried by this element, the corresponding STA can set them to the default EDCA and MU-EDCA parameters of these ACs.

[0074] The AC HP Indication field in FIG. 13 indicates which ACs are included in the HP parameter record field. This field may contain a list of bits, with each bit representing an AC. If a bit is set to a 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. The order of the high-priority EDCA and MU EDCA parameters of the corresponding AC should follow the order of the ACs in this field. For example, if the AC HP Indication has four bits, from left to right, the first bit indicates the presence of high-priority EDCA and MU EDCA parameters of AC_VO. The second bit indicates the presence of high-priority EDCA and MU EDCA parameters of AC_VI. The third bit indicates the presence of high-priority EDCA and MU EDCA parameters of AC_BE. The fourth bit indicates the presence of high-priority EDCA and MU EDCA parameters of AC_BK. When this field is set to "1010", it indicates the presence of high priority EDCA and MU EDCA parameters for AC_VO and AC_BE in the HP parameter record.

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

[0076] The AC LP Indication field in Figure 13 indicates which ACs are included in the LP parameter record field. This field may include, for example, a list of bits, with each bit representing an AC. If a bit is set to a first state (e.g., "1"), the low-priority EDCA and MU EDCA parameters for the corresponding AC are included in the LP parameter record field; otherwise, the low-priority EDCA and MU EDCA parameters for the corresponding AC are not included in the LP parameter record field.

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

[0078] Figure 14 shows an example embodiment 210 illustrating the format of the HP parameter record subfield for an AC. AC_x in the figure represents an AC. For example, this can be AC_VI, AC_VO, AC_BE, AC_BK, or a newly added AC in EDCA.

[0079] The AC_x Parameter Record field indicates the high-priority EDCA parameters that the corresponding STA should configure. The format of this field can be the same as that shown in FIG.

[0080] The MU AC_x Parameter Record field indicates the high-priority MU EDCA parameters that the corresponding STA should configure. The format of this field can be the same as that shown in FIG.

[0081] The AC_x HP-EDCA Timer field indicates the maximum time, e.g., maximum priority period, that a STA can continuously contend for the channel of AC_x using high-priority EDCA and MU EDCA parameters. If the LP-EDCA timer value of AC_x is non-zero, non-AP STAs should count down the LP-EDCA timer uniformly to 0 without interruption.

[0082] Figure 15 shows an example embodiment 230 illustrating the format of the LP parameter record subfield of an AC, where AC_x represents an AC, which can be, for example, AC_VI, AC_VO, AC_BE, AC_BK, or a newly added AC in EDCA.

[0083] The AC_x Parameter Record field indicates the low-priority EDCA parameters of AC_x that the corresponding STA should configure. The format of this field is shown in Figure 3.

[0084] The MU AC_x Parameter Record field indicates the low-priority MU EDCA parameters for AC_x that the corresponding STA should configure. The format of this field is shown in Figure 5.

[0085] The AC_x LP-EDCA timer field indicates the amount of time that a STA must contend for AC_x's channel using low-priority EDCA and MU EDCA parameters after using AC_x's high-priority EDCA and MU EDCA parameters, e.g., a non-priority period after a priority period. If AC_x's LP-EDCA timer value has a non-terminal (e.g., non-zero) value, the LP-EDCA timer counts down uniformly to the terminal count (e.g., zero) without being interrupted by non-AP STAs.

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

[0087] FIG. 16 illustrates an example embodiment 250 of beacon frame content including an EDCA parameter set element, an MU EDCA parameter set element, and a preferred EDCA parameter set element.

[0088] The Frame Control field indicates the type of frame. The Duration field contains NAV information used for CSMA / CA channel access. The RA field contains the address of the frame's recipient. The TA field contains the address of the STA that sent the frame. The BSS ID is a label to identify the BSS from others. The Sequence control field contains the fragment number and sequence number of the packet.

[0089] The Beacon Frame Body field can have the same content as the frame body of an IEEE 802.11 beacon frame, and some example subfields are shown below. The RNR (Reduced Neighbor Report) element contains channel and other information related to neighboring APs as defined in IEEE 802.11be. This element can also carry the default EDCA, default MU EDCA, and preferred EDCA parameter sets of the neighboring AP.

[0090] The Element ID identifies the element and indicates that it is an RNR element. The Length field indicates the length of the element.

[0091] The Neighbor AP Information field includes one or more Neighbor AP Information fields as illustrated in Figure 17. Each Neighbor AP Information field can carry the default EDCA, default MU EDCA, and preferred EDCA parameter sets of the neighbor AP and other APs that belong to the same MLD as the neighbor AP on different links.

[0092] The Prioritized EDCA field is set to indicate whether a preferred EDCA parameter set is used by the AP transmitting the beacon frame. By way of example and not limitation, this field may be implemented as a one-bit indication. If the bit is set to a first state (e.g., "1"), the preferred EDCA parameter set is used; otherwise, it is set to a second state (e.g., "0"). In at least one implementation, a predetermined process / method may be utilized to determine / calculate the preferred EDCA parameters based on the default EDCA and MU EDCA parameters. For example, the TXOP limit of the low-priority EDCA parameters for AC_VI is always set to half the TXOP limit of the default EDCA parameters for AC_VI. A STA should use the preferred EDCA parameters when associated with the AP to which the Preferred EDCA field belongs.

[0093] The EDCA parameter set field indicates the default EDCA parameters that a STA receiving a beacon frame should set when associated with the AP transmitting the beacon frame. The format of this field is shown in Figure 1.

[0094] The MU EDCA parameter set field indicates the default MU EDCA parameters that a STA receiving a beacon frame should set when associated with the AP transmitting the beacon frame. The format of this field is shown in Figure 4.

[0095] The Priority EDCA parameter set field indicates the priority EDCA parameters that the STA receiving the beacon frame should set when associated with the AP transmitting the beacon frame. The format of this field is shown in Figure 13.

[0096] The Multiple BSSID element defined in IEEE 802.11be is used to indicate information about all non-transmitting BSSs supported by an AP. Information about each non-transmitting BSS is carried by a Non-transmitted BSSID Profile field. The Non-transmitted BSSID Profile field can include a Preferred EDCA field, an EDCA parameter set element, an MU EDCA parameter set element, and a Preferred EDCA parameter set element. If the AP of a non-transmitting BSS belongs to an MLD, the corresponding Non-transmitted BSSID Profile field can include a Multilink element. As shown in Figure 20, the Multilink element can carry the EDCA and MU EDCA parameter settings on each link of the MLD.

[0097] The multilink element indicates information of APs on multiple links that belong to the non-transmitting BSSID indicated in the non-transmitting BSSID profile (defined in IEEE 802.11be). Figure 20 shows the possibility that the multilink element carries the Preferred EDCA field, EDCA Parameter Set field, MU EDCA Parameter Set field, and Preferred EDCA Parameter Set field for each AP on multiple links that belong to the non-transmitting BSSID.

[0098] Note that if a preferred EDCA parameter set element does not carry parameters for all ACs, the preferred EDCA parameters of the ACs not carried by the preferred EDCA parameter set element may inherit (i.e., be set to the same values ​​as) the parameters in the EDCA parameter set elements and MU EDCA parameter set elements carried in the same beacon frame body field as the preferred EDCA parameter set element. For example, if the high-priority EDCA parameters of AC_BK are not included in the preferred EDCA parameter set element as shown in Figure 16, these parameters may be set to the same values ​​as the normal EDCA parameters of AC_BK shown in the EDCA parameter set element as shown in Figure 16.

[0099] FIG. 17 illustrates an example embodiment 270 of the Neighbor AP Information field defined in IEEE 802.11be, configured to carry the Preferred EDCA field, the EDCA Parameter Set field, the MU EDCA Parameter Set field, and the Preferred EDCA Parameter Set field within the TBTT Information Set subfield for configuring these parameters in STAs associated with the AP in the TBTT Information Set subfield.

[0100] The TBTT Information Length subfield in the TBTT Information Header field is set to indicate the presence of a Preferred EDCA field, an EDCA Parameter Set field, an MU EDCA Parameter Set field, and a Preferred EDCA Parameter Set field within the TBTT Information Set subfield.

[0101] As a result, the TBTT information set field can carry a Preferred EDCA field, an EDCA parameter set field, an MU EDCA parameter set field, and a Preferred EDCA parameter set field, as shown in FIG.

[0102] FIG. 18 illustrates an example embodiment 290 of the MLD Parameters subfield of the TBTT information defined in IEEE 802.11be, configured to carry the Preferred EDCA field, the EDCA parameter set element, the MU EDCA parameter set element, and the Preferred EDCA parameter set element within the TBTT information set subfield for configuring these parameters in the STAs associated with the AP of the TBTT information set subfield.

[0103] MLD ID indicates the identity of the MLD to which the AP belongs. Link ID indicates the identity of the link on which the AP is acting. These two fields identify the AP to which the MLD parameters belong.

[0104] The Change Sequence field indicates the version number of the MLD parameters. The value in this Change Sequence field is updated by incrementing it by 1 each time the MLD parameters of the AP to which the MLD parameters belong are updated.

[0105] The Prioritized EDCA field is set to indicate whether a preferred EDCA parameter set is used by the AP to which the MLD parameters belong. In at least one implementation, this field can be configured to use a one-bit indication. If the bit is set to a first state (e.g., "1"), the preferred EDCA parameter set is used; otherwise, it is set to a second state (e.g., "0"). In at least one implementation, a predetermined process / method is used to determine / calculate the preferred EDCA parameters based on the default EDCA and MU EDCA parameters. For example, the TXOP limit of the low-priority EDCA parameters for AC_VI is always set to half the TXOP limit of the default EDCA parameters for AC_VI. The STA should use the preferred EDCA parameters when associated with the AP to which the Preferred EDCA field belongs.

[0106] The EDCA parameter set field indicates the default EDCA parameters. When the STA associates the MLD parameters with the AP to which it belongs, it should set the default EDCA parameters as indicated in the last received EDCA parameter set field. The format of this field is shown in Figure 1.

[0107] The MU EDCA parameter set field indicates the default MU EDCA parameters. If the MLD parameters are associated with the AP to which the STA belongs, the STA should set the default MU EDCA parameters as indicated in the last received MU EDCA parameter set field. The format of this field is shown in Figure 4.

[0108] The Priority EDCA Parameter Set element indicates the priority EDCA parameters. When the MLD parameter is associated with the AP to which the STA belongs, the STA should set the priority EDCA parameters as indicated in the last received Priority EDCA Parameter Set field. The format of this field is shown in Figure 13.

[0109] Note that if a preferred EDCA parameter set element does not carry parameters for all ACs, the preferred EDCA parameters of the ACs not carried by the preferred EDCA parameter set element may inherit (i.e., be set to the same values ​​as) the parameters in the EDCA parameter set elements and MU EDCA parameter set elements carried by the same MLD parameter field as the preferred EDCA parameter set element. For example, if the high-priority EDCA parameters of AC_BK are not included in the preferred EDCA parameter set element as shown in Figure 18, these parameters may be set to the same values ​​as the normal EDCA parameters of AC_BK shown in the EDCA parameter set element as shown in Figure 18.

[0110] If the EDCA parameter set element, MU EDCA parameter set element, or Preferred EDCA parameter set element are not present, these parameters may inherit the parameters indicated in the beacon frame body or receiver of the beacon frame as shown in FIG.

[0111] FIG. 19 illustrates an example embodiment 310 of a non-transmitting BSSID profile field defined in IEEE 802.11be, here configured to convey the Preferred EDCA field, the EDCA Parameter Sets field, the MU EDCA Parameter Sets field, and the Preferred EDCA Parameter Sets field for setting these parameters in STAs associated with the AP of the non-transmitting BSSID profile field.

[0112] The Prioritized EDCA field is set to indicate whether prioritized EDCA parameters are used by the AP to which the non-transmitting BSSID profile field belongs. 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 prioritized EDCA parameter set is used; otherwise, it is set to a second state (e.g., "0"). At least one implementation utilizes a predetermined process / method to determine / calculate 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 the TXOP limit of the default EDCA parameters of AC_VI.

[0113] The EDCA parameter set field indicates the default EDCA parameters. When a STA associates with the AP to which the non-transmitting BSSID profile field belongs, the STA should set the default EDCA parameters as indicated in the EDCA parameter set field. The format of this field is shown in Figure 1.

[0114] The MU EDCA Parameter Set element indicates the default MU EDCA parameters. When a STA is associated with the AP to which the non-transmitting BSSID profile field belongs, the STA should 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.

[0115] The Priority EDCA parameter set element indicates the priority EDCA parameters. When a STA is associated with the AP to which the non-transmitting BSSID profile field belongs, it should set the priority EDCA parameters as indicated in the Priority EDCA parameter set field. The format of this field is shown in Figure 13. When a STA is associated with the AP to which the Priority EDCA field belongs, it should use the priority EDCA parameters.

[0116] The multilink element indicates information about APs on multiple links that belong to the non-transmitting BSSID indicated in the non-transmitting BSSID profile (defined in IEEE 802.11be). Figure 20 shows that in some cases, the multilink element can be used to carry the Preferred EDCA field, the EDCA parameter set field, the MU EDCA parameter set field, and the Preferred EDCA parameter set field for each AP on multiple links that belong to the non-transmitting BSSID.

[0117] Note that if a Preferred EDCA parameter set element does not carry parameters for all ACs, the Preferred EDCA parameters for ACs not carried by the Preferred EDCA parameter set element may inherit (i.e., be set to the same values ​​as) the parameters in the EDCA parameter set elements and MU EDCA parameter set elements carried by the same non-transmitting BSSID profile field as the Preferred EDCA parameter set element. For example, if the high-priority EDCA parameters for AC_BK are not included in the Preferred EDCA parameter set element as shown in Figure 19, these parameters may be set to the same values ​​as the normal EDCA parameters for AC_BK shown in the EDCA parameter set element as shown in Figure 19.

[0118] If the EDCA Parameter Sets field, MU EDCA Parameter Sets field, or Preferred EDCA Parameter Sets field are not present, these parameters may inherit values ​​from the beacon frame body or fields indicated at the receiver of the beacon frame as shown in Figure 16. Figure 20 shows an example embodiment 330 of a Multilink element defined in IEEE 802.11be configured to carry the Preferred EDCA Element, EDCA Parameter Sets Element, MU EDCA Parameter Sets Element, and Preferred EDCA Parameter Sets fields in the Per-STA Profile subfield for setting these parameters in the STAs associated with the AP in the Per-STA Profile subfield.

[0119] The Link ID field indicates the link that the AP serves. This field identifies the AP to which the parameters indicated in the Preferred EDCA field, EDCA Parameter Set element, MU EDCA Parameter Set element, and Preferred EDCA Parameter Set element belong.

[0120] The Prioritized EDCA field is set to indicate whether a preferred 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 preferred EDCA parameter set is used; otherwise, it is set to a second state (e.g., "0"). In at least one implementation, a predetermined process / method is used to determine / calculate the preferred 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 the TXOP limit of the default EDCA parameters of AC_VI. The STA should use the preferred EDCA parameters when associated with the AP to which the Preferred EDCA field belongs.

[0121] The EDCA parameter set field indicates the default EDCA parameters. When a STA associates with the AP to which the MLD parameter belongs, the STA should set the default EDCA parameters as indicated in the EDCA parameter set field. The format of this field is shown in Figure 1.

[0122] The MU EDCA parameter set field indicates the default MU EDCA parameters. When the STA is associated with the AP to which the MLD parameters belong, the STA should set the default MU EDCA parameters as shown in the MU EDCA parameter set field in Figure 4.

[0123] 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, the STA should set the priority EDCA parameters as shown in the Priority EDCA Parameter Set field in FIG. 13.

[0124] Note that if a Preferred EDCA parameter set element does not carry parameters for all ACs, the preferred EDCA parameters of the ACs not carried by the Preferred EDCA parameter set element may inherit (i.e., be set to the same values ​​as) the parameters in the EDCA parameter set elements and MU EDCA parameter set elements carried by the same Per-STA profile field as the Preferred EDCA parameter set element. For example, if high-priority EDCA parameters for AC_BK are not included in the Preferred EDCA parameter set element, these parameters may be set to the same values ​​as the normal EDCA parameters for AC_BK indicated in the EDCA parameter set element.

[0125] If the EDCA Parameter Set field, MU EDCA Parameter Set field, or Preferred EDCA Parameter Set field are not present, these parameters may be inherited from the non-transmitting BSSID profile or the fields indicated in the STA to which the non-transmitting BSSID profile belongs, as shown in Figure 19.

[0126] Figure 21 shows the format of a Priority Parameter Set Update frame. The Frame Control field indicates the frame type. The Duration field contains the NAV information used 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 sent 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 additional control information for HT, VHT, HE, or EHT frames. The Action field indicates the action to be taken if this is a Priority Parameter Set Update frame. The Category field and QoS Action field indicate the type of action field. In this case, the Action field indicates the presence of a Priority Parameter Set Update frame. The Priority EDCA Parameter Set field indicates the priority EDCA parameters that the receiving STA should set to update. The format of this field is shown in Figure 13.

[0127] Figure 22 shows the format of the Multilink Parameter Update frame. The Frame Control field indicates the type of frame. The Duration field contains the NAV information used 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 sent 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 further control information for HT, VHT, HE, or EHT frames.

[0128] The Action field indicates the action to be taken if it is a Multilink Parameter Update frame. The Category field and QoS / ML Action field indicate the type of action field, and in this case the Action field indicates that it is a Multilink Parameter Update frame. The MLD parameters field indicates the parameters to be set on multiple links. The MLD ID indicates the identity of the MLD to which the AP belongs. The Link ID indicates the identity of the link on which the AP acts. These two fields identify the AP to which the MLD parameters belong (the AP for which the MLD parameters carry information).

[0129] The Change Sequence field indicates the version number of the MLD parameters. The number value in this field is updated by incrementing it by 1 each time the MLD parameters of the AP to which the MLD parameters belong are updated.

[0130] The Prioritized EDCA field is set to indicate whether a preferred 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 preferred EDCA parameter set is used; otherwise, it is set to a second state (e.g., "0"). In at least one implementation, a predetermined process / method is used to determine / calculate the preferred 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 the TXOP limit of the default EDCA parameters of AC_VI. The STA should use the preferred EDCA parameters when associated with the AP to which the Preferred EDCA field belongs.

[0131] The EDCA parameter set field indicates the default EDCA parameters. When a STA is associated with the AP to which the MLD parameter belongs, the STA should set the default EDCA parameters as indicated in the EDCA parameter set field shown in FIG. 1.

[0132] The MU EDCA parameter set element indicates the default MU EDCA parameters. When the STA is associated with the AP to which the MLD parameters belong, the STA should set the default MU EDCA parameters as shown in the MU EDCA parameter set field in Figure 4.

[0133] The Priority EDCA Parameter Set element indicates the priority EDCA parameters. When a STA is associated with the AP to which the MLD parameter belongs, the STA should set the priority EDCA parameters as indicated in the Priority EDCA Parameter Set field shown in Figure 1.

[0134] Note that if a Preferred EDCA parameter set element does not carry parameters for all ACs, the Preferred EDCA parameters of the ACs not carried by the Preferred EDCA parameter set element may inherit (i.e., be set to the same values ​​as) the parameters in the EDCA parameter set elements and MU EDCA parameter set elements carried by the same MLD parameter field as the Preferred EDCA parameter set element. For example, if the high-priority EDCA parameters of AC_BK are not included in the Preferred EDCA parameter set element as shown in Figure 22, these parameters may be set to the same values ​​as the normal EDCA parameters of AC_BK shown in the EDCA parameter set element as shown in Figure 22.

[0135] 4.3.1.4. Parameter setting example Tables 1A to 1C show examples of normal / high priority / low priority EDCA / MU-EDCA parameter settings. Each AP and STA can set the EDCA and MU EDCA parameters as shown in the tables. Note that there may be parameters not shown in these tables.

[0136] When a STA begins contending for a channel on an AC, it preferably generates a random backoff count for the additional deferral time before transmitting packets on that AC, as specified in IEEE 802.11. It will be understood that the random backoff count must be greater than or equal to 1 (backoff slot) when generated, especially when AIFSN=1. That is, each time a STA contends for a channel on an AC, it must count down at least one backoff slot before accessing the channel. For example, if the contention window size is CW, then the random backoff count can be drawn from a uniform distribution over the interval [1, CW+1] rather than [0, CW].

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

[0138] During normal operation of AC_x, STA1 represents a STA belonging to an MLD, and STA2 represents a single (non-MLD) STA. Station 392 can represent either STA1 or STA2, both of which are P-enabled. STA1 and STA2 in this example can also be replaced by APs.

[0139] During AC_x's normal period 394, stations 392 can contend for the channel and obtain a TXOP using default EDCA parameters for packet transmission 398. For example, a backoff 396 (normal BO as shown) can be generated by AC_x's normal / default contention window. The TXOP reservation should obey the constraints of AC_x's normal / default TXOP limit.

[0140] During AC_x's priority period 400, stations 392 can contend 402 for a channel and obtain a TXOP using high-priority EDCA parameters for packet transmission 404. For example, a backoff (HP BO as shown) can be generated by AC_x's high-priority EDCA parameter contention window. The TXOP reservation should comply with the constraints of the TXOP limit of AC_x's high-priority EDCA parameters.

[0141] During the non-priority period 406 of AC_x, the station 392 can contend 408 for the channel and obtain a TXOP using the low-priority EDCA parameters for packet transmission 410. For example, a backoff (LH BO as shown) can be generated by the low-priority EDCA parameter contention window of AC_x. The TXOP reservation should comply with the TXOP limit constraint of the low-priority EDCA parameters of AC_x.

[0142] 24 illustrates an example embodiment 430 for disabling channel contention for an AC using low-priority EDCA parameter settings. The illustrated topology, STAs, and normal and preferred periods are the same as those described for FIG.

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

[0144] 25 shows an example embodiment 450 in which the STAs have a non-preferred period after the preferred period of the AC. The topology and STAs, as well as the normal and preferred periods, are the same as those in FIG.

[0145] However, on the right side of the figure, a non-priority period 452 can be seen before the end of AC_x's LP-EDCA time. Therefore, station 392 should set AC_x's LP-EDCA timer when AC_x's priority period ends, immediately starting AC_x's non-priority period. AC_x's non-priority period continues until AC_x's LP-EDCA timer counts down to its end value (e.g., zero). In the figure, a low-priority backoff 454 is used to contend for transmission 456 to acquire the channel.

[0146] 26 shows an example embodiment 470 in which a STA delays between two priority periods of an AC. The STA and network topology are the same as those shown in FIGS.

[0147] The figure shows a priority period 476 for AC_x during which station 392 can contend for the channel (478) using high-priority EDCA parameters, obtain a TXOP, and perform a priority packet transmission (480). The figure also shows the minimum time between two consecutive priority periods 474 for AC_x. Note that block 482 represents the channel time between priority and non-priority periods. For example, a backoff (HP BO as shown) can be generated by the high-priority contention window for AC_x. TXOP reservations should obey the restrictions of the high-priority TXOP limit for AC_x.

[0148] STA1 or STA2 do not have to immediately switch to a non-priority period for AC_x after the end of the priority period for AC_x. The non-priority period for AC_x 484 can be scheduled at any time before the start of the next priority period for AC_x 490. When the non-priority period for AC_x begins, station 392 sets and counts down the LP-EDCA timer for AC_x as it contends 486 for the channel. In this example, the channel is acquired and packet transmission 488 is performed. The non-priority period ends when LP-EDCA timer 484 for AC_x counts down to zero.

[0149] Thereafter, another priority period 490 with high priority backoff 492 and priority packet transmission 494 can begin.

[0150] Figure 27 shows an example embodiment 510 in which a STA uses different EDCA parameters for non-priority packets during a priority period. The STA and network topology are the same as those shown in Figures 23-25.

[0151] When a STA transmits a non-priority packet during a priority period, the STA may also use either regular or LP EDCA parameters for channel contention.

[0152] During the normal period 514 of AC_x, the station 392 can contend 516 for the channel and obtain a TXOP using default EDCA parameters for packet transmission 518. For example, a backoff (normal BO as shown) can be generated by the normal / default contention window of AC_x. The TXOP reservation should obey the constraints of the normal / default TXOP limit of AC_x.

[0153] Thereafter, during AC_x's priority period 520, station 392 can contend for the channel and obtain a TXOP using high-priority EDCA parameters 522 for prioritized packet transmission 524. For example, a backoff (HP BO as shown) can be generated by the contention window of AC_x's high-priority EDCA parameters. The TXOP reservation should obey the constraints of the TXOP limit of AC_x's high-priority EDCA parameters.

[0154] The STA has a packet to transmit that is not a priority packet during the same priority period. The station 392 can contend 526 for the channel and obtain a TXOP using low-priority EDCA parameters for a normal packet transmission 528. For example, a backoff (LH BO as shown) can be generated by the low-priority contention window of AC_x. The TXOP reservation should obey the constraints of the low-priority TXOP limit of AC_x. The station 392 can also contend 526 for the channel and obtain a TXOP using normal EDCA parameters for a normal packet transmission 528.

[0155] Figure 28 shows an example embodiment 530 in which a STA simultaneously configures different mode periods for multiple ACs. The network topology is as shown in Figure 8. The example ACs used are AC_x and AC_y, which in these examples represent any AC in EDCA. STA1 is P-enabled, and the illustrated process remains the same if STA1 is replaced by an AP. Station 532 can also be STA2, as in the previous example.

[0156] STA1 is shown both transmitting and receiving on link 1. STA1 can configure normal periods 534 for both AC_x and AC_y simultaneously. During the normal periods, STA1 can contend for the channel and obtain a TXOP using default EDCA parameters. For example, the normal BO (backoff) for AC_y 538 and AC_x 536 as shown is generated by the normal / default contention windows of AC_y and AC_x, respectively. When AC_x and AC_y reserve a TXOP, their TXOP periods should be subject to the normal / default TXOP limits of AC_x and AC_y, respectively. In the figure, AC_x acquires the channel first and performs packet transmission 540, followed by AC_y acquiring the channel and performing packet transmission 542.

[0157] STA1 can also configure a period 544 that simultaneously includes a prioritized period for AC_x and a non-priority period for AC_y. During this time, STA1 contends for a TXOP using AC_x's high-priority EDCA parameters (546) and contends for a TXOP using AC_y's low-priority EDCA parameters (548). As shown, AC_y's LP BO represents the backoff formed by the contention window of AC_y's low-priority EDCA parameters. In this illustration, AC_x acquires the channel first and performs prioritized packet transmission 550, followed by packet transmission(s) for AC_y 552.

[0158] The TXOP duration of AC_y should not last longer than the TXOP limit of the low-priority EDCA parameters of AC_y. The HP BO of AC_x represents the backoff formed 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 of the high-priority EDCA parameters of AC_x.

[0159] Note that in such an example, it is possible that STA 532 does not need to schedule a non-preferred period for AC_x after the preferred period for AC_x.

[0160] Figure 29 shows an example embodiment 570 in which a STA uses preferred EDCA parameters of multiple ACs during a priority period. The network topology is the same as Figure 8. Note 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 are P-enabled and can be replaced by APs. STA1 and STA2 may not be associated with the same AP.

[0161] During the normal period, STA1 and STA2 can contend for the channel (578, 580) using default EDCA parameters and obtain a TXOP. For example, the normal BO (backoff) of AC_y and AC_x as shown is generated by the normal / default contention windows of AC_y and AC_x, respectively. When AC_x and AC_y reserve a TXOP, their TXOP time should be constrained by the normal / default TXOP limits of AC_x and AC_y, respectively. In the figure, STA1 of AC_x obtains the channel first and performs packet transmission(s) 582, followed by STA2 of AC_y performing packet transmission(s) 584.

[0162] A period 586 is then entered, which includes the preferred period for AC_x in STA1 and the non-preferred period for AC_y in STA2. During this time, STA1 performs backoff 588 using the high-priority EDCA parameters of AC_x, while STA2 contends for the channel with backoff 590 using the low-priority EDCA parameters of AC_y. As shown, the LP BO for AC_y represents the backoff formed by the contention window for the low-priority EDCA parameters of AC_y in STA2. The TXOP period for AC_y should not be longer than the TXOP limit for the low-priority EDCA parameters of AC_y. The HP BO for AC_x represents the backoff formed by the contention window for the high-priority EDCA parameters of AC_x in STA1. The TXOP period for AC_x should not be longer than the TXOP limit for the high-priority EDCA parameters of AC_x. This figure shows that STA1 first acquires the channel AC_x and performs priority packet transmission(s) 592, followed by STA2 acquiring the channel AC_y and performing packet transmission 594.

[0163] Figure 30 shows an example embodiment 610 of one AC of a STA using the backoff slot duration of the LP EDCA parameter during the priority period. The network topology is the same as that shown in Figure 8. The notation AC_i and AC_j represent either AC in EDCA. During the normal period of AC_i and AC_j, STA1 612 is P-capable. STA1 can be replaced with any type of STA without changing this example.

[0164] During normal period 614, the arbitration interval for frame transmission (AIFS) is shown as AIFS[i] 616 and AIFS[j] 618. It can be seen that STA1 uses the default backoff slot duration when contending for the channel of any AC. The duration of the AIFS of an AC can be calculated by the AIFSN number of that AC and the backoff slot duration during that period.

[0165] It can be seen that a period 620 is entered, including AC_i's preferred period and AC_j's non-preferred period, which ends before the HP-EDCA timer expires. During AC_j's non-preferred period, STA1 contends for the channel using the backoff slot durations as seen in the low-priority EDCA parameters to acquire AC_j's TXOP. For example, the duration of each of backoff slots 7 and 6 (622) is twice the duration of AC_j's normal backoff slots shown in slots 8-12, as used by AC_i 624. Given this difference, AC_i has a higher probability of acquiring the channel more easily than AC_j. STA1 acquires the channel and transmits its preferred packet 628, and AC_j finds its Clear Channel Assessment (CCA) busy 626.

[0166] Figure 31 shows an example embodiment 630 in which STAs use the backoff slot duration of the LP EDCA parameter during a priority period. The network topology is similar to Figure 8, showing STA1 632 and STA2 634, which are P-enabled. STA1 can be replaced by any type of STA. Again, AC_i and AC_j can represent any AC in EDCA. AC_i and AC_j can also be the same AC.

[0167] During the normal period 636 of AC_i and AC_j, STA1 or STA2 contends for the channel (642 and 644) using the default backoff slot duration and obtains the TXOP. Before backoff, AIFS[i] 638 and AIFS[j] 640 are seen.

[0168] Next, a new period 646 is entered, which is a priority period for STA2's AC_i (ending before the HP-EDCA timer expires) but a non-priority period for STA1's AC_j. During AC_j's non-priority period, STA1 should contend for the channel 647 and obtain a TXOP using the backoff slot durations in the low-priority EDCA parameters for AC_j. For example, the duration of each of backoff slots 7 and 6 (647) is twice the duration of AC_j's normal backoff slots 8 through 12, respectively. Therefore, AC_i has a higher probability of gaining channel access sooner than AC_j. During STA2's AC_i's priority period, the backoff slot duration can be set to the same as the normal period. In this figure, STA2 gains channel access for AC_i after backoff 648 and transmits a priority packet 652, while STA1 finds CCA busy 650 after backoff.

[0169] Figure 32 shows an example embodiment 670 in which a STA uses MU EDCA parameters for the preferred EDCA parameters during a preferred period. The network topology is similar to Figure 8, showing AP1 672, STA1 674, STA2 676, and STA3 678, all of which are P-enabled. Again, the notation AC_x and AC_y can refer to any AC within the EDCA.

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

[0171] STA1, STA2, and STA3 can contend for the channel using default MU EDCA parameters after completing the IEEE 802.11 trigger-based uplink transmission.

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

[0173] In response to TF 702, a data frame 704 is transmitted during the priority period of AC_x at STA1, after which the AP transmits BA 710. STA1 then begins counting down the MU EDCA timer for AC_x using the MU EDCA parameters for 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 for AC_x.

[0174] In response to TF 702, a data frame 706 is transmitted during the priority period of AC_y at STA2, after which the AP transmits BA 710. STA2 then begins counting down the MU EDCA timer for AC_y using the MU EDCA parameters for AC_y in the high priority (HP) MU EDCA parameters 714. The MU EDCA timer for AC_y is also set by the high priority EDCA parameters for AC_y.

[0175] In response to TF 702, a data frame 708 is transmitted during the non-priority period of STA3's AC_y, followed by the AP's transmission of BA 710. STA3 then begins counting down the MU EDCA timer for AC_y using the MU EDCA parameters for AC_y in 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 period is represented by 718.

[0176] 33 illustrates an example embodiment 730 in which a STA switches to using low priority MU EDCA parameters during a priority period. The network topology, notation, and stations are the same as those described for FIG.

[0177] This figure shows the same normal period actions for data uplinks 704, 706, and 708 from STA1, STA2, and STA3, respectively. However, in this figure, STA1 of AC_x begins counting down its MU EDCA timer for AC_x after transmitting data frame 704. It can be seen that if STA1 has more high priority traffic to send, it uses the AC_x MU EDCA parameters in the high priority (HP) MU EDCA parameters 732 while counting down its AC_x MU EDCA timer. The AC_x MU EDCA timer is also set by the AC_x high priority MU EDCA parameters.

[0178] After transmitting the data frame 706, STA2 begins counting down the MU EDCA timer for AC_x during the priority period of AC_x at STA2. If STA2 does not have any further high-priority traffic to transmit, it can use the MU EDCA parameters for AC_x in the low-priority (LP) MU EDCA parameters 734 while counting down the MU EDCA timer for AC_x. The MU EDCA timer for AC_x can also be set by the low-priority MU EDCA parameters for AC_x. Note that STA2 can also use the regular MU EDCA parameters instead of the low-priority MU EDCA parameters.

[0179] After transmitting data frame 708, STA3 uses the MU EDCA parameters for AC_y in the low priority (LP) EDCA parameters 736 while counting down the EDCA timer for AC_y during the non-priority period for AC_y at STA3. 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 period is 738.

[0180] Figure 34 shows an example embodiment 750 in which a STA uses multiple EDCA Functions (EDCAFs) for a single packet transmission. The network topology is as shown in Figure 8, and P-enabled STA1 has AC_x 752 and AC_y 754, which can represent either AC in the EDCAF.

[0181] STA1 contends for the channel to transmit Packet 1 using EDCAF for AC_x and AC_y. STA1 performs backoff 756 for AC_y, after which it sees that backoff 758 for AC_x begins. After backoff, it first obtains a TXOP for AC_x, followed by the first transmission 760 of Packet 1. However, the first transmission of Packet 1 fails, and STA1 begins backoff 762 for AC_x.

[0182] During this time, we can see that AC_y gets a TXOP and performs the first retransmission of packet 1 764. The first retransmission of packet 1 fails, and AC_x performs a second retransmission (766) of packet 1 after getting the next TXOP.

[0183] Figure 35 shows an example embodiment 770 in which 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 Figure 34. Note that this case occurs only if AC_x has a higher priority than AC_y.

[0184] STA1 contends for the channel to transmit a packet from AC_x using the EDCAFs of AC_x and AC_y. As shown, backoff 774 for AC_x begins when there are no packets to transmit for AC_y. STA1 first acquires a TXOP for AC_x and transmits a packet (776). Next, AC_y acquires a TXOP after its backoff 772 and transmits a packet 780 from AC_x only. At this time, AC_x is performing backoff 778 and continues to transmit a packet 782 from AC_x when it acquires the next TXOP.

[0185] If there are no packets from AC_y to transmit, the EDCAF of AC_y can start contending for the channel to transmit packets from AC_x. If there are packets from AC_x to transmit, the EDCAF of AC_y starts contending for the channel to transmit packets from AC_x.

[0186] 36A and 36B show an example embodiment 790 in which a STA uses prioritized EDCA and multiple EDCAFs to transmit packets from one AC. The network topology is similar to that of FIG. 8, where AC_x and AC_y can again represent any AC in the EDCA.

[0187] In this example, STA1 contends for the channel using EDCAF of AC_x and AC_y, and it should be understood that STA1 may also use more EDCAF of AC to contend for the channel.

[0188] During the normal period of AC_x and AC_y shown in Figure 36A, the EDCAFs of AC_x and AC_y contend for the channel and acquire TXOP independently by performing normal backoff 794, 796 for packets from AC_x and AC_y, respectively. The figure shows that a packet 798 from AC_x is transmitted, and after backoff of AC_y, it acquires a TXOP and transmits packet 800.

[0189] During the priority period 801 of AC_x and AC_y shown in Figure 36B, there are only priority 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 backoffs (BOs) 802 and 804 of AC_x and AC_y are configured using high priority (HP) EDCA parameters. As shown, after backoff, AC_x gets the TXOP first to transmit packet 806 from AC_x. Then, AC_y gets the TXOP to transmit packet 808 from AC_x only.

[0190] Entering the non-priority period 809 for AC_x and AC_y, the EDCAFs for AC_x and AC_y contend for the channel and obtain TXOP by performing backoffs 810 and 812 for packets from AC_x and AC_y, respectively. The backoffs (BO) for AC_x and AC_y in this case are configured using parameters for low priority (LP) EDCA. It can be seen that STA1 transmits a packet from AC_x 814, and after BO 812, transmits a packet from AC_y 816.

[0191] Figures 37A and 37B show an example embodiment 830 in which a STA uses prioritized EDCA and multiple EDCAFs to transmit packets from one AC. The network topology and STAs are the same as those in Figures 36A and 36B. Again, STA1 can use more of the AC's EDCAFs to compete for the channel.

[0192] The normal period shown in FIG. 37A is the same as the normal period shown in FIG. 36A.

[0193] The next period 832 shown in Figure 37B is a prioritized period for AC_x and a non-priority period for AC_y, where 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 (BOs) 834 and 836 for AC_x and AC_y are configured using high-priority (HP) and low-priority (LP) EDCA parameters, respectively. As shown, the backoff for AC_x first gets the TXOP to transmit a packet 838 from AC_x. Next, AC_y gets the TXOP to transmit a packet 840 from only AC_x.

[0194] The next period 842 is a non-priority period for AC_x. The EDCAFs for AC_x and AC_y contend for the channel and obtain a TXOP by performing backoffs 844 and 846 for packets from AC_x and AC_y, respectively. The backoffs (BO) for AC_x and AC_y as shown are configured using low priority (LP) EDCA parameters for AC_x and normal EDCA parameters for AC_y. STA1 first obtains the TXOP for AC_x and transmits packet 848, and then transmits packet 850 from AC_y after normal backoff 846 for AC_y.

[0195] Note that the non-preferred period of AC_y can be any type of period.

[0196] FIG. 38 illustrates an example embodiment 870 using different AIFS during a backoff procedure, such as when the backoff procedure spans different EDCA parameter setting periods. For example, consider an ongoing backoff procedure in which the STAs may continue the countdown procedure using different AIFS. The AIFS may be determined by the EDCA parameter setting as the STA continues backoff. The network topology is shown in FIG. 8. This figure illustrates operation during a normal period 874 of AC_x on a P-enabled station (e.g., STA1 or STA2) 392. STA1 / STA2 represent one P-enabled STA that may or may not belong to an MLD. STA1 or STA2 may also be replaced by an AP.

[0197] During the normal period 874 of AC_x, STA1 or STA2 begins contending for the channel 880 by invoking a backoff procedure 882 for AC_x. The backoff may set a backoff counter for AC_x using the default EDCA parameters for AC_x. STA1 or STA2 may then begin counting down the backoff 886 using the AIFSN 884 in the default EDCA parameters for AC_x.

[0198] The backoff counter does not count down to zero during the normal period, but pauses only during CCA busy 888 periods that extend beyond AC_x's normal period 874 and into AC_x's priority period 876. If a STA 890 with an AIFSN in the high priority EDCA parameters 892 continues countdown backoff 894 for AC_x during AC_x's priority period, this is used for AC_x.

[0199] If the backoff counter does not reach zero during AC_x's priority period 876, such as due to a CCA busy 896, the station may continue 898 counting down the backoff during AC_x's non-priority period 878. Because a CCA busy existed during AC_x's priority period, the STA may continue the backoff countdown 902 procedure using the AIFSN in AC_x's low priority EDCA parameters 900 after the CCA busy. The STA then knows to perform its packet transmission 904.

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

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

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

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

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

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

[0206] 1. An apparatus for wireless communication in a network, comprising: (a) a wireless station (STA) operating as either an access point (AP) STA or a non-AP STA on a wireless local area network (WLAN) employing carrier sense multiple access with collision avoidance (CSMA / CA); and (c) a non-transitory memory storing instructions executable by the processor for communicating with other STAs, the instructions, when executed by the processor, perform one or more steps including: (i) configuring an EDCA function to operate using a plurality of single-user or multi-user (MU) EDCA operating parameter sets providing different ranges of priority levels, each of which provides a different level of nominal access time to be used by the STA for different periods of time when contending for the at least one channel; (ii) utilizing a high-priority single-user or multi-user (MU) EDCA operating parameter set when the STA needs to speed up channel access; and (iii) utilizing a low-priority EDCA operating parameter set when the STA needs to slow down channel access.

[0207] An apparatus for wireless communication in a network, comprising: (a) a wireless communication circuit configured to, as a wireless station (STA) operating as either an access point (AP) STA or a non-AP STA, communicate wirelessly over a channel with other wireless stations (STAs), either AP or non-AP STAs, on a wireless local area network (WLAN) employing carrier sense multiple access with collision avoidance (CSMA / CA); (b) a processor coupled to the wireless communication circuit and operating as an STA on the WLAN; and (c) a non-transitory memory storing instructions executable by the processor for communicating with other STAs, wherein (d) the instructions, when executed by the processor, (d)(i) configure an EDCA function to operate using a plurality of single EDCA or multi-user (MU) EDCA operating parameter sets providing various ranges of priority levels, each providing a different level of nominal access time for STAs to use at different time periods when contending for the at least one channel, and (d)(ii) the plurality of single EDCA or MU-EDCA operating parameter sets providing a back-off slot period that is variable in response to a change between the plurality of single EDCA or MU-EDCA operating parameter sets. and (d)(iii) utilizing a high-priority single-EDCA or multi-user (MU)-EDCA operating parameter set when the STA needs to speed up channel access by shortening the nominal channel access time, and (d)(iv) utilizing a low-priority EDCA operating parameter set when the STA needs to slow down channel access to compensate for using the high-priority EDCA operating parameter set, wherein (d)(v) the STA is configured to simultaneously utilize single-EDCA or MU-EDCA operating parameters of different priority levels for backoff based on different ACs; and (d)(vi) limiting the amount of time the STA can continuously use the high-priority single-EDCA or MU-EDCA operating parameters configured for an Access Category (AC).

[0208] A wireless communication method 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 over a channel with other wireless stations (STAs), which are APs or non-AP STAs, on a wireless local area network (WLAN) employing carrier sense multiple access with collision avoidance (CSMA / CA); (b) configuring an EDCA function to operate using multiple single-EDCA or multi-user (MU) EDCA operating parameter sets providing different ranges of priority levels, each providing a different level of nominal access time to be used by the STA at different periods when contending for the at least one channel; (c) utilizing a high-priority single-EDCA or multi-user (MU) EDCA operating parameter set when the STA needs to speed up channel access; and (d) utilizing a low-priority EDCA operating parameter set when the STA needs to slow down channel access.

[0209] A wireless communication device in which a STA transmits packets using CSMA / CA with one default EDCA parameter set, the device including: (a) the STA has multiple EDCA parameter sets and uses them at different time periods; (b) the STA uses a high-priority EDCA parameter set when it needs to speed up channel access compared to the default set; and (c) the STA uses a low-priority EDCA parameter set when it needs to slow down channel access compared to the default set.

[0210] An apparatus or method of any preceding implementation, wherein the nominal channel access time for priority traffic transmission is reduced by utilizing a high priority single EDCA or multi-user (MU) EDCA operating parameter set.

[0211] The apparatus or method of any preceding implementation, wherein the instructions, when executed by a processor, further perform a step including switching the STA to a low-priority single-EDCA or MU-EDCA operating parameter set to compensate for the STA's use of a high-priority EDCA operating parameter set.

[0212] The apparatus or method of any preceding implementation, wherein the instructions, when executed by a processor, further perform a step including limiting a period of time during which the STA can continuously use a high-priority single EDCA or MU-EDCA operating parameter set configured for an access category (AC).

[0213] 10. The apparatus or method of any preceding implementation, wherein the plurality of operational parameter sets includes a normal operational parameter set having a default priority, a high priority (HP) operational parameter set, and a low priority (LP) operational parameter set.

[0214] 11. The apparatus or method of any preceding implementation, wherein the normal operating parameter sets are loaded to match default single-EDCA and multi-user (MU) EDCA parameter settings of an IEEE 802.11ax protocol.

[0215] The apparatus or method of any preceding implementation, wherein the plurality of single-EDCA or MU-EDCA operating parameter sets are configured by communications received from an AP associated with the STA.

[0216] The apparatus or method of any preceding implementation, wherein the multiple single-EDCA or MU-EDCA operating parameter sets are configured by communication from a STA associated with the AP through the use of a beacon frame, a probe response frame, or a (re)association response frame.

[0217] The apparatus or method of any preceding implementation, wherein the instructions, when executed by a processor, further perform a step including the plurality of single EDCA or MU-EDCA operating parameter sets including a backoff slot duration parameter that enables a backoff slot duration to be dynamically set in response to changes between the plurality of single EDCA or MU-EDCA operating parameter sets.

[0218] The apparatus or method of any preceding implementation, wherein the plurality of single-EDCA or MU-EDCA operating parameter sets can be set in response to receiving a frame in a communication.

[0219] 2. The apparatus of claim 1, wherein the instructions, when executed by the processor, further perform steps including the STA simultaneously using single-EDCA or MU-EDCA operating parameters at different priority levels for backoff based on different ACs.

[0220] The apparatus or method of any preceding implementation, wherein the instructions, when executed by a processor, further perform steps including operating as an AP utilizing one single EDCA or MU-EDCA operating parameter set during a period of time, while the station utilizes multiple EDCA capabilities to transmit packets from a single AC and contend for a channel to obtain a TXOP.

[0221] The apparatus or method of any preceding implementation, wherein the instructions, when executed by a processor, further perform a step including forcing the STA that was utilizing a high-priority single-EDCA or MU-EDCA operating parameter set to use a low-priority operating parameter set for a period of time to compensate for the previous use of the high priority.

[0222] An apparatus or method of any preceding implementation in which a STA having multiple EDCA parameter sets can be configured by its associated AP via a beacon frame.

[0223] An apparatus or method of any preceding implementation, wherein an AP can configure a STA with multiple EDCA parameter sets via a probe response frame.

[0224] An apparatus or method of any preceding implementation in which a STA with multiple EDCA parameter sets can be configured by its associated AP via a (re)association response frame.

[0225] The apparatus or method of any preceding implementation, wherein a STA with multiple EDCA parameter sets can dynamically configure backoff slot durations.

[0226] The apparatus or method of any preceding implementation, wherein a STA having multiple EDCA parameter sets can be configured for frames transmitted over other links.

[0227] The apparatus or method of any preceding implementation, wherein a STA having multiple EDCA parameter sets can simultaneously use a low-priority EDCA parameter set of one AC and a high-priority EDCA parameter and MU EDCA parameter set of another AC.

[0228] An apparatus or method of any preceding implementation that can force a STA using a high-priority EDCA parameter set to use a low-priority EDCA parameter set for a period of time after using the high-priority EDCA parameter set.

[0229] The apparatus or method of any preceding implementation, wherein an AP using one EDCA parameter set during a period can contend for a channel and obtain a TXOP using multiple EDCAFs to transmit packets from only one AC.

[0230] The term "implementation," as used herein, is intended to include, without limitation, any embodiment, example, or other form for practicing the techniques described herein.

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

[0232] In this disclosure, phrases such as "A, B, and / or C" indicate that either A, B, or C, or any combination of items A, B, and C, can be present. Phrases such as "at least one of" followed by a group of listed elements indicate that at least one of the group of elements is present, including, where applicable, any possible combination of the listed elements.

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

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

[0235] Use of relative terms such as first and second, top and bottom, etc. in this document is used merely to distinguish one entity or action from another and does not necessarily require or imply any such actual relationship or ordering between such entities or actions.

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

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

[0238] Additionally, amounts, ratios, and other numerical values ​​may be presented in range format herein. Such range formats are used for convenience and simplicity, and should be understood to include numerical values ​​explicitly specified as the limits of the range, but also to include all individual numerical values ​​or subranges within the range, as if each such numerical value and subrange were expressly set forth. For example, a ratio within the range of about 1 to about 200 should be understood to include the explicitly recited limits of about 1 and about 200, but also to include individual ratios such as about 2, about 3, and about 4, as well as subranges such as about 10 to about 50 and about 20 to about 100.

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

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

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

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

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

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

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

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

[0247] 112 Start 114 What type of period is P-enabled STA within for AC? 116 P-capable STAs contend for the channel using normal EDCA and MU-EDCA parameters for AC and obtain TXOP 118 P-capable STAs contend for the channel using high-priority EDCA and MU-EDCA parameters for AC and obtain TXOP 120 P-capable STAs contend for the channel using low-priority EDCA and MU-EDCA parameters for AC and obtain TXOP Table 1A Typical EDCA / MU EDCA parameter setting example TIFF0007801342000001.tif78143 “BO” - Backoff slot duration (in uS); “TXOP” - TXOP timer (mS) Table 1B High Priority EDCA / MU EDCA Parameter Setting Example TIFF0007801342000002.tif78143 “BO” - Backoff slot duration (in uS); “TXOP” - TXOP timer (mS) Table 1C Low Priority EDCA / MU EDCA Parameter Setting Example TIFF0007801342000003.tif73133 “BO” - Backoff slot duration (in uS); “TXOP” - TXOP timer (mS)

Claims

1. 1. An apparatus for wireless communication in a network, comprising: (a) a wireless communication circuit configured to, as a wireless station (STA) operating as either an access point (AP) STA or a non-AP STA, communicate wirelessly over a channel with other wireless stations (STAs), either AP or non-AP STAs, on a wireless local area network (WLAN) employing carrier sense multiple access with collision avoidance (CSMA / CA); (b) a processor coupled to the wireless communication circuitry and operating as a STA on a WLAN; (c) a non-transitory memory storing instructions executable by the processor for communicating with other STAs; (d) the instructions, when executed by the processor, (i) configuring an EDCA function to operate using multiple sets of single EDCA or multi-user (MU) EDCA operating parameters providing various ranges of priority levels, each set providing different levels of channel access time for the STAs to use at different time periods when contending for at least one of the channels, and for the STAs to simultaneously use the single EDCA or MU-EDCA operating parameters with different priority levels for backoff based on different ACs; (ii) utilizing a high-priority set of the single-EDCA or MU-EDCA operating parameters when the STA needs to speed up channel access; (iii) utilizing a lower priority set of the single-EDCA or MU-EDCA operating parameters when the STA needs to slow down channel access; performing one or more steps including An apparatus characterized in that

2. Utilizing a high priority set of the single EDCA or MU-EDCA operating parameters reduces channel access time for prioritized traffic transmissions.

10. The apparatus of claim 1.

3. The instructions, when executed by the processor, further perform a step including switching to a lower priority set of the plurality of sets of single EDCA or MU-EDCA operating parameters to compensate for the STA utilizing a higher priority set of the plurality of sets of single EDCA or MU-EDCA operating parameters.

10. The apparatus of claim 1.

4. The instructions, when executed by the processor, further perform the step of limiting a period of time during which the STA may continuously use a higher priority set of the single EDCA or MU-EDCA operating parameters set for an access category (AC).

10. The apparatus of claim 1.

5. the plurality of sets of single-EDCA or MU-EDCA operating parameters include a normal operating parameter set with default priority, a high priority (HP) operating parameter set, and a low priority (LP) operating parameter set; 10. The apparatus of claim 1.

6. The normal operating parameter set 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 5.

7. the multiple sets of single-EDCA or MU-EDCA operating parameters are configured by communications received from an AP associated with the STA; 10. The apparatus of claim 1.

8. The multiple sets of single-EDCA or MU-EDCA operating parameters are configured by communications from STAs associated with an AP through the use of beacon frames, probe response frames, or (re)association response frames.

10. The apparatus of claim 1.

9. The instructions, when executed by the processor, further perform the step of: the multiple sets of single EDCA or MU-EDCA operational parameters including a backoff slot duration parameter that enables a backoff slot duration to be dynamically set in response to changes between the multiple sets of single EDCA or MU-EDCA operational parameters.

10. The apparatus of claim 1.

10. The multiple sets of single-EDCA or MU-EDCA operational parameters may be set in response to receiving a frame in a communication.

10. The apparatus of claim 1.

11. The instructions, when executed by the processor, further perform steps including operating as an AP utilizing a single EDCA or MU-EDCA operating parameter set during a period of time while the STA utilizes multiple EDCA capabilities to transmit packets from a single AC and contend for a channel to obtain a TXOP.

10. The apparatus of claim 1.

12. The instructions, when executed by the processor, further perform the step of forcing the STA that was utilizing a higher priority set of the multiple sets of single EDCA or MU-EDCA operating parameters to use a lower priority set of the multiple sets of single EDCA or MU-EDCA operating parameters for a period of time to compensate for the previous higher priority use.

10. The apparatus of claim 1.

13. 1. An apparatus for wireless communication in a network, comprising: (a) a wireless communication circuit configured to, as a wireless station (STA) operating as either an access point (AP) STA or a non-AP STA, communicate wirelessly over a channel with other wireless stations (STAs), either AP or non-AP STAs, on a wireless local area network (WLAN) employing carrier sense multiple access with collision avoidance (CSMA / CA); (b) a processor coupled to the wireless communication circuitry and operating as a STA on a WLAN; (c) a non-transitory memory storing instructions executable by the processor for communicating with other STAs; (d) the instructions, when executed by the processor, (i) configuring an EDCA function to operate using multiple sets of single EDCA or multi-user (MU) EDCA operating parameters providing various ranges of priority levels, each providing different levels of channel access time for the STAs to use during different periods when contending for at least one of the channels; (ii) the multiple sets of single-EDCA or MU-EDCA operating parameters include a back-off slot duration parameter that enables a back-off slot duration to be dynamically configured in response to changes between the multiple sets of single-EDCA or MU-EDCA operating parameters; and (iii) utilizing a high-priority set of the single-EDCA or multi-user (MU)-EDCA operating parameters when the STA needs to speed up channel access by reducing channel access time; and (iv) utilizing a lower priority set of the single-EDCA or multi-user (MU)-EDCA operating parameters when the STA needs to slow down channel access to compensate for utilizing a higher priority set of the single-EDCA or multi-user (MU)-EDCA operating parameters; (v) the STA is configured to simultaneously utilize single EDCA or MU-EDCA operating parameters of different priority levels for backoff based on different ACs; and (vi) limiting the time for which the STA can continuously use a higher priority set of the single EDCA or MU-EDCA operation parameters configured for an access category (AC); and performing one or more steps including An apparatus characterized in that

14. the plurality of sets of single-EDCA or MU-EDCA operating parameters include a normal operating parameter set having a default priority, a high priority (HP) operating parameter set, and a low priority (LP) operating parameter set; 14. The apparatus of claim 13.

15. The normal operating parameter set is loaded to match the default single-EDCA and multi-user (MU)-EDCA parameter settings of the IEEE 802.11ax protocol.

15. The apparatus of claim 14.

16. the multiple sets of single-EDCA or MU-EDCA operating parameters are configured by communications received from an AP associated with the STA; 14. The apparatus of claim 13.

17. The multiple sets of single-EDCA or MU-EDCA operating parameters are configured by communications from STAs associated with an AP through the use of beacon frames, probe response frames, or (re)association response frames.

14. The apparatus of claim 13.

18. The multiple sets of single-EDCA or MU-EDCA operational parameters may be set in response to receiving a frame in a communication.

14. The apparatus of claim 13.

19. A wireless communication method in a network, 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 another wireless station (STA), which may be an AP or a non-AP STA, in a wireless local area network (WLAN) employing carrier sense multiple access with collision avoidance (CSMA / CA); (b) configuring an EDCA function to operate using multiple sets of single EDCA or multi-user (MU) EDCA operating parameters providing various ranges of priority levels, each set providing different levels of channel access time for the STAs to use at different time periods when contending for at least one of the channels, and for the STAs to simultaneously use the single EDCA or MU-EDCA operating parameters with different priority levels for backoff based on different ACs; (c) utilizing a high-priority set of the 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 the single-EDCA or MU-EDCA operating parameters when the STA needs to slow down channel access; A method comprising:

Images