Triggered transmission opportunity (TXOP) shared power saving mode operation

Abstract

In one aspect, an access point (AP) receives, from a first station (STA), a first frame indicating that a triggered transmission opportunity (TXOP) sharing (TXS) power saving mode is enabled or disabled at the first STA. The AP transmits a trigger frame that shares a time period of the TXOP with the second STA. The AP avoids transmission to the first STA during the time period based on the first frame indication enabling the TXS power saving mode at the first STA. In another aspect, the first STA receives, from the AP, a first frame that shares a time period of TXOP with the second STA. The first STA transitions a power state of the first STA to a sleep state based on a TXS power saving mode being enabled at the first STA.

Description

Cross-reference to related applications

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 537,232, filed September 8, 2023, which is hereby incorporated in its entirety by reference. Attached Figure Description

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

[0005] Figure 3 An example of Target Wake Time (TWT) operation is shown.

[0006] Figure 4 An example of TWT operation is shown in an environment that includes AP multilink devices (AP MLD) and station multilink devices (STA MLD).

[0007] Figure 5 This demonstrates a sample TWT element that can be used to support individual TWT operations.

[0008] Figure 6 Example TWT elements that can be used to support restricted TWT (r-TWT) operations are shown.

[0009] Figure 7 An example of a standalone TWT operation is shown.

[0010] Figure 8 An example of broadcast TWT operation is shown.

[0011] Figure 9 An example of TWT protection in a standalone TWT operation is shown.

[0012] Figure 10 This demonstrates a sample MRTT frame that can be used in the TXS program.

[0013] Figure 11 An example of a TXS program (mode = 1) is shown.

[0014] Figure 12 An example of a TXS program (mode = 2) is shown.

[0015] Figure 13 This is an example demonstrating a sample TXS procedure between multiple linked devices (MLDs).

[0016] Figure 14 This is an example demonstrating inefficient STA operations that can occur during the TXS procedure.

[0017] Figure 15 This is an example demonstrating the TXS PS (PS) mode.

[0018] Figure 16 This is an example of STA demonstrating the enabling or disabling of TXS PS mode according to an embodiment.

[0019] Figure 17 This is an example of STA demonstrating the enabling or disabling of TXS PS mode according to another embodiment.

[0020] Figure 18 This is an example of STA demonstrating the enabling or disabling of TXS PS mode according to another embodiment.

[0021] Figure 19 Example control information subfields that can be used in the embodiments are shown.

[0022] Figure 20 Example action frames that can be used in the embodiments are shown.

[0023] Figure 21 An example process according to an embodiment is shown.

[0024] Figure 22 Another example process according to an embodiment is shown. Detailed Implementation

[0025] In this disclosure, various embodiments are presented in the form of examples of how the disclosed techniques can be implemented and / or how the disclosed techniques can be practiced in environments and scenarios. It will be apparent to those skilled in the art that various changes in form and detail can be made therein without departing from the scope. Alternative embodiments will become apparent to those skilled in the art upon reading this specification. Embodiments of the invention are not limited to any of the exemplary embodiments described. Embodiments of this disclosure will be described with reference to the accompanying drawings. Limitations, features, and / or elements from the disclosed exemplary embodiments can be combined to create further embodiments within the scope of this disclosure. Any diagrams highlighting functionality and advantages are given for illustrative purposes only. The disclosed architecture is flexible and configurable enough that it can be utilized in ways other than those shown. For example, any actions listed in a flowchart can be reordered or used only optionally in certain embodiments.

[0026] The embodiments can be configured to operate as needed. When certain criteria are met, the disclosed mechanisms can be executed, for example, in stations, access points, radio environments, networks, combinations thereof, etc. Example standards may be based at least in part on, for example, wireless device or network node configuration, traffic load, initial system setup, packet size, traffic characteristics, combinations thereof, etc. Various example embodiments can be applied when one or more criteria are met. Therefore, it is possible to implement example embodiments that selectively implement the disclosed protocols.

[0027] In this disclosure, “a” and “an”, and similar phrases, will be interpreted as “at least one” and “one or more”. Similarly, any term ending with the suffix “(s)” will be interpreted as “at least one” and “one or more”. In this disclosure, the term “may” is 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 variety of suitable possibilities that may or may not be used in one or more of the various embodiments. As used herein, the terms “comprising” and “consisting of” enumerate one or more components of the element being described. The terms “comprising” and “including” are interchangeable and do not exclude the inclusion of unlisted components in the element being described. In contrast, “consisting of” provides a complete enumeration of one or more components of the element being described. As used herein, the term “based on” can be interpreted as “at least partially based on” rather than, for example, “based on only.” As used herein, the term “and / or” indicates any possible combination of the enumerated elements. For example, "A, B and / or C" can mean A; B; C; A and B; A and C; B and C; or A, B and C.

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

[0029] The term "configured" can refer to the capabilities of a device, whether the device is in an operational or non-operational state. "Configured" can refer to specific settings within the 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 to provide specific characteristics to the device, whether the device is in an operational or non-operational state. Similarly, the term "control messages generated in the device" can mean that the control messages have parameters that can be used to configure specific characteristics in the device or to perform certain actions in the device, regardless of whether the device is in an operational or non-operational state.

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

[0031] By using the word "may" or parentheses, many of the presented features are described as optional. For brevity and readability, this disclosure does not explicitly describe every permutation that can be obtained by selecting from the group 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 different 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.

[0032] Many elements described in the disclosed embodiments can be implemented as modules. A module is defined herein as an element that performs the defined function and has the defined interface to other elements. Modules described in this disclosure can be implemented as hardware, software combined with hardware, firmware, wet hardware (e.g., hardware with biological elements), or combinations thereof, all of which may be behaviorally equivalent. For example, a module can be implemented as a software routine written in a computer language configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, Matlab, etc.) or a modeling / simulation program (such as Simulink, Stateflow, GNU Octave, or LabVIEW MathScript). It is possible to implement modules using physical hardware incorporating 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 aforementioned techniques are often used in combination to achieve the desired result of functional modules.

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

[0034] like Figure 1 As shown, an example wireless communication network may include an IEEE 802.11 (WLAN) infrastructure network 102. WLAN infrastructure network 102 may include one or more Basic Service Sets (BSS) 110 and 120 and a Distribution System (DS) 130.

[0035] 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 association procedures to communicate with each other.

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

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

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

[0039] 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 an IBSS are managed in a distributed manner. STAs forming an IBSS can be fixed or mobile.

[0040] A STA, serving as a predefined functional medium, may include a Media Access Control (MAC) layer conforming to the IEEE 802.11 standard. The physical layer interface of the radio medium can be used in both AP and non-AP stations (STAs). STAs may also be referred to using various other terms, including mobile terminal, radio device, radio transmit / receive 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.

[0041] Physical Layer (PHY) Protocol Data Units (PPDUs) can be composite structures, comprising a PHY preamble and a payload in the form of a PHY Service Data Unit (PSDU). For example, a PSDU may include a PHY preamble and a header and / or one or more MAC Protocol Data Units (MPDUs). The information provided in the PHY preamble can be used by the receiving device to decode subsequent data in the PSDU. When the PPDU is transmitted over a bonded channel (a channel formed by channel bonding), the preamble field can be copied and transmitted in each of the multiple component channels. The PHY preamble may include both a traditional portion (or "traditional preamble") and a non-traditional portion (or "non-traditional preamble"). The traditional preamble can be used for purposes such as packet detection, automatic gain control, and channel estimation. The traditional preamble is also typically used to maintain compatibility with legacy devices. 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.

[0042] 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 modifications can be transmitted in 2.4 GHz, 5 GHz, and / or 6 GHz bands, each band can be divided into multiple 20 MHz channels. PPDUs can be transmitted through physical channels with a minimum bandwidth of 20 MHz. Larger channels can be formed through channel bonding. For example, multiple 20 MHz channels can be bonded together to transmit PPDUs through physical channels with bandwidths of 40 MHz, 80 MHz, 160 MHz, or 320 MHz.

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

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

[0045] Memory 230 / 280 may include read-only memory (ROM), random access memory (RAM), flash memory, memory card, storage medium, and / or other storage units. Memory 230 / 280 may contain 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 of the operations / embodiments discussed in this application. Memory 230 / 280 may be implemented (or located) within processor 220 / 270 or external to processor 220 / 270. Memory 230 / 280 may be operatively connected to processor 220 / 270 in various ways known in the art.

[0046] Transceiver 240 / 290 can be configured to transmit / receive radio signals. In embodiments, transceiver 240 / 290 can implement the PHY layer of the 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. Therefore, STA 210 and / or AP 260 can each implement multiple PHY layers. One or more of transceivers 240 / 290 can be used to implement multiple PHY layers.

[0047] The Target Wake-Up Time (TWT) 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. TWTs can reduce the amount of time a STA utilizing power management modes might require to wake up. TWTs can be standalone or broadcast. Standalone TWTs follow a negotiated TWT protocol between STAs. Broadcast TWTs are based on schedule settings and are provided to STAs by the AP.

[0048] In a standalone TWT, the STA that requests the TWT protocol 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 the frame and exchange the frame with the TWT responding STA. The TWT requesting STA can transmit wake-up scheduling information to the TWT responding STA. When a TWT protocol is established between the two, the TWT responding STA can transmit the TWT value to the TWT requesting STA.

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

[0050] The TWT value of an implicit TWT can be periodic. A TWT request STA operating according to the implicit TWT protocol can determine the start time of the next TWT service cycle (TWT SP) by adding the value of the TWT wake-up interval associated with the TWT protocol to the start time of the current TWT SP. A TWT response STA can include a series of start times 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 setup command field. The start time of the TWT SP series can indicate the start time of the first TWT SP in the series. The start time of subsequent TWT SPs can be determined by adding the value of the TWT wake-up interval to the start time of the current TWT SP. In the example, a TWT request STA waking up for an implicit TWT SP can enter a dormant state after a TWT SP has passed or after receiving a service cycle end (EOSP) field equal to 1 from a TWT response STA (whichever occurs first).

[0051] A TWT session can be negotiated between the AP and STA. The TWT session can configure TWT SPs for DL ​​and UL traffic between the AP and STA. Expected traffic may be limited by the negotiated SP. A TWT SP can start at a specific time. A TWT SP can run for a specific duration. A TWT SP can repeat for each SP time interval.

[0052] Figure 3 Example 300 of the TWT operation is shown. Figure 3 As shown, Example 300 includes AP 311, STA 312, and STA 313. AP 311 and STA 312 can build TWT SP 320. AP 311 and STA 313 can build TWT SP 321. TWT SP 320 and TWT SP 321 can be used as follows: Figure 3 The repetition shown is such that TWT SP 320 may include a first TWT SP 320-1 and a second TWT SP 320-2, and TWT SP 321 may include a first TWT SP 321-1 and a second TWT SP 321-2.

[0053] AP 311 and STA 312 may exchange frames during the first TWT SP 320-1. STA 312 may enter a sleep state at the end of TWT SP 320-1 and may remain in a sleep state until the start of the second TWT SP 320-2. The start of the second TWT SP 320-2 may be indicated by the TWT wake-up interval 330 associated with TWT SP 320. AP 311 and STA 312 may exchange frames again during the second TWT SP 320-2.

[0054] Similarly, AP 311 and STA 313 may exchange frames during the first TWT SP 321-1. STA 313 may enter a sleep state at the end of the first TWT SP 321-1 and may remain in a sleep state until the start of the second TWT SP 321-2. The start of the second TWT SP 321-2 may be indicated by the TWT wake-up interval 331 associated with TWT SP 321. AP 311 and STA 313 may exchange frames again during the second TWT SP 31-2.

[0055] In wake-up mode, the STA can be fully powered. The STA can transmit and / or receive frames to / from the AP or another STA. In sleep mode, the STA may not transmit / receive frames to / from the AP or another STA.

[0056] An MLD is an entity capable of managing communication over multiple links. An MLD can be a logical entity and can have more than one affiliated station (STA). An MLD can have a single MAC Service Access Point (MAC-SAP) that provides MAC data services to the LLC layer. When the STA attached to the MLD is an AP STA (or AP), the MLD can be an Access Point MLD (AP MLD). When the STA attached to the MLD is a non-AP STA (or STA), the MLD can be a Non-Access Point MLD (Non-AP MLD) or a STA MLD.

[0057] During TWT protocol negotiation, a TWT requesting STA attached to the STA MLD and a TWT response STA attached to the AP MLD can transmit multiple TWT elements. A TWT element can contain a link ID bitmap subfield indicating different links in the TWT establishment frame. TWT parameters provided by the TWT element can be applied to the corresponding link indicated in the TWT element.

[0058] Figure 4 Example 400 of TWT operation is shown in a multi-link environment including an AP multi-link device (AP MLD) 410 and a STA multi-link device (STA MLD) 420. Figure 4 As shown, AP MLD 410 can have three auxiliary APs: AP 411, AP2 412, and AP3 413. In the example, AP 411, AP2 412, and AP3 413 can operate on the 2.4 GHz band, 5 GHz band, and 6 GHz band, respectively. STA MLD 420 can have three auxiliary STAs: STA 421, STA 422, and STA 423. In the example, STA 421, STA 422, and STA 423 can operate on the 2.4 GHz band, 5 GHz band, and 6 GHz band, respectively. In the example, AP 411, AP2 412, and AP3 413 can be communicatively coupled to STA 421, STA 422, and STA 423 via a first link (link 1), a second link (link 2), and a third link (link 3), respectively.

[0059] In the example, STA 421 can transmit a TWT request to AP 411. The TWT request can include three TWT elements. Each TWT element can indicate the corresponding link of links 1-3 and can request the establishment of a TWT agreement for the indicated link. These three TWT elements can have different TWT parameters, such as the Target Wake-up Time (TWT). In response to the TWT request, AP 411 can transmit a TWT response to STA 421. The TWT response can include three TWT elements. Each TWT element can indicate the corresponding link of links 1-3 and can include a 'Accept TWT' value in the TWT Establishment Command field.

[0060] Successful TWT agreement establishment on links 1-3 establishes three TWT SPs with the same or different TWT parameters on links 1-3 respectively. The target wake-up time field of the TWT element for a given link indicates the start time of the TWT SP for that link. The start time can be indicated by referring to the link's Time Synchronization Function (TSF) time.

[0061] In Example 400, the initial TWT SPs 430-1, 430-2, and 430-3 of Link 1-3 can be aligned separately. The TWT wake-up intervals associated with the TWT protocol of Link 1-3 can be set differently. Therefore, the second TWT SPs 431-1, 431-2, and 431-3 of Link 1-3 can be misaligned. STAs 421, STA 422, and STA 423 can enter a sleep state between the end of the initial TWT SPs 430-1, 430-2, and 430-3 and the beginning of the second TWT SPs 431-1, 431-2, and 431-3, respectively.

[0062] Figure 5 An example Target Wake Time (TWT) element 500 is shown that can be used to support individual TWT operations.

[0063] In the example, the AP and STA can use TWT element 500 to negotiate the TWT protocol. The AP and / or STA can transmit TWT element 500 in a separately addressed management frame. For example, the management frame can take the following types: action, unacknowledged action, (re)association request / response, and probe request response.

[0064] TWT schedules and parameters can be provided during the TWT setup phase. Renegotiation / changes to the TWT schedule can be signaled via separately addressed frames containing the updated TWT schedule / parameters. These frames can be management frames as described above, or control or data frames carrying fields containing the updated TWT schedule / parameters.

[0065] refer to Figure 5The TWT element 500 includes an element ID field, a length field, a control field, and a TWT parameter information field.

[0066] The element ID field (e.g., 1 octet in length) can indicate that information element 500 is a TWT element. The length field (e.g., 1 octet in length) can indicate the length of TWT element 500 from the start of the control field to the end of TWT element 500. The end of TWT element 500 can be the end of the TWT channel field or the end of the link ID bitmap field of the TWT parameter information field.

[0067] TWT parameter information fields may include a request type field (e.g., 2 octets), a target wake-up time field (e.g., 8 octets or less), a TWT group assignment field (e.g., 9, 3, 2, or 0 octets), a nominal minimum TWT wake-up duration field (e.g., 1 octet), a TWT wake-up interval mantissa (e.g., 2 octets), a TWT channel field (e.g., 1 octet), an optional NDP paging field (e.g., 0 or 4 octets), and / or a link ID bitmap field (e.g., 0 or 2 octets).

[0068] The request type field can indicate the type of TWT request. The request type field may include a TWT request field (e.g., 1 bit), a TWT setup command field (e.g., 3 bits), a trigger field (e.g., 1 bit), an implicit field (e.g., 1 bit), a stream type (e.g., 1 bit), a TWT stream identifier (e.g., 3 bits), a TWT wake-up interval index (e.g., 5 bits), and / or a TWT protection field (e.g., 1 bit).

[0069] The TWT Request field indicates whether TWT element 500 represents a request. If the value of the TWT Request field is 1, then TWT element 500 can represent a request to initiate TWT scheduling / establishment.

[0070] The TWT creation command field can indicate the type of TWT command. In a TWT request, the type of TWT command indicated can be: Request TWT (TWT responds to STA specifying a TWT value; for example, the field is set to 0), Suggest TWT (TWT requests STA to suggest a TWT value; for example, the field is set to 1), and Request TWT (TWT requests STA to request a TWT value; for example, the field is set to 2).

[0071] In a TWT response, the type of TWT command indicated can be: TWT grouping (the TWT response STA suggests TWT grouping parameters that are different from those suggested or requested by the TWT request STA; for example, field set to 3), Accept TWT (the TWT response STA accepts a TWT request with TWT parameters indicated by the TWT request STA; for example, field set to 4), Alternative TWT (the TWT response STA suggests TWT parameters that are different from those suggested or requested by the TWT request STA; for example, field set to 5), Indicate TWT (the TWT response STA requests TWT parameters that are different from those suggested or requested by the TWT request STA; for example, field set to 6), or Reject TWT (the TWT response STA rejects TWT establishment; for example, field set to 7).

[0072] In a TWT response, the TWT command can also indicate a non-demand response or a broadcast TWT. A non-demand TWT response is a separate addressing frame intended for a specific STA. A non-demand TWT response can be followed by an ACK frame from the STA that received the non-demand TWT response. A broadcast TWT can be intended for multiple STAs and can be carried in a broadcast frame (e.g., a beacon frame). Broadcast TWTs cannot be acknowledged by the receiving STA.

[0073] A TWT Response STA can use a non-demand TWT response to request the receiver to comply with the TWT schedule contained in the TWT element. In an embodiment, a non-demand TWT response may have a TWT Request field set to 0 and a 'Instruct TWT' value in the TWT Setup Command field. A TWT Response STA can use a broadcast TWT response to schedule TWTs for any STA that receives and decodes TWT elements.

[0074] In some embodiments, a TWT element (such as TWT element 500) may contain a set of TWT parameters for multiple TWT negotiations or indications as described herein. Therefore, a TWT element may include multiple instances of control and TWT parameter information fields. The TWT flow identifier of the request type field indicates which parameters the TWT parameter information field carries for TWT negotiation.

[0075] Figure 6 An example TWT element 600 that can be used to support restricted target wake-up time (r-TWT) operation is shown. For r-TWT, TWT element 600 can be transmitted in a broadcast management frame, which can be a beacon frame, a TIM broadcast frame, a probe response frame, etc. In this embodiment, TWT element 600 provides a non-negotiated TWT schedule (e.g., a broadcast TWT schedule).

[0076] As shown in the figure, TWT element 600 includes an element ID field, a length field, a control field, and a TWT parameter information field.

[0077] The element ID field (e.g., 1 octet in length) can indicate that information element 600 is a TWT element. The length field (e.g., 1 octet in length) can indicate the length of TWT element 600 from the start of the control field to the end of TWT element 600. The end of TWT element 600 can be the end of the broadcast TWT information field or the end of the r-TWT flow information field of the TWT parameter information field.

[0078] The TWT parameter information fields may include a request type field, a target wake-up time field (e.g., 2 octets), a nominal minimum TWT wake-up duration field (e.g., 1 octet), a TWT wake-up time interval mantissa (e.g., 2 octets), a broadcast TWT information field (e.g., 2 octets), and an optional r-TWT flow information field (e.g., 0 or 3 octets).

[0079] The request type field may include the TWT request field, the stream type field, the TWT wake-up interval index field, and other fields.

[0080] The TWT Request field indicates whether TWT element 600 is a request. If the value of the TWT Request field is 0, then TWT element 600 can represent a response to a request used to initiate TWT scheduling / establishment (requesting TWT), non-requesting TWT responses, and / or broadcast TWT messages.

[0081] The TWT wake-up interval represents the average time expected to elapse between consecutive TWT SP start times in the TWT schedule for a TWT requesting STA or a TWT scheduled STA. The TWT wake-up interval exponent field indicates the (base-2) exponent used to calculate the TWT wake-up interval in microseconds. In this embodiment, the TWT wake-up interval is equal to: (TWT wake-up interval mantissa) × 2(TWT wake-up interval exponent). The TWT wake-up interval mantissa, expressed in microseconds, is represented by a base-2 in the TWT wake-up interval mantissa field of the TWT parameter information field.

[0082] The nominal minimum TWT wake-up duration field can indicate the minimum amount of time (in the cell indicated by the wake-up duration cell subfield of the control field) that a TWT requesting STA or a TWT scheduled STA expects to wake up within the TWT wake-up interval to complete frame exchange.

[0083] In a TWT response that successfully establishes a TWT agreement between the TWT requesting STA and the TWT responding STA, the Stream Type field indicates the type of interaction between the TWT requesting STA and the TWT responding STA within the TWT SP of the TWT agreement. A Stream Type field equal to 0 indicates a declared TWT. In a declared TWT, the TWT responding STA may not transmit frames to the TWT requesting STA within the TWT SP until it receives a PS polling frame or a QoS empty frame from the TWT requesting STA. A Stream Type field equal to 1 indicates an undeclared TWT. In an undeclared TWT, the TWT responding STA may transmit frames to the TWT requesting STA within the TWT SP before receiving frames from the TWT requesting STA.

[0084] Within a TWT element containing a TWT setup command value of 'Request TWT', 'Suggest TWT', or 'Demand TWT', the Broadcast TWT ID can indicate the specific broadcast TWT that the TWT requesting STA has requested to participate in. Within a TWT element containing a TWT setup command value of 'Accept TWT', 'Alternative TWT', 'Indicate TWT', or 'Reject TWT', the Broadcast TWT ID can indicate the specific broadcast TWT that the TWT responds to by providing TWT parameters to the STA. A value of 0 in the Broadcast TWT ID subfield can indicate a broadcast TWT whose members correspond to all STAs that are members of the BSS corresponding to the BSSID of the management frame carrying the TWT element, and is allowed to contain trigger frames with random access resource elements for unassociated STAs. The Broadcast TWT ID subfield in the r-TWT parameter set field is always set to a non-zero value.

[0085] The broadcast TWT element 600 containing the r-TWT parameter set is also referred to as the r-TWT element. The r-TWT traffic information presence subfield of the broadcast TWT information field can be set to 1 to indicate the presence of the r-TWT traffic information field in TWT element 600. When the r-TWT traffic information presence subfield is set to 1, the r-TWT traffic information field exists in the r-TWT parameter set field.

[0086] The r-TWT traffic information field may include a traffic information control field, an r-TWT DL TID bitmap field, and an r-TWT UL TID bitmap field.

[0087] The flow information control fields may include a DL TID bitmap valid subfield and a UL TID bitmap valid subfield. The DL TID bitmap valid subfield indicates whether the r-TWT DL TID bitmap field has valid information. When the value of the DL TID bitmap valid subfield is set to 0, it indicates that the DL flow of the TID is identified as delay-sensitive flow, and the r-TWT DL TID bitmap field is retained. The UL TID bitmap valid subfield indicates whether the r-TWT UL TID bitmap field has valid information. When the value of the UL TID bitmap valid subfield is set to 0, it indicates that the UL flow of the TID is identified as delay-sensitive flow, and the r-TWT UL TID bitmap field is retained.

[0088] The r-TWT DL TID bitmap subfield and the r-TWT UL TID bitmap subfield can respectively specify which TIDs the TWT scheduling AP or TWT scheduling STA will identify as delay-sensitive traffic flows in the downlink and uplink directions. A value of 1 at bit position k in the bitmap indicates that TID k is classified as a delay-sensitive traffic flow. A value of 0 at bit position k in the bitmap indicates that TID k is not classified as a delay-sensitive traffic flow.

[0089] A single target wake-up time (TWT) can be a specific time or set of times negotiated between two separate stations (e.g., STA and another STA, or STA and AP, etc.), during which the stations can wake up to exchange frames during the service period (SP) of the TWT.

[0090] In a trigger-enabled TWT, the AP can use uplink OFDMA (Orthogonal Frequency Division Multiple Access) and / or uplink MU-MIMO (Multi-User Multiple-Input Multiple-Output) during the trigger-enabled TWT SP to transmit a trigger frame for scheduling uplink multi-user transmissions from one or more STAs. A TWT STA receiving the trigger frame from the AP can transmit the frame back to the AP via the resources indicated in the trigger frame during the trigger-enabled TWT SP.

[0091] In non-triggered TWT enabled, the AP may not need to transmit a trigger frame to schedule uplink multi-user transmissions from one or more STAs during non-triggered TWT enabled SP.

[0092] In a declared TWT, the STA can transmit frames (e.g., PS polling frames or QoS empty frames) to the AP to retrieve downlink buffered data from the AP during the TWT SP. In an undeclared TWT, the AP can transmit downlink data to the TWT STA without receiving frames (e.g., PS polling frames or QoS empty frames) from the TWT STA during the TWT SP.

[0093] Figure 7 Example 700 of a standalone TWT operation is shown. (e.g.) Figure 7 As shown, Example 700 includes AP 710, STA 711, and STA 712. In the example, AP 710 can be a TWT response STA, and STA 711 and STA 712 can be TWT request STAs.

[0094] In the example, STA 711 can transmit a TWT request to AP 710 to establish a first trigger-enabled TWT agreement. STA 711 can set the trigger field of the TWT request to 1 to indicate that it is requesting trigger-enabled TWT. AP 710 can accept the first TWT agreement with STA 711. AP 710 can acknowledge acceptance in a TWT response sent to STA 711. The TWT response can indicate the next TWT 730, which indicates the time until the next TWT SP 720 according to the first TWT agreement.

[0095] In the example, AP 710 can transmit a non-demand TWT response to STA 712 to establish a second trigger-enabled TWT agreement with STA 712 without receiving a TWT request from STA 712. The first and second TWT agreements can be established as declared TWTs.

[0096] After the TWT agreement is established, STA 711 and STA 712 can enter a sleep state until TWT SP 720 begins. During the TWT SP 720 activation period, AP 710 can transmit a trigger frame. STA 711 and STA 712 can respond to the trigger frame by indicating that they are in a wake-up state. In the example, STA 711 can transmit a Power Saving Polling (PS Polling) frame. The PS Polling frame may contain a BSSID (Receiver Address: RA) field set to the address of AP 710 and a Transmitter Address (TA) field set to the address of STA 711. In the example, STA 712 can respond to the trigger frame by transmitting a QoS empty frame. The QoS empty frame may contain a MAC header without a frame body (e.g., frame control field, duration field, address field, sequence control field, QoS control field).

[0097] In response to PS-Poll frames and QoS empty frames, AP 710 can transmit Multi-STA Block Acknowledgment (M-BA) frames. The M-BA frame may include acknowledgment information associated with the PS-Poll frame and QoS empty frame received from STA 711 and 712, respectively. Subsequently, STA 711 and STA 712 can receive Downlink Bufferable Units (DL BUs) from AP 710. DL BUs may include Media Access Control (MAC) Service Data Units (MSDUs), Aggregated MAC Service Data Units (A-MSDUs), and / or Bufferable MAC Management Protocol Data Units (MMPDUs). STA 711 and STA 712 may transmit Block Acknowledgment (BA) frames in response to the DL BUs. At the end of TWT SP 720, STA 711 and STA 712 may return to sleep mode.

[0098] The STA can perform a standalone TWT establishment switch. The STA may not transmit frames to APs outside the negotiated TWT SP. The STA may not transmit frames to APs within the trigger-enabled TWT SP that are not included in the High Efficiency Trigger-Based Physical Protocol Data Unit (HE TB PPDU). The HE TB PPDU can be transmitted by the STA based on a trigger frame that triggers uplink multi-user transmission.

[0099] An AP that triggers the TWT protocol can schedule trigger frames for transmitting STAs within the trigger-enabled TWT SP. STAs can transmit HE TB PPDUs in response to trigger frames sent during the trigger-enabled TWT SP. If the TWT is a declared TWT, STAs in power-saving (PS) mode can include PS polling frames or QoS empty frames in the HE TB PPDU to indicate to the AP that the STA is currently awake. An AP receiving PS polling frames, QoS empty frames, or any other indications from a STA in PS mode can deliver as many buffer BUs as are available at the AP to the STA during the TWT SP.

[0100] The Broadcast Target Wake-up Time (TWT) can be a specific time or set of times broadcast by the AP to one or more STAs, at which the STA can wake up during the SP period of the TWT to exchange frames with the AP.

[0101] Figure 8 Example 800 of broadcast TWT operation is shown. Figure 8 As shown, Example 800 includes AP 810, STA 811, and STA 812. In Example 800, AP 810 can be a TWT-scheduled AP, and STA 811 and STA 812 can be TWT-scheduled STAs.

[0102] In the example, AP 810 may include a broadcast TWT element in the beacon frame indicating broadcast TWT SP 820. During broadcast TWT SP 820, AP 810 may transmit a trigger frame or DL ​​BU to STA 811 and STA 812. Beacon frames may be periodically transmitted by AP810 at the Target Beacon Transmission Time (TBTT). The number of time units (TU) between consecutive TBTTs is called the beacon interval. TU is equal to 1024 microseconds.

[0103] In the example, STA 811 and STA 812 can enter a sleep state until the First Target Beacon Transmission Time (TBTT). STA 811 and STA 812 can wake up to receive a beacon frame at the first TBTT, thereby determining the broadcast TWT. After receiving the broadcast TWT element in the beacon frame, STA 811 and STA 812 can re-enter a sleep state until the trigger enables TWT SP 820 to begin.

[0104] During the activation of TWT SP 820 by the trigger, AP 810 can transmit a basic trigger frame to STA 811 and STA 812. STA 811 can indicate that it is awake by transmitting a PS polling signal, and STA 812 can indicate that it is awake by transmitting a QoS empty frame in response to the basic trigger frame. Subsequently, STA 811 and STA 812 can receive DL BU from AP 810. STA 811 and STA 812 can then return to a sleep state outside of TWT SP 720.

[0105] In the example, a STA designed to operate in power-saving mode can negotiate a wake-up TBTT and wake-up interval with the AP. For example, as... Figure 8 As shown, STA 811 can transmit a TWT request to AP 810, which identifies the wake-up interval between the first beacon frame's wake-up TBTT and subsequent beacon frames. AP 810 can respond to the TWT request acknowledging the wake-up TBTT and wake-up interval with a TWT response. After successful negotiation, STA 811 can enter a sleep state until the first negotiation wake-up TBTT 830. STA 811 can be awake to listen for beacon frames transmitted during the first negotiation wake-up TBTT 830. If STA 811 receives a beacon frame from AP 810 at or after TBTT 830, STA 811 can return to a sleep state until the next wake-up TBTT unless the Flow Indication Map (TIM) element in the beacon frame includes a positive indication for STA 811. STA 811 can return to a sleep state after the nominal minimum TBTT wake-up duration has elapsed since the TBTT start time.

[0106] The Network Allocation Vector (NAV) is an indicator of a time period maintained by a Station (STA) during which the STA cannot initiate transmissions on the Radio Medium (WM) regardless of whether its Free Channel Assessment (CCA) function senses that the WM is busy. A STA that has received at least one valid frame in a PSDU can update its NAV using information from any valid duration field in the PSDU. The STA can update its NAV when the received duration field value is greater than its current NAV value.

[0107] TWT protection is a mechanism used to protect a TWT session from transmissions by external STAs. During a TWT SP configured to protect the TWT session, the STA that initiates the Transmission Opportunity (TXOP) for transmitting frames can protect the TWT session by setting the NAV of other STAs based on received RTS and / or CTS frames to transmit Request to Transmit (RTS) or Clear to Transmit (CTS) frames. An RTS frame may contain a Frame Control field, a Duration field, a Receiver Address (RA) field, a Transmitter Address (TA) field, and a Frame Check Sequence (FCS) field. A CTS frame may contain a Frame Control field, a Duration field, a Receiver Address (RA) field, and a Frame Check Sequence (FCS) field.

[0108] The TWT Protection field in a TWT element indicates whether a TWT is protected or unprotected. A TWT Request STA can set the TWT Protection field to 1 to request a TWT Response STA to provide protection for the TWT SP set. A TWT Protection field equal to 1 indicates that NAV protection mechanisms should be used to protect access to the media during the corresponding TWT SP.

[0109] Figure 9 Example 900 of TWT protection in a standalone TWT operation is shown. (e.g.) Figure 9 As shown, Example 900 includes AP 910 and STA 911.

[0110] In the example, AP 910 can set the TWT protection field to 1 in the TWT response frame to protect the TWT SP using the NAV protection mechanism. After receiving the TWT response frame, STA 911 can enter a sleep state until the next TWT 930. AP 910 with the TWT protection field set to 1 can transmit an NAV setup frame at the start of TWT SP 920. For example, the NAV setup frame can be an RTS frame or a CTS frame.

[0111] A STA that receives an NV setup frame and is not scheduled to access the medium during TWT SP 920 can set its NAV according to the NAV setup frame. In the NAV setup frame, the STA may not access the medium for the specified amount of time.

[0112] STA 911 can be scheduled to access the medium during TWT SP 920. STA 911 can respond to RTS frames with CTS frames. Upon receiving a CTS frame, AP 910 can transmit downlink frames to STA 911. STA 911 can respond to downlink frames with BA frames. When TWT SP 920 ends, STA 911 can return to sleep mode.

[0113] Triggered TXOP Sharing (TXS) is a technique introduced in the IEEE 802.11be standard amendment. TXS allows an AP to allocate a duration within a acquired TXOP to a STA for transmitting one or more non-trigger-based (non-TB) PPDUs. For TXS procedures, the AP can transmit a Multi-User Request to Transmit (MU-RTS) trigger frame, where the Triggered TXOP Sharing Mode subfield is set to a non-zero value. The MU-RTS trigger frame is used to trigger CTS frames from multiple users. The MU-RTS trigger frame where the Triggered TXOP Sharing Mode subfield is set to a non-zero value is called an MU-RTS TXS Trigger (MRTT) frame.

[0114] In the example, when the Trigger TXOP Share Mode subfield is set to 1, the STA can transmit one or more non-TB PPDUs to the AP during the allocated duration. In the example, when the Trigger TXOP Share Mode subfield is set to 2, the STA can transmit one or more non-TB PPDUs to the AP or a peer STA during the allocated duration. A peer STA can be a STA with a connection for peer-to-peer (P2P) communication or direct communication with the STA. In the example, a direct wireless link is established according to the Channel Direct Link Establishment (TDLS) protocol.

[0115] Figure 10 This demonstrates an example MRTT frame 1000 that can be used in the TXS program. Figure 10 As shown, the example MRTT frame 1000 may contain 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.

[0116] In the 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 10As shown, the EHT variant public information field may contain one or more of the following subfields: trigger type, UL length, additional TF, required CS, UL BW, GI and HE / EHT-LTF type / trigger TXOP sharing mode, number of HE / EHT-LTF symbols, LDPC additional symbol fragments, AP Tx power, pre-FEC fill factor, PE ambiguity, UL space reuse, HE / EHT P160, special user information field flag, reserved EHT, reserved or trigger-related public information.

[0117] The trigger type subfield indicates that frame 1000 is an MRTT frame.

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

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

[0120] The AID12 subfield can indicate the associated identifier (AID) of an STA, which can use the time indicated by the Assigned Duration subfield.

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

[0122] The allocation duration subfield can indicate the time allocated by the AP transmitting MRTT frame 1000. The allocation time can be a portion of the TXOP obtained by the AP. In an example embodiment, the allocation duration subfield can indicate a first time period.

[0123] Figure 11 Example 1100 demonstrates a TXS program (mode = 1). (e.g.) Figure 11 As shown, the TXS procedure can begin with the transmission of MRTT frame 1120 from AP 1110 to STA 1111. MRTT frame 1120 can allocate a portion of the TXOP obtained by AP 1110 to STA 1111 and can indicate a TXS mode equal to 1. STA 1111, receiving MRTT frame 1120, can use the allocated time to transmit one or more non-TB PPDUs to AP 1110. The one or more non-TB PPDUs can contain data frames, control frames, management frames, or action frames.

[0124] In the example, MRTT frame 1120 may include a Trigger TXOP Shared Mode subfield, which indicates a TXS mode and / or subfield, which indicates a first time period corresponding to the allocated time. In the example, the first time period may be set to a value of X microseconds (µs).

[0125] STA 1111 can respond to MRTT frame 1120 by transmitting CTS frame 1121 to AP 1110. Subsequently, STA 1111 can transmit non-TB PPDUs 1122, 1124 containing one or more data frames to AP 1110 during the first time period indicated in MRTT frame 1120. In the example, AP 1110 can transmit one or more BA frames 1123, 1125 in response to one or more data frames contained in the non-TB PPDUs 1122, 1124 received from STA 1111.

[0126] Figure 12 Example 1200 demonstrates a TXS program (mode = 2). (e.g.) Figure 12 As shown, the TXS procedure can begin with the transmission of MRTT frame 1220 from AP 1210 to STA 1211. MRTT frame 1220 can allocate a portion of the TXOP obtained by AP 1210 to STA 1211 and can indicate a TXS mode equal to 2. STA 1211, receiving MRTT frame 1220, can use the allocated time to transmit one or more non-TB PPDUs to STA 1212. The one or more non-TB PPDUs can contain data frames, control frames, management frames, or action frames.

[0127] In the example, MRTT frame 1220 may include a Trigger TXOP Shared Mode subfield, which indicates a TXS mode and / or subfield, which indicates a first time period corresponding to the allocated time. In the example, the first time period may be set to a value of X microseconds (µs).

[0128] STA 1211 can respond to MRTT frame 1220 by transmitting CTS frame 1221 to AP 1210. Subsequently, STA 1211 can transmit non-TB PPDUs 1222, 1224 containing one or more data frames to STA 1212 during the first time period indicated in MRTT frame 1220. In the example, STA 1212 can transmit one or more BA frames 1223, 1225 in response to one or more data frames contained in the non-TB PPDUs 1222, 1224 received from STA 1211.

[0129] Figure 13 Example 1300 illustrates a sample TXS procedure between multiple linked devices (MLDs). Figure 13 As shown, Example 1300 includes AP MLD 1302 and non-AP MLD 1304. AP 1302-1 and AP 1302-2 can be attached to AP MLD 1302. STA 1304-1 and STA 1304-2 can be attached to non-AP MLD 1304. STA 1304-1 can be associated with AP 1302-1. AP 1302-1 and STA 1304-1 can communicate via a first link (Link 1). STA 1304-2 can be associated with AP 1302-2. AP 1302-2 and STA 1304-2 can communicate via a second link (Link 2).

[0130] In the example, AP 1302-1 can transmit MU-RTS TXS Triggered (MRTT) frame 1306 to STA 1304-1 on link 1. MRTT frame 1306 may contain a TXOP shared mode subfield set to 1, an AID12 subfield set to the AID of STA 1304-1, and / or a first time period (e.g., X us, where X is an integer value greater than 0).

[0131] In the example, STA 1304-1 can transmit CTS frame 1308 in response to MRTT frame 1306 on link 1. Subsequently, STA 1304-1 can transmit data frame 1310 to AP 1302-1 on link 1 during a first time period (e.g., in a non-TBPPDU). AP 1302-1 can transmit BA frame 1313 on link 1 in response to data frame 1310 during the first time period.

[0132] In the example, AP 1302-2 can transmit MRTT frame 1314 to STA 1304-2 on link 2. MRTT frame 1314 may contain a TXOP shared mode subfield set to 1, an AID12 subfield set to the AID of STA 1304-2, and / or a first time period (e.g., Y us, where Y is an integer value greater than 0).

[0133] In the example, STA 1304-2 may transmit CTS frame 1316 in response to MRTT frame 1314 on link 2. Subsequently, STA 1304-2 may transmit data frame 1318 to AP 1302-2 on link 2 during a first time period (e.g., in a non-TBPPDU). AP 1302-2 may transmit BA frame 1320 on link 2 in response to data frame 1318 during a first time period (e.g., Y us).

[0134] Figure 14 Example 1400 illustrates an inefficient STA operation that may occur during a TXS procedure. (e.g.) Figure 14 As shown, Example 1400 includes AP 1402 and STAs 1404, 1406 and 1408. STA 1404 may be associated with AP 1402.

[0135] In the example, AP 1402 can allocate a portion of its acquired TXOP to STA 1404 by transmitting MRTT frame 1410. STA 1404 can then transmit CTS frame 1412 to AP 1402 in response to MRTT frame 1410.

[0136] MRTT frame 1410 may include a TXOP shared mode subfield, an AID12 subfield set to STA 1404, and / or a first time period (e.g., X us).

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

[0138] In the example, the TXOP sharing mode subfield is set to 2. A TXOP sharing mode subfield set to 2 indicates that STA 1404 may transmit one or more non-TB PPDUs to AP 1402 or to a peer STA during a first time period. In the example, the peer STA may be a STA with a connection for P2P communication or direct communication with STA 1404. In the example, the peer STA may be STA 1406. One or more non-TB PPDUs may contain data frames, control frames, management frames, or action frames. In example 1400, STA 1404 may transmit data frame 1414 to STA 1406 during the first time period. STA 1406 may transmit BA frame 1416 to STA 1404 in response to data frame 1414. STA 1404 may then transmit data frame 1418 to STA 1406. STA 1406 may respond to data frame 1418 with BA frame 1420.

[0139] After receiving MRTT frame 1410, STA 1408 may be in a wake-up state during the first time period (X) indicated in MRTT frame 1410. However, during this first time period, AP 1402 may not communicate with STA 1408 because STA 1408 was not assigned power by MRTT frame 1410. Therefore, the wake-up power state of STA 1408 may lead to unnecessary power waste at STA 1408.

[0140] Figure 15 Example 1500 demonstrates a sample TXS PS (PS) pattern that can be used to solve this problem. Figure 15 As shown, Example 1500 includes AP 1502 and STAs 1504, 1506 and 1508. One or more STAs 1504, 1506 and 1508 may be associated with AP 1502.

[0141] like Figure 15As shown, Example 1500 can begin with AP 1502 transmitting the first frame 1510 to allocate a portion of the acquired TXOP to STA 1504. Frame 1510 may contain a TXOP sharing mode subfield, an AID 12 subfield, and a first time period (e.g., X us). The TXOP sharing mode subfield can indicate the triggering of the TXOP sharing procedure. For example, the TXOP sharing mode subfield can be set to a non-zero value (e.g., 1, 2, ...) indicating whether TXOP sharing mode 1 or TXOP sharing mode 2 is triggered. The AID 12 subfield can be set to the AID of the STA that can use the first time period to transmit and receive one or more frames. For example, the AID 12 subfield can be set to the AID of STA 1504. The first time period can be specified in microseconds or other time units. In the example, frame 1510 may be an MRTT frame.

[0142] Upon receiving frame 1510, STA 1504 may transmit a second frame 1512 to AP 1502. In this example, frame 1512 may be a CTS frame. STA 1504 may then transmit one or more non-TB PPDUs containing one or more data frames 1514 and 1518 to STA 1506 during a first time period. STA 1506 may transmit one or more BA frames 1516 and 1520 to STA 1504 in response to data frames 1514 and 1518, respectively.

[0143] In the implementation scheme, based on receiving frame 1510 during the first time period during which no STA 1508 is assigned, STA 1508 can transition to a sleep state. In an example embodiment, STA 1508 can transition to a sleep state under the following circumstances: - After STA 1508 receives frame 1510 and before STA 1508 receives frame 1512 in response to frame 1510; - After STA 1508 receives frame 1512 in response to frame 1510; or - In the case where no third frame is received during the second time period after STA 1508 receives frame 1510.

[0144] 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 via a fourth frame sent by AP 1502. The fourth frame can be a beacon frame, probe response frame, or association response frame.

[0145] In one implementation, STA 1508 may remain in a dormant state for a portion of a first time period after STA 1508 transitions to a dormant state. Alternatively, STA 1508 may be in an awake state at the end of the first time period or at least from the end of the first time period.

[0146] In the implementation scheme, AP 1502 may not transmit the third frame 1522 to STA 1508 during the first time period. AP 1502 may transmit the third frame 1522 to STA 1508 after the first time period.

[0147] In the implementation, AP 1502 and STA 1508 may exchange indications of support for the TXS PS mode before the start of Example 1500. For example, STA 1508 may include an indication of TXS PS mode support in an association request frame to AP 1502. STA 1508 may set the TXS PS mode field (or TXS PS support field) to 1 in the association request frame to indicate support for the TXS PS mode. The TXS PS mode field (or TXS PS support field) may be provided in the EHTMAC capability information field of the association request frame. AP 1502 may include an indication of TXS PS mode support in an association response frame to STA 1508. STA 1508 may set the TXS PS mode field (or TXS PS support field) to 1 in the association response frame to indicate support for the TXS PS mode. The TXS PS mode field (or TXS PS support field) may be provided in the EHTMAC capability information field of the association response frame.

[0148] In the implementation, when STA 1508 indicates support for the TXS PS mode (e.g., the TXS PS field is set to 1 in an association request frame to AP 1502), AP 1502 can avoid transmitting to STA 1508 during the first time period (when STA 1508 is not assigned a time slot), because STA 1508 can enter a sleep state during the first time period (even if STA 1508 is not actually in a sleep state during the first time period). AP 1502 can continue to use this behavior for STA 1508 during any subsequent TXS time periods when STA 1508 is not assigned a time slot. That is, based on the fact that STA 1508 has indicated support for the TXS PS mode, AP 1502 may not transmit to STA 1508 during the TXS time periods when STA 1508 is not assigned a time slot.

[0149] However, a recent amendment to the 802.11be standard has proposed that after a STA has completed transmitting its buffered traffic, the STA can return any remaining time of the time slot allocated to it (in TXS mode 2) to the AP. The AP can use the remaining time of the time slot to transmit downlink traffic, or it can allocate a portion of the remaining time to another STA. For example, see reference... Figure 15 Assuming STA 1504 has no more traffic to transmit after transmitting data frame 1518, STA 1504 can return the remaining time of the first time segment after receiving BA frame 1520 from STA 1506. AP 1502 can use the remaining time of the first time segment to transmit downlink traffic (e.g., to STA 1506 or 1508), or it can allocate a portion of the remaining time (e.g., to STA 1506 or 1508). According to the IEEE 802.11be standard amendment, APs supporting this "TXOP return" function can transmit 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 mode 2, the frames including an HE variant HT control field with a CAS control subfield, where the RDG / More PPDU subfield is equal to 0. The AP can transmit PPDUs in SIFS after receiving a frame with the CAS control subfield. Conversely, a STA receiving an MRTT frame in which the TXOP shared mode subfield is equal to 2 can transmit QoS data or QoS empty frames to the associated AP within the allocated time. The QoS data or QoS empty frames include an HE variant HT control field with a CAS control subfield, where the RDG / More PPDU subfield is equal to 0, and the STA has received an EHT capability element from the associated AP, where the "TXOP return support in TXOP shared mode 2" subfield is set to 1.

[0150] However, based on existing behavior, the AP may not use the remaining time of the returned time period to transmit to or allocate a portion of the remaining time to a STA that indicates support for TXS PS mode and is not allocated during that time period. In fact, as described above, when a STA indicates support for TXS PS mode and is not allocated during a time period, the AP may not transmit to the STA during that time period because the STA may enter a sleep state during that time period. For example, see reference... Figure 15Assuming STA1508 indicates support for TXS PS mode to AP 1502 (e.g., the TXS PS field is set to 1 in an association request frame to AP 1502), AP 1502 may not transmit to STA 1508 during the first time period (when STA 1508 is not allocated time), even if STA 1504 returns the remaining time of the first time period to AP 1502 after receiving BA frame 1520. Similarly, AP 1502 may not allocate a portion of the returned remaining time to STA 1508. This could happen even if STA 1508 does not enter a sleep state during the first time period.

[0151] This behavior can lead to inefficiency because the AP may be restricted in how it uses the remaining time of the TXS period. For example, the AP might have buffered downlink traffic for a STA that is not allocated during the TXS period and indicates support for TXS PS mode. Even though the STA might be awake during the TXS period, the AP must wait until the TXS period ends before transmitting the buffered downlink traffic to the STA. In another example, the AP might want to share a portion of the remaining time of the TXS period with the STA. However, because the AP may not transmit to the STA during the TXS period, the AP may not send a time allocation to the STA, even if the STA might be awake during the TXS period.

[0152] As further described below, embodiments of this disclosure address the aforementioned problems. On one hand, a STA supporting TXS PS mode can transmit a frame to the AP instructing the AP to enable or disable TXS PS mode at the STA. Based on the frame instructing the AP to enable TXS PS mode at the STA, the AP can avoid transmitting to the first STA during a TXOP period in which the STA is not allocated. Based on the frame instructing the AP to enable TXS PS mode at the STA, the AP can transmit to the first STA after the TXOP period ends. Based on the frame instructing the AP to enable TXS PS mode at the STA, the STA can switch its power state to sleep mode during the TXOP period. The AP can transmit to the first STA during the TXOP period if a frame instructs the AP to disable TXS PS mode at the STA. Based on the frame instructing the AP to disable TXS PS mode at the STA, the STA can remain in wake-up mode or operate in wake-up mode during the TXOP period.

[0153] In the first embodiment, the frame indicating whether to enable or disable the TXS PS mode at the STA can be an association request frame or a reassociation request frame. Figure 16 Example 1600 illustrates such an embodiment. Figure 16As shown, Example 1600 includes AP1602 and STAs 1604, 1606, and 1608. One or more of STAs 1604, 1606, and 1608 may be associated with AP 1602. STAs 1604, 1606, and / or 1608 may support the TXS PS mode as described above.

[0154] like Figure 16 As shown, Example 1600 can begin with STA 1608 transmitting an association (or reassociation) request frame 1610 to AP 1602. In this example, the association request frame 1610 may include a TXS PS mode field (or a TXS PS support field). In Example 1600, 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 1608. 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 1602 can respond to the association request frame 1610 by transmitting an association response frame 1612 to STA 1608. In this example, the association response frame 1612 may include a TXS PS mode field (or a TXS PS support field). In Example 1600, the TXS PS mode field (or TXS PS support field) may be set to 1 to indicate that TXS PS mode is supported at AP 1602. 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.

[0155] Subsequently, AP 1602 can transmit frame 1614 to allocate a portion of the acquired TXOP to STA 1604. Frame 1614 may contain a TXOP sharing mode subfield, an AID 12 subfield, and a first time period (e.g., X us). The TXOP sharing mode subfield may indicate the triggering of the TXOP sharing procedure. For example, the TXOP sharing mode subfield may be set to a non-zero value (e.g., 1, 2, ...) indicating whether TXOP sharing mode 1 or TXOP sharing mode 2 is triggered. The AID 12 subfield may be set to the AID of the STA that can use the first time period to transmit and receive one or more frames. For example, the AID 12 subfield may be set to the AID of STA 1604. The first time period may be specified in microseconds or other time units. In the example, frame 1614 may be an MRTT frame.

[0156] Upon receiving frame 1614, STA 1604 can transmit frame 1616 to AP 1602. In this example, frame 1616 may be a CTS frame. Subsequently, STA 1604 may transmit a non-TBPPDU containing data frame 1618 to STA 1606 during a first time period. STA 1606 may transmit BA frame 1620 to STA 1604 in response to data frame 1618.

[0157] Based on the receipt of frame 1614, which indicates that STA 1608 is not assigned during the first time period, and the TXS PS mode being enabled at STA 1608, STA 1608 can transition to a sleep state during the first time period. According to the TX PS mode, STA 1608 can transition to a sleep state in the following situations: after STA 1608 receives frame 1614 and before STA 1608 receives frame 1616 in response to frame 1614; after STA 1608 receives frame 1616 in response to frame 1614; or if STA 1608 does not receive a third frame during the second time period after receiving frame 1614. 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 1602. The fourth frame can be a beacon frame, a probe response frame, or a correlation response frame.

[0158] In this implementation, STA 1608 may remain in a sleep state for a portion of a first time period after STA 1608 transitions to a sleep state. In this implementation, STA 1608 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 this implementation, AP 1602 may not transmit frames to STA 1608 during the first time period. AP 1602 may transmit frames to STA 1608 after the first time period. In the example ( Figure 16 (Not shown in the image), AP 1602 can receive a frame from STA 1604 within a first time period indicating the release or return of the remaining time of the first time period. The frame may contain a QoS data frame or a QoS empty frame, the QoS data frame or QoS empty frame including an HE variant HT control field with a CAS control subfield, where the RDG / More PPDU subfield is equal to 0. Based on the TXS PS mode being enabled at STA 1608, AP 1602 can wait for the remaining time to end before transmitting the frame to STA 1608. In the example, AP 1602 can use the remaining time to transmit the frame to STA 1604 or STA 1606 (assuming STA 1604 or STA 1606 is in a waking state) or another STA ( Figure 16(Not shown in the image, for example, a traditional STA that does not support TXS PS mode). In another example, AP 1602 can allocate a portion of the remaining time to STA 1606.

[0159] In Example 1600, STA 1608 can return to wake-up state after the first time period ends, or at least from the end of the first time period. STA 1608 can then transmit an association (or reassociation) request frame 1622 to AP 1602. In this example, association request frame 1622 may include a TXS PS mode field (or a TXS PS support field). In Example 1600, the TXS PS mode field (or TXS PS support field) can be set to 0 to indicate that TXS PS mode is disabled at STA 1608. The TXS PS mode field (or TXS PS support field) can be provided in the EHT MAC capability information field of association request frame 1622. AP 1602 can respond to association request frame 1622 by transmitting an association response frame 1624 to STA 1608. In this example, association response frame 1624 may include a TXS PS mode field (or a TXS PS support field). In Example 1600, the TXS PS mode field (or TXS PS support field) can be set to 1 to indicate that TXS PS mode is supported at AP 1602. 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.

[0160] Subsequently, AP 1602 can transmit frame 1626 to allocate a portion of the acquired TXOP to STA 1604. Frame 1626 may contain a TXOP sharing mode subfield, an AID 12 subfield, and a first time period (e.g., X us). The TXOP sharing mode subfield may indicate the triggering of the TXOP sharing procedure. For example, the TXOP sharing mode subfield may be set to a non-zero value (e.g., 1, 2, ...) indicating whether TXOP sharing mode 1 or TXOP sharing mode 2 is triggered. The AID 12 subfield may be set to the AID of the STA that can use the first time period to transmit and receive one or more frames. For example, the AID 12 subfield may be set to the AID of STA 1604. The first time period may be specified in microseconds or other time units. In the example, frame 1626 may be an MRTT frame.

[0161] Upon receiving frame 1626, STA 1604 can transmit frame 1628 to AP 1602. In this example, frame 1616 could be a CTS frame. Subsequently, STA 1604 can transmit a non-TBPPDU containing data frame 1630 to STA 1606 during a first time period. STA 1606 can then transmit BA frame 1632 to STA 1604 in response to data frame 1630.

[0162] Upon receiving frame 1626, in which STA 1608 is not allocated during the first time period, and STA 1608 is disabled based on TXS PS mode, STA 1608 can remain awake during the first time period. In the example ( Figure 16 (Not shown in the image) AP 1602 can receive frames from STA 1604 during a first time period indicating the release or return of the remaining time of the first time period. These frames can contain QoS data frames or QoS empty frames, which include a HE variant of the HT control field with a CAS control subfield, where the RDG / More PPDU subfield is equal to 0. In the example, based on the TXS PS mode being disabled at STA 1608, AP 1602 can transmit frames to STA 1608 during the remaining time of the first time period. In another example, based on the TXS PS mode being disabled at STA 1608, AP 1602 can allocate a portion of the remaining time to STA 1608. Depending on the indicated TXS mode, STA 1608 can use the allocated portion of the remaining time to transmit to AP 1602 or another STA.

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

[0164] In a second embodiment, the frame indicating whether TXS PS mode is enabled or disabled at the STA can be separate from the frame signaling support for TXS PS mode at the STA. In this embodiment, the frame can be a QoS data frame, a QoS empty frame, an action frame, a control frame, or a management frame. The frame may contain elements or subfields indicating whether TXS PS mode is enabled or disabled at the STA. Figure 17Example 1700 illustrates such an embodiment. Figure 17 As shown, Example 1700 includes AP 1702 and STAs 1704, 1706, and 1708. One or more of STAs 1704, 1706, and 1708 may be associated with AP 1702. STAs 1704, 1706, and / or 1708 may support the TXS PS mode as described above.

[0165] like Figure 17 As shown, Example 1700 can begin with STA 1708 transmitting an association (or reassociation) request frame 1710 to AP 1702. In this example, the association request frame 1710 may include a TXS PS mode field (or a TXS PS support field). In Example 1700, the TXS PS mode field (or TXS PS support field) may be set to 1 to indicate that STA 1708 supports the TXS PS mode. 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 1710.

[0166] In an implementation, STA 1708's support for TXS PS mode may include STA 1708's ability to perform TXS PS mode operation under defined conditions. In an implementation, TXS PS mode operation may include STA 1708 entering a sleep state during the TXOP period. The defined conditions may include STA 1708 not being assigned by AP 1702 during the TXOP period. In an implementation, STA 1708's support for TXS PS mode may include STA 1708's ability to transmit frames to AP indicating whether TXS PS mode is enabled or disabled, as described herein. In an embodiment, the frame may include a TXS PS (TPS) control subfield (further described below) indicating whether TXS PS mode is enabled or disabled at STA 1708. The TPS control subfield may include a TPS disable subfield carrying an indication regarding whether TXS PS mode is enabled or disabled at STA 1708. In the implementation, STA 1708's support for TXS PS mode may include STA 1708 being able to enter a sleep state during a TXS period that is not allocated to STA 1708 (e.g., via MRTT frames) when STA 1708 sets the TPS disable subfield to 0.

[0167] AP 1702 can respond to association request frame 1710 by transmitting association response frame 1712 to STA 1708. In the example, association response frame 1712 may contain a TXS PS mode field (or TXS PS support field). In example 1700, the TXS PS mode field (or TXS PS support field) may be set to 1 to indicate AP 1702's support for TXS PS mode. The TXS PS mode field (or TXS PS support field) may be provided in the EHT MAC capability information field of association response frame 1712.

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

[0169] Subsequently, in the example, STA 1708 may transmit frame 1734 indicating that TXS PS mode is enabled at STA 1708. Frame 1734 may be a QoS data frame, a QoS empty frame, an action frame, a control frame, or a management frame. Frame 1734 may contain elements or subfields that can be used to indicate whether TXS PS mode is enabled or disabled at STA 1708.

[0170] In the example, frame 1734 can be QoS data or a QoS empty frame. The QoS data or QoS empty frame may contain an A-control field, which carries an indication of enabling or disabling TXS PS mode at STA 1708. The A-control field may be carried in the HT control field of the QoS data frame or the QoS empty frame. In an embodiment, the A-control field may contain, as shown below: Figure 19The TPS control subfield is shown. 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 1708, and can be set to 1 to indicate that TXS PS mode is disabled at STA 1708. The TPS control subfield may further include reserved bits.

[0171] In another example, frame 1734 could be an action frame. An action frame could contain elements / fields indicating whether TXS PS mode is enabled or disabled at STA 1708. In this example, the action frame could be an EML operation mode notification frame. In an embodiment, the action frame could have, for example... Figure 20 The format shown. For example... Figure 20 As shown, 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 1708, and can be set to 1 to indicate that TXS PS mode is disabled at STA 1708. The TPS control subfield may further include reserved bits.

[0172] In the implementation scheme, AP 1702 can acknowledge frame 1734 by transmitting acknowledgment frame 1736 to STA 1708. Acknowledgment frame 1736 can be an ACK frame or a BA frame.

[0173] Subsequently, AP 1702 can transmit frame 1714 to allocate a portion of the acquired TXOP to STA 1704. Frame 1714 may contain a TXOP sharing mode subfield, an AID 12 subfield, and a first time period (e.g., X us). The TXOP sharing mode subfield may indicate the triggering of the TXOP sharing procedure. For example, the TXOP sharing mode subfield may be set to a non-zero value (e.g., 1, 2, ...) indicating whether TXOP sharing mode 1 or TXOP sharing mode 2 is triggered. The AID 12 subfield may be set to the AID of the STA that can use the first time period to transmit and receive one or more frames. For example, the AID 12 subfield may be set to the AID of STA 1704. The first time period may be specified in microseconds or other time units. In the example, frame 1714 may be an MRTT frame.

[0174] Upon receiving frame 1714, STA 1704 can transmit frame 1716 to AP 1702. In this example, frame 1716 may be a CTS frame. Subsequently, STA 1704 can transmit a non-TBPPDU containing data frame 1718 to STA 1706 during a first time period. STA 1706 can then transmit BA frame 1720 to STA 1704 in response to data frame 1718.

[0175] Based on the receipt of frame 1714, which indicates that STA 1708 is not assigned during the first time period, and the TXS PS mode being enabled at STA 1708, STA 1708 can transition to a sleep state during the first time period. According to the TX PS mode, STA 1708 can transition to a sleep state in the following situations: after STA 1708 receives frame 1714 and before STA 1708 receives frame 1716 in response to frame 1714; after STA 1708 receives frame 1716 in response to frame 1714; or if STA 1708 does not receive a third frame during the second time period after receiving frame 1714. 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 1702. The fourth frame can be a beacon frame, a probe response frame, or a correlation response frame.

[0176] In one implementation, STA 1708 may remain in a sleep state for a portion of a first time period after STA 1708 transitions to a sleep state. In another implementation, STA 1708 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 yet another implementation, AP 1702 may not transmit frames to STA 1708 during the first time period. AP 1702 may transmit frames to STA 1708 after the first time period. In the example ( Figure 17 (Not shown in the image), AP 1702 can receive a frame from STA 1704 within a first time period indicating the release or return of the remaining time of the first time period. The frame may contain a QoS data frame or a QoS empty frame, the QoS data frame or QoS empty frame including an HE variant HT control field with a CAS control subfield, where the RDG / More PPDU subfield is equal to 0. Based on the TXS PS mode being enabled at STA 1708, AP 1702 can wait for the remaining time to end before transmitting the frame to STA 1708. In the example, AP 1702 can use the remaining time to transmit the frame to STA 1704 or STA 1706 (assuming STA 1704 or STA 1706 is in a waking state) or another STA ( Figure 17 (Not shown in the diagram, for example, a traditional STA that does not support TXS PS mode). In another example, AP 1702 can allocate a portion of the remaining time to STA 1706.

[0177] In Example 1700, STA 1708 may return to a wake-up state after the first time period ends, or at least from the end of the first time period. Subsequently, STA 1708 may transmit frame 1738 indicating that the TXS PS mode is disabled at STA 1708. Frame 1738 may be a QoS data frame, a QoS empty frame, an action frame, a control frame, or a management frame. Frame 1738 may contain elements or subfields that can be used to indicate whether the TXS PS mode is enabled or disabled at STA 1708. In this example, frame 1738 may be QoS data or a QoS empty frame. QoS data or a QoS empty frame may contain an A-control field carrying an indication of whether the TXS PS mode is enabled or disabled at STA 1708. The A-control field may be carried in the HT control field of the QoS data frame or the QoS empty frame. In another example, frame 1738 may be an action frame. An action frame may contain elements / fields indicating whether the TXS PS mode is enabled or disabled at STA 1708. In this example, the action frame may be an EML operation mode notification frame.

[0178] In the implementation scheme, AP 1702 can acknowledge frame 1738 by transmitting acknowledgment frame 1740 to STA 1708. Acknowledgment frame 1740 can be an ACK frame or a BA frame.

[0179] Subsequently, AP 1702 can transmit frame 1726 to allocate a portion of the acquired TXOP to STA 1704. Frame 1726 may contain a TXOP sharing mode subfield, an AID 12 subfield, and a first time period (e.g., X us). The TXOP sharing mode subfield may indicate the triggering of the TXOP sharing procedure. For example, the TXOP sharing mode subfield may be set to a non-zero value (e.g., 1, 2, ...) indicating whether TXOP sharing mode 1 or TXOP sharing mode 2 is triggered. The AID 12 subfield may be set to the AID of the STA that can use the first time period to transmit and receive one or more frames. For example, the AID 12 subfield may be set to the AID of STA 1704. The first time period may be specified in microseconds or other time units. In the example, frame 1726 may be an MRTT frame.

[0180] Upon receiving frame 1726, STA 1704 can transmit frame 1728 to AP 1702. In this example, frame 1716 could be a CTS frame. Subsequently, STA 1704 can transmit a non-TBPPDU containing data frame 1730 to STA 1706 during a first time period. STA 1706 can then transmit BA frame 1732 to STA 1704 in response to data frame 1730.

[0181] Upon receiving frame 1726, in which STA 1708 is not allocated during the first time period, and STA 1708 is disabled based on TXS PS mode, STA 1708 can remain awake during the first time period. In the example ( Figure 17 (Not shown in the image) AP 1702 can receive frames from STA 1704 during a first time period indicating the release or return of the remaining time of the first time period. These frames can contain QoS data frames or QoS empty frames, which include a HE variant of the HT control field with a CAS control subfield, where the RDG / More PPDU subfield is equal to 0. In the example, based on the TXS PS mode being disabled at STA 1708, AP 1702 can transmit frames to STA 1708 during the remaining time of the first time period. In another example, based on the TXS PS mode being disabled at STA 1708, AP 1702 can allocate a portion of the remaining time to STA 1708. Depending on the indicated TXS mode, STA 1708 can use the allocated portion of the remaining time to transmit to AP 1702 or another STA.

[0182] like Figure 17 The advantages of the second embodiment, as demonstrated, include reduced signaling overhead and latency in the STA notifying the AP of TXS PS mode state changes at the STA. As described above, TXS PS mode state changes can be carried in various frame types and are not limited to association request frames. For example, TXS PS mode state changes can be carried in QoS data / empty frames or short action frames. The AP can respond to frames from the STA with short acknowledgment frames instead of relatively large association response frames.

[0183] In the third embodiment, similar to the second embodiment, the AP can request the TXS PS mode status at the STA. The STA can respond to the request from the AP by transmitting a frame to the AP indicating whether the TXS PS mode is enabled or disabled at the STA. In this embodiment, the AP can transmit a frame requesting the TXS PS mode status at the STA to the STA before initiating TXS operation. Figure 18 Example 1800 illustrates such an embodiment. Figure 18 As shown, Example 1800 includes AP 1802 and STAs 1804, 1806, and 1808. One or more of STAs 1804, 1806, and 1808 may be associated with AP 1802. STAs 1804, 1806, and / or 1808 may support the TXS PS mode as described above.

[0184] like Figure 18As shown, Example 1800 can begin with STA 1808 transmitting an association (or reassociation) request frame 1810 to AP 1802. In this example, the association request frame 1810 may include a TXS PS mode field (or a TXS PS support field). In Example 1800, the TXS PS mode field (or TXS PS support field) may be set to 1 to indicate that STA 1808 supports the TXS PS mode. 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 1810.

[0185] In an implementation, STA 1808's support for TXS PS mode may include STA 1808's ability to perform TXS PS mode operation under defined conditions. In an implementation, TXS PS mode operation may include STA 1808 entering a sleep state during the TXOP period. The defined conditions may include STA 1808 not being allocated by AP 1802 during the TXOP period. In an implementation, STA 1808's support for TXS PS mode may include STA 1808's ability to transmit frames to AP indicating whether TXS PS mode is enabled or disabled, as described herein. In an embodiment, the frame may include a TPS control subfield indicating whether TXS PS mode is enabled or disabled at STA 1808. The TPS control subfield may include a TPS disable subfield carrying an indication regarding whether TXS PS mode is enabled or disabled at STA 1808. In the implementation, STA 1808's support for TXS PS mode may include STA 1808 being able to enter a sleep state during a TXS period that is not allocated to STA 1808 (e.g., via MRTT frames) when STA 1808 sets the TPS disable subfield to 0.

[0186] AP 1802 can respond to association request frame 1810 by transmitting association response frame 1812 to STA 1808. In the example, association response frame 1812 may contain a TXS PS mode field (or a TXS PS support field). In example 1800, the TXS PS mode field (or TXS PS support field) may be set to 1 to indicate AP 1802's support for TXS PS mode. The TXS PS mode field (or TXS PS support field) may be provided in the EHT MAC capability information field of association response frame 1812.

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

[0188] Subsequently, in the example, AP 1802 may transmit frame 1838 to STA 1808 requesting the TXS PS mode status at STA 1808. Frame 1838 may be a control frame, management frame, or action frame. In an embodiment, AP 1802 may transmit frame 1838 to STA 1808 before initiating TXS operation. In example 1800, STA 1808 may respond to frame 1838 by transmitting frame 1834 to AP 1802, indicating that TXS PS mode is enabled at STA 1808. Frame 1834 may be a QoS data frame, QoS empty frame, action frame, control frame, or management frame. Frame 1834 may contain elements or subfields that can be used to indicate whether TXS PS mode is enabled or disabled at STA 1808.

[0189] In the example, frame 1834 can be QoS data or a QoS empty frame. The QoS data or QoS empty frame may contain an A-control field carrying an indication of enabling or disabling the TXS PS mode at STA 1808. The A-control field may be carried in the HT control field of the QoS data frame or the QoS empty frame. In an embodiment, the A-control field may contain as described above. Figure 19 The TPS control subfields are shown.

[0190] In another example, frame 1834 could be an action frame. An action frame may contain elements / fields indicating whether TXS PS mode is enabled or disabled at STA 1808. In this example, the action frame could be an EML operation mode notification frame. In embodiments, the action frame may have the features described above. Figure 20 The format shown.

[0191] In the implementation scheme, AP 1802 can acknowledge frame 1834 by transmitting acknowledgment frame 1836 to STA 1808. Acknowledgment frame 1836 can be an ACK frame or a BA frame.

[0192] Subsequently, AP 1802 can transmit frame 1814 to allocate a portion of the acquired TXOP to STA 1804. Frame 1814 may contain a TXOP sharing mode subfield, an AID 12 subfield, and a first time period (e.g., X us). The TXOP sharing mode subfield may indicate the triggering of the TXOP sharing procedure. For example, the TXOP sharing mode subfield may be set to a non-zero value (e.g., 1, 2, ...) indicating whether TXOP sharing mode 1 or TXOP sharing mode 2 is triggered. The AID 12 subfield may be set to the AID of the STA that can use the first time period to transmit and receive one or more frames. For example, the AID 12 subfield may be set to the AID of STA 1804. The first time period may be specified in microseconds or other time units. In the example, frame 1814 may be an MRTT frame.

[0193] Upon receiving frame 1814, STA 1804 can transmit frame 1816 to AP 1802. In this example, frame 1816 may be a CTS frame. Subsequently, STA 1804 may transmit a non-TBPPDU containing data frame 1818 to STA 1806 during a first time period. STA 1806 may transmit BA frame 1820 to STA 1804 in response to data frame 1818.

[0194] Based on the receipt of frame 1814, which indicates that STA 1808 is not assigned during the first time period, and the TXS PS mode being enabled at STA 1808, STA 1808 can transition to a sleep state during the first time period. According to the TX PS mode, STA 1808 can transition to a sleep state in the following situations: after STA 1808 receives frame 1814 and before STA 1808 receives frame 1816 in response to frame 1814; after STA 1808 receives frame 1816 in response to frame 1814; or if STA 1808 does not receive a third frame during the second time period after receiving frame 1814. 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 1802. The fourth frame can be a beacon frame, a probe response frame, or a correlation response frame.

[0195] In this implementation, STA 1808 may remain in a sleep state for a portion of a first time period after STA 1808 transitions to a sleep state. In this implementation, STA 1808 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 this implementation, AP 1802 may not transmit frames to STA 1808 during the first time period. AP 1802 may transmit frames to STA 1808 after the first time period. In the example ( Figure 18 (Not shown in the image), AP 1802 can receive a frame from STA 1804 within a first time period indicating the release or return of the remaining time of the first time period. The frame may contain a QoS data frame or a QoS empty frame, the QoS data frame or QoS empty frame including an HE variant HT control field with a CAS control subfield, where the RDG / More PPDU subfield is equal to 0. Based on the TXS PS mode being enabled at STA 1808, AP 1802 can wait for the remaining time to end before transmitting the frame to STA 1808. In the example, AP 1802 can use the remaining time to transmit the frame to STA 1804 or STA 1806 (assuming STA 1804 or STA 1806 is in a waking state) or another STA ( Figure 18 (Not shown, for example, a traditional STA that does not support TXS PS mode). In another example, AP 1802 can allocate a portion of the remaining time to STA 1806.

[0196] Figure 21 An example process 2100 according to an embodiment is shown. Example process 2100 can be executed by an AP (such as AP 1602, AP 1702, or AP 1802 described above). Figure 21 As shown, process 2100 may include steps 2102 and 2104.

[0197] Step 2102 includes transmitting a first frame of the time period shared by the AP and the first STA with the first STA. The first STA may be associated with the AP. The first frame may contain a trigger frame. The trigger frame may contain an MRTT frame.

[0198] Step 2104 includes the AP enabling TXS PS mode at the second STA to avoid transmission to the second STA during the time period. The second STA may be associated with the AP. In embodiments, step 2104 may include enabling TXS PS mode at the second STA to postpone, delay, or reschedule transmissions to the second STA to a later time period.

[0199] In an embodiment, process 2100 may further include the AP receiving a second frame from the second STA, the second frame indicating whether TXS PS mode is enabled or disabled at the second STA. In an embodiment, process 2100 may further include the AP transmitting a frame to the second STA requesting the TXS PS mode status at the second STA; and receiving the second frame in response to the request frame.

[0200] In one embodiment, enabling the TXS PS mode at the second STA involves the second STA performing TXS PS mode operation under defined conditions. In another embodiment, disabling the TXS PS mode at the second STA involves the second STA not performing TXS PS mode operation under defined conditions. In another embodiment, the defined conditions include the second STA not sharing a TXOP period with the first STA or not allocating a second STA during the first frame. In yet another embodiment, TXS PS mode operation involves the second STA entering a sleep state during the TXOP period.

[0201] In this embodiment, the second frame includes an association request frame. In this embodiment, the association request frame includes a TXS PS mode field (or a TXS PS support field). In this embodiment, if the second frame indicates that TXS PS mode is enabled, the TXS PS mode field (or TXS PS support field) can be set to 1. In this embodiment, if the second frame indicates that TXS PS mode is disabled, the TXS PS mode field (or TXS PS support field) can be set to 0.

[0202] In another embodiment, the second frame includes a QoS data frame, a QoS empty frame, an action frame, a control frame, or a management frame. The second frame may include elements or subfields indicating whether TXS PS mode is enabled or disabled at the second STA.

[0203] In an embodiment, process 2100 may further include the AP transmitting an acknowledgment frame to the second STA in response to the second frame. The acknowledgment frame may include an ACK frame or a BA frame.

[0204] In an embodiment, process 2100 may further include the AP receiving an associated request frame from the second STA indicating the second STA's support for the TXS PS mode; and the AP transmitting an associated response frame to the second STA indicating the AP's support for the TXS PS mode.

[0205] In an embodiment, process 2100 may further include the AP transmitting a third frame to the second STA after the time period ends.

[0206] In an embodiment, process 2100 may further include the AP receiving a fourth frame from the first STA indicating the remaining time period of the release period; and during the remaining time period, the AP transmitting a fifth frame to the second STA, provided that the TXS PS mode is disabled at the second STA.

[0207] In an embodiment, process 2100 may further include the AP receiving a fourth frame from the first STA indicating the remaining time period of the release period; and after the remaining time period, the AP transmitting a fifth frame to the second STA based on the TXS PS mode being enabled at the second STA.

[0208] Figure 22 Another example process 2200 according to an embodiment is shown. Example process 2200 can be executed by a first STA (such as STA 1608, STA 1708, or STA 1808 as described above). Figure 22 As shown, process 2200 may include steps 2202 and 2204.

[0209] Step 2202 includes the first STA receiving a first frame from the AP that shares a time period of TXOP with the second STA. The first STA and / or the second STA may be associated with the AP. The first frame may contain a trigger frame. The trigger frame may contain an MRTT frame.

[0210] Step 2204 includes switching the power state of the first STA to a sleep state by enabling the first STA based on TXS PS mode at the first STA.

[0211] In an embodiment, process 2200 may further include a second frame transmitted from the first STA to the AP indicating whether TXS PS mode is enabled or disabled at the first STA. In an embodiment, process 2200 may further include a frame received by the first STA from the AP requesting a TXS PS mode status at the first STA; and the transmission of the second frame in response to the request frame.

[0212] In one embodiment, enabling the TXS PS mode at the first STA involves the first STA performing TXS PS mode operation under defined conditions. In another embodiment, disabling the TXS PS mode at the first STA involves the first STA not performing TXS PS mode operation under defined conditions. In another embodiment, the defined conditions include the first frame not sharing a TXOP time period with the first STA or not allocating a TXOP to the first STA. In yet another embodiment, TXS PS mode operation involves the first STA entering a sleep state during the TXOP time period.

[0213] In this embodiment, the second frame includes an association request frame. In this embodiment, the association request frame includes a TXS PS mode field (or a TXS PS support field). In this embodiment, if the second frame indicates that TXS PS mode is enabled, the TXS PS mode field (or TXS PS support field) can be set to 1. In this embodiment, if the second frame indicates that TXS PS mode is disabled, the TXS PS mode field (or TXS PS support field) can be set to 0.

[0214] In another embodiment, the second frame includes a QoS data frame, a QoS empty frame, an action frame, a control frame, or a management frame. The second frame may include elements or subfields indicating whether TXS PS mode is enabled or disabled at the first STA.

[0215] In an embodiment, process 2200 may further involve the first STA receiving an acknowledgment frame from the AP in response to the second frame. The acknowledgment frame may contain an ACK frame or a BA frame.

[0216] In an embodiment, process 2200 may further include the first STA transmitting an associated request frame to the AP indicating the first STA's support for the TXS PS mode; and the first STA receiving an associated response frame from the AP indicating the AP's support for the TXS PS mode.

[0217] In an embodiment, process 2200 may further include receiving a third frame from the AP by the first STA after the time period ends.

[0218] In another embodiment, process 2200 may further include, during a time period, the first STA receiving a fourth frame from the AP, provided that the TXS PS mode is disabled at the first STA. The AP may transmit the fourth frame to the first STA based on a fifth frame received from the second STA indicating the remaining time period for releasing the time period.

Claims

1. A method comprising: The access point (AP) receives a first frame from the first station (STA), which indicates whether the triggered transmission opportunity (TXOP) shared TXS power-saving mode is enabled or disabled at the first STA. The AP transmits a trigger frame for the time period during which it shares the TXOP with the second STA; as well as The AP enables the TXS power-saving mode at the first STA based on the first frame indication, thereby avoiding transmission to the first STA during the time period.

2. A method comprising: The first frame is transmitted by the access point (AP), and the first frame shares the transmission opportunity (TXOP) time period with the first STA; and The AP-triggered TXOP shared TXS power-saving mode is enabled at the second STA to avoid transmission to the second STA during the time period.

3. The method of claim 2, wherein the first frame comprises a trigger frame.

4. The method of claim 3, wherein the trigger frame comprises a multi-user request to send a trigger MRTT frame.

5. The method according to any one of claims 2 to 4, further comprising receiving a second frame from the second STA by the AP, the second frame indicating whether the TXS power saving mode is enabled or disabled at the second STA.

6. The method according to any one of claims 2 to 5, wherein the TXS power saving mode enabled at the second STA comprises the second STA performing TXS power saving mode operation under defined conditions.

7. The method of claim 6, wherein the TXS power saving mode disabled at the second STA includes the second STA not performing the TXS power saving mode operation under the defined conditions.

8. The method of claim 7, wherein the defined condition includes that the first frame does not share the time period of the TXOP with the second STA, and wherein the TXS power saving mode operation includes the second STA entering a sleep state during the time period of the TXOP.

9. The method of claim 5, wherein the second frame comprises an association request frame.

10. The method of claim 9, wherein the associated request frame includes a TXS power saving mode field.

11. The method of claim 10, wherein the second frame indicates that the TXS power saving mode is enabled at the second STA, and wherein the TXS power saving mode field is set to 1.

12. The method of any one of claims 10 to 11, wherein the second frame indicates that the TXS power saving mode is disabled at the second STA, and wherein the TXS power saving mode field is set to 0.

13. The method of claim 5, wherein the second frame comprises a QoS data frame, a QoS empty frame, an action frame, a control frame, or a management frame.

14. The method of claim 13, wherein the second frame includes an element or subfield indicating whether the TXS power saving mode is enabled or disabled at the second STA.

15. The method of claim 5, further comprising the AP transmitting an acknowledgment frame to the second STA in response to the second frame.

16. The method of claim 15, wherein the acknowledgment frame comprises an ACK frame or a block acknowledgment (BA) frame.

17. The method of claim 5, further comprising: The AP receives an association request frame from the second STA, the association request frame indicating that the second STA supports the TXS power-saving mode; and The AP transmits an association response frame to the second STA, the association response frame indicating the AP's support for the TXS power saving mode.

18. The method according to any one of claims 2 to 17, further comprising the AP transmitting a third frame to the second STA after the end of the time period.

19. The method according to any one of claims 2 to 18, further comprising: The AP receives a fourth frame from the first STA, the fourth frame indicating the remaining time for releasing the time period; and During the remaining time, with the TXS power-saving mode disabled at the second STA, the AP transmits the fifth frame to the second STA.

20. The method according to any one of claims 2 to 18, further comprising: The AP receives a fourth frame from the first STA, the fourth frame indicating the remaining time for releasing the time period; and The AP transmits the fifth frame to the second STA after the remaining time, based on the TXS power-saving mode being enabled at the second STA.

21. The method according to any one of claims 2 to 20, wherein the second STA is associated with the AP.

22. A method comprising: The first frame is transmitted from the first STA to the access point AP. The first frame indicates whether the triggered transmission opportunity TXOP shared TXS power saving mode is enabled or disabled at the first STA. The first STA receives a trigger frame from the AP that shares the TXOP time period with the second STA; as well as The first STA switches its power state to sleep mode by enabling the TXS power saving mode based on the first frame indication.

23. A method comprising: The first frame, received by the first STA from the access point AP, shares the time period of the TXOP with the second STA; and The first STA is switched to a sleep state by enabling the TXOP shared TXS power saving mode triggered by the first STA.

24. The method of claim 23, wherein the first frame comprises a trigger frame.

25. The method of claim 24, wherein the trigger frame comprises a multi-user request to send a trigger MRTT frame.

26. The method according to any one of claims 23 to 25, further comprising transmitting a second frame from the first STA to the AP, the second frame indicating whether the TXS power-saving mode is enabled or disabled at the first STA.

27. The method of any one of claims 23 to 26, wherein the TXS power saving mode enabled at the first STA comprises the first STA performing TXS power saving mode operation under defined conditions.

28. The method of claim 27, wherein the TXS power saving mode disabled at the first STA comprises the first STA not performing the TXS power saving mode operation under the defined conditions.

29. The method of claim 28, wherein the defined condition includes the first frame not sharing the time period of the TXOP with the first STA, and wherein the TXS power saving mode operation includes the first STA entering the sleep state during the time period of the TXOP.

30. The method of claim 26, wherein the second frame comprises an association request frame.

31. The method of claim 30, wherein the associated request frame includes a TXS power saving mode field.

32. The method of claim 31, wherein the second frame indicates that the TXS power saving mode is enabled at the first STA, and wherein the TXS power saving mode field is set to 1.

33. The method of any one of claims 31 to 32, wherein the second frame indicates that the TXS power saving mode is disabled at the first STA, and wherein the TXS power saving mode field is set to 0.

34. The method of claim 26, wherein the second frame comprises a QoS data frame, a QoS empty frame, an action frame, a control frame, or a management frame.

35. The method of claim 34, wherein the second frame includes an element or subfield indicating whether the TXS power saving mode is enabled or disabled at the first STA.

36. The method of claim 26, further comprising receiving an acknowledgment frame from the AP in response to the second frame by the first STA.

37. The method of claim 36, wherein the acknowledgment frame comprises an ACK frame or a block acknowledgment (BA) frame.

38. The method of claim 26, further comprising: The first STA transmits an association request frame to the AP, the association request frame indicating the first STA's support for the TXS power-saving mode; and The first STA receives an associated response frame from the AP, the associated response frame indicating that the AP supports the TXS power saving mode.

39. The method according to any one of claims 23 to 38, further comprising receiving a third frame from the AP by the first STA after the end of the time period.

40. The method according to any one of claims 23 to 39, further comprising, during the time period, receiving a fourth frame from the AP by the first STA under the condition that the TXS power-saving mode is disabled at the first STA.

41. The method of claim 40, wherein the AP transmits the fourth frame to the first STA based on receiving a fifth frame from the second STA indicating the remaining time of the time period to be released.

42. The method according to any one of claims 23 to 41, wherein the first STA is associated with the AP.

43. An apparatus comprising: One or more processors; and A memory that stores instructions that, when executed by the one or more processors, cause the apparatus to perform the method according to any one of claims 1 to 42.

44. 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 to 42.

Images