+

WO2019005942A1 - Protection de trame de réveil - Google Patents

Protection de trame de réveil Download PDF

Info

Publication number
WO2019005942A1
WO2019005942A1 PCT/US2018/039723 US2018039723W WO2019005942A1 WO 2019005942 A1 WO2019005942 A1 WO 2019005942A1 US 2018039723 W US2018039723 W US 2018039723W WO 2019005942 A1 WO2019005942 A1 WO 2019005942A1
Authority
WO
WIPO (PCT)
Prior art keywords
frame
wur
wake
authentication field
indicator bit
Prior art date
Application number
PCT/US2018/039723
Other languages
English (en)
Inventor
Po-Kai Huang
Minyoung Park
Robert Stacey
Ehud Reshef
Original Assignee
Intel Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Intel Corporation filed Critical Intel Corporation
Publication of WO2019005942A1 publication Critical patent/WO2019005942A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0229—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal
    • H04W52/0235—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal where the received signal is a power saving command
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H04W12/069—Authentication using certificates or pre-shared keys
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/10—Integrity
    • H04W12/106—Packet or message integrity
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • This disclosure generally relates to systems, methods, and devices for wireless communications and, more particularly, to wake-up frame protection.
  • FIG. 1 is a network diagram illustrating an example network environment for wake- up frame protection, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 2 depicts an illustrative schematic diagram for low power wake-up signaling, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 3 depicts an illustrative frame having an indicator for frame integrity and replay attack protection, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 4 illustrates a flow diagram of an illustrative process for receiving a wake-up frame, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 5 illustrates a flow diagram of an illustrative process for generating and transmitting a wake-up frame, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 6 shows a functional diagram of an exemplary communication station that may be suitable for use as a user device, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 7 is a block diagram of an example machine upon which any of one or more techniques (e.g., methods) may be performed, in accordance with one or more example embodiments of the present disclosure.
  • LP- WUR Low Power Wake Up Receiver/Radio
  • IEEE 802.1 lba is currently in development and is directed in part to the standardization of Low Power Wake Up Receiver/Radio (LP- WUR) capabilities.
  • LP- WUR is a technique to enable ultra-low power operation for Wi-Fi devices. The idea is for a device to have a simple low power receiver that can receive a wake-up frame from its peer. This low power receiver (the LP- WUR) will wake up the primary radio or processor (sometimes referred to as a primary connectivity radio) in response to receiving a wake-up frame.
  • the LP- WUR may have a lower power requirement than the primary radio or processor.
  • the device can stay in a low power mode (e.g., a WUR mode) until receiving the wake-up frame from an access point (AP).
  • a low power mode e.g., a WUR mode
  • the LP- WUR will be ON while the primary radio or processor will be OFF or in a low power state. In this manner, power may be conserved on the device.
  • a conventional device without a LP- WUR will save power by turning off the primary radio or by placing the primary radio in a limited functionality low power state.
  • the amount of power saved is proportional to the amount of time the primary radio remains off or in a low power state.
  • the tradeoff is that any data packets destined for the device are delayed until the primary radio is switched back to a full power state.
  • the introduction of a LP- WUR directly addresses this issue by allowing a device to power down the primary connectivity radio without causing a reduction in latency.
  • the LP- WUR receives any data packets destined for the primary connectivity radio, and in response, can wake up the primary connectivity radio.
  • the lowest data rate of a wake-up frame based on the current version of 802.1 lba is only around 62.5 kbps, which is much lower than the lowest data rate for 802.1 In, which is around 6 Mbps.
  • the frame format of a wake-up frame needs to be carefully designed to avoid a high overhead and a waste of medium usage.
  • a LP-WUR is ideally only receiving WUR frames from legitimate transmitters (e.g., an originator such as an associated AP) having data packets destined for the primary connectivity radio of the LP-WUR device.
  • legitimate transmitters e.g., an originator such as an associated AP
  • STA station
  • WUR frames can be built with various frame authentication capabilities to ensure packet integrity (also referred to herein as frame integrity).
  • Frame authentication can provide a device with a means to verify that a received frame is really from a legitimate transmitter, such as an associated AP. In this manner, a device having an LP-WUR can ensure that the primary connectivity radio is woken up only by frames received from legitimate sources.
  • the basic idea of frame authentication is to provide an authentication field in the transmitted frame itself.
  • the value of the authentication field is computed using data that is only known by the legitimate transmitters and receivers, such as, for example, using a shared key.
  • a LP-WUR that receives a WUR frame can easily check the value of the authentication field to determine if the transmission of the WUR frame is legitimate. If the check fails, the LP-WUR can ignore the WUR frame.
  • the hash like operation is based on, for example, a shared key (sometimes referred to as an integrity key) known by both the transmitter and receiver of the WUR frame.
  • the transmitter and receiver may not have a shared key.
  • some Wi-Fi associations such as those that do not require a password (e.g., a freely accessible public Wi-Fi), do not have a pre-shared key at all.
  • an active authentication field refers to an authentication field that must be validated by the receiving device prior to taking any further actions (e.g., sending a wake-up signal to a primary connectivity radio). For example, an AP will need to communicate to a STA whether a particular frame is protected via an authentication field.
  • the receiving device may compare a value in the authentication field against a predetermined value already known by the receiving device. The predetermined value may be based at least in part on secret information exchanged ahead of time between the receiving device and the transmitting device, for example, a shared key.
  • wake-up frame design does not provide an indication of whether a frame received from a transmitting device includes an active authentication field for frame integrity and replay attack protection. As a result, there is no way to optimize the frame format or receiver operation procedure based on whether frame integrity and replay attack protection exists in the frame.
  • Example embodiments of the present disclosure relate to systems, methods, and devices for wake-up frame protection.
  • lower energy consumption may be achieved by adding an LP-WUR to a device to wake-up a primary connectivity radio (e.g., an IEEE 802.11 transceiver) of the device.
  • This wake-up signal can be sent by the LP-WUR in response to receiving a WUR frame from another device (e.g., an AP associated with the device).
  • the LP-WUR integrated in the circuitry of the device may be configured to receive a wake-up frame as an indication that the main or primary connectivity radio of the device may need to be powered on in order to start receiving/sending data.
  • the device transmitting the wake-up frame may include a wake-up frame transmitter that generates the wake-up frame to be transmitted to the device.
  • the LP-WUR may be based on, but is not limited to, "on-off keying” (OOK), amplitude shift keying (ASK) or frequency shift keying (FSK) for signaling, and is characterized with a much lower power consumption compared to a normal IEEE 802.11 orthogonal frequency-division multiplexing (OFDM) receiver (e.g., an IEEE 802.11 receiver).
  • OOK on-off keying
  • ASK amplitude shift keying
  • FSK frequency shift keying
  • the WUR frame format is that of a WUR Beacon.
  • a WUR Beacon is a periodic transmission from an AP that maintains synchronization with a STA that has its LP- WUR turned on and its primary connectivity radio turned off.
  • the WUR frame format is that of a unicast wake-up frame.
  • a unicast wake-up frame refers to a WUR frame that is addressed to a single STA. In other words, a unicast wake-up frame can wake up the primary connectivity radio of one STA.
  • the WUR frame format is that of a multicast wake-up frame.
  • a multicast wake-up frame refers to a WUR frame that is addressed to many STAs. In other words, a multicast wake-up frame can wake up the primary connectivity radio of one or more STAs.
  • a wake-up frame protection system may differentiate the three kinds of wake-up frames. For example, a type field may be required in every wake-up frame.
  • the type frame can contain data for identifying whether the frame being transmitted is a WUR Beacon, a unicast wake-up frame, a multicast wake-up frame, or any other type of frame.
  • a STA may include one or more types of radios used for transmitting and receiving messages with another STA.
  • the one or more types of radios may include LP- WUR and/or a primary connectivity radio.
  • STA2 may send a wake-up frame to wake up STAl .
  • STA2 is an AP, but can also be another STA in peer-to-peer scenarios.
  • a wake-up frame protection system may have an indication between STA2 to STAl to indicate if the packet from STA2 is equipped with a mechanism for frame integrity and replay attack protection, for example, by requiring authentication verification.
  • the indication can notify a receiving device that the receiving device is expected to validate a value in the authentication field.
  • the indication may be a combined frame type and indication bit set in the type field of the WUR frame.
  • One entry is used to indicate a unicast wake-up frame without frame integrity and replay attack protection.
  • the WUR frame can include a bit set to "0" to indicate a unicast WUR frame without an active authentication field.
  • One entry is used to indicate a unicast wake-up frame with frame integrity and replay attack protection.
  • the WUR frame can include a bit set to "1" to indicate a unicast WUR frame with an active authentication field.
  • One entry is used to indicate a multicast wake-up frame without frame integrity and replay attack protection.
  • the WUR frame can include a bit set to "2" to indicate a multicast WUR frame without an active authentication field.
  • One entry is used to indicate a multicast wake-up frame with frame integrity and replay attack protection.
  • the WUR frame can include a bit set to "3" to indicate a multicast WUR frame with an active authentication field.
  • One entry is used to indicate a WUR Beacon with frame integrity and replay attack protection.
  • the WUR frame can include a bit set to "4" to indicate a WUR Beacon with an active authentication field.
  • One entry is used to indicate a WUR Beacon without frame integrity and replay attack protection.
  • the WUR frame can include a bit set to "5" to indicate a WUR Beacon without an active authentication field.
  • the indication may be a separate indicator bit set in the WUR frame.
  • This bit can also be referred to as a protected bit.
  • the value of the indicator bit can indicate whether the frame has an active authentication field for frame integrity and replay attack protection.
  • One value of the indicator bit indicates that the frame includes an active authentication field.
  • the WUR frame can include an indicator bit set to "1" to indicate that the authentication field is active.
  • One value of the indicator bit indicates that the frame does not include an active authentication field.
  • the WUR frame can include an indicator bit set to "0" to indicate that the authentication field is not active.
  • the indication can be a separate indicator bit in the type field of the WUR frame.
  • the value of the indicator bit can indicate whether the frame has an active authentication field for frame integrity and replay attack protection.
  • One value of the indicator bit indicates that the frame does include an active authentication field.
  • the WUR frame can include an indicator bit set in the type field to "1" to indicate that the frame includes an active authentication field.
  • One value of the indicator bit indicates that the frame does not include an active authentication field.
  • the WUR frame can include an indicator bit set in the type field to "0" to indicate that the frame does not include an active authentication field.
  • STA1 and STA2 can agree on the indication through a WUR negotiation for WUR capability. For example, if STA1 and STA2 agree during this negotiation on having frame integrity and replay attack protection, then STA1 may treat all the frames received from STA2 as frames with frame integrity and replay attack protection. In other words, STA1 can treat a received frame from STA2 as a trusted frame that has passed an authentication field check, without actually requiring STA1 to check the value of the indicator bit or to complete the verification.
  • STAl can treat all the frames from STA2 as frames without frame integrity and replay attack protection.
  • the WUR negotiation is incorporated within an initial negotiation (e.g., an association negotiation between an AP and a STA) during which the secret information (e.g., a password) is exchanged, as described in further detail herein.
  • an initial negotiation e.g., an association negotiation between an AP and a STA
  • the secret information e.g., a password
  • a first device can consider frames received from a second device as having frame integrity and replay attack protection as a result of a successful association negotiation with the second device. The idea is that the first device, having already purposefully exchanged a password with the second device to gain an association with the second device, can trust that the second device will not be a source of a data integrity or replay attack.
  • stating that a frame has "frame integrity and replay attack protection” means that a first device (e.g., STAl) has to go through a specific verification and authentication process for a received packet.
  • STAl must validate an authentication field in the frame by checking a value in the authentication field against a value known by STAl.
  • This secret information such as a password used to establish the initial connection between the devices, can serve as, or be used to generate, a shared key.
  • the authentication field may be referred to as a Message Integrity Code (MIC) or as a Message Authentication Code (MAC), although the authentication mechanism is not meant to be limited by the name or designation of the field for providing authentication.
  • MIC Message Integrity Code
  • MAC Message Authentication Code
  • the verification and authentication mechanism can be but is not limited to the following.
  • the authentication field of a frame includes data for providing frame integrity, replay attack protection, or both.
  • the authentication field may be based on a shared key exchanged between the transmitter and receiver of the frame.
  • the authentication field may include data that is the output of an agreed upon function when applying the shared key to an agreed upon input.
  • the value of the function, shared key, and input can be negotiated, prior to exchanging the frame, by a transmitter and a receiver (e.g., between a STAl and a STA2, or between an AP and a STA).
  • STAl may do the computation (verification) after receiving the frame and may see if the results match the contention (value) in the authentication field carried in the frame.
  • the shared key can be a reused (repurposed) shared key from a prior interaction between the devices.
  • the shared key can be generated by the transmitter or the receiver of the frame 300 based on a mutually known password. For example, a network associated with an AP and a STA may require all connected devices to provide a password prior to accessing any network services. This password can serve as the shared key, or can be used to generate a shared key.
  • the transmitter and receiver of the frame 300 negotiate a value of the shared key. This negotiation can occur prior to transmitting the frame 300.
  • verifying an authentication field requires the transmitter and receiver to do the same hash like operation.
  • the hash like operation may be based on, for example, a shared key between the transmitter and receiver of the WUR frame.
  • a value of the shared key is negotiated between the respective devices.
  • the shared key can be negotiated in various ways.
  • the shared key can be provided by a first device (e.g., an AP) to a second device (e.g., a STA).
  • a shared key unique to a specific AP can be provided by the AP to one or more STAs.
  • a shared key can be provided by a STA to an AP.
  • the shared key can be a reused (repurposed) shared key from a prior interaction between the devices.
  • the shared key is exchanged ahead of time through the primary connectivity radios for added security.
  • An attacker who will not know the agreed upon function or the agreed upon input, and who will not have access to any shared key, will not be able to generate an authentication field having the correct output value. Consequently, any frames received from the attacker will fail the authentication field check. Once the authentication field check fails, the receiving device may ignore the frame. In this manner, receiving a malicious frame (e.g., a spoofed wake-up frame designed to waste power) will not trigger the LP- WUR of the receiving device to wake-up the primary radio.
  • a malicious frame e.g., a spoofed wake-up frame designed to waste power
  • the primary connectivity radio will have a shared key, and in other scenarios, the primary connectivity radio will not. In other words, it is then required for the STA to understand whether a received WUR frame requires authentication verification or not.
  • the frame format for a unicast or multicast wake- up frame can be optimized for the case when there is authentication verification and for the case when there is no authentication verification. Further, the STA may also optimize the receiving operation based on whether there is authentication verification for the receiving unicast/multicast wake-up frame.
  • a transmitter may selectively turn frame authentication on or off based on a perceived threat or lack of any threat to the AP or to any devices associated with the AP (e.g., an associated STA).
  • the AP or a STA in a peer-to-peer environment
  • the AP can allow for frames to be easily exchanged without the complications and computational overhead associated with the additional authentication field checks until those checks are needed to protect the AP or an associated device.
  • an AP can operate under a default state where no frames require authentication, and this default state can be maintained until a perceived or realized threat or attack occurs. Once a threat or attack is identified, the AP can turn on frame authentication, and all new frames will require verification of a value in an authentication field.
  • a threat or attack can be identified in various ways.
  • a number of repeated wake-up frames received by the AP or a STA associated with the AP within a predetermined period of time exceeding a threshold can indicate an attack.
  • four wake-up frames received by a device within 10 minutes can indicate an attack.
  • the basic idea of frame authentication is to provide an authentication field in the transmitted frame itself.
  • the authentication field in the wake-up frame provides packet integrity (also referred to herein as frame integrity).
  • the wake-up frame also includes a sequence number field to prevent replay attack.
  • sequence number fields are included in all multicast wake-up frames.
  • the additional sequence number field can include a sequence number (e.g., a packet number) identifying the current frame sequence number for frames sent between the transmitter and receiver.
  • the sequence number is the current number of frames sent between the transmitter and receiver.
  • the tenth frame exchanged between a first device and a second device can have a sequence number with a value of "10.”
  • the sequence number can be part of the authentication field verification calculations. The idea behind exchanging a running sequence of the number of frames exchanged is two-fold. First, an attacker will not immediately know the current sequence number. By the time the attacker discovers the current sequence number, and transmits a frame having a next sequence number, the sequence number may have already naturally changed (due, e.g., to another frame exchange between the transmitter and receiver).
  • the attacker is constantly playing catch-up, and frames received from the attacker can be easily ignored, because they contain a reference to an old sequence number.
  • the next legitimate transmission from the transmitter may include the same sequence number, altering the devices to an attack. For example, if the current sequence number is "10" and an attacker sends a frame with a sequence number of "11,” the next frame from the transmitter may also include a sequence number for "11." The receiver, having received two frames with an "11" sequence number, will know that there has been an attack.
  • FIG. 1 is a network diagram illustrating an example network environment of low power wake-up signaling, according to some example embodiments of the present disclosure.
  • Wireless network 100 may include one or more user devices 120 and one or more access points(s) (APs) 102, which may communicate in accordance with IEEE 802.11 communication standards.
  • the user device(s) 120 may be mobile devices that are non-stationary (e.g., not having fixed locations) or may be stationary devices.
  • the user devices 120 and the AP 102 may include one or more computer systems similar to that of the functional diagram of FIG. 6 and/or the example machine/system of FIG. 7.
  • One or more illustrative user device(s) 120 and/or AP(s) 102 may be operable by one or more user(s) 110. It should be noted that any addressable unit may be a station (STA). An STA may take on multiple distinct characteristics, each of which shape its function. For example, a single addressable unit might simultaneously be a portable STA, a quality-of- service (QoS) STA, a dependent STA, and a hidden STA. The one or more illustrative user device(s) 120 and the AP(s) 102 may be STAs.
  • STA station
  • An STA may take on multiple distinct characteristics, each of which shape its function. For example, a single addressable unit might simultaneously be a portable STA, a quality-of- service (QoS) STA, a dependent STA, and a hidden STA.
  • QoS quality-of- service
  • the one or more illustrative user device(s) 120 and/or AP(s) 102 may operate as a personal basic service set (PBSS) control point/access point (PCP/AP).
  • PBSS personal basic service set
  • PCP/AP control point/access point
  • the user device(s) 120 (e.g., 124, 126, or 128) and/or AP(s) 102 may include any suitable processor-driven device including, but not limited to, a mobile device or a no n- mobile, e.g., a static, device.
  • user device(s) 120 and/or AP(s) 102 may include, a user equipment (UE), a station (STA), an access point (AP), a software enabled AP (SoftAP), a personal computer (PC), a wearable wireless device (e.g., bracelet, watch, glasses, ring, etc.), a desktop computer, a mobile computer, a laptop computer, an ultrabookTM computer, a notebook computer, a tablet computer, a server computer, a handheld computer, a handheld device, an internet of things (IoT) device, a sensor device, a PDA device, a handheld PDA device, an on-board device, an off-board device, a hybrid device (e.g., combining cellular phone functionalities with PDA device functionalities), a consumer device, a vehicular device, a non- vehicular device, a mobile or portable device, a non-mobile or non-portable device, a mobile phone, a cellular telephone, a PCS device, a PDA device which
  • IoT Internet of Things
  • IP Internet protocol
  • ID Bluetooth identifier
  • NFC near-field communication
  • An IoT device may have a passive communication interface, such as a quick response (QR) code, a radio-frequency identification (RFID) tag, an NFC tag, or the like, or an active communication interface, such as a modem, a transceiver, a transmitter-receiver, or the like.
  • QR quick response
  • RFID radio-frequency identification
  • An IoT device can have a particular set of attributes (e.g., a device state or status, such as whether the IoT device is on or off, open or closed, idle or active, available for task execution or busy, and so on, a cooling or heating function, an environmental monitoring or recording function, a light-emitting function, a sound-emitting function, etc.) that can be embedded in and/or controlled/monitored by a central processing unit (CPU), microprocessor, ASIC, or the like, and configured for connection to an IoT network such as a local ad-hoc network or the Internet.
  • a device state or status such as whether the IoT device is on or off, open or closed, idle or active, available for task execution or busy, and so on, a cooling or heating function, an environmental monitoring or recording function, a light-emitting function, a sound-emitting function, etc.
  • CPU central processing unit
  • ASIC application specific integrated circuitry
  • IoT devices may include, but are not limited to, refrigerators, toasters, ovens, microwaves, freezers, dishwashers, dishes, hand tools, clothes washers, clothes dryers, furnaces, air conditioners, thermostats, televisions, light fixtures, vacuum cleaners, sprinklers, electricity meters, gas meters, etc., so long as the devices are equipped with an addressable communications interface for communicating with the IoT network.
  • IoT devices may also include cell phones, desktop computers, laptop computers, tablet computers, personal digital assistants (PDAs), etc.
  • the IoT network may be comprised of a combination of "legacy" Internet-accessible devices (e.g., laptop or desktop computers, cell phones, etc.) in addition to devices that do not typically have Internet-connectivity (e.g., dishwashers, etc.).
  • “legacy” Internet-accessible devices e.g., laptop or desktop computers, cell phones, etc.
  • devices that do not typically have Internet-connectivity e.g., dishwashers, etc.
  • the user device(s) 120 and/or AP(s) 102 may also include mesh stations in, for example, a mesh network, in accordance with one or more IEEE 802.11 standards and/or 3 GPP standards.
  • Any of the user device(s) 120 may be configured to communicate with each other via one or more communications networks 130 and/or 135 wirelessly or wired.
  • the user device(s) 120 may also communicate peer-to-peer or directly with each other with or without the AP(s) 102.
  • Any of the communications networks 130 and/or 135 may include, but not limited to, any one of a combination of different types of suitable communications networks such as, for example, broadcasting networks, cable networks, public networks (e.g., the Internet), private networks, wireless networks, cellular networks, or any other suitable private and/or public networks.
  • any of the communications networks 130 and/or 135 may have any suitable communication range associated therewith and may include, for example, global networks (e.g., the Internet), metropolitan area networks (MANs), wide area networks (WANs), local area networks (LANs), or personal area networks (PANs).
  • any of the communications networks 130 and/or 135 may include any type of medium over which network traffic may be carried including, but not limited to, coaxial cable, twisted-pair wire, optical fiber, a hybrid fiber coaxial (HFC) medium, microwave terrestrial transceivers, radio frequency communication mediums, white space communication mediums, ultra-high frequency communication mediums, satellite communication mediums, or any combination thereof.
  • coaxial cable twisted-pair wire
  • optical fiber a hybrid fiber coaxial (HFC) medium
  • microwave terrestrial transceivers microwave terrestrial transceivers
  • radio frequency communication mediums white space communication mediums
  • ultra-high frequency communication mediums satellite communication mediums, or any combination thereof.
  • Any of the user device(s) 120 may include one or more communications antennas.
  • the one or more communications antennas may be any suitable type of antennas corresponding to the communications protocols used by the user device(s) 120 (e.g., user devices 124, 126 and 128), and AP(s) 102.
  • suitable communications antennas include Wi-Fi antennas, Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards compatible antennas, directional antennas, non-directional antennas, dipole antennas, folded dipole antennas, patch antennas, multiple-input multiple-output (MIMO) antennas, omnidirectional antennas, quasi- omnidirectional antennas, or the like.
  • the one or more communications antennas may be communicatively coupled to a radio component to transmit and/or receive signals, such as communications signals to and/or from the user devices 120 and/or AP(s) 102.
  • Any of the user device(s) 120 may be configured to perform directional transmission and/or directional reception in conjunction with wirelessly communicating in a wireless network.
  • Any of the user device(s) 120 e.g., user devices 124, 126, 128), and AP(s) 102 may be configured to perform such directional transmission and/or reception using a set of multiple antenna arrays (e.g., DMG antenna arrays or the like). Each of the multiple antenna arrays may be used for transmission and/or reception in a particular respective direction or range of directions.
  • Any of the user device(s) 120 (e.g., user devices 124, 126, 128), and AP(s) 102 may be configured to perform any given directional transmission towards one or more defined transmit sectors. Any of the user device(s) 120 (e.g., user devices 124, 126, 128), and AP(s) 102 may be configured to perform any given directional reception from one or more defined receive sectors.
  • MIMO beamforming in a wireless network may be accomplished using RF beamforming and/or digital beamforming.
  • user devices 120 and/or AP(s) 102 may be configured to use all or a subset of its one or more communications antennas to perform MIMO beamforming.
  • Any of the user devices 120 may include any suitable radio and/or transceiver for transmitting and/or receiving radio frequency (RF) signals in the bandwidth and/or channels corresponding to the communications protocols utilized by any of the user device(s) 120 and AP(s) 102 to communicate with each other.
  • the radio components may include hardware and/or software to modulate and/or demodulate communications signals according to pre-established transmission protocols.
  • the radio components may further have hardware and/or software instructions to communicate via one or more Wi-Fi and/or Wi-Fi direct protocols, as standardized by the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards.
  • the radio component in cooperation with the communications antennas, may be configured to communicate via 2.4 GHz channels (e.g., 802.11b, 802. llg, 802.11 ⁇ , 802.11ax), 5 GHz channels (e.g. 802.11 ⁇ , 802.11ac, 802.11ax), or 60 GHz channels (e.g., 802.1 lad).
  • non- Wi-Fi protocols may be used for communications between devices, such as Bluetooth, dedicated short-range communication (DSRC), Ultra-High Frequency (UHF) (e.g., IEEE 802.1 laf, IEEE 802.22), white band frequency (e.g., white spaces), or other packetized radio communications.
  • the radio component may include any known receiver and baseband suitable for communicating via the communications protocols.
  • the radio component may further include a low noise amplifier (LNA), additional signal amplifiers, an analog-to-digital (A/D) converter, one or more buffers, and digital baseband.
  • LNA low noise amplifier
  • A/D analog-to-digital converter
  • one or more AP e.g., AP(s) 102
  • the AP(s) 102 may communicate in a downlink direction and the user devices 120 may communicate with one or more AP(s) 102 in an uplink direction by sending data frames in either direction.
  • the user devices 120 may also communicate peer-to-peer or directly with each other with or without the AP 102.
  • the communication 140 may be multiuser communication between an AP and one or more user devices.
  • the one or more user devices may belong to the same or different BSS.
  • the one or more user devices 120 may operate in a low power mode (e.g., a LP- WUR mode) to conserve power.
  • a low power mode e.g., a LP- WUR mode
  • the LP-WUR of a user device 120 may be active while an 802.11 transceiver may be inactive. Because the LP-WUR may operate in a lower power state than the 802.11 transceiver, power may be conserved on the user device 120.
  • an AP 102 may send a wake-up frame 142 to one or more user device(s) 120.
  • a wake-up frame 142 may signal to a user device 120 to activate a higher power mode, which may include activating a higher powered 802.11 transceiver on the user device 120.
  • STA2 e.g., AP 102
  • STA1 e.g., user device 120
  • WUR wake-up radio
  • a wake-up frame protection system may include an indication from STA2 to STA1 to indicate if the packet from STA2 is equipped with mechanism for frame integrity and replay attack protection, for example, by including an authentication verification field.
  • the indication may be in the type field of the wake-up frame 142.
  • One entry is used to indicate a unicast wake-up frame without frame integrity and replay attack protection.
  • One entry is used to indicate a unicast wake-up frame with frame integrity and replay attack protection.
  • One entry is used to indicate a multicast wake-up frame without frame integrity and replay attack protection.
  • One entry is used to indicate a multicast wake-up frame with frame integrity and replay attack protection.
  • One entry is used to indicate a WUR Beacon with frame integrity and replay attack protection.
  • One entry is used to indicate a WUR Beacon without frame integrity and replay attack protection.
  • the indication may be a separate bit in the wake-up frame 142.
  • This bit can be referred to as an indicator bit, or as a protected bit.
  • the bit is set to 1 to indicate the frame has frame integrity and replay attack protection (for example, by way of an authentication verification field).
  • the bit is set to 0 to indicate the frame does not have frame integrity and replay attack protection.
  • the indication can be a separate bit in the type field of the wake- up frame 142.
  • One bit in the type field is set to 1 to indicate the frame has frame integrity and replay attack protection.
  • One bit in the type field is set to 0 to indicate the frame does not have frame integrity and replay attack protection.
  • STAl and STA2 can agree on the indication through WUR negotiation for WUR capability. For example, if STAl and STA2 agree on having frame integrity and replay attack protection, then STAl treats all the frames (including, e.g., wake- up frame 142) from STA2 with frame integrity and replay attack protection, regardless of the value of the indicator bit. If STAl and STA2 do not agree on having frame integrity and replay attack protection, then STAl treats all the frames from STA2 as frames without frame integrity and replay attack protection unless the frame includes an indication for frame integrity and replay attack protection.
  • WUR negotiation for WUR capability. For example, if STAl and STA2 agree on having frame integrity and replay attack protection, then STAl treats all the frames (including, e.g., wake- up frame 142) from STA2 with frame integrity and replay attack protection, regardless of the value of the indicator bit. If STAl and STA2 do not agree on having frame integrity and replay attack protection, then STAl treats all the frames from STA2 as frames without
  • the wake-up frame 142 having frame integrity and replay attack protection means that STAl has to go through a specific verification and authentication process for the received packet.
  • the verification and authentication mechanism can be but is not limited to the following.
  • the authentication field of the wake-up frame 142 includes data for providing frame integrity, replay attack protection, or both.
  • the authentication field may be based on a shared key exchanged between the STAl and the STA2.
  • the authentication field may include data that is the output of an agreed upon function when applying the shared key to an agreed upon input. The value of the function, shared key, and input can be negotiated, prior to exchanging the frame, by the STAl and the STA2. After the STAl receives the wake-up frame 142 from STA2, STAl can verify the wake- up frame 142 by checking the value in the authentication field against a locally computed value based on the shared key.
  • the shared key can be a reused (repurposed) shared key from a prior interaction between the STAl and STA2.
  • the shared key can be generated based on a mutually known password. For example, STA2 may require STAl (and all other stations) to have a password prior to accessing any network services. This password can serve as the shared key, or can be used to generate a shared key.
  • STA1 and STA2 negotiate a value of the shared key. This negotiation can occur prior to transmitting the wake-up frame 142.
  • verifying an authentication field requires the STA1 and STA2 to do the same hash like operation.
  • the hash like operation may be based on, for example, a shared key.
  • a value of the shared key is negotiated between the respective devices.
  • the value of the shared key can be negotiated in various ways.
  • the shared key can be provided by the STA2 to the STA1.
  • a shared key can be provided by the STA1 to the STA2.
  • the shared key can be a reused (repurposed) shared key from a prior interaction between the STA1 and STA2.
  • the shared key is exchanged ahead of time through the primary connectivity radios of the STA1 and STA2 for added security.
  • FIG. 2 depicts an illustrative schematic diagram for low power wake-up signaling, in accordance with one or more example embodiments of the present disclosure.
  • a transmitting device e.g., AP 202
  • a receiving device e.g., user device 222
  • the AP 202 may utilize a low power wake-up transmitter 230 to send a wake-up frame 232 to the low power wake-up receiver (LP-WUR) 234 included in the user device 222.
  • the AP 202 does not include a low power wake-up transmitter 230, and the wake-up frame 232 is instead sent by the 802.11 transceiver 238.
  • a LP-WUR enables ultra-low power operation for Wi-Fi devices.
  • a device e.g., the user device 222
  • the device can stay in low power mode (i.e., 802.11 transceiver 236 can remain in a low power state) until receiving the wake-up frame 232.
  • FIG. 2 shows an example of a unicast wake-up frame.
  • a transmitter e.g., an AP
  • the LP- WUR 234 may use simple modulation schemes such as on-off keying (OOK), amplitude shift keying (ASK), or frequency shift keying (FSK) for signaling.
  • OOK on-off keying
  • ASK amplitude shift keying
  • FSK frequency shift keying
  • the LP- WUR 234 may use hardware and/or software components that may allow it to operate at a lower power consumption mode than a typical radio component (e.g., 802.11 transceivers 236 and 238).
  • the LP- WUR 234 may be constantly active (e.g., ON state 240) on the user device 222 in order to receive a wake-up communication (e.g., the wake-up frame 232).
  • the AP 202 may begin transmitting the wake-up frame 232 using a low power communication method.
  • the LP- WUR 234 may detect and/or decode the wake-up frame 232 and may determine whether the wake-up frame 232 is destined for the user device 222.
  • the LP- WUR 234 may then send a wake-up signal 246 to the 802.11 transceiver 236 to power on (e.g., ON/OFF state 242) its circuitry.
  • the 802.11 transceiver 236 Once the 802.11 transceiver 236 is powered on, the AP 202 and the user device 222 can exchange one or more data frames, such as, for example, beacon frame(s) 244.
  • the wake-up frame 232 may include timing information such as a wake-up period.
  • the wake-up period may be a period of time during which the user device 222 may need to have the 802.11 transceiver 236 powered on because devices, such as the AP 202, may be sending data to the user device 222.
  • the user device 222 may power off some or all of its circuitry (e.g., the 802.11 transceiver 236) to reduce power consumption and preserve the life of its battery.
  • the low power wake-up transmitter 230 may be a device on the AP 202 that transmits a wake-up frame to other devices (e.g., the user device 222).
  • the low power wake- up transmitter 230 may transmit at the same simple modulation schemes of the user device 222 (e.g., OOK, ASK, FSK, etc.).
  • the low power wake-up transmitter 230 may utilize signaling in order to generate and transmit the wake-up frame 232.
  • FIG. 3 depicts an illustrative frame 300 for indicating frame integrity and replay attack protection, in accordance with one or more example embodiments of the present disclosure.
  • a frame 300 having a First Frame Field 302 and various other fields, such as optional additional fields 304 (e.g., a variable data field) and an Authentication Field 306.
  • the frame 300 also includes an indicator bit 308.
  • the First Frame Field 302 can include frame header data including an indicator for the type of frame of the frame 300, such as, for example, a "WUR Beacon” indicator, a "unicast wake-up frame” indicator, or a "multicast wake-up frame” indicator.
  • the indicator bit 308 (also referred to as a protected bit) is set to "1" or "0,” depending on whether the frame 300 includes frame integrity and replay attack protection.
  • the indicator bit 308 can be set to "1" to indicate that the frame 300 does include frame integrity and replay attack protection.
  • Frame integrity and replay attack protection can be provided, for example, by the authentication field 306.
  • an indicator bit 308 having a value set to "1" indicates to the receiving device that the authentication field 306 is active (i.e., that the authentication field 306 has data which must be verified).
  • the authentication field 306 in the frame 300 includes data for providing frame integrity, replay attack protection, or both.
  • the authentication field 306 may include data that is the output of an agreed upon function with an agreed upon input.
  • the agreed upon function and input may be shared prior to exchanging the frame 300 (e.g., between a STA1 and a STA2, or between an AP and a STA).
  • STA1 can use the agreed upon function and input to validate the authentication field.
  • STA1 may compute a first output after receiving the frame 300. The STA1 can then compare the computed first output to the output included in the authentication field 306 carried in the frame 300 to see if the results match. If the results match, the validation is successful.
  • An attacker who will not know the agreed upon function or the agreed upon input, will not be able to generate an authentication field 306 having the agreed upon output value. Consequently, any frames received from the attacker will fail the authentication field 306 check. Once the authentication field 306 check fails, the receiving device may ignore the frame. In this manner, receiving a malicious frame (e.g., a spoofed wake-up frame designed to waste power) will not trigger the LP-WUR of the receiving device to wake-up the primary radio.
  • a malicious frame e.g., a spoofed wake-up frame designed to waste power
  • the authentication field 306 may be based on a shared key exchanged between the transmitter and receiver of the frame 300.
  • the shared key can be provided by a first device (e.g., an AP) to a second device (e.g., a STA).
  • the shared key can be a reused (repurposed) shared key from a prior interaction between the devices.
  • the shared key can be generated by the transmitter or the receiver of the frame 300 based on a mutually known password. For example, a network associated with an AP and a STA may require all connected devices to provide a password prior to accessing any network services. This password can serve as the shared key, or can be used to generate a shared key.
  • the transmitter and receiver of the frame 300 negotiate a value of the shared key. This negotiation can occur prior to transmitting the frame 300.
  • STA1 In the case of STA1 receiving a frame from STA2, STA1 can use the shared key to validate the authentication field 306, in a similar manner as done with the agreed upon function and input. An attacker will not know the shared key, and consequently, any frames received from the attacker will fail the authentication field 306 check.
  • FIG. 4 illustrates a flow diagram of an illustrative process 400 for receiving a wake- up frame, in accordance with one or more example embodiments of the present disclosure.
  • a device may transition a primary connectivity radio of the device (e.g., the 802.11 transceiver of the user device 222 of FIG. 2) to a low power state.
  • the primary connectivity radio remains in the low power state until a wake-up frame is received. In this manner, power may be conserved on the device.
  • a wake-up receiver (WUR) frame from a second device is received by a low power wake-up receiver (LP- WUR) of the device.
  • the WUR frame is a WUR beacon for maintaining synchronization between the device and the second device while the primary connectivity radio of the device remains in the low power state.
  • the WUR frame is a wake-up frame (e.g., the wake-up frame 300 of FIG. 3).
  • the wake-up frame is a unicast wake-up frame addressed only to the device.
  • the wake-up frame is a multicast wake-up frame addressing the device and one or more other devices.
  • the WUR frame includes an indicator bit (e.g., the indicator bit 308 of FIG. 3) that signifies that an authentication field (e.g., the authentication field 306 of FIG. 3) exists in the WUR frame.
  • the indicator bit indicates that a value in the authentication field should be validated. Validation of the authentication field is discussed below with respect to block 406.
  • the indicator bit is set in a type field of the WUR frame.
  • one indicator bit value may be used to indicate a unicast wake-up frame without frame integrity and replay attack protection.
  • the indicator bit value may be used to indicate a unicast wake-up frame with frame integrity and replay attack protection.
  • the indicator bit may be a separate single bit set in the WUR frame outside of the type field.
  • one indicator bit value may be used to indicate that the WUR frame includes an active authentication field.
  • the WUR frame includes an indicator bit set to "1" to indicate that the authentication field is active and set to "0" to indicate that the authentication field is not active.
  • the indicator bit can be a separate single bit in the type field of the WUR frame.
  • the value of the indicator bit can indicate whether the frame has an active authentication field or not. For example, one value of the indicator bit may indicate that the WUR frame does include an active authentication field. In another example, one value of the indicator bit may indicate that the WUR frame does not include an active authentication field.
  • the device and the second device can agree on the value of the indicator bit during a WUR negotiation for WUR capability. For example, if these devices agree during the WUR negotiation on having frame integrity and replay attack protection, then the device may treat all the frames (e.g., the WUR frame) received from the second device as frames with frame integrity and replay attack protection. In other words, the device can treat the WUR frame as a trusted frame that has passed an authentication field check, without actually requiring the device to check the value of the indicator bit or to complete the verification of a value in the authentication field. In one embodiment, if the device and the second device do not agree during the WUR negotiation on the status of frames sent between the devices, then the device may treat all the frames from the second device as frames without frame integrity and replay attack protection.
  • the device may treat all the frames from the second device as frames without frame integrity and replay attack protection.
  • the WUR negotiation is incorporated within an initial negotiation (e.g., an association negotiation between the device and the second device) during which the secret information (e.g., a password) is exchanged.
  • the device can consider frames received from the second device as having frame integrity and replay attack protection as a result of a successful association negotiation with the second device.
  • a value in the authentication field is validated.
  • the value of the authentication field can be validated in a similar manner as the authentication field 306 of FIG. 3.
  • the LP- WUR of the receiving device validates the value in the authentication field.
  • the device may validate an authentication field in the WUR frame by checking a value in the authentication field against a predetermined value already known by the device.
  • the predetermined value is based at least in part on secret information exchanged ahead of time between the device and the second device.
  • this secret information may include a password used to establish the initial connection between the devices.
  • the password serves as, or is used to generate, a shared key.
  • the authentication field may include data that is the output of a function agreed upon by the device and the second device.
  • the function is based on a shared key and/or an agreed upon input value.
  • the value of the function, shared key, and input can be negotiated, prior to exchanging the frame, by the device and the second device.
  • the device after receiving the WUR frame, may compare a value of an authentication field of the WUR frame against the predetermined value.
  • the device uses a shared key known by the device and the second device to calculate the predetermined value.
  • a value of the shared key is negotiated between the device and the second device.
  • the value of the shared key can be negotiated in various ways.
  • the shared key can be provided by the device to the second device, or by the second device to the device.
  • the shared key can be a reused or repurposed shared key from a prior interaction between the device and the second device.
  • the shared key is exchanged ahead of time using the primary connectivity radio of the device.
  • the LP- WUR sends a wake-up signal (e.g., wake-up signal 246 of FIG. 2) to the primary connectivity radio of the device. As discussed previously herein, sending the wake-up signal may be in response to validating the value of the authentication field. In some embodiments, the device transitions the primary connectivity radio from the low power state to a high power state in response to the wake-up signal sent from the LP- WUR.
  • a wake-up signal e.g., wake-up signal 246 of FIG. 246 of FIG. 246 of FIG. 246 of FIG.
  • FIG. 5 illustrates a flow diagram of an illustrative process 500 for generating and transmitting a wake-up frame, in accordance with one or more example embodiments of the present disclosure.
  • a wake-up receiver (WUR) frame is generated.
  • the WUR frame is generated by a first device (e.g., the AP 202 of FIG. 2) for transmission to a second device (e.g., the user device 222 of FIG. 2).
  • the WUR frame is a WUR beacon for maintaining synchronization between devices while a primary connectivity radio of one of the devices remains in a low power state.
  • the WUR frame is a wake-up frame (e.g., the wake-up frame 300 of FIG. 3).
  • the wake-up frame is a unicast wake-up frame addressed only to a single device.
  • the wake-up frame is a multicast wake-up frame addressing one or more devices.
  • the WUR frame may include an indicator bit (e.g., the indicator bit 308 of FIG. 3) that indicates that an authentication field (e.g., the authentication field 306 of FIG. 3) exists in the WUR frame.
  • the indicator also indicates that a value in the authentication field should be validated.
  • the WUR frame may also include an instruction to transition a primary connectivity radio of a device (e.g., the 802.11 transceiver of the user device 222 of FIG. 2) from a low power state to a high power state.
  • the indicator bit is set in a type field of the WUR frame.
  • one indicator bit value may be used to indicate a unicast wake-up frame without frame integrity and replay attack protection.
  • the indicator bit value may be used to indicate a multicast wake-up frame with frame integrity and replay attack protection.
  • the indicator bit may be a separate single bit set in the WUR frame outside of the type field.
  • one indicator bit value may be used to indicate that the WUR frame includes an active authentication field.
  • the WUR frame includes an indicator bit set to "1" to indicate that the authentication field is active and set to "0" to indicate that the authentication field is not active.
  • the indicator bit can be a separate single bit in the type field of the WUR frame.
  • the value of the indicator bit can indicate whether the frame has an active authentication field or not. For example, one value of the indicator bit may indicate that the WUR frame does include an active authentication field. In another example, one value of the indicator bit may indicate that the WUR frame does not include an active authentication field.
  • the device and the second device can agree on the value of the indicator bit during a WUR negotiation for WUR capability, as discussed previously herein. For example, if these devices agree during the WUR negotiation on having frame integrity and replay attack protection, then the device may treat all the frames (e.g., the WUR frame) received from the second device as frames with frame integrity and replay attack protection.
  • the device may treat all the frames (e.g., the WUR frame) received from the second device as frames with frame integrity and replay attack protection.
  • the WUR frame is transmitted to the device (e.g., the user device 222 of FIG. 2).
  • the WUR frame is transmitted by a primary connectivity radio of a transmitting device.
  • the WUR frame may be transmitted by the 802.11 transceiver 238 of the AP 202 depicted in FIG. 2.
  • the WUR frame is transmitted by a low power wake-up transmitter of a transmitting device.
  • the WUR frame may be transmitted by the low power wake-up transmitter 230 of the AP 202 depicted in FIG. 2.
  • transmitting the WUR frame using a low power wake-up transmitter allows for a primary connectivity radio of the transmitting device to remain in a low power mode until the receiving device (e.g., the user device 222 of FIG. 2) has acknowledged the WUR frame and is ready to exchange data packets.
  • a response from the receiving device e.g., the user device 222 of FIG. 2) indicating an acknowledgment of the WUR frame is identified by the transmitting device (e.g., the AP 202 of FIG. 2).
  • the acknowledgment indicates that a LP- WUR (e.g., the LP- WUR 234 of the user device 222 of FIG. 2) has received the WUR frame.
  • the acknowledgment may indicate that a primary connectivity radio of the device (e.g., the 802.11 transceiver 236 of the user device 222 of FIG. 2) has transitioned from the low power state to the high power state.
  • the low power wake-up transmitter of the transmitter may send a wake- up signal to a primary connectivity radio of the transmitter in response to receiving an acknowledgment from the receiving device that the primary connectivity radio of the receiving device has transitioned from the low power state to the high power state.
  • FIG. 6 shows a functional diagram of an exemplary communication station 600 in accordance with some embodiments.
  • FIG. 6 illustrates a functional block diagram of a communication station that may be suitable for use as an AP 102 (FIG. 1) or user device 120 (FIG. 1) in accordance with some embodiments.
  • the communication station 600 may also be suitable for use as a handheld device, a mobile device, a cellular telephone, a smartphone, a tablet, a netbook, a wireless terminal, a laptop computer, a wearable computer device, a femtocell, a high data rate (HDR) subscriber station, an access point, an access terminal, or other personal communication system (PCS) device.
  • HDR high data rate
  • PCS personal communication system
  • the communication station 600 may include communications circuitry 602 and a transceiver 610 for transmitting and receiving signals to and from other communication stations using one or more antennas 601.
  • the communications circuitry 602 may include circuitry that can operate the physical layer (PHY) communications and/or media access control (MAC) communications for controlling access to the wireless medium, and/or any other communications layers for transmitting and receiving signals.
  • the communication station 600 may also include processing circuitry 606 and memory 608 arranged to perform the operations described herein. In some embodiments, the communications circuitry 602 and the processing circuitry 606 may be configured to perform operations detailed in FIGs. 2-5.
  • the communications circuitry 602 may be arranged to contend for a wireless medium and configure frames or packets for communicating over the wireless medium.
  • the communications circuitry 602 may be arranged to transmit and receive signals.
  • the communications circuitry 602 may also include circuitry for modulation/demodulation, upconversion/downconversion, filtering, amplification, etc.
  • the processing circuitry 606 of the communication station 600 may include one or more processors.
  • two or more antennas 601 may be coupled to the communications circuitry 602 arranged for sending and receiving signals.
  • the memory 608 may store information for configuring the processing circuitry 606 to perform operations for configuring and transmitting message frames and performing the various operations described herein.
  • the memory 608 may include any type of memory, including non-transitory memory, for storing information in a form readable by a machine (e.g., a computer).
  • the memory 608 may include a computer-readable storage device, read-only memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices and other storage devices and media.
  • the communication station 600 may be part of 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 medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), a wearable computer device, or another device that may receive and/or transmit information wirelessly.
  • PDA personal digital assistant
  • laptop or portable computer with wireless communication capability 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 medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), a wearable computer device, or another device that may receive and/or transmit information wirelessly.
  • the communication station 600 may include one or more antennas 601.
  • the antennas 601 may include 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.
  • a single antenna with multiple apertures may be used instead of two or more antennas.
  • each aperture may be considered a separate antenna.
  • MIMO multiple-input multiple-output
  • the antennas may be effectively separated for spatial diversity and the different channel characteristics that may result between each of the antennas and the antennas of a transmitting station.
  • the communication station 600 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.
  • the communication station 600 is illustrated as having several separate functional elements, two 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.
  • DSPs digital signal processors
  • some elements may include 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.
  • the functional elements of the communication station 600 may refer to one or more processes operating on one or more processing elements.
  • Certain embodiments may be implemented in one or a combination of hardware, firmware, and software. Other 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 memory mechanism for storing information in a form readable by a machine (e.g., a computer).
  • 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.
  • the communication station 600 may include one or more processors and may be configured with instructions stored on a computer-readable storage device memory.
  • FIG. 7 illustrates a block diagram of an example of a machine 700 or system upon which any one or more of the techniques (e.g., methodologies) discussed herein may be performed.
  • the machine 700 may operate as a standalone device or may be connected (e.g., networked) to other machines.
  • the machine 700 may operate in the capacity of a server machine, a client machine, or both in server-client network environments.
  • the machine 700 may act as a peer machine in peer-to- peer (P2P) (or other distributed) network environments.
  • P2P peer-to- peer
  • the machine 700 may be a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a mobile telephone, a wearable computer device, a web appliance, a network router, a switch or bridge, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine, such as a base station.
  • PC personal computer
  • PDA personal digital assistant
  • STB set-top box
  • mobile telephone a wearable computer device
  • web appliance e.g., a web appliance
  • network router e.g., a network router, a switch or bridge
  • any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine such as a base station.
  • 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 (Saa
  • 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 when operating.
  • a module includes hardware.
  • the hardware may be specifically configured to carry out a specific operation (e.g., hardwired).
  • the hardware may include configurable execution units (e.g., transistors, circuits, etc.) and a computer readable medium containing instructions where the instructions configure the execution units to carry out a specific operation when in operation. The configuring may occur under the direction of the execution units or a loading mechanism. Accordingly, the execution units are communicatively coupled to the computer-readable medium when the device is operating.
  • the execution units may be a member of more than one module.
  • the execution units may be configured by a first set of instructions to implement a first module at one point in time and reconfigured by a second set of instructions to implement a second module at a second point in time.
  • the machine 700 may include a hardware processor 702 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 704 and a static memory 706, some or all of which may communicate with each other via an interlink (e.g., bus) 708.
  • the machine 700 may further include a power management device 732, a graphics display device 710, an alphanumeric input device 712 (e.g., a keyboard), and a user interface (UI) navigation device 714 (e.g., a mouse).
  • the graphics display device 710, alphanumeric input device 712, and UI navigation device 714 may be a touch screen display.
  • the machine 700 may additionally include a storage device (i.e., drive unit) 716, a signal generation device 718 (e.g., a speaker), a wake-up frame protection device 719, a network interface device/transceiver 720 coupled to antenna(s) 730, and one or more sensors 728, such as a global positioning system (GPS) sensor, a compass, an accelerometer, or other sensor.
  • GPS global positioning system
  • the machine 700 may include an output controller 734, 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 with or control one or more peripheral devices (e.g., a printer, a card reader, etc.)).
  • 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 with or control one or more peripheral devices (e.g., a printer, a card reader, etc.)).
  • USB universal serial bus
  • IR infrared
  • NFC near field communication
  • the storage device 716 may include a machine-readable medium 722 on which is stored one or more sets of data structures or instructions 724 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein.
  • the instructions 724 may also reside, completely or at least partially, within the main memory 704, within the static memory 706, or within the hardware processor 702 during execution thereof by the machine 700.
  • one or any combination of the hardware processor 702, the main memory 704, the static memory 706, or the storage device 716 may constitute machine- readable media.
  • the wake-up frame protection device 719 may carry out or perform any of the operations and processes (e.g., the processes 400 and 500) described and shown above.
  • the wake-up frame protection device 719 may be configured to receive a wake-up frame as an indication that a primary connectivity radio may need to be powered on in order to start receiving/sending data.
  • the wake-up frame protection device 719 may negotiate a wake-up radio (WUR) capability with another device. During this negotiation, the wake-up frame protection device 719 can agree to treat all frames from another device as having, or not having, an active authentication field.
  • WUR wake-up radio
  • the wake-up frame protection device 719 may indicate that a frame is equipped with a mechanism for frame integrity and replay attack protection, for example, by requiring authentication verification.
  • the indication can notify a receiving device that the receiving device is expected to verify a value in the authentication field.
  • the wake-up frame protection device 719 may provide frame integrity and replay attack protection by use of an authentication field. For example, an indicator bit having a value set to "1" indicates to a receiving device that the authentication field in the frame generated by the wake-up frame protection device 719 is active (i.e., that the authentication field has data which must be verified).
  • the wake-up frame protection device 719 may generate a frame having an indicator bit for indicating frame integrity and replay attack protection.
  • the wake-up frame protection device 719 may set the indicator bit to "1" or "0,” depending on whether the frame includes frame integrity and replay attack protection.
  • the indicator bit can be set to "1" to indicate that the frame does include frame integrity and replay attack protection.
  • the wake-up frame protection device 719 may set the value of the authentication field based on a shared key or an agreed upon function and input, in a similar manner as discussed herein with respect to the authentication field 306 of FIG. 3. A device receiving the frame generated by the wake-up frame protection device 719 can easily verify the frame by validating the value of the authentication field.
  • the wake-up frame protection device 719 may use a combined frame type and an indication bit set in the type field of the WUR frame.
  • One entry is used to indicate a unicast wake-up frame without frame integrity and replay attack protection.
  • the WUR frame can include a bit set to "0" to indicate a unicast WUR frame without an active authentication field.
  • One entry is used to indicate a unicast wake-up frame with frame integrity and replay attack protection.
  • the WUR frame can include a bit set to "1" to indicate a unicast WUR frame with an active authentication field.
  • One entry is used to indicate a multicast wake-up frame without frame integrity and replay attack protection.
  • the WUR frame can include a bit set to "2" to indicate a multicast WUR frame without an active authentication field.
  • One entry is used to indicate a multicast wake-up frame with frame integrity and replay attack protection.
  • the WUR frame can include a bit set to "3" to indicate a multicast WUR frame with an active authentication field.
  • One entry is used to indicate a WUR Beacon with frame integrity and replay attack protection.
  • the WUR frame can include a bit set to "4" to indicate a WUR Beacon with an active authentication field.
  • One entry is used to indicate a WUR Beacon without frame integrity and replay attack protection.
  • the WUR frame can include a bit set to "5" to indicate a WUR Beacon without an active authentication field.
  • the wake-up frame protection device 719 may use a separate indicator bit set in the WUR frame. This bit can also be referred to as a protected bit.
  • the value of the indicator bit can indicate whether the frame has an active authentication field for frame integrity and replay attack protection.
  • One value of the indicator bit indicates that the frame includes an active authentication field.
  • the WUR frame can include an indicator bit set to "1" to indicate that the authentication field is active.
  • One value of the indicator bit indicates that the frame does not include an active authentication field.
  • the WUR frame can include an indicator bit set to "0" to indicate that the authentication field is not active.
  • the wake-up frame protection device 719 may use a separate indicator bit in the type field of the WUR frame.
  • the value of the indicator bit can indicate whether the frame has an active authentication field for frame integrity and replay attack protection.
  • One value of the indicator bit indicates that the frame does include an active authentication field.
  • the WUR frame can include an indicator bit set in the type field to "1" to indicate that the frame includes an active authentication field.
  • One value of the indicator bit indicates that the frame does not include an active authentication field.
  • the WUR frame can include an indicator bit set in the type field to "0" to indicate that the frame does not include an active authentication field.
  • the wake-up frame protection device 719 may incorporate WUR negotiation within an initial negotiation with another device (e.g., during an association negotiation) during which secret information (e.g., a password) is exchanged. For example, the wake-up frame protection device 719 may consider frames received from a second device as having frame integrity and replay attack protection as a result of a successful association negotiation with the second device.
  • secret information e.g., a password
  • verifying an authentication field may require the wake-up frame protection device 719 and a second device to do the same hash like operation.
  • the hash like operation may be based on, for example, a shared key between the wake-up frame protection device 719 and the second device.
  • the wake-up frame protection device 719 may negotiate a value of a shared key with other devices.
  • the value of the shared key can be negotiated in various ways.
  • the wake- up frame protection device 719 may provide the shared key to the other devices or may receive the shared key from the other devices.
  • the wake-up frame protection device 719 may selectively turn frame authentication on or off based on a perceived threat or lack of any threat to the machine 700 or to any devices associated with the machine 700 (e.g., an associated STA or AP). In this manner, the wake-up frame protection device 719 may allow for frames to be easily exchanged without the complications and computational overhead associated with the additional authentication field checks until those checks are needed to protect the AP or an associated device.
  • wake-up frame protection device 719 may be configured to perform and that other functions included throughout this disclosure may also be performed by the wake-up frame protection device 719.
  • machine-readable medium 722 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 724.
  • 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 724.
  • Various embodiments may be implemented fully or partially in software and/or firmware.
  • This software and/or firmware may take the form of instructions contained in or on a non-transitory computer-readable storage medium. Those instructions may then be read and executed by one or more processors to enable performance of the operations described herein.
  • the instructions may be in any suitable form, such as but not limited to source code, compiled code, interpreted code, executable code, static code, dynamic code, and the like.
  • Such a computer-readable medium may include any tangible non-transitory medium for storing information in a form readable by one or more computers, such as but not limited to read only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; a flash memory, etc.
  • machine-readable medium may include any medium that is capable of storing, encoding, or carrying instructions for execution by the machine 700 and that cause the machine 700 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.
  • a massed machine-readable medium includes a machine-readable medium with a plurality of particles having resting mass.
  • massed machine-readable media may include non-volatile memory, such as semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM), or electrically erasable programmable read-only memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD- ROM disks.
  • semiconductor memory devices e.g., electrically programmable read-only memory (EPROM), or electrically erasable programmable read-only memory (EEPROM)
  • EPROM electrically programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • the instructions 724 may further be transmitted or received over a communications network 726 using a transmission medium via the network interface device/transceiver 720 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.).
  • transfer protocols e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.
  • Example communications 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, wireless data networks (e.g., Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi®, IEEE 802.16 family of standards known as WiMax®), IEEE 802.15.4 family of standards, and peer-to-peer (P2P) networks, among others.
  • the network interface device/transceiver 720 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 726.
  • the network interface device/transceiver 720 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.
  • transmission medium shall be taken to include any intangible medium that is capable of storing, encoding, or carrying instructions for execution by the machine 700 and includes digital or analog communications signals or other intangible media to facilitate communication of such software.
  • the operations and processes described and shown above may be carried out or performed in any suitable order as desired in various implementations. Additionally, in certain implementations, at least a portion of the operations may be carried out in parallel. Furthermore, in certain implementations, less than or more than the operations described may be performed.
  • the word "exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any embodiment described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments.
  • the terms “computing device,” “user device,” “communication station,” “station,” “handheld device,” “mobile device,” “wireless device” and “user equipment” (UE) as used herein refers to a wireless communication device such as a cellular telephone, a smartphone, a tablet, a netbook, a wireless terminal, a laptop computer, a femtocell, a high data rate (HDR) subscriber station, an access point, a printer, a point of sale device, an access terminal, or other personal communication system (PCS) device.
  • the device may be either mobile or stationary.
  • the term "communicate” is intended to include transmitting, or receiving, or both transmitting and receiving. This may be particularly useful in claims when describing the organization of data that is being transmitted by one device and received by another, but only the functionality of one of those devices is required to infringe the claim. Similarly, the bidirectional exchange of data between two devices (both devices transmit and receive during the exchange) may be described as “communicating,” when only the functionality of one of those devices is being claimed.
  • the term “communicating” as used herein with respect to a wireless communication signal includes transmitting the wireless communication signal and/or receiving the wireless communication signal.
  • a wireless communication unit which is capable of communicating a wireless communication signal, may include a wireless transmitter to transmit the wireless communication signal to at least one other wireless communication unit, and/or a wireless communication receiver to receive the wireless communication signal from at least one other wireless communication unit.
  • the term "access point" (AP) as used herein may be a fixed station.
  • An access point may also be referred to as an access node, a base station, an evolved node B (eNodeB), an evolved node B (eNodeB), or some other similar terminology known in the art.
  • An access terminal may also be called a mobile station, user equipment (UE), a wireless communication device, or some other similar terminology known in the art.
  • Embodiments disclosed herein generally pertain to wireless networks. Some embodiments may relate to wireless networks that operate in accordance with one of the IEEE 802.11 standards.
  • Some embodiments may be used in conjunction with various devices and systems, for example, a personal computer (PC), a desktop computer, a mobile computer, a laptop computer, a notebook computer, a tablet computer, a server computer, a handheld computer, a handheld device, a personal digital assistant (PDA) device, a handheld PDA device, an onboard device, an off-board device, a hybrid device, a vehicular device, a non- vehicular device, a mobile or portable device, a consumer device, a non- mobile or non-portable device, a wireless communication station, a wireless communication device, a wireless access point (AP), a wired or wireless router, a wired or wireless modem, a video device, an audio device, an audio-video (A/V) device, a wired or wireless network, a wireless area network, a wireless video area network (WVAN), a local area network (LAN), a wireless LAN (WLAN), a personal area network (PAN), a wireless PAN (W
  • Some embodiments may be used in conjunction with one way and/or two-way radio communication systems, cellular radio-telephone communication systems, a mobile phone, a cellular telephone, a wireless telephone, a personal communication system (PCS) device, a PDA device which incorporates a wireless communication device, a mobile or portable global positioning system (GPS) device, a device which incorporates a GPS receiver or transceiver or chip, a device which incorporates an RFID element or chip, a multiple-input multiple-output (MIMO) transceiver or device, a single-input multiple-output (SIMO) transceiver or device, a multiple-input single-output (MISO) transceiver or device, a device having one or more internal antennas and/or external antennas, digital video broadcast (DVB) devices or systems, multi- standard radio devices or systems, a wired or wireless handheld device, e.g., a smartphone, a wireless application protocol (WAP) device, or the like.
  • WAP wireless application
  • Some embodiments may be used in conjunction with one or more types of wireless communication signals and/or systems following one or more wireless communication protocols, for example, radio frequency (RF), infrared (IR), frequency-division multiplexing (FDM), orthogonal FDM (OFDM), time-division multiplexing (TDM), time-division multiple access (TDM A), extended TDMA (E-TDMA), general packet radio service (GPRS), extended GPRS, code-division multiple access (CDMA), wideband CDMA (WCDMA), CDMA 2000, single-carrier CDMA, multi-carrier CDMA, multi-carrier modulation (MDM), discrete multi- tone (DMT), Bluetooth®, global positioning system (GPS), Wi-Fi, Wi-Max, ZigBee, ultra- wideband (UWB), global system for mobile communications (GSM), 2G, 2.5G, 3G, 3.5G, 4G, fifth generation (5G) mobile networks, 3GPP, long term evolution (LTE), LTE advanced, enhanced
  • Example 1 may include a device, the device comprising a low power wake- up receiver (LP-WUR), a primary connectivity radio, and storage and processing circuitry configured to: transition the primary connectivity radio to a low power state; receive, by the LP-WUR, a wake-up receiver (WUR) frame from a second device, the WUR frame comprising an indicator bit, the indicator bit signifying that the WUR frame comprises an authentication field and that a value in the authentication field should be validated; and validate, by the LP- WUR, the value in the authentication field.
  • LP-WUR low power wake- up receiver
  • WUR wake-up receiver
  • Example 2 may include the device of example 1 and/or some other example herein, wherein the WUR frame is a wake-up frame, and wherein the storage and processing circuitry is further configured to: cause to send, by the LP-WUR, a wake-up signal to the primary connectivity radio; and transition the primary connectivity radio from the low power state to a high power state.
  • Example 3 may include the device of example 1 and/or some other example herein, wherein validating the value in the authentication field is based at least in part on a shared key known by both the device and the second device.
  • Example 4 may include the device of example 3 and/or some other example herein, further comprising calculating, by the LP-WUR, an expected value for the authentication field based at least in part on the shared key.
  • Example 5 may include the device of example 4 and/or some other example herein, further comprising determining that the expected value for the authentication field is equal to the value in the authentication field.
  • Example 6 may include the device of example 1 and/or some other example herein, wherein the indicator bit comprises a single bit set in a field of the WUR frame.
  • Example 7 may include the device of example 1 and/or some other example herein, wherein the indicator bit comprises a single bit in a type field of the WUR frame.
  • Example 8 may include the device of example 7 and/or some other example herein, wherein the indicator bit further comprises an indication of a frame type.
  • Example 9 may include the device of any one of the examples 1 to 8 and/or some other example herein, further comprising, negotiating an effective value of the indicator bit with the second device.
  • Example 10 may include the device of example 1 and/or some other example herein, further comprising a transceiver configured to transmit and receive wireless signals.
  • Example 11 may include the device of example 10 and/or some other example herein, further comprising one or more antennas coupled to the transceiver.
  • Example 12 may include a no n- transitory computer-readable medium storing computer-executable instructions which when executed by one or more processors result in performing operations comprising: generating a wake-up receiver (WUR) frame comprising an indicator bit, the indicator bit signifying that the WUR frame comprises an authentication field and that a value in the authentication field should be validated; transmitting the WUR frame to a device; and identifying a response from the device indicating an acknowledgment of the WUR frame.
  • WUR wake-up receiver
  • Example 13 may include the no n- transitory computer-readable medium of example
  • the WUR frame is a wake-up frame comprising an instruction to transition a primary connectivity radio of the device from a low power state to a high power state.
  • Example 14 may include the non-transitory computer-readable medium of example
  • acknowledgment indicates that the primary connectivity radio of the device has transitioned from the low power state to the high power state.
  • Example 15 may include the non-transitory computer-readable medium of example 12 and/or some other example herein, further comprising transmitting a data frame to the device.
  • Example 16 may include the non-transitory computer-readable medium of example 12 and/or some other example herein, wherein transmitting the WUR frame comprises a unicast transmission.
  • Example 17 may include the non-transitory computer-readable medium of example 12 and/or some other example herein, wherein transmitting the WUR frame comprises a multicast transmission.
  • Example 18 may include the non-transitory computer-readable medium of any one of examples 12 to 17 and/or some other example herein, wherein the indicator bit comprises a single bit set in a field of the WUR frame.
  • Example 19 may include a method comprising: transitioning a primary connectivity radio of a first device to a low power state; receiving, by a low power wake-up receiver (LP- WUR) of the first device, a wake-up receiver (WUR) frame from a second device, the WUR frame comprising an indicator bit signifying that the WUR frame comprises an authentication field and that a value in the authentication field should be validated; and validating, by the LP- WUR of the first device, the value in the authentication field.
  • LP- WUR low power wake-up receiver
  • WUR wake-up receiver
  • Example 20 may include the method of example 19 and/or some other example herein, wherein validating the value in the authentication field is based at least in part on a shared key known by both the first device and the second device.
  • Example 21 may include the method of any one of examples 19 to 20 and/or some other example herein, further comprising, negotiating an effective value of the indicator bit.
  • Example 22 may include an apparatus comprising means for: generating a wake-up receiver (WUR) frame comprising an indicator bit, the indicator bit signifying that the WUR frame comprises an authentication field and that a value in the authentication field should be validated; transmitting the WUR frame to a device; and identifying a response from the device indicating an acknowledgment of the WUR frame.
  • WUR wake-up receiver
  • Example 23 may include the apparatus of example 22 and/or some other example herein, further comprising transmitting a data frame to the device.
  • Example 24 may include the apparatus of example 22 and/or some other example herein, wherein the acknowledgment indicates that a primary connectivity radio of the device has transitioned from the low power state to the high power state.
  • Example 25 may include the apparatus of any one of examples 22 to 24 and/or some other example herein, wherein the indicator bit comprises a single bit set in a field of the WUR frame.
  • Example 26 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1-25, or any other method or process described herein.
  • Example 27 may include an apparatus comprising logic, modules, and/or circuitry to perform one or more elements of a method described in or related to any of examples 1-25, or any other method or process described herein.
  • Example 28 may include a method, technique, or process as described in or related to any of examples 1-25, or portions or parts thereof.
  • Example 29 may include an apparatus comprising: one or more processors and one or more computer readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-25, or portions thereof.
  • Example 30 may include a method of communicating in a wireless network as shown and described herein.
  • Example 31 may include a system for providing wireless communication as shown and described herein.
  • Example 32 may include a device for providing wireless communication as shown and described herein.
  • Embodiments according to the invention are in particular disclosed in the attached claims directed to a method, a storage medium, a device and a computer program product, wherein any feature mentioned in one claim category, e.g., method, can be claimed in another claim category, e.g., system, as well.
  • the dependencies or references back in the attached claims are chosen for formal reasons only. However, any subject matter resulting from a deliberate reference back to any previous claims (in particular multiple dependencies) can be claimed as well, so that any combination of claims and the features thereof are disclosed and can be claimed regardless of the dependencies chosen in the attached claims.
  • These computer-executable program instructions may be loaded onto a special- purpose computer or other particular machine, a processor, or other programmable data processing apparatus to produce a particular machine, such that the instructions that execute on the computer, processor, or other programmable data processing apparatus create means for implementing one or more functions specified in the flow diagram block or blocks.
  • These computer program instructions may also be stored in a computer-readable storage media or memory that may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable storage media produce an article of manufacture including instruction means that implement one or more functions specified in the flow diagram block or blocks.
  • certain implementations may provide for a computer program product, comprising a computer- readable storage medium having a computer-readable program code or program instructions implemented therein, said computer-readable program code adapted to be executed to implement one or more functions specified in the flow diagram block or blocks.
  • the computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational elements or steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions that execute on the computer or other programmable apparatus provide elements or steps for implementing the functions specified in the flow diagram block or blocks.
  • blocks of the block diagrams and flow diagrams support combinations of means for performing the specified functions, combinations of elements or steps for performing the specified functions and program instruction means for performing the specified functions. It will also be understood that each block of the block diagrams and flow diagrams, and combinations of blocks in the block diagrams and flow diagrams, may be implemented by special-purpose, hardware-based computer systems that perform the specified functions, elements or steps, or combinations of special-purpose hardware and computer instructions.
  • Conditional language such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain implementations could include, while other implementations do not include, certain features, elements, and/or operations. Thus, such conditional language is not generally intended to imply that features, elements, and/or operations are in any way required for one or more implementations or that one or more implementations necessarily include logic for deciding, with or without user input or prompting, whether these features, elements, and/or operations are included or are to be performed in any particular implementation.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne des systèmes, des procédés, et des dispositifs associés à la protection d'une trame de réveil. Un dispositif peut comprendre un récepteur de réveil économe en énergie (LP-WUR), et une radio à connectivité primaire. Le dispositif peut faire passer la radio à connectivité primaire dans un état d'économie d'énergie afin d'économiser l'énergie. Le dispositif peut recevoir, par le LP-WUR, une trame WUR, d'un second dispositif. La trame WUR peut comprendre un bit indicateur. Le bit indicateur peut signifier que la trame WUR comprend un champ d'authentification, et qu'une valeur du champ d'authentification doit être validée. Le LP-WUR du dispositif peut valider la valeur du champ d'authentification. Le dispositif peut envoyer, par le LP-WUR, un signal de réveil à la radio à connectivité primaire. Le dispositif peut faire passer la radio à connectivité primaire de l'état d'économie d'énergie à un état de pleine puissance.
PCT/US2018/039723 2017-06-28 2018-06-27 Protection de trame de réveil WO2019005942A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201762526197P 2017-06-28 2017-06-28
US62/526,197 2017-06-28

Publications (1)

Publication Number Publication Date
WO2019005942A1 true WO2019005942A1 (fr) 2019-01-03

Family

ID=64742658

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2018/039723 WO2019005942A1 (fr) 2017-06-28 2018-06-27 Protection de trame de réveil

Country Status (1)

Country Link
WO (1) WO2019005942A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20200104254A (ko) * 2019-02-26 2020-09-03 차드라 래보러토리즈 엘엘씨 멀티 인터페이스 트랜스폰더 디바이스
WO2023193193A1 (fr) * 2022-04-07 2023-10-12 北京小米移动软件有限公司 Procédé et dispositif de transmission d'informations de puissance de signal de réveil, et support de stockage lisible

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090077249A1 (en) * 2007-08-07 2009-03-19 Xingwen Chen Method and device for implementing remote control of a terminal
US20110107075A1 (en) * 2009-10-29 2011-05-05 Inha-Industry Partnership Institute Network device and network control device in wireless body area network, and secure wake-up method and wake-up authentication code generation method of network device and network control device
WO2012127440A1 (fr) * 2011-03-23 2012-09-27 Renesas Mobile Corporation Procédé et appareil pour favoriser les communications automatisées
US8964662B2 (en) * 2009-04-30 2015-02-24 Samsung Electronics Co., Ltd Method and system for managing a body area network using a coordinator device
WO2016036581A1 (fr) * 2014-09-05 2016-03-10 Google Inc. Systèmes et procédés de réveil de dispositifs dans un réseau structuré

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090077249A1 (en) * 2007-08-07 2009-03-19 Xingwen Chen Method and device for implementing remote control of a terminal
US8964662B2 (en) * 2009-04-30 2015-02-24 Samsung Electronics Co., Ltd Method and system for managing a body area network using a coordinator device
US20110107075A1 (en) * 2009-10-29 2011-05-05 Inha-Industry Partnership Institute Network device and network control device in wireless body area network, and secure wake-up method and wake-up authentication code generation method of network device and network control device
WO2012127440A1 (fr) * 2011-03-23 2012-09-27 Renesas Mobile Corporation Procédé et appareil pour favoriser les communications automatisées
WO2016036581A1 (fr) * 2014-09-05 2016-03-10 Google Inc. Systèmes et procédés de réveil de dispositifs dans un réseau structuré

Cited By (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114745665A (zh) * 2019-02-26 2022-07-12 查德拉实验室有限责任公司 多接口应答器设备
EP4087329A1 (fr) * 2019-02-26 2022-11-09 Chadra Laboratories LLC Dispositif de transpondeur multi-interface
CN111654822A (zh) * 2019-02-26 2020-09-11 查德拉实验室有限责任公司 多接口应答器设备
EP3703431A3 (fr) * 2019-02-26 2020-11-25 Chadra Laboratories LLC Dispositif de transpondeur multi-interface
US11019567B2 (en) 2019-02-26 2021-05-25 Chadra Laboratories Llc Multi-interface transponder device-altering power modes
KR102393332B1 (ko) * 2019-02-26 2022-05-02 차드라 래보러토리즈 엘엘씨 멀티 인터페이스 트랜스폰더 디바이스
JP2020141403A (ja) * 2019-02-26 2020-09-03 アップル インコーポレイテッドＡｐｐｌｅ Ｉｎｃ． マルチインタフェーストランスポンダデバイス
KR20220058877A (ko) * 2019-02-26 2022-05-10 차드라 래보러토리즈 엘엘씨 멀티 인터페이스 트랜스폰더 디바이스
KR20200104254A (ko) * 2019-02-26 2020-09-03 차드라 래보러토리즈 엘엘씨 멀티 인터페이스 트랜스폰더 디바이스
CN111654822B (zh) * 2019-02-26 2022-05-13 查德拉实验室有限责任公司 多接口应答器设备
KR102514480B1 (ko) * 2019-02-26 2023-03-27 차드라 래보러토리즈 엘엘씨 멀티 인터페이스 트랜스폰더 디바이스
KR20230043812A (ko) * 2019-02-26 2023-03-31 차드라 래보러토리즈 엘엘씨 멀티 인터페이스 트랜스폰더 디바이스
US11638212B2 (en) 2019-02-26 2023-04-25 Chadra Laboratories Llc Multi-interface transponder device—altering power modes
US12279205B2 (en) 2019-02-26 2025-04-15 Apple Inc. Multi-interface transponder device-altering power modes
KR102664277B1 (ko) * 2019-02-26 2024-05-10 차드라 래보러토리즈 엘엘씨 멀티 인터페이스 트랜스폰더 디바이스
WO2023193193A1 (fr) * 2022-04-07 2023-10-12 北京小米移动软件有限公司 Procédé et dispositif de transmission d'informations de puissance de signal de réveil, et support de stockage lisible

Similar Documents

Publication Publication Date Title
US11558818B2 (en) Wake-up radio advertisement channel
US11812361B2 (en) Enhanced beacon frames in wireless communications
US10701688B2 (en) Dynamic channel bonding and multi-band aggregation
US12213115B2 (en) Enhanced high efficiency frames for wireless communications
CN110870335B (zh) 用于唤醒分组认证的动态签名
US11825414B2 (en) Group identification indication signaling
US11653208B2 (en) Invalid measurement indication in location measurement report
US10785819B2 (en) Maximum idle period for multi-band dual connectivity
US11902898B2 (en) Wake-up frame indication
WO2019055152A1 (fr) Préambule de récepteur d'éveil amélioré
WO2019040092A1 (fr) Double connectivité pour 6 ghz
US10750467B2 (en) Bidirectional location measurement report feedback
US11533757B2 (en) Scrambler initialization for multi-user clear to send transmission
WO2019005942A1 (fr) Protection de trame de réveil
WO2018194723A1 (fr) Trames de déclenchement améliorées pour communications sans fil
WO2018186919A1 (fr) Indication de services de réseautage sensible au voisinage
US20240323834A1 (en) Adaptive synchronization management system for enhancing wireless network performance
WO2018231734A1 (fr) Attribution d'identification de point d'accès dans un environnement coopératif
WO2019045855A1 (fr) Signalisation de réveil améliorée destinée à des communications sans fil

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18824678

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18824678

Country of ref document: EP

Kind code of ref document: A1

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载