Method of operation of a user equipment (UE), method of operation of a non-terrestrial network entity (NTN), and, methods of operation of a position estimation entity

Description

1 / 158 “METHOD OF OPERATION OF A USER EQUIPMENT (UE), METHOD OF OPERATION OF A NON-TERRESTRIAL NETWORK ENTITY (NTN), AND METHODS OF OPERATION OF AN ESTIMATE ENTITY "POSITION" BACKGROUND OF THE DISCLOSURE 1. Field of dissemination

[0001] The aspects of disclosure generally refer to wireless communications. 2. Description of the related technique

[0002] Wireless communication systems have developed over several generations, including a first-generation (1G) analog wireless telephone service, a second-generation (2G) digital wireless telephone service (including 2.5G and 2.75G interim networks), a third-generation (3G) wireless service with high-speed internet and data capabilities, and a fourth-generation (4G) service (e.g., long-term evolution (LTE) or WiMax). Currently, there are many different types of wireless communication systems in use, including cellular systems and personal communications service (PCS) systems.Examples of well-known cellular systems include the analog cellular system of the Advanced Mobile Phone System (AMPS), and digital cellular systems based on Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), and Time Division Multiple Access (TDMA). Petition 870250086012, dated 09 / 23 / 2025, page 10 / 362 2 / 158 global for mobile communications (GSM - global system for mobile communications) etc.

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

[0004] A simplified summary relating to one or more aspects disclosed in the present invention is presented below. Therefore, the following summary should not be considered an extensive overview relating to all aspects contemplated, nor should the following summary be considered to identify key or critically important elements relating to all aspects contemplated, or to delineate the scope associated with any particular aspect. Consequently, the following summary has the sole purpose of presenting certain concepts relating to one or more aspects related to the disclosed mechanisms. Petition 870250086012, dated 09 / 23 / 2025, p. 11 / 362 3 / 158 of the present invention in a simplified form to precede the detailed description presented below.

[0005] In one aspect, a method of operation of a user equipment (UE) includes receiving a downlink positioning reference signal (DL-PRS) from a non-terrestrial network entity (NTN) on a first symbol of a downlink timing period; transmitting an uplink sounding reference signal (UL-SRS) to the NTN entity on a second symbol of an uplink timing period;and transmit a measurement report comprising sufficient information to determine (i) a receive-transmit (Rx-Tx) UE 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 duration for one or more symbols preceding the first symbol of the downlink timing period.

[0006] In one aspect, a method of operation of a non-terrestrial network entity (NTN) includes receiving an uplink probe reference signal (UL-SRS) from a user equipment (UE) at a first symbol of an uplink timing period; and transmitting a measurement report comprising information Petition 870250086012, dated 09 / 23 / 2025, page 12 / 362 4 / 158 sufficient 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) to the first timestamp and (iii) to the second timestamp, wherein the start of the downlink timing period is based on one or more assumptions associated with the symbol duration for one or more symbols preceding the first symbol of the uplink timing period.

[0007] In one aspect, a method of operation of a position estimation entity includes receiving a measurement report comprising 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 entity (NTN) and a second timestamp corresponding to the start of an uplink timing period associated with the transmission of an uplink probing reference signal (UL-SRS) to the NTN entity, (ii) to the first timestamp and (iii) to the second timestamp; and to determine a round-trip time (RTT) between the UE and the NTN entity based, at least in part, on the information.

[0008] In one aspect, a method of operation of a position estimation entity includes receiving a report Petition 870250086012, dated 09 / 23 / 2025, p. 13 / 362 5 / 158 measurement comprising sufficient information to determine (i) a receive-transmit (Rx-Tx) time difference of an NTN entity 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 a round-trip time (RTT) between a user equipment (UE) and the NTN entity based, at least in part, on the information.

[0009] In one aspect, a user equipment (UE) includes a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and to the at least one transceiver, wherein the at least one processor is configured to: receive, through the at least one transceiver, a downlink positioning reference signal (DL-PRS) from a non-terrestrial network entity (NTN) on a first symbol of a downlink timing period; transmit, through the at least one transceiver, an uplink polling reference signal (UL-SRS) to the NTN entity on a second symbol of an uplink timing period; and transmit, through the at least one transceiver, a measurement report comprising sufficient information to determine (i) a receive-transmit (Rx-Tx) time difference of The EU is defined as the time between a first timestamp corresponding to the start of the downlink timing period and a second timestamp corresponding to the start of the Petition 870250086012, dated 09 / 23 / 2025, p. 14 / 362 6 / 158 uplink timing period, (ii) at the first time stamp and (iii) at the second time stamp, wherein the start of the downlink timing period is based on one or more assumptions associated with the symbol duration for one or more symbols preceding the first symbol of the downlink timing period.

[0010] In one aspect, a non-terrestrial network (NTN) entity includes a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and to the at least one transceiver, wherein the at least one processor is configured to: receive, through the at least one transceiver, an uplink polling reference signal (UL-SRS) from a user equipment (UE) at a first symbol of an uplink timing period;and transmit, through at least one transceiver, a measurement report comprising 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) 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 duration for one or more symbols preceding the first symbol of the uplink timing period.

[0011] In one aspect, a position estimation entity includes a memory; at least one transceiver; and Petition 870250086012, dated 09 / 23 / 2025, p. 15 / 362 7 / 158 at least one processor communicatively coupled to memory and at least one transceiver, wherein the at least one processor is configured to: receive, through the at least one transceiver, a measurement report comprising 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 receipt of a downlink positioning reference symbol (DL-PRS) from a non-terrestrial network entity (NTN) and a second timestamp corresponding to the start of an uplink timing period associated with the transmission of an uplink probing reference signal (UL-SRS) to the NTN entity, (ii) to the first timestamp and (iii) to the second timestamp;and to determine a round-trip travel time (RTT) between the EU and the NTN entity based, at least in part, on the information.

[0012] In one aspect, a position estimation entity includes a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and to the at least one transceiver, wherein the at least one processor is configured to: receive, through the at least one transceiver, a measurement report comprising sufficient information to determine (i) a receive-transmit (Rx-Tx) time difference of an NTN entity 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) to Petition 870250086012, dated 09 / 23 / 2025, p. 16 / 362 8 / 158 first time stamp and (iii) to the second time stamp; and determine a round-trip travel time (RTT) between a user equipment (UE) and the NTN entity based, at least in part, on the information.

[0013] In one aspect, a user equipment (UE) includes means for receiving a downlink positioning reference signal (DL-PRS) from a non-terrestrial network entity (NTN) on a first symbol of a downlink timing period; means for transmitting an uplink probing reference signal (UL-SRS) to the NTN entity on a second symbol of an uplink timing period;and means for transmitting a measurement report comprising sufficient information to determine (i) a UE (Rx-Tx) receive-transmit 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) to the first timestamp and (iii) to the second timestamp, wherein the start of the downlink timing period is based on one or more assumptions associated with the symbol duration for one or more symbols preceding the first symbol of the downlink timing period.

[0014] In one aspect, a non-terrestrial network entity (NTN) includes means for receiving an uplink probe 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 comprising information Petition 870250086012, dated 09 / 23 / 2025, page 17 / 362 9 / 158 sufficient 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) to the first timestamp and (iii) to the second timestamp, wherein the start of the downlink timing period is based on one or more assumptions associated with the symbol duration for one or more symbols preceding the first symbol of the uplink timing period.

[0015] In one aspect, a position estimation entity includes means for receiving a measurement report comprising 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 receiving a downlink positioning reference symbol (DL-PRS) from a non-terrestrial network entity (NTN) and a second timestamp corresponding to the start of an uplink timing period associated with transmitting an uplink probing reference signal (UL-SRS) to the NTN entity, (ii) to the first timestamp and (iii) to the second timestamp; and means for determining a round-trip time (RTT) between the UE and the NTN entity based, at least in part, on the information.

[0016] In one aspect, a position estimation entity includes means for receiving a measurement report. Petition 870250086012, dated 09 / 23 / 2025, p. 18 / 362 10 / 158 comprising sufficient information to determine (i) a receive-transmit (Rx-Tx) time difference of an NTN entity 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 to determine a round-trip time (RTT) between a user equipment (UE) and the NTN entity based, at least in part, on the information.

[0017] In one aspect, a non-transient, computer-readable medium that stores computer-executable instructions which, when executed by a user equipment (UE), cause the UE to: receive a downlink positioning reference signal (DL-PRS) from a non-terrestrial network entity (NTN) on a first symbol of a downlink timing period; transmit an uplink polling reference signal (UL-SRS) to the NTN entity on a second symbol of an uplink timing period;and transmit a measurement report comprising 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 on which the start of the downlink timing period is based; Petition 870250086012, dated 09 / 23 / 2025, p. 19 / 362 11 / 158 in one or more assumptions associated with the symbol duration for one or more symbols preceding the first symbol of the downlink timing period.

[0018] In one aspect, a non-transient, computer-readable medium that stores computer-executable instructions which, when executed by a non-terrestrial network entity (NTN), cause the NTN entity to: receive an uplink polling reference signal (ULSRS) from a user equipment (UE) at a first symbol of an uplink timing period;and transmit a measurement report comprising 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) 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 duration for one or more symbols preceding the first symbol of the uplink timing period.

[0019] In one aspect, a non-transient, computer-readable medium that stores computer-executable instructions which, when executed by a position estimation entity, cause the position estimation entity to: receive a measurement report comprising sufficient information to determine (i) a user equipment (UE) receive-transmit (Rx-Tx) time difference between a first timestamp. Petition 870250086012, dated 09 / 23 / 2025, page 20 / 362 12 / 158 corresponding to the start of a downlink timing period associated with receiving a downlink positioning reference symbol (DL-PRS) from a non-terrestrial network entity (NTN) and a second timestamp corresponding to the start of an uplink timing period associated with transmitting an uplink probing reference signal (UL-SRS) to the NTN entity, (ii) to the first timestamp and (iii) to the second timestamp; and determine a round-trip time (RTT) between the UE and the NTN entity based, at least in part, on the information.

[0020] In one aspect, a non-transient computer-readable medium that stores computer-executable instructions that, when executed by a position estimation entity, cause the position estimation entity to: receive a measurement report comprising sufficient information to determine (i) a receive-transmit (Rx-Tx) time difference from the NTN entity 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 determine a round-trip time (RTT) between a user equipment (UE) and the NTN entity based, at least in part, on the information.

[0021] Other objectives and advantages associated with the aspects disclosed in the present invention will become apparent to those skilled in the art based on the accompanying drawings and detailed description. Petition 870250086012, dated 09 / 23 / 2025, page 21 / 362 13 / 158 BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The attached drawings are presented to assist in describing various aspects of the disclosure and are provided for illustrative purposes only, and not to limit them.

[0023] Figure 1 illustrates an example wireless communication system, according to disclosure aspects.

[0024] Figures 2A, 2B and 2C illustrate example wireless network structures, according to disclosure aspects.

[0025] Figures 3A, 3B, and 3C are simplified block diagrams of various sample component aspects that can be employed in a user equipment (UE), a base station, and a network entity, respectively, and configured to support communications as taught in the present invention.

[0026] Figure 4 is a diagram illustrating an example framework structure, according to disclosure aspects.

[0027] Figure 5 is a diagram illustrating various downlink channels in an example downlink slot, according to aspects of the disclosure.

[0028] Figure 6 is a diagram of an example positioning reference signal (PRS) configuration for PRS transmissions from a given base station, according to aspects of the disclosure.

[0029] Figure 7 is a diagram illustrating various uplink channels within an example uplink slot, according to aspects of the disclosure. Petition 870250086012, dated 09 / 23 / 2025, page 22 / 362 14 / 158

[0030] Figure 8 illustrates examples of various positioning methods supported in New Radio (NR), according to aspects of dissemination.

[0031] Figure 9 is a diagram illustrating an example round-trip travel time (RTT) procedure for determining a UE location, in accordance with disclosure aspects.

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

[0033] Figure 11 illustrates a single and multi-RTT satellite technique, according to aspects of the disclosure.

[0034] Figure 12 illustrates a terrestrial network (TN) timing, in accordance with aspects of this disclosure.

[0035] Figure 13 illustrates a UE timing scenario for Tue-rx-tx, according to aspects of the disclosure.

[0036] Figure 14 illustrates a gNB timing scenario for Tue-rx-tx, according to aspects of the disclosure.

[0037] Figure 15 illustrates an exemplary communication process, according to one aspect of dissemination.

[0038] Figure 16 illustrates an exemplary communication process, according to one aspect of dissemination. Petition 870250086012, dated 09 / 23 / 2025, p. 23 / 362 15 / 158

[0039] Figure 17 illustrates an exemplary communication process, according to one aspect of dissemination.

[0040] Figure 18 illustrates an exemplary communication process, according to one aspect of dissemination.

[0041] Figure 19 illustrates an example implementation of the processes in Figures 15 to 18, respectively, according to aspects of disclosure. DETAILED DESCRIPTION

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

[0043] Several aspects generally refer to differences in reception and transmission (Rx-Tx) time between a UE and a non-terrestrial network entity (NTN) (e.g., LEO satellite) in various scenarios. Some aspects refer more specifically to UE RxTx time differences, NTN Rx-Tx time differences, or both.

[0044] Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, such aspects may provide several technical advantages, such as overcoming some or all of the problems that may arise if terrestrial network (TN) timing techniques for Rx-Tx time differences are Petition 870250086012, dated 09 / 23 / 2025, p. 24 / 362 16 / 158 mirrored for NTN positioning (e.g., more accurate subframe start time, a coupled Rx-Tx time difference report by the UE and the NTN entity, and so on), which can in turn improve the accuracy of the UE position estimate and / or the accuracy of the UE position verification.

[0045] The words exemplifying and / or exemplary are used in the present invention to mean serving as an example, instance, or illustration. Any aspect described in the present invention as exemplifying and / or exemplary should not necessarily be interpreted as preferential or advantageous in relation to other aspects. Similarly, the term aspects of the disclosure does not require that all aspects of the disclosure include the attribute, advantage, or mode of operation discussed.

[0046] Those skilled in the art will recognize that the information and signals described below can be represented using any one of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the description below can be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof, depending in part on the particular application, in part on the desired design, in part on the corresponding technology, etc.

[0047] Additionally, many aspects are described in terms of sequences of actions to be performed, for example, by elements of a computing device. It will be recognized that several actions described in Petition 870250086012, dated 09 / 23 / 2025, page 25 / 362 17 / 158 The present invention may be implemented by specific circuits (for example, by application-specific integrated circuits (ASICs)), by program instructions that are executed by one or more processors, or by a combination of both. Additionally, the sequence(s) of actions described in the present invention may be considered as fully incorporated in any form of non-transient computer-readable storage medium that stores a corresponding set of computer instructions which, upon execution, would cause, or instruct, an associated processor of a device to perform the functionalities described in the present invention. Thus, the various aspects of the disclosure may be embodied in several different forms, all of which have been contemplated as being within the scope of the claimed subject matter.Furthermore, for each of the aspects described in the present invention, the corresponding form of any of these aspects can be described in the present invention as, for example, logic configured to perform the described action.

[0048] As used in the present invention, the terms user equipment (UE) and base station are not intended to be specific or otherwise limited to any particular radio access technology (RAT), except where otherwise specified. In general, a UE can be any wireless communication device (e.g., a mobile phone, a router, a tablet computer, a laptop computer, a location device, etc.). Petition 870250086012, dated 09 / 23 / 2025, page 26 / 362 18 / 158 consumer assets, a wearable device (e.g., smartwatch, glasses, augmented reality (AR) / virtual reality (VR) headset, etc.), vehicle (e.g., automobile, motorcycle, bicycle, etc.), Internet of Things (IoT) device, etc.) used by a user for communication via a wireless communications network. A UE may be mobile or may (e.g., at certain times) be stationary and may communicate with a radio access network (RAN). As used in the present invention, 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, a mobile device, mobile terminal, mobile station or variations thereof.In general, UEs can communicate with a core network via a RAN, and through the core network, UEs can be connected 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 UEs, such as through wired access networks, wireless local area networks (WLANs) (for example, based on the descriptive report of the Institute of Electrical and Electronics Engineers (IEEE) 802.11, etc.), and so on. [004 9] A base station can operate according to one of several RATs in communication with UEs, depending on the network in which it is implemented and can alternatively be called an access point (AP), a network node, Petition 870250086012, dated 09 / 23 / 2025, page 27 / 362 19 / 158 a NodeB, an evolved NodeB (eNB), a next-generation eNB (ng-eNB), a New Radio (NR) NodeB (also called gNB or gNodeB), etc. A base station can be used primarily to support wireless access by UEs, including supporting data, voice, and / or signaling connections for the supported UEs. In some systems, a base station may provide purely edge node signaling functions, while in other systems it may provide additional network control and / or management functions. A communication link through which UEs can send signals to a base station is called an uplink (UL) channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, etc.).A communication link through which the base station can send signals to UEs is called a downlink (DL) channel or a direct link channel (e.g., a paging channel, a control channel, a broadcast channel, a direct traffic channel, etc.). As used in the present invention, the term traffic channel (TCH traffic channel) can refer to an uplink / reverse link or a downlink / direct link traffic channel.

[0050] The term base station may refer to a single physical transmission-reception point (TRP) or to multiple physical TRPs that may or may not be colocated. For example, when the term base station refers to a single physical TRP, the physical TRP may be an antenna of the base station corresponding to a cell (or several cell sectors) of the base station. When the term base station refers to multiple colocated physical TRPs, the physical TRPs may be an arrangement of Petition 870250086012, dated 09 / 23 / 2025, p. 28 / 362 20 / 158 antennas (for example, as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming) from the base station. When the term base station refers to multiple non-co-located physical TRPs, the physical TRPs may be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transport medium) or a remote radio head (RRH) (a remote base station connected to a serving base station). Alternatively, the non-co-located physical TRPs may be the serving base station receiving the measurement report from the UE and a neighboring base station whose reference radio frequency (RF) signals the UE is measuring.Because a TRP is the point from which a base station transmits and receives wireless signals, as used in the present invention, references to transmission from or reception at a base station should be understood as referring to a particular TRP of the base station.

[0051] In some implementations that support UE positioning, a base station may not support wireless access by UEs (e.g., it may not support data, voice, and / or signaling connections to UEs), but may instead transmit reference signals to UEs to be measured by the UEs, and / or may receive and measure signals transmitted by the UEs. Such a base station may be referred to as a positioning beacon (e.g., when transmitting signals to UEs) and / or as a location measurement unit (e.g., when receiving and measuring signals from UEs). Petition 870250086012, dated 09 / 23 / 2025, page 29 / 362 21 / 158

[0052] An RF signal comprises an electromagnetic wave with a given frequency that carries information through the space between a transmitter and a receiver. As used in the present invention, a transmitter may transmit a single RF signal or multiple RF signals to a receiver. However, the receiver may receive multiple RF signals corresponding to each transmitted RF signal due to the propagation characteristics of RF signals through multipath channels. The same RF signal transmitted over different paths between the transmitter and the receiver may be called a multipath RF signal. As used in the present invention, an RF signal may also be called a wireless signal or simply a signal, where it is evident from the context that the term signal refers to a wireless signal or an RF signal.

[0053] Figure 1 illustrates an example 100 wireless communication system, according to aspects of the disclosure. The 100 wireless communication system (which may also be called a wireless wide area network (WWAN)) may include multiple 102 base stations (marked as BS) and multiple 104 UEs. The 102 base stations may include macrocell base stations (high-power cellular base stations) and / or small cell base stations (low-power cellular base stations). In one aspect, the macrocell base stations may include eNBs and / or ng-eNBs, where the 100 wireless communication system corresponds to an LTE network, or gNBs where the 100 wireless communication system corresponds to an NR network, or a Petition 870250086012, dated 09 / 23 / 2025, page 30 / 362 22 / 158 combination of both, and small cell base stations may include femtocells, picocells, microcells, etc.

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

[0055] In addition to other functions, 102 base stations can perform functions related to one or more of the following: user data transfer, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), intercellular interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, positioning, and alert message delivery.Base stations 102 can communicate with each other directly or indirectly (for example, via EPC / 5GC) through backhaul links 134, which can be wired or wireless.

[0056] Base stations 102 can communicate wirelessly with UEs 104. Each base station 102 can provide communication coverage for a respective geographic coverage area 110. In one aspect, one or more cells can be supported by a base station 102 in each geographic coverage area 110. A cell is a logical communication entity used for communication with a base station (e.g., through a frequency resource, called carrier frequency, component carrier, carrier, band, or the like), and may be associated with a Petition 870250086012, dated 09 / 23 / 2025, p. 32 / 362 24 / 158 identifier (e.g., a physical cell identifier (PCI), an enhanced cell identifier (ECI), a virtual cell identifier (VCI), a cell global identifier (CGI), etc.) to distinguish cells operating via the same or different carrier frequency. In some cases, different cells may be configured according to different protocol types (e.g., machine-type communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or others) that may provide access for different UE types. Because a cell is supported by a specific base station, the term cell may refer to one or both of the logical communication entities and the base station that supports it, depending on the context.Furthermore, due to the fact that a TRP is typically the physical transmission point of a cell, the terms cell and TRP can be used interchangeably. In some cases, the term cell may also refer to a geographic coverage area of ​​a base station (e.g., a sector), insofar as a carrier frequency can be detected and used for communication in some portion of the geographic coverage areas 110.

[0057] Although the geographic coverage areas 110 of the neighboring macrocell base station 102 may partially overlap (e.g., in a handover region), some of the geographic coverage areas 110 may be substantially overlapped by a coverage area Petition 870250086012, dated 09 / 23 / 2025, page 33 / 362 25 / 158 larger geographic area 110. For example, a small cell base station 102' (marked as SC, short for small cell) may have a geographic coverage area 110' that substantially overlaps the geographic coverage area 110 of one or more macrocell base stations 102. A network that includes 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), which may provide services to a restricted group known as a closed subscriber group (CSG).

[0058] The 120 communication links between base stations 102 and UEs 104 may include uplink (also called reverse link) transmissions from a UE 104 to a base station 102 and / or downlink (DL) (also called forward link) transmissions from a base station 102 to a UE 104. The 120 communication links may use MIMO antenna technology, which includes spatial multiplexing, beamforming, and / or transmission diversity. The 120 communication links may be over one or more carrier frequencies. Carrier allocation may be asymmetrical with respect to the downlink and uplink (e.g., a greater or lesser number of carriers may be allocated to the downlink than to the uplink).

[0059] The wireless communications system 100 may additionally include a wireless local area network (WLAN) access point (AP) 150 communicating with WLAN stations (STAs) 152 via communication links 154 in an unlicensed frequency spectrum (e.g., 5 Petition 870250086012, dated 09 / 23 / 2025, page 34 / 362 26 / 158 GHz). When communicating in an unlicensed frequency spectrum, WLAN 152 STAs and / or WLAN 150 APs may perform a Clear Channel Assessment (CCA) or Listen Before Talk (LBT) procedure before communication to determine if the channel is available.

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

[0061] The wireless communication system 100 may additionally include a millimeter wave (mmW) base station 180 that may operate at mmW and / or near mmW frequencies in communication with a UE 182. Extremely high frequency (EHF) is part of the RF spectrum in the electromagnetic spectrum. EHF has a range from 30 GHz to 300 GHz and a wavelength between 1 millimeter and 10 millimeters. Radio waves in this band can be called millimeter waves. The near mmW wave can extend up to a frequency of 3 GHz with a wavelength of 100 millimeters. The band of Petition 870250086012, dated 09 / 23 / 2025, pp. 35 / 362 27 / 158 Super High Frequency (SHF) extends between 3 GHz and 30 GHz, also known as centimeter wave. Communications using the mmW / near mmW radio frequency band have high path loss and a relatively short range. The mmW 180 base station and the UE 182 can use beamforming (transmission and / or reception) on an mmW 184 communication link to compensate for the extremely high path loss and short range. Additionally, it will be recognized that, in alternative configurations, one or more base stations 102 can also transmit using mmW or near mmW and beamforming. Consequently, it will be recognized that the aforementioned illustrations are merely examples and should not be interpreted as limiting the various aspects disclosed in the present invention.

[0062] Transmission beamforming is a technique for focusing an RF signal in a specific direction. Traditionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts the signal in all directions (omnidirectionally). With transmission beamforming, the network node determines where a given target device (e.g., a UE) is located (relative to the transmitting network node) and projects a stronger downlink RF signal in that specific direction, thus providing a faster (in terms of data rate) and stronger RF signal to the receiving device(s). To alter the directionality of the RF signal when transmitting, a network node can control the phase and relative amplitude of the RF signal in each direction. Petition 870250086012, dated 09 / 23 / 2025, pp. 36 / 362 28 / 158 among one or more transmitters that are broadcasting the RF signal. For example, a network node might use an antenna array (called a phased array or antenna array) that creates a beam of RF waves that can be oriented to point in different directions without actually moving the antennas. Specifically, the RF current from the transmitter is used to feed the individual antennas with the correct phase relationship so that the radio waves from the separate antennas add to each other to increase radiation in a desired direction, while canceling each other out to suppress radiation in undesired directions.

[0063] Transmission beams can be quasi-colocalized, meaning that they appear to the receiver (e.g., a UE) as having the same parameters, regardless of whether the network node's own transmitting antennas are physically colocalized or not. In NR, there are four types of quasi-colocalization (QCL) relationships. Specifically, a QCL relationship of a given type means that certain parameters about a second reference RF signal in a second beam can be derived from information about a source reference RF signal in a source beam. Thus, if the source reference RF signal is QCL type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, average delay, and delay spread of a second reference RF signal transmitted on the same channel.If the source reference RF signal is QCL type B, the receiver can use the source reference RF signal for estimation. Petition 870250086012, dated 09 / 23 / 2025, pp. 37 / 362 29 / 158 the Doppler shift and Doppler spread of a second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type C, the receiver can use the source reference RF signal to estimate the Doppler shift and average delay of a second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type D, the receiver can use the source reference RF signal to estimate the spatial reception parameter of a second reference RF signal transmitted on the same channel.

[0064] In beamforming, the receiver uses a receiving beam to amplify the RF signals detected in a given channel. For example, the receiver may increase the gain setting and / or adjust the phase setting of an antenna array in a particular direction to amplify (e.g., increase the gain level of) the RF signals received from that direction. Thus, when a receiver is said to beam in a certain direction, it means that the beam gain in that direction is high relative to the beam gain along other directions, or that the beam gain in that direction is the highest compared to the beam gain in that direction among all other receiving beams available to the receiver.This results in a stronger received signal strength (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), signal-to-interference-plus-noise ratio (SINR), etc.) of the RF signals received from that direction. Petition 870250086012, dated 09 / 23 / 2025, pp. 38 / 362 30 / 158

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

[0066] 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 is forming the downlink beam to transmit a reference signal to a UE, the downlink beam is a transmit beam. However, if the UE is forming the downlink beam, it will be a receive beam to receive the 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 is forming the uplink beam, it will be an uplink receive beam, and if a UE is forming Petition 870250086012, dated 09 / 23 / 2025, pp. 39 / 362 31 / 158 the uplink beam, it will be an uplink transmission beam.

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

[0068] Frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified an operating band for these mid-band frequencies as the frequency band designation FR3 (7.125 GHz to 24.25 GHz). Frequency bands within FR3 can inherit characteristics from FR1 and / or characteristics from FR2, and thus can effectively extend the attributes of FR1 and / or FR2 to mid-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 band designations FR4a or FR4-1 (52.6 GHz). Petition 870250086012, dated 09 / 23 / 2025, p. 40 / 362 32 / 158 to 71 GHz), FR4 (52.6 GHz to 114.25 GHz) and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands is in the EHF band.

[0069] With the above aspects in mind, except where specifically indicated otherwise, it should be understood that the term sub-6 GHz or similar, if used in the present invention, may broadly represent frequencies that may be less than 6 GHz, may be in FR1, or may include mid-band frequencies. Additionally, except where specifically indicated otherwise, it should be understood that the term millimeter wave or similar, if used in the present invention, may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or may be within the EHF band.

[0070] In a multi-carrier system, such as 5G, one of the carrier frequencies is called the primary carrier or anchor carrier or primary server cell or PCell, and the other carrier frequencies are called secondary carriers or secondary server cells or SCells. In carrier aggregation, the anchor carrier is the carrier that operates on the primary frequency (e.g., FR1) used by a UE 104 / 182 and the cell in which the UE 104 / 182 performs the initial radio resource control (RRC) connection establishment procedure or initiates the RRC connection re-establishment procedure. The primary carrier carries all common and specific control channels for the UE and may be a carrier on a licensed frequency (however, this is not always the case). Petition 870250086012, dated 09 / 23 / 2025, page 41 / 362 33 / 158 A secondary carrier is a carrier operating on a second frequency (e.g., FR2) that can be configured once the RRC connection is established between the UE 104 and the anchor carrier and can be used to provide additional radio resources. In some cases, the secondary carrier may be a carrier on an unlicensed frequency. The secondary carrier may contain only necessary signaling information and signals; for example, those specific to the UE may not be present on the secondary carrier, since both uplink and downlink primary carriers are typically UE-specific. This means that different UE 104 / 182s in a cell may have different downlink primary carriers. The same applies to uplink primary carriers. The network has the ability to change the primary carrier of any UE 104 / 182 at any time.This is done, for example, to balance the load across different carriers. Because a server cell (whether a PCell or an SCell) corresponds to a carrier / component carrier frequency through which some base station is communicating, the terms cell, server cell, component carrier, carrier frequency, and the like, can be used interchangeably.

[0071] For example, still referring to Figure 1, one of the frequencies used by the 102 macrocell base stations may be an anchor carrier (or PCell), and other frequencies used by the 102 macrocell base stations and / or the mmW 180 base station may be secondary carriers (SCells). The transmission and / or the Petition 870250086012, dated 09 / 23 / 2025, p. 42 / 362 Simultaneous reception of multiple carriers enables UE 104 / 182 to significantly increase its data transmission and / or reception rates. For example, two aggregated 20 MHz carriers in a multi-carrier system would theoretically lead to a twofold increase in data rate (i.e., 40 MHz) compared to that obtained with a single 20 MHz carrier.

[0072] The wireless communications system 100 may additionally include a UE 164 that can communicate with a macrocell base station 102 via a communication link 120 and / or with the mmW base station 180 via an mmW communication link 184. For example, the macrocell base station 102 may support a PCell and one or more SCells for the UE 164, and the mmW base station 180 may support one or more SCells for the UE 164.

[0073] In some cases, UE 164 and UE 182 may be capable of sidelink communication. Sidelink-capable UEs (SL-UEs) can communicate with base stations 102 via communication links 120 using the Uu interface (i.e., the air interface between a UE and a base station). SL-UEs (e.g., UE 164, UE 182) can also communicate directly with each other via a wireless sidelink 160 using the PC5 interface (i.e., the air interface between sidelink-capable UEs). A wireless sidelink (or simply sidelink) is an adaptation of the cellular core standard (e.g., LTE, NR) that allows direct communication between two or more UEs without the communication needing to pass through a base station. Sidelink communication can be unicast or multicast. Petition 870250086012, dated 09 / 23 / 2025, p. 43 / 362 35 / 158 and can be used for device-to-device (D2D) media sharing, vehicle-to-vehicle (V2V) communication, vehicle-to-everything (V2X) communication (e.g., cellular V2X communication (cV2X), enhanced V2X communication (eV2X)). (Enhanced V2X), etc.), emergency rescue applications, etc. One or more of a group of SL-UEs using side-link communications may be within the geographic coverage area 110 of a base station 102. Other SL-UEs in such a group may be outside the geographic coverage area 110 of a base station 102 or may otherwise be unable to receive transmissions from a base station 102. In some cases, groups of SL-UEs communicating via side-link communications may use a one-to-many (1:M) system in which each SL-UE transmits to all other SL-UEs in the group. In some cases, a base station 102 facilitates the scheduling of resources for side-link communications. In other cases, side-link communications are performed between SL-UEs without the involvement of a base station 102.

[0074] In one aspect, the 160 side link can operate through a wireless communication medium of interest, which can be shared with other wireless communications between other vehicles and / or infrastructure access points, as well as other RATs. A medium can be composed of one or more time, frequency and / or space communication resources (e.g., spanning one or more channels across one or more carriers) associated with wireless communication between one or more pairs of Petition 870250086012, dated 09 / 23 / 2025, p. 44 / 362 36 / 158 transmitter / receiver. In one aspect, the medium of interest may correspond to at least a portion of an unlicensed frequency band shared among several RATs. Although different licensed frequency bands have been reserved for certain communication systems (for example, by a government entity such as the Federal Communications Commission (FCC) in the United States), these systems, particularly those employing small cell access points, have recently extended operation to unlicensed frequency bands, such as the unlicensed national information infrastructure (U-NII) band used by wireless local area network (WLAN) technologies, most notably the IEEE 802.11x WLAN technologies, commonly referred to as Wi-Fi.Examples of such systems include different variants of CDMA systems, TDMA systems, FDMA systems, orthogonal FDMA (OFDMA) systems, single-carrier FDMA (SC-FDMA) systems, and so on.

[0075] It should be noted that although Figure 1 illustrates only two of the UEs as SL-UEs (i.e., UEs 164 and 182), any of the UEs illustrated could be SL-UEs. Additionally, although only UE 182 has been described as being capable of beamforming, any of the UEs illustrated, including UE 164, could be capable of beamforming. When SL-UEs are capable of beamforming, they can form beams towards each other (i.e., towards other SL-UEs), towards other UEs (e.g., UE 104), towards base stations (e.g., base stations). Petition 870250086012, dated 09 / 23 / 2025, page 45 / 362 37 / 158 102, 180, small cell 102', access point 150) etc. In this way, in some cases, UEs 164 and 182 can use beamforming through the side link 160.

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

[0077] In a satellite positioning system, the use of 124 signals can be augmented by various satellite-based augmentation systems (SBAS) that may be associated with, or Petition 870250086012, dated 09 / 23 / 2025, page 46 / 362 38 / 158 otherwise enabled for use with one or more global and / or regional satellite navigation systems. For example, an SBAS may include augmentation system(s) that provide integrity information, differential corrections, etc., such as the wide area augmentation system (WAAS), the European geostationary navigation overlay service (EGNOS), the multi-functional satellite augmentation system (MSAS), global positioning system (GPS)-aided geo-augmented navigation, or GPS and geo-augmented navigation system (GAGAN), and / or similar systems.Thus, as used in the present invention, a satellite positioning system may include any combination of one or more global and / or regional navigation satellites associated with one or more satellite positioning systems.

[0078] In one aspect, SVs 112 can additionally or alternatively be part of one or more non-terrestrial networks (NTNs). In an NTN, an SV 112 is connected to a ground station (also called a terrestrial station, NTN gateway, or gateway) which, in turn, is connected to an element in a 5G network, such as a modified base station 102 (without a terrestrial antenna), or a network node in a 5GC. This element, in turn, would provide access to other elements in the 5G network and, ultimately, to entities external to the 5G network, such as internet web servers and other user devices. In this way, a UE 104 can receive communication signals (e.g., 124 signals) from an SV 112. Petition 870250086012, dated 09 / 23 / 2025, page 47 / 362 39 / 158 instead of, or in addition to, communication signals from a ground base station 102.

[0079] The wireless communication system 100 may additionally include one or more UEs, such as UE 190, which indirectly connects to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (called side links). In the example in Figure 1, UE 190 has a D2D P2P link 192 with one of the UEs 104 connected to one of the base stations 102 (for example, through which UE 190 can indirectly obtain cellular connectivity) and a D2D P2P link 194 with WLAN STA 152 connected to WLAN AP 150 (through which UE 190 can indirectly obtain WLAN-based Internet connectivity). In one example, D2D and P2P links 192 and 194 can be supported with any known D2D RAT, such as LTE Direct (LTE-D), Wi-Fi Direct®, Bluetooth®, and so on.

[0080] Figure 2A illustrates an example wireless network structure 200. For example, a 5GC 210 (also called a next-generation core (NGC)) can be functionally viewed as control plane (C-plane) functions 214 (e.g., UE registration, authentication, network access, gateway selection, etc.), and user plane (U-plane) functions 212 (e.g., UE gateway function, data network access, IP routing, etc.) that operate cooperatively to form the core network. The user plane interface (NG-U) 213 and the control plane interface (NG-C control plane interface) 215 connect the gNB 222 to the 5GC 210, and specifically to the user plane functions 212 and Petition 870250086012, dated 09 / 23 / 2025, page 48 / 362 40 / 158 control plane functions 214, respectively. In an additional configuration, an ng-eNB 224 can also be connected to the 5GC 210 via NG-C 215 for control plane functions 214 and NG-U 213 for user plane functions 212. Additionally, the ng-eNB 224 can communicate directly with the gNB 222 via a backhaul connection 223. In some configurations, a next-generation RAN (NG-RAN) 220 may have one or more gNBs 222, while other configurations include one or more of both ng-eNBs 224 and gNBs 222. One (or both) gNB 222 or ng-eNB 224 can communicate with one or more UEs 204 (for example, any of the UEs described in the present invention).

[0081] Another optional aspect may include a location server 230, which may be in communication with 5GC 210 in order to provide location assistance for UE(s) 204. The location server 230 may be implemented in the form of a plurality of separate servers (e.g., physically separate servers, different software modules on a single server, different software modules spread across multiple physical servers, etc.) or, 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 may connect to the location server 230 via the core network, 5GC 210 and / or via the Internet (not shown). Additionally, the location server 230 may be integrated into a component of the core network or, alternatively, may be external to the core network (e.g., a third-party server, Petition 870250086012, dated 09 / 23 / 2025, p. 49 / 362 41 / 158 as an original equipment manufacturer (OEM) server, or service server).

[0082] Figure 2B illustrates another example wireless network structure 240. A 5GC 260 (which may correspond to 5GC 210 in Figure 2A) can be viewed functionally as control plane functions, provided by an access and mobility management function (AMF) 264, and user plane functions, provided by a user plane function (UPF) 262, which operate cooperatively to form the core network (i.e., 5GC 260).The functions of AMF 264 include record management, connection management, accessibility management, mobility management, lawful interception, transport for session management (SM) messages between one or more UEs 204 (for example, any of the UEs described in the present invention) and a session management function (SMF) 266, transparent proxy services for routing SM messages, access authentication and access authorization, transport for short message service (SMS) messages between UE 204 and the short message service function (SMSF) (not shown), and security anchor functionality (SEAF security anchor functionality).The AMF 264 also interacts with an authentication server function (AUSF authentication server function) (not shown) and the UE 204, and receives the intermediate key that was established as a result of the UE 204 authentication process. This is in the case of authentication based on a subscriber identity module. Petition 870250086012, dated 09 / 23 / 2025, page 50 / 362 42 / 158 (USIM - subscriber identity module) of the Universal Mobile Telecommunications System (UMTS), AMF 264 retrieves security material from AUSF. AMF 264 functions also include security context management (SCM). SCM receives a SEAF key which it uses to derive specific access network keys. AMF 264 functionality also includes location service management for regulatory services, transport for location service messages between UE 204 and a Location Management Function (LMF) 270 (acting as a location server 230), transport for location service messages between NG-RAN 220 and LMF 270, carrier identifier allocation for the evolved packet system (EPS) for interoperability with EPS, and UE 204 mobility event notification.In addition, AMF 264 also supports features for non-Third Generation Partnership Project (3GPP®) access networks.

[0083] The functions of UPF 262 include acting as an anchor point for intra / inter-RAT mobility (when applicable), acting as an external protocol data unit (PDU) session point for interconnection to a data network (not shown), providing packet routing and forwarding, packet inspection, enforcement of user plan directive rules (e.g., gating, redirection, traffic steering), lawful interception (user plan collection), traffic usage reporting, quality handling of Petition 870250086012, dated 09 / 23 / 2025, page 51 / 362 43 / 158 service (QoS - quality of service) for the user plane (e.g., uplink / downlink rate enforcement, reflective QoS marking on the downlink), uplink traffic verification (service data flow (SDF) for QoS flow mapping), transport layer packet marking on the uplink and downlink, downlink packet buffering and downlink data notification triggering, and sending and forwarding one or more end markers to the originating RAN node. The UPF 262 can also support the transfer of location service messages on a user plane between the UE 204 and a location server, such as an SLP 272.

[0084] The functions of SMF 266 include session management, allocation and management of UE Internet Protocol (IP) addresses, selection and control of user plane functions, configuration of traffic routing on UPF 262 to route traffic to the appropriate destination, control of part of the compliance with QoS guidelines and downlink data notification. The interface through which SMF 266 communicates with AMF 264 is called the N11 interface.

[0085] Another optional aspect may include an LMF 270, which may be in communication with the 5GC 260 to provide localization assistance for UEs 204. The LMF 270 may be implemented in the form of a plurality of separate servers (e.g., physically separate servers, different software modules on a single server, different software modules spread across multiple physical servers, etc.) or, alternatively, Petition 870250086012, dated 09 / 23 / 2025, page 52 / 362 44 / 158 each can correspond to a single server. The LMF 270 can be configured to support one or more location services for UEs 204 that can connect to the LMF 270 via the core network, 5GC 260 and / or via the Internet (not shown). The SLP 272 can support similar functions to the LMF 270 but, whereas the LMF 270 can communicate with the AMF 264, the NG-RAN 220 and the UEs 204 on a control plane (e.g., using interfaces and protocols intended to carry signaling messages and not voice or data), the SLP 272 can communicate with the UEs 204 and external clients (e.g., a third-party server 274) on a user plane (e.g., using protocols intended to carry voice and / or data, such as the Transmission Control Protocol (TCP) and / or IP).

[0086] Yet another optional aspect may include a third-party server 274, which may be in communication with the LMF 270, the SLP 272, the 5GC 260 (e.g., via the AMF 264 and / or the UPF 262), the NG-RAN 220 and / or the UE 204, in order to obtain location information (e.g., a location estimate) for the UE 204. In this way, in some cases the third-party server 274 may be called a location services client (LCS) or an external client. The third-party server 274 may be implemented as a plurality of separate servers (e.g., physically separate servers, different software modules on a single server, different software modules spread across multiple physical servers, etc.) or, alternatively, each may correspond to a single server. Petition 870250086012, dated 09 / 23 / 2025, page 53 / 362 45 / 158

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

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

[0089] The deployment of communication systems, such as 5G NR systems, can be arranged in multiple ways with various constituent components or parts. In a 5G NR technology system, or network, a network node, a network entity, a network mobility element, a RAN node, a core network node, a network element or network equipment, such as a base station, or one or more units (or one or more components) that perform base station functionality, can be implemented in an aggregated or disaggregated architecture. For example, a base station (such as a NodeB (NB), an evolved NB (eNB), NR base station, 5G NB, an access point (AP), a transmit / receive point (TRP), or a cell, etc.) can be implemented as an aggregated base station (also known as a standalone base station or a monolithic base station) or a disaggregated base station. Petition 870250086012, dated 09 / 23 / 2025, page 55 / 362 47 / 158

[0090] An aggregated base station can be configured to use a radio protocol stack that is physically or logically integrated into a single RAN node. A disaggregated base station can be configured to use a protocol stack that is physically or logically distributed among two or more units (such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)). In some respects, a CU can be implemented at a RAN node and one or more DUs can be co-located with the CU or, alternatively, can be geographically or virtually distributed across one or more other RAN nodes. DUs can be implemented to communicate with one or more RUs.Each of the CU, DU, and RU can also be implemented as virtual units, that is, a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0091] Base station-type operation or network design may consider base station functionality aggregation features. For example, disaggregated base stations may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN) (such as the O-RAN ALLIANCE® sponsored network configuration), or a virtualized radio access network (vRAN), also known as a cloud radio access network (C-RAN). Petition 870250086012, dated 09 / 23 / 2025, page 56 / 362 48 / 158 radio access network). Disaggregation can include distributing functionality across two or more units in multiple physical locations, as well as distributing functionality to at least one unit virtually, which can enable flexibility in network design. The various units of the disaggregated base station, or disaggregated RAN architecture, can be configured for wired or wireless communication with at least one other unit.

[0092] Figure 2C illustrates an example of a disaggregated base station architecture 250, according to disclosure aspects. The disaggregated base station architecture 250 may include one or more central units (CUs) 280 (e.g., gNB-CU 226) that can communicate directly with a core network 267 (e.g., 5GC 210, 5GC 260) via a backhaul link, or indirectly with the core network 267 through one or more disaggregated base station units (such as a near-real-time RAN intelligent controller (RIC) 259 via an E2 link, or a non-real-time RIC 257 associated with a service management and orchestration (SMO) framework 255, or both). A CU 280 can communicate with one or more DUs 285 (e.g., gNB-DUs 228) via their respective midhaul links, such as an F1 interface. DUs 285 can communicate with one or more radio units (RUs) 287 (e.g., gNB-RUs 229) via their respective fronthaul links. RUs 287 can communicate with their respective UEs 204 via one or more radio frequency (RF) access links. In some Petition 870250086012, dated 09 / 23 / 2025, p. 57 / 362 49 / 158 implementations, UE 204 can be simultaneously served by multiple RUs 287.

[0093] Each of the units, that is, the CUs 280, the DUs 285, the RUs 287, as well as the near-RT 259 RICs, the non-RT 257 RICs and the SMO 255 ​​structure, may include one or more interfaces or be coupled to one or more interfaces configured to receive or transmit signals, data or information (collectively, signals) through a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to the units' communication interfaces, may be configured to communicate with one or more of the other units through the transmission medium. For example, the units may include a wired interface configured to receive or transmit signals through a wired transmission medium to one or more of the other units.Additionally, the units may include a wireless interface, which may include a receiver, a transmitter, or a transceiver (such as an RF transceiver), configured to receive or transmit signals, or both, via a wireless transmission medium to one or more of the other units.

[0094] In some respects, the CU 280 can host one or more higher-layer control functions. Such control functions may include RRC, PDCP, Service Data Adaptation Protocol (SDAP), or similar. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 280. The CU 280 can be configured to handle user-plane functionality (i.e., central unit - user plane (CU-UP)). Petition 870250086012, dated 09 / 23 / 2025, page 58 / 362 50 / 158 - central unit - user plane), the control plane functionality (i.e., central unit - control plane (CUCP)) or a combination thereof. In some implementations, the CU 280 may be logically divided into one or more CU-UP units and one or more CU-CP units. The CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface, such as the E1 interface, when implemented in an O-RAN configuration. The CU 280 may be implemented to communicate with the DU 285, as needed, for network control and signaling.

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

[0096] The lowest layer functionality can be implemented by one or more RUs 287. In some deployments, a RU 287, controlled by a DU 285, can Petition 870250086012, dated 09 / 23 / 2025, p. 59 / 362 51 / 158 corresponds to a logical node that hosts RF processing functions or low-layer PHY functions (such as performing fast Fourier transform (FFT), inverse fast Fourier transform (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, or similar), or both, based at least in part on functional division, as a lower-layer functional division. In such an architecture, the RU(s) 287 can be implemented to handle over-the-air (OTA) communications with one or more UEs 204. In some implementations, real-time and non-real-time aspects of control plane and user communication with the RU(s) 287 can be controlled by the corresponding DU 285. In some scenarios, this configuration may enable the DU 285 and CU 280 to be deployed in a cloud-based RAN architecture, such as a vRAN architecture.

[0097] The SMO 255 ​​framework can be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO 255 ​​framework can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO 255 ​​framework can be configured to interact with a cloud computing platform (such as an open cloud (O-cloud) 269) to perform element lifecycle management. Petition 870250086012, dated 09 / 23 / 2025, page 60 / 362 52 / 158 network (how to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface). These virtualized network elements may include, but are not limited to, CUs 280, DUs 285, RUs 287, and near-RT 259 RICs. In some implementations, the SMO 255 ​​framework may communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 261, via an O1 interface. Additionally, in some implementations, the SMO 255 ​​framework may communicate directly with one or more RUs 287 via an O1 interface. The SMO 255 ​​framework may also include a non-RT 257 RIC configured to support the functionality of the SMO 255 ​​framework.

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

[0099] In some implementations, to generate AI / ML models to be deployed on the RIC near RT 259, the RIC not at RT 257 can receive, from servers Petition 870250086012, dated 09 / 23 / 2025, page 61 / 362 53 / 158 external, parameters, or external enrichment information. Such information can be used by the near-RT 259 RIC and can be received in the SMO 255 ​​framework, or in the non-RT 257 RIC from non-network data sources or from network functions. In some examples, the non-RT 257 RIC or the near-RT 259 RIC can be configured to adjust RAN behavior or performance. For example, the non-RT 257 RIC can monitor long-term trends and patterns in performance, and employ AI / ML models to perform corrective actions through the SMO 255 ​​framework (such as reconfiguration via O1) or through the creation of RAN management guidelines (such as A1 guidelines).

[0100] Figures 3A, 3B, and 3C illustrate various example components (represented by corresponding blocks) that can be incorporated into a UE 302 (which may correspond to any of the UEs described in the present invention), a base station 304 (which may correspond to any of the base stations described in the present invention), and a network entity 306 (which may correspond to or incorporate any of the network functions described in the present invention, including the location server 230 and the LMF 270, or alternatively, may be independent of the NG-RAN 220 and / or 5GC 210 / 260 infrastructure depicted in Figures 2A and 2B, as a private network) to support the operations described in the present invention. It will be recognized that these components can be deployed in different types of appliances in different deployments (e.g., in an ASIC, in a system-on-a-chip (SoC), etc.). The illustrated components can be Petition 870250086012, dated 09 / 23 / 2025, page 62 / 362 54 / 158 also incorporated into other devices in a communication system. For example, other devices in a system may include components similar to those described to provide similar functionality. In addition, a given device may contain one or more of the components. For example, a device may include multiple transceiver components that enable the device to operate on multiple carriers and / or communicate via different technologies.

[0101] UE 302 and base station 304 each include one or more wireless wide area network (WWAN) transceivers 310 and 350, respectively, providing means for communication (e.g., means for transmission, means for reception, means for measurement, means for tuning, means for refraining from transmission, etc.) via one or more wireless communication networks (not shown), such as an NR network, an LTE network, a GSM network and / or similar. Each of the WWAN transceivers 310 and 350 can be connected to one or more antennas 316 and 356, respectively, for communication with other network nodes, such as other UEs, access points, base stations (e.g., eNBs, gNBs), etc., via at least one designated RAT (e.g., NR, LTE, GSM, etc.) through a wireless communication medium of interest (e.g., some set of time / frequency features in a particular frequency spectrum).The WWAN 310 and 350 transceivers can be configured in various ways to transmit and encode 318 and 358 signals (e.g., messages, indications, information, and so on), respectively, and conversely, to receive and decode 318 and 358 signals (e.g., messages, indications, information, pilots, and so on), respectively. Petition 870250086012, dated 09 / 23 / 2025, page 63 / 362 55 / 158 according to the designated RAT. Specifically, WWAN transceivers 310 and 350 include one or more transmitters 314 and 354, respectively, to transmit and encode signals 318 and 358, respectively, and one or more receivers 312 and 352, respectively, to receive and decode signals 318 and 358, respectively.

[0102] The UE 302 and base station 304 also include, each at least in some cases, one or more short-range wireless transceivers 320 and 360, respectively. The short-range wireless transceivers 320 and 360 can be connected to one or more antennas 326 and 366, respectively, and provide means for communication (e.g., means for transmitting, means for receiving, means for measuring, means for adjusting, means for refraining from transmitting, etc.) with other network nodes, such as other UEs, access points, base stations, etc., via at least one designated RAT (e.g., WiFi, LTE-D, BLUETOOTH®, ZIGBEE®, ZWAVE®, PC5, dedicated short-range communications (DSRC), wireless access for vehicular environments (WAVE), near field communication (NFC), ultra-wideband communications (UWB), etc.) through a wireless communication medium of interest.The 320 and 360 short-range wireless transceivers can be configured in various ways to transmit and encode 328 and 368 signals (e.g., messages, indications, information, and so on), respectively, and conversely, to receive and decode 328 and 368 signals (e.g., messages, indications, information, pilots, and so on), respectively. Petition 870250086012, dated 09 / 23 / 2025, page 64 / 362 56 / 158 according to the designated RAT. Specifically, short-range wireless transceivers 320 and 360 include one or more transmitters 324 and 364, respectively, to transmit and encode signals 328 and 368, respectively, and one or more receivers 322 and 362, respectively, to receive and decode signals 328 and 368, respectively. As specific examples, short-range wireless transceivers 320 and 360 may be Wi-Fi transceivers, BLUETOOTH® transceivers, ZIGBEE® transceivers and / or Z-WAVE® transceivers, NFC transceivers, UWB transceivers, or vehicle-to-vehicle (V2V) and / or vehicle-to-everything (V2X) transceivers.

[0103] UE 302 and base station 304 also include, at least in some cases, satellite signal transceivers 330 and 370, which include satellite receiver(s) 330-1 and / or 370-1, respectively, and / or satellite transmitter(s) 330-2 and / or 370-2, respectively. In some designs, the satellite signal transceivers may alternatively be implemented as Rx-only satellite receivers or Tx-only satellite transmitters. In some designs, base station 304 is a terrestrial base station that can communicate with satellite(s) via the satellite signal transceiver(s). In other designs, base station 304 itself may be a satellite (or non-terrestrial entity) that uses the satellite signal transceiver(s) 370 to communicate with terrestrial networks and / or other satellites.

[0104] Satellite signal receivers 330-1 and 370-1 can be connected to one or more antennas 336 and 376, respectively, and can provide means for receiving and / or Petition 870250086012, dated 09 / 23 / 2025, p. 65 / 362 57 / 158 measure satellite positioning / communication signals 338 and 378, respectively. When satellite signal receivers 330-1 and 370-1 are satellite positioning system receivers, satellite positioning / communication signals 338 and 378 may be Global Positioning System (GPS) signals, Global Navigation Satellite System (GLONASS®) signals, Galileo signals, Beidou signals, Indian Regional Navigation Satellite System (NAVIC) signals, Quasi-Zenith Satellite System (QZSS) signals, etc. When 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 (e.g., carrying control and / or user data) originating from a 5G network.Satellite signal receivers 330-1 and 370-1 may comprise any hardware and / or software suitable for receiving and processing satellite positioning / communication signals 338 and 378, respectively. Satellite signal receivers 330-1 and 370-1 may request information and operations, as appropriate, from the other systems, and, at least in some cases, perform calculations to determine the locations of UE 302 and base station 304, respectively, using measurements obtained through any suitable satellite positioning system algorithm.

[0105] Satellite signal transmitters 3302 and 370-2 can be connected to one or more antennas 336 and 376, respectively, and can provide means for transmitting Petition 870250086012, dated 09 / 23 / 2025, page 66 / 362 58 / 158 satellite positioning / communication signals 338 and 378, respectively. When satellite signal transmitters 330-2 and 370-2 are satellite positioning system transmitters, 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-Zenithal Satellite System (QZSS), etc. When satellite signal transmitters 330-2 and 370 are non-terrestrial network (NTN) transmitters, satellite positioning / communication signals 338 and 378 may be communication signals (e.g., carrying control and / or user data) originating from a 5G network.Satellite signal transmitters 330-2 and 370-2 may comprise any hardware and / or software suitable for transmitting satellite positioning / communication signals 338 and 378, respectively. Satellite signal transmitters 3302 and 370-2 may request information and operations, as appropriate, from the other systems, and, at least in some cases, perform calculations to determine the locations of UE 302 and base station 304, respectively, using measurements transmitted to / from any suitable satellite positioning system algorithm.

[0106] Base station 304 and network entity 306 each include one or more network transceivers 380 and 390, respectively, which provide means for communication (e.g., means for transmitting, means for receiving, etc.) with other network entities (e.g., other Petition 870250086012, dated 09 / 23 / 2025, page 67 / 362 59 / 158 base stations 304, other network entities 306). For example, base station 304 may employ one or more network transceivers 380 to communicate with other base stations 304 or network entities 306 through one or more wired or wireless backhaul links. As another example, network entity 306 may employ one or more network transceivers 390 to communicate with one or more base stations 304 on one or more wired or wireless backhaul links, or with other network entities 306 through one or more wired or wireless core network interfaces.

[0107] A transceiver can be configured to communicate over a wired or wireless link. A transceiver (whether a wired transceiver or a wireless transceiver) includes a set of transmitter circuits (e.g., transmitters 314, 324, 354, 364) and a set of receiver circuits (e.g., receivers 312, 322, 352, 362). A transceiver may be an integrated device (e.g., incorporating the transmitter circuit set and the receiver circuit set in a single device) in some implementations, may comprise a separate transmitter circuit set and a separate receiver circuit set in some implementations, or may be incorporated in other ways in other implementations. The transmitter circuitry and the receiver circuitry of a wired transceiver (for example, 380 and 390 network transceivers in some implementations) can be coupled to one or more wired network interface ports.The wireless transmitter circuitry (e.g., 314, 324, 354, 364 transmitters) may include or be coupled to a plurality of antennas (e.g., Petition 870250086012, dated 09 / 23 / 2025, page 68 / 362 60 / 158 antennas 316, 326, 356, 366), as an antenna array, which allows the respective device (e.g., UE 302, base station 304) to perform transmission beamforming, as described in the present invention. Similarly, the wireless receiver circuitry (e.g., receivers 312, 322, 352, 362) may include or be coupled to a plurality of antennas (e.g., antennas 316, 326, 356, 366), as an antenna array, which allows the respective device (e.g., UE 302, base station 304) to perform reception beamforming, as described in the present invention. In one aspect, the transmitter circuit set and the receiver circuit set can share an equal plurality of antennas (for example, antennas 316, 326, 356, 366), so that the respective device can only receive or transmit at a given time, not both at the same time.A wireless transceiver (e.g., WWAN 310 and 350 transceivers, short-range wireless 320 and 360 transceivers) may also include a network listen module (NLM) or similar, to perform various measurements.

[0108] As used in the present invention, the various wireless transceivers (e.g., 310, 320 transceivers, Network transceivers (e.g., 350 and 360, and network transceivers 380 and 390 in some implementations) and wired transceivers (e.g., network transceivers 380 and 390 in some implementations) can generally be distinguished as a single transceiver, at least one transceiver, or one or more transceivers. Thus, whether a particular transceiver is a wired or wireless transceiver can be inferred from the type of communication performed. For example, communication of Petition 870250086012, dated 09 / 23 / 2025, p. 69 / 362 61 / 158 backhaul between network devices or servers generally refers to signaling via a wired transceiver, while wireless communication between a UE (e.g., UE 302) and a base station (e.g., base station 304) generally refers to signaling via a wireless transceiver.

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

[0110] UE 302, base station 304, and network entity 306 include the set of memory circuits that implement memories 340, 386, and 396 (e.g., each including a memory device), respectively, for Petition 870250086012, dated 09 / 23 / 2025, p. 70 / 362 62 / 158 maintain information (e.g., information indicating reserved resources, thresholds, parameters, and so forth). Memories 340, 386, and 396 can therefore provide means for storing, means for retrieving, means for maintaining, etc. In some cases, UE 302, base station 304, and network entity 306 may include RxTx components 342, 388, and 398, respectively. RxTx components 342, 388, and 398 may be hardware circuits that are part of, or coupled to, processors 332, 384, and 394, respectively, which, when executed, cause UE 302, base station 304, and network entity 306 to perform the functionality described in the present invention. In other respects, the Rx-Tx component of the 342, 388, and 398 processors may be external to the 332, 384, and 394 processors (for example, part of a modem processing system, integrated into another processing system, etc.).Alternatively, the Rx-Tx components 342, 388, and 398 may be memory modules stored in memories 340, 386, and 396, respectively, which, when executed by processors 332, 384, and 394 (or a modem processing system, another processing system, etc.), cause UE 302, base station 304, and network entity 306 to perform the functionality described in the present invention. Figure 3A illustrates possible locations of the Rx-Tx component 342, which may, for example, be part of one or more WWAN transceivers 310, memory 340, one or more processors 332, or any combination thereof, or it may be a standalone component. Figure 3B illustrates possible locations of the Rx-Tx component 388, which may, for example, be part of one or more transceivers. Petition 870250086012, dated 09 / 23 / 2025, p. 71 / 362 63 / 158 WWAN 350, memory 386, one or more processors 384, or any combination thereof, or it may be a standalone component. Figure 3C illustrates possible locations for the Rx-Tx component 398, which may be, for example, part of one or more network transceivers 390, memory 396, one or more processors 394, or any combination thereof, or it may be a standalone component.

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

[0112] In addition, UE 302 includes a user interface 346 that provides means for providing indications (by Petition 870250086012, dated 09 / 23 / 2025, page 72 / 362 64 / 158 example, audible and / or visual cues) to a user and / or to receive information entered by the user (for example, through user activation of a sensing device, such as a numeric keypad, a touch screen, a microphone, and so on). Although not shown, base station 304 and network entity 306 may also include user interfaces.

[0113] With reference to one or more 384 processors in more detail, in the downlink, IP packets from network entity 306 can be provided to processor 384. One or more 384 processors can implement functionality for an RRC layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer.One or more 384 processors can provide RRC layer functionality associated with broadcast transmission of system information (e.g., master information block (MIB), system information blocks (SIBs)), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-RAT mobility, and measurement configuration for UE measurement reports; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with upper-layer PDU transfer, error correction via automatic retry request (ARQ). Petition 870250086012, dated 09 / 23 / 2025, page 73 / 362 65 / 158 automatic repeat request), concatenation, segmentation and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling and logical channel prioritization.

[0114] Transmitter 354 and receiver 352 can implement layer 1 (L1) functionality associated with various signal processing functions. Layer 1, which includes a physical layer (PHY), can include error detection in transport channels, forward error correction (FEC) encoding / decoding of transport channels, interleaving, rate correlation, mapping to physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. Transmitter 354 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), multilevel phase-shift keying (M-PSK), multilevel quadrature amplitude modulation (MQAM)).The encoded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to an orthogonal frequency division multiplexing (OFDM) subcarrier. Petition 870250086012, dated 09 / 23 / 2025, page 74 / 362 66 / 158 multiplexing), multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and are then combined using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time-domain OFDM symbol stream. The OFDM symbol stream is spatially pre-coded to produce multiple spatial streams. Channel estimates from a channel estimator can be used to determine the modulation and coding scheme, as well as for spatial processing. The channel estimate can be derived from a reference signal and / or channel condition feedback transmitted by UE 302. Each spatial stream can then be provided to one or more different antennas 356. The transmitter 354 can modulate an RF carrier with a corresponding spatial stream for transmission.

[0115] In UE 302, receiver 312 receives a signal through its respective antenna(s) 316. Receiver 312 retrieves the modulated information on an RF carrier and provides the information to one or more processors 332. Transmitter 314 and receiver 312 implement layer 1 functionality associated with various signal processing functions. Receiver 312 can perform spatial processing on the information to retrieve any spatial streams destined for UE 302. If multiple spatial streams are destined for UE 302, they can be combined by receiver 312 into a single OFDM symbol stream. Receiver 312 then converts the OFDM symbol stream from the time domain to the frequency domain using a Fast Fourier Transform (FFT). The frequency domain signal comprises Petition 870250086012, dated 09 / 23 / 2025, page 75 / 362 67 / 158 a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most probable signal constellation points transmitted by base station 304. These soft decisions can be based on channel estimates computed by a channel estimator. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by base station 304 on the physical channel. The data and control signals are then provided to one or more processors 332, which implement the functionality of layer 3 (L3 layer-3) and layer 2 (L2 layer-2).

[0116] In the downlink, the one or more 332 processors provide demultiplexing between transport and logic channels, packet reassembly, decryption, header decompression, and control signal processing to retrieve IP packets from the core network. The one or more 332 processors are also responsible for error detection.

[0117] Similar to the functionality described in connection with downlink transmission by base station 304, the one or more 332 processors provide RRC layer functionality associated with the acquisition of system information (e.g., MIBs, SIBs), RRC connections, and measurement reports; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); and RLC layer functionality associated with the transfer of upper-layer PDUs and error correction. Petition 870250086012, dated 09 / 23 / 2025, p. 76 / 362 68 / 158 via ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs into transport blocks (transport blocks TBs), demultiplexing of MAC SDUs from TBs, scheduling information reports, error correction via hybrid automatic retry request (HARQ), priority handling and logical channel prioritization.

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

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

[0120] In the uplink, one or more 384 processors provide demultiplexing between transport and logic channels, packet reassembly, decryption, header decompression, signal processing of Petition 870250086012, dated 09 / 23 / 2025, page 77 / 362 69 / 158 control to retrieve IP packets from UE 302. IP packets from one or more 384 processors can be provided to the core network. The one or more 384 processors are also responsible for error detection.

[0121] For convenience, UE 302, base station 304 and / or network entity 306 are shown in Figures 3A, 3B and 3C as including various components that can be configured according to the various examples described in the present invention. It will be recognized, however, that the illustrated components may have different functionalities in different designs. In particular, several components in Figures 3A to 3C are optional in alternative configurations, and the various aspects include configurations that may vary due to design choices, costs, device usage or other considerations.For example, in the case of Figure 3A, a particular implementation of UE 302 may omit the WWAN transceiver(s) 310 (for example, a wearable device or tablet computer, or personal computer (PC) or laptop computer may have Wi-Fi and / or BLUETOOTH® capability without cellular capability), or it may omit the short-range wireless transceiver(s) 320 (for example, cellular only, etc.), or it may omit the satellite receiver 330, or it may omit the sensor(s) 344, and so on. In another example, in the case of Figure... 3B, a particular implementation of base station 304 may omit the WWAN transceiver(s) 350 (e.g., a Wi-Fi hotspot access point without cellular capability), or may omit the short-range wireless transceiver(s) 360 (e.g., cellular only, etc.), or may omit the satellite receiver 370, and so on. For brevity, the Petition 870250086012, dated 09 / 23 / 2025, page 78 / 362 70 / 158 An illustration of the various alternative configurations is not provided in the present invention, but would be readily understandable to one skilled in the art.

[0122] The various components of UE 302, base station 304, and network entity 306 can be communicatively coupled to each other on data buses 334, 382, ​​and 392, respectively. In one aspect, data buses 334, 382, ​​and 392 can form, or be part of, a communication interface of UE 302, base station 304, and network entity 306, respectively. For example, when different logical entities are incorporated into an equal device (e.g., gNB functionality and location server incorporated into equal base station 304), data buses 334, 382, ​​and 392 can provide communication between them.

[0123] 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 can use and / or incorporate at least one memory component to store information or executable code used by the circuit to provide this functionality. For example, some or all of the functionalities represented by blocks 310 to 346 can be implemented by the processor and the memory component(s) of UE 302 (for example, by executing suitable code and / or by configuring appropriate processor components). Similarly, some or all of the functionalities Petition 870250086012, dated 09 / 23 / 2025, p. 79 / 362 71 / 158 represented by blocks 350 to 388 can be implemented by the processor and memory component(s) of base station 304 (for example, by executing suitable code and / or by configuring suitable processor components). Furthermore, some or all of the functionalities represented by blocks 390 to 398 can be implemented by the processor and memory component(s) of network entity 306 (for example, by executing suitable code and / or by configuring suitable processor components). For simplicity, various operations, acts, and / or functions are described in the present invention as being performed by a UE, a base station, a network entity, etc. However, as will be recognized, such operations, acts, and / or functions can in fact be performed by components, or combinations of components, specific to UE 302, base station 304, network entity 306, etc., such as processors 332, 384, 394, transceivers 310, 320, 350 and 360, memories 340, 386, and 396, positioning component 342, 388 and 398 etc.

[0124] In some designs, network entity 306 may be implemented as a core network component. In other designs, network entity 306 may be distinct from a cellular network infrastructure operator or operation (e.g., NG RAN 220 and / or 5GC 210 / 260). For example, network entity 306 may be a component of a private network that may be configured to communicate with UE 302 via base station 304, or independently of base station 304 (e.g., via a non-cellular communication link such as Wi-Fi). Petition 870250086012, dated 09 / 23 / 2025, page 80 / 362 72 / 158

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

[0126] LTE and, in some cases, NR, use orthogonal frequency division multiplexing (OFDM) on the downlink and single-carrier frequency division multiplexing (SC-FDM) on the uplink. Unlike LTE, however, NR has the option of using OFDM on the uplink as well. OFDM and SC-FDM partition the system bandwidth into multiple (K) orthogonal subcarriers, which are also commonly called tones, bins, etc. Each subcarrier can be modulated with data. In general, modulation symbols are sent in the frequency domain with OFDM and in the time domain with SC-FDM. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can be dependent on the system bandwidth.For example, the subcarrier spacing could be 15 kilohertz (kHz - kilohertz) and the minimum resource allocation (resource block) could be 12 subcarriers (or 180 kHz). Consequently, the nominal Fast Fourier Transform (FFT) size could be 128, 256, 512, 1024, or 2048 for a system bandwidth of 1.25, 2.5, 5, 10, or 20 megahertz (MHz). Petition 870250086012, dated 09 / 23 / 2025, page 81 / 362 73 / 158 respectively. The system bandwidth can also be partitioned into sub-bands. For example, a sub-band might cover 1.08 MHz (i.e., 6 resource blocks), and there could be 1, 2, 4, 8, or 16 sub-bands for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, respectively.

[0127] LTE supports a single numerology (subcarrier spacing (SCS), symbol length, etc.). In contrast, NR can support multiple numerologies (μ), for example, subcarrier spacings of 15 kHz (μ=0), 30 kHz (μ=1), 60 kHz (μ=2), 120 kHz (μ=3) and 240 kHz (μ=4) or higher frequencies may be available. In each subcarrier spacing, there are 14 symbols for each slot. For 15 kHz SCS (μ = 0), there is one slot for each subframe, 10 slots for each frame, the slot duration is 1 millisecond (ms), the symbol duration is 66.7 microseconds (μs), and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 50. For 30 kHz SCS (μ = 1), there are two slots for each subframe, 20 slots for each frame, the slot duration is 0.5 ms, the symbol duration is 33.3 μs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 100. For 60 kHz SCS (μ = 2), there are four slots for each subframe, 40 slots for each frame, the slot duration is 0.25 ms, the symbol duration is... 16.7 μs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 200.For 120 kHz SCS (μ=3), there are eight slots for each subframe, 80 slots for each frame, the slot duration is 0.125 ms, the symbol duration is 8.33 μs, and the maximum nominal system bandwidth (in MHz) has a size of... Petition 870250086012, dated 09 / 23 / 2025, page 82 / 362 74 / 158 A 4K FFT is 400. For 240 kHz SCS (μ=4), there are 16 slots for each subframe, 160 slots for each frame, the slot duration is 0.0625 ms, the symbol duration is 4.17 μs, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 800.

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

[0129] A resource grid can be used to represent time slots, where each time slot includes one or more time-simultaneous 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 can correspond to a symbol length in the time domain and a subcarrier in the frequency domain. In the numerology of Figure 4, for a normal cyclic prefix, an RB can contain 12 consecutive subcarriers in the frequency domain and seven consecutive symbols in the time domain, for a total of 84 REs. For an extended cyclic prefix, an RB can contain 12 consecutive subcarriers in the frequency domain and six consecutive symbols in the time domain, for a total of 72 REs. The number of bits carried by each RE depends on the modulation scheme. Petition 870250086012, dated 09 / 23 / 2025, p. 83 / 362 75 / 158

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

[0131] Figure 5 is a 500 diagram illustrating several downlink channels within an example downlink slot. In Figure 5, time is represented horizontally (on the X-axis), with time increasing from left to right, while frequency is represented vertically (on the Y-axis) with frequency increasing (or decreasing) from bottom to top. In the example in Figure 5, a numerology of 15 kHz is used. Thus, in the time domain, the illustrated slot is one millisecond (ms) long, divided into 14 symbols. Petition 870250086012, dated 09 / 23 / 2025, page 84 / 362 76 / 158

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

[0133] With reference to Figure 5, a primary synchronization signal (PSS) is used by a UE to determine the subframe / symbol timing and a physical layer identity. A secondary synchronization signal (SSS) is used by a UE to determine a physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a PCI. Based on the PCI, the UE can determine the locations of the previously mentioned DL-RS. The physical broadcast channel (PBCH), which carries a master information block (MIB), can be logically grouped with the PSS and SSS to form an SSB (also called SS / PBCH). The MIB provides a number of RBs in the link system bandwidth. Petition 870250086012, dated 09 / 23 / 2025, page 85 / 362 77 / 158 downlink and a system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data and broadcasts system information not transmitted through PBCH, such as system information blocks (SIBs) and paging messages.

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

[0135] In the example in Figure 5, there is one CORESET for each BWP, and the CORESET spans three symbols (although it may have only one or two symbols) in the time domain. Unlike LTE control channels, which occupy the entire system bandwidth, in NR, PDCCH channels are located in a specific region in the frequency domain (i.e., a CORESET). Thus, the frequency component of the PDCCH shown in Figure 5 is illustrated as less than one Petition 870250086012, dated 09 / 23 / 2025, page 86 / 362 78 / 158 unique BWP in the frequency domain. Note that although the illustrated CORESET is contiguous in the frequency domain, it does not need to be. Furthermore, the CORESET may encompass fewer than three symbols in the time domain.

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

[0137] Figure 6 is a diagram of an example PRS 600 configuration for PRS transmissions from a given base station, according to broadcast aspects. In Figure 6, time is represented horizontally, increasing from left to right. Each long rectangle represents a slot and each short (shaded) rectangle represents an OFDM symbol. In the example in Figure Petition 870250086012, dated 09 / 23 / 2025, page 87 / 362 79 / 158 6, a PRS 610 resource set (marked as PRS resource set 1) includes two PRS resources, a first PRS 612 resource (marked as PRS resource 1) and a second PRS 614 resource (marked as PRS resource 2). The base station transmits PRS on PRS resources 612 and 614 of the PRS 610 resource set.

[0138] The PRS 610 feature set has an occasion length (N_PRS) of two slots and a periodicity (T_PRS) of, for example, 160 slots or 160 milliseconds (ms) (for 15 kHz subcarrier spacing). Thus, both the PRS 612 and 614 features have a length of two consecutive slots and are repeated every T_PRS slot, starting from the slot in which the first symbol of the respective PRS feature occurs. In the example in Figure 6, the PRS 612 feature has a symbol length (N_symb) of two symbols, and the PRS 614 feature has a symbol length (N_symb) of four symbols. The PRS 612 feature and the PRS 614 feature can be transmitted on separate beams from the same base station.

[0139] Each instance of the PRS 610 feature set, illustrated as instances 620a, 620b, and 620c, includes an occasion of length '2' (i.e., N_PRS=2) for each PRS 612, 614 feature of the PRS feature set. The PRS 612 and 614 features are repeated every T_PRS slot up to the T_REP periodicity of the silencing sequence. Thus, a bitmap of length T_REP would be needed to indicate which occasions of instances 620a, 620b, and 620c of the PRS 610 feature set are silenced (i.e., not transmitted). Petition 870250086012, dated 09 / 23 / 2025, page 88 / 362 80 / 158

[0140] In one aspect, there may be additional restrictions in the PRS 600 configuration. For example, for all PRS features (e.g., PRS 612, 614 features) of a PRS feature set (e.g., PRS 610 feature set), the base station can configure the following parameters to be the same: (a) the occasion length (N_PRS), (b) the number of symbols (N_symb), (c) the comb type, and / or (d) the bandwidth. Furthermore, for all PRS features of all PRS feature sets, the subcarrier spacing and cyclic prefix can be configured to be the same for one base station or for all base stations. Whether for one base station or all base stations, this may depend on the UE's ability to support the first and / or second option.

[0141] Figure 7 is a 700 diagram illustrating several uplink channels within an example uplink slot. In Figure 7, time is represented horizontally (on the X-axis), with time increasing from left to right, while frequency is represented vertically (on the Y-axis) with frequency increasing (or decreasing) from bottom to top. In the example of Figure 7 uses a 15 kHz numerology. Thus, in the time domain, the illustrated slot is one millisecond (ms) long, divided into 14 symbols.

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

[0143] In one aspect, the reference signal carried on the REs marked as R in Figure 4 may be SRS. The SRS transmitted by a UE can be used by a base station to obtain channel state information (CSI) for each transmitting UE. CSI describes how an RF signal propagates from the UE to the base station and represents the combined effect of scattering, fading, and power drop with distance. The system uses SRS for resource scheduling, link adaptation, massive MIMO, beam management, etc.

[0144] A collection of REs that are used for SRS transmission is called an SRS resource and can be identified by the SRS-ResourceId parameter. The collection of Petition 870250086012, dated 09 / 23 / 2025, page 90 / 362 82 / 158 resource elements can encompass multiple PRBs in the frequency domain and N (e.g., one or more) consecutive symbol(s) within a time domain range. In a given OFDM symbol, an SRS resource occupies consecutive PRBs. An SRS resource set is a set of SRS resources used for transmitting SRS signals, and is identified by an SRS Resource Set ID (SRS-ResourceSetId).

[0145] The transmission of SRS features in a given PRB has a particular comb size (also called comb density). A comb size N represents the subcarrier spacing (or frequency / tone spacing) within each symbol of an SRS feature configuration. Specifically, for a comb size 'N', the SRS is transmitted across the entire Nth subcarrier of a PRB symbol. For example, for comb-4, for each symbol of the SRS feature configuration, REs corresponding to each fourth subcarrier (such as subcarriers 0, 4, 8) are used to transmit the SRS feature's SRS. In the example in Figure 4, the illustrated SRS is comb-4 over four symbols. That is, the locations of the shaded SRS REs indicate a comb-4 SRS feature configuration.

[0146] Currently, an SRS resource can span 1, 2, 4, 8, or 12 consecutive symbols in a slot with a comb-2, comb-4, or comb-8 size. The symbol-to-symbol frequency offsets of the currently supported SRS comb patterns are shown below. 1-symbol comb-2: {0}; 2-symbol comb-2: {0, 1}; 2-symbol comb-4: {0, 2}; 4-symbol comb-2: {0, 1, 0, 1}; 4-symbol comb-4: {0, 2, 1, 3} (as in the example of Petition 870250086012, dated 09 / 23 / 2025, page 91 / 362 83 / 158 Figure 4); 8-symbol 4-comb: {0, 2, 1, 3, 0, 2, 1, 3}; 12-symbol 4-comb: {0, 2, 1, 3, 0, 2, 1, 3, 0, 2, 1, 3}; 4-symbol 8-comb: {0, 4, 2, 6}; 8-symbol 8-comb: {0, 4, 2, 6, 1, 5, 3, 7}; and 12-symbol 8-comb: {0, 4, 2, 6, 1, 5, 3, 7, 0, 4, 2, 6}.

[0147] In general, as mentioned above, an UE transmits SRS to enable the receiving base station (the serving base station or a neighboring base station) to measure channel quality (i.e., CSI) between the UE and the base station. However, SRS can also be specifically configured as reference signals for uplink positioning for uplink-based positioning procedures, such as uplink time difference of arrival (UL-TDOA), round-trip time (RTT), uplink angle of arrival (UL-AoA), etc. As used in the present invention, the term SRS can refer to SRS configured for channel quality measurements or SRS configured for positioning purposes.The first may be referred to in the present invention as SRS for communication, and / or the second may be referred to as SRS for positioning or SRS for positioning when necessary to distinguish the two types of SRS.

[0148] Several improvements over the previous definition of SRS have been proposed for SRS for placement (also called UL-PRS or UL-SRS), such as a new misaligned pattern in an SRS feature (except for a single symbol / comb 2), a new comb type for SRS, new sequences for SRS, a larger number of SRS feature sets per component carrier, and a larger number of features. Petition 870250086012, dated 09 / 23 / 2025, page 92 / 362 84 / 158 SRS per component carrier. Additionally, the SpatialRelationInfo and PathLossReference parameters must be configured based on a downlink or SSB reference signal from a neighboring TRP. Furthermore, an SRS resource can be transmitted outside the active BWP, and an SRS resource can extend across multiple component carriers. Additionally, the SRS can be configured in the RRC connected state and transmitted only within an active BWP. Furthermore, there can be no frequency hopping, no repeat factor, a single antenna port, and new lengths for SRS (e.g., 8 and 12 symbols). There can also be open-loop power control and no closed-loop power control, and 8-comb (i.e., one SRS transmitted on each octave subcarrier on the same symbol) can be used. Lastly, the UE can transmit over the same broadcast beam from multiple SRS resources to UL-AoA.All of these are attributes that are in addition to the current SRS structure, which is configured through RRC upper-layer signaling (and potentially triggered or activated through a MAC control element (MAC-CE) or downlink control information (DCI)).

[0149] NR technology supports a range of cellular network-based positioning technologies, including downlink-based, uplink-based, and both downlink-and-uplink-based positioning methods. Downlink-based positioning methods include observed time difference of arrival (OTDOA) in LTE, and downlink-based time difference of arrival. Petition 870250086012, dated 09 / 23 / 2025, page 93 / 362 85 / 158 (DL-TDOA - downlink time difference of arrival) in NR, and downlink angle of departure (DL-AoD - downlink angle-of-departure) in NR. Figure 8 illustrates examples of various positioning methods, according to aspects of disclosure. In an OTDOA or DL-TDOA positioning procedure, illustrated by scenario 810, a UE measures the differences between the arrival times (ToAs - times of arrival) of reference signals (e.g., positioning reference signals (PRS)) received from pairs of base stations, called reference signal time difference (RSTD - reference signal time difference) or time difference of arrival (TDOA - time difference of arrival) measurements, and reports them to a positioning entity. More specifically, the UE receives the identifiers (ID identifiers) of a reference base station (e.g., a serving base station) and multiple non-reference base stations in the assist data.The UE then measures the RSTD between the reference base station and each of the non-reference base stations. Based on the known locations of the base stations involved and the RSTD measurements, the positioning entity (e.g., the UE for UE-based positioning or a location server for UE-assisted positioning) can estimate the UE's location.

[0150] For DL-AoD positioning, illustrated by scenario 820, the positioning entity uses a UE measurement report, of received signal strength measurements from multiple downlink transmission beams, to determine the angle(s) between the UE and the transmitting base station(s). The entity of Petition 870250086012, dated 09 / 23 / 2025, page 94 / 362 86 / 158 positioning can then estimate the UE's location based on the determined angle(s) and the known location(s) of the transmission base station(s).

[0151] Uplink-based positioning methods include uplink time difference of arrival (UL-TDOA) and uplink angle of arrival (UL-AoA). UL-TDOA is similar to DL-TDOA, but relies on uplink reference signals (e.g., polling reference signals (SRS)) transmitted by the UE to multiple base stations. Specifically, a UE transmits one or more uplink reference signals that are measured by a reference base station and a plurality of non-reference base stations. Each base station then reports the reception time (called relative time of arrival (RTOA)) of the reference signal(s) to a positioning entity (e.g., a location server) that knows the locations and relative timing of the base stations involved.Based on the reception-to-reception (Rx-Rx) time difference between the reported RTOA of the reference base station and the reported RTOA of each non-reference base station, the known locations of the base stations and their known timing offsets, the positioning entity can estimate the UE's location using TDOA.

[0152] For UL-AoA positioning, one or more base stations measure the received signal strength of one or more uplink reference signals (e.g., SRS) received from a UE on one or more beams of Petition 870250086012, dated 09 / 23 / 2025, p. 95 / 362 87 / 158 uplink reception. The positioning entity uses signal strength measurements and the angle(s) of the reception beam(s) to determine the angle(s) between the UE and the base station(s). Based on the determined angle(s) and the known location(s) of the base station(s), the positioning entity can then estimate the UE's location.

[0153] Downlink and uplink-based positioning methods include enhanced cell-ID (E-CID) positioning and multi-round-trip time (RTT) positioning (also called multi-cell RTT and multi-RTT). In an RTT procedure, a first entity (e.g., a base station or a UE) transmits a first RTT-related signal (e.g., a PRS or an SRS) to a second entity (e.g., a UE or a base station), which transmits a second RTT-related signal (e.g., an SRS or a PRS) back to the first entity. Each entity measures the time difference between the arrival time (ToA) of the received RTT-related signal and the transmission time of the transmitted RTT-related signal. This time difference is called a receive-to-transmit (Rx-Tx) time difference.The Rx-Tx time difference measurement can be made, or adjusted, to include only the time difference between the nearest slot boundaries for the received and transmitted signals. Both entities can then send their Rx-Tx time difference measurement to a location server (e.g., an LMF 270), which calculates the round-trip propagation time (i.e., RTT) between them. Petition 870250086012, dated 09 / 23 / 2025, page 96 / 362 88 / 158 two entities of the two Rx-Tx time difference measurements (e.g., as the sum of the two Rx-Tx time difference measurements). Alternatively, one entity can send its Rx-Tx time difference measurement to the other entity, which then calculates the RTT. The distance between the two entities can be determined from the RTT and the known signal speed (e.g., the speed of light). For multi-RTT positioning, illustrated by scenario 830, a first entity (e.g., a UE or a base station) performs an RTT positioning procedure with multiple second entities (e.g., multiple base stations or UEs) to enable the location of the first entity to be determined (e.g., using multilateration) based on the distances to, and the known locations of, the second entities.RTT and multi-RTT methods can be combined with other positioning techniques, such as UL-AoA and DL-AoD, to improve location accuracy, as illustrated by scenario 840.

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

[0155] To assist with positioning operations, a location server (e.g., location server 230, LMF 270, SLP 272) can provide Petition 870250086012, dated 09 / 23 / 2025, page 97 / 362 89 / 158 UE assistance data. For example, assistance data may include identifiers of the base stations (or base station cells / TRPs) from which to measure reference signals, reference signal configuration parameters (e.g., number of consecutive slots including PRS, periodicity of consecutive slots including PRS, muting sequence, frequency hopping sequence, reference signal identifier, reference signal bandwidth, etc.) and / or other parameters applicable to the particular positioning method. Alternatively, assistance data may originate directly from the base stations themselves (e.g., in periodically broadcast overhead messages, etc.). In some cases, the UE may be able to detect neighboring network nodes itself without the use of assistance data.

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

[0157] A location estimate may be called by other names, such as a position estimate, Petition 870250086012, dated 09 / 23 / 2025, page 98 / 362 90 / 158 location, position, position correction, correction or similar. A location estimate may be geodetic and comprise coordinates (e.g., latitude, longitude and possibly altitude), or it may be civic and comprise a street address, postal address, or some other verbal description of a location. A location estimate may additionally be defined relative to some other known location or defined in absolute terms (e.g., using latitude, longitude and possibly altitude). A location estimate may include an uncertainty or expected error (e.g., by including an area or volume within which the location is expected to be included with some specified or standard confidence level).

[0158] In NR, precise timing synchronization across the network may not be possible. Instead, coarse timing synchronization across base stations may be sufficient (e.g., within a cyclic prefix (CP) duration of orthogonal frequency division multiplexing (OFDM) symbols). RTT-based methods generally only require coarse timing synchronization and are thus preferred placement methods in NR.

[0159] Figure 9 illustrates an example 900 wireless communications system, according to aspects of the disclosure. In the example in Figure 9, a UE 904 (for example, any of the UEs described in the present invention) is attempting to calculate an estimate of its location, or to assist another entity (for example, a base station or core network component, another UE, a server of Petition 870250086012, dated 09 / 23 / 2025, page 99 / 362 91 / 158 location, a third-party application, etc.) to calculate an estimate of its location. The UE 904 can transmit and receive wireless signals to and from a plurality of network nodes (marked as Node) 902-1, 902-2, and 902-3 (collectively, network nodes 902). The network nodes 902 may include one or more base stations (e.g., any of the base stations described in the present invention), one or more reconfigurable intelligent displays (RIS), one or more positioning beacons, one or more UEs (e.g., connected by side links), etc.

[0160] In a network-centric RTT positioning procedure, the serving base station (e.g., one of the 902 network nodes) instructs UE 904 to measure RTT measurement signals (e.g., PRS) from two or more neighboring 902 network nodes (and typically the serving base station, since at least three 902 network nodes are required for a two-dimensional location estimate). The involved 902 network nodes transmit RTT measurement signals on low-reuse resources (e.g., resources used by the 902 network nodes to transmit system information, where the 902 network nodes are base stations) allocated by the network (e.g., location server 230, LMF 270, SLP 272).The UE 904 records the arrival time (also called reception time, reception time, reception instant, or arrival time) of each RTT measurement signal relative to the current downlink timing of the UE 904 (e.g., as derived by the UE 904 from a downlink signal received from its serving base station) and transmits a response signal. Petition 870250086012, dated 09 / 23 / 2025, page 100 / 362 92 / 158 Common or individual RTT (e.g., SRS) for the network nodes 902 involved in the resources allocated by the serving base station. The UE 904, if not the positioning entity, reports a UE receive-to-transmit (Rx-Tx) time difference measurement to the positioning entity. The UE Rx-Tx time difference measurement indicates the time difference between the arrival time of each RTT measurement signal at UE 904 and the transmission time(s) of the RTT response signal(s). Each involved network node 902 also reports a network node Rx-Tx time difference measurement (also called a base station (BS) or gNB) Rx-Tx time difference measurement) to the positioning entity, indicating the difference between the transmission time of the RTT measurement signal and the reception time of the RTT response signal.

[0161] A UE-centered RTT positioning procedure is similar to the network-based procedure, except that UE 904 transmits uplink RTT measurement signal(s) (e.g., on resources allocated by the serving base station). The uplink RTT measurement signal(s) are measured by multiple network nodes 902 in the vicinity of UE 904. Each network node involved responds with a downlink RTT response signal and reports an Rx-Tx time difference measurement from the network node to the positioning entity. The network node Rx-Tx time difference measurement indicates the time difference between the arrival time of the RTT measurement signal at network node 902 and the transmission time of the RTT response signal. UE 904, if not the positioning entity, reports a measurement for each network node 902. Petition 870250086012, dated 09 / 23 / 2025, page 101 / 362 93 / 158 UE Rx-Tx time difference indicating the difference between the transmission time of the RTT measurement signal and the reception time of the RTT response signal.

[0162] In order to determine the location (x, y) of UE 904, the positioning entity needs to know the locations of the network nodes 902, which can be represented in a reference coordinate system as (x_k, y_y), where k=1, 2, 3 in the example of Figure 9. When UE 904 is the positioning entity, a location server with knowledge of the network geometry (e.g., location server 230, LMF 270, SLP 272) can provide the locations of the network nodes involved in UE 902 for UE 904.

[0163] The positioning entity determines each distance 910 (d_k, where k=1, 2, 3) between UE 904 and the respective network node 902 based on UE and network node Rx-Tx time difference measurements and the speed of light, as further described below with reference to Figure 10. Specifically, in the example in Figure 9, the distance 910-1 between UE 904 and network node 902-1 is d_1, the distance 910-2 between UE 904 and network node 902-2 is d_2, and the distance 910-3 between UE 904 and network node 902-3 is d_3. Once each distance 910 is determined, the positioning entity can solve the (x, y) location of UE 904 using various known geometric techniques, such as trilateration. From Figure 9, it can be noted that the location of UE 904 is ideally situated at the common intersection of three semicircles, where each semicircle is defined by the radius dk and the center (x_k, y_k), where k=1, 2, 3. Petition 870250086012, dated 09 / 23 / 2025, page 102 / 362 94 / 158

[0164] Figure 10 is a diagram 1000 showing example timings of RTT measurement signals exchanged between a network node 1002 (marked as Node) and a UE 1004, according to aspects of the disclosure. UE 1004 can be any of the UEs described in the present invention. Network node 1002 can be a base station (e.g., any of the base stations described in the present invention), a RIS, a positioning beacon, another UE (e.g., connected via a side link) or similar.

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

[0166] UE 1004 reports the difference between time T_3 and time T_2 (that is, the Rx-Tx time difference measurement of UE 1004, shown as UE_Rx-Tx 1012) to the positioning entity. Similarly, the network node Node 1002 reports the difference between time T_4 and time T_1 (that is, the Rx-Tx time difference measurement of network node 1002, shown as Node_Rx-Tx 1022) for the positioning entity. Using these measurements and the speed of light Petition 870250086012, dated 09 / 23 / 2025, page 103 / 362 95 / 158 known, the positioning entity can calculate the distance to UE 1004 as d = 1 / 2*c*(Node_Rx-Tx - UE_RxTx) = 1 / 2*c*(T_4 - T_1) - 1 / 2*c*(T_3 - T_2) (Equation 1), where c is the speed of light.

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

[0168] In one aspect, the positioning entity can calculate the 904 / 1004 location of the UE using a two-dimensional coordinate system; however, the aspects disclosed in the present invention are not limited in this way, and may also be applicable to determining locations using a three-dimensional coordinate system, if the extra dimension is desired. Additionally, although Figure 9 illustrates a 904 UE and three 902 network nodes and Figure 10 illustrates a 1004 UE and a 1002 network node, as will be recognized, there may be more 904 / 1004 UEs and more 902 / 1002 network nodes.

[0169] Support is contemplated in some communication systems (e.g., Rel-18 NR NTN WI) to support a single-satellite multi-RTT technique for network-verified UE location. For example, in some designs, multi-RTT can be used to support network-verified UE location in NTN assuming a single satellite in view. Although the multi-RTT technique for positioning in Petition 870250086012, dated 09 / 23 / 2025, page 104 / 362 Although 96 / 158 terrestrial networks are already supported by 3GPP, improvements are needed to account for the rapid movement of satellites, for example: • The durations of the received DL signal slot do not vary over time in the UE. • The EU has to constantly adjust the timing of autonomous transmissions.

[0170] Figure 11 illustrates a side-link RTT pattern 1100 according to disclosure aspects. In Figure 11, a fast-moving low Earth orbit (LEO) satellite 1102 is depicted at locations indicated as (1), (2), (3) and (4). At location (1), LEO satellite 1102 transmits a DL-PRS to RTT to UE 1104, denoted as RTT1. At location (2), LEO satellite 1102 receives a UL-PRS to RTT from UE 1104, denoted as RTT2. At location (3), LEO satellite 1102 transmits a DL-PRS to RTT to UE 1104, denoted as RTT3. At location (4), LEO satellite 1102 receives a UL-PRS for UE 1104 RTT, denoted as RTT4. In this scenario, the fast-moving nature of the LEO 1102 satellite provides sufficient spatial diversity for position estimation and / or position verification of UE 1104 (which, even though moving, is moving at a much lower speed than the LEO 1104 satellite and, in comparison, can be considered stationary).

[0171] Figure 12 illustrates terrestrial network (TN) timing 1200, according to aspects of this disclosure. In Figure 12, a gNB DL timing reference, a gNB UL timing reference, a UE DL timing reference and a reference of Petition 870250086012, dated 09 / 23 / 2025, p. 105 / 362 97 / 158 EU UL timing is depicted in relation to a subframe.

[0172] With reference to Figure TN, RTT = Tue-rxtx+TçnB-Rx-tx (Equation 2). UE reports Tue-rx-tx with a timestamp that is the slot number of a DL PRS, m. gNB reports TgNB_RX-TX with the timestamp which is the slot number of a SRS, n. The LMF can combine the two, provided that they are not too far apart. For this reason, UE and gNB reports are decoupled, that is, UE has the freedom to choose the subframes (SF - subframe) for which Tue-rx-tx are reported and gNB has the freedom to choose the received SRS for which TgNB_Rx-Tx are reported. Therefore, it is observed that Tue-rx-tx and TgNB_Rx-Tx do not need to be for the same TN subframe. The assumptions for the equation above (RTT =TuE-Rx-Tx+TgNB_Rx-Tx (Equation 2)) are that there is no change in timing advance (TA) of the UE between the time difference measurement time of the UE RX-TX, meo the transmission time of the SRS, n, that the same TA is applied to all slots in the subframe (SF) and the duration of the SF is constant in the uE.

[0173] Figure 13 illustrates a UE 1300 timing scenario for Tue-rx-tx, according to disclosure aspects. In Figure 13, a DL subframe of uE i significantly delays a uL subframe of uE i, which may have a greater tendency to occur in NTN placement. Several problems may occur if TN timing techniques for RTT are migrated to NTN placement.

[0174] For current definition of UE Rx-Tx time difference (Tue-rx-tx): Petition 870250086012, dated 09 / 23 / 2025, p. 106 / 362 98 / 158 • In TN, if jei are equal (that is, RTT is less than 0.5 ms and NTA-offset=0), the Rx-Tx time difference of UE is TA. • In NTN, the Rx-Tx time difference of UE is Tue_rx-tx = TA (of subframe j)-(ji) durations of the subframe in EU

[0175] More specifically, in some designs: Petition 870250086012, dated 09 / 23 / 2025, p. 107 / 362 99 / 158 Definition: The UE RX-TX timing difference can be defined as Tue-rx — Tue-tx, where: Tue-rx is the UE received timing of downlink subframe #ia from a TP, defined by the first time path detected. Tue-tx is the UE transmission timing of uplink subframe #j that is closest in time to subframe #i received from the TP. Multiple DL PRS features can be used to determine the start of a subframe of the first incoming path from the TP. For frequency band 1, the measurement reference point for Tue-rx will be the UE's Rx antenna connector, and the reference point for Tue-tx measurement will be the UE's Tx antenna connector. For frequency band 2, the measurement reference point for Tue-rx will be the UE's Rx antenna, and the reference point for Tue-tx measurement will be the UE's Tx antenna. RRC_CONNECTED applies to RRC_INACTIVE Table 1

[0176] In terms of subframe start, for NTN, it can be difficult to estimate the start of a subframe. Determining the start of the subframe using multiple DL-PRS can be challenging. Petition 870250086012, dated 09 / 23 / 2025, page 108 / 362 100 / 158 Furthermore, when multiple DL-PRS are used, ephemeris and GNSS may also need to be employed. Therefore, the benefit of such techniques in NTN positioning is questionable.

[0177] In terms of transmission time, the j subframe is unknown in NTN for the network as a whole, unless accurate TA is reported.

[0178] In terms of the use of subframes in general, the maximum RTT change in 1 ms can be 90 ns. UEs can thus have different TAs for slots in SF.

[0179] Figure 14 illustrates a gNB 1400 timing scenario for TUE-RX-TX, according to aspects of the disclosure. Several problems can occur if TN timing techniques for RTT are migrated to NTN placement.

[0180] For the current definition of gNB Rx-Tx time difference (Tçnb-rx-tx), when NTA_offset=0, it is the UE UL timing error of subframe i for both TN and NTN, as represented in Figure 14.

[0181] More specifically, in some designs: Petition 870250086012, dated 09 / 23 / 2025, page 109 / 362 101 / 158 Definition: The gNB Rx-Tx time difference is defined as TgNB-RX — TgNB-TX, where: TgNB-RX is the received timing of the transmission and reception point (TRP) of the uplink subframe #i containing the SRS associated with the UE, defined by the first detected time path. TgNB-TX is the transmission timing of the TRP of the downlink subframe #j that is closest in time to the subframe #i received from the UE. Multiple SRS positioning features can be used to determine the start of a subframe containing an SRS. The reference point for TgNB-RX should be: for base station type 1-C TS 38.104: the Rx antenna connector; for base station type 1-O or 2-O TS 38.104: the Rx antenna (i.e., the central location of the radiating region of the Rx antenna); for base station type 1-H TS 38.104: the Rx transceiver array boundary connector. The reference point for gNB-TX should be: for base station type 1-C TS 38.104: the Tx antenna connector, for the 1-O or 2-O type base station TS 38.104: the Tx antenna (i.e., the central location of the radiating region of the Tx antenna). Petition 870250086012, dated 09 / 23 / 2025, page 110 / 362 102 / 158 for TS 38.104 type 1-H base station: the Tx transceiver array boundary connector. Table 2

[0182] As will be recognized, for the gNB scenario, some of the same problems may occur if TN timing techniques for RTT are migrated to NTN placement compared to the UE side.

[0183] Aspects of disclosure are directed at Rx-Tx time differences between a UE and an NTN entity (e.g., LEO satellite) in various scenarios. Such aspects can provide several technical advantages, such as overcoming some or all of the problems that may arise if TN timing techniques for Rx-Tx time differences are mirrored for NTN positioning (e.g., more accurate subframe start time, a coupled Rx-Tx time difference report by the UE and the NTN entity, and so on), which can, in turn, improve the accuracy of the UE position estimate and / or the accuracy of the UE position verification.

[0184] Figure 15 illustrates an exemplary 1500 communications process, according to one aspect of the disclosure. The 1500 process in Figure 15 is carried out by a UE, such as UE 302.

[0185] With reference to Figure 15, in 1510, UE 302 (e.g., receiver 312 or 322 or 330, etc.) receives a downlink positioning reference signal (DL-PRS) from a non-terrestrial network entity (NTN) in the first symbol of a link timing period. Petition 870250086012, dated 09 / 23 / 2025, p. 111 / 362 103 / 158 descending. A means of achieving 1510 reception may include receiver 312 or 322 or 330, etc., of Figure 3A.

[0186] With reference to Figure 15, at 1520, UE 302 (e.g., transmitter 314 or 324 or 330-2, etc.) transmits an uplink probe reference signal (UL-SRS) to the NTN entity at one second symbol of an uplink timing period. A means of performing the 1520 transmission may include transmitter 314 or 324 or 330-2, etc., of Figure 3A.

[0187] With reference to Figure 15, at 1530, UE 302 (e.g., transmitter 314 or 324 or 330-2, etc.) transmits a measurement report comprising 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. In some designs, the start of the downlink timing period is based on one or more assumptions associated with the symbol duration for one or more symbols preceding the first symbol of the downlink timing period. For example, sufficient information to determine (i)-(iii) may include at least two of (i) to (iii), for example, (i)+(ii) or (i)+(iii) or (ii)+(iii) or (i)+(ii)+(iii).One means of carrying out the 1530 transmission may include transmitter 314 or 324 or 330-2, etc., of Figure 3A.

[0188] With reference to Figure 15, in some designs, the downlink timing period is a Petition 870250086012, dated 09 / 23 / 2025, page 112 / 362 104 / 158 is a descending link slot, a descending link subframe, or a descending link symbol, and the ascending link timing period is an ascending link slot, an ascending link subframe, or an ascending link symbol. In some designs, a timestamp granularity associated with the first timestamp, the second timestamp, or both corresponds to a respective granularity associated with the descending link timing period, the ascending link timing period, or both. For example, if the descending link timing period is a slot, then the first timestamp might be a slot indication; if the ascending link timing period is a subframe, then the second timestamp might be a subframe indication, and so on. In the case of timestamps at the symbol level, the indices of the initial ULSRS and / or DL-RS symbols (e.g., DL-PRS, etc.)In addition to slot / SFN indices, other data may be reported to the LMF. In some designs, this information may be included in the timestamps or reported separately to the LMF.

[0189] With reference to Figure 15, in some designs, a DL-PRS instance associated with 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 UL-SRS is among a subset of UL-SRS instances associated with a ULSRS resource configuration for the UE position estimation session. In some designs, the subset of DL-PRS instances and / or the subset of UL-SRS instances are configured by a Petition 870250086012, dated 09 / 23 / 2025, p. 113 / 362 105 / 158 location management function (LMF) or a wireless network component, or the subset of DL-PRS instances and / or the subset of UL-SRS instances are indicated or requested by the UE.

[0190] With reference to Figure 15, in some designs, the one or more assumptions comprise an assumption that the symbol duration for the one or more symbols preceding the first symbol of the downlink timing period corresponds to a predefined symbol duration based on a zero Doppler condition.

[0191] With reference to Figure 15, in some designs, the information comprises the time difference between Rx-Tx of the UE and the first time marking, or the information comprises the time difference between Rx-Tx of the UE and the second time marking, or the information comprises the time difference between Rx-Tx of the UE and the first time marking and the second time marking, or the information comprises the time difference between Rx-Tx of the UE and the Doppler information associated with DL-PRS and the first time marking, or the information comprises the time difference between Rx-Tx of the UE and the Doppler information associated with DL-PRS and the second time marking.

[0192] With reference to Figure 15, in some designs, UL-SRS is associated with an older UL-SRS instance that is subsequent to a DL-PRS instance associated with DL-PRS.

[0193] With reference to Figure 15, in some designs, the UE additionally transmits an indication of UE Rx-Tx time difference measurement capability which indicates the type of UE Rx-Tx time difference that Petition 870250086012, dated 09 / 23 / 2025, p. 114 / 362 106 / 158 The UE is able to measure and / or report to NTN for a position estimation entity (e.g., LMF) and receives a measurement report configuration for the information in response to the UE's Rx-Tx time difference measurement capability indication for NTN (e.g., from the position estimation entity, such as LMF). For example, the UE's Rx-Tx time difference measurement capability indication may indicate the exact definition of the UE's Rx-Tx time difference and associated reports that the UE is able to measure / report. For example, if a legacy Rx-Tx time difference is measured, the UE may additionally add more Doppler information (e.g., so that the position estimation entity can apply a Doppler-based adjustment 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 is able to measure / report a new Rx-Tx time difference without expressly indicating the Doppler to the position estimation entity.

[0194] With reference to Figure 15, in some designs, the measurement report additionally includes an indication of a measurement reporting configuration associated with the information (for example, if the UE is not instructed to use a specific measurement reporting configuration, a measurement reporting configuration selected / used by the UE may instead be indicated in the measurement report).

[0195] Figure 16 illustrates an exemplary 1600 communication process, according to one aspect Petition 870250086012, dated 09 / 23 / 2025, p. 115 / 362 107 / 158 of the disclosure. Process 1600 in Figure 16 is performed by an NTN entity, such as BS 304, NTN 1102 entity, etc.

[0196] With reference to Figure 16, in 1610, the NTN entity (e.g., receiver 352 or 362 or 370-1, etc.) receives an uplink probe reference signal (UL-SRS) from a user equipment (UE) in a first symbol of an uplink timing period. A means of performing 1610 reception may include receiver 352 or 362 or 370-1, etc., of Figure 3B.

[0197] With reference to Figure 16, in 1620, the NTN entity (e.g., transmitter 354 or 364 or 3702, etc.) transmits a measurement report comprising sufficient information to determine (i) a receive-transmit (Rx-Tx) time difference of the NTN entity 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 the downlink timing period is based on one or more assumptions associated with the symbol duration for one or more symbols preceding the first symbol of the uplink timing period.For example, the information sufficient to determine (i) -(iii) may include at least two of (i) to (iii), for example, (i) + (ii) or (i) + (iii) or (ii) + (iii) or (i) + (ii) + (iii). A means of carrying out the 1620 transmission may include transmitter 354 or 364 or 370-2, etc., of Figure 3B. Petition 870250086012, dated 09 / 23 / 2025, page 116 / 362 108 / 158

[0198] With reference to Figure 16, in some designs, the downlink timing period comprises 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. In some designs, the UL-SRS is associated with an older UL-SRS instance that is subsequent to a 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 a DL positioning reference signal (DL-PRS) or a DL channel state information RS (DL-CSI-RS) (e.g., or any other type of DL-RS).

[0199] With reference to Figure 16, in some designs, the start of the uplink timing period is determined based on a UL-SRS receive timing that begins within the uplink timing period.

[0200] With reference to Figure 16, in some designs, 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. In some designs, a timestamp granularity associated with the first timestamp, the second timestamp, or both corresponds to a respective granularity associated with the timing period. Petition 870250086012, dated 09 / 23 / 2025, p. 117 / 362 109 / 158 of downlink timing, to the uplink timing period, or to both. For example, if the downlink timing period is a slot, then the first timestamp might be a slot indication; if the uplink timing period is a subframe, then the second timestamp might be a subframe indication, and so on. In the case of symbol-level timestamps, the indices of the initial ULSRS and / or DL-RS symbols (e.g., DL-PRS, etc.), in addition to the slot / SFN indices, may be reported to the LMF. In some designs, this information may be included in the timestamp or reported separately to the LMF.

[0201] With reference to Figure 16, in some designs, a UL-SRS instance associated with the UL-SRS is among a subset of UL-SRS instances associated with a UL-SRS resource configuration for a UE position estimation session. In some designs, the subset of UL-SRS instances is configured by a location management function (LMF) or a wireless network component, or the subset of UL-SRS instances is indicated or requested by the UE.

[0202] With reference to Figure 16, in some designs, the one or more assumptions comprise an assumption that the symbol duration for the one or more symbols preceding the first symbol of the downlink timing period corresponds to a predefined symbol duration based on a zero Doppler condition.

[0203] With reference to Figure 16, in some designs, the information comprises the NTN entity Rx-Tx time difference and the first timestamp, or Petition 870250086012, dated 09 / 23 / 2025, p. 118 / 362 110 / 158 the information comprises the Rx-Tx time difference of an NTN entity and the second timestamp, or the information comprises the first timestamp and the second timestamp.

[0204] Figure 17 illustrates an exemplary 1700 communications process, according to one aspect of disclosure. The 1700 process in Figure 17 is performed by a position estimation entity. In some designs, the position estimation entity may correspond to a network component (e.g., an integrated LMF in gNB / BS 304 / NTN entity or O-RAN component or a remote location server, such as network entity 306, etc.). In other designs, the position estimation entity may correspond to another UE (e.g., side link anchor UE) or to the target UE itself (e.g., for UE-based position estimation, in which case any of the Rx / Tx operations between the UE and the position estimation entity may correspond to the transfer of information between different logical components of the UE via a data bus, etc.).) or to the NTN entity itself (for example, in which case any Rx / Tx operations between the NTN entity and the position estimation entity may correspond to the transfer of information between different logical components of the NTN entity via a data bus, etc.). In another aspect, process 1700 in Figure 17 in the position estimation entity may correspond to a process performed in parallel with process 1500 in Figure 15 in the UE.

[0205] With reference to Figure 17, in 1710, the position estimation entity (e.g., receiver 312 Petition 870250086012, dated 09 / 23 / 2025, p. 119 / 362 111 / 158 or 322 or 352 or 362 or 330-1 or 370-1 or data bus 334 or data bus 382 or network transceiver(s) 380 or 390, etc.) receives a measurement report comprising 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 receiving a downlink positioning reference symbol (DL-PRS) from a non-terrestrial network entity (NTN) and a second timestamp corresponding to the start of an uplink timing period associated with transmitting an uplink probing reference signal (UL-SRS) to the NTN entity, (ii) to the first timestamp and (iii) to the second timestamp; For example, sufficient information to determine (i)-(iii) may include at least two of (i) to (iii), for example, (i)+(ii) or (i)+(iii) or (ii)+(iii) or (i)+(ii)+(iii).A means of performing 1710 reception may include receiver 312 or 322 or 352 or 362 or 330-1 or 370-1 or data bus 334 or data bus 382 or network transceiver(s) 380 or 390, etc., of Figures 3A to 3C, depending on the implementation of the position estimation entity as mentioned above.

[0206] With reference to Figure 17, in 1720, the position estimation entity (e.g., processor(s) 332 or 384 or 394, Rx-Tx component 342 or 388 or 398, etc.) determines a round-trip travel time (RTT) between the UE and the NTN entity based, at least in part, on the information. A means to perform the Petition 870250086012, dated 09 / 23 / 2025, page 120 / 362 112 / 158 determination of 1720 may include processor(s) 332 or 384 or 394, Rx-Tx component 342 or 388 or 398, etc., from Figures 3A to 3C, depending on the implementation of the position estimation entity as noted above.

[0207] With reference to Figure 17, in some designs, the position estimation entity may additionally determine a subset of UL-SRS instances associated with the UL-SRS resource configuration for a UE position estimation session and may transmit an indication of the subset of UL-SRS instances to the UE and the NTN entity to facilitate the transmission and measurement of one or more UL-SRSs on the UL-SRS instances by the UE and the NTN entity, respectively. In this way, particular UL-SRS instances.

[0208] With reference to Figure 17, in some designs, the downlink timing period is a downlink slot or a downlink subframe, and the uplink timing period is an uplink slot or an uplink subframe. In some designs, a timestamp granularity associated with the first timestamp, the second timestamp, or both corresponds to a respective granularity associated with the downlink timing period, the uplink timing period, or both. For example, if the downlink timing period is a slot, then the first timestamp might be a slot indication; if the uplink timing period is a subframe, then the second timestamp might be a subframe indication, and so on. In the case of timestamps at the level Petition 870250086012, dated 09 / 23 / 2025, pp. 121 / 362 113 / 158 of the symbol, the initial UL-SRS and / or DL-RS symbol indices (e.g., DL-PRS, etc.), in addition to the slot / SFN indices, may be reported to the LMF. In some designs, this information may be included in the timestamp or reported separately to the LMF.

[0209] With reference to Figure 17, in some designs, the information comprises the time difference between the Rx-Tx of the UE and the first time marking, or the information comprises the time difference between the Rx-Tx of the UE and the second time marking, or the information comprises the first time marking and the second time marking, or the information comprises the time difference between the Rx-Tx of the UE and the Doppler information associated with the DL-PRS.

[0210] With reference to Figure 17, in some designs, the UL-SRS is associated with an older UL-SRS instance that is subsequent to a DL-PRS instance associated with the DL-PRS.

[0211] Figure 18 illustrates an exemplary 1800 communications process, according to one aspect of disclosure. The 1800 process in Figure 18 is performed by a position estimation entity. In some designs, the position estimation entity may correspond to a network component (e.g., an integrated LMF in gNB / BS 304 / NTN entity or O-RAN component or a remote location server, such as network entity 306, etc.). In other designs, the position estimation entity may correspond to another UE (e.g., side link anchor UE) or to the target UE itself (e.g., for UE-based position estimation, in which case any of the Rx / Tx operations between the UE and the entity of Petition 870250086012, dated 09 / 23 / 2025, pp. 122 / 362 114 / 158 position estimation may correspond to the transfer of information between different logical components of the UE through a data bus, etc.) or to the NTN entity itself (for example, in which case any Rx / Tx operations between the NTN entity and the position estimation entity may correspond to the transfer of information between different logical components of the NTN entity through a data bus, etc.). In another aspect, process 1800 in Figure 18 in the position estimation entity may correspond to a process performed in parallel with process 1600 in Figure 16 in the NTN entity.

[0212] With reference to Figure 18, in 1810, the position estimation entity (e.g., receiver 312 or 322 or 352 or 362 or 330-1 or 370-1 or data bus) 334 or data bus 382 or network transceiver(s) 380 or 390, etc.) receives a measurement report comprising sufficient information to determine (i) a receive-transmit (Rx-Tx) time difference of an NTN entity 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. For example, sufficient information to determine (i)(iii) may include at least two of (i) to (iii), for example, (i)+(ii) or (i)+(iii) or (ii)+(iii) or (i)+(ii)+(iii). A means of achieving 1810 reception may include receiver 312 or 322 or 352 or 362 or 330-1 or 370-1 or data bus 334 or data bus 382 or Petition 870250086012, dated 09 / 23 / 2025, p. 123 / 362 115 / 158 network transceiver(s) 380 or 390, etc., from Figures 3A to 3C, depending on the implementation of the position estimation entity as mentioned above.

[0213] With reference to Figure 18, in 1820, the position estimation entity (e.g., processor(s) 332 or 384 or 394, Rx-Tx component 342 or 388 or 398, etc.) determines a round-trip time (RTT) between the user equipment (UE) and the NTN entity based, at least in part, on the information. A means of performing the determination of 1820 may include processor(s) 332 or 384 or 394, Rx-Tx component 342 or 388 or 398, etc., from Figures 3A to 3C, depending on the implementation of the position estimation entity as noted above.

[0214] With reference to Figure 18, in some designs, the downlink timing period comprises a 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.

[0215] With reference to Figure 18, in some designs the UL-SRS is associated with an older UL-SRS instance that is subsequent to a DL-PRS instance associated with the DL-PRS or within the same system subframe number and / or the same slot index.

[0216] With reference to Figure 18, in some designs, the start of the uplink timing period is determined based on a timing of Petition 870250086012, dated 09 / 23 / 2025, pp. 124 / 362 116 / 158 reception of the UL-SRS that begins within the uplink timing period.

[0217] With reference to Figure 18, in some designs, the downlink timing period is a downlink slot or a downlink subframe, and the uplink timing period is an uplink slot or an uplink subframe. In some designs, a timestamp granularity associated with the first timestamp, the second timestamp, or both corresponds to a respective granularity associated with the downlink timing period, the uplink timing period, or both. For example, if the downlink timing period is a slot, then the first timestamp might be a slot indication; if the uplink timing period is a subframe, then the second timestamp might be a subframe indication, and so on.In the case of symbol-level timestamps, the indexes of the initial UL-SRS and / or DL-RS symbols (e.g., DL-PRS, etc.), in addition to the slot / SFN indexes, may be reported to the LMF. In some designs, this information may be included in the timestamp or reported separately to the LMF.

[0218] Figure 19 illustrates an example 1900 implementation of processes 1500 to 1800 in Figures 15 and 18, according to aspects of the disclosure.

[0219] With reference to Figure 19, in a specific example, specific to the UE Rx-Tx time difference, a new type (type 2) UE Rx-Tx time difference can be defined. A UE Rx-Tx time difference Petition 870250086012, dated 09 / 23 / 2025, p. 125 / 362 117 / 158 type 2 in NTN is the time gap between the received timing of subframe (slot) i of a transmission point (TP) and the transmission timing of a subframe (slot) of UL j of the TP, represented in Figure 19 as T1. By definition or specification, subframe / slot j containing an SRS. By definition or specification, subframe / slot i must contain a PRS that is closed to subframe / slot j at time in UE. The received timing is determined by the PRS DL that starts within the subframe. When determining the start timing of a subframe / slot, the nominal symbol duration (e.g., assuming zero Doppler shift) is assumed for symbols before the start of the PRS / SRS in the subframe / slot. The nominal symbol duration is the duration of a symbol in gNB, as defined by 38.211. The EU reports the SF / slot transmission index jeo SF / slot index i or the SF / slot index jea difference between the index of SF / slot iej, or the SF / slot iea difference index between ie j. LMF or gNB sets a minimum set of SRS for which UE Rx-Tx must be measured and reported. Alternatively, UE indicates to gNB in ​​advance a minimum set of SRS for which UE Rx-Tx must be measured and reported. Although described above in relation to the UE Rx-Tx time difference, it will be recognized that a similar procedure can be implemented in the NTN entity to derive the NTN Rx-Tx time difference.

[0220] With reference to Figure 19, in another specific example, specific to the UE Rx-Tx time difference, a new type (type 2) UE Rx-Tx time difference is defined. The UE Rx-Tx time difference is the time difference of the timing received from Petition 870250086012, dated 09 / 23 / 2025, pp. 126 / 362 118 / 158 subframe / slot i of a TP and the transmission timing of subframe / slot i of the TP (i.e., TA of SF / slot i). The received timing of a subframe / slot can be determined by one or multiple PRS of the TP. The UE reports the timestamp, the subframe / slot index of the SRS, along with the UE Rx-Tx time difference. LMF or gNB sets a minimum set of SRS for which the UE Rx-Tx should be measured and reported. Alternatively, the UE indicates to gNB in ​​advance a minimum set of SRS for which the UE Rx-Tx should be measured and reported. When determining the start timing of a subframe / slot, the nominal symbol duration is assumed for symbols before the start of the PRS / SRS in the subframe / slot. The nominal duration of the symbol is the duration of a symbol in gNB, as defined by 38.211.Although described above in relation to the Rx-Tx time difference of the EU, it will be recognized that a similar procedure can be implemented in the NTN entity to derive the Rx-Tx time difference of the NTN.

[0221] With reference to Figure 19, in another specific example, specific to the UE Rx-Tx time difference, the legacy UE-Rx-Tx time difference (as used in TN placement) with enhancements can be used. The UE reports the SF / slot transmission index jeo or the SF / slot index jea difference between the SF / slot index iej, or the SF / slot index iea difference between ie j. The UE reports the Doppler of the signal of DL, along with each UE, LMF, or gNB Rx-Tx time difference, establishes a minimum set of SRS for which UE Rx-Tx must be measured and reported. Alternatively, UE indicates to gNB in ​​advance a minimum set of SRS for Petition 870250086012, dated 09 / 23 / 2025, page 127 / 362 119 / 158 which EU Rx-Tx must be measured and reported. When determining the start timing of a subframe / slot, the nominal symbol duration is assumed for symbols before the start of the PRS / SRS in the subframe / slot. The nominal symbol duration is the duration of a symbol in gNB, as defined by 38.211. Although described above in relation to the EU Rx-Tx timing difference, it will be recognized that a similar procedure can be implemented in the NTN entity to derive the NTN Rx-Tx timing difference.

[0222] With reference to Figure 19, in another specific example, specific to the UE Rx-Tx time difference, both a new type (type 2) UE Rx-Tx time difference and a legacy UE Rx-Tx time difference can be supported. In this case, UE or LMF indicates which type should be reported (e.g., based on UE capacity, etc.). Although described above in relation to the UE Rx-Tx time difference, it will be recognized that a similar procedure can be implemented in the NTN entity to derive the NTN Rx-Tx time difference.

[0223] In the detailed description above, it can be seen that different attributes are grouped into examples. This method of disclosure should not be understood as an intention that the example clauses have more attributes than are explicitly mentioned in each clause. Instead, the various aspects of the disclosure may include fewer than the totality of the attributes of an individual disclosed example clause. Therefore, the following clauses should be considered incorporated into the description, where each clause by itself can serve as a separate example. Although each dependent clause may refer in the clauses to a Petition 870250086012, dated 09 / 23 / 2025, pp. 128 / 362 120 / 158 specific combination with one of the other clauses, the aspect(s) of that dependent clause are not limited to the specific combination. It will be recognized that other example clauses may also include a combination of the aspect(s) of the dependent clause with the subject matter of any other dependent or independent clause, or a combination of any attribute with other dependent and independent clauses. The various aspects disclosed in the present invention expressly include such combinations, unless it is explicitly stated or can be easily inferred that a specific combination is not intended (for example, contradictory aspects, such as defining an element as an electrical insulator and an electrical conductor). Furthermore, it is also intended that aspects of a clause may be included in any other independent clause, even if the clause is not directly dependent on the independent clause.

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

[0225] Clause 1. A method of operating a user equipment (UE) comprising: receiving a downlink positioning reference signal (DLPRS) from a non-terrestrial network entity (NTN) on a first symbol of a downlink timing period; transmitting an uplink probing reference signal (UL-SRS) to the NTN entity on a second symbol of an uplink timing period; and transmitting a measurement report comprising sufficient information to determine (i) a receive-transmit time difference (Rx-Tx) Petition 870250086012, dated 09 / 23 / 2025, page 129 / 362 121 / 158 receive-transmit) of the EU 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) to the first timestamp and (iii) to the second timestamp, wherein the start of the downlink timing period is based on one or more assumptions associated with the symbol duration for one or more symbols preceding the first symbol of the downlink timing period.

[0226] Clause 2. The method of clause 1, wherein the downlink timing period is a downlink slot or a downlink subframe or a downlink symbol, and wherein the uplink timing period is an uplink slot or an uplink subframe or an uplink symbol.

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

[0228] Clause 4. The method of any of clauses 1 to 3, wherein a DL-PRS instance associated with the 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 where a UL-SRS instance associated with the UL-SRS is among a subset of UL-SRS instances associated with a Petition 870250086012, dated 09 / 23 / 2025, pp. 130 / 362 122 / 158 UL-SRS resource configuration for the UE position estimation session.

[0229] Clause 5. The method of clause 4, wherein the subset of DL-PRS instances and / or the subset of UL-SRS instances are configured by a location management function (LMF) or a wireless network component, or wherein the subset of DL-PRS instances and / or the subset of UL-SRS instances are indicated or requested by the UE.

[0230] Clause 6. The method of any of clauses 1 to 5, wherein one or more assumptions comprise an assumption that the symbol duration for the one or more symbols preceding the first symbol of the downlink timing period corresponds to a predefined symbol duration based on a zero Doppler condition.

[0231] Clause 7. The method of any of clauses 1 to 6, wherein the information comprises the time difference between Rx-Tx of UE and the first time marking, or wherein the information comprises the time difference between Rx-Tx of UE and the second time marking, or wherein the information comprises the time difference between Rx-Tx of UE and the first time marking and the second time marking, or wherein the information comprises the time difference between Rx-Tx of UE and the Doppler information associated with DL-PRS and the first time marking, or wherein the information comprises the time difference between Rx-Tx of UE and the Doppler information associated with DL-PRS and the second time marking. Petition 870250086012, dated 09 / 23 / 2025, pp. 131 / 362 123 / 158

[0232] Clause 8. The method of any of clauses 1 to 7, where the UL-SRS is associated with an older UL-SRS instance that is subsequent to a DL-PRS instance associated with the DL-PRS.

[0233] Clause 9. The method of any of clauses 1 to 8 which further comprises: transmitting an indication of EU Rx-Tx time difference measurement capability indicating a type of EU Rx-Tx time difference that the EU is capable of measuring and / or reporting to NTN for a position estimation entity; and receiving a measurement reporting configuration for the information in response to the indication of EU Rx-Tx time difference measurement capability to NTN.

[0234] Clause 10. The method of any of clauses 1 to 9, wherein the measurement report additionally comprises an indication of a measurement report configuration associated with the information.

[0235] Clause 11. A method of operating a non-terrestrial network entity (NTN) comprising: receiving an uplink probe reference signal (ULSRS) from a user equipment (UE) at a first symbol of an uplink timing period; and transmitting a measurement report comprising 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) at the first timestamp and (iii) at the second timestamp, in Petition 870250086012, dated 09 / 23 / 2025, pp. 132 / 362 124 / 158 that the start of the downlink timing period is based on one or more assumptions associated with the symbol duration for one or more symbols preceding the first symbol of the uplink timing period.

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

[0237] Clause 13. The method of clause 12, where the UL-SRS is associated with an older UL-SRS instance that is subsequent to a DL-RS instance associated with the DL-RS or within the same system subframe number and / or the same slot index.

[0238] Clause 14. The method of either of clauses 12 to 13, wherein DL-RS is a DL positioning reference signal (DL-PRS) or a DL channel state information RS (DL-CSI-RS).

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

[0240] Clause 16. The method of any of clauses 11 to 15, wherein the downlink timing period is a downlink slot or a downlink subframe or a downlink symbol, and wherein the uplink timing period is a Petition 870250086012, dated 09 / 23 / 2025, pp. 133 / 362 125 / 158 ascending link slot or an ascending link subframe or an ascending link symbol.

[0241] Clause 17. The method of any of clauses 11 to 16, wherein a 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.

[0242] Clause 18. The method of clause 17, wherein the subset of UL-SRS instances is configured by a location management function (LMF) or a wireless network component, or wherein the subset of UL-SRS instances is indicated or requested by the UE.

[0243] Clause 19. The method of any of clauses 11 to 18, wherein one or more assumptions comprise an assumption that the symbol duration for the one or more symbols preceding the first symbol of the downlink timing period corresponds to a predefined symbol duration based on a zero Doppler condition.

[0244] Clause 20. The method of any of clauses 11 to 19, wherein the information comprises the NTN entity's Rx-Tx time difference and the first time stamp, or wherein the information comprises the NTN entity's Rx-Tx time difference and the second time stamp, or wherein the information comprises the first time stamp and the second time stamp.

[0245] Clause 21. A method of operation of a position estimation entity comprising: receiving a measurement report comprising sufficient information to determine (i) a difference in receiving time and Petition 870250086012, dated 09 / 23 / 2025, pp. 134 / 362 126 / 158 User Equipment (UE) transmission (Rx-Tx) 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 entity (NTN) and a second timestamp corresponding to the start of an uplink timing period associated with the transmission of an uplink probing reference signal (UL-SRS) to the NTN entity, (ii) to the first timestamp and (iii) to the second timestamp; and determine a round-trip time (RTT) between the UE and the NTN entity based, at least in part, on the information.

[0246] Clause 22. The method of clause 21 which further comprises: determining a subset of UL-SRS instances associated with the UL-SRS resource configuration for a UE position estimation session; and transmitting an indication of the subset of UL-SRS instances to the UE and the NTN entity to facilitate transmission and measurement of one or more UL-SRSs on the UL-SRS instances by the UE and the NTN entity, respectively.

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

[0248] Clause 24. The method of any of clauses 21 to 23, wherein the information comprises the Petition 870250086012, dated 09 / 23 / 2025, pp. 135 / 362 127 / 158 time difference between Rx-Tx of UE and the first time marking, or wherein the information comprises the time difference between Rx-Tx of UE and the second time marking, or wherein the information comprises the first time marking and the second time marking, or wherein the information comprises the time difference between Rx-Tx of UE and the Doppler information associated with DL-PRS.

[0249] Clause 25. The method of any of clauses 21 to 24, where the UL-SRS is associated with an older UL-SRS instance that is subsequent to a DL-PRS instance associated with the DL-PRS.

[0250] Clause 26. A method of operation of a position estimation entity comprising: receiving a measurement report comprising sufficient information to determine (i) a receive-transmit (Rx-Tx) time difference from an NTN entity 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 a round-trip time (RTT) between a user equipment (UE) and the NTN entity based, at least in part, on the information.

[0251] Clause 27. The method of clause 26, wherein the downlink timing period comprises a downlink positioning reference signal (DL-RS), or wherein the downlink timing period is associated with the same number of Petition 870250086012, dated 09 / 23 / 2025, pp. 136 / 362 128 / 158 subframe of the system and / or the same slot index as the uplink timing period.

[0252] Clause 28. The method of clause 27, where the UL-SRS is associated with an older UL-SRS instance that is subsequent to a DL-RS instance associated with the DL-RS or within the same system subframe number and / or the same slot index.

[0253] Clause 29. The method of any of clauses 26 to 28, wherein the start of the uplink timing period is determined based on a UL-SRS receive timing that begins within the uplink timing period.

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

[0255] Clause 31. A user equipment (UE) comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and to the at least one transceiver, wherein the at least one processor is configured to: receive, through the at least one transceiver, a downlink positioning reference signal (DL-PRS) from a non-terrestrial network entity (NTN) at the first symbol of a downlink timing period; transmit, through the at least one transceiver, an uplink polling reference signal (UL-SRS) to Petition 870250086012, dated 09 / 23 / 2025, pp. 137 / 362 129 / 158 the NTN entity in a second symbol of an uplink timing period; and transmit, through at least one transceiver, a measurement report comprising sufficient information to determine (i) a receive-transmit (Rx-Tx) UE time difference between a first timestamp corresponding to a start of the downlink timing period and a second timestamp corresponding to a start of the uplink timing period, (ii) to the first timestamp and (iii) to the second timestamp, wherein the start of the downlink timing period is based on one or more assumptions associated with the symbol duration for one or more symbols preceding the first symbol of the downlink timing period.

[0256] Clause 32. The EU of clause 31, wherein the downlink timing period is a downlink slot or a downlink subframe or a downlink symbol, and wherein the uplink timing period is an uplink slot or an uplink subframe or an uplink symbol.

[0257] Clause 33. The EU of clause 32, wherein a timestamp granularity associated with the first timestamp, the second timestamp or both corresponds to a respective granularity associated with the downlink timing period, the uplink timing period or both.

[0258] Clause 34. The EU of any of clauses 31 to 33, where a DL-PRS instance associated with the DL-PRS is among a subset of DL-PRS instances Petition 870250086012, dated 09 / 23 / 2025, pp. 138 / 362 130 / 158 associated with a DL-PRS resource configuration for a UE position estimation session and / or where a UL-SRS instance associated with UL-SRS is among a subset of UL-SRS instances associated with a UL-SRS resource configuration for the UE position estimation session.

[0259] Clause 35. The UE of clause 34, wherein the subset of DL-PRS instances and / or the subset of UL-SRS instances are configured by a location management function (LMF) or a wireless network component, or wherein the subset of DL-PRS instances and / or the subset of UL-SRS instances are indicated or requested by the UE.

[0260] Clause 36. The EU of any of clauses 31 to 35, wherein one or more assumptions comprise an assumption that the symbol duration for the one or more symbols preceding the first symbol of the downlink timing period corresponds to a predefined symbol duration based on a zero Doppler condition.

[0261] Clause 37. The UE of any of clauses 31 to 36, wherein the information comprises the UE Rx-Tx time difference and the first time stamp, or wherein the information comprises the UE Rx-Tx time difference and the second time stamp, or wherein the information comprises the UE Rx-Tx time difference and the first time stamp and the second time stamp, or wherein the information comprises the UE Rx-Tx time difference and the Doppler information associated with the DL-PRS and the first time stamp, or wherein Petition 870250086012, dated 09 / 23 / 2025, pp. 139 / 362 131 / 158 that the information includes the UE RxTx time difference and the Doppler information associated with DL-PRS and the second time marking.

[0262] Clause 38. The UE of any of clauses 31 to 37, where the UL-SRS is associated with an older UL-SRS instance that is subsequent to a DL-PRS instance associated with the DL-PRS.

[0263] Clause 39. The UE of any of clauses 31 to 38, wherein at least one processor is additionally configured to: transmit, through at least one transceiver, an indication of UE Rx-Tx time difference measurement capability that indicates a type of UE Rx-Tx time difference that the UE is capable of measuring and / or reporting to NTN for a position estimation entity; and receive, through at least one transceiver, a measurement reporting configuration for the information in response to the UE Rx-Tx time difference measurement capability indication to NTN.

[0264] Clause 40. The EU of any of clauses 31 to 39, wherein the measurement report additionally includes an indication of a measurement report configuration associated with the information.

[0265] Clause 41. A non-terrestrial network entity (NTN) comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and to the at least one transceiver, wherein the at least one processor is configured to: receive, through the at least one transceiver, an uplink polling reference signal (UL-SRS) from a user equipment (UE) on a first symbol of a period of Petition 870250086012, dated 09 / 23 / 2025, pp. 140 / 362 132 / 158 uplink timing; and transmit, through at least one transceiver, a measurement report comprising 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) 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 duration for one or more symbols preceding the first symbol of the uplink timing period.

[0266] Clause 42. The NTN entity of clause 41, wherein the downlink timing period comprises a downlink positioning reference signal (DL-RS), or wherein the downlink timing period is associated with the same system subframe number and / or the same slot index as the uplink timing period.

[0267] Clause 43. The NTN entity of clause 42, where the UL-SRS is associated with an older UL-SRS instance that is subsequent to a DL-RS instance associated with the DL-RS or within the same system subframe number and / or the same slot index.

[0268] Clause 44. The NTN entity of either clause 42 and 43, where DL-RS is a DL positioning reference signal (DL-PRS) or a DL channel state information RS (DL-CSI-RS). Petition 870250086012, dated 09 / 23 / 2025, pp. 141 / 362 133 / 158

[0269] Clause 45. The NTN of any of clauses 41 to 44, wherein the start of the uplink timing period is determined based on a UL-SRS receive timing that begins within the uplink timing period.

[0270] Clause 46. The NTN entity of any of clauses 41 to 45, wherein the downlink timing period is a downlink slot or a downlink subframe or a downlink symbol, and wherein the uplink timing period is an uplink slot or an uplink subframe or an uplink symbol.

[0271] Clause 47. The NTN entity of any of clauses 41 to 46, where a UL-SRS instance associated with UL-SRS is among a subset of UL-SRS instances associated with a ULSRS resource configuration for a UE position estimation session.

[0272] Clause 48. The NTN entity of clause 47, wherein the subset of UL-SRS instances is configured by a location management function (LMF) or a wireless network component, or wherein the subset of UL-SRS instances is indicated or requested by the UE.

[0273] Clause 49. The NTN entity of any of clauses 41 to 48, wherein one or more assumptions comprise an assumption that the symbol duration for the one or more symbols preceding the first symbol of the downlink timing period corresponds to a predefined symbol duration based on a zero Doppler condition. Petition 870250086012, dated 09 / 23 / 2025, pp. 142 / 362 134 / 158

[0274] Clause 50. The NTN entity of any of clauses 41 to 49, wherein the information comprises the NTN entity's Rx-Tx time difference and the first time stamp, or wherein the information comprises the NTN entity's Rx-Tx time difference and the second time stamp, or wherein the information comprises the first time stamp and the second time stamp.

[0275] Clause 51. A position estimation entity comprising: a memory; at least one transceiver;and at least one processor communicatively coupled to memory and at least one transceiver, wherein the at least one processor is configured to: receive, through the at least one transceiver, a measurement report comprising 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 receipt of a downlink positioning reference symbol (DL-PRS) from a non-terrestrial network entity (NTN) and a second timestamp corresponding to the start of an uplink timing period associated with the transmission of an uplink probing reference signal (UL-SRS) to the NTN entity, (ii) to the first timestamp and (iii) to the second timestamp;and to determine a round-trip travel time (RTT) between the EU and the NTN entity based, at least in part, on the information.

[0276] Clause 52. The position estimation entity of clause 51, where at least one processor Petition 870250086012, dated 09 / 23 / 2025, pp. 143 / 362 135 / 158 is additionally configured to: determine a subset of UL-SRS instances associated with the UL-SRS resource configuration for a UE position estimation session; and transmit, through at least one transceiver, an indication of the subset of UL-SRS instances to the UE and the NTN entity to facilitate the transmission and measurement of one or more UL-SRSs on the UL-SRS instances by the UE and the NTN entity, respectively.

[0277] Clause 53. The position estimating entity of any of clauses 51 to 52, wherein the downlink timing period is a downlink slot or a downlink subframe or a downlink symbol, and wherein the uplink timing period is an uplink slot or an uplink subframe or an uplink symbol.

[0278] Clause 54. The position estimation entity of any of clauses 51 to 53, wherein the information comprises the time difference between Rx-Tx of UE and the first time marking, or wherein the information comprises the time difference between Rx-Tx of UE and the second time marking, or wherein the information comprises the first time marking and the second time marking, or wherein the information comprises the time difference between Rx-Tx of UE and the Doppler information associated with DL-PRS.

[0279] Clause 55. The position estimation entity of any of clauses 51 to 54, where ULSRS is associated with an older UL-SRS instance that is subsequent to a DL-PRS instance associated with DL-PRS. Petition 870250086012, dated 09 / 23 / 2025, pp. 144 / 362 136 / 158

[0280] Clause 56. A position estimation entity comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and to the at least one transceiver, wherein the at least one processor is configured to: receive, through the at least one transceiver, a measurement report comprising sufficient information to determine (i) a receive-transmit (Rx-Tx) time difference of an NTN entity 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 a round-trip time (RTT) between a user equipment (UE) and the NTN entity based, at least in part, on the information.

[0281] Clause 57. The position estimation entity of clause 56, wherein the downlink timing period comprises a downlink positioning reference signal (DL-RS), or wherein the downlink timing period is associated with the same system subframe number and / or the same slot index as the uplink timing period.

[0282] Clause 58. The position estimation entity in clause 57, where the UL-SRS is associated with an older UL-SRS instance that is subsequent to a DL-RS instance associated with the DL-RS or within the same system subframe number and / or the same slot index. Petition 870250086012, dated 09 / 23 / 2025, pp. 145 / 362 137 / 158

[0283] Clause 59. The position estimation entity of any of clauses 56 to 58, wherein the start of the uplink timing period is determined based on a UL-SRS receive timing that begins within the uplink timing period.

[0284] Clause 60. The position estimating entity of any of clauses 56 to 59, wherein the downlink timing period is a downlink slot or a downlink subframe or a downlink symbol, and wherein the uplink timing period is an uplink slot or an uplink subframe or an uplink symbol.

[0285] Clause 61. A user equipment (UE) comprising: means for receiving a downlink positioning reference signal (DL-PRS) from a non-terrestrial network entity (NTN) on a first symbol of a downlink timing period; means for transmitting an uplink probing reference signal (UL-SRS) to the NTN entity on a second symbol of an uplink timing period; and means for transmitting a measurement report comprising sufficient information to determine (i) a UE receive-transmit time difference (Rx-Tx) 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, on which the start of the downlink timing period is based. Petition 870250086012, dated 09 / 23 / 2025, pp. 146 / 362 138 / 158 in one or more assumptions associated with the symbol duration for one or more symbols preceding the first symbol of the downlink timing period.

[0286] Clause 62. The EU of clause 61, wherein the downlink timing period is a downlink slot or a downlink subframe or a downlink symbol, and wherein the uplink timing period is an uplink slot or an uplink subframe or an uplink symbol.

[0287] Clause 63. The EU of clause 62, wherein a timestamp granularity associated with the first timestamp, the second timestamp or both corresponds to a respective granularity associated with the downlink timing period, the uplink timing period or both.

[0288] Clause 64. The UE of any of clauses 61 to 63, where a DL-PRS instance associated with the 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 where a UL-SRS instance associated with the UL-SRS is among a subset of UL-SRS instances associated with a UL-SRS resource configuration for the UE position estimation session.

[0289] Clause 65. The EU of clause 64, wherein the subset of DL-PRS instances and / or the subset of UL-SRS instances are configured by a location management function (LMF) or a wireless network component, or wherein the subset of DL-PRS instances Petition 870250086012, dated 09 / 23 / 2025, pp. 147 / 362 139 / 158 and / or the subset of UL-SRS instances are indicated or requested by the EU.

[0290] Clause 66. The EU of any of clauses 61 to 65, wherein one or more assumptions comprise an assumption that the symbol duration for the one or more symbols preceding the first symbol of the downlink timing period corresponds to a predefined symbol duration based on a zero Doppler condition.

[0291] Clause 67. The UE of any of clauses 61 to 66, wherein the information comprises the UE Rx-Tx time difference and the first time stamp, or wherein the information comprises the UE Rx-Tx time difference and the second time stamp, or wherein the information comprises the UE Rx-Tx time difference and the first time stamp and the second time stamp, or wherein the information comprises the UE Rx-Tx time difference and the Doppler information associated with the DL-PRS and the first time stamp, or wherein the information comprises the UE Rx-Tx time difference and the Doppler information associated with the DL-PRS and the second time stamp.

[0292] Clause 68. The EU of any of clauses 61 to 67, where the UL-SRS is associated with an older UL-SRS instance that is subsequent to a DL-PRS instance associated with the DL-PRS.

[0293] Clause 69. The UE of any of clauses 61 to 68 additionally comprising: means for transmitting an indication of UE Rx-Tx time difference measurement capability indicating a time difference type Petition 870250086012, dated 09 / 23 / 2025, pp. 148 / 362 140 / 158 UE Rx-Tx time that the UE is able to measure and / or report to NTN for a position estimation entity; and means to receive a measurement report configuration for the information in response to the indication of UE Rx-Tx time difference measurement capability to NTN.

[0294] Clause 70. The EU of any of clauses 61 to 69, wherein the measurement report additionally includes an indication of a measurement report configuration associated with the information.

[0295] Clause 71. A non-terrestrial network entity (NTN) comprising: means for receiving an uplink probe 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 comprising 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) 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 duration for one or more symbols preceding the first symbol of the uplink timing period.

[0296] Clause 72. The NTN entity of clause 71, wherein the downlink timing period comprises a downlink positioning reference signal (DL-RS), or wherein the timing period of Petition 870250086012, dated 09 / 23 / 2025, pp. 149 / 362 141 / 158 downlink is associated with the same system subframe number and / or the same slot index as the uplink timing period.

[0297] Clause 73. The NTN entity of clause 72, where the UL-SRS is associated with an older UL-SRS instance that is subsequent to a DL-RS instance associated with the DL-RS or within the same system subframe number and / or the same slot index.

[0298] Clause 74. The NTN entity of either clause 72 and 73, where DL-RS is a DL positioning reference signal (DL-PRS) or a DL channel state information RS (DL-CSI-RS).

[0299] Clause 75. The NTN entity of any of clauses 71 to 74, where the start of the uplink timing period is determined based on a UL-SRS reception timing that begins within the uplink timing period.

[0300] Clause 76. The NTN entity of any of clauses 71 to 75, wherein the downlink timing period is a downlink slot or a downlink subframe or a downlink symbol, and wherein the uplink timing period is an uplink slot or an uplink subframe or an uplink symbol.

[0301] Clause 77. The NTN entity of any of clauses 71 to 76, where a UL-SRS instance associated with UL-SRS is among a subset of UL-SRS instances associated with a ULSRS resource configuration for a UE position estimation session. Petition 870250086012, dated 09 / 23 / 2025, pp. 150 / 362 142 / 158

[0302] Clause 78. The NTN entity of clause 77, wherein the subset of UL-SRS instances is configured by a location management function (LMF) or a wireless network component, or wherein the subset of UL-SRS instances is indicated or requested by the UE.

[0303] Clause 79. The NTN entity of any of clauses 71 to 78, wherein one or more assumptions comprise an assumption that the symbol duration for the one or more symbols preceding the first symbol of the downlink timing period corresponds to a predefined symbol duration based on a zero Doppler condition.

[0304] Clause 80. The NTN entity of any of clauses 71 to 79, wherein the information comprises the NTN entity's Rx-Tx time difference and the first time stamp, or wherein the information comprises the NTN entity's Rx-Tx time difference and the second time stamp, or wherein the information comprises the first time stamp and the second time stamp.

[0305] Clause 81. A position estimation entity comprising: means for receiving a measurement report comprising 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 receipt of a downlink positioning reference symbol (DL-PRS) from a non-terrestrial network entity (NTN) and a second timestamp corresponding to the start of a timing period of Petition 870250086012, dated 09 / 23 / 2025, pp. 151 / 362 143 / 158 uplink associated with the transmission of an uplink probe reference signal (UL-SRS) to the NTN entity, (ii) to the first time stamp and (iii) to the second time stamp; and means for determining a round-trip time (RTT) between the UE and the NTN entity based, at least in part, on the information.

[0306] Clause 82. The position estimation entity of clause 81 further comprising: means for determining a subset of UL-SRS instances associated with the UL-SRS resource configuration for a UE position estimation session; and means for transmitting an indication of the subset of UL-SRS instances to the UE and the NTN entity to facilitate transmission and measurement of one or more UL-SRSs on the UL-SRS instances by the UE and the NTN entity, respectively.

[0307] Clause 83. The position estimating entity of either clause 81 and 82, wherein the downlink timing period is a downlink slot or a downlink subframe or a downlink symbol, and wherein the uplink timing period is an uplink slot or an uplink subframe or an uplink symbol.

[0308] Clause 84. The position estimating entity of any of clauses 81 to 83, wherein the information comprises the EU Rx-Tx time difference and the first time stamp, or wherein the information comprises the EU Rx-Tx time difference and the second time stamp, or wherein the information comprises the first time stamp and the second time stamp, or Petition 870250086012, dated 09 / 23 / 2025, pp. 152 / 362 144 / 158 where the information includes the UE RxTx time difference and the Doppler information associated with DL-PRS.

[0309] Clause 85. The position estimation entity of any of clauses 81 to 84, where ULSRS is associated with an older UL-SRS instance that is subsequent to a DL-PRS instance associated with DL-PRS.

[0310] Clause 86. A position estimation entity comprising: means for receiving a measurement report comprising sufficient information to determine (i) a receive-transmit (Rx-Tx) time difference of an NTN entity 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.

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

[0312] Clause 88. The position estimate entity of clause 87, where the UL-SRS is associated with an older UL-SRS instance that is subsequent to a Petition 870250086012, dated 09 / 23 / 2025, pp. 153 / 362 145 / 158 instance of DL-RS associated with DL-RS or within the same system subframe number and / or the same slot index.

[0313] Clause 89. The position estimation entity of any of clauses 86 to 88, wherein the start of the uplink timing period is determined based on a UL-SRS receive timing that begins within the uplink timing period.

[0314] Clause 90. The position estimating entity of either clause 86 and 89, wherein the downlink timing period is a downlink slot or a downlink subframe or a downlink symbol, and wherein the uplink timing period is an uplink slot or an uplink subframe or an uplink symbol.

[0315] Clause 91. A non-transient, computer-readable medium that stores computer-executable instructions which, when executed by a user equipment (UE), causes the UE to: receive a downlink positioning reference signal (DL-PRS) from a non-terrestrial network entity (NTN) at a first symbol of a downlink timing period; transmit an uplink polling reference signal (UL-SRS) to the NTN entity at a second symbol of an uplink timing period; and transmit a measurement report comprising sufficient information to determine (i) a receive-transmit (Rx-Tx) time difference of the UE between a first timestamp corresponding to the start of the downlink timing period and a second Petition 870250086012, dated 09 / 23 / 2025, pp. 154 / 362 146 / 158 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 duration for one or more symbols preceding the first symbol of the downlink timing period.

[0316] Clause 92. The non-transient, computer-readable medium of clause 91, wherein the downlink timing period is a downlink slot or a downlink subframe or a downlink symbol, and wherein the uplink timing period is an uplink slot or an uplink subframe or an uplink symbol.

[0317] Clause 93. The non-transient, machine-readable means of clause 92, wherein a timestamp granularity associated with the first timestamp, the second timestamp, or both, corresponds to a respective granularity associated with the downlink timing period, the uplink timing period, or both.

[0318] Clause 94. The non-transient, machine-readable means of any of clauses 91 to 93, where a DL-PRS instance associated with 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 where a ULSRS instance associated with UL-SRS is among a subset of Petition 870250086012, dated 09 / 23 / 2025, pp. 155 / 362 147 / 158 instances of UL-SRS associated with a UL-SRS resource configuration for the UE position estimation session.

[0319] Clause 95. The non-transient, machine-readable means of clause 94, wherein the subset of DL-PRS instances and / or the subset of ULSRS instances are configured by a location management function (LMF) or a wireless network component, or wherein the subset of DL-PRS instances and / or the subset of ULSRS instances are indicated or requested by the UE.

[0320] Clause 96. The non-transient, computer-readable means of any of clauses 91 to 95, wherein one or more assumptions comprise an assumption that the symbol duration for the one or more symbols preceding the first symbol of the downlink timing period corresponds to a predefined symbol duration based on a zero Doppler condition.

[0321] Clause 97. The non-transient, computer-readable medium of any of clauses 91 to 96, wherein the information comprises the time difference between Rx-Tx of the UE and the first time stamp, or wherein the information comprises the time difference between Rx-Tx of the UE and the second time stamp, or wherein the information comprises the time difference between Rx-Tx of the UE and the first time stamp and the second time stamp, or wherein the information comprises the time difference between Rx-Tx of the UE and the Doppler information associated with the DL-PRS and the first time stamp, or wherein the information comprises the time difference between Rx-Tx of the UE and the Doppler information associated with the DL-PRS and the second time stamp. Petition 870250086012, dated 09 / 23 / 2025, pp. 156 / 362 148 / 158

[0322] Clause 98. The non-transitory, machine-readable medium of any of clauses 91 to 97, where the UL-SRS is associated with an older UL-SRS instance that is subsequent to a DL-PRS instance associated with the DL-PRS.

[0323] Clause 99. The non-transient, computer-readable means of any of Clauses 91 to 98 further comprising computer-executable instructions which, when executed by the UE, cause the UE to: transmit an indication of UE Rx-Tx time difference measurement capability indicating a type of UE Rx-Tx time difference that the UE is capable of measuring and / or reporting to NTN for a position estimation entity; and receive a measurement reporting configuration for the information in response to the UE Rx-Tx time difference measurement capability indication to NTN.

[0324] Clause 100. The non-transitory, computer-readable means of any of clauses 91 to 99, wherein the measurement report additionally comprises an indication of a measurement report configuration associated with the information.

[0325] Clause 101. A non-transient, computer-readable medium that stores computer-executable instructions which, when executed by a non-terrestrial network entity (NTN), cause the NTN entity to: receive an uplink probe reference signal (ULSRS) from a user equipment (UE) at a first symbol of an uplink timing period; and transmit a measurement report comprising sufficient information to determine (i) a time difference of Petition 870250086012, dated 09 / 23 / 2025, pp. 157 / 362 149 / 158 reception and transmission (Rx-Tx) of an NTN entity 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) to the first timestamp and (iii) to the second timestamp, wherein the start of the downlink timing period is based on one or more assumptions associated with the symbol duration for one or more symbols preceding the first symbol of the uplink timing period.

[0326] Clause 102. The non-transient, computer-readable medium of clause 101, wherein the downlink timing period comprises a downlink positioning reference signal (DL-RS), or wherein the downlink timing period is associated with the same system subframe number and / or the same slot index as the uplink timing period.

[0327] Clause 103. The non-transitory, machine-readable means of clause 102, wherein the UL-SRS is associated with an older UL-SRS instance that is subsequent to a DL-RS instance associated with the DL-RS or within the same system subframe number and / or the same slot index.

[0328] Clause 104. The non-transient, computer-readable means of either clause 102 or 103, wherein DL-RS is a DL positioning reference signal (DL-PRS) or a DL channel state information RS (DL-CSI-RS). Petition 870250086012, dated 09 / 23 / 2025, pp. 158 / 362 150 / 158

[0329] Clause 105. The non-transient, computer-readable means of any of clauses 101 to 104, wherein the start of the uplink timing period is determined based on a UL-SRS receive timing that begins within the uplink timing period.

[0330] Clause 106. The non-transient, computer-readable medium of any of clauses 101 to 105, wherein the downlink timing period is a downlink slot or a downlink subframe or a downlink symbol, and wherein the uplink timing period is an uplink slot or an uplink subframe or an uplink symbol.

[0331] Clause 107. The non-transient, machine-readable means of any of clauses 101 to 106, wherein a 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.

[0332] Clause 108. The non-transitory, machine-readable means of clause 107, wherein the subset of UL-SRS instances is configured by a location management function (LMF) or a wireless network component, or wherein the subset of UL-SRS instances is indicated or requested by the UE.

[0333] Clause 109. The non-transitory, computer-readable means of any of clauses 101 to 108, wherein one or more assumptions comprise an assumption that the duration of the symbol for the one or more symbols preceding the Petition 870250086012, dated 09 / 23 / 2025, pp. 159 / 362 151 / 158 The first symbol of the downlink timing period corresponds to a predefined symbol duration based on a zero Doppler condition.

[0334] Clause 110. The non-transitory, computer-readable medium of any of clauses 101 to 109, wherein the information comprises the NTN entity's Rx-Tx time difference and the first timestamp, or wherein the information comprises the NTN entity's Rx-Tx time difference and the second timestamp, or wherein the information comprises the first timestamp and the second timestamp.

[0335] Clause 111. A non-transient, computer-readable medium that stores computer-executable instructions that, when executed by a position estimation entity, cause the position estimation entity to: receive a measurement report comprising 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 receiving a downlink positioning reference symbol (DL-PRS) from a non-terrestrial network entity (NTN) and a second timestamp corresponding to the start of an uplink timing period associated with transmitting an uplink probing reference signal (UL-SRS) to the NTN entity, (ii) to the first timestamp and (iii) to the second timestamp;and to determine a round-trip travel time (RTT) between the EU and the NTN entity based, at least in part, on the information. Petition 870250086012, dated 09 / 23 / 2025, pp. 160 / 362 152 / 158

[0336] Clause 112. The non-transient, computer-readable means of Clause 111 which further comprises computer-executable instructions which, when executed by the position estimation entity, cause the position estimation entity to: determine a subset of UL-SRS instances associated with the UL-SRS resource configuration for a UE position estimation session; and transmit an indication of the subset of UL-SRS instances to the UE and the NTN entity to facilitate transmission and measurement of one or more UL-SRSs on the UL-SRS instances by the UE and the NTN entity, respectively.

[0337] Clause 113. The non-transient, computer-readable medium of any of clauses 111 to 112, wherein the downlink timing period is a downlink slot or a downlink subframe or a downlink symbol, and wherein the uplink timing period is an uplink slot or an uplink subframe or an uplink symbol.

[0338] Clause 114. The non-transient, computer-readable medium of any of clauses 111 to 113, wherein the information comprises the UE Rx-Tx time difference and the first time stamp, or wherein the information comprises the UE Rx-Tx time difference and the second time stamp, or wherein the information comprises the first time stamp and the second time stamp, or wherein the information comprises the UE Rx-Tx time difference and the Doppler information associated with the DL-PRS. Petition 870250086012, dated 09 / 23 / 2025, pp. 161 / 362 153 / 158

[0339] Clause 115. The non-transitory, machine-readable medium of any of clauses 111 to 114, where UL-SRS is associated with an older ULSRS instance that is subsequent to a DL-PRS instance associated with DL-PRS.

[0340] Clause 116. A non-transient, computer-readable medium that stores computer-executable instructions that, when executed by a position estimation entity, cause the position estimation entity to: receive a measurement report comprising sufficient information to determine (i) a receive-transmit (Rx-Tx) time difference from an NTN entity 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 determine a round-trip time (RTT) between a user equipment (UE) and the NTN entity based, at least in part, on the information.

[0341] Clause 117. The non-transient, computer-readable medium of clause 116, wherein the downlink timing period comprises a downlink positioning reference signal (DL-RS), or wherein the downlink timing period is associated with the same system subframe number and / or the same slot index as the uplink timing period.

[0342] Clause 118. The non-transitory, computer-readable medium of clause 117, to which the UL-SRS is attached. Petition 870250086012, dated 09 / 23 / 2025, pages 162 / 362 154 / 158 refers to an older UL-SRS instance that is subsequent to a DL-RS instance associated with DL-RS or within the same system subframe number and / or the same slot index.

[0343] Clause 119. The non-transient, computer-readable means of any of clauses 116 to 118, wherein the start of the uplink timing period is determined based on a UL-SRS receive timing that begins within the uplink timing period.

[0344] Clause 120. The non-transient, computer-readable medium of any of clauses 116 to 119, wherein the downlink timing period is a downlink slot or a downlink subframe or a downlink symbol, and wherein the uplink timing period is an uplink slot or an uplink subframe or an uplink symbol.

[0345] Those skilled in the art will recognize that information and signals can be represented using any of several different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the description above can be represented by voltages, currents, electromagnetic waves, magnetic particles or fields, optical particles or fields, or any combination thereof.

[0346] Additionally, those skilled in the art will recognize that the various illustrative logic blocks, modules, circuits, and algorithm steps described in connection with the aspects disclosed in the present invention may Petition 870250086012, dated 09 / 23 / 2025, pp. 163 / 362 155 / 158 can be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, several illustrative components, blocks, modules, circuits, and stages have been described above in terms of their functionality. The possibility of such functionality being implemented as hardware or software depends on the particular application and the design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in various ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of this disclosure.

[0347] The various logic blocks, modules, and illustrative circuits described in connection with the aspects disclosed in the present invention may be implemented or realized with a general-purpose processor, a digital signal processor (DSP), an ASIC, a field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in the present invention. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, a Petition 870250086012, dated 09 / 23 / 2025, pp. 164 / 362 156 / 158 or more microprocessors in conjunction with a DSP core or any other such configuration.

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

[0349] In one or more example aspects, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored or transmitted in the form of one or more instructions or code in a computer-readable medium. Computer-readable media Petition 870250086012, dated 09 / 23 / 2025, pp. 165 / 362 157 / 158 Computer media include both computer storage media and communication media, including any means that facilitates the transfer of a computer program from one place to another. A storage medium may be any available medium that can be accessed by a computer. By way of example, and not limitation, such computer-readable media may comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and that can be accessed by a computer. In addition, any connection is properly termed a computer-readable medium.For example, if the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless communication technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless communication technologies such as infrared, radio, and microwave are included in the definition of medium. As used in the present invention, disks (disk and disc) include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc, where disks generally reproduce data magnetically, while discs reproduce data optically by means of lasers. Combinations of the items. Petition 870250086012, dated 09 / 23 / 2025, pp. 166 / 362 158 / 158 above should also be included in the scope of computer-readable media.

[0350] Although the aforementioned disclosure shows illustrative aspects of the disclosure, it should be noted that various changes and modifications can be made to the present invention without it departing from the scope of the disclosure as defined by the appended claims. The functions, steps, and / or actions of the method claims according to the aspects of the disclosure described in the present invention need not be performed in any particular order. Furthermore, although the elements of the disclosure may be described or claimed in the singular, the plural is contemplated unless a limitation to the singular is explicitly stated. Petition 870250086012, dated 09 / 23 / 2025, pp. 167 / 362

Claims

1 / 10 CLAIMS 1. Method of operation of a user equipment (UE) characterized by comprising: receiving a downlink positioning reference signal (DL-PRS) from a non-terrestrial network entity (NTN) in a first symbol of a downlink timing period; transmitting an uplink probing reference signal (UL-SRS) to the NTN entity in a second symbol of an uplink timing period;and transmit a measurement report comprising 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) to the first timestamp and (iii) to the second timestamp, wherein the start of the downlink timing period is based on one or more assumptions associated with the symbol duration for one or more symbols preceding the first symbol of the downlink timing period.

2. Method according to claim 1, characterized in that: the downlink timing period being a downlink slot or a downlink subframe or a downlink symbol, and Petition 870250086012, dated 23 / 09 / 2025, p. 327 / 362 2 / 10 the uplink timing period being an uplink slot or an uplink subframe or an uplink symbol.

3. A method according to claim 2, characterized in that a timestamp granularity associated with the first timestamp, the second timestamp, or both corresponds to a respective granularity associated with the downlink timing period, the uplink timing period, or both.

4. Method according to claim 1, characterized in that: a DL-PRS instance associated with the 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 the UL-SRS is among a subset of UL-SRS instances associated with a UL-SRS resource configuration for the UE position estimation session.

5. Method according to claim 4, characterized in that: the subset of DL-PRS instances and / or the subset of UL-SRS instances are configured by a location management function (LMF) or a wireless network component, or the subset of DL-PRS instances and / or the subset of UL-SRS instances are indicated or requested by the UE.

6. Method, according to claim 1, characterized in that one or more assumptions comprise Petition 870250086012, dated 09 / 23 / 2025, p. 328 / 362 3 / 10 an assumption that the symbol duration for the one or more symbols preceding the first symbol of the downlink timing period corresponds to a predefined symbol duration based on a zero Doppler condition.

7. Method according to claim 1, characterized in that: the information comprises the time difference between the Rx-Tx of the UE and the first time marking, or the information comprises the time difference between the Rx-Tx of the UE and the second time marking, or the information comprises the time difference between the Rx-Tx of the UE and the first time marking and the second time marking, or the information comprises the time difference between the Rx-Tx of the UE and the Doppler information associated with the DLPRS and the first time marking, or the information comprises the time difference between the Rx-Tx of the UE and the Doppler information associated with the DLPRS and the second time marking.

8. Method, according to claim 1, characterized in that the UL-SRS is associated with an older UL-SRS instance that is subsequent to a DL-PRS instance associated with the DL-PRS.

9. Method according to claim 1, characterized by further comprising: transmitting an indication of UE Rx-Tx time difference measurement capability indicating a type of UE Rx-Tx time difference that the UE is capable of measuring and / or reporting to NTN for a position estimation entity; and receiving a measurement reporting configuration for the information in response to the UE Rx-Tx time difference measurement capability indication to NTN.

10. Method according to claim 1, characterized in that the measurement report further comprises an indication of a measurement report configuration associated with the information.

11. Method of operation of a non-terrestrial network entity (NTN) characterized by comprising: receiving an uplink probe reference signal (UL-SRS) from a user equipment (UE) on a first symbol of an uplink timing period; and transmitting a measurement report comprising 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) 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 duration for one or more symbols preceding the first symbol of the uplink timing period.

12. Method according to claim 11, characterized in that: Petition 870250086012, dated 09 / 23 / 2025, p. 330 / 362 5 / 10 the downlink timing period comprises 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.

13. Method, according to claim 12, characterized in that the UL-SRS is associated with an older UL-SRS instance that is subsequent to a DL-RS instance associated with the DL-RS or within the same system subframe number and / or the same slot index.

14. Method according to claim 12, characterized in that the DL-RS is a DL positioning reference signal (DL-PRS) or a DL channel state information RS (DL-CSI-RS).

15. Method according to claim 11, characterized in that the start of the uplink timing period is determined based on a UL-SRS reception timing that begins within the uplink timing period.

16. Method according to claim 11, characterized in that: the downlink timing period being a downlink slot or a downlink subframe or a downlink symbol, and the uplink timing period being an uplink slot or an uplink subframe or an uplink symbol. Petition 870250086012, dated 23 / 09 / 2025, pp. 331 / 362 6 / 10 17. Method according to claim 11, characterized in that a UL-SRS instance associated with ULSRS is among a subset of UL-SRS instances associated with a UL-SRS resource configuration for a UE position estimation session.

18. Method according to claim 17, characterized in that: the subset of UL-SRS instances is configured by a location management function (LMF) or a wireless network component, or the subset of UL-SRS instances is indicated or requested by the UE.

19. Method according to claim 11, characterized in that one or more assumptions comprise an assumption that the symbol duration for the one or more symbols preceding the first symbol of the downlink timing period corresponds to a predefined symbol duration based on a zero Doppler condition.

20. Method according to claim 11, characterized in that: the information comprises the time difference between the Rx-Tx of an NTN entity and the first timestamp, or the information comprises the time difference between the Rx-Tx of an NTN entity and the second timestamp, or the information comprises the first timestamp and the second timestamp.

21. Method of operation of a position estimation entity characterized by comprising: Petition 870250086012, dated 09 / 23 / 2025, p.332 / 362 7 / 10 receive a measurement report comprising 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 receiving a downlink positioning reference symbol (DL-PRS) from a non-terrestrial network entity (NTN) and a second timestamp corresponding to the start of an uplink timing period associated with transmitting an uplink probing reference signal (UL-SRS) to the NTN entity, (ii) to the first timestamp and (iii) to the second timestamp; and to determine a round-trip time (RTT) between the UE and the NTN entity based, at least in part, on the information.

22. Method according to claim 21, characterized by further comprising: determining a subset of UL-SRS instances associated with the UL-SRS resource configuration for a UE position estimation session; and transmitting an indication of the subset of UL-SRS instances to the UE and the NTN entity to facilitate transmission and measurement of one or more UL-SRSs on the UL-SRS instances by the UE and the NTN entity, respectively.

23. Method according to claim 21, characterized in that: Petition 870250086012, dated 09 / 23 / 2025, p. 333 / 362 8 / 10 the downlink timing period being a downlink slot or a downlink subframe or a downlink symbol, and the uplink timing period being an uplink slot or an uplink subframe or an uplink symbol.

24. Method according to claim 21, characterized in that: the information comprises the time difference between the Rx-Tx of the UE and the first time marking, or the information comprises the time difference between the Rx-Tx of the UE and the second time marking, or the information comprises the first time marking and the second time marking, or the information comprises the time difference between the Rx-Tx of the UE and the Doppler information associated with the DL-PRS.

25. Method according to claim 21, characterized in that the UL-SRS is associated with an older UL-SRS instance that is subsequent to a DL-PRS instance associated with the DL-PRS.

26. Method of operation of a position estimation entity characterized by comprising: receiving a measurement report comprising sufficient information to determine (i) a receive-transmit (Rx-Tx) time difference from an NTN entity 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) Petition 870250086012, dated 23 / 09 / 2025, pp. 334 / 362 9 / 10 to the first timestamp and (iii) to the second timestamp, and determining a round-trip time (RTT) between a user equipment (UE) and the NTN entity based, at least in part, on the information.

27. Method according to claim 26, characterized in that: the downlink timing period comprises 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.

28. Method, according to claim 27, characterized in that the UL-SRS is associated with an older UL-SRS instance that is subsequent to a DL-RS instance associated with the DL-RS or within the same system subframe number and / or the same slot index.

29. Method according to claim 26, characterized in that the start of the uplink timing period is determined based on a UL-SRS receive timing that begins within the uplink timing period.

30. Method according to claim 26, characterized in that: the downlink timing period being a downlink slot or a downlink subframe or a downlink symbol, and the uplink timing period being an uplink slot or an uplink subframe or an uplink symbol.

Images