Techniques for Enhanced Downlink Data Delivery

Abstract

This disclosure provides methods, components, devices, and systems for enhanced downlink (DL) data distribution. Some embodiments relate more specifically to reducing latency and power consumption associated with distributing DL buffered units (BUs) to stations (STAs) in enhanced distribution mode. In some implementations, an access point (AP) may transmit queue information instructions associated with one or more pending DL BUs for an STA. The AP may, according to the queue information, identify a set of operating parameters to be used for transmitting one or more pending DL BUs. Similarly, an STA may, according to the queue information, identify a set of operating parameters to be used for receiving one or more pending DL BUs. The AP may, according to the queue information and the set of operating parameters, transmit one or more pending DL BUs to the STA.

Description

Technical Field

[0001] (Cross - Reference to Related Applications)

[0001] This patent application claims priority to U.S. Patent Application No. 18 / 740,708, entitled "TECHNIQUES FOR ENHANCED DOWNLINK DATA DELIVERY" by Asterjadhi et al., filed on June 12, 2024, and U.S. Provisional Patent Application No. 63 / 508,487, entitled "TECHNIQUES FOR ENHANCED DOWNLINK DATA DELIVERY" by Asterjadhi et al., filed on June 15, 2023, each of which is assigned to the assignee of this application and is hereby expressly incorporated herein by reference.

[0002]

[0002] The present disclosure relates to wireless communication, and more particularly, to techniques for enhanced downlink (DL) data delivery.

[0003] Description of Related Technologies

[0003] A wireless local area network (WLAN) can be formed by one or more wireless access points (APs) that provide a shared wireless communication medium for use by multiple client devices, also known as wireless stations (STAs). The basic building block of a WLAN conforming to the Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards is a Basic Service Set (BSS) managed by an AP. Each BSS is identified by a Basic Service Set Identifier (BSSID) advertised by the AP. The AP periodically broadcasts beacon frames so that any STA within the AP's wireless range can establish or maintain a communication link with the WLAN.

[0004]

[0004] In some WLANs, the STA may periodically switch to an enhanced distribution mode (e.g., from active mode to power saving (PS) mode) to conserve power. However, distributing downlink (DL) data to an STA in PS mode can sometimes result in delay, signaling overhead, and unrelated power consumption. [Overview of the project]

[0005]

[0005] Each of the systems, methods, and devices disclosed herein has several innovative aspects, and no single aspect thereof alone realizes any of the desirable attributes disclosed herein.

[0006]

[0006] In some embodiments, the method may include: transmitting instructions for queue information associated with one or more pending downlink (DL) buffered units (BUs) for a station (STA) in enhanced distribution mode; identifying a plurality of operational parameters to be used for transmitting one or more pending DL BUs according to the queue information associated with one or more pending DL BUs; and transmitting one or more pending DL BUs to the STA according to the queue information and the plurality of operational parameters.

[0007]

[0007] In some embodiments, the device for wireless communication at an access point (AP) may include a processing system comprising a processor circuit configuration and a memory circuit configuration for storing code. The processing system may be configured to cause the device to transmit instructions for queue information associated with one or more pending DL BUs for an STA in enhanced delivery mode, to identify a plurality of operational parameters to be used for transmitting one or more pending DL BUs according to the queue information associated with one or more pending DL BUs, and to transmit one or more pending DL BUs to the STA according to the queue information and the plurality of operational parameters.

[0008]

[0008] Some embodiments described herein may further include an operation, feature, means, or command for sending a request to the STA to use a second set of operating parameters for receiving one or more pending DL BUs, one or more pending DL BUs which may be sent in accordance with the request.

[0009]

[0009] In some embodiments, the method may include receiving instructions for queue information associated with one or more pending DL BUs for the STA while the STA is in an enhanced delivery mode; identifying a plurality of operational parameters to be used for receiving one or more pending DL BUs according to the queue information associated with one or more pending DL BUs; and receiving one or more pending DL BUs from the AP according to the queue information and the plurality of operational parameters.

[0010]

[0010] In some embodiments, the device for wireless communication in the STA may include a processing system which includes a processor circuit configuration and a memory circuit configuration for storing code. The processing system may be configured to cause the device to receive instructions for queue information associated with one or more pending DL BUs for the STA while the STA is in an enhanced delivery mode, to identify a plurality of operational parameters to be used for receiving one or more pending DL BUs according to the queue information associated with one or more pending DL BUs, and to receive one or more pending DL BUs from the AP according to the queue information and the plurality of operational parameters.

[0011]

[0011] Some embodiments described herein may further include operations, features, means, or instructions for transmitting instructions for a second set of operating parameters intended for use by the STA for receiving one or more pending DL BUs, one or more pending DL BUs which may be received in accordance with such instructions. [Brief explanation of the drawing]

[0012] [Figure 1]

[0012] An exemplary diagram of a wireless local area network (WLAN) supporting techniques for enhanced downlink (DL) data delivery is shown. [Figure 2]

[0013] This document illustrates an exemplary protocol data unit (PDU) that can be used for communication between a wireless access point (AP) and one or more wireless stations (STAs), supporting techniques for enhanced DL data distribution. [Figure 3]

[0014] This document illustrates an exemplary physical layer (PHY) protocol data unit (PPDU) that can be used for communication between a wireless AP and one or more wireless STAs, supporting techniques for enhanced DL data delivery. [Figure 4]

[0015] This document illustrates an exemplary PPDU hierarchical format usable for communication between a wireless AP and one or more wireless STAs, supporting techniques for enhanced DL data distribution. [Figure 5]

[0016] This diagram illustrates an exemplary signaling pattern for wireless communication between a wireless AP and a wireless STA in a WLAN, supporting techniques for enhanced DL data distribution. [Figure 6]

[0017] This document illustrates an exemplary process flow between a wireless AP and a wireless STA in a WLAN, supporting techniques for enhanced DL data distribution. [Figure 7]

[0018] This shows a block diagram of an exemplary wireless communication device that supports techniques for enhanced DL data distribution. [Figure 8] This shows a block diagram of an exemplary wireless communication device that supports techniques for enhanced DL data distribution. [Figure 9]

[0019] A flowchart illustrates an exemplary process that can be implemented by wireless communication devices supporting techniques for enhanced DL data delivery. [Figure 10]A flowchart illustrates an exemplary process that can be implemented by wireless communication devices supporting techniques for enhanced DL data delivery.

[0013]

[0020] Similar reference numbers and names in various drawings refer to the same elements. [Modes for carrying out the invention]

[0014]

[0021] The following description focuses on several specific implementations for the purpose of illustrating innovative aspects of the present disclosure. However, it will be readily apparent to those skilled in the art that the teachings herein can be applied in many different ways. Some or all of the implementations described may be implemented in any device, system, or network capable of transmitting and receiving radio frequency (RF) signals in accordance with, among other things, the IEEE 802.11 standard, the IEEE 802.15 standard, the Bluetooth standard as defined by the Bluetooth Special Interest Group (SIG), or one or more of the Long Term Evolution (LTE), 3G, 4G, or 5G (New Radio (NR)) standards issued by the 3rd Generation Partnership Project (3GPP).

[0015]

[0022] The implementations described may be implemented in any device, system, or network capable of transmitting and receiving RF signals according to one or more of the following technologies or techniques: code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), spatial division multiple access (SDMA), rate-splitting multiple access (RSMA), multi-user (MU) shared access (MUSA), single-user (SU) multiple-input multiple-output (MIMO), and MU-MIMO. The described implementations may also be carried out using other wireless communication protocols or RF signals suitable for use in one or more of the following: wireless personal area networks (WPAN), wireless local area networks (WLAN), wireless wide area networks (WWAN), wireless metropolitan area networks (WMAN), or Internet of Things (IoT) networks.

[0016]

[0023] In some WLANs, a wireless station (STA) may periodically or sporadically switch from active mode to power-saving (PS) mode to conserve power. Furthermore, in some examples, PS mode may be referred to as an enhanced distribution mode, which may include active mode (AM). When operating in active mode, the STA is always awake and capable of transmitting and receiving frames at any time. While operating in PS mode, the STA may switch between a dosed state (where the STA is inactive) and an awake state (where the STA is capable of transmitting and receiving frames). When in the awake state, a PS STA can monitor beacon frames from a wireless access point (AP). Beacon frames may contain a traffic indicator map (TIM) information element (IE) that identifies which STA has pending downlink (DL) data. If the AP has pending DL data to deliver to the STA (as indicated by the TIM IE), the STA may send a frame (such as a PS pole frame, QoS null frame, or QoS data frame) to notify the AP that the STA is awake (and therefore available to receive pending DL data from the AP). When the frame is a QoS null frame or QoS data frame requesting an immediate response, the power management bit in the frame control field is set to 1 to indicate that the STA is in PS mode and to 0 to indicate that the STA is transitioning to active mode. Similar power-saving protocols may be used when the AP is in PS mode or when the STA is operating in peer-to-peer (P2P) mode.

[0017]

[0024] However, in some cases, the AP's ability to deliver two or more packets, such as buffered units (BUs) or protocol data units (PDUs), to the STA at a given time may be limited (e.g., due to the power management (PM) mode used by the STA). For example, when the STA is in the PS mode and sending a PS poll, the AP may be restricted to sending only a single DL packet to the STA. When the STA is in the PS mode and sending a QoS null frame or a QoS data frame, the AP may be restricted to sending a limited number (the same number as advertised by the STA during association and supported in reception when in this particular PS mode, i.e., APSD) of DL packets to the STA. Thus, if the AP has multiple DL packets to deliver to the STA, the STA may terminate the PS mode (e.g., enter the active mode), or send additional PS poll frames to request each additional DL packet from the AP. In some implementations, the STA may stay in the awake state until all queued DL packets are delivered, and / or transition from the doze state to the awake state, which can cause delays, power consumption, etc. Further, the AP may buffer all queued DL packets until they are delivered, which can cause buffer overflow and scheduling complexity.

[0018]

[0025] One or more innovative aspects of the subject matter described in this disclosure may be implemented to reduce the latency, power consumption, and airtime utilization associated with delivering DL data to the PS STA. In some implementations, to improve the efficiency of DL data delivery, the AP may provide queue information to the STA (such as an STA in active mode or awake state), thereby enabling the AP to deliver pending DL BUs to the STA with greater efficiency, lower signaling overhead, reduced latency, etc. The queue information provided by the AP may, in other implementations, indicate, for example, the number of pending DL BUs for the STA, the duration that the DL BUs have been pending, or the duration until the pending DL BUs are dropped, and a score (determined by the AP or provided by a higher layer (e.g., the application layer)) that determines the priority of delivery of these pending DL BUs.

[0019]

[0026] Additionally, or alternatively, an AP may configure or instruct an STA to use a specific set of operational parameters for receiving pending DL BUs. For example, an AP may instruct an STA to increase its receive (RX) bandwidth (BW) and / or number of spatial streams (NSS) during the next service period (SP), thereby enabling the AP to deliver larger amounts of DL data to the STA in a shorter amount of time. An AP may provide queue information and / or operational parameters via beacon frames, trigger frames, individually addressed frames, group-addressed frames, or separate broadcast frames. In some implementations, an AP may also provide an STA with link-specific information, such as how long it will take to deliver all pending DL BUs on a given communication link to the STA (such as an STA belonging to a multi-link capable device (MLD)). The AP may also provide the STA with a list of links to which the AP intends to deliver pending DL BUs, and ultimately specify that queue information and / or operational parameters are applicable to all or each of the communication links set up with the MLD to which the STA belongs (e.g., each link has its own queue information and / or operational parameters). Link-specific information may enable the STA to retrieve pending DL BUs from the AP with greater efficiency, reduced latency, etc.

[0020]

[0027] Certain aspects of the subject matter described in this disclosure may be implemented to realize one or more of the following potential advantages. In some implementations, by providing the STA with queue information (such as the number of DL BUs pending for the STA, the total size of the pending DL BUs, or the queue size in octets), the techniques described can enable and / or facilitate the STA to retrieve the pending DL BUs with higher efficiency, reduced latency, and reduced power consumption. For example, instead of the AP sending a PS poll frame and receiving as a response one medium access control (MAC) protocol data unit (MAC PDU, MPDU) (e.g., a single pending DL BU) and repeating this process until all pending DL BUs are delivered, the STA may switch from the PS mode to the active mode in order to receive a larger number of DL BUs from the AP in a shorter time span and / or use a specific RX configuration (such as maximum RX BW or NSS), and then the STA can return to the PS mode and continue to conserve power.

[0021]

[0028] Further, some wireless communication systems may support using trigger frames to request (e.g., trigger) UL packets from the STA, but such techniques may be limited to UL communication (e.g., the AP uses a trigger frame to notify the STA which resources are available for UL packets / data). The enhanced DL delivery techniques described herein provide to the STA notice of the next (e.g., pending) DL packet / data so that the STA can be prepared to receive the pending DL packets / data with higher efficiency, higher throughput, reduced latency, etc.

[0022]

[0029] The DL delivery enhancements described herein are applicable to a variety of wireless communication protocol standards, including (but not limited to) IEEE 802.11bn, which supports ultra-high reliability (UHR) communication. The techniques described herein can reduce the latency and power consumption associated with DL reception for UHR STAs (such as STAs that support UHR communication). Furthermore, providing APs and / or STAs with the opportunity to specify the duration and, in some implementations, the maximum number of spatial streams (NSS) along with other transmit (TX) / receive (RX) parameters available for DL ​​delivery can promote coexistence and improved resource management of UHR devices.

[0023]

[0030] Figure 1 shows an illustrative diagram of WLAN100. In some embodiments, WLAN100 may be an example of a Wi-Fi network. For example, WLAN100 may be a network implementing at least one of the IEEE 802.11 family of wireless communication protocol standards (such as those specified in the IEEE 802.11-2020 family specifications or their supplemental revisions, including but not limited to 802.11ay, 802.11ax, 802.11az, 802.11ba, 802.11bd, 802.11be, 802.11bf, and the 802.11 supplemental revisions associated with Wi-Fi 8). WLAN100 may include numerous wireless communication devices, such as a wireless AP102 and multiple wireless STA104s. Although only one AP102 is shown in Figure 1, WLAN100 may also include multiple AP102s. The AP102 shown in Figure 1 can represent a wide variety of AP types, including, but not limited to, enterprise-level APs, single-frequency APs, dual-band APs, standalone APs, software-enabled APs (soft APs), and multi-link APs. The coverage area and capacity of cellular networks (such as LTE and 5G NR) can be further improved by small cells supported by AP102, which act as miniature base stations. Furthermore, private cellular networks can also be built through wireless area networks using small cells.

[0024]

[0031] Each of the STA104 may also be referred to as a mobile station (MS), mobile device, mobile handset, wireless handset, access terminal (AT), user equipment (UE), subscriber station (SS), or subscriber unit in other implementations. The STA104 may represent a variety of devices in other implementations, such as mobile phones, personal digital assistants (PDAs), other handheld devices, netbooks, notebook computers, tablet computers, laptops, Chromebooks, extended reality (XR) headsets, wearable devices, display devices (e.g., TVs (including smart TVs), computer monitors, navigation systems), music or other audio or stereo devices, remote control devices ("remote controls"), printers, kitchen appliances or other electrical appliances (including smart refrigerators), key fobs (e.g., for passive keyless entry and start (PKES) systems), Internet of Things (IoT) devices, and vehicles. Various STA104 units in the network can communicate with each other via AP102.

[0025]

[0032] A set of a single AP102 and its associated STA104 may be referred to as a basic service set (BSS) managed by the individual AP102. Figure 1 additionally shows an exemplary coverage area 108 of AP102, which may represent the basic service area (BSA) of WLAN100. The BSS may be identified or indicated to users by a service set identifier (SSID) and to other devices by a BSS identifier (BSSID), which may be the MAC address of AP102. AP102 may periodically broadcast beacon frames ("beacons") containing the BSSID so that any STA104 within AP102's wireless range can "associate" or reassociate with AP102 in order to establish a separate communication link 106 (hereinafter also referred to as a "Wi-Fi link") with AP102 or to maintain a communication link 106 with AP102.

[0026]

[0033] For example, a beacon may include identification information or instructions for the primary channel used by an individual AP102, as well as timing synchronization functionality to establish or maintain timing synchronization with the AP102. Additionally or alternatively, a beacon may indicate the presence of a pending DL BU for a particular STA104. For example, the TIM IE in a beacon may contain multiple bits corresponding to multiple STA104s served by the AP102. If a particular bit is set to 1, the corresponding STA104 can infer from the beacon that the AP has a pending DL BU buffered for the STA104.

[0027]

[0034] AP102 can provide access to the external network to various STA104 in the WLAN via their respective communication links 106. To establish a communication link 106 with AP102, each STA104 is configured to perform passive scanning or active scanning ("scan") on a frequency channel within one or more frequency bands (e.g., 2.4 gigahertz (GHz), 5GHz, 6GHz, or 60GHz bands). To perform passive scanning, STA104 listens for beacons, which are transmitted by each AP102 at periodic time intervals (measured in time units (TUs), where one TU may be equal to 1024 microseconds (μs)) referred to as the target beacon transmission time (TBTT). To perform active scanning, STA104 generates probe requests, transmits them sequentially on each channel to be scanned, and listens for probe responses from AP102. Each STA104 may identify, determine, confirm, or select an AP102 to associate with according to the scanning information obtained through passive or active scanning, and may perform authentication and association operations to establish a communication link 106 with the selected AP102. While operating in PS mode or active mode, STA may use passive scanning techniques, active scanning techniques, or both. In the final stage of the association operation, AP102 assigns an association identifier (AID) to STA104, which AP102 uses to track STA104.

[0028]

[0035] AP102 and STA104 can communicate (via their respective communication links 106) in accordance with one or more of the IEEE 802.11 family of wireless communication protocol standards. These standards define WLAN radio protocols and baseband protocols for the PHY and MAC layers. AP102 and STA104 transmit and receive wireless communications (hereinafter also referred to as "Wi-Fi communications" or "wireless packets") to and from each other in the form of PPDUs. AP102 and STA104 within WLAN 100 can transmit PPDUs over unlicensed spectrum, which may be a portion of the spectrum including frequency bands conventionally used by Wi-Fi technology, such as the 2.4 GHz band, 5 GHz band, 60 GHz band, 3.6 GHz band, and 900 megahertz (MHz) band. Some implementations of AP102 and STA104 described herein may also communicate in other frequency bands, such as the 5.9 GHz and 6 GHz bands, which may support both licensed and unlicensed communications. AP102 and STA104 can also communicate over other frequency bands, such as shared-license frequency bands, where multiple operators may have licenses to operate within one or more frequency bands that are the same or overlapping.

[0029]

[0036] Each frequency band may contain multiple subbands or frequency channels. For example, PPDUs compliant with the supplemental revisions of the IEEE 802.11n, 802.11ac, 802.11ax, 802.11be, and 802.11bn standards may be transmitted over the 2.4GHz, 5GHz, 6GHz, or 60GHz bands, each divided into multiple 20MHz channels. Therefore, these PPDUs are transmitted over physical channels with a minimum bandwidth of 20MHz, but larger channels can also be formed through channel bonding. For example, a PPDU may be transmitted over physical channels with bandwidths of 40MHz, 80MHz, 160MHz, 320MHz, 480MHz, 640MHz, or 1280MHz by bonding multiple 20MHz channels together.

[0030]

[0037] Each PPDU is a composite structure containing a PHY preamble and payload in the form of a PHY service data unit (PSDU). The information provided within the preamble can be used by the receiving device to decode subsequent data within the PSDU. In instances where a PPDU is transmitted over bonded channels, the preamble fields are duplicated and may be transmitted in each of multiple component channels. A PHY preamble may contain both a legacy portion (or "legacy preamble") and a non-legacy portion (or "non-legacy preamble"). The legacy preamble may be used for packet detection, automatic gain control, and channel estimation, among other applications. The legacy preamble may also be used to maintain compatibility with legacy devices. The format, encoding, and information provided within the non-legacy portion of the preamble are associated with specific IEEE 802.11 protocols that should be used to transmit the payload.

[0031]

[0038] As described herein, AP102 may transmit instructions for queue information associated with one or more pending DL BUs for STA104 in an enhanced delivery mode. The enhanced delivery mode may include PS mode or AM mode. AP102 may identify a first set of operational parameters to be used for the transmission of one or more pending DL BUs, according to the queue information associated with one or more pending DL BUs. The first set of operational parameters may include one or more of the following to be used for the transmission of one or more pending DL BUs: BW, NSS, MCS, PPDU type, preamble puncture pattern, etc. In some examples, the first set of operational parameters may vary according to the queue information provided. For example, AP102 may identify a higher MCS if there are many pending DL BUs for STA104. Conversely, AP102 may identify a lower MCS if there are fewer pending DL BUs for STA104.

[0032]

[0039] Similarly, STA104 may identify a second set of operational parameters to be used for receiving one or more pending DL BUs, according to queue information associated with one or more pending DL BUs. The second set of operational parameters may include one or more of BW, NSS, or MCS to be used for receiving one or more pending DL BUs. AP102 may transmit one or more pending DL BUs to STA104 according to the queue information and the first set or second set of operational parameters, or a common set of operational parameters obtained from the first and second sets. In some implementations, the first set of operational parameters may be the maximum value advertised by AP102. When pending DL BUs are delivered, STA104 may select a second set of operational parameters within the range of the first set of operational parameters advertised by AP102. For example, if the first set of operating parameters signaled by AP102 includes a maximum NSS value of 4, the second set of operating parameters selected by STA104 may include NSS values ​​within the range of the maximum NSS value advertised by AP102 (e.g., less than or equal to it). Thus, STA104 may use the selected NSS value (e.g., 3) for receiving the pending DL BU. In some implementations, STA104 may send instructions for the second set of operating parameters to AP102 before delivering the pending DL BU (thus AP102 is aware of which operating parameters STA intends to use).

[0033]

[0040] Figure 2 shows an exemplary PDU 200 that can be used for wireless communication between a wireless AP 102 and one or more wireless STAs 104. For example, the PDU 200 may be configured as a PPDU. As shown in the figure, the PDU 200 includes a PHY preamble 202 and a PHY payload 204. For example, the preamble 202 may include a legacy portion that itself contains a legacy short training field (L-STF) 206, which may consist of two symbols, a legacy long training field (L-LTF) 208, which may consist of two symbols, and a legacy signal field (L-SIG) 210, which may consist of two symbols. The legacy portion of the preamble 202 may be configured according to the IEEE 802.11a wireless communication protocol standard. The preamble 202 may also include a non-legacy portion, for example, one or more non-legacy fields 212 that conform to one or more of the IEEE 802.11 family of wireless communication protocol standards.

[0034]

[0041] L-STF206 generally enables the receiving device to perform coarse timing and frequency tracking and automatic gain control (AGC). L-LTF208 generally enables the receiving device to perform precise timing and frequency tracking and initial estimation of the wireless channel. L-SIG210 generally enables the receiving device to determine (e.g., acquire, select, identify, detect, verify, calculate, or compute) the duration of a PDU and use the determined duration to avoid overlapping transmissions with the PDU. The legacy portion of the preamble, including L-STF206, L-LTF208, and L-SIG210, may be modulated according to binary phase shift keying (BPSK) modulation. Payload 204 may be modulated according to BPSK modulation, quadrature BPSK (Q-BPSK) modulation, quadrature amplitude modulation (QAM) modulation, or another suitable modulation scheme. The payload 204 may include a PSDU containing a data field (DATA) 214, which may carry higher-layer data, for example, in the form of an MPDU or an aggregated MPDU (A-MPDU).

[0035]

[0042] As described above, AP102 may transmit instructions for queue information associated with one or more pending DL BUs for STA104 in enhanced distribution mode. In some implementations, queue information may be carried in the MAC header of PDU200. In particular, queue information may be transmitted via one or more IEs (such as buffer status report (BSR) IEs) in DATA214 (such as beacon frames or broadcast frames) of PDU200. A BSR IE can indicate a list of BSRs, each BSR corresponding to a given STA104 (not necessarily limited to STA104 in PS mode), and STA104 is identified by an AID subfield in the BSR IE, or another element such as an AID bitmap element. A BSR corresponding to a given STA104 may indicate all pending DL BUs (independent of TID) for each TID or for each AC. AP102 may send one or more pending DL BUs (which may be implementations of PDU200) to STA104 according to the queue information.

[0036]

[0043] Figure 3 shows another exemplary PPDU 300 that can be used for wireless communication between a wireless AP 102 and one or more wireless STA 104s. The PPDU 300 can be used for SU transmission, OFDMA transmission, or MU-MIMO transmission. The PPDU 300 may be formatted as an EHT WLAN PPDU in accordance with the IEEE 802.11be Supplemental Revision for the IEEE 802.11 family of wireless communication protocol standards, or as a PPDU compliant with any subsequent version (post-EHT) of a new wireless communication protocol compliant with a future IEEE 802.11 wireless communication protocol standard (such as the 802.11 Supplemental Revision associated with Wi-Fi 8), or another wireless communication standard. The PPDU 300 includes a PHY preamble, which includes a legacy portion 352 and a non-legacy portion 354. The PPDU 300 may further include a PHY payload 356 after the preamble, for example in the form of a PSDU, which includes a data field 374.

[0037]

[0044] The legacy portion 352 of the preamble includes L-STF358, L-LTF360, and L-SIG362. The non-legacy portion 354 of the preamble includes a repetition of L-SIG, RL-SIG364, and several wireless communication protocol version-dependent signal fields following RL-SIG364. For example, the non-legacy portion 354 may include a universal signal field (referred to herein as "U-SIG366") and an ultra-high reliability (UHR) signal field (referred to herein as "UHR-SIG368"). The presence of RL-SIG364 and U-SIG366 may indicate to STA104 compliant with UHR or a later version that PPDU300 is an EHT PPDU, or a PPDU compliant with any subsequent version (post-EHT) of a new wireless communication protocol compliant with a future IEEE 802.11 wireless communication protocol standard.

[0038]

[0045] UHR is an IEEE 802.11 wireless communication protocol standard that supports higher communication reliability through the use of distributed multi-link operation (MLO), integrated millimeter wave (mmW) operation, and AP coordination, among other implementation forms. In some implementation forms, a UHR AP102 (such as an AP102 that supports UHR communication) may provide queue information relating to the amount of pending DL BUs buffered for a specific UHR STA104 (such as an STA104 that supports UHR communication). Providing queue information to a UHR STA104 (such as an STA504 shown and described with reference to Figure 5) may enable the UHR AP102 (such as an AP502 shown and described with reference to Figure 5) to deliver DL BUs to the UHR STA104 with reduced latency, lower signaling overhead, and improved network resource utilization.

[0039]

[0046] U-SIG366 and UHR-SIG368, or both, may be configured as other wireless communication protocol versions associated with supplementary revisions to the IEEE standards family from UHR onward, and may carry version-dependent information about them. For example, U-SIG366 may be used by a receiving device to interpret bits in one or more of UHR-SIG368 or data field 374. In instances involving the use of bonded channels, such as L-STF358, L-LTF360, and L-SIG362, the information in U-SIG366 and UHR-SIG368 may be duplicated and transmitted over each of the 20 MHz component channels.

[0040]

[0047] The non-legacy portion 354 further includes an additional STF370 (referred to herein as “UHR-STF370”, which is configured as other wireless communication protocol versions after UHR and can carry version-dependent information about them), and one or more additional LTFs (referred to herein as “UHR-LTF372”, which are configured as other wireless communication protocol versions after UHR and can carry version-dependent information about them). The UHR-STF370 can be used for timing and frequency tracking and AGC, and the UHR-LTF372 can be used for more refined channel estimation.

[0041]

[0048] AP102 may use UHR-SIG368 to identify one or more STA104s and inform them that AP102 has scheduled UL or DL ​​resources for them. UHR-SIG368 can be decoded by each compatible STA104 served by AP102. UHR-SIG368 can generally be used by a receiving device to interpret bits in data field 374. For example, UHR-SIG368 may include RU allocation information, spatial stream configuration information, and user-specific (e.g., STA-specific) signaling information. Each UHR-SIG368 may include a common field and at least one user-specific field. In the context of OFDMA, the common field may, among other implementations, indicate the RU distribution across multiple STA104s, indicate RU allocation in the frequency domain, indicate which RUs are allocated to MU-MIMO transmissions, which RUs respond to OFDMA transmissions, and indicate the amount of user in the allocation. User-specific fields are assigned to specific STA104s and carry STA-specific scheduling information, such as user-specific modulation and coding scheme (MCS) values ​​and user-specific RU allocation information. Such information enables each STA104 to identify and decode the corresponding RU in its associated data field 374.

[0042]

[0049] Figure 4 shows an exemplary hierarchical format of a PPDU that can be used for communication between a wireless AP 102 and one or more wireless STAs 104. As described, each PPDU 400 includes a PHY preamble 402 and a PSDU 404. Each PSDU 404 may represent (or "carry") one or more MAC PDUs (MPDUs) 416. For example, each PSDU 404 may carry an aggregate MPDU (A-MPDU) 406 that includes an aggregation of multiple aggregate MPDU (A-MPDU) subframes 408. Each A-MPDU subframe 408 may include an MPDU frame 410 that includes a MAC delimiter 412 and a MAC header 414 before the accompanying MPDU 416 which includes the data portion ("payload" or "frame body") of the MPDU frame 410. Each MPDU frame 410 may also include a frame check sequence (FCS) field 418 for error detection (for example, the FCS field may include a cyclic redundancy check (CRC)) and padding bits 420. An MPDU 416 may carry one or more MAC service data units (MSDUs) 426. For example, an MPDU 416 may carry an aggregated MSDU (A-MSDU) 422 containing multiple A-MSDU subframes 424. Each A-MSDU subframe 424 includes a corresponding MSDU 430, preceded by a subframe header 428 and, in some implementations, followed by padding bits 432.

[0043]

[0050] Referring again to the MPDU frame 410, the MAC delimiter 412 may serve as a marker for the start of the associated MPDU 416 and may indicate the length of the associated MPDU 416. The MAC header 414 may include several fields containing information that defines or indicates the characteristics or attributes of the data encapsulated within the frame body. The MAC header 414 may include a duration field indicating the duration from the end of the PPDU to the end of at least the acknowledgment (ACK) or block ACK (BA) of the PPDU that will be transmitted by the receiving wireless communication device.

[0044]

[0051] The use of the duration field helps reserve the wireless medium over the indicated duration, allowing the receiving device to establish its network allocation vector (NAV). The MAC header 414 also includes one or more fields indicating the addresses of the data encapsulated within the frame body. For example, the MAC header 414 may include a combination of source address, transmitter address, receiver address, or destination address. The MAC header 414 may further include a frame control field containing control information. The frame control field may specify the frame type, for example, a data frame, control frame, or management frame.

[0045]

[0052] Some AP102s and STA104s may implement techniques for spatial reuse involving cooperation in a communication scheme. According to such techniques, AP102s may compete for access to the wireless medium to gain control of the medium for a transmit opportunity (TXOP). The winning AP102 (hereinafter also referred to as the "source AP") may select one or more other AP102s (hereinafter also referred to as "destination APs") to share the TXOP's resources. The source and destination AP102s may be located close to each other such that at least some of their wireless coverage areas overlap at least partially. Some implementations may specifically involve cooperative AP TDMA or OFDMA techniques for sharing the TXOP's time or frequency resources. To share these time or frequency resources, the source AP102 may divide the TXOP into multiple time or frequency segments, each containing a time or frequency resource representing a portion of the TXOP. The source AP102 may allocate a time segment or frequency segment to itself or to one or more of the destination AP102s. For example, each destination AP102 may utilize a partial TXOP allocated by the source AP102 for its uplink (UL) or DL ​​communication with its associated STA104.

[0046]

[0053] In some implementations of such TDMA techniques, each of the multiple parts of the TXOP contains a set of time resources that do not overlap with any time resources of any other part of the multiple parts. In such implementations, scheduling information may include instructions for time resources among the multiple time resources of the TXOP that are associated with each part of the TXOP. For example, scheduling information may include instructions for time segments of the TXOP, such as instructions for one or more sets of slots or symbolic periods associated with each part of the TXOP for MU TDMA, etc.

[0047]

[0054] In some other implementations of the OFDMA technique, each of the multiple parts of the TXOP contains a set of frequency resources that do not overlap with any of the other parts of the multiple. In such implementations, scheduling information may include instructions for the frequency resources of the multiple frequency resources of the TXOP associated with each part of the TXOP. For example, scheduling information may include instructions for the BW portion of the wireless channel, such as instructions for one or more subchannels or RUs associated with each part of the TXOP for MU OFDMA.

[0048]

[0055] In this way, the acquisition of the TXOP by the source AP enables communication between one or more additional destination APs 102 and their respective BSSs, subject to appropriate power control and link adaptation. For example, the source AP 102 may limit the transmit power of selected destination APs 102 so that interference from the selected APs 102 does not prevent the STA 104 associated with the TXOP owner from successfully decoding packets transmitted by the source AP 102. Such techniques can be used to reduce latency because other APs 102 do not have to wait for the competition for the TXOP to win so that they can transmit and receive data according to conventional CSMA / CA or enhanced distributed channel access (EDCA) techniques.

[0049]

[0056] In the case of UL MU transmission, AP102 can send a trigger frame to initiate and synchronize UL MU-OFDMA or UL MU-MIMO transmissions from multiple STA104s to AP102. Thus, such a trigger frame can enable multiple STA104s to transmit UL traffic to AP102 simultaneously. The trigger frame can address one or more STA104s via their respective association identifiers (AIDs), and can assign one or more RUs to each AID (and therefore to each STA104) that can be used to transmit UL traffic to AP102. AP102 can also designate one or more random access (RA) RUs that unscheduled STA104s may compete for.

[0050]

[0057] As described above, AP102 may transmit instructions for queue information associated with one or more pending DL BUs destined for STA104 in enhanced delivery mode. In some implementations, the queue information may be carried in the MAC header 414 of an MPDU frame 410, which may be part of the A-MPDU subframe 408 of an A-MPDU frame 406. In some other implementations, the queue information may be carried in an IE or field contained within the frame body of the MPDU frame 410. The A-MPDU frame 406 containing the queue information may be contained within a PSDU 404 (such as a beacon frame or broadcast frame) of a PPDU 400. The queue information provided by AP102 may enable AP102 to deliver DL BUs (such as an MSDU 430 or A-MSDU frame 422) to STA104 with greater efficiency, reduced latency, and lower signaling overhead, among other benefits. Since the operating parameters described herein also apply to STA104 in active mode, the DL delivery enhancements described herein may be applicable to all STA104 (not just STA104 in PS mode). For example, AP102 may request STA104 in active mode to transition from 20MHz 1 SS mode to 160MHz 2 SS mode. In some implementations, AP may instruct STA104 to use a specific channel via off-channel instruction. In some embodiments, the transition from one mode to another may be based on a buffer status threshold that can be communicated to STA104 in advance (e.g., during association, via management frame exchange, etc.).

[0051]

[0058] Figure 5 shows an illustration of a signaling diagram 500. The signaling diagram 500 can implement or be implemented by an embodiment of WLAN 100. For example, the signaling diagram 500 includes AP 502, which may be an example of an embodiment of a wireless AP, such as AP 102 shown and described with reference to Figure 1. The signaling diagram 500 also includes STA 504, which may be an example of an embodiment of a wireless STA, such as one of STA 104, which is shown and described with reference to Figure 1. As shown and described in the example of Figure 5, AP 502 can improve the efficiency of DL data delivery to the UHR STA (such as STA 504) by providing the UHR STA with queue information 506 relating to pending DL BU(s) 512 and / or by indicating / negotiating the use of a set of operational parameters for the delivery of pending DL BU(s).

[0052]

[0059] As described herein, including with reference to Figures 1 to 4, an IEEE 802.11 STA (such as STA504) can operate in active mode or PS mode. While in active mode, STA504 is awake and can transmit and receive frames at any time. STA504 may indicate that it is in active mode by sending a frame to AP502 with the PM bit set to 0.

[0053]

[0060] In PS mode, the STA504 can wake up at a specified time and transmit and receive during that time, subject to certain constraints. For example, due to the PS data delivery constraints and traffic scheduling considerations of the AP502, the STA504 may not be able to receive more than two MPDUs after a PS pole frame has been sent. Additionally, or alternatively, the STA504 may be constrained to receiving a certain number of MPDUs after an automatic power save delivery (APSD) trigger frame has been sent. The STA504 may indicate that it is in PS mode by sending a frame with the PM bit set to 1 to the AP502, and indicate that it is in active mode by sending a frame with the PM bit set to 0.

[0054]

[0061] A PS STA (such as STA504) can be either awake or dosed. In the awake state, STA504 may be able to receive and transmit frames subject to any PS mode constraints. In the dosed state, STA504 may not be able to transmit or receive (to conserve power). AP502 may support DL data delivery to PS STAs in some implementations. PS STAs (such as STA504) may remain in the dosed state for most of the time and periodically wake up to receive beacon frames from AP502. These beacon frames may indicate whether there are pending DL BU(s)512 for STA504. This information may be provided in the TIM IE of the beacon frame.

[0055]

[0062] Upon receiving a beacon frame indicating the presence of a pending DL BU(s) 512 for STA504, STA504 may send a frame (to AP502) indicating that STA504 has entered the awakened state. The specific frame used to transmit this information may depend on which PS mode STA504 is in. For example, a PS pole frame may be used for legacy PS modes (such as TIM mode), and an APSD trigger frame (such as a Quality of Service (QoS) null frame or QoS data frame) may be used for APSD mode(s). APSD, which includes both unscheduled APSD (U-APSD) and scheduled APSD (S-APSD), is a power-saving mechanism that offers higher efficiency compared to legacy PS polling methods. In APSD, the PS pole frame is replaced by a trigger frame (which can be any type of data frame), thereby reducing the need for a PS STA (such as STA504) to send a PS pole frame to request buffered DL data from the AP502. In some implementations, STA504 can autonomously decide to transition to active mode by sending a frame with the PM bit set to 0. The AP502 may schedule DL distribution according to STA504's decision, subject to the following constraints:

[0056]

[0063] AP502 can schedule up to one MPDU when STA504 sends a PS pole frame, and STA504 can send more PS pole frames to retrieve additional MPDUs from AP502. Alternatively, when STA504 sends an APSD trigger frame to AP502, up to X MPDUs can be scheduled within the SP, where X is indicated by the maximum SP length of the QoS information field sent by STA (which can be 2, 4, 6, or all). When STA504 enters active mode, AP502 can deliver any number of MPDUs to STA504, and DL data delivery can continue until STA504 returns to PS mode (for example, by setting the PM bit to 1).

[0057]

[0064] In some DL data distribution schemes, STA504 may autonomously determine when and how to retrieve pending DL BUs (one or more) 512 from AP502. This decision may depend on a single bit in the beacon frame (such as the TIM bit indicating the presence of DL BUs for the STA, identified by the TIM bit). AP502 may keep any pending DL BUs buffered until they are delivered to STA504, which can cause delays in data distribution, buffer overflows in the AP, and unexpected changes to the DL schedule (e.g., due to unexpected frames from the PS STA). In such implementations, a single bit of information provided by the AP indicates whether there are pending DL BUs (one or more) for STA504. This bit can be used by the STA to make several decisions, such as when to wake up and receive a beacon frame from AP502, when to send a UL triggering frame and transition to the awake state, whether to remain in PS mode (which PS mode to use) or switch to active mode, how long to remain in active mode, and which RX parameters (e.g., RX BW and NSS) to use while in the awake state (note that the STA can be awake in both PS mode and active mode). These decisions can directly affect DL data delivery performance, network performance, power consumption, etc.

[0058]

[0065] Aspects of the subject matter described in this disclosure may be implemented to provide enhancements to the DL delivery protocol that reduce DL delivery delay and improve queue management in AP502, while reducing power consumption and airtime utilization for DL ​​data delivery. Some implementations of the subject matter described in this disclosure may involve increasing the amount of information about pending DL BU(s)512 delivered by AP502. For example, AP502 may provide STA504 with queue information506 which may include, or otherwise indicate, BSR, cumulative delay, etc. Aspects of the subject matter described in this disclosure may also reduce the time it takes for STA504 to send UL triggering frames to AP502, thereby enabling STA504 to perform polling immediately after receiving beacon frames (trigger, NAV protection).

[0059]

[0066] Aspects of the subject matter described herein may also be implemented to improve the delivery rate for an STA that would otherwise be in PS mode. For example, AP502 may send a request 508 to STA504 asking it to increase its RX capability so that AP502 can deliver a larger amount of data in a shorter time period. Request 508 may include a request asking STA504 to switch to active mode (if STA is in PS mode), a request asking STA504 to use maximum RX BW and maximum RX NSS over a time period (the time period itself may also be part of the parameter set), and so on. Alternatively, request 508 may cause STA504 to implicitly switch to active mode, maximum RX BW, maximum RX NSS, etc. In some embodiments, STA504 may indicate (in a frame sent to AP502) how long STA504 is able to remain in this mode.

[0060]

[0067] To support enhanced DL delivery reporting in AP502, AP502 may report the amount of buffered data for UHR STAs (such as STA504), which may also be reported along with the presence of pending DL BUs (one or more) for PS STAs. For example, AP502 may continue to provide TIM IE (within the beacon frame) indicating whether there are pending DL BUs (one or more) for STA504, and queue information 506 (such as BSR) may be appended to the frame sent by AP502. In some implementations, queue information 506 may be provided by a BSR IE in the beacon frame or a separate broadcast frame. The BSR IE may indicate a BSR for one or more UHR STAs that have pending DL BUs. Queue information 506 may be signaled by traffic identifier (TID), by access category (AC), etc.

[0061]

[0068] In other implementations, queue information 506 may be provided by individually addressed frames (such as QoS null frames or QoS data frames) sent to STA 504. For example, queue information 506 may be reported via the QoS control field or BSR control field in the MAC header. In some other implementations, queue information 506 may be provided via a trigger frame. If queue information 506 is reported via a separate broadcast frame, the broadcast frame may be scheduled immediately after the beacon frame. The broadcast frame may include a list of UHR STAs with pending DL BUs, and the corresponding BSR for each UHR STA.

[0062]

[0069] Additionally, or alternatively, queue information 506 may indicate a communication link (such as communication link 106 shown and described with reference to Figure 1) from which each UHR multilink-enabled device (MLD) can retrieve pending DL data. Queue information 506 may also indicate, for each communication link, how long the DL BU has been pending, how much time remains before the pending data is dropped (e.g., due to buffer overflow or aging), a request to the STA to switch to active mode (or enhanced PS mode), a request to the STA to increase RX operating parameters, the average latency for DL ​​data delivery on a given link (which may be provided per TID or per AC), and the BSS load on each link (which may be signaled per TID or per AC). In some implementations, queue information 506 may be provided via a link recommendation frame or a TIM (broadcast) frame.

[0063]

[0070] Aspects of the subject matter described herein may also be implemented to enhance PS mode operation in STA504. For example, a UHR AP (such as AP502) may schedule for TX a control frame (and possibly a new variation of the trigger frame) addressed to a UHR STA (not just those in PS mode), which includes queue information about the UHR STA and, optionally, a set of operational parameters to be used by each UHR STA to receive pending DL BUs and ultimately transmit those pending data frames (UL BUs). In some implementations, the trigger frame may be addressed to an STA with additional DL delivery reports for each of the STAs. The trigger frame may be a variation of the MU RTS trigger frame. The MU RTS trigger frame, which may include the information described above, requests a response frame (e.g., a transmittable frame) from one or more of the UHR STAs, and the transmission of the CTS frame provides acknowledgment from the UHR STA that, among other things, the set of operational parameters requested will be used to receive pending DL BUs. In another embodiment, the trigger frame may be a variation of a buffer status report poll (BSRP) trigger frame which may include the information described above, requesting buffer status reports (BSRs) from one or more of the STAs, which provide either an acknowledgment from each of the UHR STAs that they will adopt the requested set of operational parameters, or a second set of operational parameters that the UHR STA intends to use for receiving pending DL BUs and / or pending UL BUs. In addition, the UHR STA may also indicate how long it intends to remain in a receive mode using this set of operational parameters.

[0064]

[0071] A trigger frame can be scheduled immediately after a beacon frame (e.g., after SIFS), and the STA504 may respond with a UL triggering frame (such as response 510) that includes, if the STA504 supports multiple MPDU RXs, an indication that the STA504 has transitioned to active mode (e.g., by setting the PM bit to 0) or enhanced PS mode, an indication of the updated RX NSS or RX BW that the STA504 intends to use over the current enhanced service period (SP), an indication of the duration for which the STA504 intends to operate according to the indicated RX parameters, or a combination thereof. This information may be advertised in the operating mode (OM) control field or the EHT OM control field in the MAC header of the UL triggering frame. In some implementations, the STA504 may switch to PS mode or a dose state, or to use the previous / original parameter set, after the duration indicated by the UL triggering frame. If this information is unavailable, the exchange of End of Service Period (EOSP) = 1 and / or More Data (MD) = 0 may be used to determine the end of the current Enhanced Service Period (SP).

[0065]

[0072] In some implementations, the duration field of the beacon frame may be set to a non-zero value, thereby providing the STA504 with a TXOP during which a UL triggering frame can be delivered. If the STA504 does not support trigger functionality, it may use EDCA to compete for the TXOP (and discard the intra-BSS NAV of the beacon frame). As described herein, EDCA is a wireless media access mechanism that provides differentiated access by directing traffic to four access category QoS priority queues. In particular, EDCA prioritizes traffic (such as voice, video, best effort, and background) using priority tags that provide a mechanism for implementing QoS at the MAC level. When competing for the TXOP, frames associated with the highest priority access category (such as voice) have the smallest backoff value and therefore have the highest probability of successfully obtaining the TXOP. AP502 may schedule group-addressed delivery after an STA with a pending DL BU(s) has been served. While the delivery of group-addressed BUs is generally not latency-sensitive, group-addressed BUs may need to be sent immediately after the DTIM beacon. Therefore, if pending DL BUs are latency-sensitive, they may be delayed by group delivery. The protocol described herein ensures that low-latency pending DL BUs are sent before the group-addressed frame.

[0066]

[0073] Figure 6 shows an exemplary process flow 600. Process flow 600 may, or can be, implemented an embodiment of WLAN 100. For example, process flow 600 may include AP602, which may be an example of an embodiment of a wireless AP, such as AP502 shown and described with reference to Figure 5. The process flow also includes STA604, which may be an example of an embodiment of a wireless STA, such as STA504, which may be shown and described with reference to Figure 5. In the following description of process flow 600, operations between AP602 and STA604 may be added, omitted, or performed in a different order (from the exemplary order shown).

[0067]

[0074] In 606, AP602 may transmit instructions for queue information associated with one or more pending DL BUs for STA604 in an enhanced delivery mode. Furthermore, the enhanced delivery mode may include PS mode or AM mode. The queue information may indicate the quantity of one or more pending DL BUs for STA604, the duration for which one or more pending DL BUs have been pending, the duration until one or more pending DL BUs are dropped, a request to STA to switch to active mode or enhanced PS mode to receive one or more pending DL BUs, a request to STA to increase one or more operating parameters to receive one or more pending DL BUs, delivery status information associated with a set of communication links between AP602 and STA604, BSS load information associated with a set of communication links, or a combination thereof.

[0068]

[0075] In some implementations, delivery status information indicates the individual delivery wait time for each communication link in a set of communication links. Either or both of the delivery status information or BSS load information may be signaled per TID or per AC, or otherwise categorized. Queue information may be signaled via individually addressed frames (such as frames addressed to STA604), group-addressed frames (such as frames addressed to one or more STAs that have queue information related to DL BUs that the AP is holding), or broadcast frames. In some implementations, queue information may be provided via the QoS control field or BSR field in the MAC header of trigger frames, beacon frames, broadcast frames, link recommendation frames, individually addressed frames, or TIM frames. In some implementations, a frame(s) containing queue information may be scheduled after a beacon frame from AP602.

[0069]

[0076] In some implementations, one or more frames indicate a list of UHR STAs (including STA604) with pending DL BUs, and the respective BSR for each UHR STA. Additionally or alternatively, queue information may indicate one or more UHR MLDs with pending DL BUs, and the respective communication links through which the UHR MLDs can receive the pending DL BUs. Queue information may also indicate the cumulative delay associated with the delivery of one or more pending DL BUs destined for STA604.

[0070]

[0077] In 608, AP602 may identify a first set of operational parameters (e.g., TX parameters) to be used for transmitting one or more pending DL BUs, according to queue information associated with one or more pending DL BUs. The first set of operational parameters may include, for example, a TX BW, TX NSS, or MCS to be used for transmitting one or more pending DL BUs.

[0071]

[0078] In 610, AP602 may optionally send a request to STA604 asking it to use a second set of parameters for receiving one or more pending DL BUs. The second set of parameters may include, for example, the RX BW, RX NSS, or MCS to be used for receiving one or more pending DL BUs. The request may also indicate a time period for which the second set of parameters should be used. In some implementations, AP602 may send an instruction for a time period during which STA604 is permitted to send UL triggering frames or PS pole frames to AP602. In some implementations, the request may include an instruction to STA604 to switch to an awake state or active mode to receive one or more pending DL BUs from AP602.

[0072]

[0079] In 612, STA604 may identify a second set of parameters to be used for receiving one or more pending DL BUs. The second set of parameters may include, for example, an RX BW, RX NSS, or MCS that STA604 intends to use for receiving one or more pending DL BUs. In some implementations, the second set of parameters selected / identified by STA604 may correspond to a set of RX parameters requested by AP602. In some implementations, STA604 may select the STA604's maximum RX BW or maximum RX NSS for receiving DL BUs.

[0073]

[0080] In 614, STA604 may optionally transmit an instruction for a second set of parameters that the STA intends to use for receiving one or more pending DL BUs. In some implementations, STA604 may transmit at least one UL triggering frame or PS pole frame that triggers the transmission of one or more pending DL BUs from AP602 during a period of time identified by AP602 (such as a period of time indicated by the NAV of the beacon frame). The UL triggering frame or PS pole frame may include an instruction that STA604 has transitioned to active mode or enhanced PS mode, an instruction for a second set of parameters, an instruction for a duration during which the STA intends to remain in active mode or enhanced PS mode, an instruction for a duration during which the STA intends to use the second set of parameters, or a combination thereof.

[0074]

[0081] In 616, AP602 may send one or more pending DL BUs to STA604 according to queue information, and STA604 may use a second set of parameters to receive one or more pending DL BUs from AP602. For example, STA604 may use a specific RX BW, RX NSS, and / or MCS to receive one or more pending DL BUs from AP602. In some implementations, STA604 may return to PS mode (such as Daze state) once all pending DL BUs have been delivered. Additionally or alternatively, AP602 may schedule group-addressed deliveries after or while servicing STA604.

[0075]

[0082] Figure 7 shows a block diagram of an exemplary wireless communication device 700 that supports techniques for enhanced DL data distribution. In some implementations, the wireless communication device 700 may be configured to perform one or more operations of process 900, which are described with reference to Figure 9. The wireless communication device 700 may include one or more chips, SoCs, chipsets, packages, components, or devices that constitute or include a processing system, individually or collectively. The processing system may interface with other components of the wireless communication device 700 and may generally process information (such as inputs or signals) received from such other components and output information (such as outputs or signals) to such other components.

[0076]

[0083] In some embodiments, the exemplary chip may include a processing system, a first interface for outputting or transmitting information, and a second interface for receiving or acquiring information. For example, the first interface may refer to an interface between the chip's processing system and a transmitting component, thereby enabling the wireless communication device 700 to transmit information output from the chip. In such an example, the second interface may refer to an interface between the chip's processing system and a receiving component, thereby enabling the wireless communication device 700 to receive information to be passed to the processing system. In some such implementations, the first interface may also acquire information from a transmitting component, etc., and the second interface may also output information to a receiving component, etc.

[0077]

[0084] The processing system of the wireless communication device 700 includes one or more processors, microprocessors, processing units (such as central processing units, CPUs, graphics processing units, GPUs, or digital signal processors, DSPs), processing blocks, application-specific integrated circuits (ASICs), programmable logic devices (PLDs) (such as field programmable gate arrays, FPGAs), or other discrete gate or transistor logic or circuit configurations (all of which may be collectively referred to as "processors" individually or collectively as "processors" or "processor circuit configurations" in this specification). One or more of these processors may be configured, individually or collectively, to perform various functions or operations as described herein.

[0078]

[0085] The processing system may further include one or more memory devices, memory blocks, memory elements, or other memory circuit configurations in the form of discrete gates or transistor logic or circuit configurations (all of which may be referred to herein collectively as “memory” individually or collectively as “memory” or “memory circuit configuration”), each of which may include tangible storage media such as random-access memory (RAM) or ROM, or combinations thereof. One or more of the memories may be coupled with one or more of the processors and may individually or collectively store processor-executable code that, when executed by one or more of the processors, can configure one or more of the processors to perform various functions or operations described herein.

[0079]

[0086] In addition, or alternatively, in some implementations, one or more processors may be pre-configured to perform various functions or operations described herein without requiring software configuration. The processing system may further include, or be coupled with, one or more modems (such as Wi-Fi (e.g., IEEE compliant) modems or cellular (e.g., 3GPP 4G LTE, 5G, or 6G compliant) modems). In some implementations, one or more processors of the processing system include or implement one or more modems. The processing system may further include, or be coupled with, multiple radios (collectively, “radios”), multiple RF chains, or multiple transceivers, each of which may then be coupled with one or more of multiple antennas. In some implementations, one or more processors of the processing system include or implement one or more radios, RF chains, or transceivers.

[0080]

[0087] In some implementations, the wireless communication device 700 may be configured for use in an AP such as AP102 as described with reference to Figure 1. In some other implementations, the wireless communication device 700 may be an AP including such a processing system, as well as other components including one or more antennas. The wireless communication device 700 may be capable of transmitting and receiving wireless communications, for example, in the form of wireless packets. For example, the wireless communication device 700 may be configured to transmit and receive packets in the form of physical layer PPDU and MPDU compliant with one or more of the IEEE 802.11 family of wireless communication protocol standards.

[0081]

[0088] In some other implementations, the wireless communication device 700 may be configured to transmit and receive signals and communications compliant with one or more 3GPP specifications, including those relating to 5G NR or 6G. In some implementations, the wireless communication device 700 may also include, or be coupled with, one or more application processors, which may be further coupled to one or more other memories. In some implementations, the wireless communication device 700 may further include at least one external network interface coupled with a processing system that enables communication with a core network or backhaul network, which allows the wireless communication device 700 to obtain access to an external network, including the Internet.

[0082]

[0089] The wireless communication device 700 may include a queue information component 725, a TX parameter component 730, a pending DL BU component 735, an RX parameter component 740, a time-duration component 745, and a group addressable distribution component 750. One or more of the queue information component 725, TX parameter component 730, pending DL BU component 735, RX parameter component 740, time-duration component 745, and group addressable distribution component 750 may be at least partially implemented in hardware or firmware. For example, one or more of the queue information component 725, TX parameter component 730, pending DL BU component 735, RX parameter component 740, time-duration component 745, and group addressable distribution component 750 may be at least partially implemented by a processor or modem. In some implementations, one or more of the queue information component 725, TX parameter component 730, pending DL BU component 735, RX parameter component 740, time duration component 745, and group addressable distribution component 750 may be implemented at least partially by the processor and by software in the form of processor-executable code stored in memory.

[0083]

[0090] The wireless communication device 700 may support techniques for wireless communication in the implementations disclosed herein. The queue information component 725 may or may not be capable of transmitting queue information instructions associated with one or more pending DL BUs for the STA in enhanced distribution mode. The TX parameter component 730 may or may not be capable of identifying a set of operational parameters to be used for transmitting one or more pending DL BUs according to the queue information associated with one or more pending DL BUs. The pending DL BU component 735 may or may not be capable of transmitting one or more pending DL BUs to the STA according to the queue information and set of operational parameters.

[0084]

[0091] In some implementations, the RX parameter component 740 may or may be configured to send a request to the STA asking it to use a second set of operating parameters for the reception of one or more pending DL BUs, and one or more pending DL BUs are sent in accordance with that request.

[0085]

[0092] In some implementations, a second set of operating parameters may be signaled via the OM control field or EHT OM control field in the MAC header. In some implementations, the first set of operating parameters, the second set of operating parameters, or both, include one or more of the BW, NSS, or MCS to be used for receiving one or more pending DL BUs. In some implementations, the BW includes the maximum BW of the STA. In some implementations, the NSS includes the maximum NSS supported by the STA.

[0086]

[0093] In some implementations, a request from the AP includes an instruction to the STA to switch to awake mode to receive one or more pending DL BUs from the AP. In some implementations, awake mode is active mode or PS mode in the awake state, and enhanced delivery mode includes power saving mode. In some implementations, the request indicates the duration for which a second set of operating parameters should be used.

[0087]

[0094] In some implementations, the RX parameter component 740 may be capable of receiving, or otherwise configured to receive, instructions for a second set of operating parameters that the STA intends to use for receiving one or more pending DL BUs, and one or more pending DL BUs are transmitted in accordance with such instructions.

[0088]

[0095] In some implementations, the first set of operating parameters, the second set of operating parameters, or both, include BW and NSS that the STA intends to use for DL ​​reception during the current enhanced SP. In some implementations, the second set of operating parameters indicated by the STA is equivalent to the set of operating parameters requested by the AP.

[0089]

[0096] In some implementations, queue information may include the quantity of one or more pending DL BUs for the STA, the duration that one or more pending DL BUs were pending, the duration until one or more pending DL BUs were dropped, requests to the STA to switch to active mode or enhanced PS mode to receive one or more pending DL BUs, requests to the STA to increase one or more operational parameters to receive one or more pending DL BUs, delivery status information associated with a set of communication links, BSS load information associated with a set of communication links, or a combination thereof.

[0090]

[0097] In some implementations, delivery status information indicates a separate delivery wait time for each of the set of communication links. In some implementations, one or more frames containing queue information are scheduled after the beacon frame.

[0091]

[0098] In some implementations, one or more frames display a list of UHR STAs with pending DL BUs, and individual queue information for each UHR STA containing the STA.

[0092]

[0099] In some implementations, delivery status information, BSS load information, or both are signaled or categorized by traffic type, or distinguished by TID or AC.

[0093]

[0100] In some implementations, queue information can be signaled via frames individually addressed to STAs, frames addressed to one or more STAs that have queue information about pending DL BUs held by the AP, or broadcast frames.

[0094]

[0101] In some implementations, queue information may be signaled via the QoS control field or BSR control field in the frame's MAC header. In some implementations, queue information may be signaled via one or more of the following: trigger frames, beacon frames, broadcast frames, link recommendation frames, individually addressed frames, or TIM frames.

[0095]

[0102] In some implementations, the broadcast frame indicates a set of communication links through which the UHR MLD, including the STA, can receive the pending DL BUs, and a UHR MLD with pending DL BUs. In some implementations, the queue information indicates the cumulative delay associated with the delivery of one or more pending DL BUs to the STA.

[0096]

[0103] In some implementations, the time period component 745 may, or may not, transmit an instruction for a time period during which the STA is permitted to transmit a UL triggering frame or a PS pole frame to the AP. In some implementations, the time period component 745 may, or may not, receive during the time period at least one UL triggering frame or PS pole frame that triggers the transmission of one or more pending DL BUs from the AP.

[0097]

[0104] In some implementations, the time duration can be signaled via the NAV within the beacon frame. In some implementations, the NAV can be indicated in the duration / ID field of the beacon frame or in the IE included within the beacon frame.

[0098]

[0105] In some implementations, the first part of the queue information may be signaled via a first IE indicating whether the AP has pending DL BUs for the STA. In some implementations, the second part of the queue information may be signaled via a second IE or field indicating the amount of one or more pending DL BUs for the STA.

[0099]

[0106] In some implementations, the second IE or field may be included within the beacon frame or broadcast frame. In some implementations, the queue information includes each BSR for a set of UHR STAs, including STAs, that have pending DL BUs. In some implementations, each BSR may be signaled per TID or per AC.

[0100]

[0107] In some implementations, to support the transmission of queue information, the queue information component 725 may or may not be configured to send a beacon frame that schedules the transmission of one or more trigger frames to a set of UHR STAs, including the STA. In some implementations, to support the transmission of queue information, the queue information component 725 may or may not be configured to receive UL triggering frames from the STA according to the beacon frame.

[0101]

[0108] In some implementations, a set of UHR STAs includes STAs with pending DL BUs, STAs with pending DL delivery reports, or both. In some implementations, UL MU capability is disabled for STAs, and the UL triggering frame includes an MU request to send a TXOP trigger frame. In some implementations, the beacon frame and the UL trigger frame are separated by at least 1 SIFS.

[0102]

[0109] In some implementations, the UL trigger frame includes an instruction that the STA has transitioned to active mode or enhanced PS mode, an instruction for a second set of operating parameters that the STA intends to use for DL ​​reception, an instruction for the duration that the STA intends to remain in active mode or enhanced PS mode, an instruction for the duration that the STA intends to use the second set of operating parameters, or a combination thereof.

[0103]

[0110] In some implementations, the group-addressed delivery component 750 may, or may not, be configured to, schedule group-addressed deliveries after or while servicing a set of UHR STAs.

[0104]

[0111] Figure 8 shows a block diagram of an exemplary wireless communication device 800 that supports techniques for enhanced DL data distribution. In some implementations, the wireless communication device 800 may be configured to perform one or more operations of process 1000, as described with reference to Figure 10. The wireless communication device 800 may include one or more chips, SoCs, chipsets, packages, components, or devices that constitute the processing system individually or collectively, or that include the processing system. The processing system may interface with other components of the wireless communication device 800 and may generally process information (such as inputs or signals) received from such other components and output information (such as outputs or signals) to such other components.

[0105]

[0112] In some embodiments, the exemplary chip may include a processing system, a first interface for outputting or transmitting information, and a second interface for receiving or acquiring information. For example, the first interface may refer to an interface between the chip's processing system and a transmitting component, thereby enabling the wireless communication device 800 to transmit information output from the chip. In such an example, the second interface may refer to an interface between the chip's processing system and a receiving component, enabling the wireless communication device 800 to receive information passed to the processing system. In some such implementations, the first interface may also acquire information from a transmitting component, etc., and the second interface may also output information to a receiving component, etc.

[0106]

[0113] The processing system of the wireless communication device 800 includes one or more processors, microprocessors, processing units (such as central processing units (CPUs), graphics processing units (GPUs), or digital signal processors (DSPs)), processing blocks, application-specific integrated circuits (ASICs), programmable logic devices (PLDs) (such as field-programmable gate arrays (FPGAs)), or other discrete gate or transistor logic or circuit configurations (all of which may be referred to herein collectively as "processors" individually or collectively as "processors" or "processor circuit configurations"). One or more of these processors may or may be configured to perform, individually or collectively, various functions or operations as described herein.

[0107]

[0114] The processing system may further include one or more memory devices, memory blocks, memory elements, or memory circuit configurations in the form of other discrete gates or transistor logic or circuit configurations (all of which may be referred to herein collectively as “memory” individually or collectively as “memory” or “memory circuit”), each of which may include tangible storage media such as random access memory (RAM) or ROM, or combinations thereof. One or more of the memories may be coupled with one or more of the processors and may individually or collectively store processor executable code that, when executed by one or more of the processors, can configure one or more of the processors to perform various functions or operations described herein.

[0108]

[0115] In addition, or alternatively, in some implementations, one or more processors may be pre-configured to perform various functions or operations described herein without requiring software configuration. The processing system may further include, or be coupled with, one or more modems (such as Wi-Fi (e.g., IEEE compliant) modems or cellular (e.g., 3GPP 4G LTE, 5G, or 6G compliant) modems). In some implementations, one or more processors of the processing system include or implement one or more modems. The processing system may further include, or be coupled with, multiple radios (collectively, “radios”), multiple RF chains, or multiple transceivers, each of which may then be coupled with one or more of multiple antennas. In some implementations, one or more processors of the processing system include or implement one or more radios, RF chains, or transceivers.

[0109]

[0116] In some implementations, the wireless communication device 800 may be configured for use in an STA such as the STA104 described with reference to Figure 1. In some other implementations, the wireless communication device 800 may be an STA including such a processing system and other components including multiple antennas. The wireless communication device 800 is capable of transmitting and receiving wireless communications, for example, in the form of wireless packets. For example, the wireless communication device 800 may be configured to transmit and receive packets in the form of physical layer PPDU and MPDU compliant with one or more of the IEEE 802.11 family of wireless communication protocol standards.

[0110]

[0117] In some other implementations, the wireless communication device 800 may be configured to transmit and receive signals and communications compliant with one or more 3GPP specifications, including those relating to 5G NR or 6G. In some implementations, the wireless communication device 800 may include, or be coupled with, one or more application processors, which may be further coupled with one or more other memories. In some implementations, the wireless communication device 800 may further include a user interface (such as a touchscreen or keypad) and a display which may be integrated with the user interface to form a touchscreen display coupled with the processing system. In some implementations, the wireless communication device 800 may further include one or more sensors coupled with the processing system, such as one or more inertial sensors, accelerometers, temperature sensors, pressure sensors, or altitude sensors.

[0111]

[0118] The wireless communication device 800 may include an instruction receiving component 825, a parameter identification component 830, a DL BU receiving component 835, an UL triggering component 840, a NAV discard component 845, and a power mode transition component 850. One or more of the instruction receiving component 825, the parameter identification component 830, the DL BU receiving component 835, the UL triggering component 840, the NAV discard component 845, and the power mode transition component 850 may be at least partially implemented in hardware or firmware. For example, one or more of the instruction receiving component 825, the parameter identification component 830, the DL BU receiving component 835, the UL triggering component 840, the NAV discard component 845, and the power mode transition component 850 may be at least partially implemented by a processor or modem. In some implementations, one or more of the instruction receiving component 825, parameter identification component 830, DL BU receiving component 835, UL triggering component 840, NAV discard component 845, and power mode transition component 850 may be implemented at least partially by the processor and software in the form of processor executable code stored in memory.

[0112]

[0119] The wireless communication device 800 may support techniques for wireless communication in the implementations disclosed herein. The instruction receiving component 825 may be capable of receiving instructions for queue information associated with one or more pending DL BUs for the STA while the STA is in an enhanced distribution mode, or may be configured to do so. The parameter identification component 830 may be capable of identifying a set of operating parameters to be used for receiving one or more pending DL BUs, according to the queue information associated with one or more pending DL BUs, or may be configured to do so. The DL BU receiving component 835 may be capable of receiving one or more pending DL BUs from the AP, according to the queue information and set of operating parameters, or may be configured to do so.

[0113]

[0120] In some implementations, the parameter identification component 830 may be capable of receiving, or otherwise configured to receive, a request to the STA to use a second set of operational parameters for the reception of one or more pending DL BUs, and one or more pending DL BUs are received in accordance with the request.

[0114]

[0121] In some implementations, the parameter identification component 830 may be capable of transmitting, or otherwise configured to transmit, instructions for a second set of operating parameters that the STA intends to use for receiving one or more pending DL BUs, one or more of which are received in accordance with such instructions.

[0115]

[0122] In some implementations, to support receiving queue information, the instruction receiving component 825 may be capable of receiving a beacon frame that schedules the transmission of a trigger frame, or may be configured to do so. In some implementations, to support receiving queue information, the UL triggering component 840 may be capable of transmitting a UL triggering frame according to the beacon frame, or may be configured to do so. In some implementations, the duration field of the beacon frame may be set to a non-zero value to indicate a TXOP that the STA can deliver a UL triggering frame to.

[0116]

[0123] In some implementations, the UL trigger frame includes an instruction that the STA has transitioned to active mode or enhanced PS mode, an instruction for a second set of operating parameters that the STA intends to use for DL ​​reception, an instruction for the duration that the STA intends to remain in active mode or enhanced PS mode, an instruction for the duration that the STA intends to use the second set of operating parameters, or a combination thereof.

[0117]

[0124] In some implementations, the power mode transition component 850 may, or may not, transition to PS mode or Dose state after a duration indicated by the UL triggering frame. In some implementations, the duration may be signaled via the EOSP field or MD field.

[0118]

[0125] In some implementations, to support receiving queue information, the instruction receiving component 825 may be capable of receiving beacon frames containing intraBSS NAVs, or may otherwise be configured to do so. In some implementations, to support receiving queue information, the NAV discarding component 845 may be capable of discarding intraBSS NAVs from beacon frames according to the triggering capability of the STA, or may otherwise be configured to do so. In some implementations, to support receiving queue information, the UL triggering component 840 may be capable of sending a UL triggering frame to the AP after performing an EDCA conflict procedure, or may otherwise be configured to do so.

[0119]

[0126] Figure 9 shows a flowchart illustrating an exemplary process 900 that can be implemented by a wireless communication device supporting techniques for enhanced DL data delivery. In some implementations, one or more operations of process 900 may be implemented by a wireless AP or its components. For example, one or more operations of process 900 may be implemented by a wireless AP (such as wireless AP 102 shown and described with reference to Figure 1) or by a wireless communication device 700 operating within an AP (as shown and described with reference to Figure 7).

[0120]

[0127] In 905, the wireless AP may transmit queue information instructions associated with one or more pending DL BUs for an STA in enhanced distribution mode. In some implementations, the operation of 905 may be carried out by the queue information component 725, as described with reference to Figure 7.

[0121]

[0128] In 910, the wireless AP may identify a set of operational parameters to be used for transmission of one or more pending DL BUs, according to queue information associated with one or more pending DL BUs. In some implementations, the operation of 910 may be carried out by the TX parameter component 730, as described with reference to Figure 7.

[0122]

[0129] In 915, the wireless AP may transmit one or more pending DL BUs to the STA according to a set of queue information and operating parameters. In some implementations, the operation of 915 may be carried out by the pending DL BU component 735, as described with reference to Figure 7.

[0123]

[0130] Figure 10 shows a flowchart illustrating an exemplary process 1000 that can be implemented by a wireless communication device supporting techniques for enhanced DL data distribution. In some implementations, one or more operations of process 1000 may be implemented by a wireless STA or its components. For example, one or more operations of process 1000 may be implemented by a wireless communication device 800 (as shown and described with reference to Figure 8), either as a wireless STA (such as one of the wireless STAs 104 shown and described with reference to Figure 1) or operating within an STA.

[0124]

[0131] In 1005, the wireless STA may receive instructions for queue information associated with one or more pending DL BUs for the STA while the STA is in enhanced distribution mode. In some implementations, the operation of 1005 may be carried out by an instruction receiving component 825, as described with reference to Figure 8.

[0125]

[0132] In 1010, the wireless STA may identify a set of operational parameters to be used for receiving one or more pending DL BUs, according to queue information associated with one or more pending DL BUs. In some implementations, the operation of 1010 may be carried out by a parameter identification component 830, as described with reference to Figure 8.

[0126]

[0133] In 1015, the wireless STA may receive one or more pending DL BUs from the AP according to a set of queue information and operating parameters. In some implementations, the operation of 1015 may be carried out by the DL BU receiving component 835, as described with reference to Figure 8.

[0127]

[0134] The following provides an overview of the aspects of this disclosure.

[0128]

[0135] Embodiment 1: A method for wireless communication at an AP, comprising: transmitting instructions for queue information associated with one or more pending DL BUs to an STA in an enhanced distribution mode; identifying a plurality of operational parameters to be used for the transmission of one or more pending DL BUs according to the queue information associated with one or more pending DL BUs; and transmitting one or more pending DL BUs to the STA according to the queue information and the plurality of operational parameters.

[0129]

[0136] Embodiment 2: The method of Embodiment 1, further comprising sending a request to the STA to use a second set of operational parameters for receiving one or more pending DL BUs, wherein one or more pending DL BUs are sent in accordance with the request.

[0130]

[0137] Embodiment 3: The method of Embodiment 2, wherein a second set of operating parameters are signaled via an OM control field or an EHT OM control field in the MAC header.

[0131]

[0138] Embodiment 4: The method of Embodiment 2 or 3, wherein a plurality of operating parameters, a second plurality of operating parameters, or both thereof, comprises one or more BWs, NSSs, or MCSs to be used for receiving one or more pending DL BUs.

[0132]

[0139] Embodiment 5: The method of Embodiment 4, wherein BW comprises the maximum BW of STA and NSS comprises the maximum NSS supported by STA.

[0133]

[0140] Embodiment 6: Any method of Embodiments 2 to 5, wherein a request from the AP includes an instruction to the STA to switch to awake mode to receive one or more pending DL BUs from the AP, the awake mode being either active mode or PS mode in an awake state, and the enhanced delivery mode includes a power saving mode.

[0134]

[0141] Embodiment 7: Any method of Embodiments 2 to 6, wherein the request indicates a duration for which a second set of operating parameters should be used.

[0135]

[0142] Embodiment 8: The STA further comprises receiving instructions for a second set of operational parameters intended for use for receiving one or more pending DL BUs, and one or more pending DL BUs being transmitted in accordance with such instructions, in any of Embodiments 1 to 7.

[0136]

[0143] Embodiment 9: The method of Embodiment 8, wherein a second set of operating parameters comprises BW and NSS, which the STA intends to use for DL ​​RX during the current enhanced SP.

[0137]

[0144] Embodiment 10: The method of Embodiment 8 or 9, wherein a second set of operating parameters indicated by STA is equivalent to a set of operating parameters required by AP.

[0138]

[0145] Embodiment 11: Any method of Embodiments 1 to 10, wherein the queue information indicates the quantity of one or more pending DL BUs for the STA, the duration for which one or more pending DL BUs have been pending, the duration for which one or more pending DL BUs are to be dropped, a request to the STA to switch to active mode or enhanced PS mode to receive one or more pending DL BUs, a request to the STA to increase one or more operational parameters to receive one or more pending DL BUs, delivery status information associated with multiple communication links, BSS load information associated with multiple communication links, or a combination thereof.

[0139]

[0146] Embodiment 12: The method of Embodiment 11, wherein the distribution status information indicates an individual distribution waiting time for each of the multiple communication links.

[0140]

[0147] Embodiment 13: The method of Embodiment 12, wherein one or more frames containing queue information are scheduled after the beacon frame.

[0141]

[0148] Embodiment 14: The method of Embodiment 12 or 13, wherein one or more frames show a list of UHR STAs having pending DL BUs, and individual queue information for each of the UHR STAs including the STA.

[0142]

[0149] Embodiment 15: Any method from Embodiments 11 to 14, wherein the distribution status information, BSS load information, or both are signaled or categorized by traffic type, or distinguished by TID or AC.

[0143]

[0150] Embodiment 16: The method according to any of Embodiments 11 to 15, wherein queue information is signaled via frames individually addressed to STAs, frames addressed to one or more STAs having queue information relating to DL BUs pending by the AP, or broadcast frames.

[0144]

[0151] Embodiment 17: Any method from Embodiments 11 to 16, wherein queue information is signaled via the QoS control field or BSR control field of the MAC header of the frame.

[0145]

[0152] Embodiment 18: Any method of Embodiments 1 to 17, wherein queue information is signaled via one or more of the following: trigger frames, beacon frames, broadcast frames, link recommendation frames, individually addressed frames, or TIM frames.

[0146]

[0153] Embodiment 19: The method of Embodiment 18, wherein a broadcast frame indicates a UHR MLD having a pending DL BU, and a UHR MLD including an STA that can receive the pending DL BU through it.

[0147]

[0154] Embodiment 20: Any method of Embodiments 1 to 19, wherein queue information indicates the cumulative delay associated with the delivery of one or more pending DL BUs to the STA.

[0148]

[0155] Embodiment 21: Any method of Embodiments 1 to 20, further comprising: sending an instruction to the AP of a time period during which the STA is permitted to send an UL triggering frame or a PS pole frame; and receiving, during the time period, at least one UL triggering frame or PS pole frame from the AP that triggers the transmission of one or more pending DL BUs.

[0149]

[0156] Embodiment 22: The method of Embodiment 21, wherein a time period is signaled via a NAV within a beacon frame, and the NAV is indicated in the duration / ID field of the beacon frame or in an IE included in the beacon frame.

[0150]

[0157] Embodiment 23: Any method of Embodiments 1 to 22, wherein a first part of the queue information is signaled via a first IE indicating whether the AP has pending DL BUs for the STA, and a second part of the queue information is signaled via a second IE or field indicating the amount of one or more pending DL BUs for the STA.

[0151]

[0158] Embodiment 24: The method of Embodiment 23, wherein the second information element or field is included in the beacon frame or broadcast frame.

[0152]

[0159] Embodiment 25: Any method of Embodiments 1 to 24, wherein the queue information comprises a BSR for each of a plurality of UHR STAs, including an STA, which has a pending DL BU.

[0153]

[0160] Embodiment 26: The method of Embodiment 25, wherein each BSR is signaled for each TID or for each AC.

[0154]

[0161] Embodiment 27: Any method of Embodiments 1 to 26, wherein transmitting queue information includes transmitting a beacon frame to a plurality of UHR STAs, including an STA, which schedules the transmission of one or more trigger frames, and receiving UL triggering frames from the STAs according to the beacon frame.

[0155]

[0162] Embodiment 28: The method of Embodiment 27, wherein multiple UHR STAs include STAs with pending DL BUs, STAs with pending DL distribution reports, or both.

[0156]

[0163] Embodiment 29: The method of Embodiment 27 or 28, wherein the UL MU capability is disabled for STA and the UL trigger ring frame comprises a MU RTS TXOP trigger frame.

[0157]

[0164] Embodiment 30: Any method of Embodiments 27 to 29, wherein the beacon frame and the UL trigger ring frame are separated by at least 1 SIFS.

[0158]

[0165] Embodiment 31: Any method of Embodiments 27 to 30, wherein the UL triggering frame indicates that the STA has transitioned to active mode or enhanced PS mode, an indication of a second set of operating parameters that the STA intends to use for DL ​​reception, an indication of the duration for which the STA intends to remain in active mode or enhanced PS mode, an indication of the duration for which the STA intends to use the second set of operating parameters, or a combination thereof.

[0159]

[0166] Embodiment 32: Any method of Embodiments 27 to 31, further comprising scheduling group-addressed deliveries after or while servicing multiple UHR STAs.

[0160]

[0167] Embodiment 33: A method for wireless communication by an STA, comprising: receiving instructions for queue information associated with one or more pending DL BUs for the STA while the STA is in an enhanced distribution mode; identifying a plurality of operational parameters to be used for receiving one or more pending DL BUs according to the queue information associated with one or more pending DL BUs; and receiving one or more pending DL BUs from an AP according to the queue information and the plurality of operational parameters.

[0161]

[0168] Embodiment 34: The method of Embodiment 33, further comprising receiving a request asking the STA to use a second set of operating parameters for receiving one or more pending DL BUs, wherein one or more pending DL BUs are received in accordance with the request.

[0162]

[0169] Embodiment 35: The method of Embodiment 33 or 34, further comprising the STA transmitting instructions for a second set of operational parameters intended for use for receiving one or more pending DL BUs, the one or more pending DL BUs being received in accordance with such instructions.

[0163]

[0170] Embodiment 36: Any method of Embodiments 33 to 35, wherein receiving queue information includes receiving a beacon frame that schedules the transmission of a trigger frame, and transmitting a UL triggering frame according to the beacon frame.

[0164]

[0171] Embodiment 37: The method of Embodiment 36, wherein the duration / ID field of the beacon frame is set to a non-zero value to indicate a TXOP that the STA can deliver an UL triggering frame to.

[0165]

[0172] Embodiment 38: The method of Embodiment 36 or 37, wherein the UL trigger ring frame indicates that the STA has transitioned to active mode or enhanced PS mode, an indication of a second set of operating parameters that the STA intends to use for DL ​​RX, an indication of the duration for which the STA intends to remain in active mode or enhanced PS mode, an indication of the duration for which the STA intends to use the second set of operating parameters, or a combination thereof.

[0166]

[0173] Embodiment 39: The method of Embodiment 38, further comprising transitioning to PS mode or Dose state after a duration indicated by the UL triggering frame.

[0167]

[0174] Embodiment 40: The method of Embodiment 38 or 39, wherein the duration is signaled via an EOSP field or an MD field.

[0168]

[0175] Embodiment 41: Any method of Embodiments 33 to 40, wherein receiving queue information includes receiving a beacon frame containing an intraBSS NAV, discarding the intraBSS NAV from the beacon frame in accordance with the triggering capability of the STA, and sending a UL triggering frame to the AP after performing an EDCA conflict procedure.

[0169]

[0176] Embodiment 42: An apparatus for wireless communication in an AP, comprising a processing system including a processor circuit configuration and a memory circuit configuration for storing code, wherein the processing system is configured to cause the AP to perform any of the methods in Embodiments 1 to 32.

[0170]

[0177] Embodiment 43: An apparatus for wireless communication in an AP, comprising at least one means for carrying out any of the methods of Embodiments 1 to 32.

[0171]

[0178] Embodiment 44: A non-temporary computer-readable medium that stores instructions executable by at least one processor for carrying out any of the methods of Embodiments 1 to 32.

[0172]

[0179] Embodiment 45: An apparatus for wireless communication in an STA, comprising a processing system including a processor circuit configuration and a memory circuit configuration for storing code, wherein the processing system is configured to cause the STA to perform any of the methods of Embodiments 33 to 41.

[0173]

[0180] Embodiment 46: An apparatus for wireless communication in an STA, comprising at least one means for carrying out any of the methods of Embodiments 33 to 41.

[0174]

[0181] Embodiment 47: A non-temporary computer-readable medium that stores instructions executable by at least one processor for carrying out any of the methods of Embodiments 33 to 41.

[0175]

[0182] As used herein, the terms “determine” or “determining” encompass a wide range of actions, and therefore “determining” may include, among other possibilities, calculating, manipulating, processing, deriving, estimating, investigating, searching (such as by searching within a table, database, or other data structure), inferring, confirming, and / or measuring. “Determining” may also include, among other possibilities, receiving (such as receiving information), accessing (such as accessing data stored in memory), or transmitting (such as sending information). Additionally, “determining” may include resolving, selecting, obtaining, choosing, establishing, and other similar actions.

[0176]

[0183] Where used herein, phrases referring to “at least one of” or “one or more of” a list of items refer to any combination of those items, including a single member. For example, “at least one of a, b, or c” is intended to include a, b, c, ab, ac, bc, and abc. Where used herein, “or” is intended to be interpreted in an inclusive sense unless otherwise explicitly indicated. For example, “a or b” may include a only, b only, or a combination of a and b. Furthermore, where used herein, phrases referring to “one (a)” or “one (an)” element refer to one or more such elements that act individually or collectively to perform the enumerated function (singular or plural). Additionally, “set” refers to one or more items, and “subset” refers to fewer items than the entire set but not empty.

[0177]

[0184] As used herein, “based on” is intended to be interpreted in a comprehensive sense unless otherwise explicitly indicated. For example, “based on” may be used interchangeably with “at least partially based on,” “associated with,” “in relation to,” or “according to,” unless otherwise explicitly indicated. Specifically, unless the phrase refers to “based solely on ‘a’” or a contextual synonym, whatever is “based on ‘a’” or “at least partially based on ‘a’” may be based solely on “a” or on a combination of “a” and one or more other factors, conditions, or pieces of information.

[0178]

[0185] The various illustrative components, logic, logic blocks, modules, circuits, operations, and algorithmic processes described in relation to the examples disclosed herein may be implemented as electronic hardware, firmware, software, or combinations of hardware, firmware, or software, including the structures disclosed herein and their structural equivalents. The compatibility of hardware, firmware, and software is described conceptually in terms of functionality and illustrated in the various illustrative components, blocks, modules, circuits, and processes described above. Whether such functionality is implemented in hardware, firmware, or software depends on the specific application and the design constraints imposed on the overall system.

[0179]

[0186] Various modifications of the examples described herein may be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other examples without departing from the spirit or scope of this disclosure. Accordingly, the claims should not be limited to the examples shown herein, but should be given the broadest scope consistent with this disclosure, the principles disclosed herein, and the novel features.

[0180]

[0187] In addition, various features described herein in the context of separate examples may also be implemented in combination in a single implementation. Conversely, various features described in the context of a single implementation may also be implemented separately or in any preferred partial combination in multiple examples. Therefore, features may be described above as acting in a particular combination, and may even be initially claimed as such, but one or more features from a claimed combination may be removed from that combination in some cases, and the claimed combination may cover partial combinations or variations of partial combinations.

[0181]

[0188] Similarly, while operations are shown in a specific order in the diagrams, this should not be understood as requiring that such operations be performed in a specific or sequential order shown, or that all illustrated operations be performed, in order to achieve the desired result. Furthermore, diagrams may schematically represent one or more exemplary processes in the form of flowcharts or flow charts. However, other operations not illustrated may be incorporated into those schematically illustrated exemplary processes. For example, one or more additional operations may be performed before, after, simultaneously with, or between any of the illustrated operations. In some situations, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the examples above should not be understood as requiring such separation in all examples, and it should be understood that the program components and systems described can generally be integrated together in a single software product or packaged into multiple software products.

Claims

1. A device for wireless communication at an access point (AP), The device comprises a processing system including a processor circuit configuration and a memory circuit configuration for storing code, wherein the processing system is provided to the device. To send instructions for queue information associated with one or more pending downlink buffered units for a station (STA) in enhanced distribution mode, According to the queue information associated with the one or more pending downlink buffered units, a plurality of operational parameters to be used for transmission of the one or more pending downlink buffered units are identified. In accordance with the queue information and the plurality of operation parameters, one or more pending downlink buffered units are sent to the STA. A device configured in such a way.

2. The processing system further includes the device, The system is configured to send a request to the STA to use a second set of operating parameters for receiving one or more of the pending downlink buffered units, and the one or more of the pending downlink buffered units are transmitted in accordance with the request. The apparatus according to claim 1.

3. The apparatus according to claim 2, wherein the second plurality of operating parameters are signaled via an operating mode control field or an ultra-high throughput operating mode control field in a media access control header.

4. The apparatus according to claim 2, wherein the plurality of operating parameters, the second plurality of operating parameters, or both thereof, comprises one or more of the bandwidth, number of spatial streams, or modulation and coding scheme to be used for receiving the one or more pending downlink buffered units.

5. The bandwidth comprises the maximum bandwidth of the STA, The number of spatial streams is such that it is the maximum number of spatial streams supported by the STA. The apparatus according to claim 4.

6. The request from the AP includes an instruction to the STA to switch to awake mode to receive the one or more pending downlink buffered units from the AP, The awakened mode is either the active mode or the power-saving mode in the awakened state, and the enhanced delivery mode includes the power-saving mode. The apparatus according to claim 2.

7. The apparatus according to claim 2, wherein the requirement indicates a duration for which the second set of operating parameters should be used.

8. The processing system further includes the device, The STA is configured to receive instructions for a second set of operating parameters intended for use in receiving the one or more pending downlink buffered units, and the one or more pending downlink buffered units receive instructions transmitted in accordance with the instructions. The apparatus according to claim 1.

9. The apparatus according to claim 8, wherein the second set of operating parameters comprises a bandwidth and a number of spatial streams that the STA intends to use for downlink reception during the current enhanced service period.

10. The apparatus according to claim 8, wherein the second set of operating parameters indicated by the STA is equivalent to the set of operating parameters required by the AP.

11. The apparatus according to claim 1, wherein the queue information indicates the quantity of one or more pending downlink buffered units for the STA, the duration for which the one or more pending downlink buffered units were pending, the duration until the one or more pending downlink buffered units are dropped, a request to the STA to switch to active mode or enhanced power-saving mode for receiving the one or more pending downlink buffered units, a request to the STA to increase one or more operating parameters for receiving the one or more pending downlink buffered units, delivery status information associated with a plurality of communication links, basic service set load information associated with the plurality of communication links, or a combination thereof.

12. The apparatus according to claim 11, wherein the distribution status information indicates an individual distribution waiting time for each of the plurality of communication links.

13. The apparatus according to claim 12, wherein one or more frames containing the queue information are scheduled after the beacon frame.

14. The apparatus according to claim 12, wherein one or more frames indicate a list of ultra-high reliability STAs having pending downlink buffered units, and individual queue information for each of the ultra-high reliability STAs, including the STA.

15. The apparatus according to claim 11, wherein the distribution status information, the basic service set load information, or both are signaled or categorized according to traffic type, or distinguished according to traffic identifier or access category.

16. The apparatus according to claim 11, wherein the queue information is signaled via frames individually addressed to the STA, frames addressed to one or more STAs having queue information relating to downlink buffered units pending by the AP, or broadcast frames.

17. The apparatus according to claim 11, wherein the queue information is signaled via the quality of service control field or buffer status reporting control field of the medium access control header of the frame.

18. The apparatus according to claim 1, wherein the queue information is signaled via one or more of the following: trigger frames, beacon frames, broadcast frames, link recommendation frames, individually addressed frames, or traffic indicator map frames.

19. The apparatus according to claim 18, wherein the broadcast frame indicates a highly reliable multilink-enabled device having a pending downlink buffered unit, and a plurality of communication links through which the highly reliable multilink-enabled device, including the STA, can receive the pending downlink buffered unit.

20. The apparatus according to claim 1, wherein the queue information indicates the cumulative delay associated with the delivery of the one or more pending downlink buffered units to the STA.

21. The processing system further includes the device, The STA causes the AP to send an instruction for a time period during which it is permitted to send an uplink triggering frame or a power-saving polling frame. During the aforementioned time period, the AP receives at least one uplink trigger frame or power-saving polling frame that triggers the transmission of one or more pending downlink buffered units. The apparatus according to claim 1, configured as follows.

22. The aforementioned time period is signaled via the network allocation vector within the beacon frame. The network allocation vector is indicated by the fields of the beacon frame or the information elements contained in the beacon frame. The apparatus according to claim 21.

23. The first portion of the queue information is signaled via a first information element indicating whether the AP has pending downlink buffered units for the STA. The second portion of the queue information is signaled via a second information element or field indicating the amount of the one or more pending downlink buffered units for the STA. The apparatus according to claim 1.

24. The apparatus according to claim 23, wherein the second information element or field is included in a beacon frame or broadcast frame.

25. The apparatus according to claim 1, wherein the queue information comprises buffer status reports for each of a plurality of ultra-high reliability STAs, including the STA, which have pending downlink buffered units.

26. Each of the aforementioned buffer status reports is signaled for each traffic identifier or for each access category. The apparatus according to claim 25.

27. In order to transmit the queue information, the processing system provides the device with A beacon frame that schedules the transmission of one or more trigger frames is sent to multiple ultra-high reliability STAs, including the STA. In accordance with the beacon frame, the uplink triggering frame is received from the STA. The apparatus according to claim 1, configured as follows.

28. A device for wireless communication at a station (STA), The device comprises a processing system including a processor circuit configuration and a memory circuit configuration for storing code, wherein the processing system is provided to the device. While the STA is in enhanced delivery mode, it receives instructions for queue information associated with one or more pending downlink buffered units for the STA. According to the queue information associated with the one or more pending downlink buffered units, a plurality of operational parameters to be used for receiving the one or more pending downlink buffered units are identified. In accordance with the queue information and the plurality of operating parameters, the access point (AP) is made to receive one or more pending downlink buffered units. A device configured in such a way.

29. A method for wireless communication at an access point (AP), Sending instructions for queue information associated with one or more pending downlink buffered units for a station (STA) in enhanced distribution mode, Identifying a number of operational parameters to be used for transmission of the one or more pending downlink buffered units, according to the queue information associated with the one or more pending downlink buffered units; Transmitting one or more pending downlink buffered units to the STA according to the queue information and the plurality of operation parameters, A method that includes [a certain feature].

Images