Carrier phase location reporting

Abstract

Aspects of the disclosure relate to carrier phase positioning reporting. A network entity provides a carrier phase positioning report configuration to a user equipment. The user equipment generates one or more carrier phase measurement reports based on the received carrier phase positioning report configuration. The user equipment sends the generated carrier phase measurement report to a network entity, which may be the same network entity from which the carrier phase positioning report configuration is received, or may be a different network entity.

Description

[0001] Cross - Reference to Related Applications

[0002] This application claims priority to U.S. Patent Application Serial No. 63 / 480,189, entitled "Carrier Phase Positioning Reporting," filed on January 17, 2023, the entire content of which is incorporated herein by reference. Technical Field

[0003] This disclosure relates to wireless communication and, more particularly, to carrier phase positioning reporting. 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 of 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 the wireless communication system (e.g., time resources (such as symbols, time slots, subframes, frames, etc.) or frequency resources (such as subcarriers, carriers)). Additionally, 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 other than 5G (e.g., sixth-generation (6G)).

[0005] Wireless communication systems enable UE-assisted and UE-based positioning methods in the 3rd Generation Partnership Project (3GPP) positioning framework. However, direct determination of UE-to-UE range / distance and orientation is not currently supported, and such support could facilitate relative positioning applications across other services, such as for vehicle-to-everything (V2X), public safety, industrial Internet of Things (IIoT), commercial, and other applications. Summary of the Invention

[0006] The present disclosure relates to a method, apparatus, and system for supporting carrier phase positioning reports. A network entity provides a carrier phase positioning report configuration to a UE. The UE generates one or more carrier phase measurement reports based on the received carrier phase positioning report configuration. The UE sends the generated carrier phase measurement reports to a network entity, which may be the same network entity from which the carrier phase positioning report configuration was received, or a different network entity or configuration entity, such as another UE. By sending carrier phase measurement reports based on the carrier phase positioning report configuration, carrier phase measurements can be made between devices and nodes within the network through a reporting configuration that allows for accurate and timely reporting of carrier phase measurements.

[0007] Some implementations of the methods and apparatuses described herein may further include: receiving, from a configuration entity, a first signaling indicating a carrier phase positioning report configuration, where the carrier phase positioning report configuration includes at least one of a set of receiver error types or a carrier phase granularity; generating, based on the received report configuration, a plurality of carrier phase measurement reports including a plurality of carrier phase positioning measurements; sending, to the configuration entity, a plurality of second signaling indicating the plurality of carrier phase measurement reports.

[0008] In some implementations of the methods and apparatuses described herein, the carrier phase reporting configuration further includes: a request to provide additional radio access technology (RAT)-related positioning measurements, the additional RAT-related positioning measurements including at least one of the following: downlink reference signal time difference (DL-RSTD), user equipment receive transmit (UE Rx-Tx) time difference, downlink positioning reference signal reference signal received power (DL PRS RSRP), downlink positioning reference signal reference signal received path power (DL PRS RSRPP), sidelink reference signal time difference (SL-RSTD), sidelink relative time of arrival (SL-RTOA), sidelink positioning reference signal reference signal received power (SL PRS RSRP), sidelink positioning reference signal reference signal received path power (SL PRS RSRPP), or sidelink angle of arrival (SL-AoA). Additionally or alternatively, the carrier phase positioning reporting configuration includes: a set of receiver error types, the set of receiver error types including at least one of the following: initial phase offset, initial phase offset group, user equipment (UE) antenna reference point position error, oscillator drift or clock offset, carrier frequency offset, and antenna phase center offset. Additionally or alternatively, each error type in the set of error types is associated with an identifier. Additionally or alternatively, the carrier phase positioning measurements are reported in a carrier phase measurement report in the form of multiple single-carrier phase measurements per transmit receive point (TRP), or in the form of multiple reference signal carrier phase difference measurements per pair of TRPs. Additionally or alternatively, the carrier phase positioning measurements are reported in a carrier phase measurement report based on a defined granularity or step value expressed in radians or degrees. Additionally or alternatively, the carrier phase positioning measurements are reported in a carrier phase measurement report based on a defined quality metric. Additionally or alternatively, incremental or differential carrier phase measurements relative to previously performed carrier phase positioning measurements and current carrier phase measurements are reported in a carrier phase measurement report. Additionally or alternatively, the method and apparatus further include: sending a device error cause related to carrier phase positioning to a configuration entity. Additionally or alternatively, the method and apparatus further include: receiving a configuration entity error cause related to carrier phase positioning. Additionally or alternatively, the method and apparatus further include causing the apparatus to: support sensing of devices capable of supporting carrier phase measurements via capability request and response messages. Additionally or alternatively, the apparatus includes a UE. Additionally or alternatively, the method and apparatus further include: in the case of UE-based positioning, sending a request for positioning reference unit (PRU) carrier phase measurements and / or associated information, and receiving a response to the request for PRU carrier phase measurements and / or associated information.Additionally or alternatively, the associated information includes at least one of the following: PRU integer ambiguity information and quality metric positioning reference signal (PRS) resource identifier (ID), PRS resource set ID, TRPID, PRU identification information, PRUID, LOS / NLOS information associated with each carrier phase positioning measurement in the carrier phase positioning measurements, additional path information associated with each carrier phase positioning measurement in the carrier phase positioning measurements, PRU receiver error type information including any oscillator drift, clock drift, initial PRU phase offset or group of phase offsets, PRU antenna reference point (ARP) position error, PRU phase center offset, PRU measurement timestamp information, or carrier phase or timing measurement quality metric.

[0009] Some implementations of the methods and apparatuses described herein may also include: receiving, from a UE, first signaling indicating a carrier phase measurement report according to a carrier phase positioning report configuration, wherein the carrier phase positioning report configuration includes at least one of a set of receiver error types or a carrier phase granularity, and wherein the carrier phase measurement report includes at least one carrier phase positioning measurement; obtaining location information of the UE based on the carrier phase measurement report.

[0010] In some implementations of the methods and apparatuses described herein, the apparatus includes a network entity, and the method and apparatus further include: sending a carrier phase report configuration to the UE. Additionally or alternatively, the apparatus includes a network entity, and the method and apparatus further include: sending a carrier phase measurement request for reporting uplink carrier phase measurements to the UE, the carrier phase measurement request including a carrier phase report configuration. Additionally or alternatively, the carrier phase report configuration further includes: a request for providing additional RAT-related positioning measurements, the request for the additional RAT-related positioning measurements including at least one of the following: DL-RSTD, UE Rx-Tx time difference, DL PRS RSRP, DL PRS RSRPP, SL-RSTD, SL-RTOA, SL PRS RSRP, SL PRS RSRPP, or SL-AoA. Additionally or alternatively, the carrier phase report configuration further includes a request for reporting location information based on the performed carrier phase measurements. Additionally or alternatively, the carrier phase positioning report configuration includes: a set of receiver error types, the set of receiver error types including at least one of the following: initial phase offset, initial phase offset group, UE antenna reference point position error, oscillator drift or clock offset, carrier frequency offset, and antenna phase center offset. Additionally or alternatively, each of the error types is associated with an identifier. Additionally or alternatively, at least one carrier phase positioning measurement is reported in the carrier phase measurement report in the form of multiple single carrier phase measurements per TRP or in the form of multiple reference signal carrier phase difference measurements per pair of TRPs. Additionally or alternatively, at least one carrier phase positioning measurement is reported in the carrier phase measurement report based on a defined granularity or step value expressed in radians or degrees. Additionally or alternatively, at least one carrier phase positioning measurement is reported in the carrier phase measurement report based on a defined quality metric. Additionally or alternatively, an incremental or differential carrier phase measurement with respect to a previously performed carrier phase positioning measurement and a current carrier phase measurement is reported in the carrier phase measurement report. Additionally or alternatively, the method and apparatus further include: receiving from the UE a UE error cause related to carrier phase positioning. Additionally or alternatively, the method and apparatus further include causing the apparatus to: send to the UE a configuration entity error cause related to carrier phase positioning. Additionally or alternatively, the method and apparatus further include: supporting awareness of devices capable of supporting carrier phase measurements via capability request and response messages. Additionally or alternatively, the method and apparatus further include causing the apparatus to: in the case of UE-based positioning, receive a request for PRU carrier phase measurements and / or associated information, and send a response to the UE with the PRU carrier phase measurements and / or associated information.Additionally or alternatively, the associated information includes at least one of the following: PRU integer ambiguity information and quality metric PRS resource ID, PRS resource set ID, TRPID, PRU identification information, PRUID, LOS / NLOS information associated with each carrier phase positioning measurement in the carrier phase positioning measurement, additional path information associated with each carrier phase positioning measurement in the carrier phase positioning measurement, PRU receiver error type information including any oscillator drift, clock drift, initial PRU phase offset or phase offset group, PRU ARP position error, PRU phase center offset, PRU measurement timestamp information, or carrier phase or timing measurement quality metric. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Figure 1 Illustrates an example of a wireless communication system supporting carrier phase positioning reporting in accordance with aspects of the present disclosure.

[0012] Figure 2 Illustrates an example of an NR beam-based positioning system related to carrier phase positioning reporting in accordance with aspects of the present disclosure.

[0013] Figure 3 Illustrates examples of absolute and relative positioning scenarios related to carrier phase positioning reporting in accordance with aspects of the present disclosure.

[0014] Figure 4 Illustrates an example of a multi-cell round-trip time (RTT) process related to carrier phase positioning reporting in accordance with aspects of the present disclosure.

[0015] Figure 5 Illustrates an example of an existing relative distance estimation system related to carrier phase positioning reporting in accordance with aspects of the present disclosure.

[0016] Figure 6 Illustrates an example of downlink (DL) or sidelink (SL) carrier phase measurement request and response report messaging related to carrier phase positioning reporting in accordance with aspects of the present disclosure.

[0017] Figure 7A and Figure 7B Illustrates an example request information element (IE) message related to carrier phase positioning reporting in accordance with aspects of the present disclosure.

[0018] Figure 8A and Figure 8B Illustrates an example response IE message related to carrier phase positioning reporting in accordance with aspects of the present disclosure.

[0019] Figure 9Illustrates examples of uplink (UL) carrier phase measurement request and response reporting message passing related to carrier phase positioning reporting in accordance with aspects of the present disclosure.

[0020] Figure 10 Illustrates examples of DL or SL carrier phase capability exchange messages related to carrier phase positioning reporting in accordance with aspects of the present disclosure.

[0021] Figure 11 Illustrates examples of IE messages related to carrier phase positioning reporting in accordance with aspects of the present disclosure.

[0022] Figure 12 Illustrates examples of IE messages related to carrier phase positioning reporting in accordance with aspects of the present disclosure.

[0023] Figure 13 and Figure 14 Illustrates examples of block diagrams of devices supporting carrier phase positioning reporting in accordance with aspects of the present disclosure.

[0024] Figures 15 to 21 Illustrates a flowchart of a method for supporting carrier phase positioning reporting in accordance with aspects of the present disclosure. Detailed Description

[0025] SL positioning can potentially support various RAT-related positioning techniques, including but not limited to SL-TDoA, SL-RTT, SL-AoA, etc. One positioning technique (i.e., carrier phase positioning (CPP)) uses carrier phase measurements to determine the distance between two nodes or entities and the absolute position of the target UE. Additionally, compared to other positioning techniques that require fine time or angle resolution to improve positioning performance, using carrier phase measurements does not require a large bandwidth. Thus, carrier phase positioning can be utilized in bandwidth-constrained situations.

[0026] Despite the 3GPP positioning framework that enables Uu interface UE-assisted and UE-based positioning methods, there is currently a lack of support for direct UE-to-UE absolute / relative position, distance, or orientation determination, which is crucial for supporting relative positioning applications across different vertical services such as V2X, public safety, IIoT, commerce, etc.

[0027] The techniques discussed herein support carrier phase measurements between devices and nodes within a network via a reporting configuration to enable accurate and timely reporting of carrier phase measurements or position information derived at least based on carrier phase measurements. A network entity provides a carrier phase positioning reporting configuration to a UE. The UE generates one or more carrier phase measurement reports based on the received carrier phase positioning reporting configuration. The UE sends the generated carrier phase measurement reports to a network entity, which may be the same network entity from which the carrier phase positioning reporting configuration was received or a different network entity.

[0028] Various different techniques are used to support carrier phase measurements between devices and nodes within a network. In one or more implementations, the techniques discussed herein allow different types of DL and SL carrier phase measurement reports according to the requested reporting configuration. Additionally or alternatively, the techniques discussed herein allow different types of UL carrier phase measurement reports according to the requested reporting configuration. Additionally or alternatively, the techniques discussed herein allow the sensing of devices capable of supporting carrier phase measurements on Uu or PC5. Additionally or alternatively, the techniques discussed herein allow error reporting notifications related to misconfigured DL or SL carrier phase configurations and / or inaccurate or erroneous measurements.

[0029] The techniques discussed herein allow the use of carrier phase positioning techniques and allow the transfer of carrier phase measurements between devices and nodes within a network via a reporting configuration that enables accurate and timely reporting of carrier phase measurements. The techniques discussed herein also allow for flexible use of carrier positioning techniques, where a configuration entity can specify various aspects of carrier phase measurements and measurement reports via a carrier phase positioning reporting configuration. The techniques discussed herein also allow the identification of other devices capable of supporting carrier phase measurements.

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

[0031] Figure 1FIG. illustrates an example of a wireless communication system 100 that supports carrier phase positioning reporting in accordance with aspects of the present disclosure. 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 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 the wireless communication system 100. One or more of the network entities 102 described herein may be or include or may be referred to as network nodes, base stations, network elements, radio access networks (RANs), base transceiver stations, access points, NodeBs, eNodeBs (eNBs), next-generation NodeBs (gNBs), or other suitable terms. The network entities 102 and the UEs 104 may communicate via a communication link 110, which may be a wireless or wired connection. For example, the network entities 102 and the UEs 104 may perform wireless communication (e.g., receive signaling, send signaling) via the Uu interface.

[0033] The network entity 102 may provide a geographical coverage area 112 for which the network entity 102 supports services (e.g., voice, video, packet data, messaging, broadcasting, etc.) for one or more UEs 104 within the geographical coverage area 112. For example, the network entity 102 and the UEs 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcasting, etc.) according to one or more radio access technologies. In some implementations, the network entity 102 may be movable, e.g., a satellite associated with a non-terrestrial network. In some implementations, different geographical coverage areas 112 associated with the same or different radio access technologies may overlap, but different geographical 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 geographical area of the wireless communication system 100. The UEs 104 may include or may be referred to as mobile devices, wireless devices, remote devices, remote units, handheld devices, subscriber devices, or some other suitable term. In some implementations, the UEs 104 may be referred to as units, stations, terminals, or clients, etc. Additionally or alternatively, the UEs 104 may be referred to as other examples such as Internet of Things (IoT) devices, Internet of Everything (IoE) devices, or machine type communication (MTC) devices, etc. In some implementations, the UEs 104 may be stationary in the wireless communication system 100. In some other implementations, the UEs 104 may be mobile in the wireless communication system 100.

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

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

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

[0038] In some implementations, network entity 102 may be configured in a split architecture that may be configured to utilize a protocol stack physically or logically distributed across 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, 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-RT RIC), a non-real-time RIC (non-RT RIC)), a service management and orchestration (SMO) system, or any combination thereof.

[0039] RU may also be referred to as a radio head, intelligent radio head, remote radio head (RRH), remote radio unit (RRU), or transmission and reception point (TRP). In a decomposed RAN architecture, one or more components of network entity 102 may be co-located, or one or more components of 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 the CU, DU, and RU can be flexible and can depend on 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) to support different functions. For example, a functional split of the protocol stack may be adopted between the CU and the DU such that the CU can support one or more layers of the protocol stack and the DU can support one or more different layers of the protocol stack. In some implementations, the CU may host upper layer 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 may be connected to one or more DUs or RUs, and one or more DUs or RUs may 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 may each be at least partially controlled by the CU.

[0041] Additionally or alternatively, a functional split of the protocol stack may be adopted between the DU and the RU such that the DU can support one or more layers of the protocol stack and the RU can 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 a protocol layer (e.g., some functions of a protocol layer may be performed by one of the CU, DU, or RU, while other functions of the protocol layer are performed by a different one of the CU, DU, or RU).

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

[0043] The core network 106 can support user authentication, access authorization, tracking, connection, and other access, routing, or mobility functions. The core network 106 can be an evolved packet core (EPC) or a 5G core (5GC), which can include a control plane entity for managing access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)), and a user plane entity for routing packets or interconnections to an external network (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)), or a location management function (LMF), which is a control plane entity for managing location services. In some implementations, in some implementations, the control plane entity can manage non-access stratum (NAS) functions, such as the mobility, authentication, and bearer management (e.g., data bearer, signaling 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 can communicate with the packet data network 108 via one or more backhaul links 116 (e.g., via S1, N2, N6, or another network interface). The packet data network 108 can include an application server 118. In some implementations, one or more UEs 104 can communicate with the application server 118. The UE 104 can 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 can 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 can 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 a wireless communication system 100, a network entity 102 and a UE 104 may use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, sub - frames, frames, etc.) or frequency resources (e.g., sub - carriers, 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 (i.e., 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 sub - carrier spacing and cyclic prefix. The first digital technology (e.g., μ = 0) may be associated with a first sub - carrier spacing (e.g., 15 kHz) and a normal cyclic prefix. The first digital technology (e.g., μ = 0) associated with the first sub - carrier spacing (e.g., 15 kHz) may utilize one time slot per sub - frame. The second digital technology (e.g., μ = 1) may be associated with a second sub - carrier spacing (e.g., 30 kHz) and a normal cyclic prefix. The third digital technology (e.g., μ = 2) may be associated with a third sub - carrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. The fourth digital technology (e.g., μ = 3) may be associated with a fourth sub - carrier spacing (e.g., 120 kHz) and a normal cyclic prefix. The fifth digital technology (e.g., μ = 4) may be associated with a fifth sub - carrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0047] The time interval of resources (e.g., communication resources) may be organized according to frames (also referred to as radio frames). Each frame may have a duration, e.g., a duration of 10 milliseconds (ms). In some implementations, each frame may include multiple sub - frames. For example, each frame may include 10 sub - frames, and each sub - frame may have a duration, e.g., a duration of 1 ms. In some implementations, each frame may have the same duration. In some implementations, each sub - frame of a frame may 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 can include a certain number (e.g., quantity) of time slots. Each time slot can 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 can depend on the digital technology. For a normal cyclic prefix, a time slot can include 14 symbols. For an extended cyclic prefix (e.g., applicable to a 60 kHz subcarrier spacing), a time slot can 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 can depend on the digital technology. It should be understood that a reference to a first digital technology (e.g., μ = 0) associated with a first subcarrier spacing (e.g., 15 kHz) can be used interchangeably between a subframe and a time slot.

[0049] In a wireless communication system 100, the electromagnetic (EM) spectrum can be split 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 name FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, the network entity 102 and the UE 104 can perform wireless communication on 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 can be used by the network entity 102 and the UE 104 and other equipment or devices for short-range, high data rate capabilities.

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

[0051] Network entity 102 provides carrier phase positioning report configuration 120 to UE 104. The network entity 102 can be, for example, an SL positioning server UE, an anchor UE, or a positioning reference unit (PRU) or a location server (LMF). UE 104 includes a carrier phase measurement report generation system 122 that generates a carrier phase measurement report 124 based on the received carrier phase positioning report configuration 120. UE 104 sends the carrier phase measurement report 124 to the network entity 102. Although UE 104 is illustrated as sending the carrier phase measurement report 124 to the network entity 102 from which the carrier phase positioning report configuration 120 is received, additionally or alternatively, UE 104 sends the carrier phase measurement report to another network entity instead of to the network entity 102 from which the carrier phase positioning report configuration 120 is received.

[0052] Communication between the devices discussed herein, such as the communication between UE 104 and network entity 102, is performed using any of a variety of different signaling. For example, such signaling can be any of a variety of messages, requests, or responses, such as a trigger message, a configuration message, etc. As another example, such signaling can be any of a variety of signaling media or protocols through which messages are transmitted, such as any combination of radio resource control (RRC), downlink control information (DCI), uplink control information (UCI), sidelink control information (SCI), media access control element (MAC-CE), sidelink positioning protocol (SLPP), PC5 radio resource control (PC5-RRC), etc.

[0053] NR positioning based on NR Uu signals and SA architecture (e.g., beam-based transmission) was first specified in Release 16. The target use cases also include commercial and regulatory (emergency services) scenarios in Release 15. The performance requirements are as follows:

[0054]

[0055] The current 3GPP Release 17 positioning has defined the positioning performance requirements for commercial and IIoT use cases, as shown below:

[0056]

[0057] The positioning technologies supported in Release 16 are listed in Table 1.

[0058] Table 1: Supported Rel-16 UE Positioning Methods

[0059]

[0060]

[0061] The individual positioning techniques shown in Table 1 can currently be configured and executed based on the requirements of the LMF capabilities and UE capabilities. The transmission of Uu (uplink and downlink) positioning reference signals (PRS) enables the UE to perform UE positioning-related measurements to enable the calculation of the UE's absolute position estimate and is configured per transmission reception point (TRP), where the TRP can include a set of one or more beams. Figure 2 A conceptual overview is illustrated therein.

[0062] Figure 2 An example of an NR beam positioning system 200 related to carrier phase positioning reporting in accordance with aspects of the present disclosure is illustrated. System 200 illustrates a UE 104 and a network entity 102 (e.g., a gNB). The PRS can be sent by different base stations (serving base stations and neighboring base stations) using narrow beams on FR1 and FR2, as shown in the example system 200, which is relatively different compared to LTE where the PRS is sent across cells. The PRS can be locally associated with a PRS resource identifier (ID) and a resource set ID (TRP) for the base station. Similarly, UE positioning measurements (such as reference signal time difference (RSTD) and PRS reference signal received power (RSRP) measurements) are made between beams (e.g., between different pairs of downlink (DL) PRS resources or DL PRS resource sets), rather than between different cells as in the case of LTE. In addition, there are additional uplink (UL) positioning methods for the network to utilize in order to calculate the location of the target UE.

[0063] Table 2 and Table 3 respectively show the reference signal to measurement mapping for each RAT-related positioning technique of the RAT-related positioning techniques supported at the UE and gNB. The RAT-related positioning techniques can utilize 3GPP RAT and core network entities to perform UE position estimation, which is different from the RAT-independent positioning techniques that rely on global navigation satellite systems (GNSS), inertial measurement unit (IMU) sensors, WLAN, and Bluetooth technologies for performing target device (UE) positioning.

[0064] Table 2: UE Measurements for Implementing RAT-Related Positioning Techniques

[0065]

[0066] Table 3: gNB Measurements to Enable RAT-Related Positioning Techniques

[0067]

[0068]

[0069] Figure 3 Example 300 illustrates examples of absolute and relative positioning scenarios related to carrier phase positioning reports in accordance with aspects of the present disclosure. The network device described with reference to Example 300 may be used with and / or implemented with the wireless communication system 100 and includes a UE 104 and a network entity 102 (e.g., eNB, gNB). Example 300 is an overview of absolute and relative positioning scenarios defined in a building (phase 1) specification using three different coordinate systems, including traditional absolute positioning at (III) 302, a fixed coordinate system; relative positioning at (II) 304, a variable and moving coordinate system; and relative positioning at (I) 306, a variable coordinate system. It is noted that the relative positioning, variable coordinate system at 306 is based on the relative device positions in a variable coordinate system, where the reference can always change with multiple nodes moving in different directions. Example 300 also includes a scenario 308 outside the coverage area, where the UEs need to determine their relative positions with respect to each other.

[0070] The relative positioning, variable and moving coordinate system at 304 can support a relative lateral position accuracy of 0.1 meter between UEs supporting V2X applications and can support a relative longitudinal position accuracy of less than 0.5 meter for UEs supporting V2X applications for nearby queuing. The relative positioning, variable coordinate system at 306 can support relative positioning between a UE and positioning nodes within 10 meters of each other. The relative positioning, variable coordinate system at 306 can also support vertical positioning of the UE's relative height / depth with respect to the local ground.

[0071] Versions 16 and 17 support various RAT-related positioning techniques such as DL-TDoA, DL-AoD, multi-RTT, E-CID / NR E-CID, UL-TDoA, and UL-AoA.

[0072] The DL-TDOA positioning method utilizes the DL RSTD (and optionally DL PRS RSRP) of the downlink signals received at the UE from multiple TPs. The UE uses the assistance data received from the positioning server to measure the DL RSTD (and optionally DL PRS RSRP) of the received signals, and the resulting measurements are used together with other configuration information to position the UE with respect to adjacent TPs.

[0073] The DL AoD positioning method utilizes the measured DL PRSRSRP of the downlink signals received at the UE from multiple TPs. The UE uses the assistance data received from the positioning server to measure the DL PRS RSRP of the received signals, and the resulting measurements are used together with other configuration information to position the UE with respect to adjacent TPs.

[0074] The multi-RTT positioning method utilizes UE Rx-Tx measurements and DL PRS RSRP of downlink signals received from multiple TRPs measured by the UE, and gNB Rx-Tx measurements and ULSRS-RSRP measured at multiple TRPs of uplink signals transmitted by the UE.

[0075] Figure 4 An example 400 of a multi-cell RTT process related to carrier phase positioning reporting according to aspects of the present disclosure is illustrated. The multi-RTT positioning technique utilizes UE Rx-Tx measurements and DL PRS RSRP of downlink signals received from multiple TRPs measured by the UE, and gNB Rx-Tx measurements and uplink sounding reference signal (SRS) RSRP (UL SRS-RSRP) measured at multiple TRPs of uplink signals transmitted by the UE. The UE uses assistance data received from a positioning server (also referred to herein as a location server) to measure UE Rx-Tx measurements (and optionally DL PRS RSRP of the received signal), and the TRP uses assistance data received from the positioning service to measure gNB Rx-Tx measurements (and optionally UL SRS-RSRP of the received signal). The measurements are used to determine the RTT at the positioning server, which is used to estimate the location of the UE. In Release 16, as shown in Table 1, multi-RTT is only supported for UE-assisted and NG RAN-assisted positioning techniques.

[0076] Figure 5 An example of a system 500 for existing relative distance estimation related to carrier phase positioning reporting according to aspects of the present disclosure is illustrated. System 500 illustrates relative distance estimation using an existing single gNB RTT positioning framework. A location server (LMF) can configure measurements for different UEs, and then the target UE can report its measurements to the location server in a transparent manner. The location server can calculate the absolute location, but to obtain the relative distance between two UEs, it requires prior information such as the location of the target UE. The latency of this method is high, and it is not an efficient method in terms of process and signaling overhead.

[0077] For NR enhanced cell ID (E-CID) positioning technology, the location of the UE is estimated using the knowledge of its serving ng-eNB, gNB, and cell, and is based on LTE signals. Information about the serving ng-eNB, gNB, and cell can be obtained through paging, registration, or other methods. NR enhanced cell ID (NR E-CID) positioning refers to the technology that uses additional UE measurements and / or NR radio resources and other measurements to use NR signals to improve UE location estimation. Although enhanced cell ID (E-CID) positioning can utilize some of the same measurements as the measurement control system in the RRC protocol, the UE may not perform additional measurements solely for positioning purposes; that is, the positioning process does not provide measurement configuration or measurement control messages, and the UE reports its available measurements without taking additional measurement actions.

[0078] Uplink time difference of arrival (UL-TDOA) positioning technology utilizes the UL-RTOA (and optionally UL SRS-RSRP) of the uplink signal transmitted from the UE at multiple receiving points (RPs). The RPs use the auxiliary data received from the positioning server to measure the UL-RTOA (and optionally UL SRS-RSRP) of the received signal, and the resulting measurements are used together with other configuration information to estimate the location of the UE.

[0079] Uplink angle of arrival (UL-AoA) positioning technology utilizes the azimuth of arrival and zenith of arrival of the uplink signal transmitted from the UE at multiple RPs. The RPs use the auxiliary data received from the positioning server (also referred to as the location server in this document) to measure the azimuth AoA (A-AoA) and zenith AoA (Z-AoA) of the received signal, and the resulting measurements are used together with other configuration information to estimate the location of the UE.

[0080] Various RAT-independent positioning technologies can also be used, such as network-assisted GNSS technology, barometric sensor positioning, WLAN positioning, Bluetooth positioning, TBS positioning, and motion sensor positioning.

[0081] Network-assisted GNSS technology utilizes a UE equipped with a radio receiver capable of receiving GNSS signals. In 3GPP specifications, the term GNSS includes both global and regional / augmented navigation satellite systems. Examples of global navigation satellite systems include the Global Positioning System (GPS), modernized GPS, Galileo, GLONASS, and the BeiDou Navigation Satellite System (BDS). Regional navigation satellite systems include the Quasi-Zenith Satellite System (QZSS), while many augmentation systems are classified under the general term of Satellite-Based Augmentation System (SBAS) and provide regional augmentation services. Network-assisted GNSS technology can use different GNSSs (e.g., GPS, Galileo, etc.) individually or in combination to determine the location of the UE.

[0082] Barometric pressure sensor positioning technology utilizes a barometric pressure sensor to determine the vertical component of the UE's location. The UE measures the barometric pressure (optionally with the aid of auxiliary data) to calculate the vertical component of its location, or sends the measurement to a positioning server for location calculation. This technology should be combined with other positioning methods to determine the 3D location of the UE.

[0083] WLAN positioning technology utilizes WLAN measurements (access point (AP) identifiers and optionally other measurements) and a database to determine the location of the UE. The UE measures the signals received from WLAN access points (optionally with the aid of auxiliary data) to send the measurements to a positioning server for location calculation. Using the measurement results and a reference database, the location of the UE is calculated. Additionally or alternatively, the UE uses the WLAN measurements and optionally WLAN AP auxiliary data provided by the positioning server to determine its location.

[0084] Bluetooth positioning technology utilizes Bluetooth measurements (beacon identifiers and optionally other measurements) to determine the location of the UE. The UE measures the signals received from Bluetooth beacons. Using the measurement results and a reference database, the location of the UE is calculated. The Bluetooth method can be combined with other positioning methods (e.g., WLAN) to improve the positioning accuracy of the UE.

[0085] TBS positioning technology utilizes TBS, which includes a terrestrial transmitter network that broadcasts signals solely for positioning purposes. Examples of the types of TBS positioning signals are MBS (Metropolitan Beacon System) signals and positioning reference signals (PRS). The UE measures the received TBS signals (optionally with the aid of auxiliary data) to calculate its location or sends the measurements to a positioning server for location calculation.

[0086] Motion sensor positioning technology uses different sensors such as accelerometers, gyroscopes, magnetometers, etc. to calculate the displacement of the UE. The UE estimates the relative displacement based on a reference position and / or a reference time. The UE sends a report including the determined relative displacement, which can be used to determine the absolute position. This method can be used together with other positioning methods for hybrid positioning.

[0087] Different DL measurements for RAT-related positioning technology include DL PRS-RSRP, DL RSTD, and UE Rx-Tx time difference. The following measurement configurations can be used: 4 pairs of DL RSTD measurements can be performed for each pair of cells, and each measurement is performed between different pairs of DL PRS resources / resource sets with a single reference timing; 8 DL PRS RSRP measurements can be performed on different DL PRS resources from the same cell.

[0088] The DL PRS reference signal received power (DL PRS-RSRP) is defined as: the linear average of the power contributions (in [W]) of the resource elements carrying the DL PRS reference information configured for RSRP measurement within the considered measurement frequency bandwidth. For frequency range 1, the reference point for DL PRS-RSRP is the antenna connector of the UE. For frequency range 2, the DL PRS-RSRP is measured based on the combined signal from the antenna elements corresponding to a given receiver branch. For frequency range 1 and frequency range 2, if the UE is using receiver diversity, the reported DL PRS-RSRP value is not lower than the corresponding DL PRS-RSRP of any individual receiver branch. DL PRS-RSRP is applicable within RRC_CONNECTED frequencies and between RRC_CONNECTED frequencies.

[0089] The DL reference signal time difference (DL RSTD) is the DL relative timing difference between positioning node j and reference positioning node i, defined as T SubframeRxj -T SubframeRxi , where T SubframeRxj is the time when the UE receives the start of a subframe from positioning node j, and T SubframeRxi is the corresponding start time of the subframe that the UE receives from positioning node i and is closest in time to the subframe received from positioning node j. Multiple DL PRS resources can be used to determine the start of a subframe from a positioning node. For frequency range 1, the reference point for DL RSTD is the antenna connector of the UE. For frequency range 2, the reference point for DL RSTD is the antenna of the UE. DL RSTD is applicable within RRC_CONNECTED frequencies and between RRC_CONNECTED frequencies.

[0090] The UE Rx-Tx time difference is defined as T UE-Rx -T UE-Tx , where T UE-Rx is the reception timing of the UE for the downlink subframe #i from the positioning node, defined by the first detected path in time, and T UE-Tx is the transmission timing of the UE for the uplink subframe #j, which is the subframe closest in time to the subframe #i received from the positioning node. Multiple DL PRS resources can be used to determine the start of a subframe of the first arrival path of the positioning node. For frequency range 1, the reference point for T UE-RX measurement should be the RX antenna connector of the UE, and the reference point for T UE-TX measurement should be the TX antenna connector of the UE. For frequency range 2, the reference point for T UE-RX measurement should be the RX antenna of the UE, and the reference point for T UE-TX measurement should be the TX antenna of the UE. The UE Rx-Tx time difference applies within the RRC_CONNECTED frequency and between RRC_CONNECTED frequencies.

[0091] The DL PRS reference signal received path power (DL PRS-RSRPP) is defined as: the power of the linear average of the channel response at the i-th path delay of the resource elements carrying the DL PRS signal configured for measurement, where the DL PRS-RCRPP for the first path delay is the power contribution corresponding to the first detected path in time. For frequency range 1, the reference point for DL PRS-RSRPP is the antenna connector of the UE. For frequency range 2, DL PRS-RSRPP is measured based on the combined signal from the antenna elements corresponding to a given receiver branch. DL PRS-RSRPP applies to RRC_CONNECTED and RRC_INACTIVE.

[0092] In one or more implementations, carrier phase measurements using at least a single measurement instance are considered to evaluate NR carrier phase positioning performance.

[0093] In one or more implementations, the impact of cycle slips on NR carrier phase positioning and potential solutions to resolve cycle slips are considered.

[0094] In one or more implementations, research on improving the accuracy of NR carrier phase measurements may consider: UE- and UE-assisted carrier phase positioning; UL carrier phase positioning and DL carrier phase positioning; NR carrier phase positioning using carrier phase measurements of one carrier frequency or multiple frequencies; combination of NR carrier phase positioning with another standardized Rel.17 positioning method (e.g., DL-TDOA, UL-TDOA, Multi-RTT, etc.). It should be noted that using "carrier phase positioning" does not necessarily mean it is an independent positioning method.

[0095] In one or more implementations, the impact of multipath on carrier phase positioning is considered.

[0096] In one or more implementations, methods for mitigating the impact of multipath on carrier phase positioning are considered.

[0097] In one or more implementations, reusing the simulation assumptions of NR Rel-16 / 17 for carrier phase positioning is considered. Additionally or alternatively, optional modifications to the simulation assumptions defined in NR Rel-16 / 17 may be considered.

[0098] In one or more implementations, baselines and optional evaluation scenarios are considered. For example, the baseline evaluation scenario may include at least one of InF-SH and InF-DH. Again, for example, the optional evaluation scenario may include at least one of IOO, Umi, and Highway. It should be noted that other evaluation scenarios are not excluded, and the existing Rel-17 DL / UL reference signals in the Uu interface can be used for the Highway scenario. For the baseline evaluation scenario, the frequency range may be FR1, and for the optional evaluation scenario, the frequency range may be FR2.

[0099] In one or more implementations (e.g., in addition to the evaluation assumptions of NR Rel-16 / 17), at least one of the following error sources may also be considered: phase noise (e.g., in FR2), carrier frequency offset (CFO) / Doppler, oscillator drift, transmitter / receiver antenna reference point position error, transmitter / receiver initial phase error, and phase center offset. It should be noted that other error sources are not excluded. Additionally or alternatively, UE mobility may be considered. Additionally or alternatively, one or more error sources may be jointly evaluated. Additionally or alternatively, an error source model is provided along with its evaluation.

[0100] In one or more implementations, consider the following. For NR downlink and / or uplink carrier phase positioning, the carrier phase (CP) of the radio frequency (RF) frequency at the receiver is a function of the signal propagation time from the Tx antenna reference point of the transmitter (e.g., TRP or UE) to the Rx antenna reference point of the receiver (e.g., UE or TRP). The propagation time can be represented by the fractional part of the period of the RF frequency and the number of integer periods, but the CP can be independent of the number of integer periods.

[0101] In one or more implementations, consider using a PRU to facilitate NR carrier phase positioning.

[0102] In one or more implementations, existing DL PRS and UL SRS for positioning can be reused as reference signals to enable positioning based on NR carrier phase measurements for both UE-based positioning and UE-assisted positioning. In one or more implementations, consider enhancements to existing DL PRS and UL SRS to obtain better positioning performance.

[0103] In one or more implementations, for UE-assisted or UE-based NR carrier phase positioning, consider at least one of the following options: the difference between the carrier phase measured from the (multiple) DL PRS signals of the target TRP and the carrier phase measured from the (multiple) DL PRS signals of the reference TRP, and the carrier phase measured from the (multiple) DL PRS signals of the TRP.

[0104] In one or more implementations, consider the benefits of using carrier phase measurements of multiple DL positioning frequency layers for NR carrier phase positioning, which can include the effect of the time gap between carrier phase measurements of multiple DL PFLs. The initial phase error and frequency error of each PFL can be independently modeled. It can be assumed that the PRS signals of all PFLs of the TRP are transmitted from the same antenna reference point (ARP) or different ARPs of the TRP. The position error of the ARP can be independently modeled. For PFLs in different frequency bands or frequency ranges, the timing error of the PFL can be different. In one or more implementations, consider that simultaneous reception of DL PRS from multiple frequency layers is not supported in Rel-17.

[0105] In one or more implementations, for UL UE-assisted NR carrier phase positioning, for positioning purposes, consider the carrier phase measured from the UL SRS. The use of multiple-input multiple-output (MIMO) SRS for positioning purposes can be transparent to the UE.

[0106] In one or more implementations, consider the impact of multipath / non-line-of-sight (NLOS) on NR carrier phase positioning. Additionally or alternatively, consider the multipath / NLOS degradation of carrier phase positioning performance and multipath mitigation for NR carrier phase positioning.

[0107] In one or more implementations, with regard to error modeling, it may be assumed that the initial phases of transmitters of different carriers are independent of each other. Similarly, it may be assumed that the initial phases of receivers of different carriers are independent of each other.

[0108] In one or more implementations, consider the effectiveness of the following multipath mitigation methods for carrier phase positioning and the potential for standard operation. For example, it may be considered to identify and separate the first path and other paths. As another example, it may be considered to report the carrier phase of the first path and optionally report additional paths. As another example, it may be considered to use the line-of-sight (LOS) / NLOS indication for carrier phase measurement (e.g., the Rel-17 LOS / NLOS indicator can be regarded as a starting point). As another example, consider the reporting of other channel information such as RSRP / RSRPP.

[0109] In one or more implementations, consider at least one of the following NR carrier phase positioning methods and identify the potential impact on the standard: reporting the carrier phase measurement together with the existing positioning measurement, and reporting only the carrier phase-based measurement without reporting the existing positioning measurement.

[0110] In one or more implementations, the initiating device initiates an SL positioning / ranging session and can be a network entity (e.g., gNB, LMF) or a UE / roadside unit (RSU).

[0111] In one or more implementations, the responding device responds to the SL positioning / ranging session from the initiating device and can be a network entity (e.g., gNB, LMF) or a UE / roadside unit (RSU).

[0112] In one or more implementations, the target UE can be referred to as the UE of interest, and its location (absolute or relative location) will be obtained by the network or the UE itself (e.g., using SL, such as the PC5 interface).

[0113] In one or more implementations, sidelink positioning refers to using reference signals transmitted through SL (e.g., the PC5 interface) to position the UE to obtain absolute location, relative location, or ranging information.

[0114] In one or more implementations, ranging refers to determining the distance and / or direction between the UE and another entity (e.g., an anchor UE).

[0115] In one or more implementations, an anchor UE refers to a UE that supports the positioning of the target UE, e.g., by transmitting and / or receiving reference signals for positioning through the SL interface, providing positioning-related information, etc. The anchor UE can also be referred to as a reference UE or an SL reference UE.

[0116] In one or more implementations, when direct ranging / sidelink positioning between the SL reference UE / anchor UE and the target UE cannot be supported, the assisting UE refers to a UE that supports ranging / sidelink positioning between the SL reference UE and the SL target UE via the SL (e.g., PC5 interface). The measurements / results of ranging / sidelink positioning between the assisting UE and the SL reference UE and between the assisting UE and the target UE are determined and used to derive the ranging / sidelink positioning result between the target UE and the SL reference UE.

[0117] In one or more implementations, the SL positioning server UE refers to a UE that provides position calculations for services based on SL positioning and ranging. The SL positioning server UE interacts with other UEs via the SL (e.g., PC5 interface) as needed to calculate the position of the target UE. If position calculation is supported, the target UE or the SL reference UE can act as the SL positioning server UE.

[0118] In one or more implementations, the SL positioning client UE refers to a third-party UE other than the SL reference UE and the target UE that initiates a ranging / sidelink positioning service request on behalf of the application residing on it. The SL positioning client UI does not have to support ranging / sidelink positioning capabilities, but communication is established between the SL positioning client UE and the SL reference UE / target UE, e.g., via PC5 or 5GC, for the transmission of service requests and results.

[0119] In one or more implementations, the SL positioning node can refer to a network entity and / or device / UE participating in an SL positioning session, such as an LMF (location server), gNB, UE, RSU, anchor UE, initiator, and / or responder UE.

[0120] In one or more implementations, the configuration entity refers to a network node or device / UE capable of configuring time-frequency resources and related SL positioning configurations. The SL positioning server UE can be used as the configuration entity.

[0121] In one or more implementations, the configuration entity refers to a network node or device (e.g., UE) capable of configuring time-frequency resources and related SL positioning configurations. The SL positioning server UE can be used as the configuration entity.

[0122] Various solutions for implementing carrier phase positioning reports are discussed herein. One solution discussed herein is to support different types of DL and SL carrier phase measurement reports according to the requested report configuration. Another solution discussed herein is to support different types of UL carrier phase measurement reports according to the requested report configuration. Another solution discussed herein is to enable the awareness of devices that support carrier phase measurements on Uu or PC5. Another solution discussed herein is to support error reporting notifications related to misconfigured DL or SL carrier phase configurations and / or inaccurate or erroneous measurements.

[0123] The various solutions discussed herein can be implemented in combination with each other to support NR RAT-related positioning methods on the SL (e.g., PC5) interface.

[0124] Positioning-related reference signals can be referred to as reference signals for positioning processes or purposes to estimate the location of a target UE (e.g., PRS) or reference signals based on existing reference signals such as channel state information reference signals (CSI-RS) or SRS; the target UE can be referred to as the device or entity to be located or positioned. In various implementations, the term "PRS" can refer to any signal, such as a reference signal, which may or may not be primarily used for positioning.

[0125] References to location or location information can refer to absolute location, relative location with respect to another node / entity, ranging in terms of distance, ranging in terms of direction, or a combination thereof.

[0126] In one or more implementations, various report configurations can be sent by a configuration entity to enable different methods of reporting DL and SL carrier phase measurements. These reporting methods also include: any location information derived based solely on carrier phase measurements or jointly based on other DL or SL positioning measurements, such as DL-RSTD, UE Rx-Tx time difference measurement, DL PRS RSRPP / RSRP, SL PRS RSRP / RSRPP, SL-AoA, SL RSTD, SL-RTOA, etc.

[0127] Figure 6 An example of DL or SL carrier phase measurement request and response reporting message passing 600 related to carrier phase positioning reports according to aspects of the present disclosure is illustrated. Message passing 600 shows the request and response signaling for exchanging carrier phase-related reported measurements between a configuration entity and a target UE 104. The configuration entity can be at least one of the following: an SL positioning server UE 602, an anchor UE or PRU 604, and an LMF 606. According to Figure 6In the messaging 600 shown, the carrier phase measurement request and response reporting messaging can be signaled using the LTE positioning protocol (LPP) for DL carrier phase measurement, such as using the LPP RequestLocationInformation and / or LPP ProvideLocationInformation messages; or using the SLPP (SL positioning protocol) for SL carrier phase measurement, such as using the SLPP RequestLocationInformation and / or SLPP ProvideLocationInformation messages. On SL, such reporting configuration messages can be sent using a security mechanism via unicast, multicast, or broadcast messages. Security can include integrity and cipher protection.

[0128] According to the messaging 600, the messaging for requesting and reporting DL or SL carrier phase measurements is as follows. An entity or node (e.g., any one of the LMF 606, anchor or PRU UE 604, SL positioning server 602 (e.g., sidelink positioning server UE)) can request the target UE 104 to provide multiple carrier phase measurements. The target UE 104 can physically respond to any one of the entity or nodes (e.g., LMF 606, anchor or PRU UE 604, SL positioning server UE) with one set of carrier phase measurements or multiple sets of carrier phase measurements and assistance information to help process the carrier phase measurements. The target UE 104 can respond to the same entity or node from which the request was received, or to a different entity or node. For example, the target UE 104 can receive a request to provide multiple carrier phase measurements from the SL positioning server 602 and respond by sending multiple carrier phase measurements to the LMF 606.

[0129] Additionally or alternatively, in the case of UE-based positioning, the target UE 104 may request DL or SL carrier phase measurements from the PRU via the aforementioned request signaling mechanism. The target UE 104 may request DL or SL carrier phase measurements from the PRU directly via SLPP signaling, or the target UE may use the gNB and LMF to request PRU carrier phase measurements via LPP. For example, the LMF may respond to the request by providing PRU carrier phase measurements to multiple target UEs via the LPP ProvideAssistanceData or RequestLocationInformation message or via new or existing positioning system information broadcast signaling (posSIB). The information that may be associated with each PRU carrier phase measurement may include: carrier frequency information, PRU integer ambiguity information, such as value range and quality metric, SCS, positioning frequency layer information, PRS resource ID, PRS resource set ID, TRP ID, PRU identification information (such as PRU ID), LOS / NLOS information (hard indicator or soft indicator) associated with each carrier phase measurement, additional path information associated with each carrier phase measurement, PRU receiver error type information (including any oscillator drift, clock drift, initial PRU phase offset or phase offset group), PRU ARP position error, PRU phase center offset information, PRU measurement timestamp information, carrier phase and / or timing measurement quality metric, etc. The reported carrier phase measurements may be derived from one or more PRUs near the target UE.

[0130] Figure 7A and Figure 7B illustrates an example request information element (IE) message 700 related to carrier phase positioning reporting in accordance with aspects of the present disclosure. The IE message 700 is an example of an NR-DL-CP-RequestLocationInformation IE message (e.g., as Figure 6 shown, sent from the SL positioning server 602, the anchor UE, or the PRU 604, or the LMF 606 to the target UE 104). The IE message 700 illustrates different elements, components, and associated descriptions for supporting DL carrier phase positioning measurement reporting.

[0131] The NR-DL-CP-RequestLocationInformation IE message 700 includes several fields, as discussed in more detail below.

[0132] The nr-AssistanceAvailability field indicates whether the target device can request additional PRS assistance data from the server. TRUE indicates permission, while FALSE indicates non-permission. The nr-AssistanceAvailability field can also indicate whether PRS on demand for carrier phase positioning can be supported.

[0133] The nr-DL-PRS-CPP-Request field indicates whether the target device is requested to report the (multiple) DL-PRS resource IDs or (multiple) DL-PRS resource set IDs associated with each DL carrier phase measurement for each positioning frequency layer.

[0134] The nr-RequestedMeasurements field specifies the additional NR positioning measurements requested, such as RSRP, RSTD, ToA, etc. In one or more implementations, this is represented by a bit string, where a value at a bit position indicates that a specific measurement is requested; a zero value indicates that it is not requested.

[0135] The additionalPaths field (if present) indicates that the target device is requested to provide the nr-AdditionalPathList in the carrier phase measurement report. If this field is present, the additionalPathsExt field does not exist.

[0136] The nr-UE-RxInitialPhaseOffset-Request field (if present) indicates that the target device is requested to provide the Rx initial phase offset in the DL carrier phase measurement report.

[0137] The nr-UE-PhaseOffsetGroup-Request field (if present) indicates that the target device is requested to provide the Rx phase offset group for all DL PRS resources within a small margin in the DL carrier phase measurement report.

[0138] The nr-UE-RxARPError-Request field (if present) indicates that the target device is requested to provide the Rx antenna reference point error in the DL carrier phase measurement report.

[0139] The nr-UE RxOscillatorDrift-Request field (if present) indicates that the target device is requested to provide the Rx oscillator drift in the DL carrier phase measurement report.

[0140] The nr-UE-RxCFO-Request field (if present) indicates that the target device is requested to provide the Rx carrier frequency offset in the DL carrier phase measurement report.

[0141] The nr-UE-RxPhaseCenterOffset-Request field, if present, indicates that the target device is requested to provide the Rx antenna phase center offset in the DL carrier phase measurement report.

[0142] The nr-los-nlos-IndicatorRequest field, if present, indicates that the target device is requested to provide the indication type and granularity of the estimated LOS-NLOS-Indicator in the DL carrier phase measurement report.

[0143] The additionalPathsExt field, if present, indicates that the target device is requested to provide the nr-AdditionalPathListExt in the DL carrier phase measurement report. If this field is present, the additionalPaths field is not present.

[0144] The additionalPathsDL-PRS-RSRP-Request field, if present, indicates that the target device is requested to provide the nr-DL-PRS-RSRPP for the additional paths in the IE NR-AdditionalPathList.

[0145] The multiMeasInSameReport field, if present, indicates that the target device is requested to provide multiple measurement instances in a single measurement report; for example, include the nr-DL-CPP-SignalMeasurementInstances (in the case of requesting UE-assisted mode) or nr-DL-CPP-LocationInformationInstances (in the case of requesting UE-based mode) in the IE NR-DL-CPP-ProvideLocationInformation.

[0146] The maxDL-PRS-CPP-MeasurementsPerTRPPair field specifies the maximum number of DL-PRS DL carrier phase measurements per pair of TRPs. This maximum number is defined across all positioning frequency layers. Then, the carrier phase difference is obtained for each pair of TRPs and may be affected by the UE capabilities.

[0147] The maxDL-PRS-DL-CPP-MeasurementsPerTRP field specifies the maximum number of DL carrier phase measurements from the same TRP. This maximum number is defined across all positioning frequency layers and may be affected by the UE capabilities.

[0148] The phaseReportingGranularityFactor field specifies the recommended reporting granularity for DL carrier phase measurements. The UE can select different granularity values or step values, expressed in radians or degrees, based on the configured step values (e.g., [0, 0.1, ..., 2pi]). Different step values can be configured to reduce the reporting overhead.

[0149] The requestedDL-PRS-ProcessingSamples field, if present, indicates the number of DL-PRS processing samples requested for performing DL carrier phase measurements. For example, the enumerated value'm1' indicates 1-sample DL-PRS processing.

[0150] Figure 8A and Figure 8B FIG. illustrates an example response IE message 800 related to carrier phase positioning reporting according to aspects of the present disclosure. IE message 700 is an example of an NR-DL-CP-SignalMeasurementInformation IE message that is part of a ProvideLocationInformation message (e.g., sent by Figure 6 target UE 104 to Figure 6 LMF 606, anchor UE / PRU 604, or SL positioning server 602). IE message 800 illustrates different elements, components, and related descriptions for supporting DL carrier phase positioning measurement reporting.

[0151] The NR-DL-CP-SignalMeasurementInformation IE message 800 includes several fields, as discussed in more detail below.

[0152] The nr-DL-PRS-RSRP-Result field specifies the NR DL-PRS reference signal received power (DL PRS-RSRP) measurement.

[0153] The nr-DL-PRS-FirstPathRSRP-Result field specifies the nr DL-PRS reference signal received path power (DL PRS-RSRPP) of the first detected path in time, as defined in 3GPP Technical Specification (TS) 38.215. The mapping of the measured quantity is as defined in 3GPP TS 38.133.

[0154] The dl-PRS-ID field is used together with the DL-PRS resource set ID and the DL-PRS resource ID to uniquely identify the DL-PRS resource. This ID can be associated with multiple DL-PRS resource sets associated with a single TRP. Each TRP can only be associated with one such ID.

[0155] The nr-PhysCellID field defines: the physical cell identity of the associated TRP.

[0156] The nr-CellGlobalID field defines: the NR cell global identifier (NCGI) of the associated TRP, i.e., the globally unique identifier of the cell in NR, as defined in 3GPP TS 38.331.

[0157] The nr-ARFCN field defines: the NR-ARFCN of the CD-SSB (as defined in 3GPP TS 38.300) of the TRP corresponding to the nr-PhysCellID.

[0158] The nr-TimeStamp field defines: the time instance at which the DL carrier phase measurement, time of arrival (TOA), or DL PRS-RSRP / RSRPP (if included) measurement is performed. The nr-SFN and nr-Slot in the IE NR-TimeStamp correspond to the TRP provided in the dl-PRS-ReferenceInfo specified in 3GPP TS 38.214. The TOA measurement refers to the TOA of the adjacent TRP or the reference TRP (if applicable). This can be combined with the nr-DL-CP or nr-DL-CP-ResultDiff IE for reporting.

[0159] The nr-DL-CP field defines: the carrier phase measurement of a single positioning frequency layer. Additionally or alternatively, this field can also define: the relative carrier phase difference between the adjacent TRP and the PRS reference TRP.

[0160] The nr-AdditionalPathList field specifies: one or more additional carrier phase measurement path timing values of the TRP or resource relative to the path timing used to determine the nr-DL-CP value. If this field is requested but not included, it indicates that the UE has not detected any additional path timing values. If this field exists, the field nr-AdditionalPathListExt does not exist.

[0161] The nr-TimingQuality field defines: the best estimate of the TOA measurement quality of the target device.

[0162] Definition of the nr-CarrierPhaseQuality field: The best estimate by the target device of the DL carrier phase measurement quality. Additionally or alternatively, the DL carrier phase measurement refers to the DL carrier phase measurement of this neighboring TRP or reference TRP, which (if applicable) is used to determine the nr-DL-CP or nr-DL-CP-ResultDiff.

[0163] The nr-los-nlos-Indicator field specifies: The best estimate by the target device of the LOS or NLOS of the DL carrier phase measurement of the TRP or resource. Note that the DL carrier phase measurement refers to the DL carrier phase of this neighboring TRP or reference TRP, which (if applicable) is used to determine that this can be reported together with the nr-DL-CP or nr-DL-CP-ResultDiff. This can be a hard (binary) indicator, while in another implementation, a soft indicator can be used.

[0164] Relative to the path timing used to determine the nr-DL-CP value, the nr-AdditionalPathListExt field provides up to 8 additional detected path timing values for the TRP or resource. In other implementations, the maximum number of additional detected paths can be configured to other values. If this field is requested but not included, it indicates that the UE has not detected any additional path timing values. If this field exists, the field nr-AdditionalPathList should not exist.

[0165] The nr-DL-CP-ResultDiff field provides an additional DL carrier phase measurement result relative to the nr-DL-CP. The measured DL carrier phase value is obtained by adding the value of this field to the value of the nr-DL-CP field. This field provides any incremental or differential report relative to the previously reported DL carrier phase measurement and the current or latest DL carrier phase measurement.

[0166] The nr-DL-PRS-RSRP-ResultDiff field provides an additional DL-PRS RSCP measurement result relative to the nr-DL-PRS-RSRP-Result. The measured DL-PRS RSRP value is obtained by adding the value of this field to the value of the nr-DL-PRS-RSRP-Result field.

[0167] The nr-DL-PRS-FirstPathRSRP-ResultDiff field specifies the additional NR DL PPRS reference signal received path power (DL PRS-RSRPP) of the first detected path in time relative to nr-DL-PRS-FirstPathRSRP-Result. The DL-PRS RSRPP of the first path value of this measurement is obtained by adding the value of this field to the value of the nr-DL-PRS-FirstPathRSRP-Result field.

[0168] The nr-UE-RxInitialPhaseOffset field (if present) indicates the initial phase offset of the target device in the DL carrier phase measurement report.

[0169] The nr-UE-PhaseOffsetGroup field (if present) indicates the phase offset group of the target device across different PRS resources of different beams / TRPs within the margin defined in the DL carrier phase measurement report for all DL PRS resources within a small margin.

[0170] The nr-UE-RxARPError field (if present) indicates the antenna reference point error of the target device in the DL carrier phase measurement report. This field can be characterized by a specific Rx ARP error ID, and the position type can be defined according to the ARP position relative to the geodetic coordinates or the ARP position relative to the Cartesian coordinates

[0171] The nr-UE-RxOscillatorDrift field (if present) indicates the oscillator drift of the target device in the DL carrier phase measurement report.

[0172] The nr-UE-RxCFO field (if present) indicates the carrier frequency offset of the target device in the DL carrier phase measurement report.

[0173] The nr-UE-RxPhaseCenterOffset field (if present) indicates the antenna phase center offset of the target device in the DL carrier phase measurement report.

[0174] In one or more implementations, the above-described reporting configuration given by NR-DL-CP-RequestLocationInformation can be extended to an SL carrier phase reporting configuration, such as that defined by NR-SL-CP-RequestLocationInformation. Similarly, the above-described DL carrier phase measurement report given by NR-DL-CP-SignalMeasurementInformation can be extended to an SL carrier phase measurement report, such as that defined by NR-SL-CP-SignalMeasurementInformation.

[0175] Additionally or alternatively, the reporting type applicable to carrier phase measurements can be configured as a single-shot report, a periodic report, an event-triggered report, or a combination thereof. A single-shot report is also referred to as an immediate report, where the target device is requested to report carrier phase measurements immediately when ready or available. The periodic report of carrier phase measurements can also be configured with a configured reporting quantity and a reporting interval or period. Additionally or alternatively, the report can also be semi-persistent using activation and deactivation commands of lower signaling (e.g., RRC or MAC CE). Event-triggered reports of carrier phase measurements can also be supported, depending on certain configuration events, such as tracking area change, cell change, operating notification area change, area change, horizontal or vertical relative distance exceeding a specific threshold, timer expiration, and each event can be associated with a reporting duration, in seconds, indicating the maximum duration for triggering the report.

[0176] In one or more implementations, various reporting configurations can be sent by a configuration entity (e.g., LMF) to a serving or neighboring gNB / TRP to enable different methods of reporting UL carrier phase measurements. These reporting methods also include any location information derived only based on carrier phase measurements or jointly based on other UL positioning measurements (e.g., UL-RTOA, UL-AoA, gNB Rx-Tx time difference measurement, etc.).

[0177] Figure 9 Illustrated is an example of UL carrier phase measurement request and response report messaging 900 related to carrier phase positioning reporting according to aspects of the present disclosure. Messaging 900 is request and response signaling between a configuration entity and a target UE for exchanging UL carrier phase-related reported measurements. As Figure 9 shown, the UL carrier phase measurement request and response report messaging can be signaled using NRPPa for UL carrier phase measurements (e.g., using NRPPa MeasurementRequest and / or NRPPa MeasurementResponse messages).

[0178] As Figure 9 shown, the steps for requesting and reporting UL carrier phase measurements are described below.

[0179] At 902, UE 104 transmits multiple SRSs for positioning signals to measure the UL carrier phase. This can be based on single-carrier transmission or multi-carrier transmission (if configured).

[0180] At 904, the serving gNB or TRP 906 performs UL carrier phase measurements based on the provided SRS configuration. In other implementations, MIMO of the SRS can also be used for UL carrier phase measurements at 902 and 904.

[0181] At 908, the LMF 910 can request multiple gNB / TRPs 906 to provide multiple carrier phase measurements via a list or index. The reporting can be performed in a one-shot, periodic, or event-triggered manner. The request can also include parameters related to the gNB / TRP beam information of the requested carrier phase measurements, the reporting granularity or step value of the carrier phase in radians or degrees, the number of error types (if known to the gNB / TRP), including receiver initial phase offset, gNB ARP position error, oscillator drift or clock offset, carrier frequency offset, antenna phase offset, or a combination thereof.

[0182] At 912, multiple gNB / TRPs can respond with UL carrier phase measurement results, which include additional parameters such as UL carrier phase measurement quality, e.g., a single quality metric, confidence interval. In the case of unavailability or error during UL carrier phase measurement, the gNB / TRP can respond with a measurement failure of the UL carrier phase measurement.

[0183] In one or more implementations, carrier phase capability exchange is supported. Any one of the entities / nodes (e.g., LMF, anchor / PRU UE, SL positioning server UE, and target UE) can exchange capability-related messages to perform DL or SL carrier phase measurements. Based on the UE type, this capability can be dynamic or static. These capability-related messages can be, for example, capability request and response messages.

[0184] Figure 10 An example of a DL or SL carrier phase capability exchange message 1000 related to carrier phase positioning reporting according to aspects of the present disclosure is illustrated. Message 1000 is a request and response signaling for exchanging carrier phase-related capability messages between a configuration entity and a target UE 1002. The configuration entity can be at least one of an SL positioning server UE 1004, an anchor UE or PRU 1006, and an LMF 1008. According to Figure 10For the message passing shown, the carrier phase capability request and response reporting message passing can use LPP for DL carrier phase measurement, such as using LPP RequestCapabilityInformation and / or LPP ProvideCapabilityInformation messages, or use SLPP (SL positioning protocol) for SL carrier phase measurement, such as using SLPP RequestCapabilityInformation and / or SLPP ProvideCapabilityInformation messages. On SL, such capability messages can be sent using security mechanisms via unicast, multicast, or broadcast messages. Security can include integrity and cipher protection.

[0185] According to message 1000, the message passing for requesting and reporting SL or DL carrier phase measurement is as follows. Any one of the entities or nodes (e.g., LMF 1008, anchor or PRU UE 1006, SL positioning server UE 1004) can request the target UE 1002 to provide multiple carrier phase capabilities. The target UE 1002 can physically respond to any one of the entities / nodes (e.g., LMF 1008, anchor or PRU UE 1006, SL positioning server UE 1004) with one set of carrier phase capabilities or multiple sets of carrier phase capabilities.

[0186] In one or more implementations, carrier phase error causes are supported. The target UE or the configuration entity can provide DL or SL carrier phase positioning error causes. The error causes related to carrier phase positioning can vary depending on the source and type of the error.

[0187] Figure 11 Illustrated is an example IE message 1100 related to carrier phase positioning reporting according to aspects of the present disclosure. The IE message 1100 shows the error causes supported by the configuration entity, which can be conveyed via LPP. The IE message 1100 is an example of an NR-DL-CP-LocationServerErrorCauses message, which is used by the location server to provide the NR DL carrier phase measurement error causes to the target device. The same applies to the SL configuration entity providing such error causes to the target UE / device.

[0188] Figure 12FIG. illustrates an example IE message 1200 related to carrier phase positioning reporting according to aspects of the present disclosure. IE message 1200 shows the error causes supported by the target UE, which can be communicated via LPP. IE message 1200 is an example of an NR-DL-CP-TargetDeviceErrorCauses message, which is used by the target UE to provide NR DL carrier phase measurement error causes to the location server. The same applies to the SL target UE / device providing the above error causes to the SL configuration entity.

[0189] Accordingly, the techniques discussed herein provide a set of solutions for supporting the reporting of carrier phase measurements through appropriate reporting configurations. One aspect of the solution relates to the efficient reporting of DL, SL, and UL carrier phase measurements, including reporting error types, including phase offset, ARP position error, oscillator drift or clock offset, CFO, and antenna phase center offset. Another aspect of the solution relates to the process for exchanging capability messages and error causes related to both DL and SL carrier phase measurements.

[0190] Figure 13 FIG. illustrates an example of a block diagram 1300 of a device 1302 that supports carrier phase positioning reporting according to aspects of the present disclosure. Device 1302 may be an example of UE 104 as described herein. Device 1302 may support wireless communication with one or more network entities 102, UE 104, or any combination thereof. Device 1302 may include components for two-way communication, including components for sending and receiving communications (such as a processor 1304, a memory 1306, a transceiver 1308, and an I / O controller 1310). These components may communicate electronically or otherwise be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., a bus).

[0191] Processor 1304, memory 1306, transceiver 1308, or various combinations or various components thereof may be examples of components for performing various aspects of the present disclosure described herein. For example, processor 1304, memory 1306, transceiver 1308, or various combinations or components thereof may support methods for performing one or more of the operations described herein.

[0192] In some implementations, processor 1304, memory 1306, transceiver 1308, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). 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 thereof, configured or otherwise supporting components for performing the functions described in this disclosure. In some implementations, processor 1304 and memory 1306 coupled to processor 1304 may be configured to perform one or more functions described herein (e.g., by processor 1304 executing instructions stored in memory 1306).

[0193] For example, according to an example disclosed herein, processor 1304 may support wireless communication at device 1302. Processor 1304 may be configured or otherwise support: receiving, from a configuration entity, first signaling indicating a carrier phase positioning report configuration, where the carrier phase positioning report configuration includes at least a set of receiver error types and a carrier phase granularity; generating, based on the received report configuration, a plurality of carrier phase measurement reports including a plurality of carrier phase positioning measurements; sending, to the configuration entity, a plurality of second signaling indicating the plurality of carrier phase measurement reports.

[0194] For example, according to an example disclosed herein, processor 1304 may support wireless communication at device 1302. Processor 1304 may be configured or otherwise support: receiving, from a configuration entity, first signaling indicating a carrier phase positioning report configuration, where the carrier phase positioning report configuration includes at least a carrier phase granularity; generating, based on the received report configuration, a plurality of carrier phase measurement reports including a plurality of carrier phase positioning measurements; sending, to the configuration entity, a plurality of second signaling indicating the plurality of carrier phase measurement reports.

[0195] Additionally or alternatively, the processor 1304 may be configured to or otherwise support: wherein the carrier phase reporting configuration further includes: a request to provide additional RAT-related positioning measurements, the request for the additional RAT-related positioning measurements including at least one of DL-RSTD, UE Rx-Tx time difference, DL PRS RSRP, DL PRS RSRPP, SL-RSTD, SL-RTOA, SL PRS RSRP, SL PRS RSRPP, or SL-AoA; wherein the carrier phase positioning reporting configuration includes a set of receiver error types, the set of receiver error types including at least one of the following: initial phase offset, initial phase offset group, UE antenna reference point position error, oscillator drift or clock offset, carrier frequency offset, and antenna phase center offset; wherein each error type in the set of error types is associated with an identifier; wherein the carrier phase positioning measurements are reported in a carrier phase measurement report in the form of multiple single-carrier phase measurements per TRP or in the form of multiple reference signal carrier phase difference measurements per pair of TRPs; wherein the carrier phase positioning measurements are reported in the carrier phase measurement report based on a defined granularity or step value expressed in radians or degrees; wherein the carrier phase positioning measurements are reported in the carrier phase measurement report based on a defined quality metric; wherein incremental or differential carrier phase measurements relative to previously performed carrier phase positioning measurements and current carrier phase measurements are reported in the carrier phase measurement report; wherein the processor is further configured to cause the device to: send to a configuration entity a device error cause related to carrier phase positioning; wherein the processor is further configured to cause the device to receive a configuration entity error cause related to carrier phase positioning; wherein the processor is further configured to cause the device to support sensing of devices capable of supporting carrier phase measurements via capability request and response messages; wherein the device includes a UE; wherein the processor is further configured to cause the device to: in the case of UE-based positioning, send a request for PRU carrier phase measurements and / or associated information and receive a response to the PRU carrier phase measurements and / or associated information; wherein the associated information includes at least one of the following: PRU cycle ambiguity information and quality metric PRS resource ID, PRS resource set ID, TRP ID, PRU identification information, PRU ID, LOS / NLOS information related to each carrier phase positioning measurement in the carrier phase positioning measurements, additional path information related to each carrier phase positioning measurement in the carrier phase positioning measurements, PRU receiver error type information including any oscillator drift, clock drift, initial PRU phase offset, or phase offset group, PRU ARP position error, PRU phase center offset, PRU measurement timestamp information, or carrier phase or timing measurement quality metric.

[0196] For example, according to the examples disclosed herein, the processor 1304 may support wireless communication at the device 1302. The processor 1304 may be configured to or otherwise support components for: receiving a first signaling from a configuration entity indicating a carrier phase positioning report configuration, where the carrier phase positioning report configuration includes at least a set of receiver error types and a carrier phase granularity; generating, based on the received report configuration, a plurality of carrier phase measurement reports including a plurality of carrier phase positioning measurements; and sending a plurality of second signaling to the configuration entity indicating the plurality of carrier phase measurement reports.

[0197] For example, according to the examples disclosed herein, the processor 1304 may support wireless communication at the device 1302. The processor 1304 may be configured to or otherwise support components for: receiving a first signaling from a configuration entity indicating a carrier phase positioning report configuration, where the carrier phase positioning report configuration includes at least a carrier phase granularity; generating, based on the received report configuration, a plurality of carrier phase measurement reports including a plurality of carrier phase positioning measurements; and sending a plurality of second signaling to the configuration entity indicating the plurality of carrier phase measurement reports.

[0198] Additionally or alternatively, the processor 1304 may be configured to or otherwise support: where the carrier phase reporting configuration further includes: a request to provide additional RAT-related positioning measurements, the request for the additional RAT-related positioning measurements including at least one of the following: DL-RSTD, UE Rx-Tx time difference, DL PRS RSRP, DL PRS RSRPP, SL-RSTD, SL-RTOA, SL PRS RSRP, SL PRS RSRPP, or SL-AoA; where the carrier phase positioning reporting configuration includes a set of receiver error types, the set of receiver error types including at least one of the following: initial phase offset, initial phase offset group, UE antenna reference point position error, oscillator drift or clock offset, carrier frequency offset, and antenna phase center offset; where each error type in the set of error types is associated with an identifier; where the carrier phase positioning measurements are reported in a carrier phase measurement report in the form of multiple single-carrier phase measurements per TRP or in the form of multiple reference signal carrier phase difference measurements per pair of TRPs; where the carrier phase positioning measurements are reported in the carrier phase measurement report based on a defined granularity or step value expressed in radians or degrees; where the carrier phase positioning measurements are reported in the carrier phase measurement report based on a defined quality metric; where incremental or differential carrier phase measurements relative to previously performed carrier phase positioning measurements and current carrier phase measurements are reported in the carrier phase measurement report; further including: sending a device error reason related to carrier phase positioning to a configuration entity; further including: receiving a configuration entity error reason related to carrier phase positioning; further including: supporting the sensing of devices capable of supporting carrier phase measurements via capability request and response messages; where the method is implemented in a user equipment; further including: sending a request for PRU carrier phase measurements and / or associated information and receiving a response to the PRU carrier phase measurements and / or associated information in the case of UE-based positioning; where the associated information includes at least one of the following: PRU integer ambiguity information and quality metric PRS resource ID, PRS resource set ID, TRPID, PRU identification information, PRUID, LOS / NLOS information related to each carrier phase positioning measurement in the carrier phase positioning measurements, additional path information related to each carrier phase positioning measurement in the carrier phase positioning measurements, PRU receiver error type information including any oscillator drift, clock drift, initial PRU phase offset, or phase offset group, PRU ARP position error, PRU phase center offset, PRU measurement timestamp information, or carrier phase or timing measurement quality metric.

[0199] According to the examples disclosed herein, a processor 1304 of a device 1302 (e.g., UE 104) may support wireless communication. The processor 1304 includes at least one controller that is coupled to at least one memory and is configured or operable to cause the processor: to receive a first signaling from a configuration entity indicating a carrier phase positioning report configuration, where the carrier phase positioning report configuration includes at least a set of receiver error types and a carrier phase granularity; to generate, based on the received report configuration, a plurality of carrier phase measurement reports including a plurality of carrier phase positioning measurements; to send a plurality of second signaling to the configuration entity indicating the plurality of carrier phase measurement reports.

[0200] According to the examples disclosed herein, a processor 1304 of a device 1302 (e.g., UE 104) may support wireless communication. The processor 1304 includes at least one controller that is coupled to at least one memory and is configured or operable to cause the processor: to receive a first signaling from a configuration entity indicating a carrier phase positioning report configuration, where the carrier phase positioning report configuration includes at least a carrier phase granularity; to generate, based on the received report configuration, a plurality of carrier phase measurement reports including a plurality of carrier phase positioning measurements; to send a plurality of second signaling to the configuration entity indicating the plurality of carrier phase measurement reports.

[0201] The processor 1304 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some implementations, the processor 1304 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 1304. The processor 1304 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1306) to cause the device 1302 to perform various functions of the present disclosure.

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

[0203] The I / O controller 1310 may manage the input and output signals of the device 1302. The I / O controller 1310 may also manage peripheral devices not integrated into the device 1302. In some implementations, the I / O controller 1310 may represent a physical connection or port to an external peripheral device. In some implementations, the I / O controller 1310 may utilize an operating system, such as MS- MS OS / or other known operating systems. In some implementations, the I / O controller 1310 may be implemented as part of a processor, such as the processor 1304. In some implementations, a user may interact with the device 1302 via the I / O controller 1310 or via hardware components controlled by the I / O controller 1310.

[0204] In some implementations, the device 1302 may include a single antenna 1312. However, in some other implementations, the device 1302 may have more than one antenna 1312 (i.e., multiple antennas), including multiple antenna panels or antenna arrays, which are capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 1308 may communicate bidirectionally via one or more antennas 1312, wired or wireless links, as described herein. For example, the transceiver 1308 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1308 may also include a modem that modulates packets, provides the modulated packets to one or more antennas 1312 for transmission, and demodulates packets received from one or more antennas 1312.

[0205] Figure 14 FIG. 1400 is an example of a block diagram of a device 1402 supporting carrier phase positioning reporting in accordance with aspects of the present disclosure. The device 1402 may be an example of the network entity 102 (e.g., a configuration entity or an LMF) described herein. The device 1402 may support wireless communication with one or more network entities 102, UEs 104, or any combination thereof. The device 1402 may include components for bidirectional communication, including components for transmitting and receiving communications (such as a processor 1404, a memory 1406, a transceiver 1408, and an I / O controller 1410). These components may communicate electronically or otherwise be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., a bus).

[0206] Processor 1404, memory 1406, transceiver 1408, or various combinations or various components thereof can be examples of components for performing various aspects of the present disclosure described herein. For example, processor 1404, memory 1406, transceiver 1408, or various combinations or components thereof can support methods for performing one or more of the operations described herein.

[0207] In some implementations, processor 1404, memory 1406, transceiver 1408, or various combinations or components thereof can be implemented in hardware (e.g., in communication management circuitry). The hardware can 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 thereof, configured to or otherwise supporting components for performing the functions described in the present disclosure. In some implementations, processor 1404 and memory 1406 coupled to processor 1404 can be configured to perform one or more of the functions described herein (e.g., by processor 1404 executing instructions stored in memory 1406).

[0208] For example, according to the examples disclosed herein, processor 1404 can support wireless communication at device 1402. Processor 1404 can be configured to or otherwise support: receiving, from a UE, a first signaling indicating a carrier phase measurement report according to a carrier phase positioning report configuration, where the carrier phase positioning report configuration includes at least a set of receiver error types and a carrier phase granularity, and where the carrier phase measurement report includes at least one carrier phase positioning measurement; and obtaining location information of the UE based on the carrier phase measurement report.

[0209] For example, according to the examples disclosed herein, processor 1404 can support wireless communication at device 1402. Processor 1404 can be configured to or otherwise support: receiving, from a UE, a first signaling indicating a carrier phase measurement report according to a carrier phase positioning report configuration, where the carrier phase positioning report configuration includes at least a carrier phase granularity, and where the carrier phase measurement report includes at least one carrier phase positioning measurement; and obtaining location information of the UE based on the carrier phase measurement report.

[0210] Additionally or alternatively, processor 1404 may be configured to or otherwise support: where the device includes a network entity, and the processor is further configured to cause the device to: send a carrier phase reporting configuration to the UE; where the device includes a network entity, and the processor is further configured to cause the device to: send a carrier phase measurement request for reporting uplink carrier phase measurements to the UE, the carrier phase measurement request including the carrier phase reporting configuration; where the carrier phase reporting configuration further includes a request for providing additional RAT-related positioning measurements, the request for additional RAT-related positioning measurements including at least one of the following: DL-RSTD, UE Rx-Tx time difference, DL PRS RSRP, DL PRS RSRPP, SL-RSTD, SL-RTOA, SL PRS RSRP, SL PRS RSRPP, or SL-AoA; where the carrier phase positioning reporting configuration includes a set of receiver error types, the set of receiver error types including at least one of the following: initial phase offset, initial phase offset group, UE antenna reference point position error, oscillator drift or clock offset, carrier frequency offset, and antenna phase center offset; where each error type in the set of error types is associated with an identifier; where at least one carrier phase positioning measurement is reported in a carrier phase measurement report in the form of multiple single-carrier phase measurements per TRP or in the form of multiple reference signal carrier phase difference measurements per pair of TRPs; where at least one carrier phase positioning measurement is reported in a carrier phase measurement report based on a defined granularity or step value expressed in radians or degrees; where at least one carrier phase positioning measurement is reported in a carrier phase measurement report based on a defined quality metric; where incremental or differential carrier phase measurements relative to previously performed carrier phase positioning measurements and current carrier phase measurements are reported in a carrier phase measurement report; where the processor is further configured to cause the device to receive from the UE a UE error cause related to carrier phase positioning; where the device includes a configuration entity, and where the processor is further configured to cause the device to: send a configuration entity error cause related to carrier phase positioning to the UE; where the processor is further configured to cause the device to: support sensing of devices capable of supporting carrier phase measurements via capability request and response messages; where the processor is further configured to cause the device to: in the case of UE-based positioning, receive a request for PRU carrier phase measurements and / or associated information and send a response with the PRU carrier phase measurements and / or associated information to the UE;The associated information includes at least one of the following items: PRU integer ambiguity information and quality metric, PRS resource ID, PRS resource set ID, TRPID, PRU identification information, PRUID, LOS / NLOS information related to each carrier phase positioning measurement in the carrier phase positioning measurement, additional path information related to each carrier phase positioning measurement in the carrier phase positioning measurement, PRU receiver error type information including any oscillator drift, clock drift, initial PRU phase offset, or phase offset group, PRU ARP position error, PRU phase center offset, PRU measurement timestamp information, or carrier phase or timing measurement quality metric.;

[0211] For example, according to the examples disclosed herein, the processor 1404 may support wireless communication at the device 1402. The processor 1404 may be configured to or otherwise support components for: receiving, from a UE, a first signaling indicating a carrier phase measurement report according to a carrier phase positioning report configuration, where the carrier phase positioning report configuration includes at least a set of receiver error types and a carrier phase granularity, and where the carrier phase measurement report includes at least one carrier phase positioning measurement; and obtaining location information of the UE based on the carrier phase measurement report.

[0212] For example, according to the examples disclosed herein, the processor 1404 may support wireless communication at the device 1402. The processor 1404 may be configured to or otherwise support components for: receiving, from a UE, a first signaling indicating a carrier phase measurement report according to a carrier phase positioning report configuration, where the carrier phase positioning report configuration includes at least a carrier phase granularity, and where the carrier phase measurement report includes at least one carrier phase positioning measurement; and obtaining location information of the UE based on the carrier phase measurement report.

[0213] Additionally or alternatively, the processor 1404 may be configured to or otherwise support: where the method is implemented in a network entity, and the method further includes: sending a carrier phase reporting configuration to the UE; where the method is implemented in a network entity, the method further includes: sending a carrier phase measurement request for reporting uplink carrier phase measurements to the UE, the carrier phase measurement request including the carrier phase reporting configuration; where the carrier phase reporting configuration further includes a request for providing additional RAT-related positioning measurements, the request for the additional RAT-related positioning measurements including at least one of the following: DL-RSTD, UE Rx-Tx time difference, DL PRS RSRP, DL PRS RSRPP, SL-RSTD, SL-RTOA, SL PRS RSRP, SL PRS RSRPP, or SL-AoA; where the carrier phase positioning reporting configuration includes a set of receiver error types, the set of receiver error types including at least one of the following: initial phase offset, initial phase offset group, UE antenna reference point position error, oscillator drift or clock offset, carrier frequency offset, and antenna phase center offset; where each of the error types is associated with an identifier; where at least one carrier phase positioning measurement is reported in a carrier phase measurement report in the form of multiple single-carrier phase measurements per TRP or in the form of multiple reference signal carrier phase difference measurements per pair of TRPs; where at least one carrier phase positioning measurement is reported in a carrier phase measurement report based on a defined granularity or step value expressed in radians or degrees; where at least one carrier phase positioning measurement is reported in a carrier phase measurement report based on a defined quality metric; where an incremental or differential carrier phase measurement with respect to a previously performed carrier phase positioning measurement and a current carrier phase measurement is reported in a carrier phase measurement report; receiving from the UE a UE error cause related to carrier phase positioning; sending to the UE a configuration entity error cause related to carrier phase positioning; supporting awareness of devices capable of supporting carrier phase measurements via capability request and response messages; receiving a request for PRU carrier phase measurements and / or associated information in the case of UE-based positioning and sending a response to the UE with the PRU carrier phase measurements and / or associated information; where the associated information includes at least one of the following: PRU integer ambiguity information and quality metric PRS resource ID, PRS resource set ID, TRP ID, PRU identification information, PRU ID, LOS / NLOS information related to each carrier phase positioning measurement in the carrier phase positioning measurements, additional path information related to each carrier phase positioning measurement in the carrier phase positioning measurements, PRU receiver error type information including any oscillator drift, clock drift, initial PRU phase offset, or phase offset group, PRU ARP position error, PRU phase center offset, PRU measurement timestamp information, or carrier phase or timing measurement quality metric.

[0214] The processor 1404 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some implementations, the processor 1404 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 1404. The processor 1404 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 1406) to cause the device 1402 to perform the various functions of the present disclosure.

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

[0216] The I / O controller 1410 may manage the input and output signals of the device 1402. The I / O controller 1410 may also manage peripheral devices not integrated into the device 1402. In some implementations, the I / O controller 1410 may represent a physical connection or port to an external peripheral device. In some implementations, the I / O controller 1410 may utilize an operating system, such as MS- MS OS / or other known operating systems. In some implementations, the I / O controller 1410 may be implemented as part of a processor such as the processor 1404. In some implementations, a user may interact with the device 1402 via the I / O controller 1410 or via hardware components controlled by the I / O controller 1410.

[0217] In some implementations, device 1402 may include a single antenna 1412. However, in some other implementations, device 1402 may have more than one antenna 1412 (i.e., multiple antennas), including multiple antenna panels or antenna arrays, which are capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 1408 may communicate bidirectionally via one or more antennas 1412, wired or wireless links, as described herein. For example, transceiver 1408 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 1408 may also include a modem that is configured to modulate packets, provide the modulated packets to one or more antennas 1412 for transmission, and demodulate packets received from one or more antennas 1412.

[0218] Figure 15 FIG. illustrates a flow diagram of a method 1500 for supporting carrier phase positioning reporting in accordance with aspects of the present disclosure. Operations of method 1500 may be implemented by a device or components thereof described herein. For example, operations of method 1500 may be performed by UE 104 as referenced Figures 1 to 14 above. 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.

[0219] At 1505, the method may include: receiving, from a configuration entity, first signaling indicating a carrier phase positioning reporting configuration, wherein the carrier phase positioning reporting configuration includes at least a carrier phase granularity. The operation of 1505 may be performed in accordance with examples described herein. In some implementations, aspects of the operation of 1505 may be performed by a device as referenced Figure 1 above.

[0220] At 1510, the method may include: generating, based on the received reporting configuration, multiple carrier phase measurement reports including a plurality of carrier phase positioning measurements. The operation of 1510 may be performed in accordance with examples described herein. In some implementations, aspects of the operation of 1510 may be performed by a device as referenced Figure 1 above.

[0221] At 1515, the method may include: sending, to the configuration entity, multiple second signaling indicating the multiple carrier phase measurement reports. The operation of 1515 may be performed in accordance with examples described herein. In some implementations, aspects of the operation of 1515 may be performed by a device as referenced Figure 1 above.

[0222] Figure 16The figure illustrates a flowchart of a method 1600 for supporting carrier phase positioning reporting in accordance with aspects of the present disclosure. Operations of method 1600 may be implemented by the devices or components described herein. For example, operations of method 1600 may be performed by the UE 104 referenced Figures 1 to 14 as described. 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.

[0223] At 1605, the method may include sending a device error cause related to carrier phase positioning to a configuration entity. The operation of 1605 may be performed in accordance with the examples described herein. In some implementations, aspects of the operation of 1605 may be performed by the device referenced Figure 1 as described.

[0224] Figure 17 The figure illustrates a flowchart of a method 1700 for supporting carrier phase positioning reporting in accordance with aspects of the present disclosure. Operations of method 1700 may be implemented by the devices or components described herein. For example, operations of method 1700 may be performed by the UE 104 referenced Figures 1 to 14 as described. 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.

[0225] At 1705, the method may include receiving a configuration entity error cause related to carrier phase positioning. The operation of 1705 may be performed in accordance with the examples described herein. In some implementations, aspects of the operation of 1705 may be performed by the device referenced Figure 1 as described.

[0226] Figure 18 The figure illustrates a flowchart of a method 1800 for supporting carrier phase positioning reporting in accordance with aspects of the present disclosure. Operations of method 1800 may be implemented by the devices or components described herein. For example, operations of method 1800 may be performed by the UE 104 referenced Figures 1 to 14 as described. 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.

[0227] At 1805, the method may include supporting awareness of devices capable of supporting carrier phase measurements via a capability request and response message. The operation of 1805 may be performed in accordance with the examples described herein. In some implementations, aspects of the operation of 1805 may be performed by the device referenced Figure 1executed by the described device.

[0228] Figure 19 FIG. 1900 is a flow chart of a method 1900 that supports carrier phase positioning reporting in accordance with aspects of the present disclosure. Operations of method 1900 may be implemented by a device or components thereof described herein. For example, operations of method 1900 may be performed by the network entity 102 referenced Figures 1 to 14 above. 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.

[0229] At 1905, the method may include: receiving, from a UE, a first signaling indicating a carrier phase measurement report according to a carrier phase positioning report configuration, where the carrier phase positioning report configuration includes at least a carrier phase granularity, and where the carrier phase measurement report includes at least one carrier phase positioning measurement. The operation of 1905 may be performed according to the examples described herein. In some implementations, aspects of the operation of 1905 may be performed by the device referenced Figure 1 above.

[0230] At 1910, the method may include: obtaining location information of the UE based on the carrier phase measurement report. The operation of 1910 may be performed according to the examples described herein. In some implementations, aspects of the operation of 1910 may be performed by the device referenced Figure 1 above.

[0231] Figure 20 FIG. 2000 is a flow chart of a method 2000 that supports carrier phase positioning reporting in accordance with aspects of the present disclosure. Operations of method 2000 may be implemented by a device or components thereof described herein. For example, operations of method 2000 may be performed by the network entity 102 referenced Figures 1 to 14 above. 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.

[0232] At 2005, the method may include the apparatus includes a network entity. The operation of 2005 may be performed according to the examples described herein. In some implementations, aspects of the operation of 2005 may be performed by the device referenced Figure 1 above.

[0233] At 2010, the method may include: sending a carrier phase report configuration to the UE. The operation of 2010 may be performed according to the examples described herein. In some implementations, aspects of the operation of 2010 may be performed by the device referenced Figure 1executed by the described device.

[0234] Figure 21 FIG. illustrates a flowchart of a method 2100 for supporting carrier phase positioning reports in accordance with aspects of the present disclosure. Operations of method 2100 may be implemented by the devices or components thereof described herein. For example, the operations of method 2100 may be performed by the network entity 102 referred to Figures 1 to 14 in the description. In some implementations, the device may execute an instruction set 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.

[0235] At 2105, the method may include the apparatus including a network entity. The operations of 2105 may be performed in accordance with the examples described herein. In some implementations, aspects of the operations of 2105 may be performed by the device referred to Figure 1 in the description.

[0236] At 2110, the method may include: sending a carrier phase measurement request for reporting uplink carrier phase measurements to a UE, the carrier phase measurement request including a carrier phase reporting configuration. The operations of 2110 may be performed in accordance with the examples described herein. In some implementations, aspects of the operations of 2110 may be performed by the device referred to Figure 1 in the description.

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

[0238] The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed with a general purpose processor, DSP, ASIC, CPU, 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. The general purpose processor may be a microprocessor, but in the 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 DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0239] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions can be stored on or transmitted via a computer-readable medium as one or more instructions or code. Other examples and implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. The features implementing the functions can also be physically located in various places, including being distributed such that portions of the functions are implemented at different physical locations.

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

[0241] Any connection is properly termed a computer-readable medium. For example, if software is transmitted 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, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology such as infrared, radio, and microwave are included in the definition of computer-readable medium. As used herein, disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc where disks typically reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

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

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

[0244] The description provided herein in conjunction with the figures describes example configurations and does not represent all examples that can be implemented or that are within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration" and not "preferred" or "superior to 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 instances, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0245] The description provided herein is to enable a person of ordinary skill in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to a person of ordinary skill in the art, and the general principles defined herein can be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but should be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE) for wireless communication, comprising: At least one memory; And At least one processor, coupled to the at least one memory and configured to cause the UE to: Receive first signaling from a configuration entity indicating a carrier phase positioning report configuration, wherein the carrier phase positioning report configuration includes at least a carrier phase granularity; Generate, based on the received report configuration, a plurality of carrier phase measurement reports including a plurality of carrier phase positioning measurements; Send a plurality of second signaling to the configuration entity indicating the plurality of carrier phase measurement reports.

2. The UE according to claim 1, wherein the carrier phase reporting configuration further comprises: A request for providing additional radio access technology (RAT)-related positioning measurements, the additional RAT-related positioning measurements including at least one of the following: downlink reference signal time difference (DL-RSTD), user equipment receive transmit (UE Rx-Tx) time difference, downlink positioning reference signal reference signal received power (DL PRS RSRP), downlink positioning reference signal reference signal received path power (DL PRS RSRPP), sidelink reference signal time difference (SL-RSTD), sidelink relative time of arrival (SL-RTOA), sidelink positioning reference signal reference signal received power (SL PRS RSRP), sidelink positioning reference signal reference signal received path power (SL PRS RSRPP), or sidelink angle of arrival (SL-AoA).

3. The UE according to claim 1, wherein the carrier phase positioning report configuration includes: A set of receiver error types, the set of receiver error types including at least one of the following: initial phase offset, initial phase offset group, UE antenna reference point position error, oscillator drift or clock offset, carrier frequency offset, or antenna phase center offset.

4. The UE according to claim 3, wherein each of the error types is associated with an identifier.

5. The UE according to claim 1, wherein the carrier phase positioning measurements are reported in the carrier phase measurement report in the form of a plurality of single carrier phase measurements per transmission reception point (TRP) or in the form of a plurality of reference signal carrier phase difference measurements per pair of TRPs.

6. The UE according to claim 1, wherein the carrier phase positioning measurements are reported in the carrier phase measurement report based on a defined granularity or step value expressed in radians or degrees.

7. The UE according to claim 1, wherein the carrier phase positioning measurements are reported in the carrier phase measurement report based on a defined quality metric.

8. The UE according to claim 1, wherein incremental or differential carrier phase measurements relative to previously performed carrier phase positioning measurements and current carrier phase measurements are reported in the carrier phase measurement report.

9. The UE according to claim 1, wherein the processor is further configured to cause the UE to: send to the configuration entity a cause of device error related to carrier phase positioning.

10. The UE according to claim 1, wherein the processor is further configured to cause the UE to: receive a cause of configuration entity error related to carrier phase positioning.

11. The UE according to claim 1, wherein the processor is further configured to cause the UE to: support sensing of devices capable of supporting carrier phase measurements via capability request and response messages.

12. The UE according to claim 1, wherein the processor is further configured to cause the UE to: in the case of UE-based positioning, send a request for positioning reference unit (PRU) carrier phase measurements and / or associated information, and receive a response to the PRU carrier phase measurements and / or associated information.

13. The UE according to claim 12, wherein the associated information includes at least one of the following: PRU integer ambiguity information and quality metric positioning reference signal (PRS) resource identifier (ID), PRS resource set ID, transmission reception point (TRP) ID, PRU identification information, PRU ID, line-of-sight (LOS) / non-line-of-sight (NLOS) information associated with each carrier phase positioning measurement in the carrier phase positioning measurement, additional path information associated with each carrier phase positioning measurement in the carrier phase positioning measurement, PRU receiver error type information including any oscillator drift, clock drift, initial PRU phase offset, or phase offset group, PRU antenna reference point (ARP) position error, PRU phase center offset, PRU measurement timestamp information, or carrier phase or timing measurement quality metric.

14. A base station for wireless communication, comprising: at least one memory; and at least one processor, coupled to the at least one memory and configured to cause the base station to: receive first signaling indicating a carrier phase measurement report from a user equipment (UE) according to a carrier phase positioning report configuration, wherein the carrier phase positioning report configuration includes at least a carrier phase granularity, and wherein the carrier phase measurement report includes at least one carrier phase positioning measurement; acquire position information of the UE based on the carrier phase measurement report.

15. A method performed by a user equipment (UE), the method comprising: receiving first signaling indicating a carrier phase positioning report configuration from a configuration entity, wherein the carrier phase positioning report configuration includes at least a carrier phase granularity; generating a plurality of carrier phase measurement reports including a plurality of carrier phase positioning measurements based on the received report configuration; and sending a plurality of second signaling indicating the plurality of carrier phase measurement reports to the configuration entity.

16. A processor for wireless communication, comprising: at least one controller, coupled to at least one memory and configured to cause the processor to: receive first signaling indicating a carrier phase positioning report configuration from a configuration entity, wherein the carrier phase positioning report configuration includes at least a carrier phase granularity; generate a plurality of carrier phase measurement reports including a plurality of carrier phase positioning measurements based on the received report configuration; send a plurality of second signaling indicating the plurality of carrier phase measurement reports to the configuration entity.

17. The processor according to claim 16, wherein the carrier phase reporting configuration further comprises: Request for additional radio access technology (RAT)-related positioning measurements, the additional RAT-related positioning measurements including at least one of the following: downlink reference signal time difference (DL-RSTD), user equipment receive transmit (UE Rx-Tx) time difference, downlink positioning reference signal reference signal received power (DL PRS RSRP), downlink positioning reference signal reference signal received path power (DL PRS RSRPP), sidelink reference signal time difference (SL-RSTD), sidelink relative time of arrival (SL-RTOA), sidelink positioning reference signal reference signal received power (SL PRS RSRP), sidelink positioning reference signal reference signal received path power (SL PRS RSRPP), and sidelink angle of arrival (SL-AoA).

18. The processor according to claim 16, wherein the carrier phase positioning report configuration comprises: Set of receiver error types, the set of receiver error types including at least one of the following: initial phase offset, initial phase offset group, user equipment (UE) antenna reference point position error, oscillator drift or clock offset, carrier frequency offset, or antenna phase center offset.

19. The processor according to claim 16, wherein the carrier phase positioning measurements are reported in the carrier phase measurement report in the form of multiple single-carrier phase measurements per transmit receive point (TRP) or in the form of multiple reference signal carrier phase difference measurements per pair of TRPs.

20. The processor according to claim 16, wherein the carrier phase positioning measurements are reported in the carrier phase measurement report based on a defined granularity or step value expressed in radians or degrees.

Images