Supporting incompatible STAS during AP dynamic power save operation

Abstract

Methods and apparatuses for supporting incompatible stations (STAs) during an access point (AP) dynamic power save operation. A method performed by an AP in wireless communication includes determining a compatibility of a first station (STA) associated with the AP for a dynamic power save (DPS) mode; and performing an enablement operation associated with enablement of the DPS mode based on the determined compatibility of the first STA for the DPS mode.

Description

SUPPORTING INCOMPATIBLE STAS DURING AP DYNAMIC POWER SAVE OPERATION

[0001] The disclosure relates to wireless communication. More particularly, the disclosure relates to supporting incompatible stations (STAs) during access point (AP) dynamic power save operation.

[0002] Wireless local area network (WLAN) technology allows devices to access the internet in the 2.4 GHz, 5GHz, 6GHz or 60 GHz frequency bands. WLANs are based on the institute of electrical and electronic engineers (IEEE) 802.11 standards. The IEEE 802.11 family of standards aim to increase speed and reliability and to extend the operating range of wireless networks.

[0003] The demand of wireless data traffic is rapidly increasing due to the growing popularity among consumers and businesses of smart phones and other mobile data devices, such as tablets, "note pad" computers, net books, eBook readers, and machine type of devices. In order to address the issue of increasing bandwidth requirements that are demanded for wireless communications systems, different schemes are being developed to allow multiple user terminals to communicate with a single access point by sharing the channel resources while achieving high data throughputs. Multiple input multiple output (MIMO) technology represents one such approach that has emerged as a popular technique. MIMO has been adopted in several wireless communications standards such 802.11ac, 802.11ax, etc.

[0004] The above information is presented as background information only to assist with an understanding of the disclosure. No determination has been made, and no assertion is made, as to whether any of the above might be applicable as prior art with regard to the disclosure.

[0005] Aspects of the disclosure are to address at least the above-mentioned problems and / or disadvantages and to provide at least the advantages described below. The disclosure provides methods and apparatuses for supporting incompatible STAs during AP dynamic power save operation.

[0006] In an embodiment, a method performed by an access point (AP) in wireless communication includes determining whether a transition to a dynamic power save (DPS) mode is desired; determining a compatibility of a first station (STA) associated with the AP for the DPS mode; determining enabling the DPS mode based on the compatibility of the first STA being incompatible with the DPS mode; maintaining association with the first STA while transitioning from a high power state to a low power state by providing an indication of reduced capabilities to the first STA, wherein the indication of reduced capabilities is based on at least one parameter of the DPS mode or a type of the first STA; and enabling the DPS mode.

[0007] In an embodiment, an AP comprises memory storing instructions, and at least one processor operably coupled with the memory. The instructions, when executed by the processor individually or collectively, cause the AP to determine whether a transition to a dynamic power save (DPS) mode is desired; determine a compatibility of a first STA associated with the AP for the DPS mode; determine enable the DPS mode based on the compatibility of the first STA being incompatible with the DPS mode; maintain association with the first STA while transitioning from a high power state to a low power state by providing an indication of reduced capabilities to the first STA, wherein the indication of reduced capabilities is based on at least one parameter of the DPS mode or a type of the first STA; and enable the DPS mode.

[0008] Other aspects, advantages, and salient features of the disclosure will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses various embodiments of the disclosure.

[0009] The above and other aspects, features, and advantages of certain embodiments of the disclosure will be more apparent from the following description taken in conjunction with the accompanying drawings, in which:

[0010] FIG. 1 illustrates an example wireless network according to an embodiment of the disclosure;

[0011] FIG. 2 illustrates an example access point (AP) according to an embodiment of the disclosure;

[0012] FIG. 3 illustrates an example station (STA) according to an embodiment of the disclosure;

[0013] FIG. 4 illustrates an example of an operating mode notification frame format according to an embodiment of the disclosure;

[0014] FIG. 5 illustrates an example of an operating mode A-control field format according to an embodiment of the disclosure;

[0015] FIG. 6 illustrates an example of an extremely high throughput (EHT) operation element that is transmitted by an EHT AP according to an embodiment of the disclosure;

[0016] FIG. 7 illustrates an example of an EHT capabilities element transmitted by an EHT STA according to an embodiment of the disclosure;

[0017] FIG. 8 illustrates an example of DPS operation of an AP during an uplink transmission according to an embodiment of the disclosure;

[0018] FIG. 9 illustrates an example of a scenario of an AP enabling DPS mode with several associated STAs according to an embodiment of the disclosure;

[0019] FIG. 10 illustrates an example of an ultra-high reliability (UHR) capabilities element indicating a STA's ability to support DPS operation or assist DPS operation at a peer STA according to an embodiment of the disclosure;

[0020] FIG. 11 illustrates an example of an AP removing incompatible STAs before transitioning to the low power state according to an embodiment of the disclosure;

[0021] FIG. 12 illustrates an example of an AP providing an indication of reduced capabilities for sufficient time before transitioning to the low power state according to an embodiment of the disclosure;

[0022] FIG. 13 illustrates an example of a DPS wrapper element which can hold one or more previous generation elements according to an embodiment of the disclosure;

[0023] FIG. 14 illustrates an example of an AP removing incompatible STAs before disabling the DPS mode according to an embodiment of the disclosure;

[0024] FIG. 15 illustrates an example of an AP providing an indication of return to full capabilities for sufficient time after transitioning to the full capability state according to an embodiment of the disclosure;

[0025] FIG. 16 illustrates an example method performed by an AP for supporting incompatible STAs during DPS operation according to an embodiment of the disclosure;

[0026] FIG. 17 illustrates an example method performed by a DPS incompatible STA during DPS operation according to an embodiment of the disclosure; and

[0027] FIG. 18 illustrates an example method performed by an AP in a wireless communication system for supporting incompatible STAs during DPS operation according to an embodiment of the disclosure.

[0028] Throughout the drawings, it should be noted that like reference numbers are used to depict the same or similar elements, features, and structures.

[0029] The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of various embodiments of the disclosure as defined by the claims and their equivalents. It includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the various embodiments described herein can be made without departing from the scope and spirit of the disclosure. In addition, descriptions of well-known functions and constructions may be omitted for clarity and conciseness.

[0030] The terms and words used in the following description and claims are not limited to the bibliographical meanings, but, are merely used by the inventor to enable a clear and consistent understanding of the disclosure. Accordingly, it should be apparent to those skilled in the art that the following description of various embodiments of the disclosure is provided for illustration purpose only and not for the purpose of limiting the disclosure as defined by the appended claims and their equivalents.

[0031] It is to be understood that the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to "a component surface" includes reference to one or more of such surfaces.

[0032] As is traditional in the field, embodiments are described and illustrated in terms of blocks that carry out a described function or functions.　These blocks, which referred to herein as managers, units, modules, hardware components or the like, are physically implemented by analog and / or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and optionally be driven by firmware and software. The circuits, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like.　The circuits constituting a block be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuitry), or by a combination of dedicated hardware to perform some functions of the block and a processor to perform other functions of the block. Each block of the embodiments be physically separated into two or more interacting and discrete blocks without departing from the scope of the proposed method.　Likewise, the blocks of the embodiments be physically combined into more complex blocks without departing from the scope of the proposed method.

[0033] FIGS. 1 through 18, discussed below, and the various embodiments used to describe the principles of the disclosure in this patent document are by way of illustration only and should not be construed in any way to limit the scope of the disclosure. Those skilled in the art will understand that the principles of the disclosure may be implemented in any suitably arranged system or device.

[0034] It should be appreciated that the blocks in each flowchart and combinations of the flowcharts may be performed by one or more computer programs which include instructions. The entirety of the one or more computer programs may be stored in a single memory device or the one or more computer programs may be divided with different portions stored in different multiple memory devices.

[0035] Any of the functions or operations described herein can be processed by one processor or a combination of processors. The one processor or the combination of processors is circuitry performing processing and may include circuitry like an application processor (AP, e.g. a central processing unit (CPU)), a communication processor (CP, e.g., a modem), a graphics processing unit (GPU), a neural processing unit (NPU) (e.g., an artificial intelligence (AI) chip), a wireless fidelity (Wi-Fi) chip, a Bluetooth®chip, a global positioning system (GPS) chip, a near field communication (NFC) chip, connectivity chips, a sensor controller, a touch controller, a finger-print sensor controller, a display driver integrated circuit (IC), an audio CODEC chip, a universal serial bus (USB) controller, a camera controller, an image processing IC, a microprocessor unit (MPU), a system on chip (SoC), an IC, or the like.

[0036] The following documents and standards descriptions are hereby incorporated by reference into the disclosure as if fully set forth herein: [1] IEEE 802.11-2020, "Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specification"; [2] IEEE P802.11ax / D8.0; [3] IEEE P802.11be / D5.0.

[0037] FIGS. 1-3 below describe various embodiments implemented in wireless communications systems and with the use of orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA) communication techniques. The descriptions of FIGS. 1-3 are not meant to imply physical or architectural limitations to the manner in which different embodiments may be implemented. Different embodiments of the disclosure may be implemented in any suitably arranged communications system.

[0038] FIG. 1 illustrates an example wireless network according to an embodiment of the disclosure. The embodiment of the wireless network shown in FIG. 1 is for illustration only. An embodiment of the wireless network 100 could be used without departing from the scope of the disclosure.

[0039] The wireless network 100 may include access points (APs) 101 and 103. The APs 101 and 103 communicate with at least one network 130, such as the Internet, a proprietary internet protocol (IP) network, or other data network. The AP 101 may provide wireless access to the network 130 for a plurality of stations (STAs) 111-114 within a coverage area 120 of the AP 101. The APs 101-103 may communicate with each other and with the STAs 111-114 using WI-FI or other WLAN communication techniques. The STAs 111-114 may communicate with each other using peer-to-peer protocols, such as tunneled direct link setup (TDLS).

[0040] Depending on the network type, other well-known terms may be used instead of "access point" or "AP," such as "router" or "gateway." For the sake of convenience, the term "AP" is used in the disclosure to refer to network infrastructure components that provide wireless access to remote terminals. In WLAN, given that the AP also contends for the wireless channel, the AP may also be referred to as a STA. Also, depending on the network type, other well-known terms may be used instead of "station" or "STA," such as "mobile station," "subscriber station," "remote terminal," "user equipment," "wireless terminal," or "user device." For the sake of convenience, the terms "station" and "STA" are used in the disclosure to refer to remote wireless equipment that wirelessly accesses an AP or contends for a wireless channel in a WLAN, whether the STA is a mobile device (such as a mobile telephone or smartphone) or is normally considered a stationary device (such as a desktop computer, AP, media player, stationary sensor, television, etc.).

[0041] Dotted lines show the approximate extents of the coverage areas 120 and 125, which are shown as approximately circular for the purposes of illustration and explanation only. It should be clearly understood that the coverage areas associated with gNBs, such as the coverage areas 120 and 125, may have other shapes, including irregular shapes, depending upon the configuration of the gNBs and variations in the radio environment associated with natural and man-made obstructions.

[0042] As described in more detail below, one or more of the APs may include circuitry and / or programming for facilitating supporting incompatible STAs during AP dynamic power save operation. Although FIG. 1 illustrates an example of a wireless network 100, various changes may be made to FIG. 1. For example, the wireless network 100 may include any number of APs and any number of STAs in any suitable arrangement. Also, the AP 101 may communicate directly with any number of STAs and provide those STAs with wireless broadband access to the network 130. Similarly, each AP 101-103 may communicate directly with the network 130 and provide STAs with direct wireless broadband access to the network 130. Further, the APs 101 and / or 103 may provide access to other or additional external networks, such as external telephone networks or other types of data networks.

[0043] FIG. 2 illustrates an example AP 101 according to an embodiment of the disclosure. The embodiment of the AP 101 illustrated in FIG. 2 is for illustration only, and the AP 103 of FIG. 1 could have the same or similar configuration. However, APs come in a wide variety of configurations, and FIG. 2 does not limit the scope of the disclosure to any particular implementation of an AP.

[0044] The AP 101 may include multiple antennas 205a-205n and multiple transceivers 210a-210n. The AP 101 may also include a controller / processor 225, memory 230, and a backhaul or network interface 235. The transceivers 210a-210n may receive, from the antennas 205a-205n, incoming radio frequency (RF) signals, such as signals transmitted by STAs 111-114 in the network 100. The transceivers 210a-210n may down-convert the incoming RF signals to generate IF or baseband signals. The IF or baseband signals may be processed by receive (RX) processing circuitry in the transceivers 210a-210n and / or controller / processor 225, which generates processed baseband signals by filtering, decoding, and / or digitizing the baseband or IF signals. The controller / processor 225 may further process the baseband signals.

[0045] Transmit (TX) processing circuitry in the transceivers 210a-210n and / or controller / processor 225 may receive analog or digital data (such as voice data, web data, e-mail, or interactive video game data) from the controller / processor 225. The TX processing circuitry may encode, multiplexe, and / or digitize the outgoing baseband data to generate processed baseband or IF signals. The transceivers 210a-210n may up-convert the baseband or IF signals to RF signals that are transmitted via the antennas 205a-205n.

[0046] The controller / processor 225 may include one or more processors or other processing devices that control the overall operation of the AP 101. For example, the controller / processor 225 may control the reception of forward channel signals and the transmission of reverse channel signals by the transceivers 210a-210n in accordance with well-known principles. The controller / processor 225 may support additional functions as well, such as more advanced wireless communication functions. For instance, the controller / processor 225 may support beam forming or directional routing operations in which outgoing signals from multiple antennas 205a-205n are weighted differently to effectively steer the outgoing signals in a desired direction. The controller / processor 225 may also support OFDMA operations in which outgoing signals are assigned to different subsets of subcarriers for different recipients (e.g., different STAs 111-114). Any of a wide variety of other functions could be supported in the AP 101 by the controller / processor 225 including facilitating supporting incompatible STAs during AP dynamic power save operation. In an embodiment, the controller / processor 225 may include at least one microprocessor or microcontroller. The controller / processor 225 is also capable of executing programs and other processes resident in the memory 230, such as an OS. The controller / processor 225 may move data into or out of the memory 230 as required by an executing process. Furthermore, controller / processor 225 may include various processing circuitry and / or multiple processors. For example, as used herein, including the claims, the term "processor" may include various processing circuitry, including at least one processor, wherein one or more of at least one processor, individually and / or collectively in a distributed manner, may be configured to perform various functions described herein. As used herein, when "a processor", "at least one processor", and "one or more processors" are described as being configured to perform numerous functions, these terms cover situations, for example and without limitation, in which one processor performs some of recited functions and another processor(s) performs other of recited functions, and also situations in which a single processor may perform all recited functions. Additionally, the at least one processor may include a combination of processors performing various of the recited / disclosed functions, e.g., in a distributed manner. At least one processor may execute program instructions to achieve or perform various functions.

[0047] The controller / processor 225 may be also coupled to the backhaul or network interface 235. The backhaul or network interface 235 may allow the AP 101 to communicate with other devices or systems over a backhaul connection or over a network. The interface 235 may support communications over any suitable wired or wireless connection(s). For example, the interface 235 may allow the AP 101 to communicate over a wired or wireless local area network or over a wired or wireless connection to a larger network (such as the Internet). The interface 235 may include any suitable structure supporting communications over a wired or wireless connection, such as an Ethernet or RF transceiver. The memory 230 may be coupled to the controller / processor 225. Part of the memory 230 may include a RAM, and another part of the memory 230 could include a flash memory or other ROM.

[0048] As described in more detail below, the AP 101 may include circuitry and / or programming for facilitating supporting incompatible STAs during AP dynamic power save operation. Although FIG. 2 illustrates an example of AP 101, various changes may be made to FIG. 2. For example, the AP 101 may include any number of each component shown in FIG. 2. As a particular example, an access point could include a number of interfaces 235, and the controller / processor 225 could support routing functions to route data between different network addresses. Alternatively, only one antenna and transceiver path may be included, such as in other APs. Also, various components in FIG. 2 could be combined, further subdivided, or omitted, and additional components could be added according to particular needs.

[0049] FIG. 3 illustrates an example STA 111 according to an embodiment of the disclosure. The embodiment of the STA 111 illustrated in FIG. 3 is for illustration only, and the STAs 111-114 of FIG. 1 could have the same or similar configuration. However, STAs come in a wide variety of configurations, and FIG. 3 does not limit the scope of the disclosure to any particular implementation of a STA.

[0050] The STA 111 may include antenna(s) 305, transceiver(s) 310, a microphone 320, a speaker 330, a processor 340, an input / output (I / O) interface (IF) 345, an input 350, a display 355, and a memory 360. The memory 360 may include an operating system (OS) 361 and one or more applications 362.

[0051] The transceiver(s) 310 may receive, from the antenna(s) 305, an incoming RF signal (e.g., transmitted by an AP 101 of the network 100). The transceiver(s) 310 may down-convert the incoming RF signal to generate an intermediate frequency (IF) or baseband signal. The IF or baseband signal may be processed by RX processing circuitry in the transceiver(s) 310 and / or processor 340, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. The RX processing circuitry may send the processed baseband signal to the speaker 330 (such as for voice data) or is processed by the processor 340 (such as for web browsing data).

[0052] TX processing circuitry in the transceiver(s) 310 and / or processor 340 may receive analog or digital voice data from the microphone 320 or other outgoing baseband data (such as web data, e-mail, or interactive video game data) from the processor 340. The TX processing circuitry may encode, multiplexe, and / or digitize the outgoing baseband data to generate a processed baseband or IF signal. The transceiver(s) 310 may up-convert the baseband or IF signal to an RF signal that is transmitted via the antenna(s) 305.

[0053] The processor 340 may include one or more processors and execute the basic OS program 361 stored in the memory 360 in order to control the overall operation of the STA 111. In one such operation, the processor 340 may control the reception of forward channel signals and the transmission of reverse channel signals by the transceiver(s) 310 in accordance with well-known principles. The processor 340 may also include processing circuitry configured to facilitate supporting incompatible STAs during AP dynamic power save operation. In an embodiment, the processor 340 may include at least one microprocessor or microcontroller. Furthermore, the processor 340 may include various processing circuitry and / or multiple processors. For example, as used herein, including the claims, the term "processor" may include various processing circuitry, including at least one processor, wherein one or more of at least one processor, individually and / or collectively in a distributed manner, may be configured to perform various functions described herein. As used herein, when "a processor", "at least one processor", and "one or more processors" are described as being configured to perform numerous functions, these terms cover situations, for example and without limitation, in which one processor performs some of recited functions and another processor(s) performs other of recited functions, and also situations in which a single processor may perform all recited functions. Additionally, the at least one processor may include a combination of processors performing various of the recited / disclosed functions, e.g., in a distributed manner. At least one processor may execute program instructions to achieve or perform various functions.

[0054] The processor 340 may be also capable of executing other processes and programs resident in the memory 360, such as operations for facilitating supporting incompatible STAs during AP dynamic power save operation. The processor 340 may move data into or out of the memory 360 as required by an executing process. In an embodiment, the processor 340 may be configured to execute a plurality of applications 362, such as applications for facilitating supporting incompatible STAs during AP dynamic power save operation. The processor 340 may operate the plurality of applications 362 based on the OS program 361 or in response to a signal received from an AP. The processor 340 may be also coupled to the I / O interface 345, which provides STA 111 with the ability to connect to other devices such as laptop computers and handheld computers. The I / O interface 345 may be the communication path between these accessories and the processor 340.

[0055] The processor 340 may be also coupled to the input 350, which includes for example, a touchscreen, keypad, etc., and the display 355. The operator of the STA 111 may use the input 350 to enter data into the STA 111. The display 355 may be a liquid crystal display, light emitting diode display, or other display capable of rendering text and / or at least limited graphics, such as from web sites. The memory 360 may be coupled to the processor 340. Part of the memory 360 may include a random-access memory (RAM), and another part of the memory 360 could include a Flash memory or other read-only memory (ROM).

[0056] Although FIG. 3 illustrates an example of STA 111, various changes may be made to FIG. 3. For example, various components in FIG. 3 could be combined, further subdivided, or omitted and additional components could be added according to particular needs. In particular examples, the STA 111 may include any number of antenna(s) 305 for MIMO communication with an AP 101. In an example, the STA 111 may not include voice communication or the processor 340 could be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). Also, while FIG. 3 illustrates the STA 111 configured as a mobile telephone or smartphone, STAs could be configured to operate as other types of mobile or stationary devices.

[0057] An embodiment of the disclosure recognize that as users move around, the signal strength of a station (STA) to its connected access point (AP) may vary. If user movement causes a significant decrease in the signal strength, a handover is necessary. During the process of handover, the STA may switch from its current associated AP to a new AP.

[0058] FIG. 4 illustrates an example of an operating mode notification frame format 400 according to an embodiment of the disclosure. The embodiment of the example operating mode notification frame format 400 shown in FIG. 4 is for illustration only. An embodiment of the example operating mode notification frame format 400 could be used without departing from the scope of the disclosure.

[0059] FIG. 5 illustrates an example of an operating mode A-control field format 500 according to an embodiment of the disclosure. The embodiment of the example operating mode A-control field format 500 shown in FIG. 5 is for illustration only. An embodiment of the example operating mode A-control field format 500 could be used without departing from the scope of the disclosure.

[0060] To provide power saving mechanisms for APs (and also for STAs) that are operating in an awake state, the 802.11 2020 draft defines a power saving mechanism called "operating mode change". By using an operating mode change, a STA may change its operating channel width (CW) and / or the maximum number of spatial streams (NSS) that it may support. Thus, it may save power by reducing channel width or number of spatial streams when required. An AP or non-AP STA may change its RX operating mode by either:

[0061] Transmitting an operating mode notification frame, which is a very high throughput (VHT) Action frame (class 3 management).

[0062] Transmitting an operating mode notification element inside a beacon frame, (re)association request / response frames.

[0063] Transmitting an operating mode (OM) control subfield or EHT OM control subfield in an A-control field of a quality of service (QoS) data, QoS null or class 3 management frames.

[0064] A non-AP STA may change its TX operating mode by either:

[0065] Transmitting an OM control subfield or EHT OM control subfield in an A-control field of a QoS data, QoS null or class 3 management frames.

[0066] For any modulation and coding scheme (MCS), the maximum receive NSS that a STA may support is equal to the smaller of:

[0067] The value of the "Rx Max Nss That Supports Specified MCS" subfield for the given EHT-MCS indicated in the supported EHT-MCS and NSS set.

[0068] The maximum supported NSS as indicated by the value of the Rx NSS field of the operating mode notification frame or the operating mode notification element if the value of Rx NSS type is 0, or by the value of the Rx NSS field of the OM control subfield if EHT OM control subfield is not present in the same A-control field, or by the value of the Rx NSS extension field of the EHT OM control subfield combined with the value of the Rx NSS field of the OM control subfield.

[0069] For any MCS, the maximum transmit NSS that an STA may support is equal to the smaller of:

[0070] The value of the "Tx Max Nss That Supports Specified MCS" subfield for the given EHT-MCS indicated in the supported EHT-MCS and NSS set.

[0071] The maximum supported NSS as indicated by the value of the Tx NSTS field of the OM control subfield if EHT OM control subfield is not present in the same A-control field, or by the value of the Tx NSS extension field of the EHT OM control subfield combined with the value of the Tx NSS field of the OM control subfield.

[0072] FIG. 6 illustrates an example of an extremely high throughput (EHT) operation element 600 that is transmitted by an EHT AP according to an embodiment of the disclosure. The embodiment of the extremely high throughput (EHT) operation element 600 shown in FIG. 6 is for illustration only. An embodiment of the extremely high throughput (EHT) operation element 600 could be used without departing from the scope of the disclosure.

[0073] To indicate the current operating parameters of a basic service set (BSS), the AP may transmit one or more operations elements in its beacons, probe response and association response frames. The AP may use the primary channel field of the HT operations element to indicate a current primary 20MHz channel. It may also use the secondary channel offset field to indicate the location of a secondary 20MHz channel if CW >= 40MHz. The CCFS0 / CCFS1 fields of the VHT operation element (or HE element if VHT is not present) indicate the location of the primary and secondary 80MHz channels. The CCFS0 / CCFS1 fields EHT operation element may indicate the primary and secondary 160MHz channels. The STA channel width field of the HT operations + channel width of the VHT operation element + channel width of the HE operation element + channel width of EHT operation element jointly indicate the operating CW of the BSS. When operating in channels where HT / VHT etc. elements are not present, these fields are replicated in the HE Operation element. For example, the operation of EHT STAs in an EHT BSS is controlled by:

[0074] The HT operation element, HE operation element, and EHT operation element if operating in the 2.4 GHz band

[0075] The HT operation element, VHT operation element (if present), HE operation element, and EHT operation element if operating in the 5 GHz band

[0076] The HE operation element and EHT operation element if operating in the 6 GHz band.

[0077] The basic HT / VHT / HE / EHT MCS and NSS set of the HT / VHT / HE / EHT operations element is what all STAs in the BSS must support at the minimum for HT / VHT / HE / EHT PPDUs. As an example, the format of the EHT operation element is depicted in FIG. 6.

[0078] FIG. 7 illustrates an example of an EHT capabilities element 700 transmitted by an EHT STA according to an embodiment of the disclosure. The embodiment of the EHT capabilities element 700 shown in FIG. 7 is for illustration only. An embodiment of the EHT capabilities element 700 could be used without departing from the scope of the disclosure.

[0079] To indicate the different channel widths, modulation and coding schemes (MCS) and number of spatial streams (NSS) that a STA supports, each STA may also transmit a capabilities element. An illustration of the EHT capabilities element is depicted in FIG. 7. In the supported channel width set field of the capabilities element, a STA may indicate the different channel widths it supports. For an AP, this is a super set of the current BSS channel width indicated in operations element(s). The MCS and NSS that may be supported at each CW is indicated in the supported MCS and NSS set field of the capabilities element. The encoding is quite different for VHT, HE and EHT.

[0080] For HT there is a 77-bit bitmap whose bit i is set to 1 if MCS i is supported. The values are common to all channel widths.

[0081] For VHT, the MCS that may be supported for each NSS is indicated in the range {0-7,0-8,0-9} in a 16-bit supported MCS and NSS set field. The values are common to all channel widths. Difference in the NSS supported for each CW is identified from the 'Supported Channel Width Set' + 'Extended NSS CW Support' fields.

[0082] For HE, the MCS that may be supported for each NSS is indicated in the "Tx / Rx HE-MCS Map" subfields of the "Supported HE MCS and NSS Set" field of the HE capabilities element (similar to VHT). However, the map is separate for each bandwidth range.

[0083] For EHT, the maximum NSS (for TX and RX respectively) for each MCS is indicated in the "EHT-MCS Map" subfield of the "Supported EHT MCS and NSS Set" field of the EHT capabilities element. Indication is separate for each MCS range {0-9,10-11,12-13} and is different for each bandwidth.

[0084] The capabilities element is a "per link indication" and is transmitted by a non-AP STA in:

[0085] Mandatorily carried in an association / reassociation request frame sent by a non-AP STA.

[0086] Mandatorily present in a probe request frame sent by a non-AP STA.

[0087] Mandatorily present in a TDLS discovery request / response frame.

[0088] The capabilities element is a "per link indication" and is transmitted by an AP STA in:

[0089] Mandatorily carried in a beacon frame transmitted by the AP.

[0090] Mandatorily carried in an association / reassociation response frame transmitted by the AP.

[0091] Mandatorily carried in a probe response frame transmitted by the AP.

[0092] FIG. 8 illustrates an example of DPS operation of an AP during an uplink transmission 800 according to an embodiment of the disclosure. The DPS operation of an AP during an uplink transmission 800 may be performed by any of the APs 101, 103 of FIG. 1. The embodiment of the DPS operation of an AP during an uplink transmission 800 shown in FIG. 8 is for illustration only. An embodiment of the DPS operation of an AP during an uplink transmission 800 could be used without departing from the scope of the disclosure.

[0093] More recently in the discussions for IEEE 802.11bn, significant attention has been paid towards the need to reduce the power consumption at the AP side. However, most existing power saving mechanisms for an AP, such as use of operating mode procedures, work at a slow time scale and may cause a significant reduction in the network throughput. To save AP power consumption and minimize the degradation in performance for latency sensitive traffic, dynamic power save (DPS) operation has been proposed. In DPS mode, by default the AP may operate in a low power state with reduced capabilities, e.g., one or more of reduced supported channel width, reduced supported limited physical protocol data unit (PPDU) formats, reduced supported MCS set and NSS set, etc. Operating with these reduced capabilities may help the AP save power. However, upon receiving a request within a TXOP, the AP may transition to a high power state, wherein it increases one or more of its supported channel width (CW), supported PPDU formats, supported MCS set and NSS set for at least the duration of the TXOP. Thus, after sending a request to the AP to increase the capabilities of an AP, the TXOP owner may perform communication at the enhanced high-power state parameters for the rest of the TXOP, with better spectral efficiency. After the end of the TXOP or after a predetermined amount of time from the end of the TXOP, the AP may return to its low power state. An example illustration of this operation is depicted pictorially in FIG. 8.

[0094] Two types of dynamic power save modes may be defined:

[0095] Option 1: Dynamic power saving (DPS) with restriction on CW, NSS, MCS:The AP has two states of operation: a low power (low capability) state and a high power (full capability) state. It operates in a low power state by default, where there are restrictions on (i) the supported channel width (CW), (ii) the supported NSS and (iii) supported MCS. It transitions to a high-power state on demand, after receiving an initial control frame (ICF) from a peer STA. For example, the low power state may support 20MHz CW, 1 SS and MCS at or below a threshold such as MCS 3. These values may be predefined by the standard or may be configurable.

[0096] Option 2: Dynamic power saving (DPS) with restriction on CW, NSS, MCS and PPDU format:This is similar to option 1, but the low power state additionally has a restriction on the decodable PPDU formats compared to high power state. For example, the low power state may be similar to the EMLSR listen state, which supports 20MHz CW, 1 SS and non-HT frames at rates 24 Mbps or below. In some variants of option 2, the AP may not have transmit capabilities when operating in the low power state.

[0097] An embodiment of the disclosure recognize that several types of STAs may be incompatible with DPS operation at the AP, referred to herein asincompatible STAs,for convenience. For example, some STA, such as a pre-UHR STA, may maintain a single capability state of the AP, and presume the AP to always be available. It is not aware of the AP capability to transition between low power and high-power states. Correspondingly, when an AP enables DPS mode, a mechanism to handle already associated incompatible STAs is desirable. Additionally, mechanisms for unassociated incompatible STAs to perform association with an AP in DPS mode are desirable. Finally, mechanisms for an AP to serve incompatible STAs while operating in DPS mode are desirable.

[0098] Accordingly, an embodiment of the disclosure provide mechanisms for interaction of an AP operating in DPS mode with incompatible STAs that do not support DPS operation of the AP, during enablement of DPS mode, during DPS operation, and after disablement of DPS mode.

[0099] FIG. 9 illustrates an example of a scenario of an AP enabling DPS mode with several associated STAs 900 according to an embodiment of the disclosure. The scenario of an AP enabling DPS mode with several associated STAs 900 of FIG. 9 may be performed by any of the STAs 111-114 of FIG. 1, such as the STA 111 of FIG. 3, and any of the APs 101, 103 of FIG. 1, such as the AP 101 of FIG. 2. The embodiment of the scenario of an AP enabling DPS mode with several associated STAs 900 shown in FIG. 9 is for illustration only. An embodiment of the scenario of an AP enabling DPS mode with several associated STAs 900 could be used without departing from the scope of the disclosure.

[0100] FIG. 10 illustrates an example of a UHR capabilities element 1000 indicating a STA's ability to support DPS operation or assist DPS operation at a peer STA according to an embodiment of the disclosure. The embodiment of the UHR capabilities element 1000 shown in FIG. 10 is for illustration only. An embodiment of the UHR capabilities element 1000 could be used without departing from the scope of the disclosure.

[0101] As illustrated in FIG. 9, an AP operating a basic service set (BSS) with several associated STAs is shown, where some of the STAs may be DPS compatible UHR STAs, and some of the STAs may be DPS incompatible STAs. There may also be several unassociated STAs which may intend to associate with the AP later. For implementation specific reasons, the AP may choose to enable or disable DPS mode. Note that, without loss of generality, the AP may be a mobile AP. In the disclosure, the terms bandwidth and channel width (CW) are used interchangeably. In the disclosure, a "limited MCS set" may imply a limitation on the modulations, on the code rates, or both of transmissions. Further, although the term AP is used, an embodiment of the disclosure may also be applicable for a mobile AP, a soft AP in a peer-to-peer network, or a non-AP MLD.

[0102] Incompatible DPS STAs may include one or more of: (i) STAs that do not support DPS operation at a peer STA, (ii) STAs that may operate with a DPS peer STA but without supporting DPS operation, (iii) STAs that cannot operate with a DPS peer STA, etc.

[0103] Incompatible STAs

[0104] In an embodiment, all STAs before a certain Wi-Fi generation may be incompatible with DPS operation at the AP. In an embodiment, a UHR STA may have a capability indication in its UHR capabilities element to indicate if it is compatible with DPS operation at the peer STA or not. The UHR STA may be either an AP or a non-AP STA and the peer STA may correspondingly be a non-AP STA or the AP STA, respectively. This field may be called, for example, the DPS assisting support field. In one variant of this embodiment, the capability indication by the UHR STA may be separate for whether it supports DPS option 1 and DPS option 2 at the peer STA, as described above. These two options may be referred to as the parameterized DPS mode and basic DPS mode, respectively. The capability indication may be carried in fields called the parameterized DPS basic assisting support and basic DPS assisting support, respectively of the UHR capabilities element, as shown in FIG. 10. Similarly, in one embodiment, there may also be separate fields called basic DPS support and parameterized DPS support to indicate if the transmitting STA may itself enable basic DPS operation or parameterized DPS operation or not. In an embodiment, some previous generation STAs may become capable of supporting DPS operation via firmware or software updates. This capability to support DPS may be indicated by the STA to the AP using a frame or element. In an example, the indication may be in a vendor-specific element or frame. In an example, the indication may be in a new element or frame or field defined in 802.11bn. In an embodiment, the AP may determine the compatibility for DPS based on one or more of:

[0105] Wi-Fi generation of the non-AP STA

[0106] The make of the non-AP STA

[0107] Indication of capability support via spec defined or vendor-specific signaling.

[0108] The DPS padding delay applicable to the DPS AP to transition from low power state to high power state.

[0109] The DPS transition delay applicable to the DPS AP to transition from high power state to low power state.

[0110] The type of DPS mode being enabled by the AP (option 1 or option 2), e.g., the capabilities of the AP in the low power state.

[0111] Whether the AP has transmit capability when operating in the low power state.

[0112] For example, if the DPS padding delay is 0 for an AP, it may consider non-AP STAs from a larger set of Wi-Fi generations as DPS compatible, e.g., HE STAs and beyond. If the DPS padding delay is > 0 for an AP, it may consider non-AP STAs from a smaller set of Wi-Fi generations as DPS compatible, e.g., UHR STAs.

[0113] FIG. 11 illustrates an example of an AP removing incompatible STAs before enabling DPS mode and transitioning to the low power state 1100 according to embodiments of the disclosure. The embodiment of the AP removing incompatible STAs before transitioning to the low power state 1100 shown in FIG. 11 is for illustration only. An embodiment of the AP removing incompatible STAs before transitioning to the low power state 1100 could be used without departing from the scope of the disclosure.

[0114] Interaction during DPS enablement:

[0115] As illustrated in FIG. 11, when enabling DPS mode, the AP may transition from the full capability state (AP baseline operation) to the low power state, which may have restriction on the supported bandwidth, NSS, MCS and / or PPDU formats etc. Correspondingly, the AP may need to provide an indication of the reduced capabilities to associated incompatible STAs, if present, before enabling DPS mode. In one embodiment, the AP may not enable DPS mode if there are incompatible associated STAs present. In an embodiment, the AP may prevent the presence of incompatible associated STAs before enabling DPS mode by one or more of:

[0116] using BSS transition management procedures to transition associated incompatible STAs to other APs or links, before enabling DPS mode.

[0117] disassociating incompatible STAs before enabling DPS mode.

[0118] This procedure is depicted pictorially in FIG. 11. In a variant of this embodiment, the incompatible non-AP STAs may associate with the AP after the DPS is enabled. In an embodiment, the incompatible non-AP STAs may not be allowed to associate with the AP after DPS is enabled.

[0119] FIG. 12 illustrates an example of an AP providing an indication of reduced capabilities for sufficient time before enabling DPS mode and transitioning to the low power state 1200 according to embodiments of the disclosure. The embodiment of the AP providing an indication of reduced capabilities for sufficient time before transitioning to the low power state 1200 shown in FIG. 12 is for illustration only. An embodiment of the AP providing an indication of reduced capabilities for sufficient time before transitioning to the low power state 1200 could be used without departing from the scope of the disclosure.

[0120] As illustrated in FIG. 12, in an embodiment, the AP may allow incompatible associated STAs to maintain association with the AP while the AP transitions to the low power state. In order to do so, the AP may provide an indication of its reduced capabilities to the incompatible STAs for sufficient time before transitioning to the low power state. The indication may be carried, for example, in broadcast or management frames, such as beacon frames, probe response, association response frames etc. The sufficient time may be determined such that all associated incompatible STAs would have a chance to receive the indication with high likelihood. This procedure is depicted pictorially in FIG. 12. In a variant of this embodiment, the AP may ask the incompatible STAs to re-associate with the AP, so that the AP may indicate the updated reduced capabilities to these STAs. In one embodiment, a new mechanism for an AP to indicate to one or more associated non-AP STAs that satisfy certain criteria to re-associate with the AP may be defined. This may be done by defining a new broadcast frame, that also indicates the criteria to be satisfied by the non-AP STAs. Incompatible non-AP STAs may associate with the AP after the DPS is enabled using the baseline procedure. In an embodiment, an AP that is capable of DPS operation and that intends to transition to DPS mode at some time may indicate its reduced capabilities to DPS incompatible STAs since their association, even if DPS is disabled during the association. Correspondingly, the AP may always communicate with DPS incompatible STAs as per the low power state capabilities, even when DPS is disabled.

[0121] In an embodiment, there may be multiple classes of incompatible STAs, (i) ones for whom indication of AP capabilities in low power state may be provided using other mechanisms and correspondingly ones that may still operate with a DPS AP, (ii) for whom there are no mechanisms to indicate the AP's reduced capabilities in the low power state and so which cannot operate with a DPS AP. The other mechanisms for type (i) may include procedures defined in older Wi-Fi generation standards. Correspondingly, for STAs of type (ii) the mechanisms mentioned in FIG. 11 may be followed while for STAs of type (i) mechanisms in FIG. 12 may be used by the AP.

[0122] In an embodiment, the indication method of the reduced capabilities to follow may be dependent on the parameters of the DPS mode and the type of incompatible STAs associated. These may include:

[0123] The AP capabilities (CW, NSS, MCS, PPDU format support, etc.) before enabling the DPS mode

[0124] The AP capabilities (CW, NSS, MCS, PPDU format support, etc.) during the low power state

[0125] The AP capabilities (CW, NSS, MCS, PPDU format support, etc.) during the high power state

[0126] The type of DPS operation enabled by the AP, i.e., option 1 or option 2.

[0127] The Wi-Fi generation of the incompatible STA (non-HT / HT / VHT / HE / EHT / UHR etc.).

[0128] The DPS parameters of the AP, including the DPS Padding delay and DPS Transition delay.

[0129] In an embodiment, where the DPS padding delay and / or DPS transition delay are 0 for the AP, the AP may not directly signal the reduced operating parameters to the associated STAs. Instead, the AP may set the TXOP duration RTS threshold field of the HE operation parameters field of the HE operations element to ensure that all transmissions with the AP by HE+ STAs are initiated with an RTS-CTS exchange. This way, even though other non-AP STA may not be aware of the exact low power state capabilities of the AP, the transmission of the RTS by the AP gives it sufficient time to switch to the high power state. Here the other non-AP STA may be a device compliant with an older generation Wi-Fi standard. In an example the AP may set the TXOP duration RTS threshold field to a value of 1.

[0130] In an embodiment, the AP may not explicitly signal each of the CW, NSS, MCS, PPDU format supported in the low power state. Rather, the AP may skip the operation elements corresponding to several Wi-Fi generations to make the DPS incompatible STAs think that the AP is of an older generation, for example, of the non-HT generation. Correspondingly, the DPS incompatible STAs may think the AP is capable of the CW, NSS, MCS and PPDU format supported in those older Wi-Fi generation devices. In a variant of this case, the AP may ask the incompatible STAs to re-associate with the AP. For DPS compatible non-AP STAs and / or UHR non-AP STAs, the AP may separately signal its full capabilities including that it is a UHR AP.

[0131] Supported CW reduction indication:

[0132] In an embodiment, the AP may indicate a reduction in its operating CW before enabling the DPS mode. The indicated operating CW may be, for example, the same or smaller than the supported CW in the low power state. To indicate a reduction in operating CW:

[0133] In an example, an AP may indicate a reduction in its operating channel width by including the channel switch announcement element, extended channel switch announcement element or operating mode element in beacon frames, probe response and association response frames that it transmits.

[0134] In an example, an AP may also use a broadcast channel switch announcement frame, extended channel switch announcement frame or operating mode notification frame for such indication.

[0135] In an example, an AP may also provide the indication in the OM control subfield of a QoS data, QoS null or class 3 management frame that it transmits.

[0136] For example, if the AP supports 20MHz as the channel width in the low power state, it may set the channel width field of the operating mode element or operating mode notification frame or OM control field to 0. In one embodiment, there may be a new field in the operating mode element or operating mode notification frame or OM control field to indicate that the reduction in bandwidth corresponds to the low power state of the DPS and / or is applicable to non-DPS supporting non-AP STAs. DPS compatible non-AP STAs which receive this indication may be able to identify whether the change in channel width indicated by the operating mode change impacts the high power state or low power state or both of the AP.

[0137] The reduced value of the supported channel width may also be indicated by the AP in the operation elements and capabilities elements it transmits in beacon, probe response and association response frames. The changes may be included in all or a subset of the capabilities and operation elements {HT, VHT, HE, EHT, UHR}. For example, these indications may be carried in one or more of:

[0138] STA Channel Width field and Secondary Channel Offset field of the HT Operations element

[0139] Supported Channel Width Set field of the HT Capabilities element

[0140] Channel Width field and CCFS0 / CCFS1 fields of the VHT Operations element

[0141] Supported Channel Width Set field and Extended NSS BW Support field of the VHT Capabilities element

[0142] Channel Width field and CCFS0 / CCFS1 fields of the HE Operations element

[0143] Supported Channel Width Set field of the HE Capabilities element

[0144] Channel Width field and CCFS0 / CCFS1 fields of the EHT Operations element

[0145] Supported Channel Width Set field of the EHT Capabilities element.

[0146] The change in these parameters may be indicated as a critical update. For example, if the AP supports 20MHz as the channel width in the low power state, it may indicate the operating bandwidth as 20MHz in HT, VHT, HE and EHT operation elements and CCFS1 field to 0 in VHT, HE and EHT operation elements. Appropriate changes may also be indicated in the capabilities element. In a variant, it may be understood that UHR non-AP STAs that do not support DPS also use the EHT operating bandwidth as the operating bandwidth to be used by them.

[0147] After providing the indication for sufficient time to ensure all associated STAs may have received it, the AP may transition to the low power state. Incompatible STAs may be expected to operate with the AP using this indicated operating CW.

[0148] In an embodiment, incompatible UHR STAs may be expected to operate with the AP as per the operation bandwidth indicated by the AP in the latest generation pre-UHR operations element (EHT>HE>VHT>HT). In an embodiment, the AP may carry an indication of the bandwidth applicable to the incompatible UHR STAs in frames it transmits, such as beacon frames, probe response frames or association response frames. The indication may be carried in, for example, the UHR operations element in a channel width field or a nominal channel width field. In an embodiment, the spec may predefine the channel width that is supported in the low power state when DPS is enabled, and hence incompatible UHR STAs may know of the supported channel width based on whether the DPS is indicated as being enabled or not by the AP.

[0149] Supported NSS reduction indication:

[0150] In an embodiment, the AP may indicate a reduction in maximum supported receive NSS and / or transmitted NSTS before enabling the DPS mode. The indicated NSS may be, for example, the same or smaller than the supported maximum NSS in the low power state. To indicate reduction in NSS:

[0151] In an example, an AP may indicate a reduction in its RX NSS by including an operating mode element in beacon frames, probe response and association response frames that it transmits.

[0152] In an example, an AP may also use a broadcast operating mode notification frame for such indication.

[0153] In an example, an AP may also provide the indication in the OM control subfield of a QoS data, QoS null or class 3 management frame that it transmits.

[0154] For example, if the AP supports 1 SS in the low power state, it may set the Rx NSS field of the operating mode element or operating mode notification frame or OM control field to 0. The Tx NSTS field may also be set to 0 in an example. In one embodiment, there may be a new field in the operating mode element or operating mode notification frame or OM control field to indicate that the reduction in the NSS corresponds to the low power state of the DPS and / or is applicable to non-DPS supporting non-AP STAs. DPS compatible non-AP STAs which receive this indication may be able to identify whether the change in NSS indicated by the operating mode change impacts the high power state or low power state or both of the AP.

[0155] The reduced maximum NSS supported may also be indicated by the AP in the operation elements and capabilities elements it transmits in beacon, probe response and association response frames. The changes may be included in all or a subset of the capabilities and operation elements {HT, VHT, HE, EHT, UHR}. For example, these indications may be carried in one or more of:

[0156] Basic HT-MCS Set field of the HT Operations element

[0157] Supported MCS Set field and Transmit Beamforming Capabilities field of the HT Capabilities element

[0158] Basic VHT-MCS and NSS Set field of the VHT Operations element

[0159] Supported VHT-MCS and NSS Set field and Extended NSS BW Support field of the VHT Capabilities element

[0160] Basic HE-MCS and NSS Set field of the HE Operations element

[0161] Supported HE-MCS and NSS Set field of the HE Capabilities element

[0162] Basic EHT-MCS and NSS Set field of the EHT Operations element

[0163] Supported EHT-MCS and NSS Set field of the EHT Capabilities element.

[0164] The change in these parameters may be indicated as a critical update. For example, if the AP supports 1 spatial stream in the low power state, it may set:

[0165] The bits 8-76 of the Rx MCS Bitmask of the Basic MCS and NSS Set field are set to 0, in the HT Operations element to 0.

[0166] The bits 8-76 of the Rx MCS Bitmask field are set to 0 and the Tx Maximum Number Spatial Streams Supported field is set to 0, in the Supported MCS Set field of the HT Capabilities element.

[0167] The Extended NSS BW Support field to 0, and Max VHT-MCS For x SS field to 3 for x > 1 in the Supported VHT-MCS and NSS Set field of the VHT Capabilities element.

[0168] The Max VHT-MCS For x SS field to 3 for x > 1 in the Basic VHT-MCS and NSS Set of the VHT Operations element.

[0169] The Max HE-MCS For x SS field to 3 for x > 1 in the Rx HE-MCS Map subfield and Tx HE-MCS Map subfield of the Basic HE-MCS And NSS Set field of the HE Operations element.

[0170] The Max HE-MCS For x SS field to 3 for x > 1 in the Rx HE-MCS Map fields and Tx HE-MCS Map fields of the Supported HE-MCS And NSS Set field of the HE Capabilities element.

[0171] The Rx Max NSS That Supports EHT-MCS fields and Tx Max NSS That Supports EHT-MCS fields are all set to either 0 or 1 (depending on the MCS supported) in the EHT-MCS Map field of the Basic EHT-MCS And NSS Set field of the EHT Operations element.

[0172] The Rx Max NSS That Supports EHT-MCS fields and Tx Max NSS That Supports EHT-MCS fields are all set to either 0 or 1 (depending on the MCS supported) in the EHT-MCS Map field of the Supported EHT-MCS And NSS Set field of the EHT Capabilities element.

[0173] After providing the indication for sufficient time to ensure all associated STAs may have received it, the AP may transition to the low power state. Incompatible STAs may be expected to operate with the AP up to the indicated RX NSS values.

[0174] In an embodiment, incompatible UHR STAs may be expected to operate with the AP as per the supported MCS and NSS sets indicated by the AP in the latest generation pre-UHR operations element (EHT>HE>VHT>HT). In an embodiment, the AP may carry an indication of the MCS and NSS combinations applicable to the incompatible UHR STAs in frames it transmits, such as beacon frames, probe response frames or association response frames. The indication may be carried in, for example, the UHR capabilities element in the reduced UHR MCS and NSS set fields. In an embodiment, the spec may predefine the NSS that is supported in the low power state when DPS is enabled, and hence incompatible UHR STAs may know of the supported NSS based on whether the DPS is indicated as being enabled or not by the AP.

[0175] Supported MCS reduction indication

[0176] In one embodiment, the AP may indicate a reduction in supported MCS set or maximum supported data rate before enabling the DPS mode. In a variant the reduction in MCS may refer to a reduction in the supported modulations and / or code rates. The indicated MCS sets and data rates may be, for example, the same or a subset of the supported MCS sets and data rates in the low power state. To indicate reduction in MCS sets, in an example, the AP may update one or more of: (i) the basic MCS and NSS set field of the operation elements and (ii) the MCS and NSS sets tables broadcast by the AP in the capabilities elements of beacon, probe response and association response frames. The changes may be included in all or a subset of the capabilities and operation elements {HT, VHT, HE, EHT, UHR}. In addition, for a non-HT case, the indication of reduction in supported rates may be carried in the supported rates and BSS membership selectors element of the beacon frames. For example, these indications may be carried in one or more of:

[0177] Supported Rates and BSS Membership Selectors element

[0178] Basic HT-MCS Set field of the HT Operations element

[0179] Supported MCS Set field and Transmit Beamforming Capabilities field of the HT Capabilities element

[0180] Basic VHT-MCS and NSS Set field of the VHT Operations element

[0181] Supported VHT-MCS and NSS Set field and Extended NSS BW Support field of the VHT Capabilities element

[0182] Basic HE-MCS and NSS Set field of the HE Operations element

[0183] Supported HE-MCS and NSS Set field of the HE Capabilities element

[0184] Basic EHT-MCS and NSS Set field of the EHT Operations element

[0185] Supported EHT-MCS and NSS Set field of the EHT Capabilities element.

[0186] The change in these parameters may be indicated as a critical update. In one variant, if the indication in the aforementioned elements does not provide sufficient granularity to indicate the maximum supported MCS, an MCS smaller or larger than the maximum supported MCS in the low power state may be indicated by the AP, and additional mechanisms such as link adaptation may be used to handle the limited MCS issue, as described later. For example, if the AP supports modulation up to 64-QAM and code rate ≤5 / 6 (for HT or beyond PPDUs) and rate ≤24Mbps (for non-HT PPDUs) in the low power state, it may set:

[0187] AP updates Supported Rates and BSS Membership Selectors element in Beacon frames to indicate support for ≤24Mbps.

[0188] The bits B32-76 of the Rx MCS Bitmask of the Basic MCS and NSS Set field are set to 0, in the HT Operations element to 0.

[0189] The bits B7, B15, B23, B31 and bits B32-76 of the Rx MCS Bitmask field are set to 0, in the Supported MCS Set field of the HT Capabilities element.

[0190] The Max VHT-MCS For x SS field of the Rx VHT-MCS Map and Tx VHT-MCS Map is set to 0 for each supported spatial streams x in the Supported VHT-MCS and NSS Set field of the VHT Capabilities element.

[0191] The Max VHT-MCS For x SS field of the Rx VHT-MCS Map and Tx VHT-MCS Map is set to 0 for each supported spatial streams x in the Basic VHT-MCS and NSS Set of the VHT Operations element.

[0192] The Max HE-MCS For x SS field of the Rx HE-MCS Map and Tx HE-MCS Map is set to 0 for each supported spatial streams x in the Rx HE-MCS Map subfield and Tx HE-MCS Map subfield of the Basic HE-MCS And NSS Set field of the HE Operations element.

[0193] The Max HE-MCS For x SS field of the Rx HE-MCS Map and Tx HE-MCS Map is set to 0 for each supported spatial streams x of the Supported HE-MCS And NSS Set field of the HE Capabilities element.

[0194] The Rx Max NSS That Supports EHT-MCS fields and Tx Max NSS That Supports EHT-MCS x fields are set to 0 for x > 7 in the EHT-MCS Map field of the Basic EHT-MCS And NSS Set field of the EHT Operations element. In an example, the value of x may be 9.

[0195] After providing the indication for sufficient time to ensure all associated STAs may have received it, the AP may transition to the low power state.

[0196] In an embodiment, the AP may also rely on the link adaptation mechanism of Wi-Fi to enable incompatible non-AP STAs to perform frame exchanges with the AP as per the AP's low power state capabilities. For example, if an incompatible non-AP STA initiates transmission at an MCS that isn't supported by the AP in the low power state, the frame exchange may fail and correspondingly over time the non-AP STA may adapt to the MCS which is supported by the AP in the low power state. In one variant of this embodiment, if an AP receives a frame from an incompatible non-AP STA while the AP is in high power state and / or the AP receives a frame successfully at an MCS that isn't supported by the AP in the low power state, it may not respond to the non-AP STA to ensure that the link adaptation mechanism at the non-AP STA works correctly and picks MCS less than the max MCS supported by the AP in the low power state. This mechanism may be used, for example, if the AP indicates a support for EHT MCS 0-9 to EHT STAs in the EHT capabilities and operations elements, but the supported maximum MCS in the low capability state is smaller, for example, MCS 6.

[0197] In an embodiment, incompatible UHR STAs may be expected to operate with the AP as per the supported MCS and NSS sets indicated by the AP in the latest generation pre-UHR operations element (EHT>HE>VHT>HT). In an embodiment, the AP may carry an indication of the MCS and NSS combinations applicable to the incompatible UHR STAs in frames it transmits, such as beacon frames, probe response frames or association response frames. The indication may be carried in, for example, the UHR capabilities element in the reduced UHR MCS and NSS set fields. In an embodiment, the spec may predefine the MCS that is supported in the low power state when DPS is enabled, and hence incompatible UHR STAs may know of the supported MCS based on whether the DPS is indicated as being enabled or not by the AP.

[0198] Supported PPDU format reduction indication:

[0199] In an embodiment, the AP may indicate a reduction in supported PPDU formats before switching to the DPS mode. To indicate reduction in supported PPDU formats, the AP may skip the operation elements and capabilities elements that it transmits in beacon, probe response and association response frames. The changes may be included in all or a subset of the capabilities and operation elements {HT, VHT, HE, EHT, UHR}. The skipping of these elements may be indicated as a critical update. In addition, the AP may skip any other generation-specific fields corresponding to a subset of the generations {HT, VHT, HE, EHT, UHR}, from broadcast or management frames such as beacon, probe response and association response frames. The exclusion of such fields may be such that incompatible STAs think the AP is of an older generation. In one embodiment, the AP may disassociate incompatible STAs before performing this operation, and allow them to re-associate. After providing the indication for sufficient time to ensure all associated STAs may have received it, the AP may transition to the low power state. In an embodiment, all PPDU formats may be supported by the DPS AP in the low power state, in which case, no new indication may be required for incompatible STAs.

[0200] In an embodiment, incompatible UHR STAs may be expected to operate with the AP as per the latest pre-UHR PPDU format supported by the AP, as indicated by the latest generation pre-UHR operations element (EHT>HE>VHT>HT) it carries in beacon, probe response and / or association response frames. In an embodiment, the AP may carry an indication of the PPDU formats applicable to the incompatible UHR STAs in frames it transmits, such as beacon frames, probe response frames or association response frames. The indication may be carried in, for example, the UHR capabilities element in the reduced capability PHY version field. In an embodiment, the spec may predefine the PPDU formats that are supported in the low power state when DPS is enabled, and hence incompatible UHR STAs may know of the supported PPDU formats based on whether the DPS is indicated as being enabled or not by the AP.

[0201] In an embodiment, the spec may predefine one or more options for the supported channel width, MCS, NSS and PHY version in the low capability state of DPS operation. Correspondingly, when enabling DPS, the identifier for the applicable option may be indicated in the frame transmitted by the AP to enable DPS mode. For example, some options are as follows: Option 0: {20MHz, 1SS, non-HT PPDUs with rate < 24Mbps}, Option 1: {20MHz, 1SS, up to UHR PPDUs, MCS 0-6}, Option 2: {20MHz, 1SS, up to UHR PPDUs, MCS 0-9}, Option 3: {40MHz, 1SS, up to UHR PPDUs, MCS 0-6}, etc.

[0202] Transmission to incompatible STAs after DPS enablement:

[0203] In an embodiment, after the AP DPS mode is enabled, the incompatible STAs may communicate with the AP as per the reduced CW, NSS, MCS and PPDU formats indicated to the STAs before enabling DPS mode.

[0204] Association of STAs after DPS enablement:

[0205] In an embodiment, the AP may be capable of receiving a probe request from an unassociated STA, if the probe request frame complies with the low power state capabilities of the AP. In one embodiment, the AP may not be capable of transmission when operating in the low power state. Upon receiving a probe request from an unassociated STA, the AP may first transition to the high power state and it may transmit a probe response frame. In an embodiment, the AP may be capable of transmission in the low power state. Correspondingly upon receiving a probe request frame an unassociated STA, the AP may immediately transmit a probe response frame if required. In one embodiment, the AP may not permit incompatible STAs from associating with it. In one embodiment, the AP may disable DPS mode when an incompatible STA attempts association with it. In an embodiment, the AP may allow other STAs to associate with it. As discussed before, the probe response and association response frames transmitted by the AP after enabling DPS mode may carry indication of the reduced CW, NSS, MCS and PPDU format support.

[0206] Supporting advanced PHY features:

[0207] FIG. 13 illustrates an example of a DPS wrapper element 1300 which may hold one or more previous generation elements according to embodiments of the disclosure. The embodiment of the example DPS wrapper element 1300 shown in FIG. 13 is for illustration only. An embodiment of the example DPS wrapper element 1300 could be used without departing from the scope of the disclosure.

[0208] In an embodiment, where the AP has reduced PHY version support during the low power state, it may skip elements of specific generations from beacon frames. For example, if the AP supports EMLSR listen operation in the low power state, it may skip the HT, VHT, HE and EHT operation elements and / or capabilities elements from its beacon, probe response and association response frames. Correspondingly, several features, such as MPDU aggregation, WPA2, WPA3, multi-link operation, target wake time, block acknowledgement, MIMO, OFDMA etc., may not be available for the incompatible STAs.

[0209] In an embodiment, one or more of the skipped fields from operation elements and capabilities elements may be included in some new UHR elements defined for supporting DPS operation. In one variant, a DPS wrapper element may be defined in UHR that may hold any of these previous generation elements which were skipped from the beacons, probe response, association response frames etc. Each such DPS wrapper element may be designed to hold one or more of these elements.

[0210] Thus, the AP may include all such skipped elements from the beacon, probe response and association response frames within the DPS wrapper element and reintroduce them within those frames. The DPS wrapper elements may be ignored by incompatible STAs. An example illustration of this element is depicted in FIG. 13. The included elements may be identified from the element ID of the included element.

[0211] In an embodiment, the AP may include one or more of these skipped fields in some UHR-specific fields of frames that it transmits or in some UHR-specific frames that it transmits. For example, there may be a UHR-specific subfield of the beacon frame to carry these indications. In an example, there may be a separate UHR-specific follow-up group-addressed frame to the beacon frame which may carry such skipped fields.

[0212] Interaction after DPS disablement:

[0213] FIG. 14 illustrates an example of an AP removing incompatible STAs before disabling the DPS mode 1400 according to embodiments of the disclosure. The embodiment of the AP removing incompatible STAs before disabling the DPS mode 1400 shown in FIG. 14 is for illustration only. An embodiment of the AP removing incompatible STAs before disabling the DPS mode 1400 could be used without departing from the scope of the disclosure.

[0214] After disabling the DPS mode, the AP may transition back to the full capability state (AP baseline operation). Correspondingly, the AP may need to provide an indication of the enhanced capabilities to associated incompatible STAs, if present, after disabling the DPS mode. In an embodiment, the AP may prevent the presence of incompatible associated STAs during disabling the DPS mode by one or more of:

[0215] using BSS transition management procedures to transition associated incompatible STAs to other APs or links, before disabling the DPS mode.

[0216] disassociating incompatible STAs before disabling the DPS mode.

[0217] This procedure is depicted pictorially in FIG. 14.

[0218] FIG. 15 illustrates an example of an AP providing an indication of return to full capabilities for sufficient time after disabling DPS mode and transitioning to the full capability state 1500 according to embodiments of the disclosure. The embodiment of the AP providing an indication of return to full capabilities for sufficient time after transitioning to the full capability state 1500 shown in FIG. 15 is for illustration only. An embodiment of the AP providing an indication of return to full capabilities for sufficient time after transitioning to the full capability state 1500 could be used without departing from the scope of the disclosure.

[0219] In an embodiment, the AP may allow incompatible associated STAs to maintain association with the AP while the AP disables the DPS mode. In order to do so, the AP may provide an indication of its enhanced capabilities to the incompatible STAs for sufficient time after transitioning to full capability state. The indication may be carried, for example, in broadcast or management frames, such as beacon frames, probe response, association response frames etc. The sufficient time may be determined such that all associated incompatible STAs would have a chance to receive the indication with high likelihood. This procedure is depicted pictorially in FIG. 15. The mechanisms for the indication may be similar to the ones used to indicate restrictions to CW, NSS, MCS described above. For indicating an increase in the PPDU format decoding capability, the AP may reintroduce the corresponding generation elements back into the management frames (beacons, probe response, association response) that it transmits and remove a DPS wrapper element.

[0220] FIG. 16 illustrates an example method 1600 performed by an AP for supporting incompatible STAs during DPS operation according to embodiments of the disclosure. The method 1600 of FIG. 16 may be performed by any of the APs 101, 103 of FIG. 1, such as AP 101 of FIG. 2. The method 1600 shown in FIG. 16 is for illustration only. An embodiment of the method 1600 could be used without departing from the scope of the disclosure.

[0221] As illustrated in FIG. 16, the method 1600 begins at operation 1602, where a determination is made whether a transition to the DPS mode is desired. When a transition to the DPS mode is desired, at operation 1604, incompatible STAs are disassociated, if applicable. At operation 1606, an indication of the reduced operating parameters (CW, NSS, MCS, PPDU format, etc.) is transmitted, if applicable. At operation 1608, after an applicable time, the AP switches into the DPS mode. At operation 1610, the AP responds to probe request frames received from a STA that are appropriately based on the AP low power state capability. At operation 1612, the AP responds to association request frames received from a STA that are appropriately based on associating STA capability. At operation 1614, the AP carries certain Wi-Fi generation elements of beacon, probe response and association response frames within DPS Wrapper elements, if applicable. At operation 1616, a determination is made whether transition out of the DPS mode is desired. At operation 1618, when transition out of the DPS mode is desired, the AP transitions to the full capability state. At operation 1620, the AP transmits an indication of the enhanced operating parameters (CW, NSS, MCS, PPDU format, etc.), if applicable.

[0222] FIG. 17 illustrates an example method 1700 performed by a DPS incompatible STA during DPS operation according to embodiments of the disclosure. The method 1700 of FIG. 17 may be performed by any of the APs 101, 103 of FIG. 1, such as AP 101 of FIG. 2. The method 1700 shown in FIG. 17 is for illustration only. An embodiment of the method 1700 could be used without departing from the scope of the disclosure.

[0223] As illustrated in FIG. 17, the method 1700 begins at operation 1702, where the STA indicates that it is DPS incompatible. At operation 1704, upon receiving an indication to disassociate or perform BSS transition, the STA complies with the request. At operation 1706, upon receiving an indication of AP reduced operating parameters (CW, NSS, MCS, PPDU format, etc.), the STA follows the appropriate transmission rules. At operation 1708, upon receiving an indication of AP enhanced operating parameters (CW, NSS, MCS, PPDU format, etc.), the STA follows the appropriate transmission rules.

[0224] FIG. 18 illustrates an example method 1800 performed by an AP in a wireless communication system for supporting incompatible STAs during DPS operation according to embodiments of the disclosure. The method 1800 of FIG. 18 may be performed by any of the APs 101, 103 of FIG. 1, such as AP 101 of FIG. 2. The method 1800 shown in FIG. 18 is for illustration only. An embodiment of the method 1800 could be used without departing from the scope of the disclosure.

[0225] As illustrated in FIG. 18, the method 1800 begins at operation 1802, where the AP determines compatibility of a first STA associated with the AP for a DPS mode. At operation 1804, the AP performs an enablement operation associated with enablement of the DPS mode based on the determined compatibility of the first STA for the DPS mode.

[0226] In an embodiment, the AP is configured to not enable the DPS mode when the determined compatibility of the first STA is incompatible with the DPS mode.

[0227] In an embodiment, the AP is configured to: enable the DPS mode when the determined compatibility of the first STA is incompatible with the DPS mode; and during enablement of the DPS mode when the determined compatibility of the first STA is incompatible with the DPS mode, maintain association with the first STA while transitioning from a high power state to a low power state by providing an indication of reduced capabilities to the first STA before enabling the DPS mode, wherein the reduced capabilities and the method of indication are based on parameters of the DPS mode or a type of the first STA.

[0228] In an embodiment, the indication of reduced capabilities comprises an indication of a reduced channel width included in an operating mode notification frame or operating mode element, operation elements, or capabilities elements, corresponding to one or more Wi-Fi generations, transmitted in a frame by the AP.

[0229] In an embodiment, the indication of reduced capabilities comprises an indication of a reduced number of spatial streams (NSS) included in an operating mode notification frame or operating mode element, operation elements, or capabilities elements, corresponding to one or more Wi-Fi generations, transmitted in a frame by the AP.

[0230] In an embodiment, the indication of reduced capabilities comprises an indication of a reduced modulation and coding scheme (MCS) included in an operating mode element, an operating mode notification frame, operation elements, or capabilities elements.

[0231] In an embodiment, the reduced capabilities comprises one or more of a reduced channel width, a reduced number of spatial streams (NSS), a reduced modulation and coding scheme (MCS) or a reduced physical protocol data unit (PPDU) supported by the AP, which are indicated by exclusion of operation elements, or capabilities elements corresponding to one or more Wi-Fi generations in a frame transmitted by the AP.

[0232] In an embodiment, the AP is configured to communicate with the first STA based on the reduced capabilities that were indicated to the first STA before enabling the DPS mode.

[0233] In an embodiment, the AP is configured to: receive, from a second STA not associated with the AP, a probe request that complies with the reduced capabilities indicated to the first STA; and transmit a probe response to the second STA.

[0234] In an embodiment, the AP is configured to: disable the DPS mode; and during disablement of the DPS mode, maintain association with the first STA while transitioning from the low power state to the high power state by providing an indication of enhanced capabilities to the first STA after disabling the DPS mode, wherein the enhanced capabilities are based on the parameters of the DPS mode or the type of the first STA.

[0235] The flowcharts herein illustrate example methods or processes that may be implemented in accordance with the principles of the disclosure and various changes could be made to the methods or processes illustrated in the flowcharts.　For example, while shown as a series of operations, various operations could overlap, occur in parallel, occur in a different order, or occur multiple times. In an example, operations may be omitted or replaced by other operations.

[0236] It will be appreciated that various embodiments of the disclosure according to the claims and description in the specification can be realized in the form of hardware, software or a combination of hardware and software.

[0237] Any such software may be stored in non-transitory computer readable storage media. The non-transitory computer readable storage media store one or more computer programs (software modules), the one or more computer programs include computer-executable instructions that, when executed by one or more processors of an electronic device individually or collectively, cause the electronic device to perform a method of the disclosure.

[0238] Any such software may be stored in the form of volatile or non-volatile storage such as, for example, a storage device like read only memory (ROM), whether erasable or rewritable or not, or in the form of memory such as, for example, random access memory (RAM), memory chips, device or integrated circuits or on an optically or magnetically readable medium such as, for example, a compact disk (CD), digital versatile disc (DVD), magnetic disk or magnetic tape or the like. It will be appreciated that the storage devices and storage media are various embodiments of non-transitory machine-readable storage that are suitable for storing a computer program or computer programs comprising instructions that, when executed, implement various embodiments of the disclosure. Accordingly, various embodiments provide a program comprising code for implementing apparatus or a method as claimed in any one of the claims of this specification and a non-transitory machine-readable storage storing such a program.

[0239] While the disclosure has been shown and described with reference to various embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the disclosure as defined by the appended claims and their equivalents.

Claims

1.A method performed by an access point (AP) in wireless communication, the method comprising:determining (1602) whether a transition to a dynamic power save (DPS) mode is desired;determining (1604) a compatibility of a first station (STA) associated with the AP for the DPS mode;determining enabling the DPS mode based on the compatibility of the first STA being incompatible with the DPS mode;maintaining association with the first STA while transitioning from a high power state to a low power state by providing (1606) an indication of reduced capabilities to the first STA, wherein the indication of reduced capabilities is based on at least one parameter of the DPS mode or a type of the first STA; andenabling (1608) the DPS mode.2.The method of Claim 1, wherein the indication of reduced capabilities comprises an indication of a reduced channel width included in an operating mode notification frame or operating mode element, operation elements, or capabilities elements, corresponding to one or more Wi-Fi generations, transmitted in a frame by the AP.3.The method of Claim 1, wherein the indication of reduced capabilities comprises an indication of a reduced number of spatial streams (NSS) included in an operating mode notification frame or operating mode element, operation elements, or capabilities elements, corresponding to one or more Wi-Fi generations, transmitted in a frame by the AP.4.The method of Claim 1, wherein the indication of reduced capabilities comprises an indication of a reduced modulation and coding scheme (MCS) included in an operating mode element, an operating mode notification frame, operation elements, or capabilities elements.5.The method of Claim 1, wherein the reduced capabilities comprises one or more of a reduced channel width, a reduced number of spatial streams (NSS), a reduced modulation and coding scheme (MCS) or a reduced physical protocol data unit (PPDU) supported by the AP, which are indicated by exclusion of operation elements, or capabilities elements corresponding to one or more Wi-Fi generations in a frame transmitted by the AP.6.The method of Claim 1, further comprising communicating with the first STA based on the reduced capabilities that were indicated to the first STA before enabling the DPS mode.7.The method of Claim 1, further comprising:receiving, from a second STA not associated with the AP, a probe request that complies with the reduced capabilities indicated to the first STA; andtransmitting a probe response to the second STA.8.The method of Claim 1, further comprising:disabling the DPS mode; andmaintaining association with the first STA while transitioning from the low power state to the high power state by providing an indication of enhanced capabilities to the first STA, wherein the indication of enhanced capabilities are based on the parameters of the DPS mode or the type of the first STA.9.An access point (AP) (101) comprising:memory (230) storing instructions; andat least one processor (225) operably coupled with the memory,wherein the instructions, when executed by the processor individually or collectively, cause the AP to:determine whether a transition to a dynamic power save (DPS) mode is desired;determine a compatibility of a first station (STA) associated with the AP for the DPS mode;determine enable the DPS mode based on the compatibility of the first STA being incompatible with the DPS mode;maintain association with the first STA while transitioning from a high power state to a low power state by providing an indication of reduced capabilities to the first STA, wherein the indication of reduced capabilities is based on at least one parameter of the DPS mode or a type of the first STA; andenable the DPS mode.10.The AP of Claim 9, wherein the indication of reduced capabilities comprises an indication of a reduced channel width included in an operating mode notification frame or operating mode element, operation elements, or capabilities elements, corresponding to one or more Wi-Fi generations, transmitted in a frame by the AP, orwherein the indication of reduced capabilities comprises an indication of a reduced number of spatial streams (NSS) included in an operating mode notification frame or operating mode element, operation elements, or capabilities elements, corresponding to one or more Wi-Fi generations, transmitted in a frame by the AP, orwherein the indication of reduced capabilities comprises an indication of a reduced modulation and coding scheme (MCS) included in an operating mode element, an operating mode notification frame, operation elements, or capabilities elements.11.The AP of Claim 9, wherein the reduced capabilities comprises one or more of a reduced channel width, a reduced number of spatial streams (NSS), a reduced modulation and coding scheme (MCS) or a reduced physical protocol data unit (PPDU) supported by the AP, which are indicated by exclusion of operation elements, or capabilities elements corresponding to one or more Wi-Fi generations in a frame transmitted by the AP.12.The AP of Claim 9, wherein the processor is further configured to communicate with the first STA based on the reduced capabilities that were indicated to the first STA before enabling the DPS mode.13.The AP of Claim 9, wherein the processor is further configured to:receive, via the transceiver from a second STA not associated with the AP, a probe request that complies with the reduced capabilities indicated to the first STA; andtransmit, via the transceiver, a probe response to the second STA.14.The AP of Claim 9, wherein the processor is further configured to:disable the DPS mode; andmaintain association with the first STA while transitioning from the low power state to the high power state by providing an indication of enhanced capabilities to the first STA, wherein the indication of enhanced capabilities are based on the parameters of the DPS mode or the type of the first STA.15.One or more non-transitory computer-readable storage media storing one or more computer programs including computer-executable instructions that, when executed by one or more processors of an access point (AP) individually or collectively, cause the location management server to perform operations, the operations comprising:determining whether a transition to a dynamic power save (DPS) mode is desired;determining a compatibility of a first station (STA) associated with the AP for the DPS mode;determining enabling the DPS mode based on the compatibility of the first STA being incompatible with the DPS mode;maintaining association with the first STA while transitioning from a high power state to a low power state by providing an indication of reduced capabilities to the first STA, wherein the indication of reduced capabilities is based on at least one parameter of the DPS mode or a type of the first STA; andenabling the DPS mode.

Images