Management of prioritized edca

Abstract

Methods, systems, and devices are described for managing high priority enhanced distributed channel access (HP EDCA). In some embodiments, a station (STA) transmits a request to an access point (AP) to use HP EDCA. The STA can receive a response from the AP to the request to use the HP EDCA. The response can indicate that the STA is accepted to use the HP EDCA, or that the STA is rejected to use the HP EDCA.

Description

Technical Field

[0001] This application relates in general to wireless communication systems, including the use of control-prioritized enhanced distributed channel access. Background Technology

[0002] Wireless communication technologies use various standards and protocols to transmit data between access points and wireless communication devices. For example, wireless communication system standards and protocols may include, for instance, 3GPP Long Term Evolution (LTE) (e.g., 4G), 3GPP New Radio (NR) (e.g., 5G), and the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard for Wireless Local Area Networks (WLANs) (often referred to as Wi-Fi within the industry organization). ® ).

[0003] In the 802.11 standard for WLAN, an access point (AP) is used to create a wireless local area network (WLAN) or Wi-Fi. ® A network device. An access point (AP) can connect to a wired network (such as Ethernet) and provide wireless access to that network for other devices. A station is a device that can wirelessly connect to an AP to join a WLAN network. A station can be a laptop, smartphone, tablet, or any other device with a WLAN adapter.

[0004] APs and stations use Wi-Fi ® The protocols communicate with each other. Various protocols have been established to improve security on wireless communication networks. For example, simultaneous authentication by peer entities is the core authentication protocol of WPA3-Personal, and is used by all Wi-Fi networks. ® All Alliance Certified devices (including both access points (APs) and non-AP stations (STAs) must support this protocol. Attached Figure Description

[0005] To facilitate the identification of any particular element or action in the discussion, one or more of the most significant digits in the figure reference numerals refer to the figure number in which the element was first introduced.

[0006] Figure 1 Example block diagrams for EDCA are shown according to some implementation schemes.

[0007] Figure 2 Example signaling diagrams using HP EDCA are shown according to some implementation schemes.

[0008] Figure 3 An example transmission timeline is illustrated according to some implementation schemes, in which four STAs compete for access to the same channel, and there is a collision of DS / CTS frames that causes L-SIG detection to fail.

[0009] Figure 4An example transmission timeline is illustrated according to some implementation schemes, in which HP EDCA STA1 sends DS / CTS, followed by RTS, but no CTS return is received due to the hidden node.

[0010] Figure 5A An example of how the action field of an SCS request frame is formed according to some implementation schemes is shown.

[0011] Figure 5B Example SCS descriptor elements are shown according to some implementation schemes.

[0012] Figure 5C Example QoS feature elements including P-EDCA usage fields are illustrated according to some implementation schemes.

[0013] Figure 5D Example control information fields are shown according to some implementation schemes.

[0014] Figure 6A Example SCS response frame action fields are shown according to some implementation schemes.

[0015] Figure 6B An example format for an SCS status list based on some implementation schemes is shown.

[0016] Figure 6C Example status code tables are shown according to some implementation schemes.

[0017] Figure 7 Example transmission timelines for HP EDCA are illustrated according to some implementation schemes.

[0018] Figure 8 Example transmission timelines for HP EDCA are illustrated according to some implementation schemes.

[0019] Figure 9 An example transmission timeline is illustrated according to some implementation schemes, where the same scrambling sequence / seed is used from the last PPDU of the previous TXOP.

[0020] Figure 10 Two example transmission timelines are illustrated according to some implementation schemes, wherein the first transmission timeline does not use HP EDCA and the second transmission timeline uses HP EDCA.

[0021] Figure 11 An example is given of a method performed by the STA according to the implementation scheme described herein.

[0022] Figure 12 An example is given of a method performed by an AP according to the implementation scheme described herein.

[0023] Figure 13 An example system for performing signaling between a wireless device and a network device according to an embodiment disclosed herein is illustrated. Detailed Implementation

[0024] Wireless communication technologies use various standards and protocols to send data between access points and wireless communication devices. One standard used for wireless communication is the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard for Wireless Local Area Networks (WLANs) (commonly referred to as Wi-Fi within the industry organization). ® Wi-Fi ® This provides a convenient way to establish a network between devices. Devices (e.g., stations) can connect to Wi-Fi. ® The access point joins the network and connects wirelessly to the Internet.

[0025] An access point (AP) is used to create a wireless local area network (WLAN) or Wi-Fi. ® Network devices. A station (STA) is a device that can wirelessly connect to an access point (AP) to join the network. A mobile AP is a device that can be used as a portable access point to provide internet access to nearby STAs. For example, a mobile AP could be a cellular phone with hotspot mode enabled.

[0026] Various implementations are described with reference to STA and AP. However, reference to STA and AP is provided for illustrative purposes only. The example implementations can be used with any electronic components that can establish a connection to a network and utilize hardware, software, and / or firmware configurations for exchanging information and data with the network. Therefore, STA and AP as described herein are used to represent any suitable electronic components.

[0027] Enhanced Distributed Channel Access (EDCA) is part of IEEE 802.11 Channel Access. EDCA is designed to improve Quality of Service (QoS) in wireless networks. It allows different types of services to be prioritized, enabling time-sensitive applications to receive better access to the wireless channel.

[0028] EDCA comprises four access categories, labeled from highest to lowest priority as Voice (VO), Video (VI), Best-effort Service (BE), and Background (BK). These categories help manage network traffic by assigning higher priority to latency-sensitive applications such as voice and video, while lower-priority services such as file downloads or email compete for remaining bandwidth.

[0029] The channel access parameters in EDCA are designed to statistically increase the likelihood that higher-priority access classes will have access to the channel and transmit frames to the radio medium (WM). This prioritization is achieved by adjusting factors such as contention window (CW) size and arbitration inter-frame space (AIFS), thereby allowing critical applications to experience minimal latency and disruption.

[0030] Figure 1 Example block diagram 102 for EDCA is illustrated according to some implementation schemes. STAs can use EDCA to prioritize packets to be transmitted. As shown, incoming MAC Service Data Units (MSDUs) along with their User Priority (UP) values ​​(e.g., MSDU, UP 104) can be mapped to access classes based on priority.

[0031] Each access category may have its own transmission queue for buffering packets before transmission. For example, there may be a VO queue 106, a VI queue 108, a BE queue 110, and a BK queue 112. Higher priority services (such as VO and VI) typically have lower latency requirements and take precedence over BE and BK services. Additionally, a per-queue EDCA function with internal conflict resolution may be present.

[0032] However, despite the statistical prioritization among access categories, there is still a possibility that higher-priority and low-latency services may be blocked and not delivered in a timely manner.

[0033] To prevent high-priority, low-latency services from being blocked, some implementations employ a high-priority (HP) EDCA (also known as priority-based EDCA (P-EDCA)) framework. Traditional EDCA has limitations that affect its ability to effectively support high-priority services. While traditional EDCA provides access opportunities for all service types, it does not guarantee channel access, even for time-sensitive applications such as voice and video. In some scenarios, lower-priority services may cause interference, making it difficult for high-priority flows to obtain transmission opportunities (TXOPs). This can lead to latency.

[0034] To address these issues, the HP EDCA mechanism can be implemented. This method separates STAs with delay-sensitive services from the general contention pool, allowing them to signal their need for prioritized access before standard EDCA contention begins. These STAs can then signal to reserve channels for a short contention interval during which STAs with delay-sensitive services can compete.

[0035] Figure 2Example signaling diagram 202 illustrates the use of HP EDCA according to some implementation schemes. In the illustrated implementation, the contention timing for the next TXOP can be based on the last frame of the previous TXOP 204. During an EDCA contention period (e.g., EDCA contention period 206), different inter-frame spaces (IFS) can define the waiting time before a station attempts to transmit, in an attempt to secure priority-based access. The shortest inter-frame space (SIFS) is the shortest and can be used for higher priority communications. The point-coordinated inter-frame space (PIFS) is slightly longer. The distributed inter-frame space (DIFS) is the longest timing interval. Different IFS can provide a mechanism to give higher priority to time-sensitive services. As shown, in HP EDCA, customized inter-frame spaces (such as AIFSNs (arbitrated inter-frame space numbers) (e.g., AIFSN 210 and AIFSN 208)) can be used to further enhance access for latency-sensitive services.

[0036] In HP EDCA, STAs with low-latency services transmit delayed signals / frames (DS), thereby bypassing existing EDCA rules. In some implementations, the DS can be a clear transmission (CTS) frame. For example, in the illustration, STA 3 and STA 4 have low-latency services. Therefore, STA 3 and STA 4 transmit DS 212 and DS 214, while other STAs without low-latency services (e.g., STA 1 and STA 2) are applying their AIFSNs.

[0037] Other STAs receiving the DS will suppress transmission for a duration known as the short contention interval. This suppression can be due to the NAV setting in the DS frame or due to older 802.11 rules that delay the receiving STAs up to the extended interframe spacing (EIFS) duration. For example, in the illustrated implementation, STA 1 and STA 2 receive DS / CTS frames from STA 3 and STA 4 and suppress transmission for the duration set by the NAV in the DS frame.

[0038] During a short contention interval, STAs that have already sent a DS frame will compete to send their low-latency data. There is a possibility that more than one STA will transmit a DS frame. STAs compete during the short contention interval. One STA wins the contention, and the other STAs later try again by sending another DS frame. For example, in the illustrated implementation, STA 3 and STA 4 compete for the next TXOP. In the illustrated implementation, STA 3 has a smaller random backoff period (BP) than STA 4. BP is the time it takes for a STA to back off in Wi-Fi... ®The randomized wait time that must be waited before attempting to send during the network's EDCA contention cycle. Because STA 3 has a smaller BP, it successfully obtains the next TXOP and transmits Request Transmission (RTS) 216, CTS 218, and its data 220. STA 4 will later attempt again by sending another DS frame.

[0039] However, there are some concerns regarding the operation of high-priority EDCA. For example, in some possible scenarios, HP EDCA may not proceed as planned, resulting in further access delays for all STAs (HP STAs and legacy STAs, etc.). HP STA can refer to a STA capable of implementing HP EDCA.

[0040] The first scenario, where HP EDCA might not proceed as planned, could involve multiple HP EDCA STAs transmitting DS / CTS frames. It's important to note that DS / CTS frames represent either dedicated DS frames transmitted by an STA for HP EDCA or CTS frames transmitted by an STA for HP EDCA. In this first scenario, collisions between DS / CTS frames could lead to failure of the legacy signal (L-SIG) (for DS / CTS frames), resulting in no short contention interval. For example, if multiple STAs transmit DS / CTS frames, signal collisions may occur, and other STAs may be unable to correctly decode the L-SIG information. This could cause other STAs to access the channel without waiting for the EIFS to expire during the short contention interval. A small contention window may give a higher probability of collisions after a DS / Request Transmission (RTS), leading to a re-evaluation of the DS / CTS.

[0041] The second scenario where HP EDCA might not proceed as planned could involve multiple Basic Service Sets (BSS). For example, if there are multiple HP EDCA STAs spanning multiple BSSs that transmit DS / CTS frames, there is a possibility of collisions and L-SIG detection failures, leading to duplicate DS / CTS transmissions.

[0042] In the third scenario where HP EDCA might not proceed as planned, the HP EDCA STA may send a DS / CTS followed by an RTS, but no CTS return is received (due to the hidden node). The STA may retry sending the DS / CTS several times, possibly with the same result.

[0043] Without any management from the AP, an HP STA may continuously attempt HP EDCA, resulting in increased channel access delay. This document provides methods, apparatus, and systems for addressing such operational concerns regarding HP EDCA.

[0044] Figure 3 and Figure 4 This is an example timeline illustrating three scenarios where HP EDCA will not proceed as planned. Specifically, Figure 3 An example transmission timeline 302 according to some implementation schemes is illustrated, in which four STAs compete for access to the same channel and there are collisions in DS / CTS frames that cause L-SIG detection failure (e.g., first scenario and second scenario). In the illustrated implementation scheme, P-EDCA STA1 304, P-EDCA STA2 306, P-EDCA STA3 308 and legacy EDCA STA 310 are using the same channel.

[0045] As shown in the figure, P-EDCA STA1 304, P-EDCA STA2 306, and P-EDCA STA3 308 can each transmit DS / CTS frames (e.g., DS / CTS 312, DS / CTS 314, and DS / CTS 316) to interrupt normal EDCA because these STAs must use HP EDCA for transmission of low-latency data. Therefore, the legacy EDCA STA 310 can receive DS / CTS frames and wait for the EIFS to expire before accessing the channel. However, in some cases, DS / CTS frames may collide, and the legacy EDCA STA 310 may fail to detect the L-SIG in the DS / CTS frame.

[0046] After a DS CTS frame is detected, P-EDCA STA1 304, P-EDCA STA2 306, and P-EDCA STA3 308 compete for the channel. In the illustrated implementation, P-EDCA STA2 306 has a longer BO period than P-EDCA STA1 304 and P-EDCA STA3 308. Therefore, P-EDCA STA2 306 does not win the contention and thus waits for another opportunity to use the channel.

[0047] However, in the illustrated implementation, both P-EDCA STA1 304 and P-EDCA STA3 308 have the same BO period, which causes them to transmit RTS frames (e.g., RTS 318 and RTS 320). In the illustrated implementation, this results in a collision between the two RTS frames, which leads to no CTS response from the AP.

[0048] When P-EDCA STA1 304 and P-EDCA STA3 308 do not receive a response, DS / CTS 322 and DS / CTS 324 transmit another DS / CTS frame (e.g., DS / CTS 322 and DS / CTS 324) and compete for the channel again. During this second competition period, P-EDCA STA1 304 has a shorter BO period than P-EDCA STA2 306 and successfully transmits RTS 326. In response, P-EDCA STA1 304 receives CTS 328 and is able to transmit its data 330. As shown, collisions can cause channel access delays.

[0049] Figure 4 An example transmission timeline 402 according to some implementation schemes is illustrated, where HP EDCA STA1 404 transmits a DS / CTS, followed by an RTS, but no CTS return is received due to a hidden node (e.g., the third scenario). As shown, HP EDCA STA1 404 may transmit DS / CTS 408, and then transmit RTS 410. However, because the channel is busy due to a hidden node 406, AP1 412 does not transmit the CTS back to HP EDCA STA1 404. Subsequently, HP EDCA STA1 404 may retry transmitting the DS / CTS and RTS frames multiple times, and continues to receive no CTS return. This may cause the legacy EDCA STA 414 to become without channel access.

[0050] The implementations described herein provide management, enabling, or admission control for prioritized EDCA channel access. Given the potential for unintended consequences of HP EDCA use, some implementations in this document recommend avoiding the “default mode” of HP EDCA with legacy BSS. In some implementations, the only mode for HP EDCA use is negotiated with a capable UHR AP. For example, the UHR AP can enable / disable the use of HP EDCA. If use is enabled, the UHR AP can recommend HP EDCA parameters. In some implementations, the UHR AP can accept / reject requests from UHR STAs to use HP EDCA. In some implementations, UHR STAs are only allowed to use HP EDCA under the conditions described above (e.g., no default HP EDCA).

[0051] In some implementations, to enable or disable HP-EDCA, the UHR AP can set a field in the UHR Operations field (e.g., "HP-EDCA parameter set exists" or "HP-EDCA enabled"), which is carried in the beacon frame sent by the UHR AP. In some implementations, if this field is set to true (e.g., set to 1), HP-EDCA is enabled, and the appended "HP-EDCA parameter set" specifies HP-EDCA attributes. Attributes such as HP-EDCA AIFSN, HP-EDCA minimum and maximum contention windows (CW), and HP-EDCA maximum TXOP duration can be specified in the HP-EDCA parameter set. The "HP-EDCA parameter set" can be carried in the beacon frame, or the UHR STA can receive this information element during authentication and association. In some implementations, if "HP-EDCA parameter set exists" or "HP-EDCA enabled" is set to false (e.g., set to 0), HP-EDCA is disabled. Changing the value of this field, either "HP-EDCA parameter set exists" or "HP-EDCA enabled", sets a critical update flag and increments the BSS parameter change count (BPCC).

[0052] In some implementations, to request or negotiate the use of HP EDCA, a UHR STA may send an HP-EDCA enable request frame to its associated UHRAP. The HP-EDCA enable request frame may include fields such as: element ID, length, element ID extension, token, service identifier (TID), link identifier (LinkID), flow classification service (SCS) identifier (SCSID), maximum data rate, minimum data rate, expected HP-EDCA duration, HP-EDCA start time, and possibly more fields. The UHR STA may specify which TID and SCSID it intends to use HP-EDCA for, and specify the minimum and maximum data rates for the service during the specified duration.

[0053] Once a UHR STA sends an HP-EDCA enable request frame to its associated UHR AP, the STA waits to receive an HP-EDCA enable response frame from its associated UHR AP. The HP-EDCA enable response frame may include the following fields: element ID, length, element ID extension, token, status code, permitted data rate, permitted HP-EDCA duration, and possibly more fields. In the status code, the AP may specify whether the request to use HP-EDCA has been accepted, rejected, or modified. The UHR AP may verify that the requesting UHR STA has a valid SCSID for the HP-EDCA usage it is requesting. If such SCSID is unavailable or has expired, the AP rejects the use of HP-EDCA. The AP may also reject the use of HP-EDCA in other circumstances. For example, the number of STAs using HP-EDCA may exceed the limits considered by the AP, or HP-EDCA may be used by some STAs for high-load traffic flows. If the request is accepted or modified, the AP may specify that the UHR STA can use HP-EDCA at the permitted data rate and for the permitted HP-EDCA duration.

[0054] In some implementations, STAs may use Flow Classification Service (SCS) / Quality of Service (QoS) features to request or negotiate the use of HP EDCA. For example, a UHR STA may also request the use of HP EDCA when negotiating the use of SCS. In some implementations, HP EDCA may be allowed only to UHR STAs when certain conditions are met. For example, a STA may be allowed to use HP EDCA if some of its pending MSDUs are reaching latency limits, or if the STA has not been triggered beyond the maximum service interval. Other conditions may be used to determine when a STA is allowed to use HP EDCA. In some implementations, a threshold number of HP EDCA usages may be disallowed between two consecutive triggers. This threshold may be pre-configured or configurable.

[0055] UHR APs can accept or reject the use of HP EDCA. The decision to accept or reject HP EDCA can be based on various parameters. For example, the decision can be based on the number of STAs already using HP EDCA.

[0056] In the SCS / QoS feature protocol, the STA can request the use of HP EDCA under certain conditions. For example, the STA can use HP EDCA if a pending MSDU is approaching the STA's latency limit. The STA can stop using HP EDCA when the SCS session is terminated or expires.

[0057] In the first scenario (Scenario 1), HP EDCA usage is enabled by the SCS+QoS feature. For example, the AP may have already enabled the HP EDCA to be used, and the STA can negotiate the parameters for HP EDCA. In some implementations, the STA can use a default HP EDCA parameter set. For example, the HP EDCA parameter set used by the STA can be a default set or a set of parameters advertised in an associated response or beacon frame. In some implementations, the STA can use the SCS procedure to negotiate the HP EDCA parameter set (this can be done using additional elements in the SCS). Negotiation of HP EDCA usage can be per-link.

[0058] In the second scenario (Scenario 2), the SCS+QoS feature may require the AP to agree to use HP EDCA. The AP can grant or deny requests from STAs to use HP EDCA. In some implementations, the AP may grant STAs permission to use the default HP EDCA parameter set (therefore, no HP EDCA parameter negotiation). In other implementations, the AP may grant STAs permission to use the provided HP EDCA parameter set (possible HP EDCA parameter negotiation).

[0059] Figures 5A to 5D An example is provided showing the SCS mechanism that a STA can use to request the use of HP EDCA. Specifically, Figure 5A An example of an SCS request frame action field formation 502 according to some implementations is illustrated. The SCS request frame action field formation 502 can be used by a STA to request the use of HP EDCA. For example, in some implementations, this request may be included in SCS descriptor element 504.

[0060] For example, Figure 5B An example SCS descriptor element 504 is illustrated according to some implementation schemes. As shown, SCS descriptor element 504 may include QoS feature element 506. A request using HP EDCA (which may also be referred to as Prioritized EDCA (P-EDCA)) may be included in QoS feature element 506.

[0061] Figure 5C An example QoS feature element 506, including a P-EDCA use field 510, is illustrated according to some implementation schemes. The P-EDCA use field 510 can be used by a STA to request the use of HP EDCA. Signaling in the QoS feature element 506 may include a control information field 508.

[0062] Figure 5D An example control information field 508 according to some implementation schemes is illustrated. As shown, control information field 508 may include an presence bitmap 512. The presence bitmap 512 may indicate Figure 5CThe presence of certain parameters in the QoS feature element 506 shown. For example, the STA can use the control information field 508 and the presence bitmap 512 to indicate the presence of a request to use HP-EDCA in the QoS feature element 506 (e.g., P-EDCA uses field 510).

[0063] In some implementations, bit 17 (B17) can be assigned for use in control information field 508 / presence bitmap 512 to indicate the presence of P-EDCA use field 510. For example, the STA can set a bit (e.g., B17) in presence bitmap 512 to one to indicate the presence of P-EDCA use field 510, and can set the bit to zero to indicate the absence of P-EDCA use field 510.

[0064] like Figure 5C As shown, a new field can be added to QoS feature element 506 for priority EDCA usage (e.g., P-EDCA usage field 510). P-EDCA usage field 510 can indicate that the STA is requesting priority EDCA for a specified link (e.g., the link identified in P-EDCA usage field 510). For example, P-EDCA usage field 510 can include the specific link for which the STA is requesting HP EDCA usage. In some implementations, P-EDCA usage field 510 can include additional subfields such as HP EDCA, CWmin, HP EDCA CWmax, HP EDCA Arbitrated Inter-Frame Space Number (AIFSN), etc. CWmin can be the minimum size of the contention window used in the backoff algorithm for HP EDCA, and CWmin can be the maximum size of the contention window used in the backoff algorithm for HP EDCA.

[0065] In some implementations, if the minimum service interval 514 / maximum service interval 516 is unspecified / unknown, the STA can set the direction subfield 518 of the control information field 508 to 0 (UL), and can also set the minimum service interval 514 / maximum service interval 516 to 0. When the minimum service interval 514 / maximum service interval 516 is set to zero in the UL direction, the AP does not consider this QoS feature element 506 as a scheduling reference. Otherwise, the STA can set the minimum service interval 514 / maximum service interval 516 per baseline.

[0066] When the AP receives an SCS request frame with an Action field setting of 502, the AP can respond to the STA to indicate whether the HP EDCA request is accepted or rejected. For example, the AP can respond to an SCS request frame with an Action field setting of 502 on a per-baseline procedure, with additional status in the SCS response indicating whether the HP EDCA request is accepted or rejected. The AP can update the use of HP EDCA by transmitting an unrequested SCS response frame with a new status code.

[0067] Figures 6A to 6C An example SCS response that can be used by an AP to respond to a request from a STA using HP EDCA is illustrated. Figure 6A An example SCS response frame action field 602 according to some implementation schemes is illustrated. The SCS response frame action field 602 may include an SCS status list 604. The SCS status list 604 may include an indication of whether the use of HP EDCA is accepted or rejected.

[0068] For example, Figure 6B An example format of an SCS status list 604 according to some implementation schemes is illustrated. As shown, the SCS status list 604 may include a status field 606. The status field 606 may indicate the status of a request from the STA. The AP may include a code in the status field 606 indicating the status of a request from the STA.

[0069] For example, Figure 6C Example status code table 608 is illustrated according to some implementation schemes. As shown, the AP can use different status codes to indicate different responses to STA requests. First status code 610 (e.g., first status code 610 could be 144) can indicate that the request for priority EDCA is rejected. First status code 610 can indicate to the STA that the SCS request was successful, but the use of priority EDCA is rejected.

[0070] The second status code 612 (for example, the second status code 612 could be 145) indicates that the request for prioritized EDCA should be modified. The second status code 612 can indicate to the STA that the SCS request was successful and that the parameters specified by the AP are acceptable for using prioritized EDCA. Therefore, if the STA wants to use prioritized EDCA, it should use the parameters specified by the AP, rather than the parameters provided by the STA in the request.

[0071] A third status code 614 (for example, third status code 614 could be 146) can indicate that the request to prioritize EDCA has been accepted. Third status code 614 can indicate to the STA that the SCS request was successful and that the parameters specified by the STA can be used to prioritize EDCA.

[0072] STAs may be allowed to use HP EDCA if the AP has accepted the request and certain conditions are met. In some implementations, STAs may be allowed to use HP EDCA if a pending MSDU is reaching a latency limit or if the STA has not been triggered beyond the maximum service interval. Between two consecutive trigger events, STAs may not be allowed to use HP EDCA more than a threshold number of times (e.g., once).

[0073] The parameters for prioritizing EDCA define various aspects of HP EDCA transmission usage. In some implementations, low-latency data can be defined. Without proper definition, HP EDCA can be used by many types of services. Conditions may exist for transmitting DS / CTS signals specific to HP EDCA.

[0074] For example, in some implementations, the condition for sending a DS / CTS can be based on a retry count (e.g., if an MSDU is sent but not acknowledged: QSRC[AC_VO] > threshold). For example, in some implementations, if a STA attempts to send an MSDU but fails to receive an ACK from the AP for a threshold number of times, the STA may be allowed to send a DS / CTS for HP EDCA.

[0075] In some implementations, the condition for sending a DS / CTS can be based on the arrival of a delay limit for a pending MSDU. For example, if a delay limit for transmitting an MSDU is reached, the STA can send a DS / CTS to transmit the MSDU via HP EDCA.

[0076] In some implementations, the use of HP EDCA may be limited to certain access classes. For example, in some implementations, only AC_VO may be allowed to use HP EDCA. The channel access parameters used to transmit DS may be AIFSN=2 and CW=0. Regarding the short contention period, the duration of the short contention period may be a set time amount (e.g., EIFS=94us). Channel access after the transmission of the DS frame may be AIFSN=2, CWmin / CWmax=7. Regarding the DS / CTS retry count, the number of consecutive HP EDCA attempts (retries) allowed can be defined.

[0077] In some implementations, new parameters can define limits on the use of DS / CTS transmissions for HP EDCA. DS / CTS usage limits can be the number of successful HP EDCA transmissions allowed per interval. For example, some implementations may introduce an HP EDCA timer. The timer can define when the STA can transmit the next DS / CTS transmission. For example, if the HP EDCA timer has not yet reached zero, the STA may not be allowed to transmit DS / CTS.

[0078] Figure 7 An example transmission timeline 702 for HP EDCA is illustrated according to some implementation schemes. As previously discussed, the DS frame can be a CTS frame. The bandwidth of the DS / CTS frame can be based on the bandwidth of the associated RTS frame. For example, the DS / CTS frame may have a larger bandwidth than or the same as the subsequent RTS frame. Otherwise, when the bandwidth of the DS / CTS frame is less than the bandwidth of the subsequent RTS frame, there is a possibility of unfairness for STAs operating on (or having) the primary channel of the remaining channels (i.e., all channels except the primary channel of the transmitter of the DS frame).

[0079] For example, in the illustrated implementation, the HP EDCA STA 704 uses a 20MHz bandwidth to transmit the DS / CTS frame 708. However, an 80MHz bandwidth is used to transmit the subsequent RTS frame 710 and data 712. Therefore, the legacy EDCA STA 706 can transmit data transmission 714 that is subject to interference and collisions from the HP EDCA STA 704.

[0080] To prevent this conflict or interference between the HP EDCA STA 704 and the older EDCA STA 706, in the illustrated example, the HP EDCA STA 704 can transmit DS / CTS frames in a non-HT repeat format within an 80MHz bandwidth. The HP EDCA STA 704 can use the same or a larger bandwidth (e.g., 20MHz, 40MHz, 60MHz, or 80MHz) as the RTS frames it intends to transmit to transmit DS / CTS frames 708.

[0081] For example, Figure 8 An example transmission timeline 802 for HP EDCA according to some implementation schemes is illustrated. As previously discussed, DS frames can be CTS frames. The bandwidth of a DS / CTS frame can be based on the bandwidth of the associated RTS frame. For fairness in wideband channel usage, the bandwidth of the RTS frame should not exceed the bandwidth of the preceding DS / CTS frame. Furthermore, DS / CTS frames can be transmitted in a non-HT repetition format, where the same content of the DS / CTS frames in the primary 20MHz band is repeated across each remaining 20MHz subband.

[0082] For example, in the illustrated implementation, the HP EDCA STA 804 transmits the DS / CTS frame 808 with the same bandwidth as the subsequent RTS frame 810 and data 812. Therefore, the legacy EDCA STA 806 can omit data transmission, thus preventing collisions.

[0083] The content of a DS / CTS frame may depend on the following: frame control and duration fields, receive address (RA), and scrambler seed. For the frame control and duration fields, these fields can be set as in the baseline specification. In some implementations, the STA may set the modulation and decoding scheme (MCS) of the DS / CTS frame to a known MCS previously indicated by the AP in the beacon frame or communicated to each associated STA during association. In some implementations, the STA may set the MCS of the DS / CTS frame to a known MCS as specified in the 802.11 specification, such as MCS0 or MCS1.

[0084] For the RA address, the DS / CTS frame may have only one address field: RA. Options for setting the RA field may include the following: In some implementations, the STA may set the RA to the Basic Service Set Identifier (BSSID). The BSSID is a unique address within the BSS. In some implementations, the STA may set the RA to a known address previously indicated by the AP in a beacon frame or communicated to each associated STA during association. In some implementations, the STA may set the RA to a known address specified in the 802.11 specification, such as a broadcast address.

[0085] In some implementations, the STA can set the RA to a predefined address used by all HP EDCA STAs. For example, the STA can use a reserved MAC address for CTS transmissions made in accordance with HP EDCA rules. This helps all UHR APs identify CTS transmissions made using HP EDCA and manage the scope and frequency of HP EDCA usage, even in OBSS scenarios where the STA is associated with other APs using HP EDCA.

[0086] Regarding scrambler seeds, the scrambler seed alters the bit sequence of a frame. Therefore, even if two DS / CTS frames have the same content, their bit sequences may differ if their scrambler seeds are different, and OFDM symbols carrying the MAC payload may collide if two CTS frames are transmitted simultaneously. To reduce the possibility of collisions between multiple DS / CTS frames, HP EDCA STAs can always use the same scrambler seed when they transmit a CTS as a DS frame. However, if a given HP EDCA STA does not know whether other STAs are transmitting CTSs as DS frames, a common / unique scrambler seed can be assigned to the DS / CTS frames. In another implementation, all HP EDCA STAs attempting to transmit a DS or CTS frame after the last PPDU from the previous TXOP can use the same scrambling sequence as the last PPDU from the previous TXOP. For example, Figure 2Both STA 3 and STA 4 can use the same scrambling sequence from the last PPDU of the last frame from TXOP 204. This ensures that both STA 3 and STA 4 use the same scrambling sequence.

[0087] For example, Figure 9 Example transmission timelines according to some implementations are illustrated, where the same scrambling sequence / seed is used from the last PPDU of the previous TXOP. As shown, HP-EDCA STA1 910 may use the scrambling sequence / seed during the last PPDU of the previous TXOP 906. HP-EDCA STA1 910 may use the same scrambling sequence / seed during the transmission of DS / CTS 908. Similarly, HP-EDCA STA2 912 may use the scrambling sequence / seed during the last PPDU of the previous TXOP 904. HP-EDCA STA2 912 may use the same scrambling sequence / seed during the transmission of DS / CTS 902.

[0088] Figure 10 Two example transmission timelines are illustrated according to some implementation schemes, wherein a first transmission timeline 1002 does not use HP EDCA, and a second transmission timeline 1004 uses HP EDCA. This example illustrates the motivation for prioritizing EDCA in SCS.

[0089] For QoS flows with strict delay limits, the STA may fail to meet those limits. The STA may fail to meet the delay limits due to insufficient triggering by the AP. This could occur due to reasons such as AP overuse, insufficient STA triggering with enough RUs, insufficient STA triggering frequency, or channel congestion on the AP side. Another reason the STA may fail to meet the delay limits is due to aperiodicity or jitter in data arrival at the STA. In the example illustrated in the first transmission timeline 1002, the STA fails to meet delay limit 1006.

[0090] In these situations, HP EDCA can help the STA transmit MSDUs with their delay limits close to the threshold. For example, in the second transmission timeline 1004, the STA uses HP EDCA 1008 and is able to successfully transmit UL PPDU 1010 before the delay limit 1012.

[0091] Figure 11A method 1100 performed by a STA according to an embodiment of this document is illustrated. The illustrated method 1100 includes: transmitting a request to the AP 1102 to use HP EDCA. Method 1100 further includes: receiving from the AP 1104 a response to the request to use HP EDCA. Method 1100 further includes: in response to a response indicating acceptance of the STA's use of HP EDCA, using HP EDCA 1106 to obtain a transmission opportunity on the channel and transmit data packets. Method 1100 further includes: in response to a response indicating rejection of the STA's use of HP EDCA, abandoning the use of HP EDCA 1108.

[0092] In some implementations of method 1100, HP EDCA is permitted in cases where some pending MSDUs are reaching latency limits or where the STA has not yet been triggered to exceed the maximum service interval.

[0093] In some implementations of method 1100, the STA is not allowed to use HP EDCA more than a threshold number of times between two consecutive triggers.

[0094] In some implementations of method 1100, the request includes an SCS request frame that includes QoS feature elements with an HPEDCA usage field.

[0095] In some implementations of method 1100, the STA uses the default HP EDCA parameter set.

[0096] In some implementations, method 1100 further includes negotiating an HP EDCA parameter set with the AP. Some such implementations also include transmitting the requested HP EDCA parameter set to the AP and receiving a modified HP EDCA parameter set in a response.

[0097] In some embodiments of method 1100, using HP EDCA includes: transmitting CTS frames, wherein the transmission of CTS frames for HP EDCA is limited by an HP EDCA timer.

[0098] In some implementations of method 1100, using HP EDCA includes: transmitting a CTS frame and a corresponding RTS frame, wherein the CTS frame has a larger or the same bandwidth as the corresponding RTS frame.

[0099] In some implementations of method 1100, using HP EDCA includes: transmitting a CTS frame, wherein the CTS frame includes an RA and a scrambler seed, wherein for all CTS frames used for HP EDCA, the RA is a reserved MAC address for the DS / CTS transmitted in accordance with HP EDCA rules, and wherein the scrambler seed is the same for all CTS frames used for HP EDCA.

[0100] Figure 12 A method 1200 performed by an AP according to an embodiment of this document is illustrated. The illustrated method 1200 includes: receiving 1202 a request from a STA to use HP EDCA. Method 1200 further includes: transmitting 1204 a response to the request to use HP EDCA to the STA, wherein the response indicates acceptance of HP EDCA use by the STA, or rejection of HP EDCA use by the STA. Method 1200 further includes: receiving 1206 data packets from the STA via HP EDCA or normal EDCA, at least in part based on the response.

[0101] In some implementations of method 1200, HP EDCA is permitted in cases where some pending MSDUs are reaching latency limits or where the STA has not yet been triggered to exceed the maximum service interval and the response indicates acceptance of HP EDCA.

[0102] In some implementations of method 1200, a threshold number of times is defined, and the STA is not allowed to use HP EDCA more than the threshold number of times between two consecutive triggers.

[0103] In some implementations of method 1200, the request includes an SCS request frame that includes QoS feature elements with an HPEDCA usage field.

[0104] In some implementations of method 1200, a default HP EDCA parameter set is defined for use with HP EDCA.

[0105] In some implementations, method 1200 further includes negotiating an HP EDCA parameter set with the STA. Some such implementations also include receiving a requested HP EDCA parameter set from the STA and transmitting a modified HP EDCA parameter set in a response.

[0106] In some implementations, method 1200 further includes setting an HP EDCA timer, wherein the transmission of CTS frames for HP EDCA is limited by the HP EDCA timer.

[0107] In some implementations, method 1200 further includes receiving a CTS frame and a corresponding RTS frame for HP EDCA from the STA, wherein the CTS frame has a larger or the same bandwidth as the corresponding RTS frame.

[0108] In some implementations, method 1200 further includes: receiving a CTS frame for HP EDCA from a STA, wherein the CTS frame includes an RA and a scrambler seed, wherein for all CTS frames for HP EDCA, the RA is a reserved MAC address for DS / CTS sent in accordance with HP EDCA rules, and wherein the scrambler seed is the same for all CTS frames for HP EDCA.

[0109] Figure 13 A system 1300 for performing signaling 1334 between STA 1302 and AP 1318 according to an embodiment disclosed herein is illustrated. System 1300 may be part of a wireless communication system as described herein. STA 1302 may be, for example, a UE of a wireless communication system. AP 1318 may be, for example, an access point of a wireless communication system.

[0110] STA 1302 may include one or more processors 1304. Processor 1304 may execute instructions to cause various operations of STA 1302 to be performed as described herein. Processor 1304 may include one or more baseband processors, which may be implemented using, for example, a central processing unit (CPU), digital signal processor (DSP), application-specific integrated circuit (ASIC), controller, field-programmable gate array (FPGA) device, another hardware device, firmware device, or any combination thereof configured to perform the operations described herein.

[0111] STA 1302 may include memory 1306. Memory 1306 may be a non-transitory computer-readable storage medium that stores instructions 1308, which may include, for example, instructions executed by processor 1304. Instructions 1308 may also be referred to as program code or a computer program. Memory 1306 may also store data used by processor 1304 and results calculated by the processor.

[0112] STA 1302 may include one or more transceivers 1310, which may include radio frequency (RF) transmitter circuitry and / or receiver circuitry that uses antenna 1312 of STA 1302 to facilitate signaling (e.g., signaling 1334) to and / or from STA 1302 to other devices (e.g., AP 1318).

[0113] STA 1302 may include one or more antennas 1312 (e.g., one, two, four or more). In embodiments with multiple antennas 1312, STA 1302 can fully utilize the spatial diversity of such multiple antennas 1312 to transmit and / or receive multiple different data streams on the same time-frequency resource. This behavior may be referred to as, for example, multiple-input multiple-output (MIMO) behavior (referring to multiple antennas used at each of the transmitting and receiving devices to implement this aspect). MIMO transmission by STA 1302 can be achieved according to pre-decoding (or digital beamforming) applied at STA 1302, which multiplexes data streams across antennas 1312 based on known or assumed channel characteristics, such that each data stream is received with appropriate signal strength relative to the other streams at a desired location in the spatial domain (e.g., the location of the receiver associated with that data stream). Some implementations may use a single-user MIMO (SU-MIMO) approach (where all data streams are directed to a single receiver) and / or a multi-user MIMO (MU-MIMO) approach (where individual data streams may be directed to individual (different) receivers at different locations in the airspace).

[0114] In some implementations with multiple antennas, STA 1302 can implement analog beamforming technology, whereby the phase of the signal transmitted by antenna 1312 is relatively adjusted, enabling (joint) transmission of the directional antenna 1312 (this is sometimes referred to as beam control).

[0115] STA 1302 may include one or more interfaces 1314. Interfaces 1314 can be used to provide input to or from the AP. For example, STA 1302 as a UE may include interfaces 1314, such as microphones, speakers, touchscreens, and buttons, to allow users of the UE to input to and / or output to the UE. Other interfaces of such UEs may consist of transmitters, receivers, and other circuitry that allow the UE to communicate with other devices (e.g., in addition to the transceiver 1310 / antenna 1312 already described), and may be based on known protocols (e.g., Wi-Fi). ® and Bluetooth ® (etc.) to perform the operation.

[0116] STA 1302 may include HP EDCA module 1316. HP EDCA module 1316 may be implemented via hardware, software, or a combination thereof. For example, HP EDCA module 1316 may be implemented as a processor, circuitry, and / or instructions 1308 stored in memory 1306 and executed by processor 1304. In some examples, HP EDCA module 1316 may be integrated within processor 1304 and / or transceiver 1310. For example, HP EDCA module 1316 may be implemented via a combination of software components and hardware components (e.g., logic gates and circuitry) within processor 1304 or transceiver 1310 (e.g., executed by a DSP or general-purpose processor).

[0117] The HP EDCA module 1316 can be used in various aspects of this disclosure, for example, Figures 1 to 12 All aspects.

[0118] AP 1318 may include one or more processors 1320. Processor 1320 is executable instructions that cause AP 1318 to perform various operations as described herein. Processor 1320 may include one or more baseband processors, which may be implemented using, for example, a CPU, DSP, ASIC, controller, FPGA device, another hardware device, firmware device, or any combination thereof configured to perform the operations described herein.

[0119] AP 1318 may include memory 1322. Memory 1322 may be a non-transitory computer-readable storage medium that stores instructions 1324, which may include, for example, instructions executed by processor 1320. Instructions 1324 may also be referred to as program code or a computer program. Memory 1322 may also store data used by processor 1320 and results calculated by the processor.

[0120] AP 1318 may include one or more transceivers 1326, which may include RF transmitter circuitry and / or receiver circuitry that uses the antenna 1328 of AP 1318 to facilitate signaling (e.g., signaling 1334) to and / or from AP 1318 to other devices (e.g., STA 1302).

[0121] AP 1318 may include one or more antennas 1328 (e.g., one, two, four or more). In embodiments with multiple antennas 1328, AP 1318 may perform MIMO, digital beamforming, analog beamforming, beam control, etc., as already described.

[0122] AP 1318 may include one or more interfaces 1330. Interface 1330 can be used to provide input to or from AP 1318. For example, AP 1318 as a base station may include interface 1330 consisting of transmitters, receivers and other circuitry (e.g., in addition to the transceiver 1326 / antenna 1328 already described), which enables the base station to communicate with other equipment in the core network and / or enables the base station to communicate with external networks, computers and databases, etc., for the purpose of operating, managing and maintaining the base station or other equipment operable to the base station.

[0123] AP 1318 may include HP EDCA module 1332. HP EDCA module 1332 may be implemented via hardware, software, or a combination thereof. For example, HP EDCA module 1332 may be implemented as a processor, circuitry, and / or instructions 1324 stored in memory 1322 and executed by processor 1320. In some examples, HP EDCA module 1332 may be integrated within processor 1320 and / or transceiver 1326. For example, HP EDCA module 1332 may be implemented via a combination of software components and hardware components (e.g., logic gates and circuitry) within processor 1320 or transceiver 1326 (e.g., executed by a DSP or general-purpose processor).

[0124] The HP EDCA module 1332 can be used in various aspects of this disclosure, for example, Figures 1 to 12 All aspects.

[0125] The embodiments contemplated herein include an apparatus comprising components for performing one or more elements of method 1100. This apparatus may be, for example, an STA (such as STA 1302, as described herein).

[0126] The embodiments contemplated herein include one or more non-transitory computer-readable media comprising instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of method 1100. The non-transitory computer-readable medium may be, for example, memory of an STA (such as memory 1306 of STA 1302, as described herein).

[0127] The embodiments contemplated herein include an apparatus comprising logic components, modules, or circuitry for performing one or more elements of method 1100. This apparatus may be, for example, an STA (such as STA 1302, as described herein).

[0128] The embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media, the one or more computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of method 1100. The apparatus may be, for example, an STA (such as STA 1302, as described herein).

[0129] The implementation scheme envisioned herein includes a signal as described in or related to one or more elements of method 1100.

[0130] The embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution of the program by a processor will cause the processor to perform one or more elements of method 1100. The processor may be a processor of the STA (such as processor 1304 of STA 1302, as described herein). These instructions may, for example, reside in the processor and / or in the memory of the STA (such as memory 1306 of STA 1302, as described herein).

[0131] The embodiments contemplated herein include an apparatus comprising components for performing one or more elements of method 1200. This apparatus may be, for example, an AP (such as AP 1318, as described herein).

[0132] The embodiments contemplated herein include one or more non-transitory computer-readable media comprising instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of method 1200. The non-transitory computer-readable medium may be, for example, the memory of an access point (such as memory 1322 of AP 1318, as described herein).

[0133] The embodiments contemplated herein include an apparatus comprising logic components, modules, or circuitry for performing one or more elements of method 1200. This apparatus may be, for example, an AP (such as AP 1318, as described herein).

[0134] The embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of method 1200. The apparatus may be, for example, an AP (such as AP1318, as described herein).

[0135] The implementation scheme envisioned herein includes a signal as described in or related to one or more elements of method 1200.

[0136] The embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution by a processing element causes the processing element to perform one or more elements of method 1200. The processor may be the processor of the AP (such as processor 1320 of AP 1318, as described herein). These instructions may, for example, reside in the processor and / or the memory of the AP (such as memory 1322 of AP 1318, as described herein).

[0137] For one or more embodiments, at least one of the components illustrated in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, and / or methods as set forth herein. For example, a processor described herein in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples set forth herein. Similarly, circuitry associated with a STA or AP described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples set forth herein.

[0138] Unless otherwise expressly stated, any of the embodiments described above may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific embodiments provides illustrative and descriptive information, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. In light of the teachings above, modifications and variations are possible, or modifications and variations may be derived from practice with various embodiments.

[0139] Implementations and specific embodiments of the systems and methods described herein may include various operations embodied in machine-executable instructions to be executed by a computer system. The computer system may include one or more general-purpose or special-purpose computers (or other electronic devices). The computer system may include hardware components, including specific logical parts for performing the operations; or may include a combination of hardware, software, and / or firmware.

[0140] It should be recognized that the systems described herein include descriptions of specific implementations. These implementations may be combined into a single system, partially integrated into other systems, divided into multiple systems, or otherwise partitioned or combined. Furthermore, it is conceivable to use parameters, attributes, aspects, etc., of one implementation in one implementation. For clarity, these parameters, attributes, aspects, etc., are described only in one or more implementations, and it should be recognized that, unless expressly stated herein, these parameters, attributes, aspects, etc., may be combined with or substituted for parameters, attributes, aspects, etc., of another implementation.

[0141] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0142] Although the foregoing has been described in considerable detail for clarity, it will be apparent that certain changes and modifications can be made without departing from the principles of the invention. It should be noted that there are many alternative ways to implement both the processes and apparatus described herein. Therefore, embodiments of the invention should be considered illustrative rather than restrictive, and this specification is not limited to the details given herein, but can be modified within the scope and equivalents of the appended claims.

Claims

1. A method performed by a station (STA), the method comprising: Send a request to the access point (AP) to use High Priority Enhanced Distributed Channel Access (HP EDCA); Receive a response from the AP to the request for using the HP EDCA; In response to the instruction to accept the STA's use of the HP EDCA, the STA uses the HP EDCA to obtain a transmission opportunity on the channel and transmit data packets; and In response to the indication that the STA is denied access to the HP EDCA, the use of the HP EDCA is abandoned.

2. The method of claim 1, wherein the HP EDCA is permitted when some pending Media Access Control Service Data Units (MSDUs) are reaching latency limits or when the STA has not yet been triggered beyond the maximum service interval.

3. The method of claim 1, wherein the STA is not allowed to use the HPEDCA more than a threshold number of times between two consecutive triggers.

4. The method of claim 1, wherein the request includes a Flow Classification Service (SCS) request frame, the Flow Classification Service (SCS) request frame including a Quality of Service (QoS) characteristic element having an HP EDCA usage field.

5. The method of claim 1, wherein the STA uses the default HP EDCA parameter set.

6. The method according to claim 1, further comprising: Negotiate the HP EDCA parameter set with the AP.

7. The method according to claim 6, further comprising: Send the requested HP EDCA parameter set to the AP; as well as The modified HP EDCA parameter set is received in the response.

8. The method of claim 1, wherein using the HP EDCA comprises: Transmit a Clear Transmit (CTS) frame, wherein the transmission of the CTS frame for the HP EDCA is limited by the HP EDCA timer.

9. The method of claim 1, wherein using the HP EDCA comprises: The transmission includes a Clear Transmission (CTS) frame for initiating an HP EDCA contention interval in a non-high throughput repeating (non-HT repeating) Physical Protocol Data Unit (PPDU) format and a Corresponding Request Transmission (RTS) frame for initiating a Transmission Opportunity (TXOP), wherein the CTS frame has a larger or the same bandwidth than the corresponding RTS frame.

10. The method of claim 1, wherein using the HP EDCA comprises: Transmit a Clear Transmit (CTS) frame, wherein the CTS frame includes a Receive Address (RA) and a scrambler seed. Wherein, for all CTS frames used in the HP EDCA, the RA is a reserved MAC address for DS / CTS transmitted according to the HP EDCA rules, and The scrambler seed is the same for all CTS frames used in the HP EDCA.

11. The method of claim 1, wherein using the HP EDCA comprises: Transmit a Clear Transmit (CTS) frame, wherein the CTS frame uses the same scrambling sequence as the scrambling sequence used for the last Physical Protocol Data Unit (PPDU) from the previous Transmit Opportunity (TXOP).

12. The method of claim 1, wherein using the HP EDCA comprises: Transmit a Clear Transmission (CTS) frame, wherein the CTS frame includes: A known modulation and decoding scheme (MCS) indicated by the AP in the beacon frame, communicated during association, or pre-specified; and The receiving address (RA) is set to a known address indicated by the AP in the beacon frame, or communicated during the association, or pre-specified.

13. A method performed by an access point (AP), the method comprising: The slave station (STA) receives a request to use High Priority Enhanced Distributed Channel Access (HP EDCA); as well as The STA is sent a response to the request to use the HP EDCA. The response indicates that the STA is allowed to use the HP EDCA, or The STA was denied access to the HP EDCA. as well as Data packets are received from the STA via HP EDCA or normal EDCA, at least in part, based on the response.

14. The method of claim 13, wherein the HP EDCA is permitted when some pending Media Access Control Service Data Units (MSDUs) are reaching latency limits or when the STA has not been triggered beyond the maximum service interval and the response indicates acceptance of the use of the HP EDCA.

15. The method of claim 13, wherein a threshold number of times is defined, and the STA is not allowed to use the HP EDCA more than the threshold number of times between two consecutive triggers.

16. The method of claim 13, wherein the request includes a Flow Classification Service (SCS) request frame, the Flow Classification Service (SCS) request frame including a Quality of Service (QoS) characteristic element having an HP EDCA usage field.

17. The method of claim 13, wherein a default HP EDCA parameter set is defined for the use of the HP EDCA.

18. The method according to claim 13, further comprising: Negotiate the HP EDCA parameter set with the STA.

19. The method according to claim 18, further comprising: Receive the requested HP EDCA parameter set from the STA; as well as The modified HP EDCA parameter set is transmitted in the response.

20. The method according to claim 13, further comprising: Configure an HP EDCA timer, wherein the transmission of CTS frames for the HP EDCA is limited by the HP EDCA timer.

21. The method according to claim 13, further comprising: The STA receives a Clear Transmission (CTS) frame for initiating HP EDCA in a non-high throughput repeating (non-HT repeating) Physical Protocol Data Unit (PPDU) format, and after a contention interval, receives a Corresponding Request Transmission (RTS) frame for initiating a Transmission Opportunity (TXOP), wherein the CTS frame has a larger or the same bandwidth than the corresponding RTS frame.

22. The method according to claim 13, further comprising: Receive a Clear Transmit (CTS) frame for the HP EDCA from the STA, wherein the CTS frame includes a Receive Address (RA) and a scrambler seed. Wherein, for all CTS frames used in the HP EDCA, the RA is a reserved MAC address for DS / CTS transmitted according to the HP EDCA rules, and The scrambler seed is the same for all CTS frames used in the HP EDCA.

23. An apparatus comprising components for performing the method according to any one of claims 1 to 22.

24. A computer-readable medium comprising instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform the method according to any one of claims 1 to 22.

25. An apparatus comprising a logic component, module, or circuitry for performing the method according to any one of claims 1 to 22.

Images