Frequency Domain Search Window for Non-Terrestrial Wave Network Positioning Reference Signal

Abstract

Techniques for wireless positioning are disclosed. In one aspect, a network entity may determine a predicted Doppler frequency shift offset and a frequency domain search window corresponding to the predicted Doppler frequency shift offset uncertainty for at least one positioning reference signal (PRS) resource associated with at least one non-terrestrial transmit-receive point (NT-TRP) for a positioning session. The network entity may measure at least one PRS resource within the frequency domain search window during the positioning session.

Description

Technical Field

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

Background Art

[0002] Description of Related Art Wireless communication systems have evolved through various generations, including first-generation (1G) analog wireless telephone services, second-generation (2G) digital wireless telephone services (including interim 2.5G and 2.75G networks), third-generation (3G) high-speed data, Internet-capable wireless services, and fourth-generation (4G) services (e.g., Long Term Evolution (LTE) or WiMax). Currently, many different types of wireless communication systems are in use, including cellular systems 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), Global System for Mobile communications (GSM) for mobile communication, and the like.

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

Summary of the Invention

[0004] The following presents a simplified summary of one or more aspects disclosed in this specification. Accordingly, the following summary should not be considered an extensive overview of all contemplated aspects, nor should the following summary be regarded as identifying key or critical elements of all contemplated aspects or as delimiting the scope of any particular aspect. Thus, the sole purpose of the following summary is to present, in a simplified form, certain concepts related to one or more aspects of the mechanisms disclosed herein prior to the detailed description presented below.

[0005] In one aspect, a method of wireless communication performed by a network entity includes determining a predicted Doppler frequency shift offset and a frequency domain search window corresponding to the predicted Doppler frequency shift offset uncertainty for at least one positioning reference signal (PRS) resource associated with at least one non-terrestrial transmission-reception point (NT-TRP) for a positioning session, and measuring at least one PRS resource within the frequency domain search window during the positioning session.

[0006] In one aspect, a method of wireless communication performed by a first network entity includes sending, to a second network entity, information for determining a predicted Doppler frequency shift offset and a frequency domain search window corresponding to the predicted Doppler frequency shift offset uncertainty for at least one positioning reference signal (PRS) resource associated with at least one non-terrestrial transmission-reception point (NT-TRP) measured by the second network entity during a positioning session, and receiving, from the second network entity, a measurement report including information corresponding to one or more measurements made on at least one PRS resource.

[0007] In one aspect, a network entity includes a memory, at least one transceiver, and at least one processor communicatively coupled to the memory and the at least one transceiver, wherein the at least one processor is configured to determine a predicted Doppler frequency shift offset and a frequency domain search window corresponding to the predicted Doppler frequency shift offset uncertainty for at least one positioning reference signal (PRS) resource associated with at least one non-terrestrial transmission-reception point (NT-TRP) for a positioning session, and to measure at least one PRS resource within the frequency domain search window during the positioning session.

[0008] In one aspect, a first network entity includes a memory, at least one transceiver, and at least one processor communicatively coupled to the memory and the at least one transceiver, wherein the at least one processor is configured to send, via the at least one transceiver, information for determining a predicted Doppler frequency shift offset and a frequency domain search window corresponding to the predicted Doppler frequency shift offset uncertainty for at least one positioning reference signal (PRS) resource associated with at least one non-terrestrial transmit-receive point (NT-TRP) measured by a second network entity during a positioning session to the second network entity, and to receive, via the at least one transceiver, a measurement report including information corresponding to one or more measurements made by the second network entity on at least one PRS resource.

[0009] In one aspect, a network entity includes means for determining a predicted Doppler frequency shift offset and a frequency domain search window corresponding to the predicted Doppler frequency shift offset uncertainty for at least one positioning reference signal (PRS) resource associated with at least one non-terrestrial transmit-receive point (NT-TRP) for a positioning session, and means for measuring at least one PRS resource within the frequency domain search window during the positioning session.

[0010] In one aspect, a first network entity includes means for sending, to a second network entity, information for determining a predicted Doppler frequency shift offset and a frequency domain search window corresponding to the predicted Doppler frequency shift offset uncertainty for at least one positioning reference signal (PRS) resource associated with at least one non-terrestrial transmit-receive point (NT-TRP) measured by the second network entity during a positioning session, and means for receiving a measurement report including information corresponding to one or more measurements made by the second network entity on at least one PRS resource.

[0011] In one aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a network entity, cause the network entity to determine a predicted Doppler frequency shift offset and a frequency-domain search window corresponding to the predicted Doppler frequency shift offset uncertainty for at least one positioning reference signal (PRS) resource associated with at least one non-terrestrial transmit-receive point (NT-TRP) for a positioning session, and to measure at least one PRS resource within the frequency-domain search window during the positioning session.

[0012] In one aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a first network entity, cause the first network entity to send to a second network entity information for determining a predicted Doppler frequency shift offset and a frequency-domain search window corresponding to the predicted Doppler frequency shift offset uncertainty for at least one PRS resource associated with at least one NT-TRP measured by the second network entity during a positioning session, and to cause the second network entity to receive a measurement report including information corresponding to one or more measurements made on at least one PRS resource.

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

[0014] The accompanying drawings are presented to assist in the description of various aspects of the present disclosure and are provided only for purposes of illustration of the aspects and not as a limitation thereof. BRIEF DESCRIPTION OF THE DRAWINGS

[0015]

Figure 1

Figure 2A

Figure 2B

Figure 2C

Figure 3A

Figure 3B

Figure 3C

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

DETAILED DESCRIPTION OF THE INVENTION

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

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

[0018] Those skilled in the art will understand 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 referred to throughout the following description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof, depending in part on the specific application, desired design, corresponding technology, and so on.

[0019] Furthermore, many aspects will be described from the perspective of sequences of actions that will be performed, for example, by elements of a computing device. It will be recognized that the various actions described herein can be implemented by a particular circuit (e.g., application specific integrated circuits (ASICs)), by program instructions executed by one or more processors, or by a combination of both. Additionally, the sequence of actions described herein, when executed, can be considered to be fully embodied within any form of non-transitory computer-readable storage medium that stores a corresponding set of computer instructions that, when executed, cause the relevant processors of the device to perform or cause to be performed the functionality described herein. Thus, the various aspects of the present disclosure can be embodied in several different forms, all of which are intended to fall within the scope of the claimed subject matter. Additionally, for each of the aspects described herein, a corresponding form of any such aspect can be described herein, for example, as “logic configured to” perform the described action.

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

[0021] The base station may operate according to one of several RATs that the base station is communicating with the UE according to the network in which the base station is deployed. Alternatively, it may be called an access point (AP), network node, Node B, evolved Node B (eNB), next generation eNB (ng-eNB), new radio (NR) Node B (also called gNB or g-node B), etc. The base station can be mainly used to support wireless access by the UE, including supporting data, voice, and / or signaling connections for the supported UEs. In some systems, the base station may provide only the edge node signaling function, while in other systems, the base station may provide additional control and / or network management functions. The communication link through which the UE can send signals to the base station is called the uplink (UL) channel (e.g., reverse traffic channel, reverse control channel, access channel, etc.). The communication link through which the base station can transmit signals to the UE is called the downlink (DL) channel or forward link channel (e.g., paging channel, control channel, broadcast channel, forward traffic channel, etc.). The term traffic channel (TCH) used in this specification may refer to either an uplink / reverse traffic channel or a downlink / forward traffic channel.

[0022] The term "base station" may refer to a single physical transmission-reception point (TRP) or multiple physical TRPs that may or may not be collocated. For example, when the term "base station" refers to a single physical TRP, that physical TRP may be the antenna of the base station corresponding to the cell (or some cell sectors) of the base station. When the term "base station" refers to multiple collocated physical TRPs, the physical TRPs may be an array of antennas of the base station (such as in a multiple-input multiple-output (MIMO) system or when the base station employs beamforming). When the term "base station" refers to multiple non-collocated 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-collocated physical TRPs may be the serving base station that receives measurement value reports from the UE and neighboring base stations whose reference radio frequency (RF) signals the UE is measuring. Since a TRP is the point from which the base station transmits and receives wireless signals, references to transmission from the base station or reception at the base station as used herein should be understood to refer to a specific TRP of the base station.

[0023] In some implementations that support UE positioning, the base station may not support wireless access by the UE (e.g., may not support a data connection, a voice connection, and / or a signaling connection for the UE), but instead may send to the UE a reference signal that is to be measured by the UE and / or may receive and measure a signal sent by the UE. Such a base station may be referred to as a positioning beacon (e.g., when sending a signal to the UE) and / or a location measurement unit (e.g., when receiving and measuring a signal from the UE).

[0024] An "RF signal" includes an electromagnetic wave of a given frequency that propagates information through the space between a transmitter and a receiver. A transmitter as used herein may transmit a single "RF signal" or a plurality of "RF signals" to a receiver. However, due to the propagation characteristics of the RF signal through a multipath channel, the receiver may receive a plurality of "RF signals" corresponding to each transmitted RF signal. The same RF signal transmitted over different paths between the transmitter and the receiver may be referred to as a "multipath" RF signal. An RF signal as used herein may also be referred to as a "wireless signal" or simply a "signal" when the context makes it clear that the term "signal" refers to a wireless signal or an RF signal.

[0025] FIG. 1 shows an exemplary wireless communication system 100 according to an aspect of the present disclosure. (Sometimes referred to as a wireless wide area network (WWAN)) The wireless communication system 100 may include various base stations 102 (labeled "BS") and various UEs 104. The base stations 102 may include macrocell base stations (high-power cellular base stations) and / or small cell base stations (low-power cellular base stations). In one aspect, the macrocell base stations may include an eNB and / or ng-eNB corresponding to an LTE network of the wireless communication system 100, or a gNB corresponding to an NR network of the wireless communication system 100, or a combination of both, and the small cell base stations may include femtocells, picocells, microcells, etc.

[0026] The base station 102 can collectively form a RAN and interface with a core network 170 (e.g., an evolved packet core (EPC) or a 5G core (5GC)) through a backhaul link 122, and through the core network 170 with 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 172 may be part of the core network 170 or may be external to the core network 170. The location server 172 can be integrated with the base station 102. The UE 104 can communicate with the location server 172 directly or indirectly. For example, the UE 104 can communicate with the location server 172 via the base station 102 currently serving the UE 104. The UE 104 can also communicate with the location server 172 through another network, such as via a wireless local area network (WLAN) access point (AP) (e.g., AP 150 described below) via an application server (not shown), etc. For signaling purposes, the communication between the UE 104 and the location server 172 can be represented as an indirect connection (e.g., through the core network 170, etc.) or a direct connection (e.g., as shown via a direct connection 128), and intervening nodes (if any) are omitted from the signaling diagram for clarity.

[0027] In addition to other functions, base station 102 may perform one or more functions related to transferring user data, wireless channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load distribution, delivery of non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and device tracing, RAN information management (RIM), paging, positioning, and delivery of warning messages. Base stations 102 may communicate with each other directly or indirectly (e.g., through the EPC / 5GC) via a backhaul link 134, which may be wired or wireless.

[0028] Base station 102 can wirelessly communicate with UE 104. Each of the base stations 102 can provide communication coverage regarding its respective geographic coverage area 110. In one aspect, one or more cells can be supported by the base stations 102 within each geographic coverage area 110. A "cell" is a logical communication entity used for communication with a base station (e.g., via several frequency resources such as those referred to as carrier frequency, component carrier, carrier, band, etc.), and may be associated with an identifier (e.g., physical cell identifier (PCI), enhanced cell identifier (ECI), virtual cell identifier (VCI), cell global identifier (CGI), etc.) for distinguishing cells operating via the same or different carrier frequencies. In some cases, different cells can be configured according to different protocol types (e.g., machine-type communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or others) that can provide access to different types of UEs. Since a cell is supported by a specific base station, the term "cell" may, depending on the context, refer to one or both of the logical communication entity and the base station that supports it. Additionally, since the 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 the geographic coverage area (e.g., sector) of a base station as long as a carrier frequency can be detected and used for communication within a certain part of the geographic coverage area 110.

[0029] The geographical coverage area 110 of the neighboring macro cell base station 102 may partially overlap (e.g., in the handover area), and some of the geographical coverage areas 110 may be significantly overlapped by a larger geographical coverage area 110. For example, the small cell base station 102’ (labeled as “SC” for “small cell”) may have a geographical coverage area 110’ that significantly overlaps with the geographical coverage area 110 of one or more macro cell base stations 102. A network including both small cell base stations and macro cell base stations may be known as a heterogeneous network. The heterogeneous network may also include home eNBs (HeNBs) that may provide services to a limited group known as a closed subscriber group (CSG).

[0030] The communication link 120 between the base station 102 and the UE 104 may include uplink (also called reverse link) transmission from the UE 104 to the base station 102 and / or downlink (DL) (also called forward link) transmission from the base station 102 to the UE 104. The communication link 120 may use MIMO antenna technology including spatial multiplexing, beamforming, and / or transmit diversity. The communication link 120 may be through one or more carrier frequencies. The carrier assignment may be asymmetric with respect to the downlink and uplink (e.g., more or fewer carriers may be assigned for the downlink than for the uplink).

[0031] Wireless communication system 100 may further include a WLAN access point (AP) 150 that communicates with WLAN stations (STAs) 152 via a communication link 154 in an unlicensed frequency spectrum (e.g., 5 gigahertz (GHz)). When communicating in an unlicensed frequency spectrum, the WLAN STA 152 and / or the WLAN AP 150 may perform a clear channel assessment (CCA) or listen before talk (LBT) procedure before communicating to determine whether the channel is available.

[0032] Small cell base station 102’ may operate in a licensed frequency spectrum and / or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell base station 102’ may utilize LTE technology or NR technology and use the same 5 GHz unlicensed frequency spectrum as used by the WLAN AP 150. A small cell base station 102’ that employs LTE / 5G in an unlicensed frequency spectrum may expand the coverage to the access network and / or increase the capacity of the access network. NR in an unlicensed spectrum may be referred to as NR-U. LTE in an unlicensed spectrum may sometimes be referred to as LTE-U, licensed assisted access (LAA), or MulteFire.

[0033] The wireless communication system 100 may further include an mmW base station 180 that communicates with the UE 182 and can operate at millimeter wave (mmW) frequencies and / or near mmW. Extremely high frequency (EHF) is a part of RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength of 1 millimeter to 10 millimeters. Radio waves within this band can be called millimeter waves. Near mmW can drop down to a frequency of 3 GHz with a wavelength of 100 millimeters. The super high frequency (SHF) band ranges from 3 GHz to 30 GHz and is also called centimeter waves. Communication using the mmW / near mmW radio frequency band has high path loss and a relatively short range. The mmW base station 180 and the UE 182 may utilize beamforming (transmission and / or reception) via the mmW communication link 184 to compensate for the extremely high path loss and short range. Further, in an alternative configuration, it will be understood that one or more base stations 102 may also transmit using mmW or near mmW and beamforming. Accordingly, it will be understood that the above examples are merely examples and should not be construed as limiting the various aspects disclosed herein.

[0034] Transmission beamforming is a technique for concentrating RF signals in a specific direction. Conventionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts the signal in all directions (omnidirectionally). Using transmission beamforming, the network node determines where a given target device (e.g., a UE) is located with respect to the transmitting network node and emits a stronger downlink RF signal in that specific direction, thereby providing a faster and more powerful RF signal to the receiving device (from the perspective of data rate). To change the directivity of the RF signal when transmitting, the network node can control the phase and relative amplitude of the RF signal at each of one or more transmitters that are broadcasting the RF signal. For example, the network node may use an array of antennas (also called a "phased array" or "antenna array") that can create a beam of RF waves that can be "steered" to point in different directions without actually moving the antennas. Specifically, the RF currents from the transmitters are supplied to the individual antennas in appropriate phase relationships such that the radio waves from the separate antennas are combined to cancel out and suppress radiation in unwanted directions while increasing the radiation in the desired direction.

[0035] The transmission beams may be quasi-collocated, which means that, regardless of whether the transmission antennas of the network node itself are physically collocated, the receiver (e.g., UE) sees the transmission beams as having the same parameters. In NR, there are four types of quasi-co-location (QCL) relationships. Specifically, a given type of QCL relationship means that certain parameters for 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 of 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 of QCL type B, the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of a second reference RF signal transmitted on the same channel. If the source reference RF signal is of 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 of QCL type D, the receiver can use the source reference RF signal to estimate the spatial reception parameters of a second reference RF signal transmitted on the same channel.

[0036] 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 of an array of antennas in that direction and / or adjust the phase setting in order to amplify (e.g., increase its gain level) an RF signal received from a particular direction. Thus, when the receiver is said to beamform in a particular direction, it means that the beam gain in that direction is higher than the beam gain along other directions, or that the beam gain in that direction is the highest compared to the beam gains of all other receive beams available to the receiver in that direction. 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 signal received from that direction.

[0037] Transmit and receive beams may be spatially related. Spatial relationship means that parameters for a second beam (e.g., a transmit beam or a 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 receive a reference downlink reference signal (e.g., a synchronization signal block (SSB)) from a base station using a particular receive beam. The UE can then form a transmit beam for sending an uplink reference signal (e.g., a sounding reference signal (SRS)) to that base station based on the parameters of the receive beam.

[0038] Note that the "downlink" beam can be either a transmit beam or a receive beam depending on the entity forming it. For example, when the base station forms a downlink beam to transmit a reference signal to the UE, the downlink beam is a transmit beam. However, when the UE forms a downlink beam, it is a receive beam for receiving the downlink reference signal. Similarly, the "uplink" beam can be either a transmit beam or a receive beam depending on the entity forming it. For example, when the base station forms an uplink beam, it is an uplink receive beam, and when the UE forms an uplink beam, it is an uplink transmit beam.

[0039] The electromagnetic spectrum is often subdivided into various classes, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands are identified as the frequency range designations FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). Although a portion of FR1 is higher than 6 GHz, it should be understood that FR1 is often (interchangeably) referred to as the "sub-6 GHz" band in various documents and papers. Similar nomenclature issues can arise with respect to FR2, which, although different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) identified by the International Telecommunications Union (ITU) as the "millimeter wave" band, is often (interchangeably) referred to as the "millimeter wave" band in documents and papers.

[0040] The frequency between FR1 and FR2 is often referred to as the intermediate band frequency. In recent 5G NR research, the operating band for these intermediate band frequencies is identified as the frequency range designation FR3 (7.125 GHz to 24.25 GHz). The frequency bands included within FR3 may inherit FR1 characteristics and / or FR2 characteristics, and thus may, in fact, extend the characteristics of FR1 and / or FR2 to the intermediate 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 are identified as the frequency range designations FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands is included within the EHF band.

[0041] With the above aspects in mind, unless otherwise specifically described, terms such as "sub-6 GHz" when used in this specification may be understood to broadly represent frequencies that can be less than 6 GHz, can be within FR1, or can include the intermediate band frequency. Furthermore, unless otherwise specified, terms such as "millimeter wave" when used in this specification may be understood to broadly represent frequencies that can include the intermediate band frequency, frequencies that can be within the range of FR2, FR4, FR4-a or FR4-1, and / or FR5, or frequencies that can be within the range of the EHF band.

[0042] In a multi-carrier system such as 5G, one of the carrier frequencies is called the "primary carrier" or "anchor carrier" or "primary serving cell" or "PCell", and the remaining carrier frequencies are called the "secondary carrier" or "secondary serving cell" or "SCell". In carrier aggregation, the anchor carrier is the carrier that operates on the primary frequency (e.g., FR1) used by the UE104 / 182 and the cell with which the UE104 / 182 performs the initial radio resource control (RRC) connection establishment procedure or starts the RRC connection re-establishment procedure. The primary carrier carries all common control channels and UE-specific control channels and can be a carrier within the licensed frequency (however, it is not always the case). The secondary carrier can be configured when an RRC connection is established between the UE104 and the anchor carrier and is a carrier that operates on a second frequency (e.g., FR2) that can be used to provide additional radio resources. In some cases, the secondary carrier can be a carrier within the unlicensed frequency. Since both the primary uplink carrier and the primary downlink carrier are usually UE-specific, the secondary carrier is assumed to contain only the necessary signaling information and signals. For example, there should be no UE-specific signaling information and signals within the secondary carrier. This means that different UE104 / 182 within a cell can have different downlink primary carriers. The same applies to the uplink primary carrier. The network can change the primary carrier of any UE104 / 182 at any time. This is done, for example, to balance the load on different carriers. The terms "cell", "serving cell", "component carrier", "carrier frequency", etc. can be used interchangeably since the "serving cell" (regardless of PCell or SCell) corresponds to the carrier frequency / component carrier through which several base stations communicate.

[0043] For example, still referring to FIG. 1, one of the frequencies utilized by macrocell base station 102 can be an anchor carrier (or "PCell"), and other frequencies utilized by macrocell base station 102 and / or mmW base station 180 can be secondary carriers ("SCell"). By simultaneously transmitting and / or receiving on multiple carriers, UE 104 / 182 can significantly increase its data transmission and / or reception rate. For example, two 20 MHz carriers aggregated within a multi-carrier system would, in theory, result in a doubling of the data rate (i.e., 40 MHz) compared to the data rate achieved by a single 20 MHz carrier.

[0044] Wireless communication system 100 may further include a UE 164 that may communicate with macrocell base station 102 via communication link 120 and / or with mmW base station 180 via mmW communication link 184. For example, macrocell base station 102 may support a PCell and one or more SCell for UE 164, and mmW base station 180 may support one or more SCell for UE 164.

[0045] In some cases, UE164 and UE182 may be capable of sidelink communication. Sidelink-capable UEs (SL-UEs) can communicate with base station 102 via communication link 120 using the Uu interface (i.e., the air interface between the UE and the base station). An SL-UE (e.g., UE164, UE182) may also communicate directly with each other via wireless sidelink 160 using the PC5 interface (i.e., the air interface between sidelink-capable UEs). A wireless sidelink (or simply "sidelink") is compliant with the core cellular (e.g., LTE, NR) standard that enables direct communication between two or more UEs without the need for communication to pass through a base station. Sidelink communication may be unicast or multicast, and can 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 the groups of SL-UEs that utilize sidelink communication may be within the geographical coverage area 110 of base station 102. Other SL-UEs in such a group may be outside the geographical coverage area 110 of base station 102 or may, in some cases, be unable to receive transmissions from base station 102. In some cases, the group of SL-UEs communicating via sidelink communication may utilize a one-to-many (1:M) system where each SL-UE transmits to all other SL-UEs within the group. In some cases, base station 102 facilitates the scheduling of resources for sidelink communication. In other cases, sidelink communication is performed between SL-UEs without the involvement of base station 102.

[0046] In one aspect, sidelink 160 may operate on a target wireless communication medium, and the associated communication medium may be shared with other wireless communications between other vehicles and / or infrastructure access points, and other RATs. The "medium" may be composed of one or more time, frequency, and / or spatial communication resources associated with wireless communication between one or more transmitter / receiver pairs (including, for example, one or more channels across one or more carriers). In one aspect, the target medium may correspond to at least a portion of an unlicensed frequency band shared among various RATs. Different licensed frequency bands are reserved for certain communication systems (e.g., by a government agency such as the Federal Communications Commission (FCC) in the United States), but these systems, particularly those employing small cell access points, have recently extended their operation to unlicensed frequency bands such as the Unlicensed National Information Infrastructure (U-NII) band used by wireless local area network (WLAN) technologies, most notably the IEEE 802.11x WLAN technologies commonly referred to as "Wi-Fi". Exemplary systems of this type include various variants such as CDMA systems, TDMA systems, FDMA systems, orthogonal FDMA (OFDMA) systems, single-carrier FDMA (SC-FDMA) systems, and the like.

[0047] FIG. 1 shows only two of the UEs as SL-UEs (i.e., UEs 164 and 182), but it should be noted that any of the illustrated UEs may be an SL-UE. Further, although only UE 182 was described as being beamforming capable, any of the illustrated UEs, including UE 164, may be beamforming capable. When beamforming capable, the SL-UEs may beamform towards each other (i.e., towards other SL-UEs), towards other UEs (e.g., UE 104), towards base stations (e.g., base stations 102, 180, small cell 102', access point 150), and so on. Thus, in some cases, UEs 164 and 182 may utilize beamforming via sidelink 160.

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

[0049] In a satellite positioning system, the use of signal 124 may be associated with use involving one or more global and / or regional navigation satellite systems or may be enabled in another way for such use and may be enhanced by various satellite-based augmentation systems (SBAS). For example, SBAS may include augmentation systems that provide integrity information, error correction, etc., such as the Wide Area Augmentation System (WAAS), the European Geostationary Navigation Overlay Service (EGNOS), the Multi-functional Satellite Augmentation System (MSAS), the Global Positioning System (GPS) - assisted Geo Augmented Navigation, or the GPS and Geo Augmented Navigation system (GAGAN). Thus, the satellite positioning system as used herein may include any combination of one or more global and / or regional navigation satellites associated with such one or more satellite positioning systems.

[0050] In one aspect, SV112 can be part of one or more non-terrestrial networks (NTNs), additionally or alternatively. In an NTN, SV112 is connected to an earth station (ES) 118 (also referred to as a ground station, NTN gateway, or gateway), which is then connected to an element in a 5G network, such as a modified base station 102 (without a terrestrial antenna) or a network node in the 5GC (e.g., core network 170). This element then provides 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, UE114 and / or 116 can receive communication signals (e.g., signal 124) from SV112 instead of or in addition to communication signals from terrestrial base station 102. The wireless link between the UE (e.g., UE114, 116) and SV112 is referred to as a "service link" (e.g., service link 124). The wireless link between SV112 and earth station 118 is referred to as a "feeder link" (e.g., feeder link 126).

[0051] NTN can also be used to enhance 5G service reliability by providing service continuity for machine-to-machine (M2M) devices and / or IoT devices, or for passengers on a moving platform (e.g., a passenger vehicle such as an aircraft, ship, high-speed train, bus, etc.), or by guaranteeing service availability anywhere, especially for critical communications. NTN can also enable 5G network scalability by providing efficient multicast / broadcast resources for data delivery towards the network edge or even towards the UE (e.g., UE114 and / or 116).

[0052] In the example of FIG. 1, SV112 communicates with UE114 (representing a UE outside the coverage area of base station 102 and in an area not served by the terrestrial 5G network) and UE116 (representing a UE inside the coverage area of base station 102 and not fully served by the terrestrial 5G network). Thus, SV112 may act as a serving base station for UE114 and as a primary cell or secondary cell for UE116 depending on the service provided by base station 102 to UE116.

[0053] Note that although FIG. 1 shows only a single SV112 and a single terrestrial station 118, it should be understood that this is merely an example, and there may be any number of SV112s connected to any number of terrestrial stations 118.

[0054] Wireless communication system 100 may further include one or more UEs, such as UE190, that are indirectly connected to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (referred to as "sidelinks"). In the example of FIG. 1, UE190 has a D2D P2P link 192 with one of UE104s connected to one of base stations 102 (e.g., through which UE190 may indirectly obtain a cellular connection) and a D2D P2P link 194 with WLAN STA152 connected to WLAN AP150 (through which UE190 may indirectly obtain a WLAN-based Internet connection). In one example, D2D P2P links 192 and 194 may be supported using any well-known D2D radio access technology (RAT), such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), Bluetooth®.

[0055] Figure 2A shows an exemplary wireless network configuration 200. For example, 5GC 210 (also referred to as Next Generation Core (NGC)) can be functionally regarded 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 network, IP routing, etc.) that operate collaboratively to form a core network. User plane interface (NG-U) 213 and control plane interface (NG-C) 215 connect gNB 222 to 5GC 210, specifically to user plane function 212 and control plane function 214, respectively. In an additional configuration, ng-eNB 224 may also be connected to 5GC 210 via NG-C 215 to the control plane function 214 and NG-U 213 to the user plane function 212. Further, ng-eNB 224 may communicate directly with gNB 222 via backhaul connection 223. In some configurations, Next Generation RAN (NG-RAN) 220 may have one or more gNBs 222, while other configurations include one or more of either ng-eNB 224 and gNB 222. Either gNB 222 or ng-eNB 224 (or both) may communicate with one or more UEs 204 (e.g., any of the UEs described herein).

[0056] Another optional aspect may include a location server 230 that may be communicating with the 5GC 210 to provide location assistance to the UE 204. The location server 230 may be implemented as a plurality of distinct servers (e.g., physically distinct servers, different software modules on a single server, different software modules across multiple physical servers, etc.), or alternatively, each may correspond to a single server. The location server 230 may be configured to support one or more location services for the UE 204 that can connect to the location server 230 via the core network, via the 5GC 210, and / or via the Internet (not shown). Further, the location server 230 may be integrated within components 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 a service server).

[0057] Figure 2B shows another exemplary wireless network structure 240. 5GC 260 (which may correspond to 5GC 210 in Figure 2A) can be regarded as a control plane function provided by an access and mobility management function (AMF) 264 that operates cooperatively to form a core network (i.e., 5GC 260), and a user plane function provided by a user plane function (UPF) 262. The functions of 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, a transparent proxy service for routing SM messages, access authentication and authorization, transport for short message service (SMS) messages between UE 204 and a short message service function (SMSF) (not shown), and security anchor functionality (SEAF). AMF 264 also interacts with an authentication server function (AUSF) (not shown) and UE 204 and receives an intermediate key established as a result of the UE 204 authentication process. In the case of authentication based on a UMTS (Universal Mobile Telecommunications System) subscriber identity module (USIM), AMF 264 retrieves security material from the AUSF. The functions of AMF 264 also include security context management (SCM).The SCM receives from the SEAF the keys that the SCM uses to derive the access network specific keys. The functionality of the AMF264 also includes location service management for regulatory services, transport for location service messages between the UE204 and the Location Management Function (LMF) 270 acting as the location server 230, transport for location service messages between the NG-RAN220 and the LMF270, allocation of EPS bearer identifiers for interacting with the evolved packet system (EPS), and UE204 mobility event notifications. In addition, the AMF264 supports functions for non-3GPP (Third Generation Partnership Project) access networks.

[0058] The functions of the UPF 262 include, when applicable, acting as an anchor point for RAT-in / RAT-inter mobility, acting as an external protocol data unit (PDU) session point for interconnection to a data network (not shown), performing 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 (mapping from service data flow (SDF) to QoS flow), transport-level packet marking in the uplink and downlink, downlink packet buffering and downlink data notification triggering, and sending and forwarding one or more "end markers" to the source RAN node. The UPF 262 may also support the transfer of location service messages on the user plane between the UE 204 and a location server such as the SLP 272.

[0059] 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 in the UPF 262 for routing traffic to appropriate destinations, some control of policy enforcement and QoS, and downlink data notification. The interface through which the SMF 266 communicates with the AMF 264 is called the N11 interface.

[0060] Another optional aspect may include an LMF 270 that is communicating with the 5GC 260 to provide location assistance to the UE 204. The LMF 270 may be implemented as a plurality of distinct servers (e.g., physically distinct servers, different software modules on a single server, different software modules across multiple physical servers, etc.), or alternatively, each may correspond to a single server. The LMF 270 may be configured to support one or more location services for the UE 204 that can connect to the LMF 270 via the core network, via the 5GC 260, and / or via the Internet (not shown). The SLP 272 may support functions similar to those of the LMF 270, while on the other hand, the LMF 270 may communicate with the AMF 264, the NG-RAN 220, and the UE 204 via the control plane (e.g., using interfaces and protocols intended to convey signaling messages rather than voice or data), and the SLP 272 may communicate with the UE 204 and an external client (e.g., a third-party server 274) via the user plane (e.g., using protocols intended to carry voice and / or data such as the transmission control protocol (TCP) and / or IP).

[0061] Another optional aspect may include communicating 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 a third-party server 274 that may be communicating with the UE 204 to obtain location information (e.g., a location estimate) for the UE 204. Thus, in some cases, the third-party server 274 may be referred to as a location service (LCS) client or an external client. The third-party server 274 may be implemented as a plurality of distinct servers (e.g., physically distinct servers, different software modules on a single server, different software modules spread across multiple physical servers, etc.), or alternatively, each may correspond to a single server.

[0062] The user plane interface 263 and the control plane interface 265 connect the 5GC 260, specifically the UPF 262 and the AMF 264, respectively, to one or more gNBs 222 and / or ng-eNBs 224 within the NG-RAN 220. The interface between the gNB 222 and / or ng-eNB 224 and the AMF 264 is called the "N2" interface, and the interface between the gNB 222 and / or ng-eNB 224 and the UPF 262 is called the "N3" interface. The gNBs 222 and / or ng-eNBs 224 of the NG-RAN 220 may communicate directly with each other via a backhaul connection 223 called the "Xn-C" interface. One or more of the gNB 222 and / or ng-eNB 224 may communicate with one or more UEs 204 via a wireless interface called the "Uu" interface.

[0063] The functionality of gNB 222 can be split 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. The gNB-CU 226 is a logical node that includes base station functions such as transferring user data, mobility control, radio access network sharing, positioning, session management, etc., except for those functions that are exclusively allocated to the gNB-DU 228. More specifically, the gNB-CU 226 generally hosts the radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) protocols of the gNB 222. The gNB-DU 228 is a logical node that generally hosts the radio link control (RLC) and medium access control (MAC) layers 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 one or more gNB-DUs 228 is called the "F1" interface. The physical (PHY) layer functionality of the gNB 222 is generally hosted by one or more stand-alone gNB-RUs 229 that perform functions such as power amplification and signal transmission / reception. The interface between the gNB-DU 228 and the gNB-RU 229 is called the "Fx" interface. Thus, the UE 204 communicates with the gNB-CU 226 via the RRC, SDAP, and PDCP layers, with the gNB-DU 228 via the RLC and MAC layers, and with the gNB-RU 229 via the PHY layer.

[0064] The deployment of a communication system such as a 5G NR system may be configured in multiple ways using various components or parts. In a 5G NR system or network, network devices such as network nodes, network entities, network mobility elements, RAN nodes, core network nodes, network elements, or base stations, or one or more units (or one or more components) that implement base station functionality may be implemented in an integrated or separated architecture. For example, a base station (such as a Node B (NB), evolved NB (eNB), NR base station, 5G NB, access point (AP), transmit-receive point (TRP), or cell) may be implemented as an integrated base station (also known as a stand-alone base station or a monolithic base station) or a separated base station.

[0065] The integrated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. The separated 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 units or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)). In some aspects, the CU may be implemented within a RAN node, one or more DUs may be collocated with the CU, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. The DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may also be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0066] The operation or network design of the base station type may consider the aggregation characteristics of the base station functions. For example, a distributed base station can be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN, such as a network configuration supported by the O-RAN Alliance), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Non-aggregation may include dispersing functions across two or more units at various physical locations, as well as virtually dispersing functions for at least one unit, which may enable flexibility in network design. The various units of a non-aggregated base station, or a non-aggregated RAN architecture, can be configured for wired or wireless communication with at least one other unit.

[0067] Figure 2C shows an exemplary split base station architecture 250 according to an aspect of the present disclosure. The split base station architecture 250 can communicate directly with a core network 267 (e.g., 5GC 210, 5GC 260) via a backhaul link or communicate indirectly with the core network 267 through one or more split base station units (e.g., 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). The split base station architecture 250 may include one or more Central Units (CUs) 280 (e.g., gNB-CU 226) that can communicate with one or more Distributed Units (DUs) 285 (e.g., gNB-DU 228) via respective midhaul links such as an F1 interface. The DU 285 can communicate with one or more Radio Units (RUs) 287 (e.g., gNB-RU 229) via respective fronthaul links. The RU 287 can communicate with respective UEs 204 via one or more Radio Frequency (RF) access links. In some implementations, a UE 204 can be served simultaneously by multiple RUs 287.

[0068] Each of the units, namely, CU280, DU285, RU287, and the quasi-RT RIC259, non-RT RIC257, and SMO framework 255, may include one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired transmission medium or a wireless transmission medium, or may be coupled to such one or more interfaces. Each of the units, or an associated processor or controller that provides instructions to the communication interface of the unit, may be configured to communicate with one or more of the other units via the transmission medium. For example, a unit may include a wired interface configured to receive or transmit signals to one or more of the other units via a wired transmission medium. Further, the units may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as a radio frequency (RF) transceiver) configured to receive, transmit, or receive and transmit signals to one or more of the other units via a wireless transmission medium.

[0069] In some aspects, CU280 can host one or more upper layer control functions. Such control functions may include, for example, Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Service Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to communicate signals with other control functions hosted by CU280. CU280 can be configured to handle user plane functions (i.e., Central Unit - User Plane (CU - UP)), control plane functions (i.e., Central Unit - Control Plane (CU - CP)), or a combination thereof. In some implementations, CU280 can be logically divided into one or more CU - UP units and one or more CU - CP units. The CU - UP units can communicate bidirectionally with the CU - CP units via an interface such as an E1 interface when implemented in an O - RAN configuration. CU280 can be implemented to communicate with DU285 as needed for network control and signaling.

[0070] DU285 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU287. In some aspects, DU285 may host one or more of a radio link control (RLC) layer, a media access control (MAC) layer, and one or more upper physical (PHY) layers (such as modules related to forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation), at least partially in accordance with a functional split such as that defined by the 3rd Generation Partnership Project (3GPP). In some aspects, DU285 may further host one or more lower PHY layers. Each layer (or module) can be implemented using an interface configured to communicate signals with other layers (and modules) hosted by DU285 or with control functions hosted by CU280.

[0071] The lower layer functions can be implemented by one or more RUs 287. In some deployments, the RUs 287 controlled by the DU 285 may correspond to logical nodes that host an RF processing function, or a lower PHY layer function (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, at least partially based on function splitting such as lower layer function splitting. In such an architecture, the RUs 287 can be implemented to handle over the air (OTA) communication with one or more UEs 204. In some implementations, the real-time and non-real-time modes of control plane communication and user plane communication with the RUs 287 can be controlled by the corresponding DU 285. In some scenarios, this configuration can enable the DU 285 and the CU 280 to be implemented in a cloud-based RAN architecture such as a vRAN architecture.

[0072] The SMO framework 255 may be configured to support the RAN deployment and provisioning of non-virtualized and virtualized network elements. In the case of non-virtualized network elements, the SMO framework 255 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements that can be managed via an operation and maintenance interface (such as an O1 interface). In the case of 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 lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, a CU 280, a DU 285, an RU 287, and a Near RT RIC 259. In some implementations, the SMO framework 255 may communicate with hardware aspects of a 4G RAN, such as an open eNB (O-eNB) 261, via an O1 interface. Additionally, in some implementations, the SMO framework 255 may communicate directly with one or more RUs 287 via an O1 interface. The SMO framework 255 may also include a non-RT RIC 257 configured to support the functions of the SMO framework 255.

[0073] The non-RT RIC 257 may be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the quasi-RT RIC 259. The non-RT RIC 257 may be coupled to the quasi-RT RIC 259 or communicate with the quasi-RT RIC 259 (e.g., via an A1 interface). The quasi-RT RIC 259 may be configured to include logical functions that enable quasi-real-time control and optimization of RAN elements and resources by data collection and actions (e.g., via an E2 interface) through an interface connecting one or more CU 280s, one or more DUs 285s, or both, and the O-eNB to the quasi-RT RIC 259.

[0074] In some implementations, the non-RT RIC 257 may receive parameters or external enrichment information from an external server to generate an AI / ML model deployed in the quasi-RT RIC 259. Such information may be utilized by the quasi-RT RIC 259 and may be received from non-network data sources or network functions in the SMO framework 255 or the non-RT RIC 257. In some examples, the non-RT RIC 257 or the quasi-RT RIC 259 may be configured to adjust RAN behavior or performance. For example, the non-RT RIC 257 may monitor long-term trends and patterns in performance and employ an AI / ML model to implement corrective actions through the SMO framework 255 (e.g., reconfiguration via O1) or via the creation of RAN management policies (e.g., A1 policies).

[0075] Figures 3A, 3B, and 3C show some exemplary components (represented by corresponding blocks) that may be incorporated within a User Equipment (UE) 302 (which may correspond to any of the UEs described herein), a base station 304 (which may correspond to any of the base stations described herein), and a network entity 306 (which may correspond to or embody any of the network functions described herein, including location server 230 and LMF 270, or alternatively, may be independent of the NG-RAN 220 and / or 5GC 210 / 260 infrastructure shown in FIGS. 2A and 2B, such as a private network) to support the operations described herein. It will be understood that these components may be implemented in different types of devices in different implementation forms (e.g., within an ASIC, within a system-on-chip (SoC), etc.). The components shown may also be incorporated within other devices in the communication system. For example, other devices in the system may include components similar to those described to provide similar functionality. Also, a given device may include one or more of the components. For example, a device may include multiple transceiver components that enable the device to operate on multiple carriers and / or communicate via different technologies.

[0076] UE 302 and base station 304 each include one or more Wireless Wide Area Network (WWAN) transceivers 310 and 350, and provide means (e.g., means for transmitting, receiving, measuring, synchronizing, refraining from transmitting, etc.) for communicating via one or more wireless communication networks (not shown), such as an NR network, an LTE network, a GSM network, etc. WWAN transceivers 310 and 350 can each be connected to one or more antennas 316 and 356, respectively, to communicate with other network nodes such as other UEs, access points, base stations (e.g., eNBs, gNBs), etc. via at least one designated Radio Access Technology (RAT) (e.g., NR, LTE, GSM, etc.) on a target wireless communication medium (e.g., some set of time / frequency resources in a specific frequency spectrum). WWAN transceivers 310 and 350 can be variously configured to transmit and encode signals 318 and 358 (e.g., messages, instructions, information, etc.) according to the designated RAT, and conversely, to receive and decode signals 318 and 358 (e.g., messages, instructions, information, pilots, etc.). Specifically, WWAN transceivers 310 and 350 each include one or more transmitters 314 and 354, respectively, for transmitting and encoding signals 318 and 358, and each include one or more receivers 312 and 352, respectively, for receiving and decoding signals 318 and 358.

[0077] UE 302 and base station 304 also each include, in at least some cases, one or more short-range wireless transceivers 320 and 360, respectively. Short-range wireless transceivers 320 and 360 may each be connected to one or more antennas 326 and 366, respectively, and provide means (e.g., means for transmitting, means for receiving, means for measuring, means for synchronizing, means for refraining from transmitting, etc.) for communicating with other network nodes such as other UEs, access points, base stations, etc. via the wireless communication medium over at least one designated RAT (e.g., WiFi, LTE-D, Bluetooth®, Zigbee®, Z-Wave®, PC5, dedicated short-range communications (DSRC), wireless access for vehicular environments (WAVE), near-field communication (NFC), ultra-wideband (UWB), etc.). Short-range wireless transceivers 320 and 360 may be variously configured to, respectively, transmit and encode signals 328 and 368 (e.g., messages, instructions, information, etc.) and, conversely, to receive and decode signals 328 and 368 (e.g., messages, instructions, information, pilots, etc.) according to the designated RAT. Specifically, short-range wireless transceivers 320 and 360 each include one or more transmitters 324 and 364, respectively, for transmitting and encoding signals 328 and 368, and each include one or more receivers 322 and 362, respectively, for receiving and decoding signals 328 and 368. As a specific example, short-range wireless transceivers 320 and 360 may be WiFi 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.

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

[0079] Base station 304 and network entity 306 each include one or more network transceivers 380 and 390, respectively, which provide means (e.g., means for transmitting, means for receiving, etc.) for communicating with other network entities (e.g., other base stations 304, other network entities 306). For example, base station 304 may employ one or more network transceivers 380 for communicating with other base stations 304 or network entities 306 via one or more wired or wireless backhaul links. As another example, network entity 306 may employ one or more network transceivers 390 for communicating with one or more base stations 304 via one or more wired or wireless backhaul links or with other network entities 306 via one or more wired or wireless core network interfaces.

[0080] The transceiver may be configured to communicate via a wired link or a wireless link. (Regardless of whether it is a wired transceiver or a wireless transceiver), the transceiver includes a transmitter circuit configuration (e.g., transmitters 314, 324, 354, 364) and a receiver circuit configuration (e.g., receivers 312, 322, 352, 362). In some implementations, the transceiver may be an integrated device (e.g., embodying the transmitter circuit configuration and the receiver circuit configuration within a single device), in some implementations, it may include separate transmitter and receiver circuit configurations, or in other implementations, it may be embodied in other ways. The transmitter and receiver circuit configurations 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. The wireless transmitter circuit configurations (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 enables each device (e.g., UE 302, base station 304) to perform transmission “beamforming” as described herein. Similarly, the wireless receiver circuit configurations (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 enables each device (e.g., UE 302, base station 304) to perform receive beamforming as described herein. In one aspect, the transmitter and receiver circuit configurations may share a plurality of the same antennas (e.g., antennas 316, 326, 356, 366) such that each device can only receive or transmit at a given time and not both at the same time. The wireless transceivers (e.g., WWAN transceivers 310 and 350, short-range wireless transceivers 320 and 360) may also include, for example, a network listen module (NLM) for performing various measurements.

[0081] 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) used in this specification may generally be characterized as a "transceiver", "at least one transceiver", or "one or more transceivers". Thus, whether a particular transceiver is a wired transceiver or a wireless transceiver can be inferred from the type of communication being implemented. For example, backhaul communication between network devices or servers generally relates to signaling via a wired transceiver, while wireless communication between a UE (e.g., UE 302) and a base station (e.g., base station 304) generally relates to signaling via a wireless transceiver.

[0082] UE 302, base station 304, and network entity 306 may also include other components that can be used in conjunction with the operations as disclosed in this specification. UE 302, base station 304, and network entity 306 each include one or more processors 332, 384, and 394, for example, to provide functions related to wireless communication and to provide other processing functions. Thus, processors 332, 384, and 394 can be equipped with processing means such as means for determining, means for calculating, means for receiving, means for transmitting, means for instructing, etc. In one aspect, processors 332, 384, and 394 can 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 circuits, or various combinations thereof.

[0083] UE 302, base station 304, and network entity 306 each include a memory circuit that implements memories 340, 386, and 396 (e.g., each including a memory device) to maintain information (e.g., information indicating reserved resources, thresholds, parameters, etc.). Thus, memories 340, 386, and 396 can include storage means, retrieval means, maintenance means, etc. In some cases, UE 302, base station 304, and network entity 306 may each include positioning components 342, 388, and 398. Positioning components 342, 388, and 398 can be part of or coupled to processors 332, 384, and 394, respectively, which, when executed, cause UE 302, base station 304, and network entity 306 to perform the functions described herein, or can be hardware circuits. In other aspects, positioning components 342, 388, and 398 can be external to processors 332, 384, and 394 (e.g., integrated with another processing system that is part of a modem processing system, etc.). Alternatively, positioning components 342, 388, and 398 can be memory modules stored in memories 340, 386, and 396, respectively, which, when executed by processors 332, 384, and 394 (or a modem processing system, another processing system, etc.), cause UE 302, base station 304, and network entity 306 to perform the functions described herein. FIG. 3A shows possible locations of positioning component 342, which can be part of, for example, one or more WWAN transceivers 310, memory 340, one or more processors 332, or any combination thereof, or can be a stand-alone component. FIG. 3B shows possible locations of positioning component 388, which can be part of, for example, one or more WWAN transceivers 350, memory 386, one or more processors 384, or any combination thereof, or can be a stand-alone component.FIG. 3C shows possible locations of positioning component 398, which may be part of, for example, one or more network transceivers 390, memory 396, one or more processors 394, or any combination thereof, or may be a stand-alone component.

[0084] UE 302 may include one or more sensors 344 coupled to one or more processors 332 to provide means for detecting or sensing movement and / or orientation information that is independent of movement data derived from signals received by one or more WWAN transceivers 310, one or more short-range wireless transceivers 320, and / or satellite signal receiver 330. By way of example, sensors 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 altimeter), and / or any other type of motion detection sensor. Additionally, sensors 344 may include multiple different types of devices and may combine their outputs to provide movement information. For example, sensors 344 may use a combination of a multi-axis accelerometer and an orientation sensor to provide the ability to calculate a position in a two-dimensional (2D) and / or three-dimensional (3D) coordinate system.

[0085] In addition, UE 302 includes a user interface 346 that provides means for providing an indication (e.g., an acoustic and / or visual display) to the user and / or receiving user input (e.g., when a user actuates a sensing device such as a keypad, touch screen, microphone, etc.). Although not shown, base station 304 and network entity 306 may also include a user interface.

[0086] Looking more specifically at one or more processors 384, in the downlink, IP packets from network entity 306 can be provided to processor 384. The one or more processors 384 can implement functions for the RRC layer, the packet data convergence protocol (PDCP) layer, the radio link control (RLC) layer, and the media access control (MAC) layer. The one or more processors 384 are associated with RRC layer functions related to the broadcast 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 reports; PDCP layer functions related to header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions related to the transfer of upper layer PDUs, error correction by automatic repeat request (ARQ), concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and rearrangement of RLC data PDUs; and MAC layer functions related to the mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization.

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

[0088] In UE 302, receiver 312 receives signals through its respective antennas 316. Receiver 312 recovers the information modulated on the RF carrier and provides the information to one or more processors 332. Transmitter 314 and receiver 312 implement layer 1 functions associated with various signal processing functions. Receiver 312 may perform spatial processing on the information to recover any spatial streams directed to UE 302. If multiple spatial streams are directed to UE 302, they may be combined by receiver 312 into a single OFDM symbol stream. Receiver 312 then uses a fast Fourier transform (FFT) to convert the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signals, are recovered and demodulated by determining the most likely signal constellation points transmitted by base station 304. These soft decisions may be based on channel estimates calculated by a channel estimator. The soft decisions are then decoded and deinterleaved to recover the data signals and control signals originally transmitted by base station 304 on the physical channel. The data and control signals are then provided to one or more processors 332 that implement layer 3 (Layer-3, L3) and layer 2 (Layer-2, L2) functions.

[0089] On the uplink, one or more processors 332 provide demultiplexing in reverse between the transport channel and the logical channel, packet reassembly, decoding, header recovery, and control signal processing to recover IP packets from the core network. One or more processors 332 are also responsible for error detection.

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

[0091] Channel estimates derived by a channel estimator from a reference signal or feedback transmitted by the base station 304 can be used by the transmitter 314 to select an appropriate coding and modulation scheme and to facilitate spatial processing. The spatial streams generated by the transmitter 314 can be provided to different antennas 316. The transmitter 314 can modulate an RF carrier using individual spatial streams for transmission.

[0092] Uplink transmission is processed at the base station 304 in a manner similar to the method described with respect to the receiver function in the UE 302. The receiver 352 receives signals via its respective antennas 356. The receiver 352 recovers the information modulated on the RF carrier and provides the information to one or more processors 384.

[0093] On the uplink, one or more processors 384 provide demultiplexing between transport channels and logical channels, packet reassembly, decoding, header restoration, and control signal processing to recover IP packets from the UE 302. IP packets from one or more processors 384 can be provided to the core network. One or more processors 384 are also responsible for error detection.

[0094] For the sake of 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 can be configured according to the various examples described herein. However, it should be understood that the shown components may have different functions in different designs. Specifically, the various components in FIGS. 3A-3C are optional in alternative configurations, and the various aspects include configurations that may vary due to design choices, cost, device usage, or other considerations. For example, in the case of FIG. 3A, a particular implementation of the UE 302 may omit the WWAN transceiver 310 (e.g., a wearable device or a tablet computer or a PC or a laptop may have Wi-Fi and / or Bluetooth capabilities without cellular capabilities), or may omit the short-range wireless transceiver 320 (e.g., cellular only), or may omit the satellite signal receiver 330, or may omit the sensor 344, etc. In another example, in the case of FIG. 3B, a particular implementation of the base station 304 may omit the WWAN transceiver 350 (e.g., a Wi-Fi "hotspot" access point without cellular functionality), or may omit the short-range wireless transceiver 360 (e.g., cellular only), or may omit the satellite receiver 370, etc. For the sake of brevity, examples of various alternative configurations are not provided herein, but should be readily understandable to those skilled in the art.

[0095] The various components of the UE 302, base station 304, and network entity 306 can be communicatively coupled to each other via data buses 334, 382, and 392, respectively. In one aspect, the data buses 334, 382, and 392 can form, or be part of, the communication interfaces of the UE 302, base station 304, and network entity 306, respectively. For example, if different logical entities are implemented within the same device (e.g., a gNB and location server functionality incorporated within the same base station 304), the data buses 334, 382, and 392 can provide communication between them.

[0096] The components of FIGS. 3A, 3B, and 3C can be implemented in various ways. In some implementations, the components of FIGS. 3A, 3B, and 3C can 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 - 346 can be implemented by the processor and memory components of UE 302 (e.g., by execution of appropriate code and / or by appropriate configuration of the processor components). Similarly, some or all of the functionality represented by blocks 350 - 388 can be implemented by the processor and memory components of base station 304 (e.g., by execution of appropriate code and / or by appropriate configuration of the processor components). Also, some or all of the functionality represented by blocks 390 - 398 can be implemented by the processor and memory components of network entity 306 (e.g., by execution of appropriate code and / or by appropriate configuration of the processor components). For simplicity, in this specification, various operations, actions, and / or functions are described as being performed "by the UE", "by the base station", "by the network entity", etc. However, as will be understood, such operations, actions, and / or functions are actually performed by specific components or combinations of components of UE 302, base station 304, network entity 306, such as processors 332, 384, 394, transceivers 310, 320, 350, and 360, memories 340, 386, and 396, positioning components 342, 388, and 398, etc.

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

[0098] NR supports several cellular network-based positioning techniques, including downlink-based positioning methods, uplink-based positioning methods, and downlink- and uplink-based positioning methods. Downlink-based positioning methods include observed time difference of arrival (OTDOA) in LTE, downlink time difference of arrival (DL-TDOA) in NR, and downlink angle-of-departure (DL-AoD) in NR. Figure 4 shows examples of various positioning methods according to aspects of the present disclosure. In the OTDOA or DL-TDOA positioning procedure shown by scenario 410, the UE measures the difference between the times of arrival (ToAs) of reference signals (e.g., positioning reference signals (PRS)) received from a pair of base stations, referred to as reference signal time difference (RSTD) measurements or time difference of arrival (TDOA) measurements, and reports them to a positioning entity. More specifically, the UE receives identifiers (IDs) of a reference base station (e.g., serving base station) and a plurality of non-reference base stations in assistance data. The UE then measures the RSTD between each of the reference base station and the non-reference base stations. Based on the known locations of the involved base stations and the RSTD measurements, a positioning entity (e.g., the UE in the case of UE-based positioning, or a location server in the case of UE-assisted positioning) can estimate the location of the UE.

[0099] In the case of DL-AoD positioning shown by scenario 420, the positioning entity uses measurement reports from the UE of the received signal strength measurements of a plurality of downlink transmission beams to determine the angle between the UE and the transmitting base station. The positioning entity can then estimate the location of the UE based on the determined angle and the known location of the transmitting base station.

[0100] The uplink-based positioning method includes 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, the UE transmits one or more uplink reference signals measured by a reference base station and a plurality of non-reference base stations. Each base station then reports the reception time of the reference signal (referred to as relative time of arrival (RTOA)) to a positioning entity (e.g., a location server) that knows the location 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.

[0101] In the case of 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 the UE on one or more uplink reception beams. The positioning entity uses the signal strength measurements and the angles of the reception beams to determine the angle between the UE and the base station. Based on the determined angle and the known locations of the base stations, the positioning entity can then estimate the location of the UE.

[0102] 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 the RTT procedure, a first entity (e.g., a base station or UE) transmits a first RTT-related signal (e.g., a PRS or SRS) to a second entity (e.g., a UE or base station), and the second entity transmits a second RTT-related signal (e.g., an SRS or PRS) back to the first entity. Each entity measures the time difference between the arrival time (ToA) of the received RTT-related signal and the transmission time of the transmitted RTT-related signal. This time difference is called the reception-to-transmission (Rx-Tx) time difference. The Rx-Tx time difference measurements can be made or adjusted to include only the time difference between the closest slot boundaries for the received and transmitted signals. Then, both entities can send their Rx-Tx time difference measurements to a location server (e.g., LMF270), and the location server calculates the round-trip propagation time (i.e., the 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, and then the other entity 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). In the case of multi-RTT positioning shown by scenario 430, a first entity (e.g., a UE or base station) performs RTT positioning procedures with a plurality of second entities (e.g., a plurality of base stations or UEs) to enable the determination of the location of the first entity based on the distance to the second entity and the known location of the second entity (e.g., using multi-lateration).As shown by scenario 440, the RTT and multi-RTT methods can be combined with other positioning techniques such as UL-AoA and DL-AoD to improve location accuracy.

[0103] The E-CID positioning method is based on radio resource management (RRM) measurements. In E-CID, the UE reports the serving cell ID, timing advance (TA), and the identifiers, estimated timing, and signal strengths of detected neighboring base stations. The location of the UE is then estimated based on this information and the known locations of the base stations.

[0104] To assist with the positioning operation, 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 the identifier of the base station (or cell / TRP of the base station) from which to measure the reference signal, reference signal configuration parameters (e.g., the number of consecutive slots containing the PRS, the periodicity of the consecutive slots containing the PRS, the muting sequence, the frequency hopping sequence, the reference signal identifier, the reference signal bandwidth, etc.), and / or other parameters applicable to a particular positioning method. Alternatively, the assistance data may be obtained directly from the base station itself (e.g., in an overhead message broadcast periodically). In some cases, the UE may be able to detect neighboring network nodes themselves without using the assistance data.

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

[0106] Location estimation may be referred to by other names such as position estimation, location, position, position fix, fix, etc. A location estimate may be geodetic and include coordinates (e.g., latitude, longitude, and optionally altitude), or it may be civic and include a street address, postal address, or some other linguistic description of the location. Location estimation may further be defined relative to some other known location or may be defined absolutely (e.g., using latitude, longitude, and optionally 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 a specified level or default level of confidence).

[0107] To support downlink and uplink transmissions between network nodes (e.g., base stations and UEs), various frame structures may be used. FIG. 5 is a diagram 500 showing an exemplary frame configuration according to an aspect of the present disclosure. The frame structure may be a downlink or uplink frame structure. Other wireless communication technologies may have different frame structures and / or different channels.

[0108] LTE, and in some cases NR, utilize Orthogonal Frequency Division Multiplexing (OFDM) on the downlink and Single-Carrier Frequency Division Multiplexing (SC-FDM) on the uplink. However, unlike LTE, NR also has the option of using OFDM on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, also commonly referred to as tones, bins, etc. Each subcarrier can be modulated with data. Generally, modulation symbols are sent using OFDM in the frequency domain and SC-FDM in the time domain. The spacing between adjacent subcarriers may be fixed, and the total number of subcarriers (K) may depend on the system bandwidth. For example, the subcarrier spacing may be 15 kilohertz (kHz), and the minimum resource allocation (resource block) may be 12 subcarriers (i.e., 180 kHz). Thus, the nominal Fast Fourier Transform (FFT) size can be equal to 128, 256, 512, 1024, or 2048 for system bandwidths of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), respectively. The system bandwidth can also be divided into subbands. For example, a subband may cover 1.08 MHz (i.e., 6 resource blocks), and there can be 1, 2, 4, 8, or 16 subbands for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, respectively.

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

[0110] In the example of FIG. 5, a numerology of 15 kHz is used. Thus, in the time domain, a 10 ms frame is divided into 10 sub-frames each sized equally at 1 ms, and each sub-frame contains one time slot. In FIG. 5, time is represented horizontally (on the X-axis), with time increasing from left to right, and frequency is represented vertically (on the Y-axis), with frequency increasing (or decreasing) from bottom to top.

[0111] A resource grid may be used to represent time slots, and each time slot may contain one or more time-parallel resource blocks (RBs) (also called physical RBs (PRBs)) in the frequency domain. The resource grid is further divided into a plurality of resource elements (REs). An RE may correspond to one symbol length in the time domain and one sub-carrier in the frequency domain. In the numerology of FIG. 5, for a normal cyclic prefix, an RB may contain 12 consecutive sub-carriers in the frequency domain and 7 consecutive symbols in the time domain to obtain a total of 84 REs. For an extended cyclic prefix, an RB may contain 12 consecutive sub-carriers in the frequency domain and 6 consecutive symbols in the time domain to obtain a total of 72 REs. The number of bits carried by each RE depends on the modulation scheme.

[0112] Some of the REs may carry a reference signal (RS). The reference signal may be a positioning reference signal (PRS), a tracking reference signal (TRS), a phase tracking reference signal (PTRS), a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS), a demodulation reference signal (DMRS), a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a synchronization signal block (SSBs), a sounding reference signal (SRS), etc., depending on whether the shown frame structure is used for uplink communication or for downlink communication. FIG. 5 shows an exemplary location of the REs that carry the reference signal (labeled "R").

[0113] The set of resource elements (REs) used for the transmission of the PRS is called a "PRS resource". The set of resource elements can span multiple PRBs in the frequency domain and (one or more, etc.) "N" consecutive symbols within a slot in the time domain. In a given OFDM symbol in the time domain, the PRS resource occupies consecutive PRBs in the frequency domain.

[0114] The transmission of PRS resources within a given PRB has a specific comb size (also referred to as "comb density"). The comb size "N" represents the sub-carrier spacing (or frequency / tone spacing) within each symbol of the PRS resource configuration. Specifically, for a comb size of "N", the PRS is transmitted on every Nth sub-carrier of the PRB symbol. For example, in the case of comb 4, for each symbol of the PRS resource configuration, the REs corresponding to every 4th sub-carrier (such as sub-carriers 0, 4, 8, etc.) are used to transmit the PRS of the PRS resource. Currently, comb sizes of comb 2, comb 4, comb 6, and comb 12 are supported for DL-PRS. FIG. 5 shows an exemplary PRS resource configuration for comb 4 (spanning 4 symbols). That is, the location of the shaded REs (labeled as "R") indicates the comb 4 PRS resource configuration.

[0115] Currently, the DL-PRS resource can span 2, 4, 6, or 12 consecutive symbols within a slot with an interleaved pattern across the entire frequency domain. The DL-PRS resource can be configured within any downlink symbol or flexible (FL) symbol configured by the upper layer of the slot. For all REs of a given DL-PRS resource, there can be a constant energy per resource element (EPRE). The following are the frequency offsets from symbol to symbol for comb sizes 2, 4, 6, and 12 spanning 2, 4, 6, and 12 symbols: 2-symbol comb 2: {0,1}, 4-symbol comb 2: {0,1,0,1}, 6-symbol comb 2: {0,1,0,1,0,1}, 12-symbol comb 2: {0,1,0,1,0,1,0,1,0,1,0,1}, (in the case of the example in FIG. 5), 4-symbol comb 4: {0,2,1,3}, 12-symbol comb 4: {0,2,1,3,0,2,1,3,0,2,1,3}, 6-symbol comb 6: {0,3,1,4,2,5}, 12-symbol comb 6: {0,3,1,4,2,5,0,3,1,4,2,5}, and 12-symbol comb 12: {0,6,3,9,1,7,4,10,2,8,5,11}.

[0116] A "PRS resource set" is a set of PRS resources used for the transmission of PRS signals, where each PRS resource has a PRS resource ID. In addition, the PRS resources in a PRS resource set are associated with the same TRP. A PRS resource set is identified by a PRS resource set ID and is associated with a specific TRP (identified by a TRP ID). In addition, the PRS resources in a PRS resource set have the same periodicity, common muting pattern configuration, and the same repetition factor (such as "PRS-ResourceRepetitionFactor") across slots. Periodicity is the time from the first repetition of the first PRS resource of the first PRS instance to the first repetition of the same first PRS resource of the next PRS instance. The periodicity is μ = 0, 1, 2, 3, and 2^μ * {4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 160, 320, 640, 1280, 2560, 5120, 10240} slots and may have a length selected from. The repetition factor may have a length selected from {1, 2, 4, 6, 8, 16, 32} slots.

[0117] The PRS resource ID in a PRS resource set is associated with a single beam (or beam ID) transmitted from a single TRP (where the TRP can transmit one or more beams). That is, each PRS resource in a PRS resource set may be transmitted on a different beam, and thus may also be referred to as a "PRS resource" or simply a "resource", or a "beam". It should be noted that this has no meaning regarding whether the TRP and beam on which the PRS is transmitted are known to the UE.

[0118] A "PRS instance" or "PRS occasion" is one instance of a periodically repeating time window (such as a group of one or more consecutive slots) that PRS is expected to be transmitted in. A PRS occasion may also be referred to as a "PRS positioning occasion", "PRS positioning instance", "positioning occasion", "positioning instance", "positioning repetition", or simply an "occasion", "instance", or "repetition".

[0119] A "positioning frequency layer" (also simply referred to as a "frequency layer") is a set of one or more PRS resource sets across one or more TRPs that have the same value for a particular parameter. Specifically, the set of PRS resource sets has the same subcarrier spacing and cyclic prefix (CP) type (meaning that all numerologies supported for the physical downlink shared channel (PDSCH) are also supported for PRS), the same Point A, the same value of downlink PRS bandwidth, the same starting PRB (and center frequency), and the same comb size. The Point A parameter takes the value of the parameter "ARFCN-ValueNR" (where "ARFCN" represents "absolute radio-frequency channel number") and is an identifier / code that specifies a pair of physical radio channels used for transmission and reception. The downlink PRS bandwidth may have a granularity of 4 PRB, with a minimum of 24 PRB and a maximum of 272 PRB. Currently, a maximum of four frequency layers are defined, and a maximum of two PRS resource sets per TRP can be configured per frequency layer.

[0120] The concept of a frequency layer is somewhat similar to the concepts of component carriers and bandwidth parts (BWPs), but component carriers and BWPs are used by a single base station (or a macro cell base station and a small cell base station) to transmit data channels, while a frequency layer is used by several (usually three or more) base stations to transmit PRS. A UE may indicate the number of frequency layers it can support, such as during an LTE positioning protocol (LPP) session when the UE transmits its positioning capabilities to the network. For example, the UE may indicate whether it can support one positioning frequency layer or four positioning frequency layers.

[0121] Note that the terms "positioning reference signal" and "PRS" generally refer to specific reference signals used for positioning in NR and LTE systems. However, as used herein, the terms "positioning reference signal" and "PRS" can also refer to any type of reference signal that can be used for positioning, such as PRS defined in LTE and NR, TRS, PTRS, CRS, CSI-RS, DMRS, PSS, SSS, SSB, SRS, UL-PRS, etc., but not limited thereto. Further, the terms "positioning reference signal" and "PRS" can refer to downlink, uplink, or side-link positioning reference signals, unless otherwise indicated by the context. If necessary to further distinguish the type of PRS, a downlink positioning reference signal may be referred to as "DL-PRS", an uplink positioning reference signal (e.g., SRS for positioning, PTRS) may be referred to as "UL-PRS", and a side-link positioning reference signal may be referred to as "SL-PRS". In addition, for signals that can be transmitted in the downlink, uplink, and / or side-link (e.g., DMRS), "DL", "UL", or "SL" may be prepended to the signal to distinguish the direction. For example, "UL-DMRS" is different from "DL-DMRS".

[0122] In one aspect, the reference signal carried on the RE labeled "R" in FIG. 5 can be the SRS. The SRS transmitted by the UE can be used by the base station to obtain channel state information (CSI) for the transmitting UE. CSI represents how the RF signal propagates from the UE to the base station and represents the combined effects of scattering, fading, and power attenuation associated with distance. The system uses SRS for resource scheduling, link adaptation, massive MIMO, beam management, etc.

[0123] The set of REs used for SRS transmission is called the "SRS resource" and can be identified by the parameter "SRS-ResourceId". The set of resource elements can span multiple PRBs in the frequency domain and "N" (e.g., one or more) consecutive symbols within a slot in the time domain. Within a given OFDM symbol, the SRS resource occupies one or more consecutive PRBs. An "SRS resource set" is a set of SRS resources used for SRS signal transmission and is identified by an SRS resource set ID ("SRS-ResourceSetId").

[0124] The transmission of the SRS resource within a given PRB has a specific comb size (also called "comb density"). The comb size "N" represents the subcarrier spacing (or frequency / tone spacing) within each symbol of the SRS resource configuration. Specifically, for the comb size "N", the SRS is transmitted on every Nth subcarrier of the PRB symbol. For example, for a comb of 4, for each symbol of the SRS resource configuration, the REs corresponding to every 4th subcarrier (such as subcarriers 0, 4, 8, etc.) are used to transmit the SRS of the SRS resource. In the example of FIG. 5, the illustrated SRS is a comb of 4 over four symbols. That is, the location of the shaded SRS REs indicates a comb 4 SRS resource configuration.

[0125] Currently, the SRS resource can span 1, 2, 4, 8, or 12 consecutive symbols within a slot with a comb size of comb2, comb4, or comb8. The following are the frequency offsets from symbol to symbol for the currently supported SRS comb patterns. 1-symbol comb2: {0}, 2-symbol comb2: {0,1}, 2-symbol comb4: {0,2}, 4-symbol comb2: {0,1,0,1}, (in the case of the example in Figure 5), 4-symbol comb4: {0,2,1,3}, 8-symbol comb4: {0,2,1,3,0,2,1,3}, 12-symbol comb4: {0,2,1,3,0,2,1,3,0,2,1,3}, 4-symbol comb8: {0,4,2,6}, 8-symbol comb8: {0,4,2,6,1,5,3,7}, and 12-symbol comb8: {0,4,2,6,1,5,3,7,0,4,2,6}.

[0126] Generally, as described above, the UE transmits the SRS to enable the receiving base station (either the serving base station or an adjacent base station) to measure the channel quality (i.e., CSI) between the UE and the base station. However, the SRS can also be specifically configured as an uplink positioning reference signal for uplink-based positioning procedures such as uplink time difference of arrival (UL-TDOA), round trip time (RTT), uplink angle of arrival (UL-AoA), etc. The term "SRS" as used herein may refer to the SRS configured for channel quality measurement or the SRS configured for positioning purposes. When it is necessary to distinguish between the two types of SRS, the former may be referred to herein as "SRS for communication" and / or the latter may be referred to as "SRS for positioning" or "positioning SRS".

[0127] (Except for single symbol / comb 2) Several extensions beyond the previous definition of SRS, such as a new staggered pattern within the SRS resource, a new comb type for SRS, a new sequence for SRS, a larger number of SRS resource sets per component carrier, and a larger number of SRS resources per component carrier, have been proposed for the positioning SRS (also called "UL-PRS"). In addition, the parameters "SpatialRelationInfo" and "PathLossReference" will be configured based on the downlink reference signal or SSB from a neighboring TRP. Furthermore, one SRS resource may be transmitted outside the active BWP, and one SRS resource may span multiple component carriers. Also, the SRS may be configured in the RRC-connected state and may be transmitted only within the active BWP. Additionally, there may be no frequency hopping, no repetition factor, there may be a single antenna port, and there may be new lengths for SRS (e.g., 8 and 12 symbols). Also, open-loop power control may be used instead of closed-loop power control, and comb 8 (i.e., SRS is transmitted for every 8 subcarriers within the same symbol) may be used. Finally, the UE may transmit from multiple SRS resources through the same transmission beam for UL-AoA. All of these are features added to the current SRS framework that are configured (and potentially triggered or activated) through RRC upper layer signaling or through MAC control element (MAC-CE) or downlink control information (DCI).

[0128] As described above, NTN is a network or a segment of a network that uses RF resources mounted on a satellite or an unmanned aircraft system (UAS) platform. According to aspects of the present disclosure, one or more of the satellite and / or UAS platforms can be non-terrestrial transmit and receive points (NT-TRPs) that transmit and / or measure PRS used in positioning determination. Examples of NTN environments that provide access to one or more UEs are shown in FIGS. 6 and 7.

[0129] FIG. 6 shows an exemplary NTN environment 600 according to an aspect of the present disclosure, together with a transparent payload and that can be used in NTN positioning operations. In the case of a transparent payload, the NT-TRP 602 performs RF filtering, frequency conversion, and amplification on the waveform signal received from the gateway 604 via the feeder link 606. Accordingly, the original waveform signal received from the gateway 604 is repeated by the NT-TRP 602 and transmitted to one or more UEs 608 via one or more service links 610. Additionally or alternatively, the NT-TRP 602 can be configured to transmit DL-PRS on one or more DL-PRS resources and / or receive UL-PRS (e.g., SRS) on one or more UL-PRS resources in accordance with its involvement in positioning determination with the UE 608. In certain aspects, the UE 608 can be configured for positioning determination through communication with the NT-TRP 602 via the service link 610, communication with one or more terrestrial network entities (e.g., base stations, location servers, UEs, etc.), or any combination thereof.

[0130] As shown in FIG. 6, NT-TRP602 generates one or more beams across a given service area bounded by the field of view 612 of NT-TRP602. In certain embodiments, the beams are used to transmit DL-PRS from NT-TRP602 to UE608 or to receive UL-PRS transmitted by UE608. Each of the beams typically has a beam footprint 614 with a corresponding elliptical shape. In certain embodiments, the field of view 612 depends on the design of the on-board antennas of NT-TRP602 and the minimum elevation angle of NT-TRP602 (e.g., the minimum angle at which NT-TRP602 can be seen by a UE).

[0131] FIG. 7 shows an exemplary NTN environment 700 that can be used in conjunction with a playback payload and in NTN positioning operations, according to an aspect of the present disclosure. In the case of a playback payload, NT-TRP702 performs not only RF filtering, frequency conversion, and amplification on the payload received before sending the payload to one or more UEs 704 via one or more service links 706, but also demodulation / decoding, switching and / or routing, and encoding / modulation. In certain embodiments, NT-TRP702 communicates directly with gateway 722 via feeder link 708. Additionally or alternatively, NT-TRP702 communicates with another satellite or UAS platform 710 via an inter-satellite link (ISL) 712. In certain embodiments, the satellite or UAS platform 710 can communicate directly with gateway 722 via a further feeder link 714.

[0132] Additionally or alternatively, NT-TRP 702 may be configured to transmit DL-PRS on one or more DL-PRS resources and / or receive UL-PRS (e.g., SRS) on one or more UL-PRS resources in accordance with being involved in positioning determination with UE 704. In certain aspects, UE 704 may be configured for positioning determination through communication with NT-TRP 702 via service link 706, communication with one or more terrestrial network entities (e.g., base stations, location servers, UEs, etc.), or any combination thereof.

[0133] As shown in FIG. 7, NT-TRP 702 generates one or more beams over a given service area bounded by the field of view 716 of NT-TRP 702. The beams may be used to transmit DL-PRS from NT-TRP 702 to UE 704 or to receive UL-PRS transmitted by UE 704. Each of the beams typically has a beam footprint 718 having a corresponding elliptical shape. In certain aspects, the field of view 716 depends on the design of the on-board antennas of NT-TRP 702 and the minimum elevation angle of NT-TRP 702 (e.g., the minimum angle at which NT-TRP 702 can be seen by a UE).

[0134] In an exemplary NTN environment, the beam footprint may move over the Earth as the corresponding NT-TRP moves over the Earth (e.g., as the corresponding NT-TRP orbits the Earth). Alternatively, the beam footprint may remain stationary within a service area located at a fixed position on the Earth. In the latter case, the NT-TRP may implement a beam pointing mechanism (e.g., mechanical or electronic steering features) to compensate for the movement of the NT-TRP.

[0135] FIG. 8 is a table 800 showing an example of a satellite platform that can be used as an NT-TRP. Table 800 provides the name of each platform, the altitude range associated with each platform, the orbit associated with each platform, and the typical beam footprint size of each platform.

[0136] The NTN positioning method can be used alone or in combination with other positioning methods to determine the position of a UE. In certain cases, the NTN positioning method can be used to verify positioning determinations made using other positioning methods. In this regard, a network operator may sometimes need to cross-check the location reported by a UE to meet regulatory requirements (e.g., lawful interception, emergency calls, public warning systems, etc.). In such cases, the location reported by a UE using one positioning method can be cross-checked with the location of the UE determined using the NTN positioning method.

[0137] FIG. 9 shows an exemplary scenario 900 in which a positioning determination based on a global navigation satellite system (GNSS) positioning method is cross-checked with a positioning determination based on the NTN positioning method, according to an aspect of the present disclosure. In this example, a network entity 902 is involved in a positioning operation with a UE 904 to determine the position of the UE 904. For this purpose, the UE 904 is involved in the GNSS positioning method and reports, in a GNSS report 906, the location of the UE 904 based on the GNSS positioning method to the network entity 902. A further determination of the position of the UE 904 is made based on the exchange of NTN positioning information associated with the execution of the NTN positioning method. The network entity 902 can use the result of the NTN positioning operation to improve and / or verify the location of the UE 904 reported in the GNSS report 906. The UE 904 is assumed to have both GNSS location capabilities and NTN positioning capabilities to perform the positioning operations shown in FIG. 9.

[0138] For an entity involved in the positioning operation where the entity measures PRS, typically, a time-based search window is configured that indicates the time when it can be expected that the entity receives PRS from the reference TRP or an adjacent TRP. During a positioning session in which the UE is designated as the target device for measuring PRS, the UE is configured by a location server (e.g., LMF) with a time-based search window within which the UE searches for PRS. The time-based search window configuration can be sent to the UE as positioning assistance data (AD) in an LPP message.

[0139] FIG. 10 shows an example of a time-based PRS search window according to an aspect of the present disclosure. In this example, it can be assumed that the start of the subframe for the PRS of the TRP is received within a time-based search window ranging from -(nr-DL-PRS-ExpectedRSTD - uncertainty × R) to +(nr-DL-PRS-ExpectedRSTD - uncertainty × R), centered around ((T_REF + N milliseconds) + (expected RSTD time corresponding to nr-DL-PRS-ExpectedRSTD × 4Ts), where T_REF is the reception time of the start of the subframe for the PRS of the reference TRP of the assistance data at the target device antenna connector, and N can be calculated based on the information of the nr-DL-PRS-SFN0-Offset information element (IE), dl-PRS-Periodicity-and-ResourceSetSlotOffset IE, and dl-PRS-ResourceSlotOffset IE. When all PRS resources are in FR2, the value of the resolution R is equal to Ts. Otherwise, the resolution R is equal to 4Ts, and Ts = 1 / (15000 * 2048) seconds.

[0140] Figure 11 shows an exemplary procedure 1100 for exchanging information between a base station 1102 (e.g., an NG-RAN node) and a location server 1104 (e.g., an LMF) in a UL-PRS (e.g., SRS) positioning procedure according to an aspect of the present disclosure. In this example, the location server 1104 starts the procedure by sending a measurement request message 1106 to the base station 1102 that indicates the TRPs for which PRS measurement values are requested in a TRP measurement request list IE. The base station 1102 uses the information included in the measurement request message to configure PRS resource measurements for the indicated TRPs. If at least one of the requested measurements is successfully measured by the base station 1102 for at least one of the TRPs, the base station 1102 responds with a measurement response message 1108 that includes the PRS measurement values of the successfully measured TRPs within a TRP measurement response list IE.

[0141] SRS can be used in uplink positioning determination. For this purpose, SRS is designed to cover the entire bandwidth of resource elements spread over different symbols so as to cover all subcarriers. Similar to PRS, SRS is also designed in a comb-based pattern. Thus, UEs can be multiplexed on the same transmission symbol by assigning different comb patterns.

[0142] The exchange of SRS configuration parameters between the base station 1102 and the location server 1104 is performed using the NR positioning protocol A (NRPPa). The configuration information includes parameters used by the base station 1102 to set a time-based search window that can be expected for the base station 1102 to receive SRS from the UE indicated in the TRP measurement request list IE. Figure 12 shows an example of an IE used to determine the parameters of such a time-based search window according to an aspect of the present disclosure.

[0143] The problem that arises with the use of NT-TRP for positioning is that there is a significant Doppler shift (and thus a frequency offset) in the signal transmitted by NT-TRP, especially when NT-TRP is a satellite orbiting the Earth. Table 1 provides an overview of the Doppler shift and shift variations for different altitudes of such satellites.

[0144]

Table 1

[0145] FIG. 13 is a diagram 1300 showing the system geometry for Doppler shift calculation for a non-geostationary satellite system according to an aspect of the present disclosure. The scenario shown in FIG. 13 assumes a Cartesian coordinate system in which a mobile satellite and a receiver (e.g., a UE, a terrestrial base station) are in the y-z plane. The Doppler shift experienced by a stationary receiver can be calculated as a function of time as follows.

[0146]

Equation

[0147]

Equation

[0148] After some mathematical operations, the Doppler shift as a function of the elevation angle can be calculated in a closed-form equation as follows.

[0149]

Equation

[0150]

Number

[0151] When a receiver (e.g., a UE) is mounted on an aircraft or a high-speed train, there will be an additional term of Doppler shift caused by its own speed. In the case of a non-geostationary satellite, the Doppler shift due to the movement of the satellite is much larger than the Doppler shift caused by the movement of the receiver. However, in the case of a geostationary earth orbiting (GEO) satellite and a high-altitude platform station (HAPS), the Doppler shift component is mainly caused by the movement of the receiver.

[0152] FIG. 14 is a graph 1400 showing an exemplary Doppler shift scenario having a 2 GHz signal at 600 km on the downlink and uplink according to an aspect of the present disclosure. Graph 1400 shows plots for both a fixed UE and a moving UE (both moving in the same direction as the satellite and in the opposite direction of the satellite).

[0153] FIG. 15 is a graph 1500 showing an exemplary Doppler shift scenario having a 2 GHz signal at 1500 km on the downlink and uplink according to an aspect of the present disclosure. Graph 1500 shows plots for both a fixed UE and a moving UE (both moving in the same direction as the satellite and in the opposite direction of the satellite).

[0154] Graphs 1400 and 1500 show the worst-case impact of a UE moving at 1000 km / h in the same direction as a satellite (which is a non-geostationary satellite). The boundaries of the graphs can be defined by adding the Doppler shift due to the movement of the satellite and the Doppler shift due to the movement of the UE. Graphs 1400 and 1500 clearly show the boundaries of the Doppler shift that depend on the sense of movement between the satellite and the UE.

[0155] The arrival time of the PRS (e.g., DL-PRS, UL-PRS, SRS) is determined at the receiving entity through the time correlation between the received PRS and a locally generated copy of the PRS. FIG. 16 shows an example of such an autocorrelation response for the PRS received under different Doppler shift conditions. Graph 1602 shows that a clearly defined time correlation peak 1604 can be obtained under 0 Doppler conditions. However, as shown in graph 1606, the peak detection of the same PRS becomes ambiguous under high Doppler shift conditions due to the appearance of side lobes 1608 and 1610. Such ambiguity is particularly problematic under the high Doppler shift conditions associated with the NT-TRP used in NTN positioning.

[0156] To address the ambiguity that occurs with PRS detection under such high Doppler shift conditions, certain aspects of the present disclosure are directed to the use of a frequency domain search window for PRS detection. The network entity can limit its PRS detection to the PRS occurring within a frequency range determined from the frequency domain search window. Thus, the peak of the PRS received under high Doppler shift conditions can be detected without the corresponding peak detection ambiguity typically associated with such high Doppler shift conditions. According to an aspect of the present disclosure, the frequency domain search window can be used together with a time-based search window to provide a two-dimensional search window for PRS detection.

[0157] Some aspects of the present disclosure are directed to wireless communications performed by a network entity, where a frequency domain search window is determined for at least one PRS resource associated with at least one NT-TRP for use during an NTN positioning session. In certain aspects, the frequency domain search window is adapted to the predicted Doppler frequency shift offset and the predicted Doppler frequency shift offset uncertainty. In certain aspects, values for the predicted Doppler frequency shift offset and the predicted Doppler frequency shift offset uncertainty are provided to the network entity in a positioning AD from a location server (e.g., LMF). In certain aspects, values for the predicted Doppler frequency shift offset and the predicted Doppler frequency shift offset uncertainty are determined by the network entity based on ephemeris information associated with the NT-TRP. The ephemeris information may be pre-programmed in the network entity, received from another network entity (e.g., UE, location server, NT-TRP, etc.), or any combination thereof. In one aspect, the PRS resource is measured within the frequency domain search window during the positioning session.

[0158] According to certain aspects of the present disclosure, the PRS may be resampled based on the predicted Doppler frequency shift offset. Multiple hypotheses for detecting a peak of at least one PRS within the frequency domain search window may be constructed based on the resampling of the at least one PRS.

[0159] Depending on the orbit of the NT-TRP, different frequency ranges and resolutions can be used for the predicted Doppler frequency shift offset and the predicted Doppler frequency shift offset uncertainty. According to certain aspects of the present disclosure, the NT-TRP is an earth orbiting satellite having a low earth orbit (LEO), a medium earth orbit (MEO), or a geostationary orbit (GEO). The predicted Doppler frequency shift offset, the predicted Doppler frequency shift offset uncertainty, or both the predicted Doppler frequency shift offset and the predicted Doppler frequency shift offset uncertainty are based on the orbit of the earth orbiting satellite. In certain aspects, the predicted Doppler frequency shift offset, the predicted Doppler frequency shift offset uncertainty, or both the predicted Doppler frequency shift offset and the predicted Doppler frequency shift offset uncertainty are based on 1) the altitude of at least one NT-TRP, 2) the frequency of the PRS resource, or 3) any combination thereof.

[0160] Other types of vehicles may be used for the NT-TRP. In certain aspects, the NT-TRP can be an unmanned aerial vehicle, a manned aircraft, or a light aircraft.

[0161] The predicted Doppler frequency shift offset and the predicted Doppler frequency shift offset uncertainty can be specified using various units of measurement. In certain aspects, the predicted Doppler frequency shift offset and the predicted Doppler frequency shift offset uncertainty can be specified as absolute frequency values. Additionally, or alternatively, the unit of measurement may be specified as parts per million (ppm). When specified as ppm, the predicted Doppler frequency shift offset and the predicted Doppler frequency shift offset uncertainty can be signaled for each NT-TRP to be measured. From the perspective of the UE, the UE can read the value in ppm units indicated in the DL-PRS assistance data and use that value to calculate the band-specific search window in units of frequency (e.g., hertz (Hz), kilohertz (kHz), megahertz (MHz), gigahertz (GHz), etc.). From the perspective of the base station (e.g., NG-RAN), the base station can read the value in ppm units indicated in the SRS measurement request and calculate the band-specific search window in units of frequency. In one aspect, the predicted Doppler frequency shift offset uncertainty is indicated as a parts per million (PPM) value relative to the predicted Doppler frequency shift offset by the positioning AD.

[0162] Additionally, or alternatively, the predicted Doppler frequency shift offset and the predicted Doppler frequency shift offset uncertainty can be specified as units of direction (e.g., azimuth and elevation angles relative to a local coordinate system with respect to the NT-TRP) indicating the position of the NT-TRP relative to the network entity. In one aspect, the reference direction can be specified as the direction of the center of the beam serving the network entity with respect to the NT-TRP and the standard deviation (or uncertainty) of the direction. The network entity can determine the predicted Doppler frequency shift offset from the reference direction and the ephemeris information associated with the NT-TRP. Further, the network can determine the predicted Doppler frequency shift offset uncertainty from the direction uncertainty.

[0163] The predicted Doppler frequency shift offset and the predicted Doppler frequency shift offset uncertainty can be used to form various configurations of the frequency domain search window. FIG. 17 shows an example of a configuration for a frequency domain search window using the predicted Doppler frequency shift offset and the predicted Doppler frequency shift offset uncertainty, according to an aspect of the present disclosure. In configuration 1702, the frequency domain search window 1704 is a symmetric arrangement of the predicted Doppler frequency shift offset uncertainty 1706 centered on the predicted Doppler frequency shift offset 1708. In configuration 1710, the frequency domain search window 1712 is an asymmetric arrangement of the predicted Doppler frequency shift offset uncertainty 1706 centered on the predicted Doppler frequency shift offset 1708, and the lower end of the frequency domain search window 1712 is offset by an amount Δf from the predicted frequency shift offset 1708. Similarly, in configuration 1714, the frequency domain search window 1716 is an asymmetric arrangement of the predicted Doppler frequency shift offset uncertainty 1706 centered on the predicted Doppler frequency shift offset 1708, and the upper end of the frequency domain search window 1716 is offset by the amount Δf from the predicted frequency shift offset 1708. In configuration 1718, the lower end of the frequency domain search window 1720 is adjacent to and includes the predicted Doppler frequency shift offset 1708. In configuration 1722, the upper end of the frequency domain search window 1724 is adjacent to and includes the predicted Doppler frequency shift offset 1708.

[0164] Certain aspects of the present disclosure consider a second aspect of Doppler shift conditions. Such a second aspect includes how the Doppler shift conditions change over time. For example, the predicted Doppler frequency offset value may drift over the duration of a positioning session. In certain aspects, the predicted Doppler frequency offset drift and / or the predicted Doppler frequency offset drift rate are determined from an indication in a positioning AD (e.g., in the case of a UE) or a measurement request message (e.g., in the case of a base station). In certain aspects, the predicted Doppler frequency shift drift and the predicted Doppler frequency shift drift rate may be used as parameters for dynamically shifting the position of a frequency domain search window in the frequency domain during a positioning session and / or for determining a new value of the predicted Doppler frequency shift during a subsequent positioning session.

[0165] In certain aspects, a network entity may determine an effective duration corresponding to a duration for which a frequency domain search window is valid. The effective duration may correspond to a maximum time for which the network entity can propagate the predicted Doppler frequency shift offset without significantly deviating from the current value of the predicted Doppler frequency shift offset. The effective duration may be indicated by 1) the positioning AD received by the network entity, 2) determined by the network entity from ephemeris information corresponding to at least one NT-TRP, or 3) any combination thereof. In certain aspects, the network entity may 1) send a request to obtain a new positioning AD based on expiration of the effective duration, 2) send an error message indicating a positioning error cause corresponding to expiration of the effective duration, or 3) perform any combination thereof. In certain aspects, the request to obtain a new positioning AD may include a request to obtain new values for the predicted Doppler frequency offset and / or the predicted Doppler frequency offset uncertainty. In certain aspects, the positioning error cause may be indicated by the ExpectedFrequencyOffsetValidityExpired parameter within the TargetDeviceErrorCausesIE.

[0166] FIG. 18 shows an exemplary method 1800 of wireless communication implemented by a network node according to an aspect of the present disclosure. In operation 1802, a network entity may determine a frequency domain search window corresponding to an expected Doppler frequency shift offset and an expected Doppler frequency shift offset uncertainty for at least one positioning reference signal (PRS) resource associated with at least one non-terrestrial transmit-receive point (NT-TRP) for a positioning session. In one aspect, operation 1802 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or positioning component 342, any or all of which may be considered means for performing this operation. In one aspect, operation 1802 may be performed by one or more WWAN transceivers 350, one or more processors 384, memory 386, and / or positioning component 388, any or all of which may be considered means for performing this operation.

[0167] In operation 1804, the network entity may measure at least one PRS resource within the frequency domain search window during a positioning session. In one aspect, operation 1804 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or positioning component 342, any or all of which may be considered means for performing this operation.

[0168] As will be appreciated, a technical advantage of method 1800 is the addition of a frequency domain search window for performing NTN positioning operations under high Doppler frequency shift conditions. By using the frequency domain search window, the ambiguity associated with detecting the peak of the PRS received under such conditions is minimized, thereby improving the accuracy of NTN positioning determinations.

[0169] FIG. 19 shows an exemplary method 1900 of wireless communication implemented by a first side link device according to an aspect of the present disclosure. In operation 1902, a first network entity sends information to a second network entity for determining a frequency domain search window corresponding to an expected Doppler frequency shift offset and an expected Doppler frequency shift offset uncertainty for at least one positioning reference signal (PRS) resource associated with at least one non-terrestrial transmit-receive point (NT-TRP) measured by the second network entity during a positioning session. In one aspect, operation 1902 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or positioning component 342, any or all of which may be regarded as means for performing this operation. In one aspect, operation 1902 may be performed by one or more WWAN transceivers 350, one or more processors 384, memory 386, and / or positioning component 388, any or all of which may be regarded as means for performing this operation. In one aspect, operation 1902 may be performed by one or more network transceivers 390, one or more processors 394, memory 396, and / or positioning component 398, any or all of which may be regarded as means for performing this operation.

[0170] In operation 1904, a first network entity receives a measurement report from a second network entity that includes information corresponding to one or more measurements made on at least one PRS resource. In one aspect, operation 1904 may be performed by one or more WWAN transceivers 310, one or more processors 332, memory 340, and / or positioning component 342, any or all of which may be regarded as means for performing this operation. In one aspect, operation 1904 may be performed by one or more WWAN transceivers 350, one or more processors 384, memory 386, and / or positioning component 388, any or all of which may be regarded as means for performing this operation. In one aspect, operation 1904 may be performed by one or more network transceivers 390, one or more processors 394, memory 396, and / or positioning component 398, any or all of which may be regarded as means for performing this operation.

[0171] As will be appreciated, a technical advantage of method 1900 is the addition of a frequency domain search window for performing NTN positioning operations under high Doppler frequency shift conditions. By using the frequency domain search window, the ambiguity associated with detecting the peak of the PRS received under such conditions is minimized, thereby improving the accuracy of NTN positioning determinations.

[0172] In the form for carrying out the above invention, it can be seen in the example that different features are grouped together. This way of disclosure should not be understood as meaning that the exemplary clauses have more features than are explicitly stated in each clause. Rather, various aspects of the present disclosure may include fewer features than all the features of the individual exemplary clauses disclosed. Therefore, the following clauses should be considered to be incorporated into the description, and each clause can be valid separately as a distinct example. Each dependent clause may refer in that clause to a specific combination with one of the other clauses, but the aspect of that dependent clause is not limited to that specific combination. It will be understood that other exemplary clauses may also include a combination of aspects of dependent clauses with the subject matter of any other dependent or independent clause, or any combination of features with other dependent and independent clauses. Various aspects disclosed herein do not explicitly include these combinations unless it is explicitly stated or can be easily inferred that a particular combination (such as defining an element as both an electrical insulator and an electrical conductor, etc., conflicting aspects) is not intended. Further, even if a clause is not directly dependent on an independent clause, it is also intended that the aspect of the clause can be included in any other independent clause.

[0173] In the following numbered clauses, implementation examples are described.

[0174] Clause 1. A method of wireless communication implemented by a network entity, comprising determining an expected Doppler frequency shift offset and a frequency domain search window corresponding to the expected Doppler frequency shift uncertainty for at least one positioning reference signal (PRS) resource associated with at least one non-terrestrial transmit-receive point (NT-TRP) for a positioning session, and measuring at least one PRS resource within the frequency domain search window during the positioning session.

[0175] Clause 2. The method according to Clause 1, further comprising resampling at least one PRS resource based on a predicted Doppler frequency shift offset in order to detect a peak of at least one PRS resource within a frequency domain search window.

[0176] Clause 3. The method according to Clause 2, further comprising constructing a plurality of hypotheses in order to detect a peak of at least one PRS within a frequency domain search window based on resampling at least one PRS resource.

[0177] Clause 4. The method according to any one of Clauses 1 to 3, further comprising transmitting a measurement report including information corresponding to one or more measurements made on at least one PRS resource.

[0178] Clause 5. The frequency domain search window is determined as a symmetric arrangement of predicted Doppler frequency shift offset uncertainty centered on the predicted Doppler frequency shift offset, an asymmetric arrangement of predicted Doppler frequency shift offset uncertainty centered on the predicted Doppler frequency shift offset, an arrangement of predicted Doppler frequency shift offset uncertainty where the minimum offset of the predicted Doppler frequency shift offset uncertainty is adjacent to the predicted Doppler frequency shift offset, or an arrangement of predicted Doppler frequency shift offset uncertainty where the maximum offset of the predicted Doppler frequency shift offset uncertainty is adjacent to the predicted Doppler frequency shift offset, according to the method described in any one of Clauses 1 to 4.

[0179] Clause 6. Determining the frequency domain search window includes receiving positioning assistance data (AD) indicating values for the predicted Doppler frequency shift offset and the predicted Doppler frequency shift offset uncertainty, receiving ephemeris information associated with at least one NT-TRP to determine the predicted Doppler frequency shift offset and the predicted Doppler frequency shift offset uncertainty, or any combination thereof, according to the method described in any one of Clauses 1 to 5.

[0180] Clause 7. The method according to clause 6 further includes receiving ephemeris information associated with at least one NT-TRP, receiving direction information for at least one NT-TRP, and determining an expected Doppler frequency shift offset and an expected Doppler frequency shift offset uncertainty based on the direction information and the ephemeris information.

[0181] Clause 8. The method according to clause 6 or 7, wherein the expected Doppler frequency shift offset uncertainty is indicated by the positioning AD as a parts per million (ppm) value with respect to the expected Doppler frequency shift offset.

[0182] Clause 9. The method according to any one of clauses 1 to 8 further includes determining an expected Doppler frequency offset drift corresponding to an expected Doppler frequency drift of the expected Doppler frequency shift offset during a positioning session, determining an expected Doppler frequency offset drift rate corresponding to an expected Doppler frequency drift rate of the expected Doppler frequency shift offset during a positioning session, or any combination thereof.

[0183] Clause 10. The method according to clause 9, wherein the expected Doppler frequency offset drift is determined from an indication in the positioning AD, the expected Doppler frequency offset drift rate is determined from an indication in the positioning AD, or any combination thereof.

[0184] Clause 11. The method according to any one of clauses 1 to 10 further includes determining an effective duration corresponding to a duration for which a frequency domain search window is valid, and the effective duration is indicated by the positioning AD received by the network entity, the effective duration is determined by the network entity from ephemeris information corresponding to at least one NT-TRP, or any combination thereof.

[0185] Clause 12. The method according to Clause 11, further comprising sending a request for obtaining a new positioning AD based on the expiration of the effective duration, sending an error message indicating the cause of the positioning error corresponding to the expiration of the effective duration, or any combination thereof.

[0186] Clause 13. At least one NT-TRP is an earth-orbiting satellite having a low Earth orbit (LEO), a medium Earth orbit (MEO), or a geostationary orbit (GEO), and the predicted Doppler frequency shift offset, the predicted Doppler frequency shift offset uncertainty, or both the predicted Doppler frequency shift offset and the predicted Doppler frequency shift offset uncertainty are based on the orbit of the earth-orbiting satellite, the method according to any of Clauses 1 to 12.

[0187] Clause 14. At least one NT-TRP is an unmanned aircraft, a manned aircraft, or a light aircraft, the method according to any of Clauses 1 to 12.

[0188] Clause 15. The predicted Doppler frequency shift offset, the predicted Doppler frequency shift offset uncertainty, or both the predicted Doppler frequency shift offset and the predicted Doppler frequency shift offset uncertainty are based on the altitude of at least one NT-TRP, the frequency of at least one PRS resource, or any combination thereof, the method according to any of Clauses 1 to 14.

[0189] Clause 16. The method according to any of Clauses 1 to 15, further comprising receiving a positioning AD indicating a time search window corresponding to the predicted time and the predicted time uncertainty for receiving at least one PRS resource.

[0190] Clause 17. Measuring one or more signals of a Global Navigation Satellite System (GNSS), wherein measuring at least one PRS resource within a frequency domain search window is measuring that is temporally close to measuring one or more signals of the GNSS, and reporting measurement data associated with the measurement of one or more signals of the GNSS and the measurement of at least one PRS resource, the method according to any one of Clauses 1 to 16 further comprising.

[0191] Clause 18. The network entity is a base station, and determining a frequency domain search window includes receiving a positioning AD indicating values for an expected Doppler frequency shift offset and an expected Doppler frequency shift offset uncertainty, and at least one PRS resource is an uplink PRS (UL-PRS) resource, the method according to any one of Clauses 1 to 17.

[0192] Clause 19. A method of wireless communication performed by a first network entity, comprising sending to a second network entity information for determining a frequency domain search window corresponding to an expected Doppler frequency shift offset and an expected Doppler frequency shift offset uncertainty for at least one positioning reference signal (PRS) resource associated with at least one non-terrestrial transmit-receive point (NT-TRP) measured by the second network entity during a positioning session, and receiving from the second network entity a measurement report including information corresponding to one or more measurements made of at least one PRS resource.

[0193] Clause 20. The frequency domain search window is based on the symmetric arrangement of the predicted Doppler frequency shift offset uncertainty centered on the predicted Doppler frequency shift offset, the asymmetric arrangement of the predicted Doppler frequency shift offset uncertainty centered on the predicted Doppler frequency shift offset, the arrangement of the predicted Doppler frequency shift offset uncertainty where the minimum offset of the predicted Doppler frequency shift offset uncertainty is adjacent to the predicted Doppler frequency shift offset, or the arrangement of the predicted Doppler frequency shift offset uncertainty where the maximum offset of the predicted Doppler frequency shift offset uncertainty is adjacent to the predicted Doppler frequency shift offset, and is the method according to Clause 19.

[0194] Clause 21. Sending information to a second network entity includes sending positioning assistance data (AD) indicating values for the predicted Doppler frequency shift offset and the predicted Doppler frequency shift offset uncertainty, sending ephemeris information associated with at least one NT-TRP for the second network entity to determine the predicted Doppler frequency shift offset and the predicted Doppler frequency shift offset uncertainty, sending direction information associated with at least one NT-TRP for the second network entity to determine the predicted Doppler frequency shift offset and the predicted Doppler frequency shift offset uncertainty, or any combination thereof, and is the method according to Clause 19 or 20.

[0195] Clause 22. The positioning AD sent to the second network entity indicates the predicted Doppler frequency shift offset uncertainty as parts per million (ppm) value with respect to the predicted Doppler frequency shift offset, and is the method according to Clause 21.

[0196] Clause 23. Sending information to a second network entity includes sending a positioning AD that indicates a positioning AD corresponding to a predicted Doppler frequency offset drift corresponding to a predicted Doppler frequency drift of a predicted Doppler frequency shift offset during a positioning session, a predicted Doppler frequency offset drift rate corresponding to a predicted Doppler frequency drift rate of the predicted Doppler frequency shift offset during the positioning session, or any combination thereof, as described in any of Clauses 19 to 22.

[0197] Clause 24. Sending information to a second network entity further includes sending a positioning AD indicating an effective duration corresponding to the duration for which the information for determining the frequency domain search window is valid, as described in any of Clauses 19 to 23.

[0198] Clause 25. The method according to Clause 24 further includes receiving a request to obtain a new positioning AD based on the expiration of the effective duration, receiving an error message indicating a positioning error cause corresponding to the expiration of the effective duration, or any combination thereof.

[0199] Clause 26. At least one NT-TRP is an earth orbiting satellite having a low earth orbit (LEO), a medium earth orbit (MEO), or a geostationary orbit (GEO), and the predicted Doppler frequency shift offset, the predicted Doppler frequency shift offset uncertainty, or both the predicted Doppler frequency shift offset and the predicted Doppler frequency shift offset uncertainty are based on the orbit of the earth orbiting satellite, as described in any of Clauses 19 to 25.

[0200] Clause 27. At least one NT-TRP includes an unmanned aircraft, a manned aircraft, or a light aircraft, as described in any of Clauses 19 to 25.

[0201] Clause 28. The method according to any of Clauses 19 to 27, wherein the predicted Doppler frequency shift offset is based on the altitude of at least one NT-TRP, the frequency of at least one PRS resource, or any combination thereof.

[0202] Clause 29. The method according to any of Clauses 19 to 28, further comprising receiving a positioning AD indicating a time search window corresponding to the predicted time and predicted time uncertainty for receiving at least one PRS resource.

[0203] Clause 30. A network entity comprising a memory, at least one transceiver, and at least one processor communicatively coupled to the memory and the at least one transceiver, wherein the at least one processor determines a frequency domain search window corresponding to a predicted Doppler frequency shift offset and a predicted Doppler frequency shift offset uncertainty for at least one positioning reference signal (PRS) resource associated with at least one non-terrestrial transceiver point (NT-TRP) for a positioning session, and is configured to measure at least one PRS resource within the frequency domain search window during the positioning session.

[0204] Clause 31. The network entity according to Clause 30, wherein the at least one processor is further configured to resample at least one PRS resource based on the predicted Doppler frequency shift offset to detect a peak of at least one PRS resource within the frequency domain search window.

[0205] Clause 32. The network entity according to Clause 31, wherein the at least one processor is further configured to construct a plurality of hypotheses to detect a peak of at least one PRS within the frequency domain search window based on resampling at least one PRS resource.

[0206] Clause 33. The network entity according to any one of Clauses 30 to 32, wherein at least one processor is further configured to transmit a measurement report including information corresponding to one or more measurements made on at least one PRS resource via at least one transceiver.

[0207] Clause 34. The network entity according to any one of Clauses 30 to 33, wherein the frequency domain search window is based on a symmetric arrangement of predicted Doppler frequency shift offset uncertainty centered on the predicted Doppler frequency shift offset, an asymmetric arrangement of predicted Doppler frequency shift offset uncertainty centered on the predicted Doppler frequency shift offset, an arrangement of predicted Doppler frequency shift offset uncertainty where the minimum offset of the predicted Doppler frequency shift offset uncertainty is adjacent to the predicted Doppler frequency shift offset, or an arrangement of predicted Doppler frequency shift offset uncertainty where the maximum offset of the predicted Doppler frequency shift offset uncertainty is adjacent to the predicted Doppler frequency shift offset.

[0208] Clause 35. The network entity according to any one of Clauses 30 to 34, including at least one processor configured to receive positioning assistance data (AD) indicating values for the predicted Doppler frequency shift offset and the predicted Doppler frequency shift offset uncertainty via at least one transceiver, to receive ephemeris information associated with at least one NT-TRP to determine the predicted Doppler frequency shift offset and the predicted Doppler frequency shift offset uncertainty via at least one transceiver, or to perform any combination thereof.

[0209] Clause 36. The network entity according to Clause 35, wherein ephemeris information associated with at least one NT-TRP is received, and at least one processor is further configured to receive direction information for at least one NT-TRP via at least one transceiver and determine an expected Doppler frequency shift offset and an expected Doppler frequency shift offset uncertainty based on the direction information and the ephemeris information.

[0210] Clause 37. The network entity according to Clause 35 or 36, wherein the expected Doppler frequency shift offset uncertainty is indicated as a parts per million (ppm) value with respect to the expected Doppler frequency shift offset by the positioning AD.

[0211] Clause 38. The network entity according to any one of Clauses 30 to 37, wherein at least one processor is further configured to determine an expected Doppler frequency offset drift corresponding to an expected Doppler frequency drift of the expected Doppler frequency shift offset during a positioning session, or determine an expected Doppler frequency offset drift rate corresponding to an expected Doppler frequency drift rate of the expected Doppler frequency shift offset during a positioning session, or perform any combination thereof.

[0212] Clause 39. The network entity according to Clause 38, wherein the expected Doppler frequency offset drift is determined from an indication in the positioning AD, the expected Doppler frequency offset drift rate is determined from an indication in the positioning AD, or any combination thereof.

[0213] Clause 40. The at least one processor is further configured to determine a valid duration corresponding to a duration for which the frequency domain search window is valid, where the valid duration is indicated by the positioning AD received by the network entity, or the valid duration is determined by the network entity from the ephemeris information corresponding to the at least one NT-TRP, or any combination thereof, of the network entity according to any one of Clauses 30 to 39.

[0214] Clause 41. The at least one processor is further configured to send a request for obtaining a new positioning AD based on the expiration of the valid duration via at least one transceiver, or to send an error message indicating a positioning error cause corresponding to the expiration of the valid duration via at least one transceiver, or any combination thereof, of the network entity according to Clause 40.

[0215] Clause 42. The at least one NT-TRP is an earth orbiting satellite having a low earth orbit (LEO), a medium earth orbit (MEO), or a geostationary earth orbit (GEO), where the predicted Doppler frequency shift offset, the predicted Doppler frequency shift offset uncertainty, or both the predicted Doppler frequency shift offset and the predicted Doppler frequency shift offset uncertainty are based on the orbit of the earth orbiting satellite, of the network entity according to any one of Clauses 30 to 41.

[0216] Clause 43. The at least one NT-TRP is of the network entity according to any one of Clauses 30 to 41, including an unmanned aerial vehicle, a manned aircraft, or a light aircraft.

[0217] Clause 44. The predicted Doppler frequency shift offset, the predicted Doppler frequency shift offset uncertainty, or both the predicted Doppler frequency shift offset and the predicted Doppler frequency shift offset uncertainty are based on the altitude of at least one NT-TRP, the frequency of at least one PRS resource, or any combination thereof, and are the network entities described in any of Clauses 30 to 43.

[0218] Clause 45. The at least one processor is further configured to receive a positioning AD indicating a time search window corresponding to a predicted time and a predicted time uncertainty for receiving at least one PRS resource via at least one transceiver, and is the network entity described in any of Clauses 30 to 44.

[0219] Clause 46. The at least one processor is configured to measure one or more signals of a global navigation satellite system (GNSS), and measuring at least one PRS resource within a frequency domain search window is performed in temporal proximity to measuring one or more signals of the GNSS, and is further configured to receive measurement data associated with the measurement of one or more signals of the GNSS and the measurement of at least one PRS resource via at least one transceiver, and is the network entity described in any of Clauses 30 to 45.

[0220] Clause 47. The network entity is a base station, and determining the frequency domain search window includes receiving a positioning AD indicating values for the predicted Doppler frequency shift offset and the predicted Doppler frequency shift offset uncertainty, and at least one PRS resource is an uplink PRS (UL-PRS) resource, and is the network entity described in any of Clauses 30 to 46.

[0221] Clause 48. The first network entity includes a memory, at least one transceiver, and at least one processor communicatively coupled to the memory and the at least one transceiver. The at least one processor is configured to send, via the at least one transceiver, information for determining a frequency domain search window corresponding to an expected Doppler frequency shift offset and an expected Doppler frequency shift offset uncertainty for at least one positioning reference signal (PRS) resource associated with at least one non-terrestrial transmit-receive point (NT-TRP) measured by a second network entity during a positioning session to the second network entity, and to receive, via the at least one transceiver, a measurement report including information corresponding to one or more measurements performed on the at least one PRS resource by the second network entity. The first network entity as described in Clause 48.

[0222] Clause 49. The first network entity as described in Clause 48, wherein the frequency domain search window is based on a symmetric arrangement of the expected Doppler frequency shift offset uncertainty centered on the expected Doppler frequency shift offset, an asymmetric arrangement of the expected Doppler frequency shift offset uncertainty centered on the expected Doppler frequency shift offset, an arrangement of the expected Doppler frequency shift offset uncertainty where the minimum offset of the expected Doppler frequency shift offset uncertainty is adjacent to the expected Doppler frequency shift offset, or an arrangement of the expected Doppler frequency shift offset uncertainty where the maximum offset of the expected Doppler frequency shift offset uncertainty is adjacent to the expected Doppler frequency shift offset.

[0223] Clause 50. At least one processor configured to send information to a second network entity includes at least one processor configured to send ranging assistance data (AD) indicating values for an expected Doppler frequency shift offset and an expected Doppler frequency shift offset uncertainty via at least one transceiver, or to send ephemeris information associated with at least one NT-TRP via at least one transceiver to determine the expected Doppler frequency shift offset and the expected Doppler frequency shift offset uncertainty, or to send direction information associated with at least one NT-TRP via at least one transceiver to determine the expected Doppler frequency shift offset and the expected Doppler frequency shift offset uncertainty, or to perform any combination thereof, the first network entity according to Clause 48 or 49.

[0224] Clause 51. The ranging AD sent to the second network entity is the first network entity according to Clause 50, indicating the expected Doppler frequency shift offset uncertainty as parts per million (ppm) value for the expected Doppler frequency shift offset.

[0225] Clause 52. At least one processor configured to send information to a second network entity includes at least one processor configured to send ranging AD indicating an expected Doppler frequency offset drift corresponding to an expected Doppler frequency drift of the expected Doppler frequency shift offset during a ranging session, an expected Doppler frequency offset drift rate corresponding to an expected Doppler frequency drift rate of the expected Doppler frequency shift offset during a ranging session, or any combination thereof, the first network entity according to any of Clauses 48 to 51.

[0226] Clause 53. The first network entity according to any of Clauses 48 to 52, including at least one processor configured to send positioning AD indicating an effective duration corresponding to a duration during which information for determining a frequency domain search window is valid, via at least one transceiver.

[0227] Clause 54. The first network entity according to Clause 53, wherein the at least one processor is further configured to receive a request to obtain a new positioning AD based on expiration of the effective duration, via at least one transceiver, or receive an error message indicating a positioning error cause corresponding to expiration of the effective duration, via at least one transceiver, or perform any combination thereof.

[0228] Clause 55. The first network entity according to any of Clauses 48 to 54, wherein the at least one NT-TRP is an earth orbiting satellite having a low earth orbit (LEO), a medium earth orbit (MEO), or a geostationary earth orbit (GEO), and the predicted Doppler frequency shift offset, the predicted Doppler frequency shift offset uncertainty, or both the predicted Doppler frequency shift offset and the predicted Doppler frequency shift offset uncertainty are based on the orbit of the earth orbiting satellite.

[0229] Clause 56. The first network entity according to any of Clauses 48 to 54, wherein the at least one NT-TRP includes an unmanned aerial vehicle, a manned aircraft, or a light aircraft.

[0230] Clause 57. The first network entity according to any of Clauses 48 to 56, wherein the predicted Doppler frequency shift offset is based on the altitude of the at least one NT-TRP, the frequency of the at least one PRS resource, or any combination thereof.

[0231] Clause 58. The at least one processor is further configured to receive a ranging AD indicating a time search window corresponding to an expected time and an expected time uncertainty for receiving at least one PRS resource via at least one transceiver, the first network entity according to any of Clauses 48 to 57.

[0232] Clause 59. A network entity comprising means for determining a frequency domain search window corresponding to an expected Doppler frequency shift offset and an expected Doppler frequency shift offset uncertainty for at least one positioning reference signal (PRS) resource associated with at least one non-terrestrial transceiver point (NT-TRP) for a positioning session, and means for measuring at least one PRS resource within the frequency domain search window during the positioning session.

[0233] Clause 60. The network entity according to Clause 59, further comprising means for resampling at least one PRS resource based on the expected Doppler frequency shift offset to detect a peak of at least one PRS resource within the frequency domain search window.

[0234] Clause 61. The network entity according to Clause 60, further comprising means for constructing a plurality of hypotheses to detect a peak of at least one PRS within the frequency domain search window based on resampling at least one PRS resource.

[0235] Clause 62. The network entity according to any of Clauses 59 to 61, further comprising means for transmitting a measurement report including information corresponding to one or more measurements made on at least one PRS resource.

[0236] Clause 63. The frequency domain search window is determined as a symmetric arrangement of Doppler frequency shift offset uncertainty centered on the predicted Doppler frequency shift offset, an asymmetric arrangement of Doppler frequency shift offset uncertainty centered on the predicted Doppler frequency shift offset, an arrangement of Doppler frequency shift offset uncertainty where the minimum offset of the Doppler frequency shift offset uncertainty is adjacent to the predicted Doppler frequency shift offset, or an arrangement of Doppler frequency shift offset uncertainty where the maximum offset of the Doppler frequency shift offset uncertainty is adjacent to the predicted Doppler frequency shift offset, and is the network entity according to any one of Clauses 59 to 62.

[0237] Clause 64. The means for determining the frequency domain search window includes means for receiving positioning assistance data (AD) indicating values for the predicted Doppler frequency shift offset and the Doppler frequency shift offset uncertainty, means for receiving ephemeris information associated with at least one NT-TRP to determine the predicted Doppler frequency shift offset and the Doppler frequency shift offset uncertainty, or any combination thereof, and is the network entity according to any one of Clauses 59 to 63.

[0238] Clause 65. The ephemeris information associated with at least one NT-TRP is received, and the network entity further includes means for receiving direction information for at least one NT-TRP and means for determining the predicted Doppler frequency shift offset and the Doppler frequency shift offset uncertainty based on the direction information and the ephemeris information, and is the network entity according to Clause 64.

[0239] Clause 66. The Doppler frequency shift offset uncertainty is indicated as a parts per million (ppm) value with respect to the predicted Doppler frequency shift offset by the positioning AD, and is the network entity according to Clause 64 or 65.

[0240] Clause 67. The network entity according to any one of Clauses 59 to 66, further comprising means for determining an expected Doppler frequency offset drift corresponding to an expected Doppler frequency drift of an expected Doppler frequency shift offset during a positioning session, means for determining an expected Doppler frequency offset drift rate corresponding to an expected Doppler frequency drift rate of an expected Doppler frequency shift offset during a positioning session, or any combination thereof.

[0241] Clause 68. The network entity according to Clause 67, wherein the expected Doppler frequency offset drift is determined from an indication in the positioning AD, the expected Doppler frequency offset drift rate is determined from an indication in the positioning AD, or any combination thereof.

[0242] Clause 69. The network entity according to any one of Clauses 59 to 68, further comprising means for determining an effective duration corresponding to the duration for which the frequency domain search window is valid, wherein the effective duration is indicated by the positioning AD received by the network entity, the effective duration is determined by the network entity from ephemeris information corresponding to at least one NT-TRP, or any combination thereof.

[0243] Clause 70. The network entity according to Clause 69, further comprising means for sending a request for obtaining a new positioning AD based on the expiration of the effective duration, means for sending an error message indicating a positioning error cause corresponding to the expiration of the effective duration, or any combination thereof.

[0244] Clause 71. At least one NT-TRP is an Earth-orbiting satellite having a Low Earth Orbit (LEO), Medium Earth Orbit (MEO), or Geostationary Earth Orbit (GEO), and the predicted Doppler frequency shift offset, the predicted Doppler frequency shift offset uncertainty, or both the predicted Doppler frequency shift offset and the predicted Doppler frequency shift offset uncertainty are network entities as described in any of Clauses 59 to 70 based on the orbit of the Earth-orbiting satellite.

[0245] Clause 72. At least one NT-TRP is a network entity as described in any of Clauses 59 to 70, including an unmanned aircraft, a manned aircraft, or a light aircraft.

[0246] Clause 73. The predicted Doppler frequency shift offset, the predicted Doppler frequency shift offset uncertainty, or both the predicted Doppler frequency shift offset and the predicted Doppler frequency shift offset uncertainty are network entities as described in any of Clauses 59 to 72 based on the altitude of at least one NT-TRP, the frequency of at least one PRS resource, or any combination thereof.

[0247] Clause 74. A network entity as described in any of Clauses 59 to 73, further comprising means for receiving a positioning AD indicating a time search window corresponding to the predicted time and the predicted time uncertainty for receiving at least one PRS resource.

[0248] Clause 75. Measuring one or more signals of a Global Navigation Satellite System (GNSS), wherein measuring at least one PRS resource within a frequency domain search window is temporally close to measuring one or more signals of the GNSS, and further comprising means for measuring and means for reporting measurement data associated with the measurement of one or more signals of the GNSS and the measurement of at least one PRS resource.

[0249] Clause 76. The network entity is a base station, and determining the frequency domain search window includes receiving a positioning AD indicating values for the predicted Doppler frequency shift offset and the predicted Doppler frequency shift offset uncertainty. At least one PRS resource is an uplink PRS (UL-PRS) resource, and the network entity described in any of Clauses 59 to 75.

[0250] Clause 77. A first network entity, for sending information to a second network entity for determining a frequency domain search window corresponding to a predicted Doppler frequency shift offset and a predicted Doppler frequency shift offset uncertainty for at least one positioning reference signal (PRS) resource associated with at least one non-terrestrial transceiver point (NT-TRP) measured by the second network entity during a positioning session, and means for receiving a measurement report including information corresponding to one or more measurements made on at least one PRS resource by the second network entity. The first network entity.

[0251] Clause 78. The first network entity according to Clause 77, wherein the frequency domain search window is based on a symmetric arrangement of the predicted Doppler frequency shift offset uncertainty centered on the predicted Doppler frequency shift offset, an asymmetric arrangement of the predicted Doppler frequency shift offset uncertainty centered on the predicted Doppler frequency shift offset, an arrangement of the predicted Doppler frequency shift offset uncertainty where the minimum offset of the predicted Doppler frequency shift offset uncertainty is adjacent to the predicted Doppler frequency shift offset, or an arrangement of the predicted Doppler frequency shift offset uncertainty where the maximum offset of the predicted Doppler frequency shift offset uncertainty is adjacent to the predicted Doppler frequency shift offset.

[0252] Clause 79. The means for sending information to a second network entity includes means for sending positioning assistance data (AD) indicating values for an expected Doppler frequency shift offset and an expected Doppler frequency shift offset uncertainty, means for sending ephemeris information associated with at least one NT-TRP to determine the expected Doppler frequency shift offset and the expected Doppler frequency shift offset uncertainty, means for sending direction information associated with at least one NT-TRP to determine the expected Doppler frequency shift offset and the expected Doppler frequency shift offset uncertainty, or any combination thereof, and is the first network entity described in Clause 77 or 78.

[0253] Clause 80. The positioning AD sent to the second network entity is the first network entity described in Clause 79, and indicates the expected Doppler frequency shift offset uncertainty as parts per million (ppm) value with respect to the expected Doppler frequency shift offset.

[0254] Clause 81. The means for sending information to a second network entity includes means for sending positioning AD indicating an expected Doppler frequency offset drift corresponding to an expected Doppler frequency drift of the expected Doppler frequency shift offset during a positioning session, means for sending an expected Doppler frequency offset drift rate corresponding to an expected Doppler frequency drift rate of the expected Doppler frequency shift offset during a positioning session, or any combination thereof, and is the first network entity described in any of Clauses 77 to 80.

[0255] Clause 82. The means for sending information to a second network entity further includes means for sending positioning AD indicating an effective duration corresponding to a duration for which information for determining a frequency domain search window is valid, and is the first network entity described in any of Clauses 77 to 81.

[0256] The first network entity according to clause 82, further comprising means for receiving a request to obtain a new positioning AD based on the expiration of the effective duration, means for receiving an error message indicating a positioning error cause corresponding to the expiration of the effective duration, or any combination thereof.

[0257] Clause 84. At least one NT-TRP is an earth orbiting satellite having a low earth orbit (LEO), medium earth orbit (MEO), or geostationary orbit (GEO), and the predicted Doppler frequency shift offset, the predicted Doppler frequency shift offset uncertainty, or both the predicted Doppler frequency shift offset and the predicted Doppler frequency shift offset uncertainty are based on the orbit of the earth orbiting satellite, and is the first network entity according to any one of clauses 77 to 83.

[0258] Clause 85. At least one NT-TRP is the first network entity according to any one of clauses 77 to 83, including an unmanned aircraft, a manned aircraft, or a light aircraft.

[0259] Clause 86. The predicted Doppler frequency shift offset is based on the altitude of at least one NT-TRP, the frequency of at least one PRS resource, or any combination thereof, and is the first network entity according to any one of clauses 77 to 85.

[0260] Clause 87. The first network entity according to any one of clauses 77 to 86, further comprising means for receiving a positioning AD indicating a time search window corresponding to the predicted time and the predicted time uncertainty for receiving at least one PRS resource.

[0261] Clause 88. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a network entity, cause the network entity to determine a frequency-domain search window corresponding to an expected Doppler frequency shift offset and an expected Doppler frequency shift offset uncertainty for at least one positioning reference signal (PRS) resource associated with at least one non-terrestrial transmit-receive point (NT-TRP) for a positioning session, and to measure at least one PRS resource within the frequency-domain search window during the positioning session.

[0262] Clause 89. The non-transitory computer-readable medium according to clause 88, further comprising computer-executable instructions that, when executed by a network entity, cause the network entity to resample at least one PRS resource based on the expected Doppler frequency shift offset to detect a peak of at least one PRS resource within the frequency-domain search window.

[0263] Clause 90. The non-transitory computer-readable medium according to clause 89, further comprising computer-executable instructions that, when executed by a network entity, cause the network entity to construct a plurality of hypotheses to detect a peak of at least one PRS within the frequency-domain search window based on resampling at least one PRS resource.

[0264] Clause 91. The non-transitory computer-readable medium according to any one of clauses 88 to 90, further comprising computer-executable instructions that, when executed by a network entity, cause the network entity to transmit a measurement report including information corresponding to one or more measurements made on at least one PRS resource.

[0265] Clause 92. The frequency domain search window is determined as a symmetric arrangement of predicted Doppler frequency shift offset uncertainty centered on the predicted Doppler frequency shift offset, an asymmetric arrangement of predicted Doppler frequency shift offset uncertainty centered on the predicted Doppler frequency shift offset, an arrangement of predicted Doppler frequency shift offset uncertainty where the minimum offset of the predicted Doppler frequency shift offset uncertainty is adjacent to the predicted Doppler frequency shift offset, or an arrangement of predicted Doppler frequency shift offset uncertainty where the maximum offset of the predicted Doppler frequency shift offset uncertainty is adjacent to the predicted Doppler frequency shift offset, and is a non-transitory computer-readable medium according to any one of Clauses 88 to 91.

[0266] Clause 93. Computer-executable instructions that, when executed by a network entity, cause the network entity to determine a frequency domain search window include computer-executable instructions that, when executed by the network entity, cause the network entity to receive positioning assistance data (AD) indicating values for the predicted Doppler frequency shift offset and the predicted Doppler frequency shift offset uncertainty, or to receive ephemeris information associated with at least one NT-TRP to determine the predicted Doppler frequency shift offset and the predicted Doppler frequency shift offset uncertainty, or to perform any combination thereof, and is a non-transitory computer-readable medium according to any one of Clauses 88 to 92.

[0267] Clause 94. The ephemeris information associated with at least one NT-TRP is received, and the computer-executable instructions further include computer-executable instructions that, when executed by the network entity, cause the network entity to receive direction information for at least one NT-TRP and to determine the predicted Doppler frequency shift offset and the predicted Doppler frequency shift offset uncertainty based on the direction information and the ephemeris information, and is a non-transitory computer-readable medium according to Clause 93.

[0268] Clause 95. The predicted Doppler frequency shift offset uncertainty is the non-transitory computer-readable medium according to clause 93 or 94, which is indicated as a parts per million (ppm) value with respect to the predicted Doppler frequency shift offset by the positioning AD.

[0269] Clause 96. When executed by a network entity, the computer-executable instructions that cause the network entity to determine a predicted Doppler frequency offset drift corresponding to the predicted Doppler frequency drift of the predicted Doppler frequency shift offset during a positioning session, or to determine a predicted Doppler frequency offset drift rate corresponding to the predicted Doppler frequency drift rate of the predicted Doppler frequency shift offset during a positioning session, or to perform any combination thereof, are further included in the non-transitory computer-readable medium according to any one of clauses 88 to 95.

[0270] Clause 97. The predicted Doppler frequency offset drift is determined from an indication in the positioning AD, the predicted Doppler frequency offset drift rate is determined from an indication in the positioning AD, or any combination thereof, in the non-transitory computer-readable medium according to clause 96.

[0271] Clause 98. When executed by a network entity, the computer-executable instructions that further cause the network entity to determine a valid duration corresponding to the duration for which the frequency domain search window is valid are included, and the valid duration is indicated by the positioning AD received by the network entity, the valid duration is determined by the network entity from ephemeris information corresponding to at least one NT-TRP, or any combination thereof, in the non-transitory computer-readable medium according to any one of clauses 88 to 97.

[0272] Clause 99. When executed by a network entity, the non-transitory computer-readable medium according to Clause 98 further includes computer-executable instructions to cause the network entity to send a request to obtain a new positioning AD based on the expiration of the validity duration, or to send an error message indicating the positioning error cause corresponding to the expiration of the validity duration, or to perform any combination thereof.

[0273] Clause 100. At least one NT-TRP is an earth-orbiting satellite having a low Earth orbit (LEO), a medium Earth orbit (MEO), or a geostationary orbit (GEO), and the predicted Doppler frequency shift offset, the predicted Doppler frequency shift offset uncertainty, or both the predicted Doppler frequency shift offset and the predicted Doppler frequency shift offset uncertainty are based on the orbit of the earth-orbiting satellite, the non-transitory computer-readable medium according to any one of Clauses 88 to 99.

[0274] Clause 101. At least one NT-TRP is the non-transitory computer-readable medium according to any one of Clauses 88 to 99, including an unmanned aircraft, a manned aircraft, or a light aircraft.

[0275] Clause 102. The predicted Doppler frequency shift offset, the predicted Doppler frequency shift offset uncertainty, or both the predicted Doppler frequency shift offset and the predicted Doppler frequency shift offset uncertainty are based on the altitude of at least one NT-TRP, the frequency of at least one PRS resource, or any combination thereof, the non-transitory computer-readable medium according to any one of Clauses 88 to 101.

[0276] Clause 103. When executed by a network entity, the non-transitory computer-readable medium according to any one of Clauses 88 to 102 further includes computer-executable instructions to cause the network entity to receive a positioning AD indicating a time search window corresponding to the predicted time and the predicted time uncertainty for receiving at least one PRS resource.

[0277] Clause 104. When executed by a network entity, the network entity is caused to measure one or more signals of a global navigation satellite system (GNSS), and measuring at least one PRS resource within a frequency domain search window is caused to be performed in temporal proximity to measuring one or more signals of the GNSS, and to transmit measurement data associated with the measurement of one or more signals of the GNSS and the measurement of at least one PRS resource. The non-transitory computer-readable medium according to any one of Clauses 88 to 103, further comprising computer-executable instructions.

[0278] Clause 105. The network entity is a base station, and determining a frequency domain search window includes receiving a positioning AD indicating values for an expected Doppler frequency shift offset and an expected Doppler frequency shift offset uncertainty. At least one PRS resource is an uplink PRS (UL-PRS) resource. The non-transitory computer-readable medium according to any one of Clauses 88 to 104.

[0279] A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a first network entity, cause the first network entity to send to a second network entity information for determining a frequency domain search window corresponding to an expected Doppler frequency shift offset and an expected Doppler frequency shift offset uncertainty for at least one positioning reference signal (PRS) resource associated with at least one non-terrestrial transmit-receive point (NT-TRP) measured by the second network entity during a positioning session, and cause the second network entity to receive a measurement report including information corresponding to one or more measurements performed on at least one PRS resource.

[0280] Clause 107. The frequency domain search window is based on a symmetric arrangement of predicted Doppler frequency shift offset uncertainty centered on the predicted Doppler frequency shift offset, an asymmetric arrangement of predicted Doppler frequency shift offset uncertainty centered on the predicted Doppler frequency shift offset, an arrangement of predicted Doppler frequency shift offset uncertainty where the minimum offset of the predicted Doppler frequency shift offset uncertainty is adjacent to the predicted Doppler frequency shift offset, or an arrangement of predicted Doppler frequency shift offset uncertainty where the maximum offset of the predicted Doppler frequency shift offset uncertainty is adjacent to the predicted Doppler frequency shift offset, the non-transitory computer-readable medium according to Clause 106.

[0281] Clause 108. When executed by a first network entity, the computer-executable instructions that cause the first network entity to send information to a second network entity, when executed by the first network entity, cause the first network entity to send positioning assistance data (AD) indicating values for the predicted Doppler frequency shift offset and the predicted Doppler frequency shift offset uncertainty, or to send ephemeris information associated with at least one NT-TRP to determine the predicted Doppler frequency shift offset and the predicted Doppler frequency shift offset uncertainty, or to send direction information associated with at least one NT-TRP to determine the predicted Doppler frequency shift offset and the predicted Doppler frequency shift offset uncertainty, or any combination thereof, the non-transitory computer-readable medium according to Clause 106 or 107.

[0282] Clause 109. The positioning AD sent to the second network entity indicates the predicted Doppler frequency shift offset uncertainty as parts per million (ppm) value relative to the predicted Doppler frequency shift offset, the non-transitory computer-readable medium according to Clause 108.

[0283] Clause 110. When executed by a first network entity, computer-executable instructions that cause the first network entity to send information to a second network entity include computer-executable instructions that, when executed by the first network entity, cause the first network entity to send a positioning AD that indicates a predicted Doppler frequency offset drift corresponding to a predicted Doppler frequency drift of a predicted Doppler frequency shift offset during a positioning session, a predicted Doppler frequency offset drift rate corresponding to a predicted Doppler frequency drift rate of the predicted Doppler frequency shift offset during the positioning session, or any combination thereof, in the non-transitory computer-readable medium according to any one of Clauses 106 to 109.

[0284] Clause 111. When executed by a first network entity, computer-executable instructions that cause the first network entity to send information to a second network entity include computer-executable instructions that, when executed by the first network entity, cause the first network entity to send a positioning AD that indicates an effective duration corresponding to a duration for which information for determining a frequency-domain search window is valid, in the non-transitory computer-readable medium according to any one of Clauses 106 to 110.

[0285] Clause 112. When executed by a first network entity, the non-transitory computer-readable medium according to Clause 111 further includes computer-executable instructions that cause the first network entity to receive a request to obtain a new positioning AD based on the expiration of the effective duration, receive an error message indicating a positioning error cause corresponding to the expiration of the effective duration, or perform any combination thereof.

[0286] Clause 113. At least one NT-TRP is an earth orbiting satellite having a low earth orbit (LEO), medium earth orbit (MEO), or geostationary orbit (GEO), and the predicted Doppler frequency shift offset, the predicted Doppler frequency shift offset uncertainty, or both the predicted Doppler frequency shift offset and the predicted Doppler frequency shift offset uncertainty is a non-transitory computer-readable medium as described in any of Clauses 106 - 112, based on the orbit of the earth orbiting satellite.

[0287] Clause 114. At least one NT-TRP is a non-transitory computer-readable medium as described in any of Clauses 106 - 112, including an unmanned aerial vehicle, a manned aircraft, or a light aircraft.

[0288] Clause 115. The predicted Doppler frequency shift offset is a non-transitory computer-readable medium as described in any of Clauses 106 - 114, based on the altitude of at least one NT-TRP, the frequency of at least one PRS resource, or any combination thereof.

[0289] Clause 116. When executed by a first network entity, the non-transitory computer-readable medium as described in any of Clauses 106 - 115 further includes computer-executable instructions that cause the first network entity to receive a positioning AD indicating a time search window corresponding to a predicted time and a predicted time uncertainty for receiving at least one PRS resource.

[0290] One of ordinary 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 referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0291] Furthermore, those skilled in the art will understand that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the aspects disclosed herein can be implemented as electronic hardware, computer software, or a combination 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. Those skilled in the art 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.

[0292] The various illustrative logical blocks, modules, and circuits described in connection with the aspects disclosed herein can be implemented or performed using a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof 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. The processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

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

[0294] In one or more exemplary aspects, the described functionality may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functionality may be stored on or transmitted over a computer-readable medium as one or more instructions or code. A computer-readable medium includes both a computer storage medium and a communication medium including any medium that facilitates transfer of a computer program from one place to another. The storage medium may be any available medium that can be accessed by a computer. By way of example, and not limitation, such computer-readable medium can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if 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. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc, where disk typically magnetically reproduces data and disc optically reproduces data using lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0295] Note that the above disclosure shows exemplary aspects of the present disclosure, but various changes and modifications can be made herein without departing from the scope of the present disclosure as defined by the appended claims. The functions, steps, and / or acts of the method claims according to the aspects of the present disclosure described herein need not be performed in any particular order. Further, elements of the present disclosure may be described or claimed in the singular, but the plural is contemplated unless expressly stated to the contrary.

Claims

1. A method of wireless communication performed by a network entity, Determining a frequency domain search window corresponding to the expected Doppler frequency shift offset and the expected Doppler frequency shift offset uncertainty for at least one positioning reference signal (PRS) resource associated with at least one non-terrestrial transmit / receive point (NT-TRP) for a positioning session, During the positioning session, measure the at least one PRS resource within the frequency domain search window, Includes, Determining the frequency domain search window includes receiving ephemeris information associated with the at least one NT-TRP in order to determine the expected Doppler frequency shift offset and the uncertainty of the expected Doppler frequency shift offset. The aforementioned method, Receiving directional information for at least one NT-TRP, Based on the directional information and the ephemeris information, the expected Doppler frequency shift offset and the expected Doppler frequency shift offset uncertainty are determined. Methods that further include the above.

2. Resampling the at least one PRS resource based on the expected Doppler frequency shift offset in order to detect the peak of the at least one PRS resource within the frequency domain search window. It further includes, Based on the resampling of the at least one PRS resource, a plurality of hypotheses are constructed to detect the peak of the at least one PRS resource within the frequency domain search window. The method according to claim 1, further comprising:

3. To transmit a measurement report containing information corresponding to one or more measurements taken at the at least one PRS resource, The method according to claim 1, further comprising:

4. The frequency domain search window is, A symmetrical arrangement of the predicted Doppler frequency shift offset uncertainty centered on the predicted Doppler frequency shift offset, Asymmetric arrangement of the predicted Doppler frequency shift offset uncertainty centered on the predicted Doppler frequency shift offset, The arrangement of the predicted Doppler frequency shift offset uncertainty such that the lowest offset of the predicted Doppler frequency shift offset uncertainty is adjacent to the predicted Doppler frequency shift offset, or The arrangement of the predicted Doppler frequency shift offset uncertainty such that the highest offset of the predicted Doppler frequency shift offset uncertainty is adjacent to the predicted Doppler frequency shift offset, The method according to claim 1, as determined to be the method described in claim 1.

5. To determine the expected Doppler frequency offset drift corresponding to the expected Doppler frequency drift of the expected Doppler frequency shift offset during the positioning session, Determining the expected Doppler frequency offset drift rate corresponding to the expected Doppler frequency drift rate of the expected Doppler frequency shift offset during the positioning session, or The method according to claim 1, further comprising any combination thereof.

6. The aforementioned predicted Doppler frequency offset drift is determined from the positioning AD instructions, The predicted Doppler frequency offset drift rate is determined from the indication in the positioning AD, or The method according to claim 5, which is any combination thereof.

7. The further includes determining an effective duration corresponding to the duration during which the frequency domain search window is effective, The effective duration is indicated by the positioning AD received by the network entity, The effective duration is determined by the network entity from the ephemeris information corresponding to at least one NT-TRP, or The method according to claim 1, which is any combination thereof.

8. Based on the expiration of the aforementioned validity period, a request is sent for a new positioning AD. Send an error message indicating the cause of the positioning error corresponding to the expiration of the aforementioned effective duration, or The method according to claim 7, further comprising any combination thereof.

9. The aforementioned at least one NT-TRP is low earth orbit (LEO), Earth-internal orbit (MEO), or It is an Earth-orbiting satellite with a geostationary orbit (GEO), The method according to claim 1, wherein the predicted Doppler frequency shift offset, the predicted Doppler frequency shift offset uncertainty, or both the predicted Doppler frequency shift offset and the predicted Doppler frequency shift offset uncertainty are based on the orbit of the Earth-orbiting satellite.

10. The aforementioned at least one NT-TRP is unmanned aircraft, Manned aircraft, or The method according to claim 1, including a light aircraft.

11. The predicted Doppler frequency shift offset, the predicted Doppler frequency shift offset uncertainty, or both the predicted Doppler frequency shift offset and the predicted Doppler frequency shift offset uncertainty are, The altitude of at least one NT-TRP, The frequency of the at least one PRS resource, or The method according to claim 1, based on any combination thereof.

12. Receiving a positioning AD that indicates a time search window corresponding to the expected time and the expected time uncertainty for receiving at least one PRS resource. It further includes, Measuring one or more signals of a Global Navigation Satellite System (GNSS), wherein the measurement of at least one PRS resource within the frequency domain search window is temporally close to the measurement of the one or more signals of the GNSS. To report measurement data associated with the measurement of one or more signals of the GNSS and the measurement of at least one PRS resource. The method according to claim 1, further comprising:

13. The aforementioned network entity is a base station, Determining the frequency domain search window includes receiving a positioning AD indicating values ​​for the expected Doppler frequency shift offset and the expected Doppler frequency shift offset uncertainty, The method according to claim 1, wherein the at least one PRS resource is an uplink PRS (UL-PRS) resource.

14. The wireless communication method is performed by a first network entity, Determining the frequency domain search window includes sending information for determining the frequency domain search window to a second network entity. The method described above is The second network entity receives a measurement report containing information corresponding to one or more measurements taken by the at least one PRS resource. The method according to claim 1, further comprising:

15. Network entity, Memory and At least one transceiver, The system comprises the memory and at least one processor communicatively coupled to the at least one transceiver, wherein the at least one processor is configured to perform the method according to any one of claims 1, 2, 5, 7, 8, and 14. Network entity.

Images