PACKETS

PRIORITY CLAIM

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

TECHNICAL FIELD [0002] Embodiments pertain to wireless communications. Some embodiments relate to wireless local area networks (WLANs) and Wi-Fi networks including networks operating in accordance with the IEEE 802.11 family of standards, including but not limited to IEEE 802.1 lax. Some embodiments relate to low power wake-up receiver (LP-WUR) operation. Some embodiments relate to LP-WUR devices.

BACKGROUND [0003] In some cases, devices may communicate over a wireless channel to exchange information such as voice, data and/or other. Some factors which may be considered in the design of some devices include cost, complexity, size, and battery life. For instance, a station (STA) or other mobile device may employ low power wake-up receiver (LP-WUR) techniques, which may increase battery life. The STA may operate in an LP-WUR mode in which reception capability may be reduced in comparison to a normal mode of operation.

Various challenges may arise as part of the LP-WUR operation, and therefore there is a general need for techniques to enable LP-WUR operation in these and other scenarios.

BRIEF DESCRIPTION OF THE DRAWINGS

[0004] FIG. 1 illustrates a wireless network in accordance with some embodiments;

[0005] FIG. 2 illustrates an example machine in accordance with some embodiments;

[0006] FIG. 3 illustrates a station (STA) in accordance with some embodiments and an access point (AP) in accordance with some embodiments;

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

[0008] FIG. 5 illustrates a front-end module circuitry for use in the radio architecture of FIG. 4 in accordance with some embodiments;

[0009] FIG. 6 illustrates a radio IC circuitry for use in the radio architecture of FIG. 4 in accordance with some embodiments;

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

[0011] FIG. 8 illustrates the operation of a method of communication in accordance with some embodiments;

[0012] FIG. 9 illustrates the operation of another method of communication in accordance with some embodiments;

[0013] FIG. 10 illustrates an example packet in accordance with some embodiments;

[0014] FIG. 11 illustrates additional example packets in accordance with some embodiments;

[0015] FIG. 12 illustrates additional example packets in accordance with some embodiments; and

[0016] FIG. 13 illustrates additional example packets in accordance with some embodiments. DETAILED DESCRIPTION [0017] The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of other embodiments. Embodiments set forth in the claims encompass all available equivalents of those claims.

[0018] FIG. 1 illustrates a wireless network in accordance with some embodiments. In some embodiments, the network 100 may be a High Efficiency (HE) Wireless Local Area Network (WLAN) network. In some embodiments, the network 100 may be a WLAN or a Wi-Fi network. These embodiments are not limiting, however, as some embodiments of the network 100 may include a combination of such networks. That is, the network 100 may support MU operation (for example HE) devices in some cases, non MU operation devices in some cases, and a combination of MU operation devices and non MU operation devices in some cases. Accordingly, it is understood that although techniques described herein may refer to either a non MU operation device or to an MU operation device, such techniques may be applicable to both non MU operation devices and MU operation devices in some cases.

[0019] Referring to FIG. 1, the network 100 may include any or all of the components shown, and embodiments are not limited to the number of each component shown in FIG. 1. In some embodiments, the network 100 may include an access point (AP) and may include any number (including zero) of stations (STAs) 103 and/or HE devices 104. In some embodiments, the AP 102 may be a master STA, may operate as a master STA and/or may be configured to operate as a master STA, although the scope of embodiments is not limited in this respect. In some embodiments, the AP 102 may receive and/or detect signals from one or more STAs 103, and may transmit data packets to one or more STAs 103. These embodiments will be described in more detail below. [0020] The AP 102 may be arranged to communicate with one or more of the components shown in FIG. 1 in accordance with one or more IEEE 802.1 1 standards (including 802.1 lax and/or others), other standards and/or other communication protocols. It should be noted that embodiments are not limited to usage of an AP 102. References herein to the AP 102 are not limiting and references herein to a master station are also not limiting. In some embodiments, a STA 103, an MU operation device (device capable of MU operation), an HE device 104 and/or other device may be configurable to operate as a master station. Accordingly, in such embodiments, operations that may be performed by the AP 102 as described herein may be performed by the STA 103, an MU operation device, an HE device 104 and/or other device that is configurable to operate as the master station.

[0021] In some embodiments, one or more of the STAs 103 may be legacy stations (for instance, a non MU operation device and/or device not capable of MU operation). These embodiments are not limiting, however, as the STAs 103 may be configured to operate as MU operation devices, HE devices 104 or may support MU operation or may support HE operation, in some embodiments. The AP 102 may be arranged to communicate with the STAs 103 and/or the HE stations and/or the MU operation stations in accordance with one or more of the IEEE 802.1 1 standards, including 802.1 lax and/or others. In accordance with some HE operation embodiments and/or MU operation embodiments, an access point (AP) may operate as a master station and may be arranged to contend for a wireless medium (e.g., during a contention period) to receive exclusive control of the medium for an 802.1 1 air access control period (i.e., a transmission opportunity (TXOP)). The AP 102 may, for example, transmit a master-sync or control transmission at the beginning of the 802.1 1 air access control period (including but not limited to an HE control period) to indicate, among other things, which MU operation stations and/or HE stations 104 are scheduled for communication during the 802.1 1 air access control period. During the 802.1 1 air access control period, the scheduled MU operation stations 104 may communicate with the AP 102 in accordance with a non- contention based multiple access technique. This is unlike conventional Wi-Fi communications in which devices communicate in accordance with a contention- based communication technique, rather than a non-contention based multiple access technique. During the 802.1 1 air access control period, the AP 102 may communicate with HE stations 104 using one or more MU PPDUs. During the 802.1 1 air access control period, STAs 103 not operating as MU operation devices may refrain from communicating in some cases. In some embodiments, the master-sync transmission may be referred to as a control and schedule transmission.

[0022] In some embodiments, the multiple-access technique used during the 802.1 1 air access control period may be a scheduled orthogonal frequency- division multiple access (OFDMA) technique, although this is not a requirement. In some embodiments, the multiple access technique may be a time-division multiple access (TDMA) technique or a frequency-division multiple access (FDMA) technique. In some embodiments, the multiple access technique may be a space-division multiple access (SDMA) technique including a multi-user (MU) multiple-input multiple-output (MIMO) (MU-MIMO) technique or combination of the above. These multiple-access techniques used during the 802.11 air access control period may be configured for uplink or downlink data communications.

[0023] The AP 102 may also communicate with STAs 103 and/or other legacy stations in accordance with legacy IEEE 802.1 1 communication techniques. In some embodiments, the AP 102 may also be configurable to communicate with the MU operation stations and/or HE stations 104 outside the 802.1 1 air access control period in accordance with legacy IEEE 802.1 1 communication techniques, although this is not a requirement.

[0024] In some embodiments, communications (including but not limited to the MU communications) during the control period may be configurable to use one of 20MHz, 40MHz, or 80MHz contiguous bandwidths or an 80+80MHz (160MHz) non-contiguous bandwidth. In some embodiments, a 320MHz channel width may be used. In some embodiments, sub-channel bandwidths less than 20MHz may also be used. In these embodiments, each channel or sub- channel of a communications (including but not limited to the MU

communications) may be configured for transmitting a number of spatial streams. [0025] In some embodiments, MU techniques may be used, although the scope of embodiments is not limited in this respect. As an example, techniques included in 802.1 lax standards and/or other standards may be used. In accordance with some embodiments, an AP 102, an STA 103, MU operation STAs and/or HE stations 104 may generate an MU packet in accordance with a short preamble format or a long preamble format. The MU packet may comprise a legacy signal field (L-SIG) followed by one or more MU signal fields (HE- SIG) and an MU long-training field (MU -LTF). It should be noted that the terms "HEW" and "HE" may be used interchangeably and both terms may refer to high-efficiency Wireless Local Area Network operation and/or high- efficiency Wi-Fi operation.

[0026] It should also be noted that the AP 102 may operate as an STA

103, in some embodiments. Some techniques, operations and/or methods may be described herein in terms of communication between two STAs 103, but such descriptions are not limiting. Some or all of those techniques, operations and/or methods may be applicable to scenarios in which an STA 103 and an AP 102 communicate. In addition, some techniques, operations and/or methods may be described herein in terms of communication between an STA 103 and an AP 102, but such descriptions are not limiting. Some or all of those techniques, operations and/or methods may be applicable to scenarios in which two or more STAs 103 communicate.

[0027] In some embodiments, the STAs 103, AP 102, other mobile devices, other base stations and/or other devices may be configured to perform operations related to contention based communication. As an example, the communication between the STAs 103 and/or AP 102 and/or the communication between the STAs 103 may be performed in accordance with contention based techniques. In such cases, the STAs 103 and/or AP 102 may be arranged to contend for a wireless medium (e.g., during a contention period) to receive exclusive control of the medium for a transmission period. For instance, the transmission period may include a transmission opportunity (TXOP), which may be included in an 802.11 standard and/or other standard.

[0028] It should be noted that embodiments are not limited to usage of contention based techniques, however, as some communication (such as that between mobile devices and/or communication between a mobile device and a base station) may be performed in accordance with schedule based techniques. Some embodiments may include a combination of contention based techniques and schedule based techniques.

[0029] In some embodiments, the communication between mobile devices and/or between a mobile device and a base station may be performed in accordance with single carrier techniques. As an example, a protocol data unit (PDU) and/or other frame(s) may be modulated on a single carrier frequency in accordance with a single carrier modulation (SCM) technique.

[0030] In some embodiments, the communication between mobile devices and/or between a mobile device and a base station may be performed in accordance with any suitable multiple-access techniques and/or multiplexing techniques. Accordingly, one or more of orthogonal frequency division multiple access (OFDMA), orthogonal frequency division multiplexing (OFDM), code- division multiple access (CDMA), time-division multiple access (TDMA), frequency division multiplexing (FDMA), space-division multiple access (SDMA), multiple-input multiple-output (MIMO), multi-user (MU) multiple- input multiple -output (MIMO) (MU-MIMO) and/or other techniques may be employed in some embodiments.

[0031] As used herein, the term "circuitry" may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. In some embodiments, the circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules. In some embodiments, circuitry may include logic, at least partially operable in hardware. Embodiments described herein may be implemented into a system using any suitably configured hardware and/or software.

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

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

[0034] Accordingly, the term "module" is understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., transitorily) configured (e.g., programmed) to operate in a specified manner or to perform part or all of any operation described herein. Considering examples in which modules are temporarily configured, each of the modules need not be instantiated at any one moment in time. For example, where the modules comprise a general -purpose hardware processor configured using software, the general-purpose hardware processor may be configured as respective different modules at different times. Software may accordingly configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time.

[0035] The machine (e.g., computer system) 200 may include a hardware processor 202 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 204 and a static memory 206, some or all of which may communicate with each other via an interlink (e.g., bus) 208. The machine 200 may further include a display device 210, an alphanumeric input device 212 (e.g., a keyboard), and a user interface (UI) navigation device 214 (e.g., a mouse). In an example, the display device 210, input device 212 and UI navigation device 214 may be a touch screen display. The machine 200 may additionally include mass storage 216 (such as a storage device, drive unit and/or other), a signal generation device 218 (e.g., a speaker), a network interface device 220, and one or more sensors 221, such as a global positioning system (GPS) sensor, compass, accelerometer, or other sensor. The machine 200 may include an output controller 228, 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.).

[0036] The mass storage 216 may include a machine readable medium

222 on which is stored one or more sets of data structures or instructions 224 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions 224 may also reside, completely or at least partially, within the main memory 204, within static memory 206, or within the hardware processor 202 during execution thereof by the machine

200. In an example, one or any combination of the hardware processor 202, the main memory 204, the static memory 206, or the mass storage 216 may constitute machine readable media. In some embodiments, the machine readable medium may be or may include a non-transitory computer-readable storage medium.

[0037] While the machine readable medium 222 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 224. The term "machine readable medium" may include any medium that is capable of storing, encoding, or carrying instructions for execution by the machine 200 and that cause the machine 200 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions. Non-limiting machine readable medium examples may include solid-state memories, and optical and magnetic media. Specific examples of machine readable media may include: non-volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable

Programmable Read-Only Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; Random Access Memory (RAM); and CD-ROM and DVD-ROM disks. In some examples, machine readable media may include non-transitory machine readable media. In some examples, machine readable media may include machine readable media that is not a transitory propagating signal.

[0038] The instructions 224 may further be transmitted or received over a communications network 226 using a transmission medium via the network interface device 220 utilizing any one of a number of transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.). Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), Plain Old Telephone (POTS) networks, and wireless data networks (e.g., Institute of Electrical and Electronics Engineers

(IEEE) 802.1 1 family of standards known as Wi-Fi®, IEEE 802.16 family of standards known as WiMax®), IEEE 802.15.4 family of standards, a Long Term

Evolution (LTE) family of standards, a Universal Mobile Telecommunications System (UMTS) family of standards, peer-to-peer (P2P) networks, among others. In an example, the network interface device 220 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 226. In an example, the network interface device 220 may include a plurality of antennas to wirelessly communicate using at least one of single-input multiple-output (SIMO), multiple-input multiple-output (MIMO), or multiple-input single-output (MISO) techniques. In some examples, the network interface device 220 may wirelessly communicate using Multiple User MIMO techniques. The term "transmission medium" shall be taken to include any intangible medium that is capable of storing, encoding or carrying instructions for execution by the machine 200, and includes digital or analog communications signals or other intangible medium to facilitate communication of such software.

[0039] FIG. 3 illustrates a station (STA) in accordance with some embodiments and an access point (AP) in accordance with some embodiments. It should be noted that in some embodiments, an STA or other mobile device may include one or more components shown in any of FIG. 2, FIG. 3 (as in 300) or FIGs. 4-7. In some embodiments, the STA 300 may be suitable for use as an STA 103 as depicted in FIG. 1, although the scope of embodiments is not limited in this respect. It should also be noted that in some embodiments, an AP or other base station may include one or more components shown in any of FIG. 2, FIG. 3 (as in 350) or FIGs. 4-7. In some embodiments, the AP 350 may be suitable for use as an AP 102 as depicted in FIG. 1, although the scope of embodiments is not limited in this respect.

[0040] The STA 300 may include physical layer circuitry 302 and a transceiver 305, one or both of which may enable transmission and reception of signals to and from components such as the AP 102 (FIG. 1), other STAs or other devices using one or more antennas 301. As an example, the physical layer circuitry 302 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 305 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 302 and the transceiver 305 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 302, the transceiver 305, and other components or layers. The STA 300 may also include medium access control (MAC) layer circuitry 304 for controlling access to the wireless medium. The STA 300 may also include processing circuitry 306 and memory 308 arranged to perform the operations described herein.

[0041] In some embodiments, the STA 300 (and/or apparatus of an STA) may include a low-power wake-up receiver (LP-WUR). In some embodiments, the STA 300 (and/or apparatus of an STA) may be configured to perform one or more operations of an LP-WUR. Different embodiments are possible, including but not limited to those described below and elsewhere herein. These embodiments are not limiting, however, as any suitable components and/or combinations of components may be used to implement one or more of the operations described herein.

[0042] In some embodiments, the STA 300 (and/or apparatus of an STA) may include an LP-WUR 315, which may be separate from the other components 302, 304, 305, 306, 308. In some of those embodiments, one or more of the components 302-308 may perform one or more operations of a normal mode, awake mode and/or similar mode. For instance, transmission and/or reception of data packets, data signals and/or other elements may be performed by one or more of the components 302-308 while the STA 300 operates in the normal mode, awake mode and/or similar mode. Reception of wake-up packets (which will be described below) may be performed by the LP- WUR 315 while the STA 300 operates in a sleep mode, low power mode and/or similar mode.

[0043] In some embodiments, one or more of the components 302-308 of the STA 300 (and/or apparatus of an STA) may perform LP-WUR functionality in addition to other functionality. For instance, the STA 300 (and/or apparatus of an STA) may operate in a sleep mode, low power mode and/or similar mode and may perform one or more operations described herein related to LP-WUR. In some embodiments, the STA 300 (and/or apparatus of an STA) may also operate in the normal mode, awake mode and/or similar mode. For instance, one or more of the components 302-308 may perform transmission and/or reception of data packets, data signals and/or other elements while the STA 300 operates in the normal mode, awake mode and/or similar mode. One or more of the components 302-308 may also perform reception of wake-up packets (which will be described below) while the STA 300 operates in a sleep mode, low power mode and/or similar mode. In another instance, one or more of the components 302-308 may also perform reception of wake-up packets (for other purposes, for example to receive specific control information ) while the STA 300 operates in the normal mode, awake mode and/or similar mode.

[0044] The AP 350 may include physical layer circuitry 352 and a transceiver 355, one or both of which may enable transmission and reception of signals to and from components such as the STA 103 (FIG. 1), other APs or other devices using one or more antennas 351. As an example, the physical layer circuitry 352 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 355 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 352 and the transceiver 355 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 352, the transceiver 355, and other components or layers. The AP 350 may also include medium access control (MAC) layer circuitry 354 for controlling access to the wireless medium. The AP 350 may also include processing circuitry 356 and memory 358 arranged to perform the operations described herein.

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

[0046] In some embodiments, the STA 300 may be configured to communicate using OFDM and/or OFDMA communication signals over a multicamer communication channel. In some embodiments, the AP 350 may be configured to communicate using OFDM and/or OFDMA communication signals over a multicarrier communication channel. Accordingly, in some cases, the STA 300 and/or AP 350 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.1 1-2012, 802.1 ln- 2009, 802.1 lac -2013 standards, 802.1 lax standards (and/or proposed standards), 802.1 lay standards (and/or proposed standards) and/or other, although the scope of the embodiments 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 embodiments, the AP 350 and/or the STA 300 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 embodiments is not limited in this respect.

[0047] In some embodiments, the STA 300 and/or AP 350 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 embodiments, the STA 300 and/or AP 350 may be configured to operate in accordance with 802.1 1 standards, although the scope of the embodiments is not limited in this respect.

Mobile devices or other devices in some embodiments 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 embodiments, the STA 300 and/or AP 350 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.

[0048] Although the STA 300 and the AP 350 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 embodiments, the functional elements may refer to one or more processes operating on one or more processing elements.

[0049] Embodiments may be implemented in one or a combination of hardware, firmware and software. Embodiments 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 embodiments may include one or more processors and may be configured with instructions stored on a computer-readable storage device.

[0050] It should be noted that in some embodiments, an apparatus of the

STA 300 may include various components of the STA 300 as shown in FIG. 3 and/or the example machine 200 as shown in FIG. 2 and/or various components shown in FIGs. 4-7. Accordingly, techniques and operations described herein that refer to the STA 300 (or 103) may be applicable to an apparatus of an STA, in some embodiments. It should also be noted that in some embodiments, an apparatus of the AP 350 may include various components of the AP 350 as shown in FIG. 3 and/or the example machine 200 as shown in FIG. 2 and/or various components shown in FIGs. 4-7. Accordingly, techniques and operations described herein that refer to the AP 350 (or 102) may be applicable to an apparatus of an AP, in some embodiments. In addition, an apparatus of a mobile device and/or base station may include one or more components shown in FIGs. 2-7, in some embodiments. Accordingly, techniques and operations described herein that refer to a mobile device and/or base station may be applicable to an apparatus of a mobile device and/or base station, in some embodiments.

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

[0052] It should be noted that the radio architecture 400 and components shown in FIGs. 5-7 support WLAN and BT, but embodiments are not limited to WLAN or BT. In some embodiments, two technologies supported by the radio architecture 400 may or may not include WLAN or BT. Other technologies may be supported. In some embodiments, WLAN and a second technology may be supported. In some embodiments, BT and a second technology may be supported. In some embodiments, two technologies other than WLAN and BT may be supported. In addition, the radio architecture 400 may be extended to support more than two protocols, technologies and/or standards, in some embodiments. Embodiments are also not limited to the frequencies illustrated in FIGs. 4-7.

[0053] FEM circuitry 404 may include a WLAN or Wi-Fi FEM circuitry 404A and a Bluetooth (BT) FEM circuitry 404B. The WLAN FEM circuitry

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

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

WLAN radio IC circuitry 406A may also include a transmit signal path which may include circuitry to up-convert WLAN baseband signals provided by the WLAN baseband processing circuitry 408A and provide WLAN RF output signals to the FEM circuitry 404A for subsequent wireless transmission by the one or more antennas 401. BT radio IC circuitry 406B may also include a transmit signal path which may include circuitry to up-convert BT baseband signals provided by the BT baseband processing circuitry 408B and provide BT

RF output signals to the FEM circuitry 404B for subsequent wireless transmission by the one or more antennas 401. In the embodiment of FIG. 4, although radio IC circuitries 406A and 406B are shown as being distinct from one another, embodiments are not so limited, and include within their scope the use of a radio IC circuitry (not shown) that includes a transmit signal path and/or a receive signal path for both WLAN and BT signals, or the use of one or more radio IC circuitries where at least some of the radio IC circuitries share transmit and/or receive signal paths for both WLAN and BT signals.

[0055] Baseband processing circuity 408 may include a WLAN baseband processing circuitry 408A and a BT baseband processing circuitry 408B. The WLAN baseband processing circuitry 408A 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 408A. Each of the WLAN baseband circuitry 408A and the BT baseband circuitry 408B 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 406, and to also generate corresponding WLAN or BT baseband signals for the transmit signal path of the radio IC circuitry 406. Each of the baseband processing circuitries 408A and 408B may further include physical layer (PHY) and medium access control layer (MAC) circuitry, and may further interface with application processor 411 for generation and processing of the baseband signals and for controlling operations of the radio IC circuitry 406.

[0056] Referring still to FIG. 4, according to the shown embodiment,

WLAN-BT coexistence circuitry 413 may include logic providing an interface between the WLAN baseband circuitry 408A and the BT baseband circuitry 408B to enable use cases requiring WLAN and BT coexistence. In addition, a switch 403 may be provided between the WLAN FEM circuitry 404A and the BT FEM circuitry 404B to allow switching between the WLAN and BT radios according to application needs. In addition, although the antennas 401 are depicted as being respectively connected to the WLAN FEM circuitry 404A and the BT FEM circuitry 404B, embodiments include within their scope the sharing of one or more antennas as between the WLAN and BT FEMs, or the provision of more than one antenna connected to each of FEM 404A or 404B. [0057] In some embodiments, the front-end module circuitry 404, the radio IC circuitry 406, and baseband processing circuitry 408 may be provided on a single radio card, such as wireless radio card 402. In some other embodiments, the one or more antennas 401, the FEM circuitry 404 and the radio IC circuitry 406 may be provided on a single radio card. In some other embodiments, the radio IC circuitry 406 and the baseband processing circuitry 408 may be provided on a single chip or integrated circuit (IC), such as IC 412.

[0058] In some embodiments, the wireless radio card 402 may include a

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

[0059] In some of these multicarrier embodiments, radio architecture 400 may be part of a Wi-Fi communication station (STA) such as a wireless access point (AP), a base station or a mobile device including a Wi-Fi device. In some of these embodiments, radio architecture 400 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, 802.1 ln-2009, IEEE 802.1 1-2012, 802.1 1n-2009, 802.1 lac, and/or 802.1 lax standards and/or proposed specifications for WLANs, although the scope of embodiments is not limited in this respect. Radio architecture 400 may also be suitable to transmit and/or receive communications in accordance with other techniques and standards.

[0060] In some embodiments, the radio architecture 400 may be configured for high-efficiency (HE) Wi-Fi (HEW) communications in accordance with the IEEE 802.1 lax standard. In these embodiments, the radio architecture 400 may be configured to communicate in accordance with an

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

[0062] In some embodiments, as further shown in FIG. 4, the BT baseband circuitry 408B may be compliant with a Bluetooth (BT) connectivity standard such as Bluetooth, Bluetooth 4.0 or Bluetooth 5.0, or any other iteration of the Bluetooth Standard. In embodiments that include BT functionality as shown for example in Fig. 4, the radio architecture 400 may be configured to establish a BT synchronous connection oriented (SCO) link and/or a BT low energy (BT LE) link. In some of the embodiments that include functionality, the radio architecture 400 may be configured to establish an extended SCO (eSCO) link for BT communications, although the scope of the embodiments is not limited in this respect. In some of these embodiments that include a BT functionality, the radio architecture may be configured to engage in a BT Asynchronous Connection-Less (ACL) communications, although the scope of the embodiments is not limited in this respect. In some embodiments, as shown in FIG. 4, 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 402, although embodiments are not so limited, and include within their scope discrete WLAN and BT radio cards.

[0063] In some embodiments, the radio-architecture 400 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).

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

[0065] FIG. 5 illustrates FEM circuitry 500 in accordance with some embodiments. The FEM circuitry 500 is one example of circuitry that may be suitable for use as the WLAN and/or BT FEM circuitry 404A/404B (FIG. 4), although other circuitry configurations may also be suitable.

[0066] In some embodiments, the FEM circuitry 500 may include a

TX/RX switch 502 to switch between transmit mode and receive mode operation. The FEM circuitry 500 may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry 500 may include a low -noise amplifier (LNA) 506 to amplify received RF signals 503 and provide the amplified received RF signals 507 as an output (e.g., to the radio IC circuitry 406 (FIG. 4)). The transmit signal path of the circuitry 500 may include a power amplifier (PA) 510 to amplify input RF signals 509 (e.g., provided by the radio IC circuitry 406), and one or more filters 512, such as band-pass filters (BPFs), low-pass filters (LPFs) or other types of filters, to generate RF signals 515 for subsequent transmission (e.g., by one or more of the antennas 401 (FIG. 4)).

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

FEM circuitry 500 may be configured to operate in either the 2.4 GHz frequency spectrum or the 5 GHz frequency spectrum. In these embodiments, the receive signal path of the FEM circuitry 500 may include a receive signal path duplexer 504 to separate the signals from each spectrum as well as provide a separate LNA 506 for each spectrum as shown. In these embodiments, the transmit signal path of the FEM circuitry 500 may also include a power amplifier 510 and a filter 512, such as a BPF, a LPF or another type of filter for each frequency spectrum and a transmit signal path duplexer 514 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 401 (FIG. 4). In some embodiments, BT communications may utilize the 2.4 GHZ signal paths and may utilize the same FEM circuitry 500 as the one used for WLAN communications.

[0068] FIG. 6 illustrates radio IC circuitry 600 in accordance with some embodiments. The radio IC circuitry 600 is one example of circuitry that may be suitable for use as the WLAN or BT radio IC circuitry 406A/406B (FIG. 4), although other circuitry configurations may also be suitable.

[0069] In some embodiments, the radio IC circuitry 600 may include a receive signal path and a transmit signal path. The receive signal path of the radio IC circuitry 600 may include at least mixer circuitry 602, such as, for example, down-conversion mixer circuitry, amplifier circuitry 606 and filter circuitry 608. The transmit signal path of the radio IC circuitry 600 may include at least filter circuitry 612 and mixer circuitry 614, such as, for example, up- conversion mixer circuitry. Radio IC circuitry 600 may also include synthesizer circuitry 604 for synthesizing a frequency 605 for use by the mixer circuitry 602 and the mixer circuitry 614. The mixer circuitry 602 and/or 614 may each, according to some embodiments, be configured to provide direct conversion functionality. The latter type of circuitry presents a much simpler architecture as compared with standard super-heterodyne mixer circuitries, and any flicker noise brought about by the same may be alleviated for example through the use of OFDM modulation. Fig. 6 illustrates only a simplified version of a radio IC circuitry, and may include, although not shown, embodiments where each of the depicted circuitries may include more than one component. For instance, mixer circuitry 602 and/or 614 may each include one or more mixers, and filter circuitries 608 and/or 612 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.

[0070] In some embodiments, mixer circuitry 602 may be configured to down-convert RF signals 507 received from the FEM circuitry 404 (FIG. 4) based on the synthesized frequency 605 provided by synthesizer circuitry 604.

The amplifier circuitry 606 may be configured to amplify the down-converted signals and the filter circuitry 608 may include a LPF configured to remove unwanted signals from the down-converted signals to generate output baseband signals 607. Output baseband signals 607 may be provided to the baseband processing circuitry 408 (FIG. 4) for further processing. In some embodiments, the output baseband signals 607 may be zero-frequency baseband signals, although this is not a requirement. In some embodiments, mixer circuitry 602 may comprise passive mixers, although the scope of the embodiments is not limited in this respect.

[0071] In some embodiments, the mixer circuitry 614 may be configured to up-convert input baseband signals 61 1 based on the synthesized frequency 605 provided by the synthesizer circuitry 604 to generate RF output signals 509 for the FEM circuitry 404. The baseband signals 61 1 may be provided by the baseband processing circuitry 408 and may be filtered by filter circuitry 612. The filter circuitry 612 may include a LPF or a BPF, although the scope of the embodiments is not limited in this respect.

[0072] In some embodiments, the mixer circuitry 602 and the mixer circuitry 614 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 604. In some embodiments, the mixer circuitry 602 and the mixer circuitry 614 may each include two or more mixers each configured for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 602 and the mixer circuitry 614 may be arranged for direct down- conversion and/or direct up-conversion, respectively. In some embodiments, the mixer circuitry 602 and the mixer circuitry 614 may be configured for superheterodyne operation, although this is not a requirement.

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

[0074] 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 605 of synthesizer 604 (FIG. 6). In some embodiments, the LO frequency may be the carrier frequency, while in other embodiments, the LO frequency may be a fraction of the carrier frequency (e.g., one-half the carrier frequency, one-third the carrier frequency). In some embodiments, the zero and ninety degree time-varying switching signals may be generated by the synthesizer, although the scope of the embodiments is not limited in this respect.

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

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

[0076] The RF input signal 507 (FIG. 5) may comprise a balanced signal, although the scope of the embodiments is not limited in this respect. The I and Q baseband output signals may be provided to low-nose amplifier, such as amplifier circuitry 606 (FIG. 6) or to filter circuitry 608 (FIG. 6).

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

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

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

[0079] In some embodiments, the synthesizer circuitry 604 may be a fractional -N synthesizer or a fractional N/N+1 synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, synthesizer circuitry 604 may be a delta-sigma synthesizer, a frequency multiplier, a frequency-locked loop or a synthesizer comprising a phase-locked loop with a frequency divider. According to some embodiments, the synthesizer circuitry 604 may include digital synthesizer circuitry. An advantage of using a digital synthesizer circuitry is that, although it may still include some analog components, its footprint may be scaled down much more than the footprint of an analog synthesizer circuitry. In some embodiments, frequency input into synthesizer circuity 604 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 408 (FIG. 4) or the application processor 41 1 (FIG. 4) depending on the desired output frequency 605. In some embodiments, a divider control input (e.g., N) may be determined from a look-up table (e.g., within a Wi-Fi card) based on a channel number and a channel center frequency as determined or indicated by the application processor 41 1.

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

[0081] FIG. 7 illustrates a functional block diagram of baseband processing circuitry 700 in accordance with some embodiments. The baseband processing circuitry 700 is one example of circuitry that may be suitable for use as the baseband processing circuitry 408 (FIG. 4), although other circuitry configurations may also be suitable. The baseband processing circuitry 700 may include a receive baseband processor (RX BBP) 702 for processing receive baseband signals 609 provided by the radio IC circuitry 406 (FIG. 4) and a transmit baseband processor (TX BBP) 704 for generating transmit baseband signals 61 1 for the radio IC circuitry 406. The baseband processing circuitry 700 may also include control logic 706 for coordinating the operations of the baseband processing circuitry 700.

[0082] In some embodiments (e.g., when analog baseband signals are exchanged between the baseband processing circuitry 700 and the radio IC circuitry 406), the baseband processing circuitry 700 may include ADC 710 to convert analog baseband signals received from the radio IC circuitry 406 to digital baseband signals for processing by the RX BBP 702. In these embodiments, the baseband processing circuitry 700 may also include DAC 712 to convert digital baseband signals from the TX BBP 704 to analog baseband signals.

[0083] In some embodiments that communicate OFDM signals or OFDMA signals, such as through baseband processor 408A, the transmit baseband processor 704 may be configured to generate OFDM or OFDMA signals as appropriate for transmission by performing an inverse fast Fourier transform (IFFT). The receive baseband processor 702 may be configured to process received OFDM signals or OFDMA signals by performing an FFT. In some embodiments, the receive baseband processor 702 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.

[0084] Referring back to FIG. 4, in some embodiments, the antennas 401

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

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

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

[0086] Embodiments may be implemented in one or a combination of hardware, firmware and software. Embodiments 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 read- only memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices, and other storage devices and media. Some embodiments may include one or more processors and may be configured with instructions stored on a computer-readable storage device.

[0087] In accordance with some embodiments, the AP 102 may select, from first and second data rates, a data rate for a wake-up packet to indicate that an STA 103 is to transition from a sleep mode to an awake mode for a downlink data transmission from the AP 102. The AP 102 may encode a medium access control (MAC) header to include an identifier of the STA 103. The AP 102 may encode the MAC header in accordance with the selected data rate. The AP 102 may encode a payload in accordance with the selected data rate. The AP 102 may encode a wake-up preamble to include a configurable number of preamble sequences to indicate the selected data rate. A first number of preamble sequences may indicate that the MAC header and the payload are encoded in accordance with the first data rate. A second number of preamble sequences may indicate that the MAC header and the payload are encoded in accordance with the second data rate. The AP 102 may encode, for transmission, the wake- up packet to include the wake-up preamble, the MAC header and the payload. These embodiments are described in more detail below.

[0088] FIG. 8 illustrates the operation of a method of communication in accordance with some embodiments. It is important to note that embodiments of the method 800 may include additional or even fewer operations or processes in comparison to what is illustrated in FIG. 8. Some embodiments of the method

800 may not necessarily include all operations shown in FIG. 8. In addition, embodiments of the method 800 are not necessarily limited to the chronological order that is shown in FIG. 8. In describing the method 800, reference may be made to FIGs. 1-7 and 9-13, although it is understood that the method 800 may be practiced with any other suitable systems, interfaces and components.

[0089] In addition, the method 800 and other methods described herein may refer to STAs 103 or APs 102 operating in accordance with an 802.11 standard, protocol and/or specification and/or WLAN standard, protocol and/or specification, in some cases. Embodiments of those methods are not limited to just those STAs 103 or APs 102 and may also be practiced on other devices, such as a User Equipment (UE), an Evolved Node-B (eNB) and/or other device. In addition, the method 800 and other methods described herein may be practiced by wireless devices configured to operate in other suitable types of wireless communication systems, including systems configured to operate according to various Third Generation Partnership Protocol (3GPP) standards, including but not limited to Long Term Evolution (LTE). The method 800 may also be practiced by an apparatus of an STA 103 and/or AP 102 and/or other device, in some embodiments.

[0090] In some embodiments, an AP 102 may perform one or more operations of the method 800, but embodiments are not limited to performance of the method 800 and/or operations of it by the AP 102. In some embodiments, an STA 103 may perform one or more operations of the method 800 (and/or similar operations). Accordingly, although references may be made to performance of one or more operations of the method 800 by the AP 102 in descriptions herein, it is understood that the STA 103 may perform the same operation(s), similar operation(s) and/or reciprocal operation(s), in some embodiments. In some embodiments, an HE device 104 may perform one or more operations of the method 800 (and/or similar operations). Accordingly, although references may be made to performance of one or more operations of the method 800 by the AP 102 in descriptions herein, it is understood that the HE device 104 may perform the same operation(s), similar operation(s) and/or reciprocal operation(s), in some embodiments.

[0091] It should also be noted that embodiments are not limited by references herein (such as in descriptions of the methods 800, 900 and/or other descriptions herein) to transmission, reception and/or exchanging of elements such as frames, messages, requests, indicators, signals or other elements. In some embodiments, such an element may be generated, encoded or otherwise processed by processing circuitry (such as by a baseband processor included in the processing circuitry) for transmission. The transmission may be performed by a transceiver or other component, in some cases. In some embodiments, such an element may be decoded, detected or otherwise processed by the processing circuitry (such as by the baseband processor). The element may be received by a transceiver or other component, in some cases. In some embodiments, the processing circuitry and the transceiver may be included in a same apparatus. The scope of embodiments is not limited in this respect, however, as the transceiver may be separate from the apparatus that comprises the processing circuitry, in some embodiments.

[0092] At operation 805, the AP 102 may receive one or more control messages from an STA 103. In some embodiments, the AP 102 may transmit one or more control messages to the STA 103. In some embodiments, the STA

103 and the AP 102 may exchange one or more control messages.

[0093] Various information may be included in the control message(s).

Some of the information may be related to LP-WUR operation of the STA 103, in some embodiments. Such information may include, but is not limited to: whether the STA 103 supports LP-WUR operation, a number of data rates supported by the STA 103 for the wake-up packet, one or more data rates supported by the STA 103 for the wake-up packet and/or other information.

These examples will be described in more detail below. In some embodiments, the control message(s) may include information that may not necessarily be related to LP-WUR operation of the STA 103.

[0094] At operation 810, the AP 102 may receive an uplink data transmission from the STA 103. At operation 815, the AP 102 may determine a signal quality measurement based at least partly on the uplink data transmission. Embodiments are not limited to usage of a signal quality measurement, as any suitable measurement may be used. Example measurements include, but are not limited to: a received power, received signal strength indicator (RSSI) and a signal-to-noise ratio (SNR). [0095] At operation 820, the AP 102 may schedule a downlink data transmission to the STA 103. In some embodiments, the AP 102 may determine that downlink data is to be transmitted to the STA 103, but may not necessarily schedule the downlink data transmission.

[0096] At operation 825, the AP 102 may select a data rate to be used for transmission of a wake-up packet. In some embodiments, the AP 102 may select a data rate to be used to encode one or more elements of the wake-up packet, including but not limited to a MAC header and a payload.

[0097] In some embodiments, the AP 102 may select the data rate based at least partly on the signal quality measurement, although the scope of embodiments is not limited in this respect.

[0098] In some embodiments, the AP 102 may select a data rate from a plurality of candidate data rates (which may be predetermined, in some cases). In a non-limiting example, the AP 102 may select the data rate from: a first data rate, and a second data rate. In some of the examples described herein, the first data rate may be higher than the second data rate, but the scope of embodiments is not limited in this respect.

[0099] In a non-limiting example, one of the data rates, such as the first data rate and/or higher data rate (of the two data rates), may be considered a "mandatory rate" in a standard. The other data rate, such as the second data rate and/or lower data rate (of the two data rates), may be considered an "optional rate" in the standard. The scope of embodiments is not limited by this example. In some embodiments, the second data rate and/or lower data rate, may be considered a "mandatory rate".

[00100] In a non-limiting example, the second data rate may be less than the first data rate. The AP 102 may select the first data rate if the signal quality measurement is greater than a predetermined threshold. The AP 102 may select the second data rate if the signal quality measurement is less than or equal to the predetermined threshold. This example may be extended to accommodate more than two data rates, in some cases. For instance, one or more additional thresholds may be used, and one or more additional comparisons may be used.

[00101] In a non-limiting example, the AP 102 may receive one or more control messages from the STA 103 (such as at operation 805) that indicate whether the STA 103 supports reception of the wake-up packet at the first data rate and whether the STA 103 supports reception of the wake-up packet at the second data rate. The AP 102 may select the data rate based at least partly on the control message. For instance, if the STA 103 supports reception at the first data rate but not at the second data rate, the AP 102 may not select the second data rate.

[00102] In some embodiments, the wake-up packet may be transmitted to indicate, to the STA 103, that the STA 103 is to transition from a sleep mode (and/or similar mode) to an active mode (and/or similar mode) for a downlink data transmission from the AP 102. In some embodiments, the wake-up packet may be transmitted to indicate, to the STA 103, that the STA 103 is to transition from the sleep mode to the active mode to receive downlink data from the AP 102. In some embodiments, the wake-up packet may be transmitted to indicate, to the STA 103, that the AP 102 intends to transmit downlink data to the STA 103.

[00103] It should be noted that some embodiments may not necessarily include all operations shown in FIG. 8. For instance, the AP 102 may not necessarily select the data rate based on an uplink data transmission and/or signal quality measurement. In some embodiments, the AP 102 may use a default data rate in some cases. The AP 102 may also determine, using other technique(s), which data rate to use.

[00104] At operation 830, the AP 102 may encode a MAC header. In some embodiments, the MAC header may include an identifier of the STA 103, although the scope of embodiments is not limited in this respect. In some embodiments, additional information may be included in the MAC header.

[00105] In a non-limiting example, the identifier of the STA 103 may be a

MAC address. In another non-limiting example, the identifier of the STA 103 may be a partial MAC address. These examples are not limiting, as other identifiers may be used.

[00106] In some embodiments, the AP 102 may encode the MAC header in accordance with the selected data rate. In a non-limiting example, the AP 102 may encode the MAC header in accordance with on-off keying (OOK) modulation. Embodiments are not limited to OOK modulation, however, as any suitable type of modulation may be used.

[00107] At operation 835, the AP 102 may encode a payload. In some embodiments, the payload may include scheduling information for the downlink transmission, although the scope of embodiments is not limited in this respect. In some embodiments, additional information may be included in the payload. In some embodiments, the payload may be referred to as a "frame body." In the methods, operations and/or techniques described herein references to a payload are not limiting. In some or all of those methods, operations and/or techniques, the payload may be replaced by a frame body.

[00108] In some embodiments, the AP 102 may encode the payload in accordance with the selected data rate. In a non-limiting example, the AP 102 may encode the payload in accordance with on-off keying (OOK) modulation. Embodiments are not limited to OOK modulation, however, as any suitable type of modulation may be used. In some embodiments, the AP 102 may encode the MAC header and the payload in accordance with a same data rate (including but not limited to the selected data rate).

[00109] In some embodiments, the AP 102 may encode one or more additional fields, such as a frame check sequence (FCS) and/or other, in accordance with the selected data rate. In some embodiments, the AP 102 may encode the MAC header, the payload, and one or more additional fields, such as a frame check sequence (FCS) and/or other, in accordance with a same data rate (including but not limited to the selected data rate).

[00110] At operation 840, the AP 102 may encode a wake-up preamble. In some embodiments, the wake-up preamble may include a configurable number of preamble sequences to indicate a data rate of the MAC header and the payload. In some embodiments, the wake-up preamble may include a configurable number of preamble sequences to indicate a data rate of one or more elements of the wake-up packet, including but not limited to the MAC header and the payload. In some embodiments, the wake-up preamble may include a configurable number of preamble sequences to indicate a data rate, of a plurality of data rates, used to encode the MAC header and the payload. [00111] In some embodiments, if the MAC header and the payload are encoded in accordance with the first data rate, the wake-up preamble may include a first number of preamble sequences. If the MAC header and the payload are encoded in accordance with a second data rate, the wake-up preamble may include a second number of preamble sequences.

[00112] In some embodiments, the AP 102 may include a first number of preamble sequences in the wake-up preamble to indicate the first data rate, and may further include a second number of preamble sequences in the wake-up packet to indicate the second data rate. In some cases, the second data rate may be less than the first data rate, and the second number of preamble sequences may be greater than the first number of preamble sequences. In a non-limiting example, the first data rate may be 125 kilobits per second (kpbs), the second data rate may be 31.25 kbps, the first number of preamble sequences may be two, and the second number of preamble sequences may be four. In another non-limiting example, the first data rate may be 250 kbps, the second data rate may be 62.5 kbps, the first number of preamble sequences may be one, and the second number of preamble sequences may be two. The two preamble sequences may include two repetitions of a first preamble sequence, in some embodiments. Embodiments are not limited by these example numbers, however, as other numbers may be used in some embodiments.

[00113] In a non-limiting example, the second data rate may be less than the first data rate. The AP 102 may encode the wake-up preamble to include, if the MAC header and the payload are encoded in accordance with the first data rate: a predetermined first preamble sequence, followed by a predetermined second preamble sequence. The AP 102 may encode the wake-up preamble to include, if the MAC header and the payload are encoded in accordance with the second data rate: the first preamble sequence, followed by the second preamble sequence, followed by the first preamble sequence, followed by the second preamble sequence.

[00114] In another non-limiting example, the second data rate may be less than the first data rate. The AP 102 may encode the wake-up preamble to include, if the MAC header and the payload are encoded in accordance with the first data rate: a predetermined first preamble sequence. For instance, a duration of the first preamble sequence may be 64 usee, although embodiments are not limited to this example duration. The AP 102 may encode the wake-up preamble to include, if the MAC header and the payload are encoded in accordance with the second data rate: the first preamble sequence, followed by a second preamble sequence. For instance, a total duration of the first and second preamble sequences may be 128 usee, although embodiments are not limited to this example duration. One or more other values may be used for one or more of the durations described above, in some embodiments.

[00115] In examples and embodiments described herein, various combinations of first and second preamble sequences are possible. In some cases, the first and second preamble sequences may be different. In some cases, the first and second preamble sequences may be the same. In some cases, the first and second preamble sequences may be related. For instance, the second preamble sequence may be based on a logical complement (and/or negation) of the first preamble sequence, in some cases.

[00116] In a non-limiting example, a preamble sequence may be of length equal to an integer power greater than one (such as 2 ^Λ η). For instance, a maximal length sequence (m-sequence) of length equal to the preamble sequence length minus one (such as 2 ^Λ η - 1) may be included in the preamble sequence. The preamble sequence may also include an additional predetermined bit, in some embodiments. The additional bit may be included to "pad" the preamble sequence to a length of 2 ^Λ η, although the scope of embodiments is not limited in this respect. One or more of the preamble sequences may be of the form described above, although the scope of embodiments is not limited in this respect.

[00117] In some embodiments, the second data rate may be less than the first data rate, and the AP 102 may encode the preamble sequences at the first data rate. In some embodiments, the AP 102 may encode the preamble sequences at the first data rate independent of the data rate (first or second) used to encode the MAC header and the preamble. For instance, if the second data rate is used for the MAC header and the preamble, the AP 102 may encode the second number of preamble sequences at the first data rate and may encode the

MAC header and the preamble at the second data rate. If the first data rate is used for the MAC header and the preamble, the AP 102 may encode the first number of preamble sequences at the first data rate and may encode the MAC header and the preamble at the first data rate.

[00118] At operation 845, the AP 102 may encode the wake-up packet. In some embodiments, the AP 102 may encode the wake-up packet to include the wake-up preamble, the MAC header and the payload. In some embodiments, the AP 102 may encode the wake-up packet to include one or more additional elements, such as a legacy preamble (like an 802.1 1 preamble and/or other), an FCS and/or other element(s).

[00119] In some embodiments, the AP 102 may encode the MAC header, the payload, the wake-up preamble and the wake-up packet in accordance with OOK modulation. The scope of embodiments is not limited in this respect, however, as other modulation types may be used in some embodiments.

[00120] At operation 850, the AP 102 may transmit the wake-up packet.

[00121] At operation 855, the AP 102 may transmit downlink data. In some embodiments, the AP 102 may transmit the downlink data in accordance with scheduling information included in the payload of the wake-up packet. In some embodiments, the AP 102 may transmit one or more downlink packets. In some embodiments, the downlink packets may be different than the wake-up packet, although the scope of embodiments is not limited in this respect. For instance, a format, a length, a modulation, content and/or other element(s) of the downlink packets may be different than corresponding elements of the wake-up packet, in some embodiments.

[00122] It should be noted that contention based transmissions (such as transmission of the wake-up packet, transmission of downlink data and/or other) may be used, in some embodiments. In some embodiments, the AP 102 may contend for access to channel resources. In a non-limiting example, the AP 102 may obtain a transmission opportunity (TXOP). The AP 102 may perform one or more downlink transmissions during the TXOP. The AP 102 may schedule one or more uplink transmissions during the TXOP. Embodiments are not limited to this example. Embodiments are also not limited to usage of contention based transmissions. [00123] In some embodiments, an apparatus of an AP 102 may comprise memory. The memory may be configurable to store one or more data rates. The memory may store one or more other elements and the apparatus may use them for performance of one or more operations. In some embodiments, the apparatus of the AP 102 may include a transceiver to transmit the wake-up packet. The transceiver may transmit and/or receive other frames, PPDUs, messages and/or other elements. The apparatus may include processing circuitry, which may perform one or more operations (including but not limited to operation(s) of the method 800 and/or other methods described herein). The processing circuitry may include a baseband processor. The baseband circuitry and/or the processing circuitry may perform one or more operations described herein, including but not limited to encoding of the wake-up packet.

[00124] FIG. 9 illustrates the operation of another method of

communication in accordance with some embodiments. As mentioned previously regarding the method 800, embodiments of the method 900 may include additional or even fewer operations or processes in comparison to what is illustrated in FIG. 9 and embodiments of the method 900 are not necessarily limited to the chronological order that is shown in FIG. 9. In describing the method 900, reference may be made to any of FIGs. 1-13, although it is understood that the method 900 may be practiced with any other suitable systems, interfaces and components. In addition, embodiments of the method 900 may be applicable to STAs 103, APs 102, UEs, eNBs and/or other wireless or mobile devices. The method 900 may also be applicable to an apparatus of an STA 103, AP 102 and/or other device, in some embodiments.

[00125] In some embodiments, a method may include one or more operations. The method may include one or more (or none) of the operations of any of the methods 800, 900. The method may include one or more operations that may be similar to and/or reciprocal to any of the operation(s) of any of the methods 800, 900. In some embodiments, the method may include one or more (or zero) additional operation(s) not shown in FIGs. 8-9.

[00126] It should be noted that the method 800 may be practiced by an AP

102 and may include exchanging of elements, such as frames, signals, messages and/or other elements with an STA 103. The method 900 may be practiced by an STA 103 and may include exchanging of elements, such as frames, signals, messages and/or other elements with an AP 102. In some cases, operations and techniques described as part of the method 800 may be relevant to the method 900. In some cases, operations and techniques described as part of the method 900 may be relevant to the method 800. In addition, embodiments of the method 900 may include one or more operations that may be the same as, similar to or reciprocal to one or more operations of the method 800. For instance, an operation of the method 900 may include reception of an element (such as a message, frame, packet and/or other) by an STA 103 and the method 800 may include transmission of a same or similar element by the AP 102.

[00127] In addition, previous discussion of various techniques, operations and/or concepts may be applicable to the method 900, in some cases, including LP-WUR, the wake-up packet, the elements of the wake-up packet, encoding of the elements of the wake-up packet, the wake-up preamble, preamble sequences, contention based access and/or others.

[00128] At operation 905, the STA 103 may transmit one or more control messages to the AP 102. In some embodiments, the STA 103 may receive one or more control messages from the AP 102. In some embodiments, the STA 103 and the AP 102 may exchange one or more control messages.

[00129] Various information may be included in the control message(s).

Some of the information may be related to LP-WUR operation of the STA 103, in some embodiments. Such information may include, but is not limited to: whether the STA 103 supports LP-WUR operation, a number of data rates supported by the STA 103 for the wake-up packet, one or more data rates supported by the STA 103 for the wake-up packet and/or other information.

These examples will be described in more detail below. In some embodiments, the control message(s) may include information that may not necessarily be related to LP-WUR operation of the STA 103.

[00130] At operation 910, the STA 103 may transmit uplink data to the AP 102. In some embodiments, one or more components of the STA 103 that are separate from the LP-WUR may transmit the uplink data, although the scope of embodiments is not limited in this respect. In some of those embodiments, the STA 103 (and/or apparatus of the STA 103) may include a separate LP- WUR.

[00131] In some embodiments, one or more components of the STA 103 may be configured to transmit the uplink data and may also be configured to receive the wake-up packet. In some of those embodiments, the STA 103 (and/or apparatus of the STA 103) may not necessarily include a separate LP- WUR.

[00132] At operation 915, the STA 103 may receive a wake-up packet from the AP 102. The techniques, arrangements, formats and/or other elements described herein for a wake-up packet may be applicable, although the scope of embodiments is not limited in this respect.

[00133] In some embodiments, the STA 103 may transition to a sleep mode such that it may need to receive a wake-up packet before being ready to receive downlink data at operation 950. The STA 103 may transition to the sleep mode between operations 910 and 915, although the scope of embodiments is not limited in this respect.

[00134] At operation 920, the STA 103 may determine a data rate of a MAC header of the wake-up packet and a payload of the wake-up packet. In some embodiments, the payload may be referred to as a "frame body." In some embodiments, the STA 103 may determine a number of preamble sequences included in a wake-up preamble of the wake-up packet. The number of preamble sequences may be one of: a predetermined first number and a predetermined second number. The STA 103 may determine, based on the number of preamble sequences included in the wake-up packet, a data rate used, by the AP 102, to encode the MAC header and the payload. The first number may correspond to a first data rate. The second number may correspond to a second data rate.

[00135] In some embodiments, the STA 103 may determine the number of preamble sequences included in the wake-up preamble while the STA 103 operates in a sleep mode. The STA 103 may determine the data rate while the STA 103 operates in the sleep mode. The wake-up packet may indicate that the STA 103 is to transition from the sleep mode to an awake mode to receive a downlink transmission from the AP 102. [00136] At operation 925, the STA 103 may decode the MAC header of the wake-up packet. In some embodiments, the STA 103 may decode the MAC header in accordance with the determined data rate.

[00137] At operation 930, the STA 103 may determine whether the wake- up packet is intended for the STA 103. In some embodiments, the STA 103 may determine whether the wake-up packet is intended for the STA 103 based at least partly on an identifier (such as a MAC address, partial MAC address and/or other) included in the MAC header.

[00138] It should be noted that some embodiments may not necessarily include all operations shown in FIG. 9. For instance, if the STA 103 determines that the wake-up packet is not intended for the STA 103, the STA 103 may not necessarily perform other operations of FIG. 9, such as 935, 945, 950 and/or other(s), in some cases. Accordingly, the STA 103 may perform one or more other operations of FIG. 9 (such as 935, 945, 950 and/or other(s)) if it is determined that the wake-up packet is intended for the STA 103, in some cases.

[00139] At operation 935, the STA 103 may decode the payload of the wake-up packet. In some embodiments, the STA 103 may decode the payload in accordance with the determined data rate.

[00140] At operation 940, the STA 103 may remain in a sleep mode. In some embodiments, the STA 103 may remain in the sleep mode if it is determined that the wake-up packet is not intended for the STA 103.

[00141] In some embodiments, the STA 103 may remain in the sleep mode if the STA 103 does not support reception in accordance with the determined data rate. In addition, the STA 103 may not necessarily attempt to decode the MAC header and/or payload if the STA 103 does not support the determined data rate.

[00142] At operation 945, the STA 103 may transition from the sleep mode to an active mode for a downlink data transmission from the AP 102. At operation 950, the STA 103 may receive downlink data from the AP 102. In some embodiments, if it is determined that the wake-up packet is intended for the STA 103, the STA 103 may transition to the awake mode to receive the downlink transmission from the AP 102. [00143] In some embodiments, the STA 103 may detect a predetermined first number of preamble sequences included in a wake-up preamble of a wake- up packet received from the AP 102. The wake-up packet may include either a first number of preamble sequences or a second number of preamble sequences. The second number may be greater than the first number. The first number may indicate that a MAC header of the wake-up packet and a payload of the wake-up packet are encoded at a first data rate. The second number may indicate that the MAC header and the payload are encoded at a second data rate. The second data rate may be less than the first data rate. The STA 103 may attempt to detect one or more additional preamble sequences. If one or more additional preamble sequences are not detected, the STA 103 may determine that the MAC header and the payload are encoded at the first data rate. If one or more additional preamble sequences are detected, the STA 103 may determine that the MAC header and the payload are encoded at the second data rate.

[00144] If it is determined that the MAC header and the payload are encoded at the first data rate, the STA 103 may: decode the MAC header and the payload; and if an identifier of the MAC header indicates that the wake-up packet is intended for the STA 103, transition the STA 103 from a sleep mode to an awake mode to receive downlink data from the AP 102 in accordance with scheduling information included in the payload.

[00145] The STA 103 may, if it is determined that the MAC header and the payload are encoded at the second data rate and if the STA supports reception at the second data rate: decode the MAC header and the payload; and if an identifier of the MAC header indicates that the wake-up packet is intended for the STA 103, transition the STA from a sleep mode to an awake mode to receive downlink data from the AP 102 in accordance with scheduling information included in the payload. The STA 103 may, if it is determined that the MAC header and the payload are encoded at the second data rate and if the STA does not support reception at the second data rate: maintain the STA in the sleep mode.

[00146] FIG. 10 illustrates an example packet in accordance with some embodiments. FIG. 11 illustrates additional example packets in accordance with some embodiments. FIG. 12 illustrates additional example packets in accordance with some embodiments. FIG. 13 illustrates additional example packets in accordance with some embodiments. It should be noted that the examples shown in FIGs. 10-13 may illustrate some or all of the concepts and techniques described herein in some cases, but embodiments are not limited by the examples. For instance, embodiments are not limited by the name, number, type, size, ordering, arrangement and/or other aspects of the operations, packets, frames, sequences, headers, data portions, fields, plots, curves and other elements as shown in FIGs. 10-13. Although some of the elements shown in the examples of FIGs. 10-13 may be included in a standard, such as 802.11, 802.1 lax, WLAN and/or other, embodiments are not limited to usage of such elements that are included in standards.

[00147] In some embodiments, a Low-Power Wake-Up Receiver (LP- WUR) may be used. In some cases, power consumption of a device may be reduced by usage of the LP-WUR and/or LP-WUR techniques. For instance, a low -power solution for a low latency Wi-Fi (or Bluetooth) connectivity of wearable, IoT and other emerging devices may be used. In some embodiments, a simple and low cost, low power hardware solution may be used. Such a solution may be a departure from previous versions of the Wi-Fi standard, in some cases, although the scope of embodiments is not limited in this respect.

[00148] Various implementations of the LP-WUR may be used, including but not limited to those described below. In some embodiments, the STA 103 may receive data, packets, frames, signals and/or other elements while in an active mode, and the STA 103 may also support a sleep mode. Embodiments are not limited by the terms "active mode" and "sleep mode," as other terminology may be used. Terminology such as "normal mode" or other may be used instead of the active mode, in some cases. Terminology such as "inactive mode" or "low power mode" or other may be used instead of the sleep mode, in some cases. In some embodiments, when the STA 103 operates in the sleep mode, a capability to transmit and receive the data, packets, frames, signals and/or other elements may be reduced in comparison to a capability of the STA 103 to receive those same elements while it operates in the active mode.

[00149] In some embodiments, operations of the active mode and the sleep mode may be implemented by a same processing circuitry. In some embodiments, first processing circuitry may implement operations of the active mode and second processing circuitry may implement operations of the sleep mode. In some embodiments, the second processing circuitry may be included in a second component that is separate from a first component that includes the first processing circuitry. The scope of embodiments is not limited by the above examples, however, as any suitable implementation of the operations of the active mode and the operations of the sleep mode may be used.

[00150] In some embodiments, a wake-up packet structure such as the example 1000 shown in FIG. 10 may be used. The wake-up packet (such as 1000 and/or other) may indicate, to the LP-WUR, that the device is to wake up (such as enter the active mode) to receive data. In some embodiments, the STA 103 may detect the wake-up packet 1000, which indicates that the STA 103 is to enter the active mode to receive data. The wake-up packet 1000 may include a preamble 1005 (which may include fields such as STF 1032, LTF 1034, SIG 1036 and/or other element(s)), a wake-up preamble 1010, a MAC header 1015, a payload 1020, FCS 1025 and/or other. In the example wake-up packet 1000, the wake-up preamble 1010 includes two PN sequences 1040. In addition, two values 1045 are also included, but these may be optional, in some cases. In the example wake-up packet 1000, the payload 1020 may include an action ID 1050, an action payload 1055 and/or other element(s). In some embodiments, the payload 1020 may be referred to as a "frame body." The payload 1020 may be replaced by a frame body, in some embodiments.

[00151] In some embodiments, multiple data rates may be possible for portions of the wake-up packet, such as a MAC header, a payload and/or other element(s). In FIG. 11, the example wake-up packet 1100 may signal a data rate used, by the AP 102, to encode the MAC header 1115 and payload 1120. It should also be noted that the signaled data rate may also be used in the FCS 1125, in some embodiments. Various techniques that may be used to signal the data rate are described herein. In some embodiments, the payload 1120 may be referred to as a "frame body." The payload 1120 may be replaced by a frame body, in some embodiments.

[00152] In some embodiments, the wake-up packet may signal one of two predetermined data rates. It should be noted that usage of two data rates is described in some techniques herein, but the scope of embodiments is not limited in this respect. In some cases, techniques for such cases of two data rates may be extended to accommodate more than two data rates. In some embodiments, techniques similar to those used for cases of two data rates may be used for cases in which more than two data rates are used. In a non-limiting example, data rates of 31.25 kbps and 125 kbps may be used for the MAC header 1115 and payload 1120. In another non-limiting example, data rates of 62.5 kbps and 250 kbps may be used for the MAC header 1115 and payload 1120. These example numbers are not limiting, however, as other data rates and/or combinations of data rates are possible.

[00153] In a non-limiting example, a first data rate (such as 31.25 kbps or other data rate) may be used for cases in which an extended range may be provided in comparison to a range of a second data rate. The second data rate (such as 125 kbps or other data rate) may have a shorter transmission time in comparison to a transmission time of the first data rate. In a non-limiting example, the first data rate (the lower data rate of the two data rates) may be used for an 802.1 lb/802.1 lax-extended-range mode, although the scope of embodiments is not limited in this respect.

[00154] In some cases, a pre-negotiation of a data rate (in which one of the data rates of the two is negotiated) may be problematic. For instance, a range between the AP 102 and the STA 103 may change (such as through a change in location of the STA 103) while the STA 103 is in a sleep mode. If the STA 103 in the new location cannot reliably support the negotiated data rate, reception of the MAC header 1115 and payload 1120 may be problematic. Techniques for signaling of the data rate in the wake-up packet may be beneficial in these and other scenarios.

[00155] In some embodiments, two different packet/preamble formats for wake-up packets may be used as a signaling method for the data rate of the wake-up packet (such as for the MAC header, payload and/or other fields). Such a technique may be different from methods of signaling a data rate by using bits of information in a field, in some cases. In some embodiments, the wake-up packet may refrain from usage of a field and/or bits of a field for per packet signaling information of the data rate. [00156] In some embodiments, two data rates may be used for the body (MAC-header and Payload portions) of the wake-up packet: ( 1) a first data rate, and (2) a second data rate (which may be optional in some cases, and may be lower than the first data rate in some cases). It should be noted that descriptions herein may refer to first and second data rates, but such references are not limiting. In a non-limiting example, one of the data rates, such as the first data rate and/or higher data rate (of the two data rates), may be considered a

"mandatory rate" in a standard. The other data rate, such as the second data rate and/or lower data rate (of the two data rates), may be considered an "optional rate" in the standard. The scope of embodiments is not limited by this example. In some embodiments, the first data rate may be considered an "optional rate" while the second data rate may be considered a "mandatory rate".

[00157] In some cases, the first data rate may cover a majority of use cases. In some cases, the first data rate may enable a simple low power hardware implementation. In some cases, the lower data rate may enable deployment in a longer range. In some cases, the lower data rate may be used for relatively difficult deployments. For instance, the lower data rate may be used in a corner case in which a Wi-Fi based temperature sensor (or other device) operates in the corner of a backyard where the indoor AP 102 may need to use 802.1 lb or 802.1 lax Extended-range mode to reach the corner point. To accommodate a lower Rx-sensitivity point, the wake-up packet may be sent at a lower data rate. This example is not limiting, as the lower data rate may be used in various other cases.

[00158] In a non-limiting example, the example wake-up packet 1000 in FIG. 10 may signal that the first data rate (the higher data rate) is used to encode the MAC header 1015, payload 1020 and/or FCS 1025. An example packet such as 1 100 in FIG. 1 1 may signal that the lower data rate is used. In FIG. 1 1, two possibilities are shown. In the example 1 130, the wake-up preamble 1 110 includes 4 repetitions of a sequence 1 140. In the example 1 160, the wake-up preamble 1 1 10 includes 3 repetitions of a sequence 1 170. These examples are not limiting. For instance, any suitable number of repetitions may be used. That number may be part of a specification and/or standard, in some cases. In some embodiments, the number of repetitions may be designed based on a target sensitivity, such as through simulation, analysis and/or other technique(s).

[00159] It should also be noted that embodiments are not limited to sequences of 15 bits, 16 bits, 31 bits, 32 bits or other. Any suitable size may be used for the sequence(s). In some embodiments, a duration of the preamble may be maintained to a value by changing bit durations of the sequences. For example, a 16-bit sequence with bit duration 4 usee may be used to provide 64 usee of preamble duration. Alternatively, a 32-bit sequence with 2 usee bit duration may be used to equivalently provide 64 usee of preamble duration. .

[00160] Referring to FIG. 12, the example wake-up packet 1200 may include the wake-up preamble 1202. One or more additional fields may also be included, including but not limited to the 802.1 1 preamble (legacy preamble (such as an 802.11 preamble and/or other) 1201, MAC header 1203, payload 1204, FCS 1205 and/or other(s). In some embodiments, the payload 1204 may be referred to as a "frame body." The payload 1204 may be replaced by a frame body, in some embodiments. In the example shown in FIG. 12, the wake-up preamble may be configurable as 1210 or 1220, which may be used to indicate two different data rates used to encode the MAC header 1203, payload 1204 and/or FCS 1205. As indicated by 1210, the wake-up preamble 1202 may include two sequences. In this case, the two sequences are a first sequence S I and a second sequence S2 ( 1211 and 1212). As indicated by 1220, the wake-up preamble 1202 may include four sequences. In this case, the four sequences are S I, S2, S I, and S2 ( 1221-1224). Different arrangements are possible. In a non- limiting example, S I and S2 may be the same. In another non-limiting example, S I and S2 may be different sequences. In another non-limiting example, S I and S2 may be logical complements (such as S2 = ~S 1, S2 = NOT(S l) and/or other).

[00161] Any suitable sequences may be used as S I and S2, including but not limited to m-sequences, PN sequences and/or other. In some embodiments, one or more additional bits may be included. For instance, an m-sequence of length equal to (2 ^Λ η - 1) may be padded with one more bit, resulting in a sequence of length equal to 2 ^Λ η. In a non-limiting example, a 15-bit m-sequence may be padded with one bit to produce a 16-bit sequence. In another non- limiting example, a 31-bit m-sequence may be padded with one bit to produce a 32-bit sequence.

[00162] Referring to FIG. 13, the example wake-up packet 1300 may include the wake-up preamble 1302. One or more additional fields may also be included, including but not limited to the 802.11 preamble (legacy preamble (such as an 802.11 preamble and/or other) 1301, MAC header 1303, payload 1304, FCS 1305 and/or other(s). In some embodiments, the payload 1304 may be referred to as a "frame body." The payload 1304 may be replaced by a frame body, in some embodiments. In the example 1300 shown in FIG. 13, the wake- up preamble may be configurable as 1310 or 1320, which may be used to indicate two different data rates used to encode the MAC header 1303, payload 1304 and/or FCS 1305. As indicated by 1310, the wake-up preamble 1302 may include the sequence Tl (indicated by 1311). In a non-limiting example, the sequence Tl may include multiple sequences. For instance, Tl may include a first sequence S I and a second sequence S2, although the scope of embodiments is not limited in this respect. As indicated by 1320, the wake-up preamble 1302 may include the sequences Tl and T2 (as indicated by 1321 and 1322). For instance, T2 may include multiple sequences. In a non-limiting example, Tl and T2 may be the same. In another non-limiting example, T2 may be a logical complement of Tl (such as T2 = ~T1, T2 = NOT(Tl) and/or other).

[00163] Referring to FIG. 13, the example wake-up packet 1350 may include the wake-up preamble 1352. One or more additional fields may also be included, including but not limited to the 802.11 preamble (legacy preamble (such as an 802.11 preamble and/or other) 1351, MAC header 1353, payload 1354, FCS 1355 and/or other(s). In some embodiments, the payload 1354 may be referred to as a "frame body." The payload 1354 may be replaced by a frame body, in some embodiments. In the example 1350 shown in FIG. 13, the wake- up preamble may be configurable as 1360 or 1370, which may be used to indicate two different data rates used to encode the MAC header 1353, payload 1354 and/or FCS 1355. As indicated by 1360, the wake-up preamble 1352 may include (as indicated by 1361) a logical complement of a sequence Tl (such as

~T1, NOT(Tl) and/or other). In a non-limiting example, the sequence Tl may include multiple sequences. For instance, Tl may include a first sequence SI and a second sequence S2, although the scope of embodiments is not limited in this respect. As indicated by 1370, the wake-up preamble 1352 may include two instances of the sequence Tl (as indicated by 1371 and 1372).

[00164] In some embodiments, the AP 102 may encode the wake-up preamble to include one instance of a preamble sequence to indicate a first data rate. The AP 102 may encode the wake-up preamble to include two instances of the preamble sequence to indicate a second data rate. Embodiments are not limited to usage of one instance and two instances to indicate the first and second data rates. Other numbers of instances may be used, in some embodiments. The first data rate may be greater than the second data rate, although the scope of embodiments is not limited in this respect. In a non- limiting example, the first data rate may be 250 kilobits per second (kbps), and the second data rate may be 62.5 kbps.

[00165] In some embodiments, the STA 103 may communicate, to the AP 102, a capability of the STA 103 to support one or more data rates for reception of the MAC header and/or payload. For instance, the STA 103 may indicate one or more of: whether the STA 103 supports the first data rate, whether the STA 103 supports only the first data rate, whether the STA 103 supports the second data rate, whether the STA 103 supports both the first data rate and the second data rate and/or other information. In a non-limiting example, when one additional data rate (in addition to the first data rate) is possible, the STA 103 may indicate, to the AP 102, that it supports 1) reception of the MAC header and payload at the first data rate but not at the second data rate, or 2) reception of the MAC header and payload at the first data rate and at the second data rate.

[00166] In some embodiments, the AP 102 may transmit a wake-up packet at the first data rate for all devices. Based on a previous RSSI measurement (and/or other measurement) for a packet received from the STA 103 (including but not limited to a packet from a main radio of the STA 103), the AP 102 may transmit a wake-up packet using the lower data rate (the second date rate) if the WUR device has indicated that it supports the lower data rate.

Alternatively, for the WUR devices that support the second, lower data rate, the

AP 102 may transmit a first wake-up packet at the first, higher data rate. If the

AP 102 detects an error (for instance, if the AP 102 does not receive a packet from the main radio of the STA 103 after a time-out duration), then the AP 102 may retransmit the wake-up packet at the second, lower data rate. This technique may enable a rate scaling mechanism for the AP 102, in some cases.

[00167] In some embodiments, the STA 103 may attempt to detect a wake-up packet. In some embodiments, a wake-up receiver (WUR) of the STA 103 may attempt to detect the wake-up packet. If the WUR supports reception (of the MAC header and payload) at both data rates, different implementations are possible. Some implementations may use parallel hardware. Some implementations may use a serial approach that may include buffering.

[00168] A non-limiting example of an implementation that uses the serial approach is described below, but it is understood that one or more of the techniques and/or operations described in this example may be used in implementations that may not necessarily use the serial approach. In the example, it is assumed that two preamble sequences (# 1 and #2) are used to signal the first, higher data rate and that four preamble sequences (#1, #2, #3 and #4) are used to signal the second, lower data rate. The WUR may search for (and/or attempt to detect) the first two preamble sequences (#1 and #2). The WUR may accumulate samples beyond the first two preamble sequences, and may further search for (and/or attempt to detect) the next two preamble sequences (#3 and #4) in the accumulated samples.

[00169] Continuing the above example, if the WUR determines that the four preamble sequences (#1, #2, #3 and #4) are included, the WUR may determine that the second, lower data rate is used for the MAC header and payload. The WUR may determine that samples accumulated after the final preamble sequence (#4) are to be accumulated and used to decode the MAC header and payload.

[00170] Continuing the above example, if the WUR determines that the first two preamble sequences (# 1 and #2) are included but the second two preamble sequences (#3 and #4) are not included, the WUR may determine that the first, higher data rate is used for the MAC header and payload. The WUR may use the accumulated samples (and perhaps subsequent samples) to decode the MAC header and payload. In some cases, usage of the above techniques may enable auto-classification, by the WUR, between two rates. [00171] In some embodiments, the STA 103 may attempt to detect a wake-up packet. In some embodiments, a wake-up receiver (WUR) of the STA 103 may attempt to detect the wake-up packet. If the WUR supports reception (of the MAC header and payload) at the first, higher data rate but not at the second, lower data rate, different implementations are possible. Some implementations may use parallel hardware. Some implementations may use a serial approach that may include buffering. The WUR may attempt to detect two or more preamble sequences by accumulating and buffering enough samples. The WUR may detect two preamble sequences (such as #1 and #2). Once the two preamble sequences are detected, the WUR may continue to accumulate samples. The WUR may use the accumulated samples to 1) attempt to decode the body portion of the wake-up packet and 2) attempt to detect additional preamble sequences. If a third preamble is detected, the WUR may determine that the lower data rate is used. As the device does not support the lower data rate, in this example, the WUR device may abandon processing of the remainder of the packet. In some embodiments, when the complement of the sequence is used (including but not limited to the example 1350 in FIG. 13), the need for buffering may be eliminated (or at least reduced) by examining the sign of correlation because correlating with the same sequence Tl gives a positive value while correlating by the complement Tl gives a negative value. Therefore when correlation is positive, the receiver may determine to continue to receive the second portion of the preamble sequence Tl .

[00172] In some embodiments, a convolutional encoder (such as .11 BCC and/or other) may be used in conjunction with the lower data rate (such as on the MAC header and payload). In some embodiments, the WUR (which may be of relatively low complexity or relatively low power) may not necessarily implement a Viterbi decoder. While this WUR is not capable of decoding at the lower data rate, it may still enabled for auto-classification of the data rate, and can terminate the receive procedure as soon as the lower data rate is detected. In some cases, early termination of the receive procedure may further reduce receive processing power and may enable the WUR device to go back to sleep mode (in cases in which duty cycling is enabled for the WUR device). [00173] In Example 1, an apparatus of an access point (AP) may comprise memory. The apparatus may further comprise processing circuitry. The processing circuitry may be configured to select, from first and second data rates, a data rate for a wake-up packet to indicate that a station (STA) is to transition from a sleep mode to an awake mode for a downlink data transmission from the AP. The processing circuitry may be further configured to encode a medium access control (MAC) header to include an identifier of the STA, the MAC header encoded in accordance with the selected data rate. The processing circuitry may be further configured to encode a payload in accordance with the selected data rate. The processing circuitry may be further configured to encode a wake-up preamble to include a configurable number of preamble sequences to indicate a data rate of the MAC header and the payload. A first number of preamble sequences may indicate the first data rate and a second number of preamble sequences may indicate the second data rate. The processing circuitry may be further configured to encode, for transmission, the wake-up packet to include the wake-up preamble, the MAC header and the payload.

[00174] In Example 2, the subject matter of Example 1, wherein the processing circuitry may be further configured to determine a signal quality measurement based at least partly on an uplink data transmission from the STA. The processing circuitry may be further configured to select the data rate based at least partly on the signal quality measurement.

[00175] In Example 3, the subject matter of one or any combination of

Examples 1-2, wherein the second data rate may be less than the first data rate. The processing circuitry may be further configured to select the first data rate if the signal quality measurement is greater than a predetermined threshold. The processing circuitry may be further configured to select the second data rate if the signal quality measurement is less than or equal to the predetermined threshold.

[00176] In Example 4, the subject matter of one or any combination of Examples 1-3, wherein the second data rate may be less than the first data rate. The second number of preamble sequences may be greater than the first number of preamble sequences. [00177] In Example 5, the subject matter of one or any combination of

Examples 1-4, wherein the first data rate may be 125 kilobits per second (kbps). The second data rate may be 31.25 kbps. The first number of preamble sequences may be two. The second number of preamble sequences may be four.

[00178] In Example 6, the subject matter of one or any combination of

Examples 1-5, wherein the first data rate may be 250 kilobits per second (kbps). The second data rate may be 62.5 kbps. The first number of preamble sequences may be one. The second number of preamble sequences may be two. The processing circuitry may be further configured to encode the wake-up preamble to include one instance of a predetermined preamble sequence to indicate the first data rate. The processing circuitry may be further configured to encode the wake-up preamble to include two instances of the predetermined preamble sequence to indicate the second data rate.

[00179] In Example 7, the subject matter of one or any combination of Examples 1-6, wherein the second data rate may be less than the first data rate. The processing circuitry may be further configured to encode the wake-up preamble to include: if the MAC header and the pay load are encoded in accordance with the first data rate, a predetermined first preamble sequence, followed by a predetermined second preamble sequence; and if the MAC header and the payload are encoded in accordance with the second data rate, the first preamble sequence, followed by the second preamble sequence, followed by the first preamble sequence, followed by the second preamble sequence.

[00180] In Example 8, the subject matter of one or any combination of

Examples 1-7, wherein the second preamble sequence may be based on a logical complement of the first preamble sequence.

[00181] In Example 9, the subject matter of one or any combination of

Examples 1-8, wherein at least one of the preamble sequences: is of a preamble sequence length equal to two raised to an integer power greater than one, includes a maximal length sequence (m-sequence) of length equal to the preamble sequence length minus one, and further include one additional predetermined bit.

[00182] In Example 10, the subject matter of one or any combination of

Examples 1-9, wherein the second data rate may be less than the first data rate. The processing circuitry may be further configured to encode the first number of preamble sequences at the first data rate. The processing circuitry may be further configured to encode the second number of preamble sequences at the first data rate.

[00183] In Example 1 1, the subject matter of one or any combination of

Examples 1-10, wherein the identifier of the STA may be a MAC address or a partial MAC address.

[00184] In Example 12, the subject matter of one or any combination of

Examples 1- 11, wherein the processing circuitry may be further configured to encode the MAC header, the payload, the wake-up preamble and the wake-up packet in accordance with an on-off keying (OOK) modulation.

[00185] In Example 13, the subject matter of one or any combination of

Examples 1-12, wherein the processing circuitry may be further configured to encode the payload to include scheduling information for the downlink data transmission. The processing circuitry may be further configured to encode downlink data for transmission in accordance with the scheduling information included in the payload.

[00186] In Example 14, the subject matter of one or any combination of

Examples 1-13, wherein the processing circuitry may be further configured to decode, from the STA, a control message that indicates whether the STA supports reception at the first data rate and whether the STA supports reception at the second data rate. The processing circuitry may be further configured to select the data rate based at least partly on the control message.

[00187] In Example 15, the subject matter of one or any combination of Examples 1-14, wherein the apparatus may further include a transceiver to transmit the wake-up packet.

[00188] In Example 16, the subject matter of one or any combination of

Examples 1-15, wherein the processing circuitry may include a baseband processor to encode the wake-up packet.

[00189] In Example 17, the subject matter of one or any combination of

Examples 1- 16, wherein the memory is configured to store the selected data rate.

[00190] In Example 18, a computer-readable storage medium may store instructions for execution by one or more processors to perform operations for communication by a station (STA). The operations may configure the one or more processors to determine a number of preamble sequences included in a wake-up preamble of a wake-up packet received from an access point (AP). The number of preamble sequences may be one of: a predetermined first number and a predetermined second number. The operations may further configure the one or more processors to determine, based on the number of preamble sequences included in the wake -up packet, a data rate used, by the AP, to encode a medium access control (MAC) header of the wake-up packet and a payload of the wake- up packet. The first number may correspond to a first data rate. The second number may correspond to a second data rate.

[00191] In Example 19, the subject matter of Example 18, wherein the one or more processors may be included in a low-power wake-up receiver (LP- WUR) of the STA.

[00192] In Example 20, the subject matter of one or any combination of Examples 18- 19, wherein the operations may further configure the one or more processors to determine the number of preamble sequences included in the wake- up preamble while the STA operates in a sleep mode. The operations may further configure the one or more processors to determine the data rate while the STA operates in the sleep mode. The wake-up packet may indicate that the STA is to transition from the sleep mode to an awake mode to receive a downlink transmission from the AP.

[00193] In Example 21, the subject matter of one or any combination of

Examples 18-20, wherein the operations may further configure the one or more processors to decode the MAC header and the payload in accordance with the determined data rate. The operations may further configure the one or more processors to determine, based on an identifier included in the MAC header, whether the wake-up packet is intended for the STA. The operations may further configure the one or more processors to, if it is determined that the wake- up packet is intended for the STA, transition the STA to the awake mode to receive the downlink transmission from the AP. The operations may further configure the one or more processors to, if it is determined that the wake-up packet is not intended for the STA, maintain the STA in the sleep mode. [00194] In Example 22, the subject matter of one or any combination of

Examples 18-21, wherein the second number may be greater than the first number. The second data rate may be less than the first data rate.

[00195] In Example 23, a method of communication at an access point (AP) may comprise encoding a medium access control (MAC) header to include an identifier of a station (STA) for which a downlink transmission is scheduled. The method may further comprise encoding a payload to include scheduling information for the downlink data transmission. The method may further comprise encoding a wake-up preamble to include a configurable number of preamble sequences to indicate a data rate, of a plurality of data rates, used to encode the MAC header and the payload. If the MAC header and the payload are encoded in accordance with a first data rate, the wake-up preamble may include a first number of preamble sequences. If the MAC header and the payload are encoded in accordance with a second data rate, the wake-up preamble may include a second number of preamble sequences. The method may further comprise encoding, for transmission, the wake-up packet to include the wake-up preamble, the MAC header and the payload.

[00196] In Example 24, the subject matter of Example 23, wherein if the

MAC header and the payload are encoded in accordance with a first data rate, the wake-up preamble may include a first preamble sequence. If the MAC header and the payload are encoded in accordance with a second data rate, the wake-up preamble may include a second preamble sequences that comprises: two repetitions of the first preamble sequence, or two repetitions of a logical complement of the first preamble sequence.

[00197] In Example 25, the subject matter of one or any combination of

Examples 23-24, wherein a duration of the second preamble sequence may be equal to a product of two and a duration of the first preamble sequence.

[00198] In Example 26, the subject matter of one or any combination of

Examples 23-25, wherein the method may further comprise encoding the wake- up packet to indicate that the STA is to transition from a sleep mode to an awake mode for the downlink data transmission.

[00199] In Example 27, the subject matter of one or any combination of

Examples 23-26, wherein the method may further comprise selecting a data rate of the plurality to be used to encode the MAC header and the payload. The method may further comprise encoding the MAC header in accordance with the selected data rate. The method may further comprise encoding the payload in accordance with the selected data rate.

[00200] In Example 28, an apparatus of a station (STA) may comprise memory. The apparatus may further comprise processing circuitry. The processing circuitry may be configured to detect a predetermined first number of preamble sequences included in a wake-up preamble of a wake-up packet received from an access point (AP). The wake-up packet may include either a first number of preamble sequences or a second number of preamble sequences. The second number may be greater than the first number. The first number may indicate that a medium access control (MAC) header of the wake-up packet and a payload of the wake-up packet are encoded at a first data rate. The second number may indicate that the MAC header and the payload are encoded at a second data rate, the second data rate less than the first data rate. The processing circuitry may be further configured to attempt to detect one or more additional preamble sequences. The processing circuitry may be further configured to, if one or more additional preamble sequences are not detected: determine that the MAC header and the payload are encoded at the first data rate. The processing circuitry may be further configured to, if one or more additional preamble sequences are detected: determine that the MAC header and the payload are encoded at the second data rate. The memory may be configured to store at least a portion of the wake-up packet.

[00201] In Example 29, the subject matter of Example 28, wherein the processing circuitry may be further configured to, if it is determined that the

MAC header and the payload are encoded at the first data rate: decode the MAC header and the payload; and if an identifier of the MAC header indicates that the wake-up packet is intended for the STA, transition the STA from a sleep mode to an awake mode to receive downlink data from the AP in accordance with scheduling information included in the payload.

[00202] In Example 30, the subject matter of one or any combination of

Examples 28-29, wherein the processing circuitry may be further configured to: if it is determined that the MAC header and the payload are encoded at the second data rate and if the STA supports reception at the second data rate: decode the MAC header and the payload; and if an identifier of the MAC header indicates that the wake-up packet is intended for the STA, transition the STA from a sleep mode to an awake mode to receive downlink data from the AP in accordance with scheduling information included in the payload. The processing circuitry may be further configured to, if it is determined that the MAC header and the payload are encoded at the second data rate and if the STA does not support reception at the second data rate: maintain the STA in the sleep mode.

[00203] In Example 31, an apparatus of a station (STA) may comprise means for determining a number of preamble sequences included in a wake-up preamble of a wake-up packet received from an access point (AP). The number of preamble sequences may be one of: a predetermined first number and a predetermined second number. The apparatus may further comprise means for determining, based on the number of preamble sequences included in the wake- up packet, a data rate used, by the AP, to encode a medium access control

(MAC) header of the wake-up packet and a payload of the wake-up packet. The first number may correspond to a first data rate. The second number may correspond to a second data rate.

[00204] In Example 32, the subject matter of Example 31, wherein the apparatus may be included in a low-power wake-up receiver (LP-WUR) of the STA.

[00205] In Example 33, the subject matter of one or any combination of

Examples 31-32, wherein the apparatus may further comprise means for determining the number of preamble sequences included in the wake-up preamble while the STA operates in a sleep mode. The apparatus may further comprise means for determining the data rate while the STA operates in the sleep mode. The wake-up packet may indicate that the STA is to transition from the sleep mode to an awake mode to receive a downlink transmission from the AP.

[00206] In Example 34, the subject matter of one or any combination of

Examples 31-33, wherein the apparatus may further comprise means for decoding the MAC header and the payload in accordance with the determined data rate. The apparatus may further comprise means for determining, based on an identifier included in the MAC header, whether the wake-up packet is intended for the STA. The apparatus may further comprise means for, if it is determined that the wake-up packet is intended for the STA: transitioning the STA to the awake mode to receive the downlink transmission from the AP. The apparatus may further comprise means for, if it is determined that the wake-up packet is not intended for the STA: maintaining the STA in the sleep mode.

[00207] In Example 35, the subject matter of one or any combination of

Examples 31-34, wherein the second number may be greater than the first number. The second data rate may be less than the first data rate.

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

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