Codebook configuration for device positioning

Abstract

Aspects of the present disclosure relate to methods, apparatuses, and systems for supporting codebook configuration for device positioning. For example, implementations provide codebook configuration based on various criteria related to a network configuration entity (e.g., a location and mobility function (LMF)), a target UE node (e.g., a UE whose location is to be determined), and / or a positioning anchor node (e.g., a node transmitting a positioning reference signal (PRS)). For example, these criteria represent attributes of different nodes that may affect codebook configuration and / or complexity. Using the configured codebook, the target UE may process the received PRS to determine different location-related parameters of the target UE. The target UE may send the location-related parameters to different nodes (e.g., network entities) to enable the different nodes to process the location-related parameters to estimate the location of the target UE.

Description

[0001] Related Applications

[0002] This application claims priority to U.S. Provisional Application Serial No. 63 / 406,466, filed on September 14, 2022, entitled “CODEBOOK CONFIGURATION FOR DEVICEPOSITIONING,” the disclosure of which is incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates to wireless communications and, more particularly, to position determination in wireless communications. Background Art

[0004] A wireless communication system may include one or more network communication devices (such as base stations), which may be referred to as eNodeB (eNB), next generation NodeB (gNB) or other suitable terms. Each network communication device (such as a base station) may support wireless communication for one or more user communication devices, which may also be referred to as user equipment (UE) or other suitable terms. A wireless communication system may support wireless communication with one or more user communication devices by utilizing resources of a wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)). In addition, a wireless communication system may support wireless communication across various radio access technologies, including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, and other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)).

[0005] Some wireless communication systems provide methods for device positioning, such as for UE positioning. However, some technologies do not support efficient configuration of logic for device positioning that takes into account device properties and / or use case details. Summary of the invention

[0006] The present disclosure relates to methods, apparatus, and systems for supporting codebook configuration for device positioning. For example, implementations provide codebook configuration based on various standards related to a network configuration entity (e.g., a location and mobility function (LMF)), a target UE node (e.g., a UE whose position is to be determined), and / or a positioning anchor node (e.g., a node that sends a positioning reference signal (PRS)). For example, these standards represent properties of different nodes that may affect codebook configuration and / or complexity. Using the configured codebook, the target UE can process the received PRS to determine different location-related parameters of the target UE. The target UE can send location-related parameters to different nodes (e.g., a network entity) so that different nodes can process the location-related parameters to estimate the location of the target UE.

[0007] By utilizing the described techniques, as part of position estimation, the codebook configuration used for position determination can be dynamically adapted to different device properties and / or scenarios, such as to improve position determination accuracy and reduce the burden on system resources (e.g., power, processing, data transmission, etc.).

[0008] Some implementations of the methods and apparatus described herein may also include generating, at a first device, a notification including a codebook configuration including codebook boundaries and a number of positioning reference signal features used to form a codebook for a second device, the number of positioning reference signal features being based at least in part on one or more criteria; sending the notification to the second device; receiving a positioning measurement generated by the second device based at least in part on the codebook configuration; and generating a position estimate for the second device based at least in part on the positioning measurement.

[0009] Some implementations of the methods and devices described herein may also include: wherein the positioning reference signal characteristics include one or more of the following items: the number of positioning reference signal codewords in each dimension, or the number of positioning reference signal beams in each dimension; one or more standards include one or more of the following items: one or more capabilities of the second device, one or more positioning accuracy characteristics of the first device, a power usage parameter of the second device, a maximum delay parameter of the first device, a mobility state of the second device, a codebook boundary of the second device, or a positioning reference signal time-frequency resource configuration of the second device; also including sending a positioning reference signal to the second device; the position estimate of the second device includes one or more of the following items: the absolute position of the second device, the relative position of the second device, or a distance estimate including one or more of the following items: a distance or relative direction relative to the first device or one or more of the devices sending the positioning reference signal to the second device; the positioning measurement is based at least in part on one or more of the following items: an uplink positioning measurement, a downlink positioning measurement, or a sidelink positioning measurement; the first device includes a network configuration entity, and the second device includes a UE; also including receiving an indication of a change in one or more standards; and dynamically adjusting the codebook configuration based on the change in one or more standards.

[0010] Some implementations of the methods and apparatus described herein may also include receiving, at a first apparatus, a notification including a codebook configuration, the codebook configuration including codebook boundaries and a number of positioning reference signal features used to form a codebook for the first apparatus; generating a codebook based at least in part on the codebook configuration; receiving a positioning reference signal; generating a positioning measurement based at least in part on the positioning reference signal and the codebook; and sending the positioning measurement to a second apparatus.

[0011] Some implementations of the methods and devices described herein may also include: wherein the positioning reference signal characteristics include one or more of the following items: the number of positioning reference signal codewords in each dimension, or the number of positioning reference signal beams in each dimension; generating a positioning measurement includes processing the positioning reference signal using codewords forming a codebook; also includes processing one or more paths of a channel impulse response (CIR) to generate a positioning measurement; also includes using one or more codebook-based methods to generate the positioning measurement; one or more codebook-based methods include multiple signal classification (MUSIC); also includes generating the positioning measurement based at least in part on one or more of the following items: an uplink positioning measurement, a downlink positioning measurement, or a sidelink positioning measurement; the first device includes a UE, and the second device includes one or more of the following items: a device for sending a notification, or a device for sending a positioning reference signal.

[0012] Some implementations of the methods and devices described herein may also include: generating, at a first device, a first notification including a codebook configuration of a second device, the codebook configuration including codebook boundaries and a number of positioning reference signal beams used to form a codebook for the second device, the number of positioning reference signal beams being based at least in part on a first set of criteria; generating, at the first device, a second notification including a codebook configuration of one or more third devices, the codebook configuration including codebook boundaries and a number of positioning reference signal beams used to form a codebook for one or more third devices, the number of positioning reference signal beams being based at least in part on a second set of criteria; sending the first notification to the second device, and sending the second notification to the one or more third devices; receiving a positioning measurement generated by the second device at least in part based on the codebook configuration of the second device; and generating a position estimate for the second device based at least in part on the positioning measurement.

[0013] Some implementations of the methods and apparatus described herein may also include: wherein one or more of the first set of criteria or the second set of criteria include one or more of the following: at least one of one or more capabilities of the second device or one or more capabilities of one or more third devices, one or more positioning accuracy characteristics of the first device, one or more power usage parameters of the second device or one or more power usage parameters of one or more third devices, a maximum delay parameter of the first device, one or more mobility states of the second device or one or more mobility states of one or more third devices, one or more codebook boundaries of the second device or one or more codebook boundaries of one or more third devices, or a positioning reference signal time-frequency information of the second device. One or more of the source configuration or the time-frequency resource configuration of the positioning reference signal of one or more third devices; the position estimate of the second device includes one or more of the following items: the absolute position of the second device, the relative position of the second device, or a distance estimate including one or more of the following items: the distance or relative direction relative to the first device or one or more devices sending the positioning reference signal to the second device; the positioning measurement is based at least in part on one or more of the following items: uplink positioning measurement, downlink positioning measurement or sidelink positioning measurement; the first device includes a network configuration entity, the second device includes a UE, and the one or more third devices include one or more devices that send a positioning reference signal to the second device.

[0014] Some implementations of the methods and devices described herein may also include: receiving, at a first device, a notification including a codebook configuration, the codebook configuration including codebook boundaries and a number of positioning reference signal beams used to form a codebook for the first device; generating a codebook based at least in part on the codebook configuration; receiving a beam including a positioning reference signal; generating a positioning measurement based at least in part on one or more positioning reference signals and the codebook from one or more beams having the strongest signal strength; and sending the positioning measurement to a second device.

[0015] Some implementations of the methods and apparatus described herein may also include: the beam including the positioning reference signal includes: one or more beams forming a codebook.

[0016] Some implementations of the methods and apparatus described herein may also include receiving, at a first device, a notification including a codebook configuration including codebook boundaries and a number of positioning reference signal beams used to form a codebook for the first device; generating a codebook based at least in part on the codebook configuration; and sending a beam including a positioning reference signal to a second device based at least in part on the codebook.

[0017] Some implementations of the methods and apparatus described herein may also include: the beam including the positioning reference signal includes: one or more beams forming a codebook. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 An example of a wireless communication system supporting codebook configuration for device positioning according to aspects of the present disclosure is illustrated.

[0019] Figure 2 A system in which PRS may be transmitted is illustrated.

[0020] Figure 3 A system providing an overview of absolute and relative positioning scenarios is illustrated.

[0021] Figure 4 A scenario of supporting codebook configuration for device positioning according to aspects of the present disclosure is illustrated.

[0022] Figure 5 A scenario of supporting codebook configuration for device positioning according to aspects of the present disclosure is illustrated.

[0023] Figure 6 and Figure 7 A system supporting codebook configuration for device positioning according to aspects of the present disclosure is illustrated.

[0024] Figure 8 and Fig. 9 An example of a block diagram of a device supporting codebook configuration for device positioning according to aspects of the present disclosure is illustrated.

[0025] Figures 10 to 14 A flowchart of a method for supporting codebook configuration for device positioning according to aspects of the present disclosure is illustrated. DETAILED DESCRIPTION

[0026] In wireless communication systems, positioning accuracy specifications can be defined based on applications and use cases, where non-critical scenarios can specify looser specifications compared to critical scenarios. For example, relaxing positioning accuracy specifications can reduce the use of system resources (e.g., time, frequency, power, etc.) and computational complexity. On the other hand, positioning estimation accuracy can depend on the estimation accuracy of location-related parameters (e.g., ToA, AoA, and AoD), where the location-related parameter estimation accuracy can be based on multiple factors, including a codebook utilized by a node (e.g., an anchor node, a target UE node, etc.). For example, a codebook can be used for various purposes, such as estimating location-related parameters from received PRS, sidelink positioning reference signal (SL-PRS), or sounding reference signal (SRS) CIR measurements using a codebook-based approach, and using a codebook beam to send and / or receive PRS, SL-PRS, or SRS signals. In implementation, the estimation accuracy, complexity, and delay of the codebook-based approach may be based on the number of codewords and / or beams forming the codebook, where more codewords and / or beams may provide better estimation accuracy at the expense of higher computational complexity and / or delay, and vice versa.

[0027] In addition, in order to maintain a certain positioning accuracy, the estimation accuracy of the location-related parameters can be improved as the distance between the anchor node and the target UE increases. Therefore, it is beneficial and necessary to adaptively adjust the estimation accuracy of the location-related parameters based on, for example, the desired positioning accuracy (e.g., based on the application and / or use case), the energy consumption limit of the estimation node, the maximum delay and latency, the mobility state of the anchor and the target UE, and the distance between the anchor node and the target UE. This can be achieved in various ways, for example, by adjusting system resources (e.g., time, frequency, power) and / or by adjusting the number of codebook codewords / beams.

[0028] Therefore, the present disclosure provides a technology for supporting codebook configuration for device positioning. For example, implementations provide codebook configuration based on various standards related to a network configuration entity (e.g., a location and mobility function (LMF)), a target UE node (e.g., a UE whose position is to be determined), and / or a positioning anchor node (e.g., a node that sends a PRS). For example, these standards represent attributes of different nodes that may affect codebook configuration and / or complexity. Using the configured codebook, the target UE can process the received PRS to determine different location-related parameters of the target UE. The target UE can send location-related parameters to different nodes (e.g., a network entity) so that different nodes can process the location-related parameters to estimate the location of the target UE.

[0029] By utilizing the described techniques, as part of position estimation, codebook configurations used for position determination can be dynamically adapted to different device properties and / or scenarios, such as to improve position determination accuracy and reduce burden on system resources (e.g., power, processing, data transmission, etc.).

[0030] Aspects of the disclosure are described in the context of a wireless communication system.Aspects of the disclosure are also illustrated and described with reference to device diagrams and flow diagrams.

[0031] Figure 1 An example of a wireless communication system 100 that supports codebook configuration for device positioning according to aspects of the present disclosure is illustrated. The wireless communication system 100 may include: one or more network entities 102, one or more UEs 104, a core network 106, and a packet data network 108. The wireless communication system 100 may support various radio access technologies. In some implementations, the wireless communication system 100 may be a 4G network, such as an LTE network or an advanced LTE (LTE-A) network. In some other implementations, the wireless communication system 100 may be a 5G network, such as an NR network. In other implementations, the wireless communication system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technologies, including the Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communication system 100 may support radio access technologies other than 5G. In addition, the wireless communication system 100 may support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).

[0032] One or more network entities 102 may be dispersed throughout a geographic area to form a wireless communication system 100. One or more of the network entities 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a RAN, a base transceiver station, an access point, a NodeB, an eNodeB (eNB), a next generation NodeB (gNB), or other suitable terms. The network entity 102 and the UE 104 may communicate via a communication link 110, which may be a wireless or wired connection. For example, the network entity 102 and the UE 104 may perform wireless communication (e.g., receive signaling, send signaling) via a Uu interface.

[0033] The network entity 102 may provide a geographic coverage area 112 for which the network entity 102 may support services (e.g., voice, video, packet data, messaging, broadcast, etc.) for one or more UEs 104 within the geographic coverage area 112. For example, the network entity 102 and the UE 104 may support wireless communications of signals associated with services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or more radio access technologies. In some implementations, the network entity 102 may be mobile, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but different geographic coverage areas 112 may be associated with different network entities 102. The information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0034] One or more UEs 104 may be dispersed throughout the geographic area of ​​the wireless communication system 100. UE 104 may include or may be referred to as a mobile device, a wireless device, a remote device, a remote unit, a handheld device, or a subscriber device, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, a station, a terminal, or a client, etc. Additionally or alternatively, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc. In some implementations, UE 104 may be stationary in the wireless communication system 100. In some other implementations, UE 104 may be mobile in the wireless communication system 100.

[0035] One or more UEs 104 may be devices in different forms or with different capabilities. Figure 1 Some examples of UE 104 are illustrated in FIG. Figure 1 As shown, the UE 104 may be able to communicate with various types of devices, such as a network entity 102, other UEs 104, or a network device (e.g., a core network 106, a packet data network 108, a relay device, an integrated access and backhaul (IAB) node, or another network device). Additionally or alternatively, the UE 104 may support communication with other network entities 102 or UEs 104 that may act as relays in the wireless communication system 100.

[0036] The UE 104 may also be capable of supporting wireless communications directly with other UEs 104 via a communication link 114. For example, the UE 104 may support wireless communications directly with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, V2X deployments, or cellular V2X deployments, the communication link 114 may be referred to as a sidelink. For example, the UE 104 may support wireless communications directly with another UE 104 via a PC5 interface.

[0037] The network entity 102 may support communication with the core network 106 or with another network entity 102 or with both. For example, the network entity 102 may be connected to the core network 106 via one or more backhaul links 116 (e.g., via S1, N2, N2 or another network interface). The network entities 102 may communicate with each other via the backhaul links 116 (e.g., via X2, Xn or another network interface). In some implementations, the network entities 102 may communicate directly with each other (e.g., between the network entities 102). In some other implementations, the network entities 102 may communicate with each other or indirectly (e.g., via the core network 106). In some implementations, one or more network entities 102 may include subcomponents, such as access network entities, which may be examples of access node controllers (ANCs). The ANC may communicate with one or more UEs 104 via one or more other access network transport entities (which may be referred to as radio heads, smart radio heads, or transport reception points (TRPs)).

[0038] In some implementations, the network entity 102 may be configured in a decomposed architecture, which may be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 102, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 102 may include one or more of the following: a central unit (CU), a distributed unit (DU), a radio unit (RU), a RAN intelligent controller (RIC) (e.g., a near real-time RIC (near real-time (RT) RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) system, or any combination thereof.

[0039] The RU may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmission reception point (TRP). In a decomposed RAN architecture, one or more components of the network entity 102 may be collocated, or one or more components of the network entity 102 may be located at distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0040] The functional split between CU, DU and RU can be flexible, and different functions can be supported according to the functions performed at the CU, DU or RU (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions and any combination thereof). For example, a functional split of a protocol stack can be adopted between a CU and a DU, so that the CU can support one or more layers of a protocol stack, and the DU can support one or more different layers of a protocol stack. In some implementations, the CU can host high-level protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functions and signaling (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), packet data convergence protocol (PDCP)). The CU can be connected to one or more DUs or RUs, and one or more DUs or RUs can host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, media access control (MAC) layer) functions and signaling, and each DU or RU can be at least partially controlled by the CU.

[0041] Additionally or alternatively, a functional split of the protocol stack may be employed between the DU and the RU such that the DU may support one or more layers of the protocol stack and the RU may support one or more different layers of the protocol stack. The DU may support one or more different cells (e.g., via one or more RUs). In some implementations, the functional split between the CU and the DU or between the DU and the RU may be within the protocol layer (e.g., some functions for the protocol layer may be performed by one of the CU, DU, or RU, while other functions of the protocol layer may be performed by different items of the CU, DU, or RU).

[0042] The CU may be further functionally split into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU may be connected to one or more DUs via a medium-range communication link (e.g., F1, F1-c, F1-u), and the DU may be connected to one or more RUs via a fronthaul communication link (e.g., an open fronthaul (FH) interface). In some implementations, the medium-range communication link or the fronthaul communication link may be implemented according to interfaces (e.g., channels) between layers of a protocol stack supported by a corresponding network entity 102 communicating via such a communication link.

[0043] The core network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The core network 106 may be an evolved packet core (EPC) or a 5G core (5GC), which may include: control plane entities that manage access and mobility (e.g., mobility management entity (MME), access and mobility management function (AMF)), and user plane entities that route packets or interconnections to external networks (e.g., serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearer, signal bearer, etc.) of one or more UEs 104 served by one or more network entities 102 associated with the core network 106.

[0044] The core network 106 may communicate with the packet data network 108 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). The packet data network 108 may include an application server 118. In some implementations, one or more UEs 104 may communicate with the application server 118. The UE 104 may establish a session (e.g., a protocol data unit (PDU) session, etc.) with the core network 106 via the network entity 102. The core network 106 may use the established session (e.g., the established PDU session) to route traffic (e.g., control information, data, etc.) between the UE 104 and the application server 118. The PDU session may be an example of a logical connection between the UE 104 and the core network 106 (e.g., one or more network functions of the core network 106).

[0045] In the wireless communication system 100, the network entity 102 and the UE 104 may use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some implementations, the network entity 102 and the UE 104 may support different resource structures. For example, the network entity 102 and the UE 104 may support different frame structures. In some implementations, such as in 4G, the network entity 102 and the UE 104 may support a single frame structure. In some other implementations, such as in 5G and other suitable radio access technologies, the network entity 102 and the UE 104 may support various frame structures (e.g., multiple frame structures). The network entity 102 and the UE 104 may support various frame structures based on one or more digital technologies.

[0046] One or more digital technologies may be supported in the wireless communication system 100, and the digital technologies may include subcarrier spacing and cyclic prefixes. A first digital technology (e.g., μ = 0) may be associated with a first subcarrier spacing (e.g., 15kHz) and a normal cyclic prefix. A first digital technology (e.g., μ = 0) associated with a first subcarrier spacing (e.g., 15kHz) may utilize one slot per subframe. A second digital technology (e.g., μ = 1) may be associated with a second subcarrier spacing (e.g., 30kHz) and a normal cyclic prefix. A third digital technology (e.g., μ = 2) may be associated with a third subcarrier spacing (e.g., 60kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth digital technology (e.g., μ = 3) may be associated with a fourth subcarrier spacing (e.g., 120kHz) and a normal cyclic prefix. A fifth digital technology (e.g., μ = 4) may be associated with a fifth subcarrier spacing (e.g., 240kHz) and a normal cyclic prefix.

[0047] The time intervals of resources (e.g., communication resources) can be organized according to frames (also referred to as radio frames). Each frame can have a duration, for example, a duration of 10 milliseconds (ms). In some implementations, each frame can include multiple subframes. For example, each frame can include 10 subframes, and each subframe can have a duration, for example, a duration of 1 ms. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have the same duration.

[0048] Additionally or alternatively, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may include a certain number (e.g., quantity) of time slots. Each time slot may include a certain number (e.g., quantity) of symbols (e.g., orthogonal frequency division multiplexing (OFDM) symbols). In some implementations, the number (e.g., quantity) of time slots for a subframe may depend on the digital technology. For a normal cyclic prefix, a time slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable to a 60kHz subcarrier spacing), a time slot may include 12 symbols. For a normal cyclic prefix and an extended cyclic prefix, the relationship between the number of symbols per time slot, the number of time slots per subframe, and the number of time slots per frame may depend on the digital technology. It should be understood that references to a first digital technology (e.g., μ=0) associated with a first subcarrier spacing (e.g., 15kHz) may be used interchangeably between subframes and time slots.

[0049] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, frequency channels, etc. based on frequency or wavelength. For example, the wireless communication system 100 can support one or more operating frequency bands, such as frequency range names FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4 (52.6 GHz to 114.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), and FR5 (114.25 GHz to 300 GHz). In some implementations, the network entity 102 and the UE 104 can perform wireless communications on the one or more operating frequency bands. In some implementations, FR1 can be used by the network entity 102 and the UE 104 and other devices or apparatuses for cellular communication services (e.g., control information, data). In some implementations, FR2 may be used by the network entity 102 and UE 104 and other devices or apparatuses for short-range, high data rate capabilities.

[0050] FR1 may be associated with one or more digital technologies (e.g., at least three digital technologies). For example, FR1 may be associated with a first digital technology (e.g., μ=0) including a subcarrier spacing of 15 kHz; a second digital technology (e.g., μ=1) including a subcarrier spacing of 30 kHz; and a third digital technology (e.g., μ=2) including a subcarrier spacing of 60 kHz. FR2 may be associated with one or more digital technologies (e.g., at least 2 digital technologies). For example, FR2 may be associated with a third digital technology (e.g., μ=2) including a subcarrier spacing of 60 kHz; and a fourth digital technology (e.g., μ=3) including a subcarrier spacing of 120 kHz.

[0051] According to an implementation of codebook configuration for device positioning, network entity 102(1) may generate codebook configuration 120(1) and send codebook configuration 120(1) to UE 104(1) (e.g., target UE), and may generate codebook configuration 120(2) and send codebook configuration 120(2) to one or more anchor nodes 122. As described below, codebook configurations 120(1), 120(2) may be generated based on various criteria, such as attributes of UE 104(1), attributes of one or more anchor nodes 122, and / or attributes of network entity 102(1). In addition, one or more anchor nodes 122 send PRS to UE 104(1). In at least one implementation, one or more anchor nodes 122 send PRS 124 based at least in part on codebook configuration 120(2), such as based on beam attributes defined by a codebook generated based on codebook configuration 120(2).

[0052] UE 104(1) then performs parameter determination 126 based on PRS 124. For example, UE 104(1) generates a codebook based on codebook configuration 120(1) and processes PRS 124 using the codebook to perform parameter determination 126. Thus, based on parameter determination 126, UE 104(1) generates a location notification 128 that includes various location-related parameters, examples of which are described in detail below. UE 104(1) sends location notification 128 to network entity 102(1), which performs location estimation 130 using the location-related parameters from location notification 128 to estimate the location of UE 104(1).

[0053] In some wireless communication systems, NR positioning based on NR Uu signals and standalone (SA) architecture (e.g., beam-based transmission) is specified, such as in Rel-16. Target use cases include commercial and regulatory (emergency services) scenarios, such as described in Rel-15. Performance requirements include the following:

[0054] Positioning error indoor outdoor Horizontal positioning For 80% of UEs less than 3m For 80% of UEs, the distance is less than 10m Vertical positioning For 80% of UEs less than 3m For 80% of UEs less than 3m

[0055] The current 3GPP Rel-17 positioning has recently defined positioning performance requirements for commercial and IIoT use cases as follows:

[0056]

[0057] Examples of positioning technologies supported in Rel-16 are listed in Table 1:

[0058] Table 1: UE positioning methods supported by Rel-16

[0059]

[0060]

[0061] According to different wireless positioning scenarios, individual positioning techniques as shown in Table 1 can currently be configured and executed based on the requirements of the location management function (LMF) and UE capabilities. The transmission of Uu (uplink and downlink) PRS enables the UE to perform UE positioning related measurements to be able to calculate the absolute position estimate of the UE, and the transmission is configured per transmission reception point (TRP), where the TRP can include a set of one or more beams.

[0062] Figure 2 A system 200 is illustrated in which PRS may be transmitted. For example, system 200 illustrates that according to Rel-16, PRS may be transmitted by different base stations (serving base station and neighboring base station) using narrow beams in FR1 and FR2, which is relatively different compared to LTE, where PRS is transmitted over the entire cell. PRS may be locally associated with a PRS resource identifier (ID) and a resource set ID of a base station (TRP). Similarly, UE positioning measurements such as reference signal time difference (RSTD) and PRS reference signal received power (RSRP) measurements are performed between beams (e.g., between different pairs of downlink (DL) PRS resources or DL ​​PRS resource sets), whereas in the case of LTE, UE positioning measurements are performed between different cells. In addition, the network may also utilize additional uplink (UL) positioning methods to calculate the location of the target UE. RAT-dependent positioning technology involves 3GPP RAT and core network entities to perform UE position estimation, which is different from RAT-independent positioning technology that relies on Global Navigation Satellite System (GNSS), Inertial Measurement Unit (IMU) sensors, Wireless Local Area Network (WLAN) and Bluetooth technology to perform target device (e.g., target UE) positioning.

[0063] Figure 3 A system 300 is illustrated that provides an overview of absolute and relative positioning scenarios. For example, the system 300 is defined in a system architecture that uses three different coordinate systems.

[0064] Absolute positioning, fixed coordinate system

[0065] Relative positioning, variable and mobile coordinate systems

[0066] Relative positioning, variable coordinate system

[0067] The following terms may be used in this disclosure, and the following represent some examples and non-limiting interpretations of these terms:

[0068] Target UE: can be called the UE of interest, its location (absolute or relative)

[0069] Will be acquired by the network or by the UE itself.

[0070] Sidelink positioning: The UE is positioned using a reference signal sent via the Sidelink (SL) (e.g., PC5 interface) to obtain absolute position, relative position and / or ranging information.

[0071] • Ranging: Determine the distance and / or direction between a UE and another entity (eg, an anchor UE).

[0072] Anchor UE: A UE that supports positioning of a target UE, for example, by sending and / or receiving reference signals for positioning, providing positioning related information, etc., such as via a sidelink interface.

[0073] SL positioning node: may refer to a network entity and / or device (e.g., UE) participating in a SL positioning session, and may be implemented as a LMF (location server), gNB, UE, road side unit (RSU), anchor UE, initiator and / or responder UE, etc.

[0074] SL PRS (pre-) configuration: (pre-) configuration parameters of SL PRS, such as time-frequency resources (not excluding other parameters), including its bandwidth and periodicity.

[0075] Therefore, the present disclosure provides solutions to support codebook configuration for device positioning according to various implementations. For example, as part of position estimation, the described solution provides dynamic codebook configuration for position determination to adapt the codebook to different device properties and / or scenarios, such as to improve position determination accuracy and reduce the burden on system resources (e.g., power, processing, data transmission, etc.).

[0076] Figure 4 A scenario 400 is illustrated that supports codebook configuration for device positioning according to aspects of the present disclosure. For example, the scenario 400 presents details for utilizing angular resolution as part of position determination.

[0077] The scenario 400 includes a codebook 402, which may be characterized using several parameters, including:

[0078] 1. Codebook dimension xD, x∈{1, 2, 3, ...}, which can be based on various factors such as node capabilities (e.g., user location accuracy (ULA), user range accuracy (URA)

[0079] and / or CIR measurement dimensions)), where in implementation, the CIR measurement may be represented / shaped as an x-dimensional tensor x∈{1, 2, 3, ...};

[0080] 2. Codebook grid boundary 404, e.g., β in 1D casemin and β max , which can set the minimum and maximum limits of the grid points, i.e., β n ∈[β min , β max ];

[0081] 3. The number N of grid points used to form codewords and / or beams in the codebook 402;

[0082] 4. The sampling method of the area spanned by the codebook grid boundary 404. For example, in the 1D case, the grid points β can be selected n ∈[β min , β max ], so that they are uniformly sampled by the codebook boundary β min and β max The area spanned (e.g., β n =β min +n·(β max -β min ) / (N-1), where n∈{0,...,N-1}), or non-uniform sampling based on implementation details;

[0083] 5. Codeword dimension M, which can be specified based on node capabilities, for example, M represents the total number of antenna elements of the node on the horizontal and vertical axes;

[0084] 6. Codebook resolution β res , which can be defined as the minimum distance between two adjacent grid points. Note that by increasing the number of codewords N and / or reducing the codebook boundary β min With β max The distance between them can obtain a fine resolution codebook.

[0085] Figure 5 A scenario 500 is illustrated that supports codebook configuration for device positioning according to aspects of the present disclosure. For example, scenario 500 illustrates the impact of the number of codewords N on the estimation accuracy of location-related parameters. In addition, it shows that when the distance between the anchor node and the target UE doubles, the positioning error may double.

[0086] Depending on the implementation, the codebook may be used for various purposes. For example, the codebook may be used to estimate location-dependent parameters from received CIR measurements using a codebook-based approach (eg, a simple correlation-based approach and / or MUSIC).

[0087] For example, consider scenario 502 shown in scenario 500, where an anchor node 504 is equipped with a ULA with M=4 antennas and sends a PRS signal to a target UE 506 with a single antenna. Depending on the implementation, it may be assumed that there is a pure line-of-sight (LOS) channel between the anchor node 504 and the target UE 506. The CIR measurement at the target UE 506 (such as in a noise-free situation) may be expressed as:

[0088] y=hs∈C M ,

[0089] where h = α·ψ(φ)∈C M is the channel vector, where ψ(φ) = [1, ..., e j(M-1)φ ] T ∈C M represents the true steering (response) vector at the anchor node 504, φ∈[0,2π] is the true AoD, α is the channel path gain, and s is the transmitted PRS symbol. Depending on the implementation, s=1 and α=1 may be assumed, such as without loss of generality. Given the measurement vector y and a codebook with N codewords as Ψ=[ψ1(β1), ..., ψ N (β M )]∈C M×N , the target UE can use a simple correlation-based method to estimate AoDφ as follows:

[0090]

[0091] where ψ n (β n )∈C M is the nth codeword. Assume β min =0,β max =2π, then the nth grid point can be chosen as n∈{0,...,N-1}.

[0092] Scenario 500 also shows correlation functions with codebook codewords and / or grid points for two different numbers N∈{8,16} of codewords at 508 and 510, respectively. As shown, increasing the number of codewords N from 8 to 16 can improve the estimation accuracy of AoD because it increases the codebook resolution from 2π / 7 to 2π / 15. In addition, it can be seen that when the position of the target UE 506 changes from [x target ,y target ]=[5,5]Move to [x target ,y target] = [10, 10], the positioning error doubles, which doubles the distance between the anchor node and the target UE, but the AoD remains unchanged, which is φ = π / 4 = 45°. Therefore, for example, if the positioning error is to be maintained, such as when the distance is doubled, the AoD estimation error is halved, such as shown at 508 and 510.

[0093] Figure 6 A system 600 for supporting codebook configuration for device positioning according to aspects of the present disclosure is illustrated, and Figure 7 Illustrated is a system 700 that supports codebook configuration for device positioning according to aspects of the present disclosure.For example, the systems 600, 700 illustrate implementations for signaling the number of codewords and / or beams between nodes such as a network entity and a UE.

[0094] The system 600 includes a network configuration entity 602 (e.g., a LMF), a receiving node 604 (e.g., a target UE), and a sending node 606 (e.g., an anchor node). In the system 600, the network configuration entity 602 determines N at 608, such as based on various criteria discussed herein. The network configuration entity 602 sends N, β_min, β_max to the receiving node 604. In addition, the sending node 606 sends a PRS to the receiving node 604. The receiving node 604 at 610 performs measurements on the PRS, generates a codebook based on N, β_min, β_max, and estimates a location-related parameter, such as AoD. The receiving node 604 may then send the estimated location-related parameters to the network configuration entity 602, which may perform a location estimation of the receiving node 604 based at least in part on the location-related parameters at 612.

[0095] The system 700 includes a network configuration entity 702 (eg, a LMF), a receiving node 704 (eg, a target UE), and a sending node 706 (eg, an anchor node). In the system 700, the network configuration entity 702 determines N at 708. T and N R , such as based on various standards discussed herein. The network configuration entity 702 sends N to the receiving node 704. R , β R _min, β R In addition, the network configuration entity 702 sends N to the sending node 706. T , β T _min, β T At 710, the receiving node 704 calculates the value of N based on R , β R _min, β R _max generates a codebook, and at 712, the sending node 706 generates a codebook based on N T , βT _min, β T _max generates codebook.

[0096] In addition to the system 700, the corresponding codebook can be used to send and receive positioning signals (e.g., PRS, SL-PRS, SRS, etc.) using the codebook beam. For example, as shown in the system 700, the anchor node 706 (e.g., gNB, RSU, TRP) can be configured to send N T beams to transmit PRS signals, and the receiving node 704 may be configured to receive N R At 714, the receiving node 704 performs measurements on the PRS and estimates position-related parameters such as AoD based on its codebook. For example, the angle of departure (AOD) and angle of arrival (AOA) can be estimated as two grid points corresponding to the transmit-receive beam pair with the strongest signal strength. In an implementation, N T and N R may be the same as N, such as in scenario 400, and the subscript ·T and ·R Used to distinguish between transmit beams and receive beams.

[0097] In addition to the system 700 , the receiving node 704 may then send the estimated location-related parameters to the network configuration entity 702 , which may perform a location estimation of the receiving node 704 based at least in part on the location-related parameters at 716 .

[0098] In implementation, the systems 600 and 700 may be implemented to dynamically adapt to changes in criteria that may affect codebook configuration, such as changes in device attributes (e.g., attributes of the target UE and / or the anchor device). For example, after configuring the codebook parameters (such as the N value and the β value) as described above in the systems 600 and 700, the network configuration entity 602 and 702 may detect changes in criteria that may affect codebook configuration. Therefore, in response to detecting a change in the codebook criteria, the network configuration entity 602 and 702 may adjust the N, N, and β values ​​in response to ... T 、N R , β_min, β_max, β T _min, β T _max, β R _min, or β R_max to generate an updated value. The updated value can be transmitted to the target UE and / or the anchor node, and is used by the target UE and / or the anchor node to generate an updated codebook for receiving, sending and / or processing a positioning reference signal. Therefore, the system 600, 700 can be implemented to initially configure the codebook features, and update the codebook features based on changes in the codebook standards. Therefore, the codebook configuration can be dynamically adjusted based on changes in one or more standards. Examples of different standards that may affect the codebook configuration are discussed below.

[0099] In implementation, the network device configuration entity (e.g., LMF and / or anchor node) may consider one or more criteria to determine the number N of codewords and / or beams forming the codebook. Examples of different criteria include:

[0100] 1. Position estimation accuracy specifications (e.g., requirements):

[0101] a. For higher (e.g., stricter) positioning accuracy specifications, a larger N may be specified, while for lower positioning accuracy specifications, a smaller N may be specified;

[0102] i. In implementation, a larger N may produce a fine resolution codebook, and thus a fine estimation accuracy, while a smaller N may produce a coarse resolution codebook, and thus a coarse estimation accuracy;

[0103] ii. In implementation, depending on the node capability, positioning accuracy may include horizontal accuracy and / or vertical accuracy. In this scenario, the total number of codewords and / or beams N may be divided between horizontal accuracy and / or vertical accuracy, i.e., N=N h ·N v , where N h represents the number of codewords and / or beams in the horizontal dimension, N v represents the number of codewords and / or beams in the vertical dimension, such as Figure 4 shown.

[0104] 2. Distance between target UE and (multiple) anchor nodes:

[0105] a. For longer distances, you can specify a larger N, and for smaller distances, you can specify a smaller N;

[0106] ⅰ. In Figure 5 In the implementation shown, if a certain positioning accuracy is specified to be maintained, the estimation accuracy of the position-related parameters will increase as the distance between the anchor node and the target UE increases;

[0107] ii. In implementation, if the target UE has a different distance to each anchor node in a set of anchor nodes, a different N may be selected for each anchor node in the set of anchor nodes;

[0108] iii. In implementations, if the distance is not explicitly available (e.g., via ranging), path loss may be used to approximate it and / or other metrics that are partly a function of distance, such as received signal strength indicator (RSSI). 3. Waiting time and / or delay specifications:

[0109] a. A smaller N is for a shorter latency and / or delay specification, while a larger N is for a longer latency and / or delay specification;

[0110] i. In implementation, a node may need N time symbols to transmit and / or receive a PRS signal via N beams, which may increase the delay of position estimation, and vice versa.

[0111] 4. Energy consumption of nodes:

[0112] a. For energy-constrained nodes (e.g., mobile phones), a smaller N may be specified, while for nodes with greater power resources, a larger N may be specified;

[0113] i. In implementation, increasing the number of beams N may increase the transmission and / or reception energy consumption, while decreasing the number of beams N may decrease the transmission and / or reception energy consumption.

[0114] 5. Node mobility status:

[0115] a. For nodes with higher mobility, a smaller N may be specified, while for nodes with lower mobility (eg, stationary and / or fixed location nodes), a larger N may be specified;

[0116] i. In implementation, higher node mobility can reduce the channel coherence time, which can limit the position estimation accuracy. Therefore, reducing the number of codewords and / or beams N can provide a coarse estimation accuracy.

[0117] 6. Codebook Boundary β min and β max :

[0118] a. For codebook boundary β min With β max A narrower distance between , a smaller N can be specified, and for the codebook boundary β min With β max A wider distance between them allows you to specify a larger N;

[0119] ⅰ. In the implementation, in order to maintain a certain codebook resolution, the codebook boundary β can be maintained. min and βmax while increasing the number N of codewords while fixing, or while maintaining the codebook boundaries β min and β max while decreasing the number N of codewords while fixing, e.g., by shrinking the codebook boundaries β min and β max while keeping the number N of codewords fixed.

[0120] 7. PRS time-frequency resource configuration, e.g., the number of time symbols and / or the number of frequency subcarriers (e.g., bandwidth, which can be characterized as the number of resource blocks (RBs)):

[0121] a. For a larger number of time symbols and / or a larger number of frequency subcarriers (RBs), a larger N can be specified, while for a smaller number of time symbols and / or

[0122] a smaller number of frequency subcarriers (RBs), a smaller N can be specified;

[0123] ⅰ. In an implementation, in a beam-based positioning method, a node can be configured to: transmit and / or receive in T time symbols and K subcarriers (e.g., RBs). Thus, a network configuration entity can determine the number of codebook beams as N = TK (e.g., using different beams in each time symbol and / or subcarrier to transmit and / or receive), or determine N < TK (where one or more beams are repeated in signal transmission and / or reception).

[0124] In an implementation, the number N of codewords and / or beams can be determined by a network device configuration entity, such as an LMF entity and / or an anchor node, such as a gNB, RSU, TRP, vehicle UE, etc. In an implementation, the number N of codewords and / or beams can be signaled to network nodes, such as an anchor node and / or a target UE that receive and / or transmit PRS, SL-PRS, or SRS signals, as shown in systems 600, 700.

[0125] In an implementation, assuming preconfigured codebook boundaries (e.g., preconfigured horizontal boundaries and and / or preconfigured vertical boundaries and ), a configuration entity (e.g., LMF) can determine the number of codewords and / or beams for each dimension (e.g., the number N of horizontal codewords and / or beams h and the number N of vertical codewords and / or beams v ). In such a scenario, the configuration entity can signal the number of codewords and / or beams for each dimension, e.g., N h and N v .

[0126] In an implementation, assuming an updated codebook boundary (e.g., an updated horizontal boundary and and / or update the vertical margins and ), the configuration entity (e.g., LMF) may determine the number of codewords and / or beams for each dimension (e.g., the number of horizontal codewords and / or beams N) based on, for example, pre-estimated position-related parameters. h and the number of vertical codewords and / or beams N v ). In this scenario, the configuration entity may configure the number of horizontal codewords and / or beams N. h and / or the number of vertical codewords and / or beams N h Signaling horizontal codebook boundaries ( and ) and / or vertical codebook boundaries ( and ).

[0127] In implementation, aspects such as positioning accuracy, latency requirements, and energy consumption may be specified by a location service (LCS) client (internal and / or external) via positioning QoS. Accuracy may also include horizontal accuracy and / or vertical accuracy.

[0128] In implementation, the relative distance between (multiple) anchor nodes and the target UE may be initially established using methods such as: coarse positioning techniques (such as measurement fingerprinting based on received signal strength (RSS)), DL and / or SL path loss estimation, relative distance derived based on area ID, etc.

[0129] In an implementation, a configuration entity and / or node may configure a transmit and / or measurement codebook based on a DL and / or SL configuration. In a scenario for DL ​​configuration, the LMF may send such a codebook request to the serving and neighboring gNBs and / or TRPs (e.g., NG-RAN nodes), and subsequently receive a response containing a codebook or lack of a codebook, which may be signaled using an NRPPa interface in an implementation. In a scenario using SL configuration, a configuration entity based on a scenario (e.g., in coverage, partial coverage, or out of coverage) may use PC5 signaling (e.g., SL positioning (e.g., ranging sidelink) sidelink protocol, PC5RRC, PC5-S, SL MAC control unit (CE) signaling, etc.) to signal the transmit and / or measurement codebook.

[0130] In implementation, the mobility state (e.g., low, medium, high) may affect the frequency of updating the codebook from coarse resolution to fine resolution (or vice versa) based on the mobility state feedback received from the target UE. For example, the frequency may be represented by a configured periodicity that signals the configuration.

[0131] Figure 8 An example of a block diagram 800 of a device 802 (e.g., an apparatus) that supports codebook configuration for device positioning according to aspects of the present disclosure is illustrated. The device 802 may be an example of a UE 104 as described herein. The device 802 may support wireless communications with one or more network entities 102, UEs 104, or any combination thereof. The device 802 may include components for bidirectional communication, including components for sending and receiving communications (such as a processor 804, a memory 806, a transceiver 808, and an I / O controller 810). These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., a bus).

[0132] The processor 804, the memory 806, the transceiver 808, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of the present disclosure described herein. For example, the processor 804, the memory 806, the transceiver 808, or various combinations thereof, or components thereof may support methods for performing one or more of the operations described herein.

[0133] In some implementations, the processor 804, the memory 806, the transceiver 808, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit system). The hardware may include a processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination of components configured to or otherwise support the functions described in the present disclosure. In some implementations, the processor 804 and the memory 806 coupled to the processor 804 may be configured to perform one or more functions described herein (e.g., by executing instructions stored in the memory 806 by the processor 804). For example, in the context of the UE 104, the transceiver 808 and the processor 804 coupled to the transceiver 808 are configured to cause the UE 104 to perform various described operations and / or combinations thereof.

[0134] For example, according to examples disclosed herein, the processor 804 and / or the transceiver 808 may support wireless communication at the device 802. For example, the processor 804 and / or the transceiver 808 may be configured to and / or otherwise support components for: receiving a notification including a codebook configuration, the codebook configuration including a codebook boundary and a number of positioning reference signal features used to form a codebook for a first device; generating a codebook based at least in part on the codebook configuration; receiving a positioning reference signal; generating a positioning measurement based at least in part on the positioning reference signal and the codebook; and sending the positioning measurement to a second device.

[0135] In addition, in some implementations, the positioning reference signal characteristics include one or more of the following items: the number of positioning reference signal codewords in each dimension, or the number of positioning reference signal beams in each dimension; in order to generate positioning measurements, the processor is configured to: process the positioning reference signal using codewords forming a codebook; the processor is also configured to: process one or more paths of the CIR to generate positioning measurements; the processor is configured to: use one or more codebook-based methods to generate positioning measurements; the one or more codebook-based methods include MUSIC; the processor is configured to: generate positioning measurements based at least in part on one or more of the following items: uplink positioning measurements, downlink positioning measurements, or sidelink positioning measurements; the first device includes a UE, and the second device includes one or more of the following items: a device for sending a notification, or a device for sending a positioning reference signal.

[0136] In another example, according to examples disclosed herein, the processor 804 and / or the transceiver 808 may support wireless communication at the device 802. For example, the processor 804 and / or the transceiver 808 may be configured to or otherwise support components for: receiving a notification including a codebook configuration including a codebook boundary and a number of positioning reference signal beams used to form a codebook for a first device; generating a codebook based at least in part on the codebook configuration; receiving a beam including a positioning reference signal; generating a positioning measurement based at least in part on one or more positioning reference signals and the codebook from one or more beams having the strongest signal strength; and sending the positioning measurement to the second device.

[0137] Furthermore, in some implementations, the beam comprising the positioning reference signal includes: forming one or more beams of a codebook.

[0138] According to examples disclosed herein, a processor 804 of a device 802 (such as UE 104) may support wireless communications. The processor 804 includes at least one controller coupled to at least one memory and configured to or operable to cause the processor to perform various operations described with reference to the device 802 (such as UE 104). For example, the processor is configured to and / or operable to: receive a notification including a codebook configuration, the codebook configuration including a codebook boundary and a number of positioning reference signal features used to form a codebook for the UE; generate a codebook based at least in part on the codebook configuration; receive a positioning reference signal; generate a positioning measurement based at least in part on the positioning reference signal and the codebook; and send the positioning measurement to the device.

[0139] The processor 804 may include an intelligent hardware device (e.g., a general purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some implementations, the processor 804 may be configured to operate a memory array using a memory controller. In some other implementations, the memory controller may be integrated into the processor 804. The processor 804 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 806) so that the device 802 performs various functions of the present disclosure.

[0140] The memory 806 may include random access memory (RAM) and read-only memory (ROM). The memory 806 may store computer-readable, computer-executable code, which includes instructions that, when executed by the processor 804, cause the device 802 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as a system memory or another type of memory. In some implementations, the code may not be directly executed by the processor 804, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In addition, in some implementations, the memory 806 may include a basic I / O system (BIOS), which may control basic hardware or software operations, such as interacting with peripheral components or devices.

[0141] I / O controller 810 can manage input and output signals for device 802. I / O controller 810 can also manage peripheral devices that are not integrated into device 802. In some implementations, I / O controller 810 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 810 can utilize an operating system, such as

[0142] Or another known operating system. In some implementations, I / O controller 810 can be implemented as part of a processor such as processor 804. In some implementations, a user can interact with device 802 via I / O controller 810 or via hardware components controlled by I / O controller 810.

[0143] In some implementations, the device 802 may include a single antenna 812. However, in some other implementations, the device 802 may have more than one antenna 812 (e.g., multiple antennas), including multiple antenna panels or antenna arrays, which may be able to concurrently send or receive multiple wireless transmissions. The transceiver 808 may communicate bidirectionally via one or more antennas 812, wired or wireless links, as described herein. For example, the transceiver 808 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 808 may also include a modem for modulating packets, providing the modulated packets to one or more antennas 812 for transmission, and demodulating packets received from one or more antennas 812.

[0144] Fig. 9 An example of a block diagram 900 of a device 902 (e.g., an apparatus) supporting codebook configuration for device positioning according to aspects of the present disclosure is illustrated. The device 902 may be an example of a network entity 102 as described herein. The device 902 may support wireless communications with one or more network entities 102, UEs 104, or any combination thereof. The device 902 may include components for bidirectional communication, including components for sending and receiving communications (such as a processor 904, a memory 906, a transceiver 908, and an I / O controller 910). These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., a bus).

[0145] The processor 904, memory 906, transceiver 908, or various combinations thereof, or various components thereof may be examples of means for performing various aspects of the present disclosure described herein. For example, the processor 904, memory 906, transceiver 908, or various combinations thereof, or components thereof may support methods for performing one or more of the operations described herein.

[0146] In some implementations, the processor 904, the memory 906, the transceiver 908, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit system). The hardware may include a processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination of components configured to or otherwise support the functions described in the present disclosure. In some implementations, the processor 904 and the memory 906 coupled to the processor 904 may be configured to perform one or more functions described herein (e.g., by executing instructions stored in the memory 906 by the processor 904). For example, in the context of the network entity 102, the transceiver 908 and the processor 904 coupled to the transceiver 908 are configured to cause the network entity 102 to perform various described operations and / or combinations thereof.

[0147] For example, according to examples disclosed herein, the processor 904 and / or the transceiver 908 may support wireless communication at the device 902. For example, the processor 904 and / or the transceiver 908 may be configured to or otherwise support components for: generating a notification including a codebook configuration, the codebook configuration including a codebook boundary and a number of positioning reference signal features used to form a codebook for a second device, the number of positioning reference signal features being based at least in part on one or more criteria; sending the notification to the second device; receiving a positioning measurement generated by the second device based at least in part on the codebook configuration; and generating a position estimate for the second device based at least in part on the positioning measurement.

[0148] In addition, in some implementations, the positioning reference signal characteristics include one or more of the following items: the number of positioning reference signal codewords in each dimension, or the number of positioning reference signal beams in each dimension; one or more standards include one or more of the following items: one or more capabilities of the second device, one or more positioning accuracy characteristics of the first device, a power usage parameter of the second device, a maximum delay parameter of the first device, a mobility state of the second device, a codebook boundary of the second device, or a positioning reference signal time-frequency resource configuration of the second device; the processor is also configured to send a positioning reference signal to the second device; the processor is configured to generate a position estimate of the second device as one or more of the following items: an absolute position of the second device, a relative position of the second device, or a distance estimate including one or more of the following items: a distance or relative direction relative to the first device or one or more of the devices sending the positioning reference signal to the second device; the positioning measurement is based at least in part on one or more of the following items: an uplink positioning measurement, a downlink positioning measurement, or a sidelink positioning measurement; the first device includes a network configuration entity, and the second device includes a UE; the processor is also configured to: receive an indication of a change in one or more standards, and dynamically adjust the codebook configuration based on the change in one or more standards.

[0149] In another example, according to the examples disclosed herein, the processor 904 and / or the transceiver 908 can support wireless communication at the device 902. For example, the processor 904 and / or the transceiver 908 can be configured to or otherwise support components for: generating a first notification including a codebook configuration for a second device, the codebook configuration including a codebook boundary and a number of positioning reference signal beams used to form a codebook for the second device, the number of positioning reference signal beams being based at least in part on a first set of criteria; generating a second notification including a codebook configuration for one or more third devices, the codebook configuration including a codebook boundary and a number of positioning reference signal beams used to form a codebook for the one or more third devices, the number of positioning reference signal beams being based at least in part on a second set of criteria; sending the first notification to the second device and sending the second notification to the one or more third devices; receiving a positioning measurement generated by the second device at least in part based on the codebook configuration of the second device; and generating a position estimate for the second device based at least in part on the positioning measurement.

[0150] In addition, in some implementations, one or more criteria in the first set of criteria or the second set of criteria include one or more of the following: at least one of one or more capabilities of the second device or one or more capabilities of one or more third devices, one or more positioning accuracy characteristics of the first device, one or more power usage parameters of the second device or one or more power usage parameters of one or more third devices, a maximum delay parameter of the first device, one or more mobility states of the second device or one or more mobility states of one or more third devices, one or more codebook boundaries of the second device or one or more codebook boundaries of one or more third devices, or a positioning reference signal time-frequency resource configuration of the second device or one or more third devices. One or more of the positioning reference signal time-frequency resource configurations of the device; the processor is configured to generate a position estimate of the second device as one or more of the following items: the absolute position of the second device, the relative position of the second device, or a distance estimate including one or more of the following items: a distance or relative direction relative to the first device or one or more of the devices sending the positioning reference signal to the second device; the positioning measurement is at least partially based on one or more of the following items: an uplink positioning measurement, a downlink positioning measurement, or a sidelink positioning measurement; the first device includes a network configuration entity, the second device includes a UE, and the one or more third devices include one or more devices that send a positioning reference signal to the second device.

[0151] In another example, according to examples disclosed herein, the processor 904 and / or the transceiver 908 may support wireless communication at the device 902. For example, the processor 904 and / or the transceiver 908 may be configured to or otherwise support means for: receiving a notification including a codebook configuration including a codebook boundary and a number of positioning reference signal beams for forming a codebook for a first device; generating a codebook based at least in part on the codebook configuration; and sending a beam including a positioning reference signal to a second device based at least in part on the codebook.

[0152] Furthermore, in some implementations, the beam comprising the positioning reference signal includes: forming one or more beams of a codebook.

[0153] The processor 904 may include an intelligent hardware device (e.g., a general purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some implementations, the processor 904 may be configured to operate a memory array using a memory controller. In some other implementations, the memory controller may be integrated into the processor 904. The processor 904 may be configured to execute computer-readable instructions stored in a memory (e.g., a memory 906) so that the device 902 performs various functions of the present disclosure.

[0154] The memory 906 may include random access memory (RAM) and read-only memory (ROM). The memory 906 may store computer-readable, computer-executable code, which includes instructions that, when executed by the processor 904, cause the device 902 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as a system memory or another type of memory. In some implementations, the code may not be directly executed by the processor 904, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In addition, in some implementations, the memory 906 may include a basic I / O system (BIOS), which may control basic hardware or software operations, such as interacting with peripheral components or devices.

[0155] I / O controller 910 can manage input and output signals for device 902. I / O controller 910 can also manage peripheral devices that are not integrated into device 2402. In some implementations, I / O controller 910 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 910 can utilize an operating system, such as

[0156] Or another known operating system. In some implementations, I / O controller 910 can be implemented as part of a processor such as processor M06. In some implementations, a user can interact with device 902 via I / O controller 910 or via hardware components controlled by I / O controller 910.

[0157] In some implementations, the device 902 may include a single antenna 912. However, in some other implementations, the device 902 may have more than one antenna 912 (e.g., multiple antennas), including multiple antenna panels or antenna arrays, which may be able to send or receive multiple wireless transmissions concurrently. The transceiver 908 may communicate bidirectionally via one or more antennas 912, wired or wireless links, as described herein. For example, the transceiver 908 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 908 may also include a modem for modulating packets, providing the modulated packets to one or more antennas 912 for transmission, and demodulating packets received from one or more antennas 912.

[0158] Fig.10 1 is a flowchart of a method 1000 for supporting codebook configuration for device positioning according to aspects of the present disclosure. The operations of the method 1000 may be implemented by a device or component thereof as described herein. For example, the operations of the method 1000 may be implemented by reference to Figures 1 to 9The network entity 102 described herein may be used to perform the functions described herein. In some implementations, the device may execute a set of instructions to control functional elements of the device to perform the described functions. Additionally or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0159] At 1002, the method may include: generating, at a first device, a notification including a codebook configuration, the codebook configuration including a codebook boundary and a number of positioning reference signal features used to form a codebook for a second device, the number of positioning reference signal features being based at least in part on one or more criteria. The operations of 1002 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1002 may be performed by reference to Figure 1 The device is used to perform the above.

[0160] At 1004, the method may include sending a notification to the second device. The operations of 1004 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1004 may be described with reference to Figure 1 The device is used to perform the above.

[0161] At 1006, the method may include receiving a positioning measurement generated by a second device based at least in part on a codebook configuration. The operations of 1006 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1006 may be described with reference to Figure 1 The device is used to perform the above.

[0162] At 1008, the method may include generating a position estimate of the second device based at least in part on the positioning measurements. The operations of 1008 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1008 may be described with reference to Figure 1 The device is used to perform the above.

[0163] Fig.11 1 is a flowchart of a method 1100 for supporting codebook configuration for device positioning according to aspects of the present disclosure. The operations of the method 1100 may be implemented by a device or component thereof as described herein. For example, the operations of the method 1100 may be implemented by reference to Figures 1 to 9 The UE 104 described herein may be used to perform the functions described herein. In some implementations, the device may execute a set of instructions to control functional elements of the device to perform the described functions. Additionally or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0164] At 1102, the method may include: at a first device, receiving a notification including a codebook configuration, the codebook configuration including a codebook boundary and a number of positioning reference signal features used to form a codebook for the first device. The operations of 1102 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1102 may be performed by reference to Figure 1 The device is used to perform the above.

[0165] At 1104, the method may include generating a codebook based at least in part on the codebook configuration. The operations of 1104 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1104 may be described with reference to Figure 1 The device is used to perform the above.

[0166] At 1106, the method may include receiving a positioning reference signal. The operations of 1106 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1106 may be performed by reference to Figure 1 The device is used to perform the above.

[0167] At 1108, the method may include generating a positioning measurement based at least in part on the positioning reference signal and the codebook. The operations of 1108 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1108 may be performed by reference to Figure 1 The device is used to perform the above.

[0168] At 1110, the method may include sending a positioning measurement to a second device. The operations of 1110 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1110 may be described with reference to Figure 1 The device is used to perform the above.

[0169] Fig.12 1 is a flowchart of a method 1200 for supporting codebook configuration for device positioning according to aspects of the present disclosure. The operations of the method 1200 may be implemented by a device or component thereof as described herein. For example, the operations of the method 1200 may be implemented by reference to Figures 1 to 9 The network entity 102 described herein may be used to perform the functions described herein. In some implementations, the device may execute a set of instructions to control functional elements of the device to perform the described functions. Additionally or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0170] At 1202, the method may include: generating, at a first device, a first notification including a codebook configuration of a second device, the codebook configuration including a codebook boundary and a number of positioning reference signal beams used to form a codebook of the second device, the number of positioning reference signal beams being based at least in part on a first set of criteria. The operations of 1202 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1202 may be performed by reference to Figure 1 The device is used to perform the above.

[0171] At 1204, the method may include: generating, at the first device, a second notification including a codebook configuration for one or more third devices, the codebook configuration including a codebook boundary and a number of positioning reference signal beams used to form a codebook for the one or more third devices, the number of positioning reference signal beams being based at least in part on a second set of criteria. The operations of 1204 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1204 may be performed by reference to Figure 1 The device is used to perform the above.

[0172] At 1206, the method may include sending a first notification to a second device, and sending a second notification to one or more third devices. The operations of 1206 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1206 may be described with reference to Figure 1 The device is used to perform the above.

[0173] At 1208, the method may include receiving a positioning measurement generated by the second device based at least in part on a codebook configuration of the second device. The operations of 1208 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1208 may be described with reference to Figure 1 The device is used to perform the above.

[0174] At 1210, the method may include generating a position estimate of the second device based at least in part on the positioning measurements. The operations of 1210 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1210 may be described with reference to Figure 1 The device is used to perform the above.

[0175] Fig.13 1 is a flowchart of a method 1300 for supporting codebook configuration for device positioning according to aspects of the present disclosure. The operations of the method 1300 may be implemented by a device or component thereof as described herein. For example, the operations of the method 1300 may be implemented by reference to Figures 1 to 9The UE 104 described herein may be used to perform the functions described herein. In some implementations, the device may execute a set of instructions to control functional elements of the device to perform the described functions. Additionally or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0176] At 1302, the method may include: at a first device, receiving a notification including a codebook configuration, the codebook configuration including a codebook boundary and a number of positioning reference signal beams used to form a codebook for the first device. The operations of 1302 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1302 may be performed by reference to Figure 1 The device is used to perform the above.

[0177] At 1304, the method may include generating a codebook based at least in part on the codebook configuration. The operations of 1304 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1304 may be described with reference to Figure 1 The device is used to perform the above.

[0178] At 1306, the method may include receiving a beam including a positioning reference signal. The operations of 1306 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1306 may be performed by reference to Figure 1 The device is used to perform the above.

[0179] At 1308, the method may include generating positioning measurements based at least in part on one or more positioning reference signals and a codebook from one or more beams having the strongest signal strength. The operations of 1308 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1308 may be performed by reference to Figure 1 The device is used to perform the above.

[0180] At 1310, the method may include sending a positioning measurement to a second device. The operations of 1310 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1310 may be described with reference to Figure 1 The device is used to perform the above.

[0181] Fig.14 1400 is a flowchart of a method 1400 for supporting codebook configuration for device positioning according to aspects of the present disclosure. The operations of the method 1400 may be implemented by a device or component thereof as described herein. For example, the operations of the method 1400 may be implemented by reference to Figures 1 to 9 The network entity 102 and / or UE 104 may be used to perform the described functions. In some implementations, the device may execute a set of instructions to control the functional elements of the device to perform the described functions. Additionally or alternatively, the device may use dedicated hardware to perform aspects of the described functions.

[0182] At 1402, the method may include: at a first device, receiving a notification including a codebook configuration, the codebook configuration including a codebook boundary and a number of positioning reference signal beams used to form a codebook for the first device. The operations of 1402 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1402 may be performed by reference to Figure 1 The device is used to perform the above.

[0183] At 1404, the method may include generating a codebook based at least in part on the codebook configuration. The operations of 1404 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1404 may be described with reference to Figure 1 The device is used to perform the above.

[0184] At 1406, the method may include: sending a beam including a positioning reference signal to a second device based at least in part on the codebook. The operations of 1406 may be performed according to examples as described herein. In some implementations, aspects of the operations of 1406 may be performed by reference to Figure 1 The device is used to perform the above.

[0185] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified, and other implementations are possible. Furthermore, aspects from two or more methods may be combined.

[0186] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed using a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0187] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or sent via a computer-readable medium as one or more instructions or codes. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or any combination of these. Features that implement the functions may also be physically located in various locations, including being distributed so that parts of the functions are implemented in different physical locations.

[0188] Computer readable media include both non-transient computer storage media and communication media, and communication media include any medium that facilitates the transmission of computer programs from one place to another. Non-transient storage media can be any available medium that can be accessed by a general or special-purpose computer. As an example and not limitation, non-transient computer readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage, disk storage or other magnetic storage devices, or can be used to carry or store desired program code components in the form of instructions or data structures and can be accessed by a general or special-purpose computer, or any other non-transient medium of a general or special-purpose processor.

[0189] Any connection may be appropriately referred to as a computer-readable medium. For example, if the software is sent from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technology (such as infrared, radio, and microwave), the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology (such as infrared, radio, and microwave) is included in the definition of computer-readable medium. Disks and optical disks as used herein include CDs, laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks, wherein disks typically reproduce data magnetically, and optical disks reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0190] As used herein, including in the claims, "or" used in a list of items (e.g., a list of items beginning with a phrase such as "at least one of" or "one or more of" or "one or both of") represents an inclusive list, so that, for example, at least one of the list A, B, or C represents A or B or C or AB or AC or BC or ABC (e.g., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on." In addition, as used herein (including in the claims), a "set" may include one or more elements.

[0191] When referring to a network entity, the terms "send," "receive," or "transmit" may refer to any part of a network entity of a RAN (e.g., base station, CU, DU, RU) that communicates with another device (e.g., directly or via one or more other network entities).

[0192] The descriptions described herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "better than other examples." The detailed description includes specific details to facilitate understanding of the described techniques. However, these techniques may be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid confusing the concepts of the described examples.

[0193] The description herein is provided to enable one of ordinary skill in the art to make or use the present disclosure. Various modifications to the present disclosure will be clear to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but should conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A network entity for wireless communication, comprising: at least one memory; as well as at least one processor coupled to the at least one memory and configured to cause the network entity to: generating a notification including a codebook configuration, the codebook configuration including a codebook boundary and a number of positioning reference signal features used to form a codebook for a user equipment (UE), the number of positioning reference signal features based at least in part on one or more criteria; sending the notification to the UE; receiving a positioning measurement generated by the UE based at least in part on the codebook configuration; as well as A position estimate for the UE is generated based at least in part on the positioning measurements.

2. The network entity according to claim 1, wherein the number of positioning reference signal characteristics comprises one or more of the following items: the number of positioning reference signal codewords in each dimension, or the number of positioning reference signal beams in each dimension.

3. The network entity of claim 1 , wherein the one or more criteria include one or more of the following: one or more capabilities of the UE; one or more location accuracy characteristics of the network entity; A power usage parameter of the UE; a maximum delay parameter of the network entity; The mobility state of the UE; The codebook boundary of the UE; or The positioning reference signal time-frequency resource configuration of the UE.

4. The network entity of claim 1, wherein the at least one processor is configured to cause the network entity to send a positioning reference signal to the UE.

5. The network entity of claim 1 , wherein the at least one processor is configured to cause the network entity to generate the position estimate of the UE as one or more of: The absolute position of the UE; the relative position of the UE; or The distance estimation comprises one or more of the following items: a distance or a relative direction relative to one or more of the network entities or the devices sending positioning reference signals to the UE.

6. The network entity of claim 1, wherein the positioning measurement is based at least in part on one or more of: an uplink positioning measurement, a downlink positioning measurement, or a sidelink positioning measurement.

7. The network entity of claim 1 , wherein the at least one processor is configured to cause the network entity to: receiving an indication of a change to the one or more criteria; and The codebook configuration is dynamically adjusted based on the change in the one or more criteria.

8. A user equipment (UE) for wireless communication, comprising: at least one memory; as well as at least one processor coupled to the at least one memory and configured to cause the UE to: receiving a notification including a codebook configuration, the codebook configuration including a codebook boundary and a number of positioning reference signal features used to form a codebook for the UE; generating a codebook based at least in part on the codebook configuration; receiving a positioning reference signal; generating positioning measurements based at least in part on the positioning reference signal and the codebook; as well as The positioning measurements are sent to a device.

9. The UE according to claim 8, wherein the number of positioning reference signal characteristics comprises one or more of the following items: the number of positioning reference signal codewords in each dimension, or the number of positioning reference signal beams in each dimension.

10. The UE of claim 8, wherein to generate the positioning measurement, the at least one processor is configured to cause the UE to process the positioning reference signal using codewords forming the codebook.

11. The UE of claim 10, wherein the at least one processor is configured to cause the UE to process one or more paths of a channel impulse response (CIR) to generate the positioning measurement.

12. The UE of claim 11, wherein the at least one processor is configured to cause the UE to generate the positioning measurements using one or more codebook-based methods.

13. The UE of claim 12, wherein the one or more codebook-based methods include multiple signal classification (MUSIC).

14. The UE of claim 8, wherein the at least one processor is configured to cause the UE to generate the positioning measurement based at least in part on one or more of: an uplink positioning measurement, a downlink positioning measurement, or a sidelink positioning measurement.

15. The UE according to claim 8, wherein the device comprises one or more of the following items: a device for sending the notification, or a device for sending the positioning reference signal.

16. A processor for wireless communication, comprising: at least one controller coupled to at least one memory and configured to cause the processor to: receiving a notification including a codebook configuration, the codebook configuration including a codebook boundary and a number of positioning reference signal features used to form a codebook for a user equipment (UE); generating a codebook based at least in part on the codebook configuration; receiving a positioning reference signal; generating positioning measurements based at least in part on the positioning reference signal and the codebook; as well as The positioning measurements are sent to a device.

17. A network entity for wireless communication, comprising: at least one memory; as well as at least one processor coupled to the at least one memory and configured to cause the network entity to: generating a first notification including a codebook configuration of a user equipment (UE), the codebook configuration including a codebook boundary and a number of positioning reference signal beams used to form a codebook for the UE, the number of positioning reference signal beams being based at least in part on a first set of criteria; generating a second notification including a codebook configuration for one or more third devices, the codebook configuration including a codebook boundary and a number of positioning reference signal beams used to form a codebook for the one or more third devices, the number of positioning reference signal beams based at least in part on a second set of criteria; sending the first notification to the UE, and sending the second notification to the one or more third devices; receiving a positioning measurement generated by the UE based at least in part on the codebook configuration of the UE; as well as A position estimate for the UE is generated based at least in part on the positioning measurements.

18. The network entity of claim 17, wherein one or more criteria in the first set of criteria or the second set of criteria include one or more of the following: at least one of the one or more capabilities of the UE or the one or more capabilities of the one or more third devices; one or more location accuracy characteristics of the network entity; one or more of a power usage parameter of the UE or a power usage parameter of the one or more third devices; a maximum delay parameter of the network entity; one or more of the mobility state of the UE or the mobility states of the one or more third devices; one or more of the codebook boundary of the UE, or the codebook boundary of the one or more third devices; or One or more of the positioning reference signal time-frequency resource configuration of the UE or the positioning reference signal time-frequency resource configuration of the one or more third devices.

19. The network entity of claim 17, wherein the at least one processor is configured to cause the network entity to generate the position estimate of the UE as one or more of: The absolute position of the UE; the relative position of the UE; or The distance estimation comprises one or more of the following items: a distance or a relative direction relative to one or more of the network entities or the devices sending positioning reference signals to the UE.

20. The network entity of claim 17, wherein the positioning measurement is based at least in part on one or more of: an uplink positioning measurement, a downlink positioning measurement, or a sidelink positioning measurement.

Images