EQUIPHASE CONTOUR INFORMATION ASSOCIATED WITH ANTENNA OF WIRELESS NODE

BACKGROUND OF THE DISCLOSURE

1. Field of the Disclosure

[0001] Aspects of the disclosure relate generally to wireless communications.

2. Description of the Related Art

[0002] Wireless communication systems have developed through various generations, including a first-generation analog wireless phone service (1G), a second-generation (2G) digital wireless phone service (including interim 2.5G and 2.75G networks), a third-generation (3G) high speed data, Internet-capable wireless service and a fourth-generation (4G) service (e.g., Long Term Evolution (LTE) or WiMax). There are presently many different types of wireless communication systems in use, including cellular and personal communications service (PCS) systems. Examples of known cellular systems include the cellular analog advanced mobile phone system (AMPS), and digital cellular systems based on code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), the Global System for Mobile communications (GSM), etc.

[0003] A fifth generation (5G) wireless standard, referred to as New Radio (NR), enables higher data transfer speeds, greater numbers of connections, and better coverage, among other improvements. The 5G standard, according to the Next Generation Mobile Networks Alliance, is designed to provide higher data rates as compared to previous standards, more accurate positioning (e.g., based on reference signals for positioning (RS-P), such as downlink, uplink, or sidelink positioning reference signals (PRS)), and other technical enhancements. These enhancements, as well as the use of higher frequency bands, advances in PRS processes and technology, and high-density deployments for 5G, enable highly accurate 5G-based positioning. SUMMARY

[0004] The following presents a simplified summary relating to one or more aspects disclosed herein. Thus, the following summary should not be considered an extensive overview relating to all contemplated aspects, nor should the following summary be considered to identify key or critical elements relating to all contemplated aspects or to delineate the scope associated with any particular aspect. Accordingly, the following summary has the sole purpose to present certain concepts relating to one or more aspects relating to the mechanisms disclosed herein in a simplified form to precede the detailed description presented below.

[0005] In an aspect, a method of operating a first node includes determining equiphase contour information associated with an antenna of the first node at one or more carrier frequencies; and transmitting an indication of the equiphase contour information to a second node.

[0006] In an aspect, a method of operating a device includes determining equiphase contour information associated with an antenna of a first node at one or more carrier frequencies; and correcting measurement information associated with a carrier phase-based position estimation session based at least in part on the equiphase contour information.

[0007] In an aspect, a first node includes a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: determine equiphase contour information associated with an antenna of the first node at one or more carrier frequencies; and transmit, via the at least one transceiver, an indication of the equiphase contour information to a second node.

[0008] In an aspect, a device includes a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: determine equiphase contour information associated with an antenna of a first node at one or more carrier frequencies; and correct measurement information associated with a carrier phase-based position estimation session based at least in part on the equiphase contour information.

[0009] In an aspect, a first node includes means for determining equiphase contour information associated with an antenna of the first node at one or more carrier frequencies; and means for transmitting an indication of the equiphase contour information to a second node.

[0010] In an aspect, a device includes means for determining equiphase contour information associated with an antenna of a first node at one or more carrier frequencies; and means for correcting measurement information associated with a carrier phase-based position estimation session based at least in part on the equiphase contour information.

[0011] In an aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a first node, cause the first node to: determine equiphase contour information associated with an antenna of the first node at one or more carrier frequencies; and transmit an indication of the equiphase contour information to a second node.

[0012] In an aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a device, cause the device to: determine equiphase contour information associated with an antenna of a first node at one or more carrier frequencies; and correct measurement information associated with a carrier phase-based position estimation session based at least in part on the equiphase contour information.

[0013] Other objects and advantages associated with the aspects disclosed herein will be apparent to those skilled in the art based on the accompanying drawings and detailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The accompanying drawings are presented to aid in the description of various aspects of the disclosure and are provided solely for illustration of the aspects and not limitation thereof.

[0015] FIG. 1 illustrates an example wireless communications system, according to aspects of the disclosure.

[0016] FIGS. 2A and 2B illustrate example wireless network structures, according to aspects of the disclosure.

[0017] FIGS. 3A, 3B, and 3C are simplified block diagrams of several sample aspects of components that may be employed in a user equipment (UE), a base station, and a network entity, respectively, and configured to support communications as taught herein.

[0018] FIG. 4 is a diagram illustrating an example frame structure, according to aspects of the disclosure.

[0019] FIG. 5 is a diagram illustrating various downlink channels within an example downlink slot, according to aspects of the disclosure.

[0020] FIG. 6 is a diagram illustrating various uplink channels within an example uplink slot, according to aspects of the disclosure. [0021] FIG. 7 illustrates time and frequency resources used for sidelink communication.

[0022] FIG. 8 is a diagram of an example positioning reference signal (PRS) configuration for the PRS transmissions of a given base station, according to aspects of the disclosure.

[0023] FIG. 9 is a diagram illustrating an example downlink positioning reference signal (DL- PRS) configuration for two transmission-reception points (TRPs) operating in the same positioning frequency layer, according to aspects of the disclosure.

[0024] FIG. 10 illustrates examples of various positioning methods supported in New Radio (NR), according to aspects of the disclosure.

[0025] FIG. 11 is a diagram illustrating an example round-trip-time (RTT) procedure for determining a location of a UE, according to aspects of the disclosure.

[0026] FIG. 12 is a diagram showing example timings of RTT measurement signals exchanged between a base station and a UE, according to aspects of the disclosure.

[0027] FIG. 13 is a diagram illustrating example timings of RTT measurement signals exchanged between a base station and a UE, according to aspects of the disclosure.

[0028] FIG. 14 illustrates a time difference of arrival (TDOA)-based positioning procedure in an example wireless communications system, according to aspects of the disclosure.

[0029] FIG. 15 illustrates an example wireless communication system in which a vehicle user equipment (V-UE) is exchanging ranging signals with a roadside unit (RSU) and another V-UE, according to aspects of the disclosure.

[0030] FIG. 16 is a diagram illustrating an example base station in communication with an example UE, according to aspects of the disclosure.

[0031] FIG. 17 illustrates a single difference (SD) anchor measurement scheme in accordance with aspects of the disclosure.

[0032] FIG. 18 illustrates a SD anchor measurement scheme in accordance with aspects of the disclosure.

[0033] FIG. 19 illustrates a double difference (DD) measurement scheme in accordance with aspects of the disclosure.

[0034] FIG. 20 illustrates a phase center depiction in accordance with aspects of the disclosure.

[0035] FIG. 21 illustrates a phase center depiction in accordance with aspects of the disclosure.

[0036] FIG. 22 illustrates a depiction of ideal vs. real equiphase contours in accordance with aspects of the disclosure.

[0037] FIG. 23 depicts antenna phase patterns with various equiphase contours in accordance with aspects of the disclosure. [0038] FIG. 24 illustrates phase centers in accordance with aspects of the disclosure.

[0039] FIG. 25 illustrates an exemplary process of communication, according to aspects of the disclosure.

[0040] FIG. 26 illustrates an exemplary process of communication, according to aspects of the disclosure.

DETAILED DESCRIPTION

[0041] Aspects of the disclosure are provided in the following description and related drawings directed to various examples provided for illustration purposes. Alternate aspects may be devised without departing from the scope of the disclosure. Additionally, well-known elements of the disclosure will not be described in detail or will be omitted so as not to obscure the relevant details of the disclosure.

[0042] The words “exemplary” and/or “example” are used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” and/or “example” is not necessarily to be construed as preferred or advantageous over other aspects. Likewise, the term “aspects of the disclosure” does not require that all aspects of the disclosure include the discussed feature, advantage or mode of operation.

[0043] Those of skill in the art will appreciate that the information and signals described below 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 below may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof, depending in part on the particular application, in part on the desired design, in part on the corresponding technology, etc.

[0044] Further, many aspects are described in terms of sequences of actions to be performed by, for example, elements of a computing device. It will be recognized that various actions described herein can be performed by specific circuits (e.g., application specific integrated circuits (ASICs)), by program instructions being executed by one or more processors, or by a combination of both. Additionally, the sequence(s) of actions described herein can be considered to be embodied entirely within any form of non- transitory computer-readable storage medium having stored therein a corresponding set of computer instructions that, upon execution, would cause or instruct an associated processor of a device to perform the functionality described herein. Thus, the various aspects of the disclosure may be embodied in a number of different forms, all of which have been contemplated to be within the scope of the claimed subject matter. In addition, for each of the aspects described herein, the corresponding form of any such aspects may be described herein as, for example, “logic configured to” perform the described action.

[0045] As used herein, the terms “user equipment” (UE) and “base station” are not intended to be specific or otherwise limited to any particular radio access technology (RAT), unless otherwise noted. In general, a UE may be any wireless communication device (e.g., a mobile phone, router, tablet computer, laptop computer, consumer asset locating device, wearable (e.g., smartwatch, glasses, augmented reality (AR) / virtual reality (VR) headset, etc.), vehicle (e.g., automobile, motorcycle, bicycle, etc.), Internet of Things (loT) device, etc.) used by a user to communicate over a wireless communications network. A UE may be mobile or may (e.g., at certain times) be stationary, and may communicate with a radio access network (RAN). As used herein, the term “UE” may be referred to interchangeably as an “access terminal” or “AT,” a “client device,” a “wireless device,” a “subscriber device,” a “subscriber terminal,” a “subscriber station,” a “user terminal” or “UT,” a “mobile device,” a “mobile terminal,” a “mobile station,” or variations thereof. Generally, UEs can communicate with a core network via a RAN, and through the core network the UEs can be connected with external networks such as the Internet and with other UEs. Of course, other mechanisms of connecting to the core network and/or the Internet are also possible for the UEs, such as over wired access networks, wireless local area network (WLAN) networks (e.g., based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 specification, etc.) and so on.

[0046] A base station may operate according to one of several RATs in communication with UEs depending on the network in which it is deployed, and may be alternatively referred to as an access point (AP), a network node, a NodeB, an evolved NodeB (eNB), a next generation eNB (ng-eNB), a New Radio (NR) Node B (also referred to as a gNB or gNodeB), etc. A base station may be used primarily to support wireless access by UEs, including supporting data, voice, and/or signaling connections for the supported UEs. In some systems a base station may provide purely edge node signaling functions while in other systems it may provide additional control and/or network management functions. A communication link through which UEs can send signals to a base station is called an uplink (UL) channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, etc.). A communication link through which the base station can send signals to UEs is called a downlink (DL) or forward link channel (e.g., a paging channel, a control channel, a broadcast channel, a forward traffic channel, etc.). As used herein the term traffic channel (TCH) can refer to either an uplink / reverse or downlink / forward traffic channel.

[0047] The term “base station” may refer to a single physical transmission-reception point (TRP) or to multiple physical TRPs that may or may not be co-located. For example, where the term “base station” refers to a single physical TRP, the physical TRP may be an antenna of the base station corresponding to a cell (or several cell sectors) of the base station. Where the term “base station” refers to multiple co-located physical TRPs, the physical TRPs may be an array of antennas (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming) of the base station. Where the term “base station” refers to multiple non-co-located physical TRPs, the physical TRPs may be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transport medium) or a remote radio head (RRH) (a remote base station connected to a serving base station). Alternatively, the non-co-located physical TRPs may be the serving base station receiving the measurement report from the UE and a neighbor base station whose reference radio frequency (RF) signals the UE is measuring. Because a TRP is the point from which a base station transmits and receives wireless signals, as used herein, references to transmission from or reception at a base station are to be understood as referring to a particular TRP of the base station.

[0048] In some implementations that support positioning of UEs, a base station may not support wireless access by UEs (e.g., may not support data, voice, and/or signaling connections for UEs), but may instead transmit reference signals to UEs to be measured by the UEs, and/or may receive and measure signals transmitted by the UEs. Such a base station may be referred to as a positioning beacon (e.g., when transmitting signals to UEs) and/or as a location measurement unit (e.g., when receiving and measuring signals from UEs).

[0049] An “RF signal” comprises an electromagnetic wave of a given frequency that transports information through the space between a transmitter and a receiver. As used herein, a transmitter may transmit a single “RF signal” or multiple “RF signals” to a receiver. However, the receiver may receive multiple “RF signals” corresponding to each transmitted RF signal due to the propagation characteristics of RF signals through multipath channels. The same transmitted RF signal on different paths between the transmitter and receiver may be referred to as a “multipath” RF signal. As used herein, an RF signal may also be referred to as a “wireless signal” or simply a “signal” where it is clear from the context that the term “signal” refers to a wireless signal or an RF signal. [0050] FIG. 1 illustrates an example wireless communications system 100, according to aspects of the disclosure. The wireless communications system 100 (which may also be referred to as a wireless wide area network (WWAN)) may include various base stations 102 (labeled “BS”) and various UEs 104. The base stations 102 may include macro cell base stations (high power cellular base stations) and/or small cell base stations (low power cellular base stations). In an aspect, the macro cell base stations may include eNBs and/or ng-eNBs where the wireless communications system 100 corresponds to an LTE network, or gNBs where the wireless communications system 100 corresponds to a NR network, or a combination of both, and the small cell base stations may include femtocells, picocells, microcells, etc.

[0051] The base stations 102 may collectively form a RAN and interface with a core network 170 (e.g., an evolved packet core (EPC) or a 5G core (5GC)) through backhaul links 122, and through the core network 170 to one or more location servers 172 (e.g., a location management function (LMF) or a secure user plane location (SUPL) location platform (SLP)). The location server(s) 172 may be part of core network 170 or may be external to core network 170. A location server 172 may be integrated with a base station 102. A UE 104 may communicate with a location server 172 directly or indirectly. For example, a UE 104 may communicate with a location server 172 via the base station 102 that is currently serving that UE 104. A UE 104 may also communicate with a location server 172 through another path, such as via an application server (not shown), via another network, such as via a wireless local area network (WLAN) access point (AP) (e.g., AP 150 described below), and so on. For signaling purposes, communication between a UE 104 and a location server 172 may be represented as an indirect connection (e.g., through the core network 170, etc.) or a direct connection (e.g., as shown via direct connection 128), with the intervening nodes (if any) omitted from a signaling diagram for clarity.

[0052] In addition to other functions, the base stations 102 may perform functions that relate to one or more of transferring user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment trace, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 may communicate with each other directly or indirectly (e.g., through the EPC / 5GC) over backhaul links 134, which may be wired or wireless.

[0053] The base stations 102 may wirelessly communicate with the UEs 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. In an aspect, one or more cells may be supported by a base station 102 in each geographic coverage area 110. A “cell” is a logical communication entity used for communication with a base station (e.g., over some frequency resource, referred to as a carrier frequency, component carrier, carrier, band, or the like), and may be associated with an identifier (e.g., a physical cell identifier (PCI), an enhanced cell identifier (ECI), a virtual cell identifier (VCI), a cell global identifier (CGI), etc.) for distinguishing cells operating via the same or a different carrier frequency. In some cases, different cells may be configured according to different protocol types (e.g., machine-type communication (MTC), narrowband loT (NB-IoT), enhanced mobile broadband (eMBB), or others) that may provide access for different types of UEs. Because a cell is supported by a specific base station, the term “cell” may refer to either or both of the logical communication entity and the base station that supports it, depending on the context. In addition, because a TRP is typically the physical transmission point of a cell, the terms “cell” and “TRP” may be used interchangeably. In some cases, the term “cell” may also refer to a geographic coverage area of a base station (e.g., a sector), insofar as a carrier frequency can be detected and used for communication within some portion of geographic coverage areas 110.

[0054] While neighboring macro cell base station 102 geographic coverage areas 110 may partially overlap (e.g., in a handover region), some of the geographic coverage areas 110 may be substantially overlapped by a larger geographic coverage area 110. For example, a small cell base station 102' (labeled “SC” for “small cell”) may have a geographic coverage area 110' that substantially overlaps with the geographic coverage area 110 of one or more macro cell base stations 102. A network that includes both small cell and macro cell base stations may be known as a heterogeneous network. A heterogeneous network may also include home eNBs (HeNBs), which may provide service to a restricted group known as a closed subscriber group (CSG). [0055] The communication links 120 between the base stations 102 and the UEs 104 may include uplink (also referred to as reverse link) transmissions from a UE 104 to a base station 102 and/or downlink (DL) (also referred to as forward link) transmissions from a base station 102 to a UE 104. The communication links 120 may use MIMO antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity. The communication links 120 may be through one or more carrier frequencies. Allocation of carriers may be asymmetric with respect to downlink and uplink (e.g., more or less carriers may be allocated for downlink than for uplink).

[0056] The wireless communications system 100 may further include a wireless local area network (WLAN) access point (AP) 150 in communication with WLAN stations (STAs) 152 via communication links 154 in an unlicensed frequency spectrum (e.g., 5 GHz). When communicating in an unlicensed frequency spectrum, the WLAN STAs 152 and/or the WLAN AP 150 may perform a clear channel assessment (CCA) or listen before talk (LBT) procedure prior to communicating in order to determine whether the channel is available.

[0057] The small cell base station 102' may operate in a licensed and/or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell base station 102' may employ LTE or NR technology and use the same 5 GHz unlicensed frequency spectrum as used by the WLAN AP 150. The small cell base station 102', employing LTE / 5G in an unlicensed frequency spectrum, may boost coverage to and/or increase capacity of the access network. NR in unlicensed spectrum may be referred to as NR-U. LTE in an unlicensed spectrum may be referred to as LTE-U, licensed assisted access (LAA), or MulteFire.

[0058] The wireless communications system 100 may further include a millimeter wave (mmW) base station 180 that may operate in mmW frequencies and/or near mmW frequencies in communication with a UE 182. Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 millimeter and 10 millimeters. Radio waves in this band may be referred to as a millimeter wave. Near mmW may extend down to a frequency of 3 GHz with a wavelength of 100 millimeters. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, also referred to as centimeter wave. Communications using the mmW/near mmW radio frequency band have high path loss and a relatively short range. The mmW base station 180 and the UE 182 may utilize beamforming (transmit and/or receive) over a mmW communication link 184 to compensate for the extremely high path loss and short range. Further, it will be appreciated that in alternative configurations, one or more base stations 102 may also transmit using mmW or near mmW and beamforming. Accordingly, it will be appreciated that the foregoing illustrations are merely examples and should not be construed to limit the various aspects disclosed herein.

[0059] Transmit beamforming is a technique for focusing an RF signal in a specific direction. Traditionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts the signal in all directions (omni-directionally). With transmit beamforming, the network node determines where a given target device (e.g., a UE) is located (relative to the transmitting network node) and projects a stronger downlink RF signal in that specific direction, thereby providing a faster (in terms of data rate) and stronger RF signal for the receiving device(s). To change the directionality of the RF signal when transmitting, a network node can control the phase and relative amplitude of the RF signal at each of the one or more transmitters that are broadcasting the RF signal. For example, a network node may use an array of antennas (referred to as a “phased array” or an “antenna array”) that creates abeam of RF waves that can be “steered” to point in different directions, without actually moving the antennas. Specifically, the RF current from the transmitter is fed to the individual antennas with the correct phase relationship so that the radio waves from the separate antennas add together to increase the radiation in a desired direction, while cancelling to suppress radiation in undesired directions.

[0060] Transmit beams may be quasi-co-located, meaning that they appear to the receiver (e.g., a UE) as having the same parameters, regardless of whether or not the transmitting antennas of the network node themselves are physically co-located. In NR, there are four types of quasi-co-location (QCL) relations. Specifically, a QCL relation of a given type means that certain parameters about a second reference RF signal on a second beam can be derived from information about a source reference RF signal on a source beam. Thus, if the source reference RF signal is QCL Type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, average delay, and delay spread of a second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL Type B, the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of a second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL Type C, the receiver can use the source reference RF signal to estimate the Doppler shift and average delay of a second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL Type D, the receiver can use the source reference RF signal to estimate the spatial receive parameter of a second reference RF signal transmitted on the same channel.

[0061] In receive beamforming, the receiver uses a receive beam to amplify RF signals detected on a given channel. For example, the receiver can increase the gain setting and/or adjust the phase setting of an array of antennas in a particular direction to amplify (e.g., to increase the gain level of) the RF signals received from that direction. Thus, when a receiver is said to beamform in a certain direction, it means the beam gain in that direction is high relative to the beam gain along other directions, or the beam gain in that direction is the highest compared to the beam gain in that direction of all other receive beams available to the receiver. This results in a stronger received signal strength (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), signal-to- interference-plus-noise ratio (SINR), etc.) of the RF signals received from that direction.

[0062] Transmit and receive beams may be spatially related. A spatial relation means that parameters for a second beam (e.g., a transmit or receive beam) for a second reference signal can be derived from information about a first beam (e.g., a receive beam or a transmit beam) for a first reference signal. For example, a UE may use a particular receive beam to receive a reference downlink reference signal (e.g., synchronization signal block (SSB)) from a base station. The UE can then form a transmit beam for sending an uplink reference signal (e.g., sounding reference signal (SRS)) to that base station based on the parameters of the receive beam.

[0063] Note that a “downlink” beam may be either a transmit beam or a receive beam, depending on the entity forming it. For example, if a base station is forming the downlink beam to transmit a reference signal to a UE, the downlink beam is a transmit beam. If the UE is forming the downlink beam, however, it is a receive beam to receive the downlink reference signal. Similarly, an “uplink” beam may be either a transmit beam or a receive beam, depending on the entity forming it. For example, if a base station is forming the uplink beam, it is an uplink receive beam, and if a UE is forming the uplink beam, it is an uplink transmit beam.

[0064] The electromagnetic spectrum is often subdivided, based on frequency/wavelength, into various classes, bands, channels, etc. In 5G NR two initial operating bands have been identified as frequency range designations FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.

[0065] The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5GNR studies have identified an operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz - 24.25 GHz). Frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics, and thus may effectively extend features of FR1 and/or FR2 into mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5GNR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz - 71 GHz), FR4 (52.6 GHz - 114.25 GHz), and FR5 (114.25 GHz - 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0066] With the above aspects in mind, unless specifically stated otherwise, it should be understood that the term “sub-6 GHz” or the like if used herein may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, it should be understood that the term “millimeter wave” or the like if used herein may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and/or FR5, or may be within the EHF band.

[0067] In a multi-carrier system, such as 5G, one of the carrier frequencies is referred to as the “primary carrier” or “anchor carrier” or “primary serving cell” or “PCell,” and the remaining carrier frequencies are referred to as “secondary carriers” or “secondary serving cells” or “SCells.” In carrier aggregation, the anchor carrier is the carrier operating on the primary frequency (e.g., FR1) utilized by a UE 104/182 and the cell in which the UE 104/182 either performs the initial radio resource control (RRC) connection establishment procedure or initiates the RRC connection re-establishment procedure. The primary carrier carries all common and UE-specific control channels, and may be a carrier in a licensed frequency (however, this is not always the case). A secondary carrier is a carrier operating on a second frequency (e.g., FR2) that may be configured once the RRC connection is established between the UE 104 and the anchor carrier and that may be used to provide additional radio resources. In some cases, the secondary carrier may be a carrier in an unlicensed frequency. The secondary carrier may contain only necessary signaling information and signals, for example, those that are UE-specific may not be present in the secondary carrier, since both primary uplink and downlink carriers are typically UE-specific. This means that different UEs 104/182 in a cell may have different downlink primary carriers. The same is true for the uplink primary carriers. The network is able to change the primary carrier of any UE 104/182 at any time. This is done, for example, to balance the load on different carriers. Because a “serving cell” (whether a PCell or an SCell) corresponds to a carrier frequency / component carrier over which some base station is communicating, the term “cell,” “serving cell,” “component carrier,” “carrier frequency,” and the like can be used interchangeably.

[0068] For example, still referring to FIG. 1, one of the frequencies utilized by the macro cell base stations 102 may be an anchor carrier (or “PCell”) and other frequencies utilized by the macro cell base stations 102 and/or the mmW base station 180 may be secondary carriers (“SCells”). The simultaneous transmission and/or reception of multiple carriers enables the UE 104/182 to significantly increase its data transmission and/or reception rates. For example, two 20 MHz aggregated carriers in a multi-carrier system would theoretically lead to a two-fold increase in data rate (i.e., 40 MHz), compared to that attained by a single 20 MHz carrier.

[0069] The wireless communications system 100 may further include a UE 164 that may communicate with a macro cell base station 102 over a communication link 120 and/or the mmW base station 180 over a mmW communication link 184. For example, the macro cell base station 102 may support a PCell and one or more SCells for the UE 164 and the mmW base station 180 may support one or more SCells for the UE 164.

[0070] In some cases, the UE 164 and the UE 182 may be capable of sidelink communication. Sidelink-capable UEs (SL-UEs) may communicate with base stations 102 over communication links 120 using the Uu interface (i.e., the air interface between a UE and abase station). SL-UEs (e.g., UE 164, UE 182) may also communicate directly with each other over a wireless sidelink 160 using the PC5 interface (i.e., the air interface between sidelink-capable UEs). A wireless sidelink (or just “sidelink”) is an adaptation of the core cellular (e.g., LTE, NR) standard that allows direct communication between two or more UEs without the communication needing to go through a base station. Sidelink communication may be unicast or multicast, and may be used for device-to-device (D2D) media-sharing, vehicle-to-vehicle (V2V) communication, vehicle-to-every thing (V2X) communication (e.g., cellular V2X (cV2X) communication, enhanced V2X (eV2X) communication, etc.), emergency rescue applications, etc. One or more of a group of SL- UEs utilizing sidelink communications may be within the geographic coverage area 110 of a base station 102. Other SL-UEs in such a group may be outside the geographic coverage area 110 of a base station 102 or be otherwise unable to receive transmissions from a base station 102. In some cases, groups of SL-UEs communicating via sidelink communications may utilize a one-to-many (1 :M) system in which each SL-UE transmits to every other SL-UE in the group. In some cases, a base station 102 facilitates the scheduling of resources for sidelink communications. In other cases, sidelink communications are carried out between SL-UEs without the involvement of a base station 102.

[0071] In an aspect, the sidelink 160 may operate over a wireless communication medium of interest, which may be shared with other wireless communications between other vehicles and/or infrastructure access points, as well as other RATs. A “medium” may be composed of one or more time, frequency, and/or space communication resources (e.g., encompassing one or more channels across one or more carriers) associated with wireless communication between one or more transmitter / receiver pairs. In an aspect, the medium of interest may correspond to at least a portion of an unlicensed frequency band shared among various RATs. Although different licensed frequency bands have been reserved for certain communication systems (e.g., by a government entity such as the Federal Communications Commission (FCC) in the United States), these systems, in particular those employing small cell access points, have recently extended operation into unlicensed frequency bands such as the Unlicensed National Information Infrastructure (U-NII) band used by wireless local area network (WLAN) technologies, most notably IEEE 802.1 lx WLAN technologies generally referred to as “Wi-Fi.” Example systems of this type include different variants of CDMA systems, TDMA systems, FDMA systems, orthogonal FDMA (OFDMA) systems, single-carrier FDMA (SC-FDMA) systems, and so on.

[0072] Note that although FIG. 1 only illustrates two of the UEs as SL-UEs (i.e., UEs 164 and 182), any of the illustrated UEs may be SL-UEs. Further, although only UE 182 was described as being capable of beamforming, any of the illustrated UEs, including UE 164, may be capable of beamforming. Where SL-UEs are capable of beamforming, they may beamform towards each other (i.e., towards other SL-UEs), towards other UEs (e.g., UEs 104), towards base stations (e.g., base stations 102, 180, small cell 102’, access point 150), etc. Thus, in some cases, UEs 164 and 182 may utilize beamforming over sidelink 160.

[0073] In the example of FIG. 1, any of the illustrated UEs (shown in FIG. 1 as a single UE 104 for simplicity) may receive signals 124 from one or more Earth orbiting space vehicles (SVs) 112 (e.g., satellites). In an aspect, the SVs 112 may be part of a satellite positioning system that a UE 104 can use as an independent source of location information. A satellite positioning system typically includes a system of transmitters (e.g., SVs 112) positioned to enable receivers (e.g., UEs 104) to determine their location on or above the Earth based, at least in part, on positioning signals (e.g., signals 124) received from the transmitters. Such a transmitter typically transmits a signal marked with a repeating pseudo-random noise (PN) code of a set number of chips. While typically located in SVs 112, transmitters may sometimes be located on ground-based control stations, base stations 102, and/or other UEs 104. A UE 104 may include one or more dedicated receivers specifically designed to receive signals 124 for deriving geo location information from the SVs 112.

[0074] In a satellite positioning system, the use of signals 124 can be augmented by various satellite-based augmentation systems (SBAS) that may be associated with or otherwise enabled for use with one or more global and/or regional navigation satellite systems. For example an SBAS may include an augmentation system(s) that provides integrity information, differential corrections, etc., such as the Wide Area Augmentation System (WAAS), the European Geostationary Navigation Overlay Service (EGNOS), the Multifunctional Satellite Augmentation System (MSAS), the Global Positioning System (GPS) Aided Geo Augmented Navigation or GPS and Geo Augmented Navigation system (GAGAN), and/or the like. Thus, as used herein, a satellite positioning system may include any combination of one or more global and/or regional navigation satellites associated with such one or more satellite positioning systems.

[0075] In an aspect, SVs 112 may additionally or alternatively be part of one or more nonterrestrial networks (NTNs). In an NTN, an SV 112 is connected to an earth station (also referred to as a ground station, NTN gateway, or gateway), which in turn is connected to an element in a 5G network, such as a modified base station 102 (without a terrestrial antenna) or a network node in a 5GC. This element would in turn provide access to other elements in the 5G network and ultimately to entities external to the 5G network, such as Internet web servers and other user devices. In that way, a UE 104 may receive communication signals (e.g., signals 124) from an SV 112 instead of, or in addition to, communication signals from a terrestrial base station 102.

[0076] The wireless communications system 100 may further include one or more UEs, such as UE 190, that connects indirectly to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (referred to as “sidelinks”). In the example of FIG. 1, UE 190 has a D2D P2P link 192 with one of the UEs 104 connected to one of the base stations 102 (e.g., through which UE 190 may indirectly obtain cellular connectivity) and a D2D P2P link 194 with WLAN STA 152 connected to the WLAN AP 150 (through which UE 190 may indirectly obtain WLAN-based Internet connectivity). In an example, the D2D P2P links 192 and 194 may be supported with any well-known D2D RAT, such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), Bluetooth®, and so on.

[0077] FIG. 2A illustrates an example wireless network structure 200. For example, a 5GC 210 (also referred to as a Next Generation Core (NGC)) can be viewed functionally as control plane (C-plane) functions 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and user plane (U-plane) functions 212, (e.g., UE gateway function, access to data networks, IP routing, etc.) which operate cooperatively to form the core network. User plane interface (NG-U) 213 and control plane interface (NG-C) 215 connect the gNB 222 to the 5GC 210 and specifically to the user plane functions 212 and control plane functions 214, respectively. In an additional configuration, an ng-eNB 224 may also be connected to the 5GC 210 via NG-C 215 to the control plane functions 214 and NG-U 213 to user plane functions 212. Further, ng-eNB 224 may directly communicate with gNB 222 via a backhaul connection 223. In some configurations, a Next Generation RAN (NG-RAN) 220 may have one or more gNBs 222, while other configurations include one or more of both ng-eNBs 224 and gNBs 222. Either (or both) gNB 222 or ng-eNB 224 may communicate with one or more UEs 204 (e.g., any of the UEs described herein).

[0078] Another optional aspect may include a location server 230, which may be in communication with the 5GC 210 to provide location assistance for UE(s) 204. The location server 230 can be implemented as a plurality of separate servers (e.g., physically separate servers, different software modules on a single server, different software modules spread across multiple physical servers, etc.), or alternately may each correspond to a single server. The location server 230 can be configured to support one or more location services for UEs 204 that can connect to the location server 230 via the core network, 5GC 210, and/or via the Internet (not illustrated). Further, the location server 230 may be integrated into a component of the core network, or alternatively may be external to the core network (e.g., a third party server, such as an original equipment manufacturer (OEM) server or service server).

[0079] FIG. 2B illustrates another example wireless network structure 250. A 5GC 260 (which may correspond to 5GC 210 in FIG. 2A) can be viewed functionally as control plane functions, provided by an access and mobility management function (AMF) 264, and user plane functions, provided by a user plane function (UPF) 262, which operate cooperatively to form the core network (i.e., 5GC 260). The functions of the AMF 264 include registration management, connection management, reachability management, mobility management, lawful interception, transport for session management (SM) messages between one or more UEs 204 (e.g., any of the UEs described herein) and a session management function (SMF) 266, transparent proxy services for routing SM messages, access authentication and access authorization, transport for short message service (SMS) messages between the UE 204 and the short message service function (SMSF) (not shown), and security anchor functionality (SEAF). The AMF 264 also interacts with an authentication server function (AUSF) (not shown) and the UE 204, and receives the intermediate key that was established as a result of the UE 204 authentication process. In the case of authentication based on a UMTS (universal mobile telecommunications system) subscriber identity module (USIM), the AMF 264 retrieves the security material from the AUSF. The functions of the AMF 264 also include security context management (SCM). The SCM receives a key from the SEAF that it uses to derive access-network specific keys. The functionality of the AMF 264 also includes location services management for regulatory services, transport for location services messages between the UE 204 and a location management function (LMF) 270 (which acts as a location server 230), transport for location services messages between the NG-RAN 220 and the LMF 270, evolved packet system (EPS) bearer identifier allocation for interworking with the EPS, and UE 204 mobility event notification. In addition, the AMF 264 also supports functionalities for non-3GPP (Third Generation Partnership Project) access networks. [0080] Functions of the UPF 262 include acting as an anchor point for intra-/inter-RAT mobility (when applicable), acting as an external protocol data unit (PDU) session point of interconnect to a data network (not shown), providing packet routing and forwarding, packet inspection, user plane policy rule enforcement (e.g., gating, redirection, traffic steering), lawful interception (user plane collection), traffic usage reporting, quality of service (QoS) handling for the user plane (e.g., uplink/ downlink rate enforcement, reflective QoS marking in the downlink), uplink traffic verification (service data flow (SDF) to QoS flow mapping), transport level packet marking in the uplink and downlink, downlink packet buffering and downlink data notification triggering, and sending and forwarding of one or more “end markers” to the source RAN node. The UPF 262 may also support transfer of location services messages over a user plane between the UE 204 and a location server, such as an SLP 272.

[0081] The functions of the SMF 266 include session management, UE Internet protocol (IP) address allocation and management, selection and control of user plane functions, configuration of traffic steering at the UPF 262 to route traffic to the proper destination, control of part of policy enforcement and QoS, and downlink data notification. The interface over which the SMF 266 communicates with the AMF 264 is referred to as the Nil interface.

[0082] Another optional aspect may include an LMF 270, which may be in communication with the 5GC 260 to provide location assistance for UEs 204. The LMF 270 can be implemented as a plurality of separate servers (e.g., physically separate servers, different software modules on a single server, different software modules spread across multiple physical servers, etc.), or alternately may each correspond to a single server. The LMF 270 can be configured to support one or more location services for UEs 204 that can connect to the LMF 270 via the core network, 5GC 260, and/or via the Internet (not illustrated). The SLP 272 may support similar functions to the LMF 270, but whereas the LMF 270 may communicate with the AMF 264, NG-RAN 220, and UEs 204 over a control plane (e.g., using interfaces and protocols intended to convey signaling messages and not voice or data), the SLP 272 may communicate with UEs 204 and external clients (e.g., third-party server 274) over a user plane (e.g., using protocols intended to carry voice and/or data like the transmission control protocol (TCP) and/or IP).

[0083] Yet another optional aspect may include a third-party server 274, which may be in communication with the LMF 270, the SLP 272, the 5GC 260 (e.g., via the AMF 264 and/or the UPF 262), the NG-RAN 220, and/or the UE 204 to obtain location information (e.g., a location estimate) for the UE 204. As such, in some cases, the third-party server 274 may be referred to as a location services (LCS) client or an external client. The third- party server 274 can be implemented as a plurality of separate servers (e.g., physically separate servers, different software modules on a single server, different software modules spread across multiple physical servers, etc.), or alternately may each correspond to a single server.

[0084] User plane interface 263 and control plane interface 265 connect the 5GC 260, and specifically the UPF 262 and AMF 264, respectively, to one or more gNBs 222 and/or ng-eNBs 224 in the NG-RAN 220. The interface between gNB(s) 222 and/or ng-eNB(s) 224 and the AMF 264 is referred to as the “N2” interface, and the interface between gNB(s) 222 and/or ng-eNB(s) 224 and the UPF 262 is referred to as the “N3” interface. The gNB(s) 222 and/or ng-eNB(s) 224 of the NG-RAN 220 may communicate directly with each other via backhaul connections 223, referred to as the “Xn-C” interface. One or more of gNBs 222 and/or ng-eNBs 224 may communicate with one or more UEs 204 over a wireless interface, referred to as the “Uu” interface.

[0085] The functionality of a gNB 222 may be divided between a gNB central unit (gNB-CU) 226, one or more gNB distributed units (gNB-DUs) 228, and one or more gNB radio units (gNB-RUs) 229. A gNB-CU 226 is a logical node that includes the base station functions of transferring user data, mobility control, radio access network sharing, positioning, session management, and the like, except for those functions allocated exclusively to the gNB-DU(s) 228. More specifically, the gNB-CU 226 generally host the radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) protocols of the gNB 222. A gNB-DU 228 is a logical node that generally hosts the radio link control (RLC) and medium access control (MAC) layer of the gNB 222. Its operation is controlled by the gNB-CU 226. One gNB-DU 228 can support one or more cells, and one cell is supported by only one gNB-DU 228. The interface 232 between the gNB-CU 226 and the one or more gNB-DUs 228 is referred to as the “Fl” interface. The physical (PHY) layer functionality of a gNB 222 is generally hosted by one or more standalone gNB-RUs 229 that perform functions such as power amplification and signal transmission/reception. The interface between a gNB-DU 228 and a gNB-RU 229 is referred to as the “Fx” interface. Thus, a UE 204 communicates with the gNB-CU 226 via the RRC, SDAP, and PDCP layers, with a gNB-DU 228 via the RLC and MAC layers, and with a gNB-RU 229 via the PHY layer.

[0086] FIGS. 3A, 3B, and 3C illustrate several example components (represented by corresponding blocks) that may be incorporated into a UE 302 (which may correspond to any of the UEs described herein), a base station 304 (which may correspond to any of the base stations described herein), and a network entity 306 (which may correspond to or embody any of the network functions described herein, including the location server 230 and the LMF 270, or alternatively may be independent from the NG-RAN 220 and/or 5GC 210/260 infrastructure depicted in FIGS. 2A and 2B, such as a private network) to support the file transmission operations as taught herein. It will be appreciated that these components may be implemented in different types of apparatuses in different implementations (e.g., in an ASIC, in a system-on-chip (SoC), etc.). The illustrated components may also be incorporated into other apparatuses in a communication system. For example, other apparatuses in a system may include components similar to those described to provide similar functionality. Also, a given apparatus may contain one or more of the components. For example, an apparatus may include multiple transceiver components that enable the apparatus to operate on multiple carriers and/or communicate via different technologies.

[0087] The UE 302 and the base station 304 each include one or more wireless wide area network (WWAN) transceivers 310 and 350, respectively, providing means for communicating (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, means for refraining from transmitting, etc.) via one or more wireless communication networks (not shown), such as an NR network, an LTE network, a GSM network, and/or the like. The WWAN transceivers 310 and 350 may each be connected to one or more antennas 316 and 356, respectively, for communicating with other network nodes, such as other UEs, access points, base stations (e.g., eNBs, gNBs), etc., via at least one designated RAT (e.g., NR, LTE, GSM, etc.) over a wireless communication medium of interest (e.g., some set of time/frequency resources in a particular frequency spectrum). The WWAN transceivers 310 and 350 may be variously configured for transmitting and encoding signals 318 and 358 (e.g., messages, indications, information, and so on), respectively, and, conversely, for receiving and decoding signals 318 and 358 (e.g., messages, indications, information, pilots, and so on), respectively, in accordance with the designated RAT. Specifically, the WWAN transceivers 310 and 350 include one or more transmitters 314 and 354, respectively, for transmitting and encoding signals 318 and 358, respectively, and one or more receivers 312 and 352, respectively, for receiving and decoding signals 318 and 358, respectively.

[0088] The UE 302 and the base station 304 each also include, at least in some cases, one or more short-range wireless transceivers 320 and 360, respectively. The short-range wireless transceivers 320 and 360 may be connected to one or more antennas 326 and 366, respectively, and provide means for communicating (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, means for refraining from transmitting, etc.) with other network nodes, such as other UEs, access points, base stations, etc., via at least one designated RAT (e.g., WiFi, LTE-D, Bluetooth®, Zigbee®, Z-Wave®, PC5, dedicated short-range communications (DSRC), wireless access for vehicular environments (WAVE), near-field communication (NFC), etc.) over a wireless communication medium of interest. The short-range wireless transceivers 320 and 360 may be variously configured for transmitting and encoding signals 328 and 368 (e.g., messages, indications, information, and so on), respectively, and, conversely, for receiving and decoding signals 328 and 368 (e.g., messages, indications, information, pilots, and so on), respectively, in accordance with the designated RAT. Specifically, the short-range wireless transceivers 320 and 360 include one or more transmitters 324 and 364, respectively, for transmitting and encoding signals 328 and 368, respectively, and one or more receivers 322 and 362, respectively, for receiving and decoding signals 328 and 368, respectively. As specific examples, the short-range wireless transceivers 320 and 360 may be WiFi transceivers, Bluetooth® transceivers, Zigbee® and/or Z-Wave® transceivers, NFC transceivers, or vehicle-to-vehicle (V2V) and/or vehicle-to-everything (V2X) transceivers.

[0089] The UE 302 and the base station 304 also include, at least in some cases, satellite signal receivers 330 and 370. The satellite signal receivers 330 and 370 may be connected to one or more antennas 336 and 376, respectively, and may provide means for receiving and/or measuring satellite positioning/communication signals 338 and 378, respectively. Where the satellite signal receivers 330 and 370 are satellite positioning system receivers, the satellite positioning/communication signals 338 and 378 may be global positioning system (GPS) signals, global navigation satellite system (GLONASS) signals, Galileo signals, Beidou signals, Indian Regional Navigation Satellite System (NAVIC), QuasiZenith Satellite System (QZSS), etc. Where the satellite signal receivers 330 and 370 are non-terrestrial network (NTN) receivers, the satellite positioning/communication signals 338 and 378 may be communication signals (e.g., carrying control and/or user data) originating from a 5G network. The satellite signal receivers 330 and 370 may comprise any suitable hardware and/or software for receiving and processing satellite positioning/communication signals 338 and 378, respectively. The satellite signal receivers 330 and 370 may request information and operations as appropriate from the other systems, and, at least in some cases, perform calculations to determine locations of the UE 302 and the base station 304, respectively, using measurements obtained by any suitable satellite positioning system algorithm.

[0090] The base station 304 and the network entity 306 each include one or more network transceivers 380 and 390, respectively, providing means for communicating (e.g., means for transmitting, means for receiving, etc.) with other network entities (e.g., other base stations 304, other network entities 306). For example, the base station 304 may employ the one or more network transceivers 380 to communicate with other base stations 304 or network entities 306 over one or more wired or wireless backhaul links. As another example, the network entity 306 may employ the one or more network transceivers 390 to communicate with one or more base station 304 over one or more wired or wireless backhaul links, or with other network entities 306 over one or more wired or wireless core network interfaces.

[0091] A transceiver may be configured to communicate over a wired or wireless link. A transceiver (whether a wired transceiver or a wireless transceiver) includes transmitter circuitry (e.g., transmitters 314, 324, 354, 364) and receiver circuitry (e.g., receivers 312, 322, 352, 362). A transceiver may be an integrated device (e.g., embodying transmitter circuitry and receiver circuitry in a single device) in some implementations, may comprise separate transmitter circuitry and separate receiver circuitry in some implementations, or may be embodied in other ways in other implementations. The transmitter circuitry and receiver circuitry of a wired transceiver (e.g., network transceivers 380 and 390 in some implementations) may be coupled to one or more wired network interface ports. Wireless transmitter circuitry (e.g., transmitters 314, 324, 354, 364) may include or be coupled to a plurality of antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, that permits the respective apparatus (e.g., UE 302, base station 304) to perform transmit “beamforming,” as described herein. Similarly, wireless receiver circuitry (e.g., receivers 312, 322, 352, 362) may include or be coupled to a plurality of antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, that permits the respective apparatus (e.g., UE 302, base station 304) to perform receive beamforming, as described herein. In an aspect, the transmitter circuitry and receiver circuitry may share the same plurality of antennas (e.g., antennas 316, 326, 356, 366), such that the respective apparatus can only receive or transmit at a given time, not both at the same time. A wireless transceiver (e.g., WWAN transceivers 310 and 350, short-range wireless transceivers 320 and 360) may also include a network listen module (NLM) or the like for performing various measurements.

[0092] As used herein, the various wireless transceivers (e.g., transceivers 310, 320, 350, and 360, and network transceivers 380 and 390 in some implementations) and wired transceivers (e.g., network transceivers 380 and 390 in some implementations) may generally be characterized as “a transceiver,” “at least one transceiver,” or “one or more transceivers.” As such, whether a particular transceiver is a wired or wireless transceiver may be inferred from the type of communication performed. For example, backhaul communication between network devices or servers will generally relate to signaling via a wired transceiver, whereas wireless communication between a UE (e.g., UE 302) and a base station (e.g., base station 304) will generally relate to signaling via a wireless transceiver.

[0093] The UE 302, the base station 304, and the network entity 306 also include other components that may be used in conjunction with the operations as disclosed herein. The UE 302, the base station 304, and the network entity 306 include one or more processors 332, 384, and 394, respectively, for providing functionality relating to, for example, wireless communication, and for providing other processing functionality. The processors 332, 384, and 394 may therefore provide means for processing, such as means for determining, means for calculating, means for receiving, means for transmitting, means for indicating, etc. In an aspect, the processors 332, 384, and 394 may include, for example, one or more general purpose processors, multi-core processors, central processing units (CPUs), ASICs, digital signal processors (DSPs), field programmable gate arrays (FPGAs), other programmable logic devices or processing circuitry, or various combinations thereof.

[0094] The UE 302, the base station 304, and the network entity 306 include memory circuitry implementing memories 340, 386, and 396 (e.g., each including a memory device), respectively, for maintaining information (e.g., information indicative of reserved resources, thresholds, parameters, and so on). The memories 340, 386, and 396 may therefore provide means for storing, means for retrieving, means for maintaining, etc. In some cases, the UE 302, the base station 304, and the network entity 306 may include equiphase contour component 342, 388, and 398, respectively. The equiphase contour component 342, 388, and 398 may be hardware circuits that are part of or coupled to the processors 332, 384, and 394, respectively, that, when executed, cause the UE 302, the base station 304, and the network entity 306 to perform the functionality described herein. In other aspects, the equiphase contour component 342, 388, and 398 may be external to the processors 332, 384, and 394 (e.g., part of a modem processing system, integrated with another processing system, etc.). Alternatively, the equiphase contour component 342, 388, and 398 may be memory modules stored in the memories 340, 386, and 396, respectively, that, when executed by the processors 332, 384, and 394 (or a modem processing system, another processing system, etc.), cause the UE 302, the base station 304, and the network entity 306 to perform the functionality described herein. FIG. 3A illustrates possible locations of the equiphase contour component 342, which may be, for example, part of the one or more WWAN transceivers 310, the memory 340, the one or more processors 332, or any combination thereof, or may be a standalone component. FIG. 3B illustrates possible locations of the equiphase contour component 388, which may be, for example, part of the one or more WWAN transceivers 350, the memory 386, the one or more processors 384, or any combination thereof, or may be a standalone component. FIG. 3C illustrates possible locations of the equiphase contour component 398, which may be, for example, part of the one or more network transceivers 390, the memory 396, the one or more processors 394, or any combination thereof, or may be a standalone component.

[0095] The UE 302 may include one or more sensors 344 coupled to the one or more processors 332 to provide means for sensing or detecting movement and/or orientation information that is independent of motion data derived from signals received by the one or more WWAN transceivers 310, the one or more short-range wireless transceivers 320, and/or the satellite signal receiver 330. By way of example, the sensor(s) 344 may include an accelerometer (e.g., a micro-electrical mechanical systems (MEMS) device), a gyroscope, a geomagnetic sensor (e.g., a compass), an altimeter (e.g., a barometric pressure altimeter), and/or any other type of movement detection sensor. Moreover, the sensor(s) 344 may include a plurality of different types of devices and combine their outputs in order to provide motion information. For example, the sensor(s) 344 may use a combination of a multi-axis accelerometer and orientation sensors to provide the ability to compute positions in two-dimensional (2D) and/or three-dimensional (3D) coordinate systems.

[0096] In addition, the UE 302 includes a user interface 346 providing means for providing indications (e.g., audible and/or visual indications) to a user and/or for receiving user input (e.g., upon user actuation of a sensing device such a keypad, a touch screen, a microphone, and so on). Although not shown, the base station 304 and the network entity 306 may also include user interfaces.

[0097] Referring to the one or more processors 384 in more detail, in the downlink, IP packets from the network entity 306 may be provided to the processor 384. The one or more processors 384 may implement functionality for an RRC layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The one or more processors 384 may provide RRC layer functionality associated with broadcasting of system information (e.g., master information block (MIB), system information blocks (SIBs)), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-RAT mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression/decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the transfer of upper layer PDUs, error correction through automatic repeat request (ARQ), concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization.

[0098] The transmitter 354 and the receiver 352 may implement Layer-1 (LI) functionality associated with various signal processing functions. Layer-1, which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation/demodulation of physical channels, and MIMO antenna processing. The transmitter 354 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an orthogonal frequency division multiplexing (OFDM) subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and/or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM symbol stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signal and/or channel condition feedback transmitted by the UE 302. Each spatial stream may then be provided to one or more different antennas 356. The transmitter 354 may modulate an RF carrier with a respective spatial stream for transmission.

[0099] At the UE 302, the receiver 312 receives a signal through its respective antenna(s) 316. The receiver 312 recovers information modulated onto an RF carrier and provides the information to the one or more processors 332. The transmitter 314 and the receiver 312 implement Layer- 1 functionality associated with various signal processing functions. The receiver 312 may perform spatial processing on the information to recover any spatial streams destined for the UE 302. If multiple spatial streams are destined for the UE 302, they may be combined by the receiver 312 into a single OFDM symbol stream. The receiver 312 then converts the OFDM symbol stream from the time-domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 304. These soft decisions may be based on channel estimates computed by a channel estimator. The soft decisions are then decoded and de-interleaved to recover the data and control signals that were originally transmitted by the base station 304 on the physical channel. The data and control signals are then provided to the one or more processors 332, which implements Layer-3 (L3) and Layer-2 (L2) functionality.

[0100] In the uplink, the one or more processors 332 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets from the core network. The one or more processors 332 are also responsible for error detection.

[0101] Similar to the functionality described in connection with the downlink transmission by the base station 304, the one or more processors 332 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression/decompression, and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ), priority handling, and logical channel prioritization.

[0102] Channel estimates derived by the channel estimator from a reference signal or feedback transmitted by the base station 304 may be used by the transmitter 314 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the transmitter 314 may be provided to different antenna(s) 316. The transmitter 314 may modulate an RF carrier with a respective spatial stream for transmission.

[0103] The uplink transmission is processed at the base station 304 in a manner similar to that described in connection with the receiver function at the UE 302. The receiver 352 receives a signal through its respective antenna(s) 356. The receiver 352 recovers information modulated onto an RF carrier and provides the information to the one or more processors 384.

[0104] In the uplink, the one or more processors 384 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets from the UE 302. IP packets from the one or more processors 384 may be provided to the core network. The one or more processors 384 are also responsible for error detection.

[0105] For convenience, the UE 302, the base station 304, and/or the network entity 306 are shown in FIGS. 3A, 3B, and 3C as including various components that may be configured according to the various examples described herein. It will be appreciated, however, that the illustrated components may have different functionality in different designs. In particular, various components in FIGS. 3A to 3C are optional in alternative configurations and the various aspects include configurations that may vary due to design choice, costs, use of the device, or other considerations. For example, in case of FIG. 3A, a particular implementation of UE 302 may omit the WWAN transceiver(s) 310 (e.g., a wearable device or tablet computer or PC or laptop may have Wi-Fi and/or Bluetooth capability without cellular capability), or may omit the short-range wireless transceiver(s) 320 (e.g., cellular-only, etc.), or may omit the satellite signal receiver 330, or may omit the sensor(s) 344, and so on. In another example, in case of FIG. 3B, a particular implementation of the base station 304 may omit the WWAN transceiver(s) 350 (e.g., a Wi-Fi “hotspot” access point without cellular capability), or may omit the short-range wireless transceiver(s) 360 (e.g., cellular-only, etc.), or may omit the satellite receiver 370, and so on. For brevity, illustration of the various alternative configurations is not provided herein, but would be readily understandable to one skilled in the art.

[0106] The various components of the UE 302, the base station 304, and the network entity 306 may be communicatively coupled to each other over data buses 334, 382, and 392, respectively. In an aspect, the data buses 334, 382, and 392 may form, or be part of, a communication interface of the UE 302, the base station 304, and the network entity 306, respectively. For example, where different logical entities are embodied in the same device (e.g., gNB and location server functionality incorporated into the same base station 304), the data buses 334, 382, and 392 may provide communication between them.

[0107] The components of FIGS. 3 A, 3B, and 3C may be implemented in various ways. In some implementations, the components of FIGS. 3 A, 3B, and 3C may be implemented in one or more circuits such as, for example, one or more processors and/or one or more ASICs (which may include one or more processors). Here, each circuit may use and/or incorporate at least one memory component for storing information or executable code used by the circuit to provide this functionality. For example, some or all of the functionality represented by blocks 310 to 346 may be implemented by processor and memory component(s) of the UE 302 (e.g., by execution of appropriate code and/or by appropriate configuration of processor components). Similarly, some or all of the functionality represented by blocks 350 to 388 may be implemented by processor and memory component(s) of the base station 304 (e.g., by execution of appropriate code and/or by appropriate configuration of processor components). Also, some or all of the functionality represented by blocks 390 to 398 may be implemented by processor and memory component(s) of the network entity 306 (e.g., by execution of appropriate code and/or by appropriate configuration of processor components). For simplicity, various operations, acts, and/or functions are described herein as being performed “by a UE,” “by a base station,” “by a network entity,” etc. However, as will be appreciated, such operations, acts, and/or functions may actually be performed by specific components or combinations of components of the UE 302, base station 304, network entity 306, etc., such as the processors 332, 384, 394, the transceivers 310, 320, 350, and 360, the memories 340, 386, and 396, the equiphase contour component 342, 388, and 398, etc.

[0108] In some designs, the network entity 306 may be implemented as a core network component. In other designs, the network entity 306 may be distinct from a network operator or operation of the cellular network infrastructure (e.g., NG RAN 220 and/or 5GC 210/260). For example, the network entity 306 may be a component of a private network that may be configured to communicate with the UE 302 via the base station 304 or independently from the base station 304 (e.g., over a non-cellular communication link, such as WiFi).

[0109] Various frame structures may be used to support downlink and uplink transmissions between network nodes (e.g., base stations and UEs). FIG. 4 is a diagram 400 illustrating an example frame structure, according to aspects of the disclosure. The frame structure may be a downlink or uplink frame structure. Other wireless communications technologies may have different frame structures and/or different channels.

[0110] LTE, and in some cases NR, utilizes OFDM on the downlink and single-carrier frequency division multiplexing (SC-FDM) on the uplink. Unlike LTE, however, NR has an option to use OFDM on the uplink as well. OFDM and SC-FDM partition the system bandwidth into multiple (K) orthogonal subcarriers, which are also commonly referred to as tones, bins, etc. Each subcarrier may be modulated with data. In general, modulation symbols are sent in the frequency domain with OFDM and in the time domain with SC-FDM. The spacing between adjacent subcarriers may be fixed, and the total number of subcarriers (K) may be dependent on the system bandwidth. For example, the spacing of the subcarriers may be 15 kilohertz (kHz) and the minimum resource allocation (resource block) may be 12 subcarriers (or 180 kHz). Consequently, the nominal FFT size may be equal to 128, 256, 512, 1024, or 2048 for system bandwidth of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), respectively. The system bandwidth may also be partitioned into subbands. For example, a subband may cover 1.08 MHz (i.e., 6 resource blocks), and there may be 1, 2, 4, 8, or 16 subbands for system bandwidth of 1.25, 2.5, 5, 10, or 20 MHz, respectively.

[OHl] LTE supports a single numerology (subcarrier spacing (SCS), symbol length, etc.). In contrast, NR may support multiple numerologies (p), for example, subcarrier spacings of 15 kHz (p=0), 30 kHz (p=l ), 60 kHz (p=2), 120 kHz (p=3), and 240 kHz (p=4) or greater may be available. In each subcarrier spacing, there are 14 symbols per slot. For 15 kHz SCS (p=0), there is one slot per subframe, 10 slots per frame, the slot duration is 1 millisecond (ms), the symbol duration is 66.7 microseconds (ps), and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 50. For 30 kHz SCS (p=l), there are two slots per subframe, 20 slots per frame, the slot duration is 0.5 ms, the symbol duration is 33.3 ps, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 100. For 60 kHz SCS (p=2), there are four slots per subframe, 40 slots per frame, the slot duration is 0.25 ms, the symbol duration is 16.7 ps, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 200. For 120 kHz SCS (p=3), there are eight slots per subframe, 80 slots per frame, the slot duration is 0.125 ms, the symbol duration is 8.33 ps, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 400. For 240 kHz SCS (p=4), there are 16 slots per subframe, 160 slots per frame, the slot duration is 0.0625 ms, the symbol duration is 4.17 ps, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 800.

[0112] In the example of FIG. 4, a numerology of 15 kHz is used. Thus, in the time domain, a 10 ms frame is divided into 10 equally sized subframes of 1 ms each, and each subframe includes one time slot. In FIG. 4, time is represented horizontally (on the X axis) with time increasing from left to right, while frequency is represented vertically (on the Y axis) with frequency increasing (or decreasing) from bottom to top.

[0113] A resource grid may be used to represent time slots, each time slot including one or more time-concurrent resource blocks (RBs) (also referred to as physical RBs (PRBs)) in the frequency domain. The resource grid is further divided into multiple resource elements (REs). An RE may correspond to one symbol length in the time domain and one subcarrier in the frequency domain. In the numerology of FIG. 4, for a normal cyclic prefix, an RB may contain 12 consecutive subcarriers in the frequency domain and seven consecutive symbols in the time domain, for a total of 84 REs. For an extended cyclic prefix, an RB may contain 12 consecutive subcarriers in the frequency domain and six consecutive symbols in the time domain, for a total of 72 REs. The number of bits carried by each RE depends on the modulation scheme.

[0114] Some of the REs may carry reference (pilot) signals (RS). The reference signals may include positioning reference signals (PRS), tracking reference signals (TRS), phase tracking reference signals (PTRS), cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), primary synchronization signals (PSS), secondary synchronization signals (SSS), synchronization signal blocks (SSBs), sounding reference signals (SRS), etc., depending on whether the illustrated frame structure is used for uplink or downlink communication. FIG. 4 illustrates example locations of REs carrying a reference signal (labeled “R”).

[0115] FIG. 5 is a diagram 500 illustrating various downlink channels within an example downlink slot. In FIG. 5, time is represented horizontally (on the X axis) with time increasing from left to right, while frequency is represented vertically (on the Y axis) with frequency increasing (or decreasing) from bottom to top. In the example of FIG. 5, a numerology of 15 kHz is used. Thus, in the time domain, the illustrated slot is one millisecond (ms) in length, divided into 14 symbols.

[0116] In NR, the channel bandwidth, or system bandwidth, is divided into multiple bandwidth parts (BWPs). A BWP is a contiguous set of RBs selected from a contiguous subset of the common RBs for a given numerology on a given carrier. Generally, a maximum of four BWPs can be specified in the downlink and uplink. That is, a UE can be configured with up to four BWPs on the downlink, and up to four BWPs on the uplink. Only one BWP (uplink or downlink) may be active at a given time, meaning the UE may only receive or transmit over one BWP at a time. On the downlink, the bandwidth of each BWP should be equal to or greater than the bandwidth of the SSB, but it may or may not contain the SSB.

[0117] Referring to FIG. 5, a primary synchronization signal (PSS) is used by a UE to determine subframe/symbol timing and a physical layer identity. A secondary synchronization signal (SSS) is used by a UE to determine a physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a PCI. Based on the PCI, the UE can determine the locations of the aforementioned DL-RS. The physical broadcast channel (PBCH), which carries a master information block (MIB), may be logically grouped with the PSS and SSS to form an SSB (also referred to as an SS/PBCH). The MIB provides a number of RBs in the downlink system bandwidth and a system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH, such as system information blocks (SIBs), and paging messages.

[0118] The physical downlink control channel (PDCCH) carries downlink control information (DCI) within one or more control channel elements (CCEs), each CCE including one or more RE group (REG) bundles (which may span multiple symbols in the time domain), each REG bundle including one or more REGs, each REG corresponding to 12 resource elements (one resource block) in the frequency domain and one OFDM symbol in the time domain. The set of physical resources used to carry the PDCCH/DCI is referred to in NR as the control resource set (CORESET). In NR, a PDCCH is confined to a single CORESET and is transmitted with its own DMRS. This enables UE-specific beamforming for the PDCCH.

[0119] In the example of FIG. 5, there is one CORESET per BWP, and the CORESET spans three symbols (although it may be only one or two symbols) in the time domain. Unlike LTE control channels, which occupy the entire system bandwidth, in NR, PDCCH channels are localized to a specific region in the frequency domain (i.e., a CORESET). Thus, the frequency component of the PDCCH shown in FIG. 5 is illustrated as less than a single BWP in the frequency domain. Note that although the illustrated CORESET is contiguous in the frequency domain, it need not be. In addition, the CORESET may span less than three symbols in the time domain.

[0120] The DCI within the PDCCH carries information about uplink resource allocation (persistent and non-persistent) and descriptions about downlink data transmitted to the UE, referred to as uplink and downlink grants, respectively. More specifically, the DCI indicates the resources scheduled for the downlink data channel (e.g., PDSCH) and the uplink data channel (e.g., physical uplink shared channel (PUSCH)). Multiple (e.g., up to eight) DCIs can be configured in the PDCCH, and these DCIs can have one of multiple formats. For example, there are different DCI formats for uplink scheduling, for downlink scheduling, for uplink transmit power control (TPC), etc. A PDCCH may be transported by 1, 2, 4, 8, or 16 CCEs in order to accommodate different DCI payload sizes or coding rates.

[0121] FIG. 6 is a diagram 600 illustrating various uplink channels within an example uplink slot. In FIG. 6, time is represented horizontally (on the X axis) with time increasing from left to right, while frequency is represented vertically (on the Y axis) with frequency increasing (or decreasing) from bottom to top. In the example of FIG. 6, a numerology of 15 kHz is used. Thus, in the time domain, the illustrated slot is one millisecond (ms) in length, divided into 14 symbols.

[0122] A random-access channel (RACH), also referred to as a physical random-access channel (PRACH), may be within one or more slots within a frame based on the PRACH configuration. The PRACH may include six consecutive RB pairs within a slot. The PRACH allows the UE to perform initial system access and achieve uplink synchronization. A physical uplink control channel (PUCCH) may be located on edges of the uplink system bandwidth. The PUCCH carries uplink control information (UCI), such as scheduling requests, CSI reports, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and HARQ ACK/NACK feedback. The physical uplink shared channel (PUSCH) carries data, and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and/or UCI.

[0123] FIG. 7 illustrates time and frequency resources used for sidelink communication. A timefrequency grid 700 is divided into subchannels in the frequency domain and is divided into time slots in the time domain. Each subchannel comprises a number (e.g., 10, 15, 20, 25, 50, 75, or 100) of physical resource blocks (PRBs), and each slot contains a number (e.g., 14) of OFDM symbols. A sidelink communication can be (pre)configured to occupy fewer than 14 symbols in a slot. The first symbol of the slot is repeated on the preceding symbol for automatic gain control (AGC) settling. The example slot shown in FIG. 4 contains a physical sidelink control channel (PSCCH) portion and a physical sidelink shared channel (PSSCH) portion, with a gap symbol following the PSCCH. PSCCH and PSSCH are transmitted in the same slot.

[0124] Sidelink communications take place within transmission or reception resource pools. Sidelink communications occupy one slot and one or more subchannels. Some slots are not available for sidelink, and some slots contain feedback resources. Sidelink communication can be preconfigured (e.g., preloaded on a UE) or configured (e.g., by a base station via RRC).

[0125] FIG. 8 is a diagram of an example PRS configuration 800 for the PRS transmissions of a given base station, according to aspects of the disclosure. In FIG. 8, time is represented horizontally, increasing from left to right. Each long rectangle represents a slot and each short (shaded) rectangle represents an OFDM symbol. In the example of FIG. 8, a PRS resource set 810 (labeled “PRS resource set 1”) includes two PRS resources, a first PRS resource 812 (labeled “PRS resource 1”) and a second PRS resource 814 (labeled “PRS resource 2”). The base station transmits PRS on the PRS resources 812 and 814 of the PRS resource set 810.

[0126] The PRS resource set 810 has an occasion length (N PRS) of two slots and a periodicity (T PRS) of, for example, 160 slots or 160 milliseconds (ms) (for 15 kHz subcarrier spacing). As such, both the PRS resources 812 and 814 are two consecutive slots in length and repeat every T PRS slots, starting from the slot in which the first symbol of the respective PRS resource occurs. In the example of FIG. 8, the PRS resource 812 has a symbol length (N symb) of two symbols, and the PRS resource 814 has a symbol length (N_symb) of four symbols. The PRS resource 812 and the PRS resource 814 may be transmitted on separate beams of the same base station.

[0127] Each instance of the PRS resource set 810, illustrated as instances 820a, 820b, and 820c, includes an occasion of length ‘2’ (i.e., N_PRS=2) for each PRS resource 812, 814 of the PRS resource set. The PRS resources 812 and 814 are repeated every T PRS slots up to the muting sequence periodicity T REP. As such, a bitmap of length T REP would be needed to indicate which occasions of instances 820a, 820b, and 820c of PRS resource set 810 are muted (i.e., not transmitted).

[0128] In an aspect, there may be additional constraints on the PRS configuration 800. For example, for all PRS resources (e.g., PRS resources 812, 814) of a PRS resource set (e.g., PRS resource set 810), the base station can configure the following parameters to be the same: (a) the occasion length (N_PRS), (b) the number of symbols (N_symb), (c) the comb type, and/or (d) the bandwidth. In addition, for all PRS resources of all PRS resource sets, the subcarrier spacing and the cyclic prefix can be configured to be the same for one base station or for all base stations. Whether it is for one base station or all base stations may depend on the UE’s capability to support the first and/or second option.

[0129] FIG. 9 is a diagram 900 illustrating an example PRS configuration for two TRPs (labeled “TRP1” and “TRP2”) operating in the same positioning frequency layer (labeled “Positioning Frequency Layer 1”), according to aspects of the disclosure. For a positioning session, a UE may be provided with assistance data indicating the illustrated PRS configuration. In the example of FIG. 9, the first TRP (“TRP1”) is associated with (e.g., transmits) two PRS resource sets, labeled “PRS Resource Set 1” and “PRS Resource Set 2,” and the second TRP (“TRP2”) is associated with one PRS resource set, labeled “PRS Resource Set 3.” Each PRS resource set comprises at least two PRS resources. Specifically, the first PRS resource set (“PRS Resource Set 1”) includes PRS resources labeled “PRS Resource 1” and “PRS Resource 2,” the second PRS resource set (“PRS Resource Set 2”) includes PRS resources labeled “PRS Resource 3” and “PRS Resource 4,” and the third PRS resource set (“PRS Resource Set 3”) includes PRS resources labeled “PRS Resource 5” and “PRS Resource 6.”

[0130] NR supports a number of cellular network-based positioning technologies, including downlink-based, uplink-based, and downlink-and-uplink-based positioning methods. Downlink-based positioning methods include observed time difference of arrival (OTDOA) in LTE, downlink time difference of arrival (DL-TDOA) in NR, and downlink angle-of-departure (DL-AoD) in NR. FIG. 10 illustrates examples of various positioning methods, according to aspects of the disclosure. In an OTDOA or DL-TDOA positioning procedure, illustrated by scenario 1010, a UE measures the differences between the times of arrival (ToAs) of reference signals (e.g., positioning reference signals (PRS)) received from pairs of base stations, referred to as reference signal time difference (RSTD) or time difference of arrival (TDOA) measurements, and reports them to a positioning entity. More specifically, the UE receives the identifiers (IDs) of a reference base station (e.g., a serving base station) and multiple non-reference base stations in assistance data. The UE then measures the RSTD between the reference base station and each of the non-reference base stations. Based on the known locations of the involved base stations and the RSTD measurements, the positioning entity (e.g., the UE for UE-based positioning or a location server for UE-assisted positioning) can estimate the UE’s location.

[0131] For DL-AoD positioning, illustrated by scenario 1020, the positioning entity uses a beam report from the UE of received signal strength measurements of multiple downlink transmit beams to determine the angle(s) between the UE and the transmitting base station(s). The positioning entity can then estimate the location of the UE based on the determined angle(s) and the known location(s) of the transmitting base station(s).

[0132] Uplink-based positioning methods include uplink time difference of arrival (UL-TDOA) and uplink angle-of-arrival (UL-AoA). UL-TDOA is similar to DL-TDOA, but is based on uplink reference signals (e.g., sounding reference signals (SRS)) transmitted by the UE. For UL-AoA positioning, one or more base stations measure the received signal strength of one or more uplink reference signals (e.g., SRS) received from a UE on one or more uplink receive beams. The positioning entity uses the signal strength measurements and the angle(s) of the receive beam(s) to determine the angle(s) between the UE and the base station(s). Based on the determined angle(s) and the known location(s) of the base station(s), the positioning entity can then estimate the location of the UE.

[0133] Downlink-and-uplink-based positioning methods include enhanced cell-ID (E-CID) positioning and multi-round-trip-time (RTT) positioning (also referred to as “multi-cell RTT” and “multi-RTT”). In an RTT procedure, a first entity (e.g., a base station or a UE) transmits a first RTT-related signal (e.g., a PRS or SRS) to a second entity (e.g., a UE or base station), which transmits a second RTT-related signal (e.g., an SRS or PRS) back to the first entity. Each entity measures the time difference between the time of arrival (ToA) of the received RTT-related signal and the transmission time of the transmitted RTT-related signal. This time difference is referred to as a reception-to-transmission (Rx- Tx) time difference. The Rx-Tx time difference measurement may be made, or may be adjusted, to include only a time difference between nearest subframe boundaries for the received and transmitted signals. Both entities may then send their Rx-Tx time difference measurement to a location server (e.g., an LMF 270 or a location management functionality), which calculates the round trip propagation time (i.e., RTT) between the two entities from the two Rx-Tx time difference measurements (e.g., as the sum of the two Rx-Tx time difference measurements). Alternatively, one entity may send its Rx-Tx time difference measurement to the other entity, which then calculates the RTT. The distance between the two entities can be determined from the RTT and the known signal speed (e.g., the speed of light). For multi-RTT positioning, illustrated by scenario 1030, a first entity (e.g., a UE or base station) performs an RTT positioning procedure with multiple second entities (e.g., multiple base stations or UEs) to enable the location of the first entity to be determined (e.g., using multilateration) based on distances to, and the known locations of, the second entities. RTT and multi-RTT methods can be combined with other positioning techniques, such as UL-AoA and DL-AoD, to improve location accuracy, as illustrated by scenario 1040.

[0134] The E-CID positioning method is based on radio resource management (RRM) measurements. In E-CID, the UE reports the serving cell ID, the timing advance (TA), and the identifiers, estimated timing, and signal strength of detected neighbor base stations. The location of the UE is then estimated based on this information and the known locations of the base station(s). [0135] To assist positioning operations, a location server (e.g., location server 230, LMF 270, SLP 272) may provide assistance data to the UE. For example, the assistance data may include identifiers of the base stations (or the cells/TRPs of the base stations) from which to measure reference signals, the reference signal configuration parameters (e.g., the number of consecutive positioning subframes, periodicity of positioning subframes, muting sequence, frequency hopping sequence, reference signal identifier, reference signal bandwidth, etc.), and/or other parameters applicable to the particular positioning method. Alternatively, the assistance data may originate directly from the base stations themselves (e.g., in periodically broadcasted overhead messages, etc.). In some cases, the UE may be able to detect neighbor network nodes itself without the use of assistance data.

[0136] In the case of an OTDOA or DL-TDOA positioning procedure, the assistance data may further include an expected RSTD value and an associated uncertainty, or search window, around the expected RSTD. In some cases, the value range of the expected RSTD may be +/- 500 microseconds (ps). In some cases, when any of the resources used for the positioning measurement are in FR1, the value range for the uncertainty of the expected RSTD may be +/- 32 ps. In other cases, when all of the resources used for the positioning measurement(s) are in FR2, the value range for the uncertainty of the expected RSTD may be +/- 8 ps.

[0137] A location estimate may be referred to by other names, such as a position estimate, location, position, position fix, fix, or the like. A location estimate may be geodetic and comprise coordinates (e.g., latitude, longitude, and possibly altitude) or may be civic and comprise a street address, postal address, or some other verbal description of a location. A location estimate may further be defined relative to some other known location or defined in absolute terms (e.g., using latitude, longitude, and possibly altitude). A location estimate may include an expected error or uncertainty (e.g., by including an area or volume within which the location is expected to be included with some specified or default level of confidence).

[0138] In NR, there may not be precise timing synchronization across the network. Instead, it may be sufficient to have coarse time-synchronization across base stations (e.g., within a cyclic prefix (CP) duration of the orthogonal frequency division multiplexing (OFDM) symbols). RTT-based methods generally only need coarse timing synchronization, and as such, are a preferred positioning method in NR. [0139] FIG. 11 illustrates an example wireless communications system 1100, according to aspects of the disclosure. In the example of FIG. 11, a UE 1104 (e.g., any of the UEs described herein) is attempting to calculate an estimate of its location, or assist another entity (e.g., a base station or core network component, another UE, a location server, a third party application, etc.) to calculate an estimate of its location. The UE 1104 may transmit and receive wireless signals to and from a plurality of network nodes (labeled “Node”) 1102-1, 1102-2, and 1102-3 (collectively, network nodes 1102). The network nodes 1102 may include one or more base stations (e.g., any of the base stations described herein), one or more reconfigurable intelligent displays (RIS), one or more positioning beacons, one or more UEs (e.g., connected over sidelinks), etc.

[0140] In a network-centric RTT positioning procedure the serving base station (e.g., one of network nodes 1102) instructs the UE 1104 to measure RTT measurement signals (e.g., PRS) from two or more neighboring network nodes 1102 (and typically the serving base station, as at least three network nodes 1102 are needed for a two-dimensional location estimate). The involved network nodes 1102 transmit RTT measurement signals on low reuse resources (e.g., resources used by the network nodes 1102 to transmit system information, where the network nodes 1102 are base stations) allocated by the network (e.g., location server 230, LMF 270, SLP 272). The UE 1104 records the arrival time (also referred to as the receive time, reception time, time of reception, or time of arrival) of each RTT measurement signal relative to the UE’s 1104 current downlink timing (e.g., as derived by the UE 1104 from a downlink signal received from its serving base station), and transmits a common or individual RTT response signal (e.g., SRS) to the involved network nodes 1102 on resources allocated by its serving base station. The UE 1104, if it not the positioning entity, reports a UE reception-to-transmission (Rx-Tx) time difference measurement to the positioning entity. The UE Rx-Tx time difference measurement indicates the time difference between the arrival time of each RTT measurement signal at the UE 1104 and the transmission time(s) of the RTT response signal(s). Each involved network node 1102 also reports, to the positioning entity, a network node Rx-Tx time difference measurement (also referred to as a base station (BS) or gNB Rx-Tx time difference measurement), which indicates the difference between the transmission time of the RTT measurement signal and the reception time of the RTT response signal. [0141] A UE-centric RTT positioning procedure is similar to the network-based procedure, except that the UE 1104 transmits uplink RTT measurement signal(s) (e.g., on resources allocated by the serving base station). The uplink RTT measurement signal(s) are measured by multiple network nodes 1102 in the neighborhood of the UE 1104. Each involved network node 1102 responds with a downlink RTT response signal and reports a network node Rx-Tx time difference measurement to the positioning entity. The network node Rx-Tx time difference measurement indicates the time difference between the arrival time of the RTT measurement signal at the network node 1102 and the transmission time of the RTT response signal. The UE 1104, if it is not the positioning entity, reports, for each network node 1102, a UE Rx-Tx time difference measurement that indicates the difference between the transmission time of the RTT measurement signal and the reception time of the RTT response signal.

[0142] In order to determine the location (x, y) of the UE 1104, the positioning entity needs to know the locations of the network nodes 1102, which may be represented in a reference coordinate system as (x_k, y_y), where k=l, 2, 3 in the example of FIG. 11. Where the UE 1104 is the positioning entity, a location server with knowledge of the network geometry (e.g., location server 230, LMF 270, SLP 272) may provide the locations of the involved network nodes 1102 to the UE 1104.

[0143] The positioning entity determines each distance 1110 (d_k, where k=l, 2, 3) between the UE 1104 and the respective network node 1102 based on the UE Rx-Tx and network node Rx-Tx time difference measurements and the speed of light, as described further below with reference to FIG. 12. Specifically, in the example of FIG. 11, the distance 1110-1 between the UE 1104 and the network node 1102-1 is d_l, the distance 1110-2 between the UE 1104 and the network node 1102-2 is d_2, and the distance 1110-3 between the UE 1104 and the network node 1102-3 is d_3. Once each distance 1110 is determined, the positioning entity can solve for the location (x, y) of the UE 1104 by using a variety of known geometric techniques, such as trilateration. From FIG. 11, it can be seen that the location of the UE 1104 ideally lies at the common intersection of three semicircles, each semicircle being defined by radius dk and center (x_k, y_k), where k=l, 2, 3.

[0144] FIG. 12 is a diagram 1200 showing example timings of RTT measurement signals exchanged between a network node 1202 (labeled “Node”) and a UE 1204, according to aspects of the disclosure. The UE 1204 may be any of the UEs described herein. The network node 1202 may be a base station (e.g., any of the base stations described herein), an RIS, a positioning beacon, another UE (e.g., connected over a sidelink), or the like.

[0145] In the example of FIG. 12, the network node 1202 (labeled “BS”) sends an RTT measurement signal 1210 (e.g., PRS) to the UE 1204 at time T_l. The RTT measurement signal 1210 has some propagation delay T_Prop as it travels from the network node 1202 to the UE 1204. At time T_2 (the reception time of the RTT measurement signal 1210 at the UE 1204), the UE 1204 measures the RTT measurement signal 1210. After some UE processing time, the UE 1204 transmits an RTT response signal 1220 (e.g., SRS) at time T_3. After the propagation delay T Prop, the network node 1202 measures the RTT response signal 1220 from the UE 1204 at time T_4 (the reception time of the RTT response signal 1220 at the network node 1202).

[0146] The UE 1204 reports the difference between time T_3 and time T_2 (i.e., the UE’s 1204 Rx-Tx time difference measurement, shown as UE_Rx-Tx 1212) to the positioning entity. Similarly, the network node 1202 reports the difference between time T_4 and time T_1 (i.e., the network node’s 1202 Rx-Tx time difference measurement, shown as Node_Rx- Tx 1222) to the positioning entity. Using these measurements and the known speed of light, the positioning entity can calculate the distance to the UE 1204 as d = l/2*c*(Node_Rx-Tx - UE_Rx-Tx) = l/2*c*(T_4 - T_l) - l/2*c*(T_3 - T_2), where c is the speed of light.

[0147] Based on the known location of the network node 1202 and the distance between the UE 1204 and the network node 1202 (and at least two other network nodes 1202), the positioning entity can calculate the location of the UE 1204. As shown in FIG. 11, the location of the UE 1204 lies at the common intersection of three semicircles, each semicircle being defined by a radius of the distance between the UE 1204 and a respective network node 1202.

[0148] In an aspect, the positioning entity may calculate the UE’s 1104/1204 location using a two-dimensional coordinate system; however, the aspects disclosed herein are not so limited, and may also be applicable to determining locations using a three-dimensional coordinate system, if the extra dimension is desired. Additionally, while FIG. 11 illustrates one UE 1104 and three network nodes 1102 and FIG. 12 illustrates one UE 1204 and one network node 1202, as will be appreciated, there may be more UEs 1104/1204 and more network nodes 1102/1202. [0149] FIG. 13 is a diagram 1300 showing example timings of RTT measurement signals exchanged between a network node 1302 and a UE 1304, according to aspects of the disclosure. The diagram 1300 is similar to the diagram 1200, except that it includes processing delays that may occur at both the network node 1302 (labeled “Node”) and the UE 1304 when transmitting and receiving the RTT measurement and response signals. The network node 1302 may be a base station (e.g., any of the base stations), an RIS (e.g., RIS 410), another UE (e.g., any of the UEs described herein), or other network node capable of performing an RTT positioning procedure. As a specific example, the network node 1302 and the UE 1304 may correspond to the base station 1202 and the UE 1204 in FIG. 12.

[0150] Referring now to potential processing delays, at the network node 1302, there is a transmission delay 1314 between the time T_1 that the network node’s 1302 baseband (labeled “BB”) generates the RTT measurement signal 1310 (e.g., a PRS) and the time T_2 that the network node’s 1302 antenna(s) (labeled “Ant”) transmit the RTT measurement signal 1310. At the UE 1304, there is a reception delay 1316 between the time T_3 that the UE’s 604 antenna(s) (labeled “Ant”) receive the RTT measurement signal 1310 and the time T_4 that the UE’s 1304 baseband (labeled “BB”) processes the RTT measurement signal 1310.

[0151] Similarly, for the RTT response signal 1320 (e.g., an SRS), there is a transmission delay 1326 between the time T_5 that the UE’s 1304 baseband generates the RTT response signal 1320 and the time T_6 that the UE’s 1304 antenna(s) transmit the RTT response signal 1320. At the network node 1302, there is a reception delay 1324 between the time T_7 that the network node’s 1302 antenna(s) receive the RTT response signal 1320 and the time T_8 that the network node’s 1302 baseband processes the RTT response signal 1320.

[0152] The difference between times T_2 and T_1 (i.e., transmission delay 1314) and times T_8 and T_7 (i.e., reception delay 1324) is referred to as the network node’s 1302 “group delay.” The difference between times T_4 and T_3 (i.e., reception delay 1316) and times T_6 and T_5 (i.e., transmission delay 1326) is referred to as the UE’s 1304 “group delay.” The group delay includes a hardware group delay, a group delay attributable to software/firmware, or both. More specifically, although software and/or firmware may contribute to group delay, the group delay is primarily due to internal hardware delays between the baseband and the antenna(s) of the network node 1302 and the UE 1304. [0153] As shown in FIG. 13, because of the reception delay 1316 and the transmission delay 1326, the UE’s 1304 Rx-Tx time difference measurement 1312 does not represent the difference between the actual reception time at time T_3 and the actual transmission time at time T_6. Similarly, because of the transmission delay 1314 and the reception delay 1324, the network node’s 1302 Rx-Tx time difference measurement 1322 does not represent the difference between the actual transmission time at time T_2 and the actual reception time at time T_7. Thus, as shown, group delays, such as reception delays 1324 and 1316 and transmission delays 1314 and 1326, can contribute to timing errors and/or calibration errors that can impact RTT measurements, as well as other measurements, such as TDOA, RSTD, etc. This can in turn can impact positioning performance. For example, in some designs, a 10 ns error will introduce three meters of error in the final location estimate.

[0154] In some cases, the UE 1304 can calibrate its group delay and compensate for it so that the UE Rx-Tx time difference measurement 1312 reflects the actual reception and transmission times from its antenna(s). Alternatively, the UE 1304 can report its group delay to the positioning entity (if not the UE 1304), which can then subtract the group delay from the UE Rx-Tx time difference measurement 1312 when determining the final distance between the network node 1302 and the UE 1304. Similarly, the network node 1302 may be able to compensate for its group delay in the network node Rx-Tx time difference measurement 1322, or simply report the group delay to the positioning entity.

[0155] FIG. 14 illustrates a time difference of arrival (TDOA)-based positioning procedure in an example wireless communications system 1400, according to aspects of the disclosure. The TDOA-based positioning procedure may be an observed time difference of arrival (OTDOA) positioning procedure, as in LTE, or a downlink time difference of arrival (DL- TDOA) positioning procedure, as in 5GNR. In the example of FIG. 14, aUE 1404 (e.g., any of the UEs described herein) is attempting to calculate an estimate of its location (referred to as “UE-based” positioning), or assist another entity (e.g., a base station or core network component, another UE, a location server, a third party application, etc.) to calculate an estimate of its location (referred to as “UE-assisted” positioning). The UE 1404 may communicate with (e.g., send information to and receive information from) one or more of a plurality of base stations 1402 (e.g., any combination of base stations described herein), labeled “BS1” 1402-1, “BS2” 1402-2, and “BS3” 1402-3. [0156] To support location estimates, the base stations 1402 may be configured to broadcast positioning reference signals (e.g., PRS, TRS, CRS, CSI-RS, etc.) to a UE 1404 in their coverage areas to enable the UE 1404 to measure characteristics of such reference signals. In a TDOA-based positioning procedure, the UE 1404 measures the time difference, known as the reference signal time difference (RSTD) or TDOA, between specific downlink reference signals (e.g., PRS, TRS, CRS, CSI-RS, etc.) transmitted by different pairs of base stations 1402, and either reports these RSTD measurements to a location server (e.g., location server 230, LMF 270, SLP 272) or computes a location estimate itself from the RSTD measurements.

[0157] Generally, RSTDs are measured between a reference cell (e.g., a cell supported by base station 1402-1 in the example of FIG. 14) and one or more neighbor cells (e.g., cells supported by base stations 1402-2 and 1402-3 in the example of FIG. 14). The reference cell remains the same for all RSTDs measured by the UE 1404 for any single positioning use of TDOA and would typically correspond to the serving cell for the UE 1404 or another nearby cell with good signal strength at the UE 1404. In an aspect, the neighbor cells would normally be cells supported by base stations different from the base station for the reference cell, and may have good or poor signal strength at the UE 1404. The location computation can be based on the measured RSTDs and knowledge of the involved base stations’ 1402 locations and relative transmission timing (e.g., regarding whether base stations 1402 are accurately synchronized or whether each base station 1402 transmits with some known time offset relative to other base stations 1402).

[0158] To assist TDOA-based positioning operations, the location server (e.g., location server 230, LMF 270, SLP 272) may provide assistance data to the UE 1404 for the reference cell and the neighbor cells relative to the reference cell. For example, the assistance data may include identifiers (e.g., PCI, VCI, CGI, etc.) for each cell of a set of cells that the UE 1404 is expected to measure (here, cells supported by the base stations 1402). The assistance data may also provide the center channel frequency of each cell, various reference signal configuration parameters (e.g., the number of consecutive positioning slots, periodicity of positioning slots, muting sequence, frequency hopping sequence, reference signal identifier, reference signal bandwidth), and/or other cell related parameters applicable to TDOA-based positioning procedures. The assistance data may also indicate the serving cell for the UE 1404 as the reference cell. [0159] In some cases, the assistance data may also include “expected RSTD” parameters, which provide the UE 1404 with information about the RSTD values the UE 1404 is expected to measure between the reference cell and each neighbor cell at its current location, together with an uncertainty of the expected RSTD parameter. The expected RSTD, together with the associated uncertainty, may define a search window for the UE 1404 within which the UE 1404 is expected to measure the RSTD value. In some cases, the value range of the expected RSTD may be +/- 500 microseconds (ps). In some cases, when any of the resources used for the positioning measurement are in FR1, the value range for the uncertainty of the expected RSTD may be +/- 32 ps. In other cases, when all of the resources used for the positioning measurement(s) are in FR2, the value range for the uncertainty of the expected RSTD may be +/- 8 ps.

[0160] TDOA assistance information may also include positioning reference signal configuration information parameters, which allow the UE 1404 to determine when a positioning reference signal occasion will occur on signals received from various neighbor cells relative to positioning reference signal occasions for the reference cell, and to determine the reference signal sequence transmitted from the various cells in order to measure a reference signal time of arrival (ToA) or RSTD.

[0161] In an aspect, while the location server (e.g., location server 230, LMF 270, SLP 272) may send the assistance data to the UE 1404, alternatively, the assistance data can originate directly from the base stations 1402 themselves (e.g., in periodically broadcasted overhead messages, etc.). Alternatively, the UE 1404 can detect neighbor base stations itself without the use of assistance data.

[0162] The UE 1404 (e.g., based in part on the assistance data, if provided) can measure and (optionally) report the RSTDs between reference signals received from pairs of base stations 1402. Using the RSTD measurements, the known absolute or relative transmission timing of each base station 1402, and the known location(s) of the reference and neighbor base stations 1402, the network (e.g., location server 230/LMF 270/SLP 272, a base station 1402) or the UE 1404 can estimate the location of the UE 1404. More particularly, the RSTD for a neighbor cell “k” relative to a reference cell “Ref’ may be given as (ToA k - ToA Ref). In the example of FIG. 14, the measured RSTDs between the reference cell of base station 1402-1 and the cells of neighbor base stations 1402-2 and 1402-3 may be represented as T2 - T1 and T3 - Tl, where Tl, T2, and T3 represent the ToA of a reference signal from the base station 1402-1, 1402-2, and 1402-3, respectively. The UE 1404 (if it is not the positioning entity) may then send the RSTD measurements to the location server or other positioning entity. Using (i) the RSTD measurements, (ii) the known absolute or relative transmission timing of each base station 1402, (iii) the known location(s) of the base stations 1402, and/or (iv) directional reference signal characteristics, such as the direction of transmission, the UE’s 1404 location may be determined (either by the UE 1404 or the location server).

[0163] In an aspect, the location estimate may specify the location of the UE 1404 in a two- dimensional (2D) coordinate system; however, the aspects disclosed herein are not so limited, and may also be applicable to determining location estimates using a three- dimensional (3D) coordinate system, if the extra dimension is desired. Additionally, while FIG. 14 illustrates one UE 1404 and three base stations 1402, as will be appreciated, there may be more UEs 1404 and more base stations 1402.

[0164] Still referring to FIG. 14, when the UE 1404 obtains a location estimate using RSTDs, the necessary additional data (e.g., the base stations’ 1402 locations and relative transmission timing) may be provided to the UE 1404 by the location server. In some implementations, a location estimate for the UE 1404 may be obtained (e.g., by the UE 1404 itself or by the location server) from RSTDs and from other measurements made by the UE 1404 (e.g., measurements of signal timing from global positioning system (GPS) or other global navigation satellite system (GNSS) satellites). In these implementations, known as hybrid positioning, the RSTD measurements may contribute towards obtaining the UE’s 1404 location estimate but may not wholly determine the location estimate.

[0165] In addition to the downlink-based, uplink-based, and downlink-and-uplink-based positioning methods, NR supports various sidelink positioning techniques. For example, link-level ranging signals can be used to estimate the distance between pairs of V-UEs or between a V-UE and a roadside unit (RSU), similar to a round-trip-time (RTT) positioning procedure.

[0166] FIG. 15 illustrates an example wireless communication system 1500 in which a V-UE 1504 is exchanging ranging signals with an RSU 1510 and another V-UE 1506, according to aspects of the disclosure. As illustrated in FIG. 15, a wideband (e.g., FR1) ranging signal (e.g., a Zadoff Chu sequence) is transmitted by both end points (e.g., V-UE 1504 and RSU 1510 and V-UE 1504 and V-UE 1506). In an aspect, the ranging signals may be sidelink positioning reference signals (SL-PRS) transmitted by the involved V-UEs 1504 and 1506 on uplink resources. On receiving a ranging signal from a transmitter (e.g., V-UE 1504), the receiver (e.g., RSU 1510 and/or V-UE 1506) responds by sending a ranging signal that includes a measurement of the difference between the reception time of the ranging signal and the transmission time of the response ranging signal, referred to as the reception-to-transmission (Rx-Tx) time difference measurement of the receiver.

[0167] Upon receiving the response ranging signal, the transmitter (or other positioning entity) can calculate the RTT between the transmitter and the receiver based on the receiver’s Rx-Tx time difference measurement and a measurement of the difference between the transmission time of the first ranging signal and the reception time of the response ranging signal (referred to as the transmission-to-reception (Tx-Rx) time difference measurement of the transmitter). The transmitter (or other positioning entity) uses the RTT and the speed of light to estimate the distance between the transmitter and the receiver. If one or both of the transmitter and receiver are capable of beamforming, the angle between the V-UEs 1504 and 1506 may also be able to be determined. In addition, if the receiver provides its global positioning system (GPS) location in the response ranging signal, the transmitter (or other positioning entity) may be able to determine an absolute location of the transmitter, as opposed to a relative location of the transmitter with respect to the receiver.

[0168] As will be appreciated, ranging accuracy improves with the bandwidth of the ranging signals. Specifically, a higher bandwidth can better separate the different multipaths of the ranging signals.

[0169] Note that this positioning procedure assumes that the involved V-UEs are time- synchronized (i.e., their system frame time is the same as, or has a known offset relative to, the other V-UE(s)). In addition, although FIG. 15 illustrates two V-UEs, as will be appreciated, they need not be V-UEs, and may instead be any other type of UE capable of sidelink communication.

[0170] FIG. 16 is a diagram 1600 illustrating a base station (BS) 1602 (which may correspond to any of the base stations described herein) in communication with a UE 1604 (which may correspond to any of the UEs described herein). Referring to FIG. 16, the base station 1602 may transmit a beamformed signal to the UE 1604 on one or more transmit beams 1602a, 1602b, 1602c, 1602d, 1602e, 1602f, 1602g, 1602h, each having a beam identifier that can be used by the UE 1604 to identify the respective beam. Where the base station 1602 is beamforming towards the UE 1604 with a single array of antennas (e.g., a single TRP/cell), the base station 1602 may perform a “beam sweep” by transmitting first beam 1602a, then beam 1602b, and so on until lastly transmitting beam 1602h. Alternatively, the base station 1602 may transmit beams 1602a - 1602h in some pattern, such as beam 1602a, then beam 1602h, then beam 1602b, then beam 1602g, and so on. Where the base station 1602 is beamforming towards the UE 1604 using multiple arrays of antennas (e.g., multiple TRPs/cells), each antenna array may perform a beam sweep of a subset of the beams 1602a - 1602h. Alternatively, each of beams 1602a - 1602h may correspond to a single antenna or antenna array.

[0171] FIG. 16 further illustrates the paths 1612c, 1612d, 1612e, 1612f, and 1612g followed by the beamformed signal transmitted on beams 1602c, 1602d, 1602e, 1602f, and 1602g, respectively. Each path 1612c, 1612d, 1612e, 1612f, 1612g may correspond to a single “multipath” or, due to the propagation characteristics of radio frequency (RF) signals through the environment, may be comprised of a plurality (a cluster) of “multipaths.” Note that although only the paths for beams 1602c - 1602g are shown, this is for simplicity, and the signal transmitted on each of beams 1602a - 1602h will follow some path. In the example shown, the paths 1612c, 1612d, 1612e, and 1612f are straight lines, while path 1612g reflects off an obstacle 1620 (e.g., a building, vehicle, terrain feature, etc.).

[0172] The UE 1604 may receive the beamformed signal from the base station 1602 on one or more receive beams 1604a, 1604b, 1604c, 1604d. Note that for simplicity, the beams illustrated in FIG. 16 represent either transmit beams or receive beams, depending on which of the base station 1602 and the UE 1604 is transmitting and which is receiving. Thus, the UE 1604 may also transmit a beamformed signal to the base station 1602 on one or more of the beams 1604a - 1604d, and the base station 1602 may receive the beamformed signal from the UE 1604 on one or more of the beams 1602a - 1602h.

[0173] In an aspect, the base station 1602 and the UE 1604 may perform beam training to align the transmit and receive beams of the base station 1602 and the UE 1604. For example, depending on environmental conditions and other factors, the base station 1602 and the UE 1604 may determine that the best transmit and receive beams are 1602d and 1604b, respectively, or beams 1602e and 1604c, respectively. The direction of the best transmit beam for the base station 1602 may or may not be the same as the direction of the best receive beam, and likewise, the direction of the best receive beam for the UE 1604 may or may not be the same as the direction of the best transmit beam. Note, however, that aligning the transmit and receive beams is not necessary to perform a downlink angle-of- departure (DL-AoD) or uplink angle-of-arrival (UL-AoA) positioning procedure.

[0174] To perform a DL-AoD positioning procedure, the base station 1602 may transmit reference signals (e.g., PRS, CRS, TRS, CSI-RS, PSS, SSS, etc.) to the UE 1604 on one or more of beams 1602a - 1602h, with each beam having a different transmit angle. The different transmit angles of the beams will result in different received signal strengths (e.g., RSRP, RSRQ, SINR, etc.) at the UE 1604. Specifically, the received signal strength will be lower for transmit beams 1602a - 1602h that are further from the line of sight (LOS) path 1610 between the base station 1602 and the UE 1604 than for transmit beams 1602a - 1602h that are closer to the LOS path 1610.

[0175] In the example of FIG. 16, if the base station 1602 transmits reference signals to the UE 1604 on beams 1602c, 1602d, 1602e, 1602f, and 1602g, then transmit beam 1602e is best aligned with the LOS path 1610, while transmit beams 1602c, 1602d, 1602f, and 1602g are not. As such, beam 1602e is likely to have a higher received signal strength at the UE 1604 than beams 1602c, 1602d, 1602f, and 1602g. Note that the reference signals transmitted on some beams (e.g., beams 1602c and/or 16021) may not reach the UE 1604, or energy reaching the UE 1604 from these beams may be so low that the energy may not be detectable or at least can be ignored.

[0176] The UE 1604 can report the received signal strength, and optionally, the associated measurement quality, of each measured transmit beam 1602c - 1602g to the base station 1602, or alternatively, the identity of the transmit beam having the highest received signal strength (beam 1602e in the example of FIG. 16). Alternatively or additionally, if the UE 1604 is also engaged in a round-trip-time (RTT) or time-difference of arrival (TDOA) positioning session with at least one base station 1602 or a plurality of base stations 1602, respectively, the UE 1604 can report reception-to-transmission (Rx-Tx) time difference or reference signal time difference (RSTD) measurements (and optionally the associated measurement qualities), respectively, to the serving base station 1602 or other positioning entity. In any case, the positioning entity (e.g., the base station 1602, a location server, a third-party client, UE 1604, etc.) can estimate the angle from the base station 1602 to the UE 1604 as the AoD of the transmit beam having the highest received signal strength at the UE 1604, here, transmit beam 1602e.

[0177] In one aspect of DL-AoD-based positioning, where there is only one involved base station 1602, the base station 1602 and the UE 1604 can perform a round-trip-time (RTT) procedure to determine the distance between the base station 1602 and the UE 1604. Thus, the positioning entity can determine both the direction to the UE 1604 (using DL- AoD positioning) and the distance to the UE 1604 (using RTT positioning) to estimate the location of the UE 1604. Note that the AoD of the transmit beam having the highest received signal strength does not necessarily he along the LOS path 1610, as shown in FIG. 16. However, for DL-AoD-based positioning purposes, it is assumed to do so.

[0178] In another aspect of DL-AoD-based positioning, where there are multiple involved base stations 1602, each involved base station 1602 can report, to the serving base station 1602, the determined AoD from the respective base station 1602 to the UE 1604, or the RSRP measurements. The serving base station 1602 may then report the AoDs or RSRP measurements from the other involved base station(s) 1602 to the positioning entity (e.g., UE 1604 for UE-based positioning or a location server for UE-assisted positioning). With this information, and knowledge of the base stations’ 1602 geographic locations, the positioning entity can estimate a location of the UE 1604 as the intersection of the determined AoDs. There should be at least two involved base stations 1602 for a two- dimensional (2D) location solution, but as will be appreciated, the more base stations 1602 that are involved in the positioning procedure, the more accurate the estimated location of the UE 1604 will be.

[0179] To perform an UL-AoA positioning procedure, the UE 1604 transmits uplink reference signals (e.g., UL-PRS, SRS, DMRS, etc.) to the base station 1602 on one or more of uplink transmit beams 1604a - 1604d. The base station 1602 receives the uplink reference signals on one or more of uplink receive beams 1602a- 1602h. The base station 1602 determines the angle of the best receive beams 1602a - 1602h used to receive the one or more reference signals from the UE 1604 as the AoA from the UE 1604 to itself. Specifically, each of the receive beams 1602a - 1602h will result in a different received signal strength (e.g., RSRP, RSRQ, SINR, etc.) of the one or more reference signals at the base station 1602. Further, the channel impulse response of the one or more reference signals will be smaller for receive beams 1602a - 1602h that are further from the actual LOS path between the base station 1602 and the UE 1604 than for receive beams 1602a - 1602h that are closer to the LOS path. Likewise, the received signal strength will be lower for receive beams 1602a - 1602h that are further from the LOS path than for receive beams 1602a - 1602h that are closer to the LOS path. As such, the base station 1602 identifies the receive beam 1602a - 1602h that results in the highest received signal strength and, optionally, the strongest channel impulse response, and estimates the angle from itself to the UE 1604 as the AoA of that receive beam 1602a - 1602h. Note that as with DL-AoD-based positioning, the AoA of the receive beam 1602a - 1602h resulting in the highest received signal strength (and strongest channel impulse response if measured) does not necessarily he along the LOS path 1610. However, for UL-AoA- based positioning purposes in FR2, it may be assumed to do so.

[0180] Note that while the UE 1604 is illustrated as being capable of beamforming, this is not necessary for DL-AoD and UL-AoA positioning procedures. Rather, the UE 1604 may receive and transmit on an omni-directional antenna.

[0181] Where the UE 1604 is estimating its location (i.e., the UE is the positioning entity), it needs to obtain the geographic location of the base station 1602. The UE 1604 may obtain the location from, for example, the base station 1602 itself or a location server (e.g., location server 230, LMF 270, SLP 272). With the knowledge of the distance to the base station 1602 (based on the RTT or timing advance), the angle between the base station 1602 and the UE 1604 (based on the UL-AoA of the best receive beam 1602a - 1602h), and the known geographic location of the base station 1602, the UE 1604 can estimate its location.

[0182] Alternatively, where a positioning entity, such as the base station 1602 or a location server, is estimating the location of the UE 1604, the base station 1602 reports the AoA of the receive beam 1602a - 1602h resulting in the highest received signal strength (and optionally strongest channel impulse response) of the reference signals received from the UE 1604, or all received signal strengths and channel impulse responses for all receive beams 1602 (which allows the positioning entity to determine the best receive beam 1602a - 1602h). The base station 1602 may additionally report the Rx-Tx time difference to the UE 1604. The positioning entity can then estimate the location of the UE 1604 based on the UE’s 1604 distance to the base station 1602, the AoA of the identified receive beam 1602a- 1602h, and the known geographic location of the base station 1602.

[0183] Measurement equations may be used to model timing and location errors at the Rx side, e.g.:

Eq. 1

Eq. 2 whereby pseudo range is denoted as pr (m), carrier phase dp is the anchor location error (m), dt is the anchor clock error (s),e _p is the pseudorange noise and multipath (m), £, _p is the carrier phase noise and multipath (m), dT is the receiver clock error (s), c is the speed of light (m/s), A is the carrier phase wavelength (m), N is the carrier phase integer ambiguity (cycle), and p is the range between anchor and receiver (m). In some designs, atmosphere propagation errors can be ignored in the NR positioning (e.g., gNB anchors or anchor UEs), and are not depicted in Equations 1 and 2 to simplify the models.

[0184] FIG. 17 illustrates a single difference (SD) anchor measurement scheme 1700 in accordance with aspects of the disclosure. In particular, the SD anchor measurement scheme 1700 relates to SD between receivers (e.g., UE C and UE D). In FIG. 1, two anchors are depicted as satellites 1-2, although in other aspects non-satellite anchors (e.g., gNBs or UE anchors) may be used. Referring to FIG. 17, the following measurement equations may be used: Eq. 3 Eq. 4

[0185] Referring to FIG. 17, a reference node (e.g., base station) measurement may be subtracted from a rover station (e.g., target UE) measurement for the same anchor. In this manner, anchor clock error dt can be eliminated, the anchor location error dp as a function baseline length (b) can be reduced and anchor initial phase _O can be eliminated as follows: Eq. 5 [0186] FIG. 18 illustrates a SD anchor measurement scheme 1800 in accordance with aspects of the disclosure. In particular, the SD anchor measurement scheme 1800 relates to SD between anchors (e.g., anchors 1 and 2). In FIG. 18, two anchors are depicted as satellites 1-2, although in other aspects non-satellite anchors (e.g., gNBs or UE anchors) may be used. Referring to FIG. 18, the following measurement equations may be used: Eq. 6 Eq. 7

[0187] Referring to FIG. 18, a anchor measurement may be subtracted from a base anchor measurement for the same receiver. In this manner, receiver clock error dT can be Qualcomm Ref. No.2107212WO 53 eliminated, and common hardware bias in the receiver can be eliminated. This aspect is equivalent to RSTD in NR positioning. [0188] FIG. 19 illustrates a double difference (DD) measurement scheme 1900 in accordance with aspects of the disclosure. In particular, the DD measurement scheme 1900 involves a target UE 1905, a reference node 1910 (e.g., an anchor UE or gNB), wireless node 1 (e.g., gNBi) and wireless node 2 (e.g., gNBj). In particular, a first SD is computed at 1915, a second SD is computed 1920, and a DD is computed at 1925. Referring to FIG.19, the following measurement equations may be used: ∇∆pr ൌ ∇∆ρ ^ ∇∆dρ ^ ε _∇∆୮ Eq.8 Eq.9 wh carrier phase. In some designs, ^^ ^^∆ ^^ is the parameter that requires estimation. [0189] Referring to FIG.19, the DD measurement scheme 1900 may be used to eliminate anchor clock error ^^ ^^ and receiver clock error ^^ ^^, and to Reduce the anchor location error ^^ ^^. To simplify the following discussion, assume ^^ ^^ = 0 and remove ^^∆ ^^ ^^. [0190] In DD carrier phase, DD integer ambiguity ^^∆ ^^ is still unknown and may be estimated by integer ambiguity resolver (IAR).With measurement ^^∆ ^^ and estimated ^^∆ ^^ known, ^^∆ ^^ is known. For TDOA based positioning, ^^∆ ^^ and prior knowledge of reference n ^{ode and gNBs’ location can be used for final RSTD estimation, as follows:} m _{es_RSTD^^ ୧୨ െ mes_RSTD୰^^ ୨ + ୰^^ ^^ ୧ mes_RSTD୧୨ ൌ genie_RSTD୧୨ ^ n Eq. 10} whe b ^{^^} d ^{୰^^} d ference node measur RSTD ^୰ ୧ _୨ ^{^^} denotes prior kno erence node location and gNBs’ locatio [0191] Carrier phase- based position estimation has been used in some GNSS systems. Using GNSS carrier phase measurements in addition to pseudorange measurements, GNSS receiver could reach 0.01~0.1m accuracy. For example, with respect to pseudo range, code phase chip length (1/ ^^ℎ ^^ ^^ ^^ ^^ ^^ ^^_ ^^ ^^ ^^ ^^), e.g. GPS L1 = 300 m, and measurement error (due to noise) = 0.3-3.0 m ( ^{^} ^ _^^^ ~ ^{^} ^ _^^ ) chip length. With respect to carrier phase wavelength, e.g., measurement error (due to noise) = 2 mm ( ^{^} ^ _^^ ) wavelength. QC2107212WO [0192] To achieve carrier phase-based positioning, GNSS real time kinematic (RTK) system requires at least one more reference node to measure the same GNSS signal as target UE, so that it can eliminate/mitigate various errors (e.g., anchor location error, anchor clock errors, propagation errors (ionospheric delay, tropospheric delay)) in the measurements. This concept is similar to the DD measurement scheme described above with respect to FIG 19.

[0193] A phase center is defined as the apparent source of radiation. If the source were ideal, it would have a spherical equiphase contour. The real case is slightly different, because the equiphase contour is irregular and each segment has its own apparent radiation origin. In GNSS, the phase center is modeled as a mean deviation from antenna physical center + phase center variation (PCV). PRSs from different TRPs will have different phase centers (e.g., equivalent to UE movements across PRS measurements).

[0194] FIG. 20 illustrates a phase center depiction 2000 in accordance with aspects of the disclosure. In FIG. 20, the ideal case is represented, whereby an instantaneous phase center is colocated with the mean phase center at an antenna panel 2010.

[0195] FIG. 21 illustrates a phase center depiction 2100 in accordance with aspects of the disclosure. In FIG. 21, a real-world case is represented, whereby an instantaneous phase center from each wireless node is offset from the mean phase center at an antenna panel 2110.

[0196] FIG. 22 illustrates a depiction 2200 of ideal vs. real equiphase contours in accordance with aspects of the disclosure. In FIG. 22, a PRS associated with an AoA arrives at an antenna panel 2220. An ideal equiphase contour (e.g., spherical) is depicted at 2230, and a real -world equiphase contour (e.g., irregularly shaped) is depicted at 2240. The irregular equiphase contour 2240 creates an instantaneous phase center that is offset from the mean phase center, as shown in FIG. 22.

[0197] FIG. 23 depicts antenna phase patterns 2300 with various equiphase contours in accordance with aspects of the disclosure. As shown in FIG. 23, the equiphase contours of the antenna phase patterns 2300 can vary greatly.

[0198] Generally, phase center is a function of carrier frequency and AoA. FIG. 24 illustrates phase centers 2400 in accordance with aspects of the disclosure. An antenna reference point is shown at 2410, a mechanical antenna phase center is shown at 2420, an L2 electrical antenna phase center is shown at 2430, and an L 1 electrical antenna phase center is shown at 2440. [0199] For carrier phase-based high accuracy positioning, the measurement error caused by phase center variation can be significant. For this reason, aspects of the disclosure are directed to a first node (e.g., UE, gNB, etc.) determining equiphase contour information associated with an antenna (e.g., Rx antenna, Tx antenna, etc.) of the first node at one or more carrier frequencies, and transmitting an indication of the equiphase contour information to a second node (e.g., UE, gNB, network entity, position estimation entity, etc.). The second node may then correct measurement information associated with a carrier phase-based position estimation session based at least in part on the equiphase contour information. Such aspects may provide various technical advantages, such as increasing position estimation accuracy for carrier phase-based position estimation sessions, particularly for NR-based carrier phase-based position estimation sessions.

[0200] FIG. 25 illustrates an exemplary process 2500 of communication, according to aspects of the disclosure. In an aspect, the process 2500 may be performed by a first node, which may correspond to a UE such as UE 302 or a BS (or gNB) such as BS 304.

[0201] Referring to FIG. 25, at 2510, the first node (e.g., processor(s) 332 or 384, equiphase contour component 342 or 388, etc.) determines equiphase contour information associated with an antenna of a first node at one or more carrier frequencies. The equiphase contour information can be determined in various ways. For example, in some designs, the equiphase contour information can be a static parameter, in which case the equiphase contour information can be associated with (e.g., predetermined for) a particular brand, model or version of the antenna. The equiphase contour information may further be associated with the antenna at different granularities (e.g., per antenna element, per antenna array, per antenna beam, etc.), as will be described below in more detail. In some designs, the indication may be transmitted as part of location assistance data. A means for performing the determination of 2510 may include processor(s) 332 or 384, equiphase contour component 342 or 388, etc., of UE 302 or BS 304.

[0202] Referring to FIG. 25, at 2520, the first node (e.g., transmitter 314 or 324 or 354 or 364, network transceiver(s) 380, etc.) transmits an indication of the equiphase contour information to a second node. In some designs, the second node may correspond to a position estimation entity, such as UE (e.g., for UE-based position estimation) or gNB (e.g., for LMF integrated in RAN) or anetwork entity 306 (e.g., a core network integrated LMF or other location server, etc.). A means for performing the transmission of 2520 may include transmiter 314 or 324 or 354 or 364, network transceiver(s) 380, etc., of UE 302 or BS 304.

[0203] FIG. 26 illustrates an exemplary process 2600 of communication, according to aspects of the disclosure. In an aspect, the process 2600 may be performed by a device, which may correspond to a position estimation entity, such as UE (e.g., for UE-based position estimation) or gNB (e.g., for LMF integrated in RAN) or a network entity 306 (e.g., a core network integrated LMF or other location server, etc.). Alternatively, the process 2600 may be performed by a wireless node (e.g., UE 302 or BS 304) that participates in a carrier phase-based position estimation session but is not the position estimation entity (e.g., the wireless node may self-correct its measurements based on the equiphase contour information, and then report the corrected measurements).

[0204] Referring to FIG. 26, at 2610, the device (e.g., processor(s) 332 or 384 or 394, equiphase contour component 342 or 388 or 398, receiver 312 or 322 or 352 or 362, network transceiver(s) 380 or 390, etc.) determines equiphase contour information associated with an antenna of a first node at one or more carrier frequencies. In some designs, the device that performs the process 2600 may correspond to the second node. In some designs, the first and second nodes may be the same (e.g., for UE-based position estimation, UE may determine its own equiphase contour information and then use for position estimation, or for gNB-based position estimation, gNB may determine its own equiphase contour information and then use for position estimation). In some designs, the determination at 2610 may be based upon a wired or wireless reception of the indication of the equiphase contour information from the first node, as described with respect to FIG. 25. Because the determination at 2610 can be performed in various ways, a means for performing the determination at 2610 may include processor(s) 332 or 384 or 394, equiphase contour component 342 or 388 or 398, receiver 312 or 322 or 352 or 362, network transceiver(s) 380 or 390, etc., of UE 302, BS 304 or network entity 306.

[0205] Referring to FIG. 26, at 2620, the device (e.g., processor(s) 332 or 384 or 394, equiphase contour component 342 or 388 or 398, etc.) corrects measurement information (e.g., phase center bias in one or more measurements) associated with a carrier phase-based position estimation session based at least in part on the equiphase contour information. As noted above, the device may correspond to a position estimation entity that corrects the measurement information in association with derivation of a position estimate of a target UE. In other designs however, the device may correspond to a wireless node (e.g., UE 302 or BS 304) that participates in a carrier phase-based position estimation session but is not the position estimation entity (e.g., in which case the wireless node may self-correct its measurements based on the equiphase contour information at 2620, and then report the corrected measurements). A means for performing the correction at 2620 may include processor(s) 332 or 384 or 394, equiphase contour component 342 or 388 or 398, etc., of UE 302, BS 304 or network entity 306.

[0206] Referring to FIGS. 25-26, in some designs, the antenna corresponds to a receive antenna, or the antenna corresponds to a transmit antenna. Accordingly, while examples of equiphase contours are described above with respect to Rx signals and AoA, equiphase contours are also associated with Tx signals and AoD, in some designs.

[0207] Referring to FIGS. 25-26, in some designs, the equiphase contour information (e.g., phase of radiation pattern) is reported per antenna element, per antenna array, or per beam. In some designs, if reported per antenna panel, the equiphase contour information may be reported per single antenna, or per antenna in an array, or per antenna panel profile. In some designs, if reported per antenna array, the antenna array may form a pseudo-omni beam to receive all PRS signal. In some designs, if reported per antenna element, the equiphase contour information may be reported per antenna array with a codebook (e.g., one or multiple beamforming coefficients).

[0208] Referring to FIGS. 25-26, in some designs, the equiphase contour information is associated with multiple carrier frequencies based on a reference signal for positioning (RS-P) configuration (e.g., DL-PRS or UL-PRS/SRS-P or SL-PRS), an RS-P measurement requirement, or a combination thereof. For example, the first node may need to report one or multiple contours of multiple carrier frequencies based on PRS configuration and measurement requirement. In some designs, the one or more carrier frequencies may include one or more sub-bands of at least one positioning frequency layer (PFL), one or more component carriers (CCs), one or more bandwidth parts (BWPs) (e.g., UL or DL or SL), or a combination thereof.

[0209] Referring to FIGS. 25-26, in some designs, the first node corresponds to a base station and the second node corresponds to a location management function (LMF), or the first node corresponds to a user equipment (UE) and the second node corresponds to the LMF, or the first node corresponds to the base station and the second node corresponds to the UE, or the first node corresponds to the UE and the second node corresponds to the base station, or the first node corresponds to the UE and the second node corresponds to another UE, or any combination thereof.

[0210] Referring to FIGS. 25-26, in some designs, the equiphase contour information (e.g., for each antenna element, antenna array, or beam) includes one or more of:

• a heatmap of a phase pattern across one or more elevation angles and one or more azimuth angles (e.g., based on the accuracy requirement and/or overhead considerations, the phase assistance data may have different angle resolutions. For AoD/AoA between two points, the phase may be interpolated, etc.). In some designs, the elevation and azimuth angle(s) may include all possible angles over a sphere at some level of precision (e.g., by providing an angle resolution, a node provides a subset of all possible angles), or

• a function (e.g., a polynomial function, a 2D function, etc.) that approximates the phase pattern (e.g., the first node may further report the maximum error (uncertainty) caused by approximation), or

• statistical information associated with a phase center bias (e.g., the variance of phase center bias compared with a sphere, max bias, etc.), or

• identification information associated with the antenna (e.g., antenna type or brand, e.g., if the phase contour is the same (or there is little to no part-to-part variation), then one report can apply to multiple or even all antenna module(s), e.g., network-side or position estimation entity may maintain a database of phase contour, which can be looked up via the identification information to determine the phase contour information), or

• a mean phase center offset relative to an antenna reference point, or

• any combination thereof.

[0211] Referring to FIGS. 25-26, in some designs, the equiphase contour information is described in terms of a global coordinate system (GCS) or a local coordinate system (LCS) in conjunction with information associated with node orientation for LCS-to-GCS coordinate conversion.

[0212] Referring to FIGS. 25-26, in some designs, the correction at 2620 may be based on AoX (e.g., AoA or AoD) and carrier frequency. For example, in general, the first node (e.g., Rx node or Tx node) may conduct AoD or AoA estimation for phase measurement correction. The AoD or AoA measurement may be sent to the position estimation entity during the carrier phase-based position estimation session.

[0213] Referring to FIGS. 25-26, in some designs, as noted above, the device that performs the process of FIG. 26 may be an Rx node which corrects the phase bias caused by its Rx antenna (e.g., in this case, in the measurement report/sharing, the Rx node may further indicate the whether the Rx phase correction is applied or not, the correction value applied, an associated confidence level, etc.). In some designs, measurement sharing may include reference node(s) sending their measurements to the target UE either via LMF (Uu) or SL.

[0214] Referring to FIGS. 25-26, in some designs, as noted above, the device that performs the process of FIG. 26 may be a position estimation entity. In this case, the position estimation entity may gather all the Tx/Rx phase contour assistance data, and AoD/AoA measurement(s) at Tx/Rx side(s), and phase measurements. The position estimation entity may then apply the correction during the location estimation procedure.

[0215] Referring to FIGS. 25-26, in some designs, the device corresponds to the first node. In this case, the first node is a position estimation entity for the carrier phase-based position estimation session, and the first node derives a position estimate of a user equipment (UE) based at least in part upon the corrected measurement information (e.g., UE-based position estimation in case first node corresponds to the UE, or UE-assisted position estimation if first node corresponds to gNB or LMF, etc.).

[0216] Referring to FIGS. 25-26, in some designs, a second node is a position estimation entity for the carrier phase-based position estimation session, and the corrected measurement information is transmitted to the position estimation entity.

[0217] Referring to FIGS. 25-26, in some designs, the device corresponds to a second node that receives the equiphase contour information from the first node, the second node is a position estimation entity for the carrier phase-based position estimation, and the second node derives a position estimate of a user equipment (UE) based at least in part upon the corrected measurement information (e.g., UE-based position estimation in case second node corresponds to the UE, or UE-assisted position estimation if second node corresponds to gNB or LMF, etc.).

[0218] In the detailed description above it can be seen that different features are grouped together in examples. This manner of disclosure should not be understood as an intention that the example clauses have more features than are explicitly mentioned in each clause. Rather, the various aspects of the disclosure may include fewer than all features of an individual example clause disclosed. Therefore, the following clauses should hereby be deemed to be incorporated in the description, wherein each clause by itself can stand as a separate example. Although each dependent clause can refer in the clauses to a specific combination with one of the other clauses, the aspect(s) of that dependent clause are not limited to the specific combination. It will be appreciated that other example clauses can also include a combination of the dependent clause aspect(s) with the subject matter of any other dependent clause or independent clause or a combination of any feature with other dependent and independent clauses. The various aspects disclosed herein expressly include these combinations, unless it is explicitly expressed or can be readily inferred that a specific combination is not intended (e.g., contradictory aspects, such as defining an element as both an insulator and a conductor). Furthermore, it is also intended that aspects of a clause can be included in any other independent clause, even if the clause is not directly dependent on the independent clause.

[0219] Implementation examples are described in the following numbered clauses:

[0220] Clause 1. A method of operating a first node, comprising: determining equiphase contour information associated with an antenna of the first node at one or more carrier frequencies; and transmitting an indication of the equiphase contour information to a second node.

[0221] Clause 2. The method of clause 1, wherein the antenna corresponds to a receive antenna, or wherein the antenna corresponds to a transmit antenna.

[0222] Clause 3. The method of any of clauses 1 to 2, wherein the equiphase contour information is reported per antenna element, per antenna array, or per beam.

[0223] Clause 4. The method of any of clauses 1 to 3, wherein the equiphase contour information is associated with multiple carrier frequencies based on a reference signal for positioning (RS-P) configuration, an RS-P measurement requirement, or a combination thereof.

[0224] Clause 5. The method of any of clauses 1 to 4, wherein the one or more carrier frequencies comprise one or more sub-bands of at least one positioning frequency layer (PFL), one or more component carriers (CCs), one or more bandwidth parts (BWPs), or a combination thereof.

[0225] Clause 6. The method of any of clauses 1 to 5, wherein the first node corresponds to a base station and the second node corresponds to a location management function (LMF), or wherein the first node corresponds to a user equipment (UE) and the second node corresponds to the LMF, or wherein the first node corresponds to the base station and the second node corresponds to the UE, or wherein the first node corresponds to the UE and the second node corresponds to the base station, or wherein the first node corresponds to the UE and the second node corresponds to another UE, or any combination thereof.

[0226] Clause 7. The method of any of clauses 1 to 6, wherein the equiphase contour information comprises: a heatmap of a phase pattern across one or more elevation angles and one or more azimuth angles, or a function that approximates the phase pattern, or statistical information associated with a phase center bias, or identification information associated with the antenna, or a mean phase center offset relative to an antenna reference point, or any combination thereof.

[0227] Clause 8. The method of any of clauses 1 to 7, wherein the equiphase contour information is described in terms of a global coordinate system (GCS) or a local coordinate system (LCS) in conjunction with information associated with node orientation for LCS-to-GCS coordinate conversion.

[0228] Clause 9. A method of operating a device, comprising: determining equiphase contour information associated with an antenna of a first node at one or more carrier frequencies; and correcting measurement information associated with a carrier phase-based position estimation session based at least in part on the equiphase contour information.

[0229] Clause 10. The method of clause 9, wherein the device corresponds to the first node.

[0230] Clause 11. The method of clause 10, wherein the first node is a position estimation entity for the carrier phase-based position estimation session, and wherein the first node derives a position estimate of a user equipment (UE) based at least in part upon the corrected measurement information.

[0231] Clause 12. The method of any of clauses 10 to 11, wherein a second node is a position estimation entity for the carrier phase-based position estimation session, and wherein the corrected measurement information is transmitted to the position estimation entity.

[0232] Clause 13. The method of any of clauses 9 to 12, wherein the device corresponds to a second node that receives the equiphase contour information from the first node, wherein the second node is a position estimation entity for the carrier phase-based position estimation, and wherein the second node derives a position estimate of a user equipment (UE) based at least in part upon the corrected measurement information.

[0233] Clause 14. The method of any of clauses 9 to 13, wherein the antenna corresponds to a receive antenna, or wherein the antenna corresponds to a transmit antenna. [0234] Clause 15. The method of any of clauses 9 to 14, wherein the equiphase contour information is reported per antenna element, per antenna array, or per beam.

[0235] Clause 16. The method of any of clauses 9 to 15, wherein the equiphase contour information is associated with multiple carrier frequencies based on a reference signal for positioning (RS-P) configuration, an RS-P measurement requirement, or a combination thereof.

[0236] Clause 17. The method of any of clauses 9 to 16, wherein the one or more carrier frequencies comprise one or more sub-bands of at least one positioning frequency layer (PFL), one or more component carriers (CCs), one or more bandwidth parts (BWPs), or a combination thereof.

[0237] Clause 18. The method of any of clauses 9 to 17, wherein the first node corresponds to a base station and the second node corresponds to a location management function (LMF), or wherein the first node corresponds to a user equipment (UE) and the second node corresponds to the LMF, or wherein the first node corresponds to the base station and the second node corresponds to the UE, or wherein the first node corresponds to the UE and the second node corresponds to the base station, or wherein the first node corresponds to the UE and the second node corresponds to another UE, or any combination thereof.

[0238] Clause 19. The method of any of clauses 9 to 18, wherein the equiphase contour information comprises: a heatmap of a phase pattern across one or more elevation angles and one or more azimuth angles, or a function that approximates the phase pattern, or statistical information associated with a phase center bias, or identification information associated with the antenna, or a mean phase center offset relative to an antenna reference point, or any combination thereof.

[0239] Clause 20. The method of any of clauses 9 to 19, wherein the equiphase contour information is described in terms of a global coordinate system (GCS) or a local coordinate system (LCS) in conjunction with information associated with node orientation for LCS-to-GCS coordinate conversion.

[0240] Clause 21. A first node, comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: determine equiphase contour information associated with an antenna of the first node at one or more carrier frequencies; and transmit, via the at least one transceiver, an indication of the equiphase contour information to a second node. [0241] Clause 22. The first node of clause 21, wherein the antenna corresponds to a receive antenna, or wherein the antenna corresponds to a transmit antenna.

[0242] Clause 23. The first node of any of clauses 21 to 22, wherein the equiphase contour information is reported per antenna element, per antenna array, or per beam.

[0243] Clause 24. The first node of any of clauses 21 to 23, wherein the equiphase contour information is associated with multiple carrier frequencies based on a reference signal for positioning (RS-P) configuration, an RS-P measurement requirement, or a combination thereof.

[0244] Clause 25. The first node of any of clauses 21 to 24, wherein the one or more carrier frequencies comprise one or more sub-bands of at least one positioning frequency layer (PFL), one or more component carriers (CCs), one or more bandwidth parts (BWPs), or a combination thereof.

[0245] Clause 26. The first node of any of clauses 21 to 25, wherein the first node corresponds to a base station and the second node corresponds to a location management function (LMF), or wherein the first node corresponds to a user equipment (UE) and the second node corresponds to the LMF, or wherein the first node corresponds to the base station and the second node corresponds to the UE, or wherein the first node corresponds to the UE and the second node corresponds to the base station, or wherein the first node corresponds to the UE and the second node corresponds to another UE, or any combination thereof.

[0246] Clause 27. The first node of any of clauses 21 to 26, wherein the equiphase contour information comprises: a heatmap of a phase pattern across one or more elevation angles and one or more azimuth angles, or a function that approximates the phase pattern, or statistical information associated with a phase center bias, or identification information associated with the antenna, or a mean phase center offset relative to an antenna reference point, or any combination thereof.

[0247] Clause 28. The first node of any of clauses 21 to 27, wherein the equiphase contour information is described in terms of a global coordinate system (GCS) or a local coordinate system (LCS) in conjunction with information associated with node orientation for LCS-to-GCS coordinate conversion.

[0248] Clause 29. A device, comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, the at least one processor configured to: determine equiphase contour information associated with an antenna of a first node at one or more carrier frequencies; and correct measurement information associated with a carrier phase-based position estimation session based at least in part on the equiphase contour information.

[0249] Clause 30. The device of clause 29, wherein the device corresponds to the first node.

[0250] Clause 31. The device of clause 30, wherein the first node is a position estimation entity for the carrier phase-based position estimation session, and wherein the first node derives a position estimate of a user equipment (UE) based at least in part upon the corrected measurement information.

[0251] Clause 32. The device of any of clauses 30 to 31, wherein a second node is a position estimation entity for the carrier phase-based position estimation session, and wherein the corrected measurement information is transmitted to the position estimation entity.

[0252] Clause 33. The device of any of clauses 29 to 32, wherein the device corresponds to a second node that receives the equiphase contour information from the first node, wherein the second node is a position estimation entity for the carrier phase-based position estimation, and wherein the second node derives a position estimate of a user equipment (UE) based at least in part upon the corrected measurement information.

[0253] Clause 34. The device of any of clauses 29 to 33, wherein the antenna corresponds to a receive antenna, or wherein the antenna corresponds to a transmit antenna.

[0254] Clause 35. The device of any of clauses 29 to 34, wherein the equiphase contour information is reported per antenna element, per antenna array, or per beam.

[0255] Clause 36. The device of any of clauses 29 to 35, wherein the equiphase contour information is associated with multiple carrier frequencies based on a reference signal for positioning (RS-P) configuration, an RS-P measurement requirement, or a combination thereof.

[0256] Clause 37. The device of any of clauses 29 to 36, wherein the one or more carrier frequencies comprise one or more sub-bands of at least one positioning frequency layer (PFL), one or more component carriers (CCs), one or more bandwidth parts (BWPs), or a combination thereof.

[0257] Clause 38. The device of any of clauses 29 to 37, wherein the first node corresponds to a base station and the second node corresponds to a location management function (LMF), or wherein the first node corresponds to a user equipment (UE) and the second node corresponds to the LMF, or wherein the first node corresponds to the base station and the second node corresponds to the UE, or wherein the first node corresponds to the UE and the second node corresponds to the base station, or wherein the first node corresponds to the UE and the second node corresponds to another UE, or any combination thereof.

[0258] Clause 39. The device of any of clauses 29 to 38, wherein the equiphase contour information comprises: a heatmap of a phase pattern across one or more elevation angles and one or more azimuth angles, or a function that approximates the phase pattern, or statistical information associated with a phase center bias, or identification information associated with the antenna, or a mean phase center offset relative to an antenna reference point, or any combination thereof.

[0259] Clause 40. The device of any of clauses 29 to 39, wherein the equiphase contour information is described in terms of a global coordinate system (GCS) or a local coordinate system (LCS) in conjunction with information associated with node orientation for LCS-to-GCS coordinate conversion.

[0260] Clause 41. A first node, comprising: means for determining equiphase contour information associated with an antenna of the first node at one or more carrier frequencies; and means for transmitting an indication of the equiphase contour information to a second node.

[0261] Clause 42. The first node of clause 41, wherein the antenna corresponds to a receive antenna, or wherein the antenna corresponds to a transmit antenna.

[0262] Clause 43. The first node of any of clauses 41 to 42, wherein the equiphase contour information is reported per antenna element, per antenna array, or per beam.

[0263] Clause 44. The first node of any of clauses 41 to 43, wherein the equiphase contour information is associated with multiple carrier frequencies based on a reference signal for positioning (RS-P) configuration, an RS-P measurement requirement, or a combination thereof.

[0264] Clause 45. The first node of any of clauses 41 to 44, wherein the one or more carrier frequencies comprise one or more sub-bands of at least one positioning frequency layer (PFL), one or more component carriers (CCs), one or more bandwidth parts (BWPs), or a combination thereof.

[0265] Clause 46. The first node of any of clauses 41 to 45, wherein the first node corresponds to a base station and the second node corresponds to a location management function (LMF), or wherein the first node corresponds to a user equipment (UE) and the second node corresponds to the LMF, or wherein the first node corresponds to the base station and the second node corresponds to the UE, or wherein the first node corresponds to the UE and the second node corresponds to the base station, or wherein the first node corresponds to the UE and the second node corresponds to another UE, or any combination thereof.

[0266] Clause 47. The first node of any of clauses 41 to 46, wherein the equiphase contour information comprises: a heatmap of a phase pattern across one or more elevation angles and one or more azimuth angles, or a function that approximates the phase pattern, or statistical information associated with a phase center bias, or identification information associated with the antenna, or a mean phase center offset relative to an antenna reference point, or any combination thereof.

[0267] Clause 48. The first node of any of clauses 41 to 47, wherein the equiphase contour information is described in terms of a global coordinate system (GCS) or a local coordinate system (LCS) in conjunction with information associated with node orientation for LCS-to-GCS coordinate conversion.

[0268] Clause 49. A device, comprising: means for determining equiphase contour information associated with an antenna of a first node at one or more carrier frequencies; and means for correcting measurement information associated with a carrier phase-based position estimation session based at least in part on the equiphase contour information.

[0269] Clause 50. The device of clause 49, wherein the device corresponds to the first node.

[0270] Clause 51. The device of clause 50, wherein the first node is a position estimation entity for the carrier phase-based position estimation session, and wherein the first node derives a position estimate of a user equipment (UE) based at least in part upon the corrected measurement information.

[0271] Clause 52. The device of any of clauses 50 to 51, wherein a second node is a position estimation entity for the carrier phase-based position estimation session, and wherein the corrected measurement information is transmitted to the position estimation entity.

[0272] Clause 53. The device of any of clauses 49 to 52, wherein the device corresponds to a second node that receives the equiphase contour information from the first node, wherein the second node is a position estimation entity for the carrier phase-based position estimation, and wherein the second node derives a position estimate of a user equipment (UE) based at least in part upon the corrected measurement information.

[0273] Clause 54. The device of any of clauses 49 to 53, wherein the antenna corresponds to a receive antenna, or wherein the antenna corresponds to a transmit antenna. [0274] Clause 55. The device of any of clauses 49 to 54, wherein the equiphase contour information is reported per antenna element, per antenna array, or per beam.

[0275] Clause 56. The device of any of clauses 49 to 55, wherein the equiphase contour information is associated with multiple carrier frequencies based on a reference signal for positioning (RS-P) configuration, an RS-P measurement requirement, or a combination thereof.

[0276] Clause 57. The device of any of clauses 49 to 56, wherein the one or more carrier frequencies comprise one or more sub-bands of at least one positioning frequency layer (PFL), one or more component carriers (CCs), one or more bandwidth parts (BWPs), or a combination thereof.

[0277] Clause 58. The device of any of clauses 49 to 57, wherein the first node corresponds to a base station and the second node corresponds to a location management function (LMF), or wherein the first node corresponds to a user equipment (UE) and the second node corresponds to the LMF, or wherein the first node corresponds to the base station and the second node corresponds to the UE, or wherein the first node corresponds to the UE and the second node corresponds to the base station, or wherein the first node corresponds to the UE and the second node corresponds to another UE, or any combination thereof.

[0278] Clause 59. The device of any of clauses 49 to 58, wherein the equiphase contour information comprises: a heatmap of a phase pattern across one or more elevation angles and one or more azimuth angles, or a function that approximates the phase pattern, or statistical information associated with a phase center bias, or identification information associated with the antenna, or a mean phase center offset relative to an antenna reference point, or any combination thereof.

[0279] Clause 60. The device of any of clauses 49 to 59, wherein the equiphase contour information is described in terms of a global coordinate system (GCS) or a local coordinate system (LCS) in conjunction with information associated with node orientation for LCS-to-GCS coordinate conversion.

[0280] Clause 61. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a first node, cause the first node to: determine equiphase contour information associated with an antenna of the first node at one or more carrier frequencies; and transmit an indication of the equiphase contour information to a second node. [0281] Clause 62. The non-transitory computer-readable medium of clause 61, wherein the antenna corresponds to a receive antenna, or wherein the antenna corresponds to a transmit antenna.

[0282] Clause 63. The non-transitory computer-readable medium of any of clauses 61 to 62, wherein the equiphase contour information is reported per antenna element, per antenna array, or per beam.

[0283] Clause 64. The non-transitory computer-readable medium of any of clauses 61 to 63, wherein the equiphase contour information is associated with multiple carrier frequencies based on a reference signal for positioning (RS-P) configuration, an RS-P measurement requirement, or a combination thereof.

[0284] Clause 65. The non-transitory computer-readable medium of any of clauses 61 to 64, wherein the one or more carrier frequencies comprise one or more sub-bands of at least one positioning frequency layer (PFL), one or more component carriers (CCs), one or more bandwidth parts (BWPs), or a combination thereof.

[0285] Clause 66. The non-transitory computer-readable medium of any of clauses 61 to 65, wherein the first node corresponds to a base station and the second node corresponds to a location management function (LMF), or wherein the first node corresponds to a user equipment (UE) and the second node corresponds to the LMF, or wherein the first node corresponds to the base station and the second node corresponds to the UE, or wherein the first node corresponds to the UE and the second node corresponds to the base station, or wherein the first node corresponds to the UE and the second node corresponds to another UE, or any combination thereof.

[0286] Clause 67. The non-transitory computer-readable medium of any of clauses 61 to 66, wherein the equiphase contour information comprises: a heatmap of a phase pattern across one or more elevation angles and one or more azimuth angles, or a function that approximates the phase pattern, or statistical information associated with a phase center bias, or identification information associated with the antenna, or a mean phase center offset relative to an antenna reference point, or any combination thereof.

[0287] Clause 68. The non-transitory computer-readable medium of any of clauses 61 to 67, wherein the equiphase contour information is described in terms of a global coordinate system (GCS) or a local coordinate system (LCS) in conjunction with information associated with node orientation for LCS-to-GCS coordinate conversion. [0288] Clause 69. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a device, cause the device to: determine equiphase contour information associated with an antenna of a first node at one or more carrier frequencies; and correct measurement information associated with a carrier phase-based position estimation session based at least in part on the equiphase contour information.

[0289] Clause 70. The non-transitory computer-readable medium of clause 69, wherein the device corresponds to the first node.

[0290] Clause 71. The non-transitory computer-readable medium of clause 70, wherein the first node is a position estimation entity for the carrier phase-based position estimation session, and wherein the first node derives a position estimate of a user equipment (UE) based at least in part upon the corrected measurement information.

[0291] Clause 72. The non-transitory computer-readable medium of any of clauses 70 to 71, wherein a second node is a position estimation entity for the carrier phase-based position estimation session, and wherein the corrected measurement information is transmitted to the position estimation entity.

[0292] Clause 73. The non-transitory computer-readable medium of any of clauses 69 to 72, wherein the device corresponds to a second node that receives the equiphase contour information from the first node, wherein the second node is a position estimation entity for the carrier phase-based position estimation, and wherein the second node derives a position estimate of a user equipment (UE) based at least in part upon the corrected measurement information.

[0293] Clause 74. The non-transitory computer-readable medium of any of clauses 69 to 73, wherein the antenna corresponds to a receive antenna, or wherein the antenna corresponds to a transmit antenna.

[0294] Clause 75. The non-transitory computer-readable medium of any of clauses 69 to 74, wherein the equiphase contour information is reported per antenna element, per antenna array, or per beam.

[0295] Clause 76. The non-transitory computer-readable medium of any of clauses 69 to 75, wherein the equiphase contour information is associated with multiple carrier frequencies based on a reference signal for positioning (RS-P) configuration, an RS-P measurement requirement, or a combination thereof.

[0296] Clause 77. The non-transitory computer-readable medium of any of clauses 69 to 76, wherein the one or more carrier frequencies comprise one or more sub-bands of at least one positioning frequency layer (PFL), one or more component carriers (CCs), one or more bandwidth parts (BWPs), or a combination thereof.

[0297] Clause 78. The non-transitory computer-readable medium of any of clauses 69 to 77, wherein the first node corresponds to a base station and the second node corresponds to a location management function (LMF), or wherein the first node corresponds to a user equipment (UE) and the second node corresponds to the LMF, or wherein the first node corresponds to the base station and the second node corresponds to the UE, or wherein the first node corresponds to the UE and the second node corresponds to the base station, or wherein the first node corresponds to the UE and the second node corresponds to another UE, or any combination thereof.

[0298] Clause 79. The non-transitory computer-readable medium of any of clauses 69 to 78, wherein the equiphase contour information comprises: a heatmap of a phase pattern across one or more elevation angles and one or more azimuth angles, or a function that approximates the phase pattern, or statistical information associated with a phase center bias, or identification information associated with the antenna, or a mean phase center offset relative to an antenna reference point, or any combination thereof.

[0299] Clause 80. The non-transitory computer-readable medium of any of clauses 69 to 79, wherein the equiphase contour information is described in terms of a global coordinate system (GCS) or a local coordinate system (LCS) in conjunction with information associated with node orientation for LCS-to-GCS coordinate conversion.

[0300] Those of skill in the art will appreciate that information and signals 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 above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0301] Further, those of skill in the art will appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the aspects disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

[0302] The various illustrative logical blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an ASIC, a field-programable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0303] The methods, sequences and/or algorithms described in connection with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An example storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal (e.g., UE). In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.

[0304] In one or more example aspects, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other 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 computer. Also, any connection is properly termed a computer-readable medium. For example, if the 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 technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0305] While the foregoing disclosure shows illustrative aspects of the disclosure, it should be noted that various changes and modifications could be made herein without departing from the scope of the disclosure as defined by the appended claims. The functions, steps and/or actions of the method claims in accordance with the aspects of the disclosure described herein need not be performed in any particular order. Furthermore, although elements of the disclosure may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated.