WO2019040093A1

WO2019040093A1 - Apparatus, system and method of communicating a wake-up radio frame

Info

Publication number: WO2019040093A1
Application number: PCT/US2017/068665
Authority: WO
Inventors: Po-Kai Huang; Noam GINSBURG; Robert Stacey; Shahrnaz Azizi; Thomas J. Kenney
Original assignee: Intel IP Corporation
Priority date: 2017-08-21
Filing date: 2017-12-28
Publication date: 2019-02-28
Also published as: DE112017007972T5

Abstract

For example, a wireless communication device may be configured to generate a wake-up radio (WUR) frame having a WUR frame format including a type field, a first type-dependent field, and a second type-dependent field, the type field to indicate a type of the WUR frame, wherein, when the type field is to indicate that the WUR frame is a WUR beacon, the first type-dependent field includes first identification information to identify a transmitter of the WUR beacon and the second type-dependent field includes a time value, and, when the type field is to indicate that the WUR frame is a wake-up packet, the first type-dependent field includes second identification information to identify a receiver of the wake-up packet and the second type-dependent field includes a counter value; and to transmit the WUR frame.

Description

APPARATUS, SYSTEM AND METHOD OF COMMUNICATING A WAKE- UP RADIO FRAME

CROSS REFERENCE

[001] This Application claims the benefit of and priority from US Provisional Patent Application No. 62/548,011 entitled "APPARATUS, SYSTEM AND METHOD OF COMMUNICATING A WAKEUP RADIO FRAME", filed August 21, 2017, the entire disclosure of which is incorporated herein by reference.

TECHNICAL FIELD

[002] Embodiments described herein generally relate to communicating a wake-up radio frame.

BACKGROUND [003] Some computing devices, for example, small computing devices, such as, for example, wearable devices and/or sensors, are constrained by a small battery capacity.

[004] However, such devices may be required to support wireless communication technologies such as, for example, Wi-Fi, and/or Bluetooth (BT), for example, to connect to other computing devices, e.g., a Smartphone, for example, to exchange data.

[005] Exchanging data using the wireless communication technologies may consume power of the battery, and it may be beneficial, or even critical, to minimize energy consumption of one or more communication blocks in such computing devices. BRIEF DESCRIPTION OF THE DRAWINGS

[006] For simplicity and clarity of illustration, elements shown in the figures have not necessarily been drawn to scale. For example, the dimensions of some of the elements may be exaggerated relative to other elements for clarity of presentation. Furthermore, reference numerals may be repeated among the figures to indicate corresponding or analogous elements. The figures are listed below.

[007] Fig. 1 is a schematic block diagram illustration of a system, in accordance with some demonstrative embodiments.

[008] Fig. 2 is a schematic illustration of a frame format including one or more fields, which may be implemented in accordance with some demonstrative embodiments.

[009] Fig. 3 is a schematic illustration of a frame format including one or more fields, which may be implemented in accordance with some demonstrative embodiments. [0010] Fig. 4 is a schematic illustration of a frame format including one or more fields, which may be implemented in accordance with some demonstrative embodiments.

[0011] Fig. 5 is a schematic illustration of a frame format including one or more fields, which may be implemented in accordance with some demonstrative embodiments.

[0012] Fig. 6 is a schematic illustration of a frame format including one or more fields, which may be implemented in accordance with some demonstrative embodiments.

[0013] Fig. 7 is a schematic illustration of a Wake-up Radio (WUR) frame format, in accordance with some demonstrative embodiments.

[0014] Fig. 8 is a schematic illustration of a WUR frame format, in accordance with some demonstrative embodiments.

[0015] Fig. 9 is a schematic illustration of a WUR frame format, in accordance with some demonstrative embodiments. [0016] Fig. 10 is a schematic flow-chart illustration of a method of communicating a WUR frame, in accordance with some demonstrative embodiments.

[0017] Fig. 11 is a schematic flow-chart illustration of a method of communicating a WUR frame, in accordance with some demonstrative embodiments. [0018] Fig. 12 is a schematic illustration of a product of manufacture, in accordance with some demonstrative embodiments.

DETAILED DESCRIPTION

[0019] In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of some embodiments. However, it will be understood by persons of ordinary skill in the art that some embodiments may be practiced without these specific details. In other instances, well-known methods, procedures, components, units and/or circuits have not been described in detail so as not to obscure the discussion.

[0020] Discussions herein utilizing terms such as, for example, "processing", "computing", "calculating", "determining", "establishing", "analyzing", "checking", or the like, may refer to operation(s) and/or process(es) of a computer, a computing platform, a computing system, or other electronic computing device, that manipulate and/or transform data represented as physical (e.g., electronic) quantities within the computer' s registers and/or memories into other data similarly represented as physical quantities within the computer's registers and/or memories or other information storage medium that may store instructions to perform operations and/or processes.

[0021] The terms "plurality" and "a plurality", as used herein, include, for example, "multiple" or "two or more". For example, "a plurality of items" includes two or more items.

[0022] References to "one embodiment", "an embodiment", "demonstrative embodiment", "various embodiments" etc., indicate that the embodiment(s) so described may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes the particular feature, structure, or characteristic. Further, repeated use of the phrase "in one embodiment" does not necessarily refer to the same embodiment, although it may. [0023] As used herein, unless otherwise specified the use of the ordinal adjectives "first", "second", "third" etc., to describe a common object, merely indicate that different instances of like objects are being referred to, and are not intended to imply that the objects so described must be in a given sequence, either temporally, spatially, in ranking, or in any other manner. [0024] Some embodiments may be used in conjunction with various devices and systems, for example, a User Equipment (UE), a Mobile Device (MD), a wireless station (STA), 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, an Internet of Things (IoT) device, a sensor device, a wearable device, a Personal Digital Assistant (PDA) device, a handheld PDA device, an on-board 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 (WPAN), and the like.

[0025] Some embodiments may be used in conjunction with devices and/or networks operating in accordance with existing IEEE 802.11 standards (including IEEE 802.11-2016 {IEEE 802.11-2016, IEEE Standard for Information technology- Telecommunications and information exchange between systems Local and metropolitan area networks-Specific requirements, Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications, December 7, 2016); IEEE 802.1 lax (IEEE 802.1 lax, High Efficiency WLAN (HEW)); IEEE802.11-ay (P802.11ay Standard for Information Technology--Telecommunications and Information Exchange Between Systems Local and Metropolitan Area Networks- Specific Requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications— Amendment: Enhanced Throughput for Operation in License-Exempt Bands Above 45 GHz)) and/or future versions and/or derivatives thereof) and/or future versions and/or derivatives thereof, devices and/or networks operating in accordance with existing Wireless-Gigabit-Alliance (WGA) specifications (including Wireless Gigabit Alliance, Inc WiGig MAC and PHY Specification Version 1.1, April 2011, Final specification) and/or future versions and/or derivatives thereof, devices and/or networks operating in accordance with existing Wireless Fidelity (WiFi) Alliance (WFA) Peer-to-Peer (P2P) specifications (including WiFi P2P technical specification, version 1.5, August 4, 2014) and/or future versions and/or derivatives thereof, devices and/or networks operating in accordance with existing cellular specifications and/or protocols, e.g., 3rd Generation Partnership Project (3GPP), 3GPP Long Term Evolution (LTE) and/or future versions and/or derivatives thereof, devices and/or networks operating in accordance with existing Bluetooth (BT) specifications and/or protocols and/or future versions and/or derivatives thereof, units and/or devices which are part of the above networks, and the like. [0026] 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 Systems (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.

[0027] Some embodiments may be used in conjunction with one or more types of wireless communication signals and/or systems, for example, Radio Frequency (RF), Infra Red (IR), Frequency-Division Multiplexing (FDM), Orthogonal FDM (OFDM), Orthogonal Frequency-Division Multiple Access (OFDMA), FDM Time-Division Multiplexing (TDM), Time-Division Multiple Access (TDM A), Multi-User MIMO (MU-MIMO), Spatial Division Multiple Access (SDMA), 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 communication (GSM), 2G, 2.5G, 3G, 3.5G, 4G, Fifth Generation (5G), or Sixth Generation (6G) mobile networks, 3GPP, Long Term Evolution (LTE), LTE advanced, Enhanced Data rates for GSM Evolution (EDGE), or the like. Other embodiments may be used in various other devices, systems and/or networks. [0028] The term "wireless device", as used herein, includes, for example, a device capable of wireless communication, a communication device capable of wireless communication, a communication station capable of wireless communication, a portable or non-portable device capable of wireless communication, or the like. In some demonstrative embodiments, a wireless device may be or may include a peripheral that is integrated with a computer, or a peripheral that is attached to a computer. In some demonstrative embodiments, the term "wireless device" may optionally include a wireless service.

[0029] The term "communicating" as used herein with respect to a communication signal includes transmitting the communication signal and/or receiving the communication signal. For example, a communication unit, which is capable of communicating a communication signal, may include a transmitter to transmit the communication signal to at least one other communication unit, and/or a communication receiver to receive the communication signal from at least one other communication unit. The verb communicating may be used to refer to the action of transmitting or the action of receiving. In one example, the phrase "communicating a signal" may refer to the action of transmitting the signal by a first device, and may not necessarily include the action of receiving the signal by a second device. In another example, the phrase "communicating a signal" may refer to the action of receiving the signal by a first device, and may not necessarily include the action of transmitting the signal by a second device.

[0030] Some demonstrative embodiments may be used in conjunction with a WLAN, e.g., a WiFi network. Other embodiments may be used in conjunction with any other suitable wireless communication network, for example, a wireless area network, a "piconet", a WPAN, a WVAN and the like.

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

[0032] The term "logic" may refer, for example, to computing logic embedded in circuitry of a computing apparatus and/or computing logic stored in a memory of a computing apparatus. For example, the logic may be accessible by a processor of the computing apparatus to execute the computing logic to perform computing functions and/or operations. In one example, logic may be embedded in various types of memory and/or firmware, e.g., silicon blocks of various chips and/or processors. Logic may be included in, and/or implemented as part of, various circuitry, e.g. radio circuitry, receiver circuitry, control circuitry, transmitter circuitry, transceiver circuitry, processor circuitry, and/or the like. In one example, logic may be embedded in volatile memory and/or non- volatile memory, including random access memory, read only memory, programmable memory, magnetic memory, flash memory, persistent memory, and the like. Logic may be executed by one or more processors using memory, e.g., registers, stuck, buffers, and/or the like, coupled to the one or more processors, e.g., as necessary to execute the logic.

[0033] The term "antenna", as used herein, may include any suitable configuration, structure and/or arrangement of one or more antenna elements, components, units, assemblies and/or arrays. In some embodiments, the antenna may implement transmit and receive functionalities using separate transmit and receive antenna elements. In some embodiments, the antenna may implement transmit and receive functionalities using common and/or integrated transmit/receive elements. The antenna may include, for example, a phased array antenna, a single element antenna, a set of switched beam antennas, and/or the like. [0034] Reference is made to Fig. 1, which schematically illustrates a system 100, in accordance with some demonstrative embodiments.

[0035] As shown in Fig. 1, in some demonstrative embodiments, system 100 may include one or more wireless communication devices. For example, system 100 may include a first wireless communication device 102, and/or a second wireless communication device 140.

[0036] In some demonstrative embodiments, device 102 and/or device 140 may include a mobile device or a non-mobile, e.g., a static, device. For example, device 102 and/or device 140 may include, for example, a UE, an MD, a STA, an AP, a PC, a desktop computer, a mobile computer, a laptop computer, an Ultrabook™ computer, a notebook computer, a tablet computer, a server computer, a handheld computer, an Internet of Things (IoT) device, sensor device, a wearable device, a BT device, a handheld 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 incorporates a wireless communication device, a mobile or portable GPS device, a DVB device, a relatively small computing device, a non-desktop computer, a "Carry Small Live Large" (CSLL) device, an Ultra Mobile Device (UMD), an Ultra Mobile PC (UMPC), a Mobile Internet Device (MID), an "Origami" device or computing device, a device that supports Dynamically Composable Computing (DCC), a context-aware device, a video device, an audio device, an A/V device, a Set-Top-Box (STB), a Blu-ray disc (BD) player, a BD recorder, a Digital Video Disc (DVD) player, a High Definition (HD) DVD player, a DVD recorder, a HD DVD recorder, a Personal Video Recorder (PVR), a broadcast HD receiver, a video source, an audio source, a video sink, an audio sink, a stereo tuner, a broadcast radio receiver, a flat panel display, a Personal Media Player (PMP), a digital video camera (DVC), a digital audio player, a speaker, an audio receiver, an audio amplifier, a gaming device, a data source, a data sink, a Digital Still camera (DSC), a media player, a Smartphone, a television, a music player, or the like.

[0037] In some demonstrative embodiments, device 102 and/or device 140 may include, operate as, and/or perform the functionality of one or more STAs. For example, device 102 may include at least one STA, and/or device 140 may include at least one STA.

[0038] In some demonstrative embodiments, device 102 and/or device 140 may include, operate as, and/or perform the functionality of one or more WLAN STAs. [0039] In some demonstrative embodiments, device 102 and/or device 140 may include, operate as, and/or perform the functionality of one or more Wi-Fi STAs. [0040] In some demonstrative embodiments, device 102 and/or device 140 may include, operate as, and/or perform the functionality of one or more BT devices.

[0041] In some demonstrative embodiments, device 102 and/or device 140 may include, operate as, and/or perform the functionality of one or more Neighbor Awareness Networking (NAN) STAs.

[0042] In some demonstrative embodiments, device 102 and/or device 140 may include, operate as, and/or perform the functionality of one or more location measurement STAs.

[0043] In some demonstrative embodiments, device 102 and/or device 140 may include, operate as, and/or perform the functionality of any other devices and/or STAs.

[0044] In some demonstrative embodiments, device 102 may include, for example, one or more of a processor 191, an input unit 192, an output unit 193, a memory unit 194, and/or a storage unit 195; and/or device 140 may include, for example, one or more of a processor 181, an input unit 182, an output unit 183, a memory unit 184, and/or a storage unit 185. Device 102 and/or device 140 may optionally include other suitable additional or alternative hardware components and/or software components. In some demonstrative embodiments, some or all of the components of one or more of device 102 and/or device 140 may be enclosed in a common housing or packaging, and may be interconnected or operably associated using one or more wired or wireless links. In other embodiments, components of one or more of device 102 and/or device 140 may be distributed among multiple or separate devices.

[0045] In some demonstrative embodiments, processor 191 and/or processor 181 may include, for example, a Central Processing Unit (CPU), a Digital Signal Processor (DSP), one or more processor cores, a single-core processor, a dual-core processor, a multiple-core processor, a microprocessor, a host processor, a controller, a plurality of processors or controllers, a chip, a microchip, one or more circuits, circuitry, a logic unit, an Integrated Circuit (IC), an Application-Specific IC (ASIC), or any other suitable multi-purpose or specific processor or controller. Processor 191 executes instructions, for example, of an Operating System (OS) of device 102 and/or of one or more suitable applications. Processor 181 executes instructions, for example, of an Operating System (OS) of device 140 and/or of one or more suitable applications. [0046] In some demonstrative embodiments, input unit 192 and/or input unit 182 may include, for example, a keyboard, a keypad, a mouse, a touch-screen, a touch-pad, a track-ball, a stylus, a microphone, or other suitable pointing device or input device. Output unit 193 and/or output unit 183 may include, for example, a monitor, a screen, a touch-screen, a flat panel display, a Light Emitting Diode (LED) display unit, a Liquid Crystal Display (LCD) display unit, a plasma display unit, one or more audio speakers or earphones, or other suitable output devices.

[0047] In some demonstrative embodiments, memory unit 194 and/or memory unit 184 may include, for example, a Random Access Memory (RAM), a Read Only Memory (ROM), a Dynamic RAM (DRAM), a Synchronous DRAM (SD-RAM), a flash memory, a volatile memory, a non- volatile memory, a cache memory, a buffer, a short term memory unit, a long term memory unit, or other suitable memory units. Storage unit 195 and/or storage unit 185 may include, for example, a hard disk drive, a floppy disk drive, a Compact Disk (CD) drive, a CD-ROM drive, a DVD drive, or other suitable removable or non-removable storage units. Memory unit 194 and/or storage unit 195, for example, may store data processed by device 102. Memory unit 184 and/or storage unit 185, for example, may store data processed by device 140.

[0048] In some demonstrative embodiments, wireless communication device 102 and/or device 140 may be capable of communicating content, data, information and/or signals via a wireless medium (WM) 103. In some demonstrative embodiments, wireless medium 103 may include, for example, a radio channel, a cellular channel, an RF channel, a WiFi channel, an IR channel, a Bluetooth (BT) channel, a Direct- Sequence Spread Spectrum (DSSS) channel, a BT Low Energy (BLE) channel, a Global Navigation Satellite System (GNSS) Channel, and the like. [0049] In some demonstrative embodiments, WM 103 may include a channel over a 2.4 Gigahertz (GHz) frequency band, a channel over a 5GHz frequency band, a channel over a millimeterWave (mmWave) frequency band, e.g., a 60GHz frequency band, a channel over a sub 1 Gigahertz (S IG) frequency band, and/or any other channel over any other band. [0050] In some demonstrative embodiments, device 102 and/or device 140 may include one or more radios including circuitry and/or logic to perform wireless communication between devices 102, 140 and/or one or more other wireless communication devices. For example, device 102 may include at least one radio 114, and/or device 140 may include at least one radio 144.

[0051] In some demonstrative embodiments, radios 114 and/or 144 may include one or more wireless receivers (Rx) including circuitry and/or logic to receive wireless communication signals, RF signals, frames, blocks, transmission streams, packets, messages, data items, and/or data. For example, radio 114 may include at least one receiver 116, and/or radio 144 may include at lest one receiver 146.

[0052] In some demonstrative embodiments, radios 114 and/or 144 may include one or more wireless transmitters (Tx) including circuitry and/or logic to transmit wireless communication signals, RF signals, frames, blocks, transmission streams, packets, messages, data items, and/or data. For example, radio 114 may include at least one transmitter 118, and/or radio 144 may include at least one transmitter 148.

[0053] In some demonstrative embodiments, radio 114, radio 144, transmitter 118, transmitter 148, receiver 116, and/or receiver 148 may include circuitry; logic; Radio Frequency (RF) elements, circuitry and/or logic; baseband elements, circuitry and/or logic; modulation elements, circuitry and/or logic; demodulation elements, circuitry and/or logic; amplifiers; analog to digital and/or digital to analog converters; filters; and/or the like. For example, radios 114 and/or 144 may include or may be implemented as part of a wireless Network Interface Card (NIC), and the like. [0054] In some demonstrative embodiments, radios 114 and/or 144 may include, or may be associated with, one or more antennas 107 and/or 147, respectively.

[0055] In one example, device 102 may include a single antenna 107. In another example, device 102 may include two or more antennas 107.

[0056] In one example, device 140 may include a single antenna 147. In another example, device 140 may include two or more antennas 147.

[0057] Antennas 107 and/or 147 may include any type of antennas suitable for transmitting and/or receiving wireless communication signals, blocks, frames, transmission streams, packets, messages and/or data. For example, antennas 107 and/or 147 may include any suitable configuration, structure and/or arrangement of one or more antenna elements, components, units, assemblies and/or arrays. Antennas 107 and/or 147 may include, for example, antennas suitable for directional communication, e.g., using beamforming techniques. For example, antennas 107 and/or 147 may include a phased array antenna, a multiple element antenna, a set of switched beam antennas, and/or the like. In some embodiments, antennas 107 and/or 147 may implement transmit and receive functionalities using separate transmit and receive antenna elements. In some embodiments, antennas 107 and/or 147 may implement transmit and receive functionalities using common and/or integrated transmit/receive elements.

[0058] In some demonstrative embodiments, device 102 may include a controller 124, and/or device 140 may include a controller 154. Controller 124 may be configured to perform and/or to trigger, cause, instruct and/or control device 102 to perform, one or more communications, to generate and/or communicate one or more messages and/or transmissions, and/or to perform one or more functionalities, operations and/or procedures between devices 102, 140 and/or one or more other devices; and/or controller 154 may be configured to perform, and/or to trigger, cause, instruct and/or control device 140 to perform, one or more communications, to generate and/or communicate one or more messages and/or transmissions, and/or to perform one or more functionalities, operations and/or procedures between devices 102, 140 and/or one or more other devices, e.g., as described below.

[0059] In some demonstrative embodiments, controllers 124 and/or 154 may include, or may be implemented, partially or entirely, by circuitry and/or logic, e.g., one or more processors including circuitry and/or logic, memory circuitry and/or logic, Media-Access Control (MAC) circuitry and/or logic, Physical Layer (PHY) circuitry and/or logic, baseband (BB) circuitry and/or logic, a BB processor, a BB memory, Application Processor (AP) circuitry and/or logic, an AP processor, an AP memory, and/or any other circuitry and/or logic, configured to perform the functionality of controllers 124 and/or 154, respectively. Additionally or alternatively, one or more functionalities of controllers 124 and/or 154 may be implemented by logic, which may be executed by a machine and/or one or more processors, e.g., as described below.

[0060] In one example, controller 124 may include circuitry and/or logic, for example, one or more processors including circuitry and/or logic, to cause, trigger and/or control a wireless device, e.g., device 102, and/or a wireless station, e.g., a wireless STA implemented by device 102, to perform one or more operations, communications and/or functionalities, e.g., as described herein. [0061] In one example, controller 154 may include circuitry and/or logic, for example, one or more processors including circuitry and/or logic, to cause, trigger and/or control a wireless device, e.g., device 140, and/or a wireless station, e.g., a wireless STA implemented by device 140, to perform one or more operations, communications and/or functionalities, e.g., as described herein.

[0062] In some demonstrative embodiments, at least part of the functionality of controller 124 may be implemented as part of one or more elements of radio 114, and/or at least part of the functionality of controller 154 may be implemented as part of one or more elements of radio 144. [0063] In other embodiments, the functionality of controller 124 may be implemented as part of any other element of device 102, and/or the functionality of controller 154 may be implemented as part of any other element of device 140.

[0064] In some demonstrative embodiments, device 102 may include a message processor 128 configured to generate, process and/or access one or messages communicated by device 102.

[0065] In one example, message processor 128 may be configured to generate one or more messages to be transmitted by device 102, and/or message processor 128 may be configured to access and/or to process one or more messages received by device 102, e.g., as described below. [0066] In some demonstrative embodiments, device 140 may include a message processor 158 configured to generate, process and/or access one or messages communicated by device 140.

[0067] In one example, message processor 158 may be configured to generate one or more messages to be transmitted by device 140, and/or message processor 158 may be configured to access and/or to process one or more messages received by device 140, e.g., as described below.

[0068] In some demonstrative embodiments, message processors 128 and/or 158 may include, or may be implemented, partially or entirely, by circuitry and/or logic, e.g., one or more processors including circuitry and/or logic, memory circuitry and/or logic, MAC circuitry and/or logic, PHY circuitry and/or logic, BB circuitry and/or logic, a BB processor, a BB memory, AP circuitry and/or logic, an AP processor, an AP memory, and/or any other circuitry and/or logic, configured to perform the functionality of message processors 128 and/or 158, respectively. Additionally or alternatively, one or more functionalities of message processors 128 and/or 158 may be implemented by logic, which may be executed by a machine and/or one or more processors, e.g., as described below. [0069] In some demonstrative embodiments, at least part of the functionality of message processor 128 may be implemented as part of radio 114, and/or at least part of the functionality of message processor 158 may be implemented as part of radio 144.

[0070] In some demonstrative embodiments, at least part of the functionality of message processor 128 may be implemented as part of controller 124, and/or at least part of the functionality of message processor 158 may be implemented as part of controller 154.

[0071] In other embodiments, the functionality of message processor 128 may be implemented as part of any other element of device 102, and/or the functionality of message processor 158 may be implemented as part of any other element of device 140.

[0072] In some demonstrative embodiments, at least part of the functionality of controller 124 and/or message processor 128 may be implemented by an integrated circuit, for example, a chip, e.g., a System on Chip (SoC). In one example, the chip or SoC may be configured to perform one or more functionalities of radio 114. For example, the chip or SoC may include one or more elements of controller 124, one or more elements of message processor 128, and/or one or more elements of radio 114. In one example, controller 124, message processor 128, and radio 114 may be implemented as part of the chip or SoC. [0073] In other embodiments, controller 124, message processor 128 and/or radio 114 may be implemented by one or more additional or alternative elements of device 102.

[0074] In some demonstrative embodiments, at least part of the functionality of controller 154 and/or message processor 158 may be implemented by an integrated circuit, for example, a chip, e.g., a System on Chip (SoC). In one example, the chip or SoC may be configured to perform one or more functionalities of radio 144. For example, the chip or SoC may include one or more elements of controller 154, one or more elements of message processor 158, and/or one or more elements of radio 144. In one example, controller 154, message processor 158, and radio 144 may be implemented as part of the chip or SoC.

[0075] In other embodiments, controller 154, message processor 158 and/or radio 144 may be implemented by one or more additional or alternative elements of device 140. [0076] In some demonstrative embodiments, device 102 and/or device 140 may include a wearable device, a sensor, small device, a mobile device, and/or any other device, which may be, for example, powered by a battery and/or any other power source having a limited capacity.

[0077] In some demonstrative embodiments, device 102 and/or device 140 may support wireless communication technologies such as, for example, Wi-Fi, Bluetooth (BT), DSSS, and/or any other additional or alternative technology, for example, to connect between device 102, device 140, and/or other wireless devices.

[0078] In some demonstrative embodiments, device 140 may include a wearable device and/or a sensor device powered by a power source having a limited capacity, e.g., a small battery.

[0079] In some demonstrative embodiments, device 140 may be configured to communicate data with another device, e.g., device 102, which may be less power constrained than device 140, for example, a Smartphone.

[0080] In some demonstrative embodiments, communicating data between device 102 and device 140 may consume power of the power source of device 140.

[0081] In some demonstrative embodiments, minimizing energy consumption of one or more communication blocks, modules and/or elements of device 140 may be beneficial, and in some cases, even critical, for example, in order to reduce and/or minimize power consumption of the power source of device 140. [0082] In some demonstrative embodiments, power consumption of device 140 may be reduced, e.g., minimized, for example, by powering off one or more communication blocks, modules and/or elements of device 140, e.g., as much as possible, for example, while maintaining data transmission and/or reception capabilities of device 140, e.g., without substantially increasing latency and/or degrading quality of data communication. [0083] In one example, one or more communication blocks, modules and/or elements of device 140 may be powered on and/or may be woken up, for example, only when there is data to transmit, and/or only when there is data to receive. According to this example, the one or more communication blocks, modules and/or elements of device 140 may be powered off and/or switched to a sleep mode, for example, for the rest of the time.

[0084] For example, one or more elements of radio 144 may be powered on and/or may be woken up, for example, only when device 140 has data to transmit, and/or only when device 140 has data to receive. According to this example, one or more elements of radio 144 may be powered off and/or switched to the sleep mode, for example, for the rest of the time.

[0085] In some demonstrative embodiments, device 140 may include a wake-up receiver (WURx) 150 configured to power on and/or to wake up radio 144 of device 140. [0086] In some demonstrative embodiments, wake-up receiver 150 may wake up radio 144, for example, based on a Wake-Up Radio (WUR) frame, for example, a wake-up packet, e.g., as describe below.

[0087] In some demonstrative embodiments, the wake-up packet may be received from another device, e.g., device 102, which is, for example, to transmit data to device 140.

[0088] In some demonstrative embodiments, wake-up receiver 150 may include a receiver 156 configured to receive the wake-up packet.

[0089] In some demonstrative embodiments, wake-up receiver 150 may include circuitry and/or logic configured to receive, decode, demodulate, and/or process the wake-up packet.

[0090] In some demonstrative embodiments, receiver 156 may include circuitry; logic; Radio Frequency (RF) elements, circuitry and/or logic; baseband elements, circuitry and/or logic; demodulation elements, circuitry and/or logic; amplifiers; analog to digital converters; filters; and/or the like. [0091] In some demonstrative embodiments, wake-up receiver 150 may include a controller 159 configured to control one or more operations and/or functionalities of wake-up receiver 150, e.g., for processing the wake-up packet and/or waking up radio 144. For example, controller 159 may be configured to control a power supply of radio 144, and/or any other mechanism to wake up radio 144, e.g., upon determining that a wake-up packet has been received by wake-up receiver 150. [0092] In some demonstrative embodiments, controller 159 may be configured to perform one or more communications, to generate and/or communicate one or more messages and/or transmissions, and/or to perform one or more functionalities, operations and/or procedures, e.g., as described below.

[0093] In some demonstrative embodiments, controller 159 may include, or may be implemented, partially or entirely, by circuitry and/or logic, e.g., one or more processors including circuitry and/or logic, memory circuitry and/or logic, MAC circuitry and/or logic, PHY circuitry and/or logic, BB circuitry and/or logic, a BB processor, a BB memory, AP circuitry and/or logic, an AP processor, an AP memory, and/or any other circuitry and/or logic, configured to perform the functionality of controller 159. Additionally or alternatively, one or more functionalities of controller 159 may be implemented by logic, which may be executed by a machine and/or one or more processors, e.g., as described below.

[0094] In one example, controller 159 may include circuitry and/or logic, for example, one or more processors including circuitry and/or logic, to cause a wireless device, e.g., device 140, and/or a wireless station, e.g., a wireless STA implemented by device 140, to perform one or more operations, communications and/or functionalities, e.g., as described herein.

[0095] In some demonstrative embodiments, wake-up receiver 150 may include a message processor 157 configured to process and/or access one or messages communicated by wake-up receiver 150.

[0096] In some demonstrative embodiments, message processor 157 may be configured to process one or more WUR frames received by wake-up receiver 150, and/or to indicate to controller 159 that a wake-up packet is received.

[0097] In one example, message processor 157 may be configured to access, process, demodulate and/or decode reception of the wake-up packets by a wireless station, e.g., a wireless STA implemented by device 140. [0098] In some demonstrative embodiments, message processor 157 may include, or may be implemented, partially or entirely, by circuitry and/or logic, e.g., one or more processors including circuitry and/or logic, memory circuitry and/or logic, MAC circuitry and/or logic, PHY circuitry and/or logic, BB circuitry and/or logic, a BB processor, a BB memory, AP circuitry and/or logic, an AP processor, an AP memory, and/or any other circuitry and/or logic, configured to perform the functionality of message processor 157, respectively. Additionally or alternatively, one or more functionalities of message processor 157 may be implemented by logic, which may be executed by a machine and/or one or more processors, e.g., as described below. [0099] In some demonstrative embodiments, at least part of the functionality of message processor 157 may be implemented as part of message processor 158.

[00100] In some demonstrative embodiments, at least part of the functionality of message processor 157 may be implemented as part of any other element of wake-up receiver 150. For example, at least part of the functionality of message processor 157 may be implemented as part of receiver 156 and/or controller 159.

[00101] In some demonstrative embodiments, at least part of the functionality of receiver 156, controller 159 and/or message processor 157 may be implemented by an integrated circuit, for example, a chip, e.g., a SoC. In one example, the chip or SoC may be configured to perform one or more functionalities of radio 144, controller 154 and/or message processor 158. For example, the chip or SoC may include one or more elements of controller 159, one or more elements of message processor 157, and/or one or more elements of receiver 156, one or more elements of radio 144, one or more elements of message processor 158, and/or one or more elements of controller 154. In one example, wake-up receiver 150, message processor 158, controller 154, and/or radio 144 may be implemented as part of the chip or SoC.

[00102] In other embodiments, radio 144, wake-up receiver 150, controller 154 and/or message processor 158 may be implemented by one or more additional or alternative elements of device 140.

[00103] In some demonstrative embodiments, wake-up receiver 150 may be associated with one or more of antennas 147, e.g., which may be shared with radio 144. [00104] In other embodiments, wake-up receiver 150 may include, or may be associated with, another, e.g., separate, antenna.

[00105] In some demonstrative embodiments, wake-up receiver 150 may be configured to wake up radio 144, for example, if device 140 has data to transmit, and/or if data is to be received by radio 144.

[00106] In one example, wake-up receiver 150 may be configured to implement a low-power wake-up receiver (LP-WUR) scheme, for example, to wake up radio 144, e.g., only when device 140 is to receive data and/or to transmit data.

[00107] In some demonstrative embodiments, wake-up receiver 150 may have, for example, a relatively low power consumption, e.g., less than 100 microwatts. Accordingly, the power consumption of device 140 may be reduced for example, during times when there is no data to be received at device 140 and only wake-up receiver 150 is on.

[00108] In some demonstrative embodiments, wake-up receiver 150 may wake up radio 144, for example, based on a wake-up packet received from device 102.

[00109] In one example, receiver 156 may be configured to receive the wake-up packet from device 102, message processor 156 may be configured to process the wake-up packet, and/or controller 159 may be configured to wake up radio 144.

[00110] In some demonstrative embodiments, device 140 may be configured to transmit the wake-up packet to device 102, for example, to indicate to wake up receiver 150 that the radio 144 is to be woken up, e.g., to receive data from device 102.

[00111] In some demonstrative embodiments, controller 159 may be configured to cause radio 144 to wake up, e.g., to switch the radio 140 from a doze state, a sleep state or an inactive state to an awake state or an active state, for example, to receive data from device 102, e.g., subsequent to receiving the wake-up packet from device 102.

[00112] In some demonstrative embodiments, controller 159 may be configured to cause, control and/or trigger radio 144 to wake up, e.g., to switch the radio 144 from a doze state, a sleep state or an inactive state to an awake state or an active state, for example, to transmit data to device 102 and/or to another device. [00113] In some demonstrative embodiments, devices 102 and/or 140 may be configured to communicate one or more WUR frames, for example, in compliance with one or more wireless communication standards and/or protocols, e.g., as described below. [00114] In some demonstrative embodiments, devices 102 and/or 140 may be configured to generate, transmit, receive, and/or process one or more WUR frames according to a WUR frame format, e.g., as described below.

[00115] In some demonstrative embodiments, devices 102 and/or 140 may be configured to communicate one or more WUR frames, for example, including one or more types of frames and/or packets, e.g., a wake-up packet, a wake-up beacon and/or one or more other types of frames or packets, e.g., as described below.

[00116] In some demonstrative embodiments, a WUR frame may be configured as a wake-up packet, which may be, for example, designed for reception and/or processing by a wake-up radio, e.g., WURx 150, e.g., as described below. [00117] In some demonstrative embodiments, a WUR frame may be configured as a WUR Beacon frame, which may be configured, for example, to allow a device, e.g., a transmitter device, e.g., device 102, to send a WUR beacon, e.g., periodically, for example, to allow a receiver device, e.g., device 140, to maintain synchronization, e.g., as described below. [00118] In some demonstrative embodiments, a WURx, e.g., WURx 150, may not be required to wake up a primary connectivity radio, e.g., radio 144, for example, after receiving a WUR Beacon, e.g., in opposed to reception of a wake-up packet which may trigger waking up the primary radio.

[00119] In some demonstrative embodiments, the WUR Beacon frame may include, for example, at least one time value, for example, a partial Time Synchronization Function (TSF) value and/or any other time value, which may allow, for example, to maintain synchronization between a transmitter device and a receiver device, e.g., as described below.

[00120] Some demonstrative embodiments are described herein with respect to a wake-up frame (also referred to as "wake-up packet") and a WUR beacon frame. In other embodiments any other additional or alternative frames may be defined and/or implemented. In one example, a vendor specific frame may be defined to enable carrying of vendor specific content.

[00121] In some demonstrative embodiments, devices 102 and/or 140 may be configured to communicate a WUR frame, for example, in compliance with one or more existing wireless communication standards and/or protocols ("legacy standards"), for example, in compliance with one or more IEEE 802.11 standards.

[00122] In some demonstrative embodiments, the WUR frame may include a preamble ("legacy preamble") in compliance with one or more legacy standards.

[00123] In some demonstrative embodiments, the WUR frame may include a preamble in compliance with one or more IEEE 802.11 standards, for example, to enable one or more legacy devices to decode and/or process the preamble, e.g., to determine a length of the WUR frame.

[00124] In some demonstrative embodiments, the WUR frame may include a payload, e.g., following the legacy preamble. [00125] In some demonstrative embodiments, the payload may be modulated by a simple modulation scheme, for example, an on-off Keying (OOK) modulation scheme and/or any other modulation scheme.

[00126] Some demonstrative embodiments are described herein with respect to an OOK modulation scheme. However, in other embodiments the WUR frame may include a payload modulated according to any other amplitude- shift keying (ASK) modulation scheme, a Frequency Shift Keying (FSK) modulation scheme, and/or any other modulation scheme.

[00127] In some demonstrative embodiments, a WUR frame format may be configured, for example, based on one or more considerations, which may be configured to address one or more technical problems, and/or to achieve one or more technical advantages, e.g., as described below.

[00128] In one example, a WUR frame format may be configured to allow a length of the WUR frame to be optimized, for example, to support a reduced, e.g., even a lowest, data rate of a WUR radio, e.g., even a data rate of only 62.5 kilobits per second (kb/s) and/or any other data rate. [00129] In another example, the WUR frame format may be configured to support a fixed length header unified WUR frame format, e.g., which may be configured to support at least both the WUR Beacon and the wake-up packet and/or one or more other types of WUR frames and/or packets, for example, without additional length signaling. Such a configuration may provide a technical benefit, for example, by allowing a simplified implementation of a WURx.

[00130] In some demonstrative embodiments, a WUR frame format may be configured, for example, to support one or more types and/or configurations of fields, for example, to allow inclusion of an increased number of fields to be placed in a WUR frame, in a manner which may allow the technical benefit of enabling and/or supporting one or both of a unified frame format and/or a low overhead, e.g., as described below.

[00131] In some demonstrative embodiments, the WUR frame format may be configured to support one or more identification fields configured to carry identification information, e.g., as described below.

[00132] In some demonstrative embodiments, the WUR frame format may be configured to support one or more types of Identifiers (IDs), for example, Transmitter Identifier (TXID) and/or a Receiver Identifier (RXID) in a WUR frame, e.g., as described below. [00133] In some demonstrative embodiments, for example, the TXID may be used by a receiver to identify a transmitter device from which the WUR frame is sent. For example, a STA may be able to know that a WUR Beacon is not from its own Basic Service Set (BSS), for example, if the TXID does not identify, e.g., match, an ID of a transmitter device in the BSS. Some embodiments are described herein with respect to a TXID. In other embodiments, any other ID information and/or field may be used.

[00134] In some demonstrative embodiments, for example, the RXID may be used by a receiver, for example, to identify if the WUR frame is for the receiver, e.g., in a BSS formed by the transmitter. For example, a STA can know that a wake-up packet does not ask the STA to wake up, for example, if the RXID does not identify the STA, e.g., if the RXID does not match a predefined value corresponding to the STA, e.g., an identifier of the STA or a group identifier corresponding to the STA. Some embodiments are described herein with respect to a RXID. In other embodiments, any other ID information and/or field may be used. In one example, a predefined value of the RXID may be assigned to the STA by the transmitter, e.g., through radios 114 and/or 144.

[00135] In some demonstrative embodiments, the WUR frame format may be configured to support one or more authentication fields configured to carry authentication information, e.g., as described below.

[00136] In some demonstrative embodiments, the WUR frame format may be configured to support a Message Integrity Check (MIC) field in the WUR frame, for example, to provide authentication. [00137] For example, a STA may check the MIC field, e.g., to see if the wake-up packet is forged or not. In one example, the MIC may be computed, for example, based on an input including one or more of an agreed private key between an AP, e.g., a transmitter of the WUR frame, and a STA e.g., a receiver of the WUR frame, an AP ID if any, a STA ID if any, a frame content of e the wake-up packet, and/or any other additional or alternative information.

[00138] In some demonstrative embodiments, for example, when a private key is not available, the MIC may be viewed as a cyclic redundancy check (CRC) or a public key can be defined, e.g., to unify the operation.

[00139] In another example, the MIC field may include a Frame Check Sequence (FCS) value.

[00140] In some demonstrative embodiments, an authentication field (also referred to as "FCS/MIC/CRC") may include one or more of the above authentication values and/or any other additional or alternative authentication values.

[00141] In some demonstrative embodiments, the WUR frame format may be configured to support one or more fields ("counter fields") including one or more count values, e.g., as described below.

[00142] In some demonstrative embodiments, the WUR frame format may be configured to support a packet number field, e.g., as described below.

[00143] In some demonstrative embodiments, the WUR frame format may be configured to support the packet number field in the WUR frame, for example, to prevent a replay attack. [00144] In one example, the counter fields may be utilized to prevent a malicious attacker from replaying a wake-up packet that has been previously sent, e.g., since the counter value, e.g., the packet number, may be different for each transmission.

[00145] In some demonstrative embodiments, the WUR frame format may be configured to support one or more time-related fields, e.g., as described below.

[00146] In some demonstrative embodiments, the WUR frame format may be configured to support a time-based field, for example, a Timing Synchronization Function (TSF), e.g., a partial TSF, which may be carried in the WUR Beacon, for example, to achieve time synchronization with the STA, e.g., to enable duty cycle operation of a WURx.

[00147] In some demonstrative embodiments, the WUR frame format may be configured to support one or more type fields, e.g., as described below.

[00148] In some demonstrative embodiments, the WUR frame format may be configured to support a Type field, which may be configured to be carried in one or more WUR frames, e.g., even in every WUR frame, to identify a type of the WUR frame, e.g., to identify if a WUR frame is a wake-up packet, a WUR Beacon, or any other type of frame.

[00149] In some demonstrative embodiments, in some deployments, use cases and/or scenarios it may not be advantageous to define a plurality of different, e.g., individual and/or different, frame formats to support communication of one or more of the fields described above, e.g., the authentication fields, the identification fields, the counter fields, the time related fields and/or the type field, e.g., as described below.

[00150] In some demonstrative embodiments, defining a frame format according to a first option (Option 1) to include a TXID field, an RXID field, and an FCS/MIC/CRC field, may have one or more potential inefficiencies, disadvantages and/or technical problems, for example, in some deployments, use cases and/or scenarios, e.g., as described below.

[00151] Reference is made to Fig. 2, which schematically illustrates a frame format including one or more fields, which may be implemented in accordance with some demonstrative embodiments. [00152] As shown in Fig. 2, frame format 200, e.g., according to Option 1, may include a TXID field 202, an RXID field 204, an FCS/MIC/CRC field 206, and one or more other fields 208.

[00153] In some demonstrative embodiments, for example, in some use cases, scenarios and/or implementations, frame format 200 may result in a reduced number of bits, e.g., very few bits, left for the FCS/MIC/CRC field 206, for example, to control overhead. Accordingly, the authentication capability, e.g., provided by FCS/MIC/CRC field 206, may be compromised, e.g., due to a possible brutal force attack. Alternatively, if enough bits are to be allocated to one or more of fields 202, 204 and/or 206, e.g., all fields, a size of a WUR frame having frame format 300 may be large.

[00154] In some demonstrative embodiments, defining a frame format according to another option (Option 2) to include an RXID field, and an FCS/MIC/CRC field, e.g., while not including the TXID field, may have one or more potential inefficiencies, disadvantages and/or technical problems, for example, in some deployments, use cases and/or scenarios, e.g., as described below.

[00155] Reference is made to Fig. 3, which schematically illustrates a frame format 300 including one or more fields, which may be implemented in accordance with some demonstrative embodiments. [00156] As shown in Fig. 3, frame format 300 may include, e.g., according to Option 2, an RXID field 304, an FCS/MIC/CRC field 306, and one or more other fields 308, e.g., while not carrying a TXID field.

[00157] In some demonstrative embodiments, in some use cases, scenarios and/or implementations, defining a frame format, which does not include a TXID, may result in one or more potential technical problems and/or disadvantages. For example, in some use cases, scenarios and/or implementations, when a WUR Beacon is transmitted, an RXID value in the RXID field 304 may be likely to include a predetermined value, e.g., all ones or any other predefined value, to indicate a broadcast transmission. As a result, if a TXID field is not utilized, every STA may be required to perform one computation for every WUR Beacon.

[00158] In some demonstrative embodiments, defining a frame format according to another option (Option 3) to include an FCS/MIC/CRC field, e.g., while not supporting an identification field, may have one or more potential inefficiencies, disadvantages and/or technical problems, for example, in some deployments, use cases and/or scenarios, e.g., as described below.

[00159] Reference is made to Fig. 4, which schematically illustrates a frame format 400 including one or more fields, which may be implemented in accordance with some demonstrative embodiments.

[00160] As shown in Fig. 4, frame format 400 may include, an FCS/MIC/CRC field 406, and one or more other fields 408, e.g., while not carrying a TXID field, and/or an RXID field. [00161] In one example, the frame format 400, e.g., according to Option 3, which may not be configured to carry an identification field, e.g., may not allow for a STA to avoid performing a MIC calculation, e.g., when the frame is not intended for the STA. As a result, the STA may be required to perform the FCS/MIC/CRC calculation for every WUR frame, e.g., in order to know if this frame is for the STA or not for the STA. A STA may perform multiple MIC calculations, for example, if the STA belongs to and/or may be identified in multiple multicast wake-up groups.

[00162] In some demonstrative embodiments, one or more frame formats may be configured to support one or more time-related fields and/or counter fields, e.g., as described below. [00163] Reference is made to Fig. 5, which schematically illustrates a frame format 500 including one or more fields, which may be implemented in accordance with some demonstrative embodiments.

[00164] As shown in Fig. 5, frame format 500 may include a TSF field 502, and one or more other fields 508. [00165] In some demonstrative embodiments, a WUR beacon may be configured to include the partial TSF field 502.

[00166] Reference is made to Fig. 6, which schematically illustrates a frame format 600 including one or more fields, which may be implemented in accordance with some demonstrative embodiments. [00167] As shown in Fig. 6, frame format 600 may include a packet number field 604, and one or more other fields 608. [00168] In some demonstrative embodiments, a wake-up frame may be configured to include the packet number field 604.

[00169] In some demonstrative embodiments, for example, using different, e.g., dedicated, frame formats for the packet number, e.g., frame format 600, and for the partial TSF, e.g., frame format 500 (Fig. 5), may not provide a solution of a unified frame format, which may minimize an overhead for a WUR Beacon and a wake-up packet.

[00170] Referring back to Fig. 1, in some demonstrative embodiments, devices 102 and/or 140 may be configured to generate, transmit, receive, encode, decode, and/or process, one or more WUR frames according to a WUR frame format, e.g., a "unified" WUR format, which may be configured to support communication of one or more fields, for example, for one or more types of WUR frames, e.g., as described below.

[00171] In some demonstrative embodiments, the WUR frame format may be configured to support communication of identification information, for example, in a unified manner, e.g., as described below.

[00172] In some demonstrative embodiments, the WUR frame format may be configured to include first identification information, e.g., an RXID field and/or any other ID field, for example, for a wake-up packet; and/or second identification information, e.g., a TXID field and/or any other ID field, for example, for a WUR Beacon, e.g., as described below.

[00173] In some demonstrative embodiments, the WUR frame format may be configured to support the first identification information, e.g., an RXID field, and the second identification information, e.g., a TXID field, sharing the same length and/or to be located in a same relative location in the wake-up packet and the WUR Beacon, e.g., as described below.

[00174] In some demonstrative embodiments, the first identification information, e.g., an RXID field, and the second identification information, e.g., a TXID field, may be allowed to have different lengths, e.g., as described below. [00175] In some demonstrative embodiments, the WUR frame format may be configured to support the counter information e.g., the packet number and/or any other counter value, and/or the time related information, e.g., the partial TSF information and/or any other time-related information, for example, in a unified manner, e.g., as described below.

[00176] In some demonstrative embodiments, the WUR frame format may be configured to include a counter field, e.g., a packet number field and/or any other counter field, for example, for a wake-up packet, and/or a time-related field, e.g., a partial TSF field and/or any other time related field, for example, for a WUR Beacon, e.g., as described below.

[00177] In some demonstrative embodiments, the WUR frame format may be configured to support the counter field, e.g., the packet number field, and the time- related field, e.g., the partial TSF field, sharing the same length and/or to be located in the same relative location in the wake-up packet and the WUR Beacon, e.g., as described below.

[00178] In some demonstrative embodiments, the counter field, e.g., the packet number field, and the time-related field, e.g., the partial TSF field, may be allowed to have different lengths, e.g., as described below.

[00179] In some demonstrative embodiments, for example, a length of the first identification information e.g., the RXID, plus the counter field, e.g., the packet number, may be equal to a length of the second identification information, e.g., the TXID, plus the time-related information, e.g., the partial TSF, e.g., as described below.

[00180] In some demonstrative embodiments, the WUR frame format may include a first field and a second field, for example, after the first field, e.g., as described below.

[00181] In some demonstrative embodiments, for example, in a WUR beacon, the first field may be configured to include first identification information, e.g., a TXID and/or any other ID information, and the second field may be configured to include time-based information, e.g., a partial TSF and/or any other time-based information, e.g., as described below.

[00182] In some demonstrative embodiments, for example, in a wake-up packet, the first field may be configured to include second identification information, e.g., an RXID and/or any other ID information, and the second field may be configured to include a counter value, e.g., a packet number and/or any other counter value, e.g., as described below. [00183] In some demonstrative embodiments, devices 102 and/or 140 may be configured to communicate a WUR frame, e.g., as describe below.

[00184] In some demonstrative embodiments, device 102 may be configured to generate and transmit the WUR frame, and/or device 140 may be configured to receive and process the WUR frame, e.g., as describe below.

[00185] In some demonstrative embodiments, the WUR frame may include a WUR beacon or a wake-up packet and/or any other type of WUR frame, e.g., as describe below.

[00186] In some demonstrative embodiments, controller 124 may be configured to cause, control, and/or trigger device 102 and/or message processor 128 to generate WUR frame having a WUR frame format, e.g., as described below.

[00187] In some demonstrative embodiments, the WUR frame format may include a type field, a first type-dependent field, and a second type-dependent field, e.g., as described below. [00188] In some demonstrative embodiments, the type field may indicate a type of the WUR frame, for example, a WUR beacon or a wake-up packet, e.g., as described below. In other embodiments, the type field may be configured to indicate any other additional or alternative type of WUR frame, e.g., which may be supported according to the WUR frame format. [00189] In some demonstrative embodiments, for example, when the type field indicates that the WUR frame is a WUR beacon, the first type-dependent field may include first identification information, and the second type-dependent field may include a first type of information corresponding to the WUR beacon, e.g., as described below. [00190] In some demonstrative embodiments, for example, when the type field indicates that the WUR frame is a WUR beacon, the first type-dependent field may include first identification information to identify a transmitter of the WUR beacon, e.g., device 102, and the second type-dependent field may include at least a time value and/or one or more other values, e.g., as described below. [00191] In some demonstrative embodiments, for example, when the type field indicates that the WUR frame is a wake-up packet, the first type-dependent field may include second identification information, e.g., different from the first identification information, and the second type-dependent field may include a second type of information corresponding to the wake-up packet, e.g., as described below.

[00192] In some demonstrative embodiments, for example, when the type field indicates that the WUR frame is a wake-up packet, the first type-dependent field may include second identification information to identify a receiver of the wake-up packet, e.g., device 140, for example, at least in the BSS formed by the transmitter, and the second type-dependent field may include at least a counter value and/or one or more other values, e.g., as described below. [00193] In some demonstrative embodiments, the first identification information may include a TXID, e.g., as described below.

[00194] In other embodiments, the first identification information may include any other information to identify a transmitter of the WUR beacon.

[00195] In one example, the TXID may be based on, e.g., part of, a Medium Access Control (MAC) address of the transmitter of the WUR beacon, e.g., a MAC address of device 102.

[00196] In some demonstrative embodiments, the TXID may be indicated by an AP, for example, through a WUR negotiation, which may be performed, for example, with a primary connectivity radio, e.g., as described below. [00197] In some demonstrative embodiments, the TXID may be, for example, indicated in a WUR Mode element, and/or may be carried in a WUR action frame, e.g., as described below.

[00198] In some demonstrative embodiments, the second identification information may include an RXID, e.g., as described below. [00199] In other embodiments, the second identification information may include any other information to identify a receiver of the wake-up packet.

[00200] In some demonstrative embodiments, the RXID may include 11 bits. For example, each STA may be assigned with an Association Identifier (AID) and an additional group ID. For example, the RXID may be based on the AID and/or the group ID. [00201] In other embodiments, the RXID may have any other length and/or may be configured and/or defined based on any other additional or alternative identifier and/or parameter.

[00202] In some demonstrative embodiments, the time value may include a partial TSF value, e.g., as described below.

[00203] In other embodiments, the time value may include any other time-based value, function and/or information.

[00204] In some demonstrative embodiments, the counter value may include a packet number, e.g., as described below. [00205] In other embodiments, the counter value may include any other counter value and/or information.

[00206] In some demonstrative embodiments, the WUR frame may include an FCS field, for example, after the first and second type-dependent fields, e.g., as described below. [00207] In some demonstrative embodiments, the FCS field may include cyclic redundancy check (CRC) information, e.g., as described below. In other embodiments any other additional or alternative authentication and/or FCS information may be used.

[00208] In some demonstrative embodiments, controller 124 may be configured to cause, control, and/or trigger device 102 and/or radio 114 to transmit the WUR frame, e.g., to device 140.

[00209] In some demonstrative embodiments, device 140 may receive and process the WUR frame from device 102, e.g., as described below.

[00210] In some demonstrative embodiments, controller 159 may be configured to cause, control, and/or trigger WURx 150 to receive from device 102 the WUR frame having the WUR frame format including the type field to indicate the type of the WUR frame, the first type-dependent field, and the second type-dependent field, e.g., as described below.

[00211] In some demonstrative embodiments, controller 159 may be configured to cause, control, and/or trigger WURx 150 to process the first type-dependent field and/or the second type-dependent field, for example, based on the type field, e.g., as described below.

[00212] In some demonstrative embodiments, controller 159 may be configured to cause, control, and/or trigger WURx 150 to process the first type-dependent field as the first identification information to identify a transmitter of the WUR beacon and the second type-dependent field as a time value, for example, when the type field indicates that the WUR frame is a WUR beacon, e.g., as described below.

[00213] In some demonstrative embodiments, controller 159 may be configured to cause, control, and/or trigger WURx 150 process the first type-dependent field as the second identification information to identify a receiver of the wake-up packet, for example, at least in the BSS formed by the transmitter, and the second type-dependent field as a counter value, for example, when the type field is to indicate that the WUR frame is a wake-up packet, e.g., as described below.

[00214] In some demonstrative embodiments, controller 159 may be configured to cause, control, and/or trigger WURx 150 to authenticate the WUR frame, for example, based on the FCS field, e.g., as described below.

[00215] In some demonstrative embodiments, controller 159 may be configured to cause, control, and/or trigger WURx 150 to receive the wake-up packet when radio 144 is not active. [00216] In some demonstrative embodiments, controller 159 may be configured to cause, control, and/or trigger WURx 150 to wake-up radio 144, for example, based on the wake-up packet.

[00217] In some demonstrative embodiments, controller 159 may be configured to cause, control, and/or trigger WURx 150 to receive the WUR beacon when radio 144 is not active.

[00218] In some demonstrative embodiments, controller 159 may be configured to cause, control, and/or trigger WURx 150 to perform one or more operations, for example, based on the WUR beacon. For example, WURx 150 may perform one or more operations to maintain synchronization with device 102, for example, based on the WUR beacon. [00219] In one example, device 102 may transmit a WUR beacon, for example, to allow device 140 to maintain synchronization with device 102. According to this example, device 102 and/or message processor 128 may generate a WUR frame according to the WUR frame format including the type field indicating that the WUR frame is the WUR beacon, the first type-dependent field including the TXID and/or any other identifier information of device 102, the second type-dependent field including at least the partial TSF of device 102, and the FCS field after the first and second type-dependent fields. For example, device 140 may receive the WUR frame, and, based on the type field of the WUR frame, device 140 may identify that the WUR frame includes the WUR beacon, and may process the first type-dependent field as the TXID, the second type-dependent field as the partial TSF, and the FCS field.

[00220] In another example, device 102 may transmit a wake-up packet, for example, to wake up radio 144 of device 140. According to this example, device 102 and/or message processor 128 may generate the WUR frame according the WUR frame format including the type field indicating the WUR frame is the wake-up packet, the first type-dependent field including the RXID and/or any other identifier information to identify device 140, the second type-dependent field including at least a counter value, and the FCS field after the first and second type-dependent fields. Device 140 may receive the WUR frame, and, based on the type field of the WUR frame, device 140 may identify that the WUR frame includes the wake- up packet, and may process the first type-dependent field as the RXID, the second type-dependent field as the counter value, and the FCS field.

[00221] In some demonstrative embodiments, a length of the first identification information may be equal to a length of the second identification information. In one example, a length of the TXID field may be equal to a length of the RXID field, e.g., as described below.

[00222] In some demonstrative embodiments, a length of the first identification information may be different from a length of the second identification information. For example, a length of the TXID field may be different from a length of the RXID field, e.g., as described below. [00223] In some demonstrative embodiments, a length of the time value may be equal to a length of the counter value. For example, a length of the partial TSF may be equal to a length of the packet number, e.g., as described below.

[00224] In some demonstrative embodiments, a length of the time value may be different from a length of the counter value. For example, a length of the partial TSF may be different from a length of the packet number, e.g., as described below.

[00225] In some demonstrative embodiments, a total length of the type field, the first type-dependent field, and the second type-dependent field may be fixed, e.g., as described below. [00226] In one example, a total length of the type field, the first type-dependent field, and the second type-dependent field, e.g., when the WUR frame includes WUR beacon, may be equal to a total length of the type field, the first type-dependent field, and the second type-dependent field, e.g., when the WUR frame includes wake-up packet. [00227] In some demonstrative embodiments, a total length of the first and second type-dependent fields when the WUR frame includes the WUR beacon may be equal to a total length of the first and second type-dependent fields when the WUR frame includes the wake-up packet, e.g., as described below.

[00228] In some demonstrative embodiments, the TXID may be indicated by an AP, e.g., device 102, for example, through a WUR negotiation, which may be performed, for example, with a primary connectivity radio, e.g., radio 144 of device 140.

[00229] In some demonstrative embodiments, the TXID may be, for example, indicated in a WUR Mode element, and/or may be carried in a WUR action frame from device 102, e.g., as described below. [00230] In some demonstrative embodiments, controller 124 may be configured to cause, control, and/or trigger device 102 and/or radio 114 to transmit a WUR action frame configured for WUR negotiation, e.g., as described below.

[00231] In some demonstrative embodiments, the WUR action frame may include the TXID of device 102, e.g., as described below. [00232] In some demonstrative embodiments, controller 159 may be configured to cause, control, and/or trigger device 140 and/or radio 144 to process the WUR action frame including the TXID from device 102, e.g., as described below.

[00233] Reference is made to Fig. 7, which schematically illustrates a frame format of a WUR frame 710, in accordance with some demonstrative embodiments.

[00234] In some demonstrative embodiments, as shown in Fig. 7, WUR frame 700 may include a type field 701, e.g., to indicate the type of WUR frame 700, a first type-dependent field 712, a second type-dependent field 716, and an FCS field 719.

[00235] In some demonstrative embodiments, type field 701 may be before type dependent fields 12 and 716. For example, type field may be included as part of a header, preamble, and/or one or more other fields of the WUR frame.

[00236] In some demonstrative embodiments, for example, when the type field indicates that the WUR frame 700 is a WUR beacon, first type-dependent field 712 may include first identification information to identify a transmitter of the WUR beacon, e.g., a TXID and/or any other identification information, and second type- dependent field 716 may include a time value, e.g., a partial TSF field and/or any other time value.

[00237] In some demonstrative embodiments, for example, when the type field indicates that the WUR frame 700 is a wake-up packet, first type-dependent field 712 may include second identification information to identify a receiver of the wake-up packet, e.g., an RXID and/or any other identification information, and second type- dependent field 716 may include a counter value, e.g., a packet number field and/or any other counter information.

[00238] In some demonstrative embodiments, one or more fields of the WUR frame 700 may have a fixed length, e.g., as described below.

[00239] In some demonstrative embodiments, one or more fields of the WUR frame 700 may not have a fixed length, e.g., as described below.

[00240] In some demonstrative embodiments, field 712 may be configured to have a fixed length. For example, a length of the first identification information may be equal to a length of the second identification information, e.g., as described below. [00241] In some demonstrative embodiments, a length of field 712 may not be fixed. For example, a length of the first identification information may be different from a length of the second identification information, e.g., as described below.

[00242] In some demonstrative embodiments, a length of field 714 may be fixed. For example, a length of the time value may be equal to a length of the counter value, e.g., as described below.

[00243] In some demonstrative embodiments, a length of field 714 may not be fixed. For example, a length of the time value may be different from a length of the counter value, e.g., as described below. [00244] In some demonstrative embodiments, a total length of the type field 701, the first type-dependent field 712 and the second type-dependent field 716 may be fixed, e.g., as described below.

[00245] In some demonstrative embodiments, a total length of the first type- dependent field 712 and the second type-dependent field 716, when the WUR frame 700 includes a WUR beacon, may be equal to a total length of the first type- dependent field 712 and the second type-dependent field 716, when the WUR frame 700 includes a wake-up packet, e.g., as described below.

[00246] Reference is made to Fig. 8, which schematically illustrates a WUR frame format 810, in accordance with some demonstrative embodiments. [00247] In some demonstrative embodiments, WUR frame format 800 may be configured in accordance with the WUR frame format of Fig. 7.

[00248] In some demonstrative embodiments, as shown in Fig. 8, WUR frame format 800 may include a type field 801, e.g., as part of one or more other fields 818, a first type-dependent field 812, a second type-dependent field 816, and an FCS field 819. [00249] In some demonstrative embodiments, the contents of first type-dependent field 812 and/or second type-dependent field 816 may be configured, for example, based on the type of a WUR frame, e.g., as indicated by type field 801.

[00250] In some demonstrative embodiments, as shown in Fig. 8, for example, when the type field 801 indicates that the WUR frame is a WUR beacon, a frame format 820 may be used, and, accordingly, first type-dependent field 812 may include a first identifier field, e.g., TXID field 811, and second type-dependent field 816 may include a time value field, e.g., partial TSF field 815.

[00251] In some 801 demonstrative embodiments, as shown in Fig. 8, for example, when the type field indicates that the WUR frame is a wake-up packet, a WUR frame format 830 may be used, and, accordingly, first type-dependent field 812 may include a second identifier field, e.g., an RXID field 813, and second type-dependent field 816 may include a counter field, e.g., packet number field 817.

[00252] In some demonstrative embodiments, as shown in Fig. 8, the WUR frame format 800 may be configured using a fixed length for field 812 and/or 816. [00253] In some demonstrative embodiments, as shown in Fig. 8, a length of TXID field 811 may be equal to a length of RXID field 813.

[00254] In some demonstrative embodiments, as shown in Fig. 8, a length of the partial TSF field 815 may be equal to a length of the packet number field 817.

[00255] In some demonstrative embodiments, as shown in Fig. 8, a total length of the first type-dependent field 812 and the second type-dependent field 816 may be fixed, e.g., as described below.

[00256] In one example, as shown in Fig. 8, a total length of the type field 801, the TXID field 811, and the partial TSF field 815, e.g., when the WUR frame 800 includes the WUR beacon format 820, may be equal to a total length of the type field 801, the RXID field 813, and the packet number field 817, e.g., when the WUR frame 800 includes the wake-up packet format 830.

[00257] Reference is made to Fig. 9, which schematically illustrates a WUR frame format configured to support a first WUR frame format 910 and a second WUR frame format 920 of a WUR frame, in accordance with some demonstrative embodiments. [00258] In some demonstrative embodiments, for example, WUR frame format 910 may be configured to support a WUR beacon transmission, and/or WUR frame format 920 may be configured to support a wake-up packet transmission.

[00259] In some demonstrative embodiments, as shown in Fig. 9, WUR frame format 910 may include a type field 901, e.g., as part of one or more other fields 918, a TXID field 911, partial TSF field 915, and an FCS field 919, for example, when the WUR frame includes a WUR beacon. [00260] In some demonstrative embodiments, as shown in Fig. 9, WUR frame format 920 may include type field 901, e.g., as part of one or more other fields 918, an RXID field 913, packet number field 917, and FCS field 919, for example, when the WUR frame includes a wake-up packet. [00261] In some demonstrative embodiments, as shown in Fig. 9, WUR frame format 910 and WUR frame format 920 may include one or more fields having a different or non-fixed length.

[00262] In some demonstrative embodiments, as shown in Fig. 9, a length of TXID field 911 may be different from a length of RXID field 913. [00263] In some demonstrative embodiments, as shown in Fig. 9, a length of the partial TSF field 915 may be different from a length of the packet number field 917.

[00264] In some demonstrative embodiments, as shown in Fig. 9, a total length of WUR frame format 910 may be equal to a total length of WUR frame format 920.

[00265] In some demonstrative embodiments, as shown in Fig. 9, a total length of the TXID field 911 and the partial TSF field 915 in WUR frame format 910, may be equal to a total length of the RXID field 913 and the packet number field 917 in WUR frame format 920.

[00266] Referring back to Fig. 1, in some demonstrative embodiments, the WUR frame format described herein, for example, the WUR frame formats of Figs. 7, 8 and/or 9, may support one or more fields for identification information, e.g., a TXID for a WUR Beacon and/or a RXID for a wake-up packet. Allowing to include this identification information in a WUR frame may enable, for example, filtering, and/or may allow reducing a number of FCS/MIC/CRC computations that a WURx may perform for a received WUR Beacon or a wake-up packet. [00267] In some demonstrative embodiments, the WUR frame format described herein, for example, the WUR frame formats of Figs. 7, 8 and/or 9, may support replacing an RXID in a wake-up packet with a TXID in a WUR Beacon, which may allow, for example, to reduce collision probability.

[00268] In some demonstrative embodiments, the WUR frame format described herein, for example, the WUR frame formats of Figs. 7, 8 and/or 9, may provide, for example, a fixed length design for one or more portions of the WUR frame, for example, for the header and FCS, e.g., to support for both a wake-up packet and a WUR Beacon, which may be, in some cases, for example, two most important WUR frames for a WUR scheme.

[00269] In some demonstrative embodiments, the WUR frame format described herein, for example, the WUR frame formats of Figs. 7, 8 and/or 9, may provide, for example, a unified frame format, which may allow a receiving STA of a WUR frame to simplify a receiving operation, and/or to support only one parsing operation of the fields of the WUR frame.

[00270] In some demonstrative embodiments, the WUR frame format described herein, for example, the WUR frame formats of Figs. 7, 8 and/or 9, may provide, for example, a reduced or even minimized frame size, for example, even without adding unnecessary fields for a wake-up packet or a WUR Beacon.

[00271] In some demonstrative embodiments, in one implementation example, the identification fields, e.g., the RXID and/or TXID fields, may be reused, for example, to provide one or more performance improvements and/or enhancements, e.g., as described below.

[00272] For example, the RXID may include 11 bits, a size of the FCS/MIC/CRC may be x, and a number of APs may be n.

[00273] For example, the RXID field may be reused as a TXID field in a WUR Beacon.

[00274] For example, it may be assumed that each AP of the APs may end up with one sequence in FCS/MIC/CRC, e.g., with uniform random distribution.

[00275] For example, it may be assumed that each AP may choose a TXID with a uniform random distribution. [00276] For example, the probability of at least one pair of APs ending up with the same TXID and FCS/MIC/CRC, for example, without reusing the RXID field as a TXID filed, may be determined, e.g., as follows:

128 1.89*10^Λ-4% 7.39*10^Λ-7%

256 7.6* 10^Λ-4% 2.97*10^Λ-6%

512 3.04*10^Λ-3% 1.19*10^Λ-5%

Table 1

[00277] For example, the probability of at least one pair of APs ending up with the same TXID and FCS/MIC/CRC, for example, when reusing the RXID field as the TXID field, may be determined, e.g., as follows:

Table 2

[00278] Reference is made to Fig. 10, which schematically illustrates a method of communicating a WUR frame, in accordance with some demonstrative embodiments. For example, one or more of the operations of the method of Fig. 10 may be performed by one or more elements of a system, e.g., system 100 (Fig. 1), for example, one or more wireless devices, e.g., device 102 (Fig. 1) and/or device 140 (Fig. 1); a controller, e.g., controller 159 (Fig. 1), controller 124 (Fig. 1) and/or controller 154 (Fig. 1); a radio, e.g., radio 114 (Fig. 1) and/or radio 144 (Fig. 1); a transmitter, e.g., transmitter 118 and/or transmitter 148 (Fig. 1); a receiver e.g., receiver 116, receiver 156 and/or receiver 146 (Fig. 1); a wake-up receiver, e.g., wake-up receiver 150 (Fig. 1); and/or a message processor, e.g., message processor 157 (Fig. 1), message processor 128 (Fig. 1) and/or message processor 158 (Fig. 1). [00279] As indicated at block 1002, the method may include generating a WUR frame having a WUR frame format including a type field, a first type-dependent field, and a second type-dependent field, the type field to indicate a type of the WUR frame, wherein, when the type field is to indicate that the WUR frame is a WUR beacon, the first type-dependent field includes first identification information to identify a transmitter of the WUR beacon and the second type-dependent field includes a time value, and, when the type field is to indicate that the WUR frame is a wake-up packet, the first type-dependent field includes second identification information to identify a receiver of the wake-up packet, for example, at least in the BSS formed by the transmitter, and the second type-dependent field may include a counter value. For example, controller 124 (Fig. 1) may control, cause and/or trigger device 102 (Fig. 1) to generate the WUR frame having the WUR frame format 700 (Fig. 7) including a type field 701 (Fig. 7), a first type-dependent field 712 (Fig. 7), and a second type- dependent field 718 (Fig. 7), e.g., as described above. [00280] As indicated at block 1004, the method may include transmitting the WUR frame. For example, controller 124 (Fig. 1) may control, cause and/or trigger radio 114 (Fig. 1) to transmit the WUR frame, e.g., as described above.

[00281] Reference is made to Fig. 11, which schematically illustrates a method of communicating a WUR frame, in accordance with some demonstrative embodiments. For example, one or more of the operations of the method of Fig. 10 may be performed by one or more elements of a system, e.g., system 100 (Fig. 1), for example, one or more wireless devices, e.g., device 102 (Fig. 1) and/or device 140 (Fig. 1); a controller, e.g., controller 159 (Fig. 1), controller 124 (Fig. 1) and/or controller 154 (Fig. 1); a radio, e.g., radio 114 (Fig. 1) and/or radio 144 (Fig. 1); a transmitter, e.g., transmitter 118 and/or transmitter 148 (Fig. 1); a receiver e.g., receiver 116, receiver 156 and/or receiver 146 (Fig. 1); a wake-up receiver, e.g., wake-up receiver 150 (Fig. 1); and/or a message processor, e.g., message processor 157 (Fig. 1), message processor 128 (Fig. 1) and/or message processor 158 (Fig. 1).

[00282] As indicated at block 1102, the method may include receiving by a WURx of a first wireless communication device a WUR frame from a second wireless communication device, the WUR frame having a WUR frame format including a type field to indicate a type of the WUR frame, a first type-dependent field, and a second type-dependent field. For example, wake-up receiver 150 (Fig. 1) may receive from device 102 (Fig. 1) the WUR frame having the WUR frame format 700 (Fig. 7) including a type field 701 (Fig. 7), the first type-dependent field 712 (Fig. 7), and the second type-dependent field 718 (Fig. 7), e.g., as described above.

[00283] As indicated at block 1104, the method may include, when the type field is to indicate that the WUR frame is a WUR beacon, processing the first type-dependent field as first identification information to identify a transmitter of the WUR beacon and the second type-dependent field as a time value. For example, wake-up receiver 150 (Fig. 1) may process the first type-dependent field 712 (Fig. 7) as the first identification information and the second type-dependent field 718 (Fig. 7) as the time value, for example, when the type field 701 (Fig. 7) is to indicate that the WUR frame is a WUR beacon, e.g., as described above.

[00284] As indicated at block 1006, the method may include, when the type field is to indicate that the WUR frame is a wake-up packet, processing the first type-dependent field as second identification information to identify a receiver of the wake-up packet, e.g., in the BSS formed by the transmitter, and the second type-dependent field as a counter value. For example, wake-up receiver 150 (Fig. 1) may process the first type- dependent field 712 (Fig. 7) as the second identification information and the second type-dependent field 718 (Fig. 7) as the counter value, for example, when the type field 701 (Fig. 7) is to indicate that the WUR frame is a wake-up packet, e.g., as described above.

[00285] Reference is made to Fig. 12, which schematically illustrates a product of manufacture 1200, in accordance with some demonstrative embodiments. Product 1200 may include one or more tangible computer-readable ("machine readable") non- transitory storage media 1202, which may include computer-executable instructions, e.g., implemented by logic 1204, operable to, when executed by at least one processor, e.g., computer processor, enable the at least one processor to implement one or more operations at device 102 (Fig. 1), device 140 (Fig. 1), radio 114 (Fig. 1), radio 144 (Fig. 1), wake-up receiver 150 (Fig. 1), transmitter 118 (Fig. 1), transmitter 148 (Fig. 1), receiver 116 (Fig. 1), receiver 146 (Fig. 1), controller 124 (Fig. 1), controller 154 (Fig. 1), message processor 128 (Fig. 1), message processor 128 (Fig. 1), and/or message processor 158 (Fig. 1), to cause device 102 (Fig. 1), device 140 (Fig. 1), radio 114 (Fig. 1), radio 144 (Fig. 1), wake-up receiver 150 (Fig. 1), transmitter 118 (Fig. 1), transmitter 148 (Fig. 1), receiver 116 (Fig. 1), receiver 146 (Fig. 1), controller 124 (Fig. 1), controller 154 (Fig. 1), message processor 128 (Fig. 1), message processor 128 (Fig. 1), and/or message processor 158 (Fig. 1) to perform one or more operations, and/or to perform, trigger and/or implement one or more operations, communications and/or functionalities described above with reference to Figs. 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, and/or 11, and/or one or more operations described herein. The phrase "non-transitory machine-readable medium" is directed to include all computer-readable media, with the sole exception being a transitory propagating signal.

[00286] In some demonstrative embodiments, product 1200 and/or storage media 1202 may include one or more types of computer-readable storage media capable of storing data, including volatile memory, non-volatile memory, removable or nonremovable memory, erasable or non-erasable memory, writeable or re-writeable memory, and the like. For example, storage media 1202 may include, RAM, DRAM, Double-Data-Rate DRAM (DDR-DRAM), SDRAM, static RAM (SRAM), ROM, programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), Compact Disk ROM (CD-ROM), Compact Disk Recordable (CD-R), Compact Disk Rewriteable (CD-RW), flash memory (e.g., NOR or NAND flash memory), content addressable memory (CAM), polymer memory, phase-change memory, ferroelectric memory, silicon-oxide-nitride- oxide- silicon (SONOS) memory, a disk, a floppy disk, a hard drive, an optical disk, a magnetic disk, a card, a magnetic card, an optical card, a tape, a cassette, and the like. The computer-readable storage media may include any suitable media involved with downloading or transferring a computer program from a remote computer to a requesting computer carried by data signals embodied in a carrier wave or other propagation medium through a communication link, e.g., a modem, radio or network connection.

[00287] In some demonstrative embodiments, logic 1204 may include instructions, data, and/or code, which, if executed by a machine, may cause the machine to perform a method, process and/or operations as described herein. The machine may include, for example, any suitable processing platform, computing platform, computing device, processing device, computing system, processing system, computer, processor, or the like, and may be implemented using any suitable combination of hardware, software, firmware, and the like. [00288] In some demonstrative embodiments, logic 1204 may include, or may be implemented as, software, a software module, an application, a program, a subroutine, instructions, an instruction set, computing code, words, values, symbols, and the like. The instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, and the like. The instructions may be implemented according to a predefined computer language, manner or syntax, for instructing a processor to perform a certain function. The instructions may be implemented using any suitable high-level, low-level, object- oriented, visual, compiled and/or interpreted programming language, such as C, C++, Java, BASIC, Matlab, Pascal, Visual BASIC, assembly language, machine code, and the like.

EXAMPLES

[00289] The following examples pertain to further embodiments.

[00290] Example 1 includes an apparatus comprising logic and circuitry configured to cause a wireless communication device to generate a Wake-up Radio (WUR) frame having a WUR frame format comprising a type field, a first type-dependent field, and a second type-dependent field, the type field to indicate a type of the WUR frame, wherein, when the type field is to indicate that the WUR frame is a WUR beacon, the first type-dependent field comprises first identification information to identify a transmitter of the WUR beacon and the second type-dependent field comprises a time value, and, when the type field is to indicate that the WUR frame is a wake-up packet, the first type-dependent field comprises second identification information to identify a receiver of the wake-up packet and the second type-dependent field comprises a counter value; and transmit the WUR frame. [00291] Example 2 includes the subject matter of Example 1, and optionally, wherein the time value comprises a partial Timing Synchronization Function (TSF) value.

[00292] Example 3 includes the subject matter of Example 1 or 2, and optionally, wherein the counter value comprises a packet number.

[00293] Example 4 includes the subject matter of any one of Examples 1-3, and optionally, wherein the WUR frame comprises a Frame Check Sequence (FCS) field after the first and second type-dependent fields. [00294] Example 5 includes the subject matter of Example 4, and optionally, wherein the FCS field comprises cyclic redundancy check (CRC) information.

[00295] Example 6 includes the subject matter of any one of Examples 1-5, and optionally, wherein a length of the first identification information is equal to a length of the second identification information.

[00296] Example 7 includes the subject matter of any one of Examples 1-5, and optionally, wherein a length of the first identification information is different from a length of the second identification information.

[00297] Example 8 includes the subject matter of any one of Examples 1-5, and optionally, wherein a length of the time value is equal to a length of the counter value.

[00298] Example 9 includes the subject matter of any one of Examples 1-5, and optionally, wherein a length of the time value is different from a length of the counter value.

[00299] Example 10 includes the subject matter of any one of Examples 1-9, and optionally, wherein a total length of the type field, the first type-dependent field and the second type-dependent field is fixed.

[00300] Example 11 includes the subject matter of any one of Examples 1-10, and optionally, wherein a total length of the first and second type-dependent fields when the WUR frame comprises the WUR beacon is equal to a total length of the first and second type-dependent fields when the WUR frame comprises the wake-up packet.

[00301] Example 12 includes the subject matter of any one of Examples 1-11, and optionally, wherein the first identification information comprises a Transmitter Identifier (TXID).

[00302] Example 13 includes the subject matter of Example 12, and optionally, wherein the apparatus is configured to cause the wireless communication device to transmit a WUR action frame configured for WUR negotiation, the WUR action frame comprising the TXID.

[00303] Example 14 includes the subject matter of any one of Examples 1-13, and optionally, comprising a radio to transmit the WUR frame. [00304] Example 15 includes the subject matter of any one of Examples 1-14, and optionally, comprising a processor, a memory, and one or more antennas. [00305] Example 16 includes a system of wireless communication comprising a wireless communication device, the wireless communication device comprising one or more antennas; a radio; a memory; a processor; and a controller configured to cause the wireless communication device to generate a Wake-up Radio (WUR) frame having a WUR frame format comprising a type field, a first type-dependent field, and a second type-dependent field, the type field to indicate a type of the WUR frame, wherein, when the type field is to indicate that the WUR frame is a WUR beacon, the first type-dependent field comprises first identification information to identify a transmitter of the WUR beacon and the second type-dependent field comprises a time value, and, when the type field is to indicate that the WUR frame is a wake-up packet, the first type-dependent field comprises second identification information to identify a receiver of the wake-up packet and the second type-dependent field comprises a counter value; and transmit the WUR frame.

[00306] Example 17 includes the subject matter of Example 16, and optionally, wherein the time value comprises a partial Timing Synchronization Function (TSF) value.

[00307] Example 18 includes the subject matter of Example 16 or 17, and optionally, wherein the counter value comprises a packet number.

[00308] Example 19 includes the subject matter of any one of Examples 16-18, and optionally, wherein the WUR frame comprises a Frame Check Sequence (FCS) field after the first and second type-dependent fields.

[00309] Example 20 includes the subject matter of Example 19, and optionally, wherein the FCS field comprises cyclic redundancy check (CRC) information.

[00310] Example 21 includes the subject matter of any one of Examples 16-20, and optionally, wherein a length of the first identification information is equal to a length of the second identification information.

[00311] Example 22 includes the subject matter of any one of Examples 16-20, and optionally, wherein a length of the first identification information is different from a length of the second identification information. [00312] Example 23 includes the subject matter of any one of Examples 16-20, and optionally, wherein a length of the time value is equal to a length of the counter value. [00313] Example 24 includes the subject matter of any one of Examples 16-20, and optionally, wherein a length of the time value is different from a length of the counter value.

[00314] Example 25 includes the subject matter of any one of Examples 16-24, and optionally, wherein a total length of the type field, the first type-dependent field and the second type-dependent field is fixed.

[00315] Example 26 includes the subject matter of any one of Examples 16-25, and optionally, wherein a total length of the first and second type-dependent fields when the WUR frame comprises the WUR beacon is equal to a total length of the first and second type-dependent fields when the WUR frame comprises the wake-up packet.

[00316] Example 27 includes the subject matter of any one of Examples 16-26, and optionally, wherein the first identification information comprises a Transmitter Identifier (TXID).

[00317] Example 28 includes the subject matter of Example 27, and optionally, wherein the controller is configured to cause the wireless communication device to transmit a WUR action frame configured for WUR negotiation, the WUR action frame comprising the TXID.

[00318] Example 29 includes a method to be performed by a wireless communication device, the method comprising generating a Wake-up Radio (WUR) frame having a WUR frame format comprising a type field, a first type-dependent field, and a second type-dependent field, the type field to indicate a type of the WUR frame, wherein, when the type field is to indicate that the WUR frame is a WUR beacon, the first type-dependent field comprises first identification information to identify a transmitter of the WUR beacon and the second type-dependent field comprises a time value, and, when the type field is to indicate that the WUR frame is a wake-up packet, the first type-dependent field comprises second identification information to identify a receiver of the wake-up packet and the second type-dependent field comprises a counter value; and transmitting the WUR frame.

[00319] Example 30 includes the subject matter of Example 29, and optionally, wherein the time value comprises a partial Timing Synchronization Function (TSF) value. [00320] Example 31 includes the subject matter of Example 29 or 30, and optionally, wherein the counter value comprises a packet number.

[00321] Example 32 includes the subject matter of any one of Examples 29-31, and optionally, wherein the WUR frame comprises a Frame Check Sequence (FCS) field after the first and second type-dependent fields.

[00322] Example 33 includes the subject matter of Example 32, and optionally, wherein the FCS field comprises cyclic redundancy check (CRC) information.

[00323] Example 34 includes the subject matter of any one of Examples 29-33, and optionally, wherein a length of the first identification information is equal to a length of the second identification information.

[00324] Example 35 includes the subject matter of any one of Examples 29-33, and optionally, wherein a length of the first identification information is different from a length of the second identification information.

[00325] Example 36 includes the subject matter of any one of Examples 29-33, and optionally, wherein a length of the time value is equal to a length of the counter value.

[00326] Example 37 includes the subject matter of any one of Examples 29-33, and optionally, wherein a length of the time value is different from a length of the counter value.

[00327] Example 38 includes the subject matter of any one of Examples 29-37, and optionally, wherein a total length of the type field, the first type-dependent field and the second type-dependent field is fixed.

[00328] Example 39 includes the subject matter of any one of Examples 29-38, and optionally, wherein a total length of the first and second type-dependent fields when the WUR frame comprises the WUR beacon is equal to a total length of the first and second type-dependent fields when the WUR frame comprises the wake-up packet.

[00329] Example 40 includes the subject matter of any one of Examples 29-39, and optionally, wherein the first identification information comprises a Transmitter Identifier (TXID).

[00330] Example 41 includes the subject matter of Example 40, and optionally, comprising transmitting a WUR action frame configured for WUR negotiation, the WUR action frame comprising the TXID. [00331] Example 42 includes a product comprising one or more tangible computer- readable non-transitory storage media comprising computer-executable instructions operable to, when executed by at least one processor, enable the at least one processor to cause a wireless communication device to generate a Wake-up Radio (WUR) frame having a WUR frame format comprising a type field, a first type-dependent field, and a second type-dependent field, the type field to indicate a type of the WUR frame, wherein, when the type field is to indicate that the WUR frame is a WUR beacon, the first type-dependent field comprises first identification information to identify a transmitter of the WUR beacon and the second type-dependent field comprises a time value, and, when the type field is to indicate that the WUR frame is a wake-up packet, the first type-dependent field comprises second identification information to identify a receiver of the wake-up packet and the second type-dependent field comprises a counter value; and transmit the WUR frame.

[00332] Example 43 includes the subject matter of Example 42, and optionally, wherein the time value comprises a partial Timing Synchronization Function (TSF) value.

[00333] Example 44 includes the subject matter of Example 42 or 43, and optionally, wherein the counter value comprises a packet number.

[00334] Example 45 includes the subject matter of any one of Examples 42-44, and optionally, wherein the WUR frame comprises a Frame Check Sequence (FCS) field after the first and second type-dependent fields.

[00335] Example 46 includes the subject matter of Example 45, and optionally, wherein the FCS field comprises cyclic redundancy check (CRC) information.

[00336] Example 47 includes the subject matter of any one of Examples 42-46, and optionally, wherein a length of the first identification information is equal to a length of the second identification information.

[00337] Example 48 includes the subject matter of any one of Examples 42-46, and optionally, wherein a length of the first identification information is different from a length of the second identification information. [00338] Example 49 includes the subject matter of any one of Examples 42-46, and optionally, wherein a length of the time value is equal to a length of the counter value. [00339] Example 50 includes the subject matter of any one of Examples 42-46, and optionally, wherein a length of the time value is different from a length of the counter value.

[00340] Example 51 includes the subject matter of any one of Examples 42-50, and optionally, wherein a total length of the type field, the first type-dependent field and the second type-dependent field is fixed.

[00341] Example 52 includes the subject matter of any one of Examples 42-51, and optionally, wherein a total length of the first and second type-dependent fields when the WUR frame comprises the WUR beacon is equal to a total length of the first and second type-dependent fields when the WUR frame comprises the wake-up packet.

[00342] Example 53 includes the subject matter of any one of Examples 42-52, and optionally, wherein the first identification information comprises a Transmitter Identifier (TXID).

[00343] Example 54 includes the subject matter of Example 53, and optionally, wherein the instructions, when executed, cause the wireless communication device to transmit a WUR action frame configured for WUR negotiation, the WUR action frame comprising the TXID.

[00344] Example 55 includes an apparatus of wireless communication by a wireless communication device, the apparatus comprising means for generating a Wake-up Radio (WUR) frame having a WUR frame format comprising a type field, a first type- dependent field, and a second type-dependent field, the type field to indicate a type of the WUR frame, wherein, when the type field is to indicate that the WUR frame is a WUR beacon, the first type-dependent field comprises first identification information to identify a transmitter of the WUR beacon and the second type-dependent field comprises a time value, and, when the type field is to indicate that the WUR frame is a wake-up packet, the first type-dependent field comprises second identification information to identify a receiver of the wake-up packet and the second type- dependent field comprises a counter value; and means for transmitting the WUR frame. [00345] Example 56 includes the subject matter of Example 55, and optionally, wherein the time value comprises a partial Timing Synchronization Function (TSF) value. [00346] Example 57 includes the subject matter of Example 55 or 56, and optionally, wherein the counter value comprises a packet number.

[00347] Example 58 includes the subject matter of any one of Examples 55-57, and optionally, wherein the WUR frame comprises a Frame Check Sequence (FCS) field after the first and second type-dependent fields.

[00348] Example 59 includes the subject matter of Example 58, and optionally, wherein the FCS field comprises cyclic redundancy check (CRC) information.

[00349] Example 60 includes the subject matter of any one of Examples 55-59, and optionally, wherein a length of the first identification information is equal to a length of the second identification information.

[00350] Example 61 includes the subject matter of any one of Examples 55-59, and optionally, wherein a length of the first identification information is different from a length of the second identification information.

[00351] Example 62 includes the subject matter of any one of Examples 55-59, and optionally, wherein a length of the time value is equal to a length of the counter value.

[00352] Example 63 includes the subject matter of any one of Examples 55-59, and optionally, wherein a length of the time value is different from a length of the counter value.

[00353] Example 64 includes the subject matter of any one of Examples 55-63, and optionally, wherein a total length of the type field, the first type-dependent field and the second type-dependent field is fixed.

[00354] Example 65 includes the subject matter of any one of Examples 55-64, and optionally, wherein a total length of the first and second type-dependent fields when the WUR frame comprises the WUR beacon is equal to a total length of the first and second type-dependent fields when the WUR frame comprises the wake-up packet.

[00355] Example 66 includes the subject matter of any one of Examples 55-65, and optionally, wherein the first identification information comprises a Transmitter Identifier (TXID).

[00356] Example 67 includes the subject matter of Example 66, and optionally, comprising means for transmitting a WUR action frame configured for WUR negotiation, the WUR action frame comprising the TXID. [00357] Example 68 includes an apparatus comprising logic and circuitry configured to cause a first wireless communication device to receive by a Wake-up Receiver (WURx) of the first wireless communication device a Wake-up Radio (WUR) frame from a second wireless communication device, the WUR frame having a WUR frame format comprising a type field to indicate a type of the WUR frame, a first type- dependent field, and a second type-dependent field; when the type field is to indicate that the WUR frame is a WUR beacon, process the first type-dependent field as first identification information to identify a transmitter of the WUR beacon and the second type-dependent field as a time value; and when the type field is to indicate that the WUR frame is a wake-up packet, process the first type-dependent field as second identification information to identify a receiver of the wake-up packet and the second type-dependent field as a counter value.

[00358] Example 69 includes the subject matter of Example 68, and optionally, wherein the time value comprises a partial Timing Synchronization Function (TSF) value.

[00359] Example 70 includes the subject matter of Example 68 or 69, and optionally, wherein the counter value comprises a packet number.

[00360] Example 71 includes the subject matter of any one of Examples 68-70, and optionally, wherein the WUR frame comprises a Frame Check Sequence (FCS) field after the first and second type-dependent fields.

[00361] Example 72 includes the subject matter of Example 71, and optionally, wherein the apparatus is configured to cause the first wireless communication device to authenticate the WUR frame based on the FCS field.

[00362] Example 73 includes the subject matter of Example 71 or 72, and optionally, wherein the FCS field comprises cyclic redundancy check (CRC) information.

[00363] Example 74 includes the subject matter of any one of Examples 68-73, and optionally, wherein a length of the first identification information is equal to a length of the second identification information.

[00364] Example 75 includes the subject matter of any one of Examples 68-73, and optionally, wherein a length of the first identification information is different from a length of the second identification information. [00365] Example 76 includes the subject matter of any one of Examples 68-73, and optionally, wherein a length of the time value is equal to a length of the counter value.

[00366] Example 77 includes the subject matter of any one of Examples 68-73, and optionally, wherein a length of the time value is different from a length of the counter value.

[00367] Example 78 includes the subject matter of any one of Examples 68-77, and optionally, wherein a total length of the type field, the first type-dependent field and the second type-dependent field is fixed.

[00368] Example 79 includes the subject matter of any one of Examples 68-78, and optionally, wherein a total length of the first and second type-dependent fields when the WUR frame comprises the WUR beacon is equal to a total length of the first and second type-dependent fields when the WUR frame comprises the wake-up packet.

[00369] Example 80 includes the subject matter of any one of Examples 68-79, and optionally, wherein the first identification information comprises a Transmitter Identifier (TXID).

[00370] Example 81 includes the subject matter of Example 80, and optionally, wherein the apparatus is configured to cause the first wireless communication device to process a WUR action frame configured for WUR negotiation from the first wireless communication device, the WUR action frame comprising the TXID. [00371] Example 82 includes the subject matter of any one of Examples 68-81, and optionally, wherein the apparatus is configured to cause the WURx to receive the wake-up packet when a radio of the first wireless communication device is not active, and to wakeup the radio of the first wireless communication device based on the wake-up packet. [00372] Example 83 includes the subject matter of any one of Examples 68-82, and optionally, comprising the WURx.

[00373] Example 84 includes the subject matter of any one of Examples 68-83, and optionally, comprising a radio, a processor, a memory, and one or more antennas.

[00374] Example 85 includes a system of wireless communication comprising a first wireless communication device, the first wireless communication device comprising one or more antennas; a radio; a Wake-up Receiver (WURx); a memory; a processor; and a controller configured to cause the first wireless communication device to receive by the WURx of the first wireless communication device a Wake-up Radio (WUR) frame from a second wireless communication device, the WUR frame having a WUR frame format comprising a type field to indicate a type of the WUR frame, a first type-dependent field, and a second type-dependent field; when the type field is to indicate that the WUR frame is a WUR beacon, process the first type-dependent field as first identification information to identify a transmitter of the WUR beacon and the second type-dependent field as a time value; and when the type field is to indicate that the WUR frame is a wake-up packet, process the first type-dependent field as second identification information to identify a receiver of the wake-up packet and the second type-dependent field as a counter value.

[00375] Example 86 includes the subject matter of Example 85, and optionally, wherein the time value comprises a partial Timing Synchronization Function (TSF) value. [00376] Example 87 includes the subject matter of Example 85 or 86, and optionally, wherein the counter value comprises a packet number.

[00377] Example 88 includes the subject matter of any one of Examples 85-87, and optionally, wherein the WUR frame comprises a Frame Check Sequence (FCS) field after the first and second type-dependent fields. [00378] Example 89 includes the subject matter of Example 88, and optionally, wherein the controller is configured to cause the first wireless communication device to authenticate the WUR frame based on the FCS field.

[00379] Example 90 includes the subject matter of Example 88 or 89, and optionally, wherein the FCS field comprises cyclic redundancy check (CRC) information. [00380] Example 91 includes the subject matter of any one of Examples 85-90, and optionally, wherein a length of the first identification information is equal to a length of the second identification information.

[00381] Example 92 includes the subject matter of any one of Examples 85-90, and optionally, wherein a length of the first identification information is different from a length of the second identification information. [00382] Example 93 includes the subject matter of any one of Examples 85-90, and optionally, wherein a length of the time value is equal to a length of the counter value.

[00383] Example 94 includes the subject matter of any one of Examples 85-90, and optionally, wherein a length of the time value is different from a length of the counter value.

[00384] Example 95 includes the subject matter of any one of Examples 85-94, and optionally, wherein a total length of the type field, the first type-dependent field and the second type-dependent field is fixed.

[00385] Example 96 includes the subject matter of any one of Examples 85-95, and optionally, wherein a total length of the first and second type-dependent fields when the WUR frame comprises the WUR beacon is equal to a total length of the first and second type-dependent fields when the WUR frame comprises the wake-up packet.

[00386] Example 97 includes the subject matter of any one of Examples 85-96, and optionally, wherein the first identification information comprises a Transmitter Identifier (TXID).

[00387] Example 98 includes the subject matter of Example 97, and optionally, wherein the controller is configured to cause the first wireless communication device to process a WUR action frame configured for WUR negotiation from the first wireless communication device, the WUR action frame comprising the TXID. [00388] Example 99 includes the subject matter of any one of Examples 85-98, and optionally, wherein the controller is configured to cause the WURx to receive the wake-up packet when the radio is not active, and to wakeup the radio based on the wake-up packet.

[00389] Example 100 includes a method to be performed by a first wireless communication device, the method comprising receiving by a Wake-up Receiver (WURx) of the first wireless communication device a Wake-up Radio (WUR) frame from a second wireless communication device, the WUR frame having a WUR frame format comprising a type field to indicate a type of the WUR frame, a first type- dependent field, and a second type-dependent field; when the type field is to indicate that the WUR frame is a WUR beacon, processing the first type-dependent field as first identification information to identify a transmitter of the WUR beacon and the second type-dependent field as a time value; and when the type field is to indicate that the WUR frame is a wake-up packet, processing the first type-dependent field as second identification information to identify a receiver of the wake-up packet and the second type-dependent field as a counter value.

[00390] Example 101 includes the subject matter of Example 100, and optionally, wherein the time value comprises a partial Timing Synchronization Function (TSF) value.

[00391] Example 102 includes the subject matter of Example 100 or 101, and optionally, wherein the counter value comprises a packet number.

[00392] Example 103 includes the subject matter of any one of Examples 100-102, and optionally, wherein the WUR frame comprises a Frame Check Sequence (FCS) field after the first and second type-dependent fields.

[00393] Example 104 includes the subject matter of Example 103, and optionally, comprising authenticating the WUR frame based on the FCS field.

[00394] Example 105 includes the subject matter of Example 103 or 104, and optionally, wherein the FCS field comprises cyclic redundancy check (CRC) information.

[00395] Example 106 includes the subject matter of any one of Examples 100-105, and optionally, wherein a length of the first identification information is equal to a length of the second identification information. [00396] Example 107 includes the subject matter of any one of Examples 100-105, and optionally, wherein a length of the first identification information is different from a length of the second identification information.

[00397] Example 108 includes the subject matter of any one of Examples 100-105, and optionally, wherein a length of the time value is equal to a length of the counter value.

[00398] Example 109 includes the subject matter of any one of Examples 100-105, and optionally, wherein a length of the time value is different from a length of the counter value.

[00399] Example 110 includes the subject matter of any one of Examples 100-109, and optionally, wherein a total length of the type field, the first type-dependent field and the second type-dependent field is fixed. [00400] Example 111 includes the subject matter of any one of Examples 100-110, and optionally, wherein a total length of the first and second type-dependent fields when the WUR frame comprises the WUR beacon is equal to a total length of the first and second type-dependent fields when the WUR frame comprises the wake-up packet.

[00401] Example 112 includes the subject matter of any one of Examples 100-111, and optionally, wherein the first identification information comprises a Transmitter Identifier (TXID).

[00402] Example 113 includes the subject matter of Example 112, and optionally, comprising processing a WUR action frame configured for WUR negotiation from the first wireless communication device, the WUR action frame comprising the TXID.

[00403] Example 114 includes the subject matter of any one of Examples 100-113, and optionally, comprising receiving the wake-up packet at the WURx, when a radio of the first wireless communication device is not active, and waking up the radio of the first wireless communication device based on the wake-up packet.

[00404] Example 115 includes a product comprising one or more tangible computer- readable non-transitory storage media comprising computer-executable instructions operable to, when executed by at least one processor, enable the at least one processor to cause a first wireless communication device to receive by a Wake-up Receiver (WURx) of the first wireless communication device a Wake-up Radio (WUR) frame from a second wireless communication device, the WUR frame having a WUR frame format comprising a type field to indicate a type of the WUR frame, a first type- dependent field, and a second type-dependent field; when the type field is to indicate that the WUR frame is a WUR beacon, process the first type-dependent field as first identification information to identify a transmitter of the WUR beacon and the second type-dependent field as a time value; and when the type field is to indicate that the WUR frame is a wake-up packet, process the first type-dependent field as second identification information to identify a receiver of the wake-up packet and the second type-dependent field as a counter value. [00405] Example 116 includes the subject matter of Example 115, and optionally, wherein the time value comprises a partial Timing Synchronization Function (TSF) value. [00406] Example 117 includes the subject matter of Example 115 or 116, and optionally, wherein the counter value comprises a packet number.

[00407] Example 118 includes the subject matter of any one of Examples 115-117, and optionally, wherein the WUR frame comprises a Frame Check Sequence (FCS) field after the first and second type-dependent fields.

[00408] Example 119 includes the subject matter of Example 118, and optionally, wherein the instructions, when executed, cause the first wireless communication device to authenticate the WUR frame based on the FCS field.

[00409] Example 120 includes the subject matter of Example 118 or 119, and optionally, wherein the FCS field comprises cyclic redundancy check (CRC) information.

[00410] Example 121 includes the subject matter of any one of Examples 115-120, and optionally, wherein a length of the first identification information is equal to a length of the second identification information. [00411] Example 122 includes the subject matter of any one of Examples 115-120, and optionally, wherein a length of the first identification information is different from a length of the second identification information.

[00412] Example 123 includes the subject matter of any one of Examples 115-120, and optionally, wherein a length of the time value is equal to a length of the counter value.

[00413] Example 124 includes the subject matter of any one of Examples 115-120, and optionally, wherein a length of the time value is different from a length of the counter value.

[00414] Example 125 includes the subject matter of any one of Examples 115-124, and optionally, wherein a total length of the type field, the first type-dependent field and the second type-dependent field is fixed.

[00415] Example 126 includes the subject matter of any one of Examples 115-125, and optionally, wherein a total length of the first and second type-dependent fields when the WUR frame comprises the WUR beacon is equal to a total length of the first and second type-dependent fields when the WUR frame comprises the wake-up packet. [00416] Example 127 includes the subject matter of any one of Examples 115-126, and optionally, wherein the first identification information comprises a Transmitter Identifier (TXID).

[00417] Example 128 includes the subject matter of Example 127, and optionally, wherein the instructions, when executed, cause the first wireless communication device to process a WUR action frame configured for WUR negotiation from the first wireless communication device, the WUR action frame comprising the TXID.

[00418] Example 129 includes the subject matter of any one of Examples 115-128, and optionally, wherein the instructions, when executed, cause the WURx to receive the wake-up packet when a radio of the first wireless communication device is not active, and to wakeup the radio of the first wireless communication device based on the wake-up packet.

[00419] Example 130 includes an apparatus of wireless communication by a first wireless communication device, the apparatus comprising means for receiving by a Wake-up Receiver (WURx) of the first wireless communication device a Wake-up Radio (WUR) frame from a second wireless communication device, the WUR frame having a WUR frame format comprising a type field to indicate a type of the WUR frame, a first type-dependent field, and a second type-dependent field; means for, when the type field is to indicate that the WUR frame is a WUR beacon, processing the first type-dependent field as first identification information to identify a transmitter of the WUR beacon and the second type-dependent field as a time value; and means for, when the type field is to indicate that the WUR frame is a wake-up packet, processing the first type-dependent field as second identification information to identify a receiver of the wake-up packet and the second type-dependent field as a counter value.

[00420] Example 131 includes the subject matter of Example 130, and optionally, wherein the time value comprises a partial Timing Synchronization Function (TSF) value.

[00421] Example 132 includes the subject matter of Example 130 or 131, and optionally, wherein the counter value comprises a packet number. [00422] Example 133 includes the subject matter of any one of Examples 130-132, and optionally, wherein the WUR frame comprises a Frame Check Sequence (FCS) field after the first and second type-dependent fields.

[00423] Example 134 includes the subject matter of Example 133, and optionally, comprising means for authenticating the WUR frame based on the FCS field.

[00424] Example 135 includes the subject matter of Example 133 or 134, and optionally, wherein the FCS field comprises cyclic redundancy check (CRC) information.

[00425] Example 136 includes the subject matter of any one of Examples 130-135, and optionally, wherein a length of the first identification information is equal to a length of the second identification information.

[00426] Example 137 includes the subject matter of any one of Examples 130-135, and optionally, wherein a length of the first identification information is different from a length of the second identification information. [00427] Example 138 includes the subject matter of any one of Examples 130-135, and optionally, wherein a length of the time value is equal to a length of the counter value.

[00428] Example 139 includes the subject matter of any one of Examples 130-135, and optionally, wherein a length of the time value is different from a length of the counter value.

[00429] Example 140 includes the subject matter of any one of Examples 130-139, and optionally, wherein a total length of the type field, the first type-dependent field and the second type-dependent field is fixed.

[00430] Example 141 includes the subject matter of any one of Examples 130-140, and optionally, wherein a total length of the first and second type-dependent fields when the WUR frame comprises the WUR beacon is equal to a total length of the first and second type-dependent fields when the WUR frame comprises the wake-up packet.

[00431] Example 142 includes the subject matter of any one of Examples 130-141, and optionally, wherein the first identification information comprises a Transmitter Identifier (TXID). [00432] Example 143 includes the subject matter of Example 142, and optionally, comprising means for processing a WUR action frame configured for WUR negotiation from the first wireless communication device, the WUR action frame comprising the TXID. [00433] Example 144 includes the subject matter of any one of Examples 130-143, and optionally, comprising means for receiving the wake-up packet at the WURx, when a radio of the first wireless communication device is not active, and waking up the radio of the first wireless communication device based on the wake-up packet.

[00434] Functions, operations, components and/or features described herein with reference to one or more embodiments, may be combined with, or may be utilized in combination with, one or more other functions, operations, components and/or features described herein with reference to one or more other embodiments, or vice versa.

[00435] While certain features have been illustrated and described herein, many modifications, substitutions, changes, and equivalents may occur to those skilled in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the disclosure.

Claims

CLAIMS What is claimed is:

1. An apparatus comprising logic and circuitry configured to cause a wireless communication device to:

generate a Wake-up Radio (WUR) frame having a WUR frame format comprising a type field, a first type-dependent field, and a second type-dependent field, the type field to indicate a type of the WUR frame, wherein, when the type field is to indicate that the WUR frame is a WUR beacon, the first type-dependent field comprises first identification information to identify a transmitter of the WUR beacon and the second type-dependent field comprises a time value, and, when the type field is to indicate that the WUR frame is a wake-up packet, the first type-dependent field comprises second identification information to identify a receiver of the wake-up packet and the second type-dependent field comprises a counter value; and

transmit the WUR frame.

2. The apparatus of claim 1, wherein the time value comprises a partial Timing

Synchronization Function (TSF) value.

3. The apparatus of claim 1, wherein the counter value comprises a packet number.

4. The apparatus of claim 1, wherein the WUR frame comprises a Frame Check Sequence (FCS) field after the first and second type-dependent fields.

5. The apparatus of claim 4, wherein the FCS field comprises cyclic redundancy check (CRC) information.

6. The apparatus of claim 1, wherein a length of the first identification information is equal to a length of the second identification information.

7. The apparatus of claim 1, wherein a length of the first identification information is different from a length of the second identification information.

8. The apparatus of claim 1, wherein a length of the time value is equal to a length of the counter value.

9. The apparatus of claim 1, wherein a length of the time value is different from a length of the counter value.

10. The apparatus of any one of claims 1-9, wherein a total length of the type field, the first type-dependent field and the second type-dependent field is fixed.

11. The apparatus of any one of claims 1-9, wherein a total length of the first and second type-dependent fields when the WUR frame comprises the WUR beacon is equal to a total length of the first and second type-dependent fields when the WUR frame comprises the wake-up packet.

12. The apparatus of any one of claims 1-9, wherein the first identification information comprises a Transmitter Identifier (TXID).

13. The apparatus of claim 12 configured to cause the wireless communication device to transmit a WUR action frame configured for WUR negotiation, the WUR action frame comprising the TXID.

14. The apparatus of any one of claims 1-9 comprising a processor, a memory, and one or more antennas.

15. A method to be performed by a wireless communication device, the method comprising:

generating a Wake-up Radio (WUR) frame having a WUR frame format comprising a type field, a first type-dependent field, and a second type-dependent field, the type field to indicate a type of the WUR frame, wherein, when the type field is to indicate that the WUR frame is a WUR beacon, the first type-dependent field comprises first identification information to identify a transmitter of the WUR beacon and the second type-dependent field comprises a time value, and, when the type field is to indicate that the WUR frame is a wake-up packet, the first type-dependent field comprises second identification information to identify a receiver of the wake-up packet and the second type-dependent field comprises a counter value; and

transmitting the WUR frame.

16. The method of claim 15, wherein a total length of the type field, the first type-dependent field and the second type-dependent field is fixed.

17. A product comprising one or more tangible computer-readable non-transitory storage media comprising computer-executable instructions operable to, when executed by at least one processor, enable the at least one processor to cause a wireless communication device to perform the method of claim 15 or 16.

18. An apparatus comprising logic and circuitry configured to cause a first wireless communication device to:

receive by a Wake-up Receiver (WURx) of the first wireless communication device a Wake-up Radio (WUR) frame from a second wireless communication device, the WUR frame having a WUR frame format comprising a type field to indicate a type of the WUR frame, a first type-dependent field, and a second type- dependent field;

when the type field is to indicate that the WUR frame is a WUR beacon, process the first type-dependent field as first identification information to identify a transmitter of the WUR beacon and the second type-dependent field as a time value; and

when the type field is to indicate that the WUR frame is a wake-up packet, process the first type-dependent field as second identification information to identify a receiver of the wake-up packet and the second type-dependent field as a counter value.

19. The apparatus of claim 18, wherein the time value comprises a partial Timing Synchronization Function (TSF) value.

20. The apparatus of claim 18, wherein the WUR frame comprises a Frame Check Sequence (FCS) field after the first and second type-dependent fields.

21. The apparatus of any one of claims 18-20, wherein a total length of the type field, the first type-dependent field and the second type-dependent field is fixed.

22. The apparatus of any one of claims 18-20 configured to cause the WURx to receive the wake-up packet when a radio of the first wireless communication device is not active, and to wakeup the radio of the first wireless communication device based on the wake-up packet.

23. The apparatus of any one of claims 18-20 comprising a radio, a processor, a memory, and one or more antennas.

24. A product comprising one or more tangible computer-readable non-transitory storage media comprising computer-executable instructions operable to, when executed by at least one processor, enable the at least one processor to cause a first wireless communication device to:

25. The product of claim 24, wherein the instructions, when executed, cause the WURx to receive the wake-up packet when a radio of the first wireless communication device is not active, and to wakeup the radio of the first wireless communication device based on the wake-up packet.