Bistatic sensing beam pairing in integrated sensing and communication system

Abstract

Aspects presented herein may improve performance of an ISAC system by enabling a receiving entity to constrain Rx beam scanning of the receiving entity in a particular beam direction and / or gain during bistatic / multi-static RF sensing. In one aspect, an apparatus configures the receiving entity to perform an Rx beam scan constrained based on at least one of a Tx beam direction, a Tx power, a Tx beam gain, or a Tx beam path loss of a Tx beam from a transmitting entity, or based on a predicted location of a target. The apparatus performs the Rx beam scan on at least one of a set of Rx beam directions or a set of Rx beam gains constrained by the at least one of the Tx beam direction, the Tx power, the Tx beam gain, or the Tx beam path loss of the Tx beam from the transmitting entity or constrained by the predicted position of the target.

Description

Technical Field

[0001] The present disclosure relates generally to communication systems, and more particularly to positioning systems involving radio frequency (RF) sensing. Background Art

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

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

[0004] A simplified summary of one or more aspects is presented below to provide a basic understanding of these aspects. This summary is not an exhaustive overview of all contemplated aspects. This summary is neither intended to identify key or important elements of all aspects nor to describe 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 a more detailed description presented later.

[0005] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus configures a receiving entity to perform a receive (Rx) beam scan constrained based on at least one of a Tx beam direction, a Tx power, a Tx beam gain, or a Tx beam path loss of a transmit (Tx) beam from a transmitting entity or based on a predicted position of a target. The apparatus performs the Rx beam scan on at least one of a set of Rx beam directions or a set of Rx beam gains constrained by at least one of the Tx beam direction, the Tx power, the Tx beam gain, or the Tx beam path loss of the Tx beam from the transmitting entity or by the predicted position of the target.

[0006] To achieve the aforementioned and related purposes, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail certain exemplary features of one or more aspects. However, these features are only indicative of only some of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0009] Figure 2B is a diagram illustrating an example of DL channels within a subframe according to various aspects of the present disclosure.

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

[0011] Figure 2D is a diagram illustrating an example of UL channels within a subframe according to various aspects of the present disclosure.

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

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

[0014] Figure 5 is a diagram illustrating an example of a radar signal (eg, a radar reference signal (RRS)) generated by a wireless device according to various aspects of the present disclosure.

[0015] Figure 6 is a diagram illustrating an example of shared components for integrated sensing and communication (ISAC) according to various aspects of the present disclosure.

[0016] Fig. 7A is a diagram illustrating an example co-located and cooperating radar system and communication system in accordance with various aspects of the present disclosure.

[0017] Figure 7B is a diagram illustrating an example co-design of a communication system and a radar system according to various aspects of the present disclosure.

[0018] Fig. 8A is a diagram illustrating an example monostatic sensing mode according to various aspects of the present disclosure.

[0019] Figure 8B is a diagram illustrating example bistatic / multistatic sensing modes in accordance with various aspects of the present disclosure.

[0020] Fig. 9 is a diagram illustrating an example bistatic sensing radar geometry in accordance with various aspects of the present disclosure.

[0021] Fig.10 is a diagram illustrating example sensing beam scanning for bistatic / multistatic sensing in accordance with various aspects of the present disclosure.

[0022] Fig.11 is a diagram illustrating examples of useful and less useful receive (Rx) beams in accordance with various aspects of the present disclosure.

[0023] Fig. 12A is a diagram illustrating an example in which a receiver constrains an Rx beam direction for a given transmit (Tx) beam based on a transmit range of the Tx beam according to various aspects of the present disclosure.

[0024] Fig. 12B is a diagram illustrating an example in which a receiver constrains an Rx beam direction for a given Tx beam based on a transmission range of the Tx beam according to various aspects of the present disclosure.

[0025] Fig.13 is a diagram illustrating an example in which a receiver constrains an Rx beam direction for a given Tx beam based on a reference signal received power (RSRP) of the Tx beam according to various aspects of the present disclosure.

[0026] Fig.14 is a diagram illustrating an example in which a receiver constrains an Rx beam direction for a given Tx beam based on an RSRP of the Tx beam according to various aspects of the present disclosure.

[0027] Fig.15 is a diagram illustrating an example in which a receiver constrains an Rx beam direction based on a predicted target position according to various aspects of the present disclosure.

[0028] Fig.16 is a diagram illustrating an example in which a receiver constrains an Rx beam gain based on a Tx beam of a transmitter according to various aspects of the present disclosure.

[0029] Fig.17 is a diagram illustrating an example in which a receiver constrains an Rx beam direction / gain based on a partition according to various aspects of the present disclosure.

[0030] Fig.18 is a flow chart of a method of wireless communication.

[0031] Fig.19 is a flow chart of a method of wireless communication.

[0032] Fig. 20 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities.

[0033] Fig.21 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities.

[0034] Fig. 22 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities. DETAILED DESCRIPTION

[0035] Various aspects presented herein can improve the efficiency and time of bistatic / multistatic sensing. Various aspects presented herein can provide better radio resource usage and power savings for devices performing RF sensing, and improve sensing accuracy by enabling beam pair power control. For example, various aspects presented herein can enable a receiver to constrain the beam scanning of the receiver in certain directions and / or using certain power parameters based on the transmitter's Tx beam to save beams, radio resources, and / or power used for beam scanning during bistatic sensing.

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

[0037] Several aspects of telecommunication systems are also presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and illustrated in the accompanying 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 such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0038] By way of example, an element, or any part of an element, or any combination of elements may be implemented as a "processing system", which 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 chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic components, discrete hardware circuits, and other suitable hardware configured to perform various functions described throughout the present disclosure. One or more processors in a processing system may execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, or any combination thereof.

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

[0040] Although various aspects, specific implementations and / or use cases are described in this application by the illustration of some examples, additional or different aspects, specific implementations and use cases may be generated in many different arrangements and scenarios. The various aspects, specific implementations and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, various aspects, specific implementations and / or use cases can be generated via integrated chip specific implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, artificial intelligence (AI) enabled devices, etc.). Although some examples may or may not be specifically for use cases or applications, the described examples may have a wide range of applicability. Various aspects, specific implementations and / or use cases can be implemented from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the range of aggregated, distributed or original equipment manufacturer (OEM) devices or systems in conjunction with one or more technologies herein. In some practical environments, the equipment combined with the various 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 include 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 various techniques described herein can be practiced in a wide variety of devices of various sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc.

[0041] The deployment of a communication system (such as a 5G NR system) can be arranged in a variety of ways using various components or constituent parts. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or network equipment (such as a base station (BS)), or one or more units (or one or more components) performing base station functionality can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

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

[0043] Base station operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configuration such as that initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

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

[0045] Each of the units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO framework 105) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively, 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 a transmission medium. For example, these units may include a wired interface configured to receive signals or send signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive signals or send signals to one or more of the other units via a wireless transmission medium, or both.

[0046] In some aspects, 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 CU 110. 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 specific implementations, CU 110 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). CU 110 may be implemented to communicate with DU 130 as needed for network control and signaling.

[0047] 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, DU 130 may host one or more of a radio link control (RLC) layer, a 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, demodulation, etc.) at least in part according to a functional split (such as a functional split defined by 3GPP). In some aspects, DU 130 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

[0048] The lower layer functionality may be implemented by one or more RUs 140. In some deployments, the RU 140 controlled by the DU 130 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on functional splitting (such as lower layer functional splitting). In such an architecture, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may enable the implementation of the DU 130 and the CU 110 in a cloud-based RAN architecture (such as a vRAN architecture).

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

[0050] The non-RT RIC 115 may be configured to include logic functions that implement 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 may be coupled to or communicate with the near-RT RIC 125 (such as via an A1 interface). The near-RT RIC 125 may be configured to include logic functions that implement near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 110, one or more DUs 130, or both, and the O-eNB with the near-RT RIC 125.

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

[0052] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Therefore, the base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component is indicated by a dotted line to indicate that each component may or may not be included in the base station 102). The base station 102 provides an access point to the core network 120 for the UE 104. The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). 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. A heterogeneous network may also include a home evolved Node B (eNB) (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 uplink (UL) (also known as reverse link) transmission from UE 104 to RU 140 and / or downlink (DL) (also known as 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 a carrier aggregation of up to Yx MHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use a spectrum of up to Y MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.) bandwidth. The carriers may be adjacent to each other or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). The component carrier 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 carrier may be referred to as a secondary cell (SCell).

[0053] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL wireless wide area network (WWAN) spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication may be performed by a variety of 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.

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

[0055] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0056] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz–24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6GHz–71GHz), FR4 (71GHz–114.25GHz), and FR5 (114.25GHz–300GHz). Each of these higher frequency bands falls within the EHF band.

[0057] In view of the above, unless otherwise specifically stated, if the term "below 6 GHz" or the like is used in this document, it may broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, if the term "millimeter wave" or the like is used in this document, it may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and / or FR5, or may be within the EHF band.

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

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

[0060] 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. AMF 161 is a control node that handles signaling between UE 104 and core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports 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, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, LMF 166, position determination entity (PDE), serving mobile location center (SMLC), mobile positioning center (MPC), etc. GMLC 165 and LMF 166 support UE location services. GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. LMF 166 receives measurement and assistance information from NG-RAN and UE 104 via AMF 161 to calculate the location of UE 104. NG-RAN may determine the location of UE 104 using one or more positioning methods. Positioning UE 104 may involve signal measurements, position estimation, and optional speed calculation based on these measurements. Signal measurements may be performed by UE 104 and / or serving base station 102. The measured signals may be based on a satellite positioning system (SPS) 170 (e.g., one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / location systems), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, 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, NR signals (e.g., multi-round trip time (multi-RTT), DL angle of departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning), and / or one or more of other systems / signals / sensors.

[0061] Examples of UE 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, 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, electric meters, gas pumps, large or small kitchen appliances, healthcare equipment, implants, sensors / actuators, displays, or any other similarly functional devices. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as stations, mobile stations, subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, user agents, mobile clients, clients, or some other suitable terminology. In some scenarios, the term UE may also be applied to one or more supporting devices, such as in a device constellation arrangement. One or more of these devices may access the network collectively and / or individually.

[0062] Reference again Figure 1 In certain aspects, the UE 104 may be configured to configure the receiving entity to perform an Rx beam scan constrained based on at least one of the Tx beam direction, Tx power, Tx beam gain, or Tx beam path loss of the Tx beam from the transmitting entity or based on a predicted position of a target; and to perform Rx beam scanning on at least one of a set of Rx beam directions or a set of Rx beam gains constrained by at least one of the Tx beam direction, Tx power, Tx beam gain, or Tx beam path loss of the Tx beam from the transmitting entity or by a predicted position of a target via the beam scanning constraint configuration component 198. In certain aspects, the base station 102 may be configured to configure the receiving entity to perform an Rx beam scan constrained based on at least one of the Tx beam direction, Tx power, Tx beam gain, or Tx beam path loss of the Tx beam from the transmitting entity or based on a predicted position of a target; and to perform Rx beam scanning on at least one of a set of Rx beam directions or a set of Rx beam gains constrained by at least one of the Tx beam direction, Tx power, Tx beam gain, or Tx beam path loss of the Tx beam from the transmitting entity or by a predicted position of a target via the beam scanning constraint configuration component 199.

[0063] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B FIG230 is a diagram illustrating an example of DL channels within a 5G NR subframe. Figure 2CFIG250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2D FIG280 is a diagram illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD) (wherein for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL), or may be time division duplex (TDD) (wherein for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL). Figure 2A , Figure 2C In the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are full DL and full UL, respectively. Other slot formats 2-61 include a mix of DL, UL and flexible symbols. The slot format is configured for the UE by the received slot format indicator (SFI) (dynamically configured by DL control information (DCI) or semi-statically / statically configured by radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0064] FIG. 2A to FIG. 2D The frame structure is illustrated, and various aspects of the present disclosure may be applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 subframes of the same size (1ms). Each subframe may include one or more time slots. A subframe may also include a microslot, which may include 7, 4 or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For a normal CP, each time slot may include 14 symbols, and for an extended CP, each time slot may include 12 symbols. The symbol on the DL may be a CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbol. The symbol on the UL may be a CP-OFDM symbol (for high throughput scenarios) or a discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbol (also known as a single carrier frequency division multiple access (SC-FDMA) symbol) (for power-limited scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and parameter set. The parameter set defines the subcarrier spacing (SCS) and effectively defines the symbol length / duration, which is equal to 1 / SCS.

[0065]

[0066] 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. Accordingly, for normal CP and parameter set μ, there are 14 symbols / slot and 2 μ timeslots / subframe. The subcarrier spacing can be equal to 2 μ *15kHz, where μ is parameter set 0 to 4. Therefore, the subcarrier spacing for parameter set μ=0 is 15kHz, and the subcarrier spacing for parameter set μ=4 is 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example of a normal CP is provided, where there are 14 symbols per slot, and the parameter set μ=2, where there are 4 slots per subframe. 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 may have a specific parameter set and CP (normal or extended).

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

[0068] like Figure 2A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) (indicated 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 may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0069] Figure 2BExamples of various DL channels within a subframe of a frame are illustrated. A 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 RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. A 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., a common search space, a UE-specific search space) during a PDCCH monitoring opportunity on a CORESET, wherein 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. A primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identity. A secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also 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 such as system information blocks (SIBs) that are not sent via the PBCH, and paging messages.

[0070] like Figure 2C As illustrated, some of the REs carry DM-RS (indicated as R for a particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may send a DM-RS for a physical uplink control channel (PUCCH) and a DM-RS for a physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first or first two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS may be sent in different configurations. The UE may send a sounding reference signal (SRS). The SRS may be sent in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the teeth of the comb. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0071] Figure 2DExamples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and 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.

[0072] Figure 3 370 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 functions. 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 medium access control (MAC) layer. The controller / processor 375 provides RRC layer functions associated with broadcasting 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 functions associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with delivery of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions 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 through HARQ, priority handling, and logical channel prioritization.

[0073] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functions associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transmission channel, forward error correction (FEC) decoding / decoding of the transmission 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 the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time domain and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially pre-coded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation schemes, as well as for spatial processing. Channel estimates may be derived based on reference signals and / or channel condition feedback sent by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier with a corresponding spatial stream for transmission.

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

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

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

[0077] The TX processor 368 may use channel estimates derived by the channel estimator 358 from a reference signal or feedback sent by the base station 310 to select the appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

[0078] UL transmissions are processed at the base station 310 in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318Rx receives a signal through its corresponding antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to the RX processor 370.

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

[0080] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform operations related to Figure 1 The beam scanning constraint configuration component 198 combines various aspects.

[0081] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform operations related to Figure 1 The beam scanning constraint configuration component 199 combines various aspects.

[0082] Figure 4 4 is a diagram illustrating an example of UE positioning based on reference signal measurement. UE 404 may be at time T SRS_TX UL-SRS 412 is sent and at time T PRS_RX A DL positioning reference signal (PRS) (DL-PRS) 410 is received. TRP 406 may be at time T SRS_RX Receive UL-SRS 412 and at time T PRS_TX 410. 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 UL-SRS 412 based on ||T SRS_RX –T PRS_TX |–|T SRS_TX –T PRS_RX || to determine RTT 414. Thus, multi-RTT positioning may utilize UE ERx-Tx time difference measurements (ie, |T SRS_TX –T PRS_RX |) and DL-PRS reference signal received power (RSRP) (DL-PRS-RSRP), and the measured TRP Rx-Tx time difference measurement (ie, |T SRS_RX –T PRS_TX|) and UL-SRS-RSRP. UE 404 measures UE Rx-Tx time difference measurement (and / or DL-PRS-RSRP of received signal) using assistance data received from positioning server, and TRP 402, 406 measures gNB Rx-Tx time difference measurement (and / or UL-SRS-RSRP of received signal) using assistance data received from positioning server. These measurements may be used at positioning server or UE 404 to determine RTT, which is used to estimate the position of UE 404. Other methods for determining RTT are possible, such as, for example, using DL-TDOA and / or UL-TDOA measurements.

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

[0084] DL-TDOA positioning may utilize DL reference signal time difference (RSTD) (and / or DL-PRS-RSRP) of downlink signals received from multiple TRPs 402, 406 at the UE 404. The UE 404 measures the DL RSTD (and / or DL-PRS-RSRP) of the received signals using assistance data received from a positioning server, and the resulting measurements are used along with other configuration information to position the UE 404 relative to neighboring TRPs 402, 406.

[0085] UL-TDOA positioning may utilize the UL relative time of arrival (RTOA) (and / or UL-SRS-RSRP) of uplink signals sent from UE 404 at multiple TRPs 402, 406. TRPs 402, 406 measure the UL-RTOA (and / or UL-SRS-RSRP) of received signals using assistance data received from a positioning server, and the resulting measurements are used along with other configuration information to estimate the position of UE 404.

[0086] UL-AoA positioning may utilize the measured azimuth angle of arrival (A-AoA) and zenith angle of arrival (Z-AoA) of uplink signals sent from the UE 404 at multiple TRPs 402, 406. The TRPs 402, 406 measure the A-AoA and Z-AoA of the received signals using assistance data received from a positioning server, and the resulting measurements are used along with other configuration information to estimate the position of the UE 404.

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

[0088] In addition to network-based UE positioning technology, wireless devices (e.g., base stations, components of base stations, UEs, etc.) may also be configured to include radar capabilities, which may be referred to as "radio frequency (RF) sensing" and / or "cellular-based RF sensing". For example, a wireless device may send a radar reference signal (RRS) and measure the RRS reflected from one or more objects. Based at least in part on the measurement, the wireless device may determine or estimate the distance between the wireless device and the one or more objects. In another example, a first wireless device may also receive an RRS sent from a second wireless device, wherein the first wireless device may determine or estimate the distance between the first wireless device and the second wireless device based at least in part on the received RRS. Therefore, in some examples, RF sensing technology may be used for UE positioning and / or for assisting UE positioning. For the purposes of this disclosure, a device capable of performing RF sensing (e.g., sending and / or receiving an RRS for detecting an object or for estimating the distance between a device and an object) may be referred to as an "RF sensing node". For example, an RF sensing node may be a UE, a base station, a component of a base station, a TRP, a device capable of sending an RRS, and / or a device configured to perform radar functions, etc.

[0089] Figure 5 5 is a diagram illustrating an example radar signal (e.g., RRS) generated by an RF sensing node according to various aspects of the present disclosure. The RF sensing node 503 can detect the object 520 (e.g., the position, distance, and / or speed of the object 520 relative to the RF sensing node 503) by sending the RRS toward the object 520 and receiving the RRS reflected (e.g., bounced) from the object 520. In some examples, the object 520 can be a radar receiver or have the ability to receive and process the RRS.

[0090] In one example, the RRS may be a chirp signal including a frequency that varies linearly (e.g., with a frequency sweep) by a modulated signal over a fixed time period (e.g., within a sweep time). For example, as shown by diagram 500, a transmitted chirp signal 502 may have a starting frequency at 504 of a sine wave. The frequency may then gradually (e.g., linearly) increase over the sine wave until the end (or highest) frequency at 506 of the sine wave is reached, and then the frequency of the signal may return to the starting frequency as shown at 508, and another chirp signal 510 may be transmitted in the same manner. In other words, each chirp signal may include an increase (e.g., linearly) in frequency and a decrease in frequency, or vice versa (e.g., including a decrease in frequency and then an increase in frequency), such that the RF sensing node 503 may transmit a chirp signal that sweeps over frequency. In some examples, such a chirp signal may also be referred to as a frequency modulated continuous wave (FMCW).

[0091] After a chirp signal (e.g., chirp signals 502, 510, 512, etc.) is transmitted by the RF sensing node 503, the transmitted chirp signal may reach the object 520 and be reflected back to the RF sensing node 503, such as shown by reflected chirp signals 514, 516, and 518, which may correspond to the transmitted chirp signals 502, 510, and 512, respectively. Because there may be a distance between the RF sensing node 503 and the object 520 and / or it may take time for the transmitted chirp signal to reach the object 520 and be reflected back to the RF sensing node 503, there may be a delay between the transmitted chirp signal and its corresponding reflected chirp signal. Since the delay may be proportional to the ranging between the RF sensing node 503 and the object 520 (eg, the farther the target, the greater the delay, and vice versa), the RF sensing node 503 may be able to measure or estimate the distance between the RF sensing node 503 and the object 520 based on the delay.

[0092] In some examples, the RF sensing node 503 may also measure a frequency difference between the transmitted chirp signal and the reflected chirp signal, which may also be proportional to the distance between the RF sensing node 503 and the object 520. In other words, since the frequency difference between the reflected chirp signal and the transmitted chirp signal increases with delay, and the delay is linearly proportional to the range, the distance of the object 520 from the RF sensing node 503 may also be determined based on the frequency difference. Therefore, the reflected chirp signal from the object 520 may be mixed with the transmitted chirp signal and down-converted to generate a beat signal (f b), the beat signal may be linearly proportional to the range after demodulation. For example, the RF sensing node 503 may determine the beat signal 522 by mixing the transmitted chirp signal 502 with its corresponding reflected chirp signal 514. Although the example in the figure illustrates the use of FMCW waveform for RRS, the RF sensing node 503 may also use other types of radar waveforms for RRS.

[0093] Due to the increase in the amount of bandwidth (BW) allocated for cellular communication systems (e.g., 5G and above) and the increase in the number of applications (e.g., use cases) introduced with cellular communication systems, joint communication and RF sensing (which may also be referred to as integrated sensing and communication (ISAC) and / or joint communication-radar (JCR)) may become an important feature of cellular systems. For example, a wireless device (e.g., a base station, a component of a base station, a UE, a component of a UE, an RF sensing node, etc.) may be configured to send a communication signal (e.g., PDSCH, PUSCH, PSSCH, etc.) together with a radar signal (e.g., RRS, FMCW signal, etc.) or in close time (e.g., based on TDM, FDM, SDM, etc.). In addition, an OFDM waveform (or a variant thereof) may be used as a waveform for ISAC / JCR because an OFDM waveform may enable in-band multiplexing with other cellular reference signals and physical channels. Therefore, the radar signal may be multiplexed with a communication signal based on an OFDM waveform. For purposes of this disclosure, a wireless device that performs RF sensing based on an OFDM waveform or sends an RRS based on an OFDM waveform may be referred to as an "OFDM radar."

[0094] Figure 6 600 is a diagram illustrating an example of shared components for an ISAC according to various aspects of the present disclosure. A wireless device may be configured to share the RF (and possibly baseband) hardware components and frequency bands of the wireless device for both sensing and communication to provide a cost and spectrum efficient design. In some examples, the ISAC may be used for macro sensing, such as weather monitoring, autonomous driving, dynamic mapping, low altitude airspace (e.g., unmanned aerial vehicle (UAV)) management, and intruder detection. In other examples, the ISAC may be used for micro sensing, such as gesture recognition, vital sign detection, and high resolution imaging using THz. In addition, the ISAC may also provide sensing-assisted communications, where information obtained via sensing (e.g., whether there are obstacles in certain directions) may be used to improve communications, such as for beam management.

[0095] In some implementations, the ISAC system can be categorized as a co-located and cooperating radar system and communication system and a co-design of the communication system and the radar system. Fig. 7A700A is a diagram illustrating an example co-located and collaborative radar system and communication system according to various aspects of the present disclosure. For this type of ISAC system, some knowledge (e.g., transmission information / configuration) is shared between the communication aspect and the radar aspect of the system to improve the performance of the system without changing the core operation of the radar system and the communication system too much. For example, as shown by diagram 700A, each of the devices used by a first user (user A) and a second user (user B) may include a radar transmit (Tx) / receive (Rx) component capable of sending / receiving a radar reference signal (RRS) and a communication Tx / Rx component capable of sending / receiving a communication signal. The radar Tx / Rx component and the communication Tx / Rx component may communicate with each other to coordinate the transmission of radar signals and communication signals to other devices and / or the reception of radar signals and communication signals from other devices.

[0096] Figure 7B 700B is a diagram illustrating an example co-design of a communication system and a radar system according to various aspects of the present disclosure. For this type of ISAC system, as shown by diagram 700B, a common transmitter or receiver is used for both communication and radar functions. This type of system may specify a certain amount of modification in the transmission waveform generation or receiver processing of both or either of the radar system and the communication system. This type of ISAC system design may provide improved hardware and spectrum reuse. A communication-centric ISAC utilizing a single communication transmission hardware may be favored by certain network implementations because it may support both high data rate communications and high resolution sensing. For example, as described above, an OFDM-based waveform may be used by a radar system for sensing purposes while remaining compatible with an OFDM-based communication system.

[0097] In some implementations, RF sensing can be categorized into two types of RF sensing modes: a monostatic sensing mode and a bistatic / multistatic sensing mode (which may also be referred to as "monostatic RF sensing" and "bistatic RF sensing," respectively). Fig. 8A 800A is a diagram illustrating an example single-base sensing mode according to various aspects of the present disclosure. Under single-base sensing, the transmitter (e.g., Tx antenna panel) and receiver (e.g., Rx antenna panel) of the RF sensor are co-located, such as in the same wireless device (e.g., base station, component of base station, UE, component of UE, etc.). Therefore, the transmission and reception of radar signals can be performed by one device. In other words, one radar / sensor is configured to both transmit sensing signals and receive reflected sensing signals. The advantage of single-base sensing is that it may not specify Tx / Rx (transmitter / receiver) pairing / grouping. However, single-base sensing may specify self-interference mitigation because the same wireless device is used to transmit both sensing signals and communication signals.

[0098] Figure 8B 800B is a diagram illustrating an example dual-base / multi-base sensing mode according to various aspects of the present disclosure. In dual-base / multi-base sensing, the transmitter and receiver can be separate (e.g., on different wireless devices and / or locations). For example, a transmitter (e.g., a Tx antenna panel) of a first wireless device can transmit sensing signals, and these sensing signals or sensing signals reflected from one or more objects can be received by a receiver (e.g., an Rx antenna panel) of a second wireless device (e.g., a sensing base station, a sensing UE, etc.). An advantage of dual-base / multi-base sensing is that it may not specify self-interference mitigation. However, dual-base / multi-base sensing may specify Tx / Rx (transmitter / receiver) pairing / grouping. However, single-base sensing may specify self-interference mitigation because the same wireless device is used to transmit both sensing signals and communication signals.

[0099] Fig. 9 900 is a diagram illustrating an example bistatic sensing radar geometry in accordance with various aspects of the present disclosure. In one example, a setup for a bistatic sensing radar can be represented as a bistatic triangle. A transmitter (e.g., Tx panel) and a receiver (e.g., Rx panel) are separated by a baseline L, R T represents the range from the transmitter to the target, and R R is the range from the receiver to the target. A bistatic angle β is formed at the target. There are three parameters that the receiver can measure: the range difference (R) between the directly sensed signal (e.g., H1) and the transmitter-target-receiver path (e.g., H2). T +R R -L), the arrival angle θ of the received reflected sensing signal R and the Doppler frequency shift f of the received reflected sensing signal D If the distance L is known, then the measured quantity (R T +R R -L) Extract dual base range (R T +R R ). Therefore, when measuring the arrival angle θ R The range of the target from the receiver can then be found based on:

[0100] Fig.101 is a diagram 1000 illustrating an example sensing beam scanning for bistatic / multistatic sensing according to various aspects of the present disclosure. To detect a target 1006, a transmitter 1002 (e.g., a first base station, a first UE, a Tx antenna panel, etc.) may measure the position and velocity of the target 1006 based on performing beam scanning with a receiver 1004 (e.g., a second base station, a second UE, an Rx antenna panel, etc.). For example, the position of the target 1006 may be determined based on the intersection of the Tx beam (of the transmitter 1002) and the Rx beam pair (of the receiver 1004) through which the target 1006 is detected. For another example, the position of the target 1006 may be determined based on the time of flight (ToF) of a signal transmitted by the Tx beam (of the transmitter 1002) and received by the Rx beam (of the receiver 1004). For another example, the position of the target 1006 may be determined based on a combination of the above two examples. The speed of the target 1006 may be analyzed based on the Doppler shift of the received signal in the Rx beam of the receiver 1004. In some examples, the transmitter 1002 may be configured to perform a Tx beam scan in all directions from a specific set. Then, for one Tx beam during the scan, the receiver 1004 may also be configured to perform an Rx beam scan in all directions from the specific set. Therefore, if there are N Tx beams and M Rx beams in a specific set, the total number of Tx and Rx beam pairs in the scan is NM. For example, if there are three (3) Tx beams and five (5) Rx beams, there are a total of fifteen (e.g., 3×5=15) Tx-Rx beam pairs. For the purposes of this disclosure, a "beam pair" may refer to a Tx beam at a transmitter and an Rx beam at a receiver. For example, if a transmitter transmits a signal / data to a receiver using Tx beam X and the receiver receives the signal / data using Rx beam Y, Tx beam X and Rx beam Y may be referred to as a beam pair.

[0101] In some scenarios, such as Fig.11 As shown in the diagram 1100 of , for a given Tx beam, there may be only a set of Rx beams that may be useful (e.g., providing useful information and measurements) in certain directions, and Rx beams in other directions may not be used or provide less useful information and measurements. Therefore, if the receiver is configured to perform Rx beam scanning in all directions in the set, there may be a waste of resources and / or receiver power because some directions and intersection partitions may be outside the coverage of the Tx beam.

[0102] Various aspects presented herein can improve the efficiency and time of bistatic / multistatic sensing. Various aspects presented herein can provide better radio resource usage and power savings for devices performing RF sensing, and improve sensing accuracy by enabling beam pair power control. For example, various aspects presented herein can enable a receiver to constrain the beam scanning of the receiver in certain directions and / or using certain power parameters based on the transmitter's Tx beam to save beams, radio resources, and / or power used for beam scanning during bistatic sensing.

[0103] Fig. 12A and Fig. 12B 1200A and 1200B are diagrams illustrating examples of a receiver according to various aspects of the present disclosure constraining an Rx beam direction for a given Tx beam based on the transmission range of the Tx beam. A receiver 1204 (which may be a first UE, a first base station, or a component of a first base station, etc.) may be configured to constrain the Rx beam scanning direction of the receiver based on the Tx beam direction, Tx power, and path loss of a Tx beam from a transmitter 1202 (which may be a second UE, a second base station, or a component of a second base station, etc.). This configuration may reduce the Rx beam scanning time and power of the receiver 1204.

[0104] In one aspect, the receiver 1204 may start Rx beam scanning at a start angle / direction and stop Rx beam scanning at a stop angle / direction based on the Tx beam of the transmitter 1202. Fig. 12A As shown in FIG. 1200A of FIG. 1200A , the starting angle / direction of the Rx beam scan may be oriented toward the transmitter 1202 or toward the Tx antenna panel of the transmitter 1202, and the stopping angle / direction of the Rx beam scan may be the maximum transmission range of the Tx beam. In some examples, the maximum transmission range of the Tx beam may be based on the transmission power of the Tx beam from the transmitting entity, the Tx beam gain, the Tx antenna gain, the Tx signal carrier frequency, the wireless channel coefficient, or a combination thereof. In other examples, such as Fig. 12B As shown in the diagram 1200B of , the maximum transmission range of the Tx beam may be further limited by path loss, obstacles and / or ground plane. During the Rx beam scanning, the transmitter 1202 may periodically transmit the same Tx beam.

[0105] In another example, if Fig.13As shown in FIG. 1300 , instead of configuring the stop angle / direction as the maximum transmission range of the Tx beam, the receiver 1204 and the receiver 1204 may determine the stop angle / direction based on the reference signal received power (RSRP) of the Tx beam being less than the RSRP threshold. For example, the receiver 1204 may start the Rx beam scan at a starting angle and measure the RSRP of the Tx beam. If the RSRP is higher than the threshold, the receiver may continue the Rx beam scan, such as moving toward the next beam step angle and performing RSRP measurements. However, when the RSRP measured at the receiver 1204 keeps decreasing and is lower than the threshold, the receiver 1204 may stop the Rx beam scan. Similarly, during the Rx beam scan, the transmitter 1202 may periodically send the same Tx beam.

[0106] Fig.14 1400 is a diagram illustrating an example of a receiver according to various aspects of the present disclosure constraining an Rx beam direction for a given Tx beam based on the RSRP of the Tx beam. In another example, to improve the efficiency and time of Rx beam scanning, the receiver 1204 may be configured to start Rx beam scanning using a wider Rx beam and measure the RSRP of the Tx beam. As shown at 1402, if the RSRP at the receiver 1204 is lower than or equal to a threshold (e.g., RSRP ≤ threshold), the receiver 1204 may change / move the Rx beam used for Rx beam scanning to the next long angle / direction and continue Rx beam scanning using a wider Rx beam. However, as shown at 1404, if the RSRP is greater than the threshold (e.g., RSRP>threshold), the receiver 1204 may change the wider Rx beam to a narrower Rx beam, and continue to perform Rx beam scanning in the same direction (e.g., the direction of the wide beam with RSRP greater than the threshold) at a smaller step angle / direction, as shown at 1406. In some examples, the threshold for continuing to move to the next step angle / direction or for changing to a narrower beam may be configured as a variable that depends on the Rx beam width. For example, since the Rx beam width may be associated with the Rx beam gain, the Rx beam width may affect the RSRP measured at the receiver 1204. Therefore, a higher threshold may be configured for a narrower beam, and a lower threshold may be configured for a wider beam, and so on.

[0107] Fig.151500 is a diagram illustrating an example of a receiver constraining an Rx beam direction based on a predicted target position according to various aspects of the present disclosure. In another example, in order to improve the efficiency and time of Rx beam scanning and / or Tx beam scanning, the receiver 1204 may be configured to constrain the Rx beam direction based on the next predicted position of the target. For example, as shown at 1502, in the case where the receiver 1204 detects the target 1504 during the Rx beam scanning, the receiver 1204 may measure at least the heading and speed of the target 1504. The receiver 1204 may be able to detect the target 1504 based on RSRP, time of flight (ToF), Doppler shift, or a combination thereof that meets one or more thresholds. Then, as shown at 1506, the receiver 1204 may predict the next position of the target 1504 for the next Tx-Rx beam pair based on the measured heading and speed of the target 1504. As shown at 1508 , the receiver 1204 may constrain the Rx beam direction / angle toward the predicted location of the target 1504 to save radio resources and / or power at the receiver 1204 .

[0108] In some examples, as shown at 1510, the receiver 1204 may report the measured target heading and velocity to the transmitter 1202. Similarly, the transmitter 1202 may predict the location of the target 1504 based on the measured heading and velocity received from the receiver 1204, and the transmitter 1202 may also constrain the Tx beam direction / angle toward the predicted location of the target 1504 to save radio resources and / or power at the transmitter 1202. Thus, both the Tx and Rx beam directions / angles may be constrained by the measured target heading and velocity because when the next Tx and Rx beam pair is used, both the transmitter 1202 and the receiver 1204 are able to predict the next location of the target 1504 using the target heading and velocity (e.g., the next Tx and Rx beams are configured to point to the predicted next location of the target).

[0109] In another example, for bistatic sensing, since the heading and speed measurements may be projections of the actual heading and speed in a specific direction, the predicted next position of the target may be an area. Therefore, the transmitter 1202 and the receiver 1204 may perform Tx and Rx beam scanning, respectively, in the predicted area to save radio resources and / or power.

[0110] Fig.161600 is a diagram illustrating an example of a receiver constraining an Rx beam gain based on a Tx beam of a transmitter according to various aspects of the present disclosure. In another aspect of the present disclosure, in order to save radio resources or power, the receiver 1204 can be configured to maintain a constant received power of targets at different locations. The accuracy of bistatic / multistatic sensing can also be improved by enhancing analog-to-digital converter (ADC) utilization, such as making the received power mainly affected by the radar cross section (RCS) of the target.

[0111] In one example, the beam gain at the transmitter 1202 and / or the receiver 1204 may be dynamically adjusted based on the target, so that a constant receiver power may be maintained at the receiver 1204 for targets at different locations. For example, as shown at 1602, for targets with shorter reflection paths, the transmitter 1202 and / or the receiver 1204 may use a lower beam gain for the beam pair (e.g., by using a wider beam or a lower transmit power, etc.), and as shown at 1604, for targets with longer reflection paths, the transmitter 1202 and / or the receiver 1204 may use a higher beam gain for the beam pair (e.g., by using a narrower beam or a higher transmit power, etc.). In other words, the transmitter 1202 may change the Tx transmit power (P) of the Tx beam i in each beam pair. t,i ) / Tx gain (G t,i ), and / or the receiver 1204 may change the Rx gain (G r,i ) to keep the receiver power constant, so that etc.

[0112] In one example, combining Fig.16 Various aspects of the discussion may be implemented at the transmitter 1202 (rather than at the receiver 1204), where the transmitter 1202 may vary the Tx transmit power (P t ) and / or Tx beam gain (G t ), and the receiver 1204 can maintain the Rx beam gain (G r ) is fixed to keep the received power of a given beam pair constant. In another example, Fig.16 Various aspects discussed may be implemented at the receiver 1204 (rather than at the transmitter 1202), where the receiver 1204 may change the Rx beam gain (G r ), and the transmitter 1202 may maintain the Tx transmission power (P t ) and / or Tx beam gain (G t ) is fixed to keep the received power of a given beam pair constant. In another example, Fig.16 Various aspects discussed may be implemented at both the transmitter 1202 and the receiver 1204, where the transmitter 1202 may vary the Tx transmit power (Pt ) and / or Tx beam gain (G t ), and the receiver 1204 may change the Rx beam gain (G r ) keeps the received power of a given beam pair constant.

[0113] In another aspect of the present disclosure, in order for the receiver 1204 to constrain the Rx beam scanning direction and / or beam gain of the receiver, the receiver 1204 may be specified to obtain information related to the Tx beam used by the transmitter 1202. For example, the information related to the Tx beam may include a transmit-receive point (TRP) position, an antenna panel orientation, a Tx beam direction, a Tx beam gain, and / or a Tx transmit power of the transmitter 1202, etc.

[0114] In one example, the transmitter 1202 may calculate and indicate to the receiver 1204 the corresponding Rx beam direction and Rx beam gain paired with the Tx beam to be transmitted (or indexed). For example, based on the Tx beam used by the transmitter 1202, the transmitter may indicate to the receiver 1204 which Rx beam direction and / or Rx beam gain to use for a given beam pair. This configuration may reduce the calculations and processing specified at the receiver 1204. In some examples, the indication may be based on an index, where different indices may be associated with different Rx beam directions / gains. Therefore, the transmitter 1202 may use the corresponding index to indicate the Rx beam direction / gain to reduce signaling overhead.

[0115] In another example, the transmitter 1202 may indicate to the receiver 1204 information related to the Tx beam used by the transmitter 1202 (e.g., TRP position, antenna panel orientation, Tx beam direction, Tx beam gain, Tx transmit power, etc.). The receiver 1204 may then determine a corresponding Rx beam direction and / or Rx beam to pair with the Tx beam. This configuration may enable the receiver 1204 to have more flexibility in configuring the Rx beam of the receiver.

[0116] In another example, the scan plan with paired Tx and Rx beams and their related parameters (e.g., Tx power, Tx / Rx gain, etc.) may be known to both the transmitter 1202 and the receiver 1204. Therefore, the transmitter 1202 may inform the receiver 1204 which scan plan to apply, such as by indicating a corresponding scan plan index.

[0117] Fig.171700 is an example of a receiver constraining an Rx beam direction / gain based on a partition according to various aspects of the present disclosure. In another aspect of the present disclosure, the area to be sensed (which may be referred to as a "sensing area") may be divided into several partitions, and the partitions may be marked by different indexes. In order to constrain the Rx beam direction and / or Rx beam gain, the transmitter 1202 may indicate one or more partition indexes to the receiver 1204 to perform RF sensing. Then, the transmitter 1202 and the receiver 1204 may perform Tx and Rx beam scanning in the corresponding partitions. For example, as shown at 1702, the transmitter 1202 may indicate the index corresponding to the sensing partition #i to the receiver 1204, and then, the transmitter 1202 and the receiver 1204 may perform Tx beam scanning and Rx beam scanning, respectively, within the sensing partition #i. For each sector, since the direction and gain of the Tx and Rx beams can be constrained by the location of the sector, the power and time consumed by beam scanning can be reduced at both the transmitter 1202 and the receiver 1204, thereby improving the efficiency of bistatic / multistatic sensing.

[0118] In one example, the transmitter 1202 may plan / configure a Tx beam scanning order and indicate the beam scanning order to the receiver 1204 (e.g., for Tx-Rx synchronization). Then, the transmitter 1202 and the receiver 1204 may perform Tx / Rx beam scanning together on the corresponding partition based on the order. For example, the transmitter 1202 may indicate to the receiver 1204 that the receiver will perform Tx beam scanning for sensing partitions #i to #i+N for certain durations. Then, based on the indication, the receiver 1204 may perform Rx beam scanning for sensing partitions #i to #i+N for the same duration. In another example, the transmitter 1202 may indicate the partition index to the receiver 1204 before each sensing of the corresponding partition (e.g., indicating one partition to the receiver 1204 each time).

[0119] Fig.18 1800 is a flow chart of a method of wireless communication / RF sensing. The method may be performed by a receiving entity (e.g., UE 104, 404; base station 102; receiver 1004, 1204; device 2004; network entity 2002, 2102; CU 2202). The method may enable the receiving entity to improve the performance and accuracy of bistatic / multistatic RF sensing by constraining the receiving entity's Rx beam scanning on a specific beam direction and / or beam gain, thereby reducing Rx beam scanning time and power.

[0120] At 1802, the receiving entity may configure the receiving entity to perform Rx beam scanning constrained based on at least one of a Tx beam direction, Tx power, Tx beam gain, or Tx beam path loss of a Tx beam from a transmitting entity or based on a predicted location of a target, such as in conjunction with Fig. 12A , Fig. 12B as well as Figures 13 to 17 For example, Fig. 12A As shown in FIG. 1200A, the receiver 1204 may constrain the Rx beam scanning direction of the receiver based on the maximum transmit power of the Tx beam from the transmitter 1202. Fig.15 As shown in diagram 1500 of FIG. 1504 , the receiver 1204 may constrain the Rx beam direction of the receiver based on the predicted position of the target 1504. Fig.16 As shown in diagram 1600 of FIG. 16 , the receiver 1204 may constrain the Rx beam gain of the receiver based on the Tx beam gain / Tx power of the Tx beam from the transmitter 1202. The configuration of the Rx beam scanning may be performed by, for example Fig. 20 The beam scanning constraint configuration component 198 of the device 2004 and / or Figure 20 to Figure 21 The beam scanning constraint configuration component 199 of the network entity 2002 / 2102 is executed.

[0121] At 1804, the receiving entity may perform Rx beam scanning on at least one of a set of Rx beam directions or a set of Rx beam gains constrained by at least one of a Tx beam direction, Tx power, Tx beam gain, or Tx beam path loss of a Tx beam from a transmitting entity or constrained by a predicted position of a target, such as in conjunction with Fig. 12A , Fig. 12B as well as Figures 13 to 17 For example, Fig. 12A As shown in diagram 1200A of FIG. 1200A , the receiver 1204 may perform Rx beam scanning in an Rx beam direction constrained based on the maximum transmission power of the Tx beam from the transmitter 1202. Fig.15 As shown in diagram 1500 of FIG. 1504 , the receiver 1204 may perform Rx beam scanning under an Rx beam direction constrained based on the predicted position of the target 1504. Fig.16 As shown in diagram 1600 of FIG. 16A , the receiver 1204 may perform Rx beam scanning at an Rx beam gain constrained based on Tx beam gain / Tx power of a Tx beam from the transmitter 1202. The Rx beam scanning may be performed by, for example, Fig. 20 The beam scanning constraint configuration component 198 and / or the transceiver 2022 of the device 2004 and / or Figure 20 to Figure 21 The beam scanning constraint configuration component 199 and / or the transceiver 2146 of the network entity 2002 / 2102 is executed.

[0122] In one example, the Rx beam scan may be performed on a set of Rx beam directions constrained by at least one of a Tx beam direction, a Tx power, or a Tx beam path loss of a Tx beam from a transmitting entity or by a predicted position of a target, and the set of Rx beam directions may include a plurality of Rx beam directions between a start angle and a stop angle relative to the receiving entity, the start angle being toward the transmitting entity, such as in combination with Fig. 12A and Fig. 12B In this example, the stop angle may be toward a maximum transmission range of a Tx beam from a transmitting entity. In this example, the maximum transmission range of a Tx beam from a transmitting entity may be based on at least one of a Tx power from the transmitting entity, a Tx beam gain, a Tx beam path loss of the Tx beam, a Tx antenna gain, a Tx signal carrier frequency, or a wireless channel coefficient.

[0123] In another example, if combined with Fig.13 As described, the stopping angle may be based on the RSRP of the Tx beam from the transmitting entity being less than an RSRP threshold.

[0124] In another example, as shown at 1806 and in conjunction with Fig.14 As described, the receiving entity may perform a first Rx beam scanning set based on a first beam width, a first beam step angle, and a first Rx beam gain when the RSRP of the Tx beam is less than or equal to an RSRP threshold, and the receiving entity may perform a second Rx beam scanning set based on a second beam width, a second beam step angle, and a second Rx beam gain when the RSRP of the Tx beam is greater than the RSRP threshold, wherein the second beam step angle is smaller than the first beam step angle, the second beam width is smaller than the first beam width, and the second Rx beam gain is greater than the first Rx beam gain.

[0125] In another example, if combined with Fig.16 As described, Rx beam scanning may be performed based on a fixed Rx beam gain set. Alternatively, Rx beam scanning may be performed based on an Rx beam gain set constrained based on a Tx beam path loss, wherein each Rx beam gain in the Rx beam gain set may be proportional to the Tx beam path loss. In another example, Rx beam scanning may be performed based on an Rx beam gain set further constrained based on Tx power and Tx beam gain.

[0126] In another example, as shown at 1808, the receiving entity may receive information indicating at least one of a set of Rx beam directions or a set of Rx beam gains for receiving a Tx beam from the transmitting entity, wherein Rx beam scanning may be performed based on the received information.

[0127] In another example, as shown at 1810, the receiving entity may receive information indicating at least one of a Tx beam direction, Tx power, or Tx beam gain of a Tx beam from a transmitting entity, and the receiving entity may determine at least one of an Rx beam direction set or an Rx beam gain set based on the received information.

[0128] In another example, as shown at 1812, the receiving entity may receive a scan planning index indicating at least one of a Tx beam direction, Tx power, or Tx beam gain of a Tx beam from a transmitting entity, or at least one of a set of Rx beam directions or a set of Rx beam gains for receiving a Tx beam from the transmitting entity, wherein the Rx beam scanning may be performed based on the received scan planning index.

[0129] In another example, as shown at 1814 and in conjunction with Fig.17 As described, a receiving entity may receive a partition index indicating a partition in a partition set for performing Rx beam scanning, and the receiving entity may determine at least one of an Rx beam direction set or an Rx beam gain set based on the received partition index. Alternatively, the receiving entity may receive a partition index set indicating a partition set for performing Rx beam scanning for a partition set in a specific order, and the receiving entity may determine at least one of an Rx beam direction set or an Rx beam gain set based on the partition index for each partition index in the partition index set, wherein the Rx beam scanning may be performed in each partition in the partition set.

[0130] In another example, as shown at 1816 and in conjunction with Fig.15 As described, when a target is detected, the receiving entity may measure the heading and velocity of the target, and the receiving entity may predict the position of the target based on the heading and velocity of the target, wherein Rx beam scanning may be performed on a set of Rx beam directions constrained by the predicted position of the target.

[0131] Fig.19 1900 is a flow chart of a method of wireless communication / RF sensing. The method may be performed by a receiving entity (e.g., UE 104, 404; base station 102; receiver 1004, 1204; device 2004; network entity 2002, 2102; CU 2202). The method may enable the receiving entity to improve the performance and accuracy of bistatic / multistatic RF sensing by constraining the receiving entity's Rx beam scanning on a specific beam direction and / or beam gain, thereby reducing Rx beam scanning time and power.

[0132] At 1902, the receiving entity may configure the receiving entity to perform Rx beam scanning constrained based on at least one of a Tx beam direction, Tx power, Tx beam gain, or Tx beam path loss of a Tx beam from a transmitting entity or based on a predicted location of a target, such as in conjunction with Fig. 12A , Fig. 12B as well as Figures 13 to 17 For example, Fig. 12A As shown in FIG. 1200A, the receiver 1204 may constrain the Rx beam scanning direction of the receiver based on the maximum transmit power of the Tx beam from the transmitter 1202. Fig.15 As shown in diagram 1500 of FIG. 1504 , the receiver 1204 may constrain the Rx beam direction of the receiver based on the predicted position of the target 1504. Fig.16 As shown in diagram 1600 of FIG. 16 , the receiver 1204 may constrain the Rx beam gain of the receiver based on the Tx beam gain / Tx power of the Tx beam from the transmitter 1202. The configuration of the Rx beam scanning may be performed by, for example Fig. 20 The beam scanning constraint configuration component 198 of the device 2004 and / or Figure 20 to Figure 21 The beam scanning constraint configuration component 199 of the network entity 2002 / 2102 is executed.

[0133] At 1904, the receiving entity may perform Rx beam scanning on at least one of a set of Rx beam directions or a set of Rx beam gains constrained by at least one of a Tx beam direction, Tx power, Tx beam gain, or Tx beam path loss of a Tx beam from a transmitting entity or constrained by a predicted position of a target, such as in conjunction with Fig. 12A , Fig. 12B as well as Figures 13 to 17 For example, Fig. 12A As shown in diagram 1200A of FIG. 1200A , the receiver 1204 may perform Rx beam scanning in an Rx beam direction constrained based on the maximum transmission power of the Tx beam from the transmitter 1202. Fig.15 As shown in diagram 1500 of FIG. 1504 , the receiver 1204 may perform Rx beam scanning under an Rx beam direction constrained based on the predicted position of the target 1504. Fig.16 As shown in diagram 1600 of FIG. 16A , the receiver 1204 may perform Rx beam scanning at an Rx beam gain constrained based on Tx beam gain / Tx power of a Tx beam from the transmitter 1202. The Rx beam scanning may be performed by, for example, Fig. 20 The beam scanning constraint configuration component 198 and / or the transceiver 2022 of the device 2004 and / or Figure 20 to Figure 21 The beam scanning constraint configuration component 199 and / or the transceiver 2146 of the network entity 2002 / 2102 is executed.

[0134] In one example, the Rx beam scan may be performed on a set of Rx beam directions constrained by at least one of a Tx beam direction, a Tx power, or a Tx beam path loss of a Tx beam from a transmitting entity, and the set of Rx beam directions may include a plurality of Rx beam directions between a start angle and a stop angle relative to the receiving entity, the start angle being toward the transmitting entity, such as in combination with Fig. 12A and Fig. 12B In this example, the stop angle may be toward a maximum transmission range of a Tx beam from a transmitting entity. In this example, the maximum transmission range of a Tx beam from a transmitting entity may be based on at least one of a Tx power from the transmitting entity, a Tx beam gain, a Tx beam path loss of the Tx beam, a Tx antenna gain, a Tx signal carrier frequency, or a wireless channel coefficient.

[0135] In another example, if combined with Fig.13 As described, the stopping angle may be based on the RSRP of the Tx beam from the transmitting entity being less than an RSRP threshold.

[0136] In another example, if combined with Fig.14 As described, the receiving entity may perform a first Rx beam scanning set based on a first beam width, a first beam step angle, and a first Rx beam gain when the RSRP of the Tx beam is less than or equal to an RSRP threshold, and the receiving entity may perform a second Rx beam scanning set based on a second beam width, a second beam step angle, and a second Rx beam gain when the RSRP of the Tx beam is greater than the RSRP threshold, wherein the second beam step angle is smaller than the first beam step angle, the second beam width is smaller than the first beam width, and the second Rx beam gain is greater than the first Rx beam gain.

[0137] In another example, if combined with Fig.16 As described, Rx beam scanning may be performed based on a fixed Rx beam gain set. Alternatively, Rx beam scanning may be performed based on an Rx beam gain set constrained based on a Tx beam path loss, wherein each Rx beam gain in the Rx beam gain set may be proportional to the Tx beam path loss. In another example, Rx beam scanning may be performed based on an Rx beam gain set further constrained based on Tx power and Tx beam gain.

[0138] In another example, the receiving entity may receive information indicating at least one of an Rx beam direction set or an Rx beam gain set for receiving a Tx beam from the transmitting entity, wherein the Rx beam scanning may be performed based on the received information.

[0139] In another example, the receiving entity may receive information indicating at least one of a Tx beam direction, Tx power, or Tx beam gain of a Tx beam from a transmitting entity, and the receiving entity may determine at least one of an Rx beam direction set or an Rx beam gain set based on the received information.

[0140] In another example, the receiving entity may receive a scan planning index indicating at least one of a Tx beam direction, Tx power, or Tx beam gain of a Tx beam from a transmitting entity, or at least one of a set of Rx beam directions or a set of Rx beam gains for receiving a Tx beam from the transmitting entity, wherein the Rx beam scanning may be performed based on the received scan planning index.

[0141] In another example, in combination with Fig.17 As described, a receiving entity may receive a partition index indicating a partition in a partition set for performing Rx beam scanning, and the receiving entity may determine at least one of an Rx beam direction set or an Rx beam gain set based on the received partition index. Alternatively, the receiving entity may receive a partition index set indicating a partition set for performing Rx beam scanning for a partition set in a specific order, and the receiving entity may determine at least one of an Rx beam direction set or an Rx beam gain set based on the partition index for each partition index in the partition index set, wherein the Rx beam scanning may be performed in each partition in the partition set.

[0142] In another example, if combined with Fig.15 As described, when a target is detected, the receiving entity may measure the heading and velocity of the target, and the receiving entity may predict the position of the target based on the heading and velocity of the target, wherein Rx beam scanning may be performed on a set of Rx beam directions constrained by the predicted position of the target.

[0143] Fig. 202000 is a diagram illustrating an example of a hardware implementation for an apparatus 2004. The apparatus 2004 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 2004 may include a cellular baseband processor 2024 (also referred to as a modem) coupled to one or more transceivers 2022 (e.g., a cellular RF transceiver). The cellular baseband processor 2024 may include on-chip memory 2024'. In some aspects, the apparatus 2004 may also include one or more subscriber identity module (SIM) cards 2020 and an application processor 2006 coupled to a secure digital (SD) card 2008 and a screen 2010. The application processor 2006 may include on-chip memory 2006'. In some aspects, the device 2004 may also include a Bluetooth module 2012, a WLAN module 2014, an SPS module 2016 (e.g., a GNSS module), one or more sensor modules 2018 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial management unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-aided detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 2026, a power source 2030, and / or a camera 2032. The Bluetooth module 2012, the WLAN module 2014, and the SPS module 2016 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). The Bluetooth module 2012, the WLAN module 2014, and the SPS module 2016 may include their own dedicated antennas and / or communicate using antennas 2080. The cellular baseband processor 2024 communicates with the UE 104 and / or with the RU associated with the network entity 2002 through the transceiver 2022 via one or more antennas 2080. The cellular baseband processor 2024 and the application processor 2006 may each include a computer-readable medium / memory 2024', 2006', respectively. The additional memory module 2026 may also be considered as a computer-readable medium / memory. Each computer-readable medium / memory 2024', 2006', additional memory module 2026 may be non-transitory. The cellular baseband processor 2024 and the application processor 2006 are each responsible for general processing, including executing software stored on a computer-readable medium / memory. The software, when executed by the cellular baseband processor 2024 / application processor 2006, enables the cellular baseband processor 2024 / application processor 2006 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor 2024 / application processor 2006 when executing the software.In some examples, the cellular baseband processor 2024 / application processor 2006 may be a component of the UE 350 and may include the memory 360 and / or at least one of the following: the TX processor 368, the RX processor 356, and the controller / processor 359. In other examples, the cellular baseband processor 2024 / application processor 2006 may be a component of the base station and may include the TX processor 316, the RX processor 370, and the controller / processor 375. In one configuration, the device 2004 may be a processor chip (modem and / or application) and only include the cellular baseband processor 2024 and / or the application processor 2006, and in another configuration, the device 2004 may be the entire UE (e.g., see. Figure 3 350) and includes additional modules of device 2004.

[0144] As discussed above, the beam scanning constraint configuration component 198 is configured to configure the receiving entity to perform Rx beam scanning constrained based on at least one of the Tx beam direction, Tx power, Tx beam gain, or Tx beam path loss of the Tx beam from the transmitting entity or based on the predicted location of the target; and perform Rx beam scanning on at least one of the Rx beam direction set or Rx beam gain set constrained by at least one of the Tx beam direction, Tx power, Tx beam gain, or Tx beam path loss of the Tx beam from the transmitting entity or constrained by the predicted location of the target. The beam scanning constraint configuration component 198 may be within the cellular baseband processor 2024, the application processor 2006, or both the cellular baseband processor 2024 and the application processor 2006. The beam scanning constraint configuration component 198 can be one or more hardware components that are specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to perform the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. As shown, the device 2004 may include a variety of components configured for various functions. In one configuration, the device 2004, and specifically the cellular baseband processor 2024 and / or the application processor 2006, includes a component for configuring the receiving entity to perform Rx beam scanning constrained based on at least one of the Tx beam direction, Tx power, Tx beam gain, or Tx beam path loss of the Tx beam from the transmitting entity or based on a predicted position of a target; and a component for performing Rx beam scanning on at least one of a set of Rx beam directions or a set of Rx beam gains constrained by at least one of the Tx beam direction, Tx power, Tx beam gain, or Tx beam path loss of the Tx beam from the transmitting entity or by a predicted position of the target.

[0145] In another configuration, the Rx beam scanning is performed on a set of Rx beam directions constrained by at least one of a Tx beam direction, a Tx power, or a Tx beam path loss of a Tx beam from a transmitting entity, and wherein the set of Rx beam directions includes a plurality of Rx beam directions between a start angle and a stop angle relative to a receiving entity, the start angle being toward the transmitting entity. In this configuration, the stop angle is toward a maximum transmission range of the Tx beam from the transmitting entity. In this configuration, the maximum transmission range of the Tx beam from the transmitting entity is based on at least one of a Tx power from the transmitting entity, a Tx beam gain, a Tx beam path loss of the Tx beam, a Tx antenna gain, a Tx signal carrier frequency, or a wireless channel coefficient.

[0146] In another configuration, the stopping angle is based on an RSRP of a Tx beam from the transmitting entity being less than an RSRP threshold.

[0147] In another configuration, the component for performing Rx beam scanning also includes configuring the device 2004 to: when the RSRP of the Tx beam is less than or equal to the RSRP threshold, perform a first Rx beam scanning set based on the first beam width, the first beam step angle and the first Rx beam gain; and when the RSRP of the Tx beam is greater than the RSRP threshold, perform a second Rx beam scanning set based on the second beam width, the second beam step angle and the second Rx beam gain, the second beam step angle being smaller than the first beam step angle, the second beam width being smaller than the first beam width, and the second Rx beam gain being greater than the first Rx beam gain.

[0148] In another configuration, Rx beam scanning is performed based on a fixed set of Rx beam gains.

[0149] In another configuration, Rx beam scanning is performed based on an Rx beam gain set constrained based on Tx beam path loss. In this configuration, each Rx beam gain in the Rx beam gain set is proportional to the Tx beam path loss. Alternatively, Rx beam scanning is performed based on an Rx beam gain set further constrained based on Tx power and Tx beam gain.

[0150] In another configuration, the apparatus 2004 further includes means for receiving information indicating at least one of a set of Rx beam directions or a set of Rx beam gains for receiving a Tx beam from a transmitting entity, wherein the Rx beam scanning is performed based on the received information.

[0151] In another configuration, the apparatus 2004 further includes means for receiving information indicating at least one of a Tx beam direction, a Tx power, or a Tx beam gain of a Tx beam from the transmitting entity.

[0152] In another configuration, the apparatus 2004 further includes means for determining at least one of a set of Rx beam directions or a set of Rx beam gains based on the received information.

[0153] In another configuration, the device 2004 also includes a component for receiving a scan planning index indicating at least one of a Tx beam direction, Tx power, or Tx beam gain of a Tx beam from a transmitting entity, or for receiving at least one of a set of Rx beam directions or a set of Rx beam gains of a Tx beam from a transmitting entity, wherein the Rx beam scanning is performed based on the received scan planning index.

[0154] In another configuration, the apparatus 2004 further includes means for receiving a set of partition indexes indicating a set of partitions for performing Rx beam scanning for the set of partitions in a specific order.

[0155] In another configuration, the apparatus 2004 further includes means for determining, for each partition index in the set of partition indexes, at least one of a set of Rx beam directions or a set of Rx beam gains based on the partition index, wherein the Rx beam scanning is performed in each partition in the set of partition indexes.

[0156] In another configuration, the apparatus 2004 further includes means for receiving a partition index indicating a partition in the set of partitions for performing Rx beam scanning.

[0157] In another configuration, the apparatus 2004 further includes means for determining at least one of a set of Rx beam directions or a set of Rx beam gains based on the received partition index.

[0158] In another configuration, Rx beam scanning is performed to obtain bistatic sensing.

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

[0160] Fig.212100 is a diagram illustrating an example of a hardware implementation for a network entity 2102. The network entity 2102 may be a BS, a component of a BS, or may implement BS functionality. The network entity 2102 may include at least one of a CU 2110, a DU 2130, or a RU 2140. For example, depending on the layer functionality handled by the beam scanning constraint configuration component 199, the network entity 2102 may include a CU 2110; both a CU 2110 and a DU 2130; each of the CU 2110, the DU 2130, and the RU 2140; the DU 2130; both a DU 2130 and a RU 2140; or a RU 2140. The CU 2110 may include a CU processor 2112. The CU processor 2112 may include an on-chip memory 2112'. In some aspects, the CU 2110 may also include an additional memory module 2114 and a communication interface 2118. CU 2110 communicates with DU 2130 via a midhaul link, such as an F1 interface. DU 2130 may include a DU processor 2132. DU processor 2132 may include on-chip memory 2132'. In some aspects, DU 2130 may also include an additional memory module 2134 and a communication interface 2138. DU 2130 communicates with RU 2140 via a fronthaul link. RU 2140 may include a RU processor 2142. RU processor 2142 may include on-chip memory 2142'. In some aspects, RU 2140 may also include an additional memory module 2144, one or more transceivers 2146, an antenna 2180, and a communication interface 2148. RU 2140 communicates with UE 104. On-chip memory 2112', 2132', 2142' and additional memory modules 2114, 2134, 2144 may each be considered a computer-readable medium / memory. Each computer readable medium / memory may be non-transitory. Each of the processors 2112, 2132, 2142 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 may also be used to store data manipulated by the processor when executing the software.

[0161] As discussed above, the beam scanning constraint configuration component 199 is configured to configure the receiving entity to perform Rx beam scanning constrained based on at least one of the Tx beam direction, Tx power, Tx beam gain, or Tx beam path loss of the Tx beam from the transmitting entity or based on the predicted location of the target; and perform Rx beam scanning on at least one of the Rx beam direction set or Rx beam gain set constrained by at least one of the Tx beam direction, Tx power, Tx beam gain, or Tx beam path loss of the Tx beam from the transmitting entity or constrained by the predicted location of the target. The beam scanning constraint configuration component 199 may be within one or more processors of one or more of the CU 2110, the DU 2130, and the RU 2140. The beam scanning constraint configuration component 199 may be one or more hardware components specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to perform the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. The network entity 2102 may include a variety of components configured for various functions. In one configuration, the network entity 2102 includes a component for configuring the receiving entity to perform Rx beam scanning constrained based on at least one of the Tx beam direction, Tx power, Tx beam gain, or Tx beam path loss of the Tx beam from the transmitting entity or based on the predicted location of the target; and a component for performing Rx beam scanning on at least one of a set of Rx beam directions or a set of Rx beam gains constrained by at least one of the Tx beam direction, Tx power, Tx beam gain, or Tx beam path loss of the Tx beam from the transmitting entity or by the predicted location of the target.

[0162] In another configuration, the Rx beam scanning is performed on a set of Rx beam directions constrained by at least one of a Tx beam direction, a Tx power, or a Tx beam path loss of a Tx beam from a transmitting entity, and wherein the set of Rx beam directions includes a plurality of Rx beam directions between a start angle and a stop angle relative to a receiving entity, the start angle being toward the transmitting entity. In this configuration, the stop angle is toward a maximum transmission range of the Tx beam from the transmitting entity. In this configuration, the maximum transmission range of the Tx beam from the transmitting entity is based on at least one of a Tx power from the transmitting entity, a Tx beam gain, a Tx beam path loss of the Tx beam, a Tx antenna gain, a Tx signal carrier frequency, or a wireless channel coefficient.

[0163] In another configuration, the stopping angle is based on an RSRP of a Tx beam from the transmitting entity being less than an RSRP threshold.

[0164] In another configuration, the component for performing Rx beam scanning also includes configuring the network entity 2102 to: when the RSRP of the Tx beam is less than or equal to the RSRP threshold, perform a first Rx beam scanning set based on a first beam width, a first beam step angle and a first Rx beam gain; and when the RSRP of the Tx beam is greater than the RSRP threshold, perform a second Rx beam scanning set based on a second beam width, a second beam step angle and a second Rx beam gain, wherein the second beam step angle is smaller than the first beam step angle, the second beam width is smaller than the first beam width, and the second Rx beam gain is greater than the first Rx beam gain.

[0165] In another configuration, Rx beam scanning is performed based on a fixed set of Rx beam gains.

[0166] In another configuration, Rx beam scanning is performed based on an Rx beam gain set constrained based on Tx beam path loss. In this configuration, each Rx beam gain in the Rx beam gain set is proportional to the Tx beam path loss. Alternatively, Rx beam scanning is performed based on an Rx beam gain set further constrained based on Tx power and Tx beam gain.

[0167] In another configuration, the network entity 2102 further includes means for receiving information indicating at least one of a set of Rx beam directions or a set of Rx beam gains for receiving a Tx beam from the transmitting entity, wherein the Rx beam scanning is performed based on the received information.

[0168] In another configuration, the network entity 2102 further includes means for receiving information indicating at least one of a Tx beam direction, a Tx power, or a Tx beam gain of a Tx beam from the transmitting entity.

[0169] In another configuration, the network entity 2102 further includes means for determining at least one of a set of Rx beam directions or a set of Rx beam gains based on the received information.

[0170] In another configuration, the network entity 2102 also includes a component for receiving a scan planning index indicating at least one of a Tx beam direction, Tx power, or Tx beam gain of a Tx beam from a transmitting entity, or for receiving at least one of a set of Rx beam directions or a set of Rx beam gains of a Tx beam from the transmitting entity, wherein the Rx beam scanning is performed based on the received scan planning index.

[0171] In another configuration, the network entity 2102 further includes means for receiving a set of partition indexes indicating a set of partitions for performing Rx beam scanning for the set of partitions in a specific order.

[0172] In another configuration, the network entity 2102 further includes means for determining at least one of a set of Rx beam directions or a set of Rx beam gains based on the partition index for each partition index in the set of partition indexes, wherein Rx beam scanning is performed in each partition in the set of partition indexes.

[0173] In another configuration, the network entity 2102 further includes means for receiving a partition index indicating a partition in the set of partitions for performing Rx beam scanning.

[0174] In another configuration, the network entity 2102 further includes means for determining at least one of a set of Rx beam directions or a set of Rx beam gains based on the received partition index.

[0175] In another configuration, Rx beam scanning is performed to obtain bistatic sensing.

[0176] The means may be the beam scanning constraint configuration component 199 of the network entity 2102 configured to perform the functions recited by the means. As described above, the network entity 2102 may include the TX processor 316, the RX processor 370, and the controller / processor 375. Thus, in one configuration, the means may be the TX processor 316, the RX processor 370, and / or the controller / processor 375 configured to perform the functions recited by the means.

[0177] Fig. 22 2200 is an example of a hardware implementation for a network entity 2260. In one example, the network entity 2260 may be within the core network 120. The network entity 2260 may include a network processor 2212. The network processor 2212 may include an on-chip memory 2212'. In some aspects, the network entity 2260 may also include an additional memory module 2214. The network entity 2260 communicates with the CU 2202 directly (e.g., a backhaul link) or indirectly (e.g., through the RIC) via a network interface 2280. The on-chip memory 2212' and the additional memory module 2214 may each be considered a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. The processor 2212 is responsible for general processing, including executing software stored on a computer-readable medium / memory. The software, when executed by the corresponding processor, enables the processor to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the processor when executing the software.

[0178] As discussed above, component 2204 is configured to configure the receiving entity to perform Rx beam scanning constrained based on at least one of the Tx beam direction, Tx power, Tx beam gain, or Tx beam path loss of the Tx beam from the transmitting entity or based on the predicted location of the target; and perform Rx beam scanning on at least one of the Rx beam direction set or Rx beam gain set constrained by at least one of the Tx beam direction, Tx power, Tx beam gain, or Tx beam path loss of the Tx beam from the transmitting entity or constrained by the predicted location of the target. Component 2204 may be within processor 2212. Component 2204 may be one or more hardware components specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to perform the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. Network entity 2260 may include a variety of components configured for various functions. In one configuration, the network entity 2260 includes a component for configuring the receiving entity to perform Rx beam scanning constrained based on at least one of the Tx beam direction, Tx power, Tx beam gain, or Tx beam path loss of the Tx beam from the transmitting entity or based on a predicted position of a target; and a component for performing Rx beam scanning on at least one of a set of Rx beam directions or a set of Rx beam gains constrained by at least one of the Tx beam direction, Tx power, Tx beam gain, or Tx beam path loss of the Tx beam from the transmitting entity or by a predicted position of the target.

[0179] In another configuration, the Rx beam scanning is performed on a set of Rx beam directions constrained by at least one of a Tx beam direction, a Tx power, or a Tx beam path loss of a Tx beam from a transmitting entity, and wherein the set of Rx beam directions includes a plurality of Rx beam directions between a start angle and a stop angle relative to a receiving entity, the start angle being toward the transmitting entity. In this configuration, the stop angle is toward a maximum transmission range of the Tx beam from the transmitting entity. In this configuration, the maximum transmission range of the Tx beam from the transmitting entity is based on at least one of a Tx power from the transmitting entity, a Tx beam gain, a Tx beam path loss of the Tx beam, a Tx antenna gain, a Tx signal carrier frequency, or a wireless channel coefficient.

[0180] In another configuration, the stopping angle is based on an RSRP of a Tx beam from the transmitting entity being less than an RSRP threshold.

[0181] In another configuration, the component for performing Rx beam scanning also includes configuring the network entity 2260 to: when the RSRP of the Tx beam is less than or equal to the RSRP threshold, perform a first Rx beam scanning set based on a first beam width, a first beam step angle and a first Rx beam gain; and when the RSRP of the Tx beam is greater than the RSRP threshold, perform a second Rx beam scanning set based on a second beam width, a second beam step angle and a second Rx beam gain, wherein the second beam step angle is smaller than the first beam step angle, the second beam width is smaller than the first beam width, and the second Rx beam gain is greater than the first Rx beam gain.

[0182] In another configuration, Rx beam scanning is performed based on a fixed set of Rx beam gains.

[0183] In another configuration, Rx beam scanning is performed based on an Rx beam gain set constrained based on Tx beam path loss. In this configuration, each Rx beam gain in the Rx beam gain set is proportional to the Tx beam path loss. Alternatively, Rx beam scanning is performed based on an Rx beam gain set further constrained based on Tx power and Tx beam gain.

[0184] In another configuration, the network entity 2260 further includes means for receiving information indicating at least one of a set of Rx beam directions or a set of Rx beam gains for receiving a Tx beam from the transmitting entity, wherein the Rx beam scanning is performed based on the received information.

[0185] In another configuration, the network entity 2260 further includes means for receiving information indicating at least one of a Tx beam direction, a Tx power, or a Tx beam gain of a Tx beam from the transmitting entity.

[0186] In another configuration, the network entity 2260 also includes means for determining at least one of a set of Rx beam directions or a set of Rx beam gains based on the received information.

[0187] In another configuration, the network entity 2260 also includes a component for receiving a scan planning index indicating at least one of a Tx beam direction, Tx power, or Tx beam gain of a Tx beam from a transmitting entity, or for receiving at least one of a set of Rx beam directions or a set of Rx beam gains of a Tx beam from the transmitting entity, wherein the Rx beam scanning is performed based on the received scan planning index.

[0188] In another configuration, the network entity 2260 further includes means for receiving a set of partition indexes indicating a set of partitions for performing Rx beam scanning for the set of partitions in a specific order.

[0189] In another configuration, the network entity 2260 further includes means for determining at least one of a set of Rx beam directions or a set of Rx beam gains based on the partition index for each partition index in the set of partition indexes, wherein Rx beam scanning is performed in each partition in the set of partition indexes.

[0190] In another configuration, the network entity 2260 further includes means for receiving a partition index indicating a partition in the set of partitions for performing Rx beam scanning.

[0191] In another configuration, the network entity 2260 further includes means for determining at least one of a set of Rx beam directions or a set of Rx beam gains based on the received partition index.

[0192] In another configuration, Rx beam scanning is performed to obtain bistatic sensing.

[0193] A means may be a component 2204 of the network entity 2260 configured to perform the functions recited by the means.

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

[0195] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not limited to the various aspects described herein, but should be given the full scope consistent with the language claims. Unless otherwise specified, reference to an element in the singular form does not mean "one and only one", but "one or more". Terms such as "if", "when" and "while" do not mean a direct temporal relationship or reaction. That is, these phrases, such as "when ......", do not mean an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply imply that if the conditions are met, the action will occur, but no specific or immediate time limit is required for the occurrence of the action. The word "exemplary" is used herein to mean "used as an example, instance, or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having advantages over other aspects. Unless otherwise specified, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, wherein any such combination may contain one or more members of A, B, or C. A set should be interpreted as a set of elements, wherein the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If the first device receives data from the second device or sends data to the second device, data may be directly received / sent between the first device and the second device, or indirectly received / sent between the first device and the second device through a collection of devices. All structural and functional equivalents of the elements throughout the various aspects described in this disclosure that are known or will later be known to a person of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims. The words "module", "mechanism", "element", "device", etc. cannot replace the word "component". Therefore, no claim element will be understood as a component plus function unless the element is explicitly stated using the phrase "component for...".

[0196] As used herein, the phrase "based on" should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) should be interpreted as "based at least on A" unless specifically stated differently.

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

[0198] Aspect 1 is a method for performing wireless communication at a receiving entity, the method comprising: configuring the receiving entity to perform Rx beam scanning constrained based on at least one of the Tx beam direction, Tx power, Tx beam gain, or Tx beam path loss of a Tx beam from a transmitting entity or based on a predicted position of a target; and performing the Rx beam scanning on at least one of a set of Rx beam directions or a set of Rx beam gains constrained by at least one of the Tx beam direction, Tx power, Tx beam gain, or Tx beam path loss of the Tx beam from the transmitting entity or by the predicted position of the target.

[0199] Aspect 2 is a method according to Aspect 1, wherein the Rx beam scanning is performed on the Rx beam direction set constrained by the at least one of the Tx beam direction, the Tx power or the Tx beam path loss of the Tx beam from the transmitting entity, and wherein the Rx beam direction set includes multiple Rx beam directions between a start angle and a stop angle relative to the receiving entity, and the start angle is toward the transmitting entity.

[0200] Aspect 3 is a method according to aspect 2, wherein the stop angle is toward a maximum transmission range of the Tx beam from the transmitting entity.

[0201] Aspect 4 is a method according to Aspect 3, wherein the maximum transmission range of the Tx beam from the transmitting entity is based on at least one of the Tx power from the transmitting entity, Tx beam gain, the Tx beam path loss of the Tx beam, Tx antenna gain, Tx signal carrier frequency, or wireless channel coefficient.

[0202] Aspect 5 is a method according to aspect 2, wherein the stopping angle is based on an RSRP of the Tx beam from the transmitting entity being less than an RSRP threshold.

[0203] Aspect 6 is a method according to any one of Aspects 1 to 5, wherein performing the Rx beam scan includes: when the RSRP of the Tx beam is less than or equal to an RSRP threshold, performing a first Rx beam scan set based on a first beam width, a first beam step angle and a first Rx beam gain; and when the RSRP of the Tx beam is greater than the RSRP threshold, performing a second Rx beam scan set based on a second beam width, a second beam step angle and a second Rx beam gain, the second beam step angle being smaller than the first beam step angle, the second beam width being smaller than the first beam width, and the second Rx beam gain being greater than the first Rx beam gain.

[0204] Aspect 7 is a method according to any one of aspects 1 to 6, wherein the Rx beam scanning is performed based on a fixed set of the Rx beam gains.

[0205] Aspect 8 is a method according to any one of aspects 1 to 7, wherein the Rx beam scanning is performed based on the Rx beam gain set constrained based on the Tx beam path loss.

[0206] Aspect 9 is a method according to aspect 8, wherein each Rx beam gain in the Rx beam gain set is proportional to the Tx beam path loss.

[0207] Aspect 10 is the method according to aspect 8, wherein the Rx beam scanning is performed based on the Rx beam gain set further constrained based on the Tx power and the Tx beam gain.

[0208] Aspect 11 is a method according to any one of Aspects 1 to 10, the method further comprising: receiving information indicating at least one of the Rx beam direction set or the Rx beam gain set for receiving the Tx beam from the transmitting entity, wherein the Rx beam scanning is performed based on the received information.

[0209] Aspect 12 is a method according to any one of Aspects 1 to 11, the method further comprising: receiving information indicating at least one of the Tx beam direction, the Tx power or the Tx beam gain of the Tx beam from the transmitting entity; and determining the at least one of the Rx beam direction set or the Rx beam gain set based on the received information.

[0210] Aspect 13 is a method according to any one of Aspects 1 to 12, the method further comprising: receiving a scanning planning index indicating the Tx beam direction, the Tx power or the Tx beam gain of the Tx beam from the transmitting entity, or at least one of the Rx beam direction set or the Rx beam gain set for receiving the Tx beam from the transmitting entity, wherein the Rx beam scanning is performed based on the received scanning planning index.

[0211] Aspect 14 is a method according to any one of Aspects 1 to 13, the method further comprising: receiving a partition index set indicating the partition set for performing the Rx beam scan for the partition set in a specific order; and determining, for each partition index in the partition index set, at least one of the Rx beam direction set or the Rx beam gain set based on the partition index, wherein the Rx beam scan is performed in each partition in the partition set.

[0212] Aspect 15 is a method according to any one of Aspects 1 to 14, the method further comprising: receiving a partition index indicating a partition in a partition set for performing the Rx beam scan; and determining at least one of the Rx beam direction set or the Rx beam gain set based on the received partition index.

[0213] Aspect 16 is a method according to any one of aspects 1 to 15, wherein the Rx beam scanning is performed to obtain bistatic sensing.

[0214] Aspect 17 is a method according to any one of Aspects 1 to 16, the method further comprising: measuring the heading and speed of the target when the target is detected; and predicting the position of the target based on the heading and the speed of the target, wherein the Rx beam scanning is performed on the set of Rx beam directions constrained by the predicted position of the target.

[0215] Aspect 18 is an apparatus for wireless communication, wherein the apparatus is configured to implement any one of aspects 1 to 17.

[0216] Aspect 19 is an apparatus for wireless communication, the apparatus comprising means for implementing any one of aspects 1 to 17.

[0217] Aspect 20 is a computer-readable medium storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 1 to 17.

Claims

1. An apparatus for wireless communication at a receiving entity, the apparatus comprising: Memory; and at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor configured to: configuring the receiving entity to perform receive (Rx) beam scanning constrained based on at least one of a transmit (Tx) beam direction, a Tx power, a Tx beam gain, or a Tx beam path loss of a transmit (Tx) beam from a transmitting entity or based on a predicted location of a target; as well as The Rx beam scanning is performed on at least one of a set of Rx beam directions or a set of Rx beam gains constrained by the at least one of the Tx beam direction, the Tx power, the Tx beam gain, or the Tx beam path loss of the Tx beam from the transmitting entity or constrained by the predicted position of the target.

2. The apparatus according to claim 1, wherein the Rx beam scanning is performed on the Rx beam direction set constrained by the at least one of the Tx beam direction, the Tx power, or the Tx beam path loss of the Tx beam from the transmitting entity, and wherein the Rx beam direction set includes a plurality of Rx beam directions between a start angle and a stop angle relative to the receiving entity, the start angle being toward the transmitting entity. 3 . The apparatus according to claim 2 , wherein the stop angle is toward a maximum transmission range of the Tx beam from the transmitting entity.

4. The apparatus of claim 3, wherein the maximum transmission range of the Tx beam from the transmitting entity is based on at least one of the Tx power from the transmitting entity, a Tx beam gain, the Tx beam path loss of the Tx beam, a Tx antenna gain, a Tx signal carrier frequency, or a wireless channel coefficient.

5. The apparatus of claim 2, wherein the stopping angle is based on a reference signal received power (RSRP) of the Tx beam from the transmitting entity being less than an RSRP threshold.

6. The apparatus according to claim 1, wherein to perform the Rx beam scanning, the at least one processor is further configured to: When a reference signal received power (RSRP) of the Tx beam is less than or equal to an RSRP threshold, performing a first Rx beam scanning set based on a first beam width, a first beam step angle, and a first Rx beam gain; and When the RSRP of the Tx beam is greater than the RSRP threshold, a second Rx beam scanning set is performed based on a second beam width, a second beam step angle, and a second Rx beam gain, wherein the second beam step angle is smaller than the first beam step angle, the second beam width is smaller than the first beam width, and the second Rx beam gain is greater than the first Rx beam gain. The apparatus according to claim 1 , wherein the Rx beam scanning is performed based on a fixed set of the Rx beam gains. 8 . The apparatus according to claim 1 , wherein the Rx beam scanning is performed based on the Rx beam gain set constrained based on the Tx beam path loss. 9 . The apparatus according to claim 8 , wherein each Rx beam gain in the set of Rx beam gains is proportional to the Tx beam path loss. 10 . The apparatus of claim 8 , wherein the Rx beam scanning is performed based on the Rx beam gain set further constrained based on the Tx power and the Tx beam gain.

11. The apparatus according to claim 1, wherein the at least one processor is further configured to: receive information indicating at least one of the Rx beam direction set or the Rx beam gain set for receiving the Tx beam from the transmitting entity, wherein the Rx beam scanning is performed based on the received information.

12. The apparatus of claim 1, wherein the at least one processor is further configured to: receiving information indicating at least one of the Tx beam direction, the Tx power, or the Tx beam gain of the Tx beam from the transmitting entity; and The at least one of the Rx beam direction set or the Rx beam gain set is determined based on the received information.

13. The apparatus according to claim 1, wherein the at least one processor is further configured to: receive a scan planning index indicating the Tx beam direction, the Tx power, or the Tx beam gain of the Tx beam from the transmitting entity, or at least one of the Rx beam direction set or the Rx beam gain set for receiving the Tx beam from the transmitting entity, wherein the Rx beam scanning is performed based on the received scan planning index.

14. The apparatus of claim 1, wherein the at least one processor is further configured to: receiving a set of partition indexes indicating the partition sets for performing the Rx beam scanning for the partition sets in a specific order; and determining, for each partition index in the partition index set, the at least one of the Rx beam direction set or the Rx beam gain set based on the partition index, The Rx beam scanning is performed in each partition in the set of partitions.

15. The apparatus of claim 1, wherein the at least one processor is further configured to: receiving a partition index indicating a partition in a set of partitions for performing the Rx beam scanning; and The at least one of the Rx beam direction set or the Rx beam gain set is determined based on the received partition index.

16. The apparatus of claim 1, wherein the at least one processor is further configured to: In case the target is detected, measuring the heading and speed of the target; and predicting the position of the target based on the heading and the speed of the target, Wherein the Rx beam scanning is performed on the set of Rx beam directions constrained by the predicted position of the target.

17. A method of wireless communication at a receiving entity, the method comprising: configuring the receiving entity to perform receive (Rx) beam scanning constrained based on at least one of a transmit (Tx) beam direction, a Tx power, a Tx beam gain, or a Tx beam path loss of a transmit (Tx) beam from a transmitting entity or based on a predicted location of a target; as well as The Rx beam scanning is performed on at least one of a set of Rx beam directions or a set of Rx beam gains constrained by the at least one of the Tx beam direction, the Tx power, the Tx beam gain, or the Tx beam path loss of the Tx beam from the transmitting entity or constrained by the predicted position of the target.

18. The method of claim 17, wherein the Rx beam scanning is performed on the Rx beam direction set constrained by the at least one of the Tx beam direction, the Tx power, or the Tx beam path loss of the Tx beam from the transmitting entity, and wherein the Rx beam direction set includes a plurality of Rx beam directions between a start angle and a stop angle relative to the receiving entity, the start angle being toward the transmitting entity.

19. The method of claim 18, wherein the stop angle is toward a maximum transmission range of the Tx beam from the transmitting entity, or the stop angle is based on a reference signal received power (RSRP) of the Tx beam from the transmitting entity being less than an RSRP threshold.

20. The method of claim 17, wherein performing the Rx beam scanning comprises: When a reference signal received power (RSRP) of the Tx beam is less than or equal to an RSRP threshold, performing a first Rx beam scanning set based on a first beam width, a first beam step angle, and a first Rx beam gain; as well as When the RSRP of the Tx beam is greater than the RSRP threshold, a second Rx beam scanning set is performed based on a second beam width, a second beam step angle, and a second Rx beam gain, wherein the second beam step angle is smaller than the first beam step angle, the second beam width is smaller than the first beam width, and the second Rx beam gain is greater than the first Rx beam gain. 21 . The method of claim 17 , wherein the Rx beam scanning is performed based on the Rx beam gain set constrained based on the Tx beam path loss.

22. The method according to claim 21, wherein each Rx beam gain in the set of Rx beam gains is proportional to the Tx beam path loss. 23 . The method of claim 21 , wherein the Rx beam scanning is performed based on the Rx beam gain set further constrained based on the Tx power and the Tx beam gain.

24. The method according to claim 17, further comprising: Information indicating the at least one of the Rx beam direction set or the Rx beam gain set for receiving the Tx beam from the transmitting entity is received, wherein the Rx beam scanning is performed based on the received information.

25. The method of claim 17, further comprising: receiving information indicating at least one of the Tx beam direction, the Tx power, or the Tx beam gain of the Tx beam from the transmitting entity; as well as The at least one of the Rx beam direction set or the Rx beam gain set is determined based on the received information.

26. The method of claim 17, further comprising: Receive a scan planning index indicating the Tx beam direction, the Tx power or the Tx beam gain of the Tx beam from the transmitting entity, or at least one of the Rx beam direction set or the Rx beam gain set for receiving the Tx beam from the transmitting entity, wherein the Rx beam scanning is performed based on the received scan planning index.

27. The method of claim 17, further comprising: receiving a set of partition indexes indicating the set of partitions for performing the Rx beam scanning for the set of partitions in a specific order; as well as determining, for each partition index in the partition index set, the at least one of the Rx beam direction set or the Rx beam gain set based on the partition index, The Rx beam scanning is performed in each partition in the set of partitions.

28. The method of claim 17, further comprising: receiving a partition index indicating a partition in a set of partitions for performing the Rx beam scanning; as well as The at least one of the Rx beam direction set or the Rx beam gain set is determined based on the received partition index.

29. An apparatus for wireless communication at a receiving entity, the apparatus comprising: means for configuring the receiving entity to perform receive (Rx) beam scanning constrained based on at least one of a transmit (Tx) beam direction, Tx power, Tx beam gain, or Tx beam path loss of a transmit (Tx) beam from a transmitting entity or based on a predicted location of a target; and A component for performing the Rx beam scanning on at least one of a set of Rx beam directions or a set of Rx beam gains constrained by the at least one of the Tx beam direction, the Tx power, the Tx beam gain or the Tx beam path loss of the Tx beam from the transmitting entity or constrained by the predicted position of the target.

30. A computer readable medium storing computer executable code at a receiving entity, the code, when executed by a processor, causes the processor to: configuring the receiving entity to perform receive (Rx) beam scanning constrained based on at least one of a transmit (Tx) beam direction, Tx power, Tx beam gain, or Tx beam path loss of a transmit (Tx) beam from a transmitting entity or based on a predicted location of a target; and The Rx beam scanning is performed on at least one of a set of Rx beam directions or a set of Rx beam gains constrained by the at least one of the Tx beam direction, the Tx power, the Tx beam gain, or the Tx beam path loss of the Tx beam from the transmitting entity or constrained by the predicted position of the target.

Images