Indicating station unavailability after transmission opportunity sharing

Abstract

The station (STA) sends a first frame to the access point (AP) indicating a power state transition. The STA then sends a second frame to the AP, which shares the transmission opportunity (TXOP) acquired by the STA with the AP. Based on the power state transition, the STA transitions from a first power state to a second power state for the remainder of the TXOP.

Description

Cross-references to related applications

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 626,131, filed January 29, 2024, the entire contents of which are incorporated herein by reference. Attached Figure Description

[0002] Examples of several embodiments of the various embodiments of this disclosure are described 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 illustrating an example implementation of a station (STA) and an access point (AP).

[0005] Figure 3 An example Multi-User Request to Send (MU-RTS) Transmission Opportunity (TXOP) Share (TXS) Trigger (MRTT) frame that can be used in the Transmission Opportunity (TXOP) Share (TXS) process is shown.

[0006] Figure 4 An example data frame that can be used as a QoS empty frame is shown.

[0007] Figure 5 An example management frame that can be used as an action frame is shown.

[0008] Figure 6 An example of the TXS process is shown.

[0009] Figure 7 Another example of the TXS process is shown.

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

[0011] Figure 9 This is an example of the TXS power saving (PS) mode that can be used to address potential waste during some wake-up states.

[0012] Figure 10 An example 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.

[0013] Figure 11 This shows an example of a STA sending an association request frame to an AP.

[0014] Figure 12 An example of existing operation is shown, where the TXOP acquired by a non-AP STA is shared with the AP.

[0015] Figure 13 Examples of one or more embodiments of energy-saving operation that can be utilized during operation in which the STA and AP share the TXOP are shown.

[0016] Figure 14 Examples of one or more embodiments are shown that can provide STA unavailability information to an AP that receives TXOP sharing from a STA.

[0017] Figure 15 Examples of one or more embodiments are shown that can provide STA unavailability information to an AP that receives TXOP sharing from a STA.

[0018] Figure 16 Examples of one or more embodiments are shown that can provide STA unavailability information to an AP that receives TXOP sharing from a STA.

[0019] Figure 17 An example process performed by the STA according to an embodiment is shown.

[0020] Figure 18 An example process performed by the AP according to an embodiment is shown. Detailed Implementation

[0021] Various embodiments are provided in this disclosure as examples of how the disclosed techniques can be implemented and / or how they can be practiced in environments and scenarios. It will be apparent to those skilled in the art that various changes in form and detail may be made without departing from the scope described. After reading this specification, those skilled in the art will understand how alternative embodiments can be implemented. The given embodiments are not limited to any of the described exemplary embodiments. Embodiments of this disclosure will be described with reference to the accompanying drawings. Limitations, features, and / or elements from the various exemplary embodiments disclosed may be combined to create additional embodiments within the scope of this disclosure. Any drawings highlighting features and advantages are provided for illustrative purposes only. The disclosed architecture is flexible and configurable enough that it can be used in ways other than those shown. For example, in some embodiments, any actions listed in the flowcharts may be reordered or used only optionally.

[0022] The embodiments can be configured to operate as needed. The disclosed mechanisms can be implemented when certain criteria are met, for example, in a station, access point, radio environment, network, or a combination thereof. Example standards can 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 of the disclosed protocols can be implemented selectively.

[0023] 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” will 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 number of suitable possibilities that may or may not be employed by one or more of the various embodiments. As used herein, the terms “comprises” and “consistsof” enumerate one or more components of the described element. The term “comprises” is interchangeable with “includes” and does not exclude the inclusion of unlisted components in the described element. In contrast, “consists 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.” As used herein, the term “and / or” refers to any possible combination of the listed elements. For example, “A, B and / or C” could mean A; B; C; A and B; A and C; B and C; or A, B and C.

[0024] 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 embodiments in 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 embodiments in various embodiments. The phrase "depending on" (or equivalently "at least depending on") indicates that the phrase following the phrase "depending on" is an example of one of a variety of suitable possibilities that may or may not be used in one or more embodiments in various embodiments. The phrase “adopt / use” (or equivalently “adopt / at least 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 embodiments in various implementations.

[0025] The term "configured" can refer to the capacity of a device, 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 to implement certain actions within the device, regardless of whether the device is in an operational or non-operational state.

[0026] In this disclosure, a parameter (or equivalently referred to as a field or information element: IEs) 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 present in at least one of the one or more messages / frames, but not necessarily in every one of the one or more messages / frames.

[0027] The numerous features provided are described as optional by using "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.

[0028] 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 a defined interface to 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 a combination thereof, and may be behaviorally equivalent. For example, a module can be implemented as a software routine written in a computer language (such as C, C++, Fortran, Java, Basic, Matlab, etc.) of the hardware machine, or a modeling / simulation program (such as Simulink, Stateflow, GNU Octave, or LabVIEW MathScript). 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, C++, etc. FPGAs, ASICs, and CPLDs are typically programmed using hardware description languages ​​(HDLs), such as VHSIC Hardware Description Language (VHDL) or Verilog, which configure connections between internal hardware modules with limited functionality on the programmable device. The techniques mentioned are often used in combination to achieve the desired functional modules.

[0029] Figure 1 Example 100 of a wireless communication network in which embodiments of the present disclosure may be implemented is shown. Figure 1 As shown, an example wireless communication network may include an IEEE 802.11 wireless local area network (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.

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

[0031] The DS 130 can be configured to connect BSS 110-1 and BSS 110-2. In this way, 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).

[0032] 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., IEEE 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.

[0033] 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 included within each other's communication range. These multiple STAs are configured such that they can communicate with each other using direct peer-to-peer communication (i.e., without via AP).

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

[0035] 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). STA may also be referred to using various other terms, 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.

[0036] Physical Layer (PHY) Protocol Data Units (PPDUs) can be composite structures comprising a PHY preamble and a payload, taking the form of PHY Service Data Units (PSDUs). 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 bonded channel (a channel formed by channel bonding), the preamble field can be copied and transmitted in each of the multiple component channels. A 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 things. 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.

[0037] 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 the 2.4 GHz, 5 GHz, and / or 6 GHz frequency 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 bonding. For example, PPDUs can be transmitted on physical channels with bandwidths of 40 MHz, 80 MHz, 160 MHz, or 320 MHz by bonding multiple 20 MHz channels together.

[0038] Figure 2 This is block diagram 200 illustrating example implementations of STA 210 and AP 260. (See diagram 200 for details.) Figure 2 As 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.

[0039] 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. The one or more processors and / or one or more controllers may include, for example, general-purpose processors, digital signal processors (DSPs), microcontrollers, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), logic circuits, or chipsets.

[0040] 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 within or outside of processor 220 / 270 (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.

[0041] Transceiver 240 / 290 can be configured to transmit / receive radio signals. In embodiments, transceiver 240 / 290 can implement the PHY layer of a corresponding device (STA 210 or AP 260). In embodiments, 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. These multiple PHY layers can be implemented using one or more of transceivers 240 / 290.

[0042] 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 allows STAs to reduce the amount of time a STA utilizing power management mode can be kept awake. TWT can be individual or broadcast. Individual 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.

[0043] In a standalone TWT, the STA that requests the TWT agreement is called the TWT requesting STA. For example, the TWT requesting STA can be a non-AP STA. The STA that responds to the request is called the TWT responding STA. For example, the TWT responding STA can be 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. Once a TWT agreement is established between the TWT requesting STA and the TWT responding STA, the TWT responding STA can send a TWT value to the TWT requesting STA.

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

[0045] The TWT value of an implicit TWT can be periodic. A TWT requester STA operating using an 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 responder STA can include the start times of a series of 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 this series of TWT SPs 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 requester STA waking up for an implicit TWT SP can enter a doze state after the TWT SP has elapsed or after receiving a Service Period End (EOSP) field equal to 1 from the TWT responder STA (whichever occurs first).

[0046] TWT sessions can be negotiated between the AP and STA. A TWT session can be configured with TWT SPs for downlink (DL) and uplink (UL) traffic between the AP and STA. Traffic is expected to be confined within the negotiated SP. A TWT SP can start at a specific time. A TWT SP can run for a duration specified in the SP. A TWT SP can repeat at each SP interval.

[0047] Figure 3An example Multi-User Request to Send (MU-RTS) Transmission Opportunity (TXOP) Sharing (TXS) Trigger (MRTT) frame 300 is shown that can be used in the Transmission Opportunity (TXOP) Sharing (TXS) process. 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.

[0048] In one example, the public information field can be either the High Efficiency (HE) variant public information field or the 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 OS, UL BW, GI and HE / EHT-LTF type / triggered TXOP sharing mode, number of HE / EHT-LTF symbols, LDPC additional symbol segment, AP Tx power, FEC pre-fill factor, PE disambiguation, UL space reuse, HE / EHT P160, special user information field flag, EHT reservation, reservation, or trigger-related public information.

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

[0050] The GI and HE / EHT-LTF type / triggered TXOP shared mode subfield may include a triggered TXOP shared mode subfield. In one example, the triggered TXOP shared mode subfield may be set to a non-zero value (e.g., 1 or 2). In one example, the triggered TXOP shared mode subfield may be set to one (1). Therefore, the triggered TXOP shared mode subfield may indicate that the STA indicated by the AID12 subfield of the (User Information List Field) User Information Field may send one or more non-TB PPDUs to the AP during the time period indicated by the Allocation Duration subfield of that User Information Field. In another example, the triggered TXOP shared mode subfield may be set to 2. Therefore, the triggered TXOP shared mode subfield may indicate that the STA indicated by the AID12 subfield of the (User Information List Field) User Information 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 that User Information Field. In one example, the peer STA may be a STA with a connection for P2P or direct communication with the STA.

[0051] The user information list fields can include one or more user information fields. In one example, such as... Figure 3As shown, the EHT variant user information field may include one or more of the following subfields: AID12, RU allocation, allocation duration, reservation, or PS160.

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

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

[0054] The allocation 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 one example, the allocation duration subfield can indicate the first time period.

[0055] Figure 4 Example data frame 400, which can be used as a QoS empty frame, is shown. A QoS empty frame is a QoS data frame with an empty frame body. A QoS empty frame includes a QoS control field and an optional HT control field, which may contain a Buffer Status Report (BSR) control subfield. QoS empty frames indicating buffer status information can be sent by the STA to the AP.

[0056] QoS control fields may include: Service Identifier (TID) subfield, Acknowledgment (Ack) Policy Indicator subfield, and Queue Size subfield (or Transmission Opportunity (TXOP) Duration Request subfield).

[0057] The TID subfield identifies the TC or TS that is requesting a TXOP for the service by setting either the TXOP duration request subfield or the queue size subfield. The encoding of the TID subfield depends on the access policy (e.g., for Enhanced Distributed Channel Access (EDCA) access policies, values ​​from 0 to 7 are allowed to identify the user priority for the TC or TS).

[0058] The Acknowledgment Policy Indicator subfield, along with other information, identifies the Ack policy followed when delivering the MPDU (e.g., normal Ack, implicit block Ack request, no Ack, block Ack, etc.). The queue size subfield is an 8-bit field that indicates the buffered traffic at the STA for a given TC or TS to be transmitted to the AP identified by the receiver address of the frame containing this subfield. The queue size subfield is present in the QoS empty frame transmitted by the STA when bit 4 of the QoS control field is set to 1. The AP can use the information contained in the queue size subfield to determine the TXOP duration allocated to the STA or to determine the uplink (UL) resources allocated to the STA.

[0059] In frames transmitted by or sent to an inefficient (non-HE) STA, the following rules may be applied to queue size values: The queue size value is the approximate total size of all MSDUs and A-MSDUs buffered at the STA (excluding MSDUs or A-MSDUs contained in the current QoS data frame) in the delivery queue for MSDUs and A-MSDUs whose TID values ​​are equal to the values ​​indicated in the TID subfield of the QoS control field. It is rounded up to the nearest multiple of 256 octets and represented in units of 256 octets.

[0060] A queue size value of 0 is used only to indicate that there are no buffered transactions in the queue for the specified TID.

[0061] The queue size value of 254 is used for all sizes greater than 64,768 octets.

[0062] The queue size value of 255 is used to indicate an unspecified or unknown size.

[0063] In frames sent from HE STA to HE AP, the following rules can be applied to queue size values.

[0064] The queue size value QS is the approximate total size, in octet, of all MSDUs and A-MSDUs buffered at the STA (including MSDUs or A-MSDUs contained in the same PSDU as the frame containing the queue size subfield) in the delivery queue of MSDUs and A-MSDUs whose TID values ​​are equal to the values ​​indicated in the TID subfield of the QoS control field.

[0065] The queue size subfield includes: the scaling factor subfield in bits B14-B15 of the QoS control field, and the unscaled value UV in bits B8-B13 of the QoS control field. The scaling factor subfield provides the scaling factor SF.

[0066] The STA obtains the queue size QS from the received QoS control field, which includes the scaling factor SF and the unscaled value UV, as shown below: QS= 16 x UV, if SF equals 0; 1024 + 256 x UV, if SF equals 1; 17408 + 2048 x UV, if SF equals 2; 148480 + 32768 x UV, if SF equals 3 and UV is less than 62; >2147328, if SF equals 3 and UV equals 62; Unspecified or unknown if SF equals 3 and UV equals 63.

[0067] The TXOP duration request subfield may be included but not the queue size subfield. The TXOP duration request subfield indicates to the sending STA the duration (in microseconds (µs) it requires for its next TXOP for a specified TID. The TXOP duration request subfield is set to 0 to indicate that no TXOP is requested for the specified TID in the current service period (SP). The TXOP duration request subfield is set to a non-zero value to indicate the requested TXOP duration in increments of 32µs, ranging from 32µs to 8160µs.

[0068] HT control fields can include aggregate control (AC control) subfields. A-control subfields can include control list subfields that contain one or more control subfields.

[0069] The control subfield can be a BSR control subfield, which can contain buffer status information for UL MU operations. The BSR control subfield can be formed by the Access Class Index (ACI) bitmap subfield, incremental TID subfield, ACI high subfield, scaling factor subfield, queue size high subfield, and queue size full subfield of the HT control field.

[0070] The ACI bitmap subfield indicates the access category for its reported buffer state (e.g., B0: Best Effort (AC_BE), B1: Background (AC_BK), B2: Video (AC_VI), B3: Voice (AC_VO), etc.). Each bit of the ACI bitmap subfield is set to 1 to indicate that the buffer state of the corresponding AC is included in the queue size full subfield, otherwise it is set to 0, with the exception that if the ACI bitmap subfield is 0 and the incremental TID subfield is 3, then the buffer states of all 8 TIDs are included.

[0071] The values ​​of the incremental TID subfield and the ACI bitmap subfield indicate the number of TIDs that the STA is reporting the buffer status for.

[0072] The ACI high subfield indicates the ACI of the AC that indicates the BSR in the queue size high subfield. The ACI to AC mapping is defined as ACI value 0 mapping to AC_BE, ACI value 1 mapping to AC_BK, ACI value 2 mapping to AC_VI, and ACI value 3 mapping to AC_VO.

[0073] The scaling factor subfield indicates the queue size high subfield and queue size full subfield in bits per byte (SF).

[0074] The queue size high subfield indicates the buffered traffic (in SF octets) for the AC identified by the ACI high subfield, which is intended for the STA identified by the receiver address of the frame containing the BSR control subfield.

[0075] The queue size full subfield indicates the buffered traffic (in SF octets) for all ACs identified by the ACI bitmap subfield, and is intended for STAs identified by the receiver address of the frame containing this BSR control subfield.

[0076] The queue size values ​​in the queue size high subfield and queue size full subfield are: the total size of all MSDUs and A-MSDUs buffered at the STA in the delivery queues of MSDUs and A-MSDUs associated with the AC specified in the ACI high subfield and ACI bitmap subfield (including MSDUs or A-MSDUs contained in the same PSDU as the frame containing the BSR control subfield), which are rounded up to the nearest multiple of SF octets.

[0077] A queue size value of 254 in both the queue size high subfield and the queue size full subfield indicates that the buffered traffic volume is greater than 254 x SF octets. A queue size value of 255 in both the queue size high subfield and the queue size full subfield indicates that the buffered traffic volume is unspecified or unknown. Even if the queued traffic volume changes with the transmission of consecutive segments, the queue size value of the QoS data frame containing the segments can remain constant.

[0078] The MAC service provides the ability to exchange MSDUs with peer entities. To support this service, the local MAC uses an underlying PHY-level service to transfer MSDUs to the peer MAC entity. This asynchronous MSDU transfer is performed on a connectionless basis.

[0079] Figure 5 An example management frame 500 that can be used as an action frame is shown. In one example, management frame 500 includes a MAC header, a variable-length frame body, and a Frame Check Sequence (FCS). The MAC header includes a frame control field, a duration field, an address 1 field, an address 2 field, an address 3 field, a sequence control field, and an optional FIT control field. The presence of the FIT control field is determined by the setting of the +HTC subfield of the frame control field.

[0080] like Figure 5 As shown, when used as an action frame, the frame body of a management frame includes: an action field, a vendor-specific element, a Management Message Integrity Code (MME) element, a Message Integrity Code (MIC), and an Authenticated Mesh Peer Exchange element.

[0081] The action field includes a category field and an action details field. The action field provides a mechanism for specifying extended management actions. The category field indicates the category of the action frame. The action details field contains details of the action requested by the action frame.

[0082] The MME exists when negotiating management frame protection, which is a group-addressed robust action frame, and (MBSS only) the action frame's class does not support group-addressed privacy as indicated by the class value; otherwise, it does not exist.

[0083] If a shared pairwise master key (PMK) exists between the sender and receiver of a self-protection action frame, then the MIC element is present in that frame; otherwise, it is not.

[0084] If a shared PMK exists between the sender and receiver of a self-protection action frame, then an authenticated mesh peer-to-peer exchange element exists in that frame; otherwise, it does not.

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

[0086] In one example, MRTT frame 620 may include: a triggered TXOP shared mode subfield indicating TXS mode, and / or a 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).

[0087] STA 611 can respond to MRTT frame 620 by sending a Clear Transmit (CTS) frame 621 to AP 610. Subsequently, STA 611 can send non-TB PPDUs 622, 624, including one or more data frames, to AP 610 during a first time period indicated in the MRTT frame 620. In one example, AP 610 can send one or more Block Acknowledgment (BA) frames 623, 625 in response to one or more data frames contained in the non-TB PPDUs 622, 624 received from STA 611.

[0088] Figure 7 Example 700 of the TXS procedure is shown (e.g., shared mode = 2). Figure 7As shown, the TXS procedure can begin when AP 710 sends an MRTT frame 720 to STA 711. The MRTT frame 720 may allocate a portion of the TXOP obtained by AP 710 to STA 711 and may indicate that the TXS mode is equal to 2. STA 711, receiving the MRTT frame 720, can use the allocated time to send one or more non-TB PPDUs to STA 712. These one or more non-TB PPDUs may include: data frames, control frames, management frames, or action frames.

[0089] In one example, MRTT frame 720 may include: a triggered TXOP shared mode subfield indicating TXS mode, and / or a 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).

[0090] STA 711 can respond to MRTT frame 720 by sending CTS frame 721 to AP 710. Subsequently, STA 711 can send non-TB PPDUs 722, 724, including one or more data frames, to STA 712 during the first time period indicated in MRTT frame 720. In one example, STA 712 can send one or more BA frames 723, 725 in response to one or more data frames contained in non-TB PPDUs 722, 724 received from STA 711.

[0091] Figure 8 This is example 800 illustrating inefficient STA operations that may occur during the TXS process. (Example 800) Figure 8 As shown, Example 800 includes AP 802 and STAs 804, 806 and 808. STA 804 may be associated with AP 802.

[0092] In one example, AP 802 can allocate a portion of its acquired TXOP to STA 804 by sending MRTT frame 810. STA 804 can respond to MRTT frame 810 by sending CTS frame 812 to AP 802.

[0093] MRTT frame 810 may include: TXOP shared mode subfield, AID12 subfield of AID set to STA 804, and / or a first time period (e.g., X us).

[0094] In one example, the first time period can indicate the portion of time allocated by AP 802 within the acquired TXOP. In one example, the first time period can be indicated by a subfield (e.g., the allocation duration field) in MRTT frame 810. In one example, the first time period can be set to the value X us.

[0095] In one example, the TXOP sharing mode subfield is set to 2. A TXOP sharing mode subfield set to 2 indicates that STA 804 can send one or more non-TB PPDUs to AP 802 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 804. In one example, the peer STA can be STA 806. The one or more non-TB PPDUs can include: data frames, control frames, management frames, or action frames. In example 800, STA 804 can send data frame 814 to STA 806 during the first time period. STA 806 can respond to data frame 814 by sending a BA frame 816 to STA 804. STA 804 can then send data frame 818 to STA 806. STA 806 can respond to data frame 818 with a BA frame 820.

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

[0097] Figure 9 Example 900 illustrates an example TXS PS (PS) mode that can be used to address potential waste during some wake-up states. 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.

[0098] like Figure 9As shown, Example 900 can begin with AP 902 sending the first frame 910 to allocate a portion of the acquired TXOP to STA 904. Frame 910 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 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 904. The first time period can be specified in microseconds or some other time unit. In one example, frame 910 may be an MRTT frame.

[0099] Upon receiving frame 910, STA 904 may send a second frame 912 to AP 902. In one example, frame 912 may be a CTS frame. STA 904 may then send one or more non-TB PPDUs, including one or more data frames 914 and 918, to STA 906 during the first time period. STA 906 may send one or more BA frames 916 and 920 to STA 904 in response to data frames 914 and 918, respectively.

[0100] In one implementation, based on the receipt of frame 910 in which STA 908 is not allocated during the first time period, STA 908 can transition to a doze state. In the example, STA 908 can transition to the doze state at the following times: - After STA 908 receives frame 910 and before STA 908 receives frame 912 in response to frame 910; - After STA 908 receives frame 912 in response to frame 910; or - In the case where STA 908 does not receive a third frame during the second time period after STA 908 receives frame 910.

[0101] 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 902. The fourth frame can be a beacon frame, probe response frame, or association response frame.

[0102] 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 another implementation, STA 908 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.

[0103] In one implementation, AP 902 may not send the third frame 922 to STA 908 during the first time period. AP 902 may send the third frame 922 to STA 908 after the first time period.

[0104] In one implementation, AP 902 and STA 908 may exchange indications of support for TXS power saving (PS) mode before the start of Example 900. For example, STA 908 may include an indication of TXS PS mode support in its association request frame to AP 902. STA 908 may 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. This TXS PS mode field (or TXS PS support field) may be provided in the EHT MAC capability information field of the association request frame. AP 902 may include an indication of TXS PS mode support in its association response frame to STA 908. STA 908 may 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. This TXS PS mode field (or TXS PS support field) may be provided in the EHT MAC capability information field of the association response frame.

[0105] In one implementation, when STA 908 indicates support for TXS PS mode (e.g., the TXS PS field is set to 1 in the association request frame to AP 902), AP 902 can avoid sending to STA 908 during the first time period (when STA 908 is not assigned a time slot), because STA 908 can enter a dormant state during the first time period (even if STA 908 is not actually dormant during the first time period). AP 902 can continue to use this behavior for STA 908 during any subsequent TXS time periods when STA 908 is not assigned a time slot. That is, based on STA 908 having indicated support for TXS PS mode, AP 902 can refrain from sending to STA 908 during TXS time periods when STA 908 is not assigned a time slot.

[0106] However, a recent revision to the 902.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 (in TXS shared mode 2) to the AP. 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 9 Assuming STA 904 has no further traffic to send after transmitting data frame 918, STA 904 can return the remaining time of the first time period after receiving BA frame 920 from STA 906. AP 902 can use the remaining time of the first time period (e.g., to STA 906 or 908) to send downlink traffic, or can allocate a portion of the remaining time (e.g., to STA 906 or 908). 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., QoS data or QoS empty frames) from STAs allocated in TXS sharing mode 2, which include an HE variant HT control field with a CAS control subfield equal to 0 for the RDG / More (RDG / More) PPDU subfield. The AP can send a PPDU after receiving a frame with this CAS control subfield following SIFS. Conversely, a STA that receives an MRTT frame with the TXOP shared mode subfield equal to 2 can send a QoS data frame or a QoS empty frame to the associated AP within the allocated time. This QoS data frame or QoS empty frame includes an HE variant HT control field with the CAS control subfield equal to 0, wherein the STA has received from the associated AP an EHT capability element with the "TXOP return support in TXOP shared mode 2" subfield set to 1.

[0107] However, based on existing behavior, the AP can either not use the remaining time of the returned time period to send to or allocate a portion of the remaining time to an STA that indicates support for TXSPS mode and is not allocated during that time period. In fact, as mentioned above, when an STA indicates support for TXSPS mode and is not allocated during a 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, refer to... Figure 9Assuming STA908 indicates support for TXS PS mode to AP 902 (e.g., the TXS PS field is set to 1 in the association request frame to AP 902), even if STA 904 is to return the remaining time of the first time period to AP 902 after receiving BA frame 920, AP 902 may not send any data to STA 908 during the first time period (when STA 908 is not allocated time). Similarly, AP 902 may not allocate a portion of the returned remaining time to STA 908. This could happen even if STA 908 does not enter a dozing state during the first time period.

[0108] This behavior can lead to inefficiency because the AP may be limited in how it can use the remaining time of the TXS period's return. For example, the AP might have a buffered downlink service for a STA that is not allocated during the TXS period and has been indicated to support TXS PS mode. Although the STA may be awake during the TXS period, the AP must wait until the TXS period ends before it can send the buffered downlink service to the STA. In another example, the AP might want to share a portion of the remaining return time with the STA. However, because the AP might not send any transmissions to the STA during the TXS period, the AP might not send a time allocation to the STA even if the STA may be awake during the TXS period.

[0109] Figure 10 Example 1000 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 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.

[0110] like Figure 10As shown, Example 1000 may begin with STA 1008 sending an association (or reassociation) request frame 1010 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) may be set to 1 to indicate that TXS PS mode is enabled at STA 1008. 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. AP 1002 may respond to the association request frame 1010 by sending an association response frame 1012 to STA 1008. In one example, the association response frame 1012 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) may be set to 1 to indicate support for TXS PS mode at AP 1002. 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.

[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 triggered TXOP sharing procedure. For example, the TXOP sharing mode subfield may 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 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 time unit. 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-TB PPDU 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, which indicates that STA 1008 is not assigned during the first time period, and the activation of TXS PS mode at STA 1008, STA 1008 can transition to a dormant state during the first time period. According to the TX PS mode, STA 1008 can transition to a dormant state at the following times: 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 the second time period after receiving frame 1014. The third frame can be a data frame, a control frame, or a 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 1002. The fourth frame can 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 an example ( Figure 10 In a first time period (not shown), AP 1002 can receive a frame from STA 1004 indicating the release or return of the remaining time for that 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 the TXS PS mode being enabled 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 As not shown, for example, a conventional STA that does not support TXS PS mode sends frames. In another example, AP 1002 may allocate a portion of the remaining time to STA 1006.

[0115] In Example 1000, STA 1008 may return to the wake-up state after the end of the first time period or at least from the beginning of the end of the first time period. STA 1008 may then send an association (or reassociation) request frame 1022 to AP 1002. In one example, association request frame 1022 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) may be set to 0 to indicate that TXS PS mode is disabled at STA 1008. The TXS PS mode field (or TXS PS support field) may be provided in the EHT MAC capability information field of association request frame 1022. AP 1002 may respond to association request frame 1022 by sending an association response frame 1024 to STA 1008. In one example, association response frame 1024 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 support for TXS PS mode at AP 1002. 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.

[0116] 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 may indicate the triggered TXOP sharing procedure. For example, the TXOP sharing mode subfield may 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 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 time unit. In one example, frame 1026 may be an MRTT frame.

[0117] 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-TB PPDU 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.

[0118] Upon receiving frame 1026, in which STA 1008 is not allocated during the first time period, and based on disabling TXS PS mode at STA 1008, STA 1008 can remain awake during the first time period. In an example ( Figure 10 (Not shown in the image) AP 1002 may receive a frame from STA 1004 during a first time period, indicating the release or return of the remaining time for 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 may 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 may allocate a portion of the remaining time to STA 1008. Depending on the indicated TXS mode, STA 1008 may use the allocated portion of the remaining time to send to AP 1002 or to another STA.

[0119] The advantage of Example 1000 is that it reuses existing (re)association request / response frames (with minor modifications) to enable the STA to signal the AP to enable or disable TXS mode. However, because the (re)association request / response frames contain information about the various capabilities supported by the STA / AP, their size can potentially be large, thus Example 1000 may lead to increased signaling overhead. The construction of the (re)association request / response frames may also require relatively large processing times at the STA / AP. Therefore, the signaling of a change in TXS PS mode state at the STA and the AP's confirmation of the change in TXS PS mode state at the STA may take a significant amount of time, resulting in suboptimal operation.

[0120] Figure 11 An example is shown that could begin with STA 1108 sending an association (or reassociation) request frame 1110 to AP 1102. In one example, association request frame 1110 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) could be set to 1 to indicate that STA 1108 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 request frame 1110.

[0121] In one implementation, STA 1108's support for TXS PS mode may include: STA 1108 being able 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. The 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 being able to send a frame to the AP indicating whether TXS PS mode is enabled or disabled, as described herein. In one example, the frame may include a TXS PS (TPS) control subfield (further described below) 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's support for TXS PS mode may include: when STA 1108 sets the TPS disable subfield to 0, STA 1108 is able to enter a dozing state during a TXS period that is not allocated to STA 1108 (e.g., via MRTT frames).

[0122] 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) can be set to 1 to indicate that AP 1102 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 1112.

[0123] 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 example, 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: when a TXS time period is not allocated (e.g., via an MRTT frame) to a STA that has the TPS disable subfield set to 0, AP 1102 may not send (or avoid sending) any frames to that STA during the TXS time period.

[0124] Subsequently, in one example, STA 1108 may send frame 1134 indicating that TXS PS mode is enabled at STA 1108. Frame 1134 may be a QoS data frame, a QoS empty frame, an action frame, a control frame, or a 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.

[0125] In one example, frame 1134 can be a QoS data frame or a QoS empty frame. A QoS data frame 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 can be carried in the HT control field of the QoS data frame or the QoS empty frame. In one example, 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 1108, and can be set to 1 to indicate that TXS PS mode is disabled at STA 1108. The TPS control subfield may also include reserved bits.

[0126] In another example, frame 1134 can 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 example, the action frame 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 1108, and can be set to 1 to indicate that TXS PS mode is disabled at STA 1108. The TPS control subfield may also include reserved bits.

[0127] In one implementation, AP 1102 can acknowledge frame 1134 by sending acknowledgment frame 1136 to STA 1108. Acknowledgment frame 1136 can be an ACK frame or a BA frame.

[0128] 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 may indicate the triggered TXOP sharing procedure. For example, the TXOP sharing mode subfield may 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 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 1104. The first time period may be specified in microseconds or some other time unit. In one example, frame 1114 may be an MRTT frame.

[0129] 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-TB PPDU including data frame 1118 to STA 1106 during a first time period. STA 1106 may send BA frame 1120 to STA 1104 in response to data frame 1118.

[0130] Based on the receipt of frame 1114, which indicates that STA 1108 is not allocated during the first time period, and the activation of TXS PS mode at STA 1108, STA 1108 can transition to a dormant state during the first time period. According to the TX PS mode, STA 1108 can transition to a dormant state at the following times: 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 the second time period after receiving frame 1114. The third frame can be a data frame, a control frame, or a 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 1102. The fourth frame can be a beacon frame, a probe response frame, or a correlation response frame.

[0131] 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 for 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 As not shown, for example, a conventional STA that does not support TXS PS mode transmits frames. In another example, AP1102 may allocate a portion of the remaining time to STA 1106.

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

[0133] In one implementation, AP 1102 can acknowledge frame 1138 by sending acknowledgment frame 1140 to STA 1108. Acknowledgment frame 1140 can be an ACK frame or a BA frame.

[0134] Subsequently, AP 1102 can send frame 1126 to allocate a portion of the acquired TXOP to STA 1104. Frame 1126 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 triggered TXOP sharing procedure. For example, the TXOP sharing mode subfield may 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 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 1104. The first time period may be specified in microseconds or some other time unit. In one example, frame 1126 may be an MRTT frame.

[0135] Upon receiving frame 1126, STA 1104 may send frame 1128 to AP 1102. In one example, frame 1116 may be a CTS frame. STA 1104 may then transmit a non-TB PPDU including data frame 1130 to STA 1106 during a first time period. STA 1106 may send BA frame 1132 to STA 1104 in response to data frame 1130.

[0136] Upon receiving frame 1126, in which STA 1108 is not allocated during the first time period, and based on disabling TXS PS mode at STA 1108, STA 1108 can remain awake during the first time period. In one example ( Figure 11 (Not shown in the image), AP 1102 can receive a frame from STA 1104 during a first time period indicating the release or return of the remaining time for 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 1108, AP 1102 can send frames to STA 1108 during the remaining time of the first time period. In another example, based on disabling the TXS PS mode at STA 1108, AP 1102 can allocate a portion of the remaining time to STA 1108. Depending on the indicated TXS mode, STA 1108 can use the allocated portion of the remaining time to send to AP 1102 or to another STA.

[0137] Figure 11 The advantages of this other example shown include reduced signaling overhead and latency for the STA to signal the AP to the STA regarding the TXS PS mode state change. 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 this frame from the STA with a short acknowledgment frame instead of a relatively large association response frame.

[0138] In yet another example, similar to the previous one, 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 example, the AP can send a frame to the STA requesting the TXS PS mode status at the STA before initiating TXS operation.

[0139] Figure 12 Example 1200 of existing operation is shown, where the TXOP acquired by a non-AP STA is shared with the AP. For example... Figure 12 As shown, Example 1200 includes AP 1210 and STAs 1211 and 1212 associated with AP 1210. In some cases, after a non-AP STA has completed transmitting / receiving using the TXOP, the non-AP STA may optionally share its TXOP with the AP (e.g., with which the non-AP STA is associated).

[0140] like Figure 12 As shown, Example 1200 can begin with STA 1211 acquiring a TXOP and sending an RTS frame 1216 to AP 1210. The TXOP can have a duration of 1250. AP 1210 can respond to RTS frame 1216 with a CTS frame 1215. Based on the receipt of CTS frame 1215, STA 1211 can send a data frame 1240 to AP 1210. AP 1210 can respond to data frame 1240 by sending a BA frame 1230 to STA 1211. In this example, after sending data frame 1240, STA 1211 has no more data frames to send during the TXOP duration of 1250. In one example, STA 1211 can indicate this by setting the "more data" field in data frame 1240 to zero. Based on this completion of STA 1211's utilization of TXOP duration 1250, as shown in the figure, STA 1211 can send a reverse TXOP sharing control frame (CTRL) 1280 to AP 1210, for example, to share a portion of TXOP duration 1250 with AP 1210, which begins at tag 1245 and continues to share TXOP duration 1255.

[0141] In this example, the shared TXOP duration 1255 can correspond to the remaining portion of the TXOP duration 1250. However, although STA 1211 has shared the remaining portion of the TXOP duration 1250 with AP 1210, STA 1211 remains in a wake-up state 1260 for the entire shared TXOP duration 1255. Because STA 1211 has no additional data to send (or receive from AP 1210) during the shared TXOP duration 1255, remaining in a wake-up state 1260 during the shared TXOP duration 1255 would unnecessarily increase the power consumption of STA 1211.

[0142] As further described below, embodiments of this disclosure address the aforementioned problem where the STA unnecessarily and wastefully remains in a wake-up state after returning a first time period (e.g., TXOP duration) to the AP. In one aspect, the STA can transition to a power-saving mode during a portion of the TXOP shared by the STA and the AP. In another aspect, the STA can send a frame to the AP sharing the transmission opportunity (TXOP). In some embodiments, this power state transition can include a transition from a first power state to a second power state after the STA sends the frame. In another aspect, the frame may also include an indication of sharing the remainder of the TXOP with the AP. Regarding this transition between states, in some embodiments, the first power state may include a wake-up power state, and the second power state may include a relatively low-power power state, such as a drowsy power state. Therefore, according to one or more embodiments, the STA can avoid unnecessarily and wastefully remaining in a wake-up state after returning the first time period to the AP.

[0143] STA can thus avoid unnecessarily and wastefully remaining in the wake-up state after returning the first time period to AP.

[0144] Figure 13 Example 1300 illustrates one or more embodiments that can utilize power-saving operation during operation where the STA and AP share the TXOP. (e.g.) Figure 13 As shown, Example 1300 includes AP 1310 and STAs 1311 and 1312 associated with AP 1310. Figure 13 As shown, Example 1300 can begin with STA 1311 acquiring a TXOP and sending an RTS frame 1316 to AP 1310. The TXOP can have a TXOP duration of 1350.

[0145] AP 1310 can respond to RTS frame 1316 with CTS frame 1315. Based on the receipt of CTS frame 1315, STA 1311 can send data frame 1340-1 to AP 1310. AP 1310 can respond to data frame 1340-1 by sending BA frame 1330-1 to STA 1311. In this example, after sending data frame 1340-1, STA 1311 has no further data frames to send during the TXOP duration of 1350.

[0146] Based on this completion of STA 1311's utilization of the TXOP duration 1350, in some cases, STA 1311 can transmit CTRL frame 1380 to share a portion of the TXOP duration 1350 with AP 1310, for example, a portion that begins at tag 1345 and continues sharing the TXOP duration 1355. In this example, based on the TXOP sharing at 1345, AP 1310 can utilize the shared TXOP duration 1355 to send data frame 1340-2 to STA 1311. STA 1311 can successfully receive data frame 1340-2 and can send BA frame 1330-2 in response.

[0147] Continuing with the example above... Figure 12 Conversely, after STA 1311 has shared the remainder of the TXOP duration 1350 with AP 1310, in one or more embodiments, STA 1311 may enter a dozing state 1365. For example, according to one or more embodiments, after STA 1311 receives data frame 1340-2 and sends BA frame 1330-2 in response, STA 1311 may transition from a first power state (e.g., STA 1311 is in a wake-up state 1360) to a second power state (e.g., STA 1311 is in a dozing state 1365). In one or more embodiments, this transition may be based on a combination of one or more factors, including but not limited to: the sharing mode of the TXOP portion allocated to AP 1310, and STA 1311 sharing the remainder of the TXOP duration 1350 with AP 1310.

[0148] Therefore, based on the transition from the awake state 1360 to the dozing state 1365, one or more embodiments can solve the aforementioned problems that may be associated with the STA unnecessarily and wastefully remaining in the awake state after sharing the TXOP duration with the AP, for example, as described above regarding Figure 12 The subject of discussion.

[0149] While one or more embodiments can address the wasteful wake-up state problem discussed above, problems may arise in some cases due to STA 1311 transitioning to dozing state 1365 after point 1323, as described below. In an example illustrating a potential problem that may occur when STA 1311 transitions to dozing state 1365, as shown in the figure, at point 1322, AP 1310 may receive and buffer additional data frames for STA 1311.

[0150] Therefore, after the slumber state 1365 for STA 1311 begins at point 1323, AP 1310 may attempt to send a buffered data frame, such as data frame 1340-3, to STA 1311 during the shared TXOP duration 1355. In this example, because the transmission of data frame 1340-3 to STA 1311 occurs while STA 1311 is in the slumber state 1365, a reception failure 1325 may occur. In some implementations, based on the shared TXOP duration 1350 between STA 1311 and AP 1310, data frame 1340-3 may have been prioritized for transmission to STA 1311 over other data intended for other STAs, thereby increasing the likelihood of reception failure 1325, as in this example.

[0151] In some cases, reception failure 1325 may lead to network performance degradation. For example, reception failure of data frames (e.g., 1340-3) for a STA that has entered a sleep state 1365 to conserve energy (e.g., STA 1311), transmission failure of data frames for other STAs attempting to send data frames to the STA in sleep state 1365 to conserve energy, and wasted retransmissions of data frames by the AP associated with the STA in sleep state 1365 to conserve energy. In some situations, the data frames missed by the STA in sleep state 1365 may be low-latency data frames, resulting in application performance degradation.

[0152] As further described below, embodiments of this disclosure address the aforementioned problems, such as network performance degradation caused by reception failures. In one aspect, the STA may send a first frame to the AP indicating a power state transition, for example, STA 1411 will become unavailable due to switching to a power-saving mode. In another aspect, the STA may send a second frame to the AP sharing a transmission opportunity (TXOP). In some embodiments, the power state transition may include the STA transitioning from a first power state to a second power state after sending the second frame. In one aspect, the second frame may also include an indication of the remaining portion of the TXOP shared with the AP. Regarding the transition between states, in some embodiments, the first power state may include a wake-up power state, and the second power state may include a relatively low-power power state, such as a drowsy power state.

[0153] Therefore, according to one or more embodiments, STA can avoid network performance degradation, such as degradation associated with reception failure.

[0154] Figure 14 Example 1400 illustrates one or more embodiments that can provide STA unavailability information to an AP that is part of a TXOP allocated by a STA. For example... Figure 14As shown, Example 1400 includes AP 1410 and STAs 1411 and 1412 associated with AP 1410. As... Figure 14 As shown, Example 1400 can begin with STA 1411 performing a random backoff 1405 and gaining access to the shared medium to obtain a TXOP. The TXOP can have a TXOP duration of 1450.

[0155] AP 1410 can respond to RTS frame 1416 with CTS frame 1415. Based on the receipt of CTS frame 1415, STA 1411 can send data frame 1440-1 to AP 1410. AP 1410 can respond to data frame 1440-1 by sending BA frame 1430-1 to STA 1411. In this example, after sending data frame 1440-1, STA 1411 has no more data frames to send during the TXOP duration 1450. In one example, STA 1411 can indicate this by setting the "More Data" field in data frame 1440-1 to zero. Based on this completion of STA 1411's utilization of TXOP duration 1450, as shown in the figure, STA 1411 can send a reverse TXOP sharing control frame (CTRL) 1480 to AP 1410, for example, to share a portion of TXOP duration 1450 with AP 1410, which begins at tag 1445 and continues to share TXOP duration 1455.

[0156] In one or more embodiments, based on this completion of STA 1411's utilization of the TXOP duration 1450 and this portion of the TXOP duration 1450 shared with AP 1410, in certain circumstances, STA 1411 may determine that it enters a dozing state 1465 (e.g., after the awakening state 1460) within a certain portion of the shared TXOP duration 1455. Figure 12 and 13 Conversely, STA 1411 can utilize CTRL frame 1480 to additionally indicate that STA 1411 will be unavailable for the duration of TXOP 1455 (e.g., after the dozing state begins at point 1423). In one or more embodiments, information describing the unavailability of STA 1411 can be indicated to AP 1410 by setting the "More Data" field in CTRL frame 1480 to zero, for example, without needing to add an additional field to CTRL frame 1480.

[0157] In this example, based on the shared TXOP at 1445, AP 1410 can use the shared TXOP duration 1455 to send data frame 1440-2 to STA 1411, where STA 1411 successfully receives data frame 1440-2 and sends BA frame 1430-2 in response.

[0158] Figure 14 The following examples illustrated in the diagram show how one or more embodiments can address the aforementioned network performance degradation associated with the STA entering a dozing state after the remainder of the shared TXOP duration of 1350 (e.g., the above regarding...). Figure 13 The described reception failure is 1325. In this example, at point 1422, AP 1410 can receive and buffer additional data for STA 1411. Figure 14 As shown, in contrast to sending data frame 1340-3 to STA 1311 in a dozing state 1365 (e.g., causing a reception failure 1325), although AP 1410 also receives and buffers additional data for STA 1411, AP 1410 can suppress sending any frames to STA 1411 during the shared TXOP duration 1455, based on the indication included in CTRL frame 1480. Instead, AP 1410 can send data frame 1440-3 only to STA 1412 (causing BA 1430-3 to be sent in response). Therefore, in some implementations, CTRL frame 1480 can prevent the above-mentioned... Figure 13 The network performance degradation issue described.

[0159] Figure 15 Example 1500 illustrates one or more embodiments that can provide STA unavailability information to an AP that is part of a TXOP allocated by a STA. Figure 15 As shown, Example 1500 includes AP 1510 and STAs 1511 and 1512 associated with AP 1510. As... Figure 15 As shown, Example 1500 can begin with STA 1511 performing a random backoff 1505 and gaining access to the shared medium to obtain a TXOP. The TXOP can have a TXOP duration of 1550.

[0160] AP 1510 can respond to RTS frame 1516 with CTS frame 1515. Based on the receipt of CTS frame 1515, STA 1511 can send data frame 1540-1 to AP 1510. AP 1510 can respond to data frame 1540-1 by sending BA frame 1530-1 to STA 1511. In this example, after sending data frame 1540-1, STA 1511 has no more data frames to send during the TXOP duration 1550. In one example, STA 1511 can indicate this by setting the "More Data" field in data frame 1540-1 to zero.

[0161] Based on this completion of STA 1511's utilization of TXOP duration 1550, as shown in the figure, STA 1511 can send a reverse TXOP sharing control frame (CTRL) 1580 to AP 1510, for example, to share a portion of TXOP duration 1550 with AP 1510, which begins at tag 1545 and continues to share TXOP duration 1555.

[0162] As shown in the figure, in order to provide AP 1510 with an indication that STA 1511 will enter a nap state 1565 (e.g., at point 1523 after wake state 1560) during a portion of the shared TXOP duration 1555, one or more embodiments may include indication 1542 within data frame 1540-1.

[0163] One method that can be used by one or more embodiments to provide indication 1542 is as follows: prior to the reverse TXOP sharing at 1545, STA 1511 sends a BSR report in data frame 1540-1, indicating an empty buffer during the transmissions performed by STA 1511 during the TXOP duration 1550. In one embodiment, the BSR report can be provided in the A-control subfield of the HT control field of data frame 1540-1. In another embodiment ( Figure 15 In (not shown), QoS empty frames (e.g., QoS empty frames may have the following characteristics) can be aggregated with data frame 1540-1. Figure 4 The BSR report is provided in the A-control subfield of the HT control field (as shown in the format). In one or more embodiments, AP 1510 can be configured to interpret the empty buffer BSR report as an indication that STA 1511 will be in a dozing state for a portion of the shared TXOP duration 1555. In this method, CTRL frame 1580 may include a reverse TXOP sharing indication, but not the dozing state indication included with data frame 1540-1.

[0164] Another method for providing indication 1542 includes providing indication 1542 as a PS flag in the A-control subfield of the HT control field of data frame 1540-1. For example, the A-control subfield of the HT control field of the data frame may have, for example, a PS flag in the A-control subfield of the HT control field of the data frame. Figure 4 The format is shown. One or more bits in the A-Control subfield can be used to carry the PS flag. For this method, a new Control ID field can be used to indicate that the control information field includes the PS flag. Similar to the previous approach, the PS flag in the A-Control subfield indicates that it can be carried in the HT control field of the QoS empty frame aggregated with data frame 1540-1. In this example, based on the TXOP sharing at 1545, AP 1510 can utilize the shared TXOP duration 1555 to send data frame 1540-2 to STA 1511. STA 1511 can successfully receive data frame 1540-2 and send BA frame 1530-2 in response. Continuing the example, as shown, during the TXOP duration 1550, AP 1510 can receive and buffer additional data frames for STA 1511.

[0165] like Figure 15 As shown, although AP 1510 also receives and buffers additional data frames for STA 1511 at point 1522, one or more embodiments can prevent the above-mentioned... Figure 13 The described network performance degradation problem is, for example, based on sending data frame 1340-3 to STA 1311, which is in a dozing state 1365 (e.g., causing reception failure 1325). For example, in one or more embodiments, based on unavailability information included in indication 1542 (e.g., STA 1511's use of a power-saving operating mode), AP 1510 may avoid sending any frames to STA 1511 during the shared TXOP duration 1555. Instead, AP 1510 may only send data frame 1540-3 to STA 1512 (causing BA 1530-3 to be sent in response). In one or more embodiments, the method can avoid reception failure by not sending buffered data frames to STA 1511 for the remainder of the shared TXOP duration 1555. Therefore, in some implementations, indication 1542 can prevent the above-mentioned... Figure 13 The network performance degradation issue described.

[0166] Figure 16 Example 1600, illustrating one or more embodiments, is shown that can utilize action frames to signal PS information to an AP that has a portion of the TXOP allocated by the STA. For example... Figure 16As shown, Example 1600 includes AP 1610 and STAs 1611 and 1612 associated with AP 1610.

[0167] like Figure 16 As shown, Example 1600 may begin with STA 1611 sending a mode frame 1618. In one or more embodiments, mode frame 1618 may include information provided by STA 1611 to AP 1610 corresponding to STA 1611's operation in RTXOP PS mode. For example, STA 1611 may switch to a power-saving mode (e.g., drowsy state 1665) based on STA 1611 utilizing RTXOP operation to share a portion of TXOP duration 1650 with AP 1610 (e.g., sharing TXOP duration 1655). In one or more embodiments, mode frame 1618 may be an action frame. Thus, the RTXOP PS mode can be indicated to AP 1610 via the PS flag in the RTXOP PS element of mode frame 1618. In other embodiments, mode frame 1618 may include an association frame, an authentication frame, and / or another similar frame. In response to mode frame 1618, AP 1610 may respond with an acknowledgment frame 1619.

[0168] Continuing with Example 1600, STA 1611 performs random backoff 1605 and gains access to the shared medium to obtain a TXOP. The TXOP can have a duration of 1650. AP 1610 can respond to RTS frame 1616 with CTS frame 1615. Based on the receipt of CTS frame 1615, STA 1611 can send data frame 1640-1 to AP 1610. AP 1610 can respond to data frame 1640-1 by sending BA frame 1630-1 to STA 1611. In this example, after sending data frame 1640-1, STA 1611 has no more data frames to send during the TXOP duration of 1650. In one example, STA 1611 can indicate this by setting the "More Data" field in data frame 1640-1 to zero.

[0169] In one or more embodiments, based on the completion of STA 1611’s utilization of TXOP duration 1650, in certain circumstances, STA 1611 may determine to operate according to the RTXOP PS mode specified by mode frame 1618, for example, a mode that may facilitate STA 1611’s transition to nap state 1665 within a portion of the shared TXOP duration 1655.

[0170] Continuing this example, to achieve reverse TXOP sharing with AP 1610, STA 1611 can send CTRL frame 1680 to AP 1610. In this example, STA 1611's communication regarding the use of RTXOP PS mode can be accomplished via mode frame 1618 discussed above, for example, without referring to the above... Figure 14 The CTRL frame 1680 described is used to complete this. Based on the shared TXOP at tag 1645, AP 1610 can use the shared TXOP duration 1655 to send data frame 1640-2 to STA 1611. STA 1611 can successfully receive data frame 1640-2 and can send BA frame 1630-2 in response. Continuing the example, as shown, just before tag 1623, which marks the start of STA 1611's nap state 1665 (e.g., after wake-up state 1660), at point 1622, AP 1610 can receive and buffer additional data frames for STA 1611.

[0171] Continuing this example, as shown at point 1622, AP 1610 can receive and buffer additional data for STA 1611. Figure 16 As shown, instead of sending data frame 1340-3 to STA 1311 in a dozing state 1365 (e.g., causing reception failure 1325), AP 1610 can avoid sending any frames to STA 1611 during the shared TXOP duration 1655, based on the RTXOP PS mode specified in mode frame 1618. Instead, AP 1610 can send data frame 1640-3 only to STA 1612 (causing BA 1630-3 to be sent in response). Therefore, in some implementations, mode frame 1618 can prevent the above-mentioned... Figure 13 The network performance degradation issue described.

[0172] Figure 17 An example process 1700 according to one embodiment is shown. Example process 1700 can be executed by STAs (such as STA 1411, STA 1412, STA 1511, STA 1512, STA 1611, and STA 1612 described above). Figure 17 As shown, process 1700 may include steps 1702 and 1704.

[0173] Step 1702 includes: the STA sending a first frame to the AP, the first frame indicating a power state transition, for example, the STA will become unavailable due to switching to power-saving mode. Step 1704 includes: the STA sending a second frame to the AP to share a transmission opportunity (TXOP) obtained by the STA with the AP.

[0174] In an additional or alternative embodiment, the power state transition may include a power state transition from a first power state to a second power state by the STA after transmitting a second frame. The second frame may also include an indication regarding sharing the remaining portion of the TXOP with the AP. In an additional or alternative embodiment, regarding the power state transition, the first power state may include a wake-up power state, and the second power state may include a power state with lower power consumption than the wake-up power state. In an additional or alternative embodiment, this power state may correspond to a dozing power state.

[0175] In additional or alternative embodiments, the power state transition includes a power state transition for the remainder of the TXOP. In additional or alternative embodiments, the second frame includes a control frame, trigger frame, Quality of Service (QoS) empty frame, QoS data frame, or management frame for sharing the TXOP. In additional or alternative embodiments, the power state transition indicating a second power state includes indicating that more data fields are zero in the second frame.

[0176] In additional or alternative embodiments, indicating a transition to the second power state may include indicating that the uplink BSR is zero in the second frame. In one embodiment, the uplink BSR may be included in the A-control field of the second frame. In additional or alternative embodiments, a response to the third frame may include an acknowledgment frame (ACK), a block ACK, or an action frame. In additional or alternative embodiments, the third frame may include an action frame, an association response frame, a probe request frame, or an authentication request frame. In additional or alternative embodiments, process 1700 may further include receiving the third frame from the AP. In additional or alternative embodiments, the third frame may include an indication regarding whether the first STA is allowed to be in the second power state. In additional or alternative embodiments, the power state transition may be based on this indication.

[0177] In additional or alternative embodiments, the indication regarding whether the first STA is allowed to be in the second power state may include an indication regarding the end of the transmission from the AP to the first STA during TXOP. In additional or alternative embodiments, the indication regarding whether the first STA is allowed to be in the second power state may include: the first STA receiving a fourth frame sent by the AP to the second STA. In additional or alternative embodiments, the fourth frame may include the address of the second STA in the receive address field of the fourth frame.

[0178] In an additional or alternative embodiment, process 1700 may further include: a first STA transitioning from a second power state to a first power state before or during the end of the TXOP. In an additional or alternative embodiment, the first power state may correspond to a wake-up state. In an additional or alternative embodiment, the second power state may correspond to a dozing state. In an additional or alternative embodiment, the second power state may correspond to an unavailable state of the STA.

[0179] Figure 18 Another example process 1800 according to an embodiment is shown. Example process 1800 can be executed by an AP (such as AP 1410, AP 1510, and AP 1610 described above). Figure 18 As shown, process 1800 may include step 1802.

[0180] Step 1802 includes: the access point (AP) sending a first frame to the first station (STA) during a transmission opportunity (TXOP) shared by the first STA and the AP, the first frame indicating that the first STA is permitted to be in a first power state during the TXOP. In an additional or alternative embodiment, process 1800 may further include: receiving an indication of a power state transition from a second power state to the first power state during the TXOP, based on the STA being permitted to be in the first power state. In an additional or alternative embodiment, the power state transition may include a power state transition for the remainder of the TXOP.

[0181] In an additional or alternative embodiment, the second power state may include a wake-up power state, and the first power state may include a nap power state. In an additional or alternative embodiment, process 1800 may further include: the AP receiving a second frame from the STA, the second frame including a first indication regarding sharing a TXOP with the AP.

[0182] In additional or alternative embodiments, the second frame may also include an indication of sharing the remaining portion of the TXOP with the AP. In additional or alternative embodiments, the first power state may include a wake-up power state, and the second power state may include a power state with lower power consumption than the wake-up power state.

[0183] In additional or alternative embodiments, the first frame may include a control frame for sharing the TXOP. In additional or alternative embodiments, the first frame may include a trigger frame. In additional or alternative embodiments, the first frame may include a Quality of Service (QoS) empty frame, a QoS data frame, or a management frame. In additional or alternative embodiments, a power state transition indicating a first power state may include indicating a more data field value of zero in the second frame. In additional or alternative embodiments, a power state transition indicating a first power state may include indicating an uplink buffer state report (BSR) of zero in the second frame. In an embodiment, the uplink BSR is indicated in the A-control field of the second frame.

Claims

1. A method comprising: The station (STA) sends a first frame to the access point (AP), which indicates a power state transition; The STA sends a second frame to the AP to share the transmission opportunity (TXOP) obtained by the STA. as well as Based on the power state transition, the STA transitions from the first power state to the second power state for the remaining portion of the TXOP.

2. A method comprising: The station (STA) sends a first frame to the access point (AP), which indicates a power state transition; as well as The STA sends a second frame to the AP, sharing the transmission opportunity (TXOP) obtained by the STA with the AP.

3. The method according to claim 2, wherein, The power state transition includes a power state transition from a first power state to a second power state after the second frame is transmitted.

4. The method according to claim 3, wherein, The second frame also includes an indication of sharing the remaining portion of the TXOP with the AP.

5. The method according to claim 3, wherein, The first power state includes a wake-up power state, and the second power state includes a power state having lower power consumption than the wake-up power state.

6. The method according to claim 5, wherein, The second power state includes a dozing power state.

7. The method according to claim 3, wherein, The power state transitions include power state transitions for the remaining portion of the TXOP.

8. The method according to any one of claims 3-7, wherein, The second frame includes a control frame for sharing the TXOP.

9. The method according to any one of claims 2-7, wherein, The second frame includes the trigger frame.

10. The method according to claims 2-7, wherein, The second frame includes a Quality of Service (QoS) empty frame, a QoS data frame, or a management frame.

11. The method according to claim 8, wherein, The power state transition indicating the second power state includes indicating that a more data field value is zero in the second frame.

12. The method according to claim 8, wherein, The power state transition indicating the second power state includes: indicating that the uplink buffer state report (BSR) is zero in the second frame.

13. The method according to claim 12, wherein, The uplink BSR is indicated in the A-control field of the second frame.

14. The method according to claim 3, further comprising: The STA sends a third frame to the AP before the TXOP, wherein the power state transition to the second power state is based on receiving a response to the third frame.

15. The method according to claim 14, wherein, The response to the third frame includes an acknowledgment frame (ACK), a block ACK, or an action frame.

16. The method according to any one of claims 14-15, wherein, The third frame includes an action frame, an associated response frame, a probe request frame, or an authentication request frame.

17. The method according to any one of claims 3-14, further comprising: A third frame is received from the AP, wherein the third frame includes an indication of whether the STA is allowed to be in the second power state, and wherein the power state transition is based on the indication.

18. The method according to claim 17, wherein, The indication of whether the STA is allowed to be in the second power state includes: an indication of the end of the transmission from the AP to the STA during the TXOP.

19. The method according to claim 17, wherein, The indication of whether the STA is allowed to be in the second power state includes: the STA receiving a fourth frame sent by the AP to the second STA.

20. The method according to claim 19, wherein, The fourth frame includes the address of the second STA in the receive address field of the fourth frame.

21. The method according to any one of claims 3-20, further comprising: Before or during the end of the TXOP, the STA switches from the second power state to the first power state.

22. The method according to any one of claims 3-21, wherein, The first power state is a wake-up state.

23. The method according to any one of claims 3-22, wherein, The second power state is a dozing state.

24. The method according to any one of claims 3-21, wherein, The second power state is the unavailable state of the STA.

25. A method comprising: During a transmission opportunity (TXOP) obtained by a station (STA), the access point (AP) receives a first frame from the STA, the first frame comprising: A first instruction to share the TXOP with the AP; and A second indication by which the STA transitions from a first power state to a second power state during the TXOP; and The AP sends a second frame to the STA, the second frame indicating that the STA is allowed to be in the second power state during the TXOP.

26. A method comprising: During a Transmission Opportunity (TXOP) shared between a station (STA) and the AP, the access point (AP) sends a first frame to the STA, the first frame indicating that the STA is permitted to be in a first power state during the TXOP.

27. The method of claim 26, further comprising: Based on allowing the STA to be in the first power state, during the TXOP, an indication of a power state transition from the second power state to the first power state is received.

28. The method according to claim 27, wherein, The power state transition includes: transitioning the remaining portion of the TXOP.

29. The method according to claim 27, wherein, The second power state includes a wake-up power state, and the first power state includes a nap power state.

30. The method according to claims 27-29, further comprising: The AP receives a second frame from the STA, the second frame including a first indication of sharing the TXOP with the AP.

31. The method according to claim 30, wherein, The second frame also includes an indication of sharing the remaining portion of the TXOP with the AP.

32. The method according to claim 27, wherein, The first power state includes a wake-up power state, and the second power state includes a power state having lower power consumption than the wake-up power state.

33. The method according to any one of claims 26-32, wherein, The first frame includes a control frame for sharing the TXOP.

34. The method according to any one of claims 26-31, wherein, The first frame includes a trigger frame.

35. The method according to claims 26-31, wherein, The first frame includes a Quality of Service (QoS) empty frame, a QoS data frame, or a management frame.

36. The method according to claim 26, wherein, Indicating that the STA is allowed to be in the first power state includes indicating that more data fields have a value of zero in the first frame.

37. The method of claim 30, wherein, Receiving the indication for the power state transition includes receiving an uplink buffer status report (BSR) of zero in the second frame.

38. The method according to claim 37, wherein, The uplink BSR is indicated in the A-control field of the second frame.

39. 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-38.

40. 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-38.

Images