WO2017026976A1

WO2017026976A1 - Apparatus, system and method of cellular-assisted fine time measurement

Info

Publication number: WO2017026976A1
Application number: PCT/US2015/000348
Authority: WO
Inventors: Ofer Hareuveni
Original assignee: Intel IP Corporation
Priority date: 2015-08-11
Filing date: 2015-12-24
Publication date: 2017-02-16
Also published as: TWI758253B; TW201707480A

Abstract

Some demonstrative embodiments include devices, systems and/or methods of cellular- assisted Fine Time Measurement (FTM). For example, a User Equipment (UE) may include a Wireless Local Area Network (WLAN) transceiver; a cellular transceiver to receive from a cellular network a cellular message including Fine Timing Measurement (FTM) capability information indicating a capability of one or more WLAN stations (STAs) to support FTM; and a Fine Timing Measurement (FTM) component configured to, based on the FTM capability information, trigger the WLAN transceiver to communicate FTM messages with the one or more WLAN STAs.

Description

APPARATUS, SYSTEM AND METHOD OF CELLULAR-ASSISTED FINE TIME

MEASUREMENT

CROSS REFERENCE

[001 ] This application claims the benefit of and priority from US Provisional Patent Application No. 62/203,621 entitled "LTE-ASS1STED FINE TIME MEASUREMENTS OVER WI-FI NETWORKS", filed August 1 1 , 2015, the entire disclosure of which is incorporated herein by reference. i

TECHNICAL FIELD

[002] Some embodiments described herein generally relate to cellular-assisted Fine Time Measurement (FTM).

BACKGROUND

[003] Various applications use range information between devices.

[004] The range information may enable, for example, users of the devices to meet new people and/or to use one or more services provided by the devices, e.g., when the devices are in proximity to each other. For example, a Smartphone can "unlock" a notebook, e.g., if the Smartphone is in within a predefined distance, e.g., less than one meter, from the notebook.

[005] The range information may enable, for example, one or more advertisers of services to interact with potential clients of the services, e.g., based on the range information. .

[006] The range information may be determined using a Time-of-Flight (ToF) measurement procedure. The ToF may be defined as the overall time a signal propagates from a first station to a second station and back to the first station. A distance between the first and second stations may be calculated based on the ToF value, for example, by dividing the ToF value by two and multiplying the result by the speed of light.

[007] Performing the ToF measurement procedure may consume a relatively large amount of power and may increase utilization of a wireless medium. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0010] Fig. 2 is a schematic illustration of a Fine Time Measurement (FTM) procedure, in

I

accordance with some demonstrative embodiments.

[001 1 ] Fig. 3 is a schematic illustration of ι elements of a User Equipment (UE), in accordance with some demonstrative embodiments.

[0012] Fig. 4 is a schematic illustration of cellular-assisted FTM in a collocated implementation, in accordance with some demonstrative embodiments.

[0013] Fig. 5 is a schematic illustration of cellular-assisted FTM in a non-collocated implementation, in accordance with some demonstrative embodiments.

[0014] Fig. 6 is a schematic flow-chart illustration of a method of providing cellular- assisted FTM information to a User Equipment (UE), in accordance with some demonstrative embodiments. '

[001 ] Fig. 7 is a schematic flow-chart illustration of a method of cellular-assisted FTM, in accordance with some demonstrative embodiments.

[0016] Fig. 8 is a schematic illustration of a product, in accordance with some demonstrative embodiments.

DETAILED DESCRIPTION

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

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

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

[0020] References to "one embodiment," "an embodiment," "demonstrative embodiment," "various embodiments," etc., indicate that the embodiment(s) so described may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes the particular feature, structure, or characteristic: Further, repeated use of the phrase "in one embodiment" does not necessarily refer to the same embodiment, although it may.

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

[0022] 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 Smartphone device, a server computer, a handheld computer, a handheld device, a Personal Digital Assistant (PDA) device, a handheld PDA device, an on-board device, an off-board device, an Internet of Things (IoT) device, a sensor device, a wearable device, a hybrid device, a vehicular device, a non- vehicular device, a mobile or portable device, : a consumer device, a non-mobile or nonportable 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 cellular network, a cellular node, a cellular device, a Wireless Local Area Network (WLAN), 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, vending machines, sell terminals,! and the like.

[0023] Some embodiments may be used in conjunction with devices and/or networks operating in accordance with existing 3rd Generation Partnership Project (3GPP) and/or Long Term Evolution (LTE) specifications (including 3GPP TS 36.300 ( 'TS 36.300 Evolved Universal Terrestrial Radio Access (E-UTRA): and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2, version J J.7.0 Release 11 ", September 2013); and/or 3GPP TS 36.331 (ETSI TS 136 331; VI 2.3.0 (2014-09); LTE; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification (3GPP TS 36.331 version 12.3.0 Release 12)) 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 Version 1.1, April 2011, Final specification) and/or future versions and/or derivatives thereof, devices and/or networks operating in accordance with existing IEEE 802.1 1 standards (including IEEE 802.1 1-201 {IEEE 802.11-2012, IEEE Standard for Information technology—Telecommunications and information exchange between systems Local and metropolitan area networ — Specific requirements Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications, March 29, 2012); and/or IEEEP802.1 IREVmc™ (IEEEP802.1 IREVmc™ _D3.0, June 2014, Draft Standard for Information Technology - Telecommunications and Information Exchange Between Systems - Local and Metropolitan Area Networks - Specific Requirements - Part 11 : Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications)), and/or future versions and/or derivatives thereof, devices and/or networks operating in accordance with existing IEEE 802. 16 standards {IEEE-Std 802.16, 2009 Edition, Air Interface for Fixed Broadband Wireless Access Systems; lEEE-Std 802.16e, 2005 Edition, Physical and Medium Access Control Layers for Combined Fixed and Mobile Operation in Licensed Bands; amendment to IEEE Std 802.16-2009, developed by Task Group m) and/or future versions and/or derivatives thereof, devices and/or networks operating in accordance with existing WirelessHD™ specifications and/or future versions and/or derivatives thereof, units and/or devices which are part of the above networks, and the like.

[0024] Some embodiments may be used in conjunction with one or more types of wireless communication signals and/or systems, for example, Radio Frequency (RF), Frequency- Division Multiplexing (FDM), Orthogonal FDM (OFDM), Single Carrier Frequency Division Multiple Access (SC-FDMA), Time-Division Multiplexing (TDM), Time-Division Multiple Access (TDMA), Extended TDMA (E-TDMA), General Packet Radio Service (GPRS), extended GPRS, Code-Division Multiple Access (CDMA), Wideband CDMA (WCDMA), CDMA 2000, single-carrier CDMA, multi-carrier CDMA, Multi-Carrier Modulation (MDM), Discrete Multi-Tone (DMJT), Bluetooth®, Global Positioning System (GPS), Wireless Fidelity (Wi-Fi), Wi-Max, ZigBee™, Ultra-Wideband (UWB), Global System for Mobile communication (GSM), second generation (2G), 2.5G, 3G, 3.5G, 4G, Fifth Generation (5G) mobile networks, 3GPP, Long Term Evolution (LTE) cellular system, LTE advance cellular system, High-Speed Downlink Packet Access (HSDPA), High-Speed Uplink Packet Access (HSUPA), High-Speed Packet Access (HSPA), HSPA+, Single Carrier Radio Transmission Technology (1 XRTT), Evolution-Data Optimized (EV-DO), Enhanced Data rates for GSM Evolution (EDGE), and the like. Other embodiments may be used in various other devices, systems and/or networks.

[0025] The term "wireless device", as used herein, includes, for example, a device capable of wireless communication, a communication device capable of wireless communication, a communication station capable of wireless communication, a portable or non-portable device capable of wireless communication, or the like. In some demonstrative embodiments, a wireless device may be or may include a peripheral that is integrated with a computer, or a peripheral that is attached to a computer. In some demonstrative embodiments, the term "wireless device" may optionally include a wireless service.

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

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

[0028] The term "antenna", as used herein, may include any suitable configuration, structure and/or arrangement of one or more antenna elements, components, units, assemblies and/or arrays. In some embodiments, the antenna may implement transmit and receive functionalities using separate transmit and receive antenna elements. In some embodiments, the antenna may implement transmit and receive functionalities using common and/or integrated transmit/receive elements. The antenna may include, for example, a phased array antenna, a single element antenna, a dipole antenna, a set of switched beam antennas, and/or the like.

[0029] The term "cell", as used herein, may include a combination of network resources, for example, downlink and optionally uplink resources. The resources may be controlled and/or allocated, for example, by a node (also referred to as a "base station"), or the like. The linking between a carrier frequency of the downlink resources and a carrier frequency of the uplink resources may be indicated in system information transmitted on the downlink resources.

[0030] Some demonstrative embodiments are described herein with respect to a LTE network. However, other embodiments may be, implemented in any other suitable cellular network or system, e.g., a Universal Mobile Telecommunications System (UMTS) cellular system, a GSM network, a 3G cellular network, a 4G cellular network, a 4.5G network, a 5G cellular network, a WiMAX cellular network, and the like.

[0031] Some demonstrative embodiments are described herein with respect to a WLAN system, a WiFi system, and/or a WiGig system. However, other embodiments may be implemented in any other suitable non-cellular network.

[0032] Some demonstrative embodiments are ' described herein with respect to a WLAN Termination (WT) node. However, other embodiments may be implemented in any other WLAN access device and/or WLAN access manager node and/or interface.

[0033] Some demonstrative embodiments are described herein with respect to one or more Fine Time Measurement (FTM) operations and/or communications, for example according to an FTM procedure and/or protocol. However, other embodiments may implement any other additional or alternative ranging measurements and/or communications, proximity measurements and/or communications, location estimation measurements and/or communications, and/or Time of Flight (ToF) measurements and/or communications, for example, according to any other additional or alternative procedure and/or protocol.

[0034] Some demonstrative embodiments may be used in conjunction with a Heterogeneous Network (HetNet), which may utilize a deployment of a mix of technologies, frequencies, cell sizes and/or network architectures, e.g., including cellular, millimeter wave ("mmWave" or "mmW"), and/or the like. In one example, the HetNet may include a radio access network having layers of different-sized cells ranging from large macrocells to small cells, for example, picocells and femtocells. Other embodiments may be used in conjunction with any other suitable wireless communication network.

[0035] Other embodiments may be used in conjunction with any other suitable wireless communication network.

[0036] Reference is now made to Fig. 1, which schematically illustrates a block diagram of a system 100, in accordance with some demonstrative embodiments.

[0037] As shown in Fig. 1 , in some demonstrative embodiments, system 100 may include one or more wireless communication devices capable of communicating content, data, information and/or signals via one or more wireless mediums 108. For example, system 100 may include at least one User Equipment (UE) 102 capable of communicating with one or more wireless communication networks, e.g., as described below. [0038] Wireless mediums 108 may include, for example, a radio channel, a cellular channel, an RF channel, a WiFi channel, an IR channel, and the like. One or more elements of system 100 may optionally be capable of communicating over any suitable wired communication links.

[0039] In some demonstrative embodiments, system 100 may include at least one cellular manager 104 to manage communication of a cellular network, e.g., as described below.

i

[0040] In some demonstrative embodiments,' cellular manager 104 may include, may operate as, and/or may perform the functionality of, an Evolved Node B (eNB). For example, cellular manager 104 may be configured to perform radio resource management (RRM), radio bearer control, radio admission control (access control), connection mobility management, resource scheduling between UEs and eNB radios, e.g., Dynamic allocation of resources to UEs in both uplink and downlink, header compression, link encryption of user data streams, packet routing of user data towards a destination, e.g., another eNB or an Evolved Packet Core (EPC), scheduling and/or transmitting paging messages, e.g., incoming calls and/or connection requests, broadcast information coordination, measurement reporting, and/or any other operations, communications, and/or functionality.

[0041] In other embodiments, cellular manager 104 may include any other functionality and/or may perform the functionality of any other cellular node, network controller, base station or any other node or network device. !

[0042] In one example, cellular manager 104 ;may be part of a UMTS. According to this example, cellular manager 104 may perform the functionality of a Radio Network Controller (RNC), which may control a plurality of Node B devices 157. For example, the node B may be configured to communicate directly with UEs, e.g., including UE 102, for example, using a Wideband Code Division Multiple Access (WCDMA) and/or Time Division Synchronous Code Division Multiple Access (TD-SCDMA) air interface technology. The RNC may include, for example, a UMTS RNC configured to control the Node B devices 157.

[0043] In some demonstrative embodiments, system 100 may include a WLAN Termination (WT) node 106, which may be configured to terminate a WLAN network interface, e.g., as described herein.

[0044] Some demonstrative embodiments are described below with respect to a WT node to terminate a WLAN network interface. In other embodiments and additional or alternative termination node may be used to terminate a network interface of any other non-cellular RAT network, for example, a Bluetooth network, a millimeter wave (mm Wave) network, and/or any other network, e.g., in addition to or instead of the WLAN network.

[0045] In some demonstrative embodiments,

node 106 may be configured to manage access to a non-cellular network 107, for example, a WLAN, e.g., a Basic Service Set (BSS).

ί

[0046] In some demonstrative embodiments, one or more functionalities of WT node 106 may be implemented, for example, in the form of, or as part of, a WLAN access device, for example, as part of a WLAN Access Point (AP), or a WLAN Access Controller (AC), as part of another device, or as a standalone device.

[0047] In other embodiments, WT node 106 may include any other functionality and/or may perform the functionality of any other device capable of controlling and/or managing WLAN radio access to one or more wired networks.

[0048] In one example, WT bode 106 may include, operate as, and/or perform the functionality of, an AP, e.g., configured to communicate directly with UE 102 via a WLAN link.

[0049] In another example, WT bode 106 may include, operate as, and/or perform the functionality of, an AC. According to this example, WT node 106 may control a plurality of AP devices, e.g., including Lightweight Access Point (LAP) devices 1 8.

[0050] In some demonstrative embodiments, UE 102 may include, for example, a Mobile Device (MD), a Station (ST A), a mobile computer, a laptop computer, a notebook computer, a tablet computer, an Ultrabook™ computer, an Internet of Things (IoT) device, a wearable device, a sensor device, a mobile internet device, a handheld computer, a handheld device, a storage 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 mobile phone, a cellular telephone, a PCS 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 video device, an audio device, an A/V device, a gaming device, a media player, a Smartphone, or the like.

[0051 ] In some demonstrative embodiments, UE 102, cellular manager 104 and/or WT node 106 may include one or more communication interfaces to perform communication between UE 102, cellular manager 104, WT node 106 and/or with one or more other wireless communication devices, e.g., as described below.

[0052] Some demonstrative embodiments include an interface 199 (also referred to as "the access device interface", "the horizontal interface", "the "Xw interface", "the X2-W interface" or "the cellular/WLAN interface"), . which may include circuitry and/or logic configured to interface, e.g., directly or indirectly, between a cellular network element, e.g., cellular manager 104, and a WLAN element, e.g., WT node 106, as described in detail below.

[0053] In some demonstrative embodiments, interface 199 may be implemented to interface between an eNB and a WT node, e.g., as described below. However, in other embodiments, the cellular/WLAN interface 199 may be implemented to directly interface between any other cellular device and any other WLAN device. In one example, the cellular/WLAN interface 199 may be implemented to directly interface between an eNB and a WLAN AP or WLAN AC. In another example, the cellular/WLAN interface 199 may be implemented to directly interface between a UMTS RNC and a WT node. In another example, the cellular/WLAN interface 199 may be implemented to directly interface between a UMTS RNC and a WLAN AP or AC.

[0054] In some demonstrative embodiments, interface 199 may be utilized to enhance and/or increase the efficiency of interworking, integration and/or management of the cellular and WLAN radio access technologies. ^!

[0055] In some demonstrative embodiments, interface 199 may be configured to perform and/or support one or more aggregation operations and/or functionalities, for example, to transfer traffic, e.g., in addition to transferring control plane information.

[0056] In some demonstrative embodiments, interface 199 may be utilized to improve efficiency of resource management, to provide efficient load balancing, and/or to improve mobility between Radio Access Technology (RAT) networks.

[0057] In some demonstrative embodiments, cellular manager 104 may include an interface ("Core Network (CN) interface") 146, e.g., a vertical interface, including circuitry and/or logic configured to communicate with one or more elements of a CN 183, e.g., an Evolved Packet Core (EPC).

[0058] In some demonstrative embodiments, CN interface 146 may include an S I vertical interface configured to communicate between cellular manager 104 and a Serving Gateway (S-GW) 185 according to an S I protocol, e.g., if cellular manager 104 performs the functionality of an eNB. According to this example, S-GW 187 may interface between cellular manager 104 and a Packet Data Network (PDN) Gateway (P-GW) 187.

[0059] In other embodiments, CN interface 146 may include any other vertical interface with one or more elements of CN 183. For example, cellular manger 104 may perform the functionality of an RNC, e.g., in a UMTS system. According to this example, CN interface 146 may include an Interface Unit Circuit Switch (Iu-CS) interface and/or an Interface Unit Packet Switch (Iu-PS) interface, to interface between the RNC and one or more packet- switched or circuit-switched CN elements.

[0060] In some demonstrative embodiments, cellular manager 104 may include an interface including circuitry and/or logic to communicate user plane traffic, directly or indirectly, between CN 183 and UE 102.

[0061] In some demonstrative embodiments, cellular manager 104 may communicate the user plane traffic directly with UE 102, for example, if cellular manager 104 performs the functionality of an eNB. According to these embodiments, cellular manager 104 may include an air interface, for example, a cellular transceiver (TRx) 167, including circuitry and/or logic configured to communicate with UE 102 via a cellular link.

[0062] In other embodiments, cellular manager 104 may communicate the user plane traffic with UE 102 via Node B 157, e.g., if cellular manager 104 performs the functionality of an RNC. According to these embodiments, cellular manager 104 may include a Node B interface 161 to communicate between the RNC and Node B 157. For example, Node B interface 161 may include an Interface Unit b (Iub).

[0063] In some demonstrative embodiments, cellular manager 104 may include a WT node interface 169 (also referred to as "WLAN control interface") including circuitry and/or logic configured to communicate with WT node 106 and/or with one or more WLAN stations (STAs), e.g., as described below. In one example, interface 169 may include an AP interface, e.g., if WLAN access device 106 performs the functionality of an AP. In another example, interface 169 may include an AC interface, e.g., if WLAN access device 106 performs the functionality of an AC. In another example, interface 169 may include any other non-cellular RAT interface to communicate with a node of a non-cellular RAT network.

[0064] In some demonstrative embodiments, WT node 106 may include a cell manager interface ("the cellular interface") 192 including circuitry and/or logic configured to communicate with cellular manager 104. In one example, interface 192 may include an eNB interface, e.g., if cellular manager 104 performs the functionality of an eNB. In another example, interface 192 may include a RNC interface, e.g., if cellular manager 104 perfonns the functionality of a RNC. i

[0065] In some demonstrative embodiments, interfaces 169 and 192 may be configured to communicate between cellular manager 104 and WT node 106 via a direct link of interface 199.

[0066] In some demonstrative embodiments, interface 199 may include a Point to Point (P2P) link, e.g., as described below.

[0067] In some demonstrative embodiments, interface 199 may be implemented by any wired and/or wireless link, e.g., using any suitable, Physical Layer (PHY) components and/or protocols.

[0068] In some demonstrative embodiments, WT node 106 may include a network interface 196 including circuitry and/or logic configured to communicate network traffic with a wired network 177, e.g., the Internet or any other network.

[0069] In some demonstrative embodiments, WLAN access device 104 may include a WLAN interface 193 including circuitry and/or logic configured to communicate the network traffic and/or any other traffic with UE 102 via a WLAN, directly or indirectly.

[0070] In some demonstrative embodiments, WT node 106 may communicate directly with UE 102 via WLAN link, for example, if WT node 106 operates as, or performs the functionality of, an AP. According to these embodiments, WLAN interface 193 may include a WLAN radio 194 including circuitry and/or logic configured to communicate the network traffic and/or any other traffic directly with UE 102, e.g., via a WLAN link between WT node 106 and UE 102, for example, if WT node 106 operates as, or performs the functionality of, an AP.

[0071 ] In some demonstrative embodiments, WT node 106 may indirectly communicate with UE 102, for example, if WT node 106 performs the functionality of an AC, or if WT node is an entity, which is separate from the WLAN AC or WLAN AP. According to these embodiments, WLAN interface 193 may include, for example, an AP interface, e.g., a LAP interface 159, to communicate the network traffic and/or any other traffic with LAP 1 58.

[0072] In some demonstrative embodiments, WLAN interface 193 may include any other additional or alternative interfaces to directly and/or indirectly communicate via the WLAN. [0073] In some demonstrative embodiments, UE 102 may include a non-cellular RAT transceiver (TRx), for example, a WLAN TRx 163, including circuitry and/or logic configured to communicate with a WLAN device, e.g., with WT node 106 and/or with LAP 158, via the WLAN link. Some embodiments are described below with respect to a UE, e.g., UE 102, including a WLAN TRx to communicate over a WLAN. In other embodiments, the UE may include any additional or alternative non-cellular RAT TRx, e.g., a Bluetooth TRx and/or any other TRx, to communicate over any additional or alternative non-cellular RAT network.

[0074] In some demonstrative embodiments, UE 102 may include a cellular transceiver (TRx) 165 including circuitry and/or logic configured to communicate with a cellular network, for example, via a cellular device, e.g., cellular manager 104 and/or Node B 157, via the cellular link.

[0075] In some demonstrative embodiments, WLAN TRx 163, cellular TRx 165, cellular TRx 167 and/or WLAN radio 194 may include one or more wireless transmitters, receivers and/or transceivers including circuitry and/or logic to process, encode, decode, send and/or receive wireless communication signals, RF signals, frames, blocks, transmission streams, packets, messages, data items, and/or data.

[0076] In some demonstrative embodiments, WLAN TRx 167 and/or WLAN radio 194 may include one or more wireless receivers (Rx) including circuitry and/or logic to receive wireless communication signals, RF signals, frames, blocks, transmission streams, packets, messages, data items, and/or data; and/or one or more wireless transmitters (Tx) including circuitry and/or logic to send wireless communication signals, RF signals, frames, blocks, transmission streams, packets, messages, data items, and/or data. For example, WLAN TRx 167 and/or WLAN radio 194 may include circuitry; logic; Radio Frequency (RF) elements, circuitry and/or logic; baseband elements, circuitry and/or logic; modulation elements, circuitry and/or logic; demodulation elements, circuitry and/or logic; amplifiers; analog to digital and/or digital to analog converters; filters; and/or the like.

[0077] In some demonstrative embodiments, cellular TRx 167 and/or cellular TRx 165 may include a multiple input multiple output (MIMO) transmitters receivers system (not shown), which may be capable of performing antenna beamforming methods, if desired. In other embodiments, cellular TRx 167 and/or cellular TRx 165 may include any other transmitters and/or receivers. [0078] In some demonstrative embodiments, cellular TRx 167 and/or cellular TRx 165 may include LTE, WCDMA and/or TD-SCDMA modulator and/or demodulator circuitry (not shown) configured to modulate and/or demodulate downlink signals to be communicated over downlink channels, e.g., between cellular, manager 104 and UE 102, and/or uplink signals to be communicated over uplink channels, e.g., between UE 102 and cellular manager 104. In other embodiments, cellular TRx 167 and/or cellular TRx 165 may include any other modulators and/or demodulators. '.

[0079] In some demonstrative embodiments, cellular TRx 167 and/or cellular TRx 165 may include a turbo decoder and/or a turbo encoder (not shown) including circuitry and/or logic for encoding and/or decoding data bits into data symbols, if desired. In some demonstrative embodiments, cellular TRx 167 and/or cellular TRx 165 may include OFDM and/or SC- FDMA modulators and/or demodulators (not shown) configured to communicate OFDM signals over downlink (DL) channels, and/or SC-FDMA signals over uplink (UL) channels.

[0080] In some demonstrative embodiments, UE .102 may establish a WLAN link with a WLAN STA, e.g., a WLAN AP. For example, WLAN TRx 163 may perform the functionality of one or more STAs, e.g., one or more WiFi STAs, WLAN STAs, and/or DMG STAs. The WLAN link may include an uplink and/or a downlink. The WLAN downlink may include, for example, a unidirectional link from the WLAN AP to the one or more STAs. The uplink may include, for example, a unidirectional link from a STA to the WLAN AP.

[0081] In some demonstrative embodiments, UE 102, cellular manager 104, and/or WT node 106, may include, or may be associated with, one or more antennas. In one example, WLAN TRx 163 and/or cellular TRx 165 may be associated with at least two antennas, e.g., antennas 1 12 and 1 14, or any other number of antennas, e.g., one antenna or more than two antennas; cellular TRx 167 may be associated with at least two antennas, e.g., antennas 132 and 134, or any other number of antennas, e.g., one antenna or more than two antennas; and/or WLAN radio 194 may be associated with one or more antennas 135.

[0082] In some demonstrative embodiments, antennas 1 12, 1 14, 132, 134 and/or 135 may include any type of antennas suitable for transmitting and/or receiving wireless communication signals, blocks, frames, transmission streams, packets, messages and/or data. For example, antennas 1 12, 1 14, 132, 134 and/or 135 may include any suitable configuration, structure and/or arrangement of one or more antenna elements, components, units, assemblies and/or arrays. For example, antennas 1 12, 1 14, 132, 134 and/or 135 may include a phased array antenna, a dipole antenna, a single element antenna, a set of switched beam antennas, and/or the like.

[0083] In some embodiments, antennas 1 12, 1 14, 132, 134 and/or 135 may implement transmit and receive functionalities using separate transmit and receive antenna elements. In some embodiments, antennas 1 12, 1 14, 132, 134 and/or 135 may implement transmit and receive functionalities using common and/or integrated transmit/receive elements.

[0084] In some demonstrative embodiments, cellular manager 104 may include at least one controller 182, UE 102 may include at least one controller 197, and/or WT node 106 may include at least one controller 149. Controllers .182, 197, and/or 149 may be configured to trigger one or more communications, may generate and/or trigger communication of one or more messages and/or transmissions, and/or may perform one or more functionalities, operations and/or procedures, e.g., as described below.

[0085] In some demonstrative embodiments, controllers 182, 197, and/or 149 may include circuitry and/or logic, e.g., one or more processors including circuitry and/or logic, memory circuitry and/or logic, Media-Access Control (MAC) circuitry and/or logic, Physical Layer (PHY) circuitry and/or logic, and/or any other circuitry and/or logic, configured to perform the functionality of controllers 182, 197, and/or 149, respectively. Additionally or alternatively, one or more functionalities of controllers 182, 197, and/or 149 may be implemented by logic, which may be executed by a machine and/or one or more processors, e.g., as described below.

[0086] In one example, controller 182 may include circuitry and/or logic, for example, one or more processors including circuitry and/or logic, configured to cause, request and/or trigger cellular manager 104 to perform one or more operations, communications and/or functionalities, e.g., as described herein. In one example, controller 197 may include circuitry and/or logic, for example, one or more processors including circuitry and/or logic, configured to cause, request and/or trigger UE 102 to perform one or more operations, communications and/or functionalities, e.g., as described herein. In one example, controller 149 may include circuitry and/or logic, for example, one or more processors including circuitry and/or logic, configured to cause, request and/or trigger WT node 106 to perform one or more operations, communications and/or functionalities, e.g., as described herein.

[0087] In some demonstrative embodiments, cellular node may include a message processor 144 configured to generate, process and/or access one or messages communicated by cellular manager 104. In one example, message processor 144 may be configured to generate one or more messages to be transmitted by cellular manager 104, and/or message processor 144 may be configured to access and/or to process one or more messages received by cellular manager 104, e.g., as described below.

[0088] In some demonstrative embodiments, UE 102 may include a message processor 198 configured to generate, process and/or access one or messages communicated by UE 102. In one example, message processor 198 may be configured to generate one or more messages to be transmitted by UE 102, and/or message processor 198 may be configured to access and/or ^' to process one or more messages received by UE 102, e.g., as described below.

[0089] In some demonstrative embodiments, WT node 106 may include a message processor 150 configured to generate, process and/or access one or messages communicated by WT node 106. In one example, message processor 150 may be configured to generate one or more messages to be transmitted by WT node 106, and/or message processor 150 may be configured to access and/or to process one or more messages received by WT node 106, e.g., as described below.

[0090] In some demonstrative embodiments, message processors 144, 198 and/or 150 may include circuitry, e.g., processor circuitry, memory circuitry, Media-Access Control (MAC) circuitry, Physical Layer (PHY) circuitry, and/or any other circuitry, configured to perform the functionality of message processors 144, 198 and/or 150. Additionally or alternatively, one or more functionalities of message processors 144, 198 and/or 150 may be implemented by logic, which may be executed by a machine and/or one or more processors, e.g., as described below.

[0091] In some demonstrative embodiments, at least part of the functionality of message processor 144 may be implemented as part of cellular TRx 167 and/or WT node interface 169; at least part of the functionality of message processor 198 may be implemented as part of cellular TRx 165 and/or WLAN TRx 163; and/or at least part of the functionality of message processor 150 may be implemented as part of interface 192 and/or interface 193.

[0092] In some demonstrative embodiments, at least part of the functionality of message processor 144 may be implemented as part of controller 182, at least part of the functionality of message processor 198 may be implemented as part of controller 197, and/or at least part of the functionality of message processor 150 may be implemented as part of controller 149. [0093] In other embodiments, at least part of the functionality of message processor 144 may be implemented as part of any other element of cellular manager 104, at least part of the functionality of message processor 198 may be implemented as part of any other element of UE 102, and/or at least part of the functionality of message processor 150 may be implemented as part of any other element of WT node 106.

[0094] In some demonstrative embodiments, cellular manager 104, WT node 106, and/or UE 102 may also include, for example, one or more of a processor, an input unit, an output unit, a memory unit, and/or a storage unit. For example, cellular manager 104 may include a processor 173 and/or a memory 174; WT node 106 may include a processor 175 and/or a memory 176; and/or UE 102 may include a memory 151 , a processor 152, an input unit 153, an output unit 154, and/or a storage unit 155. UE 102, cellular manager 104 and/or WT node 106 may optionally include other suitable hardware components and/or software components. In some demonstrative embodiments, some or all of the components of one or more of UE 102, cellular manager 104 and/or WT node 106 may be enclosed in a common housing or packaging, and may be interconnected or operably associated using one or more wired or wireless links. In other embodiments, components of one or more of UE 102, cellular manager 104 and/or WT node 106 may be distributed among multiple or separate devices.

[0095] In some demonstrative embodiments, processors 173, 175 and/or 152 may include, for example, a Central Processing Unit (CPU), a Digital Signal Processor (DSP), one or more processor cores, a single-core processor, a dual-core processor, a multiple-core processor, a microprocessor, a host processor, a controller, a plurality of processors or controllers, a chip, a microchip, one or more circuits, circuitry, a logic unit, an Integrated Circuit (IC), an Application-Specific IC (ASIC), or any other suitable multi-purpose or specific processor or controller. For example, processor 173 may execute instructions, for example, of an Operating System (OS) of cellular manager 104 and/or of one or more suitable applications; processor 175 may execute instructions of an OS of WT node 106 and/or of one or more suitable applications; and/or processor 152 may execute instructions of an OS of UE 102 and/or of one or more suitable applications.

[0096] In some demonstrative embodiments, input unit 153 may include, for example, a keyboard, a keypad, a mouse, a touch-screen, a touch-pad, a track-ball, a stylus, a microphone, or other suitable pointing device or input device. Output unit 154 includes, for example, a monitor, a screen, a touch-screen, a flat panel display, a Light Emitting Diode (LED) display unit, a Liquid Crystal Display (LCD) display unit, a plasma display unit, one or more audio speakers or earphones, or other suitable output devices.

[0097] In some demonstrative embodiments, memory unit 174, 176 and/or 151 may include, for example, a Random Access Memory (RAM), a Read Only Memory (ROM), a Dynamic RAM (DRAM), a Synchronous DRAM (SD-RAM), a flash memory, a volatile memory, a non-volatile memory, a cache memory, a buffer, a short term memory unit, a long term memory unit, or other suitable memory units. Storage unit 155 includes, for example, a hard disk drive, a floppy disk drive, a Compact Disk (CD) drive, a CD-ROM drive, a DVD drive, or other suitable removable or non-removable storage units. For example, memory unit 174 may store data processed by cellular manager 104; and/or memory unit 176 may store data processed by WT node 106.

[0098] In some demonstrative embodiments, UE 102 may be configured to utilize a cellular connection, e.g., a LTE cellular connection or any other cellular connection, to communicate with cellular manager 104, and a WLAN connection, e.g., a Wireless-Fidelity (WiFi) connection, a mm Wave connection, a wireless P2P connection, or any other WLAN connection, to communicate with a WLAN AP ;Connected to, or implemented by, WT node 106. :

j

[0099] In some demonstrative embodiments, one or more elements of system 100 may perform the functionality of a HetNet, which may utilize a deployment of a mix of technologies, frequencies, cell sizes and/or network architectures, for example, including cellular, WLAN, and/or the like.

[00100] For example, the HetNet may be configured to provide a service through a first wireless communication environment, e.g., a cellular network, and to maintain the service when switching to another communication environment, e.g., WLAN. The HetNet architecture may enable utilizing a mixture of wireless communication environments, e.g., a WLAN environment and a cellular environment, for example, to optimally respond to rapid changes in customer demand, reduce power consumption, reduce cost, increase efficiency and/or achieve any other benefit.

[00101] In one example, system 100 may utilize a Multi-tier, Multi-Radio Access Technology (Multi-RAT) Het-Net architecture, including a tier of small cells, e.g., pico, femto, relay stations, WiFi APs, and the like, overlaid on top of a macro cellular deployment to augment network capacity. [00102] In another example, system 100 may utilize Multi-RAT small cells integrating multiple radios such as WiFi and 3GPP air interfaces in a single infrastructure device.

[00103] In other embodiments, system 100 may implement any other architecture and/or deployment.

[00104] In some demonstrative embodiments, UE 102 and/or cellular manager 104 may be configured to establish one or more Evolved UMTS Terrestrial Radio Access Network (E- UTRAN) Radio Access Bearers (E-RABs) between UE 102 and S-GW 185, e.g., via cellular manager 104.

[00105] In some demonstrative embodiments, ,UE 102, cellular manager 104 and/or WT node 106 may be configured to communicate according to a LTE/WLAN protocol aggregation (WLA) scheme, e.g., as described below.

[00106] In some demonstrative embodiments, the LTE/WLAN protocol stack aggregation may be configured to enable LTE interworking with a WLAN protocol stack.

[00107] In some demonstrative embodiments, the LTE/WLAN protocol stack aggregation may be configured to anchor WLAN mobility at the cellular manager 104.

[00108] In some demonstrative embodiments, cellular manager 104 and/or WT node 106 may be configured according to a network architecture of a non-collocated LTE/WLAN aggregation, e.g., in which cellular manager 104 and WT node 106 are not collocated as part of an integrated device and/or in which interface il 99 is not an internal interface.

[00109] In some demonstrative embodiments, cellular manager 104 and/or WT node 106 may be configured according to a network architecture of a collocated LTE/WLAN aggregation, e.g., in which cellular manager 104 and WT node 106 may be collocated as part of an integrated device and/or in which interface 199 is an internal interface.

[001 10] In some demonstrative embodiments, UE 102 may include a Fine Time Measurement (FTM) component 145 configured to perform one or more FTM operations, communications and/or procedures with one or more WLAN stations (STAs) 1 19, e.g., as described below.

[001 1 1 ] In some demonstrative embodiments, FTM component 145 may include, or may be implemented, using suitable circuitry and/or logic, e.g., controller circuitry and/or logic, scheduler circuitry and/or logic, processor circuitry and/or logic, memory circuitry and/or logic, and/or any other circuitry and/or logic, which may be configured to perform at least part of the functionality of FTM component 145. Additionally or alternatively, one or more functionalities of FTM component 145 may be implemented by logic, which may be executed by a machine and/or one or more processors, e.g., as described below.

[001 12] In some demonstrative embodiments, FTM component 145 may be configured to perform one or more operations of, and/or at least part of the functionality of, message processor 198 and/or controller 197, for example, to trigger communication of one or more FTM messages, e.g., as described below. ^'

[001 13] In some demonstrative embodiments, at least part of the functionality of FTM component 145 may be implemented by an integrated circuit, for example, a chip, e.g., a System on Chip (SoC). In one example, the chip or SoC may be configured to perform one or more functionalities of cellular transceiver 165 and/or WLAN TRx 163. For example, the chip or SoC may include one or more elements of FTM component 145, and/or one or more elements of cellular transceiver 165 and/or WLAN TRx 163. In one example, FTM component 145, cellular transceiver 163, and WLAN TRx 163 may be implemented as part of the chip or SoC. In other embodiments, FTM component 145, cellular transceiver 165 and/or WLAN TRx 163 may be implemented by one or more additional or alternative elements of UE 102.

[001 14] In some demonstrative embodiments, FTM component 145 may be configured to trigger the FTM measurements, for example, periodically and/or or upon a request from an application executed by UE 102, for example, to determine an accurate location of UE 102, e.g., as described below.

[001 15] In some demonstrative embodiments,■ the one or more WLAN STAs 1 19 may include one or more WLAN APs, one or more FTM responders, one or more dedicated responder stations, one or more non-dedicated responder stations, one or more stations having at least capabilities of an FTM responder, one or more stationary devices having a known geo-location, one or more mobile devices, one or more UEs, one or more routers, and/or any other device and/or station capable of communicating one or more FTM messages, for example, as part of an FTM procedure, e.g., as described below.

[001 16] In some demonstrative embodiments, WT node 106 may be configured to perform the functionality of a WLAN STA 1 19, for example, in a collocated LTE/WLAN aggregation implementation. [001 17] In some demonstrative embodiments, node 106 may be configured to control and/or communicate with one or more WLAN STAs ,1 19, e.g., a plurality of WLAN APs and/or responders.

[001 18] In some demonstrative embodiments, FTM component 145 may be configured to perform one or more measurements according to an FTM protocol, for example, in accordance with an IEEE 802.1 1 Specification, e.g., an IEEE 802.1 I RevMC Specification and/or any other specification and/or protocol.

[001 19] In some demonstrative embodiments, FTM component 145 may be configured to perform one or more operations of an FTM initiator to perform one or more FTM measurements with one or more FTM responders, e.g., WLAN stations 1 19.

[00120] In some demonstrative embodiments, FTM component 145 may be configured to perform one or more proximity, ranging, and/or location estimation measurements, e.g., in an indoor location, based on the FTM measurements. For example, the FTM measurements may provide a relatively accurate estimation of location, range and/or proximity, e.g., in an indoor location.

[00121] Some demonstrative embodiments are ; described herein with respect to an FTM component, e.g., FTM component 145, configured to perform measurements according to an FTM protocol and/or procedure. However, in other embodiments, the FTM component may be configured to perform any other additional or alternative type of Time of Flight (ToF) measurements, ranging measurements, proximity measurements, and/or location estimation measurements, e.g., according to any additional or alternative protocol and/or procedure.

[00122] Reference is made to Fig. 2, which schematically illustrates a sequence diagram, which demonstrates operations and interactions between a first wireless communication device 202 ("Initiating STA" or "initiator") and a second wireless communication device 240 ("Responding STA" or "responder"), of an FTM procedure 200, in accordance with some demonstrative embodiments. For example, device 202 may perform the functionality of UE 102 (Fig. 1 ), and/or device 240 may perform the functionality of a WLAN STA 1 19 (Fig. 1 ).

[00123] As shown in Fig. 2, device 202 may transmit to device 240 an FTM request message 23 1 to request to perform the FTM procedure 200 with device 240. For example, FTM component 145 (Fig. 1) may trigger, instruct, cause and/or request WLAN TRx 163 (Fig. 1) to transmit the FTM request message 231. ,

[00124] As shown in Fig. 2, device 240 may transmit an FTM request acknowledgement (ACK.) 232 to device 202, to acknowledge receipt of the FTM request message 23 1 , and to confirm the request to perform the FTM procedure. For example, FTM component 145 (Fig. l).may trigger, instruct, cause and/or request WLAN TRx 163 (Fig. 1) to process reception of the FTM request ACK message 232.

[00125] As shown in Fig. 2, FTM procedure 200 may include an FTM measurement period, during which devices 202 and 240 may communicate FTM measurement frames, e.g., as described below. For example, FTM component 145 (Fig. 1) may trigger, instruct, cause and/or request WLAN TRx 163 (Fig. 1) to communicate one or more messages during the FTM measurement period, e.g., as described below.

[00126] In some demonstrative embodiments, devices 202 and/or 240 may communicate the FTM measurement frames between devices 202 and 240 during the FTM measurement period, for example, to determine a Time of Flight (ToF) value between devices 202 and 240.

[00127] In some demonstrative embodiments, as shown in Fig. 2, device 240 may transmit an FTM message 234 to device 202, at a time, j denoted tl. The time // may be a Time of

Departure (ToD), denoted ToD(M), of message 234.

i

[00128] In some demonstrative embodiments, as shown in Fig. 2, device 202 may receive message 234 and may determine a time, denoted (2, e.g., by determining a Time of Arrival (ToA), denoted ToA(M), of message 234. For example, FTM component 145 (Fig. 1 ) may be configured to trigger, instruct, cause and/or request WLAN TRx 163 (Fig. 1 ) to process receipt of message 234, and/or FTM component 145 (Fig. 1 ) may be configured to determine the ToA of message 234.

[00129] In some demonstrative embodiments, as shown in Fig. 2, device 202 may transmit a message 236 to device 240, at a time, denoted t3. Message 236 may include, for example, an acknowledgement message transmitted in response to FTM message 234. The time t3 may be a ToD, denoted ToD(ACK), of the message 236. For example, FTM component 145 (Fig. 1) may be configured to trigger, instruct, cause and/or request WLAN TRx 163 (Fig. 1) to transmit message 236, and/or FTM component 145 (Fig. 1) may be configured to determine the ToD of message 236.

[00130] In some demonstrative embodiments, as shown in Fig. 2, device 240 may receive message 236 and may determine a time, denoted t4, e.g., by determining a ToA, denoted ToA (ACK), of message 236. [00131] In some demonstrative embodiments, as shown in Fig. 2, device 240 may transmit an FTM message 238 to device 202. Message 238 may include, for example, infonnation corresponding to the time tl and/or the time t4. For example, message 238 may include a timestamp, e.g., a ToD timestamp, including the time tl, and a timestamp, e.g., a ToA timestamp, including the time t4. '

[00132] In some demonstrative embodiments, as shown in Fig. 2, device 202 may receive message 238. For example, FTM component 145 (Fig. 1) may be configured to trigger, instruct, cause and/or request WLAN TRx 163 (Fig. 1 ) to process receipt of message 238, and/or FTM component 145 (Fig. 1) may be configured to access, extract and/or process the infonnation corresponding to the time tl and/or the time t4.

[00133] In some demonstrative embodiments, as shown in Fig. 2, device 202 may transmit a message 239 to device 240. Message 239 may 'include, for example, an acknowledgement message transmitted in response to message 238. For example, FTM component 145 (Fig. 1) may be configured to trigger, instruct, cause and/or request WLAN TRx 163 (Fig. 1 ) to transmit message 239.

[00134] In some demonstrative embodiments, device 202 may determine a ToF between device 202 and device 240, for example, based on message 238. For example, FTM component 145 (Fig. 1) may be configured determine the ToF, e.g., as described below.

[00135] For example, device 202 may determine the ToF based on an average, or any other function, applied to the time values tl, t2, t3 and t4. For example, device 202 may determine the ToF, e.g., as follows:

ToF= [(t4-tl)-(t3-t2)]/2 (1)

[00136] In some demonstrative embodiments, device 202 may determine the distance between devices 202 and 240 based on the calculated ToF.

[00137] For example, device 202 may determine the distance, denoted r*, e.g., as follows:

rk =ToF*C (2)

wherein C denotes the radio wave propagation speed.

[00138] Referring back to Fig. 1 , in some demonstrative embodiments, FTM component 145 may be configured to trigger WLAN TRx 163 to communicate one or more FTM messages with one or more WLAN STAs 1 19, for example, according to the FTM procedure 200 (Fig. 2). [00139] In some demonstrative embodiments, FTM component 145 (Fig. 1) may be configured to determine the range or distance between UE 102 and a WLAN STA 1 19 (Fig. 1), for example, according to Equations 1 and/or 2.

[00140] In some demonstrative embodiments, a location of UE 102, e.g., an absolute location of UE 102, may be determined based on the estimated range r*.

[00141] For example, the UE 102 may determine two or more ToF values and/or range values, e.g., according to Equations 1 and/or 2, with respect to two or more respective WLAN STAs 1 19, e.g., at least three or four WLAN STAs 1 19. The location of UE 102 may be determined based on the two or more ToF values, for example, by trilateration.

[00142] In some demonstrative embodiments, FTM component 145 may be configured to provide, e.g., to one or more applications executed by UE 102, one more range values, proximity values, and/or location values, which may be determined based on the FTM procedure. For example, the applications may include a social application, a file sharing application, a media application, a gaming application, a navigation application, a consumer application, a printing service, a displaying service, and/or any other application and/or service, which may be configured to utilize the range values, proximity values, and/or location values.

[00143] In some demonstrative embodiments, it may be power consuming and/or time consuming for UE 102 to perform one or more discovery and/or scanning operations to discover a plurality of proximate WLAN STAs 1 19, e.g., at least three WLAN STA 1 19, which also support FTM, and/or to discover information regarding the plurality of proximate WLAN STAs 1 19, for example, operating channels of the plurality of proximate WLAN STAs 1 19.

[00144] For example, a typical deployment of FTM responders may be configured to communicate over an unlicensed frequency band, for example, the 5.2-5.8 Gigahertz (GHz) frequency band. Due to regulatory restrictions in most countries, a device may only be allowed to search for Access Points in this frequency band by performing only passive scanning, for example, by searching for beacons transmitted by access points, e.g., at a typical rate of once every 102.4 milliseconds (msec). This passive scanning may typically result in a scanning time of a few seconds, for example, to scan over all available channels. A power consumption of such a discovery process may be relatively high, for example, even as much as an order of magnitude larger that a power consumption required for an actual exchange of frames used for timing measurements. Accordingly, the discovery process may impose a very high overhead, e.g., in terms of power consumption and/or time, for perfonning an FTM procedure. Although some mechanisms may enable to improve power consumption of proximity measurements, such mechanisms do not address the issue of reducing the time and/or power consumption for the discovery of WLAN STAs, e.g., to perform accurate positioning.

[00145] In some demonstrative embodiments, cellular manager 104 and/or UE 102 may be configured to enable UE 102 to perform an FTM procedure, for example, while avoiding or even eliminating a discovery procedure to discover WLAN STAs 1 19, which may be suitable for the FTM procedure, e.g., as described below.

[00146] In some demonstrative embodiments, cellular manager 104 may be configured to provide to UE 102 information regarding a capability of one or more WLAN STAs 1 19 to support FTM, e.g., as described below.

[00147] In some demonstrative embodiments, cellular manager 104 may be configured to provide to UE 102 information regarding one or more operating channels and/or any other attributes of one or more WLAN STAs 1 19 to support FTM, e.g., as described below.

[00148] In some demonstrative embodiments, cellular manager 104 and/or WT node 106 may be configured to utilize interface 199 to provide a flow control interface between the cellular manager 104 and collocated or non-cpllocated Wi-Fi Access Points or multiple Access Points controlled by a Network Controller or Router, for example, WLAN STAs 1 19, e.g., as described below. ¹

[00149] In some demonstrative embodiments, a Radio Resource Control (RRC) protocol between a RAN and UE 102 over a primary cell, e.g., LTE, may be extended, for example, to provide UE 102 with information of WLAN STAs, for example, a list of Access Point IDs, which may be used by the UE 102 for WiFi Link Aggregation (WLA), for example, while being in the coverage area of the cellular cell.

[00150] In some demonstrative embodiments, cellular manager 104 may use RRC signaling to inform UE 102 of FTM capabilities, and, optionally, operating channels and/or any other additional or alternative attributes, of the APs, e.g., as described below.

[00151 ] In some demonstrative embodiments, UE 102 may be configured to use the RRC signaling information, for example, to selectively avoid and/or skip over a channel scanning procedure, e.g., for Access Points supporting FTM. As a result, UE 102 may be able to significantly reduce power consumption, time to locate responders, and/or time spent off an operating channel of UE 102, which may, for example, impact User Quality of Service.

[00152] In some demonstrative embodiments, message processor 144 may be configured to generate a cellular message including Fine Timing Measurement (FTM) capability information indicating a capability of one or more WLAN STAs 1 19 to support FTM, e.g., as described below.

[00153] In some demonstrative embodiments, the cellular interface of cellular manager 104 may be configured to send the cellular message to UE 102 via a cellular link. For example, controller 182 may be configured to trigger, cause, instruct and/or request cellular TRx 167 to transmit the cellular message to UE 102.

[00154] In some demonstrative embodiments, the cellular message may include a RRC message, e.g., as described below. For example, message processor 144 may be configured to generate an RRC message including the FTM capability information, and controller 182 may be configured to trigger cellular TRx 167 to transmit the RRC message to UE 102. In other embodiments, the FTM capability information may be transmitted as part of any other cellular message, for example, a UE-dedicated message or a broadcast cellular message.

[00155] In some demonstrative embodiments, the FTM capability information may include, for example, at least an identifier to identify a WLAN STA 1 19 capable of responding to an FTM request, e.g., as described below. For example, the FTM capability information may include, for example, at least an identifier to identify a WLAN STA 1 19 capable of responding to FTM request 231 (Fig. 1) and/or performing FTM procedure 200 (Fig. 2).

[001 6] In some demonstrative embodiments, the FTM capability information may include a plurality of identifiers of a plurality of WLAN STAs 1 19 capable of performing an FTM procedure, for example, in the form of a list of WLAN STAs 1 19.

[00157] In some demonstrative embodiments, the identifier of the WLAN STA 1 19 may include, for example, a Media Access Control (MAC) address of the WLAN STA 1 19, a Basic Service Set Identifier (BSSID) of the WLAN STA 1 19, and/or any other identifier to identify WLAN STA 1 19.

[00158] In some demonstrative embodiments, the FTM capability information may include information of one or more attributes of the one or more WLAN STAs 1 19, for example, including one or more attributes to enable UE 102 to discover WLAN STAs 1 19 and/or communicate FTM messages with WLAN STAs 1 19. [00159] In some demonstrative embodiments, the FTM capability information corresponding to a WLAN STA 1 19 may include, for example, at least radio frequency information indicating a wireless communication channel : to communicate FTM messages with the WLAN STA 1 19. '

[00160] In some demonstrative embodiments, the FTM capability information may include, for example, a plurality of information elements corresponding to a respective plurality of WLAN STAs 1 19, e.g., in the form of a list. For example, an information element corresponding to a WLAN AP 1 19 may include, for example, at least an identifier of the WLAN AP, e.g., a MAC address and/or a BSSID; channel information indicating one or more channels; an indication of one or more FTM capabilities for performing FTM; and/or an indication of one or more supported rates and/or bandwidth for FTM exchange, e.g., as described below. !

i

[00161 ] In some demonstrative embodiments, the indication of one or more FTM capabilities may include, for example, at least an FTM Format and Bandwidth field, e.g., in accordance with an IEEE 802. 1 1 RevMC Specification; an FTM Responder Location type, e.g., CIVIC location using ANQP-element, Public using AP Location Public Identifier URI/FQDN, Neighbor report, or other; and/or an FTM Responder Location.

[00162] In some demonstrative embodiments, the RRC message including the FTM capabilities information may include, for example, a System Information Block (SIB) Type 1 7 message, and/or any other type of message, j

[00163] In some demonstrative embodiments, ;the FTM capabilities information may be included for example, as part of an information element, for example, as part of a LateNonCriticalExtension element, e.g., as follows:

lateNonCriticalExtension ::= SEQUENCE ^'{

WLAN-Identifiers-rl2 ::= SEQUENCE {

ssid-rl 2 OCTET STRING (SIZE (1..32)) OPTIONAL, bssid-rl 2 OCTET STRING (SIZE (6)) OPTIONAL, hessid-r! 2 OCTET STRING (SIZE (6)) OPTIONAL,

}

wlan-band ENUMERATED { 5000Mhz, 2400Mhz OPTIONAL,

wlan-channel-id INTEGER (0..255) OPTIONAL,

FTMFormatAndBandwidth INTEGER (0..63) OPTIONAL,

FTMResponderLocationType ENUMERATED {CIVIC location-rl 3,

APLocationPublicIdentifierURl-rl3, APLocationPublicIdentifierFQDN-rl 3,

NeighborReport-rl 3, other} OPTIONAL,

FTM Responder Location OCTET STRING 3 (SIZE (L.maxFTMResponderLocation-rl 3)) OPTIONAL,

[00164] In other embodiments, the FTM capabilities information may be included as part of any other message type, message format, information element, and/or format.

[00165] In some demonstrative embodiments, cellular manager 104 may be configured to detennine the FTM capability information, for example, based on information ("WLAN STA information") to identify WLAN STAs 1 19, information corresponding to the FTM capabilities of WLAN STAs 1 19, and/or the information corresponding to the attributes of WLAN STAs 1 19, e.g., the operating channels of WLAN STAs 1 19.

[00166] In some demonstrative embodiments, cellular manager 104 may receive at least part of the WLAN STA information from one or more of WLAN STAs 1 19.

[00167] In some demonstrative embodiments, cellular manager 104 may be configured to receive at least part of the WLAN STA information from WT node 106, for example, if cellular manager 104 does not communicate directly with WLAN STAs 1 19, e.g., in a deployment according to a non-collocated architecture.

[00168] In some demonstrative embodiments, controller 149 may be configured to send the WLAN STA information to cellular manager 104. For example, message processor 150 may be configured to generate one or more messages including the WLAN STA information corresponding to WLAN STAs 1 19, and interface 192 may send the message to cellular manager 104, e.g., via interface 199.

[00169] In some demonstrative embodiments, cellular manager 104 may be implemented according to the collocated eNB/WLAN architecture. For example, cellular manager 104 may include a collocated eNB Access Point (eNB/AP), which may include at least one WLAN STA 1 19, e.g., a WLAN AP. According to these embodiments, the FTM capability infonnation may indicate at least a capability iof the WLAN AP collocated with cellular manager 104, to support FTM.

[00170] In some demonstrative embodiments, UE 102 may receive the FTM capability information from cellular manager 104. For example, cellular transceiver 165 may be configured to process reception of the cellular message, e.g., the RRC message, including the FTM capability information indicating the capability of one or more WLAN stations STAs 1 19 to support FTM.

[00171 ] In some demonstrative embodiments, FTM component 145 may be configured to access and/or process the FTM capability information.

[00172] In some demonstrative embodiments, FTM component 145 may be configured to trigger UE 102 to perform one or more operations and/or communications, for example, based on the FTM capability information, e.g., as described below.

[00173] In some demonstrative embodiments, FTM component 145 may be configured to, based on the FTM capability information, trigger WLAN transceiver 163 to communicate FTM messages with the one or more WLAN STAs 1 19.

[00174] In some demonstrative embodiments, FTM component 145 may be configured to determine one or more WLAN STAs 1 19, which may be capable of communicating FTM messages, e.g., based on the identifiers of the WLAN STAs included in the FTM capability information.

[00175] In some demonstrative embodiments, FTM component 145 may be configured to determine one or more operating channels of the ne or more WLAN STAs 1 19, which may be capable of communicating FTM messages, for example, based on the radio frequency information included in the FTM capability information.

[00176] In some demonstrative embodiments, the FTM capability information may include an identifier to identify a WLAN STA 1 19 capable of responding to an FTM request, and radio frequency information indicating a wireless communication channel to communicate the FTM messages with the WLAN STA 1 19, e.g., as described above.

[00177] In some demonstrative embodiments, FTM component 145 may be configured to trigger WLAN transceiver 163 to transmit the FTM request, e.g., FTM request 23 1 (Fig. 2), to the WLAN STA 1 19 over the wireless communication channel indicated by the FTM capability information corresponding to the WLAN STA 1 19.

[00178] In some demonstrative embodiments, FTM component 145 may be configured to selectively trigger WLAN TRx 163 to perform or more operations and/or communications, and/or to select to avoid one or more WLAN operations and/or communications, for example, based on the FTM capability information, e.g., as described below.

[00179] In some demonstrative embodiments, FTM component 145 may be configured to trigger WLAN transceiver 163 to communicate an FTM request, e.g., FTM request 23 1 (Fig. 1 ), with a WLAN STA 1 19 of the one or more WLAN ST As 1 19, for example, based on the FTM capability information, and to select to avoid a WLAN scan for the WLAN STA 1 19 over one or more wireless communication channels supported by WLAN transceiver 163, e.g., one or more wireless communication channels which are different from the operating channel of the WLAN STA 1 19.

[00180] In some demonstrative embodiments, FTM component 145 may be configured to trigger WLAN transceiver 163 to communicate an FTM request, e.g., FTM request 231 (Fig. 1 ), with a WLAN STA 1 19 of the one or more WLAN STAs 1 19, for example, based on the FTM capability information, and to select to avoid sending to the WLAN STA 1 19 an inquiry on a capability of the WLAN STA to support FTM.

[00181 ] In some demonstrative embodiments, FTM component 145 may be configured to trigger WLAN transceiver 163 to communicate an FTM request, e.g., FTM request 231 (Fig. 1 ), with a WLAN STA 1 19 of the one or more WLAN STAs 1 19, for example, based on the FTM capability information, and to select to avoid listening for WLAN beacons over one or more wireless communication channels supported by WLAN transceiver 163.

[00182] In some demonstrative embodiments, FTM component 145 may be configured to use the FTM capability information received from cellular manager 104, for example, to at least partially optimize an execution time and/or power consumption for performing the FTM with WLAN STAs 1 19, for example, by selecting to avoid over the air search for proximal WLAN STAs 1 19, for example, on one or more supported WLAN channels of WLAN TRx 163, e.g., as described above.

[00183] In some demonstrative embodiments, FTM component 145 may be configured to use the FTM capability information received from cellular manager 104, for example, to at least partially optimize an execution time and/or power consumption for performing the FTM with WLAN STAs 1 19, for example, by selecting to avoid sending of inquiry frames over the one or more supported WLAN channels, listening for WLAN AP responses, and/or analyzing the capability of the WLAN APs to perform an FTM frame exchange, e.g., as described above.

[00184] In some demonstrative embodiments, FTM component 145 may be configured to use the FTM capability information received from cellular manager 104, for example, to at least partially optimize an execution time and/or !power consumption for performing the FTM with WLAN STAs 1 19, for example, by selecting to avoid an operation of listening to beacons or discovery frames from one or more WLAN APs over the one or more supported WLAN channels, and/or analyzing a capability of the WLAN APs to perform FTM frame exchange, for example, from capabilities published by the WLAN APs in periodic beacons or discovery frames. j

[00185] Reference is made to Fig. 3, which schematically illustrates elements of a UE device 300, in accordance with some demonstrative embodiments. For example, one or more elements of UE device 300 may perform the functionality of one or more elements of UE 102 (Fig. 1 ). In one example, one or more elements of UE device 300 may be configured to perform the functionality of one or more of cellular TRx 165 (Fig. 1), WLAN TRx 163 (Fig. 1), FTM component 145 (Fig. 1 ), controller 197 (Fig., 1 ), message processor 198 (Fig. 1 ), and/or one or more other elements of UE 102 (Fig. 1). In some demonstrative embodiments, embodiments of a UE may be implemented into a system using any suitably configured hardware and/or software. Fig. 3 illustrates, for one embodiment, example components of UE device 300.

[00186] In some demonstrative embodiments, UE device 300 may include application circuitry 302, baseband circuitry 304, Radio Frequency (RF) circuitry 306, front-end module (FEM) circuitry 308, and one or more antennas 310, coupled together at least as shown.

[00187] In one example, application circuitry 302 may be configured to perform at least part of the functionality of FTM component 145 (Fig. 1), controller 197 (Fig. 1), and/or message processor 198 (Fig. 1); and/or baseband circuitry 304, RF circuitry 306, and/or FEM circuitry 308 may be configured to perform at least part of the functionality of cellular TRx 165 (Fig. 1), WLAN TRx 163 (Fig. 1), controller 197 (Fig. 1), message processor 198 (Fig. 1), and/or FTM component 145 (Fig. 1 ). [00188] In some demonstrative embodiments, the application circuitry 302 may include one or more application processors. For example, the application circuitry 302 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors may be coupled with and/or may include memory/storage and may be configured to execute instructions stored in the memory/storage to enable various applications and/or operating systems to run on the system.

[00189] In some demonstrative embodiments, the baseband circuitry 304 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 304 may include one or more baseband processors and/or control logic to process baseband signals received from a receive signal path of the RF circuitry 306 and to generate baseband signals for a transmit signal path of the RF circuitry 306. Baseband processing circuitry 304 may interface with the application circuitry 302, for example, for generation and processing of the baseband signals and for controlling operations, of the RF circuitry 306. For example, in some embodiments, the baseband circuitry 304 may include a second generation (2G) baseband processor 304a, a third generation (3G) baseband processor 304b, a fourth generation (4G) baseband processor 304c, and/or other baseband processor(s) 304d for other existing generations, generations in development or to be developed in the future (e.g., fifth generation (5G), 6G, etc.). The baseband circuitry 304 (e.g., one or more of baseband processors 304a-d) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 306. The radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some embodiments, modulation/demodulation circuitry of the baseband circuitry 304 may include Fast-Fourier Transform (FFT), precoding, and/or constellation mapping/demapping functionality. In some embodiments, encoding/decoding circuitry of the baseband circuitry 304 may include convolution, tail-biting convolution, turbo, Viterbi, and/or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.

[00190] In some demonstrative embodiments, the baseband circuitry 304 may include elements of a protocol stack such as, for example, elements of an evolved universal terrestrial radio access network (EUTRAN) protocol including, for example, physical (PHY), media access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), and/or radio resource control (RRC) elements. A central processing unit (CPU) 304e of the baseband circuitry 304 may be configured, for example, to run elements of the protocol stack for signaling of the PHY, MAC, RLC, PDCP and/or RRC layers. In some embodiments, the baseband circuitry may include one or more audio digital signal processor(s) (DSP) 304f. The audio DSP(s) 304f may be include elements for compression/decompression and echo cancellation, and/or may include other suitable processing elements in other embodiments. Components of the baseband circuitry 304 may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments. In some embodiments, some or all of the constituent components of the baseband circuitry 304 and the application circuitry 302 may be implemented together such as, for example, on a system on a chip (SOC).

[00191 ] In some demonstrative embodiments, the baseband circuitry 304 may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 304 may support communication with an evolved universal terrestrial radio access network (EUTRAN) and/or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN), and/or one or more additional or alternative networks. Embodiments in which the baseband circuitry 304 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

[00192] In some demonstrative embodiments, RF circuitry 306 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 306 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry 306 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 308, and to provide baseband signals to the baseband circuitry 304. RF circuitry 306 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 304 and provide RF output signals to the FEM circuitry 308 for transmission.

[00193] In some demonstrative embodiments, the RF circuitry 306 may include a receive signal path and a transmit signal path. The receive signal path of the RF circuitry 306 may include mixer circuitry 306a, amplifier circuitry 306b, and filter circuitry 306c. The transmit signal path of the RF circuitry 306 may include filter circuitry 306c and mixer circuitry 306a. RF circuitry 306 may also include synthesizer circuitry 306d for synthesizing a frequency for use by the mixer circuitry 306a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 306a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 308 based on the synthesized frequency provided by synthesizer circuitry 306d. The amplifier circuitry 306b may be configured to amplify the down-converted signals and the filter circuitry 306c may be, for example, a low-pass filter (LPF) or a band-pass filter (BPF), configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals may be provided to the baseband circuitry 304 for further processing. In some embodiments, the output baseband signals may be zero-frequency baseband signals, although this is not a requirement. In some embodiments, mixer circuitry 306a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect. ^:

[00194] In some demonstrative embodiments, the mixer circuitry 306a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry! 306d to generate RF output signals for the FEM circuitry 308. The baseband signals may be provided by the baseband circuitry 304 and may be filtered by filter circuitry 306c. The filter circuitry 306c may include a low-pass filter (LPF), although the scope of the embodiments is not limited in this respect.

[00195] In some demonstrative embodiments, the mixer circuitry 306a of the receive signal path and the mixer circuitry 306a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconyersion and/or upconversion respectively. In some embodiments, the mixer circuitry 306a of the receive signal path and the mixer circuitry 306a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 306a of the receive signal path and the mixer circuitry 306a may be arranged for direct downconversion and/or direct upconversion, respectively. In some embodiments, the mixer circuitry 306a of the receive signal path and the mixer circuitry 306a of the transmit signal path may be configured for super-heterodyne operation.

[00196] In some demonstrative embodiments, the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In these alternate embodiments, the RF circuitry 306 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and the baseband circuitry 304 may include a digital baseband interface to communicate with the RF circuitry 306.

[00197] In some dual-mode embodiments, a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.

[00198] In some demonstrative embodiments, the synthesizer circuitry 306d may be a fractional-N synthesizer or a fractional N/N+l synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, synthesizer circuitry 3.06d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

[00199] In some demonstrative embodiments, the synthesizer circuitry 306d may be configured to synthesize an output frequency for use by the mixer circuitry 306a of the RF circuitry 306 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 306d may be a fractional N/N+l synthesizer.

[00200] In some demonstrative embodiments, frequency input may be provided by a voltage controlled oscillator (VCO), although that is not¹ a requirement. Divider control input may be

i

provided by either the baseband circuitry 304 or the applications processor 302 depending on

i

the desired output frequency. In some embodiments, a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the applications processor 302.

[00201] In some demonstrative embodiments, synthesizer circuitry 306d of the RF circuitry 306 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator. In some embodiments, the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by either N or N+l (e.g., based on a carry out) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D- type flip-flop. In these embodiments, the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[00202] In some demonstrative embodiments, synthesizer circuitry 306d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some embodiments, the output frequency may be a LO frequency (fLO). In some embodiments, the RF circuitry 306 may include an IQ/polar converter.

[00203] In some demonstrative embodiments, FEM circuitry 308 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 3 10, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 306 for further processing. FEM circuitry 308 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 306 for transmission by one or more of the one or more antennas 310.

[00204] In some demonstrative embodiments, the FEM circuitry 308 may include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry may include a low-noise amplifier (LNA) to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 306). The transmit signal path of the FEM circuitry 308 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 306), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 310.

[00205] In some embodiments, the UE device 300 may include one or more additional or alternative elements such as, for example, memory/storage, display, camera, sensor, and/or input/output (I/O) interface.

[00206] Reference is made to Fig. 4, which schematically illustrates of cellular-assisted FTM in a collocated implementation, in accordance with some demonstrative embodiments. [00207] In some demonstrative embodiments, in a collocated implementation, as shown in Fig. 4, an eNB 403 may include an LTE component 402 collocated with a WLAN AP 406 capable of providing FTM support.

[00208] In some demonstrative embodiments, LTE component 402 and WLAN AP 406 may be configured to communicate via an interface 410, e.g., an X2W interface supporting a general packet radio service (GPRS) Tunneling Protocol User Plane (GTP-U) and/or any other protocol.

[00209] In one example, LTE component 402 may perform the functionality of cellular manager 104 (Fig. 1), WLAN AP 406 may perform the functionality of WT node 106 (Fig. 1), and/or interface 410 may perform the functionality of interface 199 (Fig. 1).

[00210] In some demonstrative embodiments, LTE component 402 may be configured to communicate with a UE 404 via a cellular link 412, e.g., an LTE link, and WLAN AP 406 may be configured to communicate with UE 404 via a WLAN link 414. For example UE 404 may perform the functionality of UE 102 (Fig. 1).

[0021 1] In some demonstrative embodiments, LTE component 402 may be configured to receive from WLAN AP 406,e .g., via interface, 410, information indicting the capability of WLAN AP 406 to support FTM, and an indication of at least one operating channel of WLAN AP 406, e.g., as described above.

[00212] In some demonstrative embodiments, LTE component 402 may be configured to transmit to UE 404 a cellular message, for example and RRC message, e.g., via link 412, including FTM capability information including an identifier of WLAN AP 406, an indication of one or more capabilities of WLAN AP 406 to support FTM, and an indication of the at least one operating channel of WLAN AP 406, e.g., as described above.

[00213] In some demonstrative embodiments, UE 404 may be configured to communicate FTM messages with WLAN AP 406 based on the FTM capability information, e.g., as described above.

[00214] Fig. 5 is a schematic illustration of cellular-assisted FTM in a non-collocated implementation, in accordance with some demonstrative embodiments.

[00215] In some demonstrative embodiments, in a non-collocated implementation, as shown in Fig. 5, an eNB 503 may include an LTE component 502, which may be configured to communicate with a WT node 506, e.g., a router, via an interface 510, e.g., an X2W interface supporting a GTP-U and/or any other protocol.

[00216] In some demonstrative embodiments, WT node 506 may be configured to control and/or communicate with one or more WLAN APs, e.g., WLAN AP 519 and WLAN AP 520.

[00217] In one example, LTE component 502 may perform the functionality of cellular manager 104 (Fig. 1), WT node 506 may perform the functionality of WT node 106 (Fig. 1 ), WLAN APs 519 and/or 520 may perform the functionality of WLAN STAs 1 19 (Fig. 1 ), and/or interface 10 may perform the functionality of interface 199 (Fig. 1 ).

[00218] In some demonstrative embodiments, LTE component 502 may be configured to communicate with a UE 504 via a cellular link 512, e.g., an LTE link, and WLAN APs 5 19 and/or 520 may be configured to communicate with UE 504 via WLAN links 5 14. For example UE 504 may perform the functionality of UE 102 (Fig. 1).

[00219] In some demonstrative embodiments, LTE component 502 may be configured to receive from WT node 506,e .g., via interface '510, information indicting the capability of WLAN APs 519 and/or 520 to support FTM, and an indication of at least one operating channel of WLAN APs 519 and/or 520, e.g., as described above.

[00220] In some demonstrative embodiments, LTE component 502 may be configured to transmit to UE 504 a cellular message, for example and RRC message, e.g., via link 512, including FTM capability information including an identifier of WLAN APs 519 and/or 520, an indication of one or more capabilities of WLAN APs 519 and/or 520 to support FTM, and an indication of the at least one operating channel of WLAN APs 519 and/or 520, e.g., as described above.

[00221] In some demonstrative embodiments, UE 504 may be configured to communicate FTM messages with WLAN APs 519 and/or 520 based on the FTM capability information, e.g., as described above.

[00222] Fig. 6 is a schematic flow-chart illustration of a method of providing cellular- assisted FTM information to a User Equipment (UE), in accordance with some demonstrative embodiments. In some embodiments, one or more of the operations of the method of Fig. 6 may be performed by a wireless communication system, e.g., system 100 (Fig. 1 ); a cellular node, e.g., cellular node 104 (Fig. 1 ); an interface, e.g., cellular TRx 167 (Fig. 1), and/or interface 169 (Fig. 1); a message processor, e.g., message processor 144 (Fig. 1 ), and/or a controller, e.g., controller 182 (Fig. 1).

[00223] As indicated at block 602, the method may include generating a cellular message including FTM capability information indicating a capability of one or more WLAN STAs to support FTM. For example, message generator 144 (Fig. 1) may be configured to generate a message, e.g., an RRC message, including the FTM capability information corresponding to WLAN STAs 1 19 (Fig. 1), e.g., as described above.

[00224] As indicated at block 603, the method may include determining the FTM capability information based on information received from at least one WT node. For example, controller 182 (Fig. 1) may be configured to determine the FTM capability information based on infonnation from WT node 106 (Fig. 1) corresponding to one or more WLAN STAs 1 19 (Fig. 1), e.g., as described above.

[00225] As indicated at block 604, the method may include sending the cellular message to a UE via a cellular link. For example, controller 182 (Fig. 1) may trigger cellular TRx 167 (Fig. 1 ) to transmit the RRC message including the FTM capability information to UE 102 (Fig. 1 ), e.g., as described above.

[00226] Fig. 7 is a schematic flow-chart illustration of a method of cellular-assisted FTM, in accordance with some demonstrative embodiments. In some embodiments, one or more of the operations of the method of Fig. 7 may be performed by a wireless communication system, e.g., system 100 (Fig. 1); a UE, e.g., UE 102 (Fig. 1); an interface, e.g., cellular TRx 165 (Fig. 1 ), and/or WLAN TRx 163 (Fig. 1); an FTM component, e.g., FTM component 145 (Fig. 1), a message processor, e.g., message processor 198 (Fig. 1), and/or a controller, e.g., controller 197 (Fig. 1).

[00227] As indicated at block 702, the method may include receiving from a cellular network a cellular message including FTM capability information indicating a capability of one or more WLAN STAs to support FTM. For example, cellular TRx 165 (Fig. 1 ) may receive from cellular manager 104 (Fig. 1) a message, e.g., an RRC message, including the FTM capability infonnation corresponding to WLAN STAs 1 19 (Fig. 1), e.g., as described above.

[00228] As indicated at block 704, the method may include triggering a WLAN transceiver to communicate FTM messages with the one or more WLAN STAs, for example, based on the FTM capability information. For example, FTM component 145 (Fig. 1 ) may be configured to, based on the FTM capability information, trigger WLAN transceiver 163 (Fig. 1) to communicate FTM messages with the one^' or more WLAN STAs 1 19 (Fig. 1), e.g., as described above.

[00229] Reference is made to Fig. 8, which schematically illustrates a product of manufacture 800, in accordance with some demonstrative embodiments. Product 800 may include a non-transitory machine-readable storage medium 802 to store logic 804, which may be used, for example, to perform at least part of the functionality of one or more components of a cellular manager, e.g., cellular manager 104 (Fig. 1); one or more components of a UE, e.g., UE 102 (Fig. 1) and/or UE 300 (Fig. 3); one or more components of a WT node, e.g., WT node 106 (Fig. 1); an FTM component, e.g., FTM component 145 (Fig. 1 ); a controller, e.g., controller 182 (Fig. 1 ), controller 197 (Fig. 1), and/or controller 149 (Fig. 1 ); and/or a message processor, e.g., message processor 144 (Fig. 1), message processor 198 (Fig. 1 ), and/or message processor 150 (Fig. 1 ), and/or to perform one or more operations of the methods of Figs. 6 and/or 7, and/or one or more operations and/or functionalities described herein. The phrase "non-transitory machine-readable medium" is directed to include all computer-readable media, with the sole exception being a transitory propagating signal.

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

[00231 ] In some demonstrative embodiments, logic 804 may include instructions, data, and/or code, which, if executed by a machine, may cause the machine to perform a method, process and/or operations as described herein.. The machine may include, for example, any suitable processing platform, computing platform, computing device, processing device, computing system, processing system, computer, processor, or the like, and may be implemented using any suitable combination of hardware, software, firmware, and the like.

[00232] In some demonstrative embodiments, logic 804 may include, or may be implemented as, software, a software module, an application, a program, a subroutine, instructions, an instruction set, computing code, words, values, symbols, and the like. The instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, and the like. The instructions may be implemented according to a predefined computer language, manner or syntax, for instructing a processor to perform a certain function. The instructions may be implemented using any suitable high-level, low-level, object-oriented, visual, compiled and/or interpreted programming language, such as C, C++, Java, BASIC, Matlab, Pascal, Visual BASIC, assembly language, machine code, and the like.

EXAMPLES

[00233] The following examples pertain to further embodiments.

[00234] Example I includes an apparatus of a User Equipment (UE) comprising a Wireless Local Area Network (WLAN) transceiver; a cellular transceiver to receive from a cellular network a cellular message comprising Fine Timing Measurement (FTM) capability information indicating a capability of one or more WLAN stations (STAs) to support FTM; and a Fine Timing Measurement (FTM) component configured to, based on the FTM capability information, trigger the WLAN transceiver to communicate FTM messages with the one or more WLAN STAs.

[00235] Example 2 includes the subject matter of Example 1 , and optionally, wherein the FTM capability information comprises an identifier to identify a WLAN STA capable of responding to an FTM request, and radio frequency information indicating a wireless communication channel to communicate the FTM messages with the WLAN STA.

[00236] Example 3 includes the subject matter_, of Example 2, and optionally, wherein the FTM component is configured to trigger the WLAN transceiver to transmit the FTM request to the WLAN STA over the wireless communication channel. [00237] Example 4 includes the subject matter of Example 2 or 3, and optionally, wherein the identifier comprises at least one identifier selected from a group consisting of a Media Access Control (MAC) address, and a Basic Service Set Identifier (BSSID).

[00238] Example 5 includes the subject matter of any one of Examples 1 -4, and optionally, wherein the FTM component is configured to trigger the WLAN transceiver to communicate an FTM request with a WLAN STA of the one or more WLAN STAs, based on the FTM capability information, and to select to avoid a WLAN scan for the WLAN STA over one or more wireless communication channels supported by the WLAN transceiver.

[00239] Example 6 includes the subject matter of any one of Examples 1 -5, and optionally, wherein the FTM component is configured to trigger the WLAN transceiver to communicate an FTM request with a WLAN STA of the one or more WLAN STAs, based on the FTM capability information, and to select to avoid sending to the WLAN STA an inquiry on a capability of the WLAN STA to support FTM.

[00240] Example 7 includes the subject matter of any one of Examples 1-6, and optionally, wherein the FTM component is configured to trigger the WLAN transceiver to communicate an FTM request with a WLAN STA of the one or more WLAN STAs, based on the FTM capability information, and to select to avoid listening for WLAN beacons over one or more wireless communication channels supported by the WLAN transceiver.

[00241 ] Example 8 includes the subject matter of any one of Examples 1 -7, and optionally, wherein the FTM component is configured to determine a location of the UE based on timing information corresponding to the FTM messages.

[00242] Example 9 includes the' subject matter of any one of Examples 1 -8, and optionally, wherein the cellular message comprises a Radio Resource Control (RRC) message.

[00243] Example 10 includes the subject matter of any one of Examples 1 -9, and optionally, wherein the one or more WLAN STAs comprise at least one WLAN Access Point (AP).

[00244] Example 1 1 includes the subject matter of any one of Examples 1 - 10, and optionally, comprising one or more antennas, a memory and a processor.

[00245] Example 12 includes an apparatus comprising circuitry and logic configured to trigger a User Equipment to process a cellular message from an Evolved Node B (eNB), the cellular message comprising Fine Timing Measurement (FTM) capability information indicating a capability of one or more Wireless Local Area Network (WLAN) stations (STAs) to support FTM; and based on the FTM capability information, trigger a WLAN transceiver of the UE to communicate FTM messages with the one or more WLAN STAs.

[00246] Example 13 includes the subject matter of Example 12, and optionally, wherein the FTM capability information comprises an identifier to identify a WLAN STA capable of responding to an FTM request, and radio frequency information indicating a wireless communication channel to communicate the FTM messages with the WLAN STA.

[00247] Example 14 includes the subject matter of Example 13, and optionally, wherein the apparatus is configured to trigger the UE to transmit the FTM request to the WLAN STA over the wireless communication channel.

[00248] Example 15 includes the subject matter of Example 13 or 14, and optionally, wherein the identifier comprises at least one identifier selected from a group consisting of a Media Access Control (MAC) address, and a Basic Service Set Identifier (BSSID).

[00249] Example 16 includes the subject matter of any one of Examples 12- 15, and optionally, wherein the apparatus is configured to trigger the UE to communicate an FTM request with a WLAN STA of the one or more WLAN STAs, based on the FTM capability information, and to select to avoid a WLAN scan for the WLAN STA over one or more wireless communication channels supported by the WLAN transceiver.

[00250] Example 17 includes the subject matter of any one of Examples 12-16, and optionally, wherein the apparatus is configured . to trigger the UE to communicate an FTM request with a WLAN STA of the one or more jWLAN STAs, based on the FTM capability information, and to select to avoid sending to the WLAN STA an inquiry on a capability of the WLAN STA to support FTM.

[00251 ] Example 18 includes the subject matter of any one of Examples 12-17, and optionally, wherein the apparatus is configured to trigger the UE to communicate an FTM request with a WLAN STA of the one or more WLAN STAs, based on the FTM capability information, and to select to avoid listening for WLAN beacons over one or more wireless communication channels supported by the WLAN transceiver.

[00252] Example 19 includes the subject matter of any one of Examples 12- 18, and optionally, wherein the apparatus is configured to determine a location of the UE based on timing information corresponding to the FTM messages. [00253] Example 20 includes the subject matter of any one of Examples 12- 19, and optionally, wherein the cellular message comprises a Radio Resource Control (RRC) message.

[00254] Example 21 includes the subject matter of any one of Examples 12-20, and optionally, wherein the one or more WLAN STAs comprise at least one WLAN Access Point

(AP). ;

[00255] Example 22 includes the subject matter of any one of Examples 12-21 , and optionally, wherein the UE comprises one or more antennas, a memory and a processor.

[00256] Example 23 includes a product comprising one or more tangible computer-readable storage media comprising computer-executable instructions operable to, when executed by at least one computer processor, enable the at least one computer processor to implement one or more operations at a User Equipment (UE), the: operations comprising processing a cellular message from an Evolved Node B (eNB), the cellular message comprising Fine Timing Measurement (FTM) capability information indicating a capability of one or more Wireless Local Area Network (WLAN) stations (STAs) to support FTM; and based on the FTM capability information, triggering a WLAN transceiver of the UE to communicate FTM messages with the one or more WLAN STAs.

[00257] Example 24 includes the subject matter of Example 23, and optionally, wherein the FTM capability information comprises an identifier to identify a WLAN STA capable of responding to an FTM request, and radio frequency information indicating a wireless communication channel to communicate the FTM messages with the WLAN STA.

[00258] Example 25 includes the subject matter of Example 24, and optionally, wherein the operations comprise triggering the WLAN transceiver to transmit the FTM request to the WLAN STA over the wireless communication channel.

[00259] Example 26 includes the subject matter of Example 24 or 25, and optionally, wherein the identifier comprises at least one identifier selected from a group consisting of a Media Access Control (MAC) address, and a Basic Service Set Identifier (BSSID).

[00260] Example 27 includes the subject matter of any one of Examples 23-26, and optionally, wherein the operations comprise triggering the WLAN transceiver to communicate an FTM request with a WLAN STA of the one or more WLAN STAs, based on the FTM capability information, and selecting to avoid a WLAN scan for the WLAN STA over one or more wireless communication channels supported by the WLAN transceiver. [00261] Example 28 includes the subject matter of any one of Examples 23-27, and optionally, wherein the operations comprise triggering the WLAN transceiver to communicate an FTM request with a WLAN STA of the one or more WLAN STAs, based on the FTM capability information, and selecting to avoid sending to the WLAN STA an inquiry on a capability of the WLAN STA to support FTM.

[00262] Example 29 includes the subject matter of any one of Examples 23-28, and optionally, wherein the operations comprise triggering the WLAN transceiver to communicate an FTM request with a WLAN STA of the one or more WLAN STAs, based on the FTM capability information, and selecting to!avoid listening for WLAN beacons over one or more wireless communication channels supported by the WLAN transceiver.

[00263] Example 30 includes the subject matter of any one of Examples 23-29, and optionally, wherein the operations comprise determining a location of the UE based on timing information corresponding to the FTM messages.

[00264] Example 31 includes the subject matter of any one of Examples 23-30, and optionally, wherein the cellular message comprises a Radio Resource Control (RRC)

i

message.

[00265] Example 32 includes the subject matter of any one of Examples 23-31 , and optionally, wherein the one or more WLAN STAs comprise at least one WLAN Access Point (AP). i

[00266] Example 33 includes a method to be .performed by a User Equipment (UE), the method comprising processing a cellular message from an Evolved Node B (eNB), the cellular message comprising Fine Timing Measurement (FTM) capability information indicating a capability of one or more Wireless Local Area Network (WLAN) stations (STAs) to support FTM; and based on the FTM capability information, triggering a WLAN transceiver of the UE to communicate FTM messages with the one or more WLAN STAs.

[00267] Example 34 includes the subject matter of Example 33, and optionally, wherein the FTM capability information comprises an identifier to identify a WLAN STA capable of responding to an FTM request, and radio frequency information indicating a wireless communication channel to communicate the FTM messages with the WLAN STA.

[00268] Example 35 includes the subject matter of Example 34, and optionally, comprising triggering the WLAN transceiver to transmit the FTM request to the WLAN STA over the wireless communication channel. [00269] Example 36 includes the subject matter of Example 34 or 35, and optionally, wherein the identifier comprises at least one identifier selected from a group consisting of a Media Access Control (MAC) address, and a Basic Service Set Identifier (BSSID).

[00270] Example 37 includes the subject matter of any one of Examples 33-36, and optionally, comprising triggering the WLAN transceiver to communicate an FTM request with a WLAN STA of the one or more WLAN STAs, based on the FTM capability information, and selecting to avoid a WLAN scan for the WLAN STA over one or more wireless communication channels supported by the WLAN transceiver.

[00271 ] Example 38 includes the subject matter of any one of Examples 33-37, and optionally, comprising triggering the WLAN transceiver to communicate an FTM request with a WLAN STA of the one or more WLAN STAs, based on the FTM capability information, and selecting to avoid sending to the WLAN STA an inquiry on a capability of the WLAN STA to support FTM.

[00272] Example 39 includes the subject matter of any one of Examples 33-38, and optionally, comprising triggering the WLAN transceiver to communicate an FTM request with a WLAN STA of the one or more WLAN STAs, based on the FTM capability information, and selecting to avoid listening for WLAN beacons over one or more wireless communication channels supported by the WLAN transceiver.

[00273] Example 40 includes the subject matter of any one of Examples 33-39, and optionally, comprising determining a location of the UE based on timing information corresponding to the FTM messages.

[00274] Example 41 includes the subject matter of any one of Examples 33-40, and optionally, wherein the cellular message comprises a Radio Resource Control (RRC) message.

[00275] Example 42 includes the subject matter of any one of Examples 33-41 , and optionally, wherein the one or more WLAN STAs comprise at least one WLAN Access Point (AP).

[00276] Example 43 includes an apparatus of cellular communication by a User Equipment (UE), the apparatus comprising means for processing a cellular message from an Evolved Node B (eNB), the cellular message comprising Fine Timing Measurement (FTM) capability information indicating a capability of one or more Wireless Local Area Network (WLAN) stations (STAs) to support FTM; and means for, based on the FTM capability information, triggering a WLAN transceiver of the UE to communicate FTM messages with the one or more WLAN STAs.

[00277] Example 44 includes the subject matter of Example 43, and optionally, wherein the FTM capability information comprises an identifier to identify a WLAN STA capable of responding to an FTM request, and radio frequency information indicating a wireless communication channel to communicate the FTM messages with the WLAN STA.

[00278] Example 45 includes the subject matter of Example 44, and optionally, comprising means for triggering the WLAN transceiver to transmit the FTM request to the WLAN STA over the wireless communication channel.

[00279] Example 46 includes the subject matter of Example 44 or 45, and optionally, wherein the identifier comprises at least one identifier selected from a group consisting of a Media Access Control (MAC) address, and a Basic Service Set Identifier (BSS1D).

[00280] Example 47 includes the subject matter of any one of Examples 43-46, and optionally, comprising means for triggering the WLAN transceiver to communicate an FTM request with a WLAN STA of the one or more WLAN STAs, based on the FTM capability information, and selecting to avoid a WLAN scan for the WLAN STA over one or more wireless communication channels supported by the WLAN transceiver.

[00281] Example 48 includes the subject matter of any one of Examples 43-47, and optionally, comprising means for triggering the WLAN transceiver to communicate an FTM request with a WLAN STA of the one or more WLAN STAs, based on the FTM capability information, and selecting to avoid sending to the WLAN STA an inquiry on a capability of the WLAN STA to support FTM.

[00282] Example 49 includes the subject matter of any one of Examples 43-48, and optionally, comprising means for triggering the WLAN transceiver to communicate an FTM request with a WLAN STA of the one or more WLAN STAs, based on the FTM capability information, and selecting to avoid listening for WLAN beacons over one or more wireless communication channels supported by the WLAN transceiver.

[00283] Example 50 includes the subject matter of any one of Examples 43-49, and optionally, comprising means for determining a location of the UE based on timing information corresponding to the FTM messages. [00284] Example 51 includes the subject matter of any one of Examples 43-50, and optionally, wherein the cellular message comprises a Radio Resource Control (RRC) message.

[00285] Example 52 includes the subject matter of any one of Examples 43-51 , and optionally, wherein the one or more WLAN STAs comprise at least one WLAN Access Point (AP).

[00286] Example 53 includes an apparatus of an Evolved Node B (eNB) comprising a message processor configured to generate a cellular message comprising Fine Timing Measurement (FTM) capability information indicating a capability of one or more Wireless Local Area Network (WLAN) stations (STAs) to support FTM; and a cellular interface configured to send the cellular message to a User Equipment (UE) via a cellular link.

[00287] Example 54 includes the subject matter of Example 53, and optionally, wherein the FTM capability information comprises an identifier to identify a WLAN STA capable of responding to an FTM request, and radio frequency information indicating a wireless communication channel to communicate FTM messages with the WLAN STA.

[00288] Example 55 includes the subject matter! of Example 54, and optionally, wherein the identifier comprises at least one identifier selected from a group consisting of a Media Access Control (MAC) address, and a Basic Service Set Identifier (BSS1D).

[00289] Example 56 includes the subject matter of any one of Examples 53-55, and optionally, comprising a collocated eNB Access Point (eNB/AP), the collocated eNB/AP comprising a WLAN AP, the FTM capability^ information indicating a capability of the WLAN AP to support FTM.

[00290] Example 57 includes the subject matter of any one of Examples 53-56, and optionally, comprising a WLAN control interface to communicate with the one or more WLAN STAs. i

[00291 ] Example 58 includes the subject matter of any one of Examples 53-57, and optionally, wherein the cellular message comprises a Radio Resource Control (RRC) message.

[00292] Example 59 includes the subject matter of any one of Examples 53-58, and optionally, wherein the one or more WLAN STAs comprise at least one WLAN Access Point (AP). [00293] Example 60 includes the subject matter of any one of Examples 53-59, and optionally, comprising one or more antennas, a memory and a processor.

[00294] Example 61 includes an apparatus comprising circuitry and logic configured to trigger an Evolved Node B (eNB) to generate a cellular message comprising Fine Timing Measurement (FTM) capability information indicating a capability of one or more Wireless Local Area Network (WLAN) stations (STAs) to support FTM; and send the cellular message to a User Equipment (UE) via a cellular link.

[00295] Example 62 includes the subject matter of Example 61 , and optionally, wherein the FTM capability information comprises an identifier to identify a WLAN STA capable of responding to an FTM request, and radio frequency information indicating a wireless communication channel to communicate FTM messages with the WLAN STA.

[00296] Example 63 includes the subject matter^' of Example 62, and optionally, wherein the identifier comprises at least one identifier selected from a group consisting of a Media Access Control (MAC) address, and a Basic Service Set Identifier (BSS1D).

[00297] Example 64 includes the subject matter of any one of Examples 61-63, and optionally, wherein the eNB comprises a collocated eNB Access Point (eNB/AP), the collocated eNB/AP comprising a WLAN AP, the FTM capability information indicating a capability of the WLAN AP to support FTM.

[00298] Example 65 includes the subject matter of any one of Examples 61-64, and optionally, wherein the eNB comprises a WLAN control interface to communicate with the one or more WLAN STAs.

[00299] Example 66 includes the subject matter of any one of Examples 61 -65, and optionally, wherein the cellular message comprises a Radio Resource Control (RRC) message.

[00300] Example 67 includes the subject matter of any one of Examples 61-66, and optionally, wherein the one or more WLAN STAs comprise at least one WLAN Access Point (AP).

[00301 ] Example 68 includes the subject matter of any one of Examples 61-67, and optionally, wherein the eNB comprises one or more antennas, a memory and a processor.

[00302] Example 69 includes a product comprising one or more tangible computer-readable storage media comprising computer-executable instructions operable to, when executed by at least one computer processor, enable the at least one computer processor to implement one or more operations at an Evolved Node B (eNB), the operations comprising generating a cellular message comprising Fine Timing Measurement (FTM) capability information indicating a capability of one or more Wireless Local Area Network (WLAN) stations (STAs) to support FTM; and sending the cellular message to a User Equipment (UE) via a cellular link.

[00303] Example 70 includes the subject matter of Example 69, and optionally, wherein the FTM capability information comprises an identifier to identify a WLAN STA capable of responding to an FTM request, and radio frequency information indicating a wireless communication channel to communicate FTM messages with the WLAN STA.

[00304] Example 1 includes the subject matter of Example 70, and optionally, wherein the identifier comprises at least one identifier selected from a group consisting of a Media Access Control (MAC) address, and a Basic Service Set Identifier (BSSID).

[00305] Example 72 includes the subject matter of any one of Examples 69-71 , and optionally, wherein the eNB comprises a collocated eNB Access Point (eNB/AP), the collocated eNB/AP comprising a WLAN AP, the FTM capability information indicating a capability of the WLAN AP to support FTM.

[00306] Example 73 includes the subject matter of any one of Examples 69-72, and optionally, wherein the eNB comprises a WLAN control interface to communicate with the one or more WLAN STAs.

[00307] Example 74 includes the subject matter of any one of Examples 69-73, and optionally, wherein the cellular message comprises a Radio Resource Control (RRC) message.

[00308] Example 75 includes the subject matter of any one of Examples 69-74, and optionally, wherein the one or more WLAN STAs comprise at least one WLAN Access Point (AP).

[00309] Example 76 includes a method to be performed at an Evolved Node B (eNB), the method comprising generating a cellular message comprising Fine Timing Measurement (FTM) capability information indicating a capability of one or more Wireless Local Area Network (WLAN) stations (STAs) to support FTM; and sending the cellular message to a User Equipment (UE) via a cellular link. [00310] Example 77 includes the subject matter of Example 76, and optionally, wherein the FTM capability information comprises an identifier to identify a WLAN STA capable of responding to an FTM request, and radio frequency information indicating a wireless communication channel to communicate FTM messages with the WLAN STA.

[003 1 1] Example 78 includes the subject matter of Example 77, and optionally, wherein the identifier comprises at least one identifier selected from a group consisting of a Media Access Control (MAC) address, and a Basic Service Set Identifier (BSS1D).

[00312] Example 79 includes the subject matter of any one of Examples 76-78, and optionally, wherein the eNB comprises a collocated eNB Access Point (eNB/AP), the collocated eNB/AP comprising a WLAN AP, the FTM capability information indicating a capability of the WLAN AP to support FTM.

[003 13] Example 80 includes the subject matter of any one of Examples 76-79, and optionally, wherein the eNB comprises a WLAN control interface to communicate with the one or more WLAN STAs.

[003 14] Example 81 includes the subject matter of any one of Examples 76-80, and optionally, wherein the cellular message comprises a Radio Resource Control (RRC) message.

[003 15] Example 82 includes the subject matter of any one of Examples 76-81 , and optionally, wherein the one or more WLAN STAs comprise at least one WLAN Access Point (AP).

[00316] Example 83 includes an apparatus of cellular communication by an Evolved Node B (eNB), the apparatus comprising means for generating a cellular message comprising Fine Timing Measurement (FTM) capability information indicating a capability of one or more Wireless Local Area Network (WLAN) stations (STAs) to support FTM; and means for sending the cellular message to a User Equipment (UE) via a cellular link.

[00317] Example 84 includes the subject matter of Example 83, and optionally, wherein the FTM capability information comprises an identifier to identify a WLAN STA capable of responding to an FTM request, and radio frequency information indicating a wireless communication channel to communicate FTM messages with the WLAN STA. [00318] Example 85 includes the subject matter of Example 84, and optionally, wherein the identifier comprises at least one identifier selected from a group consisting of a Media Access Control (MAC) address, and a Basic Service Set Identifier (BSSID).

[00319] Example 86 includes the subject matter of any one of Examples 83-85, and optionally, wherein the eNB comprises a collocated eNB Access Point (eNB/AP), the collocated eNB/AP comprising a WLAN AP, the FTM capability information indicating a capability of the WLAN AP to support FTM.

[00320] Example 87 includes the subject matter of any one of Examples 83-86, and optionally, wherein the eNB comprises a WLAN control interface to communicate with the one or more WLAN STAs.

[00321 ] Example 88 includes the subject matter of any one of Examples 83-87, and optionally, wherein the cellular message comprises a Radio Resource Control (RRC) message.

[00322] Example 89 includes the subject matter of any one of Examples 83-88, and optionally, wherein the one or more WLAN STAs comprise at least one WLAN Access Point (AP).

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

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

Claims

CLAIMS What is claimed is:

1. An apparatus of a User Equipment (UE), the apparatus comprising:

a Wireless Local Area Network (WLAN) transceiver;

a cellular transceiver to receive from a cellular network a cellular message comprising Fine Timing Measurement (FTM) capability information indicating a capability of one or more WLAN stations (STAs) to support FTM; and

i

a FTM component configured to, based; on said FTM capability information, trigger the WLAN transceiver to communicate FTM messages with the one or more WLAN STAs.

2. The apparatus of claim 1 , wherein the FTM capability information comprises an identifier to identify a WLAN STA capable of responding to an FTM request, and radio frequency information indicating a wireless communication channel to communicate the FTM messages with the WLAN STA.

3. The apparatus of claim 2, wherein the FTM component is configured to trigger the WLAN transceiver to transmit the FTM request to the WLAN STA over the wireless communication channel.

4. The apparatus of claim 2, wherein the identifier comprises at least one identifier selected from a group consisting of a Media Access Control (MAC) address, and a Basic Service Set Identifier (BSSID).

5. The apparatus of any one of claims 1-4, wherein the FTM component is configured to trigger the WLAN transceiver to communicate an FTM request with a WLAN STA of said one or more WLAN STAs, based on the FTM capability information, and to select to avoid a WLAN scan for the WLAN STA over one or more wireless communication channels supported by the WLAN transceiver.

6. The apparatus of any one of claims 1-4, wherein the FTM component is configured to trigger the WLAN transceiver to communicate an FTM request with a WLAN STA of said one or more WLAN STAs, based on the FTM capability information, and to select to avoid sending to the WLAN STA an inquiry on a capability of the WLAN STA to support FTM.

7. The apparatus of any one of claims 1 -4, wherein the FTM component is configured to trigger the WLAN transceiver to communicate an FTM request with a WLAN STA of said one or more WLAN STAs, based on the FTM capability information, and to select to avoid listening for WLAN beacons over one or more wireless communication channels supported by the WLAN transceiver.

8. The apparatus of any one of claims 1-4, wherein the FTM component is configured to determine a location of the UE based on timing information corresponding to the FTM messages.

9. The apparatus of any one of claims 1-4, wherein the cellular message comprises a Radio Resource Control (RRC) message.

10. The apparatus of any one of claims 1-4, wherein the one or more WLAN STAs comprise at least one WLAN Access Point (AP).

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

12. A product comprising one or more tangible computer-readable storage media comprising computer-executable instructions operable to, when executed by at least one computer processor, enable the at least one computer processor to implement one or more operations at a User Equipment (UE), the operations comprising:

processing a cellular message from an Evolved Node B (eNB), the cellular message comprising Fine Timing Measurement (FTM) capability information indicating a capability of one or more Wireless Local Area Network (WLAN) stations (STAs) to support FTM; and based on said FTM capability information, triggering a WLAN transceiver of the UE to communicate FTM messages with the one or more WLAN STAs.

13. The product of claim 12, wherein the FTM capability information comprises an identifier to identify a WLAN STA capable of responding to an FTM request, and radio frequency information indicating a wireless communication channel to communicate the FTM messages with the WLAN STA.

14. The product of claim 12 or 13, wherein the operations comprise triggering the WLAN transceiver to communicate an FTM request with a WLAN STA of said one or more WLAN STAs, based on the FTM capability information, and selecting to avoid a WLAN scan for the WLAN STA over one or more wireless communication channels supported by the WLAN transceiver.

15. A system of cellular communication comprising an apparatus of an Evolved Node B (eNB), the apparatus comprising:

a message processor configured to generate a cellular message comprising Fine Timing Measurement (FTM) capability information indicating a capability of one or more Wireless Local Area Network (WLAN) stations (STAs) to support FTM; and

a cellular interface configured to send the cellular message to a User Equipment (UE) via a cellular link. '

16. The system of claim 15, wherein the FTM capability information comprises an identifier to identify a WLAN STA capable of responding to an FTM request, and radio frequency information indicating a wireless communication channel to communicate FTM messages with the WLAN STA.

17. The system of claim 16, wherein the■ identifier comprises at least one identifier selected from a group consisting of a Media Access Control (MAC) address, and a Basic Service Set Identifier (BSSID).

18. The system of claim 15, wherein the eNB comprises a collocated eNB Access Point (eNB/AP), the collocated eNB/AP comprising a WLAN AP, the FTM capability information indicating a capability of the WLAN AP to support FTM.

19. The system of claim 15, wherein the apparatus comprises a WLAN control interface to communicate with the one or more WLAN STAs.

20. The system of any one of claims 15-19, wherein the cellular message comprises a Radio Resource Control (RRC) message.

21. The system of any one of claims 15- 19, wherein the one or more WLAN STAs comprise at least one WLAN Access Point (AP)..

22. The system of any one of claims 15-19, wherein the apparatus comprises one or more antennas, a memory and a processor.

23. A method to be performed at an Evolved Node B (eNB), the method comprising: generating a cellular message comprising Fine Timing Measurement (FTM) capability information indicating a capability of one or more Wireless Local Area Network (WLAN) stations (STAs) to support FTM; and

sending the cellular message to a User Equipment (UE) via a cellular link.

24. The method of claim 23, wherein the FTM capability information comprises an identifier to identify a WLAN STA capable of responding to an FTM request, and radio frequency information indicating a wireless communication channel to communicate FTM messages with the WLAN STA.

25. A product comprising one or more tangible computer-readable storage media comprising computer-executable instructions operable to, when executed by at least one computer processor, enable the at least one computer processor to perform the method of claim 23 or 24.