Power saving operation during triggered transmission opportunity sharing procedure

Abstract

A station (STA) receives a first frame from an access point (AP), the first frame indicating: a first time period of a transmission opportunity (TXOP) allocated to the STA, and a sharing mode for the first time period. The STA transmits a second frame to the AP indicating that the STA returns the first time period to the AP during the first time period. After transmitting the second frame, the STA transitions from a first power state to a second power state based on the sharing mode.

Description

Cross-references to related applications

[0001] This application claims the benefits of U.S. Provisional Application No. 63 / 620,513, filed January 12, 2024, and U.S. Provisional Application No. 63 / 563,665, filed March 11, 2024, the entire contents of which are incorporated herein by reference. Attached Figure Description

[0002] This document describes examples of several embodiments of various embodiments of the present disclosure with reference to the accompanying drawings.

[0003] Figure 1 An example wireless communication network in which embodiments of the present disclosure can be implemented is shown.

[0004] Figure 2 This is a block diagram showing an example implementation of a station (STA) and an access point (AP).

[0005] Figure 3 An example Multi-User Request Transmission (MU-RTS) Transport Opportunity Sharing (TXS) Triggered (MRTT) frame is shown, which can be used during the TXS process.

[0006] Figure 4 An example of the TXS procedure (mode=1) is shown.

[0007] Figure 5 An example of the TXS procedure (mode=2) is shown.

[0008] Figure 6 This is an example illustrating a TXS process between multiple linked devices (MLDs).

[0009] Figure 7 This is an example illustrating inefficient STA operations that may occur during the TXS process.

[0010] Figure 8 This is an example demonstrating the TXS power saving (PS) mode.

[0011] Figure 9 This is an example showing how STA enables or disables TXS PS mode in a sample implementation.

[0012] Figure 10 This is an example showing how STA enables or disables TXS PS mode according to another example implementation.

[0013] Figure 11 This is an example showing how STA enables or disables TXS PS mode according to another example implementation.

[0014] Figure 12An example of existing operation is shown, in which the STA can enter a nap state during the Target Wake Time (TWT) service period (SP).

[0015] Figure 13 An example illustrating the TXS process is shown.

[0016] Figure 14 Examples of one or more embodiments that can utilize power-saving operations during the TXS process are shown.

[0017] Figure 15 Examples of one or more embodiments that can utilize power-saving operations during the TXS process are shown.

[0018] Figure 16 Examples of one or more embodiments that can utilize power-saving operations during the TXS process are shown.

[0019] Figure 17 Examples of one or more embodiments that can utilize power-saving operations during the TXS process are shown.

[0020] Figure 18 Examples of one or more embodiments that can utilize power-saving operations during the TXS process are shown.

[0021] Figure 19 Examples of one or more embodiments that can utilize power-saving operation during the TXS process are shown.

[0022] Figure 20 Examples of one or more embodiments that can utilize power-saving operations during the TXS process are shown.

[0023] Figure 21 Different signaling capabilities of one or more embodiments are described.

[0024] Figure 22 An example process according to an embodiment is shown.

[0025] Figure 23 An example process according to an embodiment is shown.

[0026] Figure 24 Examples of one or more embodiments that can utilize power-saving operations during the TXS process are shown. Detailed Implementation

[0027] In this disclosure, various embodiments are presented as examples of how the disclosed techniques and / or how the disclosed techniques can be practiced in environments and scenarios. It will be apparent to those skilled in the art that various changes in form and detail can be made without departing from the scope. How alternative embodiments can be implemented will be apparent to those skilled in the art after reading the description. This embodiment is not limited to any of the exemplary embodiments described. Embodiments of this disclosure will be described with reference to the accompanying drawings. Limitations, features, and / or elements from the disclosed example embodiments can be combined to create further embodiments within the scope of this disclosure. Any drawings emphasizing features and advantages are presented for illustrative purposes only. The disclosed architecture is flexible and configurable enough that it can be utilized in ways other than those shown. For example, actions listed in any flowchart can be reordered or used only optionally in some embodiments.

[0028] The embodiments can be configured to operate as needed. The disclosed mechanisms can be executed when certain criteria are met, for example, in a station, access point, radio environment, network, or a combination thereof. Example standards may be based at least in part on, for example, wireless device or network node configuration, traffic load, initial system setup, packet size, service characteristics, or a combination thereof. Various example embodiments can be applied when one or more criteria are met. Therefore, example embodiments that selectively implement the disclosed protocols can be implemented.

[0029] In this disclosure, “a” and “an”, and similar phrases, should be interpreted as “at least one” and “one or more”. Similarly, any term ending with the suffix “(s)” should be interpreted as “at least one” and “one or more”. In this disclosure, the term “may” should be interpreted as “may, for example.” In other words, the term “may” indicates that the phrase following the term “may” is an example of one of a plurality of suitable possibilities that may or may not be employed by one or more of the various embodiments. As used herein, the terms “comprising” and “consisting of” enumerate one or more components of the described element. The term “comprising” is interchangeable with “including” and does not exclude the inclusion of unlisted components in the described element. In contrast, “consisting of” provides a complete enumeration of one or more components of the described element. The term “based on” as used herein can be interpreted as “at least partially based on” rather than, for example, “based on only.” The term “and / or” as used herein indicates any possible combination of the enumerated elements. For example, "A, B and / or C" can mean A; B; C; A and B; A and C; B and C; or A, B and C.

[0030] If A and B are sets and every element of A is an element of B, then A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, possible subsets of B = {STA1, STA2} are: {STA1}, {STA2}, and {STA1, STA2}. The phrase “based on” (or equivalently “at least based on”) indicates that the phrase following the term “based on” is an example of one of a variety of suitable possibilities that may or may not be used in one or more of the various embodiments. The phrase “in response to” (or equivalently “at least in response to”) indicates that the phrase following the phrase “in response to” is an example of one of a variety of suitable possibilities that may or may not be used in one or more of the various embodiments. The phrase “depends on” (or equivalently “at least depends on”) indicates that the phrase following the phrase “depends on” is an example of one of a variety of suitable possibilities that may or may not be used in one or more of the various embodiments. The phrase “adopt / use” (or equivalently “at least adopt / use”) indicates that the phrase following the phrase “adopt / use” is an example of one of a variety of suitable possibilities that may or may not be used in one or more of the various embodiments.

[0031] The term "configured" can refer to the capabilities of a device, regardless of whether the device is in an operational or non-operational state. "Configured" can also refer to specific settings within a device that affect its operational characteristics, regardless of whether the device is in an operational or non-operational state. In other words, hardware, software, firmware, registers, memory values, etc., can be "configured" within the device, whether the device is in an operational or non-operational state, to provide specific characteristics to the device. Terms such as "control messages induced in the device" can mean that the control messages have parameters that can be used to configure specific characteristics, or can be used to perform certain actions within the device, regardless of whether the device is in an operational or non-operational state.

[0032] In this disclosure, a parameter (or equivalently referred to as a field or information element: IE) may include one or more information objects, and an information object may include one or more other objects. For example, if parameter (IE)N includes parameter (IE)M, and parameter (IE)M includes parameter (IE)K, and parameter (IE)K includes parameter (information element)J, then, for example, N includes K, and N includes J. In the example embodiment, when one or more messages / frames include multiple parameters, this means that a parameter among the multiple parameters is in at least one message / frame of one or more messages, but not necessarily in every message / frame of one or more messages / frames.

[0033] Many of the features presented are described as optional using the word "may" or parentheses. For brevity and readability, this disclosure does not explicitly describe every permutation that can be obtained by selecting from the set of optional features. This disclosure should be interpreted as explicitly disclosing all such permutations. For example, a system described as having three optional features can be embodied in seven ways: having only one of the three possible features, having any two of the three possible features, or having three of the three possible features.

[0034] Many of the elements described in the disclosed embodiments can be implemented as modules. A module is defined herein as an element that performs a defined function and has an interface to the definitions of other elements. Modules described in this disclosure can be implemented in hardware, software combined with hardware, firmware, wet hardware (e.g., hardware with biological elements), or combinations thereof, and may be behaviorally equivalent. For example, a module can be implemented as a software routine or modeling / simulation program (such as Simulink, Stateflow, GNU Octave, or LabVIEW MathScript) written in a computer language (such as C, C++, Fortran, Java, Basic, Matlab, etc.) configured to be executed by a hardware machine. Modules can be implemented using physical hardware that includes discrete or programmable analog, digital, and / or quantum hardware. Examples of programmable hardware include: computers, microcontrollers, microprocessors, application-specific integrated circuits (ASICs); field-programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs). Computers, microcontrollers, and microprocessors are programmed using languages ​​such as assembly, C, and C++. FPGAs, ASICs, and PLDs are typically programmed using hardware description languages ​​(HDLs), such as VHSIC Hardware Description Language (VHDL) or Verilog, which configure the connections between internal hardware modules with limited functionality on the programmable device. The techniques mentioned are often used in combination to achieve the desired result of functional modules.

[0035] Figure 1 Example 100 wireless communication networks in which various embodiments of this disclosure can be implemented are shown. For example... Figure 1 As shown, an example wireless communication network may include an IEEE 802.11 (WLAN) infrastructure network 102. WLAN infrastructure network 102 may include one or more Basic Service Sets (BSS) 110 and 120 and a Distribution System (DS) 130.

[0036] BSS 110-1 and 110-2 each include a set of access points (APs or AP STAs) and at least one station (STA or non-AP STA). For example, BSS 110-1 includes AP 104-1 and STA 106-1, and BSS 110-2 includes AP 104-2 and STAs 106-2 and 106-3. The APs and at least one STA in the BSS perform an association process to communicate with each other.

[0037] The DS 130 can be configured to connect BSS 110-1 and BSS 110-2. Therefore, the DS 130 can enable Extended Service Set (ESS) 150. Within the ESS 150, APs 104-1 and 104-2 are connected via the DS 130 and can have the same Service Set Identifier (SSID).

[0038] The WLAN infrastructure network 102 can be coupled to one or more external networks. For example, such as Figure 1 As shown, WLAN infrastructure network 102 can be connected to another network 108 (e.g., 802.X) via portal 140. Portal 140 can be used as a bridge to connect DS 130 of WLAN infrastructure network 102 to another network 108.

[0039] Figure 1 The example wireless communication network shown may also include one or more self-organizing networks or independent BSSs (IBSSs). A self-organizing network or IBSS is a network of multiple STAs that are within each other's communication range. The multiple STAs are configured such that they can communicate with each other using direct peer-to-peer communication (i.e., not via an AP).

[0040] For example, in Figure 1 In this configuration, STAs 106-4, 106-5, and 106-6 can be configured to form a first IBSS 112-1. Similarly, STAs 106-7 and 106-8 can be configured to form a second IBSS 112-2. Since an IBSS does not include an AP, it does not include a centralized management entity. Instead, STAs within the IBSS are managed in a distributed manner. STAs forming an IBSS can be fixed or mobile.

[0041] A STA, serving as a predefined functional medium, may include a Media Access Control (MAC) layer conforming to the IEEE 802.11 standard. A physical layer interface for the radio medium can be used between APs and non-AP stations (STAs). Various other terms may also be used to refer to a STA, including mobile terminal, radio device, radio transceiver unit (WTRU), user equipment (UE), mobile station (MS), mobile subscriber unit, or user. For example, the term "user" may be used to refer to a STA participating in uplink multi-user multiple-input multiple-output (MU MIMO) and / or uplink orthogonal frequency division multiple access (OFDMA) transmissions.

[0042] A Physical Layer (PHY) Protocol Data Unit (PPDU) can be a composite structure including a PHY preamble and a payload in the form of a PHY Service Data Unit (PSDU). For example, a PSDU may include a PHY preamble and a header and / or one or more MAC Protocol Data Units (MPDUs). The information provided in the PHY preamble can be used by the receiving device to decode subsequent data in the PSDU. When transmitting PPDUs via a bundled channel (a channel formed by channel bundling), the preamble field can be copied and transmitted in each of the multiple component channels. The PHY preamble may include both a traditional portion (or "traditional preamble") and a non-traditional portion (or "non-traditional preamble"). The traditional preamble can be used for packet detection, automatic gain control, and channel estimation, among other purposes. The traditional preamble is also typically used to maintain compatibility with legacy equipment. The format, encoding, and information provided in the non-traditional portion of the preamble are based on the specific IEEE 802.11 protocol to be used for transmitting the payload.

[0043] A frequency band can include one or more sub-bands or frequency channels. For example, PPDUs conforming to IEEE 802.11n, 802.11ac, 802.11ax, and / or 802.11be standard revisions can be transmitted in 2.4 GHz, 5 GHz, and / or 6 GHz bands, each of which can be divided into multiple 20 MHz channels. PPDUs can be transmitted on physical channels with a minimum bandwidth of 20 MHz. Larger channels can be formed through channel bundling. For example, PPDUs can be transmitted on physical channels with bandwidths of 40 MHz, 80 MHz, 160 MHz, or 320 MHz by bundling multiple 20 MHz channels together.

[0044] Figure 2 This is block diagram 200 illustrating example implementations of STA 210 and AP 260. (See diagram 200 for details.) Figure 2As shown, STA 210 may include at least one processor 220, memory 230, and at least one transceiver 240. AP 260 may include at least one processor 270, memory 280, and at least one transceiver 290. Processors 220 / 270 may be operatively connected to memory 230 / 280 and / or transceiver 240 / 290.

[0045] Processors 220 / 270 can implement the functions of the PHY layer, MAC layer, and / or logical link control (LLC) layer of the corresponding device (STA 210 or AP 260). Processors 220 / 270 may include one or more processors and / or one or more controllers. For example, one or more processors and / or one or more controllers may include, for example, a general-purpose processor, a digital signal processor (DSP), a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), logic circuits, or a chipset.

[0046] Memory 230 / 280 may include read-only memory (ROM), random access memory (RAM), flash memory, memory cards, storage media, and / or other storage units. Memory 230 / 280 may include one or more non-transitory computer-readable media. Memory 230 / 280 may store computer program instructions or code that can be executed by processor 220 / 270 to perform one or more operations / embodiments discussed in this application. Memory 230 / 280 may be implemented (or located) within or outside of processor 220 / 270. Memory 230 / 280 may be operatively connected to processor 220 / 270 via various means known in the art.

[0047] Transceiver 240 / 290 can be configured to transmit / receive radio signals. In an embodiment, transceiver 240 / 290 can implement the PHY layer of a corresponding device (STA 210 or AP 260). In an embodiment, STA 210 and / or AP 260 can be multi-link devices (MLDs), which are devices capable of operating on multiple links defined by the IEEE 802.11 standard. Thus, STA 210 and / or AP 260 can each implement multiple PHY layers. Multiple PHY layers can be implemented using one or more of transceivers 240 / 290.

[0048] Target Wake-Up Time (TWT) (a feature introduced in the IEEE 802.11ah standard) allows STAs to manage activity in the BSS by scheduling STAs to operate at different times to reduce contention. TWT can allow STAs to reduce the amount of time required for a STA utilizing power management mode to be woken up. TWT can be a standalone TWT or a broadcast TWT. Standalone TWTs follow a TWT protocol negotiated between STAs. Broadcast TWTs are based on a scheduling set and are provided to the STAs by the AP.

[0049] In a standalone TWT, the STA that requests the TWT protocol is called the TWT requesting STA. The TWT requesting STA can be, for example, a non-AP STA. The STA that responds to the request is called the TWT responding STA. The TWT responding STA can be, for example, an AP. The TWT requesting STA is assigned a specific time to wake up and exchange frames with the TWT responding STA. The TWT requesting STA can transmit wake-up scheduling information to the TWT responding STA. When the TWT protocol is established between the TWT responding STA and the TWT requesting STA, the TWT responding STA can send a TWT value to the TWT requesting STA.

[0050] When using explicit TWT, the TWT requesting STA can wake up and perform frame exchange. The TWT requesting STA can receive the next TWT information in the response from the TWT responding STA. When using implicit TWT, the TWT requesting STA can calculate the next TWT by adding a fixed value to the current TWT value.

[0051] The TWT value of an implicit TWT can be periodic. A TWT request STA operating using the implicit TWT protocol can determine the start time of the next TWT service period (TWT SP) by adding the value of the TWT wake-up interval associated with the TWT protocol to the start time of the current TWT SP. A TWT response STA can include a series of start times for TWT SPs corresponding to a single TWT stream identifier of the implicit TWT protocol in the target wake-up time field of the TWT element. The TWT element can include a "Accept TWT" value in the TWT setting command field. The start time of the TWT SP series can indicate the start time of the first TWT SP in the series. The start time of subsequent TWT SPs can be determined by adding the value of the TWT wake-up interval to the start time of the current TWT SP. In one example, a TWT request STA (wakeable for an implicit TWT SP) can go into a dozing state after the TWT SP has elapsed or after receiving a service period end (EOSP) field equal to 1 from the TWT response STA (whichever occurs first).

[0052] A TWT session can be negotiated between the AP and STA. The TWT session can configure TWT SPs for DL ​​and UL services between the AP and STA. Expected services can be confined to the negotiated SP. A TWT SP can start at a specific time. A TWT SP can run for the duration of the SP. A TWT SP can repeat once per SP interval.

[0054] Figure 3 An example MRTT frame 300 that can be used in the TXS process is shown. Figure 3 As shown, the example MRTT frame 300 may include a frame control field, a duration field, a receiver address (RA) field, a transmitter address (TA) field, a common information field, a user information list field, a padding field, and / or a frame check sequence (FCS) field.

[0055] In one example, the public information field could be a High Efficiency (HE) variant public information field or an Extremely High Throughput (EHT) variant public information field. For example... Figure 3 As shown, the EHT variant public information field may include one or more of the following subfields: trigger type, UL length, additional TF, required CS, UL BW, GI and HE / EHT-LTF type / trigger TXOP sharing mode, number of HE / EHT-LTF symbols, LDPC additional symbol segment, AP Tx power, pre-FEC fill factor, PE disambiguation, UL space reuse, HE / EHT P160, special user information field flag, EHT reservation, reservation or trigger-related public information.

[0056] The trigger type subfield indicates that frame 300 is an MRTT frame.

[0057] The GI and HE / EHT-LTF type / trigger TXOP shared mode subfield may include a trigger TXOP shared mode subfield. In one example, the trigger TXOP shared mode subfield may be set to a non-zero value (e.g., 1 or 2). In one example, the trigger TXOP shared mode subfield may be set to one (1). Thus, the trigger TXOP shared mode subfield may indicate that the STA indicated by the AID12 subfield of the User Information field (of the User Information List field) may send one or more non-TB PPDUs to the AP during the time period indicated by the Allocation Duration subfield of the User Information field. In another example, the trigger TXOP shared mode subfield may be set to 2. In this way, the trigger TXOP shared mode subfield may indicate that the STA indicated by the AID12 subfield of the User Information field (of the User Information List field) may send one or more non-TB PPDUs to the AP or peer STA during the time period indicated by the Allocation Duration subfield of the User Information field. In one example, the peer STA may be a STA with a connection for P2P communication or direct communication with the STA.

[0058] The user information list field may include one or more user information fields. In one example, the EHT variant user information field may include, for example: Figure 3 One or more of the following subfields are shown: AID12, RU allocation, allocation duration, reservation, or PS160.

[0059] The AID12 subfield can indicate the associated identifier (AID) of the STA that can use the time indicated by the Assigned Duration subfield.

[0060] The RU allocation subfield can indicate the location and size of the RU allocated to the STA indicated by the AID12 subfield.

[0061] The allocated duration subfield can indicate the time allocated by the AP that sent the MRTT frame 300. The allocated time can be a portion of the TXOP obtained by the AP. In an example embodiment, the allocated duration subfield can indicate a first time period.

[0062] Figure 4 Example 400 of the TXS procedure (mode=1) is shown. Figure 4As shown, the TXS procedure can begin when AP 410 sends an MRTT frame 420 to STA 411. The MRTT frame 420 may allocate a portion of the TXOP obtained by AP 410 to STA 411 and may indicate that the TXS mode is equal to 1. STA 411, receiving the MRTT frame 420, can use the allocated time to send one or more non-TB PPDUs to AP 410. The one or more non-TB PPDUs may include data frames, control frames, management frames, or action frames.

[0063] In one example, MRTT frame 420 may include a trigger TXOP shared mode subfield, which indicates a TXS mode and / or subfield, the TXS mode and / or subfield indicating a first time period corresponding to the allocated time. In one example, the first time period may be set to a value of X microseconds (µs).

[0064] STA 411 can respond to MRTT frame 420 by sending CTS frame 421 to AP 410. Subsequently, STA 411 can send non-TB PPDUs 422, 424, including one or more data frames, to AP 410 during the first time period indicated in MRTT frame 420. In one example, AP 410 can send one or more BA frames 423, 425 in response to one or more data frames contained in the non-TB PPDUs 422, 424 received from STA 411.

[0065] Figure 5 Example 500 of the TXS process (mode=2) is shown. Figure 5 As shown, the TXS procedure can begin when AP 510 sends an MRTT frame 520 to STA 511. The MRTT frame 520 may allocate a portion of the TXOP obtained by AP 510 to STA 511 and may indicate that the TXS mode is equal to 2. STA 511, receiving the MRTT frame 520, can use the allocated time to send one or more non-TB PPDUs to STA 512. The one or more non-TB PPDUs may include data frames, control frames, management frames, or action frames.

[0066] In one example, MRTT frame 520 may include a trigger TXOP shared mode subfield, which indicates a TXS mode and / or subfield, the TXS mode and / or subfield indicating a first time period corresponding to the allocated time. In one example, the first time period may be set to a value of X microseconds (µs).

[0067] STA 511 can respond to MRTT frame 520 by sending CTS frame 521 to AP 510. Subsequently, STA 511 can send non-TB PPDUs 522, 524, including one or more data frames, to STA 512 during the first time period indicated in MRTT frame 520. In one example, STA 512 can send one or more BA frames 523, 525 in response to one or more data frames contained in non-TB PPDUs 522, 524 received from STA 511.

[0068] Figure 6 Example 600 illustrates an example TXS process between multiple linked devices (MLDs). Figure 6 As shown, Example 600 includes AP MLD 602 ​​and non-AP MLD 604. AP 602-1 and AP 602-2 can be subordinate to AP MLD 602. STA 604-1 and STA 604-2 can be subordinate to non-AP MLD 604. STA 604-1 can be associated with AP 602-1. AP 602-1 and STA 604-1 can communicate via a first link (Link 1). STA 604-2 can be associated with AP 602-2. AP 602-2 and STA 604-2 can communicate via a second link (Link 2).

[0069] In one example, AP 602-1 may send a MU-RTS TXS Triggered (MRTT) frame 606 to STA 604-1 on link 1. MRTT frame 606 may include a TXOP shared mode subfield set to 1, an AID12 subfield set to STA 604-1's AID, and / or a first time period (e.g., X us, where X is an integer value greater than 0).

[0070] In one example, STA 604-1 may respond to MRTT frame 606 by sending CTS frame 608 on link 1. Subsequently, STA 604-1 may send data frame 610 to AP 602-1 on link 1 during a first time period (e.g., in a non-TBPPDU). AP 602-1 may respond to data frame 610 by sending BA frame 613 on link 1 during the first time period.

[0071] In one example, AP 602-2 may send MRTT frame 614 to STA 604-2 on link 2. MRTT frame 614 may include a TXOP shared mode subfield set to 1, an AID12 subfield set to STA 604-2's AID, and / or a first time period (e.g., Y us, where Y is an integer value greater than 0).

[0072] In one example, STA 604-2 may send CTS frame 616 on link 2 in response to MRTT frame 614. Subsequently, STA 604-2 may send data frame 618 to AP 602-2 on link 2 during a first time period (e.g., in a non-TBPPDU). AP 602-2 may send BA frame 620 on link 2 in response to data frame 618 during the first time period (e.g., Y us).

[0073] Figure 7 Example 700 illustrates an inefficient STA operation that can occur during a TXS process. (e.g.) Figure 7 As shown, Example 700 includes AP 702 and STAs 704, 706 and 708. STA 704 may be associated with AP 702.

[0074] In one example, AP 702 can allocate a portion of its acquired TXOP to STA 704 by sending MRTT frame 710. STA 704 can then respond to MRTT frame 710 by sending CTS frame 712 to AP 702.

[0075] MRTT frame 710 may include a TXOP shared mode subfield, an AID12 subfield of AID set to STA 704, and / or a first time period (e.g., X us).

[0076] In one example, the first time period may indicate a portion of the time allocated by AP 702 within the acquired TXOP. In another example, the first time period may be indicated by a subfield (e.g., the allocation duration field) in MRTT frame 710. In yet another example, the first time period may be set to the value of X us.

[0077] In one example, the TXOP sharing mode subfield is set to 2. A TXOP sharing mode subfield set to 2 indicates that STA 704 can send one or more non-TB PPDUs to AP 702 or a peer STA during a first time period. In one example, the peer STA can be a STA with a connection for P2P or direct communication with STA 704. In one example, the peer STA can be STA 706. One or more non-TB PPDUs can include data frames, control frames, management frames, or action frames. In example 700, STA 704 can send data frame 714 to STA 706 during the first time period. STA 706 can respond to data frame 714 by sending a BA frame 716 to STA 704. STA 704 can then send data frame 718 to STA 706. STA 706 can respond to data frame 718 with a BA frame 720.

[0078] After receiving MRTT frame 710, STA 708 can be in a wake-up state during the first time period (X) indicated in MRTT frame 710. However, during this first time period, AP 702 may not communicate with STA 708 because STA 708 is not assigned power by MRTT frame 710. Therefore, the wake-up power state of STA 708 may lead to unnecessary power waste at STA 708.

[0079] Figure 8 This is an example 800 illustrating an example TXS PS (PS) mode that can be used to address potential waste during some wake-up states. (Example 800) Figure 8 As shown, Example 800 includes AP 802 and STAs 804, 806 and 808. One or more of STAs 804, 806 and 808 may be associated with AP 802.

[0080] like Figure 8 As shown, Example 800 can begin with AP 802 sending the first frame 810 to allocate a portion of the acquired TXOP to STA 804. Frame 810 may include a TXOP sharing mode subfield, an AID 12 subfield, and a first time period (e.g., Xus). The TXOP sharing mode subfield can indicate a triggered TXOP sharing procedure. For example, the TXOP sharing mode subfield can be set to a non-zero value (e.g., 1, 2, ...) indicating triggered TXOP sharing mode 1 or triggered TXOP sharing mode 2. The AID 12 subfield can be set to the AID of the STA that can use the first time period to send and receive one or more frames. For example, the AID 12 subfield can be set to the AID of STA 804. The first time period can be specified in microseconds or some other unit of time. In the example, frame 810 can be an MRTT frame.

[0081] Upon receiving frame 810, STA 804 may send a second frame 812 to AP 802. In one example, frame 812 may be a CTS frame. STA 804 may then send one or more non-TB PPDUs, including one or more data frames 814 and 818, to STA 806 during the first time period. STA 806 may send one or more BA frames 816 and 820 to STA 804 in response to data frames 814 and 818, respectively.

[0082] In one implementation, STA 808 can transition to a dozing state based on the receipt of frame 810 during a first time period where no STA 808 is assigned. In an example embodiment, STA 808 can transition to a dozing state under the following circumstances: -After STA 808 receives frame 810 and before STA 808 receives frame 812 in response to frame 810; -After STA 808 receives frame 812 in response to frame 810; or -If STA 808 does not receive a third frame during the second time period after STA 808 receives frame 810.

[0083] The third frame can be a data frame, control frame, or management frame. The value of the second time period can be a fixed value, or it can be signaled by a fourth frame sent by AP 802. The fourth frame can be a beacon frame, probe response frame, or association response frame.

[0084] In one implementation, STA 808 may remain in a dozing state for a portion of a first time period after STA 808 transitions to a dozing state. In another implementation, STA 808 may be in a wake-up state at the end of the first time period or at least from the end of the first time period.

[0085] In one implementation, AP 802 may not send the third frame 822 to STA 808 during the first time period. AP 802 may send the third frame 822 to STA 808 after the first time period.

[0086] In one implementation, AP 802 and STA 808 can exchange indications of support for TXS Power Saving (PS) mode before the start of Example 800. For example, STA 808 can include an indication of TXS PS mode support in its association request frame to AP 802. STA 808 can set the TXS PS mode field (or TXS PS support field) to 1 in the association request frame to indicate support for TXS PS mode. The TXS PS mode field (or TXS PS support field) can be provided in the EHT MAC capability information field of the association request frame. AP 802 can include an indication of TXS PS mode support in its association response frame to STA 808. STA 808 can set the TXS PS mode field (or TXS PS support field) to 1 in the association response frame to indicate support for TXS PS mode. The TXS PS mode field (or TXS PS support field) can be provided in the EHT MAC capability information field of the association response frame.

[0087] In one implementation, when STA 808 indicates support for the TXS PS mode (e.g., by setting the TXS PS field to 1 in an association request frame to AP 802), AP 802 can avoid sending to STA 808 during a first time period (where STA 808 is not assigned a time slot), because STA 808 can enter a dormant state during the first time period (even if STA 808 is not actually dormant during the first time period). For any subsequent TXS time periods where STA 808 is not assigned a time slot, AP 802 can continue to use this behavior for STA 808. That is, based on the fact that STA 808 has indicated support for the TXS PS mode, AP 802 can refrain from sending to STA 808 during the TXS time periods where STA 808 is not assigned a time slot.

[0088] However, a recent revision of the 802.11be standard has proposed that, after a STA has finished transmitting its buffered traffic, the STA can return any remaining time of the time slot allocated to it to the AP (in TXS shared mode 2). The AP can use the remaining time of that time slot to transmit downlink traffic, or it can allocate a portion of the remaining time to another STA. For example, see reference... Figure 8 Assuming STA 804 has no further traffic to send after transmitting data frame 818, STA 804 can return the remaining time of the first time period after receiving BA frame 820 from STA 806. AP 802 can use the remaining time of the first time period (e.g., to STA 806 or 808) to send downlink traffic, or it can allocate a portion of the remaining time (e.g., to STA 806 or 808). According to the IEEE 802.11be standard revision, APs supporting this "TXOP return" feature can send an EHT MAC capability information field to the associated STA, where the "TXOP return support in TXOP sharing mode 2" subfield is set to 1. This indicates that the AP supports receiving frames (e.g., Quality of Service (QoS) data or QoS empty frames) from STAs allocated in TXS sharing mode 2, including HE variant HT control fields with CAS control subfields, where the RDG / More PPDU subfield is equal to 0. The AP can send PPDUs after SIFS following the receipt of a frame with CAS control subfields. Conversely, a STA receiving an MRTT frame with a TXOP shared mode subfield equal to 2 can, within the allocated time, send QoS data or a QoS empty frame, including a CAS control subfield with an RDG / more PPDU subfield equal to 0, to its associated AP, which has received an EHT capability element with a "TXOP return support in TXOP shared mode 2" subfield set to 1.

[0089] However, based on existing behavior, the AP can either not use the remaining time of the time period to send to a STA that indicates support for TXS PS mode and has not been allocated time during the time period, or allocate a portion of the remaining time to that STA. In fact, as mentioned above, when a STA indicates support for TXS PS mode and is not allocated time during the time period, the AP can choose not to send to the STA during that time period because the STA can enter a dormant state during that time period. For example, see reference... Figure 8 Assuming STA 808 indicates support for TXS PS mode to AP 802 (e.g., by setting the TXS PS field to 1 in an association request frame to AP 802), even if STA 804 returns the remaining time of the first time period to AP 802 after receiving BA frame 820, AP 802 may not send any data to STA 808 during the first time period (when STA 808 is not allocated a time slot). Similarly, AP 802 may not allocate a portion of the returned remaining time to STA 808. This could happen even if STA 808 does not enter a dozing state during the first time period.

[0090] This behavior can lead to inefficiency because the AP may be limited in how it can return the remaining time during the TXS period. For example, the AP may have buffered downlink traffic for an STA that was not allocated during the TXS period and has been instructed to support TXS PS mode. Although the STA can be awake during the TXS period, the AP must wait until the TXS period ends before it can send the buffered downlink traffic to the STA. In another example, the AP may want to share a portion of the returned remaining time with the STA. However, because the AP may not send any data to the STA during the TXS period, the AP may not send a time allocation to the STA even if the STA may be awake during the TXS period.

[0091] Figure 9 The first example 900 is shown, where the frame indicating whether to enable or disable TXS PS mode at the STA can be an association request frame or a reassociation request frame. For example... Figure 9 As shown, Example 900 includes AP 902 and STAs 904, 906, and 908. One or more of STAs 904, 906, and 908 may be associated with AP 902. STAs 904, 906, and / or 908 may support the TXS PS mode as described above.

[0092] like Figure 9As shown, Example 900 can begin with STA 908 sending an association (or reassociation) request frame 910 to AP 902. In one example, the association request frame 910 may include a TXS PS mode field (or a TXS PS support field). In Example 900, the TXS PS mode field (or TXS PS support field) can be set to 1 to indicate that TXS PS mode is enabled at STA 908. The TXS PS mode field (or TXS PS support field) can be provided in the EHT MAC capability information field of the association request frame. AP 902 can respond to the association request frame 910 by sending an association response frame 912 to STA 908. In one example, the association response frame 912 may include a TXS PS mode field (or a TXS PS support field). In Example 900, the TXS PS mode field (or TXS PS support field) can be set to 1 to indicate support for TXS PS mode at AP 902. The TXS PS mode field (or TXS PS support field) can be provided in the EHT MAC capability information field of the association response frame.

[0093] Subsequently, AP 902 can send frame 914 to allocate a portion of the acquired TXOP to STA 904. Frame 914 may include a TXOP sharing mode subfield, an AID 12 subfield, and a first time period (e.g., X us). The TXOP sharing mode subfield can indicate the triggering of the TXOP sharing process. For example, the TXOP sharing mode subfield can be set to a non-zero value (e.g., 1, 2, ...), indicating whether TXOP sharing mode 1 or TXOP sharing mode 2 is triggered. The AID 12 subfield can be set to the AID of the STA that can use the first time period to send and receive one or more frames. For example, the AID 12 subfield can be set to the AID of STA 904. The first time period can be specified in microseconds or some other unit of time. In one example, frame 914 may be an MRTT frame.

[0094] Upon receiving frame 914, STA 904 may send frame 99 to AP 902. In one example, frame 99 may be a CTS frame. STA 904 may then send a non-TB PPDU including data frame 918 to STA 906 during the first time period. STA 906 may send BA frame 920 to STA 904 in response to data frame 918.

[0095] Based on the receipt of frame 914 from an unassigned STA 908 during the first time period and the activation of TXSPS mode at STA 908, STA 908 can transition to a dormant state during the first time period. According to TXPS mode, STA 908 can transition to a dormant state in the following situations: after STA 908 receives frame 914 and before STA 908 receives frame 99 in response to frame 914; after STA 908 receives frame 99 in response to frame 914; or if STA 908 does not receive a third frame during a second time period after receiving frame 914. The third frame can be a data frame, control frame, or management frame. The value of the second time period can be a fixed value, or it can be signaled by a fourth frame transmitted by AP 902. The fourth frame can be a beacon frame, a probe response frame, or a correlation response frame.

[0096] In one implementation, STA 908 may remain in a dozing state for a portion of a first time period after STA 908 transitions to a dozing state. In one implementation, STA 908 may return to a wake-up state at the end of the first time period or at least from the end of the first time period. In one implementation, AP 902 may not send frames to STA 908 during the first time period. AP 902 may send frames to STA 908 after the first time period. In one example ( Figure 9 (Not shown in the image), AP 902 can receive a frame from STA 904 within a first time period indicating the release or return of the remaining time of the first time period. This frame may include a QoS data frame or a QoS empty frame, which includes an HE variant HT control field with a CAS control subfield having an RDG / More PPDU subfield equal to 0. Based on enabling TXS PS mode at STA 908, AP 902 can wait for the remaining time to end before sending a frame to STA 908. In one example, AP 902 can use the remaining time to send a frame to STA 904 or STA 906 (assuming STA 904 or STA 906 is in a wake-up state) or to another STA (…). Figure 9 As not shown, for example, a traditional STA that does not support TXS PS mode sends frames. In another example, AP 902 can allocate a portion of the remaining time to STA 906.

[0097] In Example 900, STA 908 may return to the wake-up state after or at least from the end of the first time period. STA 908 may then send an association (or reassociation) request frame 922 to AP 902. In one example, the association request frame 922 may include a TXS PS mode field (or a TXS PS support field). In Example 900, the TXS PS mode field (or TXS PS support field) may be set to 0 to indicate that TXS PS mode is disabled at STA 908. The TXS PS mode field (or TXS PS support field) may be provided in the EHT MAC capability information field of the association request frame 922. AP 902 may respond to the association request frame 922 by sending an association response frame 924 to STA 908. In one example, the association response frame 924 may include a TXS PS mode field (or a TXS PS support field). In Example 900, the TXS PS mode field (or TXS PS support field) may be set to 1 to indicate support for TXS PS mode at AP 902. The TXS PS mode field (or TXS PS support field) can be provided in the EHT MAC capability information field of the associated response frame.

[0098] Subsequently, AP 902 can send frame 926 to allocate a portion of the acquired TXOP to STA 904. Frame 926 may include a TXOP sharing mode subfield, an AID 12 subfield, and a first time period (e.g., X us). The TXOP sharing mode subfield can indicate the triggering of the TXOP sharing process. For example, the TXOP sharing mode subfield can be set to a non-zero value (e.g., 1, 2, ...), indicating whether TXOP sharing mode 1 or TXOP sharing mode 2 is triggered. The AID 12 subfield can be set to the AID of the STA that can use the first time period to send and receive one or more frames. For example, the AID 12 subfield can be set to the AID of STA 904. The first time period can be specified in microseconds or some other unit of time. In one example, frame 926 may be an MRTT frame.

[0099] Upon receiving frame 926, STA 904 may send frame 928 to AP 902. In one example, frame 99 may be a CTS frame. STA 904 may then send a non-TB PPDU including data frame 930 to STA 906 during the first time period. STA 906 may send BA frame 932 to STA 904 in response to data frame 930.

[0100] When frame 926, which does not allocate STA 908, is received during the first time period, and based on disabling TXS PS mode at STA 908, STA 908 can remain awake during the first time period. In one example ( Figure 9 (Not shown in the image) AP 902 can receive a frame from STA 904 within a first time period indicating the release or return of the remaining time of the first time period. This frame may include a QoS data frame or a QoS empty frame, which includes an HE variant HT control field with a CAS control subfield having an RDG / More PPDU subfield equal to 0. In one example, based on disabling the TXS PS mode at STA 908, AP 902 can send frames to STA 908 during the remaining time of the first time period. In another example, based on disabling the TXS PS mode at STA 908, AP 902 can allocate a portion of the remaining time to STA 908. Depending on the indicated TXS mode, STA 908 can use the allocated portion of the remaining time to send to AP 902 or to another STA.

[0101] The advantage of the first example is that it reuses an existing (re)association request / response frame (with minor modifications) to allow the STA to signal to the AP that TXS mode is enabled or disabled. However, the first example may result in increased signaling overhead because the (re)association request / response frame can be large in size due to containing information about the various capabilities supported by the STA / AP. The construction of the (re)association request / response frame may also require relatively large processing times at the STA / AP. The STA's signaling and the AP's confirmation of the TXS PS mode state change may therefore take a significant amount of time, leading to suboptimal operation.

[0102] In another example, the frame indicating whether TXS PS mode is enabled or disabled at the STA can be separate from the frame signaling support for TXS PS mode at the STA. In embodiments, the frame can be a QoS data frame, a QoS empty frame, an action frame, a control frame, or a management frame. The frame may include elements or subfields indicating whether TXS PS mode is enabled or disabled at the STA. Figure 10 Example 1000 illustrates such an embodiment. Figure 10 As shown, Example 1000 includes AP 1002 and STAs 1004, 1006, and 1008. One or more of STAs 1004, 1006, and 1008 may be associated with AP 1002. STAs 1004, 1006, and / or 1008 may support the TXS PS mode as described above.

[0103] Figure 10An example is shown where an association (or reassociation) request frame 1010 can begin, sent from STA 1008 to AP 1002. In one example, the association request frame 1010 may include a TXS PS mode field (or a TXS PS support field). In example 1000, the TXS PS mode field (or TXS PS support field) can be set to 1 to indicate that STA 1008 supports the TXS PS mode. The TXS PS mode field (or TXS PS support field) can be provided in the EHT MAC capability information field of the association request frame 1010.

[0104] In one implementation, STA 1008's support for TXS PS mode may include STA 1008's ability to perform TXS PS mode operation under defined conditions. In one implementation, TXS PS mode operation may include STA 1008 entering a dormant state during the TXOP period. Defined conditions may include AP 1002 not assigning STA 1008 during the TXOP period. In one implementation, STA 1008's support for TXS PS mode may include STA 1008's ability to send frames to AP indicating whether TXS PS mode is enabled or disabled, as described herein. In one embodiment, the frame may include a TXS PS (TPS) control subfield (further described below) indicating whether TXS PS mode is enabled or disabled at STA 1008. The TPS control subfield may include a TPS disable subfield carrying the indication whether TXS PS mode is enabled or disabled at STA 1008. In one implementation, STA 1008 support for TXS PS mode may include STA 1008 being able to enter a dozing state during a TXS period not assigned to STA 1008 (e.g., via MRTT frames) when STA 1008 sets the TPS disable subfield to 0.

[0105] AP 1002 can respond to association request frame 1010 by sending association response frame 1012 to STA 1008. In one example, association response frame 1012 may include a TXS PS mode field (or TXS PS support field). In example 1000, the TXS PS mode field (or TXS PS support field) can be set to 1 to indicate that AP 1002 supports TXS PS mode. The TXS PS mode field (or TXS PS support field) can be provided in the EHT MAC capability information field of association response frame 1012.

[0106] In one implementation, AP 1002's support for TXS PS mode may include AP 1002's ability to receive frames from STAs indicating whether TXS PS mode is enabled or disabled at the STA, as described herein. In one embodiment, the frame may include a TPS control subfield indicating whether TXS PS mode is enabled or disabled at the STA. The TPS control subfield may include a TPS disable subfield carrying an indication whether TXS PS mode is enabled or disabled at the STA. In one implementation, AP 1002's support for TXS PS mode may further include AP 1002's ability to send acknowledgments to the STA of frames indicating whether TXS PS mode is enabled or disabled at the STA. In one implementation, AP 1002's support for TXS PS mode may further include AP 1002's ability not to send (or avoid sending) any frames with the TPS disable subfield set to 0 during the TXS period when the TXS period is not allocated to the STA (e.g., via MRTT frames).

[0107] Subsequently, in one example, STA 1008 may send frame 1034 indicating that TXS PS mode is enabled at STA 1008. Frame 1034 may be a QoS data frame, a QoS empty frame, an action frame, a control frame, or a management frame. Frame 1034 may include elements or subfields that can be used to indicate whether TXS PS mode is enabled or disabled at STA 1008.

[0108] In one example, frame 1034 can be QoS data or a QoS empty frame. The QoS data or QoS empty frame may include an A-control field carrying an indication of enabling or disabling TXS PS mode at STA 1008. The A-control field can be carried in the HT control field of the QoS data frame or the QoS empty frame. In one embodiment, the A-control field may include a TPS control subfield. The TPS control subfield may include a TPS disable subfield. The TPS disable subfield can be set to 0 to indicate that TXS PS mode is enabled at STA 1008, and can be set to 1 to indicate that TXS PS mode is disabled at STA 1008. The TPS control subfield may also include reserved bits.

[0109] In another example, frame 1034 may be an action frame. An action frame may include elements / fields indicating whether TXS PS mode is enabled or disabled at STA 1008. In one example, the action frame may be an EML operation mode notification frame. In one embodiment, the action frame may include a TPS disable subfield. The TPS disable subfield may be set to 0 to indicate that TXS PS mode is enabled at STA 1008, and may be set to 1 to indicate that TXS PS mode is disabled at STA 1008. The TPS control subfield may also include reserved bits.

[0110] In one implementation, AP 1002 can acknowledge frame 1034 by sending acknowledgment frame 1036 to STA 1008. Acknowledgment frame 1036 can be an ACK frame or a BA frame.

[0111] Subsequently, AP 1002 may send frame 1014 to allocate a portion of the acquired TXOP to STA 1004. Frame 1014 may include a TXOP sharing mode subfield, an AID 12 subfield, and a first time period (e.g., X us). The TXOP sharing mode subfield may indicate the triggering of the TXOP sharing process. For example, the TXOP sharing mode subfield may be set to a non-zero value (e.g., 1, 2, ...), indicating whether TXOP sharing mode 1 or TXOP sharing mode 2 is triggered. The AID 12 subfield may be set to the AID of the STA that can use the first time period to send and receive one or more frames. For example, the AID 12 subfield may be set to the AID of STA 1004. The first time period may be specified in microseconds or some other unit of time. In one example, frame 1014 may be an MRTT frame.

[0112] Upon receiving frame 1014, STA 1004 may send frame 1016 to AP 1002. In one example, frame 1016 may be a CTS frame. STA 1004 may then send a non-TBPPDU including data frame 1018 to STA 1006 during a first time period. STA 1006 may send BA frame 1020 to STA 1004 in response to data frame 1018.

[0113] Based on the receipt of frame 1014 from an unassigned STA 1008 during the first time period and the activation of TXS PS mode at STA 1008, STA 1008 may transition to a dormant state during the first time period. According to TX PS mode, STA 1008 may transition to a dormant state in the following situations: after STA 1008 receives frame 1014 and before STA 1008 receives frame 1016 in response to frame 1014; after STA 1008 receives frame 1016 in response to frame 1014; or if STA 1008 does not receive a third frame during a second time period after receiving frame 1014. The third frame may be a data frame, control frame, or management frame. The value of the second time period may be a fixed value, or it may be signaled by a fourth frame sent by AP 1002. The fourth frame may be a beacon frame, a probe response frame, or a correlation response frame.

[0114] In one implementation, STA 1008 may remain in a dozing state for a portion of a first time period after STA 1008 transitions to a dozing state. In one implementation, STA 1008 may return to a wake-up state at the end of the first time period or at least from the end of the first time period. In one implementation, AP 1002 may not send frames to STA 1008 during the first time period. AP 1002 may send frames to STA 1008 after the first time period. In one example ( Figure 10 (Not shown in the image), AP 1002 can receive a frame from STA 1004 within a first time period indicating the release or return of the remaining time of the first time period. This frame may include a QoS data frame or a QoS empty frame, which includes an HE variant HT control field with a CAS control subfield having an RDG / More PPDU subfield equal to 0. Based on enabling TXS PS mode at STA 1008, AP 1002 can wait for the remaining time to end before sending a frame to STA 1008. In one example, AP 1002 can use the remaining time to send a frame to STA 1004 or STA 1006 (assuming STA 1004 or STA 1006 is in a wake-up state) or to another STA (…). Figure 10 (Not shown, for example, a traditional STA that does not support TXS PS mode) sends frames. In another example, AP 1002 can allocate a portion of the remaining time to STA 1006.

[0115] In Example 1000, STA 1008 may return to the wake-up state after or at least from the end of the first time period. Subsequently, STA 1008 may send frame 1038 indicating that the TXS PS mode is disabled at STA 1008. Frame 1038 may be a QoS data frame, a QoS empty frame, an action frame, a control frame, or a management frame. Frame 1038 may include elements or subfields that can be used to indicate whether the TXS PS mode is enabled or disabled at STA 1008. In one example, frame 1038 may be QoS data or a QoS empty frame. QoS data or a QoS empty frame may include an A-control field carrying an indication to enable or disable the TXS PS mode at STA 1008. The A-control field may be carried in the HT control field of the QoS data frame or the QoS empty frame. In another example, frame 1038 may be an action frame. An action frame may include elements / fields indicating whether the TXS PS mode is enabled or disabled at STA 1008. In one example, the action frame may be an EML operation mode notification frame.

[0116] In one implementation, AP 1002 can acknowledge frame 1038 by sending acknowledgment frame 1040 to STA 1008. Acknowledgment frame 1040 can be an ACK frame or a BA frame.

[0117] Subsequently, AP 1002 can send frame 1026 to allocate a portion of the acquired TXOP to STA 1004. Frame 1026 may include a TXOP sharing mode subfield, an AID 12 subfield, and a first time period (e.g., X us). The TXOP sharing mode subfield can indicate the triggering of the TXOP sharing process. For example, the TXOP sharing mode subfield can be set to a non-zero value (e.g., 1, 2, ...), indicating whether TXOP sharing mode 1 or TXOP sharing mode 2 is triggered. The AID 12 subfield can be set to the AID of the STA that can use the first time period to send and receive one or more frames. For example, the AID 12 subfield can be set to the AID of STA 1004. The first time period can be specified in microseconds or some other unit of time. In one example, frame 1026 may be an MRTT frame.

[0118] Upon receiving frame 1026, STA 1004 may send frame 1028 to AP 1002. In one example, frame 1016 may be a CTS frame. STA 1004 may then send a non-TBPPDU including data frame 1030 to STA 1006 during the first time period. STA 1006 may send BA frame 1032 to STA 1004 in response to data frame 1030.

[0119] When frame 1026 is received during the first time period and STA 1008 is not assigned, and based on disabling TXS PS mode at STA 1008, STA 1008 can remain awake during the first time period. In one example ( Figure 10 (Not shown in the image) AP 1002 can receive a frame from STA 1004 during a first time period indicating the release or return of the remaining time of the first time period. This frame may include a QoS data frame or a QoS empty frame, which includes an HE variant HT control field with a CAS control subfield having an RDG / More PPDU subfield equal to 0. In one example, based on disabling the TXS PS mode at STA 1008, AP 1002 can send frames to STA 1008 during the remaining time of the first time period. In another example, based on disabling the TXS PS mode at STA 1008, AP 1002 can allocate a portion of the remaining time to STA 1008. Depending on the indicated TXS mode, STA 1008 can use the allocated portion of the remaining time to send to AP 1002 or to another STA.

[0120] Figure 10Another advantage illustrated is the reduction in signaling overhead and latency for the STA to signal the AP about the TXS PS mode state change at the STA. As mentioned above, the TXS PS mode state change can be carried in various frame types and is not limited to association request frames. For example, the TXS PS mode state change can be carried in QoS data / empty frames or short action frames. The AP can respond to frames from the STA using short acknowledgment frames instead of relatively large association response frames.

[0121] In yet another example, similar to the previous embodiment, the AP can request the TXS PS mode status at the STA. The STA can respond to the request from the AP by sending a frame to the AP indicating whether TXS PS mode is enabled or disabled at the STA. In one embodiment, the AP can send a frame requesting the TXS PS mode status at the STA before initiating TXS operation. Figure 11 Example 1100 illustrates such an embodiment. (As shown) Figure 11 As shown, Example 1100 includes AP 1102 and STAs 1104, 1106, and 1108. One or more of STAs 1104, 1106, and 1108 may be associated with AP 1102. STAs 1104, 1106, and / or 1108 may support the TXS PS mode as described above.

[0122] Figure 11 Example 1100 of an existing operation is shown, in which the STA can enter a napping state during the TXOP time period. Figure 11 As shown, Example 1100 may begin with STA 1108 sending an association (or reassociation) request frame 1110 to AP 1102. In one example, the association request frame 1110 may include a TXS PS mode field (or a TXS PS support field). In Example 1100, the TXS PS mode field (or TXS PS support field) may be set to one (1) to indicate that STA 1108 supports the TXS PS mode. The TXS PS mode field (or TXS PS support field) may be provided in the EHT (or Ultra High Reliability (UHR)) MAC capability information field of the association request frame 1110.

[0123] In one implementation, STA 1108's support for TXS PS mode may include STA 1108's ability to perform TXS PS mode operation under defined conditions. In one implementation, TXS PS mode operation may include STA 1108 entering a dormant state during the TXOP period. Defined conditions may include STA 1108 not being assigned by AP 1102 during the TXOP period. In one implementation, STA 1108's support for TXS PS mode may include STA 1108's ability to send frames to AP indicating whether TXS PS mode is enabled or disabled, as described herein. In one embodiment, the frame may include a TPS control subfield indicating whether TXS PS mode is enabled or disabled at STA 1108. The TPS control subfield may include a TPS disable subfield carrying an indication of whether TXS PS mode is enabled or disabled at STA 1108. In one implementation, STA 1108 support for TXS PS mode may include STA 1108 being able to enter a dozing state during a TXS period not assigned to STA 1108 (e.g., via MRTT frames) when STA 1108 sets the TPS disable subfield to 0.

[0124] AP 1102 can respond to association request frame 1110 by sending association response frame 1112 to STA 1108. In one example, association response frame 1112 may include a TXS PS mode field (or TXS PS support field). In example 1100, the TXS PS mode field (or TXS PS support field) may be set to one (1) to indicate that AP 1102 supports TXS PS mode. The TXS PS mode field (or TXS PS support field) may be provided in the EHT (or UHR) MAC capability information field of association response frame 1112.

[0125] In one implementation, AP 1102's support for TXS PS mode may include AP 1102's ability to receive frames from STAs indicating whether TXS PS mode is enabled or disabled at the STA, as described herein. In one embodiment, the frame may include a TPS control subfield indicating whether TXS PS mode is enabled or disabled at the STA. The TPS control subfield may include a TPS disable subfield carrying an indication of whether TXS PS mode is enabled or disabled at the STA. In one implementation, AP 1102's support for TXS PS mode may further include AP 1102's ability to send an acknowledgment to the STA of the frame indicating whether TXS PS mode is enabled or disabled at the STA. In one implementation, AP 1102's support for TXS PS mode may further include AP 1102's ability not to send (or avoid sending) any frames during the TXS period to STAs that have the TPS disable subfield set to 0 (when the TXS period is not allocated to the STA, e.g., via MRTT frames).

[0126] Subsequently, in one example, AP 1102 may send frame 1138 to STA 1108 requesting the TXS PS mode status at STA 1108. Frame 1138 may be a control frame, management frame, or action frame. In one embodiment, AP 1102 may send frame 1138 to STA 1108 before initiating TXS operation. In example 1100, STA 1108 may respond to frame 1138 by sending frame 1134 to AP 1102, indicating that TXS PS mode is enabled at STA 1108. Frame 1134 may be a QoS data frame, QoS empty frame, action frame, control frame, or management frame. Frame 1134 may include elements or subfields that can be used to indicate whether TXS PS mode is enabled or disabled at STA 1108.

[0127] In one example, frame 1134 can be QoS data or a QoS empty frame. QoS data or a QoS empty frame may include an A-control field carrying an indication to enable or disable TXS PS mode at STA 1108. The A-control field may be carried in the HT control field of the QoS data frame or the QoS empty frame. In one embodiment, the A-control field may include a TPS control subfield.

[0128] In another example, frame 1134 may be an action frame. An action frame may include elements / fields indicating whether TXS PS mode is enabled or disabled at STA 1108. In one example, the action frame may be an EML operation mode notification frame. In one embodiment, the action frame may have the features described above. Figure 20 The format shown.

[0129] In one implementation, AP 1102 can acknowledge frame 1134 by sending an acknowledgment frame 1136 to STA 1108. The acknowledgment frame 1136 can be an ACK frame or a BA frame. In additional or alternative embodiments, STA 1108 can send frame 1134 without receiving frame 1138 from AP 1102, for example, to indicate that TXS PS mode is enabled at STA 1108. In one example, STA 1108 can enable TXS PS mode when it receives acknowledgment frame 1136 from AP 1102 in response to frame 1134.

[0130] Subsequently, AP 1102 can send frame 1114 to allocate a portion of the acquired TXOP to STA 1104. Frame 1114 may include a TXOP sharing mode subfield, an AID 12 subfield, and a first time period (e.g., X us). The TXOP sharing mode subfield can indicate the triggering of the TXOP sharing process. For example, the TXOP sharing mode subfield can be set to a non-zero value (e.g., 1, 2, ...), indicating whether TXOP sharing mode 1 or TXOP sharing mode 2 is triggered. The AID 12 subfield can be set to the AID of the STA that can use the first time period to send and receive one or more frames. For example, the AID 12 subfield can be set to the AID of STA 1104. The first time period can be specified in microseconds or some other unit of time. In one example, frame 1114 may be an MRTT frame.

[0131] Upon receiving frame 1114, STA 1104 may send frame 1116 to AP 1102. In one example, frame 1116 may be a CTS frame. STA 1104 may then send a non-TBPPDU including data frame 1111 to STA 1106 during a first time period. STA 1106 may send BA frame 1120 to STA 1104 in response to data frame 1111.

[0132] Based on the receipt of frame 1114 from an unassigned STA 1108 during the first time period and the activation of TXS PS mode at STA 1108, STA 1108 may transition to a dormant state during the first time period. According to TX PS mode, STA 1108 may transition to a dormant state in the following situations: after STA 1108 receives frame 1114 and before STA 1108 receives frame 1116 in response to frame 1114; after STA 1108 receives frame 1116 in response to frame 1114; or if STA 1108 does not receive a third frame during a second time period after receiving frame 1114. The third frame may be a data frame, control frame, or management frame. The value of the second time period may be a fixed value, or it may be signaled by a fourth frame transmitted by AP 1102. The fourth frame may be a beacon frame, a probe response frame, or a correlation response frame.

[0133] In one implementation, STA 1108 may remain in a dozing state for a portion of a first time period after STA 1108 transitions to a dozing state. In one implementation, STA 1108 may return to a wake-up state at the end of the first time period or at least from the end of the first time period. In one implementation, AP 1102 may not send frames to STA 1108 during the first time period. AP 1102 may send frames to STA 1108 after the first time period. In one example ( Figure 11 (Not shown in the image), AP 1102 can receive a frame from STA 1104 within a first time period indicating the release or return of the remaining time of the first time period. This frame may include a QoS data frame or a QoS empty frame, which includes an HE variant HT control field with a CAS control subfield having an RDG / More PPDU subfield equal to 0. Based on enabling TXS PS mode at STA 1108, AP 1102 can wait for the remaining time to end before sending a frame to STA 1108. In one example, AP 1102 can use the remaining time to send a frame to STA 1104 or STA 1106 (assuming STA 1104 or STA 1106 is awake) or to another STA (…). Figure 11 (Not shown, for example, a conventional STA that does not support TXS PS mode) sends frames. In another example, AP 1102 can allocate a portion of the remaining time to STA 1106.

[0134] Figure 12 Example 1200 of existing operation is shown, in which the STA can enter a nap state during TWT SP. Figure 12As shown, Example 1200 includes AP 1202 and STA 1206. STA 1206 may be associated with AP 1202. In this example, STA 1206 may negotiate a specific target wake-up time (e.g., TWT SP 1250) with AP 1202 to wake up and be able to communicate with AP 1202, which may facilitate STA 1206 entering a low-power sleep mode (e.g., nap state 1230) to conserve battery life.

[0135] like Figure 12 As shown, Example 1200 can begin with AP 1202 sending a downlink (DL) frame 1210-1 to STA 1206 during TWT SP 1250. In Example 1200, DL frame 1210-1 may include an indication that the SP has not yet ended, for example, the service session has ended (EOSP=0). STA 1206 may respond to DL frame 1210-1 by sending a BA frame 1220-1 to AP 1202.

[0136] Subsequently, in Example 1200, AP 1202 may send another DL frame 1210-2 to STA 1206, and DL frame 1210-2 may include an indication that SP has ended, for example, EOSP=1. STA 1206 may send a BA frame 1220-2 to AP 1202 in response to DL frame 1210-2. In this example of TWT power-saving operation, during TWT SP 1250, the TWT-scheduled STA 1206 may enter a dozing state 1230 if there is no indication of additional traffic from AP 1202, for example, a frame such as DL frame 1210-1 with the EOSP=1 indication discussed above, and / or an indication that no more data is coming (MD=0). As depicted, in this example, STA 1206's dozing state 1230 continues until the end of TWT SP 1250.

[0137] Figure 13 Example 1300 illustrates an example TXS procedure. (Example 1300 is shown.) Figure 13 As shown, Example 1300 includes AP 1310, and STAs 1311 and 1312 can be associated with AP 1310. As... Figure 13 As shown, Example 1300 can begin with AP 1310 sending MRTT frame 1315 to allocate a portion of the acquired TXOP 1355 to STA 1311. MRTT frame 1315 specifies the TXOP sharing mode (e.g., TXS sharing mode 2 for communication between STAs 1311 and 1312), and the allocation duration of the portion of the TXOP allocated to STA 1311, for example, in Figure 13 The duration is 1365 as shown in the figure.

[0138] Upon receiving MRTT frame 1315, STA 1311 may send CTS frame 1340 to AP 1310. STA 1311 may then send one or more non-TB PPDUs to STA 1312, such as non-TB PPDUs 1360-1 and 1360-2. In this example, STA 1312 may respond to non-TB PPDUs 1360-1 and 1360-2 by sending one or more BA frames 1320-1 and 1313-2 to STA 1311.

[0139] In this example, for STA 1311, after receiving BA 1320-2, STA does not have any additional frames to send to STA 1312. For example... Figure 13 As shown, because STA 1311 is operating in TXS shared mode 2 and has completed transmitting its buffered traffic during the allocated duration 1365 and / or TXOP 1355, STA 1311 can return any remaining time of the allocated duration 1365 allocated to STA 1311 to the AP. One way to return the remaining allocated time, as shown, is to send an indication to AP 1310 to return the time. In this example, the indication can be sent using a QoS data frame (not shown) or a QoS empty frame 1370.

[0140] In the implementation of QoS empty frame 1370, the frame includes an HE variant HT control field with a CAS control subfield, where the RDG / More PPDU subfield is equal to 0 for the associated AP (e.g., AP 1310). Discussing this in more detail, the HE variant HT control field can be a field within the MAC header of QoS empty frame 1370 that includes control information specific to High Efficiency (HE) operation, and "HT" refers to High Throughput (as described in 802.11n). The HE variant HT control field specifies that the frame structure supports HT features but has been extended or modified to support HE capabilities. The HT control field with a CAS control subfield refers to the Command and Status (CAS) control subfield of the HT control field. RDG stands for "Reverse Authorization," which specifies that the receiver of the frame can respond without having to contend for the medium again. Because the RDG / More PPDU subfield is set to zero (0) in this example, this indicates that this mechanism is not used for QoS empty frame 1370, and there are no PPDUs to be sent in the reverse direction after receiving QoS empty frame 1370.

[0141] In this example, although an indication is transmitted using QoS empty frame 1370 and acknowledgment frame 1330 from AP 1310, there is no provision that would allow STA 1311 to enter a dozing state, for example, as described above. Figure 12The description of the dozing state is shown in 1230. Therefore, as... Figure 13 As shown, STA 1311 does not enter low-power mode during the remainder of TXOP 1355. For example, STA 1311 remains in wake state 1335 until TXOP 1355 ends.

[0142] In this example, because the STA 1311 assigned to TXS will be in a wake-up state 1335 during the remaining TXS allocation duration 1365 or the remaining TXOP 1355, the power consumption of the STA 1311 assigned to TXS will increase, especially when there is no DL / UL service for the STA 1311 assigned to TXS. Figure 13 As shown.

[0143] As further described below, embodiments of this disclosure address the aforementioned problems of existing TXS operations. In one aspect, the STA can receive from the AP a first frame indicating a first time period of TXOP allocated to the STA and a shared mode of the first time period. The STA can send a second frame to the AP during the first time period, the second frame instructing the STA to return the first time period to the AP. After sending the second frame, the STA can transition from a first power state to a second power state based on the shared mode in a power-saving mode. In another embodiment, after sending the second frame, the STA may be unavailable in an active mode, for example, unavailable from a first power state input based on the shared mode. In this example context, an unavailable STA cannot receive PPDUs. In one embodiment, the first power state corresponds to the wake-up state of the STA in a power-saving or active mode, while the second power state corresponds to the STA's dozing state in a power-saving mode, the second power state corresponds to the STA being unavailable in an active mode, or the second power state corresponds to the STA's listening state in a power-saving mode. In one embodiment, the STA can transition from a first power state to a second power state based on the shared mode, which means the STA can transition from a first power state to a second power state according to the mode of its communication with a peer STA (e.g., TXS shared mode 2). Therefore, the STA can avoid unnecessary and wasteful lingering in the wake-up state after returning the first time period to the AP.

[0144] Figure 14 Example 1400 illustrates one or more embodiments that can utilize power-saving operations during the TXS process. (e.g.) Figure 14As shown, Example 1400 includes AP 1410 and STAs 1411 and 1412 associated with AP 1410. Example 1400 may begin with AP 1410 sending MRTT frame 1415 to specify an allocation duration 1465 for the acquired TXOP 1455 to be allocated to STA 1411. In this example, MRTT frame 1415 specifies a TXOP sharing mode of 2 (e.g., for communication between STAs 1411 and 1412) and a value corresponding to the allocation duration 1465.

[0145] Upon receiving MRTT frame 1415, STA 1411 may send CTS frame 1440 to AP 1410. Depending on the allocated duration 1465, STA 1411 may subsequently send non-TB PPDUs 1460-1 and 1460-2 to STA 1412, wherein STA 1412 responds to the non-TB PPDUs 1460-1 and 1460-2 by sending one or more BA frames 1420-1 and 1420-2 to STA 1411, respectively. In one or more embodiments, to indicate to AP 1410 that no additional data needs to be transmitted from STA 1411 to STA 1412, STA 1411 may send a QoS empty frame 1470 to AP 1410. In response to the QoS empty frame 1470, AP 1410 may respond with an acknowledgment frame 1435.

[0146] Continuing with this example embodiment, after transmitting a QoS empty frame 1470 to AP 1410 and STA 1411 receiving an acknowledgment frame 1435 from AP 1410, STA 1411 can allocate a duration of 1465 (in Figure 14 Depicted as a drowsy state (1430-1) or TXOP 1455 (in Figure 14 The second power state (e.g., nap state) is entered during the remaining duration of the nap state (described as 1430-2). Therefore, one or more embodiments can solve the aforementioned problems that may be associated with the STA assigned a TXS unnecessarily and wastefully remaining in an awake state, for example, as described above. Figure 13 The subject of discussion.

[0147] As implemented, one or more embodiments may facilitate entry into one of the nap states 1430-1 and 1430-2 (hereinafter collectively referred to as "nap state 1430") based on one or more combinations of conditions (e.g., conditions that facilitate improved operation of the network). For example, to facilitate the use of nap state 1430 in an embodiment, STA 1411 is scheduled by an MRTT frame 1415 addressed to STA 1411. To further facilitate the use of nap state 1430, STA 1411 indicates to AP 1410 the return of the remaining TXS allocation duration, for example, by transmitting a QoS empty frame 1470 to AP 1410.

[0148] In another example embodiment of the STA operating according to the disclosure herein, example 1400 may begin with the STA (e.g., STA 1411) receiving a first frame (e.g., MRTT frame 1415) from the AP (e.g., AP 1410) indicating a first time period (e.g., allocation duration 1465) of a TXOP allocated to the STA and a sharing mode for the first time period (e.g., TXS sharing mode 2). Continuing this example, the STA may send a second frame (e.g., QoS empty frame 1470) during this time period, instructing the STA to return the first time period to the AP.

[0149] In another aspect of this example, after sending the second frame, the STA can transition from a first power state (e.g., STA 1411 is in an active state) to a second power state (e.g., STA 1411 enters a dozing state 1430) based on a sharing mode (e.g., TXS sharing mode 2). In one implementation, the first power state may correspond to the wake-up state of the STA in power-saving mode or active mode, while the second power state may correspond to the dozing state in power-saving mode.

[0150] In an example embodiment of an AP operating according to the disclosure herein, example 1400 may begin with the AP (e.g., AP 1410) sending a first frame to the STA (e.g., STA 1411) indicating a first time period of a TXOP allocated to the STA (e.g., allocation duration 1465 of TXOP 1455) and a sharing mode for the first time period (e.g., TXS sharing mode 2). Continuing with this AP example, example 1400 may include a second frame (e.g., a QoS empty frame 1470 or a QoS data frame) received by the AP from the STA during the first time period, the second frame instructing the STA to return the first time period to the AP. In an additional embodiment, the QoS empty frame 1470 (or the QoS data frame) may include an HE variant HT control field with a CAS control subfield having an RDG / more PPDU subfield equal to 0.

[0151] Based on the sharing mode (e.g., TXS sharing mode 2) and the second frame, the AP can receive a third frame from STA 1411 during a first time period. This third frame includes a first indication that STA 1411 is (or has) transitioned from a first power state (e.g., STA 1411 is in an active state) to a second power state (e.g., STA 1411 enters a dozing state 1430).

[0152] As shown below Figure 15-19 Further discussed, in one implementation, based on the use of the nap state 1430 according to one or more embodiments, AP 1410 may be restricted to different combinations of operations that AP 1410 can perform during the time STA 1411 is in nap state 1430. For example, according to one or more embodiments, AP 1410 may be restricted from sending any frames to STA 1411 for the remaining duration of the allocated duration 1465 (e.g., for nap state 1430-1) or TXOP 1455 (e.g., for nap state 1430-2). Continuing with the example embodiments of the AP discussed above, AP 1410 may be restricted from sending any frames to STA 1411 for the remaining duration of the allocated duration 1465 and / or TXOP 1455. Upon the end of the allocated duration 1465 and / or TXOP 1455, AP 1410 may not be restricted from transmitting any frames to STA 1411.

[0153] In an alternative embodiment, after transmitting a QoS empty frame 1470 to AP 1410 and STA 1411 receiving an acknowledgment frame 1435 from AP 1410, STA 1411 may enter a second power state corresponding to unavailability for the remaining duration (e.g., the remaining duration of allocation duration 1465 or TXOP 1455). In this context, an unavailable STA cannot receive PPDUs.

[0154] Figure 15 Example 1500 is shown, illustrating one or more embodiments that can utilize power-saving operations during the TXS process. (e.g.) Figure 15 As shown, Example 1500 includes AP 1510, and STA 1511 and 1512 can be associated with AP 1510.

[0155] Example 1500 may begin with AP 1510 sending MRTT frame 1515 to specify an allocation duration 1565 for the acquired TXOP 1555 to be allocated to STA 1511. In this example, MRTT frame 1515 specifies a TXOP sharing mode of 2 (e.g., for communication between STAs 1511 and 1512), a value corresponding to the allocation duration 1565, and potentially, as described below, MRTT frame 1515 may include information corresponding to indication 1517-1 (allowing the use of TXS PS).

[0156] Upon receiving MRTT frame 1515, STA 1511 may send CTS frame 1540 to AP 1510. Based on the allocated duration 1565, STA 1511 may subsequently send non-TB PPDUs 1560-1 and 1560-2 to STA 1512, wherein STA 1512 responds to STA 1511 with one or more BA frames 1520-1 and 1520-2, respectively. In one or more embodiments, to indicate to AP 1510 that no additional data needs to be transmitted from STA 1511 to STA 1512, STA 1511 may send a QoS empty frame 1570 to AP 1510.

[0157] In additional or alternative embodiments, at different points in the communication sequence between AP 1510 and STA 1511, AP 1510 may analyze different factors associated with whether STA 1511 should be allowed to enter a nap state. Examples of factors that can be evaluated to support allowing STA 1511 to enter a nap state include, but are not limited to: AP 1510 not having buffered traffic for STA 1511; AP 1510 having non-low-latency buffered traffic for STA 1511, and AP 1510 having low-latency buffered traffic for another STA associated with AP 1510; and / or AP 1510 having buffered traffic for STA 1511, but AP 1510 having traffic that is more urgent than the buffered traffic for the other STA associated with AP 1510.

[0158] In some implementations, the method of transmitting this determination may utilize frames transmitted from AP 1510 to STA 1511, such as trigger frames, immediate response frames (e.g., Ack frames or BlockAck (BA) frames), control frames, management frames, action frames, QoS data frames, and / or QoS empty frames, or more of these. Examples of using MRTT frame 1515 and immediate response frames (e.g., acknowledgment frame 1535) are described below. In one or more embodiments, when the embodiments described herein utilize trigger frames, the trigger frame may be an MRTT trigger frame.

[0159] An example point in the communication sequence between AP 1510 and STA 1511 includes a point prior to the transmission of MRTT frame 1515 from AP 1510 to STA 1511. In this example, when AP 1510 determines that STA 1511 is allowed to use TXS power-saving operation, an indication 1517-1 (allow TXS PS) to STA 1511 can be included with MRTT frame 1515, and this indication can allow STA 1511 to enter a slumber state (e.g., slumber state 1530-1 or slumber state 1530-2, hereinafter collectively referred to as "slumber state 1530") according to the embodiments described herein. Alternatively, when indication 1517-1 corresponds to a determination that STA 1511 is not allowed to use a slumber state, according to the embodiments described herein, this indication included with MRTT frame 1515 can instruct STA 1511 not to enter a slumber state (e.g., slumber state 1530-1 or slumber state 1530-2).

[0160] Alternative example points in the communication sequence between AP 1510 and STA 1511 include the point after AP 1510 receives QoS empty frame 1570 and before AP 1510 sends acknowledgment frame 1535 to STA 1511 in response to QoS empty frame 1570. In this example, AP 1510 may collect and analyze additional information to determine whether the slumber state 1530 is permitted. As depicted, when the power-saving operation discussed herein is permitted, an indication 1517-2 (TXSPS allowed) may be included along with acknowledgment frame 1535, and subsequent operations of STA 1511 may be controlled according to this indication.

[0161] The acknowledgment frame 1535 (or BA, not shown) includes an indication 1517-2 of a method that allows the use of the More Data (MD) subfield of the Ack or BA frame. When this currently available subfield is set to zero (0), this can be used to indicate to STA 1511 that no more data is available from AP 1510 to STA 1511, and thus allow the use of dozing state 1530. Conversely, according to one or more embodiments, the MD subfield of the acknowledgment frame 1535 can be set to one (1) to indicate to STA 1511 that more data is available from AP 1510 to STA 1511, and thus disallow the use of dozing state 1530.

[0162] Another method for transmitting information related to the use of the TXS SP procedure to the STA 1511 can be by utilizing the buffered traffic indication subfield of immediate response frames, control frames, management frames, action frames, and / or QoS empty / data frames. Yet another method for transmitting information related to the use of the TXS SP procedure to the STA 1511 can be by utilizing the SIG field (e.g., U-SIG, UHR-SIG, etc.) of the preamble of the PPDU carrying this field. The following is in conjunction with... Figure 20 These additional methods will be discussed in more detail.

[0163] Figure 16 Example 1600 is shown that utilizes power-saving operations during a TXS process according to one or more embodiments. Figure 16 As shown, Example 1600 includes AP 1610, and STAs 1611 and 1612 may be associated with AP 1610. Example 1600 may begin with AP 1610 sending MRTT frame 1615 to specify an allocation duration 1665 for the acquired TXOP 1655 to be allocated to STA 1611. In this example, MRTT frame 1615 specifies a TXOP sharing mode of 2 (e.g., for communication between STAs 1611 and 1612), and a value corresponding to the allocation duration 1665.

[0164] Upon receiving MRTT frame 1615, STA 1611 may send CTS frame 1640 to AP 1610. Based on the allocated duration 1665, STA 1611 may subsequently send non-TB PPDUs 1660-1 and 1660-2 to STA 1612, wherein STA 1612 responds to non-TB PPDUs 1660-1 and 1660-2 by sending one or more BA frames 1620-1 and 1620-2 to STA 1611, respectively. In one or more embodiments, to indicate to AP 1610 that no additional data needs to be transmitted from STA 1611 to STA 1612, STA 1611 may send a QoS empty frame 1670 to AP 1610.

[0165] As mentioned above Figure 14 As described above, when STA 1611 is utilizing TXS power-saving operation, one or more embodiments can limit the operation of AP 1610. To achieve these limitations, in Figure 16In the additional or alternative embodiments depicted, STA 1611 may use QoS empty frame 1670 to further indicate to AP 1610 whether STA 1611 is transitioning from a first power state (e.g., a wake-up state) to a second power state (e.g., a dozing state 1630-1 or 1630-2, or an unavailable state) during the remaining duration (e.g., allocated duration 1665 or TXOP 1655). Figure 16 As shown, indication 1671 (TXS PS notification) can be transmitted to AP 1610 along with QoS empty frame 1670, and based on indication 1671, AP 1610 can determine not to send any frames to STA 1611 during the remaining duration of allocated duration 1665 or TXOP 1655.

[0166] Continuing this example, in response to QoS empty frame 1670, AP 1610 can respond with acknowledgment frame 1635. After transmitting QoS empty frame 1670 to AP 1610, AP 1610 receiving indication 1671, and STA 1611 receiving acknowledgment frame 1635 from AP 1610, AP 1610 can restrict communication to STA 1611, and STA 1611 can enter a second power state (e.g., dozing state 1630-1 or 1630-2 or unavailable state) for the remaining duration (e.g., allocated duration 1665 or TXOP 1655).

[0167] Figure 17 Example 1700 illustrates one or more embodiments that can utilize power-saving operations during the TXS process. (e.g.) Figure 17 As shown, Example 1700 includes AP 1710 and STAs 1711 and 1712 associated with AP 1710.

[0168] Example 1700 may begin with AP 1710 sending MRTT frame 1715 to specify an allocation duration 1765 for the acquired TXOP 1755 to be allocated to STA 1711. In this example, MRTT frame 1715 specifies a TXOP sharing mode of 2 (e.g., for communication between STAs 1711 and 1712), a value corresponding to the allocation duration 1765, and potentially, as described below, MRTT frame 1715 may include information corresponding to indication 1717 (allowing the use of TXS PS).

[0169] Upon receiving MRTT frame 1715, STA 1711 may send CTS frame 1740 to AP 1710. Based on the allocated duration 1765, STA 1711 may subsequently send non-TB PPDUs 1760-1 and 1760-2 to STA 1712, wherein STA 1712 responds to non-TB PPDUs 1760-1 and 1760-2 by sending one or more BA frames 1720-1 and 1720-2 to STA 1711, respectively. In one or more embodiments, to indicate to AP 1710 that no additional data needs to be transmitted from STA 1711 to STA 1712, STA 1711 may send a QoS empty frame 1770 to AP 1710.

[0170] As described above Figure 17 As discussed, in one or more embodiments, AP 1710 may analyze various factors associated with whether STA 1711 should be allowed to enter nap state 1730-1 or nap state 1730-2 (collectively, "nap state 1730"). Examples of factors that can be evaluated to support allowing STA 1711 to enter nap state 1730 include, but are not limited to: AP 1710 not having buffered traffic for STA 1711; AP 1710 having non-low-latency buffered traffic for STA 1711; and AP 1710 having low-latency buffered traffic for another STA associated with AP 1710; and / or AP 1710 having buffered traffic for STA 1711, but AP 1710 having traffic that is more urgent than the buffered traffic for the other STA associated with AP 1710.

[0171] In additional or alternative embodiments, when STA 1711 indicates to AP 1710 via QoS empty frame 1770 that there is no additional data to be transmitted from STA 1711 to STA 1712, STA 1711 may use indication 1771 to request permission to utilize TXS power-saving operation. In this case, at least based on the example factors described above, AP 1710 may determine whether to allow STA 1711 to use TXS power-saving operation in response to indication 1771 (TXS PS request) included with QoS empty frame 1770.

[0172] Regarding the transmission of determining information corresponding to instruction 1717 to STA 1711, one or more embodiments may utilize the above-described method. Figure 15The described method, for example, may utilize frames transmitted from AP 1710 to STA 1511, including one or more of trigger frames, immediate response frames (e.g., Ack frames or BlockAck (BA) frames), control frames, management frames, action frames, QoS data frames, and / or QoS empty frames. The above... Figure 15 And below Figure 20 An example of using an immediate response frame (e.g., acknowledgment frame 1735) is described. An immediate response frame (e.g., acknowledgment frame 1735) may include an indication 1717. In one embodiment, indication 1717 may be included in a frame separate from acknowledgment frame 1735. In additional or alternative embodiments, indication 1771 may be included in a frame separate from QoS empty frame 1770.

[0173] Figure 18 Example 1800 shows one or more embodiments that can utilize power-saving operations during the TXS process. (e.g.) Figure 18 As shown, Example 1800 includes AP 1810 and STAs 1811 and 1812 associated with AP 1810.

[0174] In one or more embodiments, the STA (or AP) may negotiate with the AP (or STA) to support the different TXS power-saving operations described in the embodiments herein. For example, the STA 1811 may or may not have the ability to utilize TXS power-saving operations.

[0175] To illustrate this exchange of capability information between AP 1810 and STA 1811, Example 1800 begins with STA 1811 sending an association (or reassociation) request frame 1825 to AP 1810. Based on the association request frame 1825, AP 1810 can respond with an association response frame 1827. In one or more embodiments, existing capability fields in the association request frame 1825 and the association response frame 1827 can be used to exchange capability information associated with TXS power-saving operation. For example, the capability fields utilized can be included in one or more capability elements (e.g., HE capability element, EHT MAC capability element, UHR MAC capability element, etc.) in one or more management frames (e.g., beacon frame, probe request frame, probe response frame, association request frame, association response frame, etc.).

[0176] Alternative frames that can be used to provide the capabilities of STA 1811 include, but are not limited to, probe request frames, association request frames, control frames, management frames, action frames, QoS data frames, and / or QoS empty frames.

[0177] Alternative frames that can be used to provide the capabilities of AP 1810 include, but are not limited to, probe response frames, association response frames, broadcast addressing frames, control frames, management frames, action frames, QoS data frames, and / or QoS empty frames. In one or more embodiments, a broadcast addressing frame may be a beacon frame, a probe response frame, and / or a Fast Initial Link Establishment (FILS) discovery frame.

[0178] Continuing with Example 1800, AP 1810 sends MRTT frame 1815 to specify the allocation duration 1865 for the acquired TXOP 1855 to be allocated to STA 1811. In this example, MRTT frame 1815 specifies a TXOP sharing mode of 2 (e.g., for communication between STAs 1811 and 1812), and a value corresponding to the allocation duration 1865.

[0179] Upon receiving MRTT frame 1815, STA 1811 may send CTS frame 1840 to AP 1810. Based on the allocated duration 1865, STA 1811 may subsequently send a non-TB PPDU 1860 to STA 1812, and STA 1812 may respond by sending a BA frame 1820 to STA 1811. In one or more embodiments, to indicate to AP 1810 that no additional data needs to be transmitted from STA 1811 to STA 1812, STA 1811 may send a QoS empty frame 1870 to AP 1810. In response to the QoS empty frame 1870, AP 1810 may respond with an acknowledgment frame 1835.

[0180] Continuing with this example embodiment, after transmitting a QoS empty frame 1870 to AP 1810 and STA 1811 receiving an acknowledgment frame 1835 from AP 1810, if it is determined that STA 1811 has the capability to support TXS power-saving operation, STA 1811 may enter a dozing state for the remaining duration, and AP 1810 should not send any frames to STA 1811 for the remaining duration. Conversely, if STA 1811 is not determined to have sufficient capability to support TXS power-saving operation, STA 1811 may not enter dozing state 1830-1 or dozing state 1830-2 (hereinafter collectively referred to as "dozing state 1830"), and AP 1810 may send frames to STA 1811 for the remaining duration.

[0181] Figure 19 Example 1900 illustrates one or more embodiments that can utilize power-saving operations during the TXS process. (e.g.) Figure 19 As shown, Example 1900 includes AP 1910, and STA 1911 and 1912 can be associated with AP 1910.

[0182] Example 1900 may begin with STA 1911 sending an association request 1925 to AP 1910. Based on association request 1925, AP 1910 may respond with association response 1925. In one or more embodiments, to facilitate STA 1911's use of TXS power-saving operation, after STA 1911 receives association response 1927, STA 1911 may send an enable frame 1980 to AP 1910, which may include an indication to STA 1911 whether to enable (activate) or disable (deactivate) TXS power-saving operation for the current communication session. For the TXS power-saving operation described herein, STA 1911 may enter a dozing state 1930-1 or dozing state 1930-2 (hereinafter collectively referred to as "dozing state 1930") for the remaining TXS allocation duration 1965 (TXOP 1955) based on STA 1911 sending enable frame 1980. Without enabling TXS power-saving operation by enabling frame 1980, the STA 1911 can remain in a dozing state for the remainder of its duration.

[0183] In the TXS power-saving operation described in this embodiment, AP 1910 may send frames to STA 1911 for the remaining time only when AP 1910 receives an indication via enable frame 1980 that the TXS power-saving operation is disabled. Otherwise, when enable frame 1980 indicates that the TXS power-saving operation will be enabled, AP 1910 may not send any frames to STA 1911 for the remaining time.

[0184] In an additional example, when AP 1910 receives enable frame 1980, AP 1910 may send a response frame (e.g., a response management ( / action) frame or an immediate response frame (e.g., Ack or BA)). Figure 19 The confirmation frame depicted in the document is 1935-1.

[0185] Example 1900 continues, where AP 1910 sends MRTT frame 1915 to specify the allocation duration 1965 for the acquired TXOP 1955 to be allocated to STA 1911. In this example, MRTT frame 1915 specifies a TXOP sharing mode of 2 (e.g., for communication between STAs 1911 and 1912) and a value corresponding to the allocation duration 1965.

[0186] Upon receiving MRTT frame 1915, STA 1911 may send CTS frame 1940 to AP 1910. Based on the allocated duration 1965, STA 1911 may subsequently send a non-TB PPDU 1960 to STA 1912, and STA 1912 may respond by sending a BA frame 1920 to STA 1911. In one or more embodiments, to indicate to AP 1910 that no additional data needs to be transmitted from STA 1911 to STA 1912, STA 1911 may send a QoS empty frame 1970 to AP 1910. In response to the QoS empty frame 1970, AP 1910 may respond with an acknowledgment frame 1935.

[0187] Continuing with this example embodiment, after transmitting a QoS empty frame 1970 to AP 1910 and STA 1911 receiving an acknowledgment frame 1935-2 from AP 1910, based on the enable frame 1980 indicating the activation of TXS power saving operation, STA 1911 may enter a second power state (e.g., a drowsy state 1930-1 or 1930-2) for the remaining duration (e.g., the allocated duration 1965 or TXOP 1955).

[0188] Figure 20 Example 2000 illustrates one or more embodiments that can utilize power-saving operations during the TXS process. (e.g.) Figure 20 As shown, Example 2000 includes AP 2010 and STA 2011 and 2012 associated with AP 2010.

[0189] Example 2000 may begin with AP 2010 sending MRTT frame 2015 to specify the allocation duration 2065 for the acquired TXOP 2055 to be allocated to STA 2011. In this example, MRTT frame 2015 specifies a TXOP sharing mode of 2 (e.g., for communication between STA 2011 and 2012), a value corresponding to the allocation duration 2065, and potentially, as described below, MRTT frame 2015 may include information corresponding to indication 2017 (allowing the use of TXS power-saving operation).

[0190] Upon receiving MRTT frame 2015, STA 2011 may send CTS frame 2040 to AP 2010. Based on the allocated duration 2065, STA 2011 may subsequently send non-TB PPDUs 2060-1 and 2060-2 to STA 2012, wherein STA 2012 responds to non-TB PPDUs 2060-1 and 2060-2 by sending one or more BA frames 2020-1 and 2020-2 to STA 2011. In one or more embodiments, to indicate to AP 2010 that no additional data needs to be transmitted from STA 2011 to STA 2012, STA 2011 may send a QoS empty frame 2070 to AP 2010.

[0191] As described above Figure 20 As discussed, in one or more embodiments, AP 2010 may analyze various factors associated with whether STA 2011 should be allowed to enter nap state 2030-1 or nap state 2030-2 (collectively, "nap state 2030"). Examples of factors that can be evaluated to support allowing STA 2011 to enter nap state 2030 include, but are not limited to: AP 2010 not having buffered traffic for STA 2011; AP 2010 having non-low-latency buffered traffic for STA 2011; and AP 2010 having low-latency buffered traffic for another STA associated with AP 2010; and / or AP 2010 having buffered traffic for STA 2011, but AP 2010 having traffic that is more urgent than the buffered traffic for the other STA associated with AP 2010.

[0192] In additional or alternative embodiments, when STA 2011 uses QoS empty frame 2070 to indicate to AP 2010 that there is no additional data to be transmitted from STA 2011 to STA 2012, STA 2011 can use indication 2071 to request permission to use TXS power-saving operation. In this case, at least based on the example factors described above, AP 2010 can determine whether to allow STA 2011 to use TXS power-saving operation in response to indication 2071 (TXS PS request) included with QoS empty frame 2070.

[0193] Regarding the transmission of the determination information corresponding to instruction 2017 to STA 2011, one or more embodiments can utilize the above-described method. Figure 15The described method, for example, is that one method of transmitting the determined frame may utilize frames transmitted from AP 2010 to STA 1511, including one or more of trigger frames, immediate response frames (e.g., Ack frames or BlockAck (BA) frames), control frames, management frames, action frames, QoS data frames, and / or QoS empty frames. The above... Figure 15 And below Figure 21 An example of using an immediate response frame (e.g., acknowledgment frame 2035) is described. In one embodiment, indication 2017 may be included in a frame separate from acknowledgment frame 2035. In additional or alternative embodiments, indication 2017 may be included in a frame separate from QoS empty frame 2070.

[0194] In one embodiment, after STA 2011 receives an instruction to allow TXS power-saving operation, STA 2011 may send an acknowledgment instruction to AP 2010. For example, as depicted, after receiving instruction 2017 with acknowledgment frame 2035, STA 2011 sends acknowledgment instruction 2075 to AP 2010 to acknowledge receipt of the instruction. In one example, the acknowledgment instruction may be a QoS data frame, a QoS empty frame, or other frames conveying similar information.

[0195] Figure 21 Examples 2100 for different signaling capabilities for one or more embodiments are described. In one or more embodiments, the TXS power saving mode 2 support subfield 2115 in UHR MAC capability element 2110 can be used using the methods described below. In an example where STA supports TXS power saving mode 2, STA can enter a dozing state during the TXS allocated duration or the remaining duration within the current TXOP when one or more of the following conditions are met: when STA sends a first frame to return the remaining duration within the allocated duration, when STA receives a response frame in response to the first frame, when STA activates ( / enables) TXS power saving operation, when STA sends a second frame indicating that STA will enter a second power state (dozing state) during the remaining duration, when STA receives a third frame indicating that STA is allowed to be in a dozing state (second power state), and when STA receives the third frame in response to the second frame. For example, for a non-AP STA, UHR MAC capability element 2110 can be carried in an association request frame or probe request frame, and the TXS power saving mode 2 support subfield is set to one (1) indicating that the non-AP STA supports TXS power saving mode 2.

[0196] For the AP, the UHR MAC capability element 2110 may be carried in a beacon frame, associated response frame, or probe response frame. The TXS power saving mode 2 support subfield 2115 is set to one (1) indicating that the AP supports TXS power saving mode 2. In this case, the AP shall not send any frame to a STA that is allowed to enter a dozing state for the duration of the TXS allocation or the remaining duration within the current TXOP when one or more of the following conditions are met: when the AP receives a first frame to return the remaining duration within the allocated duration, when the AP sends a response frame in response to the first frame, when the AP receives a frame from the STA to activate / enable TXS power saving operation, when the AP receives a second frame from the STA indicating that the STA will enter a second power state (dozing state) for the remaining duration, when the AP sends a third frame indicating that the STA is allowed to be in a dozing state (second power state), and when the AP sends a third frame in response to the second frame.

[0197] In one or more embodiments, different methods can be used to execute the signaling values ​​corresponding to enabling and disabling TXS power saving operation. One option is to use an A-control field (e.g., EHT OM control subfield 2120). Another option is to use an action frame 2130 (e.g., an EML Operation Mode Notification (OMN) frame). In one embodiment, action frame 2130 may include an EHT TPS control element, and the EHT TPS control element may include a TXS power saving mode 2 enable subfield 2125.

[0198] In one or more embodiments, a signaling value corresponding to TXS power-saving entry can be executed by utilizing the TXS power-saving entry subfield. For example, the STA can indicate whether it transitions to ( / enters) a second power state (e.g., a dozing state) or an unavailable state during the remaining duration (TXS allocation duration or TXOP). The TXS power-saving entry subfield can be included in a QoS empty / data frame (e.g., a CAS control field or a new A-control field) or a control, management, action frame or SIG field (e.g., U-SIG, UHR-SIG, etc.) carrying the preamble of the PPDU carrying this field. In some implementations, when the TXS power-saving entry subfield can be set to one (1), this can indicate that the STA transitions to ( / enters) a second power state (e.g., a dozing state) during the remaining duration in power-saving mode. Alternatively or additionally, the TXS power-saving entry subfield can be set to one (1) when the STA will be unavailable during the remaining duration (allocation or TXOP) in active mode. In one embodiment, the TXS power-saving enter subfield may be set to one (1) when one or more of the following conditions are met: if the STA sends a first frame that includes the TXS power-saving enter subfield set to one (1), or if the STA receives a second frame (e.g., an immediate response frame (Ack or BA), a response management frame, a control frame, a management frame, or an action frame), as used herein.

[0199] In some implementations, if the STA receives a second frame (e.g., an immediate response frame (Ack or BA) or a response management frame) in response to a first frame including the TXS power saving enter subfield, the second frame indicates that the STA is permitted to be in a second power state for the remaining duration (e.g., a dozing state in TXS power saving mode (e.g., TXS power saving mode 2)), or that the STA is permitted to be unavailable in active mode for the remaining duration. It should be noted that for one or more methods of utilizing the TXS power saving operation described herein, the STA and / or AP support TXS power saving mode 2 and / or STA activation / enablement of TXS power saving mode 2.

[0200] In one or more embodiments, the AP may use the TXS power-saving enable subfield to indicate whether a non-AP STA is permitted to enter a second power state (e.g., a dozing state) in a power-saving mode (e.g., TXS power-saving mode 2) for the remaining duration or whether a non-AP STA is permitted to be unavailable in active mode for the remaining duration (allocation or TXOP). The TXS power-saving enable subfield may be included in an immediate response frame (e.g., an Ack frame or a BlockAck (BA) frame), a control frame, a management frame, an action frame, or a QoS empty / data frame, or in the SIG field of the preamble of the PPDU carrying this field (e.g., U-SIG, UHR-SIG, etc.). If the STA receives a frame carrying a TXS power-saving enable subfield set to a (1), the non-AP STA may transition to (or enter) a second power state (e.g., a dozing state) in a power-saving mode (e.g., TXS power-saving mode 2) during the remaining duration, or the non-AP STA may be unavailable in active mode during the remaining duration (e.g., allocation duration or TXOP) if one or more of the following conditions are met: the STA sends a first frame including a TXS power-saving enter subfield set to a (1) (e.g., before the STA receives the TXS power-saving enable subfield); the STA receives a second frame (e.g., an immediate response frame (Ack or BA) or a management frame, or a control frame, a QoS empty / data frame, or an action frame); the STA receives the second frame (e.g., an immediate response frame (Ack or BA) or a response management frame) in response to the first frame including the TXS power-saving enter subfield; and the second frame indicates that the STA is allowed to be in a second power state (e.g., a dozing state) in a power-saving mode (e.g., TXS power-saving mode 2) during the remaining duration, or the STA is allowed to be unavailable in active mode during the remaining duration. The TXS power saving allow subfield can be set to one (1) when one or more of the following conditions are met: when the AP does not have a buffered service to be sent to the STA, when the AP has a non-low latency service for the STA, and when the AP has a non-low latency buffered service for the STA, but the AP has a low latency service for another STA.

[0201] In one or more embodiments, the AP may use a buffered service indicator subfield to indicate whether the AP has a buffered service (or low-latency service) to send to the STA. In some implementations, the buffered service indicator subfield may be included in an immediate response frame (e.g., an Ack frame or a BlockAck (BA) frame), a control frame, a management frame, an action frame, a QoS empty / data frame, and the SIG field (e.g., U-SIG, UHR-SIG, etc.) of the preamble of the PPDU carrying this field. In some implementations, the buffered service indicator subfield is set to one (1) to indicate that the AP has a buffered service (or low-latency buffered service) to send to the STA. Otherwise, the buffered service indicator subfield is set to zero (0).

[0202] In some implementations, when a STA receives a frame carrying a subfield set to a (1), a non-AP STA may transition to (or enter) a second power state (e.g., a dozing state) or an unavailable state during the remaining duration (e.g., allocation duration or TXOP) if one or more of the following conditions are met: the STA sends a first frame including a TXS power saving entry subfield set to a (1) (e.g., before the STA receives a buffered traffic indication subfield); the STA receives a second frame (e.g., an immediate response frame (Ack or BA) or a management frame, or a control frame, a QoS empty / data frame, or an action frame); the STA receives a second frame (e.g., an immediate response frame (Ack or BA) or a response management frame) in response to the first frame including the TXS power saving entry subfield; the second frame indicates that the STA is allowed to be in a second power state (e.g., a dozing state) in a power saving mode (e.g., TXS power saving mode 2) for the remaining duration, or the STA is allowed to be unavailable in active mode for the remaining duration; or the STA and / or AP support TXS power saving mode 2 and the STA activates / enables TXS power saving mode 2.

[0203] Figure 22 An example process 2200 according to an embodiment is shown. Example process 2200 can be executed by an AP (such as AP1410, AP1510, AP1610, AP1710, AP1810, 1920, or AP2010 described above). Figure 22 As shown, process 2200 may include steps 2202 and 2204.

[0204] Step 2202 includes: sending a first frame from the access point (AP) to the station (STA), the first frame indicating a time period in a transmission opportunity (TXOP) allocated to the STA. The STA may be associated with the AP. The first frame may include a trigger frame. The trigger frame may include an MRTT frame.

[0205] Step 2204 includes: the AP receiving a second frame from the STA during the time period, the second frame instructing the STA to return the time period to the AP. In one embodiment, the second frame includes a QoS data frame, a QoS empty frame, an action frame, a control frame, or a management frame.

[0206] In one embodiment, process 2200 may further include: receiving a third frame from the STA by the AP during a first time period, the third frame including a first indication of transition from a first power state to a second power state. In one embodiment, the second frame includes the first indication. In one embodiment, the second or third frame is a control frame, management frame, action frame, QoS data frame, or QoS empty frame. In one embodiment, process 2200 may further include: sending a fourth frame to the STA by the AP during the first time period, the fourth frame including a second indication of whether the STA is permitted to be in the second power state. In one embodiment, the AP sends the fourth frame to the STA in response to the second frame.

[0207] In one embodiment, the AP sends a fourth frame to the STA in response to a second frame including a first indication. In one embodiment, the AP sends a fourth frame to the STA in response to a third frame. In one embodiment, the fourth frame is a trigger frame, an immediate response frame, a control frame, a management frame, an action frame, a QoS data frame, or a QoS empty frame. In one embodiment, the trigger frame includes a MU-RTSTXS trigger frame or a MU-RTS trigger frame. In one embodiment, the immediate response frame includes an acknowledgment (Ack) frame or a BlockAck (BA) frame. In one embodiment, the Ack frame or BA frame includes a More Data (MD) subfield set to 0 to indicate that the STA is permitted to be in the second power state. In one embodiment, the Ack frame or BA frame includes a More Data (MD) subfield set to 1 to indicate that the STA is not permitted to be in the second power state. In one embodiment, a second indication that the STA is permitted to be in the second power state includes that the AP does not have buffered traffic for the STA.

[0208] In one embodiment, the second indication regarding a STA being allowed in a second power state includes the AP having a non-low-latency buffered service for the STA and the AP having a low-latency buffered service for another STA. In one embodiment, the second indication regarding a STA being allowed in a second power state includes the AP having a buffered service for the STA, but the AP having a more urgent service for another STA. In one embodiment, process 2200 may further include: the AP sending a fourth frame to the STA during a first time period, the fourth frame including a third indication regarding whether the AP has a buffered service for the STA. In one embodiment, process 2200 may further include: the AP sending a fourth frame to the STA during the first time period, the fourth frame including a third indication regarding whether the AP has a low-latency buffered service for that STA. In one embodiment, process 2200 may further include: the AP receiving a fifth frame from the STA before the first time period, the fifth frame including a first capability of whether the STA supports TXS power-saving operation, and after receiving the fifth frame, the AP sending a sixth frame to the STA, the sixth frame including a second capability of whether the AP supports TXS power-saving operation.

[0209] In one embodiment, the fifth frame is a probe request frame, an association request frame, a control frame, a management frame, an action frame, a QoS data frame, or a QoS empty frame. In one embodiment, the sixth frame is a probe response frame, an association response frame, a control frame, a management frame, an action frame, a QoS data frame, or a QoS empty frame. In one embodiment, the broadcast addressing frame further includes a second capability. In one embodiment, the broadcast addressing frame is a beacon frame, a probe response frame, or a Fast Initial Link Establishment (FILS) discovery frame.

[0210] Figure 23 Another example process 2300 according to an embodiment is shown. Example process 2300 can be performed by a first STA (such as STA 1411, STA 1511, STA 1611, STA 1711, STA 1811, 1911, or 2011 described above). Figure 23 As shown, process 2300 may include steps 2302, 2304 and 2306.

[0211] Step 2302 includes: receiving a first frame from an access point (AP) by a station (STA) indicating a time period allocated to the STA in a transmission opportunity (TXOP). The first STA may be associated with the AP. The first frame may include a trigger frame. The trigger frame may include an MRTT frame. Step 2304 includes: sending a second frame to the AP during the time period by the STA, the second frame instructing the STA to return the time period to the AP. In one embodiment, the second frame includes a QoS data frame, a QoS empty frame, an action frame, a control frame, or a management frame. Step 2306 includes: after sending the second frame, transitioning the STA from a first power state (wake-up) to a second power state (sleep).

[0212] In one embodiment, the second frame includes a first indication. In one embodiment, the second or third frame is a control frame, management frame, action frame, QoS data frame, or QoS empty frame. In one embodiment, process 2300 may further include: the STA receiving a fourth frame from the AP during a first time period, the fourth frame including a second indication regarding whether the STA is permitted to be in a second power state; and based on the second indication regarding whether the STA is permitted to be in a second power state, the STA transitioning from a first power state to a second power state.

[0213] In one embodiment, the STA receives a fourth frame from the AP in response to a second frame. In one embodiment, the STA receives a fourth frame from the AP in response to a second frame including a first indication. In one embodiment, the STA receives a fourth frame from the AP in response to a third frame. In one embodiment, the fourth frame is a trigger frame, an immediate response frame, a control frame, a management frame, an action frame, a QoS data frame, or a QoS empty frame. In one embodiment, the trigger frame includes a MU-RTS TXS trigger frame. In one embodiment, the immediate response frame includes an acknowledgment (Ack) frame or a BlockAck (BA) frame. In one embodiment, the Ack frame or BA frame includes a More Data (MD) subfield set to 0 to indicate that the STA is permitted to be in the second power state. In one embodiment, the Ack frame or BA frame includes a More Data (MD) subfield set to 1 to indicate that the STA is not permitted to be in the second power state. In one embodiment, a second indication that the STA is permitted to be in the second power state includes that the AP does not have buffered traffic for the STA.

[0214] In one embodiment, the second indication that a STA is allowed to be in the second power state includes that the AP has a non-low-latency buffered service for the STA and that the AP has a low-latency buffered service for another STA. In another embodiment, the second indication that a STA is allowed to be in the second power state includes that the AP has a buffered service for the STA, but the AP has a more urgent service for another STA. In one embodiment, process 2300 may further include: the STA receiving a fourth frame from the AP during a first time period, the fourth frame including a third indication of whether the AP has a buffered service for the STA, and based on the third indication that the AP does not have a buffered service for the STA, the STA transitioning from the first power state to the second power state.

[0215] In one embodiment, process 2300 may further include: the STA receiving a fourth frame from the AP during a first time period, the fourth frame including a third indication of whether the AP has a low-latency buffered service for the STA, and based on the third indication that the AP does not have a low-latency buffered service for the STA, the STA transitioning from a first power state to a second power state. In one embodiment, process 2300 may further include: the STA sending a fifth frame to the AP before the first time period, the fifth frame including a first capability of whether the STA supports TXS power-saving operation; after sending the fifth frame, the STA receiving a sixth frame from the AP, the sixth frame including a second capability of whether the AP supports TXS power-saving operation; and based on the first and second capabilities supporting TXS power-saving operation, the STA transitioning from the first power state to the second power state.

[0216] In one embodiment, the fifth frame is a probe request frame, an association request frame, a control frame, a management frame, an action frame, a QoS data frame, or a QoS empty frame. In one embodiment, the sixth frame is a probe response frame, an association response frame, a control frame, a management frame, an action frame, a QoS data frame, or a QoS empty frame. In one embodiment, the broadcast addressing frame further includes a second capability. In one embodiment, the broadcast addressing frame is a beacon frame, a probe response frame, or a Fast Initial Link Establishment (FILS) discovery frame.

[0217] In one implementation, the second power state may be referred to as a lower power receive state or a listen / monitor state. While in the second power state, the STA is able to receive first-class PPDUs. In another implementation, the STA is able to receive only first-class PPDUs during the second power state.

[0218] In one implementation, the first category may include PPDUs with a non-HT PPDU format. In another implementation, the first category may additionally or alternatively include PPDUs with a data rate of less than or equal to 24 Mbps, a bandwidth of 20 MHz, and / or a single spatial stream.

[0219] Figure 24 Example 2400 is shown, illustrating one or more embodiments that can utilize power-saving operations during the TXS process. (e.g.) Figure 24 As shown, Example 2400 includes AP 2410 and STAs 2411 and 2412 associated with AP 2410.

[0220] Example 2400 may begin with AP 2410 sending MRTT frame 2415 to specify an allocation duration 2465 for the acquired TXOP 2455 to be allocated to STA 2411. In this example, MRTT frame 2415 specifies a TXOP sharing mode of 2 (e.g., for communication between STAs 2411 and 2412), a value corresponding to the allocation duration 2465, and potentially, as described below, MRTT frame 2415 may include information corresponding to indication 2417 (allowing the use of TXS PS). Indication 2417 may indicate whether TXS PS is allowed to be used by STA 2411. Indication 2417 may indicate whether the AP has buffered traffic for STA 2411. Indication 2417 may indicate whether the AP has low-latency / latency-sensitive / urgent buffered traffic for STA 2411. Instruction 2417 may indicate whether the AP will schedule DL transmissions for STA 2411 faster than other STAs during TXOP 2455 or the allocation duration 2465. For example, instruction 2417 may indicate that when the AP has low-latency / latency-sensitive / urgent buffered traffic for STA 2411, the AP will schedule DL transmissions for STA 2411 faster than other STAs during TXOP 2455 or the allocation duration 2465. In this case, the AP will send the DL PPDU for STA 2411 faster than other STAs during TXOP 2455 or the allocation duration 2465, and STA 2411 will be awakened after sending the QoS empty frame 2470 and subsequently receive an immediate response frame (e.g., acknowledgment frame 2435) in response to the QoS empty frame 2470. For example, Instruction 2417 could indicate that when the AP does not have a buffered low-latency / latency-sensitive / urgent service for STA 2411, the AP will not send DL transmissions for STA 2411 faster than other STAs during TXOP 2455 or the allocation duration 2465. If Instruction 2417 indicates that DL transmissions for STA 2411 will not be scheduled faster than other STAs during TXOP 2455 or the allocation duration 2465, then the AP can send DL PPDUs for other STAs faster than STA 2411 during TXOP 2455 or the allocation duration 2465, and STA 2411 will transition to a second power state (listening state) after sending a QoS empty frame 2470 and then receiving an immediate response frame (e.g., acknowledgment frame 2435) in response to the QoS empty frame 2470.

[0221] Upon receiving MRTT frame 2415, STA 2411 may send CTS frame 2440 to AP 2410. Depending on the allocated duration 2465, STA 2411 may subsequently send non-TB PPDUs 2460-1 and 2460-2 to STA 2412, wherein STA 2412 responds to non-TB PPDUs 2460-1 and 2460-2 by sending one or more BA frames 2420-1 and 2420-2 to STA 2411. In one or more embodiments, to indicate to AP 2410 that no additional data needs to be transmitted from STA 2411 to STA 2412, STA 2411 may send a QoS empty frame 2470 to AP 2410.

[0222] As described above Figure 24 As discussed, in one or more embodiments, AP 2410 may analyze various factors associated with whether STA 2411 should be allowed to enter listening state 2430. Examples of factors that can be evaluated to support allowing STA 2411 to enter listening state 2430 include, but are not limited to: AP 2410 not having buffered traffic for STA 2411; AP 2410 having non-low-latency buffered traffic for STA 2411; and AP 2410 having low-latency buffered traffic for another STA associated with AP 2410; and / or AP 2410 having buffered traffic for STA 2411, but AP 2410 having traffic that is more urgent than the buffered traffic for the other STA associated with AP 2410.

[0223] In additional or alternative embodiments, when STA 2411 uses QoS empty frame 2470 to indicate to AP 2410 that there is no additional data to be transmitted from STA 2411 to STA 2412, STA 2411 can use indication 2471 to request permission to use TXS power-saving operation. In this case, at least based on the example factors described above, AP 2410 can determine whether to allow STA 2411 to use TXS power-saving operation in response to indication 2471 (TXS PS request) included with QoS empty frame 2470.

[0224] Regarding the transmission of the determination information corresponding to instruction 2417 to STA 2411, one or more embodiments can utilize the above-described method. Figure 15 The described method, for example, is that one method of transmitting the determined frame may utilize frames transmitted from AP 2410 to STA 1511, including trigger frames, immediate response frames (e.g., Ack frames or BlockAck (BA) frames), control frames, management frames, action frames, QoS data frames, and / or QoS empty frames, or more of these. Figure 15 and 20An example using an immediate response frame (e.g., acknowledgment frame 2435) is described. An immediate response frame (e.g., acknowledgment frame 2435) may include an indication 2417. In one embodiment, the indication 2417 may be included in a frame separate from the acknowledgment frame 2435. In additional or alternative embodiments, the indication 2417 may be included in a frame separate from the QoS empty frame 2470. In one embodiment, the AP 2410 and STA 2411 operations for the indication 2417 will be the same as described above.

[0225] In one example, when STA 2411 is in listening state 2430, AP 2410 can send DLPPDU 2436 to STA 2412, and STA 2412 can respond to DLPPDU 2436 by sending BA 2420-3 to AP 2410. In one example, AP 2410 can send an Initial Control Frame (ICF) 2437 to STA 2411. The Initial Control Frame may include an RTS frame, MU-RTS frame, BSRP frame, BAR frame, or a new control frame. After receiving ICF 2437, STA 2411 can transition from the second power state (listening state) to the first power state (wake-up state). In response to ICF 2437, STA 2411 can send an Initial Control Response Frame (ICR) 2480 to AP 2410. After receiving ICR 2480, AP 2410 can send DLPPDU 2436 to STA 2411. In response to DL PPDU 2436, STA 2411 can send BA 2485.

Claims

1. A method comprising: The station (STA) receives the first frame from the access point (AP), which indicates: The first time period allocated to the STA in a transmission opportunity (TXOP); as well as The sharing mode for the first time period; The STA sends a second frame to the AP during the first time period, and the second frame instructs the STA to return the first time period to the AP. as well as After the second frame is transmitted, the STA switches from the first power state to the second power state based on the sharing mode.

2. A method comprising: The station (STA) receives a first frame from the access point (AP), the first frame indicating a first time period in a transmission opportunity (TXOP) allocated to the STA; The STA sends a second frame to the AP during the first time period, and the second frame instructs the STA to return the first time period to the AP. as well as After the second frame is transmitted, the STA switches from the first power state to the second power state.

3. The method according to claim 2, wherein, The first frame also indicates the sharing mode for the first time period.

4. The method according to claim 3, wherein, The transition from the first power state to the second power state by the STA is based on the shared mode.

5. The method according to any one of claims 2-4, further comprising: During the first time period, the STA sends a third frame to the AP, the third frame including a first indication of transition from the first power state to the second power state; as well as After the third frame is transmitted, the STA transitions from the first power state to the second power state.

6. The method according to claim 5, wherein, The second frame includes the first indication.

7. The method according to any one of claims 5-6, wherein, The second or third frame is a control frame, management frame, action frame, quality of service (QoS) data frame, or QoS empty frame.

8. The method according to any one of claims 5-7, further comprising: During the first time period, the STA receives a fourth frame from the AP, the fourth frame including a second indication of whether the STA is allowed to be in the second power state; as well as Based on the second indication that the STA is allowed to be in the second power state, the STA switches from the first power state to the second power state.

9. The method according to claim 8, wherein, The STA responds to the second frame by receiving the fourth frame from the AP.

10. The method according to any one of claims 8-9, wherein, The STA receives the fourth frame from the AP in response to the second frame including the first indication.

11. The method according to claim 8, wherein, The STA receives the fourth frame from the AP in response to the third frame.

12. The method according to any one of claims 8-11, wherein, The fourth frame is a trigger frame, an immediate response frame, a control frame, a management frame, an action frame, a QoS data frame, or a QoS empty frame.

13. The method according to claim 12, wherein, The trigger frame includes a Multiple User Request Transmission (MU-RTS) Transport Opportunity Sharing (TXS) Trigger (MRTT) frame.

14. The method according to claim 12, wherein, The immediate response frame includes an acknowledgment (Ack) frame or a block acknowledgment (BA) frame.

15. The method according to claim 14, wherein, The Ack frame or the BA frame includes a More Data (MD) subfield set to 0 to indicate that the STA is allowed to be in the second power state.

16. The method of claim 14, wherein, The Ack frame or the BA frame includes an MD subfield set to 1 to indicate that the STA is not allowed to be in the second power state.

17. The method according to any one of claims 8-16, wherein, The second indication that the STA is allowed to be in the second power state includes: the AP does not have buffered services for the STA.

18. The method according to any one of claims 8-16, wherein, The second indication that the STA is allowed to be in the second power state includes: the AP has a non-low latency buffered service for the STA, and the AP has a low latency buffered service for another STA.

19. The method according to any one of claims 8-16, wherein, The second indication regarding the STA being allowed to be in the second power state includes: the AP has buffered services for the STA, but the AP has more urgent services for other STAs.

20. The method according to any one of claims 8-19, further comprising: The STA receives the fourth frame from the AP during the first time period, the fourth frame including a third indication of whether the AP has buffered services for the STA; as well as Based on the third indication that the AP does not have buffered services for the STA, the STA transitions from the first power state to the second power state.

21. The method of claim 20, further comprising: The STA receives the fourth frame from the AP during the first time period, the fourth frame including a third indication of whether the AP has a low-latency buffer service for the STA; as well as Based on the third indication that the AP does not have the low-latency buffer service for the STA, the STA transitions from the first power state to the second power state.

22. The method according to any one of claims 2-21, further comprising: The STA sends a fifth frame to the AP before the first time period, the fifth frame including a first capability regarding whether the STA supports TXS power saving (PS) operation; After the fifth frame is sent, the STA receives a sixth frame from the AP, the sixth frame including a second capability regarding whether the AP supports TXS PS operation; as well as Based on the first capability and the second capability, the TXS PS operation is supported, and the STA transitions from the first power state to the second power state.

23. The method according to claim 22, wherein, The fifth frame is a probe request frame, association request frame, control frame, management frame, action frame, QoS data frame, or QoS empty frame.

24. The method according to any one of claims 22-23, wherein, The sixth frame is a probe response frame, an associated response frame, a control frame, a management frame, an action frame, a QoS data frame, or a QoS empty frame.

25. The method according to any one of claims 22-24, wherein, Broadcast addressing frames also include the second capability.

26. The method of claim 25, wherein, The broadcast addressing frame is a beacon frame, a probe response frame, or a Fast Initial Link Establishment (FILS) discovery frame.

27. The method according to any one of claims 2-26, further comprising: The STA sends a seventh frame to the AP before the first time period, the seventh frame including an indication of activation or deactivation of TXS PS mode; The STA receives the eighth frame from the AP in response to the seventh frame; as well as Based on the indication of activation of the TXS PS mode, the STA transitions from the first power state to the second power state.

28. The method according to claim 27, wherein, The eighth frame includes an indication of whether the activation of the TXS PS mode is accepted or rejected.

29. The method according to any one of claims 27-28, wherein, The seventh frame is a control frame, management frame, action frame, QoS data frame, or QoS empty frame.

30. The method according to any one of claims 27-29, wherein, The eighth frame is an immediate response frame, control frame, management frame, action frame, QoS data frame, or QoS empty frame.

31. The method according to any one of claims 2-30, wherein, The first power state corresponds to the wake-up state or active mode of the STA in power-saving mode.

32. The method according to any one of claims 2-31, wherein, The second power state corresponds to the STA's dozing state in power-saving mode.

33. The method according to claims 2-32, wherein, The second power state corresponds to the STA being unavailable when it is in wake-up mode.

34. The method according to any one of claims 2-33, wherein, The second frame includes a High Efficiency (HE) variant High Throughput (HT) control field with a Command and Status (CAS) control subfield, the Command and Status (CAS) control subfield having a Reverse Authorization (RDG) / More Physical Layer (PHY) Protocol Data Unit (PPDU) subfield equal to 0.

35. The method according to any one of claims 3-34, wherein, The sharing mode is set to TXS mode 2.

36. The method according to any one of claims 2-35, wherein, After transitioning to the second power state, the STA maintains the second power state for the first remaining duration of the first time period.

37. The method according to any one of claims 2-35, wherein, After transitioning to the second power state, the STA maintains the second power state for the second remaining duration of the TXOP.

38. The method according to any one of claims 2-37, further comprising: After the first time period ends, the STA switches from the second power state to the first power state.

39. The method according to claims 2-37, further comprising: After the TXOP ends, the STA transitions from the second power state to the first power state.

40. A method comprising: The access point (AP) sends a first frame to the station (STA), the first frame indicating: The first time period allocated to the STA in a transmission opportunity (TXOP); as well as The sharing mode for the first time period; During the first time period, the AP receives a second frame from the STA, and the second frame instructs the STA to return the first time period to the AP; as well as The AP receives a third frame from the STA during the first time period, the third frame including a first indication of a transition from a first power state to a second power state.

41. A method comprising: The access point (AP) sends a first frame to the station (STA), the first frame indicating: The first time period allocated to the STA in a transmission opportunity (TXOP); as well as The sharing mode for the first time period; as well as The AP receives a second frame from the STA during the first time period, and the second frame instructs the STA to return the first time period to the AP.

42. The method of claim 41, further comprising: The AP receives a third frame from the STA during the first time period, the third frame including a first indication of a transition from a first power state to a second power state.

43. The method of claim 42, further comprising: The AP sends a fourth frame to the STA during the first time period, the fourth frame including a second indication of whether the STA is allowed to be in the second power state.

44. The method according to claim 43, wherein, The AP responds to the third frame by sending the fourth frame to the STA.

45. The method according to any one of claims 41-44, further comprising: The AP receives a fifth frame from the STA before the first time period, the fifth frame including a first capability regarding whether the STA supports TXS PS operation; as well as After receiving the fifth frame, the AP sends a sixth frame to the STA, the sixth frame including a second capability regarding whether the AP supports the TXS PS operation.

46. ​​The method according to any one of claims 41-45, further comprising: The AP receives a seventh frame from the STA before the first time period, the seventh frame including an indication of activation or deactivation of the TXS PS mode; as well as The AP sends an eighth frame to the STA in response to the seventh frame.

47. An apparatus comprising: One or more processors; as well as A memory for storing instructions that, when executed by the one or more processors, cause the device to perform the method according to any one of claims 1-46.

48. A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform the method according to any one of claims 1-46.

Images