End of service period indication

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, an access point can initiate a target wakeup time (TWT) service period (SP). The access point can receive an end of SP (EOSP) indication from a station. The access point can stop the TWT SP before scheduling of the TWT SP ends based on receiving the EOSP indication. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Patent Application No. 17 / 662,644, filed on May 9, 2022, entitled “END OF SERVICE PERIOD INDICATION” and assigned to the assignee of this application. The disclosure of the prior application is considered a part of this patent application and is incorporated by reference into this patent application. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications and techniques and apparatus for using end of service period indications. Background Art

[0004] 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 referred to as stations (STAs). The basic building block of a WLAN that complies with the Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards is a basic service set (BSS) managed by an AP. Each BSS is identified by a basic service set identifier (BSSID) announced 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.

[0005] To improve data throughput, the AP may communicate with one or more STAs over multiple concurrent communication links. Each of these communication links may have various bandwidths, for example, by bonding 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 over any of these different communication links, and thus expect to improve communication between the AP and the one or more STAs over each of these communication links. Summary of the invention

[0006] 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 a scheduled end of the TWT SP based on receiving the first EOSP indication.

[0007]

[0013] 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 sending an EOSP indication to an access point before a scheduled end of the TWT SP.

[0008] Some aspects described herein relate to an access point 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 start a TWT SP. The one or more processors may be configured to receive a first EOSP indication from a station. The one or more processors may be configured to stop the TWT SP before the scheduling of the TWT SP ends based on receiving the first EOSP indication.

[0009] Some aspects described herein relate to a station 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 indication to an access point before the scheduling of the TWT SP ends.

[0010] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by one or more instructions, the one or more instructions, when executed by one or more processors of an access point. The instruction set, when executed by the one or more processors of the one or more instructions, may cause the one or more instructions to start a TWTSP when executed by the one or more processors of the access point. The instruction set, when executed by the one or more processors of the one or more instructions, may cause the one or more instructions to receive a first EOSP indication from a station when executed by the one or more processors of the access point. The instruction set, when executed by the one or more processors of the one or more instructions, may cause the one or more instructions to stop the TWT SP before the scheduling of the TWT SP ends based on receiving the first EOSP indication when executed by the one or more processors of the access point.

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

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

[0013] 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 sending an EOSP indication to an access point before a scheduled end of the TWT SP.

[0014] Aspects collectively include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, stations, access points, wireless communication devices, and / or processing systems as fully described herein with reference to and as illustrated in the drawings and description.

[0015] The features and technical advantages of examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations to the claims.

[0016] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers). The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0018] Figure 1A is a diagram illustrating an example of a wireless communication network according to the present disclosure.

[0019] Figure 1B A block diagram of an example wireless communication device according to the present disclosure is shown.

[0020] Figure 1C A block diagram of an example access point (AP) according to the present disclosure is shown.

[0021] Figure 1D A block diagram of an example station (STA) according to the present disclosure is shown.

[0022] Figure 2A Example protocol data units (PDUs) that may be used for communications between an AP and multiple STAs according to the present disclosure are shown.

[0023] Figure 2B It shows that according to the present disclosure Figure 2A Example fields in a PDU.

[0024] Figure 3A Another example PDU that may be used for communication between an AP and one or more STAs according to the present disclosure is shown.

[0025] Figure 3B Another example PDU that may be used for communication between an AP and one or more STAs according to the present disclosure is shown.

[0026] Figure 4 is a diagram illustrating an example of a target wake-up time according to the present disclosure.

[0027] Figure 5 is a diagram illustrating an example of a service period (SP) according to the present disclosure.

[0028] Figure 6 is a diagram illustrating an example of EOSP timeout according to the present disclosure.

[0029] Figure 7 is a diagram illustrating an example of SP termination using an reverse end of SP (EOSP) indication according to the present disclosure.

[0030] Figure 8is a diagram illustrating an example of using a reverse EOSP indication according to the present disclosure.

[0031] Figures 9 and 10 is a diagram illustrating an example of an extended reality topology according to the present disclosure.

[0032] Figure 11 to Figure 12 is a diagram illustrating an example of an extended personal area network topology according to the present disclosure.

[0033] Fig.13 is a diagram illustrating an example of a power graph according to the present disclosure.

[0034] Fig.14 is a diagram illustrating an example of the effect of early SP termination on concurrent operations according to the present disclosure.

[0035] Fig.15 is a diagram illustrating an example of comparison of EOSP termination techniques according to the present disclosure.

[0036] Fig.16A , Fig. 16B and Fig. 16C is a diagram illustrating a comparison of EOSP termination techniques according to the present disclosure.

[0037] Fig.17 is a diagram illustrating an example process performed, for example, by an access point according to the present disclosure.

[0038] Fig.18 is a diagram illustrating an example process performed, for example, by a station according to the present disclosure.

[0039] Figure 19 to Figure 20 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0040] The following description is directed to certain specific implementations in order to describe the 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 a variety of different ways. The specific implementations described can be implemented in a manner that can be implemented in accordance with the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, the IEEE 802.15 standard, the Bluetooth Special Interest Group (SIG) standard, or the like. The described implementations may be implemented in any device, system, or network capable of transmitting and receiving radio frequency (RF) signals in accordance with one or more of the Long Term Evolution (LTE), 3G, 4G, or 5G (New Radio (NR)) standards, etc., released by the Third Generation Partnership Project (3GPP). The described implementations may be implemented in any device, system, or network capable of transmitting and receiving RF signals in accordance with one or more of the following technologies or techniques: 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), a wireless local area network (WLAN), a wireless wide area network (WWAN), or an Internet of Things (IOT) network.

[0041] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be interpreted as being limited to any specific structure or function presented throughout the present disclosure. On the contrary, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of the present disclosure will be fully conveyed to those skilled in the art. It should be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods implemented using other structures, functions, or structures and functions in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

[0042] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated 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 these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0043] Although various aspects may be described herein using terminology generally associated with Institute of Electrical Engineers (IEEE) standards (e.g., IEEE 802) or 5G or new radio (NR) radio access technologies (RATs), various aspects of the present disclosure may be applicable to other RATs, such as ultra-wideband (UWB) technology, 3G RATs, 4G RATs, and / or post-5G RATs (e.g., 6G).

[0044] Figure 1A A block diagram of an example wireless communication network 100 is shown. According to some aspects, the wireless communication network 100 may be an example of a wireless local area network (WLAN) such as a Wi-Fi network (and will be referred to as WLAN 100 hereinafter). For example, the WLAN 100 may be a network implementing at least one of the IEEE 802.11 family of standards such as those defined by the IEEE 802.11-2016 specification or amendments thereof, including but not limited to 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba, and 802.11be. The WLAN 100 may include numerous wireless communication devices such as an access point (AP) 102 and a plurality of stations (STAs) 104. Although only one AP 102 is shown, the WLAN network 100 may also include a plurality of APs 102.

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

[0046] A single AP 102 and the associated set of STAs 104 may be referred to as a basic service set (BSS), which is managed by the corresponding AP 102 . Figure 1AAdditionally shown is an example coverage area 105 of the AP 102, which may represent a basic service area (BSA) of the WLAN 100. The BSS may be identified to users by a service set identifier (SSID) and to other devices by a basic service set identifier (BSSID), which may be a medium access control (MAC) address of the AP 102. The AP 102 periodically broadcasts a beacon frame ("beacon") including the BSSID to enable any STA 104 within the wireless range of the AP 102 to "associate" or re-associate with the AP 102, thereby establishing a corresponding communication link 106 (hereinafter also referred to as a "Wi-Fi link") with the AP 102 or maintaining a communication link 106 with the AP. For example, the beacon may include an identification of a primary channel used by the corresponding AP 102 and a timing synchronization function for establishing or maintaining timing synchronization with the AP 102. The AP 102 may provide access to external networks to various STAs 104 in the WLAN via the corresponding communication links 106.

[0047] To establish a communication link 106 with the AP 102, each of the STAs 104 is configured to perform passive or active scanning operations ("scans") on frequency channels in one or more frequency bands (eg, the 2.4 GHz, 5.0 GHz, 6.0 GHz, or 60 GHz bands). To perform a passive scan, the STA 104 listens for beacons transmitted by the corresponding AP 102 at periodic time intervals, referred to as target beacon transmission times (TBTTs), measured in time units (TUs), where one TU may be equal to 1024 microseconds (μs). To perform an active scan, the STA 104 generates probe requests and sequentially transmits them on each channel to be scanned, and listens for probe responses from the AP 102. Each STA 104 may be configured to identify or select an AP 102 to associate with based on discovery information obtained through passive or active scanning, and perform authentication and association operations to establish a communication link 106 with the selected AP 102. After authentication, the AP 102 may assign an association identifier (AID) to each associated STA 104.

[0048] As wireless networks become more and more common, STA 104 may have the opportunity to select one of many BSSs within the range of the STA or to select among multiple APs 102 that together form an extended service set (ESS) (including multiple connected BSSs). Extended network stations associated with WLAN 100 may be connected to a wired or wireless distribution system that allows multiple APs 102 to be connected in such ESS. Thus, STA 104 may be covered by more than one AP 102 and may be associated with different APs 102 at different times for different transmissions. Additionally, after associating with AP 102, STA 104 may also be configured to periodically scan its surroundings to find a more appropriate AP 102 to associate with. For example, a STA 104 that is moving relative to its associated AP 102 may perform a "roaming" scan to find another AP 102 with more suitable network characteristics (such as a larger received signal strength indicator (RSSI) or a reduced traffic load).

[0049] In some cases, STA 104 may form a network without AP 102 or other equipment other than STA 104 itself. An example of such a network is an ad hoc network (or 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 WLAN 100). In such a specific implementation, although STA 104 may be able to communicate with each other through AP 102 using a communication link 106, STA 104 may also communicate directly with each other via a direct wireless link 108. Additionally, two STAs 104 may communicate via a direct communication link 108, regardless of whether the two STAs 104 are associated with the same AP 102 and served by the same AP. In such an ad hoc system, one or more STAs 104 may assume the role played by AP 102 in a BSS. Such STAs 104 may be referred to as group owners (GOs) and may coordinate transmissions within the ad hoc network. Examples of direct wireless links 108 include Wi-Fi Direct connections, connections established using a Wi-Fi Tunneled Direct Link Setup (TDLS) link, and other P2P group connections.

[0050] The AP 102 and the STA 104 may operate and communicate in accordance with the IEEE 802.11 family of standards (such as those defined by the IEEE 802.11-2016 specification or amendments thereof, including, but not limited to, 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba, and 802.11be) (via respective communication links 106). These standards define WLAN radio and baseband protocols for the PHY and medium access control (MAC) layers. The AP 102 and the STA 104 send and receive wireless communications (hereinafter also referred to as "Wi-Fi communications") to and from each other in the form of physical layer convergence protocol (PLCP) protocol data units (PPDUs). The AP 102 and STA 104 in the WLAN 100 may send PPDUs on an unlicensed spectrum, which may be a portion of a spectrum that includes frequency bands traditionally used by Wi-Fi technology, such as the 2.4 GHz band, the 5.0 GHz band, the 60 GHz band, the 3.6 GHz band, and the 900 MHz band. Some implementations of the AP 102 and STA 104 described herein may also communicate in other frequency bands, such as the 6.0 GHz band, that may support both licensed and unlicensed communications. The AP 102 and STA 104 may also be configured to communicate on other frequency bands, such as shared licensed frequency bands, where multiple operators may have licenses to operate in one or more of the same or overlapping frequency bands.

[0051] Each of the frequency bands may include multiple sub-bands or frequency channels. For example, PPDUs that comply with the IEEE 802.11n, 802.11ac, and 802.11ax standard amendments may be sent on 2.4 GHz and 5.0 GHz frequency bands, where each frequency band is divided into multiple 20 MHz channels. In this way, these PPDUs are sent on a physical channel with a minimum bandwidth of 20 MHz, but larger channels may be formed through channel bonding. For example, a PPDU may be sent on a physical channel with a bandwidth of 40 MHz, 80 MHz, 160 MHz, or 320 MHz by bonding multiple 20 MHz channels together.

[0052] Each PPDU is a composite structure including a PHY preamble and a payload in the form of a PLCP service data unit (PSDU). The information provided in the preamble can be used by the receiving device to decode subsequent data in the PSDU. In an instance where the PPDU is sent on a bound channel, the preamble field can be copied and sent in each of the multiple component channels. The PHY preamble may include both a legacy part (or "legacy preamble") and a non-legacy part (or "non-legacy preamble"). Legacy preambles can be used for packet detection, automatic gain control, and channel estimation, as well as other purposes. Legacy preambles can also generally be used to maintain compatibility with legacy devices. The format, decoding, and information provided therein of the non-legacy part of the preamble are based on the specific IEEE 802.11 protocol to be used to send the payload.

[0053] Figure 1B 1 shows a block diagram of an example wireless communication device 110. In some implementations, the wireless communication device 110 may be a STA (such as the one described above with reference to Figure 1A In some implementations, the wireless communication device 110 may be an example of a device in an AP (such as the one of the STAs 104 described above). Figure 1A The wireless communication device 110 is an example of a device used in the AP 102 described in the foregoing. The wireless communication device 110 is capable of sending (or outputting for sending) and receiving wireless communications (e.g., in the form of wireless packets). For example, the wireless communication device may be configured to send and receive communications that conform to the IEEE 802.11 standard (such as that defined by the IEEE 802.11-2016 specification or its amendments, including but not limited to 802.11ah, 802.11ad, 802.11 ay , 802.11ax, 802.11az, 802.11ba, and 802.11be).

[0054] The wireless communication device 110 may be or may include a chip, system on chip (SoC), chipset, package, or device that includes one or more modems 112, such as Wi-Fi (IEEE 802.11 compliant) modems. 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 compatible modem). In some implementations, the wireless communication device 110 also includes one or more radio components 114 (collectively, “radio components 114”). In some implementations, the wireless communication device 116 also includes one or more processors, processing blocks, or processing elements 116 (collectively, “processors 116”) and one or more memory blocks or elements 118 (collectively, “memory 118”).

[0055] The modem 112 may include an intelligent hardware block or device, such as an application specific integrated circuit (ASIC) or the like. 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 component 114 for transmission over a wireless medium. The modem 112 is similarly configured to obtain modulated packets received by the radio component 114 and demodulate the packets to provide demodulated packets. In addition to the modulator and demodulator, the modem 112 may also include a digital signal processing (DSP) circuit, an automatic gain control (AGC), a decoder, a decoder, a multiplexer, and a demultiplexer. For example, when in a transmit mode, the data obtained from the processor 116 is provided to a decoder, which encodes the data to provide coded bits. The coded bits are then mapped to points in the modulation constellation (using the selected MCS) to provide modulated symbols. The modulated symbols can then be mapped to a number N SS spatial streams or the number N STS The modulated symbols in the corresponding spatial stream or space-time stream may then be multiplexed, transformed via an inverse fast Fourier transform (IFFT) block, and then provided to the DSP circuit for Tx windowing and filtering. The digital signal may then be provided to a digital-to-analog converter (DAC). The resulting analog signal may then be provided to an upconverter and ultimately to the radio component 114. In a specific implementation involving beamforming, the modulated symbols in the corresponding spatial stream are pre-decoded via a steering matrix before being provided to the IFFT block.

[0056] When in receive mode, a digital signal received from the radio component 114 is provided to a DSP circuit configured to acquire the received signal, for example, by detecting the presence of the signal and estimating the initial timing and frequency offset. The DSP circuit system is further configured to digitally condition the digital signal, for example, using channel (narrowband) filtering, analog impairment conditioning (such as correcting I / Q imbalance), and applying digital gain to ultimately obtain a narrowband signal. The output of the DSP circuit can then be fed to an AGC configured to use information extracted from the digital signal (e.g., in one or more received training fields) to determine the appropriate gain. The output of the DSP circuit is also coupled to a demodulator configured to extract the modulated symbols from the signal and, for example, calculate a log-likelihood ratio (LLR) for each bit position of each subcarrier in each spatial stream. The demodulator is coupled to a decoder, which can be configured to process the LLRs to provide decoded bits. The decoded bits from all spatial streams are then fed 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.

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

[0058] The processor 116 may include an intelligent hardware block or device designed to perform the functions described herein, such as 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 programmable logic device (PLD) (such as a field programmable gate array (FPGA)), a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof. The processor 116 processes information received through the radio component 114 and the modem 112, and processes information to be output by the modem 112 and the radio component 114 for transmission over a wireless medium. For example, the processor 116 may implement a control plane and a MAC layer, which is 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 the coding and decoding of frames, spatial multiplexing, space-time block coding (STBC), beamforming, and OFDMA resource allocation, and other operations or techniques. In some specific implementations, the processor 116 may generally control the modem 112 so that the modem performs the various operations described above.

[0059] The memory 118 may include a tangible storage medium, such as a random access memory (RAM) or a read-only memory (ROM) or a combination thereof. The memory 118 may also store non-transitory processor or computer executable software (SW) code containing instructions that, when executed by the processor 116, cause 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 various components disclosed herein or the various blocks or steps of the methods, operations, processes, or algorithms disclosed herein may be implemented as one or more modules of one or more computer programs.

[0060] Figure 1C 1 shows a block diagram of an example AP 120. For example, AP 120 may be a reference Figure 1A 1. An example implementation of AP 102 is described. AP 120 includes a wireless communication device (WCD) 122. For example, wireless communication device 122 may be a wireless communication device (WCD) 122. Figure 1BThe example implementation of the wireless communication device 110 described herein. The AP 120 also includes a plurality of antennas 124 coupled to the wireless communication device 122 to send and receive wireless communications. In some implementations, the AP 120 additionally includes an application processor 126 coupled to the wireless communication device 122 and a memory 128 coupled to the application processor 126. The AP 120 also includes at least one external network interface 130 that enables the AP 120 to communicate with a core network or a backhaul network to gain access to an external network including the Internet. For example, the 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). Components of the above components may communicate directly or indirectly with other components of the components via at least one bus. The AP 120 also includes a housing that surrounds the wireless communication device 122, the application processor 126, the memory 128, and at least portions of the antennas 124 and the external network interface 130.

[0061] In some aspects, the AP 120 may include a communication manager 132. As described in more detail elsewhere herein, the communication manager 132 may start a target wake time (TWT) service period (SP). The communication manager 132 may receive a first end of SP (EOSP) indication from a station and stop the TWT SP before the scheduled end of the TWT SP based on receiving the first EOSP indication. Additionally or alternatively, the communication manager 132 may perform one or more other operations described herein.

[0062] In some aspects, the AP 120 includes: a component for starting the TWT SP; a component for receiving a first EOSP indication from a station; and / or a component for stopping the TWT SP before the scheduling of the TWT SP ends based on receiving the first EOSP indication. In some aspects, the components for the AP 120 to perform the operations described herein may include, for example, one or more of the communication manager 132, the antenna 124, the application processor 126, the WCD 122, and / or the memory 128.

[0063] Figure 1D 1 shows a block diagram of an example STA 140. For example, STA 140 may be a reference Figure 1A 104. STA 140 includes a wireless communication device 142. For example, the wireless communication device 142 may be a reference Figure 1B140 is an example implementation of a wireless communication device 110 described herein. STA 140 also includes one or more antennas 144 coupled to the wireless communication device 142 to send and receive wireless communications. STA 140 additionally includes an application processor 146 coupled to the wireless communication device 142 and a memory 148 coupled to the application processor 146. In some implementations, STA 140 also includes a user interface (UI) 150 (such as a touch screen or keyboard) and a display 152, which can be integrated with UI 150 to form a touch screen display. In some implementations, STA 140 can also include one or more sensors 154, such as one or more inertial sensors, accelerometers, temperature sensors, pressure sensors, or altitude sensors. Components of the above components can communicate directly or indirectly with other components of the components through at least one bus. STA 140 also includes a housing that surrounds the wireless communication device 142, the application processor 146, the memory 148, and at least portions of the antenna 144, UI 150, and the display 152.

[0064] In some aspects, the STA 140 may include a communication manager 156. As described in more detail elsewhere herein, the communication manager 156 may enter the TWT SP and send an EOSP indication to the access point before the scheduled end of the TWT SP. Additionally or alternatively, the communication manager 156 may perform one or more other operations described herein.

[0065] In some aspects, STA 140 includes: a component for entering a TWT SP; and / or a component for sending an EOSP indication to an access point before the scheduling of the TWT SP ends. In some aspects, the components for STA 140 to perform the operations described herein may include, for example, one or more of a communication manager 156, an antenna 144, an application processor 146, a WCD 142, and / or a memory 148.

[0066] As indicated above, Figures 1A to 1D are provided as examples. Other examples can be found in the Figures 1A-1D The content described is different.

[0067] Figure 2AAn example protocol data unit (PDU) 200 that can be used for communication between an AP and multiple STAs is shown. For example, the PDU 200 can be configured as a PPDU. As shown, the PDU 200 includes a PHY preamble 202 and a PHY payload 204. For example, the PHY preamble 202 may include a legacy portion, which 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. The PHY preamble 202 may also include a non-legacy portion (not shown). The L-STF 206 generally enables a receiving device to perform automatic gain control (AGC) and coarse timing and frequency estimation. The L-LTF 208 generally enables a receiving device to perform fine timing and frequency estimation, and also estimates a wireless channel. The L-SIG 210 generally enables a receiving device to determine the duration of the PDU and use the determined duration to avoid transmitting over 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 appropriate modulation scheme. Payload 204 may generally carry higher layer data (e.g., in the form of a medium access control (MAC) protocol data unit (MPDU) or an aggregated MPDU (A-MPDU)).

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

[0069] As indicated above, FIG. 2A to FIG. 2B are provided as examples. Other examples can be found in the FIG. 2A to FIG. 2B The examples described are different.

[0070] Figure 3AAnother example PDU 300 that can be used for wireless communication between an AP and one or more STAs is shown. The PDU 300 can be used for SU, OFDMA, or MU-MIMO transmission. The PDU 300 can be formatted as a high-efficiency (HE) WLAN PPDU according to the IEEE 802.11ax amendment 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 also include a PHY payload 306 after the preamble (e.g., in the form of a PSDU including a data field 324).

[0071] 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-LTF) 322. For OFDMA or MU-MIMO communications, the second portion 304 further includes a second HE signal field (HE-SIG-B) 318 that is encoded separately from the HE-SIG-A 316. As with the L-STF 308, L-LTF 310, and L-SIG 312, in instances involving the use of bonded channels, the information in the RL-SIG 314 and HE-SIG-A 316 may be replicated and sent in each component 20 MHz channel. In contrast, the content in the HE-SIG-B 318 may be unique to each 20 MHz channel and targeted specific STA 104 .

[0072] The RL-SIG 314 may indicate to the HE-compatible STA 104 that the PDU 300 is a HE PPDU. The AP 102 may use the HE-SIG-A 316 to identify multiple STAs 104 and inform the multiple STAs that the AP has scheduled UL or DL ​​resources for them. For example, the HE-SIG-A 316 may include a resource allocation subfield indicating resource allocation for the identified STA 104. The HE-SIG-A 316 may be decoded by each HE-compatible STA 104 served by the AP 102. For MU transmission, the HE-SIG-A 316 also includes information that can be used by each identified STA 104 to decode the associated HE-SIG-B 318. For example, the HE-SIG-A 316 may indicate the frame format (including the location and length of the HE-SIG-B 318), the available channel bandwidth, and the modulation and coding scheme (MCS), etc. The HE-SIG-A 316 may also include HE WLAN signaling information that can be used by STAs 104 other than the identified STA 104.

[0073] HE-SIG-B 318 may carry STA-specific scheduling information, such as, for example, STA-specific (or "user-specific") MCS values ​​and STA-specific RU allocation information. In the context of DL MU-OFDMA, such information enables the corresponding STA 104 to identify and decode the corresponding resource unit (RU) in the associated data field 324. Each HE-SIG-B 318 includes a common field and at least one STA-specific field. The common field may indicate RU allocations (including RU assignments in the frequency domain) to multiple STAs 104, indicating which RUs are allocated for MU-MIMO transmissions and which RUs correspond to MU-OFDMA transmissions, as well as the number of users in the allocation and other examples. The common field may be encoded with common bits, CRC bits, and tail bits. User-specific fields are assigned to a specific STA 104 and may be used to schedule a specific RU and indicate the scheduling to other WLAN devices. Each user-specific field may include multiple user block fields. Each user block field may include two user fields containing information for two corresponding STAs to decode their corresponding RU payloads in the data field 324 .

[0074] Figure 3BAnother example PPDU 350 that can be used for wireless communication between an AP and one or more STAs is shown. PDU 350 can be used for SU, OFDMA, or MU-MIMO transmission. PDU 350 can be formatted as an extremely high throughput (EHT) WLAN PPDU according to the IEEE 802.11be amendment to the IEEE 802.11 wireless communication protocol standard, or can be formatted as a PPDU that complies with any future (post-EHT) version of a new wireless communication protocol (complying with future IEEE 802.11 wireless communication protocol standards or other wireless communication standards). PDU 350 includes a PHY preamble that includes a legacy portion 352 and a non-legacy portion 354. PDU 350 can also include a PHY payload 356 after the preamble (e.g., in the form of a PSDU including a data field 374).

[0075] 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-related signal fields following the RL-SIG 364. For example, the non-legacy portion 354 may include a universal 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 to be used for other wireless communication protocol versions above the EHT and carry information related to the version. The non-legacy portion 354 also includes an additional short training field 370 (referred to herein as "EHT-STF 370", but which may also be constructed and carry version-related information for wireless communication protocol versions other than EHT) and one or more additional long training fields 372 (referred to herein as "EHT-LTF 372", but they may be constructed and carry version-related information for wireless communication protocol versions other than EHT). As with the L-STF 358, L-LTF 360, and L-SIG 362, in instances involving the use of bonded channels, the information in the U-SIG 366 and the EHT-SIG 368 may be replicated and sent in each component 20 MHz channel. In some implementations, the EHT-SIG 368 may additionally or alternatively carry information in one or more non-primary 20 MHz channels that is different from the information carried in the primary 20 MHz channel.

[0076] The EHT-SIG 368 may include one or more jointly coded symbols and may be encoded in a different block from the block in which the U-SIG 366 is encoded. The EHT-SIG 368 may be used by the AP to identify multiple STAs 104 and notify the multiple STAs that the AP has scheduled UL or DL ​​resources for them. The EHT-SIG 368 may be decoded by each compatible STA 104 served by the AP 102. The EHT-SIG 368 may generally be used by a receiving device to interpret the bits in the data field 374. For example, the EHT-SIG 368 may include RU allocation information, spatial stream configuration information, and per-user signaling information (such as MCS) and other examples. The EHT-SIG 368 may also include a cyclic redundancy check (CRC) (e.g., four bits) and a tail (e.g., 6 bits) that may be used for a binary convolutional code (BCC). In some implementations, the EHT-SIG 368 may include one or more code blocks each including a CRC and a tail. In some aspects, each code block may be encoded separately.

[0077] The EHT-SIG 368 may carry STA-specific scheduling information, such as, for example, user-specific MCS values ​​and user-specific RU allocation information. The EHT-SIG 368 may generally be used by a receiving device to interpret bits in the data field 374. In the context of DL MU-OFDMA, such information enables the corresponding STA 104 to identify and decode the corresponding RU in the associated data field 374. Each EHT-SIG 368 may include a common field and at least one user-specific field. The common field may indicate the RU distribution to multiple STAs 104, indicate the RU assignment in the frequency domain, indicate which RUs are allocated for MU-MIMO transmission and which RUs correspond to MU-OFDMA transmission, and the number of users in the allocation and other examples. The common field may be encoded with a common bit, a CRC bit, and a tail bit. The user-specific field is assigned to a specific STA 104 and may be used to schedule a specific RU and indicate the scheduling to other WLAN devices. Each user-specific field may include multiple user block fields. Each user block field may include, for example, two user fields containing information for two corresponding STAs to decode their corresponding RU payloads.

[0078] The presence of the RL-SIG 364 and the U-SIG 366 may indicate to the EHT or later version compatible STA 104 that the PPDU 350 is an EHT PPDU or a PPDU of any later (post-EHT) version that complies with a new wireless communication protocol (complying with future IEEE 802.11 wireless communication protocol standards). For example, the U-SIG 366 may be used by a receiving device to interpret bits in one or more of the EHT-SIG 368 or the data field 374.

[0079] As indicated above, FIG. 3A to FIG. 3B Some examples are provided. Other examples can be found in FIG. 3A to FIG. 3B Different than described.

[0080] Figure 4 is a diagram illustrating an example 400 of a TWT according to the present disclosure.

[0081] An AP (e.g., AP 120) such as a service or software AP (SAP) can use TWT to reduce power consumption for latency-sensitive and power-limited wireless devices. A TWT can be a duration when a requesting station (e.g., STA 1) is awakened for activity (e.g., for periodic data transmission). STA 1 (e.g., STA 140) can sleep in other ways. TWT can be configured or negotiated and can be used for applications such as extended reality (XR) applications and / or PAN applications.

[0082] At the beginning of a time interval or service period, such as at the beginning of a TBTT, the SAP may operate in a broadcast core network (BCN) period. The BCN may involve a multicast (MC) or broadcast (BC) message. The SAP may then perform a broadcast TWT period, followed by a separate TWT period. The SP may start at the beginning of a separate TWT period (SP start) and end at the end of a separate TWT period (SP end), and may therefore be referred to as a "TWT SP". The SP end of the TWT SP may be a scheduled end that is scheduled to end after a configured amount of time from the SP start of the WT SP. That is, the scheduled end may be a configured end according to a configured 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 beginning of the SP. The station may be awakened during the BCN period and sleep during the broadcast TWT period.

[0083] During the TWT SP of SAP and the TWT SP of STA 1, SAP may send a quality of service (QoS) data message or a QoS empty message (no data). STA 1 may send an acknowledgment (ACK), a block ACK (BA), or a multi-block ACK (MBA) for such a QoS message. STA 1 may also send a QoS data message or a QoS empty message. As shown in example 400, SAP may send an EOSP message with a field equal to 1 (e.g., if there is no data to be sent). STA 1 may enter sleep (hibernation) mode after receiving the EOSP message or after a certain duration (e.g., AdjustedMinimumTWTWakeDuration) has passed since the TWT SP start time as identified by STA 1, whichever occurs first. STA 1 may also terminate its TWT SP. However, SAP does not terminate its TWT SP until after the inactivity timeout (ITO).

[0084] As indicated above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 The examples described are different.

[0085] Figure 5 is a diagram illustrating an example 500 of a SP according to the present disclosure.

[0086] Example 500 shows multiple TBTTs each with a TWT SP. A service interval may span from the start of a TWT SP to the start of the next TWT SP. Smaller service intervals provide less latency but higher power consumption. Larger service intervals provide less power consumption but more latency.

[0087] STA 1 and STA 2 can be requesting stations, and SAP can be a responding station. SAP can send QoS messages and EOSP to STA 1 and STA 2. For example, SAP can send EOSP 502 to STA 2, and STA 2 can enter sleep mode. EOSP 504 and EOSP 506 are other examples of EOSP. However, in this configuration, SAP cannot terminate its TWT SP before the scheduling of the TWT SP ends (for example, when EOSP is only in one direction from SAP to the station). SAP cannot perform off-channel or concurrent operations either. This reduces the already limited dwell time. It is also expected that SAP remains awake to receive traffic outside the SP. In each scenario, SAP consumes more power than required.

[0088] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 The examples described are different.

[0089] Figure 6 is a diagram illustrating an example 600 of an EOSP timeout according to the present disclosure.

[0090] Example 600 shows two SPs for a SAP for two TBTTs (TBTT 602 and TBTT 604). During the active portion of the SP for TBTT 602, the SAP may send a QoS data message with a first packet (Packet 1) to STA 1. The SAP may receive an ACK for Packet 1. The SAP may send a QoS data message with Packet 1 to STA 2. The QoS messages are in bold, indicating that these QoS messages may include an EOSP indication that causes the corresponding station to enter sleep mode. The SAP may receive an ACK for this Packet 1 during the listening portion of the SP, which starts an inactivity timer. Note that the ACK is not in bold because the ACK from the station cannot include an EOSP indication.

[0091] If there is no data to be sent and no data is received from any station, the SP can time out after the ITO, which ends the listening part of the SP for the SAP. Now that the SP has timed out, the SAP can be in idle mode, which effectively terminates the SP. The minimum configurable ITO in the software of the SAP can be 1 millisecond (ms). For the gaming business in the extended PAN (XPAN), the TWT SP can be 2ms, and the business is expected to last 0.5ms to 1ms. Therefore, it is not even feasible to terminate the SP using ITO in most SPs. In addition, ITO is prone to errors and is not optimal for all SP configurations. During TBTT 604, ITO can start after sending a QoS message. However, when an uplink message is received and an ACK is sent, the ITO can be cancelled. The ITO can then be restored and ended before the idle period for the SP. Starting, stopping and resuming the inactivity timer may consume additional processing resources and increase latency.

[0092] As indicated above, Figure 6 are provided as examples. Other examples can be found in the Figure 6 The examples described are different.

[0093] Figure 7 is a diagram illustrating an example 700 of SP termination using reverse EOSP indication according to the present disclosure.

[0094] According to various aspects described herein, a station may send an EOSP indication (e.g., a reverse EOSP indication) to a SAP. Thus, the SAP may receive information indicating the end of the SP, which would otherwise be unknown to the SAP. Receiving this information may allow the SAP to stop the TWT SP before the scheduled end of the TWT SP. Thus, the SAP may save energy (e.g., by entering a sleep mode, avoiding sending or receiving) by stopping the TWT SP earlier than scheduled. Additionally or alternatively, the SAP may perform out-of-channel or concurrent operations between the reception of a first EOSP indication (termination of the TWT SP) and the scheduled end of the TWT SP by stopping the TWT SP earlier than scheduled, thereby improving the performance of the network by reallocating resources used for communication.

[0095] According to various aspects described herein, each station may send an EOSP indication to the SAP. For example, if there is no more data to be sent, the station may send an EOSP. This EOSP from the station may be referred to as a "reverse EOSP indication" because the reverse EOSP indication is in the opposite direction of the existing EOSP from the SAP only. Once the SAP has received the EOSP from each station to which the SAP is connected and associated with the TWTSP, the SAP may stop (terminate) the TWT SP and enter sleep or idle mode. This termination may also be referred to as "authorization-based EOSP termination" or "GeoSP termination". The reverse EOSP may be part of a light handshake between the SAP and the station, in which a message is sent and an ACK is returned. That is, the reverse EOSP may be included with existing signaling. For example, the SAP may send a QoS data message to STA 2, and STA 2 may send an EOSP indication 702 with an ACK to the SAP. The EOSP indication 702 may share a frame with the ACK, be multiplexed with the ACK, or be included in a frame configured for the ACK. For the EOSP indication 702, no new signal is required. In some aspects, STA 2 may reuse the EOSP subfield in the QoS control field of a QoS data frame or a QoS empty frame as a request to terminate the SP. The request may solicit a response. STA 2 may reuse an existing field or a reserved field in ACK / BA / MBA to confirm SP termination. This helps to avoid another explicit frame exchange sequence as part of a handshake mechanism. In some aspects, STA 2 may use an information element (IE) to specify the use of a reverse EOSP indication and / or the reuse of a field in a QoS data frame, a QoS empty frame, and / or an ACK / BA / MBA during TWT setup or association. Alternatively, STA 1 may send an EOSP indication in a frame separate from an ACK, BA, or MBA.

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

[0097] By utilizing deterministic EOSP to enter sleep or idle mode before the TWT SP ends (and earlier than ITO), the SAP saves more power. The SAP can also perform off-channel operations (such as communication on another channel separate from the station) or concurrent operations (such as switching to another link) earlier. That is, the station can send EOSP as new signaling, so that the EOSP is sent by both the SAP and the station, not just from the SAP. Once the EOSP is received from all stations in the station associated with the TWT SP, the SAP can terminate its TWT SP earlier.

[0098] In some aspects, the SAP may save energy (e.g., enter sleep mode, avoid sending or receiving) or perform off-channel or concurrent operations between the receipt of the first EOSP indication (termination of the TWT SP) and the end of the scheduling of the TWT SP. The SAP may also continue to save energy or perform other operations between the end of the scheduling 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.

[0099] As indicated above, Figure 7 are provided as examples. Other examples can be found in the Figure 7 The examples described are different.

[0100] Figure 8 8 is a diagram illustrating an example 800 associated with using a reverse EOSP indication according to the present disclosure. Figure 8 As shown in FIG. 8 , an access point such as SAP 810 (e.g., AP 120) can initiate TWT SP 812. SAP 810 can communicate with a station such as STA 820 (e.g., STA 140). STA 820 can initiate TWT SP 822. SAP 810 can also communicate with other stations such as STA 830 (TWT SP 832) and STA 840 (TWT SP 842).

[0101] After any data transmission, the station may no longer have data to be sent and may send a reverse EOSP indication, as shown by reference numerals 845, 850, and 855. For example, STA 820 may send a reverse EOSP to SAP 810 based on STA 820 completing data transmission and / or not having any (more) data to be sent. If there is no more data to be sent to the station, SAP 810 may also send an EOSP indication to the station, as shown by reference numeral 860. As shown by reference numeral 865, the stations may terminate their respective TWT SPs. For example, each station may terminate the respective TWT SP based on receiving an EOSP indication from SAP 10 and not having any (more) data to be sent. As shown by reference numeral 870, SAP 810 may terminate TWT SP 812 based on receiving an EOSP indication from all stations in the station. For example, SAP 810 may determine whether an EOSP indication is received from each station (e.g., STA 820, STA 830, and STA 840). If an EOSP indication has not been received from each station (e.g., received from less than all stations associated with or connected to the SAP 810), the SAP 810 may continue the TWT SP 812. For example, if an EOSP is not received from each station before the end of the schedule of the TWT SP 812, the SAP 810 may continue the TWT SP 812 until the end of the schedule of the TWT SP 812 without terminating earlier. If an EOSP indication is received from each station (e.g., received from all stations associated with or connected to the SAP 810), the SAP 810 may terminate the TWT SP 812 (e.g., before the end of the schedule of the TWT SP 812).

[0102] In some aspects, a Reverse EOSP indication is received and TWT SP termination is implemented via a software application or a service application. In some aspects, a Reverse EOSP indication is received via a configured component (eg, hardware, firmware).

[0103] Although Figure 8 An example is illustrated in which each reverse EOSP indication is sent before the EOSP indication from SAP 810, but it should be understood that the ordering of this signaling is not limited to this particular example, and the reverse EOSP indications and EOSP indications may be sent in other orders.

[0104] As indicated above, Figure 8 are provided as examples. Other examples can be found in the Figure 8 The examples described are different.

[0105] Fig. 9 is a diagram illustrating an example 900 of an XR topology according to the present disclosure.

[0106] Reverse EOSP indication can be used in various XR scenarios. Example 900 shows some example XR topologies that can involve augmented reality (AR) applications, where data is sent, for example, between an AP and a smartphone (or other type of computer) and between a smartphone and a peripheral device such as AR or XR glasses. For example, as shown in topology 1, an AP can act as a Figure 7 and Figure 8 As shown in topology 2, if cloud computing is involved, the smartphone (circled) between the AP and the glasses can act as the SAP 810.

[0107] As indicated above, Fig. 9 are provided as examples. Other examples can be found in the Fig. 9 The examples described are different.

[0108] Fig.10 is a diagram illustrating example 1000 of more XR topologies according to the present disclosure.

[0109] Example 1000 shows topology 3, where various combinations of devices can act as a combination of Figure 8 and Figure 8 Depicted SAP 810 or STA 820. A smartphone (circled) may act as a SAP 810 that receives a reverse EOSP indication.

[0110] As indicated above, Fig.10 are provided as examples. Other examples can be found in the Fig.10 The examples described are different.

[0111] Fig.11 is a diagram illustrating an example 1100 of an XPAN topology according to the present disclosure.

[0112] Reverse EOSP indication can be used in various XR scenarios, which can use some of the examples shown by "BT" in the topology. Agreement. Such as combining Figure 7 and Figure 8 The stations depicted as STA 820 may include smartphones and / or earbuds (circled). The earbuds may include primary (P) earbuds and secondary (S) earbuds. The smartphone may also act as an AP, such as SAP 810.

[0113] As indicated above, Fig.11 are provided as examples. Other examples can be found in the Fig.11 The examples described are different.

[0114] Fig.12 is a diagram illustrating an example 1200 of further XPAN topologies according to the present disclosure.

[0115] Reverse EOSP indication can be used in various other XPAN scenarios, such as with multiple smartphones and earbuds operating with true wireless (TWS) technology. The more likely scenarios for Reverse EOSP indication are circled.

[0116] As indicated above, Fig.12 are provided as examples. Other examples can be found in the Fig.12 The examples described are different.

[0117] Fig.13 is a diagram illustrating an example 1300 of a power graph in accordance with the present disclosure.

[0118] Example 1300 shows a power diagram where power savings may occur. Potential power savings may occur after an early termination (reverse EOSP). There may be unused dwell periods.

[0119] As indicated above, Fig.13 are provided as examples. Other examples can be found in the Fig.13 The examples described are different.

[0120] Fig.14 is a diagram of an example 1400 illustrating the impact of early SP termination on concurrent operations according to the present disclosure.

[0121] Example 1400 is another diagram showing an unused dwell period. An unused dwell period may be a duration that may have been used by an infrastructure link (Infra Link) (terminating earlier on an XR or XPAN link). This may be about 50% of the negotiated SP for gaming services (which is 1 ms). There may be a 2 ms to 3 ms Clear to Send (CTS) to Self period to enter an XR or XPAN interval. There may be a Contention Free (CF) end to exit an XR or XPAN interval.

[0122] As indicated above, Fig.14 are provided as examples. Other examples can be found in the Fig.14 The examples described are different.

[0123] Fig.15 is a diagram illustrating an example 1500 of a comparison of EOSP termination techniques according to the present disclosure.

[0124] Example 1500 shows the same as FIG. 16a, Fig. 16B and 16CThe table may summarize the air frame exchange sequence to signal the reverse EOSP indication. If there is no downlink (DL) traffic from the AP to the station or there is no uplink (UL) traffic from the station to the AP, a software implementation (without hardware changes) may use DL and UL QoS null messages for reverse EOSP. Hardware specific implementations (e.g., configured components) may use DL QoS null messages.

[0125] If there is only DL traffic, a software implementation may use UL QoS Null message for reverse EOSP indication, and a hardware implementation may use UL ACK / BA for reverse EOSP indication.

[0126] If there is only UL traffic, a software implementation may use a DL QoS Null message for the reverse EOSP indication, and a hardware implementation may use a DL ACK / BA for the reverse EOSP indication.

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

[0128] As indicated above, Fig.15 are provided as examples. Other examples can be found in the Fig.15 The examples described are different.

[0129] Fig.16A , Fig. 16B and Fig. 16C is a diagram illustrating a comparison of EOSP termination techniques according to the present disclosure.

[0130] Fig.16A The current signaling is shown without a reverse EOSP indication. An EOSP field value of 1 indicates EOSP. There is no reverse EOSP indication. Fig. 16B Shows the combination Fig.15 An example of a software implementation of a reverse EOSP indication is described. Fig. 16C Shows the combination Fig.15 An example of a hardware implementation of a reverse EOSP indication is described.

[0131] As indicated above, Fig. 16B and Fig. 16C Examples are provided. Other examples may differ from the examples described with respect to FIG. 16 .

[0132] Fig.17is a diagram illustrating an example process 1700 performed, for example, by an access point in accordance with the present disclosure. Example process 1700 is an example in which an access point (eg, SAP 810) performs operations associated with a reverse EOSP indication.

[0133] like Fig.17 As shown in FIG. 17 , in some aspects, process 1700 may include initiating a TWT SP (block 1710). For example, an access point (e.g., using Fig.19 The communication manager 1908 and / or service period component 1910 depicted in FIG. 10A may initiate a TWT SP as described above.

[0134] like Fig.17 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 (e.g., using Fig.19 The communication manager 1908 and / or receiving component 1902 depicted in FIG. 1 may receive a first EOSP indication from a station, as described above.

[0135] like Fig.17 As further shown in FIG. 17 , in some aspects, process 1700 may include stopping the TWT SP before the scheduling of the TWT SP ends based on receiving the first EOSP indication (block 1730). Fig.19 The communication manager 1908 and / or service period component 1910 depicted in FIG. 14 may stop the TWT SP before the scheduled end of the TWT SP based on receiving the first EOSP indication, as described above.

[0136] Process 1700 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

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

[0138] 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, a BA, or an MBA.

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

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

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

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

[0143] 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 receipt of a first EOSP indication and a scheduled end of a TWT SP.

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

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

[0146] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the process 1700 includes further servicing an out-of-channel or concurrent operation mode between a scheduled end of a TWT SP and a start of a next TWT SP.

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

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

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

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

[0151] although Fig.17 An example block diagram of process 1700 is shown, but in some aspects, process 1700 may include Fig.17 The blocks depicted in the process 1700 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1700. Additionally or alternatively, two or more blocks in the blocks of the process 1700 may be performed in parallel.

[0152] Fig.18 is a diagram illustrating an example process 1800, performed, for example, by a station, according to the present disclosure. The example process 1800 is an example in which a station (eg, STA 820) performs operations associated with a reverse EOSP indication.

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

[0154] like Fig.18 As further shown in FIG. 18, in some aspects, process 1800 may include sending an EOSP indication to an access point before the scheduling of the TWT SP ends (block 1820). For example, a station (e.g., using Fig. 20 The communication manager 2008 and / or the sending component 2004 depicted in FIG. 2004 may send the EOSP indication to the access point before the scheduling of the TWT SP ends, as described above.

[0155] Process 1800 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0156] In a first aspect, sending the EOSP indication includes sending the EOSP indication based on no data being ready to send.

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

[0158] In a third aspect, alone or in combination with one or more of the first and second aspects, sending the EOSP indication comprises sending the EOSP indication in a frame shared with an Ack, a BA, or an MBA.

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

[0160] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, sending the EOSP indication includes sending the EOSP indication in a frame shared with or configured for a QoS Null message.

[0161] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, sending the EOSP indication includes sending the EOSP indication in a frame shared with or configured for the QoS data message.

[0162] 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 exists.

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

[0164] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, sending the EOSP indication comprises sending the EOSP indication in a frame separate from the QoS message, ACK, BA, or MBA.

[0165] although Fig.18 An example block diagram of process 1800 is shown, but in some aspects, process 1800 may include Fig.18 The blocks depicted in the process 1800 may include additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1800. Additionally or alternatively, two or more blocks in the blocks of the process 1800 may be performed in parallel.

[0166] Fig.191 is a diagram of an example apparatus 1900 for wireless communication. Apparatus 1900 may be an access point (e.g., AP 120, SAP 810), or an access point may include apparatus 1900. In some aspects, apparatus 1900 includes a receiving component 1902 and a transmitting component 1904 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1900 may use receiving component 1902 and transmitting component 1904 to 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). As further shown, apparatus 1900 may include a communication manager 1908. Communication manager 1908 may control and / or otherwise manage one or more operations of receiving component 1902 and / or transmitting component 1904. In some aspects, communication manager 1908 may include a communication manager 1908 in conjunction with receiving component 1902 and / or transmitting component 1904. Figure 1C One or more antennas, modems, controllers / processors, memories, or combinations thereof of the APs described herein. The communications manager 1908 may be or be similar to Figure 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 a receiving component 1902 and / or a sending component 1904. The communication manager 1908 can include a service period component 1910, etc.

[0167] In some aspects, the apparatus 1900 may be configured to perform one or more operations described herein in conjunction with FIGS. 1 to 16. Additionally or alternatively, the apparatus 1900 may be configured to perform one or more processes described herein, such as Fig.17 The process 1700. In some aspects, Fig.19 The apparatus 1900 and / or one or more components shown in FIG. 1 may include a combination of Figure 1C Additionally or alternatively, Fig.19 One or more of the components shown in the figure may be combined with Figure 1C Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0168] The receiving component 1902 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the apparatus 1906. The receiving component 1902 may provide the received communications to one or more other components of the apparatus 1900. In some aspects, the receiving component 1902 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding) on ​​the received communications and may provide the processed signals to one or more other components of the apparatus 1900. In some aspects, the receiving component 1902 may include combining Figure 1C An access point may include one or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof.

[0169] Transmit component 1904 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to device 1906. In some aspects, one or more other components of device 1900 may generate communications and may provide the generated communications to transmit component 1904 for transmission to device 1906. In some aspects, transmit component 1904 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1906. In some aspects, transmit component 1904 may include in conjunction with Figure 1C One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described access points. In some aspects, the transmit component 1904 can be co-located with the receive component 1902 in a transceiver.

[0170] The service period component 1910 can start the TWT SP. The receiving component 1902 can receive a first EOSP indication from a station. The service period component 1910 can stop the TWT SP before the scheduling of the TWT SP ends based on receiving the first EOSP indication.

[0171] The sending component 1904 and the receiving component 1902 may enter a sleep state or avoid sending or receiving between the reception of the first EOSP indication and the scheduled end of the TWT SP. The sending component 1904 and the receiving component 1902 may remain in a sleep state or further avoid sending or receiving between the scheduled end of the TWT SP and the start of the next TWT SP.

[0172] The apparatus 1900 may serve an off-channel or concurrent mode of operation between receipt of a first EOSP indication and the scheduled end of a TWT SP. The apparatus 1900 may further serve an off-channel or concurrent mode of operation between the scheduled end of a TWT SP and the start of a next TWT SP.

[0173] The receiving component 1902 may receive a second EOSP indication, wherein stopping the TWT SP comprises stopping the TWT SP based on receiving both the first EOSP indication and the second EOSP indication. The receiving component 1902 may receive an EOSP indication from each station connected to the access point and associated with the TWT SP, wherein stopping the TWT SP comprises stopping the TWT SP based on receiving an EOSP indication from all stations connected to the access point and associated with the TWT SP.

[0174] Fig.19 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Fig.19 The components shown in the figure may include additional components, fewer components, different components, or components arranged in a different manner. Fig.19 Two or more components shown in the figure may be implemented in a single component, or Fig.19 The single component shown in can be implemented as multiple distributed components. Additionally or alternatively, Fig.19 A set (one or more) of components shown in the figure may perform the operations described as being performed by Fig.19 One or more functions performed by another group of components shown in the figure.

[0175] Fig. 20 is a diagram of an example apparatus 2000 for wireless communication. Apparatus 2000 may be a station (e.g., STA 140, STA 820), or a station may include apparatus 2000. In some aspects, apparatus 2000 includes a receiving component 2002 and a transmitting component 2004 that may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 2000 may use receiving component 2002 and transmitting component 2004 to 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). As further shown, apparatus 2000 may include a communication manager 2008. Communication manager 2008 may control and / or otherwise manage one or more operations of receiving component 2002 and / or transmitting component 2004. In some aspects, communication manager 2008 may include a communication manager 2008 in conjunction with receiving component 2002 and / or transmitting component 2004. Figure 1D One or more antennas, modems, controllers / processors, memories, or combinations thereof of the STAs described herein. The communication manager 2008 may be or be similar to Figure 1DFor example, in some aspects, the communication manager 2008 can be configured to perform one or more of the functions described as being performed by the communication manager 156. In some aspects, the communication manager 2008 can include a receiving component 2002 and / or a sending component 2004. The communication manager 2008 can include a service period component 2010, etc.

[0176] In some aspects, the apparatus 2000 may be configured to perform one or more operations described herein in conjunction with FIGS. 1 to 16. Additionally or alternatively, the apparatus 2000 may be configured to perform one or more processes described herein, such as Fig.18 In some aspects, the apparatus 2000 and / or Fig. 20 One or more of the components shown in the figure may include a combination of Figure 1D Additionally or alternatively, Fig. 20 One or more of the components shown in the figure may be combined with Figure 1D Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0177] Receive component 2002 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from apparatus 2006. Receive component 2002 may provide received communications to one or more other components of apparatus 2000. In some aspects, receive component 2002 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding) on ​​received communications and may provide processed signals to one or more other components of apparatus 2000. In some aspects, receive component 2002 may include in conjunction with Figure 1D One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described stations.

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

[0179] The service period component 2010 can enter the TWT SP. The sending component 2004 can send the EOSP indication to the access point before the scheduling of the TWT SP ends. The receiving component 2002 can receive the forward EOSP indication. The service period component 2010 can stop the TWT SP based on receiving the forward EOSP indication.

[0180] Fig. 20 The number and arrangement of components shown in the figure are provided as examples. In practice, there may be Fig. 20 The components shown in the figure may include additional components, fewer components, different components, or components arranged in a different manner. Fig. 20 Two or more components shown in the figure may be implemented in a single component, or Fig. 20 The single component shown in can be implemented as multiple distributed components. Additionally or alternatively, Fig. 20 A set (one or more) of components shown in the figure may perform the operations described as being performed by Fig. 20 One or more functions performed by another group of components shown in the figure.

[0181] The following provides an overview of some aspects of the disclosure:

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

[0183] Aspect 2: The method of aspect 1, wherein receiving the first EOSP indication comprises receiving the first EOSP indication in a frame shared with an acknowledgment, a block acknowledgment, or a multi-block acknowledgment.

[0184] Aspect 3: The method according to aspect 1 or 2, wherein receiving the first EOSP indication comprises receiving the first EOSP indication multiplexed with an acknowledgement, a block acknowledgement, or a multi-block acknowledgement.

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

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

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

[0188] Aspect 7: The method of aspect 1, wherein receiving the first EOSP indication comprises receiving the first EOSP indication in a frame separate from a quality of service message, an acknowledgement, a block acknowledgement, or a multi-block acknowledgement.

[0189] Aspect 8: According to any one of aspects 1 to 7, the method further comprises: entering a sleep state or avoiding sending or receiving between the reception of the first EOSP indication and the end of the scheduling of the TWT SP.

[0190] Aspect 9: The method according to aspect 8, further comprising: maintaining the sleep state or further avoiding transmission or reception between the end of the scheduling of the TWT SP and the start of the next TWT SP.

[0191] Aspect 10: The method according to any one of aspects 1 to 9, the method further comprising: serving an out-of-channel or concurrent operation mode between the reception of the first EOSP indication and the scheduling end of the TWT SP.

[0192] Aspect 11: The method according to aspect 10, the method further comprising: further serving the out-of-channel or concurrent operation mode between the end of the scheduling of the TWT SP and the start of the next TWT SP.

[0193] Aspect 12: The method according to any one of aspects 1 to 11, wherein receiving the first EOSP indication comprises receiving the first EOSP indication at a serving application of the access point.

[0194] Aspect 13: The method of any one of aspects 1 to 12, wherein receiving the first EOSP indication comprises receiving the first EOSP indication via the configured component.

[0195] Aspect 14: The method according to any one of aspects 1 to 13, the method further comprising: receiving a second EOSP indication, wherein stopping the TWT SP comprises stopping the TWT SP based on receiving both the first EOSP indication and the second EOSP indication.

[0196] Aspect 15: According to the method described in any one of Aspects 1 to 14, the method further includes: receiving an EOSP indication from each station connected to the access point and associated with the TWT SP, wherein stopping the TWT SP includes stopping the TWT SP based on receiving the EOSP indication from all stations connected to the access point and associated with the TWT SP.

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

[0198] Aspect 17: The method of aspect 16, wherein sending the EOSP indication comprises sending the EOSP indication based on no data being ready to send.

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

[0200] Aspect 19: The method according to any one of aspects 16 to 18, wherein sending the EOSP indication comprises sending the EOSP indication in a frame shared with an acknowledgement, a block acknowledgement, or a multi-block acknowledgement.

[0201] Aspect 20: The method according to any one of aspects 16 to 19, wherein sending the EOSP indication comprises sending the EOSP indication multiplexed with an acknowledgement, a block acknowledgement, or a multi-block acknowledgement.

[0202] Aspect 21: The method according to any one of aspects 16 to 20, wherein sending the EOSP indication comprises sending the EOSP indication in a frame shared with a quality of service null message or configured for the quality of service null message.

[0203] Aspect 22: The method according to any one of aspects 16 to 21, wherein sending the EOSP indication comprises sending the EOSP indication in a frame shared with or configured for a quality of service data message.

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

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

[0206] Aspect 25: The method according to any one of aspects 16 to 18 and 24, wherein sending the EOSP indication comprises sending the EOSP indication in a frame separate from a quality of service message, an acknowledgement, a block acknowledgement, or a multi-block acknowledgement.

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

[0208] Aspect 27: A device for wireless communication, the device comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 1 to 25.

[0209] Aspect 28: An apparatus for wireless communication, the apparatus comprising: at least one component for performing the method according to one or more of aspects 1 to 25.

[0210] Aspect 29: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 25.

[0211] Aspect 30: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising 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 described in aspects 1 to 25.

[0212] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the various aspects.

[0213] As used herein, the term "component" is intended to be broadly interpreted as hardware and / or a combination of hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures and / or functions, etc. As used herein, "processors" are 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 by different forms of hardware and / or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit the various aspects. Therefore, no reference is made to specific software codes to describe the operation and behavior of the systems and / or methods herein, because those skilled in the art will understand that software and hardware can be designed to implement the systems and / or methods based at least in part on the descriptions herein.

[0214] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0215] Although the specific combination of features is set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically described in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of the list of items" refers to any combination of these items (it includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (for example, 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 sorting of a, b and c).

[0216] Any element, action or instruction used herein should not be interpreted as key or necessary unless explicitly stated. In addition, as used herein, the article "one" is intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If you only want to refer to an item, the phrase "only one" or similar terms will be used. Moreover, as used herein, the terms "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "an element with" A can also have B). In addition, the phrase "based on" is intended to mean "based at least in part on", unless explicitly stated otherwise. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless explicitly stated otherwise (eg, if used in conjunction with "either" or "only one of").

Claims

1. An access point for wireless communication, the access point comprising: Memory; and one or more processors coupled to the memory and configured to: Start the target wake time (TWT) service period (SP); receiving a first End of SP (EOSP) indication from the station; and The TWT SP is stopped before a scheduled end of the TWT SP based on receiving the first EOSP indication.

2. The access point of claim 1, wherein to receive the first EOSP indication, 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.

3. The access point of claim 1, wherein to receive the first EOSP indication, the one or more processors are configured to receive the first EOSP indication multiplexed with an acknowledgment, a block acknowledgment, or multiple block acknowledgments.

4. The access point of claim 1, wherein to receive the first EOSP indication, the one or more processors are configured to receive the first EOSP indication in a frame shared with or configured for a quality of service null message.

5. The access point of claim 1, wherein to receive the first EOSP indication, the one or more processors are configured to receive the first EOSP indication in a frame shared with or configured for a quality of service data message.

6. The access point of claim 5, wherein the quality of service data message is associated with an extended reality application or a personal area network application.

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

8. The access point of claim 1, wherein the one or more processors are configured to enter a sleep state or refrain from transmitting or receiving between receipt of the first EOSP indication and the scheduled end of the TWT SP.

9. The access point of claim 8, wherein the one or more processors are configured to remain in the sleep state or further refrain from transmitting or receiving between the end of the schedule of the TWT SP and the start of a next TWT SP.

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

11. The access point of claim 10, wherein the one or more processors are configured to further service the off-channel or concurrent operation mode between the end of the schedule of the TWTSP and the start of a next TWTSP.

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

13. The access point of claim 1, wherein to receive the first EOSP indication, the one or more processors are configured to receive the first EOSP indication via the configured component.

14. The access point of claim 1, wherein the one or more processors are configured to receive a second EOSP indication, and wherein to stop the TWT SP, 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.

15. An access point according to claim 1, wherein the one or more processors are configured to receive an EOSP indication from each station connected to the access point and associated with the TWT SP, and wherein in order to stop the TWT SP, the one or more processors are configured to stop the TWT SP based on receiving the EOSP indication from all stations connected to the access point and associated with the TWT SP.

16. A station for wireless communication, the station comprising: Memory; and one or more processors coupled to the memory and configured to: Entering a target wake time (TWT) service period (SP); and An EOSP indication is sent to the access point before the scheduling of the TWT SP ends.

17. The station of claim 16, wherein to send the EOSP indication, the one or more processors are configured to send the EOSP indication based on no data being ready to send.

18. The station of claim 16, wherein the one or more processors are configured to: receiving a forward EOSP indication; and The TWT SP is stopped based on receiving the forward EOSP indication.

19. The station of claim 16, wherein to send the EOSP indication, the one or more processors are configured to send the EOSP indication in a frame shared with an acknowledgment, a block acknowledgment, or a multi-block acknowledgment.

20. The station of claim 16, wherein to send the EOSP indication, the one or more processors are configured to send the EOSP indication multiplexed with an acknowledgment, a block acknowledgment, or multiple block acknowledgments.

21. The station of claim 16, wherein to send the EOSP indication, the one or more processors are configured to send the EOSP indication in a frame shared with or configured for a quality of service null message.

22. The station of claim 16, wherein to send the EOSP indication, the one or more processors are configured to send the EOSP indication in a frame shared with or configured for a quality of service data message.

23. The station of claim 22, wherein the frame is the last frame in which data exists.

24. The station of claim 23, wherein the data is associated with an extended reality application or a personal area network application.

25. The station of claim 16, wherein to send the EOSP indication, the one or more processors are configured to send the EOSP indication in a frame separate from a quality of service message, an acknowledgment, a block acknowledgment, or a multi-block acknowledgment.

26. A method of wireless communication performed by an access point, the method comprising: Start the target wake time (TWT) service period (SP); receiving a first end of SP (EOSP) indication from the station; as well as The TWT SP is stopped before a scheduled end of the TWT SP based on receiving the first EOSP indication.

27. The method of claim 26, wherein receiving the first EOSP indication comprises receiving the first EOSP indication in a frame shared with a quality of service null message, a quality of service data message, or an acknowledgement.

28. The method of claim 26, wherein receiving the first EOSP indication comprises receiving the first EOSP indication in a frame separate from a quality of service message, an acknowledgment, a block acknowledgment, or a multi-block acknowledgment.

29. A method of wireless communication performed by a station, the method comprising: Entering the target wake time (TWT) service period (SP); as well as An EOSP indication is sent to the access point before the scheduling of the TWT SP ends.

30. The method of claim 29, wherein sending the EOSP indication comprises sending the EOSP indication in a frame shared with a quality of service null message, a quality of service data message, or an acknowledgement.

Images