Patent Description:
In recent years, applications have been developed relating to social networking, Internet of Things (IoT), wireless docking, and the like. It may be desirable to design low power solutions that can be always-on. However, constantly providing power to a wireless local area network (WLAN) radio may be expensive in terms of battery life. Document <CIT> discloses methods and stations for wireless communication, the station may include a processing circuit configured to process a first signal transmitted to the station, the first signal indicating a target up time when an activation signal is expected to be received.

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.

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

Referring to <FIG>, the network <NUM> may include any or all of the components shown, and embodiments are not limited to the number of each component shown in <FIG>. In some embodiments, the network <NUM> may include a master station (AP) <NUM> and may include any number (including zero) of stations (STAs) <NUM> and/or HEW devices <NUM>. In some embodiments, the AP <NUM> may transmit a trigger frame (TF) to an STA <NUM> to indicate that the STA <NUM> is to perform an uplink data transmission to the AP. In some embodiments, the AP <NUM> may transmit downlink data packets to the STA <NUM>, and the STA <NUM> may transmit a block acknowledgement (BA) message for the downlink data packets. These embodiments will be described in more detail below.

The AP <NUM> may be arranged to communicate with one or more of the components shown in <FIG> in accordance with one or more IEEE <NUM> standards (including <NUM>. 11ax and/or others), other standards and/or other communication protocols. It should be noted that embodiments are not limited to usage of an AP <NUM>. References herein to the AP <NUM> are not limiting and references herein to the master station <NUM> are also not limiting. In some embodiments, a STA <NUM>, HEW device <NUM> 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 <NUM> as described herein may be performed by the STA <NUM>, HEW device <NUM> and/or other device that is configurable to operate as the master station.

In some embodiments, one or more of the STAs <NUM> may be legacy stations. These embodiments are not limiting, however, as the STAs <NUM> may be configured to operate as HEW devices <NUM> or may support HEW operation in some embodiments. The master station <NUM> may be arranged to communicate with the STAs <NUM> and/or the HEW stations <NUM> in accordance with one or more of the IEEE <NUM> standards, including <NUM>. 11ax and/or others. In accordance with some HEW embodiments, an access point (AP) may operate as the master station <NUM> 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 HEW control period (i.e., a transmission opportunity (TXOP)). The master station <NUM> may, for example, transmit a master-sync or control transmission at the beginning of the HEW control period to indicate, among other things, which HEW stations <NUM> are scheduled for communication during the HEW control period. During the HEW control period, the scheduled HEW stations <NUM> may communicate with the master station <NUM> 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 HEW control period, the master station <NUM> may communicate with HEW stations <NUM> using one or more HEW frames. During the HEW control period, STAs <NUM> not operating as HEW 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.

In some embodiments, the multiple-access technique used during the HEW 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. These multiple-access techniques used during the HEW control period may be configured for uplink or downlink data communications.

The master station <NUM> may also communicate with STAs <NUM> and/or other legacy stations in accordance with legacy IEEE <NUM> communication techniques. In some embodiments, the master station <NUM> may also be configurable to communicate with the HEW stations <NUM> outside the HEW control period in accordance with legacy IEEE <NUM> communication techniques, although this is not a requirement.

In some embodiments, the HEW communications during the control period may be configurable to use one of <NUM>, <NUM>, or <NUM> contiguous bandwidths or an <NUM>+<NUM> (<NUM>) non-contiguous bandwidth. In some embodiments, a <NUM> channel width may be used. In some embodiments, sub-channel bandwidths less than <NUM> may also be used. In these embodiments, each channel or sub-channel of an HEW communication may be configured for transmitting a number of spatial streams.

In some embodiments, high-efficiency wireless (HEW) techniques may be used, although the scope of embodiments is not limited in this respect. As an example, techniques included in <NUM>. 11ax standards and/or other standards may be used. In accordance with some embodiments, a master station <NUM> and/or HEW stations <NUM> may generate an HEW packet in accordance with a short preamble format or a long preamble format. The HEW packet may comprise a legacy signal field (L-SIG) followed by one or more high-efficiency (HE) signal fields (HE-SIG) and an HE long-training field (HE-LTF). For the short preamble format, the fields may be configured for shorter-delay spread channels. For the long preamble format, the fields may be configured for longer-delay spread channels. These embodiments are described in more detail below. 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.

Embodiments described herein may be implemented into a system using any suitably configured hardware and/or software.

<FIG> illustrates a block diagram of an example machine in accordance with some embodiments. The machine <NUM> is an example machine upon which any one or more of the techniques and/or methodologies discussed herein may be performed. The machine <NUM> may be an AP <NUM>, STA <NUM>, HEW device, HEW AP, HEW STA, UE, 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.

Examples as described herein, may include, or may operate on, logic or a number of components, modules, or mechanisms.

The machine (e.g., computer system) <NUM> may include a hardware processor <NUM> (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory <NUM> and a static memory <NUM>, some or all of which may communicate with each other via an interlink (e.g., bus) <NUM>. The machine <NUM> may include an output controller <NUM>, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).

In some embodiments, the machine readable medium may be or may include a non-transitory computer-readable storage medium. In some embodiments, the machine readable medium may be or may include a computer-readable storage medium.

The term "machine readable medium" may include any medium that is capable of storing, encoding, or carrying instructions for execution by the machine <NUM> and that cause the machine <NUM> 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; magnetooptical 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.

The instructions <NUM> may further be transmitted or received over a communications network <NUM> using a transmission medium via the network interface device <NUM> 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) <NUM> family of standards known as Wi-Fi®, IEEE <NUM> family of standards known as WiMax®), IEEE <NUM>. <NUM> family of standards, a Long Term Evolution (LTE) family of standards, a Universal Mobile Telecommunications System (UNITS) family of standards, peer-to-peer (P2P) networks, among others. In an example, the network interface device <NUM> 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 <NUM>. In an example, the network interface device <NUM> 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 <NUM> 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 <NUM>, and includes digital or analog communications signals or other intangible medium to facilitate communication of such software.

<FIG> 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 some or all of the components shown in either <FIG> or <FIG> (as in <NUM>) or both. The STA <NUM> may be suitable for use as an STA <NUM> as depicted in <FIG>, in some embodiments. It should also be noted that in some embodiments, an AP or other base station may include some or all of the components shown in either <FIG> or <FIG> (as in <NUM>) or both. The AP <NUM> may be suitable for use as an AP <NUM> as depicted in <FIG>, in some embodiments.

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

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

The antennas <NUM>, <NUM>, <NUM> 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 <NUM>, <NUM>, <NUM> may be effectively separated to take advantage of spatial diversity and the different channel characteristics that may result.

In some embodiments, the STA <NUM> may be configured as an HEW device <NUM> (<FIG>), and may communicate using OFDM and/or OFDMA communication signals over a multicarrier communication channel. In some embodiments, the AP <NUM> may be configured to communicate using OFDM and/or OFDMA communication signals over a multicarrier communication channel. In some embodiments, the HEW device <NUM> may be configured to communicate using OFDM communication signals over a multicarrier communication channel. Accordingly, in some cases, the STA <NUM>, AP <NUM> and/or HEW device <NUM> 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 <NUM>-<NUM>, <NUM>. 11n-<NUM> and/or <NUM>. 11ac-<NUM> standards and/or proposed specifications for WLANs including proposed HEW standards, 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 <NUM>, HEW device <NUM> and/or the STA <NUM> configured as an HEW device <NUM> 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. Embodiments disclosed herein provide two preamble formats for High Efficiency (HE) Wireless LAN standards specification that is under development in the IEEE Task Group 11ax (TGax).

In some embodiments, the STA <NUM> and/or AP <NUM> 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 <NUM> and/or AP <NUM> may be configured to operate in accordance with <NUM> 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 <NUM> and/or AP <NUM> 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.

Although the STA <NUM> and the AP <NUM> 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.

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.

It should be noted that in some embodiments, an apparatus used by the STA <NUM> may include various components of the STA <NUM> as shown in <FIG> and/or the example machine <NUM> as shown in <FIG>. Accordingly, techniques and operations described herein that refer to the STA <NUM> (or <NUM>) may be applicable to an apparatus for an STA, in some embodiments. It should also be noted that in some embodiments, an apparatus used by the AP <NUM> may include various components of the AP <NUM> as shown in <FIG> and/or the example machine <NUM> as shown in <FIG>. Accordingly, techniques and operations described herein that refer to the AP <NUM> (or <NUM>) may be applicable to an apparatus for an AP, in some embodiments. In addition, an apparatus for a mobile device and/or base station may include one or more components shown in <FIG>, 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 for a mobile device and/or base station, in some embodiments.

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

<FIG> illustrates an example system <NUM> in which a low-power wake-up radio is operated. As shown, the system <NUM> includes a transmitter <NUM> and a receiver <NUM>. The transmitter <NUM> may be a WLAN station (e.g., Wi-Fi router) and the receiver <NUM> may be a computing device capable of connecting to the WLAN station, such as a mobile phone, a tablet computer, a laptop computer, a desktop computer, and the like. The transmitter <NUM> includes an WLAN (<NUM>+) radio <NUM>. The receiver <NUM> includes a WLAN (<NUM>) radio <NUM> (e.g., Wi-Fi radio) and a LP-WUR <NUM>. The WLAN radio <NUM> of the transmitter <NUM> transmits one or more wake-up packets <NUM>. One of the wake-up packets <NUM> is received at the LP-WUR <NUM> of the receiver <NUM>. Upon receiving the wake-up packet <NUM>, the LP-WUR <NUM> sends a wake-up signal <NUM>, which causes the WLAN radio <NUM> of the receiver <NUM> to turn on. The WLAN radio <NUM> of the transmitter <NUM> transmits data packet(s) <NUM> to the WLAN radio <NUM> of the receiver <NUM>, and the WLAN radio <NUM> of the receiver <NUM> receives the data packet(s) <NUM>.

As illustrated in <FIG>, LP-WUR relates to a technique to enable ultra-low power operation for a Wi-Fi device (e.g., receiver <NUM>). The idea is for the device to have a minimum radio configuration (e.g., LP-WUR <NUM>) that can receive a wake-up packet <NUM> from the peer (e.g., transmitter <NUM>). Hence, the device can stay in low power mode until receiving the wake-up packet <NUM>.

The receiver <NUM> of the wake-up packet <NUM> may negotiate with the transmitter <NUM> of wake-up packet <NUM> before the receiver <NUM> enables the LP-WUR mode. Hence, the transmitter <NUM> knows the agreed bandwidth and channel in which to transmit the wake-up packet, the identification in the wake-up packet, and other related information. In some cases, the transmitter <NUM> may also send a response action frame with information to the receiver <NUM> before the receiver <NUM> enables the LP-WUR mode.

The receiver <NUM> of the wake-up packet <NUM> may inform the transmitter <NUM> of wake-up packet <NUM> before the receiver <NUM> enables the LP-WUR mode and turns off the WLAN radio <NUM>. Hence, the transmitter <NUM> knows that wake-up packet <NUM> is allowed to transmit to the receiver <NUM>. In some cases, the transmitter <NUM> may also send a response action frame with information to the receiver <NUM> before the receiver <NUM> enables the LP-WUR mode.

On the other hand, the transmitter <NUM> may be AP that regulates the power save operation in the base station subsystem (BSS). The receiver <NUM> may be a senor, which has simple design and relies on AP to decide the power save mode. As a result, the AP may request the receiver <NUM> to enable or enable the LP-WUR mode, and the receiver <NUM> provides a response action frame accepting the request.

Some aspects of the subject technology devein the LP-WUR request frame and response action frame. The LP-WUR request frame and response action frame may be similar to the wireless network management (WNM) sleep mode request/ response in the Institute of Electrical and Electronics Engineers (IEEE) <NUM> specification.

In a BSS, the LP-WUR request frame can be sent by the non-AP STA or the AP STA. Then, the LP-WUR response action frame is sent by the AP STA or non-AP STA to accept/reject the request in the request frame. Examples are shown in <FIG> illustrate communications between an AP <NUM> and a STA <NUM>.

<FIG> is a data flow diagram illustrating an example method 500A of the AP <NUM> requesting for the STA <NUM> to enable an LP-WUR mode, in accordance with some embodiments. At operation 510A, the AP <NUM> transmits to the STA <NUM> an LP-WUR request frame requesting for the STA <NUM> to enable the LP-WUR mode. At operation <NUM>, the STA <NUM> transmits to the AP <NUM> the LP-WUR response action frame indicating that the STA <NUM> accepts the request in the request frame.

<FIG> is a data flow diagram illustrating an example method 500B of the STA <NUM> requesting to enable an LP-WUR mode from the AP <NUM>. At operation 510B, the STA <NUM> transmits to the AP <NUM> a request frame to enable the LP-WUR mode. At operation 520B, the AP <NUM> transmits to the STA <NUM> the LP-WUR response action frame indicating that the AP <NUM> accepts the request in the request frame.

Some aspects of the subject technology enable the request frame to be sent from the AP <NUM> to allow a simple sensor at the STA <NUM> to give full control to the AP <NUM>. Some aspects of the subject technology define additional information that may be placed in the request frame or the response action frame.

Aspects of the subject technology differentiate two procedures for LP-WUR. To enable/ enable LP-WUR mode, a pair of STAs negotiate/setup the LP-WUR parameters and procedure. To enable LP-WUR mode, the wake-up packet receiver negotiates with the wake-up packet transmitter about the wake-up packet transmission parameters and related information. To enable the LP-WUR mode, the wake-up packet receiver informs the wake-up packet transmitter that the receiver has turned off <NUM> radio and has turned on the LP-WUR receiver on so that the transmitter can start to send the wake-up packet when the receiver needs to be waked up.

Aspects of the subject technology define the LP-WUR request frame and response action frame negotiation for a pair of STAs. The LP-WUR request frame and response action frame can be used by a pair of STAs to enable or enable LP-WUR mode. To enable LP-WUR mode, the LP-WUR request can be used by a STA to indicate if the STA itself (or a peer STA) is going to turn off the <NUM> radio and have the LP-WUR receiver turned on.

In some cases, STA1 is the wake-up packet transmitter (e.g., transmitter <NUM>) and STA2 is the wake-up packet receiver (e.g., receiver <NUM>). Aspects of the subject technology define two procedures for STA1 and STA2 to enable LP-WUR modes.

According to a first procedure, STA2 sends the LP-WUR request to STA1 in order to request for enabling LP-WUR mode between STA1 and STA2. STA1 sends the LP-WUR response in response to the request from STA2 to enable the LP-WUR mode between STA1 and STA2. STA2 enables the LP-WUR mode after receiving the response which indicates acceptance. STA2 does not enables the LP-WUR mode after receiving the response which indicates rejection. If the response indicates acceptance, STA1 enables the LP-WUR mode after receiving, from STA2, an acknowledgement (ACK) for the LP-WUR response.

According to a second procedure, STA1 sends the LP-WUR request to request STA2 to enables the LP-WUR mode between STA1 and STA2. In response to the request from STA1, STA2 sends an LP-WUR response indicating acceptance or rejection. If the response indicates acceptance, STA1 enables the LP-WUR mode and STA2 enables the LP-WUR. mode after receiving an ACK of the response from STA1. If the response indicates rejection, STA2 does not enable the LP-WUR mode.

The first and second procedures, set forth above, may be differentiated by an explicit approach where one bit in the LP-WUR request indicates if the requester is the wake-up packet transmitter or receiver. Alternatively, an implicit approach may be used. According to the implicit approach: (i) if the request is sent from a non-AP STA to an AP STA, then the request is a self-request for the non-AP STA to be a wake-up packet receiver; and (ii) if the request is sent from an AP STA to a non-AP STA, then the request is a request for the non-AP STA to be a wake-up packet receiver. It should be noted that the implicit approach may not work for peer-to-peer (e.g., device-to-device or sidelink) situations.

Aspects of the subject technology define further information that can be sent in the LP-WUR request frame and response action frame. Specifically, an element associated with the request frame or the response action frame may be defined for LP-WUR.

The element may include STA2 identification in the wake-up packet. The identification may be placed in the LP-WUR request frame or response action frame from STA1.

The element may include STA1 identification in the wake-up packet. The identification may be placed in the LP-WUR request frame or response action frame from STA1. If STA1 is the access point, then the identification may be the BSS color.

The element may include broadcast identification in the wake-up packet. The identification for every STA (negotiated LP-WUR mode with the wake up packet transmitter) may be placed in the wake-up packet. The identification may be placed in the LP-WUR request frame or response action frame from STA1. If specific station IDs are assigned during the request frame or response action frame from STA1, then the broadcast identification may be an all <NUM> flag or all <NUM> flag.

The element may include group identification in the wake-up packet. The identification for a group of STAs (negotiated LP-WUR mode with the wake up packet transmitter) may be placed in the wake up packet. The identification may be placed in the LP-WUR request frame or response action frame from STA1.

The element may include the time for STA2 to turn the <NUM> radio (e.g., <NUM> radio <NUM>) from off to on after receiving the wake-up packet at the LP-WUR (e.g., LP-WUR <NUM>). The time may be placed in the request frame or response action frame from STA2. The required time may be indicated when STA1 and STA2 exchange LP-WUR capability information during association.

The element may include identification of STA2 requirements regarding the wake-up packet from STA1. STA2 requirements regarding the wake-up packet from STA1 may be placed in the LP-WUR request frame or response action frame.

The element may include STA2 periodic wake-up interval information for STA2 to periodically wake up the WLAN radio of STA2. The STA2 periodic wake-up interval information may be placed in the LP-WUR request frame or response action frame from STA2. Alternatively, the STA2 periodic wake-up interval information may be placed in the LP-WUR request frame or response action frame from STA1. The unit of the periodic wake-up interval may be a delivery traffic indication message (DTIM) beacon interval or a beacon interval. The STA2 periodic wake-up interval information may include an indication of the number of times for periodic wake-up.

Claim 1:
An apparatus of a wake-up radio, WUR, non-access point, non-AP, station, STA, (<NUM>), the apparatus comprising: memory; and processing circuitry, the processing circuitry comprising a primary connectivity radio, PCR, (<NUM>) and a WUR receiver (<NUM>), the PCR (<NUM>) comprising a wireless local area network, WLAN, radio, the processing circuitry configured to:
encode a request frame (510B) for transmission to a WUR access point, AP, station, STA, (<NUM>), the request frame (510B) including a request to the WUR AP STA (<NUM>) for the WUR non-AP STA (<NUM>) to enter a WUR mode;
the request frame (510B) further encoded to indicate a transition delay for the WUR non-AP STA (<NUM>) to turn on the PCR (<NUM>) in response to the WUR non-AP STA (<NUM>) receiving a wake-up frame (<NUM>);
configure the non-AP STA (<NUM>) to transmit the request frame (510B);
decode a response frame (520B) from the WUR AP STA (<NUM>), the response frame (520B) indicating acceptance or denial of the request; and
decode a wake-up frame (<NUM>) from the WUR AP STA (<NUM>), wherein the WUR receiver (<NUM>) is configured to turn on the PCR (<NUM>) in response to the decoding of the wake-up frame (<NUM>).