Point cloud reporting in cellular systems

Abstract

The first network entity may identify a point cloud that includes a plurality of points associated with the RF sensing. The first network entity may send an indication of the point cloud for a second network entity. The second network entity may perform a sensing operation based on the received point cloud. The point cloud may be based on one or more radar data cubes. Each point of the plurality of points may be associated with at least one of a range, a velocity, or one or more angles. The point cloud may be associated with a global coordinate system or a local coordinate system associated with the first network entity.

Description

[0001] Cross - Reference to Related Applications

[0002] This application claims the benefit of U.S. Patent Application Serial No. 18 / 054,512, entitled "POINT CLOUD REPORTING IN CELLULAR SYSTEMS", filed on November 10, 2022, which is hereby incorporated by reference in its entirety. Technical Field

[0003] This disclosure generally relates to communication systems and, more particularly, to point cloud reporting associated with radio frequency (RF) sensing in a wireless communication system. Background Art

[0004] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasting. A typical wireless communication system may employ a multiple access technology that is 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.

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at the urban, national, regional, and even global levels. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the ongoing evolution of mobile broadband promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., related to the Internet of Things (IoT)), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine - type communication (mMTC), and ultra - reliable low - latency communication (URLLC). Certain aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. Additionally, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the Invention

[0006] A simplified summary of one or more aspects is presented below in order to provide a basic understanding of these aspects. This summary is not an extensive overview of all contemplated aspects. This summary neither identifies key or critical 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 description that is presented later.

[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a first network node. The apparatus may identify a point cloud including a plurality of points associated with RF sensing. The apparatus may send an indication of the point cloud to a second network entity.

[0008] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a second network node. The apparatus may receive a point cloud including a plurality of points associated with RF sensing from a first network entity. The apparatus may perform a sensing operation based on the received point cloud.

[0009] To achieve the foregoing and related purposes, one or more aspects include the features described comprehensively below and particularly pointed out in the claims. The following description and the drawings set forth in detail some illustrative features of one or more aspects. However, these features indicate only some of the various ways in which the principles of the various aspects may be employed. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0011] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0012] Figure 2B is a diagram illustrating an example of a downlink (DL) channel within a subframe according to various aspects of the present disclosure.

[0013] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0014] Figure 2D is a diagram illustrating an example of an uplink (UL) channel within a subframe according to various aspects of the present disclosure.

[0015] Figure 3 is a diagram illustrating an example of a base station and a user equipment (UE) in an access network.

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

[0017] Figure 5 is a diagram illustrating an example of generating a sample radar data cube.

[0018] Figure 6 is a diagram illustrating a communication flow of a method of wireless communication.

[0019] Figure 7It is a flowchart of a method for wireless communication.

[0020] Figure 8 It is a flowchart of a method for wireless communication.

[0021] Figure 9 It is a flowchart of a method for wireless communication.

[0022] Figure 10 It is a flowchart of a method for wireless communication.

[0023] Figure 11 It is a diagram illustrating an example of a hardware implementation for exemplifying a device and / or a network entity.

[0024] Figure 12 It is a diagram illustrating an example of a hardware implementation for exemplifying a network entity.

[0025] Figure 13 It is a diagram illustrating an example of a hardware implementation for exemplifying a network entity. Detailed Description

[0026] Generating a point cloud in a wireless communication system and reporting the point cloud (e.g., by a reporting network entity that performs RF sensing) to a sensing entity can be an important operation in the context of RF sensing in a cellular wireless communication system.

[0027] In one or more aspects, a first network entity may identify a point cloud including a plurality of points associated with RF sensing. The first network entity may send an indication of the point cloud to a second network entity. The second network entity may perform sensing operations based on the received point cloud. Thus, reporting the point cloud from the reporting network entity to the sensing entity can be achieved.

[0028] The detailed description set forth below in connection with the accompanying drawings is a description of various configurations and does not represent the only configurations in which the concepts described herein may be practiced. For a thorough understanding of the various concepts, the detailed description includes specific details. However, the concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0029] Several aspects of a telecommunication system are presented with reference to various devices and methods. These devices and methods are described in the following detailed description and illustrated in the drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether an element is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

[0030] By way of example, an element, or any portion of an element, or any combination of elements can be implemented as a "processing system" that includes 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, systems on a chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described throughout this disclosure. One or more processors in the processing system can execute software. Software should be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof, regardless of whether it is referred to as software, firmware, middleware, microcode, hardware description language, or other terms.

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

[0032] While aspects, embodiments, and / or use cases are described herein by way of illustration of some examples, additional or different aspects, embodiments, and / or use cases may arise in many different arrangements and scenarios. The aspects, embodiments, and / or use cases described herein may be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, aspects, embodiments, and / or use cases may be implemented via integrated chips and other non-module-component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchase devices, medical devices, artificial intelligence (AI)-enabled devices, etc.). While some examples may or may not be specific to a use case or application, the examples described may have broad applicability. Aspects, embodiments, and / or use cases may range from chip-level or modular components to non-modular, non-chip-level embodiments and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems that incorporate one or more of the techniques herein. In some actual settings, devices incorporating the aspects and features described 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 includes 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 may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated components, or disaggregated components, end-user devices, etc., of various sizes, shapes, and configurations.

[0033] The deployment of a communication system such as a 5G NR system can be arranged in various ways with various components or constituent parts. In a 5G NR system or network, network nodes, network entities, mobility elements of the network, radio access network (RAN) nodes, core network nodes, network elements, or network equipment (such as a base station (BS)) or one or more units (or one or more components) performing base station functions may be implemented in an aggregated or disaggregated architecture. For example, a BS (such as a Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit-receive point (TRP), or cell, etc.) can be implemented as an aggregated base station (also referred to as a stand-alone BS or monolithic BS) or a disaggregated base station.

[0034] A centralized base station can be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A split base station can be configured to utilize a protocol stack physically or logically distributed between 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 aspects, a CU can be implemented within a RAN node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually distributed among one or more other RAN nodes. A DU can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0035] Base station operation or network design can consider the aggregated characteristics of base station functionality. For example, a split base station can be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN, such as a network configuration initiated by the O-RAN Alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Splitting can include distributing functions across two or more units at various physical locations, as well as virtually distributing the functions of at least one unit, which can achieve flexibility in network design. The various units of a split base station or a split RAN architecture can be configured for wired or wireless communication with at least one other unit.

[0036] Figure 1 FIG. 100 is a diagram illustrating an example of a wireless communication system and an access network. The illustrated wireless communication system includes a split base station architecture. The split base station architecture can include one or more CUs 110, which can communicate directly with the core network 120 via a backhaul link, or indirectly with the core network 120 through one or more split 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. The CU 110 can communicate with one or more DUs 130 via a respective midhaul link, such as an F1 interface. The DU 130 can communicate with one or more RUs 140 via a respective fronthaul link. The RU 140 can communicate with a respective UE 104 via one or more radio frequency (RF) access links. In some embodiments, the UE 104 can be served simultaneously by multiple RUs 140.

[0037] Each unit (i.e., CU 110, DU 130, RU 140, and the near RT RIC 125, non-RT RIC 115, and SMO framework 105) may include one or more interfaces or be coupled to one or more interfaces that are configured to receive or transmit signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interfaces of these units may be configured to communicate with one or more of the other units via the transmission medium. For example, the units may include a wired interface that is configured to receive signals or transmit signals to one or more of the other units via a wired transmission medium. Additionally, the units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) that is configured to receive and / or transmit signals to one or more of the other units via a wireless transmission medium.

[0038] In some aspects, the CU 110 may host one or more higher layer control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Service Data Adaptation Protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by the CU 110. The CU 110 may 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 embodiments, the CU 110 may be logically partitioned 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 may communicate bidirectionally with the CU-CP units via an interface (such as an E1 interface). As needed, the CU 110 may be implemented to communicate with the DU 130 for network control and signaling.

[0039] The DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 140. In some aspects, the DU 130 may host one or more of the Radio Link Control (RLC) layer, Medium 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.) at least in part according to a functional split (such as those defined by 3GPP). In some aspects, the DU 130 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 130 or with control functions hosted by the CU 110.

[0040] The lower layer functions can be implemented by one or more RUs 140. In some deployments, the RUs 140 controlled by the DU 130 can correspond to logical nodes that host 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, etc.) or both, at least in part based on function splitting (such as lower layer function splitting). In such an architecture, the RU 140 can be implemented to handle over-the-air (OTA) communication with one or more UEs 104. In some embodiments, the real-time and non-real-time aspects of the control plane and user plane communication with the RU 140 can be controlled by the corresponding DU 130. In some scenarios, this configuration enables the implementation of the DU 130 and CU 110 in a cloud-based RAN architecture (such as a vRAN architecture).

[0041] The SMO framework 105 can be configured to support the deployment and provisioning of RANs for both non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 105 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operation and maintenance interface (such as the O1 interface). For virtualized network elements, the SMO framework 105 can be configured to interact with a cloud computing platform (such as the 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 can include, but are not limited to, the CU 110, DU 130, RU 140, and the near RT RIC 125. In some embodiments, the SMO framework 105 can communicate with the hardware aspects of the 4G RAN (such as the Open eNB (O-eNB) 111) via the O1 interface. Additionally, in some embodiments, the SMO framework 105 can communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 105 can also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105.

[0042] The non-RT RIC 115 can be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / machine learning (ML) (AI / ML) workflows including model training and updating, or policy-based guidance of 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 the A1 interface). The near-RT RIC 125 can be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via the E2 interface) that connects one or more CUs 110, one or more DUs 130, or both, and the O-eNB to the near-RT RIC 125.

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

[0044] At least one of CU 110, DU 130, and RU 140 may be referred to as base station 102. Thus, 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 an access point to core network 120 for UE 104. Base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Small cells include femto cells, pico cells, and micro cells. A network including both small cells and macro cells may be referred to as a heterogeneous network. The heterogeneous network may also include a home evolved Node B (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include an uplink (UL) (also referred to as a reverse link) transmission from UE 104 to RU 140 and / or a downlink (DL) (also referred to as a forward link) transmission from RU 140 to UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may pass through one or more carriers. For each carrier allocated in carrier aggregation with a total 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., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.). These carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric for DL and UL (e.g., more or fewer carriers may be allocated for DL compared to UL). Component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carriers may be referred to as secondary cells (SCells).

[0045] Some UEs 104 may use device-to-device (D2D) communication link 158 to communicate with each other. D2D communication link 158 may use DL / UL wireless wide area network (WWAN) spectrum. D2D communication link 158 may 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 may be through various wireless D2D communication systems, such as, for example, Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0046] The wireless communication system may further include a Wi-Fi AP 150 that communicates with the UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, e.g., in the 5 GHz unlicensed spectrum, etc. When communicating in the unlicensed spectrum, the UE 104 / AP 150 may perform a Clear Channel Assessment (CCA) before communication to determine whether the channel is available.

[0047] The electromagnetic spectrum is generally subdivided into various categories, frequency bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating frequency bands have been identified as Frequency Range Designation FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). Although a part of FR1 is greater than 6 GHz, in various documents and articles, FR1 is generally referred to (interchangeably) as the "sub-6 GHz" band. Regarding FR2, a similar naming issue sometimes occurs, which is generally (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the Extremely High Frequency (EHF) band (30 GHz - 300 GHz) identified by the International Telecommunication Union (ITU) as the "millimeter wave" band.

[0048] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating frequency bands for these mid-band frequencies as Frequency Range Designation FR3 (7.125 GHz - 24.25 GHz). The frequency bands falling within FR3 may inherit the characteristics of FR1 and / or FR2, and thus can effectively extend the features of FR1 and / or FR2 to the mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating frequency bands have been identified as Frequency Range Designation FR2-2 (52.6 GHz - 71 GHz), FR4 (71 GHz - 114.25 GHz), and FR5 (114.25 GHz - 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0049] Considering the above aspects, unless otherwise specifically stated, if the term "sub-6 GHz" etc. is used herein, it may broadly represent frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise specifically stated, if the term "millimeter wave" etc. is used herein, it may broadly represent frequencies that can include mid-band frequencies, can be within FR2, FR4, FR2-2, and / or FR5, or can be within the EHF band.

[0050] 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 signal 182 to UE 104 in one or more transmission directions. UE 104 may receive the beamformed signal from base station 102 in one or more reception directions. UE 104 may also transmit beamformed signal 184 to base station 102 in one or more transmission directions. Base station 102 may receive the beamformed signal from UE 104 in one or more reception directions. Base station 102 / UE 104 may perform beam training to determine the optimal reception and transmission directions for each of base station 102 / UE 104. The transmission and reception directions of base station 102 may be the same or may not be the same. The transmission and reception directions of UE 104 may be the same or may not be the same.

[0051] Base station 102 may include and / or be referred to as gNB, Node B, eNB, access point, base station transceiver, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmission reception point (TRP), network node, network entity, network equipment, or some other suitable term. Base station 102 may be implemented as an integrated access and backhaul (IAB) node, relay node, sidelink node, a convergent (monolithic) base station with a baseband unit (BBU) (including CU and DU) and RU, or as a disaggregated base station including one or more of CU, DU, and / or RU. A set of base stations including disaggregated base stations and / or convergent base stations may be referred to as next generation (NG) RAN (NG-RAN).

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

[0053] Examples of the UE 104 include cellular phones, smart phones, Session Initiation Protocol (SIP) phones, laptop computers, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similar functional devices. Some of the UEs in the UE 104 may be referred to as IoT devices (e.g., parking meters, air pumps, toasters, vehicles, heart monitors, etc.). The 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, cell phone, user agent, mobile client, client, or some other suitable term. In some scenarios, the term UE may also apply to one or more companion devices, such as in a device constellation arrangement. One or more of these devices may access the network jointly and / or access the network individually.

[0054] Referring again to Figure 1 , in some aspects, the UE 104 (operating as a first network entity) may include a point cloud component 198 that may be configured to identify a point cloud including a plurality of points associated with RF sensing. The point cloud component 198 may be configured to send an indication of the point cloud to a second network entity. In some aspects, the base station 102 (operating as a first network entity) may include a point cloud component 199 that may be configured to identify a point cloud including a plurality of points associated with RF sensing. The point cloud component 199 may be configured to send an indication of the point cloud to a second network entity. Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0055] Figure 2A is a diagram 200 illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B is a diagram 230 illustrating an example of a DL channel within a 5G NR subframe. Figure 2C is a diagram 250 illustrating an example of a second subframe within a 5G NR frame structure. Figure 2DFIG. 280 is an illustration of an example of UL channels within a 5G NR subframe. The 5G NR frame structure can be frequency division duplexing (FDD) (wherein for a particular set of subcarriers (carrier system bandwidth), the subframes within that set of subcarriers are dedicated to DL or UL), or can be time division duplexing (TDD) (wherein for a particular set of subcarriers (carrier system bandwidth), the subframes within that set of subcarriers are dedicated to both DL and UL). In Figure 2A , Figure 2C the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (where most are DL), where D is DL, U is UL, and F is flexibly usable between DL / UL, and subframe 3 is configured with slot format 1 (where all are UL). Although subframes 3, 4 are shown as having slot formats 1, 28 respectively, any particular subframe can be configured with any of the various available slot formats 0 - 61. Slot formats 0, 1 are all - DL, all - UL respectively. The other slot formats 2 - 61 include a mixture of DL, UL, and flexible symbols. The UE is configured with the slot format by receiving a slot format indicator (SFI) (configured dynamically via DL control information (DCI) or semi - statically / statically via radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0056] Figures 2A to 2D The frame structure is illustrated, and aspects of the present disclosure can be applicable to other wireless communication technologies that may have different frame structures and / or different channels. One frame (10 ms) can be divided into 10 equal - sized subframes (1 ms). Each subframe can include one or more slots. A subframe can also include mini - slots, which can include 7, 4, or 2 symbols. Each slot can include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each slot can include 14 symbols, and for extended CP, each slot can include 12 symbols. The symbols on the DL can be cyclic prefix orthogonal frequency division multiplexing (CP - OFDM) symbols. The symbols on the UL can be CP - OFDM symbols (for high - throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT - s - OFDM) symbols (for power - limited scenarios; limited to single - stream transmission). The number of slots within a subframe is based on the CP and the parameter set. The parameter set defines the subcarrier spacing (SCS) (see Table 1). The symbol length / duration can be scaled with 1 / SCS.

[0057]

[0058] Table 1: Parameter Sets, SCS, and CP

[0059] For normal CP (14 symbols / slot), different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Thus, for normal CP and parameter set μ, there are 14 symbols / slot and 2 μ slots / subframe. The subcarrier spacing can be equal to 2 μ *15 kHz, where κ is parameter set 0 to 4. Thus, the subcarrier spacing for parameter set μ = 0 is 15 kHz, and the subcarrier spacing for parameter set μ = 4 is 240 kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figures 2A to 2D An example of normal CP with 14 symbols per slot and parameter set μ = 2 with 4 slots per subframe is provided. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency division multiplexed (see Figure 2B ). Each BWP can have a specific parameter set and CP (normal or extended).

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

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

[0062] Figure 2BIllustrates examples of various DL channels within a subframe of a frame. The Physical Downlink Control Channel (PDCCH) carries DCI within one or more Control Channel Elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six Resource Element Groups (REGs), and each REG including 12 consecutive Resource Elements (REs) within an OFDM symbol of an RB. The PDCCH within a BWP may be referred to as a Control Resource Set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., common search space, UE-specific search space) during a PDCCH monitoring occasion 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 within symbol 2 of a specific subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and the physical layer identity. The Secondary Synchronization Signal (SSS) may be within symbol 4 of a specific subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE may determine the Physical Cell Identifier (PCI). Based on the PCI, the UE may determine the location of the DM-RS. The Physical Broadcast Channel (PBCH) carrying the Master Information Block (MIB) may be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the System Frame Number (SFN) and the number of RBs in the system bandwidth. The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (such as System Information Blocks (SIBs)), and paging messages.

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

[0064] Figure 2DAn example of various UL channels within a subframe of a frame is illustrated. The PUCCH may be located at the position indicated in one configuration. The PUCCH carries uplink control information (UCI), such as a scheduling request, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and a hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0065] Figure 3 is a block diagram of a base station 310 in an access network communicating with a UE 350. In the DL, Internet Protocol (IP) packets may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a media access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcast of 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 transfer of upper layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and re-ordering 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 prioritization.

[0066] The transmit (TX) processor 316 and the 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) encoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to signal constellations based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The encoded and modulated symbols may then be split into parallel streams. Subsequently, each stream may be mapped to OFDM subcarriers, multiplexed with reference signals (e.g., pilots) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time-domain OFDM symbol stream. The OFDM stream is space precoded to generate multiple spatial streams. Channel estimates from the channel estimator 374 may be used to determine the encoding and modulation schemes, as well as for spatial processing. The channel estimates may be derived from reference signals transmitted by the UE 350 and / or channel state feedback. Then, each spatial stream may be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier with the corresponding spatial stream for transmission.

[0067] At the 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 the information to the receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 may perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they may be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then uses a fast Fourier transform (FFT) to convert the OFDM symbol stream from the time domain to the frequency domain. The frequency-domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, as well as the reference signals, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 310. These soft decisions may be based on the channel estimates calculated by the channel estimator 358. Then, the soft decisions are decoded and deinterleaved to recover the data and control signals originally transmitted by the base station 310 on the physical channel. The data and control signals are then provided to the controller / processor 359, which implements layer 3 and layer 2 functionality.

[0068] 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 between the transport channel and the logical channel, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 359 is also responsible for error detection using the ACK and / or NACK protocols to support HARQ operations.

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

[0070] Channel estimates derived by the channel estimator 358 based on reference signals or feedback sent by the base station 310 may be used by the TX processor 368 to select appropriate decoding and modulation schemes and facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via a separate transmitter 354Tx. Each transmitter 354Tx modulates an RF carrier with the corresponding spatial stream for transmission.

[0071] UL transmission is processed at the base station 310 in a manner similar to that described in connection with the receiver function at the 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 the information to the RX processor 370.

[0072] 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 the UL, the controller / processor 375 provides demultiplexing between the transport channel and the logical channel, packet reassembly, decryption, header decompression, control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using the ACK and / or NACK protocols to support HARQ operations.

[0073] At least one of TX processor 368, RX processor 356, and controller / processor 359 may be configured to perform aspects in conjunction with Figure 1 point cloud component 198.

[0074] At least one of TX processor 316, RX processor 370, and controller / processor 375 may be configured to perform aspects in conjunction with Figure 1 point cloud component 199.

[0075] Figure 4 FIG. 400 is a diagram illustrating an example of UE positioning based on reference signal measurements. UE 404 may transmit UL-SRS 412 at time T SRS_TX and receive a downlink positioning reference signal (PRS) (DL-PRS) 410 at time T PRS_RX . TRP 406 may receive UL-SRS 412 at time T SRS_RX and transmit DL-PRS 410 at time T PRS_TX . UE 404 may receive DL-PRS 410 before transmitting UL-SRS 412, or may transmit UL-SRS 412 before receiving DL-PRS 410. In both cases, a positioning server (e.g., location server 168) or UE 404 may determine the RTT 414 based on ||T SRS_RX – T PRS_TX | – |T SRS_TX – T PRS_RX ||. Thus, multi-RTT positioning may utilize the UE Rx-Tx time difference measurement of the downlink signals received from multiple TRPs 402, 406 and measured by UE 404 (i.e., |T SRS_TX – T PRS_RX |) and the DL-PRS reference signal received power (RSRP) (DL-PRS-RSRP), as well as the measured TRP Rx-Tx time difference measurement of the uplink signals transmitted from UE 404 at multiple TRPs 402, 406 (i.e., |T SRS_RX – T PRS_TX |) and UL-SRS-RSRP. UE 404 uses the assistance data received from the positioning server to measure the UE Rx-Tx time difference measurement (and the DL-PRS-RSRP of the received signal), and TRPs 402, 406 use the assistance data received from the positioning server to measure the gNB Rx-Tx time difference measurement (and the UL-SRS-RSRP of the received signal). These measurements may be used at the positioning server or 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.

[0076] DL-AoD positioning can utilize the measured DL-PRS-RSRP of the downlink signals received at the UE 404 from multiple TRPs 402, 406. The UE 404 uses the assistance data received from the positioning server to measure the DL-PRS-RSRP of the received signals, and the resulting measurements, together with the azimuth of departure (A-AoD), zenith angle of departure (Z-AoD), and other configuration information, are used to position the UE 404 relative to the neighboring TRPs 402, 406.

[0077] DL-TDOA positioning can utilize the DL reference signal time difference (RSTD) (and DL-PRS-RSRP) of the downlink signals received at the UE 404 from multiple TRPs 402, 406. The UE 404 uses the assistance data received from the positioning server to measure the DL RSTD (and DL-PRS-RSRP) of the received signals, and the resulting measurements, together with other configuration information, are used to position the UE 404 relative to the neighboring TRPs 402, 406.

[0078] UL-TDOA positioning can utilize the UL relative time of arrival (RTOA) (and UL-SRS-RSRP) of the uplink signals transmitted from the UE 404 at multiple TRPs 402, 406. The TRPs 402, 406 use the assistance data received from the positioning server to measure the UL-RTOA (and UL-SRS-RSRP) of the received signals, and the resulting measurements, together with other configuration information, are used to estimate the location of the UE 404.

[0079] UL-AoA positioning can utilize the measured azimuth of arrival (A-AoA) and zenith angle of arrival (Z-AoA) of the uplink signals transmitted from the UE 404 at multiple TRPs 402, 406. The TRPs 402, 406 use the assistance data received from the positioning server to measure the A-AoA and Z-AoA of the received signals, and the resulting measurements, together with other configuration information, are used to estimate the location of the UE 404.

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

[0081] Figure 5FIG. 500 illustrates an example radar data cube generation. FIG. 510 illustrates an example RF sensing. At a reporting network entity, an RF signal transmitted via a transmit RF chain 514 may be reflected by one or more objects 518 (e.g., 4 objects 518) in the environment. As shown, two of the objects 518 may be at a range R from the node performing the sensing 1 and may be moving at velocities V 1 and V 2 respectively. Additionally, two other of the objects 518 may be at a range R 2 (greater than R 1 ) and may be moving at velocities V 3 and V4 respectively. A receive RF chain 516 may receive the reflected RF signals. Based on the received reflected RF signals, a radar processor 512 (e.g., an OFDM radar processor) (e.g., at the node performing the sensing) may generate one or more radar data cubes. In some configurations, as shown in FIG. 550, a radar data cube may be generated by applying a two-dimensional (2D) FFT operation to the baseband in-phase and quadrature (IQ) samples of the received OFDM samples, where the first dimension of the FFT may span time (also referred to as slow-time FFT or row / Doppler FFT) and the second FFT may be along the frequency (e.g., sub-carrier) domain (also referred to as fast-time FFT or column / range FFT). As shown, after the row / Doppler FFT, the Doppler values corresponding to the object velocities may be highlighted (i.e., these columns may have higher values than other values). Additionally, after the column / range FFT, the actual ranges may be located. Thus, the rows corresponding to R 1 and R 2 may have higher values. Thus, when the column / range FFT is performed after the row / Doppler FFT, 4 entries in the matrix having higher values (compared to other entries) corresponding to the 4 objects 518 may be highlighted. Other ways of generating the radar data cube may be used in additional configurations. For example, super-resolution algorithms (e.g., Multiple Signal Classification (MUSIC), Estimation of Signal Parameters via Rotational Invariance Techniques (ESPRIT), etc.) may be used instead of the FFT operation to obtain more accurate results (which may come at the cost of higher computational complexity).

[0082] RF sensing may become a major use case in future cellular wireless communication networks. In the case of RF sensing, RF signals may be used to obtain information about the characteristics of the environment and the objects within the environment (e.g., shape, size, velocity, location, distance, or relative motion between objects, etc.). Dedicated frequency-domain and time-domain resources may be used for the sensing operation. Generally, a device may perform the sensing operation by using RF beam scanning of an area. For example, a device may scan an area by sweeping across multiple beams.

[0083] RF sensing can also be applied to different usage scenarios. Examples of usage scenarios for RF sensing can include joint communication sensing, environmental scanning, object detection, weather monitoring, etc.

[0084] In some configurations, a wireless communication system (e.g., a 5G NR system or another wireless communication system) can support RF sensing and the collection of sensing measurement data. The wireless communication system can support the reporting of sensing measurement data for processing. Additionally, the wireless communication system can support the processing of sensing measurement data, including correlating (associating) the sensing measurement data with other auxiliary information (e.g., location information). Further, the wireless communication system can support (e.g., via the core network) the export (exposure) of sensing measurement data and sensing results to third-party applications (e.g., authorized third-party applications).

[0085] In some configurations, for sensing purposes, a UE can be configured to report time-domain and / or frequency-domain samples of the received waveform to the network. In some configurations, a UE can be configured to report a radar data cube (e.g., a full matrix) to the network. Specifically, a point cloud can be generated based on post-processing of the sensing data or radar data. A point cloud can be a collection of n-dimensional points, where each dimension can correspond to a feature / characteristic of an object (e.g., range, Doppler, angle, etc.). A point cloud can be considered a refined output of one or more radar data cubes. Thus, multiple radar data cubes can be combined to generate a point cloud. Additionally, additional processing operations can be performed to obtain the point cloud. The additional processing operations can include, for example, constant false alarm rate (CFAR) detection, range / Doppler / angle ambiguity resolution, averaging of multiple frames or captures, etc.

[0086] In some configurations, a point cloud can be an input to AI / ML-based algorithms for applications such as semantic segmentation, detection, or object classification (e.g., for automotive usage scenarios). Thus, generating a point cloud in a wireless communication system and reporting the point cloud to a sensing entity can be an important operation in the context of RF sensing based on a cellular wireless communication system.

[0087] In one or more aspects, a network entity (e.g., a UE, a base station, or a TRP) can report one or more point clouds to a sensing entity in a wireless communication system. The point cloud can be constructed to facilitate reporting. Additionally, the configuration of the point cloud reporting can be specified (e.g., by the sensing entity). Here, the sensing entity can also be referred to as a sensing management entity. In a further configuration, a network entity (e.g., a UE, a base station, or a TRP) can provide an indication of the node capabilities of the network entity related to the reporting / signaling of the point cloud.

[0088] In one or more configurations, a point cloud information element (IE) (e.g., an IE named "PointCloudIE") can be defined for point cloud reporting. In one configuration, the point cloud IE can include point cloud elements (e.g., a parameter named "PointCloudElement") that can be defined in a coordinate system. Specifically, the point cloud element parameter can include fields such as range, velocity, angle (e.g., azimuth and / or elevation angle).

[0089] For the range, a mapping from integers to range values can be specified and used. For example, for a fixed step-size reporting granularity, a step size (ΔR) can be specified and defined. Thus, the maximum reportable range can be ΔR * maximum integer (e.g., ΔR * range - Range). In different examples, different mapping rules (i.e., for mapping from integers to range values) can be defined based on intervals. Similarly, for velocity, a mapping from integers to velocity values can be specified and used. For example, a step size (Δv) of the velocity can be specified and defined. The step size of the velocity can determine the maximum reportable velocity.

[0090] In addition, for the angle, a reporting step size can be specified. For example, if the step size (scale factor) is 1 degree, the azimuth angle can be reported at a granularity of 1 degree in the range between 0 degrees and 359 degrees, and the elevation angle can be reported at a granularity of 1 degree in the range between 0 degrees and 180 degrees. In another example, the reporting of the angle can be at a finer granularity. For example, a step size (scale factor) of 0.1 degree can be used. Thus, for example, the angle can be reported at a granularity of 0.1 degree in the range between 0 degrees and 0.9 degrees, without reporting the angle as 0 degree or 1 degree.

[0091] In different configurations, the point cloud can be reported relative to a local coordinate system or a global coordinate system. If a local coordinate system is used, the point cloud report can include an indication (report) of the center of the local coordinate system. The center of the local coordinate system can be indicated directly (i.e., using an absolute position to indicate) or by specifying an offset relative to a known position (i.e., a reference). For example, for a UE reporting the point cloud, the reference can be the position of the UE. In another example, for a TRP reporting the point cloud, the reference can be the antenna reference point (ARP) of the TRP. In additional configurations, if a global coordinate system is used, the coordinate system of the point cloud can be reported / indicated together with the points in the point cloud. In addition, a framework for translation between the local coordinate system and the global coordinate system can be used (e.g., a framework associated with the "lcs - GCS - TranslationParameter" parameter).

[0092] In one or more configurations, before configuring a network entity (e.g., a UE, a base station, or a TRP) for point cloud reporting, a sensing entity may want to know whether the network entity supports point cloud reporting. Thus, in some configurations, a network entity (e.g., a UE, a base station, or a TRP) may indicate its point cloud reporting capability to the sensing entity. The indication of the point cloud reporting capability may be provided as part of an indication of sensing-related capabilities.

[0093] The indication of the point cloud reporting capability may include an indication of different capabilities at different granularity levels. In one configuration, the indication of the point cloud reporting capability may include an indication of attributes (e.g., range, velocity, angle, etc.) (e.g., all attributes or a subset of attributes) that can be reported in an IE (i.e., an IE parameter). In one configuration, the indication of the point cloud reporting capability may include an indication of the supported coordinate systems (e.g., a local coordinate system and / or a global coordinate system). In one configuration, the indication of the point cloud reporting capability may include an indication of the reporting format (e.g., the reporting device / network entity may not be able to track the entire point cloud and may only report the most recent (new) cloud points at each reporting occasion). In one configuration, the indication of the point cloud reporting capability may include an indication of the frequencies supported by the reporting network entity and / or the antenna configuration for each frequency. In one configuration, the indication of the point cloud reporting capability may include an indication of the beam pattern configuration.

[0094] In one or more configurations, a sensing entity may configure a reporting network entity / node (e.g., a UE, a base station, or a TRP) for point cloud reporting (e.g., by sending a configuration of the point cloud reporting). The configuration of the point cloud reporting may include one or more of a sensing RS configuration, a reporting frequency configuration, a reporting format configuration, etc.

[0095] For the sensing RS configuration, the resources (e.g., time-frequency resources) of the sensing RS to be used for generating the point cloud may be configured. In one configuration, the resources may be specifically configured for generating the point cloud. In another configuration, based on the sensing RS configuration, existing resources (e.g., already configured positioning RSs or another already configured sensing RS, etc.) may be used for generating the point cloud. If existing resources are to be used for generating the point cloud, the sensing RS configuration may indicate the resources associated with the already configured sensing RS that are to be used for generating the point cloud. For example, a TRP may use the same positioning RS for both positioning and RF sensing. Additionally, in one configuration, within the sensing RS configuration, for Doppler estimation, the number of instances (e.g., across time) to be used for Doppler estimation may be indicated.

[0096] In some configurations, the network entity / node that sends the sensing RS may be different from the network entity / node that receives the sensing RS (i.e., bistatic sensing). If bistatic sensing is used, the sensing RS configuration may include auxiliary data for the receiving network entity / node. For example, the auxiliary data may include sensing RS resource configuration, an indication of the location of the sending network entity / node, an indication of the speed of the sending network entity / node, etc. In one configuration, the point cloud report may include an indication of whether the report is generated based on monostatic sensing (i.e., RF sensing, where the sending network entity / node and the receiving network entity / node may be the same network entity / node) or bistatic sensing.

[0097] In one example configuration, for the reporting frequency configuration, the configuration of the point cloud report may indicate that a point cloud report can be generated / requested / provided after every nth transmission of the sensing RS (the sensing RS can be specified in the above sensing RS configuration).

[0098] For the report format configuration, in one configuration, at each reporting occasion, the reporting network entity may report the point cloud independently of the previously reported point cloud. In another configuration, differential reporting may be used. Specifically, a full point cloud may be reported at the first reporting occasion. Thereafter, at subsequent reporting occasions, the modifications / differences with respect to the point cloud (map) reported at the previous occasion may be indicated in the point cloud report (e.g., newly emerged points may be indicated in the report, and points that have disappeared / are no longer present may also be indicated in the report). To enable differential reporting, each point may be associated with an index / identifier (ID) such that existing, disappearing, and newly emerged points in the point cloud can be tracked. In one example, the maximum number of supported point indices / IDs may be specified. In one example, the index / ID of a point that has disappeared may be reused for a newly emerged point at a later occasion.

[0099] In one or more configurations, the configuration of the point cloud report can specify whether speed compensation is to be used. Based on this configuration, speed compensation can be enabled or disabled during point cloud reporting. For example, if the sender network entity / node or the receiver network entity / node is moving, speed compensation can be enabled and applied. For example, if a vehicle UE (reporting network entity / node) is moving, static objects around the vehicle UE can appear to have a non-zero speed because the output of RF sensing at the vehicle UE can detect the object speed relative to the vehicle UE. For example, a tree in the environment can appear as a detected object with a specific non-zero speed. In this case, the sensing entity can request that the reporting vehicle UE apply speed compensation to the generated point cloud to correct for the movement of the vehicle UE. Since the vehicle UE knows its own speed and direction, the vehicle UE can compensate for its own movement so that detected stationary objects (e.g., the tree) have a zero speed in the point cloud. In another example, the vehicle UE may not directly apply speed compensation. Instead, the vehicle UE can include information about its movement (speed, orientation, etc.) in the point cloud report. Then, the sensing entity can apply the compensation to the received point cloud report based on the information about the movement of the vehicle UE.

[0100] In one or more configurations, the configuration of the point cloud report can specify one or more reporting conditions. For example, the bounds of the reported cloud points can be specified. The bounds can relate to a minimum range, a maximum range, or both a minimum range and a maximum range. In one example, based on the configured bounds, the reporting network entity can report only the points in the point cloud that are within a range that exceeds the configured (minimum) value. In other words, the reporting network entity can exclude the points that fall below the range in the point cloud report. In different configurations, other similar bounds can be configured / specified for one or more of speed, angle (azimuth and / or elevation), etc.

[0101] In one or more configurations, the configuration of the point cloud report can specify the coordinate system representation (e.g., polar coordinate representation or Cartesian coordinate representation). For example, by default, the range / angle (r,θ) representation can be the polar coordinate representation of the cloud point positions in the reference coordinate system. In some configurations, the sensing entity can select an alternative Cartesian coordinate representation. Thus, the sensing entity can specify the Cartesian coordinate representation in the configuration of the point cloud report. If the Cartesian coordinate representation is requested, the reporting network entity can map (transform) the default polar coordinate representation (e.g., the (r,θ) representation) to a 2D or three-dimensional (3D) Cartesian coordinate representation (e.g., the (x coordinate, y coordinate) representation) (e.g., depending on the configuration and / or the capabilities of the reporting network entity / node), and can use the (2D or 3D) Cartesian coordinate representation (e.g., the (x coordinate, y coordinate) representation) in the report instead of the polar coordinate representation (i.e., the (range r, angle θ) representation).

[0102] In one or more configurations, if the orientation and / or location of a reporting network entity (e.g., a UE, a TRP, or a base station) is known or ascertainable, the reporting network entity may provide the orientation and / or location information to a sensing entity as part of a sensing report. The orientation and / or location information regarding the reporting network entity may be used (e.g., by the sensing entity) to fuse the point cloud at a later stage.

[0103] Additionally, in one configuration, the reporting network entity (e.g., a UE, a TRP, or a base station) may report the point cloud separately for each frequency layer used in sensing. In another configuration, the reporting network entity (e.g., a UE, a TRP, or a base station) may report the point cloud across multiple frequencies used in sensing (e.g., after performing fusion across multiple frequency layers corresponding to the multiple frequencies).

[0104] Figure 6 FIG. 600 is a diagram of a communication flow of a method of wireless communication. A first network entity 602 may implement aspects of the UE 104 / 350 or the base station 102 / 310. A second network entity 604 may implement aspects of the sensing entity. Thus, the first network entity 602 may include at least one of a UE, a TRP, or a base station. The second network entity 604 may include a sensing entity in a wireless communication system.

[0105] At 606, the first network entity 602 may send a second indication of one or more point cloud reporting capabilities associated with the first network entity 602 to the second network entity 604. The one or more point cloud reporting capabilities may correspond to one or more of the reported parameters, coordinate systems, reporting formats, one or more frequencies, at least one antenna configuration, or beam pattern configuration.

[0106] At 608, the second network entity 604 may send a configuration of the point cloud report to the first network entity 602. The configuration of the point cloud report may correspond to one or more of a sensing reference signal configuration, a reporting frequency, or a reporting format. The reporting format may correspond to a full report or a differential report.

[0107] In one or more configurations, the configuration of the point cloud report may also correspond to a velocity compensation mode, at least one reporting condition, or a representation system.

[0108] At 610, the first network entity 602 may identify a point cloud including a plurality of points associated with RF sensing.

[0109] In one configuration, the point cloud may be based on one or more radar data cubes.

[0110] In one or more configurations, each point in the plurality of points may be associated with at least one of a range, a velocity, or one or more angles.

[0111] In one or more configurations, the point cloud may be associated with a global coordinate system or a local coordinate system associated with a first network entity 602.

[0112] In one configuration, the configuration of the point cloud report may include at least one reporting condition. Thus, in order to identify the point cloud at 610, at 610a, the first network entity 602 may exclude at least one point from the point cloud based on the at least one reporting condition.

[0113] In one or more configurations, the point cloud may be associated with a single frequency layer or multiple frequency layers.

[0114] At 612, the first network entity 602 may send an indication of the point cloud to the second network entity 604.

[0115] At 614, the second network entity 604 may receive a second indication of the position or orientation of the first network entity 602 from the first network entity 602.

[0116] At 616, the second network entity 604 may perform a sensing operation based on the received point cloud.

[0117] Figure 7 is a flowchart 700 of a method of wireless communication. The method may be performed by a first network entity (e.g., UE 104 / 350; device 1104; base station 102 / 310; network entity 1102; first network entity 602). At 702, the first network entity may identify a point cloud including a plurality of points associated with RF sensing. For example, 702 may be performed by Figure 11 component 198 in Figure 12 or Figure 6 component 199 in. Referring to

[0118] At 704, the first network entity may send an indication of the point cloud to the second network entity. For example, 704 may be performed by Figure 11 component 198 in Figure 12 or Figure 6 component 199 in. Referring to

[0119] Figure 8Flowchart 800 of a method for wireless communication. The method may be performed by a first network entity (e.g., UE 104 / 350; device 1104; base station 102 / 310; network entity 1102; first network entity 602). At 806, the first network entity may identify a point cloud including a plurality of points associated with RF sensing. For example, 806 may be performed by component 198 in Figure 11 or component 199 in Figure 12 . Referring to Figure 6 , at 610, the first network entity 602 may identify a point cloud including a plurality of points associated with RF sensing.

[0120] At 810, the first network entity may send an indication of the point cloud to a second network entity. For example, 810 may be performed by component 198 in Figure 11 or component 199 in Figure 12 . Referring to Figure 6 , at 612, the first network entity 602 may send an indication of the point cloud to a second network entity 604.

[0121] In one configuration, the point cloud may be based on one or more radar data cubes.

[0122] In one configuration, each of the plurality of points is associated with at least one of range, velocity, or one or more angles.

[0123] In one configuration, referring to Figure 6 , the point cloud may be associated with a global coordinate system or a local coordinate system associated with the first network entity 602.

[0124] In one configuration, at 802, the first network entity may send a second indication of one or more point cloud reporting capabilities associated with the first network entity to a second network entity. The one or more point cloud reporting capabilities may correspond to one or more of the reported parameters, coordinate systems, reporting formats, one or more frequencies, at least one antenna configuration, or beam pattern configuration. For example, 802 may be performed by component 198 in Figure 11 or component 199 in Figure 12 . Referring to Figure 6 , at 606, the first network entity 602 may send a second indication of one or more point cloud reporting capabilities associated with the first network entity 602 to a second network entity 604.

[0125] In one configuration, at 804, the first network entity may receive a configuration of a point cloud report from the second network entity. The configuration of the point cloud report may correspond to one or more of a sensing reference signal configuration, a reporting frequency, or a reporting format. The reporting format may correspond to a full report or a differential report. For example, 804 may be performed by Figure 11by component 198 in Figure 12 or component 199 in Figure 6 Referring to Figure 6 , at 608, a first network entity 602 may receive a configuration of a point cloud report from a second network entity 604.

[0126] In one configuration, referring to Figure 6 Figure 6 , the configuration of the point cloud report at 608 may also correspond to a velocity compensation mode, at least one reporting condition, or one or more of a representation system.

[0127] In one configuration, referring to Figure 6 Figure 6 , the configuration of the point cloud report at 608 may also at least correspond to at least one reporting condition. To identify the point cloud, at 806a, the first network entity may exclude at least one point from the point cloud based on the at least one reporting condition. For example, 806a may be performed by Figure 11 component 198 in Figure 12 or component 199 in Figure 6 Referring to Figure 6 , at 610a, the first network entity 602 may exclude at least one point from the point cloud based on the at least one reporting condition.

[0128] In one configuration, at 808, the first network entity may send a second indication of the position or orientation of the first network entity to the second network entity. For example, 808 may be performed by Figure 11 component 198 in Figure 12 or component 199 in Figure 6 Referring to Figure 6 , at 614, the first network entity 602 may send a second indication of the position or orientation of the first network entity 602 to the second network entity 604.

[0129] In one configuration, the point cloud may be associated with a single frequency layer or multiple frequency layers.

[0130] In one configuration, referring to Figure 6 Figure 6 , the first network entity 602 may include at least one of a UE, a TRP, or a base station. The second network entity 604 may include a sensing entity in a wireless communication system.

[0131] Figure 9 is a flowchart 900 of a method of wireless communication. The method may be performed by a second network entity (e.g., a sensing entity; the second network entity 604; the network entity 1360). At 902, the second network entity may receive a point cloud including a plurality of points associated with RF sensing from a first network entity. For example, 902 may be performed by Figure 13 component 1399 in Figure 6 Referring to Figure 6 , at 612, the second network entity 604 may receive a point cloud including a plurality of points associated with RF sensing from the first network entity 602.

[0132] At 904, a second network entity may perform a sensing operation based on the received point cloud. For example, 904 may be performed by Figure 13 component 1399 in. Refer to Figure 6 , at 616, the second network entity 604 may perform a sensing operation based on the received point cloud.

[0133] Figure 10 is a flowchart 1000 of a method of wireless communication. The method may be performed by a second network entity (e.g., a sensing entity; the second network entity 604; the network entity 1360). At 1006, the second network entity may receive a point cloud including a plurality of points associated with RF sensing from a first network entity. For example, 1006 may be performed by Figure 13 component 1399 in. Refer to Figure 6 , at 612, the second network entity 604 may receive a point cloud including a plurality of points associated with RF sensing from the first network entity 602.

[0134] At 1010, the second network entity may perform a sensing operation based on the received point cloud. For example, 1010 may be performed by Figure 13 component 1399 in. Refer to Figure 6 , at 616, the second network entity 604 may perform a sensing operation based on the received point cloud.

[0135] In one configuration, the point cloud may be based on one or more radar data cubes.

[0136] In one configuration, each point in the plurality of points may be associated with at least one of range, velocity, or one or more angles.

[0137] In one configuration, refer to Figure 6 , the point cloud may be associated with a global coordinate system or a local coordinate system associated with the first network entity 602.

[0138] In one configuration, at 1002, the second network entity may receive a second indication of one or more point cloud reporting capabilities associated with the first network entity from the first network entity. The one or more point cloud reporting capabilities may correspond to one or more of the reported parameters, coordinate systems, reporting formats, one or more frequencies, at least one antenna configuration, or beam pattern configuration. For example, 1002 may be performed by Figure 13 component 1399 in. Refer to Figure 6 , at 606, the second network entity 604 may receive a second indication of one or more point cloud reporting capabilities associated with the first network entity 602 from the first network entity 602.

[0139] In one configuration, at 1004, a second network entity may send a configuration of a point cloud report to a first network entity. The configuration of the point cloud report may correspond to one or more of a sensing reference signal configuration, a reporting frequency, or a reporting format. The reporting format may correspond to a full report or a differential report. For example, 1004 may be performed by Figure 13 component 1399 therein. Refer to Figure 6 , at 608, the second network entity 604 may send a configuration of a point cloud report to the first network entity 602.

[0140] In one configuration, refer to Figure 6 , the configuration of the point cloud report at 1004 may also correspond to one or more of a velocity compensation mode, at least one reporting condition, or a representation system.

[0141] In one configuration, at 1008, the second network entity may receive a second indication of the position or orientation of the first network entity from the first network entity. For example, 1008 may be performed by Figure 13 component 1399 therein. Refer to Figure 6 , at 614, the second network entity 604 may receive a second indication of the position or orientation of the first network entity 602 from the first network entity 602.

[0142] In one configuration, the point cloud may be associated with a single frequency layer or multiple frequency layers.

[0143] In one configuration, refer to Figure 6 , the first network entity 602 may include at least one of a UE, a TRP, or a base station. The second network entity 604 may include a sensing entity in a wireless communication system.

[0144] Figure 11FIG. 1100 is a diagram illustrating an example of a hardware implementation for an apparatus 1104. The apparatus 1104 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1104 may include a cellular baseband processor 1124 (also referred to as a modem) coupled to one or more transceivers 1122 (e.g., cellular RF transceivers). The cellular baseband processor 1124 may include on-chip memory 1124'. In some aspects, the apparatus 1104 may also include one or more subscriber identity module (SIM) cards 1120 and an application processor 1106 coupled to a secure digital (SD) card 1108 and a screen 1110. The application processor 1106 may include on-chip memory 1106'. In some aspects, the apparatus 1104 may also include a Bluetooth module 1112, a WLAN module 1114, an SPS module 1116 (e.g., GNSS module), one or more sensor modules 1118 (e.g., barometric pressure sensor / altimeter; motion sensors such as an inertial measurement unit (IMU), gyroscope, and / or accelerometer; light detection and ranging (LIDAR), radio assisted detection and ranging (RADAR), sound navigation and ranging (SONAR), magnetometer, audio, and / or other technologies for positioning), additional memory modules 1126, a power source 1130, and / or a camera 1132. The Bluetooth module 1112, the WLAN module 1114, and the SPS module 1116 may include on-chip transceivers (TRX) (or in some cases, only a receiver (RX)). The Bluetooth module 1112, the WLAN module 1114, and the SPS module 1116 may include their own dedicated antennas and / or communicate using the antenna 1180. The cellular baseband processor 1124 communicates with the UE 104 and / or with the RU associated with the network entity 1102 via the transceiver 1122 through one or more antennas 1180. The cellular baseband processor 1124 and the application processor 1106 may each separately include computer-readable media / memory 1124', 1106'. The additional memory module 1126 may also be considered computer-readable media / memory. Each computer-readable media / memory 1124', 1106', 1126 may be non-transitory. The cellular baseband processor 1124 and the application processor 1106 are each responsible for general processing, including executing software stored on the computer-readable media / memory. The software, when executed by the cellular baseband processor 1124 / application processor 1106, causes the cellular baseband processor 1124 / application processor 1106 to perform the various functions described above. The computer-readable media / memory may also be used to store data manipulated by the cellular baseband processor 1124 / application processor 1106 when executing the software.The cellular baseband processor 1124 / application processor 1106 can be a component of the UE 350 and can include the memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the device 1104 can be a processor chip (modem and / or application) and include only the cellular baseband processor 1124 and / or the application processor 1106, and in another configuration, the device 1104 can be the entire UE (e.g., see Figure 3 of 350) and include additional modules of the device 1104.

[0145] As discussed above, the component 198 is configured to identify a point cloud that includes a plurality of points associated with RF sensing. The component 198 is configured to send an indication of the point cloud to a second network entity. The component 198 can be within the cellular baseband processor 1124, the application processor 1106, or both the cellular baseband processor 1124 and the application processor 1106. The component 198 can be one or more hardware components that are specifically configured to perform the stated processes / algorithms, implemented by one or more processors configured to perform the stated processes / algorithms, stored in a computer-readable medium for implementation by one or more processors, or some combination of the above. As shown, the device 1104 can include a variety of components configured for various functions. In one configuration, the device 1104 (and specifically the cellular baseband processor 1124 and / or the application processor 1106) includes components for identifying a point cloud that includes a plurality of points associated with RF sensing. The device 1104 (and specifically, the cellular baseband processor 1124 and / or the application processor 1106) includes components for sending an indication of the point cloud to a second network entity.

[0146] In one configuration, the point cloud may be based on one or more radar data cubes. In one configuration, each of the plurality of points may be associated with a range, a velocity, or at least one of one or more angles. In one configuration, the point cloud may be associated with a global coordinate system or a local coordinate system associated with a first network entity. In one configuration, apparatus 1104 (and specifically, cellular baseband processor 1124 and / or application processor 1106) includes means for sending, to a second network entity, a second indication of one or more point cloud reporting capabilities associated with the first network entity. The one or more point cloud reporting capabilities may correspond to one or more of the reported parameters, coordinate systems, reporting formats, one or more frequencies, at least one antenna configuration, or beam pattern configuration. In one configuration, apparatus 1104 (and specifically, cellular baseband processor 1124 and / or application processor 1106) includes means for receiving, from the second network entity, a configuration of the point cloud report. The configuration of the point cloud report may correspond to one or more of a sensing reference signal configuration, a reporting frequency, or a reporting format. The reporting format may correspond to a full report or a differential report. In one configuration, the configuration of the point cloud report may further correspond to a velocity compensation mode, at least one reporting condition, or a representation system. In one configuration, the configuration of the point cloud report may further at least correspond to at least one reporting condition. The means for identifying the point cloud may be further configured to exclude at least one point from the point cloud based on the at least one reporting condition. In one configuration, apparatus 1104 (and specifically, cellular baseband processor 1124 and / or application processor 1106) includes means for sending, to the second network entity, a second indication of the location or orientation of the first network entity. In one configuration, the point cloud may be associated with a single frequency layer or multiple frequency layers. In one configuration, the first network entity may include at least one of a UE, a TRP, or a base station. The second network entity may include a sensing entity in a wireless communication system.

[0147] The means may be component 198 of apparatus 1104 configured to perform the functions recited by the means. As described above, apparatus 1104 may include TX processor 368, RX processor 356, and controller / processor 359. Thus, in one configuration, the means may be TX processor 368, RX processor 356, and / or controller / processor 359 configured to perform the functions recited by the means.

[0148] Figure 12FIG. 1200 is a diagram illustrating an example of a hardware implementation for network entity 1202. Network entity 1202 can be a BS, a component of a BS, or can implement BS functionality. Network entity 1202 can include at least one of CU 1210, DU 1230, or RU 1240. For example, depending on the layer functionality handled by component 199, network entity 1202 can include CU 1210; both CU 1210 and DU 1230; each of CU 1210, DU 1230, and RU 1240; DU 1230; both DU 1230 and RU 1240; or RU 1240. CU 1210 can include CU processor 1212. CU processor 1212 can include on-chip memory 1212'. In some aspects, CU 1210 can also include additional memory modules 1214 and communication interface 1218. CU 1210 communicates with DU 1230 via an intermediate link (such as the F1 interface). DU 1230 can include DU processor 1232. DU processor 1232 can include on-chip memory 1232'. In some aspects, DU 1230 can also include additional memory modules 1234 and communication interface 1238. DU 1230 communicates with RU 1240 via a fronthaul link. RU 1240 can include RU processor 1242. RU processor 1242 can include on-chip memory 1242'. In some aspects, RU 1240 can also include additional memory modules 1244, one or more transceivers 1246, antenna 1280, and communication interface 1248. RU 1240 communicates with UE 104. On-chip memories 1212', 1232', 1242' and additional memory modules 1214, 1234, 1244 can each be considered computer-readable media / memories. Each computer-readable media / memory can be non-transitory. Each of processors 1212, 1232, 1242 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 can also be used to store data manipulated by the processor when executing the software.

[0149] As discussed above, component 199 is configured to identify a point cloud that includes a plurality of points associated with RF sensing. Component 199 is configured to send an indication of the point cloud to a second network entity. Component 199 can be within one or more processors of one or more of CU 1210, DU 1230, and RU 1240. Component 199 can be one or more hardware components that are specifically configured to perform the stated processes / algorithms, implemented by one or more processors configured to perform the stated processes / algorithms, stored in a computer-readable medium for implementation by one or more processors, or some combination of the above. Network entity 1202 can include a variety of components configured for various functions. In one configuration, network entity 1202 includes components for identifying a point cloud that includes a plurality of points associated with RF sensing. Network entity 1202 includes components for sending an indication of the point cloud to a second network entity.

[0150] In one configuration, the point cloud can be based on one or more radar data cubes. In one configuration, each of the plurality of points can be associated with at least one of range, velocity, or one or more angles. In one configuration, the point cloud can be associated with a global coordinate system or a local coordinate system associated with the first network entity. In one configuration, network entity 1202 includes components for sending a second indication of one or more point cloud reporting capabilities associated with the first network entity to a second network entity. The one or more point cloud reporting capabilities can correspond to one or more of the reported parameters, coordinate systems, reporting formats, one or more frequencies, at least one antenna configuration, or beam pattern configuration. In one configuration, network entity 1202 includes components for receiving a configuration of a point cloud report from a second network entity. The configuration of the point cloud report can correspond to one or more of a sensing reference signal configuration, reporting frequency, or reporting format. The reporting format can correspond to a full report or a differential report. In one configuration, the configuration of the point cloud report can also correspond to a velocity compensation mode, at least one reporting condition, or a representation system. In one configuration, the configuration of the point cloud report can also at least correspond to at least one reporting condition. The components for identifying the point cloud can be further configured to exclude at least one point from the point cloud based on the at least one reporting condition. In one configuration, network entity 1202 includes components for sending a second indication of the location or orientation of the first network entity to a second network entity. In one configuration, the point cloud can be associated with a single frequency layer or multiple frequency layers. In one configuration, the first network entity can include at least one of a UE, a TRP, or a base station. The second network entity can include a sensing entity in a wireless communication system.

[0151] A component can be a component 199 of network entity 1202 configured to perform the functions described by the component. As described above, network entity 1202 can include a TX processor 316, an RX processor 370, and a controller / processor 375. Thus, in one configuration, the component can be the TX processor 316, the RX processor 370, and / or the controller / processor 375 configured to perform the functions described by the component.

[0152] Figure 13 FIG. 1300 is a diagram illustrating an example of a hardware implementation for network entity 1360. In one example, network entity 1360 can be within core network 120. Network entity 1360 can include a network processor 1312. Network processor 1312 can include on-chip memory 1312'. In some aspects, network entity 1360 can also include additional memory modules 1314. Network entity 1360 communicates with CU 1302 directly (e.g., a fronthaul link) or indirectly (e.g., through the RIC) via network interface 1380. On-chip memory 1312' and the additional memory modules 1314 can each be considered a computer-readable medium / memory. Each computer-readable medium / memory can be non-transitory. Processor 1312 is responsible for general processing, including executing software stored on the computer-readable medium / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the processor when executing the software.

[0153] As discussed above, component 1399 is configured to receive a point cloud including a plurality of points associated with RF sensing from a first network entity. Component 1399 is configured to perform sensing operations based on the received point cloud. Component 1399 can be within processor 1312. Component 1399 can be one or more hardware components specifically configured to perform the stated processes / algorithms, implemented by one or more processors configured to perform the stated processes / algorithms, stored in a computer-readable medium for implementation by one or more processors, or some combination of the above. Network entity 1360 can include various components configured for various functions. In one configuration, network entity 1360 includes a component for receiving a point cloud including a plurality of points associated with RF sensing from a first network entity. Network entity 1360 includes a component for performing sensing operations based on the received point cloud.

[0154] In one configuration, the point cloud may be based on one or more radar data cubes. In one configuration, each of the plurality of points may be associated with at least one of range, velocity, or one or more angles. In one configuration, the point cloud may be associated with a global coordinate system or a local coordinate system associated with a first network entity. In one configuration, network entity 1360 includes components for receiving, from a first network entity, a second indication of one or more point cloud reporting capabilities associated with the first network entity. The one or more point cloud reporting capabilities may correspond to one or more of the parameters to be reported, coordinate systems, reporting formats, one or more frequencies, at least one antenna configuration, or beam pattern configuration. In one configuration, network entity 1360 includes components for sending a configuration of a point cloud report to the first network entity. The configuration of the point cloud report may correspond to one or more of a sensing reference signal configuration, reporting frequency, or reporting format. The reporting format may correspond to a full report or a differential report. In one configuration, the configuration of the point cloud report may further correspond to one or more of a velocity compensation mode, at least one reporting condition, or a representation system. In one configuration, network entity 1360 includes components for receiving, from the first network entity, a second indication of the position or orientation of the first network entity. In one configuration, the point cloud may be associated with a single frequency layer or multiple frequency layers. In one configuration, the first network entity may include at least one of a UE, a TRP, or a base station. The second network entity may include a sensing entity in a wireless communication system.

[0155] The component may be component 1399 of network entity 1360 configured to perform the functions recited by the component.

[0156] Re-reference Figures 4 to 13 , the first network entity may identify a point cloud including a plurality of points associated with RF sensing. The first network entity may send an indication of the point cloud to the second network entity. The second network entity may perform sensing operations based on the received point cloud. Thus, reporting of the point cloud from a reporting network entity to a sensing entity may be achieved.

[0157] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is illustrative of example methods. It should be understood that based on design preferences, the specific order or hierarchy of the blocks in the process / flowchart may be rearranged. Further, some blocks may be combined or omitted. The appended method claims present the elements of the various blocks in a sample order, but are not limited to the specific order or hierarchy presented.

[0158] 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 readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Thus, the claims are not limited to the aspects described herein, but are to be accorded the full scope consistent with the language of the claims, and the singular forms of the elements are not intended to mean "one and only one" but "one or more" unless specifically stated otherwise. Terms such as "if," "when," and "while" 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 or during the occurrence of an action, but simply imply that if the condition is met, then the action will occur, 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 having an advantage over other aspects. Unless specifically stated otherwise, 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 "any combination of A, B, C, or any of them," including any combination of A, B, and / or C, may include multiple As, multiple Bs, or multiple Cs. 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 "any combination of A, B, C, or any of them" 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 construed as a collection of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If a first device receives data from or sends data to a second device, the data may be received / sent directly between the first device and the second device, or indirectly between the first device and the second device through a collection of devices. All structural and functional equivalents of the elements of the aspects described throughout this disclosure that are known or later will be known to those of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. Additionally, nothing disclosed herein is intended to be dedicated to the public, whether or not such disclosure is explicitly recited in the claims. The words "module," "mechanism," "element," "device," etc. do not substitute for the word "component." Thus, no claim element is to be construed as a means-plus-function unless the element is expressly recited using the phrase "means for...".

[0159] As used herein, the phrase "based on" should not be construed to refer 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, a condition, a factor, etc.) should be construed as "at least based on A", unless stated otherwise specifically.

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

[0161] Aspect 1 is a method for wireless communication at a first network entity, the method comprising: identifying a point cloud including a plurality of points associated with RF sensing; and sending an indication of the point cloud to a second network entity.

[0162] Aspect 2 can be combined with Aspect 1 and includes: the point cloud is based on one or more radar data cubes.

[0163] Aspect 3 can be combined with any one of Aspects 1 and 2 and includes: each of the plurality of points is associated with at least one of a range, a speed, or one or more angles.

[0164] Aspect 4 can be combined with any one of Aspects 1 to 3 and includes: the point cloud is associated with a global coordinate system or a local coordinate system associated with the first network entity.

[0165] Aspect 5 can be combined with any one of Aspects 1 to 4 and further includes: sending a second indication of one or more point cloud reporting capabilities associated with the first network entity to the second network entity, where the one or more point cloud reporting capabilities correspond to one or more of the reported parameters, coordinate systems, reporting formats, one or more frequencies, at least one antenna configuration, or beam pattern configuration.

[0166] Aspect 6 can be combined with any one of Aspects 1 to 5 and further includes: receiving a configuration of a point cloud report from the second network entity, where the configuration of the point cloud report corresponds to one or more of a sensing reference signal configuration, a reporting frequency, or a reporting format, and where the reporting format corresponds to a full report or a differential report.

[0167] Aspect 7 can be combined with Aspect 6 and includes: the configuration of the point cloud report further corresponds to one or more of a speed compensation mode, at least one reporting condition, or a representation system.

[0168] Aspect 8 can be combined with Aspect 7 and includes: the configuration of the point cloud report further corresponds at least to the at least one reporting condition, and in order to identify the point cloud, the at least one processor is further configured to exclude at least one point from the point cloud based on the at least one reporting condition.

[0169] Aspect 9 can be combined with any one of Aspects 1 to 8, and further includes: sending, by the second network entity, a second indication of the position or orientation of the first network entity.

[0170] Aspect 10 can be combined with any one of Aspects 1 to 9, and includes: the point cloud being associated with a single frequency layer or multiple frequency layers.

[0171] Aspect 11 can be combined with any one of Aspects 1 to 10, and includes: the first network entity includes at least one of a UE, a TRP, or a base station, and wherein the second network entity includes a sensing entity in a wireless communication system.

[0172] Aspect 12 is a method for wireless communication at a second network entity, the method including: receiving, from a first network entity, a point cloud including a plurality of points associated with RF sensing; and performing a sensing operation based on the received point cloud.

[0173] Aspect 13 can be combined with Aspect 12, and includes: the point cloud being based on one or more radar data cubes.

[0174] Aspect 14 can be combined with any one of Aspects 12 and 13, and includes: each point in the plurality of points being associated with at least one of a range, a speed, or one or more angles.

[0175] Aspect 15 can be combined with any one of Aspects 12 to 14, and includes: the point cloud being associated with a global coordinate system or a local coordinate system associated with the first network entity.

[0176] Aspect 16 can be combined with any one of Aspects 12 to 15, and further includes: receiving, from the first network entity, a second indication of one or more point cloud reporting capabilities associated with the first network entity, wherein the one or more point cloud reporting capabilities correspond to one or more of one or more reported parameters, a coordinate system, a reporting format, one or more frequencies, at least one antenna configuration, or a beam pattern configuration.

[0177] Aspect 17 can be combined with any one of Aspects 12 to 16, and further includes: sending, to the first network entity, a configuration of a point cloud report, wherein the configuration of the point cloud report corresponds to one or more of a sensing reference signal configuration, a reporting frequency, or a reporting format, and wherein the reporting format corresponds to a full report or a differential report.

[0178] Aspect 18 can be combined with Aspect 17, and includes: the configuration of the point cloud report further corresponds to one or more of a speed compensation mode, at least one reporting condition, or a representation system.

[0179] Aspect 19 may be combined with any one of aspects 12 to 18 and further includes: receiving a second indication of the position or orientation of the first network entity from the first network entity.

[0180] Aspect 20 may be combined with any one of aspects 12 to 19 and includes: the point cloud is associated with a single frequency layer or multiple frequency layers.

[0181] Aspect 21 may be combined with any one of aspects 12 to 20 and includes: the first network entity includes at least one of a UE, a TRP, or a base station, and wherein the second network entity includes a sensing entity in a wireless communication system.

[0182] Aspect 22 is a device for wireless communication, the device including: at least one processor, the at least one processor coupled to a memory, and at least partially based on information stored in the memory, the at least one processor is configured to implement the method according to any one of aspects 1 to 21.

[0183] Aspect 23 may be combined with aspect 22 and further includes: a transceiver coupled to the at least one processor.

[0184] Aspect 24 is a device for performing wireless communication, the device including components for implementing any one of aspects 1 to 21.

[0185] Aspect 25 is a non-transitory computer-readable storage medium storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 1 to 21.

[0186] Aspects have been described herein. These aspects and other aspects are within the scope of the following claims.

Claims

1. An apparatus for wireless communication at a first network entity, the apparatus comprises: 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: identify a point cloud comprising a plurality of points associated with radio frequency (RF) sensing; and send an indication of the point cloud to a second network entity.

2. The apparatus according to claim 1, wherein the point cloud is based on one or more radar data cubes.

3. The apparatus according to claim 1, wherein each of the plurality of points is associated with at least one of range, velocity, or one or more angles.

4. The apparatus according to claim 1, wherein the point cloud is associated with a global coordinate system or a local coordinate system associated with the first network entity.

5. The apparatus according to claim 1, the at least one processor being further configured to: send a second indication of one or more point cloud reporting capabilities associated with the first network entity to the second network entity, wherein the one or more point cloud reporting capabilities correspond to one or more of one or more reported parameters, coordinate systems, reporting formats, one or more frequencies, at least one antenna configuration, or beam pattern configuration.

6. The apparatus according to claim 1, the at least one processor being further configured to: receive a configuration of a point cloud report from the second network entity, wherein the configuration of the point cloud report corresponds to one or more of a sensing reference signal configuration, reporting frequency, or reporting format, and wherein the reporting format corresponds to a full report or a differential report.

7. The apparatus according to claim 6, wherein the configuration of the point cloud report further corresponds to one or more of a velocity compensation mode, at least one reporting condition, or a representation system.

8. The apparatus according to claim 7, wherein the configuration of the point cloud report further corresponds at least to the at least one reporting condition, and to identify the point cloud, the at least one processor is further configured to exclude at least one point from the point cloud based on the at least one reporting condition.

9. The apparatus according to claim 1, the at least one processor being further configured to: send a second indication of the position or orientation of the first network entity to the second network entity.

10. The apparatus according to claim 1, wherein the point cloud is associated with a single frequency layer or multiple frequency layers.

11. The apparatus according to claim 1, wherein the first network entity comprises at least one of a user equipment (UE), a transmit receive point (TRP), or a base station, and wherein the second network entity comprises a sensing entity in a wireless communication system.

12. The apparatus according to claim 1, the apparatus further comprising a transceiver coupled to the at least one processor, wherein to send the indication of the point cloud, the at least one processor is configured to: send the indication of the point cloud via the transceiver.

13. A method for wireless communication at a first network entity, the method comprises: identifying a point cloud including a plurality of points associated with radio frequency (RF) sensing; and sending an indication of the point cloud to a second network entity.

14. The method according to claim 13, wherein the point cloud is based on one or more radar data cubes.

15. The method according to claim 13, wherein each of the plurality of points is associated with at least one of range, velocity, or one or more angles.

16. An apparatus for wireless communication at a second network entity, the apparatus comprises: a memory; and at least one processor coupled to the memory and at least partially based on information stored in the memory, the at least one processor being configured to: receive from a first network entity a point cloud including a plurality of points associated with radio frequency (RF) sensing; and perform a sensing operation based on the received point cloud.

17. The apparatus according to claim 16, wherein the point cloud is based on one or more radar data cubes.

18. The apparatus according to claim 16, wherein each of the plurality of points is associated with at least one of range, velocity, or one or more angles.

19. The apparatus according to claim 16, wherein the point cloud is associated with a global coordinate system or a local coordinate system associated with the first network entity.

20. The apparatus according to claim 16, the at least one processor being further configured to: receive from the first network entity a second indication of one or more point cloud reporting capabilities associated with the first network entity, wherein the one or more point cloud reporting capabilities correspond to one or more of reported parameters, coordinate systems, reporting formats, one or more frequencies, at least one antenna configuration, or beam pattern configuration.

21. The apparatus according to claim 16, the at least one processor being further configured to: send a configuration of a point cloud report to the first network entity, wherein the configuration of the point cloud report corresponds to one or more of a sensing reference signal configuration, a reporting frequency, or a reporting format, and wherein the reporting format corresponds to a full report or a differential report.

22. The apparatus according to claim 21, wherein the configuration of the point cloud report further corresponds to one or more of a velocity compensation mode, at least one reporting condition, or a representation system.

23. The apparatus according to claim 16, the at least one processor being further configured to: receive from the first network entity a second indication of the position or orientation of the first network entity.

24. The apparatus according to claim 16, wherein the point cloud is associated with a single frequency layer or multiple frequency layers.

25. The apparatus according to claim 16, wherein the first network entity includes at least one of a user equipment (UE), a transmit receive point (TRP), or a base station, and wherein the second network entity includes a sensing entity in a wireless communication system.

26. The apparatus according to claim 16, the apparatus further comprising a transceiver coupled to the at least one processor, wherein, in order to receive the point cloud including the plurality of points, the at least one processor is configured to: receive the point cloud including the plurality of points via the transceiver.

27. A method for wireless communication at a second network entity, the method comprising: receiving, from a first network entity, a point cloud including a plurality of points associated with radio frequency (RF) sensing; and performing a sensing operation based on the received point cloud.

28. The method according to claim 27, wherein the point cloud is based on one or more radar data cubes.

29. The method according to claim 27, wherein each point of the plurality of points is associated with at least one of range, velocity, or one or more angles.

30. The method according to claim 27, wherein the point cloud is associated with a global coordinate system or a local coordinate system associated with the first network entity.

Images