Service Period End Instruction

Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, an access point may initiate a target wake time (TWT) service period (SP). The access point may receive an SP end of service (EOSP) indication from a station. The access point may stop the TWT SP before the scheduled end of the TWT SP based on receiving the EOSP indication. Numerous other aspects are described.

Description

Technical Field

[0001] (Cross - Reference to Related Applications)

[0001] This patent application claims the priority of U.S. Patent Application No. 17 / 662,644, titled "END OF SERVICE PERIOD INDICATION", filed on May 9, 2022, which was assigned to the assignee of this application. The disclosure of the prior application is considered a part of this patent application and is incorporated herein by reference.

[0002]

[0002] Aspects of the present disclosure generally relate to wireless communication and techniques and apparatuses for using end - of - service - period indications.

Background Art

[0003]

[0001] A wireless local area network (WLAN) may be formed by one or more access points (APs) that provide a shared wireless communication medium for use by several client devices, also called stations (STAs). The basic building block of a WLAN compliant with the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard family is a basic service set (BSS) managed by an AP. Each BSS is identified by a basic service set identifier (BSSID) advertised by the AP. The AP periodically broadcasts beacon frames to enable any STA within the wireless range of the AP to establish or maintain a communication link with the WLAN.

[0004]

[0002] To improve data throughput, an AP may communicate with one or more STAs through multiple simultaneous communication links. Each of the communication links may be of various bandwidths, for example, by combining several 20 MHz-wide channels together to form a 40 MHz-wide channel, an 80 MHz-wide channel, or a 160 MHz-wide channel. The AP may establish a BSS on any of the different communication links, and thus, it is desirable to improve the communication between the AP and one or more STAs through each of the communication links.

Summary of the Invention

[0005]

[0003] Some aspects described herein relate to a method of wireless communication performed by an access point. The method may include starting a target wake time (TWT) service period (SP). The method may include receiving a first end of SP (EOSP) indication from a station. The method may include stopping the TWT SP before the scheduled end of the TWT SP based on receiving the first EOSP indication.

[0006]

[0004] Some aspects described herein relate to a method of wireless communication performed by a station. The method may include entering a TWT SP. The method may include transmitting an EOSP indication to an access point before the scheduled end of the TWT SP.

[0007]

[0005] Some aspects described in this specification relate to access points for wireless communication. The access point may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to initiate a TWT SP. The one or more processors may be configured to receive a first EOSP instruction from a station. The one or more processors may be configured to stop the TWT SP before the scheduled end of the TWT SP based on receiving the first EOSP instruction.

[0008]

[0006] Some aspects described herein relate to stations for wireless communication. The station may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to enter a TWT SP. The one or more processors may be configured to send an EOSP instruction to an access point before the scheduled end of the TWT SP.

[0009]

[0007] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by one or more instructions when executed by one or more processors of an access point. The set of instructions can cause a TWT SP to be initiated by one or more instructions when executed by one or more processors of the access point. The set of instructions can cause one or more processors of the access point to receive a first EOSP indication from a station when executed by one or more instructions when executed by one or more processors of the access point. The set of instructions can cause the TWT SP to be stopped before a scheduled end of the TWT SP based on receiving the first EOSP indication by one or more instructions when executed by one or more processors of the access point.

[0010]

[0008] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a station. The set of instructions can cause the station to enter a TWT SP when executed by one or more processors of the station. The set of instructions can cause the station to send an EOSP indication to an access point before a scheduled end of the TWT SP when executed by one or more processors of the station.

[0011] [

[0009] ] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for starting a TWT SP. The apparatus may include means for receiving a first EOSP indication from a station. The apparatus may include means for stopping the TWT SP before a scheduled end of the TWT SP based on receiving the first EOSP indication.

[0012] [

[0010] ] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for entering a TWT SP. The apparatus may include means for transmitting an EOSP indication to an access point before a scheduled end of the TWT SP.

[0013] [

[0011] ] Aspects generally relate to a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, station, access point, wireless communication device, and / or processing system substantially as described herein with reference to the drawings and the specification, and as shown by the drawings and the specification.

[0014] [

[0012] ] Above, the features and technical advantages of the examples according to the present disclosure have been outlined rather broadly so as to better understand the following "Modes for Carrying Out the Invention". Additional features and advantages are described below. The concepts and specific examples of the disclosure can be readily utilized as a basis for modifying or designing other structures to achieve the same object of the disclosure. Such equivalent structures do not depart from the scope of the appended claims. The characteristics of both the organization and the method of operation of the concepts disclosed herein, and the advantages associated therewith, will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the drawings is provided for purposes of illustration and explanation, not as a definition of the limitations of the claims.

[0015] Aspects are described in this disclosure by way of several examples, and those skilled in the art will understand that such aspects can be implemented in many different configurations and scenarios. The techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or packaging configurations. For example, some aspects can be implemented via integrated chip embodiments or other non-module component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchase devices, medical devices, and / or artificial intelligence-enabled devices). Aspects can be implemented at the chip-level component, modular component, non-modular component, non-chip-level component, device-level component, and / or system-level component. Devices incorporating the described aspects and features may include additional components and features for the implementation and practice of the claimed and described aspects. For example, the transmission and reception of wireless signals can include one or more components for analog and digital applications (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or summers). The aspects described herein are intended to be practiced in a wide variety of devices, components, systems, distributed configurations, and / or end-user devices of various sizes, shapes, and structures.

Brief Description of the Drawings

[0016]

[0014] To better understand the above-listed features of the present disclosure, a more detailed description, briefly summarized above, may be obtained by referring to the embodiments shown in the accompanying drawings. However, it should be noted that the accompanying drawings only show specific exemplary embodiments of the present disclosure, and therefore, this description should not be considered as limiting the scope of the present disclosure, as other equally effective embodiments may be recognized. The same reference numerals in different drawings may identify the same or similar elements.

Figure 1A

[0015] FIG. showing an example of a wireless communication network according to the present disclosure.

Figure 1B

[0016] FIG. showing a block diagram of an exemplary wireless communication device according to the present disclosure.

Figure 1C

[0017] FIG. showing a block diagram of an exemplary access point (AP) according to the present disclosure.

Figure 1D

[0018] FIG. showing a block diagram of an exemplary station (STA) according to the present disclosure.

Figure 2A

[0019] FIG. showing an exemplary protocol data unit (PDU) that can be used for communication between an AP and several STAs according to the present disclosure.

Figure 2B

[0020] FIG. showing an exemplary field within the PDU of FIG. 2A according to the present disclosure.

Figure 3A

[0021] FIG. showing another exemplary PDU that can be used for communication between an AP and one or more STAs according to the present disclosure.

Figure 3B

[0022] FIG. showing another exemplary PDU that can be used for communication between an AP and one or more STAs according to the present disclosure.

Figure 4

[0023] FIG. showing an example of a target wake time according to the present disclosure.

Figure 5

[0024] A diagram showing an example of service periods (SPs) according to the present disclosure.

Figure 6

[0025] A diagram showing an example of EOSP timeout according to the present disclosure.

Figure 7

[0026] A diagram showing an example of SP cancellation using a reverse SP end (EOSP) instruction according to the present disclosure.

Figure 8

[0027] A diagram showing an example of using a reverse EOSP instruction according to the present disclosure.

Figure 9

[0028] A diagram showing an example of an extended reality topology according to the present disclosure.

Figure 10

Figure 11

[0029] A diagram showing an example of an extended personal area network topology according to the present disclosure.

Figure 12

Figure 13

[0030] A diagram showing an example of a power diagram according to the present disclosure.

Figure 14

[0031] A diagram showing an example of the impact of early SP cancellation on simultaneous operation according to the present disclosure.

Figure 15

[0032] A diagram showing an example of a comparison of EOSP cancellation techniques according to the present disclosure.

Figure 16A

[0033] A diagram showing a comparison of EOSP cancellation techniques according to the present disclosure.

Figure 16B

Figure 16C

Figure 17

[0034] A diagram showing an exemplary process performed, for example, by an access point according to the present disclosure.

Figure 18

[0035] FIG. showing an exemplary process executed, for example, by a station according to the present disclosure.

Figure 19

[0036] FIG. of an exemplary apparatus for wireless communication according to the present disclosure.

Figure 20

DETAILED DESCRIPTION OF THE INVENTION

[0017]

[0037] The following description is directed to several implementations for the purpose of describing innovative aspects of the present disclosure. However, one of ordinary skill in the art will readily recognize that the teachings herein can be applied in many different ways. The described implementations can be implemented, in particular, in any device, system, or network capable of transmitting and receiving radio frequency (RF) signals in accordance with one or more of the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards, IEEE 802.15 standards, the Bluetooth® standards defined by the Bluetooth Special Interest Group (SIG), or the Long Term Evolution (LTE), 3G, 4G, or 5G (New Radio (NR)) standards published by the 3rd Generation Partnership Project (3GPP). The described implementations can be implemented in any device, system, or network capable of transmitting and receiving RF signals in accordance with one or more of the following techniques or methods, namely, code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), single-user (SU) multiple-input multiple-output (MIMO), and multi-user (MU) MIMO.The described implementations may also be implemented using other wireless communication protocols or RF signals suitable for use in one or more of a wireless personal area network (WPAN), wireless local area network (WLAN), wireless wide area network (WWAN), or internet of things (IOT) network.

[0018]

[0038] Various aspects of the present disclosure are described in more detail below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout the present disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. It should be understood by those skilled in the art that the scope of the disclosure herein is intended to cover any aspect of the disclosure herein, regardless of whether it is implemented independently of or in combination with any other aspect of the disclosure. For example, any number of the aspects described herein can be used to implement an apparatus or practice a method. Additionally, the scope of the present disclosure is intended to cover such apparatus or methods practiced using other structures, functions, or structures and functions in addition to, or other than, the various aspects of the present disclosure described herein. It should be understood that any aspect of the present disclosure disclosed herein can be embodied by one or more elements of the claims.

[0019]

[0039] Next, some aspects of a telecommunications system are shown with reference to various devices and techniques. These devices and techniques are described in the context of implementing the following invention and are shown in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or as software depends on the specific application example and the design constraints imposed on the overall system.

[0020]

[0040] Aspects may be described herein using terms commonly associated with Institute of Electrical and Electronics Engineers (IEEE) standards (e.g., IEEE 802), or 5G or New Radio (NR) radio access technology (RAT), but aspects of the present disclosure can be applied to other RATs such as ultra-wideband (UWB) technology, 3G RAT, 4G RAT, and / or post-5G RAT (e.g., 6G).

[0021]

[0041] FIG. 1A shows a block diagram of an exemplary wireless communication network 100. According to some aspects, wireless communication network 100 can be an example of a wireless local area network (WLAN) such as a Wi-Fi network (also referred to hereinafter as WLAN 100). For example, WLAN 100 can be a network that implements at least one of the IEEE 802.11 standard family (including, but not limited to, those defined by its revisions such as the IEEE 802.11-2016 specification, or 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba, and 802.11be). WLAN 100 may include a number of wireless communication devices such as an access point (AP) 102 and a plurality of stations (STAs) 104. Although only one AP 102 is shown, WLAN network 100 may include multiple APs 102.

[0022]

[0042] Each of the STA104s, among other things, may also be referred to as a mobile station (MS), mobile device, mobile handset, wireless handset, access terminal (AT), user equipment (UE), subscriber station (SS), or subscriber unit. The STA104s, among other things, may particularly represent various devices such as mobile phones, personal digital assistants (PDAs), other handheld devices, netbooks, notebook computers, tablet computers, laptops, display devices (e.g., particularly TVs, computer monitors, navigation systems), music devices or other audio devices or stereo devices, remote control devices (“remotes”), printers, kitchen appliances or other household appliances, key fobs (e.g., for passive keyless entry and start (PKES) systems), etc.

[0023]

[0043] A single AP102 and an associated set of STAs104 may be referred to as a basic service set (BSS) managed by the respective AP102. FIG. 1A further shows an exemplary coverage area 105 of an AP102 that may represent the basic service area (BSA) of the WLAN100. A BSS may be identified to a user by a service set identifier (SSID) and to other devices by a basic service set identifier (BSSID), which may be the medium access control (MAC) address of the AP102. The AP102 periodically broadcasts a beacon frame (“beacon”) containing the BSSID so that any STA104 within the wireless range of the AP102 can “associate” or re-associate with the AP102 to establish or maintain a respective communication link 106 (hereinafter also referred to as a “Wi-Fi link”) with the AP102. For example, the beacon may include identification information of the primary channel used by the respective AP102 and a timing synchronization function for establishing or maintaining timing synchronization with the AP102. The AP102 may provide access to an external network to various STAs104 in the WLAN via the respective communication links 106.

[0024]

[0044] To establish a communication link 106 with an AP102, each of the STAs 104 is configured to perform a passive scan operation or an active scan operation ("scan") on a frequency channel in one or more frequency bands (e.g., 2.4 GHz, 5.0 GHz, 6.0 GHz, or 60 GHz band). To perform a passive scan, the STA 104 listens for beacons, which are transmitted by respective AP102s at periodic time intervals called target beacon transmission times (TBTTs) (measured in time units (TUs), where 1 TU may be equal to 1024 microseconds (μs)). To perform an active scan, the STA 104 generates probe requests, transmits them continuously on each channel to be scanned, and listens for probe responses from the AP102s. Each STA 104 may be configured to identify or select the AP102 to associate with based on the discovery information obtained through the passive scan or active scan, and perform an authentication operation and an association operation to establish a communication link 106 with the selected AP102. After authentication, the AP102 may assign an association identifier (AID) to each associated STA 104.

[0025]

[0045] As a result of the increasing pervasiveness of wireless networks, STA104 may have the opportunity to select one of many BSSs within the range of the STA, or to select from among a plurality of APs102 that together form an extended service set (ESS) including multiple connected BSSs. The extended network stations associated with WLAN100 may be connected to a wired or wireless distribution system that may enable multiple APs102 to be connected within such an ESS. Thus, STA104 can be covered by two or more APs102 and can be associated with different APs102 at different times for different transmissions. Additionally, after association with an AP102, STA104 can also be configured to periodically scan its surroundings to find a more suitable AP102 to associate with. For example, STA104 moving with respect to its associated AP102 may perform a "roaming" scan to find another AP102 with more desirable network characteristics such as a greater received signal strength indicator (RSSI) or reduced traffic load.

[0026]

[0046] In some cases, STA104 may form a network without involving AP102 or other devices other than STA104 itself. An example of such a network is an ad hoc network (or a wireless ad hoc network). An ad hoc network may alternatively be referred to as a mesh network or a peer-to-peer (P2P) network. In some cases, an ad hoc network may be implemented within a larger wireless network such as WLAN100. In such an implementation, STA104 may be able to communicate with each other through AP102 using communication link 106, but STA104 may also be able to communicate directly with each other via direct wireless link 108. Additionally, two STA104s may communicate via direct communication link 108 regardless of whether both STA104s are associated with and served by the same AP102. In such an ad hoc system, one or more of STA104 may assume the role fulfilled by AP102 within the BSS. Such STA104 may be referred to as a group owner (GO) and may coordinate transmissions within the ad hoc network. Examples of direct wireless link 108 include connections established by using Wi-Fi Direct connections, Wi-Fi Tunneled Direct Link Setup (TDLS) links, and other P2P group connections.

[0027]

[0047] AP102 and STA104 may function and communicate (via their respective communication links 106) in accordance with the IEEE 802.11 standard family (such as those defined by its revisions including, but not limited to, the IEEE 802.11-2016 specification, or 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba, and 802.11be). These standards define WLAN wireless and baseband protocols for the PHY layer and the Medium Access Control (MAC) layer. AP102 and STA104 send and receive wireless communication (hereinafter also referred to as "Wi-Fi communication") with each other in the form of Physical Layer Convergence Protocol (PLCP) Protocol Data Units (PPDUs). The AP102 and STA104 in the WLAN100 may transmit PPDUs via an unlicensed spectrum, which may be a portion of the spectrum including frequency bands conventionally used by Wi-Fi technologies such as the 2.4 GHz band, 5.0 GHz band, 60 GHz band, 3.6 GHz band, and 900 MHz band. Some implementations of the AP102 and STA104 described herein may also communicate in other frequency bands such as the 6.0 GHz band that may support both licensed and unlicensed communication. AP102 and STA104 may also be configured to communicate via other frequency bands such as shared licensed frequency bands where multiple operators may have permission to operate within the same or overlapping frequency bands.

[0028]

[0048] Each frequency band may include a plurality of sub - bands or frequency channels. For example, PPDUs compliant with the revised versions of the IEEE802.11n, 802.11ac, and 802.11ax standards may be transmitted on the 2.4GHz and 5.0GHz bands, each of which is divided into a plurality of 20MHz channels. Thus, these PPDUs are transmitted via physical channels having a minimum bandwidth of 20MHz, but larger channels can be formed through channel bonding. For example, a PPDU can be transmitted via a physical channel having a bandwidth of 40MHz, 80MHz, 160, or 320MHz by bonding a plurality of 20MHz channels together.

[0029]

[0049] Each PPDU is a composite structure that includes a PHY preamble and a payload in the form of a PLCP service data unit (PSDU). The information provided in the preamble may be used by the receiving device to decode the subsequent data in the PSDU. In cases where a PPDU is transmitted via a bonded channel, the preamble field may be replicated and transmitted in each of the plurality of component channels. The PHY preamble may include both a legacy part (or "legacy preamble") and a non - legacy part (or "non - legacy preamble"). The legacy preamble can be used, among other uses, for packet detection, automatic gain control, and channel estimation. The legacy preamble can also generally be used to maintain compatibility with legacy devices. The format, coding, and information provided in the non - legacy part of the preamble are based on the specific IEEE802.11 protocol that will be used to transmit the payload.

[0030]

[0050] Figure 1B shows a block diagram of an exemplary wireless communication device 110. In some implementations, the wireless communication device 110 can be an example of a device used in a STA such as one of the above STA104 with reference to Figure 1A. In some implementations, the wireless communication device 110 can be an example of a device used in an AP such as the above AP102 with reference to Figure 1A. The wireless communication device 110 is capable of transmitting (or outputting for transmission) and receiving wireless communication (e.g., in the form of wireless packets). For example, the wireless communication device can transmit and receive packets in the form of Physical Layer Convergence Protocol (PLCP) Protocol Data Units (PPDUs) and Medium Access Control (MAC) Protocol Data Units (MPDUs) compliant with the IEEE 802.11 standard, including but not limited to those defined by its revisions such as the IEEE 802.11-2016 specification, or 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba, and 802.11be.

[0031]

[0051] The wireless communication device 110 can be or include a chip, a system on chip (SoC), a chipset, a package, or a device that includes one or more modems 112, such as a Wi-Fi (IEEE 802.11 compliant) modem. In some implementations, the one or more modems 112 (collectively "modems 112") additionally include a WWAN modem (e.g., a 3GPP 4G LTE or 5G compliant modem). In some implementations, the wireless communication device 110 also includes one or more radios 114 (collectively "radios 114"). In some implementations, the wireless communication device 116 further includes one or more processors, processing blocks, or processing elements 116 (collectively "processor 116") and one or more memory blocks or memory elements 118 (collectively "memory 118").

[0032]

[0052] The modem 112 can include intelligent hardware blocks or devices, such as, among other things, an application-specific integrated circuit (ASIC). The modem 112 is generally configured to implement the PHY layer. For example, the modem 112 is configured to modulate packets and output the modulated packets to the radio 114 for transmission over the wireless medium. The modem 112 is similarly configured to obtain the modulated packets received by the radio 114 and demodulate the packets to provide the demodulated packets. In addition to the modulator and demodulator, the modem 112 may further include digital signal processing (DSP) circuitry, automatic gain control (AGC), a coder, a decoder, a multiplexer, and a demultiplexer. For example, during the transmit mode, the data obtained from the processor 116 is provided to the coder, which encodes the data to provide encoded bits. The encoded bits are then mapped to points within the modulation constellation (using the selected MCS) to provide modulated symbols. The modulated symbols are then N SS number of spatial streams or N STScan be mapped to a number of spatio-temporal streams. Then, the modulated symbols in each spatial stream or spatio-temporal stream are multiplexed, converted via an inverse fast Fourier transform (IFFT) block, and subsequently provided to a DSP circuit for Tx window processing and filtering. The digital signal can then be provided to a digital-to-analog converter (DAC). The resulting analog signal can then be provided to a frequency upconverter and ultimately to radio 114. In an implementation with beamforming, the modulated symbols in each spatial stream are precoded via a steering matrix before being provided to the IFFT block.

[0033]

[0053] While in the receive mode, the digital signal received from the radio 114 is provided to the DSP circuit, which is configured to acquire the received signal by, for example, detecting the presence of the signal and estimating the initial timing and frequency offset. The DSP circuit configuration is further configured to digitally condition the digital signal using, for example, channel (narrowband) filtering, analog impairment adjustment (such as correcting I / Q imbalance), and applying digital gain to ultimately obtain a narrowband signal. The output of the DSP circuit may then be supplied to the AGC, which is configured to use information extracted from the digital signal within one or more received training fields, for example, to determine an appropriate gain. The output of the DSP circuit is also coupled to a demodulator, which is configured to extract the modulated symbols from the signal and, for example, calculate the logarithm likelihood ratios (LLRs) for each bit position of each subcarrier in each spatial stream. The demodulator is coupled to a decoder, which may be configured to process the LLRs to provide decoded bits. The decoded bits from all of the spatial streams are then supplied to a demultiplexer for demultiplexing. The demultiplexed bits may then be descrambled and provided to the MAC layer (processor 116) for processing, evaluation, or interpretation.

[0034]

[0054] The radio 114 generally includes at least one radio frequency (RF) transmitter (or "transmitter chain") and at least one RF receiver (or "receiver chain"), which can be combined into one or more transceivers. For example, the RF transmitter and the RF receiver may each include various DSP circuits including at least one power amplifier (PA) and at least one low-noise amplifier (LNA). The RF transmitter and the RF receiver can then be coupled to one or more antennas. For example, in some implementations, the wireless communication device 110 may include or be coupled to a plurality of transmit antennas (each with a corresponding transmit chain) and a plurality of receive antennas (each with a corresponding receive chain). The symbols output from the modem 112 are provided to the radio 114, and then the radio 114 transmits the symbols via the coupled antennas. Similarly, the symbols received via the antennas are acquired by the radio 114, and then the radio 114 provides the symbols to the modem 112.

[0035]

[0055] Processor 116 can include an intelligent hardware block or device, such as, for example, a processing core, a processing block, a central processing unit (CPU), a microprocessor, a microcontroller, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. Processor 116 processes information received via radio 114 and modem 112 and processes information to be output via modem 112 and radio 114 for transmission over a wireless medium. For example, processor 116 may implement a control plane and a MAC layer configured to perform various operations related to the generation and transmission of MPDUs, frames, or packets. The MAC layer is configured to perform, or facilitate, among other operations or techniques, frame coding and decoding, spatial multiplexing, space-time block coding (STBC), beamforming, and OFDMA resource allocation. In some implementations, processor 116 can generally control modem 112 to cause the modem to perform the various operations described above.

[0036]

[0056] Memory 118 can include a tangible storage medium such as a random-access memory (RAM), a read-only memory (ROM), or a combination thereof. Memory 118 can also store non-transitory processor or computer-executable software (SW) code that, when executed by processor 116, causes the processor to perform various operations described herein for wireless communication, including generation, transmission, reception, and interpretation of MPDUs, frames, or packets. For example, the various functions of the components disclosed herein, or the various blocks or steps of the methods, operations, processes, or algorithms disclosed herein, can be implemented as one or more modules of one or more computer programs.

[0037]

[0057] FIG. 1C shows a block diagram of an exemplary AP120. For example, AP120 may be an exemplary implementation of AP102 described with reference to FIG. 1A. AP120 includes a wireless communication device (WCD) 122. For example, wireless communication device 122 may be an exemplary implementation of wireless communication device 110 described with reference to FIG. 1B. AP120 also includes a plurality of antennas 124 coupled to wireless communication device 122 for transmitting and receiving wireless communication. In some implementations, AP120 additionally includes an application processor 126 coupled to wireless communication device 122 and a memory 128 coupled to application processor 126. AP120 further includes at least one external network interface 130 that enables AP120 to communicate with a core network or a backhaul network to obtain access to an external network including the Internet. For example, external network interface 130 may include one or both of a wired (e.g., Ethernet) network interface and a wireless network interface (such as a WWAN interface). Some of the components described above can communicate directly or indirectly with some of the other components via at least one bus. AP120 further includes a housing that includes wireless communication device 122, application processor 126, memory 128, and at least a portion of antennas 124 and external network interface 130.

[0038]

[0058] In some aspects, AP120 may include a communication manager 132. As described in more detail elsewhere in this specification, the communication manager 132 may initiate a Target Wake Time (TWT) Service Period (SP). The communication manager 132 may receive a first End of Service Period (EOSP) indication from a station and, based on receiving the first EOSP indication, may stop the TWT SP before the scheduled end of the TWT SP. Additionally, or alternatively, the communication manager 132 may perform one or more other operations described herein.

[0039]

[0059] In some aspects, AP120 includes means for initiating a TWT SP, means for receiving a first EOSP indication from a station, and / or means for stopping the TWT SP before the scheduled end of the TWT SP based on receiving the first EOSP indication. In some aspects, the means by which AP120 performs the operations described herein may include, for example, one or more of communication manager 132, antenna 124, application processor 126, WCD 122, and / or memory 128.

[0040]

[0060] Figure 1D shows a block diagram of an exemplary STA140. For example, STA140 can be an exemplary implementation of STA104 described with reference to Figure 1A. STA140 includes a wireless communication device 142. For example, wireless communication device 142 can be an exemplary implementation of wireless communication device 110 described with reference to Figure 1B. STA140 also includes one or more antennas 144 coupled to wireless communication device 142 for transmitting and receiving wireless communication. Additionally, STA140 includes an application processor 146 coupled to wireless communication device 142 and a memory 148 coupled to application processor 146. In some implementations, STA140 further includes a user interface (UI) 150 (such as a touch screen or keypad) and a display 152, and display 152 can be integrated with UI150 to form a touch screen display. In some implementations, STA140 can further include one or more sensors 154, such as one or more inertial sensors, accelerometers, temperature sensors, pressure sensors, or altitude sensors. Some of the components described above can communicate directly or indirectly with some of the other components via at least one bus. STA140 further includes a housing that includes at least a portion of wireless communication device 142, application processor 146, memory 148, and antennas 144, UI150, and display 152.

[0041]

[0061] In some aspects, STA140 can include a communication manager 156. As described in more detail elsewhere in this specification, communication manager 156 can enter the TWT SP and transmit an EOSP indication to an access point before the scheduled end of the TWT SP. Additionally, or alternatively, communication manager 156 can perform one or more of the other operations described in this specification.

[0042]

[0062] In some aspects, STA140 includes means for entering the TWT SP and / or means for transmitting an EOSP indication to the access point before the scheduled end of the TWT SP. In some aspects, the means for STA140 to perform the operations described herein may include one or more of, for example, communication manager 156, antenna 144, application processor 146, WCD 142, and / or memory 148.

[0043]

[0063] As described above, FIGS. 1A-1D are provided as examples. Other examples may differ from those described with respect to FIGS. 1A-1D.

[0044]

[0064] FIG. 2A shows an exemplary protocol data unit (PDU) 200 that can be used for communication between an AP and several STAs. For example, PDU 200 may be configured as a PPDU. As shown, PDU 200 includes a PHY preamble 202 and a PHY payload 204. For example, PHY preamble 202 may include a legacy portion that itself includes a legacy short training field (L-STF) 206, a legacy long training field (L-LTF) 208, and a legacy signaling field (L-SIG) 210. PHY preamble 202 may also include a non-legacy portion (not shown). L-STF 206 generally enables a receiving device to perform automatic gain control (AGC), coarse timing estimation, and frequency estimation. L-LTF 208 generally enables a receiving device to perform fine timing estimation and frequency estimation and also to estimate a wireless channel. L-SIG 210 generally enables a receiving device to determine the duration of a PDU and use the determined duration to avoid transmitting on the PDU. For example, L-STF 206, L-LTF 208, and L-SIG 210 may be modulated according to a binary phase shift keying (BPSK) modulation scheme. Payload 204 may be modulated according to a BPSK modulation scheme, a quadrature BPSK (Q-BPSK) modulation scheme, a quadrature amplitude modulation (QAM) modulation scheme, or another suitable modulation scheme. Payload 204 generally may carry upper layer data, for example, in the form of a media access control (MAC) protocol data unit (MPDU) or an aggregated MPDU (A-MPDU).

[0045]

[0065] Figure 2B shows an exemplary L-SIG field 210 in the PDU of Figure 2A. The L-SIG 210 includes a data rate field 222, reserved bits 224, a length field 226, parity bits 228, and a tail field 230. The data rate field 222 indicates the data rate (note that the data rate indicated within the data rate field 222 may not be the actual data rate of the data carried within the payload 204). The length field 226 indicates the length of the packet, for example, in bytes. The parity bits 228 are used to detect bit errors. The tail field 230 includes tail bits used by the receiving device to terminate the operation of a decoder (e.g., a Viterbi decoder). The receiving device utilizes the data rate and length indicated in the data rate field 222 and the length field 226 to determine the duration of the packet, for example, in microseconds (μs).

[0046]

[0066] As described above, FIGS. 2A-2B provide examples. Other examples may differ from those described with respect to FIGS. 2A-2B.

[0047]

[0067] Figure 3A shows another exemplary PDU 300 that can be used for wireless communication between an AP and one or more STAs. The PDU 300 may be used for SU transmission, OFDMA transmission, or MU-MIMO transmission. The PDU 300 may be formatted as a High Efficiency (HE) WLAN PPDU according to the IEEE 802.11ax revision to the IEEE 802.11 wireless communication protocol standard. The PDU 300 includes a PHY preamble that includes a legacy portion 302 and a non-legacy portion 304. The PDU 300 may further include a PHY payload 306 after the preamble, for example, in the form of a PSDU that includes a data field 324.

[0048]

[0068] The legacy portion 302 of the preamble includes an L-STF 308, an L-LTF 310, and an L-SIG 312. The non-legacy portion 304 includes a repetition of the L-SIG (RL-SIG) 314, a first HE signal field (HE-SIG-A) 316, an HE short training field (HE-STF) 320, and one or more HE long training fields (or symbols) (HE-LTFs) 322. In the case of OFDMA communication or MU-MIMO communication, the second portion 304 further includes a second HE signal field (HE-SIG-B) 318 encoded separately from the HE-SIG-A 316. In cases involving the use of a bonded channel, such as the L-STF 308, L-LTF 310, and L-SIG 312, the information within the RL-SIG 314 and HE-SIG-A 316 may be replicated and transmitted in each of the 20 MHz component channels. In contrast, the content of the HE-SIG-B 318 may be specific to each 20 MHz channel and the particular STA 104 targeted.

[0049]

[0069] RL-SIG314 may indicate to the HE-compatible STA104 that the PDU300 is a HE PPDU. The AP102 may use the HE-SIG-A316 to identify a plurality of STAs104 and inform the plurality of STAs104 that the AP has scheduled UL or DL resources for the plurality of STAs104. For example, the HE-SIG-A316 may include a resource allocation subfield indicating the resource allocation for the identified STA104. The HE-SIG-A316 may be decoded by each HE-compatible STA104 served by the AP102. In the case of MU transmission, the HE-SIG-A316 further includes information available for use by each identified STA104 to decode the associated HE-SIG-B318. For example, the HE-SIG-A316 may indicate a frame format including, among other things, the position and length of the HE-SIG-B318, the available channel bandwidth, and the modulation and coding scheme (MCS). The HE-SIG-A316 may also include HE WLAN signaling information available for use by STAs104 other than the identified STA104.

[0050]

[0070] HE-SIG-B318 can carry STA-specific scheduling information such as, for example, the STA-specific (or "user-specific") MCS value and STA-specific RU allocation information. In the context of DL MU-OFDMA, such information enables each STA104 to identify and decode the corresponding resource units (RUs) within the associated data field 324. Each HE-SIG-B318 includes a common field and at least one STA-specific field. The common field indicates, among other things, the RU allocation for a plurality of STAs104 including the RU assignment in the frequency domain, which RUs are allocated for MU-MIMO transmission, which RUs correspond to MU-OFDMA transmission, and the number of users in the allocation. The common field may be encoded with common bits, CRC bits, and tail bits. The user-specific field is assigned to a specific STA104 and may be used to schedule the specific RUs and indicate the scheduling to other WLAN devices. Each user-specific field may include a plurality of user block fields. Each user block field may include two user fields containing information for two respective STAs for decoding each RU payload within the data field 324.

[0051]

[0071] Figure 3B shows another exemplary PPDU 350 that can be used for wireless communication between an AP and one or more STAs. The PDU 350 may be used for SU transmission, OFDMA transmission, or MU-MIMO transmission. The PDU 350 may be formatted as an Extreme High Throughput (EHT) WLAN PPDU according to the IEEE 802.11be revision to the IEEE 802.11 wireless communication protocol standard, or as a PPDU compliant with any subsequent (post-EHT) version of a new wireless communication protocol compliant with a future IEEE 802.11 wireless communication protocol standard or other wireless communication standards. The PDU 350 includes a PHY preamble that includes a legacy portion 352 and a non-legacy portion 354. The PDU 350 may further include a PHY payload 356 after the preamble, in the form of a PSDU that includes, for example, a data field 374.

[0052]

[0072] The legacy portion 352 of the preamble includes an L-STF 358, an L-LTF 360, and an L-SIG 362. The non-legacy portion 354 of the preamble includes an RL-SIG 364 and a plurality of wireless communication protocol version-dependent signal fields following the RL-SIG 364. For example, the non-legacy portion 354 may include a general-purpose signal field 366 (referred to herein as "U-SIG 366") and an EHT signal field 368 (referred to herein as "EHT-SIG 368"). One or both of the U-SIG 366 and the EHT-SIG 368 may be configured as other wireless communication protocol versions after EHT and may carry version-dependent information therefor. The non-legacy portion 354 further includes an additional short training field 370 (referred to herein as "EHT-STF 370" which may be constructed as other wireless communication protocol versions after EHT and may carry version-dependent information therefor), and one or more additional long training fields 372 (referred to herein as "EHT-LTF 372" which may be constructed as other wireless communication protocol versions after EHT and may carry version-dependent information therefor). In cases involving the use of a bonded channel, such as the L-STF 358, the L-LTF 360, and the L-SIG 362, the information within the U-SIG 366 and the EHT-SIG 368 may be replicated and transmitted in each of the 20 MHz component channels. In some implementations, the EHT-SIG 368 may, additionally or alternatively, carry information different from the information carried in the 20 MHz primary channel in one or more 20 MHz non-primary channels.

[0053]

[0073] The EHT-SIG368 may include one or more jointly encoded symbols and may be encoded in a block different from the block in which the U-SIG366 is encoded. The EHT-SIG368 may be used by the AP to identify a plurality of STAs104 and inform the plurality of STAs104 that the AP has scheduled UL or DL resources for the plurality of STAs104. The EHT-SIG368 may be decoded by each compatible STA104 served by the AP102. The EHT-SIG368 may generally be used by the receiving device to interpret bits within the data field 374. For example, the EHT-SIG368 may include, among other examples, RU allocation information, spatial stream configuration information, and per-user signaling information such as MCS. The EHT-SIG368 may further include a cyclic redundancy check (CRC) (e.g., 4 bits) and a tail (e.g., 6 bits) that may be used for a binary convolutional code (BCC). In some implementations, the EHT-SIG368 may include one or more code blocks each including a CRC and a tail. In some aspects, each of the code blocks may be encoded separately.

[0054]

[0074] The EHT-SIG368 can carry STA-specific scheduling information such as, for example, user-specific MCS values and user-specific RU allocation information. The EHT-SIG368 can generally be used by a receiving device to interpret bits within the data field 374. In the context of DLMU-OFDMA, such information enables each STA104 to identify and decode the corresponding RU within the associated data field 374. Each EHT-SIG368 may include a common field and at least one user-specific field. The common field can indicate, among other examples, RU distribution for multiple STAs104, RU allocation in the frequency domain, which RUs are allocated for MU-MIMO transmission, which RUs correspond to MU-OFDMA transmission, and the number of users in the allocation. The common field may be encoded with common bits, CRC bits, and tail bits. The user-specific field is allocated to a specific STA104 and may be used to schedule a specific RU and indicate the scheduling to other WLAN devices. Each user-specific field may include a plurality of user block fields. Each user block field may include, for example, two user fields containing information for two respective STAs for decoding each respective RU payload.

[0055]

[0075] The presence of the RL-SIG364 and U-SIG366 can indicate to an STA104 compliant with EHT or a later version that the PPDU350 is an EHT PPDU or a PPDU compliant with any subsequent (post-EHT) version of a new wireless communication protocol compliant with the future IEEE802.11 wireless communication protocol standard. For example, the U-SIG366 can be used by a receiving device to interpret bits within one or more of the EHT-SIG368 or the data field 374.

[0056]

[0076] As described above, FIGS. 3A-3B provide some examples. Other examples may differ from those described with respect to FIGS. 3A-3B.

[0057]

[0077] FIG. 4 is a diagram showing an example 400 of a TWT according to the present disclosure.

[0058]

[0078] An AP (e.g., AP120), such as a service or software AP (SAP), may use TWT to reduce power consumption for latency-sensitive and power-constrained wireless devices. The TWT can be the duration that a requesting station (e.g., STA1) is in an awake state for activities (e.g., for periodic data transmission). STA1 (e.g., STA140) may otherwise be in a sleep state. The TWT can be configured or negotiated and used for applications such as extended reality (XR) applications and / or PAN applications.

[0059]

[0079] At the beginning of the opportunity of the time interval or service period, for example, at the beginning of the TBTT, the SAP may operate during a broadcast core network (BCN) period. The BCN may include multi-cast (MC) or broadcast (BC) messages. The SAP may then proceed to the broadcast TWT period and then to the individual TWT period. The SP starts at the beginning of the individual TWT period (SP start) and may end at the end of the individual TWT period (SP end), and thus may be referred to as "TWT SP". The SP end of the TWT SP may be a scheduled end scheduled to end after a set amount of time from the SP start of the WT SP. That is, the scheduled end may be a set end that follows a set duration or amount of time for the TWT SP. For example, the scheduled end of the TWT SP may be based on the expiration of a timer that starts at the SP start. The station may be in an awake state during the BCN period and may be in a sleep state during the broadcast TWT period.

[0060]

[0080] During the TWT SP of SAP and the TWT SP of STA1, SAP may send a quality of service (QoS) data message or a QoS null message (no data). STA1 may send an acknowledgment (ACK), a block ACK (BA), or a multi-block ACK (MBA) for such a QoS message. STA1 may also send a QoS data message or a QoS null message. As shown in Example 400, SAP may send an EOSP message having a field equal to 1 (for example, when there is no data to be sent). STA1 may enter the sleep (doze) mode after receiving the EOSP message, whichever occurs first, or after a duration (for example, AdjustedMinimumTWTWakeDuration) has elapsed from the TWT SP start time as identified by STA1. STA1 may also cancel its TWT SP. However, SAP does not cancel its TWT SP until after an inactivity timeout (ITO).

[0061]

[0081] As described above, FIG. 4 is provided as an example. Other examples may differ from those described with respect to FIG. 4.

[0062]

[0082] FIG. 5 is a diagram showing Example 500 of an SP according to the present disclosure.

[0063]

[0083] Example 500 shows a plurality of TBTTs each having a TWT SP. The service interval can extend from the start of one TWT SP to the start of the next TWT SP. The smaller the service interval, the lower the latency but the higher the power consumption. The larger the service interval, the lower the power consumption but the higher the latency.

[0064]

[0084] STA1 and STA2 can be the requesting stations, and SAP can be the responding station. SAP can send QoS messages and EOSPs to STA1 and STA2. For example, SAP can send EOSP502 to STA2, and STA2 can enter the sleep mode. EOSP504 and EOSP506 are other examples of EOSPs. However, under this configuration, SAP cannot release the TWT SP before the scheduled end of the TWT SP (e.g., when the EOSP is one-way only from SAP to the station). SAP also cannot perform off-channel or simultaneous operations. This reduces the dwell time, which is already limited. SAP is also expected to stay in the awake state to receive traffic external to the SP. In each scenario, SAP can consume more power than necessary.

[0065]

[0085] As described above, FIG. 5 is provided as an example. Other examples may differ from those described with respect to FIG. 5.

[0066]

[0086] FIG. 6 is a diagram showing an example 600 of EOSP timeout according to the present disclosure.

[0067]

[0087] Example 600 shows two SPs for SAP for two TBTTs, TBTT602 and TBTT604. During the active part of the SP for TBTT602, SAP can send a QoS data message having a first packet (packet 1) to STA1. SAP can receive an ACK for packet 1. SAP can send a QoS data message having packet 1 to STA2. The QoS messages are in bold, indicating that they can each include an EOSP instruction to cause the respective station to enter the sleep mode. SAP can receive an ACK for this packet 1 during the listening part of the SP, which starts an inactivity timer. Note that since the ACK from the station cannot include an EOSP instruction, the ACK is not in bold.

[0068]

[0088] If there is no data to be transmitted and no data is received from any station, the SP may time out after ITO, and as a result, the listening part of the SP for the SAP ends. Now that the SP has timed out, the SAP may enter the idle mode, effectively releasing the SP. The minimum configurable ITO in the SAP software can be 1 millisecond (ms). In the case of game traffic in an extended PAN (XPAN), the TWT SP can be 2 ms, and the traffic is expected to last between 0.5 and 1 ms. Therefore, for most SPs, it may not even be feasible to release the SP using ITO. Furthermore, ITO is prone to errors and is not optimal for all SP configurations. During the TBTT 604, ITO can start after sending a QoS message. However, ITO can be cancelled when an uplink message is received and an ACK is sent. ITO can then resume and end before the idle period for the SP. Starting, stopping, and resuming the inactive timer can consume additional processing resources and add latency.

[0069]

[0089] As described above, FIG. 6 is provided as an example. Other examples may be different from those described with respect to FIG. 6.

[0070]

[0090] FIG. 7 is a diagram showing an example 700 of SP release using a reverse direction EOSP indication according to the present disclosure.

[0071]

[0091] According to various aspects described herein, the station may send an EOSP indication (e.g., a reverse EOSP indication) to the SAP. Thus, the SAP may receive information indicating the end of the SP that would otherwise not be noticed by the SAP. Receiving this information may enable the SAP to stop the TWT SP before the scheduled end of the TWT SP. Thus, the SAP may save energy by stopping the TWT SP earlier than scheduled (e.g., entering sleep mode, refraining from transmitting or receiving). Additionally, or alternatively, the SAP may perform off-channel or co-channel operations between the reception of the first EOSP indication (release of the TWT SP) and the scheduled end of the TWT SP by stopping the TWT SP earlier than scheduled, thereby improving network performance by reallocating resources for communication.

[0072]

[0092] According to various aspects described herein, each station may send an EOSP indication to the SAP. The station may send an EOSP, for example, when there is no further data to be sent. This EOSP from the station may be referred to as a "reverse EOSP indication". This is because the reverse EOSP indication is in the opposite direction of the existing EOSP that only comes from the SAP. When the SAP receives an EOSP from each station that the SAP is connected to and associated with the TWT SP, the SAP may stop (release) the TWT SP and enter the sleep or idle mode. This release may also be referred to as "grant-based EOSP release" or "GeoSP release". The reverse EOSP may be part of a write handshake between the SAP and the station where a message is sent and an ACK is returned. That is, the reverse EOSP may be included with the existing signaling. For example, the SAP may send a QoS data message to STA2, and STA2 may send an EOSP indication 702 to the SAP along with the ACK. The EOSP indication 702 may share a frame with the ACK, be multiplexed with the ACK, or be included within a frame configured for the ACK. No new signal is required for the EOSP indication 702. In some aspects, STA2 may repurpose the EOSP subfield within the QoS control field of the QoS data frame or QoS null frame as a request to release the SP. The request may claim a response. STA2 may repurpose an existing field or reserved field within the ACK / BA / MBA to positively respond to the SP release. This helps avoid another explicit frame exchange sequence as part of the handshake mechanism. In some aspects, STA2 may use an information element (IE) during TWT setup or association to specify the use of the reverse EOSP indication and / or the repurposing of fields within the QoS data frame, QoS null frame, and / or ACK / BA / MBA. Alternatively, STA1 may send the EOSP indication in a frame separate from the ACK, BA, or MBA.

[0073]

[0093] In some aspects, the station may send an EOSP indication within a QoS data message or a QoS null message. Example 700 shows an EOSP indication 704 included with a UL QoS data message. All of the messages in Example 700, for both uplink and downlink, are in bold to indicate that any of these messages may include an EOSP indication. In short, if the SAP receives EOSP from all stations, the SAP may sleep. If a station receives EOSP from the SAP, the station may sleep. The station may wait for EOSP before sleeping.

[0074]

[0094] Before the end of the TWT SP (and earlier than the ITO), by entering sleep or idle mode with a deterministic EOSP, the SAP saves more power. The SAP may also perform off-channel operations (e.g., communication on a different channel separate from the stations) or concurrent operations (e.g., switching to another link) earlier. That is, a station may send EOSP as new signaling, whereby EOSP is sent not only from the SAP but also by both the SAP and the stations. When EOSP is received from all stations associated with the TWT SP, the SAP may release that TWT SP early.

[0075]

[0095] In some aspects, the SAP may conserve energy (e.g., enter sleep mode, refrain from transmitting or receiving) or perform off-channel or concurrent operations between the receipt of the first EOSP indication (release of the TWT SP) and the scheduled end of the TWT SP. The SAP may also continue to conserve energy or perform other operations between the scheduled end of the TWT SP and the start of the next TWT SP. The start of the next TWT SP may be after the end of the service interval.

[0076]

[0096] As described above, FIG. 7 is provided as an example. Other examples may be different from those described with respect to FIG. 7.

[0077]

[0097] FIG. 8 is a diagram showing an example 800 associated with using a reverse direction EOSP indication according to the present disclosure. As shown in FIG. 8, an access point such as SAP810 (e.g., AP120) may initiate TWT SP812. SAP810 may communicate with a station such as STA820 (e.g., STA140). STA820 may initiate TWT SP822. SAP810 may also communicate with other stations such as STA830 (TWT SP832) and STA840 (TWT SP842).

[0078]

[0098] After any data transfer, the station may have no further data to send and may send a reverse direction EOSP indication as indicated by reference numerals 845, 850, and 855. For example, STA820 may send a reverse direction EOSP to SAP810 based on STA820 having completed the transmission of data and / or having no (further) data to send at all. SAP810 may also send an EOSP indication to the station as indicated by reference numeral 860 if there is no further data to be sent to the station. As indicated by reference numeral 865, the station may release their respective TWT SPs. For example, each station may release its respective TWT SP based on receiving an EOSP indication from SAP10 and having no (further) data to send at all. As indicated by reference numeral 870, SAP810 may release TWT SP812 based on receiving EOSP indications from all of the stations. For example, SAP810 may determine whether EOSP indications have been received from each station (e.g., STA820, STA830, and STA840). If EOSP indications have not been received from each station (e.g., if received from fewer stations than all of the stations associated with or connected to SAP810), then at this time, SAP810 may continue TWT SP812. For example, if EOSP is not received from each station before the scheduled end of TWT SP812, SAP810 may continue TWT SP812 until the scheduled end of TWT SP812 without performing an early release. If EOSP indications have been received from each station (e.g., if received from all of the stations associated with or connected to SAP810), then at this time, SAP810 may release TWT SP812 (e.g., before the scheduled end of TWT SP812).

[0079]

[0099] In some embodiments, a reverse direction EOSP instruction is received via a software application or a service application, and the TWT SP release is performed. In some embodiments, a reverse direction EOSP instruction is received via a configured component (e.g., hardware, firmware).

[0080]

[0100] FIG. 8 shows an example where each reverse direction EOSP instruction is transmitted before the EOSP instruction from SAP810, but it should be understood that this signaling ordering is not limited to this particular example, and the reverse direction EOSP instruction and the EOSP instruction can be transmitted in other orders.

[0081]

[0101] As described above, FIG. 8 is provided as an example. Other examples may be different from those described with respect to FIG. 8.

[0082]

[0102] FIG. 9 is a diagram showing an example 900 of an XR topology according to the present disclosure.

[0083]

[0103] The reverse direction EOSP instruction can be used in various XR scenarios. Example 900 shows some exemplary XR topologies that may include an augmented reality (AR) application where data is transmitted, for example, between an AP and a smartphone (or other type of computer), as well as between the smartphone and a peripheral device such as AR or XR glasses. For example, as shown by topology 1, the AP can play the role of SAP810 as described with respect to FIGS. 7 and 8, and the smartphone can play the role of the local station. Alternatively, the smartphone (encircled) can play the role of the SAP, and the glasses can play the role of the local station. As shown by topology 2, when cloud computing is involved, the smartphone (encircled) between the AP and the glasses can play the role of SAP810.

[0084]

[0104] As described above, FIG. 9 is provided as an example. Other examples may be different from those described with respect to FIG. 9.

[0085]

[0105] Figure 10 is a diagram showing Example 1000 of a further XR topology according to the present disclosure.

[0086]

[0106] Example 1000 shows Topology 3 in which various combinations of devices can perform the role of SAP810 or STA820 described with respect to FIGS. 8 and 8. A smartphone (encircled) can perform the role of SAP810 that receives a reverse EOSP instruction.

[0087]

[0107] As described above, FIG. 10 is provided as an example. Other examples may differ from those described with respect to FIG. 10.

[0088]

[0108] Figure 11 is a diagram showing Example 1100 of an XPAN topology according to the present disclosure.

[0089]

[0109] The reverse EOSP instruction can be used in various XPAN scenarios that can use some Bluetooth® protocols indicated by "BT" within an exemplary topology. Stations such as STA820 described with respect to FIGS. 7 and 8 can include smartphones and / or earphones (encircled). The earphones can include primary (P) earphones and secondary (S) earphones. The smartphone can also perform the role of an AP such as SAP810.

[0090]

[0110] As described above, FIG. 11 is provided as an example. Other examples may differ from those described with respect to FIG. 11.

[0091]

[0111] Figure 12 is a diagram showing Example 1200 of a further XPAN topology according to the present disclosure.

[0092]

[0112] The reverse-direction EOSP indication can be used in various other XPAN scenarios, such as those having a plurality of smartphones and earphones operating using full wireless (true wireless, TWS) techniques. More likely scenarios for the reverse-direction EOSP indication are circled.

[0093]

[0113] As described above, FIG. 12 is provided as an example. Other examples may be different from those described with respect to FIG. 12.

[0094]

[0114] FIG. 13 is a diagram showing an example 1300 of a power diagram according to the present disclosure.

[0095]

[0115] Example 1300 shows a power diagram in which power savings can be made. Potential power savings can be made after early release (reverse-direction EOSP). There may be an unused dwell period.

[0096]

[0116] As described above, FIG. 13 is provided as an example. Other examples may be different from those described with respect to FIG. 13.

[0097]

[0117] FIG. 14 is a diagram showing an example 1400 of the impact of early SP release on simultaneous operation according to the present disclosure.

[0098]

[0118] Example 1400 is another diagram showing an unused dwell period. The unused dwell period can be the duration that could have been used by the infra link (along with early release on the XR or XPAN link). This can be about 50% of the negotiated SP (which is 1 ms) for game traffic. There may be a 2-3 ms clear to send (CTS) (CTS to self) period to enter the XR or XPAN interval. There may be a contention free (CF) end to exit the XR or XPAN interval.

[0099]

[0119] As described above, FIG. 14 is provided as an example. Other examples may differ from those described with respect to FIG. 14.

[0100]

[0120] FIG. 15 is a diagram showing Example 1500 of a comparison of EOSP release techniques according to the present disclosure.

[0101]

[0121] Example 1500 shows a table associated with FIGS. 16a, 16B, and 16C. The table may summarize a radio frame exchange sequence for signaling reverse direction EOSP indications. If there is no downlink (DL) traffic from the AP to the station or no uplink (UL) traffic from the station to the AP, the software implementation may use DL and UL QoS null messages for reverse direction EOSP (without making hardware changes). A hardware implementation (e.g., a configured component) may use the DL QoS null message.

[0102]

[0122] If only DL traffic exists, the software implementation may use the UL QoS null message for reverse direction EOSP indication, and the hardware implementation may use the UL ACK / BA for reverse direction EOSP indication.

[0103]

[0123] If only UL traffic exists, the software implementation may use the DL QoS null message for reverse direction EOSP indication, and the hardware implementation may use the DL ACK / BA for reverse direction EOSP indication.

[0104]

[0124] If both DL and UL traffic exist, the software implementation may use the last data packet or frame for reverse direction EOSP indication, and the hardware implementation may use the ACK / BA or the last packet or frame for reverse direction EOSP indication.

[0105]

[0125] As described above, FIG. 15 is provided as an example. Other examples may be different from those described with respect to FIG. 15.

[0106]

[0126] FIGS. 16A, 16B, and 16C are diagrams showing a comparison of EOSP release techniques according to the present disclosure.

[0107]

[0127] FIG. 16A shows current signaling without a reverse EOSP indication. A value of 1 in the EOSP field indicates EOSP. There is no reverse EOSP indication. FIG. 16B shows an example of a software implementation of the reverse EOSP indication described with respect to FIG. 15. FIG. 16C shows an example of a hardware implementation of the reverse EOSP indication described with respect to FIG. 15.

[0108]

[0128] As described above, FIGS. 16B and 16C provide examples. Other examples may be different from those described with respect to FIG. 16.

[0109]

[0129] FIG. 17 is a diagram showing an exemplary process 1700 executed by, for example, an access point according to the present disclosure. The exemplary process 1700 is an example in which an access point (e.g., SAP810) performs operations associated with a reverse EOSP indication.

[0110]

[0130] As shown in FIG. 17, in some aspects, process 1700 may include starting a TWT SP (block 1710). For example, the access point may start the TWT SP as described above (e.g., using communication manager 1908 and / or service period component 1910 shown in FIG. 19).

[0111]

[0131] As further shown in FIG. 17, in some aspects, process 1700 may include receiving a first EOSP indication from a station (block 1720). For example, an access point may receive a first EOSP indication from a station (e.g., using communication manager 1908 and / or receiving component 1902 shown in FIG. 19) as described above.

[0112]

[0132] As further shown in FIG. 17, based on receiving the first EOSP indication, process 1700 may include stopping the TWT SP before the scheduled end of the TWT SP (block 1730). For example, an access point may stop the TWT SP before the scheduled end of the TWT SP based on receiving the first EOSP indication (e.g., using communication manager 1908 and / or service period component 1910 shown in FIG. 19) as described above.

[0113]

[0133] Process 1700 may include additional aspects such as any single aspect or any combination of aspects described in connection with one or more other processes described below and / or elsewhere in this specification.

[0114]

[0134] In a first aspect, receiving the first EOSP indication includes receiving the first EOSP indication in a frame shared with an ACK, BA, or MBA.

[0115]

[0135] In a second aspect, alone or in combination with the first aspect, receiving the first EOSP indication includes receiving the first EOSP indication multiplexed with an ACK, BA, or MBA.

[0116]

[0136] In a third aspect, alone or in combination with one or more of the first and second aspects, receiving the first EOSP indication includes receiving the first EOSP indication in a frame shared with a QoS null message or configured for a QoS null message.

[0117]

[0137] In a fourth aspect, receiving the first EOSP indication, alone or in combination with one or more of the first to third aspects, includes receiving the first EOSP indication within a frame shared with or configured for a QoS data message.

[0118]

[0138] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, a QoS data message is associated with an XR application or a PAN application.

[0119]

[0139] In a sixth aspect, receiving the first EOSP indication, alone or in combination with one or more of the first to fifth aspects, includes receiving the first EOSP indication within a frame separate from a QoS message, ACK, BA, or MBA.

[0120]

[0140] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, process 1700 includes entering a sleep state or refraining from transmitting or receiving between receiving the first EOSP indication and the scheduled end of the TWT SP.

[0121]

[0141] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, process 1700 includes remaining in a sleep state or further refraining from transmitting or receiving between the scheduled end of the TWT SP and the start of the next TWT SP.

[0122]

[0142] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, process 1700 includes operating in an off-channel or concurrent mode between receiving the first EOSP indication and the scheduled end of the TWT SP.

[0123]

[0143] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, process 1700 includes further functioning in an off-channel or co-operative mode between the scheduled end of the TWT SP and the start of the next TWT SP.

[0124]

[0144] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, receiving a first EOSP indication includes receiving the first EOSP indication in a service application of an access point.

[0125]

[0145] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, receiving a first EOSP indication includes receiving the first EOSP indication via a configured component.

[0126]

[0146] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, process 1700 includes receiving a second EOSP indication, and stopping the TWT SP includes stopping the TWT SP based on receiving both the first EOSP indication and the second EOSP indication.

[0127]

[0147] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, process 1700 includes receiving an EOSP indication from each station connected to the access point and associated with the TWT SP, and stopping the TWT SP includes stopping the TWT SP based on receiving EOSP indications from all stations connected to the access point and associated with the TWT SP.

[0128]

[0148] FIG. 17 shows exemplary blocks of process 1700, but in some aspects, process 1700 may include additional blocks, fewer blocks, different blocks, or differently configured blocks compared to the blocks shown in FIG. 17. Additionally, or alternatively, two or more of the blocks of process 1700 may be executed in parallel.

[0129]

[0149] FIG. 18 is a diagram illustrating an exemplary process 1800, such as may be performed by a station, according to the present disclosure. The exemplary process 1800 is an example where a station (e.g., STA 820) performs operations associated with a reverse direction EOSP indication.

[0130]

[0150] As shown in FIG. 18, in some aspects, process 1800 may include entering the TWT SP (block 1810). For example, a station may enter the TWT SP as described above (e.g., using communication manager 2008 and / or service period component 2010 shown in FIG. 20).

[0131]

[0151] As further shown in FIG. 18, in some aspects, process 1800 may include transmitting an EOSP indication to an access point before a scheduled end of the TWT SP (block 1820). For example, a station may transmit an EOSP indication to an access point before a scheduled end of the TWT SP as described above (e.g., using communication manager 2008 and / or transmission component 2004 shown in FIG. 20).

[0132]

[0152] Process 1800 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in relation to one or more other processes described elsewhere in this specification.

[0133]

[0153] In a first aspect, transmitting an EOSP indication includes transmitting the EOSP indication based on there being no data prepared for transmission.

[0134]

[0154] In a second aspect, alone or in combination with the first aspect, process 1800 receives a forward EOSP instruction and, based on receiving the forward EOSP instruction, includes stopping the TWT SP.

[0135]

[0155] In a third aspect, alone or in combination with one or more of the first and second aspects, transmitting an EOSP instruction includes transmitting the EOSP instruction within a frame shared with an Ack, BA, or MBA.

[0136]

[0156] In a fourth aspect, alone or in combination with one or more of the first to third aspects, transmitting an EOSP instruction includes transmitting an EOSP instruction multiplexed with an ACK, BA, or MBA.

[0137]

[0157] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, transmitting an EOSP instruction includes transmitting the EOSP instruction within a frame shared with a QoS null message or configured for a QoS null message.

[0138]

[0158] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, transmitting an EOSP instruction includes transmitting the EOSP instruction within a frame shared with a QoS data message or configured for a QoS data message.

[0139]

[0159] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the frame is the last frame in which data is present.

[0140]

[0160] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the data is associated with an extended reality application or a personal area network application.

[0141]

[0161] In a ninth aspect, sending an EOSP indication, either alone or in combination with one or more of the first to eighth aspects, includes sending the EOSP indication within a frame that is separate from a QoS message, ACK, BA, or MBA.

[0142]

[0162] FIG. 18 shows exemplary blocks of process 1800, but in some aspects, process 1800 may include additional blocks, fewer blocks, different blocks, or differently configured blocks compared to the blocks shown in FIG. 18. Additionally, or alternatively, two or more of the blocks of process 1800 may be executed in parallel.

[0143]

[0163] FIG. 19 is a diagram of an exemplary apparatus 1900 for wireless communication. The apparatus 1900 can be an access point (e.g., AP 120, SAP 810), or the access point can include the apparatus 1900. In some aspects, the apparatus 1900 includes a receiving component 1902 and a transmitting component 1904 that can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 1900 can communicate with another apparatus 1906 (such as a UE, a base station, a network entity, a station, an access point, or another wireless communication device) using the receiving component 1902 and the transmitting component 1904. Further shown, the apparatus 1900 can include a communication manager 1908. The communication manager 1908 can control and / or otherwise manage one or more operations of the receiving component 1902 and / or the transmitting component 1904. In some aspects, the communication manager 1908 can include one or more antennas, modems, controllers / processors, memories, or combinations thereof of the AP described in connection with FIG. 1C. The communication manager 1908 can be or be similar to the communication manager 132 shown in FIG. 1C. For example, in some aspects, the communication manager 1908 can be configured to perform one or more of the functions described as being performed by the communication manager 132. In some aspects, the communication manager 1908 can include the receiving component 1902 and / or the transmitting component 1904. The communication manager 1908 can include, among other examples, a service duration component 1910.

[0144]

[0164] In some aspects, apparatus 1900 may be configured to perform one or more operations described herein with respect to FIGS. 1-16. Additionally, or alternatively, apparatus 1900 may be configured to perform one or more processes described herein, such as process 1700 of FIG. 17. In some aspects, apparatus 1900 and / or one or more components shown in FIG. 19 may include one or more components of the access point described with respect to FIG. 1C. Additionally, or alternatively, one or more components shown in FIG. 19 may be implemented within one or more components described with respect to FIG. 1C. Additionally, or alternatively, one or more components of a set of components may be implemented at least in part as software stored in memory. For example, a component (or a portion of a component) may be stored in a non-transitory computer-readable medium and implemented as instructions or code executable by a controller or processor to perform the functions or operations of the component.

[0145]

[0165] Receiving component 1902 may receive communications, such as a reference signal, control information, data communication, or a combination thereof, from apparatus 1906. Receiving component 1902 may provide the received communications to one or more other components of apparatus 1900. In some aspects, receiving component 1902 may perform signal processing (such as, among other examples, filtering, amplification, demodulation, analog-to-digital conversion, de-multiplexing, de-interleaving, demapping, equalization, interference cancellation, or decoding) on the received communications and provide the processed signals to one or more other components of apparatus 1900. In some aspects, receiving component 1902 may include one or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories, or combinations thereof of the access point described with respect to FIG. 1C.

[0146]

[0166] The transmitting component 1904 may transmit communications such as a reference signal, control information, data communication, or a combination thereof to the device 1906. In some aspects, one or more other components of the device 1900 may generate the communication and provide the generated communication to the transmitting component 1904 for transmission to the device 1906. In some aspects, the transmitting component 1904 may perform signal processing on the generated communication (such as, among other examples, filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding), and transmit the processed signal to the device 1906. In some aspects, the transmitting component 1904 may include one or more antennas, a modem, a modulator, a transmitting MIMO processor, a transmitting processor, a controller / processor, a memory, or a combination thereof of the access points described with respect to FIG. 1C. In some aspects, the transmitting component 1904 may be co-located with the receiving component 1902 in a transceiver.

[0147]

[0167] The service period component 1910 may initiate the TWT SP. The receiving component 1902 may receive a first EOSP indication from the station. Based on receiving the first EOSP indication, the service period component 1910 may stop the TWT SP before the scheduled end of the TWT SP.

[0148]

[0168] The transmitting component 1904 and the receiving component 1902 may enter a sleep state or refrain from transmitting or receiving between receiving the first EOSP indication and the scheduled end of the TWT SP. The transmitting component 1904 and the receiving component 1902 may remain in the sleep state or further refrain from transmitting or receiving between the scheduled end of the TWT SP and the start of the next TWT SP.

[0149]

[0169] Device 1900 may operate in an off-channel or concurrent mode between the receipt of the first EOSP indication and the scheduled end of the TWT SP. Device 1900 may further operate in an off-channel or concurrent mode between the scheduled end of the TWT SP and the start of the next TWT SP.

[0150]

[0170] Receiving component 1902 may receive a second EOSP indication, and stopping the TWT SP includes stopping the TWT SP based on receipt of both the first EOSP indication and the second EOSP indication. Receiving component 1902 may be connected to an access point and receive EOSP indications from each station associated with the TWT SP, and stopping the TWT SP includes stopping the TWT SP based on receipt of EOSP indications from all stations connected to the access point and associated with the TWT SP.

[0151]

[0171] The number and configuration of the components shown in FIG. 19 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently configured components compared to the components shown in FIG. 19. Further, two or more of the components shown in FIG. 19 may be implemented within a single component, or a single component shown in FIG. 19 may be implemented as a plurality of distributed components. Additionally, alternatively or instead, a set of (one or more) components shown in FIG. 19 may perform one or more functions described as being performed by another set of components shown in FIG. 19.

[0152]

[0172] FIG. 20 is a diagram of an exemplary apparatus 2000 for wireless communication. Apparatus 2000 can be a station (e.g., STA140, STA820), or a station can include apparatus 2000. In some aspects, apparatus 2000 includes a receiving component 2002 and a transmitting component 2004 that can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 2000 can communicate with another apparatus 2006 (such as a UE, a base station, a network entity, an access point, a station, or another wireless communication device) using receiving component 2002 and transmitting component 2004. Further shown, apparatus 2000 can include a communication manager 2008. Communication manager 2008 can control and / or otherwise manage one or more operations of receiving component 2002 and / or transmitting component 2004. In some aspects, communication manager 2008 can include one or more antennas, modems, controllers / processors, memories, or combinations thereof of the STA described in connection with FIG. 1D. Communication manager 2008 can be or be similar to communication manager 56 shown in FIG. 1D. For example, in some aspects, communication manager 2008 can be configured to perform one or more of the functions described as being performed by communication manager 156. In some aspects, communication manager 2008 can include receiving component 2002 and / or transmitting component 2004. Communication manager 2008 can include, among other examples, a service period component 2010.

[0153]

[0173] In some aspects, apparatus 2000 may be configured to perform one or more operations described herein with respect to FIGS. 1-16. Additionally or alternatively, apparatus 2000 may be configured to perform one or more processes described herein, such as process 1800 of FIG. 18. In some aspects, apparatus 2000 and / or one or more components shown in FIG. 20 may include one or more components of the station described with respect to FIG. 1D. Additionally or alternatively, one or more components shown in FIG. 20 may be implemented within one or more components described with respect to FIG. 1D. Additionally or alternatively, one or more components of a set of components may be implemented at least partially as software stored in a memory. For example, a component (or a portion of a component) may be stored in a non-transitory computer-readable medium and implemented as instructions or code executable by a controller or processor to perform the functions or operations of the component.

[0154]

[0174] Receiving component 2002 may receive communications, such as a reference signal, control information, data communication, or a combination thereof, from apparatus 2006. Receiving component 2002 may provide the received communications to one or more other components of apparatus 2000. In some aspects, receiving component 2002 may perform signal processing (such as, among other examples, filtering, amplification, demodulation, analog-to-digital conversion, de-multiplexing, de-interleaving, demapping, equalization, interference cancellation, or decoding) on the received communications and provide the processed signals to one or more other components of apparatus 2000. In some aspects, receiving component 2002 may include one or more antennas, modems, demodulators, MIMO detectors, receiving processors, controllers / processors, memories, or combinations thereof of the station described with respect to FIG. 1D.

[0155]

[0175] The transmitting component 2004 may transmit communications such as a reference signal, control information, data communication, or a combination thereof to the device 2006. In some aspects, one or more other components of the device 2000 may generate the communication and provide the generated communication to the transmitting component 2004 for transmission to the device 2006. In some aspects, the transmitting component 2004 may perform signal processing (such as, among other examples, filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding) on the generated communication and transmit the processed signal to the device 2006. In some aspects, the transmitting component 2004 may include one or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the station described with respect to FIG. 1D. In some aspects, the transmitting component 2004 may be co-located with the receiving component 2002 in a transceiver.

[0156]

[0176] The service period component 2010 may enter the TWT SP. The transmitting component 2004 may transmit an EOSP indication to the access point before the scheduled end of the TWT SP. The receiving component 2002 may receive the forward EOSP indication. The service period component 2010 may stop the TWT SP based on receiving the forward EOSP indication.

[0157]

[0177] The number and configuration of the components shown in FIG. 20 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently configured components compared to the components shown in FIG. 20. Further, two or more components shown in FIG. 20 may be implemented within a single component, or a single component shown in FIG. 20 may be implemented as a plurality of distributed components. Additionally, alternatively or instead, a set of (one or more) components shown in FIG. 20 may perform one or more functions described as being performed by another set of components shown in FIG. 20.

[0158]

[0178] The following provides an overview of some aspects of the present disclosure.

[0159]

[0179] Aspect 1: A method of wireless communication performed by an access point, the method including starting a target wake time (TWT) service period (SP), receiving a first SP end of service period (EOSP) indication from a station, and stopping the TWT SP before a scheduled end of the TWT SP based on receiving the first EOSP indication.

[0160]

[0180] Aspect 2: The method according to Aspect 1, wherein receiving the first EOSP indication includes receiving the first EOSP indication within a frame shared with an acknowledgment, a block acknowledgment, or a multi-block acknowledgment.

[0161]

[0181] Aspect 3: The method according to Aspect 1 or 2, wherein receiving the first EOSP indication includes receiving the first EOSP indication multiplexed with an acknowledgment, a block acknowledgment, or a multi-block acknowledgment.

[0162]

[0182] Aspect 4: The method according to any one of Aspects 1 to 3, wherein receiving the first EOSP indication includes receiving the first EOSP indication within a frame shared with or configured for a quality of service null message.

[0163]

[0183] Aspect 5: The method according to any one of Aspects 1 to 3, wherein receiving the first EOSP indication includes receiving the first EOSP indication within a frame shared with or configured for a quality of service data message.

[0164]

[0184] Aspect 6: The method according to Aspect 5, wherein the quality of service data message is associated with an extended reality application or a personal area network application.

[0165]

[0185] Aspect 7: The method according to Aspect 1, wherein receiving the first EOSP indication includes receiving the first EOSP indication within a frame separate from a quality of service message, an acknowledgement, a block acknowledgement, or a multi-block acknowledgement.

[0166]

[0186] Aspect 8: The method according to any one of Aspects 1 to 7, further including entering a sleep state or refraining from transmission or reception between receiving the first EOSP indication and the scheduled end of the TWT SP.

[0167]

[0187] Aspect 9: The method according to Aspect 8, further including remaining in a sleep state or further refraining from transmission or reception between the scheduled end of the TWT SP and the start of the next TWT SP.

[0168]

[0188] Aspect 10: The method according to any one of Aspects 1 to 9, further including operating in an off-channel or concurrent mode between receiving the first EOSP indication and the scheduled end of the TWT SP.

[0169]

[0189] Aspect 11: The method according to aspect 10, further comprising operating further in an off-channel or simultaneous operation mode between the scheduled end of the TWT SP and the start of the next TWT SP.

[0170]

[0190] Aspect 12: The method according to any one of aspects 1 to 11, wherein receiving the first EOSP instruction includes receiving the first EOSP instruction in a service application of an access point.

[0171]

[0191] Aspect 13: The method according to any one of aspects 1 to 12, wherein receiving the first EOSP instruction includes receiving the first EOSP instruction via a configured component.

[0172]

[0192] Aspect 14: Further comprising receiving a second EOSP instruction, and stopping the TWT SP includes stopping the TWT SP based on receiving both the first EOSP instruction and the second EOSP instruction. The method according to any one of aspects 1 to 13.

[0173]

[0193] Aspect 15: Further comprising receiving an EOSP instruction from each station connected to the access point and associated with the TWT SP, and stopping the TWT SP includes stopping the TWT SP based on receiving EOSP instructions from all stations connected to the access point and associated with the TWT SP. The method according to any one of aspects 1 to 14.

[0174]

[0194] Aspect 16: A method of wireless communication performed by a station, comprising entering a target wake time (TWT) service period (SP), and transmitting an EOSP instruction to an access point before the scheduled end of the TWT SP.

[0175]

[0195] Aspect 17: The method according to aspect 16, wherein transmitting the EOSP instruction includes transmitting the EOSP instruction based on there being no data prepared for transmission.

[0176]

[0196] Aspect 18: The method according to aspect 16 or 17, further comprising receiving a forward EOSP instruction and stopping the TWT SP based on receiving the forward EOSP instruction.

[0177]

[0197] Aspect 19: The method according to any one of aspects 16 to 18, wherein transmitting the EOSP instruction includes transmitting the EOSP instruction within a frame shared with an affirmative response, a block affirmative response, or a multi-block affirmative response.

[0178]

[0198] Aspect 20: The method according to any one of aspects 16 to 19, wherein transmitting the EOSP instruction includes transmitting a multiplexed EOSP instruction with an affirmative response, a block affirmative response, or a multi-block affirmative response.

[0179]

[0199] Aspect 21: The method according to any one of aspects 16 to 20, wherein transmitting the EOSP instruction includes transmitting the EOSP instruction within a frame shared with a quality of service null message or configured for a quality of service null message.

[0180]

[0200] Aspect 22: The method according to any one of aspects 16 to 21, wherein transmitting the EOSP instruction includes transmitting the EOSP instruction within a frame shared with a quality of service data message or configured for a quality of service data message.

[0181]

[0201] Aspect 23: The method according to aspect 22, wherein the frame is the last frame in which data exists.

[0182]

[0202] Aspect 24: The method according to aspect 23, wherein the data is associated with an extended reality application or a personal area network application.

[0183]

[0203] Aspect 25: The method according to any one of Aspects 16 to 18 and 24, wherein transmitting the EOSP indication includes transmitting the EOSP indication in a frame that is separate from a quality of service message, an affirmative acknowledgment, a block affirmative acknowledgment, or a multi-block affirmative acknowledgment.

[0184]

[0204] Aspect 26: An apparatus for wireless communication in a device, comprising a processor, a memory coupled to the processor, and instructions stored in the memory and executable by the processor to cause the device to perform one or more of the methods of Aspects 1 to 25.

[0185]

[0205] Aspect 27: A device for wireless communication, comprising a memory and one or more processors coupled to the memory and configured to perform one or more of the methods of Aspects 1 to 25.

[0186]

[0206] Aspect 28: An apparatus for wireless communication, comprising at least one means for performing one or more of the methods of Aspects 1 to 25.

[0187]

[0207] Aspect 29: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform one or more of the methods of Aspects 1 to 25.

[0188]

[0208] Aspect 30: A set of instructions for wireless communication, the set of instructions stored in a non-transitory computer-readable medium and including one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods of Aspects 1 to 25.

[0189]

[0209] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the disclosed aspects to the precise forms disclosed. Modifications and variations can be added in light of the above disclosure, or can be obtained from practice of the aspects.

[0190]

[0210] As used herein, the term "component" is intended to be broadly construed as hardware and / or a combination of hardware and software. "Software" is construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, and / or functions, among other examples, whether referred to by another name or not. As used herein, "processor" is implemented in hardware and / or a combination of hardware and software. It will be apparent that the systems and / or methods described herein can be implemented in different forms of hardware and / or combinations of hardware and software. The actual specialized control hardware code or software code used to implement these systems and / or methods does not limit the aspects. Thus, those skilled in the art will understand that software and hardware can be designed, at least in part based on the description herein, to implement the systems and / or methods. Accordingly, in this specification, the operation and behavior of the systems and / or methods are described without reference to specific software code.

[0191]

[0211] As used herein, "meeting a threshold" can, depending on the context, refer to a value being greater than a threshold, being greater than or equal to a threshold, being less than a threshold, being less than or equal to a threshold, being equal to a threshold, not being equal to a threshold, and the like.

[0192]

[0212] Even if a particular combination of features is recited in the claims and / or disclosed herein, these combinations are not intended to limit the disclosure in various aspects. Many of these features may be combined in ways that are not specifically recited in the claims and / or not disclosed herein. The disclosure in various aspects includes each dependent claim combined with all other claims within the claim set. As used herein, the phrase referring to "at least one of" a list of items refers to any combination of those items, including a single member. By way of example, "at least one of a, b, or c" is intended to include a, b, c, a + b, a + c, b + c, and a + b + c, as well as any combination having multiple identical elements (e.g., a + a, a + a + a, a + a + b, a + a + c, a + b + b, a + c + c, b + b, b + b + b, b + b + c, c + c, and c + c + c, or any other order of a, b, and c).

[0193]

[0213] None of the elements, acts, or instructions used in this specification should be construed as important or essential unless explicitly described as such. Also, as used in this specification, the articles "a" and "an" are intended to include one or more items and may be used interchangeably with "one or more". Further, as used in this specification, the definite article "the" is intended to include one or more items referred to by the definite article "the" and may be used interchangeably with "one or more". Additionally, as used in this specification, the terms "set" and "group" are intended to include one or more items and may be used interchangeably with "one or more". When only one item is intended, the phrase "only one" or similar words are used. Also, as used in this specification, terms such as "has", "have", "having", etc. are intended to be open-ended terms that do not limit the elements they modify (e.g., an element "having" A may also have B). Further, the phrase "based on" is intended to mean "at least partially based on" unless otherwise specified. Also, as used in this specification, the term "or" is intended to be inclusive when used consecutively and may be used interchangeably with "and / or" unless otherwise specified (e.g., when used in combination with "either" or "only one of").

Claims

1. 1. An access point for wireless communications, comprising: Memory and one or more processors coupled to the memory, Initiate a Target Wake Time (TWT) Service Period (SP), receiving a first end of service program (EOSP) indication from the station; based on receiving the first EOSP indication, stopping the TWT SP before its scheduled end; Entering a sleep state or refraining from transmitting or receiving between receiving the first EOSP indication from the station and the scheduled end of the TWT SP; one or more processors configured to An access point comprising:

2. 2. The access point of claim 1, wherein the one or more processors are configured to receive the first EOSP indication in a frame shared with an acknowledgment, a block acknowledgment, or a multi-block acknowledgment, to receive the first EOSP indication.

3. 2. The access point of claim 1, wherein the one or more processors are configured to receive the first EOSP indication multiplexed with an acknowledgement, a block acknowledgement, or a multi-block acknowledgement to receive the first EOSP indication.

4. 2. The access point of claim 1, wherein the one or more processors are configured to receive the first EOSP indication within a frame shared with or configured for a Frame Quality of Service Null message to receive the first EOSP indication.

5. the one or more processors are configured to receive the first EOSP indication within a frame shared with or configured for a frame quality of service data message, to receive the first EOSP indication; the quality of service data message is associated with an extended reality application or a personal area network application; The access point of claim 1 .

6. 2. The access point of claim 1, wherein the one or more processors are configured to receive the first EOSP indication in a frame that is separate from a quality of service message, an acknowledgment, a block acknowledgment, or a multi-block acknowledgment, to receive the first EOSP indication.

7. 2. The access point of claim 1, wherein the one or more processors are configured to remain in the sleep state or refrain from further transmission or reception between the scheduled end of the TWT SP and the start of a next TWT SP.

8. 10. The access point of claim 1, wherein the one or more processors are configured to function in an off-channel or concurrent operation mode between receiving the first EOSP indication and the scheduled end of the TWT SP.

9. 10. The access point of claim 8, wherein the one or more processors are configured to further function in the off-channel or concurrent operation mode between the scheduled end of the TWT SP and the start of a next TWT SP.

10. 2. The access point of claim 1, wherein the one or more processors are configured to receive the first EOSP indication at a service application of the access point to receive the first EOSP indication.

11. 2. The access point of claim 1, wherein the one or more processors are configured to receive a second EOSP indication, and wherein the one or more processors are configured to stop the TWT SP based on receiving both the first EOSP indication and the second EOSP indication to stop the TWT SP.

12. 1. A station for wireless communication, comprising: Memory and one or more processors coupled to the memory, Entering the Target Wake Time (TWT) Service Period (SP), sending an end of service period (EOSP) indication from the station to the access point prior to the scheduled end of the TWT SP in a frame shared with an acknowledgment, block acknowledgment, or multi-block acknowledgment; one or more processors configured to A station equipped with:

13. 1. A method of wireless communication performed by an access point, comprising: Initiating a target wake time (TWT) service period (SP); receiving a first end of service period (EOSP) indication from the station; based on receiving the first EOSP indication, stopping the TWT SP before its scheduled end; entering a sleep state or refraining from transmitting or receiving between receiving the first EOSP indication from the station and the scheduled end of the TWT SP; A method comprising:

14. 1. A method of wireless communication performed by a station, comprising: Entering a Target Wake Time (TWT) Service Period (SP); transmitting an end of service period (EOSP) indication from the station to an access point prior to the scheduled end of the TWT SP in a frame shared with an acknowledgment, block acknowledgment, or multi-block acknowledgment; A method comprising:

15. A computer program comprising instructions, the instructions comprising:

14. When executed by one or more processors of an access point for wireless communication, causing the one or more processors to perform the method of claim 13; 15. A computer program product which, when executed by one or more processors of a station for wireless communication, causes the one or more processors to perform the method of claim 14.

Images