Patent Description:
A wireless local area network (WLAN) may be formed by one or more access points (APs) that provide a shared wireless communication medium for use by a number of client devices also referred to as stations (STAs). The basic building block of a WLAN conforming to the Institute of Electrical and Electronics Engineers (IEEE) <NUM> family of standards is a Basic Service Set (BSS), which is managed by an AP and including one or more wirelessly connected STAs. A station (STA) may have a wireless connection (referred to as a wireless association, or just "association") when it has authenticated and established a wireless session with the AP. One or more STAs in the WLAN may utilize the shared wireless communication medium to communicate with the AP, and vice versa. The AP and STAs may use a contention-based access scheme to determine which WLAN device can use the shared wireless communication medium at a particular time. It is desirable for an AP to enable priority access for certain STAs to transmit or receive communications via the shared wireless communication medium. <CIT> relates to various systems, methods, and non-transitory computer-readable mediums for providing a quality of service (QoS) level for communication between a wireless device and a wireless local area network (WLAN). A user classification may be determined for a user associated with a wireless device. An access class (AC) associated with a set of data to be exchanged between the wireless device and the access point (AP) of the WLAN may be determined. Using the user classification and the AC associated with the set of data to be exchanged between the wireless device and the access point of the WLAN, a priority of the set of data may be established. The set of data may be exchanged between the wireless device and the access point of the WLAN in accordance with the determined priority. Document vol. <NUM> EHT, XP068164287 relates to methods introducing priority access support in IEEE <NUM> The for National Security and Emergency Preparedness (NS/EP) priority services with additional applicability. Document <CIT> relates to a contention-based communications channel access method emulating scheduled access by dynamically updating Enhanced Distribution Channel Access (EDCA) parameters for groups of member stations in a Wireless Local Area Network (WLAN).

The claimed invention is defined by the independent claims. Further embodiments of the claimed invention are described in the dependent claims. The systems, methods, and devices of this disclosure each have several innovative aspects, no single one of which is solely responsible for the desirable attributes disclosed herein.

The following description is directed to some particular implementations for the purposes of describing innovative aspects of this disclosure. However, a person having ordinary skill in the art will readily recognize that the teachings herein can be applied in a multitude of different ways. The described implementations can be implemented in any device, system or network that is capable of transmitting and receiving radio frequency (RF) signals according to one or more of the Institute of Electrical and Electronics Engineers (IEEE) <NUM> standards, the IEEE <NUM> standards, the Bluetooth® standards as defined by the Bluetooth Special Interest Group (SIG), or the Long Term Evolution (LTE), <NUM>, <NUM> or <NUM> (New Radio (NR)) standards promulgated by the 3rd Generation Partnership Project (3GPP), among others. The described implementations can be implemented in any device, system or network that is capable of transmitting and receiving RF signals according to one or more of the following technologies or techniques: code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), single-user (SU) multiple-input multiple-output (MIMO) and multi-user (MU) MIMO. The described implementations also can be implemented using other wireless communication protocols or RF signals suitable for use in one or more of a wireless personal area network (WPAN), a wireless local area network (WLAN), a wireless wide area network (WWAN), or an internet of things (IOT) network.

A wireless local area network (WLAN, sometimes also referred to as a Wi-Fi™ network) in a home, apartment, business, or other area may include one or more WLAN devices. An access point (AP) is a WLAN device that includes a distribution system access function. An AP may provide a wireless coverage area for devices to access the WLAN via a wireless channel. The AP may provide distribution system access for one or more stations (STAs, sometimes also referred to as non-AP STAs) that are associated with the AP. The basic building block of a WLAN is a Basic Service Set (BSS), which is managed by an AP and includes one or more STAs associated with the AP. STAs can establish a wireless association (also referred to as a wireless link wireless connection, among other examples) with an AP via the wireless channel to join the BSS. Once the STA has a wireless association with the AP, the STA may communicate with other devices of the WLAN or of another network via the distribution system access function of the AP.

A contention-based access scheme may be used to determine which WLAN device (such as an AP or a STA) can use the wireless channel at a particular time. The contention-based access scheme may influence the distribution of resources available in the shared wireless channel. Using contention-based access, each WLAN device may contend for access to the wireless channel. To prevent collisions, each WLAN device may observe the wireless channel before attempting to transmit. If the wireless channel is busy (by another device), the device may wait for a random backoff time period before checking the wireless channel again. If the wireless channel is free, the WLAN device may contend for access the network. Multiple WLAN devices may contend at the same time. Enhanced Distributed Channel Access (EDCA) is an example of a contention-based access protocol. The examples of contention-based access techniques in this disclosure are based on EDCA. However, other types of contention-based access and contention parameters may be used. Using EDCA, a set of parameters (referred to as EDCA parameters) may be associated with a particular access class (AC) and level of priority. Different access categories (having different levels of priority) may have different contention parameters that impact the likelihood that a STA will win contention for the wireless channel. Examples of contention parameters include contention window boundaries (CWmin, CWmax), arbitration interframe space number (AIFSN), and a backoff algorithm. In addition to defining rules for the contention, EDCA permits a winner of a contention to use the wireless channel for a period of time called a transmission opportunity (TXOP). Several factors may impact which device wins the contention. Depending on the quantity of devices contenting for access and the TXOP duration, some devices may be prevented from transmitting or receiving important wireless communications. It is desirable to provide some WLAN devices with higher priority access to the shared wireless channel. For example, national security and emergency preparedness (NSEP) personnel may benefit from having a higher priority or lower latency when using a shared wireless channel. Examples of NSEP personnel may include first responders and law enforcement officers.

This disclosure provides systems, methods, and apparatus, including computer programs encoded on computer-readable media, enabling priority access by a particular STA in a wireless local area network. Various implementations relate generally to managing contention-based access settings to enable priority access for one or more STAs (which may be referred to as a priority STA or NSEP STA, among other examples). In some implementations, the priority STA may use different EDCA parameters (such as more aggressive contention window times, shorter interframe space, and longer TXOP compared to other STAs) to ensure or improve the likelihood of the priority STA winning a contention for the wireless channel. Other STAs that do not support the priority access service or are not authorized to use the priority access service may be referred to as non-priority STAs. In some implementations, the non-priority STAs may use less aggressive EDCA parameters (compared to the priority STA) to provide more opportunity for the priority STA to win contention for the wireless channel.

Priority Access provides priority to system resource access for authorized users to enhance their probability of successful communication during periods of network congestion. Priority access involves preferential treatment in obtaining channel access and in allocation of network resources. The priority access service (also referred to as priority access mode) is only available to designated, authorized individuals or devices. When an authorized user or a managed service provider determines a need for priority, it may invoke the priority access service in an on-demand fashion in accordance with the examples described herein.

In all implementations, a priority STA invokes a priority access service by sending a request to the AP. The priority STA transmits a frame that includes a priority access indication. The priority access indication may be included in a transmission, such as a physical layer convergence protocol (PLCP) protocol data unit (PPDU). In all implementations, the priority access indication is included in a preamble or a physical layer (PHY) header of the PPDU. In some implementations, the priority STA also may signal a priority service duration. The priority service duration may inform other devices of an amount of time the priority STA intends to use the priority access service. The priority service indication or the priority service duration (or both) may be signaled as one or more bits of the preamble or PHY header of the PPDU. In some implementations, when a priority STA activates a priority access service in a BSS, other priority STAs associated with the BSS may use the priority access service.

In some implementations, a priority STA may transmit a priority service request frame indicating a request to utilize a priority access service. The AP may be configured to verify that the priority STA is authorized to use the priority access service and respond with a priority access response frame. If the priority STA is authorized to use the priority access service, the AP and the priority STA may manage transmission of traffic to and from the priority STA in accordance with the priority access service. In some implementations, managing transmission of the traffic to and from the priority STA can include using preferential treatment. Alternatively, or additionally, an AP may detect a need for priority access by a priority STA. Thus, in some implementations, the AP invoke the priority access service by sending a priority service request frame to the priority STA.

In some implementations, an AP may adjust or select the contention parameters to support the priority access by the priority STA. Referring to the example using EDCA for contention-based access, EDCA currently defines four access classes (ACs) based on type of traffic. ACs may refer to an "access class" or an "access category" interchangeably. In some implementations, each traffic stream from a STA may be associated with a particular AC and may use a set of EDCA parameters related to that AC. The ACs may include background, best effort, voice, and video access classes. For example, a background access category (AC_BK) may have a lower quality of service compared to a best effort access category (AC_BE). A voice access category (AC_VO) may have a higher quality of service than the AC_BE. A video access category (AC_VI) may have a higher quality of service than the AC_VO. In some implementations, the priority access service may be associated with the AC_VO access class while prioritizing the traffic to or from the priority STA above traffic for non-priority STAs using the AC_VO access class. In some implementations, the AP may redefine the access categories or adjust the contention parameters for a priority STA. Additionally or alternatively, the AP may adjust the contention parameters of non-priority STAs to enable a priority STA to have a higher priority. As an example, the AP may provide more aggressive EDCA contention parameters to a priority STA or provide less aggressive EDCA contention parameters to non-priority STAs. The final outcome of the adjustment of the EDCA contention parameters (for either or both of the priority STA or the non-priority STAs) is that a priority STA has higher priority when contending for the medium to transmit priority traffic.

In some implementations, one or more new access categories may be defined to have a greater level of priority than existing access categories. In some implementations, the priority access service is defined by a priority access class (AC_PRI) that has a higher quality of service compared to existing access classes defined for EDCA (including the AC_BK, AC_BE, AC_VO, and AC VI). Because the AC_PRI may not be recognized by legacy STAs that only recognize the existing four access classes, it is possible that the legacy STAs may not recognize the AC_PRI and may fail to defer to the priority STA. Therefore, in some implementations, an AP may modify one or more settings (such as the EDCA parameters) for the existing access classes to weaken contention-based access for STAs using the existing access classes.

In some implementations, an AP may adjust the EDCA parameters for non-priority STAs so that the non-priority STAs get a lower priority compared to the priority STA. For example, the AP can adjust the EDCA parameters (also referred to as an EDCA set) for existing access classes to be less aggressive. In some implementations, the AP may create a new EDCA set for the priority STA based on existing EDCA parameters for an access class while the existing EDCA parameters for that access class are downgraded. Whichever EDCA parameters for various access classes are modified, the result is that priority STAs have a higher priority compared to non-priority STAs.

In some implementations, non-priority STAs may modify their respective EDCA parameters or TXOP duration limits to back off utilization of the wireless channel so that the priority STAs will have more likelihood of winning contention. For example, the non-priority STAs may adjust their contention parameters to weaken contention-based access for the existing access classes. In some implementations, non-priority STAs may modify a backoff algorithm or contention window boundaries so that the priority STA can have a higher likelihood of winning contention. For example, the non-priority STA may disable a minimum contention window size (CWmin) or upper limit for a random backoff counter. Thus, the non-priority STA may be less aggressive in retrying a contention. In some implementations, the random backoff counter may be selected from a range from zero to one less than a maximum contention window size (CWmax). The priority STA will continue to use the CWmin which will give the priority STA a smaller range for selecting an initial random backoff counter. In some implementations, the non-priority STAs may add an offset value to the contention window boundaries (CWmin, CWmax) or arbitration interframe space number (AIFSN). Alternatively, or additionally, the non-priority STAs may decrease a TXOP duration limit by an offset value. In some implementations, the AP may signal an offset value or other setting to modify the CWmin, the CWmax, the AIFSN, or the TXOP duration. Alternatively, or additionally, the offset value or other setting may be specified in a standard technical specification.

In some implementations, a first AP that manages a first BSS may support priority access for a priority STA even if the priority STA is not associated with the first BSS. As more WLANs are deployed in an environment, the wireless medium may be shared by many BSSs. For example, a first AP may manage a first BSS via the same wireless channel utilized by a second AP managing a second BSS. BSSs that share a wireless channel in the same location may be referred to as neighboring BSSs or overlapping BSSs (OBSSs). In some implementations, the priority STA may be associated with an OBSS (such as a second BSS) that uses a same wireless channel as the first BSS. The first AP may determine that the priority STA is utilizing the priority access service. For example, the first AP may detect a transmission from the priority STA in the OBSS. The first AP may observe a preamble or PHY header of the transmission for a priority access indication. If the first AP detects a priority access indication for any device (either in its BSS or in an OBSS), the first AP may signal a priority service enablement indicator to the first BSS. The priority service enablement indicator may cause STAs in the first BSS to weaken their contention parameters or otherwise give preferential treatment for the priority STA to access the wireless channel.

In some implementations a first AP may inform a second AP when the priority service is activated. In general, a first AP has control of the EDCA parameters of the STAs (priority STAs or non-priority STAs) that are associated to it. It may be desirable to adjust EDCA parameters for non-priority STAs that are associated to the second AP so that a priority STA associated with the first AP can have a higher priority over non-priority STAs in an OBSS managed by the second BSS. Thus, in some implementations, the first AP may request or instruct a second AP in the vicinity (or any other APs managing an OBSS) to cause non-priority STAs to update the EDCA contention parameters in their respective BSSs. For example, the first AP may send a message (via a wireless or wired communication media or via a service provider network) to a second AP to inform the second AP that the priority service has been activated by a priority STA in a first BSS managed by the first AP. The second AP may be expected to adjust the EDCA contention parameters for STAs in a second BSS managed by the second AP to support the priority service for the priority STA in the first BSS.

In some implementations, a non-priority STA may assist with an AP determining that a priority-STA is utilizing a priority access service. For example, a non-priority STA may detect a transmission from the priority STA that includes a priority access indication. The non-priority STA may signal a priority detection indicator to its respective AP to cause its AP to support the priority access. When the AP receives the priority detection indicator, the AP may signal a priority service enablement indicator to its BSS. Furthermore, in some implementations, the AP may signal changes to contention parameters for existing access classes. Thus, legacy STAs in the BSS may weaken their contention parameters even if they do not recognize the priority access service and even if the priority STA is in an OBSS.

In some implementations, an AP may advertise the access modes (including the priority access mode) and access classes that the AP supports. For example, the AP may include an indication, in a beacon message or probe response message, that the AP supports the priority access service. A priority STA may select an AP that supports the priority access service. In some implementations, when a priority STA or the AP activates the priority access service, the priority access service may be used for all traffic between the AP and the priority STA. Alternatively, the AP or the priority STA may use the priority access service for particular frames (such as those that include emergency communications).

This disclosure includes various techniques for an AP to set different contention parameters for different access classes used by STAs in its BSS. For example, the AP may include an EDCA Parameter Set element in a management frame (such as a Beacon, Probe Response, or Association Response, among other examples). In some implementations, the AP may indicate to a particular STA to use another access class so that a priority STA can have a higher quality of service. The AP may signal the change in a frame to a particular STA or to all STAs using the legacy access classes. Furthermore, in some implementations, an AP may transmit a beacon frame or other management frame that includes a priority service activation notification so that any STAs or other APs in the vicinity of the priority STA may become aware that the priority service has been activated. Any non-priority STAs or other APs may adjust the EDCA contention parameters to enable the priority STA to gain a higher priority access to the wireless channel.

In some implementations, the AP or the priority STA also may indicate to the non-priority STAs the duration of time (priority service event duration) for which the priority access service is valid. Thus, the AP or the priority STA can selectively turn on and turn off the priority access service either by enabling a priority access service for traffic to and from the priority STA, by the use of the priority access indication in particular transmissions, by enabling the priority access service for an indicated priority service event duration.

In some implementations, an AP may determine that a STA is abusing the priority access service to transmit non-priority traffic. For example, a non-priority STA may attempt to use the priority access service without authorization. The AP may authorize the priority access service based on a network configuration, manufacturer configuration, or device setting. However, if a STA does not have authorization to use the priority access service, the AP may take countermeasures against the STA. For example, the AP may disassociate the STA or may modify one or more settings for the other STAs to redistribute the contention likelihood for the other STAs.

In some implementations, an AP that supports a priority access service may advertise this capability in Beacon and Probe Response frames. A priority STA may query the AP to gain additional details prior to association. During association, the AP may verify the authority of a requesting STA to use the priority access service. This may be accomplished using a subscription service provider's authorization infrastructure via a subscription service provider network (SSPN) interface. In some implementations, the AP may store the results of this authorization process locally to enable subsequent verification. An AP also may use this information to confirm authority during an association or a reassociation request from a priority STA. For example, the AP may confirm the authority of the priority STA to use the priority access service (such as using the locally stored verification information or reaching out to an NSEP Service Provider via the SSPN interface).

Particular implementations of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. A priority STA can share the priority access service while non-priority STAs may use a lower quality of service (QoS) relative to the priority STA. NSEP personnel can obtain priority access service to enhance their probability of successful communication during periods of network congestion. By modifying the EDCA parameters for the priority STA or non-priority STAs, an AP may provide the priority access service to the priority STA even though non-priority STAs may be legacy devices. Advantageously, some implementations of this disclosure enable priority access for a priority STA regardless of whether the priority STA is associated with an OBSS.

<FIG> shows a pictorial diagram of an example wireless communication network <NUM> that supports priority access according to some implementations. According to some aspects, the wireless communication network <NUM> can be an example of a wireless local area network (WLAN) such as a Wi-Fi network (and will hereinafter be referred to as WLAN <NUM>). For example, the WLAN <NUM> can be a network implementing at least one of the IEEE <NUM> family of wireless communication protocol standards (such as that defined by the IEEE <NUM>-<NUM> specification or amendments thereof including, but not limited to, <NUM>. 11ah, <NUM>. 11ad, <NUM>. 11ay, <NUM>. 11ax, <NUM>. 11az, <NUM>. 11ba and <NUM>. The WLAN <NUM> may provide access to another network <NUM>. For example, the AP <NUM> may be connected to a gateway device (not shown) which provides connectivity to the other network <NUM>. The WLAN <NUM> may include numerous wireless communication devices such as at least one access point (AP) <NUM> and multiple stations (STAs) <NUM> that may have a wireless association with the AP <NUM>. While only one AP <NUM> is shown, the WLAN network <NUM> also can include multiple APs <NUM>.

Each of the STAs <NUM> also may be referred to as a mobile station (MS), a mobile device, a mobile handset, a wireless handset, an access terminal (AT), a user equipment (UE), a subscriber station (SS), or a subscriber unit, among other possibilities. The STAs <NUM> may represent various devices such as mobile phones, personal digital assistant (PDAs), other handheld devices, netbooks, notebook computers, tablet computers, laptops, display devices (for example, TVs, computer monitors, navigation systems, among others), music or other audio or stereo devices, remote control devices ("remotes"), printers, kitchen or other household appliances, key fobs (for example, for passive keyless entry and start (PKES) systems), among other possibilities.

A single AP <NUM> and an associated set of STAs <NUM> may be referred to as a basic service set (BSS), which is managed by the respective AP <NUM>. <FIG> additionally shows an example coverage area <NUM> of the AP <NUM>, which may represent a basic service area (BSA) of the WLAN <NUM>. The BSS may be identified to users by a service set identifier (SSID), as well as to other devices by a basic service set identifier (BSSID), which may be a medium access control (MAC) address of the AP <NUM>. The AP <NUM> periodically broadcasts beacon frames ("beacons") including the BSSID to enable any STAs <NUM> within wireless range of the AP <NUM> to "associate" or re-associate with the AP <NUM> to establish a respective communication link <NUM> (hereinafter also referred to as a "Wi-Fi link"), or to maintain a communication link <NUM>, with the AP <NUM>. For example, the beacons can include an identification of a primary channel used by the respective AP <NUM> as well as a timing synchronization function for establishing or maintaining timing synchronization with the AP <NUM>. The AP <NUM> may provide access to external networks to various STAs <NUM> in the WLAN via respective communication links <NUM>.

To establish a communication link <NUM> with an AP <NUM>, each of the STAs <NUM> is configured to perform passive or active scanning operations ("scans") on frequency channels in one or more frequency bands (for example, the <NUM>, <NUM>, <NUM> or <NUM> bands). To perform passive scanning, a STA <NUM> listens for beacons, which are transmitted by respective APs <NUM> at a periodic time interval referred to as the target beacon transmission time (TBTT) (measured in time units (TUs) where one TU may be equal to <NUM> microseconds (µs)). To perform active scanning, a STA <NUM> generates and sequentially transmits probe requests on each channel to be scanned and listens for probe responses from APs <NUM>. Each STA <NUM> may be configured to identify or select an AP <NUM> with which to associate based on the scanning information obtained through the passive or active scans, and to perform authentication and association operations to establish a communication link <NUM> with the selected AP <NUM>. The AP <NUM> assigns an association identifier (AID) to the STA <NUM> at the culmination of the association operations, which the AP <NUM> uses to track the STA <NUM>.

As a result of the increasing ubiquity of wireless networks, a STA <NUM> may have the opportunity to select one of many BSSs within range of the STA or to select among multiple APs <NUM> that together form an extended service set (ESS) including multiple connected BSSs. An extended network station associated with the WLAN <NUM> may be connected to a wired or wireless distribution system that may allow multiple APs <NUM> to be connected in such an ESS. As such, a STA <NUM> can be covered by more than one AP <NUM> and can associate with different APs <NUM> at different times for different transmissions. Additionally, after association with an AP <NUM>, a STA <NUM> also may be configured to periodically scan its surroundings to find a more suitable AP <NUM> with which to associate. For example, a STA <NUM> that is moving relative to its associated AP <NUM> may perform a "roaming" scan to find another AP <NUM> having more desirable network characteristics such as a greater received signal strength indicator (RSSI) or a reduced traffic load.

In some cases, STAs <NUM> may form networks without APs <NUM> or other equipment other than the STAs <NUM> themselves. One example of such a network is an ad hoc network (or wireless ad hoc network). Ad hoc networks may alternatively be referred to as mesh networks or peer-to-peer (P2P) networks. In some cases, ad hoc networks may be implemented within a larger wireless network such as the WLAN <NUM>. In such implementations, while the STAs <NUM> may be capable of communicating with each other through the AP <NUM> using communication links <NUM>, STAs <NUM> also can communicate directly with each other via direct wireless links <NUM>. Additionally, two STAs <NUM> may communicate via a direct communication link <NUM> regardless of whether both STAs <NUM> are associated with and served by the same AP <NUM>. In such an ad hoc system, one or more of the STAs <NUM> may assume the role filled by the AP <NUM> in a BSS. Such a STA <NUM> may be referred to as a group owner (GO) and may coordinate transmissions within the ad hoc network. Examples of direct wireless links <NUM> include Wi-Fi Direct connections, connections established by using a Wi-Fi Tunneled Direct Link Setup (TDLS) link, and other P2P group connections.

The APs <NUM> and STAs <NUM> may function and communicate (via the respective communication links <NUM>) according to the IEEE <NUM> family of wireless communication protocol standards (such as that defined by the IEEE <NUM>-<NUM> specification or amendments thereof including, but not limited to, <NUM>. 11ah, <NUM>. 11ad, <NUM>. 11ay, <NUM>. 11ax, <NUM>. 11az, <NUM>. 11ba and <NUM>. These standards define the WLAN radio and baseband protocols for the PHY and medium access control (MAC) layers. The APs <NUM> and STAs <NUM> transmit and receive wireless communications (hereinafter also referred to as "Wi-Fi communications") to and from one another in the form of physical layer convergence protocol (PLCP) protocol data units (PPDUs). The APs <NUM> and STAs <NUM> in the WLAN <NUM> may transmit PPDUs over an unlicensed spectrum, which may be a portion of spectrum that includes frequency bands traditionally used by Wi-Fi technology, such as the <NUM> band, the <NUM> band, the <NUM> band, the <NUM> band, and the <NUM> band. Some implementations of the APs <NUM> and STAs <NUM> described herein also may communicate in other frequency bands, such as the <NUM> band, which may support both licensed and unlicensed communications. The APs <NUM> and STAs <NUM> also can be configured to communicate over other frequency bands such as shared licensed frequency bands, where multiple operators may have a license to operate in the same or overlapping frequency band or bands.

Each of the frequency bands may include multiple sub-bands or frequency channels. For example, PPDUs conforming to the IEEE <NUM>. 11n, <NUM>. 11ac and <NUM>. 11ax standard amendments may be transmitted over the <NUM> and <NUM> bands, each of which is divided into multiple <NUM> channels. As such, these PPDUs are transmitted over a physical channel having a minimum bandwidth of <NUM>, but larger channels can be formed through channel bonding. For example, PPDUs may be transmitted over physical channels having bandwidths of <NUM>, <NUM>, <NUM> or <NUM> by bonding together multiple <NUM> channels.

Each PPDU is a composite structure that includes a PHY preamble and a payload in the form of a PLCP service data unit (PSDU). The information provided in the preamble may be used by a receiving device to decode the subsequent data in the PSDU. In instances in which PPDUs are transmitted over a bonded channel, the preamble fields may be duplicated and transmitted in each of the multiple component channels. The PHY preamble may include both a legacy portion (or "legacy preamble") and a non-legacy portion (or "non-legacy preamble"). The legacy preamble may be used for packet detection, automatic gain control and channel estimation, among other uses. The legacy preamble also may generally be used to maintain compatibility with legacy devices. The format of, coding of, and information provided in the non-legacy portion of the preamble is based on the particular IEEE <NUM> protocol to be used to transmit the payload.

<FIG> shows a priority STA <NUM> that is associated with the AP <NUM>. For example, the priority STA <NUM> may have a wireless communication link <NUM> with the AP <NUM>. The priority STA <NUM> may have priority traffic to send to the AP <NUM> or the AP <NUM> may have priority traffic to send to the priority STA <NUM>. However, in a traditional contention-based access scheme, each of the devices (the AP <NUM>, the priority STA <NUM>, and the other STAs <NUM>) may contend for access to the wireless channel. Absent the techniques in this disclosure, one of the other STAs <NUM> may be more likely to win contention, thereby preventing the priority STA <NUM> from having access to the wireless channel for a period of time. In accordance with this disclosure, the WLAN may support priority access for the priority STA <NUM> to enhance their probability of successful communication during periods of network congestion.

In some implementations, the priority STA <NUM> may invoke the priority access service by sending a request to the AP <NUM>. The AP <NUM> may verify that the priority STA <NUM> is authorized to use the priority access service and respond with a priority access response message. The priority access service may include prioritizing traffic to or from the priority STA <NUM> over other STAs <NUM>. For example, the AP <NUM> may give a higher priority for traffic to or from the priority STA <NUM> over the other STAs <NUM>. In some implementations, when the priority STA <NUM> is authorized to use the priority access service, the priority STA <NUM> may use the AC_V0 access class for its contention-based access of the wireless channel. The AP <NUM> may prioritize traffic to or from the priority STA <NUM> over traffic to or from other STAs <NUM> allocated for the AC_VO access class.

In some implementations, the AP <NUM> may manipulate one or more contention parameters to enable priority access service for the priority STA <NUM>. For example, the priority access may be accomplished by modifying EDCA parameters for different access classes. EDCA defines four access classes based on type of traffic: AC_BK, AC_BE, AC_VO, and AC_VI. However, there currently is not an access class for priority access. In some implementations, a priority access class (AC_PRI) can be defined. Furthermore, because the AC_VI and AC_VO access classes already have aggressive contention parameters, the contention parameters for those classes can be temporarily weakened so that the priority STA <NUM> is more likely to win contention-based access of the wireless channel. Either the AP <NUM> or the other STAs <NUM> may detect a transmission from the priority STA <NUM> that enables a priority access service for the priority STA <NUM>. The AP <NUM> and the other STAs <NUM> may weaken their respective contention parameters to support the priority access of the priority STA <NUM>.

The AP <NUM> may include a priority access support unit <NUM> which supports the priority access by the priority STA <NUM>. The priority access support unit <NUM> may include a priority access service detection unit <NUM>. The priority access service detection unit <NUM> may detect a transmission from the priority STA <NUM> that includes a priority access indication. The priority access indication may be in a preamble or a PHY header of a PPDU transmitted by the priority STA <NUM>. In some implementations, the priority access service detection unit <NUM> may be configured to receive a management message from a network operator that activates the priority access service. The priority access support unit <NUM> may be configured to send a priority access enablement indicator <NUM> so that the other STAs <NUM> also can support the priority access service of the priority STA <NUM>. The priority access support unit <NUM> also may include a contention parameters modification unit <NUM> to modify contention parameters for the access classes of the other STAs <NUM>. In some implementations, the contention parameters modification unit <NUM> may advertise different CWmin, CWmax, AIFSN, or TXOP durations for one or more legacy access classes so that a legacy STA will have less likelihood of winning contention (compared to the priority STA <NUM>). Although described as being in the AP <NUM>, the priority access support unit <NUM> also may be implemented in a non-priority STA (such as one of the other STAs <NUM>).

The priority STA <NUM> may include a priority access utilization unit <NUM>. The priority access utilization unit <NUM> may include a priority access service controller <NUM> configured to enable or disable a priority access service of the priority STA <NUM>. In some implementations, the priority STA <NUM> may be configured to always use the priority access service. Alternatively, the priority access service may be activated by the priority access service controller <NUM> when needed, such as an emergency. The priority access utilization unit <NUM> may be configured to send a priority access indication <NUM>. The priority access indication <NUM> may be included in a transmission of the priority STA <NUM> so that the AP <NUM> and the other STAs <NUM> can determine that the priority STA <NUM> is using the priority access service. The priority access utilization unit <NUM> may include a priority access contention manager <NUM> configured to manage contention-based access by the priority STA <NUM>. The priority access contention manager <NUM> may implement aggressive EDCA parameters (compared to the other STAs <NUM>) to ensure or improve likelihood that the priority access utilization unit <NUM> will win contention-based access of the wireless channel.

In traditional WLAN deployments, a single user (SU) access mode was based on contention-based access in which a station obtains the use of the full channel up to a TXOP duration when it wins contention. Different priorities and access classes may be used by the WLAN to implement the prioritization of traffic. More recently, the IEEE draft <NUM> ax technical standard implemented OFDMA which supports more efficient use of a wireless channel using either the scheduled access mode or the MU EDCA access mode. Using OFDMA and the scheduled access mode, the AP <NUM> may schedule airtime availability for different stations. Using OFDMA and the MU EDCA access mode, the AP <NUM> may trigger contention-based access for portions of a transmission opportunity by various STAs. However, it may be possible that the SU access mode provides a greater quality of service than the MU EDCA access mode since it includes full channel access or may have different contention parameters associated with the access categories. To provide a higher quality of service for the priority STA <NUM>, the priority STA <NUM> may use a priority access service that is better than the existing access modes. <FIG> and <FIG> provide more detail about how the priority access service compares to the existing access modes and access classes described in this disclosure.

<FIG> shows an example conceptual diagram of OFDM <NUM>. The OFDM channel width may include multiple subcarriers. A WLAN packet <NUM> (also referred to as a PPDU) includes data that is encoded using the subcarriers of the channel width. For example, a first STA may transmit a first PPDU <NUM> at a first time period. During a second time period, a second STA may transmit a second PPDU <NUM>. The PPDUs <NUM> and <NUM> may be different lengths of time. Typically, the first STA and the second STA (and any other STAs in the BSS) will contend for access to the channel. Once the STA wins the contention, the STA can use the channel for transmission of a PPDU. As shown in <FIG>, different shading of the PPDUs indicates that different STAs may utilize the wireless channels sequentially, one at a time. However, this communication structure may be inefficient if a STA does not have enough data to justify using the full channel width. IEEE <NUM>. 11ax introduced the use of OFDMA in a WLAN.

<FIG> shows an example conceptual diagram of OFDMA <NUM>. OFDMA breaks down the channel width into a plurality of resource units (RUs). Each RU may include a different quantity of subcarriers. Using OFDMA, an AP may allocate different RUs for different STAs. For example, a PPDU <NUM> may include different RUs allocated for a first STA, a second STA, a third STA, and a fourth STA. One RU <NUM> is allocated for a STA to transmit data in the PPDU <NUM>, while other RUs are allocated for different STAs. The allocation of RUs may be used to schedule channel access. For example, a trigger message from an AP may indicate which RUs are allocated to particular STAs to use for traffic in the PPDU that follows the trigger message.

The allocation of RUs may be used to schedule priority access. For example, an AP may transmit a trigger message that indicates which RUs are allocated to a priority STAs to use for priority access service in an UL MU PPDU that follows the trigger message. In some implementations, the AP may allocate some RUs (referred to as random access resource units, or RA-RUs) for contention-based access. One or more STAs may use an UL OFDMA-based random access (UORA) technique to transmit data via the RA-RUs.

<FIG> shows example relationships between QoS and various access modes. The SU access mode <NUM> provides quality of service based on the priority of access categories (as, for example, described in <FIG>). Some legacy STAs may only support the SU access mode <NUM>. For example, legacy STAs may include non-high-throughput (non-HT) STAs, high throughput (HT) STAs, or very high throughput (VHT) STAs, as described in IEEE <NUM> and amendments thereto. However, the WLAN protocols have evolved to support both more access modes. For example, IEEE <NUM>. 11ax describes high efficiency (HE) STAs that support the scheduled access mode <NUM> and the MU EDCA access mode <NUM>). Because the MU scheduled access mode includes scheduling by an AP, the AP may control the scheduling of resources to support a greater quality of service using the scheduled access mode <NUM> compared to the SU access mode <NUM>. However, it is possible that the MU EDCA access mode <NUM> provides a lower quality of service compared to the SU access mode <NUM> because the MU EDCA access mode <NUM> would be used to gain access to only portions of a transmission opportunity or only portions of the channel. The scheduled access mode <NUM> and the MU EDCA access mode <NUM> were introduced in IEEE <NUM>. 11ax and are supported by high efficiency (HE)-capable devices and expected to be supported by extremely high throughput (EHT)-capable devices.

A priority access service <NUM> may provide an even greater quality of service as compared to the scheduled access mode <NUM>. The priority access service <NUM> may be based on one or more new access classes specified in a technical standard (such as IEEE <NUM>. The priority access service may be used by priority STAs. The priority access service <NUM> may be used on a per-STA basis depending on implementations or based on the QoS parameters supported by the priority access service <NUM>.

In some implementations, the priority access service may be based on a modification of contention parameters for the SU access mode <NUM> or the MU EDCA access mode <NUM>. For example, a priority STA may use more aggressive contention parameters for SU access contention or MU-EDCA contention. Non-priority STAs may use weaker contention parameters for the SU access contention or the MU-EDCA contention.

<FIG> shows example various access modes and various associated access classes. The chart <NUM> shows the relative quality of service for each AC defined for the access modes. The ACs may include access classes for background, best effort, voice, and video. For example, a background access class (AC_BK) <NUM> may have a lower quality of service compared to a best effort access class (AC_BE) <NUM>. A voice access class (AC_VO) <NUM> may have a higher quality of service than the AC_BE <NUM>. A video access class (AC_VI) <NUM> may have a higher quality of service than the AC_VO <NUM>.

The quality of service for the access classes may be based on the contention parameters or levels of priority for each AC. The contention parameters may include a minimum contention window (CWmin), a maximum contention window (CWmax), an arbitration interframe space number (AIFSN), or a maximum transmission opportunity (TXOP) duration, among other examples. The contention parameters may be referred to as AIFSN[AC], CWmin[AC], CWmax[AC], TXOP Limit[AC], where the AC refers to a particular access class. Each STA may generate traffic streams related to the AC_VO, AC_VI, AC_BE, and AC_BK access classes. Each traffic stream may use contention parameters associated with each access class depending on the type of traffic in the traffic stream. Table <NUM> shows some example contention parameters for the access classes.

As described in <FIG>, the different access modes also impact the quality of service. For example, AC_BK <NUM> for the MU EDCA access mode <NUM> may be lower than the AC_BK <NUM> for the SU access mode <NUM>. The SU access mode <NUM> may have similarly defined access classes as described above (AC_BK <NUM>, AC_BE <NUM>, AC_VO <NUM>, and AC_VI <NUM>). The scheduled access mode <NUM> may use traffic categories and scheduling of resources to provide a higher quality of service than can be provided by the SU access mode <NUM>.

The priority access service <NUM> may provide a higher quality of service compared to the scheduled access mode <NUM>. The priority access service <NUM> may define a new access class for priority traffic (AC_PRI) <NUM>. The AC_PRI may be associated with different contention parameters that give a priority ATA a higher quality of service compared to the existing ACs defined for the SU access mode <NUM> and the MU EDCA access mode <NUM>. For example, they may have a smaller AIFSN, more favorable contention windows, or larger TXOP durations, among other examples. Although illustrated as a separate priority access service, the AC_PRI <NUM> may be used with SU access or MU EDCA access modes.

In some implementations, the AP may advertise the contention parameters that are defined for the ACs. For example, the AP may transmit a beacon message, probe response, or another management frame that indicates the contention parameters. The AP may adjust the contention parameters for non-priority access classes as needed to support priority access by a priority STA.

Modifying the contention parameters (such as the CWmin, CWmax, AIFSN, and TXOP duration limit) may accomplished in a number of ways. In one example, the AP may transmit the modified contention parameters for each access class. In another example, each non-priority STA may modify their own contention parameters according to a predefined algorithm. For example, each non-priority STA may add an offset value to the CWmin, CWmax, or AIFSN, to increase the values associated with those parameters. In another example, each non-priority STA may decrease the TXOP duration limit based on a fixed or signaled offset value. The offset values used to modify the contention parameters may be signaled by the AP to its BSS or may be predefined in a standard technical specification.

In some implementations, modifying the contention parameters also may include changing a backoff algorithm. Typically, each STA starts an initial random backoff counter that causes a randomized delay before each STA attempts to access the wireless channel. The initial random backoff counter is selected from a range from zero to CWmin (which sets an upper limit for the initial backoff time). If the wireless channel is busy, the STA will double the initial random backoff counter up to a maximum value (CWmax). In some implementations, when a priority access service is being used by a priority STA, the other STAs may modify their backoff algorithm to give more favorable access to the priority STA. Examples of modifying the backoff algorithm may include disregarding the CWmin and selecting an initial random backoff counter between a range from zero to the CWmax (or the CWmax minus <NUM>).

Although this disclosure describes an AC_PRI access class being different from the existing access classes, some implementations of priority access may utilize prioritization within an existing access class. For example, the priority access may be associated with a particular access class (such as the AC_VI access class or the AC_VO access class). Among STAs within the particular access class, an AP may prioritize traffic for a priority STA above other STAs in that same access class.

<FIG> shows an example conceptual timing diagram <NUM> in which a priority STA wins contention of a wireless channel. The conceptual timing diagram <NUM> shows an AP <NUM>, priority STA <NUM>, and multiple other (non-priority STAs) <NUM> that share a wireless channel using contention-based access. At a first contention <NUM>, the priority STA <NUM> wins the contention because either the priority STA <NUM> has more aggressive contention parameters, or because the AP <NUM> and other STAs <NUM> have less aggressive contention parameters, or both. The first contention <NUM> may be a contention period for SU access mode (as shown) or may be triggered by a MU-UL MIMO trigger message from the AP <NUM>. In either case, the priority STA <NUM> is configured to use a priority access service. Therefore, the priority STA <NUM> has better contention parameters and wins the first contention <NUM>. After winning the first contention <NUM>, the priority STA <NUM> may transmit a priority access transmission (such as a priority access frame <NUM>). The priority access transmission may include an indicator to specify that the priority STA <NUM> is using the priority access service. The priority STA <NUM> may maintain control of the wireless channel for a TXOP duration <NUM>. In some implementations, a longer TXOP duration is permitted for priority STAs. Following the TXOP duration <NUM>, a second contention <NUM> may occur. Once again, if the priority STA <NUM> still has priority traffic to transmit, the non-priority STA <NUM> may contend and win control for another TXOP (not shown) following the second contention <NUM>.

<FIG> shows an example conceptual timing diagram <NUM> in which a non-priority STA initially wins contention of a wireless channel. Although it is unlikely to occur, it is possible that a non-priority STA <NUM> may win a first contention <NUM> despite having weakened contention parameters. There may be multiple ways (as shown in <FIG>) to mitigate delay to the priority STA. One mechanism is to cause the non-priority STA <NUM> to use a reduced TXOP duration <NUM>. For example, the AP <NUM> may have previously signaled TXOP duration limits for each access class. When the priority access service is enabled, the AP <NUM> may signal a reduced TXOP duration limit or may signal a priority service enablement indicator that causes the non-priority STAs <NUM> to use a reduced TXOP duration <NUM> if they should win contention. In some implementations, the reduced TXOP duration may be specified in a standard technical specification. During the reduced TXOP duration <NUM>, since the non-priority STA <NUM> won contention, the non-priority STA <NUM> may transmit a non-priority frame <NUM>.

<FIG> shows a second contention <NUM> that occurs after the non-priority frame <NUM>. This provides an opportunity to describe another example mechanism for favoring the priority STA <NUM>. Typically, after transmitting or detecting a transmission, each STA will wait for an interval of time, referred to as a distributed coordinated function (DCF) interframe space (DIFS), before attempting to access the wireless channel. The DIFS may define the beginning of the contention window. As shown in <FIG>, a priority STA <NUM> may use a reduced DIFS, such as a priority interframe space (PIFS) <NUM>. The PIFS <NUM> may be less than the DIFS used by the other devices. As a result of using the PIFS <NUM> instead of the DIFS, the priority STA <NUM> may gain some additional advantage in winning the second contention <NUM>. After winning the second contention <NUM>, the priority STA <NUM> may transmit a priority access frame <NUM>.

<FIG> shows an example message flow diagram in which all nearby devices support a priority access service of a priority STA. In this illustrative example <NUM>, the AP <NUM> and other STAs <NUM> are capable of recognizing a priority access indicator in a transmission <NUM> from the priority STA <NUM>. The priority STA <NUM> may be in the same BSS as the AP <NUM> and the other STAs <NUM> or may be in an OBSS. For example, the priority access indication may be included in a preamble or PHY header of a transmission from the priority STA <NUM>. The other devices may be capable of interpreting the preamble or PHY header even if they do not belong to the same BSS as the priority STA <NUM>. Upon receiving the transmission <NUM>, the AP <NUM> may modify (shown at block <NUM>) its own contention parameters to prevent the AP <NUM> from winning contention over the priority STA <NUM>. Similarly, the other STAs <NUM> may modify (shown at block <NUM>) their respective contention parameters to prevent them from winning contention over the priority STA <NUM>. During the time that the priority STA <NUM> is transmitting priority transmissions <NUM>, the priority STA <NUM> may be said to be using a priority access service <NUM>.

<FIG> shows a message flow diagram in which an AP activates a priority access service of a priority STA. In this illustrative example <NUM>, the AP <NUM> may determine that the priority STA <NUM> needs the priority access service. For example, the priority STA <NUM> may send a message (such as a priority access request message <NUM>) that indicates the priority STA <NUM> is requesting the priority access service. The AP <NUM> may receive the priority access request message <NUM> from the priority STA <NUM>. Alternatively, or additionally, the AP <NUM> may receive a priority service activation message <NUM> from a network operator <NUM> or another priority STA (not shown) in the BSS. The AP <NUM> may process (shown at block <NUM>) the priority access request message <NUM> or the priority service activation message <NUM> and determine whether the priority STA <NUM> is authorized to use the priority access service. In some implementations, the, AP <NUM> may send a priority service response message (not shown) to the priority STA <NUM> to indicate that the priority access service was successfully enabled for the priority STA <NUM>.

The AP <NUM> may determine changes to one or more settings for the STAs in the BSS to enhance the probability that the priority STA <NUM> will successfully win access to the wireless channel before other STAs. For example, the AP <NUM> may send one or more configuration messages <NUM> to modify the settings (such as contention parameters) in the BSS. The non-priority STAs <NUM> may modify (shown at block <NUM>) their respective contention parameters to prevent them from winning contention over the priority STA <NUM>. Alternatively, or additionally, the AP <NUM> may transmit a priority service enablement indicator <NUM> (such as a priority service response frame) to the priority STA <NUM> indicating that the priority STA <NUM> can use the priority access service. In some implementations, the priority service enablement indicator <NUM> may be included in a priority service activation notification sent to other APs (not shown) or any STAs in the vicinity of the AP <NUM>. For example, the priority service activation notification may be a beacon frame or other management frame that informs the other STAs <NUM> or other APs (not shown) to adjust their respective EDCA parameters such that the priority STA <NUM> has a higher priority to utilize the wireless channel. The priority STA <NUM> may proceed with transmitting priority transmissions <NUM>. During the time that the priority STA <NUM> is transmitting priority transmissions <NUM>, the priority STA <NUM> may be said to be using a priority access service <NUM>.

In some implementations, the priority access service may have a limited duration, such as a priority service event duration. The priority service event duration may be signaled in the priority access request message <NUM> or the priority service activation message <NUM>. After the priority service event duration, the AP <NUM> may determine (shown at block <NUM>) to end the priority access service <NUM>. Alternatively, or additionally, the AP <NUM> may receive a management message from the network operator <NUM> indicating an end of the priority access service. The AP <NUM> may transmit configuration messages <NUM> to revert the regular access mode <NUM> settings. During the regular access mode <NUM>, the priority STA <NUM> and the non-priority STAs <NUM> may have equal opportunity to win contention of the wireless channel based on existing access classes.

<FIG> shows an example message flow diagram in which a non-priority STA can enable priority access service on behalf of a priority STA. In this illustrative example <NUM>, one of the other STAs <NUM> may be capable of recognizing a priority access indicator in a transmission <NUM> from the priority STA <NUM>. For example, the priority access indicator may be included in a preamble or PHY header of a transmission from the priority STA <NUM>. The other devices may be capable of interpreting the preamble or PHY header even if they do not belong to the same BSS as the priority STA <NUM>. Upon receiving the transmission <NUM>, the other STA <NUM> may modify (shown at block <NUM>) its respective contention parameters to prevent it from winning contention over the priority STA <NUM>. However, other STAs <NUM> (or the AP <NUM>) may be too far to properly receive the transmission <NUM> from the priority STA <NUM> that includes the priority access indicator. Furthermore, there may be legacy STAs (not shown) that are unable to interpret the priority access indicator. In both scenarios, the non-priority STA <NUM> that detects the priority access indicator can send a priority service detection indication <NUM> to the AP <NUM>. The AP <NUM> may modify its contention parameters (shown at block <NUM>). Furthermore, the AP <NUM> may send a priority service enable indicator or one or more configuration messages <NUM> to cause the STAs in its BSS to modify their contention parameters. Alternatively, or additionally, the AP <NUM> may transmit a priority service enablement indicator <NUM> (such as a priority service response frame) to the priority STA <NUM> indicating that the priority STA <NUM> can use the priority access service. Furthermore, in some implementations, the AP <NUM> may transmit a priority service activation notification (not shown) to any STAs or other APs to cause them to adjust their respective EDCA parameters such that the priority STA <NUM> has a higher priority to utilize the wireless channel.

<FIG> shows a pictorial diagram of an example environment with OBSSs <NUM>. A first BSS may be managed by a first AP <NUM>. Similarly, a second BSS may be managed by a second AP <NUM>. Each of the APs <NUM>, <NUM> may be similar to the AP <NUM> described in <FIG>. <FIG> additionally shows example coverage areas associated with each AP. For example, a first coverage area <NUM> of the AP <NUM> may represent a basic service area (BSA) of the first BSS. An example second coverage area <NUM> of the second AP <NUM> may form a BSA of the second BSS. Each BSS may be a network implementing at least one of the IEEE <NUM> family of standards (such as that defined by the IEEE <NUM>-<NUM> specification or amendments thereof). Each AP may provide access to other networks (not shown). In some implementations, the second BSS managed by the second AP <NUM> may be referred to as an overlapping BSS (OBSS) in relation to the first BSS managed by the first AP <NUM>. Each BSS may include numerous wireless communication devices such as an AP and a plurality of STAs. In this description, the first AP <NUM> is described as an access point using an infrastructure mode. However, in some implementations, the first AP <NUM> may be a STA which is operating as an AP. For example, the first AP <NUM> may be a STA capable of operating in a peer-to-peer mode or independent mode. In other examples, the first AP <NUM> may be a software AP (SoftAP) operating on a computer system.

In <FIG>, the first BSS includes the first AP <NUM> and at least one priority STA <NUM>. There also may be non-priority STAs (not shown) in the first BSS. The second BSS includes the second AP <NUM> and STAs <NUM> and <NUM>. In the example of <FIG>, the APs <NUM> and <NUM> may be configured to use a same wireless channel. For example, the first BSS and the second BSS may be referred to as OBSSs (or neighboring BSSs) because they are configured for the same wireless channel in the same location. Traditionally, the APs may share the wireless channel using either a time-based division of the wireless channel or by obtaining access through a contention-based procedure.

In one example of <FIG>, one of the STAs of the second BSS may assist the second AP <NUM> to determine that a priority STA <NUM> requires a priority service via the wireless channel. For example, the first STA <NUM> and the second AP <NUM> may implement the message flow described with reference to <FIG>. A first STA <NUM> associated with the second AP <NUM> may detect a priority transmission <NUM> from the priority STA <NUM>. Even though the priority STA <NUM> is in the first BSS (managed by the first AP <NUM>), the preamble or PHY header of the priority transmission <NUM> may be detectable by the first STA <NUM>. The first STA <NUM> may communicate with the second AP <NUM> to cause the second AP <NUM> to modify contention parameters for the STAs (including a legacy STA <NUM>) associated with the second BSS managed by the second AP <NUM>.

In another example described with reference to <FIG>, the first AP <NUM> may determine that the priority STA <NUM> requires the priority service. The first AP <NUM> may communicate a priority service activation notification to the second AP <NUM> via a communication link <NUM>. The communication link <NUM> may be a wireless communication link or may be a wired or networked communication link between the first AP <NUM> and the second AP <NUM>. The priority service activation notification may inform the second AP <NUM> that the first AP <NUM> is activating the priority service. Upon receiving the priority service activation notification, the second AP <NUM> may adjust access classes or EDCA contention parameters for STAs in the second BSS (including the STAs <NUM> and <NUM> if they are non-priority STAs). Thus, the first AP <NUM> may enable priority service for the priority STA <NUM> to access a wireless channel by causing the second AP <NUM> to reduce EDCA parameters for non-priority STAs in an OBSS managed by the second AP <NUM>.

In another example described with reference to <FIG>, when the first AP <NUM> enables the priority service for the priority STA <NUM>, the first AP <NUM> may broadcast a beacon frame or other management frame that includes a priority service activation notification. The second AP <NUM> may receive the priority service activation notification and adjust the EDCA parameters for non-priority STAs in the second BSS managed by the second AP <NUM>.

<FIG> shows an example protocol data unit (PDU) <NUM> usable for communications between an AP and a number of STAs. For example, the PDU <NUM> can be configured as a PPDU. As shown, the PDU <NUM> includes a PHY preamble <NUM> and a PHY payload <NUM>. For example, the PHY preamble <NUM> may include a legacy portion that itself includes a legacy short training field (L-STF) <NUM>, a legacy long training field (L-LTF) <NUM>, and a legacy signaling field (L-SIG) <NUM>. The PHY preamble <NUM> also may include a non-legacy portion (not shown). The L-STF <NUM> generally enables a receiving device to perform automatic gain control (AGC) and coarse timing and frequency estimation. The L-LTF <NUM> generally enables a receiving device to perform fine timing and frequency estimation and also to estimate the wireless channel. The L-SIG <NUM> generally enables a receiving device to determine a duration of the PDU and use the determined duration to avoid transmitting on top of the PDU. For example, the L-STF <NUM>, the L-LTF <NUM> and the L-SIG <NUM> may be modulated according to a binary phase shift keying (BPSK) modulation scheme. The payload <NUM> may be modulated according to a BPSK modulation scheme, a quadrature BPSK (Q-BPSK) modulation scheme, a quadrature amplitude modulation (QAM) modulation scheme, or another appropriate modulation scheme. The payload <NUM> may generally carry higher layer data, for example, in the form of medium access control (MAC) protocol data units (MPDUs) or an aggregated MPDU (A-MPDU).

<FIG> shows an example L-SIG field <NUM> in the PDU of <FIG>. The L-SIG <NUM> includes a data rate field <NUM>, a reserved bit <NUM>, a length field <NUM>, a parity bit <NUM>, and a tail field <NUM>. The data rate field <NUM> indicates a data rate (note that the data rate indicated in the data rate field <NUM> may not be the actual data rate of the data carried in the payload <NUM>). The length field <NUM> indicates a length of the packet in units of, for example, bytes. The parity bit <NUM> is used to detect bit errors. The tail field <NUM> includes tail bits that are used by the receiving device to terminate operation of a decoder (for example, a Viterbi decoder). The receiving device utilizes the data rate and the length indicated in the data rate field <NUM> and the length field <NUM> to determine a duration of the packet in units of, for example, microseconds (µs).

In some implementations, the L-SIG <NUM> or a PHY header in the payload <NUM> may be modified to include one or more indicators described in this disclosure, such as the priority access indication, the priority detection indicator, the priority service duration, or the priority service enablement indicator. The indicators may be signaled using one or more bits of the preamble or PHY header.

In some implementations, a priority STA or an AP may use a management frame (such as a beacon frame, probe response frame, generic advertisement service (GAS) message, among other examples) to indicate that the wireless communication device supports priority access service.

<FIG> shows a conceptual diagram of an example format of a message <NUM> for communicating priority access information. For example, a priority STA <NUM> may transmit the message <NUM> to the AP <NUM> or another STA <NUM>. The AP <NUM> may transmit the message <NUM> to the priority STA <NUM> or another STA <NUM>. The message <NUM> may include one or more indicators (or information elements) that include priority access information. In some implementations, the message <NUM> is transmitted in the form of a PPDU. The message <NUM> (which also may be formatted as a PPDU) may include a preamble <NUM>, a frame header <NUM>, a frame body <NUM>, and a frame check sequence (FCS) <NUM>. The preamble <NUM> may include one or more bits to establish synchronization. The frame header <NUM> may include source and destination network addresses (such as the network address of the sending AP and receiving AP, respectively), the length of the data frame, or other frame control information. The frame body <NUM> may include a variety of indicators <NUM>.

<FIG> includes several example indicators <NUM>. The indicators may be included as one or more bits of the preamble <NUM> or the frame header <NUM>, as shown in <FIG>. Alternatively, the indicators may be included as information elements or fields of a management message (not shown) in payload of the frame body <NUM>. The example indicators <NUM> include a priority access indicator <NUM>. In some implementations, the priority access indicator <NUM> may be included in every priority transmission from a priority STA. The example indicators <NUM> may include a priority service event duration <NUM> specifying a duration of the priority access service. The example indicators <NUM> may include a priority service enablement indicator <NUM>. The priority service enablement indicator <NUM> may be included in a message from an AP to its BSS. The example indicators <NUM> may include modified contention parameters <NUM>. For example, the AP <NUM> may include contention parameters for each access class (potentially including the new AC_PRI) in a configuration message to the BSS. The example indicators <NUM> may include access class change information <NUM>. For example, an AP <NUM> may cause some STAs to change to a lower access class to provide support for the priority access by the priority STA. The example indicators <NUM> may include a priority service activation notification <NUM> to inform STAs or other APs that the priority service has been activated for a priority STA.

The examples in <FIG> are provided for pedagogical purposes and other examples messages may be within the scope of this disclosure. For example, the message <NUM> may be a priority access request frame formatted to include a request to activate the priority access service. A priority access request frame may include a request indicator, a security token, a duration, or any combination thereof. In another example, the message <NUM> may be a priority access response frame formatted to include a either a success or failure to activate the priority access service. In yet another example, the message <NUM> may be a management or configuration frame that indicates whether the sending WLAN device (such as an AP or a priority STA) supports the priority access service.

<FIG> shows a flowchart illustrating a process <NUM> by an AP to support priority access. The process <NUM> is performed by a wireless communication device such as the AP <NUM> described above. In some implementations, the process <NUM> begins in block <NUM>. In block <NUM>, an AP manages a first basic service set (BSS) on a wireless channel. In block <NUM>, the AP determines that at least a first station (STA) is configured to utilize a priority access service of the first BSS, the priority access service associated with prioritizing traffic to or from the first STA via the wireless channel. In block <NUM>, the AP modifies one or more settings of the first BSS based on a determination that the first STA is configured to utilize the priority access service, where the one or more settings are modified to favor a contention-based access of the wireless channel by the first STA over one or more other STAs of the first BSS that are not configured to utilize the priority access service.

<FIG> shows a flowchart illustrating a process <NUM> by a priority STA to implement priority access. The process <NUM> is performed by a wireless communication device such as the priority STA <NUM> described above. In some implementations, the process <NUM> begins in block <NUM>. In block <NUM>, the priority STA transmits a priority service request frame that includes a priority access indication to the AP. In block <NUM>, the priority STA receives a priority service response frame that indicates the first STA is authorized to use the priority access service. In block <NUM>, the priority STA performs a prioritized contention-based access of the wireless channel using a first set of enhanced distributed channel access (EDCA) parameters associated with the priority access service, where the first set of EDCA parameters favors the first STA over one or more other STAs that are not configured to utilize the priority access service.

<FIG> shows a flowchart illustrating an example process by a non-priority STA to support priority access. In some implementations, the process <NUM> may be performed by a wireless communication device such as the STAs <NUM> described above. In some implementations, the process <NUM> begins in block <NUM>. In block <NUM>, a first STA may determine that at least a second station (STA) is configured to utilize a priority access service of a basic service set (BSS), the priority access service associated with prioritizing traffic to or from the second STA via a wireless channel. In block <NUM>, the first STA may determine that the first STA is not configured to utilize the priority access service. In block <NUM>, the first STA may modify one or more settings used by the first STA for the contention-based access of the wireless channel, where modifying the one or more settings causes the second STA to have priority over the first STA.

<FIG> shows a block diagram of an example wireless communication device <NUM>. In some implementations, the wireless communication device <NUM> can be an example of a device for use in a STA such as one of the STAs <NUM> or <NUM> described above with reference to <FIG>. In some implementations, the wireless communication device <NUM> can be an example of a device for use in an AP such as the AP <NUM> described above with reference to <FIG>. The wireless communication device <NUM> is capable of transmitting (or outputting for transmission) and receiving wireless communications (for example, in the form of wireless packets). For example, the wireless communication device can be configured to transmit and receive packets in the form of physical layer convergence protocol (PLCP) protocol data units (PPDUs) and medium access control (MAC) protocol data units (MPDUs) conforming to an IEEE <NUM> wireless communication protocol standard, such as that defined by the IEEE <NUM>-<NUM> specification or amendments thereof including, but not limited to, <NUM>. 11ah, <NUM>. 11ad, <NUM>. 11ay, <NUM>. 11ax, <NUM>. 11az, <NUM>. 11ba and <NUM>.

The wireless communication device <NUM> can be, or can include, a chip, system on chip (SoC), chipset, package or device that includes one or more modems <NUM>, for example, a Wi-Fi (IEEE <NUM> compliant) modem. In some implementations, the one or more modems <NUM> (collectively "the modem <NUM>") additionally include a WWAN modem (for example, a 3GPP <NUM> LTE or <NUM> compliant modem). In some implementations, the wireless communication device <NUM> also includes one or more radios <NUM> (collectively "the radio <NUM>"). In some implementations, the wireless communication device <NUM> further includes one or more processors, processing blocks or processing elements <NUM> (collectively "the processor <NUM>") and one or more memory blocks or elements <NUM> (collectively "the memory <NUM>").

The modem <NUM> can include an intelligent hardware block or device such as, for example, an application-specific integrated circuit (ASIC) among other possibilities. The modem <NUM> is generally configured to implement a PHY layer. For example, the modem <NUM> is configured to modulate packets and to output the modulated packets to the radio <NUM> for transmission over the wireless medium. The modem <NUM> is similarly configured to obtain modulated packets received by the radio <NUM> and to demodulate the packets to provide demodulated packets. In addition to a modulator and a demodulator, the modem <NUM> may further include digital signal processing (DSP) circuitry, automatic gain control (AGC), a coder, a decoder, a multiplexer and a demultiplexer. For example, while in a transmission mode, data obtained from the processor <NUM> is provided to a coder, which encodes the data to provide encoded bits. The encoded bits are then mapped to points in a modulation constellation (using a selected MCS) to provide modulated symbols. The modulated symbols may then be mapped to a number NSS of spatial streams or a number NSTS of space-time streams. The modulated symbols in the respective spatial or space-time streams may then be multiplexed, transformed via an inverse fast Fourier transform (IFFT) block, and subsequently provided to the DSP circuitry for Tx windowing and filtering. The digital signals may then be provided to a digital-to-analog converter (DAC). The resultant analog signals may then be provided to a frequency upconverter, and ultimately, the radio <NUM>. In implementations involving beamforming, the modulated symbols in the respective spatial streams are precoded via a steering matrix prior to their provision to the IFFT block.

While in a reception mode, digital signals received from the radio <NUM> are provided to the DSP circuitry, which is configured to acquire a received signal, for example, by detecting the presence of the signal and estimating the initial timing and frequency offsets. The DSP circuitry is further configured to digitally condition the digital signals, for example, using channel (narrowband) filtering, analog impairment conditioning (such as correcting for I/Q imbalance), and applying digital gain to ultimately obtain a narrowband signal. The output of the DSP circuitry may then be fed to the AGC, which is configured to use information extracted from the digital signals, for example, in one or more received training fields, to determine an appropriate gain. The output of the DSP circuitry also is coupled with the demodulator, which is configured to extract modulated symbols from the signal and, for example, compute the logarithm likelihood ratios (LLRs) for each bit position of each subcarrier in each spatial stream. The demodulator is coupled with the decoder, which may be configured to process the LLRs to provide decoded bits. The decoded bits from all of the spatial streams are then fed to the demultiplexer for demultiplexing. The demultiplexed bits may then be descrambled and provided to the MAC layer (the processor <NUM>) for processing, evaluation, or interpretation.

The radio <NUM> generally includes at least one radio frequency (RF) transmitter (or "transmitter chain") and at least one RF receiver (or "receiver chain"), which may be combined into one or more transceivers. For example, the RF transmitters and receivers may include various DSP circuitry including at least one power amplifier (PA) and at least one low-noise amplifier (LNA), respectively. The RF transmitters and receivers may, in turn, be coupled to one or more antennas. For example, in some implementations, the wireless communication device <NUM> can include, or be coupled with, multiple transmit antennas (each with a corresponding transmit chain) and multiple receive antennas (each with a corresponding receive chain). The symbols output from the modem <NUM> are provided to the radio <NUM>, which then transmits the symbols via the coupled antennas. Similarly, symbols received via the antennas are obtained by the radio <NUM>, which then provides the symbols to the modem <NUM>.

The processor <NUM> can include an intelligent hardware block or device such as, for example, a processing core, a processing block, a central processing unit (CPU), a microprocessor, a microcontroller, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a programmable logic device (PLD) such as a field programmable gate array (FPGA), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The processor <NUM> processes information received through the radio <NUM> and the modem <NUM>, and processes information to be output through the modem <NUM> and the radio <NUM> for transmission through the wireless medium. For example, the processor <NUM> may implement a control plane and MAC layer configured to perform various operations related to the generation and transmission of MPDUs, frames or packets. The MAC layer is configured to perform or facilitate the coding and decoding of frames, spatial multiplexing, space-time block coding (STBC), beamforming, and OFDMA resource allocation, among other operations or techniques. In some implementations, the processor <NUM> may generally control the modem <NUM> to cause the modem to perform various operations described above.

The memory <NUM> can include tangible storage media such as random-access memory (RAM) or read-only memory (ROM), or combinations thereof. The memory <NUM> also can store non-transitory processor- or computer-executable software (SW) code containing instructions that, when executed by the processor <NUM>, cause the processor to perform various operations described herein for wireless communication, including the generation, transmission, reception and interpretation of MPDUs, frames or packets. For example, various functions of components disclosed herein, or various blocks or steps of a method, operation, process or algorithm disclosed herein, can be implemented as one or more modules of one or more computer programs.

<FIG> shows a block diagram of an example AP <NUM>. For example, the AP <NUM> can be an example implementation of the AP <NUM> described with reference to <FIG>. The AP <NUM> includes a wireless communication device (WCD) <NUM> (although the AP <NUM> may itself also be referred to generally as a wireless communication device as used herein). For example, the wireless communication device <NUM> may be an example implementation of the wireless communication device <NUM> described with reference to <FIG>. The AP <NUM> also includes multiple antennas <NUM> coupled with the wireless communication device <NUM> to transmit and receive wireless communications. In some implementations, the AP <NUM> additionally includes an application processor <NUM> coupled with the wireless communication device <NUM>, and a memory <NUM> coupled with the application processor <NUM>. The AP <NUM> further includes at least one external network interface <NUM> that enables the AP <NUM> to communicate with a core network or backhaul network to gain access to external networks including the Internet. For example, the external network interface <NUM> may include one or both of a wired (for example, Ethernet) network interface and a wireless network interface (such as a WWAN interface). Ones of the aforementioned components can communicate with other ones of the components directly or indirectly, over at least one bus. The AP <NUM> further includes a housing that encompasses the wireless communication device <NUM>, the application processor <NUM>, the memory <NUM>, and at least portions of the antennas <NUM> and external network interface <NUM>.

<FIG> shows a block diagram of an example STA <NUM>. For example, the STA <NUM> can be an example implementation of the STA <NUM> described with reference to <FIG>. The STA <NUM> includes a wireless communication device <NUM> (although the STA <NUM> may itself also be referred to generally as a wireless communication device as used herein). For example, the wireless communication device <NUM> may be an example implementation of the wireless communication device <NUM> described with reference to <FIG>. The STA <NUM> also includes one or more antennas <NUM> coupled with the wireless communication device <NUM> to transmit and receive wireless communications. The STA <NUM> additionally includes an application processor <NUM> coupled with the wireless communication device <NUM>, and a memory <NUM> coupled with the application processor <NUM>. In some implementations, the STA <NUM> further includes a user interface (UI) <NUM> (such as a touchscreen or keypad) and a display <NUM>, which may be integrated with the UI <NUM> to form a touchscreen display. In some implementations, the STA <NUM> may further include one or more sensors <NUM> such as, for example, one or more inertial sensors, accelerometers, temperature sensors, pressure sensors, or altitude sensors. Ones of the aforementioned components can communicate with other ones of the components directly or indirectly, over at least one bus. The STA <NUM> further includes a housing that encompasses the wireless communication device <NUM>, the application processor <NUM>, the memory <NUM>, and at least portions of the antennas <NUM>, UI <NUM>, and display <NUM>.

<FIG> and the operations described herein are examples meant to aid in understanding example implementations and should not be used to limit the potential implementations or limit the scope of the claims. Some implementations may perform additional operations, fewer operations, operations in parallel or in a different order, and some operations differently.

While the aspects of the disclosure have been described in terms of various examples, any combination of aspects from any of the examples is also within the scope of the disclosure. The examples in this disclosure are provided for pedagogical purposes. Alternatively, or in addition to the other examples described herein, examples include any combination of the following implementation options.

In some implementations, a method may be performed by an AP of a WLAN. The method may include managing a first BSS on a wireless channel. The method may include determining that at least a first STA is configured to utilize a priority access service on the wireless channel. The method may include modifying one or more settings of the first BSS based on a determination that the first STA is configured to utilize the priority access service. The one or more settings may be modified to favor a contention-based access of the wireless channel by the first STA over one or more other STAs of the first BSS that are not configured to utilize the priority access service.

In some implementations, determining that the at least first STA is configured to utilize the priority access service may include at least one of: receiving, by the AP, a message from a network operator that includes a priority access enablement indicator, receiving, from a second STA associated with the first BSS, a priority access detection indicator that indicates that the second STA has detected a priority transmission from the first AP, and detecting, by the AP, a transmission from the first STA that includes a priority access indication.

In some implementations, one or more bits of a preamble or a PHY header of the transmission from the first STA is populated with the priority access indication.

In some implementations, the transmission may include a priority service duration. The method may include reverting the one or more settings of the first BSS after the priority service duration.

In some implementations, modifying one or more settings of the first BSS includes signaling a priority service enablement indicator in the first BSS.

In some implementations, signaling the priority service enablement indicator includes outputting, for transmission via a wireless communication interface, a management frame that includes the priority service enablement indicator.

In some implementations, the management frame is a beacon frame. The priority service enablement indicator may be included in an operation element of the beacon frame.

In some implementations, the first STA is associated with a second BSS different from the first BSS. The first BSS and the second BSS may be OBSSs.

In some implementations, the priority access service is associated with a PIFS that is shorter than a DIFS used by the one or more other STAs.

In some implementations, modifying the one or more settings includes enabling a priority access class (AC_PRI) for the first STA based on the determination that the first STA is configured to utilize the priority access service.

In some implementations, the AC_PRI is associated with a first set of EDCA parameters that is different from other access classes for the one or more other STAs.

In some implementations, the AC_PRI has different EDCA parameters from those of a voice access class (AC_VO), a video access class (AC_VI), a best effort access class (AC_BE), or a background access class (AC_BK) used by the one or more other STAs.

In some implementations, the method may include advertising the AC_PRI in a beacon message.

In some implementations, modifying the one or more settings includes causing the one or more other STAs to use a different access class for the contention-based access of the wireless channel.

In some implementations, modifying the one or more settings includes causing the one or more other STAs to use a reduced TXOP duration when they win the contention-based access of the wireless channel.

In some implementations, the method may include modifying the one or more settings includes causing the one or more other STAs to adjust one or more EDCA parameters for the contention-based access of the wireless channel.

In some implementations, the method may include causing the one or more other STAs to adjust one or more EDCA parameters includes causing the one or more STAs to change an AIFSN setting, a CWmin setting, or a CWmax setting.

In some implementations, causing the one or more other STAs to adjust one or more EDCA parameters includes causing the one or more STAs to apply an offset value to an AIFSN setting, a CWmin setting, or a CWmax setting.

In some implementations, the offset value is specified in a standard technical specification.

In some implementations, the method may include signaling the offset value in a management message from the AP to the one or more other STAs.

In some implementations, the one or more other STAs includes a second STA. In some implementations, causing the one or more other STAs to apply the offset value includes applying a first offset value to one or more EDCA parameters if the second STA is using a first access class, and applying a second offset value to the one or more EDCA parameters if the second STA is using a second access class.

In some implementations, causing the one or more other STAs to adjust one or more EDCA parameters includes causing the one or more other STAs to use a modified algorithm for determining an initial backoff wait time for the contention-based access of the wireless channel.

In some implementations, the modified algorithm ignores a CWmin setting for determining the initial backoff wait time.

In some implementations, the modified algorithm is configured to determine the initial backoff wait time within a range from zero to one less than a CWmax setting.

In some implementations, the method may include, before modifying the one or more settings, determining whether the first STA is authorized to utilize the priority access service, and modifying the one or more settings if the first STA is authorized to utilize the priority access service.

In some implementations, the method may include preventing the first STA from obtaining favorable contention-based access if the first STA is not authorized to utilize the priority access service.

In some implementations, preventing the first STA from obtaining the favorable contention-based access includes one or more countermeasures. The countermeasures may include disassociating the first STA from the first BSS if the first STA is associated with the first BSS or modifying one or more EDCA parameters for the one or more other STAs.

In some implementations, a method performed by a first STA of a WLAN. The first STA may be configured to utilize a priority access service on a wireless channel. In some implementations, the method may include outputting, via a wireless communication interface, a transmission that includes a priority access indication. The method may include using a first set of EDCA parameters for a contention-based access of the wireless channel. The first set of EDCA parameters may favor the first STA over one or more other STAs that are not configured to utilize the priority access service.

In some implementations, the transmission is a PPDU.

In some implementations, one or more bits of a preamble or a PHY header of the PPDU is populated with the priority access indication.

In some implementations, the transmission includes a priority service duration.

In some implementations, the first set of EDCA parameters are associated with a priority access class (AC_PRI) that is different from other access classes for the one or more other STAs.

In some implementations, the AC_PRI has comparatively more aggressive EDCA parameters when compared to a voice access class (AC_VO), a video access class (AC_VI), a best effort access class (AC_BE), and a background access class (AC_BK) used by the one or more other STAs.

In some implementations, the method may include receiving a beacon message from an AP. The beacon message may indicate that the AP supports the priority access service. The method may include outputting, via the wireless communication interface, the transmission in response to a determination that the AP supports the priority access service.

In some implementations, the method may include transmitting a priority service activation notification to a second AP that managed an OBSS to cause the second AP to adjust EDCA parameters for non-priority STAs associated with the second AP.

In some implementations, the priority service activation notification may be included in a beacon frame or other management frame broadcast by the first AP.

Another innovative aspect of the subject matter described in this disclosure can be implemented as a method performed by a first STA of a WLAN. The method may include determining that at least a second STA is configured to utilize a priority access service for contention-based access of a wireless channel. The method may include determining that the first STA is not configured to utilize the priority access service for the contention-based access of the wireless channel. The method may include modifying one or more settings used by the first STA for the contention-based access of the wireless channel. Modifying the one or more settings may cause the second STA to have priority over the first STA.

In some implementations, determining that the at least second STA is configured to utilize the priority access service includes detecting a transmission from the second STA that includes a priority access indication.

In some implementations, the transmission includes a priority service duration. The method may include reverting the one or more settings after the priority service duration.

In some implementations, determining that the at least second STA is configured to utilize the priority access service includes receiving a priority service enablement indicator from an access point.

In some implementations, receiving the priority service enablement indicator includes receiving a management frame that includes the priority service enablement indicator.

In some implementations, modifying the one or more settings includes using a different access class for the contention-based access of the wireless channel.

In some implementations, modifying the one or more settings includes using a reduced TXOP duration when the first STA wins the contention-based access of the wireless channel.

In some implementations, the reduced TXOP duration is specified by a standard technical specification.

In some implementations, modifying the one or more settings includes adjusting one or more EDCA parameters used by the first STA for the contention-based access of the wireless channel.

In some implementations, adjusting the one or more EDCA parameters includes changing an AIFSN setting, a CWmin setting, a CWmax setting, or any combination thereof.

In some implementations, adjusting the one or more EDCA parameters includes applying an offset value to an AIFSN setting, a CWmin setting, or a CWmax setting.

In some implementations, the method may include receiving the offset value in a management message from an access point.

In some implementations, adjusting the one or more EDCA parameters includes applying a first offset value to one or more EDCA parameters if the first STA is using a first access class and applying a second offset value to the one or more EDCA parameters if the first STA is using a second access class.

In some implementations, modifying the one or more settings includes using a modified algorithm for determining an initial backoff wait time for the contention-based access of the wireless channel.

In some implementations, the method may include outputting, for transmission via a wireless communication interface, a priority detection indicator to an AP to indicate that the first STA has determined that at least the second STA is configured to utilize a priority access service. The method may include causing the AP to transmit a priority service enablement indicator to a first BSS managed by the AP.

In some implementations, the method may include causing the AP to modify one or more settings of the first BSS. The one or more settings may be modified to favor the contention-based access of the wireless channel by the second STA over one or more other STAs of the first BSS that are not configured to utilize the priority access service.

Another innovative aspect of the subject matter described in this disclosure can be implemented as an apparatus. The apparatus may include a processor configured to perform any one of the above-mentioned methods.

Another innovative aspect of the subject matter described in this disclosure can be implemented as a computer-readable medium having stored therein instructions which, when executed by a processor, causes the processor to perform any one of the above-mentioned methods.

Another innovative aspect of the subject matter described in this disclosure can be implemented as a system having means for implementing any one of the above-mentioned methods.

As used herein, a phrase referring to "at least one of" or "one or more of" a list of items refers to any combination of those items, including single members. For example, "at least one of: a, b, or c" is intended to cover the possibilities of: a only, b only, c only, a combination of a and b, a combination of a and c, a combination of b and c, and a combination of a and b and c.

The hardware and data processing apparatus used to implement the various illustrative components, logics, logical blocks, modules and circuits described in connection with the aspects disclosed herein may be implemented or performed with a general purpose single- or multi-chip processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, or any conventional processor, controller, microcontroller, or state machine. A processor also may be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. In some implementations, particular processes, operations and methods may be performed by circuitry that is specific to a given function.

As described above, in some aspects implementations of the subject matter described in this specification can be implemented as software. For example, various functions of components disclosed herein, or various blocks or steps of a method, operation, process or algorithm disclosed herein can be implemented as one or more modules of one or more computer programs. Such computer programs can include non-transitory processor- or computer-executable instructions encoded on one or more tangible processor- or computer-readable storage media for execution by, or to control the operation of, data processing apparatus including the components of the devices described herein. By way of example, and not limitation, such storage media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that may be used to store program code in the form of instructions or data structures. Combinations of the above should also be included within the scope of storage media.

Additionally, various features that are described in this specification in the context of separate implementations also can be implemented in combination in a single implementation. Conversely, various features that are described in the context of a single implementation also can be implemented in multiple implementations separately or in any suitable subcombination. As such, although features may be described above as acting in particular combinations, and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.

Claim 1:
A method for wireless communication by an access point, AP, comprising:
managing (<NUM>) a first basic service set, BSS, on a wireless channel;
determining (<NUM>) that at least a first station, STA, is configured to utilize a priority access service of the first BSS, the priority access service associated with prioritizing traffic to or from the first STA via the wireless channel,
wherein the determining that the at least first STA is configured to utilize the priority access service includes receiving a priority service request frame including a priority access indication from the first STA, and
wherein the priority access indication is included in a preamble or a physical layer, PHY, header of the priority service request frame;
the method further comprising:
modifying (<NUM>) one or more settings of the first BSS based on a determination that the first STA is configured to utilize the priority access service, wherein the one or more settings are modified to favor a contention-based access of the wireless channel by the first STA over one or more other STAs of the first BSS that are not configured to utilize the priority access service; and
transmitting a priority service response frame to the first STA to confirm that the first STA is authorized to use the priority access service.