Prioritization of R-TWT TIDs in R-TWT SP

Abstract

A method for resolving the contention problem in the R-TWT SP will be described. Specifically, an enhanced mechanism for prioritizing the transmission of the R-TWT TID in the corresponding R-TWT SP is defined. Also, an enhanced access mechanism for resolving the problem that the station accesses the channel after detecting an idle channel after the DIFS or AIFS period will be described.

Description

Technical Field

[0001] 〔Cross - Reference to Related Applications〕 This application claims priority and the benefit of U.S. Provisional Patent Application Serial No. 63 / 371,406, filed on August 15, 2022, the entire disclosure of which is incorporated herein by reference. This application claims priority and the benefit of U.S. Provisional Patent Application Serial No. 63 / 367,387, filed on June 30, 2022, the entire disclosure of which is incorporated herein by reference. This application claims priority and the benefit of U.S. Provisional Patent Application Serial No. 63 / 367,342, filed on June 30, 2022, the entire disclosure of which is incorporated herein by reference.

[0002] 〔Description of Federally Sponsored Research or Development〕 Not applicable

[0003] 〔Notice 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 does not object to the reproduction by others of the patent document or the patent disclosure, as it appears in the U.S. Patent and Trademark Office's general - public file or records, but reserves all copyrights otherwise. The copyright owner does not hereby waive any of its rights to maintain the patent document in confidence, including, but not limited to, the rights under 37 C.F.R. § 1.14.

[0004] The technology of this disclosure generally relates to restricted - target wait time (R - TWT) operations. Specifically, it relates to assigning R - TWT TIDs and preventing collisions during the R - TWT service period (SP) when using DIFS / AIFS access.

Background Art

[0005] Restricted Target Weight Time (R-TWT) scheduling is performed by an access point (AP) that determines which R-TWT TIDs are considered delay-sensitive traffic. However, in the current configuration, there is a risk of misuse of R-TWT IDs. Also, collisions may occur within the R-TWT SP when using DIFS / AIFS access.

Summary of the Invention

Problems to be Solved by the Invention

[0006] Therefore, there is a need for enhanced mechanisms within the wireless protocol to address these R-TWT issues. This disclosure meets these needs and provides additional advantages over existing systems.

Means for Solving the Problems

[0007] Wireless protocol enhancements under IEEE802.11 (e.g., IEEE802.11be) that resolve the contention problem in the R-TWT SP are described. Specifically, enhanced mechanisms for prioritizing the transmission of R-TWT TIDs within the corresponding R-TWT SP are defined. Also described are enhanced access mechanisms that resolve the problem of a station accessing the channel after detecting an idle channel after the DIFS or AIFS period.

[0008] In the following parts of this specification, further aspects of the technology described herein will become apparent, and this detailed description is for the purpose of fully disclosing the technology without limiting the preferred embodiments of the technology.

[0009] The technology described herein will be fully understood by referring to the following drawings for illustrative purposes only.

Brief Description of the Drawings

[0010]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Mode for Carrying Out the Invention

[0011] 1. Communication Station (STA) Hardware FIG. 1 shows an exemplary embodiment 10 of STA hardware configured to execute the protocol of the present disclosure. An external I / O connection 14 is coupled to an internal bus 16 of the circuit 12, and a CPU 18 and a memory (e.g., RAM) 20 are preferably connected on the internal bus 16 to execute a program (single or plural) implementing a communication protocol. The host machine houses at least one modem 22 supporting communication, which is coupled to at least one RF module 24, 28 each connected to one or more antennas 29, 26a, 26b, 26c~26n. The RF module having a plurality of antennas (e.g., an antenna array) enables the execution of beamforming during transmission and reception. Thus, the STA can transmit signals using multiple sets of beam patterns.

[0012] Bus 14 can connect various devices such as sensors and actuators to the CPU. On the processor 18, instructions from the memory 20 are executed to run a program implementing a communication protocol that enables the STA to perform the functions of an access point (AP) station or a normal station (non-AP STA). Also, this programming is configured to operate in different modes (TXOP owner, TXOP shared participant, source, intermediate, destination, first AP, other AP, station related to the first AP, station related to other AP, coordinator, coordinatee, AP within OBSS, and STA within OBSS, etc.) depending on what role it is playing in the current communication situation.

[0013] Accordingly, the illustrated STA HW is composed of at least one modem and associated RF circuitry for providing communication on at least one band. Note that it should be understood that the present disclosure can be configured using a plurality of modems 22 each coupled to any number of RF circuits. Generally, the more RF circuits used, the wider the coverage of the antenna beam direction. 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 can be disabled when the 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 a plurality of antennas controlled to perform beamforming for transmission and reception. Thus, the STA can transmit signals using a set of multiple beam patterns where each beam pattern direction is regarded as an antenna sector.

[0014] Also, multiple instances of the local hardware as shown in this figure can be combined into a multi-link device (MLD). Usually, this MLD has a processor and memory for coordinating activities. However, since separate CPUs and memories are not necessarily required for each STA within the MLD, it should be understood that these resources can be shared.

[0015] 2. R-TWT ID Problem 2.1. Description of the R-TWT ID Problem IEEE802.11be [Draft P802.11be_D2.0] defines a stream classification service (SCS) traffic stream (TS) and a restricted target weight time (R-TWT) schedule for the purpose of low-latency features in Wi-Fi networks.

[0016] The member station (STA) of the R-TWT and the R-TWT schedule side access point (AP) negotiate to determine an R-TWT traffic identifier (TID) that is considered traffic that is less sensitive to delay during the service period (SP) of the R-TWT and should be transmitted with a higher priority than normal traffic during the SP of the R-TWT. However, a method for setting the R-TWT TID during the membership setup procedure is not defined. What is needed is an enhanced protocol that provides restrictions / rules to avoid abuse of the R-TWT TID during the R-TWT SP.

[0017] Both the member STA and the non-member STA end the TXOP before the start of the next R-TWT SP. However, no different behavior is shown between the member STA and the non-member STA over the next R-TWT SP. If the member STA and the non-member STA behave similarly, there is no advantage in being a member STA within the next R-TWT SP.

[0018] 2.2. Overview of R-TWT ID Solutions The disclosed technology enhances the existing protocol by defining rules and restrictions regarding when to set the R-TWT TID during the R-TWT membership negotiation procedure and how to prioritize the transmission of the R-TWT TID during the corresponding R-TWT SP. Section 3 describes the solutions according to this disclosure.

[0019] 3. Solution Examples (1) In an IEEE802.11 network, when a STA negotiates the membership of an R-TWT with an R-TWT schedule side AP, only the TID established as a (single or multiple) stream classification service (SCS) traffic stream (TS) can be set as the R-TWT TID of that R-TWT. (a) The R-TWT TID can be an R-TWT uplink (UL) TID, an R-TWT downlink (DL) TID, and an R-TWT peer-to-peer (P2P) TID. In particular, the R-TWT P2P TID means the TID of an SCS traffic stream whose direction is P2P. (b) In the case of the R-TWT P2P TID, the STA needs to follow the corresponding TID-link mapping of the SCS traffic stream indicated in the QoS characteristic element of the SCS traffic stream.

[0020] (2) Multiple SCS traffic streams can share the same TID only when one or more of the following conditions are met. (a) When these SCS traffic streams have the same delay bound (and / or MSDU lifetime) within the QoS characteristic element. (b) When the differentiated service code point (DSCP) range of TID / UP is set to zero and the original DSCP range of TID / UP is covered by other TIDs, user priorities (UPs), or access categories (ACs). (c) When only one TID within an AC can be used as the R-TWT TID, or both TIDs within the same AC must be used as the R-TWT TID. (d) In the case of a P2P SCS traffic stream, when the SCS traffic stream must have the same TID-link mapping within its QoS characteristic element.

[0021] (3) The R-TWT schedule side AP cannot schedule an R-TWT SP time exceeding the requirements of its R-TWT TID. (a) For example, when the R-TWT TID has only one SCS traffic stream, the R-TWT SP time (R-TWT SP period / R-TWT SP interval) should not be longer than the media time of the SCS traffic stream (time per second). (b) When the R-TWT TID has multiple SCS traffic streams, the media time should be the total media time of all SCS traffic streams of that R-TWT TID. (c) When the TID is the R-TWT TID of multiple R-TWTs, the R-TWT SP time should be the total R-TWT SP time of these R-TWTs. (d) When the media time of the SCS traffic stream is calculated for the required transmission time over a specific bandwidth (e.g., 20 MHz), the schedule side AP should reduce the channel time allocated for the transmission of the SCS traffic stream when the bandwidth is wider than 20 MHz.

[0022] (4) When the R-TWT schedules non-trigger-enabled SPs, the member STA of the R-TWT that is the TXOP owner must ensure that the TXOP ends before the start time of any SP of the R-TWT, except for the TXOP used to transmit the R-TWT TID after the start time of the SP. (a) If the primary AC of the TXOP is not mapped to any R-TWT TID of the member STA, the member STA must end the TXOP unless it can share the TXOP to transmit frames of the R-TWT TID after the start time of the SP. (b) Alternatively, if the primary AC of the TXOP is not mapped to any R-TWT TID of the member STA, in at least one embodiment / mode / option, the member STA shares the TXOP to transmit frames of the R-TWT TID after the start time of the SP even if there are frames of the primary AC to be transmitted remaining. (c) The member STA should check whether it has enough time to complete the transmission of these frames (including solicited responses) by the start time of the next R-TWT SP before transmitting frames that are not of the R-TWT TID of the next R-TWT SP. If there is not enough time for that, the STA should resume the backoff process using the contention window (CW[AC]) of the access class (AC) and the QoS Short Retry Counter (QSRC[AC]) of the AC that is not changed immediately without transmitting.

[0023] (5) When the R-TWT schedules a trigger-enabled SP, the member STA of the R-TWT, which is the TXOP owner, must ensure that it shares the TXOP with the R-TWT scheduling side AP before the start of any SP of the R-TWT, or ensure that the TXOP ends before the start of any SP of the R-TWT. (a) The member STA can send a frame such as a CTS frame or a QoS frame in which the Reverse Direction Grant (RDG) is set to the first state (e.g., "1") to the scheduling side AP to share its TXOP (start the RDG). When the AP receives the Clear-To-Send (CTS) frame, it can function (operate) as the TXOP owner in the CTS frame period (or the Network Allocation Vector (NAV)) field to extend the TXOP. (b) The member STA can send a frame to share its TXOP with the AP even if it cannot complete the frame transmission by the start of the R-TWT SP.

[0024] (6) The R-TWT scheduling side AP, which is the TXOP owner during the R-TWT SP, can send frames of any R-TWT TID of the R-TWT SP for the reason that they are frames from the primary AC during the TXOP. In at least one embodiment / mode / option, the AP can use the Enhanced Distributed Channel Access Functions (EDCAF) of any AC to obtain the TXOP during the R-TWT SP, or can use only the EDCAF of the R-TWT (DL) TID of the R-TWT SP to obtain the TXOP during the R-TWT SP.

[0025] (7) The (member or R-TWT scheduled side) STA should send frames with a TID that is not any R-TWT TID of any R-TWT outside the R-TWT SP.

[0026] (8) Member STA shall not transmit the frame of its R-TWT TID outside the SP of the R-TWT.

[0027] (9) The STA on the R-TWT schedule side (or only the member STA of the trigger-enabled R-TWT SP) shall follow the rules / behaviors of the STA on the TWT schedule side within the trigger-enabled R-TWT SP. Note that the STA on the R-TWT schedule side refers to the STA that supports the R-TWT feature.

[0028] FIG. 2 shows an example embodiment 50 of a restricted target weight time (R-TWT) traffic information field utilized in accordance with at least one embodiment of the present disclosure.

[0029] The following sub-fields are added as compared with those of IEEE802.11be D2.0. A Peer-to-Peer (P2P) Traffic Identification (TID) Bitmap Valid field that can include a 1-bit indication is added. For example, when this field is set to the first state (e.g., "1"), a Restricted TWT P2P TID Bitmap exists within the restricted TWT traffic information field. Otherwise, this field is set to the second state (e.g., "0") and the restricted TWT P2P TID Bitmap does not exist. When this field is set to the second state (e.g., "0"), it can indicate either (a) all P2P SCS traffic streams are regarded as the R-TWT TID of the R-TWT, or (b) none of the P2P SCS traffic streams are regarded as the R-TWT TID of the R-TWT.

[0030] When the Negotiation Type subfield of the TWT element is equal to "2", the P2P TID bitmap valid subfield is set to a second state (e.g., "0").

[0031] The restricted TWT P2P TID bitmap has each bit of this subfield representing a TID (e.g., TIDs 0 to 7). When the bit of this subfield is set to a first state (e.g., "1"), the corresponding TID of the P2P traffic is regarded as the R-TWT TID of the R-TWT. Otherwise, this subfield is set to a second state (e.g., "0").

[0032] FIG. 3 shows an embodiment example 70 of adding an Emergency Preparedness Service (EPCS) priority access enabled field within a Quality of Service (QoS) characteristic element (the QoS characteristic element is an existing element in the IEEE specification. Refer to the 11be specification, 9.4.2.316 QoS characteristic element - FIG. 9 - 1002au - QoS characteristic element format).

[0033] The STA on the R-TWT schedule side can ignore the R-TWT schedule under the following conditions when it has enabled emergency preparedness communication service (EPCS) priority access. (a) When the STA on the R-TWT schedule side that is the TXOP owner transmitting EPCS traffic can continue its TXOP beyond the start time of any R-TWT SP. Specifically, when the STA cannot end its TXOP before the start time of the R-TWT SP. (b) When the STA on the R-TWT schedule side that is the TXOP owner transmitting EPCS traffic ignores overlapping quiet intervals during the R-TWT SP.

[0034] EPCS traffic can be identified as an SCS traffic stream. An EPCS traffic subfield indicating that the SCS traffic stream is EPCS traffic is added within the QoS characteristic element (note that the control information field is the fourth field of the QoS characteristic element, and the details of the control information field can be found in the 11be specification shown as the control information field format in Figure 9-1002av). When this field is set to the first state (e.g., "1"), the SCS traffic stream under this QoS characteristic element is EPCS traffic. Otherwise, this field is set to the second state (e.g., "0"), and the SCS traffic stream under this QoS characteristic element is not EPCS traffic.

[0035] The R-TWT schedule side STA can ignore the R-TWT schedule when the emergency preparedness communication service (EPCS) priority access is enabled. When the R-TWT schedule side STA, which is the TXOP owner transmitting EPCS traffic, can continue the TXOP beyond the start time of any R-TWT SP. Specifically, the STA does not need to end the TXOP before the start time of the R-TWT SP. The R-TWT schedule STA, which is the TXOP owner transmitting EPCS traffic, can ignore overlapping quiet intervals during the R-TWT SP.

[0036] The member STAs of the R-TWT can use the MU EDCA parameters to compete for a channel for the R-TWT TID (or traffic sensitive to delay) during the R-TWT SP, even if the member STAs use the MU EDCA parameters to compete for a channel before the start time of the R-TWT SP and the MU EDCA timer has not expired at the start of the R-TWT SP.

[0037] In at least one embodiment / mode / option, member STA continues to use the MU EDCA parameters immediately after finishing transmission during the R-TWT SP, or immediately after the R-TWT SP ends. Member STA continues to count down the MU EDCA timer that was paused at the start of the R-TWT SP, as long as the MU EDCA timer is not updated during that period.

[0038] In at least one embodiment / mode / option, member STA resets the MU EDCA timer to zero for the AC of the R-TWT UL TID (or delay-insensitive traffic) at the start of the R-TWT SP.

[0039] The scheduled STA that is not a member STA of the R-TWT must use the MU-EDCA parameters to compete for the channel during the SP of the R-TWT.

[0040] Member STA of the R-TWT must use the MU EDCA parameters to compete for the channel for non-R-TWT TID (or traffic not affected by delay) during the SP of the R-TWT.

[0041] Figures 4 to 6 show Example Embodiment 150 of R-TWT prioritization for non-AP STAs. In Check 152, it is determined whether the non-AP has negotiated R-TWT membership. If the non-AP has not negotiated membership, the process ends.

[0042] Otherwise, in Block 154, the non-AP STA negotiates for the TIDs established during the SCS procedure. In Check 156, it is determined whether the non-AP STA has enabled EPCS priority access. If it is enabled, in Block 168, the non-AP STA can ignore any R-TWT schedule and the process ends.

[0043] In check 156, if it is determined that the non-AP STA has not enabled EPCS priority access, the execution reaches check 158 in FIG. 6 to determine whether the STA is the TXOP owner.

[0044] If the STA is the TXOP owner, in check 160, it is determined whether the next R-TWT SP is of the trigger-enabled type. If it is not of the trigger-enabled type, in block 178, the STA cannot end its TXOP at the start of a non-triggered R-TWT SP if it intends to use the current TXOP to send an R-TWT TID, and then the execution ends.

[0045] Otherwise, in check 162, a decision is made between option "a" and option "b". In option "a", the STA decides to share the TXOP with the R-TWT schedule side AP at the start of the triggered R-TWT SP (164). In option "b", the STA decides to end the TXOP before the start of the triggered R-TWT SP (166). The process ends after either option "a" or option "b" is executed.

[0046] Next, returning to check 158 in FIG. 6, if the STA is not the TXOP owner, the execution proceeds to block 170 in FIG. 7 to determine whether the STA is an R-TWT member STA.

[0047] If this condition is met, in check 172, it is determined whether the STA is sending R-TWT TID traffic. If the condition is met, in block 176, the STA can use EDCA or MU-EDCA to compete for the channel during the R-TWT SP, and then the process ends.

[0048] If either condition of Check 170 or 172 is not satisfied, at block 174, the STA uses MC-EDCA to compete for a channel during the T-TWT SP, and then the process ends.

[0049] FIG. 7 shows an example embodiment 210 of R-TWT prioritization for an AP STA. At check 212, it is determined whether there is a scheduled R-TWT for the R-TWT member STA. If the condition is not satisfied, the process ends.

[0050] On the other hand, if the condition is satisfied, at block 214, the AP cannot exceed the QoS requirements of the scheduled R-TWT SP during the SCS procedure for the corresponding R-TWT TID.

[0051] Next, at check 216, it is determined whether the AP is the TXOP owner. If the condition is satisfied, at block 218, the AP can transmit traffic for any R-TWT TID during the R-TWT SP or obtain a TXOP using the EDCAF of any AC.

[0052] Otherwise, at block 220, the AP can continue the shared TXOP from the R-TWT member STA at the start of the R-TWT SP and act as the TXOP owner. After either execution of block 218 or 220, the execution ends.

[0053] 4. DIFs / AIFs Access 4.1. DIFs / AIFs Access Problem In IEEE 802.11, under certain conditions such as when an arriving packet reaches the transmission queue of an idle STA, the STA can access the channel immediately after detecting channel idle for the DIFS period. This is called DIFS access. Note that when using DIFS access, the STA does not select a backoff count or count down the backoff slots. The STA on the R-TWT schedule side starts competing for the channel at the start of the R-TWT SP. If these STAs are permitted to compete for the channel using DIFS access, collisions will occur when multiple STAs use DIFS access. AIFS access is similar to DIFS access, that is, the STA accesses the channel after detecting channel idle for the AIFS period under certain conditions, and these conditions are the same as those for DIFS access.

[0054] 4.2. Solutions for DIFs / AIFs Access The STA on the R-TWT schedule side shall not use DIFS access (and / or AIFS access) to compete for the channel at the start of the R-TWT SP.

[0055] FIG. 8 shows an example 310 of detecting whether the channel is idle over the DIFs period.

[0056] This figure shows the DIFs access 312 during the DIFS period 314 and the access 316 after DIFS that can be used under certain conditions. The period of deferred access 320 is also shown. It shows that DIFS 314 follows after the medium is busy 318. Then a backoff 324 is executed, showing the backoff slot 326 and the single slot time 328. Note that the backoff count can be decremented as long as the medium is idle (330). The next frame 332 is shown after the backoff.

[0057] The following are possible different solutions.

[0058] The STA on the R-TWT schedule side shall not use DIFS access (or AIFS access) during the R-TWT SP. The STA on the R-TWT schedule side shall not use DIFS access (or AIFS access) during the first x periods of the R-TWT SP. The value of x represents time in seconds, milliseconds, or microseconds. For example, the STA on the R-TWT schedule side shall not use DIFS access (or AIFS access) during the first 43 microseconds (DIFS time + backoff slot time). Note that the STA on the R-TWT schedule side shall not use the DIFS access procedure as shown in 312 of FIG. 8, or the AIFS access procedure not shown in this figure, within the first x hours of the R-TWT SP. If DIFS / AIFS access is used, the STA shall not execute the backoff procedure as shown at the start of 330 - 332.

[0059] The STA on the R-TWT schedule side can use only the backoff procedure to compete for the channel (select and decrement the backoff count). In at least one embodiment / mode / option, the STA cannot select a zero backoff count.

[0060] The member STAs of the R-TWT can use the EDCA parameters to compete for the channel for the R-TWT TID (or traffic sensitive to delay) during the R-TWT SP, even if they use the MU EDCA parameters to compete for the channel before the start of the R-TWT SP, even if the MU EDCA timer has not expired at the start of the R-TWT SP.

[0061] In at least one embodiment / mode / option, the member STA continues to use the MU EDCA parameters immediately after finishing transmission during the R-TWT SP, or immediately after the end of the R-TWT SP. The member STA continues to count down the MU EDCA timer that was paused at the start of the R-TWT SP, as long as the MU EDCA timer is not updated during that period.

[0062] In at least one embodiment / mode / option, at the start of the R-TWT SP, member STA resets the MU EDCA timer to zero for the AC of the R-TWT UL TID (or traffic that is not sensitive to delay).

[0063] The scheduled STA that is not a member STA of the R-TWT uses the MU-EDCA parameters to compete for the channel during the SP of the R-TWT.

[0064] The member STA of the R-TWT uses the MU EDCA parameters to compete for the channel for non-R-TWT TIDs (or traffic not affected by delay) during the SP of the R-TWT.

[0065] 5. General scope of the embodiments In this specification, embodiments of the present technology can be described with reference to methods and systems, and / or procedures, algorithms, steps, operations, mathematical formulas, or other computational representations in the form of a flowchart, which can also be implemented as a computer program product. In this regard, each block or step of the flowchart, and combinations of blocks (and / or steps) of the flowchart, as well as any procedure, algorithm, step, operation, mathematical formula, or computational representation, can be implemented by various means such as software including one or more computer program instructions embodied in hardware, firmware, and / or computer-readable program code. As will be understood, such any computer program instructions can be executed by one or more computer processors including, but not limited to, general-purpose computers or special-purpose computers, or any other programmable processing device for producing machines, such that the computer program instructions executed on the computer processor or other programmable processing device create means for implementing the specified functions (singular or plural).

[0066] Accordingly, the blocks of the flowcharts, as well as the procedures, algorithms, steps, operations, mathematical formulas, or computational expressions described herein, support computer program instructions for performing (single or plural) specific functions, in the form of combinations of means for performing (single or plural) specific functions, combinations of steps for performing (single or plural) specific functions, and computer-readable program code logic means. Also, it will be understood that each block of the flowcharts described herein, as well as any procedure, algorithm, step, operation, mathematical formula, or computational expression, and combinations thereof, can be implemented by a dedicated hardware-based computer system for performing (single or plural) specific functions or steps, or by a combination of dedicated hardware and computer-readable program code.

[0067] Furthermore, these computer program instructions, embodied in the form of computer-readable program code or the like, can be stored in one or more computer-readable memories or memory devices that direct a computer processor or other programmable processing device to function in a specific manner, such that the instructions stored in these computer-readable memories or memory devices produce an article of manufacture that includes instruction means for performing the functions specified within (single or plural) blocks of (single or plural) flowcharts. The computer program instructions can be executed by a computer processor or other programmable processing device to generate a computer-implemented process in which a series of operational steps are executed on the computer processor or other programmable processing device, and the instructions executed on the computer processor or other programmable processing device provide steps for performing the functions specified within (single or plural) blocks, (single or plural) procedures, (single or plural) algorithms, (single or plural) steps, (single or plural) operations, (single or plural) mathematical formulas, or (single or plural) computational expressions of (single or plural) flowcharts.

[0068] Furthermore, as used herein, the terms "program" or "program executable statement" 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 can be embodied in software, firmware, or a combination of software and firmware. The instructions can be stored locally on a non-transitory medium of the device, or stored remotely, such as on a server, or some instructions can be stored locally and some remotely. The remotely stored instructions can be downloaded (pushed) to the device automatically by a user's initiation or based on one or more factors.

[0069] Furthermore, as used herein, the terms processor, hardware processor, computer processor, central processing unit (CPU), and computer are used synonymously to denote a device capable of executing instructions and communicating with an input / output interface 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 variants thereof.

[0070] From the description herein, it will be understood that the present disclosure includes a plurality of technical implementations including, but not limited to, the following.

[0071] An apparatus for wireless communication in a network, which operates as either a normal non-access point (AP) STA or an access point (AP) STA that performs transmission of frames between the media access control (MAC) layers of an IEEE 802.11 network as an independent station (STA) or an STA within a multi-link device (MLD), and wirelessly communicates with other wireless stations (STAs) using a carrier sense multiple access / collision avoidance (CSMA / CA) mechanism on a wireless local area network (WLAN) where extended distributed channel access (EDCA) is used for random channel access on all links, or trigger-based channel access is used for trigger-based (TB) uplink transmission on all links; a wireless communication circuit; (b) a processor coupled to the wireless communication circuit and operating on the WLAN; and (c) a non-transitory memory storing instructions executable by the processor for communicating with other STAs, wherein (d) the instructions, when executed by the processor, prioritize transmission for setting a restricted target weight time (R-TWT) traffic identifier (TID) during R-TWT membership negotiation, and (d)(i) negotiate the R-TWT service period (SP) between the R-TWT schedule side STA and the R-TWT schedule side AP to become an R-TWT member STA of the R-TWT SP, and (d)(ii) the R-TWT SP is prioritized as negotiated for transmission of low-latency traffic having a specific TID, where two types of channel access, trigger-enabled channel access and non-trigger-enabled channel access, are provided, thereby identifying the R-TWT SP as either a trigger-enabled R-TWT SP or a non-trigger-enabled R-TWT SP, and executing steps of a wireless communication protocol for the wireless communication circuit.

[0072] A method for performing wireless communication in a network, comprising: (a) operating as either a normal non-access point (AP) STA or an access point (AP) STA that performs transmission of frames between the media access control (MAC) layers of an IEEE 802.11 network as an independent wireless station (STA) or an STA within a multi-link device (MLD), and using a carrier sense multiple access / collision avoidance (CSMA / CA) mechanism to wirelessly communicate with other wireless stations (STA) on a wireless local area network (WLAN) where extended distributed channel access (EDCA) is used for random channel access on all links or trigger-based (TB) channel access is used for trigger-based uplink transmission on all links; (b) negotiating the R-TWT SP between the R-TWT schedule side STA and the R-TWT schedule side AP to become an R-TWT member STA of the R-TWT SP; (c) in the R-TWT, prioritizing the transmission of low-latency traffic having a specific TID including the R-TWT TID, where two types of channel access, trigger-enabled channel access and non-trigger-enabled channel access, are provided, thereby identifying the R-TWT SP as either a trigger-enabled R-TWT SP or a non-trigger-enabled R-TWT SP, respectively.

[0073] The negotiated R-TWT TID includes an R-TWT uplink (UL) TID, an R-TWT downlink (DL) TID, and an R-TWT peer-to-peer (P2P) TID, and is established based on a stream classification service (SCS) traffic stream indicated by a quality of service (QoS) characteristic element of a (single or multiple) SCS traffic stream, for any prior implementation device or method.

[0074] The established R-TWT P2P TID follows the TID-link mapping of the corresponding SCS traffic stream, for any prior implementation device or method.

[0075] When at least one of the following conditions is met: (a) the SCS traffic streams have the same delay bound and / or MSDU lifetime within the QoS characteristic elements; (b) the differentiated service code point (DSCP) range of TID / UP is set to zero; (c) only one TID within an access category (AC) is used as the R-TWT TID, or both TIDs within the same AC need to be used as the R-TWT TID; and (d) the P2P SCS traffic streams have the same TID-link mapping within their QoS characteristic elements, multiple SCS traffic streams are mapped to the same TID, in any previous implementation of a device or method.

[0076] The R-TWT schedule-side AP cannot schedule an R-TWT SP time of an R-TWT TID that exceeds the media time requirement of the SCS traffic stream of the R-TWT TID as determined by: (a) when the R-TWT TID has multiple SCS traffic streams, the media time is the total media time of all SCS traffic streams of the R-TWT TID; (b) when the TID is the R-TWT TID of multiple R-TWTs, the R-TWT time is the total R-TWT SP time of these R-TWTs; (c) when the media time of the SCS traffic stream is calculated for the required transmission time over a specific bandwidth, the schedule-side AP reduces the channel time allocation for the transmission of the SCS traffic stream when the bandwidth is wider than the specific bandwidth, in any previous implementation of a device or method.

[0077] In a non-trigger-enabled R-TWT SP, the R-TWT member STAs of the non-trigger-enabled R-TWT SP operate as TXOP owners to ensure that the TXOP ends before the start of any SP of the R-TWT except for the primary AC of the TXOP mapped to any of the R-TWT TIDs of the non-trigger-enabled R-TWT SP, in any previous implementation of a device or method.

[0078] In the case where the primary AC of the TXOP cannot be mapped to any R-TWT TID, the R-TWT member STA can continue with the TXOP, as in any prior implementation of an apparatus or method.

[0079] The R-TWT member STA shares a TXOP to transmit frames of the R-TWT TID after the start of the R-TWT SP, as in any prior implementation of an apparatus or method.

[0080] The R-TWT member STA checks whether it has enough time to complete the transmission of a frame including a claim response before the start of the next R-TWT SP. If there is not enough time, the R-TWT member STA does not perform the transmission and resumes backoff using the contention window (CW) of the AC and the QoS short retry counter (QSRC) of the non-changed AC, as in any prior implementation of an apparatus or method.

[0081] In a trigger-enabled R-TWT SP, the R-TWT member STA, which is the TXOP owner, ensures that it shares the TXOP with the R-TWT schedule-side AP before the start of any R-TWT SP, or ensures that the TXOP ends before the start of any R-TWT SP. In this case, (a) the member STA can transmit a frame including a reverse direction grant (RDG) set to indicate that the schedule-side AP shares its TXOP, and when the AP receives a frame including the RDG, it can operate as the TXOP owner in the frame period or the network allocation vector (NAV) field to extend the TXOP; (b) the member STA transmits a frame to share the TXOP with the AP even if the transmission of the frame is not expected to be completed by the start of the R-TWT SP, as in any prior implementation of an apparatus or method.

[0082] The R-TWT schedule side AP, which is the TXOP owner in the R-TWT SP, is a device or method of any previous implementation that transmits frames of any R-TWT TID in the R-TWT SP as frames from the primary AC during the TXOP.

[0083] The AP uses the Extended Distributed Channel Access Function (EDCAF) of any AC to obtain a TXOP in the R-TWT SP, or the AP uses only the EDCAF of the R-TWT (DL) TID of the R-TWT SP to obtain a TXOP in the R-TWT SP, which is a device or method of any previous implementation.

[0084] The R-TWT member STA or the R-TWT schedule side STA is a device or method of any previous implementation that transmits frames with a TID that is not the R-TWT TID of any R-TWT outside the R-TWT SP.

[0085] The member STA is a device or method of any previous implementation that does not transmit frames of the R-TWT TID of the R-TWT outside the R-TWT SP.

[0086] The R-TWT schedule side STA ignores the R-TWT schedule when the R-TWT schedule side STA enabled with Emergency Preparedness Communication Service (EPCS) priority access (a) continues its TXOP beyond the start point of any R-TWT SP and does not need to end its TXOP before the start point of any R-TWT SP, and (b) the R-TWT schedule side STA that is the TXOP owner transmitting EPCS traffic ignores overlapping quiet intervals in the R-TWT SP, which is a device or method of any previous implementation.

[0087] The R-TWT schedule STA identifies the Emergency Preparedness Communication Service (EPCS) priority access as an SCS traffic stream, which is a device or method of any previous implementation.

[0088] An apparatus or method of any previous implementation in which an EPCS traffic sub-field indicating that the SCS traffic stream is EPCS traffic is added to the QoS characteristic element.

[0089] An apparatus or method of any previous implementation in which when the EPCS traffic sub-field is set to a first state, the SCS traffic stream under the QoS characteristic element is EPCS traffic, otherwise the field is set to a second state and the SCS traffic stream under the QoS characteristic element is not regarded as EPCS traffic.

[0090] An R-TWT member STA uses EDCA parameters to compete for a channel for an R-TWT TID or delay-sensitive traffic during an R-TWT SP even if it uses multi-user (MU) EDCA parameters to compete for a channel before the start of the R-TWT SP and the MU EDCA timer has not expired at the start of the R-TWT SP.

[0091] A member STA continues to use multi-user (MU) EDCA parameters immediately after finishing transmission during an R-TWT SP or immediately after the R-TWT SP ends, and the member STA continues to count down the MU EDCA timer that was paused at the start of the R-TWT SP as long as the MU EDCA timer is not updated during that period.

[0092] An apparatus or method of any previous implementation in which the member STA resets to zero the multi-user (MU) EDCA timer for the R-TWT upload (UL) TID or the AC of delay-sensitive traffic at the start of the R-TWT SP.

[0093] A device or method of any prior implementation in which a non-R-TWT schedule side STA that is not a member STA of the R-TWT uses multi-user (MU) EDCA parameters to request a channel and compete during the SP of the R-TWT.

[0094] A device or method of any prior implementation in which a member STA of the R-TWT uses multi-user (MU) EDCA parameters to request a channel and compete for a channel for non-R-TWT TID or traffic not affected by delay during the SP of the R-TWT.

[0095] A device or method of any prior implementation in which the non-R-TWT schedule side STA does not use DIFS access and / or AIFS access to request a channel and compete at the start of the R-TWT SP.

[0096] A device or method of any prior implementation in which the non-R-TWT schedule side STA does not use DIFS access or AIFS access during the R-TWT SP.

[0097] A device or method of any prior implementation in which the non-R-TWT schedule side STA does not use DIFS access or AIFS access during the first x hours of the R-TWT SP, where x represents time in seconds, milliseconds, or microseconds.

[0098] A device or method of any prior implementation in which the non-R-TWT schedule side STA uses a backoff procedure to request a channel and compete, selects a backoff count and decrements it, and the STA cannot select a backoff count equal to zero.

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

[0100] As used herein, the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. A reference to an item in the singular is not meant to mean "only one" unless specifically stated as such, but rather "one or more."

[0101] Expressions such as "A, B, and / or C" in the present disclosure represent that any of A, B, or C, or any combination of items A, B, and C, may exist. Expressions indicating a group of elements listed after "at least one of" indicate that at least one of these listed elements exists, including any possible combination of these listed elements when applicable.

[0102] References to "an embodiment," "at least one embodiment," or similar phrases in the present disclosure indicate that a particular feature, structure, or characteristic described in connection with the described embodiment is included in at least one embodiment of the present disclosure. Thus, these various embodiments' expressions do not necessarily all mean the same embodiment or a particular embodiment different from all other described embodiments. The expression "embodiment" should be construed to mean that a particular feature, structure, or characteristic of a given embodiment can be combined in any suitable form in one or more embodiments of the disclosed device, system, or method.

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

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

[0105] The terms “comprises,” “comprising,” “has,” “having,” “includes,” “including,” “contains,” “containing,” or any other variation of these terms are intended to include non-exclusive inclusion, so that a process, method, article, apparatus, or system 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 inherent to such process, method, article, apparatus, or system. Elements following “comprises … a,” “has … a,” “includes … a,” or “contains … a” are not excluded from the further existence of additional identical elements in the process, method, article, apparatus, or system that comprises, has, or includes such element without further limitation.

[0106] The terms "approximately", "approximate", "substantially", "essentially", and "about", or any variations thereof, as used in this specification, are used for the description and explanation of minor variations. When these terms are used in relation to an event or situation, they can mean that the event or situation will definitely occur, and when the probability of these events or situations occurring is very high. When these terms are used in relation to a numerical value, they 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 that numerical value. For example, "substantially" aligned can mean an angular variation range of ±10° or less, such as ±5° or less, ±4° or less, ±3° or less, ±2° or less, ±1° or less, ±0.5° or less, ±0.1° or less, or ±0.05° or less.

[0107] Also, in this specification, quantities, ratios, and other numerical values may be presented in range form. Such range form is used for convenience and simplicity, and includes the numerical values clearly specified as the limits of the range. However, it should be understood flexibly that all individual numerical values or sub - ranges included in this range are also included as if each of these numerical values and sub - ranges were clearly indicated. For example, a ratio within the range of about 1 to about 200 includes the clearly listed limit values of about 1 and about 200, but should also be understood to include individual ratios such as about 2, about 3, about 4, etc., and sub - ranges such as about 10 to about 50, about 20 to about 100, etc.

[0108] The term "coupled", as used in this specification, is defined as "connected", but is not necessarily a direct mechanical connection. A device or structure "configured" in a particular form is configured at least in that form, but can also be configured in forms not listed.

[0109] Advantages, merits, problem-solving means, and any (single or plural) elements that give rise to or make more prominent any of the advantages, merits, or problem-solving means should not be construed as important, necessary, or essential features or elements of the technology described in this specification or of some or all of the claims.

[0110] Also, in the above disclosure, various features can be grouped together in various embodiments for the purpose of rationalizing the disclosure. The method of the present disclosure should not be construed as reflecting an intention that the embodiments described in the claims require more features than those explicitly described in each claim. The subject matter of the present invention can be achieved by fewer than all the features of a single disclosed embodiment.

[0111] The abstract of the present disclosure is presented with the understanding that it is provided to enable a reader to quickly ascertain the essence of the technical disclosure and is not to be used to interpret or limit the scope of the claims or their meaning.

[0112] Depending on the jurisdiction, it should be understood that there is also a practice of seeking deletion of one or more portions of the present disclosure after filing. Accordingly, the reader should refer to the application as of the filing date with respect to the original content of the present disclosure. Any deletion of the disclosed content should not be construed as a waiver, forfeiture, or dedication to the public of any subject matter of the application as of the original filing.

[0113] The following claims are incorporated into the present disclosure with each claim standing on its own as a separate inventive subject matter.

[0114] Although the description in this specification includes many details, these should not be construed as limiting the scope of the present disclosure, but merely as exemplifying a part of the presently preferred embodiments. Accordingly, the scope of the present disclosure will be understood to fully encompass other embodiments that will become apparent to those skilled in the art.

[0115] Structural and functional equivalents of elements of the embodiments of the present disclosure that are well-known to those skilled in the art are also expressly incorporated herein by reference and are intended to be included within the scope of the claims. Further, elements, components, or method steps of the present disclosure are not intended to be generally disclosed, whether or not they are expressly recited in the claims. With respect to the elements of the claims herein, they should not be construed as "means-plus-function" elements unless the element is expressly recited using the phrase "means for". Also, with respect to the elements of the claims herein, they should not be construed as "step-plus-function" elements unless the element is expressly recited using the phrase "step for".

Description of Reference Numerals

[0116] Embodiment of R-TWT prioritization for 210 AP STA Is there a scheduled R-TWT for 212 R-TWT member STA? 214 The scheduled R-TWT SP cannot exceed the QoS requirements established during the SCS procedure for the corresponding R-TWT TID Is 216 AP the TXOP owner? 218 AP can transmit traffic for any R-TWT TID during the R-TWT SP or obtain a TXOP using the EDCAF of any AC 220 AP can continue the shared TXOP from the R-TWT member STA at the start of the R-TWT SP and act as the TXOP owner

Claims

1. An apparatus for wireless communication in a network, (a) A normal non-access point (AP) STA or an access point (AP) STA that operates as an independent wireless station (STA) or an STA within a multi-link device (MLD) and executes the transmission of frames between the media access control (MAC) layers of the IEEE 802.11 network, where extended distributed channel access (EDCA) is used for random channel access on all links, or trigger-based (TB) channel access is used for trigger-based uplink transmission on all links, and communicates wirelessly with other wireless stations (STAs) using a carrier sense multiple access / collision avoidance (CSMA / CA) mechanism on a wireless local area network (WLAN), (b) A processor coupled to the wireless communication circuit and operating on the WLAN, (c) A non-transitory memory storing instructions executable by the processor for communicating with other STAs, comprising, (d) When the instructions are executed by the processor, when prioritizing the transmission for setting a restricted target weight time (R-TWT) traffic identifier (TID) during R-TWT membership negotiation, (i) Negotiating the R-TWT service period (SP) between the R-TWT scheduled side STA and the R-TWT scheduled side AP to become an R-TWT member STA of the R-TWT SP, (ii) Prioritizing the R-TWT SP as negotiated for the transmission of low-latency traffic having a specific TID, where two types of channel access, trigger-enabled channel access and non-trigger-enabled channel access, are provided, thereby identifying the R-TWT SP as either a trigger-enabled R-TWT SP or a non-trigger-enabled R-TWT SP, including steps of a wireless communication protocol for the wireless communication circuit, An apparatus characterized by the above.

2. The negotiated R-TWT TIDs include R-TWT uplink (UL) TIDs, R-TWT downlink (DL) TIDs, and R-TWT peer-to-peer (P2P) TIDs, and are established based on a stream classification service (SCS) traffic stream shown in the quality of service (QoS) characteristic elements of a (single or multiple) SCS traffic stream. The apparatus according to claim 1.

3. The established R-TWT P2P TID follows the TID-link mapping of the corresponding SCS traffic stream. The apparatus according to claim 2.

4. (a) The SCS traffic stream has the same delay bound and / or MSDU lifetime within the QoS characteristic elements. (b) The differentiated service code point (DSCP) range of TID / UP is set to zero. (c) Only one TID within the access category (AC) is used as the R-TWT TID, or both TIDs within the same AC need to be used as the R-TWT TID. And (d) The P2P SCS traffic stream has the same TID-link mapping within its QoS characteristic elements. When at least one of the following conditions is met, multiple SCS traffic streams are mapped to the same TID. The apparatus according to claim 2.

5. The R-TWT schedule side AP (a) When the R-TWT TID has multiple SCS traffic streams, the media time is the total media time of all SCS traffic streams of the R-TWT TID. (b) When the TID is the R-TWT TID of multiple R-TWTs, the R-TWT time is the total R-TWT SP time of these R-TWTs. (c) When the media time of the SCS traffic stream is calculated for the required transmission time over a specific bandwidth, the schedule side AP reduces the channel time allocation for the transmission of the SCS traffic stream when the bandwidth is wider than the specific bandwidth. It is not possible to schedule the R-TWT SP time of the R-TWT TID that exceeds the media time requirement of the SCS traffic stream of the R-TWT TID as determined by the above. The apparatus according to claim 4.

6. In a non-trigger-enabled R-TWT SP, the R-TWT member STA of the non-trigger-enabled R-TWT SP operates as a TXOP owner and guarantees that the TXOP ends before the start of any SP of the R-TWT excluding the primary AC of the TXOP mapped to any of the R-TWT TIDs of the non-trigger-enabled R-TWT SP. The apparatus according to claim 1.

7. If the primary AC of the TXOP cannot be mapped to any R-TWT TID, the R-TWT member STA can continue its TXOP. The apparatus according to claim 6.

8. The R-TWT member STA shares the TXOP to transmit a frame of the R-TWT TID after the start of the R-TWT SP. The apparatus according to claim 7.

9. The R-TWT member STA checks whether it has enough time to complete the transmission of a frame including a request response before the start of the next R-TWT SP. If there is not enough time, the R-TWT member STA does not perform the transmission and resumes the backoff using the contention window (CW) of the AC and the QoS short retry counter (QSRC) of the unchanged AC. The apparatus according to claim 6.

10. In a trigger-enabled R-TWT SP, the R-TWT member STA that is the TXOP owner guarantees to share the TXOP with the R-TWT schedule-side AP before the start of any R-TWT SP, or guarantees that the TXOP ends before the start of any R-TWT SP. In this case, (a) The member STA can transmit a frame including a reverse direction grant (RDG) set to indicate that the schedule-side AP shares its TXOP. When the AP receives a frame including the RDG, it can extend the TXOP by operating as the TXOP owner in the frame period or the network allocation vector (NAV) field. (b) The member STA transmits a frame to share the TXOP with the AP even if the transmission of the frame is not expected to be completed by the start of the R-TWT SP. The apparatus according to claim 1.

11. The R-TWT schedule side AP, which is the TXOP owner in the R-TWT SP, transmits the frame of any R-TWT TID in the R-TWT SP as the frame from the primary AC in the TXOP. The apparatus according to claim 1.

12. The AP uses the extended distributed channel access function (EDCAF) of any AC to obtain a TXOP in the R-TWT SP, or the AP uses only the EDCAF of the R-TWT (DL) TID of the R-TWT SP to obtain a TXOP in the R-TWT SP. The apparatus according to claim 11.

13. The R-TWT member STA or the R-TWT schedule side STA transmits a frame with a TID that is not the R-TWT TID of any R-TWT outside the R-TWT SP. The apparatus according to claim 1.

14. The member STA does not transmit a frame with the R-TWT TID of the R-TWT outside the SP of the R-TWT. The apparatus according to claim 1.

15. The R-TWT schedule side STA is the case where the emergency preparedness communication service (EPCS) priority access is enabled. (a) When the R-TWT schedule side STA, which is the TXOP owner transmitting EPCS traffic, continues its TXOP beyond the start point of any R-TWT SP and does not need to end its TXOP before the start point of any R-TWT SP, and (b) When the R-TWT schedule side STA, which is the TXOP owner transmitting EPCS traffic, ignores the overlapping quiet intervals in the R-TWT SP. Ignores the R-TWT schedule. The apparatus according to claim 1.

16. The R-TWT schedule STA identifies the emergency preparedness communication service (EPCS) priority access as an SCS traffic stream. The apparatus according to claim 15.

17. An EPCS traffic subfield indicating that the SCS traffic stream is EPCS traffic is added to the QoS characteristic element. The apparatus according to claim 16.

18. When the EPCS traffic subfield is set to the first state, the SCS traffic stream under the QoS characteristic element is EPCS traffic; otherwise, the field is set to the second state and the SCS traffic stream under the QoS characteristic element is not regarded as EPCS traffic. The apparatus according to claim 17.

19. Even if the R-TWT member STA uses the multi-user (MU) EDCA parameters to request and compete for a channel before the start of the R-TWT SP in order to compete for a channel, and the MU EDCA timer has not expired at the start of the R-TWT SP, the R-TWT member STA uses the EDCA parameters to request and compete for a channel for the R-TWT TID or delay-sensitive traffic during the R-TWT SP. The apparatus according to claim 1.

20. Immediately after the member STA finishes transmitting during the R-TWT SP, or immediately after the R-TWT SP ends, the member STA continues to use the multi-user (MU) EDCA parameters. The member STA continues to count down the MU EDCA timer that was paused at the start of the R-TWT SP as long as the MU EDCA timer is not updated during that period. The apparatus according to claim 19.

21. The member STA resets the multi-user (MU) EDCA timer to zero for the R-TWT upload (UL) TID or the AC of delay-sensitive traffic at the start of the R-TWT SP. The apparatus according to claim 19.

22. The STA on the R-TWT schedule side that is not an R-TWT member STA uses the multi-user (MU) EDCA parameters to request and compete for a channel during the SP of the R-TWT. The apparatus according to claim 1.

23. The R-TWT member STA uses the multi-user (MU) EDCA parameters to request and compete for a channel for non-R-TWT TID or traffic not affected by delay during the SP of the R-TWT. The apparatus according to claim 1.

24. The STA on the R-TWT schedule side does not use DIFS access and / or AIFS access to request and compete for a channel at the start of the R-TWT SP. The apparatus according to claim 1.

25. The STA on the R-TWT schedule side does not use DIFS access or AIFS access during the R-TWT SP. The apparatus according to claim 24. **Claim 26** The STA on the R-TWT schedule side does not use DIFS access or AIFS access during the first x hours of the R-TWT SP, where x represents time in units of seconds, milliseconds, or microseconds. The apparatus according to claim 24. **Claim 27** The STA on the R-TWT schedule side uses a backoff procedure to compete for a channel, selects a backoff count and decrements it, and the STA cannot select a backoff count equal to zero. The apparatus according to claim 24. **Claim 28** A method for performing wireless communication in a network, (a) Performing transmission of frames between the medium access control (MAC) layers of an IEEE 802.11 network as a STA that is an independent wireless station (STA) or a STA within a multi-link device (MLD), and using an extended distributed channel access (EDCA) for random channel access on all links, or using a trigger-based (TB) channel access for trigger-based (TB) uplink transmission on all links, and operating as either a normal non-access point (AP) STA or an access point (AP) STA that communicates wirelessly with other wireless stations (STAs) using a carrier sense multiple access / collision avoidance (CSMA / CA) mechanism on a wireless local area network (WLAN); (b) Negotiating the R-TWT SP between the STA on the R-TWT schedule side and the R-TWT schedule side AP to become an R-TWT member STA of the R-TWT SP; (c) In the R-TWT, prioritizing the transmission of low-latency traffic having a specific TID including the R-TWT TID, where two types of channel access, namely trigger-enabled channel access and non-trigger-enabled channel access, are provided, thereby identifying the R-TWT SP as either a trigger-enabled R-TWT SP or a non-trigger-enabled R-TWT SP respectively; characterized by including the above.

Images