WO2019027511A1

WO2019027511A1 - Location measurement report feedback schedule in wireless communications

Info

Publication number: WO2019027511A1
Application number: PCT/US2018/025388
Authority: WO
Inventors: Chittabrata GHOSH
Original assignee: Intel IP Corporation
Priority date: 2017-07-31
Filing date: 2018-03-30
Publication date: 2019-02-07

Abstract

This disclosure describes systems, methods, and devices related to location measurement report (LMR) feedback schedule in wireless communications. A device may cause to send a measurement polling request to one or more station devices. The device may identify one or more responses to the measurement polling request from at first subset of the one or more station devices. The device may determine a trigger frame comprising one or more fields to notify the first subset of the one or more station devices of one or more resource units. The device may set a location measurement report (LMR) feedback indication in the trigger frame. The device may cause to send the trigger frame to the first subset of the one or more station devices.

Description

LOCATION MEASUREMENT REPORT FEEDBACK SCHEDULE IN WIRELESS

COMMUNICATIONS

CROSS-REFERENCE TO RELATED APPLICATION(S)

[0001] This application claims the benefit of U.S. Provisional Application No. 62/539,313, filed July 31, 2017, the disclosure of which is incorporated herein by reference as if set forth in full.

TECHNICAL FIELD

[0002] This disclosure generally relates to systems, methods, and devices for wireless communications and, more particularly, location measurement report (LMR) feedback schedule in wireless communications.

BACKGROUND

[0003] Wireless devices are becoming widely prevalent and are increasingly requesting access to wireless channels. The Institute of Electrical and Electronics Engineers (IEEE) is developing one or more standards that utilize Orthogonal Frequency-Division Multiple Access (OFDMA) in channel allocation.

BRIEF DESCRIPTION OF THE DRAWINGS

[0004] FIG. 1 depicts a diagram illustrating an example network environment of illustrative location measurement report (LMR) feedback schedule system, in accordance with one or more example embodiments of the present disclosure.

[0005] FIG. 2 depicts an illustrative schematic diagram for polling, measurement, and LMR feedback in one availability window.

[0006] FIG. 3 depicts an illustrative schematic diagram for LMR feedback schedule, in accordance with one or more example embodiments of the present disclosure.

[0007] FIG. 4 depicts an illustrative schematic diagram for LMR feedback schedule, in accordance with one or more example embodiments of the present disclosure.

[0008] FIG. 5A depicts a flow diagram of illustrative process for a LMR feedback schedule system, in accordance with one or more embodiments of the disclosure.

[0009] FIG. 5B depicts a flow diagram of illustrative process for a LMR feedback schedule system, in accordance with one or more embodiments of the disclosure.

[0010] FIG. 6 depicts a functional diagram of an example communication station, in accordance with one or more example embodiments of the present disclosure. [0011] FIG. 7 depicts a block diagram of an example machine upon which any of one or more techniques (e.g., methods) may be performed, in accordance with one or more example embodiments of the present disclosure.

DETAILED DESCRIPTION

[0012] The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of other embodiments. Embodiments set forth in the claims encompass all available equivalents of those claims.

[0013] In the specification of 802.1 lax, a trigger frame is defined for uplink (UL) multiuser operation using OFDMA. Upon reception of a trigger frame, station devices (STAs) that have been assigned resource units (RUs) indicated in the trigger frame may perform time, frequency offset, and power corrections with respect to the access point's (AP) clock, frequency offset, and transmit power, respectively. Following short inter-frame space (SIFS) time, these designated STAs send their UL A physical layer convergence protocol data units (PPDUs) in multiuser (mu) format, termed as high-efficiency trigger-based PPDUs. The AP might schedule the location measurement report (LMR) feedback within the same service period (SP) / transmit opportunity (TXOP) or in a separate TXOP / service period. However, the measurement phase might consist of a single UL sounding phase (comprising of a single trigger frame requesting UL null data packet (NDP) frames from a set of STAs) or several UL sounding phases (comprising of a sequence where each sequence consists of a single trigger frame requesting UL NDP frames from a set of STAs).

[0014] The AP may decide to schedule LMR feedback either within the same TXOP / service period or in a different TXOP / SP. However, this is unknown to STAs that have participated in the measurement phase. Due to this ambiguity, the STAs that have participated in the measurement phase have to decode each of the following trigger frames to know whether LMR feedback is requested by the AP in this TXOP / SP. This raises the problem of power inefficiency, since prior knowledge after participation in measurement phase would enable the STAs to enter doze state, provided the AP does not intend to schedule trigger frames for LMR feedback.

[0015] Example embodiments of the present disclosure relate to systems, methods, and devices for LMR feedback schedule. [0016] In one embodiment, the LMR feedback schedule system may facilitate that an AP may perform polling with one or more station devices. The polling performed by the AP is to determine whether a station device is interested in performing location measurement.

[0017] After the polling, the AP would enter a measurement phase, where the AP may send a trigger frame that solicits from one or more station devices their uplink NDP frames. The one or more station devices that have been polled by the AP during the measurement polling phase, may not all be solicited with the trigger frame. In other words, a subset of the one or more station devices that were polled may be solicited by the trigger frame. This Trigger frame can be a polling Trigger frame, an UL sounding Trigger frame, or any variant of the Trigger frame.

[0018] The solicited station devices may then send their uplink NDP frames to the AP. It should be understood that there may be additional measurement phase(s), where the AP may send another trigger frame soliciting the station devices for their uplink NDPs and so on.

[0019] After the measurement phase(s), the AP may initiate an LMR feedback from the AP to the STA. In the LMR feedback phase, the AP indicates the location associated with the solicited station devices based on all the received uplink NDPs received from the solicited station devices during the measurement phase(s).

[0020] The solicited station devices may send their own LMR feedback to the AP indicating they are known location. This LMR feedback from the station device to the AP may be an optional phase.

[0021] The NDP is a packet that does not include MAC frame and only a PHY preamble. The NDP is included in the long training field (LTF) field of the PHY preamble. The LTF carries known sequences and based on how these known sequences are received at the AP, the AP is capable of determining timing information associated with the NDP. For example, based on the sequences, the AP knows the pilot tone locations and whether they are attenuated or amplified. This information helps the AP determine the distance to the station device that sent the NDP.

[0022] The measurement polling phase, the measurement phase(s), the LMR feedback from AP to STA phase, and/or the LMR feedback from STA to AP phase could be within a target wake time service. This way, a station device that is a power save device, that goes to a low power state (e.g., doze state), would know when to wake up to receive the measurement polling frame. [0023] In one embodiment, an LMR feedback schedule system may enable an efficient mechanism for power save devices to enter into a low-power state based on information included in the trigger frame that is sent in the measurement phase(s).

[0024] In one embodiment, an LMR feedback schedule system may address a new method for multiusers (MU) scheduling and resources allocation enabling STAs to perform location measurements simultaneously. Triggered uplink operation is one factor to MU location measurements.

[0025] In one embodiment, an LMR feedback schedule system may define special signaling in the Trigger frame format for llaz-based ranging for enhanced power efficiency. This may assist STAs to enter doze state after the Measurement Phase, when the AP does not schedule LMR feedback within the same availability window. For example, the AP may indicate to the station device(s), within the SP, the AP will serve the STA within this service period.

[0026] In one embodiment, an LMR feedback schedule system may facilitate the definition of signaling in Trigger frame for ranging to schedule LMR feedback within the same availability window (e.g., TXOP, TWT SP, and/or SP). It may also facilitate the definition of signaling in Trigger frame for ranging to schedule LMR feedback in the next pre-negotiated target wake time (TWT) SP. For example, the AP may indicate to the station device(s) that the AP will serve the STA within the next SP, which may be pre-negotiated with the STA.

[0027] In one embodiment, an LMR feedback schedule system may facilitate the definition of signaling in Trigger frame for ranging to schedule LMR feedback at a time advertised in the next beacon frame. For example, the AP may not have negotiated with the station devices (s) regarding a TWT SP. In that case, the AP may indicate in the trigger frame that the station device(s) should wait until a next beacon frame where the AP may advertise to the station device(s) when the station device(s) need to wake up.

[0028] Currently, scheduling the LMR feedback may be performed within the same TXOP or in different TXOP. However, for a single user (SU) performing Measurement Phase, the LMR feedback might be scheduled in the same TXOP / SP.

[0029] In one embodiment, an LMR feedback schedule system may define a subfield in a trigger frame to carry LMR feedback information to one or more solicited station devices. The subfield may be comprised of one or more bits. The one or more bits may be set to one or more values to carry the LMR feedback information to the one or more solicited station devices. For example, the one or more bits may be set to a first value indicating that a station device is solicited in a trigger frame within an availability window (e.g., TXOP, SP, and TWT SP). In another example, the one or more bits may be set to a second value indicating that the LMR feedback may be performed in a next pre-negotiated availability window (e.g., TXOP, SP, and TWT SP). For example, a station device and an AP may have performed negotiation before starting the LMR procedure, where the station device may have indicated when it will be in a low-power state (doze) and when it will wake up. In this case, the AP may indicate using the subfield by setting the one or more bits to the second value to inform the station device that based on the pre-negotiation, the station device should wake up (go into a high power state) at a later availability window. In another example, the one or more bits may be set to a third value to indicate to the one or more solicited station devices that the LMR feedback is scheduled in a different availability window (e.g., TXOP, SP, TWT SP), right after the current period. In yet another example, the one or more bits may be set to a fourth value that indicates to the one or more solicited devices to check in the next beacon frame for LMR feedback schedule. Although the examples above show four values for the subfield in the trigger frame, more bits and more values may be envisioned to carry additional indications to the one or more solicited station devices.

[0030] In one embodiment, the subfield of the trigger frame that carries the LMR information to the one or more solicited station devices may be included in the common information field of the trigger frame, included in one or more user information fields of the trigger frame, or any other fields within the trigger frame.

[0031] The above descriptions are for purposes of illustration and are not meant to be limiting. Numerous other examples, configurations, processes, etc., may exist, some of which are described in detail below. Example embodiments will now be described with reference to the accompanying figures.

[0032] FIG. 1 is a diagram illustrating an example network environment, in accordance with one or more example embodiments of the present disclosure. Wireless network 100 may include one or more user devices 120 and one or more access point(s) (AP) 102, which may communicate in accordance with IEEE 802.11 communication standards. The user device(s) 120 may be mobile devices that are non-stationary (e.g., not having fixed locations) or may be stationary devices.

[0033] In some embodiments, the user devices 120, and the AP(s) 102 may include one or more computer systems similar to that of the functional diagram of FIG. 6 and/or the example machine/system of FIG. 7.

[0034] One or more illustrative user device(s) 120 and/or AP(s) 102 may be operable by one or more user(s) 110. It should be noted that any addressable unit may be a station (STA). An STA may take on multiple distinct characteristics, each of which shape its function. For example, a single addressable unit might simultaneously be a portable STA, a quality-of- service (QoS) STA, a dependent STA, and a hidden STA. The one or more illustrative user device(s) 120 and the AP(s) 102 may be STAs. The one or more illustrative user device(s) 120 and/or AP(s) 102 may operate as a personal basic service set (PBSS) control point/access point (PCP/AP). The user device(s) 120 (e.g., 124, 126, or 128) and/or AP(s) 102 may include any suitable processor-driven device including, but not limited to, a mobile device or a non-mobile, e.g., a static, device. For example, user device(s) 120 and/or AP(s) 102 may include, a user equipment (UE), a station (STA), an access point (AP), a software enabled AP (SoftAP), a personal computer (PC), a wearable wireless device (e.g., bracelet, watch, glasses, ring, etc.), a desktop computer, a mobile computer, a laptop computer, an ultrabook™ computer, a notebook computer, a tablet computer, a server computer, a handheld computer, a handheld device, an internet of things (IoT) device, a sensor device, a PDA device, a handheld PDA device, an on-board device, an off-board device, a hybrid device (e.g., combining cellular phone functionalities with PDA device functionalities), a consumer device, a vehicular device, a non-vehicular device, a mobile or portable device, a non-mobile or non-portable device, a mobile phone, a cellular telephone, a PCS device, a PDA device which incorporates a wireless communication device, a mobile or portable GPS device, a DVB device, a relatively small computing device, a non-desktop computer, a "carry small live large" (CSLL) device, an ultra mobile device (UMD), an ultra mobile PC (UMPC), a mobile internet device (MID), an "origami" device or computing device, a device that supports dynamically composable computing (DCC), a context-aware device, a video device, an audio device, an A/V device, a set-top-box (STB), a blu-ray disc (BD) player, a BD recorder, a digital video disc (DVD) player, a high definition (HD) DVD player, a DVD recorder, a HD DVD recorder, a personal video recorder (PVR), a broadcast HD receiver, a video source, an audio source, a video sink, an audio sink, a stereo tuner, a broadcast radio receiver, a flat panel display, a personal media player (PMP), a digital video camera (DVC), a digital audio player, a speaker, an audio receiver, an audio amplifier, a gaming device, a data source, a data sink, a digital still camera (DSC), a media player, a smartphone, a television, a music player, or the like. Other devices, including smart devices such as lamps, climate control, car components, household components, appliances, etc. may also be included in this list.

[0035] As used herein, the term "Internet of Things (IoT) device" is used to refer to any object (e.g., an appliance, a sensor, etc.) that has an addressable interface (e.g., an Internet protocol (IP) address, a Bluetooth identifier (ID), a near-field communication (NFC) ID, etc.) and can transmit information to one or more other devices over a wired or wireless connection. An IoT device may have a passive communication interface, such as a quick response (QR) code, a radio-frequency identification (RFID) tag, an NFC tag, or the like, or an active communication interface, such as a modem, a transceiver, a transmitter-receiver, or the like. An IoT device can have a particular set of attributes (e.g., a device state or status, such as whether the IoT device is on or off, open or closed, idle or active, available for task execution or busy, and so on, a cooling or heating function, an environmental monitoring or recording function, a light-emitting function, a sound-emitting function, etc.) that can be embedded in and/or controlled/monitored by a central processing unit (CPU), microprocessor, ASIC, or the like, and configured for connection to an IoT network such as a local ad-hoc network or the Internet. For example, IoT devices may include, but are not limited to, refrigerators, toasters, ovens, microwaves, freezers, dishwashers, dishes, hand tools, clothes washers, clothes dryers, furnaces, air conditioners, thermostats, televisions, light fixtures, vacuum cleaners, sprinklers, electricity meters, gas meters, etc., so long as the devices are equipped with an addressable communications interface for communicating with the IoT network. IoT devices may also include cell phones, desktop computers, laptop computers, tablet computers, personal digital assistants (PDAs), etc. Accordingly, the IoT network may be comprised of a combination of "legacy" Internet-accessible devices (e.g., laptop or desktop computers, cell phones, etc.) in addition to devices that do not typically have Internet-connectivity (e.g., dishwashers, etc.).

[0036] The user device(s) 120 and/or AP(s) 102 may also include mesh stations in, for example, a mesh network, in accordance with one or more IEEE 802.11 standards and/or 3 GPP standards.

[0037] Any of the user device(s) 120 (e.g., user devices 124, 126, 128), and AP(s) 102 may be configured to communicate with each other via one or more communications networks 130 and/or 135 wirelessly or wired. The user device(s) 120 may also communicate peer-to-peer or directly with each other with or without the AP(s) 102. Any of the communications networks 130 and/or 135 may include, but not limited to, any one of a combination of different types of suitable communications networks such as, for example, broadcasting networks, cable networks, public networks (e.g., the Internet), private networks, wireless networks, cellular networks, or any other suitable private and/or public networks. Further, any of the communications networks 130 and/or 135 may have any suitable communication range associated therewith and may include, for example, global networks (e.g., the Internet), metropolitan area networks (MANs), wide area networks (WANs), local area networks (LANs), or personal area networks (PANs). In addition, any of the communications networks 130 and/or 135 may include any type of medium over which network traffic may be carried including, but not limited to, coaxial cable, twisted-pair wire, optical fiber, a hybrid fiber coaxial (HFC) medium, microwave terrestrial transceivers, radio frequency communication mediums, white space communication mediums, ultra-high frequency communication mediums, satellite communication mediums, or any combination thereof.

[0038] Any of the user device(s) 120 (e.g., user devices 124, 126, 128) and AP(s) 102 may include one or more communications antennas. The one or more communications antennas may be any suitable type of antennas corresponding to the communications protocols used by the user device(s) 120 (e.g., user devices 124, 126 and 128), and AP(s) 102. Some non-limiting examples of suitable communications antennas include Wi-Fi antennas, Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards compatible antennas, directional antennas, non-directional antennas, dipole antennas, folded dipole antennas, patch antennas, multiple-input multiple-output (MIMO) antennas, omnidirectional antennas, quasi- omnidirectional antennas, or the like. The one or more communications antennas may be communicatively coupled to a radio component to transmit and/or receive signals, such as communications signals to and/or from the user devices 120 and/or AP(s) 102.

[0039] Any of the user device(s) 120 (e.g., user devices 124, 126, 128), and AP(s) 102 may be configured to perform directional transmission and/or directional reception in conjunction with wirelessly communicating in a wireless network. Any of the user device(s) 120 (e.g., user devices 124, 126, 128), and AP(s) 102 may be configured to perform such directional transmission and/or reception using a set of multiple antenna arrays (e.g., DMG antenna arrays or the like). Each of the multiple antenna arrays may be used for transmission and/or reception in a particular respective direction or range of directions. Any of the user device(s) 120 (e.g., user devices 124, 126, 128), and AP(s) 102 may be configured to perform any given directional transmission towards one or more defined transmit sectors. Any of the user device(s) 120 (e.g., user devices 124, 126, 128), and AP(s) 102 may be configured to perform any given directional reception from one or more defined receive sectors.

[0040] MIMO beamforming in a wireless network may be accomplished using RF beamforming and/or digital beamforming. In some embodiments, in performing a given MIMO transmission, user devices 120 and/or AP(s) 102 may be configured to use all or a subset of its one or more communications antennas to perform MIMO beamforming.

[0041] Any of the user devices 120 (e.g., user devices 124, 126, 128), and AP(s) 102 may include any suitable radio and/or transceiver for transmitting and/or receiving radio frequency (RF) signals in the bandwidth and/or channels corresponding to the communications protocols utilized by any of the user device(s) 120 and AP(s) 102 to communicate with each other. The radio components may include hardware and/or software to modulate and/or demodulate communications signals according to pre-established transmission protocols. The radio components may further have hardware and/or software instructions to communicate via one or more Wi-Fi and/or Wi-Fi direct protocols, as standardized by the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards.

[0042] Some embodiments may be used in conjunction with devices and/or networks operating in accordance with existing. Wireless Fidelity (Wi-Fi) Alliance (WFA) Specifications, including Wi-Fi Neighbor Awareness Networking (NAN) Technical Specification (e.g., NAN and NAN2) and/or future versions and/or derivatives thereof, devices and/or networks operating in accordance with existing WFA Peer-to-Peer (P2P) specifications and/or future versions and/or derivatives thereof, devices and/or networks operating in accordance with existing Wireless-Gigabit-Alliance (WGA) specifications (Wireless Gigabit Alliance, Inc. WiGig MAC and PHY Specification) and/or future versions and/or derivatives thereof, devices and/or networks operating in accordance with existing IEEE 802.11 standards and/or amendments (e.g., 802.11b, 802.11g, 802.11η, 802.1 lac, 802.1 lax, 802.1 lad, 802. Hay, 802.1 laz, etc.).

[0043] In certain example embodiments, the radio component, in cooperation with the communications antennas, may be configured to communicate via 2.4 GHz channels (e.g., 802.11b, 802.1 lg, 802.11η, 802.11ax), 5 GHz channels (e.g., 802.11η, 802.11ac, 802.1 lax), or 60 GHZ channels (e.g., 802.1 lad). In some embodiments, non-Wi-Fi protocols may be used for communications between devices, such as Bluetooth, dedicated short-range communication (DSRC), Ultra-High Frequency (UHF) (e.g., IEEE 802.11af, IEEE 802.22), white band frequency (e.g., white spaces), or other packetized radio communications. The radio component may include any known receiver and baseband suitable for communicating via the communications protocols. The radio component may further include a low noise amplifier (LNA), additional signal amplifiers, an analog-to-digital (A/D) converter, one or more buffers, and digital baseband.

[0044] In one embodiment, and with reference to FIG. 1, a user device 120 may be in communication with one or more APs 102.

[0045] For example, AP 102 may communicate with a user device 120 by signaling LMR feedback schedule 140 between each other. It is understood that the above descriptions are for purposes of illustration and are not meant to be limiting. [0046] FIG. 2 depicts an illustrative schematic diagram for polling, measurement, and LMR feedback in one availability window.

[0047] Referring to FIG. 2, there is shown an availability window 202 for sending and/or receiving location determination measurement. The availability window 202 may be any one of a TXOP period, a TWT period, or a service period (SP).

[0048] During the availability window 202, the AP and the STA may enter into location measurements using one or more frames in one or more phases. For example, a measurement polling phase 201, one or more measurement phase(s) 203, an LMR feedback from AP to STA phase 205, and/or an LMR feedback from STA to AP phase 207. The measurement polling phase 201 and the one or more measurement phases 203 may be separated by a time period tool for. Similarly, the LMR feedback from AP to STA phase 205 and the LMR feedback from STA to AP phase 207 (if present) may also be separated by a similar time period (e.g., time period 206). It should be understood that time periods 204 and 206 may have the same length and time and may be defined as short inter-frame space (SIFS) time.

[0049] There are multiple variants of the Trigger frame defined in 802.1 lax draft specification namely: Basic variant Trigger (for UL MU operation); Beamforming Report Poll Trigger (to collect feedback from STAs in MU for DL sounding); Buffer Status Report Poll trigger (to collect buffer status information from multiple STAs simultaneously); MU-RTS (Trigger frame for protection of DL PPDUs at the STAs from their neighboring STAs); Bandwidth Query Report Poll Trigger (to collect channel bandwidth information from STAs).

[0050] A unique Trigger Type may be defined for 802. llaz-based ranging and four different Trigger frame sub-types (different from the seven variants defined in 802.1 lax as shown below) have been identified. They are as follows: Trigger frame for l laz-based MU ranging negotiation; Trigger frame for llaz-based MU measurement phase (Triggering the UL NDP from multiple STAs); Trigger frame for LMR report from multiple STAs simultaneously; and Trigger frame for the polling phase preceding the MU measurement phase. This Trigger frame can be a polling Trigger frame, an UL sounding Trigger frame, or any variant of the Trigger frame.

[0051] As shown in the FIG. 2, the AP might schedule the location measurement report (LMR) feedback within the same availability window 202 (e.g., TXOP, TWT SP, or SP) or in a separate availability window. FIG. 2 illustrates the LMR feedback from AP and the STAs within the same availability window (for example, TWT service period). However, the measurement phase 203 might consist of a single UL sounding phase (comprising of a single Trigger Frame requesting UL NDP frames from a set of STAs) or several UL sounding phases (comprising of a sequence where each sequence consists of a single Trigger Frame requesting UL NDP frames from a set of STAs).

[0052] The AP decides the scheduling of LMR feedback scheduling either within the same availability window or in a different availability window, but this information is unknown to STAs that have participated in the Measurement Phase. Due to this ambiguity, the STAs that have participated in the Measurement Phase 203 have to decode each of the subsequent Trigger frames to know whether LMR feedback is requested by the AP in this availability window. This raises the problem of power inefficiency, since prior knowledge after participation in Measurement Phase would enable the STAs to enter doze state, provided the AP does not intend to schedule trigger frames for LMR feedback.

[0053] FIG. 3 depicts an illustrative schematic diagram 300 for LMR feedback schedule, in accordance with one or more example embodiments of the present disclosure.

[0054] Typically, the Trigger Sub-types are defined in the Trigger Dependent Common Info field.

[0055] In one embodiment, an LMR feedback schedule system may define a subfield termed as "LMR Feedback Schedule" in the Trigger Dependent Common Info field of a Trigger frame for Measurement Phase. The values in this subfield may be set in one or more bits (e.g., 2-bits). The subfield may be defined by one or more bits to enable the LMR feedback schedule indication in a trigger frame. In the example of 2-bit LMR feedback schedule subfield, the bit definition may be as follows:

[0056] "00" - indicates that the LMR feedback is scheduled in current availability window (e.g., TXOP, SP, or TWT SP);

[0057] "01" - indicates that the LMR feedback is scheduled in the next pre-negotiated availability window (e.g., TXOP, SP, or TWT SP). For example, in the case of TWT SP, if TWT is supported by all STAs that have participated in the current Trigger frame requesting UL NDPs;

[0058] "10"- indicates that the LMR feedback is scheduled in a different availability window (e.g., TXOP, SP, or TWT SP)right after the current availability window; and

[0059] "11" - indicates that the LMR feedback schedule is advertised in the following beacon frame.

[0060] It should be understood that the subfield values of two bits is only shown as an example and that the subfield values are not limited to only two bits. [0061] When the value in the LMR Feedback Schedule subfield is set to "00" in the currently sent Trigger frame for UL sounding, then the AP may schedule the LMR feedback in the same (current) availability window (e.g., TXOP / SP / TWT SP).

[0062] Referring back to FIG. 2, an AP may send a message to poll a STA regarding location measurements. The STA may then respond with an affirmation (or rejection) to participate in one or more measurement phases (e.g., measurement phase(s) 203). The AP may send a trigger frame containing the LMR feedback schedule subfield. In the case when the STA identifies that the LMR feedback schedule subfield is set to "00" in the trigger frame, the STA may determine that it should not enter in a low power state (go to sleep or enter a doze state) because the STA determines that the LMR feedback schedule subfield of "00" indicates that the LMR feedback from AP to STA (e.g., LMR feedback from AP to STA phase 205) will be sent in the same availability window (e.g., TXOP, TWT SP, or SP). The STA, after sending its UL NDP frame in response to the trigger frame containing the LMR feedback schedule in an resource unit (RU) assigned to the STA, does not go to sleep state after the Measurement Phase 203. The STA may wait for the LMR feedback phase 205 to be completed and then enter the doze state.

[0063] Referring to FIG. 3, there is shown a negotiation stage 301, a first availability window 302, and a second (subsequent) availability window 303. The first availability window 302 and the second availability window 303 may be any one of a TXOP, a TWT SP, or an SP.

[0064] In the first availability window 302, there is shown a measurement polling phase 304 and one or more measurement phase(s) 305 separated by a SIFS time. Further, FIG. 3 shows that the LMR feedback is determined to be in the next pre-negotiated availability window (e.g., second availability window 303). The negotiation might be performed by STAs in conjunction with the fine timing measurement (FTM) negotiation during the negotiation stage 301. The negotiation stage 301 may be comprised of one or more request frames and one or more acknowledgment frames. In the example of FIG. 3 there is shown that the negotiation stage is a combination of FTM negotiation and TWT negotiation. In this case, TWT request frames may be acknowledged with acknowledgment frames. During that negotiation stage 301, the AP and the STAs may determine one or more availability windows that the STA wake up at in order to receive additional frames from the AP. In this example, the trigger frame sent during the one or more measurement phase(s) may set in the LMR feedback schedule subfield a value. When the value in the LMR feedback schedule subfield is set to "01" in the currently sent trigger frame (e.g., during the first availability window 302) for UL sounding, then the AP may schedule the LMR feedback in the next pre-negotiated availability window (e.g., during the second availability window 303).

[0065] After an STA sends its UL NDP frame, in response to the trigger frame containing the LMR feedback schedule in an RU assigned to the STA, the STA may enter doze state right after sending the UL NDP frame. The STA need not decode the subsequent trigger frames scheduled for successive measurement phases with other sets of STAs in the current availability window because of the determination that the LMR feedback schedule is set to "01". In this scenario, the STAs can doze for a duration equivalent to the value of, for example, a TWT interval 325 negotiated by the set of STAs with the AP during the negotiation stage 301. It is understood that the above LMR feedback schedule values and/or the usage of specific availability window, are for purposes of illustration and are not meant to be limiting.

[0066] In case an STA does not support TWT operation and the LMR Feedback Schedule subfield is set to "01" in the currently sent trigger frame (e.g., during the first availability window 302) for UL sounding, the LMR feedback is sent at an indicated time, where the indication is provided by the STA in a prior frame exchange (e.g., during the negotiation stage 301). Therefore, the STA enters doze state by setting the power management (PM) bit to 1. If there is no explicit indication provided by the STA about the next wake-up schedule, the AP might schedule the LMR feedback when the STA resets the PM bit to 0. It should be understood that a STA sets the bit in the frame control field to indicate that it is in power-save mode. The AP will then start to buffer frames in one or more queues. The AP will not buffer frames for an STA in active mode, as indicated by a 0 in the PM bit.

[0067] When the value in the LMR feedback schedule subfield is set to "10" in the currently sent trigger frame for UL sounding, then the AP may schedule the LMR feedback in a different availability window after the current availability window. In this case, the AP and the STA may not have determined during a negotiation stage when the STA should wake up. In this scenario, the STAs may doze until the end of the current availability window after sending the UL NDPs in response to the trigger frame for UL sounding. If the time is not enough to doze, the STAs may remain awake until the beginning of the next availability window. It is understood that the above descriptions are for purposes of illustration and are not meant to be limiting.

[0068] FIG. 4 depicts an illustrative schematic diagram 400 for LMR feedback schedule, in accordance with one or more example embodiments of the present disclosure. [0069] Referring to FIG. 4, there is shown a measurement stage comprising a measurement polling phase 402 and one or more measurement phase(s) 403 within a first availability window 401.

[0070] Referring to FIG. 4, there is shown an illustration of polling, measurement in current TXOP and LMR feedback in a TXOP at a time advertised in the Beacon frame.

[0071] When the value in the LMR Feedback Schedule subfield is set to "11" in the currently sent Trigger frame (e.g., during the first availability window 401) for UL sounding, then the AP may schedule the LMR feedback at a time that is advertised in the forthcoming Beacon frame 404.

[0072] In one embodiment, the AP may set a time advertised termed as target time for LMR feedback 405. The target time for LMR feedback 405 may indicate a target time (e.g., target time 407) when the next LMR feedback from AP to STA and/or the optional LMR feedback 406 from STA to AP may be expected. The target time 407 for LMR feedback may be carried in an information element in the beacon frame 404, such as a new IE or an existing IE of the beacon frame 404. For example, the beacon frame 404 may carry LMR feedback information in a new IE or in a TWT element. In the case of a new IE, the new IE may be called "availability window IE."

[0073] In this scenario, the STAs after participating in the Measurement Phase may enter a doze state for the remaining time to target beacon transmission time (TBTT) in order to decode the advertised time. Once it decodes the advertised time, the STAs may enter doze state again until the end of the target time advertised. It is understood that the above descriptions are for purposes of illustration and are not meant to be limiting.

[0074] FIG. 5 illustrates a flow diagram of illustrative process 500 for an illustrative LMR feedback schedule system, in accordance with one or more example embodiments of the present disclosure.

[0075] At block 502, a device (e.g., the user device(s) 120 and/or the AP 102 of FIG. 1) may cause to send a measurement polling request to one or more station devices. For example, the AP may perform polling with one or user devices. The polling performed by the AP is to determine whether a station device is interested in performing location measurement.

[0076] At block 504, the device may identify one or more responses to the measurement polling request from at first subset of the one or more station devices. For example, the one or more user devices may respond to the AP's polling request indicating a desire to perform location measurements. After the polling, the AP may enter a measurement phase, where the AP may send a trigger frame that solicits from one or more user devices their uplink NDP frames.

[0077] At block 506, the device may encode a trigger frame comprising one or more fields to notify a first subset of the one or more station devices of one or more resource units. For example, the one or more user devices that have been polled by the AP during the measurement polling phase, may not all be solicited with the trigger frame. In other words a subset of the one or more station devices that were polled may be solicited by the trigger frame.

[0078] At block 508, the device may set a location measurement report (LMR) feedback indication in the trigger frame. For example, the AP may use a subfield in a trigger frame to carry LMR feedback information to one or more solicited station devices. The subfield may be comprised of one or more bits. The one or more bits may be set to one or more values to carry the LMR feedback information to the one or more solicited user devices. For example, the one or more bits may be set to a first value indicating that a user device is solicited in a trigger frame within an availability window (e.g., TXOP, SP, and TWT SP). In another example, the one or more bits may be set to a second value indicating that the LMR feedback may be performed in a next pre-negotiated availability window (e.g., TXOP, SP, and TWT SP). For example, a user device and an AP may have performed negotiation before starting the LMR procedure, where the user device may have indicated when it will be in a low-power state (doze) and when it will wake up. In this case, the AP may indicate using the subfield by setting the one or more bits to the second value to inform the user device that based on the pre- negotiation, the user device should wake up (go into a high power state) at a later availability window. In another example, the one or more bits may be set to a third value to indicate to the one or more solicited user devices that the LMR feedback is scheduled in a different availability window (e.g., TXOP, SP, TWT SP), right after the current period. In yet another example, the one or more bits may be set to a fourth value that indicates to the one or more solicited devices to check in the next beacon frame for LMR feedback schedule. Although the examples above show four values for the subfield in the trigger frame, more bits and more values may be envisioned to carry additional indications to the one or more solicited user devices.

[0079] At block 510, the device may cause to send the trigger frame to the first subset of the one or more station devices.

[0080] It is understood that the above descriptions are for purposes of illustration and are not meant to be limiting. [0081 ] FIG. 5B illustrates a flow diagram of illustrative process 550 for an illustrative LMR feedback schedule system, in accordance with one or more example embodiments of the present disclosure.

[0082] At block 552, a device (e.g., the user device(s) 120 and/or the AP 102 of FIG. 1) may identify a measurement polling request from a device. For example, the user device may receive a polling request during a measurement polling stage associated with an AP. During that stage the APS soliciting one or more user devices to participate in location measurements. In this case, if a user device received the polling request, the user device may determine whether it wants to participate in location measurements and response to the AP accordingly.

[0083] At block 554, the device may cause to send a response to the measurement polling request. For example, the user device may determine that it is interested in participating in location measurements and may respond to the polling request from the AP by indicating such.

[0084] At block 556, the device may decode a trigger frame comprising one or more fields, wherein at least one of the one or more fields contains information associated with a first resource unit. The trigger frame may be for ranging to schedule LMR feedback within the same availability window (e.g., TXOP, TWT SP, and/or SP). Upon reception of a trigger frame, user devices that have been assigned resource units (RUs) indicated in the trigger frame

[0085] At block 558, the device may determine a location measurement report (LMR) feedback indication in the trigger frame. For example, the AP may use a subfield in a trigger frame to carry LMR feedback information to one or more solicited station devices. The subfield may be comprised of one or more bits. The one or more bits may be set to one or more values to carry the LMR feedback information to the one or more solicited user devices. For example, the one or more bits may be set to a first value indicating that a user device is solicited in a trigger frame within an availability window (e.g., TXOP, SP, and TWT SP). In another example, the one or more bits may be set to a second value indicating that the LMR feedback may be performed in a next pre-negotiated availability window (e.g., TXOP, SP, and TWT SP). For example, a user device and an AP may have performed negotiation before starting the LMR procedure, where the user device may have indicated when it will be in a low-power state (doze) and when it will wake up. In this case, the AP may indicate using the subfield by setting the one or more bits to the second value to inform the user device that based on the pre- negotiation, the user device should wake up (go into a high power state) at a later availability window. In another example, the one or more bits may be set to a third value to indicate to the one or more solicited user devices that the LMR feedback is scheduled in a different availability window (e.g., TXOP, SP, TWT SP), right after the current period. In yet another example, the one or more bits may be set to a fourth value that indicates to the one or more solicited devices to check in the next beacon frame for LMR feedback schedule. Although the examples above show four values for the subfield in the trigger frame, more bits and more values may be envisioned to carry additional indications to the one or more solicited user devices.

[0086] At block 560, the device may determine a low power state based on the LMR feedback indication.

[0087] It is understood that the above descriptions are for purposes of illustration and are not meant to be limiting.

[0088] FIG. 6 shows a functional diagram of an exemplary communication station 600 in accordance with some embodiments. In one embodiment, FIG. 6 illustrates a functional block diagram of a communication station that may be suitable for use as an AP 102 (FIG. 1) or a user device 120 (FIG. 1) in accordance with some embodiments. The communication station 600 may also be suitable for use as a handheld device, a mobile device, a cellular telephone, a smartphone, a tablet, a netbook, a wireless terminal, a laptop computer, a wearable computer device, a femtocell, a high data rate (HDR) subscriber station, an access point, an access terminal, or other personal communication system (PCS) device.

[0089] The communication station 602 may include communications circuitry 602 and a transceiver 610 for transmitting and receiving signals to and from other communication stations using one or more antennas 601. The transceiver 610 may be a device comprising both a transmitter and a receiver that are combined and share common circuitry (e.g., communication circuitry 602). The communication circuitry 602 may include amplifiers, filters, mixers, analog to digital and/or digital to analog converters. The transceiver 610 may transmit and receive analog or digital signals. The transceiver 610 may allow reception of signals during transmission periods. This mode is known as full-duplex, and may require the transmitter and receiver to operate on different frequencies to minimize interference between the transmitted signal and the received signal. The transceiver 610 may operate in a half-duplex mode, where the transceiver 610 may transmit or receive signals in one direction at a time.

[0090] The communications circuitry 602 may include circuitry that can operate the physical layer (PHY) communications and/or media access control (MAC) communications for controlling access to the wireless medium, and/or any other communications layers for transmitting and receiving signals. The communication station 600 may also include processing circuitry 606 and memory 608 arranged to perform the operations described herein. In some embodiments, the communications circuitry 602 and the processing circuitry 606 may be configured to perform operations detailed in FIGs.1-4, and 5A-5B. [0091] In accordance with some embodiments, the communications circuitry 602 may be arranged to contend for a wireless medium and configure frames or packets for communicating over the wireless medium. The communications circuitry 602 may be arranged to transmit and receive signals. The communications circuitry 602 may also include circuitry for modulation/demodulation, upconversion/downconversion, filtering, amplification, etc. In some embodiments, the processing circuitry 606 of the communication station 600 may include one or more processors. In other embodiments, two or more antennas 601 may be coupled to the communications circuitry 602 arranged for sending and receiving signals. The memory 608 may store information for configuring the processing circuitry 606 to perform operations for configuring and transmitting message frames and performing the various operations described herein. The memory 608 may include any type of memory, including non-transitory memory, for storing information in a form readable by a machine (e.g., a computer). For example, the memory 608 may include a computer-readable storage device, read-only memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash- memory devices and other storage devices and media.

[0092] In some embodiments, the communication station 600 may be part of a portable wireless communication device, such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capability, a web tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), a wearable computer device, or another device that may receive and/or transmit information wirelessly.

[0093] In some embodiments, the communication station 600 may include one or more antennas 601. The antennas 601 may include one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas, or other types of antennas suitable for transmission of RF signals. In some embodiments, instead of two or more antennas, a single antenna with multiple apertures may be used. In these embodiments, each aperture may be considered a separate antenna. In some multiple-input multiple-output (MIMO) embodiments, the antennas may be effectively separated for spatial diversity and the different channel characteristics that may result between each of the antennas and the antennas of a transmitting station.

[0094] In some embodiments, the communication station 600 may include one or more of a keyboard, a display, a non-volatile memory port, multiple antennas, a graphics processor, an application processor, speakers, and other mobile device elements. The display may be an LCD screen including a touch screen.

[0095] Although the communication station 600 is illustrated as having several separate functional elements, two or more of the functional elements may be combined and may be implemented by combinations of software-configured elements, such as processing elements including digital signal processors (DSPs), and/or other hardware elements. For example, some elements may include one or more microprocessors, DSPs, field- programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio- frequency integrated circuits (RFICs) and combinations of various hardware and logic circuitry for performing at least the functions described herein. In some embodiments, the functional elements of the communication station 600 may refer to one or more processes operating on one or more processing elements.

[0096] Certain embodiments may be implemented in one or a combination of hardware, firmware, and software. Other embodiments may also be implemented as instructions stored on a computer-readable storage device, which may be read and executed by at least one processor to perform the operations described herein. A computer-readable storage device may include any non-transitory memory mechanism for storing information in a form readable by a machine (e.g., a computer). For example, a computer-readable storage device may include read-only memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices, and other storage devices and media. In some embodiments, the communication station 600 may include one or more processors and may be configured with instructions stored on a computer-readable storage device memory.

[0097] FIG. 7 illustrates a block diagram of an example of a machine 700 or system upon which any one or more of the techniques (e.g., methodologies) discussed herein may be performed. In other embodiments, the machine 700 may operate as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine 700 may operate in the capacity of a server machine, a client machine, or both in server-client network environments. In an example, the machine 700 may act as a peer machine in peer-to-peer (P2P) (or other distributed) network environments. The machine 700 may be a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a mobile telephone, a wearable computer device, a web appliance, a network router, a switch or bridge, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine, such as a base station. Further, while only a single machine is illustrated, the term "machine" shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein, such as cloud computing, software as a service (SaaS), or other computer cluster configurations.

[0098] Examples, as described herein, may include or may operate on logic or a number of components, modules, or mechanisms. Modules are tangible entities (e.g., hardware) capable of performing specified operations when operating. A module includes hardware. In an example, the hardware may be specifically configured to carry out a specific operation (e.g., hardwired). In another example, the hardware may include configurable execution units (e.g., transistors, circuits, etc.) and a computer readable medium containing instructions where the instructions configure the execution units to carry out a specific operation when in operation. The configuring may occur under the direction of the executions units or a loading mechanism. Accordingly, the execution units are communicatively coupled to the computer-readable medium when the device is operating. In this example, the execution units may be a member of more than one module. For example, under operation, the execution units may be configured by a first set of instructions to implement a first module at one point in time and reconfigured by a second set of instructions to implement a second module at a second point in time.

[0099] The machine (e.g., computer system) 700 may include a hardware processor 702 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 704 and a static memory 706, some or all of which may communicate with each other via an interlink (e.g., bus) 708. The machine 700 may further include a power management device 732, a graphics display device 710, an alphanumeric input device 712 (e.g., a keyboard), and a user interface (UI) navigation device 714 (e.g., a mouse). In an example, the graphics display device 710, alphanumeric input device 712, and UI navigation device 714 may be a touch screen display. The machine 700 may additionally include a storage device (i.e., drive unit) 716, a signal generation device 718 (e.g., a speaker), an LMR feedback schedule device 719, a network interface device/transceiver 720 coupled to antenna(s) 730, and one or more sensors 728, such as a global positioning system (GPS) sensor, a compass, an accelerometer, or other sensor. The machine 700 may include an output controller 734, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate with or control one or more peripheral devices (e.g., a printer, a card reader, etc.)).

[0100] The storage device 716 may include a machine readable medium 722 on which is stored one or more sets of data structures or instructions 724 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions 724 may also reside, completely or at least partially, within the main memory 704, within the static memory 706, or within the hardware processor 702 during execution thereof by the machine 700. In an example, one or any combination of the hardware processor 702, the main memory 704, the static memory 706, or the storage device 716 may constitute machine-readable media.

[0101] The LMR feedback schedule device 719 may carry out or perform any of the operations and processes (e.g., processes 500 and 550) described and shown above.

[0102] The LMR feedback schedule device 719 may enable an efficient mechanism for power save devices to enter into a low-power state based on information included in the trigger frame that is sent in the measurement phase(s).

[0103] The LMR feedback schedule device 719 may address a new method for multiusers (MU) scheduling and resources allocation enabling STAs to perform location measurements simultaneously. Triggered uplink operation is one factor to MU location measurements.

[0104] The LMR feedback schedule device 719 may define special signaling in the Trigger frame format for llaz-based ranging for enhanced power efficiency. This may assist STAs to enter a doze state after the Measurement Phase, when the AP does not schedule LMR feedback within the same TXOP / SP. For example, the AP may indicate to the station device(s), within the SP, the AP will serve the STA within this service.

[0105] The LMR feedback schedule device 719 may facilitate the definition of signaling in Trigger frame for ranging to schedule LMR feedback within the same TXOP /SP. It may also facilitate the definition of signaling in Trigger frame for ranging to schedule LMR feedback in the next pre-negotiated target wake time (TWT) SP. For example, the AP may indicate to the station device(s) that the AP will serve the STA within the next SP, which may be pre-negotiated with the STA.

[0106] The LMR feedback schedule device 719 may facilitate the definition of signaling in Trigger frame for ranging to schedule LMR feedback at a time advertised in the next beacon frame. For example, the AP may not have negotiated with the station devices(s) regarding a TWT SP. In that case, the AP may indicate in the trigger frame that the station device(s) should wait until a next beacon frame where the AP may advertise to the station device(s) when the station device(s) need to wake up. Currently, scheduling the LMR feedback may be performed within the same TXOP or in a different TXOP. However, for a single user (SU) performing Measurement Phase, the LMR feedback might be scheduled in the same TXOP / SP.

[0107] The LMR feedback schedule device 719 may define a subfield in a trigger frame to carry LMR information to one or more solicited station devices. The subfield may be comprised of one or more bits. The one or more bits may be set to one or more values to carry the LMR information to the one or more solicited station devices. For example, the one or more bits may be set to a first value indicating that a station device is solicited in a trigger frame within an availability window (e.g., TXOP, SP, TWT SP). In another example, the one or more bits may be set to a second value indicating that the LMR feedback may be performed in a next pre-negotiated availability window (e.g., TXOP, SP, TWT SP). For example, a station device and AP may have performed negotiations before starting the LMR procedure, where the station device may have indicated when it will be in a low-power state (doze) and when it will wake up. In this case, the AP may indicate using the subfield by setting the one or more bits to the second value to inform the station device that based on the pre-negotiation, the station device should wake up (go into a high power state) at a later availability window. In another example, the one or more bits may be set to a third value to indicate to the one or more solicited station devices that the LMR feedback is scheduled in a different availability window (e.g., TXOP, SP, TWT SP), right after the current period. In yet another example, the one or more bits may be set to a fourth value that indicates to the one or more solicited devices to check in the next beacon frame for LMR feedback schedule. Although the examples above show four values for the subfield in the trigger frame, more bits and more values may be envisioned to carry additional indications to the one or more solicited station devices.

[0108] The LMR feedback schedule device 719 may facilitate that the subfield of the trigger frame that carries the LMR information to the one or more solicited station devices may be included in the common information field of the trigger frame, included in one or more user information fields of the trigger frame, or any other fields within the trigger frame.

[0109] It is understood that the above are only a subset of what the LMR feedback schedule device 719 may be configured to perform and that other functions included throughout this disclosure may also be performed by the LMR feedback schedule device 719.

[0110] While the machine -readable medium 722 is illustrated as a single medium, the term "machine-readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions 724.

[0111] Various embodiments may be implemented fully or partially in software and/or firmware. This software and/or firmware may take the form of instructions contained in or on a non-transitory computer-readable storage medium. Those instructions may then be read and executed by one or more processors to enable performance of the operations described herein. The instructions may be in any suitable form, such as but not limited to source code, compiled code, interpreted code, executable code, static code, dynamic code, and the like. Such a computer-readable medium may include any tangible non-transitory medium for storing information in a form readable by one or more computers, such as but not limited to read only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; a flash memory, etc.

[0112] The term "machine-readable medium" may include any medium that is capable of storing, encoding, or carrying instructions for execution by the machine 700 and that cause the machine 700 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding, or carrying data structures used by or associated with such instructions. Non-limiting machine-readable medium examples may include solid-state memories and optical and magnetic media. In an example, a massed machine-readable medium includes a machine -readable medium with a plurality of particles having resting mass. Specific examples of massed machine-readable media may include non-volatile memory, such as semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM), or electrically erasable programmable read-only memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD- ROM disks.

[0113] The instructions 724 may further be transmitted or received over a communications network 726 using a transmission medium via the network interface device/transceiver 720 utilizing any one of a number of transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.). Example communications networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), plain old telephone (POTS) networks, wireless data networks (e.g., Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi®, IEEE 802.16 family of standards known as WiMax®), IEEE 802.15.4 family of standards, and peer-to-peer (P2P) networks, among others. In an example, the network interface device/transceiver 720 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas to connect to the communications network 726. In an example, the network interface device/transceiver 720 may include a plurality of antennas to wirelessly communicate using at least one of single-input multiple- output (SIMO), multiple-input multiple-output (MIMO), or multiple-input single-output (MISO) techniques. The term "transmission medium" shall be taken to include any intangible medium that is capable of storing, encoding, or carrying instructions for execution by the machine 700 and includes digital or analog communications signals or other intangible media to facilitate communication of such software. The operations and processes described and shown above may be carried out or performed in any suitable order as desired in various implementations. Additionally, in certain implementations, at least a portion of the operations may be carried out in parallel. Furthermore, in certain implementations, less than or more than the operations described may be performed.

[0114] The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments. The terms "computing device," "user device," "communication station," "station," "handheld device," "mobile device," "wireless device" and "user equipment" (UE) as used herein refers to a wireless communication device such as a cellular telephone, a smartphone, a tablet, a netbook, a wireless terminal, a laptop computer, a femtocell, a high data rate (HDR) subscriber station, an access point, a printer, a point of sale device, an access terminal, or other personal communication system (PCS) device. The device may be either mobile or stationary.

[0115] As used within this document, the term "communicate" is intended to include transmitting, or receiving, or both transmitting and receiving. This may be particularly useful in claims when describing the organization of data that is being transmitted by one device and received by another, but only the functionality of one of those devices is required to infringe the claim. Similarly, the bidirectional exchange of data between two devices (both devices transmit and receive during the exchange) may be described as "communicating," when only the functionality of one of those devices is being claimed. The term "communicating" as used herein with respect to a wireless communication signal includes transmitting the wireless communication signal and/or receiving the wireless communication signal. For example, a wireless communication unit, which is capable of communicating a wireless communication signal, may include a wireless transmitter to transmit the wireless communication signal to at least one other wireless communication unit, and/or a wireless communication receiver to receive the wireless communication signal from at least one other wireless communication unit.

[0116] As used herein, unless otherwise specified, the use of the ordinal adjectives "first," "second," "third," etc., to describe a common object, merely indicates that different instances of like objects are being referred to and are not intended to imply that the objects so described must be in a given sequence, either temporally, spatially, in ranking, or in any other manner.

[0117] The term "access point" (AP) as used herein may be a fixed station. An access point may also be referred to as an access node, a base station, an evolved node B (eNodeB), or some other similar terminology known in the art. An access terminal may also be called a mobile station, user equipment (UE), a wireless communication device, or some other similar terminology known in the art. Embodiments disclosed herein generally pertain to wireless networks. Some embodiments may relate to wireless networks that operate in accordance with one of the IEEE 802.11 standards.

[0118] Some embodiments may be used in conjunction with various devices and systems, for example, a personal computer (PC), a desktop computer, a mobile computer, a laptop computer, a notebook computer, a tablet computer, a server computer, a handheld computer, a handheld device, a personal digital assistant (PDA) device, a handheld PDA device, an onboard device, an off-board device, a hybrid device, a vehicular device, a non- vehicular device, a mobile or portable device, a consumer device, a non-mobile or non-portable device, a wireless communication station, a wireless communication device, a wireless access point (AP), a wired or wireless router, a wired or wireless modem, a video device, an audio device, an audio- video (A/V) device, a wired or wireless network, a wireless area network, a wireless video area network (WVAN), a local area network (LAN), a wireless LAN (WLAN), a personal area network (PAN), a wireless PAN (WPAN), and the like.

[0119] Some embodiments may be used in conjunction with one way and/or two-way radio communication systems, cellular radio-telephone communication systems, a mobile phone, a cellular telephone, a wireless telephone, a personal communication system (PCS) device, a PDA device which incorporates a wireless communication device, a mobile or portable global positioning system (GPS) device, a device which incorporates a GPS receiver or transceiver or chip, a device which incorporates an RFID element or chip, a multiple input multiple output (MIMO) transceiver or device, a single input multiple output (SIMO) transceiver or device, a multiple input single output (MISO) transceiver or device, a device having one or more internal antennas and/or external antennas, digital video broadcast (DVB) devices or systems, multi- standard radio devices or systems, a wired or wireless handheld device, e.g., a smartphone, a wireless application protocol (WAP) device, or the like.

[0120] Some embodiments may be used in conjunction with one or more types of wireless communication signals and/or systems following one or more wireless communication protocols, for example, radio frequency (RF), infrared (IR), frequency-division multiplexing (FDM), orthogonal FDM (OFDM), time-division multiplexing (TDM), time-division multiple access (TDM A), extended TDMA (E-TDMA), general packet radio service (GPRS), extended GPRS, code-division multiple access (CDMA), wideband CDMA (WCDMA), CDMA 2000, single-carrier CDMA, multi-carrier CDMA, multi-carrier modulation (MDM), discrete multi- tone (DMT), Bluetooth®, global positioning system (GPS), Wi-Fi, Wi-Max, ZigBee, ultra- wideband (UWB), global system for mobile communications (GSM), 2G, 2.5G, 3G, 3.5G, 4G, fifth generation (5G) mobile networks, 3 GPP, long term evolution (LTE), LTE advanced, enhanced data rates for GSM Evolution (EDGE), or the like. Other embodiments may be used in various other devices, systems, and/or networks.

[0121] Example 1 may include a device comprising memory and processing circuitry configured to: cause to send a measurement polling request to one or more station devices; identify one or more responses to the measurement polling request from at first subset of the one or more station devices; determine a trigger frame comprising one or more fields, wherein the trigger frame notifies a first subset of the one or more station devices of one or more resource units; set a location measurement report (LMR) feedback transmission indication in the trigger frame; and cause to send the trigger frame to the first subset of the one or more station devices.

[0122] Example 2 may include the device of example 1 and/or some other example herein, wherein the first subset may be a group of station devices intending to perform one or more location measurements.

[0123] Example 3 may include the device of example 1 and/or some other example herein, wherein the trigger frame comprises at least one of a polling trigger frame or an uplink sounding trigger frame.

[0124] Example 4 may include the device of example 1 and/or some other example herein, wherein the LMR feedback comprises at least one a report from the AP to the first subset of the one or more stations devices.

[0125] Example 5 may include the device of example 1 and/or some other example herein, wherein the LMR feedback transmission indication may be included in at least one of a trigger dependent common information field of the trigger frame or a user information field of the trigger frame.

[0126] Example 6 may include the device of example 1 and/or some other example herein, wherein the LMR feedback transmission indication comprises one or more bits to be sent to indicate a transmission status of an LMR feedback from the device to the first subset of the one or more station devices during an availability window.

[0127] Example 7 may include the device of example 6 and/or some other example herein, wherein the transmission status may be at least one of a transmission status of the LMR feedback within a current availability window, a transmission status of the LMR feedback within a pre-negotiated availability window, a transmission status of the LMR feedback within a subsequent availability window, or a transmission status of the LMR feedback based on a schedule advertised in a subsequent beacon frame.

[0128] Example 8 may include the device of example 1 and/or some other example herein, further comprising a transceiver configured to transmit and receive wireless signals.

[0129] Example 9 may include the device of example 8 and/or some other example herein, further comprising an antenna coupled to the transceiver.

[0130] Example 10 may include a non-transitory computer-readable medium storing computer-executable instructions which when executed by one or more processors result in performing operations comprising: identifying a measurement polling request from a device; causing to send a response to the measurement polling request; determining a trigger frame comprising one or more fields, wherein the trigger frame notifies a first subset of the one or more station devices of one or more resource units; determining a location measurement report (LMR) feedback transmission indication in the trigger frame; and determining a low power state based on the LMR feedback transmission indication.

[0131] Example 11 may include the non- transitory computer-readable medium of example 10 and/or some other example herein, wherein the response may include an indication to perform one or more location measurements with the device.

[0132] Example 12 may include the non- transitory computer-readable medium of example 10 and/or some other example herein, wherein the LMR feedback transmission indication may be included in at least one field of the trigger frame.

[0133] Example 13 may include the device of example 12 and/or some other example herein, wherein the at least one field may be a trigger dependent common information field or a user information field.

[0134] Example 14 may include the non- transitory computer-readable medium of example 10 and/or some other example herein, wherein the first resource unit are used to send an uplink null data packet (NDP) to the device.

[0135] Example 15 may include the non-transitory computer-readable medium of example 10 and/or some other example herein, wherein the LMR feedback indication transmission comprises one or more bits set to indicate a transmission status of an LMR feedback during an availability window.

[0136] Example 16 may include the non- transitory computer-readable medium of example 15 and/or some other example herein, wherein the transmission status may be at least one of a transmission status of the LMR feedback within a current availability window, a transmission status of the LMR feedback within a pre-negotiated availability window, a transmission status of the LMR feedback within a subsequent availability window, or a transmission status of the LMR feedback based on a schedule advertised in a subsequent beacon frame.

[0137] Example 17 may include the non-transitory computer-readable medium of example 15 and/or some other example herein, wherein the availability window may be at least one of a transmit opportunity (TXOP) period, a target wake time (TWT) period, or a service period (SP).

[0138] Example 18 may include a method comprising: causing, by one or more processors, to send a measurement polling request to one or more station devices; identifying one or more responses to the measurement polling request from at first subset of the one or more station devices; determining a trigger frame comprising one or more fields, wherein the trigger frame notifies a first subset of the one or more station devices of one or more resource units; setting a location measurement report (LMR) feedback indication in the trigger frame; and cause to send the trigger frame to the first subset of the one or more station devices.

[0139] Example 19 may include the method of example 18 and/or some other example herein, wherein the first subset may be a group of station devices intending to perform one or more location measurements.

[0140] Example 20 may include the method of example 18 and/or some other example herein, wherein the LMR feedback transmission indication may be included in at least one of a trigger dependent common information field of the trigger frame or a user information field of the trigger frame.

[0141] Example 21 may include the method of example 18 and/or some other example herein, wherein the LMR feedback transmission indication comprises one or more bits to be sent to indicate a transmission status of an LMR feedback from the device to the first subset of the one or more station devices during an availability window.

[0142] Example 22 may include the method of example 21 and/or some other example herein, wherein the transmission status may be at least one of a transmission status of the LMR feedback within a current availability window, a transmission status of the LMR feedback within a pre-negotiated availability window, a transmission status of the LMR feedback within a subsequent availability window, or a transmission status of the LMR feedback based on a schedule advertised in a subsequent beacon frame.

[0143] Example 23 may include an apparatus comprising means for: identifying a measurement polling request from a device; causing to send a response to the measurement polling request; determining a trigger frame comprising one or more fields, wherein the trigger frame notifies a first subset of the one or more station devices of one or more resource units; determining a location measurement report (LMR) feedback transmission indication in the trigger frame; and determining a low power state based on the LMR feedback transmission indication.

[0144] Example 24 may include the apparatus of example 23 and/or some other example herein, wherein the response may include an indication to perform one or more location measurements with the device.

[0145] Example 25 may include the apparatus of example 23 and/or some other example herein, wherein the LMR feedback transmission indication may be included in at least one field of the trigger frame.

[0146] Example 26 may include the device of example 25 and/or some other example herein, wherein the at least one field may be a trigger dependent common information field or a user information field.

[0147] Example 27 may include the apparatus of example 23 and/or some other example herein, wherein the first resource unit are used to send an uplink null data packet (NDP) to the device.

[0148] Example 28 may include the apparatus of example 23 and/or some other example herein, wherein the LMR feedback indication transmission comprises one or more bits set to indicate a transmission status of an LMR feedback during an availability window.

[0149] Example 29 may include the apparatus of example 28 and/or some other example herein, wherein the transmission status may be at least one of a transmission status of the LMR feedback within a current availability window, a transmission status of the LMR feedback within a pre-negotiated availability window, a transmission status of the LMR feedback within a subsequent availability window, or a transmission status of the LMR feedback based on a schedule advertised in a subsequent beacon frame.

[0150] Example 30 may include the apparatus of example 28 and/or some other example herein, wherein the availability window may be at least one of a transmit opportunity (TXOP) period, a target wake time (TWT) period, or a service period (SP).

[0151] Example 31 may include an apparatus comprising means for: causing to send a measurement polling request to one or more station devices; identifying one or more responses to the measurement polling request from at first subset of the one or more station devices; determining a trigger frame comprising one or more fields, wherein the trigger frame notifies a first subset of the one or more station devices of one or more resource units; setting a location measurement report (LMR) feedback transmission indication in the trigger frame; and causing to send the trigger frame to the first subset of the one or more station devices.

[0152] Example 32 may include the apparatus of example 31 and/or some other example herein, wherein the first subset may be a group of station devices intending to perform one or more location measurements.

[0153] Example 33 may include the apparatus of example 31 and/or some other example herein, wherein the trigger frame comprises at least one of a polling trigger frame or an uplink sounding trigger frame.

[0154] Example 34 may include the apparatus of example 31 and/or some other example herein, wherein the LMR feedback comprises at least one a report from the AP to the first subset of the one or more stations devices.

[0155] Example 35 may include the apparatus of example 31 and/or some other example herein, wherein the LMR feedback transmission indication may be included in at least one of a trigger dependent common information field of the trigger frame or a user information field of the trigger frame.

[0156] Example 36 may include the apparatus of example 31 and/or some other example herein, wherein the LMR feedback transmission indication comprises one or more bits to be sent to indicate a transmission status of an LMR feedback from the device to the first subset of the one or more station devices during an availability window.

[0157] Example 37 may include the apparatus of example 36 and/or some other example herein, wherein the transmission status may be at least one of a transmission status of the LMR feedback within a current availability window, a transmission status of the LMR feedback within a pre-negotiated availability window, a transmission status of the LMR feedback within a subsequent availability window, or a transmission status of the LMR feedback based on a schedule advertised in a subsequent beacon frame.

[0158] Example 38 may include one or more non- transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1-37, or any other method or process described herein.

[0159] Example 39 may include an apparatus comprising logic, modules, and/or circuitry to perform one or more elements of a method described in or related to any of examples 1-37, or any other method or process described herein. [0160] Example 40 may include a method, technique, or process as described in or related to any of examples 1-37, or portions or parts thereof.

[0161] Example 41 may include an apparatus comprising: one or more processors and one or more computer readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-37, or portions thereof.

[0162] Example 42 may include a method of communicating in a wireless network as shown and described herein.

[0163] Example 43 may include a system for providing wireless communication as shown and described herein.

[0164] Example 44 may include a device for providing wireless communication as shown and described herein.

[0165] Embodiments according to the disclosure are in particular disclosed in the attached claims directed to a method, a storage medium, a device and a computer program product, wherein any feature mentioned in one claim category, e.g., method, can be claimed in another claim category, e.g., system, as well. The dependencies or references back in the attached claims are chosen for formal reasons only. However, any subject matter resulting from a deliberate reference back to any previous claims (in particular multiple dependencies) can be claimed as well, so that any combination of claims and the features thereof are disclosed and can be claimed regardless of the dependencies chosen in the attached claims. The subject- matter which can be claimed comprises not only the combinations of features as set out in the attached claims but also any other combination of features in the claims, wherein each feature mentioned in the claims can be combined with any other feature or combination of other features in the claims. Furthermore, any of the embodiments and features described or depicted herein can be claimed in a separate claim and/or in any combination with any embodiment or feature described or depicted herein or with any of the features of the attached claims.

[0166] The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

[0167] Certain aspects of the disclosure are described above with reference to block and flow diagrams of systems, methods, apparatuses, and/or computer program products according to various implementations. It will be understood that one or more blocks of the block diagrams and flow diagrams, and combinations of blocks in the block diagrams and the flow diagrams, respectively, may be implemented by computer-executable program instructions. Likewise, some blocks of the block diagrams and flow diagrams may not necessarily need to be performed in the order presented, or may not necessarily need to be performed at all, according to some implementations.

[0168] These computer-executable program instructions may be loaded onto a special- purpose computer or other particular machine, a processor, or other programmable data processing apparatus to produce a particular machine, such that the instructions that execute on the computer, processor, or other programmable data processing apparatus create means for implementing one or more functions specified in the flow diagram block or blocks. These computer program instructions may also be stored in a computer-readable storage media or memory that may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable storage media produce an article of manufacture including instruction means that implement one or more functions specified in the flow diagram block or blocks. As an example, certain implementations may provide for a computer program product, comprising a computer- readable storage medium having a computer-readable program code or program instructions implemented therein, said computer-readable program code adapted to be executed to implement one or more functions specified in the flow diagram block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational elements or steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions that execute on the computer or other programmable apparatus provide elements or steps for implementing the functions specified in the flow diagram block or blocks.

[0169] Accordingly, blocks of the block diagrams and flow diagrams support combinations of means for performing the specified functions, combinations of elements or steps for performing the specified functions and program instruction means for performing the specified functions. It will also be understood that each block of the block diagrams and flow diagrams, and combinations of blocks in the block diagrams and flow diagrams, may be implemented by special-purpose, hardware-based computer systems that perform the specified functions, elements or steps, or combinations of special-purpose hardware and computer instructions.

[0170] Conditional language, such as, among others, "can," "could," "might," or "may," unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain implementations could include, while other implementations do not include, certain features, elements, and/or operations. Thus, such conditional language is not generally intended to imply that features, elements, and/or operations are in any way required for one or more implementations or that one or more implementations necessarily include logic for deciding, with or without user input or prompting, whether these features, elements, and/or operations are included or are to be performed in any particular implementation.

[0171] Many modifications and other implementations of the disclosure set forth herein will be apparent having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the disclosure is not to be limited to the specific implementations disclosed and that modifications and other implementations are intended to be included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

Claims

CLAIMS What is claimed is:

1. A device, the device comprising memory and processing circuitry configured to:

cause to send a measurement polling request to one or more station devices; identify one or more responses to the measurement polling request from a first subset of the one or more station devices;

determine a trigger frame comprising one or more fields, wherein the trigger frame notifies the first subset of the one or more station devices of one or more resource units;

set a location measurement report (LMR) feedback transmission indication in the trigger frame; and

cause to send the trigger frame to the first subset of the one or more station devices.

2. The device of claim 1, wherein the first subset is a group of station devices intending to perform one or more location measurements.

3. The device of claim 1, wherein the trigger frame comprises at least one of a polling trigger frame or an uplink sounding trigger frame.

4. The device of claim 1, wherein the LMR feedback transmission indication comprises a report to the first subset of the one or more stations devices.

5. The device of claim 1, wherein the LMR feedback transmission indication is included in at least one of a trigger dependent common information field of the trigger frame or a user information field of the trigger frame.

6. The device of one of claims 1-5, wherein the LMR feedback transmission indication comprises one or more bits to be sent to indicate a transmission status of an LMR feedback from the device to the first subset of the one or more station devices during an availability window.

7. The device of claim 6, wherein the transmission status is at least one of a transmission status of the LMR feedback within a current availability window, a transmission status of the LMR feedback within a pre-negotiated availability window, a transmission status of the LMR feedback within a subsequent availability window, or a transmission status of the LMR feedback based on a schedule advertised in a subsequent beacon frame.

8. The device of claim 1, further comprising a transceiver configured to transmit and receive wireless signals.

9. The device of claim 8, further comprising an antenna coupled to the transceiver.

10. A non-transitory computer-readable medium storing computer-executable instructions which when executed by one or more processors result in performing operations comprising:

identifying a measurement polling request from a device;

causing to send a response to the measurement polling request;

determining a trigger frame comprising one or more fields, wherein the trigger frame notifies a first subset of one or more station devices of one or more resource units;

determining a location measurement report (LMR) feedback transmission indication in the trigger frame; and

determining a low power state based on the LMR feedback transmission indication.

11. The non- transitory computer-readable medium of claim 10, wherein the response includes an indication to perform one or more location measurements with the device.

12. The non-transitory computer-readable medium of claim 10, wherein the LMR feedback transmission indication is included in at least one field of the trigger frame.

13. The device of claim 12, wherein the at least one field is a trigger dependent common information field or a user information field.

14. The non-transitory computer-readable medium of claim 10, wherein a first resource unit is used to send an uplink null data packet (NDP) to the device.

15. The non-transitory computer-readable medium of one of claims 10-14, wherein the LMR feedback indication transmission comprises one or more bits set to indicate a transmission status of an LMR feedback during an availability window.

16. The non-transitory computer-readable medium of claim 15, wherein the transmission status is at least one of a transmission status of the LMR feedback within a current availability window, a transmission status of the LMR feedback within a pre- negotiated availability window, a transmission status of the LMR feedback within a subsequent availability window, or a transmission status of the LMR feedback based on a schedule advertised in a subsequent beacon frame.

17. The non-transitory computer-readable medium of claim 15, wherein the availability window is at least one of a transmit opportunity (TXOP) period, a target wake time (TWT) period, or a service period (SP).

18. A method comprising:

causing, by one or more processors, to send a measurement polling request to one or more station devices;

identifying one or more responses to the measurement polling request from at first subset of the one or more station devices;

determining a trigger frame comprising one or more fields, wherein the trigger frame notifies a first subset of the one or more station devices of one or more resource units;

setting a location measurement report (LMR) feedback transmission indication in the trigger frame; and

19. The method of claim 18, wherein the first subset is a group of station devices intending to perform one or more location measurements.

20. The method of claim 18, wherein the LMR feedback transmission indication is included in at least one of a trigger dependent common information field of the trigger frame or a user information field of the trigger frame.

21. The method of one of claims 18-20, wherein the LMR feedback transmission indication comprises one or more bits to be sent to indicate a transmission status of an LMR feedback from the device to the first subset of the one or more station devices during an availability window.

22. The method of claim 21, wherein the transmission status is at least one of a transmission status of the LMR feedback within a current availability window, a transmission status of the LMR feedback within a pre-negotiated availability window, a transmission status of the LMR feedback within a subsequent availability window, or a transmission status of the LMR feedback based on a schedule advertised in a subsequent beacon frame.

23. An apparatus comprising means for:

identifying a measurement polling request from a device;

causing to send a response to the measurement polling request;

determining a trigger frame comprising one or more fields, wherein the trigger frame notifies a first subset of one or more station devices of one or more resource units; determining a location measurement report (LMR) feedback transmission indication in the trigger frame; and

24. The apparatus of claim 23, wherein the response includes an indication to perform one or more location measurements with the device.

25. The apparatus of one of claims 23-24, wherein the LMR feedback transmission indication is included in at least one field of the trigger frame.