TW201631947A - Triggered target wake time operation - Google Patents

Abstract

A method, an apparatus, and a computer-readable medium for wireless communication are provided. In an aspect, an apparatus may be configured to determine whether to switch to an active mode, a power save mode, or a TWT power save mode. During the TWT power save mode, the apparatus may enter an awake state during TWT service periods and may enter a doze state outside of the TWT service periods. The apparatus may transmit a message to a second wireless device based on the determination.

Description

Triggered target wake-up time operation (3) [Cross-reference to related applications]

This patent application claims US Provisional Application No. 62/109,024, filed on January 28, 2015, entitled "TRIGGERED TARGET WAKE TIME OPERATION", on February 27, 2015 U.S. Provisional Application No. 62/126,403, entitled "TRIGGERED TARGET WAKE TIME OPERATION", filed on October 21, 2015, entitled "TRIGGERED TARGET WAKE TIME OPERATION (" U.S. Provisional Application No. 62/244,682, which was filed on October 23, 2015, and the US Provisional Application entitled "TRIGGERED TARGET WAKE TIME OPERATION" US Provisional Application No. 62/260,155, filed on November 25, 2015, entitled "TRIGGERED TARGET WAKE TIME OPERATION", dated November 25, 2015, in January 2016 The US Provisional Application No. 62/278,366, entitled "TRIGGERED TARGET WAKE TIME OPERATION", filed on the 13th, The entire contents of the application via expressly incorporated herein.

This case is generally about the communication system, especially regarding the triggering target wake-up time operation.

In many telecommunication systems, communication networks are used to exchange messages between several spatially separated interactive devices. The network may be classified according to geographic extent, which may be, for example, a city area, a local area, or a personal area. Such networks can be designated as wide area networks (WANs), metropolitan area networks (MANs), regional networks (LANs), wireless local area networks (WLANs), or personal area networks (PANs), respectively. The network is also based on the switching/routing techniques used to interconnect various network nodes and devices (eg, circuit switching versus packet switching), the type of physical media used for transmission (eg, wired versus wireless), and used The set of communication protocols (for example, Internet Protocol Suite, Synchronous Optical Networking (SONET), Ethernet, etc.) varies.

Wireless networks are often preferred when the network elements are mobile and thus have dynamic connectivity requirements or where the network architecture is formed in an ad hoc topology rather than a fixed topology. Wireless networks use electromagnetic waves in the frequency bands of radio, microwave, infrared, light, etc. to employ intangible physical media in a non-guided propagation mode. Wireless networks advantageously facilitate user mobility and rapid on-site deployment when compared to fixed wired networks.

The system, method, computer readable medium and device of the present invention each have several aspects, and not all of the single aspects are responsible for the desired attributes of the present invention. Without limiting the scope of the invention as expressed by the appended claims In the case, some features will now be briefly discussed. After considering this discussion, and particularly after reading the section entitled "Detailed Description," it will be appreciated that the features of the present invention are to provide advantages to devices in a wireless network.

One aspect of the present invention provides a device (e.g., station or access point) for wireless communication. The apparatus can be configured to transmit a first message including the first trigger field to the second wireless device. The first trigger field may indicate whether the first message includes a request for a trigger message (or frame) to be sent by the second wireless device at the beginning of one or more TWTs of the one or more target wake time (TWT) service periods . In one aspect, the TWT can be referred to as a target trigger time (TTT), or any other time reference. The apparatus can be configured to receive a second message from the second wireless device. The second message can include a second trigger field based on the first message, and the second trigger field can indicate whether the second wireless device will transmit the trigger message at the beginning of the TWT service period. In some embodiments, the second message can be sent to the first wireless device without receiving the first message. In some embodiments, the message can be multicast or broadcast.

Another aspect of the present disclosure provides a device (e.g., station or access point) for wireless communication. The apparatus can be configured to receive a first message including the first trigger field from the second wireless device. The first trigger field may indicate whether the first message includes a request for a trigger message to be sent by the first wireless device at the beginning of the TWT service period. The apparatus can be configured to determine the TWT schedule based on the received first message. The apparatus can be configured to transmit the second message to the second wireless device. The second message can include a TWT schedule and a second trigger field based on the determined TWT schedule. The second trigger field may indicate whether the device will transmit a trigger message at the beginning of the TWT service period.

Another aspect of the present disclosure provides a device (e.g., station or access point). The device can be configured to determine the TWT schedule. The apparatus can be configured to broadcast a message including TWT schedules to a plurality of wireless devices. The message may include a broadcast indicator indicating that the TWT schedule is a broadcast TWT schedule.

Another aspect of the present disclosure provides a device (e.g., station or access point). The apparatus can be configured to receive a message including a TWT schedule from the second wireless device. The message may include a broadcast indicator indicating that the TWT schedule is a broadcast TWT schedule. The apparatus can be configured to determine one or more TWTs for the first wireless device based on the TWT schedule.

Another aspect of the present disclosure provides a device (e.g., station or access point). The apparatus can be configured to decide whether to switch to an active mode, a power save mode, or a TWT power save mode. During the TWT power save mode, the device may enter an awake state during the TWT service period and may enter a doze state outside of the TWT service period. The apparatus can be configured to transmit a message to the second wireless device based on a decision whether to switch the mode.

Another aspect of the present disclosure provides a device (e.g., station or access point). The apparatus can be configured to receive a message from the second wireless device indicating an intent of the second wireless device to switch to an operational mode. The mode of operation can be one of an active mode, a power save mode, or a TWT power save mode. During the TWT power save mode, the second wireless device may enter an awake state during the TWT service period and may enter the snoring state outside of the TWT service period. The apparatus can be configured to store an operational mode associated with the second wireless device. The apparatus can be configured to transmit an acknowledgement of the operational mode switch to the second wireless device.

100‧‧‧Wireless communication system

102‧‧‧Basic Service Area (BSA)

104‧‧‧AP

108‧‧‧Downlink (DL)

110‧‧‧Uplink (UL)

112‧‧‧STA

114‧‧‧STA

116‧‧‧STA

118‧‧‧STA

124‧‧‧TWT components

126‧‧‧TWT components

200‧‧‧TWT elements

300‧‧‧ diagram

302‧‧‧AP

304‧‧‧BSS

306‧‧‧STA

308‧‧‧STA

310‧‧‧STA

312‧‧‧First message

314‧‧‧Second message

316‧‧‧Trigger message

350‧‧‧Time Sequence Flow Chart

400‧‧‧ method

405‧‧‧ square

410‧‧‧ square

415‧‧‧ square

420‧‧‧ square

425‧‧‧ square

430‧‧‧ square

435‧‧‧ squares

440‧‧‧ squares

500‧‧‧ method

505‧‧‧ square

510‧‧‧ square

515‧‧‧ square

520‧‧‧ square

525‧‧‧ square

530‧‧‧ square

600‧‧‧图

602‧‧‧AP

604‧‧‧BSA

606‧‧‧STA

608‧‧‧STA

610‧‧‧STA

612‧‧‧ operation

614‧‧‧First message

616‧‧‧trigger frame

618‧‧‧Information

650‧‧‧Timeline flow chart

700‧‧‧ method

705‧‧‧ square

710‧‧‧ square

715‧‧‧ square

720‧‧‧ squares

725‧‧‧ square

800‧‧‧ method

805‧‧‧ square

810‧‧‧ square

815‧‧‧ square

820‧‧‧ square

825‧‧‧ square

830‧‧‧ square

835‧‧‧ squares

900‧‧‧图

902‧‧‧AP

904‧‧‧BSA

906‧‧‧STA

908‧‧‧STA

910‧‧‧STA

912‧‧‧ operation

914‧‧‧Information

916‧‧‧Accept the message

918‧‧‧Second message

950‧‧‧Timeline flow chart

1000‧‧‧ method

1005‧‧‧ square

1010‧‧‧ square

1015‧‧‧

1020‧‧‧ square

1025‧‧‧ square

1100‧‧‧ method

1105‧‧‧ square

1110‧‧‧

1115‧‧‧

1120‧‧‧ square

1125‧‧‧ square

1130‧‧‧

1135‧‧‧ square

1140‧‧‧ square

1200‧‧‧Request Type Field

1300‧‧‧ method

1400‧‧‧ method

1405‧‧‧Beacon

1410‧‧‧ Trigger frame

1415‧‧‧Second trigger frame

1500‧‧‧TWT group assignment field

1600‧‧‧ Second TWT element format

1605‧‧‧TWT elements

1702‧‧‧Wireless equipment

1704‧‧‧ Processor

1706‧‧‧ memory

1708‧‧‧Shell

1710‧‧‧transmitter

1712‧‧‧ Receiver

1714‧‧‧ transceiver

1716‧‧‧Antenna

1718‧‧‧Signal Detector

1720‧‧‧Digital Signal Processor (DSP)

1722‧‧‧User interface

1724‧‧‧TWT components

1726‧‧‧ busbar system

1800‧‧‧Wireless communication equipment

1805‧‧‧ Receiver

1810‧‧‧Processing system

1815‧‧‧transmitter

1824‧‧‧TWT components

1826‧‧‧ mode components

Figure 1 illustrates an example wireless communication system in which aspects of the present invention may be employed.

2 is an exemplary diagram of a target wake-up time element for supporting a target wake-up time and a trigger frame schedule.

3 is an exemplary diagram of a wireless network implementing a TWT schedule and an exemplary timing diagram for TWT operations.

4 is a flow diagram of an example method of requesting a TWT schedule.

5 is a flow diagram of an example method of responding to a TWT scheduling request or transmitting information related to a TWT schedule.

6 is an exemplary diagram of a wireless network implementing broadcast TWT scheduling and an exemplary timing diagram for TWT operations.

7 is a flow diagram of an example method of broadcasting a TWT schedule.

8 is a flow diagram of an example method of communicating based on a broadcast TWT schedule.

9 is an exemplary diagram of a wireless network supporting a power save mode of a TWT schedule and an exemplary timing diagram for TWT operation.

10 is a flow diagram of an example method of switching to or leaving a TWT power save mode.

11 is a flow diagram of an example signal transfer method for switching to a TWT power save mode.

12 is an exemplary diagram of a request type field within a TWT element for broadcasting a TWT.

FIG. 13 illustrates a method of broadcasting a TWT for a plurality of TWTs.

Figure 14 illustrates the adoption of a level in the trigger frame during the TWT service period. The method of linking fields.

15 is an exemplary diagram of a TWT group assignment field within a TWT element of a broadcast TWT for multiple STAs.

FIG. 16 illustrates an exemplary diagram of a second TWT element format.

17 illustrates an example functional block diagram of a wireless device that can perform TWT scheduling within the wireless communication system of FIG.

18 is a functional block diagram of an example wireless communication device that performs TWT scheduling.

Various aspects of the novel systems, devices, computer readable media and methods are described more fully hereinafter with reference to the accompanying drawings. However, the present invention may be embodied in many different forms and should not be construed as being limited to any specific structure or function. Rather, these aspects are provided so that this disclosure will be thorough and complete, and the scope of the present invention will be fully conveyed by those of ordinary skill in the art to which the invention pertains. Based on the teachings herein, one of ordinary skill in the art to which the present invention pertains will be appreciated. The scope of the present disclosure is intended to cover any aspect of the novel systems, devices, computer program products and methods disclosed herein, regardless of the present invention. Any other aspect is implemented independently or in combination. For example, any number of aspects set forth herein can be used to implement an apparatus or a method of practice. In addition, the scope of the invention is intended to cover such apparatus or methods that are practiced in the embodiments of the invention. It should be understood that any aspect disclosed herein can be implemented by one or more elements of the claim.

Although specific aspects are described herein, numerous variations and permutations of these aspects are within the scope of the present disclosure. Although some of the benefits and advantages of the preferred aspects are mentioned, the scope of the present invention is not intended to be limited to a particular benefit, use, or objective. Rather, the various aspects of the present invention are intended to be broadly applicable to different wireless technologies, system configurations, networks, and transmission protocols, some of which are illustrated by way of example in the drawings and the description of the preferred aspects. The detailed description and drawings are merely illustrative of the present invention, and the scope of the present invention is defined by the appended claims and their equivalents.

Popular wireless network technologies can include various types of WLANs. WLANs can be used to interconnect nearby devices with widely used networking protocols. The various aspects described herein can be applied to any communication standard, such as a wireless protocol.

In some aspects, orthogonal frequency division multiplexing (OFDM), direct sequence spread spectrum (DSSS) communication, a combination of OFDM and DSSS communication, or other schemes can be used to transmit wireless signals in accordance with the 802.11 protocol. The implementation of the 802.11 protocol can be used for sensors, metering, and smart grids. Advantageously, aspects of certain devices implementing the 802.11 protocol may consume less power than devices implementing other wireless protocols, and/or may be used across relatively long distances (eg, about 1 kilometer or longer) ) to transmit wireless signals.

In some implementations, a WLAN includes various devices that are components of an access wireless network. For example, there can be two types of devices: an access point (AP) and a client (also known as a station or "STA"). In general, an AP can be used as a hub or base station for a WLAN, and a STA is used as a user of a WLAN. For example, the STA can be a laptop, a personal digital assistant (PDA), a mobile phone, and the like. In a In an example, a STA connects to an AP via a wireless link that follows WiFi (eg, IEEE 802.11 protocol) to gain general connectivity to the Internet or to other wide area networks. In some implementations, the STA can also be used as an AP.

An access point may also be implemented, or referred to as a Node B, a Radio Network Controller (RNC), an evolved Node B, a Base Station Controller (BSC), a Base Transceiver Station (BTS), a base station (BS), Transceiver Function (TF), Radio Router, Transceiver, Connection Point, or some other terminology.

The station may also be implemented as, or be referred to as, an access terminal (AT), a subscriber station, a subscriber unit, a mobile station, a remote station, a remote terminal, a user terminal, a user agent, a user equipment, User equipment, or some other terminology. In some implementations, the station may include a cellular telephone, a wireless telephone, a Session Initiation Protocol (SIP) telephone, a wireless area loop (WLL) station, a personal digital assistant (PDA), a palm-sized device with wireless connectivity, or a connection to Some other suitable processing device for wireless data machines. Thus, one or more aspects taught herein can be incorporated into a telephone (eg, a cellular or smart phone), a computer (eg, a laptop), a portable communication device, a handset, a portable Computing device (eg, personal data assistant), entertainment device (eg, music or video device, or satellite radio), gaming device or system, global positioning system device, or any other suitable device configured to communicate via wireless media in.

The term "associated with" or "associated" or any variant thereof shall be given the broadest possible meaning within the context of the present disclosure. As an example, when the first device is associated with the second device, it should be understood that the two devices may be directly associated or There may be an intermediate device. For the sake of brevity, the procedure for establishing an association between two devices will be described using a handshake protocol that requires one of these devices to make an "association request" followed by another device to make an "association response" "." Those of ordinary skill in the art to which the invention pertains will appreciate that the handshake protocol may require other signal delivery, such as, for example, to provide for signal delivery for authentication.

Any reference to an element such as "first" or "second" as used herein generally does not limit the number or order of those elements. Rather, these designations are used herein as a convenient way to distinguish between two or more elements or examples of elements. Therefore, the reference to the first element and the second element does not mean that only two elements can be used, or that the first element must be preceded by the second element. In addition, the phrase "at least one" in a list of items refers to any combination of those items, including individual members. As an example, "at least one of A, B, or C" is intended to encompass: A, or B, or C, or any combination thereof (eg, A-B, A-C, B-C, and A-B-C).

As discussed above, certain devices described herein may implement, for example, the 802.11 standard. Such devices (whether used as STAs or APs or other devices) can be used for smart metering or for use in smart grids. Such devices can be used in sensor applications or in home automation. These devices may be used instead or in addition to a health care environment, such as for personal health care. These devices can also be used to monitor to enable extended range of Internet connectivity (for example, for use with hotspots) or for machine-to-machine communication.

FIG. 1 illustrates an example wireless communication system 100 in which various aspects of the present invention may be employed. Wireless communication system 100 can operate in accordance with wireless standards, such as the 802.11 standard. The wireless communication system 100 can include an AP 104 that is associated with an STA (eg, , STA 112, 114, 116, and 118) communication.

Various procedures and methods can be used for transmission between the AP 104 and the STA in the wireless communication system 100. For example, signals can be transmitted and received between the AP 104 and the STA in accordance with OFDM or Orthogonal Frequency Division Multiple Access (OFDMA) techniques. If this is the case, the wireless communication system 100 can be referred to as an OFDM/OFDMA system. Alternatively, signals can be transmitted and received between the AP 104 and the STA in accordance with CDMA techniques. If this is the case, the wireless communication system 100 can be referred to as a CDMA system. In one aspect, the wireless communication system 100 can support MIMO transmission, including single-user MIMO and multi-user MIMO. The wireless communication system 100 can also support multi-user OFDMA and the like.

A communication link that facilitates transmissions from the AP 104 to one or more STAs may be referred to as a downlink (DL) 108, while a communication link that facilitates transmissions from one or more STAs to the AP 104 may be referred to as an uplink. Link (UL) 110. Alternatively, downlink 108 may be referred to as a forward link or a forward channel, and uplink 110 may be referred to as a reverse link or a reverse channel. In some aspects, the DL communication can include unicast or multicast traffic indications.

In some aspects, the AP 104 can suppress adjacent channel interference (ACI) so that the AP 104 can receive UL communications on more than one channel simultaneously without causing significant analog-to-digital conversion (ADC) clipping noise. The AP 104 may improve the suppression of ACI, for example, via having a separate finite impulse response (FIR) filter for each channel or a longer ADC backoff period with a bit width increase.

The AP 104 can act as a base station and provide wireless communication coverage in the Basic Service Area (BSA) 102. A BSA (eg, BSA 102) is an AP (eg, , AP 104) coverage area. The AP 104, along with the STAs associated with the AP 104 and communicating using the AP 104, may be referred to as a Basic Service Set (BSS). It should be noted that the wireless communication system 100 may not have a central AP (e.g., AP 104), but may function as a peer-to-peer network between STAs. Accordingly, the functionality of the AP 104 described herein may alternatively be performed by one or more STAs.

The AP 104 can communicate to other nodes of the wireless communication system 100 (STA) via a communication link (such as the downlink 108) over one or more channels (eg, multiple narrowband channels, each channel including a frequency bandwidth) A beacon signal (or simply "beacon") is transmitted, which can help other nodes (STAs) synchronize their timing with the AP 104, or provide other information or functionality. Such beacons can be transmitted periodically. In one aspect, the period between successive transmissions can be referred to as a hyperframe. The transmission of the beacon can be divided into several groups or intervals. In one aspect, the beacon may include, but is not limited to, information such as: timestamp information for setting a shared clock, peer-to-peer network identifier, device identifier, capability information, hyperframe duration, transmission direction information, Receive direction information, neighbor list, and/or extended neighbor list, some of which are described in more detail below. Thus, a beacon can include both information that is shared (eg, shared) between several devices, as well as information that is specific to a given device.

In some aspects, a STA (e.g., STA 114) may be required to associate with the AP 104 to send and/or receive communications from the AP 104. In one aspect, information for association is included in the beacon broadcast by the AP 104. In order to receive such beacons, STA 114 may perform a wide coverage search, for example, on the coverage area. For example, the search may also be performed by the STA 114 by sweeping the coverage area in a lighthouse manner. Received from the beacon or probe response frame After the information for association, STA 114 may transmit a reference signal to AP 104, such as an association probe or request. In some aspects, the AP 104 can use a backhaul service, for example, to communicate with a larger network, such as the Internet or the Public Switched Telephone Network (PSTN).

In one aspect, AP 104 can include one or more components for performing various functions. For example, the AP 104 can include a TWT component 124 for performing procedures related to TWT operations/schedules. In one aspect, the TWT component referenced herein can be a scheduling component. In one example, TWT component 124 can be configured to receive a first message including a first triggering field from a second wireless device. The first trigger field may indicate whether the first message includes a request for a trigger message to be sent by the first wireless device at the beginning of the TWT service period. The TWT component 124 can be configured to determine the TWT schedule based on the received first message. The TWT component 124 can be configured to transmit a second message to the second wireless device. The second message can include a TWT schedule and a second trigger field based on the determined TWT schedule. The second trigger field may indicate whether the AP 104 will transmit a trigger message at the beginning of the TWT service period (or during the TWT service period). In one aspect, the AP 104 can transmit one or more trigger messages during the TWT service period. The trigger message is such that one or more intended recipients can transmit a message to the transmitter of the trigger message after the determined time period after receiving the trigger message (eg, after the inter-frame space (SIFS)) or The frame is for example a frame for an immediate response to the trigger message, wherein the frames can be sent in single-user (SU) mode or multi-user (MU) mode. In another example, TWT component 124 can be configured to determine a TWT schedule and broadcast a message to one or more wireless devices that can include the determined TWT schedule. The message may include indicating that the TWT schedule is wide Broadcast indicator of the TWT schedule. In yet another example, the TWT component 124 can be configured to receive, from the second wireless device, a message indicating that the second wireless device is to switch to an intent to operate as one of an active mode, a power save mode, or a TWT power save mode . During the TWT power save mode, the second wireless device may enter an awake state during the TWT service period and may enter the snoring state outside of the TWT service period. In this example, TWT component 124 can be configured to store an operational mode associated with the second wireless device and transmit an acknowledgement of the operational mode switch to the second wireless device.

In another aspect, STA 114 can include one or more components for performing various functions. For example, STA 114 may include a TWT component 126 for performing procedures related to TWT operations/scheduling. In one example, TWT component 126 can be configured to transmit a first message including a first trigger field to a second wireless device. The first trigger field may indicate whether the first message includes a request for a trigger message to be sent by the second wireless device at the beginning of the TWT service period or during the TWT service period. The TWT component 126 can be configured to receive a second message from the second wireless device. The second message can include a second trigger field based on the first message, and the second trigger field can indicate whether the second wireless device will transmit the trigger message at the beginning of the TWT service period. In another example, TWT component 126 can be configured to receive a message including a TWT schedule from a second wireless device. The message may include a broadcast indicator indicating that the TWT schedule is a broadcast TWT schedule. The TWT component 126 can be configured to determine one or more TWTs for the first wireless device based on the TWT schedule. In another example, TWT component 126 can be configured to decide whether to switch to an active mode, a power save mode, or a TWT power save mode. STA 114 may enter during the TWT service period during the TWT power save mode The awake state and the snoring state can be entered outside the TWT service period. In this example, TWT component 126 can be configured to transmit a message to the second wireless device based on the decision.

In a Wi-Fi network, an AP often serves multiple STAs within a BSS, as illustrated in FIG. When a STA (e.g., STA 112, 114, 116, 118) has data to transmit or receive, the STA exchanges a UL/DL frame with the AP (e.g., in a multi-user context). The UL/DL frame represents only UL, only DL, or both. In order to perform data transmission or reception, the STA may need to receive a trigger frame from the AP to enable UL/DL exchange. The trigger frame can contain a resource configuration set for UL/DL exchange. In order to receive the trigger frame, the STA may need to be in the awake mode/state for an unknown period of time to wait for the trigger frame. The potentially long and frequent periods of time spent waiting for the trigger frame increase the power consumption of the STA. As such, there is a need to reduce power consumption by reducing the overhead time required for UL/DL frame exchange. One solution is to implement a target wake-up time (TWT) scheduling protocol in which devices (eg, STAs or APs) can be scheduled to sleep and wake up at a particular time to perform UL/DL exchanges, and trigger frames can be queued Cheng Cheng is used for transmission at scheduled or negotiated times. When the STA or AP is not scheduled to wake up to receive the trigger frame, for example, the STA or AP may be in sleep mode (or power save mode) to conserve power. The TWT Scheduling Agreement is beneficial for any scheduling mechanism that can be negotiated between devices or specified by a device to schedule a time interval for exchanging information between two or more devices. Although the above description relates to power consumption aspects, other benefits of scheduling are also apparent to those of ordinary skill in the art to which the present invention pertains, such as contention reduction, hidden node mitigation, interference management, and the like.

To facilitate improved power management protocols and technologies for Wi-Fi networks, three topics are provided below. A first subject relates to claiming a TWT protocol that enables a first wireless device to negotiate with a second wireless device to determine an individual TWT schedule that will indicate when the first wireless device will wake up with the second wireless device communication. A second subject matter relates to a broadcast TWT protocol, wherein a first wireless device, such as, for example, an AP, can determine a TWT schedule for one or more wireless devices (eg, multiple STAs). The TWT schedule in the broadcast TWT protocol may not be negotiated. Instead, other wireless devices that want to communicate with the first wireless device will wake up based on the time provided in the broadcasted TWT schedule. Other wireless devices may also communicate with the first wireless device based on parameters provided by the first wireless device. Both the TWT protocol and the broadcast TWT protocol can be used to use implicit or periodic TWT scheduling (where the first TWT can be explicitly indicated in the message, and the additional TWT can be from the first TWT and other included in the message) Parameters to imply) and explicit or aperiodic TWT schedules (where all TWTs associated with the TWT schedule can be explicitly indicated in the message, and the message about any subsequent TWT can be prior to the subsequent TWT service Delivered during the time period). Finally, the third theme relates to switching between devices in different modes of operation (eg, active mode, passive or power saving mode, and/or TWT power saving mode) to conserve power. In particular, as further described below, the TWT power save mode is an operational mode that is designed to reduce the power consumption of a wireless device operating in accordance with a TWT protocol or schedule.

In one aspect, in order for a wireless device to negotiate and/or transmit a TWT schedule, a signal delivery mechanism that identifies different parameters associated with the TWT schedule is required. Figure 2 provides an exemplary diagram of a TWT element for TWT scheduling. In this exemplary illustration, one or more of the fields shown in the figures may optionally be present depending on the parameters being delivered. As an example, in a TWT setup, the TWT element may not include a TWT group assignment field, an NDP paging field, and/or an OFDMA channel bit mapping field. Other fields may also not exist in the TWT element being exchanged. Other variations of TWT elements consistent with the teachings herein are also provided in subsequent figures.

2 is an exemplary diagram of a TWT element 200 for supporting target wake time and trigger frame scheduling. In order to enable TWT scheduling, the AP and the STA may, for example, use a TWT element to negotiate a target wake-up time, the TWT element providing the necessary signal transfer between the devices for scheduling one or more target wake-up times and their corresponding parameters. When the TWT is negotiated between the first wireless device and the second wireless device (eg, during the TWT setup phase), the TWT element can be transmitted in an individually addressed management frame, the type of the management frame can be an action, The action has no ack, (re)association request/response, probe request response, and so on. In another embodiment, for the broadcast TWT, the TWT element may be transmitted in a broadcast management frame, and the type of the broadcast management frame may be a beacon, or a TIM broadcast frame or the like. In this embodiment, the TWT element provides a non-negotiated schedule (e.g., a broadcast TWT schedule), as further described below.

In one aspect, a STA requesting a TWT schedule may be referred to as a TWT requestor, and an AP responding to the request may be referred to as a TWT responder. In this embodiment, TWT schedules and parameters are provided during the TWT setup phase, and the renegotiation/change of the TWT schedule is notified via an individually addressed frame containing updated TWT parameters. The frames may be the management frame, the control frame, and the field carrying the updated TWT schedule and its associated parameters. Or information frame. In another aspect, two STAs can negotiate a TWT schedule, and one STA can be a TWT requestor and another STA can be a TWT responder.

Referring to FIG. 2, in the TWT element 200, an element ID (eg, 1 octet in length) may indicate that the information element is a TWT element. The length field (eg, 1 octet) may indicate the length of the TWT element 200 from the control field until the end of the TWT element (eg, the end of the OFDMA channel bit map field). The TWT element 200 can include a target wake time field (eg, 8 octets or less), a TWT group assignment field (eg, 9, 3, 2, or 0 octets), nominally minimum The wake-up time field (eg, 1 octet), the TWT wake-up interval mantissa (eg, 2 octets), the TWT channel field (eg, 1 octet), the NDP paging field ( For example, 0 or 4 octets) and/or OFDMA channel bit mapping fields (eg, 0, 1, 2 to 8 octets). In some embodiments, the length field may indicate a plurality of groups or instances carrying the fields (eg, fields from control, request type, ... up to at least one of the OFDMA channel bit map fields) The length of the TWT element of multiple groups, as shown in TWT element 200). In such embodiments the 'TWT element 200 may include TWT parameters for one or more TWT negotiations or indications, as described herein. Each TWT negotiation included in the TWT element can be identified by a unique TWT flow identifier. In some embodiments, the one or more field groups may relate to a non-negotiating TWT (eg, a broadcast TWT), as described further below.

Referring to Figure 2, a request type field (e.g., 2 octets) may indicate the type of TWT request. The request type field can include multiple fields (or sub-fields). These fields may include a TWT request field (eg, 1 bit), a TWT setup command field (eg, 3 bits), a trigger field (eg, 1 bit), Implicit field (eg, 1 bit), stream type (eg, 1 bit), TWT stream identifier (eg, 3 bits), wake interval index (eg, 5 bits), and/or TWT protection Field (for example, 1 bit).

The TWT request field may indicate whether the TWT element 200 represents a request. If the TWT request field has a value of 1, the TWT element 200 can represent a request to initiate a TWT schedule/establishment. Otherwise, if the TWT request field has a value of 0, the TWT element 200 may represent a response to the request to initiate the TWT scheduling/establishment (solicited TWT), the unsolicited TWT (which is used to initiate the TWT scheduling) In response, it is similar in concept to claiming TWT, except that the TWT requestor STA does not send a TWT request requesting the TWT response, and/or a non-negotiable TWT schedule message (or broadcast TWT message). In the case of a non-negotiable TWT (Broadcast TWT), one or more of the above fields (including the TWT request field) may not be present in the TWT element, as discussed further below.

The TWT Setup Command field indicates the type of TWT command. In the TWT request, the type of the TWT command may indicate the following: Request TWT (TWT field contains 0, because TWT responder specifies TWT value; for example, field set to 0), recommended TWT (TWT requester suggests TWT value) ; for example, a field set to 1), and a TWT is required (the TWT requester requests a TWT value; for example, a field set to 2). In the TWT response, the type of TWT command may include a TWT group (TWT group parameters suggested by the TWT responder different from the TWT requester's suggested or required TWT parameters; for example, a field set to 3), accepting TWT (TWT) The responder accepts the TWT request with the indicated TWT parameter; for example, the field set to 4), replaces the TWT (the TWT parameter suggested by the TWT responder to be different from the parameter suggested or required by the TWT requester; for example, set to 5 Field), TWT (TWT) The responder requires a different TWT parameter than the one suggested or requested by the TWT requestor; for example, a field set to 6), or rejects the TWT (the TWT responder rejects the TWT setup; for example, a field set to 7).

In a TWT response, the TWT command may indicate a non-claim request (eg, the TWT responder may require the recipient to follow the TWT schedule included in the element), and broadcast the TWT (the TWT responder is scheduled to be reading the element) Any of the STA's TWT) and so on. In particular, for a non-claim response, the TWT element 200 can include a value specifying the TWT in the TWT command field and the TWT request field can be set to zero. The unsolicited TWT is a frame intended to be addressed individually to a particular STA (while the broadcast TWT can be to multiple STAs and can be carried in a broadcast frame such as, for example, a beacon). In addition, the unsolicited TWT may generally involve a frame exchange in which a STA that receives a non-solicited TWT can respond with an ACK, and the broadcast TWT may not be acknowledged.

In one aspect, a TWT responder that receives a TWT request from a TWT requester and whose TWT wakeup interval has a value equal to the TWT requester's listening interval can use the TWT or reject TWT in the TWT command field to make the TWT request. Respond. In the case of accepting the TWT, the accepting TWT may include the value of the assigned first target beacon transmission time in the TWT wakeup time field and include successive target beacon transmissions in the TWT wake interval and the TWT wake interval index field. The value of the listening interval between times (TBTT). In this aspect, the TWT request/TWT response mechanism can be used by the requesting STA to identify which broadcast frames (e.g., beacon frames) containing the broadcast TWT schedule that it will wake up to receive. In some embodiments, the value of the TWT flow identifier can be reserved for this purpose (negotiation of the TBTT) to distinguish it from the TWT setup that negotiates the TWT schedule. As an example The value 0 or 7 of the TWT stream identifier can be used for this purpose (negotiation of the TBTT). In this aspect, any of these values should not be used for the purpose of negotiating TWT schedules.

If sent in a TWT request, the trigger field may indicate whether the request for the target wake time includes a trigger to be sent by the TWT responder at the beginning of the TWT service period corresponding to the requested TWT schedule or during the TWT service period Frame request. In one aspect, the trigger frame can be transmitted for a duration of a TWT service period corresponding to the scheduled TWT, and one or more trigger frames can be scheduled by the TWT responder. If sent in a TWT response, the trigger field may indicate whether the response to the target wake time request indicates whether one or more trigger frames will be sent at the scheduled TWT. The one or more trigger frames may be sent within a boundary of a TWT service period duration corresponding to the requested TWT schedule. For example, in a TWT request, if the trigger field has a value of 0, the TWT request may not request a trigger frame, but if the trigger field has a value of 1, the TWT request may request a trigger frame. In the TWT response, if the trigger field has a value of 0, no trigger frame will be sent, but if the trigger field has a value of 1, at least one trigger frame can be at or during the scheduled TWT service period. Transfer. In some embodiments, the trigger field may be included in any of the fields in the TWT element or included in any other field of other elements used to provide scheduling information.

The implicit field can indicate whether the next TWT is implicitly calculated or explicitly signaled. For example, if the implicit field has a value of 1, the next TWT is scheduled by the TWT requester (and the TWT responder) in the scheduled TWT (in some embodiments, as identified by the TWT flow identifier) TWT) is implicitly calculated during the TWT service period. For example, the subsequent or next TWT may be determined based on the TWT value of the current TWT service period (as indicated by the TWT value in TWT element 200) plus a multiple of the TWT wake-up interval (eg, TWT period = TWT wake-up interval mantissa * 2 ^{Awaken the interval index} so that the next TWT = current TWT + TWT period ). This allows for periodic scheduling of TWTs, which are simple and flexible for normal operation. In one aspect, a wireless device having an implicit TWT schedule (or protocol) with another wireless device may not generate a block acknowledge TWT frame (BAT) for a subsequent TWT start time associated with the same TWT schedule. Frame, TWT acknowledgement (TACK) frame, or short TWT acknowledgement (STACK) frame. If the implicit field has a value of 0, the next TWT can be explicitly signaled by the TWT responder during the TWT service period. The TWT responder may transmit a BAT or TACK or STACK frame, each of which is a control response frame that may contain the next TWT information.

In some embodiments, the TWT responder may transmit a TWT message frame containing similar TWT information (eg, an action frame or an action without an ack frame). These frames may include a partial timestamp (containing a partial value of the TWT responder's TSF timer) and a next TWT indicating when the next TWT is scheduled (eg, the next TWT is starting at the TWT since the current TWT service period) Scheduled within 2 or 5 seconds).

In another configuration, within the implicit TWT protocol, the TWT responder or TWT requestor may transmit a TWT message frame for rescheduling the next TWT. The TWT information frame may include a response to the requested subfield set to 0 and a next TWT request subfield set to zero. In one aspect, when the TWT information frame is transmitted by the TWT responder, the TWT information frame may indicate non-zero in the next TWT subfield. Next TWT. In another aspect, when the next TWT subfield does not exist and the TWT information frame is transmitted by the TWT requestor, the TWT information frame can indicate the suspension of the TWT protocol (or all TWT protocols). In another aspect, when the next TWT subfield is present and the TWT information frame is transmitted by the TWT requestor, the TWT information frame can indicate the recovery of the previously suspended TWT protocol (or all TWT protocols). In this aspect, the next TWT subfield may include the next TWT selected from the previously negotiated implicit TWT, which is restored at the next TWT. In another embodiment, an indication of any frame transmitted by the TWT requestor to the TWT responder may provide such an indication. As an example, the subfield in the MAC header of the frame transmitted to the TWT responder (eg, in the High Efficiency (HE) variant of the High Delivery (HT) Control field) can be set to 1. Indicates the hang of the TWT protocol, and if set to 0, may indicate recovery of the TWT protocol, or vice versa.

The TWT stream type may indicate the type of interaction at the TWT between the TWT requestor and the TWT responder. In one aspect, the TWT requestor can set the TWT stream type. For example, a value of 0 in the TWT stream type may indicate the announcement of the TWT, where the TWT requester is at the beginning of the TWT SP via a transmit power save poll (PS-Poll) frame or an automatic power save delivery (APSD) trigger frame to The TWT responds to the TWT requester to send a message to the TWT responder to signal the awake state of the TWT requester to announce itself. In one aspect, the TWT responder may not send a frame to the TWT requestor without knowing the power state of the TWT requestor to avoid transmitting to the TWT requestor when the TWT requestor is in a doze state. In another example, a value of 1 in the stream type may indicate a non-declared TWT. In non-announced TWT, the TWT requester may not need to declare itself . The TWT responder can assume that the TWT requestor is awake. The TWT responder may transmit one or more DL frames to the TWT requestor at the TWT without waiting to receive a PS-poll or APSD trigger frame from the TWT requestor.

In another aspect, the TWT responder can set the TWT stream type to 0 to indicate that the TWT responder can transmit a frame to the TWT requestor at the TWT without waiting to receive a PS-poll or APSD trigger from the TWT requestor. frame. In another aspect, the TWT responder can set the TWT flow type to 1 to indicate that the TWT responder cannot transmit a message to the TWT requestor within the TWT service period until the TWT responder has received the PS from the TWT requestor. Poll or APSD trigger frame.

The TWT stream identifier can contain a 3-bit value. In one aspect, for a TWT or a non-claim TWT (eg, a TWT element contained in an individually addressed frame), the TWT flow identifier can be between the same TWT requestor and the TWT responder pair. Other requests made uniquely identify specific information about the TWT request. In some aspects, as previously described, the value of the TWT flow identifier can be reserved for TBTT negotiation purposes (eg, value 0 or value 7) for broadcasting TWT operations. In another aspect, such as for a TWT element carrying information about one or more TWT parameter sets - wherein each TWT parameter set includes information related to one or more TWT SPs that are broadcast TWT SPs (eg, at The broadcast TWT element carried in the broadcast frame (or the general group address frame), the TWT flow identifier may indicate that the TWT service period is responded to during the TWT service period when the trigger field is set to 1. The type of stream that the trigger frame can allow, and the type of stream that is allowed during the TWT SP when the trigger field of the element is set to zero. In one example, a wildcard or random OFDMA allocation access from a non-associated STA may be allowed when the TWT flow identifier is zero. In another example, when TWT knows When the sign is 1, the wildcard or random OFDMA allocation access from the associated STA may be allowed. In another example, when the TWT flow identifier is 2, scheduled access of associated STAs in power save mode may be allowed. In another example, voice traffic may be allowed when the TWT flow identifier is 3. In yet another example, when the TWT stream identifier is 4, video traffic or the like can be allowed. In another example, the value of the TWT flow identifier may indicate that (T) DLS (direct link setup or tunneling direct link setup) traffic is allowed (eg, frames exchanged between STAs (eg, these STAs are not STAs that send trigger frames when the trigger field of the TWT element is set to 1). In some aspects, the above functionality of the TWT stream identifier can be incorporated into different subfields within the TWT element. In other embodiments, such as when a TWT service period that is not a broadcast TWT service period, the TWT Flow Identifier subfield may include uniquely identifying other requests made between the same TWT requestor and the TWT responder pair The value of the specific information associated with the TWT request.

The TWT protection field can indicate whether the TWT is protected or unprotected. The TWT requestor may set the TWT protection field to 1 to request the TWT responder to communicate with one or more restricted access windows (RAW) that limit media access during the TWT service period corresponding to the TWT. The set of TWT service periods corresponding to the requested TWT ID provides protection. In some embodiments, a TWT protection field equal to 1 indicates a request (eg, should) use a Network Allocation Vector (NAV) protection mechanism to protect the request or response of media access during the corresponding TWT service period. If the TWT protection via the RAW allocation is not requested for the corresponding TWT, the TWT requester sets the TWT protection field to zero. For unprotected TWTs, TWT responders can use the NAV protection mechanism (or other similar mechanism) to protect the TWT service period. That is, each STA can include a NAV and can be in it The STA increases the NAV while transmitting and delays the transmission.

In some aspects, a TWT responder that has set the TWT protection field to 1 can send a NAV setup frame roughly at the beginning of the TWT service period corresponding to a particular scheduled TWT. For example, the NAV setup frame can be a CTS message. In these aspects, any STA that receives the frame and is not scheduled to access the media during the TWT service period covered by the NAV duration of the NAV setup frame should set its NAV and not save for a specified amount of time. Take the media. In another aspect, any STA that receives the frame and is scheduled to access media during the TWT service period should ignore the NAV settings specified by the CTS to self (CTS to self) frame (in some embodiments) In the STA, the STA can reset its NAV counter even if these counters have been reset by other frames received.

In one aspect, the NAV or NAV setup frame can be ignored by the STA that is accessing the media during the TWT service period (eg, only for certain frames, such as multiple users or single users, short packet sizes, etc.).

In a TWT request, the TWT wakeup interval may be the average time that the TWT requestor expects to elapse between successive TWT service periods. In a TWT response, the TWT wakeup interval may be the average time that the TWT responder expects to elapse between successive TWT service periods. When transmitted by the TWT requestor, the TWT field may contain a positive integer corresponding to the time the TWT requester requested to wake up, or a value of 0 if the TWT setup command field contains a value corresponding to the command "Request TWT." When transmitted by the TWT responder, the TWT field may contain a value corresponding to the time the TWT responder requested the TWT requestor to wake up. The TWT group assignment field may provide the TWT requester with information about the TWT group to which the TWT requestor is assigned. The nominal minimum wake time field can indicate that the TWT requester is targeting TWT The waking interval period expects the minimum amount of time that the TWT requestor needs to wake up in order to complete the frame exchange associated with the TWT flow identifier, which is the average value that the TWT requestor expects to lapse between successive TWT service periods. . The TWT wake-up interval mantissa can be set to a tail value of 2 based on the TWT wake-up interval value in microseconds.

When transmitted by the TWT requestor, the TWT channel field may contain which channel or channels are intended to be used as temporary primary channels or used for DL during the TWT service period corresponding to the scheduled TWT by the TWT requestor. And/or bit map (or other information) of the channel of the UL MU transmission (MU OFDMA or MIMO). When transmitted by a TWT responder, the TWT channel field may contain an indication of which channels the TWT requestor is allowed to use as one or more temporary channels during the TWT service period or for use in DL and/or UL MU transmissions ( Bit map (or other information) of the channel of MU OFDMA or MIMO). In some embodiments, the channel width of each channel identified by the bits in the TWT channel bit map may be 20 MHz. As such, in one configuration, the TWT channel field may indicate the channel and channel width that the TWT requestor or TWT responder desires to exchange for the frame during the TWT service period. The Single User Entity Layer Convergence Procedure (PLCP) Protocol Data Unit (PPDU) exchanged between devices during the TWT service period may not exceed the negotiated channel width. For example, the PLCP Service Data Unit (PSDU) contained in the MU PPDU may be transmitted in the negotiated channel and may not exceed the width of the negotiated channel. For example, if the negotiated channel has an upper part element equal to one, the MU PSDU exchanged during the TWT service period may be located in the upper 20 MHz of the 160 MHz channel. This configuration enables the STA to dynamically negotiate the operation of the primary channel/width and also indicates which MU resource is preferred. If the STA preferably does not use the signal transmission, the STA may set the TWT channel field to the BSS main channel and set the channel width to the width of the BSS main channel. In another configuration, the TWT channel field can be set to 0 without any indication.

In another aspect, the TWT element 200 can additionally include an OFDMA channel bit map field. In some embodiments, this field may provide a sub-channel bit map of the channel indicated in the TWT channel field. The OFDMA channel bit map field can include a subchannel bit map. In one aspect, the OFDMA channel bit mapping field may contain one or more bit maps (one bit map for each bit set to 1 in the TWT channel field), where each bit map may Associated with a channel indicated in the TWT channel bit map. Each bit map may comprise 8 bits, wherein each bit may identify a subchannel (eg, an OFDMA channel) of a 20 MHz channel of a corresponding bit in the TWT channel bit map, the channel bandwidth of the subchannel being 2.5MHz or less. The number of OFDMA channel bit maps may be equal to the number of non-zero bits in the TWT channel field prior to the OFDMA channel bit map field. The nth OFDMA channel bit map field may be a subchannel map of the nth channel located at the nth position in the TWT channel bit map. Note that for exemplary purposes, some values for channel width and field size are described, but any value can be used to cover different bandwidth, channel, and sub-channel units. As such, greater flexibility can be added by defining an OFDMA channel bit map for each TWT channel indicated in the TWT channel field. The OFDMA channel bit map enables the TWT requestor to indicate in the TWT channel and ultimately in the OFDMA channel bit map a preference for which channel will be allocated during UL/DL multi-user operation. The TWT responder may agree to the TWT requestor's suggestion or suggest a different channel or a subset of the indicated channel in the TWT response.

As discussed above, the TWT element 200 can be transmitted in different types of frames. These frames may be individually addressed frames or group addressed frames. In one aspect, TWT element 200 can be transmitted in an action frame (eg, action ACK or action no ACK frame) or other frame type (such as an association request/response and/or probe request/response frame). In other aspects, the TWT element 200 can be transmitted in a beacon frame or in another management frame. In one aspect, the aforementioned parameters or fields in the TWT element 200 (including TWT, TWT wake-up interval, and TWT channel parameters) can be negotiated between devices during TWT setup, which can be used in response to TWT requesters and TWTs. The individually addressed frames exchanged between the parties are executed. In another aspect, the bit length of each of the fields/subfields described above is provided for exemplary purposes and is not intended to limit the scope of the TWT element 200.

Request TWT scheduling

FIG. 3 includes an exemplary diagram 300 of a wireless network implementing a TWT schedule and an exemplary timing diagram 350 for TWT operations. The illustration illustrates that AP 302 is broadcasting or transmitting within BSS 304. The STAs 306, 308, 310 are within the BSS 304 and are served by the AP 302. STAs 306, 308, 310 and AP 302 may perform TWT scheduling.

In one configuration, STA 306 and AP 302 can negotiate TWT schedules. In this configuration, STA 306 can act as a TWT requestor and initiate a TWT setup with AP 302 (but STA 306 and AP 302 can also swap roles). During TWT setup, STA 306 may transmit a first message 312 (e.g., an action frame, associated frame, or another frame) to AP 302, which may act as a TWT responder. First A message 312 can include a TWT element (eg, the TWT element 200 illustrated in FIG. 2). The first message 312 can include a first element ID that identifies the TWT element 200. The first message 312 can include a first TWT request field having a value of 1 to indicate that the TWT element is a TWT request. If the STA 306 does not request a trigger frame to be sent by the AP 302 at the beginning of the TWT service period or during the TWT service period, the first message 312 may include a first trigger field having a value of zero. In another aspect, if the STA 306 includes a request for a trigger message to be sent by the AP 302 at the beginning of one or more TWT service periods corresponding to the requested TWT schedule or during the one or more TWT service periods The first message may include a first trigger field having a value of one. In another aspect, STA 306 can set the first TWT setup command to "Request TWT" to enable AP 302 to set the TWT for STA 306. In another aspect, STA 306 can set the first TWT setup command to "recommended TWT" to indicate to the AP 302 the suggested/requested TWT. Additionally, STA 306 can set other parameters of the TWT request to indicate other parameters of the request. For example, STA 306 may set the implicit field to 1 to indicate a request for an implicit TWT schedule (eg, a periodic TWT schedule) or set to 0 to indicate an explicit TWT. In one aspect, STA 306 can set the implicit field to 1 and set the NDP paging indicator subfield of the element to zero. The STA 306 may set the flow type to indicate the announcement of the TWT (eg, the TWT requestor intends to first send a frame (eg, PS-Poll or APSD trigger frame) after the trigger frame) or undeclared TWT (eg, TWT) The responder will assume that the STA is in the awake state and send another frame to the STA in the DL). The STA 306 may also indicate in the TWT channel field preferred channels and/or preferred sub-channels for use during the scheduled TWT. In one aspect, STA 306 can further indicate a preferred one in the OFDMA subchannel bit map field within first message 312. OFDMA subchannel.

After receiving the first message 312 from the STA 306, the AP 302 can decide whether to schedule one or more target wake times based on the first message 312. The AP 302 can decide whether to schedule the TWT for the STA 306 based on the number of STAs and/or data traffic within the BSA 304. For example, if the AP 302 detects a large number of STAs (eg, 4) in the BSS 304, the AP 302 can disperse the STA wake-up time, or in the case where the STAs are operating in a single-user (SU) mode. The STA wake-up time is concentrated in the case of multi-user (MU) mode operation to improve channel contention. Conversely, if AP 302 detects a small number of STAs (eg, 1 or 2), AP 302 can closely schedule the target wake-up time so that resources are not wasted and the data rate can be higher. However, AP 302 may wish to improve the power savings of the STA, in which case AP 302 may take into account STA recommendations for TWT allocation, and the like. Similarly, if the AP 302 determines that the media is busy, the AP 302 can disperse the wake-up time of each STA to reduce traffic. If the media is not busy, the AP 302 can closely schedule the target wake up time. In one aspect, if AP 302 determines that the media is not busy and the first message 312 includes the suggested TWT, then AP 302 may decide to accept the TWT requested in the first message 312. In another aspect, if the media is busy, the AP 302 can decide to provide a scheduled TWT that is different from the TWT suggested/requested by the STA 306. In yet another aspect, AP 302 may decide not to schedule the TWT for STA 306. In addition, the AP 302 can allocate multiple STAs with similar requests in the traffic scheduling, mode, quality of service (QoS) requirements, power saving requirements, and feedback modes in the same TWT schedule, so that the AP 302 can use the trigger signal. The MU transmission triggered by the box exchanges traffic with these STAs.

After receiving the first message 312, the AP 302 can be based on the first message. The value of the first trigger field included in 312 determines whether one or more trigger frames are sent to STA 306. If the value of the first trigger field in the first message 312 is 0, the AP 302 may decide not to transmit the trigger frame at the beginning of the TWT service period or during the TWT service period. If the value of the first trigger field in the first message 312 is 1, the AP may be based on media status (eg, traffic volume), number of STAs in the BSA 304, and/or any other TWT request from other STAs. It is decided to send one or more trigger frames at the beginning of one or more TWT service periods or during one or more TWT service periods. The AP 302 can transmit a second message 314 to the STA 306. The second message 314 may be a TWT response to the TWT request (e.g., the first message 312) transmitted by the STA 306 (soliciting TWT setup). In another embodiment, the second message 314 can be a TWT response (not requesting a TWT setup) that can be sent without receiving any TWT request from the STA 306. The second message 314 can include a second trigger field based on the first message 312. The second trigger field may indicate whether the AP 302 will transmit one or more trigger frames at the scheduled TWT of the TWT service period. For example, if the first trigger field in the first message 312 has a value of 0, the second trigger field in the second message 314 may have a value of zero. However, if the first trigger field in the first message 312 has a value of 1, then the AP 302 decides to transmit one or more trigger frames at one or more scheduled TWTs of one or more TWT service periods. In the case, the second trigger field in the second message 314 may have a value of one. The scheduled TWT can be the same as the requested TWT in the first message 312. The scheduled TWT may also be a different TWT as determined by AP 302. In another aspect, the scheduled TWT can be a TWT suggested by the AP 302 such that the STA 306 can suggest a different TWT at a later time (eg, the STA 306 can renegotiate via transmitting another TWT request). Assume that AP 302 schedules one or more During one or more triggering frames during a TWT service period (eg, TWT service period 1, 2), the STA 306 may be able to send data to the AP 302 or from the AP 302 upon receiving the one or more trigger frames. Receive data. Upon receiving the second message 314, the STA 306 can determine whether the second trigger field has a value of 0 or 1. If the second trigger field has a value of 1, the STA 306 may wait for one or more trigger frames to be transmitted at the scheduled TWT and begin UL/DL exchange upon receipt of the trigger frame. Alternatively, even if the trigger field has a value of 1, the negotiation procedure can continue, and the STA 306 can negotiate different schedules by transmitting another message requesting a different TWT to the AP 302 (eg, via a unicast frame). TWT. In addition to negotiating the TWT, other parameters of the TWT operation (eg, TWT wake-up interval, TWT channel, etc.) may also be negotiated. If the second trigger field has a value of 0, the STA 306 can wake up at the scheduled TWT indicated in the second message 314 but does not know what content from the AP 302 is expected during the TWT service period. For example, when the second trigger field has a value of 0, the AP 302 may or may not send a trigger frame at the beginning of the TWT service period (eg, TWT service period 1).

Although STA 306 is a TWT requestor in the foregoing disclosure, in another configuration, AP 302 may be a TWT requestor and STA 306 may be a TWT responder. In yet another configuration, TWT setup and negotiation can occur between two STAs, such as STAs 306, 308. Each STA may perform TWT negotiation with each other when performing device-to-device communication, such as in Tunneling Direct Link Setup (TDLS).

In one aspect, after TWT setup and negotiation, STA 306 can indicate that its intended transmission is triggered by triggering an enabled TWT service period (eg, AP 302 has been set to 1 by the trigger field of the TWT element to be exchanged during TWT setup). The frame is not transmitted to the AP 302 during the TWT service period of the trigger frame unless the frame is requested by the trigger frame from the AP 302. However, if STA 306 has data to transmit outside of the TWT SP, STA 306 may contend for media with respect to other STAs using lower priority Enhanced Distributed Channel Access (EDCA) parameters. The lower priority order can be achieved, for example, via the use of EDCA parameters assigned to the MU STA or TWT STA. Such EDCA parameters may be associated with lower access categories (such as best effort access category (AC_BE) or background access category (AC_BK)), which are associated with higher priority access categories (such as video access categories (AC_VI). ) or the voice access category (AC_VO)) contrasts. In one aspect, the EDCA parameters may include a minimum contention window (CWMIN), a maximum contention window (CWMAX), an inter-array inter-frame spacing number (AIFSN), and/or a transmission opportunity (TXOP). The AC_BE and AC_BK access categories may have less favorable CWMIN, CWMAX, TXOP, and/or AIFSN values for media contention.

Additionally, after the STA 306 negotiates an individual TWT communication period, the STA 306 may remain awake after the TWT start time for at least the adjusted minimum TWT wake-up period (eg, the minimum time duration associated with the TWT service period) to wait for the AP 302 Trigger message 316. In another aspect, when the STA 306 transmits a frame during the triggered enabled TWT service period based on the trigger message 316, the STA 306 can be granted special media access privileges (eg, if the transmitted frame is a trigger message) When the box responds, STA 306 does not contend for media based on EDCA access categories or parameters.

In another aspect, after the STA 306 has negotiated an individual TWT communication period with the AP 302, the STA 306 may not need to read the beacon frame from the AP 302, as the STA 306 may not be expected to follow the broadcast TWT, which will be further s Said.

In essence, this TWT operation provides several benefits. The TWT operation improves channel contention because the STA's wake-up time is either spread out for the SU mode or concentrated in the MU mode for the same period of time as used for the exchange frame. The STA may wake up during the scheduled target wake up time and go to sleep outside of the TWT service period. TWT operation also reduces power consumption because DL/UL frame exchanges have less time to empty.

Additionally, although the aforementioned signal passing is discussed with respect to TWT elements (e.g., TWT element 200 in FIG. 2), similar signal passing can be utilized in the RAW parameter set (RPS). For example, the RPS can include one or more RAW start time fields and a trigger field. The Trigger field in the RPS indicates whether the trigger frame will be transmitted at the beginning of RAW.

Although FIG. 2 and the foregoing description reveal a single TWT in TWT element 200, TWT element 200 may include one or more TWTs by adjusting the value of the length field of TWT element 200. Thus, different TWT flows can be associated with different device target wake-up times. In addition, TWT element 200 can schedule additional TWTs on a periodic basis. For example, when the implicit field as discussed above is set to 1, the next scheduled TWT can be implicitly calculated. The next scheduled TWT can be calculated based on the multiple of the scheduled TWT plus TWT wake-up interval. In this aspect, a scheduled TWT can be associated with a plurality of scheduled TWTs that occur later, and the scheduled TWT can be associated with the corresponding TWT service period and associated with the row that occurs later. A plurality of later TWT service periods of the TWT are associated.

4 is a flow diagram of an example method 400 of requesting a TWT schedule. Method 400 can use a device (eg, AP 302, STA 306, or no such as below) Line device 1302) is executed. Although method 400 is described below with respect to elements of wireless device 1302 of FIG. 13, other components may be used to implement one or more of the steps described herein.

At block 405, the device can transmit a first message including the first trigger field to the second wireless device. The first trigger field may indicate whether the first message includes a request for a trigger message to be sent by the second wireless device at the beginning of the TWT service period. For example, referring to FIG. 3, the device can be STA 306 and the second wireless device can be AP 302. The STA 306 can transmit a first message 312 including the first trigger field to the AP 302. The first trigger field has a value of one to indicate that the first message 312 includes a request for a trigger frame to be sent by the AP 302. In this example, the first trigger field with a value of 1 is (or indicates) a request for a trigger frame. The first message 312 also includes the suggested TWT for the TWT service period. In another example, the requested TWT may be a null value to indicate that no specific time is requested for the TWT and the AP 302 is free to select the scheduled TWT time. In one aspect, the first message 312 can include a TWT channel field that indicates the channel and channel width that the STA 306 can use to communicate with the AP 302 during the TWT service period.

At block 410, the device can receive a second message from the second wireless device. The second message can include a TWT parameter and a second trigger field based on the first message, and the second trigger field can indicate whether the second wireless device will transmit the trigger message at the beginning of the TWT service period. For example, referring to FIG. 3, STA 306 can receive a second message 314 from AP 302. The second message 314 can include one or more fields (TWT parameters) in the TWT element and a second trigger field based on the first message 312. The second trigger field may have a value of one to indicate that the AP 302 will transmit a trigger frame at the scheduled TWT of the TWT service period. In one aspect, scheduled The TWT value is later than the requested TWT value in the first message 312. Moreover, the first message 312 can include an OFDMA bit map indicating one or more OFDMA channels and channel widths associated with the channels indicated in the TWT channel for communicating with the STA 306.

At block 415, the device may determine the TWT schedule based on the received second message. The apparatus may determine the TWT schedule by determining whether the TWT schedule is an implicit TWT schedule or an explicit TWT schedule based on the received second message and determining to associate with the TWT schedule based on the received second message One or more TWTs. For example, referring to FIG. 3, STA 306 can determine whether second message 314 indicates an implicit or explicit TWT schedule based on whether the implicit field is set to 1 (implicit TWT) or 0 (explicit TWT). If the TWT schedule is implicit, the STA 306 may determine to associate with the TWT schedule based on the TWT value included in the second message 314 and based on the TWT wake interval and the wake interval index included in the second message 314. One or more TWTs. Conversely, if the TWT schedule is an explicit TWT schedule, the STA 306 can determine one or more TWTs based on the TWT included in the second message 314.

At block 420, the device may decide whether to transmit to the second wireless device based on the determined TWT schedule. In one configuration, the apparatus can determine whether to transmit if: determining to transmit only when a trigger message is received from the second wireless device during the TWT service period, or to decide to be based on the TWT service period The EDCA parameters associated with the best effort access category (AC_BE) or background access category (AC_BK) are transmitted. For example, referring to FIG. 3, STA 306 can decide whether to transmit to AP 302 based on the determined TWT schedule. If STA 306 wishes to be associated with the determined TWT schedule The UE 306 may wait for a trigger message 316 from the AP 302 before transmitting to the AP 302 during the TWT service period. If STA 306 transmits based on trigger message 316 during the TWT service period, STA 306 may not need to use EDCA to contend for media. If the STA 306 does not receive the trigger message 316, the STA 306 may inhibit transmissions during the TWT service period. In another aspect, if the STA 306 has data to transmit outside of the TWT service period, the STA can transmit based on EDCA contention for lower priority EDCA parameters associated with the best effort access category.

At block 425, the device can receive a trigger message based on the determined TWT schedule. The trigger message can include a cascading indicator that indicates whether the second wireless device will transmit another trigger message after the trigger message in the TWT service period. For example, referring to FIG. 3, STA 306 can receive trigger message 316 based on the determined TWT schedule. Trigger message 316 may include a concatenation indicator set to 0 indicating that AP 302 will not transmit another trigger message in the TWT service period.

At block 430, the device can receive a TWT information message from the second wireless device. The TWT information message may include the next TWT value. For example, referring to FIG. 3, STA 306 can receive a TWT information message from AP 302. In one aspect, the TWT schedule can be an implicit TWT schedule, and the TWT information message can indicate a next TWT that is different from the next TWT implied based on the TWT schedule. In another aspect, the TWT schedule can be an explicit TWT schedule indicated by the second message 314, and the TWT information message can indicate a next TWT value that is different from the TWT value indicated in the second message 314.

At block 435, the device may update the TWT schedule based on the received TWT information message. For example, referring to Figure 3, STA 306 can store a new next The TWT value is associated with the determined TWT schedule.

At block 440, the device can transmit a TWT information message to the second wireless device. The TWT information message may indicate the suspension of the implicit TWT schedule or the recovery of the implicit TWT schedule after the implicit TWT schedule has been suspended. For example, referring to FIG. 3, if the TWT protocol between the STA 306 and the AP 302 is an implicit TWT schedule, and the STA 306 no longer has data to transmit, the STA 306 can transmit a TWT information message to the AP 302 to transmit a notification. The hang of the implicit TWT schedule. Subsequently, when the STA 306 has data to transmit, the STA 306 can transmit a second TWT information message to the AP 302 to indicate the recovery of the suspended TWT schedule.

Although the foregoing example describes a STA as a means of performing the steps in method 400, the AP may also perform the steps in method 400. That is, the AP can be a TWT requestor and the STA can be a TWT responder. In another aspect, each STA can perform device-to-device communication, and one STA can be a TWT requestor and another STA can be a TWT responder.

5 is a flow diagram of an example method 500 of responding to TWT scheduling requests or transmitting information related to TWT scheduling. Method 500 can be performed using a device (e.g., STA 306, AP 302, or wireless device 1302, e.g., below). Although method 500 is described below with respect to elements of wireless device 1302 of FIG. 13, other components may be used to implement one or more of the steps described herein.

At block 505, the device can receive a first message including the first trigger field from the second wireless device. The first trigger field may indicate whether the first message includes a request for a trigger message to be sent by the device at the beginning of the TWT service period. For example, referring to FIG. 3, the device may be an AP 302, and the second wireless device The device can be STA 306. The AP 302 can receive the first message 312 from the STA 306. The first message 312 can include a first trigger field set to 1 to indicate that the first message 312 requests a trigger frame to be sent by the AP 302. The first message 312 can further include a requested TWT for the STA 306.

At block 510, the device may determine the TWT schedule based on the received first message. The device may determine the TWT schedule by: determining whether the first trigger field in the first message includes a request for a trigger message and scheduling the request if the trigger field includes a request for a trigger message One or more TWTs of the wireless device. For example, referring to FIG. 3, the AP 302 can determine whether to send a trigger frame to the STA 306 by deciding that the first message 312 includes a first trigger field set to one and via a TWT scheduled for the STA 306. The scheduled TWT can be for an implicit TWT. In one aspect, AP 302 can determine the TWT based on expected traffic on the wireless medium.

At block 515, the device can transmit a second message to the second wireless device. The second message can include a TWT schedule and a second trigger field based on the determined TWT schedule. The second trigger field may indicate whether the device will transmit a trigger message at the beginning of the TWT service period. In one example, referring to FIG. 3, AP 302 can transmit a second message 314 to STA 306. The second message 314 can include a TWT schedule and a second trigger field having a value of one based on the decision to send a trigger frame to the STA 306. The second message 314 can also indicate that the trigger frame will be transmitted at the scheduled TWT, the scheduled TWT being different from the requested TWT in the first message 312.

At block 520, the device can transmit a trigger message including a cascading indicator. The cascading indicator may indicate whether the device will transmit another trigger message after the trigger message in the TWT service period. For example, referring to FIG. 3, AP 302 can A trigger message 316 including a cascading indicator is transmitted. The cascading indicator can be set to 1 and instruct the AP 302 to transmit another trigger message within the same TWT service period as the trigger message 316.

At block 525, the apparatus can transmit a TWT information message including a next TWT value that is different from all TWT values associated with the TWT schedule included in the second message. For example, referring to FIG. 3, AP 302 can transmit a TWT information message that includes a next TWT value that is different from the TWT value associated with the implicit TWT schedule included in the second message 314. Alternatively, if the TWT schedule is an explicit TWT schedule, AP 302 may transmit a TWT information message that includes a next TWT value that is different from the TWT value associated with the explicit TWT schedule.

At block 530, the device can receive a TWT information message from the second wireless device. The TWT information message may indicate the suspension of the implicit TWT schedule or the recovery of the implicit TWT schedule after the implicit TWT schedule has been suspended. For example, referring to FIG. 3, AP 302 can receive TWT information messages from STAs 306. The TWT information message may indicate that the STA 306 wishes to suspend the implicit TWT schedule. In another example, if the implicit TWT schedule has been suspended, the AP 302 can receive a TWT information message from the STA 306 requesting to resume the implicit TWT schedule.

Although the foregoing examples describe an AP as a means of performing the steps in method 500, the STA may also perform the steps in method 500. That is, the AP can be a TWT requestor and the STA can be a TWT responder. In another aspect, each STA can perform device-to-device communication, and one STA can be a TWT requestor and another STA can be a TWT responder.

Broadcast TWT schedule

6 is an exemplary diagram 600 of a wireless network implementing a broadcast TWT schedule and an exemplary timing diagram 650 for TWT operations. The illustration shows that the AP 602 is broadcasting or transmitting within the BSA 604. STAs 606, 608, 610 are within BSA 604 and are served by AP 602. STAs 606, 608, 610 and AP 602 may perform non-negotiable TWT schedules. In one aspect, the wireless device can optionally negotiate a TBTT during TWT setup.

In a broadcast TWT schedule, delivery of TWT schedules can occur without negotiation between devices. The AP 602 can determine (612) a TWT schedule for communicating with one or more STAs. The AP 602 can determine the TWT schedule by determining that the AP 602 has data to transmit to the STA (eg, the buffer approximating capacity or the buffered unit is available for delivery), and determining that the STA 606, 608, 610 has data to transmit to the AP. 602, and/or determine access to the media available. Based on such buffer status and network conditions, the AP 602 can schedule one or more wake-up times for the STAs 606, 608, 610, and the AP 602 can transmit a trigger frame after the wake-up time to enable communication. The AP 602 can be in the first message 614 (eg, a beacon frame transmitted at or after the scheduled TBTT (in one aspect, the TBTT can be negotiated between wireless devices), or intended to go to one or more STAs The intent of transmitting one or more trigger frames is indicated in the management message), and the first message 614 is received by the STAs 606, 608, 610 at a given time. The TBTT may correspond to the time at which the beacon carrying the TWT element containing the broadcast TWT is scheduled for delivery. The first message 614 can include a TWT element (eg, the TWT element 200 illustrated in Figure 2). The first message 614 can include a first element ID identifying the TWT element 200 and one or more TWT parameter sets, as described below (see, for example, FIG. 16). In the following description, details regarding the signal passing contained in one of these TWT parameter sets are provided. First A message 614 can include a first TWT request field having a value of 0 to indicate that the TWT element is not a request (a TWT request field with a value of 0 indicates that the TWT element is a response or not a request). The first message 614 can indicate one or more scheduled TWTs (either explicitly or implicitly, as discussed above), and the scheduled TWT indicates when the STA should wake up. The one or more scheduled TWTs may not be part of the TWT negotiation; that is, the STAs 606, 608, 610 may not be able to negotiate different scheduled TWTs upon receiving the first message 614. In addition, STAs 606, 608, 610 may also be unable to negotiate other parameters within the TWT element. The one or more scheduled TWTs can be included in a TWT field or other field within the TWT element. The first message 614 can include a first trigger field having a value of one to indicate that one or more trigger frames are to be transmitted during one or more TWT service periods associated with the one or more scheduled TWTs. In other words, the first message 614 can indicate to the STAs that during the TWT service period 1, the STAs can have the scheduled TWT and the trigger frame can be sent at the scheduled TWT. The first message 614 can further indicate that other trigger frames can be sent during a subsequent TWT service period (eg, TWT service period 2). The first message 614 can include a broadcast indicator/sub-field, which can be a control field within the TWT element or a bit included in some other field. In one aspect, the broadcast indicator can be set to 1 to indicate that the first message 614 includes a TWT element with a non-negotiable parameter (eg, the TWT element is a broadcast TWT element). In another aspect, the broadcast indicator can be set to 0 to indicate that the first message 614 includes a TWT element having a negotiable parameter, in which case the TWT element can be associated with the solicited TWT discussed above. In another aspect, the broadcast indicator can establish a value for the command subfield based on the TWT of the request type field. For example, when the TWT setup command subfield is set to a specific value (its The first message 614 is a non-negotiable TWT schedule message if it is any value less than 3) and the TWT request field is set to zero.

When the TWT element is transmitted in the first message 614, the first message 614 can include any of the fields in the TWT element (eg, the TWT element 200 in FIG. 2). The TWT element can include multiple field groups (or TWT parameter sets), and each field group (or TWT parameter) can correspond to a single given scheduled TWT. For example, a TWT element can include a plurality of scheduled TWTs, and each TWT can be associated with a separate TWT field group (eg, request type, target wake time, TWT group assignment field, etc.), as illustrated in FIG. Shown. In another aspect, instead of having two or more field groups within a single TWT element when transmitting a plurality of TWTs within the first message 614, the AP 602 can include a plurality of TWT elements within the first message 614. And each TWT element can include a TWT and associated TWT field group.

Referring to Figure 2, the target wake time field can be 8 octets or less. In one aspect, when AP 602 broadcasts a TWT element in first message 614, AP 602 may decide to use less than 8 octets to indicate the scheduled TWT to save space. In one aspect, assuming that the AP 602 and the STAs 606, 608, 610 have been time synchronized (eg, the beacon carrying the TWT element has carried the TSF timer in the timestamp field), the TWT field may indicate the timing synchronization function. The (TSF) timer will have the least significant octet of the binary value at the scheduled TWT. For example, the TWT field can use 3 least significant bytes to indicate the scheduled TWT. In another aspect, if the AP 602 wishes to provide a lower resolution for the TWT (eg, 10 μs instead of 1 μs, which is originally the resolution of the generic TSF timer of the wireless device), the TWT field may include even fewer bits. yuan. In another state As such, the TWT field can be used to indicate an estimated time at which the trigger frame can be sent or an estimated time at which the scheduled TWT ends relative to the first message 614. For example, if the TWT field has a value of 100 ms, it may indicate that the STA 606, 608, 610 wakes up 100 ms after receiving the last field of the first message 614, or may indicate to the STA 606, 608, 610 at the STA 606, 608 The STA 606, 608, 610 can receive the trigger frame at approximately 100 ms after receiving the entire first message 614. In yet another aspect, the subset of bits in the TWT field can be a shifted subset of bits corresponding to the TSF timer. For example, assume that the TSF timer has 8 bytes. Instead of including the 3 least significant bytes, the subset can be shifted, wherein the TWT field includes the second, third, and fourth least significant bytes of the 8-bit representation of the TSF timer. In some embodiments, bit shifting can occur at the bit level rather than at the byte level.

In another aspect, when the TWT element is included in the first message 614, the TWT wakeup interval may only be valid within the beacon interval following the first message 614 sent at the beginning of the beacon interval. In another aspect, if the first message 614 including the TWT element is a Delivery Traffic Indication Map (DTIM) beacon, the TWT wakeup interval can be valid within the DTIM interval. In another aspect, the TWT wake-up interval can be valid for the duration of the existence of the basic service set. That is, as long as the STA remains associated with the AP, the TWT wake-up interval can be valid.

In another aspect, the TWT element can include a stream identifier indicating one or more types of allowed data streams (eg, a request field in a field group of the TWT element or one or more of the other fields) TWT stream identifier fields). In one configuration, if the TWT flow identifier has a value of 0, the trigger frame associated with the first message 614 can be used for wildcard (or random) access from non-associated STAs. For example, if the non-associated STA wishes to send an association request or probe request to the AP 602, the non-associated STA may wake up at the scheduled TWT indicated in the first message 614 and randomly select the subchannel/subband to use the random backoff or Another collision avoidance mechanism is used to transmit the association request/probing request. If the TWT flow identifier has a value of 1, the trigger frame associated with the first message 614 can be used for wildcard access from the associated STA. For example, if the STA 606 receives the first message 614 on the broadcast, the STA 606 may decide to wake up at one or more of the scheduled TWTs indicated in the first message 614. The STA 606 can receive one or more trigger messages at the one or more scheduled TWTs and transmit uplink data to the AP 602 after receiving the one or more trigger messages. If the TWT flow identifier has a value of 2, the associated STA in power save mode can transmit when the trigger frame is received at the scheduled TWT. If the TWT flow identifier has a value of 3, the associated STA may transmit voice traffic upon receipt of the trigger frame at the scheduled TWT. If the TWT flow identifier has a value of 4, the associated STA may transmit the video traffic upon receiving the trigger frame at the scheduled TWT.

In another configuration, the allowed data types indicated by the TWT flow identifier may include: multi-user OFDMA random access for non-associated STAs, multi-user OFDMA random access for associated STAs, for Multi-user downlink OFDMA scheduling access for TIM STAs, multi-user uplink OFDMA scheduling access for TIM STAs, multi-user uplink MIMO scheduling access for TIM STAs, and / or multi-user downlink MIMO scheduling access for TIM STAs.

In the first category, that is, multi-user OFDMA random access for non-associated STAs, only non-associated STAs may receive the TWT service period by the AP 602. The data is transmitted to the AP 602 after the trigger frame sent at one or more scheduled TWTs during the period. The frame that can be sent by the non-associated STA can include a probe request, an association request, a re-association request, an authentication request, and the like. These frames may be sent in any OFDMA resource following a random access procedure for selecting OFDMA resources for transmission. Regarding the random access procedure, one or more non-associated STAs may randomly select an OFDMA channel for transmitting these frames. Non-associated STAs may coordinate with each other such that if two or more non-associated STAs randomly select the same OFDMA channel, then these non-associated STAs will randomly select another OFDMA channel until each non-associated STA has selected Different OFDMA channels.

In a second category, multi-user OFDMA random access for associated STAs, only associated STAs (STAs 606, 608, 610) may receive TWTs associated with one or more scheduled TWTs by AP 602 The trigger frame sent during the service period is transmitted. The frame that can be sent by the associated STA can be any frame. These frames may be PS-Poll or APSD trigger frames, or any other frame that may be used to indicate to the AP 602 the buffer status and/or transmission preferences of the associated STA. Transmission preferences may include preferred MCS, bandwidth, sub-channels, and the like.

In the third category, multi-user downlink OFDMA scheduled access for TIM STAs, only its associated identifier (AID) is included in the beacon message (eg, first message 614) carrying the TWT element. The STA corresponding to the value 1 in the traffic information map (TIM) element bit map may receive the data from the AP 602 after receiving the trigger frame transmitted at the scheduled TWT or during the TWT service period. In some embodiments, instead of transmitting a trigger frame, the AP 602 can transmit downlink data to the STA in multi-user OFDMA. The AP 602 may also indicate in the trigger frame an uplink OFDMA resource associated with each STA to be used within the same scheduled TWT or TWT service period.

In the fourth category, that is, the multi-user uplink OFDMA scheduled access for the TIM STA, only the AID and the TIM element bit included in the beacon message carrying the TWT element (for example, the first message 614) The STA corresponding to the value 1 in the mapping may transmit the data after receiving the trigger frame transmitted at the scheduled TWT during the TWT service period. The AP 602 may indicate that the TWT service period is allocated for uplink only transmission. The AP 602 may decide to transmit downlink data to the STA after terminating the exchange enabled by the first trigger.

In the fifth and sixth categories, namely multi-user uplink MIMO scheduling access for TIM STAs and multi-user downlink MIMO scheduling access for TIM STAs, the AID bits are in the TIM element. The AP and STA in the middle 1 can use multi-user MIMO to exchange downlink and uplink data. As indicated previously in the other fields, not only the TWT Flow Identifier field may indicate the allowed data category. For example, the TWT Wake Interval Index subfield can be overloaded to replace the TWT Flow Identifier field to signal the type of data allowed for the notification.

In another aspect, the flow identifier can be used to indicate a traffic class or traffic identifier (TID) identifying the traffic type that is allowed to be exchanged during the TWT service period. For example, as previously discussed, a flow identifier can be used to indicate the type of flow that can be allowed in response to a trigger frame. Traffic types can include voice and video traffic.

When the STA 606 receives the first message 614, the STA 606 may decide whether to be associated with one or more scheduled TWTs included in the first message 614. One or more TWT service periods are awakened during the service period. The STA 606 may decide whether to wake up during the one or more TWT service periods by deciding whether the STA 606 has data to transmit to the AP 602 and via determining whether the STA 606 is expected to receive data from the AP 602.

During a TWT service period in which the triggering frame is expected to be associated with the scheduled TWT included in the first message 614, the STAs 606, 608, 610 may not contend for accessing the media for data transmission. Instead, STAs 606, 608, 610 may await receipt of a trigger frame 616 sent by AP 602 that enables STAs 606, 608, 610 to transmit data frames. The data frame can be sent in single-user or multi-user mode.

Assuming that STA 606 decides to participate in the TWT schedule, STA 606 may transmit data 618 to AP 602 or receive data 618 from AP 602 upon receipt of trigger frame 616. Data 618 can be transmitted during the TWT service period. The STA that failed to transmit after the trigger frame 616 (e.g., STA 606) may transmit after the end of the TWT service period. The transmission may be a retransmission of a failed transmission or it may be a resource configuration request.

7 is a flow diagram of an example method 700 of broadcasting a TWT schedule. Method 700 can be performed using a device (e.g., AP 602, STA 606, or wireless device 1302, such as hereinafter). Although method 700 is described below with respect to elements of wireless device 1302 of FIG. 13, other components may be used to implement one or more of the steps described herein.

At block 705, the device may determine TWT schedules for other wireless devices. The device may determine the TWT schedule by determining one or more fields within the TWT element. In one aspect, the device can determine the state of the network (eg, expected The number of wireless devices communicating with the device and/or the amount of traffic on the wireless medium). For example, referring to FIG. 6, AP 602 can determine a broadcast TWT schedule for one or more STAs. The broadcast schedule can include non-negotiable TWT parameters for communicating with the AP 602. The AP 602 can determine the broadcast TWT schedule by deciding whether to use an implicit TWT schedule or an explicit TWT schedule. In addition, one or more TWTs are associated with a broadcast TWT schedule. The AP 602 can determine any of the other fields or parameters associated with the TWT element (eg, the TWT element 200).

At block 710, the device can broadcast a message including the TWT schedule to a plurality of wireless devices. The message may include a broadcast indicator indicating that the TWT schedule is a broadcast TWT schedule. In one aspect, the message can include a trigger field that indicates whether the device will transmit a trigger message at the beginning of the TWT service period or during the TWT service period. The message may further include a TWT flow identifier indicating the type of data stream allowed during the TWT service period. For example, referring to FIG. 6, the device may be an AP 602. The AP 602 can broadcast a first message 614 that includes a TWT schedule. The broadcast bit in the first message 614 can be set to 1, indicating that the TWT schedule is a broadcast TWT. The first message 614 may also include a trigger field set to 1 to indicate that the AP 602 will transmit a trigger frame during the TWT service period. The first message 614 can include an implicit field set to zero to indicate that the TWT schedule is an explicit TWT schedule. The first message 614 can further include four scheduled TWTs associated with the four TWT parameter sets. In one aspect, the first message 614 can include a repeat indicator indicating that the TWT schedule is valid for 5 TWT service periods. In another aspect, the first message 614 can include a TWT protection indicator set to 1 to indicate that the message exchanged between the STA 606 and the AP 602 has an RTS message from the transmitting party and a CTS message from the recipient.

At block 715, the device can transmit a trigger message based on the TWT schedule. The trigger message can include a cascading indicator indicating whether the device will transmit an additional trigger message in the TWT service period. For example, referring to FIG. 6, AP 602 can transmit trigger frame 616. In one aspect, for MU operations, the AP 602 can transmit multiple trigger frames during the TWT service period to enable multiple STAs to transmit to the AP 602. As such, the AP 602 can transmit a trigger frame 616 addressed to the STAs 606, 608 with a cascading indicator set to 1 to indicate that the AP 302 will transmit another trigger frame within the same TWT service period. The STAs 606, 608 can transmit uplink data to the AP 602 based on the trigger frame 616. The AP 602 can then transmit another trigger frame addressed to the STAs 608, 610 to indicate resources for another uplink transmission.

At 720, the device can transmit a TWT information message to the second wireless device. The TWT information message may indicate the suspension of the implicit TWT schedule or the recovery of the implicit TWT schedule after the implicit TWT schedule has been suspended. For example, referring to FIG. 6, if the broadcast TWT schedule indicated in the first message 614 is an implicit TWT schedule, the AP 602 may transmit a TWT information message to the STAs 606, 608, 610 to indicate the suspension of the broadcast TWT schedule. Start. In one aspect, implicit TWT scheduling can be suspended based on network conditions, lack of data for transmission, or to save power. In another aspect, to resume the previously suspended implicit TWT schedule, the AP 602 can transmit a TWT information message to the STAs 606, 608, 610 to indicate the recovery of the suspended TWT schedule.

At block 725, the device can transmit a TWT information message to the second wireless device. The TWT information message may indicate a scheduled TWT that is different from the TWT in the broadcasted message. For example, referring to FIG. 6, AP 602 can provide STAs 606, 608, 610 transmits a TWT information message indicating a scheduled TWT that is different from the TWT implied in the implicit TWT schedule. In another example, if the TWT schedule is an explicit TWT schedule, the TWT information message can include a scheduled TWT that is different than the TWT indicated in the explicit TWT schedule in the first message 614.

Although the foregoing example provides an AP broadcast TWT schedule, the STA may also broadcast TWT schedules to the AP or another STA.

8 is a flow diagram of an example method 800 for communicating based on a broadcast TWT schedule. Method 500 can be performed using a device (e.g., STA 606, or wireless device 1302, such as hereinafter). Although method 800 is described below with respect to elements of wireless device 1302 of FIG. 13, other components may be used to implement one or more of the steps described herein.

At block 805, the device can receive a message including the TWT schedule from the second wireless device. The message may include a broadcast indicator indicating that the TWT schedule is a broadcast TWT schedule. For example, referring to FIG. 6, the device can be STA 606. The STA 606 can receive the first message 614 including the TWT schedule from the AP 602. The first message 614 can include a broadcast indicator set to 1 to indicate that the TWT schedule is a broadcast schedule. The first message 614 can include a trigger field set to 1 to indicate that the AP 602 will transmit the trigger frame 616 at the beginning of the TWT service period or during the TWT service period. The first message 614 can further include a TWT flow identifier set to 1 to indicate that there is no constraint on the type of frame or message during the broadcast TWT service period.

At block 810, the device can determine one or more TWTs for the device based on the TWT schedule. The device may determine one or more TWTs by determining whether the TWT schedule is an implicit TWT schedule or an explicit TWT schedule. If the TWT The schedule is an implicit TWT schedule, and the device can determine one or more TWTs based on the first TWT indicated in the TWT schedule. The subsequent TWT may be determined based on the TWT wake-up interval mantissa and the wake-up interval index, which may be indicated in the message or pre-configured at the device. If the TWT schedule is an explicit TWT schedule, the device may extract one or more TWTs from the received message. For example, referring to FIG. 6, STA 606 may determine whether the TWT schedule indicated in first message 614 is an implicit TWT schedule or an explicit TWT schedule, and calculate or extract a TWT value based on the decision.

At block 815, the device can receive the trigger message based on the determined one or more TWTs. For example, referring to FIG. 6, STA 606 can receive trigger frame 616 based on the determined one or more TWTs.

At block 820, the device may decide to transmit to the second wireless device upon receipt of the trigger message from the second wireless device during the TWT service period. For example, referring to FIG. 6, STA 606 may determine to be directed to the AP via the decision material available for transmission to the AP 602, via the decision that the data may be transmitted during the TWT service period, and via the decision that the trigger frame 616 has been received from the AP 602. 602 transmits.

At block 825, the apparatus may decide to transmit to the second wireless device based on the EDCA parameters associated with AC_BE or AC_BK outside of the TWT service period. For example, referring to FIG. 6, STA 606 may determine that data is available for transmission to AP 602 and that no trigger frame has been received from AP 602 or that the material cannot wait for the next available TWT service period. As such, STA 606 may decide to transfer to AP 602 via contention access based on lower priority EDCA access class AC_BE.

At block 830, the device can receive a TWT information message from the second wireless device. The TWT information message may indicate the suspension of the implicit TWT schedule or the recovery of the implicit TWT schedule after the implicit TWT schedule has been suspended. For example, referring to FIG. 6, STA 606 can receive a TWT information message from AP 602 indicating the suspension of an implicit TWT schedule or the suspension of a suspended implicit TWT schedule.

At block 835, the device can receive a TWT information message from the second wireless device. The TWT information message may indicate a scheduled TWT that is different from the TWT in the received message. For example, referring to FIG. 6, STA 606 can receive a TWT information message from AP 602, and the TWT information message can indicate a scheduled TWT that is different than the TWT indicated in first message 614.

TWT power saving mode

In the future IEEE 802.11 standard, an AP may send a trigger frame to request an uplink data frame from one or more STAs in a multi-user mode and/or transmit downlink information to one or more STAs. frame. In general, the trigger frame can be generated by the AP at any time. A STA intending to transmit uplink data may have to stay awake to receive a trigger frame intended for the STA. However, staying awake during periods when no trigger frame is to be sent may result in unnecessary power consumption, as the AP may schedule multiple trigger frames for multiple STAs. One way to address this issue is to allow the STA and the AP to negotiate a target trigger transmission time, as previously discussed, so that the STA knows when the trigger frame will arrive. These transmission times may be negotiated (solicited TWT or unsolicited TWT) to be periodic or aperiodic, or may not be non-negotiated (broadcast TWT).

In some examples, the scheduled TWT can be based on being made by an AP or STA The mode indication changes dynamically between the periodic mode and the aperiodic mode. The mode indication can be indicated by an implicit field contained in the message carrying the trigger field. The implicit field can be set to 1 to indicate that the mode is periodic and can be set to 0 to indicate that the mode is aperiodic.

When the mode is aperiodic, the next TWT can explicitly signal the notification by the TWT responder (eg, AP). In one aspect, the TWT responder can transmit a TACK/STACK/BAT or TWT message frame to signal the next TWT. These frames may contain the value of the next TWT and may include a TWT flow identifier identifying the TWT flow corresponding to the next TWT in the case of the TWT protocol. The TWT requestor may request a mode change of the next TWT by transmitting a TACK/STACK/BAT frame carrying the next TWT field. The TWT requestor can confirm the new schedule in the subsequent frame (TACK/STACK/BAT, etc.) containing the next TWT field.

When the mode is periodic, the TWT responder does not provide the next TWT during the current TWT service period. Instead, the TWT requestor implicitly calculates the next TWT based on the TWT value of the current TWT service period plus the value of the negotiated TWT wake-up interval as specified in the negotiation period of the TWT for each TWT service period. During periodic TWT (ie, implicit TWT), any of these devices may request rescheduling of parameters for a given TWT flow. This can be performed via a request or response with updated parameters at any time during the TWT service period. The request or response in this case may have a dialog token equal to the value of the dialog exchange exchanged during the TWT setup. Similarly, the request or response may include a TWT flow identifier for which to request rescheduling. The request can be confirmed, an alternative can be provided, or the request can be rejected. In a certain In some embodiments, the response for renegotiating parameters may be non-negotiable and effective from the next TWT.

In some cases, even if the AP and the STA may have protocols (eg, scheduling) for exchanging uplink/downlink frames after the triggering of the periodic mode (eg, during the TWT service period) However, there may be a time period in which one of the STAs does not expect traffic for a long period of time. As such, there is a need for the STA to indicate that the agreed schedule is suspended for a given amount of time. In this way, the STA does not need to wake up during certain TWT service periods in which the STA has no uplink data to transmit to the AP. Also in some cases, the AP does not plan to use the full TWT service period to send a trigger frame, and as such, the AP may wish to indicate an early termination of a given TWT service period.

9 is an exemplary diagram 900 of a wireless network supporting a TWT scheduled power save mode and an exemplary timing diagram 950 for TWT operation. The illustration shows that the AP 902 is broadcasting or transmitting within the BSA 904. STAs 906, 908, 910 are within BSA 904 and are served by AP 902.

In one configuration, STA 906 (or any other STA) may be in one of two different power states: an awake state and a hiccup (or sleep) state. In the awake state, the STA is full power. In the doze state, the STA 906 may be unable to transmit or receive data and may consume very little power. The STA 906 can switch between an awake state and a doze state based on a power management mode - an active mode (AM) and a power save (PS) mode. In active mode, STA 906 can be in a sustained wake state. In PS mode, STA 906 is in a doze state and can enter an awake state to receive selected beacons, receive group addressed transmissions after certain received beacon frames, and schedule multicast services with retry During the service period of the time period (GCR-SP), the transmission is received, transmitted, or waiting for a response to the transmitted PS-poll frame or receiving a contention free (CF) data transmission.

To change the power management mode, the STA 906 can notify the AP 902 via a successful frame exchange initiated by the STA 906. The frame may be a management frame, an extension frame, or a data frame, and may include an acknowledgment (ACK) or block acknowledgment (Block ACK) frame from the AP 902. The frame may include a power management subfield in the frame control field, and the power management subfield may indicate the power that the STA 906 can adopt after successfully completing the entire frame exchange (eg, frame and acknowledgement). Management mode. The STA 906 may not be able to change the power management mode using a frame exchange that does not receive an ACK or a block acknowledgment frame from the AP 902 or a Block ACK Request (BlockACKReq) frame. When the AP 902 receives a message from the STA 906 indicating a mode change, the AP 902 can store the new power management mode and transmit an ACK frame to the STA 906.

If STA 906 has negotiated a TWT with AP 902, STA 906 may be in active mode at each scheduled TWT and for some time thereafter (eg, during a TWT service period associated with the scheduled TWT) Even if the STA 906 does not have uplink data to transmit. This may be a burden for the STA 906 that has no more information to transmit to the AP 902. In one aspect, the STA 906 can use TWT power save mode to conserve power.

In the TWT power save mode, the STA 906 may be in a doze state and may enter an awake state at the beginning of the scheduled TWT and may remain in the awake state for a duration of one or more TWT service periods associated with the scheduled TWT . In another aspect, STA 906 can stay awake for less than the TWT service period. Small time duration. However, during times outside of the TWT service period, the STA 906 may enter a doze state. In the TWT power save mode, if there is an additional TWT service period associated with the scheduled TWT and the STA 906 has no more data to transmit (and/or is not expected to receive any data from the AP 902), then the STA 906 may wish to enter a sleep state (eg, switch to power save mode) during the remaining TWT service periods. For this situation, a power save mode switching signal transfer is required, as described below. In one configuration, when the STA 906 is in the TWT power save mode, the STA 906 may additionally continue to meet the requirements of the existing PS mode (eg, enter an awake state to receive the selected beacon, after some received beacon frame) Receiving a group-addressed transmission, receiving a transmission, transmitting, or waiting for a response or receiving contention for a transmitted PS-poll frame during a service period with a scheduled multi-cast service period (GCR-SP) with retry (CF) data transmission). In another configuration, the STA 906 may not meet the requirements of the PS mode and simply remain in a sleep state.

9, when the STA 906 decides (912) to switch to the TWT power save mode, the STA 906 can transmit a message 914 (e.g., a frame) to the AP 902 to indicate that the STA 906 intends to switch from the active mode to the TWT power save mode or Switch from PS mode to TWT power save mode. Message 914 may include an indicator or field (e.g., an End of Service Period (EOSP) field) indicating the power management mode that STA 906 will adopt after successfully completing the message/frame exchange. For example, if the field is set to 1 (eg, EOSP is 1), message 914 may indicate that STA 906 is switching from TWT power save mode to PS mode. If the field is set to 0, message 914 indicates that STA 906 is not switching from TWT power save mode to PS mode. In some embodiments, any field in the frame exchanged with the AP 902 can be sent. The number is passed to notify the new status. In other embodiments, certain frame types may be used to signal the delivery of notifications to or from the TWT power save mode. In one aspect, STA 906 can only switch between active mode and TWT power save mode, or only between PS mode and TWT power save mode. In this aspect, the transition between states can be signaled by the 1-bit power management subfield in message 914. When the power management subfield has 1 bit, the STA 906 may be able to switch between two modes - active mode and TWT power save mode, or TWT power save mode and PS mode. In another aspect, the power management subfield can have 2 bits, which will enable the STA 906 to switch between all three modes. For example, "00" can indicate PS mode, "01" can represent TWT PS mode, and "10" can indicate active mode.

Upon receiving the message 914, the AP 902 can store the power management mode to which the STA 906 intends to switch. For example, if message 914 indicates that STA 906 intends to switch to TWT power save mode, then AP 902 may store information indicating that STA 906 is in TWT power save mode. In this mode, the AP 902 may be aware that no data is to be transmitted to the STA 906 outside of the TWT service period in which the STA 906 is awake. The AP 902 can then transmit an acknowledgement message 916 to the STA 906 to instruct the AP 902 to receive the message 914.

In one aspect, AP 902 can transmit a second message 918 to STA 906. The second message 918 can use the EOSP field to instruct the STA 906 to switch from the TWT power save mode to the PS mode. For example, AP 902 can set the EOSP field to 1 to instruct STA 906 to switch from TWT power save mode to PS mode. The AP 902 can also transmit a second message 918 to other STAs 908, 910.

However, once STA 906 enters PS mode, because STA 906 may The sleep state is for an extended period of time, so the AP 902 may be unable to instruct the STA 906 to switch back to the TWT power save mode by transmitting a frame intended to indicate the STA 906 handover mode. However, STA 906 may request a handover back to the TWT power save mode via a handover request (eg, a request similar to message 914). For example, STA 906 can transmit another message to AP 902. The other message may include an EOSP field set to 0 to instruct the STA 906 to request a switch back to the TWT power save mode. Otherwise, STA 906 may set EOSP to 1 to indicate that STA 906 does not wish to switch back to TWT power save mode. In some embodiments, the power management subfield can be used for similar signal delivery. In some embodiments, the power management switch can be performed via a TWT request or a non-solicited TWT response. In some embodiments, the AP 902 can selectively indicate that certain STAs are switched from the PS mode by initiating a bit in the traffic indication mapping element that can be included in the message frame (eg, the second message 918). To TWT power saving mode. For example, the second message 918 can be a beacon message and the second message 918 can include a TIM element that includes a bit map. The STAs 906, 908, 910 can receive the second message 918 and decide whether to switch to the TWT power save mode based on each AID location of the bit map. For example, if the location in the bit map corresponding to the AID of the STA 906 has a value of 0, the STA 906 can switch to the TWT power save mode. In some embodiments, the validity of the new mode is limited to the beacon interval following the beacon frame (eg, the second message 918).

10 is a flow diagram of an example method 1000 of switching to or leaving a TWT power save mode. Method 1000 can be performed using a device (e.g., STA 906, AP 902, or wireless device 1302, such as hereinafter). Although the method 1000 is described below with respect to the elements of the wireless device 1302 of Figure 13, it can be used Other components implement one or more of the steps described herein.

At block 1005, the device can receive an indication from the second wireless device that the device switches to or switches away from the TWT power save mode. For example, referring to FIG. 9, the device may be STA 906, and STA 906 may receive a message from AP 902 instructing STA 906 to switch to TWT power save mode. In one aspect, the message can include an EOSP set to 1 to indicate that the TWT service period is ending and no more material will be transmitted.

At block 1010, the device may decide whether to switch to an active mode, a power save mode, or a TWT power save mode. In the TWT power save mode, the device may enter an awake state during the TWT service period and enter a doze state outside of the TWT service period. In one configuration, the device can decide whether to switch by deciding whether additional data is available for transmission or reception by the device. In another configuration, the device may decide whether to switch modes by receiving a QoS message from the second wireless device and by determining whether the QoS message includes an EOSP indicator set to 0 or 1. In another configuration, the device can determine whether to receive a trigger message from the second wireless device and determine whether the trigger message includes a cascading indicator set to 0 or 1 and whether to determine whether the trigger message is intended for the device Switch mode. For example, referring to FIG. 9, STA 906 may decide to switch to TWT power save mode based on a decision to receive a QoS message indicating EOSP set to 1 from AP 902.

At block 1015, the device can transmit a message to the second wireless device based on the decision. For example, referring to FIG. 9, STA 906 can transmit message 914 to AP 902 based on the decision to switch to TWT power save mode. Message 914 may include a power management field set to 1 to indicate that STA 906 wishes to switch to TWT power save mode. formula.

At block 1020, the device can determine the mode of the second wireless device. In one configuration, the device can determine the mode by receiving a second message including a responder mode indicator from the second wireless device. The device may determine whether the responder mode indicator indicates whether the second wireless device is in a doze state outside of the TWT service period. If so, the second wireless device can be in the TWT power save mode; otherwise, the second wireless device can be in the active mode. In another configuration, the device can determine the mode by receiving a trigger message from the second wireless device and by determining whether the trigger message includes a resource configuration for any wireless device. For example, referring to FIG. 9, STA 906 can receive a message from AP 902 that includes a responder PM mode indicator (eg, in a control field). The responder PM mode indicator can be set to 1 to indicate that the AP 902 is in the TWT power save mode.

At block 1025, the device can receive a second message including a traffic indication map from the second wireless device. The traffic indication map may indicate an operational mode selected by the first wireless device. For example, STA 906 can receive a message including an TIM from AP 902. The TIM may include a bit associated with the AID of the STA 906. If the bit is set to 1, the STA 906 can expect to receive the data and can enter the TWT power save mode or the active mode, but if the bit is set to 0, the STA 906 can anticipate receiving data and can enter power savings. mode.

11 is a flow diagram of an example signal transfer method 1100 for switching to a TWT power save mode. Method 1100 can be performed using a device (eg, AP 902, STA 906, or wireless device 1302, eg, below). Although method 1100 is described below with respect to elements of wireless device 1302 of FIG. 13, other components may be used to implement one or more of the steps described herein.

At block 1105, the apparatus can receive a message from the second wireless device indicating that the second wireless device is to switch to an intent to operate as one of an active mode, a power save mode, or a TWT power save mode. During the TWT power save mode, the second wireless device may enter an awake state during the TWT service period and enter a doze state outside of the TWT service period. For example, referring to FIG. 9, the device may be an AP 902. The AP 902 may receive a message 914 from the STA 906 indicating that the STA 906 intends to switch to the TWT power save mode, during which the STA 906 may enter an awake state during the TWT service period and may enter outside of the TWT service period Snoring state.

At block 1110, the device can store an operational mode associated with the second wireless device. For example, referring to FIG. 9, AP 902 can store information indicating that STA 906 is in TWT power save mode.

At block 1115, the device may transmit an acknowledgement of the operational mode switch to the second wireless device. For example, referring to FIG. 9, AP 902 can transmit acknowledgement information 916 to instruct AP 902 to acknowledge the handover of STA 906 to TWT power save mode.

At 1120, the device can transmit a QoS message including an EOSP indicator set to 1 to instruct the second wireless device to switch the mode of operation. For example, referring to FIG. 9, AP 902 can transmit a QoS frame with an EOSP indicator set to 1 to STA 906, which instructs STA 906 to switch the mode of operation.

At 1125, the device can transmit a responder mode indicator indicating whether the first wireless device is in a doze state outside of the TWT service period. For example, referring to FIG. 9, the AP 902 can transmit a message including a responder PM mode indicator in the control field, and the responder PM mode indicator can be set to 1 to indicate that the AP 902 is in the TWT power save mode.

At 1130, the device can transmit a trigger message with unassigned resources to indicate that the device will enter a doze state. For example, referring to FIG. 9, AP 902 can transmit a trigger frame with unassigned resources to the STA indicating that AP 902 will enter a doze state.

At 1135, the device can transmit a traffic indication map indicating an operational mode selected by the second wireless device. For example, referring to FIG. 9, AP 902 can transmit a TIM with a bit set to 1 corresponding to the AID of STA 906 indicating that STA 906 should be in an active mode.

At 1140, the apparatus can transmit an indication to the second wireless device that the second wireless device switches to or switches away from the TWT power save mode. For example, referring to FIG. 9, AP 902 can transmit a second message 918 to instruct STA 906 to switch from an active mode to a TWT power save mode.

Additionally, during the TWT service period, the AP may transmit one or more trigger frames and/or may not wish to always use the full duration of the TWT service period. For example, an AP may wish to send a trigger frame (eg, a PS-poll or resource request) for polling feedback of one or more STAs, a trigger frame for UL data delivery from one or more STAs, for A trigger frame for exchanging DL data with one or more STAs, and the like. In order to allow the STA to decide to terminate the expected number of frames or the early termination of the TWT service period, the AP may indicate in the TWT element itself the number of trigger frames that the AP intends to transmit. In another embodiment, the AP may indicate that the AP has more trigger frames to transmit in any of the frames transmitted by the AP during the TWT service period. For example, the AP may indicate that the AP intends to transmit at least another trigger frame after the current frame by setting the bit in the frame currently being transmitted to 1. In an embodiment, the frame may be a trigger frame, and the bit may be a frame control. More data fields in the field, newly defined fields, or APs can rely on EOSP field signal delivery. In another embodiment, the frame may be any other frame sent by the AP. For example, the bit may be a power management field in the frame control field of the frame transmitted by the AP during the TWT service period. In another embodiment, any other field or value can be used for this purpose. For example, the EOSP field can be set to 1 to indicate that the AP is not intending to transmit another (trigger) frame during the TWT service period. In another example, more data fields, or other fields as described above, can be set to 0 to indicate that the AP intends to transmit another (trigger) frame during the TWT service period. Thus, the STA that received the indication (eg, there are no more trigger frames during the TWT service period) may go to sleep earlier than the end of the scheduled TWT service period. The STAs addressed by the trigger frame may not go to sleep because they are scheduled to transmit the UL frame in response to the trigger frame. The remaining STAs that go to sleep in the remainder of the scheduled TWT service period may wake up in other TWTs (next TWT) as negotiated or indicated by the AP in a previous exchange or schedule.

12 is an exemplary diagram of a request type field 1200 within a TWT element for broadcasting a TWT. Referring to FIG. 12, the request type field may include a TWT stream identifier subfield, which may have various values as indicated in FIG. The TWT Flow Identifier subfield may contain a 3-bit value that uniquely identifies the particular information associated with the TWT request with other requests made between the same TWT requesting STA and the TWT responding STA pair. In the broadcast TWT mode, there may be no concept of STA pairs. As such, the TWT Flow Identifier subfield can be used to specify different flows (or traffic classes) that are allowed for broadcast TWTs in the TWT service period.

Referring to FIG. 12, in one aspect, when the TWT stream ID is set to 0, then There may be no constraints on the type of framework that can be exchanged during the scheduled TWT service period specified by the TWT parameter set of the broadcast TWT containing the TWT Flow ID. In another aspect, when the TWT stream ID is set to 1, only frames containing feedback and/or management information (eg, PS-Poll, CQI, buffer status, probe information, actions, etc.) can be exchanged. . In this aspect, the trigger frame may not contain RUs (eg, resource elements) for random access. In another aspect, when the TWT stream ID is set to 2, only frames containing feedback and/or management information can be exchanged (eg, PS-Poll, CQI, buffer status, sounding information, actions, pre- Related frames, etc.). In this aspect, the trigger frame can include at least one RU (or resource element) for random access. In one aspect, when the TWT stream ID is set to 1 or 2, the QoS frame can also be exchanged. In yet another aspect, when the TWT stream ID is set to 3, the exchangable quality of service is constrained (eg, a short frame having a payload of a particular AC/type of less than 256 or 128 bytes, etc.) .

In another aspect, the TWT Flow Identifier subfield may indicate a transmission from any device (eg, an AP or STA that may or may not be associated with a device transmitting a frame containing the TWT element). For example, when the TWT stream ID is set to 4 (or some other value), the transmission is not expected (ie, the blanking service period). In addition to illustrating the STA conserving power, this feature can also be used to cause the STA to enter or remain in sleep mode to reserve time for another device to communicate. This means that the device transmitting the TWT element is aware of other devices (not associated with it) that are intended to be transmitted to one or more other devices during the scheduled time period (in some embodiments, by these other devices via scheduling information) It is also beneficial when the exchange mechanism is similar to the knowledge provided by TWT elements or other means.

Although the TWT Flow ID value is provided in the TWT Flow Identifier subfield, similar values for the stream type used to identify the broadcast TWT may be provided in other fields within the TWT element or by one or more other devices. The other parts of the frame that the device transmits are provided.

FIG. 13 illustrates a method 1300 of broadcasting a TWT for multiple TWTs. Referring to FIG. 13, the AP may indicate a broadcast target trigger (awake) time in an information element (eg, a TWT element) included in the beacon 1305 or any other management frame. In one aspect, the TWT mode provided by the element can be periodic. As an example, in this aspect, the TWT element can include a TWT field and a TWT wake-up interval that enables periodic mode. In another aspect, the mode can be aperiodic. In this aspect, the TWT element can signal the transmission of multiple aperiodic TWTs per beacon interval. This may allow for greater flexibility in the beacon interval, within the DTIM interval, or through the target wake-up time throughout the operational lifetime.

In order to enable multiple aperiodic TWTs per beacon interval, etc., more than one TWT parameter set may be included in the beacon frame or another frame. In one aspect, more than one TWT information element can be included in the beacon. In another aspect, the TWT element can be modified such that the TWT element can carry multiple TWT parameter sets. For example, a TWT element can carry multiple occurrences of a field following the control field of the element. The TWT parameter set may include one or more of the following fields: request type, TWT, TWT group, nominal minimum wake time, TWT wake interval mantissa, TWT channel, NDP paging, and the like. The length of the TWT element provides signal passing for determining its content. As an example, if each TWT parameter set (the length of which is based on the signal contained therein) is 7 bytes, if the TWT element contains 2 TWT parameter sets, the length field of the TWT element may be equal to 15-bit tuple (7*2 plus a control field for a byte), and so on.

Figure 14 illustrates a method 1400 of employing a cascading field (previously referred to as more material, power management, etc.) in a trigger frame within a TWT service period. Referring to FIG. 14, the AP may notify the STA that is expected to wake up at the TWT service period via the beacon 1405 or the TWT information element included in the general frame. In one aspect, the AP can overestimate the number of STAs that will be allocated during the TWT service period. This is because in the broadcast TWT, only a part of the STAs may be served during the TWT service period (or expect to wake up, or be able to successfully receive the TWT carrying frame) (this is for the TWT (or the TWT mentioned earlier) ) is also possible). As such, the AP may send a trigger frame 1410 at the beginning of the TWT service period. Trigger block 1410 may include a list of Association Identifiers (AIDs) (or other identifiers assigned by the AP) for the STA to enable uplink transmissions. That is, each AID can identify a STA. The trigger frame 1410 can include a cascading subfield indicating whether an additional trigger frame follows the trigger frame 1410 in the TWT service period. For example, if the cascading subfield is set to 1, another trigger frame (eg, second trigger frame 1415) follows the trigger frame 1410. However, if the cascading subfield is set to 0, no trigger frame will follow the trigger frame 1410 during the same TWT service period.

The non-AP STA that received the trigger frame 1410 has several options. In response to a trigger frame 1410 intended for the STA (e.g., STAs 1, 2, 3, 4), the STA may transmit an uplink frame. If the cascading field is set to 1 and the trigger frame 1410 is not intended for the STA, the STA (e.g., STA 5, 6, 7) may remain awake to receive, for example, the second trigger frame 1415 (although the STA may Within the duration of the UL PPDU transmitted as a response to the current trigger frame Go to sleep). In another aspect, if the trigger frame 1410 is not intended for the STA and the cascade field of the trigger frame 1410 is set to 0, the STA can enter a sleep mode (or a doze state). After receiving an uplink transmission from each STA, the AP may transmit an acknowledgment (eg, multiple block acknowledgments (MBA)). In another aspect, the STA may contend for independent access to the media after the frame exchange enabled by the trigger frame with a cascading field equal to zero. In some embodiments, the STA should not begin to contend for accessing the media after receiving a trigger frame containing a cascading field equal to one.

15 is an exemplary diagram of a TWT group assignment field 1500 within a TWT element of a broadcast TWT for multiple STAs. Referring to FIG. 15, the TWT group ID subfield may have 7 bits (eg, corresponding to B0 to B6), and the zero offset existence subfield may have 1 bit (eg, corresponding to B7), the group zero offset The field may have 48 or 0 bits (eg, corresponding to B8 to B55), the TWT unit subfield may have 4 bits (eg, corresponding to B56 to B59), and the TWT offset subfield may have 12 bits. Meta (for example, corresponding to B60 to B71). Within the TWT offset subfield, there may be a start AID subfield, an end AID subfield, and a reserved subfield. The start AID subfield may have 5 bits, the end AID subfield may have 5 bits, and the reserved subfield may have 2 bits. Although FIG. 15 illustrates the start AID and end AID subfields, other IDs assigned by the AP other than the AID may also be used.

The TWT group assignment field can be negotiated and used by the AP to allocate TWTs for STAs within the group. For each STA within the group identified by the TWT group ID, the TWT group assignment subfield may provide information about the staggered (offset) TWT within the group itself. In one aspect, the TWT group assignment subfield can be staggered at the AP. A group of multiple STAs are used when UL single-user transmission. In another aspect, the TWT group assignment subfield can be used to designate the STA group to wake up at a TWT. For example, the TWT group assignment field may identify the range of STAs that are scheduled to wake up at the designated TWT.

In one aspect, when the trigger field within the request type field is set to 1, the TWT group ID can specify the AID of each STA belonging to the group that will wake up at the particular TWT (or another ID assigned by the AP) The 7 most significant digits. The TWT unit may be reserved, for example, to indicate that no uplink transmission is required to be offset from the first TWT, as the uplink transmission may be triggered after XIFS, where the XIFS may be Inter-Short Interframe Space (SIFS) or Point Coordination Function (PCF) Interframe Space (PIFS). The TWT offset field may contain the 5 least significant bits of the start AID of the group and the 5 least significant bits of the end AID of the group.

In another aspect, when the zero offset presence is set to 1, the group zero offset field can specify the TWT if the TWT wake time field does not exist. In another aspect, for a basic broadcast TWT scenario, the TIM element can also provide a list of STAs to be polled by the trigger. In one aspect, a broadcast TWT supporting multiple STAs can improve signal delivery for identifying STA groups for multi-user operations in TWT elements.

FIG. 16 illustrates an exemplary diagram of a second TWT element format 1600. Referring to Figure 16, TWT element 1605 can include an element ID field (e.g., 1 octet in length), a length field (e.g., 1 octet in length), and a control field (e.g., length) 1 octet), request type field (for example, 2 octets in length), target wake time field (for example, length 2, 4, 6 or 8 octets), TWT Group assignment field (optional), nominal minimum The wake-up time field (for example, 1 octet in length), the TWT wake-up interval field (for example, 2 octets in length), the TWT channel (optional), and/or the NDP paging bar Bit (also optional). The TWT set may be formed by one or more of a request type field, a target wake time field, a TWT group assignment field, a nominal minimum wake time field, a TWT wake interval field, and/or a TWT channel field. Or equivalent TWT parameter set. The TWT element 1605 can have one or more TWT parameter sets that can be used to indicate different TWT service periods.

The control field may have multiple sub-fields, such as an NDP paging indicator sub-field (eg, 1 bit), a broadcast sub-field (eg, 1 bit), a responder PM (negative mode) mode sub-field ( For example, 1 bit), and/or reserved subfields (eg, 5 bits). The broadcast bit may be used to indicate whether the TWT element 1605 is a broadcast TWT (where the target wake time may not be negotiated between the AP and the STA), or whether the TWT element 1605 is requesting a TWT (which may be between the AP and the STA or The target wakeup time is negotiated between the STA and another STA). For example, when the broadcast bit is set to 1, then the TWT element 1605 can be a broadcast TWT, and when the broadcast bit is set to 0, then the TWT element 1605 can be a request TWT. Broadcast bits can also be referred to as non-negotiable indications. In one configuration, the responder PM mode subfield may indicate that the TWT responder may be in a dozing state outside of the TWT SP (eg, for a broadcast TWT, the TWT responder may be an AP). In one option, the AP may set the Responder PM mode subfield to 1 to indicate that the AP may be in a doze outside of the TWTSP. Alternatively, if the AP is not allowed to enter the power save mode, the AP may set the Responder PM mode subfield to zero. In another configuration, the AP may indicate that the AP is in power saving by transmitting one or more trigger frames. Mode, the trigger frame may include a resource configuration (eg, a resource element) that is not assigned to any STA during a TWT service period in which the AP intends to enter the power save mode.

The length field may indicate the length of the TWT element 1605 and may be used to determine the number of TWT parameter sets within the TWT element 1605. For example, if the length field indicates that the TWT element 1605 is an 8-bit tuple, the TWT element 1605 can have a TWT parameter set (eg, a 7-bit field for a TWT parameter set and a control field for a byte) Bit). If the length field indicates a 15-byte, the TWT element 1605 can have two TWT parameter sets. As such, the length field can indicate the number of TWT sets.

The request type field may have one or more of the following subfields, such as: repeat subfield, trigger subfield, reserved subfield, stream type subfield, TWT stream identifier subfield, wake up Interval index subfield, and/or TWT protection subfield. In one aspect, the request type field can be 1 byte long and includes a repeating subfield (eg, 2 bits), a trigger subfield (eg, 1 bit), a TWT stream identifier subfield ( For example, 3-bit), and the wake-up interval index (for example, 2 bits). In another aspect, the request type field may not include an awake interval index sub-field, the value of which may be pre-configured within the device (eg, the device may have a pre-configured value of 10 for the wake-up interval index field). If the TWT is periodic (eg, the TWT set may include a non-zero value of the TWT wake-up interval field), the repeating subfield may indicate the number of valid TWT service periods associated with the TWT specified by the TWT parameter set Subtract 1 from it. "Subtract 1" takes into account the TWT indicated in the target wake time field. For example, if the TWT is valid for 6 TWT service periods, the repeat field can be set to 5. In one aspect, if the TWT wake-up interval subfield is set to 0, then the TWT is not periodic. Conversely, if the TWT interval mantissa subfield has a non-zero value, the TWT may be periodic and may repeat as many times as specified by the value indicated in the repeating subfield. The TWT wake interval may be determined based on the product of the TWT wake interval and the power of the value indicated in the wake interval index ( period = TWT wake interval x 2 ^{wake interval index} ). In another aspect, a repeating subfield set to zero may indicate a non-periodic TWT.

The trigger subfield indicates whether a trigger (eg, a trigger frame) will be sent at the beginning of the target wake time specified by the TWT set. In such an embodiment, the field can be set to one. Otherwise, it can be set to 0 to indicate that there will be no trigger frame sent at the beginning of the target wake time. The TWT Flow Identifier subfield indicates the type of data stream that is expected during the TWT service period specified by the TWT set. The TWT Flow Identifier subfield may be associated with the value indicated in FIG. The target wake time subfield may include a TSF timer (as included in the timestamp field of the beacon frame transmitted at that time) in the first TWT (if periodic) or a unique TWT (if not) Periodically) 2 least significant bytes of values to have. In another aspect, the target wake time subfield may include a shifted subset of the 2 least significant bytes of the TSF timer. For example, assuming that the TSF timer has 8 bytes, instead of including 2 least significant bytes, the subset can be shifted, wherein the TWT field includes the second and the second of the 8-bit representation of the TSF timer. The third least significant byte, in this case, the time resolution may not be, say, 1 microsecond, but 256 microseconds. By doing so, the 2-byte TWT field can indicate a larger time value (while losing some resolution). In some embodiments, bit shifting can occur at the bit level rather than at the byte level.

The TWT Protection subfield may indicate that the TWT service period specified by the corresponding TWT parameter set may be protected or unprotected (or required to be protected or unprotected in the TWT request). In one aspect, when the TWT protection subfield is set to 0, the TWT service period can be unprotected. In another aspect, when the TWT protection subfield is set to 1, the subfield may indicate that the STA associated with the AP transmitting the TWT element 1605 and having read the frame carrying the TWT element 1605 is in the corresponding TWT set. The access media should not be contending for the specified duration of the TWT service period indicated in . In another embodiment, only STAs having traffic allowed by the AP to be delivered during the TWT service period may contend for accessing the media. For example, when the AP sends a TWT element indicating that there is no trigger frame at the beginning of the TWT and the TWT is to announce the TWT (eg, the STA should send a frame to the AP), then only certain types of traffic (eg, PS-) The STAs of the Poll or U-APSD Trigger can access the media to transmit their frames. In another aspect, when the TWT protection subfield is set to 1, the subfield may indicate that the STA that is not associated with the AP and has read the frame carrying the TWT element 1605 is in the TWT service(s) Access to the media should not be contending for the specified duration of the time period. An AP that sets the TWT protection subfield to one may also indicate that the AP intends to transmit a NAV setup frame at the beginning of the TWT service period to protect at least a portion of the duration of the TWT service period(s). If the TWT element 1605 contains a list of STAs that the TWT element 1605 intends to go to, the intended STA receiver of the TWT element 1605 may discard the NAV setup frame sent by the AP at the beginning of the TWT service period and access the medium, Or transmit immediately for any frame sent by the AP (for example, in SIFS time). In another aspect, an AP with the TWT protection subfield set to 1 can indicate that there are multiple users (MUs) prior to the scheduled data exchange during the TWT SP. Request to send (RTS) or clear to send (CTS) message exchange.

In one aspect, another AP that has set up another BSS and within the range of the AP that transmitted the TWT element 1605 (eg, can read the frame carrying the TWT element 1605) may be during the TWT service period(s) Resources are not allocated to any STA associated with the other AP to minimize the risk of inter-BSS collisions.

In the foregoing description, methods, functions, protocols, and techniques described with respect to STAs may also be applied to an AP, and vice versa, unless explicitly stated.

17 illustrates an example functional block diagram of a wireless device 1702 that can perform TWT scheduling within the wireless communication system 100 of FIG. Wireless device 1702 is an example of a device that can be configured to implement the various methods described herein. For example, wireless device 1702 can include one of APs 104, 302, 602, 902 or one of STAs 112, 114, 116, 118, 306, 308, 310, 606, 608, 610, 906, 908, 910.

Wireless device 1702 can include a processor 1704 that controls the operation of wireless device 1702. Processor 1704 may also be referred to as a central processing unit (CPU). Memory 1706, which may include both read-only memory (ROM) and random access memory (RAM), may provide instructions and data to processor 1704. A portion of memory 1706 may also include non-volatile random access memory (NVRAM). The processor 1704 typically performs logical and arithmetic operations based on program instructions stored within the memory 1706. Instructions in memory 1706 may be executable (eg, by processor 1704) to implement the methods described herein.

Processor 1704 can include or be a component of a processing system implemented with one or more processors. One or more processors can use general purpose microprocessing , microcontroller, digital signal processor (DSP), field programmable gate array (FPGA), programmable logic device (PLD), controller, state machine, strobe logic, individual hardware components, dedicated hard A finite state machine, or any combination of any other suitable entity capable of performing calculations or other manipulations on information.

The processing system can also include machine readable media for storing software. Software should be interpreted broadly to mean any type of instruction, whether it be called software, firmware, mediation software, microcode, hardware description language, or otherwise. Instructions may include code (eg, in raw code format, binary code format, executable code format, or any other suitable code format). These instructions, when executed by the one or more processors, cause the processing system to perform the various functions described herein.

The wireless device 1702 can also include a housing 1708, and the wireless device 1702 can include a transmitter 1710 and/or a receiver 1712 to allow data transfer and reception between the wireless device 1702 and the remote device. Transmitter 1710 and receiver 1712 can be combined into transceiver 1714. Antenna 1716 can be attached to housing 1708 and electrically coupled to transceiver 1714. The wireless device 1702 can also include multiple transmitters, multiple receivers, multiple transceivers, and/or multiple antennas.

The wireless device 1702 can also include a signal detector 1718 that can be used to detect and quantize the level of signals received by the transceiver 1714 or the receiver 1712. Signal detector 1718 can detect signals such as total energy, energy per symbol per symbol, power spectral density, and other signals. Wireless device 1702 can also include a digital signal processor (DSP) 1720 for processing signals. The DSP 1720 can be configured to generate a packet for transmission. In some aspects, the packet can include a PPDU.

In some aspects, the wireless device 1702 can further include a user interface 1722. User interface 1722 can include a keypad, a microphone, a speaker, and/or a display. User interface 1722 can include any component or component that conveys information to and/or receives input from a user of wireless device 1702.

When the wireless device 1702 is implemented as a STA (e.g., STA 306, 606, 906) or an AP (e.g., AP 302, 602, 902), the wireless device 1702 can also include a TWT component 1724.

In one configuration, the wireless device 1702 can be a TWT requestor requesting a TWT. In such a configuration, TWT component 1724 can be configured to transmit a first message including a first trigger field to a second wireless device (eg, a TWT responder). The first trigger field may indicate whether the first message includes a request for a trigger message to be sent by the second wireless device at the beginning of the TWT service period. The TWT component 1724 can be configured to receive the second message from the second wireless device. The second message can include a second trigger field based on the first message. The second trigger field may indicate whether the second wireless device will transmit a trigger message at the beginning of the TWT service period. In one aspect, the first message can include the requested TWT, the first trigger field can be set to 1, and the first message can request a trigger message to be sent at the requested TWT. In another aspect, the second message can include the scheduled TWT, the second trigger field can be set to 1, and the second message can indicate that the second wireless device can transmit the trigger message at the scheduled TWT. In another aspect, the scheduled TWT can be different than the requested TWT included in the first message. In one embodiment, TWT component 1724 can be configured to determine a TWT schedule based on the received second message and decide whether to transmit to the second wireless device based on the determined TWT schedule. In this embodiment, the TWT component 1724 can be configured to operate via Determining a TWT schedule: determining whether the TWT schedule is an implicit TWT schedule or an explicit TWT schedule based on the received second message and determining one or more associated with the TWT schedule based on the received second message TWT. In another embodiment, the TWT component 1724 can be configured to decide whether to transmit if: to decide to transmit when receiving a trigger message from the second wireless device during the TWT service period, or to decide to serve in the TWT The timeout is based on the EDCA parameters associated with AC_BE or AC_BK. In another aspect, TWT component 1724 can decide to transmit during the TWT service period based on the received trigger message, and the transmission may not be based on EDCA contention. In another embodiment, the TWT component 1724 can be configured to receive a trigger message based on the determined TWT schedule. The trigger message can include a cascading indicator that indicates whether the second wireless device will transmit another trigger message after the trigger message in the TWT service period. In another embodiment, the TWT component 1724 can be configured to receive a TWT information message from the second wireless device, and the TWT information message can include the next TWT value. The TWT component 1724 can be configured to update the TWT schedule based on the received TWT information message. In another embodiment, the TWT schedule can be an implicit TWT schedule, and the TWT component 1724 can be configured to transmit a TWT information message to the second wireless device. The TWT information message may indicate the suspension of the implicit TWT schedule or the recovery of the implicit TWT schedule after the implicit TWT schedule has been suspended. In another aspect, the first message can include a TWT channel indicator that indicates the channel and channel width that the TWT component 1724 can use to communicate with the second wireless device during the TWT service period. In another aspect, the first message can include an OFDMA bit map indicating one or more OFDMA channels and channel widths that will be used to communicate with the second wireless device.

In another configuration, the wireless device 1702 can be a TWT responder requesting a TWT. In this configuration, TWT component 1724 can be configured to receive a first message including a first triggering field from a second wireless device. The first trigger field may indicate whether the first message includes a request for a trigger message to be sent by the wireless device 1702 at the beginning of the TWT service period. The TWT component 1724 can be configured to determine the TWT schedule based on the received first message. The TWT component 1724 can be configured to transmit a second message to the second wireless device. The second message can include a TWT schedule and a second trigger field based on the determined TWT schedule. The second trigger field may indicate whether the wireless device 1702 can transmit the trigger message at the beginning of the TWT service period. In one aspect, the first message can include the requested TWT, the first trigger field can be set to 1, and the first message can request a trigger message to be sent at the requested TWT. In another aspect, the second message can include the scheduled TWT, the second trigger field can be set to 1, and the second message can indicate that the wireless device 1702 will transmit the trigger message at the scheduled TWT. In another aspect, the scheduled TWT can be different than the requested TWT included in the first message. In an embodiment, the TWT component 1724 can be configured to determine the TWT schedule via the following operations: determining whether the first trigger field includes a request for a trigger message and including a request for a trigger message in the first trigger field The lower schedule is for one or more TWTs of the second wireless device. In another embodiment, TWT component 1724 can be configured to transmit a TWT information message that includes a next TWT value that is different than all TWT values associated with the TWT schedule included in the second message. In another embodiment, the TWT schedule can be an implicit TWT schedule, and the TWT component 1724 can be configured to receive the TWT information message from the second wireless device. The TWT information message may indicate that the implicit TWT schedule is suspended or that the implicit TWT schedule has been suspended. After the recovery of the implicit TWT schedule. In another aspect, the second message can include a TWT channel indicator indicating a channel and channel width to be used for communication between the wireless device 1702 and the second wireless device during the TWT service period. In another embodiment, the TWT component 1724 can be configured to transmit a trigger message including a cascading indicator. The cascading indicator may indicate whether the wireless device 1702 will transmit another trigger message after the trigger message in the TWT service period. In another aspect, the second message can include a TWT protection indicator indicating whether there is an RTS and CTS message exchange prior to the message exchanged with the wireless device 1702 based on the TWT schedule.

In another configuration, the wireless device 1702 can broadcast the TWT to other wireless devices. In this configuration, TWT component 1724 can be configured to determine TWT schedules and broadcast messages including TWT schedules to other wireless devices. The message may include a broadcast indicator indicating that the TWT schedule is a broadcast TWT schedule. In one aspect, the broadcast TWT schedule can include non-negotiable TWT parameters for communicating between the wireless device 1702 and at least one of the wireless devices. In another aspect, the message can further include a trigger field that indicates whether the wireless device 1702 will transmit the trigger message at the beginning of the TWT service period. In another aspect, the message can include a TWT Flow Identifier field that indicates the type of data stream allowed during the TWT service period. In another aspect, the allowed data stream types can include MU OFDMA random access for wireless devices not associated with wireless device 1702, MU OFDMA random access for wireless devices associated with wireless device 1702. Taking MU DL OFDMA scheduled access for the wireless device indicated in the TIM, MU UL OFDMA scheduled access for the wireless device indicated in the TIM, for the wireless device indicated in the TIM MU UL MIMO scheduled access, MU DL MIMO scheduled access for wireless devices indicated in the TIM. In another aspect, the TWT Flow Identifier field may indicate one of the following allowed data stream types: unconstrained with the type of message to be exchanged with the wireless device 1702, and may exchange information including feedback or management information with the wireless device 1702. The message and the trigger message from the wireless device 1702 does not include a resource element for random access, the message containing the feedback information or management information can be exchanged with the wireless device 1702 and the trigger message from the wireless device 1702 includes resources for random access. The element may exchange information containing the quality of service information with the wireless device 1702 or may not communicate traffic to or from the wireless device 1702. In another aspect, the TWT schedule can be an implicit TWT schedule or an explicit TWT schedule. In another aspect, the TWT schedule can be an explicit TWT schedule, the TWT schedule can include one or more TWT parameter sets, and each TWT parameter set can correspond to the scheduled TWT. In another embodiment, the TWT schedule can be an implicit TWT schedule, and the TWT component 1724 can be configured to transmit a TWT information message to the second wireless device. The TWT information message may indicate the suspension of the implicit TWT schedule or the recovery of the implicit TWT schedule after the implicit TWT schedule has been suspended. In another embodiment, the TWT component 1724 can be configured to transmit a TWT information message to the second wireless device, and the TWT information message can indicate a different location than the scheduled TWT in the TWT schedule in the broadcasted message. Schedule TWT. In another embodiment, the TWT component 1724 can be configured to transmit a trigger message based on the TWT schedule. The trigger message can include a cascading indicator that indicates whether the wireless device 1702 will transmit an additional trigger message in the TWT service period. In another aspect, the message can include a TWT group assignment field, and the TWT group assignment field can include identifying a wireless device group scheduled to wake up at a TWT during a TWT service period The range of identifiers. In another aspect, the message can include a repeat indicator, and the repeat indicator can indicate the number of TWT service periods in which the scheduled TWT indicated in the message is valid. In another aspect, the message can include a TWT protection indicator indicating whether there is an RTS and CTS message exchange prior to the message exchanged with the wireless device 1702 based on the TWT schedule.

In another configuration, the wireless device 1702 can receive the broadcast TWT and decide whether to join the broadcast TWT. In this configuration, TWT component 1724 can be configured to receive a message including a TWT schedule from a second wireless device. The message may include a broadcast indicator indicating that the TWT schedule is a broadcast TWT schedule. The TWT component 1724 can be configured to determine one or more TWTs for the wireless device 1702 based on the TWT schedule. In one aspect, the broadcast TWT schedule can include non-negotiable TWT parameters for communicating between the wireless device 1702 and the second wireless device. In another aspect, the message can include a trigger field that indicates whether the second wireless device will transmit a trigger message at the beginning of the TWT service period. In another aspect, the message can include a TWT Flow Identifier field that indicates the type of data stream allowed during the TWT service period. In another aspect, the TWT flow identifier field may indicate that the type of the message to be exchanged with the second wireless device is unconstrained, and the message including the feedback information or the management information may be exchanged with the second wireless device and is from the first The trigger message of the second wireless device does not include a resource element for random access, and may exchange information including feedback information or management information with the second wireless device, and the trigger message from the second wireless device includes a resource element for random access. The message containing the quality of service information may be exchanged with the second wireless device or may not be communicated to or from the second wireless device. In another aspect, the TWT schedule can be an implicit TWT schedule or an explicit TWT schedule. In another state As such, the TWT schedule can be an explicit TWT schedule, the TWT schedule can include one or more TWT parameter sets, and each TWT parameter set can correspond to the scheduled TWT. In another aspect, the TWT schedule can be an implicit TWT schedule, and the TWT component 1724 can be configured to receive the TWT information message from the second wireless device. The TWT information message may indicate the suspension of the implicit TWT schedule or the recovery of the implicit TWT schedule after the implicit TWT schedule has been suspended. In another embodiment, the TWT component 1724 can be configured to receive a TWT information message from the second wireless device. The TWT information message may indicate a scheduled TWT that is different from the TWT in the received message. In another aspect, the message can include a repeat indicator, and the repeat indicator can indicate the number of TWT service periods in which the scheduled TWT indicated in the message is valid. In another embodiment, the TWT component 1724 can be configured to receive a trigger message based on the determined one or more TWTs. In another aspect, the trigger message can include a cascading indicator that indicates whether the second wireless device will transmit an additional trigger message after the trigger message in the TWT service period. In another embodiment, the TWT component 1724 can be configured to decide to transmit to the second wireless device upon receipt of the trigger message from the second wireless device during the TWT service period, and to decide to be based outside of the TWT service period The EDCA parameters associated with AC_BE or AC_BK are transmitted to the second wireless device.

In another configuration, the wireless device 1702 can be a TWT requestor that decides whether to switch the mode of operation. In this configuration, TWT component 1724 can be configured to decide whether to switch to an active mode, a power save mode, or a TWT power save mode. During the TWT power save mode, the wireless device 1702 may enter an awake state during the TWT service period and may enter the doze state outside of the TWT service period. TWT component 1724 can be configured to be based on the decision to the second wireless The device transmits a message. In another aspect, the TWT service period can be identified based on the TWT schedule associated with the wireless device 1702. In another aspect, the message can include a power management indicator that indicates a mode to which the wireless device 1702 intends to switch. In another embodiment, the TWT component 1724 can be configured to receive an indication from the second wireless device that the wireless device 1702 is instructed to switch to or switch away from the TWT power save mode. In another aspect, the indication can include an EOSP indicator set to one. In another embodiment, the TWT component 1724 can be configured to decide whether to switch if: whether there is additional material for transmission or reception, and receiving QoS with the EOSP indicator set to 1 from the second wireless device. The message, or a trigger message with a cascading indicator set to 0, is received from the second wireless device (where the trigger message is not intended to go to the wireless device 1702). In another embodiment, the TWT component 1724 can be configured to determine the mode of the second wireless device. In another embodiment, the TWT component 1724 can be configured to determine a mode of the second wireless device via receiving a second message from the second wireless device, wherein the second message can include indicating that the second wireless device is outside of the TWT service period Whether the responder mode indicator is in a hiccup state. The decision on the mode of the second wireless device can be based on the responder mode indicator. In another embodiment, the TWT component 1724 can be configured to determine a mode of the second wireless device via receiving a trigger message from the second wireless device. The determination of the mode of the second wireless device may be based on whether the trigger message includes a resource configuration for any wireless device. In another embodiment, the TWT component 1724 can be configured to receive a second message including a traffic indication map from the second wireless device, and the traffic indication map can indicate an operational mode selected by the wireless device 1702.

In another configuration, the wireless device 1702 can be in an operational mode The TWT responder. In this configuration, the TWT component 1724 can be configured to receive a message from the second wireless device indicating that the second wireless device is to switch to an intent to operate as one of an active mode, a power save mode, or a TWT power save mode. During the TWT power save mode, the second wireless device may enter an awake state during the TWT service period and may enter the snoring state outside of the TWT service period. The TWT component 1724 can be configured to store an operational mode associated with the second wireless device and transmit an acknowledgement of the operational mode switch to the second wireless device. In one aspect, the TWT service period can be identified based on the TWT schedule associated with the second wireless device. In another aspect, the message can include a power management indicator indicating an operational mode to which the second wireless device is intended to switch. In another embodiment, the TWT component 1724 can be configured to transmit a QoS message, which can include an EOSP indicator set to 1 to instruct the second wireless device to switch the mode of operation. In another embodiment, the TWT component 1724 can be configured to transmit a responder mode indicator that indicates whether the wireless device 1702 is in a doze state outside of the TWT service period. In another embodiment, TWT component 1724 can be configured to transmit a trigger message with unassigned resources to indicate that wireless device 1702 will enter a doze state. In another embodiment, the TWT component 1724 can be configured to transmit a traffic indication map indicating an operational mode selected by the second wireless device. In another embodiment, the TWT component 1724 can be configured to transmit an indication to the second wireless device that the second wireless device switches to or switches away from the TWT power save mode.

The various components of wireless device 1702 can be coupled together by busbar system 1726. The busbar system 1726 can include, for example, a data bus, and a power bus, a control signal bus, and a status signal bus in addition to the data bus. The components of the wireless device 1702 can be coupled using some other mechanism Put together or accept or provide input to each other.

Although several separate components are illustrated in FIG. 17, one or more of these components may be combined or implemented collectively. For example, processor 1704 can be used to implement not only the functionality described above with respect to processor 1704, but also the functionality described above with respect to signal detector 1718, DSP 1720, user interface 1722, and/or TWT component 1724. . Additionally, each of the components illustrated in Figure 17 can be implemented using a plurality of separate components.

18 is a functional block diagram of an example wireless communication device 1800 that performs TWT scheduling. Wireless communication device 1800 can include a receiver 1805, a processing system 1810, and a transmitter 1815. Processing system 1810 can include TWT component 1824 and mode component 1826.

In one configuration, the wireless communication device 1800 can be the TWT requestor requesting the TWT. In such a configuration, processing system 1810, TWT component 1824, and/or transmitter 1815 can be configured to transmit a first message including a first trigger field to a second wireless device (eg, a TWT responder). The first trigger field may indicate whether the first message includes a request for a trigger message to be sent by the second wireless device at the beginning of the TWT service period. Processing system 1810, TWT component 1824, and/or receiver 1805 can be configured to receive a second message from a second wireless device. The second message can include a second trigger field based on the first message. The second trigger field may indicate whether the second wireless device will transmit a trigger message at the beginning of the TWT service period. In one aspect, the first message can include the requested TWT, the first trigger field can be set to 1, and the first message can request a trigger message to be sent at the requested TWT. In another aspect, the second message can include the scheduled TWT, the second trigger field can be set to 1, and the second message can indicate the second wireless device. The trigger message can be transmitted at the scheduled TWT. In another aspect, the scheduled TWT can be different than the requested TWT included in the first message. In one embodiment, the processing system 1810 and/or the TWT component 1824 can be configured to determine a TWT schedule based on the received second message and decide whether to transmit to the second wireless device based on the determined TWT schedule. . In this embodiment, the processing system 1810 and/or the TWT component 1824 can be configured to determine the TWT schedule via the operation of determining whether the TWT schedule is an implicit TWT schedule or an explicit TWT schedule based on the received second message. And determining one or more TWTs associated with the TWT schedule based on the received second message. In another embodiment, the processing system 1810 and/or the TWT component 1824 can be configured to determine whether to transmit if: determining to transmit during a TWT service period when a trigger message is received from the second wireless device, Or decide to transmit outside of the TWT service period based on the EDCA parameters associated with AC_BE or AC_BK. In another aspect, processing system 1810 and/or TWT component 1824 can decide to transmit during the TWT service period based on the received trigger message, and the transmission may not be based on EDCA contention. In another embodiment, processing system 1810, TWT component 1824, and/or receiver 1805 can be configured to receive a trigger message based on the determined TWT schedule. The trigger message can include a cascading indicator that indicates whether the second wireless device will transmit another trigger message after the trigger message in the TWT service period. In another embodiment, processing system 1810, TWT component 1824, and/or receiver 1805 can be configured to receive a TWT information message from a second wireless device, and the TWT information message can include a next TWT value. Processing system 1810 and/or TWT component 1824 can be configured to update the TWT schedule based on the received TWT information message. In another embodiment, the TWT schedule can Is an implicit TWT schedule, and processing system 1810, TWT component 1824, and/or transmitter 1815 can be configured to transmit TWT information messages to the second wireless device. The TWT information message may indicate the suspension of the implicit TWT schedule or the recovery of the implicit TWT schedule after the implicit TWT schedule has been suspended. In another aspect, the first message can include a TWT channel indicator that indicates the channel and channel width that the TWT component 1824 can use to communicate with the second wireless device during the TWT service period. In another aspect, the first message can include an OFDMA bit map indicating one or more OFDMA channels and channel widths that will be used to communicate with the second wireless device.

In another configuration, the wireless communication device 1800 can be a TWT responder requesting a TWT. In this configuration, processing system 1810, TWT component 1824, and/or receiver 1805 can be configured to receive a first message including a first triggering field from a second wireless device. The first trigger field may indicate whether the first message includes a request for a trigger message to be sent by the wireless communication device 1800 at the beginning of the TWT service period. Processing system 1810 and/or TWT component 1824 can be configured to determine a TWT schedule based on the received first message. TWT component 1824, processing system 1810, and/or transmitter 1815 can be configured to transmit a second message to the second wireless device. The second message can include a TWT schedule and a second trigger field based on the determined TWT schedule. The second trigger field may indicate whether the wireless communication device 1800 can transmit a trigger message at the beginning of the TWT service period. In one aspect, the first message can include the requested TWT, the first trigger field can be set to 1, and the first message can request a trigger message to be sent at the requested TWT. In another aspect, the second message can include the scheduled TWT, the second trigger field can be set to 1, and the second message can instruct the wireless communication device 1800 to transmit the trigger message at the scheduled TWT. In another aspect, the scheduled TWT can be different The requested TWT included in the first message. In an embodiment, processing system 1810 and/or TWT component 1824 can be configured to determine a TWT schedule via: determining whether the first trigger field includes a request for a trigger message and including a pair in the first trigger field In the case of a request to trigger a message, one or more TWTs for the second wireless device are scheduled. In another embodiment, the processing system 1810, the TWT component 1824, and/or the transmitter 1815 can be configured to transmit TWT information messages including all TWTs that are different from the TWT schedules included in the second message. The next TWT value of the value. In another embodiment, the TWT schedule can be an implicit TWT schedule, and the processing system 1810, the TWT component 1824, and/or the receiver 1805 can be configured to receive TWT information messages from the second wireless device. The TWT information message may indicate the suspension of the implicit TWT schedule or the recovery of the implicit TWT schedule after the implicit TWT schedule has been suspended. In another aspect, the second message can include a TWT channel indicator indicating a channel and channel width to be used for communication between the wireless communication device 1800 and the second wireless device during the TWT service period. In another embodiment, processing system 1810, TWT component 1824, and/or transmitter 1815 can be configured to transmit a trigger message that includes a cascading indicator. The cascading indicator may indicate whether the wireless communication device 1800 will transmit another trigger message after the trigger message in the TWT service period. In another aspect, the second message can include a TWT protection indicator indicating whether there is an RTS and CTS message exchange prior to the message exchanged with the wireless communication device 1800 based on the TWT schedule.

In another configuration, the wireless communication device 1800 can broadcast the TWT to other wireless devices. In this configuration, processing system 1810 and/or TWT component 1824 can be configured to determine TWT schedules and broadcast to other wireless devices including TWT banks. Cheng's message. The message may include a broadcast indicator indicating that the TWT schedule is a broadcast TWT schedule. In one aspect, the broadcast TWT schedule can include non-negotiable TWT parameters for communicating between the wireless communication device 1800 and at least one of the wireless devices. In another aspect, the message can further include a trigger field that indicates whether the wireless communication device 1800 will transmit the trigger message at the beginning of the TWT service period. In another aspect, the message can include a TWT Flow Identifier field that indicates the type of data stream allowed during the TWT service period. In another aspect, the allowed data stream types can include MU OFDMA random access for wireless devices not associated with wireless communication device 1800, MU OFDMA for wireless devices associated with wireless communication device 1800 Random access, MU DL OFDMA scheduled access for wireless devices indicated in the TIM, MU UL OFDMA scheduled access for wireless devices indicated in the TIM, for wireless devices indicated in the TIM MU UL MIMO scheduled access, MU DL MIMO scheduled access for wireless devices indicated in the TIM. In another aspect, the TWT flow identifier field can indicate one of the following allowed data stream types: unconstrained for the type of message to be exchanged with the wireless communication device 1800, and can exchange feedback information or management with the wireless communication device 1800 The information message and the trigger message from the wireless communication device 1800 does not include a resource element for random access, and can exchange information including feedback information or management information with the wireless communication device 1800 and the trigger message from the wireless communication device 1800 includes The randomly accessed resource element may exchange information containing the quality of service information with the wireless communication device 1800 or may not be expected to communicate with or from the wireless communication device 1800. In another aspect, the TWT schedule can be an implicit TWT schedule or an explicit TWT schedule. In another aspect, the TWT schedule can be an explicit TWT schedule, TWT The schedule may include one or more TWT parameter sets, and each TWT parameter set may correspond to the scheduled TWT. In another embodiment, the TWT schedule can be an implicit TWT schedule, and processing system 1810, TWT component 1824, and/or transmitter 1815 can be configured to transmit TWT information messages to the second wireless device. The TWT information message may indicate the suspension of the implicit TWT schedule or the recovery of the implicit TWT schedule after the implicit TWT schedule has been suspended. In another embodiment, the processing system 1810, the TWT component 1824, and/or the transmitter 1815 can be configured to transmit a TWT information message to the second wireless device, and the TWT information message can indicate the TWT in the broadcasted message. The scheduled TWT of the scheduled TWT in the schedule. In another embodiment, processing system 1810, TWT component 1824, and/or transmitter 1815 can be configured to transmit a trigger message based on the TWT schedule. The trigger message can include a cascading indicator that indicates whether the wireless communication device 1800 will transmit an additional trigger message in the TWT service period. In another aspect, the message can include a TWT group assignment field, and the TWT group assignment field can include an identifier range identifying the wireless device group scheduled to wake up at the TWT during the TWT service period. In another aspect, the message can include a repeat indicator, and the repeat indicator can indicate the number of TWT service periods in which the scheduled TWT indicated in the message is valid. In another aspect, the message can include a TWT protection indicator indicating whether there is an RTS and CTS message exchange prior to the message exchanged with the wireless communication device 1800 based on the TWT schedule.

In another configuration, the wireless communication device 1800 can receive the broadcast TWT and decide whether to join the broadcast TWT. In this configuration, processing system 1810, TWT component 1824, and/or receiver 1805 can be configured to receive a message including a TWT schedule from a second wireless device. The message may include indicating that the TWT schedule is Broadcast indicator of the broadcast TWT schedule. Processing system 1810 and/or TWT component 1824 can be configured to determine one or more TWTs for wireless communication device 1800 based on the TWT schedule. In one aspect, the broadcast TWT schedule can include non-negotiable TWT parameters for communicating between the wireless communication device 1800 and the second wireless device. In another aspect, the message can include a trigger field that indicates whether the second wireless device will transmit a trigger message at the beginning of the TWT service period. In another aspect, the message can include a TWT Flow Identifier field that indicates the type of data stream allowed during the TWT service period. In another aspect, the TWT flow identifier field may indicate that the type of the message to be exchanged with the second wireless device is unconstrained, and the message including the feedback information or the management information may be exchanged with the second wireless device and is from the first The trigger message of the second wireless device does not include a resource element for random access, and may exchange information including feedback information or management information with the second wireless device, and the trigger message from the second wireless device includes a resource element for random access. The message containing the quality of service information may be exchanged with the second wireless device or may not be communicated to or from the second wireless device. In another aspect, the TWT schedule can be an implicit TWT schedule or an explicit TWT schedule. In another aspect, the TWT schedule can be an explicit TWT schedule, the TWT schedule can include one or more TWT parameter sets, and each TWT parameter set can correspond to the scheduled TWT. In another aspect, the TWT schedule can be an implicit TWT schedule, and the processing system 1810, the TWT component 1824, and/or the receiver 1805 can be configured to receive TWT information messages from the second wireless device. The TWT information message may indicate the suspension of the implicit TWT schedule or the recovery of the implicit TWT schedule after the implicit TWT schedule has been suspended. In another embodiment, processing system 1810, TWT component 1824, and/or receiver 1805 can be configured to receive from a second wireless device TWT information message. The TWT information message may indicate a scheduled TWT that is different from the TWT in the received message. In another aspect, the message can include a repeat indicator, and the repeat indicator can indicate the number of TWT service periods in which the scheduled TWT indicated in the message is valid. In another embodiment, processing system 1810, TWT component 1824, and/or receiver 1805 can be configured to receive a trigger message based on the determined one or more TWTs. In another aspect, the trigger message can include a cascading indicator that indicates whether the second wireless device will transmit an additional trigger message after the trigger message in the TWT service period. In another embodiment, the processing system 1810 and/or the TWT component 1824 can be configured to determine to transmit to the second wireless device upon receipt of the trigger message from the second wireless device during the TWT service period, and to determine that The TWT service period is transmitted to the second wireless device based on the EDCA parameters associated with AC_BE or AC_BK.

In another configuration, the wireless communication device 1800 can be a TWT requestor that decides whether to switch the mode of operation. In this configuration, processing system 1810, mode component 1826, and/or TWT component 1824 can be configured to decide whether to switch to an active mode, a power save mode, or a TWT power save mode. During the TWT power save mode, the wireless communication device 1800 may enter an awake state during the TWT service period and may enter the snoring state outside of the TWT service period. Processing system 1810, TWT component 1824, mode component 1826, and/or transmitter 1815 can be configured to transmit a message to the second wireless device based on the decision. In another aspect, the TWT service period can be identified based on the TWT schedule associated with the wireless communication device 1800. In another aspect, the message can include a power management indicator that indicates a mode to which the wireless communication device 1800 is intended to switch. In another implementation In an example, processing system 1810, TWT component 1824, mode component 1826, and/or receiver 1805 can be configured to receive an indication from the second wireless device that the wireless communication device 1800 is instructed to switch to or switch away from the TWT power save mode. In another aspect, the indication can include an EOSP indicator set to one. In another embodiment, the processing system 1810, the TWT component 1824, and/or the mode component 1826 can be configured to determine whether to switch if: whether additional data is available for transmission or reception, received from the second wireless device, A QoS message with an EOSP indicator set to 1, or a trigger message with a cascading indicator set to 0 (where the trigger message is not intended to go to the wireless communication device 1800) is received from the second wireless device. In another embodiment, processing system 1810, TWT component 1824, and/or mode component 1826 can be configured to determine the mode of the second wireless device. In another embodiment, the processing system 1810, the TWT component 1824, and/or the mode component 1826 can be configured to determine a mode of the second wireless device via receiving a second message from the second wireless device, wherein the second message can include A responder mode indicator indicating whether the second wireless device is in a doze state outside of the TWT service period. The decision on the mode of the second wireless device can be based on the responder mode indicator. In another embodiment, processing system 1810, TWT component 1824, and/or mode component 1826 can be configured to determine a mode of the second wireless device via receiving a trigger message from the second wireless device. The determination of the mode of the second wireless device may be based on whether the trigger message includes a resource configuration for any wireless device. In another embodiment, the processing system 1810, the TWT component 1824, the mode component 1826, and/or the receiver 1805 can be configured to receive a second message including a traffic indication map from the second wireless device, and the traffic indication The mapping may indicate an operating mode selected by the wireless communication device 1800.

In another configuration, the wireless communication device 1800 can be a TWT responder with respect to an operational mode. In this configuration, processing system 1810, TWT component 1824, mode component 1826, and/or receiver 1805 can be configured to receive from the second wireless device an indication that the second wireless device is to be switched to be an active mode, a power save mode, or The intended message of the operating mode of one of the TWT power saving modes. During the TWT power save mode, the second wireless device may enter an awake state during the TWT service period and may enter the snoring state outside of the TWT service period. Processing system 1810, TWT component 1824, and/or mode component 1826 can be configured to store an operational mode associated with the second wireless device and transmit an acknowledgement of the operational mode switch to the second wireless device. In one aspect, the TWT service period can be identified based on the TWT schedule associated with the second wireless device. In another aspect, the message can include a power management indicator indicating an operational mode to which the second wireless device is intended to switch. In another embodiment, processing system 1810, TWT component 1824, mode component 1826, and/or transmitter 1815 can be configured to transmit QoS messages, which can include an EOSP indicator set to 1 to instruct a second wireless device to switch Operating mode. In another embodiment, processing system 1810, TWT component 1824, mode component 1826, and/or transmitter 1815 can be configured to transmit a responder mode indicator that indicates whether wireless communication device 1800 is outside of the TWT service period Snoring state. In another embodiment, processing system 1810, TWT component 1824, mode component 1826, and/or transmitter 1815 can be configured to transmit a trigger message with unassigned resources to indicate that wireless communication device 1800 will enter a doze state. In another embodiment, processing system 1810, TWT component 1824, mode component 1826, and/or transmitter 1815 can be configured to transmit a traffic indication map indicating an operational mode selected by the second wireless device. In another embodiment The processing system 1810, the TWT component 1824, the mode component 1826, and/or the transmitter 1815 can be configured to transmit an indication to the second wireless device that the second wireless device switches to or switches away from the TWT power save mode.

Receiver 1805, processing system 1810, TWT component 1824, mode component 1826, and/or transmitter 1815 can be configured to perform blocks 405, 410, 415, 420, 425, 430, 435, and 440 described above with respect to FIG. 4; Blocks 505, 510, 515, 520, 525, and 530 of FIG. 5; blocks 705, 710, 715, 720, and 725 of FIG. 7; blocks 805, 810, 815, 820, 825, 830, and 835 of FIG. One or more of the functions discussed in blocks 1005, 1010, 1015, 1020, and 1025 of FIG. 10; and blocks 1105, 1110, 1115, 1120, 1125, 1130, 1135, and 1140 of FIG. Receiver 1805 can correspond to receiver 1712. Processing system 1810 can correspond to processor 1704. Transmitter 1815 may correspond to transmitter 1710. TWT component 1824 can correspond to TWT component 126, TWT component 124, and/or TWT component 1724.

In one configuration, the wireless communication device 1800 can be the TWT requestor requesting the TWT. In such a configuration, the wireless communication device 1800 can include means for transmitting a first message including a first trigger field to a second wireless device (e.g., a TWT responder). The first trigger field may indicate whether the first message includes a request for a trigger message to be sent by the second wireless device at the beginning of the TWT service period. The wireless communication device 1800 can include means for receiving a second message from the second wireless device. The second message can include a second trigger field based on the first message. The second trigger field may indicate whether the second wireless device will transmit a trigger message at the beginning of the TWT service period. In one aspect, the first message can include the requested TWT, the first trigger field can be set to 1, and the first message can be requested. The trigger message that will be sent at the requested TWT. In another aspect, the second message can include the scheduled TWT, the second trigger field can be set to 1, and the second message can indicate that the second wireless device can transmit the trigger message at the scheduled TWT. In another aspect, the scheduled TWT can be different than the requested TWT included in the first message. In one embodiment, the wireless communication device 1800 can include means for determining a TWT schedule based on the received second message, and for determining whether to transmit to the second wireless device based on the determined TWT schedule s installation. In this embodiment, the means for determining the TWT schedule can be configured to determine whether the TWT schedule is an implicit TWT schedule or an explicit TWT schedule based on the received second message and based on the received second message To determine one or more TWTs associated with the TWT schedule. In another embodiment, the means for deciding whether to transmit may be configured to decide to transmit when a trigger message is received from the second wireless device during the TWT service period, or to decide to be based on the TWT service period The EDCA parameters associated with AC_BE or AC_BK are transmitted. In another aspect, the wireless communication device 1800 can decide to transmit during the TWT service period based on the received trigger message, and the transmission may not be based on EDCA contention. In another embodiment, the wireless communication device 1800 can include means for receiving a trigger message based on the determined TWT schedule. The trigger message can include a cascading indicator that indicates whether the second wireless device will transmit another trigger message after the trigger message in the TWT service period. In another embodiment, the wireless communication device 1800 can include means for receiving a TWT information message from the second wireless device, and the TWT information message can include the next TWT value. The wireless communication device 1800 can include means for updating the TWT schedule based on the received TWT information message. In another embodiment, The TWT schedule can be an implicit TWT schedule, and the wireless communication device 1800 can include means for transmitting a TWT information message to the second wireless device. The TWT information message may indicate the suspension of the implicit TWT schedule or the recovery of the implicit TWT schedule after the implicit TWT schedule has been suspended. In another aspect, the first message can include a TWT channel indicator that indicates the channel and channel width that the wireless communication device 1800 can use to communicate with the second wireless device during the TWT service period. In another aspect, the first message can include an OFDMA bit map indicating one or more OFDMA channels and channel widths that will be used to communicate with the second wireless device.

In another configuration, the wireless communication device 1800 can be a TWT responder requesting a TWT. In this configuration, the wireless communication device 1800 can include means for receiving a first message including a first trigger field from the second wireless device. The first trigger field may indicate whether the first message includes a request for a trigger message to be sent by the wireless communication device 1800 at the beginning of the TWT service period. The wireless communication device 1800 can include means for determining a TWT schedule based on the received first message. The wireless communication device 1800 can include means for transmitting a second message to the second wireless device. The second message can include a TWT schedule and a second trigger field based on the determined TWT schedule. The second trigger field may indicate whether the wireless communication device 1800 can transmit a trigger message at the beginning of the TWT service period. In one aspect, the first message can include the requested TWT, the first trigger field can be set to 1, and the first message can request a trigger message to be sent at the requested TWT. In another aspect, the second message can include the scheduled TWT, the second trigger field can be set to 1, and the second message can instruct the wireless communication device 1800 to transmit the trigger message at the scheduled TWT. In another aspect, the scheduled TWT can be different than the requested TWT included in the first message. In an embodiment, for use in The device for scheduling the TWT schedule can be configured to determine whether the first trigger field includes a request for a trigger message and schedule the one for the second wireless device if the first trigger field includes a request for the trigger message Multiple TWTs. In another embodiment, the wireless communication device 1800 can include means for transmitting a TWT information message including a next TWT different from all TWT values associated with the TWT schedule included in the second message. value. In another embodiment, the TWT schedule can be an implicit TWT schedule, and the wireless communication device 1800 can include means for receiving TWT information messages from the second wireless device. The TWT information message may indicate the suspension of the implicit TWT schedule or the recovery of the implicit TWT schedule after the implicit TWT schedule has been suspended. In another aspect, the second message can include a TWT channel indicator indicating a channel and channel width to be used for communication between the wireless communication device 1800 and the second wireless device during the TWT service period. In another embodiment, the wireless communication device 1800 can include means for transmitting a trigger message including a cascading indicator. The cascading indicator may indicate whether the wireless communication device 1800 will transmit another trigger message after the trigger message in the TWT service period. In another aspect, the second message can include a TWT protection indicator indicating whether there is an RTS and CTS message exchange prior to the message exchanged with the wireless communication device 1800 based on the TWT schedule.

In another configuration, the wireless communication device 1800 can broadcast the TWT to other wireless devices. In this configuration, wireless communication device 1800 can include means for determining TWT schedules and means for broadcasting messages including TWT schedules to other wireless devices. The message may include a broadcast indicator indicating that the TWT schedule is a broadcast TWT schedule. In one aspect, the broadcast TWT schedule can include at least one of the wireless communication device 1800 and the wireless devices. Non-negotiable TWT parameters for communication between. In another aspect, the message can further include a trigger field that indicates whether the wireless communication device 1800 will transmit the trigger message at the beginning of the TWT service period. In another aspect, the message can include a TWT Flow Identifier field that indicates the type of data stream allowed during the TWT service period. In another aspect, the allowed data stream types can include MU OFDMA random access for wireless devices not associated with wireless communication device 1800, MU OFDMA for wireless devices associated with wireless communication device 1800 Random access, MU DL OFDMA scheduled access for wireless devices indicated in the TIM, MU UL OFDMA scheduled access for wireless devices indicated in the TIM, for wireless devices indicated in the TIM MU UL MIMO scheduled access, MU DL MIMO scheduled access for wireless devices indicated in the TIM. In another aspect, the TWT flow identifier field can indicate one of the following allowed data stream types: unconstrained for the type of message to be exchanged with the wireless communication device 1800, and can exchange feedback information or management with the wireless communication device 1800 The information message and the trigger message from the wireless communication device 1800 does not include a resource element for random access, and can exchange information including feedback information or management information with the wireless communication device 1800 and the trigger message from the wireless communication device 1800 includes The randomly accessed resource element may exchange information containing the quality of service information with the wireless communication device 1800 or may not be expected to communicate with or from the wireless communication device 1800. In another aspect, the TWT schedule can be an implicit TWT schedule or an explicit TWT schedule. In another aspect, the TWT schedule can be an explicit TWT schedule, the TWT schedule can include one or more TWT parameter sets, and each TWT parameter set can correspond to the scheduled TWT. In another embodiment, the TWT schedule can be an implicit TWT schedule, and the wireless communication device 1800 can include A means for transmitting a TWT information message to a second wireless device. The TWT information message may indicate the suspension of the implicit TWT schedule or the recovery of the implicit TWT schedule after the implicit TWT schedule has been suspended. In another embodiment, the wireless communication device 1800 can include means for transmitting a TWT information message to the second wireless device, and the TWT information message can indicate the scheduled TWT in the TWT schedule in the broadcasted message. Different scheduled TWTs. In another embodiment, the wireless communication device 1800 can include means for transmitting a trigger message based on the TWT schedule. The trigger message can include a cascading indicator that indicates whether the wireless communication device 1800 will transmit an additional trigger message in the TWT service period. In another aspect, the message can include a TWT group assignment field, and the TWT group assignment field can include an identifier range identifying the wireless device group scheduled to wake up at the TWT during the TWT service period. In another aspect, the message can include a repeat indicator, and the repeat indicator can indicate the number of TWT service periods in which the scheduled TWT indicated in the message is valid. In another aspect, the message can include a TWT protection indicator indicating whether there is an RTS and CTS message exchange prior to the message exchanged with the wireless communication device 1800 based on the TWT schedule.

In another configuration, the wireless communication device 1800 can receive the broadcast TWT and decide whether to join the broadcast TWT. In this configuration, wireless communication device 1800 can include means for receiving a message including a TWT schedule from a second wireless device. The message may include a broadcast indicator indicating that the TWT schedule is a broadcast TWT schedule. The wireless communication device 1800 can include means for determining one or more TWTs for the wireless communication device 1800 based on the TWT schedule. In one aspect, the broadcast TWT schedule can include non-negotiable TWT parameters for communicating between the wireless communication device 1800 and the second wireless device. In another aspect, the message can A trigger field is included that indicates whether the second wireless device will transmit a trigger message at the beginning of the TWT service period. In another aspect, the message can include a TWT Flow Identifier field that indicates the type of data stream allowed during the TWT service period. In another aspect, the TWT flow identifier field may indicate that the type of the message to be exchanged with the second wireless device is unconstrained, and the message including the feedback information or the management information may be exchanged with the second wireless device and is from the first The trigger message of the second wireless device does not include a resource element for random access, and may exchange information including feedback information or management information with the second wireless device, and the trigger message from the second wireless device includes a resource element for random access. The message containing the quality of service information may be exchanged with the second wireless device or may not be communicated to or from the second wireless device. In another aspect, the TWT schedule can be an implicit TWT schedule or an explicit TWT schedule. In another aspect, the TWT schedule can be an explicit TWT schedule, the TWT schedule can include one or more TWT parameter sets, and each TWT parameter set can correspond to the scheduled TWT. In another aspect, the TWT schedule can be an implicit TWT schedule, and the wireless communication device 1800 can include means for receiving TWT information messages from the second wireless device. The TWT information message may indicate the suspension of the implicit TWT schedule or the recovery of the implicit TWT schedule after the implicit TWT schedule has been suspended. In another embodiment, the wireless communication device 1800 can include means for receiving a TWT information message from the second wireless device. The TWT information message may indicate a scheduled TWT that is different from the TWT in the received message. In another aspect, the message can include a repeat indicator, and the repeat indicator can indicate the number of TWT service periods in which the scheduled TWT indicated in the message is valid. In another embodiment, the wireless communication device 1800 can include means for receiving a trigger message based on the determined one or more TWTs. In another aspect, the trigger The message may include a cascading indicator indicating whether the second wireless device will transmit an additional trigger message after the trigger message in the TWT service period. In another embodiment, the wireless communication device 1800 can include means for determining to transmit to the second wireless device upon receipt of the trigger message from the second wireless device during the TWT service period, and for determining to be at the TWT Means for transmitting to the second wireless device based on the EDCA parameters associated with AC_BE or AC_BK outside of the service period.

In another configuration, the wireless communication device 1800 can be a TWT requestor that decides whether to switch the mode of operation. In this configuration, the wireless communication device 1800 can include means for deciding whether to switch to an active mode, a power save mode, or a TWT power save mode. During the TWT power save mode, the wireless communication device 1800 may enter an awake state during the TWT service period and may enter the snoring state outside of the TWT service period. The wireless communication device 1800 can include means for transmitting a message to the second wireless device based on the decision. In another aspect, the TWT service period can be identified based on the TWT schedule associated with the wireless communication device 1800. In another aspect, the message can include a power management indicator that indicates a mode to which the wireless communication device 1800 is intended to switch. In another embodiment, the wireless communication device 1800 can include means for receiving an indication from the second wireless device that the wireless communication device 1800 is instructed to switch to or switch away from the TWT power save mode. In another aspect, the indication can include an EOSP indicator set to one. In another embodiment, the means for deciding whether to perform the handover may be configured to determine whether additional data is available for transmission or reception, receive a QoS message with the EOSP indicator set to 1 from the second wireless device, or The second wireless device receives a trigger message with a cascading indicator set to 0 (where the trigger message is not intended to go to none Line communication equipment 1800). In another embodiment, the wireless communication device 1800 can include means for determining a mode of the second wireless device. In another embodiment, the means for determining the mode of the second wireless device can be configured to receive the second message from the second wireless device, wherein the second message can include indicating whether the second wireless device is outside of the TWT service period Responder mode indicator in hiccup state. The decision on the mode of the second wireless device can be based on the responder mode indicator. In another embodiment, the means for determining the mode of the second wireless device can be configured to receive a trigger message from the second wireless device. The determination of the mode of the second wireless device may be based on whether the trigger message includes a resource configuration for any wireless device. In another embodiment, the wireless communication device 1800 can include means for receiving a second message including a traffic indication map from the second wireless device, and the traffic indication map can indicate an operational mode selected by the wireless communication device 1800 .

In another configuration, the wireless communication device 1800 can be a TWT responder with respect to an operational mode. In this configuration, the wireless communication device 1800 can include a message for receiving from the second wireless device a message indicating that the second wireless device is to switch to an operational mode that is one of an active mode, a power save mode, or a TWT power save mode. Device. During the TWT power save mode, the second wireless device may enter an awake state during the TWT service period and may enter the snoring state outside of the TWT service period. The wireless communication device 1800 can include means for storing an operational mode associated with the second wireless device and means for transmitting an acknowledgement of the operational mode switch to the second wireless device. In one aspect, the TWT service period can be identified based on the TWT schedule associated with the second wireless device. In another aspect, the message can include indicating that the second wireless device intends to switch to The power management indicator of the operating mode. In another embodiment, the wireless communication device 1800 can include means for transmitting a QoS message including an EOSP indicator set to 1 to instruct the second wireless device to switch the mode of operation. In another embodiment, the wireless communication device 1800 can include means for transmitting a responder mode indicator that indicates whether the wireless communication device 1800 is in a doze state outside of the TWT service period. In another embodiment, the wireless communication device 1800 can include means for transmitting a trigger message with unassigned resources to indicate that the wireless communication device 1800 will enter a doze state. In another embodiment, the wireless communication device 1800 can include means for transmitting a traffic indication map indicating an operational mode selected by the second wireless device. In another embodiment, the wireless communication device 1800 can include means for transmitting an indication to the second wireless device that the second wireless device switches to or switches away from the TWT power save mode.

For example, the means for transmitting may include a processing system 1810, a TWT component 1824, and/or a transmitter 1815. The means for receiving may include a processing system 1810, a TWT component 1824, and/or a receiver 1805. The means for determining the TWT schedule based on the received second message may include a processing system 1810 and/or a TWT component 1824. The means for deciding whether to transmit to the second wireless device based on the determined TWT schedule may include processing system 1810 and/or TWT component 1824. The means for updating may include processing system 1810 and/or TWT component 1824. The means for determining the TWT schedule based on the received first message may include a processing system 1810 and/or a TWT component 1824. The means for determining the TWT schedule may include a processing system 1810 and/or a TWT component 1824. The means for broadcasting may include a processing system 1810, a TWT component 1824, and/or a transmitter 1815 . The means for determining one or more TWTs can include a processing system 1810 and/or a TWT component 1824. The means for determining to transmit to the second wireless device during the TWT service period may include processing system 1810 and/or TWT component 1824. The means for determining to transmit to the second wireless device outside of the TWT service period may include processing system 1810 and/or TWT component 1824. The means for deciding whether to switch may include processing system 1810, mode component 1826, and/or TWT component 1824. The means for determining the mode of the second wireless device can include a processing system 1810, a TWT component 1824, and/or a mode component 1826. The means for storing may include a processing system 1810, a TWT component 1824, and/or a mode component 1826.

The various operations of the methods described above may be performed by any suitable means capable of performing such operations, such as various hardware and/or software components, circuits, and/or modules. In general, any of the operations illustrated in the figures can be performed by a corresponding functional device capable of performing the operations.

The various illustrative logical blocks, components, and circuits described in connection with the present disclosure can be a general purpose processor, DSP, ASIC, FPGA or other PLD, individual gate or transistor logic, individual hardware components, or a single hardware component designed to perform the functions described herein. Or any combination thereof to implement or perform. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

In one or more aspects, the functions described can be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions can be stored on or transmitted as computer readable media as one or more instructions or codes. Computer readable media includes both computer storage media and communication media, including any media that facilitates the transfer of a computer program from one location to another. The storage medium can be any available media that can be accessed by the computer. By way of example and not limitation, such computer readable medium may include RAM, ROM, EEPROM, compact disk (CD) ROM (CD-ROM) or other optical disk storage, disk storage or other magnetic storage device, or may be used Any other medium that carries or stores the desired code in the form of an instruction or data structure and that can be accessed by a computer. Any connection is also properly referred to as computer readable media. For example, if the software is transmitted from a web site, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave. The coaxial cable, fiber optic cable, twisted pair cable, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of the media. As used herein, the disk (disk) and disc (disc) including CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks (disk) tend to magnetically reproduce information The disc ( disc ) uses laser light to reproduce the data optically. Thus, computer readable media includes non-transitory computer readable media (eg, tangible media).

The methods disclosed herein comprise one or more steps or actions for implementing the methods described. These method steps and/or actions may be interchanged without departing from the scope of the claims. In other words, the order and/or use of specific steps and/or actions may be modified without departing from the scope of the claims.

Accordingly, certain aspects may include a computer program product for performing the operations provided herein. For example, such a computer program product can include computer readable media having stored thereon (and/or encoded) instructions executable by one or more processors to perform the operations described herein. For some aspects, computer program products may include packaging materials.

In addition, it should be appreciated that components and/or other suitable means for performing the methods and techniques described herein can be downloaded and/or otherwise obtained by a user terminal and/or a base station where applicable. For example, such a device can be coupled to a server to facilitate the transfer of means for performing the methods described herein. Alternatively, the various methods described herein can be provided via a storage device (eg, RAM, ROM, physical storage media such as a CD or floppy disk, etc.) such that once the storage device is coupled to or provided to the user terminal and / or base station, the device can get a variety of methods. Moreover, any other suitable technique suitable for providing the methods and techniques described herein to a device may be utilized.

It will be understood that the claims are not limited to the precise configurations and components illustrated above. Various changes, modifications, and variations can be made in the arrangement, operation and details of the methods and apparatus described above without departing from the scope of the claims.

Although the foregoing is directed to the various aspects of the present invention, other and further aspects of the present invention can be devised without departing from the basic scope and the scope thereof is determined by the appended claims.

The previous description is provided to enable the general knowledge in the field of the invention to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those of ordinary skill in the art to which the invention pertains, and the general principles defined herein may be applied to other aspects. because Therefore, the claims are not intended to be limited to the aspects shown herein, but should be accorded to all categories that are consistent with the linguistic claims. The singular singular representation of the elements is not intended unless otherwise stated Indicates "has one and only one" but "one or more". Unless specifically stated otherwise, the term "some" refers to one or more. All of the structural and functional equivalents of the present invention, which are presently known in the art to which the present invention pertains, are hereby incorporated by reference. . Moreover, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly recited in the scope of the application. No element of the claim shall be construed in accordance with the provisions of Rule 19, Item 4, unless the element is explicitly stated using the phrase "apparatus for" or in the case of a method request. It is described using the phrase "steps for...".

300‧‧‧ diagram

302‧‧‧AP

304‧‧‧BSS

306‧‧‧STA

308‧‧‧STA

310‧‧‧STA

312‧‧‧First message

314‧‧‧Second message

316‧‧‧Trigger message

350‧‧‧Time Sequence Flow Chart

Claims (56)

A method for wireless communication by a first wireless device, comprising the steps of: deciding whether to switch to an active mode, a power saving mode, or a target wake time (TWT) power saving mode, wherein during the TWT power saving mode The first wireless device enters an awake state during the TWT service period and enters a doze state outside of the TWT service period; and transmits a message to a second wireless device based on the decision. The method of claim 1, wherein the TWT service periods are identified based on a TWT schedule associated with the first wireless device. The method of claim 1, wherein the message comprises a power management indicator indicating a mode to which the first wireless device intends to switch. The method of claim 1, further comprising receiving an indication from the second wireless device that the first wireless device switches to or switches away from the TWT power save mode. The method of claim 4, wherein the indication comprises an end of service period (EOSP) indicator set to one. The method of claim 1, wherein the determining comprises the step of: determining whether additional information is available for transmission or reception; Receiving, from the second wireless device, a Quality of Service (QoS) message with an End of Service Period (EOSP) indicator set to 1; or receiving from the second wireless device a cascading indicator with a setting of 0 A trigger message and the trigger message is not intended for the first wireless device. The method of claim 1, further comprising determining a mode of the second wireless device. The method of claim 7, wherein the determining the mode of the second wireless device comprises receiving a second message from the second wireless device, wherein the second message comprises indicating that the second wireless device is in the TWT service time period Whether or not the outside is in a doze state, and the decision of the mode for the second wireless device is based on the responder mode indicator. The method of claim 1, wherein the determining the mode of the second wireless device comprises receiving a trigger message from the second wireless device, wherein the determining of the mode of the second wireless device is based on whether the trigger message includes Resource configuration for any wireless device. The method of claim 1, further comprising receiving, from the second wireless device, a second message including a traffic indication map, wherein the traffic indication map indicates an operational mode selected by the first wireless device. A method for wireless communication by a first wireless device, including the following Step: receiving, from a second wireless device, a message indicating that the second wireless device is to switch to an operating mode that is one of an active mode, a power saving mode, or a target wake time (TWT) power saving mode An intention, wherein during the TWT power save mode, the second wireless device enters an awake state during a TWT service period and enters a doze state outside of the TWT service period; storing associated with the second wireless device The mode of operation; and transmitting to the second wireless device an acknowledgement of the mode of operation switching. The method of claim 11, wherein the TWT service periods are identified based on a TWT schedule associated with the second wireless device. The method of claim 11, wherein the message includes a power management indicator indicating the mode of operation to which the second wireless device intends to switch. The method of claim 11, further comprising transmitting a Quality of Service (QoS) message, the QoS message including an End of Service Period (EOSP) indicator set to 1 to instruct the second wireless device to switch the mode of operation. The method of claim 11, further comprising transmitting a responder mode indicator indicating whether the first wireless device is in a doze state outside of the TWT service periods. The method of claim 11, further comprising transmitting a trigger message with unassigned resources to indicate that the first wireless device is to enter a doze state. The method of claim 11, further comprising transmitting a traffic indication map indicating the mode of operation selected by the second wireless device. The method of claim 11, further comprising transmitting to the second wireless device an indication that the second wireless device switches to or switches away from the TWT power save mode. An apparatus for wireless communication, the apparatus being a first wireless device, the apparatus comprising: means for determining whether to switch to an active mode, a power saving mode, or a target wake time (TWT) power saving mode, During the TWT power saving mode, the first wireless device enters an awake state during the TWT service period and enters a doze state outside of the TWT service period; and is configured to transmit to a second wireless device based on the decision A device for a message. The apparatus of claim 19, wherein the TWT service periods are identified based on a TWT schedule associated with the first wireless device. The apparatus of claim 19, wherein the message comprises indicating the first wireless device A power management indicator of a mode intended to switch to. The apparatus of claim 19, further comprising means for receiving, from the second wireless device, an indication that the first wireless device switches to or switches away from the TWT power save mode. The apparatus of claim 22, wherein the indication comprises an End of Service Period (EOSP) indicator set to one. The apparatus of claim 19, wherein the means for determining is configured to: determine if additional data is available for transmission or reception; receive an End of Service (EOSP) indicator with the set to 1 from the second wireless device a quality of service (QoS) message; or receiving a trigger message with the first level indicator set to 0 from the second wireless device and the trigger message is not intended for the first wireless device. The apparatus of claim 19, further comprising means for determining a mode of the second wireless device. The apparatus of claim 25, wherein the means for determining the mode of the second wireless device is configured to receive a second message from the second wireless device, wherein the second message comprises indicating that the second wireless device is Whether a response mode indicator outside the TWT service period is in a doze state, and the decision of the mode for the second wireless device is based on the responder mode indication symbol. The apparatus of claim 19, wherein the means for determining the mode of the second wireless device is configured to receive a trigger message from the second wireless device, and wherein the determining of the mode of the second wireless device It is based on whether the trigger message includes resource configuration for any wireless device. The apparatus of claim 19, further comprising means for receiving a second message including a traffic indication map from the second wireless device, wherein the traffic indication map indicates an operational mode selected by the first wireless device . An apparatus for wireless communication, the apparatus being a first wireless device, the apparatus comprising: means for receiving a message from a second wireless device, the message indicating that the second wireless device is to be switched to be an active mode An intent of an operational mode of one of a power save mode, or a target wake up time (TWT) power save mode, wherein during the TWT power save mode, the second wireless device enters an awake state during a TWT service period And entering a doze state outside of the TWT service period; means for storing the mode of operation associated with the second wireless device; and for transmitting to the second wireless device a switch to the mode of operation Received device. The apparatus of claim 29, wherein the TWT service periods are identified based on a TWT schedule associated with the second wireless device. The apparatus of claim 29, wherein the message includes a power management indicator indicating the mode of operation to which the second wireless device intends to switch. The apparatus of claim 29, further comprising means for transmitting a Quality of Service (QoS) message, the QoS message including an End of Service Period (EOSP) indicator set to 1 to instruct the second wireless device to switch the mode of operation. The apparatus of claim 29, further comprising means for transmitting a responder mode indicator indicating whether the first wireless device is in a doze state outside of the TWT service periods. The apparatus of claim 29, further comprising means for transmitting a trigger message with unassigned resources to indicate that the first wireless device is to enter a doze state. The apparatus of claim 29, further comprising means for transmitting a traffic indication map indicating the mode of operation selected by the second wireless device. The apparatus of claim 29, further comprising means for transmitting to the second wireless device an indication that the second wireless device switches to or switches away from the TWT power save mode. A device for wireless communication, the device being a first wireless device, the device comprising: a memory; and at least one processor coupled to the memory and configured to: determine whether to switch to an active mode, a power save mode, or a target wake up time (TWT) power save mode, wherein during the TWT power save mode, the first wireless device enters an awake state during a TWT service period and enters one outside of the TWT service period a snooze state; and based on the decision to transmit a message to a second wireless device. The apparatus of claim 37, wherein the TWT service periods are identified based on a TWT schedule associated with the first wireless device. The device of claim 37, wherein the message comprises a power management indicator indicating a mode to which the first wireless device intends to switch. The apparatus of claim 37, wherein the at least one processor is further configured to receive an indication from the second wireless device that the first wireless device switches to or switches away from the TWT power save mode. The device of claim 40, wherein the indication comprises an End of Service Period (EOSP) indicator set to one. The apparatus of claim 37, wherein the at least one processor is configured to determine whether to determine whether additional data is available for transmission or reception, and to receive from the second wireless device an end of a service period set to 1 ( EOSP) a quality of service (QoS) message; or receiving a trigger message with the first level indicator set to 0 from the second wireless device and the trigger message is not intended for the first wireless device. The device of claim 37, wherein the at least one processor is configured to determine a mode of the second wireless device. The device of claim 43, wherein the at least one processor is configured to determine the mode of the second wireless device by receiving a second message from the second wireless device, wherein the second message comprises indicating Whether the second wireless device is in a doze state outside of the TWT service period, and the decision for the mode of the second wireless device is based on the responder mode indicator. The device of claim 37, wherein the at least one processor is configured to determine the mode of the second wireless device by receiving a trigger message from the second wireless device, wherein the second wireless device The decision of the mode is based on whether the trigger message includes a resource configuration for any wireless device. The apparatus of claim 37, wherein the at least one processor is further configured to receive a second message including a traffic indication map from the second wireless device, wherein the traffic indication mapping indication is for the first wireless device to select One mode of operation. A device for wireless communication, the device being a first wireless device, the device comprising: a memory; and at least one processor coupled to the memory and configured to: receive a message from a second wireless device The message indicates an intent of the second wireless device to switch to an operational mode that is one of an active mode, a power save mode, or a target wake time (TWT) power save mode, wherein the TWT power save mode During the TWT service period, the second wireless device enters an awake state and enters a doze state outside of the TWT service period; stores the operational mode associated with the second wireless device; and transmits to the second wireless The device transmits an acknowledgement of the switching of the operating mode. The apparatus of claim 47, wherein the TWT service periods are identified based on a TWT schedule associated with the second wireless device. The device of claim 47, wherein the message comprises the second wireless device A power management indicator of the operational mode to which the intent is switched. The apparatus of claim 47, wherein the at least one processor is further configured to transmit a Quality of Service (QoS) message, the QoS message including an End of Service Period (EOSP) indicator set to 1 to instruct the second wireless device to switch Operating mode. The apparatus of claim 47, wherein the at least one processor is further configured to transmit a responder mode indicator indicating whether the first wireless device is in a doze state outside of the TWT service period . The apparatus of claim 47, wherein the at least one processor is further configured to transmit a trigger message with unassigned resources to indicate that the first wireless device is to enter a doze state. The apparatus of claim 47, wherein the at least one processor is further configured to transmit a traffic indication map indicating the mode of operation selected by the second wireless device. The apparatus of claim 47, wherein the at least one processor is further configured to transmit to the second wireless device an indication that the second wireless device switches to or switches away from the TWT power save mode. A computer readable medium storing a computer executable code for a first wireless device, comprising code for determining whether to switch to an active mode, a power save mode, or a target wake time (TWT) a power save mode, wherein during the TWT power save mode, the first wireless device enters an awake state during a TWT service period and enters a doze state outside of the TWT service period; and proceeds to a second wireless based on the decision The device transmits a message. A computer readable medium storing a computer executable code for a first wireless device, comprising code for receiving a message from a second wireless device indicating that the second wireless device is to switch to An intent of an operational mode as one of an active mode, a power save mode, or a target wake up time (TWT) power save mode, wherein during the TWT power save mode, the second wireless device is during a TWT service period Entering an awake state and entering a doze state outside of the TWT service period; storing the mode of operation associated with the second wireless device; and transmitting an acknowledgement to the second wireless device of the mode of operation switching.