Operation and Parameters of Restricted Target Wake Time (R-TWT)

Abstract

A wireless protocol implementing restricted target wake time (R-TWT) signaling and its parameters to reduce latency for real-time application traffic and the like. During an R-TWT service period (SP), R-TWT operation (modes) are described that enhance operation by providing additional traffic flow control including whether the R-TWT SP can be extended, whether multiple overlapping R-TWT SPs on different links can be initiated, whether spatial reuse is required during the R-TWT SP, whether transmissions outside the R-TWT SP are permitted, or whether a quiet element is used to protect the R-TWT SP. The protocol is applicable to wireless local area networks (WLANs) and is particularly suited for real-time application (RTA) traffic such as over 802.11be 802.11ax, as well as time-sensitive networks, Wi-Fi, and multi-link devices (MLDs).

Description

Technical Field

[0001] [Cross - Reference to Related Applications] This application claims priority and the benefit thereof to U.S. Patent Application Serial No. 17 / 679,798, filed on February 24, 2022, which is hereby incorporated by reference in its entirety. This application claims priority and the benefit thereof to U.S. Provisional Patent Application Serial No. 63 / 211,683, filed on June 17, 2021, which is hereby incorporated by reference in its entirety. This application claims priority and the benefit thereof to U.S. Provisional Patent Application Serial No. 63 / 192,656, filed on May 25, 2021, which is hereby incorporated by reference in its entirety.

[0002] [Description of Research or Development Sponsored by the Federal Government] Not applicable

[0003] [Notice of Materials Subject to Copyright Protection] Some of the materials in this patent document may be subject to copyright protection under the copyright laws of the United States of America and other countries. The copyright owners do not object to the reproduction of the patent document or patent disclosure by third parties as represented in the public files or records of the United States Patent and Trademark Office, but reserve all copyrights otherwise. The copyright owners do not hereby waive any rights to keep this patent document confidential, including, but not limited to, the rights under 37 C.F.R. § 1.14.

[0004] The technology of this disclosure generally relates to the use of Target Wake Time (TWT) in a WLAN station, and specifically to the Reserved TWT mode for enhanced TWT use and the setting of its various parameters.

Background Art

[0005] The Target Wake Time (TWT) was first introduced with 802.11ah and has evolved up to 802.11ax. The purpose of TWT is to enable a device to determine when and how to wake up for data transmission and reception. For example, in 802.11ax, an access point can increase the sleep time of a device to save battery life. This aspect is particularly beneficial in roles such as the Internet of Things (IoT). TWT also provides a mechanism that allows a wireless access point and similar devices to negotiate a specific time to access the medium, thus assisting in spectral efficiency.

Summary of the Invention

Problems to be Solved by the Invention

[0006] However, TWT is mainly aimed at power saving and does not particularly address reducing real-time latency.

[0007] Therefore, there is a need to enhance the handling of TWT. This disclosure meets this need and provides further advantages.

Means for Solving the Problems

[0008] A method of performing Restricted Target Wake Time (R-TWT) signaling transmitted by using bits within a broadcast TWT parameter set field defined as preliminary under IEEE802.11ax for R-TWT parameter settings. R-TWT is particularly beneficial for use with traffic from stations that operate in a low-power configuration and wake up for data transmission and reception, especially for real-time application traffic or other latency-sensitive traffic.

[0009] In addition to indicating that the R-TWT should be executed, additional parameters for specifying the traffic flow that can be transmitted during the R-TWT service period (SP) are also described, including parameters indicating whether the R-TWT SP can be extended, parameters indicating whether multiple overlapping R-TWT SPs on different links can be started, parameters indicating whether spatial reuse is required during the R-TWT SP, and parameters indicating whether a Quiet element should be used to protect the R-TWT SP. Accordingly, the selection of the R-TWT operation (mode) is also described, along with the enhanced operations and their associated parameters.

[0010] In particular, the disclosed technology describes the use of spare bits within the broadcast TWT parameter set field to establish R-TWT parameter settings. For example, spare bits 5-7 of the broadcast TWT recommended subfield and bit 15 (B15) of the request type field of the broadcast TWT parameter set field are used for R-TWT parameter settings. Some of these additional parameters that enhance R-TWT signaling are also described.

[0011] This disclosure is applicable to wireless local area networks (WLANs) and is particularly suitable for real-time application (RTA) traffic (or traffic sensitive to delay), such as 802.11be, 802.11ax, and time-dependent networks, Wi-Fi, and on multi-link devices (MLDs).

[0012] In the following sections 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.

[0013] The technology described herein will be fully understood by reference to the following drawings, which are for illustrative purposes only.

Brief Description of the Drawings

[0014]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

DETAILED DESCRIPTION OF THE INVENTION

[0015] 1. Introduction The broadcast TWT (B-TWT) signaling defined in IEEE802.11ax can also be adapted to support restricted TWT (R-TWT) signaling. By using a specific value (e.g., 4) of the broadcast TWT recommended subfield in the broadcast TWT parameter set field, it can be indicated that the signaling is for R-TWT defined in draft P802.11be D1.31.

[0016] B-TWT enables an AP, such as a TWT schedule side AP, to schedule a TWT service period (SP) for exchanging frames with other stations (STAs) that are STAs on the TWT schedule side (or members of the TWT). An individual STA can have membership within the broadcast TWT as a result of negotiation with the schedule side AP. The STA on the TWT schedule side should not transmit frames to the schedule side AP outside the broadcast TWT SP, except when it can transmit frames within the negotiated individual TWT SP as defined in 26.8.2 (e.g., individual TWT agreement) according to draft P802.11ax_D8.0. Also, frames not included in the high-efficiency (HE) trigger-based (TB) PPDU within the trigger-enabled broadcast TWT SPs should not be transmitted to the schedule side AP.

[0017] The R-TWT SP can be scheduled and notified in the same way as the B-TWT SP. If the signaling is for the R-TWT, the TWT SP within this signaling is scheduled for the R-TWT. Otherwise, the TWT SP within the signaling is scheduled for the B-TWT.

[0018] This disclosure provides enhanced R-TWT signaling as described in the following sections.

[0019] 2. Embodiments The use of enhanced R-TWT can be implemented in various 802.11 hardware configurations shown as an example and not limited to the following.

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

[0021] Bus 14 can connect various devices such as sensors and actuators to the CPU. On processor 18, instructions from memory 20 are executed to run a program that implements 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 APs, coordinator, coordinatee, AP within OBSS, and STA within OBSS, etc.) depending on what role it is playing in the current communication situation.

[0022] Accordingly, the illustrated STA HW is composed of at least one modem and associated RF circuitry for providing communication on at least one band. This disclosure is mainly targeted at the sub-6 GHz band.

[0023] It should be understood that this 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 used 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 circuit includes a frequency converter and an array antenna controller, etc., and is connected to a plurality of antennas that are controlled to perform beamforming for transmission and reception. In this way, the STA can transmit signals using a set of multiple beam patterns where each beam pattern direction is considered an antenna sector.

[0024] Also, multiple instances of local hardware as shown can be combined into a Multi-Link Device (MLD). Usually, this MLD has a processor and memory to coordinate activities, but it is not necessarily the case that each STA within the MLD requires a separate CPU and memory.

[0025] Figure 2 shows an example embodiment 40 of the hardware configuration of a Multi-Link Device (MLD). A plurality of STAs belong to the MLD, and each STA operates on a link with a different frequency. The MLD has external I / O access to an application, and this access is connected to an MLD management entity 48 having a CPU 62 and a memory (e.g., RAM) 64, enabling the execution of a (single or multiple) program that implements a communication protocol at the MLD level. The MLD can distribute tasks to each of the connected local stations exemplified here as STA1 42, STA2 44 to STA N46 and collect information from them, and share information among the belonging STAs.

[0026] In at least one embodiment, each STA of the MLD has its own CPU 50 and memory (RAM) 52, which are coupled through 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 a plurality of antennas 60a, 60b, 60c to 60n in the form of an antenna array. The modem combined with the RF circuit and the associated (single or multiple) antennas transmits / receives data frames to / from neighboring STAs. In at least one implementation, the RF module includes a frequency converter, an array antenna controller, and other circuits for interacting with its antenna.

[0027] It should be understood that each STA of the MLD can share resources with each other and / or with the MLD management entity depending on a specific MLD implementation, and thus does not necessarily require its own processor and memory. Note that the above MLD diagram is shown as an example and not a limitation, and it should be understood that the present disclosure can operate with a wide range of MLD implementations.

[0028] 2.2 Data fields of the TWT Figure 3 shows an exemplary embodiment 110 of the broadcast TWT parameter set field. The illustrated field is the Request Type, Target Wake Time, Nominal Minimum TWT Wake Duration, TWT Wake Interval Mantissa, and Broadcast TWT Information as described in IEEE 802.11ax (Draft P802.11ax_D8.0).

[0029] Figure 4 shows an exemplary embodiment 130 of the Broadcast TWT Information (Info) subfield. The illustrated field is Reserved, Broadcast TWT ID (identification), and Broadcast TWT Persistence.

[0030] Figure 5 shows an exemplary embodiment 150 of the Request Type field of the broadcast TWT parameter set field. The illustrated field is the TWT Request, TWT Setup Command, Trigger, Last Broadcast Parameter Set, Flow Type, Broadcast TWT Recommendation, TWT Wake Interval Exponent, and Reserved field.

[0031] 3. Description of the problem The broadcast TWT recommended subfield indicates the instruction of the R-TWT. However, in order to provide the enhanced R-TWT operation as disclosed in this specification, it is necessary to determine what parameter settings should be included in the B-TWT signaling for the R-TWT. The following is a list of some parameter setting candidates for the R-TWT. (a) During the R-TWT SP, parameters specifying the traffic flow can be transmitted. (i) The traffic flow can be identified by the SCS ID, Traffic Identifier (TID), Real-Time Application (RTA) ID, or User Priority (UP). Note that the RTA ID can be an ID representing one or more low-latency traffic streams. (ii) The R-TWT signaling frame can also convey a TSPEC element specifying that only the traffic under the traffic specification (TSPEC) element during the R-TWT signaling can be transmitted into the R-TWT SP. In the stream classification service (SCS), the stream can be arbitrarily mapped to a primary queue and an alternate queue. (b) A parameter indicating whether the R-TWT SP can be extended. For example, the R-TWT SP may not start at the scheduled start time. If the R-TWT SP starts late, the R-TWT SP can be extended after its scheduled end time. (c) A parameter indicating that multiple overlapping R-TWT SPs on different links can be started. There are two options for scheduling multiple overlapping R-TWT SPs on different links. In the first option, only one of these scheduled overlapping R-TWT SPs can be started, and the other R-TWT SPs are canceled. In the second option, multiple of these scheduled overlapping R-TWT SPs can be started. (d) A parameter indicating whether spatial reuse is required in the R-TWT SP. For example, this parameter can require the scheduling side AP of the R-TWT to use a Parameterized Spatial Reuse Transmission (PSRT) or Parameterized Spatial Reuse Reception (PSRR) Physical Layer Convergence Procedure (PLCP) Protocol Data Unit (PPDU) defined in IEEE802.11ax for spatial reuse. (e) A parameter indicating whether a quiet element should be used to protect the R-TWT SP. In the R-TWT SP, the scheduling side AP can schedule a quiet interval to prevent channel contention from STAs that are not members of the R-TWT SP. These STAs can enter the quiet mode in the R-TWT SP after receiving a quiet element command from the scheduling side AP.

[0032] 4.0. Objectives of the present disclosure The disclosure of this R-TWT has the following objectives. (a) Setting the R-TWT parameter settings using the reserved bits of the broadcast TWT parameter set field in FIG. 5. For example, setting the request type field within the broadcast TWT parameter set field. In the broadcast TWT recommended subfield, while the values of bits 5-7 of this field are reserved, B15 of the broadcast TWT parameter set field is also reserved. (b) Bits B0 - B2 are reserved in the broadcast TWT information subfield of FIG. 4. (c) Implementing enhanced R-TWT operations.

[0033] 5.0. Embodiments 5.1. Reserved bit options for representing the R-TWT set Figure 6 shows an example embodiment 170 of an option where each spare bit represents an R-TWT setting. Note that the definition of each spare bit for R-TWT signaling is predetermined within the protocol. In this flowchart, the protocol should select either Option 1 or Option 2. This flowchart represents that the STA can set the parameters within the broadcast TWT parameter set field for R-TWT signaling. The STA can be the TWT schedule side AP or an individual STA.

[0034] Specifically, this flowchart shows that the STA reuses (172) the broadcast TWT parameter set field for R-TWT signaling and selects (174) either Option 1 or Option 2. In the case of Option 1, the STA sets the most significant bit of the broadcast TWT recommendation subfield to a first state (e.g., "1") to indicate that this signaling is for R-TWT and also sets the other bits for R-TWT parameter setting (176). Then, in block 180, the STA uses the other spare bits within the broadcast TWT parameter set field for R-TWT parameter setting.

[0035] On the other hand, if the STA decides to use Option 2 in block 174, it sets the broadcast TWT recommendation subfield to a value of 4 or more to indicate that this signaling is for a different type of R-TWT (178), and then reaches block 180 as described above.

[0036] Figure 7 shows an example embodiment 190 where the STA identifies whether the received broadcast TWT parameter set field indicates R-TWT signaling when using Option 1 of Figure 6. Note that it should be understood that the STA can be the TWT schedule side AP or an individual STA.

[0037] Specifically, this flowchart shows that the STA receives a broadcast TWT parameter set field (192), and then performs a check 194 to determine whether the most significant bit of the broadcast TWT recommendation subfield is set to a first state (e.g., "1").

[0038] If the bit is not set to the first state, it reaches block 200, which is the broadcast TWT parameter set field in B-TWT signaling.

[0039] On the other hand, if the bit is in the first state, the execution proceeds from check 194 to block 196, where it is recognized that the broadcast TWT parameter set field is set for R-TWT signaling. Thereafter, the STA uses the parameter settings found within the broadcast TWT parameter set field for R-TWT (198).

[0040] FIG. 8 shows an example embodiment 210 in which the STA identifies whether the received broadcast TWT parameter set field indicates R-TWT signaling when using Option 2 of FIG. 6.

[0041] This flowchart describes how the STA identifies whether the received broadcast TWT parameter set field is for R-TWT signaling when using Option 2 of FIG. 6. It should be understood that the STA can be the TWT schedule side AP or an individual STA.

[0042] Specifically, this flowchart shows that the STA receives the broadcast TWT parameter set field (212) and checks the broadcast TWT recommended subfield (214) to determine whether the value is equal to or greater than a set value of "4" in terms of compatibility with the existing subfield value. If the value is less than this set value, it is determined that B-TWT signaling is to be executed (220).

[0043] On the other hand, if the values match in block 214 (in this case, equal to or greater than the set value of 4), the execution reaches block 216, and it is determined that the broadcast TWT parameter set field indicates the execution of R-TWT signaling. As a result, the STA uses the parameter settings within the broadcast TWT parameter set field for R-TWT in block 218.

[0044] 5.2. Option 1 where each spare bit represents an R-TWT set FIG. 9 shows an example of option 1 where each spare bit represents an R-TWT set, and an embodiment example 230 of the request type field within the broadcast TWT recommended subfield.

[0045] The request type field within the broadcast TWT parameter set field includes only B7 to B15. If this field is for R-TWT signaling, particularly for R-TWT negotiation, additional bits for R-TWT parameter settings can be added either within the request type field or at any location within the broadcast TWT parameter set field. Note that the position of each bit parameter can be changed.

[0046] In bit 9 (B9) (or the most significant bit) of the request type field within the broadcast TWT parameter set field, there is an R-TWT indication subfield. The R-TWT indication provides a 1-bit indication indicating whether the signaling is for R-TWT or for B-TWT. For example, when the R-TWT indication is set to a first state (e.g., "1"), it indicates that the signaling is for R-TWT rather than B-TWT. Accordingly, the TWT SP in this signaling is scheduled for R-TWT SP. Otherwise, the value of the broadcast TWT recommendation field is 0 to 3 for broadcast TWT signaling, and the TWT SP in this signaling is scheduled for B-TWT SP.

[0047] For other spare bits within the broadcast TWT parameter set field, when the signaling is for R-TWT, each bit can be used to set a parameter set for R-TWT. Each optional bit can only be set by the scheduling side AP, and other STAs need to follow the settings by the scheduling side AP when transmitting the broadcast TWT parameter set for the same R-TWT.

[0048] Alternatively, in at least one embodiment, it is also possible to negotiate each optional bit between only the scheduling side AP and the STA that requests membership in R-TWT. The scheduling side AP broadcasts the setting of this optional bit to other members after negotiation, or reserves this optional bit when broadcasting the setting.

[0049] For example, the Overlapped R-TWT field on the ML in FIG. 9 is set when the STA requests R-TWT membership, but is otherwise reserved (not used) when the schedule-side AP broadcasts the broadcast TWT parameter set. When this option bit is reserved during broadcast by the schedule-side AP, this bit option is valid only between the schedule-side AP and the R-TWT member STA (or the scheduled STA) that negotiates this option. When this option bit is set during broadcast by the schedule-side AP, this bit option is also valid for all member STAs of the corresponding R-TWT. Note that the following descriptions of each option can represent the default operation of R-TWT even if these options are not parameters set in the broadcast TWT parameter set field. For example, since the R-TWT SP can always be extended by default, the extend R-TWT SP field can be a parameter not set in the broadcast TWT parameter set field.

[0050] Note that each of the following options can be any (single or multiple) bit in the broadcast TWT parameter setting field (including additional bits added to the broadcast TWT parameter setting field for R-TWT parameter setting).

[0051] (1) Quiet element protection: This 1-bit indicates whether a quiet interval is scheduled to protect the R-TWT SP. This subfield is set to a first state (e.g., "1") to indicate that the scheduling side AP schedules a quiet interval using a quiet element to protect the R-TWT SP. The STA that receives this bit (or a member STA of the R-TWT SP only) can ignore the quiet interval scheduled during the R-TWT SP. Otherwise, this subfield is set to a second state (e.g., "0"), and no quiet interval is scheduled to protect the R-TWT SP.

[0052] (2) ALL SCS (or all traffic streams (TS)): This 1-bit indicates whether traffic belonging to all SCSs (or TSs) is permitted to be transmitted during the R-TWT SP. This field is set to a first state (e.g., "1") if permitted, or to a second state (e.g., "0") if not permitted, so that only traffic belonging to the specified SCS (or TS) can be transmitted during the R-TWT SP. In at least one embodiment, SCS (or TS) configuration information (such as SCSID, TID, TSPEC element, or QoS characteristic element) can be included in a TWT signaling frame such as a TWT request / response frame.

[0053] (3) Extend R-TWT SP: This subfield can consist of a 1-bit indication. When this bit is set to a first state (e.g., "1"), a member of the R-TWT (or the scheduling side AP only) can extend the R-TWT SP, for example, if the R-TWT SP did not start as scheduled, or if the members of the R-TWT could not access the channel at the scheduled start time of the R-TWT SP.

[0054] In this case, the scheduling side AP or the member STA can reserve a TXOP during the R-TWT SP that exceeds the originally scheduled R-TWT SP end time. Note that in at least one embodiment, the extended R-TWT SP time is restricted so as not to be longer than the transmission opportunity (TXOP) limit. Also, in at least one embodiment, the TXOP time obtained by the R-TWT members (including the scheduling side AP) during the R-TWT SP is also restricted so as not to be longer than the scheduled R-TWT SP time. In at least one embodiment, the R-TWT can be trigger-based, and only the AP can extend the R-TWT SP. Otherwise, this bit is set to a second state (e.g., "0"), and the R-TWT SP cannot be extended. The R-TWT SP needs to end at the scheduled end time, and the TXOP reserved by the R-TWT members (including the scheduling side AP) during the R-TWT SP cannot exceed the originally scheduled end time of the R-TWT SP. In at least one embodiment, if there is another R-TWT SP scheduled immediately after the current R-TWT SP, the range of the R-TWT SP subfield of the current R-TWT SP should be set to a second state (e.g., "0"). In at least one embodiment, the scheduling side AP makes the decision to set this subfield.

[0055] In some embodiments, the R-TWT SP can be extended only in the case of DL transmission of any member STA of the R-TWT SP that competes for a channel outside the R-TWT SP and / or UL / P2P transmission of the member STA of the R-TWT SP.

[0056] (4) Target Wake-up required: This subfield can be implemented with a 1-bit indication. When this bit is set to the first state (e.g., "1"), the members of the R-TWT perform wake-up and sleep according to the broadcast TWT. For example, a member STA of the R-TWT wakes up during the R-TWT SP and sleeps outside the R-TWT SP. Otherwise, this bit is set to the second state (e.g., "0"), and the member STA of the R-TWT always remains awake. As a result, the scheduling side AP can perform DL transmissions (and / or trigger UL / P2P transmissions) to the member STA outside the R-TWT SP. Note that the R-TWT SP is scheduled and notified in the same way as the B-TWT SP.

[0057] (5) Duplicate R-TWTs on ML: This 1-bit indication can be set to indicate whether the scheduling side AP MLD and the same R-TWT MLD members can start multiple duplicate R-TWT SPs on different links. When this bit is set to the first state (e.g., "1"), the AP and the R-TWT members can start multiple R-TWT SPs on different links. In at least one embodiment, it may not be possible to use a quiet interval to protect the R-TWT SP. Otherwise, this bit is set to the second state (e.g., "0"), and the AP and the R-TWT members can only start one R-TWT SP on one link even if multiple duplicate R-TWT SPs are scheduled on different links.

[0058] (6) PSRR: This 1-bit indication can be used to indicate whether the AP needs to send a PSRR PPDU to trigger a UL transmission. When this bit is set to the first state (e.g., "1"), the AP is configured to send a PSRR PPDU to trigger a UL transmission (PSRT PPDU) during the R-TWT SP. That is, the AP cannot set the spatial reuse field in the uplink (UL) spatial reuse subfield within the common information field of the trigger frame (PSRR PPDU) to PSR_DISALLOW or PSR_AND_NON-SRG_OBSS_PD_PROHIBITED to disable the execution of parameterized spatial reuse (PSR)-based SR transmission by the OBSS STA. The spatial reuse value of the solicited TB PPSU should follow the PSRR PPDU. When an Overlapping Basic Service Set (OBSS) STA receives this bit, it recognizes the existence of a spatial reuse parameter (SRP) during the R-TWT SP.

[0059] Otherwise, this bit is set to the second state (e.g., "0"), and the AP does not send a PSRR PPDU when triggering a UL transmission. When the AP broadcasts this option, the OBSS STA that receives this option can access the channel during a parameterized spatial reuse (PSR) opportunity, and the intra-Basic Service Set (BSS) STA can refrain from requesting membership in the R-TWT if it does not support PSR-based SR. The intra-BSS STA can also request a change to this option when requesting membership.

[0060] (7) SR Enable: This 1-bit indication can be used to indicate whether spatial reuse is permitted within the R-TWT SP. When this bit is set to the first state (e.g., "1"), the AP and members of the R-TWT can (or must) perform spatial reuse operations within the R-TWT SP, such as OBSS preamble detection (PD)-based spatial reuse and PSR-based spatial reuse defined in IEEE 802.11ax. The spatial reuse operations within the R-TWT SP can be the same as those outside the R-TWT SP. Otherwise, this bit is set to the second state (e.g., "0"), and the scheduling-side AP and members of the R-TWT cannot perform spatial reuse operations within the R-TWT SP. When the AP broadcasts this option, the OBSS STAs that receive this option can access the channel during spatial reuse (PSR) opportunities, and the STAs within the BSS can refrain from requesting membership in the R-TWT if they do not support SR. The STAs within the BSS can also request a change in this option when requesting membership.

[0061] (8) TWT protection: This bit is similar to the TWT protection request type field within the individual TWT parameter set field.

[0062] (9) All TID: This 1-bit indication is set to indicate whether traffic belonging to all TIDs can be transmitted in the R-TWT SP. This field is set to the first state (e.g., "1") if traffic belonging to all TIDs (in some cases only low-latency traffic) can be transmitted in the R-TWT SP. A STA that is a member of the R-TWT can transmit traffic belonging to all TIDs (in some cases only low-latency traffic) to be transmitted into the R-TWT SP. Otherwise, this subfield is set to the second state (e.g., "0"), and only traffic belonging to the specified TID (in some cases only low-latency traffic) can be transmitted into the R-TWT SP. Traffic information can be included in a TWT signaling frame such as a TWT request / response frame.

[0063] (10) Link ID Bitmap Present: This 1-bit indication can be used to indicate whether a Link ID Bitmap field exists within the Broadcast TWT Parameter Set field. When this bit is set to the first state (e.g., "1"), the R-TWT signaling is for multi-link R-TWT, and a Link ID Bitmap field exists within the Broadcast TWT Parameter Set field. The R-TWT SP should be scheduled on the links indicated in the Link ID Bitmap field. Otherwise, this bit is set to the second state (e.g., "0"), and no Link ID Bitmap field exists within the Broadcast TWT Parameter Set field. The R-TWT signaling is for only the link on which the signaling is transmitted.

[0064] (11) R-TWT External Transmission Allowance: This field is set to a first state (e.g., "1") to indicate that a member STA of the R-TWT can compete (i.e., transmit a frame) for channel access rights outside the R-TWT SP. In a TWT request frame, this bit (set to "1") can also indicate that an individual STA seeking membership in the R-TWT needs to (or is scheduled to) transmit (and / or receive) a frame outside the R-TWT SP. In a TWT response frame, this bit (set to "1") can also indicate that the R-TWT schedule-side AP is scheduled to be able to schedule UL (and / or DL and / or P2P) transmissions of member STAs of the R-TWT. Otherwise, this bit is set to a second state (e.g., "0") to indicate that a member STA of the R-TWT cannot (or should not) compete for channel access rights outside the R-TWT SP (in some cases, transmit and receive). In a TWT request frame, this bit (set to "0") can also indicate that an individual STA seeking membership in the R-TWT does not transmit (and / or receive) a frame outside the R-TWT SP. In a TWT response frame, this bit (set to "0") can also indicate that the R-TWT schedule-side AP does not schedule UL (and / or DL and / or P2P) transmissions of member STAs of the R-TWT.

[0065] Set this bit in the TWT request frame to indicate that each individual STA needs to (or is scheduled to) transmit (and / or receive) frames outside the R-TWT SP. When the TWT request is accepted, the R-TWT schedule-side AP can schedule (or trigger) the UL (and / or DL and / or P2P) transmissions of each individual STA only within the scheduled R-TWT SP. For example, if the R-TWT SP is extended after the scheduled end time, the R-TWT schedule-side AP will not schedule the UL (and / or DL and / or P2P) transmissions of each individual STA. That is, the R-TWT SP will not be extended for the UL (and / or DL, and / or P2P) transmissions of each individual STA that is a member of the R-TWT SP. Set this bit in the TWT request frame to indicate that each individual STA will not transmit (and / or receive) frames outside the R-TWT SP. When the TWT request is accepted, the R-TWT schedule-side AP can extend the R-TWT SP for the UL (and / or DL and / or P2P) transmissions of each individual STA that is a member of the R-TWT SP.

[0066] The figure shows an example where B7 is used for all SCS sub-fields, B8 is used for the quiet element protection sub-field, and B15 is used for the duplicate R-TWT sub-field on the ML. Each spare bit can be used for any R-TWT parameter set option. For example, the all SCS sub-field of B7 can also be replaced with the all TID sub-field. Note that additional bits can be added to the request type field within the broadcast TWT parameter set field for R-TWT if this is for R-TWT signaling. For example, as shown in the figure, the PSRR field, SR enable field, TWT protection field, all TID field, link ID bitmap presence field, R-TWT external transmission permission field exist in additional bits for R-TWT parameter settings. Also, it should be understood that these additional bits can exist in any location within the broadcast TWT parameter set field for R-TWT parameter settings.

[0067] 5.3. Example of Use of Spare Bits in Broadcast TWT Information FIG. 10 shows an example embodiment 250 of using spare bits within the broadcast TWT information field. As shown in this example, when B-TWT signaling is used for R-TWT, the spare bits B0 to B2 within the broadcast TWT information field can be used for R-TWT information. Note that the spare bits can be used for any of the fields shown in FIG. 9.

[0068] (1) All SCS: This 1-bit indication is set to indicate whether to permit the transmission of traffic belonging to all SCSs during the R-TWT SP. When this field is set to the first state (e.g., "1"), it permits the transmission of traffic belonging to all SCSs during the R-TWT SP, and the STA that is a member of the R-TWT can transmit traffic belonging to all SCSs during the R-TWT SP. Otherwise, this subfield is set to the second state (e.g., "0"), and only traffic belonging to the specified SCS can be transmitted during the R-TWT SP. TWT signaling frames such as TWT request / response frames can include SCS configuration information (e.g., SCS ID field, TSPEC element (or QoS characteristic element), TCLAS element, traffic classification (TCLAS) processing element, priority element within the access category). The SCS configuration information can be used to set the SCS for which traffic should be transmitted during the R-TWT SP. In this example, when the all SCS field is set to the second state (e.g., "0"), traffic from the SCS indicated in the SCS ID field can be transmitted during the R-TWT SP.

[0069] (2) AC: When this field is set to AC, traffic having a priority higher than AC indicated in the AC field can be transmitted during the R-TWT SP. For example, let the value of AC_BK be 0, the value of AC_BE be 1, the value of AC_VI be 2, and the value of AC_VO be 3. Since AC_VO and AC_VI have a higher priority than AC_BE, when this field is set to 1, traffic of AC_VO, AC_VI, and AC_BE can be transmitted during the R-TWT SP. In some cases, only traffic of the AC indicated in the AC field can be transmitted during the R-TWT SP.

[0070] (3) When broadcast TWT information is used for R-TWT, the broadcast TWT ID represents the R-TWT ID. Note that the scheduling side AP or STA should not set the same ID for both R-TWT and broadcast TWT at the same time. In this way, the AP or STA can distinguish between the broadcast TWT and the R-TWT by their IDs.

[0071] (4) The AC subfield can be conveyed by any two of the other spare bits within the broadcast TWT parameter set field.

[0072] 5.4. Example of Setting All SCS to Zero FIG. 11 shows Embodiment Example 290 in which all SCS are set so as not to be permitted (e.g., "0"). The broadcast TWT information field is shown at the top of the figure, and the broadcast TWT parameter set field is shown at the bottom of the figure.

[0073] (1) When the all SCS field is set to "0" (the second state), traffic information such as the SCS ID, TSPEC (or QoS characteristic element), and TID for each traffic stream (i.e., for each traffic stream) can be included in the broadcast TWT parameter set field within the TWT signaling frame such as the TWT setting (request / response) frame. Note that the all SCS field can be replaced with any field that can indicate the presence of traffic information. In at least one embodiment, for example, when the SCS ID, TID, and TSPEC field (or QoS characteristic element) are transmitted by a non-AP STA to request membership in the R-TWT, these fields can exist by default. The traffic information can be included in any location within the TWT signaling frame such as the TWT setting (request / response) frame.

[0074] (2) If traffic information exists within the broadcast TWT parameter set field of the broadcast TWT setup frame transmitted by a non-AP STA to request membership in an R-TWT, this traffic information specifies that traffic belonging to the traffic stream (between the non-AP STA and the scheduling AP) indicated by the traffic information needs to be transmitted within the R-TWT SP. When receiving this information, the scheduling AP can determine whether to accept the membership request based on this information. The following are two examples where the scheduling AP does not accept the membership request depending on the content found within the traffic information.

[0075] (a) In at least one embodiment, if the total time required to transmit the traffic of all traffic streams indicated in the broadcast TWT parameter set field exceeds the time that can be scheduled for the R-TWT SP, the membership request is not accepted. For example, the total media time of the TSPEC elements of all traffic streams indicated in the broadcast TWT parameter set field is longer than the time permitted per second for the scheduled R-TWT SP.

[0076] (b) In at least one embodiment, if the total time required to transmit the traffic of all traffic streams indicated in the broadcast TWT parameter set field exceeds the upper limit of the total time of all R-TWT SPs that the scheduling side AP can schedule (or the scheduling side AP MLD can schedule on all links), the membership request is not accepted. In the network, there can be an upper limit to the total time of all R-TWT SPs that each scheduling side AP can schedule (or the scheduling side AP MLD can schedule on all links). For example, if the transmission time of all traffic streams indicated in the broadcast TWT parameter set field (e.g., the total of the medium times in the TSPEC elements of all traffic streams indicated in the broadcast TWT parameter set field is equal to 60 ms per second) exceeds the R-TWT SP time where the total time of all R-TWT SPs of the scheduling side AP (or the scheduling side AP MLD) exceeds the upper limit value (upper limit value = 5 ms per beacon interval (e.g., 0.1 s), or approximately 5 ms / 0.1 s = 50 ms / s < 60 ms / s), and the scheduling side AP is required to schedule this R-TWT SP time, the scheduling side AP can reject the membership request.

[0077] (3) If traffic information exists in the broadcast TWT parameter set field of the broadcast TWT setting frame transmitted by the scheduling side AP to accept the membership request of the R-TWT, this traffic information can represent the traffic that can be transmitted during the scheduled R-TWT SP (transmitted between the non-AP STA and the scheduling side AP), while other traffic (transmitted between the non-AP STA and the scheduling side AP) cannot be transmitted during the R-TWT SP or can have a lower priority (compared to the traffic indicated in the traffic information).

[0078] (4) If traffic information exists in the broadcast TWT parameter set field of the broadcast TWT setting frame transmitted by the schedule side AP to respond to the membership request of the R-TWT, and the TWT setting command field in the response frame is Alternate TWT or Dictate TWT, this traffic information can represent the traffic proposed to be transmitted in the R-TWT SP (transmitted between the non-AP STA and the schedule side AP). The non-AP STA can send another request frame containing the proposed traffic information to request membership in the R-TWT.

[0079] (5) More SCS / TID: When this field is set to the first state (e.g., "1"), it indicates that there is additional traffic information such as SCS ID, TSPEC, and TID for another traffic stream. Otherwise, this bit is set to the second state (e.g., "0").

[0080] (6) Traffic information can be used for traffic identification, such as distinguishing traffic that is sensitive to delay under SCS or TSPEC from other traffic.

[0081] (7) Note that the schedule side AP MLD is an MLD that has multiple schedules belonging to different links. One traffic stream such as SCS can be mapped to only one R-TWT of the schedule side AP MLD, or can be mapped to only one R-TWT of the schedule side AP on one link. For example, one SCS can be mapped to only one R-TWT. That is, if the traffic of the SCS is permitted to be transmitted by the R-TWT in its R-TWT SP, other R-TWTs should not accept the traffic transmission request of that SCS in its R-TWT SP.

[0082] 5.5. Setting Example of Existence of Link ID Bitmap FIG. 12 shows an example embodiment 310 indicating the existence of a link ID bitmap. At the top of the figure, a request type field in the broadcast TWT parameter set field of the R-TWT is shown, and at the bottom of the figure, the broadcast TWT parameter set field is shown.

[0083] Signaling is used for the R-TWT. When the existence of the link ID bitmap in the signaling is set to the first state (e.g., "1"), a link ID bitmap exists in the broadcast TWT parameter set field.

[0084] As shown in the figure, B15 of the request type field in the broadcast TWT parameter set field of the R-TWT is used to convey the link ID bitmap existence subfield. Any spare bit in the broadcast TWT parameter set field can operate in the same manner as B15 of the request type field in the broadcast TWT parameter set field.

[0085] Link ID Bitmap: This field consists of a series of bits where each bit is pre-set or mapped to a link. When a bit is set to the first state (e.g., "1"), the R-TWT is set for the link related to that bit. Otherwise, the bit is set to the second state (e.g., "0"), and the R-TWT is not set for the link related to that bit. Note that this is one possible method for scheduling duplicate R-TWT SPs on multiple links. Also, the link ID bitmap existence subfield can be used for broadcast TWT settings on multiple links. Note that multiple bits can be set to "1" in the link ID bitmap field.

[0086] 5.6. Option 2: Each Value Represents an R-TWT Option In Option 2, the bit values of bits 4 to 7 of the broadcast TWT recommendation field represent one R-TWT for which the default parameters are set.

[0087] By way of example and not limitation, each of the values from 4 to 7 can be set to represent one of the following R-TWT settings. - Basic R-TWT, or - R-TWT with quiet element or protection, or - R-TWT for only the specified SCS with quiet element or protection, or - R-TWT for only the specified SCS, or - Duplicate R-TWT on the ML, or - Duplicate R-TWT on the ML for only the specified SCS, or - R-TWT that does not require a target wakeup, or - R-TWT where the constraints on the frames transmitted in the R-TWT SP are similar to values 0 to 3.

[0088] In this example, for instance, value 4 represents the basic R-TWT. It should be understood that these values can be mapped in any desired order without departing from the teachings of the present disclosure.

[0089] 5.6. Duplicate R-TWT SP on Multiple Links FIG. 13 shows an example embodiment 330 of executing a duplicate R-TWT SP on multiple links. The duplicate R-TWTs on different links are R-TWTs managed by the schedule-side AP MLD, and the R-TWT SPs on those different links are scheduled over the same period. Note that the duplicate R-TWTs can represent only those that serve the same TID or the same SCS or traffic stream or the same MLD member.

[0090] Specifically, this operation indicates that multiple overlapping R-TWT SPs on different links are scheduled for the same R-TWT member over the same period (332).

[0091] In check 334, it is determined whether overlapping R-TWTs on multiple links are permitted. As an example, check 334 can include checking whether the ML subfield is set to a first state (e.g., "1") indicating that overlapping R-TWTs on the ML are permitted, and if the overlapping R-TWTs on the ML subfield are set to a second state (e.g., "0"), the overlapping R-TWTs on the ML are not permitted.

[0092] If overlapping R-TWTs on multiple links are not permitted, in block 338, if the process determines that one R-TWT SP is started on one link, other overlapping R-TWT SPs on other links scheduled over the same period are cancelled.

[0093] On the other hand, if overlapping R-TWTs on multiple links are permitted, in block 336, if the process determines that one R-TWT SP is started on one link, other overlapping R-TWT SPs on other links scheduled over the same period can also be started.

[0094] 5.7. Example of overlapping R-TWTs on the ML FIG. 14 shows an embodiment example 350 of a first example of overlapping R-TWTs on the ML (overlapping R-TWTs on the ML = 0).

[0095] This figure shows an MLD 352 including an AP1 354 and an AP2 356.

[0096] There are multiple overlapping R-TWT SPs, such as R-TWT SP1 358 and SP2 360, scheduled on different links, such as link 1 and link 2. The overlapping R-TWT fields on the ML are set to 0 for the overlapping R-TWT SPs. The MLD member starts R-TWT SP2 366 on link 2 (364).

[0097] All MLDs operating on link 1 and link 2 can confirm that R-TWT SP2 has started on link 2 by detecting a frame indicating the start of R-TWT SP2, for example. Thus, since the overlapping R-TWT fields on the ML = 0, R-TWT SP1 on link 1 recognizes that it is canceled (362). As a result, all MLDs (or only MLDs that are not R-TWT members) can compete for the channel on link 1 during R-TWT SP1. If a quiet interval is scheduled in the R-TWT SP on link 1, the STA operating on link 1 can ignore the quiet interval.

[0098] AP2 or the R-TWT SP2 member can send a frame indicating the start of R-TWT SP2. For example, this frame can be a Clear-to-Send (CTS) frame having a special Receiver Address (RA) field indicating the start of R-TWT SP2. The RA field of the frame (e.g., CTS) can be set to a special ID for the link that can be mapped to the R-TWT ID and / or STA ID and / or BSS ID. In at least one embodiment or mode, the RA field of the frame can be set to the address of AP2. Other stations (nodes) can determine the start of R-TWT SP2 scheduled by AP2.

[0099] FIG. 15 shows an embodiment example 370 of a second example of overlapping R-TWTs on the ML (overlapping R-TWTs on the ML = 0). This figure shows communication between an MLD 352 including AP1 354 and AP2 356 and another MLD 396 that is not a member of the R-TWT, including associated local STAs STA1 398 and STA2 400.

[0100] Here, a plurality of overlapping R-TWT SPs exemplified as R-TWT SP1 372 and SP2 374 are scheduled on different links shown as Link 1 and Link 2. The overlapping R-TWT field on the ML is set to 0 for the overlapping R-TWT SPs. The MLD member starts R-TWT SP2 380 on Link 2.

[0101] All MLDs operating on Link 1 and Link 2 confirm that R-TWT SP2 has been started on Link 2, such as by detecting a frame indicating the start of R-TWT SP2. Thus, since the overlapping R-TWT field on the ML = 0, it is recognized that R-TWT SP1 on Link 1 is canceled (376).

[0102] As a result, all MLDs (or only MLDs that are not R-TWT members) can compete for the channel on Link 1 during R-TWT SP1. If a quiet interval is scheduled during R-TWT SP on Link 1, these MLDs operating on Link 1 can ignore the quiet interval.

[0103] The AP2 or R-TWT SP2 member can send a frame indicating the start of R-TWT SP2. This frame can be a CTS frame with a special RA indicating the start of R-TWT SP2. The RA field of the frame (e.g., CTS) can be set to a special ID for the link that can be mapped to the R-TWT ID and / or STA ID and / or BSS ID. The RA field of the frame can also be set to the address of AP2. Other nodes can recognize the start of R-TWT SP2 scheduled by AP2.

[0104] An AP (e.g., AP1) belonging to the same MLD of the R-TWT SP2 member on Link 1 can access the channel on Link 1 only for the following purposes until the R-TWT on Link 2 ends. The scheduling AP can access the channel to send a frame such as a QoS Data frame or a QoS Null frame having an EOSP subfield equal to 1 indicating the end of R-TWT SP1 because R-TWT SP1 is canceled. The AP can access the channel to provide services to R-TWT members including MLDs that are not R-TWT members on Link 2. The AP can access the channel to send a frame (e.g., CF-End) indicating the end of the R-TWT or the end of the quiet time on Link 1 as shown in FIG. 384. The TA field of the frame (e.g., CF-End) can be set to a special ID for the link that can be mapped to the R-TWT ID and / or STA ID and / or BSS ID.

[0105] The AP can access the channel to transmit DL traffic (or DL traffic that is not permitted to be transmitted only during the R-TWT SP) to the associated STA, or to trigger UL traffic (or UL traffic that is not permitted to be transmitted only during the R-TWT SP). The AP can access the channel to transmit control frames or management frames. As an example, the figure shows a PPDU 386 transmitted from AP1 to STA1 via Link 1, and a subsequent block acknowledgment (BA) 388 from the STA. It also shows that a trigger frame (TF) 390 is transmitted from AP1 to STA1, in response to which a trigger-based (TB) PPDU 392 is transmitted from STA1 to AP1, and then a BA 394 is transmitted from AP1.

[0106] In at least one embodiment, an R-TWT member can classify an event by indicating the end / termination of the R-TWT SP in the same manner as in the case of B-TWT in IEEE 802.11ax.

[0107] FIG. 16 shows an example embodiment 410 of a third example of overlapping R-TWTs on the ML (overlapping R-TWTs on the ML = 0). This figure shows an MLD 352 including AP1 354 and AP2 356.

[0108] For example, there are multiple overlapping R-TWT SPs shown as R-TWT SP1 358 and SP2 360, scheduled for the same MLD member on different links shown as Link 1 and Link 2. The overlapping R-TWT fields on the ML are set to 0 for the overlapping R-TWT SPs. The MLD member starts the R-TWT SP2 366 on Link 2 (364).

[0109] All MLDs operating on Link 1 and Link 2 can confirm that R-TWT SP2 has started on Link 2, such as by receiving a frame indicating the start of R-TWT SP2. Since the overlapping R-TWT field on the ML = 0, it is recognized that R-TWT SP1 on Link 1 is canceled (362). As a result, all MLDs (or only MLDs that are not R-TWT members) can compete for the channel on Link 1 during R-TWT SP1. If a quiet interval is scheduled during R-TWT SP on Link 1, these MLDs operating on Link 1 can ignore the quiet interval.

[0110] STAs belonging to the same MLD that is an R-TWT member on Link 1 may not be able to access the channel on Link 1 until R-TWT SP2 on Link 2 ends. R-TWT SP2 on Link 2 may end earlier than scheduled. AP2 or other R-TWT SP2 members can send a frame, such as a Contention Free (CF)-End like in the previous example, to indicate the end of R-TWT SP2. Also, a frame (e.g., CF end) can indicate the end of the quiet interval on Link 2.

[0111] An AP (e.g., AP1) belonging to the same MLD of the R-TWT SP2 member on Link 1 can access the channel on Link 1 only for the following purposes until the R-TWT SP on Link 1 (or Link 2) ends. The AP can access the channel to provide services to R-TWT members including MLDs that are not R-TWT members on Link 2. The AP can access the channel to transmit a frame (e.g., CF end) indicating the end of the R-TWT SP or the end of the quiet time on Link 1. The TA field of the frame (e.g., CF end) can be set to a special ID for the link that can be mapped to the R-TWT ID and / or STA ID and / or BSS ID. The AP can access the channel to transmit downlink (DL) traffic (or DL traffic that is not permitted to be transmitted only during the R-TWT SP) to the associated STA, or to trigger uplink (UL) traffic (or UL traffic that is not permitted to be transmitted only during the R-TWT SP). The AP can access the channel to transmit a control frame or a management frame.

[0112] FIG. 17 shows an embodiment example 450 of a fourth example of overlapping R-TWTs on the ML. In this example, a maximum of two overlapping R-TWT SPs are permitted on different links over the same period. The figure shows an MLD 452 including AP1 454, AP2 456, and AP3 458.

[0113] The figure shows overlapping R-TWTs with ML = 1, and R-TWT SPs 1, 460, SP2 462, and SP3 464 are scheduled. In this example, only a limited number of overlapping R-TWT SPs can be started on different links. In this example, a maximum of two overlapping R-TWT SPs can be started (or activated) on different links during the same R-TWT SP period. This example can function only when the trigger subfield of the request type field in the broadcast TWT parameter set field = 1.

[0114] It can be seen that when AP2 starts R-TWT SP2 on Link 2 and then AP3 starts R-TWT SP3 on Link 3, R-TWT SP1 is cancelled.

[0115] FIG. 18 shows an example embodiment 490 of extending R-TWT SP. In this figure, an example of extending R-TWT SP is shown when the R-TWT SP extension (Extend R-TWT SP) subfield is set to a first state (e.g., "1") indicating that the R-TWT SP is extended. In the figure, an AP or STA has a scheduled R-TWT SP494, which can be extended (500) for a period of time 1 502 only. The AP or other R-TWT members can start (496) the R-TWT SP (e.g., the time to acquire channel access rights and obtain a TXOP) for a period of time 2 498 until the R-TWT SP ends (504). The present disclosure can provide numerous options for R-TWT SP extension.

[0116] The following options for restricting R-TWT SP extension are shown as an example and not by way of limitation. Option 1: Time 1 should not be longer than the TXOP limit. Option 2: Time 1 should not be longer than a given percentage (e.g., 50%) of the TXOP limit period. Option 3: Time 2 should not be longer than the TXOP limit. Option 4: Time 2 should not be longer than a given percentage (e.g., 50%) of the TXOP limit. Option 5: Time 2 should not be longer than the scheduled R-TWT SP time. Option 6: Time 1 should not exceed the next target beacon transmission time. Option 7: An AP or STA that is a member of an R-TWT SP may acquire a TXOP during a scheduled R-TWT SP and extend the R-TWT SP if the TXOP continues beyond the end time of the scheduled R-TWT SP. The R-TWT SP is extended until the end time of the TXOP. Option 8: An AP or STA that is a member of an R-TWT SP may start a PPDU transmission during a scheduled R-TWT SP and extend the R-TWT SP if the PPDU period and the response-type transmission extend beyond the end time of the scheduled R-TWT SP. The R-TWT SP is extended until the end time of this PPDU transmission and its response-type transmission.

[0117] The TXOP limit can be the TXOP limit of the AC that acquires the TXOP. The TXOP limit can also be the TXOP limit of the AC with the highest priority TID having traffic scheduled to be transmitted during the R-TWT SP. The TXOP limit can also be the maximum TXOP limit of the TIDs having traffic scheduled to be transmitted during the R-TWT. The TXOP limit can be a value set only for the R-TWT SP.

[0118] FIG. 19 shows an embodiment example 510 where R-TWT extension is not permitted. This example shows a situation where R-TWT SP extension is not permitted, for example, when the R-TWT SP extension subfield is set to a second state (e.g., "0") indicating that extension is not permitted.

[0119] It can be seen that the AP or STA 512 has a scheduled R-TWT SP 514. The AP2 or another R-TWT member accesses the channel up to the maximum TXOP length 518 (516).

[0120] As shown in the figure, the R-TWT SP cannot be extended. When accessing the channel during the R-TWT SP, the R-TWT member cannot reserve a TXOP beyond the end time 520 of the R-TWT SP.

[0121] Figure 20 shows an example embodiment 530 of setting the PSRR to allow the PSRR to be set to a first state (e.g., "1"). AP1 should always set the parameters within the PSRR PPDU to allow the PSR.

[0122] It shows that AP1 532 and AP2 534 have an R-TWT SP on link 1 536, and AP1 accesses the channel to start the R-TWT SPT538 with the PSRR PPDU540. This figure also illustrates that the TB PPDU542 is received, and during this time, AP2 transmits the PSRT PPDU544, and a block acknowledgment response 546 is shown for this.

[0123] In this example, AP1 cannot set the spatial reuse field within the UL spatial reuse subfield of the common information field of the trigger frame (PSRR PPDU) to PSR_DISALLOW or PSR_AND_NON-SRG_OBSS_PD_PROHIBITED to disable the execution of PSR-based SR transmission by the OBSS STA. The spatial reuse value of the response-type TB PPSU should follow the PSRR PPDU.

[0124] 5.8. Scheduling Quiet Time Using Quiet Elements In at least one implementation or mode, a quiet element is used to schedule a quiet time to protect the R-TWT SP within the R-TWT SP. The quiet interval should not exceed the R-TWT SP time. The end of this quiet time should be aligned with the end time of the R-TWT SP (and / or the start time of the quiet time should be aligned with the start time of the R-TWT SP).

[0125] When an R-TWT SP member accesses a channel for the purpose of R-TWT within the R-TWT SP, it can transmit a frame (e.g., CF end) to cancel the quiet time scheduled during the quiet time.

[0126] If the R-TWT SP ends earlier than scheduled, it can transmit a frame (e.g., CF end) to cancel the quiet time scheduled during the current R-TWT SP.

[0127] FIG. 21 shows Embodiment Example 550 of a first example using a quiet element where the end time of the quiet interval coincides with the end time of the R-TWT SP.

[0128] This figure shows AP1 552 on Link 1, STA1 554 which is a member of the R-TWT on Link 1, and STA2 556 which is not a member of the R-TWT on Link 1.

[0129] Also shown is R-TWT SP558 on Link 1 where AP1 560 accesses the channel to start an R-TWT SP on Link 1. On Link 1, a scheduled quiet time interval 562 is started and STA2 enters the quiet mode 564. The quiet time interval ends simultaneously with the end 566 of the R-TWT SP on Link 1, at which point STA2 ends the quiet mode (568).

[0130] FIG. 22 shows Embodiment Example 570 of a second example using a quiet element. This figure shows the same stations as in the previous example.

[0131] It shows that an R-TWT SP572 has occurred on Link 1 at the time when a quiet interval 574 is scheduled on Link 1 by the quiet element. In response, STA2 enters the quiet mode 576.

[0132] AP1 accesses the channel and starts R-TWT SP on Link 1 (578). The quiet time interval ends simultaneously with the end of R-TWT SP on Link 1 580, and STA2 ends the quiet mode (582).

[0133] 6. 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 that 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, a general-purpose computer or a dedicated computer, or any other programmable processing device for producing a machine, so that the computer program instructions executed on the computer processor or other programmable processing device can create means for implementing the specified function(s).

[0134] 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.

[0135] 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 in (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.

[0136] Furthermore, as used herein, the terms "program" or "program execution statement" will be understood to mean one or more instructions that can be executed by one or more computer processors to perform one or more of the 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 remotely, such as on a server, or a combination of local and remote storage of all or part of the instructions can be used. Remotely stored instructions can be downloaded (pushed) to the device automatically by a user's initiation or based on one or more factors.

[0137] 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 and multi-core devices, and variants thereof.

[0138] 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.

[0139] An apparatus for wireless communication in a network, comprising: (a) a wireless communication circuit that operates as a station (STA) that operates either as a normal wireless station (STA) or an access point (AP) STA, 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); (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; and (d) the instructions, when executed by the processor, (d)(i) reuse broadcast target wake time (B-TWT) signaling defined in IEEE 802.11ax for the establishment of restricted TWT (R-TWT); (d)(ii) indicate the use of R-TWT within the B-TWT using bits of a broadcast TWT parameter set field that is reserved in IEEE 802.11ax; and (d)(iii) indicate additional settings specifying a traffic flow for R-TWT in response to utilizing other bits within a broadcast TWT recommendation field that is reserved in IEEE 802.11ax, the apparatus performing one or more steps of a wireless communication protocol for the wireless communication circuit.

[0140] An apparatus for wireless communication in a network, comprising: (a) a wireless communication circuit that operates as either a normal wireless station (STA) or an STA operating as an access point (AP) STA, and wirelessly communicates with other wireless stations (STA) 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; (d) the instructions, when executed by the processor, (d)(i) reuse broadcast target wake time (B-TWT) signaling defined in IEEE 802.11ax for the establishment of restricted TWT (R-TWT); (d)(ii) use bits of a broadcast TWT parameter set field that is preliminary in IEEE 802.11ax to indicate the use of R-TWT within the B-TWT; (d)(iii) IEEE 802.In response to using other bits within the broadcast TWT recommendation field that are preliminary in 11ax, performing one or more steps of a wireless communication protocol for the wireless communication circuit, including indicating additional settings that specify a traffic flow for the R-TWT; (iv) one or more of the traffic flow settings include: (A) indicating whether a quiet element is used to protect the R-TWT; (B) indicating whether a restricted TWT can be extended beyond its scheduled end time if corresponding traffic is not being transmitted at the end of the R-TWT SP; (C) indicating whether the AP is forced to use PSR-based spatial reuse during a restricted TWT SP; (D) indicating whether the AP and R-TWT members can access multiple overlapping R-TWT SPs on different links over the same period; (E) indicating whether traffic from all SCSs is permitted to transmit during an R-TWT SP; (F) indicating whether members of the R-TWT need to start and sleep in response to a broadcast TWT; (G) indicating the amount of traffic information included in the broadcast TWT parameter set field, a device selected from a group of traffic flow settings.

[0141] A wireless communication method in a network, comprising: (a) a STA that executes a wireless communication protocol and operates as a normal wireless station (STA) or an access point (AP) STA wirelessly communicates with other wireless stations (STA) using a carrier sense multiple access / collision avoidance (CSMA / CA) mechanism on a wireless local area network (WLAN); (b) reusing broadcast target wake time (B-TWT) signaling defined in IEEE 802.11ax for the establishment of restricted TWT (R-TWT); (c) using bits in a broadcast TWT parameter set field that is reserved in IEEE 802.11ax to indicate the use of R-TWT within the B-TWT; and (d) indicating additional settings for specifying a traffic flow for R-TWT in response to using other bits within a broadcast TWT recommendation field that is reserved in IEEE 802.11ax.

[0142] An apparatus for wireless communication in a network, comprising: (a) a wireless communication circuit that operates as a STA that operates as either a normal wireless station (STA) or an access point (AP) STA and wirelessly communicates packets with other wireless stations (STA) using a carrier sense multiple access / collision avoidance (CSMA / CA) mechanism for use with a multi-link device (MLD) on a wireless local area network (WLAN); (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, perform one or more steps of a wireless communication protocol for the wireless communication circuit, including: (d)(i) the MLD schedules a plurality of overlapping R-TWT SPs; (d)(ii) if the number of overlapping R-TWT SPs started on a link has not reached the maximum number, start an R-TWT SP on another link; and (d)(iii) if the number of R-TWT SPs started on another link has reached the maximum number, cancel an R-TWT SP on a specific link.

[0143] An apparatus for wireless communication in a network, comprising: (a) a wireless communication circuit that operates as a station (STA) that operates either as a normal wireless station (STA) or an access point (AP) STA, and wirelessly communicates with other wireless stations (STA) 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; and (c) a non-transitory memory storing instructions executable by the processor for communicating with other STAs, wherein (d) the instructions, when executed by the processor, (d)(i) schedule a quiet interval by setting a restricted transmission window (R-TWT) such that an end time of the R-TWT coincides with an end time of the quiet interval; (d)(ii) cause a STA that is not a member of the R-TWT to enter a quiet mode during the quiet interval; and (d)(iii) not permit a STA that is a member of the R-TWT to enter a quiet mode during the quiet interval, and execute one or more steps of a wireless communication protocol for the wireless communication circuit.

[0144] An apparatus for wireless communication in a network, comprising: (a) a wireless communication circuit that operates as either a normal wireless station (STA) or an STA operating as an access point (AP) STA, 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); (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; and (d) the instructions, when executed by the processor, perform one or more steps of a wireless communication protocol for the wireless communication circuit, including: (d)(i) sending an R-TWT membership request including specific traffic information to be transmitted in the SP of the R-TWT to the associated AP; (d)(ii) the associated AP determining whether to accept the R-TWT membership request based on the specific traffic information; and (d)(iii) the associated AP using the specific traffic information to distinguish traffic that matches this specific traffic information from other traffic information.

[0145] An apparatus for wireless communication in a network, comprising: (a) a wireless communication circuit that operates as either a normal wireless station (STA) or an access point (AP) STA 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); (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, perform one or more steps of a wireless communication protocol for the wireless communication circuit, including: (d)(i) the AP schedules a start time of an R-TWT SP; (d)(ii) the AP and R-TWT members start the R-TWT SP as scheduled; and (d)(iii) if the AP and R-TWT members cannot start the R-TWT SP as scheduled, the AP and R-TWT members extend the R-TWT SP.

[0146] A wireless communication device that executes packet transmission, in a system / device, comprising: (a) the STA sets a restricted TWT by reusing broadcast TWT signaling defined in IEEE802.11ax; (b) the STA indicates in a broadcast TWT recommendation field within a reserved bit of a broadcast TWT parameter set field that the signaling is for the restricted TWT; and (c) the STA indicates an additional setting of the restricted TWT in the broadcast TWT recommendation field, wherein CSMA / CA is applied.

[0147] A wireless communication device that executes packet transmission, in a system / device, (a) the MLD schedules a plurality of overlapping R-TWT SPs; (b) when the number of overlapping R-TWT SPs started on a certain link does not reach the maximum number, R-TWT SPs can be started on other links (overlapping R-TWTs can represent only those that provide services to the same TID or the same SCS or traffic stream); (c) when the maximum number of R-TWT SPs is started on other links, cancel the R-TWT SPs on some links, and a device to which CSMA / CA including these is applied.

[0148] A wireless communication device that executes packet transmission, in a system / device, (a) the STA schedules the quiet interval by setting the R-TWT so that the end time of the R-TWT SP coincides with the end time of the quiet interval; (b) an STA that is not a member of the R-TWT enters the quiet mode during the quiet interval; (c) an STA that is a member of the R-TWT can be prevented from entering the quiet mode during the quiet interval, and a device to which CSMA / CA including these is applied.

[0149] A wireless communication device that executes packet transmission, in a system / device, (a) the STA transmits an R-TWT membership request including specific traffic information to be transmitted during the R-TWT SP to the AP; (b) the AP determines whether to accept the R-TWT membership request based on the specific traffic information; (c) the AP uses the specific traffic information to distinguish traffic that matches the specific traffic information from other traffic, and a device to which CSMA / CA including these is applied.

[0150] A wireless communication device that executes packet transmission, and in a system / device, (a) an AP schedules a start time of an R-TWT SP, (b) the AP and R-TWT members attempt to start the R-TWT SP as scheduled, and (c) the AP and R-TWT members extend the R-TWT SP if they cannot start the R-TWT SP as scheduled, and a CSMA / CA including the above is applied.

[0151] The device or method of any preceding implementation

[0152] The STA uses bit 9 (B9) of the request type field in the broadcast TWT parameter set field to indicate whether the broadcast TWT signaling is for restricted TWT (R-TWT), and the device or method of any preceding implementation.

[0153] The STA uses 1 bit between bit 7 (B7) and bit 8 (B8) or bit 15 (B15) of the request type field in the broadcast TWT parameter set field to indicate additional settings for restricted TWT, and the device or method of any preceding implementation.

[0154] The STA uses 1 bit between bit 7 (B7) and bit 8 (B8) or bit 15 (B15) of the request type field in the broadcast TWT parameter set field to indicate whether a quiet element is used to protect the R-TWT. The quiet element schedules a quiet interval to prevent channel contention from STAs that are not members of the R-TWT SP and enter the quiet mode during the R-TWT SP after receiving a quiet element command from the scheduling side AP, and the device or method of any preceding implementation.

[0155] The STA uses 1 bit between bit 7 (B7) and bit 8 (B8) or bit 15 (B15) of the request type field within the broadcast TWT parameter set field to indicate whether a restricted TWT can be extended beyond its scheduled end time when the corresponding traffic is not being transmitted at the end of the R-TWT SP, for any prior implementation's apparatus or method.

[0156] The STA uses 1 bit between bit 7 (B7) and bit 8 (B8) or bit 15 (B15) of the request type field within the broadcast TWT parameter set field to indicate whether the AP is forced to use PSR-based spatial reuse during the restricted TWT SP, for any prior implementation's apparatus or method.

[0157] The PSR-based spatial reuse includes a parameterized spatial reuse transmission (PSRT) or parameterized spatial reuse reception (PSRR) physical layer convergence procedure (PLCP) protocol data unit (PPDU) defined for spatial reuse in IEEE 802.11ax, for any prior implementation's apparatus or method.

[0158] The STA uses 1 bit between bit 7 (B7) and bit 8 (B8) or bit 15 (B15) of the request type field within the broadcast TWT parameter set field to indicate whether the AP and R-TWT members can access multiple overlapping R-TWT SPs on different links over the same period, for any prior implementation's apparatus or method.

[0159] Options for multiple overlapping R-TWT SPs are selected from a group of options consisting of (a) allowing only one scheduled overlapping R-TWT SP to be started and the others to be canceled, and (b) allowing multiple scheduled overlapping R-TWT SPs to be started, for any prior implementation's apparatus or method.

[0160] The STA uses one bit between bit 7 (B7) and bit 8 (B8) or bit 15 (B15) of the request type field in the broadcast TWT parameter set field to indicate whether traffic from all SCSs is permitted to transmit during the R-TWT SP, for any prior implementation's apparatus or method.

[0161] The STA uses one bit between bit 7 (B7) and bit 8 (B8) or bit 15 (B15) of the request type field in the broadcast TWT parameter set field to indicate whether members of the R-TWT need to start up and sleep as per the broadcast TWT, for any prior implementation's apparatus or method.

[0162] The STA uses one bit between bit 7 (B7) and bit 8 (B8) or bit 15 (B15) of the request type field in the broadcast TWT parameter set field to indicate the amount of traffic information included in the broadcast TWT parameter set field, for any prior implementation's apparatus or method.

[0163] The traffic information is selected from a group of traffic information consisting of a traffic specification (TSPEC), a stream classification service identifier (SCSID), and a traffic identifier (TID), for any prior implementation's apparatus or method.

[0164] The STA uses one bit between bit 7 (B7) and bit 8 (B8) or bit 15 (B15) of the request type field in the broadcast TWT parameter set field to indicate whether R-TWT members are permitted to perform channel contention outside the R-TWT SP, for any prior implementation's apparatus or method.

[0165] The STA uses bit 9 (B9) of the request type field within the broadcast TWT parameter set field to indicate whether the broadcast TWT signaling is for restricted TWT (R-TWT) in any prior implementation's apparatus or method.

[0166] Duplicate R-TWT can represent only those that serve the same TID, the same SCS, or traffic streams in any prior implementation's apparatus or method.

[0167] The R-TWT SP can end earlier than its scheduling in any prior implementation's apparatus or method.

[0168] The STA can send a frame indicating the start of the R-TWT SP in any prior implementation's apparatus or method.

[0169] A STA that is a member of a canceled R-TWT SP cannot access the channel until the R-TWT SP on another link ends in any prior implementation's apparatus or method.

[0170] A STA on a link where the R-TWT SP has been canceled competes for the channel according to EDCA or CSMA / CA in any prior implementation's apparatus or method.

[0171] The number of duplicate R-TWT SPs that can be started on different links is restricted in any prior implementation's apparatus or method.

[0172] The R-TWT member sends a frame indicating the end of the R-TWT SP in any prior implementation's apparatus or method.

[0173] A STA that receives a frame indicating the end of the R-TWT SP can start competing for the channel in any prior implementation's apparatus or method.

[0174] The apparatus or method of any preceding implementation, further comprising transmitting a frame indicating the end of the current R-TWT SP or the end of the quiet interval.

[0175] The apparatus or method of any preceding implementation, which cannot schedule a quiet interval exceeding the R-TWT SP period.

[0176] The apparatus or method of any preceding implementation, further comprising transmitting a quiet element notifying other STAs of the quiet interval schedule.

[0177] The apparatus or method of any preceding implementation, wherein specific information is selected from a group of information consisting of SCSID, TID, and TSPEC.

[0178] The apparatus or method of any preceding implementation, further comprising rejecting an R-TWT membership request if the associated AP determines that the R-TWT SP cannot meet the transmission requirements of specific traffic.

[0179] The apparatus or method of any preceding implementation, further comprising rejecting an R-TWT membership request if the total time required to transmit specific traffic exceeds the upper limit of the total time of all R-TWT SPs that the associated AP can schedule.

[0180] The apparatus or method of any preceding implementation, further comprising rejecting an R-TWT membership request if the total time required to transmit specific traffic exceeds the upper limit of the total time of all R-TWT SPs that the MLD to which the AP belongs can schedule on all links.

[0181] The apparatus or method of any preceding implementation, wherein the same specific traffic cannot be accepted by two different R-TWTs of an AP on one link.

[0182] The apparatus or method of any previous implementation where the same specific traffic cannot be accepted by two different R-TWTs of the MLD of the APs on all links.

[0183] The extended time of the R-TWT SP cannot exceed the TXOP limit or a determined ratio of the TXOP limit, for the apparatus or method of any previous implementation.

[0184] The actual R-TWT SP period cannot exceed the TXOP limit or a determined ratio of the TXOP limit, for the apparatus or method of any previous implementation.

[0185] The actual R-TWT SP period cannot exceed the scheduled R-TWT SP time, for the apparatus or method of any previous implementation.

[0186] The extended time of the R-TWT SP cannot exceed the next target beacon transmission time, for the apparatus or method of any previous implementation.

[0187] The AP or the STA which is a member of the R-TWT SP can obtain a TXOP during the scheduled R-TWT SP and extend the R-TWT SP if the TXOP is extended beyond the end time of the scheduled R-TWT SP, and the R-TWT SP is extended until the end time of the TXOP, for the apparatus or method of any previous implementation.

[0188] The AP or the STA which is a member of the R-TWT SP can start PPDU transmission during the scheduled R-TWT SP and extend the R-TWT SP when the PPDU period and the response-type transmission exceed the end time of the scheduled R-TWT SP, for the apparatus or method of any previous implementation.

[0189] The R-TWT SP is extended until the end time of its PPDU transmission and its response-type transmission, for the apparatus or method of any previous implementation.

[0190] The STA can indicate whether the broadcast TWT signaling is for restricted TWT using B9 in the request type field of the broadcast TWT parameter set field, in any prior implementation of an apparatus or method.

[0191] The STA can indicate additional settings for restricted TWT using 1 bit between B7 and B8 or B15 in the request type field of the broadcast TWT parameter set field, in any prior implementation of an apparatus or method.

[0192] The STA can indicate whether a quiet element is used for restricted TWT using 1 bit between B7 and B8 or B15 in the request type field of the broadcast TWT parameter set field, in any prior implementation of an apparatus or method.

[0193] If no corresponding traffic is being transmitted at the end of the R-TWT SP, the STA can indicate whether the restricted TWT can be extended using 1 bit between B7 and B8 or B15 in the request type field of the broadcast TWT parameter set field, in any prior implementation of an apparatus or method.

[0194] The STA can indicate whether the AP is forced to use PSR-based spatial reuse during the restricted TWT SP using 1 bit between B7 and B8 or B15 in the request type field of the broadcast TWT parameter set field, in any prior implementation of an apparatus or method.

[0195] The STA can indicate whether the AP and R-TWT members can access multiple R-TWT SPs on different links over the same period using 1 bit between B7 and B8 or B15 in the request type field of the broadcast TWT parameter set field, in any prior implementation of an apparatus or method.

[0196] The STA can indicate whether it can transmit traffic from all SCSs during the R-TWT SP using 1 bit between B7 and B8 or B15 of the request type field in the broadcast TWT parameter set field, in any prior implementation of an apparatus or method.

[0197] The STA can indicate whether members of the R-TWT need to start and sleep as a broadcast TWT using 1 bit between B7 and B8 or B15 of the request type field in the broadcast TWT parameter set field, in any prior implementation of an apparatus or method.

[0198] The STA can indicate whether the broadcast TWT parameter set field contains one or more traffic information such as TSPEC, SCSID, or TID using 1 bit between B7 and B8 or B15 of the request type field in the broadcast TWT parameter set field, in any prior implementation of an apparatus or method.

[0199] The STA can indicate whether R-TWT members can compete for a channel outside the R-TWT SP using 1 bit between B7 and B8 or B15 of the request type field in the broadcast TWT parameter set field, in any prior implementation of an apparatus or method.

[0200] The R-TWT SP can end earlier than its schedule, in any prior implementation of an apparatus or method.

[0201] The STA can transmit a frame indicating the start of the R-TWT SP, in any prior implementation of an apparatus or method.

[0202] STA, which is a member of the cancelled R-TWT SP, is a device or method of any previous implementation that cannot access the channel until the R-TWT SP on another link ends.

[0203] All STAs on the link where the R-TWT SP is cancelled are devices or methods of any previous implementation that compete for the channel according to EDCA or CSMA / CA.

[0204] The number of overlapping R-TWT SPs that can be started on different links is limited, which is a device or method of any previous implementation.

[0205] The R-TWT member is a device or method of any previous implementation that can send a frame indicating the end of the R-TWT SP.

[0206] The STA that receives a frame indicating the end of the R-TWT SP is a device or method of any previous implementation that can start competing for the channel.

[0207] The STA is a device or method of any previous implementation that can send a frame such as a CF end indicating the end of the current R-TWT SP or the end of the quiet interval.

[0208] The STA is a device or method of any previous implementation that cannot schedule a quiet interval exceeding the R-TWT SP.

[0209] The STA is a device or method of any previous implementation that can send a quiet element notifying other STAs of the schedule of the quiet interval.

[0210] A device or method of any previous implementation where specific information includes the SCS ID.

[0211] A device or method of any previous implementation where specific information includes the TID.

[0212] The apparatus or method of any preceding implementation, where specific information includes a TSPEC.

[0213] The apparatus or method of any preceding implementation, where the AP can reject an R-TWT membership request if the R-TWT SP cannot meet the transmission requirements for specific traffic.

[0214] The apparatus or method of any preceding implementation, where the AP can reject an R-TWT membership request if the total time required to transmit specific traffic exceeds the upper limit of the total time of all R-TWT SPs that the AP can schedule (or that the schedule-side AP MLD can schedule on all links).

[0215] The apparatus or method of any preceding implementation, where the AP can reject an R-TWT membership request if the total time required to transmit specific traffic exceeds the upper limit of the total time of all R-TWT SPs that the MLD to which the AP belongs can schedule on all links.

[0216] The apparatus or method of any preceding implementation, where the same specific traffic cannot be accepted by two different R-TWTs of an AP on one link.

[0217] The apparatus or method of any preceding implementation, where the same specific traffic cannot be accepted by two different R-TWTs of the MLD of an AP on all links.

[0218] The apparatus or method of any preceding implementation, where the extended time of an R-TWT SP cannot be longer than the TXOP limit.

[0219] The apparatus or method of any preceding implementation, where the extended time of an R-TWT SP cannot be longer than a predetermined percentage (e.g., 50%) of the TXOP limit.

[0220] The actual R-TWT SP period cannot be longer than the TXOP limit, for any prior implementation of an apparatus or method.

[0221] The actual R-TWT SP period cannot be longer than a certain percentage of the TXOP limit, for any prior implementation of an apparatus or method.

[0222] The actual R-TWT SP period cannot be longer than the scheduled R-TWT SP time, for any prior implementation of an apparatus or method.

[0223] The extended time of the R-TWT SP cannot exceed the next target beacon transmission time, for any prior implementation of an apparatus or method.

[0224] An AP or a STA that is a member of the R-TWT SP can obtain a TXOP during the scheduled R-TWT SP and extend the R-TWT SP if the TXOP continues beyond the end time of the scheduled R-TWT SP. The R-TWT SP is extended until the end time of the TXOP.

[0225] An AP or a STA that is a member of the R-TWT SP can start transmitting a PPDU during the scheduled R-TWT SP and extend the R-TWT SP when the PPDU period and the response-type transmission exceed the end time of the scheduled R-TWT SP. The R-TWT SP is extended until the end time of that PPDU transmission and that response-type transmission.

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

[0227] As used herein, the singular forms "a," "an," and "the" include the plural reference unless the context clearly indicates otherwise. A reference to an item in the singular does not mean "only one" unless so stated explicitly, but rather means "one or more than one."

[0228] Expressions such as "A, B, and / or C" in this disclosure represent that any one of A, B, or C, or any combination of items A, B, and C, may exist. An expression structure indicating that a group of elements listed after "at least one of" follows, when applicable, indicates that at least one of these listed elements exists, including any conceivable combination of these listed elements.

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

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

[0231] Relational terms such as first and second, top and bottom, etc. 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.

[0232] The terms "comprises", "comprising", "has", "having", "includes", "including", "contains", "containing", or any other variations of these terms are intended to include non-exclusive inclusion. Thus, a process, method, article, or apparatus that comprises, has, or includes a list of elements does not include only those elements but may also include other elements not expressly listed or inherent to such process, method, article, or apparatus. Elements followed by "comprises... a", "has... a", "includes... a", or "contains... a" do not preclude the existence of additional identical elements in the process, method, article, or apparatus that comprises, has, or includes that element, without further limitation.

[0233] The terms "approximately", "approximate", "substantially", "essentially", and "about", or any variations thereof, as used herein are for the purpose of describing and accounting for minor variations. These terms, when used in relation to an event or situation, can mean that the event or situation will occur without fail and when the likelihood of the event or situation occurring is very high. These terms, when used in relation to a numerical value, 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.

[0234] In addition, in this specification, amounts, ratios, and other numerical values may be presented in a range format. Such a range format 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 enumerated limit values of about 1 and about 200, but it 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.

[0235] As used herein, the term "coupled" is defined as "connected", but it 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 enumerated.

[0236] Advantages, benefits, problem-solving means, and any (single or plural) elements that give rise to or make more prominent any advantage, benefit, or solution should not be construed as important, necessary, or essential features or elements of the technology described herein, or of some or all of the claims.

[0237] Also, in the above disclosure, for the purpose of rationalizing the disclosure, various features can be grouped together in various embodiments. The method of this 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 less than all the features of a single disclosed embodiment.

[0238] The abstract of this disclosure is presented with the understanding that it is not used to interpret or limit the scope or meaning of the claims. It is intended to enable a reader to quickly ascertain the essence of the technical disclosure.

[0239] Depending on the jurisdiction, it should be understood that there is also a practice of seeking deletion of one or more parts of the present disclosure after filing. Therefore, the reader should refer to the application as of the filing date for 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 originally filed.

[0240] The following claims are incorporated into the present disclosure in a state where each claim stands on its own as a separate inventive subject matter.

[0241] 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. Therefore, the scope of the present disclosure will be understood to completely include other embodiments that would be apparent to those skilled in the art.

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

Description of Reference Numerals

[0243] 170 Example of Embodiment 172 The STA re-uses the broadcast TWT parameter set field for R-TWT signaling 174 Option 176 The STA sets the most significant bit of the broadcast TWT recommendation subfield to "1" to indicate that the signaling is for R-TWT, and also sets the other bits for R-TWT parameter setting. 178 The STA sets the broadcast TWT recommendation subfield to a value of 4 or more to indicate that the signaling is for a different type of R-TWT. 180 The STA uses the other spare bits in the broadcast TWT parameter set field for R-TWT parameter setting.

Claims

1. An apparatus for wireless communication in a network, comprising: (a) a STA operating as either a normal wireless station (STA) or an access point (AP) STA, the STA wirelessly communicating with other wireless stations (STAs) using a carrier sense multiple access / collision avoidance (CSMA / CA) mechanism over a wireless local area network (WLAN); (b) a processor coupled to the wireless communication circuit and operating over the WLAN; (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, (i) reuse IEEE 802.11ax-defined broadcast target wake time (B-TWT) signaling for establishing restricted TWT (R-TWT); (ii) use bits of a broadcast TWT parameter set field that is reserved in IEEE 802.11ax to indicate use of R-TWT within the B-TWT; (iii) indicate additional settings for specifying a traffic flow for R-TWT in response to using other bits different from the bits indicating use of R-TWT within the B-TWT in the broadcast TWT parameter set field that is reserved in IEEE 802.11ax; perform steps of a wireless communication protocol for the wireless communication circuit, including the STA using one bit between bit 7 (B7) and bit 8 (B8) or bit 15 (B15) of a request type field within the broadcast TWT parameter set field as a bit different from the bit indicating use of R-TWT within the B-TWT in the broadcast TWT parameter set field to indicate whether the AP is forced to use PSR-based spatial reuse during the restricted TWT service period (R-TWT SP); characterized by the apparatus.

2. The STA uses bit 9 (B9) of a request type field within the broadcast TWT parameter set field as the bit indicating use of R-TWT within the B-TWT in the broadcast TWT parameter set field to indicate whether the broadcast TWT signaling is for restricted TWT (R-TWT). The apparatus according to claim 1.

3. The STA uses one bit between bit 7 (B7) and bit 8 (B8) or bit 15 (B15) of the request type field in the broadcast TWT parameter set field as a bit different from the bit indicating the use of R-TWT in B-TWT within the broadcast TWT parameter set field, and as another bit different from the bit indicating whether the AP is forced to use PSR-based spatial reuse during the service period of R-TWT (R-TWT SP), to indicate an additional setting for specifying a traffic flow for restricted TWT (R-TWT). The apparatus according to claim 1.

4. The STA uses one bit between bit 7 (B7) and bit 8 (B8) or bit 15 (B15) of the request type field in the broadcast TWT parameter set field as a bit different from the bit indicating the use of R-TWT in B-TWT within the broadcast TWT parameter set field, and as another bit different from the bit indicating whether the AP is forced to use PSR-based spatial reuse during the service period of R-TWT (R-TWT SP), to indicate whether a quiet element is used to protect R-TWT. The quiet element is used to schedule a quiet interval to prevent channel contention from STAs that are not members of the service period of R-TWT (R-TWT SP) from entering the quiet mode during the service period of R-TWT (R-TWT SP) after receiving a quiet element command from the schedule side AP. The apparatus according to claim 1.

5. The STA uses a bit between bit 7 (B7) and bit 8 (B8) or bit 15 (B15) of the request type field in the broadcast TWT parameter set field, which is different from the bit indicating the use of R-TWT in B-TWT within the broadcast TWT parameter set field, and is also different from another bit indicating whether the AP is forced to use PSR-based spatial reuse during the service period of R-TWT (R-TWT SP). When the corresponding traffic is not being transmitted at the end of the service period of R-TWT (R-TWT SP), it indicates whether the restricted TWT (R-TWT) can be extended beyond its scheduled end time. The apparatus according to claim 1. **Claim 6** The PSR-based spatial reuse includes a parameterized spatial reuse transmission (PSRT) or parameterized spatial reuse reception (PSRR) physical layer convergence procedure (PLCP) protocol data unit (PPDU) defined for spatial reuse in IEEE 802.11ax. The apparatus according to claim 1. **Claim 7** The STA uses a bit between bit 7 (B7) and bit 8 (B8) or bit 15 (B15) of the request type field in the broadcast TWT parameter set field, which is different from the bit indicating the use of R-TWT in B-TWT within the broadcast TWT parameter set field, and is also different from another bit indicating whether the AP is forced to use PSR-based spatial reuse during the service period of R-TWT (R-TWT SP). It is used as another different bit to indicate whether the AP and R-TWT members can access multiple overlapping service periods of R-TWT (R-TWT SP) on different links over the same period. The apparatus according to claim 1. **Claim 8** Options for multiple overlapping service periods of R-TWT (R-TWT SP) are selected from a group of options consisting of: (a) allowing only one service period of R-TWT (R-TWT SP) among the scheduled multiple overlapping service periods of R-TWT (R-TWT SP) to start and canceling the others; and (b) allowing multiple scheduled overlapping service periods of R-TWT (R-TWT SP) to start. The apparatus according to claim 7.

9. The STA uses one bit between bit 7 (B7) and bit 8 (B8) or bit 15 (B15) of the request type field in the broadcast TWT parameter set field as a bit different from the bit indicating the use of R-TWT in B-TWT within the broadcast TWT parameter set field, and also as another bit different from the bit indicating whether the AP is forced to use PSR-based spatial reuse during the service period of R-TWT (R-TWT SP), to indicate whether traffic from all stream classification services (SCS) is permitted to be transmitted during the service period of R-TWT (R-TWT SP). The apparatus according to claim 1.

10. The STA uses one bit between bit 7 (B7) and bit 8 (B8) or bit 15 (B15) of the request type field in the broadcast TWT parameter set field as a bit different from the bit indicating the use of R-TWT in B-TWT within the broadcast TWT parameter set field, and also as another bit different from the bit indicating whether the AP is forced to use PSR-based spatial reuse during the service period of R-TWT (R-TWT SP), to indicate whether the members of the R-TWT need to be activated and put to sleep as indicated in the broadcast TWT. The apparatus according to claim 1.

11. The STA uses one bit between bit 7 (B7) and bit 8 (B8) or bit 15 (B15) of the request type field in the broadcast TWT parameter set field as a bit different from the bit indicating the use of R-TWT in B-TWT within the broadcast TWT parameter set field, and also as another bit different from the bit indicating whether the AP is forced to use PSR-based spatial reuse during the service period of R-TWT (R-TWT SP), to indicate the amount of traffic information included in the broadcast TWT parameter set field. The apparatus according to claim 1.

12. The traffic information is selected from a group of traffic information consisting of traffic specification (TSPEC), stream classification service identifier (SCSID), and traffic identifier (TID). The apparatus according to claim 11.

13. The STA uses one bit between bit 7 (B7) and bit 8 (B8) or bit 15 (B15) of the request type field in the broadcast TWT parameter set field as a bit indicating the use of R-TWT in B-TWT within the broadcast TWT parameter set field, and is different from the bit indicating whether the AP is forced to use PSR-based spatial reuse during the service period of R-TWT (R-TWT SP). It is used as another bit to indicate whether R-TWT members are permitted to perform channel contention outside the service period of R-TWT (R-TWT SP). The apparatus according to claim 1.

14. An apparatus for wireless communication in a network, (a) A STA operating as either a normal wireless station (STA) or an access point (AP) STA, a wireless communication circuit that 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); (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, and (d) the instructions, when executed by the processor, (i) Reusing IEEE 802.11ax-defined broadcast target wake time (B-TWT) signaling for the establishment of restricted TWT (R-TWT); (ii) Using bits of the broadcast TWT parameter set field, which is preliminary in IEEE 802.11ax, to indicate the use of R-TWT within B-TWT; (iii) In response to using other bits different from the bit indicating the use of R-TWT within B-TWT in the broadcast TWT parameter set field, which is preliminary in IEEE 802.11ax, indicating additional settings for specifying a traffic flow for R-TWT; Executing steps of a wireless communication protocol for the wireless communication circuit, including (iv) One or more of the additional settings that specify the traffic flow indicate: (A) whether a quiet element is used to protect the R-TWT; (B) whether the restricted TWT (R-TWT) can be extended beyond its scheduled end time if no corresponding traffic is being transmitted at the end of the service period of the R-TWT (R-TWT SP); (C) whether the AP is forced to use PSR-based spatial reuse during the service period of the R-TWT (R-TWT SP); (D) whether the AP and the R-TWT members can access multiple overlapping R-TWT service periods (R-TWT SP) on different links for the same period of time; (E) whether traffic from all stream classification services (SCS) is permitted to be transmitted during the service period of the R-TWT (R-TWT SP); (F) whether the members of the R-TWT need to initiate / sleep in response to a broadcast TWT; (G) the amount of traffic information included in the broadcast TWT parameter set field, and are selected from a group of additional settings that specify the traffic flow, wherein the STA uses a bit different from the bit indicating the use of the R-TWT in the B-TWT within the broadcast TWT parameter set field as another bit between bit 7 (B7) and bit 8 (B8) of the request type field within the broadcast TWT parameter set field to indicate whether the AP is forced to use PSR-based spatial reuse during the service period of the R-TWT (R-TWT SP), a device characterized thereby. **Claim 15** wherein the STA uses bit 9 (B9) of the request type field within the broadcast TWT parameter set field as the bit indicating the use of the R-TWT in the B-TWT within the broadcast TWT parameter set field to indicate whether the broadcast TWT signaling is for the restricted TWT (R-TWT), The device according to claim 14. **Claim 16** The STA uses a bit different from the bit indicating the use of R-TWT in B-TWT within the broadcast TWT parameter set field, which is a bit between bit 7 (B7) and bit 8 (B8) of the request type field within the broadcast TWT parameter set field or bit 15 (B15), and is also a different bit from the bit indicating whether the AP is forced to use PSR-based spatial reuse during the service period of R-TWT (R-TWT SP), to indicate an additional setting for specifying a traffic flow for restricted TWT (R-TWT). The apparatus according to claim 15.

17. The traffic information is selected from a group of traffic information including traffic specification (TSPEC), stream classification service identifier (SCSID), and traffic identifier (TID). The apparatus according to claim 14.

18. A wireless communication method in a network, wherein: (a) a STA that executes a wireless communication protocol and operates as a normal wireless station (STA) or an access point (AP) STA communicates wirelessly with other wireless stations (STAs) using a carrier sense multiple access / collision avoidance (CSMA / CA) mechanism over a wireless local area network (WLAN); (b) reusing broadcast target wake time (B-TWT) signaling defined in IEEE 802.11ax for the establishment of restricted TWT (R-TWT); (c) using bits in the broadcast TWT parameter set field that are reserved in IEEE 802.11ax to indicate the use of R-TWT within B-TWT; (d) in response to using other bits different from the bit indicating the use of R-TWT within B-TWT in the broadcast TWT parameter set field that is reserved in IEEE 802.11ax, indicating an additional setting for specifying a traffic flow for R-TWT. comprising The STA uses a bit other than the bit indicating the use of R-TWT in B-TWT within the broadcast TWT parameter set field, which is a bit between bit 7 (B7) and bit 8 (B8) or bit 15 (B15) of the request type field within the broadcast TWT parameter set field, to indicate whether the AP is forced to use PSR-based spatial reuse during the service period of R-TWT (R-TWT SP). A method characterized by this. The STA uses bit 9 (B9) of the request type field within the broadcast TWT parameter set field as the bit indicating the use of R-TWT in B-TWT within the broadcast TWT parameter set field, to indicate whether the broadcast TWT signaling is for restricted TWT (R-TWT). The method according to claim 18. ​

Images