Beam skew profiling, indication and reporting for positioning and sensing

Abstract

Aspects presented herein may enable a network node (e.g., a UE, TRP / base station) to provide its beam skew information and / or receive beam skew information for another positioning entity to improve the accuracy and reliability of UE positioning. In one aspect, a network node obtains beam skew information associated with a set of beams of the network node at a plurality of center frequencies. The network node sends, for a network entity, the beam skew information for at least one beam of the set of beams for locating a session. The network entity participates in the positioning session with the network entity via the at least one beam based on the beam skew information.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. non-provisional patent application serial number 18 / 161,797, entitled “BEAM SQUINT PROFILING, INDICATION, AND REPORTING FORPOSITIONING AND SENDING,” filed on January 30, 2023, which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates generally to communication systems and, more particularly, to wireless communications related to positioning and sensing. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasts. 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.

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and 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 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). 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

[0006] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of these aspects. This summary is not an extensive overview of all contemplated aspects. This summary does not identify key or critical elements of all aspects, nor does it delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that will be presented later.

[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus obtains beam deflection information associated with a beam set of a network node at multiple center frequencies. The apparatus transmits, to a network entity, the beam deflection information for at least one beam in the beam set used for a positioning session. The apparatus participates in the positioning session with the network entity via the at least one beam based on the beam deflection information.

[0008] In one aspect of the present disclosure, a method, computer-readable medium, and apparatus are provided. The apparatus receives, from a network node, beam deflection information associated with at least one beam in a beam set of the network node for use in a positioning session. The apparatus participates in the positioning session with the network node via the at least one beam based on the beam deflection information.

[0009] To accomplish the foregoing and related objectives, one or more aspects may include the features hereinafter fully described and particularly pointed out in the claims. The following description and accompanying drawings set forth in detail some illustrative features of one or more aspects. However, these features are indicative of only some of the various ways in which the principles of the various aspects may be employed. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

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

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

[0017] Figure 5 is a diagram illustrating example beam deflection according to various aspects of the present disclosure.

[0018] Figure 6 is a diagram illustrating an example of measuring radio frequency (RF) characteristics of a UE based on a spherical measurement test according to various aspects of the present disclosure.

[0019] Figure 7 is a diagram illustrating an example of obtaining beam deflection information for a UE based on spherical measurement according to various aspects of the present disclosure.

[0020] Figure 8A is a diagram illustrating an example capability transfer process that may be used to report beam deflection information of a target to a server according to various aspects of the present disclosure.

[0021] Figure 8B is a diagram illustrating an example LTE Positioning Protocol (LPP) location information delivery process that may be used to report beam deflection information of a target to a server according to various aspects of the present disclosure.

[0022] Figure 9A is a diagram illustrating example beam deflection information messaging in accordance with various aspects of the present disclosure.

[0023] Figure 9B is a diagram illustrating example beam deflection information messaging in accordance with various aspects of the present disclosure.

[0024] Figure 10A is a diagram illustrating example beam deflection information messaging in accordance with various aspects of the present disclosure.

[0025] Figure 10B is a diagram illustrating example beam deflection information messaging in accordance with various aspects of the present disclosure.

[0026] Figure 11 is a diagram illustrating example beam deflection information messaging in accordance with various aspects of the present disclosure.

[0027] Figure 12 is a diagram illustrating example beam deflection information messaging in accordance with various aspects of the present disclosure.

[0028] Figure 13 is a diagram illustrating an example assistance data (AD) delivery process that may be used to indicate beam deflection information of a transmit-receive point (TRP) to a target in accordance with various aspects of the present disclosure.

[0029] Figure 14 is a diagram illustrating example beam deflection information messaging in accordance with various aspects of the present disclosure.

[0030] Figure 15 is a diagram illustrating example beam deflection information messaging in accordance with various aspects of the present disclosure.

[0031] Figure 16 is a diagram illustrating example beam deflection information messaging in accordance with various aspects of the present disclosure.

[0032] Figure 17A is a diagram illustrating an example in which a base station reports its beam deflection information to a server based on a TRP information exchange process according to various aspects of the present disclosure.

[0033] Figure 17B 2 is a diagram illustrating an example in which a base station reports its beam deflection information to a server based on the NR Positioning Protocol A (NRPPa) positioning information exchange procedure according to various aspects of the present disclosure.

[0034] Figure 17C is a diagram illustrating an example in which a base station reports its beam tilt information to a server based on an NRPPa measurement information exchange procedure according to various aspects of the present disclosure.

[0035] Figure 18 is a diagram illustrating example beam deflection information messaging in accordance with various aspects of the present disclosure.

[0036] Figure 19 is a diagram illustrating example beam deflection information messaging in accordance with various aspects of the present disclosure.

[0037] Figure 20 2 is a diagram illustrating an example in which a server provides beam steering information of a UE to a base station based on an NRPPa assistance information exchange procedure according to various aspects of the present disclosure.

[0038] Figure 21 is a diagram illustrating example beam deflection information messaging in accordance with various aspects of the present disclosure.

[0039] Figure 22 is a diagram illustrating example beam deflection information messaging in accordance with various aspects of the present disclosure.

[0040] Figure 23 is a diagram illustrating example beam deflection information messaging in accordance with various aspects of the present disclosure.

[0041] Figure 24 is a flow chart of a method of wireless communication.

[0042] Figure 25 is a flow chart of a method of wireless communication.

[0043] Figure 26 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities.

[0044] Figure 27 is a flow chart of a method of wireless communication.

[0045] Figure 28 is a flow chart of a method of wireless communication.

[0046] Figure 29 is a diagram illustrating an example of a hardware implementation for an example network entity. DETAILED DESCRIPTION

[0047] When user equipment (UE) positioning is based on a communication link operating on a wideband channel where beam deflection may occur, the various aspects presented herein can improve the accuracy and reliability of UE positioning. The various aspects presented herein can enable network entities and nodes (e.g., base stations, location servers, transmit-receive points (TRPs), UEs, etc.) to consider beam deflection information when performing positioning for the UE, such as performing angle of arrival (AoA) / angle of departure (AoD) based positioning and sensing for the UE. In one aspect of the present disclosure, the UE and / or TRP can be configured / designated to report its relevant beam deflection information to a location server (e.g., a location management function (LMF)), where the beam deflection information can be parsed based on spherical measurement tests. The various aspects presented herein also provide example signaling for the UE and / or TRP to provide its transmit (Tx) / receive (Rx) beam deflection information to the location server, and also provide example signaling for the location server to provide Tx beam deflection information to a receiver (e.g., for AoA / AoD based positioning).

[0048] Certain aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages: For example, by enabling positioning entities (e.g., UE, TRP / base station, and location server, etc.) to exchange their associated beam skew information, the positioning entities can evaluate the beam skew associated with the UE / TRP and, if beam skew is expected, correct the angle measurements used for positioning and sensing applications, thereby improving the accuracy and reliability of positioning.

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

[0050] Several aspects of telecommunication systems are presented with reference to various apparatuses and methods. These apparatuses 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 can be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0051] As an example, an element or any part of an element or any combination of elements can be implemented as a "processing system", which includes one or more processors. The example of a processor includes a microprocessor, a microcontroller, a graphics processing unit (GPU), a central processing unit (CPU), an application processor, a digital signal processor (DSP), a reduced instruction set computing (RISC) processor, a system on a chip (SoC), a baseband processor, a field programmable gate array (FPGA), a programmable logic device (PLD), a state machine, a gating logic, a discrete hardware circuit and other suitable hardware configured to perform various functionalities described throughout this disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other terms, software should be broadly interpreted as meaning an instruction, an instruction set, a code, a code segment, a program code, a program, a subroutine, a software component, an application, a software application, a software package, a routine, a subroutine, an object, an executable, a thread of execution, a process, a function or any combination thereof.

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

[0053] Although various aspects, specific implementations and / or use cases are described in this application by way of illustration of some examples, additional or different aspects, specific implementations and / or use cases may be produced in many different arrangements and scenarios. The various aspects, specific implementations and / or use cases described herein may be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, various aspects, specific implementations and / or use cases may be produced via integrated chip 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, devices that enable artificial intelligence (AI), 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 may be within the scope of chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the scope of aggregation, distribution or original equipment manufacturer (OEM) equipment or systems in conjunction with one or more technologies herein. In some actual settings, the equipment in conjunction 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 both analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The techniques described herein can be practiced in a wide variety of devices of various sizes, shapes, and configurations, including chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, and the like.

[0054] 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 functions can be implemented in a converged 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 a converged base station (also known as a standalone BS or a monolithic BS) or a decomposed base station.

[0055] 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 across two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some 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 across one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0056] 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 utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (a 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)). Disaggregation 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. Various units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0057] Figure 1 FIG100 is a diagram illustrating an example of a wireless communication system and 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, which 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.

[0058] 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 transmit 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 transmit 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 and / or transmit signals to one or more of the other units via a wireless transmission medium.

[0059] In some aspects, the CU 110 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by the CU 110. The CU 110 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, the 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). As needed, the CU 110 may be implemented to communicate with the DU 130 for network control and signaling.

[0060] The DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 140. In some aspects, the DU 130 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more higher physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) based at least in part on a functional split (such as those defined by 3GPP). In some aspects, the DU 130 may also host one or more lower PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU 130 or with control functions hosted by the CU 110.

[0061] Lower layer functionality may be implemented by one or more RUs 140. In some deployments, a RU 140 controlled by a DU 130 may correspond to a logical node that hosts RF processing functionality or low PHY layer functionality (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 a functional split (such as a lower layer functional split). 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, both real-time and non-real-time aspects of control and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may enable the DU 130 and CU 110 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0062] The SMO framework 105 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 105 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface (such as the O1 interface). For virtualized network elements, the SMO framework 105 can be configured to interact with a cloud computing platform (such as Open Cloud (O-Cloud) 190) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements may include, but are not limited to, CU 110, DU 130, RU 140, and near-RT RIC 125. In some implementations, the SMO framework 105 can communicate with hardware aspects of the 4G RAN (such as Open eNB (O-eNB) 111) via the O1 interface. Additionally, in some implementations, the SMO framework 105 can 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 .

[0063] The non-RT RIC 115 can be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / machine learning (ML) (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 125. The non-RT RIC 115 can be coupled to or in communication with the near-RT RIC 125 (e.g., via an A1 interface). The near-RT RIC 125 can be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources through data collection and actions over an interface (e.g., 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.

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

[0065] At least one of the CU 110, DU 130, and RU 140 may be referred to as a base station 102. Thus, the base station 102 may include one or more of the CU 110, DU 130, and 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 that includes 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 called a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) (also known as reverse link) transmissions from UE 104 to RU 140 and / or downlink (DL) (also known as forward link) transmissions from RU 140 to UE 104. The communication link may utilize multiple-input, multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be over one or more carriers. Base station 102 / UE 104 may utilize spectrum with a bandwidth of up to Y MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.) for each carrier allocated in a carrier aggregation for transmission in each direction for a total of up to Yx MHz (x component carriers). These carriers may 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 for DL ​​compared to UL). Component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

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

[0067] 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 the 5 GHz unlicensed spectrum. When communicating in the unlicensed spectrum, the UE 104 / AP 150 may perform a clear channel assessment (CCA) to determine whether the channel is available before communicating.

[0068] 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 referred to (interchangeably) as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes occurs with reference to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0069] 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 frequency 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 operation 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.

[0070] With the above in mind, unless otherwise specified, if the term "sub-6 GHz" or the like is used herein, it may broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Furthermore, unless otherwise specified, if the term "millimeter wave" or the like is used herein, 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.

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

[0072] 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 TRP, a network node, a network entity, a network equipment, or some other suitable terminology. The base station 102 may be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, a converged (monolithic) base station having 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 collection of base stations that may include disaggregated base stations and / or converged base stations may be referred to as a next generation (NG) RAN (NG-RAN).

[0073] The core network 120 may include an access and mobility management function (AMF) 161, a session management function (SMF) 162, a user plane function (UPF) 163, a unified data management (UDM) 164, one or more location servers 168, and other functional entities. The AMF 161 is a control node that handles signaling between the UE 104 and the core network 120. The AMF 161 supports registration management, connection management, mobility management, and other functions. The SMF 162 supports session management and other functions. The UPF 163 supports packet routing, packet forwarding, and other functions. The UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identity handling, access authorization, and subscription management. The one or more location servers 168 are exemplified as including a gateway mobile location center (GMLC) 165 and a location management function (LMF) 166. However, 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. The GMLC 165 and LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. The LMF 166 receives measurements and assistance information from the NG-RAN and UE 104 via the AMF 161 to calculate the location of the UE 104. The NG-RAN may utilize one or more positioning methods to determine the location of the UE 104. Positioning the UE 104 may involve signal measurements, position estimation, and optional velocity calculation based on these measurements. Signal measurements may be performed by the UE 104 and / or the base station 102 serving the UE 104. The measured signals may be based on one or more of 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 other systems / signals / sensors.

[0074] Examples of UE 104 include a cellular phone, a smartphone, a Session Initiation Protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, or any other similarly functional device. Some of UE 104 may be referred to as IoT devices (e.g., a parking meter, a gas pump, a toaster, a vehicle, a heart monitor, etc.). UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. In some scenarios, the term UE may also apply to one or more companion devices, such as in a device constellation arrangement. One or more of these devices may access the network collectively and / or individually.

[0075] See again Figure 1 In certain aspects, the UE 104 and / or the base station 102 may include a beam deflection information exchange component 198 / 199, which may be configured to: obtain beam deflection information associated with a beam set of a network node at multiple center frequencies; send beam deflection information for at least one beam in the beam set for a positioning session to a network entity; and participate in a positioning session with the network entity via the at least one beam based on the beam deflection information.

[0076] In certain aspects, one or more location servers 168 may have a beam deflection information exchange component 197, which may be configured to: receive beam deflection information associated with at least one beam in a beam set of the network node for a positioning session from a network node; and participate in a positioning session with the network node via the at least one beam based on the beam deflection information.

[0077] 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 2C FIG250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2DFIG280 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), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL, or time division duplex (TDD), where 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 can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are all DL and all UL, respectively. The other slot formats 2-61 include a mix of DL, UL, and flexible symbols. The UE is configured with the slot format via the received slot format indicator (SFI) (dynamically configured via DL control information (DCI) or semi-statically / statically configured via radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0078] Figures 2A to 2D The frame structure is illustrated, and various aspects of the present disclosure are applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10ms) can be divided into 10 equally sized subframes (1ms). Each subframe may include one or more time slots. A subframe may also include a mini-time slot, 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 symbols on the DL may be CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols. The symbols on the UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) extended OFDM (DFT-s-OFDM) symbols (for power-limited scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and the parameter set. The parameter set defines the subcarrier spacing (SCS) (see Table 1). Symbol length / duration can be scaled with 1 / SCS.

[0079]

[0080] Table 1: Parameter set, SCS and CP

[0081] For normal CP (14 symbols / slot), different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Thus, for normal CP and parameter set μ, there are 14 symbols / slot and 2 μ time slots / 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. Symbol length / duration is inversely related to subcarrier spacing. Figures 2A to 2D An example is provided for a normal CP with 14 symbols per slot and a parameter set μ=2 with 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).

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

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

[0084] Figure 2BExamples of various DL channels within a subframe of a frame are illustrated. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE comprising six RE groups (REGs), each REG comprising 12 consecutive REs within an OFDM symbol of a RB. The PDCCH within a BWP may be referred to as a control resource set (CORESET). During a PDCCH monitoring opportunity on the 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), where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies across the channel bandwidth. The primary synchronization signal (PSS) may be within symbol 2 of a specific subframe of the frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identification. The secondary synchronization signal (SSS) may be within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE 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 not sent over the PBCH (such as the system information block (SIB)), and paging messages.

[0085] like Figure 2C As illustrated, some of the REs carry DM-RS (indicated as R for a specific configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may transmit the DM-RS of the physical uplink control channel (PUCCH) and the DM-RS of the physical uplink shared channel (PUSCH). The PUSCH DM-RS may be transmitted in the first or first two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is transmitted and depending on the specific PUCCH format used, the PUCCH DM-RS may be transmitted in different configurations. The UE may transmit a sounding reference signal (SRS). The SRS may be transmitted in the last symbol of the subframe. The SRS may have a comb structure, and the UE may transmit 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.

[0086] 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 a scheduling request, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (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.

[0087] Figure 3 3 is a block diagram of a base station 310 in an access network communicating with a UE 350. In the DL, Internet Protocol (IP) packets may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functionality 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 functionality associated with header compression / decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0088] The transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functionality associated with various signal processing functions. Layer 1, which includes the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping onto 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), and M-order quadrature amplitude modulation (M-QAM)). The coded and modulated symbols are then separated into parallel streams. Each stream is then mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then combined 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. The channel estimates may be derived from a reference signal and / or channel state feedback transmitted 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 using a corresponding spatial stream for transmission.

[0089] At the UE 350, each receiver 354Rx receives a signal via 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 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they 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, as well as the reference signal, are recovered and demodulated by determining the most likely signal constellation point transmitted 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 a controller / processor 359, which implements layer 3 and layer 2 functionality.

[0090] 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 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 an ACK and / or NACK protocol to support HARQ operations.

[0091] Similar to the functionality described in conjunction with DL transmissions performed by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with 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 functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0092] Channel estimates derived by the channel estimator 358 based on a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 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.

[0093] 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.

[0094] 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 and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.

[0095] 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 deflection information exchange component 198 combines various aspects.

[0096] 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 deflection information exchange component 199 combines various aspects.

[0097] Figure 4 FIG4 is a diagram illustrating an example of UE positioning based on reference signal measurements (which may also be referred to as “network-based positioning”) according to various aspects of the present disclosure. UE 404 may be at time T SRS_TX UL-SRS 412 is sent and at time T PRS_RX Receive DL Positioning Reference Signal (PRS) (DL-PRS) 410. TRP 406 may be at time T SRS_RX Receive UL-SRS 412 and at time T PRS_TX 410. The UE 404 may receive the DL-PRS 410 before transmitting the UL-SRS 412, or may transmit the UL-SRS 412 before receiving the DL-PRS 410. In both cases, the positioning server (e.g., the location server 168) or the UE 404 may determine the UL-SRS 412 based on the || T SRS_RX –T PRS_TX |–|T SRS_TX –T PRS_RX || to determine RTT 414. Thus, multi-RTT positioning may utilize UE Rx-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 uses assistance data received from the positioning server to measure the UE Rx-Tx time difference measurement (and optionally the DL-PRS-RSRP of the received signal), and TRP 402, 406 uses assistance data received from the positioning server to measure the gNB Rx-Tx time difference measurement (and optionally the UL-SRS-RSRP of the received signal). These measurements can be used at the positioning server or UE 404 to determine the 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.

[0098] PRS can be defined for network-based positioning (e.g., NR positioning) to enable UEs to detect and measure more neighboring transmit and receive points (TRPs), with multiple configurations supported to enable various deployments (e.g., indoor, outdoor, sub-6, mmW, etc.). To support PRS beam operation, beam scanning can also be configured for PRS. The UL positioning reference signal can be based on a sounding reference signal (SRS) with enhancement / adjustment for positioning purposes. In some examples, the UL-PRS can be referred to as "SRS for positioning," and a new information element (IE) can be configured for SRS for positioning in RRC signaling.

[0099] DL PRS-RSRP may be defined as the linear average of the power contributions (in watts) of the resource elements of the antenna ports carrying the configured DL PRS reference signal for RSRP measurement, within the considered measurement frequency bandwidth. In some examples, for FR1, the reference point for DL ​​PRS-RSRP may be the UE's antenna connector. For FR2, DL PRS-RSRP may be measured based on the combined signal from the antenna elements corresponding to a given receiver branch. For both FR1 and FR2, if the UE uses receiver diversity, the reported DL PRS-RSRP value may not be lower than the corresponding DL PRS-RSRP of any of the individual receiver branches. Similarly, UL SRS-RSRP may be defined as the linear average of the power contributions (in watts) of the resource elements carrying the sounding reference signal (SRS). UL SRS-RSRP may be measured over the configured resource elements, within the considered measurement frequency bandwidth, and during configured measurement occasions. In some examples, for FR1, the reference point for UL SRS-RSRP may be the antenna connector of the base station (e.g., gNB). For FR2, the UL SRS-RSRP may be measured based on the combined signals from the antenna elements corresponding to a given receiver branch. For FR1 and FR2, if the base station uses receiver diversity, the reported UL SRS-RSRP value may not be lower than the corresponding UL SRS-RSRP of any of the individual receiver branches.

[0100] PRS-Path RSRP (PRS-RSRPP) can be defined as the power of the linear average of the channel response at the i-th path delay of the resource element carrying the DL PRS signal configured for measurement, where the DL PRS-RSRPP for the 1st path delay is the power contribution corresponding to the first detected path in time. In some examples, the PRS path phase measurement can refer to the phase associated with the i-th path of the channel derived using the PRS resource.

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

[0102] DL-TDOA positioning may utilize DL Reference Signal Time Difference (RSTD) (and optionally DL-PRS-RSRP) of downlink signals received at a UE 404 from multiple TRPs 402, 406. The UE 404 uses assistance data received from a positioning server to measure the DL RSTD (and optionally DL-PRS-RSRP) of the received signals, and the resulting measurements, along with other configuration information, are used to position the UE 404 relative to neighboring TRPs 402, 406.

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

[0104] 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 a 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, along with other configuration information, are used to estimate the position of the UE 404. For purposes of this disclosure, positioning operations in which a UE provides measurements to a base station / positioning entity / server for use in calculating the UE's position may be described as "UE-assisted," "UE-assisted positioning," and / or "UE-assisted position calculation," while positioning operations in which a UE measures and calculates its own position may be described as "UE-based," "UE-based positioning," and / or "UE-based position calculation."

[0105] 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 technologies may be combined in various ways to increase accuracy, determine and / or enhance certainty, supplement / complement measurements, and / or replace / provide missing information. For example, some UE positioning mechanisms may be radio access technology (RAT) dependent (e.g., positioning of the UE is based on the RAT), such as downlink positioning (e.g., observed time difference of arrival (OTDOA) measurements), uplink positioning (e.g., uplink time difference of arrival (UTDOA) measurements), and / or combined DL and UL based positioning (e.g., measurements of RTT relative to neighboring cells). Some wireless communication systems may also support enhanced cell ID (E-CID) positioning procedures based on radio resource management (RRM) measurements. On the other hand, some UE positioning mechanisms may be RAT-independent (e.g., UE positioning does not depend on RAT), such as enhanced GNSS, and / or positioning technologies based on WLAN, Bluetooth, Terrestrial Beacon System (TBS), and / or positioning technologies based on sensors (e.g., air pressure sensors, motion sensors), etc. Some UE positioning mechanisms may be based on a hybrid model, in which multiple positioning methods are used, which may include both RAT-dependent positioning technologies and RAT-independent positioning technologies (e.g., GNSS and OTDOA hybrid positioning).

[0106] It should be noted that the terms "positioning reference signal" and "PRS" generally refer to specific reference signals used for positioning in NR and LTE systems. However, as used herein, the terms "positioning reference signal" and "PRS" may also refer to any type of reference signal that can be used for positioning, such as, but not limited to, PRS, TRS, PTRS, CRS, CSI-RS, DMRS, PSS, SSS, SSB, SRS, UL-PRS, and the like, as defined in LTE and NR. Furthermore, the terms "positioning reference signal" and "PRS" may refer to either downlink or uplink positioning reference signals, unless otherwise indicated by the context. To further distinguish between the types of PRS, downlink positioning reference signals may be referred to as "DL PRS," and uplink positioning reference signals (e.g., SRS, PTRS used for positioning) may be referred to as "UL-PRS." Furthermore, for signals that can be transmitted in both the uplink and downlink (e.g., DMRS, PTRS), these signals may be prepended with "UL" or "DL" to distinguish their direction. For example, "UL-DMRS" may be distinguished from "DL-DMRS."

[0107] If combined Figure 1As described, wireless devices can communicate with each other based on beamforming, where a transmitting device can steer / send its signal in a specific direction (e.g., toward a receiving device). Thus, beamforming can use multiple antennas to transmit the same signal and direct it in a single direction, rather than transmitting the signal from a broadcast antenna to spread in all directions. Beamforming can achieve faster and more reliable wireless data transfer. Although beamforming patterns (e.g., for transmit (Tx) and / or receive (Rx) beams) can be optimized in a specific direction for a specific frequency, frequencies that deviate from this optimization may cause a skew in the resulting beam. This may be referred to as beam squint or beamsquinting, where the beam direction may change or drift when the operating frequency changes.

[0108] Figure 5 5 is a diagram illustrating example beam deflection according to various aspects of the present disclosure. As shown at 504, based on beamforming, a Tx beam 502 can be configured to transmit in a first direction at a first Tx frequency (Frequency 1). However, as shown at 506, if the Tx frequency changes (e.g., increases or decreases to a second Tx frequency (Frequency 2)), the direction of the Tx beam 502 may also change, such as shifting by X degrees (X°). In some examples, for a phased array or slotted waveguide antenna, beam deflection can refer to the angle at which the transmission is offset from the normal to the plane of the antenna. Thus, beam deflection can also refer to a change in the beam direction based on operating frequency, polarization, or orientation.

[0109] Beam skew can become more noticeable (and common) when a communication link is operating over a wideband channel but relies on beams optimized over a subset of that wideband. This can lead to varying levels of performance degradation depending on the level of skew. For example, once the Tx frequency changes, the Tx beam may no longer point in the preferred / desired direction.

[0110] Generally speaking, a UE (and to some extent certain transmit receive points (TRPs)) may have an antenna array that can be optimized for a limited number of center frequencies. However, given the plethora of frequency bands available today (e.g., FR2 and above), a UE and / or TRP may be more likely to operate on a variety of center frequencies and / or on a portion of a wideband channel (e.g., on a subband (SB) of a wideband channel). Therefore, beam steering may be an impairment that the UE and / or TRP may consider.

[0111] In some scenarios, beam deflection may affect the accuracy and reliability of UE positioning. Figure 4In the described network-based positioning, beam deflection may cause the transmitting or receiving device to provide erroneous or inaccurate beam angle information, which may affect the accuracy of calculating angle-of-arrival (AoA)-based and / or angle-of-departure (AoD)-based positioning and sensing. For the purposes of this disclosure, AoD-based positioning and sensing (such as downlink (DL)-AoD positioning) may refer to positioning methods that utilize the measured DL-positioning reference signal (PRS)-reference signal received power (RSRP) (DL-PRS-RSRP) and DL-PRS-reference signal received path power (DL-PRS-RSRPP) of DL signals received from multiple TPs at a UE. The UE may use assistance data received from a positioning server (e.g., LMF) to measure the DL-PRS-RSRP and DL-PRS-RSRPP of the received signals, and the resulting measurements may be used by the positioning server and / or the UE, along with other configuration information, to locate the UE relative to neighboring transmission points (TPs). On the other hand, AoA-based positioning and sensing (such as uplink (UL)-AoA positioning) may refer to a positioning method that utilizes the measured azimuth angle of arrival (A-AoA) and zenith angle of arrival (Z-AoA) at multiple reception points (RPs) of uplink signals transmitted from the UE. The RP may measure the A-AoA and Z-AoA (and optionally UL-SRS-RSRPP) of the received signal using assistance data received from a positioning server (e.g., LMF), and the resulting measurements may be used by the positioning server and / or the UE, along with other configuration information, to estimate the UE's position.

[0112] Various aspects presented herein may improve the accuracy and reliability of UE positioning when UE positioning is based on a communication link operating on a wideband channel where beam deflection may occur. Various aspects presented herein may enable network entities and nodes (e.g., base stations, location servers, TRPs, UEs, etc.) to consider beam deflection information when performing positioning for a UE, such as performing AoA / AoD-based positioning and sensing for the UE. In one aspect of the present disclosure, a UE and / or TRP may be configured / designated to report its relevant beam deflection information to a location server (e.g., a location management function (LMF)), which may assist the location server (and other UEs / TRPs) in evaluating the beam deflection associated with the UE / TRP and, if beam deflection is expected, correcting the angle measurements used for positioning and sensing applications. Various aspects presented herein may enable beam deflection information to be analyzed using spherical measurement tests. The aspects presented herein also provide example signaling for a UE and / or TRP to provide its Tx / Rx beam deflection information to a location server, and also provide example signaling for a location server to provide Tx beam deflection information to a receiver (e.g., for AoA / AoD based positioning).

[0113] In one aspect of the present disclosure, beam skew characteristics / information associated with a wireless device (e.g., UE, TRP, etc.) may be measured / determined based on using a spherical measurement test. Figure 6 600 is a diagram illustrating an example of measuring radio frequency (RF) characteristics of a UE based on a spherical measurement test according to various aspects of the present disclosure. As shown at 602, a direct far field (DFF) measurement can be set up for a UE 604, which measures the RF characteristics of the UE 604 from different angles, where the goal is to ensure that the composite beam pattern on all beams of the UE 604 is as wide as possible. DFF measurement can refer to an over-the-air (OTA) test method used in wireless communications (e.g., 5G NR), which involves mounting the UE 604 (which can also be referred to as a device under test (DUT)) on a positioner that rotates in azimuth and elevation directions. This process can enable measurements of the UE 604 at any angle on a three-dimensional (3D) sphere (hence the term spherical measurement). In some examples, the far field of the UE 604 can also be measured in an anechoic chamber. As shown at 606, the DFF / spherical measurement can specify a first positioning system in which the angle between the dual-polarized measurement antenna and the UE 604 has at least two degrees of freedom axes and maintains a polarization reference, and as shown at 608, the DFF / spherical measurement can also specify a second positioning system such that the angle between the link antenna and the DUT has at least two degrees of freedom axes and maintains a polarization reference. The second positioning system for the link antenna can be complementary to the first positioning system for the measurement antenna, where the second positioning system can provide an angular relationship that can be controlled independently of the measurement antenna. In one example, as shown at 610, to perform spherical coverage test measurements for the UE 604, a 45° beam steering granularity in the xz plane (e.g., from 45° to 135°) and a 22.5° beam steering granularity in the xy plane (e.g., from -90° to 90°) can be configured for testing.

[0114] In some examples, two different types of measurement grids can be used for spherical surface measurements: a planar uniform grid and a spherical uniform grid. With a planar uniform grid, the measurement grid points can have azimuth and elevation angles that are evenly distributed with a constant step size. On the other hand, with a spherical uniform grid, the measurement grid points can be evenly distributed across the surface of the sphere with a constant density.

[0115] In one aspect of the present disclosure, Figure 6 The spherical measurement test described can be used to characterize the beam deflection of a wireless device at different center frequencies, where the purpose of the spherical measurement test is to determine the beam deflection for a specified frequency grid (such as N different center frequencies F= <f1,…,f N>). The beam deflection information associated with the wireless device can then be stored as a lookup table (e.g., in a memory of the wireless device or on a server). For the purposes of this disclosure, a center frequency (e.g., of a filter or channel) can refer to a frequency between an upper cutoff frequency and a lower cutoff frequency. For example, if the UE is configured to communicate using a frequency band between 26.5 GHz and 29.5 GHz, the center frequency used for communication can be 27 GHz.

[0116] Figure 7 FIG700 is a diagram illustrating an example of obtaining beam deflection information for a UE based on spherical measurements according to various aspects of the present disclosure. Figure 7 The example illustrates performing spherical measurements on a UE to obtain beam deflection information of the UE, but the aspects presented herein may also be applied to other wireless devices, such as TRPs, hardware components capable of sending / receiving RF, and / or RF sensing devices, etc.

[0117] In one example, as shown at 704, the UE 702 may have the capability to beamform a set of beams (e.g., Tx beams and / or Rx beams), which may include a first beam (Beam 1), a second beam (Beam 2), and up to a B-th beam (Beam B). In addition, as shown at 706, the UE 702 may also support (e.g., operate under) a set of center frequencies F, which may include a first center frequency (f1), a second center frequency (f2), and up to an N-th center frequency (f3). N ).

[0118] As shown at 708, spherical measurements may be set up for the UE 702 to measure beam deflection information associated with one or more beams of the UE 702, wherein the measurements may be performed in a designated darkroom or test location. In one example, for each beam j in a beam set (e.g., beams 1 to beam B, codebook, etc.), the UE 702 may be configured to form the beam j at a center frequency (e.g., codebook, delay line settings, etc.), where the center frequency is f k Then, a spherical measurement test can be performed on the UE 702 in the far field region, where for beam j (at center frequency f k The equivalent isotropic radiated power (EIRP) at ) can be recorded in (all) possible spherical directions. For example, It can be expressed for beam j (at center frequency f k The EIRP set recorded at It can be expressed for beam j (at frequency f k The EIRP captured at all possible azimuth / elevation angles (e.g., In some examples, the granularity of the measurements in terms of azimuth (δφ) and elevation (δθ) directions can be determined based on regulatory and / or standardization specifications. For example, based on some regulatory specifications, the azimuth and elevation directions (δφ, δθ) can be configured to be uniform or non-uniform. In addition, each EIRP measurement can be specified as being expressed in terms of its corresponding azimuth direction φ. i and the elevation angle θ i The measurement process may continue for multiple or all beams in the beam set B and / or for multiple or all center frequencies in the center frequency set F.

[0119] As shown at 710, based on spherical measurements, a set of EIRP measurements (e.g., beam deflection information) for different combinations of beams and center frequencies may be obtained for UE 702. In one example, the beam deflection information for a particular beam (such as beam j) may be characterized based on at least one of the following options.

[0120] As shown at 712, under a first option, beam deflection information for a particular beam (e.g., beam j) may include detailed EIRP measurements at measured angles for different center frequencies, where and This option may specify higher storage / memory space for storing the beam steering information of UE 702 and higher signaling overhead for sending the beam steering information of UE 702.

[0121] Under the second option, the beam deflection information for a specific beam (e.g., beam j) may include a reference frequency / reference center frequency (e.g., f1) and a target frequency / target center frequency (e.g., f2). j ) at the measured angle. For the purposes of this disclosure, a reference frequency or reference center frequency may refer to a first frequency / center frequency associated with an EIRP measurement set. On the other hand, a target frequency or target center frequency may refer to a second frequency / center frequency (different from the first frequency / center frequency) whose EIRP measurement is represented based on a difference (e.g., Δ) from the EIRP measurement set associated with the first frequency / center frequency. For example, an EIRP measurement may be in and This option may reduce the amount of storage / memory space designated for storing the beam deflection information of the UE 702 and also reduce the signaling overhead for sending the beam deflection information of the UE 702 .

[0122] Under the third option, the beam tilt information for a particular beam (e.g., beam j) may include the angles (azimuth, elevation) of the maximum EIRP measurement at different frequencies, e.g. in Although this option may not include other EIRP measurements (e.g., non-maximum EIRP measurements), this option may further reduce the storage / memory space and signaling overhead designated for storing or transmitting the beam steering information of the UE 702.

[0123] Under the fourth option, the beam deflection information for a specific beam (eg, beam j) may include the reference frequency (eg, f1) and the target frequency (eg, f j ) is the difference between the angles at which the maximum EIRP is measured, e.g. in Similarly, this option may further reduce the storage / memory space and signaling overhead designated for storing or transmitting the beam deflection information of the UE 702.

[0124] In some examples, if the UE 702 supports a wide range of center frequencies, it may be impractical to measure the EIRP of a beam (or multiple beams) using all available center frequencies. Therefore, beam skew information at some frequencies may be obtained / estimated by interpolation. For example, if beam skew information for a specific beam at center frequencies of 26 GHz and 30 GHz is known, beam skew information for a specific beam at center frequencies between 26 GHz and 30 GHz (e.g., 27 GHz, 28 GHz, 29 GHz, etc.) may also be estimated or determined based on interpolation.

[0125] After obtaining the beam deflection information of UE 702, the beam deflection information can be stored in a memory / storage of UE 702. In some examples, the beam deflection information can be stored as a lookup table, such as shown at 710. In other examples, the beam deflection information can be stored or available at a server (e.g., a cloud server) or a network entity (e.g., a base station, a location server, a LMF, etc.). Then, if UE 702 is designated to provide its beam deflection information, the UE can load its beam deflection information or the lookup table from the memory / storage or retrieve it from the server.

[0126] In another aspect of the present disclosure, if the beam deflection information of a wireless device (e.g., UE, TRP, etc.) is available / known, the beam deflection information of the wireless device can be shared between different network entities or nodes. For example, during a UE positioning session, the beam deflection information of the UE and / or TRP can be shared between one or more base stations and / or location servers (e.g., LMF) (which can be collectively referred to as positioning entities). Then, based on the beam deflection information of the UE / TRP, the location server can derive more accurate measurements between the UE and the TRP, such as AoA and AoD measurements, thereby improving the accuracy and reliability of UE positioning.

[0127] In one example, a UE or TRP (hereinafter collectively referred to as a "target") may report its beam deflection information to a location server (e.g., LMF) using a capability transfer procedure and / or an LTE Positioning Protocol (LPP) location information transfer procedure. Furthermore, the target may be configured to report bulk beam deflection information (e.g., beam deflection information for multiple beams and / or center frequencies) or individual beam deflection information (e.g., beam deflection information for a specified beam and / or center frequency).

[0128] Figure 8A FIG800A is a diagram illustrating an example capability transfer process that can be used to report beam deflection information of a target to a server according to various aspects of the present disclosure. As shown at 806, a server 804 (e.g., a location server, LMF, etc.) can use capability messaging (e.g., by transmitting a request via a request capability message) to request a target 802 (e.g., a UE, a TRP, etc.) to provide beam deflection information of the target 802 (e.g., bulk beam deflection information or individual beam deflection information). In response, as shown at 808, the target 802 can indicate its beam deflection information (e.g., for available TX and / or RX beams) to the server 804, such as via a provide capability message. The request for beam deflection information of the target 802 can apply to both the Tx beam and the Rx beam of the target 802. For example, if the UE positioning session is associated with AoA-based positioning, the server 804 can request the target 802 (e.g., a UE) to provide beam deflection information for the Tx beam of the target 802. On the other hand, if the UE positioning session is associated with AoD-based positioning, the server 804 may request the target 802 (eg, UE) to provide beam tilt information of an Rx beam for the target 802 , etc.

[0129] Figure 8BFIG800B is a diagram illustrating an example LPP location information delivery process that can be used to report beam deflection information of a target to a server in accordance with various aspects of the present disclosure. As shown at 810, the server 804 can also use LPP location information delivery messaging (e.g., by transmitting a request via a Request Location Information message) to request the target 802 to provide beam deflection information of the target 802 (e.g., bulk beam deflection information or individual beam deflection information). In response, as shown at 812, the target 802 can indicate to the server 804 beam deflection information for beams used by the target 802 in positioning, such as via a Provide Location Information message. In some examples, as shown at 814, the target 802 can provide beam deflection information via multiple messages (e.g., for different beams). For example, for AoD-based positioning, the target 802 (e.g., a UE) can provide beam deflection information for its Rx beam used to perform AoD-based positioning.

[0130] In one example, if Figure 9A As shown in diagram 900A of FIG. 8 , the server 804 may use an AoD related information element (IE) (e.g., IE NR-DL-AoD-RequestCapabilities) to request the target 802 to provide beam deflection related capabilities (e.g., beam deflection information) as part of the LPP capability transfer process (e.g., in conjunction with Figure 8B In another example, Figure 9B As shown in FIG900B , the server 804 may use a dedicated (e.g., new) IE (e.g., IENR-DL-BeamSquint-RequestCapabilities) to request the target 802 to provide capabilities related to beam skewing as part of the LPP capability transfer process. In one example, the request from the server 804 may first query the target 802 for a general capability description related to beam skewing (e.g., whether the target 802 has the capability to indicate its beam skewing information). In another example, the request may include a flag for informing the target 802 as to whether the target 802 is designated to provide a detailed capability response for beam skewing information or to wait for additional solicited requests. In addition, the server 804 may send further / additional requests based on the target 802's response to solicit certain / additional beam skewing information / capabilities from the target 802. In another example, the server 804 may also request / solidate beam skewing information for beams on specific frequencies. For example, the server 804 may request beam tilt information for a given beam on a predefined frequency grid, and the target 802 may indicate the beam tilt information based on the requested grid.

[0131] In another example, as shown by Figure 10AAs shown in FIG. 1000A , the target 802 may provide its beam deflection information to the server 804 as a combination of Figure 8B In another example, as described by Figure 10B As shown in diagram 1000B of FIG. 1 , target 802 may provide its beam skew information to server 804 as part of an LPP capability transfer process (e.g., based on unsolicited capabilities), where target 802 may indicate its initial set of beam skew information and wait for a solicited capabilities request from server 804. In some examples, the beam skew information provided by target 802 may be part of the IE nr-DL-AoD-ProvideCapabilities or a dedicated / new IEnr-DL-BeamSquint-ProvideCapabilities.

[0132] In another example, Figure 11 As shown in FIG1100, the server 804 may use a request message (eg, using IE NR-DL-AoD-ReportConfig-rxx) to request the target 802 to perform AoD-based positioning as a location information delivery process (eg, in conjunction with Figure 8A ), where the request message may include a flag that triggers the target 802 to report the amount of beam skewing desired for a given measurement / beam (e.g., using the IE NR-DL-BeamSquint-RequestCapabilities).

[0133] In another example, Figure 12 As shown in diagram 1200 of FIG. 1 , the target 802 can perform AoD-based positioning upon request and provide beam deflection information of the RX beam used for positioning as part of a provide message (e.g., using IENR-DL-AoD-ProvideLocationInformation). In some examples, the provide message can include estimated angle-related measurements and beam deflection information related to the RX beam used by the target 802 for AoD-related measurements.

[0134] Figure 131300 is a diagram illustrating an example assistance data (AD) delivery process that may be used to indicate beam deflection information of a TRP to a target (e.g., a UE) in accordance with various aspects of the present disclosure. In another aspect of the present disclosure, a server 804 may indicate beam deflection information of a TRP to a target 802 (e.g., a UE) via assistance data. For example, as shown at 1302, during a positioning session (for target 802), target 802 (e.g., a UE) may transmit a request for assistance data to server 804, such as using a Request Assistance Data message. At 1304, in response to the request, server 804 may send assistance data for the positioning session to target 802, wherein the assistance data may include beam deflection information of a Tx beam of a TRP for AoD positioning. The beam deflection information may be bulk beam deflection information (e.g., bulk PRS Tx beam deflection information).

[0135] On the other hand, the server 804 can also be combined with Figure 8B The described LPP location information delivery process indicates beam skew information for individual Tx beams of a TRP to a target 802 (e.g., a UE). For example, the server 804 may indicate individual Tx beam (which may also be referred to as a PRS Tx beam) skew information for a TRP (or for multiple TRPs) as part of the request location information messaging shown at 810 (e.g., using IE NR-DL-AoD-ReportConfig-r16, NR-DL-TX-BeamSquint-info, etc.). The benefit of the server 804 (e.g., LMF) indicating beam skew information for the PRS Tx beam of a TRP to the target 802 is that it allows the target 802 to perform better estimates of AoD-related measurements (e.g., more precise / accurate angle measurements may be obtained).

[0136] In one example, if Figure 14 As shown in FIG1400, the target 802 may request the server 804 to provide assistance data related to the PRS Tx beam deflection information of one or more TRPs. Figure 13 As part of the LPP assistance data delivery process shown at 1302, for example, using IE NR-DL-AoD-RequestAssistanceData or a dedicated / new IE NR-DL-TX-BeamSquint-RequestAssistanceData. In another example, as Figure 15 As shown in FIG1500, the server 804 may provide assistance data associated with PRS Tx beam deflection information for one or more TRPs as Figure 13The LPP assistance data is delivered as shown at 1304 or as part of the LPP assistance data transmission process, for example using the IE NR-DL-AoD-ProvideAssistanceData or the dedicated / new IE NR-DL-TX-BeamSquint-ProvideAssistanceData.

[0137] In another example, Figure 16 As shown in FIG1600, the server 804 may also provide the target 802 with the individual PRS Tx beam deflection information of the TRP as part of the LPP information delivery process (e.g., in conjunction with Figure 8B In order for the server 804 to indicate the individual PRS Tx beam deflection information of the TRP to the target 802, it can be assumed that the server 804 already knows the PRS Tx beam used for positioning.

[0138] In another aspect of the present disclosure, a base station (e.g., an NG-RAN node) may report its beam deflection information (or the beam deflection information of its TRP). Figure 17A FIG1700A is an example of a base station reporting its beam deflection information to a server (e.g., LMF) based on a TRP information exchange procedure according to various aspects of the present disclosure. As shown at 1706, a server 1704 (e.g., LMF) may request a base station 1702 (e.g., an NG-RAN node) to provide beam deflection information of the base station 1702 (e.g., for its TRP), such as via a TRP information request message. At 1708, in response to the request, the base station 1702 may indicate to the server 1704 that the base station 1702 has beam deflection information (e.g., bulk beam deflection information) for its available Tx beams and / or Rx beams (e.g., Tx beams of the base station 1702 for AoD-based positioning, Rx beams of the base station 1702 for AoA-based positioning, etc.).

[0139] Figure 17B and Figure 17C1700B and 1700C illustrate examples of a base station reporting its beam deflection information to a server based on an NR Positioning Protocol A (NRPPa) positioning information exchange procedure or based on an NRPPa measurement information exchange procedure according to various aspects of the present disclosure. In one example, at 1710 or 1714, the server 1704 may request the base station 1702 to perform / perform AoA-based positioning or perform measurements for positioning (e.g., AoA-related measurements), such as using a positioning information request message (e.g., for an NRPPa positioning information exchange procedure) or using a measurement request message (e.g., for an NRPPa measurement information exchange procedure). In some examples, the request message may include a flag for triggering the base station 1702 to report the desired beam deflection amount for a given measurement.

[0140] As shown at 1712 and 1716, in response to the request, the base station 1702 may perform AoA-based positioning according to the request and provide beam deflection information of the Rx beam used for positioning, such as using a positioning information response message or a measurement response. The response message may include the estimated angle-related measurement and the beam deflection information related to the Rx beam used for the AoA-related measurement.

[0141] In one example, if Figure 18 As shown in FIG1800, the server 1704 may request the base station 1702 to provide capabilities related to beam deflection as part of the NRPPa TRP information exchange process (e.g., in conjunction with Figure 17A ), such as using TRP information request messaging (e.g., via IE TRPInformationTypeItem). In one example, the request may first query a general capability description from base station 1702 (e.g., whether base station 1702 has the capability to indicate its beam deflection information). In another example, the request may include a flag for informing base station 1702 whether the base station 1702 node is designated to provide a detailed capability response for beam deflection information or to wait for additional solicited requests. In some examples, server 1704 may transmit further / additional requests to base station 1702 based on the response of base station 1702 to solicit certain beam deflection capabilities. In addition, server 1704 may request beam deflection information for a given beam on a predefined frequency grid, and base station 1702 may indicate beam deflection information at the requested grid in response.

[0142] In another example, Figure 19 As shown in FIG1900, the base station 1702 may provide its beam deflection information to the server 1704 via a TRP information response message as part of the NRPPa TRP information exchange process (e.g., in conjunction with Figure 17Adiscussed), such as using IEs TRPInformationTypeResponseItem-ExtIEs (e.g., TRPBeamSquintInformation).

[0143] In another aspect of the present disclosure, the server 1704 (e.g., LMF) may also provide the base station 1702 with beam deflection information of the Tx beam (which may also be referred to as an SRS Tx beam) of the target (e.g., UE, target 802, etc.) for AoA-based positioning. In one example, Figure 20 As shown in diagram 2000 of FIG. 1 , server 1704 may transmit beam deflection information (e.g., bulk SRS Tx beam deflection information) associated with a target (e.g., UE, target 802) to base station 1702 based on an NRPPa assistance information exchange procedure (e.g., via an assistance information control message). Figure 21 As shown in diagram 2100 , the server 1704 may provide assistance information related to the target's SRS Tx beam skew information as part of the NRPPa assistance information delivery process, such as using IE AssistanceInformationControl-IEs NRPPA-PROTOCOL-IES.

[0144] In another example, the server 1704 may send separate SRS Tx beam deflection information (or target) to the base station 1702 as a combination of Figure 17B and Figure 17C Part of the positioning information request message transmission or measurement request message transmission discussed. Figure 22 As shown in FIG2200 , the server 1704 may provide the SRS Tx beam squint information of the target (eg, UE) via a positioning information request message (eg, using IEid-Measurement-AoA-TX-BeamSquintInfo). Figure 23 As shown in diagram 2300 of FIGURE 2300, server 1704 may also provide the target's SRS Tx beam skew information via a measurement request message (e.g., using the IE id-Measurement-AoA-TX-BeamSquintInfo). Server 1704 indicating the SRS Tx beam information to base station 1702 may be beneficial because it may enable base station 1702 to perform better estimation of AoA-related measurements.

[0145] After the beam deflection information associated with the UE and / or TRP (or base station) is exchanged between positioning entities (e.g., UE, base station, location server, etc.), as combined with Figure 8A 、 Figure 8B 、 Figure 13 、 Figure 17A 、 Figure 17B 、 Figure 17C and Figure 20 As discussed, the positioning entity may perform or participate in a positioning session for the UE based on the beam deflection information, such as using or utilizing the Tx / Rx beam associated with the beam deflection information for communication, and / or modifying related positioning measurements (e.g., AoA measurements, AoD measurements, etc.) based on the beam deflection information. For example, the angle of the measurement used for AoA / AoD-based positioning may be adjusted based on the available beam deflection information.

[0146] Figure 24 2400 is a flow chart of a method for wireless communication. The method may be performed by a network node (e.g., UE 104, 604, 702; base station 102, 1702; target 802; device 2604). The method may enable the network node to provide its own beam deflection information and / or receive beam deflection information from another positioning entity to improve the accuracy and reliability of UE positioning.

[0147] At 2402, a network node may obtain beam deflection information associated with a set of beams of the network node at a plurality of center frequencies, such as in conjunction with Figure 7 For example, as described in conjunction with Figure 7 As discussed in 708 and 710 of FIG. 7 , UE 702 may obtain its beam deflection information based on a spherical measurement test, wherein the beam deflection information may be stored in a memory / storage device of the UE or in a server (e.g., as a lookup table). The beam deflection information may be obtained by, for example, Figure 26 The beam deflection information exchange component 198, application processor 2606, cellular baseband processor 2624 and / or transceiver 2622 of the device 2604 are executed.

[0148] In one example, the beam deflection information for each beam in the beam set may include at least one of the following: a set of equivalent isotropic radiated power (EIRP) measurements for a plurality of center frequencies at different angles, a first difference between a set of EIRP measurements for a reference center frequency among the plurality of center frequencies and one or more non-reference center frequencies among the plurality of center frequencies at different angles, an angle of maximum EIRP measurement for each of the plurality of center frequencies, a second difference between an angle of maximum EIRP measurement for a reference center frequency among the plurality of center frequencies and one or more non-reference center frequencies among the plurality of center frequencies, or a combination thereof. In another example, the beam deflection information for one or more beams in the beam set may be obtained based on interpolation.

[0149] In another example, as shown at 2408, the beam deflection information may be stored in a memory or storage device of the network node, and in order to obtain the beam deflection information, the network node may load the beam deflection information for at least one beam in the beam set from the memory or storage device of the network node.

[0150] In another example, the beam set may include one or more Tx beams, one or more Rx beams, or a combination thereof.

[0151] At 2404, the network node may send beam deflection information about at least one beam in the set of beams for the positioning session to the network entity, such as in conjunction with Figure 8A 、 Figure 8B 、 Figure 13 、 Figure 17A 、 Figure 17B 、 Figure 17C and Figure 20 For example, as described in conjunction with Figure 8A As discussed in 808 of , the target 802 may send beam deflection information for at least one of its beams to the server 804 based on a capability transfer procedure associated with UE positioning. The sending of the beam deflection information may be performed by, for example Figure 26 The beam deflection information exchange component 198, application processor 2606, cellular baseband processor 2624 and / or transceiver 2622 of the device 2604 are executed.

[0152] In one example, as shown at 2410, to transmit beam deflection information for at least one beam in a beam set, the network node may receive a request for providing beam deflection information from a network entity via a capability request message, and the network node may transmit the beam deflection information for one or more beams in the beam set to the network entity via a capability indication message in response to the capability request message. In some implementations, the capability request message and the capability indication message may be associated with at least one of a capability transfer procedure or a capability indication procedure.

[0153] In one example, as shown at 2412, to transmit beam deflection information for at least one beam in a beam set, the network node may receive a request to perform a positioning session from a network entity via a request message, and the network node may transmit beam deflection information for one or more beams in the beam set to be used for the positioning session to the network entity via a provide message. In some implementations, the request message and the provide message may be associated with a location information transfer procedure.

[0154] At 2406, the network node may participate in a positioning session with a network entity via at least one beam based on the beam deflection information, such as in conjunction with Figure 8A 、 Figure 8B 、 Figure 13 、 Figure 17A 、 Figure 17B 、 Figure 17C and Figure 20 For example, after the target 802 provides its beam deflection information, the target 802 may use the beam provided in the beam deflection information to perform UE positioning. Participation in the positioning session may be performed by, for example Figure 26 The beam deflection information exchange component 198, application processor 2606, cellular baseband processor 2624 and / or transceiver 2622 of the device 2604 are executed.

[0155] In one example, the network node may be a UE, and the network node may receive, from a network entity, second beam deflection information associated with at least one Tx beam of at least one TRP associated with a positioning session. In some implementations, the second beam deflection information may be received via assistance data or a request location information message. In some implementations, if the positioning session is associated with AoD positioning, the network node may receive a PRS set from at least one Tx beam of the at least one TRP, and the network node may estimate an AoD for the PRS set based on the second beam deflection information.

[0156] In another example, the network node may be a base station and the network entity may be a location server or a LMF, and the network node may receive a request for providing beam deflection information from the location server or the LMF via a TRP information request message, and the network node may send beam deflection information for one or more beams in the beam set to the location server or the LMF via a TRP information response message in response to the TRP information request message. In some implementations, the TRP information request message and the TRP information response message may be associated with a TRP information exchange procedure.

[0157] In another example, the network node may be a base station and the network entity may be a location server or LMF. The network node may receive a request to perform a positioning session from the location server or LMF via a request message, and the network node may send beam deflection information for one or more beams in a beam set to be used for the positioning session to the network entity via a provide message. In some implementations, the request message and the provide message may be associated with a positioning information exchange procedure or a measurement information exchange procedure. In some implementations, the positioning session may be associated with AoA positioning, and the one or more beams in the beam set may include an Rx beam set for the base station.

[0158] In another example, the network node is a base station and the network entity is a location server or LMF. The network entity may receive, from the location server or LMF, second beam deflection information associated with at least one transmit Tx beam of the UE associated with a positioning session. In some implementations, the second beam deflection information may be received via an assistance information control message associated with an assistance information exchange procedure or via a positioning information request message associated with a positioning information exchange procedure. In some implementations, the positioning session may be associated with AoA positioning, the network node may receive an SRS set from at least one Tx beam of the UE, and the network node may estimate the AoA for the SRS set based on the second beam deflection information.

[0159] Figure 25 2500 is a flow chart of a method for wireless communication. The method may be performed by a network node (e.g., UE 104, 604, 702; base station 102, 1702; target 802; device 2604). The method may enable the network node to provide its own beam deflection information and / or receive beam deflection information from another positioning entity to improve the accuracy and reliability of UE positioning.

[0160] At 2502, a network node may obtain beam deflection information associated with a set of beams of the network node at a plurality of center frequencies, such as in conjunction with Figure 7 For example, as described in conjunction with Figure 7 As discussed in 708 and 710 of FIG. 7 , UE 702 may obtain its beam deflection information based on a spherical measurement test, wherein the beam deflection information may be stored in a memory / storage device of the UE or in a server (e.g., as a lookup table). The beam deflection information may be obtained by, for example, Figure 26 The beam deflection information exchange component 198, application processor 2606, cellular baseband processor 2624 and / or transceiver 2622 of the device 2604 are executed.

[0161] In one example, the beam deflection information for each beam in the beam set may include at least one of the following: a set of EIRP measurements for a plurality of center frequencies at different angles, a first difference between a set of EIRP measurements for a reference center frequency among the plurality of center frequencies and one or more non-reference center frequencies among the plurality of center frequencies at different angles, an angle of maximum EIRP measurement for each of the plurality of center frequencies, a second difference between an angle of maximum EIRP measurement for a reference center frequency among the plurality of center frequencies and one or more non-reference center frequencies among the plurality of center frequencies, or a combination thereof. In another example, the beam deflection information for one or more beams in the beam set may be obtained based on interpolation.

[0162] In another example, the beam deflection information may be stored in a memory or storage device of the network node, and in order to obtain the beam deflection information, the network node may load the beam deflection information for at least one beam in the beam set from the memory or storage device of the network node.

[0163] In another example, the beam set may include one or more Tx beams, one or more Rx beams, or a combination thereof.

[0164] At 2504, the network node may send beam deflection information for at least one beam in the beam set used for the positioning session to the network entity, such as in conjunction with Figure 8A 、 Figure 8B 、 Figure 13 、 Figure 17A 、 Figure 17B 、 Figure 17C and Figure 20 For example, as described in conjunction with Figure 8A As discussed in 808 of , the target 802 may send beam deflection information for at least one of its beams to the server 804 based on a capability transfer procedure associated with UE positioning. The sending of the beam deflection information may be performed by, for example Figure 26 The beam deflection information exchange component 198, application processor 2606, cellular baseband processor 2624 and / or transceiver 2622 of the device 2604 are executed.

[0165] In one example, to transmit beam deflection information for at least one beam in a beam set, a network node may receive a request for providing beam deflection information from a network entity via a capability request message, and the network node may transmit the beam deflection information for one or more beams in the beam set to the network entity via a capability indication message in response to the capability request message. In some implementations, the capability request message and the capability indication message may be associated with at least one of a capability transfer procedure or a capability indication procedure.

[0166] In one example, to transmit beam deflection information for at least one beam in a beam set, a network node may receive a request to perform a positioning session from a network entity via a request message, and the network node may transmit beam deflection information for one or more beams in the beam set to be used for the positioning session to the network entity via a provide message. In some implementations, the request message and the provide message may be associated with a location information transfer procedure.

[0167] At 2506, the network node may participate in a positioning session with a network entity via at least one beam based on the beam deflection information, such as in conjunction with Figure 8A 、 Figure 8B 、 Figure 13 、 Figure 17A 、 Figure 17B 、 Figure 17C and Figure 20 For example, after the target 802 provides its beam deflection information, the target 802 may use the beam provided in the beam deflection information to perform UE positioning. Participation in the positioning session may be performed by, for example Figure 26 The beam deflection information exchange component 198, application processor 2606, cellular baseband processor 2624 and / or transceiver 2622 of the device 2604 are executed.

[0168] In one example, the network node may be a UE, and the network node may receive, from a network entity, second beam deflection information associated with at least one Tx beam of at least one TRP associated with a positioning session. In some implementations, the second beam deflection information may be received via assistance data or a request location information message. In some implementations, if the positioning session is associated with AoD positioning, the network node may receive a PRS set from at least one Tx beam of the at least one TRP, and the network node may estimate an AoD for the PRS set based on the second beam deflection information.

[0169] In another example, the network node may be a base station and the network entity may be a location server or a LMF, and the network node may receive a request for providing beam deflection information from the location server or the LMF via a TRP information request message, and the network node may send beam deflection information for one or more beams in the beam set to the location server or the LMF via a TRP information response message in response to the TRP information request message. In some implementations, the TRP information request message and the TRP information response message may be associated with a TRP information exchange procedure.

[0170] In another example, the network node may be a base station and the network entity may be a location server or LMF. The network node may receive a request to perform a positioning session from the location server or LMF via a request message, and the network node may send beam deflection information for one or more beams in a beam set to be used for the positioning session to the network entity via a provide message. In some implementations, the request message and the provide message may be associated with a positioning information exchange procedure or a measurement information exchange procedure. In some implementations, the positioning session may be associated with AoA positioning, and the one or more beams in the beam set may include an Rx beam set for the base station.

[0171] In another example, the network node is a base station and the network entity is a location server or LMF. The network entity may receive, from the location server or LMF, second beam deflection information associated with at least one transmit Tx beam of the UE associated with a positioning session. In some implementations, the second beam deflection information may be received via an assistance information control message associated with an assistance information exchange procedure or via a positioning information request message associated with a positioning information exchange procedure. In some implementations, the positioning session may be associated with AoA positioning, the network node may receive an SRS set from at least one Tx beam of the UE, and the network node may estimate the AoA for the SRS set based on the second beam deflection information.

[0172] Figure 2626 is a diagram illustrating an example of a hardware implementation for an apparatus 2604. The apparatus 2604 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 2604 may include a cellular baseband processor 2624 (also referred to as a modem) coupled to one or more transceivers 2622 (e.g., a cellular RF transceiver). The cellular baseband processor 2624 may include on-chip memory 2624′. In some aspects, the apparatus 2604 may also include one or more subscriber identity module (SIM) cards 2620 and an application processor 2606 coupled to a secure digital (SD) card 2608 and a screen 2610. The application processor 2606 may include on-chip memory 2606′. In some aspects, the device 2604 may also include a Bluetooth module 2612, a WLAN module 2614, an SPS module 2616 (e.g., a GNSS module), one or more sensor modules 2618 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial measurement 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 2626, a power source 2630, and / or a camera 2632. The Bluetooth module 2612, the WLAN module 2614, and the SPS module 2616 may include an on-chip transceiver (TRX) (or, in some cases, only a receiver (RX)). The Bluetooth module 2612, the WLAN module 2614, and the SPS module 2616 may include their own dedicated antennas and / or utilize an antenna 2680 for communication. The cellular baseband processor 2624 communicates with the UE 104 and / or RUs associated with the network entity 2602 via the transceiver 2622 via one or more antennas 2680. The cellular baseband processor 2624 and the application processor 2606 may each include computer-readable media / memory 2624', 2606', respectively. The additional memory module 2626 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 2624', 2606', 2626 may be non-transitory. The cellular baseband processor 2624 and the application processor 2606 are each responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the cellular baseband processor 2624 / application processor 2606, this software enables the cellular baseband processor 2624 / application processor 2606 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 2624 / application processor 2606 when executing the software.The cellular baseband processor 2624 / application processor 2606 may be a component of the UE 350 and may include the memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the device 2604 may be a processor chip (modem and / or applications) and include only the cellular baseband processor 2624 and / or the application processor 2606, and in another configuration, the device 2604 may be the entire UE (e.g., see ). Figure 3 UE 350) and includes additional modules of device 2604.

[0173] As discussed above, beam deflection information exchange component 198 can be configured to obtain beam deflection information associated with a set of beams at multiple center frequencies for a network node. Beam deflection information exchange component 198 can also be configured to send, to a network entity, beam deflection information for at least one beam in the set of beams used for a positioning session. Beam deflection information exchange component 198 can also be configured to participate in a positioning session with the network entity via the at least one beam based on the beam deflection information. Beam deflection information exchange component 198 can be within cellular baseband processor 2624, application processor 2606, or both. Beam deflection information exchange component 198 can be one or more hardware components specifically configured to perform the described processes / algorithms, implemented by one or more processors configured to perform the described processes / algorithms, stored on a computer-readable medium for implementation by one or more processors, or some combination thereof. As shown, apparatus 2604 can include various components configured for various functions. In one configuration, the apparatus 2604 (and in particular the cellular baseband processor 2624 and / or the application processor 2606) may include means for obtaining beam deflection information associated with a set of beams for a network node at a plurality of center frequencies. The apparatus 2604 may also include means for transmitting, to a network entity, beam deflection information for at least one beam in the set of beams used for a positioning session. The apparatus 2604 may also include means for participating in a positioning session with the network entity via the at least one beam based on the beam deflection information.

[0174] In one configuration, the beam deflection information for each beam in the beam set may include at least one of the following: a set of EIRP measurements for a plurality of center frequencies at different angles, a first difference between a set of EIRP measurements for a reference center frequency among the plurality of center frequencies and one or more non-reference center frequencies among the plurality of center frequencies at different angles, an angle of maximum EIRP measurement for each of the plurality of center frequencies, a second difference between an angle of maximum EIRP measurement for a reference center frequency among the plurality of center frequencies and one or more non-reference center frequencies among the plurality of center frequencies, or a combination thereof. In another configuration, the beam deflection information for one or more beams in the beam set may be obtained based on interpolation.

[0175] In another configuration, the beam deflection information may be stored in a memory or storage device of the device 2604, and the means for obtaining the beam deflection information may include configuring the device 2604 to load the beam deflection information for at least one beam in the beam set from the memory or storage device of the device 2604.

[0176] In another configuration, the beam set may include one or more Tx beams, one or more Rx beams, or a combination thereof.

[0177] In another configuration, the means for transmitting beam deflection information for at least one beam in the set of beams may include configuring the apparatus 2604 to receive a request to provide beam deflection information from a network entity via a capability request message, and to transmit the beam deflection information for one or more beams in the set of beams to the network entity via a capability indication message in response to the capability request message. In some implementations, the capability request message and the capability indication message may be associated with at least one of a capability transfer procedure or a capability indication procedure.

[0178] In one configuration, the means for transmitting beam deflection information for at least one beam in the set of beams may include configuring the apparatus 2604 to receive a request to perform a positioning session from a network entity via a request message, and to transmit beam deflection information for one or more beams in the set of beams to be used for the positioning session to the network entity via a provide message. In some implementations, the request message and the provide message may be associated with a location information transfer procedure.

[0179] In another configuration, the apparatus 2604 may be a UE, and the apparatus 2604 may further include means for receiving, from a network entity, second beam deflection information associated with at least one Tx beam associated with a positioning session of at least one TRP. In some implementations, the second beam deflection information may be received via assistance data or a request location information message. In some implementations, if the positioning session is associated with AoD positioning, the apparatus 2604 may further include means for receiving a PRS set from at least one Tx beam of the at least one TRP, and means for estimating an AoD for the PRS set based on the second beam deflection information.

[0180] In another configuration, the apparatus 2604 may be a base station and the network entity may be a location server or a LMF, and the apparatus 2604 may further include means for receiving a request for providing beam deflection information from the location server or the LMF via a TRP information request message, and means for sending beam deflection information for one or more beams in the beam set to the location server or the LMF via a TRP information response message in response to the TRP information request message. In some implementations, the TRP information request message and the TRP information response message may be associated with a TRP information exchange procedure.

[0181] In another configuration, the apparatus 2604 may be a base station and the network entity may be a location server or LMF. The apparatus 2604 may further include means for receiving a request to perform a positioning session from the location server or LMF via a request message, and means for sending, to the network entity, via a provide message, beam deflection information for one or more beams in the beam set to be used for the positioning session. In some implementations, the request message and the provide message may be associated with a positioning information exchange procedure or a measurement information exchange procedure. In some implementations, the positioning session may be associated with AoA positioning, and the one or more beams in the beam set may include an Rx beam set for the base station.

[0182] In another configuration, the apparatus 2604 is a base station and the network entity is a location server or LMF, and the apparatus 2604 may further include means for receiving, from the location server or LMF, second beam deflection information associated with at least one transmit Tx beam of the UE associated with the positioning session. In some implementations, the second beam deflection information may be received via an assistance information control message associated with an assistance information exchange procedure or via a positioning information request message associated with a positioning information exchange procedure. In some implementations, the positioning session may be associated with AoA positioning, and the apparatus 2604 may further include means for receiving an SRS set from at least one Tx beam of the UE, and means for estimating an AoA for the SRS set based on the second beam deflection information.

[0183] The means may be the beam deflection information exchange component 198 of the apparatus 2604 configured to perform the functions recited by the means. As described above, the apparatus 2604 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.

[0184] Figure 27 2700 is a flow chart of a method for wireless communication. The method may be performed by a network entity (e.g., one or more location servers 168; servers 804, 1704; network entity 2960). The method may enable the network entity to receive beam deflection information from one or more positioning entities and / or transmit beam deflection information from one positioning entity to another positioning entity to improve the accuracy and reliability of UE positioning.

[0185] At 2702, a network entity may receive, from a network node, beam skew information associated with at least one beam in a set of beams of the network node for a positioning session, such as in conjunction with Figure 8A 、 Figure 8B 、 Figure 13 、 Figure 17A 、 Figure 17B 、 Figure 17C and Figure 20 For example, as described in conjunction with Figure 8A As discussed above at 808, the server 804 may receive beam deflection information associated with at least one beam in the set of beams of the target 802 for the positioning session. The beam deflection information may be received by, for example, Figure 29 The beam deflection information exchange component 197 and / or the network interface 2980 of the network entity 2960 is executed.

[0186] At 2704, the network entity may participate in a positioning session with a network node via at least one beam based on the beam deflection information, such as in conjunction with Figure 8A 、 Figure 8B 、 Figure 13 、 Figure 17A 、 Figure 17B 、 Figure 17C and Figure 20 For example, after the server 804 receives the beam deflection information from the target 802, the server 804 may perform UE positioning or positioning measurement based on the beam deflection information. The beam deflection information may be received by, for example, Figure 29 The beam deflection information exchange component 197 and / or the network interface 2980 of the network entity 2960 is executed.

[0187] In one example, the beam deflection information for each beam in the beam set may include at least one of: a set of EIRP measurements for a plurality of center frequencies at different angles, a first difference between a set of EIRP measurements for a reference center frequency among the plurality of center frequencies and one or more non-reference center frequencies among the plurality of center frequencies at different angles, an angle of maximum EIRP measurement for each of the plurality of center frequencies, a second difference between an angle of maximum EIRP measurement for a reference center frequency among the plurality of center frequencies and one or more non-reference center frequencies among the plurality of center frequencies, or a combination thereof.

[0188] In another example, as shown at 2706, in order to receive beam deflection information for at least one beam in a beam set, the network node may send a request for providing beam deflection information to the network entity via a capability request message, and the network entity may receive beam deflection information for one or more beams in the beam set from the network node via a capability indication message in response to the capability request message.

[0189] In another example, as shown at 2708, in order to receive beam deflection information for at least one beam in a beam set, the network entity may send a request to perform a positioning session to a network node via a request message; and receive beam deflection information for one or more beams in the beam set to be used for the positioning session from the network node via a provide message.

[0190] In another example, the network node is a UE, and the network node may send second beam deflection information associated with at least one Tx beam associated with the positioning session of at least one TRP to the UE.

[0191] In another example, the network node is a base station and the network entity is a location server or LMF, the network entity can send a request for providing beam deflection information to the base station via a TRP information request message, and the network entity can receive beam deflection information for one or more beams in the beam set from the base station via a TRP information response message in response to the TRP information request message.

[0192] In another example, the network node is a base station and the network entity is a location server or LMF, the network entity can send a request to the base station to perform a positioning session via a request message, and the network entity can send beam deflection information for one or more beams in a beam set to be used for the positioning session to the network entity via a provide message.

[0193] In another example, the network node may be a base station and the network entity may be a location server or LMF, and the network entity may send second beam deflection information associated with at least one Tx beam of the UE associated with the positioning session to the base station.

[0194] Figure 28 2800 is a flow chart of a method for wireless communication. The method may be performed by a network entity (e.g., one or more location servers 168; servers 804, 1704; network entity 2960). The method may enable the network entity to receive beam deflection information from one or more positioning entities and / or transmit beam deflection information from one positioning entity to another positioning entity to improve the accuracy and reliability of UE positioning.

[0195] At 2802, a network entity may receive, from a network node, beam skew information associated with at least one beam in a beam set of the network node for a positioning session, such as in conjunction with Figure 8A 、 Figure 8B 、 Figure 13 、 Figure 17A 、 Figure 17B 、 Figure 17C and Figure 20 For example, as described in conjunction with Figure 8A As discussed above at 808, the server 804 may receive beam deflection information associated with at least one beam in the set of beams of the target 802 for the positioning session. The beam deflection information may be received by, for example, Figure 29 The beam deflection information exchange component 197 and / or the network interface 2980 of the network entity 2960 is executed.

[0196] At 2804, the network entity may participate in a positioning session with a network node via at least one beam based on the beam deflection information, such as in conjunction with Figure 8A 、 Figure 8B 、 Figure 13 、 Figure 17A 、 Figure 17B 、 Figure 17C and Figure 20 For example, after the server 804 receives the beam deflection information from the target 802, the server 804 may perform UE positioning or positioning measurement based on the beam deflection information. The beam deflection information may be received by, for example, Figure 29 The beam deflection information exchange component 197 and / or the network interface 2980 of the network entity 2960 is executed.

[0197] In one example, the beam deflection information for each beam in the beam set may include at least one of: a set of EIRP measurements for a plurality of center frequencies at different angles, a first difference between a set of EIRP measurements for a reference center frequency among the plurality of center frequencies and one or more non-reference center frequencies among the plurality of center frequencies at different angles, an angle of maximum EIRP measurement for each of the plurality of center frequencies, a second difference between an angle of maximum EIRP measurement for a reference center frequency among the plurality of center frequencies and one or more non-reference center frequencies among the plurality of center frequencies, or a combination thereof.

[0198] In another example, in order to receive beam deflection information for at least one beam in a beam set, the network node may send a request for providing beam deflection information to the network entity via a capability request message, and the network entity may receive beam deflection information for one or more beams in the beam set from the network node via a capability indication message in response to the capability request message.

[0199] In another example, in order to receive beam deflection information for at least one beam in a beam set, the network entity may send a request to perform a positioning session to a network node via a request message; and receive beam deflection information for one or more beams in the beam set to be used for the positioning session from the network node via a provide message.

[0200] In another example, the network node is a UE, and the network node may send second beam deflection information associated with at least one Tx beam associated with the positioning session of at least one TRP to the UE.

[0201] In another example, the network node is a base station and the network entity is a location server or LMF, the network entity can send a request for providing beam deflection information to the base station via a TRP information request message, and the network entity can receive beam deflection information for one or more beams in the beam set from the base station via a TRP information response message in response to the TRP information request message.

[0202] In another example, the network node is a base station and the network entity is a location server or LMF, the network entity can send a request to the base station to perform a positioning session via a request message, and the network entity can send beam deflection information for one or more beams in a beam set to be used for the positioning session to the network entity via a provide message.

[0203] In another example, the network node may be a base station and the network entity may be a location server or LMF, and the network entity may send second beam deflection information associated with at least one Tx beam of the UE associated with the positioning session to the base station.

[0204] Figure 29 FIG2900 is a diagram illustrating an example of a hardware implementation for a network entity 2960. In one example, the network entity 2960 may be located within the core network 120. The network entity 2960 may include a network processor 2912. The network processor 2912 may include on-chip memory 2912′. In some aspects, the network entity 2960 may also include an additional memory module 2914. The network entity 2960 communicates with the CU 2902 directly (e.g., a backhaul link) or indirectly (e.g., through an RIC) via a network interface 2980. The on-chip memory 2912′ and the additional memory module 2914 may each be considered a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. The processor 2912 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the corresponding processor, the software 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.

[0205] As discussed above, beam deflection information exchange component 197 can be configured to receive, from a network node, beam deflection information associated with at least one beam in the network node's beam set that is used for a positioning session. Beam deflection information exchange component 197 can also be configured to participate in a positioning session with the network node via the at least one beam based on the beam deflection information. Beam deflection information exchange component 197 can be within processor 2912. Beam deflection information exchange component 197 can be one or more hardware components specifically configured to perform the recited processes / algorithms, implemented by one or more processors configured to perform the recited processes / algorithms, stored on a computer-readable medium for implementation by one or more processors, or some combination thereof. Network entity 2960 can include various components configured for various functions. In one configuration, network entity 2960 can include means for receiving, from a network node, beam deflection information associated with at least one beam in the network node's beam set that is used for a positioning session. The network entity 2960 may also include means for participating in a positioning session with a network node via at least one beam based on the beam deflection information.

[0206] In one configuration, the beam deflection information for each beam in the beam set may include at least one of: a set of EIRP measurements for a plurality of center frequencies at different angles, a first difference between a set of EIRP measurements for a reference center frequency among the plurality of center frequencies and one or more non-reference center frequencies among the plurality of center frequencies at different angles, an angle of a maximum EIRP measurement for each of the plurality of center frequencies, a second difference between an angle of a maximum EIRP measurement for a reference center frequency among the plurality of center frequencies and one or more non-reference center frequencies among the plurality of center frequencies, or a combination thereof.

[0207] In another configuration, the component for receiving beam deflection information for at least one beam in a beam set may include configuring the network entity 2960 to: send a request for providing beam deflection information to a network node via a capability request message, and receive beam deflection information for one or more beams in a beam set from the network node via a capability indication message in response to the capability request message.

[0208] In another configuration, the component for receiving beam deflection information for at least one beam in a beam set may include configuring the network entity 2960 to: send a request to perform a positioning session to a network node via a request message; and receive beam deflection information for one or more beams in the beam set to be used for the positioning session from the network node via a provide message.

[0209] In another configuration, the network node is a UE, and the network entity 2960 may further include a component for sending second beam deflection information associated with at least one Tx beam associated with the positioning session of at least one TRP to the UE.

[0210] In another configuration, the network node is a base station and the network entity is a location server or LMF, the network entity 2960 may also include a component for sending a request for providing beam deflection information to the base station via a TRP information request message, and a component for receiving beam deflection information for one or more beams in the beam set from the base station via a TRP information response message in response to the TRP information request message.

[0211] In another configuration, the network node is a base station and the network entity is a location server or LMF, the network entity 2960 may also include a component for sending a request to the base station to perform a positioning session via a request message, and a component for receiving beam deflection information for one or more beams in the beam set to be used for the positioning session from the base station via a provide message.

[0212] In another configuration, the network node may be a base station and the network entity may be a location server or LMF, the network entity 2960 may further include a component for sending second beam deflection information associated with at least one Tx beam of the UE associated with the positioning session to the base station.

[0213] The means may be the beam steering information exchange component 197 of the network entity 2960 configured to perform the functions recited by the means.

[0214] It should be understood that the specific order or hierarchy of blocks in the disclosed process / flowchart is merely illustrative of an exemplary method. It should be understood that the specific order or hierarchy of blocks in the process / flowchart may be rearranged based on design preferences. In addition, some blocks may be combined or omitted. The accompanying method claims provide elements of the various blocks in a sample order, but are not limited to the specific order or hierarchy provided.

[0215] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not limited to the aspects described herein, but should be given the full scope consistent with the language claims. Unless otherwise specified, references to elements in the singular form do not mean "one and only one", but "one or more". Terms such as "if", "when" and "while" do not imply a direct temporal relationship or reaction. That is, these phrases, such as "when...", do not mean 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 there is no need for a specific or immediate time limit for the action to occur. The word "exemplary" is used herein to mean "used as an example, instance or illustration". Any aspect described as "exemplary" herein is not necessarily to be interpreted as 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, which may include multiple As, multiple Bs, or multiple Cs. Specifically, combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “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, B, and C, where any such combination may include one or more members of A, B, or C. A set should be interpreted as a set of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If a first device receives data from a second device or sends data to a second device, the data may be received / sent directly between the first device and the second device, or indirectly between the first device and the second device through a collection of devices. A device configured to "output" data (such as, transmit, signal, or message) may, for example, send the data with a transceiver, or may transmit the data to a device that sends the data. A device configured to "obtain" data (such as, transmit, signal, or message) may, for example, receive the data with a transceiver, or may obtain the data from a device that receives the data. All structural and functional equivalents of the elements of the various aspects described throughout this disclosure that are known or later become known to those of ordinary skill in the art are expressly incorporated herein by reference and are encompassed by the claims.Furthermore, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly recited in the claims. Words such as "module," "mechanism," "element," and "device" are not intended to replace the word "component." Thus, no claim element is to be construed as part-plus-function unless the element is explicitly recited using the phrase "component for..."

[0216] 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.

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

[0218] Aspect 1 is a method for performing wireless communication at a network node, the method comprising: obtaining beam deflection information associated with a beam set of the network node at multiple center frequencies; sending the beam deflection information for at least one beam in the beam set for a positioning session to a network entity; and participating in the positioning session with the network entity via the at least one beam based on the beam deflection information.

[0219] Aspect 2 is a method according to Aspect 1, wherein the beam deflection information for each beam in the beam set includes at least one of the following items: an EIRP measurement set for the multiple center frequencies at different angles, a first difference between the EIRP measurement set of the reference center frequency among the multiple center frequencies and one or more non-reference center frequencies among the multiple center frequencies at the different angles, an angle of maximum EIRP measurement for each of the multiple center frequencies, a second difference between the angle of maximum EIRP measurement between the reference center frequency among the multiple center frequencies and the one or more non-reference center frequencies among the multiple center frequencies, or a combination thereof.

[0220] Aspect 3 is a method according to aspect 2, wherein the beam deflection information for one or more beams in the beam set is obtained based on interpolation.

[0221] Aspect 4 is a method according to any one of Aspects 1 to 3, wherein the beam deflection information is stored in a memory or storage device of the network node, and wherein obtaining the beam deflection information includes: loading the beam deflection information for at least one beam in the beam set from the memory or storage device of the network node.

[0222] Aspect 5 is a method according to any one of Aspects 1 to 4, wherein sending the beam deflection information for at least one beam in the beam set includes: receiving a request for providing the beam deflection information from the network entity via a capability request message; and sending the beam deflection information for one or more beams in the beam set to the network entity via a capability indication message in response to the capability request message.

[0223] Aspect 6 is the method according to aspect 5, wherein the capability request message and the capability indication message are associated with at least one of a capability transfer procedure or a capability indication procedure.

[0224] Aspect 7 is a method according to any one of Aspects 1 to 6, wherein sending the beam deflection information for at least one beam in the beam set includes: receiving a request to perform the positioning session from the network entity via a request message; and sending the beam deflection information for one or more beams in the beam set to be used for the positioning session to the network entity via a provide message.

[0225] Aspect 8 is the method according to aspect 7, wherein the request message and the provide message are associated with a location information delivery procedure.

[0226] Aspect 9 is a method according to any one of aspects 1 to 8, wherein the beam set includes one or more Tx beams, one or more Rx beams, or a combination thereof.

[0227] Aspect 10 is a method according to any one of Aspects 1 to 9, wherein the network node is a UE, and the method further includes: receiving second beam deflection information associated with at least one Tx beam associated with the positioning session of at least one TRP from the network entity.

[0228] Aspect 11 is a method according to aspect 10, wherein the second beam deflection information is received via assistance data or a request position information message.

[0229] Aspect 12 is a method according to Aspect 10, wherein the positioning session is associated with AoD positioning, and the method further includes: receiving a PRS set from the at least one Tx beam of the at least one TRP, and estimating the AoD for the PRS set based on the second beam deflection information.

[0230] Aspect 13 is a method according to any one of Aspects 1 to 12, wherein the network node is a base station and the network entity is a location server or LMF, and the method further includes: receiving a request for providing the beam deflection information from the location server or the LMF via a TRP information request message; and sending the beam deflection information for one or more beams in the beam set to the location server or the LMF via a TRP information response message in response to the TRP information request message.

[0231] Aspect 14 is a method according to aspect 13, wherein the TRP information request message and the TRP information response message are associated with a TRP information exchange process.

[0232] Aspect 15 is a method according to any one of Aspects 1 to 14, wherein the network node is a base station and the network entity is a location server or LMF, and the method further includes: receiving a request to perform the positioning session from the location server or the LMF via a request message; and sending the beam deflection information for one or more beams in the beam set to be used for the positioning session to the network entity via a provide message.

[0233] Aspect 16 is the method according to aspect 15, wherein the request message and the provide message are associated with a positioning information exchange procedure or a measurement information exchange procedure.

[0234] Aspect 17 is a method according to aspect 15, wherein the positioning session is associated with AoA positioning, and the one or more beams in the beam set include an Rx beam set for the base station.

[0235] Aspect 18 is a method according to any one of Aspects 1 to 17, wherein the network node is a base station and the network entity is a location server or LMF, and the method further includes: receiving second beam deflection information associated with at least one Tx beam of the UE associated with the positioning session from the location server or the LMF.

[0236] Aspect 19 is a method according to aspect 18, wherein the second beam deflection information is received via an assistance information control message associated with an assistance information exchange procedure or via a positioning information request message associated with a positioning information exchange procedure.

[0237] Aspect 20 is a method according to aspect 18, wherein the positioning session is associated with AoA positioning, and the method further includes: receiving an SRS set from the at least one Tx beam of the UE; and estimating the AoA for the SRS set based on the second beam deflection information.

[0238] Aspect 21 is an apparatus for wireless communication at a network node, the apparatus comprising: a memory; and at least one processor coupled to the memory, and based at least in part on information stored in the memory, the at least one processor is configured to implement any one of aspects 1 to 20.

[0239] Aspect 22 is the apparatus of aspect 21, further comprising at least one of a transceiver or an antenna coupled to the at least one processor.

[0240] Aspect 23 is an apparatus for wireless communication, comprising means for implementing any one of aspects 1 to 20.

[0241] Aspect 24 is a computer-readable medium (eg, non-transitory 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 20.

[0242] Aspect 25 is a method for wireless communication at a network entity, the method comprising: receiving beam deflection information associated with at least one beam in a beam set of the network node for a positioning session from a network node; and participating in the positioning session with the network node via the at least one beam based on the beam deflection information.

[0243] Aspect 26 is a method according to Aspect 25, wherein the beam deflection information for each beam in the beam set includes at least one of the following items: a set of EIRP measurements for multiple center frequencies at different angles, a first difference between the EIRP measurement sets of a reference center frequency among the multiple center frequencies and one or more non-reference center frequencies among the multiple center frequencies at the different angles, an angle of maximum EIRP measurement for each of the multiple center frequencies, a second difference between the angle of maximum EIRP measurement between the reference center frequency among the multiple center frequencies and the one or more non-reference center frequencies among the multiple center frequencies, or a combination thereof.

[0244] Aspect 27 is a method according to aspect 25 or 26, wherein receiving the beam deflection information for at least one beam in the beam set includes: sending a request for providing the beam deflection information to the network node via a capability request message; and receiving the beam deflection information for one or more beams in the beam set from the network node via a capability indication message in response to the capability request message.

[0245] Aspect 28 is a method according to any one of Aspects 25 to 27, wherein receiving the beam deflection information for at least one beam in the beam set includes: sending a request to perform the positioning session to the network node via a request message; and receiving the beam deflection information for one or more beams in the beam set to be used for the positioning session from the network node via a provide message.

[0246] Aspect 29 is a method according to any one of Aspects 25 to 28, wherein the network node is a UE, and the method further includes: sending second beam deflection information associated with at least one Tx beam associated with the positioning session of at least one TRP to the UE.

[0247] Aspect 30 is a method according to any one of Aspects 25 to 29, wherein the network node is a base station and the network entity is a location server or LMF, and the method further includes: sending a request for providing the beam deflection information to the base station via a TRP information request message; and receiving the beam deflection information for one or more beams in the beam set from the base station via a TRP information response message in response to the TRP information request message.

[0248] Aspect 31 is a method according to any one of Aspects 25 to 30, wherein the network node is a base station and the network entity is a location server or LMF, and the method further includes: sending a request to perform the positioning session to the base station via a request message; and receiving the beam deflection information for one or more beams in the beam set to be used for the positioning session from the base station via a provide message.

[0249] Aspect 32 is a method according to any one of aspects 25 to 31, wherein the network node is a base station and the network entity is a location server or a LMF, the method further comprising:

[0250] Second beam deflection information associated with at least one Tx beam of the UE associated with the positioning session is sent to the base station.

[0251] Aspect 33 is an apparatus for wireless communication at a network entity, the apparatus comprising: a memory; and at least one processor coupled to the memory, and based at least in part on information stored in the memory, the at least one processor is configured to implement any one of aspects 25 to 32.

[0252] Aspect 34 is the apparatus of aspect 33, further comprising at least one of a transceiver or an antenna coupled to the at least one processor.

[0253] Aspect 35 is an apparatus for wireless communication, comprising means for implementing any one of aspects 25 to 32.

[0254] Aspect 36 is a computer-readable medium (eg, non-transitory computer-readable medium) storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 25 to 32 .

Claims

1. An apparatus for wireless communication at a network node, the apparatus comprising: Memory; and at least one processor coupled to the memory, and the at least one processor configured to: Obtaining beam skew information associated with a beam set of the network node at a plurality of center frequencies; sending, to a network entity, the beam deflection information for at least one beam in the set of beams used for a positioning session; as well as The positioning session is participated in with the network entity via the at least one beam based on the beam deflection information.

2. The apparatus according to claim 1 , wherein the beam deflection information for each beam in the set of beams comprises at least one of the following: a set of equivalent isotropic radiated power (EIRP) measurements for the plurality of center frequencies at different angles, a first difference between the EIRP measurement sets of a reference center frequency among the multiple center frequencies and one or more non-reference center frequencies among the multiple center frequencies at the different angles; an angle of maximum EIRP measurement for each of the plurality of center frequencies, a second difference between angles of maximum EIRP measurements of the reference center frequency among the plurality of center frequencies and the one or more non-reference center frequencies among the plurality of center frequencies, or A combination of them. 3 . The apparatus of claim 2 , wherein the at least one processor is configured to obtain the beam deflection information for one or more beams in the set of beams based on interpolation.

4. The apparatus of claim 1 , wherein the beam deflection information is configured to be stored in the memory or storage device of the network node, and wherein to obtain the beam deflection information, the at least one processor is configured to: The beam skew information for the at least one beam in the set of beams is loaded from the memory or the storage device of the network node.

5. The apparatus of claim 1 , wherein to transmit the beam deflection information for the at least one beam in the set of beams, the at least one processor is configured to: receiving a request to provide the beam deflection information from the network entity via a capability request message; and The beam deflection information for one or more beams in the set of beams is sent to the network entity via a capability indication message in response to the capability request message. 6 . The apparatus of claim 5 , wherein the capability request message and the capability indication message are associated with at least one of a capability transfer procedure or a capability indication procedure.

7. The apparatus of claim 1 , wherein to transmit the beam deflection information for the at least one beam in the set of beams, the at least one processor is configured to: receiving a request to perform the positioning session from the network entity via a request message; and The beam deflection information for one or more beams in the set of beams to be used for the positioning session is sent to the network entity via a provide message. The apparatus of claim 7 , wherein the request message and the provide message are associated with a location information delivery procedure.

9. The apparatus of claim 1, wherein the beam set comprises one or more transmit (Tx) beams, one or more receive (Rx) beams, or a combination thereof.

10. The apparatus of claim 1 , wherein the network node is a user equipment (UE), and wherein the at least one processor is further configured to: Second beam skew information associated with at least one transmit (Tx) beam associated with the positioning session of at least one transmit-receive point (TRP) is received from the network entity.

11. The apparatus of claim 10, wherein the at least one processor is configured to receive the second beam deflection information via assistance data or a request position information message.

12. The apparatus of claim 10, wherein the positioning session is associated with angle of departure (AoD) positioning, and wherein the at least one processor is further configured to: receiving a set of positioning reference signals (PRSs) from the at least one Tx beam of the at least one TRP; and The AoD for the PRS set is estimated based on the second beam steering information.

13. The apparatus of claim 1 , wherein the network node is a base station and the network entity is a location server or a location management function (LMF), and wherein the at least one processor is further configured to: receiving a request to provide the beam tilt information from the location server or the LMF via a transmit-receive point (TRP) information request message; and The beam deflection information for one or more beams in the beam set is sent to the location server or the LMF via a TRP information response message in response to the TRP information request message.

14. The apparatus according to claim 13, wherein the TRP information request message and the TRP information response message are associated with a TRP information exchange process.

15. The apparatus of claim 1 , wherein the network node is a base station and the network entity is a location server or a location management function (LMF), and wherein the at least one processor is further configured to: receiving a request to perform the positioning session from the location server or the LMF via a request message; and The beam deflection information for one or more beams in the set of beams to be used for the positioning session is sent to the network entity via a provide message. 16 . The apparatus of claim 15 , wherein the request message and the offer message are associated with a positioning information exchange procedure or a measurement information exchange procedure.

17. The apparatus of claim 15, wherein the positioning session is associated with angle-of-arrival (AoA) positioning, and the one or more beams in the set of beams comprise a receive (Rx) beam set for the base station.

18. The apparatus of claim 1 , wherein the network node is a base station and the network entity is a location server or a location management function (LMF), and wherein the at least one processor is further configured to: Second beam skew information associated with at least one transmit (Tx) beam of a user equipment (UE) associated with the positioning session is received from the location server or the LMF.

19. The apparatus of claim 18, wherein the at least one processor is configured to receive the second beam deflection information via an assistance information control message associated with an assistance information exchange procedure or via a positioning information request message associated with a positioning information exchange procedure.

20. The apparatus of claim 18, wherein the positioning session is associated with angle-of-arrival (AoA) positioning, and wherein the at least one processor is further configured to: receiving a sounding reference signal (SRS) set from the at least one Tx beam of the UE; and The AoA for the SRS set is estimated based on the second beam skew information.

21. A method for wireless communication at a network node, the method comprising: Obtaining beam skew information associated with a beam set of the network node at a plurality of center frequencies; sending, to a network entity, the beam deflection information for at least one beam in the set of beams used for a positioning session; as well as The positioning session is participated in with the network entity via the at least one beam based on the beam deflection information.

22. An apparatus for wireless communication at a network entity, the apparatus comprising: Memory; and at least one processor coupled to the memory, and the at least one processor configured to: receiving, from a network node, beam skew information associated with at least one beam in a set of beams of the network node for use in a positioning session; and and engaging in the positioning session with the network node via the at least one beam based on the beam deflection information.

23. The apparatus of claim 22, wherein the beam deflection information for each beam in the set of beams comprises at least one of: A collection of Equivalent Isotropic Radiated Power (EIRP) measurements at various center frequencies at different angles. a first difference between the EIRP measurement sets of a reference center frequency among the multiple center frequencies and one or more non-reference center frequencies among the multiple center frequencies at the different angles; an angle of maximum EIRP measurement for each of the plurality of center frequencies, a second difference between angles of maximum EIRP measurements of the reference center frequency among the plurality of center frequencies and the one or more non-reference center frequencies among the plurality of center frequencies, or A combination of them.

24. The apparatus of claim 22, wherein to receive the beam deflection information for the at least one beam in the set of beams, the at least one processor is configured to: sending a request for providing the beam deflection information to the network node via a capability request message; and The beam skew information for one or more beams in the set of beams is received from the network node via a capability indication message in response to the capability request message.

25. The apparatus of claim 22, wherein to receive the beam deflection information for the at least one beam in the set of beams, the at least one processor is configured to: sending a request to the network node to perform the positioning session via a request message; and The beam skew information for one or more beams in the set of beams to be used for the positioning session is received from the network node via a provide message.

26. The apparatus of claim 22, wherein the network node is a user equipment (UE), and wherein the at least one processor is further configured to: Second beam deflection information associated with at least one transmit (Tx) beam associated with the positioning session of at least one transmit-receive point (TRP) is sent to the UE.

27. The apparatus of claim 22, wherein the network node is a base station and the network entity is a location server or a location management function (LMF), and wherein the at least one processor is further configured to: sending a request for providing the beam deflection information to the base station via a transmit-receive point (TRP) information request message; and The beam deflection information for one or more beams in the beam set is received from the base station via a TRP information response message in response to the TRP information request message.

28. The apparatus of claim 22, wherein the network node is a base station and the network entity is a location server or a location management function (LMF), and wherein the at least one processor is further configured to: Sending a request to the base station to perform the positioning session via a request message; and The beam deflection information for one or more beams in the set of beams to be used for the positioning session is received from the base station via a provide message.

29. The apparatus of claim 22, wherein the network node is a base station and the network entity is a location server or a location management function (LMF), and wherein the at least one processor is further configured to: Second beam deflection information associated with at least one transmit (Tx) beam of a user equipment (UE) associated with the positioning session is transmitted to the base station.

30. A method of wireless communication at a network entity, the method comprising: receiving, from a network node, beam skew information associated with at least one beam in a set of beams of the network node for use in a positioning session; as well as and engaging in the positioning session with the network node via the at least one beam based on the beam deflection information.

Images