The receive-transmit time difference of round trip time associated with non-terrestrial network entities.

Abstract

A technology for wireless communication is disclosed. In one embodiment, a user device (UE) reports a measurement report containing sufficient information to determine the receive-transmit (Rx-Tx) time difference of a non-terrestrial network (NTN) entity. A location-estimating entity determines the round-trip time (RTT) between the UE and the NTN entity based at least in part on the information. In another embodiment, an NTN entity transmits a measurement report containing sufficient information to determine the receive-transmit Rx-Tx time difference of an NTN entity. A location-estimating entity determines the RTT between the UE and the NTN entity based at least in part on the information.

Description

[Technical Field]

[0001] 1. Areas of Disclosure The aspects of this disclosure generally relate to wireless communications.

[0002] 2. Explanation of related technologies Wireless communication systems have evolved through various generations, including first-generation (1G) analog wireless telephone services, second-generation (2G) digital wireless telephone services (including provisional 2.5G and 2.75G networks), third-generation (3G) high-speed data and internet-enabled 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 cellular analog advanced mobile phone systems (AMPS), and digital cellular systems based on code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), and the Global System for Mobile communications (GSM).

[0003] The fifth-generation (5G) wireless standard, known as New Radio (NR), enables improvements such as higher data transfer speeds, more connections, and better coverage. According to the Next Generation Mobile Network Alliance, the 5G standard is designed to provide higher data rates, more accurate positioning (based on reference signals for positioning, RS-P, such as downlink, uplink, or sidelink positioning reference signals, PRS), and other technological enhancements compared to previous standards. These enhancements enable highly accurate 5G-based positioning, as well as the use of higher frequency bands, advances in PRS processes and technology, and high-density deployment for 5G. [Overview of the project]

[0004] The following provides a simplified overview of one or more embodiments disclosed herein. Therefore, the following overview should not be considered a broad overview of all conceivable embodiments, nor should it be considered to identify any major or essential elements of all conceivable embodiments, nor should it be considered to define the scope associated with any particular embodiment. Accordingly, the sole purpose of the following overview is to provide a simplified overview of a specific concept relating to one or more embodiments of the mechanism disclosed herein, prior to the “Modes for Carrying Out the Invention” presented below.

[0005] In one embodiment, a method for operating a user device (UE) includes receiving a downlink positioning reference signal (DL-PRS) from a non-terrestrial network (NTN) entity at a first symbol of a downlink timing period, transmitting an uplink sounding reference signal (UL-SRS) to an NTN entity at a second symbol of an uplink timing period, and transmitting a measurement report containing sufficient information to determine (i) the UE receive-transmit (Rx-Tx) time difference between a first timestamp corresponding to the start of a downlink timing period and a second timestamp corresponding to the start of an uplink timing period, (ii) the first timestamp, and (iii) the second timestamp, wherein the start of a downlink timing period is based on one or more assumptions associated with the symbol durations of one or more symbols preceding the first symbol of the downlink timing period.

[0006] In one embodiment, a method for operating a non-terrestrial network (NTN) entity includes receiving an uplink sounding reference signal (UL-SRS) from a user equipment (UE) at a first symbol of an uplink timing period, and transmitting a measurement report containing sufficient information to determine (i) the NTN entity receive-transmit (Rx-Tx) time difference between a first timestamp corresponding to the start of an uplink timing period and a second timestamp corresponding to the start of a downlink timing period, (ii) the first timestamp, and (iii) the second timestamp, based on one or more assumptions associated with the symbol durations of one or more symbols preceding the first symbol of the uplink timing period.

[0007] In one embodiment, a method for operating a location estimation entity includes: (i) receiving a measurement report containing sufficient information to determine the user equipment (UE) receive-transmit (Rx-Tx) time difference between a first timestamp corresponding to the start of a downlink timing period associated with the reception of a downlink positioning reference symbol (DL-PRS) from a non-terrestrial network (NTN) entity and a second timestamp corresponding to the start of an uplink timing period associated with the transmission of an uplink sounding reference signal (UL-SRS) to an NTN entity; (ii) the first timestamp; and (iii) the second timestamp; and determining the round-trip time (RTT) between the UE and the NTN entity, at least in part, based on the information.

[0008] In one embodiment, a method for operating a location estimation entity includes receiving a measurement report containing sufficient information to determine (i) the NTN entity receive-transmit (Rx-Tx) time difference between a first timestamp corresponding to the start of an uplink timing period and a second timestamp corresponding to the start of a downlink timing period, (ii) the first timestamp, and (iii) the second timestamp, and determining the round-trip time (RTT) between the user equipment (UE) and the NTN entity based at least in part on the information.

[0009] In one embodiment, a user device (UE) includes 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 receive a downlink positioning reference signal (DL-PRS) from a non-terrestrial network (NTN) entity via the at least one transceiver at a first symbol of a downlink timing period, and to transmit an uplink sounding reference signal (UL-SRS) to an NTN entity via the at least one transceiver at a second symbol of an uplink timing period, and to transmit a measurement report via the at least one transceiver containing sufficient information to determine (i) the UE receive-transmit (Rx-Tx) time difference between a first timestamp corresponding to the start of a downlink timing period and a second timestamp corresponding to the start of an uplink timing period, (ii) the first timestamp, and (iii) the second timestamp, wherein the start of a downlink timing period is based on one or more assumptions associated with the symbol durations of one or more symbols preceding the first symbol of the downlink timing period.

[0010] In one embodiment, a non-terrestrial network (NTN) entity comprises memory, at least one transceiver, and at least one processor communicatively coupled to the memory and at least one transceiver, wherein at least one processor is configured to receive an uplink sounding reference signal (UL-SRS) from a user equipment (UE) via at least one transceiver at a first symbol of an uplink timing period, and to transmit via at least one transceiver a measurement report containing sufficient information to determine (i) the NTN entity receive-transmit (Rx-Tx) time difference between a first timestamp corresponding to the start of an uplink timing period and a second timestamp corresponding to the start of a downlink timing period, (ii) the first timestamp, and (iii) the second timestamp, wherein the start of a downlink timing period is based on one or more assumptions associated with the symbol durations of one or more symbols preceding the first symbol of an uplink timing period.

[0011] In one embodiment, the location estimation entity includes a memory, at least one transceiver, and at least one processor communically coupled to the memory and the at least one transceiver, wherein the at least one processor receives via the at least one transceiver a measurement report containing sufficient information to determine (i) the user equipment (UE) receive-transmit (Rx-Tx) time difference between (i) a first timestamp corresponding to the start of a downlink timing period associated with the reception of a downlink positioning reference symbol (DL-PRS) from a non-terrestrial network (NTN) entity and a second timestamp corresponding to the start of an uplink timing period associated with the transmission of an uplink sounding reference signal (UL-SRS) to an NTN entity, (ii) the first timestamp, and (iii) the second timestamp, and determines the round-trip time (RTT) between the UE and the NTN entity, at least in part on the information.

[0012] In one embodiment, the location estimation entity includes a memory, at least one transceiver, and at least one processor communically coupled to the memory and the at least one transceiver, wherein the at least one processor is configured to receive via the at least one transceiver a measurement report containing sufficient information to determine (i) the NTN entity receive-transmit (Rx-Tx) time difference between a first timestamp corresponding to the start of an uplink timing period and a second timestamp corresponding to the start of a downlink timing period, (ii) the first timestamp, and (iii) the second timestamp, and to determine the round-trip time (RTT) between the user equipment (UE) and the NTN entity, at least in part, based on the information.

[0013] In one embodiment, the user equipment (UE) includes means for receiving a downlink positioning reference signal (DL-PRS) from a non-terrestrial network (NTN) entity in a first symbol of a downlink timing period, means for transmitting an uplink sounding reference signal (UL-SRS) to an NTN entity in a second symbol of an uplink timing period, and means for transmitting a measurement report containing (i) a UE receive-transmit (Rx-Tx) time difference between a first timestamp corresponding to the start of a downlink timing period and a second timestamp corresponding to the start of an uplink timing period, (ii) a first timestamp, and (iii) information sufficient to determine the second timestamp, wherein the start of the downlink timing period is based on one or more assumptions associated with the symbol durations of one or more symbols preceding the first symbol of the downlink timing period.

[0014] In one embodiment, a non-terrestrial network (NTN) entity includes means for receiving an uplink sounding reference signal (UL-SRS) from a user equipment (UE) at a first symbol of an uplink timing period, and means for transmitting a measurement report containing (i) an NTN entity receive-transmit (Rx-Tx) time difference between a first timestamp corresponding to the start of an uplink timing period and a second timestamp corresponding to the start of a downlink timing period, (ii) a first timestamp, and (iii) information sufficient to determine the second timestamp, wherein the start of the downlink timing period is based on one or more assumptions associated with the symbol durations of one or more symbols preceding the first symbol of the uplink timing period.

[0015] In one embodiment, the location estimation entity includes means for receiving a measurement report containing sufficient information to determine (i) a user equipment (UE) receive-transmit (Rx-Tx) time difference between a first timestamp corresponding to the start of a downlink timing period associated with the reception of a downlink positioning reference symbol (DL-PRS) from a non-terrestrial network (NTN) entity and a second timestamp corresponding to the start of an uplink timing period associated with the transmission of an uplink sounding reference signal (UL-SRS) to an NTN entity, (ii) the first timestamp, and (iii) the second timestamp, and means for determining the round-trip time (RTT) between the UE and the NTN entity, at least in part, based on the information.

[0016] In one embodiment, the location estimation entity includes means for receiving a measurement report containing sufficient information to determine (i) the NTN entity receive-transmit (Rx-Tx) time difference between a first timestamp corresponding to the start of an uplink timing period and a second timestamp corresponding to the start of a downlink timing period, (ii) the first timestamp, and (iii) the second timestamp; and means for determining the round-trip time (RTT) between the user equipment (UE) and the NTN entity, at least in part, based on the information.

[0017] In one embodiment, a non-temporary computer-readable medium storing computer-executable instructions, wherein when the computer-executable instructions are executed by a user device (UE), the UE causes the UE to receive a downlink positioning reference signal (DL-PRS) from a non-terrestrial network (NTN) entity in a first symbol of a downlink timing period, transmit an uplink sounding reference signal (UL-SRS) to an NTN entity in a second symbol of an uplink timing period, transmit a measurement report containing (i) a UE receive-transmit (Rx-Tx) time difference between a first timestamp corresponding to the start of a downlink timing period and a second timestamp corresponding to the start of an uplink timing period, (ii) a first timestamp, and (iii) a second timestamp, and the non-temporary computer-readable medium is based on one or more assumptions relating the start of a downlink timing period to the symbol duration of one or more symbols preceding the first symbol of the downlink timing period.

[0018] In one embodiment, a non-temporary computer-readable medium storing computer-executable instructions, wherein when a computer-executable instruction is executed by a non-terrestrial network (NTN) entity, the NTN entity causes the NTN entity to receive an uplink sounding reference signal (UL-SRS) from a user device (UE) at a first symbol of an uplink timing period, and to transmit a measurement report containing sufficient information to determine (i) the NTN entity receive-transmit (Rx-Tx) time difference between a first timestamp corresponding to the start of an uplink timing period and a second timestamp corresponding to the start of a downlink timing period, (ii) the first timestamp, and (iii) the second timestamp, and the start of a downlink timing period is based on one or more assumptions associated with the symbol duration of one or more symbols preceding the first symbol of an uplink timing period.

[0019] In one embodiment, a non-temporary computer-readable medium for storing computer-executable instructions, the non-temporary computer-readable medium causes the location-estimating entity to receive a measurement report containing sufficient information to determine (i) a user equipment (UE) receive-transmit (Rx-Tx) time difference between (i) a first timestamp corresponding to the start of a downlink timing period associated with the reception of a downlink positioning reference symbol (DL-PRS) from a non-terrestrial network (NTN) entity and a second timestamp corresponding to the start of an uplink timing period associated with the transmission of an uplink sounding reference signal (UL-SRS) to an NTN entity, (ii) a first timestamp, and (iii) a second timestamp, and to determine the round-trip time (RTT) between the UE and the NTN entity, at least in part, based on the information.

[0020] In one aspect, a non - transitory computer - readable medium storing computer - executable instructions, wherein when the computer - executable instructions are executed by a position - estimating entity, the position - estimating entity is caused to receive a measurement report containing information sufficient to determine (i) the NTN entity receive - transmit (Rx - Tx) time difference between a first timestamp corresponding to the start of an uplink timing period and a second timestamp corresponding to the start of a downlink timing period, (ii) the first timestamp, and (iii) the second timestamp, and based at least in part on the information, cause a round - trip time (RTT) between a user equipment (UE) and the NTN entity to be determined.

[0021] Other objectives and advantages associated with the aspects disclosed herein will be apparent to those skilled in the art based on the accompanying drawings and the "Detailed Description of the Invention".

[0022] The accompanying drawings are presented to assist in the description of various aspects of the present disclosure and are provided by way of example only and not to limit those aspects.

Brief Description of the Drawings

[0023] [Figure 1] An exemplary wireless communication system according to an aspect of the present disclosure is shown. [Figure 2A] An exemplary wireless network configuration according to an aspect of the present disclosure is shown. [Figure 2B] An exemplary wireless network configuration according to an aspect of the present disclosure is shown. [Figure 2C] An exemplary wireless network configuration according to an aspect of the present disclosure is shown. [Figure 3A] A simplified block diagram of some exemplary aspects of components that can be employed in a user equipment (UE) and configured to support the communications taught herein. [Figure 3B]This is a simplified block diagram of some exemplary embodiments of components that may be employed in a base station and configured to support the communications taught herein. [Figure 3C] This is a simplified block diagram of some exemplary embodiments of components that may be employed in a network entity and configured to support the communications taught herein. [Figure 4] This figure shows an exemplary frame configuration according to an aspect of the present disclosure. [Figure 5] This figure shows various downlink channels in an exemplary downlink slot according to an aspect of the present disclosure. [Figure 6] This diagram shows an exemplary PRS configuration for transmitting a positioning reference signal (PRS) from a given base station, according to an aspect of the present disclosure. [Figure 7] This figure shows various uplink channels in an exemplary uplink slot according to an aspect of this disclosure. [Figure 8] Examples of various positioning methods supported in New Radio (NR) according to the aspects of this disclosure are shown. [Figure 9] This figure shows an exemplary round-trip time (RTT) procedure for determining the location of a UE according to an aspect of this disclosure. [Figure 10] This figure shows exemplary timing of RTT measurement signals exchanged between a base station and an UE according to an aspect of this disclosure. [Figure 11] This disclosure describes a single-satellite multi-RTT technique according to the present invention. [Figure 12] The timing of the terrestrial network (TN) according to the aspects of this disclosure is shown. [Figure 13] The present disclosure illustrates a timing scenario for the UE for TUE-RX-TX. [Figure 14] The timing scenarios for the gNB for TUE-RX-TX according to the aspects of this disclosure are shown. [Figure 15] An exemplary communication process according to one aspect of this disclosure is shown. [Figure 16] An exemplary communication process according to one aspect of this disclosure is shown. [Figure 17] An exemplary communication process according to one aspect of this disclosure is shown. [Figure 18] An exemplary communication process according to one aspect of this disclosure is shown. [Figure 19] Figures 15 to 18 show exemplary implementations of the processes according to the aspects of this disclosure. [Modes for carrying out the invention]

[0024] The aspects of this disclosure are provided in the following description and related drawings, which cover various examples provided for illustrative purposes. Alternative embodiments can be devised without departing from the scope of this disclosure. Furthermore, well-known elements of this disclosure will not be described in detail or will be omitted so as not to obscure the relevant details of this disclosure.

[0025] Various aspects generally relate to the receive-transmit (Rx-Tx) time difference between a UE and a non-terrestrial network (NTN) entity (e.g., a LEO satellite) in various scenarios. Some aspects, in more detail, relate to the UE Rx-Tx time difference, the NTN Rx-Tx time difference, or both.

[0026] Certain aspects of the subject matter described herein can be implemented to realize one or more of the following potential benefits. In some examples, such aspects may provide a variety of technical benefits, such as overcoming some or all of the problems that may arise when a terrestrial network (TN) timing technique for Rx-Tx time difference is mirrored for NTN positioning (e.g., more accurate subframe start times, "combined" Rx-Tx time difference reporting by both the UE and NTN entities), which may improve the accuracy of UE position estimation and / or UE position verification.

[0027] In this specification, the terms “exemplary” and / or “example” are used to mean “to serve as an example, case, or illustration.” Any aspect described herein as “exemplary” and / or “example” should not necessarily be construed as being preferable or advantageous to any other aspect. Similarly, the term “aspects of the disclosure” does not require that all aspects of the disclosure include the features, advantages, or modes of operation discussed.

[0028] Those skilled in the art will understand that the information and signals described below may be represented using any of a variety of different techniques and methods. For example, the data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned 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, etc.

[0029] Furthermore, many embodiments are described, for example, in terms of sequences of actions to be performed by elements of a computing device. It will be recognized that the various actions described herein can be performed by specific circuits (e.g., application-specific integrated circuits, ASICs), by program instructions executed by one or more processors, or a combination of both. In addition, the sequence(s) of actions described herein, when executed, can be considered to be fully embodied in any form of non-temporary computer-readable storage medium that stores a corresponding set of computer instructions that cause or instruct the associated processor of the device to perform the functions described herein. Thus, the various embodiments of this disclosure can be embodied in several different forms, all of which are intended to fall within the scope of the claimed subject matter. In addition, for each of the embodiments described herein, any corresponding form of such embodiment may be described herein, for example, as “logic configured to perform” the described actions.

[0030] As used herein, the terms “User Equipment” (UE) and “Base Station” are not intended to be specific to or otherwise limited to any particular radio access technology (RAT), unless otherwise stated. Generally, a UE may be any wireless communication device used by a user to communicate over a wireless communication network (e.g., mobile phones, routers, tablet computers, laptop computers, consumer location devices, wearables (e.g., smartwatches, glasses, augmented reality (AR) / virtual reality (VR) headsets, etc.), vehicles (e.g., cars, motorcycles, bicycles, etc.), Internet of Things (IoT) devices, etc.). A UE may be mobile or (e.g., stationary at a given time) and may communicate with a radio access network (RAN). As used herein, the term “UE” 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 the core network via the RAN, and through the core network, a UE may connect to external networks 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 a UE, such as via a wired access network, a wireless local area network (WLAN) network (for example, based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 specification, etc.).

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

[0032] The term "base station" can refer to a single physical transmission-reception point (TRP), or to multiple physical TRPs, which may or may not be co-located. For example, when the term "base station" refers to a single physical TRP, that TRP may be the base station's antennas corresponding to the base station's cells (or several cell sectors). When the term "base station" refers to multiple co-located physical TRPs, those TRPs may be an array of antennas for the base station (for example, in a multiple-input multiple-output (MIMO) system, or when the base station employs beamforming). When the term "base station" refers to multiple unco-located physical TRPs, those 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). Instead, uncollocated physical TRPs may be serving base stations that receive measurement reports from UEs, and neighboring base stations whose reference radio frequency (RF) signals the UE is measuring. Since a TRP is the point at which a base station transmits and receives wireless signals, as used herein, references to transmission from or reception at a base station should be understood to refer to the specific TRP of that base station.

[0033] In some implementations that support UE positioning, the base station may not support wireless access by the UE (for example, it may not support data, voice, and / or signaling connections to the UE), but instead it can transmit a reference signal to the UE that will be measured by the UE, and / or it can also receive and measure signals transmitted by the UE. Such a base station may be called a positioning beacon (for example, when transmitting signals to the UE) and / or a location measurement unit (for example, when receiving and measuring signals from the UE).

[0034] An "RF signal" includes electromagnetic waves of a given frequency that transport information through the space between a transmitter and a receiver. A transmitter used herein may transmit a single "RF signal" or multiple "RF signals" to a receiver. However, a receiver may receive multiple "RF signals" corresponding to each transmitted RF signal due to the propagation characteristics of RF signals through multipath channels. The same RF signal transmitted through different paths between a transmitter and a receiver may be called a "multipath" RF signal. As used herein, an RF signal may also be called a "wireless signal" or simply a "signal" where it is clear from the context that the term "signal" refers to a wireless signal or an RF signal.

[0035] Figure 1 shows an exemplary wireless communication system 100 according to an aspect of the present disclosure. The wireless communication system 100 (sometimes referred to as a wireless wide area network, WWAN) may include various base stations 102 (labeled "BS") and various UEs 104. The base stations 102 may include 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 station may include an eNB and / or ng-eNB on which the wireless communication system 100 is compatible with an LTE network, or a gNB on which the wireless communication system 100 is compatible with an NR network, or a combination of both, and the small cell base station may include femtocells, picocells, microcells, etc.

[0036] Base station 102 may collectively form a RAN and interface with a core network 170 (e.g., an evolved packet core (EPC) or a 5G core (5GC)) via a backhaul link 122, and with one or more location servers 172 (e.g., a location management function (LMF) or a secure user plane location (SUPL) location platform (SLP)) via the core network 170. The location server(s) 172 may be part of the core network 170 or may be outside the core network 170. The location server(s) 172 may be integrated with base station 102. UE(s) 104 may communicate with the location server(s) 172 directly or indirectly. For example, UE(s) 104 may communicate with the location server(s) 172 via the base station(s) 102 currently serving it. UE104 may also communicate with location server 172 via other routes, such as via an application server (not shown), via a wireless local area network (WLAN) access point (AP) (e.g., AP150 described below), or via another network. For signaling purposes, communication between UE104 and location server 172 may be represented as an indirect connection (e.g., via core network 170) or a direct connection (e.g., as illustrated via direct connection 128), and intervening nodes (if any) are omitted from the signaling diagram for clarity.

[0037] In addition to other functions, base stations 102 may perform functions related to one or more of the following: 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 balancing, non-access stratum (NAS) message delivery, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracing, RAN information management (RIM), paging, positioning, and warning message delivery. Base stations 102 may communicate with each other directly or indirectly (e.g., via EPC / 5GC) via backhaul links 134, which may be wired or wireless.

[0038] Base station 102 can communicate wirelessly with UE 104. Each base station 102 can provide communication coverage for its respective geographical coverage area 110. In one embodiment, one or more cells may be supported by base stations 102 within each geographical coverage area 110. A “cell” is a logical communication entity used for communication with a base station (over several frequency resources, e.g., 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.) to distinguish cells operating over the same or different carrier frequencies. In some cases, different cells may be configured according to different protocol types that can provide access to different types of UEs (e.g., machine-type communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or others). Since a cell is supported by a specific base station, the term "cell" may, depending on the context, refer to either or both of the logical communication entity and the base station that supports the cell. In addition, since a TRP is typically the physical transmission point of a cell, the terms "cell" and "TRP" may be used interchangeably. In some cases, the term "cell" may also refer to the geographical coverage area (e.g., sector) of a base station, insofar as the carrier frequency can be detected and used for communication within a portion of the geographical coverage area 110.

[0039] The geographical coverage areas 110 of neighboring macrocell base stations 102 may partially overlap (for example, in handover areas), and some of the geographical coverage areas 110 may be significantly overlapped by larger geographical coverage areas 110. For example, a small cell base station 102' (labeled "SC" for "small cell") may have a geographical coverage area 110' that significantly overlaps with the geographical coverage areas 110 of one or more macrocell base stations 102. A network containing both small cell base stations and macrocell base stations may be known as a heterogeneous network. A heterogeneous network may also include home eNBs (HeNBs) that may serve a limited group known as a closed subscriber group (CSG).

[0040] The communication link 120 between base station 102 and UE 104 may include uplink (also called reverse link) transmission from UE 104 to base station 102, and / or downlink (DL) (also called forward link) transmission from base station 102 to UE 104. The communication link 120 may utilize MIMO antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link 120 may consist of one or more carrier frequencies. Carrier allocation may be asymmetric with respect to the downlink and uplink (for example, more or fewer carriers may be allocated to the downlink than to the uplink).

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

[0042] Small cell base station 102' may operate in the licensed frequency spectrum and / or the unlicensed frequency spectrum. When operating in the unlicensed frequency spectrum, small cell base station 102' may employ LTE or NR technology and use the same 5GHz unlicensed frequency spectrum used by WLAN AP150. Small cell base station 102' employing LTE / 5G in the unlicensed frequency spectrum may extend coverage to the access network and / or increase the capacity of the access network. NR in the unlicensed spectrum may be called NR-U. LTE in the unlicensed spectrum may be called LTE-U, licensed assisted access (LAA), or MULTEFIRE®.

[0043] The wireless communication system 100 may further include a millimeter wave (mmW) base station 180 that can operate at millimeter wave (mmW) frequencies and / or quasi-mmW frequencies while communicating with the UE 182. Extremely high frequency (EHF) is a part of RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and wavelengths of 1 mm to 10 mm. Radio waves in this band may be called millimeter waves. Quasi-mmW may extend up to a frequency of 3 GHz with a wavelength of 100 mm. The super high frequency (SHF) band extends from 3 GHz to 30 GHz and is also called centimeter waves. Communication using the mmW / quasi-mmW radio frequency band has high path loss and relatively short distances. The mmW base station 180 and UE 182 may utilize beamforming (transmit and / or receive) via the mmW communication link 184 to compensate for the extremely high path loss and short distances. Furthermore, in alternative configurations, it will be understood that one or more base stations 102 may also transmit using mmW or quasi-mmW and beamforming. Accordingly, it will be understood that the above examples are merely illustrative and should not be construed as limiting the various aspects of the disclosure herein.

[0044] Transmit beamforming is a technique for concentrating RF signals in a specific direction. Traditionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts that signal in all directions (omnidirectionally). Using transmit beamforming, a network node can determine where a given target device (e.g., a UE) is located (relative to the transmitting network node) and emit a stronger downlink RF signal in that specific direction, thereby providing a faster and more powerful RF signal (in terms of data rate) to one or more receiving devices. To change the directivity of an RF signal when transmitting, a network node can control the phase and relative amplitude of the RF signal at each of the one or more transmitters broadcasting the RF signal. For example, a network node may use an array of antennas (also called a "phased array" or "antenna array") that creates a beam of RF waves that can be "steered" to point in different directions without actually moving the antennas. Specifically, the RF current from the transmitter is supplied to each antenna in an appropriate phase relationship so that the radio waves from separate antennas combine to cancel out and suppress radiation in undesirable directions, while simultaneously increasing radiation in desired directions.

[0045] Transmit beams can be quasi-co-located, meaning that to a receiver (e.g., UE), the transmit beam appears to have the same parameters regardless of whether the network node's transmit antenna itself is physically co-located. 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 the source reference RF signal on the source beam. Thus, if the source reference RF signal is QCL type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, mean delay, and delay spread of a second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type B, the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of a second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type C, the receiver can use the source reference RF signal to estimate the Doppler shift and mean delay of a second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type D, the receiver can use the source reference RF signal to estimate the spatial reception parameters of a second reference RF signal transmitted on the same channel.

[0046] In receive beamforming, a receiver uses a received beam to amplify an RF signal detected on a given channel. For example, a receiver can increase the gain setting of an antenna array in a particular direction and / or adjust the phase setting to amplify an RF signal received from that direction (e.g., increase its gain level). Therefore, when a 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 gain of all other receive beams available to the receiver in that direction. This results in a stronger received signal intensity (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), signal-to-interference-plus-noise ratio (SINR)) of the RF signal received from that direction.

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

[0048] It should be noted that a “downlink” beam can be either a transmit beam or a receive beam, depending on the entity forming it. For example, if a base station forms a downlink beam to transmit a reference signal to a UE, then the downlink beam is a transmit beam. However, if a UE forms a downlink beam, then it is a receive beam for receiving a downlink reference signal. Similarly, an “uplink” beam can be either a transmit beam or a receive beam, depending on the entity forming it. For example, if a base station forms an uplink beam, then it is an uplink receive beam, and if a UE forms an uplink beam, then it is an uplink transmit beam.

[0049] The electromagnetic spectrum is often subdivided into various classes, bands, and channels based on frequency / wavelength. In 5G NR, two initial operating bands are identified as 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 above 6 GHz, it should be understood that FR1 is often referred to (for interchangeability) as the "sub-6 GHz" band in various documents and papers. A similar nomenclature issue arises with FR2, which is often referred to (for interchangeability) as the "millimeter wave" band in documents and papers, even though it is different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) designated as the "millimeter wave" band by the International Telecommunication Union (INTERNATIONAL TELECOMMUNICATION UNION®).

[0050] The frequencies between FR1 and FR2 are often referred to as intermediate band frequencies. Recent 5G NR research has identified the operating band for these intermediate band frequencies as frequency range designation FR3 (7.125 GHz to 24.25 GHz). The frequency bands included within FR3 may inherit the FR1 and / or FR2 characteristics, and therefore, in effect, the features of FR1 and / or FR2 can be extended to the intermediate band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz 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 falls within the EHF band.

[0051] With the above aspects in mind, unless otherwise specified, terms such as "sub-6GHz" may broadly refer to frequencies that may be less than 6GHz, frequencies that may be within FR1, or frequencies that may include intermediate band frequencies, as used herein. Furthermore, unless otherwise specified, terms such as "millimeter wave" may broadly refer to frequencies that may include intermediate band frequencies, frequencies that may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or frequencies that may be within the EHF band, as used herein.

[0052] In multi-carrier systems such as 5G, one of the carrier frequencies is called the "primary carrier," "anchor carrier," "primary serving cell," or "PCell," while the remaining carrier frequencies are called "secondary carriers," "secondary serving cells," or "SCells." In carrier aggregation, the anchor carrier is the carrier operating on the primary frequency (e.g., FR1) utilized by UE104 / 182, and is the cell from which UE104 / 182 either performs the initial radio resource control (RRC) connection establishment procedure or initiates the RRC connection re-establishment procedure. The primary carrier carries all common control channels and UE-specific control channels and may (but not always) be a carrier on licensed frequencies. The secondary carrier is a carrier operating on a second frequency (e.g., FR2) that may be configured once an RRC connection is established between UE104 and the anchor carrier and may be used to provide additional radio resources. In some cases, the secondary carrier may be a carrier on unlicensed frequencies. Since both the primary uplink carrier and primary downlink carrier are typically UE-specific, the secondary carrier should contain only the necessary signaling information and signals, and for example, there may be no UE-specific signaling information and signals in 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. Since a "serving cell" (whether PCell or SCell) corresponds to the carrier frequency / component carrier through which several base stations communicate, terms such as "cell," "serving cell," "component carrier," and "carrier frequency" can be used interchangeably.

[0053] For example, referring further to Figure 1, one of the frequencies used by the macrocell base station 102 may be the anchor carrier (or "PCell"), and the other frequencies used by the macrocell base station 102 and / or the mmW base station 180 may be secondary carriers ("SCell"). Simultaneous transmission and / or reception of multiple carriers allows UE 104 / 182 to significantly increase its data transmission rate and / or data reception rate. For example, two 20MHz carriers bundled together in a multicarrier system would theoretically result in a data rate increase of twice as much (i.e., 40MHz) compared to the data rate achieved by a single 20MHz carrier.

[0054] The wireless communication system 100 may further include a UE 164 capable of communicating with a macrocell base station 102 via a communication link 120 and / or with an mmW base station 180 via an mmW communication link 184. For example, the macrocell base station 102 may support PCell and one or more SCells to the UE 164, and the mmW base station 180 may support one or more SCells to the UE 164.

[0055] In some cases, UE164 and UE182 may be capable of sidelink communication. Sidelink-capable UEs (SL-UEs) may 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). SL-UEs (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). Wireless sidelink (or simply "sidelink") is an adaptation of core-cellular (e.g., LTE, NR) standards that enables direct communication between two or more UEs without the need for communication to go through a base station. Sidelink communication can be unicast or multicast and may be used for device-to-device (D2D) medium 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 utilizing 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 otherwise unable to receive transmissions from base station 102. In some cases, a 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 in 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.

[0056] In one embodiment, the sidelink 160 may operate on a wireless communication medium of interest, which may be shared with other vehicles and / or infrastructure access points, as well as with other wireless communications between other RATs. The “medium” may consist of one or more time, frequency, and / or spatial communication resources (e.g., one or more channels across one or more carriers) associated with wireless communications between one or more transmitter / receiver pairs. In one embodiment, the medium of interest may correspond to at least a portion of an unlicensed frequency band shared among various RATs. Different licensed frequency bands are reserved for certain communications systems (e.g., by government agencies 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) technology, most notably IEEE 802.11x WLAN technology commonly known as “Wi-Fi”. Examples of this type of system include various variations such as CDMA systems, TDMA systems, FDMA systems, orthogonal FDMA (OFDMA) systems, and single-carrier FDMA (SC-FDMA) systems.

[0057] Figure 1 shows only two of the UEs as SL-UEs (i.e., UE164 and UE182), but note that any of the shown UEs could be an SL-UE. Furthermore, although it was stated that only UE182 is beamforming, any of the shown UEs, including UE164, could be beamforming. If SL-UEs are beamforming, they can beamform toward each other (i.e., toward other SL-UEs), toward other UEs (e.g., UE104), toward base stations (e.g., base stations 102, 180, small cell 102', access point 150), and so on. Therefore, in some cases, UE164 and UE182 can utilize beamforming via sidelink 160.

[0058] In the example shown in Figure 1, any of the UEs shown (shown in Figure 1 as a single UE104 for simplicity) may receive signals 124 from one or more Earth-orbiting space vehicles (SVs) 112 (e.g., satellites). In one embodiment, the SV112 may be part of a satellite positioning system that the UE104 can use as an independent source of location information. The satellite positioning system typically includes a system of transmitters (e.g., SV112) which are arranged to enable a receiver (e.g., UE104) to determine the location of the receiver on or above Earth, at least in part, based on positioning signals (e.g., signals 124) received from the transmitters. Such transmitters typically transmit signals marked with a set number of repeating pseudo-random noise (PN) codes. The transmitters are typically located within the SV112, but may in some cases be located on a ground-based control station, base station 102, and / or other UE104. UE104 may include one or more dedicated receivers specifically designed to receive signals 124 for deriving geolocation information from SV112.

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

[0060] In one embodiment, SV112 may, additionally or alternatively, be part of one or more non-terrestrial networks (NTNs). In an NTN, SV112 is connected to an earth station (also called a ground station, NTN gateway, or gateway), which is then connected to an element in the 5G network, such as a modified base station 102 (without a terrestrial antenna) or a network node in 5GC. This element then provides access to other elements in the 5G network, and ultimately to entities outside the 5G network, such as internet web servers and other user devices. In this way, UE104 may receive communication signals (e.g., signal 124) from SV112 in place of, or in addition to, communication signals from the ground base station 102.

[0061] The wireless communication system 100 may further include one or more UEs, such as UE190, which are indirectly connected to one or more communication networks via one or more D2D peer-to-peer (P2P) links (referred to as “sidelinks”). In the example in Figure 1, UE190 has a D2D P2P link 192 with one of the UEs 104 connected to one of the base stations 102 (for example, through which UE190 may indirectly obtain cellular connectivity), and a D2D P2P link 194 with a WLAN STA 152 connected to a WLAN AP 150 (through which UE190 may indirectly obtain WLAN-based internet connectivity). In one example, D2D P2P links 192 and 194 may be supported using any well-known D2D RAT, such as LTE Direct (LTE-D), WI-FI DIRECT®, or BLUETOOTH®.

[0062] Figure 2A shows an exemplary wireless network configuration 200. For example, 5GC210 (also called Next Generation Core (NGC)) can be functionally considered to have 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 functions, access to data networks, IP routing, etc.) working collaboratively to form the core network. User plane interface (NG-U) 213 and control plane interface (NG-C) 215 connect gNB222 to 5GC210, specifically to user plane functions 212 and control plane functions 214, respectively. In an additional configuration, ng-eNB224 may also be connected to 5GC210 via NG-C215 to control plane functions 214 and NG-U213 to user plane functions 212. Furthermore, ng-eNB224 may communicate directly with gNB222 via backhaul connection 223. In some configurations, the Next Generation RAN (NG-RAN) 220 may have one or more gNB222s, while other configurations may include one or more of both ng-eNB224 and gNB222. Either (or both) of the gNB222 or ng-eNB224 may communicate with one or more UE204s (e.g., any of the UEs described herein).

[0063] Another optional configuration may include a location server 230, which may communicate with the 5GC210 to provide location assistance to one or more UEs 204. The location server 230 can be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules across multiple physical servers), or alternatively, each may correspond to a single server. The location server 230 may be configured to support one or more location services for UEs 204 that can connect to the location server 230 via the core network, the 5GC210, and / or the internet (not shown). Furthermore, the location server 230 may be integrated into the core network components, or alternatively, be located outside the core network (e.g., a third-party server, such as an original equipment manufacturer (OEM) server or service server).

[0064] Figure 2B shows another exemplary wireless network configuration 240. 5GC260 (which may correspond to 5GC210 in Figure 2A) can be functionally considered as a control plane function provided by an access and mobility management function (AMF) 264, and a user plane function provided by a user plane function (UPF) 262, working collaboratively to form the core network (i.e., 5GC260). The functions of AMF264 include registration management, connection management, reachability management, mobility management, lawful interception, transport for session management (SM) messages between one or more UE204 (e.g., any of the UEs described herein) and session management function (SMF)266, transparent proxy service for routing SM messages, access authentication and access permission, transport for short message service (SMS) messages between UE204 and short message service function (SMSF) (not shown), and security anchor functionality (SEAF). AMF264 also interacts with authentication server function (AUSF) (not shown) and UE204 and receives intermediate keys established as a result of the UE204 authentication process. In the case of authentication based on UMTS (Universal Mobile Telecommunications System) subscriber identity module (USIM), AMF264 retrieves security material from AUSF. The AMF264's functionality also includes security context management (SCM).The SCM receives keys from the SEAF that the SCM uses to derive access network-specific keys. The AMF264's functions also include 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-RAN 220 and the LMF270, EPS bearer identifier assignment for interacting with the evolved packet system (EPS), and UE204 mobility event notification. In addition, the AMF264 also supports functions for non-3GPP ("3GPP" is a registered trademark) (Third Generation Partnership Project) access networks.

[0065] The functions of UPF262 include (when applicable) acting as an anchor point for intra-RAT / inter-RAT mobility, acting as an external protocol data unit (PDU) session point for interconnection to a data network (not shown), 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) processing for the user plane (e.g., uplink / downlink rate enforcement, reflective QoS marking on the downlink), uplink traffic verification (mapping service data flow (SDF) to QoS flow), transport-level packet marking on the uplink and downlink, providing downlink packet buffering and downlink data notification triggering, and sending and forwarding one or more “end markers” to the source RAN node. UPF262 may also support the forwarding of location service messages on the user plane between UE204 and location servers such as SLP272.

[0066] The functions of the SMF266 ​​include session management, UE Internet Protocol (IP) address assignment and management, selection and control of user plane functions, configuration of traffic steering in the UPF262 for routing traffic to appropriate destinations, some control over policy enforcement and QoS, and downlink data notification. The interface through which the SMF266 ​​communicates with the AMF264 is called the N11 interface.

[0067] Another optional embodiment may include an LMF270 that may communicate with the 5GC260 to provide location assistance to the UE204. The LMF270 can be implemented as multiple separate servers (e.g., physically separate 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 LMF270 can be configured to support one or more location services for the UE204, which can connect to the LMF270 via the core network, the 5GC260, and / or via the internet (not shown). The SLP272 may support similar functionality to the LMF270, while the LMF270 can communicate with the AMF264, NG-RAN220, and UE204 via the control plane (e.g., using interfaces and protocols intended to transmit signaling messages rather than voice or data), while the SLP272 can communicate with the UE204 and external clients (e.g., third-party servers 274) via the user plane (e.g., using the transmission control protocol (TCP) and / or protocols intended to carry voice and / or data, such as IP).

[0068] Another optional configuration may include a third-party server 274 that may communicate with the LMF270, SLP272, 5GC260 (e.g., via the AMF264 and / or UPF262), NG-RAN220, and / or UE204 to obtain location information (e.g., location estimates) about the UE204. Thus, in some cases, the third-party server 274 may be referred to as a location service (LCS) client or external client. The third-party server 274 can be implemented as multiple separate servers (e.g., physically separate 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.

[0069] The user plane interface 263 and the control plane interface 265 connect the 5GC260, specifically the UPF262 and AMF264, to one or more gNB222 and / or ng-eNB224 in the NG-RAN220, respectively. The interface between the gNB(single or multiple)222 and / or ng-eNB(single or multiple)224 and the AMF264 is called the "N2" interface, and the interface between the gNB(single or multiple)222 and / or ng-eNB(single or multiple)224 and the UPF262 is called the "N3" interface. The gNB(single or multiple)222 and / or ng-eNB(single or multiple)224 in the NG-RAN220 can communicate directly with each other via a backhaul connection 223 called the "Xn-C" interface. One or more of the gNB222 and / or ng-eNB224 may communicate with one or more UE204s via a wireless interface called the "Uu" interface.

[0070] The functions of gNB222 can be divided among 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 forwarding user data, mobility control, radio access network sharing, positioning, and session management, except for those functions which are exclusively assigned to the gNB-DU(s) 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 gNB222. The gNB-DU228 is a logical node that generally hosts the radio link control (RLC) and medium access control (MAC) layers of the gNB222. Its operation is controlled by the gNB-CU226. A single gNB-DU228 can support one or more cells, and one cell is supported by only one gNB-DU228. The interface 232 between the gNB-CU226 and one or more gNB-DU228s is called the "F1" interface. The physical (PHY) layer functions of the gNB222 are generally hosted by one or more standalone gNB-RU229s that perform functions such as power amplification and signal transmission / reception. The interface between the gNB-DU228 and the gNB-RU229 is called the "Fx" interface. Therefore, UE204 communicates with gNB-CU226 via the RRC, SDAP, and PDCP layers, with gNB-DU228 via the RLC and MAC layers, and with gNB-RU229 via the PHY layer.

[0071] The deployment of communication systems such as 5G NR systems can be configured in multiple ways using various components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, RAN nodes, core network nodes, network elements, or network equipment, such as base stations or one or more units (or one or more components) that perform base station functions, can be implemented in an aggregated or unaggregated architecture. For example, a base station (Node B (NB), advanced NB (eNB), NR base station, 5G NB, access point (AP), transceiver point (TRP), or cell, etc.) can be implemented as an aggregated base station (also known as a standalone base station or a monolithic base station) or an unaggregated base station.

[0072] Aggregated base stations may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. Non-aggregated base stations may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)). In some embodiments, CUs may be implemented within a RAN node, and one or more DUs may be co-located with CUs or, alternatively, geographically or virtually distributed across one or more other RAN nodes. DUs may be implemented to communicate with one or more RUs. Each of CUs, DUs, and RUs 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).

[0073] The operation or network design of a base station type may take into account the aggregation characteristics of the base station functions. For example, non-aggregated base stations can be used in integrated access backhaul (IAB) networks, open radio access networks (O-RAN (such as network configurations supported by the O-RAN ALLIANCE®)), or virtualized radio access networks (vRAN, also known as cloud radio access networks (C-RAN)). Non-aggregated configurations may include distributing functions across two or more units in various physical locations, and virtually distributing the functions of at least one unit, which can allow for flexibility in network design. 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.

[0074] Figure 2C shows an exemplary unaggregated base station architecture 250 according to an aspect of the present disclosure. The unaggregated base station architecture 250 may include one or more central units (CUs) 280 (e.g., gNB-CU226) that can communicate directly with the core network 267 (e.g., 5GC210, 5GC260) via backhaul links, or indirectly with the core network 267 via one or more unaggregated 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 CUs 280 may communicate with one or more DUs 285 (e.g., gNB-DU228) via their respective midhaul links, such as an F1 interface. The DU285 may communicate with one or more radio units (RUs) 287 (e.g., gNB-RU229) via their respective fronthaul links. The RU287 may communicate with their respective UE204 via one or more radio frequency (RF) access links. In some implementations, the UE204 may be serviced simultaneously by multiple RU287s.

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

[0076] In some embodiments, the CU280 may host one or more higher-layer control functions. Such control functions may include RRC, PDCP, Service Data Adaptive Protocol (SDAP), etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by the CU280. The CU280 may 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, the CU280 may be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units may communicate bidirectionally with the CU-CP units via an interface such as the E1 interface. The CU280 may be implemented to communicate with the DU285 as needed for network control and signaling.

[0077] The DU285 may correspond to a logic unit containing one or more base station functions for controlling the operation of one or more RU287s. In some embodiments, the DU285 may host one or more of the RLC layer, MAC layer, and one or more upper PHY layers (such as modules related to forward error correction (FEC) coding and decoding, scrambling, modulation and demodulation, etc.), at least in part according to a functional decomposition such as that defined by the 3rd Generation Partnership Project (3GPP®). In some embodiments, the DU285 may further host one or more lower PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU285, or with control functions hosted by the CU280.

[0078] Lower-layer functions can be implemented by one or more RU287s. In some deployments, RU287s controlled by DU285s may correspond to logical nodes hosting RF processing functions, or lower PHY layer functions (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 functional decomposition such as lower-layer functional decomposition. In such architectures, RU(s)287s can be implemented to handle over-the-air (OTA) communication with one or more UE204s. In some implementations, real-time and non-real-time modes of control plane communication and user plane communication with RU(s)287s can be controlled by the corresponding DU285s. In some scenarios, this configuration can enable the DU(singular or plural)285 and CU280 to be implemented in cloud-based RAN architectures such as vRAN architectures.

[0079] The SMO framework 255 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 255 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operational and maintenance interfaces (such as the O1 interface). For virtualized network elements, the SMO framework 255 may be configured to interact with a cloud computing platform (such as the 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 the O2 interface). Such virtualized network elements may include, but are not limited to, the CU280, DU285, RU287, and quasi-RT RIC259. In some implementations, the SMO framework 255 may communicate with hardware embodiments of the 4G RAN, such as the Open eNB (O-eNB) 261, via the O1 interface. In addition, in some implementations, the SMO framework 255 can communicate directly with one or more RU287s via the O1 interface. The SMO framework 255 may also include non-RT RIC257s configured to support the functionality of the SMO framework 255.

[0080] Non-RT RIC257 may be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, including artificial intelligence / machine learning (AI / ML) workflows, model training and updating, or policy-based guidance for applications / features in quasi-RT RIC259. Non-RT RIC257 may be coupled to or communicate with quasi-RT RIC259 (e.g., via the A1 interface). Quasi-RT RIC259 may be configured to include logical functions that enable quasi-real-time control and optimization of RAN elements and resources via data acquisition and actions through an interface connecting to quasi-RT RIC259 (e.g., via the E2 interface), including one or more CU280s, one or more DU285s, or both, and an O-eNB, via an interface connecting to quasi-RT RIC259 (e.g., via the E2 interface).

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

[0082] Figures 3A, 3B, and 3C show several exemplary components (represented by corresponding blocks) that may be incorporated into UE302 (which may correspond to any of the UEs described herein), base station 304 (which may correspond to any of the base stations described herein), and network entity 306 (which may correspond to or embody any of the network functions described herein, including location server 230 and LMF270, or alternatively, a private network, which may be independent of the NG-RAN220 and / or 5GC210 / 260 infrastructure shown in Figures 2A and 2B) 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 into other devices in a 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, the device may include multiple transceiver components that enable the device to operate on multiple carriers and / or communicate via different technologies.

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

[0084] Each UE 302 and base station 304 also includes, in at least some cases, one or more short-range wireless transceivers 320 and 360, respectively. The short-range wireless transceivers 320 and 360 may be connected to one or more antennas 326 and 366, respectively, and may provide means (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, means for refraining from transmitting, etc.) for communicating with other network nodes such as other UEs, access points, and base stations via at least one designated RAT (e.g., Wi-Fi, LTE-Direct, BLUETOOTH®, ZIGBEE®, Z-WAVE®, PC5, dedicated short-range communications (DSRC), wireless access for vehicular environments (WAVE), near-field communication (NFC), ultra-wideband (UWB), etc.) via the wireless communication medium of interest. The short-range wireless transceivers 320 and 360 can be configured in various ways to transmit and encode signals 328 and 368 (e.g., messages, instructions, information, etc.), respectively, according to a specified RAT, and conversely, to receive and decode signals 328 and 368 (e.g., messages, indications, information, pilots, etc.), respectively. Specifically, the short-range wireless transceivers 320 and 360 include one or more transmitters 324 and 364, respectively, for transmitting and encoding signals 328 and 368, respectively, and one or more receivers 322 and 362, respectively, for receiving and decoding signals 328 and 368, respectively.For example, the short-range wireless transceivers 320 and 360 may be Wi-Fi transceivers, BLUETOOTH® transceivers, ZIGBEE® and / or Z-WAVE® transceivers, NFC transceivers, UWB transceivers, or vehicle-to-vehicle (V2V) and / or vehicle-to-everything (V2X) transceivers.

[0085] UE 302 and base station 304 also include satellite signaling transceivers 330 and 370, each including, in at least some cases, satellite receivers(single or multiple) 330-1 and / or 370-1, and / or satellite transmitters(single or multiple) 330-2 and / or 370-2, respectively. In some designs, the satellite signaling "transceivers" may be implemented as Rx-only satellite receivers or Tx-only satellite transmitters. In some designs, base station 304 is a ground station capable of communicating with satellites(single or multiple) via satellite signaling transceivers(single or multiple). In other designs, base station 304 may itself be a satellite (or non-terrestrial entity) that communicates with terrestrial networks and / or other satellites using satellite signaling transceivers(single or multiple) 370.

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

[0087] Satellite signal transmitters 330-2 and 370-2 may be connected to one or more antennas 336 and 376, respectively, and may provide means for transmitting satellite positioning / communication signals 338 and 378, respectively. If satellite signal transmitters 330-2 and 370-2 are satellite positioning system transmitters, the satellite positioning / communication signals 338 and 378 may be Global Positioning System (GPS) signals, Global Navigation Satellite System (GLONASS) signals, Galileo signals, Beidou signals, Indian Regional Navigation Satellite System (NAVIC), Quasi-Zenith Satellite System (QZSS), etc. If satellite signal transmitters 330-2 and 370-2 are non-terrestrial network (NTN) transmitters, the satellite positioning / communication signals 338 and 378 may be communication signals originating from a 5G network (e.g., controlling and / or carrying user data). Satellite signal transmitters 330-2 and 370-2 may include any suitable hardware and / or software for transmitting satellite positioning / communication signals 338 and 378, respectively. Satellite signal transmitters 330-2 and 370-2 may, as necessary, request information and actions from other systems and, in at least some cases, perform calculations to determine the locations of UE 302 and base station 304, respectively, using measurements transmitted to and from any suitable satellite positioning system algorithm.

[0088] Each 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.

[0089] A transceiver may be configured to communicate over a wired or wireless link. A transceiver (whether wired or wireless) 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, a transceiver may be an integrated device (e.g., embodying the transmitter and receiver circuit configurations within a single device), in some implementations it may have 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. A wireless transmitter circuit configuration (e.g., transmitters 314, 324, 354, 364) may include, or be coupled to, multiple antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, enabling each device (e.g., UE 302, base station 304) to perform transmit beamforming. Similarly, a wireless receiver circuit configuration (e.g., receivers 312, 322, 352, 362) may include, or be coupled to, multiple antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, enabling each device (e.g., UE 302, base station 304) to perform receive beamforming. In one embodiment, the transmitter and receiver circuit configurations may share multiple identical antennas (e.g., antennas 316, 326, 356, 366), such that each device can either receive or transmit only at a given time, but not both at the same time. Wireless transceivers (e.g., WWAN transceivers 310 and 350, short-range wireless transceivers 320 and 360) may also include network listen modules (NLMs) for performing various measurements.

[0090] The various wireless transceivers used herein (e.g., transceivers 310, 320, 350, and 360 in some implementations, and network transceivers 380 and 390) and wired transceivers (e.g., network transceivers 380 and 390 in some implementations) may generally be characterized as “transceivers,” “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 performed. For example, backhaul communication between network devices or servers generally involves signaling via wired transceivers, while wireless communication between a UE (e.g., UE 302) and a base station (e.g., base station 304) generally involves signaling via wireless transceivers.

[0091] UE302, base station 304, and network entity 306 also include other components that may be used in conjunction with the operations disclosed herein. UE302, 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 other processing functions. Thus, processors 332, 384, and 394 may provide processing means such as means for determining, means for calculating, means for receiving, means for transmitting, and means for instructing. In one embodiment, processors 332, 384, and 394 may include, for example, one or more general-purpose processors, multicore 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.

[0092] The UE302, base station 304, and network entity 306 include memory circuit configurations that implement memories 340, 386, and 396, respectively (each including a memory device, for example), to maintain information (e.g., information indicating reserved resources, thresholds, parameters, etc.). Thus, memories 340, 386, and 396 may provide means for storing, retrieving, maintaining, etc. In some cases, the UE302, base station 304, and network entity 306 may include Rx-Tx components 342, 388, and 398, respectively. The Rx-Tx components 342, 388, and 398 may be hardware circuits that are part of processors 332, 384, and 394, respectively, or hardware circuits coupled thereto, which, when executed, cause the UE302, base station 304, and network entity 306 to perform the functions described herein. In other embodiments, the Rx-Tx components 342, 388, and 398 may be external to the processors 332, 384, and 394 (e.g., as part of a modem processing system, integrated with another processing system, etc.). Alternatively, the Rx-Tx components 342, 388, and 398 may be memory modules stored in memory 340, 386, and 396, respectively, which, when executed by the processors 332, 384, and 394 (or a modem processing system, another processing system, etc.), cause the UE 302, base station 304, and network entity 306 to perform the functions described herein. Figure 3A shows possible configurations of the Rx-Tx component 342, which may be part of, for example, one or more WWAN transceivers 310, memory 340, one or more processors 332, or any combination thereof, or may be a standalone component. Figure 3B shows possible configurations of the Rx-Tx component 388, which may be part of, for example, one or more WWAN transceivers 350, memory 386, one or more processors 384, or any combination thereof, or may be a standalone component.Figure 3C shows possible configurations of the Rx-Tx 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 it may be a standalone component.

[0093] UE302 may include one or more sensors 344 coupled to one or more processors 332 to provide means for sensing or detecting motion and / or orientation information that is independent of motion data derived from signals received by one or more WWAN transceivers 310, one or more short-range wireless transceivers 320, and / or satellite signal receivers 330. For example, one or more sensors 344 may include accelerometers (e.g., micro-electrical mechanical systems, MEMS devices), gyroscopes, geomagnetic sensors (e.g., compasses), altimeters (e.g., barometric altimeters), and / or any other type of motion-sensing sensor. Furthermore, one or more sensors 344 may include multiple different types of devices, and their outputs may be combined to provide motion information. For example, a sensor(s) 344 may use a combination of a multi-axis accelerometer and an orientation sensor to provide the ability to calculate position in a two-dimensional (2D) and / or three-dimensional (3D) coordinate system.

[0094] In addition, UE302 includes a user interface 346 that provides means for providing instructions to the user (e.g., audible and / or visual instructions) and / or for receiving user input (e.g., when a user activates a sensing device such as a keypad, touchscreen, or microphone). Although not shown, the base station 304 and the network entity 306 may also include user interfaces.

[0095] Referring more specifically to one or more processors 384, in the downlink, IP packets from network entity 306 may be provided to processor 384. One or more processors 384 may implement functions for the RRC layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Medium Access Control (MAC) layer. One or more processors 384 may provide RRC layer functions associated with broadcasting system information (e.g., master information blocks (MIBs), system information blocks (SIBs)), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection correction, and RRC connection release), inter-RAT mobility, and measurement configuration for UE measurement reporting; PDCP layer functions associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with forwarding 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 reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, priority processing, and logical channel prioritization.

[0096] The transmitter 354 and 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 to 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 coded and modulated symbols can then be divided into parallel streams. Next, each stream may be mapped to an orthogonal frequency division multiplexing (OFDM) subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then synthesized together using an inverse fast Fourier transform (IFFT) to generate a physical channel that carries a time-domain OFDM symbol stream. The OFDM symbol stream is spatially precoded to generate multiple spatial streams. Channel estimates from a channel estimator may be used to determine the coding and modulation scheme, and for spatial processing. Channel estimates may be derived from the reference signal and / or channel state feedback transmitted by UE302. Each spatial stream may then be supplied to one or more different antennas 356. Transmitter 354 may modulate RF carriers using each spatial stream for transmission.

[0097] In UE302, receiver 312 receives signals through its respective antenna(s) 316. Receiver 312 reconstructs the information modulated on the RF carrier and provides this 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 reconstruct any spatial stream directed to UE302. If multiple spatial streams are directed to UE302, they can be combined into a single OFDM symbol stream by receiver 312. 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 contains a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are reconstructed and demodulated by determining the most likely signal constellation point transmitted by base station 304. These soft decisions can be based on channel estimates calculated by a channel estimator. Next, the soft decision decodes and deinterleaves the data and control signals initially transmitted by the base station 304 on the physical channel. The data and control signals are then provided to one or more processors 332 implementing Layer 3 (L3) and Layer 2 (L2) functions.

[0098] In the downlink, one or more processors 332 provide demultiplexing between transport and logical channels, packet reassembly, decoding, header decompression, and control signal processing to reconstruct IP packets from the core network. One or more processors 332 are also responsible for error detection.

[0099] Similar to the functions described in relation to downlink transmission by base station 304, one or more processors 332 provide RRC layer functions associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functions associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with forwarding 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 MAC SDUs onto transport blocks (TBs), demultiplexing MAC SDUs from TBs, scheduling information reporting, error correction by hybrid automatic repeat request (HARQ), priority processing, and logical channel prioritization.

[0100] The channel estimate derived by the channel estimator from the reference signal or feedback transmitted by the base station 304 may 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 may be supplied to different antennas 316. The transmitter 314 may modulate the RF carrier using each spatial stream for transmission.

[0101] Uplink transmissions are processed at base station 304 in a manner similar to that described in relation to the receiver function in UE302. Receiver 352 receives the signal through its respective antenna(s) 356. Receiver 352 reconstructs the information modulated on the RF carrier and provides this information to one or more processors 384.

[0102] In the uplink, one or more processors 384 provide demultiplexing between transport and logical channels, packet reassembly, decoding, header decompression, and control signal processing to reconstruct IP packets from the UE302. IP packets from one or more processors 384 can then be supplied to the core network. One or more processors 384 are also responsible for error detection.

[0103] For convenience, the UE302, base station 304, and / or network entity 306 are shown in Figures 3A, 3B, and 3C as including various components that may be configured according to the various examples described herein. However, it should be understood that the components shown may have different functions in different designs. In detail, the various components in Figures 3A–3C are optional in alternative configurations, and the various embodiments include configurations that may vary due to design choices, cost, device usage, or other considerations. For example, in Figure 3A, a particular implementation of UE302 may omit the WWAN transceiver(s) 310 (e.g., a wearable device, tablet computer, personal computer (PC), or laptop may have Wi-Fi and / or Bluetooth® capabilities without cellular capabilities), or the short-range wireless transceiver(s) 320 (e.g., cellular only), or the satellite signal receiver(s) 330, or the sensor(s) 344, etc. Another example is in Figure 3B, where a particular implementation of base station(s) 304 may omit the WWAN transceiver(s) 350 (e.g., a Wi-Fi "hotspot" access point without cellular capabilities), or the short-range wireless transceiver(s) 360 (e.g., cellular only), or the satellite signal receiver(s) 370, etc. For the sake of brevity, examples of various alternative configurations are not provided herein, but they should be readily apparent to those skilled in the art.

[0104] Various components of UE302, base station 304, and network entity 306 can be coupled to communicate with one another via data buses 334, 382, ​​and 392, respectively. In one embodiment, data buses 334, 382, ​​and 392 may form or be part of the communication interfaces of UE302, base station 304, and network entity 306, respectively. For example, if different logical entities are embodied within the same device (e.g., gNB and location server functions are integrated within the same base station 304), data buses 334, 382, ​​and 392 may provide communication between them.

[0105] The components in Figures 3A, 3B, and 3C can be implemented in various ways. In some implementations, the components in Figures 3A, 3B, and 3C can be implemented in one or more circuits, such as 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 may be implemented by the processor and memory components (one or more) of UE302 (e.g., by the execution of appropriate code and / or by the appropriate configuration of the processor components). Similarly, some or all of the functionality represented by blocks 350-388 may be implemented by the processor and memory components (one or more) of base station 304 (e.g., by the execution of appropriate code and / or by the appropriate configuration of the processor components). Furthermore, some or all of the functions represented by blocks 390-398 may be implemented by the processor and memory components (one or more) of the network entity 306 (for example, by the execution of appropriate code and / or by the appropriate configuration of processor components). For simplicity, various operations, actions, and / or functions are described herein as being performed “by the UE,” “by the base station,” “by the network entity,” etc. However, as can be understood, such operations, actions, and / or functions may actually be performed by specific components or combinations of components such as the UE 302, base station 304, and network entity 306, including processors 332, 384, 394, transceivers 310, 320, 350, and 360, memories 340, 386, and 396, and Rx-Tx components 342, 388, and 398.

[0106] In some designs, the network entity 306 may be implemented as a core network component. In other designs, the network entity 306 may be separate from the network operator or operation of the cellular network infrastructure (e.g., NG RAN220 and / or 5GC210 / 260). For example, the network entity 306 may be a component of a private network that communicates with the UE302 via the base station 304, or it may be configured independently of the base station 304 (e.g., via a non-cellular communication link such as Wi-Fi).

[0107] Various frame configurations may be used to support downlink and uplink transmissions between network nodes (e.g., base stations and UEs). Figure 4 is a 400-figure diagram illustrating an exemplary frame configuration according to an aspect of this disclosure. The frame configuration may be a downlink or uplink frame configuration. Other wireless communication technologies may have different frame configurations and / or different channels.

[0108] LTE, and sometimes 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, commonly called tones or bins. Each subcarrier can be modulated with data. Generally, the modulation symbol is transmitted 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). Therefore, the nominal Fast Fourier Transform (FFT) sizes 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 for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, there can be 1, 2, 4, 8, or 16 subbands, respectively.

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

[0110] In the example in Figure 4, a 15 kHz numerology is used. Therefore, in the time domain, a 10 ms frame is divided into 10 subframes of equal size, each of 1 ms, and each subframe contains one time slot. In Figure 4, time is represented horizontally (on the X axis), increasing from left to right, and frequency is represented vertically (on the Y axis), increasing (or decreasing) from bottom to top.

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

[0112] Some of the REs may carry reference (pilot) signals (RS). Depending on whether the shown frame configuration is used for uplink or downlink communication, the reference signals may include positioning reference signals (PRS), tracking reference signals (TRS), phase tracking reference signals (PTRS), cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), primary synchronization signal (PSS), secondary synchronization signal (SSS), synchronization signal blocks (SSBs), sounding reference signals (SRS), etc. Figure 4 shows an exemplary arrangement of REs carrying reference signals (labeled "R").

[0113] Figure 5 is a diagram illustrating various downlink channels within an exemplary downlink slot. In Figure 5, time is represented horizontally (on the X-axis), increasing from left to right, and frequency is represented vertically (on the Y-axis), increasing (or decreasing) from bottom to top. In the example in Figure 5, a 15 kHz numerology is used. Thus, in the time domain, the shown slot is 1 millisecond (ms) long and is divided into 14 symbols.

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

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

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

[0117] In the example in Figure 5, there is one CORESET per BWP, and the CORESET spans three symbols in the time domain (although it could be only one or two symbols). Unlike the LTE control channel, which occupies the entire system bandwidth, in NR, the PDCCH channel is confined to a specific region in the frequency domain (i.e., a CORESET). Therefore, the frequency component of the PDCCH shown in Figure 5 is shown as less than a single BWP in the frequency domain. Note that the shown CORESET is contiguous in the frequency domain, but it does not have to be. In addition, a CORESET can span fewer than three symbols in the time domain.

[0118] The DCIs within a PDCCH carry information about uplink resource allocations (persistent and non-persistent), called uplink grants and downlink grants, and descriptions of downlink data to be sent to the UE, respectively. More specifically, DCIs indicate resources scheduled for downlink data channels (e.g., PDSCHs) and uplink data channels (e.g., physical uplink shared channels (PUSCHs)). Multiple (e.g., up to eight) DCIs may be configured within a PDCCH, and these DCIs may have one of several formats. For example, different DCI formats exist for uplink scheduling, downlink scheduling, and uplink transmit power control (TPC). A PDCCH can be transported by one, two, four, eight, or sixteen CCEs to accommodate different DCI payload sizes or coding rates.

[0119] Figure 6 is a diagram of an exemplary PRS configuration 600 for PRS transmission of a given base station according to an aspect of the present disclosure. In Figure 6, time is represented horizontally and increases from left to right. Each long rectangle represents a slot, and each short (shaded) rectangle represents an OFDM symbol. In the example of Figure 6, PRS resource set 610 (labeled “PRS resource set 1”) includes two PRS resources, namely a first PRS resource 612 (labeled “PRS resource 1”) and a second PRS resource 614 (labeled “PRS resource 2”). The base station transmits PRS on PRS resources 612 and 614 of PRS resource set 610.

[0120] PRS resource set 610 has an occasion length of 2 slots (N_PRS) and a period of, for example, 160 slots or 160 milliseconds (ms) (for a subcarrier interval of 15 kHz) (T_PRS). Thus, both PRS resources 612 and 614 are two consecutive slots in length, starting with the slot in which the first symbol of the individual PRS resource appears, and repeating every T_PRS slots. In the example in Figure 6, PRS resource 612 has a symbol length of 2 symbols (N_symb), and PRS resource 614 has a symbol length of 4 symbols (N_symb). PRS resources 612 and 614 may be transmitted on separate beams of the same base station.

[0121] Each instance of the PRS resource set 610, shown as instances 620a, 620b, and 620c, contains an occasion of length "2" (i.e., N_PRS=2) for each PRS resource 612, 614 in the PRS resource set. PRS resources 612 and 614 are iterated over T_PRS slots until the muting sequence period T_REP. Therefore, a bitmap of length T_REP is required to indicate which occasions among instances 620a, 620b, and 620c of the PRS resource set 610 are muted (i.e., not transmitted).

[0122] In one embodiment, additional constraints may apply to the PRS configuration 600. For example, with respect to all PRS resources (e.g., PRS resources 612, 614) of a PRS resource set (e.g., PRS resource set 610), the base station may configure the following parameters, namely (a) occasion length (N_PRS), (b) number of symbols (N_symb), (c) comb type, and / or (d) bandwidth, to be the same. In addition, with respect to all PRS resources of all PRS resource sets, the subcarrier spacing and cyclic prefix may be configured to be the same for one base station or for all base stations. Whether it is for one base station or for all base stations may depend on the UE's ability to support the first and / or second option.

[0123] Figure 7 is a diagram showing various uplink channels within an exemplary uplink slot. In Figure 7, time is represented horizontally (on the X-axis), increasing from left to right, and frequency is represented vertically (on the Y-axis), increasing (or decreasing) from bottom to top. In the example in Figure 7, a 15 kHz numerology is used. Thus, in the time domain, the shown slot is 1 millisecond (ms) long and is divided into 14 symbols.

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

[0125] In one embodiment, the reference signal carried on the RE labeled "R" in Figure 4 may be an SRS. The SRS transmitted by the UE may be used by the base station to obtain channel state information (CSI) from the transmitting UE. The CSI describes how the RF signal propagates from the UE to the base station and represents the combined effects of scattering, fading, and power attenuation with distance. The system uses the SRS for resource scheduling, link adaptation, massive MIMO, beam management, and other purposes.

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

[0127] The transmission of an SRS resource within a given PRB has a specific comb size (also called "comb density"). The comb size "N" represents the subcarrier interval (or frequency / tone interval) within each symbol of the SRS resource configuration. Specifically, for a comb size "N", the SRS is transmitted on every Nth subcarrier of the symbols in the PRB. For example, for comb 4, for each symbol of the SRS resource configuration, the RE corresponding to every 4th subcarrier (subcarrier 0, 4, 8, etc.) is used to transmit the SRS of the SRS resource. In the example in Figure 4, the shown SRS is comb 4 across four symbols. That is, the arrangement of the shaded SRS REs indicates the SRS resource configuration for comb 4.

[0128] Currently, SRS resources can span 1, 2, 4, 8, or 12 consecutive symbols within a comb size of comb 2, comb 4, or comb 8 slots. The following are the symbol-to-symbol frequency offsets for currently supported SRS comb patterns. 1 symbolcom2:{0}, 2 symbolcom2:{0,1}, 2 symbolcom4:{0,2}, 4 symbolcom2:{0,1,0,1}, 4 symbolcom4:{0,2,1,3} (as in the example in Figure 4), 8 symbolcom4:{0,2,1,3,0,2,1,3}, 12 symbolcom4:{0,2,1,3,0,2,1,3,0,2,1,3}, 4 symbolcom8:{0,4,2,6}, 8 symbolcom8:{0,4,2,6,1,5,3,7}, and 12 symbolcom8:{0,4,2,6,1,5,3,7,0,4,2,6}.

[0129] Generally, as described above, a UE transmits an SRS to enable a receiving base station (either a serving base station or an adjacent base station) to measure the channel quality (i.e., CSI) between the UE and the base station. However, an SRS may also be specifically configured as an uplink positioning reference signal for uplink-based positioning procedures such as uplink time difference (UL-TDOA), round-trip time (RTT), and uplink angle of arrival (UL-AoA). As used herein, the term “SRS” may refer to an SRS configured for channel quality measurement or an 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 “communication SRS” and / or the latter as “positioning SRS” or “positioning SRS”.

[0130] Several extensions beyond the previous definition of SRS have been proposed for positioning SRS (also known as "UL-PRS" or "UL-SRS"), including new staggered patterns within SRS resources (except single symbol / comb 2), new comb types for SRS, new sequences for SRS, SRS resource sets with a greater number per component carrier, and SRS resources with a greater number per component carrier. In addition, the parameters "SpatialRelationInfo" and "PathLossReference" will be set based on downlink reference signals or SSB from neighboring TRPs. Furthermore, a single SRS resource may be transmitted outside of an active BWP, and a single SRS resource may span multiple component carriers. Also, SRS may be configured in an RRC connected state and may only be transmitted within an active BWP. Furthermore, frequency hopping and repetition coefficients may be absent, a single antenna port may exist, and new lengths for SRS (e.g., 8 and 12 symbols) may exist. Furthermore, open-loop power control may be used instead of closed-loop power control, and Com 8 (i.e., SRS is transmitted for every eighth subcarrier within the same symbol) may be used. Finally, a UE may transmit from multiple SRS resources for UL-AoA through the same transmit beam. All of these are features added to the current SRS framework, which is configured through RRC upper-layer signaling (and potentially triggered or activated through MAC control elements (MAC-CE) or downlink control information (DCI)).

[0131] 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 8 shows examples of various positioning methods according to aspects of this disclosure. In the OTDOA or DL-TDOA positioning procedure shown by Scenario 810, the UE measures the difference between the times of arrival (ToAs) of a reference signal (e.g., positioning reference signal (PRS)) received from a pair of base stations, called reference signal time difference (RSTD) measurements or time difference of arrival (TDOA) measurements, and reports them to the positioning entity. More specifically, the UE receives identifiers (IDs) of a reference base station (e.g., a serving base station) and several non-reference base stations in the support 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.

[0132] In DL-AoD positioning as shown in Scenario 820, the positioning entity uses measurement reports from the UE of received signal intensity measurements of multiple downlink transmit beams to determine the angle(s) between the UE and the transmitting base station(s). The positioning entity can then estimate the location of the UE based on the determined angle(s) and the known locations(s) of the transmitting base station(s).

[0133] Uplink-based positioning methods include uplink time difference (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 multiple non-reference base stations. Each base station then reports the reception time of the reference signal(s) (called relative time of arrival, RTOA) to a positioning entity (e.g., a location server) that knows the locations and relative timings of the involved base stations. Based on the reception-to-reception (Rx-Rx) time difference between the reference base station's reported RTOA and each non-reference base station's reported RTOA, the known locations of the base stations, and their known timing offsets, the positioning entity can use TDOA to estimate the UE's location.

[0134] In 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 receive beams. The positioning entity uses the signal strength measurements and the angles(single or multiple) of the received beams(single or multiple) to determine the angle(s) between the UE and the base station(s). Based on the determined angle(s) and the known locations(s) of the base stations(s), the positioning entity can then estimate the location of the UE.

[0135] Downlink and uplink-based positioning methods include enhanced cell-ID (E-CID) positioning and multi-round-trip time (RTT) positioning (also known 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., 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., SRS or PRS) back to the first entity. Each entity measures the time difference between the time to arrival (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 measurement may be made to include only the time difference between the nearest slot boundaries for the received and transmitted signals, or it may be adjusted accordingly. Next, both entities may send their Rx-Tx time difference measurements to a location server (e.g., LMF270), which calculates the round-trip propagation time (i.e., RTT) between the two entities from the two Rx-Tx time difference measurements (e.g., as the sum of the two Rx-Tx time difference measurements). Alternatively, one entity may send its Rx-Tx time difference measurement to the other entity, which then calculates the RTT. The distance between the two entities can be determined from the RTT and a known signal speed (e.g., the speed of light). In the case of multi-RTT positioning as shown in Scenario 830, the first entity (e.g., a UE or base station) performs RTT positioning procedures with multiple second entities (e.g., multiple base stations or UEs) to enable the location of the first entity to be determined (e.g., using multilateration) based on the distance to the second entity and the known location of the second entity. As demonstrated by Scenario 840, RTT and multi-RTT methods can be combined with other positioning techniques such as UL-AoA and DL-AoD to improve location accuracy.

[0136] 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 identifier, estimated timing, and signal strength of the detected nearby base station. The UE's location is then estimated based on this information and the known locations of the base station(s).

[0137] To support positioning operations, location servers (e.g., location servers 230, LMF270, SLP272) may provide support data to the UE. For example, the support data may include the identifier of the base station (or base station cell / TRP) from which the reference signal will be measured, reference signal configuration parameters (e.g., the number of consecutive slots containing the PRS, the period 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 support data may be obtained directly from the base station itself (e.g., in periodically broadcast overhead messages). In some cases, the UE may be able to discover the neighboring network node itself without using support data.

[0138] In the case of OTDOA or DL-TDOA positioning procedures, the supporting data may further include the expected RSTD value and the uncertainty associated with the expected RSTD before and after, or the search window. In some cases, the expected RSTD value range may be + / - 500 microseconds (μs). In some cases, when any of the resources used for positioning measurements are in 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 (one or more) are in FR2, the value range for the uncertainty of the expected RSTD may be + / - 8 μs.

[0139] Location estimates may be referred to by other names such as position estimates, location, position, position fix, or fix. Location estimates may be geodetic and include coordinates (e.g., latitude, longitude, and possibly altitude), or urban and include addresses, postal addresses, or some other linguistic description of the location. Location estimates may further be defined for some other known locations, or they may be defined absolutely (e.g., using latitude, longitude, and possibly altitude). Location estimates may include expected errors or uncertainties (e.g., by including area or volume in which the location is expected to be contained with some specified or default level of confidence).

[0140] In NR, precise timing synchronization across the network may not be available. Instead, coarse time synchronization across base stations (e.g., within the cyclic prefix (CP) duration of orthogonal frequency division multiplexing (OFDM) symbols) may suffice. RTT-based methods generally require only coarse timing synchronization and are therefore preferred positioning methods in NR.

[0141] Figure 9 shows an exemplary wireless communication system 900 according to an aspect of the present disclosure. In the example of Figure 9, UE 904 (any of the UEs described herein) attempts to calculate an estimate of its location or to assist another entity (e.g., a base station or core network component, another UE, a location server, a third-party application, etc.) in calculating an estimate of its location. UE 904 may transmit and receive wireless signals to and from a plurality of network nodes 902-1, 902-2, and 902-3 (labeled “nodes”) (collectively, network node 902). Network node 902 may include one or more base stations (e.g., any of the base stations described herein), one or more reconfigurable intelligent displays (RISs), one or more positioning beacons, one or more UEs (e.g., connected via sidelinks), etc.

[0142] In a network-centric RTT positioning procedure, a serving base station (e.g., one of the network nodes 902) instructs UE904 to measure RTT measurement signals (e.g., PRS) from two or more neighboring network nodes 902 (and typically the serving base station, as at least three network nodes 902 are required for 2D location estimation). The participating network nodes 902 transmit RTT measurement signals over low-reuse resources allocated by the network (e.g., location server 230, LMF270, SLP272) (e.g., resources used by network node 902 to transmit system information if network node 902 is a base station). UE904 records the arrival time (also called receive time, reception time, time of reception, or time of arrival) of each RTT measurement signal relative to UE904's current downlink timing (for example, derived by UE904 from the downlink signal received from its serving base station), and transmits a common or individual RTT response signal (e.g., SRS) to the involved network node 902 on the resources allocated by its serving base station. UE904 reports a UE receive-transmit (Rx-Tx) time difference measurement to the positioning entity if it is not a positioning entity. The UE Rx-Tx time difference measurement shows the time difference between the arrival time of each RTT measurement signal in UE904 and the transmit time(s) of the RTT response signal(s). Each participating network node 902 also reports to the positioning entity a network node Rx-Tx time difference measurement (also called a base station (BS) or gNB Rx-Tx time difference measurement) which shows the difference between the transmission time of the RTT measurement signal and the reception time of the RTT response signal.

[0143] The UE-centric RTT positioning procedure is similar to the network-based procedure, except that the UE 904 transmits an uplink RTT measurement signal(s) (e.g., on a resource allocated by a serving base station). The uplink RTT measurement signal(s) are measured by several network nodes 902 in the UE 904's neighborhood. Each participating network node 902 responds with a downlink RTT response signal and reports a network node Rx-Tx time difference measurement to the positioning entity. The network node Rx-Tx time difference measurement indicates the time difference between the arrival time of the RTT measurement signal and the transmission time of the RTT response signal at the network node 902. The UE 904, if it is not the positioning entity, reports a UE Rx-Tx time difference measurement for each network node 902, indicating the difference between the transmission time of the RTT measurement signal and the reception time of the RTT response signal.

[0144] To determine the location (x,y) of UE904, the positioning entity needs to know the location of network node 902, which may be represented as (x_k,y_y) in the reference coordinate system, where k=1, 2, and 3 in the example in Figure 9. If UE904 is a positioning entity, a location server with knowledge of the network geometry (e.g., location server 230, LMF270, SLP272) can provide UE904 with the locations of the involved network node 902.

[0145] The positioning entity determines each distance 910 (d_k, k=1,2,3) between UE904 and each network node 902 based on the UE Rx-Tx and network node Rx-Tx time difference measurements and the speed of light, as further explained below with reference to Figure 10. Specifically, in the example in Figure 9, the distance 910-1 between UE904 and network node 902-1 is d_1, the distance 910-2 between UE904 and network node 902-2 is d_2, and the distance 910-3 between UE904 and network node 902-3 is d_3. Once each distance 910 is determined, the positioning entity can solve for the location (x,y) of UE904 by using various known geometric techniques such as trilateration. From Figure 9, it can be seen that the location of UE904 is ideally at the common intersection of three semicircles, each semicircle defined by radius dk and center (x_k, y_k), where k = 1, 2, and 3.

[0146] Figure 10 is a figure 1000 illustrating exemplary timing of RTT measurement signals exchanged between a network node 1002 (labeled “Node”) and a UE 1004 according to an aspect of this disclosure. UE 1004 may be any of the UEs described herein. Network node 1002 may be a base station (e.g., any of the base stations described herein), a RIS, a positioning beacon, or another UE (e.g., connected via a sidelink).

[0147] In the example in Figure 10, network node 1002 (labeled "BS") sends an RTT measurement signal 1010 (e.g., PRS) to UE 1004 at time T_1. The RTT measurement signal 1010 has some propagation delay T_Prop as it travels from network node 1002 to UE 1004. At time T_2 (the time UE 1004 receives the RTT measurement signal 1010), UE 1004 measures the RTT measurement signal 1010. After some UE processing time, UE 1004 sends an RTT response signal 1020 (e.g., SRS) at time T_3. After the propagation delay T_Prop, network node 1002 measures the RTT response signal 1020 from UE 1004 at time T_4 (the time network node 1002 receives the RTT response signal 1020).

[0148] UE1004 reports to the positioning entity the difference between time T_3 and time T_2 (i.e., the Rx-Tx time difference measurement of UE1004, indicated as UE_Rx-Tx1012). Similarly, network node 1002 reports to the positioning entity the difference between time T_4 and time T_1 (i.e., the Rx-Tx time difference measurement of network node 1002, indicated as Node_Rx-Tx1022). Using these measurements and the known speed of light, the positioning entity calculates the distance to UE1004 as d=1 / 2 * c * (Node_Rx-Tx-UE_Rx-Tx)=1 / 2 * c * (T_4-T_1)-1 / 2 * c * It can be calculated as (T_3-T_2), where c is the speed of light.

[0149] Based on the known location of network node 1002 and the distance between UE1004 and network node 1002 (and at least two other network nodes 1002), the positioning entity can calculate the location of UE1004. As shown in Figure 9, the location of UE1004 lies at the common intersection of three semicircles, each semicircle defined by the radius of the distance between UE1004 and its respective network node 1002.

[0150] In one embodiment, a positioning entity may calculate the location of a UE904 / 1004 using a two-dimensional coordinate system. However, the embodiments disclosed herein are not limited thereto and may be equally applicable to determining the location using a three-dimensional coordinate system if additional dimensions are desired. In addition, Figure 9 shows one UE904 and three network nodes 902, and Figure 10 shows one UE1004 and one network node 1002, but as can be understood, there may be more UE904 / 1004 and more network nodes 902 / 1002.

[0151] In some communication systems (e.g., Rel-18 NR NTN WI), support is intended for single-satellite multi-RTT techniques for UE location by network verification. For example, in some designs, multi-RTT may be used to support UE location by network verification in NTN, assuming a single satellite is in the field of view. While multi-RTT techniques for positioning in terrestrial networks are already supported by 3GPP, extensions are needed to account for high-speed satellite movement, such as the following: • The slot duration of the received DL signal does not vary over time in the UE. The UE must constantly perform autonomous transmission timing adjustments.

[0152] Figure 11 shows a single satellite multi-RTT technique 1100 according to an aspect of the present disclosure. In Figure 11, a high-speed moving low-earth orbit (LEO) satellite 1102 is shown at the locations indicated as (1), (2), (3), and (4). At location (1), the LEO satellite 1102 transmits a DL-PRS for RTT, shown as RTT1, to the UE 1104. At location (2), the LEO satellite 1102 receives an UL-PRS for RTT, shown as RTT2, from the UE 1104. At location (3), the LEO satellite 1102 transmits a DL-PRS for RTT, shown as RTT3, to the UE 1104. At location (4), the LEO satellite 1102 receives an UL-PRS for RTT, shown as RTT4, from the UE 1104. In this scenario, the high-speed moving nature of the LEO satellite 1102 provides sufficient spatial diversity for the position estimation and / or position verification of the UE 1104 (the UE 1104 moves at a much slower speed than the LEO satellite 1104 and can be considered "stationary" in comparison even when it is moving).

[0153] Figure 12 shows terrestrial network (TN) timing 1200 according to an aspect of the present disclosure. In Figure 12, the gNB DL timing reference, gNB UL timing reference, UE DL timing reference, and UE UL timing reference are shown with respect to a subframe.

[0154] Referring to Figure TN, RTT = T UE-RX-TX + T gNB_RX-TX is. The UE reports TUE-RX-TX whose time stamp is the slot number m of the DL PRS. The gNB reports T gNB_RX-TX whose time stamp is the slot number n of the SRS. The LMF can match the two as long as m and n are not too far apart. For this reason, the UE report and the gNB report are separated, that is, the UE has the freedom to choose the subframe (SF) in which T UE-RX-TX is reported, and the gNB reports T gNB_RX-TXThey have the freedom to choose which receiving SRS reports. Therefore, it should be noted that T UE-RX-TX and T gNB_RX_TX This does not require targeting the same TN subframe. The above formula (RTT=T UE-RX-TX +T gNB_RX-TX The assumptions in this model are that there is no change in UE timing advance (TA) between the measurement time m of the UE RX-TX time difference and the SRS transmission time n, that the same TA applies to all slots in the subframe (SF), and that the SF duration is constant in the UE.

[0155] Figure 13 shows a T according to an aspect of this disclosure. UE-RX-TX The UE timing scenario 1300 for this is shown. In Figure 13, the UE DL subframe i is significantly delayed compared to the UE UL subframe i, which is more likely to occur in NTN positioning. Various problems may arise when TN timing techniques for RTT are migrated to NTN positioning.

[0156] The current definition of the UE Rx-Tx time difference (TUE-RX-TX) is as follows: In TN, j and i are equal (i.e., RTT is less than 0.5ms and N TA-offset If (=0), the UE Rx-Tx time difference is TA. At NTN, the UE Rx-Tx time difference is: T UE_RX-TX =TA-(ji) is the subframe duration of (subframe j) in UE.

[0157] More specifically, in some designs, the following applies:

[0158] [Table 1]

[0159] Regarding subframe initiation, in the case of NTN, estimating the start of a subframe can be difficult. Determining subframe initiation using multiple DL-PRS systems can also be difficult. Furthermore, when multiple DL-PRS systems are used, ephemeris and GNSS may also need to be used. Therefore, the benefit of such techniques in NTN positioning is questionable.

[0160] Regarding transmission timing, subframe j is generally unknown to the network at NTN unless the exact TA is reported.

[0161] Regarding the use of subframes, generally, the maximum RTT change in 1ms can be 90ns. Therefore, the UE may have different TAs for slots within the SF.

[0162] Figure 14 shows a T according to an aspect of this disclosure. UE-RX-TX This shows gNB timing scenario 1400 for RTT. Various problems may arise if the TN timing technique for RTT is transitioned to NTN positioning.

[0163] gNB Rx-Tx time difference (T gNB-RX-TX In the current definition of ), N TA_offset When = 0, it is the UE UL timing error of subframe i in both TN and NTN, as shown in Figure 14.

[0164] More specifically, in some designs, the following applies:

[0165] [Table 2]

[0166] As can be understood, in the case of a gNB scenario, if the TN timing technique for RTT is migrated to NTN positioning, some of the same problems may occur compared to the UE side.

[0167] Aspects of this disclosure relate to Rx-Tx time differences between a UE and an NTN entity (e.g., a LEO satellite) in various scenarios. Such aspects may offer various technical advantages, such as overcoming some or all of the problems that may arise when TN timing techniques for Rx-Tx time differences are mirrored for NTN positioning (e.g., more accurate subframe start times, "combined" Rx-Tx time difference reporting by both the UE and the NTN entity), which may improve the accuracy of the UE's position estimation and / or UE's position verification.

[0168] Figure 15 shows an exemplary communication process 1500 according to one aspect of the present disclosure. Process 1500 in Figure 15 is performed by a UE such as UE302.

[0169] Referring to Figure 15, in 1510, UE 302 (e.g., receivers 312, 322, or 330) receives a Downlink Positioning Reference Signal (DL-PRS) from a Non-Terrestrial Network (NTN) entity at a first symbol of the Downlink Timing Period. Means for performing the reception in 1510 may include receivers 312, 322, or 330, etc., as shown in Figure 3A.

[0170] Referring to Figure 15, in 1520, UE 302 (e.g., transmitter 314, 324, or 330-2) transmits an uplink sounding reference signal (UL-SRS) to the NTN entity at a second symbol of the uplink timing period. Means for performing the transmission of 1520 may include transmitter 314, 324, or 330-2, etc., as shown in Figure 3A.

[0171] Referring to Figure 15, in 1530, UE 302 (e.g., transmitter 314, 324, or 330-2) transmits a measurement report containing sufficient information to determine (i) the UE receive-transmit (Rx-Tx) time difference between a first timestamp corresponding to the start of the downlink timing period and a second timestamp corresponding to the start of the uplink timing period, (ii) the first timestamp, and (iii) the second timestamp. In some designs, the start of the downlink timing period is based on one or more assumptions associated with the symbol durations of one or more symbols preceding the first symbol of the downlink timing period. For example, "sufficient" information to determine (i) to (iii) may include at least two of (i) to (iii), e.g., (i) + (ii) or (i) + (iii) or (ii) + (iii) or (i) + (ii) + (iii). Means for performing the transmission of 1530 may include transmitters 314, 324, or 330-2 in Figure 3A.

[0172] Referring to Figure 15, in some designs, the downlink timing period is a downlink slot, downlink subframe, or downlink symbol, and the uplink timing period is an uplink slot, uplink subframe, or uplink symbol. In some designs, the timestamp granularity associated with the first timestamp, the second timestamp, or both corresponds to the respective granularity associated with the downlink timing period, the uplink timing period, or both. For example, if the downlink timing period is a slot, the first timestamp may be a slot indicator, and if the uplink timing period is a subframe, the second timestamp may be a subframe indicator, and so on. For symbol-level timestamps, in addition to the slot / SFN index, the index of the starting symbol UL-SRS and / or DL-RS (e.g., DL-PRS) may be reported to the LMF. In some designs, this information may be included in the timestamp or reported separately to the LMF.

[0173] Referring to Figure 15, in some designs, DL-PRS instances associated with DL-PRS are within a subset of DL-PRS instances associated with the DL-PRS resource configuration for the UE's position estimation session, and / or UL-SRS instances associated with UL-SRS are within a subset of UL-SRS instances associated with the UL-SRS resource configuration for the UE's position estimation session. In some designs, the subset of DL-PRS instances and / or the subset of UL-SRS instances are comprised of a Location Management Function (LMF) or wireless network component, or the subset of DL-PRS instances and / or the subset of UL-SRS instances are indicated or required by the UE.

[0174] Referring to Figure 15, some designs include one or more assumptions that the symbol durations of one or more symbols preceding the first symbol in the downlink timing period correspond to a predefined symbol duration based on the zero-Doppler state.

[0175] Referring to Figure 15, in some designs, the information includes the UE Rx-Tx time difference and a first timestamp, or the information includes the UE Rx-Tx time difference and a second timestamp, or the information includes the UE Rx-Tx time difference, a first timestamp, and a second timestamp, or the information includes the UE Rx-Tx time difference, Doppler information associated with DL-PRS, and a first timestamp, or the information includes the UE Rx-Tx time difference, Doppler information associated with DL-PRS, and a second timestamp.

[0176] Referring to Figure 15, in some designs, the UL-SRS is associated with the earliest UL-SRS instance that follows the DL-PRS instance associated with the DL-PRS.

[0177] Referring to Figure 15, in some designs, the UE further sends a UE Rx-Tx time difference measurement capability instruction to the location estimation entity (e.g., LMF) indicating the type of UE Rx-Tx time difference that the UE is capable of measuring and / or reporting for NTN, and in response to the UE Rx-Tx time difference measurement capability instruction for NTN, receives a measurement report configuration for the information (e.g., from the location estimation entity such as the LMF). For example, the UE Rx-Tx time difference measurement capability instruction may indicate an accurate UE Rx-Tx time difference definition and associated reports that the UE is capable of measuring / reporting. For example, if a legacy Rx-Tx time difference is measured, the UE may further add Doppler information (e.g., so that the location estimation entity can apply Doppler-based adjustments to the legacy Rx-Tx time difference). Alternatively, if the UE can support one or more of the “new” Rx-Tx time differences described above, the UE may measure / report the new Rx-Tx time difference without explicitly indicating Doppler to the localization entity.

[0178] Referring to Figure 15, in some designs, the measurement report further includes instructions for the measurement report configuration associated with the information (for example, if the UE is not instructed to use a particular measurement report configuration, the measurement report configuration selected / used by the UE may be indicated in the measurement report instead).

[0179] Figure 16 shows an exemplary communication process 1600 according to one aspect of the present disclosure. Process 1600 in Figure 16 is performed by NTN entities such as BS304 and NTN entity 1102.

[0180] Referring to Figure 16, in 1610, an NTN entity (e.g., receiver 352, 362, or 370-1, etc.) receives an uplink sounding reference signal (UL-SRS) from the user equipment (UE) at a first symbol of the uplink timing period. Means for performing reception in 1610 may include receivers 352, 362, 370-1, etc., as shown in Figure 3B.

[0181] Referring to Figure 16, in 1620, an NTN entity (e.g., transmitter 354 or 364 or 370-2) transmits a measurement report containing sufficient information to determine (i) the NTN entity receive-transmit (Rx-Tx) time difference between a first timestamp corresponding to the start of an uplink timing period and a second timestamp corresponding to the start of a downlink timing period, (ii) the first timestamp, and (iii) the second timestamp. In some designs, the start of a downlink timing period is based on one or more assumptions associated with the symbol duration of one or more symbols preceding the first symbol of the uplink timing period. For example, "sufficient" information to determine (i) to (iii) may include at least two of (i) to (iii), e.g., (i) + (ii) or (i) + (iii) or (ii) + (iii) or (i) + (ii) + (iii). Means for performing the 1620 transmission may include transmitters 354, 364, or 370-2 in Figure 3B.

[0182] Referring to Figure 16, in some designs, the downlink timing period includes the downlink positioning reference signal (DL-RS), or the downlink timing period is associated with the same system subframe number and / or the same slot index as the uplink timing period. In some designs, the UL-SRS is associated with the earliest UL-SRS instance that is after the DL-RS instance associated with the DL-RS, or within the same system subframe number and / or the same slot index. In some designs, the DL-RS is the DL positioning reference signal (DL-PRS) or DL ​​channel status information RS (DL-CSI-RS) (e.g., or any other type of DL-RS).

[0183] Referring to Figure 16, in some designs, the start of the uplink timing period is determined based on the UL-SRS reception timing that begins within the uplink timing period.

[0184] Referring to Figure 16, in some designs, the downlink timing period is a downlink slot, downlink subframe, or downlink symbol, and the uplink timing period is an uplink slot, uplink subframe, or uplink symbol. In some designs, the timestamp granularity associated with the first timestamp, the second timestamp, or both corresponds to the respective granularity associated with the downlink timing period, the uplink timing period, or both. For example, if the downlink timing period is a slot, the first timestamp may be a slot indicator, and if the uplink timing period is a subframe, the second timestamp may be a subframe indicator, and so on. For symbol-level timestamps, in addition to the slot / SFN index, the index of the starting symbol UL-SRS and / or DL-RS (e.g., DL-PRS) may be reported to the LMF. In some designs, this information may be included in the timestamp or reported separately to the LMF.

[0185] Referring to Figure 16, in some designs, the UL-SRS instances associated with UL-SRS are within a subset of the UL-SRS instances associated with the UL-SRS resource configuration for the UE's location estimation session. In some designs, the subset of UL-SRS instances is comprised of the Location Management Function (LMF) or wireless network components, or the subset of UL-SRS instances is indicated or requested by the UE.

[0186] Referring to Figure 16, some designs include one or more assumptions that the symbol durations of one or more symbols preceding the first symbol in the downlink timing period correspond to a predefined symbol duration based on the zero-Doppler state.

[0187] Referring to Figure 16, in some designs, the information includes the NTN entity Rx-Tx time difference and a first timestamp, or the information includes the NTN entity Rx-Tx time difference and a second timestamp, or the information includes a first timestamp and a second timestamp.

[0188] Figure 17 shows an exemplary communication process 1700 according to one aspect of the present disclosure. Process 1700 in Figure 17 is performed by a location estimation entity. In some designs, the location estimation entity may correspond to a network component (e.g., an LMF integrated in a gNB / BS 304 / NTN entity or O-RAN component, or a remote location server such as network entity 306). In other designs, the location estimation entity may correspond to another UE (e.g., a sidelink anchor UE), or the target UE itself (e.g., in the case of UE-based location estimation, any Rx / Tx operation between the UE and the location estimation entity may correspond to the transfer of information over a data bus between different logical components of the UE), or the NTN entity itself (e.g., in that case, any Rx / Tx operation between the NTN entity and the location estimation entity may correspond to the transfer of information over a data bus between different logical components of the NTN entity). In further aspects, process 1700 in Figure 17 in the location estimation entity may correspond to a process that runs in parallel with process 1500 in Figure 15 in the UE.

[0189] Referring to Figure 17, in 1710, a position estimation entity (e.g., receivers 312, 322, 352, 362, 330-1 or 370-1, data bus 334 or data bus 382, ​​or network transceiver(s) 380 or 390, etc.) receives a measurement report containing sufficient information to determine (i) the user equipment (UE) receive-transmit (Rx-Tx) time difference between (i) a first timestamp corresponding to the start of a downlink timing period associated with receiving a downlink positioning reference symbol (DL-PRS) from a non-terrestrial network (NTN) entity and a second timestamp corresponding to the start of an uplink timing period associated with transmitting an uplink sounding reference signal (UL-SRS) to an NTN entity, (ii) the first timestamp, and (iii) the second timestamp. For example, "sufficient" information to determine (i) to (iii) may include at least two of (i) to (iii), for example, (i) + (ii) or (i) + (iii) or (ii) + (iii) or (i) + (ii) + (iii). Means for performing reception of 1710 may include receivers 312, 322, 352, 362, 330-1, or 370-1, data bus 334 or data bus 382, ​​or network transceiver(s) 380 or 390, depending on the implementation of the position estimation entity as described above, as shown in Figures 3A to 3C.

[0190] Referring to Figure 17, in 1720, the location estimation entity (e.g., one or more processors 332, 384, or 394, Rx-Tx components 342, 388, or 398, etc.) determines the round-trip time (RTT) between the UE and the NTN entity based at least partially on the information. The means for performing the determination in 1720 may include, depending on the implementation of the location estimation entity as described above, the one or more processors 332, 384, or 394, or the Rx-Tx components 342, 388, or 398, etc., as shown in Figures 3A to 3C.

[0191] Referring to Figure 17, in some designs, the position estimation entity may further determine a subset of UL-SRS instances associated with the UL-SRS resource configuration for the UE's position estimation session, and may send instructions to the UE and NTN entities, respectively, for a subset of UL-SRS instances to facilitate the transmission and measurement of one or more UL-SRS instances on the UL-SRS instances. In this way, a specific UL-SRS instance.

[0192] Referring to Figure 17, in some designs, the downlink timing period is a downlink slot or downlink subframe, and the uplink timing period is an uplink slot or uplink subframe. In some designs, the timestamp granularity associated with the first timestamp, the second timestamp, or both corresponds to the respective granularity associated with the downlink timing period, the uplink timing period, or both. For example, if the downlink timing period is a slot, the first timestamp may be a slot indicator, and if the uplink timing period is a subframe, the second timestamp may be a subframe indicator, and so on. For symbol-level timestamps, in addition to the slot / SFN index, the index of the starting symbol UL-SRS and / or DL-RS (e.g., DL-PRS) may be reported to the LMF. In some designs, this information may be included in the timestamp or reported separately to the LMF.

[0193] Referring to Figure 17, in some designs, the information includes the UE Rx-Tx time difference and a first timestamp, or the information includes the UE Rx-Tx time difference and a second timestamp, or the information includes the first timestamp and a second timestamp, or the information includes the UE Rx-Tx time difference and Doppler information associated with DL-PRS.

[0194] Referring to Figure 17, in some designs, the UL-SRS is associated with the earliest UL-SRS instance that follows the DL-PRS instance associated with the DL-PRS.

[0195] Figure 18 shows an exemplary communication process 1800 according to one aspect of the present disclosure. Process 1800 in Figure 18 is performed by a location estimation entity. In some designs, the location estimation entity may correspond to a network component (e.g., an LMF integrated in a gNB / BS 304 / NTN entity or O-RAN component, or a remote location server such as network entity 306). In other designs, the location estimation entity may correspond to another UE (e.g., a sidelink anchor UE), or the target UE itself (e.g., in the case of UE-based location estimation, any Rx / Tx operation between the UE and the location estimation entity may correspond to the transfer of information over a data bus between different logical components of the UE), or the NTN entity itself (e.g., in that case, any Rx / Tx operation between the NTN entity and the location estimation entity may correspond to the transfer of information over a data bus between different logical components of the NTN entity). In a further embodiment, process 1800 in Figure 18 in the position estimation entity may correspond to a process that runs in parallel with process 1600 in Figure 16 in the NTN entity.

[0196] Referring to Figure 18, in 1810, a location estimation entity (e.g., receivers 312, 322, 352, 362, 330-1 or 370-1, data bus 334 or data bus 382, ​​or network transceiver 380 or 390, etc.) receives a measurement report containing sufficient information to determine (i) the NTN entity receive-transmit (Rx-Tx) time difference between a first timestamp corresponding to the start of the uplink timing period and a second timestamp corresponding to the start of the downlink timing period, (ii) the first timestamp, and (iii) the second timestamp. For example, "sufficient" information to determine (i) to (iii) may include at least two of (i) to (iii), e.g., (i) + (ii) or (i) + (iii) or (ii) + (iii) or (i) + (ii) + (iii). The means for performing reception of 1810 may include, depending on the implementation form of the position estimation entity as described above, receivers 312, 322, 352, 362, 330-1, or 370-1 shown in Figures 3A to 3C, data bus 334 or data bus 382, ​​or network transceiver 380 or 390.

[0197] Referring to Figure 18, in 1820, the location estimation entity (e.g., one or more processors 332, 384, or 394, or Rx-Tx components 342, 388, or 398, etc.) determines the round-trip time (RTT) between the user equipment (UE) and the NTN entity based at least partially on the information. The means for performing the determination in 1820 may include, depending on the implementation of the location estimation entity as described above, the one or more processors 332, 384, or 394, or Rx-Tx components 342, 388, or 398, etc., as shown in Figures 3A to 3C.

[0198] Referring to Figure 18, in some designs, the downlink timing period includes the downlink positioning reference signal (DL-PRS), or the downlink timing period is associated with the same system subframe number and / or the same slot index as the uplink timing period.

[0199] Referring to Figure 18, in some designs, the UL-SRS is associated with the earliest UL-SRS instance that is either after the DL-PRS instance associated with the DL-PRS, or within the same system subframe number and / or the same slot index.

[0200] Referring to Figure 18, in some designs, the start of the uplink timing period is determined based on the UL-SRS reception timing that begins within the uplink timing period.

[0201] Referring to Figure 18, in some designs, the downlink timing period is a downlink slot or downlink subframe, and the uplink timing period is an uplink slot or uplink subframe. In some designs, the timestamp granularity associated with the first timestamp, the second timestamp, or both corresponds to the respective granularity associated with the downlink timing period, the uplink timing period, or both. For example, if the downlink timing period is a slot, the first timestamp may be a slot indicator, and if the uplink timing period is a subframe, the second timestamp may be a subframe indicator, and so on. For symbol-level timestamps, in addition to the slot / SFN index, the index of the starting symbol UL-SRS and / or DL-RS (e.g., DL-PRS) may be reported to the LMF. In some designs, this information may be included in the timestamp or reported separately to the LMF.

[0202] Figure 19 shows exemplary implementation configurations 1900 of processes 1500 to 1800 of Figures 15 to 18, respectively, according to one aspect of the present disclosure.

[0203] Referring to Figure 19, in a specific example unique to UE Rx-Tx time differences, a new type (Type 2) of UE Rx-Tx time difference may be defined. In NTN, the Type 2 UE Rx-Tx time difference is the time gap between the reception timing of subframe (slot) i of the transmit point (TP) and the transmission timing of UL subframe (slot) j of the TP, shown as T1 in Figure 19. By definition or specification, subframe / slot j contains an SRS. By definition or specification, subframe / slot i must contain the PRS that is temporally closest to subframe / slot j in the UE. The reception timing is determined by the DL PRS that starts within the subframe. When determining the start timing of the subframe / slot, a nominal symbol duration is assumed for the symbols before the start of the PRS / SRS in the subframe / slot (e.g., assuming a 0 Doppler shift). The nominal symbol duration is the duration of the symbol in the gNB, as defined by 38.211. The UE reports the transmitted SF / slot index j and SF / slot index i, or the difference between SF / slot index j and SF / slot index i and j, or the difference between SF / slot index i and i and j. The LMF or gNB constitutes the minimum set of SRS from which the UE Rx-Tx is measured and reported. Alternatively, the UE provides the gNB in ​​advance with the minimum set of SRS from which the UE Rx-Tx is measured and reported. While the UE Rx-Tx time difference has been described above, it will be understood that a similar procedure may be implemented in the NTN entity to derive the NTN Rx-Tx time difference.

[0204] Referring to Figure 19, another specific example unique to the UE Rx-Tx time difference defines a new type (Type 2) UE Rx-Tx time difference. The UE Rx-Tx time difference is the time difference between the reception timing of the TP's subframe / slot i and the transmission timing of the TP's subframe / slot i (i.e., the TA of SF / slot i). The reception timing of the subframe / slot may be determined by one or more PRSs from the TP. The UE reports the timestamp, the subframe / slot index of the SRS, along with the UE Rx-Tx time difference. The LMF or gNB constitutes the minimum set of SRSs from which the UE Rx-Tx is measured and reported. Alternatively, the UE provides the gNB in ​​advance with the minimum set of SRSs from which the UE Rx-Tx is measured and reported. When determining the start timing of the subframe / slot, a nominal symbol duration is assumed for symbols prior to the start of the PRS / SRS in the subframe / slot. The nominal symbol duration is the duration of the symbol in the gNB, as defined by 38.211. While the UE Rx-Tx time difference has been explained above, it should be understood that a similar procedure can be implemented in NTN entities to derive the NTN Rx-Tx time difference.

[0205] Referring to Figure 19, another specific example specific to UE Rx-Tx time differences is that legacy UE Rx-Tx time differences with extensions (as used in TN positioning) may be utilized. The UE reports the transmit SF / slot index j and SF / slot index i, or the difference between SF / slot index j and SF / slot index i and j, or the difference between SF / slot index i and j. The UE reports the Doppler of the DL signal along with each UE Rx-Tx time difference, and the LMF or gNB constitutes the minimum set of SRS from which UE Rx-Tx is measured and reported. Alternatively, the UE provides the gNB with the minimum set of SRS from which UE Rx-Tx is measured and reported in advance. When determining the start timing of a subframe / slot, a nominal symbol duration is assumed for symbols prior to the start of PRS / SRS in the subframe / slot. The nominal symbol duration is the duration of the symbol in the gNB, as defined by 38.211. As explained above regarding the UE Rx-Tx time difference, it should be understood that a similar procedure can be implemented in NTN entities to derive the NTN Rx-Tx time difference.

[0206] Referring to Figure 19, another specific example unique to UE Rx-Tx time lags shows that both the new type (Type 2) UE Rx-Tx time lag and the legacy UE Rx-Tx time lag can be supported. In this case, either the UE or the LMF indicates which type should be reported (for example, based on UE capabilities). While the UE Rx-Tx time lag has been explained above, it will be understood that a similar procedure can be implemented in NTN entities to derive the NTN Rx-Tx time lag.

[0207] In the embodiments for carrying out the above invention, it will be seen that different features are grouped together in the examples. This form of disclosure should not be understood as an intention that the exemplary clauses have more features than are explicitly stated within each clause. Rather, the various embodiments of this disclosure may contain fewer features than all the features of the individual exemplary clauses disclosed. Accordingly, the following clauses should be considered as incorporated into the description, and each clause may be valid on its own as a separate example. Each dependent clause may refer within itself to a particular combination with one of the other clauses, but the embodiments (one or more) of that dependent clause are not limited to that particular combination. It will be understood that other exemplary clauses may also contain combinations of embodiments (one or more) of dependent clauses with the subject matter of any other dependent clause or independent clause, or any combination of features with other dependent clauses and independent clauses. The various embodiments disclosed herein explicitly include certain combinations (e.g., contradictory embodiments such as defining an element as both an electrical insulator and an electrical conductor) unless it is explicitly stated or easily inferred that such combinations are not intended. Furthermore, even if a clause is not directly subordinate to an independent clause, it is intended that the form of the clause may be included in any other independent clause.

[0208] Implementation examples are described in the following numbered clauses.

[0209] Clause 1. A method for operating user equipment (UE), comprising: receiving a downlink positioning reference signal (DL-PRS) from a non-terrestrial network (NTN) entity in a first symbol of a downlink timing period; transmitting an uplink sounding reference signal (UL-SRS) to an NTN entity in a second symbol of an uplink timing period; and transmitting a measurement report containing sufficient information to determine (i) the UE receive-transmit (Rx-Tx) time difference between a first timestamp corresponding to the start of a downlink timing period and a second timestamp corresponding to the start of an uplink timing period, (ii) the first timestamp, and (iii) the second timestamp, wherein the start of a downlink timing period is based on one or more assumptions associated with the symbol durations of one or more symbols preceding the first symbol of the downlink timing period.

[0210] Clause 2. The method according to Clause 1, wherein the downlink timing period is a downlink slot, downlink subframe, or downlink symbol, and the uplink timing period is an uplink slot, uplink subframe, or uplink symbol.

[0211] Clause 3. The method according to Clause 2, wherein the timestamp granularity associated with the first timestamp, the second timestamp, or both corresponds to the respective granularity associated with the downlink timing period, the uplink timing period, or both.

[0212] Clause 4. The method according to any one of Clauses 1 to 3, wherein the DL-PRS instance associated with DL-PRS is among a subset of DL-PRS instances associated with DL-PRS resource configuration for UE position estimation sessions, and / or the UL-SRS instance associated with UL-SRS is among a subset of UL-SRS instances associated with UL-SRS resource configuration for UE position estimation sessions.

[0213] Clause 5. The method described in Clause 4, wherein a subset of DL-PRS instances and / or a subset of UL-SRS instances are comprised of Location Management Functions (LMF) or Wireless Network Components, or the subset of DL-PRS instances and / or a subset of UL-SRS instances are indicated or required by the UE.

[0214] Clause 6. The method of any of Clauses 1 to 5, wherein one or more assumptions include the assumption that the symbol duration of one or more symbols preceding the first symbol in the downlink timing period corresponds to a predefined symbol duration based on a zero-Doppler state.

[0215] Clause 7. The method according to any one of Clauses 1 to 6, wherein the information includes a UE Rx-Tx time difference and a first timestamp, or the information includes a UE Rx-Tx time difference and a second timestamp, or the information includes a UE Rx-Tx time difference, a first timestamp, and a second timestamp, or the information includes a UE Rx-Tx time difference, Doppler information associated with DL-PRS, and a first timestamp, or the information includes a UE Rx-Tx time difference, Doppler information associated with DL-PRS, and a second timestamp.

[0216] Clause 8. The method of any of Clauses 1 to 7, wherein the UL-SRS is associated with the earliest UL-SRS instance that follows the DL-PRS instance associated with the DL-PRS.

[0217] The method of any one of the clauses 1 to 8, further comprising: transmitting a UE Rx-Tx time difference measurement capability directive to a location estimation entity indicating the type of UE Rx-Tx time difference that the UE is capable of measuring and / or reporting for NTN; and receiving a measurement report configuration for information in response to the UE Rx-Tx time difference measurement capability directive for NTN.

[0218] Clause 10. The method of any of Clauses 1 to 9, wherein the measurement report further includes instructions for the configuration of the measurement report associated with the information.

[0219] Clause 11. A method for operating a non-terrestrial network (NTN) entity, comprising: receiving an uplink sounding reference signal (UL-SRS) from a user equipment (UE) at a first symbol of an uplink timing period; and transmitting a measurement report containing sufficient information to determine (i) the NTN entity receive-transmit (Rx-Tx) time difference between a first timestamp corresponding to the start of an uplink timing period and a second timestamp corresponding to the start of a downlink timing period, (ii) the first timestamp, and (iii) the second timestamp, wherein the start of the downlink timing period is based on one or more assumptions associated with the symbol durations of one or more symbols preceding the first symbol of the uplink timing period.

[0220] Clause 12. The method according to Clause 11, wherein the downlink timing period includes a downlink positioning reference signal (DL-RS), or the downlink timing period is associated with the same system subframe number and / or the same slot index as the uplink timing period.

[0221] Clause 13. The method of Clause 12, wherein the UL-SRS is associated with the earliest UL-SRS instance that is after the DL-RS instance associated with the DL-RS, or within the same system subframe number and / or the same slot index.

[0222] Clause 14. The method according to Clause 12 or 13, wherein DL-RS is DL positioning reference signal (DL-PRS) or DL ​​channel status information RS (DL-CSI-RS).

[0223] Clause 15. The method of any of Clauses 11 to 14, wherein the start of the uplink timing period is determined based on the timing of UL-SRS reception that begins within the uplink timing period.

[0224] Clause 16. The method according to any one of Clauses 11 to 15, wherein the downlink timing period is a downlink slot, downlink subframe, or downlink symbol, and the uplink timing period is an uplink slot, uplink subframe, or uplink symbol.

[0225] Clause 17. The method described in any of Clauses 11-16, wherein the UL-SRS instance associated with UL-SRS is within a subset of the UL-SRS instances associated with the UL-SRS resource configuration for the UE position estimation session.

[0226] Clause 18. The method described in Clause 17, wherein a subset of UL-SRS instances consists of a Location Management Function (LMF) or wireless network components, or a subset of UL-SRS instances is indicated or required by the UE.

[0227] Clause 19. The method of any of Clauses 11 to 18, wherein one or more assumptions include the assumption that the symbol duration of one or more symbols preceding the first symbol in the downlink timing period corresponds to a predefined symbol duration based on a zero-Doppler state.

[0228] Clause 20. The method according to any one of Clauses 11 to 19, wherein the information includes an NTN entity Rx-Tx time difference and a first timestamp, or the information includes an NTN entity Rx-Tx time difference and a second timestamp, or the information includes a first timestamp and a second timestamp.

[0229] Clause 21. A method for operating a location estimation entity, comprising: (i) a user equipment (UE) receive-transmit (Rx-Tx) time difference between a first timestamp corresponding to the start of a downlink timing period associated with the reception of a downlink positioning reference symbol (DL-PRS) from a non-terrestrial network (NTN) entity and a second timestamp corresponding to the start of an uplink timing period associated with the transmission of an uplink sounding reference signal (UL-SRS) to an NTN entity; (ii) receiving a measurement report containing sufficient information to determine the first timestamp and (iii) the second timestamp; and determining the round-trip time (RTT) between the UE and the NTN entity, at least in part, based on the information.

[0230] The method according to Clause 21, further comprising determining a subset of UL-SRS instances associated with the UL-SRS resource configuration for a UE location estimation session, and sending instructions to the UE and NTN entities, respectively, for the subset of UL-SRS instances to facilitate the transmission and measurement of one or more UL-SRS instances by the UE and NTN entities on the UL-SRS instances.

[0231] Clause 23. The method according to Clause 21 or 22, wherein the downlink timing period is a downlink slot, downlink subframe, or downlink symbol, and the uplink timing period is an uplink slot, uplink subframe, or uplink symbol.

[0232] Clause 24. The method according to any of Clauses 21 to 23, wherein the information includes a UE Rx-Tx time difference and a first timestamp, or the information includes a UE Rx-Tx time difference and a second timestamp, or the information includes a first timestamp and a second timestamp, or the information includes a UE Rx-Tx time difference and Doppler information associated with DL-PRS.

[0233] Clause 25. The method of any of Clauses 21-24, wherein the UL-SRS is associated with the earliest UL-SRS instance that follows the DL-PRS instance associated with the DL-PRS.

[0234] Clause 26. A method for operating a location estimation entity, comprising: (i) receiving a measurement report containing sufficient information to determine the NTN entity receive-transmit (Rx-Tx) time difference between a first timestamp corresponding to the start of an uplink timing period and a second timestamp corresponding to the start of a downlink timing period; (ii) the first timestamp; and (iii) the second timestamp; and determining the round-trip time (RTT) between the user equipment (UE) and the NTN entity, at least in part, based on the information.

[0235] Clause 27. The method according to Clause 26, wherein the downlink timing period includes a downlink positioning reference signal (DL-RS), or the downlink timing period is associated with the same system subframe number and / or the same slot index as the uplink timing period.

[0236] The method described in Clause 27, wherein the UL-SRS is associated with the earliest UL-SRS instance that is after the DL-RS instance associated with the DL-RS, or within the same system subframe number and / or the same slot index.

[0237] Clause 29. The method of any of Clauses 26 to 28, wherein the commencement of the uplink timing period is determined based on the timing of UL-SRS reception that commences within the uplink timing period.

[0238] Clause 30. The method according to any one of Clauses 26 to 29, wherein the downlink timing period is a downlink slot, downlink subframe, or downlink symbol, and the uplink timing period is an uplink slot, uplink subframe, or uplink symbol.

[0239] Clause 31. A user device (UE) comprising memory, at least one transceiver, and at least one processor communicatively coupled to the memory and at least one transceiver, wherein at least one processor is configured to receive a downlink positioning reference signal (DL-PRS) from a non-terrestrial network (NTN) entity via at least one transceiver at a first symbol of a downlink timing period, transmit an uplink sounding reference signal (UL-SRS) to an NTN entity via at least one transceiver at a second symbol of an uplink timing period, and transmit a measurement report via at least one transceiver containing sufficient information to determine (i) the UE receive-transmit (Rx-Tx) time difference between a first timestamp corresponding to the start of a downlink timing period and a second timestamp corresponding to the start of an uplink timing period, (ii) the first timestamp, and (iii) the second timestamp, wherein the start of a downlink timing period is based on one or more assumptions associated with the symbol duration of one or more symbols preceding the first symbol of the downlink timing period.

[0240] Clause 32. The UE described in Clause 31, wherein the downlink timing period is a downlink slot, downlink subframe, or downlink symbol, and the uplink timing period is an uplink slot, uplink subframe, or uplink symbol.

[0241] Clause 33. The UE described in Clause 32, wherein the timestamp granularity associated with the first timestamp, the second timestamp, or both corresponds to the respective granularity associated with the downlink timing period, the uplink timing period, or both.

[0242] A UE as described in any of Clauses 31-33, wherein the DL-PRS instance associated with the DL-PRS is among a subset of DL-PRS instances associated with the DL-PRS resource configuration for the UE's position estimation session, and / or the UL-SRS instance associated with the UL-SRS is among a subset of UL-SRS instances associated with the UL-SRS resource configuration for the UE's position estimation session.

[0243] Clause 35. A UE as described in Clause 34, in which a subset of DL-PRS instances and / or a subset of UL-SRS instances are comprised of a Location Management Function (LMF) or wireless network component, or in which a subset of DL-PRS instances and / or a subset of UL-SRS instances are indicated or required by the UE.

[0244] Clause 36. A UE described in any of Clauses 31 to 35, which includes one or more assumptions that the symbol duration of one or more symbols preceding the first symbol in the downlink timing period corresponds to a predefined symbol duration based on a zero-Doppler state.

[0245] Clause 37. A UE as described in any of Clauses 31 to 36, wherein the information includes a UE Rx-Tx time difference and a first timestamp, or the information includes a UE Rx-Tx time difference and a second timestamp, or the information includes a UE Rx-Tx time difference, a first timestamp, and a second timestamp, or the information includes a UE Rx-Tx time difference, Doppler information associated with DL-PRS, and a first timestamp, or the information includes a UE Rx-Tx time difference, Doppler information associated with DL-PRS, and a second timestamp.

[0246] Clause 38. A UE described in any of Clauses 31-37, where the UL-SRS is associated with the earliest UL-SRS instance that follows the DL-PRS instance associated with the DL-PRS.

[0247] A UE as described in any of Clauses 31 to 38, further configured to transmit a UE Rx-Tx time difference measurement capability instruction via at least one transceiver to a location estimation entity indicating the type of UE Rx-Tx time difference that the UE can measure and / or report for NTN, and to receive a measurement report configuration for information via at least one transceiver in response to the UE Rx-Tx time difference measurement capability instruction for NTN.

[0248] Clause 40. The measurement report further includes instructions for the configuration of the measurement report associated with the information, as set forth in any of Clauses 31 to 39.

[0249] Clause 41. A non-terrestrial network (NTN) entity comprising memory, at least one transceiver, and at least one processor communicatively coupled to the memory and at least one transceiver, wherein at least one processor is configured to receive an uplink sounding reference signal (UL-SRS) from a user equipment (UE) via at least one transceiver at a first symbol of an uplink timing period, and to transmit via at least one transceiver a measurement report containing sufficient information to determine (i) the NTN entity receive-transmit (Rx-Tx) time difference between a first timestamp corresponding to the start of an uplink timing period and a second timestamp corresponding to the start of a downlink timing period, (ii) the first timestamp, and (iii) the second timestamp, wherein the start of a downlink timing period is based on one or more assumptions associated with the symbol duration of one or more symbols preceding the first symbol of an uplink timing period.

[0250] Clause 42. An NTN entity as described in Clause 41, wherein the downlink timing period includes a downlink positioning reference signal (DL-RS), or the downlink timing period is associated with the same system subframe number and / or the same slot index as the uplink timing period.

[0251] Clause 43. An NTN entity as described in Clause 42, whose UL-SRS is associated with the earliest UL-SRS instance that is after the DL-RS instance associated with the DL-RS, or within the same system subframe number and / or the same slot index.

[0252] Clause 44. An NTN entity as described in Clause 42 or 43, wherein DL-RS is a DL positioning reference signal (DL-PRS) or DL ​​channel status information RS (DL-CSI-RS).

[0253] Clause 45. NTN as described in any of Clauses 41-44, where the commencement of the uplink timing period is determined based on the timing of UL-SRS reception that commences within the uplink timing period.

[0254] Clause 46. An NTN entity as described in any of Clauses 41-45, where the downlink timing period is a downlink slot, downlink subframe, or downlink symbol, and the uplink timing period is an uplink slot, uplink subframe, or uplink symbol.

[0255] Clause 47. An NTN entity as described in any of Clauses 41-46 whose UL-SRS instance associated with UL-SRS is among a subset of UL-SRS instances associated with a UL-SRS resource configuration for a UE position estimation session.

[0256] Clause 48. NTN entities as defined in Clause 47, in which a subset of UL-SRS instances consists of Location Management Functions (LMF) or Wireless Network Components, or in which a subset of UL-SRS instances is indicated or required by the UE.

[0257] An NTN entity as described in any of Clauses 41-48, wherein one or more assumptions include the assumption that the symbol duration of one or more symbols preceding the first symbol in the downlink timing period corresponds to a predefined symbol duration based on a zero-Doppler state.

[0258] Clause 50. An NTN entity as described in any of Clauses 41 to 49, wherein the information includes an NTN entity Rx-Tx time difference and a first timestamp, or the information includes an NTN entity Rx-Tx time difference and a second timestamp, or the information includes a first timestamp and a second timestamp.

[0259] Clause 51. A location estimation entity comprising memory, at least one transceiver, and at least one processor communicatively coupled to the memory and at least one transceiver, wherein the at least one processor is configured to receive via at least one transceiver a measurement report containing sufficient information to determine (i) a user equipment (UE) receive-transmit (Rx-Tx) time difference between (i) a first timestamp corresponding to the start of a downlink timing period associated with the reception of a downlink positioning reference symbol (DL-PRS) from a non-terrestrial network (NTN) entity and a second timestamp corresponding to the start of an uplink timing period associated with the transmission of an uplink sounding reference signal (UL-SRS) to an NTN entity, (ii) a first timestamp, and (iii) a round-trip time (RTT) between the UE and the NTN entity, at least in part on the information.

[0260] Clause 52. A location estimation entity as described in Clause 51, further configured to have at least one processor that determines a subset of UL-SRS instances associated with a UL-SRS resource configuration for a UE location estimation session, and transmits instructions for the subset of UL-SRS instances to the UE and NTN entities, respectively, via at least one transceiver, in order to facilitate the transmission and measurement of one or more UL-SRS instances on the UL-SRS instances by the UE and NTN entities.

[0261] Clause 53. A location estimation entity as described in Clause 51 or 52, wherein the downlink timing period is a downlink slot, downlink subframe, or downlink symbol, and the uplink timing period is an uplink slot, uplink subframe, or uplink symbol.

[0262] Clause 54. A location estimation entity as described in any of Clauses 51 to 53, wherein the information includes a UE Rx-Tx time difference and a first timestamp, or the information includes a UE Rx-Tx time difference and a second timestamp, or the information includes a first timestamp and a second timestamp, or the information includes a UE Rx-Tx time difference and Doppler information associated with DL-PRS.

[0263] Clause 55. A localization entity as described in any of Clauses 51-54, where the UL-SRS is associated with the earliest UL-SRS instance that follows the DL-PRS instance associated with the DL-PRS.

[0264] Clause 56. A location estimation entity comprising memory, at least one transceiver, and at least one processor communicatively coupled to the memory and at least one transceiver, wherein the at least one processor is configured to receive via at least one transceiver a measurement report containing sufficient information to determine (i) an NTN entity receive-transmit (Rx-Tx) time difference between a first timestamp corresponding to the start of an uplink timing period and a second timestamp corresponding to the start of a downlink timing period, (ii) a first timestamp, and (iii) a second timestamp, and to determine the round-trip time (RTT) between a user device (UE) and the NTN entity, at least in part on the information.

[0265] Clause 57. A position estimation entity as described in Clause 56, wherein the downlink timing period includes a downlink positioning reference signal (DL-RS), or the downlink timing period is associated with the same system subframe number and / or the same slot index as the uplink timing period.

[0266] Clause 58. A location estimation entity as described in Clause 57, where the UL-SRS is associated with the earliest UL-SRS instance that is after the DL-RS instance associated with the DL-RS, or within the same system subframe number and / or the same slot index.

[0267] Clause 59. A location estimation entity as described in any of Clauses 56-58, whose uplink timing period commencement is determined based on the timing of UL-SRS reception that commences within the uplink timing period.

[0268] Clause 60. The positioning entity according to any of Clauses 56 to 59, wherein the downlink timing period is a downlink slot, a downlink subframe, or a downlink symbol, and the uplink timing period is an uplink slot, an uplink subframe, or an uplink symbol.

[0269] Clause 61. A user equipment (UE) comprising: means for receiving a downlink positioning reference signal (DL-PRS) from a non-terrestrial network (NTN) entity in a first symbol of a downlink timing period; means for transmitting an uplink sounding reference signal (UL-SRS) to the NTN entity in a second symbol of an uplink timing period; and means for transmitting a measurement report including sufficient information to determine (i) a UE receive-transmit (Rx-Tx) time difference between a first timestamp corresponding to the start of the downlink timing period and a second timestamp corresponding to the start of the uplink timing period, (ii) the first timestamp, and (iii) the second timestamp, wherein the start of the downlink timing period is based on one or more assumptions associated with the symbol durations of one or more symbols preceding the first symbol of the downlink timing period.

[0270] Clause 62. The UE according to Clause 61, wherein the downlink timing period is a downlink slot, a downlink subframe, or a downlink symbol, and the uplink timing period is an uplink slot, an uplink subframe, or an uplink symbol.

[0271] Clause 63. The UE according to Clause 62, wherein the timestamp granularity associated with the first timestamp, the second timestamp, or both corresponds to the respective granularity associated with the downlink timing period, the uplink timing period, or both.

[0272] The UE according to any one of Clauses 61 to 63, wherein the DL-PRS instance associated with the DL-PRS is within a subset of the DL-PRS instances associated with the DL-PRS resource configuration for the UE's positioning session, and / or the UL-SRS instance associated with the UL-SRS is within a subset of the UL-SRS instances associated with the UL-SRS resource configuration for the UE's positioning session.

[0273] The UE according to Clause 64, wherein a subset of the DL-PRS instances and / or a subset of the UL-SRS instances are configured by a Location Management Function (LMF) or a wireless network component, or a subset of the DL-PRS instances and / or a subset of the UL-SRS instances are indicated or requested by the UE.

[0274] The UE according to any one of Clauses 61 to 65, wherein one or more assumptions include the assumption that the symbol durations of one or more symbols preceding the first symbol of the downlink timing period correspond to predefined symbol durations based on a zero Doppler state.

[0275] The UE according to any one of Clauses 61 to 66, wherein the information includes the UE Rx-Tx time difference and the first timestamp, or the information includes the UE Rx-Tx time difference and the second timestamp, or the information includes the UE Rx-Tx time difference, the first timestamp, and the second timestamp, or the information includes the UE Rx-Tx time difference, the Doppler information associated with the DL-PRS, and the first timestamp, or the information includes the UE Rx-Tx time difference, the Doppler information associated with the DL-PRS, and the second timestamp.

[0276] The UE according to any one of Clauses 61 to 67, wherein the UL-SRS is associated with the earliest UL-SRS instance that comes after the DL-PRS instance associated with the DL-PRS.

[0277] A UE according to any one of the clauses 61 to 68, further comprising: means for transmitting a UE Rx-Tx time difference measurement capability indication to a location estimation entity indicating the type of UE Rx-Tx time difference that the UE can measure and / or report for NTN; and means for receiving a measurement report configuration for information in response to the UE Rx-Tx time difference measurement capability indication for NTN.

[0278] Clause 70. The measurement report further includes instructions for the configuration of the measurement report associated with the information, as set forth in any of Clauses 61-69.

[0279] Clause 71. An NTN non-terrestrial network (NTN) entity comprising means for receiving an uplink sounding reference signal (UL-SRS) from a user equipment (UE) in a first symbol of an uplink timing period, and means for transmitting a measurement report containing (i) an NTN entity receive-transmit (Rx-Tx) time difference between an NTN entity receiving-transmit (Rx-Tx) time difference between an NTN entity receiving a first timestamp corresponding to the start of an uplink timing period and a second timestamp corresponding to the start of a downlink timing period, (ii) a first timestamp, and (iii) information sufficient to determine the second timestamp, wherein the start of a downlink timing period is based on one or more assumptions associated with the symbol duration of one or more symbols preceding the first symbol of an uplink timing period.

[0280] Clause 72. An NTN entity as described in Clause 71, wherein the downlink timing period includes a downlink positioning reference signal (DL-RS), or the downlink timing period is associated with the same system subframe number and / or the same slot index as the uplink timing period.

[0281] Clause 73. An NTN entity as described in Clause 72, whose UL-SRS is associated with the earliest UL-SRS instance that is after the DL-RS instance associated with the DL-RS, or within the same system subframe number and / or the same slot index.

[0282] Clause 74. An NTN entity as described in Clause 72 or 73, wherein DL-RS is a DL positioning reference signal (DL-PRS) or DL ​​channel status information RS (DL-CSI-RS).

[0283] Clause 75. An NTN entity as described in any of Clauses 71-74, whose commencement of the uplink timing period is determined based on the timing of UL-SRS reception that commences within the uplink timing period.

[0284] Clause 76. An NTN entity as described in any of Clauses 71 to 75, where the downlink timing period is a downlink slot, downlink subframe, or downlink symbol, and the uplink timing period is an uplink slot, uplink subframe, or uplink symbol.

[0285] Clause 77. An NTN entity as described in any of Clauses 71-76, whose UL-SRS instance associated with UL-SRS is among a subset of UL-SRS instances associated with the UL-SRS resource configuration for the UE's position estimation session.

[0286] Clause 78. NTN entities as defined in Clause 77, whose subset of UL-SRS instances consists of Location Management Functions (LMF) or Wireless Network Components, or whose subset of UL-SRS instances are indicated or required by the UE.

[0287] An NTN entity as described in any of Clauses 71-78, wherein one or more assumptions include the assumption that the symbol duration of one or more symbols preceding the first symbol in the downlink timing period corresponds to a predefined symbol duration based on a zero-Doppler state.

[0288] Clause 80. An NTN entity as described in any of Clauses 71 to 79, wherein the information includes an NTN entity Rx-Tx time difference and a first timestamp, or the information includes an NTN entity Rx-Tx time difference and a second timestamp, or the information includes a first timestamp and a second timestamp.

[0289] A location-estimating entity comprising: (i) a user equipment (UE) receive-transmit (Rx-Tx) time difference between a first timestamp corresponding to the start of a downlink timing period associated with the reception of a downlink positioning reference symbol (DL-PRS) from a non-terrestrial network (NTN) entity and a second timestamp corresponding to the start of an uplink timing period associated with the transmission of an uplink sounding reference signal (UL-SRS) to an NTN entity; (ii) a measurement report containing sufficient information to determine the first timestamp and (iii) the second timestamp; and a means for determining the round-trip time (RTT) between the UE and the NTN entity, at least in part, based on the information.

[0290] The location estimation entity described in Clause 81, further comprising means for determining a subset of UL-SRS instances associated with a UL-SRS resource configuration for a UE location estimation session, and means for transmitting instructions to the UE and NTN entities, respectively, of a subset of UL-SRS instances in order to facilitate the transmission and measurement of one or more UL-SRS instances on the UL-SRS instances by the UE and NTN entities.

[0291] Clause 83. The position estimation entity according to Clause 81 or 82, wherein the downlink timing period is a downlink slot, a downlink subframe, or a downlink symbol, and the uplink timing period is an uplink slot, an uplink subframe, or an uplink symbol.

[0292] Clause 84. The position estimation entity according to any one of Clauses 81 to 83, wherein the information includes the UE Rx-Tx time difference and the first timestamp, or the information includes the UE Rx-Tx time difference and the second timestamp, or the information includes the first timestamp and the second timestamp, or the information includes the UE Rx-Tx time difference and the Doppler information associated with the DL-PRS.

[0293] Clause 85. The position estimation entity according to any one of Clauses 81 to 84, wherein the UL-SRS is associated with the earliest UL-SRS instance after the DL-PRS instance associated with the DL-PRS.

[0294] Clause 86. A position estimation entity comprising means for receiving a measurement report including information sufficient to determine (i) the NTN entity receive-transmit (Rx-Tx) time difference between a first timestamp corresponding to the start of an uplink timing period and a second timestamp corresponding to the start of a downlink timing period, (ii) the first timestamp, and (iii) the second timestamp, and means for determining a round trip time (RTT) between a user equipment (UE) and the NTN entity based at least in part on the information.

[0295] Clause 87. The position estimation entity according to Clause 86, wherein the downlink timing period includes a downlink positioning reference signal (DL-RS), or the downlink timing period is associated with the same system subframe number and / or the same slot index as the uplink timing period.

[0296] Clause 88. A location estimation entity as described in Clause 87, where the UL-SRS is associated with the earliest UL-SRS instance that is after the DL-RS instance associated with the DL-RS, or within the same system subframe number and / or the same slot index.

[0297] Clause 89. A location estimation entity as described in any of Clauses 86-88, whose uplink timing period commencement is determined based on the timing of UL-SRS reception that commences within the uplink timing period.

[0298] Clause 90. A location estimation entity as described in any of Clauses 86-89, wherein the downlink timing period is a downlink slot, downlink subframe, or downlink symbol, and the uplink timing period is an uplink slot, uplink subframe, or uplink symbol.

[0299] Clause 91. A non-temporary computer-readable medium storing computer-executable instructions, wherein when the computer-executable instructions are executed by a user device (UE), the UE causes the UE to receive a downlink positioning reference signal (DL-PRS) from a non-terrestrial network (NTN) entity at a first symbol of a downlink timing period, transmit an uplink sounding reference signal (UL-SRS) to an NTN entity at a second symbol of an uplink timing period, transmit a measurement report containing (i) a UE receive-transmit (Rx-Tx) time difference between a first timestamp corresponding to the start of a downlink timing period and a second timestamp corresponding to the start of an uplink timing period, (ii) a first timestamp, and (iii) a second timestamp, and the start of a downlink timing period is based on one or more assumptions associated with the symbol durations of one or more symbols preceding the first symbol of the downlink timing period.

[0300] Clause 92. Non-temporary computer-readable media as described in Clause 91, wherein the downlink timing period is a downlink slot, downlink subframe, or downlink symbol, and the uplink timing period is an uplink slot, uplink subframe, or uplink symbol.

[0301] Clause 93. A non-temporary computer-readable medium as described in Clause 92, wherein the timestamp granularity associated with the first timestamp, the second timestamp, or both corresponds to the respective granularity associated with the downlink timing period, the uplink timing period, or both.

[0302] Non-temporary computer-readable media as described in any of Clauses 91-93, wherein a DL-PRS instance associated with a DL-PRS is among a subset of DL-PRS instances associated with a DL-PRS resource configuration for a UE position estimation session, and / or a UL-SRS instance associated with a UL-SRS is among a subset of UL-SRS instances associated with a UL-SRS resource configuration for a UE position estimation session.

[0303] Clause 95. Non-transient computer-readable media as described in Clause 94, wherein a subset of DL-PRS instances and / or a subset of UL-SRS instances are comprised of Location Management Functions (LMF) or wireless network components, or a subset of DL-PRS instances and / or a subset of UL-SRS instances are indicated or required by the UE.

[0304] Clause 96. A non-transient computer-readable medium as described in any of Clauses 91 to 95, wherein one or more assumptions include the assumption that the symbol duration of one or more symbols preceding the first symbol in the downlink timing period corresponds to a predefined symbol duration based on a zero-Doppler state.

[0305] Clause 97. Non-temporary computer-readable media as described in any of Clauses 91 to 96, wherein the information includes a UE Rx-Tx time difference and a first timestamp, or the information includes a UE Rx-Tx time difference and a second timestamp, or the information includes a UE Rx-Tx time difference, a first timestamp, and a second timestamp, or the information includes a UE Rx-Tx time difference, Doppler information associated with DL-PRS, and a first timestamp, or the information includes a UE Rx-Tx time difference, Doppler information associated with DL-PRS, and a second timestamp.

[0306] Clause 98. A non-temporary computer-readable medium as described in any of Clauses 91-97, to which the UL-SRS is associated with the earliest UL-SRS instance that follows the DL-PRS instance associated with the DL-PRS.

[0307] A non-temporary computer-readable medium as described in any of Clauses 91 to 98, further comprising: a computer-executable instruction, when executed by a UE, causing the UE to transmit a UE Rx-Tx time difference measurement capability instruction indicating the type of UE Rx-Tx time difference that the UE is capable of measuring and / or reporting for NTN to a location estimation entity; and, in response to the UE Rx-Tx time difference measurement capability instruction for NTN, causing the UE to receive a measurement reporting configuration for information.

[0308] Clause 100. A non-temporary computer-readable medium as described in any of Clauses 91-99, which further includes instructions for the configuration of the measurement report associated with the information.

[0309] Clause 101. A non-temporary computer-readable medium storing computer-executable instructions, wherein when a computer-executable instruction is executed by a non-terrestrial network (NTN) entity, the NTN entity causes the NTN entity to receive an uplink sounding reference signal (UL-SRS) from a user equipment (UE) at a first symbol of an uplink timing period, and to transmit a measurement report containing sufficient information to determine (i) the NTN entity receive-transmit (Rx-Tx) time difference between a first timestamp corresponding to the start of an uplink timing period and a second timestamp corresponding to the start of a downlink timing period, (ii) the first timestamp, and (iii) the second timestamp, based on one or more assumptions that the start of a downlink timing period is associated with the symbol duration of one or more symbols preceding the first symbol of an uplink timing period.

[0310] Clause 102. Non-transient computer-readable media as described in Clause 101, wherein the downlink timing period includes a downlink positioning reference signal (DL-RS), or the downlink timing period is associated with the same system subframe number and / or the same slot index as the uplink timing period.

[0311] Clause 103. Non-temporary computer-readable media as described in Clause 102, where the UL-SRS is associated with the earliest UL-SRS instance that is after the DL-RS instance associated with the DL-RS, or within the same system subframe number and / or the same slot index.

[0312] Clause 104. A non-temporary computer-readable medium as described in Clause 102 or 103, wherein DL-RS is a DL positioning reference signal (DL-PRS) or DL ​​channel status information RS (DL-CSI-RS).

[0313] Clause 105. A non-transient computer-readable medium as described in any of Clauses 101 to 104, wherein the commencement of the uplink timing period is determined based on the timing of the reception of UL-SRS that commences within the uplink timing period.

[0314] Clause 106. A non-temporary computer-readable medium as described in any of Clauses 101 to 105, wherein the downlink timing period is a downlink slot, downlink subframe, or downlink symbol, and the uplink timing period is an uplink slot, uplink subframe, or uplink symbol.

[0315] Clause 107. A non-temporary computer-readable medium as described in any of Clauses 101-106, in which the UL-SRS instance associated with the UL-SRS is among a subset of the UL-SRS instances associated with the UL-SRS resource configuration for the UE's position estimation session.

[0316] Clause 108. Non-transient computer-readable media as described in Clause 107, in which a subset of UL-SRS instances is comprised of Location Management Functions (LMF) or wireless network components, or in which a subset of UL-SRS instances is indicated or required by the UE.

[0317] Clause 109. A non-transient computer-readable medium as described in any of Clauses 101 to 108, wherein one or more assumptions include the assumption that the symbol duration of one or more symbols preceding the first symbol in the downlink timing period corresponds to a predefined symbol duration based on a zero-Doppler state.

[0318] Clause 110. Non-temporary computer-readable media as described in any of Clauses 101 to 109, in which the information includes an NTN entity Rx-Tx time difference and a first timestamp, or the information includes an NTN entity Rx-Tx time difference and a second timestamp, or the information includes a first timestamp and a second timestamp.

[0319] Clause 111. In one embodiment, a non-temporary computer-readable medium storing computer-executable instructions, the non-temporary computer-readable medium causing the location-estimating entity to receive a measurement report containing sufficient information to determine (i) a user equipment (UE) receive-transmit (Rx-Tx) time difference between (i) a first timestamp corresponding to the start of a downlink timing period associated with the reception of a downlink positioning reference symbol (DL-PRS) from a non-terrestrial network (NTN) entity and a second timestamp corresponding to the start of an uplink timing period associated with the transmission of an uplink sounding reference signal (UL-SRS) to an NTN entity, (ii) the first timestamp, and (iii) the second timestamp, and to determine the round-trip time (RTT) between the UE and the NTN entity, at least in part on the information.

[0320] Clause 112. A non-temporary computer-readable medium as described in Clause 111, further comprising a computer-executable instruction which, when executed by a position estimation entity, causes the position estimation entity to determine a subset of UL-SRS instances associated with a UL-SRS resource configuration for a UE position estimation session, and to transmit instructions for the subset of UL-SRS instances to the UE and NTN entities, respectively, to facilitate the transmission and measurement of one or more UL-SRS instances on the UL-SRS instances by the UE and NTN entities.

[0321] Clause 113. Non-temporary computer-readable media as described in Clause 111 or 112, wherein the downlink timing period is a downlink slot, downlink subframe, or downlink symbol, and the uplink timing period is an uplink slot, uplink subframe, or uplink symbol.

[0322] Clause 114. Non-temporary computer-readable media as described in any of Clauses 111 to 113, wherein the information includes a UE Rx-Tx time difference and a first timestamp, or the information includes a UE Rx-Tx time difference and a second timestamp, or the information includes a first timestamp and a second timestamp, or the information includes a UE Rx-Tx time difference and Doppler information associated with DL-PRS.

[0323] Clause 115. A non-temporary computer-readable medium as described in any of Clauses 111-114, to which the UL-SRS is associated with the earliest UL-SRS instance that follows the DL-PRS instance associated with the DL-PRS.

[0324] Clause 116. Non-temporary computer-readable medium for storing computer-executable instructions, wherein when the computer-executable instructions are executed by a location-estimating entity, the location-estimating entity receives a measurement report containing sufficient information to determine (i) the NTN entity receive-transmit (Rx-Tx) time difference between a first timestamp corresponding to the start of an uplink timing period and a second timestamp corresponding to the start of a downlink timing period, (ii) the first timestamp, and (iii) the second timestamp, and determines the round-trip time (RTT) between the user equipment (UE) and the NTN entity, at least in part on the information.

[0325] Clause 117. Non-transient computer-readable media as described in Clause 116, wherein the downlink timing period includes a downlink positioning reference signal (DL-RS), or the downlink timing period is associated with the same system subframe number and / or the same slot index as the uplink timing period.

[0326] Clause 118. Non-temporary computer-readable media as described in Clause 117, which is associated with the earliest UL-SRS instance that is after the DL-RS instance associated with the DL-RS, or within the same system subframe number and / or the same slot index.

[0327] Clause 119. Non-transient computer-readable media as described in any of Clauses 116 to 118, wherein the commencement of the uplink timing period is determined based on the timing of the reception of UL-SRS that commences within the uplink timing period.

[0328] Clause 120. Non-temporary computer-readable media as described in any of Clauses 116 to 119, wherein the downlink timing period is a downlink slot, downlink subframe, or downlink symbol, and the uplink timing period is an uplink slot, uplink subframe, or uplink symbol.

[0329] Those skilled in the art will understand that information and signals can be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description may be represented by voltage, electric current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0330] Furthermore, those skilled in the art will understand that various exemplary logic blocks, modules, circuits, and algorithmic steps described in relation to the embodiments disclosed herein may be implemented as electronic hardware, computer software, or a combination of both. To clearly demonstrate this hardware-software compatibility, various exemplary components, blocks, modules, circuits, and steps have been outlined above in relation to their functions. Whether such functions are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art may implement the described functions in various ways for specific applications, but such implementation decisions should not be construed as causing a departure from the scope of this disclosure.

[0331] Various exemplary logic blocks, modules, and circuits described in relation to the embodiments disclosed herein may be implemented or run using general-purpose processors, digital signal processors (DSPs), ASICs, field-programmable gate arrays (FPGAs), or other programmable logic devices, 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 alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors working with a DSP core, or any other such configuration.

[0332] The methods, sequences, and / or algorithms described in relation to the embodiments disclosed herein may be embodied in hardware directly, in software modules executed by a processor, or in a combination of both. 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 disks, removable disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from and write information to the storage medium. Alternatively, the storage medium may be integrated with the processor. The processor and storage medium may reside within an ASIC. The ASIC may reside within a user terminal (e.g., a UE). Alternatively, the processor and storage medium may reside within a user terminal as discrete components.

[0333] In one or more exemplary embodiments, the functions described may be implemented in hardware, software, firmware, or any combination thereof. Where implemented in software, these functions may be stored on or transmitted via computer-readable media as one or more instructions or codes. Computer-readable media include both computer storage media and communication media, including any media that facilitate the transfer of computer programs from one location to another. Storage media may be any available media accessible by a computer. Such computer-readable media may include, but are not limited to, RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other media accessible by a computer that can be used to carry or store desired program code in the form of instructions or data structures. Furthermore, any connection may be appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then those coaxial cables, fiber optic cables, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. As used herein, disks and discs include compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray® discs, where a disk typically reproduces data magnetically and a disc optically reproduces data using a laser.The above combinations should also be included within the scope of computer-readable media.

[0334] While the above disclosures represent exemplary aspects of the Disclosure, it should be noted that various changes and modifications can be made herein without departing from the scope of the Disclosure as defined by the appended claims. The functions, steps, and / or actions of the method claims in the aspects of the Disclosure described herein do not need to be performed in any particular order. Furthermore, elements of the Disclosure may be described or claimed in the singular, but the plural is intended unless a limitation to the singular is expressly stated.

Claims

1. A method for operating user equipment (UE), In the first symbol of the downlink timing period, a downlink positioning reference signal (DL-PRS) is received from a non-terrestrial network (NTN) entity, In the second symbol of the uplink timing period, an uplink sounding reference signal (UL-SRS) is transmitted to the NTN entity, (i) transmitting a measurement report containing sufficient information to determine the UE receive-transmit (Rx-Tx) time difference between a first timestamp corresponding to the start of the downlink timing period and a second timestamp corresponding to the start of the uplink timing period, (ii) the first timestamp, and (iii) the second timestamp. Includes, The start of the downlink timing period is based on one or more assumptions associated with the symbol duration of one or more symbols preceding the first symbol of the downlink timing period, method.

2. The downlink timing period is a downlink slot, a downlink subframe, or a downlink symbol. The uplink timing period is an uplink slot, an uplink subframe, or an uplink symbol. The method according to claim 1.

3. The method according to claim 2, wherein the timestamp granularity associated with the first timestamp, the second timestamp, or both corresponds to the respective granularity associated with the downlink timing period, the uplink timing period, or both.

4. The DL-PRS instance associated with the DL-PRS is among a subset of DL-PRS instances associated with the DL-PRS resource configuration for the UE's position estimation session, and / or The UL-SRS instance associated with the UL-SRS is among a subset of UL-SRS instances associated with the UL-SRS resource configuration for the UE's position estimation session. The method according to claim 1.

5. The subset of DL-PRS instances and / or the subset of UL-SRS instances are composed of location management functions (LMF) or wireless network components, or The subset of DL-PRS instances and / or the subset of UL-SRS instances as indicated or requested by the UE The method according to claim 4.

6. The method according to claim 1, wherein one or more assumptions include the assumption that the symbol duration of one or more symbols preceding the first symbol in the downlink timing period corresponds to a predefined symbol duration based on a zero-Doppler state.

7. The information includes the UE Rx-Tx time difference and the first timestamp, or The information includes the UE Rx-Tx time difference and the second timestamp, or The information includes the UE Rx-Tx time difference, a first timestamp, and a second timestamp, or The information includes the UE Rx-Tx time difference, the Doppler information associated with the DL-PRS, and the first timestamp, or The information includes the UE Rx-Tx time difference, the Doppler information associated with the DL-PRS, and the second timestamp. The method according to claim 1.

8. The method according to claim 1, wherein the UL-SRS is associated with the earliest UL-SRS instance that follows the DL-PRS instance associated with the DL-PRS.

9. Transmitting a UE Rx-Tx time difference measurement capability indication to the position estimation entity, which indicates the type of UE Rx-Tx time difference that the UE can measure and / or report for NTN, In response to the UE Rx-Tx time difference measurement capability instruction for NTN, the measurement report configuration for the information is received, The method according to claim 1, further comprising:

10. The method according to claim 1, wherein the measurement report further includes instructions for a measurement report configuration associated with the information.

11. A method for operating a non-terrestrial network (NTN) entity, In the first symbol of the uplink timing period, the uplink sounding reference signal (UL-SRS) is received from the user equipment (UE), (i) transmitting a measurement report containing sufficient information to determine the NTN entity receive-transmit (Rx-Tx) time difference between a first timestamp corresponding to the start of the uplink timing period and a second timestamp corresponding to the start of the downlink timing period, (ii) the first timestamp, and (iii) the second timestamp. Includes, The start of the downlink timing period is based on one or more assumptions associated with the symbol duration of one or more symbols preceding the first symbol of the uplink timing period, method.

12. The downlink timing period includes the downlink positioning reference signal (DL-RS), or The downlink timing period is associated with the same system subframe number and / or the same slot index as the uplink timing period. The method according to claim 11.

13. The method according to claim 12, wherein the UL-SRS is associated with the DL-RS instance that is after the DL-RS instance associated with the DL-RS, or with the earliest UL-SRS instance that is within the same system subframe number and / or the same slot index.

14. The method according to claim 12, wherein the DL-RS is a DL positioning reference signal (DL-PRS) or a DL channel status information RS (DL-CSI-RS).

15. The method according to claim 11, wherein the start of the uplink timing period is determined based on the reception timing of the UL-SRS that starts within the uplink timing period.

16. The downlink timing period is a downlink slot, a downlink subframe, or a downlink symbol. The uplink timing period is an uplink slot, an uplink subframe, or an uplink symbol. The method according to claim 11.

17. The method according to claim 11, wherein the UL-SRS instance associated with the UL-SRS is among a subset of UL-SRS instances associated with the UL-SRS resource configuration for the UE's position estimation session.

18. The subset of UL-SRS instances is comprised of a Location Management Function (LMF) or a Wireless Network component, or The subset of UL-SRS instances is indicated or requested by the UE. The method according to claim 17.

19. The method according to claim 11, wherein one or more assumptions include the assumption that the symbol duration of one or more symbols preceding the first symbol in the downlink timing period corresponds to a predefined symbol duration based on a zero-Doppler state.

20. The information includes the NTN entity Rx-Tx time difference and the first timestamp, or The information includes the NTN entity Rx-Tx time difference and the second timestamp, or The information includes the first timestamp and the second timestamp. The method according to claim 11.

21. A method for operating a location-estimating entity, (i) receiving a measurement report containing sufficient information to determine the first timestamp and the second timestamp, (ii) the first timestamp and (iii) the second timestamp, Based at least in part on the aforementioned information, the round-trip time (RTT) between the UE and the NTN entity is determined, Methods that include...

22. Determining a subset of UL-SRS instances associated with the UL-SRS resource configuration for the UE's position estimation session, To facilitate the transmission and measurement of one or more UL-SRS instances on the UL-SRS instance by the UE and the NTN entity, instructions for the subset of UL-SRS instances are transmitted to the UE and the NTN entity, respectively. The method according to claim 21, further comprising:

23. The downlink timing period is a downlink slot, a downlink subframe, or a downlink symbol. The uplink timing period is an uplink slot, an uplink subframe, or an uplink symbol. The method according to claim 21.

24. The information includes the UE Rx-Tx time difference and the first timestamp, or The information includes the UE Rx-Tx time difference and the second timestamp, or The information includes the first timestamp and the second timestamp, or The information includes the UE Rx-Tx time difference and the Doppler information associated with the DL-PRS. The method according to claim 21.

25. The method according to claim 21, wherein the UL-SRS is associated with the earliest UL-SRS instance that follows the DL-PRS instance associated with the DL-PRS.

26. A method for operating a location-estimating entity, (i) receiving a measurement report containing sufficient information to determine the NTN entity receive-transmit (Rx-Tx) time difference between a first timestamp corresponding to the start of the uplink timing period and a second timestamp corresponding to the start of the downlink timing period, (ii) the first timestamp, and (iii) the second timestamp. Based at least in part on the aforementioned information, the round-trip time (RTT) between the user equipment (UE) and the NTN entity is determined, Methods that include...

27. The downlink timing period includes the downlink positioning reference signal (DL-RS), or The downlink timing period is associated with the same system subframe number and / or the same slot index as the uplink timing period. The method according to claim 26.

28. The method according to claim 27, wherein the UL-SRS is associated with the DL-RS instance that is after the DL-RS instance associated with the DL-RS, or with the earliest UL-SRS instance that is within the same system subframe number and / or the same slot index.

29. The method according to claim 26, wherein the start of the uplink timing period is determined based on the reception timing of the UL-SRS that starts within the uplink timing period.

30. The downlink timing period is a downlink slot, a downlink subframe, or a downlink symbol. The uplink timing period is an uplink slot, an uplink subframe, or an uplink symbol. The method according to claim 26.

Images