WO2018160257A1

WO2018160257A1 - Delegation of autonomy based on network conditions in a multiple access point environment

Info

Publication number: WO2018160257A1
Application number: PCT/US2017/067620
Authority: WO
Inventors: Preston Joel HUNT; Carlos Cordeiro; Cheng Chen
Original assignee: Intel IP Corporation
Priority date: 2017-03-01
Filing date: 2017-12-20
Publication date: 2018-09-07
Also published as: DE112017007168T5

Abstract

Methods, computer readable media, and apparatuses for delegation of autonomy based on network conditions in a multiple access point (AP) environment are disclosed. An apparatus is disclosed comprising processing circuitry, where the processing circuity is configured to decode a first Physical Layer Convergence Procedure (PLCP) Protocol Data Unit (PPDU) from a second AP, the first PPDU including an autonomy grant, the autonomy grant indicating a function and a condition, and where the autonomy grant indicates that when the condition is met that the first access point is authorized to perform the function. The processing circuitry may be further configured to determine whether the condition is met. The processing circuitry may be further configured to decode a second PPDU from a station, the second PPDU requesting the function be performed for the station, and if the determination is that the condition is met, perform the function for the station.

Description

DELEGATION OF AUTONOMY BASED ON NETWORK CONDITIONS IN A MULTIPLE ACCESS POINT ENVIRONMENT

PRIORITY CLAIM

[0001] This application claims the benefit of priority to United States Provisional Patent Application Serial No. 62/465,365, filed March 1, 2017, which is incorporated herein by reference in its entirety.

TECHNICAL FIELD

[0002] Embodiments pertain to wireless networks and wireless communications. Some embodiments relate to wireless local area networks (WLANs) and Wi-Fi networks including networks operating in accordance with the IEEE 802.1 1 family of standards. Some embodiments relate to IEEE 802.1 lax. Some embodiments relate to methods, computer readable media, and apparatus for delegation of autonomy based on network conditions in a multiple access point (AP) environment.

BACKGROUND

[0003] Efficient use of the resources of a wireless local-area network

(WLAN) is important to provide bandwidth and acceptable response times to the users of the WLAN. However, often there are many devices trying to share the same resources and some devices may be limited by the communication protocol they use or by their hardware bandwidth. Moreover, wireless devices may need to operate with both newer protocols and with legacy device protocols. BRIEF DESCRIPTION OF THE DRAWINGS

[0004] The present disclosure is illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like references indicate similar elements and in which:

[0005] FIG. 1 is a block diagram of a radio architecture in accordance with some embodiments;

[0006] FIG. 2 illustrates a front-end module circuitry for use in the radio architecture of FIG. 1 in accordance with some embodiments;

[0007] FIG. 3 illustrates a radio IC circuitry for use in the radio architecture of FIG. 1 in accordance with some embodiments;

[0008] FIG. 4 illustrates a baseband processing circuitry for use in the radio architecture of FIG.1 in accordance with some embodiments;

[0009] FIG. 5 illustrates a WLAN in accordance with some

embodiments;

[0010] FIG. 6 illustrates a block diagram of an example machine upon which any one or more of the techniques (e.g., methodologies) discussed herein may perform;

[0011] FIG. 7 illustrates a block diagram of an example wireless device upon which any one or more of the techniques (e.g., methodologies or operations) discussed herein may perform;

[0012] FIG. 8 illustrates a system for delegation of autonomy based on network conditions in a multiple AP environment;

[0013] FIG. 9 illustrates a multi-AP controller in accordance with some embodiments;

[0014] FIG. 10 illustrates a multi-AP agent in accordance with some embodiments;

[0015] FIG. 11 illustrates an autonomy grant information element (IE) in accordance with some embodiments;

[0016] FIG. 12 illustrates capabilities information element in accordance with some embodiments; [0017] FIG . 13 illustrates a service request in accordance with some embodiments;

[0018] FIG . 14 illustrates a method for delegation of autonomy based on network conditions in a multiple AP environment in accordance with some embodiments;

[0019] FIG . 15 illustrates a method for delegation of autonomy based on network conditions in a multiple AP environment in accordance with some embodiments;

[0020] FIG . 16 illustrates a method for delegation of autonomy based on network conditions in a multiple AP environment in accordance with some embodiments; and

[0021] FIG . 17 illustrates a method for delegation of autonomy based on network conditions in a multiple AP environment in accordance with some embodiments.

DESCRIPTION

[0022] The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of other embodiments. Embodiments set forth in the claims encompass all available equivalents of those claims.

[0023] FIG. 1 is a block diagram of a radio architecture 100 in accordance with some embodiments. Radio architecture 100 may include radio front-end module (FEM) circuitry 104, radio IC circuitry 106 and baseband processing circuitry 108. Radio architecture 100 as shown includes both Wireless Local Area Network (WLAN) functionality and Bluetooth (BT) functionality although embodiments are not so limited. In this disclosure, "WLAN" and "Wi-Fi" are used interchangeably.

[0024] FEM circuitry 104 may include a WLAN or Wi-Fi FEM circuitry

104A and a Bluetooth (BT) FEM circuitry 104B. The WLAN FEM circuitry 104A may include a receive signal path comprising circuitry configured to operate on WLAN RF signals received from one or more antennas 101, to amplify the received signals and to provide the amplified versions of the received signals to the WLAN radio IC circuitry 106A for further processing. The BT FEM circuitry 104B may include a receive signal path which may include circuitry configured to operate on BT RF signals received from one or more antennas 101, to amplify the received signals and to provide the amplified versions of the received signals to the BT radio IC circuitry 106B for further processing. FEM circuitry 104A may also include a transmit signal path which may include circuitry configured to amplify WLAN signals provided by the radio IC circuitry 106A for wireless transmission by one or more of the antennas 101. In addition, FEM circuitry 104B may also include a transmit signal path which may include circuitry configured to amplify BT signals provided by the radio IC circuitry 106B for wireless transmission by the one or more antennas. In the embodiment of FIG. 1, although FEM 104A and FEM 104B are shown as being distinct from one another, embodiments are not so limited, and include within their scope the use of an FEM (not shown) that includes a transmit path and/or a receive path for both WLAN and BT signals, or the use of one or more FEM circuitries where at least some of the FEM circuitries share transmit and/or receive signal paths for both WLAN and BT signals.

[0025] Radio IC circuitry 106 as shown may include WLAN radio IC circuitry 106A and BT radio IC circuitry 106B. The WLAN radio IC circuitry 106A may include a receive signal path which may include circuitry to down- convert WLAN RF signals received from the FEM circuitry 104A and provide baseband signals to WLAN baseband processing circuitry 108A. BT radio IC circuitry 106B may in turn include a receive signal path which may include circuitry to down-convert BT RF signals received from the FEM circuitry 104B and provide baseband signals to BT baseband processing circuitry 108B.

WLAN radio IC circuitry 106A may also include a transmit signal path which may include circuitry to up-convert WLAN baseband signals provided by the WLAN baseband processing circuitry 108 A and provide WLAN RF output signals to the FEM circuitry 104A for subsequent wireless transmission by the one or more antennas 101. BT radio IC circuitry 106B may also include a transmit signal path which may include circuitry to up-convert BT baseband signals provided by the BT baseband processing circuitry 108B and provide BT RF output signals to the FEM circuitry 104B for subsequent wireless transmission by the one or more antennas 101. In the embodiment of FIG. 1, although radio IC circuitries 106A and 106B are shown as being distinct from one another, embodiments are not so limited, and include within their scope the use of a radio IC circuitry (not shown) that includes a transmit signal path and/or a receive signal path for both WLAN and BT signals, or the use of one or more radio IC circuitries where at least some of the radio IC circuitries share transmit and/or receive signal paths for both WLAN and BT signals.

[0026] Baseband processing circuity 108 may include a WLAN baseband processing circuitry 108A and a BT baseband processing circuitry 108B. The WLAN baseband processing circuitry 108A may include a memory, such as, for example, a set of RAM arrays in a Fast Fourier Transform or Inverse Fast Fourier Transform block (not shown) of the WLAN baseband processing circuitry 108A. Each of the WLAN baseband circuitry 108A and the BT baseband circuitry 108B may further include one or more processors and control logic to process the signals received from the corresponding WLAN or BT receive signal path of the radio IC circuitry 106, and to also generate corresponding WLAN or BT baseband signals for the transmit signal path of the radio IC circuitry 106. Each of the baseband processing circuitries 108A and 108B may further include physical layer (PHY) and medium access control layer (MAC) circuitry, and may further interface with application processor 1 11 for generation and processing of the baseband signals and for controlling operations of the radio IC circuitry 106.

[0027] Referring still to FIG. 1, according to the shown embodiment,

WLAN-BT coexistence circuitry 113 may include logic providing an interface between the WLAN baseband circuitry 108A and the BT baseband circuitry 108B to enable use cases requiring WLAN and BT coexistence. In addition, a switch 103 may be provided between the WLAN FEM circuitry 104A and the BT FEM circuitry 104B to allow switching between the WLAN and BT radios according to application needs. In addition, although the antennas 101 are depicted as being respectively connected to the WLAN FEM circuitry 104A and the BT FEM circuitry 104B, embodiments include within their scope the sharing of one or more antennas as between the WLAN and BT FEMs, or the provision of more than one antenna connected to each of FEM 104A or 104B.

[0028] In some embodiments, the front-end module circuitry 104, the radio IC circuitry 106, and baseband processing circuitry 108 may be provided on a single radio card, such as wireless radio card 102. In some other embodiments, the one or more antennas 101, the FEM circuitry 104 and the radio IC circuitry 106 may be provided on a single radio card. In some other embodiments, the radio IC circuitry 106 and the baseband processing circuitry 108 may be provided on a single chip or integrated circuit (IC), such as IC 112.

[0029] In some embodiments, the wireless radio card 102 may include a

WLAN radio card and may be configured for Wi-Fi communications, although the scope of the embodiments is not limited in this respect. In some of these embodiments, the radio architecture 100 may be configured to receive and transmit orthogonal frequency division multiplexed (OFDM) or orthogonal frequency division multiple access (OFDMA) communication signals over a multicarrier communication channel. The OFDM or OFDMA signals may comprise a plurality of orthogonal subcarriers.

[0030] In some of these multicarrier embodiments, radio architecture 100 may be part of a Wi-Fi communication station (STA) such as a wireless access point (AP), a base station or a mobile device including a Wi-Fi device. In some of these embodiments, radio architecture 100 may be configured to transmit and receive signals in accordance with specific communication standards and/or protocols, such as any of the Institute of Electrical and Electronics Engineers (IEEE) standards including, IEEE 802.1 1n-2009, IEEE 802.1 1-2012, IEEE

802.1 1-2016, IEEE 802.1 lac, and/or IEEE 802.1 lax standards and/or proposed specifications for WLANs, although the scope of embodiments is not limited in this respect. Radio architecture 100 may also be suitable to transmit and/or receive communications in accordance with other techniques and standards.

[0031] In some embodiments, the radio architecture 100 may be configured for high-efficiency (HE) Wi-Fi (HEW) communications in accordance with the IEEE 802.1 lax standard. In these embodiments, the radio architecture 100 may be configured to communicate in accordance with an OFDMA technique, although the scope of the embodiments is not limited in this respect.

[0032] In some other embodiments, the radio architecture 100 may be configured to transmit and receive signals transmitted using one or more other modulation techniques such as spread spectrum modulation (e.g., direct sequence code division multiple access (DS-CDMA) and/or frequency hopping code division multiple access (FH-CDMA)), time-division multiplexing (TDM) modulation, and/or frequency-division multiplexing (FDM) modulation, although the scope of the embodiments is not limited in this respect.

[0033] In some embodiments, as further shown in FIG. 1, the BT baseband circuitry 108B may be compliant with a Bluetooth (BT) connectivity standard such as Bluetooth, Bluetooth 4.0 or Bluetooth 5.0, or any other iteration of the Bluetooth Standard. In embodiments that include BT functionality as shown for example in Fig. 1, the radio architecture 100 may be configured to establish a BT synchronous connection oriented (SCO) link and/or a BT low energy (BT LE) link. In some of the embodiments that include functionality, the radio architecture 100 may be configured to establish an extended SCO (eSCO) link for BT communications, although the scope of the embodiments is not limited in this respect. In some of these embodiments that include a BT functionality, the radio architecture may be configured to engage in a BT

Asynchronous Connection-Less (ACL) communications, although the scope of the embodiments is not limited in this respect. In some embodiments, as shown in FIG. 1, the functions of a BT radio card and WLAN radio card may be combined on a single wireless radio card, such as single wireless radio card 102, although embodiments are not so limited, and include within their scope discrete WLAN and BT radio cards

[0034] In some embodiments, the radio-architecture 100 may include other radio cards, such as a cellular radio card configured for cellular (e.g., 3GPP such as LTE, LTE-Advanced or 5G communications).

[0035] In some IEEE 802.1 1 embodiments, the radio architecture 100 may be configured for communication over various channel bandwidths including bandwidths having center frequencies of about 900 MHz, 2.4 GHz, 5 GHz, and bandwidths of about 1 MHz, 2 MHz, 2.5 MHz, 4 MHz, 5MHz, 8 MHz, 10 MHz, 16 MHz, 20 MHz, 40MHz, 80MHz (with contiguous bandwidths) or 80+80MHz (160MHz) (with non-contiguous bandwidths). In some embodiments, a 320 MHz channel bandwidth may be used. The scope of the embodiments is not limited with respect to the above center frequencies however.

[0036] FIG. 2 illustrates FEM circuitry 200 in accordance with some embodiments. The FEM circuitry 200 is one example of circuitry that may be suitable for use as the WLAN and/or BT FEM circuitry 104A/104B (FIG. 1), although other circuitry configurations may also be suitable.

[0037] In some embodiments, the FEM circuitry 200 may include a

TX/RX switch 202 to switch between transmit mode and receive mode operation. The FEM circuitry 200 may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry 200 may include a low -noise amplifier (LNA) 206 to amplify received RF signals 203 and provide the amplified received RF signals 207 as an output (e.g., to the radio IC circuitry 106 (FIG. 1)). The transmit signal path of the circuitry 200 may include a power amplifier (PA) to amplify input RF signals 209 (e.g., provided by the radio IC circuitry 106), and one or more filters 212, such as band-pass filters (BPFs), low-pass filters (LPFs) or other types of filters, to generate RF signals 215 for subsequent transmission (e.g., by one or more of the antennas 101 (FIG. 1))·

[0038] In some dual-mode embodiments for Wi-Fi communication, the

FEM circuitry 200 may be configured to operate in either the 2.4 GHz frequency spectrum, the 5 GHz frequency spectrum, or the 60 GHz frequency spectrum. In these embodiments, the receive signal path of the FEM circuitry 200 may include a receive signal path duplexer 204 to separate the signals from each spectrum as well as provide a separate LNA 206 for each spectrum as shown. In these embodiments, the transmit signal path of the FEM circuitry 200 may also include a power amplifier 210 and a filter 212, such as a BPF, a LPF or another type of filter for each frequency spectrum and a transmit signal path duplexer 214 to provide the signals of one of the different spectrums onto a single transmit path for subsequent transmission by the one or more of the antennas 101 (FIG. 1). In some embodiments, BT communications may utilize the 2.4 GHZ signal paths and may utilize the same FEM circuitry 200 as the one used for WLAN communications.

[0039] FIG. 3 illustrates radio IC circuitry 300 in accordance with some embodiments. The radio IC circuitry 300 is one example of circuitry that may be suitable for use as the WLAN or BT radio IC circuitry 106A/106B (FIG. 1), although other circuitry configurations may also be suitable.

[0040] In some embodiments, the radio IC circuitry 300 may include a receive signal path and a transmit signal path. The receive signal path of the radio IC circuitry 300 may include at least mixer circuitry 302, such as, for example, down-conversion mixer circuitry, amplifier circuitry 306 and filter circuitry 308. The transmit signal path of the radio IC circuitry 300 may include at least filter circuitry 312 and mixer circuitry 314, such as, for example, up- conversion mixer circuitry. Radio IC circuitry 300 may also include synthesizer circuitry 304 for synthesizing a frequency 305 for use by the mixer circuitry 302 and the mixer circuitry 314. The mixer circuitry 302 and/or 314 may each, according to some embodiments, be configured to provide direct conversion functionality. The latter type of circuitry presents a much simpler architecture as compared with standard super-heterodyne mixer circuitries, and any flicker noise brought about by the same may be alleviated for example through the use of OFDM modulation. Fig. 3 illustrates only a simplified version of a radio IC circuitry, and may include, although not shown, embodiments where each of the depicted circuitries may include more than one component. For instance, mixer circuitry 320 and/or 314 may each include one or more mixers, and filter circuitries 308 and/or 312 may each include one or more filters, such as one or more BPFs and/or LPFs according to application needs. For example, when mixer circuitries are of the direct-conversion type, they may each include two or more mixers.

[0041] In some embodiments, mixer circuitry 302 may be configured to down-convert RF signals 207 received from the FEM circuitry 104 (FIG. 1) based on the synthesized frequency 305 provided by synthesizer circuitry 304. The amplifier circuitry 306 may be configured to amplify the down-converted signals and the filter circuitry 308 may include a LPF configured to remove unwanted signals from the down-converted signals to generate output baseband signals 307. Output baseband signals 307 may be provided to the baseband processing circuitry 108 (FIG. 1) for further processing. In some embodiments, the output baseband signals 307 may be zero-frequency baseband signals, although this is not a requirement. In some embodiments, mixer circuitry 302 may comprise passive mixers, although the scope of the embodiments is not limited in this respect.

[0042] In some embodiments, the mixer circuitry 314 may be configured to up-convert input baseband signals 31 1 based on the synthesized frequency 305 provided by the synthesizer circuitry 304 to generate RF output signals 209 for the FEM circuitry 104. The baseband signals 31 1 may be provided by the baseband processing circuitry 108 and may be filtered by filter circuitry 312. The filter circuitry 312 may include a LPF or a BPF, although the scope of the embodiments is not limited in this respect.

[0043] In some embodiments, the mixer circuitry 302 and the mixer circuitry 314 may each include two or more mixers and may be arranged for quadrature down -conversion and/or up-conversion respectively with the help of synthesizer 304. In some embodiments, the mixer circuitry 302 and the mixer circuitry 314 may each include two or more mixers each configured for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 302 and the mixer circuitry 314 may be arranged for direct down- conversion and/or direct up-conversion, respectively. In some embodiments, the mixer circuitry 302 and the mixer circuitry 314 may be configured for superheterodyne operation, although this is not a requirement.

[0044] Mixer circuitry 302 may comprise, according to one embodiment: quadrature passive mixers (e.g., for the in-phase (I) and quadrature phase (Q) paths). In such an embodiment, RF input signal 207 from Fig. 3 may be down- converted to provide I and Q baseband output signals to be sent to the baseband processor

[0045] Quadrature passive mixers may be driven by zero and ninety- degree time -varying LO switching signals provided by a quadrature circuitry which may be configured to receive a LO frequency (fro) from a local oscillator or a synthesizer, such as LO frequency 305 of synthesizer 304 (FIG. 3). In some embodiments, the LO frequency may be the carrier frequency, while in other embodiments, the LO frequency may be a fraction of the carrier frequency (e.g., one-half the carrier frequency, one-third the carrier frequency). In some embodiments, the zero and ninety-degree time-varying switching signals may be generated by the synthesizer, although the scope of the embodiments is not limited in this respect.

[0046] In some embodiments, the LO signals may differ in duty cycle

(the percentage of one period in which the LO signal is high) and/or offset (the difference between start points of the period). In some embodiments, the LO signals may have a 25% duty cycle and a 50% offset. In some embodiments, each branch of the mixer circuitry (e.g., the in-phase (I) and quadrature phase (Q) path) may operate at a 25% duty cycle, which may result in a significant reduction is power consumption.

[0047] The RF input signal 207 (FIG. 2) may comprise a balanced signal, although the scope of the embodiments is not limited in this respect. The I and Q baseband output signals may be provided to low-nose amplifier, such as amplifier circuitry 306 (FIG. 3) or to filter circuitry 308 (FIG. 3).

[0048] In some embodiments, the output baseband signals 307 and the input baseband signals 31 1 may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate

embodiments, the output baseband signals 307 and the input baseband signals 31 1 may be digital baseband signals. In these alternate embodiments, the radio IC circuitry may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry.

[0049] In some dual-mode embodiments, a separate radio IC circuitry may be provided for processing signals for each spectrum, or for other spectrums not mentioned here, although the scope of the embodiments is not limited in this respect.

[0050] In some embodiments, the synthesizer circuitry 304 may be a fractional -N synthesizer or a fractional N/N+1 synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, synthesizer circuitry 304 may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider. According to some embodiments, the synthesizer circuitry 304 may include digital synthesizer circuitry. An advantage of using a digital synthesizer circuitry is that, although it may still include some analog components, its footprint may be scaled down much more than the footprint of an analog synthesizer circuitry. In some embodiments, frequency input into synthesizer circuity 304 may be provided by a voltage controlled oscillator (VCO), although that is not a requirement. A divider control input may further be provided by either the baseband processing circuitry 108 (FIG. 1) or the application processor 1 1 1 (FIG. 1) depending on the desired output frequency 305. In some embodiments, a divider control input (e.g., N) may be determined from a look-up table (e.g., within a Wi-Fi card) based on a channel number and a channel center frequency as determined or indicated by the application processor 1 1 1.

[0051] In some embodiments, synthesizer circuitry 304 may be configured to generate a carrier frequency as the output frequency 305, while in other embodiments, the output frequency 305 may be a fraction of the carrier frequency (e.g., one-half the carrier frequency, one-third the carrier frequency). In some embodiments, the output frequency 305 may be a LO frequency (fLo).

[0052] FIG. 4 illustrates a functional block diagram of baseband processing circuitry 400 in accordance with some embodiments. The baseband processing circuitry 400 is one example of circuitry that may be suitable for use as the baseband processing circuitry 108 (FIG. 1), although other circuitry configurations may also be suitable. The baseband processing circuitry 400 may include a receive baseband processor (RX BBP) 402 for processing receive baseband signals 309 provided by the radio IC circuitry 106 (FIG. 1) and a transmit baseband processor (TX BBP) 404 for generating transmit baseband signals 31 1 for the radio IC circuitry 106. The baseband processing circuitry 400 may also include control logic 406 for coordinating the operations of the baseband processing circuitry 400.

[0053] In some embodiments (e.g., when analog baseband signals are exchanged between the baseband processing circuitry 400 and the radio IC circuitry 106), the baseband processing circuitry 400 may include ADC 410 to convert analog baseband signals received from the radio IC circuitry 106 to digital baseband signals for processing by the RX BBP 402. In these embodiments, the baseband processing circuitry 400 may also include DAC 412 to convert digital baseband signals from the TX BBP 404 to analog baseband signals.

[0054] In some embodiments that communicate OFDM signals or OFDMA signals, such as through baseband processor 108A, the transmit baseband processor 404 may be configured to generate OFDM or OFDMA signals as appropriate for transmission by performing an inverse fast Fourier transform (IFFT). The receive baseband processor 402 may be configured to process received OFDM signals or OFDMA signals by performing an FFT. In some embodiments, the receive baseband processor 402 may be configured to detect the presence of an OFDM signal or OFDMA signal by performing an autocorrelation, to detect a preamble, such as a short preamble, and by performing a cross-correlation, to detect a long preamble. The preambles may be part of a predetermined frame structure for Wi-Fi communication.

[0055] Referring back to FIG. 1, in some embodiments, the antennas 101

(FIG. 1) may each comprise one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas or other types of antennas suitable for transmission of RF signals. In some multiple-input multiple-output (MIMO) embodiments, the antennas may be effectively separated to take advantage of spatial diversity and the different channel characteristics that may result.

Antennas 101 may each include a set of phased-array antennas, although embodiments are not so limited.

[0056] Although the radio-architecture 100 is illustrated as having several separate functional elements, one or more of the functional elements may be combined and may be implemented by combinations of software-configured elements, such as processing elements including digital signal processors (DSPs), and/or other hardware elements. For example, some elements may comprise one or more microprocessors, DSPs, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio-frequency integrated circuits (RFICs) and combinations of various hardware and logic circuitry for performing at least the functions described herein. In some embodiments, the functional elements may refer to one or more processes operating on one or more processing elements.

[0057] FIG. 5 illustrates a WLAN 500 in accordance with some embodiments. The WLAN 500 may comprise a basis service set (BSS) that may include a HE access point (AP) 502, which may be an AP, a plurality of high- efficiency wireless (e.g., IEEE 802.1 lax) (HE) stations 504, and a plurality of legacy (e.g., IEEE 802.1 1n/ac) devices 506.

[0058] The HE AP 502 may be an AP using the IEEE 802.1 1 communication protocol to transmit and receive. The HE AP 502 may be a base station. The HE AP 502 may use other communications protocols as well as the IEEE 802.1 1 protocol. The IEEE 802.1 1 protocol may be IEEE 802.1 lax. The IEEE 802.1 1 protocol may include using orthogonal frequency division multiple-access (OFDMA), time division multiple access (TDMA), and/or code division multiple access (CDMA). The IEEE 802.1 1 protocol may include a multiple access technique. For example, the IEEE 802.1 1 protocol may include space-division multiple access (SDMA) and/or multiple-user multiple-input multiple-output (MU-MIMO). There may be more than one HE AP 502 that is part of an extended service set (ESS). A controller (not illustrated) may store information that is common to the more than one HE APs 502.

[0059] The legacy devices 506 may operate in accordance with one or more of IEEE 802.1 1 a/b/g/n/ac/ad/af/ah/aj/ay, or another legacy wireless communication standard. The legacy devices 506 may be STAs or IEEE STAs. The HE STAs 504 may be wireless transmit and receive devices such as cellular telephone, portable electronic wireless communication devices, smart telephone, handheld wireless device, wireless glasses, wireless watch, wireless personal device, tablet, or another device that may be transmitting and receiving using the IEEE 802.1 1 protocol such as IEEE 802.1 lax or another wireless protocol. In some embodiments, the HE STAs 504 may be termed high efficiency (HE) stations.

[0060] The HE AP 502 may communicate with legacy devices 506 in accordance with legacy IEEE 802.1 1 communication techniques. In example embodiments, the HE AP 502 may also be configured to communicate with HE STAs 504 in accordance with legacy IEEE 802.1 1 communication techniques. [0061] In some embodiments, a HE frame may be configurable to have the same bandwidth as a channel. The HE frame may be a physical Layer Convergence Procedure (PLCP) Protocol Data Unit (PPDU). In some embodiments, there may be different types of PPDUs that may have different fields and different physical layers and/or different media access control (MAC) layers.

[0062] The bandwidth of a channel may be 20MHz, 40MHz, or 80MHz,

160MHz, 320MHz contiguous bandwidths or an 80+80MHz (160MHz) noncontiguous bandwidth. In some embodiments, the bandwidth of a channel may be 1 MHz, 1.25MHz, 2.03MHz, 2.5MHz, 4.06 MHz, 5MHz and 10MHz, or a combination thereof or another bandwidth that is less or equal to the available bandwidth may also be used. In some embodiments the bandwidth of the channels may be based on a number of active data subcarriers. In some embodiments the bandwidth of the channels is based on 26, 52, 106, 242, 484, 996, or 2x996 active data subcarriers or tones that are spaced by 20 MHz. In some embodiments the bandwidth of the channels is 256 tones spaced by 20 MHz. In some embodiments the channels are multiple of 26 tones or a multiple of 20 MHz. In some embodiments a 20 MHz channel may comprise 242 active data subcarriers or tones, which may determine the size of a Fast Fourier Transform (FFT). An allocation of a bandwidth or a number of tones or sub- carriers may be termed a resource unit (RU) allocation in accordance with some embodiments.

[0063] In some embodiments, the 26-subcarrier RU and 52-subcarrier

RU are used in the 20 MHz, 40 MHz, 80 MHz, 160 MHz and 80+80 MHz OFDMA HE PPDU formats. In some embodiments, the 106-subcarrier RU is used in the 20 MHz, 40 MHz, 80 MHz, 160 MHz and 80+80 MHz OFDMA and MU-MIMO HE PPDU formats. In some embodiments, the 242-subcarrier RU is used in the 40 MHz, 80 MHz, 160 MHz and 80+80 MHz OFDMA and MU- MIMO HE PPDU formats. In some embodiments, the 484-subcarrier RU is used in the 80 MHz, 160 MHz and 80+80 MHz OFDMA and MU-MIMO HE PPDU formats. In some embodiments, the 996-subcarrier RU is used in the 160 MHz and 80+80 MHz OFDMA and MU-MIMO HE PPDU formats. [0064] A HE frame may be configured for transmitting a number of spatial streams, which may be in accordance with MU-MIMO and may be in accordance with OFDMA. In other embodiments, the HE AP 502, HE STA 504, and/or legacy device 506 may also implement different technologies such as code division multiple access (CDMA) 2000, CDMA 2000 IX, CDMA 2000 Evolution-Data Optimized (EV-DO), Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Long Term Evolution (LTE), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), BlueTooth®, or other technologies.

[0065] Some embodiments relate to HE communications. In accordance with some IEEE 802.1 1 embodiments, e.g, IEEE 802.1 lax embodiments, a HE AP 502 may operate as a master station which may be arranged to contend for a wireless medium (e.g., during a contention period) to receive exclusive control of the medium for an HE control period. In some embodiments, the HE control period may be termed a transmission opportunity (TXOP). The HE AP 502 may transmit a HE master-sync transmission, which may be a trigger frame or HE control and schedule transmission, at the beginning of the HE control period. The HE AP 502 may transmit a time duration of the TXOP and sub-channel information. During the HE control period, HE STAs 504 may communicate with the HE AP 502 in accordance with a non-contention based multiple access technique such as OFDMA or MU-MIMO. This is unlike conventional WLAN communications in which devices communicate in accordance with a contention- based communication technique, rather than a multiple access technique. During the HE control period, the HE AP 502 may communicate with HE stations 504 using one or more HE frames. During the HE control period, the HE STAs 504 may operate on a sub-channel smaller than the operating range of the HE AP 502. During the HE control period, legacy stations refrain from communicating. The legacy stations may need to receive the communication from the HE AP 502 to defer from communicating.

[0066] In accordance with some embodiments, during the TXOP the HE

STAs 504 may contend for the wireless medium with the legacy devices 506 being excluded from contending for the wireless medium during the master-sync transmission. In some embodiments the trigger frame may indicate an uplink (UL) UL-MU-MIMO and/or UL OFDMA TXOP. In some embodiments, the trigger frame may include a DL UL-MU-MIMO and/or DL OFDMA with a schedule indicated in a preamble portion of trigger frame.

[0067] In some embodiments, the multiple-access technique used during the HE TXOP may be a scheduled OFDMA technique, although this is not a requirement. In some embodiments, the multiple access technique may be a time-division multiple access (TDMA) technique or a frequency division multiple access (FDMA) technique. In some embodiments, the multiple access technique may be a space-division multiple access (SDMA) technique. In some embodiments, the multiple access technique may be a Code division multiple access (CDMA).

[0068] The HE AP 502 may also communicate with legacy stations 506 and/or HE stations 504 in accordance with legacy IEEE 802.11 communication techniques. In some embodiments, the HE AP 502 may also be configurable to communicate with HE stations 504 outside the HE TXOP in accordance with legacy IEEE 802.1 1 communication techniques, although this is not a requirement.

[0069] In some embodiments the HE station 504 may be a "group owner" (GO) for peer-to-peer modes of operation. A wireless device may be a HE station 502 or a HE AP 502.

[0070] In some embodiments, the HE station 504 and/or HE AP 502 may be configured to operate in accordance with IEEE 802.1 lmc. In example embodiments, the radio architecture of FIG. 1 is configured to implement the HE station 504 and/or the HE AP 502. In example embodiments, the front-end module circuitry of FIG. 2 is configured to implement the HE station 504 and/or the HE AP 502. In example embodiments, the radio IC circuitry of FIG. 3 is configured to implement the HE station 504 and/or the HE AP 502. In example embodiments, the base-band processing circuitry of FIG. 4 is configured to implement the HE station 504 and/or the HE AP 502.

[0071] In example embodiments, the HE stations 504, HE AP 502, an apparatus of the HE stations 504, and/or an apparatus of the HE AP 502 may include one or more of the following: the radio architecture of FIG. 1, the front- end module circuitry of FIG. 2, the radio IC circuitry of FIG. 3, and/or the baseband processing circuitry of FIG. 4.

[0072] In example embodiments, the radio architecture of FIG. 1, the front-end module circuitry of FIG. 2, the radio IC circuitry of FIG. 3, and/or the base-band processing circuitry of FIG. 4 may be configured to perform the methods and operations/functions herein described in conjunction with FIGS. 1- 17.

[0073] In example embodiments, the HE station 504 and/or the HE AP 502 are configured to perform the methods and operations/functions described herein in conjunction with FIGS. 1- 17. In example embodiments, an apparatus of the HE station 504 and/or an apparatus of the HE AP 502 are configured to perform the methods and functions described herein in conjunction with FIGS. 1-17. The term Wi-Fi may refer to one or more of the IEEE 802.1 1

communication standards. AP and STA may refer to HE access point 502 and/or HE station 504 as well as legacy devices 506.

[0074] In some embodiments, a HE AP STA may refer to a HE AP 502 and a HE STAs 504 that is operating a HE APs 502. In some embodiments, when an HE STA 504 is not operating as a HE AP, it may be referred to as a HE non-AP STA or HE non-AP. In some embodiments, HE STA 504 may be referred to as either a HE AP STA or a HE non-AP.

[0075] FIG. 6 illustrates a block diagram of an example machine 600 upon which any one or more of the techniques (e.g., methodologies) discussed herein may perform. In alternative embodiments, the machine 600 may operate as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine 600 may operate in the capacity of a server machine, a client machine, or both in server-client network environments. In an example, the machine 600 may act as a peer machine in peer-to-peer (P2P) (or other distributed) network environment. The machine 600 may be a HE AP 502, HE station 504, personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a portable communications device, a mobile telephone, a smart phone, a web appliance, a network router, switch or bridge, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while only a single machine is illustrated, the term "machine" shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein, such as cloud computing, software as a service (SaaS), other computer cluster configurations.

[0076] Machine (e.g., computer system) 600 may include a hardware processor 602 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 604 and a static memory 606, some or all of which may communicate with each other via an interlink (e.g., bus) 608.

[0077] Specific examples of main memory 604 include Random Access

Memory (RAM), and semiconductor memory devices, which may include, in some embodiments, storage locations in semiconductors such as registers.

Specific examples of static memory 606 include non-volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; RAM; and CD-ROM and DVD-ROM disks.

[0078] The machine 600 may further include a display device 610, an input device 612 (e.g., a keyboard), and a user interface (UI) navigation device 614 (e.g., a mouse). In an example, the display device 610, input device 612 and UI navigation device 614 may be a touch screen display. The machine 600 may additionally include a mass storage (e.g., drive unit) 616, a signal generation device 618 (e.g., a speaker), a network interface device 620, and one or more sensors 621, such as a global positioning system (GPS) sensor, compass, accelerometer, or other sensor. The machine 600 may include an output controller 628, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared(IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.). In some embodiments the processor 602 and/or instructions 624 may comprise processing circuitry and/or transceiver circuitry. [0079] The storage device 616 may include a machine readable medium

622 on which is stored one or more sets of data structures or instructions 624 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions 624 may also reside, completely or at least partially, within the main memory 604, within static memory 606, or within the hardware processor 602 during execution thereof by the machine 600. In an example, one or any combination of the hardware processor 602, the main memory 604, the static memory 606, or the storage device 616 may constitute machine readable media.

[0080] Specific examples of machine readable media may include: nonvolatile memory, such as semiconductor memory devices (e.g., EPROM or EEPROM) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; RAM; and CD-ROM and DVD-ROM disks.

[0081] While the machine readable medium 622 is illustrated as a single medium, the term "machine readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions 624.

[0082] An apparatus of the machine 600 may be one or more of a hardware processor 602 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 604 and a static memory 606, sensors 621, network interface device 620, antennas 660, a display device 610, an input device 612, a UI navigation device 614, a mass storage 616, instructions 624, a signal generation device 618, and an output controller 628. The apparatus may be configured to perform one or more of the methods and/or operations disclosed herein. The apparatus may be intended as a component of the machine 600 to perform one or more of the methods and/or operations disclosed herein, and/or to perform a portion of one or more of the methods and/or operations disclosed herein. In some embodiments, the apparatus may include a pin or other means to receive power. In some embodiments, the apparatus may include power conditioning hardware. [0083] The term "machine readable medium" may include any medium that is capable of storing, encoding, or carrying instructions for execution by the machine 600 and that cause the machine 600 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions. Non- limiting machine readable medium examples may include solid-state memories, and optical and magnetic media. Specific examples of machine readable media may include: non-volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; Random Access Memory (RAM); and CD-ROM and DVD-ROM disks. In some examples, machine readable media may include non-transitory machine- readable media. In some examples, machine readable media may include machine readable media that is not a transitory propagating signal.

[0084] The instructions 624 may further be transmitted or received over a communications network 626 using a transmission medium via the network interface device 620 utilizing any one of a number of transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.). Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), Plain Old Telephone (POTS) networks, and wireless data networks (e.g., Institute of Electrical and Electronics Engineers (IEEE) 802.1 1 family of standards known as Wi-Fi®, IEEE 802.16 family of standards known as WiMax®), IEEE 802.15.4 family of standards, a Long Term Evolution (LTE) family of standards, a Universal Mobile Telecommunications System (UMTS) family of standards, peer-to-peer (P2P) networks, among others.

[0085] In an example, the network interface device 620 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas to connect to the communications network 626. In an example, the network interface device 620 may include one or more antennas 660 to wirelessly communicate using at least one of single-input multiple-output (SIMO), multiple-input multiple-output (MIMO), or multiple-input single-output (MISO) techniques. In some examples, the network interface device 620 may wirelessly communicate using Multiple User MIMO techniques. The term "transmission medium" shall be taken to include any intangible medium that is capable of storing, encoding or carrying instructions for execution by the machine 600, and includes digital or analog communications signals or other intangible medium to facilitate communication of such software.

[0086] Examples, as described herein, may include, or may operate on, logic or a number of components, modules, or mechanisms. Modules are tangible entities (e.g., hardware) capable of performing specified operations and may be configured or arranged in a certain manner. In an example, circuits may be arranged (e.g., internally or with respect to external entities such as other circuits) in a specified manner as a module. In an example, the whole or part of one or more computer systems (e.g., a standalone, client or server computer system) or one or more hardware processors may be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module that operates to perform specified operations. In an example, the software may reside on a machine readable medium. In an example, the software, when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.

[0087] Accordingly, the term "module" is understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., transitorily) configured (e.g., programmed) to operate in a specified manner or to perform part or all of any operation described herein. Considering examples in which modules are temporarily configured, each of the modules need not be instantiated at any one moment in time. For example, where the modules comprise a general -purpose hardware processor configured using software, the general-purpose hardware processor may be configured as respective different modules at different times. Software may accordingly configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time. [0088] Some embodiments may be implemented fully or partially in software and/or firmware. This software and/or firmware may take the form of instructions contained in or on a non-transitory computer-readable storage medium. Those instructions may then be read and executed by one or more processors to enable performance of the operations described herein. The instructions may be in any suitable form, such as but not limited to source code, compiled code, interpreted code, executable code, static code, dynamic code, and the like. Such a computer-readable medium may include any tangible non- transitory medium for storing information in a form readable by one or more computers, such as but not limited to read only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; flash memory, etc.

[0089] FIG. 7 illustrates a block diagram of an example wireless device

700 upon which any one or more of the techniques (e.g., methodologies or operations) discussed herein may perform. The wireless device 700 may be a HE device. The wireless device 700 may be a HE STA 504 and/or HE AP 502 (e.g., FIG. 5). A HE STA 504 and/or HE AP 502 may include some or all of the components shown in FIGS. 1-7. The wireless device 700 may be an example machine 600 as disclosed in conjunction with FIG. 6.

[0090] The wireless device 700 may include processing circuitry 708.

The processing circuitry 708 may include a transceiver 702, physical layer circuitry (PHY circuitry) 704, and MAC layer circuitry (MAC circuitry) 706, one or more of which may enable transmission and reception of signals to and from other wireless devices 700 (e.g., HE AP 502, HE STA 504, and/or legacy devices 506) using one or more antennas 712. As an example, the PHY circuitry 704 may perform various encoding and decoding functions that may include formation of baseband signals for transmission and decoding of received signals. As another example, the transceiver 702 may perform various transmission and reception functions such as conversion of signals between a baseband range and a Radio Frequency (RF) range.

[0091] Accordingly, the PHY circuitry 704 and the transceiver 702 may be separate components or may be part of a combined component, e.g., processing circuitry 708. In addition, some of the described functionality related to transmission and reception of signals may be performed by a combination that may include one, any or all of the PHY circuitry 704 the transceiver 702, MAC circuitry 706, memory 710, and other components or layers. The MAC circuitry 706 may control access to the wireless medium. The wireless device 700 may also include memory 710 arranged to perform the operations described herein, e.g., some of the operations described herein may be performed by instructions stored in the memory 710.

[0092] The antennas 712 (some embodiments may include only one antenna) may comprise one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas or other types of antennas suitable for transmission of RF signals. In some multiple-input multiple-output (MIMO) embodiments, the antennas 712 may be effectively separated to take advantage of spatial diversity and the different channel characteristics that may result.

[0093] One or more of the memory 710, the transceiver 702, the PHY circuitry 704, the MAC circuitry 706, the antennas 712, and/or the processing circuitry 708 may be coupled with one another. Moreover, although memory 710, the transceiver 702, the PHY circuitry 704, the MAC circuitry 706, the antennas 712 are illustrated as separate components, one or more of memory 710, the transceiver 702, the PHY circuitry 704, the MAC circuitry 706, the antennas 712 may be integrated in an electronic package or chip.

[0094] In some embodiments, the wireless device 700 may be a mobile device as described in conjunction with FIG. 6. In some embodiments the wireless device 700 may be configured to operate in accordance with one or more wireless communication standards as described herein (e.g., as described in conjunction with FIGS. 1-6, IEEE 802.1 1). In some embodiments, the wireless device 700 may include one or more of the components as described in conjunction with FIG. 6 (e.g., display device 610, input device 612, etc.) Although the wireless device 700 is illustrated as having several separate functional elements, one or more of the functional elements may be combined and may be implemented by combinations of software-configured elements, such as processing elements including digital signal processors (DSPs), and/or other hardware elements. For example, some elements may comprise one or more microprocessors, DSPs, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio-frequency integrated circuits (RFICs) and combinations of various hardware and logic circuitry for performing at least the functions described herein. In some embodiments, the functional elements may refer to one or more processes operating on one or more processing elements.

[0095] In some embodiments, an apparatus of or used by the wireless device 700 may include various components of the wireless device 700 as shown in FIG. 7 and/or components from FIGS. 1-6. Accordingly, techniques and operations described herein that refer to the wireless device 700 may be applicable to an apparatus for a wireless device 700 (e.g., HE AP 502 and/or HE STA 504), in some embodiments. In some embodiments, the wireless device 700 is configured to decode and/or encode signals, packets, and/or frames as described herein, e.g., PPDUs.

[0096] In some embodiments, the MAC circuitry 706 may be arranged to contend for a wireless medium during a contention period to receive control of the medium for a HE TXOP and encode or decode an HE PPDU. In some embodiments, the MAC circuitry 706 may be arranged to contend for the wireless medium based on channel contention settings, a transmitting power level, and a clear channel assessment level (e.g., an energy detect level).

[0097] The PHY circuitry 704 may be arranged to transmit signals in accordance with one or more communication standards described herein. For example, the PHY circuitry 704 may be configured to transmit a HE PPDU. The PHY circuitry 704 may include circuitry for modulation/demodulation, upconversion/downconversion, filtering, amplification, etc. In some embodiments, the processing circuitry 708 may include one or more processors. The processing circuitry 708 may be configured to perform functions based on instructions being stored in a RAM or ROM, or based on special purpose circuitry. The processing circuitry 708 may include a processor such as a general purpose processor or special purpose processor. The processing circuitry 708 may implement one or more functions associated with antennas 712, the transceiver 702, the PHY circuitry 704, the MAC circuitry 706, and/or the memory 710. In some embodiments, the processing circuitry 708 may be configured to perform one or more of the functions/operations and/or methods described herein.

[0098] In mmWave technology, communication between a station (e.g., the HE stations 504 of FIG. 5 or wireless device 700) and an access point (e.g., the HE AP 502 of FIG. 5 or wireless device 700) may use associated effective wireless channels that are highly directionally dependent. To accommodate the directionality, beamforming techniques may be utilized to radiate energy in a certain direction with certain beamwidth to communicate between two devices. The directed propagation concentrates transmitted energy toward a target device in order to compensate for significant energy loss in the channel between the two communicating devices. Using directed transmission may extend the range of the millimeter-wave communication versus utilizing the same transmitted energy in omni-directional propagation.

[0099] FIGS. 8-13 will be disclosed in conjunction with one another. FIG. 8 illustrates a system 800 for delegation of autonomy based on network conditions in a multiple AP environment. Illustrated in FIG. 8 is wide area network (WAN) 812, fronthaul link 814, WAN link 816, link 818, multi-AP devices 820, non-AP STA 822, and backhaul link 824.

[00100] The fronthaul link 814 and the backhaul link 824 may be wireless or wired communications (as illustrated it is a wireless connection). In some embodiments, the fronthaul link 814 and the wireless backhaul link 824 may use a communication protocol such as IEEE 802.11 or IEEE 802.16. Although, the communication protocol is not limited to these examples. The fronthaul links 814 may be wireless or wired links between a multi-AP device 820 and a non- AP STA 822. For example, fronthaul 806.2 may communicate via fronthaul link 814.2 with non-AP STA 822.2 via the antennas. The backhaul links 824 may be wireless or wired links between two multi-AP devices 820. For example, backhaul STA 810.3 may communicate with multi-AP device 820.1 via backhaul link 824.2.

[00101] The WAN 812 may be a telecommunications or computer network that may extend over a large geographic distance. For example, the WAN 812 may be the internet or include the internet. One or more of the multi- AP devices 820 may be directly connected to the WAN 812. For example, the multi-AP device 820.1 may be connected to the WAN 812 via WAN link 816, which may be a wired connection or a wireless connection. The multi-AP device 820.1 may have multipaths to the WAN 812, e.g., the multi-AP device 820.1 may have an LTE connection to the WAN 812 (not illustrated).

[00102] The multi-AP device 820.1 may provide routing functions for

PPDUs or packets to and from the other devices, e.g., multi-AP device 820.2, 820.3, 820.4, non-AP STA 822.1, 822.2, 822.3, 822.4, and wired or wireless devices residing in the WAN 812, e.g., VOIP services, video streaming, etc.

[00103] The multi-AP devices 820 may be HE APs 502. The multi-AP devices 820 may include multi-AP controller 802, multi-AP agent 804, fronthaul 806, logical ethernet port 808, and backhaul STA 810.

[00104] The multi-AP controller 802 may be a controller that is configured to communicate with and control multi-AP agents 804, which may be on other multi-AP devices 820 and on a same multi-AP device 820 (e.g., 820.1). The multi-AP controller 802 and multi-AP agent 804 may be configured to perform one or more of the functions described herein. A multi-AP device 820 that includes a multi-AP controller 802 may be termed a root AP, in accordance with some embodiments. A multi-AP controller 802 that includes a multi-AP agent 804 and does not include a multi-AP controller 802 may be termed a satellite AP, in accordance with some embodiments. The multi-AP controller 802 may be a logical entity that implements functions for controlling the operation of one or more portions of the system 800.

[00105] The multi-AP device 820.1 may request that multi-AP devices

820 that are being controlled by the multi-AP controller 802 send continuous (e.g., 1 time per second) real-time traffic reports and usage statistics for all associated non-AP STA 822 (e.g., 822.1, 822.2, 822.3, and 822.4). In some embodiments, the multi-AP device 820.1 may poll or request usage statistics from the multi-AP devices 820 that are being controlled by the multi-AP controller 802. The usage statistics may be stored in measurements and statistics 906.

[00106] FIG. 9 illustrates a multi-AP controller 802 in accordance with some embodiments. The multi-AP controller 802 may include measurements and statistics 906 and multi-AP device information 904. FIG. 10 illustrates a multi-AP agent 804 in accordance with some embodiments. The multi-AP agent 804 may include capability information 1002, measurements and statistics 1004, and autonomy grants 1006.

[00107] The measurements and statistics 906 may be measurements and statistics for the communication and traffic in the system 800, e.g., received signal strength indicator (RSSI) for fronthaul links 814 and the backhaul links 824, a number of dropped packets for fronthaul links 814 and the wireless backhaul links 824, packet flow for each of the multi-AP devices 820, non-AP STAs 822, the WAN 821, network conditions (e.g., system 800 conditions), packet error rate over a duration of time for fronthaul links 814 and the backhaul links 824, and a measured energy level of a legacy portion of a received packet for fronthaul links 814 and the backhaul links 824.

[00108] The multi-AP device information 904 may be information for each multi-AP device 820 in the system 800. The multi-AP device information 904 may include multi-AP device identification (ID) 902, measurements and statistics 908, autonomy grants 910, and capability information 912. The multi- AP device ID 902 may be a media access control (MAC) address or an association ID (AID), in accordance with some embodiments. The

measurements and statistics 908 may be the same or similar to measurements and statistics 906 with the measurement and statistics related to the multi-AP device 820 with the multi-AP device ID 902. The autonomy grants 910 may include one or more autonomy grant IEs 1 100 as described in conjunction with FIG. 1 1. The autonomy grants 910 may be autonomy grants 910 granted to the multi-AP device 820 with the multi-AP device ID 902, in accordance with some embodiments. In some embodiments, the autonomy grants 910 may include additional fields, e.g., a field to indicate a time when the autonomy grant 910 was granted, whether the autonomy grant 910 is still active, etc.

[00109] FIG. 1 1 illustrates an autonomy grant information element (IE)

1 100 in accordance with some embodiments. The autonomy grants 910 may include N function 1 102 and condition 1104 pairs 1 106. The function 1 102 may be an operation that the multi-AP device 820 may perform. The condition 1304 may be optional, in accordance with some embodiments. The condition 1304 may include conditions when the function 1 102 may be performed by the multi- AP device 820 when the condition 1304 is met. The functions 1 102 may include associate, disassociate, handover, beamforming, and stream from the WAN (e.g., internet) 812. The conditions may include when a measured receive signal strength indicator (RSSI) of a third PPDU from the second AP is above a first threshold, when the measured RSSI of the third PPDU is below a second threshold, when the first AP is disconnected from the second AP, when a number of hops between the first AP and the second AP is greater than a threshold, when a latency between the first AP and the second AP is greater than a threshold, when a response from the second AP to a third PPDU from the first AP is not received within a threshold period of time, when a response from the second AP to a service request from the first AP is not received within a threshold number of retries, when a communication with the second AP and the first AP has timed out, when an elapsed time since decoding the first PPDU is less than a time indicated by the condition, and when a link metric between the first AP and the second AP is below a threshold. A condition 1 104 may be if a service request to the root AP 1406 or AP 1506 has timed out.

[00110] The multi-AP controller 802 may receive measurements (receive signal strength indicators, RSSI), statistics (e.g., packet drop rate), and capability information (e.g., 1002) from multi-AP devices 820, fronthauls 806 (e.g., fronthaul 806.1, 806.2, 806.3, and 806.3), non-AP STAs 822, logical ethernet ports 808, and backhaul STAs 810. In some embodiments, the multi-AP controller 802 is configured to communication with the multi-AP agents 804. For example, multi-AP controller 802 may communicate with multi-AP agent 804.1, 804.2, and 804.3.

[00111] The multi-AP controller 802 may be configured to generate an autonomy grant 910 for a multi-AP device 820 based the measurements and statistics 906. For example, the multi-AP controller 802 may determine that backhaul link 824.1 is noisy or weak (e.g., based on a RSSI being below a threshold or a packet error rate being above a threshold), and based on the determination generate and encode an autonomy grant 910 for multi-AP device 820.2, e.g., a function 1 102 and a condition 1 104 pair 1 106 such as if the RSSI is below a threshold, then multi-AP device 820.2 may perform handovers to other multi-AP devices 820 (e.g., 820.3 or 820.4) without first communicating with the multi-AP device 820.1 (e.g., the multi-AP controller 802).

[00112] The capability information 912 may include capability information (e.g., capability information 1300) for the multi-AP device 820 with the multi-AP device ID 902. The capability information 912 may be the same or similar to capability information 1300.

[00113] FIG. 12 illustrates capabilities information element 1200 in accordance with some embodiments. The capabilities information element 1200 may include function 1202 and condition 1204 pairs 1206. The condition 1204 may be optional and there may be one or more additional fields, e.g., a version of a standard. The function 1202 may be the same or similar to function 1 102. The condition 1204 may be the same or similar to condition 1 104. The capabilities information element 1200 may indicate that the multi-AP device 820 is capable of performing function 1202 when condition 1204 is present or true. If the condition 1204 is not present, then the capabilities information element 1200 may indicate that the multi-AP device 820 is capable of performing function 1202.

[00114] Capability information 1002 may be the same or similar to capabilities information element 1200. The capability information 1002 may be the capabilities (e.g., the function 1202 and condition 1204 pairs 1206) that the multi-AP device 820 with the multi-AP agent 804 is capable of performing.

[00115] The measurements and statistics 1004 may be the same or similar as measurement and statistics 906 or measurement and statistics 908 for the multi-AP device 820 with the multi-AP agent 804. For example, the measurements and statistics 1004 may include RSSI values for all the wireless connections the multi-AP device 820 current has (e.g., multi-AP device 820.3 may maintain RSSI values for packets received from non-AP STA 822.3, multi- AP device 820.2, and multi-AP device 820.1). The measurement and statistics 1004 may include one or more additional fields, e.g., a field for a time stamp.

[00116] The autonomy grants 1006 may be the same or similar to autonomy grants 910 or autonomy grant information element 1 100. The autonomy grants 1006 may be the active autonomy grants 1006 from the multi- AP controller 802. In some embodiments, the autonomy grants 1006 may include one or more additional fields such as a time stamp when the autonomy grant 1006 was received.

[00117] The multi-AP device 820 may transmit a service request 1300 to the multi-AP controller 802 (e.g., to the multi-AP device 820.1 with multi-AP controller 802). FIG. 13 illustrates a service request 1300 in accordance with some embodiments. The service request 1300 may include N function 1302 and condition 1304 pairs 1306. The function 1302 may be the same or similar to function 1 102 and/or function 1202. The multi-AP controller 802 may be configured to respond to the service request 1300 with an autonomy grant information element 1 100. The multi-AP controller 802 may refuse the service request 1300 by transmitting a packet indicating the service request 1300 is denied. In some embodiments, an autonomy grant information element 1 100 may have one or more fields that indicate that the service request 1300 is denied. The mutli-AP device 820 may determine whether to grant the service request 1300 based on the measurements and statistics 906 and/or based on the service request 1300 (e.g., a condition 1304 of the service request 1300 such as a threshold for an RSSI of a packet received by the multi-AP device 820 that includes the multi-AP controller 802).

[00118] An autonomy grant information element 1100, capabilities information element 1200, or service request 1300 may have a function 1 102, 1202, or 1302, respectively, used more than once for different conditions 1 104, 1204, or 1304. An autonomy grant information element 1100, capabilities information element 1200, or service request 1300 may have a condition 1 104, 1204, or 1304, respectively, used more than once for different functions 1 102, 1202, or 1302.

[00119] The logical Ethernet ports 808 may be ports for use in communicating using ethernet. The logical ethernet port 808.2 is connected to logical ethernet port 808.1 via link 818, which may be a wired connection or a wireless connection (as illustrated it is a wired connection). WAN link 816 and link 818 may be a wired connection that may be Ethernet (IEEE 802.1 1),

Multimedia over Coax Alliance (MoCA), or power line communication (PLC), in accordance with some embodiments. [00120] The autonomy grant information element 1100, capabilities information element 1200, and/or service request 1300 may be part of a packet or PPDU. In some embodiments, the autonomy grant information element 1100, the capabilities information element 1200, and/or the service request 1300 may be fields of a packet or PPDU.

[00121] FIG. 14 illustrates a method 1400 for delegation of autonomy based on network conditions in a multiple AP environment in accordance with some embodiments. Illustrated in FIG. 14 is a root AP 1406, a satellite AP 1408, a client 1410, and time 1412. The root AP 1406 may be a multi-AP device 820.1 with a multi-AP controller 802. The satellite AP 1408 may be multi-AP device 820.2, 820.3, or 820.4 with a multi-AP agent 804.2, 804.3, or 804.4, respectively. The client 1410 may be a non-AP STA 822.1, 822.2, 822.3, or 822.4.

[00122] The method 1400 may begin with the satellite AP 1408 transmitting 1402 a capabilities information element 1404.1. The capabilities information element 1404.1 may be a capabilities information element 1200 as described in conjunction with FIG. 12. For example, the capabilities information element 1404.1 may include a number of function 1202 and condition 1204 pairs 1206. The function 1202 may be to perform handovers or other functions as described herein. The condition 1204 may not be present, in accordance with some embodiments. In some embodiments, the condition 1204 may be related to a measured RSSI between the root AP 1406 and the satellite AP 1408. The capabilities information element 1404.1 may be transmitted over a wired or wireless connection, e.g., link 818 or backhaul link 824. The root AP 1406 may receive the capabilities information element 1404.1 and store it, e.g. in a multi- AP device information 904 by setting the multi-AP device ID 902 to a multi-AP device ID of the satellite AP 1408, and by storing the capabilities information element 1404.1 in the capability information 912. The multi-AP device 820 may determine the capabilities information element 1404.1 based on a configuration of the multi-AP device 820, e.g., the multi-AP device 820 may have a number of antennas that determine whether the multi-AP device 820 may perform beamforming. The multi-AP device 820 may be configured to operate in accordance with one or more communication protocols, which may determine whether the device may perform some functions (e.g., receive a stream from non-AP STA 822 and stream it another wireless device, e.g., a television or music player.) The multi-AP device 820 may be directly connected to the WAN 812, which would enable some functions such as forwarding connection and streaming requests to the internet services.

[00123] The method 1400 continues at operation 1402.2 with transmitting autonomy grant information element 1404.2. For example, autonomy grant information element 1404.2 may be an autonomy grant information element 1 100 as disclosed in conjunction with FIG. 1 1. For example, the function 1 102.1 may be handover, and condition 1 104.1 may be a RSSI between the root AP 1406 and the satellite AP 1408. The autonomy grant information element 1404.2 may include additional function 1 102 and condition 1 104 pairs 1 106. The autonomy grant information element 1404.2 may be transmitted over a wired or wireless connection, e.g., link 818 or backhaul link 824. The satellite AP 1408 may store the autonomy grant information element 1404.2 as autonomy grants 1006 as described in conjunction with FIG. 10.

[00124] In some embodiments, the root AP 1406 may determine which function 1 102 and condition 1 104 pairs based on whether the root AP 1406 is overloaded with operations. For example, if the root AP 1406 receives a service request from the satellite AP 1408 and the root AP 1406 determines that the load of the root AP 1406 is not sufficient to service the request adequately, then the root AP 1406 may generate the autonomy grant 1006 to enable the satellite AP 1408 to perform the service. For example, the service may be for a handover, connection to a server on the WAN 812, etc. In some embodiments, the root AP 1406 generates the autonomy grant 1006 to enable the satellite AP 1408 to perform the service before the condition 1104 occurs. E.g., the root AP 1406 may send an autonomy grant 1006 to the satellite AP 1408 to perform service requests if the root AP 1406 is overloaded.

[00125] The method 1400 continues at operation 1402.3 with satellite AP 1408 performing a function 1404.3 for client 1410. For example, for a function 1102 and condition 1 104 pair 1106 with the condition if the RSSI signal of a received packet from the root AP 1406 is below a threshold and with the function being handover, then the function 1 102 may be for the satellite AP 1408 to handover the client 1410 to another satellite AP (not illustrated.) The RSSI signal may drop below the threshold because the client 1410 moves (e.g., to a different room). The operation 1402.3 may be more than one transmission between the client 1410 and the satellite AP 1408. In some embodiments, the satellite AP 1408 may receive a handover request from the client 1410. In some embodiments, the satellite AP 1408 may determine the client 1410 should be handed over to another AP based on a measured received signal from the client 1410 (e.g., RSSI). The satellite AP 1408 may determine the autonomy of the handover operation based on stored autonomy grants 1006. The satellite AP 1408 may then determine whether to perform the handover with the client 1410 autonomously or to contact the root AP 1406.

[00126] The method 1400 continues at operation 1402.4 with transmitting autonomy grant information element 1404.4. The autonomy grant information element 1404.4 may be an update of autonomy grant information element 1404.2. For example, autonomy grant information element 1404.2 may be an autonomy grant information element 1100 as disclosed in conjunction with FIG. 11. For example, the function 1102.1 may be associate, and condition 1104.1 may be a packet error rate between the root AP 1406 and the satellite AP 1408. The autonomy grant information element 1404.4 may include additional function 1102 and condition 1104 pairs 1 106. The autonomy grant information element 1404.4 may be transmitted over a wired or wireless connection, e.g., link 818 or backhaul link 824. The satellite AP 1408 may store the autonomy grant information element 1404.4 as autonomy grants 1006 as described in conjunction with FIG. 10. In some embodiments, the satellite AP 1408 may replace the previously stored autonomy grant information element 1404.2 with autonomy grant information element 1404.4. In some embodiments, the satellite AP 1408 may merge the previously stored autonomy grant information element 1404.2 with autonomy grant information element 1404.4. In some

embodiments, the stored autonomy grant information element 1404.2 may include a field to indicate whether a function 1102 and condition 1104 pair 1106 are cancelled or updated.

[00127] The method 1400 continues at operation 1402.5 with satellite AP

1408 performing a function 1404.5 for client 1410. For example, for a function 1102 and condition 1104 pair 1106 with the condition if a packet error rate is above a threshold for packets from the root AP 1406 and with the function being associate, then the function 1102 may be for the satellite AP 1408 to associate with the client 1410. In some embodiments, the function may be for the satellite AP 1408 to associate with the client 1410 without first contacting the root AP 1406. The operation 1402.5 may be more than one transmission between the client 1410 and the satellite AP 1408. In some embodiments, the satellite AP 1408 may receive an association request from the client 1410. The satellite AP 1408 may determine the autonomy of the associate request based on stored autonomy grants 1006. The satellite AP 1408 may then determine whether to perform the associate with the client 1410 autonomously or to contact the root AP 1406.

[00128] FIG. 15 illustrates a method 1500 for delegation of autonomy based on network conditions in a multiple AP environment in accordance with some embodiments. Illustrated in FIG. 15 is a root AP 1506, a satellite AP 1508, a client 1510, and time 1512. The root AP 1506 may be a multi-AP device 820.1 with a multi-AP controller 802. The satellite AP 1508 may be a multi-AP device 820.2, 820.3, or 820.4 with a multi-AP agent 804.2, 804.3, or 804.4, respectively. The client 1410 may be a non-AP STA 822.1, 822.2, 822.3, or 822.4.

[00129] The method 1500 may begin at operation 1502.1 with the satellite

AP 1508 transmitting a service request 1504.1. The service request 1504.1 may be a service request 1300 as described in conjunction with FIG. 13. For example, the service request 1504.1 may include a function 1302.1 and condition 1304.1. The function 1302.1 may be to perform handovers. The condition 1304.1 may not be present, in accordance with some embodiments. The condition 1304.1 may be one of the conditions disclosed herein. In some embodiments, the condition 1304.1 may be related to a measured RSSI between the root AP 1406 and the satellite AP 1408. The service request 1402.1 may be transmitted over a wired or wireless connection, e.g., link 818 or backhaul link 824.

[00130] The root AP 1506 may receive the service request 1504.1 and determine whether to grant the service request 1504.1 based on the measurements and statistics 906. For example, if there is an indication that there a packet error rate is above a threshold for communications between the root AP 1506 and the satellite AP 1508, then the root AP 1506 may grant the service request 1504.1. In some embodiments, the root AP 1506 may set a condition on the grant of the service request 1504.1, e.g., only if the packet error rate as measured by the satellite AP 1508 between the satellite AP 1508 and the root AP 1506 is greater than a threshold.

[00131] The method 1500 may continue at operation 1502.2 with the root

AP 1506 transmitting an autonomy grant information element 1504.2 in response to the service request 1504.1. The autonomy grant information element 1504.2 may be the same or similar to autonomy grant information element 1100. In some embodiments, the root AP 1506 may transmit a packet that indicates the service request 1504.1 is denied. In some embodiments, the autonomy grant information element 1504.2 may indicate the service request 1504.1 is denied. The autonomy grant element 1504.2 may include a function 1102.1 and condition 1104.1, e.g., the function 1102.1 may be to perform handovers and the condition 1104.1 may be that the function 1102.1 is granted if a packet error rate between the root AP 1506 and the satellite AP 1508 is greater than a threshold. The autonomy grant information element 1504.2 may be transmitted over a wired or wireless connection, e.g., link 818 or backhaul link 824.

[00132] The method 1500 continues at operation 1502.3 with satellite AP

1508 performing a function 1504.3 for client 1510. For example, for a function 1102 and condition 1104 pair 1106 of the autonomy grant information element 1504.2 with a condition (e.g., if a packet error rate between the root AP 1506 and the satellite AP 1508 is greater than a threshold) and with the function being handover, then the function 1102 may be for the satellite AP 1508 to handover the client 1510 to another satellite AP (not illustrated.) The operation 1502.3 may be the same or similar to operations 1402.3 and/or 1402.5.

[00133] The method 1500 may continue at operation 1502.4 with the satellite AP 1508 transmitting a second service request 1504.4. The second service request 1504.4 may be a service request 1300 as described in conjunction with FIG. 13. For example, the second service request 1504.4 may include a function 1302.1 and condition 1304.1. The function 1302.1 may be to perform handovers. The condition 1304.1 may not be present, in accordance with some embodiments. The condition 1304.1 may be one of the conditions disclosed herein. In some embodiments, the condition 1304.1 may be related to a measured RSSI between the root AP 1406 and the satellite AP 1408. The service request 1402.1 may be transmitted over a wired or wireless connection, e.g., link 818 or backhaul link 824.

[00134] The method 1500 may continue at operation 1502.5 with the root

AP 1506 transmitting a second autonomy grant information element 1504.5 in response to the second service request 1504.4. Operation 1502.5 may be the same or similar to operation 1504.2. The second autonomy grant information element 1504.5 may be the same or similar to autonomy grant information element 1504.2. The second autonomy grant information element 1504.5 may replace the autonomy grant information element 1504.2 or supplement the autonomy grant information element 1502.2. The satellite AP 1508 updates its autonomy grants 1006.

[00135] The method 1500 continues at operation 1502.3 with satellite AP

1508 performing a function 1504.3 for client 1510. The operation 1502.6 may be the same or similar to operations 1502.3, 1402.3 and/or 1402.5.

[00136] FIG. 16 illustrates a method 1600 for delegation of autonomy based on network conditions in a multiple AP environment in accordance with some embodiments. The method 1600 begins at operation 1602 with decoding a first PPDU received from a second AP, the first PPDU comprising an autonomy grant, the autonomy grant indicating a function and a condition, wherein the autonomy grant indicates that when the condition is met that the first access point is authorized to perform the function.

[00137] For example, satellite AP 1408 may receive autonomy grant information element 1404.2 or 1404.4 from root AP 1406. In another example, satellite AP 1508 may receive autonomy grant information element 1504.2 or 1504.5.

[00138] The method 1600 continues at operation 1604 with determining whether the condition is met. For example, satellite AP 1408 may determine whether autonomy grant information element 1404.2 or 1404.4 includes a function 1102 and condition 1104 pair 1106 where the condition 1104 is met. In another example, satellite AP 1508 may determine whether autonomy grant information element 1504.2 or 1504.5 includes a function 1 102 and condition 1 104 pair where the condition 1 104 is met.

[00139] The method 1600 continues at operation 1606 with decoding a second PPDU received from a station, the second PPDU requesting the function be performed for the station. For example, satellite AP 1408 may receive a PPDU from a client 1410 at operation 1402.3 or operation 1402.5 requesting a function 1 102 or indicating that a function should be performed for the client 1510. In another example, satellite AP 1508 may receive a PPDU from a client 1510 at operation 1502.3 or 1502.6 requesting a function 1 102 or that indicates that a function 1 102 should be performed for the client 1510.

[00140] The method 1600 continues at operation 1606 with if or when the determination is that the condition is met, performing the function for the station, wherein the memory is configured to store the first PPDU and the second PPDU. For example, satellite AP 1408 may determine if a condition 1 104 of the autonomy grant information element 1404.2 or autonomy grant information element 1404.4 is met, and if the condition 1 104 is met, then the satellite AP 1408 may perform the function 1 102 of the function 1 104 and condition pair 1 106 as disclosed in conjunction with FIG. 14.

[00141] In another example, satellite AP 1508 may determine if a condition 1 104 of the autonomy grant information element 1504.2 or autonomy grant information element 1504.4 is met, and if the condition 1 104 is met, then the satellite AP 1508 may perform the function 1 102 of the function 1 104 and condition pair 1 106 as disclosed in conjunction with FIG. 15.

[00142] In some embodiments, the order of the operations of method 1600 may be different, and one or more operations may be omitted. Additionally, method 1600 may include one or more additional operations. In some embodiments, method 1600 may be performed by a root AP 1506, satellite AP 1508, multi-AP device 820, an apparatus of a root AP 1506, an apparatus of a satellite AP 1508, or an apparatus of multi-AP device 820.

[00143] FIG. 17 illustrates a method 1700 for delegation of autonomy based on network conditions in a multiple AP environment in accordance with some embodiments. The method 1700 begins at operation 1702 with decoding a first PPDU, the first PPDU comprising capability information of a second AP, the capability information indicating functions the second AP is capable of performing. For example, root AP 1506 may receive capability information element 1504 at operation 1502.1 of FIG. 15.

[00144] The method 1700 continues at operation 1704 with encoding a second PPDU, the second PPDU comprising an autonomy grant, the autonomy grant indicating a function and a condition, wherein the autonomy grant indicates that when the condition is met that the second access point is authorized to perform the function, and wherein the function is one of the functions the second AP is capable of performing. For example, root AP 1506 may send autonomy grant information element 1402.2 to satellite AP 1408 where the autonomy grant information element 1402.2 may comprise N function 1 102 and condition 1 104 pairs 1 106.

[00145] The method 1700 continues at operation 1706 with configuring the first AP to transmit the second PPDU to the second AP. For example, an apparatus of the root AP 1506 may configure the root AP 1506 to transmit the autonomy grant information element 1402.2.

[00146] In some embodiments, the order of the operations of method 1700 may be different, and one or more operations may be omitted. Additionally, method 1700 may include one or more additional operations. In some embodiments, method 1700 may be performed by a root AP 1506, satellite AP 1508, multi-AP device 820, an apparatus of a root AP 1506, an apparatus of a satellite AP 1508, or an apparatus of multi-AP device 820.

[00147] Some embodiments provide a technical solution to the problem of how to maintain system (e.g., 800) network throughput when the network quality degrades by enabling satellite APs to perform functions or services. Some embodiments, enable more efficient use of the system (e.g., 800) by enabling satellite APs to perform functions or services that they would not be able to perform if the satellite AP had to rely on the root AP.

[00148] The following examples pertain to further embodiments.

Example 1 is an apparatus of a first access point (AP) comprising: memory; and processing circuitry coupled to the memory, the processing circuity configured to: decode a first Physical Layer Convergence Procedure (PLCP) Protocol Data Unit (PPDU) received from a second AP, the first PPDU comprising an autonomy grant, the autonomy grant indicating a function and a condition, wherein the autonomy grant indicates that when the condition is met that the first AP is authorized by the second AP to perform the function; determine whether the condition is met; decode a second PPDU received from a station, the second PPDU requesting the function be performed for the station; and if the determination is that the condition is met, perform the function for the station.

[00149] In Example 2, the subject matter of Example 1 optionally includes wherein the condition is one of the following group: when a measured receive signal strength indicator (RSSI) of a third PPDU from the second AP is above a first threshold, when the measured RSSI of the third PPDU is below a second threshold, when the first AP is disconnected from the second AP, when a number of hops between the first AP and the second AP is greater than a threshold, when a latency between the first AP and the second AP is greater than a threshold, when a response from the second AP to a third PPDU from the first AP is not received within a threshold period of time, when a response from the second AP to a service request from the first AP is not received within a threshold number of retries, when a communication with the second AP and the first AP has timed out, when an elapsed time since decoding the first PPDU is less than a time indicated by the condition, and when a link metric between the first AP and the second AP is below a threshold.

[00150] In Example 3, the subject matter of any one or more of Examples

1-2 optionally include wherein the function is one of the following group: a handover of the station from the first AP to a third AP, Institute of Electrical and Electronic Engineering (IEEE) 802.1 lv fast basic service set (BSS) transition from the first AP to a third AP, associate with a second station, perform beamforming, and connect to a server.

[00151] In Example 4, the subject matter of any one or more of Examples

1-3 optionally include wherein the autonomy grant is included in an autonomy grant information element, the autonomy grant information element comprising one or more pairs of functions and conditions. [00152] In Example 5, the subject matter of any one or more of Examples

1-4 optionally include wherein the first AP is a satellite AP and the second AP is a root AP.

[00153] In Example 6, the subject matter of any one or more of Examples 1-5 optionally include wherein the processing circuitry is further configured to: encode a third PPDU, the third PPDU comprising a request for an autonomy grant; configure the first AP to transmit the third PPDU to the second AP; and decode a fourth PPDU, the fourth PPDU comprising a response to the request for the autonomy grant.

[00154] In Example 7, the subject matter of Example 6 optionally includes wherein the response comprises a second condition and a second function, and wherein the processing circuitry is further configured to: determine whether the second condition is met; decode a fifth PPDU from the station, the fifth PPDU requesting the second function be performed for the station; and if the determination is that the second condition is met, perform the second function for the station.

[00155] In Example 8, the subject matter of any one or more of Examples

1-7 optionally include wherein the processing circuitry is further configured to: encode a third PPDU, the third PPDU comprising a service request for a second function; configure the first AP to transmit the third PPDU to the second AP; and decode a fourth PPDU, the fourth PPDU comprising a response to the service request for the second function.

[00156] In Example 9, the subject matter of Example 8 optionally includes wherein the response comprises an indication of whether the second function was granted to the first AP, and wherein the processing circuitry is further configured to: determine whether the second function was granted; decode a fifth PPDU from the station, the fifth PPDU requesting the second function be performed for the station; and if the determination is that the second function was granted, perform the second function for the station.

[00157] In Example 10, the subject matter of any one or more of

Examples 1-9 optionally include wherein the processing circuitry is further configured to: decode a third PPDU from the second AP, the third PPDU comprising an autonomy grant, the autonomy grant indicating a function, wherein the autonomy grant indicates that the first access point is authorized to perform the function; decode a second PPDU from a station, the second PPDU requesting the function be performed for the station; and perform the function for the station.

[00158] In Example 1 1, the subject matter of any one or more of

Examples 1-10 optionally include wherein the first PPDU is received from a multi-AP controller of the second AP.

[00159] In Example 12, the subject matter of any one or more of

Examples 1-1 1 optionally include wherein the first AP, the second AP, and the station wireless are each one from the following group: an Institute of Electrical and Electronic Engineers (IEEE) 802.1 lax access point, an IEEE 802.1 lax station, an IEEE 802.1 1 station, an IEEE 802.1 1 access point, and an IEEE multi-AP device.

[00160] In Example 13, the subject matter of any one or more of Examples 1-12 optionally include transceiver circuitry coupled to the processing circuitry; and one or more antennas coupled to the transceiver circuitry, wherein the memory is configured to store the first PPDU and the second PPDU.

[00161] Example 14 is a non-transitory computer-readable storage medium that stores instructions for execution by one or more processors of an apparatus of a first access point (AP), the instructions to configure the one or more processors to: decode a first Physical Layer Convergence Procedure (PLCP) Protocol Data Unit (PPDU) received from a second AP, the first PPDU comprising an autonomy grant, the autonomy grant indicating a function and a condition, wherein the autonomy grant indicates that when the condition is met that the first AP is authorized by the second AP to perform the function;

determine whether the condition is met; decode a second PPDU received from a station, the second PPDU requesting the function be performed for the station; and if the determination is that the condition is met, perform the function for the station.

[00162] In Example 15, the subject matter of Example 14 optionally includes wherein the instructions further configured the one or more processors to: encode a third PPDU, the third PPDU comprising a request for an autonomy grant; configure the first AP to transmit the third PPDU to the second AP; and decode a fourth PPDU, the fourth PPDU comprising a response to the request for the autonomy grant.

[00163] In Example 16, the subject matter of any one or more of

Examples 14-15 optionally include wherein the instructions further configured the one or more processors to: determine whether the second condition is met; decode a fifth PPDU from the station, the fifth PPDU requesting the second function be performed for the station; and if the determination is that the second condition is met, perform the second function for the station.

[00164] Example 17 is a method performed by an apparatus of a first access point (AP), the method comprising: decoding a first Physical Layer Convergence Procedure (PLCP) Protocol Data Unit (PPDU) received from a second AP, the first PPDU comprising an autonomy grant, the autonomy grant indicating a function and a condition, wherein the autonomy grant indicates that when the condition is met that the first AP is authorized by the second AP to perform the function; determining whether the condition is met; decoding a second PPDU received from a station, the second PPDU requesting the function be performed for the station; and if the determination is that the condition is met, performing the function for the station.

[00165] In Example 18, the subject matter of Example 17 optionally includes wherein the condition is one of the following group: if a measured receive signal strength indicator (RSSI) of a third PPDU from the second AP is above a first threshold, if the measured RSSI of the third PPDU is below a second threshold, and wherein the function is one of the following group: a handover of the station from the first AP to a third AP, and Institute of Electrical and Electronic Engineering (IEEE) 802.1 lv fast basic service set (BSS) transition from the first AP to a third AP.

[00166] Example 19 is an apparatus of a first access point (AP) comprising: memory; and processing circuitry coupled to the memory, the processing circuity configured to: decode a first Physical Layer Convergence Procedure (PLCP) Protocol Data Unit (PPDU), the first PPDU comprising capability information of a second AP, the capability information indicating functions the second AP is capable of performing; encode a second PPDU, the second PPDU comprising an autonomy grant, the autonomy grant indicating a function and a condition, wherein the autonomy grant indicates that when the condition is met that the second access point is authorized to perform the function, and wherein the function is one of the functions the second AP is capable of performing; and configure the first AP to transmit the second PPDU to the second AP, wherein the memory is configured to store the first PPDU and the second PPDU.

[00167] In Example 20, the subject matter of Example 19 optionally includes wherein the processing circuitry is further configured to: decode a third PPDU, the third PPDU comprising a request for an autonomy grant from the second AP; encode a fourth PPDU, the fourth PPDU comprising a response to the request for the autonomy grant; and configure the first AP to transmit the fourth PPDU to the second AP.

[00168] In Example 21, the subject matter of Example 20 optionally includes wherein the response comprises a second condition and a second function.

[00169] In Example 22, the subject matter of any one or more of

Examples 19-21 optionally include wherein the processing circuitry is further configured to: decode a third PPDU, the third PPDU comprising a service request for a second function; determine whether to grant the second function to the second AP; encode a fourth PPDU, the fourth PPDU comprising a response to the service request for the second function; and configure the first AP to transmit the third PPDU to the second AP, wherein the response comprises an indication of whether the second function was granted to the second AP.

[00170] In Example 23, the subject matter of any one or more of Examples 19-22 optionally include wherein the autonomy grant is included in an autonomy grant information element, the autonomy grant information element comprising one or more autonomy grants.

[00171] In Example 24, the subject matter of any one or more of

Examples 20-23 optionally include wherein the first AP, the second AP, and the station wireless are each one from the following group: an Institute of Electrical and Electronic Engineers (IEEE) 802.1 lax access point, an IEEE 802.1 lax station, an IEEE 802.11 station, and an IEEE 802.11 access point. [00172] In Example 25, the subject matter of any one or more of

Examples 20-24 optionally include transceiver circuitry coupled to the processing circuitry; and, one or more antennas coupled to the transceiver circuitry.

[00173] Example 26 is a non-transitory computer-readable storage medium that stores instructions for execution by one or more processors of an apparatus of a first wireless device, the instructions to configure the one or more processors to: decode a first Physical Layer Convergence Procedure (PLCP) Protocol Data Unit (PPDU), the first PPDU comprising capability information of a second AP, the capability information indicating functions the second AP is capable of performing; encode a second PPDU, the second PPDU comprising an autonomy grant, the autonomy grant indicating a function and a condition, wherein the autonomy grant indicates that when the condition is met that the second access point is authorized to perform the function, and wherein the function is one of the functions the second AP is capable of performing; and configure the first AP to transmit the second PPDU to the second AP, wherein the memory is configured to store the first PPDU and the second PPDU.

[00174] In Example 27, the subject matter of Example 26 optionally includes wherein the instructions further configure the one or more processors to: decode a third PPDU, the third PPDU comprising a request for an autonomy grant from the second AP; encode a fourth PPDU, the fourth PPDU comprising a response to the request for the autonomy grant; and configure the first AP to transmit the fourth PPDU to the second AP.

[00175] In Example 28, the subject matter of any one or more of

Examples 26-27 optionally include wherein the response comprises a second condition and a second function.

[00176] In Example 29, the subject matter of any one or more of

Examples 26-28 optionally include wherein the instructions further configure the one or more processors to: decode a third PPDU, the third PPDU comprising a service request for a second function; determine whether to grant the second function to the second AP; encode a fourth PPDU, the fourth PPDU comprising a response to the service request for the second function; and configure the first AP to transmit the third PPDU to the second AP, wherein the response comprises an indication of whether the second function was granted to the second AP.

[00177] In Example 30, the subject matter of any one or more of

Examples 26-29 optionally include wherein the autonomy grant is included in an autonomy grant information element, the autonomy grant information element comprising one or more autonomy grants.

[00178] In Example 31, the subject matter of any one or more of

Examples 26-30 optionally include wherein the first AP, the second AP, and the station wireless are each one from the following group: an Institute of Electrical and Electronic Engineers (IEEE) 802.1 lax access point, an IEEE 802.1 lax station, an IEEE 802.1 1 station, and an IEEE 802.1 1 access point.

[00179] Example 32 is a method performed by an apparatus of a first wireless device, the method comprising: decoding a first Physical Layer Convergence Procedure (PLCP) Protocol Data Unit (PPDU), the first PPDU comprising capability information of a second AP, the capability information indicating functions the second AP is capable of performing; encoding a second PPDU, the second PPDU comprising an autonomy grant, the autonomy grant indicating a function and a condition, wherein the autonomy grant indicates that when the condition is met that the second access point is authorized to perform the function, and wherein the function is one of the functions the second AP is capable of performing; and configuring the first AP to transmit the second PPDU to the second AP, wherein the memory is configured to store the first PPDU and the second PPDU.

[00180] In Example 33, the subject matter of Example 32 optionally includes wherein the method further comprises: decoding a third PPDU, the third PPDU comprising a request for an autonomy grant from the second AP;

encoding a fourth PPDU, the fourth PPDU comprising a response to the request for the autonomy grant; and configuring the first AP to transmit the fourth PPDU to the second AP.

[00181] In Example 34, the subject matter of any one or more of

Examples 32-33 optionally include wherein the response comprises a second condition and a second function. [00182] In Example 35, the subject matter of any one or more of

Examples 32-34 optionally include wherein the method further comprises: decoding a third PPDU, the third PPDU comprising a service request for a second function; determining whether to grant the second function to the second AP; encoding a fourth PPDU, the fourth PPDU comprising a response to the service request for the second function; and configuring the first AP to transmit the third PPDU to the second AP, wherein the response comprises an indication of whether the second function was granted to the second AP.

[00183] In Example 36, the subject matter of any one or more of Examples 32-35 optionally include wherein the autonomy grant is included in an autonomy grant information element, the autonomy grant information element comprising one or more autonomy grants.

[00184] In Example 37, the subject matter of any one or more of

Examples 32-36 optionally include wherein the first AP, the second AP, and the station wireless are each one from the following group: an Institute of Electrical and Electronic Engineers (IEEE) 802.1 lax access point, an IEEE 802.1 lax station, an IEEE 802.1 1 station, and an IEEE 802.1 1 access point.

[00185] Example 38 is an apparatus of a first wireless device, the apparatus comprising: means for decoding a first Physical Layer Convergence Procedure (PLCP) Protocol Data Unit (PPDU), the first PPDU comprising capability information of a second AP, the capability information indicating functions the second AP is capable of performing; means for encoding a second PPDU, the second PPDU comprising an autonomy grant, the autonomy grant indicating a function and a condition, wherein the autonomy grant indicates that when the condition is met that the second access point is authorized to perform the function, and wherein the function is one of the functions the second AP is capable of performing; and means for configuring the first AP to transmit the second PPDU to the second AP, wherein the memory is configured to store the first PPDU and the second PPDU.

[00186] In Example 39, the subject matter of Example 38 optionally includes wherein the apparatus further comprises: means for decoding a third PPDU, the third PPDU comprising a request for an autonomy grant from the second AP; means for encoding a fourth PPDU, the fourth PPDU comprising a response to the request for the autonomy grant; and means for configuring the first AP to transmit the fourth PPDU to the second AP.

[00187] In Example 40, the subject matter of Example 39 optionally includes wherein the response comprises a second condition and a second function.

[00188] In Example 41, the subject matter of any one or more of

Examples 39-40 optionally include wherein the apparatus further comprises: means for decoding a third PPDU, the third PPDU comprising a service request for a second function; means for determining whether to grant the second function to the second AP; means for encoding a fourth PPDU, the fourth PPDU comprising a response to the service request for the second function; and means for configuring the first AP to transmit the third PPDU to the second AP, wherein the response comprises an indication of whether the second function was granted to the second AP.

[00189] In Example 42, the subject matter of any one or more of

Examples 39-41 optionally include wherein the autonomy grant is included in an autonomy grant information element, the autonomy grant information element comprising one or more autonomy grants.

[00190] In Example 43, the subject matter of any one or more of Examples 39-42 optionally include wherein the first AP, the second AP, and the station wireless are each one from the following group: an Institute of Electrical and Electronic Engineers (IEEE) 802.1 lax access point, an IEEE 802.1 lax station, an IEEE 802.1 1 station, and an IEEE 802.1 1 access point.

[00191] Example 44 is an apparatus of a first access point (AP) comprising: means for decoding a first Physical Layer Convergence Procedure (PLCP) Protocol Data Unit (PPDU) received from a second AP, the first PPDU comprising an autonomy grant, the autonomy grant indicating a function and a condition, wherein the autonomy grant indicates that when the condition is met that the first AP is authorized by the second AP to perform the function; means for determining whether the condition is met; means for decoding a second PPDU received from a station, the second PPDU requesting the function be performed for the station; and if the determination is that the condition is met, means for performing the function for the station. [00192] In Example 45, the subject matter of Example 44 optionally includes wherein the condition is one of the following group: when a measured receive signal strength indicator (RSSI) of a third PPDU from the second AP is above a first threshold, when the measured RSSI of the third PPDU is below a second threshold, when the first AP is disconnected from the second AP, when a number of hops between the first AP and the second AP is greater than a threshold, when a latency between the first AP and the second AP is greater than a threshold, when a response from the second AP to a third PPDU from the first AP is not received within a threshold period of time, when a response from the second AP to a service request from the first AP is not received within a threshold number of retries, when a communication with the second AP and the first AP has timed out, when an elapsed time since decoding the first PPDU is less than a time indicated by the condition, and when a link metric between the first AP and the second AP is below a threshold.

[00193] In Example 46, the subject matter of any one or more of

Examples 44-45 optionally include wherein the function is one of the following group: a handover of the station from the first AP to a third AP, Institute of Electrical and Electronic Engineering (IEEE) 802.1 lv fast basic service set (BSS) transition from the first AP to a third AP, associate with a second station, perform beamforming, and connect to a server.

[00194] In Example 47, the subject matter of any one or more of

Examples 44-46 optionally include wherein the autonomy grant is included in an autonomy grant information element, the autonomy grant information element comprising one or more pairs of functions and conditions.

[00195] In Example 48, the subject matter of any one or more of

Examples 44-47 optionally include wherein the first AP is a satellite AP and the second AP is a root AP.

[00196] In Example 49, the subject matter of any one or more of

Examples 44-48 optionally include wherein the apparatus further comprising: means for encoding a third PPDU, the third PPDU comprising a request for an autonomy grant; means for configuring the first AP to transmit the third PPDU to the second AP; and means for decoding a fourth PPDU, the fourth PPDU comprising a response to the request for the autonomy grant. [00197] In Example 50, the subject matter of Example 49 optionally includes wherein the response comprises a second condition and a second function, and wherein the apparatus further comprises: means for determining whether the second condition is met; means for decoding a fifth PPDU from the station, the fifth PPDU requesting the second function be performed for the station; and if the determination is that the second condition is met, means for performing the second function for the station.

[00198] In Example 51, the subject matter of any one or more of

Examples 44-50 optionally include wherein the apparatus further comprising: means for encoding a third PPDU, the third PPDU comprising a service request for a second function; means for configuring the first AP to transmit the third PPDU to the second AP; and means for decoding a fourth PPDU, the fourth PPDU comprising a response to the service request for the second function.

[00199] In Example 52, the subject matter of Example 51 optionally includes wherein the response comprises an indication of whether the second function was granted to the first AP, and wherein the apparatus further comprises: means for determining whether the second function was granted; means for decoding a fifth PPDU from the station, the fifth PPDU requesting the second function be performed for the station; and if the determination is that the second function was granted, means for performing the second function for the station.

[00200] In Example 53, the subject matter of any one or more of

Examples 44-52 optionally include wherein the apparatus further comprises: means for decoding a third PPDU from the second AP, the third PPDU comprising an autonomy grant, the autonomy grant indicating a function, wherein the autonomy grant indicates that the first access point is authorized to perform the function; means for decoding a second PPDU from a station, the second PPDU requesting the function be performed for the station; and means for performing the function for the station.

[00201] In Example 54, the subject matter of any one or more of

Examples 44-53 optionally include wherein the first PPDU is received from a multi-AP controller of the second AP. [00202] In Example 55, the subject matter of any one or more of

Examples 44-54 optionally include wherein the first AP, the second AP, and the station wireless are each one from the following group: an Institute of Electrical and Electronic Engineers (IEEE) 802.1 lax access point, an IEEE 802.1 lax station, an IEEE 802.1 1 station, an IEEE 802.1 1 access point, and an IEEE multi-AP device.

[00203] In Example 56, the subject matter of any one or more of

Examples 44-55 optionally include means for processing radio-frequency signals coupled to means for storing and retrieving the first PPDU; and means for transmitting and receiving the radio-frequency signals coupled to the means for processing the radio-frequency signals.

[00204] The Abstract is provided to comply with 37 C.F.R. Section

1.72(b) requiring an abstract that will allow the reader to ascertain the nature and gist of the technical disclosure. It is submitted with the understanding that it will not be used to limit or interpret the scope or meaning of the claims. The following claims are hereby incorporated into the detailed description, with each claim standing on its own as a separate embodiment.

Claims

CLAIMS What is claimed is:

1. An apparatus of a first access point (AP) comprising: memory; and processing circuitry coupled to the memory, the processing circuity configured to:

decode a first Physical Layer Convergence Procedure (PLCP) Protocol Data Unit (PPDU) received from a second AP, the first PPDU comprising an autonomy grant, the autonomy grant indicating a function and a condition, wherein the autonomy grant indicates that when the condition is met that the first AP is authorized by the second AP to perform the function;

determine whether the condition is met;

decode a second PPDU received from a station, the second PPDU requesting the function be performed for the station; and

if the determination is that the condition is met, perform the function for the station.

2. The apparatus of claim 1, wherein the condition is one of the following group: when a measured receive signal strength indicator (RSSI) of a third PPDU from the second AP is above a first threshold, when the measured RSSI of the third PPDU is below a second threshold, when the first AP is disconnected from the second AP, when a number of hops between the first AP and the second AP is greater than a threshold, when a latency between the first AP and the second AP is greater than a threshold, when a response from the second AP to a third PPDU from the first AP is not received within a threshold period of time, when a response from the second AP to a service request from the first AP is not received within a threshold number of retries, when a communication with the second AP and the first AP has timed out, when an elapsed time since decoding the first PPDU is less than a time indicated by the condition, and when a link metric between the first AP and the second AP is below a threshold.

3. The apparatus of claim 1, wherein the function is one of the following group: a handover of the station from the first AP to a third AP, Institute of Electrical and Electronic Engineering (IEEE) 802.1 lv fast basic service set (BSS) transition from the first AP to a third AP, associate with a second station, perform beamforming, and connect to a server.

4. The apparatus of claim 1, wherein the autonomy grant is included in an autonomy grant information element, the autonomy grant information element comprising one or more pairs of functions and conditions.

5. The apparatus of claim 1, wherein the first AP is a satellite AP and the second AP is a root AP.

6. The apparatus of claim 1, wherein the processing circuitry is further configured to :

encode a third PPDU, the third PPDU comprising a request for an autonomy grant;

configure the first AP to transmit the third PPDU to the second AP; and decode a fourth PPDU, the fourth PPDU comprising a response to the request for the autonomy grant.

7. The apparatus of claim 6, wherein the response comprises a second condition and a second function, and wherein the processing circuitry is further configured to:

determine whether the second condition is met;

decode a fifth PPDU from the station, the fifth PPDU requesting the second function be performed for the station; and

if the determination is that the second condition is met, perform the second function for the station.

8. The apparatus of claim 1, wherein the processing circuitry is further configured to: encode a third PPDU, the third PPDU comprising a service request for a second function;

configure the first AP to transmit the third PPDU to the second AP; and decode a fourth PPDU, the fourth PPDU comprising a response to the service request for the second function.

9. The apparatus of claim 8, wherein the response comprises an indication of whether the second function was granted to the first AP, and wherein the processing circuitry is further configured to:

determine whether the second function was granted;

if the determination is that the second function was granted, perform the second function for the station.

10. The apparatus of claim 1, wherein the processing circuitry is further configured to:

decode a third PPDU from the second AP, the third PPDU comprising an autonomy grant, the autonomy grant indicating a function, wherein the autonomy grant indicates that the first access point is authorized to perform the function;

decode a second PPDU from a station, the second PPDU requesting the function be performed for the station; and

perform the function for the station.

1 1. The apparatus of claim 1, wherein the first PPDU is received from a multi-AP controller of the second AP.

12. The apparatus of claim 1, wherein the first AP, the second AP, and the station wireless are each one from the following group: an Institute of

Electrical and Electronic Engineers (IEEE) 802.1 lax access point, an IEEE 802.1 lax station, an IEEE 802.1 1 station, an IEEE 802.1 1 access point, and an IEEE multi-AP device.

13. The apparatus of claim 1, further comprising transceiver circuitry coupled to the processing circuitry; and one or more antennas coupled to the transceiver circuitry, wherein the memory is configured to store the first PPDU and the second PPDU.

14. A non-transitory computer-readable storage medium that stores instructions for execution by one or more processors of an apparatus of a first access point (AP), the instructions to configure the one or more processors to: decode a first Physical Layer Convergence Procedure (PLCP) Protocol Data Unit (PPDU) received from a second AP, the first PPDU comprising an autonomy grant, the autonomy grant indicating a function and a condition, wherein the autonomy grant indicates that when the condition is met that the first AP is authorized by the second AP to perform the function;

determine whether the condition is met;

15. The non-transitory computer-readable storage medium of claim 14, wherein the instructions further configured the one or more processors to: encode a third PPDU, the third PPDU comprising a request for an autonomy grant;

16. The non-transitory computer-readable storage medium of claim 14, wherein the instructions further configured the one or more processors to: determine whether the second condition is met;

decode a fifth PPDU from the station, the fifth PPDU requesting the second function be performed for the station; and if the determination is that the second condition is met, perform the second function for the station.

17. A method performed by an apparatus of a first access point (AP), the method comprising:

decoding a first Physical Layer Convergence Procedure (PLCP) Protocol Data Unit (PPDU) received from a second AP, the first PPDU comprising an autonomy grant, the autonomy grant indicating a function and a condition, wherein the autonomy grant indicates that when the condition is met that the first AP is authorized by the second AP to perform the function;

determining whether the condition is met;

decoding a second PPDU received from a station, the second PPDU requesting the function be performed for the station; and

if the determination is that the condition is met, performing the function for the station.

18. The method of claim 17, wherein the condition is one of the following group: if a measured receive signal strength indicator (RSSI) of a third PPDU from the second AP is above a first threshold, if the measured RSSI of the third PPDU is below a second threshold, and wherein the function is one of the following group: a handover of the station from the first AP to a third AP, and Institute of Electrical and Electronic Engineering (IEEE) 802.1 lv fast basic service set (BSS) transition from the first AP to a third AP.

19. An apparatus of a first access point (AP) comprising: memory; and processing circuitry coupled to the memory, the processing circuity configured to:

decode a first Physical Layer Convergence Procedure (PLCP) Protocol Data Unit (PPDU), the first PPDU comprising capability information of a second AP, the capability information indicating functions the second AP is capable of performing;

encode a second PPDU, the second PPDU comprising an autonomy grant, the autonomy grant indicating a function and a condition, wherein the autonomy grant indicates that when the condition is met that the second access point is authorized to perform the function, and wherein the function is one of the functions the second AP is capable of performing; and

configure the first AP to transmit the second PPDU to the second AP, wherein the memory is configured to store the first PPDU and the second PPDU.

20. The apparatus of claim 19, wherein the processing circuitry is further configured to:

decode a third PPDU, the third PPDU comprising a request for an autonomy grant from the second AP;

encode a fourth PPDU, the fourth PPDU comprising a response to the request for the autonomy grant; and

configure the first AP to transmit the fourth PPDU to the second AP.

21. The apparatus of claim 20, wherein the response comprises a second condition and a second function.

22. The apparatus of claim 19, wherein the processing circuitry is further configured to:

decode a third PPDU, the third PPDU comprising a service request for a second function;

determine whether to grant the second function to the second AP;

encode a fourth PPDU, the fourth PPDU comprising a response to the service request for the second function; and

configure the first AP to transmit the third PPDU to the second AP, wherein the response comprises an indication of whether the second function was granted to the second AP.

23. The apparatus of claim 19, wherein the autonomy grant is included in an autonomy grant information element, the autonomy grant information element comprising one or more autonomy grants.

24. The apparatus of claim 20, wherein the first AP, the second AP, and the station wireless are each one from the following group: an Institute of Electrical and Electronic Engineers (IEEE) 802.1 lax access point, an IEEE 802.1 lax station, an IEEE 802.11 station, and an IEEE 802.1 1 access point.

25. The apparatus of claim 20, further comprising transceiver circuitry coupled to the processing circuitry; and, one or more antennas coupled to the transceiver circuitry.