WLAN-based RF sensing in cellular systems

Abstract

Various techniques related to wireless communication at a UE are disclosed herein. The UE transmits capability information for the WLAN RF-based sensing of the wireless device. The UE obtains at least one of configuration or assistance data for WLAN RF-based sensing of the wireless device based on the capability information, wherein the at least one of the configuration or assistance data indicates at least one of a set of RF sensing measurements for the WLAN RF-based sensing or a set of RF sensing parameters for the WLAN RF-based sensing.

Description

Cross-references to related applications

[0001] This application claims the benefit of U.S. Non-Provisional Patent Application Serial No. 18 / 306,148, filed April 24, 2023, entitled “WLAN-Based RF Sensing in Cellular Systems,” the entire contents of which are expressly incorporated herein by reference. Technical Field

[0002] This disclosure relates generally to communication systems, and more specifically to sensing based on wireless local area networks (WLANs). Background Technology

[0003] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0004] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the city, national, regional, and even global levels. An example telecommunications standard is 5G New Radio (NR). 5G NR is part of the Continuous Evolution of Mobile Broadband (CEM) program issued by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT),) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Some aspects of 5G NR can be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. Furthermore, these improvements can also be applied to other multiple access technologies and telecommunications standards that adopt these technologies. Summary of the Invention

[0005] The following is a simplified summary of one or more aspects to provide a basic understanding of these aspects. This summary is not a comprehensive overview of all conceived aspects. It neither identifies key or essential elements of all aspects nor describes the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed descriptions that follow.

[0006] In one aspect of this disclosure, a method, computer-readable medium, and apparatus for wireless communication at a network entity are provided. The apparatus includes: a memory; and at least one processor coupled to the memory, and configured, at least in part, based on information stored in the memory, to: obtain capability information for sensing based on a wireless local area network (WLAN) radio frequency (RF) for at least one wireless device; and to transmit, for the at least one wireless device and based on the capability information, at least one of configuration or auxiliary data for the WLAN RF-based sensing, wherein the at least one of the configuration or auxiliary data indicates at least one of a set of RF sensing measurements or a set of RF sensing parameters for the WLAN RF-based sensing.

[0007] In one aspect of this disclosure, a method, computer-readable medium, and apparatus for wireless communication at a wireless device are provided. The apparatus includes: a memory; and at least one processor coupled to the memory, and is configured, at least in part, based on information stored in the memory, to: transmit capability information for wireless local area network (WLAN)-based radio frequency (RF) sensing of the wireless device; and to obtain, based on the capability information, at least one of configuration or auxiliary data for WLAN-based RF sensing of the wireless device, wherein the at least one of the configuration or auxiliary data indicates at least one of a set of RF sensing measurements or a set of RF sensing parameters for WLAN-based RF sensing.

[0008] To achieve the foregoing and related objectives, one or more aspects may include the features fully described below and specifically pointed out in the claims. The following description and drawings set forth some exemplary features of one or more aspects in detail. However, these features indicate only a few of the various ways in which the principles of the various aspects may be employed. Attached Figure Description

[0009] Figure 1 This is a diagram illustrating an example of a wireless communication system and an access network.

[0010] Figure 2A This is an illustration of an example of the first frame according to various aspects of this disclosure.

[0011] Figure 2B This is a diagram illustrating examples of downlink (DL) channels within a subframe according to various aspects of this disclosure.

[0012] Figure 2C This is an illustration of an example of a second frame according to various aspects of this disclosure.

[0013] Figure 2D This is a diagram illustrating examples of uplink (UL) channels within a subframe according to various aspects of this disclosure.

[0014] Figure 3 This is a diagram illustrating examples of base stations and user equipment (UEs) in an access network.

[0015] Figure 4 This is a diagram illustrating an example of UE positioning based on reference signal measurements.

[0016] Figure 5 This is a diagram illustrating an example of a wireless communication system.

[0017] Figure 6 This is a diagram illustrating the example positioning process.

[0018] Figure 7 This is an illustration of an example aspect of positioning technology.

[0019] Figure 8 This is an example diagram illustrating a aspect of location based on a wireless local area network (WLAN).

[0020] Figure 9 This is a diagram illustrating an example aspect of WLAN-based positioning.

[0021] Figure 10 This is a diagram illustrating an example aspect of WLAN-based positioning.

[0022] Figure 11 This is a diagram illustrating an example aspect of sensing feedback for WLAN-based positioning.

[0023] Figure 12 This is an illustration of an example of a wireless device that shares WLAN radio frequency (RF) sensing capabilities with sensing entities in the core network.

[0024] Figure 13 This is a diagram illustrating an example aspect of configuring a UE for WLAN-based RF sensing.

[0025] Figure 14 This is a diagram illustrating an example aspect of configuring an access point (AP) for WLAN-based RF sensing.

[0026] Figure 15 This is a diagram illustrating an example aspect of auxiliary data used for WLAN-based RF sensing.

[0027] Figure 16 This is a diagram illustrating an example of communication between a network entity and a wireless device.

[0028] Figure 17 This is a flowchart of a wireless communication method.

[0029] Figure 18 This is a flowchart of a wireless communication method.

[0030] Figure 19 This is a diagram illustrating an example of a hardware implementation used in an example device.

[0031] Figure 20 This is a diagram illustrating an example of a hardware implementation used for an example network entity.

[0032] Figure 21 This is a diagram illustrating an example of a hardware implementation used for an example network entity. Detailed Implementation

[0033] Cellular communication systems can utilize various technologies for positioning to determine the location of a UE or another object. WLAN communication systems can utilize WLAN RF sensing for positioning purposes. However, the interaction between positioning in cellular and WLAN communication systems may not be well-defined regarding specific characteristics of WLAN RF sensing, leading to technical challenges. For example, a cellular communication system may not be configured to facilitate positioning in the absence of a UE.

[0034] Various aspects are involved in sensing as a whole. Some aspects are more specifically involved in WLAN-based sensing. In one example, a network entity obtains capability information for sensing via the radio frequency (RF) of at least one wireless device using a wireless local area network (WLAN). The network entity transmits, for the at least one wireless device and based on the capability information, at least one of configuration or auxiliary data for WLAN-based RF sensing, wherein the at least one of the configuration or auxiliary data indicates at least one of a set of RF sensing measurements or a set of RF sensing parameters for WLAN-based RF sensing.

[0035] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, by transmitting at least one of configuration or auxiliary data for WLAN RF-based sensing, a network entity can enable at least one wireless device to perform enhanced positioning techniques using WLAN RF-based sensing. For example, configuration and / or auxiliary data can enable at least one wireless device to determine the location of a wireless device or another object in a more accurate manner compared to a wireless device that has not received configuration (which is based on capability information) or auxiliary data for WLAN RF-based sensing. In another example, the transmitted configuration and / or auxiliary data can enable positioning to be performed via an AP without involving a UE. Furthermore, the transmitted configuration can enable the AP to transmit sensing results to a network entity without assistance from a UE.

[0036] The detailed descriptions following, illustrated with reference to the accompanying drawings, describe various configurations and do not represent the only configurations in which the concepts described herein can be practiced. To provide a thorough understanding of the various concepts, the detailed descriptions include specific details. However, these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0037] Various apparatuses and methods are presented with reference to several aspects of a telecommunications system. These apparatuses and methods are described in detail below and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively, “elements”). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0038] As an example, an element, any part of an element, or any combination of elements may be implemented as a “processing system” including one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in a processing system may execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, or any combination thereof.

[0039] Therefore, in one or more example aspects, specific implementations, and / or use cases, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality may be stored or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media. Storage media can be any available medium that can be accessed by a computer. By way of example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disc storage devices, magnetic disk storage devices, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures accessible by a computer.

[0040] While aspects, implementations, and / or use cases are described herein by way of example, additional or different aspects, implementations, and / or use cases may arise in many different arrangements and scenarios. The aspects, implementations, and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, aspects, implementations, and / or use cases may arise via integrated chip implementations and other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specific to a use case or application, the described examples may exhibit broad applicability. Aspects, implementations, and / or use cases can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the technologies described herein. In some practical settings, devices incorporating the described aspects and features may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily involve multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or decomposed components, end-user equipment, etc., of various sizes, shapes, and configurations.

[0041] The deployment of communication systems such as 5G NR systems can be arranged in a variety of ways using various components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, radio access network (RAN) nodes, core network nodes, network elements or network equipment (such as base stations (BS)), or one or more units (or components) performing base station functionality can be implemented in aggregated or decomposed architectures. For example, BSs (such as Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit / receive point (TRP), or cell, etc.) can be implemented as aggregated base stations (also known as standalone BS or monolithic BS) or decomposed base stations.

[0042] Aggregated base stations can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. Decentralized base stations can be configured to utilize a protocol stack that is physically or logically distributed across two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some respects, the CU may be implemented within a RAN node, and one or more DUs may co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. DUs may be implemented to communicate with one or more RUs. Each of the CUs, DUs, and RUs may be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0043] Base station operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be used in Integrated Access Backhaul (IAB) networks, Open Radio Access Networks (O-RAN (such as network configurations advocated by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)). Decomposition can include distributing functionality across two or more units in various physical locations, as well as virtually distributing the functionality of at least one unit, which enables flexibility in network design. The various units of a decomposed base station or decomposed RAN architecture can be configured to communicate wirelessly with at least one other unit.

[0044] Figure 1 Figure 100 illustrates an example of a wireless communication system and access network. The illustrated wireless communication system includes a decomposed base station architecture. The decomposed base station architecture may include one or more CUs 110, which may communicate directly with the core network 120 via a backhaul link, or indirectly with the core network 120 via one or more decomposed base station units, such as a near real-time (near-RT) RAN Intelligent Controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a Service Management and Orchestration (SMO) framework 105, or both. CUs 110 may communicate with one or more DUs 130 via a corresponding midhaul link (such as an F1 interface). DUs 130 may communicate with one or more RUs 140 via a corresponding fronthaul link. RUs 140 may communicate with a corresponding UE 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

[0045] Each of the units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO frame 105) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of these units, may be configured to communicate with one or more other units via transmission media. For example, these units may include wired interfaces configured to receive signals or transmit signals to one or more other units via wired transmission media. Additionally, these units may include wireless interfaces that may include receivers, transmitters, or transceivers (such as RF transceivers) configured to receive signals via wireless transmission media or transmit signals to one or more other units, or both.

[0046] In some aspects, the CU 110 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Serving Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by the CU 110. The CU 110 can be configured to handle user plane functionality (i.e., Central Unit-User Plane (CU-UP)), control plane functionality (i.e., Central Unit-Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 110 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 110 can be implemented to communicate with the DU 130 for network control and signaling purposes, as needed.

[0047] DU 130 may correspond to a logic unit that includes one or more base station functions for controlling the operation of one or more RU 140s. In some aspects, DU 130 may at least partially host one or more of the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) according to functional splits (such as those defined by 3GPP). In some aspects, DU 130 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signaling with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

[0048] Lower-layer functionality can be implemented by one or more RU 140s. In some deployments, an RU140 controlled by a DU 130 may correspond to a logical node that hosts RF processing functions or low-PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, or both, based at least in part on functional decomposition (such as lower-layer functional decomposition). In such architectures, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UE 104s. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration enables the implementation of the DU 130 and CU 110 in cloud-based RAN architectures such as vRAN architectures.

[0049] SMO framework 105 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 105 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, SMO framework 105 can be configured to interact with a cloud computing platform such as Open Cloud (O-Cloud) 190 to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface such as the O2 interface. Such virtualized network elements may include, but are not limited to, CU 110, DU 130, RU 140, and near-RT RIC 125. In some implementations, SMO framework 105 can communicate with the hardware aspects of the 4G RAN (such as Open eNB (O-eNB) 111) via the O1 interface. Additionally, in some implementations, SMO framework 105 can communicate directly with one or more RU 140s via the O1 interface. SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of SMO framework 105.

[0050] The non-RT RIC 115 can be configured to include logical functions enabling non-real-time control and optimization of RAN elements and resources, including artificial intelligence (AI) / machine learning (ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 125. The non-RT RIC 115 can be coupled to or communicate with the near-RT RIC 125, such as via an A1 interface. The near-RT RIC 125 can be configured to include logical functions enabling near real-time control and optimization of RAN elements and resources via data collection and actions through an interface such as an E2 interface, connecting one or more CU 110s, one or more DU 130s, or both, and O-eNBs to the near-RT RIC 125.

[0051] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 125, the non-RT RIC 115 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 125 and may be received from non-network data sources or network functions at the SMO framework 105 or the non-RT RIC 115. In some examples, the non-RT RIC 115 or the near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 may monitor long-term trends and patterns in performance and employ AI / ML models to perform corrective actions via the SMO framework 105 (such as reconfiguration via O1) or by creating RAN management policies (such as A1 policies).

[0052] At least one of CU 110, DU 130, and RU 140 may be referred to as base station 102. Therefore, base station 102 may include one or more of CU 110, DU 130, and RU 140 (each component is indicated by a dashed line to indicate that each component may or may not be included in base station 102). Base station 102 provides UE 104 with an access point to core network 120. Base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Small cells include femtocells, picocells, and microcells. A network that includes both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include an evolved home node B (eNB) (HeNB), which can provide service to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) transmission (also known as reverse link) from UE 104 to RU 140 and / or downlink (DL) transmission (also known as forward link) transmission from RU 140 to UE 104. The communication link may utilize multiple-input multiple-output (MIMO) antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may use one or more carriers. For each carrier allocated in a carrier aggregation of up to Yx MHz (x component carriers) for transmission in each direction, base station 102 / UE 104 may use a spectrum with a bandwidth of up to Y MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.). Carriers may be adjacent to each other or may not be adjacent to each other. Carrier allocation may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). Component carriers may include primary component carriers and one or more secondary component carriers. The primary component carrier can be referred to as the primary cell (PCell) and the secondary component carrier can be referred to as the secondary cell (SCell).

[0053] Some UEs 104 can communicate with each other using device-to-device (D2D) communication link 158. D2D communication link 158 can use DL / UL Wireless Wide Area Network (WWAN) spectrum. D2D communication link 158 can use one or more sidelink channels, such as Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Shared Channel (PSSCH), and Physical Sidelink Control Channel (PSCCH). D2D communication can be performed through various wireless D2D communication systems, such as Bluetooth™ (Bluetooth is a trademark of the Bluetooth Special Interest Group (SIG), Wi-Fi™ based on the IEEE 802.11 standard (Wi-Fi is a trademark of the Wi-Fi Alliance), LTE, or NR.

[0054] The wireless communication system may also include a Wi-Fi™ AP 150 that communicates with the UE 104 (also known as a Wi-Fi station (STA)) via a communication link 154, for example, in an unlicensed spectrum such as 5 GHz. When communicating in unlicensed spectrum, the UE 104 / AP150 may perform a free channel assessment (CCA) to determine whether the channel is available before communication.

[0055] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz–7.125GHz) and FR2 (24.25GHz–52.6GHz). Although a portion of FR1 is greater than 6GHz, in various documents and articles, FR1 is often (interchangeably) referred to as the “sub-6GHz” band. Similar naming issues sometimes occur with FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although this is distinct from the Extremely High Frequency (EHF) band (30GHz–300GHz) designated as a “millimeter wave” band by the International Telecommunication Union (ITU).

[0056] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR studies have identified the operating bands used for these mid-band frequencies as the frequency range designation FR3 (7.125GHz–24.25GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 to mid-band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6GHz. For example, three higher operating bands have been identified as the frequency range designations FR2-2 (52.6GHz–71GHz), FR4 (71GHz–114.25GHz), and FR5 (114.25GHz–300GHz). Each of these higher bands falls within the EHF band.

[0057] In view of the above, unless otherwise specified, the term "below 6 GHz" as used herein can broadly refer to frequencies less than 6 GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise specified, the term "millimeter wave" as used herein can broadly refer to frequencies that can include intermediate frequency band frequencies, within FR2, FR4, FR2-2 and / or FR5, or within the EHF band.

[0058] Base station 102 and UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. Base station 102 may transmit beamformed signals 182 to UE 104 in one or more transmit directions. UE 104 may receive beamformed signals from base station 102 in one or more receive directions. UE 104 may also transmit beamformed signals 184 to base station 102 in one or more transmit directions. Base station 102 may receive beamformed signals from UE 104 in one or more receive directions. Base station 102 / UE 104 may perform beamforming training to determine the optimal receive and transmit directions for each of base station 102 / UE 104. The transmit and receive directions of base station 102 may be the same or different. The transmit and receive directions of UE 104 may be the same or different.

[0059] Base station 102 may include and / or be referred to as gNB, Node B, eNB, access point, base transceiver, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), TRP, network node, network entity, network equipment, or some other suitable terminology. Base station 102 may be implemented as an integrated access and backhaul (IAB) node, relay node, sidelink node, aggregated (monolithic) base station with baseband units (BBU) (including CU and DU) and RU, or may be implemented as a decomposed base station including one or more of CU, DU, and / or RU. A collection of base stations that may include decomposed base stations and / or aggregated base stations may be referred to as Next Generation (NG) RAN (NG-RAN).

[0060] The core network 120 may include Access and Mobility Management Function (AMF) 161, Session Management Function (SMF) 162, User Plane Function (UPF) 163, Unified Data Management (UDM) 164, one or more location servers 168, and other functional entities. AMF 161 is the control node that handles signaling between UE 104 and the core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports authentication and key agreement (AKA) credential generation, user identity processing, access authorization, and subscription management. One or more location servers 168 are exemplified as including a Gateway Mobile Location Center (GMLC) 165 and a Location Management Function (LMF) 166. However, generally, one or more location servers 168 may include one or more location / positioning servers, which may include one or more of GMLC 165, LMF 166, Position Determination Entity (PDE), Serving Mobile Location Center (SMLC), Mobile Location Center (MPC), etc. GMLC 165 and LMF 166 support UE location services. GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE location information. LMF 166 receives measurement and auxiliary information from NG-RAN and UE 104 via AMF 161 to calculate the location of UE 104. NG-RAN may use one or more positioning methods to determine the location of UE 104. Positioning UE 104 may involve signal measurement, location estimation, and optional speed calculation based on these measurements. Signal measurement may be performed by UE 104 and / or base station 102 serving UE 104. The measured signals may be based on one or more of the following: Satellite Positioning System (SPS) 170 (e.g., one or more of Global Navigation Satellite System (GNSS), Global Positioning System (GPS), Non-Terrestrial Network (NTN) or other satellite positioning / location systems), LTE signals, Wireless Local Area Network (WLAN) signals, Bluetooth signals, Terrestrial Beacon System (TBS), sensor-based information (e.g., barometric pressure sensor, motion sensor), NR Enhanced Cell ID (NR E-CID) method, NR signals (e.g., multiple round-trip time (multiple RTT), DL departure angle (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning) and / or other systems / signals / sensors.

[0061] Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, GPS devices, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet devices, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional device. Some UEs in UE 104 may be referred to as IoT devices (e.g., parking meters, air pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, mobile phone, user agent, mobile client, client, or some other suitable terminology. In some scenarios, the term UE may also be applied to one or more companion devices, such as in a device constellation arrangement. One or more of these devices may access the network together and / or individually.

[0062] Refer again Figure 1 In some aspects, the core network 120 may have a WLAN RF sensing component 198, which can be configured to acquire capability information for WLAN RF-based sensing of at least one wireless device; and to transmit, for at least one wireless device and based on the capability information, at least one of configuration or auxiliary data for WLAN RF-based sensing, wherein the at least one of the configuration or auxiliary data indicates at least one of a set of RF sensing measurements or a set of RF sensing parameters for WLAN RF-based sensing. In some aspects, the UE 104 and / or Wi-Fi™ AP 150 may have a WLAN RF sensing component 199, which can be configured to transmit capability information for WLAN RF-based sensing of a wireless device; and to acquire, based on the capability information, at least one of configuration or auxiliary data for WLAN RF-based sensing of a wireless device, wherein the at least one of the configuration or auxiliary data indicates at least one of a set of RF sensing measurements or a set of RF sensing parameters for WLAN RF-based sensing. Although the following description may focus on 5G NR, the concepts described herein may also be applied to other types of wireless communication systems.

[0063] Figure 2A Figure 200 illustrates an example of the first subframe within a 5G NR frame structure. Figure 2BFigure 230 illustrates an example of a DL channel within a 5G NR subframe. Figure 2C Figure 250 is an example of a second subframe within a 5G NR frame structure. Figure 2D Figure 280 illustrates an example of a UL channel within a 5G NR subframe. The 5G NR frame structure can be Frequency Division Duplex (FDD) (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to either DL or UL) or Time Division Duplex (TDD) (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to both DL and UL). Figure 2A , Figure 2C In the provided example, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28 respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are both DL and UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The slot format is configured for the UE via the received Slot Format Indicator (SFI) (dynamically configured via DL Control Information (DCI) or semi-statically / statically configured via Radio Resource Control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0064] Figures 2A to 2D The frame structure is illustrated, and aspects of this disclosure are applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10 ms) can be divided into 10 equal-sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include micro-time slots, which may include 7, 4, or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each time slot may include 14 symbols, and for extended CP, each time slot may include 12 symbols. Symbols on the DL may be CP Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. Symbols on the UL may be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Extended OFDM (DFT-s-OFDM) symbols (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and a parameter set. The parameter set defines the subcarrier spacing (SCS) (see Table 1). Symbol length / duration can be scaled with 1 / SCS.

[0065]

[0066] Table 1: Parameter Set, SCS, and CP

[0067] For a normal CP (14 symbols / slot), different parameter sets µ 0 through 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For an extended CP, parameter set 2 allows 4 slots per subframe. Therefore, for a normal CP and parameter set µ, there are 14 symbols / slot and 2... µ One time slot / subframe. Subcarrier spacing can be equal to ,in The parameter sets are 0 to 4. Therefore, the subcarrier spacing is 15 kHz for parameter set µ=0 and 240 kHz for parameter set µ=4. The symbol length / duration is negatively correlated with the subcarrier spacing. Figures 2A to 2D Examples of a normal frequency division multiplexing (CP) with 14 symbols per time slot and a parameter set of µ=2 with 4 time slots per subframe are provided. The time slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within the frame set, there may be one or more distinct bandwidth portions (BWPs) of frequency division multiplexing (see [link to relevant documentation]). Figure 2B Each BWP can have a specific set of parameters and CP (normal or extended).

[0068] A resource grid can be used to represent the frame structure. Each time slot consists of a resource block (RB) extending for 12 consecutive subcarriers (also known as a physical RB (PRB)). The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0069] like Figure 2A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. RS may include demodulation RS (DM-RS) (indicated as R for a particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE. RS may also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

[0070] Figure 2BExamples of various DL channels within a subframe of a frame are illustrated. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE comprising six RE Groups (REGs), each REG comprising 12 consecutive REs in the OFDM symbol of the RB. A PDCCH within a BWP can be referred to as a Control Resource Set (CORESET). The UE is configured to monitor PDCCH candidates in the PDCCH search space (e.g., the common search space, the UE-specific search space) during PDCCH monitoring timing on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. The Primary Synchronization Signal (PSS) may be located within symbol 2 of a specific subframe of the frame. The PSS is used by the UE 104 to determine subframe / symbol timing and physical layer identification. The Secondary Synchronization Signal (SSS) may be located within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the Physical Layer Cell Identifier Group Number and radio frame timing. Based on the Physical Layer Identifier and the Physical Layer Cell Identifier Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The Physical Broadcast Channel (PBCH), carrying the Master Information Block (MIB), can be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block (also known as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the System Frame Number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (such as System Information Block (SIB)), and paging messages.

[0071] like Figure 2C As illustrated, some REs in the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and DM-RS for the Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS can be transmitted in the first or first two symbols of the PUSCH. Depending on whether a short or long PUCCH is transmitted and depending on the specific PUCCH format used, the PUCCH DM-RS can be transmitted in different configurations. The UE can transmit a Sounding Reference Signal (SRS). The SRS can be transmitted in the last symbol of a subframe. The SRS can have a comb structure, and the UE can transmit the SRS on one of the comb teeth. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

[0072] Figure 2DExamples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), pre-decoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUCCH carries data and may additionally be used to carry buffer status reports (BSR), power clearance reports (PHR), and / or UCIs.

[0073] Figure 3 This is a block diagram illustrating communication between base station 310 and UE 350 in the access network. In the DL, Internet Protocol (IP) packets can be provided to controller / processor 375. Controller / processor 375 implements Layer 3 and Layer 2 functionality. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the delivery of upper-layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority ordering.

[0074] Transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) decoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. TX processor 316 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to OFDM subcarriers, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and then combined using inverse fast Fourier transform (IFFT) to produce a physical channel carrying a stream of time-domain OFDM symbols. The OFDM stream undergoes spatial pre-decoding to generate multiple spatial streams. Channel estimates from channel estimator 374 can be used to determine decoding and modulation schemes, as well as for spatial processing. Channel estimates can be derived from reference signals and / or channel state feedback transmitted by UE 350. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx can utilize the corresponding spatial stream to modulate a radio frequency (RF) carrier for transmission.

[0075] At UE 350, each receiver 354Rx receives signals via its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides that information to the receive (RX) processor 356. The TX processor 368 and RX processor 356 implement Layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for UE 350. If multiple spatial streams are destined for UE 350, the RX processor 356 can combine them into a single OFDM symbol stream. The RX processor 356 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal consists of a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, along with the reference signal, are recovered and demodulated by determining the most probable signal constellation point transmitted by base station 310. These soft decisions can be based on a channel estimate calculated by channel estimator 358. The soft decision is then decoded and deinterleaved to recover the data and control signals originally transmitted by base station 310 on the physical channel. The data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functionality.

[0076] The controller / processor 359 may be associated with a memory 360 that stores program code and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller / processor 359 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transport and logical channels to recover IP packets. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0077] Similar to the functionality described in conjunction with DL transmission performed by base station 310, controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connectivity, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with upper-layer PDU delivery, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority ordering.

[0078] The TX processor 368 can use the channel estimate derived from the reference signal or feedback transmitted by the channel estimator 358 from the base station 310 to select an appropriate decoding and modulation scheme and facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via individual transmitters 354Tx. Each transmitter 354Tx can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0079] UL transmission is processed at base station 310 in a manner similar to that described in conjunction with the receiver function at UE 350. Each receiver 318Rx receives signals via its corresponding antenna 320. Each receiver 318Rx recovers the information modulated onto the RF carrier and provides that information to RX processor 370.

[0080] The controller / processor 375 may be associated with a memory 376 that stores program code and data. The memory 376 may be referred to as a computer-readable medium. In UL, the controller / processor 375 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets between transport and logical channels. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0081] At least one of the TX processor 368, RX processor 356, and controller / processor 359 can be configured to perform and Figure 1 Various aspects related to the WLAN RF sensing component 199.

[0082] Figure 4 Figure 400 illustrates an example of UE positioning based on reference signal measurements. UE 404 can be positioned at time T. SRS_TX Send UL-SRS 412 and at time T PRS_RX Receives the DL positioning reference signal (PRS) (DL-PRS) 410. TRP 406 can be used at time T. SRS_RX Receive UL-SRS 412 and at time T PRS_TX Send DL-PRS 410. UE 404 may receive DL-PRS 410 before sending UL-SRS 412, or may send UL-SRS 412 before receiving DL-PRS 410. In both cases, the location server (e.g., location server 168) or UE 404 may base its response on ||T SRS_RX – T PRS_TX | – |T SRS_TX – T PRS_RX || to determine RTT 414. Therefore, multi-RTT positioning can utilize the UE Rx-Tx time difference measurement (i.e., |T) of downlink signals received from multiple TRPs 402, 406 and measured by UE 404. SRS_TX – T PRS_RX |) and DL-PRS reference signal received power (RSRP) (DL-PRS-RSRP), and the measured TRP Rx-Tx time difference measurement (i.e., |T) of the uplink signal transmitted from UE 404 at multiple TRPs 402, 406. SRS_RX – T PRS_TX |) and UL-SRS-RSRP. UE 404 uses auxiliary data received from the location server to measure the UE Rx-Tx time difference (and optionally the DL-PRS-RSRP of the received signal), and TRPs 402 and 406 use auxiliary data received from the location server to measure the gNB Rx-Tx time difference (and optionally the UL-SRS-RSRP of the received signal). These measurements can be used at the location server or at UE 404 to determine the RTT, which is used to estimate the location of UE 404. Other methods for determining the RTT are possible, such as, for example, using DL-TDOA and / or UL-TDOA measurements.

[0083] DL-AoD positioning utilizes the measured DL-PRS-RSRP of downlink signals received at UE 404 from multiple TRPs 402 and 406. UE 404 uses auxiliary data received from the positioning server to measure the DL-PRS-RSRP of the received signals, and the resulting measurement, along with the departure azimuth angle (A-AoD), departure zenith angle (Z-AoD), and other configuration information, is used to position UE 404 relative to adjacent TRPs 402 and 406.

[0084] DL-TDOA positioning utilizes the DL Reference Signal Time Difference (RSTD) (and optionally DL-PRS-RSRP) of downlink signals received at UE 404 from multiple TRPs 402, 406. UE 404 uses auxiliary data received from the positioning server to measure the DL RSTD (and optionally DL-PRS-RSRP) of the received signals, and the resulting measurement, along with other configuration information, is used to position UE 404 relative to adjacent TRPs 402, 406.

[0085] UL-TDOA positioning utilizes the UL relative time of arrival (RTOA) (and optionally UL-SRS-RSRP) of the uplink signal transmitted from UE 404 at multiple TRPs 402, 406. TRPs 402, 406 use auxiliary data received from the positioning server to measure the UL-RTOA (and optionally UL-SRS-RSRP) of the received signal, and the resulting measurements, along with other configuration information, are used to estimate the location of UE 404.

[0086] UL-AoA positioning utilizes the measured azimuth (A-AoA) and zenith (Z-AoA) of the uplink signal transmitted from UE 404 at multiple TRPs 402 and 406. TRPs 402 and 406 use auxiliary data received from the positioning server to measure the A-AoA and Z-AoA of the received signal, and the resulting measurements, along with other configuration information, are used to estimate the position of UE 404.

[0087] Additional positioning methods can be used to estimate the location of UE 404, such as, for example, UE-side UL-AoD and / or DL-AoA. It should be noted that data / measurements from various technologies can be combined in various ways to increase accuracy, determine and / or enhance certainty, supplement / improve measurements, and / or replace / provide missing information.

[0088] Figure 5Figure 500 illustrates an example of estimating the location of a UE based on multi-RTT measurements from multiple TRPs according to various aspects of this disclosure. The UE 502 may be configured by the serving base station to decode DL-PRS resources 512 corresponding to and transmitted from first TRP 504 (TRP-1), second TRP 506 (TRP-2), third TRP 508 (TRP-3), and fourth TRP 510 (TRP-4). The UE 502 may also be configured to transmit UL-SRS on a UL-SRS resource set, which may include first SRS resource 514, second SRS resource 516, third SRS resource 518, and fourth SRS resource 520, such that the serving cell (e.g., first TRP 504, second TRP 506, third TRP 508, and fourth TRP 510) and other neighboring cells can be able to measure the UL-SRS resource set transmitted from the UE 502. For multi-RTT measurements based on DL-PRS and UL-SRS, since there may be a correlation between the UE's DL-PRS measurement and the TRP's UL-SRS measurement, the smaller the gap between the UE's DL-PRS measurement and the UE's UL-SRS transmission, the better the accuracy of estimating the UE's location and / or the UE's distance to each TRP.

[0089] In some aspects of wireless communication, the terms "location reference signal" and "PRS" generally refer to specific reference signals used for positioning in NR and LTE systems. However, as used herein, the terms "location reference signal" and "PRS" can also refer to any type of reference signal that can be used for positioning, such as, but not limited to, PRS, TRS, PTRS, CRS, CSI-RS, DMRS, PSS, SSS, SSB, SRS, UL-PRS, etc., as defined in LTE and NR. Furthermore, the terms "location reference signal" and "PRS" can refer to downlink or uplink positioning reference signals, unless otherwise indicated by the context. In some aspects, downlink positioning reference signals may be referred to as "DL-PRS," while uplink positioning reference signals (e.g., positioning SRS, PTRS) may be referred to as "UL-PRS." Additionally, for signals that can be transmitted in both uplink and downlink (e.g., DMRS, PTRS), these signals may be prefixed with "UL" or "DL" to distinguish direction. For example, "UL-DMRS" can be distinguished from "DL-DMRS."

[0090] Figure 6This is a communication flow 600 illustrating an example multi-RTT positioning process according to various aspects of this disclosure. The numbers associated with the communication flow 600 do not specify a particular time sequence and are used only as a reference to the communication flow 600. Furthermore, one or more subsets of this multi-RTT positioning process may be used for DL-only and / or UL-only positioning.

[0091] At 610, LMF 606 may request one or more positioning capabilities from UE 602 (e.g., from the target device). In some examples, the request for one or more positioning capabilities from UE 602 may be associated with the LTE Positioning Protocol (LPP). For example, LMF 606 may use the LPP capability delivery procedure to request positioning capabilities from UE 602. At 612, LMF 606 may request UL SRS configuration information from UE 602. LMF 606 may also provide auxiliary data (e.g., path loss reference, spatial relationships, and / or SSB configuration, etc.) specified by the serving base station 604. For example, LMF 606 may transmit an NR Positioning Protocol A (NRPPa) positioning information request message to the serving base station 604 to request UL information from UE 602.

[0092] At 614, the serving base station 604 may determine the resources available for UL SRS, and at 616, the serving base station 604 may configure one or more UL SRS resource sets for UE 602 based on the available resources. At 618, the serving base station 604 may provide UL SRS configuration information to LMF 606, such as via an NRPPa location information response message. At 620, LMF 606 may select one or more candidate neighboring BS / TRP 608, and LMF 606 may provide UL SRS configuration to one or more candidate neighboring BS / TRP 608 and / or the serving base station 604, such as via an NRPPa measurement request message. The message may include information enabling one or more candidate neighboring BS / TRP 608 and / or the serving base station to perform UL measurements.

[0093] At 622, LMF 606 may transmit an LPP (Local Power Request) auxiliary data message to UE 602. The message may include specified auxiliary data for UE 602 to perform DL (Low-Distance) measurements. At 624, LMF 606 may transmit an LPP request location information message to UE 602 to request multi-RTT (Multi-Round-Trip) measurements. At 626, for semi-persistent or aperiodic UL SRS, LMF 606 may request serving base station 604 to activate / trigger UL SRS in UE 602. For example, LMF 606 may request activation of UE SRS transmission by transmitting an NRPPa (Location Activation Request) message to serving base station 604.

[0094] At 628, the serving base station 604 can activate UE SRS transmission and transmit an NRPPa location activation response message. In response, UE 602 can begin UL-SRS transmission according to the temporal behavior configured for UL SRS resources. At 630, UE 602 can perform DL measurements from one or more candidate neighboring BS / TRPs 608 and / or the serving base station 604, as provided in the auxiliary data. At 632, each of the one or more configured candidate neighboring BS / TRPs 608 and / or the serving base station 604 can perform UL measurements. At 634, UE 602 can report the DL measurements to LMF 606, such as via an LPP location information message. At 636, each of the one or more candidate neighboring BS / TRPs 608 and / or the serving base station 604 can report the UL measurements to LMF 606, such as via an NRPPa measurement response message. At 638, LMF 606 can determine the RTT from UE 602 and the BS / TRP Rx-Tx time difference measurement of each of one or more candidate neighboring BS / TRP 608 and / or serving base station 604 that provide corresponding UL and DL measurements at 634 and 636, and LMF 606 can calculate the location of UE 602.

[0095] Some aspects of wireless communication can utilize different types of Positioning Reference Signals (PRS), such as downlink (DL) PRS. PRS is utilized by different wireless communications (e.g., New Radio (NR)) and positioning methods to enable devices (e.g., UEs) to detect and measure different objects. For example, a PRS can enable a UE to detect and measure the increase of neighboring TRPs or base stations. Several different types of positioning configurations are supported in wireless communications to enable various deployments or environments (e.g., indoor, outdoor, sub-6, mmW environments) for devices or UEs. Different types of wireless communications (e.g., NR) support both UE-assisted positioning methods (e.g., computational) and UE-based positioning methods. Furthermore, specific types of wireless communications (e.g., NR) can support several types of positioning methods. For example, NR positioning methods can support at least one of the following: NR multiple round-trip time (multiple RTT) positioning, NR downlink (DL) time difference of arrival (DL-TDOA) positioning, or NR DL departure angle (DL-AoD) positioning.

[0096] In some aspects, different types of reference signals (e.g., downlink (DL) or uplink (UL) reference signals) and UE measurements can be used to facilitate support for different positioning technologies. For example, DL PRS and DL reference signal time difference (RSTD) UE measurements can facilitate support for DL-TDOA positioning. Additionally, DL PRS and DL PRS reference signal received power (RSRP) UE measurements can facilitate support for DL-TDOA positioning, DL-AoD positioning, and / or multi-RTT positioning. Furthermore, DL PRS and probe reference signals (SRS) used for positioning and UE receive (Rx)-transmit (Tx) time difference UE measurements can facilitate support for multi-RTT positioning. Furthermore, synchronization signal blocks (SSBs) and channel state information (CSI)-reference signals (CSI-RS) used for radio resource management (RRM), as well as synchronization signal (SS)-RSRP (e.g., RSRP for RRM), SS-reference signal reception quality (SS-RSRQ) (e.g., for RRM), CSI-RSRP (e.g., for RRM) and CSI-RSRP (e.g., for RRM) can facilitate support for enhanced cell identifier (ID) (E-CID) location.

[0097] Different aspects of positioning can also utilize pre-configured DL PRS auxiliary data (AD). Pre-configured DL PRS AD refers to DL-PRS auxiliary data (with associated validity criteria) that can be provided to the UE (e.g., before or during an ongoing LTE Location Protocol (LPP) positioning session) and then used at a later time for potential positioning measurements (e.g., for a delayed Mobile Termination Location Request (MT-LR)). In some aspects, pre-configured DL-PRS auxiliary data may include multiple instances, each applicable to a different area within the network. Additionally, each DL-PRS auxiliary data instance may be associated with an area ID. In some instances, the area ID may include a list of cells the UE can camp on / connect to. Furthermore, the applicable area ID for the UE's location can be selected based on the cells the UE camps on / connects to. If the UE camps on / connects to one of the cells indicated in the cell list within the area ID, the instance of auxiliary data can be valid / selected.

[0098] Figure 7 Figure 700 illustrates an example aspect of positioning technology. Some cellular systems (i.e., wireless communication systems, such as 5G NR wireless communication systems) can support technologies that enable wireless devices to perform positioning (i.e., 5G NR positioning technology). Positioning can refer to determining the location of a wireless device or another object based on signals / data exchanged between a wireless device and another wireless device, measurements performed on the signals / data, and / or other types of measurements (i.e., location).

[0099] Location can include Radio Access Technology (RAT) related location 702. In RAT related location 702, the location of the wireless device is determined based on measurements performed on data / signals transmitted via a Radio Access Network (RAN) (such as a 5G NR RAN). RAT related location 702 can include Enhanced Cell ID (e-CID) location 704. In e-CID location 704, the UE's location can be calculated based on at least one of serving cell ID, timing advance, estimated timing and power of neighboring cells detected by the UE, and / or other information such as angle of arrival. In one example, e-CID location 704 can calculate the UE's location using received signal strength (RSS) measurements, RTT measurements, and / or angle of arrival measurements. RAT related location 702 can include downlink location 706. In downlink location 706, the UE's location can be calculated based on observed time difference of arrival (OTDOA) measurements. RAT related location 702 can include uplink location 708. In uplink positioning 708, the UE's positioning can be calculated based on uplink time difference of arrival (UTDOA) measurements.

[0100] Location can include RAT-independent positioning 710. In RAT-independent positioning 710, the location of a wireless device is determined based on measurements and / or other measurements performed on wirelessly transmitted data / signals. RAT-independent positioning 710 may be independent of the presence of a RAN (such as a 5G NR RAN). RAT-independent positioning 710 can include enhanced GNSS positioning 712, WLAN positioning 714, Bluetooth positioning 716, Terrestrial Beacon System (TBS) positioning 718, and sensor-based positioning 720. WLAN positioning 714 can refer to positioning performed via a wireless communication network based on the 802.11 protocol. For example, WLAN positioning 714 can utilize WLAN measurements (AP identifiers and optional other measurements) and a database to determine the location of the UE. The UE can measure signals received from a WLAN access point (AP), optionally assisted by auxiliary data, to transmit the measurements to a positioning server for location calculation. Using the measurement results and a reference database, the location of the UE can be calculated. Alternatively, the UE can utilize WLAN measurements and WLAN AP auxiliary data provided by the positioning server to determine the location of the UE. In one example, WLAN positioning 714 may include performing RTT measurements, Received Signal Strength Indicator (RSSI) measurements, and / or angle measurements. WLAN positioning 714 may also be referred to as WLAN RF-based positioning or WLAN-based positioning. Sensor-based positioning 720 may refer to positioning performed based on sensors in the UE, such as barometric pressure sensors, motion sensors, etc.

[0101] Positioning may include hybrid positioning 722. Hybrid positioning 722 may combine one or more aspects of RAT positioning 702 as described above and / or one or more aspects of RAT independent positioning 710. In one example, hybrid positioning 722 may include auxiliary GNSS (A-GNSS) positioning combined with OTDOA positioning.

[0102] Figure 8 Figure 800 illustrates an example aspect of WLAN-based positioning. This example aspect may correspond to the WLAN positioning 714 described above. In the first example 802, a target device may use a “WLAN-ProvideLocationInformation” information element (IE) to provide measurements for one or more WLANs to a location server. The “WLAN-ProvideLocationInformation” IE can also be used to provide WLAN positioning-specific error reasons. The first example 802 illustrates data that may be included in the “WLAN-ProvideLocationInformation” IE.

[0103] In the second example 804, the location server can use the "WLAN-RequestLocationInformation" IE to request WLAN measurements from the target device. The second example 804 illustrates data that can be included in the "WLAN-RequestLocationInformation" IE.

[0104] Figure 9 Figure 900 illustrates an example aspect of WLAN-based positioning. This example aspect may correspond to the WLAN positioning 714 described above. In a third example 902, the target device can use the "WLAN-ProvideCapabilities" IE to provide the location server with the target device's capabilities for WLAN positioning. The third example 902 illustrates data that can be included in the "WLAN-ProvideCapabilities" IE.

[0105] In Example 904, the location server can use the "WLAN-RequestCapabilities" IE to request WLAN location capability information from the target device. Example 904 illustrates the data that can be included in the "WLAN-RequestCapabilities" IE.

[0106] Figure 10This is an example illustration 1000 illustrating an example aspect of WLAN-based positioning. This example aspect may correspond to the WLAN positioning 714 described above. In the fifth example 1002, the location server or the target device can use a "WLAN-Error" IE to provide the error reason for the WLAN positioning to the target device or the location server, respectively. The fifth example 1002 illustrates data that can be included in the "WLAN-Error" IE.

[0107] In Example 1004, the location server can use the "WLAN-ProvideAssistanceData" IE to provide assistance information for UE-based and UE-assisted WLAN positioning. The "WLAN-ProvideAssistanceData" IE can also be used to provide WLAN positioning-specific error reasons. Example 1004 illustrates data that can be included in the "WLAN-ProvideAssistanceData" IE.

[0108] In the seventh example 1006, the target device can use the "WLAN-RequestAssistanceData" IE to request WLAN assistance from the location server. The seventh example 1006 illustrates the data that can be included in the "WLAN-RequestAssistanceData" IE.

[0109] Figure 11 Figure 1100 illustrates an example aspect of sensing feedback 1102 for WLAN-based positioning. Sensing feedback 1102 (which may also be referred to as "feedback") can refer to a measurement type that supports WLAN-based RF sensing. Sensing feedback 1102 can correspond to the IEEE 802.11bf protocol (i.e., supported by it).

[0110] Sensing feedback 1102 may include channel state information (CSI) feedback 1104. In CSI feedback 1104, a channel impulse response (time domain) may be returned for a combination of received (Rx) and / or transmitted (Tx). Sensing / radar processing may be performed at the initiating device (rather than the responding device) in CSI feedback 1104. CSI feedback 1104 can enable non-radar type sensing (e.g., sensing based on data / signals transmitted at frequencies less than 7 GHz).

[0111] Sensing feedback 1102 may include image feedback 1106. Image feedback 1106 may include two-dimensional (2D), three-dimensional (3D), and / or four-dimensional (4D) images, including one or more of distance measurements, azimuth measurements, elevation measurements, and / or Doppler measurements. In image feedback 1106, the responding device may perform filtering (e.g., constant false alarm rate (CFAR) filtering) to remove non-realistic reflections from the image; that is, the responding device may include real reflections, rather than non-realistic reflections, as part of the feedback.

[0112] Sensing feedback 1102 may include target feedback 1108. In target feedback 1108, the target may be an object, and the object may exhibit several reflections. In target feedback 1108, feedback for each target may include distance measurement, azimuth measurement, elevation measurement, and / or Doppler measurement, and the corresponding distance for each of the distance measurement, azimuth measurement, elevation measurement, and / or Doppler measurement. The response device may integrate the distance measurement, azimuth measurement, elevation measurement, and / or Doppler measurement (which may be collectively referred to as distance / azimuth / elevation / Doppler point) into the target.

[0113] Cellular communication systems can utilize various technologies for positioning to determine the location of a UE or another object. WLAN communication systems can utilize WLAN RF sensing for positioning purposes. However, the interaction between positioning in cellular and WLAN communication systems may not be well-defined regarding specific characteristics of WLAN RF sensing, leading to technical challenges. For example, a cellular communication system may not be configured to facilitate positioning in the absence of a UE.

[0114] This document describes various techniques related to WLAN-based RF sensing in cellular systems. In one example, a network entity obtains capability information for WLAN-based RF sensing of at least one wireless device. The network entity transmits, for the at least one wireless device and based on the capability information, at least one of configuration or auxiliary data for WLAN-based RF sensing, wherein the configuration or auxiliary data indicates at least one of a set of RF sensing measurements or a set of RF sensing parameters for WLAN-based RF sensing. By transmitting at least one of the configuration or auxiliary data for WLAN-based RF sensing, the network entity enables the at least one wireless device to perform enhanced positioning techniques. For example, compared to a wireless device that has not received configuration (based on capability information) or auxiliary data for WLAN-based RF sensing, the configuration and / or auxiliary data enables the at least one wireless device to determine the location of the wireless device or another object in a more accurate manner.

[0115] WLAN-based RF sensing can utilize Wi-Fi™ for RF sensing. This document describes the NR process for supporting WLAN-based RF sensing. In one example, a UE or AP can provide a sensing entity with its respective capabilities for WLAN RF sensing. In one example, capabilities may include the types of measurements supported by the UE / AP in WLAN-based RF sensing. Furthermore, the sensing entity can configure the UE for WLAN-based RF sensing.

[0116] Figure 12 Figure 1200 illustrates an example of a wireless device 1202 that shares the WLAN RF sensing capability 1204 with a sensing entity 1206 of the core network 1208. In one example, the core network 1208 may be a core network 120. In one example, the wireless device 1202 may be a UE or an access point (e.g., a WLAN AP).

[0117] Wireless device 1202 may transmit WLAN RF sensing capability 1204 to sensing entity 1206. WLAN RF sensing capability 1204 may indicate a first measurement type 1210 supported by wireless device 1202 in WLAN RF sensing. WLAN RF sensing capability 1204 may indicate an Nth measurement type 1212 supported by wireless device 1202 in WLAN RF sensing, where N is a positive integer greater than 1. In one example, the first measurement type 1210 and the Nth measurement type 1212 may include a distance map, a Doppler map, and / or an angle map (e.g., an azimuth map, an elevation map, etc.). In another example, the first measurement type 1210 and the Nth measurement type 1212 may include CSI feedback 1104, image feedback 1106, and / or target feedback 1108. WLAN RF sensing capability 1204 may indicate a combination of measurement types supported by wireless device 1202. For example, the first measurement type 1210 may be a distance map, and the Nth measurement type 1212 may be a Doppler map.

[0118] In one aspect, the sensing entity may send a request 1214 for WLAN RF sensing capability 1204. The wireless device 1202 may send the WLAN RF sensing capability 1204 to the sensing entity 1206 based on the receipt of the request 1214.

[0119] Figure 13Figure 1300 illustrates an example aspect of configuring a UE for WLAN-based RF sensing. In a first example 1302, the wireless device 1202 may be a UE 1304. After receiving WLAN RF sensing capability 1204, sensing entity 1206 may configure UE 1304 for WLAN-based RF sensing. For example, sensing entity 1206 may generate and transmit WLAN RF sensing configuration 1306 based on WLAN RF sensing capability 1204.

[0120] The WLAN RF sensing configuration 1306 may include an AP list 1308 that indicates with which the UE 1304 will perform WLAN-based RF sensing operations. In one example, the AP list 1308 may include an identifier for a first AP 1310. The AP list 1308 may also include an identifier for an Mth AP 1312, where M is a positive integer greater than 1.

[0121] The WLAN RF sensing configuration 1306 may include an indication of the measurement type 1314 that the UE 1304 will perform during WLAN-based RF sensing. Measurement type 1314 may include a range map, Doppler map, angle map (e.g., azimuth map, elevation map, etc.), CSI feedback 1104, image feedback 1106, and / or target feedback 1108. Measurement type 1314 may also be referred to as a feedback type.

[0122] The WLAN RF sensing configuration 1306 may include parameters 1316 for measurement type 1314 of WLAN-based RF sensing. Parameter 1316 may indicate reporting parameters (i.e., quantization parameters) for measurement type 1314. Parameter 1316 may specify characteristics used to perform WLAN-based RF sensing measurements and / or characteristics used to report WLAN-based RF sensing measurements to sensing entity 1206 (or another network entity). In one example, parameter 1316 may instruct UE 1304 to report WLAN-based RF sensing measurements for objects with speeds greater than a threshold speed within a specified distance interval. Parameter 1316 may indicate whether a sensing session performing WLAN-based RF sensing measurements during its duration is periodic, semi-persistent, or non-periodic.

[0123] Periodic sensing sessions can occur repeatedly at repetition intervals (e.g., once per second, once per minute, etc.). UE1304 (or another wireless device) can perform WLAN-based RF sensing measurements at repetition intervals. If the sensing session is periodic, parameter 1316 can indicate the repetition interval.

[0124] Semi-persistent sensing sessions can be activated and deactivated by sensing entity 1206. For example, sensing entity 1206 can send an activation instruction to UE 1304 (or another wireless device) to activate WLAN-based RF sensing, and sensing entity 1206 can send a deactivation instruction to UE 1304 (or another wireless device) to deactivate WLAN-based RF sensing. UE 1304 (or another wireless device) can perform WLAN-based RF sensing measurements at repetition intervals while WLAN-based RF sensing is activated. UE 1304 (or another wireless device) can continue performing WLAN-based RF sensing measurements until a deactivation instruction is received. If the sensing session is semi-persistent, parameter 1316 can indicate the repetition interval at which WLAN-based RF sensing measurements will be performed while WLAN-based RF sensing is activated.

[0125] A non-periodic sensing session (i.e., a "single" sensing session) can occur when UE 1304 receives an indication from sensing entity 1206. For example, UE 1304 may receive an indication from sensing entity 1206, and UE 1304 may perform one or more WLAN-based RF sensing measurements based on the received indication. UE 1304 may not perform additional WLAN-based RF sensing measurements until UE 1304 receives additional indications from sensing entity 1206. If the sensing session is non-periodic, parameter 1316 may indicate the number of WLAN-based RF sensing measurements to be performed upon receiving the indication.

[0126] The WLAN RF sensing configuration 1306 may include different parameters for different types of WLAN-based RF sensing measurements. For example, the WLAN RF sensing configuration 1306 may instruct the UE 1304 to perform angle measurements in a non-periodic sensing session and the UE 1304 to perform Doppler measurements in a periodic sensing session.

[0127] UE 1304 can perform WLAN-based RF sensing measurements based on WLAN RF sensing configuration 1306. For example, UE 1304 can perform WLAN-based RF sensing measurements based on data / signals transmitted by one or more of the first AP 1310 and / or the M AP 1312. UE 1304 can send WLAN-based RF sensing measurements to sensing entity 1206. UE 1304 and / or sensing entity 1206 can use WLAN-based RF sensing measurements to perform positioning.

[0128] In the second example 1318, at 1320, UE 1304 can discover APs that UE 1304 can communicate with. In one example, UE 1304 can discover a first AP 1310 and an Mth AP 1312. UE 1304 can send an indication of the discovered AP 1322 to sensing entity 1206. Sensing entity 1206 can select one or more APs from the discovered APs 1322. Sensing entity 1206 can generate a WLAN RF sensing configuration 1306 as described above, where the AP list 1308, measurement type 1314, and parameters 1316 are for the discovered APs selected by sensing entity 1206. In one example, sensing entity 1206 can select the first AP 1310 (instead of the Mth AP 1312). In another example, sensing entity 1206 can select both the first AP 1310 and the Mth AP 1312. Sensing entity 1206 can select one or more APs from the discovered APs 1322 based on various factors such as the number of thresholds, the characteristics of the discovered APs, etc.

[0129] Sensing entity 1206 may send WLAN RF sensing configuration 1306 to UE 1304. UE 1304 may then perform WLAN-based RF sensing measurements based on the WLAN RF sensing configuration 1306 as described above. UE 1304 may send WLAN-based RF sensing measurements to sensing entity 1206 as described above. UE 1304 and / or sensing entity 1206 may use the WLAN-based RF sensing measurements as described above to perform positioning.

[0130] In one aspect, the WLAN RF sensing configuration 1306 may instruct the UE 1304 to report independent WLAN sensing results (i.e., WLAN-based RF sensing measurements) for each AP. For example, the WLAN RF sensing configuration 1306 may instruct the UE 1304 to perform a first WLAN-based RF sensing measurement for the first AP 1310 and a second WLAN-based RF sensing measurement for the M AP 1312, and the UE 1304 will report the first WLAN-based RF sensing measurement and the second WLAN-based RF sensing measurement to the sensing entity 1206.

[0131] In one aspect, the WLAN RF sensing configuration 1306 may instruct the UE 1304 to combine WLAN sensing results across multiple APs (i.e., WLAN-based RF sensing measurements), and the UE 1304 will report the combined WLAN sensing results to the sensing entity 1206. For example, the WLAN RF sensing configuration 1306 may instruct the UE 1304 to perform a first WLAN-based RF sensing measurement on a first AP 1310 and a second WLAN-based RF sensing measurement on a second AP 1312, calculate a representative value for the first and second WLAN-based RF sensing measurements, and send the representative value to the sensing entity 1206. In one example, the representative value may be an average value or include an average value.

[0132] In one aspect, if a WLAN-based RF sensing measurement cannot be performed by the wireless device, or if the wireless device cannot obtain a WLAN-based RF sensing measurement, the wireless device can provide a "sensing error reason" indicating why the wireless device cannot perform / obtain a WLAN-based RF sensing measurement.

[0133] Figure 14 Figure 1400 illustrates an example aspect of configuring an AP for WLAN-based RF sensing. In a WLAN RF sensing session that performs WLAN-based RF sensing measurements, the AP can perform WLAN-based RF sensing measurements with or without the UE involved. The AP can then share the results (i.e., the WLAN-based RF sensing measurements performed by the AP or another AP) with the sensing entity.

[0134] In the first example 1402, sensing entity 1206 can obtain AP list 1404 (i.e., list of available APs), where AP list 1404 includes identifiers of APs in a specific geographic area. In one example, sensing entity 1206 can obtain AP list 1404 from another component / entity of core network 1208 (e.g., 5G core network). In one example, AP list 1404 may include identifiers of a first AP 1310 and an Mth AP 1312. Sensing entity 1206 can exchange sensing capabilities with APs. In one example, sensing entity 1206 can send a request to the first AP 1310, and the first AP 1310 can send WLAN RF sensing capabilities 1204 for the first AP 1310 and / or the Mth AP 1312 to sensing entity 1206. In another example, the first AP 1310 can send WLAN RF sensing capabilities 1204 to sensing entity 1206 without receiving a request.

[0135] Sensing entity 1206 can configure the first AP 1310 and / or the M AP 1312 for sensing sessions / measurements; that is, sensing entity 1206 can generate a WLAN RF sensing configuration 1306 (as described above) for the first AP 1310 and the M AP 1312 based on the WLAN RF sensing capability 1204. As discussed above, the WLAN RF sensing configuration 1306 can be periodic, semi-persistent, or non-periodic. In one aspect, the WLAN RF sensing configuration 1306 can specify or enable multi-AP sessions, where one or more APs are transmitters and one or more APs are receivers during the multi-AP session. As discussed above, the WLAN RF sensing configuration 1306 can indicate the type of measurement to be performed. The WLAN RF sensing configuration 1306 can also indicate parameters for the measurement and / or reporting.

[0136] Sensing entity 1206 can send WLAN RF sensing configuration 1306 to first AP 1310 and M AP 1312. First AP 1310 and M AP 1312 can perform WLAN-based RF sensing measurements based on the WLAN RF sensing configuration 1306. In one aspect, first AP 1310 and M AP 1312 can report sensing results (i.e., WLAN-based RF sensing measurements) to sensing entity 1206; that is, first AP 1310 and M AP 1312 can send sensing results to sensing entity 1206. In another aspect, M AP 1312 can send sensing results for M AP 1312 to first AP 1310, and first AP 1310 can send sensing results for both first AP 1310 and M AP 1312 to sensing entity 1206.

[0137] In the second example 1406, sensing entity 1206 can obtain the AP list 1404, as described above in the first example 1402. Sensing entity 1206 can exchange sensing capabilities with the APs, as described above. In one example, sensing entity 1206 can send a request to first AP 1310, and first AP 1310 can send WLAN RF sensing capabilities 1204 to sensing entity 1206 for first AP 1310 and / or M AP 1312. In another example, first AP 1310 can send WLAN RF sensing capabilities 1204 to sensing entity 1206 without receiving a request.

[0138] Sensing entity 1206 can configure the first AP 1310 for sensing sessions / measurements; that is, sensing entity 1206 can generate a WLAN RF sensing configuration 1306 (as described above) for the first AP 1310 and the M AP 1312 based on the WLAN RF sensing capability 1204. Sensing entity 1206 can send the WLAN RF sensing configuration 1306 to the first AP 1310. The first AP 1310 can configure the M AP 1312 based on the WLAN RF sensing configuration 1306; that is, the first AP 1310 can send the WLAN RF sensing configuration 1306 to the M AP 1312.

[0139] The first AP 1310 and the M AP 1312 can perform WLAN-based RF sensing measurements based on the WLAN RF sensing configuration 1306. In one aspect, the first AP 1310 and the M AP 1312 can report sensing results (i.e., WLAN-based RF sensing measurements) to the sensing entity 1206; that is, the first AP 1310 and the M AP 1312 can send sensing results to the sensing entity 1206. In another aspect, the M AP 1312 can send sensing results for the M AP 1312 to the first AP 1310, and the first AP 1310 can send sensing results for both the first AP 1310 and the M AP 1312 to the sensing entity 1206.

[0140] In the first example 1402 and the second example 1406, sensing entity 1206 may generate and send a subsequent WLAN RF sensing configuration after sending the WLAN RF sensing configuration 1306 or after receiving the sensing result, and the first AP 1310 and the M AP 1312 may perform and report subsequent WLAN-based RF sensing measurements based on the subsequent WLAN RF sensing configuration. In one example, sensing entity 1206 may generate the subsequent WLAN RF sensing configuration based on a sensing request.

[0141] Figure 15 Figure 1500 illustrates an example aspect of auxiliary data for WLAN-based RF sensing. In one example, sensing entity 1206 may provide auxiliary data 1502 to UE 1304, that is, sensing entity 1206 may send auxiliary data 1502 to UE 1304.

[0142] Auxiliary data 1502 may include an indication of the RF sensing channel 1504 (i.e., the WLAN RF sensing channel) used for the AP (e.g., the first AP 1310, the Mth AP 1312). Auxiliary data 1502 may include an indication of the supported measurement type 1506 (e.g., the first measurement type 1210, the Nth measurement type 1212) for the AP. Auxiliary data 1502 may include an indication of the AP's location 1508 (e.g., latitude, longitude, altitude). Auxiliary data 1502 may include an indication of the AP's location uncertainty 1510 (i.e., confidence level). Auxiliary data 1502 may include an indication of the AP's trust type 1512. In one example, the AP's trust type can be trusted or untrusted. A trusted AP may utilize a set of security parameters (e.g., encryption) and is therefore trusted, while an untrusted AP may not utilize a set of security parameters and is therefore untrusted. In one example, an untrusted AP may be a public AP. UE 1304 and / or AP can then perform and report WLAN-based RF sensing measurements based on auxiliary data 1502.

[0143] In one aspect, UE 1304 may send a request 1514 for auxiliary data 1502 to sensing entity 1206. Request 1514 may indicate a list of access points (APs) for which auxiliary data 1502 is requested (e.g., AP list 1404). Sensing entity 1206 may send auxiliary data 1502 based on request 1514. UE 1304 may receive a response to request 1514 as part of a message including auxiliary data 1502. If sensing entity 1206 cannot provide auxiliary data 1502, sensing entity 1206 may send an error reason to UE 1304, where the error reason indicates why sensing entity 1206 cannot provide auxiliary data 1502 to UE 1304.

[0144] Figure 16 Figure 1600 illustrates example communication between network entity 1602 and wireless device 1604. In one example, network entity 1602 may be or include a sensing entity (e.g., sensing entity 1206). In one example, wireless device 1604 may be wireless device 1202. In one example, wireless device 1604 may be or include a UE (e.g., UE 104, UE 1304, etc.) or an AP (e.g., first AP 1310, M AP 1312, etc.).

[0145] At 1606, network entity 1602 can obtain capability information for WLAN RF-based sensing. For example, in one aspect, at 1608, wireless device 1604 can send capability information to network entity 1602, and network entity 1602 can receive capability information. In another aspect, at 1610, network entity 1602 can send a request for capability information to wireless device 1604, and wireless device 1604 can send capability information to network entity 1602 at 1608 based on receiving the request.

[0146] At 1612, network entity 1602 can generate a configuration for WLAN RF-based sensing and send it to wireless device 1604. In one aspect, at 1614, wireless device 1604 can send a request to network entity 1602 for auxiliary data for WLAN RF-based sensing. At 1616, network entity can send auxiliary data to wireless device 1604 based on the request.

[0147] In one aspect, at 1618, network entity 1602 may send an AP list to wireless device 1604. At 1620, wireless device 1604 may configure the APs indicated in the AP list based on configuration. In another aspect, at 1622, wireless device 1604 may discover APs based on the configuration obtained at 1612 and / or auxiliary data received at 1616. At 1624, wireless device 1604 may send an indication of the discovered APs to network entity 1602. At 1626, the network entity may select a subset of APs from the discovered APs, wherein wireless device 1604 will perform WLAN-RF-based sensing with the AP subset. At 1628, network entity 1602 may send an indication of the AP subset to wireless device 1604.

[0148] At 1630, wireless device 1604 can perform a set of measurements for WLAN-based RF sensing based on configuration and / or auxiliary data. In some aspects, wireless device 1604 can perform the set of measurements for WLAN-based RF sensing based on an AP list received at 1618 or an indication of a subset of APs received at 1628. At 1632, wireless device 1604 can send an indication of the measurement set to network entity 1602. Network entity 1602 and / or wireless device 1604 can use the measurement set for positioning purposes.

[0149] Figure 17This is a flowchart 1700 of a wireless communication method. This method can be performed by network entities (e.g., core network 120, sensing entity 1206, core network 1208, network entity 1602, network entity 2160). In one example, this method (including the various aspects described in detail below) can be performed by a WLAN RF sensing component 198.

[0150] At point 1702, the network entity obtains WLAN-based radio frequency (RF) sensing capability information for at least one wireless device. For example, Figure 16 At 1606, it is shown that network entity 1602 can obtain capability information for WLAN RF-based sensing of wireless device 1604. In one example, the capability information may be or include WLAN RF sensing capability 1204. In another example, the capability information may include the above-mentioned combination. Figure 9 The third example 902 describes various aspects. In one example, 1702 can be performed by the WLAN RF sensing component 198.

[0151] At 1704, the network entity transmits at least one of configuration or auxiliary data for WLAN RF-based sensing to the at least one wireless device and based on the capability information, wherein the at least one of the configuration or auxiliary data indicates at least one of a set of RF sensing measurements or a set of RF sensing parameters for WLAN RF-based sensing. For example, Figure 16 At 1612, it is shown that network entity 1602 can send configuration for WLAN RF-based sensing to wireless device 1604. In another example, Figure 16 At 1616, it is shown that network entity 1602 can send auxiliary data for WLAN RF-based sensing to wireless device 1604. In one example, the configuration may be or include WLAN RF sensing configuration 1306. In another example, the auxiliary data may be or include auxiliary data 1502. In yet another example, the auxiliary data may include the combination of the above. Figure 10 The aspects described in the sixth example 1004. In one example, 1704 can be performed by the WLAN RF sensing component 198.

[0152] In one aspect, capability information may indicate that the at least one wireless device supports at least one of a range map measurement set, a Doppler map measurement set, or an angle map measurement set. For example, capability information obtained at 1606 may indicate that wireless device 1604 supports at least one of a range map measurement set, a Doppler map measurement set, or an angle map measurement set.

[0153] In some respects, network entities can send requests for capability information to wireless devices, where obtaining the capability information may include obtaining the capability information based on the request. For example, Figure 16 At 1610, it is shown that network entity 1602 can send a request for capability information to wireless device 1604.

[0154] In one aspect, at least one wireless device may include at least one UE, and a network entity may send a list of APs with which the at least one UE will perform WLAN RF-based sensing. For example, wireless device 1604 may be a UE, and Figure 16 At 1618, it is shown that network entity 1602 can send an AP list to wireless device 1604, whereby wireless device 1604 will perform WLAN RF-based sensing with the APs in the AP list. The foregoing aspect may correspond to... Figure 13 The first example is 1302.

[0155] In one aspect, the at least one wireless device may include at least one UE, and the network entity may receive a list of APs discovered by the at least one UE based on at least one of configuration or auxiliary data. For example, wireless device 1604 may be a UE, and Figure 16 At 1624, it is shown that network entity 1602 can receive instructions from wireless device 1604 regarding the discovered AP. The foregoing aspect may correspond to... Figure 13 The second example is 1318.

[0156] In one respect, network entities can select a subset of APs from the AP list based on WLAN RF-based sensing. For example, Figure 16 At point 1626, it is shown that network entity 1602 can select a subset of APs from the discovered APs. The aforementioned aspect can correspond to... Figure 13 The second example is 1318.

[0157] In one aspect, a network entity can send an indication to at least one UE to a subset of APs in an AP list, wherein the UE will perform WLAN RF-based sensing with the subset of APs. For example, Figure 16 At 1628, it is shown that network entity 1602 can send instructions to a subset of APs among the discovered APs. The foregoing aspect can correspond to... Figure 13 The second example is 1318.

[0158] In one aspect, the configuration may also indicate at least one type of RF sensing measurement in the RF sensing measurement set and reporting parameters for that at least one type of RF sensing measurement in the RF sensing measurement set. For example, the at least one type of RF sensing measurement may include the aspects described above in conjunction with measurement type 1314, and the reporting parameters may include the aspects described above in conjunction with parameter 1316. In one example, the reporting parameters may be quantization parameters.

[0159] In one aspect, the configuration may also indicate at least one condition or limitation on the set of RF sensing measurements for WLAN RF-based sensing. For example, parameter 1316 may indicate conditions and / or limitations on the set of RF sensing measurements for WLAN RF-based sensing.

[0160] In one aspect, the at least one wireless device may include at least one UE, and the network entity may receive from the at least one UE an indication of a set of RF sensing measurements for WLAN-based RF sensing, wherein the indication of the set of RF sensing measurements may include at least one of RF sensing measurements for each AP in the AP list or a combination of representative RF measurements indicating RF sensing measurements for each AP in the AP list. For example, wireless device 1604 may be a UE, and Figure 16 At 1632, it is shown that network entity 1602 can receive an indication of a set of RF sensing measurements for WLAN-based RF sensing. The indication of the set of RF sensing measurements may include at least one of RF sensing measurements for each AP in the AP list or a combination of representative RF measurements indicating RF sensing measurements for each AP in the AP list.

[0161] In one aspect, the at least one wireless device may include at least one AP, and wherein the configuration may instruct a set of RF sensing measurements for WLAN RF-based sensing to be performed in one of a periodic sensing session of the at least one AP, a semi-persistent sensing session of the at least one AP, or an aperiodic sensing session of the at least one AP. For example, wireless device 1604 may be an AP, and the configuration transmitted at 1612 may instruct a set of RF sensing measurements for WLAN RF-based sensing to be performed in one of a periodic sensing session of the at least one AP, a semi-persistent sensing session of the at least one AP, or an aperiodic sensing session of the at least one AP.

[0162] In one aspect, the at least one wireless device may include at least one receiving AP and at least one transmitting AP, and the configuration may indicate that the at least one receiving AP and the at least one transmitting AP will participate in a sensing session associated with a set of RF sensing measurements for WLAN-based RF sensing. For example, wireless device 1604 may be an AP, and the configuration transmitted at 1612 may indicate that at least one receiving AP and at least one transmitting AP will participate in a sensing session associated with a set of RF sensing measurements for WLAN-based RF sensing. In one example, at least one receiving AP may include a first AP 1310, and at least one transmitting AP may include a Mth AP 1312.

[0163] In one aspect, the at least one wireless device may include an access point (AP), and the configuration may instruct the AP to configure at least one additional AP for WLAN RF-based sensing based on that configuration. For example, wireless device 1604 may be an AP, and the configuration transmitted at 1612 may instruct the AP to configure at least one additional AP for WLAN RF-based sensing based on that configuration. The foregoing aspect may correspond to Figure 14 The second example is 1406.

[0164] In one aspect, the at least one wireless device may include at least one access point (AP), and the network entity may receive indications of a set of RF sensing measurements for WLAN-based RF sensing from the at least one AP, based on a configuration. For example, wireless device 1604 may be an AP, and Figure 16 At 1632, it is shown that network entity 1602 can receive instructions on the RF measurement set.

[0165] In one aspect, auxiliary data for WLAN RF-based sensing may include at least one of a list of WLAN RF sensing channels for the AP, at least one type of RF sensing measurement from a set of RF sensing measurements, a set of AP locations, a set of AP location uncertainties, or a trust type of the AP. For example, auxiliary data 1502 may include an indication of an RF sensing channel 1504 for the AP, an indication of a supported measurement type 1506 for the AP, an indication of a location 1508 (e.g., latitude, longitude, altitude), an indication of a location uncertainty 1510 for the AP, and / or an indication of a trust type 1512 for the AP.

[0166] In one aspect, the at least one wireless device may include at least one UE, and a network entity may receive a request for auxiliary data from the at least one UE, wherein the request indicates a list of APs for which it requests auxiliary data, and wherein sending auxiliary data for WLAN RF-based sensing may include sending auxiliary data for WLAN RF-based sensing based on the request. For example, wireless device 1604 may be a UE, and Figure 16 At 1614, it is shown that network entity 1602 can receive requests for auxiliary data. Furthermore, sending auxiliary data at 1616 can be based on receiving a request at 1614.

[0167] In one aspect, at least one wireless device may include at least one of a trusted AP or an untrusted AP. For example, wireless device 1604 may be or include a trusted AP or an untrusted AP.

[0168] Figure 18 This is a flowchart 1800 of a wireless communication method. The method can be performed by a wireless device (e.g., wireless device 1202, wireless device 1604). In one example, the wireless device can be or includes a UE (e.g., UE 104, UE 350, UE 404, UE 502, UE 602, UE 1304, device 1904). In one example, the wireless device can be or includes an AP (e.g., Wi-Fi™ AP 150, first AP 1310, M AP 1312). In one example, the method can be performed by a WLANRF sensing component 199.

[0169] At 1802, the wireless device transmits sensing capability information based on the wireless local area network (WLAN) radio frequency (RF) for the wireless device. For example, Figure 16 At 1608, it is shown that the wireless device 1604 can transmit capability information for WLAN RF-based sensing. In one example, the capability information may be or include WLAN RF sensing capability 1204. In another example, the capability information may include the above-mentioned combination. Figure 9 The third example 902 describes various aspects. In one example, 1802 can be performed by the WLANRF sensing component 199.

[0170] At 1804, the wireless device obtains at least one of configuration or auxiliary data for WLAN RF-based sensing based on capability information, wherein at least one of the configuration or auxiliary data indicates at least one of a set of RF sensing measurements or a set of RF sensing parameters for WLAN RF-based sensing. For example, Figure 16At 1612, it is shown that wireless device 1604 can receive configuration for WLAN RF-based sensing from network entity 1602. In another example, Figure 16 1616 illustrates that a wireless device 1604 can receive auxiliary data for WLAN RF-based sensing from a network entity 1602. In one example, the configuration may be or include a WLAN RF sensing configuration 1306. In another example, the auxiliary data may be or include auxiliary data 1502. In yet another example, the auxiliary data may include the above-described combinations. Figure 10 The aspects described in the sixth example 1004. In one example, 1804 can be performed by the WLAN RF sensing component 199.

[0171] In one aspect, capability information may indicate that the wireless device supports at least one of a range map measurement set, a Doppler map measurement set, or an angle map measurement set. For example, capability information transmitted at 1608 may indicate that the wireless device 1604 supports at least one of a range map measurement set, a Doppler map measurement set, or an angle map measurement set.

[0172] In one aspect, a wireless device can receive a request for capability information from a network entity, wherein sending the capability information may include sending the capability information based on the request. For example... Figure 16 At 1610, it is shown that wireless device 1604 can receive a request for capability information from network entity 1602.

[0173] In one aspect, the wireless device may include a UE, and the UE may receive from the network entity a list of APs with which it will perform WLAN RF-based sensing. For example, wireless device 1604 may be a UE, and Figure 16 At 1618, it is shown that wireless device 1604 can receive a list of access points (APs) from network entity 1602, wherein wireless device 1604 will perform WLAN RF-based sensing with APs in the AP list. The foregoing aspect may correspond to... Figure 13 The first example is 1302.

[0174] In one aspect, the wireless device may include a UE, and the UE may discover the set of APs based on at least one of configuration or auxiliary data. For example, wireless device 1604 may be a UE, and Figure 16 At 1622, it is shown that wireless device 1604 can discover APs based on configuration and / or auxiliary data.

[0175] In one respect, the UE can send a first indication to the set of APs for network entities and based on at least one of configuration or auxiliary data. For example, Figure 16At 1624, it is shown that wireless device 1604 can send an indication to network entity 1602 regarding a discovered AP. The foregoing aspect can correspond to... Figure 13 The second example is 1318.

[0176] In one aspect, the UE can receive a second indication from a network entity for a subset of APs in the AP set, whereby the UE will perform WLAN RF-based sensing with the AP subset. For example, Figure 16 At 1628, it is shown that wireless device 1604 can receive indications from network entity 1602 regarding a subset of APs among the discovered APs. The foregoing aspect may correspond to... Figure 13 The second example is 1318.

[0177] In one aspect, the configuration may also indicate at least one type of RF sensing measurement in the RF sensing measurement set and reporting parameters for that at least one type of RF sensing measurement in the RF sensing measurement set. For example, the at least one type of RF sensing measurement may include the aspects described above in conjunction with measurement type 1314, and the reporting parameters may include the aspects described above in conjunction with parameter 1316. In one example, the reporting parameters may be quantization parameters.

[0178] In one aspect, the configuration may also indicate at least one condition or limitation on the set of RF sensing measurements for WLAN RF-based sensing. For example, parameter 1316 may indicate conditions and / or limitations on the set of RF sensing measurements for WLAN RF-based sensing.

[0179] In one aspect, the wireless device may include a UE, and the UE may perform a set of RF sensing measurements for WLAN-based RF sensing based on at least one of configuration or auxiliary data. For example, wireless device 1604 may be a UE, and Figure 16 At 1630, it is shown that wireless device 1604 can perform a set of RF sensing measurements for WLAN-based RF sensing based on the configuration obtained at 1612 and / or auxiliary data obtained at 1616.

[0180] In one aspect, the UE may send an indication to a network entity of a set of RF sensing measurements performed for WLAN RF-based sensing, wherein the indication of the set of RF sensing measurements performed may include at least one of RF sensing measurements for each AP in the AP list or a combination of representative RF measurements indicating RF sensing measurements for each AP in the AP list. For example, the wireless device 1604 may be the UE, and Figure 16At 1632, it is shown that the wireless device 1604 can transmit an indication of a set of RF sensing measurements for WLAN-based RF sensing. The indication of the set of RF sensing measurements may include at least one of RF sensing measurements for each AP in the AP list or a combination of representative RF measurements indicating RF sensing measurements for each AP in the AP list.

[0181] In one aspect, the wireless device may include an access point (AP), and the configuration may instruct a set of RF sensing measurements for WLAN RF-based sensing to be performed in one of a periodic sensing session of the AP, a semi-persistent sensing session of the AP, or an aperiodic sensing session of the AP. For example, wireless device 1604 may be an AP, and the configuration obtained at 1612 may instruct a set of RF sensing measurements for WLAN RF-based sensing to be performed in one of a periodic sensing session of the at least one AP, a semi-persistent sensing session of the at least one AP, or an aperiodic sensing session of the at least one AP.

[0182] In one aspect, the wireless device may include a receiving AP or a transmitting AP, and the configuration may instruct the wireless device to participate in a sensing session associated with a set of RF sensing measurements for WLAN-based RF sensing, along with at least one additional AP. For example, wireless device 1604 may be an AP, and the configuration obtained at 1612 may instruct at least one receiving AP and at least one transmitting AP to participate in a sensing session associated with a set of RF sensing measurements for WLAN-based RF sensing. In one example, at least one receiving AP may include a first AP 1310, and at least one transmitting AP may include a third AP 1312.

[0183] In one aspect, the wireless device may include an access point (AP), and the configuration may instruct the AP to configure at least one additional AP for WLAN RF-based sensing based on that configuration, and the AP may configure the at least one additional AP for WLAN RF-based sensing based on that configuration. For example, wireless device 1604 may be an AP, and the configuration obtained at 1612 may instruct the AP to configure at least one additional AP for WLAN RF-based sensing based on that configuration. Furthermore, Figure 16 At 1620, it is shown that wireless device 1604 can configure the AP based on the configuration obtained at 1612. The foregoing aspects may correspond to... Figure 14 The second example is 1406.

[0184] In one aspect, the wireless device may include an access point (AP), and the AP may send indications to a set of RF sensing measurements for WLAN-based RF sensing, based on configuration and directed to network entities. For example, wireless device 1604 may be an AP, and... Figure 16 At 1632, it is shown that the wireless device 1604 can send instructions on the RF measurement set.

[0185] In one aspect, auxiliary data for WLAN RF-based sensing may include at least one of a list of WLAN RF sensing channels for the AP, at least one type of RF sensing measurement from a set of RF sensing measurements, a set of AP locations, a set of AP location uncertainties, or a trust type of the AP. For example, auxiliary data 1502 may include an indication of an RF sensing channel 1504 for the AP, an indication of a supported measurement type 1506 for the AP, an indication of a location 1508 (e.g., latitude, longitude, altitude), an indication of a location uncertainty 1510 for the AP, and / or an indication of a trust type 1512 for the AP.

[0186] In one aspect, the wireless device may include a UE, and the UE may send a request for auxiliary data to a network entity, wherein the request indicates a list of APs for which it requests auxiliary data, and wherein receiving auxiliary data for WLAN RF-based sensing may include receiving auxiliary data for WLAN RF-based sensing based on the request. For example, wireless device 1604 may be a UE, and Figure 16 At 1614, it is shown that the wireless device 1604 can send a request for auxiliary data. Furthermore, receiving auxiliary data at 1616 can be based on sending the request at 1614.

[0187] In one aspect, a wireless device may include a trusted AP or an untrusted AP. For example, wireless device 1604 may be or include a trusted AP or an untrusted AP.

[0188] Figure 19Figure 1900 illustrates an example of a hardware implementation for device 1904. Device 1904 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, device 1904 may include a cellular baseband processor 1924 (also referred to as a modem) coupled to one or more transceivers 1922 (e.g., cellular RF transceivers). Cellular baseband processor 1924 may include on-chip memory 1924'. In some aspects, device 1904 may also include one or more Subscriber Identity Module (SIM) cards 1920 and an application processor 1906 coupled to a Secure Digital Card (SD) card 1908 and a screen 1910. Application processor 1906 may include on-chip memory 1906'. In some aspects, device 1904 may also include a Bluetooth module 1912, a WLAN module 1914, an SPS module 1916 (e.g., a GNSS module), one or more sensor modules 1918 (e.g., a barometric pressure sensor / altimeter; motion sensors such as an inertial measurement unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-assisted detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 1926, a power source 1930, and / or a camera 1932. Bluetooth module 1912, WLAN module 1914, and SPS module 1916 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). Bluetooth module 1912, WLAN module 1914, and SPS module 1916 may include their own dedicated antennas and / or communicate using antenna 1980. Cellular baseband processor 1924 communicates with UE 104 and / or with RU associated with network entity 1902 via transceiver 1922 through one or more antennas 1980. Cellular baseband processor 1924 and application processor 1906 may each include computer-readable media / memory 1924', 1906' respectively. Additional memory module 1926 may also be considered computer-readable media / memory. Each computer-readable media / memory 1924', 1906', 1926 may be non-transitory. Cellular baseband processor 1924 and application processor 1906 are each responsible for general processing, including executing software stored on the computer-readable media / memory. When executed by cellular baseband processor 1924 / application processor 1906, the software causes cellular baseband processor 1924 / application processor 1906 to perform the various functions described above. The computer-readable media / memory may also be used to store data manipulated by cellular baseband processor 1924 / application processor 1906 during software execution.Cellular baseband processor 1924 / application processor 1906 may be a component of UE 350 and may include memory 360 and / or at least one of TX processor 368, RX processor 356, and controller / processor 359. In one configuration, device 1904 may be a processor chip (modem and / or application) and may only include cellular baseband processor 1924 and / or application processor 1906, and in another configuration, device 1904 may be the entire UE (see, for example). Figure 3 The UE 350 includes an additional module for device 1904.

[0189] As discussed above, the WLAN RF sensing component 199 can be configured to transmit capability information for WLAN RF-based sensing of a wireless device. The WLAN RF sensing component 199 can be configured to obtain, based on the capability information, at least one of configuration or auxiliary data for WLAN RF-based sensing of the wireless device, wherein the at least one of the configuration or auxiliary data indicates at least one of a set of RF sensing measurements or a set of RF sensing parameters for WLAN RF-based sensing. The WLAN RF sensing component 199 can be configured to receive a request for capability information from a network entity, wherein transmitting the capability information includes transmitting the capability information based on the request. The WLAN RF sensing component 199 can be configured to receive from a network entity a list of APs with which the UE will perform WLAN RF-based sensing. The WLAN RF sensing component 199 can be configured to discover an AP set based on at least one of the configuration or auxiliary data. The WLAN RF sensing component 199 can be configured to transmit a first indication of the AP set to a network entity and based on at least one of the configuration or auxiliary data. The WLAN RF sensing component 199 can be configured to receive a second indication from a network entity for a subset of APs in an AP set, wherein the UE will perform WLAN RF-based sensing with the AP subset. The WLAN RF sensing component 199 can be configured to perform a set of RF sensing measurements for the WLAN RF-based sensing based on at least one of configuration or auxiliary data. The WLAN RF sensing component 199 can be configured to send an indication to the network entity for the performed set of RF sensing measurements for the WLAN RF-based sensing, wherein the indication for the performed set of RF sensing measurements includes at least one of RF sensing measurements for each AP in the AP list or a representative RF measurement indicating a combination of RF sensing measurements for each AP in the AP list. The WLAN RF sensing component 199 can be configured to configure at least one additional AP for the WLAN RF-based sensing based on a configuration. The WLAN RF sensing component 199 can be configured to send an indication for the set of RF sensing measurements for the WLAN RF-based sensing to the network entity and based on the configuration. The WLAN RF sensing component 199 can be configured to send a request for auxiliary data to a network entity, wherein the request indicates a list of APs for which auxiliary data is requested, and wherein receiving auxiliary data for WLAN RF-based sensing includes receiving auxiliary data for WLAN RF-based sensing based on the request. The WLAN RF sensing component 199 may be located within a cellular baseband processor 1924, an application processor 1906, or both.The WLAN RF sensing component 199 may be one or more hardware components specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to perform the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. As shown, the device 1904 may include a variety of components configured for various functions. In one configuration, the device 1904, specifically the cellular baseband processor 1924 and / or application processor 1906, may include components for transmitting capability information for sensing based on the wireless local area network (WLAN) radio frequency (RF) of a wireless device. In one configuration, the device 1904, specifically the cellular baseband processor 1924 and / or application processor 1906, may include components for obtaining at least one of configuration or auxiliary data for sensing based on the capability information for the wireless device, wherein at least one of the configuration or auxiliary data indicates at least one of a set of RF sensing measurements or a set of RF sensing parameters for sensing based on the WLAN RF. In one configuration, device 1904, specifically cellular baseband processor 1924 and / or application processor 1906, may include components for receiving a request for capability information from a network entity, wherein sending the capability information includes sending the capability information based on the request. In one configuration, device 1904, specifically cellular baseband processor 1924 and / or application processor 1906 may include components for receiving from a network entity a list of access points (APs) with which the UE will perform WLAN RF-based sensing. In one configuration, device 1904, specifically cellular baseband processor 1924 and / or application processor 1906 may include components for discovering a set of access points (APs) based on at least one of configuration or auxiliary data. In one configuration, device 1904, specifically cellular baseband processor 1924 and / or application processor 1906 may include components for sending a first indication to a set of APs to a network entity and based on at least one of configuration or auxiliary data. In one configuration, device 1904, specifically cellular baseband processor 1924 and / or application processor 1906, may include components for receiving a second indication from a network entity for a subset of APs in an AP set, wherein the UE will perform WLAN RF-based sensing with the AP subset. In another configuration, device 1904, specifically cellular baseband processor 1924 and / or application processor 1906, may include components for performing a set of RF sensing measurements for WLAN RF-based sensing based on at least one of configuration or auxiliary data.In one configuration, device 1904, specifically cellular baseband processor 1924 and / or application processor 1906, may include components for transmitting to a network entity an indication of a set of RF sensing measurements performed for WLAN RF-based sensing, wherein the indication of the set of RF sensing measurements performed includes at least one of RF sensing measurements for each AP in the access point (AP) list or a representative RF measurement indicating a combination of RF sensing measurements for each AP in the AP list. In one configuration, device 1904, specifically cellular baseband processor 1924 and / or application processor 1906, may include components for configuring at least one additional AP for WLAN RF-based sensing based on a configuration. In one configuration, device 1904, specifically cellular baseband processor 1924 and / or application processor 1906, may include components for transmitting, to a network entity and based on a configuration, an indication of a set of RF sensing measurements for WLAN RF-based sensing. In one configuration, device 1904, specifically cellular baseband processor 1924 and / or application processor 1906, may include components for sending requests for auxiliary data to network entities, wherein the request indicates a list of access points (APs) for which auxiliary data is requested, and wherein receiving auxiliary data for WLAN RF-based sensing includes receiving auxiliary data for WLAN RF-based sensing based on the request. The component may be a WLAN RF sensing component 199 of device 1904 configured to perform the functions described therein. As described above, device 1904 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Therefore, in one configuration, the component may be a TX processor 368, an RX processor 356, and / or a controller / processor 359 configured to perform the functions described therein.

[0190] Figure 20Figure 2000 illustrates an example of a hardware implementation for network entity 2002. Network entity 2002 may be a BS, a component of a BS, or may implement BS functionality. Network entity 2002 may include at least one of CU 2010, DU 2030, or RU 2040. Network entity 2002 may include CU 2010; both CU 2010 and DU 2030; each of CU 2010, DU 2030, and RU 2040; DU 2030; both DU 2030 and RU 2040; or RU 2040. CU 2010 may include CU processor 2012. CU processor 2012 may include on-chip memory 2012'. In some aspects, CU 2010 may also include an additional memory module 2014 and a communication interface 2018. CU 2010 communicates with DU 2030 via a midhaul link such as an F1 interface. DU 2030 may include DU processor 2032. DU processor 2032 may include on-chip memory 2032'. In some aspects, DU 2030 may also include additional memory module 2034 and communication interface 2038. DU 2030 communicates with RU 2040 via a fronthaul link. RU 2040 may include RU processor 2042. RU processor 2042 may include on-chip memory 2042'. In some aspects, RU 2040 may also include additional memory module 2044, one or more transceivers 2046, antenna 2080, and communication interface 2048. RU 2040 communicates with UE 104. On-chip memories 2012', 2032', 2042' and additional memory modules 2014, 2034, 2044 may each be considered as computer-readable media / memory. Each computer-readable medium / memory may be non-transitory. Each of processors 2012, 2032, and 2042 is responsible for general processing, including executing software stored on computer-readable media / memory. When executed by the corresponding processor, the software causes the processor to perform the various functions described above. The computer-readable media / memory can also be used to store data manipulated by the processor while executing the software.

[0191] Figure 21Figure 2100 illustrates an example of a hardware implementation for network entity 2160. In one example, network entity 2160 may be within core network 120. Network entity 2160 may include network processor 2112. Network processor 2112 may include on-chip memory 2112'. In some aspects, network entity 2160 may also include additional memory module 2114. Network entity 2160 communicates with CU 2102 directly (e.g., via a backhaul link) or indirectly (e.g., via RIC) through network interface 2180. On-chip memory 2112' and additional memory module 2114 may each be considered as computer-readable media / memory. Each computer-readable media / memory may be non-transitory. Processor 2112 is responsible for general processing, including executing software stored on the computer-readable media / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described above. The computer-readable media / memory may also be used to store data manipulated by the processor when executing the software.

[0192] As discussed above, the WLAN RF sensing component 198 can be configured to obtain capability information for WLAN RF-based sensing for at least one wireless device. The WLAN RF sensing component 198 can be configured to send, to at least one wireless device and based on the capability information, at least one of the configuration or auxiliary data for WLAN RF-based sensing, wherein the configuration or auxiliary data indicates at least one of a set of RF sensing measurements or a set of RF sensing parameters for WLAN RF-based sensing. The WLAN RF sensing component 198 can be configured to send a request for capability information to the wireless device, wherein obtaining the capability information includes obtaining the capability information based on the request. The WLAN RF sensing component 198 can be configured to send to at least one UE a list of APs with which the at least one UE will perform WLAN RF-based sensing. The WLAN RF sensing component 198 can be configured to receive, from at least one UE, the list of APs discovered by the at least one UE and based on at least one of the configuration or auxiliary data. The WLAN RF sensing component 198 can be configured to select a subset of APs from the AP list based on WLAN RF-based sensing. The WLAN RF sensing component 198 can be configured to send an indication to at least one UE to a subset of APs in an AP list, wherein the UE will perform WLAN RF-based sensing with the AP subset. The WLAN RF sensing component 198 can be configured to receive from at least one UE an indication of a set of RF sensing measurements for WLAN RF-based sensing, wherein the indication of the set of RF sensing measurements includes at least one of RF sensing measurements for each AP in the AP list or a representative RF measurement indicating a combination of RF sensing measurements for each AP in the AP list. The WLAN RF sensing component 198 can be configured to receive the indication of the set of RF sensing measurements for WLAN RF-based sensing from at least one AP and based on a configuration. The WLAN RF sensing component 198 can be configured to receive a request for auxiliary data from at least one UE, wherein the request indicates a list of APs for which auxiliary data is requested, and wherein sending auxiliary data for WLAN RF-based sensing includes sending auxiliary data for WLAN RF-based sensing based on the request. The WLAN RF sensing component 198 may be located within processor 2112. The WLAN RF sensing component 198 may be one or more hardware components specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to perform the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. Network entity 2160 may include a variety of components configured for various functions.In one configuration, network entity 2160 may include components for obtaining capability information for WLAN-based radio frequency (RF) sensing for at least one wireless device. In one configuration, network entity 2160 may include components for transmitting, to at least one wireless device and based on the capability information, at least one of the configuration or auxiliary data for WLAN-based RF sensing, wherein the at least one of the configuration or auxiliary data indicates at least one of a set of RF sensing measurements or a set of RF sensing parameters for WLAN-based RF sensing. In one configuration, network entity 2160 may include components for sending a request for capability information to the wireless device, wherein obtaining the capability information includes obtaining the capability information based on the request. In one configuration, network entity 2160 may include components for transmitting to at least one UE a list of access points (APs) with which the at least one UE will perform WLAN-based RF sensing. In one configuration, network entity 2160 may include components for receiving, from at least one UE, a list of access points (APs) discovered by the at least one UE and based on at least one of the configuration or auxiliary data. In one configuration, network entity 2160 may include components for selecting a subset of APs in an AP list based on WLAN RF-based sensing. In another configuration, network entity 2160 may include components for transmitting an indication to at least one UE of a subset of APs in the AP list, wherein the UE will perform WLAN RF-based sensing with the AP subset. In yet another configuration, network entity 2160 may include components for receiving from at least one UE an indication of a set of RF sensing measurements for WLAN RF-based sensing, wherein the indication of the set of RF sensing measurements includes at least one of RF sensing measurements for each AP in the access point (AP) list or a representative RF measurement indicating a combination of RF sensing measurements for each AP in the AP list. In yet another configuration, network entity 2160 may include components for receiving, based on configuration, an indication of a set of RF sensing measurements for WLAN RF-based sensing from at least one AP. In one configuration, network entity 2160 may include a component for receiving a request for auxiliary data from at least one UE, wherein the request indicates a list of access points (APs) for which auxiliary data is requested, and wherein sending auxiliary data for WLAN RF-based sensing includes sending auxiliary data for WLAN RF-based sensing based on the request. The component may be a WLAN RF sensing component 198 of network entity 2160 configured to perform the functions described in the component.

[0193] Cellular communication systems can utilize various technologies for positioning to determine the location of a UE or another object. WLAN communication systems can utilize WLAN RF sensing for positioning purposes. However, the interaction between positioning in cellular and WLAN communication systems may not be well-defined regarding specific characteristics of WLAN RF sensing, leading to technical challenges. For example, a cellular communication system may not be configured to facilitate positioning in the absence of a UE.

[0194] This document describes various techniques related to WLAN-based RF sensing in cellular systems. In one example, a network entity obtains capability information for WLAN-based RF sensing of at least one wireless device. The network entity transmits, for the at least one wireless device and based on the capability information, at least one of configuration or auxiliary data for WLAN-based RF sensing, wherein the configuration or auxiliary data indicates at least one of a set of RF sensing measurements or a set of RF sensing parameters for WLAN-based RF sensing. By transmitting at least one of the configuration or auxiliary data for WLAN-based RF sensing, the network entity enables the at least one wireless device to perform enhanced positioning techniques. For example, compared to a wireless device that has not received configuration (based on capability information) or auxiliary data for WLAN-based RF sensing, the configuration and / or auxiliary data enables the at least one wireless device to determine the location of the wireless device or another object in a more accurate manner.

[0195] It should be understood that the specific order or hierarchy of the boxes in the disclosed process / flowcharts is merely an example of the exemplary method. It should be understood that the specific order or hierarchy of the boxes in the process / flowcharts may be rearranged based on design preferences. Furthermore, some boxes may be combined or omitted. The appended method claims present the elements of various boxes in a sample order, but are not limited to the given specific order or hierarchy.

[0196] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not limited to the aspects described herein but should be given the full scope consistent with the language of the claims. Unless specifically stated otherwise, references to elements in the singular form do not mean “one and only one” but rather “one or more.” Terms such as “if,” “when,” and “simultaneously” do not imply a direct temporal relationship or reaction. That is, these phrases, such as “when…”, do not imply an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply suggest that an action will occur if the condition is met, without requiring a specific or immediate time limit for the occurrence of the action. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or superior to other aspects. Unless otherwise specifically stated, the term “some” refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, which may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" can be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a collection of elements, where the number of elements is one or more. Therefore, for a set of X, X will include one or more elements. If the first device receives data from or sends data to the second device, data can be received / sent directly between the first and second devices, or indirectly between the first and second devices via a set of devices. A device configured to "output" data (such as transmission, signaling, or messaging) can, for example, transmit the data using a transceiver, or can transmit the data to the device that sent the data. A device configured to "receive" data (such as transmission, signaling, or messaging) can, for example, receive the data using a transceiver, or can obtain the data from the device that received the data. Information stored in memory includes instructions and / or data. All structural and functional equivalents of the elements throughout the various aspects described herein that are known to those skilled in the art or will later be known are expressly incorporated herein by reference and are covered by the claims.Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is explicitly stated in the claims. Terms such as “module,” “mechanism,” “element,” and “device” cannot replace the term “component.” Therefore, no claim element will be interpreted as a functional component unless the element is explicitly stated using the phrase “component for…”.

[0197] As used in this article, the phrase “based on” should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase “based on A” (where “A” can be information, conditions, factors, etc.) should be interpreted as “based on at least A”, unless specifically stated differently.

[0198] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

[0199] Aspect 1 is a method for wireless communication at a network entity, the method comprising: obtaining capability information for sensing based on wireless local area network (WLAN) radio frequency (RF) for at least one wireless device; and transmitting, for the at least one wireless device and based on the capability information, at least one of configuration or auxiliary data for the WLAN RF-based sensing, wherein the configuration or at least one of the auxiliary data indicates at least one of a set of RF sensing measurements or a set of RF sensing parameters for the WLAN RF-based sensing.

[0200] Aspect 2 is the method according to aspect 1, wherein the capability information indicates that the at least one wireless device supports at least one of a range map measurement set, a Doppler map measurement set, or an angle map measurement set.

[0201] Aspect 3 is a method according to any one of Aspects 1 to 2, the method further comprising: for the wireless device, sending a request for the capability information, wherein obtaining the capability information includes obtaining the capability information based on the request.

[0202] Aspect 4 is a method according to any one of Aspects 1 to 3, wherein the at least one wireless device includes at least one user equipment (UE), and the method further includes: for the at least one UE, transmitting a list of access points (APs) with which the at least one UE will perform the WLAN RF-based sensing.

[0203] Aspect 5 is a method according to any one of Aspects 1 to 3, wherein the at least one wireless device includes at least one user equipment (UE), the method further comprising: receiving, from the at least one UE and based on at least one of the configuration or the auxiliary data, a list of access points (APs) discovered by the at least one UE; selecting a subset of APs in the AP list based on the WLAN RF-based sensing; and, for the at least one UE, sending an indication to the subset of APs in the AP list, wherein the UE will perform the WLAN RF-based sensing with the subset of APs.

[0204] Aspect 6 is the method according to any one of aspects 1 to 5, wherein the configuration further indicates at least one type of RF sensing measurement in the RF sensing measurement set and reporting parameters for the at least one type of RF sensing measurement in the RF sensing measurement set.

[0205] Aspect 7 is the method according to any one of aspects 1 to 6, wherein the configuration further indicates at least one condition or limitation on the set of RF sensing measurements for the WLAN RF-based sensing.

[0206] Aspect 8 is a method according to any one of Aspects 1 to 7, wherein the at least one wireless device includes at least one user equipment (UE), the method further comprising: receiving from the at least one UE an indication of a set of RF sensing measurements for the WLAN-based RF sensing, wherein the indication of the set of RF sensing measurements includes at least one of RF sensing measurements for each AP in the access point (AP) list or a representative RF measurement indicating a combination of RF sensing measurements for each AP in the AP list.

[0207] Aspect 9 is a method according to any one of Aspects 1 to 3 and / or Aspects 6 to 7, wherein the at least one wireless device includes at least one access point (AP), and wherein the configuration indicates that the set of RF sensing measurements for the WLAN RF-based sensing will be performed in one of a periodic sensing session of the at least one AP, a semi-persistent sensing session of the at least one AP, or an aperiodic sensing session of the at least one AP.

[0208] Aspect 10 is a method according to any one of Aspects 1 to 3, 6 to 7 or 9, wherein the at least one wireless device includes at least one receiving access point (AP) and at least one transmitting AP, and wherein the configuration indicates that the at least one receiving AP and the at least one transmitting AP will participate in a sensing session associated with the RF sensing measurement set for the WLAN-based RF sensing.

[0209] Aspect 11 is a method according to any one of Aspects 1 to 3, 6 to 7 or 9 to 10, wherein the at least one wireless device includes an access point (AP), and wherein the configuration indicates that the AP will configure at least one additional AP for the WLAN RF-based sensing based on the configuration.

[0210] Aspect 12 is a method according to any one of aspects 1 to 3, 6 to 7 or 9 to 11, wherein the at least one wireless device includes at least one access point (AP), and the method further includes: receiving, from the at least one AP and based on the configuration, an indication of the set of RF sensing measurements for the WLAN-based RF sensing.

[0211] Aspect 13 is a method according to any one of aspects 1 to 12, wherein the auxiliary data for the WLAN RF-based sensing includes at least one of a list of WLAN RF sensing channels for an access point (AP), at least one type of RF sensing measurement in the set of RF sensing measurements, a set of locations of the AP, a set of location uncertainties of the AP, or a trust type of the AP.

[0212] Aspect 14 is a method according to any one of Aspects 1 to 8 or 13, wherein the at least one wireless device includes at least one user equipment (UE), the method further comprising: receiving a request for auxiliary data from the at least one UE, wherein the request indicates a list of access points (APs) for which the auxiliary data is requested, and wherein sending the auxiliary data for the WLAN RF-based sensing includes sending the auxiliary data for the WLAN RF-based sensing based on the request.

[0213] Aspect 15 is a method according to any one of aspects 1 to 3, 6 to 7 or 9 to 13, wherein the at least one wireless device includes at least one of a trusted access point (AP) or an untrusted AP.

[0214] Aspect 16 is an apparatus for wireless communication at a network entity, the apparatus including a memory and at least one processor coupled to the memory and based at least in part on information stored in the memory, the at least one processor being configured to perform a method according to any one of aspects 1 to 15.

[0215] Aspect 17 is an apparatus for wireless communication, the apparatus including components for performing the method according to any one of aspects 1 to 15.

[0216] Aspect 18 is an apparatus according to aspect 16 or 17, the apparatus further comprising at least one of a transceiver or an antenna coupled to the at least one processor, wherein the at least one processor is configured to transmit at least one of the configuration or the auxiliary data via the at least one of the transceiver or the antenna.

[0217] Aspect 19 is a computer-readable medium (e.g., a non-transitory computer-readable medium) including instructions that, when executed by at least one processor, cause the at least one processor to perform the method according to any one of aspects 1 to 15.

[0218] Aspect 20 is a method for wireless communication at a wireless device, the method comprising: transmitting capability information for sensing based on a wireless local area network (WLAN) radio frequency (RF) of the wireless device; and obtaining, based on the capability information, at least one of configuration or auxiliary data for the WLAN RF-based sensing of the wireless device, wherein the configuration or at least one of the auxiliary data indicates at least one of a set of RF sensing measurements or a set of RF sensing parameters for the WLAN RF-based sensing.

[0219] Aspect 21 is the method according to aspect 20, wherein the capability information indicates that the wireless device supports at least one of a range map measurement set, a Doppler map measurement set, or an angle map measurement set.

[0220] Aspect 22 is a method according to any one of aspects 20 to 21, the method further comprising: receiving a request for the capability information from a network entity, wherein sending the capability information includes sending the capability information based on the request.

[0221] Aspect 23 is a method according to any one of aspects 20 to 22, wherein the wireless device includes a user equipment (UE), and the method further includes: receiving from a network entity a list of access points (APs) with which the UE will perform the WLAN RF-based sensing.

[0222] Aspect 24 is a method according to any one of Aspects 20 to 22, wherein the wireless device includes a user equipment (UE), the method further comprising: discovering a set of access points (APs) based on at least one of the configuration or the auxiliary data; sending a first indication to the set of APs for a network entity and based on at least one of the configuration or the auxiliary data; and receiving from the network entity a second indication to a subset of APs in the set of APs, wherein the UE will perform the WLAN RF-based sensing with the subset of APs.

[0223] Aspect 25 is a method according to any one of aspects 20 to 24, wherein the configuration further indicates at least one type of RF sensing measurement in the RF sensing measurement set and reporting parameters for the at least one type of RF sensing measurement in the RF sensing measurement set.

[0224] Aspect 26 is the method according to any one of aspects 20 to 25, wherein the configuration further indicates at least one condition or limitation on the set of RF sensing measurements for the WLAN RF-based sensing.

[0225] Aspect 27 is a method according to any one of Aspects 20 to 26, wherein the wireless device includes a user equipment (UE), the method further comprising: performing a set of RF sensing measurements for the WLAN RF-based sensing based on at least one of the configuration or the auxiliary data; and sending an instruction to a network entity for the performed set of RF sensing measurements for the WLAN RF-based sensing, wherein the instruction for the performed set of RF sensing measurements includes at least one of RF sensing measurements for each AP in the access point (AP) list or a representative RF measurement indicating a combination of the RF sensing measurements for each AP in the AP list.

[0226] Aspect 28 is a method according to any one of aspects 20 to 22 or 25 to 26, wherein the wireless device includes an access point (AP), and wherein the configuration indicates that the set of RF sensing measurements for the WLAN RF-based sensing will be performed in one of a periodic sensing session of the AP, a semi-persistent sensing session of the AP, or an aperiodic sensing session of the AP.

[0227] Aspect 29 is a method according to any one of aspects 20 to 22, 25 to 26 or 28, wherein the wireless device includes a receiving access point (AP) or a transmitting AP, and wherein the configuration indicates that the wireless device will participate in a sensing session with at least one additional AP associated with the set of RF sensing measurements for the WLAN-based RF sensing.

[0228] Aspect 30 is a method according to any one of aspects 20 to 22, 25 to 26 or 28 to 29, wherein the wireless device includes an access point (AP), and wherein the configuration instructs the AP to configure at least one additional AP for the WLAN RF-based sensing based on the configuration, the method further comprising: configuring the at least one additional AP for the WLAN RF-based sensing based on the configuration.

[0229] Aspect 31 is a method according to any one of aspects 20 to 22, 25 to 26 or 28 to 30, wherein the wireless device includes an access point (AP), and the method further includes: sending an indication to the set of RF sensing measurements for the WLAN-based RF sensing for a network entity and based on the configuration.

[0230] Aspect 32 is a method according to any one of aspects 20 to 31, wherein the auxiliary data for the WLAN RF-based sensing includes at least one of a list of WLAN RF sensing channels for an access point (AP), at least one type of RF sensing measurement in the set of RF sensing measurements, a set of locations of the AP, a set of location uncertainties of the AP, or a trust type of the AP.

[0231] Aspect 33 is a method according to any one of Aspects 20 to 27 or 32, wherein the wireless device includes a user equipment (UE), the method further comprising: for a network entity, sending a request for the auxiliary data, wherein the request indicates a list of access points (APs) for which the auxiliary data is requested, and wherein receiving the auxiliary data for the WLAN RF-based sensing includes receiving the auxiliary data for the WLAN RF-based sensing based on the request.

[0232] Aspect 34 is a method according to any one of aspects 20 to 22, 25 to 26 or 28 to 32, wherein the wireless device includes a trusted access point (AP) or an untrusted AP.

[0233] Aspect 35 is an apparatus for wireless communication at a wireless device, the apparatus including a memory and at least one processor coupled to the memory and based at least in part on information stored in the memory, the at least one processor being configured to perform a method according to any one of aspects 20 to 34.

[0234] Aspect 36 is an apparatus for wireless communication, the apparatus including components for performing the method according to any one of aspects 20 to 34.

[0235] Aspect 37 is an apparatus according to aspect 35 or 36, the apparatus further comprising at least one of a transceiver or an antenna coupled to the at least one processor, wherein the at least one processor is configured to obtain at least one of the configuration or the auxiliary data via the at least one of the transceiver or the antenna.

[0236] Aspect 38 is a computer-readable medium (e.g., a non-transitory computer-readable medium) including instructions that, when executed by at least one processor, cause the at least one processor to perform the method according to any one of aspects 20 to 34.

Claims

1. An apparatus for performing wireless communication at a wireless device, the apparatus comprising: Memory; as well as At least one processor, coupled to the memory, and configured, based at least in part on information stored in the memory, to: Transmitting sensing capability information based on wireless local area network (WLAN) radio frequency (RF) for the wireless device; and Based on the capability information, at least one of the configuration or auxiliary data for the WLAN RF-based sensing of the wireless device is obtained, wherein the configuration or at least one of the auxiliary data indicates at least one of the RF sensing measurement set or the RF sensing parameter set for the WLAN RF-based sensing.

2. The apparatus of claim 1, wherein the capability information indicates that the wireless device supports at least one of a range map measurement set, a Doppler map measurement set, or an angle map measurement set.

3. The apparatus of claim 1, wherein the at least one processor is further configured to: A request for the capability information is received from a network entity, wherein, in order to send the capability information, the at least one processor is configured to send the capability information based on the request.

4. The apparatus of claim 1, wherein the wireless device includes user equipment (UE), and wherein the at least one processor is further configured to: The UE will receive a list of access points (APs) from the network entity with which it will perform the WLAN RF-based sensing.

5. The apparatus of claim 1, wherein the wireless device includes user equipment (UE), and wherein the at least one processor is further configured to: The set of access points (APs) is discovered based on at least one of the configuration or the auxiliary data. For network entities, a first indication to the set of APs is sent based on at least one of the configuration or the auxiliary data; and The UE receives a second instruction from the network entity for a subset of APs in the AP set, wherein the UE will perform the WLAN RF-based sensing with the subset of APs.

6. The apparatus of claim 1, wherein the configuration further indicates at least one type of RF sensing measurement in the RF sensing measurement set and reporting parameters for the at least one type of RF sensing measurement in the RF sensing measurement set.

7. The apparatus of claim 1, wherein the configuration further indicates at least one condition or limitation on the set of RF sensing measurements for the WLAN RF-based sensing.

8. The apparatus of claim 1, wherein the wireless device comprises user equipment (UE), and wherein the at least one processor is further configured to: The RF sensing measurement set for the WLAN RF-based sensing is performed based on at least one of the configuration or the auxiliary data; and For a network entity to send an instruction for the set of RF sensing measurements performed for the WLAN RF-based sensing, the instruction for the set of RF sensing measurements performed includes at least one of RF sensing measurements for each AP in the access point (AP) list or a representative RF measurement indicating a combination of the RF sensing measurements for each AP in the AP list.

9. The apparatus of claim 1, wherein the wireless device includes an access point (AP), and wherein the configuration indicates that the set of RF sensing measurements for the WLAN RF-based sensing will be performed in one of a periodic sensing session of the AP, a semi-persistent sensing session of the AP, or an aperiodic sensing session of the AP.

10. The apparatus of claim 1, wherein the wireless device includes a receiving access point (AP) or a transmitting AP, and wherein the configuration indicates that the wireless device will participate in a sensing session with at least one additional AP associated with the set of RF sensing measurements for the WLAN-based RF sensing.

11. The apparatus of claim 1, wherein the wireless device includes an access point (AP), and wherein the configuration instructs the AP to configure at least one additional AP for the WLAN RF-based sensing based on the configuration, and wherein the at least one processor is further configured to: Based on the configuration, the at least one additional AP is configured for the WLAN RF-based sensing.

12. The apparatus of claim 1, wherein the wireless device includes an access point (AP), and wherein the at least one processor is further configured to: For network entities and based on the configuration, send instructions for the RF sensing measurement set for the WLAN RF-based sensing.

13. The apparatus of claim 1, wherein the auxiliary data for the WLAN RF-based sensing includes at least one of a list of WLAN RF sensing channels for an access point (AP), at least one type of RF sensing measurement from the set of RF sensing measurements, a set of AP locations, a set of AP location uncertainties, or a trust type of the AP.

14. The apparatus of claim 1, wherein the wireless device comprises user equipment (UE), and wherein the at least one processor is further configured to: For a network entity, a request for the auxiliary data is sent, wherein the request indicates a list of access points (APs) for which the auxiliary data is requested, and wherein, in order to receive the auxiliary data for the WLAN RF-based sensing, the at least one processor is configured to receive the auxiliary data for the WLAN RF-based sensing based on the request.

15. The apparatus of claim 1, wherein the wireless device comprises a trusted access point (AP) or an untrusted AP.

16. The apparatus of claim 1, further comprising at least one of a transceiver or an antenna coupled to the at least one processor, wherein, in order to obtain the configuration or the auxiliary data, the at least one processor is configured to obtain the configuration or the auxiliary data via the at least one of the transceiver or the antenna.

17. A method for performing wireless communication at a wireless device, the method comprising: Transmit capability information for sensing based on wireless local area network (WLAN) radio frequency (RF) for the wireless device; as well as Based on the capability information, at least one of the configuration or auxiliary data for the WLAN RF-based sensing of the wireless device is obtained, wherein the configuration or at least one of the auxiliary data indicates at least one of the RF sensing measurement set or the RF sensing parameter set for the WLAN RF-based sensing.

18. An apparatus for wireless communication at a network entity, the apparatus comprising: Memory; as well as At least one processor, coupled to the memory, and configured, based at least in part on information stored in the memory, to: Obtain information on the sensing capabilities of at least one wireless device based on wireless local area network (WLAN) radio frequency (RF). as well as For the at least one wireless device, and based on the capability information, transmit at least one of the configuration or auxiliary data for the WLAN RF-based sensing, wherein the configuration or at least one of the auxiliary data indicates at least one of the RF sensing measurement set or the RF sensing parameter set for the WLAN RF-based sensing.

19. The apparatus of claim 18, wherein the capability information indicates that the at least one wireless device supports at least one of a range map measurement set, a Doppler map measurement set, or an angle map measurement set.

20. The apparatus of claim 18, further comprising at least one of a transceiver or an antenna coupled to the at least one processor, wherein the at least one processor is further configured to: For the at least one wireless device, a request for the capability information is sent via at least one of the transceiver or the antenna, wherein, in order to obtain the capability information, the at least one processor is configured to obtain the capability information based on the request.

Images