CN110832912B - Closed loop transmission associated with wake-up radio - Google Patents

Abstract

Methods, systems, and devices are disclosed for operating a wireless transmit/receive unit (WTRU) in a wake-up radio (WUR) state and receiving (WUR) frames from an Access Point (AP). WUR frames may include a Multicast Counter (MC) field. It may be determined whether the received MC value in the received MC field is the same value as the stored MC value. The WTRU may operate in WUR state where the received MC value is the same value as the stored MC value. In the case where the received MC value is a different value than the stored MC value, the WTRU may operate in a Primary Connection Radio (PCR) state.

Description

Closed loop transmission associated with wake-up radio

Cross Reference to Related Applications

The present application claims priority from U.S. provisional patent application serial No. 62/501,892 filed on month 05 of 2017 and U.S. provisional patent application serial No. 62/595,750 filed on month 7 of 12 of 2017, each entitled "closed loop transmission related to wake-up radio", and each of which is incorporated herein by reference in its entirety.

Background

In a wake-up radio (WUR) scenario, for example, where power savings at a non-access point (non-AP) device (e.g., a non-AP station (non-AP STA)) may be a goal, there may be a number of Downlink (DL) transmissions from one or more APs that may be directed to one or more non-AP STAs. The number of Uplink (UL) transmissions from one or more non-AP STAs to one or more APs may be small (e.g., the number is less than the aforementioned number of DL transmissions). One or more closed loop transmission schemes may be used in the WUR case, such as beamforming, antenna selection, rate selection, modulation and Coding Scheme (MCS) selection, WUR narrowband channel selection, etc.

Disclosure of Invention

Methods, systems, and devices are disclosed for operating a wireless transmit/receive unit (WTRU) in a wake-up radio (WUR) state and receiving (WUR) frames from an Access Point (AP). WUR frames may include a Multicast Counter (MC) field. It may be determined whether the received MC value in the received MC field is the same value as the stored MC value. In the case where the received MC value is the same value as the stored MC value, the WTRU may operate in WUR state. In the event that the received MC value is a different value than the stored MC value, the WTRU may operate in a Primary Connection Radio (PCR) state. The WTRU may operate according to a duty cycle (duty cycle) having an "off period and an" on "period. The duty cycle of the WTRU may be synchronized with one or more other duty cycles associated with one or more other WTRUs. The WTRU may start the PCR timer when the received MC value is a different value than the MC value stored in the WTRU. The WTRU may determine that the PCR timer value has met one or more thresholds and may responsively enter a WUR state, enter a PCR state, and/or invalidate the stored MC value.

Drawings

Fig. 1A shows a system diagram of an exemplary communication system.

Fig. 1B is a system diagram of an example wireless transmit/receive unit (WTRU) that may be used within the communication system shown in fig. 1A.

Fig. 1C is a system diagram of an example Radio Access Network (RAN) and an example Core Network (CN) that may be used within the communication system shown in fig. 1A.

Fig. 1D is a system diagram of another example RAN and another example CN that may be used within the communication system shown in fig. 1A.

Fig. 1E illustrates an exemplary Wireless Local Area Network (WLAN) device.

Fig. 2A illustrates an exemplary frame exchange and wake-up receiver (WUR) negotiation.

Fig. 2B illustrates an exemplary WUR frame format.

Fig. 3 illustrates an exemplary frame exchange including multicast transmissions over WUR channels.

FIG. 4 illustrates an exemplary system in which one or more delta factors may be utilized.

Fig. 5 illustrates an exemplary beamforming transmission procedure.

Fig. 6 illustrates another exemplary beamforming transmission procedure.

Fig. 7 illustrates another exemplary beamforming transmission procedure.

Fig. 8 illustrates an exemplary channel selection process.

Fig. 9 illustrates another exemplary channel selection process.

Fig. 10 illustrates another exemplary channel selection process.

Fig. 11 illustrates an exemplary rate selection process.

Fig. 12 illustrates another exemplary rate selection process.

Fig. 13 illustrates another exemplary rate selection process.

Fig. 14 illustrates an exemplary wake-up process.

Fig. 15 shows a block diagram representing an exemplary method.

Fig. 16 illustrates an exemplary wake-up process.

Fig. 17 shows a block diagram representing an exemplary method.

Fig. 18 shows a block diagram representing another exemplary method.

Fig. 19 shows a block diagram representing another exemplary method.

Fig. 20 shows a block diagram representing another exemplary method.

Detailed Description

Fig. 1A is a diagram illustrating an exemplary communication system 100. Communication system 100 may be a multiple-access system that provides content, such as voice, data, video, messages, broadcasts, etc., to a plurality of wireless users. Communication system 100 may enable multiple wireless users to access such content by sharing system resources including wireless bandwidth. For example, communication system 100 may employ one or more channel access methods, which may include any one or more and/or any combination of Code Division Multiple Access (CDMA), time Division Multiple Access (TDMA), frequency Division Multiple Access (FDMA), orthogonal FDMA (OFDMA), single carrier FDMA (SC-FDMA), zero tail unique word DFT-spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, filter Bank Multicarrier (FBMC), and any other type of channel access method.

As shown in fig. 1A, the communication system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, a RAN 104, a CN 106, a Public Switched Telephone Network (PSTN) 108, the internet 110, and other networks 112. It should be appreciated that the disclosed examples contemplate any number of WTRUs, base stations, networks, and/or network elements. Each WTRU 102a, 102b, 102c, 102d may be any one or more and/or any combination of the following: a device configured to operate and/or communicate in a wireless environment. Any of the WTRUs 102a, 102b, 102c, 102d may be referred to as a "station" and/or a "STA," which may be configured to transmit and/or receive wireless signals, and may include any one or more and/or any combination of the following: user Equipment (UE), mobile station, fixed or mobile subscriber unit, subscription-based unit, pager, cellular telephone, personal Digital Assistant (PDA), smart phone, laptop computer, netbook, personal computer, wireless sensor, hotspot, mi-Fi device, internet of things (IoT) device, watch, any type of wearable device, head Mounted Display (HMD), vehicle, drone, medical device, medical application (e.g., tele-surgery), industrial device, industrial application (e.g., robot and/or other wireless device operating in an industrial and/or automated processing chain loop environment), consumer electronics device, device operating on a commercial and/or industrial wireless network, and any other type of device configured to transmit and/or receive wireless signals. Any WTRU 102a, 102b, 102c, 102d may be interchangeably referred to as a UE.

Communication system 100 may also include base station 114a and/or base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks (e.g., the CN106, the internet 110, and/or the other network 112). Each of the base stations 114a, 114B may be any one or more of a Base Transceiver Station (BTS), a node B, e node B, a home enodeb, a next generation node B (gNB), a NR node B, a site controller, an Access Point (AP), a wireless router, and any other type of device that may perform one or more functions of a base station, and/or any combination thereof. Although the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and/or network elements.

Base station 114a may be part of RAN 104 that may also include other base stations and/or network elements (which may not be shown), such as Base Station Controllers (BSCs), radio Network Controllers (RNCs), relay nodes, and the like. Base station 114a and/or base station 114b may be configured to transmit and/or receive wireless signals on one or more carrier frequencies, which may be referred to as cells. Such frequencies may be in a licensed spectrum, an unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage of a wireless service to a particular geographic area, which may be relatively fixed or may change over time. The cell may be further divided into cell sectors. For example, a cell associated with base station 114a may be divided into three sectors. Base station 114a may include three transceivers, e.g., one for each sector of a cell. Base station 114a may employ multiple-input multiple-output (MIMO) technology and/or may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and/or receive signals in desired spatial directions.

The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d via an air interface 116, which may be any suitable wireless communication link (e.g., radio Frequency (RF), microwave, centimeter wave, millimeter wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable Radio Access Technology (RAT).

Communication system 100 may be a multiple access system and may employ any one or more and/or any combination of channel access schemes such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA and any other type of channel access scheme. For example, the base station 114a and WTRUs 102a, 102b, 102c in the RAN 104 may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) terrestrial radio access (UTRA), which may use Wideband CDMA (WCDMA) to establish the air interface 116.WCDMA may include communication protocols such as High Speed Packet Access (HSPA) and/or evolved HSPA (hspa+). HSPA may include high speed Downlink (DL) packet access (HSDPA) and/or high speed Uplink (UL) packet access (HSUPA).

The base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology, such as evolved UMTS terrestrial radio access (E-UTRA), which may use Long Term Evolution (LTE) and/or LTE-advanced (LTE-a) and/or LTE-advanced Pro (LTE-a Pro) to establish the air interface 116.

The base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR radio access that may use a New Radio (NR) to establish the air interface 116.

The base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, e.g., using a Dual Connectivity (DC) principle. Thus, the air interface used by the WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and/or transmissions sent to/from multiple types of base stations (e.g., enbs and gnbs).

The base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as any one or more and/or any combination of IEEE802.11 (e.g., wireless fidelity (WiFi), IEEE 802.16 (e.g., worldwide Interoperability for Microwave Access (WiMAX)), CDMA 2000 1x, CDMA 2000EV-DO, temporary standard 2000 (IS-2000), temporary standard 95 (IS-95), temporary standard 856 (IS-856), global system for mobile communication (GSM), enhanced data rates for GSM evolution (EDGE), GSM EDGE (GERAN), and any other type of radio technology.

The base station 114B in fig. 1A may be any one or more of a wireless router, a home node B, an access point, and any other type of device that may perform one or more base station functions, and/or any combination thereof. The base station 114b may utilize any suitable RAT to facilitate wireless connectivity in local areas, including any one or more of and/or any combination of business sites, homes, vehicles, campuses, industrial facilities, air corridors (e.g., for use by drones), roads, and any other type of RAT. The base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a Wireless Local Area Network (WLAN). The base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a Wireless Personal Area Network (WPAN). The base station 114b and the WTRUs 102c, 102d may also or alternatively utilize cellular-based RATs (e.g., WCDMA, CDMA2000, GSM, LTE-a Pro, NR, etc.) to establish pico or femto cells. As shown in fig. 1A, the base station 114b may have a direct connection to the internet 110. Thus, the base station 114b may not need to access the internet 110 via the CN 106.

The RAN 104 may communicate with the CN 106, which may be any type of network configured to provide voice, data, application, and/or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102 d. Such data may have varying quality of service (QoS) requirements, including any one or more and/or any combination of different throughput requirements, latency requirements, fault tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and any other type of QoS requirements. The CN 106 may provide call control, billing services, mobile location based services, prepaid calls, internet connections, video distribution, etc., and/or may perform advanced security functions such as user authentication. The RAN 104 and/or the CN 106 may communicate directly or indirectly with other RANs that employ the same RAT as the RAN 104 or a different RAT. For example, in addition to being connected to RAN 104, which may utilize NR radio technology, CN 106 may also communicate with another RAN employing GSM, UMTS, CDMA, wiMAX, E-UTRA, and/or other WiFi radio technology.

The CN 106 may also act as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the internet 110, and/or other networks 112.PSTN 108 may include circuit-switched telephone networks that may provide Plain Old Telephone Services (POTS). The internet 110 may include a global system of interconnected computer networks and devices that may use common communication protocols, such as transmission control protocol/internet protocol (TCP/IP) in the TCP, user Datagram Protocol (UDP), and/or IP of the internet protocol family. Other networks 112 may include wired and/or wireless communication networks owned and/or operated by other service providers. For example, the other network 112 may include another CN connected to one or more RANs, which may use the same RAT as the RAN 104 or a different RAT.

Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links). For example, the WTRU 102c shown in fig. 1A may be configured to communicate with a base station 114a, which may employ a cellular-based radio technology, and/or with a base station 114b, which may employ an IEEE 802 radio technology.

Fig. 1B is a system diagram illustrating an example WTRU 102. WTRU 102 may include a processor 118, a transceiver 120, a transmit/receive element 122, a speaker/microphone 124, a keypad 126, a display/touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a Global Positioning System (GPS) chipset 136, and/or other peripherals 138, etc. It should be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with the present disclosure.

The processor 118 may be any one or more and/or any combination of a general purpose processor, a special purpose processor, a conventional processor, a Digital Signal Processor (DSP), a microprocessor associated with a DSP core, a controller, a microcontroller, an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) circuit, any other type of Integrated Circuit (IC), a state machine, and any other type of processor. The processor 118 may perform signal coding, data processing, power control, input/output processing, and/or any other function that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to a transceiver 120, which may be coupled to a transmit/receive element 122. The processor 118 and the transceiver 120 may be separate components or may be integrated together in an electronic package or chip.

The transmit/receive element 122 may be configured to transmit signals to and/or receive signals from a base station (e.g., base station 114 a) over the air interface 116. The transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals. The transmit/receive element 122 may be an emitter/detector configured to emit and/or receive, for example, IR, UV, and/or visible light signals. The transmit/receive element 122 may also or alternatively be configured to transmit and/or receive both RF and optical signals. The transmit/receive element 122 may be configured to transmit and/or receive any combination of wireless signals.

The transmit/receive element 122 may be a single element or any number and/or combination of transmit/receive elements 122. For example, the WTRU 102 may use MIMO technology. The WTRU 102 may include two or more transmit/receive elements 122 (e.g., multiple antennas) for transmitting and/or receiving wireless signals over the air interface 116.

Transceiver 120 may be configured to modulate signals that may be transmitted by transmit/receive element 122 and/or demodulate signals that may be received by transmit/receive element 122. The WTRU 102 may have multimode capabilities. The transceiver 120 may include multiple transceivers that may enable the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11.

The processor 118 of the WTRU102 may be connected to and may receive user input data from a speaker/microphone 124, a keypad 126, and/or a display/touchpad 128, such as a Liquid Crystal Display (LCD) display unit or an Organic Light Emitting Diode (OLED) display unit. The processor 118 may also output user data to the speaker/microphone 124, the keyboard 126, and/or the display/touchpad 128. The processor 118 may access information from and/or store data in any type of suitable memory, such as non-removable memory 130 and/or removable memory 132. The non-removable memory 130 may include Random Access Memory (RAM), read Only Memory (ROM), a hard disk, and/or any other type of memory storage device. Removable memory 132 may include any one or more of and/or any combination of a Subscriber Identity Module (SIM) card, a memory stick, a Secure Digital (SD) memory card, and any other type of removable memory. The processor 118 may access information from, and/or store data in, a memory that is not physically located on the WTRU102, such as on a server and/or home computer.

The processor 118 may receive power from the power source 134 and may be configured to distribute and/or control power for other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include any one or more and/or any combination of a dry cell (e.g., nickel cadmium (NiCd), nickel zinc (NiZn), nickel metal hydride (NiMH), lithium ion (Li-ion), etc.), a solar cell, a fuel cell, and any other type of device suitable for powering the WTRU 102.

The processor 118 may be coupled to a GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to or in lieu of information from the GPS chipset 136, the WTRU 102 may receive location information from base stations (e.g., base stations 114a, 114 b) over the air interface 116 and/or determine its location based on the timing of signals received from two or more neighboring base stations. It should be appreciated that the WTRU 102 may acquire location information by any suitable location determination method while remaining consistent with the present disclosure.

The processor 118 may be coupled to other peripheral devices 138, which may include one or more software and/or hardware modules that may provide additional features, functionality, and/or wired and/or wireless connections. The peripheral devices 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (e.g., for photos and/or videos), universal Serial Bus (USB) port, vibration device, television transceiver, hands-free headset, portable electronic device, and electronic device,

One or more and/or any combination of modules, frequency Modulation (FM) radio units, digital music players, media players, video game modules, internet browsers, virtual reality and/or augmented reality (VR/AR) devices, activity trackers, and any other type of peripheral device. The peripheral device 138 may include one or more sensors. Such sensors may include any one or more and/or any combination of gyroscopes, accelerometers, hall effect sensors, magnetometers, orientation sensors, proximity sensors, temperature sensors, time sensors, geolocation sensors, altimeters, light sensors, touch sensors, magnetometers, barometers, gesture sensors, biometric sensors, humidity sensors, and any other type of sensor.

WTRU102 may include a full duplex radio that transmits or receives some or all signals, such as associated with a particular subframe for one or both of Uplink (UL) (e.g., for transmission) or Downlink (DL) (e.g., for reception). Such transmission and/or reception may be concurrent and/or simultaneous. The full duplex radio may include an interference management unit that may reduce and/or substantially eliminate self-interference via either or both of hardware (e.g., choke) and/or signal processing via a processor (e.g., a separate processor and/or processor 118). WTRU102 may include a half-duplex radio that transmits or receives some or all signals, such as associated with a particular subframe for one or both of UL (e.g., for transmission) or downlink (e.g., for reception).

Fig. 1C is a system diagram illustrating an exemplary RAN 104 and CN 106. RAN 104 may employ an E-UTRA radio technology to communicate with WTRUs 102a, 102b, 102c via an air interface 116. RAN 104 may also communicate with CN 106.

RAN 104 may include enode bs 160a, 160B, 160c, although it should be appreciated that RAN 104 may include any number of enode bs while remaining consistent with the invention. each of the enode bs 160a, 160B, 160c may include one or more transceivers for communicating with the WTRUs 102a, 102B, 102c over the air interface 116. The enode bs 160a, 160B, 160c may implement MIMO technology. For example, the enode B160a may use multiple antennas to transmit wireless signals to and/or receive wireless signals from the WTRU102 a.

each of the enodebs 160a, 160B, 160c may be associated with a particular cell and/or may be configured to process any one or more and/or any combination of radio resource management decisions, handover decisions, user scheduling in UL and/or DL, and any other type of enode B functionality. The enode bs 160a, 160B, 160c may communicate with each other via an X2 interface.

The CN 106 may include a Mobility Management Entity (MME) 162, a Serving Gateway (SGW) 164, and/or a Packet Data Network (PDN) gateway (PGW) 166. Any or all of such elements may be owned and/or operated by an entity other than the operator of the CN 106.

MME162 may be connected to each of enode bs 160a, 160B, 160c in RAN 104 via an S1 interface and may act as a control node. For example, the MME162 may be responsible for any one or more and/or any combination of functions including authenticating the user of the WTRUs 102a, 102b, 102c, bearer activation/deactivation, selecting a particular serving gateway during initial attachment of the WTRUs 102a, 102b, 102c, and any other type of MME function. MME162 may provide control plane functionality for switching between RAN 104 and other RANs that may employ other radio technologies (e.g., GSM and/or WCDMA).

SGW 164 may be connected to each of the enode bs 160a, 160B, 160c in RAN 104 via an S1 interface. The SGW 164 may route and/or forward user data packets to/from the WTRUs 102a, 102b, 102 c. The SGW 164 may perform other functions including anchoring user planes during inter-enodeb handovers, triggering paging when DL data is available to the WTRUs 102a, 102B, 102c, managing and/or storing the contexts of the WTRUs 102a, 102B, 102c, and any other type of gateway function, any one or more, and/or any combination.

The SGW 164 may be connected to a PGW 166 that may provide the WTRUs 102a, 102b, 102c with access to a packet switched network, such as the internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP enabled devices.

The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to a circuit switched network, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and legacy landline communication devices. The CN 106 may include or may communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server), which may serve as an interface between the CN 106 and the PSTN 108. The CN 106 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and/or wireless networks owned and/or operated by other service providers.

While one or more WTRUs may be described in this disclosure as wireless terminals, it is contemplated that any such WTRU may use (e.g., temporarily or permanently) a wired communication interface with a communication network. Note also that one or more of the disclosed networks, such as network 112, may be a WLAN.

A WLAN in infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) for the BSS and one or more Stations (STAs) associated with the AP. The AP may have access and/or interfaces to a Distributed System (DS) and/or another type of wired/wireless network that may carry traffic into and/or out of the BSS. Traffic originating from outside the BSS to the STA may arrive through the AP and may be delivered to the STA. Traffic originating from the STA to a destination outside the BSS may be sent to the AP to be delivered to the corresponding destination. Traffic between STAs within a BSS may be transmitted by the AP, for example, where a source STA may transmit traffic to the AP and the AP may deliver the traffic to a destination STA. Traffic between STAs within a BSS may be considered and/or referred to as peer-to-peer traffic. Peer-to-peer traffic may be transmitted between (e.g., directly between) a source STA and a destination STA using Direct Link Setup (DLS). The DLS may use 802.11e DLS or 802.11z Tunnel DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP and one or more STAs (e.g., all STAs) within or using the IBSS may communicate directly with each other. The IBSS communication mode may be referred to as an "ad-hoc" communication mode.

When using the 802.11ac infrastructure mode of operation or similar modes of operation, the AP may transmit a beacon, such as a primary channel, on a fixed channel. The primary channel may be a fixed width (e.g., 20MHz wide bandwidth) or a dynamically set width that may be set via signaling. The primary channel may be an operating channel of the BSS and may be used by the STA to establish a connection with the AP. For example, in an 802.11 system, carrier sense multiple access with collision avoidance (CSMA/CA) may be implemented. For CSMA/CA, STAs (e.g., each STA) that include an AP may sense the primary channel. A particular STA may fall back if the primary channel is sensed/detected and/or determined to be busy by the particular STA. One STA (e.g., only one station) may transmit at any given time in a given BSS.

High Throughput (HT) STAs may communicate using channels having a width of 40MHz, for example, by combining a 20MHz primary channel with 20MHz adjacent or non-adjacent channels to form a channel having a width of 40 MHz.

Very High Throughput (VHT) STAs may support channels of 20MHz, 40MHz, 80MHz and/or 160MHz in width. 40MHz, 80MHz and/or 160MHz channels may be formed by combining consecutive 20MHz channels. The 160MHz channel may be formed by combining eight (8) consecutive 20MHz channels or by combining two (2) non-consecutive 80MHz channels (this combination may be referred to as an 80+80 configuration). For the 80+80 configuration, after channel coding, the data may be passed through a segment parser that may not divide the data into two streams. An Inverse Fast Fourier Transform (IFFT) process and a time domain process may be performed on each stream separately. The streams may be mapped on two 80MHz channels and data may be transmitted by the transmitting STA using the two 80MHz channels. At the receiver performing the receiving STA, the above-described operations for the 80+80 configuration may be reversed and the combined data may be sent to a Medium Access Control (MAC).

The 802.11af and 802.11ah support secondary 1GHz modes of operation. The channel operating bandwidth and carrier used in 802.11af and 802.11ah is reduced compared to 802.11n and 802.11 ac. The 802.11af supports 5MHz, 10MHz, and 20MHz bandwidths in the TV white space (TVWS) spectrum. 802.11ah supports 1MHz, 2MHz, 4MHz, 8MHz, and 16MHz bandwidths using non-TVWS spectrum. According to an exemplary embodiment, 802.11ah may support meter type control/machine type communication (each may be referred to as "MTC"), such as MTC devices in a macro coverage area. MTC devices may have some capability, e.g. limited capabilities including supporting (e.g. supporting only) some and/or limited bandwidth. MTC devices may include a battery, and the battery life of the battery is above a threshold (e.g., to maintain a long battery life).

For WLAN systems (e.g., 802.11n, 802.11ac, 802.11af, and 802.11 ah) that can support multiple channels and channel bandwidths, these systems include channels that can be designated as primary channels. The bandwidth of the primary channel may be equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and/or limited by a STA that originates from all STAs operating in the corresponding BSS. The bandwidth of such a primary channel supports a minimum bandwidth mode of operation. In implementations regarding 802.11ah, the width of the primary channel may be 1MHz for STAs (e.g., MTC-type devices) that support (e.g., support only) 1MHz modes, even though the AP and other STAs in the respective BSS support one or more of 2MHz, 4MHz, 8MHz, 16MHz, and/or other channel bandwidth modes of operation. Carrier sensing and/or Network Allocation Vector (NAV) settings may depend on the state of the primary channel. If the primary channel is busy (e.g., because the STA (which only supports 1MHz mode of operation) transmits to the AP), the entire available frequency band may be considered busy even though most of the frequency band remains idle and available for use.

The available frequency band for 802.11ah in the united states is 902MHz to 928MHz. In korea, the available frequency band is 917.5MHz to 923.5MHz. In Japan, the available frequency band is 916.5MHz to 927.5MHz. The total bandwidth available for 802.11ah is 6MHz to 26MHz, according to the country code.

Fig. 1D is a system diagram illustrating an exemplary RAN113 and CN 115. RAN113 may employ NR radio technology to communicate with WTRUs 102a, 102b, 102c via an air interface 116. RAN113 may also communicate with CN 115.

RAN113 may include gnbs 180a, 180b, 180c, but it should be understood that RAN113 may include any number of gnbs in accordance with the present disclosure. Each gNB180a, 180b, 180c may include one or more transceivers to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The gnbs 180a, 180b, 180c may implement MIMO technology. The gnbs 180a, 108b may transmit signals to and/or receive signals from the WTRUs 102a, 102b, 102c using beamforming. Thus, the gNB180a may use multiple antennas to transmit wireless signals to and/or receive wireless signals from the WTRU 102a, for example. The gnbs 180a, 180b, 180c may implement carrier aggregation techniques. The gNB180a may transmit multiple component carriers to the WTRU 102 a. A subset of these component carriers may be on the unlicensed spectrum while the remaining component carriers may be on the licensed spectrum. In such examples, the gnbs 180a, 180b, 180c may implement coordinated multipoint (CoMP) techniques. WTRU 102a may receive coordinated transmissions from gNB180a and gNB180 b (and/or gNB180 c).

The WTRUs 102a, 102b, 102c may communicate with the gnbs 180a, 180b, 180c using transmissions associated with the scalable parameter configurations. For example, the OFDM symbol interval and/or OFDM subcarrier interval may vary for different transmissions, different cells, and/or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with the gnbs 180a, 180b, 180c using subframes or Transmission Time Intervals (TTIs) of various and/or scalable lengths (e.g., including varying numbers of OFDM symbols and/or absolute times of continuously varying lengths).

The gnbs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in an independent configuration and/or in a non-independent configuration. In an example standalone configuration, the WTRUs 102a, 102B, 102c may communicate with the gnbs 180a, 180B, 180c without also having access to other RANs (e.g., the enode bs 160a, 160B, 160c described herein). In an independent configuration, the WTRUs 102a, 102b, 102c may utilize one or more of the gnbs 180a, 180b, 180c as mobility anchors. In a stand-alone configuration, the WTRUs 102a, 102b, 102c may communicate with the gnbs 180a, 180b, 180c using signals in unlicensed frequency bands.

In an example non-standalone configuration, the WTRU 102a, 102B, 102c may communicate with and/or connect to the gNB 180a, 180B, 180c while also communicating with and/or connecting to another RAN (e.g., the enode B160a, 160B, 160c described herein). For example, the WTRUs 102a, 102B, 102c may implement DC principles to communicate with one or more gnbs 180a, 180B, 180c and/or one or more enodebs 160a, 160B, 160c, e.g., substantially simultaneously. In an example non-standalone configuration, the enode bs 160a, 160B, 160c may serve as one or more mobility anchors for the WTRUs 102a, 102B, 102c, while the gnbs 180a, 180B, 180c may provide additional coverage and/or throughput for serving the WTRUs 102a, 102B, 102 c.

Each of the gnbs 180a, 180b, 180c may be associated with a particular cell and/or may be configured to handle any one or more and/or any combination of functions including radio resource management decisions, handover decisions, user scheduling in UL and/or DL, supporting network slicing, dual connectivity, interworking between NR and E-UTRA, routing of user plane data to User Plane Functions (UPFs) 184a, 184b, routing of control plane information to access and mobility management functions (AMFs) 182a, 182b, and any other type of function that may be performed by the gNB. The gnbs 180a, 180b, 180c may communicate with each other through an Xn interface.

The CN 115 shown in fig. 1D may include any one or more and/or any combination of AMFs 182a, 182b, UPFs 184a, 184b, session Management Functions (SMFs) 183a, 183b, data Networks (DNs) 185a, 185b, and any other type of management function. While each of these functions is depicted in fig. 1D as part of the CN 115, it will be understood that any one or more of these elements may be owned and/or operated by an entity other than the CN operator.

AMFs 182a, 182b may be connected to one or more of gNB 180a, 180b, 180c in RAN 113 via an N2 interface and may act as a control node. For example, the AMFs 182a, 182b may be responsible for the following functions, which may include any one or more and/or any combination of the following functions: authenticating a user of the WTRU 102a, 102b, 102c, supporting network slicing (e.g., handling different PDU sessions with different requirements), selecting a particular SMF 183a, 183b, managing a registration area, terminating NAS signaling, mobility management, and any other type of control node function. Network slices may be used by one or both of the AMFs 182a and 182b to customize the CN support for the WTRUs 102a, 102b, 102c based on the type of service utilized by the WTRUs 102a, 102b, 102 c. For example, different network slices may be established for different use cases, including any one or more and/or any combination of services that rely on ultra-reliable low latency (URLLC) access, services that rely on enhanced large-scale mobile broadband (eMBB) access, services for Machine Type Communication (MTC) access, and any other type of use case. One or more of the AMFs 182A, 182b may provide control plane functionality for switching between RAN 113 and any other RAN that may employ other radio technologies, such as LTE, LTE-A, LTE-a Pro, and/or any non-3 GPP access technology (e.g., wiFi).

One or more of the SMFs 183a, 183b may be connected to one or more of the AMFs 182a, 182b in the CN 115 via an N11 interface. One or more of the SMFs 183a, 183b may also be connected to one or more of the UPFs 184a, 184b in the CN 115 via an N4 interface. One or more of the SMFs 183a, 183b may select and/or control one or more of the UPFs 184a, 184b and/or configure routing of traffic through one or more of the UPFs 184a, 184 b. One or more of the SMFs 183a, 183b may perform other functions including any one or more and/or any combination of managing and/or assigning UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notifications, and any other type of function. The PDU session types may be IP-based, non-IP-based, and/or Ethernet-based.

One or more of the UPFs 184a, 184b may connect to one or more of the gnbs 180a, 180b, 180c in the RAN 113 via an N3 interface, which may provide one or more of the WTRUs 102a, 102b, 102c with access to a packet-switched network, such as the internet 110, which may facilitate communications between one or more of the WTRUs 102a, 102b, 102c and IP-enabled devices. One or more of UPFs 184a, 184b may also or alternatively perform other functions including any one or more and/or any combination of routing and/or forwarding packets, enforcing user plane policies, supporting multi-homing PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, and any other type of functionality.

The CN 115 may facilitate communications with other networks. For example, the CN 115 may include or may communicate with an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server), which may serve as an interface between the CN 115 and the PSTN 108. The CN 115 may provide one or more WTRUs 102a, 102b, 102c with access to one or more other networks 112. One or more other networks 112 may include wired and/or wireless networks that may be owned and/or operated by other service providers. One or more of the WTRUs 102a, 102b, 102c may connect to one or more of the local Data Networks (DNs) 185a, 185b through one or more of the UPFs 184a, 184b via an N3 interface to the UPFs 184a, 184b and an N6 interface between the UPFs 184a, 184b and the DNs 185a, 185 b.

One or more and/or any combination of the functions described herein with respect to the WTRUs 102a-d, the base stations 114a-B, the enode bs 160a-c, the MME 162, the SGW 164, the PGW 166, the gnbs 180a-c, the AMFs 182a-B, the UPFs 184a-B, the SMFs 183a-B, the DNs 185a-B, and/or any other devices described herein may be performed by any one or more emulated devices. Such an emulation device may be any one or more and/or any combination of devices configured to emulate one or more and/or any combination of the functions described herein. For example, such an emulation device may be used to test other devices and/or analog network and/or WTRU functions.

The simulation device may be designed to implement one or more tests of one or more other devices in a laboratory environment and/or an operator network environment. For example, one or more emulation devices can perform one or more and/or any combination of functions while being fully or partially implemented and/or deployed as part of a wired and/or wireless communication network in order to test other devices within the communication network. One or more of the simulated device executable functions and/or any combination thereof, while being temporarily implemented and/or deployed as part of a wired and/or wireless communication network. The emulated device may be directly coupled to another device for testing purposes and/or may perform the test using over-the-air wireless communications.

One or more emulation devices can perform one or more and/or any combination of functions without being implemented and/or deployed as part of a wired and/or wireless communication network. For example, one or more simulation devices may be used in a test laboratory and/or a test scenario in a non-deployed (e.g., tested) wired and/or wireless communication network in order to enable testing of one or more components. The one or more simulation devices may be test devices. One or more emulating devices can transmit and/or receive data using direct RF coupling and/or wireless communication via RF circuitry (e.g., which can include one or more antennas).

Fig. 1E illustrates an exemplary Wireless Local Area Network (WLAN) device. One or more such devices may be used to implement one or more aspects disclosed herein. WLAN may include, but is not limited to, access Point (AP) 102, station (STA) 110, and STA 112. One or both of STAs 110 and 112 may be associated with AP 102. The WLAN may be configured as one or more protocols implementing the IEEE 802.11 communication standard, which may include one or more channel access schemes, such as Direct Sequence Spread Spectrum (DSSS), OFDM, OFDMA, etc. The WLAN may operate in a certain mode, e.g., in infrastructure mode, ad hoc mode, etc.

A WLAN operating in infrastructure mode may include one or more APs in communication with one or more STAs. One or more APs and/or STAs associated with a particular AP may include a Basic Service Set (BSS). For example, AP 102, STA 110, and/or STA 112 may include BSS 142. An Extended Service Set (ESS) may include one or more APs (which may be associated with one or more BSSs) and/or one or more STAs associated with the one or more APs. The AP may access and/or interface to a Distribution System (DS) 116, which may be wired and/or wireless, and may carry traffic to and/or from the AP. Traffic originating outside the WLAN to STAs in the WLAN may be received at an AP in the WLAN, which may send the traffic to the STAs in the WLAN. Traffic originating from a STA in the WLAN destined for a destination outside the WLAN (e.g., to server 118) may be sent to an AP in the WLAN, which may send the traffic to the destination, e.g., to network 114 via DS 116 for sending to server 118. Traffic between STAs within a WLAN may be transmitted through one or more APs. For example, a source STA (e.g., STA 110) may have traffic intended for a destination STA (e.g., STA 112). STA 110 may send such traffic to AP 102. AP 102 may send such traffic to STA 112.

The WLAN may operate in an ad hoc mode. Ad hoc mode WLANs may be referred to as independent basic service sets (IBBS). In an ad hoc mode WLAN, STAs may communicate directly with each other (e.g., STA 110 may communicate with STA 112 without such communication being routed through the AP).

IEEE 802.11 devices (e.g., IEEE 802.11 APs in a BSS) may use beacon frames to advertise the presence of a WLAN network. An AP, such as AP 102, may transmit beacons on a channel, such as a primary channel (e.g., which may be a fixed channel). The STA may establish a connection with the AP using a channel such as a primary channel.

One or more STAs and/or one or more APs may use a carrier sense multiple access with collision avoidance (CSMA/CA) channel access mechanism. In CSMA/CA, STAs and/or APs may sense the primary channel. For example, if the STA has data to transmit, the STA may sense the primary channel. The STA may fall back if it detects that the sensed primary channel is busy. For example, a WLAN or a portion thereof may be configured so that one or more particular STAs may transmit at a given time, e.g., in a given BSS. Channel access may include RTS and/or CTS signaling. The transmitting device may transmit an exchange of Request To Send (RTS) frames and the receiving device may transmit a Clear To Send (CTS) frame. The AP may send an RTS frame to the STA if the AP has data to send to the STA. If the STA is ready to receive data, the STA may respond with a CTS frame. The CTS frame may include a time value that may alert other STAs to defer from accessing the medium while the AP initiating the RTS may transmit its data. Upon receiving the CTS frame from the STA, the AP may transmit data to the STA.

A device may reserve spectrum via a Network Allocation Vector (NAV) field. In an IEEE 802.11 frame, a NAV field may be used to reserve a channel for a period of time. An STA that may desire to transmit data may set the NAV to a time at which it may desire to use the associated channel. When such STAs set a NAV, the NAV may be set for the associated WLAN or subset thereof (e.g., BSS). One or more other STAs may count down the NAV until the NAV counter reaches a value equal to zero. When such a counter reaches a value of zero, the NAV function may indicate to one or more other STAs that the channel may now be available.

Devices in a WLAN, such as an AP or STA, may include one or more of a processor, memory, radio receiver, transmitter (e.g., which may be combined in a transceiver), and/or antenna (e.g., antenna 106 in fig. 1E), etc. The processor functions may include one or more processors. For example, a processor may include any one or more and/or any combination of general-purpose processors, special-purpose processors (e.g., baseband processors, MAC processors, etc.), digital Signal Processors (DSPs), application Specific Integrated Circuits (ASICs), field Programmable Gate Array (FPGA) circuits, any other type of Integrated Circuit (IC), state machines, and any other type of processor that may perform one or more processing functions. Two or more processors may or may not be integrated with each other. A processor (e.g., one or more processors of a processor function or subset thereof) may be integrated with one or more other functions (e.g., other functions such as memory). The processor may perform any one or more and/or any combination of signal encoding, data processing, power control, input/output processing, modulation, demodulation, and/or any other functions that may enable the device to operate in a wireless environment such as the WLAN of fig. 1E. The processor may be configured to execute processor-executable code (e.g., instructions), including, for example, software and/or firmware instructions. The processor may be configured to execute computer-readable instructions, which may be included on one or more processors (e.g., a chipset that may include memory and/or a processor) and/or memory. Execution of these instructions may cause the device to perform any one or more and/or any combination of the functions described herein.

A device may include one or more antennas. The device may employ Multiple Input Multiple Output (MIMO) technology. Such one or more antennas may receive one or more radio signals. One or more processors associated with such devices can receive one or more radio signals, for example, via one or more antennas. One or more antennas may transmit one or more radio signals (e.g., based on one or more signals that may be transmitted from a processor).

A device may have memory that may include one or more devices for storing programming and/or data, such as any one or more and/or any combination of processor-executable code and/or instructions (e.g., software, firmware, etc.), electronic data, databases, and any other type of digital information. The memory may include one or more memory cells. Such one or more memory units may be integrated with one or more other functions (e.g., functions configured and/or included in the device, such as functions in a processor associated with the device). The memory may include any one or more of read-only memory (ROM) (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), etc.), random Access Memory (RAM), magnetic disk storage media, optical storage media, flash memory devices, and any other non-transitory computer-readable medium that may be configured to store information, and/or any combination thereof. The memory may be coupled to the processor. The processor may communicate directly with one or more memory entities, e.g., via a system bus, etc.

A WLAN in an infrastructure Basic Service Set (BSS) mode may include an Access Point (AP) associated with the BSS and one or more Stations (STAs) associated with the AP. The AP may have access and/or interface to a Distribution System (DS), which may be wireless and/or wired or a combination thereof. The AP may also or alternatively access and/or interface to one or more wired and/or wireless networks, which may be any other type of network that may transmit traffic into and/or out of the BSS. Such wired and/or wireless networks may carry traffic entering and/or exiting the BSS. Traffic to one or more STAs (e.g., one or more of which may originate from STAs outside the BSS) may arrive through the AP and may be delivered to the one or more STAs. Traffic originating from one or more STAs (e.g., directed to a destination outside the BSS) may be sent to the AP (e.g., delivered to the respective destination).

Traffic between one or more STAs within the BSS may be transmitted through an AP associated with the BSS. The source STA may send traffic to the AP. The AP may deliver the traffic to the destination STA. Traffic between STAs (e.g., within a BSS) may be peer-to-peer traffic. Such peer-to-peer traffic may be sent between the source STA and the destination STA (e.g., directly), e.g., with Direct Link Setup (DLS) that may use 802.11e DLS and/or 802.11z Tunnel DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not include one or more APs and/or one or more STAs that may communicate directly with each other. The AP and/or STA may use an "ad hoc" communication mode.

The AP may transmit a beacon on a fixed channel, such as a primary channel (e.g., using an 802.11ac infrastructure mode of operation). Such a channel may be 20MHz wide. Such a channel may be an operating channel of a BSS. Such channels may be used by one or more STAs to establish a connection with one or more APs. The channel access mechanism (e.g., in an 802.11 system) may be carrier sense multiple access with collision avoidance (CSMA/CA).

In an operational mode utilizing the CSMA/CA channel access mechanism, one or more STAs and/or one or more APs (e.g., each STA in the BSS, including any AP) may detect (e.g., sense) a fixed channel (e.g., a primary channel). The one or more STAs and/or the one or more APs may fall back if such a channel is detected to be busy. A STA (e.g., only one STA) may transmit at a given time in a given BSS.

High Throughput (HT) STAs may communicate using 40MHz wide channels (e.g., in an 802.11n system). For example, the use of such channels may be achieved by combining a 20MHz primary channel with an adjacent 20MHz channel to form an adjacent channel having a width of 40 MHz.

Very High Throughput (VHT) STAs may support any one or more and/or any combination of channels (e.g., in an 802.11ac system) that are 20MHz, 40MHz, 80MHz, and 160MHz wide. In some examples, such 40MHz and/or 80MHz channels may be formed in a manner similar to the 802.11n system described herein forming 40MHz wide channels, for example, by combining multiple 20MHz channels (e.g., consecutive 20MHz channels).

For example, a 160MHz channel may be formed by combining eight (8) consecutive 20MHz channels or by combining two non-consecutive 80MHz channels. Such 160MHz channel configurations may be referred to as 80+80MHz configurations and/or 80+80 configurations. In the example 80+80 configuration, after channel coding, the data may pass through a segment parser. The segment parser may split such data into two streams. IFFT and/or time domain processing may be performed on such streams, e.g., on each of the two streams separately. The resulting two processed streams may each be mapped to one of two channels. For example, a first processing stream may be mapped to a first channel of a set of two channels in an 80+80 configuration, and a second processing stream may be mapped to a second channel of the set of two channels in the 80+80 configuration. The data of the two streams may be transmitted, for example, via two channels. At the receiver, the foregoing operations may be reversed, and the data of the two streams may be combined. The combined data may be sent to the MAC.

Secondary 1GHz modes of operation (e.g., via 802.11af and/or 802.11 ah) may be supported. One or more channel operating bandwidths and/or carriers may be reduced (e.g., relative to carriers that may be used in 802.11n and/or 802.11 ac). The 802.11af may support, for example, 5MHz, 10MHz, and/or 20MHz bandwidths in the TV white space (TVWS) spectrum. 802.11ah may support, for example, 1MHz, 2MHz, 4MHz, 8MHz, and 16MHz bandwidths in non-TVWS spectrum. In accordance with the present disclosure, metering Type Control (MTC) devices may be supported, for example, in macro coverage areas (e.g., in 802.11ah systems). MTC devices may have limited capabilities. MTC devices may include (e.g., only) support for limited bandwidth. MTC devices may also or alternatively be designed to increase battery life.

The WLAN system may support multiple channels and/or channel widths, such as those described in the 802.11n, 802.11ac, 802.11af, and/or 802.11ah standards. WLAN systems (e.g., such as those with multi-channel and/or multi-channel width support) may include channels designated as primary channels. The primary channel may have a bandwidth substantially equal to (e.g., equal to) the maximum common operating bandwidth that may be supported by one or more STAs (e.g., all STAs) in the BSS. The bandwidth of the primary channel may be limited by a minimum bandwidth mode of operation supported by one or more STAs (e.g., one or more STAs operating in a BSS).

For example, if there are one or more STAs (e.g., one or more MTC-type devices) that may support (e.g., only) 1MHz mode (e.g., in a non-limiting example 802.11ah implementation), the primary channel may be 1MHz wide. In such an exemplary implementation, the primary channel may be set to a minimum bandwidth supported by any one or more of the STAs and/or APs operating in the BSS, which in this example is a 1MHz wide mode, in the case where any other AP and/or STA in the BSS may support 2MHz, 4MHz, 8MHz, 16MHz, and/or any other channel bandwidth operating mode other than 1 MHz.

One or more carrier sense settings (e.g., all carrier sense settings) and/or one or more NAV settings (e.g., all NAV settings) may depend on the status of the primary channel. For example, if the primary channel is busy (e.g., because STAs supporting only 1MHz mode of operation are transmitting to the AP), then all available frequency bands may be considered busy, e.g., where most of the frequency bands may remain idle and available.

For example, the available frequency bands that can be used by an 802.11ah implementation may depend on location. For example, the available frequency bands that may be used by 802.11ah implementations may range from 902MHz to 928MHz (e.g., in the united states), from 917.5MHz to 923.5MHz (e.g., in korea), from 916.5MHz to 927.5MHz (e.g., in japan), and so forth. The total bandwidth available for an exemplary 802.11ah implementation may be 6MHz to 26MHz, or any other bandwidth range, and may depend on the country code.

According to the disclosed examples, the quality of service provided to a user may be enhanced. For example, quality of service provided to a wide range of users in various usage scenarios (e.g., high density scenarios in the 2.4GHz and/or 5GHz bands) may be enhanced in accordance with the disclosed examples. The disclosed aspects may support dense deployments of APs and/or STAs and/or their associated Radio Resource Management (RRM) techniques.

Applications of high-efficiency WLAN (HEW) may include any one or more and/or any combination of emerging usage scenarios, such as data delivery for stadium events, high user density scenarios (e.g., train stations), enterprise environments, retail environments, scenarios that may rely on video delivery, wireless services for medical applications, and any other type of usage scenario.

Measured traffic for various applications may tend to be relatively short packets. For example, the network application may generate short packets. Such applications (not limited to network applications) may include one or more of a virtual office application, a TCP ACK application, a video stream ACK application, a device and/or controller application (e.g., a mouse application, a keyboard application, a game control application, etc.), an access activity application (e.g., probe request, probe response, etc.), a network selection activity application (e.g., probe request, access Network Query Protocol (ANQP), etc.), a network management activity application (e.g., control frame, etc.), and any other application that may generate short packets.

The multi-user (MU) feature may include one or more of UL OFDMA, DL OFDMA, UL MU-MIMO, and DL MU-MIMO, or any combination thereof. One or more apparatuses and/or mechanisms for multiplexing UL random access for different purposes may be designed and/or defined in accordance with the present disclosure.

Low power operation for devices such as 802.11 devices may be set forth herein. For example, wake-up radio (WUR) operations that may be performed at the MAC layer and/or PHY layer are set forth in this disclosure.

WUR operating bands may include 2.4GHz and/or 5GHz. WUR operating bands can be extended to the secondary 1GHz. WUR may operate as a companion radio to a primary connected radio that may be used to transmit 802.11 packets (e.g., a "regular" 802.11 packet and/or a non-WUR 802.11 packet). WUR may transmit packets that may carry control information (e.g., control information only). WUR transmissions may have low active receiver power consumption, for example, less than one milliwatt. Reception of the wake-up packet by WUR may wake-up the accompanying primary connection radio from sleep. WUR may have a range that may be the same as or greater than the range accompanying the primary connection radio (e.g., when the primary connection radio operates over at least a 20MHz payload bandwidth).

The AP STA and/or the non-AP STA may be associated with at least one WUR as a companion radio. For example, the one or more WUR may be included in any usage scenario that may include any one or more and/or any combination of IoT devices, low-power operation of smartphones, fast message/incoming call notification scenarios, fast status query/report, configuration change scenarios, fast emergency/critical event reporting scenarios, and any other type of usage scenario suitable for including one or more WUR.

One or more WUR related negotiations may be performed in the primary radio. Such negotiations may include any one or more of band negotiations, channel negotiations, negotiations relating to STA ID allocation in wake up packets, negotiations relating to an indication of time required to turn on an 802.11 radio, negotiations relating to an indication of periodic WUR receiver on/off scheduling, negotiations relating to the definition of one or more WUR pattern elements (e.g., to carry information in a current frame exchange and/or another frame exchange), and any other WUR related negotiations, and/or any combination thereof.

Fig. 2A illustrates an example frame exchange and WUR negotiation 200. The AP 210 may receive WUR requests 221 from STAs 220 during periods when WURx 230 may shut down 231. The AP 210 may send WUR responses 211 to the STA 220 during periods when WURx 230 may shut down 231. STA 220 may perform WUR signaling 222 during periods when WURx 230 may shut down 231. Such WUR signaling 222 may indicate or otherwise inform the AP 210 that the STA 220 may be entering WUR state. The period that WURx 230 may be off may be the same as or similar to the period that Primary Connectivity Radio (PCR) 240 may be on 241. Note that "PCR", "802.11 radio" and "primary radio" may be used interchangeably herein.

STA 220 may enter WURx on state 232 and PCR 240 off state 242. During such periods (e.g., periods 232 and/or 242), the AP 210 may transmit the wake-up packet 212. For example, after a certain amount of delay 251, STA 220 may enter PCR on state 243 and WURx off state 233, e.g., according to or based on a pre-configured and/or dynamically determined schedule. When STA 220 is in WURx off state 233, STA 220 may send PS-poll frames to AP 210 and/or trigger unscheduled asynchronous power save delivery (U-APSD) 223.

One or more WUR action frames may be used. The one or more WUR action frames may have a WUR frame format, such as the exemplary format 290 shown in fig. 2B. WUR action frames 260 may be transmitted over WUR channels. The length of the MAC header 261 of WUR action frame 260 may be fixed. The MAC header 261 may include a subfield 270 that may include any one or more and/or any combination of a frame control subfield 271, an address subfield 272, a Type Dependent (TD) control subfield 273, and any other type of subfield.

The frame control subfield 271 in the subfield 270 may include one or more WUR frame type subfields, such as a WUR type subfield 281 and/or a WUR type subfield 282. The type subfield 281 and/or the type subfield 282 may each identify and/or indicate WUR frame types. For example, the type subfield 281 may indicate WUR beacon frame type and/or the type subfield 282 may indicate WUR wake up frame. Any one or more frame types may be indicated by each of any one or more and/or any combination of type subfields that may be included in the frame control subfield.

The Type Dependent (TD) control subfield 273 of the MAC header 260 may include type dependent control information. WUR action frame 260 may include one or more frame body fields, such as frame body field 262.WUR action frame 260 may also or alternatively include one or more Frame Check Sequence (FCS) fields, such as FCS field 263.

In an exemplary WUR scenario, to save power on the non-AP STA side, there may be one or more (e.g., many) downlink transmissions from the AP to the non-AP STA, while there may be limited or no uplink transmissions from such non-AP STA to the AP. Closed loop transmission schemes such as beamforming, antenna selection, rate or Modulation Coding Scheme (MCS) selection, WUR narrowband channel selection, etc., may be used in such exemplary WUR scenarios.

WUR may be in a duty cycle mode (e.g., not always on). The duty cycle may be defined as a period T, where t=t _on +T _off Wherein T is _on Representing the duration of the "on" period of the duty cycle, T _off Representing the duration of the "off" period of the duty cycle.

Multicast and/or broadcast transmissions may be transmitted over WUR channels. Fig. 3 illustrates an example frame exchange 300 that may represent one or more example multicast and/or broadcast transmissions that may be performed, for example, when one or more STAs are in a duty cycle mode. The duty cycle mode may cause STA1 320 to be in an on state 321, an off state 322, an on state 323, an off state 324, and/or an on state 325, for example. The duty cycle period 341 may be a duty cycle period used by the STA1 320. The duty cycle mode may cause, for example, STA 2330 to be in an off state 331, an on state 332, an off state 333, an on state 334, and/or an off state 335. The duty cycle period 351 may be a duty cycle period used by the STA 2330.

The AP 310 may attempt to transmit WUR frames 311 to one or more of the SAT1 320 and STA2 330. STA2 330 may receive WUR frame 311 because it may be in an on state 332 when WUR frame 311 is transmitted. STA1 320 may not receive WUR frame 311 at 361 because it may be in off state 322 when WUR frame 311 is transmitted.

One or more closed loop transmission schemes may be implemented in accordance with the present disclosure. Any one or more and/or any combination of measurements in the primary radio, such as Channel State Information (CSI), signal-to-noise ratio (SNR), signal-to-noise-and-interference ratio (SINR), and any other type of measurement, may be reused and/or applied at the WUR radio. Information that may be related to one or more closed loop schemes (e.g., beamforming (BF), rate adaptation, etc.) may be included in one or more negotiation frames. Such information, which may be related to one or more closed loop schemes, may include, for example, channel information that may be used for WUR channel selection, WUR beamforming, and/or WUR rate selection. Such information related to the one or more closed loop schemes may also or alternatively include, for example, WUR radio delta factors and/or primary radio delta factors (e.g., which may be used to compensate for one or more RF chain differences).

The WLAN device may include multiple sets (e.g., two sets) of radios and/or RF chains (e.g., due to the addition of WUR). The first such set may be for the WLAN primary radio, while the second such set may be for WUR. Multiple (e.g., two) radio sets may share the same antenna set. For example, measurements made on one radio (e.g., a set of multiple radios and/or RF chains of a WLAN device) may be applied to another radio using a set of one or more delta factors.

Fig. 4 illustrates an exemplary system 400. The WTRU 410 may be one or both of an AP and a STA, which may include multiple antennas, such as antennas 411, 412, 413, 414. The WTRU 420 may be one or both of an AP and a STA, which may include multiple antennas, such as antennas 421, 422.

The WTRU 420 may be a receiver of exemplary communications (e.g., one or both of an AP and a STA). Two or more sets of RF chains may share the same antenna group at the receiver and/or transmitter.

The physical channel (e.g., an over-the-air physical channel) may remain the same physical channel, e.g., independent of any two or more RF chains that may be used at the receiver. One or more channel measurements may be performed at baseband. RF chain impairments may be indicated by such one or more channel measurements. The one or more channel measurements performed at the primary radio (e.g., primary radio RF processing function 431) may be different from the one or more channel measurements performed at the WUR radio (e.g., WUR radio RF processing function 432).

The transmitter WTRU 410 may reuse the channel measurements that have been measured by the primary radio RF processing function 431 to predict the channel conditions that WUR baseband may observe (observe). The transmitter WTRU 410 may use the primary radio to exchange one or more communications regarding channel state information that may be used to configure transmissions with WUR radio RF processing functions 432. A closed loop WUR configuration is possible.

The difference between measurements performed by each of the two or more radios (e.g., the primary radio RF processing function 431 and WUR radio RF processing function 432) may be referred to as an increment factor. One or more delta factors may be determined at, received by, and/or provided to a transmitter (e.g., WTRU 410) such that such transmitter may compensate for differences between measurements in a system (e.g., system 400), for example, using one or more differences indicated by the one or more delta factors.

One or more channel measurements on first and second antennas (e.g., antennas 421 and 422) of a set of at least two antennas (or first and second layers of a set of at least two layers) may make such measurements using a primary radio (e.g., primary radio RF processing function 431). For non-limiting illustration purposes only, such primary radio measurements made by such first and second antennas (e.g., antennas 421 and 422), respectively, may be referred to herein as M_main ₁ And M_main ₂ 。

One or more channel measurements made by first and second antennas (e.g., antennas 421 and 422) of a set of at least two antennas (or first and second layers of a set of at least two layers) may make such measurements using WUR radios (e.g., WUR radio RF processing functions 432). For non-limiting explanation purposes only, such WUR radio measurements made by such first and second antennas (e.g., antennas 421 and 422), respectively, may be referred to herein as M WUR ₁ And M_WUR ₂ 。

One or more delta factors may be defined as, for example, the receive antenna or M_main on the receive layer _x -M_WUR _x Is a result of the expected outcome of (a). In the exemplary system 400, exemplary delta factors may be defined by equations 1 and 2.

Delta ₁ ＝E(M_main ₁ -M_SUR ₁ ) (1)

Delta ₂ ＝E(M_main ₂ -M_SUR ₂ ) (2)

The system 400 may include deltas that may correspond to two receive RF processing functions, respectively ₁ Factors 441 and Delta ₂ A factor 442.Delta (Delta) ₁ Factor 441 may provide the RF processing difference between 445 of the primary radio RF processing function 431 and 446 of WURx RF processing function 432. Delta (Delta) ₂ The factor 442 may provide an RF processing difference between 447 of the primary radio RF processing function 431 and 448 of the WURx RF processing function 432. One or more measurements M_WUR observed through the first antenna 421 and WUR RX processing function 432 may be used ₁ 446 and general purposeOne or more measurements M_main observed through the first antenna 421 and the primary radio RX processing function 431 ₁ To calculate Delta ₁ Factor 441. One or more measurements M_WUR observed through the second antenna 422 and WUR RX processing function 432 may be used ₂ 448 and one or more measurements m_main observed through the second antenna 422 and the primary radio RX processing function 431 ₂ To calculate Delta ₂ A factor 442.

In examples that may include more than two receive antennas and/or more than two MIMO layers, more than two delta factors may be obtained and/or determined. The measurements contemplated herein include any one or more and/or any combination of CSI, SNR, SINR, received Signal Strength Indicator (RSSI), and any other type of measurement.

The one or more delta factors associated with the first WUR channel may be different from the one or more corresponding delta factors associated with the second WUR channel. One or more delta factors may be reported, for example, per WUR channel. For example, where four WUR channels may be supported, the narrowband delta factor associated with each of the four WUR channels may be reported.

The delta factor may not be sensitive to WUR channel frequency. For example, one or more wideband delta factors may be reported, which may represent one or more delta factors that may be associated with all applicable WUR channels or any subset thereof.

One or more delta factors may be obtained and/or determined offline. Alternatively or additionally, one or more delta factors may be hard-coded to the device. Alternatively or additionally, one or more delta factors may be obtained online, for example, by turning each radio (e.g., master radio RF processing function 431 and WUR radio RF processing function 432) on and off and comparing the resulting measurements.

One or more delta factors may be exchanged by the transmitter and the receiver, such as WTRU 410 and WTRU 420, respectively. Such one or more delta factors may be exchanged via a capability exchange. The one or more delta factors may also or alternatively be exchanged by the transmitter and receiver (e.g., WTRU 410 and WTRU 420) using one or more control frames and/or management frames, respectively.

WUR negotiations may be driven by the AP during one or more beamforming transmissions. Alternatively, or in addition, WUR negotiations may be driven by STAs during one or more beamforming transmissions. Fig. 5 illustrates an exemplary beamforming transmission procedure 500 for WUR negotiations that may be driven by an AP. Beamforming transmission procedures for WUR negotiations that may be driven by STAs are also contemplated herein.

Using the primary radio, the AP501 may transmit a sounding frame or set of sounding frames. AP501 may send a Null Data Packet (NDP) Notification (NDPA) frame 502 to one or more STAs, such as STA1 and STA2, 520. NDPA frame 502 may include a request by one or more receiving STAs (e.g., STA1, 510, 520) to report CSI and/or Channel Quality Indication (CQI) information, e.g., over the entire frequency band and/or one or more Resource Units (RUs).

AP501 may transmit NDP frame 503 using the primary radio after an inter-frame space (IFS) duration xIFS 509 following transmission of NDPA frame 502.NDP frame 503 may include one or more sounding sequences. Note that terms such as "xIFS" are used herein to refer to various IFSs that may be the same or different from any other IFS or IFSs described herein, where "x" may be any value, variable, or indicator.

The AP501 may attempt to reuse channel measurements in one or more future transmissions, e.g., using different radios. The AP501 may be configured to not apply spatial precoding to the NDP training sequence.

The AP501 may be configured to apply a precoding scheme to one or more NDP training sequences. The AP501 may be configured to apply the same precoding scheme to one or more (e.g., future) WUR transmissions.

AP501 may send trigger frame 504 after an xIFS duration 509, which may follow the transmission of NDP frame 503, which may request one or more measurements, such as one or more channel state information measurements from one or both of STA1 and STA2 520. Any type of request for any one or more measurements, and any combination of any one or more measurements, is contemplated herein.

STA1 and STA2 520 may send UL CSI511 and 521, respectively, to AP501 in response to trigger frame 504. STA1 510 and STA2 520 may transmit UL CSI511 and 521 after the xIFS duration 509 after transmission of frame 504 may be triggered. Measurement information such as UL CSI521 may include information obtained or otherwise determined by monitoring primary radio 531. Any other measurements and any combination thereof are contemplated herein.

AP501 may send WUR trigger frame 505 to one or both of STA1 and STA2 520 after receiving the xIFS duration 509 after UL CSI511 and UL CSI 521. Alternatively, or in addition, the transmission of WUR trigger frame 505 may be performed using a different transmission opportunity (TXOP) than that used previously by AP501 to transmit, for example, frames 502, 503, 504.

The AP 501 may sense and/or acquire a channel that may be used to transmit WUR trigger frames 505. WUR trigger frame 505 may include a closed loop transmission indication that may indicate an intent to perform one or more closed loop transmissions. WUR trigger frame 505 may include an indication (e.g., an explicit indication) of a detailed closed loop transmission scheme. WUR trigger frame 505 may include a beamforming scheme indication. The beamforming scheme indication may indicate or otherwise indicate to one or more STAs (e.g., STA1, STA2, 502) that the STAs may be required to transmit one or more delta factors to an AP (e.g., AP 501).

After receiving the xIFS duration 509 after WUR trigger frame 505, STA1 and STA2 520 may respond by transmitting WUR signal frames 512 and 522, respectively, to AP 501. WUR signal frames 512 and 522 may be transmitted using Single User (SU) transmissions or multi-user (MU) transmissions, or any combination thereof. One or more delta factors 532 may be included in WUR signal frames, such as WUR signal frame 512 and/or WUR signal frame 522, where the closed loop transmission indication may be provided in a WUR trigger frame (e.g., WUR trigger frame 505).

Using WUR channels, AP 501 may send Beam Forming (BF) transmissions 506, 507 to STA1 and STA2, 520, respectively. AP 501 may store, obtain, or otherwise determine CSI (e.g., per subcarrier, per x subcarriers) that may have been measured on the primary radio of AP 501. The AP 501 may store, obtain, or otherwise determine one or more receive delta factors (e.g., per receive antenna, per receive layer). The AP 501 may store, obtain, or otherwise determine one or more transmit delta factors (e.g., per transmit antenna, per transmit layer). For example, such one or more transmit delta factors may be available or obtainable when the AP 501 may use different RF chains to transmit the primary WLAN signal and/or WUR WLAN signal. AP 501 may use CSI and one or more delta factors 508 to generate BF transmissions: STA1 BF 506 and/or STA2 BF 507.

The AP 501 may store, obtain, or otherwise determine one or more WUR BF weights, for example, based on any of the information described herein.

The AP 501 may apply one or more WUR BF weights in the time and/or frequency domains. WUR BF weights in the time domain may be different from those in the frequency domain. The AP 501 may indicate in the WUR PHY header the time domain or frequency domain to which one or more WUR BF weights may be applied.

For example, concurrent WUR MU-MIMO transmissions may be performed when one or more beamforming weights may be obtained or otherwise determined. Such one or more beamforming weights may be obtained or otherwise determined for potentially increasing the signal strength of the transmission and/or suppressing the signal strength of the interfering signal.

The AP may apply WUR BF weights in the time and/or frequency domains. The AP may have frequency domain CSI (e.g., per subcarrier, per x subcarriers) that has been measured by the primary radio. Such CSI may be referred to as H _k Where k may be a subcarrier index. The AP may apply one or more delta factors (e.g., at the transmitter and/or receiver) to the channel matrix H. Such APs may be obtained or otherwise determined to be may be referred to as Hc _k Is described. The AP may obtain or otherwise determine a covariance matrix COV over the plurality of subcarriers. Equation 3 shows an exemplary mathematical equation that may be used to determine the covariance matrix COV on multiple subcarriers.

COV＝E(Hc _k Hc ^H _k ) (3)

Correction can be applied to the COV matrix, which can be based on H _k The COV matrix is calculated. For example, equations 4 and 5 may be used to calculate the covariance matrix for beamforming weight generation.

COV _pre ＝E(H _k H ^H _k ) (4)

COV＝COV _pre +E(delta delta ^H ) (5)

One or more BF weights may be obtained or determined by applying Singular Value Decomposition (SVD) to the covariance matrix. The resulting set or sets of BF weights may be applied to one or more subcarriers (e.g., to all subcarriers) in the frequency domain. Applying the resulting one or more sets of BF weights to one or more subcarriers (e.g., to all subcarriers) in the frequency domain may be equivalent or substantially equivalent to applying a single set of such BF weights in the time domain.

The AP may obtain or otherwise determine one or more BF weights based on SVD that may be performed on one or more Hc matrices. Such one or more BF weights may be one or more of a per-subcarrier weight and a per-x subcarrier weight (e.g., x may have a value greater than 1), or any combination thereof. Such one or more BF weights may be applied to the corresponding WUR signal in the frequency domain.

WUR beamforming transmission procedures may not use an increment factor. Fig. 6 illustrates an exemplary beamforming transmission procedure 600 for WUR negotiation that may be driven by an AP and may not use an increment factor. Also encompassed herein are beamforming transmission procedures for WUR negotiations that may be driven by STAs and may not use incremental factors.

One or more of WUR STA1 610 and WUR STA2 620 may be able to monitor multiple WUR channels simultaneously. One or more of WUR STA1 610 and WUR STA2 620 may be assigned to perform one or more CSI measurements on the assigned WUR channels. Such one or more CSI measurements may be performed using WUR (e.g., WUR STA1 610, WUR STA2 620) and without an increment factor.

Using the primary radio, the AP 601 may transmit a sounding frame or a set of sounding frames. AP 601 may transmit NDPA frame 602 to one or more STAs (e.g., STA1 610 and STA2 620). NDPA frame 602 may include a request 641 requesting one or more receiving STAs (e.g., STA1, 610, 620) to monitor and report CSI and/or CQI information for WUR radios, e.g., over the entire frequency band and/or one or more RUs.

The AP 601 may use the "other radio" field (which may also be referred to as a "second radio" field) in the request frame to request that one or more CSI measurements be performed on another radio (e.g., WUR radio). For example, the AP 601 may indicate such a request in the NDPA frame 602 and/or via a field (e.g., an "other radio" field) and/or any other frame in the NDPA frame 602. The AP 601 may include a field indicating a request to perform one or more CSI measurements on WUR radios in addition to the normal NDPA field.

One or both of STA1610 and STA2620 may be capable of performing wideband reception on one or more WUR channels. The AP 601 may instruct (e.g., via NDPA frame 602) one or both of STA1610 and STA2620 to report CSI on one or more of such WUR channels (e.g., on all of these WUR channels).

One or both of STA1610 and STA2620 may not be able to perform wideband reception using WUR radio and/or WUR channels. AP 601 may indicate WUR channel indices and/or IDs to one or both of STA1 and STA2620 (e.g., via NDPA frame 602), requesting that the respective one or more of STA1 and STA2620 monitor CSI on WUR channels indicated by such WUR channel indices and/or IDs.

Upon receiving a frame (e.g., NDPA frame 602) having a set of "other radio" fields or similar field sets, one or both of STA1 and STA2620 may use the other radio, e.g., WUR radio, to listen, monitor and/or measure CSI on one or more WUR channels that may be indicated by such "other radio" or similar fields.

AP 601 may transmit NDP frame 603 using the primary radio after yIFS duration 609 after transmission of NDPA frame 602. NDP frame 603 may include one or more sounding sequences.

The AP 601 may attempt to reuse channel measurements in one or more future transmissions, e.g., using different radios. The AP 601 may be configured to not apply spatial precoding to the NDP training sequence.

The AP 601 may be configured to apply a precoding scheme to one or more NDP training sequences. The AP 601 may be configured to apply the same precoding scheme over one or more (e.g., future) WUR transmissions.

One or both of STA1610 and STA2620 may know, obtain, or otherwise determine the training field position within the NDP frame 603. One or both of STA1610 and STA2620 may use WUR measurement channels based on the training fields of NDP frame 603.

One or both of STA1610 and STA2620 may know, obtain, or otherwise determine the duration of the NDP frame 603. One or both of STA1610 and STA2620 may switch back to the primary radio after receiving NDP frame 603.

The yIFS duration 609 may be the same or substantially the same as the xIFS duration 509 described herein with respect to fig. 5, e.g., the IFSs may be the same IFSs for examples that may utilize one or more delta factors and examples that do not utilize delta factors.

The yIFS duration 609 may be longer than the xIFS duration 509 described herein with respect to fig. 5, e.g., the IFS used in examples where one or more delta factors may be utilized may be shorter than the IFS used in examples where delta factors are not utilized. In examples where the delta factor is not used, a relatively longer yIFS duration may provide more time for STAs to switch between radio sets (e.g., between two radio sets).

The AP 601 may transmit a trigger frame 604 after the yIFS duration 609 after transmission of the NDP frame 603, which may request one or more measurements, such as one or more channel state information measurements, from one or both of STA1 and STA2 620. Any type of request for any one or more measurements, and any combination of any one or more measurements, is contemplated herein.

STA1 and STA2 610 and 620 may transmit UL CSI611 and 621, respectively, to AP 601 in response to trigger frame 604. UL CSI611 and 621 may be transmitted by STA1 and STA2 620 after yIFS duration 609 after transmission of trigger frame 604. Measurement information, such as UL CSI 621, may include information that may have been obtained or otherwise determined by monitoring WUR radio 631. Any other measurement and any combination thereof are contemplated herein.

In one or both of the example UL CSI611 and 621 frames, STA1 and/or STA2 620, respectively, may use the "other radio" field (or "second radio" field or any similar field) to indicate that CSI may be measured on another radio (e.g., WUR radio). The requested CSI may be associated with measurements of one WUR channel, multiple WUR channels, or all WUR channels.

The CSI may include any one or more and/or any combination of time domain CSI determined for narrowband WUR channels, time domain CSI determined for BF weight sets for each of one or more WUR channels, frequency domain CSI determined for narrowband WUR channels, frequency domain CSI determined for BF weight sets for each of one or more WUR channels, and any other type of CSI.

AP 601 may transmit WUR trigger frame 605 to one or both of STA1 610 and STA2 620 after the xIFS duration 609, which may follow the reception of UL CSI 611 and 621. Alternatively, or in addition, the transmission of WUR trigger frame 605 may be performed using a different TXOP than the one used previously by AP 601 to transmit, for example, frames 602, 603, 604.

The AP 601 may sense and/or acquire a channel that may be used to transmit WUR trigger frames 605. WUR trigger frame 605 may include a closed loop transmission indication, which may indicate an intent to perform one or more closed loop transmissions. WUR trigger frame 605 may include an indication (e.g., an explicit indication) of a detailed closed loop transmission scheme. WUR trigger frame 605 may include a beamforming scheme indication.

After receiving the yIFS duration 609 after the WUR trigger frame 605, STA1 and STA2 620 may respond by transmitting WUR signal frames 612 and 622, respectively, to the AP 601 using PCR or primary radio. WUR signal frames 612 and 622 may be transmitted using SU transmissions or MU transmissions, or any combination thereof.

Using the WUR channel, the AP 601 may send BF transmissions 606, 607 to STA1 and STA2 620, respectively. The AP 601 may store, obtain, or otherwise determine CSI (e.g., per subcarrier, per x subcarrier) that may have been measured in the time and/or frequency domain on WUR radios of the AP 601. The AP 601 may store, obtain, or otherwise determine one or more WUR BF weights, for example, based on any of the information described herein. The AP 601 may use the CSI 608 to generate BF transmissions STA1 BF 606 and/or STA2 BF 607.

The AP 601 may apply one or more WUR BF weights in the time and/or frequency domain. WUR BF weights in the time domain may be different from those in the frequency domain. The AP 601 may indicate in the WUR PHY header the time domain or frequency domain to which one or more WUR BF weights may be applied.

As noted, WUR beamforming transmission procedures may not use an increment factor. Fig. 7 illustrates an exemplary beamforming transmission procedure 700 for WUR negotiation that may be driven by an AP and may not use an increment factor. Also encompassed herein are beamforming transmission procedures for WUR negotiations that may be driven by STAs and may not use incremental factors.

Using the primary radio, the AP 701 may transmit a sounding frame or a set of sounding frames. AP 701 may transmit NDPA frame 702 to one or more STAs (e.g., STA1 and STA2, 720). STA1 710 and/or STA2 720 may not be able and/or configured to monitor multiple WUR channels simultaneously. NDPA frame 702 may include a request 741 requesting one or more receiving STAs (e.g., STA1, STA2, 720) to monitor and report CSI and/or CQI information for one or more WUR channels, e.g., using at least one WUR radio over the entire frequency band and/or one or more RUs.

The AP 701 may indicate, for example in the NDPA frame 702, that multiple NDP frames 703 may be sent ₁ ……703 _n Which may instruct and/or allow one or more STAs (e.g., STA1, STA2, 720) to sequentially (as opposed to simultaneously) switch to and monitor each of the plurality of WUR channels. The number of such NDP frames may be explicitly signaled, for example, in a frame such as NDPA frame 702. Alternatively, the number of the first and second channels,or, in addition, the number of NDP frames may be implicitly indicated, e.g., where the number of NDP frames may be the same as the number of WUR channels associated with "normal" WLAN bandwidth. NDP frame 703 ₁ ……703 _n May indicate to one or both of STA1710 and STA2720 that such STAs may be instructed and/or allowed to perform one or more CSI measurements using multiple WUR channels.

In response to an explicit or implicit indication of the number of NDP frames, one or more of STA1 and STA2720 may switch to a first WUR channel (e.g., WUR channel 1), e.g., after receiving a zIFS duration 709 after NDPA frame 702. The zIFS duration 709 may be equal to or greater than the amount of time that may be used for radio set handoff. The zIFS duration 709 may be less than, equal to, or greater than any of the xIFS duration 509 and yIFS 609 described herein.

STA1 and/or STA2 720 may switch to WUR radio and monitor one or more WUR channels (e.g., all applicable WUR channels) during one or more NDP frame transmission periods. After switching to WUR radio and monitoring one or more WUR channels, STA1 and/or STA2 720 may then switch back to the primary wireless.

The AP 701 may perform beamforming using, for example, CQIs measured directly by one or both of STA1 and STA2 720 on one or more WUR channels. One or both of STA1 and STA2 720 may or may not be configured to receive transmissions via multiple WUR channels.

The AP 701 may be in, for example, NDP frame 703 _n After a zIFS duration 709 following the transmission of (b) a trigger frame 704 is transmitted. NDP frame 703 _n May be an NDP frame 703 ₁ ……703 _n Final NDP frames in the set of (a). Trigger frame 704 may request one or more measurements, such as one or more channel state information measurements, from one or both of STA1 and STA2 720. Any type of request for any one or more measurements, and any combination of any one or more measurements, is contemplated herein.

STA1 and STA2 710 and 720 may transmit UL CSI 711 and 721, respectively, to AP 701 in response to trigger frame 704. UL CSI 711 and 721 may be transmitted by STA1 and STA2 720 after the zIFS duration 709 after the transmission of trigger frame 704.

Measurement information, such as UL CSI 721, may include information 732, such as CSI (e.g., which may have been obtained or otherwise determined by WUR monitoring one or more WUR channels). CSI may be monitored by WUR and fed back by PCR. For example, NDP frame 703 ₁ ……703 _n May have allowed and/or instructed STA2 720 to feedback CSI monitored by WUR at 732. Any other measurement and any combination thereof are contemplated herein.

The CSI may include any one or more and/or any combination of time domain CSI determined for narrowband WUR channels, time domain CSI determined for BF weight sets for each of one or more WUR channels, frequency domain CSI determined for narrowband WUR channels, frequency domain CSI determined for BF weight sets for each of one or more WUR channels, and any other type of CSI.

AP 701 may transmit WUR trigger frame 705 to one or both of STA1 and STA2 720 after receiving UL CSI 711 and zIFS duration 709 after UL CSI 721. Alternatively, or in addition, transmission of WUR trigger frame 705 may be performed using a different TXOP than the TXOP that AP 701 previously used to transmit, for example, frames 702, 703, 704.

After receiving the zIFS duration 709 after the WUR trigger frame 705, STA1 and STA2 720 may respond by transmitting WUR signal frames 712 and WUR signal frames 722, respectively, to the AP 701. WUR signal frames 712 and 722 may be transmitted using SU transmissions or MU transmissions, or any combination thereof.

Using the WUR channel, AP 701 may send STA1 WUR1 transmission 706 and STA2 WUR3 transmission 706 to STA1 and STA2 720, respectively, indicating that STA1 710 uses WUR1 and STA2 720 uses WUR3, respectively. The AP 701 may store, obtain, or otherwise determine CSI (e.g., per subcarrier, per x subcarriers) that may have been measured in the time and/or frequency domain on WUR radios of the AP 701. The AP 701 may use 708 the CSI to generate STA1 WUR1 transmissions 706 and/or STA2 WUR3 transmissions 707.

WUR channel estimation may be performed on the primary radio. The AP may learn (e.g., acquire, determine, and/or receive information) the wireless channels associated with WUR radios. Such an AP may use a primary control channel associated with a wireless channel associated with a WUR radio to send WUR channel request packets to STAs (e.g., selected STAs, specific STAs). Such WUR channel request packets may include one or more parameters that may be related to WUR channels. For example, such parameters may include one or more of tap number, WUR configuration information (e.g., one or more WUR scan locations), number of training packets for subsequent transmission, and the like.

The STA may adjust its device configuration to allow the STA to receive signals (e.g., from the AP) over the WUR RF channel. Such STAs may send ACK packets to the AP. The AP may send training packets to the STA over the WUR channel. The STA may estimate a channel, which may be a WUR channel. The STA may send an ACK packet to the AP to indicate that the STA may be ready for the next training packet. The STA may send a feedback packet to the AP. Such feedback packets may include information related to the WUR channel, such as a channel impulse response, one or more channel frequency coefficients over the WUR frequency band, and so on.

The one or more channel selection procedures may select one or more narrowband WUR channels available to the STA from among WUR channels. Fig. 8 illustrates an exemplary channel selection process 800. In process 800, any one or more of NDPA frame 802, NDP frame 803, trigger frame 804, UL CSI frame 811, and UL CSI frame 821 may acquire, receive, or otherwise determine one or more CQIs for one or more WUR channels. WUR parameter configurations may be different from those that may be used in other WLANs. The AP 801 may request an RU-based CQI report at 841. STA2 820 may respond by providing report 831, which may include the results of RU-based CQI monitoring by the primary radio, e.g., via UL CSI frame 821. RU-based CQI reports (e.g., report 831) on the primary radio may be used, for example, by the AP 801 to determine (e.g., calculate) WUR channel quality.

The STA may include an increment factor in the UL CSI report. For example, STA2 802 may include delta factor 851 in UL CSI frame 821. The AP801 may advertise channel WUR allocations 861 for one or more STAs (e.g., for each STA associated with the AP 801), for example, in WUR trigger frame 805. Channel allocation 861 may be determined based on one or more (e.g., estimated) WUR CQI reports and/or one or more delta factors (e.g., delta factor 851). The CQI reports may include SNR, SINR, RSSI, etc. The estimated WUR CQI may be a function of one or more factors, which may include a CQI report for the primary radio, one or more delta factors reported to the AP by one or more STAs (e.g., one or more delta factors 851 reported to the AP801 by STA2820 via UL CSI frame 821), and/or a transmit delta factor at the AP (e.g., AP 801).

After receiving the aIFS duration 809 after the WUR trigger frame 805, STA1 and STA2820 may respond by transmitting WUR signal frames 812 and 822, respectively, to the AP 801. WUR signal frames 812 and 822 may be transmitted using SU transmissions or MU transmissions, or any combination thereof.

One or more selected WUR channels may be allocated to one or more STAs for subsequent transmissions. For example, AP801 may assign channel WUR1 to STA1 810 at 806 and/or channel WUR3 to STA2820 at 807 at 808.

Fig. 9 illustrates an exemplary channel selection process 900 that may not use an increment factor. In process 900, STA1 and/or STA2 910 and/or 920 may acquire, receive, or otherwise determine one or more CQIs for one or more WUR channels. For example, the AP 901 may send one or more requests for monitoring and determining such CQIs for one or more WUR channels via any one or more of the NDPA frame 902, NDP frame 903, and trigger frame 904. The number of NDP frames may be explicitly signaled, for example, in a frame such as NDPA frame 902. Alternatively, or in addition, the number of NDP frames may be implicitly indicated, e.g., where the number of NDP frames may be the same as the number of WUR channels associated with a "normal" WLAN bandwidth.

In response to receiving NDPA frame 902, which may include request 941 for monitoring and determining CQI of one or more WUR channels, one or more recipients of NDPA frame 902 (e.g., recipients such as STA1 910 and STA2 920) may switch to one or more WUR channels, for example, after sending bfs duration 909 after NDPA frame 902. A value of the bsifs duration 909 that is equal to or greater than the radio set handover time may be selected.

WUR STA 910 and/or WUR STA 920 may not be able to monitor and/or receive on multiple WUR channels simultaneously. STA1 910 and/or STA2 920 may monitor one or more WUR channels (e.g., all WUR channels) sequentially (as opposed to simultaneously) during the transmission period of NDP frame 903. One or more receiving STAs (e.g., STA1, STA2 920) may send one or more responses to the request (e.g., request 941) via any one or more of the UL CSI frames. For example, in response to the request 941, which may be included in NDPA frame 902, sta2 920 may feedback a CQI via UL CSI frame 921 at 931. In an example, at 931, the cqi may be monitored by WUR and fed back by PCR. Note that STA1 910 and/or any STA in communication with AP 901 may also or alternatively receive a request for CQI monitoring and perform WUR monitoring and/or generation of CQI reports for WUR channels that may be sent to one or more APs.

STA1 910 and/or STA2 920 may switch back to the primary radio, e.g., after monitoring one or more WUR channels. At 961, the ap 901 may perform channel selection and/or allocation 961 based at least in part on the CQI measured (e.g., directly) on one or more WUR channels. Channel selection and/or allocation 961 may be transmitted to STA1 901 and/or STA2 902 in WUR trigger frame 905.

After receiving the bfs duration 909 after the WUR trigger frame 905, STA1 and STA2 920 may respond by transmitting WUR signal frames 912 and 922, respectively, to the AP 901. WUR signal frames 912 and 922 may be transmitted using SU transmissions or MU transmissions, or any combination thereof.

Fig. 10 illustrates an exemplary channel selection process 1000 that may not use an increment factor. In process 1000, STA1 1010 and/or STA2 1020 may acquire, receive, or otherwise determine one or more CQIs for one or more WUR channels. STA1 1010 and/or STA2 1020 may not be able and/or may not be configured to monitor multiple WUR channels simultaneously. For example, the AP 1001 may transmit one or more requests for monitoring and determining CQI of one or more WUR channels via any one or more of the NDPA frame 1002, NDP frame 1003x, and trigger frame 1004.

The AP 1001 may indicate, for example in the NDPA frame 1002, that multiple NDP frames 1003 may be sent ₁ ……1003 _n Which may instruct and/or allow one or more STAs (e.g., STA1, STA2, 1020) to sequentially (as opposed to simultaneously) switch to and monitor each of the plurality of WUR channels. The number of such NDP frames may be explicitly signaled in a frame such as NDPA frame 1002, for example. Alternatively, or in addition, the number of NDP frames may be implicitly indicated, e.g., where the number of NDP frames may be the same as the number of WUR channels associated with a "normal" WLAN bandwidth. NDP frame 1003 ₁ ……1003 _n One or more of the STAs may indicate 1051 to one or both of STA1 and STA2 1020 that one or both of these STAs may be indicated and/or allowed to perform one or more CQI measurements using multiple WUR channels. Such measurements may be performed sequentially by one or both of STA1 and STA2 1020.

In response to receiving NDPA frame 1002, which may include request 1041 for monitoring and determining CQI for one or more WUR channels, one or more recipients of NDPA frame 1002 (e.g., recipients such as STA1 1010 and STA2 1020) may switch to one or more WUR channels, for example, after a c ifs duration 1009 following transmission of NDPA frame 1002. A value of the caifs duration 1009 that is equal to or greater than the radio set handover time may be selected.

As described above, WUR STA 1010 and/or WUR STA 1020 may not be able to monitor and/or receive on multiple WUR channels simultaneously. STA1 1010 and/or STA2 1020 may be in NDP frame 1003 _x One or more WUR channels (e.g., all WUR channels) are monitored sequentially (as opposed to simultaneously) during the transmission period of (a). One or more receiving STAs (e.g., STA1, STA2 1020) may send one or more responses to the request (e.g., request 1041) via any one or more UL CSI frames. For example, the response may be included in NDPA frame 1002 The star21020 may feed back the CQI via UL CSI frame 1021 at 1031. In an example, at 1031, the cqi may be fed back by the PCR. Note that STA1 1010 and/or any STA in communication with AP 1001 may also or alternatively receive a request for CQI monitoring and may perform WUR monitoring and/or generation of CQI reports that may be sent to one or more STAs.

STA1 1010 and/or STA21020 may switch back to the primary radio, for example, after monitoring one or more WUR channels. At 1061, the ap 1001 may perform channel selection and/or allocation 1061 based at least in part on the CQI measured (e.g., directly) on one or more WUR channels. Channel selection and/or allocation 1061 may be transmitted to STA1 1001 and/or STA21002 in WUR trigger frame 1005.

After receiving the caifs duration 1009 after the WUR trigger frame 1005, STA1 and STA21020 may respond by transmitting WUR signal frames 1012 and 1022, respectively, to the AP 1001. WUR signal frames 1012 and 1022 may be transmitted using SU transmissions, MU transmissions, or any combination thereof.

For example, a transmission rate and/or MCS may be selected or otherwise determined for WUR from a plurality of transmission rates and/or MCSs available in the associated system. Fig. 11 illustrates an exemplary WUR rate selection process 1100. Any combination of NDPA frame 1102, NDP frame 1103, trigger frame 1104, UL CSI feedback frame 1111, and UL CSI feedback frame 1121 may be used to acquire or otherwise determine CQI for one or more channels associated with WUR. WUR parameter configurations may be different from those that may be used in other WLANs. The AP 1101 may request an RU-based CQI report 1141 for the primary radio, which may be used to determine (e.g., calculate) WUR channel quality. The AP 1101 may request RU-based CQI report 1141 via NDPA frame 1102. STA2 1120 may respond by providing CQI results, e.g., via UL CSI frame 1121, which may include the results of RU-based CQI monitoring by PCR at 1131.

STA2 1120 may include one or more delta factors 1151 in UL CSI frame 1121. The AP 1101 may advertise WUR rate allocation 1161 for one or more STAs (e.g., for each STA associated with the AP 1101), for example, in WUR trigger frame 1105. The rate assignment 1161 may be determined based on, for example, one or more of the estimated WUR CQI reports (e.g., CQI results 1131) and/or one or more delta factors (e.g., delta factors 1151). The CQI reports may include SNR, SINR, RSSI, etc. The estimated WUR CQI may be a function of one or more factors, which may include a CQI report for the primary radio, one or more delta factors reported to the AP by one or more STAs (e.g., one or more delta factors 1151 reported to the AP 1101 by STA2 1120 via UL CSI frame 1121), and/or a transmit delta factor at the AP (e.g., AP 1101).

After receiving the dIFS duration 1109 after WUR trigger frame 1105, STA1 and STA2 1120 may respond by transmitting WUR signal frames 1112 and WUR signal frames 1122, respectively, to AP 1101. WUR signal frames 1112 and 1122 may be transmitted using SU transmissions or MU transmissions, or any combination thereof.

One or more selected WUR rates may be assigned to one or more STAs for subsequent transmission. For example, AP 1101 may assign WUR rate 1 to STA1 1110 via STA1 rate 1 frame 1106 at 1108. AP 1101 may assign WUR rate 2 to STA2 1120 via STA2 rate 2 frame 1107 at 1108.

For example, the transmission rate and/or MCS may be selected or otherwise determined for WUR from a plurality of transmission rates and/or MCSs available in the associated system without using an increment factor. Fig. 12 illustrates an exemplary WUR rate selection process 1200 that may not use an increment factor. Any combination of NDPA frame 1202, NDP frame 1203, trigger frame 1204, UL CSI feedback frame 1211, and UL CSI feedback frame 1221 may acquire or otherwise determine CQI for one or more WUR channels. WUR parameter configurations may be different from those that may be used in other WLANs. The AP1201 may request an RU-based CQI report for the WUR radio at 1241, where the report may be used to determine (e.g., calculate) WUR channel quality. The AP1201 may request 1241 an RU-based CQI report via the NDPA frame 1202. STA2 1220 may respond by providing CQI results, e.g., via UL CSI frame 1221, which may include results from RU-based CQI monitoring by the WUR radio at 1231.

In response to receiving the NDPA frame 1202, which may include a request 1241 for monitoring and determining CQI for one or more WUR channels, one or more recipients (e.g., STA1 1210, STA2 1220) of the NDPA frame 1202 may switch to the one or more WUR channels, for example, after an eIFS duration 1209 following transmission of the NDPA frame 1202. A value of eIFS duration 1209 equal to or greater than the radio set switching time may be selected.

STA1 1210 and/or STA2 1220 may monitor one or more WUR channels (e.g., all WUR channels) simultaneously. Alternatively, STA1 1010 and/or STA2 1020 may monitor one or more WUR channels (e.g., all WUR channels) sequentially (as opposed to simultaneously) during the transmission period of NDP frame 1203. One or more responses to one or more requests, such as request 1241, may be transmitted via any one or more of UL CSI frame 1211 and UL CSI frame 1221. For example, in response to such a request, STA2 1220 may feedback CQI (e.g., determined at 1231) via UL CSI frame 1221. Note that STA1 1210 and/or any STA in communication with AP 1201 may also or alternatively receive a request for CQI monitoring and perform WUR monitoring and generate CQI reports.

STA1 1210 and/or STA2 1220 may switch back to the primary radio, e.g., after monitoring one or more WUR channels. At 1261, the ap 1201 may perform rate selection and/or allocation 1261 based at least in part on the CQI measured (e.g., directly) on one or more WUR channels. Rate selection and/or allocation 1261 may be transmitted to STA1 1201 and/or STA2 1202 in WUR trigger frame 1205.

The AP 1201 may announce WUR rate allocation 1261 for one or more STAs (e.g., for each STA associated with the AP 1201), for example, in WUR trigger frame 1205. The rate allocation 1261 may be determined based at least on, for example, estimated WUR CQI results. The CQI reports may include SNR, SINR, RSSI, etc. The estimated WUR CQI may be a function of one or more factors, which may include the CQI results of the primary radio.

After receiving eIFS duration 1209 after WUR trigger frame 1205, STA1 1210 and STA2 1220 may respond by transmitting WUR signal frame 1212 and WUR signal frame 1222, respectively, to AP 1201. WUR signal frames 1212 and 1222 may be transmitted using SU transmissions or MU transmissions, or any combination thereof.

One or more selected WUR rates may be assigned to one or more STAs (e.g., STA1 1210, STA2 1220) for subsequent transmission. For example, the AP 1201 may allocate WUR rate 1 to STA1 1210 via STA1 rate 1 frame 1206 at 1208. AP 1201 may allocate WUR rate 2 to STA2 1210 via STA2 rate 2 frame 1207 at 1208.

Fig. 13 illustrates an exemplary WUR rate selection process 1300 that may not use an increment factor. In process 1300, STA1 1310 and/or STA2 1320 may acquire, receive, or otherwise determine one or more CQIs for one or more WUR channels. STA1 1310 and/or STA2 1320 may not be able and/or configured to monitor multiple WUR channels simultaneously. For example, AP 1301 may transmit NDP frames 1303 via NDPA frame 1302 _x And trigger any one or more of frames 1304 to send one or more requests to monitor, determine, and/or measure one or more CQIs for one or more WUR channels using WUR radios.

The AP 1301 may, for example, indicate in the NDPA frame 1302: multiple NDP frames 1303 may be transmitted ₁ ……1303 _n Which may instruct and/or allow one or more STAs (e.g., STA1 1310, STA2 1320) to sequentially (as opposed to simultaneously) switch to and monitor each of the plurality of WUR channels. For example, such NDP frame 1303 may be explicitly signaled in a frame such as NDPA frame 1302 ₁ ……1303 _n Is a number of (3). Alternatively, or in addition, such NDP frames 1303 may be implicitly indicated ₁ ……1303 _n For example, where the number of NDP frames may be the same as the number of WUR channels associated with a "normal" WLAN bandwidth. NDP frame 1303 ₁ ……1303 _n Any one or more of which may be, for example, via NDP frame 1303 ₁ ……1303 _n One or both of indication 1351STA1 1310 and STA2 1320 to AP 1301 may be indicated and/or allowed to perform one or more CQI measurements using multiple WUR channels. STA1 1310 and/or STA2 1320 may be in NDP frame 1303 _x In (a) and (b)One or more WUR channels (e.g., all WUR channels) are monitored and/or measured sequentially (as opposed to simultaneously) during a transmission period of one or more frames.

In response to receiving NDPA frame 1302, which may include request 1341 for monitoring and determining CQI for one or more WUR channels, one or more recipients of NDPA frame 1302 (e.g., recipients such as STA1 1310 and STA2 1320) may switch to one or more WUR channels, e.g., after a fIFS duration 1309 following transmission of NDPA frame 1302. A value of the fIFS duration 1309 that is equal to or greater than the radio set handoff time may be selected.

One or more receiving STAs (e.g., STA1 1310, STA2 1320) may send one or more responses to the request (e.g., request 1341) via any one or more UL CSI frames. For example, in response to a request 1341 that may be included in NDPA frame 1302, STA2 1320 may feedback, at 1331, a CQI obtained by monitoring one or more WUR channels via UL CSI frame 1321. Note that STA1 1310 and/or any STA in communication with AP 1301 may also or alternatively receive a request for CQI monitoring and/or may perform WUR channel monitoring and/or generation of CQI reports for WUR channels that may be sent to one or more APs.

STA1 1310 and/or STA2 1320 may switch back to the primary radio, for example, after monitoring one or more WUR channels. At 1361, the AP 1301 (e.g., after switching back to the primary radio) may perform rate determination, selection, and/or allocation based at least in part on the CQI measured (e.g., directly) on the one or more WUR channels. The rate determination, selection, and/or allocation at 1361 may be transmitted to STA1 1310 and/or STA2 1320 via WUR trigger frame 1305.

After receiving the fIFS duration 1309 after the WUR trigger frame 1305, STA1 and STA2 1320 may respond by transmitting WUR signal frames 1312 and 1322, respectively, to the AP 1301. Either or both WUR signal frames 1312 and 1322 may be transmitted using SU transmissions, MU transmissions, or any combination thereof.

One or more selected, obtained, or otherwise determined WUR rates may be assigned (e.g., by AP 1301) to one or more STAs (e.g., STA1 1310, STA2 1320) for subsequent transmission. For example, AP 1301 may allocate WUR rate 1 to STA1 1310 via STA1 WUR rate 1 frame 1306 at 1308. AP 1301 may assign WUR rate 2 to STA2 1320 via STA2 WUR rate 2 frame 1307 at 1308.

Note that while some aspects set forth herein describe performing one or more of the disclosed functions (e.g., channel sounding) using NDPA, NDP, trigger, WUR trigger, and/or other CSI feedback frame exchanges over the primary radio and/or WUR radio, any other scheme, exchange, and procedure consistent with the present disclosure may be contemplated.

Fig. 14 illustrates an exemplary wake-up process 1400.STA1 may initially be in the "on" period 1411 of the duty cycle period 1431. STA1 1410 may enter the "off period 1421, for example, when the" off period 1421 of the applicable duty cycle arrives. While in the "off period 1421, the STA may switch to" on "to monitor WUR beacon transmissions 1412. When in the "off period 1421, the STA may switch to" on "at 1413 due to the content in the received WUR beacon.

The AP 1401 may transmit a WUR beacon 1402 during a beacon interval 1451. WUR beacon field 1405 of WUR beacon 1402 may indicate that all STAs receiving WUR beacon 1402 remain "active (up)" (e.g., "awake") during the next beacon interval 1451. The multicast/broadcast WUR frame 1403 may be transmitted during a beacon interval 1451.

STA1 may obtain, acquire, or otherwise determine a configuration of WUR beacon interval 1451 and/or a configuration of WUR duty cycle via, for example, WUR action frames that may be received from an AP (such as AP 1401). WUR action frames may be transmitted using a Primary Connection Radio (PCR). STA1 may switch to WUR based on a configuration received, for example, via WUR action frames.

STA1 may monitor WUR beacons when STA1 1410 may be in the "off" period of the duty cycle. STA1 may detect and/or receive WUR beacon 1402.WUR beacon 1402 may include an indication and/or instruction in, for example, field 1405 that one or more WUR STAs (e.g., all WUR STAs) including WUR STA1 1410 are to remain "awake" for the duration of WUR beacon interval 1451 and/or for a period of time following transmission and/or reception of WUR beacon frame 1402.

WUR beacon interval 1451 and/or time periods following transmission and/or reception of WUR beacon frame 1402 may be predefined and/or preconfigured. The period 1451 of WUR beacon interval and/or the period following transmission and/or reception of WUR beacon frames 1402 may alternatively or additionally be determined dynamically, e.g., as needed, using any applicable criteria. The period of WRU beacon interval 1451 and/or the period of time following transmission and/or reception of WUR beacon frame 1402 may be indicated in WUR beacon frame 1402. The period of WRU beacon interval (e.g., beacon interval 1451) and/or the period of time following transmission and/or reception of WUR beacon frames (e.g., WUR beacon frame 1452) may be indicated using one or more WUR action frames.

The time period following transmission and/or reception of WUR beacon frames 1402 may be predetermined and/or preconfigured. Alternatively or additionally, a time period following transmission and/or reception of WUR beacon frame 1402 may be signaled in a WUR beacon frame, such as WUR beacon frame 1402. Alternatively or additionally, the time period following transmission and/or reception of WUR beacon frames 1402 may be negotiated using, for example, one or more WUR action frames received and/or transmitted via PCR.

STA1 may remain awake for at least WUR Beacon Interval (BI) 1451 and/or for a period of time following transmission and/or reception of WUR beacon frames 1402. STA1 may receive or expect to receive at least one broadcast and/or multicast frame, for example, during WUR beacon interval 1451 or during a period following transmission and/or reception of WUR beacon frame 1402.

If STA1 1410 receives WUR beacon frames 1402 and STA1 is the intended recipient (e.g., one of the intended recipients), STA1 1410 may operate using PCR and may enter an "on" state at 1413 in response to WUR beacon frames 1402.

STA1 1410 may continue to operate in a duty cycle mode in which it operates before receiving WUR beacon frames 1402. STA1 may remain awake to receive one or more WUR beacons and/or monitor the period of time for subsequent WUR BI may not be counted, recorded, or otherwise recorded as the "on" duration of the duty cycle. Thus, such a period of time may have no impact on the duty cycle associated with STA1 1410.

CSI and/or beamforming related information may be used to perform closed loop transmission. Such information may change over time. The duration may be referred to as, for example, "cl_parameter_valid_duration," which may indicate whether one or more CSI and/or beamforming related parameters are valid. The AP and/or STA may operate a timer that may be started when CSI and/or beamforming related information is set and/or reset. If the value of such timer becomes greater than the value of cl_parameter_valid_duration, one or both of the AP and STA may determine that CSI and/or beamforming-related information is invalid. If one or both of the AP and STA determines that the CSI and/or beamforming related information is invalid, updated CSI and/or beamforming related information may be acquired, requested, or otherwise obtained. The cl_parameter_valid_duration value may be predetermined, predefined, and/or configurable. The cl_parameter_valid_duration value may be signaled in one or more WUR negotiation frames, WUR beacon frames, PCR control/management frames (e.g., PCR beacon frames), and so forth.

Fig. 15 illustrates a diagram representative of an exemplary method 1500. At block 1510, the sta may acquire, obtain, or otherwise determine a configuration that may indicate WUR beacon intervals. Additionally, or alternatively, at block 1510, the sta may acquire, obtain, or otherwise determine configuration and/or other information associated with the WUR duty cycle. For example, the STA may receive a WUR action frame from the AP, which may contain an indicator of WUR beacon interval and/or information associated with WUR duty cycle. Based on one or both of WUR beacon interval information and information associated with WUR duty cycles, the STA may switch to WUR.

At block 1520, the STA may monitor WUR beacons, for example, even when such STA may be in an "off" period of the duty cycle. At block 1530, the STA may determine whether it has detected and/or received a WUR beacon, which may include an indication and/or instructions that one or more WUR STAs (e.g., all WUR STAs) are to remain "awake" for the duration of a WUR beacon interval and/or for a period of time following transmission and/or reception of such WUR beacons. If at block 1530 the STA may determine that it did not detect and/or receive WUR beacons, which may include an indication and/or instruction that one or more WUR STAs (e.g., all WUR STAs) remain "awake" for the duration of a WUR beacon interval and/or for a period of time following transmission and/or reception of such WUR beacons, the method 1500 may return to block 1520 and continue monitoring for beacons.

If at block 1530 the STA may determine that it has detected and/or received a WUR beacon, which may include an indication and/or instruction that one or more WUR STAs (e.g., all WUR STAs) remain "awake" for the duration of a WUR beacon interval and/or for a period of time following transmission and/or reception of such WUR beacon, then at block 1540 the STA may "wake up" and remain "awake" for the determined duration (e.g., the duration of the beacon interval, the determined period of time, etc.), e.g., even during an "on" period of the WUR duty cycle prior to (e.g., immediately prior to) receiving the WUR beacon, and may be expected to return to an "off" period of the WUR duty cycle after (e.g., immediately after) receiving the WUR beacon.

If the STA determines at block 1530 that it did not detect and/or did not receive WUR beacons, which may include an indication and/or instructions that one or more WUR STAs (e.g., all WUR STAs) remain "awake" during a WUR beacon interval and/or for a period of time following transmission and/or reception of such WUR beacons, the STA may return to block 1520 to continue operating in the duty cycle mode in which it was operating.

The period of time that the STA may remain awake to receive one or more WUR beacons and/or monitor a subsequent WUR BI (or any other duration that the STA may remain awake to receive one or more beacons WUR and/or monitor a subsequent WUR BI) may not be counted, recorded, or otherwise noted as the "on" duration of the duty cycle. Such a period of time may have no impact on the duty cycle associated with such STAs.

Note that any period of time that a STA may remain awake may be predefined, preconfigured, determined dynamically (e.g., as needed) using any applicable criteria, signaled using WUR beacon frames, negotiated using one or more WUR action frames (e.g., through use of PCR), etc. All such examples are contemplated herein.

At block 1550, the sta may determine whether it has received a WUR frame since it was "awakened" at block 1540. If not, the STA may return to block 1520 and continue to monitor for beacons and remain in the same duty cycle. If the STA determines that it has received a WUR frame since it was "awakened" at block 1540, the STA may activate its PCR and begin using the PCR at block 1560. After its PCR activation, the STA may maintain, replace, and/or discard any WUR duty cycle settings, e.g., depending on WUR negotiations between the AP and the STA before the STA may enter WUR mode.

Fig. 16 illustrates an exemplary wake-up process 1600. Process 1600 may employ repeated multicast and/or broadcast frames, any one or more of which may include a Multicast Counter (MC) value.

The STA (e.g., STA1 1610, STA2 1620) may maintain and/or record the MC value, which may be initially set to "invalid" by the AP, for example. STA1 1610 and/or STA2 1620 may be in a duty cycle mode in WUR. The AP may send a broadcast/multicast wakeup frame and may repeat the transmission multiple times so that a STA in duty cycle mode may have the opportunity to receive one of such broadcast/multicast wakeup frame transmissions. In a broadcast/multicast wakeup frame, there may be a field that may indicate whether the frame is a "new" transmission or a repetition of a previously transmitted broadcast/multicast wakeup frame. This field may include or indicate a Multicast Counter (MC) value. For "new" transmissions (e.g., transmissions that may use a different receive group or wake-up cause than that used in previous (e.g., immediately previous) transmissions), STA1 1610 and/or STA2 1620 may desire to detect an increased, decreased, or otherwise changed MC value. For repeated transmissions (e.g., transmissions that may use the same reception group or wake-up cause as was used in a previous (e.g., immediately previous) transmission), STA1 1610 and/or STA2 1620 may expect to detect unchanged MC values. Before the STA can enter WUR mode, it can receive the current MC counter value from the AP, e.g., during a WUR negotiation process and/or in WUR suspended mode. Such MC counter values may be indicated in one or more WUR response values.

STA1 1610 and/or STA2 1620 may receive multicast/broadcast WUR frame 1601, which may include MC value 1641, which may be 0. STA1 1610 and/or STA2 1620 may receive frame 1601 during respective "on" periods of 1611 and 1621, STA1 duty cycle period 1671, and STA2 duty cycle period 1672, respectively. STA1 1610 and/or STA2 1620 may each determine whether to "wake up" based on comparing the MC value 1641 with maintained MC values stored by STA1 1610 and/or STA2 1620, respectively. Because the value of the MC counter may change, the STA receiving the wake-up frame may use one or more current and/or incremented future counter values to evaluate whether the frame receiving the WUR is destined for its own BSS WUR by adding an embedded BSSID field and/or one or more GIDs and/or TIDs associated with the STA. Such STAs may evaluate whether FCS or CRC in WUR frames can be properly verified. For example, if the currently stored MC value is N, the WUR STA in the WUR mode may insert the value N N N+m into the MC value field, where m may be equal to or greater than 1, and evaluate whether the FCS/CRC may be properly verified. The value m may be indicated by the AP and may be included in WUR response frames during a WUR negotiation process or in WUR suspended mode, or may be included in WUR operation elements or other elements, e.g., in beacons and/or WUR beacons. The value of m may be based on how much time may have elapsed since the WUR STA received a WUR frame from its AP. WUR packets may be considered valid if FCS/CRC can be verified and meaningful to STA BSS and/or WID/GID.

If one or both of STA1 1610 and STA2 1620 have a maintained MC value, which may be the same value as MC value 1641, then the corresponding STA having a stored MC value that matches MC value 1641 may not wake up. If one or both of STA1 1610 and STA2 1620 have a maintained MC value, which may not be the same value as MC value 1641, then the corresponding STA having a stored MC value that is different from MC value 1641 may update the stored MC value to MCs value 1641, wake up and/or activate its PCR (e.g., STA1 switches to PCR 1651, STA2 switches to PCR 1661).

One or more STAs may maintain WUR duty cycle settings unless the AP updates such settings, for example, when the STAs may use PCR. When these STAs switch to PCR, they may start a PCR timer to keep track of the duration of time that these STAs remain on the PCR. When the PCR timer becomes greater than a predefined, predetermined, and/or configured threshold, the corresponding STA may determine to remain in the PCR for a relatively long duration, and the parameters set by the WUR may no longer be considered valid.

When the MC value transmitted in the WUR frame is different from the MC value stored at the STA receiving such frame, the receiving STA may update its MC value by storing the MC value received in the WUR frame instead of its current MC value, thereby making the stored MC value the same as the MC value received in the WUR frame.

When the MC value transmitted in WUR frames is different from the MC value stored at the STA receiving such frames, the receiving STA may activate or switch to PCR (e.g., 1651, 1661) and may start a PCR timer. For example, the MC value 1641 may be different from the MC value stored by STA1 1610, and in response, STA1 1610 may switch to PCR 1651. In such examples, STA1 1610 may use PCR for a relatively short duration before the PCR timer expires and may again switch back to WUR during STA1 duty cycle period 1671 and continue into WUR duty cycle "off period 1612 and/or save the MC value 1641 as its stored MC value. STA1 1610 may enter WUR duty cycle "on" period 1613 and receive another multicast WUR frame 1603 with MC value 1643. STA1 1610 may compare the MC value 1643 with its stored MC value and may determine that the MC value is different. In this case, STA1 1610 may switch to PCR 1652.

STA2 1620 may use a different WUR duty cycle setting than STA1 1610. In response to multicasting WUR frame 1601, sta2 1620 may update its recorded MC value and switch to PCR 1661. Then, before the PCR timer expires, it may switch back to WUR and continue to use WUR duty cycle. STA2 1620 may receive multicast WUR frame 1602 with MC value 1642. STA2 1620 may compare MC value 1642 to its stored MC value and may determine that the MC values are the same. Thus, STA2 1620 may not switch to PCR 1662.

If a STA switches from PCR to WUR, this STA may stop its PCR timer and compare its PCR timer to a threshold (e.g., may be referred to as "pcr_timer_threshold"). If the STA determines that its PCR timer is greater than pcr_timer_threshold, the STA may set its stored MC value to invalid (e.g., if the STA may remain using PCR for a longer duration than the AP uses in the transmission of repeated broadcast and/or multicast frames). If the STA determines that its PCR timer is not greater than pcr_timer_threshold, the STA may keep its stored MC value unchanged.

STA1 1610 may not receive or otherwise interpret the multicast WUR frame 1602, for example, because STA1 1610 may be in WUR duty cycle "off" mode 1612.

STA2 1620 may receive or otherwise interpret multicast WUR frame 1602 and, for example, determine that MC value 1642 is not different from the MC value stored by STA2 1620 (e.g., where STA2 1620 sets its MC value to 0 in response to multicast WUR frame 1601 and MC 1642 may be 0), and thus STA2 1620 may not switch to PCR 1662. At the end of the STA2 period 1672, the STA2 1620 may enter an "on" mode 1623 and begin another duty cycle period, entering an "off" mode 1624 after the "on" mode 1623. After the period of the "off" mode 1624, STA2 1620 may enter an "on" mode 1625.STA2 1620 may enter an "on" mode 1625, receive the multicast WUR frame 1643, determine that the MC value 1603 is different from the MC value stored by STA2 1620 (e.g., where STA2 1620 still has its MC value set to 0 in response to the multicast WUR frame 1601 and MC1643 may be 1), and in response, STA2 may switch to PCR at 1663.

A BSS parameter update counter (BPUS) may be used in WUR frames to indicate whether WUR STAs in WUR mode need to wake up to learn of the basic BSS-wide parameter updates. Since the value of BPUS may change, the STA receiving the wake-up frame may need to use the current and/or incremented future counter values to evaluate whether the received WUR frame is destined for its own BSS by adding the embedded BSSID field and/or WID, GID and/or TID of the STA, and to evaluate whether the FCS or CRC in the WUR frame can be properly verified. For example, if the currently stored BPUS value is N, a WUR STA in WUR mode may need to insert the value N N N+m into the BPUS value field, where m may be equal to or greater than 1, and evaluate whether FCS/CRC may be properly verified for the received WUR frame. The value m may be indicated by the AP, which may be included in WUR response frames during a WUR negotiation process or in WUR suspended mode, or may be included in WUR operation elements or other elements in beacons and/or WUR beacons. The value m may depend (e.g., also depend) on how long has elapsed since the WUR STA received the WUR frame from its AP. WUR packets may be considered valid if FCS/CRC validation passes and meaningful to the STA's BSS and/or WID/GID.

The partial TSF field may be included in a WUR frame, e.g., a WUR beacon frame, e.g., to keep WUR STAs in WUR mode, synchronized until the TSF timer. As the value of the Partial TSF (PT) may change, the STA receiving the wakeup frame may need to use the current and/or increased future TP values to evaluate whether the received WUR frame is destined for its own BSS by adding the embedded BSSID field and/or WID, GID and/or TID of the STA, and to evaluate whether the FCS or CRC in the WUR frame can be properly verified. For example, if the current expected value of PT is N, then a WUR STA in WUR mode may need to insert the value N-l N N+m into the TP value field and evaluate whether FCS/CRC can be properly verified for the received WUR frame, where m and l may be equal to or greater than 1. The values m and/or l may be indicated by the AP, which may be included in WUR response frames during a WUR negotiation process or in WUR suspended mode, or may be included in WUR operation elements or other elements in beacons and/or WUR beacons. The values of m and/or l may depend (e.g., also depend) on how long has elapsed since the WUR STA received WUR frames from its AP. WUR packets may be considered valid if FCS/CRC validation passes and meaningful to the STA's BSS and/or WID/GID.

In an example, the partial TSF field may not be included in the process of verifying FCS/CRC of WUR frames. For example, when a WUR STA in WUR mode receives a WUR frame, it may exclude a partial TSF field and insert into the embedded BSSID field and evaluate whether FCS/CRC of the received WUR frame can be properly verified.

Examples of verifying the FCS/CRC of the WUR frame may include one or more of the following. If a WUR frame is detected, WUR STA may need to evaluate the potential value N of K variable fields for K variable fields in WUR as part of FCS/CRC evaluation _k –l _k ≤n _k ≤N _k +m _k Wherein N is _k Is the stored current or expected value of the kth variable field, l _k And/or m _k May be equal to or greater than 0, may be indicated by the AP, may be included in WUR response frames during a WUR negotiation process or in WUR suspended mode, or may be included in WUR operation elements or other elements in beacons and/or WUR beacons. The values of m and/or l may also depend on how long has elapsed since the WUR STA received a WUR frame from its AP. WUR STAs may use these potential values of the K variable fields and/or insert into the embedded BSSID field and evaluate whether the FCS/CRC of the received WUR frame may be properly verified, in which case one or more variable fields, e.g., part of the TSF field, may be ignored. WUR packets may be considered valid if FCS/CRC validation passes and meaningful to the STA's BSS and/or WID/GID. Some examples N _k The value may include a TID (transmitter ID), a WID (wake ID), and/or one of a plurality of GIDs (group IDs) assigned to or associated with WUR STAs. In an example, N _k May be a start/end GID of a group to which WUR STAs belong and may be assigned to WUR STAs. The AP may indicate l for GID range _k And/or m _k And/or N indicating the group(s) to which the WUR STA belongs _k 。

One or more parameters that may be used in the disclosed aspects (e.g., the number of repeated broadcast and/or multicast frames (e.g., may be referred to as "n_repeat"), the duration during which repeated broadcast and/or multicast frames may be transmitted (e.g., may be referred to as "t_repeat"), the maximum number of pcr_timer_threshold, MC values (e.g., may be referred to as "MCmax")) may be predefined or predetermined, and/or may be signaled. Any one or more such parameters may be signaled in one or more WUR action frames and/or in any other type of frame that may be used for WUR parameter negotiation using, for example, PCR. The parameters may also or alternatively be signaled using, for example, WUR in one or more WUR beacon frames and/or in any other type of frame that may be used as a WUR broadcast and/or multicast frame. The parameters may be signaled using control/management frames (e.g., PCR beacon frames) sent by PCR. Parameter comparisons, such as determining whether PCR_timer_threshold is greater than or equal to T_repeat and determining whether N_repeat is less than or equal to MCmax, may be used in determining parameters.

The maximum MC value (MCmax) may be determined by the number of bits allocated to signal the MC value. For example, the AP may determine and use an increased MC value for new multicast and/or broadcast WUR frame transmissions (e.g., mc_new=mod (mc_old+1, MCmax). When two bits are used to signal the MC value, e.g., the potential MC value may be [0,1,2,3], the AP may set the MC value (e.g., the MC value may be set each time it generates a new WUR multicast/broadcast frame for transmission) to mc_new=mod (mc_old+1, 4). In this example, mcmax=4.

Fig. 17 illustrates an example method 1700 for using MC values with APs and STAs in a repeated multicast and/or broadcast frame scenario. At block 1710, the STA may (e.g., initially) set its stored MC value to invalid. Such STAs may be in WUR mode. In one case, the STA may be in WUR duty cycle mode. At block 1720, the STA may monitor the WUR signal during one or more "on" periods of the duty cycle. In block 1730, the sta may receive broadcast and/or multicast WUR frames. The STA may determine that it may be the intended recipient of such a frame. The received broadcast and/or multicast WUR frame may include an MC value.

At block 1740, the STA may compare the MC value in the received WUR frame with the MC value stored by the STA. If the MC values are the same, the STA may determine that the received WUR frame may be a repetition of a WUR frame received earlier at the STA. In response, the STA may determine not to wake up in response to the received WUR frame. Such STAs may remain in the WUR and continue their duty cycle at block 1750 and return to block 1720 to monitor for additional WUR signals.

If the STA determines that the MC value in the received WUR frame is not the same as the STA stored MC value at block 1740, the STA may re-encode its MC value to be the same as the MC value included in the received WUR frame at block 1745. In block 1755, the sta may switch to PCR operation and start a PCR timer. At block 1765, the STA may stop the PCR timer due to any criteria set forth herein, such as determining that the PCR timer expires, is greater than a predefined, predetermined, or otherwise determined threshold, etc., or the STA may not be in the PCR mode of operation. At block 1765, the sta may begin operating in WUR mode again.

At block 1775, the sta may compare its (e.g., stopped) PCR timer to a predefined, predetermined, or otherwise determined threshold (e.g., pcr_timer_threshold). At block 1775, the sta may determine that its PCR timer is greater than the value of such threshold, and in response, may change its stored MC value to invalid at block 1790, and may return to block 1720 to monitor for additional WUR signals. At block 1775, a value may be determined whose PCR timer is not greater than such a threshold, and in response, its stored MC value may be kept unchanged at block 1785, and a return may be made to block 1720 to monitor for additional WUR signals.

Any one or more parameters described herein, such as the number of repeated broadcast and/or multicast frames (n_repeat), the transmission duration of such repeated frames (t_repeat), pcr_timer_threshold, the maximum value of the MC value (MCmax), etc., may be predefined, predetermined, signaled, or otherwise determined using one or more WUR action frames and/or any other type of frame or frames that may be used for WUR parameter negotiation on PCR. Any one or more of such parameters described herein may be predefined, predetermined, signaled, or determined using one or more WUR beacon frames and/or other WUR broadcast and/or multicast frames on WUR. Any one or more of such parameters described may follow rules such as pcr_timer_threshold > = t_repeated and/or n_repeated < = MCmax.

Fig. 18 illustrates an exemplary method 1800 that may be implemented by an AP and that may use MC. At block 1810, the ap may determine multicast information that may be transmitted to one or more STAs. At block 1820, the ap may transmit such information in broadcast and/or multicast WUR frames. In an example, the AP may repeatedly transmit the same broadcast and/or multicast WUR frame over a period of time. The new frame (e.g., an initial frame in a sequence of repeatedly transmitted frames) may include MC having a different value than one or more previously transmitted frames. The subsequent frame may include MC having the same value as MC included in the initial frame or the new frame.

Fig. 19 illustrates an example method 1900 that may be implemented by a STA and that may use MC. At block 1910, the STA may receive a multicast frame, which may have a MC value different from the MC value stored by the STA. In block 1920, the sta may change its MC value to the MC value included in the received frame, and may store the updated MC value. At block 1930, the sta may begin PCR operations and may start a PCR timer. In block 1940, the STA may stop its PCR timer, e.g., due to the PCR timer expiring or meeting or exceeding a threshold, or due to the STA entering WUR operation. In block 1950, the sta may begin WUR operation. In block 1960, the STA may set its MC value to invalid if its PCR timer expires or meets or exceeds a threshold. If the STA's MC value is already invalid, such STA may keep its MC value unchanged.

Fig. 20 illustrates an exemplary method 2000 that may be implemented by a STA and may use MC. In block 2010, the STA may receive a multicast frame, which may have the same MC value as the STA stored. The same MC value may indicate that the received frame is the same as one or more frames that have been received (e.g., received immediately prior to the most recently received frame). The sta may change its MC value to the MC value included in the received frame at block 1920 and may store the updated MC value, and the sta may begin PCR operations and may start a PCR timer at block 1930. At block 2020, the sta may maintain WUR operation and continue the duty cycle.

STAs sharing the same WUR group ID may have a synchronized duty cycle. STAs in the synchronized duty cycle may have the same duty cycle period and the same "on" duration. STAs in the synchronized duty cycle may each begin their "on" duration at the same time.

STAs with the same WUR group ID may enter WUR mode in different time slots. To synchronize the STAs with their duty cycles, the duty cycle period may be an integer (e.g., a multiple) of the WUR beacon interval. The "on" duration of the duty cycle period may be allocated at the beginning of the period. STAs belonging to the same WUR group (e.g., all STAs synchronized or to be synchronized) may have the same duty cycle period or different duty cycle periods.

The start times of the duty cycles may be synchronized. A partial Timing Synchronization Function (TSF) timer may be carried in WUR beacons (e.g., in each WUR beacon). The partial TSF may be used to synchronize the start time of the duty cycle. One or more STAs (e.g., all STAs synchronized or to be synchronized) that may each belong to the same WUR group may have the same duty cycle period T. The start time of the duty cycle may be the time when the partial TSF is equal to an integer multiple of T.

One or more STAs (e.g., all synchronized or to be synchronized STAs) that may each belong to the same WUR group may have different duty cycle periods T _k Where K ε {1,2, …, K } and K is the total number of STAs in such a group. T may be defined as { T } _k The least common multiple of k=1, …, K }. The start time of the duty cycle may be the time when the partial TSF is equal to an integer multiple of T.

When the partial TSF is equal to an integer multiple of T, broadcast and/or multicast frames may be sent to the group.

When the partial TSF may be equal to an integer multiple of T plus a delay D (e.g., mt+d), broadcast and/or multicast frames may be sent to the group. Delay D may be set to tolerate timing errors between STAs.

WUR group ID and duty cycle negotiations may be exchanged between the AP and one or more STAs through PCR. Duty cycle negotiation may be performed using WUR action frames and/or any other type of control and/or management frames.

In an example, WUR Group ID (GID) may have implications for the behavior of a group of STAs to be awakened. A particular GID in the wake-up frame may mean that the group-addressed PCR packets are buffered at the AP and the STA should wake up to retrieve the group-addressed packets using its PCR. The particular GID in the wake-up frame may suggest: the group of STAs that are being awakened are (e.g., all) MU-capable STAs, and when awakened using their PCR, the STAs may access using MU medium. The particular GID may suggest that STAs should wake up and wait for a trigger frame to send a trigger-based PPDU to the AP using their PCRs. A particular GID may suggest that STAs should wake up and use their PCRs for traditional medium access, such as EDCF, contention-based medium access. The function and meaning of the GID may be indicated in frames, e.g., WUR response frames, WUR action frames, which may be communicated using PCR, e.g., during WUR negotiation process and/or WUR suspended mode. In the above example, the GID is used as an example and may be replaced by a WID, TID, or any other field or subfield in the wakeup frame.

Although features and elements are described herein with reference to examples and/or particular combinations of examples illustrated and described, each feature or element can be used alone without the other features and elements described herein or in various combinations with or without other features and elements described.

Although the examples described herein consider 802.11 specific protocols, it should be understood that the examples described herein are not limited to those protocols and are also applicable to other wireless systems.

Although SIFS is used to indicate various inter-frame intervals in the example, all other inter-frame intervals such as RIFS or other agreed time intervals may be applied.

The processes described above may be implemented in a computer program, software and/or firmware incorporated in a computer readable medium for execution by a computer and/or processor. Examples of computer readable media include, but are not limited to, electronic signals (transmitted over wired and/or wireless connections) and/or computer readable storage media. Examples of computer readable storage media include, but are not limited to, read Only Memory (ROM), random Access Memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media such as, but not limited to, internal hard disks and removable disks, magneto-optical media, and/or optical media such as CD-ROM disks and/or Digital Versatile Disks (DVDs). A processor associated with the software may be used to implement a radio frequency transceiver for use in a WTRU, a terminal, a base station, an RNC, and/or any host computer.

Claims (12)

1. A method performed by a station STA, the method comprising:

operating a wake-up radio WUR to receive a WUR frame from an access point AP, wherein the WUR frame comprises an MC field indicating a multicast counter MC value and at least one field indicating a destination address; and

when the received MC value is a different value than the stored MC value, and when the received MC value and the destination address verify that the STA is the intended recipient of the WUR frame, a primary connection radio PCR is activated to receive a beacon frame from the AP.

2. The method of claim 1, wherein the STA is operating in a duty cycle.

3. The method of claim 2, wherein the STA is operating in a shutdown period of the duty cycle.

4. The method of claim 2, further comprising activating the WUR to receive WUR frames in response to a determination that the received MC value is the same value as the stored MC value.

5. The method of claim 2, wherein the duty cycle is synchronized with a duty cycle of another STA.

6. The method of claim 2, further comprising continuing to operate in the duty cycle in response to the determination that the received MC value is the same value as the stored MC value.

7. A station STA, the STA comprising:

a processor configured to:

operating a wake-up radio WUR to receive a WUR frame from an access point AP, wherein the WUR frame comprises an MC field indicating a multicast counter MC value and at least one field indicating a destination address;

the processor is configured to:

when the received MC value is a different value than the stored MC value, and when the received MC value and the address verify that the STA is the intended recipient of the WUR frame, a primary connection radio PCR is activated to receive a beacon frame from the AP.

8. The STA of claim 7, wherein the STA operates in a duty cycle.

9. The STA of claim 8, wherein the STA operates in an off period of the duty cycle.

10. The STA of claim 8, wherein the processor is further configured to activate the WUR to receive WUR frames in response to a determination that the received MC value is the same value as the stored MC value.

11. The STA of claim 8, wherein the duty cycle is synchronized with a duty cycle of another STA.

12. The STA of claim 8, wherein the processor is further configured to continue operating in the duty cycle in response to the determination that the received MC value is the same value as the stored MC value.

Images