+

WO2018160222A1 - Signalisation d'activation améliorée destinée à des communications sans fil - Google Patents

Signalisation d'activation améliorée destinée à des communications sans fil Download PDF

Info

Publication number
WO2018160222A1
WO2018160222A1 PCT/US2017/053538 US2017053538W WO2018160222A1 WO 2018160222 A1 WO2018160222 A1 WO 2018160222A1 US 2017053538 W US2017053538 W US 2017053538W WO 2018160222 A1 WO2018160222 A1 WO 2018160222A1
Authority
WO
WIPO (PCT)
Prior art keywords
wake
packet
access point
time
identifier
Prior art date
Application number
PCT/US2017/053538
Other languages
English (en)
Inventor
Po-Kai Huang
Minyoung Park
Robert Stacey
Original Assignee
Intel IP 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 IP Corporation filed Critical Intel IP Corporation
Publication of WO2018160222A1 publication Critical patent/WO2018160222A1/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
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/10—Small scale networks; Flat hierarchical networks
    • H04W84/12—WLAN [Wireless Local Area Networks]
    • 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 and methods for wireless communications and, more particularly, to enhanced wake-up signaling for wireless communications.
  • FIG. 1 is a network diagram illustrating an example network environment for enhanced wake-up signaling, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 2 illustrates an enhanced wake-up signal communication system, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 3A illustrates an enhanced wake-up communication process, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 3B illustrates an enhanced wake-up communication process, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 4 depicts an illustrative schematic diagram for enhanced wake-up signaling, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 5A illustrates a portion of an enhanced wake-up packet, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 5B illustrates a portion of an enhanced wake-up packet, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 6A depicts an information exchange for low-power wake-up signaling, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 6B illustrates a portion of a mode element for a wake-up packet using low- power wake-up signaling for multiple devices, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 7 A depicts a flow diagram of an illustrative process for enhanced wake-up signaling, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 7B depicts a flow diagram of an illustrative process for enhanced wake-up signaling, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 7C depicts a flow diagram of an illustrative process for enhanced wake-up signaling, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 8 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. 9 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.
  • Example embodiments described herein provide certain systems, methods, and devices for multicast wake-up packet transmission.
  • the following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them.
  • Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of other embodiments.
  • Embodiments set forth in the claims encompass all available equivalents of those claims.
  • Power consumption of a Wi-Fi device may be managed based at least in part on the enabling and disabling of ultra-low power operations.
  • a Wi-Fi device may have a low- power radio configuration that may receive a wake-up packet from a peer device when a low- power radio is on. By operating in an ultra-low power mode until receiving a wake-up packet, for example, the Wi-Fi device may conserve power.
  • the wake-up packet may indicate to the Wi-Fi device to activate a main radio that uses more power than the low-power radio.
  • a receiving device e.g., a Wi-Fi device
  • a receiving device may also include a low-power wake-up receiver (LP-WUR) to be active while the main 802.11 receiver is powered off.
  • LP-WUR low-power wake-up receiver
  • the LP-WUR may have different architecture and modulation schemes than a main 802.11 receiver, for example, and therefore may not be configured to receive 802.11 transmissions that the main 802.11 receiver may receive.
  • a Wi-Fi device may transmit and receive beacon frames that include information about a wireless network.
  • a beacon frame may refer to a legacy data frame used in higher- powered operating states of a Wi-Fi device by using, for example, an 802.11 transceiver.
  • Beacon frames and/or wake-up packets may be transmitted from a transmitting device to a receiving device, for example, on a periodic basis according to a time interval.
  • the transmitting device of a wake-up packet may be an access point (AP), and the receiving device of wake-up packet may be a non-AP station (STA).
  • AP access point
  • STA non-AP station
  • the AP may govern a number of STAs, and all the STAs may turn off an 802.11 main radio and turn on a low- power wake-up receiver (WURx or LP-WUR).
  • the AP may need to wake up these STAs at certain times to perform updates or to collect information from the STAs.
  • An AP may send one multicast wake-up packet to all the non-AP STAs and wake them up simultaneously. However, if not all STAs have their WURxs on during the same time period, then the AP may then send wake-up packets one after the other to wake up each STA (e.g., unicast wake- up packets).
  • the 802.1 lba standard may define enhanced wake-up signaling.
  • a physical AP may communicate with one or more receiving devices, such as STAs.
  • a physical AP may be associated with multiple networks (e.g., a personal home network, a work network, a guest network, etc.).
  • a physical AP may have multiple instances of virtual APs (e.g., API, AP2, AP3,..., APn) to support different STAs, which may be any type of wireless device, in one or more networks.
  • a virtual AP may be a software simulation of a physical AP that may form wireless connections with one or more STAs. Each network associated with a physical AP may be supported by a virtual AP.
  • STAs associated with a physical AP may be connected to different virtual APs.
  • STAs are connected to multiple virtual APs in 802.1 lax, in order to communicate information to each STA associated with the physical AP, a frame may be sent from each virtual AP to the respectively connected STAs. For example, in 802.1 lax, if three virtual APs are associated with a physical AP, the information may be replicated among three different frames - one for each virtual AP to send to connected STAs.
  • All virtual APs may belong to the same multiple basic service set identifier (BSSID) set, which may be a collection of cooperating APs, such that all of the APs use a common operating class, channel, and antenna connector.
  • BSSID basic service set identifier
  • a common AP identifier (APID), referred to as a transmitted BSSID, may also be defined so that an STA associated with any virtual AP in a multiple BSSID set may recognize a transmission from the corresponding virtual AP.
  • APID may be useful for a virtual AP in the BSSID set to send, for example, a trigger frame to solicit an uplink orthogonal frequency-division multiple access (UL OFDMA) transmission from STAs associated with the virtual AP.
  • UL OFDMA uplink orthogonal frequency-division multiple access
  • All STAs associated with one specific virtual AP in the multiple BSSID set may be associated with a separate group identifier.
  • the group identifier defined for a specific virtual AP in the multiple BSSID set may be recognized by all STAs associated with the virtual AP.
  • an AP may send a multicast wake-up packet to wake up all STAs associated with a physical AP.
  • the physical AP may want to wake up all STAs associated with any virtual AP of the multiple BSSID set to update information that is relevant to all STAs associated with the one member of the multiple BSSID set. For example, if a channel of the multiple BSSID set is changed and affects all members, then the physical AP may need to wake up all STAs associated with the physical AP to inform the STAs with an 802.11 frame that the channel has changed. Otherwise, for example, an STA may not find the corresponding AP in a channel once the AP has switched channels.
  • WUR beacon frame e.g., a wake-up receiver frame
  • a WUR beacon frame e.g., a wake-up receiver frame
  • STAs connected to a particular virtual AP one or more identifiers may be used to identify the STAs of the virtual AP to receive the WUR beacon frame. If all STAs are to receive the WUR beacon frame, a common identifier associated with all virtual APs of a physical AP may be used so that all STAs associated with the physical AP receive the WUR beacon frame.
  • Example embodiments of the present disclosure relate to systems, methods, and devices for enhanced wake-up signaling for wireless communication.
  • lower energy consumption may be achieved by adding an LP- WUR to a device to wake up the main radio system (e.g., IEEE 802.11 transceiver) of the device based on receiving a wake-up packet from another device.
  • the LP-WUR integrated in the circuitry of the device may be configured to receive a wake-up packet as an indication that the radio system of the device may need to be powered on in order to start receiving/sending data.
  • the LP-WUR may be based on, but not limited to, "on-off keying” (OOK), amplitude shift keying (ASK) or frequency shift keying (FSK) for signaling, and 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 other device may include a wake-up packet transmitter that generates a wake-up packet to be transmitted to the device.
  • the LP-WUR may improve power management by conserving power of a wireless device.
  • the wireless device may remain in an ultra-low power mode until receiving a wake-up packet.
  • a wake-up packet may signal to the wireless device to activate a higher power mode, which may refer to, for example, activating an 802.11 transceiver. Consequently, power consumption of the wireless device may be lowered by implementing the LP-WUR in an ultra-low power operating state and may prevent a user device from utilizing excess processing power until receiving a wake-up packet and activating (e.g., powering on) the 802.11 transceiver.
  • a multicast wake-up packet transmission system may facilitate one or more rules for the transmitting device (e.g., an AP) of a wake-up packet and all the receiving devices (e.g., STAs) of the wake-up packet, wherein the receiving devices agree to have wake-up packets with the transmitting device to activate receiving mechanisms during a common period of time in which the multicast wake-up packet may be transmitted.
  • the transmitting device e.g., an AP
  • the receiving devices e.g., STAs
  • a multicast wake-up packet system may facilitate that a transmitting device of a wake-up packet may signal a period of time where a multicast wake- up packet may be transmitted to every receiving device of the wake-up packet.
  • the signaling may be implicit signaling (e.g., defined by the wireless specification) or explicit signaling (e.g., indicated by one or more devices).
  • a multicast wake-up packet system may facilitate the communication of a wake-up packet for a receiving device whose WURx is on (e.g., powered on) during the signaled time period, the wake-up packet indicating to the receiving device to power on an 802.11 transceiver.
  • the receiving device of the wake-up packet may have its WURx on during the signaled time period.
  • the multicast wake-up packet system may introduce signaling from the receiving device of the wake-up packet to indicate if the WURx of the receiving device will be on during the signaled time period.
  • a unicast wake-up packet will be sent to the receiving device.
  • Sending a common wake- up packet to multiple receiving devices whose respective WURxs is on during a common time period may resolve the problem of higher wake-up packet transmission overhead when different WURxs of receiving devices have different wake-up periods.
  • a receiving device side which may not follow the suggested period, may also be implemented.
  • FIG. 1 is a network diagram illustrating an example network environment of enhanced 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) (AP) 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. 8 and/or the example machine/system of FIG. 9.
  • 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 non-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 ultrabook 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 incorporate
  • 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 may 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 may 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. l lg, 802.11 ⁇ , 802.1 lax), 5 GHz channels (e.g., 802.11 ⁇ , 802.1 lac, 802.1 lax), 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
  • the one or more user devices 120 may operate in an ultra-low power mode to conserve power.
  • the LP-WUR 146 of a user device 120 may be active while a main radio 144 may be inactive. Because the LP-WUR 146 may operate in a lower power state than the main radio 144, power may be conserved on the user device 120.
  • a user device 120 may indicate to an AP 102 that the user device 120 intends to activate the LP-WUR 146. To indicate that the user device 120 intends to activate the LP-WUR 146, the user device 120 may send a wake-up request to the AP 102. The AP 102 may receive one or more wake-up requests from one or more of the user devices 120.
  • the AP 102 and the user devices 120 may negotiate a common time to turn on the respective LP-WURs 146 at the user devices 120 so that the AP 102 may send a wake-up packet 140 in a multicast transmission to more than one of the user devices 120 at the common time (e.g., the negotiation may take place between the main radio 142 of the AP 102 and the main radio 144 of the user device(s) 120).
  • the common time may also be determined based on the 802.11 standard.
  • an AP 102 and a user device 120 may determine when the user device 120 will activate an LP-WUR 146 on the user device 120. For example, the user device 120 may indicate to the AP 102 that the user device 120 will turn on its LP-WUR 146. Based on agreed or predefined time period, the user device 120 may activate the LP-WUR 146 during the time period so that, for example, the LP-WUR 146 may receive a wake-up packet 140 from the AP 102.
  • an AP 102 and a user device 120 may determine when the user device 120 shall activate an LP-WUR 146 on the user device 120, or whether the user device 120 may have the option of whether or not to activate the LP-WUR 146 during the agreed time.
  • the user device 120 may signal to the AP 102 that the LP-WUR 146 will be active during the agreed time so that the LP-WUR 146 may receive a wake-up packet 140 from the AP 102.
  • the user device 120 may determine not to activate its LP-WUR 146 during the agreed time period.
  • the user device 120 may be executing one or more tasks that do not allow the user device 120 to enter a low- power mode with the LP-WUR 146 active.
  • the user device 120 may indicate to the AP 102 (e.g., with a signal) that the user device 120 will not activate its LP-WUR 146 during the agreed time.
  • an AP 102 may send, in a multicast transmission, one or more wake-up packets 140 to one or more user device(s) 120 whose LP-WURs 146 will be on during an agreed time period.
  • a wake-up packet 140 may signal to a user device 120 to activate a higher power mode, which may include activating a higher-powered main radio 144 on the user device 120.
  • an AP 102 may include a main radio 142 (e.g., an 802.11 radio), and the user device(s) 120 may include a main radio 144 and an LP-WUR 146.
  • the LP-WUR 146 may receive the wake-up packet 140 from the AP 102, and may activate the main radio 144. Once the main radio 144 is active, the user device(s) 120 may be able to receive 802.11 transmissions from the AP 102.
  • the AP 102 may send a wake-up packet 140 in a unicast transmission to such a user device 120.
  • the AP 102 and the user device 120 may agree upon such a time, or the user device 120 may indicate to the AP 102 when the user device 120 may activate its LP-WUR 146.
  • the LP-WUR 146 may use simple modulation schemes such as on-off keying (OOK), amplitude shift keying (ASK), or frequency shift keying (FSK) for signaling.
  • the LP-WUR 146 may use hardware and/or software components that may allow it to operate at a lower power consumption mode than a typical 802.11 radio component (e.g., main radios 142 and 144). Because of the hardware and/or modulation schemes, for example, the wake-up packet may be formatted so that the LP-WUR 146 may receive the wake-up packet 140, but the main radio 144 may not. Likewise, some 802.11 transmissions may not be received by the LP-WUR 146.
  • OOK on-off keying
  • ASK amplitude shift keying
  • FSK frequency shift keying
  • the LP-WUR 146 may be active, and the user device 120 may be in a low-power mode when the user device 120 does not need to receive an 802.11 transmission, and the user device 120 may activate the main radio 144 when the user device 120 needs to receive an 802.11 transmission that the LP-WUR 146 may not receive.
  • the LP-WUR 146 may be constantly active (e.g., power ON state) on the user device 120 in order to receive a wake-up communication (e.g., the wake-up packet 140).
  • the AP 102 and the user device 120 may negotiate a time for the user device 120 to turn on the LP-WUR 146.
  • the AP 102 may begin transmitting the wake-up packet 140 using a low-power communication method at the agreed-upon time.
  • the LP-WUR 146 may detect and/or decode the wake-up packet and may determine whether the wake-up packet is destined for the user device 120. If the LP-WUR 146 (or other portions of the user device 120) determines that the receiver address (RA) field of the media access control (MAC) header from the wake-up packet 140 matches the address of the user device 120, the LP-WUR 146 may then send a wake-up packet 140 to the main radio 144 to power on (e.g., ON/OFF state) its circuitry.
  • RA receiver address
  • MAC media access control
  • the wake-up packet 140 may include timing information such as a wake-up period.
  • the wake-up period may be a period of time that the user device 120 may need to have when devices, such as the AP 102, may be sending data to the main radio 144 of the user device 120.
  • the user device 120 may power off some or all of its circuitry (e.g., main radio 144) to reduce power consumption and preserve the life of its battery.
  • FIG. 2 illustrates a wake-up signal communication system 200, in accordance with one or more example embodiments of the present disclosure.
  • a physical AP 201 may include one or more virtual APs (e.g., virtual APs 202, 204, 206) which may communicate with one or more STAs (e.g., STAs 208, 210, 212, 214, 216, 218).
  • Virtual APs may represent different networks (e.g., a personal home network, a work network, a guest network, etc.).
  • virtual AP 202 may communicate with STA 208 and STA 210.
  • Virtual AP 204 may communicate with STA 212 and STA 214.
  • Virtual AP 206 may communicate with STA 216 and STA 218.
  • Physical AP 201 may have multiple virtual APs to support different STAs, which may be any type of wireless device, in one or more networks. Each network associated with a physical AP 201 may be supported by a virtual AP. As such, STAs associated with a physical AP 201 may be connected to different virtual APs.
  • STAs When STAs are connected to multiple virtual APs in 802.1 lax, in order to communicate information to each STA associated with the physical AP 201, a frame may be sent from each virtual AP to the respectively connected STAs. For example, in 802.1 lax, if three virtual APs are associated with a physical AP 201, the information may be replicated among three different frames - one for each virtual AP to send to connected STAs.
  • All virtual APs may belong to the same BSSID set.
  • a common APID referred to as a transmitted BSSID, may also be defined so that an STA associated with any virtual AP in a multiple BSSID set may recognize a transmission from the corresponding virtual AP.
  • the use of an APID may be useful for a virtual AP in the BSSID set to send, for example, a trigger frame to solicit an uplink orthogonal frequency-division multiple access (UL OFDMA) transmission from STAs associated with the virtual AP.
  • UL OFDMA uplink orthogonal frequency-division multiple access
  • All STAs associated with one specific virtual AP in the multiple BSSID set may be associated with a separate group identifier.
  • the group identifier defined for a specific virtual AP in the multiple BSSID set may be recognized by all STAs associated with the virtual AP.
  • an AP may send a multicast wake-up packet to wake up all STAs associated with a physical AP 201.
  • the physical AP 201 may want to wake up all STAs associated with any virtual AP of the multiple BSSID set to update information that is relevant to all STAs associated with the one member of the multiple BSSID set. If a channel of the multiple BSSID set is changed and affects all members, for example, then the physical AP 201 may need to wake up all STAs associated with the physical AP 201 to inform the STAs with an 802.11 frame that the channel has changed.
  • identifiers may be used to identify the STAs of the virtual AP to receive the WUR beacon frame. If all STAs are to receive the WUR beacon frame, a common identifier associated with all virtual APs of a physical AP 201 may be used so that all STAs associated with the physical AP 201 receive the WUR beacon frame.
  • FIG. 3A illustrates a wake-up communication process 300, in accordance with one or more example embodiments of the present disclosure.
  • the STAs e.g., STAs 304, 306, 308, 310) may not have their respective WURxs (e.g., LP-WUR 146 of FIG. 1) on during the same time period (e.g., WURx ON).
  • STA 304 may have a WURx ON period 320, followed by a WURx OFF period 322, followed by a WURx ON period 324, followed by a WURx OFF period 326.
  • STA 306 may have a WURx OFF period 328, followed by a WURx ON period 330, followed by a WURx OFF period 332, followed by a WURx ON period 334, followed by a WURx OFF period 336.
  • STA 308 may have a WURx OFF period 338, followed by a WURx ON period 340, followed by a WURx OFF period 342, followed by a WURx ON period 344, followed by a WURx OFF period 346.
  • STA 310 may have a WURx OFF period 348, followed by a WURx ON period 350, followed by a WURx OFF period 352, followed by a WURx ON period 354.
  • the WURx ON periods of STA 304, STA 306, STA 308, and STA 310 may not align (e.g., WURx ON period 320, WURx ON period 330, WURx ON period 340, and WURx ON period 350 may not all overlap in a common time period). Because there may not be a common time period when all the STAs have their respective WURxs on, the AP 302 may transmit a wake-up packet during each WURx ON period (e.g., WURx ON period 320, WURx ON period 330, WURx ON period 340, WURx ON period 350). As shown in FIG.
  • a first wake-up packet 312 may be sent during WURx ON period 320 for STA 304.
  • a second wake-up packet 314 may be sent during WURx ON period 330 for STA 306.
  • a third wake-up packet 316 may be sent during WURx ON period 340 for STA 308.
  • a fourth wake-up packet 318 may be sent during WURx ON period 350 for STA 310.
  • the number of wake-up packets needed to wake up multiple STAs may be reduced by coordinating the WURx ON period(s) for multiple STAs.
  • the AP 302 may be a physical AP (e.g., physical AP 201 of FIG. 2) or a virtual AP (e.g., virtual APs 202, 204, 206 of FIG. 2).
  • FIG. 3B illustrates a wake-up communication process 360, in accordance with one or more example embodiments of the present disclosure.
  • AP 362 may be in communication with STA 364, STA 366, STA 368, and STA 370.
  • the AP 362 may send a multicast wake-up packet 372 during a common time period when the STAs each have their WURx (e.g., LP-WUR 146 of FIG. 1) active.
  • the AP 362 and the STAs may set the common period for each STA to turn on its respective WURx.
  • STA 364 may have a WURx ON period 374, followed by a WURx OFF period 376, followed by a WURx ON period 378, followed by a WURx OFF period 380.
  • STA 366 may have a WURx ON period 382, followed by a WURx OFF period 384, followed by a WURx ON period 386, followed by a WURx OFF period 388.
  • STA 368 may have a WURx ON period 390, followed by a WURx OFF period 392, followed by a WURx ON period 394, followed by a WURx OFF period 395.
  • STA 370 may have a WURx ON period 396, followed by a WURx OFF period 397, followed by a WURx ON period 398, followed by a WURx OFF period 399.
  • the WURx ON periods of the STAs may exist during a common time.
  • WURx ON period 374, WURx ON period 382, WURx ON period 390, and WURx ON period 396 may exist during a common time period.
  • WURx ON period 378, WURx ON period 386, WURx ON period 394, and WURx ON period 398 may exist during a common time period.
  • each STA (or at least multiple STAs) may have its WURx active during a common time period (e.g., WURx ON periods 374, 382, 390, 396, or WURx ON periods 378, 386, 394, 398)
  • the AP 362 may generate a multicast wake-up packet 372 to transmit to each STA with an active WURx during the common time period.
  • the multicast wake-up packet 372 may allow the AP 362 to reduce the number of wake-up packet transmissions needed to reach each STA.
  • FIG. 4 depicts an illustrative schematic diagram 400 for multicast wake-up packet transmission, in accordance with one or more example embodiments of the present disclosure.
  • a receiving device 402 e.g., user device 120 of FIG. 1
  • a sending device 404 e.g., AP 102 of FIG. 1
  • a multicast wake-up packet 406, 408 may wake up the main radio (e.g., main radio 144) of device 402.
  • a target wake-up beacon transmission time (e.g., TWBTT 410, 412, 414) may indicate a beginning and end time for WURx beacon interval 416 during which the multicast wake-up packet 404, 406 may be transmitted.
  • the TWBTT 410, 412, 414 may indicate when a wake-up beacon 418, 420, 422 may be sent to the device 402 to start a respective TWBTT 410, 412, 414.
  • the multicast wake-up packet 404, 406 may be sent anytime during a respective beacon interval 416.
  • the signaling of the TWBTT 410, 412, 414 may be achieved by implicit or explicit signaling.
  • implicit signaling an IEEE standard may define the respective TWBTT 410, 412, 414.
  • explicit signaling the sending device 404 may signal the respective TWBTT 410, 412, 414 to the receiving device 402.
  • the respective TWBTT 410, 412, 414 may be negotiated between the sending device 404 and the receiving device 402.
  • the signaling may be included in a frame, which may be part of a WURx request/response or any other management frame.
  • TSF time synchronization factor
  • mod x e.g., mod x
  • the receiving device 402 of the multicast wake-up packet 406, 408 may have its WURx on during the signaled beacon interval 416.
  • the receiving device 402 may, for example, follow a schedule agreed to with, or provided from, the sending device 404 for multicast transmission.
  • the receiving device 402 of the multicast wake-up packet 406, 408 may decide whether to turn its WURx on during the beacon interval 416. This option may provide flexibility on the receiving device 402 side.
  • a multicast wake-up packet 406, 408 transmission system may introduce signaling from the receiving device 402 of a multicast wake-up packet 406, 408 to indicate if the receiving device 402 will be awake during the beacon interval 416. The signaling may be included in a frame, and the frame may be included in the WURx request/response or any other management frame. If the receiving device 402 signals that its main radio will not be awake during the signaled time period, then a unicast wake-up packet instead may be sent to the receiving device 402 to indicate to the receiving device 402 to activate the main radio.
  • FIG. 5A illustrates a portion 500 of an enhanced wake-up packet, in accordance with one or more example embodiments of the present disclosure.
  • the portion 500 of a wake-up packet may be used for low-power wake-up signaling of multiple STAs (e.g., user devices 120 of FIG. 1).
  • the wake-up packet may have a preamble 502 and a media access control (MAC) layer 504.
  • the MAC layer 504 may include a source address (SA) 506, a destination address (DA) 508, other fields 510, and a frame check sequence (FCS) 512.
  • SA source address
  • DA destination address
  • FCS frame check sequence
  • an STA may wake up its main radio (e.g., main radio 144 of FIG. 1) after receiving a wake-up packet and considering at least the SA 506 and the DA 508.
  • the SA 506 may represent an identifier of one or more virtual APs (e.g., virtual APs 202, 204, 206 of FIG. 2).
  • the identifier corresponds to a virtual AP
  • any STA connected to that virtual AP may receive the wake-up packet.
  • the SA 506 identifier may be for a single virtual AP or multiple virtual APs, including a common identifier for all virtual APs associated with a physical AP (e.g., physical AP 201 of FIG. 2).
  • the SA 506 identifier APID1 may be unique to a first virtual AP (e.g., virtual AP 202 in FIG. 2)
  • the SA 506 identifier APID2 may be unique to a second virtual AP (e.g., virtual AP 204 in FIG. 2)
  • the SA 506 identifier APID3 may be unique to a third virtual AP (e.g., virtual AP 206 in FIG. 2).
  • the SA 506 identifier APID 0 may be a common identifier for all virtual APs associated with a physical AP, including the first virtual AP, the second virtual AP, and the third virtual AP.
  • the SA 506 identifiers may represent multiple virtual APs.
  • SA 506 identifier APID4 may represent the first virtual AP and the second virtual AP.
  • SA 506 identifier APID5 may represent the first virtual AP and the third virtual AP.
  • SA 506 identifier APID6 may represent the second virtual AP and the third virtual AP.
  • a physical AP may intend to send a wake-up packet to any STA associated with any virtual APs associated with the physical AP.
  • the wake-up packet may be received by any STA associated with a network of the physical AP. If the physical AP intends to send a wake-up packet to only the STAs associated with a first virtual AP, then the wake-up packet may include the SA 506 identifier APID1.
  • the format of the portion 500 of the wake-up packet shown in FIG. 5A may also include a DA 508 identifier, which may represent any or all STAs associated with the virtual AP(s) identified by the SA 506 identifier.
  • a DA 508 identifier may represent any or all STAs associated with the virtual AP(s) identified by the SA 506 identifier.
  • the SA 506 identifier is APID1 for the first virtual AP
  • the DA 508 group identifier e.g., group ID
  • the wake-up packet may be received by all STAs associated with the first virtual AP.
  • the wake-up packet may include the SA 506 identifier APID1, and the DA 508 identifier group ID 0.
  • the wake-up packet may be received by all STAs of a first virtual AP.
  • the wake-up packet may include the SA 506 identifier APID2, and the DA 508 identifier group ID 0.
  • the wake-up packet may be received by all STAs of a second virtual AP.
  • the wake-up packet may include the SA 506 identifier APID3, and the DA 508 identifier group ID 0.
  • the wake-up packet may be received by all STAs of a third virtual AP.
  • the wake-up packet may include the SA 506 identifier APID4, and the DA 508 identifier group ID 0.
  • the wake-up packet may be received by all STAs of a first virtual AP and of a second virtual AP.
  • the wake-up packet may include the SA 506 identifier APID5, and the DA 508 identifier group ID 0.
  • the wake-up packet may be received by all STAs of a first virtual AP and of a third virtual AP.
  • the wake-up packet may include the SA 506 identifier APID6, and the DA 508 identifier group ID 0.
  • the wake-up packet may be received by all STAs of a second virtual AP and of a third virtual AP.
  • the STAs associated with a physical AP may have WURx ON time periods that are not synchronized with each other (e.g., the scenario shown in FIG. 3A).
  • the AP may need to synchronize at least some of the STAs to have one or more common time periods during which the LP- WURs of the STAs are on so that the AP may send a multicast wake-up packet (e.g., the scenario shown in FIG. 3B).
  • the AP may send a multicast wake-up packet to the multiple STAs using the format of the portion 500 of the wake-up packet shown in FIG. 5A.
  • FIG. 5B illustrates a portion 550 of an enhanced wake-up packet, in accordance with one or more example embodiments of the present disclosure.
  • the portion 550 of a wake-up packet may be used for low-power wake-up signaling of multiple STAs (e.g., user devices 120 of FIG. 1).
  • the wake-up packet may have a preamble 552 and a MAC layer 554.
  • the MAC layer 554 may include a DA 556, other fields 558, and an FCS 560.
  • an STA may wake up its main radio after receiving a wake-up packet and after considering at least the DA 556 of the wake-up packet.
  • the DA 556 may represent an identifier (e.g., group ID) that corresponds with one or more virtual APs (e.g., virtual APs 202, 204, 206 of FIG. 2) associated with a physical AP (e.g., physical AP 201 of FIG. 2). If the DA 556 uses Group ID1 to associate with a first virtual AP (e.g., virtual AP 202 of FIG. 2), then any STA connected to the first virtual AP may receive a wake-up packet that includes Group ID1 in the DA 556.
  • group ID e.g., group ID
  • each virtual AP may define a common Group ID 0 to be recognized by all STAs, and the Group ID may be included in the DA 556.
  • DA 556 may include Group ID1 to be recognized by STAs connected to a first virtual AP.
  • DA 556 may include Group ID2 to be recognized by STAs connected to a second virtual AP.
  • DA 556 may include Group ID3 to be recognized by STAs connected to a third virtual AP.
  • DA 556 may include Group ID4 to be recognized by STAs connected to the first virtual AP and to the second virtual AP.
  • DA 556 may include Group ID5 to be recognized by STAs connected to the first virtual AP and to the third virtual AP.
  • DA 556 may include Group ID6 to be recognized by STAs connected to the second virtual AP and to the third virtual AP.
  • a wake-up packet may include Group ID 0 in DA 556. Any STA associated with the physical AP may receive the wake-up packet.
  • a wake-up packet may include Group ID1 in DA 556. Any STA associated with the first virtual AP may receive the wake-up packet.
  • a wake-up packet may include Group ID2 in DA 556. Any STA associated with the second virtual AP may receive the wake-up packet. [00110] In one or more embodiments, a wake-up packet may include Group ID3 in DA 556. Any STA associated with the third virtual AP may receive the wake-up packet.
  • a wake-up packet may include Group ID4 in DA 556. Any STA associated with the first virtual AP and the second virtual AP may receive the wake-up packet.
  • a wake-up packet may include Group ID5 in DA 556. Any STA associated with the first virtual AP and the third virtual AP may receive the wake-up packet.
  • a wake-up packet may include Group ID6 in DA 556. Any STA associated with the second virtual AP and the third virtual AP may receive the wake-up packet.
  • the STAs associated with a physical AP may have WURx ON time periods that are not synchronized with each other (e.g., the scenario shown in FIG. 3A).
  • the AP may need to synchronize at least some of the STAs to have one or more common time periods during which the LP- WURs of the STAs are on so that the AP may send a multicast wake-up packet (e.g., the scenario shown in FIG. 3B).
  • the AP may send a multicast wake-up packet to the multiple STAs using the format of the portion 550 of the wake-up packet shown in FIG. 5B.
  • FIG. 6A depicts an information exchange 600 for low-power wake-up signaling, in accordance with one or more example embodiments of the present disclosure.
  • virtual AP 602 may be in communication with STA 604, virtual AP 606 may be in communication with STA 608, and virtual AP 610 may be in communication with STA 612.
  • STA 604 may send a wake-up receiver request 614 to virtual AP 602.
  • the wake-up receiver request 614 may be sent with a main 802.11 radio (e.g., main radio 144 of FIG. 1), and may indicate that the STA 604 may enter a low-power mode with an active LP-WUR (e.g., LP-WUR 146 of FIG. 1).
  • virtual AP 602 may send a wake-up receiver response 616 (e.g., wake-up packet 140 of FIG. 1), which may include one or more identifiers indicating which STAs, including STA 604, are to receive the wake-up packet and activate their main 802.11 radios.
  • STA 608 may send a wake-up receiver request 618 to virtual AP 606.
  • the wake-up receiver request 618 may be sent with a main 802.11 radio, and may indicate that the STA 608 may enter a low-power mode with an active LP-WUR.
  • virtual AP 606 may send a wake-up receiver response 620, which may include one or more identifiers indicating which STAs, including STA 608, are to receive the wake-up packet and activate their main 802.11 radios.
  • STA 612 may send a wake-up receiver request 622 to virtual AP 610.
  • the wake-up receiver request 622 may be sent with a main 802.11 radio, and may indicate that the STA 612 may enter a low-power mode with an active LP-WUR.
  • virtual AP 610 may send a wake-up receiver response 624, which may include one or more identifiers indicating which STAs, including STA 612, are to receive the wake-up packet and activate their main 802.11 radios.
  • FIG. 6B illustrates a portion of a mode element 650 for a wake-up packet using low- power wake-up signaling for multiple devices, in accordance with one or more example embodiments of the present disclosure.
  • the portion of the mode element 650 for a wake-up packet using low-power wake-up signaling for multiple devices may include an element ID 652, a length 654, an action type 656, an APID 658, a Common APID 660, a Group ID 662, and other relevant information.
  • APID 658 may be included in an SA (e.g., SA 506 of FIG. 5A) and may identify one or more virtual APs (e.g., virtual APs 202, 204, 206 of FIG. 2) whose connected STAs are intended to receive the wake-up packet.
  • an APID 658 of 1 may correspond to a first virtual AP
  • an APID 658 of 2 may correspond to a second virtual AP, and so forth.
  • Common APID 660 may be included in an SA and may identify all virtual APs associated with a physical AP (e.g., physical AP 201 of FIG. 2) whose connected STAs are intended to receive the wake-up packet. Common APID 660 may correspond to an SA value of 0 so that any STA of any virtual AP associated with the physical AP may receive the wake-up packet.
  • Group ID may be included in a DA (e.g., DA 508 of FIG. 5A or DA 556 of FIG. 5B), and may represent any STAs associated with a virtual AP.
  • Group ID may indicate that all STAs associated with one or more virtual APs indicated in an SA are intended to receive a wake-up packet. If there is no SA (e.g., the format in FIG. 3B), then Group ID may represent one or more virtual APs whose STAs are intended to receive the wake-up packet.
  • the STAs associated with a physical AP may have WURx ON time periods that are not synchronized with each other (e.g., the scenario shown in FIG. 3A).
  • the AP may need to synchronize at least some of the STAs to have one or more common time periods during which the LP- WURs of the STAs are on so that the AP may send a multicast wake-up packet (e.g., the scenario shown in FIG. 3B).
  • the AP may send a multicast wake-up packet to the multiple STAs using the format of the portion of the mode element 650 of the wake-up packet shown in FIG. 6B.
  • FIG. 7 A illustrates a flow diagram of an illustrative process 700 for enhanced wake-up signaling, in accordance with one or more embodiments of the disclosure.
  • one or more processors of a device may determine a multicast wake-up packet (e.g., wake-up packet 140 of FIG. 1) to be sent to one or more receiving devices (e.g., the user device(s) 120 of FIG. 1).
  • the multicast wake-up packet may be used to indicate to the one or more receiving devices to activate their respective main radios (e.g., main radio 144 of FIG. 1).
  • the multicast wake-up packet may be determined for one or more groups of receiving devices (e.g., STAs 208, 210 of FIG. 2), or for all receiving devices associated with the device.
  • the one or more processors of the device may determine a common period of time for the one or more receiving devices to power on their respective low-power receivers (e.g., LP-WUR 146 of FIG. 1).
  • the common period of time may be negotiated between the device and the one or more receiving devices. For example, when the one or more receiving devices request the device to activate their respective low-power receivers, the device may explicitly signal to the one or more receiving devices when the common period of time will be. Signaling of the common time period may also be implicit (e.g., defined by a technical standard) so that the one or more receiving devices know when they should activate their respective low-power receivers.
  • the one or more processors of the device may cause the device to send the multicast wake-up packet to the one or more receiving devices during the common time period determined at block 704.
  • the one or more receiving devices that have activated their respective low-power receivers may receive the multicast wake-up packet indicating that the low-power receivers should activate their main radios.
  • FIG. 7B illustrates a flow diagram of an illustrative process 730 for enhanced wake-up signaling, in accordance with one or more embodiments of the disclosure.
  • one or more processors of one or more receiving devices may identify a first wake-up packet.
  • the wake-up packet may be a multicast wake-up packet sent to the one or more receiving devices from a device (e.g., AP 102 of FIG. 1).
  • the AP may be a physical AP (e.g., physical AP 201 of FIG. 2) or may represent a virtual AP (e.g., virtual APs 202, 204, 206 of FIG. 1) of a physical AP.
  • the one or more receiving devices may be associated with the physical AP and a virtual AP of the physical AP.
  • the one or more receiving devices may receive and identify the first wake-up packet when their respective low-power radios (e.g., LP-WUR 146 of FIG. 1) are active.
  • the one or more processors of the one or more receiving devices may determine a first identifier (e.g., SA 506, DA 508 of FIG. 5A; DA 556 of FIG. 5B) of the first wake-up packet.
  • the first identifier may indicate a group of the one or more receiving devices to receive the first wake-up packet.
  • the group identifier may indicate a common group of the one or more receiving devices (e.g., all of the one or more receiving devices associated with a physical AP), or may indicate one or groups of one or more receiving devices associated with a physical AP (e.g., groups of receiving devices associated with one or more virtual APs of the physical AP as shown in FIG. 2).
  • the one or more processors of the one or more receiving devices may determine that the first wake-up packet indicates to each of the one or more receiving devices to activate a main radio (e.g., main radio 144 of FIG. 1) on each of the one or more receiving devices.
  • a main radio e.g., main radio 144 of FIG. 1
  • the one or more processors of the one or more receiving devices may activate the main radio on the respective receiving device.
  • Activating the main radio may include sending an activation signal to the main radio and powering on the main radio.
  • the one or more receiving devices associated with the process 730 may be in a low-power mode with their respective low-power radios on at a common time (e.g., as shown in FIG. 3B).
  • the common time for having on low-power radios of the one or more receiving devices may be a result of the process 700 of FIG. 7A.
  • FIG. 7C illustrates a flow diagram of an illustrative process 760 for enhanced wake-up signaling, in accordance with one or more embodiments of the disclosure.
  • one or more processors of one or more devices may determine a first receiving device and a second receiving device to receive a wake-up packet.
  • the wake-up packet may be a multicast wake-up packet capable of reaching at least the first and second receiving devices to indicate to the first and second devices to activate a main radio (e.g., main radio 144 of FIG. 1).
  • the first and second receiving devices may be associated with a physical AP (e.g., physical AP 201 of FIG. 2) and may be associated with one or more virtual APs (e.g., virtual APs 202, 204, 206 of FIG. 2) of the physical AP.
  • the first and second receiving devices may belong to a common virtual AP, and thus may be part of a group of receiving devices to receive the wake-up packet.
  • the first and second receiving devices may be in a low-power mode with their respective low-power radios (e.g., LP-WUR 146 of FIG. 1) active at a time set by a technical standard or as part of a negotiation with the one or more devices.
  • the time that the first and second receiving devices have their respective low-power radios active may be a common time period determined by the process 700 of FIG. 7A.
  • the one or more processors of the one or more devices may determine the wake-up packet.
  • the wake-up packet may indicate to the first and second devices that they should activate their respective main radios (e.g., main radio 144 of FIG. 1).
  • the wake-up packet may include one or more identifiers.
  • the one or more identifiers may indicate one or more groups that include the first and second devices (e.g., SA 506, DA 508 of FIG. 5A; DA 556 of FIG. 5B).
  • the one or more processors of the one or more devices may cause the one or more devices to send the wake-up packet.
  • the wake-up packet may be sent at a common time as determined by the process 700 of FIG. 7A, and may be sent to the one or more groups of devices as indicated by the one or more identifiers determined at block 764.
  • FIG. 8 shows a functional diagram of an exemplary communication station 800 in accordance with some embodiments.
  • FIG. 8 illustrates a functional block diagram of a communication station that may be suitable for use as an AP 102 (FIG. 1) or a user device 120 (FIG. 1) in accordance with some embodiments.
  • the communication station 800 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
  • the communication station 800 may include communications circuitry 802 and a transceiver 810 for transmitting and receiving signals to and from other communication stations using one or more antennas 801.
  • the transceiver 810 may be a device comprising both a transmitter and a receiver that are combined and share common circuitry (e.g., communication circuitry 802).
  • the communications circuitry 802 may include amplifiers, filters, mixers, analog to digital and/or digital to analog converters.
  • the transceiver 810 may transmit and receive analog or digital signals.
  • the transceiver 810 may allow reception of signals during transmission periods. This mode is known as full-duplex, and may require the transmitter and receiver to operate on different frequencies to minimize interference between the transmitted signal and the received signal.
  • the transceiver 810 may operate in a half- duplex mode, where the transceiver 810 may transmit or receive signals in one direction at a time.
  • the communications circuitry 802 may include circuitry that may 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 800 may also include processing circuitry 806 and memory 808 arranged to perform the operations described herein.
  • the communications circuitry 802 and the processing circuitry 806 may be configured to perform operations detailed in FIGs. 2, 3A, 3B, 4, 5A, 5B, 6A, 6B, 7A, 7B, and 7C.
  • the communications circuitry 802 may be arranged to contend for a wireless medium and configure frames or packets for communicating over the wireless medium.
  • the communications circuitry 802 may be arranged to transmit and receive signals.
  • the communications circuitry 802 may also include circuitry for modulation/demodulation, upconversion/downconversion, filtering, amplification, etc.
  • the processing circuitry 806 of the communication station 800 may include one or more processors.
  • two or more antennas 801 may be coupled to the communications circuitry 802 arranged for sending and receiving signals.
  • the memory 808 may store information for configuring the processing circuitry 806 to perform operations for configuring and transmitting message frames and performing the various operations described herein.
  • the memory 808 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 808 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 800 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 800 may include one or more antennas 801.
  • the antennas 801 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 800 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 800 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 800 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 800 may include one or more processors and may be configured with instructions stored on a computer-readable storage device.
  • FIG. 9 illustrates a block diagram of an example of a machine 900 or system upon which any one or more of the techniques (e.g., methodologies) discussed herein may be performed.
  • the machine 900 may operate as a standalone device or may be connected (e.g., networked) to other machines.
  • the machine 900 may operate in the capacity of a server machine, a client machine, or both in server-client network environments.
  • the machine 900 may act as a peer machine in peer-to-peer (P2P) (or other distributed) network environments.
  • P2P peer-to-peer
  • the machine 900 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 network router, a switch or bridge
  • network router e.g., a router, a router, 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.
  • 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 (
  • 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 executions 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 (e.g., computer system) 900 may include a hardware processor 902 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 904 and a static memory 906, some or all of which may communicate with each other via an interlink (e.g., bus) 908.
  • the machine 900 may further include a power management device 932, a graphics display device 910, an alphanumeric input device 912 (e.g., a keyboard), and a user interface (UI) navigation device 914 (e.g., a mouse).
  • UI user interface
  • the graphics display device 910, alphanumeric input device 912, and UI navigation device 914 may be a touch screen display.
  • the machine 900 may additionally include a storage device (i.e., drive unit) 916, a signal generation device 918 (e.g., a speaker), an Enhanced Wake-Up device 919, a network interface device/transceiver 920 coupled to antenna(s) 930, and one or more sensors 928, such as a global positioning system (GPS) sensor, a compass, an accelerometer, or other sensor.
  • GPS global positioning system
  • the machine 900 may include an output controller 934, 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.)).
  • the storage device 916 may include a machine readable medium 922 on which is stored one or more sets of data structures or instructions 924 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein.
  • the instructions 924 may also reside, completely or at least partially, within the main memory 904, within the static memory 906, or within the hardware processor 902 during execution thereof by the machine 900.
  • the hardware processor 902, the main memory 904, the static memory 906, or the storage device 916 may constitute machine-readable media.
  • the Enhanced Wake-Up device 919 may carry out or perform any of the operations and processes (e.g., the process 700 of FIG. 7A, the process 730 of FIG. 7B, and the process 760 of FIG. 7C) described and shown above.
  • the Enhanced Wake-Up device 919 may determine a multicast wake-up packet to be sent to one or more devices, wherein the wake-up packet is formatted for respective low-power receivers of the one or more devices.
  • the Enhanced Wake-Up device 919 may determine a common period of time for powering on the respective low-power receivers of the one or more devices.
  • the Enhanced Wake-Up device 919 may send the multicast wake-up packet to the one or more devices at the common period of time.
  • the Enhanced Wake-Up device 919 may determine the common period of time in accordance with an IEEE 802.11 standard.
  • the Enhanced Wake-Up device 919 may send one or more messages indicating the common time.
  • the Enhanced Wake-Up device 919 may identify a signal from at least one of the one or more devices, wherein the signal indicates that the at least one of the one or more devices will not power on its low-power receiver during the common period of time.
  • the Enhanced Wake-Up device 919 may send a unicast wake-up packet to at least one of the one or more devices. [00165] In one or more embodiments, the Enhanced Wake-Up device 919 may identify one or more wake-up requests from the one or more devices, wherein the common time is based at least in part on the one or more wake-up requests.
  • the Enhanced Wake-Up device 919 may determine a first period of time for powering on a low-power radio.
  • the Enhanced Wake-Up device 919 may identify a wake-up packet formatted for the low-power radio.
  • the Enhanced Wake-Up device 919 may determine that the wake-up packet indicates a second period of time for powering on a main radio.
  • the Enhanced Wake-Up device 919 may identify one or more messages indicating the first time.
  • the Enhanced Wake-Up device 919 may activate the main radio during the second time period.
  • the Enhanced Wake-Up device 919 may activate the low-power radio during the first time period, wherein the wake-up packet is sent in a multicast transmission during the first time period.
  • the Enhanced Wake-Up device 919 may indicate that the low-power radio will not be activated during the first time period, wherein the wake- up packet is sent in a unicast transmission.
  • the Enhanced Wake-Up device 919 may send a wake-up request to activate the low-power radio, wherein the first time period is based at least in part on the wake-up request.
  • the Enhanced Wake-Up device 919 may determine a multicast wake-up packet to be sent to one or more devices, wherein the wake-up packet is formatted for respective low-power receivers of the one or more devices.
  • the Enhanced Wake-Up device 919 may determine a common period of time for powering on the respective low-power receivers of the one or more devices.
  • the Enhanced Wake-Up device 919 may send the multicast wake-up packet to the one or more devices at the common period of time.
  • the Enhanced Wake-Up device 919 may identify a first wake-up packet that includes a first identifier, wherein the first wake-up packet is formatted for a low-power wake-up receiver of the device and is sent in a multicast transmission. [00178] In one or more embodiments, the Enhanced Wake-Up device 919 may determine that the first identifier is for the device.
  • the Enhanced Wake-Up device 919 may determine that the first wake-up packet indicates to the device to activate a main radio at a first time.
  • the Enhanced Wake- Up device 919 may activate the main radio at the first time.
  • the Enhanced Wake-Up device 919 may determine a second time when the low-power wake-up receiver will be on.
  • the Enhanced Wake-Up device 919 may activate the low-power wake-up receiver at the second time, wherein the first wake-up packet is sent based on the second time.
  • the Enhanced Wake-Up device 919 may identify a second wake-up packet that includes a second identifier, wherein the second wake-up packet is formatted for the low-power wake-up receiver.
  • the Enhanced Wake-Up device 919 may determine that the second identifier is not for the device.
  • the Enhanced Wake-Up device 919 may discard the second wake-up packet.
  • the Enhanced Wake-Up device 919 may determine that the second identifier is for all devices connected to a third virtual access point for a physical access point, wherein the device is not connected to the third virtual access point.
  • the Enhanced Wake-Up device 919 may determine a first receiving device and a second receiving device to receive a wake-up packet formatted for a respective low-power wake-up receiver at each of the first receiving device and the second receiving device.
  • the Enhanced Wake-Up device 919 may determine the wake-up packet, wherein the wake-up packet comprises a first identifier for a first virtual access point of a physical access point, and wherein the first receiving device and the second receiving device are connected to the first virtual access point.
  • the Enhanced Wake-Up device 919 may send the wake-up packet in a multicast transmission.
  • the Enhanced Wake-Up device 919 may determine a third receiving device to receive the wake-up packet, wherein the third receiving device is connected to a second virtual access point of the physical access point. [00191] In one or more embodiments, the Enhanced Wake-Up device 919 may determine the first identifier, wherein the first identifier indicates a destination address for the first receiving device and for the second receiving device.
  • the Enhanced Wake-Up device 919 may determine a second identifier, wherein the second identifier indicates a source address for the first virtual access point.
  • the Enhanced Wake-Up device 919 may determine a fourth receiving device connected to the first virtual access point, wherein the destination address is also for the fourth receiving device.
  • the Enhanced Wake-Up device 919 may identify, at a first device, a first wake-up packet that includes a first identifier, wherein the first wake-up packet is formatted for a low-power wake-up receiver of the first device and is sent in a multicast transmission.
  • the Enhanced Wake-Up device 919 may determine the first identifier is associated with the first device.
  • the Enhanced Wake-Up device 919 may determine that the first wake-up packet indicates to the first device to activate a main radio at a first time.
  • the Enhanced Wake-Up device 919 may activate the main radio at the first time.
  • machine-readable medium 922 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 924.
  • 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 924.
  • 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 900 and that cause the machine 900 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 readonly 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 readonly memory (EEPROM)
  • EPROM electrically programmable read-only memory
  • EEPROM electrically erasable programmable readonly memory
  • flash memory devices e.g., electrically erasable programmable read only memory (EEPROM)
  • EPROM electrically programmable read-only memory
  • EEPROM electrically erasable programmable readonly memory
  • flash memory devices e.g., electrically erasable programmable read only memory (EEPROM)
  • the instructions 924 may further be transmitted or received over a communications network 926 using a transmission medium via the network interface device/transceiver 920 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 920 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 926.
  • the network interface device/transceiver 920 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 900 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), 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
  • 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 protocol
  • 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 (TDMA), 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 data rates for
  • the device may include memory and processing circuitry configured to determine a multicast wake-up packet to be sent to one or more station devices, wherein the multicast wake-up packet is formatted for respective low-power receivers of the one or more station devices; determine a common period of time for powering on the respective low-power receivers of the one or more station devices; and cause to send the multicast wake-up packet to the one or more station devices during the common period of time.
  • the implementations may include one or more of the following features.
  • the common period of time may be determined in accordance with an IEEE 802.11 standard.
  • To determine the common time comprises the processing circuitry being further configured to cause to send one or more messages indicating the common period of time.
  • the memory and the processing circuitry may be further configured to identify a signal from at least one of the one or more station devices, wherein the signal indicates that at least one of the one or more station devices will not power on its low-power receiver during the common period of time.
  • the memory and the processing circuitry may be further configured to cause to send a respective unicast wake-up packet to each of the at least one of the one or more station devices.
  • the common period of time may be a time when the one or more station devices must have their respective low-power receivers turned on.
  • the memory and the processing circuitry may be further configured to identify one or more wake-up requests from the one or more station devices, wherein the common period of time is based at least in part on the one or more wake-up requests.
  • the memory and the processing circuitry may be further configured to comprise a transceiver configured to transmit and receive wireless signals.
  • the memory and the processing circuitry may be further configured to comprise one or more antennas coupled to the transceiver.
  • the device may include memory and processing circuitry configured to cause to send a wake-up request; determine a second time when the low-power wake-up receiver will be on; and activate the low-power wake-up receiver at the second time, wherein the first wake-up packet is sent based on the second time.
  • the implementations may include one or more of the following features.
  • the first identifier may be a common group identifier for the device and to all other devices connected to a physical access point.
  • the first identifier may be an access point identifier for the device and to all other devices connected to a first virtual access point for a physical access point, wherein the device is connected to the first virtual access point.
  • the access point identifier may also be for all devices connected to a second virtual access point for the physical access point.
  • the memory and the processing circuitry may be further configured to: identify a second wake-up packet that includes a second identifier, wherein the second wake-up packet is formatted for the low-power wake-up receiver; determine that the second identifier is not for the device; and discard the second wake-up packet.
  • To determine that the second identifier is not associated with the device comprises determining that the second identifier is for all devices connected to a third virtual access point for a physical access point, wherein the device is not connected to the third virtual access point.
  • the memory and the processing circuitry may be further configured to: identify a first signal indicating a third time to activate the low-power wake-up receiver; cause to send a signal indicating that the low-power wake-up receiver will not be active at the third time; identify a second signal indicating a fourth time to activate the low-power wake-up receiver; and activate the low-power wake-up receiver at the fourth time, wherein the first wake-up packet is sent based on the fourth time.
  • the memory and the processing circuitry may be further configured to comprise a transceiver configured to transmit and receive wireless signals.
  • the memory and the processing circuitry may be further configured to comprise one or more antennas coupled to the transceiver.
  • the device may include memory and processing circuitry configured to determine a first device and a second device to receive a wake-up packet formatted for a respective low-power wake-up receiver at each of the first device and the second device; determine the wake-up packet, wherein the wake-up packet comprises a first identifier for a first virtual access point of a physical access point, and wherein the first device and the second device are connected to the first virtual access point; and cause the first virtual access point to send the wake-up packet in a multicast transmission.
  • the implementations may include one or more of the following features.
  • the memory and processing circuitry may be further configured to: determine a third device to receive the wake-up packet, wherein the third device is connected to a second virtual access point of the physical access point.
  • the first identifier may also be for the second virtual access point.
  • To determine the wake-up packet comprises determining the first identifier, wherein the first identifier indicates a destination address for the first device and for the second receiving device.
  • To determine the wake-up packet may further comprise determining a second identifier, wherein the second identifier indicates a source address for the first virtual access point.
  • the memory and processing circuitry may be further configured to determine a fourth device connected to the first virtual access point, wherein the destination address is also for the fourth device.
  • the source address may be for every virtual access point of the physical access point, wherein the destination address is for any receiving device connected to any virtual access point of the physical access point.
  • the memory and processing circuitry may be further configured to comprise a transceiver configured to transmit and receive wireless signals.
  • the memory and processing circuitry may be further configured to comprise one or more antennas coupled to the transceiver.
  • the method may include determining a multicast wake-up packet to be sent to one or more station devices, wherein the multicast wake-up packet is formatted for respective low-power receivers of the one or more station devices; determining a common period of time for powering on the respective low-power receivers of the one or more station devices; and causing to send the multicast wake-up packet to the one or more station devices at the common period of time.
  • the implementations may include one or more of the following features.
  • the common period of time may be determined in accordance with an IEEE 802.11 standard. Determining the common period time may comprise causing to send one or more messages indicating the common period of time.
  • the method may further comprise identifying a signal from at least one of the one or more station devices, wherein the signal indicates that the at least one of the one or more station devices will not power on its low-power receiver during the common period of time.
  • the method may further comprise causing to send a respective unicast wake-up packet to each of the at least one of the one or more station devices.
  • the common period of time may be a time when the one or more station devices must have their respective low-power receivers turned on.
  • the method may further comprise identifying one or more wake-up requests from the one or more station devices, wherein the common period of time is based at least in part on the one or more wake-up requests.
  • the method may include identifying at a device a first wake-up packet that includes a first identifier, wherein the first wake-up packet is formatted for a low-power wake-up receiver of the device and is sent in a multicast transmission; determining that the first identifier is for the device; determining that the first wake-up packet indicates to the device to activate a main radio at a first time; and activating the main radio at the first time.
  • the implementations may include one or more of the following features.
  • the method may further comprise causing to send a wake-up request; determining a second time when the low-power wake-up receiver will be on; and activating the low-power wake-up receiver at the second time, wherein the first wake-up packet is sent based on the second time.
  • the first identifier may be a common group identifier for the device and to all other devices connected to a physical access point.
  • the first identifier may be an access point identifier for the device and to all other devices connected to a first virtual access point for a physical access point, wherein the device is connected to the first virtual access point.
  • the access point identifier may also be for all devices connected to a second virtual access point for the physical access point.
  • the method may further comprise identifying a second wake-up packet that includes a second identifier, wherein the second wake-up packet is formatted for the low-power wake-up receiver; determining that the second identifier is not for the device; and discarding the second wake-up packet. Determining that the second identifier may not be associated with the device comprises determining that the second identifier is for all devices connected to a third virtual access point for a physical access point, wherein the device is not connected to the third virtual access point.
  • the method may further comprise identifying a first signal indicating a third time to activate the low-power wake-up receiver; causing to send a signal indicating that the low-power wake-up receiver will not be active at the third time; identifying a second signal indicating a fourth time to activate the low-power wake-up receiver; and activating the low- power wake-up receiver at the fourth time, wherein the first wake-up packet is sent based on the fourth time.
  • the method may include determining a first device and a second device to receive a wake-up packet formatted for a respective low-power wake-up receiver at each of the first device and the second device; determining the wake-up packet, wherein the wake-up packet comprises a first identifier for a first virtual access point of a physical access point, and wherein the first device and the second device are connected to the first virtual access point; and causing the first virtual access point to send the wake-up packet in a multicast transmission.
  • the implementations may include one or more of the following features.
  • the method may further comprise determining a third device to receive the wake-up packet, wherein the third device is connected to a second virtual access point of the physical access point.
  • the first identifier may also be for the second virtual access point.
  • the first identifier may also be for the second virtual access point.
  • the first identifier may be a common identifier for all virtual access points of the physical access point.
  • Determining the wake-up packet may comprise determining the first identifier, wherein the first identifier indicates a destination address for the first device and for the second device.
  • the method may further comprise determining a fourth device connected to the first virtual access point, wherein the destination address is also for the fourth device.
  • the source address may be for every virtual access point of the physical access point, wherein the destination address is for any device connected to any virtual access point of the physical access point.
  • a non-transitory computer-readable medium storing computer-executable instructions which, when executed by a processor, cause the processor to perform operations.
  • the operations may include determining a multicast wake-up packet to be sent to one or more station devices, wherein the multicast wake-up packet is formatted for respective low-power receivers of the one or more station devices; determining a common period of time for powering on the respective low- power receivers of the one or more station devices; and causing to send the multicast wake- up packet to the one or more station devices during the common period of time.
  • the implementations may include one or more of the following features.
  • the operations may further comprise identifying a signal from at least one of the one or more station devices, wherein the signal indicates that at least one of the one or more station devices will not power on its low-power receiver during the common period of time.
  • the operations may further comprise causing to send a respective unicast wake-up packet to each of the at least one of the one or more station devices.
  • the common period of time may be a time when the one or more station devices must have their respective low-power receivers turned on.
  • the operations may further comprise identifying one or more wake-up requests from the one or more station devices, wherein the common period of time is based at least in part on the one or more wake-up requests.
  • a non-transitory computer-readable medium storing computer-executable instructions which, when executed by a processor, cause the processor to perform operations.
  • the operations may include identifying at a device a first wake-up packet that includes a first identifier, wherein the first wake-up packet is formatted for a low-power wake-up receiver of the device and is sent in a multicast transmission; determining that the first identifier is for the device; determining that the first wake-up packet indicates to the device to activate a main radio at a first time; and activating the main radio at the first time.
  • the implementations may include one or more of the following features.
  • the operations may further comprise: causing to send a wake-up request; determining a second time when the low-power wake-up receiver will be on; and activating the low-power wake-up receiver at the second time, wherein the first wake-up packet is sent based on the second time.
  • the first identifier may be a common group identifier for the device and to all other devices connected to a physical access point.
  • the first identifier may be an access point identifier for the device and to all other devices connected to a first virtual access point for a physical access point, wherein the device is connected to the first virtual access point.
  • the access point identifier may also be for all devices connected to a second virtual access point for the physical access point.
  • the operations further comprise: identifying a second wake-up packet that includes a second identifier, wherein the second wake-up packet is formatted for the low-power wake-up receiver; determining that the second identifier is not for the device; and discarding the second wake-up packet. Determining that the second identifier may not be associated with the device comprises determining that the second identifier is for all devices connected to a third virtual access point for a physical access point, wherein the device is not connected to the third virtual access point.
  • the operations may further comprise: identifying a first signal indicating a third time to activate the low-power wake-up receiver; causing to send a signal indicating that the low-power wake-up receiver will not be active at the third time; identifying a second signal indicating a fourth time to activate the low-power wake-up receiver; and activating the low-power wake-up receiver at the fourth time, wherein the first wake-up packet is sent based on the fourth time.
  • a non-transitory computer-readable medium storing computer-executable instructions which, when executed by a processor, cause the processor to perform operations.
  • the operations may include determining a first device and a second device to receive a wake-up packet formatted for a respective low-power wake-up receiver at each of the first device and the second device; determining the wake-up packet, wherein the wake-up packet comprises a first identifier for a first virtual access point of a physical access point, and wherein the first device and the second device are connected to the first virtual access point; and causing the first virtual access point to send the wake-up packet in a multicast transmission.
  • the implementations may include one or more of the following features.
  • the operations may further comprise: determining a third device to receive the wake-up packet, wherein the third device is connected to a second virtual access point of the physical access point.
  • the first identifier may also be for the second virtual access point.
  • the first identifier may be a common identifier for all virtual access points of the physical access point.
  • Determining the wake-up packet may comprise determining the first identifier, wherein the first identifier indicates a destination address for the first receiving device and for the second receiving device.
  • the operations may further comprise determining a fourth device connected to the first virtual access point, wherein the destination address is also for the fourth device.
  • the source address may be for every virtual access point of the physical access point, wherein the destination address is for any device connected to any virtual access point of the physical access point.
  • the apparatus may include means for determining a multicast wake-up packet to be sent to one or more station devices, wherein the multicast wake-up packet is formatted for respective low- power receivers of the one or more station devices; means for determining a common period of time for powering on the respective low-power receivers of the one or more station devices; and means for causing to send the multicast wake-up packet to the one or more station devices at the common period of time.
  • the implementations may include one or more of the following features.
  • the common period of time may be determined in accordance with an IEEE 802.11 standard.
  • Means for determining the common period time may comprise means for causing to send one or more messages indicating the common period of time.
  • the apparatus may further comprise means for identifying a signal from at least one of the one or more station devices, wherein the signal indicates that the at least one of the one or more station devices will not power on its low-power receiver during the common period of time.
  • the apparatus may further comprise means for causing to send a respective unicast wake-up packet to each of the at least one of the one or more station devices.
  • the common period of time may be a time when the one or more station devices must have their respective low-power receivers turned on.
  • the apparatus may further comprise means for identifying one or more wake-up requests from the one or more station devices, wherein the common period of time is based at least in part on the one or more wake-up requests.
  • the apparatus may include means for causing to send a wake-up request; means for determining a second time when the low-power wake-up receiver will be on; and means for activating the low-power wake-up receiver at the second time, wherein the first wake-up packet is sent based on the second time.
  • the implementations may include one or more of the following features.
  • the first identifier may be a common group identifier for the device and to all other devices connected to a physical access point.
  • the first identifier may be an access point identifier for the device and to all other devices connected to a first virtual access point for a physical access point, wherein the device is connected to the first virtual access point.
  • the access point identifier may also be for all devices connected to a second virtual access point for the physical access point.
  • the apparatus may further comprise means for identifying a second wake-up packet that includes a second identifier, wherein the second wake-up packet is formatted for the low-power wake-up receiver; means for determining that the second identifier is not for the device; and means for discarding the second wake-up packet.
  • Means for determining that the second identifier may not be associated with the device comprises determining that the second identifier is for all devices connected to a third virtual access point for a physical access point, wherein the device is not connected to the third virtual access point.
  • the apparatus may further comprise means for identifying a first signal indicating a third time to activate the low-power wake-up receiver; means for causing to send a signal indicating that the low-power wake-up receiver will not be active at the third time; means for identifying a second signal indicating a fourth time to activate the low-power wake-up receiver; and means for activating the low-power wake-up receiver at the fourth time, wherein the first wake-up packet is sent based on the fourth time.
  • the apparatus may include means for determining a first device and a second device to receive a wake-up packet formatted for a respective low-power wake-up receiver at each of the first device and the second device; means for determining the wake-up packet, wherein the wake-up packet comprises a first identifier for a first virtual access point of a physical access point, and wherein the first device and the second device are connected to the first virtual access point; and means for causing the first virtual access point to send the wake-up packet in a multicast transmission.
  • the first identifier may also be for the second virtual access point.
  • the first identifier may be a common identifier for all virtual access points of the physical access point.
  • Means for determining the wake-up packet may comprise means for determining the first identifier, wherein the first identifier indicates a destination address for the first device and for the second device.
  • Means for determining the wake-up packet may further comprise means for determining a second identifier, wherein the second identifier indicates a source address for the first virtual access point.
  • the apparatus may further comprise means for determining a fourth device connected to the first virtual access point, wherein the destination address is also for the fourth device.
  • the source address may be for every virtual access point of the physical access point, wherein the destination address is for any receiving device connected to any virtual access point of the physical access point.
  • 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)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne des systèmes, des procédés et des dispositifs liés à une de transmission de paquets d'activation de multidiffusion. Un dispositif peut déterminer un paquet d'activation de multidiffusion devant être envoyé à un ou plusieurs dispositifs de station. Le dispositif peut déterminer une période de temps commune pour alimenter des récepteurs respectifs desdits dispositifs de station. Le dispositif peut provoquer l'envoi du paquet d'activation de multidiffusion auxdits dispositifs de station pendant la période de temps commune.
PCT/US2017/053538 2017-02-28 2017-09-26 Signalisation d'activation améliorée destinée à des communications sans fil WO2018160222A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201762465082P 2017-02-28 2017-02-28
US62/465,082 2017-02-28
US201762467748P 2017-03-06 2017-03-06
US62/467,748 2017-03-06

Publications (1)

Publication Number Publication Date
WO2018160222A1 true WO2018160222A1 (fr) 2018-09-07

Family

ID=63370520

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2017/053538 WO2018160222A1 (fr) 2017-02-28 2017-09-26 Signalisation d'activation améliorée destinée à des communications sans fil

Country Status (1)

Country Link
WO (1) WO2018160222A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112771949A (zh) * 2018-09-27 2021-05-07 株式会社Ntt都科摩 用户终端、无线基站以及无线通信方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8923178B2 (en) * 2011-04-29 2014-12-30 Blackberry Limited Managing group messages for LTE wakeup
US20160165625A1 (en) * 2011-05-31 2016-06-09 Lg Electronics Inc. Method for transmitting and receiving physical layer convergence procedure protocol data unit in wireless local area network system supporting power save mode operation and apparatus for the same
US20170019208A1 (en) * 2015-07-14 2017-01-19 Universitat Politecnica De Catalunya Data modulation method for ieee 802.11 and ieee 802.15 devices to generate low frequency signals

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8923178B2 (en) * 2011-04-29 2014-12-30 Blackberry Limited Managing group messages for LTE wakeup
US20160165625A1 (en) * 2011-05-31 2016-06-09 Lg Electronics Inc. Method for transmitting and receiving physical layer convergence procedure protocol data unit in wireless local area network system supporting power save mode operation and apparatus for the same
US20170019208A1 (en) * 2015-07-14 2017-01-19 Universitat Politecnica De Catalunya Data modulation method for ieee 802.11 and ieee 802.15 devices to generate low frequency signals

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
JOERG ROBERT: "Ultra Low Power Strategies for Selective Wake-Up from Receiver Prospect", IEEE 802.11-17/0184R0, 20 January 2017 (2017-01-20), pages 1 - 15, XP055547187 *
KISEON RYE ET AL.: "Overall MAC Procedure for WUR", IEEE 802.11-16/1445R1, 8 November 2016 (2016-11-08), pages 1 - 10, XP055547181 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112771949A (zh) * 2018-09-27 2021-05-07 株式会社Ntt都科摩 用户终端、无线基站以及无线通信方法
CN112771949B (zh) * 2018-09-27 2024-05-17 株式会社Ntt都科摩 用户终端、无线基站以及无线通信方法

Similar Documents

Publication Publication Date Title
US20240031871A1 (en) Multi-link traffic steering with traffic indication map
US12219476B2 (en) Low power wake-up radio beacon signaling
US11558818B2 (en) Wake-up radio advertisement channel
US11743834B2 (en) Enhanced multi-band power saving for wireless communications
US11622332B2 (en) Wake up receiver frame
US11825414B2 (en) Group identification indication signaling
US12213115B2 (en) Enhanced high efficiency frames for wireless communications
EP3476076A2 (fr) Négociation améliorée de protocole de mesure de synchronisation fine
US10798707B2 (en) Enhanced data path structure for multi-band operations in wireless communications
US10785819B2 (en) Maximum idle period for multi-band dual connectivity
US11902898B2 (en) Wake-up frame indication
WO2019027511A1 (fr) Planification de rétroaction de rapport de mesure de position dans des communications sans fil
WO2019040092A1 (fr) Double connectivité pour 6 ghz
WO2018160994A1 (fr) Regroupement et identification de points d'accès
WO2018186919A1 (fr) Indication de services de réseautage sensible au voisinage
WO2018160222A1 (fr) Signalisation d'activation améliorée destinée à des communications sans fil
CN111034282B (zh) 用于无线通信的增强唤醒信号
WO2018147904A1 (fr) Identification de groupe améliorée pour des entrées et sorties multiples avec de multiples utilisateurs sur liaison descendante
WO2018182624A1 (fr) Attributions de tonalités à bande étroite

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: 17898658

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: 17898658

Country of ref document: EP

Kind code of ref document: A1

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