Dynamic EDCA in R-TWT initial access

Abstract

An adaptive set of RTA adaptive EDCA rules and structures are provided that allow non-AP STAs to send RTA packets within the R-TWT SP. The RTA adaptive EDCA parameter set can be selected in response to receiving a trigger from the associated AP or by pre-configuration. Non-AP STAs that are R-TWT members or non-members of the current R-TWT SP can switch from using normal EDCA parameters to new RTA adaptive EDCA parameters within the R-TWT SP. Various rules regarding the duration of use are described, but the AP can prevent STAs from using the new RTA adaptive EDCA at any time within the R-TWT SP.

Description

[Technical field]

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

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

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

[0004] The techniques of this disclosure relate generally to 802.11 compliant wireless communications utilizing Enhanced Distributed Channel Access (EDCA), and more particularly to enhanced EDCA that is particularly beneficial for real-time traffic. [Background technology]

[0005] Wireless communications according to certain IEEE 802.11 protocols include enhanced distributed channel access (EDCA), under which high priority traffic has a higher probability of being transmitted than low priority traffic, for example, stations with high priority traffic generally wait less time before being able to transmit a packet than stations with low priority traffic.

[0006] EDCA also provides contention-free access to the channel over a bounded time interval called a Transmit Opportunity (TXOP), and a station may transmit as many frames as it wishes within the maximum duration of a TXOP. Traffic priority levels in EDCA are called Access Categories (AC). The contention window (CW) can vary for each type of traffic in each access category. Summary of the Invention [Problem to be solved by the invention]

[0007] However, EDCA has shortcomings, especially when it comes to handling real-time application (RTA) traffic, since it cannot handle dynamic situations efficiently.

[0008] Thus, there is a need for an enhanced EDCA-based protocol that can achieve higher efficiency levels by reducing RTA packets that time out upon expiration of RTA packet lifetime thresholds. The present disclosure fulfills this need and provides further advantages. [Means for solving the problem]

[0009] A new EDCA mechanism is described that dynamically adjusts Enhanced Distributed Channel Access (EDCA) in response to the Access Category (AC) of the buffered RTA MAC Service Data Units (MSDUs) and the dynamically decreasing Real Time Application (RTA) Lifetime value. Based on the AC of the buffered MSDUs and the remaining RTA Lifetime, a new RTA Adaptive EDCA Parameter Set is defined with new EDCA parameters. The new RTA Adaptive EDCA Parameter Set provides multiple threshold levels for evaluating the remaining RTA Lifetime. As time passes and the viable lifetime of the MSDUs decreases toward the end, the STAs can use the new RTA Adaptive EDCA Parameter Set to increase the probability of transmitting these MSDUs before their lifetime expires. In at least one case, the maximum backoff when using these new RTA Adaptive EDCA Parameter Sets is less than the initial remaining RTA Lifetime of the MSDUs. Many options and variations are described throughout the following description.

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

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

[0012] [Figure 1] FIG. 2 is a data field diagram of a typical (conventional) EDCA parameter set element. [Diagram 2] FIG. 13 is a data field diagram of the EDCA update information field used for S1G STA. [Diagram 3] FIG. 2 is a data field diagram of a parameter record field shown in FIG. 1. [Figure 4] FIG. 4 is a data field diagram of the field format of the ACI / AIFSN subfield shown in FIG. 3. [Diagram 5] FIG. 4 is a data field diagram detailing the ECWmin / ECWmax fields shown in FIG. 3. [Figure 6] FIG. 1 is a data field diagram of an MU EDCA parameter set. [Figure 7] FIG. 13 is a data field diagram of the MU AC parameter record field. [Figure 8] FIG. 13 is a data field diagram of a QoS information field. [Figure 9] FIG. 2 is an interlayer communication diagram of an SCS request and response. [Figure 10] FIG. 13 is a data field diagram of the SCS descriptor element. [Figure 11] FIG. 13 is a data field diagram of a QoS characteristic element. [Figure 12] FIG. 11 is a data field diagram of a control information subfield. [Figure 13] FIG. 2 is a block diagram of communication station hardware in accordance with at least one embodiment of the present disclosure. [Figure 14] FIG. 1 is a block diagram of a multi-link device (MLD) hardware in accordance with at least one embodiment of the present disclosure. [Figure 15] FIG. 1 is a network topology diagram utilized in accordance with at least one embodiment of the present disclosure. [Figure 16] FIG. 1 is a flow diagram of adaptive EDCA operation at the AP side in accordance with at least one embodiment of the present disclosure. [Figure 17] 1 is a flow diagram of adaptive EDCA operation for a non-AP STA in accordance with at least one embodiment of the present disclosure. [Figure 18] 1 is a flow diagram of adaptive EDCA operation for a non-AP STA in accordance with at least one embodiment of the present disclosure. [Figure 19] 1 is a flow diagram of adaptive EDCA operation for a non-AP STA in accordance with at least one embodiment of the present disclosure. [Figure 20]1 is a flow diagram of adaptive EDCA operation for a non-AP STA in accordance with at least one embodiment of the present disclosure. [Figure 21] FIG. 2 is a data field diagram of an element ID field in accordance with at least one embodiment of the present disclosure. [Figure 22] FIG. 1 is a data field diagram of an RTA adaptive AC parameter record in accordance with at least one embodiment of the present disclosure. [Diagram 23] FIG. 23 is a data field diagram of the ACI Lifetime / AIFSN subfield shown in FIG. 22 in accordance with at least one embodiment of the present disclosure. [Figure 24] FIG. 2 is a data field diagram of an RTA adaptive EDCA reset frame in accordance with at least one embodiment of the present disclosure. [Diagram 25] FIG. 2 is a data field diagram of an RTA adaptive EDCA control field in accordance with at least one embodiment of the present disclosure. [Figure 26] FIG. 2 is a communication diagram of Example 1 using triggerable RTA adaptive EDCA, in accordance with at least one embodiment of the present disclosure. [Figure 27] FIG. 11 is a communication diagram of Example 2 using triggerable RTA adaptive EDCA, in accordance with at least one embodiment of the present disclosure. [Figure 28] FIG. 11 is a communication diagram of Example 3 using triggerable RTA adaptive EDCA in accordance with at least one embodiment of the present disclosure. [Figure 29] FIG. 11 is a communication diagram of Example 4 using triggerable RTA adaptive EDCA, in accordance with at least one embodiment of the present disclosure. [Diagram 30] FIG. 11 is a communication diagram of Example 5 using triggerable RTA adaptive EDCA in accordance with at least one embodiment of the present disclosure. [Diagram 31] FIG. 13 is a communication diagram of Example 6 using triggerable RTA adaptive EDCA in accordance with at least one embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] 1. Introduction Current wireless technologies using Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA) focus on high throughput network performance but lack the critical low latency capability. However, many applications, such as Real Time Applications (RTA), require low latency packet delivery, which is not adequately addressed.

[0014] RTA requires low latency communication and uses best effort communication. Data generated from RTA is called RTA traffic and is packetized as RTA frames at a transmitting station (STA), whereas non-time sensitive traffic, referred to herein as non-RTA traffic, is packetized as non-RTA frames at the transmitting STA.

[0015] RTA frames require low latency due to their high timely delivery requirements. They are only valid if they are delivered within a certain period of time, called their lifetime. One solution in CSMA / CA wireless technology is to schedule a Service Period (SP) of Restricted Target Wake Time (R-TWT) defined in 802.11be for RTA frame exchange. This TWT allows devices to decide when and how often to wake up to transmit or receive data.

[0016] An R-TWT SP is scheduled to complete transmissions to and from a group of non-AP STAs that are R-TWT members of this SP. Non-AP Very High Throughput (EHT) STA Transmission Opportunity (TXOP) owners that have agreed to an R-TWT schedule but are not members of the R-TWT SP must ensure that they finish their TXOP before the start of any R-TWT SP if the TXOP is acquired outside of the R-TWT SP.

[0017] Non-AP EHT STAs that do not have membership in a given R-TWT SP can still spontaneously access the R-TWT SP, but may not obtain the same priority level as R-TWT SP member STAs, especially if their transmissions are initiated or triggered by the R-TWT scheduling AP.

[0018] The R-TWT SP guarantees highest priority to scheduled RTA frames, but unscheduled RTA frames may be subject to significant delays because the R-TWT SP is scheduled to better serve STAs that are members of the R-TWT SP.

[0019] A non-AP EHT STA establishes membership for one or more R-TWT schedules with its associated EHT AP through the exchange of association, reassociation or TWT setup frames. A Stream Classification Service (SCS) descriptor specifies the traffic characteristics and Quality of Service (QoS) expectations of a traffic flow. The QoS expectations of the traffic include parameters such as Delay Bound and MSDU Lifetime, which specify the time limits of MSDUs belonging to an SCS stream.

[0020] The EDCA parameter set provides information required by the STA for correct operation of the QoS mechanisms and may be carried by beacon, association or reassociation response and probe response frames, which are typically exchanged within at least one beacon interval.

[0021] However, the EDCA parameter set element does not convey a parameter set that conforms to the MSDU lifetime and thus dynamically adapts to the needs of the RTA traffic.

[0022] In 802.11ax, an AP may advertise another set of EDCA parameters, named MU-EDCA parameters, that may be carried by beacon, association or reassociation response and probe response frames. A non-AP HE STA that receives a basic trigger frame containing a user information field addressed to the STA MUST update the CWmin[AC], CWmax[AC], AIFSN[AC] and MUEDCATimer[AC] state variables to the values ​​contained in dot11MUEDCATale for all ACs that successfully transmitted at least one QoS data frame in an HE TB PPDU in response to the trigger frame.

[0023] A non-AP STA SHOULD start counting down the MUEDCATimer[AC] at the end of an immediate acknowledgement if the transmitted HE TB PPDU contains at least one QoS data frame requiring immediate acknowledgment for that AC, and SHALL start counting down the MUEDCATimer[AC] at the end of an HE TB PPDU if the transmitted HE TB PPDU does not contain any QoS data frames requiring immediate acknowledgment for that AC.

[0024] When MUEDCATimer[AC] reaches zero, the non-AP HE STA must update its CWmin[AC], CWmax[AC] and AIFSN[AC] to the values ​​contained in the most recently received EDCA parameter set element sent by the AP.

[0025] 1.1. Current EDCA parameter set update (REVme_D5.0) The following provides an overview of the features of the EDCA parameter set update REVme_D5.0.

[0026] MLME-EDCAPARAMETERSET.request primitive

[0027] Function: This primitive requests that an EDCA parameter set frame be transmitted to a non-AP STA.

[0028] Primitive semantics:

[0029] PeerSTAAddress: A MAC address that specifies the address of the peer MAC entity with which to perform an EDCA parameter set update.

[0030] EDCAParameterSet: An EDCA parameter set element that specifies the service parameters of the updated EDCA parameter set.

[0031] When Generated: This primitive is generated by the SME to request that an EDCA parameter set frame be transmitted to a non-AP STA.

[0032] Effect of Reception: Upon receiving this primitive, the MLME constructs an EDCA parameter set frame, which the AP then attempts to transmit to associated non-AP STAs.

[0033] MLME-EDCAPARAMETERSET.indication primitive

[0034] Function: This primitive indicates that an EDCA parameter set frame has been received from the AP.

[0035] Primitive semantics:

[0036] PeerSTAAddress: A MAC address that specifies the address of the peer MAC entity with which to perform an EDCA parameter set update.

[0037] EDCAParameterSet: An EDCA parameter set element that specifies the service parameters of the updated EDCA parameter set.

[0038] Generated: This primitive is generated by the MLME when an EDCA parameter set frame is received.

[0039] Effect of Reception: Upon receiving this primitive, the SME shall act according to the procedures in 10.2.3.2 (HCF Contention-Based Channel Access (EDCA)) of draft P802.11REVmd_D5.0.

[0040] EDCA parameter set information may be carried by a beacon frame where the EDCA parameter set element is present if dot11QosOptionImplemented is true, dot11MeshActivated is false, and the QoS capabilities element is not present, otherwise it is not present (ax_D8.0).

[0041] EDCA parameter set information can also be carried by a (re)association response frame, in which case the EDCA parameter set element is present if dot11QosOptionImplemented is true, and is absent otherwise.

[0042] EDCA parameter set information can also be carried by a probe response frame, where the EDCA parameter set element is present if dot11QosOptionImplemented is true and dot11MeshActivated is false.

[0043] 1.2. Current EDCA Parameter Set Elements (REVmd_D5.0 and ax_D8.0) A typical (conventional) EDCA parameter set element that provides the information required by a STA for the correct operation of QoS mechanisms is shown in Figure 1. The Element ID field indicates the identity of the element, and the Length field indicates the number of octets in the element, excluding the Element ID and Length fields.

[0044] The QoS Info field includes an EDCA Parameter Set Update Count subfield that indicates when the EDCA parameters and, in the case of an HE BSS, the MU EDCA parameters, were changed (see 10.2.3.2 “HCF Contention-Based Channel Access (EDCA)” of draft P802.11ax_D8.0).

[0045] The QoS Information field is carried in the QoS Capabilities element which can be carried in beacon frames (if dot11QosOptionImplemented is true, dot11MeshActivated is false and the QoS Capabilities element is not present) or in (re)association frames (if dot11QosOptionImplemented is true).

[0046] The Update EDCA Information field is reserved for stations operating in the frequency range above GHz, called non-S1G-STAs, and FIG. 2 shows the EDCA Update Information field used for S1G STAs.

[0047] The formats of the AC_BE, AC_BK, AC_VI, and AC_VO parameter record fields are the same as those shown in FIG.

[0048] The format of the parameter record fields shown in FIG. 1 is detailed in FIG. 3 which shows the ACI / AIFSN, ECWmin / ECWmax and TXOP limit fields.

[0049] The ACI / AIFSN subfield of Figure 3 is detailed in Figure 4, which shows the following subfields: The AIFSN subfield indicates the number of slots after a SIFS that a STA will reserve before initiating a backoff call or transmission.

[0050] The ACM (admission control mandatory) subfield indicates that admission control is required for the AC.

[0051] The value of the AC Index (ACI) references the AC to which all the parameters in this record correspond.

[0052] Figure 5 shows details of the ECWmin / ECWmax fields shown in Figure 3. The ECWmin and ECWmax subfields encode the values ​​of CWmin and CWmax, respectively, in exponential format.

[0053] The TXOP Limit field is specified as an unsigned integer in units of 32 microseconds. The TXOP Limit field set to 0 has special meaning (see IEEE Draft 10.23.2.9 (TXOP Limit)).

[0054] 1.3. Current MU EDCA parameter set (ax_DX8.0) FIG. 6 illustrates the MU EDCA parameter sets that may be carried by association and reassociation response frames, where the parameters are optionally present if dot11HEOptionImplemented is true and dot11MUEDCAParametersActivated is true, and are not present otherwise.

[0055] The MU EDCA parameter set may also be carried by a Beacon frame, in which case the MU EDCA parameter set element is present if dot11HEOptionImplemented is true, dot11MeshActivated is false, dot11MUEDCAParametersActivated is true, and the QoS capabilities element is not present, and is not present otherwise.

[0056] The MU EDCA parameter set may also be carried by a Probe Response frame, in which case this element is present if dot11HEOptionImplemented is true and dot11MUEDCAParametersActivated is true, otherwise it is absent.

[0057] In an infrastructure BSS, the AP uses the MU EDCA parameter set element to control the use of EDCA by non-AP HE STAs after a particular UL MU HE TB PPDU transmission as specified in 26.2.7 (EDCA Operation with MU EDCA Parameters) of the draft P802.11ax_D8.0 specification. The Element ID field indicates the identity of the element, and the Length field indicates the number of octets in the element excluding the Element ID and Length fields. The Element ID Extension indicates the presence of an Element ID extension.

[0058] The format of the QoS Information field as transmitted by the AP is shown below in FIG. 8 (QoS Information Field).

[0059] The formats of the MU AC_BE, MU AC_BK, MU AC_VI, and MU AC_VO parameter record fields are identical and are defined in Figure 7 below.

[0060] FIG. 7 shows the MU AC parameter record fields with the fields ACI / AIFSN, ECWmin / ECWmax and MU EDCA timers.

[0061] The format of the ACI / AIFSN fields and the encoding of its subfields in Figure 7 are specified in 9.4.2.29 (EDCA Parameter Set Element) of the draft P802.11ax_D8.0 specification, except that a value of 0 in the AIFSN field indicates that EDCA is disabled for the period specified by the MU EDCA Timer of the corresponding AC. The format of the ECWmin / ECWmax fields is specified in Figure 5. The MU EDCA Timer field indicates the period in eight time units (TUs) for which the HE STA will use the MU EDCA parameters of the corresponding AC, except that the value zero ("0") is reserved.

[0062] Figure 8 shows the QoS Information field with an EDCA Parameter Set Update Count subfield that indicates when the EDCA parameters and, in the case of an HE BSS, the MU EDCA parameters have changed. This field also indicates Q-Ack, Queue Request, and TXOP Request.

[0063] 1.3. Current SCS and Response Process (REVmd_D5.0) Figure 9 illustrates the SCS request and response process outlined below.

[0064] MLME-SCS.request primitive:

[0065] Function: Requests the transmission of an SCS request frame to the AP.

[0066] Primitive semantics:

[0067] PeerSTAAddress: Specifies the address of the peer MAC entity with which the SCS process is running.

[0068] DialogToken: Identifies SCS request and response transactions.

[0069] SCSRequest: An SCS Descriptor element as shown in FIG. 10, which specifies the frame classifier and priority of the requested SCS stream.

[0070] VendorSpecificInfo: A series of elements.

[0071] Generated: This primitive is generated by the SME to request that an SCS request frame be sent to the AP associated with the STA.

[0072] Effect of reception: Upon receiving this primitive, the MLME constructs an SCS request frame, which the STA then attempts to transmit to the associated AP.

[0073] MLME-SCS.indication primitive:

[0074] Function: Indicates that an SCS request frame was received from a non-AP STA.

[0075] Primitive semantics:

[0076] PeerSTAAddress: The address of the non-AP STA MAC entity from which the SCS request frame originated.

[0077] DialogToken: Identifies SCS request and response transactions.

[0078] SCSRequest: An SCS descriptor element that specifies the frame classifier and priority of the requested SCS stream.

[0079] VendorSpecificInfo: A series of elements.

[0080] Generated: Generated by the MLME when an SCS request frame is received.

[0081] Effect of Reception: Upon receiving this primitive, the SME shall act in accordance with 11.25.2 (SCS Procedures) of the draft P802.11REVmd_D5.0 specification.

[0082] 1.4. Current SCS Request and Response Process (REVmd_D5.0) Draft P802.11REVmd_D5.0 Specification

[0083] MLME-SCS.response primitive:

[0084] Function: Generated in response to an MLME-SCS.indication primitive requesting that an SCS response frame be sent to a non-AP STA.

[0085] Primitive semantics:

[0086] PeerSTAAddress: The address of the non-AP STA MAC entity from which the SCS request frame originated.

[0087] DialogToken: Identifies SCS request and response transactions.

[0088] SCSID: Identifies the SCS stream being classified.

[0089] Status: Indicates the result of the response for the requested SCSID.

[0090] SCS Descriptor: An SCS Descriptor element that specifies the frame classifier and priority of the responded SCS stream.

[0091] VendorSpecificInfo: A series of elements.

[0092] Generated: Generated by the SME in response to an MLME-SCS.indication primitive requesting that an SCS response frame be sent to a non-AP STA.

[0093] Effect of Reception: Upon receiving this primitive, the MLME constructs an SCS Response frame. The STA then attempts to transmit this frame to the non-AP STA indicated by the PeerSTAAddress parameter.

[0094] MLME-SCS.confirm primitive:

[0095] Function: Reports the result of an SCS procedure.

[0096] Primitive semantics:

[0097] PeerSTAAddress: Specifies the address of the peer MAC entity with which the SCS process is running.

[0098] DialogToken: Provides identification of SCS request and response transactions.

[0099] SCSID: Identifies the SCS stream being classified.

[0100] Status: Indicates the result of the response for the requested SCSID.

[0101] SCS Descriptor: An SCS Descriptor element that specifies the frame classifier and priority of an identified SCS stream.

[0102] VendorSpecificInfo: A series of elements.

[0103] Generated: This primitive is generated by the MLME as a result of the MLME-SCS.request primitive to indicate the result of the request. This primitive is generated when the STA receives an SCS response frame from the AP.

[0104] Effect of Reception: Upon receiving this primitive, the SME shall act according to the procedures in 11.25.2 (SCS Procedures) of the draft P802.11REVmd_D5.0 specification.

[0105] FIG. 10 shows an SCS descriptor element having the subfields: element ID, length, SCSID, request type, priority element within access category (optional), TCLAS element (0 or more optional TCLAS elements), TCLAS processing element (optional), optional QoS characteristic element, and optional subelements.

[0106] 1.5. Current SCS Descriptor Element (be_D1.31). 11 shows the QoS characteristic element field, which contains zero or one QoS characteristic element describing the traffic characteristics and QoS expectations of the traffic flows belonging to this SCS stream. The QoS characteristic element has the following subfields:

[0107] The Minimum Service Interval field specifies the minimum interval, in microseconds, between the start of two consecutive service periods.

[0108] The Maximum Service Interval field specifies the maximum interval, in microseconds, between the start of two consecutive service periods.

[0109] The Minimum Data Rate field specifies the minimum data rate, in kilobits per second, specified in the MAC SAP for transmitting MSDUs or A-MSDUs belonging to the traffic flow described by this element.

[0110] The Delay Bound field specifies the maximum time in microseconds allowed for the transmission of a MAC Service Data Unit (MSDU) or an Aggregated MSDU (A-MSDU) belonging to the traffic flow described by this element, measured between the time the MSDU or the first of the MSDUs constituting an Aggregated MSDU arrives at the local MAC sublayer from the local MAC Service Access Point (SAP), which is the interface between the MAC layer and higher layers, and the time of completion of successful transmission or retransmission of the MSDU or A-MSDU to its destination. The completion time of the MSDU or A-MSDU transmission includes the transmission time of the associated acknowledgement frame, if any.

[0111] The Maximum MSDU Size field specifies the maximum size, in octets, of an MSDU or A MSDU that may belong to the traffic flow described by this element.

[0112] The Service Start Time field specifies the time, in microseconds, when the first service period begins.

[0113] The Mean Data Rate field indicates the mean data rate specified in the MAC SAP for transmitting MSDUs or A-MSDUs belonging to the traffic flows within this element, in kilobits per second (kbps).

[0114] The Burst Size field specifies the largest burst, in octets, of MSDUs or A-MSDUs belonging to a traffic flow arriving at the MAC SAP at its peak data rate.

[0115] The MSDU Lifetime field contains an unsigned integer that specifies the maximum time, in milliseconds, since an MSDU arrived at the MAC Data Service Interface, after which the MSDU is no longer useful and may be discarded by the MSDU sender: (a) The time specified in this field is greater than or equal to the time specified in the Delay Bound field, if present.

[0116] The MSDU Delivery Ratio field specifies the MSDU loss requirement.

[0117] The MSDU Count Exponent field contains an unsigned integer that specifies the exponent from which the number of incoming MSDUs used to calculate the MSDU delivery ratio is taken.

[0118] The Medium Time field contains an unsigned integer that specifies the medium time requested by the STA as the average medium time required per second.

[0119] Figure 12 shows the subfields of the control information field shown in Figure 11. The subfields of the control information field will be described below.

[0120] The Direction subfield specifies the direction of the data described by this element. The Traffic Identifier (TID) subfield contains the TID value of the data frame described by this element. The User Priority subfield contains the user priority value (0-7) of the data frame described by this element. The Presence Bitmap of Additional Parameters subfield contains a bitmap, where the i-th entry of the bitmap is set to "1" if the i-th field starting from the Maximum MSDU Size field is present in this element. (e) The LinkID subfield contains the link identifier for the next direct link transmission.

[0121] 2. Problem Statement EDCA parameters mainly capture the priority of Buffered Units (BUs), but do not capture the dynamic changes of MSDU lifetime of buffered RTAs.

[0122] The EDCA parameter set elements that provide the information the STA needs for correct operation of the QoS mechanisms are carried by beacon frames, probe response frames, and / or association / reassociation response frames that may require more than one beacon interval to update and therefore cannot capture the necessary dynamics of the MSDU lifetime of buffered RTAs.

[0123] The AP uses the MU EDCA parameter set elements to control EDCA usage by non-AP HE STAs after a particular UL MU HE TB PPDU transmission. However, the MU EDCA parameter set also cannot configure EDCA corresponding to the dynamic RTA MSDU lifetime.

[0124] The QoS characteristic element carried by the SCS Descriptor element includes an MSDU Lifetime field, however, due to the long interval between exchanges of SCS Request / Response frames, the MSDU Lifetime field is not dynamically updated.

[0125] Therefore, there is no QoS mechanism in operation that can capture the dynamic changes in the MSDU lifetime of the buffered RTAs.

[0126] The AP may not be able to predict the emergence of new buffered RTA traffic from non-AP STAs, and therefore may not be able to capture the dynamic needs of RTA transmission.

[0127] 3. Contribution of this Disclosure In this disclosure, new RTA Adaptive EDCA rules are described for non-AP STAs to send RTA packets in R-TWT SP. A new RTA Adaptive EDCA Parameter Set element and a new RTA Adapt EDCA Reset frame are created. The application of the new RTA Adaptive EDCA can be initiated by (a) receiving a trigger from an associated AP or (b) pre-configuring the non-AP STA to start automatically when the R-TWT SP starts.

[0128] A non-AP STA, as an R-TWT member or non-member of the current R-TWT SP, can switch from using normal EDCA in the R-TWT SP to using the new RTA adaptive EDCA. For example, this can take the following form:

[0129] (a) STAs applying the RTA adaptive EDCA rule can dynamically adjust the RTA adaptive EDCA parameters corresponding to the (AC, RTA remaining lifetime threshold) level of the buffered MSDUs. (b) For the same (AC, RTA remaining lifetime threshold) level, R-TWT member STAs can have a higher RTA adaptive EDCA priority than non-R-TWT member STAs with the same (AC, RTA lifetime) level. (c) STAs applying the RTA adaptive EDCA rule must switch from using the RTA adaptive EDCA parameters to using the normal EDCA parameters at the end of the R-TWT SP.

[0130] The duration of application of the new RTA adaptive EDCA rule is adjustable and can, for example, (a) last until the end of the current R-TWT SP, or (b) be maintained for a period of time within the current R-TWT SP.

[0131] The AP may prevent the STA from using the new RTA adaptive EDCA at any time within the R-TWT SP.

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

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

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

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

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

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

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

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

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

[0141] 15 illustrates an example embodiment 70 of a network topology that will be used to aid in the following discussion, although it should be understood that the disclosure is in no way limited to this example topology, as the protocol may be utilized in communications between WLAN STAs and MLDs of any desired topology.

[0142] In this example, assume there is one AP (AP1) 72 on the network and two other STAs shown as non-AP STA1 74 and non-AP STA2 76. The AP, STA1, and STA2 are within communication range of each other. STA1 and STA2 are EHT STAs that understand R-TWT and are associated with AP1. AP1 has the same or different scheduled R-TWT SPs for STA1 and STA2. STA1 and STA2 can utilize adaptive EDCA for RTA traffic during the scheduled R-TWT SPs.

[0143] Process Flow 16 illustrates an example embodiment 110 of adaptive EDCA for an AP. In check 112, the AP determines whether it has entered or is otherwise within an R-TWT SP and needs to initiate RTA adaptive EDCA. If the condition is not met, the process ends.

[0144] If the condition is met, the AP transmits a trigger frame to inform the associated STAs to switch their EDCA mode to adaptive EDCA parameters in block 114. The AP then receives (116) trigger-based (TB) PPDU(s) and responds (118) with BA / Ack(es).

[0145] At check 120, it is determined whether the AP needs to reset the RTA adaptive EDCA parameters for certain or all (e.g., AC, RTA lifetime threshold) levels. If no changes are needed, the AP returns to check 112. If changes are needed, the AP transmits (122) an RTA adaptive reset frame and the process ends after receiving (124) the BA / Ack(es).

[0146] 17-20 illustrate an example embodiment 210 of adaptive EDCA operation for a non-AP STA. At check 212, the non-AP STA determines if it is in or within an R-TWT SP. If not, at block 244 of FIG. 20, the non-AP STA uses normal EDCA and the process ends.

[0147] If an R-TWT SP has been entered, check 214 of Figure 17 determines whether RTA adaptive EDCA is enabled through pre-configuration at the start of the R-TWT SP. If the condition is met, in block 222 the non-AP STA switches to using RTA adaptive EDCA and execution reaches block 224 of Figure 18, described below.

[0148] On the other hand, if the condition of check 214 is not met, then in check 216 it is determined whether the non-AP STA has received a trigger frame (TF) that initiates the application of RTA-adaptive EDCA. If this condition is not met, then the non-AP STA uses normal EDCA and the process ends in block 244 of FIG. 20. On the other hand, if the condition of check 216 is met, then in block 218 the non-AP STA responds with a TB-PPDU (218) and after receiving the BA / Ack (220), it reaches block 222 and switches to RTA-adaptive EDCA and execution proceeds to block 224 of FIG. 18.

[0149] In check 224, the non-AP STA determines whether the RTA adaptive EDCA is valid until the end of the current R-TWT SP. If the condition is met, in block 228, the non-AP STA uses the RTA adaptive EDCA parameters at the specified or all (AC, RTA Lifetime Threshold) levels until the end of the current R-TWT SP, after which execution proceeds to check 230 of FIG.

[0150] On the other hand, if the conditions of check 224 are not met, then in block 226, the non-AP STA uses only the RTA adaptive EDCA parameters of the particular or all (AC, RTA Lifetime Threshold) levels until the RTA adaptive EDCA timer for the RTA adaptive EDCA parameters reaches zero, at which point execution also proceeds to check 230 of FIG. 19.

[0151] At check 230 of Figure 19, the non-AP STA determines whether it has received an RTA adaptive EDCA reset frame from its associated AP. If a reset has not been received, execution proceeds to check 236 of Figure 20.

[0152] Otherwise, since a reset frame has been received, the non-AP STA responds with a BA / Ack to the AP (232) and resets the RTA adaptive EDCA parameters for certain or all (AC, RTA Lifetime Threshold) levels, and execution proceeds to check 236 of FIG. 20.

[0153] In check 236 of FIG. 20, the non-AP STA determines whether it has received a trigger frame that initiates the application of RTA-adaptive EDCA. If the condition is not met, the process is complete. Otherwise, the non-AP STA responds with a TB-PPDU in block 238, receives a BA / Ack (240), and determines whether it is within the R-TWT SP in check 242. If it is not within the R-TWT SP, the non-AP STA switches to using normal EDCA in block 244 and the process is complete. However, if the condition of being within the R-TWT SP is met, the non-AP STA returns to block 226 of FIG. 18 and uses the RTA-adaptive EDCA parameters as described above.

[0154] 5. Data Fields 5.1.EDCA Parameter Set Data Fields 21 illustrates an example embodiment 310 of an RTA Adaptive EDCA Parameter Set element with the following fields: Element ID field indicates the identity of the element. Length field indicates the number of octets in the element excluding the Element ID and Length fields. Element ID Extension indicates the presence of an Element ID extension.

[0155] The Quality of Service (QoS) Information field, if sent from the AP, may be the same as the QoS Information field shown in Figure 8. The EDCA Parameter Set Update Count subfield in Figure 8 indicates that the RTA adaptive EDCA parameters have changed if the EDCA parameters are for an EHT BSS.

[0156] The Applied Group subfield of FIG. 21 indicates the group of non-AP STAs, such as R-TWT member STAs and non-R-TWT member STAs, that should use the RTA adaptive EDCA parameters defined in this element.

[0157] A first state (e.g., "1") of the Applicability Group subfield indicates that the RTA adaptive EDCA parameters apply to R-TWT member STAs, and a second state (e.g., "0") of this value indicates that the RTA adaptive EDCA parameters also apply to non-R-TWT member STAs.

[0158] Figure 21 shows various numbers of exemplary RTA adaptive parameter record lists for different access categories AC_BE, AC_BK, AC_VI and AC_VO, and their subfields are shown in Figure 22. The AC_BE, AC_BK, AC_VI and AC_VO parameter record list fields are identical and each of them can contain multiple RTA adaptive AC parameter record fields.

[0159] As introduced in Section 5.2 below, the RTA adaptive EDCA parameter set element of FIG. 21 may be carried by beacon frames, association / reassociation response frames, probe response frames, and RTA adaptive EDCA reset frames.

[0160] Non-AP EHT STAs should switch to using the parameter set defined in the RTA Adaptive EDCA Parameter Set element by receiving a signal / trigger from the associated AP or can automatically start at the start of the R-TWT SP based on pre-configuration.

[0161] Different application groups, such as R-TWT member STAs and non-R-TWT member STAs, may have different RTA adaptive EDCA parameters for the same (AC, RTA remaining lifetime threshold) level defined in this element.

[0162] Non-AP EHT STAs shall use the corresponding EDCA parameter set indicated in the most recently received RTA Adaptive EDCA Parameter Set element according to both the AC and remaining MSDU lifetime of the arriving RTA traffic.

[0163] FIG. 22 illustrates an example embodiment 330 of an RTA adaptive AC parameters record with the following fields:

[0164] The ACI Lifetime / AIFSN field is described below with reference to FIG.

[0165] The format of the ECWmin / ECWmax field is defined in Figure 5. The ECWmin and ECWmax subfields encode the CWmin and CWmax values, respectively, of the corresponding (AC, RTA-LIFE) levels, where these levels are provided in exponential form.

[0166] The RTA Adaptive EDCA TXOP Limit field indicates the TXOP limit of the corresponding (AC, RTA Lifetime) level.

[0167] The RTA Adaptive EDCA Timer field indicates the duration for which the EHT STA will use the RTA Adaptive EDCA parameters of the corresponding (AC, RTA Lifetime) level, except that a second state (e.g., "0") indicates that RTA Adaptive EDCA is valid until the end of the current R-TWT SP. When a non-AP STA's RTA Adaptive EDCA timer (e.g., a non-zero value of an RTA Adaptive EDCA parameter set element) reaches a terminal count (e.g., "0"), the STA shall switch to using CWmin[AC], CWmax[AC], and AIFSN[AC] according to the values ​​contained in the most recently received normal EDCA parameter set elements sent from the associated AP, either by counting towards the terminal count or due to a reset after receiving an RTA Adaptive EDCA Reset frame introduced in Section 5.2 below.

[0168] Figure 23 illustrates an example embodiment 350 of the ACI Lifetime / AIFSN subfield shown in Figure 22. In Figure 23, the encoding of subfields AIFSN, ACM, and ACI is the same as that defined in Figure 4, with the following exceptions: (a) A first state (e.g., "0") of the AIFSN field indicates that normal EDCA is disabled for a period specified by the RTA adaptive EDCA timer for the corresponding AC. (b) The RTA Lifetime subfield indicates the remaining MSDU expiration threshold for RTA MSDUs for the corresponding AC that uses RTA adaptive EDCA.

[0169] Note that each AC can be configured with different (AC, RTA life) pairs such as (AC2, most urgent), (AC2, medium urgent), and (AC2, less urgent) or the like.

[0170] The remaining MSDU expiration threshold level is application dependent and in at least one embodiment or mode is pre-configured to be understood by all very high throughput (EHT) devices supporting this RTA adaptive EDCA feature. (a) For example, different applications may have different tolerances for communication latency and may evaluate the urgency of the RTA MSDU remaining expiration level differently. (b) For example, the MSDU expiration level of a VR game may be relatively more stringent than a video stream, and thus the EDCA of the (AC2, most urgent) pair of the VR game may be prioritized over the EDCA of the (AC, most urgent) pair of the video stream. (c) The exact definition of the RTA lifetime threshold levels, such as most urgent, moderately urgent, and less urgent in a VR game or video stream, is application dependent.

[0171] 5.2.RTA Adaptive EDCA Reset Frame FIG. 24 illustrates an example embodiment 370 of an RTA Adaptive EDCA Reset frame generated by an associated AP to instruct a non-AP STA to reset its use of the RTA Adaptive EDCA parameter set and to use the most recently received EDCA parameter set.

[0172] When a non-AP STA receives an RTA adaptive EDCA reset frame, it resets its RTA adaptive EDCA timer to its final state (e.g., "0") and the STA switches from using CWmin[AC, RTA remaining lifetime threshold], CWmax[AC, RTA remaining lifetime threshold] and AIFSN[AC, RTA remaining lifetime threshold] to using CWmin[AC], CWmax[AC] and AIFSN[AC] in accordance with the values ​​contained in the most recently received EDCA parameter set element sent by the associated AP.

[0173] The reset caused by the RTA adaptive EDCA reset frame remains in effect until the end of the current R-TWT X SP, unless the STA receives a trigger frame indicating that it should switch to using RTA adaptive EDCA.

[0174] The RTA adaptive EDCA reset frame is an action frame and its corresponding Action field is as follows:

[0175] The Category field contains a value that indicates the category of the action frame.

[0176] The Protected EHT Action field in the octet immediately following the Category field distinguishes the format of the Protected EHT Action frame.

[0177] The RTA adaptive EDCA control field is described below with reference to FIG.

[0178] FIG. 25 illustrates an example embodiment 390 of an RTA adaptive EDCA control field having the following subfields:

[0179] The Reset All subfield contains one bit indicating whether the reset is for all (AC, RTA lifetime threshold) level EDCA parameters. The first state (e.g., "1") indicates that the reset applies to all EDCA parameters, and the second state (e.g., "0") indicates that none apply to all. When the Reset All subfield is set as the first state, the Affected ACs subfield and the Affected RTA remaining lifetime threshold Levels subfields for AC_VO, AC_VI, AC_BK, and AC_BE are not used.

[0180] The Affected ACs subfield and Affected AC_VO, AC_VI, AC_BK, AC_BE RTA Life threshold Levels subfields contain independent bitmaps indicating the ACs and RTA life levels of different ACs for which RTA adaptive EDCA parameters should be reset upon receipt of an affected STA's RTA adaptive EDCA Reset frame. Each bit of the bitmap contained in the Affected ACs subfield corresponds to one AC, where bit B0 is mapped to AC_BK, bit B1 is mapped to AC_BE, bit B2 is mapped to AC_VI, and bit B3 is mapped to AC_VO. Each bit of the bitmap contained in the Affected RTA Life Levels subfields of AC_VO, AC_VI, AC_BK, AC_BE corresponds to one remaining life expiration level. The remaining life expiration threshold levels are application dependent and in at least one embodiment / mode / option are pre-configured to be recognized (understood) by all EHT devices supporting this feature.

[0181] A value set to a first state (e.g., "1") in a bit position corresponding to a given AC and a value set to a first state (e.g., "1") in a bit position corresponding to a given RTA lifetime level indicates that the non-AP STA should switch the corresponding EDCA from using the RTA ADPT EDCA parameter set to using the normal EDCA parameter set because the corresponding RTA adaptive EDCA timer has reached its terminal count (e.g., "0"), otherwise the value of the bit is set to a second state (e.g., "0").

[0182] 6. Example of operation 6.1. Triggerable RTA Adaptive EDCA 26 shows a first example embodiment 410 illustrating triggerable RTA adaptive EDCA illustrating two R-TWT SPs identified as ID "X", where STA1 413 is a member of the R-TWT in this example. Unless otherwise stated in the context, the RTA traffic in these examples is of the same highest AC.

[0183] In the first R-TWT X SP 414, the AP 412 acquires channel access after a backoff (BO) 418 and transmits a trigger frame (TF) 420 indicating that the addressed recipient should use RTA adaptive EDCA parameters. In this case, the trigger indicates that the addressed recipient(s) should use an RTA adaptive EDCA timer that is short enough for one or more TXOP periods in the current R-TWT SP.

[0184] STA1 receives a trigger addressed to it and responds with a TB-PPDU 422 , which the associated AP 412 acknowledges with an Ack / BA frame 424 .

[0185] After this, STA1 switches to the RTA adaptive parameter set in a short period based on the RTA adaptive EDCA timer field and contends for access to transmit some new buffered RTA MPDUs (428), and STA1's RTA traffic has the highest priority AC and the more refined lifetime-based priority of the same AC. This priority STA1 with urgent RTA traffic acquires the channel more easily. After acquiring the channel access right, STA1 transmits urgent RTA PPDU 430 to the associated AP and receives Ack / BA 432 from the AP in response.

[0186] After STA1 finishes the TXOP acquired using the RTA adaptive EDCA parameters, it should switch to using the normal EDCA parameter set to contend for channel access when the (short) RTA adaptive EDCA timer reaches zero. The figure shows, as an example, that both the AP and STA1 are contending for the channel (434, 436).

[0187] In the second R-TWT X SP 416, the AP acquires channel access after BO 438 and transmits a trigger frame 440 indicating triggerable RTA adaptive EDCA with long RTA and adaptive EDCA timers directed to the member receiver(s) to update the RTA adaptive EDCA parameters. The long RTA adaptive EDCA timer should last until the end of the R-TWT X SP.

[0188] STA1 receives the basic trigger containing a user information field addressed to it and responds with a trigger-based (TB) PPDU, shown here as TB-PPDU 442. The associated AP acknowledges this TB-PPDU with an Ack / BA frame 444.

[0189] STA1 then switches to the RTA adaptive parameter set 446 when transmitting a new buffered RTA MPDU 450 and contends 448 for channel access and finds that the AP acknowledges 452 the RTA MPDU 450. STA1 then contends 454 within this same long RTA period 446 to gain channel access to transmit a PPDU 456 and receives an Ack / BA 458 from the AP during this current R-TWT X SP.

[0190] STA1 then switches to normal EDCA parameters after completion of the current R-TWT x SP (462) and contends for channel access rights (460).

[0191] 6.2. Self-initiated RTA Adaptive EDCA at the start of R-TWT SP 27 illustrates an example embodiment 510 of self-initiated RTA adaptive EDCA at the beginning of an R-TWT SP. Similar to the previous figure, communication between an AP 412 and a non-AP STA1 413 during two consecutive R-TWT SPs (e.g., R-TWT X SPs) 414 and 416 is shown, where STA1 has R-TWT membership.

[0192] The R-TWT X member STA1 automatically switches to use the RTA adaptive EDCA parameter set to contend for channel access rights (514, 528) upon initiation of both the first and second R-TWT X SPs. Unlike the previous illustrated example, in this case, it is assumed that the EDCA parameter set has been set through pre-configuration.

[0193] In the first R-TWT X SP 414, the RTA adaptive EDCA parameters are enabled for a certain short period 512, such as 1TXOP. STA1 adjusts the EDCA parameters according to the (AC, RTA remaining lifetime threshold) level, terminates the BO at the earliest position to gain channel access right, sends RTA PPDU 516 to the associated AP, and receives Ack / BA 518 as a response from the AP.

[0194] The RTA adaptive EDCA parameters are enabled for a short period of time after which the RTA adaptive EDCA timer reaches zero. This causes STA1 to switch to using the normal EDCA parameter set before the end of the current R-TWT SP (519). STA1 should use the normal EDCA parameter set in the current R-TWT X SP unless it receives a trigger frame from its associated AP indicating it can switch to using the RTA adaptive EDCA parameter set. Otherwise, as shown, STA1 switches to the normal EDCA parameters to contend for channel access rights when the current R-TWT X SP ends.

[0195] The AP contends for channel access (520) and sends an adaptive EDCA triggerable RTA (522), to which STA1 responds with a TB-PPDU 524 and the AP responds with an Ack / BA 526. Once this is complete, STA1 switches (523) to the RTA adaptive EDCA parameter set and continues operation until the end of this first R-TWT X SP 414, at which point STA1 switches (525) to the regular EDCA parameter set.

[0196] The figure then shows a second R-TWT X SP 416, where the RTA adaptive EDCA parameters are enabled until the end of the current R-TWT X SP (527). STA1 switches to the adaptive EDCA parameter set (529), adjusts the EDCA parameters according to the (AC, RTA remaining lifetime threshold) level, ends the BO 528 in the earliest position, acquires channel access right, sends RTA PPDU 530 to the associated AP, and receives Ack / BA 532 in response from the AP.

[0197] The AP executes BO 534 at some point in the current R-TWT x SP, acquires channel access right, and transmits a trigger frame 536 addressed to STA1, which does not include STA1's RTA adaptive EDCA information.

[0198] STA1 receives a basic trigger frame that does not contain RTA-adaptive EDCA information and therefore should continue to use the RTA-adaptive EDCA parameter set for channel access. STA1 can be seen to transmit TB-PPDU 538 and receive Ack / BA 540 from the AP. STA1 then contends 542 for the channel, transmits PPDU 544, and receives Ack / BA 546 from the AP.

[0199] STA1 switches back to normal EDCA parameters to contend for channel access rights at the end of the current R-TWT x SP (548).

[0200] 6.3. Resetting All RTA-Adaptive EDCA 28 illustrates an example embodiment 610 of resetting all RTA adaptive EDCA. Similar to the previous figure, communication between an AP 412 and a non-AP STA1 413 in two consecutive R-TWT SPs (e.g., R-TWT X SPs) 414 and 416 is shown, where STA1 has R-TWT membership. This figure shows two R-TWT SPs identified as ID "X", where STA1 has R-TWT membership.

[0201] At the start of R-TWT X SP 414 and 416, R-TWT X member STA1 automatically switches (613, 631) to use RTA adaptive EDCA parameters to contend for channel access rights (614 and 634) until the end of the current R-TWT SP, this adaptive EDCA being obtained through pre-configuration. Unless otherwise stated in the context, it is assumed that the RTA traffic in this example is of the same highest AC as in the previous examples.

[0202] In the first R-TWT X SP414, STA1 adjusts EDCA parameters according to the (AC, RTA remaining lifetime threshold) level, then contends (614), gains channel access right and sends a Transmit (RTA) PPDU616 to the associated AP, and the AP sends an Ack / BA618 in response.

[0203] The AP decides to terminate the application of RTA adaptive EDCA for all receivers at some point in the current R-TWT x SP, and the AP contends (620) for and obtains channel access to transmit an RTA adaptive EDCA reset frame 622 that resets (625) the EDCA parameters back to normal EDCA parameters for all (AC, RTA remaining lifetime threshold) levels and all receivers.

[0204] STA1 acknowledges (Ack) the reset after receiving the RTA adaptive EDCA reset frame from its associated AP (624) and switches to using normal EDCA parameters to contend for channel access rights. STA1 then contends using the normal parameters to obtain channel access rights at BO 626 and sends a PPDU 628, to which the AP responds with an Ack / BA 630, and the R-TWT X SP 414 is found to be finished.

[0205] In the second R-TWT X SP416, STA1 switches to the adaptive parameter set (631), adjusts its EDCA parameters according to the (AC, RTA remaining lifetime threshold) level, contends for channel access rights (634), wins channel access rights, and sends an (RTA)PPDU636 to the associated AP, which responds with an Ack / BA638.

[0206] The AP contends 640 for channel access at some point in the current R-TWT X SP 416, wins channel access, and transmits a trigger frame 642 indicating that the addressed recipient should update its RTA adaptive EDCA parameters for a short period of time. STA1 can be seen receiving the trigger frame addressed to it and responding with a TB-PPDU 644, which the associated AP acknowledges with an Ack / BA frame 646.

[0207] STA1 then contends 648 for and acquires a channel to transmit the newly buffered RTA MPDU using the RTA adaptive EDCA parameters to contend for channel access within the updated RTA adaptive EDCA timer period 653 shortly before the short updated RTA adaptive EDCA timer expires. STA1 obtains channel access before the RTA adaptive EDCA timer reaches zero, transmits a PPDU 650 to its associated AP, and receives an Ack / BA 652 from the AP.

[0208] After STA1 finishes this TXOP, the (short) RTA adaptive EDCA timer reaches 0 and STA1 switches to using the normal EDCA parameter set to contend for channel access rights.

[0209] STA1 should continue to use normal EDCA parameters for the remainder of the current R-TWT X SP unless it receives a trigger frame indicating that it should switch to and use RTA adaptive EDCA.

[0210] 6.4. Selected (AC, RTA Lifetime) RTA Adaptive EDCA Reset An example embodiment 710 for resetting a particular (AC, RTA Lifetime) RTA adaptive EDCA is shown in Figure 29. The figure shows communication within an R-TWT SP 414 identified as ID "X", where STA1 413 and STA2 415 have R-TWT membership.

[0211] At the start of the R-TWT X SP, R-TWT X members STA1 and STA2 automatically switch (715) to use the illustrated RTA adaptive EDCA parameter set over the R-TWT X SP 414 as obtained through pre-configuration. STA1 and STA2 contend (712, 714) for channel access rights. Unless otherwise stated in the context, it is assumed that the RTA traffic in this example is of the same highest AC.

[0212] During the first UL PPDU transmission sequence, STA1 has a medium urgent RTA MSDU buffered and STA2 has some of the most urgent RTA MSDUs buffered. Therefore, STA2 has higher priority channel access EDCA, but expires its BO counter later than STA1 due to the randomness of the selected contention window. STA1 gains channel access and transmits a medium urgent RTA PPDU 716 to its associated AP, which responds with an Ack / BA 718.

[0213] Here, it is shown that the AP resets the RTA adaptive EDCA for the highest AC moderately urgent RTA at some point, such as when it detects an unexpectedly long delay of the most urgent RTA from STA2. In this case, the AP performs a backoff 720 to contend for channel access rights and transmits an RTA adaptive EDCA reset frame 722 to reset the (highest AC, moderately urgent RTA) level adaptive EDCA to the highest AC normal EDCA. In response, the STA maintains the use of the RTA adaptive EDCA parameters for the other (AC, RTA Lifetime) levels of RTA traffic.

[0214] Any STA that receives an RTA Adaptive EDCA Reset frame from its associated AP should respond, as can be seen in this example by STA1 sending BA 724. Any STA that receives an RTA Adaptive EDCA Reset frame from its associated AP (e.g., STA1 in this example) will reset its RTA Adaptive EDCA at the specified (AC, RTA Lifetime) level to normal EDCA for that AC (727).

[0215] During the second UL PPDU transmission sequence, STA1 is illustrated as having some moderately urgent RTA MSDUs buffered content and contends for channel access rights using regular EDCA (726). STA2 has some of the most urgent RTA MSDUs buffered and contends for channel access rights using RTA adaptive EDCA parameters corresponding to its (AC, RTA remaining lifetime threshold) level (728).

[0216] STA2 completes BO 728 and obtains channel access rights more easily than STA1. STA2 transmits the most urgent UL RTA PPDU 729 to the associated AP and receives an Ack / BA 730 in response.

[0217] The AP may restore the RTA adaptive EDCA parameters of the moderately urgent RTA of the highest AC at some point, such as when it detects that the problem of the unexpectedly long delay of the most urgent RTA has been resolved.

[0218] In this example, the AP contends for channel access (731), wins channel access, and transmits a trigger frame 732 indicating that the addressed recipient should again use the RTA adaptive EDCA parameters.

[0219] It can be seen that STA1 and STA2 receive the trigger frame addressed to them and respond with TB-PPDUs 734 and 736 , which the associated AP acknowledges with a BA frame 738 .

[0220] In the final UL PPDU transmission sequence shown, STA1 has some moderately urgent RTA MSDUs buffered and STA2 has some less urgent or non-urgent RTA MSDUs buffered. STA1 switches (743) to the RTA adaptive EDCA parameter set. Both stations contend (740, 742) for the channel. STA1 completes BO 740 before STA2, gains channel access, and transmits a medium urgent RTA PPDU 744 to its associated AP, which responds with an Ack / BA 746.

[0221] Both STA1 and STA2 switch back to normal EDCA parameters upon completion of R-TWT X SP414 in order to subsequently contend for channel access rights.

[0222] 6.5. RTA Adaptive EDCA for End-of-Life RTAs Figure 30 illustrates an example embodiment 810 of RTA adaptive EDCA for end-of-life RTAs. This figure also shows a single R-TWT SP identified as ID "X" 414, with R-TWT memberships of STA1 413 and STA2 415. Unless otherwise stated in this context, it is assumed that the RTA traffic in this example is of the same highest AC.

[0223] At the start of the R-TWT X SP, R-TWT members STA1 and STA2 automatically switch (813) to use the RTA adaptive EDCA parameters, assumed here to be achieved by pre-configuration 811, for the R-TWT members to contend for channel access rights until the end of the current R-TWT SP.

[0224] STA1 and STA2 need to contend for channel access to transmit the newly buffered RTA MPDU, and contend for channel access using the RTA adaptive EDCA parameters (812, 814).

[0225] The first UL PPDU transmission sequence 816 is initiated by STA1 since STA1 has a higher RTA remaining lifetime based priority than STA2 with the same (highest) AC. This prioritized STA1 with urgent RTA traffic can acquire the channel easier (faster). STA1 transmits a PPDU 816 to the associated AP and receives an Ack / BA 818 from the AP.

[0226] At this point, the second UL PPDU transmission sequence is initiated by STA2 since STA2 has a higher RTA remaining lifetime based priority than STA1 in the same (highest) AC. Again, STA1 and STA2 both contend for channel access rights (820, 822). The prioritized STA2 with its urgent RTA traffic gains channel access rights faster, sending a PPDU 824 to its associated AP and receiving an Ack / BA 826 from the AP.

[0227] STA1 and STA2 are constrained at the end of the R-TWT X SP 414 to stop using the RTA adaptive EDCA parameters when the current R-TWT X SP ends and switch to using the normal EDCA parameter set to contend for channel access rights (827). STA1 and STA2 are seen to be contending using the normal EDCA parameters after the R-TWT X SP (828 and 830).

[0228] 6.6. RTA Adaptive EDCA for Member STAs 31 illustrates an example embodiment 910 of RTA adaptive EDCA for R-TWT member STAs and non-R-TWT member STAs. This figure shows one R-TWT SP identified as ID "X" 414. STA1 (413) has membership in R-TWT X and STA2 (415) has membership in R-TWT Y. Unless otherwise stated in this context, it is assumed that the illustrated RTA traffic is from the same highest AC.

[0229] At the start of the R-TWT X SP, STA1, an R-TWT X member, and ST2, a non-R-TWT member, automatically switch (915) to using RTA adaptive EDCA parameters for the R-TWT member and non-R-TWT member, respectively, to contend for channel access rights (912, 914) until the end of the current R-TWT SP. It is assumed that the use of RTA adaptive EDCA parameters in this case is achieved through pre-configuration.

[0230] Assume that STA1 and STA2 have the same (AC, RTA remaining lifetime threshold) level of buffered RTA traffic, and the RTA adaptive EDCA parameters of the R-TWT members with the same (AC, RTA remaining lifetime threshold) level may have higher priority than those of non-R-TWT members.

[0231] In the first UL PPDU transmission sequence, STA1 has some of the most urgent RTA traffic buffered in the queue and should adjust EDCA according to the (AC, RTA remaining lifetime threshold) level of R-TWT membership. STA1 finishes BO 912 easier (faster) than STA2's BO 914, and thus gains channel access right to send PPDU 916 to the associated AP and receive Ack / BA 917.

[0232] In the second UL PPDU transmission sequence, STA1 and STA2 adjust the RTA adaptive EDCA parameters with STA1's priority 921 above STA2's priority. STA1 has some less urgent RTA traffic buffered in the queue and uses adaptive EDCA according to its (AC, RTA remaining lifetime threshold) level of R-TWT membership. STA1 still completes BO 918 faster than STA2, gains channel access right to send PPDU 922 to associated AP, and receives Ack / BA 924 from AP.

[0233] In the third UL PPDU transmission sequence, the stations still adjust their RTA adaptive EDCA parameters (AC, RTA remaining lifetime threshold), but this time STA2 has priority over STA1 because STA1 only has non-RTA traffic buffered in its queue (925). STA2 has some of the most urgent RTA traffic buffered and adjusts its EDCA according to the non-RTWT members' (AC, RTA remaining lifetime threshold) levels. Both stations contend for channel access using BO 926, 928 respectively. In this case, STA2, which has a higher EDCA priority than STA1, finishes BO 928 before STA1. STA2 transmits PPDU 930 to its associated AP and receives Ack / BA 932 from the AP.

[0234] STA1 and STA2 can be seen to switch back to normal EDCA parameters (933) upon the end of the current R-TWT x SP414 and contend (934, 936) for channel access rights.

[0235] 7. Description of the embodiment

[0236] The significant elements of this disclosure are described below in a hierarchical overview format, with references between the elements, so as to illustrate the interoperability of aspects of these elements.

[0237] A. In the new feature, a non-AP STA supporting this feature can dynamically adjust the EDCA corresponding to the AC of the buffered RTA MSDU and the dynamically decreasing remaining RTA lifetime, and this feature is designed as follows: (a) This new feature uses an RTA adaptive EDCA parameter set that defines new EDCA parameters based on the AC of the buffered MSDU and the remaining RTA lifetime. (a)(i) The RTA adaptive parameters include CWmin[AC, RTA remaining lifetime threshold], CWmax[AC, RTA remaining lifetime threshold], AIFSN[AC, RTA remaining lifetime threshold], and RTA adaptive EDCA TXOP limit[AC, RTA remaining lifetime threshold], etc. (b) Multiple threshold levels, such as most urgent, moderately urgent, and less urgent, can be used for the evaluation of the remaining RTA lifetime. The mechanism for determining the exact RTA remaining lifetime threshold level depends on the application. (c) Over time, the MSDU lifetime decreases to reach the new RTA remaining lifetime threshold level, which causes the STA to use the new EDCA parameter set according to the new (AC, RTA remaining lifetime threshold) pair information. (d) The maximum backoff using the new EDCA parameter set may be required to be less than the initial RTA remaining lifetime of the MSDU. CWmax[AC, RTA remaining lifetime threshold] and AIFSN[AC, RTA remaining lifetime threshold] need to be properly designed to meet this requirement.

[0238] B. New RTA Adaptive EDCA parameter set elements introduced in IEEE Draft 10.1 that can be carried by beacon frames, probe response frames or (re)association frames. (a) When the remaining buffered RTA MSDU lifetime of an AC decreases to a certain threshold level, STAs using RTA Adaptive EDCA parameters shall automatically adjust their EDCA corresponding to the new (AC, RTA remaining lifetime threshold) level without negotiating with the associated AP. (b) It is possible to design different RTA remaining lifetime threshold levels for the buffered RTA MSDUs of the same AC.

[0239] C. Use of the RTA adaptive EDCA parameters can be initiated by (a) the AP triggering / signaling the non-AP EHT STA during the R-TWT SP(s) or (b) by pre-configuration when the non-AP EHT STA enters the R-TWT SP(s).

[0240] The trigger / signal sent by the AP for DCa may result from the AP detecting an unexpectedly long delay from the received RTA PPDU over a period of time.

[0241] E. STAs that support the new feature receive the Ca trigger / signal to complete the current UL TB communication sequence, and such STAs can switch to using the new RTA adaptive EDCA parameter set when they have a UL PPDU to the associated AP.

[0242] (a) The first new BO counter after switching to use the new feature can be one of the following: (i) the minimum BO value between the BO value obtained based on the new RTA adaptive EDCA parameter set and the remaining BO value (if any) based on normal EDCA from the previously paused BO counter, (ii) relying only on the BO value obtained based on the new RTA adaptive EDCA parameter set and ignoring the remaining BO value (if any) that can be reset to 0 from the previously paused BO counter, (iii) relying only on the remaining BO value (if any) that can be scaled from the previously paused BO counter and not using the BO value obtained based on the new RTA adaptive EDCA parameter set.

[0243] (b) The countdown of the BO counter based on the new feature follows the same rules as the baseline.

[0244] F. The period for applying the RTA adaptive EDCA parameters may be set by the RTA adaptive EDCA timer subfield of the RTA adaptive EDCA parameter set. The time for applying the RTA adaptive EDCA parameters may be as follows:

[0245] (a) Until the end of the current R-TWT SP.

[0246] (b) for a period of time within the current R-TWT SP. (i) When the RTA Adaptive EDCA timer (set as a non-zero value in the RTA Adaptive EDCA Parameter Set element) reaches zero, either by counting down or due to a reset after receiving an RTA Adaptive EDCA Reset frame introduced in IEEE Draft 10.2, the STA shall switch to using normal EDCA of the corresponding AC according to the value contained in the most recently received normal EDCA Parameter Set element sent by the associated AP.

[0247] G. Different RTA adaptive EDCA parameter sets are designed for different application groups, such as R-TWT member STAs and non-R-TWT member STAs. (a) R-TWT member STAs and non-R-TWT member STAs can have different RTA adaptive EDCA parameter sets at the same (AC, RTA remaining lifetime threshold) level. (b) R-TWT members can have higher RTA adaptive EDCA priority than non-R-TWT member STAs at the same (AC, RTA remaining lifetime threshold) level.

[0248] The H.AP may terminate the use of RTA adaptive EDCA for all / specific (AC, RTA remaining lifetime threshold) levels at any time during the R-TWT SP by: (a) sending an RTA adaptive EDCA reset frame that resets the non-AP STA to use the RTA adaptive EDCA parameter set for all / specific (AC, RTA remaining lifetime threshold) levels to use the most recently received EDCA parameter set for all / specific ACs; (i) upon receiving the RTA adaptive EDCA reset frame, the non-AP STA shall reset its RTA adaptive EDCA timer to 0 and the STA shall switch from using RTA adaptive EDCA to normal EDCA included in the most recently received EDCA parameter set element sent by the associated AP. For example, the non-AP STA shall switch from using CWmin[AC, RTA remaining lifetime threshold], CWmax[AC, RTA remaining lifetime threshold], and AIFSN[AC, RTA remaining lifetime threshold] to using CWmin[AC], CWmax[AC], and AIFSN[AC].

[0249] I. Non-AP STAs must automatically terminate the application of RTA adaptive EDCA for all (AC, RTA remaining lifetime threshold) levels upon the end of the current R-TWT SP and start using normal EDCA.

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

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

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

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

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

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

[0256] An apparatus for wireless communication in a network, comprising: (a) a wireless communication circuit that performs transmission of frames between a medium access control (MAC) layer of an IEEE 802.11 network as an STA that is an independent wireless station (STA) or as an STA in a multi-link device (MLD) and communicates wirelessly with other wireless stations (STAs) using a carrier sense multiple access with collision avoidance (CSMA / CA) mechanism on a wireless local area network (WLAN) in which enhanced distributed channel access (EDCA) is utilized for random channel access on all links; (b) a processor coupled to the wireless communication circuit and operating on the WLAN; and (c) a non-transitory memory that stores instructions executable by the processor for communicating with the other STAs, and (d) the instructions, when executed by the processor, perform transmission of frames between a medium access control (MAC) layer of an IEEE 802.11 network as an STA that is an independent wireless station (STA) or as an STA in a multi-link device (MLD), and communicates wirelessly with other wireless stations (STAs) using a carrier sense multiple access with collision avoidance (CSMA / CA) mechanism on a wireless local area network (WLAN) in which enhanced distributed channel access (EDCA) is utilized for random channel access on all links; an apparatus for performing steps of a wireless communication protocol for the wireless communication circuit, dynamically adjusting EDCA corresponding to an AC of a buffered RTA MSDU to dynamically reduce a remaining real-time application (RTA) lifetime, the steps including: (d)(ii) using a new RTA adaptive EDCA parameter set that defines new EDCA parameters based on an access category (AC) and a remaining real-time application (RTA) lifetime of a MAC service data unit (MSDU); (d)(ii) using multiple threshold levels to evaluate the remaining RTA lifetime; (d)(iii) the lifetime of the MSDU decreases over time to reach a new RTA remaining lifetime threshold level, causing a STA to use the new RTA adaptive EDCA parameter set; and (d)(iv) a maximum backoff when using the new RTA adaptive EDCA parameter set is less than an initial RTA remaining lifetime of the MSDU.

[0257] An apparatus for wireless communication in a network, comprising: (a) a wireless communication circuit that performs transmission of frames between a medium access control (MAC) layer of an IEEE 802.11 network as an STA that is an independent wireless station (STA) or as an STA in a multi-link device (MLD) and communicates wirelessly with other wireless stations (STAs) using a carrier sense multiple access with collision avoidance (CSMA / CA) mechanism on a wireless local area network (WLAN) in which enhanced distributed channel access (EDCA) is utilized for random channel access on all links; (b) a processor coupled to the wireless communication circuit and operating on the WLAN; and (c) a non-transitory memory that stores instructions executable by the processor for communicating with the other STAs, and (d) the instructions, when executed by the processor, perform transmission of frames between a medium access control (MAC) layer of an IEEE 802.11 network as an STA that is an independent wireless station (STA) or as an STA in a multi-link device (MLD), and communicates wirelessly with other wireless stations (STAs) using a carrier sense multiple access with collision avoidance (CSMA / CA) mechanism on a wireless local area network (WLAN) in which enhanced distributed channel access (EDCA) is utilized for random channel access on all links; 2. An apparatus for performing steps of a wireless communication protocol for the wireless communication circuit that dynamically adjusts EDCA corresponding to an AC of a buffered RTA MSDU and / or dynamically reduces the remaining RTA lifetime, the steps including: (d)(ii) using a new RTA adaptive EDCA parameter set that defines new EDCA parameters based on an access category (AC) and remaining real-time application (RTA) lifetime of a MAC service data unit (MSDU); (d)(ii) using multiple threshold levels to evaluate the remaining RTA lifetime; and (d)(iii) decreasing the lifetime of the MSDU over time to reach a new RTA remaining lifetime threshold level, causing the STA to use the new RTA adaptive EDCA parameter set that increases the probability that the STA will deliver the MSDU during the specified lifetime.

[0258] A method for performing wireless communication in a network, comprising: (a) performing wireless communication between a medium access control (MAC) layer of an IEEE 802.11 network as an independent radio station (STA) or as an STA in a multi-link device (MLD), operating as either a normal STA or an access point (AP) STA communicating wirelessly with other radio stations (STAs) using a carrier sense multiple access with collision avoidance (CSMA / CA) mechanism in a wireless local area network (WLAN) in which enhanced distributed channel access (EDCA) is utilized for random channel access on all links; and (b) performing buffered RTA A method comprising: (a) using a new RTA adaptive EDCA parameter set that defines new EDCA parameters based on an access category (AC) and a remaining real-time application (RTA) lifetime of a MAC service data unit (MSDU); (c) using multiple threshold levels to evaluate the remaining RTA lifetime; (d) the MSDU lifetime decreases over time to reach a new RTA remaining lifetime threshold level, causing a STA to use the new RTA adaptive EDCA parameter set; and (e) a maximum backoff when using the new RTA adaptive EDCA parameter set is less than an initial RTA remaining lifetime of the MSDU.

[0259] The apparatus or method of any preceding implementation, wherein the RTA adaptive EDCA parameter set has elements including CWmin, CWmax, AIFSN, and RTA adaptive EDCA TXOP limit.

[0260] The apparatus or method of any preceding implementation, wherein each of the elements of the RTA adaptive EDCA parameter set is applicable to the AC and RTA remaining lifetime thresholds.

[0261] The apparatus or method of any preceding implementation, wherein the threshold levels utilized to assess remaining RTA life include at least three thresholds: most urgent, moderately urgent, and less urgent.

[0262] The determination of the RTA remaining life threshold level is application dependent, apparatus or method of any preceding implementation.

[0263] The apparatus or method of any preceding implementation, wherein the CWmax threshold and RTA Lifetime threshold of the AC, and the AIFSN and RTA Lifetime threshold of the AC are adjusted to satisfy a requirement that the maximum backoff is less than the initial remaining RTA Lifetime of the MSDU.

[0264] The apparatus or method of any preceding implementation, further including communicating the RTA adaptive EDCA parameter set element via a beacon, a probe response, an association frame, or a reassociation frame.

[0265] The apparatus or method of any preceding implementation, further including, in response to determining that the remaining buffered RTA MSDU lifetime of the AC has decreased to a certain threshold level, automatically adjusting the EDCA corresponding to the new AC or RTA remaining lifetime threshold level without negotiating with an associated AP.

[0266] The apparatus or method of any preceding implementation, further including allowing for the existence of different RTA remaining lifetime threshold levels for buffered RTA MSDUs of the same AC.

[0267] An apparatus or method of any preceding implementation, wherein the determination of when the RTA adaptive EDCA parameter set is available is determined by (i) a trigger frame or signal from an access point (AP) STA to one or more non-AP very high throughput (EHT) STAs in one or more R-TWT SPs, or (ii) pre-configuration of a non-AP EHT STA when the non-AP EHT STA enters an R-TWT SP(s).

[0268] The apparatus or method of any preceding implementation, wherein the trigger frame or signal sent by the AP is in response to the AP detecting an unexpectedly long delay from a received RTA PPDU that exceeds a given period.

[0269] The apparatus or method of any preceding implementation further includes a STA supporting a new RTA adaptive EDCA parameter set receiving the trigger frame or signal, the STA switching to use the new RTA adaptive EDCA parameter set when it has a UL PPDU to send to an associated AP after completing a current upload (UL) trigger-based (TB) communication sequence.

[0270] An apparatus or method of any preceding implementation, wherein an initial backoff (BO) counter value after switching to use a new RTA adaptive EDCA parameter set feature is selected from the following values: (i) a minimum BO value between a BO value obtained based on the new RTA adaptive EDCA parameter set and any remaining BO value based on normal EDCA from a previously suspended BO counter, or (ii) relying only on a BO value obtained based on the new RTA adaptive EDCA parameter set while ignoring any remaining BO value from a previously suspended BO counter that can be reset to zero, or (iii) relying only on any remaining BO value from a previously suspended BO counter that can be scaled and not utilizing a BO value obtained based on the new RTA adaptive EDCA parameter set.

[0271] The apparatus or method of any preceding implementation, further including utilizing an RTA adaptive EDCA timer subfield of the RTA adaptive EDCA parameter set to determine the period for which the RTA adaptive EDCA parameter set applies.

[0272] The apparatus or method of any preceding implementation, wherein the period for applying the RTA adaptive EDCA parameter set is selected from a group of intervals including: (a) an interval that is applied until the end of the current R-TWT SP is reached, or (b) an interval that spans a specified period within the current R-TWT SP.

[0273] The apparatus or method of any preceding implementation further includes, when the RTA adaptive EDCA timer reaches a terminal value or in response to receiving a reset in an RTA adaptive EDCA reset frame, switching to utilize EDCA of the corresponding AC(s) according to a value contained in a most recently received normal EDCA parameter set element.

[0274] The apparatus or method of any preceding implementation, further comprising different RTA-adaptive EDCA parameter sets configured for different application groups.

[0275] The apparatus or method of any preceding implementation, wherein the different application groups are determined based on R-TWT membership status.

[0276] An apparatus or method of any preceding implementation, wherein a STA may receive an instruction from an associated AP at any time during an R-TWT SP to terminate use of an RTA-adaptive EDCA parameter set for all or a particular AC and / or RTA remaining lifetime threshold level(s).

[0277] The apparatus or method of any preceding implementation, wherein the instruction to terminate use of an RTA adaptive EDCA parameter set is received as part of a transmitted RTA adaptive EDCA reset frame for resetting a non-AP STA.

[0278] An apparatus or method of any preceding implementation, wherein all non-AP STAs automatically terminate application of the RTA adaptive EDCA parameter set level upon the end of the current R-TWT SP and start using normal EDCA.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0296] 110 Example of embodiment 112 Is the R-TWT SP in place or otherwise within the R-TWT SP and needs to initiate RTA adaptive EDCA? 114 Send a trigger frame to tell associated STAs to switch from EDCA to RTA-adaptive EDCA Received 116 TB-PPDU 118 BA / ACK response 120 Is it necessary to reset RTA adaptive EDCA parameters for certain or all (AC, RTA Life Threshold) levels? 122 Send RTA adaptive reset frame 124 BA / ACK received

Claims

1. An apparatus for wireless communication in a network, comprising: (a) a wireless communication circuit that performs transmission of frames between a medium access control (MAC) layer of an IEEE 802.11 network as an independent wireless station (STA) STA or as an STA in a multi-link device (MLD), and operates as either a normal STA or an access point (AP) STA that wirelessly communicates with other wireless stations (STAs) using a carrier sense multiple access with collision avoidance (CSMA / CA) mechanism on a wireless local area network (WLAN) in which enhanced distributed channel access (EDCA) is utilized for random channel access on all links; (b) a processor coupled to the wireless communication circuitry for operating on the WLAN; (c) a non-transitory memory storing instructions executable by said processor for communicating with other STAs; Equipped with (d) the instructions, when executed by the processor, (i) utilizing a new RTA adaptive EDCA parameter set that defines new EDCA parameters based on the Access Category (AC) and remaining Real Time Application (RTA) lifetime of buffered RTA MAC Service Data Units (MSDUs); (ii) multiple threshold levels are utilized to assess remaining RTA life; and (iii) the MSDU lifetime decreases over time to reach a new RTA remaining lifetime threshold level, causing the STA to use a new RTA adaptive EDCA parameter set; and (iv) a maximum backoff when using the new RTA adaptive EDCA parameter set is less than the initial RTA remaining lifetime of the MSDU; and performing steps of a wireless communication protocol for the wireless communication circuit, the steps including: dynamically adjusting EDCAs corresponding to ACs of buffered RTA MSDUs to dynamically reduce a remaining RTA lifetime; An apparatus comprising:

2. The RTA adaptive EDCA parameter set has elements including CWmin, CWmax, AIFSN, and RTA adaptive EDCA TXOP limit.

2. The apparatus of claim 1.

3. Each of the elements of the RTA adaptive EDCA parameter set is applicable to AC and RTA remaining life thresholds.

3. The apparatus of claim 2.

4. The threshold levels utilized to assess remaining RTA life include at least three thresholds as most urgent, moderately urgent, and less urgent.

2. The apparatus of claim 1.

5. The determination of the RTA remaining life threshold level is application dependent.

2. The apparatus of claim 1.

6. the CWmax threshold and the RTA Lifetime threshold of the AC, and the AIFSN and the RTA Lifetime threshold of the AC are adjusted to satisfy the requirement that the maximum backoff is less than the initial remaining RTA Lifetime of the MSDU; 2. The apparatus of claim 1.

7. and communicating the RTA adaptive EDCA parameter set element through a beacon, a probe response, an association frame, or a reassociation frame.

2. The apparatus of claim 1.

8. and in response to determining that the remaining buffered RTA MSDU lifetime of the AC has decreased to a certain threshold level, automatically adjusting the EDCA corresponding to the new AC or RTA remaining lifetime threshold level without negotiating with an associated AP.

2. The apparatus of claim 1.

9. and enabling the existence of different RTA remaining lifetime threshold levels for buffered RTA MSDUs of the same AC.

2. The apparatus of claim 1.

10. The determination of when the RTA adaptive EDCA parameter set is available is determined by (i) a trigger frame or signal from an access point (AP) STA to one or more non-AP very high throughput (EHT) STAs during one or more R-TWT SPs, or (ii) pre-configuration of a non-AP EHT STA when the non-AP EHT STA enters the R-TWT SP(s); 2. The apparatus of claim 1.

11. The trigger frame or signal transmitted by an AP is in response to the AP detecting an unexpectedly long delay, exceeding a given period, from a received RTA PPDU.

11. The apparatus of claim 10.

12. The method further includes a STA supporting a new RTA-adaptive EDCA parameter set receiving the trigger frame or signal, and the STA switches to use the new RTA-adaptive EDCA parameter set when the STA has an UL PPDU to transmit to an associated AP after completing a current upload (UL) trigger-based (TB) communication sequence.

11. The apparatus of claim 10.

13. The initial back-off (BO) counter value after switching to use the new RTA-adaptive EDCA parameter set feature is selected from values ​​consisting of: (i) a minimum BO value between the BO value obtained based on the new RTA-adaptive EDCA parameter set and any remaining BO value based on normal EDCA from the previously suspended BO counter; or (ii) relying only on the BO value obtained based on the new RTA-adaptive EDCA parameter set while ignoring any remaining BO value from the previously suspended BO counter that may be reset to zero; or (iii) relying only on any remaining BO value from the previously suspended BO counter that may be scaled and not utilizing the BO value obtained based on the new RTA-adaptive EDCA parameter set.

13. The apparatus of claim 12.

14. determining a period for applying the RTA adaptive EDCA parameter set using an RTA adaptive EDCA timer subfield of the RTA adaptive EDCA parameter set; 2. The apparatus of claim 1.

15. The time period for applying the RTA adaptive EDCA parameter set is selected from a group of intervals including: (a) an interval that applies until the end of the current R-TWT SP is reached; or (b) an interval that spans a specified time period within the current R-TWT SP.

15. The apparatus of claim 14.

16. and when the RTA-adaptive EDCA timer reaches a termination value or in response to receiving a reset in an RTA-adaptive EDCA reset frame, switching to utilize EDCA of the corresponding AC(s) according to a value included in a most recently received normal EDCA parameter set element.

15. The apparatus of claim 14.

17. and further comprising different RTA adaptive EDCA parameter sets configured for different application groups.

2. The apparatus of claim 1.

18. The different application groups are determined based on R-TWT membership status.

20. The apparatus of claim 17.

19. The STA may receive a command from an associated AP at any time during the R-TWT SP to terminate use of the RTA adaptive EDCA parameter set for all or a particular AC and / or RTA remaining lifetime threshold level(s); 2. The apparatus of claim 1.

20. The command to terminate use of the RTA-adaptive EDCA parameter set is received as part of a transmitted RTA-adaptive EDCA reset frame to reset a non-AP STA.

20. The apparatus of claim 19.

21. All non-AP STAs automatically terminate the application of the RTA adaptive EDCA parameter set level and start using normal EDCA at the end of the current R-TWT SP; 2. The apparatus of claim 1.

22. An apparatus for wireless communication in a network, comprising: (a) a wireless communication circuit that performs transmission of frames between a medium access control (MAC) layer of an IEEE 802.11 network as an independent wireless station (STA) STA or as an STA in a multi-link device (MLD), and operates as either a normal STA or an access point (AP) STA that wirelessly communicates with other wireless stations (STAs) using a carrier sense multiple access with collision avoidance (CSMA / CA) mechanism on a wireless local area network (WLAN) in which enhanced distributed channel access (EDCA) is utilized for random channel access on all links; (b) a processor coupled to the wireless communication circuitry for operating on the WLAN; (c) a non-transitory memory storing instructions executable by said processor for communicating with other STAs; Equipped with (d) the instructions, when executed by the processor, (i) utilizing a new RTA adaptive EDCA parameter set that defines new EDCA parameters based on the Access Category (AC) and remaining Real Time Application (RTA) lifetime of buffered RTA MAC Service Data Units (MSDUs); (ii) multiple threshold levels are utilized to assess remaining RTA life; and (iii) the MSDU lifetime decreases over time to reach a new RTA remaining lifetime threshold level, causing the STA to use a new RTA adaptive EDCA parameter set that increases the probability that the STA will deliver the MSDU within the specified lifetime; and dynamically adjusting EDCAs corresponding to ACs of buffered RTA MSDUs and / or dynamically decreasing a remaining RTA lifetime; An apparatus comprising:

23. 1. A method for conducting wireless communication in a network, comprising: (a) performing wireless communication between the medium access control (MAC) layer of an IEEE 802.11 network as an independent STA or as an STA in a multi-link device (MLD), and operating as either a normal STA or an access point (AP) STA that communicates wirelessly with other STAs using a carrier sense multiple access / collision avoidance (CSMA / CA) mechanism on a wireless local area network (WLAN) in which enhanced distributed channel access (EDCA) is utilized for random channel access on all links; (b) utilizing a new RTA adaptive EDCA parameter set that defines new EDCA parameters based on the Access Category (AC) and remaining Real Time Application (RTA) lifetime of buffered RTA MAC Service Data Units (MSDUs); and (c) multiple threshold levels are utilized to assess remaining RTA life; and (d) the MSDU lifetime decreases over time to reach a new RTA remaining lifetime threshold level, causing the STA to use a new RTA adaptive EDCA parameter set; and (e) a maximum backoff when using the new RTA adaptive EDCA parameter set is less than the initial RTA remaining lifetime of the MSDU; and The method according to claim 1, further comprising:

Images