Protection mechanisms for multi-access point operation

A multi-AP coordination framework with COFDMA, CBF, JT/JR, and CSR schemes addresses network disruptions by optimizing channel access and data sharing, enhancing communication reliability and quality in multi-AP networks.

WO2026241073A1PCT designated stage Publication Date: 2026-11-19OFINNO LLC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/US2026/027236
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-12
Filing Date
2026-05-08
Publication Date
2026-11-19

Smart Images

  • Figure US2026027236_19112026_PF_FP_ABST
    Figure US2026027236_19112026_PF_FP_ABST
Patent Text Reader

Abstract

A first access point (AP) receives, from a second AP, a first frame indicating a duration for a first coordinated sounding sequence for the second AP and a third AP. The first AP sets a network allocation vector (NAV) based on the duration. The first AP receives from the second AP, and during the duration, a second frame comprising an invitation, by the second AP to the first AP, to a second coordinated sounding sequence for the first AP and the second AP. Based on receiving the second frame during the duration, the NAV is reset and a third frame accepting the invitation is transmitted, by the first AP to the second AP and during the duration.
Need to check novelty before this filing date? Find Prior Art

Description

Docket No.: 25-3026PCTTITLE PROTECTION MECHANISMS FOR MULTI-ACCESS POINT OPERATIONCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 804,015, filed May 12, 2025, which is hereby incorporated by reference in its entirety.BRIEF DESCRIPTION OF THE DRAWINGS

[0002] Examples of several of the various embodiments of the present disclosure are described herein with reference to the drawings.

[0003] FIG. 1 illustrates example wireless communication networks in which embodiments of the present disclosure may be implemented.

[0004] FIG. 2 is a block diagram illustrating example implementations of a station (STA) and an access point (AP).

[0005] FIG. 3 illustrates an example multi-AP network.

[0006] FIG. 4 illustrates Enhanced Distributed Channel Access (EDCA) and Coordinated Orthogonal Frequency Division Multiple Access (COFDMA).

[0007] FIG. 5 illustrates an example network that includes a coordinated AP set.

[0008] FIG. 6 illustrates an example multi-AP operation procedure.

[0009] FIG. 7 illustrates an example multi-AP sounding phase.

[0010] FIG. 8 illustrates an example extremely high throughput (EHT) sounding null data PPDU (NDP).

[0011] FIG. 9 illustrates an example null data PPDU (NDP) announcement (NDPA) frame format.

[0012] FIG. 10 illustrates an example control frame which may be used as a trigger frame.

[0013] FIG. 11 illustrates an example EHT compressed beamforming / channel quality indication (CQI) frame.

[0014] FIG. 12 illustrates an example of a trigger based (TB) sounding sequence.

[0015] FIG. 13 illustrates an example block acknowledgment frame which may be used as a response frame.

[0016] FIG. 14 illustrates an example of sequential NDP sounding.

[0017] FIG. 15 illustrates an example of joint NDP sounding.

[0018] FIG. 16 illustrates an example multi-AP downlink data transmission phase.

[0019] FIG. 17 illustrates an example multi-AP uplink data transmission phase.

[0020] FIG. 18 illustrates an example of NDP sounding procedures.

[0021] FIG. 19 illustrates an example of a mechanism for protecting a multi-AP coordination transmission.

[0022] FIG. 20 illustrates an example that highlights a problem that may occur when an AP protects a multi-AP coordination transmission.

[0023] FIG. 21 illustrates an example of a procedure according to an embodiment.

[0024] FIG. 22 illustrates an example of another procedure according to an embodiment.

[0025] FIG. 23 illustrates an example process according to an embodiment.

[0026] FIG. 24 illustrates another example process according to an embodiment.Docket No.: 25-3026PCTDETAILED DESCRIPTION

[0027] In the present disclosure, various embodiments are presented as examples of how the disclosed techniques may be implemented and / or how the disclosed techniques may be practiced in environments and scenarios. It will be apparent to persons skilled in the relevant art that various changes in form and detail can be made therein without departing from the scope. After reading the description, it will be apparent to one skilled in the relevant art how to implement alternative embodiments. The present embodiments may not be limited by any of the described exemplary embodiments. The embodiments of the present disclosure will be described with reference to the accompanying drawings. Limitations, features, and / or elements from the disclosed example embodiments may be combined to create further embodiments within the scope of the disclosure. Any figures which highlight the functionality and advantages, are presented for example purposes only. The disclosed architecture is sufficiently flexible and configurable, such that it may be utilized in ways other than that shown. For example, the actions listed in any flowchart may be re-ordered or only optionally used in some embodiments.

[0028] Embodiments may be configured to operate as needed. The disclosed mechanism may be performed when certain criteria are met, for example, in a station, an access point, a radio environment, a network, a combination of the above, and / or the like. Example criteria may be based, at least in part, on for example, wireless device or network node configurations, traffic load, initial system set up, packet sizes, traffic characteristics, a combination of the above, and / or the like. When the one or more criteria are met, various example embodiments may be applied. Therefore, it may be possible to implement example embodiments that selectively implement disclosed protocols.

[0029] In this disclosure, “a” and "an” and similar phrases are to be interpreted as “at least one” and “one or more.” Similarly, any term that ends with the suffix “(s)” is to be interpreted as “at least one” and “one or more.” In this disclosure, the term “may” is to be interpreted as “may, for example.” In other words, the term “may” is indicative that the phrase following the term “may” is an example of one of a multitude of suitable possibilities that may, or may not, be employed by one or more of the various embodiments. The terms “comprises” and “consists of”, as used herein, enumerate one or more components of the element being described. The term “comprises” is interchangeable with “includes” and does not exclude unenumerated components from being included in the element being described. By contrast, “consists of’ provides a complete enumeration of the one or more components of the element being described. The term “based on”, as used herein, may be interpreted as “based at least in part on” rather than, for example, “based solely on”. The term “and / or” as used herein represents any possible combination of enumerated elements. For example, “A, B, and / or C” may represent A; B; C; A and B; A and C; B and C; or A, B, and C.

[0030] If A and B are sets and every element of A is an element of B, A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, possible subsets of B = {STA1, STA2) are: {STA1 }, {STA2}, and {STA1 , STA2). The phrase “based on” (or equally “based at least on”) is indicative that the phrase following the term “based on” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “in response to” (or equally “in response at least to”) is indicative that the phrase following the phrase “in response to” is an example of one of a multitude of suitable possibilities that may, orDocket No.: 25-3026PCTmay not, be employed to one or more of the various embodiments. The phrase "depending on” (or equally “depending at least to”) is indicative that the phrase following the phrase “depending on” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments. The phrase “employi ng / using” (or equally “employing / using at least”) is indicative that the phrase following the phrase “employing / using” is an example of one of a multitude of suitable possibilities that may, or may not, be employed to one or more of the various embodiments.

[0031] The term configured may relate to the capacity of a device whether the device is in an operational or non-operational state. Configured may refer to specific settings in a device that effect the operational characteristics of the device whether the device is in an operational or non-operational state. In other words, the hardware, software, firmware, registers, memory values, and / or the like may be “configured” within a device, whether the device is in an operational or nonoperational state, to provide the device with specific characteristics. Terms such as “a control message to cause in a device" may mean that a control message has parameters that may be used to configure specific characteristics or may be used to implement certain actions in the device, whether the device is in an operational or non-operational state.

[0032] In this disclosure, parameters (or equally called, fields, or Information elements: lEs) may comprise one or more information objects, and an information object may comprise one or more other objects. For example, if parameter (IE) N comprises parameter (IE) M, and parameter (IE) M comprises parameter (IE) K, and parameter (IE) K comprises parameter (information element) J. Then, for example, N comprises K, and N comprises J. In an example embodiment, when one or more messages / frames comprise a plurality of parameters, it implies that a parameter in the plurality of parameters is in at least one of the one or more messages / frames but does not have to be in each of the one or more messages / frames.

[0033] Many features presented are described as being optional through the use of “may” or the use of parentheses. For the sake of brevity and legibility, the present disclosure does not explicitly recite each and every permutation that may be obtained by choosing from the set of optional features. The present disclosure is to be interpreted as explicitly disclosing all such permutations. For example, a system described as having three optional features may be embodied in seven ways, namely with just one of the three possible features, with any two of the three possible features or with three of the three possible features.

[0034] Many of the elements described in the disclosed embodiments may be implemented as modules. A module is defined here as an element that performs a defined function and has a defined interface to other elements. The modules described in this disclosure may be implemented in hardware, software in combination with hardware, firmware, wetware (eg. hardware with a biological element) or a combination thereof, which may be behavioral ly equivalent. For example, modules may be implemented as a software routine written in a computer language configured to be executed by a hardware machine (such as C, C++, Fortran, Java, Basic, Matlab or the like) or a modeling / simulation program such as Simulink, Stateflow, GNU Octave, or LabVIEWMathScript. It may be possible to implement modules using physical hardware that incorporates discrete or programmable analog, digital and / or quantum hardware. Examples of programmable hardware comprise: computers, microcontrollers, microprocessors, application-specific integrated circuitsDocket No.: 25-3026PCT(ASICs); field programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs). Computers, microcontrollers and microprocessors are programmed using languages such as assembly, C, C++ or the like. FPGAs, ASICs and CPLDs are often programmed using hardware description languages (HDL) such as VHSIC hardware description language (VHDL) or Verilog that configure connections between internal hardware modules with lesser functionality on a programmable device. The mentioned technologies are often used in combination to achieve the result of a functional module.

[0035] FIG. 1 illustrates example wireless communication networks in which embodiments of the present disclosure may be implemented.

[0036] As shown in FIG. 1, the example wireless communication networks may include an Institute of Electrical and Electronic Engineers (IEEE) 802.11 (WLAN) infra-structure network 102. WLAN infra-structure network 102 may include one or more basic service sets (BSSs) 110 and 120 and a distribution system (DS) 130.

[0037] BSS 110-1 and 110-2 each includes a set of an access point (AP or AP STA) and at least one station (STA or non-AP STA). For example, BSS 110-1 includes an AP 104-1 and a STA 106-1, and BSS 110-2 includes an AP 104-2 and STAs 106-2 and 106-3. The AP and the at least one STA in a BSS perform an association procedure to communicate with each other.

[0038] DS 130 maybe configured to connect BSS 110-1 and BSS 110-2. As such, DS 130 may enable an extended service set (ESS) 150. Within ESS 150, APs 104-1 and 104-2 are connected via DS 130and may have the same service set identification (SSID).

[0039] WLAN infra-structure network 102 may be coupled to one or more external networks. For example, as shown in FIG. 1, WLAN infra-structure network 102 may be connected to another network 108 (e.g., 802.X) via a portal 140. Portal 140 may function as a bridge connecting DS 130 of WLAN infra-structure network 102 with the other network 108.

[0040] The example wireless communication networks illustrated in FIG. 1 may further include one or more ad-hoc networks or independent BSSs (IBSSs). An ad-hoc network or IBSS is a network that includes a plurality of STAs that are within communication range of each other. The plurality of STAs are configured so that they may communicate with each other using direct peer-to-peer communication (i.e., not via an AP).

[0041] For example, in FIG. 1, STAs 106-4, 106-5, and 106-6 maybe configured to form a first IBSS 112-1. Similarly, STAs 106-7 and 106-8 may be configured to form a second IBSS 112-2. Since an IBSS does not include an AP, it does not include a centralized management entity. Rather, STAs within an IBSS are managed in a distributed manner. STAs forming an IBSS may be fixed or mobile.

[0042] A STA as a predetermined functional medium may include a medium access control (MAC) layer that complies with an IEEE 802.11 standard. A physical layer interface for a radio medium may be used among the APs and the non-AP stations (STAs). The STA may also be referred to using various other terms, including mobile terminal, wireless device, wireless transmit / receive unit (WTRU), user equipment (UE), mobile station (MS), mobile subscriber unit, or user. For example, the term "user" maybe used to denote a STA participating in uplink Multi-user Multiple Input, Multiple Output (MU MIMO) and / or uplink Orthogonal Frequency Division Multiple Access (OFDMA) transmission.Docket No.: 25-3026PCT

[0043] A physical layer (PHY) protocol data unit (PPDU) may be a composite structure that includes a PHY preamble and a payload in the form of a PLCP service data unit (PSDU). For example, the PSDU may include a PHY Convergence Protocol (PLCP) preamble and header and / or one or more MAC protocol data units (MPDUs). The information provided in the PHY preamble may be used by a receiving device to decode the subsequent data in the PSDU. In instances in which PPDUs are transmitted over a bonded channel (channel formed through channel bonding), the preamble fields may be duplicated and transmitted in each of the multiple component channels. The PHY preamble may include 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 uses. The legacy preamble also may generally be used to maintain compatibility with legacy devices. The format of, coding of, and information provided in the non-legacy portion of the preamble is based on the particular IEEE 802.11 protocol to be used to transmit the payload.

[0044] A frequency band may include one or more sub-bands or frequency channels. For example, PPDUs conforming to the IEEE 802.11n, 802.11ac, 802.11ax and / or 802.11 be standard amendments may be transmitted over the 2.4 GHz, 5 GHz, and / or 6 GHz bands, each of which may be divided into multiple 20 MHz channels. The PPDUs may be transmitted over a physical channel having a minimum bandwidth of 20 MHz. Larger channels may be formed through channel bonding. For example, PPDUs may be transmitted over physical channels having bandwidths of 40 MHz, 80 MHz, 160 MHz, or 520 MHz by bonding together multiple 20 MHz channels.

[0045] FIG. 2 is a block diagram illustrating example implementations of a STA 210 and an AP 260. As shown in FIG.2, STA 210 may include at least one processor 220, a memory 230, and at least one transceiver 240. AP 260 may include at least one processor 270, a memory 280, and at least one transceiver 290. Processor 220 / 270 may be operatively connected to memory 230 / 280 and / or to transceiver 240 / 290.

[0046] Processor 220 / 270 may implement functions of the PHY layer, the MAC layer, and / or the logical link control (LLC) layer of the corresponding device (STA 210 or AP 260). Processor 220 / 270 may include one or more processors and / or one or more controllers. The one or more processors and / or one or more controllers may comprise, for example, a general-purpose processor, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a logic circuit, or a chipset, for example.

[0047] Memory 230 / 280 may include a read-only memory (ROM), a random-access memory (RAM), a flash memory, a memory card, a storage medium, and / or other storage unit. Memory 230 / 280 may comprise one or more non-transi tory computer readable mediums. Memory 230 / 280 may store computer program instructions or code that may be executed by processor 220 / 270 to carry out one or more of the operations / embodiments discussed in the present application. Memory 230 / 280 may be implemented (or positioned) within processor 220 / 270 or external to processor 220 / 270. Memory 230 / 280 may be operatively connected to processor 220 / 270 via various means known in the art.

[0048] Transceiver 240 / 290 may be configured to transmit / receive radio signals. In an embodiment, transceiver 240 / 290 may implement a PHY layer of the corresponding device (STA 210 or AP 260). In an embodiment, STA 210 and / or AP 260 may be a multi-link device (MLD), that is a device capable of operating over multiple links as defined byDocket No.: 25-3026PCTthe IEEE 802.11 standard. As such, STA 210 and / or AP 260 may each implement multiple PHY layers. The multiple PHY layers may be implemented using one or more of transceivers 240 / 290.

[0049] FIG.3 illustrates an example multi-AP network 300. Example multi-AP network 300 may be a multi-AP network in accordance with the Wi-Fi Alliance standard specification for multi-AP networks. As shown in FIG.3, multi-AP network 300 may include a multi-AP controller 302 and a plurality of multi-AP groups (or multi-AP sets) 304, 306, and 308.

[0050] Multi-AP controller 302 may be a logical entity that implements logic for controlling the APs in multi-AP network 300. Multi-AP controller 302 may receive capability information and measurements from the APs and may trigger AP control commands and operations on the APs. Multi-AP controller 302 may also provide onboarding functionality to onboard and provision APs onto multi-AP network 300.

[0051] Multi-AP groups 304, 306, and 308 may each include a plurality of APs. APs in a multi-AP group are in communication range of each other and may coordinate their transmissions and / or transmissions from their associated STAs. Coordinated transmissions may involve all or a subset of the APs in a multi-AP group. A multi-AP group may also be referred to as an AP candidate set as APs in a multi-AP group are considered candidates for a coordinated transmission initiated by an AP. The APs in a multi-AP group are not required to have the same primary channel. As used herein, the primary channel for an AP refers to a default channel that the AP monitors for management frames and / or uses to transmit beacon frames. For a STA associated with an AP, the primary channel refers to the primary channel of the AP, which is advertised through the AP's beacon frames.

[0052] In one approach, a multi-AP group may be established by a coordinator AP in a multi-AP setup phase prior to any multi-AP coordination. APs of the multi-AP group, other than the coordinator AP, may be referred to as the coordinated APs. A coordinator AP may establish one or more multi-AP groups. A coordinated AP may likewise be a member of multiple multi-AP groups. A coordinator AP of a multi-AP group may be a coordinated AP of another multi-AP group, and vice versa. In another approach, a multi-AP group may be established by a network administrator manually by configuring APs as part of the multi-AP group. In yet another approach, a multi-AP group may be established in a distributed manner by APs without a central controller. In this case, an AP may advertise its multi-AP capability in a beacon or other management frame (e.g., public action frame). Other APs that receive the frame with the multi-AP capability information may perform a multi-AP setup with the AP that advertised the multi-AP capability.

[0053] In one approach, one of the APs in a multi-AP group may be designated as a master AP. The designation of the master AP may be done by AP controller 302 or by the APs of the multi-AP group. The master AP of a multi-AP group may be fixed or may change over time between the APs of the multi-AP group. An AP that is not the master AP of the multi-AP group is known as a slave AP.

[0054] In one approach, APs in a multi-AP group may perform coordinated transmissions together. Coordinated transmissions between APs may be performed via a multi-AP coordination (MAPC) framework that includes a set of coordination or transmission schemes (such as coordinated beamforming (CBF, CoBF, or Co-BF), coordinated spatial reuse (CSR, CoSR, orCo-SR), coordinated time division multiple access (CTDMA, Co-TDMA, orCo-TDMA), coordinated restricted target wake time (CRTWT, CoRTWT, or Co-RTWT), joint transmission or reception (JT / JR), coordinatedDocket No.: 25-3026PCTOFDMA (COFDMA), or a combination of two or more of the aforementioned techniques) and procedures for OBSS APs to coordinate their transmissions and improve communications reliability. As part of the MAPC framework, two or more APs may perform coordinated sounding in order to obtain the channel state information (CSI) between the two or more APs and each of their target STAs. Obtaining CSI from a coordinated sounding procedure may be a necessary step prior to performing Co-BF or JT / JR, for example. As part of the MAPC framework, two or more APs may perform a coordinated interference measurement procedure in order to obtain the interference level between the two or more APs and each of their target STAs. Obtaining interference levels from a coordinated interference measurement procedure may be a necessary step prior to performing Co-SR, for example. As used herein, a coordinated transmission, also referred to as a multi-AP transmission or MAPC transmission, is a transmission event in which multiple APs (of a multi-AP group or a multi-AP network) transmit in a coordinated manner over a time period (e.g. Co-BF transmission, Co-SR transmission, JT / JR, and coordinated / Co-B F / JT- JR sounding). Coordinated transmissions may involve simultaneous transmissions by a plurality of APs in a multi-AP group. The time period of simultaneous transmissions may be a continuous period.

[0055] Multi-AP transmissions may be enabled by the AP controller and / or by the master AP of the multi-AP group. In one approach, the AP controller and / or the master AP may control time and / or frequency sharing in a transmission opportunity (TXOP). For example, when one of the APs (e.g., the master AP) in the multi-AP group obtains a TXOP, the AP controller and / or the master AP may control how time / frequency resources of the TXOP are to be shared with other APs of the multi-AP group. In an implementation, the AP of the multi-AP group that obtains a TXOP becomes the master AP of the multi-AP group. The master AP may then share a portion of its obtained TXOP (which may be the entire TXOP) with one or more other APs of the multi-AP group.

[0056] Different multi-AP transmission schemes may be suitable for different use cases in terms of privacy protection, including whether transmitted data may be shared with other BSSs in the multi-AP group. For example, some multi-AP transmission schemes, such as CSR, CDTMA, coordinated frequency division multiple access (CFDMA), COFDMA, and CBF, enable a master AP to coordinate slave APs by sharing control information among APs, without requiring the sharing of user data among APs. The control information may include BSS information of APs, link quality information of channels between each AP and its associated STAs, and information related to resources to be used to achieve multiplexing in power, time, frequency, or special domains for multi-AP transmission. The control information exchanged among a master AP and slave APs may be used for interference avoidance or nulling to avoid or null co-channel interference introduced to neighboring BSSs in a multi-AP network. Interference avoidance or interference nulling requires that data transmissions between an AP and STAs are only within the same BSS. In other words, each AP transmits or receives data frames to or from its associated STAs, while each STA receives or transmits data frames to or from its associating AP.

[0057] By contrast, other multi-AP transmission schemes may enable a master AP to coordinate slave APs by sharing both control information and user data among APs in a multi-AP group. Control information may include BSS information related to APs and link quality information of channels between each AP and its associated STAs. By having user data exchanged over backhaul, the master AP and slave APs may perform data transmissions jointly to achieve spatial diversity, e.g., using distributed Ml MO, for example, joint transmission (JT) for downlink transmissions and joint receptionDocket No.: 25-3026PCT(JR) for uplink transmissions. The data transmissions between APs and STAs may include transmissions within the same BSS and / or across different BSSs. In other words, an AP may transmit or receive data frames to or from its associated STAs as well STAs associated with other APs participating in multi-AP transmission Similarly, a STA may transmit or receive data frames to or from multiple APs.

[0058] Different multi-AP transmission schemes may be suitable for different use cases in terms of signal reception levels at STAs or APs within a multi-AP group. For example, CBF and JT / JR require that each STA involved in a multi-AP transmission be located within a common area of signal coverage of the APs involved in the multi-AP transmission. Generally, CBF may be suitable when a receiving STA suffers from potential interference from other APs in the multi-AP group. By using channel related information such as channel state information (CSI), channel quality indication (CQI), or compressed beamforming (BF) feedback exchanged among APs, an AP may pre-code a signal to be transmitted to form a beam that increases power toward a target STA while reducing the power that interferes with a STA associated with a neighboring AP. Use cases of JT / JR may require a sufficient received signal power at receiving STAs for JT and a sufficient received signal power at receiving APs for JR. By contrast, CSR may perform multi-AP transmission in an interference coordination manner. The received signal power at a STA associated with an AP transmitting data may be required to be much higher than the received interference power.

[0059] Different multi-AP transmission schemes may require different synchronization levels and may operate with or without a backhaul between a master AP and slave APs in a multi-AP group. For example, CSR may require PPDU-level synchronization, whereas CBF may require symbol-level synchronization. On the other hand, JT / JR may require tight time / frequency / phase-level synchronization as well as a backhaul for data sharing between APs in the multi-AP group.

[0060] Different multi-AP transmission schemes may have different complexity levels with regard to coordination between a master AP and slave APs in a multi-AP group. For example, JT / JR may require very high complexity due to both CSI and user data being shared between APs. CBF may require medium complexity due to the sharing of CSI. CFDMA, COFDMA and CTDMA may require medium or relatively low complexity due to the CSI and time / frequency resources to be shared between APs. CSR may require low complexity as the amount of information related to spatial reuse and traffic that needs to be exchanged between APs may be low.

[0061] A multi-AP group may adopt a static multi-AP operation including a static multi-AP transmission scheme. A multi-AP network may also be dynamic due to various reasons. For example, a STA may join or leave the multi-AP network, a STA may switch to a power save mode, or an AP or a STA may change its location. Such changes may lead to changes in the conditions underlying the selection of the multi-AP transmission scheme and may cause certain requirements (e.g., synchronization, backhaul, coordination, etc.) for the multi-AP transmission scheme to be lost. This results in an inferior quality of transmissions in the multi-AP network.

[0062] In COFDMA, the master AP may share a portion of its TXOP with multiple APs by assigning each of the multiple APs a respective frequency resource (e.g., channel / subchannel) of available frequency resources. COFDMA is illustrated in FIG.4 as a multi-AP channel access, compared with Enhanced Distributed Channel Access (EDCA). As shown in FIG.4, in EDCA, channel access by multiple APs (e.g., AP1, AP2) may occur in consecutive time periods (e.g., TXOPs).Docket No.: 25-3026PCTDuring a given channel access, the channel (e.g., 80 MHz) in its entirety may be used by a single AP. In contrast, in COFDMA, access by multiple APs (multi-AP channel access) may take place in a same time period (e.g., same TXOP or same portion of a TXOP) over orthogonal frequency resources. For example, as shown in FIG. 4, an 80 MHz channel may be divided into four non-overlapping 20 MHz channels, each assigned to a respective AP of the multiple APs. The multiple APs may transmit in a coordinated manner, simultaneously in the same time period, to achieve a multi-AP transmission. In the multi-AP transmission, each of the multiple APs may transmit a PPDU to one or more STAs.

[0063] FIG. 5 illustrates an example network 500 that includes a coordinated AP set. As shown in FIG. 5, the coordinated AP set may include two APs - AP 502-1 and AP 502-2. The coordinated AP set may be a subset of an established multi-AP group. At least one STA may be associated with each of APs 502-1 and 502-2. For example, a STA 504-1 may be associated with AP 502-1 , and a STA 504-2 may be associated with AP 502-2.

[0064] APs 502-1 and 502-2 may belong to the same ESS as described above in FIG. 1. In such a case, APs 502-1 and 502-2 may be connected by a DS to support ESS features. In addition, as part of a coordinated AP set, APs 502-1 and 502-2 may be connected by a backhaul. The backhaul is used to share information quickly between APs to support coordinated transmissions. The shared information may be channel state information or data to be sent to associated STAs. The backhaul may be a wired backhaul or a wireless backhaul. A wired backhaul is preferred for high-capacity information transfer without burdening the main radios of the APs. However, a wired backhaul may require a higher deployment cost and may place greater constraints on AP placement. A wireless backhaul is preferred for its lower deployment cost and flexibility regarding AP placement. However, because a wireless backhaul relies on the main radios of the APs to transfer information, the APs cannot transmit or receive any data while the wireless backhaul is being used.

[0065] Typically, one of APs 502-1 and 502-2 may act as a Master AP and the other as a Slave AP. The Master AP is the AP that is the owner of the TXOP. The Master AP shares frequency resources during the TXOP with the Slave AP. When there are more than two APs in the coordinated set, a Master AP may share its TXOP with only a subset of the coordinated AP set. The role of the Master AP may change overtime. For example, the Master AP role maybe assigned to a specific AP for a duration of time. Similarly, the Slave AP role may be chosen by the Master AP dynamically or can be pre-assigned for a duration of time.

[0066] Depending on the capability of APs in a coordinated AP set, the APs may only do certain type of coordinated transmissions. For example, in FIG. 5, if AP 502-1 supports JT and CSR while AP 502-2 supports CSR and CBF, both APs may only perform CSR as a coordinated transmission scheme. An AP may also prefer to perform single AP transmissions for a duration of time if the benefit of coordinated transmission does not outweigh some disadvantages with coordinated transmission such as reduced flexibility and increased computational power required.

[0067] CSR is one type of multi-AP coordination that may be supported by AP 502-1 and AP 502-2 as shown in FIG.5. Spatial reuse using CSR can be more stable than non-AP coordinated spatial reuse schemes such as overlapping basic service set (OBSS) PD-based SR and PSR-based SR. For example, in example network 500, APs 502-1 and 502-2 may perform a joint sounding operation in order to measure path loss (PL) on paths of example network 500. For example, the joint sounding operation may result in the measurement of PL 508 for the path between APs 502-1 andDocket No.: 25-3026PCT502-2, path loss 510 for the path between AP 502-1 and STA 504-2, and path loss 512 for the path between AP 502-2 and STA 504-1. The measured path loss information may then be shared between APs 502-1 and 502-2 (e.g . , using the backhaul) to allow for simultaneous transmissions by APs 502-1 and 502-2 to their associated STAs 504-1 and 504-2 respectively. Specifically, one of APs 502-1 and 502-2 obtains a TXOP to become the Master AP. The Master AP may then send a CSR announcement frame to the other AP(s). In an embodiment, the Master AP may perform a polling operation, before sending the CSR announcement frame, to poll Slave APs regarding packet availability for transmission. If at least one Slave AP responds indicating packet availability, the Master AP may proceed with sending the CSR announcement frame. In the CSR announcement, the Master AP may limit the transmit power of a Slave AP in order to protect its own transmission to its target STA. The Slave AP may similarly protect its own transmission to its target STA by choosing a modulation scheme that enables a high enough Signal to Interference Ratio (SIR) margin to support the interference due to the transmission of the Master AP to its target STA.

[0068] FIG. 6 illustrates an example 600 of a multi-AP operation procedure. In example 600, the multi-AP operation procedure is illustrated with respect to a multi-AP network that includes APs 602 and 604 and STAs 606 and 608. In an example, APs 602 and 604 may form a multi-AP group. AP 602 may be the master AP and AP 604 may be a slave AP of the multi-AP group. For example, AP 602 may obtain a TXOP making it the master AP of the multi-AP group. Alternatively, AP 602 may be designated as the master AP by a multi-AP controller.

[0069] As shown in FIG. 6, the multi-AP operation procedure may include a series of phases in time, each of which may contain a plurality of frame exchanges within the multi-AP network. Specifically, the multi-AP operation procedure may include a multi-AP selection phase 610, a multi-AP data sharing phase 612, a multi-AP sounding phase 614, and a multi-AP data transmission phase 616.

[0070] A multi-AP network may carry out a multi-AP operation based on a specific multi-AP transmission scheme. The multi-AP transmission scheme may be chosen by the master AP based on the capabilities of the slave APs in a multi-AP group. Prior to a multi-AP operation, a slave AP may inform the master AP of capability information related to the slave AP, including the capabilities of supporting one or more multi-AP transmission schemes. The slave AP may also inform the master AP of BSS information of the BSS of the slave AP and of link quality information for STAs associated with the slave AP. The master AP may receive information related to all available slave APs. The information related to slave APs may include capability information, BSS information, and link quality information. Based on the information provided by available slave APs, the master AP may determine during a multi-AP selection phase the slave APs to be designated for a multi-AP transmission and a specific multi-AP transmission scheme to be used during the multi-AP transmission.

[0071] Multi-AP selection phase 610 may include procedures for soliciting, selecting, or designating slave AP(s) for a multi-AP group by a master AP. As seen in FIG.6, the multi-AP selection phase may include transmissions of frame 618 from AP 602 and frame 620 from AP 604. AP 602 may transmit frame 618 to solicit information regarding the buffer status of AP 604. In response, AP 604 may transmit frame 620 to inform AP 602 of its and its associated STAs buffer status and / or whether it intends to join multi-AP operation. Multi-AP selection phase 610 may also be used to exchange information related to multi-AP operation, including BSS information of APs and link quality information between each APDocket No.: 25-3026PCTand its associated STAs, for example. The BSS information of an AP may include a BSS ID of the BSS of the AP, identifiers and / or capabilities of STAs belonging to the BSS, information regarding sounding capabilities of the STAs, information regarding Ml MO capabilities of the AP, etc. Link quality information may include received signal strength indicator (RSSI), signal-to-noise ratio (SNR), signal-to-interference-plus-noise-ratio (SINR), channel state information (CSI), channel quality indicator (CQI).

[0072] Multi-AP data sharing phase 612 may include procedures for sharing data frames to be transmitted by APs to associated STAs among the master AP and selected slave AP(s) via direct connections between APs. Phase 612 may be optional for some multi-AP data transmission schemes. For example, phase 612 may be required for JT / JR as data frames may be exchanged between APs before or after multi-AP data transmission phase 616.

[0073] Multi-AP data sharing phase 612 may be performed using a wired backhaul, an in-channel wireless backhaul, or an off-channel wireless backhaul. In some cases, multi-AP data sharing phase 612 may be performed over an in-channel backhaul, e.g., using the same wireless channel used to transmit / receive data to / from STAs. For example, as shown in FIG. 6, in phase 612, AP 602 may transmit a frame 622, which may be received by AP 604. Frame 622 may include MPDlls that AP 602 wishes to transmit to associated STAs using a multi-AP operation. Similarly, AP 604 may transmit a frame 624, which may be received by AP 602. Frame 624 may include MPDUs that AP 604 wishes to transmit to associated STAs using a multi-AP operation.

[0074] Multi-AP sounding phase 614 may include procedures for multi-AP channel sounding, including channel estimation and feedback of channel estimates among the master AP, candidate slave AP(s), and associated STAs. Phase 614 may be optional for some multi-AP transmission schemes, such as COFDMA, CDTMA, and CSR. For example, phase 614 may be performed by the master AP to aid in resource unit allocation when orchestrating a COFDMA transmission.

[0075] Multi-AP data transmission phase 616 may include exchange of data frames between the master AP, slave AP(s), and their associated STAs based on multi-AP transmission scheme(s) determined by the master AP. Depending on the multi-AP transmission scheme(s) to be used, phase 616 may include optional synchronization between APs of the multi-AP group, before exchange of data frames between APs and STAs within the multi-AP group.

[0076] The order of phases 610, 612, 614 and 616 may be different than shown in FIG.6. For example, in COFDMA, phase 616 may occur immediately after phase 610, whereas, in JT / JR, phase 612 may occur after phase 610. Further, as mentioned above, some phases may be optional and may or may not be present. For example, phase 614 may not be required for COFDMA but may be required for JT / JR.

[0077] FIG. 7 illustrates an example 700 of a multi-AP sounding phase. Example 700 may be an example of multi-AP sounding phase 614. As shown in FIG. 7, example 700 may include a master AP 702 and a slave AP 704 of a multi-AP group. Example 700 may further include a STA 706 associated with AP 702 and a STA 708 associated with AP 704.

[0078] As shown in FIG. 7, example 700 may include frame exchanges to allow AP 702 (the master AP) to acquire channel state information (CSI) of channels in the multi-AP group. In an implementation, example 700 may include a first subphase 710 and a second subphase 712.Docket No.: 25-3026PCT

[0079] During the first subphase 710, APs may initiate channel sounding and STAs may estimate channel state information (CSI). For example, AP 702 may transmit a frame 714 to AP 704 (the slave AP) to trigger multi-AP sounding. Frame 714 may comprise a multi-AP trigger frame. Subsequently, APs 702 and 704 may transmit respectively announcement frames 716-1 and 716-2 to their respective associated STAs 706 and 708 to announce the transmission of sounding frames. Frames 716-1 and 716-2 may comprise multi-AP null data packet announcement (NDPA) frames. Frames 716-1 and 716-2 may be transmitted simultaneously. Next, APs 702 and 704 may transmit respectively frames 718-1 and 718-2 to STAs 706 and 708 respectively. Frames 718-1 and 718-2 may comprise multi-AP null data packet (NDP) frames. STAs 706 and 708 receive frames 718-1 and 718-2 respectively and perform channel estimation of the channels from AP 702 to STA 706 and from AP 704 to STA 708, respectively.

[0080] During the second subphase 712, APs may initiate a procedure for STAs to feed back channel estimates to the APs. For example, AP 702 may transmit a frame 720 to trigger STAs 706 and 708 to transmit their channel estimates to APs 702 and 704 respectively. Frame 720 may comprise a multi-AP trigger frame. In response, STAs 706 and 708 may transmit respectively frames 722 and 724 including feedback of channel estimates to APs 702 and 704 respectively. Frames 722 and 724 may comprise NDP feedback frames. The feedback of channel estimates may include NDP feedback, CSI-related information, a beamforming report (BFR), or a channel quality indication (CQI) report.

[0081] FIG. 8 illustrates an EHT sounding NDP 800. EHT sounding NDP 800 maybe used for sounding to one or more users. EHT sounding NDP 800 may be a variant of an EHT multi-user (MU) PPDU used by STAs conforming to the IEEE 802.11be standard amendment. An EHT sounding NDP may be indicated by setting a “PPDU Type and Compression Mode” field of a U-SIG field of an EHT PPDU to 1, an EHT-SIG MCS field of an EHT-SIG field of the EHT PPDU to 0, and a “Number of EHT-SIG Symbols” field to 0 in the U-SIG field of the EHT PPDU. In an example, an ultra high reliability (UHR) NDP used by STAs conforming to the IEEE 802.11bn standard amendment may use the same, or similar, structure as EHT sounding NDP 800. In an example, a UHR NDP may have the same fields as the EHT sounding NDP but with a PHY version ID in the U-SIG field indicating UHR instead of EHT. In addition, the EHT-SIG field as shown in FIG. 8 may be replaced by a UHR-SIG field which may have different carried information compared to the EHT-SIG field but with the same modulation and transmission procedure. Further, CBF may use an EHT sounding NDP 800, a UHR NDP format (to the extent a UHR NDP format differs from an EHT format), or a high efficiency (HE) NDP format used by STAs conforming to the IEEE 802.11ax.

[0082] As shown in FIG. 8, EHT sounding NDP 800 comprises a non-high throughput (non-HT) short training field (L-STF), a non-HT long training field (L-LTF), a non-HT signal field (L-SIG), a repeated non-HT signal field (RL-SIG), a universal signal field (U-SIG), an EHT signal field (EHT-SIG), an EHT short training field (EHT-STF), an EHT long training field (EHT-LTF), and a packet extension (PE) field.

[0083] The L-STF, L-LTF, L-SIG, RL-SIG, U-SIG, and EHT-SIG fields maybe referred to as pre-EHT modulated fields, while the EHT-STF, EHT-LTF, and PE fields may be referred to as EHT modulated fields.

[0084] The EHT-LTF field may comprise one or more EHT-LTF symbols. The number of EHT-LTF symbols may be indicated in a “number of EHT-LTF symbols” field of the EHT-SIG field.Docket No.: 25-3026PCT

[0085] The EHT-LTF field provides a means for a receiver of EHT sounding NDP 800 to estimate the Ml MO channel between the set of constellation mapper outputs and the receive chains. A spatial stream may refer to one or more symbols that may be transmitted over multiple spatial dimensions that are created by the use of multiple antennas at both ends of a communications link. In an EHT MU PPDU, the transmitter provides training for NSS,r, total spatial streams used for the transmission of PSDU(s) in an r-th resource unit (RU). In an EHT TB PPDU, the transmitter of user u in the r-th RU provides training for NSS, r,u spatial streams used for the transmission of the PSDU. For each subcarrier in the r-th RU, the MIMO channel that can be estimated is an NRX x NSS, r, total matrix.

[0086] An EHT transmission has a preamble that contains EHT-LTF symbols, where the data tones of each EHT-LTF symbol are multiplied by entries belonging to a matrix PEHT-LTF, to enable channel estimation at the receiver. When single stream pilots are used in 2 x or 4 x EHT-LTF, the pilot subcarriers of each EHT-LTF symbol are multiplied by the entries of a matrix REHT-LTF to allow receivers to track phase and / or frequency offset during MIMO channel estimation using the EHT-LTF. Single stream pilots are used for all spatial multiplexing modes (both UL and DL) defined in EHT except when 1 x EHT-LTF is used. PEHT-LTF is defined such that each modulated spatial stream in an RU is active on all subcarriers in that RU for which the EHT-LTF sequence takes a nonzero value.

[0087] In an EHT MU PPDU, the number of EHT-LTF symbols NEHT-LTF is indicated in the EHT-SIG field. In a non-OFDMA EHT MU PPDU or an EHT sounding NDP, the initial number of EHT-LTF symbols, initial NEHT-LTF, is a function of the total number of spatial streams NSS.

[0088] In order to improve the MIMO channel estimation for the reception of a non-OFDMAEHT MU PPDU or an EHT sounding NDP, the number of EHT-LTFs may be larger than the initial number of EHT-LTFs determined by the total number of spatial streams. If additional EHT-LTFs are used, then the total number of EHT-LTFs (which is signaled separately from NSS) can be no more than twice the initial number of EHT-LTFs determined by the number of spatial streams and chosen from the set {248}. Supporting additional EHT-LTFs is optional for the receiver, which is indicated by the maximum number of supported EHT-LTFs subfield of the EHT PHY capabilities information field.

[0089] FIG.9 illustrates an example NDPA frame 900. As shown in FIG.9, example NDPA frame 900 includes a Frame Control field, a Duration field, a receiver address (RA) field, a transmitter address (TA) field, a Sounding Dialog Token field, a STA Info List field, and a frame check sequence (FCS).

[0090] The Frame Control field indicates a type (NDPA) of NDPA frame 900. The Duration field indicates a duration of NDPA frame 900. The RA field indicates an address of one or more receiver of NDPA frame 900. The TA field indicates an address of a transmitter of NDPA frame 900. The TA field is set to the address of a STA transmitting NDPA frame 900 or a bandwidth signaling TA of the STA transmitting NDPA frame 900.

[0091] The Sounding Dialog Token field includes an NDP Announcement Variant subfield and a Sounding Dialog Token Number subfield. Based on its value, the NDP Announcement Variant subfield indicates a variant of NDPA frame 900 from among four variants: a VHT NDP Announcement frame, an HE NDP Announcement frame, a Ranging NDP Announcement frame, and an EHT NDP Announcement frame. The NDP Announcement Variant subfield is set to 2 to identify NDPA frame 900 as an HE NDP Announcement frame. The NDP Announcement Variant subfield is set to 3 toDocket No.: 25-3026PCTidentify NDPA frame 900 as an EHT NDP Announcement frame. In the HE NDP Announcement and the EHT NDP Announcement frame, the Duration, RA, and TA fields are set as in the VHT NDP Announcement frame. The Sounding Dialog Token Number subfield contains a value selected by the transmitter of NDPA frame 900 to identify NDPA frame 900.

[0092] The STA Info List field contains one or more STA Info fields. The STA Info List field includes at most one STA Info field per STA to which NDPA frame 900 is addressed in the RA field. If the STA Info List field includes only one STA Info field with a value less than 2008 in an AID11 subfield, then in the case that NDPA frame 900 is a VHT, HE, or EHT NDP Announcement frame the RA field is set to the address of the STA indicated in the only STA Info field of NDPA frame 900. If STA Info List field includes more than one STA Info field with a value less than 2008 in the AID11 subfield, then the RA field is set to a broadcast address.

[0093] A STA Info field may include an AID 11 subfield, a Partial Bandwidth (BW) Info subfield, an Nc Index subfield, a Feedback Type and Ng subfield, a Disambiguation subfield, and a Codebook Size subfield.

[0094] The AID11 subfield contains an identifier of a STA expected to process an EHT sounding NDP that follows NDPA frame 900 and to prepare sounding feedback based on the EHT sounding NDP.

[0095] The Partial BW Info subfield includes a Resolution subfield and a Feedback Bitmap subfield. The Resolution subfield indicates a resolution bandwidth for each bit in the Feedback Bitmap subfield. The Feedback Bitmap subfield indicates whether feedback is requested for each resolution bandwidth and is ordered from a lowest frequency to a highest frequency, followed by zeros. A bit in the Feedback Bitmap subfield set to 1 indicates that feedback is requested for the corresponding frequency with the resolution bandwidth. For example, a first position bit (B1) of the Feedback Bitmap subfield set to 1 indicates a request for feedback for the lowest frequency at the indicated resolution bandwidth.

[0096] When NDPA frame 900 is an EHT NDP Announcement frame and the bandwidth of a PPDU carrying NDPA frame 900 is less than 320 MHz, bit B0 of the Resolution subfield is set to 0 to indicate a resolution bandwidth of 20 MHz.

[0097] When NDPA frame 900 is an EHT NDP Announcement frame and the bandwidth of the PPDU carrying NDPA frame 900 is equal to 20 MHz, the first position bit (B1) of the Feedback Bitmap subfield is set to 1 to indicate a request for feedback on a 242-tone RU. Bits B2-B8 of the Feedback Bitmap subfield are set to 0.

[0098] When NDPA frame 900 is an EHT NDP Announcement frame and the bandwidth of the PPDU carrying NDPA frame 900 is equal to 40 MHz, the first position bit (B1) and the second position bit (B2) of the Feedback Bitmap subfield respectively indicate a request for feedback on a respective 242-tone RU (of two 242-tone RUs) from lower frequency to higher frequency. Bits B3-B8 of the Feedback Bitmap subfield are set to 0.

[0099] When NDPA frame 900 is an EHT NDP Announcement frame and the bandwidth of the PPDU carrying NDPA frame 900 is equal to 80 MHz, bits B1-B4 of the Feedback Bitmap subfield set to 1 indicate a request for feedback on a 996-tone RU; otherwise, bits B1-B4 respectively indicate a request for feedback on a respective 242-tone RU (of four 242-tone RUs) from lower frequency to higher frequency. Bits B5-B8 of the Feedback Bitmap subfield are set to 0.

[0100] When NDPA frame 900 is an EHT NDP Announcement frame and the bandwidth of the PPDU carrying NDPA frame 900 is equal to 160 MHz, bits B1-B4 of the Feedback Bitmap subfield set to 1 indicate a request for feedback onDocket No.: 25-3026PCTa lower 996-tone RU (among a lower 996-tone RU and an upper 996-tone RU); otherwise, bits B1-B4 respectively indicate a request for feedback on a respective 242-tone RU (of four 242-tone RUs) from lower frequency to higher frequency in the lower 80 MHz of the 160 MHz PPDU bandwidth. Similarly, bits B5-B8 set to 1 indicate a request for feedback on the upper 996-tone RU (among the lower 996-tone RU and the upper 996-tone RU); otherwise, bits B5-B8 respectively indicate a request for feedback on a respective 242-tone RU (of the four 242-tone RUs) from lower frequency to higher frequency in the upper 80 MHz of the 160 MHz.

[0101] When NDPA frame 900 is an EHT Announcement frame and the bandwidth of the PPDU carrying NDPA frame 900 is equal to 320 MHz, bit B0 of the Resolution subfield set to 1 indicates a resolution bandwidth of 40 MHz. When bits B1 and B2 of the Feedback Bitmap subfield are both set to 1 , they indicate a request for feedback request on a lowest 996-tone RU (among a lowest 996-tone RU, a second lowest 996-tone RU, a third lowest 996-tone RU, and a highest 996-tone RU); otherwise, bits B1 and B2 respectively indicate a request for feedback on a respective 484-tone (of two 484-tone RUs) from lower frequency to higher frequency in a lowest 80 MHz of the 320 MHz PPDU bandwidth. When bits B3 and B4 of the Feedback Bitmap subfield are both set to 1, they indicate a request for feedback on the second lowest 996-tone RU; otherwise, bits B3 and B4 indicate respectively a request for feedback on a respective 484-tone RU (of two 484-tone RUs) from lower frequency to higher frequency in a second lowest 80 MHz of the 320 MHz PPDU bandwidth. When bits B5 and B6 of the Feedback Bitmap subfield are both set to 1 , they indicate a request for feedback on the third lowest 996-tone RU; otherwise, B5 and B6 respectively indicate a request for feedback on respective 484-tone RU (of two 484-tone RUs) from lower frequency to higher frequency in a third lowest 80 MHz of the 320 MHz PPDU bandwidth. When bits B7 and B8 of the Feedback Bitmap subfield are both set to 1 , they indicate a request for feedback on the highest 996-tone RU; otherwise, bits B7 and B8 indicate respectively a request for feedback on respective 484-tone RU (of two 484-tone RUs) from lower frequency to higher frequency in a highest 80 MHz of the 320 MHz PPDU bandwidth. The feedback tone set for each 484-tone RU is composed of the feedback tone sets of the two 242-tone RUs overlapping with the 484-tone RU.

[0102] Returning to FIG. 9, the Nc Index subfield indicates the number of columns of a beamforming feedback matrix (reported in a compressed beamforming report in response to NDPA frame 900) minus 1 , if the feedback is SU feedback or MU feedback; and indicates the number of spatial streams of a CQI report (reported in a CQI report in response to NDPA frame 900) minus 1, if the feedback is CQI feedback.

[0103] The “Feedback Type and Ng” subfield indicates a feedback type and a subcarrier grouping, Ng, to be used by the STA generating the sounding feedback based on the EHT sounding NDP that follows NDPA frame 900. The feedback type may be SU feedback, MU feedback, or CQI feedback. The subcarrier grouping, Ng, indicates the number (eg., 4, 16) of adjacent subcarriers that are to be grouped in a beamforming report. When grouping is used, a single beamforming feedback matrix is reported for each group of Ng adjacent subcarriers. The “Feedback Type and Ng" subfield and the Codebook Size subfield for EHT trigger-based (TB) sounding are the same as for HE TB sounding. The “Feedback Type and Ng” and the Codebook Size subfields for EHT non-TB sounding are the same as for HE non-TB sounding.Docket No.: 25-3026PCT

[0104] If NDPA frame 900 is an EHT NDP Announcement frame with more than one STA Info field that contains a value less than 2008 in the AID11 subfield, the RA field indicates a broadcast address, and the Nc Index subfield may be set as follows:— If the "Feedback Type and Ng” subfield and the Codebook Size subfield indicate single user (SU) or multi-user (MU), the Nc Index subfield indicates the number of columns in the compressed beamforming feedback matrix minus 1, Nc-1. Nc Index subfield values above 1 are reserved.— If the "Feedback Type and Ng” subfield and the Codebook Size subfield indicate channel quality information (CQI), the Nc Index subfield indicates the number of spatial streams in the CQI report minus 1 , Nc-1. Nc Index subfield values above 7 are reserved.

[0105] If NDPA frame 900 is an EHT NDP Announcement frame with a single STA Info field that contains a value less than 2008 in the AID11 subfield, the RA field indicates an individual address, and the Nc index subfield is reserved.

[0106] In an example, a UHR NDP Announcement frame used by STAs conforming to the IEEE 802.11 bn standard amendment may use the same, or similar, structure as NDPA frame 900. In an example, a UHR NDP Announcement frame may have the same fields as the EHT NDP Announcement frame but with an NDPA version field indicating that the EHT NDP Announcement frame is followed by a UHR Sounding NDP instead of an EHT Sounding NDP, and that the UHR NDP Announcement frame is soliciting a UHR Compressed Beamforming / CQI frame instead of an EHT Compressed Beamforming / CQI frame as discussed below.

[0107] FIG. 10 illustrates an example format of a trigger frame 1000. Trigger frame 1000 may be used by an AP to allocate resources for and solicit one or more TB PPDU transmissions from one or more STAs. Trigger frame 1000 may also carry other information required by a responding STA to transmit a TB PPDU to the AP.

[0108] Trigger frame 1000 may be used to carry an invitation or polling for performing a MAPC transmission by an initiating AP to a responding AP. Depending on the purpose of the invitation / polling, trigger frame 1000 may be referred to as a Co-BF sounding invite frame, a Co-SR interference measurement invite frame, a Co-BF request frame, or a Co-SR request frame.

[0109] As shown in FIG. 10, trigger frame 1000 includes a Frame Control field, a Duration field, a receiver address (RA) field, a transmitter address (TA) field, a Common Info field, a User Info List field, a Padding field, and an FCS field.

[0110] The Frame Control field includes the following subfields: protocol version, type, subtype, To DS, From DS, more fragments, retry, power management, more data, protected frame, and +HTC.

[0111] The Duration field indicates various contents depending on frame type and subtype and the QoS capabilities of the sending STA. For example, in control frames of the power save poll (PS-Poll) subtype, the Duration field carries an association identifier (AID) of the STA that transmitted the frame in the 14 least significant bits (LSB), and the 2 most significant bits (MSB) are both set to 1. In other frames sent by STAs, the Duration field contains a duration value (in microseconds) which is used by a recipient to update a network allocation vector (NAV).

[0112] The RA field is the address of the STA that is intended to receive the incoming transmission from the transmitting station. The TA field is the address of the STA transmitting trigger frame 1000 if trigger frame 1000 is addressed to STAsDocket No.: 25-3026PCTthat belong to a single BSS. The TA field is the transmitted BSSID if trigger frame 1000 is addressed to STAs from at least two different BSSs of the multiple BSSID set.

[0113] The Common Info field specifies a trigger frame type of trigger frame 1000, a transmit power of trigger frame 1000 in dBm, and several key parameters of a TB PPDU that is transmitted by a STA in response to trigger frame 1000. The trigger frame type of a trigger frame used by an AP to receive QoS data using UL MU operation is referred to as a basic trigger frame. A non-EHT non-AP HE STA interprets the Common Info field as HE variant. A non-AP EHT STA interprets the Common Info field as HE variant if B54 and B55 in the Common Info field are equal to 1; and interprets the Common Info field as EHT variant otherwise. The HE variant Common Info field and the EHT variant Common Info field use the same encoding method for the Trigger Type, UL Length, More TF, CS Required, LDPC Extra Symbol Segment, AP TX Power, Pre-FEC Padding Factor, PE Disambiguity, and Trigger Dependent Common Info subfields.

[0114] The User Info List field contains zero or more User Info fields. There are three variants for the User Info field, which are the Special User Info field, the EHT variant User Info field, and the HE variant User Info field.

[0115] The Special User Info field is a User Info field that does not carry the user specific information but carries the extended common information not provided in the Common Info field. If the Special User Info field is included in the Trigger frame, then the Special User Info Field Flag subfield of the EHT variant Common Info field is set to 0, otherwise it is set to 1. The Special User Info field is identified by an AID12 value of 2007 and is optionally present in a Trigger frame that is generated by an EHT AP. The Special User Info field, if present, is located immediately after the Common Info field of the Trigger frame and carries information for the U-SIG field of a solicited EHT TB PPDU. The PHY Version Identifier subfield indicates the PHY version of the solicited TB PPDU that is not an HE TB PPDU. The PHY Version Identifier subfield is set to 0 for EHT. Other values from 1 to 7 are reserved. The UL Bandwidth (BW) Extension subfield, together with the UL BW subfield in the Common Info field, indicates the bandwidth of the solicited TB PPDU from the addressed EHT STA (i.e., the bandwidth in the U-SIG field of the EHT TB PPDU). The EHT Spatial Reuse n subfield carries the values to be included in the corresponding Spatial Reuse n subfield in the U-SIG field of the EHT TB PPDU. The U-SIG Disregard And Validate subfield carries the values to be included in the Disregard and Validate subfields of the U-SIG field of the solicited EHT TB PPDUs. The presence and length of the Trigger Dependent User Info subfield in the Special User Info field depends on the variant of the Trigger frame.

[0116] The EHT variant User Info field contains a User Info field per STA addressed in trigger frame 1000. The per STA User Info field includes, among others, an Al D12 subfield, an RU Allocation subfield, a UL FEC Coding Type subfield, a UL EHT-MCS subfield, a Reserved subfield, a Spatial Stream (SS) Allocation / RA-RU information subfield, a UL Target Receive Power subfield, and a Power Save (PS) 160 subfield to be used by a STA in a TB PPDU transmitted in response to trigger frame 1000, and a Trigger Dependent User Info subfield. The RU Allocation subfield in an EHT variant User Info field in a Trigger frame that is not an MU-RTS Trigger frame, along with the UL BW subfield in the Common Info field, the UL BW Extension subfield in the Special User Info field, and the PS160 subfield in the EHT variant User Info field, identifies the size and the location of the RU or MRU. The values of PS160 subfield and B0 of RU Allocation subfield indicate the 80 MHz frequency subblock in which the RU or MRU is located for 26-tone RU, 52-tone RU, 106-tone RU,Docket No.: 25-3026PCT242-tone RU, 484-tone RU, 996-tone RU, 52+26-tone RU, and 106+26-tone RU. The values of PS160 subfield indicates the 160 MHz segment in which the RU or MRU is located for 20996-tone RU, 996+484-tone MRU, and 996+484+242-tone MRU. The UL FEC Coding Type subfield of the User Info field indicates the code type of the solicited EHT TB PPDU. The UL FEC Coding Type subfield is set to 0 to indicate BCC and set to 1 to indicate LDPC. The UL EHT-MCS subfield of the User Info field indicates the EHT-MCS of the solicited EHTTB PPDU. TheSS Allocation subfield of the EHT variant User Info field indicates the spatial streams of the solicited EHT TB PPDU. The UL Target Receive Power subfield indicates the expected receive signal power, measured at the AP's antenna connector and averaged over the antennas, for the EHT portion of the EHT TB PPDU transmitted on the assigned RU. The Trigger Dependent User Info subfield can be used by an AP to specify a preferred access category (AC) per STA. The preferred AC sets the minimum priority AC traffic that can be sent by a participating STA. The AP determines the list of participating STAs, along with the BW, MCS, RU allocation, SS allocation, Tx power, preferred AC, and maximum duration of the TB PPDU per participating STA. The RA-RU Information subfield is reserved in the EHT variant User Info field.

[0117] The Padding field is optionally present in management frame 400 to extend the frame length to give recipient STAs enough time to prepare a response for transmission one SIFS after the frame is received. The Padding field, if present, is at least two octets in length and is set to all 1s.

[0118] The FCS field is used by a STA to validate a received frame and to interpret certain fields from the MAC headers of a frame.

[0119] FIG. 11 illustrates an example EHT compressed beamforming / CQI frame 1100. EHT Compressed Beamforming / CQI frame 1100 may be an Action No Ack frame of category EHT. The Action field of an EHT Compressed Beamforming / CQI frame contains the information including a Category field, an EHT Action field, an EHT MIMO Control field, an EHT Compressed Beamforming Report field, an EHT MU Exclusive Beamforming Report field, an EHT CQI Report.

[0120] The Category field is set to a value of 36 for EHT category.

[0121] The EHT Action field, in the octet immediately after the Category field, differentiates the EHT Action frame formats. The EHT Action field values associated with each frame format within the EHT category. The EHT Action field is set to a value of 0 for EHT Compressed Beamforming / CQI.

[0122] The EHT MIMO Control field comprises a Nc Index subfield, a Nr Index subfield, a BW subfield, a Grouping subfield, a Codebook Information subfield, a Feedback Type subfield, a Remaining Feedback Segments subfield, a First Feedback Segment subfield, a Partial BW Info subfield, a Sounding Dialog Token Number subfield.

[0123] In an EHT Compressed Beamforming / CQI frame not carrying all or part of an EHT compressed beamforming / CQI report, the Nc Index, Nr Index, BW, Grouping, Codebook Information, Feedback Type, and Sounding Dialog Token Number subfields are reserved, the First Feedback Segment subfield is set to 0, and the Remaining Feedback Segments subfield is set to 7.Docket No.: 25-3026PCT

[0124] The EHT Compressed Beamforming Report field carries the average SNR of each spatial stream and compressed beamforming feedback matrices for use by a transmit beamformer to determine steering matrices for explicit feedback beamforming.

[0125] The EHT MU Exclusive Beamforming Report field carries explicit feedback in the form of delta SNRs. The information in the EHT Compressed Beamforming Report field and the EHT MU Exclusive Beamforming Report field can be used by the transmit MU beamformer to determine the steering matrices for DL MU-MIMO.

[0126] The EHT CQI Report field carries the per-RU average SNRs of each spatial stream, where each per-RU average SNR is the arithmetic mean of the SNR in decibels over the subcarriers of a 26-tone RU for which feedback is being requested.

[0127] The EHT CQI Report field contains EHT CQI report information. EHT CQI Report information is included in the EHT compressed beamforming / CQI report if the Feedback Type subfield in the EHT MIMO Control field indicates CQI feedback

[0128] The presence and contents of the EHT Compressed Beamforming Report field, EHT MU Exclusive Beamforming Report field, and EHT CQI Report field are dependent on the values of the Feedback Type subfield of the EHT MIMO Control field.

[0129] A Vendor Specific element is not present in the EHT Compressed Beamforming / CQI frame.

[0130] A beamforming report poll (BFRP) trigger frame may be a variation of the trigger frame 1000 illustrated in FIG.10, above. In an example, the Trigger Dependent Common Info subfield is not present in the BFRP Trigger frame. The Trigger Dependent User Info subfield of the BFRP Trigger frame may include a Feedback Segment Retransmission Bitmap subfield. The Feedback Segment Retransmission Bitmap subfield may indicate the requested feedback segments of an HE or EHT compressed beamforming / CQI report. If the bit in position n (n=0 for LSB and n=7 for MSB) is 1, then the feedback segment with the Remaining Feedback Segments subfield in the HE MIMO Control field equal to n is requested. If the bit in position n is 0, then the feedback segment with the Remaining Feedback Segments subfield in the HE MIMO Control field equal to n is not requested.

[0131] If a BFRP Trigger frame solicits an EHT compressed beamforming / CQI report, all of the bits in the Feedback Segment Retransmission Bitmap subfield are set to 1.

[0132] In an example, a UHR compressed beamforming / CQI frame used by STAs conforming to the IEEE 802.11bn standard amendment may use the same, or similar, structure as the EHT compressed beamforming / CQI frame 1100. In an example, a UHR compressed beamforming / CQI frame may have the same fields as the EHT compressed beamforming / CQI frame 1100 but with a UHR Action field indicating that the EHT compressed beamforming / CQI frame 1100 is a feedback frame in accordance to a previously received UHR NDP Announcement frame and a UHR Sounding NDP.

[0133] FIG. 12 illustrates an example 1200 of a trigger based (TB) sounding sequence. As shown in FIG. 12, example 1200 includes an AP 1202 and STAs 1204 and 1206. Example 1200 may begin with AP 1202 initiating the TB sounding sequence by transmitting an NDPA frame 1210 to STAs 1204 and 1206. NDPA frame 1210 maybe an example of NDPADocket No.: 25-3026PCTframe 900 described above. In an example, AP 1202 may be an EHT beamformer. NDPA frame 1210 may include two STA Info fields with AID11 subfields set respectively to the AIDs of STAs 1204 and 1206. An RA field of NDPA frame 1210 may be set to a broadcast address. While example 1200 is discussed as an EHT beamformer, this is merely an example. Example 1200, and other examples described throughout, may use UHR beamforming by replacing EHT frame(s) with corresponding UHRframe(s).

[0134] NDPA frame 1210 may solicit SU feedback, MU feedback, or CQI feedback from STAs 1204 and 1206. In an example, SU feedback may comprise a compressed beamforming report. In an example, the compressed beamforming report may comprise an average SNR of each spatial stream and compressed beamforming feedback matrices for use by AP 1202 to determine steering matrices for explicit feedback beamforming to STAs 1204 and 1206. In an example, MU feedback may comprise a compressed beamforming report and an MU exclusive beamforming report. In an example, the MU exclusive beamforming report may comprise explicit feedback in the form of delta SNRs. In an example, CQI feedback may comprise a CQI report. In an example, the CQI report may comprise per-RU average SNRs of each spatial stream. In an implementation, a per-RU average SNR may comprise an arithmetic mean of the SNR in decibels over the subcarriers of a 26-tone RU for which feedback is being requested. In an example, AP 1202 may be an EHT beamformer. NDPA frame 1210 may include a first STA Info field and a second STA Info field. The AID11 subfield of the first STA Info field may be set to the AID of STA 1204. The AID11 subfield of the second STA Info field may be set to the AID of STA 1206.

[0135] A SIPS after transmitting NDPA frame 1210, AP 1202 transmits an NDP 1212. NDP 1212 may be an EHT sounding NDP. A SIPS after transmitting NDP 1212, AP 1202 transmits a trigger frame 1214. Trigger frame 1214 may be a beamforming report poll frame (BFRP) frame. Trigger frame 1214 may address STAs 1204 and 1206 as beamformees ASIFS after receiving trigger frame 1214, STAs 1204 and 1206 may transmit respective feedback frames 1216 and 1218. Feedback frames 1216 and 1218 may each comprise an EHT compressed beamforming / CQI frame and may be carried in a TB PPDU. The EHT compressed beamforming / CQI frame may comprise one or more beamforming reports. For example, the beamforming report may comprise the compressed beamforming report, the MU exclusive beamforming report, or the CQI report.

[0136] In an implementation, AP 1202 may transmit additional trigger frames in the same TXOP to solicit feedback frames from EHT beamformees not addressed in trigger frame 1214. In an implementation, AP 1202 may not transmit a trigger frame that solicits a STA identified in NDPA frame 1210 unless the trigger frame is in the same TXOP as NDPA frame 1210.

[0137] In an implementation, example 1200 may represent an EHT TB sounding sequence. As such, AP 1202 may representan EHT beamformer, STAs 1204 and 1206 may represent EHT beamformees, and NDPA frame 1210 maybe an EHT NDPA.

[0138] In an implementation, as an EHT beamformer, AP 1202 may not transmit a BFRP Trigger frame that solicits a STA (e.g., STA 1204 or STA 1206) identified in NDPA frame 1210 unless the BFRP Trigger frame is in the same TXOPDocket No.: 25-3026PCTas the EHT TB sounding sequence. In an implementation, the STAs identified in NDPA frame 1210 are the same as the STAs identified in trigger frame(s) in the same TXOP.

[0139] In an implementation, as an EHT beamformer, AP 1202 may set all the bits of a "Feedback Segment Retransmission Bitmap" field of (e.g., BFRP) trigger frame 1214 to 1s. (BFRP) trigger frame 1214 contains one or more User Info fields, each of which identifies an EHT beamformee (e.g., STA 1204 or STA 1206).

[0140] In an implementation, when NDPA frame 1210 solicits SU or MU feedback, a STA Info field in NDPA frame 1210 indicates the subcarrier grouping, Ng, codebook size, and the number of columns, Nc, to be used by the EHT beamformee identified by the STA Info field for the generation of the SU or MU feedback. In an implementation, when NDPA frame 1210 solicits CQI feedback, a STA Info field in NDPA frame 900 indicates the Nc to be used by the EHT beamformee identified by the STA Info field for the generation of the CQI feedback.

[0141] In an implementation, as an EHT beamformee, when STA 1204 (or STA 1206) receives NDPA frame 1210 soliciting CQI feedback, STA 1204 / 1206 generatesan EHT CQI report for CQI feedback with Nc determined by AP 1202.

[0142] In an implementation, as an EHT beamformee, when STA 1204 (or STA 1206) receives NDPA frame 1210 with a STA Info field identifying STA 1204 (or STA 1206) soliciting SU or MU feedback, STA 1204 (or STA 1206) generates an EHT compressed beamforming report using the feedback type, Ng, codebook size, and Nc indicated in the STA Info field.

[0143] In an implementation, as an EHT beamformee, when STA 1204 (or STA 1206) receives (BFRP) trigger frame 1214 with a matching User Info field, STA 1204 (or STA 1206) transmits an EHT TB PPDU containing the EHT compressed beamforming / CQI report. In an implementation, AP 1202 transmits NDPA frame 1210 with a TA field set to a transmitted BSSID, and STA 1204 (or STA 1206) is a non-AP STA associated with an AP corresponding to a nontransmitted BSSID that supports receiving control frames with TA fields set to the transmitted BSSID, then the EHT compressed beamforming / CQI report sentby STA 1204 (or STA 1206) in response may include an RA field set to a MAC address of AP 1202.

[0144] In an implementation, if an EHT compressed beamforming / CQI report solicited by AP 1202 would result in a feedback frame (e.g., 1216 or 1218) that exceeds 11454 octets in length, then the EHT compressed beamforming / CQI report is split into up to eight feedback segments. Each feedback segment is included in a separate feedback frame and contains successive portions of the EHT compressed beamforming / CQI report. Feedback segments may be of equal length except the last feedback segment, which may be shorter. Each feedback frame that includes a feedback segment that is not the last feedback segment has a length of 11454 octets. Each feedback segment is identified by the value of the "Remaining Feedback Segments” subfield and the “First Feedback Segment' subfield in an EHT MIMO Control field of the feedback frame that includes the feedback segment. The other non-reserved subfields of the EHT MIMO Control field may be the same for all feedback segments. Feedback frames may be sent in an A-MPDU contained in a single PPDU and maybe included in the A-MPDU in descending order based on values of the “Remaining Feedback Segments” subfield.Docket No.: 25-3026PCT

[0145] In an implementation, as an EHT beamformer, when AP 1202 transmits (BFRP) trigger frame 1214 to retrieve an EHT compressed beamforming / CQI report from an EHTbeamformee (e.g., STA 1204 or STA 1206), AP 1202 solicits all possible feedback segments by setting to 1 all of the bits of the “Feedback Segment Retransmission Bitmap” subfield of the User Info field (of trigger frame 1214) identifying the EHT beamformee.

[0146] In implementation, as an EHT beamformer, if AP 1202 fails to receive some or all of the feedback segments of the EHT compressed beamforming / CQI report from an EHT beamformee (e.g., STA 1204 or STA 1206), AP 1202 may not transmit a further BFRP Trigger frame to request retransmission of the feedback segments. Instead, AP 1202 may repeat the entire EHT sounding sequence.

[0147] As feedback frames 1216 and 1218 (e.g., TB PPDUs carrying feedback frames 1216 and 1218) are transmitted by STAs 1204 and 1206 simultaneously in response to trigger frame 1214, precorrection of time, frequency, sampling clock, and power (in the case of a High Efficiency (HE) TB PPDU or extremely high throughput (EHT) TB PPDU) by STAs 1204 and 1206 maybe necessary to mitigate synchronization and interference issues atAP 1202. Specifically, frequency and sampling clock precorrections may be needed to prevent inter-carrier interference. Power precorrection may be necessary to control interference between the TB PPDUs carrying feedback frames 1216 and 1218.

[0148] In an implementation, trigger frame 1214 includes in a User Info field an uplink (UL) Target Receive Power subfield that indicates whether a STA among STAs 1204 and 1206 is to transmit TB PPDUs carrying feedback frames 1216 and / or 1218 at a maximum transmit power. The maximum transmit power may correspond to the STA's maximum transmit power for the assigned HE-MCS. The respective STA transmits the TB PPDU carrying feedback frames 1216 or 1218 at the maximum transmit power when the UL Target Receive Power subfield indicates that the maximum transmit power is to be used. Otherwise, the STA calculates the transmit power, Txp^, of the TB PPDU for the assigned HE-MCS using the equation:= PLDL + TargetRxpwrwhere PLDLis the downlink pathloss and TargetRxpwris the expected receive signal power, in units of dBm, as indicated by the UL Target Receive Power subfield in the User Info field of trigger frame 1214. If STA 1204 and / or STA 1206 applies beamforming to the TB PPDU carrying feedback frame 1216 and / or 1218, the respective STA may take into account the beamforming gain when calculating the transmit power.

[0149] In an implementation, STA 1204 and / or STA 1206 computes PLDLusing the equation:PLDL TxpwrRxpwrwhere T xp^,ris the AP’s transmit power, in units of dBm / 20 MHz, as indicated by an AP Tx Power subfield of a Common Info field of trigger frame 1214 and Rxpwris the receive signal power, in units of dBm / 20MHz, of trigger frame 1214 at an antenna connector of the STA. Rxpwrmay be an average of the receive signal power over the antennas on which the average PLDLis being computed.

[0150] Due to the finite accuracy of clock generating circuits of an AP and a STA, an AP and an associated STA tuned to the same carrier frequency may have errors in their generated carrier frequencies in reference to the ideal carrierDocket No.: 25-3026PCTfrequency. When an AP receives a TB PPDU as in example 1200, the AP may observe a baseband signal whose center frequency has an offset (i.e. carrier frequency offset or CFO) from the DC subcarrier. Similarly, an AP receiving the symbols of a TB PPDU sampled using its own clock may observe that the TB PPDU signal is generated at a clock offset (i.e. symbol clock offset or SCO) from its own sampling clock. Both SCO and CFO may result in receive errors when not properly mitigated. In order to limit the effects of CFO and SCO, a STA compensates for carrier frequency offset (CFO) error and symbol clock error with respect to trigger frame 1214 when the TB PPDU carrying feedback frame 1216 and / or 1218 is a TB PPDU or a non-HT or non-HT duplicate PPDU with the TXVECTOR parameter TRIGGE R_RES PONDI NG set to true. After compensation, the absolute value of residual CFO error with respect to trigger frame 1214 shall not exceed the following levels when measured at the 10% point of a complementary cumulative distribution function (CCDF) of CFO errors in Additive White Gaussian Noise (AWGN) ata received power of -60 dBm in the primary 20 MHz channel: 350 Hz for the data subcarriers of a TB PPDU; 2 kHz for a non-HT PPDU or non-HT duplicate PPDU. The residual CFO error measurement on an HE TB PPDU shall be made after the HE-SIG-A field. The residual CFO error measurement on an EHT TB PPDU shall be made after the U-SIG field. The residual CFO error measurement on a non-HT or non-HT duplicate PPDU shall be made after the L-STF field. The symbol clock error shall be compensated by the same ppm amount as the CFO error.

[0151] FIG. 13 illustrates an example block acknowledgment (BA) frame 1300 which maybe used as a response frame. For example, BA frame 1300 may be used to carry acceptance or rejection information by a responding AP to an invite / poll frame (e.g. Co-BF sounding invite frame, Co-SR interference measurement invite frame, Co-BF request frame, or Co-SR request frame) from an initiating AP. Depending on the invite / poll frame, BA frame 1300 may be referred to as a Co-BF sounding response frame, a Co-BF response frame, ora Co-SR response frame. As illustrated in FIG. 13, BA frame 1300 may correspond to a multi-STA BlockAck (multi-STA BA) frame as defined in the existing IEEE 802.11 ax / be / bn standard amendment. BA frame 1300 may be used by an AP to acknowledge one or more successfully received TB PPDU transmissions from one or more STAs or one SU PPDU transmission from one STA. BA frame 1300 may also carry other information required by a responding STA to transmit a TB PPDU to the AP. According to IEEE 802.11 ax / be / bn standard amendments, a multi-STA BA frame is supported if either UL MU or multi-TID A-MPDU operation is supported. Further, the multi-STA BA acknowledges MPDUs carried in a TB PPDU or multi-STA multi-TID, multi-STA single-TID, or single-STA multi-TID A-MPDUs.

[0152] As shown in FIG. 13, BA frame 1300 includes a Frame Control field, a Duration field, a RA field, a TA field, a block acknowledgment (BA) control field, a BA information field, and an FCS field.

[0153] The Frame Control and Duration fields may be similar to corresponding fields described above with respect to trigger frame 1000 shown in FIG. 10.

[0154] The RA field may include the address of the STA intended to receive BA frame 1300. The TA field may include the address of the STA transmitting BA frame 1300 if BA frame 1300 is addressed to STAs that belong to a single BSS.

[0155] The BA Control field includes the following subfields: reserved, BA type, reserved, no memory kept, memory configuration tag, management ACK, and TIDJNFO. As shown FIG. 13, the BA type subfield indicates BA frame variants.Docket No.: 25-3026PCTThe BA type subfield comprises 4 bits. For example, BA type 11 (1011 in binary) represents a multi-STA BA variant. The no memory kept, memory configuration tag, and the management ACK subfields are reserved for 802.1 lay standard amendments. The TIDJNFO subfield maybe reserved.

[0156] The BA Information field is sent as an acknowledgment to QoS Data frames that solicit a Multi-STA BA frame response. The BA information field may include a Per AID TID Info subfield that comprises a variable number of octets. The Per AID TID Info subfield may include the following subfields: AID TID Info (2 octets), Block Ack Starting Sequence Control (0 or 2 octets), and Block Ack Bitmap (0, 4, 9, 19, 32, 64, or 128 octets).

[0157] The AID TID Info subfield contains three subfields: AID11, ACK Type, and TID. The AID 11 subfield carries the 11 LSBs of the AID of the STA for which the Per AID TID Info subfield is intended. The ACK type and the TID subfields provide different acknowledgment contexts of the multi-STA BA frame. The Block Ack Starting Sequence Control subfield of the Per AID TID Info contains the sequence number of the first MSDU or A-MSDU for which the multi-STA BA frame is sent. The Block Ack Bitmap subfield of the BA Information field is used to indicate the received status of A-MSDUs for the STA.

[0158] The FCS field is used by a STA to validate a received frame and to interpret certain fields from the MAC headers of a frame.

[0159] FIG. 14 illustrates an example 1400 of sequential NDP sounding. Example 1400 may include two APs 1402 and 1404. Example 1400 may further include a STA 1406 associated with AP 1402 and a STA 1408 associated with AP 1404. APs 1402 and 1404 may form a multi-AP group. In example 1400, AP 1402 may wish to perform a coordinated beamforming procedure or coordinated spatial reuse procedure with AP 1404. AP 1402 may be the AP coordinating / controlling the coordinated beamforming procedure. As such, AP 1402 may be referred to as a master / sharing AP, and AP 1404 may be referred to as a slave / shared AP. As illustrated, example 1400 may include a channel sounding phase 1410 and a channel sounding phase 1420 that maybe initiated byAP 1402. Channel sounding phase 1410 may be referred to as an in-BSS UHR Co-BF sounding sequence, whereas channel sounding phase 1420 may be referred to as a cross-BSS UHR Co-BF sounding sequence. Both sounding sequences are examples of coordinated sounding (may also be referred to as Co-BF sounding) defined by a common MAPC framework for coordinated transmission schemes supported by APs. In an embodiment, example 1400 may be performed by AP 1402 and AP 1404 periodically or as necessary, to collect channel feedback for a coordinated beamforming or coordinated spatial reuse operation.

[0160] During channel sounding phase 1410, AP 1402 may use TB sounding (e.g., as discussed above in relation to example 1200 illustrated in FIG. 12) to acquire CSI of a channel between AP 1402 and STA 1406. For example, AP 1402 may transmit an NDPA frame 1412. NDPA frame 1412 may be an example of NDPA frame 900 described above and maybe used for TB sounding like NDPA frame 1210 illustrated in FIG. 12. In an example, NDPA frame 1412 is addressed to STAs associated with transmitting AP 1402 (e.g., NDPA frame 1412 is addressed to STA 1406 associated with AP 1402). In an embodiment, channel sounding phase 1410 may include, prior to NDPA frame 1412, a Co-BF sounding invite / poll frame (not shown) from AP 1402 toAP 1404 and a sounding response frame (not shown) from AP 1404 to APDocket No.: 25-3026PCT1402. In such an embodiment, the channel sounding may be terminated by AP 1402 if a sounding response frame is not received byAP 1402.

[0161] After transmitting NDPA frame 1412, AP 1402 may transmit an NDP 1414. NDP 1414 may bean EHT sounding NDP, like NDP 1212 described above in example 1200. STA 1406 determines an estimate of the channel (CSI) between AP 1402 and STA 1406 based on NDP 1414. After transmitting NDP 1414, AP 1402 may transmit a trigger frame 1416. Trigger frame 1416 maybe a BFRP frame, corresponding to trigger frame 1214 in example 1200, and may address STA 1406 as a beamformee. Like example 1200, while example 1400 is discussed as an EHT beamformer, this is merely an example. Example 1400, and other EHT examples described throughout, may use UHR beamforming by replacing EHT frame(s) with corresponding UHRframe(s).

[0162] After receiving trigger frame 1416, STA 1406 may transmit a feedback frame 1418. Like feedback frames 1216 and 1218 in example 1200, feedback frame 1418 may be carried in a TB PPDU and may include one or more beamforming reports with CSI for the channel between STA 1406 and AP 1402 (e.g., a compressed beamforming report, an MU exclusive beamforming report, ora CQI report). AP 1402 may receive feedback frame 1418 and may use the CSI for the channel between STA 1406 and AP 1402 for coordinated beamforming with AP 1404 to STAs 1406 and 1408, as discussed further below. In the coordinated beamforming, AP 1402 transmits a beamformed transmission to STA 1406 (with nulling towards STA 1408) and AP 1404 transmits a beamformed transmission to STA 1408 (with nulling towards STA 1406).

[0163] During channel sounding phase 1420, AP 1402 and AP 1404 may use TB sounding to acquire CSI of a channel between AP 1404 and STA 1406. For example, AP 1402 may transmit an NDPA frame 1422. NDPA frame 1422 maybe an example of NDPA frame 900 described above, and may be used for TB sounding like NDPA frame 1210 illustrated in FIG. 12.

[0164] As in channel sounding phase 1410, in an example, NDPA frame 1422 is addressed to STAs associated with AP 1402 (e.g., STA 1406). AP 1404 may also receive NDPA frame 1422. After receiving NDPA frame 1422 from AP 1402, AP 1404 may transmit an NDP 1424 (e.g., to STA 1406 or as a broadcast). In an example, AP 1402 and AP 1404 may negotiate in advance that AP 1404 uses NDPA frames from AP 1402 to trigger transmission of an NDP from AP 1404 to STA 1406 (e.g., an overlapping basic service set (OBSS) STA for AP 1404). In an example, an OBSS STA for an AP is a STA that is a member of a BSS operating on the same channel as the AP's BSS and within (either partly or wholly) the AP’s basic service area (BSA). As one example, AP 1402 may include an indication in NDPA frame 1422 that AP 1404 should trigger transmission of NDP 1424 from AP 1404 to STA 1406.

[0165] NDP 1424 may be an EHT sounding NDP, like NDP 1414 and NDP 1212 described above in example 1200. STA 1406 determines an estimate of the channel (CSI) between AP 1404 and STA 1406 based on NDP 1424. After AP 1404 transmits NDP 1424, AP 1402 may transmit a trigger frame 1426. Like trigger frame 1416, trigger frame 1426 may be a BFRP frame, corresponding to trigger frame 1214 in example 1200, and may address STA 1406 as a beamformee.

[0166] After receiving trigger frame 1426, STA 1406 may transmit a feedback frame 1428. Like feedback frame 1418 and feedback frames 1216 and 1218 in example 1200, feedback frame 1428 may be carried in a TB PPDU and mayDocket No.: 25-3026PCTinclude one or more beamforming reports. Based on STA 1406 receiving NDP 1424 from AP 1404, these beamforming reports may include CSI for the channel between STA 1406 and AP 1404 (e.g., a compressed beamforming report, an MU exclusive beamforming report, or a CQI report). In an example, AP 1404 receives feedback frame 1428 from STA 1406 and may use the CSI for the channel between STA 1406 and AP 1404 for coordinated beamforming with AP 1402 to STAs 1406 and 1408.

[0167] After AP 1402 completes channel sounding phase 1410 and channel sounding phase 1420 for its associated STAs (e.g., STA 1406), AP 1404 may repeat the same procedure for its associated STAs (e.g., STA 1408). For example, AP 1404 may use a third and fourth channel sounding phase (not pictured), analogous to the illustrated channel sounding phases 1410 and 1420, to acquire CSI for a channel between AP 1404 and STA 1408, and for a channel between AP 1402 and STA 1408. AP 1404 may initiate either or both third and fourth channel sounding phase (not pictured) by first transmitting a Co-BF sounding invite / poll frame to AP 1402, to which AP 1402 may respond by transmitting a sounding response frame to AP 1404.

[0168] FIG. 15 illustrates an example 1500 of joint NDP sounding. Example 1500 may include two APs 1502 and 1504. Example 1500 may further include a STA 1506 associated with AP 1502, and a STA 1508 associated with AP 1504. APs 1502 and 1504 may form a multi-AP group. In example 1500, AP 1502 may wish toperform a coordinated beamforming procedure or coordinated spatial reuse procedure with AP 1504. AP 1502 may be the AP coordinating / controlling the coordinated beamforming procedure. As such, AP 1502 may be referred to as a master / sharing AP, and AP 1504 may be referred to as a slave / shared AP. In an embodiment, example 1500 may be performed by AP 1502 and AP 1504 periodically or as necessary, to collect the necessary channel feedback for a coordinated beamforming or coordinated spatial reuse operation.

[0169] As illustrated, example 1500 may include a channel sounding phase 1510 and a channel sounding phase 1520. Channel sounding phase 1510 and channel sounding phase 1520 maybe initiated by AP 1502 and AP 1504, respectively. Channel sounding phase 1510 and channel sounding phase 1520 may each be referred to as a UHR Co-BF joint NDP sounding sequence. Both channel sounding phases 1510 and 1520 may be examples of coordinated sounding defined by a common MAPC framework for coordinated transmission schemes supported by APs. In an example, during channel sounding phase 1510, AP 1502 and AP 1504 may perform both sounding phases discussed in example 1400, simultaneously, for STA 1506. During channel sounding phase 1520, AP 1502 and AP 1504 may perform both sounding phases discussed in example 1400, simultaneously, for STA 1508.

[0170] During channel sounding phase 1510, AP 1502 may transmit an NDPAframe 1512. NDPAframe 1512 maybe an example of NDPA frame 900 described above and may be used for TB sounding like NDPA frame 1210 illustrated in FIG. 12. In an example, NDPAframe 1512 is addressed to STAsassociated with transmitting AP 1502 (e.g., NDPAframe 1512 is addressed to STA 1506 associated with AP 1502).

[0171] AP 1504 may receive NDPAframe 1512. In an example, AP 1502 and AP 1504 may negotiate in advance that AP 1504 uses N DPA frames from AP 1502 to trigger transmission of an NDP from AP 1504 to STA 1506. As one example, AP 1502 may include an indication in NDPA frame 1512 that AP 1504 should trigger transmission of NDP 1515 from APDocket No.: 25-3026PCT1504 to STA 1506 (e.g., after a SIFS duration). In an example, AP 1502 may transmit NDP 1514 to STA 1506, simultaneous with AP 1504 transmitting NDP 1515 to STA 1506. For example, AP 1502 may transmit NDP 1514 after a SIFS duration following transmission of NDPA frame 1512.

[0172] In an example, NDP 1514 and NDP 1515 are transmitted orthogonally in the code domain to avoid collision. For example, NDP 1514 and NDP 1515 may use orthogonal rows of a P matrix used in MIMO LTFs. This allows STA 1506 to simultaneously estimate CSI for a channel between STA 1506 and AP 1502 (e.g., based on NDP 1514), and for a channel between STA 1506 and AP 1504 (e.g., based on NDP 1515).

[0173] After transmitting NDP 1514, AP 1502 may transmit a trigger frame 1516. Trigger frame 1516 may be a BFRP frame, corresponding to trigger frame 1214 in example 1200, and may address STA 1506 as a beamformee.

[0174] After receiving trigger frame 1516, STA 1506 may transmit a feedback frame 1518. Like feedback frames 1216 and 1218 in example 1200, feedback frame 1518 may be carried in a TB PPDU and may include one or more beamforming reports with CSI (e.g., a compressed beamforming report, an MU exclusive beamforming report, or a CQI report). In an example, feedback frame 1518 may include CSI for both the channel between STA 1506 and AP 1502 (e.g., based on NDP 1514), and for the channel between STA 1506 and AP 1504 (e.g., based on NDP 1515). In an example, the feedback included in feedback frame 1518 may be based on large V-based feedback where the eigenvectors span the antennas across both AP 1502 and AP 1504.

[0175] AP 1502 may receive feedback frame 1518 from STA 1506 and may use the CSI for the channel between STA 1506 and AP 1502 for coordinated beamforming with AP 1504 to STAs 1506 and 1508. Similarly, AP 1504 may also receive feedback frame 1518 from STA 1506, and may use the CSI for the channel between STA 1506 and AP 1504 for the coordinated beamforming with AP 1502 to STAs 1506 and 1508. In the coordinated beamforming, AP 1502 transmits a beamformed transmission to STA 1506 (with nulling towards STA 1508) and AP 1504 transmits a beamformed transmission to STA 1508 (with nulling towards STA 1506).

[0176] As discussed, channel sounding phase 1510 illustrates joint sounding for STA 1506 associated with AP 1502. In an example, channel sounding phase 1520 corresponds to channel sounding phase 1510, but for STA 1508 associated with AP 1504 instead of STA 1506 associated with AP 1502. AP 1504 may transmit an NDPA frame 1522, and AP 1502 and AP 1504 may simultaneously transmit an NDP 1524 and an NDP 1525 (e.g., using orthogonal transmission in the code domain to avoid collision, as discussed above for NDP 1514 and NDP 1515 in channel sounding phase 1510). AP 1504 may transmit a trigger frame 1526 (e.g., a BFRP frame, like trigger frame 1516) to STA 1508.

[0177] After receiving trigger frame 1526, STA 1508 may transmit a feedback frame 1528 with CSI for both the channel between STA 1508 and AP 1504 (eg., based on NDP 1524), and for the channel between STA 1508 andAP 1502 (e.g., based on NDP 1525). AP 1504 may receive feedback frame 1528 and may use the CSI for the channel between STA 1508 and AP 1504 for coordinated beamforming with AP 1502 to STAs 1506 and 1508. Similarly, AP 1502 may also receive feedback frame 1528 from STA 1508, and may use the CSI for the channel between STA 1508 and AP 1502 for the coordinated beamforming to STAs 1506 and 1508.Docket No.: 25-3026PCT

[0178] FIG. 16 illustrates an example 1600 of a multi-AP downlink data transmission phase. Example 1600 may bean example of multi-AP data transmission phase 616. As shown in FIG. 16, example 1600 may include a master AP 1602 and a slave AP 1604 of a multi-AP group. Example 1600 may further include a STA 1606 associated with AP 1602, and a STA 1608 associated with AP 1604.

[0179] As shown in FIG. 16, example 1600 may include frame exchanges to enable master AP 1602 to coordinate with slave AP 1604 to perform specific multi-AP transmission schemes with their associated STAs 1606 and 1608 respectively. The multi-AP transmission schemes may include COFDMA, CTDMA, Co-SR, Co-BF, JT / JR, or a combination of two or more of the aforementioned schemes.

[0180] As shown in FIG. 16, master AP 1602 may begin example 1600 by transmitting a frame 1610 to AP 1604. Frame 1610 may include information related to AP 1604 (e.g., an identifier of AP 1604), synchronization information, information related to a specific multi-AP transmission scheme to be used, and / or information related to a resource unit ( RU) for use by AP 1604 to acknowledge frame 1610. Frame 1610 may comprise a control frame. For example, frame 1610 may comprise a multi-AP trigger frame.

[0181] Slave AP 1604 may receive frame 1610 and may use the synchronization information to synchronize with master AP 1602. Subsequently, APs 1602 and 1604 may perform data transmission to their associated STAs 1606 and 1608 respectively. Specifically, AP 1602 may transmit a data frame 1612 to its associated STA 1606, and AP 1604 may transmit a data frame 1614 to its associated STA 1608. Depending on the multi-AP transmission scheme being used, APs 1602 and 1604 may transmit frames 1612 and 1614 respectively to STAs in different BSSs. For example, when the multi-AP transmission scheme is JT / JR, AP 1602 may also transmit frame 1612 to STA 1608 associated with slave AP 1604, and AP 1604 may also transmit frame 1614 to STA 1608 associated with AP 1604. The resources for transmitting and receiving frames 1612 and 1614 may depend on the specific multi-AP transmission scheme adopted.

[0182] STAs 1606 and 1608 may acknowledge frames 1612 and 1614 respectively. For example, STA 1606 may transmit a frame 1616 to AP 1602, and STA 1608 may transmit a frame 1618 to AP 1604. Frames 1616 and 1618 may comprise block ack (BA) frames. STAs 1606 and 1608 may also transmit frames 1616 and 1618 to APs in different BSSs, when required by the used multi-AP transmission scheme. For example, when the multi-AP transmission scheme is JT / JR, STA 1606 may also transmit frame 1616 to AP 1604, and STA 1608 may also transmit frame 1618 to AP 1602. The resources for transmitting and receiving frames 1616 and 1618 may depend on the specific multi-AP transmission scheme adopted.

[0183] FIG. 17 illustrates an example 1700 of a multi-AP uplink data transmission phase. Example 1700 may be an example of multi-AP data transmission phase 616. As shown in FIG. 17, example 1700 may include a master AP 1702 and a slave AP 1704 of a multi-AP group. Example 1700 may further include STAs 1706 and 1708 associated with AP 1702, and a STA 1710 associated with AP 1704.

[0184] As shown in FIG. 17, example 1700 may include frame exchanges to enable master AP 1702 to coordinate with slave AP 1704 to perform specific multi-AP transmission schemes with STAs 1706, 1708, and 1710. The multi-APDocket No.: 25-3026PCTtransmission schemes may include COFDMA, CTDMA, Co-SR, Co-BF, JT / JR, or a combination of two or more of the aforementioned schemes.

[0185] As shown in FIG. 17, master AP 1702 may begin example 1700 by transmitting a frame 1712 to AP 1704. Frame 1712 may include information related to AP 1704 (e.g., an identifier of AP 1704), synchronization information, information related to a specific multi-AP transmission scheme to be used, and / or information related to an RU for use by AP 1704 to acknowledge frame 1712. Frame 1712 may comprise a control frame. For example, frame 1712 may comprise a multi-AP trigger frame.

[0186] Slave AP 1704 may receive frame 1712 and may use the synchronization information to synchronize with master AP 1702. Subsequently, APs 1702 and 1704 may solicit uplink data transmissions from their associated STAs 1706, 1708 and 1710 using trigger frames. Specifically, AP 1702 may transmit a trigger frame 1714 to its associated STAs 1706 and 1708, and AP 1 04 may transmit a trigger frame 1716 to its associated STA 1710. Depending on the multi-AP transmission scheme being used, APs 1702 and 1704 may also transmit trigger frames 1714 and 1716 respectively to STAs in different BSSs. For example, when the multi-AP transmission scheme is JT / JR, AP 1702 may also transmit trigger frame 1714 to STA 1710 associated with slave AP 1704, and AP 1704 may also transmit trigger frame 1716 to STAs 1706 and 1708 associated with AP 1702. The resources for transmitting and receiving trigger frames 1714 and 1716 may depend on the specific multi-AP transmission scheme adopted.

[0187] STAs 1706 and 1708 may respond to trigger frame 1714, STA 1710 may respond to trigger frame 1716. For example, STAs 1706 and 1708 may transmit frames 1718 and 1720 respectively to AP 1702, while STA 1710 may transmit a frame 1722 to AP 1704. Frames 1718, 1720, and / or 1722 may be transmitted simultaneously. Frames 1718, 1720, and 1722 may comprise data frames or null data frames. STAs 1706, 1708, and 1710 may also transmit frames 1718, 1720, and 1722 respectively to APs in different BSSs, when required by the used multi-AP transmission scheme. For example, when the multi-AP transmission scheme is JT / JR, STAs 1706 and 1708 may also transmit respective frames 1718 and 1720 to AP 1704, and STA 1710 may also transmit frame 1722 to AP 1702. The resources for transmitting and receiving frames 1718, 1720, and 1722 may depend on the specific multi-AP transmission scheme adopted. AP 1702 may acknowledge frames 1718 and 1720 by transmitting a multi-STA BA frame 1724 to STAs 1706 and 1708. AP 1704 may acknowledge frame 1722 by transmitting a BA frame 1726 to STA 1710.

[0188] FIG. 18 shows an example 1800 that illustrates NDP sounding procedures, such as the sequential NDP sounding procedure illustrated in FIG. 14 and the joint NDP sounding procedure illustrated in FIG. 15. As shown in FIG.18, example 1800 includes APs 1802 and 1804. APs 1802 and 1804 may form a multi-AP group. In example 1800, AP 1802 may wish to perform a coordinated beamforming (Co-BF ) procedure with AP 1804 in a TXOP obtained by AP 1802. AP 1802 may be the AP coordinating / controlling the Co-BF procedure. As such, AP 1802 may be referred to as a master / sharing AP, and AP 1804 may be referred to as a slave / shared AP.

[0189] As shown in FIG. 18, example 1800 may begin with traffic for transmission by AP 1804. In an example, the traffic may be for transmission using Co-BF (e.g., using a CO-BF PPDU). A Co-BF PPDU may be any PPDU format that is used by a sharing AP (e.g., AP 1802) and a shared AP (e.g., AP 1804) to beamform their respective data streamsDocket No.: 25-3026PCTduring a Co-BF transmission. In an example, a Co-BF PPDU may include a UHR multi-user (MU) PPDU with an indication of Co-BF transmission in the U-SIG field. In example 1800, AP 1804 may have one or more buffered bufferable unit(s) (BU) available for transmission using a Co-BF PPDU. A buffered BU available for transmission using a Co-BF PPDU may include any buffered BU for any STA that is capable of responding as a beamformee during an NDP sounding procedure for Co-BF transmission.

[0190] AP 1802 and AP 1804 may then perform a sounding sequence 1812 and a sounding sequence 1814 (e.g., as part of a sounding procedure for coordinated beamforming). For example, AP 1802 may be a member of a first BSS (e.g., along with a first one or more associated STAs), andAP 1804 maybe a member of a second, different, BSS (e.g., along with a second one or more associated STAs). In an example, the first BSS of which AP 1802 is a member may be an overlapping basic service set (OBSS) with the second BSS of which AP 1804 is a member. Sounding sequences 1812 and 1814 may be used byAP 1802 and AP 1804 to sound STAs in these separate BSSs, for Co-BF: sounding sequence 1812 may be used by AP 1802 and AP 1804 to sound the first BSS of which AP 1802 is a member (eg., to sound channels between the first one or more STAs associated with the first BSS, and each of AP 1802 and AP 1804), while sounding sequence 1814 maybe used byAP 1802 and AP 1804 to sound a second BSS of which AP 1804 is a member (e.g., to sound channels between the second one or more STAs associated with the second BSS, and each of AP 1802 andAP 1804).

[0191] Thus, as one example, sounding sequences 1812 and 1814 may correspond with sounding sequences in a sequential sounding procedure, as discussed in example 1400 illustrated in FIG. 14. In this example, AP 1802 may correspond with AP 1402 discussed in example 1400 and AP 1804 may correspond with AP 1404 discussed in example 1400. During sounding sequence 1812, AP 1802 and AP 1804 may perform both channel sounding phase 1410 and channel sounding phase 1420 in example 1400, to sound channels between each respective AP and the firstone or more STAs in the first BSS associated with AP 1802 (e.g., STA 1406 in example 1400). During sounding sequence 1814, AP 1802 and AP 1804 may again perform both channel sounding phase 1410 and channel sounding phase 1420 in example 1400, this time to sound channels between each respective AP and the second one or more STAs in the second BSS associated with AP 1804 (e.g., STA 1408 in example 1400).

[0192] As another example, sounding sequences 1812 and 1814 may correspond with sounding sequences in a joint sounding procedure, as discussed in example 1500 illustrated in FIG. 15. In this example, AP 1802 may correspond with AP 1502 discussed in example 1500 and AP 1804 may correspond with AP 1504 discussed in example 1500. In an example, sounding sequence 1812 may correspond with channel sounding phase 1510 in example 1500, and both AP 1802 and AP 1804 may sound channels between the respective APs and the first one or more STAs in the first BSS associated with AP 1802 (e.g., STA 1506 in example 1500). Sounding sequence 1814 may correspond with channel sounding phase 1520 in example 1500, and both AP 1802 and AP 1804 may sound channels between the respective APs and one or more STAs in the second BSS associated with AP 1804 (e.g., STA 1508 in example 1500).

[0193] Thus, in an example, AP 1802 and AP 1804 may perform both sounding sequence 1812 and sounding sequence 1814 to sound channels for two BSSs, to facilitate Co-BF byAP 1802 and AP 1804.Docket No.: 25-3026PCT

[0194] As illustrated in example 1800, AP 1802 may transmit a poll 1816 to AP 1804, and AP 1804 may respond with a response 1818. AP 1804 may indicate in response 1818 that AP 1804 has data to send via Co-BF . AP 1802 may receive response 1818. In an example, AP 1802 and AP 1804 may then transmit a PPDU 1820 using Co-BF (e.g., to a STA associated with AP 1804).

[0195] AP 1802 may then transmit another poll 1822 to AP 1804, and AP 1804 may respond with another response 1824. AP 1804 may indicate in response 1824 that AP 1804 has no data to send via Co-BF . For example, AP 1804 may have no buffered BU to transmit to STAs that support responding as a beamformee in a Co-BF transmission. As another example, AP 1804 may prioritize transmission of buffered BUs to STAs that do not support Co-BF (e.g., for a subsequent duration). AP 1802 may then transmit a PPDU 1826. In an example, AP 1802 may transmit PPDU 1826 without beamforming, or using beamforming from AP 1802 alone (e.g., without using Co-BF from both AP 1802 and AP 1804).

[0196] In an example, AP 1802 and AP 1804 perform additional sounding sequences 1828 and 1830. For example, AP 1802 and AP 1804 may repeat sounding periodically (e.g , at a defined interval) to facilitate transmission using Co-BF. In an example, sounding sequences 1828 and 1830 correspond with sounding sequences 1812 and 1814, discussed above, and AP 1802 and AP 1804 both sound STAs in their respective BSS.

[0197] FIG. 19 shows an example 1900 of a mechanism for protecting a multi-AP coordination (MAPC) transmission. A MAPC transmission may include a set of coordination schemes such as Co-BF, Co-SR, Co-BF sounding, or Co-SR interference measurement. As shown in FIG. 19, example 1900 includes an AP 1902, an AP 1904, and a STA 1908. In example 1900, AP 1902 coordinates with AP 1904. In an example, AP 1902 and AP 1904 may be members of a coordinating AP set or a multi-AP group. In example 1900, STA 1908 is a non-AP STA that is associated with AP 1902. STA 1908 supports Co-BF sounding (sequential NDP and / or joint NDP sounding) and Co-BF reception as a beamformee.

[0198] In example 1900, the MAPC transmission is a sequential NDP sounding procedure similar to example 1400 in FIG. 14. In contrast to example 1400, in example 1900, AP 1902 first initiates a channel sounding phase 1910, a cross-BSS UHR Co-BF sounding sequence, followed by a channel sounding phase 1920, an in-BSS UHR Co-BF sounding sequence.

[0199] Example 1900 begins with AP 1902 initiating channel sounding phase 1910 by transmitting a poll frame 1912 (e.g., a Co-BF sounding invite frame). Poll frame 1912 may be a variation of trigger frame 1000 illustrated in FIG. 10, above. Poll frame 1912 may include or indicate an invitation or a request from AP 1902 to AP 1904 to perform channel sounding phase 1910. In response to poll frame 1912, AP 1904 may transmit a response frame 1914 (e.g., a Co-BF sounding response frame). Response frame 1914 may be a variation of BA frame 1300 described in FIG. 13, above. In an implementation, the frame exchange of poll frame 1912 and response frame 1914 may be used to allow AP 1904 to reject the invitation / request by AP 1902 to perform a channel sounding phase when AP 1904 does not have enough resources to perform channel sounding (e.g., due to having too many ongoing channel sounding operations with other APs) or does not have buffered traffic to candidate Co-BF STAs. Based on AP 1904 responding to poll frame 1912 with response frame 1914, channel sounding phase 1910 may proceed (e.g., continue up to STA 1908 transmitting feedback frame 1924) or may be terminated / truncated at some point. In example 1900, response frame 1914 indicates acceptanceDocket No.: 25-3026PCTof the request / invitation in poll frame 1912, and channel sounding phase 1910 continues up to STA 1908 transmitting feedback frame 1924.

[0200] During channel sounding phase 1910, AP 1902 and AP 1904 may use TB sounding to acquire CSI of a channel between AP 1904 and STA 1908. For example, AP 1902 may transmit an NDPA frame 1916. NDPA frame 1916 may be an example of NDPA frame 900, described above, and may be used for TB sounding like NDPA frame 1210 illustrated in FIG. 12.

[0201] In an example, NDPA frame 1916 is addressed to STAs associated with AP 1902 (e.g., STA 1908). AP 1904 may also receive NDPA frame 1916. After receiving NDPA frame 1916 from AP 1902, AP 1904 may transmit an NDP 1918 (e.g., to STA 1908 or as a broadcast frame). In an example, AP 1902 and AP 1904 may negotiate in advance that an NDPA frame from AP 1902 triggers AP 1904 to transmit an NDP from AP 1904 to STA 1908 (e.g., an overlapping basic service set (OBSS) STA for AP 1904). As one example, AP 1902 may include an indication in NDPA frame 1916 that AP 1904 is to transmit NDP 1918 from AP 1904 to STA 1908.

[0202] NDP 1918 may be an EHT sounding NDP, like NDP 1212 described above in example 1200. STA 1908 determines an estimate of the channel (CSI) between AP 1904 and STA 1908 based on NDP 1918. After AP 1904 transmits NDP 1918, AP 1902 may transmit a trigger frame 1922. Trigger frame 1922 may be a BFRP frame, corresponding to trigger frame 1214 in example 1200, and may address STA 1908 as a beamformee.

[0203] After receiving trigger frame 1922, STA 1908 may transmit a feedback frame 1924. Like feedback frames 1216 and 1218 in example 1200, feedback frame 1924 may be carried in a TB PPDU and may include one or more beamforming reports. Based on STA 1908 receiving NDP 1918 from AP 1904, these beamforming reports may include CSI for the channel between AP 1904 and STA 1908 (e.g., a compressed beamforming report, an MU exclusive beamforming report, or a CQI report). In an example, AP 1904 receives feedback frame 1924 from STA 1908 and may use the CSI for the channel between AP 1904 and STA 1908 for coordinated beamforming with AP 1902 to STA 1908 and a STA associated with AP 1904 (not shown).

[0204] During channel sounding phase 1920, AP 1902 may use TB sounding (e.g., as discussed above in relation to example 1400 illustrated in FIG. 14) to acquire CSI of a channel between AP1902 and STA 1908. For example, AP 1902 may transmit an NDPA frame 1926. NDPA frame 1926 may be an example of NDPA frame 900, described above and maybe used for TB sounding like NDPA frame 1412 illustrated in FIG. 14. In an example, NDPA frame 1926 is addressed to STAs associated with AP 1902 (e.g., NDPA frame 1926 is addressed to STA 1908 associated with AP 1902).

[0205] After transmitting NDPA frame 1926, AP 1902 may transmit an NDP 1928. NDP 1928 may bean EHT sounding NDP, like NDP 1212 described above in example 1200. STA 1908 determines an estimate of the channel (CSI) between AP 1902 and STA 1908 based on NDP 1928. After transmitting NDP 1928, AP 1902 may transmit a trigger frame 1930. Trigger frame 1930 maybe a BFRP frame, corresponding to trigger frame 1214 in example 1200, and may address STA 1908 as a beamformee. Like examples 1200 and 1400, while example 1900 is discussed as using EHT beamforming, this is merely an example. Example 1900, and other EHT examples described throughout, may use UHR beamforming by replacing EHT frame(s) with corresponding UHRframe(s).Docket No.: 25-3026PCT

[0206] After receiving trigger frame 1930, STA 1908 may transmit a feedback frame 1932. Like feedback frames 1216 and 1218 in example 1200, and feedback frame 1418 in example 1400, feedback frame 1932 may be carried in a TB PPDU and may include one or more beamforming reports with CSI for the channel between AP 1902 and STA 1908 (e.g., a compressed beamforming report, an MU exclusive beamforming report, ora CQI report). AP 1902 may receive feedback frame 1932 and may use the CSI for the channel between AP 1902 and STA 1908 for coordinated beamforming with AP 1904 to STA 1908 and another STA associated with AP 1904 (not shown).

[0207] After AP 1902 completes channel sounding phase 1910 and channel sounding phase 1920 for its associated STAs (e.g., STA 1908), AP 1904 may repeat the same procedure for sounding the associated STAs (not shown) of AP 1904. For example, AP 1404 may use a third and fourth channel sounding phase (not pictured), analogous to the illustrated channel sounding phases 1910 and 1920, to acquire CSI fora channel between AP 1904 and an associated STA (not shown), and for a channel between AP 1902 and the same associated STA (not shown). AP 1904 may initiate the third channel sounding phase (not pictured) by first transmitting a Co-BF sounding invite / poll frame, to which AP 1902 may respond by transmitting a sounding response frame.

[0208] In an implementation, to protect the MAPC transmission, poll frame 1912 may include a duration field set to a duration value (e.g., in microseconds) of T, where T is equal to the time required to transmit at least response frame 1914, NDPA frame 1916, and NDP 1918, plus any applicable IFSs (e.g. SIFS, DIFS, or PIFS) (e.g., one SIFS between poll frame 1912 and response frame 1914, one SIFS between response frame 1914 and NDPA frame 1916, and one SIFS between NDPA frame 1916 and NDP 1918). In an implementation, a STA (AP STA or non-AP STA) receiving poll frame 1912 indicating the duration value of T may set its NAV to T, starting at the end of the PPDU carrying poll frame 1912 (e.g., time T 1 in FIG. 19), and may defer channel access for the duration of T until the end of NDP 1918 (e.g., until time T2 shown in FIG. 19). In an implementation, when AP 1904 transmits response frame 1914, in response to poll frame 1912, AP 1904 may set a duration field of response frame 1914 to a duration value of T, minus a SIFS, and minus the time required to transmit response frame 1914. As such, a station (AP STA or non-AP STA) receiving response frame 1914 may set or update its NAV to also end / expire at time T2 and may also defer channel access until the end of NDP 1918. Hence, by indicating a duration value of T in poll frame 1912, AP 1904 increases the probability of NDP 1918 being transmitted, due to the channel deferral of stations hearing poll frame 1912 and / or response frame 1914.

[0209] In another implementation, one or more exchanges of ICF / ICR frames may be required for the target STA(s) of the MAPC transmission. The duration value T may also include the time required for these one or more exchanges. For example, an ICF frame may be transmitted by AP 1902 to poll STA 1908 to determine the availability and / or willingness of STA 1908 to participate during channel sounding phase 1910. In an example, the participation of STA 1908 may require transitioning from a listening operation or a power save mode of operation to a frame exchange mode or an active mode of operation. After transitioning to the frame exchange mode or active mode of operation, STA 1908 may transmit an ICR to inform AP 1902 of its successful transition and / or any response (if needed) to a request in the ICF. In an implementation, the duration value T may further include the time required to transmit the ICF and ICR, plus 2 additional SIFS (or 32 microseconds) (e.g., a first SIFS before the ICR and a second SIFS between the ICF and the ICR).Docket No.: 25-3026PCT

[0210] FIG. 20 illustrates an example 2000 that highlights a problem that may occur when an AP protects a MAPC transmission. The MAPC transmission may include Co-BF, Co-SR, Co-SR interference measurement, or Co-BF sounding, for example. As shown in FIG. 20, example 2000 includes APs 2002, 2004, and 2006. In example 2000, AP 2002 coordinates with AP 2004 and AP 2006. In an example, AP 2002, AP 2004 and AP 2006 coordinate with each other as members of a coordinating AP set or a multi-AP group.

[0211] In example 2000, the MAPC transmission may be a cross-BSS UHR Co-BF sounding sequence similar to channel sounding phase 1910 described in FIG. 19 above. As shown in FIG. 20, the cross-BSS UHR Co-BF sounding sequence is initiated byAP 2002 transmitting a poll frame 2012. Poll frame 2012 may include an invitation ora request from AP 2002 to perform the cross-BSS UHR Co-BF sounding sequence. In an implementation, poll frame 2012 may include a duration field set to a duration value (e.g., in microseconds) of T, where T is equal to the time required to transmit at least a response frame to poll frame 2012, an NDPA frame, and an NDP, plus any applicable IFSs (e.g. SIFS, DIFS, or PIFS) (e.g., one SIFS between poll frame 2012 and the response frame, one SIFS between the response frame and the NDPA, and one SIFS between the NDPA and the NDP). In another implementation, where one or more exchanges of ICF / ICR frames are required for the target STA(s) of the MAPC transmission, the duration value T may also include the time required for these exchanges, including any applicable SIFSs. In example 2000, AP 2006 receives poll frame 2012 and sets its NAV to the duration value T indicated in poll frame 2012.

[0212] In example 2000, due to a carrier sense (CS) / clear channel assessment (CCA) state of AP 2004 being busy after receiving poll frame 2012, AP 2004 does not respond to poll frame 2012. When AP 2002 does not receive a response topoIl frame 2012 after a timeout duration (TO) has elapsed, AP 2002 may determine that AP 2004 has a CS / CCA state that is not idle, which prevents AP 2004 from responding to poll frame 2012 and / or performing cross-BSS UHR Co-BF sounding In an implementation, TO may be based on a CTSTimeout interval. In an implementation, AP 2002 may use the CTSTimeout interval to determine whether a transmission of poll frame 2012 failed after a PHY-RXEARLYSIG. indication or PHY-RXSTART.indication primitive is not received during a CTSTimeout interval after transmitting poll frame 2012. In another implementation, TO may include a value of aSI FSTime (e.g. 16 microseconds) + aSlotTime (e.g. 9 microseconds) + aRxPHYStartDelay (e.g 24 microseconds).

[0213] In an implementation, based on determining that AP 2004 has a CS / CCA state that is not idle / busy, AP 2002 transmits a poll frame 2014 to AP 2006 to initiate a second MAPC transmission (e.g. Co-BF sounding, Co-SR interference measurement, Co-BF transmission, Co-SR transmission). AP 2006 may be willing to join the second MAPC transmission with AP 2002, but as AP 2006 set its NAV to the duration value T based on poll frame 2012, AP 2006 may have a nonzero NAV when AP 2006 receives poll frame 2014 and may thus not be able to respond to poll frame 2014. This may result in channel inefficiency with multiple poll frame retransmissions and missed opportunities for MAPC transmissions.

[0214] Embodiments of the present disclosure, as further described below, address the above-described problem of existing technologies. In an aspect, a first AP receives a first frame, transmitted by a second AP to a third AP, where the first frame indicates a first duration of a transmit opportunity (TXOP) obtained by the second AP. The first AP receives from the second AP, and during the first duration, a second frame soliciting a third frame from the first AP. In anDocket No.: 25-3026PCTembodiment, based on receiving the second frame, the first AP transmits to the second AP, the third frame. In another embodiment, based on the second AP being an owner / holder of the TXOP at the time the reception of the second frame, the first AP transmits to the second AP, the third frame. In a further embodiment, based on the first AP coordinating with the second AP for a multi-AP coordination (MAPC) operation, the first AP transmits to the second AP, the third frame. As such, the first AP may transmit the third frame, during the first duration, despite having a non-zero NAV set based on the first frame. In an embodiment, the first AP may reset or ignore the NAV before transmitting the third frame. In an embodiment, the first frame and the second frame may comprise polling frames for MAPC transmission, and the third frame may comprise a response to a polling frame.

[0215] One or more disclosed embodiments may improve communication efficiency. For example, in an embodiment, APs may avoid wasted poll and response frames for multi-AP coordinated transmission. In an embodiment, APs, which may be unnecessarily prevented from responding to a MAPC operation invitation from another AP using existing procedures, are enabled to respond to such invitation. By avoiding these wasted transmissions and / or unnecessary preventions, channel efficiency may be increased.

[0216] FIG.21 illustrates an example 2100 of a procedure according to an embodiment. As shown in FIG.21, example 2100 includes APs 2102, 2104, and 2106 and STA 2108. In an embodiment, AP 2102, AP 2104, and AP 2106 coordinate with each other as members of a coordinating AP setor a multi-AP group. In example 2100, AP 2102 may wish to perform a MAPC transmission (e.g., a Co-BF transmission, a Co-SR transmission, ora Co-BF sounding operation / sequence) with APs 2104 and 2106 in a TXOP obtained by AP 2102. AP 2102 may be the AP coordi nating / control ling / initiating the MAPC transmission. As such, AP 2102 may be referred to as a master / sharing / initiating AP, and APs 2104 and 2106 may be referred to as slave / shared / responding APs. STA 2108 may be associated with AP 2102. In example 2100, STA 2108 may be a Co-BF candidate STA for a Co-BF transmission that includes AP 2102. As such, STA 2108 supports Co-BF sounding (sequential NDP and / or joint NDP sounding) and Co-BF reception as a beamformee.

[0217] In example 2100, the MAPC transmission initiated by AP 2102 may be a cross-BSS UHR Co-BF sounding sequence similar to channel sounding phase 1910 described in FIG. 19 above. As shown in FIG. 21, the cross-BSS UHR Co-BF sounding sequence is initiated by AP 2102 transmitting a frame 2114. Frame 2114 may include an invitation or a request (e.g., a Co-BF sounding invite frame) from AP 2102 to AP 2104 to perform the cross-BSS UHR Co-BF sounding sequence. Frame 2114 may be a variation of trigger frame 1000 illustrated in FIG. 10, above. In additional embodiments, frame 2114 may be an initial control frame (ICF) that initiates a transmit opportunity (TXOP) in which the MAPC transmission is to occur.

[0218] In an embodiment, frame 2114 may include a duration field set to a duration value (e.g., in microseconds) of T, where T is equal to the time required to transmit at least a response to frame 2114 (e.g., similar to response frame 1914 in example 1900), an NDPA frame (e.g., similar to frame 1916 in example 1900), an NDP (e.g., similar to NDP 1918 in example 1900), plus any applicable IFSs (e.g. SIFS, DIFS, or PIFS) (e.g., one SIFS between frame 2114 and the response frame, one SIFS between the response frame and the NDPA, and one SIFS between the NDPA and the NDP). In another embodiment, where one or more exchanges of IC F / ICR frames are required for the target STA(s) of the MAPCDocket No.: 25-3026PCTtransmission, the duration value T may also include the time required for these exchanges, including any applicable SIFSs. In an implementation, a station (AP STA or non-AP STA) receiving frame 2114 indicating the duration value of T may set its NAV to T, starting at the end of the PPDU carrying frame 2114 (e.g., time T1 in FIG. 21), and may defer channel access for the duration of T (e.g., until time T2 in FIG. 21). For example, in example 2100, on receiving frame 2114, AP 2106 sets its NAV to the duration value T indicated in frame 2114. As further described below, AP 2106 defers channel access between time T 1 and time T2, unless a condition for channel access is met as further described below.

[0219] In example 2100, due to a carrier sense (CS) / clear channel assessment (CCA) state of AP 2104 being busy after receiving frame 2114, AP2104 may not respond to frame 2114. In an embodiment, based on AP2102 not receiving a response to frame 2114 aftera timeout duration (TO) has elapsed, AP 2102 may determine that AP 2104 has a CS / CCA state that is not idle or is busy. In an embodiment, TO may be based on a CTSTimeout interval. In an embodiment, AP 2102 may use the CTSTimeout inverval to determine whether a transmission of frame 2114 fails after a PHY-RXEARLYSIG. indication or PHY-RXSTART.indication primitive is not received during a CTSTimeout interval after transmitting frame 2114. In another embodiment, TO may include a value of aSIFSTime (e.g. 16 microseconds) + aSlotTime (e.g. 9 microseconds) + aRxPHYStartDelay (e.g 24 microseconds).

[0220] In an embodiment, based on determining that AP 2104 has a CS / CCA state that is not idle (or based on not receiving a response to frame 2114 after TO has elapsed), AP 2102 may transmit frame 2116 to AP 2106 to invite AP 2106 to a second MAPC transmission (e.g. Co-BF sounding, Co-BF transmission, Co-SR transmission or Co-SR interference measurement).

[0221] In an embodiment, despite having a non-zero NAV set based on receiving frame 2114, AP 2106 may transmit a frame 2118 in response to frame 2116. In an embodiment, AP 2106 may ignore / reset / not consider the NAV when transmitting frame 2118. In an embodiment, ignoring / resetting / not considering the NAV by AP 2106 may be based on frame 2116 being a poll frame or an invite frame (e.g. Co-BF sounding invite frame, Co-BF request frame, Co-SR request frame, Co-SR interference measurement invite frame). In another embodiment, ignoring / resetting / not considering the NAV by AP 2106 may be, additionally or alternatively, based on AP 2106 determining that frame 2116 is being transmitted by a TXOP owner (i.e. AP 2102). In an embodiment, AP 2106 determining that frame 2116 is being transmitted by a TXOP owner is based on frame 2114 being an initial control frame. In a further embodiment, ignoring / resetting / not considering the NAV by AP 2106 may be, additionally or alternatively, based on AP 2106 not detecting a frame (e.g., within a timeout period) after receiving frame 2114. In an embodiment, not detecting a frame after receiving frame 2114 may be based on absence of a PHY-RXEARLYSIG. indication or PHYRXSTART.indication primitive being received from the physical layer (PHY) (of AP 2106) during a timeout period starting when the medium access layer (MAC) (or AP 2106) receives a PHY-RXEND. indication primitive corresponding to the detection of frame 2114. In an embodiment the timeout period may be based on the NAVTimeout period. In an embodiment, the timeout period includes 2 x aSIFS Time (e.g., 16 microseconds) + responsejme + aRxPHYStartDelay (e.g., 24 microseconds) + (2 x aSlotTime), where the response time is equal to a time required to transmit the response to frame 2114. In a further embodiment, ignoring / resetting / not considering the NAV by AP 2106 may be, additionally or alternatively, based on AP 2106 receiving a frame (not shownDocket No.: 25-3026PCTin FIG. 21) transmitted by AP 2104 in response to frame 2114, after AP 2106 receives frame 2114 and before AP 2106 receives frame 2116. In a further embodiment, ignoring / resetting / not considering the NAV by AP 2106 may be, additionally or alternatively, based on AP 2106 receiving a response to frame 2114 that indicates a rejection of an invitation (or request) that is included in frame 2114.

[0222] In example 2100, frame 2118 may indicate acceptance of the invitation. In an embodiment, frame 2118 may be a variation of BA frame 1300 described in FIG. 13, above. After AP 2102 receives frame 2118 from AP 2106, AP 2102 may transmit a frame 2120 to continue the second MAPC transmission. In an embodiment, where frame 2116 is a Co-BF sounding invite frame, frame 2120 may be an NPDA frame similar to NDPA frame 1916. In an example, frame 2120 is addressed to STAs associated with AP 2102 (e.g., STA 2108). AP 2106 may also receive frame 2120. After receiving frame 2120 from AP 2102, AP 2106 may transmit a frame 2122 (e.g., to STA 2108 or as a broadcast frame). In an embodiment, frame 2122 maybe an NDP similar to NDP 1918 in example 1900. In an example, AP 2102 and AP 2106 may negotiate in advance that an NDPA frame from AP 2102 triggers AP 2106 to transmit an NDP from AP 2106 to STA 2108 (e.g., an overlapping basic service set (OBSS) STA for AP 2106). As one example, AP 2102 may include an indication in frame 2120 that AP 2106 is to transmit frame 2122 to STA 2108.

[0223] In an embodiment, frame 2116 may include a duration field set to a duration value (e.g., in microseconds) of T, where T is equal to the time required to transmit at least a response to frame (e.g., frame 2118), an NDPA frame (e.g., frame 2120), an NDP (e.g., frame 2122), plus any applicable IFSs (e.g. SIFS, DIFS, or PIFS) (e.g., one SIFS between frame 2116 and frame 2118, one SIFS between frame 2118 and frame 2120, and one SIFS between frame 2120 and frame 2122). In another embodiment, where one or more exchanges of ICF / ICR frames are required for the target STA(s) of the MAPC transmission, the duration value T may also include the time required for these exchanges, including any applicable SIFSs. In an implementation, a station (AP STA or non-AP STA) receiving frame 2116 indicating the duration value of T may set its NAV to T, starting at the end of the PPDU carrying frame 2116 (e.g., time T3 in FIG. 21), and may defer channel access for the duration of T (e.g., until time T4 in FIG. 21).

[0224] After AP 2106 transmits frame 2122, AP 2102 may transmit a trigger frame 2124. Trigger frame 2124 may be a BFRP frame, corresponding to trigger frame 1214 in example 1200, and may address STA 2108 as a beamformee.

[0225] After receiving trigger frame 2124, STA 2108 may transmit a feedback frame 2126. Like feedback frames 1216 and 1218 in example 1200, feedback frame 2126 may be carried in a TB PPDU and may include one or more beamforming reports. Based on STA 2108 receiving frame 2122 from AP 2106, these beamforming reports may include CSI for the channel between AP 2106 and STA 2108 (e.g., a compressed beamforming report, an MU exclusive beamforming report, or a CQI report). In an example, AP 2106 receives feedback frame 2126 from STA 2108 and may use the CSI for the channel between AP 2106 and STA 2108 for coordinated beamforming with AP 2102 to STA 2108 and a STA associated with AP 2106 (not shown).

[0226] FIG. 22 illustrates an example 2200 of a procedure according to an embodiment. As shown in FIG. 22, example 2200 includes APs 2202, 2204, and 2206 and STA 2208. In an embodiment, AP 2202, AP 2204, and AP 2206 coordinate with each other as members of a coordinating AP set or a multi-AP group. In example 2200, AP 2202 may wish to performDocket No.: 25-3026PCTa MAPC transmission (e.g., a Co-BF transmission, a Co-SR transmission, ora Co-BF sounding operation / sequence) with APs 2204 and 2206 in a TXOP obtained by AP 2202. AP 2202 may be the AP coordinating / controlling / initiating the MAPC transmission. As such, AP 2202 may be referred to as a master / sharing / initiating AP, and APs 2204 and 2206 may be referred to as slave / shared / responding APs. STA 2208 may be associated with AP 2202. In example 2200, STA 2208 may be a Co-BF candidate STA for a Co-BF transmission that includes AP 2202. As such, STA 2208 supports Co-BF sounding (sequential NDP and / or joint NDP sounding) and Co-BF reception as a beamformee.

[0227] In an embodiment, AP 2202, AP 2204, and / or AP 2206 may each maintain two or more NAVs. In an embodiment, a first NAV, which may be referred to as an intra-MAPC NAV, may be updated by a first AP when receiving PPDUs identified to be sent from a second AP that the first AP coordinates with or that is a member of a multi-AP group that the first AP is a member of. Alternatively or additionally, the first NAV may be updated by a first AP when receiving PPDUs identified to be sent from STAs associated with a second AP that the first AP coordinates with or that is a member of a multi-AP group that the first AP is a member of. In an embodiment, a second NAV may be an intra-BSS NAV and may be updated by a first AP when receiving PPDUs identified to be sent from a STA associated with the first AP. In an embodiment, a third NAV may be a basic NAV and may be updated by a first AP when receiving PPDUs identified to be sent from a second AP that the first AP does not coordinate with or that is not a member of a multi-AP group of which the first AP is a member. Alternatively or additionally, the third NAV may be updated by the first AP when receiving PPDUs identified to be sent from a STA that is associated with a second AP that the first AP does not coordinate with or that is not a member of a multi-AP group of which the first AP is a member.

[0228] In example 2200, the MAPC transmission initiated by AP 2202 may be a cross-BSS UHR Co-BF sounding sequence similar to channel sounding phase 1910 described in FIG. 19 above. As shown in FIG. 22, the cross-BSS UHR Co-BF sounding sequence is initiated by AP 2202 transmitting a frame 2214. Frame 2214 may include an invitation ora request (e.g., a Co-BF sounding invite frame) from AP 2202 to AP 2204 to perform the cross-BSS UHR Co-BF sounding sequence. Frame 2214 maybe a variation of trigger frame 1000 illustrated in FIG. 10, above. In additional embodiments, frame 2214 may be an initial control frame (ICF) that initiates a transmit opportunity (TXOP) in which the MAPC transmission is to occur.

[0229] In an embodiment, frame 2214 may include a duration field set to a duration value (e.g., in microseconds) of T, where T is equal to the time required to transmit at least a response to frame 2214 (e.g., similar to response frame 1914 in example 1900), an NDPA frame (e.g., similar to frame 1916 in example 1900), an NDP (e.g., similar to NDP 1918 in example 1900), plus any applicable IFSs (e.g. SIFS, DIFS, or PIFS) (e.g., one SIFS between frame 2214 and the response frame, one SIFS between the response frame and the NDPA, and one SIFS between the NDPA and the NDP). In another embodiment, where one or more exchanges of IC F / ICR frames are required for the target STA(s) of the MAPC transmission, the duration value T may also include the time required for these exchanges, including any applicable SIFSs. In an embodiment, a station (AP STA or non-AP STA) receiving frame 2214 indicating the duration value of T may set / update its first NAV (e.g., intra-MAPC NAV) to T, starting at the end of the PPDU carrying frame 2214 (e.g., time T1 in FIG.22), and may defer channel access for the duration of T (e.g., until time T2 in FIG. 22). For example, in exampleDocket No.: 25-3026PCT2200, on receiving frame 2214 and based on coordinating with AP 2202, AP 2206 sets its first NAV to the duration value T indicated in frame 2214. As further described below, AP 2206 defers channel access between time T1 and time T2, unless a condition for channel access is met as further described below.

[0230] In example 2200, due to a carrier sense (CS) / clear channel assessment (CCA) state of AP 2204 being busy after receiving frame 2214, AP 2204 may not respond to frame 2214. In an embodiment, based on AP 2202 not receiving a response to frame 2214 aftera timeout duration (TO) has elapsed, AP 2202 may determine that AP 2204 has a CS / CCA state that is not idle or busy. In an embodiment, TO may be based on a CTSTimeout interval. In an embodiment, AP 2202 may use the CTSTimeout inverval to determine whether a transmission of frame 2214 fails after a PHY-RXEARLYSIG. indication or PHY-RXSTART.indication primitive is not received during a CTSTimeout interval after transmitting frame 2214. In another embodiment, TO may include a value of aSIFSTime (e.g. 16 microseconds) + aSlotTime (e.g. 9 microseconds) + aRxPHYStartDelay (e.g 24 microseconds).

[0231] In an embodiment, based on determining that AP 2204 has a CS / CCA state that is not idle (or based on not receiving a response to frame 2214 after TO has elapsed), AP 2202 may transmit frame 2216 to AP 2206 to invite AP 2206 to a second MAPC transmission (e.g. Co-BF sounding, Co-BF transmission, Co-SR transmission or Co-SR interference measurement).

[0232] In an embodiment, frame 2216 may include a duration field set to a duration value (e.g., in microseconds) of T, where T is equal to the time required to transmit at least a response frame (e.g., frame 2218), an NDPA frame (e.g., frame 2220), an NDP (e.g., frame 2222), plus any applicable IFSs (e.g. SIFS, DIFS, or PIFS) (e.g., one SIFS between frame 2216 and frame 2218, one SIFS between the frame 2218 and frame 2220, and one SIFS between frame 2220 and frame 2222). In another embodiment, where one or more exchanges of ICF / ICR frames are required for the target STA(s) of the MAPC transmission, the duration value T may also include the time required for these exchanges, including any applicable SIFSs. In an embodiment, a station (AP STA or non-AP STA) receiving frame 2216 indicating the duration value of T may set its first NAV (e.g., intra-MAPC NAV) to T, starting at the end of the PPDU carrying frame 2216 (e.g., time T3 in FIG. 22), and may defer channel access for the duration of T (e.g., until time T4 in FIG. 22). For example, in example 2200, on receiving frame 2216 and based on coordinating with AP 2202, AP 2204 may set its first NAV to the duration value T indicated in frame 2216.

[0233] As mentioned above, AP 2206 may set / update its first NAV (e.g., intra-MAPC NAV) based on receiving frame 2214 (based on coordinating with AP 2202 or based on AP 2206 and AP 2202 being members of the same multi-AP group). In an embodiment, AP 2206 may not set / update its second / third NAV based on receiving frame 2214. As such, after receiving frame 2214, AP 2206 may have its first NAV set to a non-zero value and its second and third NAVs set to 0. In an embodiment, despite having a non-zero first NAV, AP 2206 may transmit a frame 2218 in response to frame 2216. In an embodiment, AP 2206 may ignore / reset / not consider the first NAV when transmitting frame 2218, based on the first NAV being set / updated based on frame 2216, which is carried in a PPDU sent by a STA (e.g., AP STA or non-AP STA) that coordinates with AP 2206 or that is a member of the same multi-AP group as AP 2206. Herein, this type of PPDU is referred as an intra-MAPC PPDU. In an embodiment, an AP may classify a PPDU as an intra-MAPC PPDU ifDocket No.: 25-3026PCTthe PPDU is transmitted by another AP that coordinates with the AP or another AP that is a member of the same multi-AP group as the AP. In another embodiment, an AP may also classify a PPDU as an intra-MAPC PPDU if the PPDU is transmitted by a STA associated with another AP that the AP coordinates with or another AP that is a member of the same multi-AP group as the AP.

[0234] In example 2200, frame 2218 may indicate acceptance of the invitation. In an embodiment, frame 2218 may be a variation of BA frame 1300 described in FIG. 13, above. After AP 2202 receives frame 2218 from AP 2206, AP 2202 may transmit a frame 2220 to continue the second MAPC transmission. In an embodiment, where frame 2216 is a Co-BF sounding invite frame, frame 2220 may be an NPDA frame similar to NDPA frame 1916. In an example, frame 2220 is addressed to STAs associated with AP 2202 (e.g., STA 2208). AP 2206 may also receive frame 2220. After receiving frame 2220 from AP 2202, AP 2206 may transmit a frame 2222 (e.g., to STA 2208 or as a broadcast frame). In an embodiment, frame 2222 maybe an NDP similar to NDP 1918 in example 1900. In an example, AP 2202 and AP 2206 may negotiate in advance that an NDPA frame from AP 2202 triggers AP 2206 to transmit an NDP from AP 2206 to STA 2208 (e.g., an overlapping basic service set (OBSS) STA for AP 2206). As one example, AP 2202 may include an indication in frame 2220 that AP 2206 is to transmit frame 2222 to STA 2208.

[0235] After AP 2206 transmits frame 2222, AP 2202 may transmit a trigger frame 2224. Trigger frame 2224 may be a BFRP frame, corresponding to trigger frame 1214 in example 1200, and may address STA 2208 as a beamformee.

[0236] After receiving trigger frame 2224, STA 2208 may transmit a feedback frame 2226. Like feedback frames 1216 and 1218 in example 1200, feedback frame 2226 may be carried in a TB PPDU and may include one or more beamforming reports. Based on STA 2208 receiving frame 2222 from AP 2206, these beamforming reports may include CSI for the channel between AP 2206 and STA 2208 (e.g., a compressed beamforming report, an MU exclusive beamforming report, or a CQI report). In an example, AP 2206 receives feedback frame 2226 from STA 2208 and may use the CSI for the channel between AP 2206 and STA 2208 for coordinated beamforming with AP 2202 to STA 2208 and a STA associated with AP 2206 (not shown).

[0237] As would be understood by a person of skill in the art based on the teachings herein, the embodiments as described by the above examples may be readily extended to implementations including more than one STA.

[0238] As would be understood by a person of skill in the art based on the teachings herein, the embodiments as described by the above examples may be readily extended to implementations including more than one AP.

[0239] As would be understood by a person of skill in the art based on the teachings herein, the embodiments as described by the above examples may be readily extended to scenarios in which any of the APs or any of the STAs may comprise a MLD, comprising at least one affiliated AP or affiliated STA.

[0240] FIG. 23 illustrates an example process 2300 according to an embodiment. Example process 2300 may be performed by a first AP, such as AP 2106 or AP 2206 illustrated in FIGS. 21-22, for example. As shown in FIG. 23, process 2300 may include steps 2302, 2304, and 2306.

[0241] Step 2302 includes receiving, by the first AP, a first frame, transmitted by a second AP to a third AP. In an embodiment, the first frame indicates a first duration of a transmit opportunity (TXOP) obtained by the second AP. TheDocket No.: 25-3026PCTsecond AP may beany suitable AP, such as AP 2102, or AP 2202, illustrated in FIGS. 21-22, for example. The third AP maybe any suitable AP, such asAP 2104, or AP 2204, illustrated in FIGS. 21-22, for example.

[0242] In an embodiment, the first AP coordinates with the second AP for multi-AP coordination (MAPC) operation / transmission. In an embodiment, the third AP coordinates with the second AP for MAPC operation / transmission. In an embodiment, the first frame comprises a first invitation, by the second AP to the third AP, to a first MAPC operation / transmission between the second AP and the third AP. In an embodiment, the first MAPC operation / transmission may include an interference measurement procedure, a Co-BF sounding sequence, a Co-SR transmission or a Co-BF transmission. In embodiments where the first MAPC operation / transmission is a Co-BF sounding, the Co-BF sounding may include sequential NDP sounding or joint NDP sounding. In an embodiment, the first duration comprises a second duration for an NDP announcement frame to be sent by the second AP to the third AP. In an embodiment, the first duration further comprises a third duration for a Co-BF sounding response frame to be sent by a STA associated with the second AP. In an embodiment, the first duration further comprises a fourth duration for an NDP to be transmitted by the third AP. In further embodiments, the first duration further comprises one or more interframe spaces. In further embodiments, the first duration further comprises a fifth duration of one or more initial control frame (ICF). In further embodiments, the first duration further comprises a sixth duration of one or more initial control response (ICR).

[0243] Step 2304 includes receiving, by the first AP from the second AP and during the duration, a second frame soliciting a third frame from the first AP. In an embodiment, the second frame comprises a second invitation, by the second AP to the first AP, to a second MAPC operation / transmission between the first AP and the second AP. In an embodiment, the second MAPC operation may include an interference measurement procedure, a Co-BF sounding sequence, a Co-SR transmission or a Co-BF transmission.

[0244] Step 2306 includes, based on receiving the second frame, transmitting by the first AP to the second AP, the third frame. In an embodiment, the third frame accepts the second invitation. In embodiment, process 2300 may further include setting, by the first AP, a network allocation vector (NAV), based on the first duration.

[0245] In an embodiment, process 2300 may include further include ignoring / resetting / not considering the NAV, by the first AP, to transmit the third frame. In an embodiment, ignoring / resetting / not considering the NAV by the first AP is based on the NAVbeing set / updated by the duration field of the first frame. In an embodiment, ignoring / resetting / not considering the NAV by the first AP is further based on a determining by the first AP that the second AP is a TXOP holder / owner. In an embodiment, ignoring / resetting / not considering the NAV by the first AP is further based on the first frame comprising a first invitation to a first MAPC operation / transmission. In an embodiment, ignoring / resetting / not considering the NAV by the first AP is further based on the first frame comprising a first invitation to a first MAPC operation / transmission. In an embodiment, ignoring / resetting / not considering the NAV by the first AP is further based on the first frame comprising a first invitation to a first MAPC operation / transmission and the first AP determining that the third AP does not respond to the first invitation within a timeout duration. In an embodiment, ignoring / resetting / not considering the NAV by the first AP is further based on the first AP receiving a fourth frame, where the fourth frame indicates a rejection of the first invitation.Docket No.: 25-3026PCTIn an embodiment, ignoring / resetting / not considering the NAV by the first AP is further based on the first AP coordinating with the second AP for multi-AP coordination (MAPC) operation.

[0246] FIG. 24 illustrates another example process 2400 according to an embodiment. Example process 2400 may be performed by a first AP, such as AP 2102 or AP 2202 illustrated in FIGS. 21-22, for example. As shown in FIG. 24, process 2400 may include steps 2402, 2404, and 2406.

[0247] Step 2402 includes transmitting, by the first AP to a second AP, a first frame indicating a first duration of a TXOP obtained by the first AP. The second AP may be any suitable AP, such as AP 2104, or AP 2204, illustrated in FIGS. 21-22, for example. The third AP may be any suitable AP, such as AP 2106, or AP 2206, illustrated in FIGS. 21-22, for example.

[0248] In an embodiment, the first AP coordinates with the second AP for multi-AP coordination (MAPC) operation / transmission. In an embodiment, the first AP coordinates with the third AP for MAPC operation / transmission. In an embodiment, the first frame comprises a first invitation, by the first AP to the second AP, to a first MAPC operation / transmission between the first AP and the second AP. I n an embodiment, the first MAPC operation / transmission may include an interference measurement procedure, a Co-BF sounding sequence, a Co-SR transmission or a Co-BF transmission. In embodiments where the first MAPC operation / transmission is a Co-BF sounding, the Co-BF sounding may include sequential NDP sounding or joint NDP sounding. In an embodiment, the first duration comprises a second duration for an NDP announcement frame to be sent by the second AP to the third AP. In an embodiment, the first duration further comprises a third duration for a Co-BF sounding response frame to be sent by a STA associated with the first AP. In an embodiment, the first duration further comprises a fourth duration for an NDP to be transmitted by the third AP. In further embodiments, the first duration further comprises one or more interframe spaces. In further embodiments, the first duration further comprises a fifth duration of one or more initial control frame (IGF). In further embodiments, the first duration further comprises a sixth duration of one or more initial control response (ICR).

[0249] Step 2404 includes determining, by the first AP, that a third AP ignores / resets / not consider a NAV based on the duration.

[0250] Step 2406 includes based on the determining, transmitting, by the first AP to the third AP and during the first duration, a second frame soliciting a third frame from the third AP. In an embodiment, the second frame comprises a second invitation, by the first AP to the third AP, to a second MAPC operation / transmission between the first AP and the third AP. In an embodiment, the second MAPC operation may include an interference measurement procedure, a Co-BF sounding sequence, a Co-SR transmission or a Co-BF transmission. In an embodiment, the third frame accepts the second invitation.

[0251] In an embodiment, determining by the first AP that the third AP ignores / resets / does not consider the NAV is based on the first frame comprising a first invitation to a first multi-AP coordination (MAPC) operation. In another embodiment, the determining by the first AP that the third AP ignores / resets / does not consider the NAV is further based on the second AP not responding to the first invitation during a timeout duration. In another embodiment, the determining by the first AP that the third AP ignores / resets / does not consider the NAV is based on the first AP receiving a fourth frame,Docket No.: 25-3026PCTwhere the fourth frame indicates a rejection of the first invitation. In another embodiment, the determining by the first AP that the third AP ignores / resets / does not consider the NAV is based on the first AP being an owner / holder of the TXOP.

[0252] In an embodiment, an AP or STA in accordance with the above-described embodiments (e.g., any AP or STA as described in FIGs. 21-24) may perform operations according to a Co-BF framework as described below. A person of skill in the art based on the teachings herein would appreciate that the below described features and operations may be readily combined with the above-described embodiments.

[0253] In an embodiment, UHR STAs may use an EHT sounding protocol to determine channel state information for beamformed transmissions other than Co-BF.

[0254] In an embodiment, UHR APs that have established a Co-BF MAP-C agreement use a UHR Co-BF sounding protocol that follows requirements of an EHT TB sounding protocol, except as specified for Co-BF, to determine channel state information for Co-BF transmission. In a further embodiment, the UHR Co-BF sounding protocol provides an explicit feedback mechanism, defined as UHR Co-BF sounding sequences, that includes a UHR Co-BF sequential NDP sounding sequence and a UHR Co-BF joint NDP sounding sequence. In a further embodiment, in the UHR Co-BF sounding sequences, a UHR Co-BF beamformee measures a channel using a training signal as defined for an EHT sounding NDP for a UHR Co-BF sounding sequence transmitted by one or two UHR beamformers and sends back a transformed estimate of the channel state, and a UHR beamformer uses this estimate to derive a steering matrix.

[0255] In an embodiment, a UHR Co-BF beamformer is a UHR AP with a Co-BF option implemented (e.g., dot11 Co-BFOptionlmplemented equal to true) that operates as a multi-user (MU) beamformer, and a UHR Co-BF beamformee is a non-AP UHR STA with the Co-BF option implemented that has enabled Co-BF operation and that operates as an MU beamformee. In a further embodiment, the UHR Co-BF beamformee is required to support full bandwidth MU feedback only.

[0256] In an embodiment, a UHR Co-BF beamformee may return an estimate of a channel state via an EHT compressed beamforming / CQI report using an MU feedback type. In a further embodiment, the UHR Co-BF beamformee may segment an EHT Compressed Beamforming / CQI Report frame if necessary.

[0257] In an embodiment, a UHR Co-BF beamformer may support a maximum MAC protocol data unit (MPDU) length for an EHT Compressed Beamforming / CQI Report frame that is the minimum of a defined number of octets and a maximum length of the EHT Compressed Beamforming / CQI Report frame that the UHR Co-BF beamformer intends to solicit from its UHR Co-BF beamformees.

[0258] In an embodiment, a type of feedback solicited by a UHR Co-BF beamformer from a UHR Co-BF beamformee is indicated in a Feedback Type And Ng field and a Codebook Size field in a STA Info field identifying the UHR Co-BF beamformee in a UHR NDP Announcement frame.

[0259] In an embodiment, a bandwidth of feedback solicited by a UHR Co-BF beamformer from a UHR Co-BF beamformee depends on a Partial BW Info field in a STA Info field identifying the UHR Co-BF beamformee in a UHR NDP Announcement frame, a bandwidth of a PPDU carrying the UHR NDP Announcement frame, and an operatingDocket No.: 25-3026PCTbandwidth of the UHR Co-BF beamformee. In a further embodiment, the bandwidth of the PPDU carrying the UHR NDP Announcement frame and a bandwidth of a subsequent EHT sounding NDP are the same.

[0260] In an embodiment, full bandwidth MU feedback refers to a feedback mode where a feedback resource unit (RU) or multiple resource unit (MRU) size indicated in a Partial BW Info field of a UHR NDP Announcement frame spans all available bandwidth within an operating bandwidth of a UHR Co-BF beamformee. In a further embodiment, if the operating bandwidth of the UHR Co-BF beamformee is larger than or equal to a bandwidth of an EHT sounding NDP, the available bandwidth is an entire PPDU bandwidth of the EHT sounding NDP when preamble puncturing is not applied to the PPDU, and is an entire occupied PPDU bandwidth of the EHT sounding NDP when preamble puncturing is applied to the PPDU.

[0261] In an embodiment, a UHR Co-BF beamformer sets a Partial BW Info field in a UHR NDP Announcement frame to a value selected from a defined set of bandwidth and partial bandwidth information settings for an EHT NDP Announcement frame.

[0262] In an embodiment, a UHR NDP Announcement frame does not request feedback on any RU that is signalled as punctured in a Universal SIGNAL (U-SIG) field of an EHT sounding NDP that follows the UHR NDP Announcement frame.

[0263] In an embodiment, a UHR Co-BF beamformer that initiates a UHR Co-BF sounding sequence using a Co-BF Sounding Invite frame is a Co-BF sounding initiating AP, and a UHR Co-BF beamformer that responds to the Co-BF Sounding Invite frame from the Co-BF sounding initiating AP using a Co-BF Sounding Response frame is a Co-BF sounding responding AP.

[0264] In an embodiment, a UHR NDP Announcement frame is followed after a SIFSTime by an EHT sounding NDP transmitted from a peer AP in a cross-BSS UHR Co-BF sounding sequence, or by EHT sounding NDPs simultaneously transmitted from a Co-BF sounding initiating AP and a Co-BF sounding responding AP in a UHR Co-BF joint NDP sounding sequence. In a further embodiment, the EHT sounding NDP or NDPs are followed after a SIFSTime by a BFRP Trigger frame from the AP that transmitted the UHR NDP Announcement frame preceding the EHT sounding NDP. In a further embodiment, in the UHR Co-BF sounding sequence, subsequent BFRP Trigger frames, if any, are transmitted a SIFSTime after an EHT TB PPDU transmitted in response to a previous BFRP Trigger frame, and each UHR Co-BF beamformee that is solicited by a BFRP Trigger frame responds, after a SIFSTime, with an EHT TB PPDU. In a further embodiment, all BFRP Trigger frames used within the UHR Co-BF sounding sequence are EHT variant BFRP Trigger frames. In a further embodiment, in the UHR Co-BF sounding sequence, a UHR Co-BF beamformer addresses a UHR Co-BF beamformee operating in Enhanced Multi-Link Single-Radio (EMLSR) mode and / or Dynamic Power Save (DPS) mode only in a first BFRP T rigger frame.

[0265] In an embodiment, a UHR Co-BF sequential NDP sounding sequence comprises a cross-BSS UHR Co-BF sounding sequence and may include an EHT TB sounding sequence. In a further embodiment, a UHR Co-BF beamformer supports the UHR Co-BF sequential NDP sounding sequence.

[0266] In an embodiment, a UHR Co-BF sequential NDP sounding sequence initiated by a Co-BF sounding initiating AP comprises a cross-BSS UHR Co-BF sounding sequence for a Co-BF sounding responding AP to collect channel stateDocket No.: 25-3026PCTinformation from non-AP STAs associated with the Co-BF sounding initiating AP, and may include an EHT TB sounding sequence to collect channel state information from the same non-AP STAs. In a further embodiment, the cross-BSS UHR Co-BF sounding sequence is based on a sounding sequence of EHT TB sounding except that the Co-BF sounding initiating AP transmits a UHR NDP Announcement frame to solicit an EHT sounding NDP from the Co-BF sounding responding AP. In a further embodiment, the UHR NDP Announcement frame includes a STA Info field corresponding to the Co-BF sounding responding AP and additional STA Info fields corresponding to the non-AP UHR STAs associated with the Co-BF sounding initiating AP.

[0267] In an embodiment, an EHT TB sounding sequence and a cross-BSS UHR Co-BF sounding sequence in a UHR Co-BF sequential NDP sounding sequence may be in different TXOPs or in a same TXOP.

[0268] In an embodiment, when an EHT TB sounding sequence and a cross-BSS UHR Co-BF sounding sequence in a UHR Co-BF sequential NDP sounding sequence are applied in different TXOPs, an ordering of the EHT TB sounding sequence and the cross-BSS UHR Co-BF sounding sequence is implementation dependent. In a further embodiment, a UHR Co-BF beamformer may skip the EHT TB sounding sequence if the UHR Co-BF beamformer already has in-BSS channel state information needed.

[0269] In an embodiment, when an EHT TB sounding sequence and a cross-BSS UHR Co-BF sounding sequence in a UHR Co-BF sequential NDP sounding sequence are applied in a same TXOP, the cross-BSS UHR Co-BF sounding sequence is applied first, and a subsequent EHT NDP Announcement in the EHT TB sounding sequence is transmitted a SI FSTime after an EHT TB PPDU of the cross-BSS UHR Co-BF sounding sequence.

[0270] In an embodiment, prior to a UHR Co-BF sequential NDP sounding sequence, a Co-BF Sounding Invite frame and a Co-BF Sounding Response frame are exchanged between a Co-BF sounding initiating AP and a Co-BF sounding responding AP.

[0271] In an embodiment, a Co-BF Sounding Invite frame is a Buffer Status Report Poll (BSRP) Trigger frame or a non-Trigger Based (NTB) Trigger frame as defined in a Co-BF Sounding Invite frame format. In a further embodiment, a Transmitter Address (TA) field of the Co-BF Sounding Invite frame is set to a Medium Access Control (MAC) address of a Co-BF sounding initiating AP, and a Receiver Address (RA) field of the Co-BF Sounding Invite frame is set to a MAC address of a Co-BF sounding responding AP. In a further embodiment, the Co-BF Sounding Invite frame solicits a Co-BF Sounding Response frame from the Co-BF sounding responding AP addressed by the Co-BF Sounding Invite frame.

[0272] In an embodiment, a Co-BF sounding responding AP that receives a Co-BF Sounding Invite frame transmits a Co-BF Sounding Response frame to a Co-BF sounding initiating AP a SI FSTime after an end of a PPDU carrying the Co-BF Sounding Invite frame. In a further embodiment, the Co-BF Sounding Response frame is a Multi-STA BlockAck frame as defined for Co-BF Sounding Response feedback. In a further embodiment, a TA field of the Co-BF Sounding Response frame is set to a MAC address of the Co-BF sounding responding AP, and an RA field of the Co-BF Sounding Response frame is set to a MAC address of the Co-BF sounding initiating AP.

[0273] In an embodiment, when an Initial Control Frame (ICF) and an Initial Control Response (ICR) frame between a Co-BF sounding initiating AP and its associated UHR non-AP STAs participating in a Co-BF sounding in a current TXOPDocket No.: 25-3026PCTare present, an ICF / ICR Duration field in a Co-BF Sounding Invite frame is set to a duration of a PPDU carrying the ICF plus a duration of a PPDU carrying the ICR plus a SIFSTime; the ICF frame is transmitted a SIFSTime after an end of a Co-BF Sounding Response frame; and a UHR NDP Announcement frame is transmitted a SIFSTime after an end of the ICR. In an alternative embodiment, the UHR NDP Announcement frame is transmitted a SIFSTime after the end of the Co-BF Sounding Response frame.

[0274] In an embodiment, a Co-BF sounding responding AP indicates whether it accepts or declines to participate in a UHR Co-BF sounding sequence in a Co-BF Sounding Response frame. In a further embodiment, if the Co-BF sounding responding AP rejects the Co-BF sounding invite, the Co-BF Sounding Response frame includes a reason for rejection as defined in a table of Co-BF Sounding Status Code field values.

[0275] In an embodiment, in a UHR Co-BF sequential NDP sounding sequence, to collect all required channel state information to compute a steering matrix for a Co-BF transmission, both UHR Co-BF beamformers that have established a MAP-C agreement fora Co-BF MAP-C scheme may initiate a UHR Co-BF sequential NDP sounding sequence to solicit channel state information from their own associated non-AP STAs.

[0276] In an embodiment, when an ICF and an ICRframe between a Co-BF sounding responding AP and its associated UHR non-AP STAs participating in a Co-BF sounding in a current TXOP are present, an ICF / ICR Duration field in a Co-BF Sounding Response frame is set to a duration of a PPDU carrying the ICF plus a duration of a PPDU carrying the ICR plus a SIFSTime; the ICF frame is transmitted a SIFSTime after an EHT TB PPDU transmitted by non-AP STAs associated with a Co-BF sounding initiating AP; and a UHR NDP Announcement frame from the Co-BF sounding responding AP is transmitted a SIFSTime after an end of the ICR. In an alternative embodiment, the UHR NDP Announcement frame from the Co-BF sounding responding AP is transmitted a SIFSTime after the EHT TB PPDU transmitted by the non-AP STAs associated with the Co-BF sounding initiating AP.

[0277] In an embodiment, a UHR Co-BF joint NDP sounding sequence is based on a same sounding sequence of EHT TB sounding except that a Co-BF sounding initiating AP transmits a UHR NDP Announcement frame, followed after a SIFS by EHT sounding NDPs transmitted simultaneously by both the Co-BF sounding initiating AP and a Co-BF sounding responding AP. In a further embodiment, the UHR NDP Announcement frame includes a STA Info field corresponding to the Co-BF sounding responding AP and to non-AP UHR STAs associated with the Co-BF sounding initiating AP.

[0278] In an embodiment, prior to a UHR Co-BF joint NDP sounding sequence, a Co-BF Sounding Invite frame and a Co-BF Sounding Response frame are exchanged between a Co-BF sounding initiating AP and a Co-BF sounding responding AP.

[0279] In an embodiment, in a UHR Co-BF joint NDP sounding sequence, to collect all required channel state information to compute a steering matrix for a Co-BF transmission, both UHR Co-BF beamformers that have established a MAP-C agreement for a Co-BF MAP-C scheme may initiate a UHR Co-BF joint NDP sounding sequence.

[0280] In an embodiment, in either a cross-BSS UHR Co-BF sounding sequence ora UHR Co-BF joint NDP sounding sequence, a Co-BF AP addressed by a UHR NDP Announcement frame uses information carried in a BFRP TriggerDocket No.: 25-3026PCTframe to receive a subsequent EHT TB PPDU transmitted by non-AP STAs associated with the Co-BF AP transmitting the UHR NDP Announcement frame.

[0281] In an embodiment, a UHR Co-BF beamformer that sends a BFRP Trigger frame sets a Feedback Segment Retransmission Bitmap field of the BFRP Trigger frame to all 1s.

[0282] In an embodiment, in a cross-BSS UHR Co-BF sounding sequence or a UHR Co-BF joint NDP sounding sequence, a Co-BF beamformer transmits a UHR NDP Announcement frame with three or more STA Info fields, and an RA field set to a broadcast address. In a further embodiment, a UHR Co-BF beamformer that transmits the UHR NDP Announcement frame sets an Association Identifier (AID) field of a first STA Info field to a defined value indicating the AP itself, and an AID field of a second STA Info field to an identifier of a peerAP that established a MAP-C agreement for a Co-BF MAP-C scheme. In a further embodiment, the UHR Co-BF beamformer sets an AID field to least significant bits (LSBs) of an AID value of each UHR Co-BF beamformee, starting from a third STA Info field. In a further embodiment, the UHR NDP Announcement frame does not include multiple STA Info fields with a common AID value addressed to a same STA, and the UHR NDP Announcement frame sets an AID field to a defined padding-indicator value if a padding field is present.

[0283] In an embodiment, in a UHR Co-BF joint NDP sounding sequence, a Number of EHT-LTF Symbols field in a UHR NDP Announcement frame and a Number of Spatial Streams field in the UHR NDP Announcement frame are both set to a defined value.

[0284] In an embodiment, in a UHR Co-BF sounding sequence, a STA Info field in a UHR NDP Announcement frame that solicits MU feedback indicates a subcarrier grouping Ng, a codebook size, and a number of columns Nc to be used by a UHR Co-BF beamformee identified by the STA Info field for generation of MU feedback.

[0285] In an embodiment, a UHR Co-BF beamformer that transmits a UHR NDP Announcement frame sets a Partial BW Info field in a STA Info field to indicate feedback subcarrier indices of a solicited EHT compressed beamforming / CQI report. In a further embodiment, the UHR Co-BF beamformer sets the Partial BW Info field such that the subcarrier indices of the solicited feedback fall within an operating channel width of a corresponding UHR Co-BF beamformee.

[0286] In an embodiment, a UHR Co-BF beamformee that receives a UHR NDP Announcement frame as part of a UHR Co-BF sounding sequence with a STA Info field identifying the beamformee and soliciting MU feedback generates an EHT compressed beamforming / CQI report using a feedback type, an Ng, a codebook size, and an Nc indicated in the STA Info field.

[0287] In an embodiment, if a UHR Co-BF beamformee receives a BFRP Trigger frame with a matching User Info field, the UHR Co-BF beamformee transmits an EHT TB PPDU containing an EHT compressed beamforming / CQI report following rules for non-AP STA behavior for uplink (UL) MU operation.

[0288] In an embodiment, a UHR Co-BF beamformee receiving a BFRP Trigger frame with a matching STA Info field transmits an EHT TB PPDU containing an EHT compressed beamforming / CQI report following segmentation rules for generating segmented feedback.Docket No.: 25-3026PCT

[0289] In an embodiment, a UHR Co-BF beamformer that sends a BFRP Trigger frame to retrieve an EHT compressed beamforming / CQI report from a UHR Co-BF beamformee solicits all possible EHT Sounding Feedback Segment fields and feedback segments by setting all of bits in a Feedback Segment Retransmission Bitmap field to 1 in a User Info field identifying the UHR Co-BF beamformee.

[0290] In an embodiment, a UHR Co-BF beamformer that fails to receive some or all of feedback segments of an EHT compressed beamforming / CQI report from a UHR Co-BF beamformee does not use a BFRP Trigger frame to request retransmission of the feedback segments. In a further embodiment, in this case, the UHR Co-BF beamformer may reinitiate a UHR Co-BF sounding sequence in another TXOP.

[0291] In an embodiment, an intended recipient or recipients of an EHT sounding NDP is or are STAs addressed by STA Info fields in an immediately preceding UHR NDP Announcement frame.

[0292] In an embodiment, an objective of coordinated beamforming (Co-BF) is to allow more efficient medium usage by enabling concurrent transmissions of two APs with multiple transmit chains to their associated non-AP STAs, where each AP transmits to its associated STAs while minimizing interference to non-AP STAs associated with the other AP of a Co-BF transmission by using channel state information (CSI) reports of channels between each AP and recipient STAs of the other AP of the Co-BF transmission.

[0293] In an embodiment, each of two APs that have established a Co-BF agreement between them obtains CSI reports required for performing a Co-BF transmission using a UHR Co-BF sounding procedure.

[0294] In an embodiment, a number of participating APs in a Co-BF transmission, a maximum number of spatial streams for each recipient STA of the Co-BF transmission, a maximum number of non-AP STAs participating in the Co-BF transmission, and other parameters are defined in rules for number of APs, STAs, and spatial streams in a Co-BF PPDU.

[0295] In an embodiment, an AP with a Co-BF option implemented (e.g. , dot11 Co-BFOption Implemented equal to true) sets a Co-BF Supported field to a value indicating support in a MAP-C Capabilities field of a MAP-C element transmitted by the AP. In a further embodiment, a Co-BF coordinating AP is an AP with the Co-BF option implemented that obtains a TXOP and transmits a Co-BF Invite frame to invite another AP to perform a Co-BF transmission, and a Co-BF coordinated AP is an AP with the Co-BF option implemented that receives a Co-BF Invite frame from the Co-BF coordinating AP to perform the Co-BF transmission. In a further embodiment, a Co-BF transmission sequence is initiated by the Co-BF coordinating AP.

[0296] In an embodiment, a Co-BF coordinating AP initiates a Co-BF transmission with a Co-BF coordinated AP by transmitting a Co-BF Invite frame to the Co-BF coordinated AP. In a further embodiment, the Co-BF Invite frame is a BSRP Trigger frame or an NTB Trigger frame as defined in a Co-BF Invite frame format. In a further embodiment, a TA field of the Co-BF Invite frame is set to a MAC address of the Co-BF coordinating AP, and an RA field of the Co-BF Invite frame is set to a MAC address of the Co-BF coordinated AP. In a further embodiment, the Co-BF Invite frame solicits an immediate Co-BF Response frame from the Co-BF coordinated AP addressed by the Co-BF Invite frame.Docket No.: 25-3026PCT

[0297] In an embodiment, a Co-BF coordinated AP that receives a Co-BF Invite frame transmits a Co-BF Response frame to a Co-BF coordinating AP a SIFS after an end of a PPDU carrying the Co-BF Invite frame. In a further embodiment, the Co-BF Response frame is a Multi-STA BlockAck frame as defined for a Multi-STA BlockAck variant. In a further embodiment, a TA field of the Co-BF Response frame is set to a MAC address of the Co-BF coordinated AP, and an RA field of the Co-BF Response frame is set to a MAC address of the Co-BF coordinating AP.

[0298] In an embodiment, when any non-AP STA associated with a Co-BF coordinating AP or a Co-BF coordinated AP that is being scheduled for a Co-BF transmission in a current TXOP operates in a mode that requires preceding frame exchanges with an IGF transmission, the non-AP STA's associated AP includes an ICF and ICR frame exchange in a Co-BF transmission sequence. In a further embodiment, this is the case for DPS-enabled non-AP STAs, for Dynamic Unavailability Operation (DUO) non-AP STAs, and for non-AP STAs affiliated with an EMLSR non-AP MLD that the Co-BF transmission will immediately follow on a corresponding EMLSR link.

[0299] In an embodiment, an ICF does not address any non-AP STA that will not be scheduled for a Co-BF transmission in a next Co-BF downlink (DL) PPDU.

[0300] In an embodiment, when an ICF and ICR frame exchange between a Co-BF coordinating APand its associated recipient STAs is included before a Co-BF transmission, the Co-BF coordinating AP transmits the ICF a SIFS after an end of a PPDU carrying a Co-BF Response frame. In a further embodiment, non-AP STAs that are associated with the Co-BF coordinating AP and that receive the ICF follow rules for EMLSR operation for a non-AP UHR MLD and DPS operation to respond with ICR frames.

[0301] In an embodiment, when an ICF and ICR frame exchange between a Co-BF coordinating APand its associated recipient STAs is not included before a Co-BF transmission and an ICF and ICR frame exchange between a Co-BF coordinated AP and its associated recipient STAs is included before the Co-BF transmission, the Co-BF coordinated AP transmits the ICF a SIFS after an end of a PPDU carrying a Co-BF Response frame.

[0302] In an embodiment, when an ICF and ICR frame exchange between a Co-BF coordinating APand its associated recipient STAs is included before a Co-BF transmission and an ICF and ICR frame exchange between a Co-BF coordinated AP and its associated recipient STAs is included before the Co-BF transmission, the Co-BF coordinated AP transmits the ICF (2 x aSIFSTime) plus a duration of the ICF and ICR frame exchange between the Co-BF coordinating AP and its associated recipient STAs that is indicated by an ICF / ICR Duration field in a Co-BF Invite frame, after an end of a PPDU carrying a Co-BF Response frame.

[0303] In an embodiment, non-AP STAs that are associated with a Co-BF coordinated AP and that receive an ICF follow rules for EMLSR operation for a non-AP UHR MLD and DPS operation to respond with ICR frames.

[0304] In an embodiment, if a Co-BF coordinated AP rejects a Co-BF invite, a Co-BF Response frame includes a reason for rejection as defined in a table of Co-BF Status Code field encodings.

Claims

Docket No.: 25-3026PCTCLAIMS1. A method comprising:receiving, by a first access point (AP) from a second AP, a first frame indicating a duration for a first coordinated sounding sequence for the second AP and a third AP;setting, by the first AP, a network allocation vector (NAV), based on the duration;receiving, by the first AP from the second AP and during the duration, a second frame comprising an invitation, by the second AP to the first AP, to a second coordinated sounding sequence for the first AP and the second AP; andbased on receiving the second frame during the duration:resetting the NAV; andtransmitting, by the first AP to the second AP and during the duration, a third frame accepting the invitation.

2. A method comprising:receiving, by a first access point (AP), a first frame, transmitted by a second AP to a third AP, wherein the first frame indicates a first duration of a transmit opportunity (TXOP) obtained by the second AP; receiving, by the first AP from the second AP and during the first duration, a second frame soliciting a third frame from the first AP; andbased on receiving the second frame, transmitting by the first AP to the second AP, the third frame.

3. The method of claim 2, wherein the first AP coordinates with the second AP for multi-AP coordination (MAPC) operation.

4. The method of claim 3, wherein the third AP coordinates with the second AP for MAPC operation.

5. The method of any of claims 2-4, wherein the first frame comprises a first invitation, by the second AP to the third AP, to a first multi-AP coordination (MAPC) operation between the first AP and the third AP.

6. The method of claim 5, wherein the first MAPC operation comprises at least one:an interference measurement procedure;a coordinated sounding sequence;a coordinated spatial reuse (CoSR) transmission; orcoordinated beamforming (CoBF) transmission.

7. The method of any of claims 2-6, wherein the second frame comprises a second invitation, by the second AP to the first AP, to a second multi-AP coordination (MAPC) operation between the first AP and the second AP.

8. The method of claim 7, wherein the second MAPC operation comprises at least one:an interference measurement procedure;a coordinated sounding sequence;a coordinated spatial reuse (CoSR) transmission; orcoordinated beamforming (CoBF) transmission.Docket No.: 25-3026PCT9. The method of any of claims 7-8, wherein the third frame accepts the second invitation.

10. The method of any of claims 2-9, further comprising, setting, by the first AP, a network allocation vector (NAV), based on the first duration.

11. The method of claim 10, further comprising ignoring / resetting / not considering the NAV, by the first AP, to transmit the third frame.

12. The method of claim 11 , wherein the ignoring / resetting / not considering the NAV by the first AP is based on at least one of:the first frame comprising a first invitation to a first multi-AP coordination (MAPC) operation; the first AP determining that the third AP does not respond to the first invitation;the first AP receiving a fourth frame, wherein the fourth frame indicates a rejection of the first invitation; the first AP coordinating with the second AP for multi-AP coordination (MAPC) operation; or the second AP being an owner / holder of the TXOP.

13. The method of claim 6, wherein the first MAPC operation comprises the coordinated sounding sequence, wherein the coordinated sounding sequence comprises sequential null data physical layer protocol data unit (NDP) sounding or joint NDP sounding.

14. The method of claim 13, wherein the first duration comprises a second duration for an NDP announcement frame to be sent by the second AP to the third AP.

15. The method of any of claims 13-14, wherein the first duration further comprises a third duration fora Co-BF sounding response frame to be sent by a station (STA) associated with the second AP.

16. The method of any of claims 13-15, wherein the first duration further comprises a fourth duration for an NDP to be transmitted by the third AP.

17. The method of any of claims 13-16, wherein the first duration further comprises one or more interframe spaces.

18. The method of claim 13-17, wherein the first duration further comprises a fifth duration of one or more initial control frame (IGF).

19. The method of claim 13-18, wherein the first duration further comprises a sixth duration of one or more initial control response (ICR).

20. A method comprising:transmitting, by a first access point (AP) to a second AP, a first frame indicating a duration for a first coordinated sounding sequence for the second AP and a second AP;determining, by the first AP, that a third AP ignores / resets / not consider a NAV based on the duration; based on the determining, transmitting, by the first AP to the third AP and during the duration, a second frame comprising an invitation, by the first AP to the third AP, to a second coordinated sounding sequence for the first AP and the third AP; andreceiving, by the first AP from the third AP and during the duration, a third frame accepting the invitation.

21. A method comprising:Docket No.: 25-3026PCTtransmitting, by a first access point (AP) to a second AP, a first frame indicating a first duration of a transmit opportunity (TXOP) obtained by the first AP;determining, by the first AP, that a third AP ignores / resets / not consider a NAV based on the duration; andbased on the determining, transmitting, by the first AP to the third AP and during the first duration, a second frame soliciting a third frame from the third AP.

22. The method of claim 21 , wherein the first AP coordinates with the second AP for multi-AP coordination (MAPC) operation.

23. The method of claim 22, wherein the first AP coordinates with the third AP for MAPC operation.

24. The method of any of claims 21-23, wherein the first frame comprises a first invitation, by the first AP to the second AP, to a first multi-AP coordination (MAPC) operation between the first AP and the second AP.

25. The method of claim 24, wherein the first MAPC operation comprises at least one:an interference measurement procedure;a coordinated sounding sequence;a coordinated spatial reuse (Co-SR) transmission; orcoordinated beamforming (Co-BF) transmission.

26. The method of any of claims 21-25, wherein the second frame comprises a second invitation, by the first AP to the third AP, to a second multi-AP coordination (MAPC) operation between the first AP and the third AP.

27. The method of claim 26, wherein the second MAPC operation comprises at least one:an interference measurement procedure;a coordinated sounding sequence;a coordinated spatial reuse (CoSR) transmission; orcoordinated beamforming (CoBF) transmission.

28. The method of any of claims 26-27, wherein the third frame accepts the second invitation.

29. The method of claim 21 , wherein determining by the first AP that the third AP ignores / resets / not consider the NAV is based on at least one of:the first frame comprising a first invitation to a first multi-AP coordination (MAPC) operation; the second AP not responding to the first invitation during a timeout duration;the first AP receiving a fourth frame, wherein the fourth frame indicates a rejection of the first invitation; orthe first AP being an owner / holder of the TXOP.

30. The method of claim 25, wherein the first MAPC operation comprises the coordinated sounding sequence, and wherein the coordinated sounding sequence comprises sequential null data physical layer protocol data unit (NDP) sounding or joint NDP sounding.Docket No.: 25-3026PCT31. The method of claim 30, wherein the first duration comprises a second duration for an NDP announcement frame to be sent by the first AP to the second AP.

32. The method of any of claims 30-31, wherein the first duration further comprises a third duration for a Co-BF sounding response frame to be sent by a station (STA) associated with the first AP.

33. The method of any of claims 30-32, wherein the first duration further comprises a fourth duration for an NDP to be transmitted by the second AP.

34. The method of any of claims 30-33, wherein the first duration further comprises one or more interframe spaces.

35. The method of claim 30-34, wherein the first duration further comprises a fifth duration of one or more initial control frame (IGF).

36. The method of claim 30-35, wherein the first duration further comprises a sixth duration of one or more initial control response (ICR).

37. A device comprising:one or more processors; andmemory storing instructions that, when executed by the one or more processors, cause the device to perform a method according to any of claims 1-36.A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method according to any of claims 1-36.