WO2018102019A1 - Mechanism for authenticating wake-up radio packets - Google Patents

Abstract

Aspects of authenticating wake-up packets for a low-power wake-up radio (LP-WUR) are described. In some aspects, a station (STA) in a low-power state, such as a WUR mode, can receive a wake-up packet from an access point (AP). In some aspects, the STA can decode from the wake-up packet, a WUR authentication field including an authentication value and calculate a WUR authentication output value based on a WUR authentication input and a WUR authentication function, wherein the apparatus obtains the WUR authentication input and the WUR authentication function during a WUR negotiation with the AP. In some aspects, the STA can compare the WUR authentication output value to the authentication value, and authenticate the received wake-up packet based on the WUR authentication output value matching the authentication value.

Description

MECHANISM FOR AUTHENTICATING WAKE-UP RADIO PACKETS

PRIORITY CLAIM

[0001] This application claims priority under 35 USC 119(e) to

United States Provisional Patent Application Serial No. 62/428,636 filed December 1, 2016, which is incorporated herein by reference in its entirety.

TECHNICAL FIELD

[0002] Aspects pertain to wireless networks and wireless communications. Some aspects relate to wireless local area networks (WLANs) and Wi-Fi networks including networks operating in accordance with the IEEE 802.11 family of standards. Some aspects relate to IEEE 802.1 lay. Some aspects relate to methods, computer readable media, and apparatus for authenticating wake-up radio packets with respect to low-power wake-up radios.

BACKGROUND

[0003] Low-Power Wake-Up Radio (LP-WUR) is a technique to enable ultra-low power operation for wireless (e.g., Wi-Fi) devices, A wireless device may have a LP-WUR that can receive wake-up packets from a peer device or an access point. The wireless device may remain in a low-power mode until receiving a wake-up packet from an access point.

[0004] In recent years, applications have been developed relating to social networking, Internet of Things (lo'T), wireless docking, and the like. It may be desirable to design low power solutions that can be always-on. Multiple efforts are ongoing in the wireless industry to address this challenge. In some aspects, the subject technology uses the Wi-Fi alliance (WFA) neighbor aware networking (NAN) program to define a mechanism for Wi-Fi devices to maintain low power and achieve service discovery. In Bluetooth® Special Interest Group (SIG), Bluetooth® Low Energy provides a power-efficient protocol for some use cases. In the Institute of Electrical and Electronics Engineers (IEEE), low-power wake-up radio (LP-WUR) has gained interest. The idea of the LP-WUR is to utilize an extremely low power radio such that a device can be in listening mode with minimum capability and consume extremely low power. If the main radio is required for data transmission, a wake- up packet may be sent out by a peer device or an access point (AP) to wake-up the main wireless local area network (WLAN) radio (e.g., Wi-Fi radio).

BRIEF DESCRIPTION OF THE DRAWINGS

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

[0006] FIG. 2 illustrates a front-end module circuitry for use in the radio

architecture of FIG. 1 in accordance with some aspects;

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

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

[0009] FIG. 5 illustrates a wireless network, in accordance with some aspects;

[0010] FIG. 6 illustrates an example machine, in accordance with some aspects;

[0011] FIG. 7 illustrates a station (STA) in accordance with some aspects and an access point (AP), in accordance with some aspects;

[0012] FIG. 8 illustrates an example system in which a low-power wake-up radio (LP-WUR) is operated, in accordance with some aspects;

[0013] FIG. 9 is a flow diagram illustrating an example method of wake-up packet authentication, in accordance with some aspects, and

[0014] FIG. 10 illustrates an example wake-up frame format in accordance with some aspects. DETAILED DESCRIPTION

[0015] The following description and the drawings sufficiently illustrate specific aspects to enable those skilled in the art to practice them. Other aspects may incorporate structural, logical, electrical, process, and other changes.

Portions and features of some aspects may be included in, or substituted for, those of other aspects. Aspects set forth in the claims encompass all available equivalents of those claims,

[0016] FIG. 1 is a block diagram of a radio architecture 100 in accordance with some aspects. Radio architecture 100 may be configured to perform one or more methods of wake-up packet authentication, according to aspects described herein. 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 aspects are not so limited. In this disclosure, "WLAN" and "Wi-Fi" are used interchangeably,

[0017] FEM circuitry 104 may include a WLAN or Wi-Fi FEM circuitry 104 A 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 106 A 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 aspect of FIG. 1, although FEM 104 A and FEM 104B are shown as being distinct from one another, aspects 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.

[0018] Radio IC circuitry 106 as shown may include WLAN radio IC circuitry 106 A and BT radio IC circuitry 106B. The WLAN radio IC circuitry 106 A may include a receive signal path which may include circuitry to down- convert WLAN RF signals received from the FEM circuitry 104 A and provide baseband signals to WLAN baseband processing circuitry 108 A. 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 106 A may also include a transmit signal path which may include circuitry to up-convert WLAN baseband signals provided by the WL AN baseband processing circuitry 108 A and provide WLAN RF output signals to the FEM circuitry 104 A for subsequent wireless transmission by the one or more antennas 101. BT radio IC circuitry 06B 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 aspect of FIG. 1, although radio IC circuitries 106 A and 106B are shown as being distinct from one another, aspects 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. [0019] Baseband processing circuity 108 may include a WLAN baseband processing circuitry 108A and a BT baseband processing circuitry 108B. The WLAN baseband processing circuitry 108 A 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 108 A. Each of the WLAN baseband circuitry 108 A 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 11 1 for generation and processing of the baseband signals and for controlling operations of the radio IC circuitry 106.

[0020] Referring still to FIG. 1 , according to the shown aspect, WLAN-

BT coexistence circuitry 1 13 may include logic providing an interface between the WLAN baseband circuitry 108 A 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 104 A 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 104 A and the BT FEM circuitry 104B, aspects 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 104 A or 104B.

[0021] In some aspects, 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 aspects, 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 aspects, 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.

[0022] In some aspects, the wireless radio card 102 may include a

WLAN radio card and may be configured for Wi-Fi communications, although the scope of the aspects is not limited in this respect. In some of these aspects, 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.

[0023] In some of these multicarrier aspects, radio archi tecture 100 may^¬ be part of a Wi-Fi communication station (ST A) such as a wireless access point (AP), a base station or a mobile device including a Wi-Fi device. In some of these aspects, 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 ln-2009, IEEE 802.11-2012, IEEE 802.11- 2016, IEEE 802.1 lac, and/or IEEE 802.1 l ax standards and/or proposed specifications for WLANs, although the scope of aspects 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.

[0024] In some aspects, 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 aspects, the radio architecture 100 may be configured to communicate in accordance with an OFDM A technique, although the scope of the aspects is not limited in this respect.

[0025] In some other aspects, 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 aspects is not limited in this respect,

[0026] In some aspects, 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 aspects 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 aspects 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 aspects is not limited in this respect. In some of these aspects 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 aspects is not limited in this respect. In some aspects, 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 aspects are not so limited, and include within their scope discrete WLAN and BT radio cards

[0027] In some aspects, 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).

[0028] In some IEEE 802.1 1 aspects, 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+8QMHz (160MHz) (with non-contiguous bandwidths). In some aspects, a 320 MHz channel bandwidth may be used. The scope of the aspects is not limited with respect to the above center frequencies however.

[0029] FIG. 2 illustrates FEM circuitry 200 in accordance with some aspects. 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.

[0030] In some aspects, the FEM circuitry 200 may include a T¾'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 (EPFs) 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)). |0031| In some dual-mode aspects for Wi-Fi communication, the FEM circuitry 200 may be configured to operate in either the 2.4 GHz frequency spectrum or the 5 GHz frequency spectrum. In these aspects, 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 aspects, 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. I). In some aspects, 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.

[0032] FIG. 3 illustrates radio IC circuitry 300 in accordance with some aspects. 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.

[0033] In some aspects, 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 3 4 may each, according to some aspects, 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, aspects where each of the depicted circuitries may include more than one component. For instance, mixer circuitry 320 and/or 3 14 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.

[0034] In some aspects, 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 aspects, the output baseband signals 307 may be zero-frequency baseband signals, although this is not a requirement. In some aspects, mixer circuitry 302 may comprise passive mixers, although the scope of the aspects is not limited in this respect,

[0035] In some aspects, the mixer circuitry 314 may be configured to up- convert input baseband signals 311 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 311 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 aspects is not limited in this respect.

[0036] In some aspects, 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 aspects, 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 aspects, the mixer circuitry 302 and the mixer circuitry 314 may be arranged for direct down-conversion and/or direct up- conversion, respectively. In some aspects, the mixer circuitry 302 and the mixer circuitry 314 may be configured for super-heterodyne operation, although this is not a requirement.

[0037] Mixer circuitry 302 may comprise, according to one aspect: quadrature passive mixers (e.g., for the in-phase (I) and quadrature phase (Q) paths). In such an aspect, 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

[0038] 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 aspects, the LO frequency may be the carrier frequency, while in other aspects, 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 aspects, the zero and ninety-degree time- varying switching signals may be generated by the synthesizer, although the scope of the aspects is not limited in this respect.

[0039] In some aspects, 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 aspects, the LO signals may have a 25% duty cycle and a 50% offset. In some aspects, 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.

[0040] The RF input signal 207 (FIG. 2) may comprise a balanced signal, although the scope of the aspects 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).

[0041] In some aspects, the output baseband signals 307 and the input baseband signals 311 may be analog baseband signals, although the scope of the aspects is not limited in this respect. In some alternate aspects, the output baseband signals 307 and the input baseband signals 31 1 may be digital baseband signals. In these alternate aspects, the radio IC circuitry may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry.

[0042] In some dual-mode aspects, 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 aspects is not limited in this respect.

[0043] In some aspects, the synthesizer circuitry 304 may be a fractional-

N synthesizer or a fractional N/N+l synthesizer, although the scope of the aspects 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 aspects, 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 aspects, 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 aspects, a divider control input (e.g., N) may be determined from a

I I 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 111.

[0044] In some aspects, synthesizer circuitry 304 may be configured to generate a carrier frequency as the output frequency 305, while in other aspects, 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 aspects, the output frequency 305 may be a LO frequency (fLo).

[0045] FIG. 4 illustrates a functional block diagram of baseband processing circuitry 400 in accordance with some aspects. 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 311 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.

[0046] In some aspects (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 aspects, the baseband processing circuitry 400 may also include DAC 412 to convert digital baseband signals from the TX BBP 404 to analog baseband signals.

[0047] In some aspects that communicate OFDM signals or OFDMA signals, such as through baseband processor 108 A, the transmit baseband processor 404 may be configured to generate OFDM or OFDM A 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 aspects, 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.

[0048] Referring back to FIG. 1, in some aspects, the antennas 101 (FIG.

1) may each comprise one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopoie 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) aspects, 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 aspects are not so limited.

[0049] 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 aspects, the functional elements may refer to one or more processes operating on one or more processing elements.

[0050] A LP-WUR enables ultra-low power operation of devices, for example, Wi-Fi devices. In some aspects, a device including a LP-WUR can receive one or more wake-up packets from a peer device, enabling the device to stay in a low-power mode until receiving the wake-up packet. A wake-up packet may be transmitted from a station (ST A) to an AP or from an AP to a ST A to cause the receiver to wake up its WLAN radio. Aspects of the subject technology relate to a low-power wake-up radio (LP-WUR) architectures and signaling, for example, a LP-WUR architectures and signaling for use in orthogonal frequency division multiplexing (OFDM) based Wi-Fi systems. The LP-WUR provides a low-power solution (e.g., approximately 100 μW in active state) for always-on Wi-Fi (or Bluetooth®) connectivity of wearable, loT (Internet of Things) and other emerging devices that may be densely deployed and used. In some aspects, the LP-WUR is configured to operate within the legacy 802.1 la/g/n/ac specifications by the Institute of Electrical and Electronics Engineers, utilizing a 4 microsecond OFDM symbol duration.

[0051] Some aspects relate to signaling for an IEEE 802.1 1 device, for example, an IEEE 802.1 1 device may be configured to transmit radio frequency (RF) signals indicating the state of the LP-WUR. With respect to the IEEE 802.1 1 radio state, in some aspects, an AP may know the state of a STA based on existing signaling and power save protocols. In some aspects, signaling for the purpose of identifying the state of an IEEE 802.1 I device can be separated from the LP-WUR radio. For example, signaling for the purpose of indicating a LP-WUR radio state may not need to override the existing signaling that identifies the state of an IEEE 802.1 1 radio. Further, in some aspects, existing power save protocols may not need to be changed to indicate a LP-WUR radio state.

[0052] In some aspects, the state of a LP-WUR can be isolated from the state of another radio (e.g., an IEEE 802.1 1 radio). For example, a LP-WUR radio may wake-up more than one IEEE 802.11 radio, such as one or more radios operating in different frequency bands (e.g., 2.4GHz radio, 5 GHz radio). In some aspects, IEEE 802.11 radio additional power management modes may not be needed, allowing all current power management and power save protocols with respect to the IEEE 802.1 1 radio to remain unchanged. In some aspects, states for an IEEE 802.11 radio may not need to be redefined and additional states may not need to be added.

[0053] In some aspects, if the wake-up packet received by a wireless device or a STA (e.g., LP-WUR in the STA) from a peer device or an AP is not integrity protected with replay attack prevention, it is possible for malicious device to send false wake-up packets to the STA. In some aspects, this can result in a Denial of Service (DoS) attack where the malicious device can drain the battery of the STA (e.g., battery of a sensor or actuator within the STA). Therefore, it is important for the wake-up packet to be integrity protected with replay attack prevention so that the wake-up packet can be authenticated by a receiving node (e.g., STA).

[0054] In some aspects, a STA may enter a low-power mode (e.g.,

WUR mode) after negotiating with another device (e.g., an AP) that is configured to transmit a wake-up packet. In some aspects, the STA may utilize a field within a wake-up packet (e.g., a WUR authentication field) received from the AP to authenticate that the wake-up packet is from the intended and authorized sender (e.g., AP), In some aspects, prior to receiving a wake-up packet including a WIJR authentication field, the STA and the AP may associate and authenticate with one another through a typical association and

authentication procedure using 802.11 security.

[0055] In some aspects, the STA may compute a message authentication code (e.g., WUR authentication output value), using a WUR authentication function, with an input (e.g., WUR authentication input) of a password or an integrity key with the nonce for freshness (e.g., to mitigate replay attack). In some aspects, the WUR authentication input may be one-time use to prevent a malicious device from sending a false wake-up packet including the WUR authentication input that it may obtain from listening to communications between the STA and the AP,

[0056] In some aspects, a one-time password may be generated and shared between the STA and the AP over a secure communication (e.g., established by 802.11 security). In some aspects, the STA and the AP may agree upon the one-time password during a WUR negotiation, as further described below. In some aspects, upon receipt of a wake-up packet, the STA may compute a message authentication code (e.g., WUR authentication output value) using the agreed upon one-time password.

[0057] In some aspects, the STA and the AP may agree on a WUR authentication function (e.g., key derivation function) to generate a wake-up integrity key (e.g., derived from an 802, 1 key hierarchy). In some aspects, a nonce is generated and shared between the STA and the AP over a secure communication (e.g., established by 802. 1 1 security). Upon receipt of a wake- up packet, in some aspects, the STA may compute a message authentication code (e.g., WUR authentication output value) using the integrity key and the nonce.

[0058] In some aspects, the STA may generate a WUR

authentication input (e.g., a password or nonce) and a WUR authentication function. In other aspects, the AP may generate the WUR authentication input and WUR authentication function. In some aspects, the STA and the AP may agree upon the WUR authentication input and the WUR authentication function during the WUR negotiation, wherein the STA and the AP may transmit and receive request and response frames. In some aspects, the WUR authentication input and the WUR authentication function may be included within the receive and request frames.

[0059] In some aspects, when a computed message authentication code is successfully verified by the STA (e.g., the WUR authentication output matches an authentication value included in a WUR authentication field of a wake-up packet), processing circuitry of the STA (e.g. , a LP WUR of the STA may wake up a main radio (e.g., 802.1 1 radio) of the STA to connect to a network. In some aspect s, after successful waking of the main radio, the WUR authentication input (e.g., password or nonce) may be refreshed for a new wake- up packet to follow. In such aspects, because the one-time WUR authentication input (e.g., password or nonce) of a respective wake-up packet expires after each successful device wake-up, a replayed wake-up packet from a malicious device including the same one-time WUR authentication input may cause the STA to discard the replayed wake-up packet, thus avoiding a DoS attack,

[0060] In some aspects, a WUR authentication input (e.g., password or nonce) can be changed automatically when a device (e.g., STA) informs another device (e.g., AP) that a main radio (e.g., 802, 1 1 radio) will be turned off and a WUR receiver (e.g., LP -WUR) will be on. In such aspects, the WUR authentication input (e.g., password or nonce) may not be carried in a separate frame. In some aspects, the WUR authentication input (e.g., password or nonce) may be updated by an agreed function based on a previous value and a function and agreed by the device (e.g., ST A) and another device (e.g., AP) through a WUR request/response negotiation.

[0061] In some aspects, a WUR authentication input (e.g., password or nonce) may be changed periodically based on a pattern agreed through a WUR request/response negotiation. In such aspects, the WUR authentication input (e.g., password or nonce) may be updated by an agreed function based on a previous value and a function and agreed by the device (e.g., STA) and another device (e.g., AP) through a WUR request/response negotiation. In some aspects, the device (e.g., STA) and another device (e.g., AP) may agree through a WUR request/response negotiation on an updating period.

[0062] FIG. 5 illustrates a wireless network (e.g., WLAN 500) in accordance with some aspects. The WLAN may comprise a basis service set (BSS) 500 that may include one or more master stations 502, which may be APs, one or more high efficiency (HE) wireless stations (HE stations) (e.g., IEEE

802.1 lax) HE stations 504, a plurality of legacy (e.g., IEEE 802.1 l.n/ac) devices 506, a plurality of loT devices 508 (e.g., IEEE 802.1 lax), and one or more sensor hubs 510.

[0063] The master station 502 may be an AP using the IEEE 802.11 to transmit and receive. The master station 502 may be a base station. The master station 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 (OFDM A), time division multiple access (TDM A), and/or code division multiple access (CDMA). The IEEE 802.11 protocol may include a multiple access technique. For example, the IEEE 802.11 protocol may include space- division multiple access (SDMA) and/or multiple-user multiple-input multiple- output (MU-MTMO). The master station 502 may be a virtual master station 502 shares hardware resources with another wireless device such as another master station 502.

[0064] 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, or another legacy wireless communication standard. The legacy devices 506 may be STAs or IEEE STAs. The HE stations 504 may be wireless transmit and receive devices such as cellular telephone, smart telephone, handheld wireless device, wireless glasses, wireless watch, wireless personal device, tablet, a portable wireless device, or another device that may be transmitting and receiving using the IEEE 802.11 protocol such as IEEE 802.1 lax or another wireless protocol. In some aspects, the HE stations 504 may be termed high efficiency wireless local-area network (HEW) stations.

[0065] The master station 502 may communicate with legacy devices 506 in accordance with legacy IEEE 802.11 communication techniques. In example aspects, the master station 502 may also be configured to

communicate with HE stations 504 in accordance with legacy IEEE 802.11 comm u nication techni ques .

[0066] The IoT devices 508 may operate in accordance with IEEE 802. J 1 ax or another standard of 802.11. The IoT devices 508 may be, in some aspects, narrow band devices that operate on a smaller sub-channel than the HE stations 504. For example, the IoT devices 508 may operate on 2.03 MHz or 4.06 MHz sub-channels. In some aspects, the IoT devices 508 are not able to transmit on a full 20 MHz sub-channei to the master station 502 with sufficient power for the master station 502 to receive the transmission. In some aspects, the IoT devices 508 may not be able to receive on a 20 MHz sub-channei and may use a small sub-channel such as 2.03 MHz or 4.06 MHz sub-channel. In some aspects, the IoT devices 508 may operate on a sub-channel with exactly 26 or 52 data sub-carriers. The IoT devices 508, in some aspects, may be short- range, low-power devices.

[0067] The IoT devices 508 may be battery constrained. The IoT devices 508 may be sensors designed to measure one or more specific parameters of interest such as temperature sensor, pressure sensor, humidity sensor, light sensor, etc. The IoT devices 508 may be location-specific sensors. Some IoT devices 508 may be connected to a sensor hub 510. The IoT devices 508 may upload measured data from sensors to the sensor hub 510. The sensor hubs 510 may upload the data to an access gateway 512 that connects several sensor hubs 510 and can connect to a cloud sever or the Internet (not illustrated). The master station 502 may act as the access gateway 512 in accordance with some aspects. The master station 502 may act as the sensor hub 510 in accordance with some aspects. The loT device 508 may have identifiers that identify a type of data that is measured from the sensors. In some aspects, the loT device 508 may be able to determine a location of the loT device 508 based on received satellite signals or received terrestrial wireless signals.

[0068] In some aspects, at least some of the loT devices 508 need to consume very low average power in order to perform a packet exchange with the sensor hub 510 and/or access gateway 512. The loT devices 508 may be densely deployed.

[0069] The IoT devices 508 may enter a power save mode and may exit the power save at intervals to gather data from sensors and/or to upload the data to the sensor hub 510 or access gateway 512.

[0070] In some aspects, the master station 502 HE stations 504, legacy stations 506, IoT devices 508, access gateways 512, Bluetooth^1M devices, and/or sensor hubs 510 enter a power save mode and exit the power save mode periodically or at a pre-scheduled times to see if there is a packet for them to be received. In some aspects, the master station 502 HE stations 504, legacy stations 506, IoT devices 508, access gateways 512, Bluetooth^™ devices, and/or sensor hubs 510 may remain in a power save mode until receiving a wake-up packet.

[0071] In some aspects, a HE frame may be configurable to have the same bandwidth as a subchannel. The bandwidth of a sub-channel may be 20MHz, 40MHz, or 80MHz, 160MHz, 320MHz contiguous bandwidths or an 80+80MHz (160MHz) non-contiguous bandwidth. In some aspects, the bandwidth of a subchannel may be 2.03125 MHz, 4.0625 MHz, 8.28125 MHz, a combination thereof or another bandwidth that is less or equal to the available bandwidth may also be used. The sub-channel may be based on a number of data sub-carriers or data tones, e.g. 26 or 52 with additional subcarriers that may be used for other reasons such as DC nulls, guard intervals, beacons, or another use other than data tones. In some aspects the bandwidth of the sub-channels may be based on a number of active subcarriers.

[0072] In some aspects, the bandwidth of a sub-channel may be equivalent to one of OFDMA sub-channels defined in IEEE 802, 1 lax. In some aspects, the OFDMA sub-channels of IEEE 802.1 lax that are less than 20MHz are equivalent to 26-tone, 52-tone and 106-tone allocations. The bandwidth of these OFDMA allocations may be 20MHz divided by 256 of a Fast Fourier Transform (FFT)-size times 26 or 52 or 106, for bandwidths of 2.03125 MHz, 4.0625 MHz, or 8.28125 MHz, respectively. In some aspects, the sub-channels may be a combination thereof or another bandwidth that is less or equal to the available bandwidth may also be used.

[0073] A HE packet may be configured for transmitting a number of spatial streams, which may be in accordance with MU-MIMO. In other aspects, the master station 502, HE stations 504, sensor hubs 5 0, access gateway 512, and/or legacy devices 506 may also implement different technologies such as code division multiple access (CDMA) 2000, CDMA 2000 I X, 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 (WiM AX)), BlueTooth®, or other technologies.

[0074] Some aspects relate to HE communications. In accordance with some IEEE 802, 1 lax aspects, a master station 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 aspects, the HE control period may be termed a transmission opportunity (TXOP). The master station 502 may transmit a HE trigger frame, which may be a trigger packet or HE control and schedule transmission, at the beginning of the HEW control period. The master station 502 may transmit a time duration of the TXOP and sub-channel information. During the HE control period, HEW stations 504 may communicate with the master station 502 in accordance with a non-contention based multiple access technique such as

OFDMA or MU-MIMO.

[0075] This is unlike conventional wireless local-area network

(WLAN) communications in which devices communicate in accordance with contention-based communication technique, rather than a multiple access technique. During the HE control period, legacy stations retrain from

communicating.

[0076] In some aspects, the multiple-access technique used during the HE control period may be a scheduled OFDMA technique, although this is not a requirement. In some aspects, the multiple access technique may be a time-division multiple access (TDMA) technique or a frequency division multiple access (FDMA) technique. In some aspects, the multiple access technique may be a space-division multiple access (SOMA) technique.

[0077] The master station 502 may also communicate with legacy stations 506, sensor hubs 510, access gateway 512, and/or HE stations 504 in accordance with legacy IEEE 802, 1 1 communication techniques. In example aspects, a master station 502, access gateway 512, HE station 504, legacy station 506, IoT devices 508, and/or sensor hub 510 may be configured to perform the methods and functions herein described in conjunction with FIGS. 1-4 and 6-10.

[0078] 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. Examples, as described herein, may include, or may operate by, logic or a number of components, or mechanisms in the machine 600. Circuitry (e.g., processing circuitry) is a collection of circuits implemented in tangible entities of the machine 600 that include hardware (e.g., simple circuits, gates, logic, etc.). Circuitry membership may be flexible over time. Circuitries include members that may, alone or in combination, perform specified operations when operating. In an example, hardware of the circuitry may be immutably designed to carry out a specific operation (e.g., hardwired). In an example, the hardware of the circuitry may include variably connected physical components (e.g., execution units, transistors, simple circuits, etc) including a machine readable medium physically modified (e.g., magnetically, electrically, moveable placement of invariant massed particles, etc.) to encode instructions of the specific operation. In connecting the physical components, the underlying electrical properties of a hardware constituent are changed, for example, from an insulator to a conductor or vice versa. The instructions enable embedded hardware (e.g., the execution units or a loading mechanism) to create members of the circuitry in hardware via the variable connections to cany out portions of the specific operation when in operation. Accordingly, in an example, the machine readable medium elements are part of the circuitry or are communicatively coupled to the other components of the circuitry when the device is operating. In an example, any of the physical components may be used in more than one member of more than one circuitry. For example, under operation, execution units may be used in a first circuit of a first circuitry at one point in time and reused by a second circuit in the first circuitry, or by a third circuit in a second circuitry at a different time. Additional examples of these components with respect to the machine 600 follow.

[0079] 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 deploy ment, 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 personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a mobile telephone, 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.

[0080] The 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, a static memory (e.g., memory or storage for firmware, microcode, a basic-input-output (BIOS), unified extensible firmware interface (UEFI), etc.) 606, and mass storage 608 (e.g., hard drive, tape drive, flash storage, or other block devices) some or ail of which may communicate with each other via an interlink (e.g., bus) 630. The machine 600 may further include a display unit 610, an alphanumeric input device 612 (e.g., a keyboard), and a user interface (UI) navigation device 614 (e.g., a mouse). In an example, the display unit 610, input device 612 and UI navigation device 614 may be a touch screen display. The machine 600 may additionally include a storage device (e.g., drive unit) 608, a signal generation device 618 (e.g., a speaker), a network interface device 620, and one or more sensors 616, 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.).

[0081] Registers of the processor 602, the main memory 604, the static memory 606, or the mass storage 608 may be, or 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 any of registers of the processor 602, the main memory 604, the static memory 606, or the mass storage 608 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 mass storage 608 may constitute the machine readable media 622. 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] 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, optical media, magnetic media, and signals (e.g., radio frequency signals, other photon based signals, sound signals, etc.). In an example, a non-transitory machine readable medium comprises a machine readable medium with a plurality of particles having invariant (e.g., rest) mass, and thus are compositions of matter. Accordingly, non-transitory machine- readable media are machine readable media that do not include transitory propagating signals. Specific examples of non-transitory 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, and CD-ROM: and DVD-ROM: disks.

[0083] The instructions 624 may be further 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 (HDP), 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, peer-to-peer (P2P) networks, among others. 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 a plurality of antennas to wirelessly communicate using at least one of single-input multiple- output (SIMO), multiple-input multiple-output (MDvlO), or multiple-input single-output (MISO) 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. A transmission medium is a machine readable medium.

[0084] FIG. 7 illustrates a ST A in accordance with some aspects and an AP in accordance with some aspects. It should be noted that in some aspects, an STA or other mobile device may include some or all of the components shown in either FIG. 6 or FIG. 7 (as in 700) or both. It should also be noted that in some aspects, an AP or other base station may include some or all of the components shown in either FIG. 6 or FIG. 7 (as in 750) or both. The AP 750 may be suitable for use as an AP 102 as depicted in FIG. 1, in some aspects.

[0085] The STA 700 may include physical layer circuitry 702 and a transceiver 705, one or both of which may enable transmission and reception of signals to and from components such as the AP 102 (FIG. I), other STAs or other devices using one or more antennas 701. As an example, the physical layer circuitry 702 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 705 may perform various transmission and reception functions such as conversion of signals between a baseband range and a Radio Frequency (RF) range. Accordingly, the physical layer circuitry 702 and the transceiver 705 may be separate components or may be part of a combined component. 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 physical layer circuitry 702, the transceiver 705, and other components or layers. The STA 700 may also include medium access control layer (MAC) circuitry 704 for controlling access to the wireless medium. The STA 700 may also include processing circuitry 706 and memory 708 arranged to perform the operations described herein.

[0086] The AP 750 may include physical layer circuitry 752 and a transceiver 755, one or both of which may enable transmission and reception of signals to and from components such as the ST A 103 (FIG. 1), other APs or other devices using one or more antennas 751. As an example, the physical layer circuitry 752 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 755 may perform various transmission and reception functions such as conversion of signals between a baseband range and a Radio Frequency (RF) range. Accordingly, the physical layer circuitry 752 and the transceiver 755 may be separate components or may be part of a combined component. 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 physical layer circuitry 752, the transceiver 755, and other components or layers. The AP 750 may also include medium access control layer (MAC) circuitry 754 for controlling access to the wireless medium. The AP 750 may also include processing circuitry 756 and memory 758 arranged to perform the operations described herein.

[0087] The antennas 701, 751 , 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 (MEMO) aspects, the antennas 701 and 751 may be effectively separated to take advantage of spatial diversity and the different channel characteristics that may result.

[0088] In some aspects, the STA 700 may be configured as an HEW device 104 (FIG. 1), and may communicate using OFDM and/or OFDMA communication signals over a multicarrier communication channel. In some aspects, the AP 750 may be configured to communicate using OFDM and/or

OFDMA communication signals over a multicarrier communication channel. In some aspects, the HEW device 104 may be configured to communicate using OFDM communication signals over a multicarrier communication channel. Accordingly, in some cases, the ST A 700, AP 750 and/or HEW device 104 may be configured to receive signals in accordance with specific communication standards, such as the Institute of Electrical and Electronics Engineers (IEEE) standards including IEEE 802.11-2012, 802.1 ln-2009 and/or 802.1 lac-2013 standards and/or proposed specifications for WLANs including proposed HEW standards, although the scope of the aspects is not limited in this respect as they may also be suitable to transmit and/or receive communications in accordance with other techniques and standards. In some other aspects, the AP 750, HEW device 104 and/or the STA 700 configured as an HEW⁷ device 104 may be configured to receive signals that were 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 aspects is not limited in this respect. Aspects disclosed herein provide two preamble formats for High Efficiency (HE) Wireless LAN standards specification that is under development in the IEEE Task Group 1 l ax (TGax).

[0089] In some aspects, the STA 700 and/or AP 750 may be a mobile device and may be a portable wireless communication device, such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capability, a web tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a wearable device such as a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), or other device that may receive and/or transmit information wirelessly. In some aspects, the STA 700 and/or AP 750 may be configured to operate in accordance with 802.1 1 standards, although the scope of the aspects is not limited in this respect. Mobile devices or other devices in some aspects may be configured to operate according to other protocols or standards, including other IEEE standards, Third

Generation Partnership Project (3GPP) standards or other standards. In some aspects, the STA 700 and/or AP 750 may include one or more of a keyboard, a display, a non-volatile memory port, multiple antennas, a graphics processor, an application processor, speakers, and other mobile device elements. The display may be an LCD screen including a touch screen.

[0090] Although the STA 700 and the AP 750 are each 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 aspects, the functional elements may refer to one or more processes operating on one or more processing elements.

[0091] Aspects may be implemented in one or a combination of hardware, firmware and software. Aspects may also be implemented as instructions stored on a computer-readable storage device, which may be read and executed by at least one processor to perform the operations described herein. A computer-readable storage device may include any non-transitory mechanism for storing information in a form readable by a machine (e.g., a computer). For example, a computer-readable storage device may include readonly memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices, and other storage devices and media. Some aspects may include one or more processors and may be configured with instructions stored on a computer-readable storage device.

[0092] It should be noted that in some aspects, an apparatus used by the STA 700 may include various components of the STA 700 as shown in FIG. 7 and/or the example machine 600 as shown in FIG. 6, Accordingly, techniques and operations described herein that refer to the STA 700 (or 103) may be applicable to an apparatus for an STA, in some aspects. It should also be noted that in some aspects, an apparatus used by the AP 750 may include various components of the AP 750 as shown in FIG. 7 and/or the example machine 600 as shown in FIG. 6. Accordingly, techniques and operations described herein that refer to the AP 750 (or 102) may be applicable to an apparatus for an AP, in some aspects. In addition, an apparatus for a mobile device and/or base station may include one or more components shown in FIGs. 6-7, in some aspects. Accordingly, techniques and operations described herein that refer to a mobile device and/or base station may be applicable to an apparatus for a mobile device and/or base station, in some aspects.

[0093] As described herein, some aspects define states for one or more LP-WUR. For example, two states can be defined for a LP-WUR, including a first state wherein the device is configured to receive wake-up packet, and a second state wherein the device is configured to not receive a wake-up packet. In such an example, the first state can be an Awake state, and the second state can be a Doze state. In alternative aspects, the terms used for these states can vary, for example, the second state may be a Sleep state. In some aspects, a wake-up radio (WU ) mode can include one or more of these states.

[0094] As described above, the state of the LP-WUR can, in some aspects, be independent of the states for an IEEE 802.1 radio. In some aspects, an IEEE 802.1 1 device can be defined to have LP-WUR capability, for example, with four possible two dimensional states as illustrated in Table 1 below.

Table 1

[0095] Referring to Case 1, an 802.1 1 radio state is set to Awake and a LP-WUR state is set to Awake. In some aspects, in Case 1, the 802. 1 radio is able to receive signals (e.g., the 802.1 1 radio in the STA can receive J signals from an AP) and the LP-WUR is also able to receive signals (e.g., the LP-WUR 425 in the STA can receive signals from an AP), In some aspects, an STA is configured to receive a wake-up packet from an associated AP and send packets to the AP.

[0096] In Case 2, an 802.11 radio state is set to Awake and a LP-

WUR state is set to Doze. In some aspects, in Case 2, the 802.1 1 radio is able to receive signals (e.g., the 802.11 radio in the STA is able to receive signals from an AP) and the LP-WUR is disabled from receiving signals (e.g., the LP-WUR 425 in the STA does not receive signals from an AP). In some aspects, a STA is configured to receive a wake-up packet from the AP for the purpose of turning on the 802.11 radio and turning off the LP-WUR,

[0097] In Case 3, an 802.11 radio state is set to Doze and a LP-

WUR state is set to Awake. In some aspects, in Case 3, the 802.1 1 radio is disabled from receiving signals (e.g., the 802.1 1 radio in the STA is not able to receive signals from an AP) and the LP-WUR is able to receive signals (e.g., the LP-WUR 425 in the STA can receive signals from an AP), In some aspects, a STA is configured to turn off the 802.11 radio and utilize the LP-WUR to save power.

[0098] In Case 4, an 802.1 1 radio state is set to Doze and a LP- WUR radio state is set to Doze. In some aspects, in Case 4, the 802, 11 radio is disabled from receiving signals (e.g., the 802.11 radio in the STA is not able to receive signals from an AP) and the LP-WUR is disabled from receiving signals (e.g., the LP-WUR 425 in the STA does not receive signals from an AP). In some aspects, a STA is configured to save power (e.g., extreme power save) while still being capable of waking the LP-WUR radio periodically.

[0099] In some aspects, a wireless device (e.g., a STA having a LP-

WUR and a WL AN radio) may transmit a request signal to an AP in order to enable a power save protocol between the AP and the wireless device. In some aspects, the request signal may include one or more parameters defining the power save protocol and the STA may receive a response signal, including one or more of the parameters, from the AP acknowledging the request signal. The one or more parameters of the request signal may include WUR parameters with respect to a wake-up radio (WUR) mode for the STA (e.g., a LP -WUR of a STA), for example, an indication of a duration of time that the STA (e.g., LP- WUR of a STA) is in a WUR mode. In some aspects, with respect to a WUR mode, a LP-WUR of a STA is configured to receive wake-up packets from the AP and a WLAN radio of the STA is configured to refrain from receiving RF signals.

[00100] In some aspects, during the WUR mode, a LP-WUR of a

STA may be configured to be in an Awake state, wherein during the Awake state the LP-WUR is configured to receive wake-up packets, and a WLAN radio of the STA is turned off. In some aspects, in response to the LP-WUR of the STA receiving a wake-up packet while in WUR mode (e.g., receiving a wake-up packet from an AP), the WLAN radio can change from a Doze state to an Awake state. In the Doze state, for example, the WLAN radio may be configured to refrain from receiving RF signals from peer devices. In the Awake state, for example, the WL AN radio can receive RF signals from peer devices.

[00101] Further, in response to the LP-WUR of the STA receiving a wake-up packet while in WUR mode, in some aspects, the LP-WUR radio can change from an Awake state to a Doze state. In the Awake state, for example, the LP-WUR can receive wake-up packets and during the Doze state the LP- WUR can refrain from receiving wake-up packets. In some aspects, after the WLAN radio of the STA changes to an Awake state, the WLAN can receive data packets from an AP. In some aspects, the STA may be configured to periodically enter the WUR mode. In such aspects, one or more parameters of a request signal (e.g., a request signal sent to an AP from the STA) can include a service identifier (ID), protocol support information, and an indication of a specific schedule that the STA is in the WUR mode. In some aspects, the WLAN radio may be configured to remain in a Doze state, during a duration of time that the STA is in the WUR mode, until the LP-WUR of the STA receives a wake-up packet.

[00102] FIG. 8 illustrates an example system 800 in which a LP-

WUR (e.g., LP-WUR 825) is operated. As shown, the system 800 includes a transmitter 805 and a receiver 810. The transmitter 805 may be a WLAN station (e.g., Wi-Fi router, AP) and the receiver 810 may be a computing device capable of connecting to the WLAN station, such as a mobile phone, a tablet computer, a laptop computer, a desktop computer, STA, and the like. The transmitter 805 includes an WLAN (802.11 +) radio 815. The receiver 810 includes a WLAN (802.11) radio 820 (e.g., Wi-Fi radio) and a LP-WUR 825. The WLAN radio 815 of the transmitter 805 transmits one or more wake-up packets 830. One of the wake-up packets 830 is received at the LP-WUR 825 of the receiver 820. Upon receiving the wake-up packet 830, the LP-WUR 825 sends a wake-up signal 840, which causes the WLAN radio 820 of the receiver 810 to turn on. The WLAN radio 815 of the transmitter 805 transmits data packet(s) 835 to the WLAN radio 820 of the receiver 810, and the WLAN radio 820 of the receiver 810 receives the data packet(s) 835.

[00103J Some aspects include a WUR negotiation, for example the WUR negotiation as described in related disclosure, U.S. Patent Application No. 15/392,398. In some aspects, a STA may be in a low-power state such as a WUR mode. During the WUR mode, a main radio of the STA (e.g., 802.11 radio 820) may be off and may refrain from receiving RF signals from the AP (e.g., transmitter 805), while the LP-WUR (e.g., LP-WUR 825) of the STA can be on and configured to receive wake-up packets 830 from the AP 805.

[00104] FIG. 9 is a flow diagram illustrating an example method of wake- up packet authentication, in accordance with some aspects. In some aspects, a STA can encode a request signal (e.g., WUR Request 902) in a frame (e.g., an action frame) for transmission to an AP. In some aspects, an action frame may be implemented with a standard power-save protocol and may define parameters associated with a power-save protocol for a LP-WUR. In some aspects, an action frame is used for request and/or response signaling with respect to a wireless device (e.g., STA) having a wake-up radio (e.g., LP-WUR 825). A STA may transmit a request signal (e.g., WUR Request 902) to an AP in order to enable a power save protocol between the AP and the STA. In some aspects, a request or response signal, such an action frame, may include one or more parameters defining the power save protocol and the STA may receive a response signal from the AP acknowledging the request signal. 00105] In some aspects, in response to a request signal from a STA, an AP may encode a response signal (e.g., WUR Response 904) for transmission to a STA, to acknowledge the request signal. In some aspects, a frame (e.g., an action frame) may include one or more parameters of a request or response signal, for example, indications of time durations that the STA is in a wake-up radio (WUR) mode, an indication of a channel for transmitting a wake-up packet, and an indication of a security protocol. Further, in some aspects, the STA may transmit to the AP a WUR signal (e.g., WUR signaling 906) indicating that the STA is entering a WUR mode (e.g., inform the AP that the STA is entering the WUR state with a nonce).

[00106] In some aspects, a frame (e.g., an action frame) may include one or more parameters for WUR authentication (e.g., WUR authentication of a wake-up packet transmitted from the AP to the STA, 908), such as a WUR authentication input. In some aspects, a WUR authentication input may be one or more parameters agreed upon by both the AP and the STA during the WUR negotiation (e.g., during the WUR request/response exchange 902 and 904). In some aspects, a WUR authentication parameter may include any one of an indication of a channel for transmitting a wake-up packet, an indication of a transmitting device identification, an indication of a receiving device

identification, and an indication of a security protocol. In some aspects, the transmitting device corresponding to the transmitting device identification may^¬ be a STA or an AP. In further aspects, the receiving device corresponding to the receiving device identification may be a STA or an AP.

[00107] In some aspects, the WUR request and response signaling may be encrypted to prevent a malicious device from listening and obtaining the one or more parameters for WUR authentication, as described in more detail below.

ooio; 8 A WUR authentication input, for example, may be an authentication password, or a nonce. Further, in some aspects, a parameter for WUR authentication, included in a frame (e.g., an action frame) can include a WUR authentication function hash function or an integrity key agreed upon by both the AP and the STA during the WUR negotiation. In some aspects, any one of the parameters for WUR authentication (e.g., WUR authentication inputs and the WUR authentication functions) may be included in a WUR Request 902 or a WUR Response 904. In some aspects, the STA can decode a parameter for WUR authentication from a frame received from the AP (e.g., WUR Response 904) or may generate a parameter for WUR authentication based on information included in the received frame.

[00109] Further, the STA can use these parameters, in some aspects, for calculating a WUR authentication output value for authentication of a wake- up packet (e.g., received from the AP). In some aspects, a STA may receive a wake-up packet (e.g., wake-up packet 908) from an AP during a WUR mode

(e.g., after the STA informs the AP that the STA is entering the WUR mode). In some aspects, during the WUR mode, a WLA radio of the STA is configured to refrain from receiving RF signals from the AP and a LP-WUR of the STA is configured to receive wake-up packets from the AP. In some aspects, the STA (e.g., LP-WUR of the STA) can decode from the wake-up packet 908, a WUR authentication field, for example, the WUR authentication field of FIG. 10.

[00110] FIG. 10 illustrates an example wake-up frame format in accordance with some aspects. The wake-up packet 908 with respect to FIG. 9, in some aspects, comprises the wake-up packet format 1000, including a WUR authentication field 604, although aspects are not so limited. In some aspects, the STA can decode the WUR authentication field 1004 from the received date- up packet 908 to initiate a WUR authentication. In some aspects, because of a low data rate that may be associated with certain power saving protocols with respect to the LP-WUR of the STA, the length of the WUR authentication field can be smaller than 8 bytes.

[00111] The WUR authentication field 1004, in some aspects, includes, an authentication value. In some aspects, the AP encodes the authentication value within the WUR authentication field 1004 for the STA to authenticate the AP, authenticate the wake-up packet 908, or for other authentication purposes. The authentication value may be included, in some aspects, within other fields of the wake-up 908, for example within other WUR parameters 002. In some aspects, the STA, after decoding the authentication value from the WUR authentication field 1004, can utilize the authentication value to compare against a calculated WUR authentication output value to authenticate the wake-up packet 908, to identify the AP, or for other

authentication purposes. In some aspects, memory within the STA can be configured to store the authentication value, the WUR authentication input, and the WUR authentication function.

[00112] In some aspects, the STA can calculate a WUR

authentication output value based on a WUR authentication input and a WUR authentication function, wherein the STA obtained the WUR authentication input and the WUR authentication function during a WUR negotiation with the AP, as described above. Additionally, the STA may include other WUR authentication parameters in calculating a WUR authentication output value, wherein the STA may obtain the WUR authentication parameters during the WUR negotiation, or may obtain the WUR authentication parameters from a received wake-up packet 908 (e.g., WUR parameters 1002). In some aspects, the STA may calculate a WUR authentication output value and compare the WUR authentication output value to the authentication value (e.g., included in the WUR authentication field 1004) to determine if there is a match between the WUR authentication output value and the authentication value. In some aspects, if the STA determines a match between the calculated WUR authentication output value and the authentication value, the STA can authenticate a received wake-up packet (e.g., wake-up packet 908).

[00113] Referring back to FIG. 9, in some aspects, when the STA authenticates the received wake-up packet 908, the STA may assume that the wake-up packet 908 is not from a malicious device, and the STA may join a network (e.g., a wireless local area networks (WLAN), Wi-Fi network, and any network operating in accordance with the IEEE 802.1 1 family of standards).

[00114] Alternatively, the STA may determine that the calculated

WUR authentication output value does not match the authentication value (e.g., included in the WUR authentication field 1004), in which case the STA may determine that the received weight-up packet 908 is not from the AP. For example, a malicious device may listen to signaling from the AP to the STA, including the wake-up packet 908, and may transmit its own signaling to the STA (e.g., including information similar to wake-up packet 908) that is a false wake-up packet 916. For example, the malicious device may transmit one or more false wake-up packets (e.g., 916), after listening to the transmission of the wake-up packet 908 from the AP to the STA, to perform a DoS attack on the STA. In such instances, the STA may receive the false wake-up packet 916 from the malicious device and may determine that the calculated WUR authentication output value does not match the authentication value, in which case the STA may decide to discard the wake-up packet 916.

[00115] In some aspects, if the STA authenticates the received wake- up packet 908, the STA can use existing signaling protocols (e.g., power save protocols), such as such as Wireless Network Management (WNM),

Unscheduled Automatic Power Save Delivery (U-APSD), or Power Save Poll (PS-POLL) or Power Save Mode (PSM), to indicate in power save signaling 910, that the STA has turned on its main radio (e.g., 802.1 1 radio 420) and that an AP can send data packets (e.g., data packet 912) to the STA. In some aspects, therefore, existing signaling protocols (e.g., power save protocols) between the STA and AP may be utilized to indicate that the STA has entered a Doze state and that an AP cannot send data packets to the STA, such as Wireless Network Management (WNM), Unscheduled Automatic Power Save Delivery (U-APSD), or Power Save Poll (PS-POLL) or Power Save Mode (PSM).

[00116] In some aspects, the WUR authentication input is a one-time value. For example, when the STA determines a match between the calculated WUR authentication output value and the authentication value, the WUR authentication input, the WU R authentication function, or one or more other parameters for WUR authentication may expire. In such aspects, prior to the STA transmitting WUR signaling 914 to the AP, indicating to the AP that the STA will enter a WUR mode again, and prior to receiving an additional and/or a second wake-up packet (not shown), the STA and the AP may enter WUR negotiation again to negotiate an additional and/or a second WUR authentication input (e.g., a second WUR authentication function). [00117] Examples

[00118] Although an aspect has been described with reference to specific example aspects, it will be evident that various modifications and changes may be made to these aspects without departing from the broader spirit and scope of the present disclosure. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. The accompanying drawings that form a part hereof show, by way of illustration, and not of limitation, specific aspects in which the subject matter may be practiced. The aspects illustrated are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other aspects may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. This Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various aspects is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.

[00119] Such aspects of the inventive subject matter may be referred to herein, individually and/or collectively, by the term "aspect" merely for convenience and without intending to voluntarily limit the scope of this application to any single aspect or inventive concept if more than one is in fact disclosed. Thus, although specific aspects have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific aspects shown. This disclosure is intended to cover any and all adaptations or variations of various aspects. Combinations of the above aspects, and other aspects not specifically described herein, will be apparent to those of skill in the art upon reviewing the above description,

[00120] In this document, the terms "a" or "an" are used, as is common in patent documents, to include one or more than one, independent of any other instances or usages of "at least one" or "one or more." In this document, the term "or" is used to refer to a nonexclusive or, such that "A or B" includes "A but not B," "B but not A," and "A and B," unless otherwise indicated. In this document, the terms "including" and "in which" are used as the plain-English equivalents of the respective terms "comprising" and "wherein. " Also, in the following claims, the terms "including" and "comprising" are open-ended, that is, a system, LIE, article, composition, formulation, or process that includes elements in addition to those listed after such a term in a claim are still deemed to fall within the scope of that claim. Moreover, in the following claims, the terms "first," "second," and "third," etc. are used merely as labels, and are not intended to impose numerical requirements on their objects.

[00121] The Abstract of the Disclosure is provided to allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in a single aspect for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed aspects require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed aspect. Thus the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate aspect.

[00122] The following describes various examples of methods, machine- readable media, and systems (e.g., machines, devices, or other apparatus) discussed herein.

[00123] Example 1 is an apparatus of a station (STA), the apparatus comprising: processing circuitry configured to: configure a low-power wake-up radio (LP-WU ) of the STA to receive a wake-up packet from an access point (AP) during a WUR mode, wherein during the WUR mode, a wireless local area network (WLAN) radio of the STA is configured to refrain from receiving radio frequency (RF) signals from the AP and the LP-WUR of the STA is configured to receive wake-up packets from the AP; decode the wake-up packet to determine a WUR authentication field including an authentication value;

calculate a WUR authentication output value based on a WUR authentication input and a WUR authentication function, wherein the apparatus obtains the WUR authentication input and the WUR authentication function during a WUR negotiation with the AP; compare the WUR authentication output value to the authentication value, and authenticate the wake-up packet based on the WUR authentication output value matching the authentication value; and memory configured to store at least one of the authentication value, the WUR

authentication input, and the WUR authentication function.

[00124] In Example 2, the subject matter of Example 1 includes, wherein the processing circuitry is further configured to discard the wake-up packet based on the calculated WUR authentication output value not matching the authentication value,

[00125] In Example 3, the subject matter of Examples 1-2 includes, wherein during the WUR negotiation, the processing circuitry is further configured to: encode, for transmission to the AP, a request frame to enable a power save protocol between the STA and the AP; and decode a response frame from the AP, the request frame including one or more WUR authentication parameters defining a WUR authentication protocol,

[00126] In Example 4, the subject matter of Example 3 includes, wherein the processing circuitry is configured to obtain the WUR authentication input and the WUR authentication function by decoding the WUR authentication input and the WUR authentication function from the response frame.

[00127] In Example 5, the subject matter of Example 4 includes, wherein the processing circuitry is further configured to generate the WUR authentication input and the WUR authentication function.

[00128] In Example 6, the subject matter of Examples 1-5 includes, wherein the WUR authentication input is one-time input value.

[00129] In Example 7, the subject matter of Examples 1 -6 includes, wherein the WUR authentication input includes one or more of an authentication password, a nonce, and an integrity key.

[00130] In Example 8, the subject matter of Examples 6-7 includes, wherein to initiate a second WUR authentication, the processing circuitry is configured to obtain a second WUR authentication input during a second WUR negotiation with the AP. [00131] In Example 9, the subject matter of Examples 3-8 includes, wherein during the WUR negotiation, the processing circuitry is further configured to obtain one or more WUR authentication parameters, the WUR authentication parameters including one or more of an indication of a channel for transmitting a wake-up packet, and an indication of a security protocol.

[00132] In Example 10, the subject matter of Examples 1-9 includes, wherein the wake-up packet includes one or more WUR authentication parameters, the WUR authentication parameters including one or more of an indication of a channel for transmitting a wake-up packet, and an indication of a security protocol.

[00133] Example 11 is a method of wake-up packet authentication comprising: receiving a wake-up packet from an access point (AP) during a wake-up radio (WUR) mode, wherein during the WUR mode, a wireless local area network (WLAN) radio of the STA is configured to refrain from receiving radio frequency (RF) signals from the AP and a low-power wake-up radio (LP- WUR) of the STA is configured to receive wake-up packets from the AP;

decoding the wake-up packet to determine a WUR authentication field including an authentication value, calculating a WUR authentication output value based on a WUR authentication input and a WUR authentication function, wherein the apparatus obtains the WUR authentication input and the WUR authentication function during a WUR negotiation with the AP; comparing the WUR

authentication output value to the authentication value; and authenticating the wake-up packet based on the WUR authentication output value matching the authentication value.

[00134] In Example 12, the subject matter of Example 1 1 includes, discarding the wake-up packet based on the calculated WUR. authentication output value not matching the authentication value.

[00135] In Example 13, the subject matter of Examples 1 1-12 includes, encoding, for transmission to the AP during the WUR negotiation, a request frame to enable a power save protocol between the STA and the AP; and decoding a response frame from the AP, the response frame including one or more WUR authentication parameters defining a WUR authentication protocol. [00136] In Example 14, the subject matter of Example 13 includes, obtaining the WUR authentication input and the WUR authentication function by decoding the WUR authentication input and the WUR authentication function from the response frame,

[00137] In Example 15, the subject matter of Example 14 includes, generating the WUR authentication input and the WUR authentication function.

[00138] In Example 16, the subject matter of Examples 11-15 includes, wherein the WUR authentication input is one-time input value.

[00139] In Example 17, the subject matter of Examples 1 1-16 includes, wherein the WUR authentication input includes one or more of an authentication password, a nonce, and an integrity key.

[00140] In Example 18, the subject matter of Examples 16-17 includes, obtaining a second WUR authentication input, during a second WUR negotiation with the AP to initiate a second U authentication for a second wake-up packet, wherein the second WUR authentication input includes one or more of an authentication password, a nonce, and an integrity key,

[00141] In Example 19, the subject matter of Examples 16-18 includes, wherein the second WUR authentication input is obtained based on a changing pattern agreed upon during the first WUR negotiation with the AP.

[00142] In Example 20, the subject matter of Examples 13-19 includes, obtaining, during the WUR negotiation, one or more WUR

authentication parameters, the WUR authentication parameters including one or more of an indication of a channel for transmitting a wake-up packet, an indication of a transmitting device identification, an indication of a receiving device identification, and an indication of a security protocol.

[00143] In Example 21, the subject matter of Examples 13-20 includes, wherein the wake-up packet includes one or more WUR authentication parameters, the WUR authentication parameters including one or more of an indication of a channel for transmitting a wake-up packet, an indication of a transmitting device identification, an indication of a receiving device

identification, and an indication of a security protocol. [00144] Example 22 is a computer-readable hardware storage device that stores instructions for execution by one or more processors of a station (STA), the instructions to configure the one or more processors to: configure a low-power wake-up radio (LP-WUR) of the STA to receive a wake-up packet from an access point (AP) during a WUR mode, wherein during the WUR mode, a wireless local area network (WLAN) radio of the ST A is configured to refrain from receiving radio frequency (RF) signals from the AP and the LP-WUR of the STA is configured to receive wake-up packets from the AP; decode the wake-up packet to determine a WUR authentication field including an authentication value; calculate a WUR authentication output value based on a WUR authentication input and a WUR authentication function, wherein the instructions are further to configure the one or more processors to obtain the WUR authentication input and the WUR authentication function during a WUR negotiation with the AP; compare the WUR authentication output value to the authentication value, and authenticate the wake-up packet based on the WUR. authentication output value matching the authentication value.

[00145] In Example 23, the subject matter of Example 22 includes, wherein the instructions are further to configure the one or more processors to discard the wake-up packet based on the calculated WUR authentication output value not matching the authentication value.

[00146] In Example 24, the subject matter of Examples 22-23 includes, wherein during the WUR negotiation, the instructions are further to configure the one or more processors to: encode, for transmission to the AP, a request frame to enable a power save protocol between the STA and the AP; and decode a response frame from the AP, the request frame including one or more WUR authentication parameters defining a WUR authentication protocol.

[00147] In Example 25, the subject matter of Example 24 includes, wherein the instructions are further to configure the one or more processors to obtain the WUR authentication input and the WUR authentication function by decoding the WUR authentication input and the WUR authentication function from the response frame. [00148] Example 26 is at least one machine-readable medium including instructions that, when executed by processing circuitry, cause the processing circuitry to perform operations to implement of any of Examples 1- ? 5

[00149] Example 27 is an apparatus comprising means to implement of any of Examples 1-25.

[00150] Example 28 is a system to implement of any of Examples 1 -

25.

[00151] Example 29 is a method to implement of any of Examples 1-

Claims

What is claimed is:

. An apparatus of a station (STA), the apparatus comprising: processing circuitry configured to: configure a low-power wake-up radio (LP-WUR) of the STA to receive a wake-up packet from an access point (AP) during a WUR mode, wherein during the WUR mode, a wireless local area network (WLAN) radio of the STA is configured to refrain from receiving radio frequency (RF) signals from the AP and the LP-WUR of the STA is configured to receive wake-up packets from the AP; decode the wake-up packet to determine a WUR authentication field including an authentication value; calculate a WUR authentication output value based on a WUR authentication input and a WUR authentication function, wherein the apparatus obtains the WUR authentication input and the WUR authentication function during a WUR negotiation with the AP; compare the WUR authentication output value to the authentication value; and authenticate the wake-up packet based on the WUR authentication output value matching the authentication value; and memory configured to store at least one of the authentication value, the WUR authentication input, and the WUR authentication function.

2. The apparatus of claim I, wherein the processing circuitry is further configured to discard the wake-up packet based on the calculated WUR authentication output value not matching the authentication value.

3. The apparatus of claim I, wherein during the WUR negotiation, the processing circuitry is further configured to: encode, for transmission to the AP, a request frame to enable a power save protocol between the STA and the AP; and decode a response frame from the AP, the request frame including one or more WUR authentication parameters defining a WUR authentication protocol.

4, The apparatus of claim 3, wherein the processing circuitry is configured to obtain the WUR authentication input and the WUR authentication function by decoding the WUR authentication input and the WUR authentication function from the response frame.

5, The apparatus of claim 4, wherein the processing circuitry is further configured to generate the WUR authentication input and the WUR authentication function.

6. The apparatus of claim 1, wherein the WUR authentication input is one-time input value.

7. The apparatus of claim 1, wherein the WUR authentication input includes one or more of an authentication password, a nonce, and an integrity key.

8, The apparatus of claim 6, wherein to initiate a second WUR authentication, the processing circuitry is configured to obtain a second WUR authentication input during a second WUR negotiation with the AP.

9. The apparatus of claim 3, wherein during the WUR negotiation, the processing circuitry is further configured to obtain one or more WUR authentication parameters, the WUR authentication parameters including one or more of an indication of a channel for transmitting a wake-up packet, and an indication of a security protocol.

10. The apparatus of claim 1, wherein the wake-up packet includes one or more WUR authentication parameters, the WUR authentication parameters including one or more of an indication of a channel for transmitting a wake-up packet, and an indication of a security protocol.

11. A method of wake-up packet authentication comprising: receiving a wake-up packet from an access point (AP) during a wake-up radio (WUR) mode, wherein during the WUR mode, a wireless local area network (WLAN) radio of the STA is configured to refrain from receiving radio frequency (RF) signals from the AP and a low-power wake-up radio (LP-WUR) of the STA is configured to receive wake-up packets from the AP; decoding the wake-up packet to determine a WUR authentication field including an authentication value; calculating a WUR authentication output value based on a WUR authentication input and a WUR authentication function, wherein the apparatus obtains the WUR authentication input and the WUR authentication function during a WUR negotiation with the AP; comparing the WUR authentication output value to the authentication value; and authenticating the wake-up packet based on the WUR authentication output value matching the authentication value.

12. The method of claim 11, further comprising discarding the wake- up packet based on the calculated WUR authentication output value not matching the authentication value.

13. The method of claim 11, further comprising; encoding, for transmission to the AP during the WUR negotiation, a request frame to enable a power save protocol between the STA and the AP; and decoding a response frame from the AP, the response frame including one or more WUR authentication parameters defining a WUR authentication protocol.

14. The method of claim 13, further comprising obtaining the WUR authentication input and the WUR authentication function by decoding the WUR authentication input and the WUR authentication function from the response frame.

15. The method of claim 14, further comprising generating the WUR authentication input and the WUR authentication function. 6. The method of claim 1 1, wherein the WUR authentication input is one-time input value.

17. The method of claim 11, wherein the WUR authentication input includes one or more of an authentication password, a nonce, and an integrity key.

18, The method of claim 16, further comprising obtaining a second WUR authentication input, during a second WUR negotiation with the AP to initiate a second WUR authentication for a second wake-up packet, wherein the second WUR authentication input includes one or more of an authentication password, a nonce, and an integrity key.

19. The method of claim 16, wherein the second WUR authentication input is obtained based on a changing pattern agreed upon during the first WUR negotiation with the AP.

20. The method of claim 13, further comprising obtaining, during the

WUR negotiation, one or more WUR authentication parameters, the WUR authentication parameters including one or more of an indication of a channel for transmitting a wake-up packet, an indication of a transmitting device

identification, an indication of a receiving device identification, and an indication of a security protocol.

21. The method of claim 13, wherein the wake-up packet includes one or more WUR authentication parameters, the WUR authentication parameters including one or more of an indication of a channel for transmitting a wake-up packet, an indication of a transmitting device identification, an indication of a receiving device identification, and an indication of a security protocol.

22. A computer-readable hardware storage device that stores instructions for execution by one or more processors of a station (STA), the instructions to configure the one or more processors to: configure a low-power wake-up radio (LP-WUR) of the STA to receive a wake-up packet from an access point (AP) during a WUR mode, wherein during the WUR mode, a wireless local area network (WLAN) radio of the STA is configured to refrain from receiving radio frequency (RF) signals from the AP and the LP-WUR of the STA is configured to receive wake-up packets from the AP; decode the wake-up packet to determine a WUR authentication field including an authentication value, calculate a WUR authentication output value based on a WUR

authentication input and a WUR authentication function, wherein the

instructions are further to configure the one or more processors to obtain the WUR authentication input and the WUR authentication function during a WUR negotiation with the AP, compare the WUR authentication output value to the authentication value; and authenticate the wake-up packet based on the WUR authentication output value matching the authentication value.

23. The computer-readable hardware storage device of claim 22, wherein the instructions are further to configure the one or more processors to discard the wake-up packet based on the calculated WUR authentication output value not matching the authentication value.

24. The computer-readable hardware storage device of claim 22, wherein during the WUR negotiation, the instructions are further to configure the one or more processors to: encode, for transmission to the AP, a request frame to enable a power save protocol between the STA and the AP; and decode a response frame from the AP, the request frame including one or more WUR authentication parameters defining a WUR authentication protocol.

25. The computer-readable hardware storage device of claim 24, wherein the instructions are further to configure the one or more processors to obtain the WUR authentication input and the WUR authentication function by decoding the WUR authentication input and the WUR authentication function from the response frame.