Non-terrestrial network communication function based on location estimate of a user equipment

Abstract

Aspects of the disclosure are directed to non-terrestrial network (NTN)-based communication function based on location estimate of a user equipment (UE). In an aspect, the NTN-based communication function is associated with a primary Global Navigation Satellite System (N-GNSS)-based positioning scheme and secondary non- GNSS (N-GNSS)-based positioning scheme(s). In an aspect, the N-GNSS-based positioning scheme(s) are utilized for the location estimate if certain condition(s) are satisfied. Such aspects may provide various technical advantages, such as improved performance associated with NTN-based communication function(s) that rely on N- GNSS-based location estimate(s).

Description

Qualcomm Ref. No. 2500095WO1 / 85NON-TERRESTRIAL NETWORK COMMUNICATION FUNCTION BASED ON LOCATION ESTIMATE OF A USER EQUIPMENTTECHNICAL FIELD

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

[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)), RF sensing, and other technical enhancements. These enhancements, as well as the use of higher frequency bands, enable improved RF sensing and 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 theQC2500095WOQualcomm Ref. No. 2500095WO2 / 85scope 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 tlie detailed description presented below.

[0005] In an aspect, a method performed by a user equipment (UE) includes determining to utilize a secondary non-Global Navigation Satellite System (N-GNSS)-based positioning scheme to support a non-terrestrial entity (NTN)-based communication function instead of a primary GNSS-based positioning scheme based on a set of conditions; obtaining a N-GNSS-based location estimate of the UE based on the N-GNSS-based positioning scheme; and performing the NTN-based communication function based on the N-GNSS- based location estimate in accordance with the determination.

[0006] In an aspect, a method performed by a network component includes receiving, from a user equipment (UE), non-Global Navigation Satellite System (N-GNSS)-based positioning scheme capability information of the UE; and transmitting, to the UE in response to the N-GNSS-based positioning scheme capability information, N-GNSS- based positioning scheme information associated with a set of secondary N-GNSS-based positioning schemes for a (NTN)-based communication function, wherein the NTN-based communication function is associated with a primary' GNSS-based positioning scheme.

[0007] In an aspect, a user equipment (UE) includes one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors, either alone or in combination, being configured to: determine to utilize a secondary' non-Global Navigation Satellite System (N-GNSS)-based positioning scheme to support a nonterrestrial entity (NTN)-based communication function instead of a primary GNSS-based positioning scheme based on a set of conditions; obtain a N-GNSS-based location estimate of the UE based on the N-GNSS-based positioning scheme; and perform the NTN-based communication function based on the N-GNSS-based location estimate in accordance with the determination.

[0008] In an aspect, a network component includes one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors, either alone or in combination, being configured to: receive, via the one or more transceivers, from a userQC2500095WOQualcomm Ref. No. 2500095WO3 / 85equipment (UE), non-Global Navigation Satellite System (N-GNSS) -based positioning scheme capability information of the UE; and transmit, via the one or more transceivers, to the UE in response to the N-GNSS-based positioning scheme capability information, N-GNSS-based positioning scheme information associated with a set of secondary N- GNSS-based positioning schemes for a (NTN)-based communication function, wherein the NTN-based communication function is associated with a primary GNSS-based positioning scheme.

[0009] In an aspect, a user equipment (UE) includes means for determining to utilize a secondary non-Global Navigation Satellite System (N-GNSS) -based positioning scheme to support a non-terrestrial entity (NTN)-based communication function instead of a primary GNSS- based positioning scheme based on a set of conditions; means for obtaining a N-GNSS- based location estimate of the UE based on the N-GNSS-based positioning scheme; and means for performing the NTN-based communication function based on the N-GNSS- based location estimate in accordance with the determination.

[0010] In an aspect, a network component includes means for receiving, from a user equipment (UE), non-Global Navigation Satellite System (N-GNSS) -based positioning scheme capability information of the UE; and means for transmitting, to the UE in response to the N-GNSS-based positioning scheme capability information, N-GNSS-based positioning scheme information associated with a set of secondary' N-GNSS-based positioning schemes for a (NTN)-based communication function, wherein the NTN-based communication function is associated with a primary GNSS-based positioning scheme.

[0011] In an aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: determine to utilize a secondary non-Global Navigation Satellite System (N-GNSS)-based positioning scheme to support a non-terrestrial entity (NTN)-based communication function instead of a primary GNSS-based positioning scheme based on a set of conditions; obtain a N-GNSS-based location estimate of the UE based on the N-GNSS- based positioning scheme; and perform the NTN-based communication function based on the N-GNSS-based location estimate in accordance with the determination.

[0012] In an aspect, a non -transitory’ computer-readable medium storing computer-executable instructions that, when executed by a network component, cause the network component to: receive, from a user equipment (UE), non-Global Navigation Satellite System (N-QC2500095WOQualcomm Ref. No. 2500095WO4 / 85GNSS)-based positioning scheme capability information of tire UE; and transmit, to the UE in response to the N-GNSS-based positioning scheme capability information, N- GNSS-based positioning scheme information associated with a set of secondary N- GNSS-based positioning schemes for a (NTN)-based communication function, wherein the NTN-based communication function is associated with a primary GNSS-based positioning scheme.

[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, 2B, and 2C 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 equipmen t (UE), a base station, and a network entity, respectively, and configured to support communications as taught herein.

[0018] FIG. 4 illustrates an example Long-Term Evolution (LTE) positioning protocol (LPP) call flow between a UE and a location server for performing positioning operations.

[0019] FIG. 5 illustrates a non-terrestrial entity (NTN) pre-compensation scheme, in accordance with aspects of the disclosure.

[0020] FIG. 6 illustrates a NTN pre-compensation scheme, in accordance with aspects of the disclosure.

[0021] FIG. 7 illustrates a NTN communications scheme, in accordance with aspects of the disclosure.

[0022] FIG. 8 illustrates a Global Navigation Satellite System (GNSS) validity’ timing scenario, in accordance with aspects of the disclosure.QC2500095WOQualcomm Ref. No. 2500095WO5 / 85

[0023] FIG. 9 illustrates a GNSS validity timing scenario, in accordance with aspects of the disclosure.

[0024] FIG. 10 illustrates a GNSS validity timing scenario, in accordance with aspects of the disclosure.

[0025] FIG. 11 illustrates an exemplary process of communications according to an aspect of the disclosure.

[0026] FIG. 12 illustrates an exemplary process of communications according to an aspect of the disclosure,

[0027] FIG. 13 illustrates an example implementation of the processes of FIGS. 11-12, respectively, in accordance with aspects of the disclosure.

[0028] FIG. 14 illustrates an example implementation of the processes of FIGS. 11-12, respectively, in accordance with aspects of the disclosure,

[0029] FIG. 15 illustrates an example implementation of the processes of FIGS. 11-12, respectively, in accordance with aspects of the disclosure.DETAILED DESCRIPTION

[0030] 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 omi tted so as not to obscure the relevant details of the disclosure.

[0031] In some designs, user equipment (UE) location fix may be determined and utilized for non-terrestrial network (NTN)-based communication functions such as timing advance (TA) compensation, frequency compensation, mobility, etc. In some designs, the positioning technology utilized for UE location fixes for supporting NTN-based communication functions is Global Navigation Satellite System (GNSS)-based. However, in cases where GNSS-based positioning is not available, the performance of the NTN-based communication functions may be degraded.

[0032] Aspects of the disclosure are directed to non-terrestrial network (NTN)-based communication function based on location estimate of a user equipment (UE). In an aspect, the NTN-based communication function is associated with a primary Global Navigation Satellite System (N-GNSS)-based positioning scheme and secondary non-QC2500095WOQualcomm Ref. No. 2500095WO6 / 85GNSS (N-GNSS)-based positioning scheme(s). In an aspect, the N-GNSS-based positioning scheme(s) are utilized for the location estimate if certain condition(s) are satisfied. Such aspects may provide various technical advantages, such as improved performance associated with NTN-based communication function(s) that rely on N- GNSS-based location estimate(s).

[0033] Tire 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.

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

[0035] 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,

[0036] 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), unlessQC2500095WOQualcomm Ref. No. 2500095WO7 / 85otherwise 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.

[0037] A base station may operate according to one of several RATs in communication with UEs depending on the network in which it is deploy ed, 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.QC2500095WOQualcomm Ref. No. 2500095WO8 / 85

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

[0039] 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).

[0040] 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.QC2500095WOQualcomm Ref. No. 2500095WO9 / 85

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

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

[0043] 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,QC2500095WOQualcomm Ref. No. 2500095WO10 / 85positioning, and delivery’ of warning messages. Tire 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.[0044j 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.

[0045] 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).QC2500095WOQualcomm Ref. No. 2500095WO11 / 85

[0046] 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 abase 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).

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

[0048] 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®.

[0049] 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.QC2500095WOQualcomm Ref. No. 2500095WO12 / 85The 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.

[0050] 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 a beam of RF w aves 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.

[0051] 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 theQC2500095WOQualcomm Ref. No. 2500095WO13 / 85same 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,

[0052] 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 recei ver 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,

[0053] 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,

[0054] 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.QC2500095WOQualcomm Ref. No. 2500095WO14 / 85

[0055] 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 FRI 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 TELECOMMUNICATION UNION® as a “millimeter wave” band.

[0056] Hie frequencies between FRI and FR2 are often referred to as mid-band frequencies.Recent 5G NR 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 FRI and / or FR2 into mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR 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.

[0057] 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 FRI, 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.

[0058] 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., FRI) utilized by a UE 104 / 182 and the cell inQC2500095WOQualcomm Ref. No. 2500095WO15 / 85which 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 tire 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’ earners. 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.

[0059] For example, still referring to FIG. 1, one of the frequencies utilized by the macro cell base stations 102 may be an anchor earner (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.

[0060] Tire 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,

[0061] In some cases, the UE 164 and the UE 182 may be capable of side link communication.Sidelink-capable UEs (SL-UEs) may communicate with base stations 102 overQC2500095WOQualcomm Ref. No. 2500095WO16 / 85communication 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. Side link communication may be unicast or multicast, and may be used for device-to-device (D2D) media-sharing, vehicle-to-vehicle (V2V) communication, vehicle-to-everything (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 side link 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.

[0062] In an aspect, the sidelink 160 may operate over a wireless communication medium of interest, w hich may be shared with other wireless communications between other vehicles and / or infrastructure access points, as w7ell 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 w ith 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 notablyQC2500095WOQualcomm Ref. No. 2500095WO17 / 85IEEE 802.11x 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.

[0063] 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 beamfonning, any of the illustrated UEs, including UE 164, may be capable of beamforming. Where SL-UEs are capable of beamfonning, 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.

[0064] 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 SV s 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 SV s 112.

[0065] 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 systemQC2500095WOQualcomm Ref. No. 2500095WO18 / 85(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.

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

[0067] Tire 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-de vice (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), WI-FI DIRECT®, BLUETOOTH®, and so on.

[0068] 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 directlyQC2500095WOQualcomm Ref. No. 2500095WO19 / 85communicate 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),

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

[0070] FIG. 2B illustrates another example wireless network structure 240. 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 (U SIM), the AMF 264 retrievesQC2500095WOQualcomm Ref. No. 2500095WO20 / 85the security material from the AUSF. Tire 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.

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

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

[0073] Another optional aspect may include an LMF 270, which may be in communication with the 5GC 260 to provide location assistance for UEs 204. Tire 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 multipleQC2500095WOQualcomm Ref. No. 2500095WO21 / 85physical 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).

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

[0075] 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 ‘TN2” 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.

[0076] 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 theQC2500095WOQualcomm Ref. No. 2500095WO22 / 85gNB-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 2.04 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.

[0077] Deployment of communication systems, such as 5G NR systems, may be arranged in multiple manners with various components or constituent parts. In a 5G NR system, or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, or a network equipment, such as a base station, or one or more units (or one or more components) performing base station functionality, may be implemented in an aggregated or disaggregated architecture. For example, a base station (such as a Node B (NB), evolved NB (eNB), NR base station, 5G NB, AP, TRP, cell, etc.) may be implemented as an aggregated base station (also known as a standalone base station or a monolithic base station) or a disaggregated base station.

[0078] An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed throughout one or multiple other RAN nodes, The DUs may be implemented to communicate with one or more RUs. Each of the CU, DU and RU also can be implemented as virtual units, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).QC2500095WOQualcomm Ref. No. 2500095WO23 / 85

[0079] Base station-type operation or network design may consider aggregation characteristics of base station functionality. For example, disaggregated base stations may be utilized in an integrated access backhaul (IAB) network, an open radio access network (0-RAN (such as the network configuration sponsored by the O-RAN ALLIANCE®)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C- RAN)). Disaggregation may include distributing functionality across two or more units at various physical locations, as well as distributing functionality for at least one unit virtually, which can enable flexibility in network design, The various units of the disaggregated base station, or disaggregated RAN architecture, can be configured for wired or wireless communication with at least one other unit.

[0080] FIG. 2C illustrates an example disaggregated base station architecture 250, according to aspects of the disclosure. The disaggregated base station architecture 250 may include one or more central units (CUs) 280 (e.g., gNB-CU 226) that can communicate directly with a core network 267 (e.g., 5GC 210, 5GC 260) via a backhaul link, or indirectly with the core network 267 through one or more disaggregated base station units (such as a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) 259 via an E2 link, or a Non-Real Time (Non-RT) RIC 257 associated with a Service Management and Orchestration (SMO) Framework 255, or both). A CU 280 may communicate with one or more DUs 285 (e.g., gNB-DUs 228) via respective midhaul links, such as an Fl interface. The DUs 285 may communicate with one or more radio units (RUs) 287 (e.g., gNB-RUs 229) via respective fronthaul links. The RUs 287 may communicate with respective UEs 204 via one or more radio frequency (RF) access links. In some implementations, the UE 204 may be simultaneously served by multiple RUs 287.

[0081] Each of tire units, i.e., the CUs 280, the DUs 285, the RUs 287, as well as the Near-RT RICs 259, the Non-RT RICs 257 and the SMO Framework 255, may include one or more interfaces or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of tlie units, or an associated processor or controller providing instructions to the communication interfaces of the units, can be configured to communicate with one or more of the other units via the transmission medium. For example, the units can include a wired interface configured to receive or transmit signals over a wired transmission medium to one or more of the other units. Additionally, the units can include a wirelessQC2500095WOQualcomm Ref. No. 2500095WO24 / 85interface, which may include a receiver, a transmitter or transceiver (such as a RF transceiver), configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.

[0082] In some aspects, the CU 280 may host one or more higher layer control functions. Such control functions can include RRC, PDCP, service data adaptation protocol (SDAP), or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 280. Tire CU 280 may be configured to handle user plane functionality (i.e., Central Unit - User Plane (CU- UP)), control plane functionality (i.e., Central Unit – Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 280 can be logically split into one or more CU-UP units and one or more CU-CP units, The CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as the El interface when implemented in an O-RAN configuration. Tire CU 280 can be implemented to communicate with the DU 285, as necessary, for network control and signaling.

[0083] The DU 285 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 287. In some aspects, the DU 285 may host one or more of a RLC layer, a MAC layer, and one or more high PHY layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, or the like) depending, at least in part, on a functional split, such as those defined by the 3rd Generation Partnership Project (3GPP®). In some aspects, the DU 285 may further host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 285, or with the control functions hosted by the CU 280.

[0084] Lower-layer functionality can be implemented by one or more RUs 287. In some deployments, an RU 287, controlled by a DU 285, may correspond to a logical node that hosts RF processing functions, or low-PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, or the like), or both, based at least in part on the functional split, such as a lower layer functional split. In such an architecture, the RU(s) 287 can be implemented to handle over the air (OTA) communication w ith one or more UEs 204. In some implementations, real-time and non-real-time aspects ofQC2500095WOQualcomm Ref. No. 2500095WO25 / 85control and user plane communication with the RU(s) 287 can be controlled by the corresponding DU 285. In some scenarios, this configuration can enable the DU(s) 285 and the CU 280 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0085] The SMO Framework 255 may be configured to support RAN deployment and provisioning of non -virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 255 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements which may be managed via an operations and maintenance interface (such as an 01 interface). For virtualized network elements, the SMO Framework 255 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 269) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an 02 interface). Such virtualized network elements can include, but are not limited to, CUs 280, DUs 285, RUs 287 and Near-RT RICs 259. In some implementations, the SMO Framework 255 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 261, via an 01 interface. Additionally, in some implementations, the SMO Framework 255 can communicate directly with one or more RUs 287 via an 01 interface. The SMO Framework 255 also may include a Non-RT RIC 257 configured to support functionality of the SMO Framework 255.

[0086] The Non-RT RIC 257 may be configured to include a logical function that enables non- real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updates, or policy-based guidance of applications / features in the Near-RT RIC 259. The Non-RT RIC 257 may be coupled to or communicate with (such as via an Al interface) the Near- RT RIC 259. The Near-RT RIC 259 may be configured to include a logical function that enables near-real-time control and optimization of RAN elemen ts and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 280, one or more DUs 285, or both, as well as an O-eNB, with the Near-RT RIC 259.

[0087] In some implementations, to generate AI / ML models to be deployed in the Near-RT RIC 259, the Non-RT RIC 257 may receive parameters or external enrichment informationQC2500095WOQualcomm Ref. No. 2500095WO26 / 85from external servers. Such information may be utilized by the Near-RT RIC 259 and may be received at the SMO Framework 255 or the Non-RT RIC 257 from non-network data sources or from network functions. In some examples, the Non-RT RIC 257 or the Near-RT RIC 259 may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 257 may monitor long-term trends and patterns for performance and employ AI / ML models to perform corrective actions through the SMO Framework 255 (such as reconfiguration via 01) or via creation of RAN management policies (such as Al policies),

[0088] 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 tire 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 operations described 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,

[0089] 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 ofQC2500095WOQualcomm Ref. No. 2500095WO27 / 85interest (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.

[0090] 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., Wi-Fi, LTE Direct, BLUETOOTH®, ZIGBEE®, Z-WAVE®, PC5, dedicated short-range communications (DSRC), wireless access for vehicular environments (WAVE), near-field communication (NFC), ultra- wideband (UWB), 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 Wi-Fi transceivers, BLUETOOTH® transceivers, ZIGBEE® and / or Z-WAVE® transceivers, NFC transceivers, UWB transceivers, or vehicle-to-vehicle (V2V) and / or vehicle-to- everything (V2X) transceivers.QC2500095WOQualcomm Ref. No. 2500095WO28 / 85

[0091] The UE 302 and the base station 304 also include, at least in some cases, satellite signal interfaces 330 and 370, which each include one or more satellite signal receivers 332 and 372, respectively, and may optionally include one or more satellite signal transmitters 334 and 374, respectively. In some cases, the base station 304 may be a terrestrial base station that may communicate with space vehicles (e.g., space vehicles 112) via the satellite signal interface 370. In other cases, the base station 304 may be a space vehicle (or other non-terrestrial entity) that uses the satellite signal interface 370 to communicate with terrestrial networks and / or other space vehicles.

[0092] The satellite signal receivers 332 and 372 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 receiver(s) 332 and 372 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 (NA VIC), Quasi-Zenith Satellite System (QZSS) signals, etc. Where the satellite signal receiver(s) 332 and 372 are nonterrestrial 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 receiver(s) 332 and 372 may comprise any suitable hardware and / or software for receiving and processing satellite positioning / communication signals 338 and 378, respectively. The satellite signal receiver(s) 332 and 372 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.

[0093] The optional satellite signal transmitter(s) 334 and 374, when present, may be connected to the one or more antennas 336 and 376, respectively, and may provide means for transmitting satellite positioning / communication signals 338 and 378, respectively. Where the satellite signal transmitter(s) 374 are satellite positioning system transmitters, the satellite positioning / communication signals 378 may be GPS signals, GLONASS® signals, Galileo signals, Beidou signals, NAVIC, QZSS signals, etc. Where the satellite signal transmitter(s) 334 and 374 are NTN transmitters, the satelliteQC2500095WOQualcomm Ref. No. 2500095WO29 / 85positioning / 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 transmitter(s) 334 and 374 may comprise any suitable hardware and / or software for transmitting satellite positioning / communication signals 338 and 378, respectively, The satellite signal transmitter(s) 334 and 374 may request information and operations as appropriate from the other systems.

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

[0095] 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 anQC2500095WOQualcomm Ref. No. 2500095WO30 / 85aspect, 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.

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

[0097] 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, lire UE 302, the base station 304, and the network entity 306 include one or more processors 342, 384, and 394, respectively, for providing functionality relating to, for example, wireless communication, and for providing other processing functionality. The processors 342, 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 342, 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.

[0098] The UE 302, the base station 304, and tire 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 mayQC2500095WOQualcomm Ref. No. 2500095WO31 / 85therefore 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 NTN component 348, 388, and 398, respectively. The NTN component 348, 388, and 398 may be hardware circuits that are part of or coupled to the processors 342, 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 NTN component 348, 388, and 398 may be external to the processors 342, 384, and 394 (e.g., part of a modem processing system, integrated with another processing system, etc.). Alternatively, the NTN component 348, 388, and 398 may be memory modules stored in the memories 340, 386, and 396, respectively, that, when executed by the processors 342, 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. 3 A illustrates possible locations of the NTN component 348, which may be, for example, part of the one or more WWAN transcei vers 310, the memory 340, the one or more processors 342, or any combination thereof, or may be a standalone component. FIG. 3B illustrates possible locations of the NTN 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 NTN 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.

[0099] The UE 302 may include one or more sensors 344 coupled to the one or more processors 342 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 interface 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 m ovement 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 aQC2500095WOQualcomm Ref. No. 2500095WO32 / 85combination 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.

[0100] 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,

[0101] 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. Tire 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.

[0102] Tire 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 constellationsQC2500095WOQualcomm Ref. No. 2500095WO33 / 85based 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. Tire transmitter 354 may modulate an RF carrier with a respective spatial stream for transmission.

[0103] 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 342. 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 342, which implements Layer-3 (L3) and Layer-2 (L2) functionality.QC2500095WOQualcomm Ref. No. 2500095WO34 / 85

[0104] In the downlink, the one or more processors 342 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 342 are also responsible for error detection.

[0105] Similar to the functionality described in connection with the downlink transmission by the base station 304, the one or more processors 342 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.

[0106] 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 tire 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.

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

[0108] 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. Tire one or more processors 384 are also responsible for error detection.QC2500095WOQualcomm Ref. No. 2500095WO35 / 85

[0109] 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 personal computer (PC) or laptop may have Wi-Fi and / or BLUETOOTH®1capability without cellular capability), or may omit the short- range wireless transceiver(s) 320 (e.g., cellular-only, etc.), or may omit the satellite signal interface 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 signal interface 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.

[0110] Tire 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 308, 382, and 392, respectively. In an aspect, the data buses 308, 382, and 392 may form, or be part of, a communication interface of tire 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 308, 382, and 392 may provide communication between them.

[0111] Tire components of FIGS, 3A, 3B, and 3C may be implemented in various ways. In some implementations, the components of FIGS. 3A, 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 andQC2500095WOQualcomm Ref. No. 2500095WO36 / 85memory components) of tire 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 342, 384, 394, the transceivers 310, 320, 350, and 360, the memories 340, 386, and 396, the NTN component 348, 388, and 398, etc.

[0112] 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 Wi-Fi).

[0113] 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 L IE, downlink time difference of arrival (DL-TDOA) in NR, and downlink angle-of-departure (DL-AoD) in NR, In an OTDOA or DL-TDOA positioning procedure, 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 RSTDQC2500095WOQualcomm Ref. No. 2500095WO37 / 85between 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.

[0114] For DL-AoD positioning, the positioning entity uses a measurement 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).

[0115] 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 to multiple base stations. Specifically, a UE transmits one or more uplink reference signals that are measured by a reference base station and a plurality of non-reference base stations. Each base station then reports the reception time (referred to as the relative time of arrival (RTOA)) of the reference signal(s) to a positioning entity (e.g., a location server) that knows the locations and relative timing of the involved base stations. Based on the reception-to-reception (Rx-Rx) time difference between the reported RTOA of the reference base station and the reported RTOA of each non-reference base station, the known locations of the base stations, and their known timing offsets, the positioning entity can estimate the location of the UE using TDOA.

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

[0117] 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 toQC2500095WOQualcomm Ref. No. 2500095WO38 / 85the 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 slot 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), 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, 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.

[0118] Tire 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).

[0119] 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 slots including PRS, periodicity of the consecutive slots including PRS, 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 stationsQC2500095WOQualcomm Ref. No. 2500095WO39 / 85themselves (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.

[0120] 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 (jis). 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 us 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 us.

[0121] 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).

[0122] FIG. 4 illustrates an example Long-Term Evolution (LTE) positioning protocol (LPP) procedure 400 between a UE 404 and a location server (illustrated as a location management function (LMF) 470) for performing positioning operations. As illustrated in FIG. 4, positioning of the UE 404 is supported via an exchange of LPP messages between the UE 404 and the LMF 470. The LPP messages may be exchanged between UE 404 and the LMF 470 via the UE's 404 serving base station (illustrated as a serving gNB 402) and a core network (not shown). The LPP procedure 400 may be used to position the UE 404 in order to support various location-related services, such as navigation for UE 404 (or for the user of UE 404), or for routing, or for provision of an accurate location to a public safety answering point (PSAP) in association with an emergency call from UE 404 to a PSAP, or for some other reason, Tire LPP procedure 400 may also be referred to as a positioning session, and there may be multiple positioningQC2500095WOQualcomm Ref. No. 2500095WO40 / 85sessions for different types of positioning methods (e.g., downlink time difference of arrival (DL-TDOA), round-trip-time (RTT), enhanced cell identity (E-CID), etc.).[0123J Initially, the UE 404 may receive a request for its positioning capabilities from the LMF 470 at stage 410 (e.g., an LPP Request Capabilities message). At stage 420, the UE 404 provides its positioning capabilities to the LMF 470 relative to the LPP protocol by sending an LPP Provide Capabilities message to LMF 470 indicating the position methods and features of these position methods that are supported by the UE 404 using LPP. The capabilities indicated in the LPP Provide Capabilities message may, in some aspects, indicate the type of positioning the UE 404 supports (e.g., DL-TDOA, RTT, E- CID, etc.) and may indicate tire capabilities of the UE 404 to support those types of positioning.

[0124] Upon reception of the LPP Provide Capabilities message, at stage 420, the LMF 470 determines to use a particular type of positioning method (e.g., DL-TDOA, RTT, E-CID, etc.) based on the indicated type(s) of positioning the UE 404 supports and determines a set of one or more transmission-reception points (TRPs) from which the UE 404 is to measure downlink positioning reference signals or towards which the UE 404 is to transmit uplink positioning reference signals. At stage 430, the LMF 470 sends an LPP Provide Assistance Data message to the UE 404 identifying the set of TRPs.

[0125] In some implementations, the LPP Provide Assistance Data message at stage 430 may be sent by the LMF 470 to the UE 404 in response to an LPP Request Assistance Data message sent by the UE 404 to the LMF 470 (not shown in FIG. 4). An LPP Request Assistance Data message may include an identifier of the UE’s 404 serving RI3and a request for the positioning reference signal (PRS) configuration of neighboring TRPs.

[0126] At stage 440, the LMF 470 sends a request for location information to the UE 404. The request may be an LPP Request Location Information message. This message usually includes information elements defining the location information type, desired accuracy of the location estimate, and response time (i.e., desired latency). Note that a low latency requirement allows for a longer response time while a high latency requirement requires a shorter response time. However, a long response time is referred to as high latency and a short response time is referred to as low latency.

[0127] Note that in some implementations, the LPP Provide Assistance Data message sent at stage 430 may be sent after the LPP Request Location Information message at 440 if, forQC2500095WOQualcomm Ref. No. 2500095WO41 / 85example, the UE 404 sends a request for assistance data to LMF 470 (e.g., in an LPP Request Assistance Data message, not shown in FIG. 4) after receiving the request for location information at stage 440.

[0128] At stage 450, the UE 404 utilizes the assistance information received at stage 430 and any additional data (e.g., a desired location accuracy or a maximum response time) received at stage 440 to perform positioning operations (e.g., measurements of DL-PRS, transmission of UL-PRS, etc.) for the selected positioning method.

[0129] At stage 460, the UE 404 may send an LPP Provide Location Information message to the LMF 470 conveying the results of any measurements that were obtained at stage 450 (e.g., time of arrival (ToA), reference signal time difference (RSTD), reception-to-transmission (Rx-Tx), etc.) and before or when any maximum response time has expired (e.g., a maximum response time provided by the LMF 470 at stage 440). The LPP Provide Location Information message at stage 460 may also include the time (or times) at which the positioning measurements were obtained and the identity of the TRP(s) from which the positioning measurements were obtained. Note that the time between the request for location information at 440 and the response at 460 is the “response time” and indicates the latency of the positioning session.

[0130] The LMF 470 computes an estimated location of the UE 404 using the appropriate positioning techniques (e.g., DL-TDOA, RTT, E-CID, etc.) based, at least in part, on measurements received in the LPP Provide Location Information message at stage 460.

[0131] NTN-IoT expands the reach of loT use cases, facilitating global coverage over land, sea and air. NTN-IoT operates at geostationary orbits (GSO) at ~ 35,786 km and non-GSO (NGSO), e.g,, LEO (300 ~ 1500 km), MEO (7000 ~ 25000 km), high-altitude platform station (HAPS), and so on. In an aspect, NTN-IoT supports transparent NTN payloads (bent-pipe) and EPC connectivity. In an aspect, NTN-IoT may be supported via Earth fixed beam, Quasi Earth fixed beam, Earth moving beam. In an aspect, NTN-IoT may be supported across an Earth fixed tracking area. In an aspect, loT-NTN may be supported for Cat-M UEs, non-Cat-M UEs supporting a coverage enhancement (CE) mode and / or NB-IoT UEs (e.g., with GNSS capability).

[0132] FIG. 5 illustrates a NTN pre-compensation scheme 500, in accordance with aspects ofthe disclosure. In FIG. 5, a location of a UE is determined based on GNSS signals from a group of NTN entities. Communications over a feeder link experience a feeder link delayQC2500095WOQualcomm Ref. No. 2500095WO42 / 85that is pre -compensated by a common timing advance (TA) between a serving NTN entity and a gateway. Communications over a service link delay between the serving NTN entity and the UE are pre-compensated based on UE ephemeris information and UE location. A backhaul delay between the gateway and gNB is also taken into account based on parameters such as Kmac, As shown at 505, the timing advance on the service link is based on GNSS information, ephemeris information and the common TA.

[0133] Referring to FIG. 5, (1) UE acquires GNSS and derives its location (in RRC IDLE), (2) UE acquires the satellite ephemeris (from SIB) to obtain satellite location and velocity (e.g., while in general, an “orbital propagation model'’ is assumed to predict these into the future from the SIB epoch time, the variations over time may be assumed to be small for GEO, as a first-cut assumption), and (3) UE pre-compensates (in time and frequency) its uplink transmission.

[0134] FIG. 6 illustrates a NTN pre-compensation scheme 600, in accordance with aspects of the disclosure.

[0135] Referring to FIG. 6, in an aspect, the time pre-compensation may be performed in accordance with the following timing advance equation, e.g.:T_TA = (N_TA + N_TA,offset + N_commonTA,adj + N^UE_TA,adj) x T_swhereby N_commonTA, adj denotes common additional delay to compensate for feeder link delay (e.g., based on 3 components from SIB: (i) TA common, (ii) TA common drift, (iii) TA common drift variation),N^UE_TA,adj is based on distance from UE to the serving NTN entity (location and ephemeris).

[0136] Referring to FIG. 6, in an aspect, Aadj is a TA component due to service link. In an aspect, the UE’s locationis determined by obtaining a GNSS fix. In an aspect, the satellite location (L^AT) at is provided in SIB (at tepoch) in one of two ways:

[0137] Set 1: Satellite position and velocity state vectors (position / velocity), e.g.: Position X, Y, Z in ECEF (m), Velocity VX, VY, VZ in ECEF (m / s)

[0138] Set 2: Parameters in orbital parameter ephemeris format, e.g.: Semi-major axis a [m], Eccentricity e, Argument of periapsis co [rad], Longitude of ascending node Q [rad], Inclination i [rad], Mean anomaly M [rad] at epoch time.QC2500095WOQualcomm Ref. No. 2500095WO43 / 85

[0139] Referring to FIG. 6, in an aspect,is derived based on the service link propagation delay: 2 × |L_SAT − L_UE| / c

[0140] With respect to frequency pre -compensation, in an aspect, if the UE transmits at a frequency Fcin the uplink, the satellite will receive it with a Doppler shift of fd— Fcxwhere v “ denotes the relative velocity’ of the UE with respect to the satellite, and 9 is the angle of the relative velocity vector. In an aspect, v^, 9 may be determined from the SIB (for satellite PVT) and GNSS position fix. In an aspect, if the Fcitself is derived from a downlink reference from the satellite, then, the satellite will receive the UL transmission with an effective doppler shift of 2 x fd. Thus, the UE should apply a pre-compensation of 2 X fdfor UL transmission.

[0141] in an aspect, with respect to segmented pre-compensation for uplink transmission, for “long” uplink transmissions, the time and / or frequency pre-compensation may change during the transmission (e.g., due to significant satellite movement). As a result, a UE may “update” the pre-compensation during the long transmission. In an aspect, the precompensation “update” may be performed “segment-wise”, e.g., the time and frequency compensation will remain constant within a segment, and will only change from one segment to another. In an aspect related to at least for NB-IoT, for GSO networks, this feature is not required, since w ithin 256 ms, the time / frequency drift is not expected to be significant enough. In an aspect, depending on UE capability, a UE may indicate a requirement for gaps (dropping slots) from one segment to another.

[0142] In an aspect, for an S-band NTN network, NB-IoT UEs may have a maximum initial frequency error of up to (20 ppm x (2 x 109) + (7.5 x 103) = 47.5 kHz. In an aspect, for terrestrial NB-IoT, the max. initial frequency offset « (20 ppm) X (0.9 X 109) + (7.5 x 103) = 25.5 kHz. In an aspect, there may be additional frequency offsets (FOs) due to satellite movement. Due to this large initial FO, the UE may lock on to an incorrect Nee 11 frequency. In an aspect, to prevent the lock on to an incorrect carrier frequency — following aspects may be implemented, e.g.:• Indicate 2 least Significant Bits (LSBs) of the Absolute Radio Frequency Channel Number (ARFCN) in the MIB.• For bands that can accommodate a larger channel raster step size (than the current raster of 100 kHz), a larger (200 kHz) raster may be specified by RAN4.QC2500095WOQualcomm Ref. No. 2500095WO44 / 85• For those bands, the above solution of indicating 2 LSBs of the ARFCN in MIB will not apply.

[0143] FIG. 7 illustrates a NTN communications scheme 700, in accordance with aspects of the disclosure. In FIG. 7, a UE is served by a serving NTN entity over a serving link, and the UE is in range of three non -serving NTN entities over non-serving links 1, 2 and 3,

[0144] Referring to FIG. 7, assume that the NTN entities are operating in the LEO orbit (600-2000 km), although other orbits are also possible. In an aspect, there is possibility of having multi -NTN satellite based positioning. In an aspect, to support any legacy NR positioning (rel-16, rel-17) techniques, the UE may send an uplink transmission from UE to multiple NTN satellite: e.g., SRS for positioning (SRS-P). In an aspect, the common TA is based only on serving cell SIB 1. In an aspect, the common TA is based on only serving cell Ephemeris. In an aspect, N^UE_TA, adj is used from the serving cell only. In this case, it is difficult to transmit the SRS for positioning (SRS-P) in a manner that will reach the non-serving NTN entities.

[0145] In some designs, with respect to NTN UL synchronization, the UE failing to acquire sufficiently accurate GNSS location to be used in the calculation of the UE’s Timing Advance value may indicate that the UE should not perform any UL transmission. After AS security is established, gNB can obtain GNSS-based location information from the UE network and may configure UE to calculate propagation differential delay and report to network.

[0146] in some designs, in RRC-IDLE state, location-based measurement triggering condition for earth-fixed ceil may include UE being located at a cell edge. In an aspect, a new threshold is defined, i.e., if UE moves X km farther than the reference location. In an aspect, a cell can broadcast serving cell reference location.

[0147] In an aspect, a coarse UE location (e.g. 2kms error) is used for mapping to a tracking aera identifier (TAI) / cell global identity (CGI) in the NG-RAN but may not always be available. When unavailable, the NG-RAN provides a best guess TAI and a CGI that may correspond to a larger area.

[0148] In an aspect, GNSS operations may be performed for a new position fix for UE pre¬ compensation during long connection times and for reduced power consumption.

[0149] In an aspect, in 3GPP Rel-17 IOT NTN operation, UE acquires GNSS before accessing the cell. This GNSS position has a validity duration. UE connects to the cell. If the validityQC2500095WOQualcomm Ref. No. 2500095WO45 / 85duration expires, the UE goes to RRC IDLE (and restarts the process). This operation limits the duration of a connection, which may be limiting in some cases (e.g. voice calls, large file download, etc.). In an aspect, GNSS validity duration is from 10s to 120min (also infinity may be a GNSS validity duration option). In an aspect, one target of this objective is to extend the connection duration to give the UE an opportunity to reacquire GNSS without dropping the connection (but without simultaneous operation). In an aspect, the following two solutions may be implemented, e.g.:• eNB-triggered GNSS reacquisition (with a gap). Tire trigger is based on MAC-CE.• UE autonomous GNSS reacquisition (with a gap / timer).

[0150] In some designs, in the basic operation for “reacquisition”, the UE reports in msg5 the GNSS position fix duration, and the duration of the GNSS measurement gap is configured by eNB. In an aspect, a default value is used for the duration of the GNSS measurement gap if not configured (e.g., in this case, the GNSS position fix duration may be reported by the UE). In an aspect, after successful reacquisition, the UE reports its new validity duration,

[0151] FIG. 8 illustrates a Global Navigation Satellite System (GNSS) validity timing scenario 800, in accordance with aspects of the disclosure. In FIG. 8, a first GNSS validity duration associated with a first GNSS position fix starts at 805, and is reported by UE to NB. At 810, the NB configures a GNSS gap 815. During the GNSS gap 815, the UE acquires a second GNSS position fix, and a second validity duration for the second GNSS position fix starts at 820, which is reported by UE to NB.

[0152] FIG. 9 illustrates a GNSS validity timing scenario 900, in accordance with aspects of the disclosure. In FIG. 9, a first GNSS validity duration associated with a first GNSS position fix starts at 905, and is reported by UE to NB. At 910, the UE acquires a second GNSS position fix during an autonomous GNSS gap. At 915, a second validity duration for tire second GNSS position fix starts and is reported by UE to NB,

[0153] FIG. 10 illustrates a GNSS validity timing scenario 1000, in accordance w ith aspects of the disclosure. In FIG. 10, a first GNSS validity duration associated with a first GNSS position fix starts at 1005, and is reported by UE to NB. At 1010, the NB extends the first GNSS validity duration. At 1015, the NB further extends the first GNSS validity duration,

[0154] In some designs, the start time for autonomous GNSS reacquisition as depicted in FIG. 9 is based on the end of the validity duration (plus “extension”), and the timer is configuredQC2500095WOQualcomm Ref. No. 2500095WO46 / 85by the network. In an aspect, the value set for an autonomous GNSS gap may be selected from { 1,2,3,4,5,6,7,13, 19,25,31 }.

[0155] In some designs, the network trigger performing GNSS reacquisition as depicted in FIG.8 is based on MAC-CE. In an aspect, the start of the GNSS measurement gap depends on whether HARQ is enabled or disabled for the (N)PDSCH carrying the MAC CE. Upon GNSS measurement trigger, the UE starts a GNSS measurement window'. Tire GNSS measurement gap length is configured by the network using a new' MAC CE command. UE indicates the required measurement gap length in Msg5. This value is used as default gap length. Upon GNSS measurement completion, the UE triggers new' GNSS validity report MAC CE, and stops the time alignment timer and triggers RACH. In an aspect, for GNSS fix during C-DRX inactive period, UE is not required to stop time alignment tinier and trigger RACH.

[0156] In some designs, the connection length may be increased to facilitate “closed loop” corrections from the network to account for stale G SS position. A mechanism where the eNB can extend the connection duration was specified. In an aspect, this may be applicable for GEO due to the lack of closed loop frequency corrections. In an aspect, when timeAlignmentTimer is not set to infinity, the “duration X” (T390) is set to the remaining value of timeAlignmenfTimer. In an aspect, for the case of timeAlignmentTimer set to infinity, there is a separate indication introduced for the value of “duration X”, which is among {sf500, sf750, sf1280, sf1920, sf2560, sf5120, sf10240}.

[0157] In some designs, user equipment (UE) location fix may be determined and utilized for non-terrestrial network (NTN)-based communication functions such as timing advance (TA) compensation, frequency compensation, mobility, etc. In some designs, the positioning technology utilized for UE location fixes for supporting NTN-based communication functions is Global Navigation Satellite System (GNSS)-based. However, in cases where GNSS-based positioning is not available, the performance of the NTN-based communication functions may be degraded.

[0158] Aspects of the disclosure are directed to non-terrestrial network (NTN)-based communication function based on location estimate of a user equipment (UE). In an aspect, the NTN-based communication function is associated with a primary Global Navigation Satellite System (N-GNSS)-based positioning scheme and secondary non- GNSS (N-GNSS)-based positioning scheme(s). In an aspect, the N-GNSS-basedQC2500095WOQualcomm Ref. No. 2500095WO47 / 85positioning scheme(s) are utilized for the location estimate if certain condition(s) are satisfied. Such aspects may provide various technical advantages, such as improved performance associated with NTN-based communication function(s) that rely on N- GNSS-based location estimate(s).

[0159] FIG. 11 illustrates an exemplary’ process 1100 of communications according to an aspect of the disclosure. The process 1100 of FIG. 11 is performed by a UE, such as UE 302. Note that in some designs, a position estimation entity is deployed separately from the UE (e.g,, at a network component such as LMF integrated at gNB / BS / TRP 304 or O- RAN component or a remote location server such as network entity 306, etc.). In other designs, the position estimation entity may correspond to another LIE (e.g., sidelink anchor UE or sidelink server UE) or to the UE itself. In scenarios where the position estimation entity is integrated with the UE itself, reference to any Rx / Tx operations between the position estimation entity and the UE in which the position estimation entity is integrated may correspond to transfer of information between different logical components of the device over a data bus, etc.

[0160] Referring to FIG. 11, at 1110, the UE (e.g., processor(s) 342, NTN component 348, etc.) determines to utilize a secondary non-Global Navigation Satellite System (N-GNSS)- based positioning scheme to support a non-terrestrial entity (NTN)-based communication function instead of a primary GNSS-based positioning scheme based on a set of conditions. In some designs, a means for performing the determination of 1110 includes processor(s) 342, NTN component 348, etc., of FIG. 3A.

[0161] Referring to FIG. 11, at 1120, the UE (e.g., processor(s) 342, NTN component 348, transmitter 314 or 324, receiver 312 or 322, etc.) obtains a N-GNSS-based location estimate of the UE based on the N-GNSS-based positioning scheme. In some designs, a means for obtaining the location estimate at 1120 includes processor(s) 342, NTN component 348, transmitter 314 or 324, receiver 312 or 322, etc., of FIG. 3A.

[0162] Referring to FIG. 11, at 1120, tire UE (e.g., processor(s) 342, NTN component 348, transmitter 314 or 324 or 334, receiver 312 or 322 or 332, etc.) obtains a N-GNSS-based location estimate of the UE based on the N-GNSS-based positioning scheme. In some designs, a means for obtaining the location estimate at 1120 includes processor(s) 342, NTN component 348, transmitter 314 or 324, receiver 312 or 322, etc., of FIG. 3A.QC2500095WOQualcomm Ref. No. 2500095WO48 / 85

[0163] Referring to FIG. 11, at 1130, the UE (e.g,, processor(s) 342, NTN component 348, transmitter 334, receiver 332, etc.) performs the NTN-based communication function based on the N-GNSS-based location estimate in accordance with the determination. In some designs, a means for performing the NTN-based communication function at 1130 includes processor(s) 342, NTN component 348, transmitter 334, receiver 332, etc., of FIG. 3A.

[0164] Referring to FIG. 11, in some designs, the N-GNSS-based positioning scheme corresponds to a terrestrial network (TN)-based, UE-based positioning scheme or a NTN- based positioning scheme associated with a low earth orbit (LEO) constellation.

[0165] Referring to FIG. 11, in some designs, the set of conditions comprises, e.g.:• expiration or near-expiration (e.g., within some threshold) of one or more location validity timers associated with a GNSS-based location estimate of the UE, or • a determination that a GNSS-based location estimate attempt has failed, or• detection that the primary GNSS-based positioning scheme is unavailable and that the secondary N-GNSS-based positioning scheme is available, or• detection that the N-GNSS-based location estimate is available, that the N-GNSS- based positioning scheme produces N-GNSS-based location estimates that match or correspond to GNSS-based location estimates for a period of time, or• any combination thereof.

[0166] Referring to FIG. 11, in some designs, the UE further transmits, to a wireless network component, capability information of the UE associated with a set of N-GNSS-based positioning schemes, and receives, from the wireless network component, N-GNSS-based positioning scheme information associated with one or more of the set of N-GNSS-based positioning schemes in response to the capability information. In an aspect, the N-GNSS- based location estimate is obtained based on the N-GNSS-based positioning scheme information.

[0167] Referring to FIG. 11, in some designs, the N-GNSS-based positioning scheme information comprises a preferred N-GNSS-based positioning scheme or a set of preferred N-GNSS-based positioning schemes, or the N-GNSS-based positioning scheme information composes a set of rules for N-GNSS-based positioning scheme selection, and the set of conditions is determined based on an evaluation of the set of rules, or the N- GNSS-based positioning scheme information comprises a ranked list of positioningQC2500095WOQualcomm Ref. No. 2500095WO49 / 85schemes for successive performance until an acceptable N-GNSS-based location measurement is obtained at a threshold level of quality, or any combination thereof.

[0168] Referring to FIG. 11, in some designs, the N-GNSS-based positioning scheme information is received via medium access control control element (MAC-CE).

[0169] Referring to FIG. 11, in some designs, the capability information comprises, e g,:• a first capability of the UE to support the set of N-GNSS-based positioning schemes, or• a second capability of the UE to support one or more N-GNSS-based positioning schemes from the set of N-GNSS-based positioning schemes with a measurement gap, or• a third capability of the UE to support at least one N-GNSS-based positioning scheme from the set of secondary N-GNSS-based positioning schemes with one or more respective scheme-specific measurement gaps, or• any combination thereof.

[0170] Referring to FIG. 11, in some designs, the UE further transmits a measurement report comprising an indication of a N-GNSS-based positioning scheme used to obtain the N- GNSS-based location estimate.

[0171] Referring to FIG. 11, in some designs, the UE further attempts to obtain a location estimate of the UE in accordance with a positioning scheme sequence that is based on a ranked list of N-GNSS-based positioning schemes. In an aspect, the N-GNSS-based location estimate corresponds to an earliest successful location estimate attempt based on the ranked list of N-GNSS-based positioning schemes, In an aspect, the ranked list of N-GNSS-based positioning schemes is UE-determined, network-configured or pre-defined.

[0172] Referring to FIG. 11, in some designs, the N-GNSS-based location estimate is associated with a set of location validity timers, and the N TN -based communication function is performed based on the N-GNSS-based location estimate while the set of location validity timers is valid. In an aspect, the set of location validity timers comprises a single location validity timer associated with the GNSS-based positioning scheme and the N-GNSS- based positioning scheme, or the set of location validity timers comprises a first location validity timer associated with the GNSS-based positioning scheme and a second location validity timer associated with the N-GNSS-based positioning scheme.QC2500095WOQualcomm Ref. No. 2500095WO50 / 85

[0173] Referring to FIG. 11, in some designs, the N-GNSS-based location estimate is determined at the UE based on one or more measurement gaps. In an aspect, the one or more measurement gaps are N-GNSS-based positioning scheme-specific. In an aspect, the one or more measurement gaps comprise one or more network-configured measurement gaps, or the one or more measurements gaps comprise one or more autonomous measurement gaps, or a combination thereof.

[0174] Referring to FIG. 11, in some designs, the NTN-based communication function comprises, e.g.:• derivation of a timing advance value associated with uplink synchronization between the UE and a NTN entity, or• reporting of first propagation delay information associated with the GNSS-based positioning scheme, or• reporting of second propagation delay information associated with the N-GNSS- based positioning scheme, or• one or more RRC-IDLE mode functions, or• one or more mobility functions, or• any combination thereof.

[0175] FIG. 12 illustrates an exemplary process 1200 of communications according to an aspect of the disclosure. Tire process 1200 of FIG. 12 is performed by a network component. In some designs, the network component may correspond to a wireless network component (e.g., gNB / BS / TRP 304 or O-RAN component such as RU) or other network component (e.g., a remote location server (e.g., LMF) such as network entity 306, etc.). In other designs, the device may correspond to a UE (e.g., sidelink anchor UE or sidelink server UE or target UE). In scenarios where the network component is integrated with another device (e.g., UE, gNB / BS / TRP, LMF, etc.), reference to any Rx / Tx operations between the network component and the other device in which the network component is integrated may correspond to transfer of information between different logical components of the device over a data bus, etc.

[0176] Referring to FIG. 12, at 1210, the network component (e.g., receiver 312 or 322 or 332 or 352 or 362 or 372, network transceiver(s) 380 or 390, etc.) receives, from a user equipment (UE), non-Global Navigation Satellite System (N-GNSS)-based positioning scheme capability information of the UE. In some designs, a means for performing theQC2500095WOQualcomm Ref. No. 2500095WO51 / 85reception of 1210 includes receiver 312 or 322 or 332 or 352 or 362 or 372, network transceiver(s) 380 or 390, etc., of FIGS. 3A-3C.

[0177] Referring to FIG. 12, at 1220, the network component (e.g., transmitter 314 or 324 or 334 or 354 or 364 or 374, network transceiver(s) 380 or 390, etc.) transmits, to the UE in response to the N-GNSS-based positioning scheme capability information, N-GNSS- based positioning scheme information associated with a set of secondary' N-GNSS-based positioning schemes for a (NTN)-based communication function. In some designs, a means for performing the transmission of 1220 includes transmitter 314 or 324 or 334 or 354 or 364 or 374, network transceiver(s) 380 or 390, etc., of FIGS. 3A-3C.

[0178] Referring to FIG. 12, in some designs, the set of N-GNSS-based positioning schemes comprises one or more terrestrial network (TN)-based, UE-based positioning schemes, one or more NTN-based positioning schemes associated with one or more respective low earth orbit (LEO) constellations, or a combination thereof.

[0179] Referring to FIG. 12, in some designs, the N-GNSS-based positioning scheme information comprises a preferred N-GNSS-based positioning scheme or a set of preferred N-GNSS-based positioning schemes, or the N-GNSS-based positioning scheme information comprises a set of rules for N-GNSS-based positioning scheme selection, or the N-GNSS-based positioning scheme information comprises a ranked list of positioning schemes for successive performance until an acceptable N-GNSS-based location measurement is obtained at a threshold level of quality, or any combination thereof. In an aspect, the N-GNSS-based positioning scheme information is transmitted via medium access control control element (MAC-CE).

[0180] Referring to FIG. 12, in some designs, the capability information comprises, e.g.:• a first capability of the UE to support the set of secondary N-GNSS-based positioning schemes, or® a second capability of the UE to support one or more secondary' N-GNSS-based positioning schemes from the set of secondary N-GNSS-based positioning schemes with a measurement gap, or® a third capability of tire UE to support at least one secondary / N-GNSS-based positioning scheme from the set of secondary N-GNSS-based positioning schemes with one or more respective scheme-specific measurement gaps, or• any combination thereof.QC2500095WOQualcomm Ref. No. 2500095WO52 / 85

[0181] Referring to FIG, 12, in some designs, the N-GNSS-based positioning scheme information is associated with evaluation of a set of conditions, the set of conditions comprising, e.g.:• expiration or near-expiration of one or more location validity timers associated with a GNSS-based location estimate of the UE, or• a determination that a GNSS-based location estimate attempt has failed, or• detection that the primary GNSS-based positioning scheme is unavailable and that the secondary N-GNSS-based positioning scheme is available, or® detection that the N-GNSS-based location estimate is available, that the N-GNSS- based positioning scheme produces N-GNSS-based location estimates that match or correspond to GNSS-based location estimates for a period of time, or• any combination thereof.

[0182] Referring to FIG. 12, in some designs, the network component further receives a measurement report comprising an indication of a N-GNSS-based positioning scheme used by the UE to obtain a N-GNSS-based location estimate associated with the NTN- based communication function. In an aspect, the N-GNSS-based location estimate corresponds to an earliest successful location estimate attempt by the UE based on a ranked list of N-GNSS-based positioning schemes. In an aspect, the ranked list of ranked list of N-GNSS-based positioning schemes is UE-determined, network-configured or predefined. In an aspect, the N-GNSS-based location estimate is associated with a set of location validity timers, and the NTN -based communication function is performed based on tire N-GNSS-based location estimate while the set of location validity timers is valid. In an aspect, the set of location validity’ timers comprises a single location validity timer associated with the primary GNSS-based positioning scheme and the set of secondary' N- GNSS-based positioning schemes, or the set of location validity’ timers comprises a first location validity timer associated with the primary’ GNSS-based positioning scheme and at least one second location validity timer associated w ith the set of secondary N-GNSS- based positioning schemes.

[0183] Referring to FIG. 12, in some designs, the N-G SS-based location estimate is determined at the UE based on one or more measurement gaps. In an aspect, the one or more measurement gaps are N-GNSS-based positioning scheme-specific. In an aspect, the one or more measurement gaps comprise one or more network-configured measurement gaps,QC2500095WOQualcomm Ref. No. 2500095WO53 / 85or the one or more measurements gaps comprise one or more autonomous measurement gaps, or a combination thereof.

[0184] Referring to FIG. 12, in some designs, the NTN-based communication function comprises:• derivation of a timing advance value associated with uplink synchronization between the UE and a NTN entity, or• reporting of first propagation delay information associated with the primary’ GNSS- based positioning scheme, or• reporting of second propagation delay information associated with a secondary N- GNSS-based positioning scheme from the set of secondary N-GNSS-based positioning schemes, or• one or more RRC-IDLE mode functions, or• one or more mobility functions, or• any combination thereof.

[0185] Referring to FIGS. 11-12, in a specific example, for NTN communication purposes, for the UE to derive the UE location, the UE may use one of the other technologies (e.g., N- GNSS technologies, such as Wi-Fi, cellular or NR-based positioning, Bluetooth-based positioning, a different LEO constellation than the one used for NTN communication, Ultra wideband (UWB)-based positioning, etc.) to derive a new location estimate, when the GNSS validity timer expires, or when the GNSS acquisition fails. In an aspect, a device (e.g., UE) may try’ a specific technology to use in such occasions under specific conditions of GNSS events. In an aspect, the device (e.g., UE) may' be configured with one, or multiple such secondary' technologies and there may be a priority / preference order for each one. For example, if the GNSS validity timer is bound to expire and the UE is within X-technology coverage and has a valid location from that X technology' which matches (within some bounds and for some period of time) with the GNSS location, then the UE transitions some or all of its location -based NTN-based communication functionalities using that location estimate. In an aspect, the “GNSS validity timer” described above with respect to FIGS. 8-10 may be generalized to a “location validity timer”, or there may be a validity timer per technology, or a “GNSS validity timer” and “other / secondary technology validity timer”.QC2500095WOQualcomm Ref. No. 2500095WO54 / 85

[0186] Referring to FIGS. 11-12, in a specific example, a UE may report its capability to derive a UE based on other technologies beyond GNSS. In an aspect, an eNB can trigger one or more of those technologies for reacquisition of a valid location. In an aspect, the MAC- CE command may contain the preferred technology or multiple technologies, or the MAC-CE command may contain an indication that: ‘"reacquire GNSS, unless the conditions for acquiring a valid location through another technology are satisfied ’. In an aspect, a UE may report whether it requires gap, and the length of the gap for any of the other technologies. In an aspect, the UE may report whether eventually it used another technology to derive a valid location.

[0187] Referring to FIGS. 11-12, in a specific example and as noted above, the UE may report its capability to derive a UE based on other technologies beyond GNSS. An eNB can trigger one or more of those technologies for reacquisition of a valid location. The MAC- CE command may contain the preferred technology or multiple technologies, or it may contain an indication that: “reacquire GNSS, unless the conditions for acquiring a valid location through another technology are satisfied”. A UE may report whether it requires gap, and the length of the gap for any of the other technologies. A UE may report whether eventually it used another technology to derive a valid location. In an aspect, a UE may perform cascaded attempts of technologies to be tried and have corresponding gaps, The trigger from the eNB may include multiple technologies or an assumed sequence of technologies to be tried. In an aspect, the UE may try a second technology only if some specific QoS / KPIs from the first technology do not match.

[0188] Referring to FIGS. 11-12, in a specific example and as noted above, a UE may report its capability to derive a UE location based on other technologies beyond GNSS with autonomous procedures. In an aspect, a UE may report the validity duration of the ongoing location (either of GNSS, or other technologies, or the maximum across technologies). In an aspect, an eNB can configure the UE to do that and suggest which of one or more of those technologies for reacquisition of a valid location. In an aspect, the signaling may contain the preferred technology or multiple technologies, or it may contain an indication that: “reacquire GNSS, unless the conditions for acquiring a valid location through another technology are satisfied”. In an aspect, a UE may report whether it requires gap, and the length of the gap for any of the other technologies. In an aspect, a UE may report whether eventually it used another technology to derive a valid location.QC2500095WOQualcomm Ref. No. 2500095WO55 / 85In an aspect, a UE may perform cascaded attempts of technologies to be tried and have corresponding gaps. In an aspect, the autonomous gaps may correspond to multiple technologies or an assumed sequence of technologies to be tried. In an aspect, a UE may try a second technology only if some specific QoS / KPIs from the first technology do not match / are not reached.

[0189] FIG. 13 illustrates an example implementation 1300 of the processes 1100-1200 of FIGS.11-12, respectively, in accordance with aspects of the disclosure. In an aspect, 1305-1320 generally correspond to 805-820 of FIG, 8. However, 1315 of FIG. 13 generalizes the gap for a location fix to a “location gap” at 1315 instead of a “GNSS gap” as at 815 of FIG.8. Hence, one or more N-GNSS-based location estimates may be determined at 1315, without being limited to GNSS-based location estimates as in FIG. 8.

[0190] FIG. 14 illustrates an example implementation 1400 of the processes 1100-1200 of FIGS.11-12, respectively, in accordance with aspects of the disclosure. In FIG. 14, a first validity duration associated with a first position fix starts at 1405, and is reported by UE to NB. In an aspect, the first position fix may be a GNSS position fix or a N-GNSS position fix. At 1410, the NB configures a location gap. At 1415, the UE attempts to obtain a new position fix using a first technology (e.g., a GNSS or N-GNSS). At 1420, assuming that the UE cannot obtain tire new position fix at 1415 using the first technology, the UE attempts to obtain a new position fix using a second technology (e.g., N-GNSS). Note that additional attempts to derive a location estimate may be performed based on additional technologies as well, until a suitable location estimate is obtained (or the location gap is over). Once, the UE is able to determine the new position fix, a second validity duration for the new position fix starts at 1425, which is reported by UE to NB.

[0191] FIG. 15 illustrates an example implementation 1500 of the processes 1100-1200 of FIGS.11-12, respectively, in accordance with aspects of the disclosure. In an aspect, 1505-1515 generally correspond to 905-915 of FIG. 9. However, 1 15 of FIG. 15 generalizes the autonomous gap for a location fix to an “autonomous location gap” at 1510 instead of an “autonomous GNSS gap” as at 910 of FIG. 9. Hence, one or more N-GNSS-based location estimates may be determined at 1510, without being limited to GNSS-based location estimates as in FIG. 9.

[0192] 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 theQC2500095WOQualcomm Ref. No. 2500095WO56 / 85example 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 wi th 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 electrical insulator and an electrical 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,

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

[0194] Clause 1. A method performed by a user equipment (UE), comprising: determining to utilize a secondary non-Global Navigation Satellite System (N-G SS)-based positioning scheme to support a non-terrestrial entity’ (NTN)-based communication function instead of a primary GNSS-based positioning scheme based on a set of conditions; obtaining a N-GNSS-based location estimate of the UE based on the N-GNSS-based positioning scheme; and performing the NTN-based communication function based on the N-GNSS- based location estimate in accordance with the determination.

[0195] Clause 2. The method of clause 1, wherein the N-GNSS-based positioning scheme corresponds to a terrestrial network (TN)-based, UE-based positioning scheme or a NTN- based positioning scheme associated with a low earth orbit (LEO) constellation.

[0196] Clause 3. Tire method of any of clauses 1 to 2, wherein the set of conditions comprises:expiration or near-expiration of one or more location validity timers associated with a GNSS-based location estimate of tire UE, or a determination that a GNSS-based location estimate attempt has failed, or detection that the primary' GNSS-based positioning scheme is unavailable and that the secondary- N-GNSS-based positioning scheme is available, or detection that the N-GNSS-based location estimate is available, that the N-GNSS-basedQC2500095WOQualcomm Ref. No. 2500095WO57 / 85positioning scheme produces N-GNSS-based location estimates that match or correspond to GNSS-based location estimates for a period of time, or any combination thereof.

[0197] Clause 4. The method of any of clauses 1 to 3, further comprising: transmitting, to a wireless network component, capability information of the UE associated with a set of N- GNSS-based positioning schemes; and receiving, from the wireless network component, N-GNSS-based positioning scheme information associated with one or more of tire set of N-GNSS-based positioning schemes in response to the capability information, wherein the N-GNSS-based location estimate is obtained based on the N-GNSS-based positioning scheme information.

[0198] Clause 5. The method of clause 4, wherein the N-GNSS-based positioning scheme information comprises a preferred N-GNSS-based positioning scheme or a set of preferred N-GNSS-based positioning schemes, or wherein the N-GNSS-based positioning scheme information comprises a set of rules for N-GNSS-based positioning scheme selection, and the set of conditions is determined based on an evaluation of the set of rules, or wherein the N-GNSS-based positioning scheme information comprises a ranked list of positioning schemes for successive performance until an acceptable N- GNSS-based location measurement is obtained at a threshold level of quality, or any combination thereof.

[0199] Clause 6. The method of any of clauses 4 to 5, wherein the N-GNSS-based positioning scheme information is received via medium access control control element (MAC-CE).

[0200] Clause 7. The method of any of clauses 4 to 6, wherein the capability information comprises: a first capability of the UE to support the set of N-GNSS-based positioning schemes, or a second capability of the UE to support one or more N-GNSS-based positioning schemes from the set of N-GNSS-based positioning schemes with a measurement gap, or a third capability of the UE to support at least one N-GNSS-based positioning scheme from the set of secondary N-GNSS-based positioning schemes with one or more respective scheme-specific measurement gaps, or any combination thereof.

[0201] Clause 8. The method of any of clauses 1 to 7, further comprising: transmitting a measurement report comprising an indication of a N-GNSS-based positioning scheme used to obtain the N-GNSS-based location estimate.

[0202] Clause 9. The method of any of clauses 1 to 8, further comprising: attempting to obtain a location estimate of the UE in accordance with a positioning scheme sequence that isQC2500095WOQualcomm Ref. No. 2500095WO58 / 85based on a ranked list of N-GNSS-based positioning schemes, wherein the N-GNSS- based location estimate corresponds to an earliest successful location estimate attempt based on the ranked list of N-GNSS-based positioning schemes.

[0203] Clause 10. The method of clause 9, wherein the ranked list of ranked list of N-GNSS- based positioning schemes is UE-determined, network-configured or pre-defined.

[0204] Clause 11. The method of any of clauses 1 to 10, wherein the N-GNSS-based location estimate is associated with a set of location validity timers, and wherein the NTN-based communication function is performed based on the N-GNSS-based location estimate while the set of location validity timers is valid.

[0205] Clause 12. The method of clause 11, wherein the set of location validity timers comprises a single location validity timer associated with the GNSS-based positioning scheme and the N-GNSS-based positioning scheme, or wherein the set of location validity timers comprises a first location validity timer associated with the GNSS-based positioning scheme and a second location validity timer associated with the N-GNSS-based positioning scheme,

[0206] Clause 13. The method of any of clauses 1 to 12, wherein the N-GNSS-based location estimate is determined at the UE based on one or more measurement gaps.

[0207] Clause 14. The method of clause 13, wherein the one or more measurement gaps are N- GNSS-based positioning scheme-specific.

[0208] Clause 15. The method of any of clauses 13 to 14, wherein the one or more measurement gaps comprise one or more netw ork-configured measurement gaps, or wherein the one or more measurements gaps comprise one or more autonomous measurement gaps, or a combination thereof.

[0209] Clause 16. The method of any of clauses 1 to 15, wherein the NTN-based communication function comprises: derivation of a timing advance value associated with uplink synchronization between the UE and a NTN entity, or reporting of first propagation delay information associated with tire GNSS-based positioning scheme, or reporting of second propagation delay information associated with the N-GNSS-based positioning scheme, or one or more RRC-IDLE mode functions, or one or more mobility functions, or any combination thereof.

[0210] Clause 17. A method performed by a network component, comprising: receiving, from a user equipment (UE), non-Global Navigation Satellite System (N-GNSS)-basedQC2500095WOQualcomm Ref. No. 2500095WO59 / 85positioning scheme capability information of the UE; and transmitting, to the UE in response to the N-GNSS-based positioning scheme capability information, N-GNSS- based positioning scheme information associated with a set of secondary N-GNSS-based positioning schemes for a (NTN)-based communication function, wherein the NTN-based communication function is associated with a primary GNSS-based positioning scheme.

[0211] Clause 18. The method of clause 17, wherein the set of N-GNSS-based positioning schemes comprises one or more terrestrial network (TN)-based, UE-based positioning schemes, one or more NTN-based positioning schemes associated with one or more respective low earth orbit (LEO) constellations, or a combination thereof.

[0212] Clause 19. The method of any of clauses 17 to 18, wherein the N-GNSS-based positioning scheme information comprises a preferred N-GNSS-based positioning scheme or a set of preferred N-GNSS-based positioning schemes, or wherein the N-GNSS-based positioning scheme information comprises a set of rules for N-GNSS-based positioning scheme selection, or wherein the N-GNSS-based positioning scheme information comprises a ranked list of positioning schemes for successive performance until an acceptable N-GNSS-based location measurement is obtained at a threshold level of quality, or any combination thereof.

[0213] Clause 20. The method of clause 19, wherein the N-GNSS-based positioning scheme information is transmitted via medium access control control element (MAC-CE).

[0214] Clause 21. The method of any of clauses 17 to 20, wherein the N-GNSS-based positioning scheme capability information comprises: a first capability of the UE to support the set of secondary N-GNSS-based positioning schemes, or a second capability of the UE to support one or more secondary’ N-GNSS-based positioning schemes from the set of secondary' N-GNSS-based positioning schemes with a measurement gap, or a third capability of the UE to support at least one secondary' N-GNSS-based positioning scheme from the set of secondary N-GNSS-based positioning schemes with one or more respective scheme-specific measurement gaps, or any combination thereof.

[0215] Clause 22. The method of any of clauses 17 to 21, wherein the N-GNSS-based positioning scheme information is associated with evaluation of a set of conditions, the set of conditions comprising: expiration or near-expiration of one or more location validity timers associated with a GNSS-based location estimate of the UE, or a determination that a GNSS-based location estimate attempt has failed, or detection that the primary GNSS-QC2500095WOQualcomm Ref. No. 2500095WO60 / 85based positioning scheme is unavailable and that the secondary’ N-GNSS-based positioning scheme is available, or detection that the N-GNSS-based location estimate is available, that the N-GNSS-based positioning scheme produces N-GNSS-based location estimates that match or correspond to GNSS-based location estimates for a period of time, or any combination thereof.

[0216] Clause 23. The method of any of clauses 17 to 22, further comprising: receiving a measurement report comprising an indication of a N-GNSS-based positioning scheme used by the UE to obtain a N-GNSS-based location estimate associated with the NTN- based communication function.

[0217] Clause 24. The method of clause 23, wherein the N-GNSS-based location estimate corresponds to an earliest successful location estimate attempt by the UE based on a ranked list of N-GNSS-based positioning schemes.

[0218] Clause 25. The method of clause 24, wherein the ranked list of ranked list of N-GNSS- based positioning schemes is UE-determined, network-configured or pre-defined.

[0219] Clause 26. The method of any of clauses 23 to 25, wherein the N-GNSS-based location estimate is associated with a set of location validity timers, and wherein the NTN-based communication function is performed based on the N-GNSS-based location estimate while the set of location validity timers is valid.

[0220] Clause 27, The method of clause 26, wherein the set of location validity timers comprises a single location validity timer associated with the primary’ GNSS-based positioning scheme and the set of secondary N-GNSS-based positioning schemes, or wherein the set of location validity timers comprises a first location validity timer associated with the primary’ GNSS-based positioning scheme and at least one second location validity timer associated w ith the set of secondary' N-GNSS-based positioning schemes.

[0221] Clause 28. The method of any of clauses 23 to 27, wherein the N-GNSS-based location estimate is determined at the UE based on one or more measurement gaps.

[0222] Clause 29. The method of clause 28, wherein the one or more measurement gaps are N- GNSS-based positioning scheme-specific.

[0223] Clause 30. The method of any of clauses 28 to 29, wherein the one or more measurement gaps comprise one or more network-configured measurement gaps, or wherein the one or more measurements gaps comprise one or more autonomous measurement gaps, or a combination thereof.QC2500095WOQualcomm Ref. No. 2500095WO61 / 85

[0224] Clause 31, The method of any of clauses 17 to 30, wherein the NTN-based communication function comprises: derivation of a timing advance value associated with uplink synchronization between the UE and a NTN entity, or reporting of first propagation delay information associated with the primary GNSS-based positioning scheme, or reporting of second propagation delay information associated with a secondary N-GNSS-based positioning scheme from tire set of secondary' N-GNSS-based positioning schemes, or one or more RRC-IDLE mode functions, or one or more mobility functions, or any combination thereof.

[0225] Clause 32. A user equipment (UE), comprising: one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors, either alone or in combination, being configured to: determine to utilize a secondary' non-Global Navigation Satellite System (N-GNSS)-based positioning scheme to support a nonterrestrial entity (NTN)-based communication function instead of a primary GNSS-based positioning scheme based on a set of conditions; obtain a N-GNSS-based location estimate of the UE based on tire N-GNSS-based positioning scheme; and perform the NTN-based communication function based on the N-GNSS-based location estimate in accordance with the determination.

[0226] Clause 33. The UE of clause 32, wherein the N-GNSS-based positioning scheme corresponds to a terrestrial ne twork (TN)-based, UE-based positioning scheme or a NTN- based positioning scheme associated with a low earth orbit (LEO) constellation.

[0227] Clause 34. The UE of any of clauses 32 to 33, wherein the set of conditions comprises:expiration or near-expiration of one or more location validity' timers associated with a GNSS-based location estimate of the UE, or a determination that a GNSS-based location estimate attempt has failed, or that the primary GNSS-based positioning scheme is unavailable and that the secondary' N-GNSS-based positioning scheme is available, or that the N-GNSS-based location estimate is available, that the N-GNSS-based positioning scheme produces N-GNSS-based location estimates that match or correspond to GNSS- based location estimates for a period of time, or any combination thereof.

[0228] Clause 35. Tire UE of any of clauses 32 to 34, wherein the one or more processors, either alone or in combination, are further configured to: transmit, via the one or more transceivers, to a wireless network component, capability information of the UEQC2500095WOQualcomm Ref. No. 2500095WO62 / 85associated with a set ofN-GNSS-based positioning schemes; and receive, via the one or more transceivers, from the wireless network component, N-GNSS-based positioning scheme information associated with one or more of the set ofN-GNSS-based positioning schemes in response to the capability information, wherein the N-GNSS-based location estimate is obtained based on the N-GNSS-based positioning scheme information.

[0229] Clause 36. The UE of clause 35, wherein the N-GNSS-based positioning scheme information comprises a preferred N-GNSS-based positioning scheme or a set of preferred N-GNSS-based positioning schemes, or wherein the N-GNSS-based positioning scheme information comprises a set of rules for N-GNSS-based positioning scheme selection, and the set of conditions is determined based on an evaluation of the set of rales, or wherein the N-GNSS-based positioning scheme information comprises a ranked list of positioning schemes for successive performance until an acceptable N- GNSS-based location measurement is obtained at a threshold level of quality, or any combination thereof.

[0230] Clause 37, Tire UE of any of clauses 35 to 36, wherein the N-GNSS-based positioning scheme information is received via medium access control control element (MAC-CE).

[0231] Clause 38. The UE of any of clauses 35 to 37, wherein the capability information comprises: a first capability of tire UE to support the set of N-GNSS-based positioning schemes, or a second capability of the UE to support one or more N-GNSS-based positioning schemes from the set of N-GNSS-based positioning schemes with a measurement gap, or a third capability of the UE to support at least one N-GNSS-based positioning scheme from the set of secondary N-GNSS-based positioning schemes with one or more respective scheme-specific measurement gaps, or any combination thereof.

[0232] Clause 39. The UE of any of clauses 32 to 38, wherein tire one or more processors, either alone or in combination, are further configured to: transmit, via the one or more transceivers, a measurement report comprising an indication of a N-GNSS-based positioning scheme used to obtain the N-GNSS-based location estimate.

[0233] Clause 40. The UE of any of clauses 32 to 39, wherein the one or more processors, either alone or in combination, are further configured to: attempt to obtain a location estimate of the UE in accordance with a positioning scheme sequence that is based on a ranked list of N-GNSS-based positioning schemes, wherein the N-GNSS-based location estimateQC2500095WOQualcomm Ref. No. 2500095WO63 / 85corresponds to an earliest successful location estimate attempt based on the ranked list of N-GNSS-based positioning schemes.

[0234] Clause 41. The UE of clause 40, wherein the ranked list of ranked list of N-GNSS-based positioning schemes is UE-detennined, network-configured or pre-defined.

[0235] Clause 42, The UE of any of clauses 32 to 41, wherein the N-GNSS-based location estimate is associated with a set of location validity timers, and -wherein the NTN-based communication function is performed based on the N-GNSS-based location estimate while the set of location validity timers is valid.

[0236] Clause 43. The UE of clause 42, wherein the set of location validity timers comprises a single location validity timer associated w ith the GNSS-based positioning scheme and the N-GNSS-based positioning scheme, or wherein the set of location validity timers comprises a first location validity timer associated with the GNSS-based positioning scheme and a second location validity timer associated with the N-GNSS-based positioning scheme.

[0237] Clause 44. The UE of any of clauses 32 to 43, wherein the N-GNSS-based location estimate is determined at the UE based on one or more measurement gaps.

[0238] Clause 45. The UE of clause 44, wherein the one or more measurement gaps are N -GNSS- based positioning scheme-specific.

[0239] Clause 46. The UE of any of clauses 44 to 45, wherein the one or more measurement gaps comprise one or more network-configured measurement gaps, or wherein the one or more measurements gaps comprise one or more autonomous measurement gaps, or a combination thereof.

[0240] Clause 47. The UE of any of clauses 32 to 46, wherein the NTN-based communication function comprises: of a timing advance value associated with uplink synchronization between the UE and a NTN entity, or report of first propagation delay information associated with the GNSS-based positioning scheme, or reporting of second propagation delay information associated w ith the N-GNSS-based positioning scheme, or one or more RRC-IDLE mode functions, or one or more mobility functions, or any combination thereof.

[0241] Clause 48. A network component, comprising: one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transcei vers, the one or more processors, either alone or inQC2500095WOQualcomm Ref. No. 2500095WO64 / 85combination, being configured to: receive, via the one or more transceivers, from a user equipment (UE), non-Global Navigation Satellite System (N-GNSS) -based positioning scheme capability information of the UE; and transmit, via the one or more transceivers, to the UE in response to the N-GNSS-based positioning scheme capability information, N-GNSS-based positioning scheme information associated with a set of secondary N- GNSS-based positioning schemes for a (NTN)-based communication function, wherein the NTN-based communication function is associated with a primary GNSS-based positioning scheme,

[0242] Clause 49. Tire network component of clause 48, wherein the set of N-GNSS-based positioning schemes comprises one or more terrestrial network (TN)-based, UE-based positioning schemes, one or more N TN-based positioning schemes associated with one or more respective low earth orbit (LEO) constellations, or a combination thereof.

[0243] Clause 50. The network component of any of clauses 48 to 49, wherein the N-GNSS- based positioning scheme information comprises a preferred N-GNSS-based positioning scheme or a set of preferred N-GNSS-based positioning schemes, or wherein the N- GNSS-based positioning scheme information comprises a set of rules for N-GNSS-based positioning scheme selection, or wherein the N-GNSS-based positioning scheme information comprises a ranked list of positioning schemes for successive performance until an acceptable N-GNSS-based location measurement is obtained at a threshold level of quality, or any combination thereof.

[0244] Clause 51. The network component of clause 50, wherein the N-GNSS-based positioning scheme information is transmitted via medium access control control element (MAC-CE).

[0245] Clause 52. The network component of any of clauses 48 to 51, wherein the N-GNSS- based positioning scheme capability information comprises: a first capability of the UE to support the set of secondary N-GNSS-based positioning schemes, or a second capability of the UE to support one or more secondary’ N-GNSS-based positioning schemes from the set of secondary' N-GNSS-based positioning schemes with a measurement gap, or a third capability of the UE to support at least one secondary N- GNSS-based positioning scheme from the set of secondary’ N-GNSS-based positioning schemes with one or more respective scheme-specific measurement gaps, or any' combination thereof.QC2500095WOQualcomm Ref. No. 2500095WO65 / 85

[0246] Clause 53. The network component of any of clauses 48 to 52, wherein the N-GNSS- based positioning scheme information is associated with evaluation of a set of conditions, the set of conditions comprising: expiration or near-expiration of one or more location validity timers associated with a GNSS-based location estimate of the UE, or a determination that a GNSS-based location estimate attempt has failed, or that the primary’ GNSS-based positioning scheme is unavailable and that the secondary N-GNSS-based positioning scheme is available, or that the N-GNSS-based location estimate is available, that the N-GNSS-based positioning scheme produces N-GNSS-based location estimates that match or correspond to GNSS-based location estimates for a period of time, or any combination thereof.

[0247] Clause 54. The network component of any of clauses 48 to 53, wherein the one or more processors, either alone or in combination, are further configured to: receive, via the one or more transceivers, a measurement report comprising an indication of a N-GNSS-based positioning scheme used by the UE to obtain a N-GNSS-based location estimate associated with the NTN-based communication function,

[0248] Clause 55. Tire network component of clause 54, wherein the N-GNSS-based location estimate corresponds to an earliest successful location estimate attempt by the UE based on a ranked list of N-GNSS-based positioning schemes.

[0249] Clause 56, The network component of clause 55, wherein the ranked list of ranked list of N-GNSS-based positioning schemes is UE-determined, network -configured or predefined.

[0250] Clause 57. The network component of any of clauses 54 to 56, wherein the N-GNSS- based location estimate is associated with a set of location validity timers, and wherein the NTN-based communication function is performed based on the N-GNSS-based location estimate while the set of location validity timers is valid.

[0251] Clause 58. Tire network component of clause 57, wherein the set of location validity timers comprises a single location validity timer associated with the primary GNSS-based positioning scheme and the set of secondary N-GNSS-based positioning schemes, or wherein the set of location validity timers comprises a first location validity timer associated with the primary GNSS-based positioning scheme and at least one second location validity timer associated with the set of secondary N-GNSS-based positioning schemes.QC2500095WOQualcomm Ref. No. 2500095WO66 / 85

[0252] Clause 59. The network component of any of clauses 54 to 58, wherein the N-GNSS- based location estimate is determined at the UE based on one or more measurement gaps.

[0253] Clause 60. The network component of clause 59, wherein the one or more measurement gaps are N-GNSS-based positioning scheme-specific.

[0254] Clause 61, Tire network component of any of clauses 59 to 60, wherein the one or more measurement gaps comprise one or more network-configured measurement gaps, or wherein the one or more measurements gaps comprise one or more autonomous measurement gaps, or a combination thereof.

[0255] Clause 62. The network component of any of clauses 48 to 61, wherein the NTN-based communication function comprises: of a timing advance value associated with uplink synchronization between the UE and a NTN entity, or report of first propagation delay information associated with the primary’ GNSS-based positioning scheme, or reporting of second propagation delay information associated with a secondary N-GNSS-based positioning scheme from the set of secondary N-GNSS-based positioning schemes, or one or more RRC-IDLE mode functions, or one or more mobility functions, or any combination thereof.

[0256] Clause 63. A user equipment (UE), comprising: means for determining to utilize a secondary non-Global Navigation Satellite System (N-GNSS)-based positioning scheme to support a non-terrestnal entity' (NTN)-based communication function instead of a primary- GNSS-based positioning scheme based on a set of conditions; means for obtaining a N-GNSS-based location estimate of the UE based on the N-GNSS-based positioning scheme; and means for performing the NTN -based communication function based on the N-GNSS-based location estimate in accordance with the determination,

[0257] Clause 64. The UE of clause 63, wherein the N-GNSS-based positioning scheme corresponds to a terrestrial network (TN)-based, UE-based positioning scheme or a NTN- based positioning scheme associated with a low earth orbit (LEO) constellation.

[0258] Clause 65. Tire UE of any of clauses 63 to 64, wherein the set of conditions comprises:expiration or near-expiration of one or more location validity timers associated with a GNSS-based location estimate of tire UE, or a determination that a GNSS-based location estimate attempt has failed, or means for that the primary' GNSS-based positioning scheme is unavailable and that the secondary' N-GNSS-based positioning scheme is available, or means for that the N-GNSS-based location estimate is available, that the N-QC2500095WOQualcomm Ref. No. 2500095WO67 / 85GNSS-based positioning scheme produces N-GNSS-based location estimates that match or correspond to GNSS-based location estimates for a period of time, or any combination thereof.

[0259] Clause 66. The UE of any of clauses 63 to 65, further comprising: means for transmitting, to a wireless network component, capability information of the UE associated with a set of N-GNSS-based positioning schemes; and means for receiving, from the wireless network component, N-GNSS-based positioning scheme information associated with one or more of the set of N-GNSS-based positioning schemes in response to the capability information, wherein the N-GNSS-based location estimate is obtained based on the N- GNSS-based positioning scheme information.

[0260] Clause 67. lire UE of clause 66, wherein the N-GNSS-based positioning scheme information comprises a preferred N-GNSS-based positioning scheme or a set of preferred N-GNSS-based positioning schemes, or wherein the N-GNSS-based positioning scheme information comprises a set of rules for N-GNSS-based positioning scheme selection, and the set of conditions is determined based on an evaluation of the set of rules, or wherein the N-GNSS-based positioning scheme information comprises a ranked list of positioning schemes for successive performance until an acceptable N- GNSS-based location measurement is obtained at a threshold level of quality, or any combination thereof.

[0261] Clause 68. The UE of any of clauses 66 to 67, wherein the N-GNSS-based positioning scheme information is received via medium access control control element (MAC-CE).

[0262] Clause 69. The UE of any of clauses 66 to 68, wherein the capability information comprises: a first capability’ of the UE to support the set of N-GNSS-based positioning schemes, or a second capability of the UE to support one or more N-GNSS-based positioning schemes from the set of N-GNSS-based positioning schemes with a measurement gap, or a third capability of the UE to support at least one N-GNSS-based positioning scheme from the set of secondary N-GNSS-based positioning schemes with one or more respective scheme -specific measurement gaps, or any combination thereof.

[0263] Clause 70. lire UE of any of clauses 63 to 69, further comprising: means for transmitting a measurement report comprising an indication of a N-GNSS-based positioning scheme used to obtain the N-GNSS-based location estimate.QC2500095WOQualcomm Ref. No. 2500095WO68 / 85

[0264] Clause 71. The UE of any of clauses 63 to 70, further comprising: means for attempting to obtain a location estimate of the UE in accordance with a positioning scheme sequence that is based on a ranked list of N-GNSS-based positioning schemes, wherein the N- GNSS-based location estimate corresponds to an earliest successful location estimate attempt based on the ranked list of N-GNSS-based positioning schemes.

[0265] Clause 72. The UE of clause 71, wherein the ranked list of ranked list of N-GNSS -based positioning schemes is UE-determined, network-configured or pre-defined.

[0266] Clause 73. Tire UE of any of clauses 63 to 72, wherein the N-GNSS-based location estimate is associated with a set of location validity timers, and wherein the NTN-based communication function is performed based on the N-GNSS-based location estimate while the set of location validity timers is valid.

[0267] Clause 74. Tire UE of clause 73, wherein the set of location validity timers comprises a single location validity timer associated with the GNSS-based positioning scheme and the N-GNSS-based positioning scheme, or wherein the set of location validity timers comprises a first location validity timer associated with the GNSS-based positioning scheme and a second location validity timer associated with the N-GNSS-based positioning scheme.

[0268] Clause 75. The UE of any of clauses 63 to 74, wherein the N-GNSS-based location estimate is determined at the UE based on one or more measurement gaps.

[0269] Clause 76. The UE of clause 75, wherein the one or more measurement gaps are N-GNSS- based positioning scheme-specific.

[0270] Clause 77. The UE of any of clauses 75 to 76, wherein the one or more measurement gaps comprise one or more network -configured measurement gaps, or wherein the one or more measurements gaps comprise one or more autonomous measurement gaps, or a combination thereof.

[0271] Clause 78. The UE of any of clauses 63 to 77, wherein the NTN-based communication function comprises: means for of a timing advance value associated with uplink synchronization between the UE and a NTN entity, or means for reporting of first propagation delay information associated with the GNSS-based positioning scheme, or reporting of second propagation delay information associated with the N-GNSS-based positioning scheme, or one or more RRC-IDLE mode functions, or one or more mobility functions, or any combination thereof.QC2500095WOQualcomm Ref. No. 2500095WO69 / 85

[0272] Clause 79. A network component, comprising: means for receiving, from a user equipment (UE), non-Global Navigation Satellite System (N-GNSS) -based positioning scheme capability information of the UE; and means for transmitting, to the UE in response to the N-GNSS-based positioning scheme capability information, N-GNSS- based positioning scheme information associated with a set of secondary’ N-GNSS-based positioning schemes for a (NTN)-based communication function, wherein the NTN-based communication function is associated with a primary GNSS-based positioning scheme.

[0273] Clause 80. Tire network component of clause 79, wherein the set of N-GNSS-based positioning schemes comprises one or more terrestrial network (TN)-based, UE-based positioning schemes, one or more NTN-based positioning schemes associated with one or more respective low earth orbit (LEO) constellations, or a combination thereof.

[0274] Clause 81. The network component of any of clauses 79 to 80, wherein the N-GNSS- based positioning scheme information comprises a preferred N-GNSS-based positioning scheme or a set of preferred N-GNSS-based positioning schemes, or wherein the N- GNSS-based positioning scheme information comprises a set of rules for N-GNSS-based positioning scheme selection, or wherein the N-GNSS-based positioning scheme information comprises a ranked list of positioning schemes for successive performance until an acceptable N-GNSS-based location measurement is obtained at a threshold level of quality, or any combination thereof.

[0275] Clause 82. The network component of clause 81, wherein the N-GNSS-based positioning scheme information is transmitted via medium access control control element (MAC-CE).

[0276] Clause 83. The network component of any of clauses 79 to 82, wherein the N-GNSS- based positioning scheme capability information comprises: a first capability’ of the UE to support the set of secondary N-GNSS-based positioning schemes, or a second capability of the UE to support one or more secondary N-GNSS-based positioning schemes from the set of secondary’ N-GNSS-based positioning schemes with a measurement gap, or a third capability of the UE to support at least one secondary N- GNSS-based positioning scheme from the set of secondary N-GNSS-based positioning schemes with one or more respective scheme-specific measurement gaps, or any combination thereof.

[0277] Clause 84. Tire network component of any of clauses 79 to 83, wherein the N-GNSS- based positioning scheme information is associated with evaluation of a set of conditions,QC2500095WOQualcomm Ref. No. 2500095WO70 / 85the set of conditions comprising: expiration or near-expiration of one or more location validity timers associated with a GNSS-based location estimate of the UE, or a determination that a GNSS-based location estimate attempt has failed, or means for that the primary GNSS-based positioning scheme is unavailable and that the secondary N- GNSS-based positioning scheme is available, or means for that the N-GNSS-based location estimate is available, that the N-GNSS-based positioning scheme produces N- GNSS-based location estimates that match or correspond to GNSS-based location estimates for a period of time, or any combination thereof,

[0278] Clause 85. The network component of any of clauses 79 to 84, further comprising: means for receiving a measurement report comprising an indication of a N-GNSS-based positioning scheme used by the UE to obtain a N-GNSS-based location estimate associated with the NTN-based communication function.

[0279] Clause 86. The network component of clause 85, wherein the N-GNSS-based location estimate corresponds to an earliest successful location estimate attempt by the UE based on a ranked list of N-GNSS-based positioning schemes.

[0280] Clause 87. Tire network component of clause 86, wherein the ranked list of ranked list of N-GNSS-based positioning schemes is UE-determined, network-configured or pre¬ defined.

[0281] Clause 88. The network component of any of clauses 85 to 87, wherein the N-GNSS- based location estimate is associated with a set of location validity timers, and wherein the NTN-based communication function is performed based on the N-GNSS-based location estimate while the set of location validity timers is valid.

[0282] Clause 89. The network component of clause 88, wherein the set of location validity timers comprises a single location validity timer associated with the primary GNSS-based positioning scheme and the set of secondary N-GNSS-based positioning schemes, or wherein the set of location validity timers comprises a first location validity timer associated with the primary GNSS-based positioning scheme and at least one second location validity timer associated with the set of secondary N-GNSS-based positioning schemes.

[0283] Clause 90. The network component of any of clauses 85 to 89, wherein the N-GNSS- based location estimate is determined at the UE based on one or more measurement gaps.QC2500095WOQualcomm Ref. No. 2500095WO71 / 85

[0284] Clause 91. The network component of clause 90, wherein the one or more measurement gaps are N-GNSS-based positioning scheme-specific.

[0285] Clause 92. The network component of any of clauses 90 to 91, wherein the one or more measurement gaps comprise one or more network-configured measurement gaps, or wherein the one or more measurements gaps comprise one or more autonomous measurement gaps, or a combination thereof.

[0286] Clause 93. The netw ork component of any of clauses 79 to 92, wherein the NTN -based communication function composes: means for of a timing advance value associated with uplink synchronization between the UE and a NTN entity, or means for reporting of first propagation delay information associated with the primary GNSS-based positioning scheme, or reporting of second propagation delay information associated with a secondary N-GNSS-based positioning scheme from the set of secondary’ N-GNSS-based positioning schemes, or one or more RRC-IDLE mode functions, or one or more mobility functions, or any combination thereof.

[0287] Clause 94. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: determine to utilize a secondary non-Global Navigation Satellite System (N-GNSS)-based positioning scheme to support a non-terrestrial entity (NTN)-based communication function instead of a primary GNSS-based positioning scheme based on a set of conditions; obtain a N-GNSS-based location estimate of the UE based on the N-GNSS- based positioning scheme; and perform the NTN-based communication function based on the N-GNSS-based location estimate in accordance with the determination.

[0288] Clause 95. The non-transitory’ computer-readable medium of clause 94, w'herein the N- GNSS-based positioning scheme corresponds to a terrestrial network (TN)-based, UE- based positioning scheme or a NTN-based positioning scheme associated with a low earth orbit (LEO) constellation.

[0289] Clause 96. Tire non-transitory' computer-readable medium of any of clauses 94 to 95, wherein the set of conditions comprises: expiration or near-expiration of one or more location validity' timers associated with a GNSS-based location estimate of the UE, or a determination that a GNSS-based location estimate attempt has failed, or that the primary GNSS-based positioning scheme is unavailable and that the secondary N-GNSS-based positioning scheme is available, or that the N-GNSS-based location estimate is available,QC2500095WOQualcomm Ref. No. 2500095WO72 / 85that the N-GNSS-based positioning scheme produces N-GNSS-based location estimates that match or correspond to GNSS-based location estimates for a period of time, or any combination thereof.

[0290] Clause 97. The non-transitory computer-readable medium of any of clauses 94 to 96, further comprising computer-executable instructions that, when executed by the UE, cause the UE to: transmit, to a wireless network component, capability information of the UE associated with a set of N-GNSS-based positioning schemes; and receive, from the wireless network component, N-GNSS-based positioning scheme information associated with one or more of the set of N-GNSS-based positioning schemes in response to the capability information, wherein the N-GNSS-based location estimate is obtained based on the N-GNSS-based positioning scheme information.

[0291] Clause 98. The non-transitory computer-readable medium of clause 97, wherein the N- GNSS-based positioning scheme information comprises a preferred N-GNSS-based positioning scheme or a set of preferred N-GNSS-based positioning schemes, or wherein the N-GNSS-based positioning scheme information comprises a set of rules for N-GNSS- based positioning scheme selection, and the set of conditions is determined based on an evaluation of the set of rules, or wherein tire N-GNSS-based positioning scheme information comprises a ranked list of positioning schemes for successive performance until an acceptable N-GNSS-based location measurement is obtained at a threshold level of quality, or any combination thereof.

[0292] Clause 99. The non-transitory computer-readable medium of any of clauses 97 to 98, wherein the N-GNSS-based positioning scheme information is received via medium access control control element (MAC-CE).

[0293] Clause 100. The non-transitory computer-readable medium of any of clauses 97 to 99, wherein the capability information comprises: a first capability of the UE to support the set of N-GNSS-based positioning schemes, or a second capability of the UE to support one or more N-GNSS-based positioning schemes from the set of N-GNSS-based positioning schemes with a measurement gap, or a third capability of the UE to support at least one N-GNSS-based positioning scheme from the set of secondary N-GNSS-based positioning schemes with one or more respective scheme -specific measurement gaps, or any combination thereof.QC2500095WOQualcomm Ref. No. 2500095WO73 / 85

[0294] Clause 101. The non-transitory computer-readable medium of any of clauses 94 to 100, further comprising computer-executable instructions that, when executed by the UE, cause the UE to: transmit a measurement report comprising an indication of a N-GNSS- based positioning scheme used to obtain tire N-GNSS-based location estimate.

[0295] Clause 102. The non-transitor ’ computer-readable medium of any of clauses 94 to 101, further comprising computer-executable instructions that, when executed by the UE, cause the UE to: attempt to obtain a location estimate of the UE in accordance with a positioning scheme sequence that is based on a ranked list of N-GNSS-based positioning schemes, wherein the N-GNSS-based location estimate corresponds to an earliest successful location estimate attempt based on the ranked list of N-GNSS-based positioning schemes.

[0296] Clause 103. The non-transitor ’ computer-readable medium of clause 102, wherein the ranked list of ranked list of N-GNSS-based positioning schemes is UE-determined, network-configured or pre-defined.

[0297] Clause 104. The non-transitory computer-readable medium of any of clauses 94 to 103, wherein the N-GNSS-based location estimate is associated with a set of location validity timers, and wherein the NTN-based communication function is performed based on the N-GNSS-based location estimate while the set of location validity timers is valid.

[0298] Clause 10. Hie non-transitory’ computer-readable medium of clause 104, wherein the set of location validity timers comprises a single location validity timer associated with the GNSS-based positioning scheme and the N-GNSS-based positioning scheme, or wherein the set of location validity' timers comprises a first location validity tinier associated with the GNSS-based positioning scheme and a second location validity' timer associated with the N-GNSS-based positioning scheme.

[0299] Clause 106. The non-transitory computer-readable medium of any of clauses 94 to 105, wherein the N-GNSS-based location estimate is determined at the UE based on one or more measurement gaps.

[0300] Clause 107. The non-transitory computer-readable medium of clause 106, wherein the one or more measurement gaps are N-GNSS-based positioning scheme-specific.

[0301] Clause 108. The non-transitory’ computer-readable medium of any of clauses 106 to 107, wherein the one or more measurement gaps comprise one or more network-configuredQC2500095WOQualcomm Ref. No. 2500095WO74 / 85measurement gaps, or wherein the one or more measurements gaps comprise one or more autonomous measurement gaps, or a combination thereof.

[0302] Clause 109. The non-transitory computer-readable medium of any of clauses 94 to 108, wherein the NTN-based communication function comprises: of a timing advance value associated with uplink synchronization between the UE and a NTN entity, or report of first propagation delay information associated with the GNSS-based positioning scheme, or reporting of second propagation delay information associated with the N-GNSS-based positioning scheme, or one or more RRC-IDLE mode functions, or one or more mobility functions, or any combination thereof.

[0303] Clause 110. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a network component, cause the network component to: receive, from a user equipment (UE), non-Global Navigation Satellite System (N- GNSS)-based positioning scheme capability information of the UE; and transmit, to the UE in response to the N-GNSS-based positioning scheme capability information, N- GNSS-based positioning scheme information associated with a set of secondary' N- GNSS-based positioning schemes for a (NTN)-based communication function, wherein the NTN-based communication function is associated with a primary GNSS-based positioning scheme.

[0304] Clause 111. Tire non-transitory’ computer-readable medium of clause 110, wherein the set of N-GNSS-based positioning schemes comprises one or more terrestrial network (TN)- based, UE-based positioning schemes, one or more NTN-based positioning schemes associated with one or more respective low earth orbit (LEO) constellations, or a combination thereof.

[0305] Clause 112. The non-transitory computer-readable medium of any of clauses 110 to 111, wherein the N-GNSS-based positioning scheme information comprises a preferred N- GNSS-based positioning scheme or a set of preferred N-GNSS-based positioning schemes, or wherein the N-GNSS-based positioning scheme information comprises a set of rules for N-GNSS-based positioning scheme selection, or wherein the N-GNSS-based positioning scheme information comprises a ranked list of positioning schemes for successive performance until an acceptable N-GNSS-based location measurement is obtained at a threshold level of quality, or any combination thereof.QC2500095WOQualcomm Ref. No. 2500095WO75 / 85

[0306] Clause 113, The non-transitory computer-readable medium of clause 112, wherein the N- GNSS-based positioning scheme information is transmitted via medium access control control element (MAC-CE).

[0307] Clause 114. The non-transitory computer-readable medium of any of clauses 110 to 113, wherein the N-GNSS-based positioning scheme capability information comprises: a first capability of the UE to support the set of secondary N-GNSS-based positioning schemes, or a second capability of the UE to support one or more secondary N-GNSS-based positioning schemes from the set of secondary N-GNSS-based positioning schemes with a measurement gap, or a third capability of the UE to support at least one secondary N- GNSS-based positioning scheme from the set of secondary N-GNSS-based positioning schemes with one or more respective scheme-specific measurement gaps, or any combination thereof.

[0308] Clause 115. The non-transitory computer-readable medium of any of clauses 110 to 114, wherein the N-GNSS-based positioning scheme information is associated with evaluation of a set of conditions, the set of conditions comprising: expiration or near-expiration of one or more location validity timers associated with a GNSS-based location estimate of the UE, or a determination that a GNSS-based location estimate attempt has failed, or that the primary GNSS-based positioning scheme is unavailable and that the secondary N- GNSS-based positioning scheme is available, orthatthe N-GNSS-based location estimate is available, that the N-GNSS-based positioning scheme produces N-GNSS-based location estimates that match or correspond to GNSS-based location estimates for a period of time, or any combination thereof.

[0309] Clause 116. Tire non-transitory computer-readable medium of any of clauses 110 to 115, further comprising computer-executable instructions that, when executed by tire network component, cause the network component to: receive a measurement report comprising an indication of a N-GNSS-based positioning scheme used by the UE to obtain a N- GNSS-based location estimate associated with the NTN-based communication function.

[0310] Clause 117. The non-transitory computer-readable medium of clause 116, wherein the N- GNSS-based location estimate corresponds to an earliest successful location estimate attempt by the UE based on a ranked list of N-GNSS-based positioning schemes.QC2500095WOQualcomm Ref. No. 2500095WO76 / 85

[0311] Clause 118, The non-transitory computer-readable medium of clause 117, wherein the ranked list of ranked list of N-GNSS-based positioning schemes is UE-determined, network-configured or pre-defined.

[0312] Clause 119. The non-transitory computer-readable medium of any of clauses 116 to 118, wherein the N-GNSS-based location estimate is associated with a set of location validity timers, and wherein the NTN-based communication function is performed based on the N-GNSS-based location estimate while the set of location validity timers is valid.

[0313] Clause 120, The non-transitory computer-readable medium of clause 119, wherein the set of location validity timers comprises a single location validity timer associated with the primary GNSS-based positioning scheme and the set of secondary N-GNSS-based positioning schemes, or wherein tire set of location validity timers comprises a first location validity timer associated with the primary’ GNSS-based positioning scheme and at least one second location validity timer associated with the set of secondary N-GNSS- based positioning schemes.

[0314] Clause 121. Tire non-transitory computer-readable medium of any of clauses 116 to 120, wherein the N-GNSS-based location estimate is determined at the UE based on one or more measurement gaps.

[0315] Clause 122. The non-transitory computer-readable medium of clause 121, wherein tire one or more measurement gaps are N-GNSS-based positioning scheme-specific.

[0316] Clause 123. The non-transitory- computer-readable medium of any of clauses 121 to 122, wherein the one or more measurement gaps comprise one or more network-configured measurement gaps, or wherein the one or more measurements gaps comprise one or more autonomous measurement gaps, or a combination thereof.

[0317] Clause 124. The non-transitory' computer-readable medium of any of clauses 110 to 123, wherein the NTN-based communication function comprises: of a timing advance value associated with uplink synchronization between the UE and a NTN entity, or report of first propagation delay information associated with the primary' GNSS-based positioning scheme, or reporting of second propagation delay information associated with a secondary N-GNSS-based positioning scheme from the set of secondary’ N-GNSS-based positioning schemes, or one or more RRC-IDLE mode functions, or one or more mobility' functions, or any combination thereof.QC2500095WOQualcomm Ref. No. 2500095WO77 / 85

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

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

[0320] Hie 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.

[0321] 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), erasableQC2500095WOQualcomm Ref. No. 2500095WO78 / 85programmable 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. Tire 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.

[0322] 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 earn,' 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.

[0323] 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. For example, theQC2500095WOQualcomm Ref. No. 2500095WO79 / 85functions, 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. Further, no component, function, action, or instruction described or claimed herein should be construed as critical or essential unless explicitly described as such. Furthermore, as used herein, the terms “set,” “group,” and the like are intended to include one or more of the stated elements. Also, as used herein, the terms “has,” “have,” “having,” “comprises,” “comprising,” “includes,” “including,” and the like does not preclude the presence of one or more additional elements (e.g., an element “having” A may also have B), Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Also, as used herein, the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and / or,” unless explicitly stated otherwise (e.g., if used in combination with “either” or “only one of’) or the alternatives are mutually exclusive (e.g., “one or more” should not be interpreted as “one and more”). Furthermore, although components, functions, actions, and instructions may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated. Accordingly, as used herein, the articles “a,” “an,” “the,” and “said” are intended to include one or more of the stated elements. Additionally, as used herein, the terms “at least one” and “one or more” encompass “one” component, function, action, or instruction performing or capable of performing a described or claimed functionality and also “two or more” components, functions, actions, or instructions performing or capable of performing a described or claimed functionality in combination.QC2500095WO

Claims

Qualcomm Ref. No. 2500095WO80 / 85CLAIMSWhat is claimed is:

1. A user equipment (UE), comprising:one or more memories;one or more transceivers; andone or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors, either alone or in combination, being configured to:determine to utilize a secondary non-Global Navigation Satellite System (N-GNSS)-based positioning scheme to support a non-terrestrial entity (NTN)-based communication function instead of a primary GNSS-based positioning scheme based on a set of conditions;obtain a N-GNSS-based location estimate of the UE based on the N-GNSS-based positioning scheme; andperform the NTN-based communication function based on the N-GNSS-based location estimate in accordance with the determination.

2. The UE of claim 1, wherein the N-GNSS-based positioning scheme corresponds to a terrestrial network (TN)-based, UE-based positioning scheme or a NTN-based positioning scheme associated with a low earth orbit (LEO) constellation.

3. The UE of claim 1, wherein the set of conditions comprises: expiration or near-expiration of one or more location validity timers associated with a GNSS-based location estimate of the UE, ora determination that a GNSS-based location estimate attempt has failed, or that the primary GNSS-based positioning scheme is unavailable and that the secondary N-GNSS-based positioning scheme is available, orthat tire N-GNSS-based location estimate is available, that the N-GNSS-based positioning scheme produces N-GNSS-based location estimates that match or correspond to GNSS-based location estimates for a period of time, orany combination thereof.QC2500095WOQualcomm Ref. No. 2500095WO81 / 854. The UE of claim 1, wherein the one or more processors, either alone or in combination, are farther configured to:transmit, via the one or more transceivers, to a wireless network component, capability information of the UE associated with a set of N-GNSS-based positioning schemes; andreceive, via the one or more transceivers, from the wireless network component, N-GNSS-based positioning scheme information associated with one or more of the set of N-GNSS-based positioning schemes in response to the capability information, wherein the N-GNSS-based location estimate is obtained based on the N-GNSS- based positioning scheme information.

5. The UE of claim 4,wherein the N-GNSS-based positioning scheme information comprises a preferred N-GNSS-based positioning scheme or a set of preferred N-GNSS-based positioning schemes, orwherein the N-GNSS-based positioning scheme information comprises a set of rules for N-GNSS-based positioning scheme selection, and the set of conditions is determined based on an evaluation of the set of rules, orwherein the N-GNSS-based positioning scheme information comprises a ranked list of positioning schemes for successive performance until an acceptable N-GNSS-based location measurement is obtained at a threshold level of quality, orany combination thereof.

6. The UE of claim 4, wherein the N-GNSS-based positioning scheme information is received via medium access control control element (MAC-CE)7. The UE of claim 4, wherein the capability information comprises: a first capability of the UE to support the set of N-GNSS-based positioning schemes, ora second capability of the UE to support one or more N-GNSS-based positioning schemes from the set of N-GNSS-based positioning schemes with a measurement gap, orQC2500095WOQualcomm Ref. No. 2500095WO82 / 85a third capability of the UE to support at least one N-GNSS-based positioning scheme from the set of secondary N-GNSS-based positioning schemes with one or more respective scheme-specific measurement gaps, orany combination thereof.

8. The UE of claim 1, wherein the one or more processors, either alone or in combination, are further configured to:transmit, via the one or more transceivers, a measurement report comprising an indication of a N-GNSS-based positioning scheme used to obtain the N-GNSS-based location estimate.

9. The UE of claim 1, wherein the one or more processors, either alone or in combination, are further configured to:attempt to obtain a location estimate of the UE in accordance with a positioning scheme sequence that is based on a ranked list of N-GNSS-based positioning schemes, wherein the N-GNSS-based location estimate corresponds to an earliest successful location estimate attempt based on the ranked list of N-GNSS-based positioning schemes.

10. The UE of claim 9, wherein the ranked list of ranked list of N-GNSS-based positioning schemes is UE-determined, network-configured or pre-defined.

11. The UE of claim 1,wherein the N-GNSS-based location estimate is associated with a set of location validity timers, andwherein the NTN-based communication function is performed based on the N-GNSS-based location estimate while the set of location validity timers is valid.

12. Hie UE of claim 11,wherein the set of location validity timers comprises a single location validity timer associated with the GNSS-based positioning scheme and the N-GNSS-based positioning scheme, orQC2500095WOQualcomm Ref. No. 2500095WO83 / 85wherein the set of location validity timers comprises a first location validity timer associated with the GNSS-based positioning scheme and a second location validity timer associated with the N-GNSS-based positioning scheme.

13. The UE of claim 1, wherein the N-GNSS-based location estimate is determined at the UE based on one or more measurement gaps.

14. The UE of claim 13, wherein the one or more measurement gaps are N-GNSS-based positioning scheme-specific.

15. The UE of claim 13,wherein the one or more measurement gaps comprise one or more network-configured measurement gaps, orwherein the one or more measurements gaps comprise one or more autonomous measurement gaps, ora combination thereof.

16. The UE of claim 1, wherein the NTN-based communication function comprises:of a timing advance value associated with uplink synchronization between the UE and a NTN entity, orreport of first propagation delay information associated with the GNSS-based positioning scheme, orreporting of second propagation delay information associated with the N-GNSS-based positioning scheme, orone or more RRC-IDLE mode functions, orone or more mobility functions, orany combination thereof.

17. A network component, comprising:one or more memories;one or more transceivers; andQC2500095WOQualcomm Ref. No. 2500095WO84 / 85one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors, either alone or in combination, being configured to:receive, via the one ormore transceivers, from a user equipment (UE), non-Global Navigation Satellite System (N-GNSS)-based positioning scheme capability information of the UE; andtransmit, via the one or more transceivers, to the UE in response to the N-GNSS-based positioning scheme capability information, N-GNSS-based positioning scheme information associated with a set of secondary N-GNSS-based positioning schemes for a (NTN)-based communication function,wherein the NTN-based communication function is associated with a primary GNSS-based positioning scheme.

18. The network component of claim 17, wherein the set of N-GNSS-based positioning schemes comprises one or more terrestrial network (TN)-based, UE-based positioning schemes, one or more NTN-based positioning schemes associated with one or more respective low earth orbit (LEO) constellations, or a combination thereof.

19. The network component of claim 17,wherein the N-GNSS-based positioning scheme information comprises a preferred N-GNSS-based positioning scheme or a set of preferred N-GNSS-based positioning schemes, orwherein the N-GNSS-based positioning scheme information comprises a set of rules for N-GNSS-based positioning scheme selection, orwherein the N-GNSS-based positioning scheme information comprises a ranked list of positioning schemes for successive performance until an acceptable N-GNSS-based location measurement is obtained at a threshold level of quality, orany combination thereof.

20. The network component of claim 19, wherein the N-GNSS-based positioning scheme information is transmitted via medium access control control element (MAC-CE).QC2500095WO

Images