Coordinated restricted target wake time (r-TWT) termination
Coordinated Restricted Target Wake Time (Co-RTWT) negotiation protocols address inefficiencies in wireless networks by synchronizing wake times across multiple access points and stations, enhancing power efficiency and reducing contention.
Patent Information
- Application Number
- PCT/US2026/027257
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2026-02-04
- Filing Date
- 2026-05-08
- Publication Date
- 2026-11-12
AI Technical Summary
Existing wireless communication networks face inefficiencies in managing wake times for stations and access points, leading to increased power consumption and contention, particularly in multi-link environments where coordinated wake time management is lacking.
The implementation of Coordinated Restricted Target Wake Time (Co-RTWT) negotiation protocols that allow for synchronized wake time agreements among multiple access points and stations, optimizing power usage and reducing contention through coordinated TWT schedules.
Co-RTWT protocols enhance power efficiency and reduce contention by aligning wake times across multiple links, thereby optimizing network performance and reducing unnecessary power consumption.
Smart Images

Figure US2026027257_12112026_PF_FP_ABST
Abstract
Description
Docket No.: 25-3025PCTTITLE COORDINATED RESTRICTED TARGET WAKE TIME (R-TWT) TERMINATIONCROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 802,903, filed May 9, 2025, and U.S. Provisional Application No. 63 / 975,701 , filed February 4, 2026, all of which are hereby incorporated by reference in their entireties.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 of target wake time (TWT) operation.
[0006] FIG. 4 illustrates an example of TWT operation in an environment including an AP multi-link device (AP MLD) and a station multi-link device (STA MLD).
[0007] FIG. 5 illustrates an example TWT element which may be used to support individual TWT operation.
[0008] FIG. 6 illustrates an example TWT element which may be used to support restricted TWT (r-TWT) operation.
[0009] FIG. 7 illustrates an example of individual TWT operation.
[0010] FIG. 8 illustrates an example of broadcast TWT operation.
[0011] FIG. 9 illustrates an example of TWT protection in individual TWT operation.
[0012] FIG. 10 illustrates an example multi-AP network.
[0013] FIG. 11 illustrates an example of a multi-AP negotiation procedure including a multi-AP coordinated restricted TWT (Co-RTWT) negotiation phase, and a multi-AP agreement tear down.
[0014] FIG. 12 illustrates an example of a problem that may arise with a coordinated r-TWT operation.
[0015] FIG. 13 illustrates an example of a procedure according to an embodiment.
[0016] FIG. 14 illustrates an example of another procedure according to an embodiment.
[0017] FIG. 15 illustrates an example of a further procedure according to an embodiment.
[0018] FIG. 16 illustrates an example of a further procedure according to an embodiment.
[0019] FIG. 17 illustrates an example of a further procedure according to an embodiment.
[0020] FIG. 18 illustrates an example of a further procedure according to an embodiment.
[0021] FIG. 19 illustrates an example process according to an embodiment.
[0022] FIG. 20 illustrates an example process according to an embodiment.
[0023] FIG. 21 illustrates an example process according to an embodiment.
[0024] FIG. 22 illustrates an example process according to an embodiment.
[0025] FIG. 23 illustrates an example process according to an embodiment.Docket No.: 25-3025PCT
[0026] FIG. 24 illustrates an example process according to an embodiment.
[0027] FIG. 25 illustrates an example of a further procedure according to an embodiment.DETAILED DESCRIPTION
[0028] 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.
[0029] 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.
[0030] 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.
[0031] 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 followingDocket No.: 25-3025PCTthe 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, or may 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.
[0032] 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.
[0033] 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.
[0034] 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.
[0035] 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 (e.g. 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 asDocket No.: 25-3025PCTSimulink, 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 circuits (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.
[0036] FIG. 1 illustrates example wireless communication networks in which embodiments of the present disclosure may be implemented.
[0037] 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.
[0038] 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.
[0039] DS 130 may be 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 130 and may have the same service set identification (SSID).
[0040] 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.
[0041] 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).
[0042] For example, in FIG. 1, STAs 106-4, 106-5, and 106-6 may be 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.
[0043] 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, wirelessDocket No.: 25-3025PCTdevice, 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.
[0044] 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 PHY service data unit (PSDU). For example, the PSDU may include a PHY 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 overa 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.
[0045] A frequency band may include one or more sub-bands or frequency channels. For example, PPDUs conforming to the IEEE 802.11 n, 802.11 ac, 802.11 ax 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 320 MHz by bonding together multiple 20 MHz channels.
[0046] 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.
[0047] 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.
[0048] 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.Docket No.: 25-3025PCT
[0049] 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 by the 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.
[0050] Target wake time (TWT), a feature introduced in the IEEE 802.11ah standard, allows STAs to manage activity in the BSS by scheduling STAs to operate at different times to reduce contention. TWTs may allow STAs to reduce the required amount of time that a STA utilizing a power management mode may be awake. TWTs may be individual TWTs or broadcast TWTs. Individual TWTs follow a negotiated TWT agreement between STAs. Broadcast TWTs are based on a schedule set and provided to STAs by an AP.
[0051] In an individual TWT, a STA that requests a TWT agreement is called a TWT requesting STA. The TWT requesting STA may be a non-AP STA for example. The STA that responds to the request is called a TWT responding STA. The TWT responding STA may be an AP for example. The TWT requesting STA is assigned specific times to wake up and exchange frames with the TWT responding STA. The TWT requesting STA may communicate wake scheduling information to the TWT responding STA. The TWT responding STA may transmit TWT values to the TWT requesting STA when a TWT agreement is established between them.
[0052] When explicit TWT is employed, the TWT requesting STA may wake up and perform a frame exchange. The TWT requesting STA may receive a next TWT information in a response from the TWT responding STA. When implicit TWT is used, the TWT requesting STA may calculate a next TWT by adding a fixed value to the current TWT value.
[0053] The TWT values for implicit TWT may be periodic. The TWT requesting STA operating with an implicit TWT agreement may determine a next TWT service period (TWT SP) start time by adding a value of a TWT wake interval associated with the TWT agreement to the value of the start time of the current TWT SP. The TWT responding STA may include the start time for a series of TWT SPs corresponding to a single TWT flow identifier of an implicit TWT agreement in a target wake time field of a TWT element. The TWT element may contain a value of ‘accept TWT’ in a TWT setup command field. The start time of the TWT SP series may indicate the start time of a first TWT SP in the series. Start times of subsequent TWT SPs may be determined by adding the value of the TWT wake interval to the start time of the current TWT SP. In an example, the TWT requesting STA, awake for an implicit TWT SP, may enter a doze state after the TWT SP has elapsed or after receiving an end of service period (EOSP) field equal to 1 from the TWT responding STA, whichever occurs first.
[0054] A TWT a may be negotiated between an AP and a STA. The TWT session may configure a TWT SP of DL and UL traffic between the AP and the STA. Expected traffic may be limited within the negotiated SP. The TWT SP may start at a specific time. The TWT SP may run for a SP duration. The TWT SP may repeat every SP interval.
[0055] FIG. 3 illustrates an example 300 of TWT operation. As shown in FIG. 3, example 300 includes an AP 311 , a STA 312, and a STA 313. AP 311 and STA 312 may establish a TWT SP 320. AP 311 and STA 313 may establish a TWT SP 321. TWT SP 320 and TWT SP 321 may repeat as shown in FIG. 3, such that TWT SP 320 may include a firstDocket No.: 25-3025PCTTWT SP 320-1 and a second TWT SP 320-2, and such that TWT SP321 may include a first TWT SP 321-1 and a second TWT SP 321-2.
[0056] AP311 and STA312 may exchange frames during first TWT SP 320-1. STA312 may enter a doze state at the end of TWT SP 320-1 and may remain in the doze state until the start of second TWT SP 320-2. The start of second TWT SP 320-2 may be indicated by a TWT wake interval 330 associated with TWT SP 320. AP 311 and STA 312 may again exchange frames during second TWT SP 320-2.
[0057] Similarly, AP 311 and STA 313 may exchange frames during first TWT SP 321-1. STA 313 may enter a doze state at the end of first TWT SP 321-1 and may remain in the doze state until the start of second TWT SP 321-2. The start of second TWT SP 321-2 may be indicated by a TWT wake interval 331 associated with TWT SP 321. AP 311 and STA 313 may again exchange frames during second TWT SP 31-2.
[0058] In an awake state, a STA may be fully powered. The STA may transmit and / or receive a frame to / from an AP or another STA. In a doze state, a STA may not transmit and may not receive a frame to / from an AP or another STA.
[0059] An MLD is an entity capable of managing communication over multiple links. The MLD may be a logical entity and may have more than one affiliated station (STA). The MLD may have a single MAC service access point (MAC-SAP) to the LLC layer, which includes a MAC data service. An MLD may be an access point MLD (AP MLD) when a STA affiliated with the MLD is an AP STA (or an AP). An MLD may be a non-access point MLD (non-AP MLD) or STA MLD when a STA affiliated with the MLD is a non-AP STA (or a STA).
[0060] During negotiation of TWT agreements, a TWT requesting STA affiliated with a STA MLD and a TWT responding STA affiliated with an AP MLD may communicate multiple TWT elements. The TWT elements may comprise link ID bitmap subfields indicating different link(s) in a TWT setup frame. The TWT parameters provided by a TWT element may be applied to the respective link that is indicated in the TWT element.
[0061] FIG.4 illustrates an example 400 of TWT operation in a multi-link environment including an AP multi-link device (AP MLD) 410 and a STA multi-link device (STA MLD) 420. As shown in FIG.4, AP MLD 410 may have three affiliated APs, AP 411, AP2412, and AP3413. In an example, AP 411, AP2412, and AP3413 may operate respectively on the 2.4 GHz band, the 5 GHz band, and the 6 GHz band. STA MLD 420 may have three affiliated STAs, STA 421 , STA 422, and STA 423. In an example, STA 421, STA 422, and STA 423 may operate respectively on the 2.4 GHz band, the 5 GHz band, and the 6 GHz band. In an example, AP 411, AP2412, and AP3413 may be communicatively coupled via a first link (link 1), a second link (link 2), and a third link (link 3) respectively with STA 421, STA 422, and STA 423, respectively.
[0062] In an example, STA 421 may transmit a TWT request to AP 411. The TWT request may include three TWT elements. Each TWT element may indicate a respective link of links 1-3 and may request the setup of a TWT agreement for the indicated link. The three TWT elements may have different TWT parameters, such as target wake time (TWT). In response to the TWT request, AP 411 may transmit a TWT response to STA 421. The TWT response may include three TWT elements. Each TWT element may indicate a respective link of links 1-3 and may include a value of ‘accept TWT’ in a TWT setup command field.Docket No.: 25-3025PCT
[0063] Successful TWT agreement setup on links 1-3 establishes three TWT SPs with same or different TWT parameters on links 1-3 respectively. The target wake time field of the TWT element indicating a given link indicates the start time of the TWP SP for that link. The starting time may be indicated in reference to a time synchronization function (TSF) time of the link.
[0064] In example 400, initial TWT SPs 430-1, 430-2, and 430-3 of links 1-3 respectively may be aligned. TWT wake intervals associated with the TWT agreements of links 1-3 respectively may be set differently. As such, second TWT SPs 431-1, 431-2, and 431-3 of links 1-3 respectively may not be aligned. STA421, STA422, and STA423 may enter a doze state between the end of initial TWT SPs 430-1, 430-2, and 430-3, respectively, and the start of second TWT SPs 431-1, 431-2, 431-3, respectively.
[0065] FIG. 5 illustrates an example target wake time (TWT) element 500 which may be used to support individual TWT operation.
[0066] In an example, an AP and a STA may use TWT element 500 to negotiate a TWT agreement. The AP and / or the STA may transmit TWT element 500 in an individually addressed management frame. The management frame may be of the type action, action no ack, (re)association request / response, and probe request response, for example.
[0067] The TWT schedule and parameters may be provided during a TWT setup phase. Renegotiation / changes of TWT schedules may be signaled via individually addressed frames that contain the updated TWT schedule / parameters. The frames may be management frames as described above or control or data frames that carry a field containing the updated TWT schedule / parameters.
[0068] Referring to FIG. 5, TWT element 500 includes an element ID field, a length field, a control field, and a TWT parameter information field.
[0069] The element ID field (e.g., 1 octet in length) may indicate that information element 500 is a TWT element. The length field (e.g., 1 octet) may indicate the length of TWT element 500 starting from the control field until an end of TWT element 500. The end of TWT element 500 may be the end of a TWT Channel field or the end of a Link ID bitmap field of the TWT parameter information field.
[0070] The TWT parameter information field may include a request type field (e.g., 2 octets), a target wake time field (e.g., 8 octets or less), a TWT group assignment field (e.g., 9, 3, 2, or 0 octets), a nominal minimal TWT wake duration field (e.g., 1 octet), a TWT wake interval mantissa (e.g., 2 octets), a TWT channel field (e.g., 1 octet), an optional NDP paging field (e.g., 0 or 4 octets), and / or a Link ID bitmaps field (e.g., 0 or 2 Octets ).
[0071] The request type field may indicate a type of TWT request. The request type field may include a TWT request field (e.g., 1 bit), a TWT setup command field (e.g., 3 bits), a trigger field (e.g., 1 bit), an implicit field (e.g., 1 bit), a flow type (e.g., 1 bit), a TWT flow identifier (e.g., 3 bits), a TWT wake interval exponent (e.g., 5 bits), and / or a TWT protection field (e.g., 1 bit).
[0072] The TWT request field may indicate whether the TWT element 500 represents a request. If TWT request field has a value of 1 , then the TWT element 500 may represent a request to initiate TWT scheduling / setup.Docket No.: 25-3025PCT
[0073] The TWT setup command field may indicate a type of TWT command. In a TWT request, the type of TWT command indicated may be: a request TWT (the TWT responding STA specifies the TWT value; e.g., field set to 0), a suggest TWT (the TWT requesting STA suggests a TWT value; e.g., field set to 1), and a demand TWT (the TWT requesting STA demands a TWT value; e.g., field set to 2).
[0074] In a TWT response, the type of TWT command indicated may be: TWT grouping (the TWT responding STA suggests TWT group parameters that are different than the suggested or demanded TWT parameters of the TWT requesting STA; e.g., field set to 3), accept TWT (the TWT responding STA accepts the TWT request with the TWT parameters indicated by the TWT requesting STA; e.g. field set to 4), alternate TWT (the TWT responding STA suggests TWT parameters that are different than the parameters suggested or demanded by the TWT requesting STA; e.g., field set to 5), dictate TWT (the TWT responding STA demands TWT parameters that are different than the parameters suggested or demanded by the TWT requesting STA; e.g., field set to 6), or reject TWT (the TWT responding STA rejects the TWT setup; e.g. field set to 7).
[0075] In a TWT response, the TWT command may also indicate an unsolicited response or a broadcast TWT. An unsolicited TWT response is an individually addressed frame that is intended for a specific STA. An unsolicited TWT response may be followed by an ACK frame from the STA receiving the unsolicited TWT response. A broadcast TWT may be intended for multiple STAs and may be carried in a broadcast frame such as, for example, a beacon frame. A broadcast TWT may not be acknowledged by receiving STAs.
[0076] An unsolicited TWT response may be used a TWT responding STA to demand that a recipient follow a TWT schedule contained in the TWT element. In an embodiment, an unsolicited TWT response may have the TWT request field set to 0 and a value of ‘dictate TWT’ in the TWT setup command field. A broadcast TWT response may be used by a TWT responding STA to schedule a TWT for any STA that receives and decodes the TWT element.
[0077] In certain embodiments, a TWT element, such as TWT element 500, may contain TWT parameter sets for multiple TWT negotiations or indications as described herein. As such, the TWT element may include multiple instances of the Control and the TWT parameter information fields. The TWT flow identifier of the request type field indicates the TWT negotiation which parameters are carried by the TWT parameter information field.
[0078] FIG.6 illustrates an example target wake time (TWT) element 600 which may be used to support restricted TWT (r-TWT) operation. For r-TWT, TWT element 600 may be transmitted in a broadcast management frame, which can be a beacon frame, a TIM broadcast frame, a probe response frame, etc. In this embodiment, TWT element 600 provides nonnegotiated TWT schedules (e.g., broadcast TWT schedules).
[0079] As shown, TWT element 600 includes an element ID field, a length field, a control field, and a TWT parameter information field.
[0080] The element ID field (e.g., 1 octet in length) may indicate that information element 600 is a TWT element. The length field (e.g., 1 octet) may indicate the length of TWT element 600 starting from the control field until an end of TWT element 600. The end of TWT element 600 may be the end of a broadcast TWT info field or the end of a r-TWT traffic info field of the TWT parameter information field.Docket No.: 25-3025PCT
[0081] The TWT parameter information field may include a request type field, a target wake time field (e.g., 2 octets), a nominal minimal TWT wake duration field (e.g., 1 octet), a TWT wake interval mantissa (e.g., 2 octets), a broadcast TWT info field (e.g., 2 octets), and an optional r-TWT traffic info field (e.g., 0 or 3 octets)
[0082] The request type field may include, among other fields, a TWT request field, a flow type field, and a TWT wake interval exponent field.
[0083] The TWT request field indicates whether TWT element 600 is a request. If the TWT request field has a value of 0, then TWT element 600 may represent a response to a request to initiate TWT scheduling / setup (solicit TWT), an unsolicited TWT response, and / or a broadcast TWT message.
[0084] The TWT wake interval represents the average time that a TWT requesting STA or a TWT scheduled STA expects to elapse between successive TWT SP start times of a TWT schedule. The TWT wake interval exponent field indicates a (base 2) exponent used to calculate the TWT wake interval in microseconds. In an embodiment, the TWT wake interval is equal to: (TWT wake interval mantissa) x 2(™TWake |n|erva|The TVVTwakeinterval mantissa value is indicated in microseconds, base 2 in a TWT wake interval mantissa field of the TWT parameter information field.
[0085] The nominal minimum TWT wake duration field may indicate the minimum amount of time (in the unit indicated by a wake duration unit subfield of the control field) that a TWT requesting STA or a TWT scheduled STA is expected to be awake to complete frame exchanges for the period of the TWT wake interval.
[0086] The flow type field, in a TWT response that successfully set up a TWT agreement between a TWT requesting STA and a TWT responding STA, may indicate a type of interaction between the TWT requesting STA and the TWT responding STA within a TWT SP of the TWT agreement. A flow type field equal to 0 may indicate an announced TWT. In an announced TWT, the TWT responding STA may not transmit a frame to the TWT requesting STA within a TWT SP until the TWT responding STA receives a PS-Poll frame or a QoS Null frame from the TWT requesting STA. A flow type field equal to 1 may indicate an unannounced TWT. In an unannounced TWT, the TWT responding STA may transmit a frame to the TWT requesting STA within a TWT SP before it has received a frame from the TWT requesting STA.
[0087] Within a TWT element that includes a TWT setup command value of ‘request TWT’, ‘suggest TWT’, or ‘demand TWT’, a broadcast TWT ID may indicate a specific broadcast TWT in which the TWT requesting STA is requesting to participate. Within a TWT element that includes a TWT setup command value of ‘accept TWT, ‘alternate TWT', ‘dictate TWT', or 'reject TWT’, a broadcast TWT ID may indicate a specific broadcast TWT for which the TWT responding STA is providing TWT parameters. The value 0 in the broadcast TWT ID subfield may indicate the broadcast TWT whose membership corresponds to all STAs that are members of the BSS corresponding to the BSSID of the management frame carrying the TWT element and that is permitted to contain trigger frames with random access resource units for unassociated STAs. The Broadcast TWT ID subfield in a r-TWT Parameter set field is always set to a nonzero value.
[0088] A broadcast TWT element 600 that contains a r-TWT parameter set is also referred to as a r-TWT element. A r-TWT traffic info present subfield of the broadcast TWT info field may be set to 1 to indicate the presence of the r-TWT traffic info field in TWT element 600. The r-TWT traffic info field is present in a r-TWT parameter set field when the r-TWT traffic info present subfield is set to 1.Docket No.: 25-3025PCT
[0089] The r-TWT traffic info field may include a traffic info control field, a r-TWT DL TID bitmap field, and a r-TWT UL TID bitmap field.
[0090] The traffic info control field may include a DL TID bitmap valid subfield and an UL TID bitmap valid subfield. The DL TID bitmap valid subfield indicates if the r-TWT DL TID bitmap field has valid information. When the value of the DL TID bitmap valid subfield is set to 0, it may indicate that DL traffic of TIDs is identified as latency sensitive traffic, and the r-TWT DL TID bitmap field is reserved. The UL TID bitmap valid subfield may indicate if the r-TWT UL TID bitmap field has valid information. When the value of the UL TID bitmap valid subfield is set to 0, it may indicate that UL traffic of TIDs is identified as latency sensitive traffic, and the r-TWT UL TID bitmap field is reserved.
[0091] The r-TWT DL TID bitmap subfield and the r-TWT UL TID bitmap subfield may specify which TID(s) are identified by the TWT scheduling AP or the TWT scheduled STA as latency sensitive traffic streams in a downlink and a uplink direction, respectively. A value of 1 at bit position k in the bitmap indicates that TID k is classified as a latency sensitive traffic stream. A value of 0 at bit position k in the bitmap indicates that TID k is not classified as a latency sensitive traffic stream.
[0092] An individual target wake time (TWT) may be a specific time or set of times negotiated between two individual stations (e.g . , a STA and another STA, or a STA and an AP, etc.) at which the stations may be awake to exchange frames during a service period (SP) of the TWT.
[0093] In trigger-enabled TWT, an AP may transmit a trigger frame for scheduling uplink multi-user transmissions from one or more STAs using uplink OFDMA (orthogonal frequency division multiple access) and / or uplink MU-MIMO (multiuser multiple input multiple output) during a trigger-enabled TWT SP. A TWT STA that receives the trigger frame from the AP may transmit a frame to the AP through a resource indicated in the trigger frame during the trigger-enabled TWT SP.
[0094] In non-trigger-enabled TWT, an AP may not be required to transmit a trigger frame to schedule uplink multi-user transmissions from one or more STAs during a non-trigger-enabled TWT SP.
[0095] In announced TWT, a STA may transmit a frame (e.g. , a PS-Poll frame or a QoS null frame) to the AP to retrieve a downlink buffered data from the AP during a TWT SP. In unannounced TWT, an AP may transmit downlink data to a TWT STA without receiving a frame (e.g., a PS-Poll frame, or a QoS null frame) from the TWT STA during a TWT SP.
[0096] FIG. 7 illustrates an example 700 of individual TWT operation. As shown in FIG.7, example 700 includes an AP 710, a STA 711 , and a STA 712. In an example, AP 710 may be a TWT responding STA and STA 711 and STA 712 may be TWT requesting STAs.
[0097] In an example, STA 711 may transmit a TWT request to AP 710 to setup a first trigger-enabled TWT agreement. STA 711 may set a trigger field of the TWT request to 1 to indicate that it is requesting a trigger-enabled TWT. AP 710 may accept the first TWT agreement with STA 711. AP710 may confirm the acceptance in a TWT response sent to STA 711. The TWT response may indicate a next TWT 730, which indicates the time until a next TWT SP 720 according to the first TWT agreement.Docket No.: 25-3025PCT
[0098] In an example, AP 710 may transmit an unsolicited TWT response to STA 712 to set up a second trigger-enabled TWT agreement with STA 712 without receiving a TWT request from STA 712. The first and second TWT agreements may be set up as announced TWTs.
[0099] After the setup of the TWT agreements, STA 711 and STA 712 may enter a doze state until the start of TWT SP 720. During trigger-enabled TWT SP 720, AP710 may transmit a trigger frame. STA 711 and STA 12 may respond to the trigger frame by indicating that they are in awake state. In an example, STA 711 may transmit a power save poll (PS-Poll) frame. The PS-Poll frame may comprise a BSSID (receiver address: RA) field set to an address of AP 710 and a transmitter address (TA) field set to an address of STA 711. In an example, STA 712 may transmit a QoS null frame in response to the trigger frame. The QoS null frame may comprise a MAC header (e.g., a frame control field, a duration field, address fields, a sequence control field, QoS control field) without a frame body.
[0100] In response to the PS-Poll frame and the QoS null frame, AP 710 may transmit a multi-STA Block Ack (M-BA) frame. The M-BA frame may include acknowledgement information associated with the PS-Poll frame and the QoS null frame received from STAs 711 and 712 respectively. Subsequently, STA 711 and STA 712 may receive downlink bufferable units (DL BUs) from AP 710. The DL BUs may include a medium access control (MAC) service data unit (MSDU), an aggregate MAC service data unit (A-MSDU), and / or a bufferable MAC management protocol data unit (MMPDU). STA 711 and STA 712 may transmit Block Ack (BA) frames in response to the DL BUs. At the end of the TWT SP 720, STA 711 and STA 712 may return to a doze state.
[0101] A STA may execute individual TWT setup exchanges. The STA may not transmit frames to an AP outside of negotiated TWT SPs. The STA may not transmit frames that are not contained within high efficiency trigger-based physical protocol data units (HE TB PPDUs) to the AP within trigger-enabled TWT SPs. A HE TB PPDU may be transmitted by a STA based on receiving a trigger frame triggering uplink multi-user transmissions.
[0102] The AP of a trigger-enabled TWT agreement may schedule for transmission a trigger frame for a STA within the trigger-enabled TWT SP. The STA may transmit an HE TB PPDU as a response to the trigger frame sent during the trigger-enabled TWT SP. A STA that is in power save (PS) mode may include a PS-Poll frame or a QoS null frame in the HE TB PPDU if the TWT is an announced TWT, to indicate to the AP that the STA is currently in the awake state. The AP that receives the PS-Poll frame or the QoS Null frame or any other indication from an STA in PS mode, may deliver to the STA as many buffered BUs as are available at the AP during the TWT SP.
[0103] A broadcast target wake time (TWT) may be a specific time or set of times broadcast by an AP to one or more STAs at which the STAs may be awake to exchange frames with the AP during a SP of the TWT.
[0104] FIG. 8 illustrates an example 800 of broadcast TWT operation. As shown in FIG. 8, example 800 includes an AP 810, a STA 811, and a STA 812. In an example 800, AP 810 maybe a TWT scheduling AP and STA 811 and STA 812 may be TWT scheduled STAs.
[0105] In an example, AP 810 may include a broadcast TWT element in a beacon frame that indicates a broadcast TWT SP 820. During the broadcast TWT SP 820, AP 810 may transmit trigger frames or DL BUs to STA 811 and STADocket No.: 25-3025PCT812. Beacon frames may be sent by AP 810 periodically at target beacon transmission times (TBTTs). The number of time units (TUs) between consecutive TBTTs is called the beacon interval. A TU is equal to 1024 microseconds.
[0106] In an example, STA 811 and STA 812 may enter a doze state until the first target beacon transmission time (TBTT). STA 811 and STA 812 may wake up to receive the beacon frame at the first TBTT to determine the broadcast TWT. Upon reception of a broadcast TWT element in a beacon frame, STA 811 and STA 812 may re-enter the doze state until the start of trigger-enabled TWT SP 820.
[0107] During trigger-enabled TWT SP 820, AP 810 may transmit a basic trigger frame to STA 811 and STA 812. STA 811 may indicate that it is awake by transmitting a PS-Poll, and STA 812 may indicate that it is awake by transmitting a QoS null frame in response to the basic trigger frame. Subsequently, STA 811 and STA 812 may receive DL BUs from AP 810. STA 811 and STA 812 may return to the doze state outside of the TWT SP 720.
[0108] In an example, a STA that intends to operate in power save mode may negotiate a wake TBTT and a wake interval with the AP. For example, as shown in FIG.8, STA 811 may transmit a TWT request to AP 810 that identifies a wake TBTT of the first beacon frame and a wake interval between subsequent beacon frames. AP 810 may respond with a TWT response to the TWT request confirming the wake TBTT and wake interval. After successfully completing the negotiation, STA 811 may enter a doze state until a first negotiated wake TBTT 830. STA 811 may be in an awake state to listen to the beacon frame transmitted at first negotiated wake TBTT 830. If STA 811 receives a beacon frame from AP 810 at or after TBTT 830, STA 811 may return to the doze state until the next wake TBTT unless a traffic indication map (TIM) element in a beacon frame includes a positive indication for STA 811. The STA 811 may return to the doze state after a nominal minimum TBTT wake duration time has elapsed from the TBTT start time.
[0109] A Network Allocation Vector (NAV) is an indicator, maintained by a station (STA), of time periods when transmission onto the wireless medium (WM) may not be initiated by the STA regardless of whether the clear channel assessment (CCA) function of the STA senses that the WM is busy. A STA that receives at least one valid frame in a PSDU may update its NAV with the information from any valid duration field in the PSDU. The STA may update the NAV when a value of the received duration field is greater than the current NAV value of the STA.
[0110] A TWT protection is a mechanism employed to protect a TWT session from external STA transmissions. During a TWT SP configured to protect the TWT session, a STA that initiates a transmission opportunity (TXOP) to transmit a frame may transmit a request to transmit (RTS) frame or a clear to transmit (CTS) frame to protect the TWT session by setting the NAV of other STAs based on receiving of the RTS frame and / or the CTS frame. The RTS frame may comprise a frame control field, a duration field, a receiver address (RA) field, a transmitter address (TA) field, and a frame check sequence (FCS) field. The CTS frame may comprise a frame control field, a duration field, a receiver address (RA) field, and a frame check sequence (FCS) field.
[0111] The TWT protection field in a TWT element may indicate whether a TWT is protected or unprotected. A TWT requesting STA may set the TWT protection field to 1 to request the TWT responding STA to provide protection for the set of TWT SPs. A TWT protection field equal to 1 may indicate to use a NAV protection mechanism to protect access to the medium during the corresponding TWT SPs.Docket No.: 25-3025PCT
[0112] FIG. 9 illustrates an example 900 of TWT protection in individual TWT operation. As shown in FIG. 9, example 900 includes an AP 910 and a STA 911.
[0113] In an example, AP 910 may set the TWT protection field to 1 in a TWT response frame to protect the TWT SPs using a NAV protection mechanism. Upon reception of the TWT response frame, STA 911 may enter a doze state until the next TWT 930. AP 910 that has set the TWT protection field to 1 may transmit a NAV setting frame at the start of the TWT SP 920. For example, the NAV setting frame may be an RTS frame or a CTS frame.
[0114] A STA that receives the NV setting frame and that is not scheduled to access the medium during the TWT SP 920 may set their NAV according to the NAV setting frame. The STA may not access the medium for the specified amount of time in the NAV setting frame.
[0115] STA 911 may be scheduled to access the medium during the TWT SP 920. STA 911 may respond to the RTS frame with a CTS frame. Upon receiving the CTS frame, AP 910 may transmit a downlink frame to STA 911. STA 911 may respond to the downlink frame with a BA frame. When the TWT SP 920 ends, STA 911 may return to the doze state.
[0116] FIG. 10 illustrates an example multi-AP network 1000. Example multi-AP network 1000 may be a multi-AP network in accordance with the Wi-Fi Alliance standard specification for multi-AP networks. As shown in FIG. 10, multi-AP network 1000 may include a multi-AP controller 1002 and a plurality of multi-AP groups (or multi-AP sets) 1004, 1006, and 1008.
[0117] Multi-AP controller 1002 may be a logical entity that implements logic for controlling the APs in multi-AP network 1000. Multi-AP controller 1002 may receive capability information and measurements from the APs and may trigger AP control commands and operations on the APs. Multi-AP controller 1002 may also provide onboarding functionality to onboard and provision APs onto multi-AP network 1000.
[0118] Multi-AP groups 1004, 1006, and 1008 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.
[0119] 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 aDocket No.: 25-3025PCTbeacon 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.
[0120] 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 1002 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.
[0121] In one approach, APs in a multi-AP group may perform coordinated transmissions together. One aspect of coordination may include coordination to perform coordinated transmissions within the multi-AP group. As used herein, a coordinated transmission, also referred to as a multi-AP transmission, is a transmission event in which multiple APs (of a multi-AP group ora multi-AP network) transmit in a coordinated manner over a time period. Coordinated transmissions may involve simultaneous transmissions of a plurality of APs in a multi-AP group. The time period of simultaneous AP transmission may be a continuous period. The multi-AP transmission may use different transmission techniques, such as Coordinated OFDMA (COFDMA), Coordinated Spatial Reuse (CSR), Joint Transmission or Reception (JT / JR), Coordinated Beamforming (CBF), and CTDMA, or a combination of two or more of the aforementioned techniques.
[0122] 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.
[0123] 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.
[0124] 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 dataDocket No.: 25-3025PCTexchanged 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 reception (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.
[0125] 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.
[0126] 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.
[0127] 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.
[0128] 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.
[0129] FIG. 11 illustrates an example 1100 of a multi-AP negotiation procedure, followed by a multi-AP termination procedure. As shown in FIG. 11, example 1100 may include an AP 1102, an AP 1104, and an AP 1106. In an example,Docket No.: 25-3025PCTthe multi-AP negotiation procedure may begin with a multi-AP discovery phase, in which AP 1102 transmits a frame 1108 to APs 1104 and 1106. In an example, frame 1108 polls APs 1104 and 1106 regarding joining a multi-AP group with AP 1102. In an example, frame 1108 may further indicate that r-TWT operation parameters will be negotiated in the multi-AP group. Frame 1108 may be a broadcast or multicast frame. APs 1104 and 1106 may respond to frame 1108 by transmitting toAP 1102 a frame 1110 and a frame 1112, respectively. For example, frames 1110 and 1112 may indicate acceptance or rejection by APs 1104 and 1106, respectively, of joining the multi-AP group with AP 1102. In an example, AP 1102 may be referred to as a coordinating AP, and APs 1104 and 1106 may be referred to as coordinated APs.
[0130] Subsequently, the multi-AP negotiation procedure may proceed to the multi-AP r-TWT negotiation phase, in which AP 1102 negotiates r-TWT operation parameters with APs 1104 and 1106. In an implementation, the objective of the multi-AP r-TWT negotiation phase is to reduce interference among APs 1102, 1104, and 1106 during r-TWT operation by, for example, ensuring that APs 1104 and 1106 extend protection to an r-TWT schedule of AP 1102. In an example, the r-TWT schedule may comprise periodic SPs for one or more STAs associated with AP 1102. The SPs may be used for low latency traffic communication between AP 1102 and the one or more STA associated with AP 1102. In an example, AP 1104 or AP 1106 extends protection to the r-TWT schedule of AP 1102 by terminating / ending an obtained TXOP before a start time of a SP of the r-TWT schedule of the AP 1102. In an example, AP 1102 may determine the r-TWT schedule for itself.
[0131] Subsequently, as shown, AP 1102 may transmit a frame 1114 to AP 1104. In an example, frame 1114 requests that AP 1104, itself, extend protection to the r-TWT schedule, but may not request that STAs associated with AP 1104 also extend protection to the r-TWT schedule. In another example, frame 1114 may request that AP 1104 and one or more of its associated STAs (e.g., all associated STAs or any subset of associated STAs) extend protection to the r-TWT schedule. Upon receiving frame 1114, AP 1104 may transmit a frame 1116 to AP 1102. For example, frame 1116 may indicate acceptance or rejection, by AP 1104, of the request to extend protection to the r-TWT schedule. APs 1102 and 1104 may exchange additional frames (not shown in FIG. 11) until agreement is reached on extending protection to the r-TWT schedule by AP 1104. In example 1100, it is assumed that AP 1104 accepts the request to extend protection to the r-TWT schedule indicated in frame 1114.
[0132] Subsequently, AP 1102 may transmit a frame 1118 to AP 1106. In an example, frame 1118 requests that AP 1106, itself, extend protection to the r-TWT schedule, but may not request that STAs associated with AP 1106 also extend protection to the r-TWT schedule. In another example, frame 1118 may request that AP 1106 and one or more of its associated STAs (e.g., all associated STAs or any subset of associated STAs) extend protection to the r-TWT schedule. Upon receiving frame 1118, AP 1106 may transmit a frame 1120 to AP 1102. For example, frame 1120 may indicate acceptance or rejection, byAP 1106, of the request to extend protection to the r-TWT schedule. APs 1102 and 1106 may exchange additional frames (not shown in FIG. 11) until agreement is reached on extending protection to the r-TWT schedule by AP 1106. In example 1100, it is assumed that AP 1106 accepts the request to extend protection to the r-TWT schedule in frame 1118. Thus, the multi-AP r-TWT negotiation phase ends with frame 1120.Docket No.: 25-3025PCT
[0133] Subsequently, as shown, the multi-AP termination procedure may begin with the multi-AP agreement tear down. In an example, AP 1102 may transmit a frame 1122 to AP 1104. In an example, frame 1122 may indicate termination of the r-TWT schedule agreement between AP 1102 and AP 1104. Upon receiving frame 1122, AP 1104 may transmit a frame 1124 to AP 1102. In an example, frame 1124 may indicate to AP 1102 an acknowledgment of reception of frame 1122 by AP 1104. In an example, upon transmitting frame 1124, AP 1104 stops extending protection to the r-TWT schedule.
[0134] Subsequently, as shown, AP 1102 may transmit a frame 1126 to AP 1106. In an example, frame 1126 may indicate termination of the r-TWT schedule agreement between AP 1102 and AP 1106. Upon receiving frame 1126, AP 1106 may transmit a frame 1128 to AP 1102. In an example, frame 1128 may indicate to AP 1102 an acknowledgment of reception of frame 1126 by AP 1106. In an example, upon transmitting frame 1128, AP 1106 stops extending protection to the r-TWT schedule.
[0135] FIG. 12 illustrates an example 1200 of a problem that may arise with a coordinated r-TWT operation. As shown in FIG. 12, example 1200 includes an AP 1202, a STA 1204, an AP 1206, and a STA 1208. In an example, STA 1204 may be associated with AP 1202, and STA 1208 may be associated with AP 1206. In an example, AP 1202 may set up an r-TWT schedule for STA 1204. The r-TWT schedule may comprise an r-TWT SP 1218 and an r-TWT SP 1230. In an example, AP 1202 and AP 1206 undertake a multi-AP negotiation procedure for coordinated r-TWT operation, as discussed above for example 1100 illustrated in FIG. 11. For example, AP 1202 may be a coordinating AP and may correspond to AP 1102 described for example 1100, while AP 1206 may be a coordinated AP and may correspond to AP 1104 described for example 1100. In the multi-AP negotiation procedure, AP 1202 may request that AP 1206 (and, potentially, one or more STAs associated with AP 1206) extend protection to the r-TWT schedule. As mentioned above, when AP 1206 and / or one or more STAs associated therewith extend protection to the r-TWT schedule, AP 1206 and / or the one or more STAs associated therewith terminate / end an obtained TXOP before a start time of a SP of the r-TWT schedule.
[0136] Example 1200 may begin with AP 1202 and AP 1206 establishing a Co-RTWT agreement as described above in example 1100 illustrated in FIG. 11. STA 1208 may transmit a frame 1210 to AP 1206 during a TXOP 1212 that does not overlap with the beginning of the r-TWT SP 1218. Subsequently, STA 1204 may transmit a low latency frame 1214 to AP 1202 during the r-TWT SP 1218.
[0137] In an example, AP 1202 may become temporarily out of range of AP 1206 after r-TWT SP 1218. As illustrated, AP 1202 may transmit a frame 1222 to STA 1204, after AP 1202 has become temporarily out of range of AP 1206. In an example, frame 1222 maybe a beacon frame. AP 1206 may not receive frame 1222 (e.g., because AP 1206 has become out of range of AP 1202).
[0138] Based on not receiving frame 1222, AP 1206 may decide to stop extending protection to the r-TWT of AP 1202, because AP 1206 may assume that AP 1202 is no longer active. AP 1206 may do this to avoid impact on its own intra-BSS transmissions. For example, AP 1202 and AP 1206 may become out of range from each other (e.g., AP 1202 and AP 1206 may not hear each other's transmissions), either permanently or temporarily. As one example, AP 1202 mayDocket No.: 25-3025PCThave a failure or become inoperative, so that AP 1206 permanently does not receive any communications from AP 1202. As another example, changes in the environment, such as strong multipath fading, interference, or jamming, may lead to AP 1206 temporarily not receiving any communications from AP 1202.
[0139] AP 1206 and its associated STAs, however, may still extend protection to the r-TWT schedule of AP 1202, unless the r-TWT session is torn down (e.g., as described above in example 1100 illustrated in FIG. 11). Thus, AP 1206 may continue extending protection for an r-TWT schedule that no longer exists (e.g., because AP 1202 is not operating) and which no longer needs protection. This can make operation of AP 1206 and its associated STAs inefficient as they unnecessarily finish their acquired TXOP(s) early to avoid overlap with the beginning of the r-TWT SP.
[0140] To mitigate this problem, AP 1206 may stop extending protection to the r-TWT schedule of AP 1202 based on not receiving any transmissions from AP 1202 for a duration of time, under the assumption that AP 1202 is therefore no longer in range of AP 1206 (or AP 1202 is no longer active). But this can cause additional issues, if AP 1202 is still operating and AP 1206 is just not receiving transmissions from AP 1202 (e.g., temporarily). In an example, some STAs associated with AP 1206 may be in range of AP 1202 and receive transmissions from AP 1202. Thus, if AP 1206 tears down the r-TWT session and stops following the r-TWT, as described above, STAs associated with AP 1206 may interfere with transmissions of AP 1202 during r-TWT operation, causing time critical traffic served during the r-TWT SP to be delayed.
[0141] Example 1200 illustrates an example scenario. As illustrated, AP 1206 stops extending protection to the r-TWT schedule of AP 1202 and transmits a frame 1224 to STA 1208 to indicate that STA 1208 does not have to extend protection to the r-TWT schedule of AP 1202. In an embodiment, frame 1224 may be a beacon frame. STA 1208 may receive frame 1224 and may stop extending protection to the r-TWT schedule of AP 1202.
[0142] In an example, however, STA 1208 may be in range of AP 1202, even though AP 1206 is out of range of AP 1202 (e.g., STA 1208 may receive frame 1222, even though AP 1206 did not receive frame 1222). Thus, transmissions by STA 1208 may potentially impact transmissions for AP 1202 and its associated STAs, because STA 1208 no longer extends protection to the r-TWT schedule of AP 1202 (e.g., after receiving frame 1224 from AP 1206). For example, STA 1208 may acquire a TXOP 1236 overlapping with the beginning of r-TWT SP 1230. STA may transmit a frame 1226 to AP 1206. Upon receiving frame 1226, AP 1202 and STA 1204 may set their NAVs to non-zero NAV 1232 and non-zero NAV 1234 respectively. After the TXOP 1236 ends, STA 1204 gains channel access and transmit a low latency frame 1228 to AP 1202. However, frame 1228 is transmitted outside of r-TWT SP 1230 and consequently delayed. This may cause the packet to fail its latency requirement and reduce the QoS of the traffic it is associated with.
[0143] Embodiments of the present disclosure, as further described below, address the above-discussed problem of existing technologies. In an aspect, a first access point (AP) may receive froma second AP a first frame requesting that the first AP extend protection to a restricted target wake time (r-TWT) schedule of the second AP. In an example, the first AP transmits to the second AP a second frame indicating that the first AP extends protection to the r-TWT schedule of the second AP, wherein, based on extending protection to the r-TWT schedule, the first AP terminates / ends an obtained transmission opportunity (TXOP) before a start time of a service period (SP) of the r-TWT schedule. Based, on the firstDocket No.: 25-3025PCTAP not receiving any frame from the second AP within a first duration from a last received frame from the second AP, transmitting, by the first AP, a third frame that triggers one or more stations (STAs), associated with the first AP, to determine whether the one or more STAs receive a fourth frame from the second AP within a second duration from the one or more STAs receiving the third frame. In an embodiment, the first AP receives from the one or more STA one or more fifth frames in response to the third frame, and the first AP stops extending protection to the r-TWT schedule of the second AP based on the one or more fifth frames indicating that the one or more STAs do not receive the fourth frame from the second AP within the second duration, and the first AP not receiving any frame from the second AP within the second duration.
[0144] In another embodiment, a STA may receive from a first AP with which the STA is associated, a first frame advertising that the first AP extends protection to a restricted target wake time (r-TWT) schedule of a second AP, wherein, based on extending protection to the r-TWT schedule, the STA terminates / ends an obtained transmission opportunity (TXOP) before a start time of a service period (SP) of the r-TWT schedule. In an embodiment, the STA may receive a second frame from the first AP. In an example, the STA may determine based on receiving the second frame, whether the STA receives a third frame from the second AP within a duration from the STA receiving the second frame. In an embodiment, the STA may transmit to the first AP a fourth frame indicating that the STA does not receive the third frame from the second AP within the duration.
[0145] One or more aspects of disclosed embodiments may improve communication efficiency. For example, one or more aspects of disclosed embodiments may improve communication reliability for coordinated r-TWT operation. For example, one or more embodiments may improve detection when a coordinated AP is out of range of a coordinated AP but it is still operating. This may allow STAs associated with the coordinated AP to keep extending protection to an r-TWT schedule of the coordinating AP, avoiding unexpected transmissions during the r-TWT service periods and improving communication efficiency.
[0146] FIG. 13 illustrates an example 1300 of a procedure according to an embodiment. In an embodiment, the procedure illustrated in example 1300 may facilitate coordinated r-TWT (Co-RTWT) operation, as described further below. Example 1300 is provided for the purpose of illustration only and is not limiting of embodiments of the present disclosure. As shown in FIG. 13, example 1300 may include an AP 1302, a STA 1304, an AP 1306, and a STA 1308. In an embodiment, any, or all, of AP 1302, STA 1304, AP 1306, and STA 1308 may be a multi-link device (MLD), that is a device capable of operating over multiple links as defined by the IEEE 802.11 standard. In an example, STA 1304 may be associated with AP 1302, and STA 1308 may be associated with AP 1306. In an embodiment, APs 1302 and 1306 may form a multi-AP group. AP 1302 may be a coordinating AP of the multi-AP group, and AP 1306 may be a coordinated AP of the multi-AP group. In an embodiment, AP 1302 and AP 1306 may be configured to schedule their own r-TWT schedules by default and may support reconfiguration of their respective r-TWT schedules during a multi-AP r-TWT negotiation phase, as described in relation to FIG. 11 above. In an embodiment, AP 1302 may set up an r-TWT schedule for STA 1304.Docket No.: 25-3025PCT
[0147] Example 1300 may begin with AP 1302 and AP 1306 undergoing a multi-AP negotiation procedure as described in example 1100 illustrated in FIG. 11 (not shown in FIG. 13). During the negotiations, AP 1302 may request that AP 1306 extend protection to an r-TWT schedule of AP 1302. After reaching an agreement (e.g., a Co-RTWT agreement), AP 1306 and STA 1308 may start extending protection to the r-TWT schedule for AP 1302.
[0148] Additionally, AP 1302 and AP 1306 may agree (e.g., during the multi-AP negotiations described in example 1100 illustrated in FIG. 11) on a duration 1314 during which, if AP 1306 does not receive any transmissions from AP 1302, AP 1306 considers AP 1302 out of its coverage area and AP 1306 may stop extending protection to the r-TWT schedule of AP 1302. For example, AP 1302 may transmit duration 1314 to AP 1306. As another example, AP 1306 may transmit duration 1314 to AP 1302. In another embodiment, the duration 1314 is pre-defined. For example, as discussed above, AP 1306 may stop extending protection to an r-TWT schedule of AP 1302 when AP 1302 is out of range (or inactive) and AP 1306 does not receive transmissions from AP 1302. Assuming AP 1302 is also out of range of AP 1306 (eg., assuming AP 1302 does not receive transmissions from AP 1306), transmissions from AP 1306 may not interfere with AP 1302 during the r-TWT SP. Hence, AP 1306 may stop extending protection to the r-TWT schedule to improve efficiency in its intra-BSS transmissions without affecting AP 1302.
[0149] For example, AP 1306 may not receive a beacon frame, or multiple beacon frames (e.g., multiple consecutive beacon frames), from AP 1302 within an expected duration (e.g., duration 1314). In an embodiment, AP 1306 may identify a duration during which it expects to receive one or more beacon frames from AP 1302. For example, AP 1306 may estimate a TBTT for AP 1302 (e.g., based on one or more received beacons from AP 1302) and may identify duration 1314 based on the estimated TBTT. AP 1306 may not receive a beacon frame, or multiple beacon frames (e.g., multiple consecutive beacon frames), from AP 1302 within duration 1314 (e.g., AP 1302 maybe out of range of AP 1306 orAP 1302 may be inactive). Based on AP 1306 not receiving a beacon frame or multiple beacon frames (e.g., multiple consecutive beacon frames), from AP 1302 within duration 1314, AP 1306 may stop extending protection to an r-TWT schedule of AP 1302. In an embodiment, duration 1314 may begin from a last received frame (e.g., a last received beacon frame, not illustrated), from AP 1302, received by AP 1306.
[0150] In an embodiment, as illustrated, AP 1302 may become out of range of AP 1306, prior to duration 1314. AP 1302 may transmit a frame 1312 to STA 1304. AP 1306 may not receive frame 1312 (e.g., because AP 1302 is out of range of AP 1306). Based on AP 1306 not receiving frame 1312 from AP 1302 within a duration 1314 from a last received frame (not shown in FIG. 13), AP 1306 may transmit a frame 1316 to STA 1308. Frame 1316 indicates a request for STA 1308 to monitor reception of a frame within a duration 1318 from STA 1308 receiving frame 1316. In an embodiment, frame 1316 may be an individually addressed control frame. In another embodiment, frame 1316 may be a broadcast / multicast frame.
[0151] In an embodiment, AP 1302 shuts down after frame 1316 is transmitted as shown in FIG. 13. STA 1308 may monitor for any transmitted frame by AP 1302 for a duration 1318 (e.g., based on receiving frame 1316 from AP 1306). In an embodiment, AP 1306 transmits a frame 1320 to STA 1308 indicating a request to STA 1308 to indicate whether STA 1308 has received any frame from AP 1302 in the duration 1318. Duration 1318 maybe negotiated or may be preDocket No.: 25-3025PCTdefined. For example, duration 1318 maybe negotiated (e.g., exchanged) between AP 1302 andAP 1306 (e.g., during the multi-AP negotiations described in example 1100 illustrated in FIG. 11). For example, AP 1302 may transmit duration 1318 to AP 1306. As another example, AP 1306 may transmit duration 1318 to AP 1302. As another example, duration 1318 maybe negotiated (e.g., exchanged) between AP 1306 and STA 1308. For example, AP 1306 may transmit duration 1318 to STA 1308, and / or STA 1308 may transmit duration 1318 to AP 1306. As another example, duration 1318 may be pre-defined (e.g., without negotiation).
[0152] In an embodiment, since AP 1302 is down, both AP 1302 and STA 1308 do not receive any transmissions from AP 1302 for duration 1318. Thus, upon reception of frame 1320, STA 1308 may transmit a frame 1322 indicating that STA 1308 has not received any frames / transmissions from AP 1302 (e.g., during duration 1318). In an embodiment, frame 1322 is an individually addressed control frame. In another embodiment, frame 1322 is a broadcast or multicast frame.
[0153] In an embodiment, based on frame 1322, AP 1306 stops extending protection to the r-TWT schedule of AP 1302. For example, based on frame 1322 indicating that STA 1308 did not receive any frames / transmissions from AP 1302 during duration 1318, AP 1306 may stop extending protection to the r-TWT schedule of AP 1302. In an embodiment, AP 1306 transmits frame 1324 to STA 1308. Frame 1324 may indicate to STA 1308 to stop extending protection to the r-TWT schedule of AP 1302. In an embodiment, frame 1324 may be a beacon frame.
[0154] In one embodiment, as described above, AP 1306 stops extending protection to the r-TWT schedule of AP 1302 based on receiving an indication from one associated STA (e.g., STA 1308) that the STA did not receive transmissions from AP 1302 (e.g., during duration 1318). In another embodiment, AP 1306 stops extending protection to the r-TWT schedule of AP 1302 based on receiving indications from multiple associated STAs (e.g., all STAs associated with AP 1302) that each of the multiple STAs has not received transmissions from AP 1302 (e.g., during duration 1318).
[0155] For example, another STA (not shown in FIG. 13) may also be associated with AP 1306. In an embodiment, AP 1306 may receive a frame from this other STA, indicating that the other STA does not receive any frame from AP 1302 for a duration 1318. In an embodiment, STA 1308 and the other STA comprise all the STAs associated with AP 1306. In an embodiment, based on frame 1322 and the frame from the other STA, AP 1306 stops extending protection to the r-TWT schedule of AP 1302. In an embodiment, AP 1306 stops extending protection to the r-TWT schedule of AP 1302 based on all STAs associated with AP 1306 not receiving any frames from AP 1302 during a given duration (e.g., a duration occurring while AP 1306 extends protection to the r-TWT schedule of AP 1302).
[0156] FIG. 14 illustrates an example 1400 of a procedure according to an embodiment. In an embodiment, the procedure illustrated in example 1400 may facilitate Co-RTWT operation, as described further below. Example 1400 is provided for the purpose of illustration only and is not limiting of embodiments of the present disclosure. As shown in FIG.14, example 1400 may include an AP 1402, a STA 1404, an AP 1406, and a STA 1408. In an embodiment, any, or all, of AP 1402, STA 1404, AP 1406, and STA 1408 may be an MLD. In an example, STA 1404 may be associated with AP 1402, and STA 1408 may be associated with AP 1406. In an embodiment, APs 1402 and 1406 may form a multi-AP group. AP 1402 may be a coordinating AP of the multi-AP group, and AP 1406 may be a coordinated AP of the multi-APDocket No.: 25-3025PCTgroup. In an embodiment, AP 1402 and AP 1406 may be configured to schedule their own r-TWT schedules by default and may support reconfiguration of their respective r-TWT schedules during a multi-AP r-TWT negotiation phase, as described in relation to FIG. 11 above In an embodiment, AP 1402 may set up an r-TWT schedule for STA 1404.
[0157] Example 1400 maybegin with AP 1402 andAP 1406 undergoing a multi-AP negotiation procedure as described in example 1100 illustrated in FIG. 11 (not shown in FIG. 14). During the negotiations, AP 1402 may request that AP 1406 extend protection for an r-TWT schedule of AP 1402. After reaching an agreement (e.g ., a Co-RTWT agreement), AP 1406 and STA 1408 may start extending protection to the r-TWT schedule for AP 1402.
[0158] In an example, AP 1402 may be out of range of AP 1406 for a duration 1412. Like duration 1314 described above for example 1300 illustrated in FIG. 13, duration 1412 may be negotiated (e.g., between AP 1402 and AP 1406, aspartof a multi-AP negotiation) or may be pre-defined. During duration 1412, AP 1402 may transmit a frame 1414 (e.g., to STA 1404 or as a broadcast frame). Since AP 1402 is out of range of AP 1406, AP 1406 may not receive frame 1414. After duration 1412 expires, AP 1406 may conclude that AP 1402 is out of range or inactive. In one embodiment, AP 1406 may stop extending protection to the r-TWT schedule of AP 1402 after duration 1412 expires.
[0159] Alternatively, instead of stopping extending protection for the r-TWT schedule of AP 1402 after duration 1412, AP 1406 may transmit a frame 1416 (e.g., to STA 1408) to request that STA 1408 report whether the STA 1408 receives any frame during a subsequent duration 1418. Like duration 1318 described above for example 1300 illustrated in FIG.13, duration 1418 may be negotiated (e.g., between any, or all, of AP 1402, AP 1406, and STA 1408) or may be predefined. In another embodiment, frame 1416 may indicate a request for STA 1408 to report if STA 1408 does not receive any frame during duration 1418 (e.g., a request for STA 1408 to report to AP 1406 only in the circumstance where STA 1408 does not receive any frame during duration 1418).
[0160] In an embodiment, frame 1416 may comprise an action frame. For example, frame 1416 may comprise a measurement request. In an embodiment, the measurement request may comprise a beacon request. In this embodiment, frame 1416 may be a broadcast or multicast frame. For example, frame 1416 may comprise a measurement request (e.g., a beacon request) further comprising an indication of duration 1418.
[0161] In an example, AP 1402 transmits a frame 1420 (e.g., to STA 1404 or as a broadcast frame) during duration 1418. Since AP 1402 is out of range of AP 1406, AP 1406 does not receive frame 1420. However, STA 1408 may be in the range of AP 1402 and may receive frame 1420. Upon receiving frame 1420, STA 1408 may transmit a frame 1422A (e.g., to AP 1406) during duration 1418. In another embodiment, STA 1408 may transmit a frame 1422B (e.g., to AP 1406) after duration 1418. In an embodiment STA 1408 transmits either frame 1422A (e.g., during duration 1418) or frame 1422B (e.g., after duration 1418) butSTA 1408 does not transmit both frame 1422A and frame 1422B. Either frame 1422A or frame 1422B may indicate that STA 1408 has received a frame from AP 1402 during duration 1418. In an embodiment, AP 1406 determines, based on receiving frame 1422A or 1422B, to continue extending protection to the r-TWT schedule of AP 1402.
[0162] In an embodiment, frame 1422A and / or frame 1422B may be a measurement report frame. For example, as discussed above, in an embodiment frame 1416 may comprise a measurement request (e.g., a beacon request). In thisDocket No.: 25-3025PCTexample, STA 1408 may respond to frame 1416 with a measurement report frame. The measurement report frame may be individually addressed (e.g., to AP 1406).
[0163] In an example, AP 1402 subsequently shuts down (e.g., after STA 1408 transmits frame 1422A or frame 1422B). In an embodiment, AP 1406 transmits frame 1424 to STA 1408. In an embodiment, frame 1424 may correspond to frame 1416, described above.
[0164] Upon receiving frame 1424, STA 1408 may monitor the reception of any frame from AP 1402 during a duration 1426. Like duration 1418 described above, duration 1426 may be negotiated (e.g., between any, or all, of AP 1402, AP 1406, and STA 1408) or may be pre-defined. Since AP 1402 is down, STA 1408 does not receive any transmission from AP 1402 during duration 1426. In an embodiment, STA 1408 transmits a frame 1428 to AP 1406 to indicate that no transmissions from AP 1402 have been received during duration 1426. In an embodiment, frame 1428 may correspond to frame 1422B, described above. Upon receiving frame 1428, AP 1406 may determine that AP 1402 is out of range of AP 1406 and STA 1408 (e.g., due to AP 1402 being down / inoperative), and AP 1406 may stop extending protection to the r-TWT schedule of AP 1402.
[0165] FIG. 15 illustrates an example 1500 of a procedure according to an embodiment. In an embodiment, the procedure illustrated in example 1500 may facilitate Co-RTWT operation, as described further below. Example 1500 is provided for the purpose of illustration only and is not limiting of embodiments of the present disclosure. As shown in FIG.15, example 1500 may include an AP 1502, a STA 1504, an AP 1506, and a STA 1508. In an embodiment, any, or all, of AP 1502, STA 1504, AP 1506, and STA 1508 may be an MLD. In an example, STA 1504 may be associated with AP 1502, and STA 1508 may be associated with AP 1506. In an embodiment, APs 1502 and 1506 may form a multi-AP group. AP 1502 may be a coordinating AP of the multi-AP group, and AP 1506 may be a coordinated AP of the multi-AP group. In an embodiment, AP 1502 and AP 1506 may be configured to schedule their own r-TWT schedules by default and may support reconfiguration of their respective r-TWT schedules during a multi-AP r-TWT negotiation phase, as described in relation to FIG. 11 above. In an embodiment, AP 1502 may set up an r-TWT schedule for STA 1504.
[0166] Example 1500 may begin with AP 1502 and AP 1506 undergoing a multi-AP negotiation procedure as described in example 1100 illustrated in FIG. 11 (not shown in FIG. 15). During the negotiations, AP 1502 may request that AP 1506 extend protection for an r-TWT schedule of AP 1502. After reaching an agreement (e.g., a Co-RTWT agreement), AP 1506 and STA 1508 may start extending protection to the r-TWT schedule for AP 1502.
[0167] In an example, AP 1502 may be out of range of AP 1506 for a duration 1510. Like duration 1314 described above for example 1300 illustrated in FIG. 13, duration 1510 may be negotiated (e.g., between AP 1502 and AP 1506, as part of a multi-AP negotiation) or may be pre-defined. In an embodiment, AP 1502 may transmit a frame 1512 (e.g., a broadcast frame) indicating the r-TWT schedule. In an embodiment, frame 1512 is a beacon frame. In an example, frame 1512 is received by STA 1504 and STA 1508, but not by AP 1502, since AP 1502 is out of range of AP 1506. In an embodiment, AP 1506 determines, based on not receiving any frame during the duration 1510, that the AP 1502 is out of range. In an embodiment, AP 1506 transmits a frame 1514 to STA 1508 to indicate a request for STA 1508 to monitorDocket No.: 25-3025PCTreception of a beacon frame for a duration 1516 (e.g., instead of AP 1506 stopping extending protection for the r-TWT schedule of AP 1502 after duration 1510).
[0168] In an example, AP 1502 indicates to AP 1506 a tear down of the r-TWT session. In an example, AP 1502 transmits a multi-AP negotiation request frame to AP 1506 (not shown in FIG. 15) to indicate the tear down of the r-TWT schedule. Were AP 1506 able to receive the multi-AP negotiation request frame, AP 1506 may transmit a multi-AP negotiation response frame to AP 1502 (not shown in FIG. 15) to acknowledge the reception of the multi-AP negotiation request frame. Since AP 1502 is not in range of AP 1506, however, AP 1506 does not receive the multi-AP negotiation request frame and does not acknowledge the multi-AP negotiation response frame. As a result, AP 1502 may assume that AP 1506 is no longer in range and unilaterally teardown the r-TWT schedule. Subsequently, AP 1502 may no longer include the r-TWT schedule, in subsequent beacon frames, after the teardown (e.g., AP 1502 may no longer include the r-TWT schedule in a frame 1518, discussed further below).
[0169] In an example, upon receiving frame 1514, STA 1508 monitors for reception of frames from AP 1502 (eg., STA 1508 monitors for reception of beacon frames from AP 1502) during a duration 1516. Like duration 1510 described above, duration 1516 may be negotiated (e.g., between any, or all, of AP 1502, 1506, and STA 1508) or may be pre-defined.
[0170] In an example, AP 1502 transmit frame 1518 (e.g., a broadcast frame). In an embodiment, frame 1518 is a beacon frame. In an embodiment, frame 1518 no longer contains the r-TWT schedule information (e.g., since AP 1502 terminated the r-TWT schedule as described above). Upon receiving frame 1518, STA 1508 determines that the r-TWT schedule no longer exists (e.g., based on frame 1518 not including the r-TWT schedule information). In an embodiment, based on receiving frame 1518, STA 1508 transmits a frame 1520 to AP 1506 indicating that STA 1508 does not receive the r-TWT schedule from AP 1502. In an embodiment, frame 1520 indicates that STA 1508 received frame 1518 from AP 1502 For example, frame 1520 may indicate that STA 1508 received a beacon frame from AP 1502. In an embodiment, frame 1520 further indicates that frame 1518 (e.g., a beacon frame) did not include the r-TWT schedule information (e.g., the r-TWT schedule or any other suitable r-TWT schedule information). Upon receiving frame 1520, AP 1506 determines to stop extending protection, by AP 1506, to the r-TWT schedule of the AP 1502.
[0171] FIG. 16 illustrates an example 1600 of a procedure according to an embodiment. In an embodiment, the procedure illustrated in example 1600 may facilitate Co-RTWT operation, as described further below. Example 1600 is provided for the purpose of illustration only and is not limiting of embodiments of the present disclosure. As shown in FIG.16, example 1600 may include an AP 1502, a STA 1504, an AP 1602, and a STA 1604. AP 1502 and STA 1504 are described above for example 1500 illustrated in FIG. 15. In an embodiment, any, or all, of AP 1602, and STA 1604 may be an MLD. In an example, STA 1604 may be associated with AP 1602. In an embodiment, APs 1502 and 1602 may form a multi-AP group. AP 1502 may be a coordinating AP of the multi-AP group, and AP 1602 may be a coordinated AP of the multi-AP group. In an embodiment, AP 1502 and AP 1602 may be configured to schedule their own r-TWT schedules by default and may support reconfiguration of their respective r-TWT schedules during a multi-AP r-TWT negotiation phase, as described in relation to FIG. 11 above.Docket No.: 25-3025PCT
[0172] Example 1600 may begin with AP 1502 and AP 1602 undergoing a multi-AP negotiation procedure as described in example 1100 illustrated in FIG. 11 (not shown in FIG. 16). During the negotiations, AP 1502 may request that AP 1602 extend protection for an r-TWT schedule of AP 1502. After reaching an agreement (e.g a Co-RTWT agreement), AP 1602 and STA 1604 may start extending protection to the r-TWT schedule for AP 1502.
[0173] In an example, AP 1502 may decide to terminate (e.g., tear down) the r-TWT agreement. In an embodiment, AP 1502 and AP 1602 may have agreed to terminate (e.g., tear down) the r-TWT agreement by removing the r-TWT schedule information from the beacon frame transmitted by AP 1502. In an embodiment, AP 1502 may transmit a request frame (not illustrated) to AP 1602 to extend protection to a r-TWT of AP 1502. In an embodiment, the request frame may be an embodiment of frame 1114 described in example 1100 illustrated in FIG. 11. In an embodiment, the request frame further comprises an agreement to stop extending protection, to the r-TWT schedule of AP 1502, based on receiving a beacon frame, from AP 1502, not including the r-TWT schedule. In an embodiment, upon receiving the request frame, AP 1602 transmits a response frame (not illustrated) to AP 1502. In an embodiment, the response frame may be an embodiment of frame 1116 described in example 1100 illustrated in FIG. 11. In an embodiment, the response frame further comprises an agreement to stop extending protection, to the r-TWT schedule of AP 1502, based on receiving the beacon frame, from AP 1502, not including the r-TWT schedule.
[0174] In an embodiment, AP 1502 may transmit a frame 1606 (e.g., a beacon frame). In an embodiment, frame 1606 (e.g., the beacon frame) may not include the r-TWT schedule information. Upon receiving frame 1606, based on frame 1606 (e.g., the beacon frame) not including the r-TWT schedule information (e.g., the r-TWT schedule or any other suitable r-TWT schedule information), AP 1602 may stop extending protection to the r-TWT schedule of AP 1502. AP 1602 may transmit a frame 1608 (e.g., to STA 1604) indicating that AP 1602 is stopping extending protection to the r-TWT schedule of AP 1502. In an embodiment, frame 1608 may be a beacon frame
[0175] FIG. 17 illustrates an example 1700 of a procedure according to an embodiment. In an embodiment, the procedure illustrated in example 1700 may facilitate Co-RTWT operation, as described further below. Example 1700 is provided for the purpose of illustration only and is not limiting of embodiments of the present disclosure. As shown in FIG.17, example 1700 may include an AP 1702, a STA 1704, an AP 1706, and an AP 1708. In an embodiment, any, or all, of AP 1702, STA 1704, AP 1706, andAP 1708 may bean MLD. In an example, STA 1704 may be associated with AP 1702. In an embodiment, APs 1702, 1706 and 1708 may form a multi-AP group. AP 1702 may be a coordinating AP of the multi-AP group, and APs 1706 and 1708 may be a coordinated AP of the multi-AP group. In an embodiment, AP 1702, AP 1706 and AP 1708 may be configured to schedule their own r-TWT schedules by default and may support reconfiguration of their respective r-TWT schedules during a multi-AP r-TWT negotiation phase, as described in relation to FIG. 11 above. In an embodiment, AP 1702 may set up an r-TWT schedule for STA 1704.
[0176] Example 1700 maybegin with AP 1702, AP 1706, and / or AP 1708 undergoing a multi-AP negotiation procedure as described in example 1100 illustrated in FIG. 11 (not shown in FIG. 17). During the negotiations, AP 1702 may request that AP 1706 and AP 1708 extend protection for an r-TWT schedule of AP 1702. After reaching an agreement (e.g., a Co-RTWT agreement), AP 1706 and AP 1708 may start extending protection to the r-TWT schedule for AP 1702.Docket No.: 25-3025PCT
[0177] In an example, AP 1706 may be out of range of AP 1702 for a duration 1714. Like duration 1314 described above for example 1300 illustrated in FIG. 13, duration 1714 maybe negotiated (e.g., between any, or all, of APs 1702, 1706, and 1708, as part of a multi-AP negotiation) or may be pre-defined. In an example, AP 1702 may transmit a frame 1712 (e.g., to STA 1704). Since AP 1702 is out of range of AP 1706, for the duration 1714, AP 1706 may not receive frame 1712. In an embodiment, AP 1706 may determine that AP 1702 is out of its range.
[0178] Based on not receiving frame 1712, AP 1706 may transmit a frame 1716 to request that AP 1708 monitor reception of any frame transmitted from AP 1702 for a duration 1718. Like duration 1714 described above, duration 1718 maybe negotiated (e.g., between any, or all, of APs 1702, 1706, and 1708, aspartof a multi-AP negotiation) or may be pre-defined. In an example, AP 1702 shuts down during duration 1718. Based on not receiving any frame from AP 1702 during duration 1718, AP 1708 may transmit a frame 1722 (e.g., upon expiration of duration 1718) indicating that AP 1708 has not received any frame from AP 1702 for duration 1718. In an embodiment, upon receiving frame 1722, AP 1706 determines to stop extending protection to the r-TWT schedule of AP 1702 (e.g., AP 1706 determines to teardown the r-TWT agreement).
[0179] FIG. 18 illustrates an example 1800 of a procedure according to an embodiment. In an embodiment, the procedure illustrated in example 1800 may facilitate Co-RTWT operation, as described further below. Example 1800 is provided for the purpose of illustration only and is not limiting of embodiments of the present disclosure. As shown in FIG.18, example 1800 may include an AP 1802, a STA 1804, an AP 1806, and a STA 1808. In an embodiment, any, or all, of AP 1802, STA 1804, AP 1806, and STA 1808 may be an MLD. In an example, STA 1804 maybe associated with AP 1802, and STA 1808 may be associated with AP 1806. In an embodiment, APs 1802 and 1806 may form a multi-AP group. AP 1802 may be a coordinating AP of the multi-AP group, and AP 1806 may be a coordinated AP of the multi-AP group. In an embodiment, AP 1802 and AP 1806 may be configured to schedule their own r-TWT schedules by default and may support reconfiguration of their respective r-TWT schedules during a multi-AP r-TWT negotiation phase, as described in relation to FIG. 11 above. In an embodiment, AP 1802 may set up an r-TWT schedule for STA 1804.
[0180] Example 1800 may begin with AP 1802 and AP 1806 undergoing a multi-AP negotiation procedure as described in example 1100 illustrated in FIG. 11 (not shown in FIG. 18). During the negotiations, AP 1802 may request that AP 1806 extend protection for an r-TWT schedule of AP 1802. After reaching an agreement (e.g., a Co-RTWT agreement), AP 1806 and STA 1808 may start extending protection to the r-TWT schedule for AP 1802.
[0181] In an example, AP 1802 may be out of range of AP 1806 for a duration 1814. Like duration 1314 described above for example 1300 illustrated in FIG. 13, duration 1814 may be negotiated (e.g., between AP 1802 and AP 1806, as part of a multi-AP negotiation) or may be pre-defined. AP 1802 may transmit a frame 1812 (e.g., to STA 1804). In an example, AP 1806 may not receive frame 1812, since AP 1802 is out of range of AP 1806. In an embodiment, AP 1806 may determine that AP 1802 is out of range of AP 1806 based on not receiving frame 1812.
[0182] In an embodiment, AP 1806 may transmit a frame 1816 to STA 1808 to indicate a request for STA 1808 to monitor reception of any frame from AP 1802 within a duration 1818. Like duration 1318 described above for example 1300 illustrated in FIG. 13, duration 1818 may be negotiated (e.g., between any, or all, of AP 1802, AP 1806, and STADocket No.: 25-3025PCT1808) or may be pre-defined. For example, frame 1816 may indicate a request for STA 1808 to respond to AP 1806 only if STA 1808 receives a frame from AP 1802 during duration 1818 (e.g., STA 1808 does not respond to AP 1806 if it receives no frames from AP 1802 during duration 1818).
[0183] In an example, AP 1802 shuts down within duration 1818. Therefore, STA 1808 does not receive any frame fromAP 1802 within duration 1818. In an embodiment, STA 1808 does not transmit any frame to AP 1806 indicating that STA 1808 did not receive frames from AP 1802 during duration 1818. As described above, in an embodiment STA 1808 only transmits a frame to AP 1806 if STA 1808 receives a frame from AP 1802 during duration 1818.
[0184] In an embodiment, AP 1806 determines, based on not receiving any frame, from STA 1808 indicating that STA 1808 received a frame from AP 1802, to stop extending protection, by AP 1806, to the r-TWT schedule of AP 1802. For example, AP 1806 determines to teardown the Co-TWT agreement.
[0185] As would be understood by a person of skill in the art based on the teachings herein, the embodiments as described by the above, and below, examples may be readily extended to implementations including more than one STA.
[0186] As would be understood by a person of skill in the art based on the teachings herein, the embodiments as described by the above, and below, examples may be readily extended to implementations including more than one AP.
[0187] As would be understood by a person of skill in the art based on the teachings herein, the embodiments as described by the above, and below, 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.
[0188] FIG. 19 illustrates an example process 1900 according to an embodiment. Example process 1900 is provided for the purpose of illustration only and is not limiting embodiments. Process 1900 may be performed by a first AP, such as AP 1306, AP 1406, AP 1506, AP 1602, AP 1706, AP 1708, or AP 1806 described above, or AP 2502, 2504, or 2506 described below As shown in FIG. 19, process 1900 may comprise steps 1902 and step 1904.
[0189] Step 1902 comprises receiving, by a first access point (AP) from a first station (STA), a first frame indicating that the first STA does not receive a second frame from a second AP. The first STA may be any suitable STA, such as STA 1308, STA 1408, STA 1508, STA 1604, AP 1708 (e.g., AP STA 1708), or STA 1808 described above. The second AP may be any suitable AP, such as AP 1302, AP 1402, AP 1502, AP 1702, or AP 1802, described above, or AP 2502, 2504, or 2506 described below.
[0190] Step 1904 comprises, based on the first frame, stopping extending protection, by the first AP, to a restricted target wake time (r-TWT) schedule of the second AP.
[0191] In an embodiment, the first AP comprises a coordinated AP of a multi-AP group comprising the first AP and the second AP. In an embodiment, the second AP comprises a coordinating AP of the multi-AP group comprising the first AP and the second AP.
[0192] In an embodiment, process 1900 further includes receiving, by the first AP from the second AP, a third frame requesting that the first AP extend protection to the r-TWT schedule of the second AP. In an embodiment, process 1900 further includes transmitting, by the first AP to the second AP and in response to the third frame, a fourth frame indicating that the first AP extends protection to the r-TWT schedule.Docket No.: 25-3025PCT
[0193] In an embodiment, based on the first AP not receiving a fifth frame from the second AP within a first duration from a last received frame, by the first AP from the second AP, the first AP transmits, to the first STA, a sixth frame.
[0194] In an embodiment, process 1900 further includes transmitting, by the first AP to the second AP, the first duration.
[0195] In an embodiment, process 1900 further includes receiving, by the first AP from the second AP, the first duration.
[0196] In an embodiment, the first duration is pre-defined.
[0197] In an embodiment, the sixth frame indicates a request for the first STA to determine whether the first STA receives the second frame from the second AP. In an embodiment, the sixth frame indicates a request for the first STA to monitor reception of the second frame within a second duration from the first STA receiving the sixth frame.
[0198] In an embodiment, process 1900 further includes transmitting, by the firs AP to the first STA, a seventh frame indicting a request to the first STA to indicate whether the first STA has received the second frame during the second duration. In an embodiment, the first AP receives the first frame in response to the seventh frame.
[0199] In an embodiment, the seventh frame is an individually addressed control frame.
[0200] In an embodiment, the seventh frame is a broadcast frame or a multicast frame.
[0201] In an embodiment, the sixth frame further indicates a request for the first STA to report whether the first STA receives the second frame during the second duration.
[0202] In an embodiment, the sixth frame further indicates a request for the first STA to report that the first STA does not receive the second frame during the second duration.
[0203] In an embodiment, the first AP receives the first frame in response to the sixth frame.
[0204] In an embodiment, the first AP receives the first frame during the second duration.
[0205] In an embodiment, the first AP receives the first frame after the second duration.
[0206] In an embodiment, process 1900 further includes transmitting, by the first AP to the second AP, the second duration.
[0207] In an embodiment, process 1900 further includes receiving, by the first AP from the second AP, the second duration.
[0208] In an embodiment, the second duration is pre-defined.
[0209] In an embodiment, the sixth frame is an individually addressed control frame.
[0210] In an embodiment, the sixth frame is a broadcast / multicast frame.
[0211] In an embodiment, the first STA is associated with the first AP.
[0212] In an embodiment, process 1900 further includes receiving, by the first AP from a second STA an eighth frame indicating that the second STA does not receive a ninth from the second AP. In an embodiment, the first STA and the second STA comprise all STAs associated with the first AP.
[0213] In an embodiment, based on the first frame and the eighth frame, the first AP stops extending protection to the r-TWT schedule of the second AP.Docket No.: 25-3025PCT
[0214] In an embodiment, the first AP stops extending protection to the r-TWT schedule of the second AP based on all STAs associated with the first AP not receiving any frames from the second AP during a third duration occurring while the first AP extends protection to the r-TWT schedule of the second AP
[0215] In an embodiment, the first STA comprises a third AP. In an embodiment, the third AP is part of a multi-AP group comprising the first AP, the second AP, and the third AP. In an embodiment, the third AP comprises a coordinated AP of a multi-AP group comprising the first AP, the second AP, and the third AP.
[0216] FIG. 20 illustrates an example process 2000 according to an embodiment. Example process 2000 is provided for the purpose of illustration only and is not limiting embodiments. Process 2000 may be performed by a first AP, such as such as AP 1306, AP 1406, AP 1506, AP 1602, AP 1706, AP 1708, orAP 1806 described above, or AP 2502, 2504, or 2506 described below. As shown in FIG.20, process 2000 may comprise steps 2002 and step 2004.
[0217] Step 2002 comprises transmitting, by a first access point (AP) to a station (STA), a first frame indicating a request for the STA to monitor reception of a second frame from a second AP within a duration. The first STA may be any suitable STA, such as STA 1308, STA 1408, STA 1508, STA 1604, AP 1708 (e.g, AP STA 1708), or STA 1808 described above. The second AP maybe any suitable AP, such as AP 1302, AP 1402, AP 1502, AP 1702, or AP 1802, described above, or AP 2502, 2504, or 2506 described below.
[0218] Step 2004 comprises, based on not receiving, by the first AP, a third frame, from the STA indicating that the STA received the second frame from the second AP, stopping extending protection, by the first AP, to a restricted target wake time (r-TWT) schedule of the second AP.
[0219] FIG. 21 illustrates an example process 2100 according to an embodiment. Example process 2100 is provided for the purpose of illustration only and is not limiting embodiments. Process 2100 may be performed by a first AP, such as such as AP 1306, AP 1406, AP 1506, AP 1602, AP 1706, AP 1708, orAP 1806 described above, or AP 2502, 2504, or 2506 described below. As shown in FIG.21, process 2100 may comprise steps 2102 and step 2104.
[0220] Step 2102 comprises receiving, by a first access point (AP) from a station (STA), a first frame indicating that the STA does not receive a restricted target wake time (r-TWT) schedule from a second AP. The first STA may be any suitable STA, such as STA 1308, STA 1408, STA 1508, STA 1604, AP 1708 (e.g., AP STA 1708), or STA 1808 described above. The second AP maybe any suitable AP, such asAP 1302, AP 1402, AP 1502, AP 1702, orAP 1802, described above, orAP 2502, 2504, or 2506 described below.
[0221] Step 2104 comprises, based on the first frame, stopping extending protection, by the first AP, to a restricted target wake time (r-TWT) schedule of the second AP.
[0222] In an embodiment, the first frame indicates that the STA received a beacon frame from the second AP. In an embodiment, the first frame further indicates that the beacon frame did not include the r-TWT schedule.
[0223] In an embodiment, process 2100 further includes the first AP transmitting, to the STA, a second frame indicating a request for the STA to monitor reception of a beacon frame within a duration. In an embodiment, the first AP receives the first frame in response to transmitting the second frame.Docket No.: 25-3025PCT
[0224] FIG. 22 illustrates an example process 2200 according to an embodiment. Example process 2200 is provided for the purpose of illustration only and is not limiting embodiments. Process 2200 may be performed by a first AP, such as AP 1306, AP 1406, AP 1506, AP 1602, AP 1706, AP 1708, or AP 1806 described above, or AP 2502, 2504, or 2506 described below. As shown in FIG. 22, process 2200 may comprise steps 2202 and step 2204.
[0225] Step 2202 comprises receiving, by a first access point (AP) from a second AP, a beacon frame. The second AP may be any suitable AP, such as AP 1302, AP 1402, AP 1502, AP 1702, or AP 1802, described above, or AP 2502, 2504, or 2506 described below.
[0226] Step 2204 comprises, based on the beacon frame not including a restricted target wake time (r-TWT) schedule, stopping extending protection, by the first AP, to the r-TWT schedule of the second AP.
[0227] In an embodiment, the first AP comprises a coordinated AP of a multi-AP group comprising the first AP and the second AP. In an embodiment, the second AP comprises a coordinating AP of the multi-AP group comprising the first AP and the second AP.
[0228] In an embodiment, process 2200 further includes receiving, by the first AP from the second AP, a first frame requesting that the first AP extend protection to the r-TWT schedule of the second AP.
[0229] In an embodiment, process 2200 further includes transmitting, by the first AP to the second AP and in response to the first frame, a second frame indicating that the first AP extends protection to the r-TWT schedule. In an embodiment, at least one of the first frame or the second frame indicates an agreement to stop extending protection, to the r-TWT schedule of the second AP, based on receiving a beacon frame, from the second AP, not including the r-TWT schedule.
[0230] FIG. 23 illustrates an example process 2300 according to an embodiment. Example process 2300 is provided for the purpose of illustration only and is not limiting embodiments. Process 2300 may be performed by any suitable STA, such as STA 1308, STA 1408, STA 1508, STA 1604, AP 1708 (e.g., AP STA 1708), or STA 1808 described above, or AP 2502, 2504, or 2506 described below. As shown in FIG. 23, process 2300 may comprise steps 2302 and step 2304.
[0231] Step 2302 comprises transmitting, by a station (STA) to a first access point (AP), a first frame indicating that the STA does not receive a second frame from a second AP. The first AP may be any suitable AP, such as AP 1306, AP 1406, AP 1506, AP 1602, AP 1706, AP 1708, or AP 1806 described above. The second AP may be any suitable AP, such as AP 1302, AP 1402, AP 1502, AP 1702, or AP 1802, described above, or AP 2502, 2504, or 2506 described below.
[0232] Step 2304 comprises, receiving, by the STA from the first AP, a third frame indicating stopping extending protection, by the first AP, to a restricted target wake time (r-TWT) schedule of the second AP.
[0233] In an embodiment, process 2300 further includes receiving, by the STA from the first AP, a fourth frame indicating a request for the STA to determine whether the STA receives the second frame from the second AP. In an embodiment, the fourth frame indicates a request for the STA to monitor reception of the second frame within a second duration from the STA receiving the fourth frame.Docket No.: 25-3025PCT
[0234] In an embodiment, process 2300 further includes receiving, by the STA from the first AP, a fifth frame indicting a request to the STA to indicate whether the STA has received the second frame during the second duration. In an embodiment, the STA transmits the first frame in response to the fifth frame.
[0235] In an embodiment, the fifth frame is an individually addressed control frame.
[0236] In an embodiment, the fifth frame is a broadcast frame or a multicast frame.
[0237] In an embodiment, the fourth frame further indicates a request for the STA to report whether the first STA receives the second frame during the second duration.
[0238] In an embodiment, the fourth frame further indicates a request for the STA to report that the STA does not receive the second frame during the second duration.
[0239] In an embodiment, the STA transmits the first frame in response to the fourth frame.
[0240] In an embodiment, the STA transmits the first frame during the second duration.
[0241] In an embodiment, the STA transmits the first frame after the second duration.
[0242] In an embodiment, the second duration is pre-defined.
[0243] In an embodiment, process 2300 further includes receiving, by the STA from the first AP, the second duration.
[0244] In an embodiment, process 2300 further includes transmitting, by the STA to the first AP, the second duration.
[0245] In an embodiment, the fourth frame is an individually addressed control frame.
[0246] In an embodiment, the fourth frame is a broadcast / multicast frame.
[0247] In an embodiment, the STA is associated with the first AP.
[0248] In an embodiment, the third frame comprises a beacon frame.
[0249] In an embodiment, the first frame indicates a third duration. In an embodiment, the third duration and the second duration are the same.
[0250] FIG. 24 illustrates an example process 2400 according to an embodiment. Example process 2400 is provided for the purpose of illustration only and is not limiting embodiments. Process 2400 may be performed by a STA, such as STA 1308, STA 1408, STA 1508, STA 1604, AP 1708 (e.g„ AP STA 1708), or STA 1808 described above, or AP 2502, 2504, or 2506 described below. As shown in FIG.24, process 2400 may comprise steps 2402 and step 2404.
[0251] Step 2402 comprises transmitting, by a station (STA) to a first access point (AP), a first frame indicating that the STA does not receive a restricted target wake time (r-TWT) schedule from a second AP. The first AP may be any suitable AP, such as AP 1306, AP 1406, AP 1506, AP 1602, AP 1706, AP 1708, or AP 1806 described above. The second AP may be any suitable AP, such as AP 1302, AP 1402, AP 1502, AP 1702, or AP 1802, described above, or AP 2502, 2504, or 2506 described below.
[0252] Step 2404 comprises receiving, by the STA from the first AP, a second frame indicating stopping extending protection, by the first AP, to the r-TWT schedule of the second AP.
[0253] In an embodiment, process 2400 further includes receiving, by the STA from the second AP, a beacon frame.
[0254] In an embodiment, process 2400 further includes determining, by the STA, that the beacon frame does not include the r-TWT schedule of the second AP.Docket No.: 25-3025PCT
[0255] In an embodiment, the first frame further indicates that the beacon frame did not include the r-TWT schedule.
[0256] In an embodiment, process 2400 further includes receiving, by the STA from the first AP, a second frame indicating a request for the STA to monitor reception of a beacon frame within a duration. In an embodiment, the STA transmits the first frame in response to receiving the second frame.
[0257] FIG.25 illustrates an example 2500 of a procedure according to an embodiment. As shown in FIG.25, example 2500 may include one or more of an AP 2502, an AP 2504, and / or an AP 2506. In an embodiment, any, or all, of AP 2502, AP 2504, and AP 2506 may be an MLD. In an embodiment, any combination of APs 2502, 2504, and / or 2506 may form a multi-AP group (e.g. , a multi-AP coordination (MAPC) group). AP 2502 may be a coordinating AP of the multi-AP group, and AP 2504 and / or AP 2506 may be a coordinated AP of the multi-AP group. In an embodiment, AP 2502, AP 2504, and / or AP 2506 may be configured to schedule their own r-TWT schedules by default and may support reconfiguration of their respective r-TWT schedules during a multi-AP r-TWT negotiation phase, as described in relation to FIG. 11 above. In an embodiment, AP 2502 may set up an r-TWT schedule for one or more of its associated STAs (not illustrated).
[0258] Example 2500 may begin with any combination of AP 2502, AP 2504, and / or AP 2506 undergoing a multi-AP negotiation procedure (e.g., a MAPC procedure) as described in example 1100 illustrated in FIG. 11 and below (not shown in FIG.25). During the negotiations, AP 2502 may request that AP 2504 and / or AP 2506 extend protection for an r-TWT schedule of AP 2502. After reaching an agreement (e.g., a Co-RTWT agreement), AP 2504 and / or AP 2506 may start extending protection to the r-TWT schedule for AP 2502. This is merely an example, and any combination of AP 2502, AP2504, and / or AP 2506 may undergo a multi-AP negotiation procedure (e.g., a MAPC procedure) for any suitable multi-AP coordination scheme. For example, any combination of AP 2502, AP 2504, and / or AP 2506 may undergo a multi-AP negotiation procedure (e.g., a MAPC negotiation) for coordinated beamforming (Co-BF), coordinated spatial reuse (Co-SR), or coordinated time division multiple access (Co-TDMA).
[0259] In an embodiment, AP 2502 may shut down at a time T1. In an embodiment, AP 2506 may determine / identify that AP 2502 may be shut down and may teardown an agreement with AP 2502 (e.g., a MAPC agreement). For example, AP 2506 may expect to receive one or more frames (e.g., one or more beacon frames) from AP 2502 within a duration (e.g., a timeout duration). In an embodiment, AP 2506 may identify a duration during which it expects to receive one or more beacon frames from AP 2502. For example, AP 2506 may estimate a TBTT for AP 2502 (e.g., based on one or more received beacons from AP 2502) and may identify duration based on the estimated TBTT. AP 2506 may not receive a beacon frame, or multiple beacon frames (e.g., multiple consecutive beacon frames), from AP 2502 within this duration. Based on not receiving one or more frames from AP 2502 (e.g., one or more consecutive beacon frames) within the duration, AP 2506 may tear down an agreement with AP 2502 (e.g., a MAPC agreement). In an embodiment, the duration (e.g., the timeout duration) may begin when AP 2506 receives a frame (e.g., a beacon frame) from AP 2502. Based on not receiving another frame (e.g., another beacon frame) from AP 2502 within the duration, AP 2506 may tear down an agreement with AP 2502 (e.g., a MAPC agreement). Alternatively, or in addition, the duration (e.g., the timeout duration) may begin based on an estimated TBTT for AP 2502, as discussed above. Based on not receiving frame(s) (e.g., beaconDocket No.: 25-3025PCTframe(s)) from AP 2502 within the duration, AP 2506 may tear down an agreement with AP 2502 (e.g., a MAPC agreement). In an embodiment, AP 2506 may tear down a Co-RTWT agreement with AP 2502. AP 2506 may stop extending protection to the r-TWT schedule of AP 2502 (e.g., after duration 2522). This is merely an example, and AP 2506 may tear down any suitable MAPC agreement (e.g., a Co-BF agreement, a Co-SR agreement, or a Co-TDMA agreement).
[0260] Further, in an embodiment, AP 2506 may transmit a frame 2512 (e.g., after AP 2502 shuts down at time T1). For example, AP 2506 may transmit frame 2512 to AP 2502. In an embodiment, frame 2512 may be a multi-AP group frame (e.g., a multi-AP group discovery frame or a multi-AP group negotiation frame, as discussed above in relation to FIG. 11). For example, frame 2512 may be a MAPC request frame (e.g., a MAPC discovery request frame or a MAPC negotiation request frame).
[0261] In an embodiment, AP 2506 transmits frame 2512 based on, or following, determining / identifying that AP 2502 may be shut down. For example, as discussed above, AP 2506 may listen for transmissions from AP 2502 and may determine that AP 2502 does not transmit when expected. As one example, AP 2506 may listen for one or more beacon frames transmitted by AP 2502, and may determine that AP 2502 does not transmit the beacon frame(s) when expected (e.g., AP 2506 may wait for a timeout duration, or may identify a time at which it expects to receive beacon frame(s) from AP 2502). AP 2506 may transmit frame 2512 based on, or following, failing to receive one or more transmissions (e.g., one or more beacon frames) from AP 2502.
[0262] In an embodiment, AP 2506 may include in frame 2512 an indication of agreement teardown (e.g., MAPC agreement teardown, such as Co-RTWT agreement teardown). For example, as discussed above, frame 2512 may be a multi-AP group frame (e.g., a MAPC frame). Frame 2512 may include an indication (e.g., a single bit indication or a multiple bit indication) that a MAPC agreement (e.g., a Co-RTWT agreement) may be torn down (e.g., because AP 2506 has determined / identified that AP 2502 may be shutdown). For example, as discussed further below, to request teardown of an established MAPC agreement, a MAPC requesting AP may set a MAPC Operation Type field to a value of two in a MAPC Scheme Request field that carries the request. AP 2506 may set a MAPC Operation Type field to a value of two in a MAPC Scheme Request field in frame 2512.
[0263] AP 2506 transmitting frame 2512 based on, or following, determining / identifying that AP 2502 may be shutdown is merely one example. Alternatively, AP 2506 may transmit frame 2512 for any suitable reason. For example, frame 2512 may be a MAPC frame (e.g., a MAPC request frame), and AP 2506 may transmit frame 2512 as part of MAPC formation / operation. In this example, frame 2512 may not include an indication of agreement teardown.
[0264] In an embodiment, AP2502 is shut down at time T1, and so AP 2502 may not respond to frame 2512 (e.g., AP 2502 does not transmit a frame 2514). In an embodiment, frame 2514 may be a multi-AP group frame. For example, frame 2514 may be a MAPC response frame (e.g., a MAPC discovery response frame or a MAPC negotiation response frame). In an embodiment, AP 2502 is shut down, does not receive frame 2512, and does not transmit frame 2514.
[0265] In an embodiment, AP 2506 waits for a duration 2522 to receive frame 2514 (e.g., in response to frame 2512). For example, duration 2522 may be a timeout duration. In an embodiment, duration 2522 may be determined duringDocket No.: 25-3025PCTmulti-AP group negotiation (e.g., MAPC negotiation). Alternatively, or in addition, duration 2522 may be received by AP 2506 in another transmission (e.g., other than during a multi-AP group negotiation) and / or may be predetermined (e.g., duration 2522 may be specified in an IEEE 80211 standard amendment). Further, AP 2506 may indicate duration 2522 in frame 2512.
[0266] In an embodiment, duration 2522 begins when AP 2506 transmits frame 2512 (e.g., immediately after AP 2506 transmits frame 2512 or a short duration after AP 2506 transmits frame 2512). In an embodiment, AP 2506 may transmit additional frames (e.g., to AP 2502) during duration 2522 (not illustrated). For example, AP 2506 may retry to transmit frame 2512 (e.g., based on not receiving a response to frame 2512 from AP 2502). In an embodiment, duration 2522 begins when AP 2506 transmits frame 2512 (e.g., regardless of retries).
[0267] In an embodiment, after waiting duration 2522, AP 2506 may tear down an agreement with AP 2502 (e.g., a MAPC agreement). For example, AP 2506 may tear down a Co-RTWT agreement with AP2502. In an embodiment, AP 2506 may stop extending protection to the r-TWT schedule of AP 2502 (e.g., after duration 2522). This is merely an example, and AP 2506 may teardown any suitable MAPC agreement (e.g., a Co-BF agreement, a Co-SR agreement, or a Co-TDMA agreement).
[0268] As discussed above, in an embodiment AP 2506 may transmit frame 2512 to AP 2502. In an embodiment, frame 2512 may be addressed to AP 2502 and may be filtered (e.g., not received) by other APs or non-AP STAs.
[0269] Alternatively, another AP (e.g., AP 2504) may receive frame 2512. For example, frame 2512 may be addressed to AP 2502, and AP 2504 may overhear frame 2512. As another example, frame 2512 may be addressed to a broadcast address and AP 2504 may receive frame 2512.
[0270] In an embodiment, AP 2504 may listen for frame 2514 (e.g., based on / after receiving frame 2512). In an embodiment, AP 2504 may wait a duration (e.g., duration 2522) for frame 2514. In an embodiment, after waiting the duration (e.g., duration 2522) AP 2504 may tear down an agreement with AP 2502 (e.g., a MAPC agreement). For example, AP 2504 may teardown a Co-RTWT agreement with AP 2502. In an embodiment, AP 2504 may stop extending protection to the r-TWT schedule of AP 2502 (e.g., after duration 2522). This is merely an example, and AP 2504 may tear down any suitable MAPC agreement (e.g., a Co-BF agreement, a Co-SR agreement, or a Co-TDMA agreement).
[0271] In an embodiment, in the case of no communication between a MAPC requesting AP and a MAPC responding AP, an agreement (e.g., a MAPC agreement) may be automatically terminated.
[0272] In an aspect, a first AP receives, from a second AP, a first frame requesting that the first AP extend protection to an r-TWT schedule of the second AP. The first AP transmits, to the second AP, a second frame indicating that the first AP extends protection to the r-TWT schedule of the second AP. Based on extending protection to the r-TWT schedule, the first AP terminates / ends an obtained TXOP before a start time of an SP of the r-TWT schedule. Based on the first AP not receiving an expected third frame from the second AP within a first duration, the first AP stops extending protection to the r-TWT schedule of the second AP. The first duration extends from at least one of: receipt of a fourth frame by the first AP from the second AP, or transmission of a fifth frame by the first AP to the second AP.Docket No.: 25-3025PCT
[0273] In another aspect, based on a first STA not receiving a third frame from a second STA within a first duration, the first STA stops extending protection to an r-TWT schedule of the second STA. The first duration may extend from at least one of: receipt of a fourth frame by the first STA from the second STA, or transmission of a fifth frame by the first STA to the second STA. In an embodiment, the first STA comprises a first access point (AP) and the second STA comprises a second AP. In an embodiment, the first STA comprises a coordinated AP of a multi-AP group comprising the first AP and the second AP. In an embodiment, the second AP comprises a coordinating AP of the multi-AP group comprising the first AP and the second AP. In an embodiment, the first AP receives, from the second AP, a first frame requesting that the first AP extend protection to the r-TWT schedule of the second AP. In an embodiment, the first AP transmits, to the second AP and in response to the first frame, a second frame indicating that the first AP extends protection to the r-TWT schedule. In an embodiment, the third frame comprises an expected third frame. In an embodiment, the first duration extends from receipt of the fourth frame by the first AP from the second AP. In an embodiment, the fourth frame comprises a first beacon frame, wherein the third frame comprises a second beacon frame, and wherein the first duration extends from receipt of the first beacon frame to expected receipt of the second beacon frame. In an embodiment, the first duration comprises a timeout duration after receipt of the first beacon frame. In an embodiment, the first duration is based on a target beacon transmission time (TBTT) for the second AP. In an embodiment, the first AP estimates the TBTT for the second AP based on one or more beacon frames previously received by the first AP from the second AP. In an embodiment, the first duration extends from transmission of the fifth frame by the first AP to the second AP. In an embodiment, the fifth frame comprises a multi-AP coordination (MAPC) request frame. In an embodiment, the fifth frame indicates teardown of a MAPC agreement. In an embodiment, the MAPC agreement comprises a coordinated r-TWT (Co-RTWT) agreement. In an embodiment, the first AP transmits the fifth frame based on not receiving an expected sixth frame from the second AP. In an embodiment, the sixth frame comprises a beacon frame.
[0274] In an embodiment, an AP or STA in accordance with the above-described embodiments (e.g., any AP or STA as described in FIGS. 3-18 or 25) may perform operations according to a multi-AP coordination (MAPC) framework as described below. For example, AP MAPC framework may correspond to multi-AP group operations discussed above (e.g., in relation to FIG. 11). 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.
[0275] The MAPC framework includes a set of schemes (Co-BF, Co-SR, Co-TDMA, Co-RTWT, and Co-CR) in which APs operating their BSSs on the same primary 20 MHz channel and having overlapping bandwidth coordinate to reduce interference levels and to improve network performance such as medium utilization efficiency, communication reliability, and latency.
[0276] To use a MAPC scheme with a peer AP, an AP establishes an agreement for that MAPC scheme by following common procedures for multi-AP coordination schemes or via other means. For example, two APs that belong to the same ESS can establish agreements) for MAPC scheme(s) via communications over the backhaul. The AP and the peerDocket No.: 25-3025PCTAP might be in the same administrative domain or in different administrative domains, and the APs might be within the same ESS or different ESSs.
[0277] Common procedures applicable for MAPC schemes include a MAPC discovery procedure and a MAPC agreement negotiation procedure. Frame exchanges between two APs related to MAPC procedures are performed only within the overlapping bandwidths of the APs and include the common BSS's primary 20 MHz channel. The MAPC operations (MAPC discovery and MAPC negotiation) of APs affiliated with the same AP MLD are independent; specifically, the MAPC operations of one AP do not affect the MAPC operations of another AP affiliated with the same AP MLD. Additional procedures for specific MAPC schemes may also be performed.
[0278] MAPC discovery procedures allow APs to advertise and discover MAPC capabilities and parameters of other APs. An AP may advertise its MAPC capabilities, common MAPC parameters, and parameters specific to MAPC schemes by transmitting a MAPC Discovery Request frame to the broadcast address, or as an individually addressed frame to another AP.
[0279] If an AP receives a soliciting MAPC Discovery Request frame from a transmitting AP, the AP responds by sending a MAPC Discovery Response frame to the broadcast address or as an individually addressed Management frame to the transmitting AP. The value of the Dialog Token field of the MAPC Discovery Response frame is set equal to the value of the Dialog Token field of the soliciting MAPC Discovery Request frame.
[0280] An AP that transmits a MAPC Discovery Request frame or a MAPC Discovery Response frame may include a Per-Scheme Profile subelement in the reported MAPC element for each MAPC scheme for which the AP signals a capability. The AP does not include the MAPC Scheme Request Set field in the reported Per-Scheme Profile subelements.
[0281] If an AP that transmits a MAPC Discovery Request frame or a MAPC Discovery Response frame to a peer AP sets the MAPC Security Supported field carried in the MAPC element to 1, the AP includes an RSNE field and RSNXE field in the Security Profile subelement of the MAPC element. The AP does not include the MAPC Security Info field in the Security Profile subelement.
[0282] An AP sets the AP ID Present field of the MAPC Control field of the MAPC element to 0 when the MAPC element is carried in a MAPC Discovery Request frame or a MAPC Discovery Response frame. An AP sets the MAPC Capabilities Present field and the MAPC Parameters Present field of the MAPC Control field of the MAPC element to 1 when the MAPC element is carried in a MAPC Discovery Request frame or a MAPC Discovery Response frame.
[0283] Procedures for MAPC agreement negotiation allow an AP to establish, update, or tear down agreements for MAPC through negotiation. These procedures are performed in addition to specific rules defined for multi-AP coordination schemes.
[0284] A MAPC requesting AP is an AP that initiates a MAPC negotiation for one or more MAPC schemes with another AP. A MAPC responding AP is an AP that responds to a MAPC requesting AP.
[0285] A MAPC requesting AP does not initiate a MAPC negotiation for a specific MAPC scheme with a peer AP if the peer AP has set the corresponding field for the support of that MAPC scheme to 0 in the MAPC Common Info fieldDocket No.: 25-3025PCTreported in the MAPC Discovery Request frame, MARC Discovery Response frame, or MARC Negotiation Request frame most recently received by the MAPC requesting AR.
[0286] A MAPC requesting AP may initiate a MAPC negotiation for one or more MAPC schemes by sending an individually addressed MAPC Negotiation Request frame to another AP. The MAPC Negotiation Request frame includes a MAPC element including at least one Per-Scheme Profile subelement in the MAPC Optional Subelements field. Additionally, the MAPC requesting AP does not include a Per-Scheme Profile subelement for a specific MAPC scheme in the MAPC element if the MAPC requesting AP has not indicated support for that MAPC scheme in the MAPC Capabilities field carried in the MAPC element. Each Per-Scheme Profile subelement included in the MAPC element in the MAPC Negotiation Request frame carries request(s) fora specific MAPC scheme in the MAPC Scheme Request Set field, including at least one MAPC Scheme Request field.
[0287] A MAPC responding AP that receives an individually addressed MAPC Negotiation Request frame from a MAPC requesting AP responds by sending an individually addressed MAPC Negotiation Response frame to the MAPC requesting AP. The value of the Dialog Token field of the MAPC Negotiation Response frame is set equal to the value of the Dialog Token field of the MAPC Negotiation Request frame. The Status Code field is set to SUCCESS if the MAPC responding AP accepts at least one of the requests carried in the received MAPC Negotiation Request frame. Otherwise, the MAPC responding AP sets the Status Code field to indicate an appropriate rejection status code.
[0288] The MAPC Optional Subelements field in the MAPC element carried in the MAPC Negotiation Response frame includes one Per-Scheme Profile subelement for each corresponding Per-Scheme Profile subelement included in the MAPC Optional Subelements field in the MAPC element in the MAPC Negotiation Request frame sent by the MAPC requesting AP. In the MAPC Negotiation Response frame, each Per-Scheme Profile subelement includes at least one MAPC Scheme Request field with a MAPC Operation Type field set to 3, 4, or 5.
[0289] The following rules apply to the MAPC Operation Type field:• If the MAPC Operation Type field is set to 3 or 4, the MAPC Request Parameter Set field is not included. • To accept a request, the MAPC Operation Type field is set to 3.• To reject a request, the MAPC Operation Type field is set to 4.• To reject a request and to indicate that the MAPC responding AP expects to accept a subsequent request with parameter values as those included by the MAPC responding AP in the MAPC Request Parameter Set field carried in the same MAPC Scheme Request field as the MAPC Operation Type field, the MAPC Operation Type field is set to 5.
[0290] The MAPC responding AP does not set the MAPC Operation Type field included in the MAPC Scheme Request field and carried in the MAPC Negotiation Response frame to 5 if a MAPC Request Parameter Set field is not present for that MAPC scheme.
[0291] After two APs establish a MAPC agreement, either of the two APs may initiate a MAPC negotiation as a MAPC requesting AP to update or teardown the MAPC agreement.Docket No.: 25-3025PCT
[0292] To request a new agreement establishment, the MAPC requesting AP sets the MAPC Operation Type field to 0 in the MAPC Scheme Request field that carries the request. If the MAPC Operation Type field is set to 0, the MAPC Request Parameter Set field is included according to the rules defined for each specific MAPC scheme.
[0293] A MAPC requesting AP does not request to establish a new agreement fora specific MAPC scheme if the MAPC responding AP has set the corresponding field for enabling MAPC agreement establishment for that MAPC scheme to 0 in the MAPC Discovery Request frame, MAPC Discovery Response frame, or MAPC Negotiation Request frame most recently received by the MAPC requesting AP.
[0294] To accept, reject, or reject with a suggestion for alternative parameters for a MAPC agreement establishment, the MAPC responding AP follows the general procedures for MAPC agreement negotiation. If the MAPC responding AP accepts the request to establish a new MAPC agreement for a specific MAPC scheme, the MAPC requesting AP and the MAPC responding AP establish a MAPC agreement for that scheme, and the agreement persists until teardown.
[0295] A MAPC requesting AP and a MAPC responding AP may establish:• Up to one MAPC agreement for each one of Co-BF, Co-SR, and Co-TDMA.• Up to one MAPC agreement per RTWT schedule for Co-RTWT.• Multiple MAPC agreements for Co-CR.
[0296] For example, if a MAPC requesting AP transmits a MAPC Negotiation Request frame including a Co-BF profile and a Co-RTWT profile, where the Co-BF profile includes a MAPC Scheme Request field for a new agreement establishment (with MAPC Operation Type set to 0) and the Co-RTWT profile includes three MAPC Scheme Request fields for three new agreement establishment requests, a MAPC responding AP may respond with a MAPC Negotiation Response frame including corresponding profiles and request responses. In this case, the MAPC requesting AP and the MAPC responding AP can establish up to one Co-BF agreement and up to three Co-RTWT agreements.
[0297] A MAPC requesting AP does not set any MAPC Operation Type field to indicate Agreement update or Agreement teardown in the MAPC Negotiation Request frame if there is no established agreement for the corresponding MAPC scheme between the MAPC requesting AP and the MAPC responding AP.
[0298] When an AP participates in a MAPC negotiation to establish new MAPC agreement(s), the AP follows specific rules to assign an AP ID to a peer AP.• UHR AP Requirements: If a UHR AP intends to assign an AP ID value, the UHR AP additionally satisfies requirements for basic UHR BSS operation.• Uniqueness: The same AP ID value is not assigned by the AP or by its affiliated MLD to any other STA. A peer AP might obtain the same or different AP IDs from other APs after separate MAPC negotiations.• Multiple BSSID Sets: If an AP is a member of a multiple BSSID set, the AP ID value assigned by the AP is greater than 2m, where m is the value carried in the MaxBSSID Indicator field of the Multiple BSSID element advertised by the AP.Docket No.: 25-3025PCT• AP MLD Sets: If an AP is affiliated with an AP MLD that has at least two affiliated APs where each is a member of a multiple BSSI D set, the AP I D value assigned by any AP is greater than 2m, where m is the maximum value indicated by the MaxBSSID Indicator field in each of the Multiple BSSID elements corresponding to the affiliated APs.• MLD Group Addressing: An AP affiliated with an AP MLD assigning an AP ID value also satisfies requirements for AP MLD operation for group addressed frames.
[0299] To assign an AP ID to another AP, an AP includes the AP ID field in a MAPC element. A MAPC requesting AP does not include the AP ID field in the MAPC element carried in a transmitted MAPC Negotiation Request frame, unless the MAPC requesting AP and the MAPC responding AP do not have an established MAPC agreement for any of the Co-BF, Co-SR, or Co-TDMA schemes and the MAPC requesting AP is requesting a new agreement for one of those schemes.
[0300] Similarly, a MAPC responding AP does not include the AP ID field in the MAPC element carried in a transmitted MAPC Negotiation Response frame, unless the two APs do not have an established MAPC agreement for Co-BF, Co-SR, or Co-TDMA and the responding AP is accepting a new agreement for one of those schemes.
[0301] Upon successful transmission or reception of a MAPC Negotiation Response frame containing an AP ID field, the assignment of AP ID values included in the response and the corresponding request is established. If the MAPC responding AP rejects all requests for new agreements and no previous agreements exist, the AP ID assignment fails, and the MAPC responding AP does not assign an AP ID.
[0302] The AP IDs assigned by the MAPC requesting AP and the MAPC responding AP are no longer valid if all established agreements for Co-BF, Co-SR, and Co-TDMA cease to exist between the two APs. When a MAPC requesting AP tears down all such agreements, the mutually assigned AP IDs are released and the values can be reassigned.
[0303] To request a parameter update for an established MAPC agreement, the MAPC requesting AP sets the MAPC Operation Type field to 1 in the MAPC Scheme Request field that carries the request. If the MAPC Operation Type field is set to 1 , the MAPC Request Parameter Set is included according to the rules defined for each specific MAPC scheme.
[0304] When an AP requests an update for an established agreement, the AP sets the AP ID Present field and the MAPC Capabilities Present field of the MAPC Control field of the MAPC element to 0. The AP sets the MAPC Parameters Present field of the MAPC Control field of the MAPC element to 1 if the AP intends to update its MAPC parameters. Note: MAPC capabilities and the assigned AP ID are static attributes of the transmitting AP and cannot be updated as part of an agreement update. Only MAPC parameters can be updated through this procedure.
[0305] To accept, reject, or reject with a suggestion for alternative parameters for an update of an existing MAPC agreement, the MAPC responding AP follows the general procedures for MAPC agreement negotiation. If the MAPC responding AP rejects the update by setting the MAPC Operation Type field to 4 or 5, the agreement update procedure fails and the parameters of the currently established MAPC agreement are not updated.
[0306] To request the teardown of an established agreement, the MAPC requesting AP sets the MAPC Operation Type field to 2 in the MAPC Scheme Request field that carries the request. If the MAPC Operation Type field is set to 2, the MAPC Request Parameter Set field is not included.Docket No.: 25-3025PCT
[0307] When an AP requests a teardown of an established agreement, the AP sets the AP ID Present field, the MAPC Capabilities Present field, and the MAPC Parameters Present field of the MAPC Control field of the MAPC element to 0. The MAPC responding AP accepts the request to teardown an existing MAPC agreement by following the general procedures for MAPC agreement negotiation.
[0308] An AP can provide information about one or more traffic flows within its BSS that the AP intends to serve during a portion of the TXOP that is coordinated with a peer AP with which the AP has established a MAPC agreement. Such information can help a coordinating AP that has obtained a TXOP determine which peer AP(s) to poll or invite during the obtained TXOP.
[0309] An AP that intends to provide information related to its traffic flows includes the Traffic Profile subelement in the MAPC element carried within the MAPC Negotiation Request frame or the MAPC Negotiation Response frame transmitted to a peer AP. An AP does not include the Traffic Profile subelement in a MAPC Discovery Request frame or MAPC Discovery Response frame.
[0310] An AP transmits an unsolicited individually addressed MAPC Notification frame (with the MAPC Notification Type field set to 0) to a peer AP when the AP intends to add, delete, or update one or more traffic flows for consideration. When including the MAPC element in this notification:• The AP ID Present field, MAPC Capabilities Present field, and MAPC Parameters Present field of the MAPC Control field are set to 0.• The MAPC Notification frame does not solicit a Management frame as a response.• The AP can consolidate updates to multiple traffic flows into a single notification for efficient medium utilization.
[0311] Each traffic flow is represented by a QoS Characteristics element.• Presence Bitmap: An AP may set the bit corresponding to the Service Start Time field or the Medium Time field in the Presence Bitmap Of Additional Parameters field to 1 to indicate their presence. The rest of the fields in the bitmap are set to 0 and their corresponding fields are not included.• Operations: The AP indicates the operation (add, delete, or update) via the MAPC Operation field of the Control field in the element. If the MAPC Operation field is set to 0 (Delete), the AP does not include any fields following the Control Info field.
[0312] Constraints and Usage:• Flow Limits: An AP does not exceed the total number of traffic flows provided to a peer AP beyond the value indicated by the Max Traffic Flows field of the MAPC element transmitted by that peer AP.• Polling Decisions: An AP that has established a MAPC agreement may consider the traffic information provided by the peer AP when deciding whether to poll or invite the peer AP during a TXOP obtained for a MAPC operation. • Data Purging: An AP purges traffic information related to a peer AP when all MAPC agreements for that peer AP are torn down.Docket No.: 25-3025PCT
[0313] In an embodiment, an AP or STA in accordance with the above-described embodiments (e.g., any AP or STA as described in FIGS. 3-18 or 25) may perform operations according to Co-RTWT 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.
[0314] The coordinated restricted target wake time (Co-RTWT) procedure enables an access point (AP) to coordinate selected restricted target wake time (RTWT) schedules with non-colocated overlapping basic service set (OBSS) APs. The Co-RTWT procedure further enables an AP to obtain extended protection for selected RTWT schedules from noncolocated OBSS APs and their respective basic service sets (BSSs).
[0315] A Co-RTWT coordinating AP is an AP with the dotHCoRTWTOptionlmplemented parameter equal to true that obtains extended protection for one or more selected RTWT schedules from a peer AP. To obtain extended protection for selected RTWT schedules, a Co-RTWT coordinating AP establishes corresponding Co-RTWT agreements with the peer AP. These agreements may be established via Co-RTWT negotiations or via other means
[0316] Co-RTWT negotiations to establish, update, or tear down Co-RTWT agreements are performed according to multi-AP coordination (MAPC) agreement negotiation rules and Co-RTWT negotiation rules.
[0317] A Co-RTWT coordinated AP is an AP with the dot1 ICoRTWTOptionlmplemented parameter equal to true that extends protection for RTWT schedules of a Co-RTWT coordinating AP. This protection is extended after establishing corresponding Co-RTWT agreements with the Co-RTWT coordinating AP and by following Co-RTWT announcement rules and transmission opportunity (TXOP) and backoff procedure rules for Co-RTWT.
[0318] An AP with the dot11 CoRTWTOptionlmplemented parameter equal to true can establish a Co-RTWT agreement by means that do not follow the common procedures for multi-AP coordination schemes. For example:• A Co-RTWT coordinated AP can be configured by a network to extend protection for RTWT schedules of another Co-RTWT coordinating AP in the same or different administrative domain. In this instance, the APs might be within the same extended service set (ESS) or different ESSs.• A Co-RTWT coordinated AP may listen to the Beacon frame of another Co-RTWT coordinating AP in the same ESS and extend protection for RTWT schedules that are announced in that Beacon frame.
[0319] A multi-AP coordination (MAPC) requesting AP that follows MAPC agreement negotiation rules to establish, update, or tear down Co-RTWT agreements with a MAPC responding AP follows the additional rules defined in this subclause.
[0320] Similarly, a MAPC responding AP that responds to a MAPC Negotiation Request frame from a MAPC requesting AP for Co-RTWT agreements and follows the MAPC agreement negotiation rules follows the additional rules defined in this subclause.
[0321] The MAPC requesting AP includes a Co-RTWT profile in the MAPC element carried in the MAPC Negotiation Request frame transmitted to the MAPC responding AP. The Co-RTWT profile includes one or more MAPC Scheme Request fields in the MAPC Scheme Request Set field, each corresponding to an RTWT schedule.
[0322] For each MAPC Scheme Request field carried in the MAPC Scheme Request Set field of the Co-RTWT profile:Docket No.: 25-3025PCT• The MAPC Per-Scheme Info Present field of the MAPC Request Control field is set to 1.• The Broadcast TWT ID field of the MAPC Per-Scheme Info field identifies the RTWT schedule. This field is set to the value of the Broadcast TWT I D field of the Restricted TWT Parameter Set field corresponding to the RTWT schedule announced by the Co-RTWT coordinating AP in its own BSS.• The MAPC Operation Type field in the MAPC Request Control field is set to:o 0 to establish a new Co-RTWT agreement.o 1 to update an existing Co-RTWT agreement.o 2 to teardown an existing Co-RTWT agreement.
[0323] The MAPC Operation Type field is not set to 1 or 2 if a Co-RTWT agreement is not yet established with the MAPC responding AP for the RTWT schedule identified by the Broadcast TWT ID field. The MAPC Operation Type field is not set to 0 if a Co-RTWT agreement is already established with the MAPC responding AP for that specific RTWT schedule.
[0324] If the MAPC Operation Type is set to 0 or 1, the MAPC Request Parameter Set field is included in the MAPC Scheme Request field. This field specifies the corresponding Co-RTWT Parameter Set field in accordance with the Restricted TWT Parameter Set field corresponding to the RTWT schedule announced by the Co-RTWT coordinating AP in its own BSS.
[0325] For each MAPC Scheme Request field included in the MAPC Negotiation Request frame, the MAPC responding AP includes a corresponding MAPC Scheme Request field in the MAPC Negotiation Response frame.
[0326] In the MAPC Negotiation Response frame:• The Broadcast TWT ID field of the MAPC Per-Scheme Info field is set to the value of the Broadcast TWT ID field from the original request.• When the MAPC responding AP provides a response for a specific RTWT schedule by setting the MAPC Operation Type field to 5, the MAPC Request Parameter Set field containing suggested parameters for the Co-RTWT agreement is included.
[0327] Each Co-RTWT agreement is uniquely identified by the tuple of <MAC ID TWT address, broadcast*. In this tuple:• The MAC address is the address of the MAPC requesting AP.• The broadcast TWT I D is the value carried in the MAPC Scheme Request field corresponding to the agreement within the Co-RTWT profile.• The broadcast TWT ID is greater than 0.
[0328] As part of extending protection for restricted target wake time (RTWT) schedules corresponding to established Co-RTWT agreements, a Co-RTWT coordinated AP advertises active coordinated RTWT schedules in its transmitted Beacon frames if the Co-RTWT coordinated AP has at least one associated STA that supports RTWT. Associated STAsDocket No.: 25-3025PCTthat support RTWT follow the established rules for transmission opportunity (TXOP) and backoff procedures for RTWT service periods (SPs).
[0329] To advertise active coordinated RTWT schedules of a Co-RTWT coordinating AP, the Co-RTWT coordinated AP announces information about these schedules by including corresponding Restricted TWT Parameter Set fields in the Broadcast TWT element contained in Management frames.
[0330] When a Co-RTWT coordinated AP advertises an active coordinated RTWT schedule, the AP includes a Restricted TWT Parameter Set field in the Broadcast TWT element with the following specific values:• The Restricted TWT Schedule Info field is set to 3.• The Broadcast TWT ID field is set to 31.
[0331] In a co-hosted BSSID set, if one Co-RTWT coordinated AP advertises an active coordinated RTWT schedule, all other APs in the same co-hosted BSSID set are also Co-RTWT coordinated APs and advertise the same RTWT schedule using the values specified above.
[0332] A Co-RTWT coordinated AP sets the following parameters within the Restricted TWT Parameter Set field: • TWT Wake Interval Exponent and Mantissa: These fields are set to the corresponding values of the RTWT schedule of the Co-RTWT coordinating AP.• Target Wake Time: The Target Wake Time field and the four most significant bits (MSBs) of the Nominal Minimum TWT Wake Duration / Target Wake Time Extension field are set according to RTWT announcement rules. These values correspond to the start time of the RTWT scheduled to occur after the Co-RTWT coordinated AP has queued the frame containing the TWT element for transmission. The start time value is obtained by converting the start time of the Co-RTWT coordinating AP's RTWT schedule to the Co-RTWT coordinated AP's local Timing Synchronization Function (TSF).• Broadcast TWT Persistence: This field is set to the number of the Co-RTWT coordinated AP’s target beacon transmission times (TBTTs) for which the RTWT schedule is expected to exist, counting forward from the current TBTT. The Co-RTWT coordinated AP determines this value to include the TBTT immediately following the time the schedule ceases to exist, based on the Broadcast TWT Persistence field of the most recent RTWT schedule from the Co-RTWT coordinating AP.
[0333] The Co-RTWT coordinated AP may change the Broadcast TWT Persistence field for any Broadcast TWT within any transmitted TWT element. Note: A non-AP STA does not request membership in an RTWT schedule advertised by the RTWT scheduling AP if the Restricted TWT Schedule Info field is equal to 3. Any TSF synchronization between a Co-RTWT coordinating AP and a Co-RTWT coordinated AP is considered outside the scope of this specification.
[0334] As part of extending protection for restricted target wake time (RTWT) schedules corresponding to established Co-RTWT agreements, a Co-RTWT coordinated AP acting as a transmission opportunity (TXOP) holder ensures that its TXOP, whether obtained on the primary channel or a non-primary channel access (NPCA) primary channel, ends before the start time of any active coordinated RTWT service period (SP). The following exceptions apply:Docket No.: 25-3025PCT• Reciprocal Agreements: If the Co-RTWT coordinated AP is a TXOP holder within an ongoing RTWT SP advertised in its own BSS, and it also holds a Co-RTWT agreement as a coordinating AP with the same peer (acting as a coordinated AP), the Co-RTWT coordinated AP should end its TXOP.• PHYLEN NPCA: If the Co-RTWT coordinated AP performs PHYLEN NPCA based on a physical layer protocol data unit (PPDU) transmitted by the Co-RTWT coordinating AP or an associated non-AP STA, and the end time of that PPDU occurs after the start of the RTWT SP, the Co-RTWT coordinated AP may continue its TXOP.• Non-Overlapping Channels: If the Co-RTWT coordinated AP's TXOP obtained via the NPCA primary channel occupies channels that do not overlap with the BSS operating channels of the Co-RTWT coordinating AP, the Co-RTWT coordinated AP may continue its TXOP.
[0335] Before starting the transmission of any PPDU within a TXOP on either the primary or NPCA primary channel, the Co-RTWT coordinated AP checks if sufficient time remains for the frame exchange to complete prior to the start of the active coordinated RTWT SP. If sufficient time is not available, the Co-RTWT coordinated AP defers transmission by selecting a random backoff count using the current contention window (C W[AC]) without advancing to the next CW value. This deferral does not affect the Quality of Service Retry Counter (QSRC[AC]). The following exceptions apply:• Reciprocal Agreements: If the Co-RTWT coordinated AP is a TXOP holder within an ongoing RTWT SP in its own BSS and holds a reciprocal Co-RTWT agreement with the peer AP, the Co-RTWT coordinated AP should defer transmission.• PHYLEN NPCA: If the Co-RTWT coordinated AP performs PHYLEN NPCA based on a PPDU from the Co-RTWT coordinating AP (or its associated STA) and the PPDU ends after the RTWT SP start time, the Co-RTWT coordinated AP may avoid deferring transmissions.• Non-Overlapping Channels: If the TXOP occupies channels that do not overlap with the Co-RTWT coordinating AP’s BSS operating channels, the Co-RTWT coordinated AP may avoid deferring transmissions.
[0336] Note: A Co-RTWT requesting AP and its associated non-EHT STAs (or EHT STAs with RTWT options disabled) are not expected to terminate a TXOP before the start time of the Co-RTWT requesting AP's own RTWT SP.
Claims
Docket No.: 25-3025PCTCLAIMSWhat is claimed is:
1. A method comprising:receiving, by a first access point (AP) from a second AP, a first frame requesting that the first AP extend protection to a restricted target wake time (r-TWT) schedule of the second AP;transmitting, by the first AP to the second AP, a second frame indicating that the first AP extends protection to the r-TWT schedule of the second AP, wherein, based on extending protection to the r-TWT schedule, the first AP terminates / ends an obtained transmission opportunity (TXOP) before a start time of a service period (SP) of the r-TWT schedule; andbased on the first AP not receiving an expected third frame from the second AP within a first duration, stopping extending protection, by the first AP, to the r-TWT schedule of the second AP wherein the first duration extends from at least one of:receipt of a fourth frame by the first AP from the second AP; ortransmission of a fifth frame by the first AP to the second AP.
2. A method comprising:based on a first station (STA) not receiving a third frame from a second STA within a first duration, stopping extending protection, by the first STA, to a restricted target wake time (r-TWT) schedule of the second STA, wherein the first duration extends from at least one of:receipt of a fourth frame by the first STA from the second STA; ortransmission of a fifth frame by the first STA to the second STA.
3. The method of claim 2, wherein the first STA comprises a first access point (AP) and the second STA comprises a second AP.
4. The method of claim 3, wherein the first STA comprises a coordinated AP of a multi-AP group comprising the first AP and the second AP.
5. The method of claim 4, wherein the second AP comprises a coordinating AP of the multi-AP group comprising the first AP and the second AP.
6. The method of any of claims 3-4, further comprising receiving, by the first AP from the second AP, a first frame requesting that the first AP extend protection to the r-TWT schedule of the second AP.
7. The method of claim 6, further comprising transmitting, by the first AP to the second AP and in response to the first frame, a second frame indicating that the first AP extends protection to the r-TWT schedule.
8. The method of any of claims 3-7, wherein the third frame comprises an expected third frame.
9. The method of any of claims 3-8, wherein the first duration extends from receipt of the fourth frame by the first AP from the second AP.Docket No.: 25-3025PCT10. The method of claim 9, wherein the fourth frame comprises a first beacon frame, wherein the third frame comprises a second beacon frame, and wherein the first duration extends from receipt of the first beacon frame to expected receipt of the second beacon frame.
11. The method of claim 10, wherein the first duration comprises a timeout duration after receipt of the first beacon frame.
12. The method of any of claims 10-11, wherein the first duration is based on a target beacon transmission time (TBTT) for the second AP.
13. The method of claim 12, further comprising: estimating, by the first AP, the TBTT for the second AP based on one or more beacon frames previously received by the first AP from the second AP.
14. The method of any of claims 3-8, wherein the first duration extends from transmission of the fifth frame by the first AP to the second AP.
15. The method of claim 14, wherein the fifth frame comprises a multi-AP coordination (MAPC) request frame.
16. The method of any of claims 14-15, wherein the fifth frame indicates teardown of a MAPC agreement.
17. The method of claim 16, wherein the MAPC agreement comprises a coordinated r-TWT (Co-RTWT) agreement.
18. The method of any of claims 14-17, wherein the first AP transmits the fifth frame based on not receiving an expected sixth frame from the second AP.
19. The method of claim 18, wherein the sixth frame comprises a beacon frame.
20. A method comprising:receiving, by a first access point (AP) from a second AP, a first frame requesting that the first AP extend protection to a restricted target wake time (r-TWT) schedule of the second AP;transmitting, by the first AP to the second AP, a second frame indicating that the first AP extends protection to the r-TWT schedule of the second AP, wherein, based on extending protection to the r-TWT schedule, the first AP temninates / ends an obtained transmission opportunity (TXOP) before a start time of a service period (SP) of the r-TWT schedule;based on the first AP not receiving any frame from the second AP within a first duration from a last received frame from the second AP, transmitting, by the first AP, a third frame that triggers one or more stations (STAs), associated with the first AP, to determine whether the one or more STAs receive a fourth frame from the second AP within a second duration from the one or more STAs receiving the third frame; receiving, by the first AP from the one or more STAs, one or more fifth frames in response to the third frame; andstopping extending protection, by the first AP, to the r-TWT schedule of the second AP based on: the one or more fifth frames indicating that the one or more STAs do not receive the fourth frame from the second AP within the second duration; andthe first AP not receiving any frame from the second AP within the second duration.
21. A method comprising:Docket No.: 25-3025PCTreceiving, by a first access point (AP) from a first station (STA), a first frame indicating that the first STA does not receive a second frame from a second AP; andbased on the first frame, stopping extending protection, by the first AP, to a restricted target wake time (r- TWT) schedule of the second AP.
22. The method of claim 21 , wherein the first AP comprises a coordinated AP of a multi-AP group comprising the first AP and the second AP.
23. The method of claim 22, where the second AP comprises a coordinating AP of the multi-AP group comprising the first AP and the second AP.
24. The method of any of claims 21-23, further comprising receiving, by the first AP from the second AP, a third frame requesting that the first AP extend protection to the r-TWT schedule of the second AP.
25. The method of claim 24, further comprising transmitting, by the first AP to the second AP and in response to the third frame, a fourth frame indicating that the first AP extends protection to the r-TWT schedule.
26. The method of any of claims 21-25, wherein based on the first AP not receiving a fifth frame from the second AP within a first duration from a last received frame, by the first AP from the second AP, the first AP transmits, to the first STA, a sixth frame.
27. The method of claim 26, further comprising transmitting, by the first AP to the second AP, the first duration.
28. The method of any of claims 26-27, further comprising receiving, by the first AP from the second AP, the first duration.
29. The method of claim 26, wherein the first duration is pre-defined.
30. The method of any of claims 26-29, wherein the sixth frame indicates a request for the first STA to determine whether the first STA receives the second frame from the second AP.
31. The method of claim 30, wherein the sixth frame indicates a request for the first STA to monitor reception of the second frame within a second duration from the first STA receiving the sixth frame.
32. The method of claim 31 , further comprising transmitting, by the first AP to the first STA, a seventh frame indicting a request to the first STA to indicate whether the first STA has received the second frame during the second duration.
33. The method of claim 32, wherein the first AP receives the first frame in response to the seventh frame.
34. The method of any of claims 32-33, wherein the seventh frame is an individually addressed control frame.
35. The method of any of claims 32-33, wherein the seventh frame is a broadcast frame or a multicast frame.
36. The method of claim 31 , wherein the sixth frame further indicates a request for the first STA to report whether the first STA receives the second frame during the second duration.
37. The method of claim 31 , wherein the sixth frame further indicates a request for the first STA to report that the first STA does not receive the second frame during the second duration.
38. The method of any of claims 36-37, wherein the first AP receives the first frame in response to the sixth frame.
39. The method of any of claims 31 -38, wherein the first AP receives the first frame during the second duration.Docket No.: 25-3025PCT40. The method of any of claims 31 -38, wherein the first AP receives the first frame after the second duration.
41. The method of any of claims 31 -40, further comprising transmitting, by the first AP to the second AP, the second duration42. The method of any of claims 31-41, further comprising receiving, by the first AP from the second AP, the second duration.
43. The method of any of claims 31-40, wherein the second duration is pre-defined.
44. The method of any of claims 26-43, wherein the sixth frame is an individually addressed control frame.
45. The method of any of claims 26-43, wherein the sixth frame is a broadcast / mu Iticast frame.
46. The method of any of claim 21-45, wherein the first STA is associated with the first AP.
47. The method of any of claims 21-46, further comprising receiving by the first AP from a second STA an eighth frame indicating that the second STA does not receive a ninth from the second AP.
48. The method of claim 47, wherein the first STA and the second STA comprise all STAs associated with the first AP.
49. The method of any of claims 47-48, wherein based on the first frame and the eighth frame, the first AP stops extending protection to the r-TWT schedule of the second AP.
50. The method of any of claims 21-49, wherein the first AP stops extending protection to the r-TWT schedule of the second AP based on all STAs associated with the first AP not receiving any frames from the second AP during a third duration occurring while the first AP extends protection to the r-TWT schedule of the second AP.
51. The method of any of claims 21-45, wherein the first STA comprises a third AP.
52. The method of claim 51 , wherein the third AP is part of a multi-AP group comprising the first AP, the second AP, and the third AP.
53. The method of claim 52, wherein the third AP comprises a coordinated AP of a multi-AP group comprising the first AP, the second AP, and the third AP.
54. A method comprising:transmitting, by a first access point (AP) to a station (STA), a first frame indicating a request for the STA to monitor reception of a second frame from a second AP within a duration; andbased on not receiving, by the first AP, a third frame, from the STA indicating that the STA received the second frame from the second AP, stopping extending protection, by the first AP, to a restricted target wake time (r-TWT) schedule of the second AP.
55. A method comprising:receiving, by a first access point (AP) from a station (STA), a first frame indicating that the STA does not receive a restricted target wake time (r-TWT) schedule from a second AP; andbased on the first frame, stopping extending protection, by the first AP, to a restricted target wake time (r- TWT) schedule of the second AP.Docket No.: 25-3025PCT56. The method of claim 55, wherein the first frame indicates that the STA received a beacon frame from the second AP.
57. The method of claim 56, wherein the first frame further indicates that the beacon frame did not include the r-TWT schedule.
58. The method of any of claims 55-57, further comprising transmitting, by the first AP to the STA, a second frame indicating a request for the STA to monitor reception of a beacon frame within a duration.
59. The method of claim 58, wherein the first AP receives the first frame in response to transmitting the second frame.
60. A method comprising:receiving, by a first access point (AP) from a second AP, a beacon frame; andbased on the beacon frame not including a restricted target wake time (r-TWT) schedule, stopping extending protection, by the first AP, to the r-TWT schedule of the second AP.
61. The method of claim 60, wherein the first AP comprises a coordinated AP of a multi-AP group comprising the first AP and the second AP.
62. The method of claim 61 , where the second AP comprises a coordinating AP of the multi-AP group comprising the first AP and the second AP.
63. The method of any of claims 60-62, further comprising receiving, by the first AP from the second AP, a first frame requesting that the first AP extend protection to the r-TWT schedule of the second AP.
64. The method of claim 63, further comprising transmitting, by the first AP to the second AP and in response to the first frame, a second frame indicating that the first AP extends protection to the r-TWT schedule.
65. The method of claim 64, wherein at least one of the first frame or the second frame indicates an agreement to stop extending protection, to the r-TWT schedule of the second AP, based on receiving a beacon frame, from the second AP, not including the r-TWT schedule.
66. A method comprising:receiving, by a station (STA) from a first access point (AP) with which the STA is associated, a first frame advertising that the first AP extends protection to a restricted target wake time (r-TWT) schedule of a second AP, wherein, based on extending protection to the r-TWT schedule, the STA terminates / ends an obtained transmission opportunity (TXOP) before a start time of a service period (SP) of the r-TWT schedule; receiving, by the STA from the first AP, a second frame;determining, by the STA and based on receiving the second frame, whether the STA receives a third frame from the second AP within a duration from the STA receiving the second frame; and transmitting, by the STA to the first AP, a fourth frame indicating that the STA does not receive the third frame from the second AP within the duration.
67. A method comprising:Docket No.: 25-3025PCTtransmitting, by a station (STA) to a first access point (AP), a first frame indicating that the STA does not receive a second frame from a second AP; andreceiving, by the STA from the first AP, a third frame indicating stopping extending protection, by the first AP, to a restricted target wake time (r-TWT) schedule of the second AP.
68. The method of claim 67, further comprising receiving, by the STA from the first AP, a fourth frame indicating a request for the STA to determine whether the STA receives the second frame from the second AP.
69. The method of claim 68, wherein the fourth frame indicates a request for the STA to monitor reception of the second frame within a second duration from the STA receiving the fourth frame.
70. The method of claim 69, further comprising receiving, by the STA from the first AP, a fifth frame indicting a request to the STA to indicate whether the STA has received the second frame during the second duration.
71. The method of claim 70, wherein the STA transmits the first frame in response to the fifth frame.
72. The method of any of claims 70-71 , wherein the fifth frame is an individually addressed control frame.
73. The method of any of claims 70-71, wherein the fifth frame is a broadcast frame or a multicast frame.
74. The method of claim 69, wherein the fourth frame further indicates a request for the STA to report whether the first STA receives the second frame during the second duration.
75. The method of claim 69, wherein the fourth frame further indicates a request for the STA to report that the STA does not receive the second frame during the second duration.
76. The method of any of claims 74-75, wherein the STA transmits the first frame in response to the fourth frame.
77. The method of any of claims 69-76, wherein the STA transmits the first frame during the second duration.
78. The method of any of claims 69-76, wherein the STA transmits the first frame after the second duration.
79. The method of any of claims 69-78, wherein the second duration is pre-defined.
80. The method of any of claims 69-78, further comprising receiving, by the STA from the first AP, the second duration.
81. The method of any of claims 69-78, further comprising transmitting, by the STA to the first AP, the second duration.
82. The method of any of claims 68-81, wherein the fourth frame is an individually addressed control frame.
83. The method of any of claims 68-81, wherein the fourth frame is a broadcast / multicast frame.
84. The method of any of claims 67-83, wherein the STA is associated with the first AP.
85. The method of any of claims 67-84, wherein the third frame comprises a beacon frame.
86. The method of any of claims 69-85, wherein the first frame indicates a third duration.
87. The method of any of claims 86, wherein the third duration and the second duration are the same.
88. A method comprising:transmitting, by a station (STA) to a first access point (AP), a first frame indicating that the STA does not receive a restricted target wake time (r-TWT) schedule from a second AP; andDocket No.: 25-3025PCTreceiving, by the STA from the first AP, a second frame indicating stopping extending protection, by the first AP, to the r-TWT schedule of the second AP.
89. The method of claim 88, further comprising receiving, by the STA from the second AP, a beacon frame.
90. The method of claim 89, further comprising determining, by the STA, that the beacon frame does not include the r-TWT schedule of the second AP.
91. The method of any of claims 89-90, wherein the first frame further indicates that the beacon frame did not include the r-TWT schedule.
92. The method of any of claims 88-91, further comprising receiving, by the STA from the first AP, a second frame indicating a request for the STA to monitor reception of a beacon frame within a duration.
93. The method of claim 92, wherein the STA transmits the first frame in response to receiving the second frame.
94. 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-93.
95. 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-93.
