Processing windows for non-terrestrial network node based positioning

Abstract

Some wireless communication systems utilize signals to perform positioning procedures. Performing positioning based on signals from one or more non-terrestrial network (NTN) nodes may pose a variety of challenges. Distances between a user equipment (UE) and the NTN nodes may be relatively large and may vary. In some cases, a UE may utilize NTN positioning measurements without measurement gaps (e.g., a positioning reference signal (PRS) processing window (PPW)). With defined measurement gaps, a single PPW that can accommodate large propagation delay is not supported in some approaches. One or more PPW patterns may be utilized in accordance with the techniques described herein. In some examples, a PPW identifier may correspond to multiple window lengths within the PPW, which may allow different lengths or gaps between pairs of the processing windows. PPW window lengths for NTN positioning may be 320 slots, 640 slots, 2560 slots, or another duration.

Description

Qualcomm Ref. No. 2407388WO1PROCESSING WINDOWS FOR NON-TERRESTRIAL NETWORK NODEBASED POSITIONING CROSS REFERENCE

[0001] The present Application for Patent claims priority to Greek Patent Application No. 20250100037 by MANOLAKOS et al., entitled “PROCESSING WINDOWS FOR NON-TERRESTRIAL NETWORK NODE-BASED POSITIONING,” filed January 20, 2025, which is assigned to the assignee hereof and expressly incorporated by reference herein.FIELD OF TECHNOLOGY

[0002] The following relates to wireless communications, including processing windows for non-terrestrial network node-based positioning.BACKGROUND

[0003] Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power). Examples of such multiple-access systems include fourth generation (4G) systems such as Long Term Evolution (LTE) systems, LTE- Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems which may be referred to as New Radio (NR) systems. These systems may employ technologies such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple-access communications system may include one or more base stations, each supporting wireless communication for communication devices, which may be known as user equipment (UE).Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO2SUMMARY

[0004] The systems, methods, and devices of this disclosure each have several innovative aspects, no single one of which is solely responsible for the desirable attributes disclosed herein.

[0005] A method for wireless communications by a wireless device is described. The method may include receiving configuration information indicating a positioning reference signal (PRS) processing window (PPW) identifier of a PPW and a periodicity of the PPW, where the configuration information indicates multiple window lengths within the periodicity of the PPW, and the PPW identifier is associated with the multiple window lengths, receiving, from at least one non-terrestrial network (NTN) node, a PRS in one or more of the multiple window lengths, and obtaining measurement information based on the PRS within a respective window length of the multiple window lengths.

[0006] A wireless device for wireless communications is described. The wireless device may include one or more transceivers, one or more memory, and one or more processors electronically coupled to the one or more memory and the one or more transceivers. The one or more processors may be configured to receive configuration information indicating a PPW identifier of a PPW and a periodicity of the PPW, where the configuration information indicates multiple window lengths within the periodicity of the PPW, and the PPW identifier is associated with the multiple window lengths, receive, from at least one NTN node, a PRS in one or more of the multiple window lengths, and obtain measurement information based on the PRS within a respective window length of the multiple window lengths.

[0007] Another wireless device for wireless communications is described. The wireless device may include means for receiving configuration information indicating a PPW identifier of a PPW and a periodicity of the PPW, where the configuration information indicates multiple window lengths within the periodicity of the PPW, and the PPW identifier is associated with the multiple window lengths, means for receiving, from at least one NTN node, a PRS in one or more of the multiple window lengths, and means for obtaining measurement information based on the PRS within a respective window length of the multiple window lengths.Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO3

[0008] A non-transitory computer-readable medium storing code for wireless communications is described. The code may include instructions executable by one or more processors to receive configuration information indicating a PPW identifier of a PPW and a periodicity of the PPW, where the configuration information indicates multiple window lengths within the periodicity of the PPW, and the PPW identifier is associated with the multiple window lengths, receive, from at least one NTN node, a PRS in one or more of the multiple window lengths, and obtain measurement information based on the PRS within a respective window length of the multiple window lengths.

[0009] In some examples of the method, wireless devices, and non-transitory computer-readable medium described herein, the configuration information indicates a first window length associated with the PPW identifier that may be different from a second window length associated with the PPW identifier.

[0010] In some examples of the method, wireless devices, and non-transitory computer-readable medium described herein, the configuration information indicates at least one gap between a pair of the multiple window lengths associated with the PPW identifier.

[0011] In some examples of the method, wireless devices, and non-transitory computer-readable medium described herein, the configuration information indicates different gaps between different pairs of the multiple window lengths associated with the PPW identifier.

[0012] Some examples of the method, wireless devices, and non-transitory computer-readable medium described herein may further include operations, features, means, one or more processors, or instructions for receiving control information indicating activation or deactivation of the PPW based on the PPW identifier of the PPW, where the activation or deactivation of the PPW corresponds to the multiple window lengths associated with the PPW identifier.

[0013] In some examples of the method, wireless devices, and non-transitory computer-readable medium described herein, the activation or deactivation of the PPW indicates activation or deactivation of the PPW that corresponds to the multiple window lengths on a bandwidth part (BWP) or a positioning frequency layer (PFL).Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO4

[0014] Some examples of the method, wireless devices, and non-transitory computer-readable medium described herein may further include operations, features, means, one or more processors, or instructions for transmitting capability information indicating a quantity of PPW identifiers for concurrent activation supported by the wireless device, where the control information may be received based on the capability information.

[0015] In some examples of the method, wireless devices, and non-transitory computer-readable medium described herein, a set of PPW identifiers includes a first subset of PPW identifiers corresponding to PPWs for NTN positioning and a second subset of PPW identifiers corresponding to PPWs for terrestrial network (TN) positioning, and where the PPW identifier may be included in the first subset of PPW identifiers for NTN positioning.

[0016] In some examples of the method, wireless devices, and non-transitory computer-readable medium described herein, the configuration information indicates that at least one of the multiple window lengths may be greater than 160 slots.

[0017] Some examples of the method, wireless devices, and non-transitory computer-readable medium described herein may further include operations, features, means, one or more processors, or instructions for transmitting a request for the configuration information indicating the PPW identifier for NTN positioning, where the configuration information may be received based on the request.

[0018] Some examples of the method, wireless devices, and non-transitory computer-readable medium described herein may further include operations, features, means, one or more processors, or instructions for receiving an indication of a set of PPW identifiers, where the request for the configuration information may be transmitted based on the set of PPW identifiers.

[0019] Some examples of the method, wireless devices, and non-transitory computer-readable medium described herein may further include operations, features, means, one or more processors, or instructions for receiving an indication of at least one parameter, including a downlink PPW identifier parameter, a downlink periodicity and start slot parameter, a length parameter, a type parameter, a priority parameter, or aAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO5combination thereof, where the request for the configuration information may be based on the at least one parameter.

[0020] Some examples of the method, wireless devices, and non-transitory computer-readable medium described herein may further include operations, features, means, one or more processors, or instructions for receiving, from a network entity, an indication of a PPW parameter, a PPW drift parameter, and a PPW drift variation parameter to determine a time-varying start parameter or a time-varying duration parameter, where a start time of the PPW may be based on the time-varying start parameter or a duration of the PPW may be based on the time-varying duration parameter.

[0021] Some examples of the method, wireless devices, and non-transitory computer-readable medium described herein may further include operations, features, means, one or more processors, or instructions for receiving, from a network entity, an indication of a PPW parameter, a PPW drift parameter, and a PPW drift variation parameter to determine a time-varying start parameter or a time-varying duration parameter, where a start time of at least one of the multiple window lengths may be based on the time-varying start parameter or a duration of at least one of the multiple window lengths may be based on the time-varying duration parameter.

[0022] In some examples of the method, wireless devices, and non-transitory computer-readable medium described herein, the configuration information indicates a priority for PRSs and receiving the PRS from the at least one NTN node may be performed based on the priority.

[0023] In some examples of the method, wireless devices, and non-transitory computer-readable medium described herein, the configuration information indicates a priority for PRSs and obtaining the measurement information based on the PRS may be performed based on the priority.

[0024] In some examples of the method, wireless devices, and non-transitory computer-readable medium described herein, the configuration information indicates a priority among the multiple window lengths and obtaining the measurement information based on the PRS may be performed based on the priority.Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO6

[0025] Some examples of the method, wireless devices, and non-transitory computer-readable medium described herein may further include operations, features, means, one or more processors, or instructions for obtaining the measurement information based on the PRS may be performed based on a priority among the multiple window lengths that may be based on an order of the multiple window lengths.

[0026] A method for wireless communications by a network entity is described. The method may include transmitting configuration information indicating a PPW identifier of a PPW and a periodicity of the PPW, where the configuration information indicates multiple window lengths within the periodicity of the PPW, and the PPW identifier is associated with the multiple window lengths and receiving measurement information, the measurement information based on the PRS within a respective window length of the multiple window lengths.

[0027] A network entity for wireless communications is described. The network entity may include one or more transceivers, one or more memory, and one or more processors electronically coupled to the one or more memory and the one or more transceivers. The one or more processors may be configured to transmit configuration information indicating a PPW identifier of a PPW and a periodicity of the PPW, where the configuration information indicates multiple window lengths within the periodicity of the PPW, and the PPW identifier is associated with the multiple window lengths and receive measurement information, the measurement information based on the PRS within a respective window length of the multiple window lengths.

[0028] Another network entity for wireless communications is described. The network entity may include means for transmitting configuration information indicating a PPW identifier of a PPW and a periodicity of the PPW, where the configuration information indicates multiple window lengths within the periodicity of the PPW, and the PPW identifier is associated with the multiple window lengths and means for receiving measurement information, the measurement information based on the PRS within a respective window length of the multiple window lengths.

[0029] A non-transitory computer-readable medium storing code for wireless communications is described. The code may include instructions executable by one or more processors to transmit configuration information indicating a PPW identifier of aAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO7PPW and a periodicity of the PPW, where the configuration information indicates multiple window lengths within the periodicity of the PPW, and the PPW identifier is associated with the multiple window lengths and receive measurement information, the measurement information based on the PRS within a respective window length of the multiple window lengths.

[0030] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the configuration information indicates a first window length associated with the PPW identifier that may be different from a second window length associated with the PPW identifier.

[0031] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the configuration information indicates at least one gap between a pair of the multiple window lengths associated with the PPW identifier.

[0032] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the configuration information indicates different gaps between different pairs of the multiple window lengths associated with the PPW identifier.

[0033] Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, one or more processors, or instructions for receiving capability information indicating a quantity of PPW identifiers for concurrent activation supported by a wireless device.

[0034] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, a set of PPW identifiers includes a first subset of PPW identifiers corresponding to PPWs for NTN positioning and a second subset of PPW identifiers corresponding to PPWs for TN positioning, and where the PPW identifier may be included in the first subset of PPW identifiers for NTN positioning.Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO8

[0035] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the configuration information indicates that at least one of the multiple window lengths may be greater than 160 slots.

[0036] Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, one or more processors, or instructions for receiving a request for the configuration information indicating the PPW identifier for NTN positioning, where the configuration information may be transmitted based on the request.

[0037] Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, one or more processors, or instructions for transmitting an indication of a set of PPW identifiers, where the request for the configuration information may be received based on the set of PPW identifiers.

[0038] Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, one or more processors, or instructions for transmitting an indication of at least one parameter, including a downlink PPW identifier parameter, a downlink periodicity and start slot parameter, a length parameter, a type parameter, a priority parameter, or a combination thereof, where the request for the configuration information may be based on the at least one parameter.

[0039] Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, one or more processors, or instructions for transmitting, to a wireless device, an indication of a PPW parameter, a PPW drift parameter, and a PPW drift variation parameter to determine a time-varying start parameter or a time-varying duration parameter, where a start time of the PPW may be based on the time-varying start parameter or a duration of the PPW may be based on the time-varying duration parameter.

[0040] Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, one or more processors, or instructions for transmitting, to a wireless device, anAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO9indication of a PPW parameter, a PPW drift parameter, and a PPW drift variation parameter to determine a time-varying start parameter or a time-varying duration parameter, where a start time of at least one of the multiple window lengths may be based on the time-varying start parameter or a duration of at least one of the multiple window lengths may be based on the time-varying duration parameter.

[0041] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the configuration information indicates a priority for PRSs and receiving the measurement information based on the PRS may be based on the priority.

[0042] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the configuration information indicates a priority among the multiple window lengths and receiving the measurement information based on the PRS may be based on the priority.

[0043] Details of one or more implementations of the subject matter described in this disclosure are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages will become apparent from the description, the drawings, and the claims. Note that the relative dimensions of the following figures may not be drawn to scale.BRIEF DESCRIPTION OF THE DRAWINGS

[0044] FIG. 1 shows an example of a wireless communications system that supports processing windows for non-terrestrial network (NTN) node-based positioning in accordance with one or more aspects of the present disclosure.

[0045] FIG. 2 shows an example of a network structure that supports processing windows for NTN node-based positioning in accordance with one or more aspects of the present disclosure.

[0046] FIG. 3 shows an example of a network architecture that supports processing windows for NTN node-based positioning in accordance with one or more aspects of the present disclosure.Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO10

[0047] FIG. 4 shows an example of a wireless communications system that supports processing windows for NTN node-based positioning in accordance with one or more aspects of the present disclosure.

[0048] FIG. 5 shows an example of a wireless communications system that supports processing windows for NTN node-based positioning in accordance with one or more aspects of the present disclosure.

[0049] FIG. 6 shows examples of timing diagrams that support processing windows for NTN node-based positioning in accordance with one or more aspects of the present disclosure.

[0050] FIG. 7 shows an example of a process flow that supports processing windows for NTN node-based positioning in accordance with one or more aspects of the present disclosure.

[0051] FIG. 8 shows an example of a process flow that supports processing windows for NTN node-based positioning in accordance with one or more aspects of the present disclosure.

[0052] FIGs. 9 and 10 show block diagrams of devices that support processing windows for NTN node-based positioning in accordance with one or more aspects of the present disclosure.

[0053] FIG. 11 shows a block diagram of a communications manager that supports processing windows for NTN node-based positioning in accordance with one or more aspects of the present disclosure.

[0054] FIG. 12 shows a diagram of a system including a device that supports processing windows for NTN node-based positioning in accordance with one or more aspects of the present disclosure.

[0055] FIGs. 13 and 14 show block diagrams of devices that support processing windows for NTN node-based positioning in accordance with one or more aspects of the present disclosure.Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO11

[0056] FIG. 15 shows a block diagram of a communications manager that supports processing windows for NTN node-based positioning in accordance with one or more aspects of the present disclosure.

[0057] FIG. 16 shows a diagram of a system including a device that supports processing windows for NTN node-based positioning in accordance with one or more aspects of the present disclosure.

[0058] FIGs. 17 through 20 show flowcharts illustrating methods that support processing windows for NTN node-based positioning in accordance with one or more aspects of the present disclosure.

[0059] FIG. 21 shows examples of wireless communications systems that supports processing windows for NTN node-based positioning in accordance with one or more aspects of the present disclosure.DETAILED DESCRIPTION

[0060] Some wireless communication systems utilize signals to perform positioning procedures. For example, a user equipment (UE) may receive signals from one or more terrestrial network (TN) nodes to perform positioning procedures. Performing positioning based on signals from one or more non-terrestrial network (NTN) nodes may pose a variety of challenges. In an example, three NTN satellites may transmit a positioning signal at the same time. The positioning signaling may be broadcasted signals for all UEs within a coverage region. The distances between UE and the NTN satellites may be relatively large and may vary from satellite to satellite. In some cases, a UE may utilize NTN positioning measurements without measurement gaps (e.g., a positioning reference signal (PRS) processing window (PPW)). With defined measurement gaps, a single PPW that can accommodate large propagation delay is not supported in some approaches. For instance, some approaches may limit PPW length to 160 slots with one or more options for periodicity or start offsets based on a subcarrier spacing (SCS).

[0061] The difference in propagation delay may impact measurements. In an example scenario, a UE may be served by a low-Earth orbit (LEO) satellite SI, and may also be within coverage of an incoming LEO satellite S2. The UE may performAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO12measurements of the neighboring cell(s) originating from S2 for mobility purposes based on a measurement configuration provided to the UE. However, the propagation delay difference from the UE to satellite SI and from the UE to satellite S2 may vary significantly. If a synchronization signal block (SSB)-based measurement time configuration (SMTC) measurement gap configuration does not account for the propagation delay difference, the UE may miss the SSB or channel state information reference signal (CSI-RS) measurement window and may thus be unable to perform measurements on the configured reference signals. This challenge may occur for geostationary Earth orbit (GEO) and LEO scenarios. A similar issue may arise in the positioning measurement in scenarios with a difference between reference signal time difference (RSTD) measurements is relatively large or a gap duration is small.

[0062] One or more PPW patterns may be utilized in accordance with the techniques described herein. In some examples, a PPW identifier may correspond to multiple window lengths within the PPW. The multiple window lengths may include processing windows of different lengths. Gaps between pairs of the processing windows may be different. Enabling multiple window lengths corresponding to one PPW identifier may enable joint activation or deactivation of multiple window lengths. In some approaches, some PPW identifiers may correspond to NTN positioning, and some PPW identifiers may correspond to TN positioning. PPWs for NTN positioning may have relatively longer durations. For instance, PPW window lengths for NTN positioning may be 320 slots, 640 slots, 2560 slots, or another duration. In some aspects, a PPW start time (e.g., start offset) or a PPW duration (or length) may vary with time due to a changing distance between the wireless device and an NTN node. In some examples, PRSs in the PPW may be prioritized, where the priority may be based on configuration information, indicated explicitly, or determined based on a window order.

[0063] Aspects of the disclosure are described in the context of wireless communications systems. Aspects of the disclosure are also described in the context of a wireless network structure. Aspects of the disclosure are further described in the context of a network architecture. Aspects of the disclosure are additionally described in the context of timing diagrams and process flows. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to processing windows for NTN node-based positioning.Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO13

[0064] FIG. 1 shows an example of a wireless communications system 100 that supports processing windows for NTN node-based positioning in accordance with one or more aspects of the present disclosure. The wireless communications system 100 may include one or more devices, such as one or more network devices (e.g., network nodes 105), one or more UEs 115, and a core network 130. In some examples, the wireless communications system 100 may be a Long Term Evolution (LTE) network, an LTE- Advanced (LTE- A) network, an LTE-A Pro network, an NR network, or a network operating in accordance with other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0065] The network nodes 105 may be dispersed throughout a geographic area to form the wireless communications system 100 and may include devices in different forms or having different capabilities. In various examples, a network node 105 may be referred to as a network element, a network entity, a mobility element, a RAN node, or network equipment, among other nomenclature. In some examples, network nodes 105 and UEs 115 may wirelessly communicate via communication link(s) 125 (e.g., a RF access link). For example, a network node 105 may support a coverage area 110 (e.g., a geographic coverage area) over which the UEs 115 and the network node 105 may establish the communication link(s) 125. The coverage area 110 may be an example of a geographic area over which a network node 105 and a UE 115 may support the communication of signals according to one or more radio access technologies (RATs).

[0066] The UEs 115 may be dispersed throughout a coverage area 110 of the wireless communications system 100, and each UE 115 may be stationary, or mobile, or both at different times. The UEs 115 may be devices in different forms or have different capabilities. Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of supporting communications with various types of devices in the wireless communications system 100 (e.g., other wireless communication devices, including UEs 115 or network nodes 105), as shown in FIG. 1.

[0067] As described herein, a node of the wireless communications system 100, which may be referred to as a network entity or a wireless node, may be a network node 105 (e.g., any network node described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO14techniques described herein. For example, a node may be a UE 115. As another example, a node may be a network node 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network node 105, and the third node may be another UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network node 105, and the third node may be another network node 105. In yet other aspects of this example, the first, second, and third nodes may be different relative to these examples. Similarly, reference to a UE 115, network node 105, apparatus, device, computing system, or the like may include disclosure of the UE 115, network node 105, apparatus, device, computing system, or the like being a node. For example, disclosure that a UE 115 is configured to receive information from a network node 105 also discloses that a first node is configured to receive information from a second node.

[0068] In some examples, network nodes 105 may communicate with a core network 130, or with one another, or both. For example, network nodes 105 may communicate with the core network 130 via wired or wireless backhaul communication link(s) 120 (e.g., in accordance with an SI, N2, N3, or other interface protocol). In some examples, network nodes 105 may communicate with one another via backhaul communication link(s) 120 (e.g., in accordance with an X2, Xn, or other interface protocol) either directly (e.g., directly between network nodes 105) or indirectly (e.g., via the core network 130). In some examples, network nodes 105 may communicate with one another via a midhaul communication link 162 (e.g., in accordance with a midhaul interface protocol) or a fronthaul communication link 168 (e.g., in accordance with a fronthaul interface protocol), or any combination thereof. The backhaul communication link(s) 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., an electrical link, an optical fiber link) or one or more wireless links (e.g., a radio link, a wireless optical link), among other examples or various combinations thereof. A UE 115 may communicate with the core network 130 via a communication link 155.

[0069] One or more of the network nodes 105 or network equipment described herein may include or may be referred to as a base station 140 (e.g., a base transceiver station, a radio base station, an NR base station, an access point (AP), a radioAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO15transceiver, a NodeB, an eNodeB (eNB), a next-generation NodeB or giga-NodeB (either of which may be referred to as a gNB), a 5GNB, a next-generation eNB (ng-eNB), a Home NodeB, a Home eNodeB, or other suitable terminology). In some examples, a network node 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within one network node (e.g., a network node 105 or a single RAN node, such as a base station 140).

[0070] In some examples, a network node 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture), which may be configured to utilize a protocol stack that is physically or logically distributed among multiple network entities (e.g., network nodes 105), such as an integrated access and backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, a network node 105 may include one or more of a central unit (CU), such as a CU 160, a distributed unit (DU), such as a DU 165, a radio unit (RU), such as an RU 170, a RAN Intelligent Controller (RIC), such as an RIC 175 (e.g., a Near-Real Time RIC (Near-RT RIC), a Non-Real Time RIC (Non-RT RIC)), a Service Management and Orchestration (SMO) system, such as an SMO system 180, or any combination thereof. An RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a TRP. One or more components of the network nodes 105 in a disaggregated RAN architecture may be co-located, or one or more components of the network nodes 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more of the network nodes 105 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU), a virtual DU (VDU), a virtual RU (VRU)).

[0071] The split of functionality between a CU 160, a DU 165, and an RU 170 is flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, or any combinations thereof) are performed at a CU 160, a DU 165, or an RU 170. For example, a functional split of a protocol stack may be employed between a CU 160 andAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO16a DU 165 such that the CU 160 may support one or more layers of the protocol stack and the DU 165 may support one or more different layers of the protocol stack. In some examples, the CU 160 may host upper protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., Radio Resource Control (RRC), service data adaptation protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU 160 (e.g., one or more CUs) may be connected to a DU 165 (e.g., one or more DUs) or an RU 170 (e.g., one or more RUs), or some combination thereof, and the DUs 165, RUs 170, or both may host lower protocol layers, such as layer 1 (LI) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally, or alternatively, a functional split of the protocol stack may be employed between a DU 165 and an RU 170 such that the DU 165 may support one or more layers of the protocol stack and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or multiple different cells (e.g., via one or multiple different RUs, such as an RU 170). In some cases, a functional split between a CU 160 and a DU 165 or between a DU 165 and an RU 170 may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU 160, a DU 165, or an RU 170, while other functions of the protocol layer are performed by a different one of the CU 160, the DU 165, or the RU 170). A CU 160 may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU 160 may be connected to a DU 165 via a midhaul communication link 162 (e.g., Fl interface, Fl-c interface, or Fl-u, among other examples), and a DU 165 may be connected to an RU 170 via a fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, a midhaul communication link 162 or a fronthaul communication link 168 may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities (e.g., one or more of the network nodes 105) that are in communication via such communication links.

[0072] In some wireless communications systems (e.g., the wireless communications system 100), infrastructure and spectral resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, providing an IAB network architecture (e.g., to a core network 130). In some cases, inAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO17an IAB network, one or more of the network nodes 105 (e.g., network nodes 105 or IAB node(s) 104) may be partially controlled by each other. The IAB node(s) 104 may be referred to as a donor entity or an IAB donor. A DU 165 or an RU 170 may be partially controlled by a CU 160 associated with a network node 105 or base station 140 (such as a donor network node or a donor base station). The one or more donor entities (e.g., IAB donors) may be in communication with one or more additional devices (e.g., IAB node(s) 104) via supported access and backhaul links (e.g., backhaul communication link(s) 120). IAB node(s) 104 may include an IAB mobile termination (IAB-MT) controlled (e.g., scheduled) by one or more DUs (e.g., DUs 165) of a coupled IAB donor. An IAB-MT may be equipped with an independent set of antennas for relay of communications with UEs 115 or may share the same antennas (e.g., of an RU 170) of IAB node(s) 104 used for access via the DU 165 of the IAB node(s) 104 (e.g., referred to as virtual IAB-MT (vIAB-MT)). In some examples, the IAB node(s) 104 may include one or more DUs (e.g., DUs 165) that support communication links with additional entities (e.g., IAB node(s) 104, UEs 115) within the relay chain or configuration of the access network (e.g., downstream). In such cases, one or more components of the disaggregated RAN architecture (e.g., the IAB node(s) 104 or components of the IAB node(s) 104) may be configured to operate according to the techniques described herein.

[0073] For instance, an access network (AN) or RAN may include communications between access nodes (e.g., an IAB donor), IAB node(s) 104, and one or more UEs 115. The IAB donor may facilitate connection between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, an IAB donor may refer to a RAN node with a wired or wireless connection to the core network 130. The IAB donor may include one or more of a CU 160, a DU 165, and an RU 170, in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and IAB node(s) 104 may communicate via an Fl interface according to a protocol that defines signaling messages (e.g., an Fl AP protocol). Additionally, or alternatively, the CU 160 may communicate with the core network 130 via an interface, which may be an example of a portion of a backhaul link, and may communicate with other CUs (e.g., including a CU 160 associated with an alternative IAB donor) via an Xn-C interface, which may be an example of another portion of a backhaul link.Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO18

[0074] IAB node(s) 104 may refer to RAN nodes that provide IAB functionality (e.g., access for UEs 115, wireless self-backhauling capabilities). A DU 165 may act as a distributed scheduling node towards child nodes associated with the IAB node(s) 104, and the IAB-MT may act as a scheduled node towards parent nodes associated with IAB node(s) 104. That is, an IAB donor may be referred to as a parent node in communication with one or more child nodes (e.g., an IAB donor may relay transmissions for UEs through other IAB node(s) 104). Additionally, or alternatively, IAB node(s) 104 may also be referred to as parent nodes or child nodes to other IAB node(s) 104, depending on the relay chain or configuration of the AN. The IAB-MT entity of IAB node(s) 104 may provide a Uu interface for a child IAB node (e.g., the IAB node(s) 104) to receive signaling from a parent IAB node (e.g., the IAB node(s) 104), and a DU interface (e.g., a DU 165) may provide a Uu interface for a parent IAB node to signal to a child IAB node or UE 115.

[0075] For example, IAB node(s) 104 may be referred to as parent nodes that support communications for child IAB nodes, or may be referred to as child IAB nodes associated with IAB donors, or both. An IAB donor may include a CU 160 with a wired or wireless connection (e.g., backhaul communication link(s) 120) to the core network 130 and may act as a parent node to IAB node(s) 104. For example, the DU 165 of an IAB donor may relay transmissions to UEs 115 through IAB node(s) 104, or may directly signal transmissions to a UE 115, or both. The CU 160 of the IAB donor may signal communication link establishment via an Fl interface to IAB node(s) 104, and the IAB node(s) 104 may schedule transmissions (e.g., transmissions to the UEs 115 relayed from the IAB donor) through one or more DUs (e.g., DUs 165). That is, data may be relayed to and from IAB node(s) 104 via signaling via an NR Uu interface to MT of IAB node(s) 104 (e.g., other IAB node(s)). Communications with IAB node(s) 104 may be scheduled by a DU 165 of the IAB donor or of IAB node(s) 104.

[0076] In the case of the techniques described herein applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support testing as described herein. For example, some operations described as being performed by a UE 115 or a network node 105 (e.g., a base station 140) may additionally, or alternatively, be performed by one or moreAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO19components of the disaggregated RAN architecture (e.g., components such as an IAB node, a DU 165, a CU 160, an RU 170, an RIC 175, an SMO system 180).

[0077] A UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where the “device” may also be referred to as a unit, a station, a terminal, or a client, among other examples. A UE 115 may also include or may be referred to as a personal electronic device such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, a UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (loT) device, an Internet of Everything (loE) device, or a machine type communications (MTC) device, among other examples, which may be implemented in various objects such as appliances, vehicles, or meters, among other examples.

[0078] The UEs 115 described herein may be able to communicate with various types of devices, such as UEs 115 that may sometimes operate as relays, as well as the network nodes 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown in FIG. 1.

[0079] The UEs 115 and the network nodes 105 may wirelessly communicate with one another via the communication link(s) 125 (e.g., one or more access links) using resources associated with one or more carriers. The term “carrier” may refer to a set of RF spectrum resources having a defined PHY layer structure for supporting the communication link(s) 125. For example, a carrier used for the communication link(s) 125 may include a portion of an RF spectrum band (e.g., a bandwidth part (BWP)) that is operated according to one or more PHY layer channels for a given RAT (e.g., LTE, LTE-A, LTE-A Pro, NR). Each PHY layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling that coordinates operation for the carrier, user data, or other signaling. The wireless communications system 100 may support communication with a UE 115 using carrier aggregation or multi-carrier operation. A UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers.Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO20Communication between a network node 105 and other devices may refer to communication between the devices and any portion (e.g., entity, sub-entity) of a network node 105. For example, the terms “transmitting,” “receiving,” or “communicating,” when referring to a network node 105, may refer to any portion of a network node 105 (e.g., a base station 140, a CU 160, a DU 165, a RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities, such as one or more of the network nodes 105).

[0080] In some examples, such as in a carrier aggregation configuration, a carrier may have acquisition signaling or control signaling that coordinates operations for other carriers. A carrier may be associated with a frequency channel (e.g., an evolved universal mobile telecommunication system terrestrial radio access (E-UTRA) absolute RF channel number (EARFCN)) and may be identified according to a channel raster for discovery by the UEs 115. A carrier may be operated in a standalone mode, in which case initial acquisition and connection may be conducted by the UEs 115 via the carrier, or the carrier may be operated in a non- standalone mode, in which case a connection is anchored using a different carrier (e.g., of the same or a different RAT).

[0081] The communication link(s) 125 of the wireless communications system 100 may include downlink transmissions (e.g., forward link transmissions) from a network node 105 to a UE 115, uplink transmissions (e.g., return link transmissions) from a UE 115 to a network node 105, or both, among other configurations of transmissions.Carriers may carry downlink or uplink communications (e.g., in an FDD mode) or may be configured to carry downlink and uplink communications (e.g., in a TDD mode).

[0082] A carrier may be associated with a particular bandwidth of the RF spectrum and, in some examples, the carrier bandwidth may be referred to as a “system bandwidth” of the carrier or the wireless communications system 100. For example, the carrier bandwidth may be one of a set of bandwidths for carriers of a particular RAT (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)). Devices of the wireless communications system 100 (e.g., the network nodes 105, the UEs 115, or both) may have hardware configurations that support communications using a particular carrier bandwidth or may be configurable to support communications using one of a set of carrier bandwidths. In some examples, the wireless communications system 100 may include network nodes 105 or UEs 115 that support concurrent communications using Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO21carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured for operating using portions (e.g., a sub-band, a BWP) or all of a carrier bandwidth.

[0083] Signal waveforms transmitted via a carrier may be made up of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may refer to resources of one symbol period (e.g., a duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The quantity of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), such that a relatively higher quantity of resource elements (e.g., in a transmission duration) and a relatively higher order of a modulation scheme may correspond to a relatively higher rate of communication. A wireless communications resource may refer to a combination of an RF spectrum resource, a time resource, and a spatial resource (e.g., a spatial layer, a beam), and the use of multiple spatial resources may increase the data rate or data integrity for communications with a UE 115.

[0084] One or more numerologies for a carrier may be supported, and a numerology may include a subcarrier spacing (A ) and a cyclic prefix. A carrier may be divided into one or more BWPs having the same or different numerologies. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time and communications for the UE 115 may be restricted to one or more active BWPs.

[0085] The time intervals for the network nodes 105 or the UEs 115 may be expressed in multiples of a basic time unit which may, for example, refer to a sampling period of Ts= l / (A / max■ Ay) seconds, for which fmaxmay represent a supported subcarrier spacing, and Ay may represent a supported discrete Fourier transform (DFT) size. Time intervals of a communications resource may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO1

[0086] Each frame may include multiple consecutively-numbered subframes or slots, and each subframe or slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a quantity of slots. Alternatively, each frame may include a variable quantity of slots, and the quantity of slots may depend on subcarrier spacing. Each slot may include a quantity of symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period). In some wireless communications systems, such as the wireless communications system 100, a slot may further be divided into multiple mini-slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., N ) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or frequency band of operation.

[0087] A subframe, a slot, a mini-slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communications system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., a quantity of symbol periods in a TTI) may be variable. Additionally, or alternatively, the smallest scheduling unit of the wireless communications system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs)).

[0088] Physical channels may be multiplexed for communication using a carrier according to various techniques. A physical control channel and a physical data channel may be multiplexed for signaling via a downlink carrier, for example, using one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques. A control region (e.g., a control resource set (CORESET)) for a physical control channel may be defined by a set of symbol periods and may extend across the system bandwidth or a subset of the system bandwidth of the carrier. One or more control regions (e.g., CORESETs) may be configured for a set of the UEs 115. For example, one or more of the UEs 115 may monitor or search control regions for control information according to one or more search space sets, and each search space set may include one or multiple control channel candidates in one or more aggregation levels arranged in a cascaded manner. An aggregation level for a control channel candidate may refer to an amount of control channel resources (e.g., control channel elements (CCEs)) associated with encodedAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO23information for a control information format having a given payload size. Search space sets may include common search space sets configured for sending control information to UEs 115 (e.g., one or more UEs) or may include UE-specific search space sets for sending control information to a UE 115 (e.g., a specific UE).

[0089] A network node 105 may provide communication coverage via one or more cells, for example a macro cell, a small cell, a hot spot, or other types of cells, or any combination thereof. The term “cell” may refer to a logical communication entity used for communication with a network node 105 (e.g., using a carrier) and may be associated with an identifier for distinguishing neighboring cells (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID)). In some examples, a cell also may refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) over which the logical communication entity operates. Such cells may range from smaller areas (e.g., a structure, a subset of structure) to larger areas depending on various factors such as the capabilities of the network node 105. For example, a cell may be or include a building, a subset of a building, or exterior spaces between or overlapping with coverage areas 110, among other examples.

[0090] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by the UEs 115 with service subscriptions with the network provider supporting the macro cell. A small cell may be associated with a network node 105 operating with lower power (e.g., a base station 140 operating with lower power) relative to a macro cell, and a small cell may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to the UEs 115 with service subscriptions with the network provider or may provide restricted access to the UEs 115 having an association with the small cell (e.g., the UEs 115 in a closed subscriber group (CSG), the UEs 115 associated with users in a home or office). A network node 105 may support one or more cells and may also support communications via the one or more cells using one or multiple component carriers.

[0091] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband loT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access for different types of devices.Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO24

[0092] In some examples, a network node 105 (e.g., a base station 140, an RU 170) may be movable and therefore provide communication coverage for a moving coverage area, such as the coverage area 110. In some examples, coverage areas 110 (e.g., different coverage areas) associated with different technologies may overlap, but the coverage areas 110 (e.g., different coverage areas) may be supported by the same network node (e.g., a network node 105). In some other examples, overlapping coverage areas, such as a coverage area 110, associated with different technologies may be supported by different network entities (e.g., the network nodes 105). The wireless communications system 100 may include, for example, a heterogeneous network in which different types of the network nodes 105 support communications for coverage areas 110 (e.g., different coverage areas) using the same or different RATs.

[0093] The wireless communications system 100 may support synchronous or asynchronous operation. For synchronous operation, network nodes 105 (e.g., base stations 140) may have similar frame timings, and transmissions from different network entities (e.g., different ones of the network nodes 105) may be approximately aligned in time. For asynchronous operation, network nodes 105 may have different frame timings, and transmissions from different network entities (e.g., different ones of network nodes 105) may, in some examples, not be aligned in time. The techniques described herein may be used for either synchronous or asynchronous operations.

[0094] Some UEs 115, such as MTC or loT devices, may be relatively low cost or low complexity devices and may provide for automated communication between machines (e.g., via Machine-to-Machine (M2M) communication). M2M communication or MTC may refer to data communication technologies that allow devices to communicate with one another or a network node 105 (e.g., a base station 140) without human intervention. In some examples, M2M communication or MTC may include communications from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application program that uses the information or presents the information to humans interacting with the application program. Some UEs 115 may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather andAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO25geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.

[0095] Some UEs 115 may be configured to employ operating modes that reduce power consumption, such as half-duplex communications (e.g., a mode that supports one-way communication via transmission or reception, but not transmission and reception concurrently). In some examples, half-duplex communications may be performed at a reduced peak rate. Other power conservation techniques for the UEs 115 may include entering a power saving deep sleep mode when not engaging in active communications, operating using a limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some UEs 115 may be configured for operation using a narrowband protocol type that is associated with a defined portion or range (e.g., set of subcarriers or resource blocks (RBs)) within a carrier, within a guard-band of a carrier, or outside of a carrier.

[0096] The wireless communications system 100 may be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof. For example, the wireless communications system 100 may be configured to support ultra-reliable low-latency communications (URLLC). The UEs 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communications may include private communication or group communication and may be supported by one or more services such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.

[0097] In some examples, a UE 115 may be configured to support communicating directly with other UEs (e.g., one or more of the UEs 115) via a D2D communication link, such as a D2D communication link 135 (e.g., in accordance with a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 of a group that are performing D2D communications may be within the coverage area 110 of a network node 105 (e.g., a base station 140, an RU 170), which may support aspects of such D2D communications being configured by (e.g., scheduled by) the network node 105. In some examples, one or more UEs 115 of such a group may be outside the Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO26coverage area 110 of a network node 105 or may be otherwise unable to or not configured to receive transmissions from a network node 105. In some examples, groups of the UEs 115 communicating via D2D communications may support a one-to-many (1 :M) system in which each UE 115 transmits to one or more of the UEs 115 in the group. In some examples, a network node 105 may facilitate the scheduling of resources for D2D communications. In some other examples, D2D communications may be carried out between the UEs 115 without an involvement of a network node 105.

[0098] In some systems, a D2D communication link 135 may be an example of a communication channel, such as a sidelink communication channel, between vehicles (e.g., UEs 115). In some examples, vehicles may communicate using vehicle-to-everything (V2X) communications, vehicle-to-vehicle (V2V) communications, or some combination of these. A vehicle may signal information related to traffic conditions, signal scheduling, weather, safety, emergencies, or any other information relevant to a V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure, such as roadside units, or with the network via one or more network entities (e.g., network nodes 105, base stations 140, RUs 170) using vehicle-to-network (V2N) communications, or with both.

[0099] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or 5G core (5GC), which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an AMF) and at least one user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)). The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UEs 115 served by the network nodes 105 (e.g., base stations 140) associated with the core network 130. User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions. The user plane entity may be connected to IP services 150 for one or more network operators. The IP services 150Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO27may include access to the Internet, Intranet(s), an IP Multimedia Subsystem (IMS), or a Packet- Switched Streaming Service.

[0100] The wireless communications system 100 may include an location server 185 (e.g., LMF). The location server 185 may provide positioning, location, or tracking functions. For instance, the location server 185 may participate in one or more positioning procedures to determine a location of (e.g., coordinates of, relative distance(s) to, or an address of) one or more of the UEs 115. Examples of positioning procedures may include one or more operations of assisted global navigation satellite system (A-GNSS), observed time difference of arrival (OTDOA), enhanced cell identifier (E-CID), sensor-based positioning, wireless local area network (WLAN)-based positioning, Bluetooth-based positioning, terrestrial beacon systems (TBS) positioning, downlink time difference of arrival (DL-TDOA), downlink angle of departure (DL-AOD), multi-round-trip time (Multi-RTT), New Radio enhanced cell identifier (NR E-CID), uplink time difference of arrival (UL-TDOA), and uplink angle of arrival (UL-AOA), among other examples. Some examples of the positioning procedures may be managed by, assisted by, or performed with the location server 185. For instance, measurements associated with reference signaling may be provided to the location server 185, which may estimate a location of a UE 115 based on the measurements. In some aspects, the location server 185 may track or store location information corresponding to one or more UEs 115. Some examples of the positioning procedures may be performed without the location server 185.

[0101] The location server 185 may be included in the core network 130 or may be separate from the core network 130. In some examples, a location server 185 may be a standalone device or may be included in (e.g., integrated with) a network node 105, a base station 140, a UE 115, a satellite 190, a server, or another device. For instance, the location server 185 may be (or may be included in) a secure user plane location (SUPL) location platform (SLP) device, a third-party server, or another device. The location server 185 may generally refer to a positioning device, a location device, a computing device, or a server, among other examples.

[0102] A UE 115 may communicate with the location server 185 directly or indirectly. For example, a UE 115 may communicate with the location server 185 via a network node 105 that is serving the UE 115 and via the core network 130.Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO28Additionally, or alternatively, a UE 115 may communicate with the location server 185 through another path (e.g., via an application server) or via another network (e.g., via a WLAN AP), among other examples. Communication between a UE 115 and the location server 185 may be represented via an indirect connection (e.g., through a communication link 125, a network node 105, a communication link 155, a backhaul communication link 120, or the core network 130) or as a direct connection, with one or more intervening nodes (if any) omitted for concision or convenience.

[0103] A satellite 190 may be an aerial or space vehicle with signaling capability. In some examples, the wireless communications system 100 may include or communicate with one or more satellites 190. The satellite(s) 190 may be included in one or more satellite positioning systems (e.g., GNSS(s)). A satellite positioning system may include any combination of one or more global or regional navigation satellites associated with one or more satellite positioning systems (e.g., global positioning system (GPS), global navigation satellite system (GLONASS), BeiDou navigation satellite system (BDS), or Galileo, among other examples). A satellite positioning system may include satellites 190 or other transmitters positioned to enable receivers (e.g., UEs 115) to determine a location on or above the Earth based on signals (e.g., the signals 195) received from the satellites 190. For instance, each satellite 190 may transmit a signal 195 marked with a repeating pseudo-random noise (PN) code of a set quantity of chips. In some cases, one or more transmitters located on ground-based control stations, network nodes 105, or UEs 115 may transmit signals for enabling a UE 115 to determine a location.

[0104] A UE 115 may include one or more receivers designed to receive the signal(s) 195 from the satellite(s) 190 for determining location information (e.g., a geographic location of the UE 115). For instance, the UE 115 may receive one or more signals 195 from the satellite(s) 190, which may be utilized to determine a location of the UE 115.

[0105] In a satellite positioning system, the use of signals 195 may be augmented with one or more satellite-based augmentation systems (SB AS) that may be associated with or enabled for use with one or more global or regional navigation satellite systems. An SB AS may provide integrity information, differential corrections, or other information for use in conjunction with a satellite positioning system. An SBAS may include one or more augmentation systems, such as the Wide Area Augmentation Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO29System (WAAS), the European Geostationary Navigation Overlay Service (EGNOS), the Multi-functional Satellite Augmentation System (MSAS), or the GPS Aided Geo Augmented Navigation (GAGAN) system, among other examples.

[0106] In some aspects, the satellite(s) 190 may be included in one or more NTNs. In an NTN, a satellite 190 may communicate with one or more devices (e.g., network entities, ground stations, NTN gateways, or gateways) located on or above the Earth. For example, the satellite 190 may send or receive one or more communications 192 with a network node 105. In some aspects, the communication(s) 192 may include one or more signals relayed to or from a UE 115. Additionally, or alternatively, the satellite 190 may communicate with another terrestrial device that is connected to one or more elements of the wireless communications system 100. For instance, the satellite 190 may communicate with a ground station or NTN gateway, which may provide access to the wireless communications system 100 or one or more other entities (e.g., Internet web servers or one or more other user devices) external to the wireless communications system 100. In some examples, a UE 115 may receive communication signals 195 from the satellite 190 instead of, or in addition to, communication signals from a terrestrial network entity.

[0107] The wireless communications system 100 may operate using one or more frequency bands, which may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features, which may be referred to as clusters, but the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than one hundred kilometers) compared to communications using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.

[0108] The wireless communications system 100 may also operate using a super high frequency (SHF) region, which may be in the range of 3 GHz to 30 GHz, also known as the centimeter band, or using an extremely high frequency (EHF) region ofAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO30the spectrum (e.g., from 30 GHz to 300 GHz), also known as the millimeter band. In some examples, the wireless communications system 100 may support millimeter wave (mmW) communications between the UEs 115 and the network nodes 105 (e.g., base stations 140, RUs 170), and EHF antennas of the respective devices may be smaller and more closely spaced than UHF antennas. In some examples, such techniques may facilitate using antenna arrays within a device. The propagation of EHF transmissions, however, may be subject to even greater attenuation and shorter range than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions that use one or more different frequency regions, and designated use of bands across these frequency regions may differ by country or regulating body.

[0109] The wireless communications system 100 may utilize licensed or unlicensed RF spectrum bands. For example, the wireless communications system 100 may employ License Assisted Access (LAA), LTE-Unlicensed (LTE-U) RAT, or NR technology using an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band. Devices in the wireless communications system 100 may communicate over unlicensed spectrum, such as the 5 GHz band, the 2.4 GHz band, the 60 GHz band, the 3.6 GHz band, and / or the 900 MHz band. The unlicensed spectrum may also include other frequency bands. While operating using unlicensed RF spectrum bands, devices such as the network nodes 105 and the UEs 115 may employ carrier sensing for collision detection and avoidance. In some examples, operations using unlicensed bands may be based on a carrier aggregation configuration in conjunction with component carriers operating using a licensed band (e.g., LAA). Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.

[0110] A network node 105 (e.g., a base station 140, an RU 170) or a UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of a network node 105 or a UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with a networkAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO31node 105 may be located at diverse geographic locations. A network node 105 may include an antenna array with a set of rows and columns of antenna ports that the network node 105 may use to support beamforming of communications with a UE 115. Likewise, a UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally, or alternatively, an antenna panel may support RF beamforming for a signal transmitted via an antenna port.[OHl] The network nodes 105 or the UEs 115 may use MIMO communications to exploit multipath signal propagation and increase spectral efficiency by transmitting or receiving multiple signals via different spatial layers. Such techniques may be referred to as spatial multiplexing. The multiple signals may, for example, be transmitted by the transmitting device via different antennas or different combinations of antennas.Likewise, the multiple signals may be received by the receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO), for which multiple spatial layers are transmitted to the same receiving device, and multiple-user MIMO (MU-MIMO), for which multiple spatial layers are transmitted to multiple devices.

[0112] Beamforming, which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network node 105, a UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining the signals communicated via antenna elements of an antenna array such that some signals propagating along particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference. The adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying amplitude offsets, phase offsets, or both to signals carried via the antenna elements associated with the device. The adjustments associated with each of the antenna elements may be defined by aAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO32beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation).

[0113] A network node 105 or a UE 115 may use beam sweeping techniques as part of beamforming operations. For example, a network node 105 (e.g., a base station 140, an RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to conduct beamforming operations for directional communications with a UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted by a network node 105 multiple times along different directions. For example, the network node 105 may transmit a signal according to different beamforming weight sets associated with different directions of transmission. Transmissions along different beam directions may be used to identify (e.g., by a transmitting device, such as a network node 105, or by a receiving device, such as a UE 115) a beam direction for later transmission or reception by the network node 105.

[0114] Some signals, such as data signals associated with a particular receiving device, may be transmitted by a transmitting device (e.g., a network node 105 or a UE 115) along a single beam direction (e.g., a direction associated with the receiving device, such as another network node 105 or UE 115). In some examples, the beam direction associated with transmissions along a single beam direction may be determined based on a signal that was transmitted along one or more beam directions. For example, a UE 115 may receive one or more of the signals transmitted by the network node 105 along different directions and may report to the network node 105 an indication of the signal that the UE 115 received with a highest signal quality or an otherwise acceptable signal quality.

[0115] In some examples, transmissions by a device (e.g., by a network node 105 or a UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from a network node 105 to a UE 115). The UE 115 may report feedback that indicates precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more sub-bands. The network node 105 may transmit a reference signal (e.g., a Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO33cell-specific reference signal (CRS), a CSI-RS), which may be precoded or unprecoded. The UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook). Although these techniques are described with reference to signals transmitted along one or more directions by a network node 105 (e.g., a base station 140, an RU 170), a UE 115 may employ similar techniques for transmitting signals multiple times along different directions (e.g., for identifying a beam direction for subsequent transmission or reception by the UE 115) or for transmitting a signal along a single direction (e.g., for transmitting data to a receiving device).

[0116] A receiving device (e.g., a UE 115) may perform reception operations in accordance with multiple receive configurations (e.g., directional listening) when receiving various signals from a transmitting device (e.g., a network node 105), such as synchronization signals, reference signals, beam selection signals, or other control signals. For example, a receiving device may perform reception in accordance with multiple receive directions by receiving via different antenna subarrays, by processing received signals according to different antenna subarrays, by receiving according to different receive beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or by processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as “listening” according to different receive configurations or receive directions. In some examples, a receiving device may use a single receive configuration to receive along a single beam direction (e.g., when receiving a data signal). The single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have a highest signal strength, highest signal-to-noise ratio (SNR), or otherwise acceptable signal quality based on listening according to multiple beam directions).

[0117] The wireless communications system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, communications at the bearer or PDCP layer may be IP -based. An RLC layer may perform packetAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO34segmentation and reassembly to communicate via logical channels. A MAC layer may perform priority handling and multiplexing of logical channels into transport channels. The MAC layer also may implement error detection techniques, error correction techniques, or both to support retransmissions to improve link efficiency. In the control plane, an RRC layer may provide establishment, configuration, and maintenance of an RRC connection between a UE 115 and a network node 105 or a core network 130 supporting radio bearers for user plane data. A PHY layer may map transport channels to physical channels.

[0118] The UEs 115 and the network nodes 105 may support retransmissions of data to increase the likelihood that data is received successfully. Hybrid automatic repeat request (HARQ) feedback is one technique for increasing the likelihood that data is received correctly via a communication link (e.g., the communication link(s) 125, a D2D communication link 135). HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve throughput at the MAC layer in relatively poor radio conditions (e.g., low signal -to-noise conditions). In some examples, a device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific slot for data received via a previous symbol in the slot. In some other examples, the device may provide HARQ feedback in a subsequent slot, or according to some other time interval.

[0119] Some wireless communication systems utilize signals to perform positioning procedures. For example, a UE 115 may receive signals from one or more TN nodes (e.g., network nodes 105) to perform positioning procedures. Performing positioning based on signals from one or more NTN nodes (e.g., satellites 190) may pose a variety of challenges. In an example, three NTN satellites may transmit a positioning signal at the same time. The positioning signaling may be broadcasted signals for all UEs 115 within a coverage region. The distances between a UE 115 and the NTN nodes (e.g., satellites 190) may be relatively large and may vary from satellite to satellite. In some cases, a UE 115 may utilize NTN positioning measurements without measurement gaps (e.g., a PPW). With defined measurement gaps, a single PPW that can accommodate large propagation delay is not supported in some approaches. For instance, someAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO35approaches may limit PPW length to 160 slots with one or more options for periodicity or start offsets based on a SCS.

[0120] In some examples, a UE may be provided a target RSTD value with an uncertainty (e.g., search space window) for one or more TN TRPs indicated in assistance data (e.g., RSTD assistance data for downlink PRS processing). In some approaches, the value range of the target RSTD may be ± 500 microseconds (ps). A value range for an uncertainty of the target RSTD may vary based on whether positioning measurements (e.g., measurements of downlink PRSs) are associated with frequency range 1 (FR1) or frequency range 2 (FR2). When one or more of the resources used for downlink positioning measurement are in FR1, the uncertainty may be ± 32 ps. When one or more of the resources used for the downlink positioning measurement are in FR2, the uncertainty may be ± 8 ps. For NTN nodes, however, the value range for a target RSTD or an uncertainty may be an order of magnitude larger than those for TN TRPs.

[0121] Examples of NTN platforms (e.g., types of satellites 190) that may be utilized in accordance with some of the techniques described herein are described in Table (1). Different platforms may have different distances, delays, or coverage on the Earth.Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO36Table (1)

[0122] Some examples of propagation ranges that may be supported in some examples of the techniques described herein are provided in Table (2). Other propagation values or ranges may be utilized or supported in other examples.Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO37Atorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO38Table (2)

[0123] As discussed above, a TN propagation delay may be on the order of ps. Based on Table (2), the propagation difference for GEO A is 542 - 477 = 65 ms, for GEO B is 270 - 238 = 32 ms, for LEO A is 25 - 8 = 17 ms, and for LEO B is 13 - 4 = 7 ms. The propagation delay for an NTN may be an order of magnitude larger than the propagation delay for TN.

[0124] The difference in propagation delay may impact measurements. In an example scenario, a UE 115 may be served by a LEO satellite SI, and may also be within coverage of an incoming LEO satellite S2. The UE may perform measurements of the neighboring cell(s) originating from S2 for mobility purposes based on a measurement configuration provided to the UE 115. However, the propagation delay difference from the UE 115 to satellite S 1 and from the UE 115 to satellite S2 may vary significantly. If an SMTC measurement gap configuration does not account for the propagation delay difference, the UE 115 may miss the SSB or CSLRS measurement window and may thus be unable to perform measurements on the configured reference signals. This challenge may occur for GEO and LEO scenarios. A similar issue may arise in the positioning measurement in scenarios with a difference between RSTD measurements is relatively large or a gap duration is small.

[0125] In some approaches, a PPW may be established to provide a time period or window for a UE 115 to receive or measure a PRS. Some aspects of an example of a PPW are provided is Listing (1). As illustrated in Listing (1), up to four PPW identifiersAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO39may be configured per BWP, where one (e.g., only one) may be activated at a given time.maxNrofPPW-Config-rl7 INTEGER ::= 4 — Maximum quantity of Preconfigured PRS processing windows per downlink bandwidth part (DL BWP)maxNrofPPW-ID-l-rl7 INTEGER ::= 15 — Maximum quantity of Preconfigured PRS processing windows minus 1DL-PPW-PreConfigToAddModList-rl7 ::= SEQUENCE (SIZE (L.maxNrofPPW-Config-rl7)) OF DL-PPW-PreConfig-rl7DL-PPW-PreConfigToReleaseList-rl7 ::= SEQUENCE (SIZE (L.maxNrofPPW-Config-rl7)) OF DL-PPW-ID-rl7DL-PPW-PreConfig-rl7 ::= SEQUENCE {dl-PPW-ID-rl7 DL-PPW-ID-rl7,dl-PPW-PeriodicityAndStartSlot-rl7 DL-PPW-PeriodicityAndStartSlot-rl7,length-rl7 INTEGER (1..160),type-rl7 ENUMERATED {typelA, typelB, type2} OPTIONAL, — Cond MultiTypepriority-rl7 ENUMERATED {stl, st2, st3 } OPTIONAL — Cond MultiState }DL-PPW-ID-rl7 ::= INTEGER (0..maxNrofPPW-ID-l-rl7)Listing (1)In Listing (1), dl-PPW-ID may indicate a configured identifier for downlink PPW configuration, dl-PPW-PeriodicityAndStartSlot may indicate a periodicity in slots andAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO40an offset of the starting slot with respect to subframe number (SFN) #0 of a serving cell where a downlink PPW is configured, length may indicate a length of a downlink PPW in slots (e.g., a value of ‘ 1’ may indicate a length of one slot, a value ‘2’ may indicate a length of two slots, and so on), priority may indicate a priority between a physical downlink control channel (PDCCH), a physical downlink shared channel (PDSCH), a CSI-RS, or PRS, and type may indicate a downlink PFS processing window type.

[0126] In some approaches, a PPW may have an associated configuration type. In configuration typel A, when a UE is to measure a downlink PRS outside a measurement gap if the UE is supporting a capability (e.g., capability 1 A), and if the downlink PRS is determined to be a higher priority than the downlink signals and channels inside the PPW, those downlink signals or channels may not be measured by the UE. In configuration typelB, when a UE is to measure the downlink PRS outside a measurement gap if the UE is supporting a capability (e.g., capability IB), and if the downlink PRS is determined to be higher priority than the downlink signals and channels inside the PPW, those downlink signals or channels in the same band as the downlink PRS may not be measured by the UE. In configuration type2, when the UE is to measure a downlink PRS outside a measurement gap if the UE is supporting a capability (e.g., capability 2), and if the downlink PRS is determined to be higher priority than the downlink signals and channels inside the PPW, those downlink signals and channels may not be measured by the UE on the overlapped symbols with the downlink PRS. In some aspects, with a first value (e.g., “st 1”), a downlink PRS may have a higher priority than all downlink signals and channels, with a second value (e.g., “st2”), a downlink PRS may have a lower priority than a PDCCH or a PDSCH scheduled by downlink control information (DCI) formats 1 1, 1 2, 1 3 or 4 2 with a priority indicator field in the corresponding DCI format set to 1, and may have a higher priority than other downlink signals and channels, or with a third value (e.g., “st3”), the downlink PRS may have a lower priority than all downlink signals and channels.

[0127] Regarding PPW processing, an example of a PRS-ProcessingCapabilityOutsideMGinPPWperType information element (IE) is provided in Listing (2). The IE PRS-ProcessingCapabilityOutsideMGinPPWperType may be utilized to indicate a downlink PRS Processing Capability outside measurement gap (MG) capabilities supported by a UE.Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO41- ASN1 START- TAG-PRS-PROCESSINGCAPABILITYOUTSIDEMGINPPWPERType-STARTPRS-ProcessingCapabilityOutsideMGinPPWperType-rl7 ::= SEQUENCE { prsProcessingType-rl7 ENUMERATED {typelA, typelB, type2},ppw-dl-PRS-BufferType-rl7 ENUMERATED {typel, type2, ...}, ppw-durationOfPRS-Processing-rl7 CHOICE {ppw-durationOfPRS-Processingl-rl7 SEQUENCE {ppw-durationOfPRS-ProcessingSymbolsN-r 17 ENUMERATED {msDotl25, msDot25, msDot5, msl, ms2, ms4, ms6, ms8, msl2,msl6, ms20, ms25, ms30, ms32, ms35, ms40, ms45, ms50{,ppw-durationOfPRS-ProcessingSymbolsT-rl7 ENUMERATED {msl, ms2, ms4, ms8, msl6, ms20, ms30, ms40, ms80,msl60, ms320, ms640, msl280}ppw-durationOfPRS-Processing2-rl7 SEQUENCE {ppw-durationOfPRS-ProcessingSymbolsN2-rl7 ENUMERATED {msDotl25, msDot25, msDot5, msl, ms2, ms3, ms4, ms5,ms6, ms8, msl2},ppw-durationOfPRS-ProcessingSymbolsT2-rl7 ENUMERATED {ms4, ms5, ms6, ms8}OPTIONAL,ppw-maxNumOfDL-PRS-ResProcessedPerSlot-rl7 SEQUENCE { scsl5-rl7 ENUMERATED {nl, n2, n4, n6, n8, nl2, nl6, n24, n32, n48, n64} OPTIONAL,scs30-rl7 ENUMERATED {nl, n2, n4, n6, n8, nl2, nl6, n24, n32, n48, n64} OPTIONAL,scs60-rl7 ENUMERATED {nl, n2, n4, n6, n8, nl2, nl6, n24, n32, n48, n64} OPTIONAL,Atorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO42scsl20-rl7 ENUMERATED {nl, n2, n4, n6, n8, nl2, nl6, n24, n32, n48, n64} OPTIONAL,},ppw-maxNumOfDL-Bandwidth-rl7 CHOICE {frl-rl7 ENUMERATED {mhz5, mhzlO, mhz20, mhz40, mhz50, mhz80, mhzlOO},fr2-rl7 ENUMERATED {mhz50, mhzlOO, mhz200, mhz400}}OPTIONAL}- TAG-PRS-PROCESSINGCAPABILITYOUTSIDEMGINPPWPERType-STOP - ASN1STOPListing (2)

[0128] In an example of PRS signaling, two NTN PRSs may be scheduled. The two NTN PRSs may be received at a UE at different times, where one gap (e.g., measurement gap) may not be long enough to capture the PRSs (e.g., both PRSs from different NTN nodes). In this example, a UE may utilize a first PPW identifier (PPW-ID-1) configuration to decode the first PRS signal from a first NTN node. The first PPW may have a PPW length (e.g., Iength-rl7), slot offset, and periodicity (e.g., dl-PPW-PeriodicityAndStartSlot-r 17). The UE may utilize a second PPW identifier (PPW-ID-2) configuration to decode the second PRS signal from a second NTN node. This approach may consume a relatively large (e.g., double an) amount of time to activate the PPW and processing of the PRS resources and to decode the NTN signaling. This approach may also have an impact on modem processing if the downlink PRS has a higher priority than another scheduled downlink signal.

[0129] One or more PPW patterns may be utilized in accordance with the techniques described herein. In some examples, a PPW identifier may correspond to multiple window lengths within the PPW. The multiple window lengths may include processing windows of different lengths. Gaps between pairs of the processing windowsAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO43may be different. Enabling multiple window lengths corresponding to one PPW identifier may enable joint activation or deactivation of multiple window lengths. In some approaches, some PPW identifiers may correspond to NTN positioning, and some PPW identifiers may correspond to TN positioning. PPWs for NTN positioning may have relatively longer durations. For instance, PPW window lengths for NTN positioning may be 320 slots, 640 slots, 2560 slots, or another duration. In some aspects, a PPW start time (e.g., start offset) or a PPW duration (or length) may vary with time due to a changing distance between the wireless device and an NTN node. In some examples, PRSs in the PPW may be prioritized, where the priority may be based on configuration information, indicated explicitly, or determined based on a window order.

[0130] FIG. 2 shows an example of a network structure 200 that supports processing windows for NTN node-based positioning in accordance with one or more aspects of the present disclosure. The wireless network structure 200 may include a core network 130-a, a RAN 225, a UE 115-a, an LMF 265, an external device 230 (e.g., third-party device or server), or an SLP 235. In some examples, the wireless network structure 200 may be included in the wireless communications system 100 described with reference to FIG. 1. The core network 130-a may be an example of the core network 130, the UE 115-a may be an example of the UEs 115, or the LMF 265 may be an example of the location server 185, as described with reference to FIG. 1.

[0131] The core network 130-a may provide one or more control plane (C-plane) functions (e.g., UE registration, authentication, network access, or gateway selection, among other examples) or one or more user plane (U-plane) functions (e.g., UE gateway function, data network access, or IP routing, among other examples). One or more of the functions of the core network 130-a may be implemented in one or more devices (e.g., one or more electronic devices, computing devices, servers, among other examples) in hardware (e.g., circuitry) or a combination of hardware and instructions (e.g., a processor with instructions). The core network 130-a may be an EPC, 5GC, or a Next Generation Core (NGC), among other examples.

[0132] The core network 130-a may provide an AMF 210, a session management function (SMF) 220, or a user plane function (UPF) 215. The AMF 210 may provide one or more C-plane functions, such as registration management, connection management, reachability management, mobility management, lawful interception, Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO44transport for session management (SM) messages between one or more UEs 115-a and the SMF 220, transparent proxy services for routing SM messages, access authentication and access authorization, transport for short message service (SMS) messages between the UE 115-a and the short message service function (SMSF), or security anchor functionality (SEAF), among other examples. In some aspects, the AMF 210 may interact with an authentication server function (AUSF) and the UE 115-a, and may receive an intermediate key established as a result of a UE 115-a authentication process. In a case of authentication based on a universal mobile telecommunications system (UMTS) subscriber identity module (USIM), the AMF 210 may retrieve security information from the AUSF. In some examples, the AMF 210 may provide a security context management (SCM) function. The SCM function may receive a key from the SEAF that may be utilized to derive access-network specific keys. The AMF 210 may provide location services management for regulatory services, transport for location services messages between the UE 115-a and an LMF 265, transport for location services messages between the RAN 225 and the LMF 265, evolved packet system (EPS) bearer identifier allocation for interworking with the EPS, or UE 115-a mobility event notification. In some approaches, the AMF 210 may support one or more functionalities for Third Generation Partnership Project (3 GPP) access networks or non-3GPP access networks.

[0133] The UPF 215 may provide one or more U-plane functions, such as acting as an anchor point for intra / inter-RAT mobility, acting as an external protocol data unit (PDU) session point of interconnection to a data network, providing packet routing and forwarding, packet inspection, user plane policy rule enforcement (e.g., gating, redirection, or traffic steering), user plane collection (e.g., interception), traffic usage reporting, quality of service (QoS) handling for the U-plane (e.g., uplink or downlink rate enforcement, reflective QoS marking in the downlink), uplink traffic verification (e.g., service data flow (SDF) to QoS flow mapping), transport level packet marking in the uplink or downlink, downlink packet buffering, downlink data notification triggering, or sending or forwarding one or more indications of an end of a transmission (e.g., “end markers”) to a source RAN node, among other examples. In some examples, the UPF 215 may support the transfer of location services messages over a U-plane between the UE 115-a and another device (e.g., the SLP 235 or the external device 230.Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO45

[0134] The SMF 220 may provide one or more functions, such as session management, UE IP address allocation and management, selection and control of user plane functions, configuration of traffic steering at the UPF 215 to route traffic to a destination, control (e.g., partial control) of policy enforcement or QoS, or downlink data notification. In some aspects, the SMF 220 may communicate with the AMF 210 over an N11 interface 240.

[0135] The RAN 225 may include one or more gNBs 255 or one or more ng-eNBs 260. The gNB(s) 255 or the ng-eNB(s) 260 may be examples of the network nodes 105 described with reference to FIG. 1. For instance, a next generation RAN (NG-RAN) may include one or more gNBs 255, or other examples of the RAN 225 may include one or more ng-eNBs 260 or gNBs 255.

[0136] The core network 130-a may communicate with the RAN 225 via a C-plane interface 245 (e.g., NG-C or N2 interface) or a U-plane interface 250 (e.g., NG-U or N3 interface). The C-plane interface 245 or the U-plane interface 250 may connect the gNB 255 or the ng-eNB 260 to the core network 130-a (e.g., to one or more control plane functions or one or more user plane functions). For instance, the C-plane interface 245 may connect the AMF 210 to one or more gNBs 255 or ng-eNBs 260 in the RAN 225, or the U-plane interface 250 may connect the UPF 215 to one or more gNBs 255 or ng-eNBs 260 in the RAN 225. The gNB(s) 255 or ng-eNB(s) 260 of the RAN 225 may communicate with each other via one or more backhaul communication links 120-a (e.g., Xn-C interface). The backhaul communication link(s) 120-a may be examples of the backhaul communication links 120 described with reference to FIG. 1. One or more of the gNBs 255 or ng-eNBs 260 may communicate with one or more UEs 115-a over one or more communication links 125-a (e.g., the Uu interface). The communication link(s) 125-a may be examples of the communication links 125 described with reference to FIG. 1.

[0137] The LMF 265 may communicate with the core network 130-a to provide location functionality (e.g., to participate in one or more positioning procedures) for the UE(s) 115-a. The LMF 265 may be an example of the location server 185 described with reference to FIG. 1. The LMF 265 may be implemented as one or more devices (e.g., one or more servers, such as physically separate servers, one or more instruction sets on a single server, or instruction sets distributed across multiple physical servers, Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO46among other examples). The LMF 265 may support one or more location services for one or more UEs 115-a that may connect to the LMF 265 via the RAN 225, via the core network 130-a, or via another connection (e.g., the Internet). In some examples, the LMF 265 may communicate with a UE 115-a or another device via a C-plane connection (e.g., using one or more interfaces or protocols for signaling control information, or separate from voice or payload data). In some aspects, the LMF 265 may be integrated into a component of the core network 130-a or may be external to the core network 130-a (e.g., on an external device 230, such as an original equipment manufacturer (OEM) server or other server).

[0138] In some examples, the SLP 235 may provide location functionality (e.g., may participate in one or more positioning procedures) for the UE(s) 115-a. The SLP 235 may be an example of the location server 185 described with reference to FIG. 1. The SLP 235 may be implemented as one or more devices (e.g., one or more servers, such as physically separate servers, one or more instruction sets on a single server, or instruction sets distributed across multiple physical servers, among other examples). The SLP 235 may support one or more location services for one or more UEs 115-a that may connect to the SLP 235 via the RAN 225, via the core network 130-a, or via another connection (e.g., the Internet). In some examples, the SLP 235 may communicate with a UE 115-a or another device via a U-plane connection (e.g., using one or more interfaces or protocols for signaling voice or payload data, such as a transmission control protocol (TCP) or IP).

[0139] In some examples, the external device 230 may communicate with the LMF 265, the SLP 235, the core network 130-a (e.g., via the AMF 210 or the UPF 215), the RAN 225, or the UE 115-a to obtain location information (e.g., a location estimate) for the UE 115-a. The external device 230 may be referred to as a location services (LCS) client or an external client. The external device 230 may be implemented as one or more devices (e.g., one or more servers, such as physically separate servers, one or more instruction sets on a single server, or instruction sets distributed across multiple physical servers, among other examples). The external device 230 may support one or more location services for one or more UEs 115-a that may connect to the external device 230 via the RAN 225, via the core network 130-a, or via another connection (e.g., the Internet).Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO47

[0140] In some approaches, the functionality of a gNB 255 may be divided between a CU 160-a, one or more DUs 165-a, or one or more RUs 170-a. The CU 160-a may be an example of the CU 160 described with reference to FIG. 1, the one or more DUs 165-a may be examples of the DU 165 described with reference to FIG. 1, or the one or more RUs 170-a may be examples of the RU 170 described with reference to FIG. 1. In some examples, the CU 160-a may provide one or more functions, such as transferring user data, mobility control, radio access network sharing, positioning, session management, or others, except for one or more functions allocated exclusively to the DU(s) 165-a. A DU 165-a may support one or more cells. The DUs 165-a may communicate with the CU 160-a via midhaul communication links 162-a (e.g., via the Fl interface). The midhaul communication links 162-a may be examples of the midhaul communication links 162 described with reference to FIG.l. The RUs 170-a may perform one or more functions such as power amplification, signal transmission, or signal reception. The RUs 170-a may communicate with the DUs 165-a via fronthaul communication links 168-a (e.g., via the Fx interface). The fronthaul communication links 168-a may be examples of the fronthaul communication links 168 described with reference to FIG.l. The UE 115-a may communicate with the gNB 255, RU 170-a, or ng-eNB 260 a via communication links 125-a. The communication links 125-a may be examples of the communication links 125 described with reference to FIG.l. The UE 115-a may communicate with the CU 160-a via the RRC, SDAP, and PDCP layers, with a DU 165-a via the RLC and MAC layers, or with an RU 170-a via the PHY layer.

[0141] As described herein, when a wireless device (e.g., UE 115-a, gNB 255, ng-eNB 260, RU 170-a, DU 165-a, or CU 160-a, among other examples) communicates (e.g., outputs, transmits, obtains, or receives) signaling or information with a network entity (e.g., LMF 265, external device 230, SLP 235, AMF 210, SMF 220, UPF 215, gNB 255, ng-eNB 260, CU 160-a, DU 165-a, or RU 170-a, among other examples), the communication (e.g., transmission or reception) may be carried out directly (without one or more intervening devices or entities) or indirectly (with one or more intervening devices or entities). For example, if the UE 115-a transmits signaling or information to the LMF 265, the signaling or information may be communicated via (or independently from) one or more of the gNB 255, ng-eNB 260, RU 170-a, DU 165-a, CU 160-a, AMF 210, SMF 220, UPF 215, SLP 235, or external device 230, among other examples.Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO48Additionally, or alternatively, if the LMF 265 transmits signaling or information to the UE 115-a, the signaling or information may be communicated via (or independently from) one or more of the gNB 255, ng-eNB 260, RU 170-a, DU 165-a, CU 160-a, AMF 210, SMF 220, UPF 215, SLP 235, or external device 230, among other examples.

[0142] FIG. 3 shows an example of a network architecture 300 (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that supports processing windows for NTN node-based positioning in accordance with one or more aspects of the present disclosure. The network architecture 300 may illustrate an example for implementing one or more aspects of the wireless communications system 100. The network architecture 300 may include one or more CUs 160-b that may communicate directly with a core network 130-b via a backhaul communication link 120-b, or indirectly with the core network 130-b through one or more disaggregated network nodes 105 (e.g., a Near-RT RIC 175-b via an E2 link, or a Non-RT RIC 175-a associated with an SMO 180-a (e.g., an SMO Framework), or both). A CU 160-b may communicate with one or more DUs 165-b via respective midhaul communication links 162-b (e.g., an Fl interface). The DUs 165-b may communicate with one or more RUs 170-b via respective fronthaul communication links 168-b. The RUs 170-b may be associated with respective coverage areas 110-a and may communicate with UEs 115-b via one or more communication links 125-b. In some implementations, a UE 115-b may be simultaneously served by multiple RUs 170-b.

[0143] Each of the network nodes 105 of the network architecture 300 (e.g., CUs 160-b, DUs 165-b, RUs 170-b, Non-RT RICs 175-a, Near-RT RICs 175-b, SMOs 180-a, Open Clouds (O-Clouds) 305, Open eNBs (O-eNBs) 310) may include one or more interfaces or may be coupled with one or more interfaces configured to receive or transmit signals (e.g., data, information) via a wired or wireless transmission medium. Each network node 105, or an associated processor (e.g., controller) providing instructions to an interface of the network node 105, may be configured to communicate with one or more of the other network nodes 105 via the transmission medium. For example, the network nodes 105 may include a wired interface configured to receive or transmit signals over a wired transmission medium to one or more of the other network nodes 105. Additionally, or alternatively, the network nodes 105 may include a wireless interface, which may include a receiver, a transmitter, or transceiver (e.g., an RFAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO49transceiver) configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other network nodes 105.

[0144] In some examples, a CU 160-b may host one or more higher layer control functions. Such control functions may include RRC, PDCP, SDAP, or the like. Each control function may be implemented with an interface configured to communicate signals with other control functions hosted by the CU 160-b. A CU 160-b may be configured to handle user plane functionality (e.g., CU-UP), control plane functionality (e.g., CU-CP), or a combination thereof. In some examples, a CU 160-b may be logically split into one or more CU-UP units and one or more CU-CP units. A CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface, such as an El interface when implemented in an O-RAN configuration. A CU 160-b may be implemented to communicate with a DU 165-b, as necessary, for network control and signaling.

[0145] A DU 165-b may correspond to a logical unit that includes one or more functions (e.g., base station functions, RAN functions) to control the operation of one or more RUs 170-b. In some examples, a DU 165-b may host, at least partially, one or more of an RLC layer, a MAC layer, and one or more aspects of a PHY layer (e.g., a high PHY layer, such as modules for FEC encoding and decoding, scrambling, modulation and demodulation, or the like) depending, at least in part, on a functional split, such as those defined by the 3rd Generation Partnership Project (3GPP). In some examples, a DU 165-b may further host one or more low PHY layers. Each layer may be implemented with an interface configured to communicate signals with other layers hosted by the DU 165-b, or with control functions hosted by a CU 160-b.

[0146] In some examples, lower-layer functionality may be implemented by one or more RUs 170-b. For example, an RU 170-b, controlled by a DU 165-b, may correspond to a logical node that hosts RF processing functions, or low-PHY layer functions (e.g., performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, or the like), or both, based at least in part on the functional split, such as a lower-layer functional split. In such an architecture, an RU 170-b may be implemented to handle over the air (OTA) communication with one or more UEs 115-b. In some implementations, real-time and non-real-time aspects of control and user plane Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO50communication with the RU(s) 170-b may be controlled by the corresponding DU 165-b. In some examples, such a configuration may enable a DU 165-b and a CU 160-b to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0147] The SMO 180-a may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network nodes 105. For non-virtualized network nodes 105, the SMO 180-a may be configured to support the deployment of dedicated physical resources for RAN coverage requirements which may be managed via an operations and maintenance interface (e.g., an 01 interface). For virtualized network nodes 105, the SMO 180-a may be configured to interact with a cloud computing platform (e.g., an O-Cloud 305) to perform network node life cycle management (e.g., to instantiate virtualized network nodes 105) via a cloud computing platform interface (e.g., an 02 interface). Such virtualized network nodes 105 can include, but are not limited to, CUs 160-b, DUs 165-b, RUs 170-b, and Near-RT RICs 175-b. In some implementations, the SMO 180-a may communicate with components configured in accordance with a 4G RAN (e.g., via an 01 interface). Additionally, or alternatively, in some implementations, the SMO 180-a may communicate directly with one or more RUs 170-b via an 01 interface. The SMO 180-a also may include a Non-RT RIC 175-a configured to support functionality of the SMO 180-a.

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

[0149] In some examples, to generate AI / ML models to be deployed in the Near-RT RIC 175-b, the Non-RT RIC 175-a may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 175-b and may be received at the SMO 180-a or the Non-RT RIC 175-a from nonAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO51network data sources or from network functions. In some examples, the Non-RT RIC 175-a or the Near-RT RIC 175-b may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 175-a may monitor long-term trends and patterns for performance and employ Al or ML models to perform corrective actions through the SMO 180-a (e.g., reconfiguration via 01) or via generation of RAN management policies (e.g., Al policies).

[0150] FIG. 4 shows an example of a wireless communications system 400 that supports processing windows for NTN node-based positioning in accordance with one or more aspects of the present disclosure. The wireless communications system 400 may implement aspects of or may be implemented by aspects of the wireless communications system 100. For example, the wireless communications system 400 includes a wireless device 415. The wireless device 415 may be an example of a UE 115, network node 105, RU 170, DU 165, or CU 160 described with reference to FIG. 1, aUE 115-a, gNB 255, RU 170-a, DU 165-a, CU 160-a, or ng-eNB 260 described with reference to FIG. 2, or a UE 115-b, RU 170-b, DU 165-b, or CU 160-b described with reference to FIG. 3. The wireless communications system 400 also includes a network entity 405, which may be an example of a network node 105, location server 185, RU 170, DU 165, or CU 160 described with reference to FIG. 1, an LMF 265, external device 230, SLP 235, AMF 210, SMF 220, UPF 215, gNB 255, RU 170-a, DU 165-a, CU 160-a, or ng-eNB 260 described with reference to FIG. 2, or an RU 170-b, DU 165-b, or CU 160-b described with reference to FIG. 3. The wireless communications system 400 also includes one or more NTN nodes 445, which may be an example(s) of a network node 105, RU 170, DU 165, or CU 160 described with reference to FIG. 1, a gNB 255, RU 170-a, DU 165-a, CU 160-a, or ng-eNB 260 described with reference to FIG. 2, or an RU 170-b, DU 165-b, or CU 160-b described with reference to FIG. 3. For example, the wireless device 415 may be a UE or a network node, the network entity 405 may include one or more network nodes, network functions, AMFs, LMFs, or servers, or the NTN node 445 may a satellite in an NTN. In some examples, the network entity 405 may include the NTN node 445, or the NTN node 445 may be associated (e.g., collocated) with the network entity 405. In some examples, the network entity 405 and one or more of the NTN nodes 445 may be a same device or may be included in a same device. As used herein, a “network function” or aAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO52“service” may refer to a device (e.g., server, computing device, network node, gNB, AMF, LMF, network entity, base station, wireless device, or UE, among other examples) for performing a function or service.

[0151] In some examples, the NTN node(s) 445 may include one or more HAPSs, high altitude vehicles (HAVs), LEO satellites, MEO satellites, GEO satellites, balloons, or a combination thereof, among other examples. For instance, the NTN node 445 may be in an orbit, such as LEO, MEO, GEO, or other non-geostationary earth orbit. The NTN node 445 may be positioned at some distance from Earth (e.g., hundreds or thousands of kilometers from Earth), which may vary or remain relatively fixed. The NTN node 445 may include communication circuitry (e.g., one or more processors, memories, modems, baseband circuitries, among other examples), one or more antennas, or one or more transponders to facilitate reception and transmission of RF signals. The NTN node 445 may serve a geographic region for an NTN.

[0152] In some examples, the wireless communications system 400 may include one or more other NTN nodes or one or more TN nodes. For instance, the wireless device 415 may communicate with one or more NTN nodes or one or more TN nodes. In some examples, a TN node may be positioned on the Earth’s surface or relatively near to the Earth’s surface (e.g., within a mile or less from the Earth’s surface). In some examples, a TN node may be anchored or attached to the Earth’s surface. A TN node may include communication circuitry (e.g., one or more processors, memories, modems, baseband circuitries, among other examples) or one or more antennas to facilitate reception and transmission of RF signals. In some examples, a TN node may provide communication service within a cell area. In some cases, the cell area may be included within a geographic region served by the NTN node 445, may partially overlap with the geographic region, or may be located outside of the geographic region. In some aspects, the NTN node 445 may instead be a TN node.

[0153] In some examples, network (e.g., RAN) functionality may be split between the NTN node 445 (e.g., a satellite, an RU on a satellite, or a gNB DU of the RAN, among other examples) and a TN node (e.g., a DU located on the ground or gNB CU of the RAN, among other examples). For instance, the NTN node 445 may be a DU 165 (e.g., may implement DU 165 functionality) and the TN node may be a CU (e.g., may implement CU 160 functionality). In some examples, a CU 160 and a DU 165 may Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO53reside on the ground and may be associated with one or more terrestrial or nonterrestrial cells or RUs. In an NTN, one or more DUs 165 may be located on a satellite and a CU 160 may be located on the Earth’s surface. In some examples, the NTN node 445 and a TN node may be included in a RAN (e.g., NG-RAN) portion of the wireless communications system 400. In some examples, the wireless device 415 may be excluded from the RAN (e.g., NG-RAN) portion of the wireless communications system 400.

[0154] The wireless device 415 may communicate with the NTN node 445 using a communication link 450. The communication link 450 between the wireless device 415 and the NTN node 445 may provide one or more of the communications 192 described with reference to FIG. 1.

[0155] In some examples of an NTN, one or more devices (e.g., the network entity 405 or another device in a data network) may communicate in accordance with a scenario based on a transparent payload. In a transparent payload, the NTN node 445 may perform radio frequency filtering, frequency conversion, or amplification.Accordingly, a waveform signal provided to the NTN node 445 may be repeated, where the payload is maintained (e.g., unchanged). For example, a device(s) may communicate with a gateway device, which may communicate a feeder link with the NTN node 445 (e.g., satellite or UAS platform). The NTN node 445 may provide one or more beam footprints in a field of view of the NTN node 445. The wireless device 415 (e.g., UE) may be located in one or more beam footprints to communicate with the NTN node 445 via a communication link 450 (e.g., service link).

[0156] In some examples of an NTN, one or more devices (e.g., the network entity 405 or another device in a data network) may communicate in accordance with a scenario based on a regenerative payload. In a regenerative payload, the NTN node 445 may perform radio frequency filtering, frequency conversion, amplification, demodulation, decoding, switching, routing, coding, or modulation, among other examples. In some examples, a regenerative payload scenario may be similar to having some or all aspects of network node (e.g., base station or gNB, among other examples) functions on-board the NTN node 445 (e.g., satellite or UAS platform). For example, a device(s) may communicate with a gateway device, which may communicate a feeder link with one or more NTN nodes 445 (e.g., satellite or UAS platform). In some Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO54approaches, the gateway device may communicate via a feeder link with a second NTN node 445, which may communicate with the NTN node 445 via an inter-satellite link (ISL), which may relay communications to the wireless device 415. The NTN node 445 may provide one or more beam footprints in a field of view of the NTN node 445. The wireless device 415 (e.g., UE) may be located in one or more beam footprints to communicate with the NTN node 445 via a communication link 450 (e.g., service link).

[0157] The communication link 450 may be a unidirectional link for downlink communications or may include a bi-directional link that enables uplink or downlink communications. For example, the NTN node 445 may transmit one or more downlink signals on a downlink (e.g., downlink channel(s), downlink resource(s)), such as downlink control signals or downlink data signals, to the wireless device 415 using the communication link 450. In some cases, the wireless device 415 may transmit one or more signals on an uplink (e.g., uplink channel(s), uplink resource(s)), such as uplink control signals or uplink data signals, to the NTN node 445 using the communication link 450.

[0158] In some examples, the NTN node(s) 445 may change position relative to the wireless device 415. Additionally, or alternatively, the wireless device 415 may change position relative to the NTN node(s) 445. For instance, relative motion between the NTN node(s) 445 and the wireless device 415 may occur due to an orbit of the NTN node(s) 445, due to movement of the Earth, due to motion of the wireless device 415, or a combination thereof.

[0159] The wireless device 415 may communicate with the network entity 405 using a link 425, which may be an example of a communication link 125, a backhaul communication link 120, or a communication link 155 described with reference to FIG. 1, a communication link 125-a, a backhaul communication link 120-a, a C-plane interface 245, or a U-plane interface 250 described with reference to FIG. 2, a communication link 125-b or a backhaul communication link 120-b described with reference to FIG. 3, another link, or a combination thereof. The link 425 may include one or more uni-directional or bi-directional links that enable uplink or downlink network communications. For example, the wireless device 415 may transmit one or more transmissions 420, such as uplink control signals or uplink data signals, to the network entity 405 using the link 425, or the network entity 405 may transmit one orAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO55more transmissions 420, such as downlink control signals or downlink data signals, to the wireless device 415 using the link 425. In some examples, the link 425 between the wireless device 415 and the network entity 405 may be carried via the NTN node 445, may be independent from the NTN node 445, or may be carried via another network node (e.g., a TN node).

[0160] The wireless device 415 may obtain (e.g., receive) configuration information 430 indicating a PPW identifier of a PPW and a periodicity of the PPW. The configuration information 430 may indicate multiple window lengths within the periodicity of the PPW, and the PPW identifier may be associated with the multiple window lengths. For instance, some of the techniques described herein may utilize a new PPW pattern for signaling from one or NTN nodes (e.g., NTN node(s) 445). A new PPW identifier may be associated with the new PPW pattern. In the PPW pattern, for example, processing window length sets per PPW configuration identifier may be utilized, or configurations may be repeated with a measurement gap periodicity.Providing multiple window lengths per PPW identifier may allow PRSs from multiple NTN nodes (e.g., NTN node(s) 445) to be measured in association with the same PPW identifier. In some examples, the configuration information may be communicated via RRC signaling.

[0161] The NTN node(s) 445 may output (e.g., transmit), or the wireless device 415 may obtain (e.g., receive), one or more PRSs 435 in one or more of the multiple window lengths. The wireless device 415 may obtain measurement information based on the PRS 435 within a respective window length of the multiple window lengths. For instance, the wireless device 415 may measure the PRS 435 for each of the NTN node(s) 445 to obtain (e.g., generate or produce) the measurement information. In some examples, the wireless device 415 may output (e.g., transmit), or the network entity 405 may obtain (e.g., receive), the measurement information, where the measurement information may be based on the PRS 435 within a respective window length of the multiple window lengths.

[0162] In some approaches, the configuration information 430 may indicate a first window length associated with the PPW identifier that is different from a second window length associated with the PPW identifier. For a PPW identifier, for instance, multiple processing widows with different lengths may be utilized.Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO56

[0163] In some aspects, the configuration information 430 may indicate at least one gap between a pair of the multiple window lengths associated with the PPW identifier. In some examples, the configuration information 430 may indicate different gaps between different pairs of the multiple window lengths associated with the PPW identifier. For a PPW identifier, for instance, different time periods (e.g., “gaps” or “measurement gaps”) between processing windows associated with a PPW identifier may be utilized. Examples of different window lengths and different time periods are given with reference to FIG. 6.

[0164] In some examples, a network device (e.g., the network entity 405 or the NTN node 445) may output (e.g., transmit), or the wireless device 415 may obtain (e.g., receive) control information indicating activation or deactivation of the PPW based on the PPW identifier of the PPW. The activation or deactivation of the PPW may correspond to the multiple window lengths associated with the PPW identifier. For instance, a PPW identifier (e.g., a single PPW identifier) may be indicated in the control information in association with information (e.g., a bit) to indicate activation or deactivation of multiple window lengths associated with the PPW identifier.

[0165] In some approaches, the activation or deactivation of the PPW may indicate activation or deactivation of the PPW that corresponds to the multiple window lengths on a BWP or a positioning frequency layer (PFL). Some examples of the techniques described herein, may provide a framework for activating or deactivated multiple windows associated with a PPW identifier on a serving BWP, on a serving PFL, on any BWP, or on any PFL.

[0166] In some examples, the control information indicating activation or deactivation of the PPW based on the PPW identifier may be communicated via a MAC CE (e.g., a positioning measurement gap activation or deactivation request or command MAC CE). In some approaches, the MAC CE may include a numEntry field, a serving cell identifier field, a PPW identifier field, and an activation or deactivation indicator field. The numEntry field may indicate a quantity of entries N-l in the MAC CE. For instance, 00 may indicate that N is equal to 2, 01 may indicate that N is equal to 3, and so on. The length of the numEntry field may be two bits. The serving cell identifier field may indicate an identity of a serving cell for which the MAC CE applies. The length of the serving cell identifier field may be five bits (for an entry of the MAC CE). The PPW Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO57identifier field may indicate an index of the PPW configured on an active downlink BWP of the serving cell identified by the serving cell identifier. Index 0 may correspond to a first entry in a list of PPW configurations by an increasing order of PPW identifiers (e.g., downlink PPW identifiers) in a BWP, index 1 may corresponds to a second entry in the list, and so on. The length of the field may be two bits. The activation or deactivation field may indicate an activation or deactivation of the PPW. The activation or deactivation field may be set to 1 to indicate activation (e.g., otherwise the field may indicate deactivation). The length of the field may be one bit. One or more reserved bits may be set to 0. For instance, a MAC CE may include an octet of bits (e.g., octet 1), where six bits are reserved and two bits are utilized to indicate the numEntry field. One or more other octets (e.g., octets 2-N, each corresponding to an entry of the MAC CE) may each include five bits to indicate the serving cell identifier, two bits for the PPW identifier, and one bit for the activation or deactivation indicator. In accordance with some of the techniques described herein, the PPW identifier (in one octet, for instance) may be associated with multiple window lengths (e.g., for measurement of PRSs from multiple NTN nodes 445 with different delays). In some approaches, the MAC CE (e.g., a PPW activation or deactivation request or command MAC CE) may be identified by a MAC subheader with an extended logical channel identifier (eLCID). The MAC CE may have a variable size.

[0167] In some approaches, the wireless device 415 may output (e.g., transmit), or the network entity 405 may obtain (e.g., receive) transmitting capability information indicating a quantity of PPW identifiers for concurrent activation supported by the wireless device 415. The control information may be communicated (e.g., output or transmitted from the network device or obtained or received by the wireless device 415) based on the capability information. For instance, the capability information (e.g., UE capability) may indicate a quantity (e.g., maximum quantity) of PPW identifiers (e.g., PPW identifiers that correspond to multiple window lengths) that may be concurrently active or activated concurrently.

[0168] In some aspects, a set of PPW identifiers may include a first subset of PPW identifiers corresponding to PPWs for NTN positioning and a second subset of PPW identifiers corresponding to PPWs for TN positioning. The PPW identifier may be included in the first subset of PPW identifiers for NTN positioning. In some approaches,Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO58one or more identifiers may be utilized between NTN and TN PPW configurations. For instance, a PPW identifier may be utilized for an NTN identifier or for a TN identifier. The wireless device 415 (e.g., UE) may determine (or receive an indication that) a PPW identifier corresponds to a TN use case. Additionally, or alternatively, the wireless device 415 (e.g., UE) may determine (or receive an indication that) a PPW identifier corresponds an NTN use case. For instance, one or more PPW identifiers may be specified as corresponding to a TN use case, to an NTN use case, or to a combination thereof.

[0169] In some examples, a relatively longer PPW window length may be utilized forNTN-based positioning. The propagation delay difference on measurements (e.g., due to different NTN nodes 445) may have a significant impact on NTN-based positioning procedures. In some cases, a relatively small measurement gap length (e.g., 160 slots or less) may limit the ability of the wireless device 415 to decode positioning resources (e.g., PRS resources) from different NTN nodes 445 (e.g., satellites). In accordance with some of the techniques described herein, one or more relatively larger PPW window lengths may be utilized for NTN-based positioning. In some examples, the configuration information 430 may indicate that at least one of the multiple window lengths is greater than 160 slots (e.g., 320 slots, 640 slots, or 2560 slots, among other examples).

[0170] In some approaches, the wireless device 415 or the network entity 405 may communicate (e.g., output, transmit, obtain, or receive) a request for the configuration information 430 indicating the PPW identifier for NTN positioning. The configuration information 430 may be communicated (e.g., output, transmitted, obtained, or received) based on the request. For instance, the wireless device 415 may output (e.g., transmit), or the network entity may obtain (e.g., receive), an on-demand NTN PPW configuration request (e.g., an on-demand request for an NTN PPW configuration identifier).

[0171] In some examples, the wireless device 415 or the network entity 405 may communicate (e.g., output, transmit, obtain, or receive), an indication of a set of PPW identifiers (e.g., a set of configured PPW identifiers). The request for the configuration information 430 may be communicated based on the set of PPW identifiers. For instance, the wireless device 415 (e.g., UE) may request an on-demand PPW based on configured PPW identifiers.Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO59

[0172] In some examples, the wireless device 415 or the network entity 405 may communicate (e.g., output, transmit, obtain, or receive) an indication of at least one parameter. For instance, the wireless device 415 (e.g., UE) may be able to request an on-demand PPW-based configured PPW identifier parameter. In some examples, the at least one parameter may include a downlink PPW identifier parameter (e.g., dl-PPW-ID-rl7 DL-PPW-ID-rl7), a downlink periodicity and start slot parameter (e.g., dl-PPW-PeriodicityAndStartSlot-rl7 DL-PPW-PeriodicityAndStartSlot-rl7), a length parameter (e.g., Iength-rl7 INTEGER (1..160)), a type parameter (e.g., type-rl7 ENUMERATED {typel A, typelB, type2} OPTIONAL, — Cond MultiType), a priority parameter (e.g., priority-rl7 ENUMERATED {stl, st2, st3 } OPTIONAL — Cond MultiState), or a combination thereof. The request for the configuration information 430 may be based on the at least one parameter.

[0173] As described herein, a distance between the wireless device 415 (e.g., UE) and the one or more NTNs 445 (e.g., satellite(s)) may vary or change over time. A timevarying timing advance (TA) may be utilized to address the varying distance for an NTN. In an NTN, for example, the network may indicate one or more parameters, such as a TA parameter (e.g., TA(t) or TACommon(t)), a TA drift rate parameter (e.g., TADrift(t) or TACommonDrift(t)), or a TA drift rate variation (e.g., TADriftVariation(t) or TACommonDriftVariation(t)). One or more of the parameters may be signaled (from the NTN node 445 or the network entity 405 to the wireless device 415, for instance). Using the indicated higher-layer TA parameter(s), if configured, the wireless device 415 (e.g., UE) may determine a one-way propagation time (e.g., Delay or Delaycommon), which may be utilized to calculate another parameter (e.g., NTA, or NTA , common ) parameter in accordance with Equation (1).>Equation (1)In Equation (1), t is a time (e.g., current time), Epoch is an epoch time corresponding to one or more of the NTN node(s) 445, TA(t), TADrift(t), and TADriftVariation(t) may be TA parameters indicated by a network device (e.g., the NTN node 445 or the network entity 405). Delay(t) may be a distance between the NTN node 445 (e.g., satellite) and an uplink time synchronization reference point divided by the speed ofAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO60light. NTA may be determined by the wireless device 415 (e.g., UE) based on Delay(t) to compensate (e.g., pre-compensate) for a two-way transmission delay between the uplink time reference point and the NTN node 445 (e.g., satellite).

[0174] In some examples, the network entity 405 (e.g., a gNB or LMF) may establish (e.g., set or define) a time varying PPW for one or more NTN use cases. The network entity 405 (e.g., gNB or LMF) may configure one or more parameters (e.g., may signal a configuration of one or more parameters) for the wireless device 415 (e.g., UE) to obtain (e.g., determine or calculate) a time-varying PPW offset (e.g., slot offset or start offset). In some examples, the network entity 405 may output (e.g., transmit), or the wireless device 415 may obtain (e.g., receive) an indication of a PPW parameter (e.g., PPW(t) or PPWcommon(t)), a PPW drift parameter (e.g., PPWDrift(t) or PPWCommonDrift(t)), or a PPW drift variation parameter (e.g., PPWDriftVariation(t) or PPWCommonDriftVariation(t)). For instance, PPW(t), PPWDrift(t), or PPWDriftVariation(t) (e.g., PPWcommon(t), PPWCommonDrift(t), or PPWCommonDriftVariation(t)) may be parameters (e.g., parameters in common) associated with a PPW identifier, which may be indicated by a network device (e.g., the NTN node 445 or the network entity 405). The PPW parameter, the PPW drift parameter, or the PPW drift variation parameter may be utilized (by the wireless device 415, for example) to determine a time-varying start parameter (e.g., PPWstart(t)) or a time-varying duration parameter (e.g., PPWDuration(t)). PPWStart(t) may be a timevarying PPW start offset. A start time of the PPW may be based on the time-varying start parameter or a duration of the PPW may be based on the time-varying duration parameter. Additionally, or alternatively, a start time of at least one of the multiple window lengths may be based on the time-varying start parameter or a duration of at least one of the multiple window lengths may be based on the time-varying duration parameter. In some examples, the time-varying start parameter (e.g., PPWstart(t)) may be determined in accordance with Equation (2).Equation (2)In Equation (2), t is a time (e.g., current time), and tepoch is an epoch time corresponding to one or more of the NTN node(s) 445. As used herein, the term “common” may meanAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO61“shared” (e.g., shared between devices) in some contexts. For instance, one or more calculations described herein may be performed with variables or factors relating to one or more devices.

[0175] In some approaches, a network entity 405 (e.g., LMF) may provide assistance data to the wireless device 415 for one or more positioning procedures. In some examples, the assistance data may be modified for one or more NTN use cases. If the one or more NTN nodes 445 (e.g., satellite(s)) have a footprint where the wireless device 415 (e.g., UE) is operating, signals received from the NTN nodes 445 (e.g., satellites) may be received with similar signal strengths. For TN or Uu link or interface use cases, for example, the network entity 405 (e.g., LMF) may prioritize a PRS based on a distance between a network node (e.g., gNB) and the wireless device 415, or based on a signal strength for signaling to the wireless device 415. The wireless device 415 (e.g., UE) may prioritize measurement of any network node (e.g., gNB) in a group. For an NTN use case, because signals from the NTN nodes 445 may be received at similar levels, the network entity 405 (e.g., LMF) may group the NTN nodes 445 (e.g., satellites) based on an expected RSTD with respect to a serving cell. The network entity 405 (e.g., LMF) may indicate a priority among each group. For instance, one or more NTN nodes 445 or PRSs 435 may be prioritized based on a PPW configuration(s).

[0176] In some examples of the techniques described herein, a wireless device 415 (e.g., UE) may operate in accordance with a search priority for NTN positioning resources (e.g., PRS resources). In TNs, a wireless device 415 may determine that the wireless device 415 is located near a cell edge due to a significant difference in RSRP relative to a cell center. This effect may not be as pronounced in non-terrestrial deployments, which may result in a relatively small difference in signal strength between two beams from NTN nodes 445 in an overlapping region. In some examples, the network entity 405 (e.g., LMF) may utilize or provide a rule for measuring PRS resources for NTN cases. In some aspects, the wireless device 415 (e.g., UE) may be configured with multiple PPWs, where one PPW may be utilized to measure PRSs from multiple NTN nodes 445 (e.g., satellites).

[0177] In some examples, the configuration information 430 may indicate a priority for PRSs. Receiving the PRS 435 from the at least one NTN node 445 may beAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO62performed based on the priority. For instance, the network entity 405 (e.g., LMF) may provide a PRS search priority based on the configured PPW.

[0178] In some approaches, the configuration information 430 may indicate a priority for PRSs. Obtaining the measurement information based on the PRS 435 may be performed based on the priority (e.g., in the order of the priority). For instance, the wireless device 415 (e.g., UE) may measure the PRS(s) 435 from the NTN node(s) 445 based on the configured PPW identifier. Additionally, or alternatively, the wireless device 415 may output (e.g., transmit), or the network entity 405 may obtain (e.g., receive) the measurement information based on the priority (e.g., in the order of the priority).

[0179] In some aspects, the configuration information 430 may indicate a priority among the multiple window lengths. Obtaining the measurement information based on the PRS 435 may be performed based on the priority (e.g., in the order of the priority). For instance, the wireless device 415 (e.g., UE) may measure the PRS(s) 435 from the NTN node(s) 445 based on an explicit or implicit priority that exists within disjoint intervals of a single PPW. In an explicit approach, for example, the network entity 405 may output (e.g., transmit), or the wireless device 415 may obtain (e.g., receive) a configuration that explicitly indicates a priority (e.g., indicates that a priority of a first interval is greater than a priority of a second interval, which is greater than a priority of a third interval). In some examples, the network entity 405 (e.g., gNB or LMF) may provide the priority order of different PPWs or different window lengths (e.g., intervals) within a single configured PPW.

[0180] In an implicit approach, for example, a first interval (e.g., the wireless device 415 or UE may determine that the first intervale) may be more likely to have a relatively larger quantity of PRSs inside compared to a second interval, and therefore the wireless device 415 may prioritize the reception of PRSs or the reporting of measurement information of the first interval over the second interval. In some examples, the wireless device 415 may output (e.g., transmit), or the network entity 405 may obtain (e.g., receive) the measurement information based on the priority (e.g., in the order of the priority).Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO63

[0181] In some examples, obtaining the measurement information based on the PRS 435 may be performed based on a priority among the multiple window lengths that is based on an order of the multiple window lengths. For instance, an order of the multiple window lengths may indicate or determine a priority order (e.g., an earlier window length may have a higher priority than a later window length).

[0182] Listing (3) may provide an example of PPW IES, parameters, or fields that includes additional information relative to Listing (1).maxNrofPPW-Config-rl7 INTEGER ::= 4 — Maximum quantity of Preconfigured PRS processing windows per downlink bandwidth part (DL BWP)maxNrofPPW-ID-l-rl7 INTEGER ::= 15 — Maximum quantity of Preconfigured PRS processing windows minus 1DL-PPW-PreConfigToAddModList-rl7 ::= SEQUENCE (SIZE (L.maxNrofPPW-Config-rl7)) OF DL-PPW-PreConfig-rl7DL-PPW-PreConfigToReleaseList-rl7 ::= SEQUENCE (SIZE (L.maxNrofPPW-Config-rl7)) OF DL-PPW-ID-rl7DL-PPW-PreConfig-rl7 ::= SEQUENCE {dl-PPW-ID-rl7 DL-PPW-ID-rl7,dl-PPW-PeriodicityAndStartSlot-rl7 DL-PPW-PeriodicityAndStartSlot-rl7,length-rl7 INTEGER (1..160),type-rl7 ENUMERATED {typelA, typelB, type2} OPTIONAL, — Cond MultiTypepriority-r!7 ENUMERATED {stl, st2, st3 } OPTIONAL — Cond Multi StateAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO64}DL-PPW-PreConfig-rl9 ::= SEQUENCE {dl-PPW-ID-rl9 DL-PPW-ID-rl9,dl-PPW-PeriodicityAndStartSlot-rl7 DL-PPW-PeriodicityAndStartSlot-rl7,length-rl7 sequence of {INTEGER (1..160)},gapBetweenConsecutivelntervals sequence of {INTEGER (1..160)}type-rl9 ENUMERATED {typelA, typelB, type2{ OPTIONAL, — Cond MultiTypepriority-rl9 ENUMERATED {stl, st2, st3 } OPTIONAL — Cond Multi State }DL-PPW-ID-rl7 ::= INTEGER (0..maxNrofPPW-ID-l-rl7)Listing (3)Listing (3) illustrates examples of a downlink PPW identifier parameter (e.g., dl-PPW-ID-rl9 DL-PPW-ID-rl9), a downlink periodicity and start slot parameter (e.g., dl-PPW-PeriodicityAndStartSlot-rl7 DL-PPW-PeriodicityAndStartSlot-rl7), a length parameter (e.g., Iength-rl7 INTEGER (1..160)), a gap or interval parameter (e.g., gapBetweenConsecutivelntervals sequence of {INTEGER (1..160)), a type parameter (e.g., type-rl9 ENUMERATED {typelA, typelB, type2{ OPTIONAL, — Cond MultiType), or a priority parameter (e.g., priority-rl9 ENUMERATED {stl, st2, st3 } OPTIONAL — Cond MultiState) that may be utilized in accordance with some of the techniques described herein.

[0183] Examples of one or more positioning procedures that may be performed based on the measurement s) of the PRS(s) 435 are provided with reference to FIG. 21. For instance, the wireless device 415, the network entity 405, or the NTN node(s) 445 may participate in a positioning procedure. In some approaches, the wireless device 415Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO65may determine a position based on the measurement s) of the PRS(s) 435 or may report information indicating the position to the network entity 405. In some approaches, the network entity 405 may utilize the measurement information (which may indicate the one or more measurement(s) of the PRS(s)) to determine a position or may report information indicating the position to the wireless device 415.

[0184] In some examples of the techniques described herein, one or more signals, indications, or information (e.g., configuration information or capability information, among other examples) described herein may be communicated (e.g., transmitted or received) as part of a protocol or signaling procedure. For instance, the wireless device 415 (e.g., UE) or the network entity 405 (e.g., LMF or other network entity(ies)) may communicate in accordance with an LTE positioning protocol (LPP), in accordance with an NR positioning protocol A (NRPPA), via LPP signaling, or via NRPPA signaling.

[0185] In some approaches, the wireless device 415 or the network entity 405 may participate in a capability exchange that may include one or more signals or messages communicated between the wireless device 415 and the network entity 405. The capability exchange may be performed via an NTN (e.g., via the NTN node 445 or another NTN node), via a TN (e.g., via one or more TN nodes), or via a combination thereof. Additionally, or alternatively, the capability exchange may be based on, or may be performed in accordance with, a protocol (e.g., LPP, NRPPA, via LPP signaling, or via NRPPA signaling, among other examples). In some aspects, a capability exchange may include request signaling (e.g., a request message(s) indicating a request from the network entity 405 for capability information of the wireless device 415) or capability information signaling (e.g., message(s) indicating capability information or one or more capabilities of the wireless device 415). The capability information may be communicated based on a request (e.g., in response to a request from the network entity 405), independent of a request, or without a request.

[0186] Some examples of capability information that may be communicated (e.g., in accordance with LPP, NRPPA, via LPP signaling, or via NRPPA signaling, among other examples) may include capability information indicating whether the wireless device 415 supports NTN communication, whether the wireless device 415 supports multiple window lengths, or a quantity of window lengths supported by the wireless Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO66device 415, among other examples. In some aspects, the capability information may indicate whether the wireless device 415 supports communication with one or more types of NTN (e.g., GEO satellite network(s), MEO satellite network(s), LEO satellite network(s), HEO satellite network(s), UAS platform(s), hybrid NTN network(s), or other NTN types). Additionally, or alternatively, the capability information may indicate one or more communication distances supported by the wireless device 415 (e.g., a quantity of kilometers for NTN communication or one or more distance categories, such as altitude ranges for LEO satellite(s), MEO satellite(s), GEO satellite(s), HEO satellite(s), or UAS platform(s), among other examples).

[0187] One or more other types of capability information may be communicated (e.g., transmitted or received by the wireless device 415, the network entity 405, the NTN node 445, or a TN node) in accordance with a protocol (e.g., LPP or NRPPA) or capability exchange. For instance, capability information may indicate a quantity of PPW identifiers for concurrent activation supported by the wireless device 415, one or more periodicities of a PPW supported by the wireless device 415, whether multiple window lengths are supported by the wireless device 415, a quantity of window lengths supported by the wireless device 415, whether one or more gaps between window lengths are supported by the wireless device 415, or one or more other capabilities supported by the wireless device 415.

[0188] In some approaches, one or more network entities 405 may communicate or store capability information associated with the wireless device 415 (or one or more other wireless devices). For instance, the wireless device 415 may output (e.g., transmit) capability information to an LMF. The LMF may store the capability information or may communicate the capability information to an AMF (or other entity) for storage. A network entity 405 (e.g., LMF, AMF, other network entity, or a combination thereof) may access the stored capability information associated with the wireless device 415, which may reduce repeated capability exchanges or signaling of the capability information between the wireless device 415 and the network entity 405. For instance, a network entity 405 may store or access capability information associated with the wireless device 415 that may indicate a quantity of PPW identifiers for concurrent activation supported by the wireless device 415, one or more periodicities of a PPW supported by the wireless device 415, whether multiple window lengths are supportedAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO67by the wireless device 415, a quantity of window lengths supported by the wireless device 415, whether one or more gaps between window lengths are supported by the wireless device 415, or one or more other capabilities supported by the wireless device 415.

[0189] In some approaches, the network entity 405 or the wireless device 415 may communicate (e.g., transmit or receive) configuration information (e.g., configuration information 430 or other configuration information) via an NTN (e.g., via the NTN node 445 or another NTN node), via a TN (e.g., via one or more TN nodes), or via a combination thereof. Additionally, or alternatively, the communication of configuration information may be based on, or may be performed in accordance with, a protocol (e.g., LPP, NRPPA, via LPP signaling, or via NRPPA signaling, among other examples). In some aspects, communicating the configuration information may be performed as part of a capability exchange or separate from a capability exchange. In some approaches, configuration information may be communicated based on request signaling (e.g., a request message(s) indicating a request from the wireless device 415 for configuration information of the network entity 405). The configuration information may be communicated based on a request (e.g., in response to a request from the wireless device 415), independent of a request, or without a request.

[0190] Some examples of configuration information that may be communicated (e.g., in accordance with LPP, NRPPA, via LPP signaling, or via NRPPA signaling, among other examples) may include configuration information indicating a configuration of the wireless device 415 to participate in NTN communication, a configuration of the wireless device 415 to utilize multiple window lengths, or a configuration of a quantity of window lengths to be utilized by the wireless device 415, among other examples. In some aspects, the configuration information may indicate a configuration of the wireless device 415 to perform communication with one or more types of NTN (e.g., GEO satellite network(s), MEO satellite network(s), LEO satellite network(s), HEO satellite network(s), UAS platform(s), hybrid NTN network(s), or other NTN types). Additionally, or alternatively, the configuration information may indicate a configuration of one or more communication distances for communication by the wireless device 415 (e.g., a quantity of kilometers for NTN communication or one or more distance categories, such as altitude ranges for LEO satellite(s), MEOAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO68satellite(s), GEO satellite(s), HEO satellite(s), or UAS platform(s), among other examples).

[0191] One or more other types of configuration information may be communicated (e.g., transmitted or received by the wireless device 415, the network entity 405, the NTN node 445, or a TN node) in accordance with a protocol (e.g., LPP or NRPPA) or capability exchange. For instance, configuration information may indicate one or more PPW identifiers, one or more periodicities of a PPW, one or more window lengths, PRS resources for receiving one or more PRSs, one or more gaps between window lengths, activation or deactivation of a PPW, a BWP or PFL for activation or deactivation of a PPW, or other information described herein.

[0192] In some approaches, one or more network entities 405 may determine or communicate configuration information based on (e.g., in accordance with) the capability information. For instance, a network entity 405 (e.g., LMF) may configure the wireless device 415 to perform PRS measurement in accordance with one or more of the capabilities of the wireless device 415.

[0193] FIG. 5 shows an example of a wireless communications system 500 that supports processing windows for NTN node-based positioning in accordance with one or more aspects of the present disclosure. The wireless communications system 500 may implement aspects of or may be implemented by aspects of the wireless communications system 100 or the wireless communications system 400. For example, the wireless communications system 500 includes a wireless device 415-a. The wireless device 415-a may be an example of the wireless device 415 described with reference to FIG. 4. The wireless communications system 500 also includes a network entity 405-a, which may be an example of the network entity 405 described with reference to FIG. 4. The wireless communications system 500 also includes a first NTN node 445-a and a second NTN node 445-b, one or more of which may be an example of the NTN node 445 described with reference to FIG. 4. The wireless device 415-a, the network entity 405-a, the NTN node 445-a, or the NTN node 445-b may perform one or more of the operations described with reference to FIG. 4.Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO69

[0194] In some approaches, the wireless communications system 500 may include one or more other NTN nodes or one or more TN nodes. For instance, the wireless device 415-a may communicate with one or more NTN nodes or one or more TN nodes.

[0195] The wireless device 415-a may communicate with the NTN node 445-a using a communication link 545. The communication link 545 between the wireless device 415-a and the NTN node 445-a may provide one or more of the communications 192 described with respect to FIG. 1 or one or more of the communications described with reference to FIG. 4. The wireless device 415-a may communicate with the NTN node 445-b using a communication link 550. The communication link 550 between the wireless device 415-a and the NTN node 445-b may provide one or more of the communications 192 described with respect to FIG. 1 or one or more of the communications described with reference to FIG. 4.

[0196] The wireless device 415-a may communicate with the network entity 405-a using a link 425-a, which may be an example of the communication link 425 described with reference to FIG. 4. The link 425-a may include one or more uni-directional or bidirectional links that enable uplink or downlink network communications. For example, the wireless device 415-a may transmit one or more transmissions, such as uplink control signals or uplink data signals, to the network entity 405-a using the link 425-a, or the network entity 405-a may transmit one or more transmissions, such as downlink control signals or downlink data signals, to the wireless device 415-a using the link 425-a. In some examples, the link 425-a between the wireless device 415-a and the network entity 405-a may be carried via the NTN node 445-a or the NTN node 445-b, may be independent from the NTN node 445 or the NTN node 445-b, or may be carried via another network node (e.g., a TN node).

[0197] In some examples, the NTN node 445-a may be located at a first location 560-a. Additionally, or alternatively, the NTN node 445-b may be located at a second location 560-b. For instance, the second location 560-b may be at a different altitude or coordinates(s) relative to the first location 560-a. In some examples, the NTN node 445-a may transmit a first PRS 535-a and the NTN node 445-b may transmit a second PRS 535-b, where the first PRS 535-a and the second PRS 535-b are transmitted at approximately the same time or within a relatively small period of time. Due to theAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO70difference in location or propagation delay, the first PRS-a and the second PRS 535-b may arrive at different times, at the wireless device 415-a.

[0198] In accordance with some examples of the techniques described herein, the wireless device 415-a may be configured with a PPW identifier that includes multiple window lengths. For instance, the first PRS 535-a may be received during a first window length and the second PRS 535-b may be received during a second window length. While the first PRS 535-a and the second PRS 535-b are associated with different NTN nodes, the first measurement window and the second measurement window may be configured, activated, or utilized in association with a single PPW identifier, which may reduce overhead configuration or activation signaling for a positioning procedure. In some approaches, a first measurement of the first PRS 535-a and a second measurement of a second PRS 535-b may be indicated in measurement information 555 in association with a single PPW identifier, which may reduce overhead reporting signaling. For instance, the wireless device 415-a may output (e.g., transmit), or the network entity 405-a may obtain (e.g., receive) the measurement information 555. The wireless device 415-a, the network entity 405-a, the NTN node 445-a, or the NTN node 445-b may participate in a positioning procedure based on the measurements of the first PRS 535-a and the second PRS 535-b.

[0199] FIG. 6 shows examples of timing diagrams 600 that support processing windows for NTN node-based positioning in accordance with one or more aspects of the present disclosure. One or more of the NTN node(s) 445, wireless device 415, network entity 405, NTN node 445-a, NTN node 445-b, wireless device 415-a, or network entity 405-a described with reference to FIG. 4 or FIG. 5 may operate in accordance with a first scenario 635-a or a second scenario 635-b described with reference to FIG. 6.

[0200] In the first scenario 635-a, a network entity may provide configuration information to a wireless device to configure the wireless device for monitoring, receiving, or measuring PRSs to be signaled within a periodicity 620-a. In some examples, the periodicity 620-a may be indicated or configured as a dl-PPW-PeriodicityAndStartSlot-rl7 or a similar parameter(s). One occasion of the periodicity 620-a may include a first window (e.g., first processing window) with a first length 605-a and a second window (e.g., second processing window) with a second length Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO71610-a that are associated with a PPW identifier (e.g., a single PPW identifier). A first gap 615-a (e.g., an interval, duration, or timing distance) between the first length 605-a and the second length 610-b may be configured as a quantity of slots. As illustrated in the first scenario 635-a, the first length 605-a may be different from the second length 610-a. In some examples, a first PRS may be received or measured in the first length 605-a and a second PRS may be received or measured in the second length 610-a. Measurements corresponding to the first PRS and the second PRS may be reported from the wireless device to a network entity as measurement information in association with a same PPW identifier.

[0201] In the second scenario 635-b, a network entity may provide configuration information to a wireless device to configure the wireless device for monitoring, receiving, or measuring PRSs to be signaled within a periodicity 620-b. In some examples, the periodicity 620-b may be indicated or configured as a dl-PPW-PeriodicityAndStartSlot-rl7 or a similar parameter(s). One occasion of the periodicity 620-b may include a first window (e.g., first processing window) with a first length 605-b, a second window (e.g., second processing window) with a second length 610-b, and a third window (e.g., third processing window) with a third length 625-b that are associated with a PPW identifier (e.g., a single PPW identifier). A first gap 615-b (e.g., an interval, duration, or timing distance) between the first length 605-b and the second length 610-b may be configured as a quantity of slots. A second gap 630-b (e.g., an interval, duration, or timing distance) between the second length 610-b and the third length 625-b may be configured as a quantity of slots. As illustrated in the second scenario 635-b, the first length 605-b, the second length 610-b, or the third length 625-b may be different from each other (e.g., may differ in a quantity of slots or time). In some examples, a first PRS may be received or measured in the first length 605-b, a second PRS may be received or measured in the second length 610-b, and a third PRS may be received or measured in the third length 625-b. Measurements corresponding to the first PRS, the second PRS, and third PRS may be reported from the wireless device to a network entity as measurement information in association with a same PPW identifier.

[0202] FIG. 7 shows an example of a process flow 700 that supports processing windows for NTN node-based positioning in accordance with one or more aspects ofAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO72the present disclosure. The process flow 700 may include a wireless device 415-b, which may be an example of the wireless device 415 described with reference to FIG. 4. The process flow 700 may also include an NTN node 445-b, which may be an example of the NTN node 445 described with reference to FIG. 4. The process flow 700 may additionally include a network entity 405-b, which may be an example of the network entity 405 described with reference to FIG. 4.

[0203] In the following description of the process flow 700, the communications between the wireless device 415-b, the NTN node 445-b, or the network entity 405-b may be transmitted in the example order shown, or in a different order than the example order shown, or the operations performed by the wireless device 415-b, the NTN node 445-b, or the network entity 405-b may be performed in different orders or at different times. One or more operations may be omitted from the process flow 700, or one or more other operations may be added to the process flow 700. Although some operations or signaling may be shown to occur at different times for discussion purposes, these operations may actually occur at the same time or in overlapping time periods in some examples.

[0204] In some examples, the wireless device 415-b and the network entity 405-b may communicate information via the NTN node 445-b, the wireless device 415-b and the network entity 405-b may communicate information independent of the NTN node 445-b, or a combination thereof. In some examples, the wireless device 415-b, the NTN node 445-b, or the network entity 405-b may communicate information, where the information may be relayed transparently via the NTN node 445-b, may be processed by the NTN node 445-b before communication to the wireless device 415-b or the network entity 405-b, or may not be transmitted to the wireless device 415-b or the network entity 405-b. In some approaches, one or more other devices (e.g., NTN node(s), TN node(s), gateway(s), or other device(s)) may be utilized for communications among the wireless device 415-b, the network entity 405-b, or the NTN node 445-b.

[0205] At 705, the wireless device 415-b may output (e.g., transmit), or the network entity 405-b may obtain (e.g., receive), capability information. For instance, capability information may be communicated as described with reference to FIG. 4.Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO73

[0206] At 710, the network entity 405-b may output (e.g., transmit), or the wireless device 415-b wireless device 415-b may obtain (e.g., receive), configuration information. For instance, the configuration information may be communicated as described with reference to FIG. 4. In some examples, the configuration information may configure the wireless device 415-b with multiple window lengths within a PPW periodicity, where the multiple window lengths may be associated with a PPW identifier.

[0207] At 715, the network entity 405-b may output (e.g., transmit), or the wireless device 415-b wireless device 415-b may obtain (e.g., receive), control information. For instance, the control information may be communicated as described with reference to FIG. 4. In some examples, the control information may indicate an activation of multiple window lengths associated with a PPW identifier.

[0208] At 720, the NTN node 445-b may output (e.g., transmit), or the wireless device 415-b may obtain (e.g., receive) one or more signals. In some examples, the signal(s) may be communicated as described with reference to FIG. 4. For instance, the wireless device 415-b may receive one or more PRSs from the NTN node 445-b. The wireless device 415-b may measure the PRS(s) to obtain one or more measurements.

[0209] At 725, the wireless device 415-b may output (e.g., transmit), or the network entity 405-b may obtain (e.g., receive), a report. In some examples, the report may be communicated as described with reference to FIG. 4. For instance, the report may include measurement information indicating one or more PRS measurements corresponding to the PPW identifier. In some examples, the wireless device 415-b may obtain (e.g., receive) signals from one or more other NTN nodes or TN nodes, where the report may include one or more indications of measurements from the signal(s) from the other NTN node(s) or TN node(s). In some examples, the network entity 405-b may utilize the measurements to determine (e.g., calculate) a position of the wireless device 415-b. In some aspects, the network entity 405-b may output (e.g., transmit), or the wireless device 415-b may obtain (e.g., receive) an indication of the position determined by the network entity 405-b.

[0210] FIG. 8 shows an example of a process flow 800 that supports processing windows for NTN node-based positioning in accordance with one or more aspects ofAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO74the present disclosure. The process flow 800 may include a wireless device 415-c, which may be an example of the wireless device 415 described with reference to FIG. 4. The process flow 800 may also include an NTN node 445-c, which may be an example of the NTN node 445 described with reference to FIG. 4. The process flow 800 may also include an NTN node 445-d, which may be an example of the NTN node 445 described with reference to FIG. 4, a satellite, or another NTN node. The NTN node 445-c and the NTN node 445-d may be included in a same NTN or in different NTNs (e.g., same or different satellite constellations). The process flow 800 may additionally include a network entity 405-c, which may be an example of the network entity 405 described with reference to FIG. 4.

[0211] In the following description of the process flow 800, the communications between the wireless device 415-c, the NTN node 445-c, the NTN node 445-d, or the network entity 405-c may be transmitted in the example order shown, or in a different order than the example order shown, or the operations performed by the wireless device 415-c, the NTN node 445-c, the NTN node 445-d, or the network entity 405-c may be performed in different orders or at different times. One or more operations may be omitted from the process flow 800, or one or more other operations may be added to the process flow 800. Although some operations or signaling may be shown to occur at different times for discussion purposes, these operations may actually occur at the same time or in overlapping time periods in some examples.

[0212] In some examples, the wireless device 415-c and the network entity 405-c may communicate information via the NTN node 445-c, the wireless device 415-c and the network entity 405-c may communicate information independent of the NTN node 445-c, or a combination thereof. In some examples, the wireless device 415-c, the NTN node 445-c, or the network entity 405-c may communicate information, where the information may be relayed transparently via the NTN node 445-c, may be processed by the NTN node 445-c before communication to the wireless device 415-c or the network entity 405-c, or may not be transmitted to the wireless device 415-c or the network entity 405-c. In some approaches, one or more other devices (e.g., NTN node(s), TN node(s), gateway(s), or other device(s)) may be utilized for communications among the wireless device 415-b, the network entity 405-b, or the NTN node 445-b.Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO75

[0213] At 805, the wireless device 415-c may output (e.g., transmit), or the network entity 405-c may obtain (e.g., receive), a request for configuration information. For instance, the request may be communicated as described with reference to FIG. 4. In some examples, the request may indicate a PPW identifier (e.g., from a set of configured PPW identifiers).

[0214] At 810, the network entity 405-c may output (e.g., transmit), or the wireless device 415-c may obtain (e.g., receive), configuration information. For instance, the configuration information may be communicated as described with reference to FIG. 4. In some examples, the configuration information may configure the wireless device 415-c with multiple window lengths within a PPW periodicity, where the multiple window lengths may be associated with a PPW identifier.

[0215] At 815, the NTN node 445-c may output (e.g., transmit), or the wireless device 415-c may obtain (e.g., receive) one or more signals (e.g., PRSs). In some examples, the signal(s) may be communicated as described with reference to FIG. 4. The wireless device 415-c may obtain one or more measurements (e.g., PRS measurements) based on the signals. In some examples, the signal(s) may be communicated during a first window length corresponding to the PPW identifier.

[0216] At 820, the NTN node 445-d may output (e.g., transmit), or the wireless device 415-c may obtain (e.g., receive) one or more signals (e.g., PRSs). In some examples, the signal(s) may be communicated as described with reference to FIG. 4. The wireless device 415-c may obtain one or more measurements (e.g., PRS measurements) based on the signals. In some examples, the signal(s) may be communicated during a second window length corresponding to the PPW identifier.

[0217] At 825, the wireless device 415-c may output (e.g., transmit), or the network entity 405-c may obtain (e.g., receive), a report. In some examples, the report may be communicated as described with reference to FIG. 4. For instance, the report may include measurement information indicating one or more PRS measurements from the first window length and the second window length corresponding to the PPW identifier. In some examples, the wireless device 415-b may obtain (e.g., receive) signals from one or more other NTN nodes or TN nodes, where the report may include one or more indications of measurements from the signal(s) from the other NTN node(s) or TNAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO76node(s). In some examples, the network entity 405-b may utilize the measurements to determine (e.g., calculate) a position of the wireless device 415-b. In some aspects, the network entity 405-c may output (e.g., transmit), or the wireless device 415-c may obtain (e.g., receive) an indication of the position determined by the network entity 405-c.

[0218] FIG. 9 shows a block diagram 900 of a device 905 that supports processing windows for NTN node-based positioning in accordance with one or more aspects of the present disclosure. The device 905 may be an example of aspects of a wireless device as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communications manager 920. The device 905, or one or more components of the device 905 (e.g., the receiver 910, the transmitter 915, the communications manager 920), may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0219] The receiver 910 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to processing windows for NTN node-based positioning). Information may be passed on to other components of the device 905. The receiver 910 may utilize a single antenna or a set of multiple antennas.

[0220] The transmitter 915 may provide a means for transmitting signals generated by other components of the device 905. For example, the transmitter 915 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to processing windows for NTN node-based positioning). In some examples, the transmitter 915 may be co-located with a receiver 910 in a transceiver module. The transmitter 915 may utilize a single antenna or a set of multiple antennas.

[0221] The communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be examples of means for performingAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO77various aspects of processing windows for NTN node-based positioning as described herein. For example, the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be capable of performing one or more of the functions described herein.

[0222] In some examples, the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include at least one of a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure. In some examples, at least one processor and at least one memory coupled with the at least one processor may be configured to perform one or more of the functions described herein (e.g., by one or more processors, individually or collectively, executing instructions stored in the at least one memory).

[0223] Additionally, or alternatively, the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by at least one processor (e.g., referred to as a processor-executable code). If implemented in code executed by at least one processor, the functions of the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure).

[0224] In some examples, the communications manager 920 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 910, the transmitter 915, or both. For example, the communications manager 920 may receive information from the receiver 910, send information to the transmitter 915, or be integrated inAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO78combination with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.

[0225] The communications manager 920 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 920 is capable of, configured to, or operable to support a means for receiving configuration information indicating a PPW identifier of a PPW and a periodicity of the PPW, where the configuration information indicates multiple window lengths within the periodicity of the PPW, and the PPW identifier is associated with the multiple window lengths. The communications manager 920 is capable of, configured to, or operable to support a means for receiving, from at least one NTN node, a PRS in one or more of the multiple window lengths. The communications manager 920 is capable of, configured to, or operable to support a means for obtaining measurement information based on the PRS within a respective window length of the multiple window lengths.

[0226] By including or configuring the communications manager 920 in accordance with examples as described herein, the device 905 (e.g., at least one processor controlling or otherwise coupled with the receiver 910, the transmitter 915, the communications manager 920, or a combination thereof) may support techniques for reduced processing, reduced power consumption, more efficient utilization of communication resources.

[0227] FIG. 10 shows a block diagram 1000 of a device 1005 that supports processing windows for NTN node-based positioning in accordance with one or more aspects of the present disclosure. The device 1005 may be an example of aspects of a device 905 or a wireless device as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communications manager 1020. The device 1005, or one or more components of the device 1005 (e.g., the receiver 1010, the transmitter 1015, the communications manager 1020), may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0228] The receiver 1010 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated withAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO79various information channels (e.g., control channels, data channels, information channels related to processing windows for NTN node-based positioning). Information may be passed on to other components of the device 1005. The receiver 1010 may utilize a single antenna or a set of multiple antennas.

[0229] The transmitter 1015 may provide a means for transmitting signals generated by other components of the device 1005. For example, the transmitter 1015 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to processing windows for NTN node-based positioning). In some examples, the transmitter 1015 may be co-located with a receiver 1010 in a transceiver module. The transmitter 1015 may utilize a single antenna or a set of multiple antennas.

[0230] The device 1005, or various components thereof, may be an example of means for performing various aspects of processing windows for NTN node-based positioning as described herein. For example, the communications manager 1020 may include a configuration component 1025, a window component 1030, a measurement component 1035, or any combination thereof. The communications manager 1020 may be an example of aspects of a communications manager 920 as described herein. In some examples, the communications manager 1020, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1010, the transmitter 1015, or both. For example, the communications manager 1020 may receive information from the receiver 1010, send information to the transmitter 1015, or be integrated in combination with the receiver 1010, the transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0231] The communications manager 1020 may support wireless communications in accordance with examples as disclosed herein. The configuration component 1025 is capable of, configured to, or operable to support a means for receiving configuration information indicating a PPW identifier of a PPW and a periodicity of the PPW, where the configuration information indicates multiple window lengths within the periodicity of the PPW, and the PPW identifier is associated with the multiple window lengths. The Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO80window component 1030 is capable of, configured to, or operable to support a means for receiving, from at least one NTN node, a PRS in one or more of the multiple window lengths. The measurement component 1035 is capable of, configured to, or operable to support a means for obtaining measurement information based on the PRS within a respective window length of the multiple window lengths.

[0232] FIG. 11 shows a block diagram 1100 of a communications manager 1120 that supports processing windows for NTN node-based positioning in accordance with one or more aspects of the present disclosure. The communications manager 1120 may be an example of aspects of a communications manager 920, a communications manager 1020, or both, as described herein. The communications manager 1120, or various components thereof, may be an example of means for performing various aspects of processing windows for NTN node-based positioning as described herein. For example, the communications manager 1120 may include a configuration component 1125, a window component 1130, a measurement component 1135, a control component 1140, a request component 1145, a parameter component 1150, a capability component 1155, an identifier component 1160, or any combination thereof. Each of these components, or components or subcomponents thereof (e.g., one or more processors, one or more memories), may communicate, directly or indirectly, with one another (e.g., via one or more buses).

[0233] The communications manager 1120 may support wireless communications in accordance with examples as disclosed herein. The configuration component 1125 is capable of, configured to, or operable to support a means for receiving configuration information indicating a PPW identifier of a PPW and a periodicity of the PPW, where the configuration information indicates multiple window lengths within the periodicity of the PPW, and the PPW identifier is associated with the multiple window lengths. The window component 1130 is capable of, configured to, or operable to support a means for receiving, from at least one NTN node, a PRS in one or more of the multiple window lengths. The measurement component 1135 is capable of, configured to, or operable to support a means for obtaining measurement information based on the PRS within a respective window length of the multiple window lengths.Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO81

[0234] In some examples, the configuration information indicates a first window length associated with the PPW identifier that is different from a second window length associated with the PPW identifier.

[0235] In some examples, the configuration information indicates at least one gap between a pair of the multiple window lengths associated with the PPW identifier.

[0236] In some examples, the configuration information indicates different gaps between different pairs of the multiple window lengths associated with the PPW identifier.

[0237] In some examples, the control component 1140 is capable of, configured to, or operable to support a means for receiving control information indicating activation or deactivation of the PPW based on the PPW identifier of the PPW, where the activation or deactivation of the PPW corresponds to the multiple window lengths associated with the PPW identifier.

[0238] In some examples, the activation or deactivation of the PPW indicates activation or deactivation of the PPW that corresponds to the multiple window lengths on a BWP or a PFL.

[0239] In some examples, the capability component 1155 is capable of, configured to, or operable to support a means for transmitting capability information indicating a quantity of PPW identifiers for concurrent activation supported by the wireless device, where the control information is received based on the capability information.

[0240] In some examples, a set of PPW identifiers includes a first subset of PPW identifiers corresponding to PPWs for NTN positioning and a second subset of PPW identifiers corresponding to PPWs for TN positioning, and where the PPW identifier is included in the first subset of PPW identifiers for NTN positioning.

[0241] In some examples, the configuration information indicates that at least one of the multiple window lengths is greater than 160 slots.

[0242] In some examples, the request component 1145 is capable of, configured to, or operable to support a means for transmitting a request for the configuration information indicating the PPW identifier for NTN positioning, where the configuration information is received based on the request.Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO82

[0243] In some examples, the identifier component 1160 is capable of, configured to, or operable to support a means for receiving an indication of a set of PPW identifiers, where the request for the configuration information is transmitted based on the set of PPW identifiers.

[0244] In some examples, the parameter component 1150 is capable of, configured to, or operable to support a means for receiving an indication of at least one parameter, including a downlink PPW identifier parameter, a downlink periodicity and start slot parameter, a length parameter, a type parameter, a priority parameter, or a combination thereof, where the request for the configuration information is based on the at least one parameter.

[0245] In some examples, the parameter component 1150 is capable of, configured to, or operable to support a means for receiving, from a network entity, an indication of a PPW parameter, a PPW drift parameter, and a PPW drift variation parameter to determine a time-varying start parameter or a time-varying duration parameter, where a start time of the PPW is based on the time-varying start parameter or a duration of the PPW is based on the time-varying duration parameter.

[0246] In some examples, the parameter component 1150 is capable of, configured to, or operable to support a means for receiving, from a network entity, an indication of a PPW parameter, a PPW drift parameter, and a PPW drift variation parameter to determine a time-varying start parameter or a time-varying duration parameter, where a start time of at least one of the multiple window lengths is based on the time-varying start parameter or a duration of at least one of the multiple window lengths is based on the time-varying duration parameter.

[0247] In some examples, the configuration information indicates a priority for PRSs. In some examples, receiving the PRS from the at least one NTN node is performed based on the priority.

[0248] In some examples, the configuration information indicates a priority for PRSs. In some examples, obtaining the measurement information based on the PRS is performed based on the priority.Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO83

[0249] In some examples, the configuration information indicates a priority among the multiple window lengths. In some examples, obtaining the measurement information based on the PRS is performed based on the priority.

[0250] In some examples, obtaining the measurement information based on the PRS is performed based on a priority among the multiple window lengths that is based on an order of the multiple window lengths.

[0251] FIG. 12 shows a diagram of a system 1200 including a device 1205 that supports processing windows for NTN node-based positioning in accordance with one or more aspects of the present disclosure. The device 1205 may be an example of or include components of a device 905, a device 1005, or a wireless device as described herein. The device 1205 may be an example of or include components of a device 1205, a device 1305, or a wireless device 415 as described herein. The device 1205 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 1220, an I / O controller, such as an I / O controller 1210, one or more transceivers 1215, one or more antennas 1225, at least one memory 1230, code 1235, and at least one processor 1240. The device 1205 may include one or more sensors 1250. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1245). The I / O controller 1210 may manage input and output signals for the device 1205. The I / O controller 1210 may also manage peripherals not integrated into the device 1205. In some cases, the I / O controller 1210 may represent a physical connection or port to an external peripheral. In some cases, the I / O controller 1210 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system.Additionally, or alternatively, the I / O controller 1210 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, the I / O controller 1210 may be implemented as part of one or more processors, such as the at least one processor 1240. In some cases, a user may interact with the device 1205 via the I / O controller 1210 or via hardware components controlled by the I / O controller 1210.Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO84

[0252] In some cases, the device 1205 may include a single antenna. However, in some other cases, the device 1205 may have more than one antenna, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver(s) 1215 may communicate bi-directionally via the one or more antennas 1225 using wired or wireless links as described herein. For example, the transceiver 1215 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 1215 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 1225 for transmission, and to demodulate packets received from the one or more antennas 1225. The transceiver 1215, or the transceiver 1215 and one or more antennas 1225, may be an example of a transmitter 915, a transmitter 1015, a receiver 910, a receiver 1010, or any combination thereof or component thereof, as described herein.

[0253] The one or more transceivers 1215 may include one or more wireless wide area network (WWAN) transceivers, one or more short-range wireless transceivers, or one or more satellite transceivers. The WWAN transceiver(s) may communicate with (e.g., transmit one or more signals to, or receive one or more signals from) one or more wireless communication networks, such as an NR network, an LTE network, or a GSM network, among other examples. The WWAN transceiver(s) may be connected to one or more of the antenna(s) 1225 for communicating with other devices, such as one or more UEs 115, network nodes 105, access points, base stations (e.g., eNBs, gNBs), or another device(s), via at least one RAT (e.g., NR, LTE, or GSM, among other examples) over a wireless communication medium (e.g., time or frequency resources of a frequency spectrum). The WWAN transceiver(s) may be configured for transmitting and encoding signals (e.g., messages, indications, or information, among other examples) or for receiving and decoding signals (e.g., messages, indications, information, or pilots, among other examples), in accordance with the RAT. For instance, the WWAN transceiver(s) may include one or more transmitters for transmitting and encoding signals, or one or more receivers for receiving and decoding signals.

[0254] The short-range wireless transceivers may be connected to one or more of the antenna(s) 1225 to communicate with (e.g., transmit one or more signals to, or receive one or more signals from) one or more network entities, such as one or more UEs 115, network nodes 105, access points, base stations, or another device(s), via atAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO85least one RAT (e.g., Wi-Fi, LTE Direct, BLUETOOTH®, ZIGBEE®, Z-WAVE®, PC5, dedicated short-range communications (DSRC), wireless access for vehicular environments (WAVE), near-field communication (NFC), or ultra-wideband (UWB), among other examples) over a wireless communication medium. The short-range wireless transceiver(s) may be configured for transmitting and encoding signals (e.g., messages, indications, or information, among other examples), or for receiving and decoding signals (e.g., messages, indications, information, or pilots, among other examples), in accordance with the RAT. For instance, the short-range wireless transceiver(s) may include one or more transmitters for transmitting and encoding signals, or one or more receivers for receiving and decoding signals. In some examples, the short-range wireless transceiver s) may be one or more Wi-Fi transceivers, BLUETOOTH® transceivers, ZIGBEE® transceivers, Z-WAVE® transceivers, NFC transceivers, UWB transceivers, vehi cl e-to- vehicle (V2V) transceivers, or vehicle-to-everything (V2X) transceivers, among other examples.

[0255] The satellite transceiver(s) may include one or more satellite signal receivers, or one or more satellite signal transmitters. In some cases, the device 1205 may be a terrestrial device that may communicate one or more satellites via the satellite transceiver(s). In other cases, device 1205 may be a satellite (or other non-terrestrial entity) that uses the satellite transceiver(s) to communicate with one or more terrestrial networks or other satellites.

[0256] The satellite signal receiver(s) may be connected to one or more of the antenna(s) 1225 for receiving or measuring satellite positioning or communication signals. In some examples, the satellite signal receiver(s) may include one or more satellite positioning system receivers, where the satellite positioning or communication signals may be GPS signals, GLONASS signals, Galileo signals, BeiDou signals, Indian Regional Navigation Satellite System (NAVIC), or Quasi-Zenith Satellite System (QZSS) signals, among other examples. In some examples, the satellite signal receiver(s) may include one or more NTN receivers, where the satellite positioning or communication signals may be communication signals (e.g., carrying control or user data) originating from a device or network. The satellite signal receiver(s) may include hardware or a combination of hardware and instructions for receiving and processing satellite positioning or communication signals. The satellite signal receiver(s) or theAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO86processor 1240 may perform calculations to determine a location of the device 1205, the UE 115, the network node 105, or another device using measurements obtained from one or more satellite signals.

[0257] The one or more satellite signal transmitters may be connected to one or more of the antennas 1225 for transmitting satellite positioning communication signals. In some examples, the satellite signal transmitter(s) may be satellite positioning system transmitters, and the satellite positioning or communication signals may be GPS signals, GLONASS® signals, Galileo signals, BeiDou signals, NAVIC, or QZSS signals, among other examples. In some examples, the satellite signal transmitter(s) include one or more NTN transmitters, and the satellite positioning or communication signals may be communication signals (e.g., carrying control or user data). The satellite signal transmitter(s) may comprise hardware or a combination of hardware and instructions for transmitting satellite positioning or communication signals.

[0258] The device 1205 may include one or more sensors 1250 coupled with the one or more processors 1240 for obtaining sensor data (e.g., image data, RF data, motion data, orientation data, or audio data, among other examples). For example, the one or more sensors 1250 may sense or detect movement or orientation information. In some aspects, the movement or orientation information may be independent from motion data derived from signals received by the one or more WWAN transceivers, the one or more short-range wireless transceivers, or the satellite signal interface. In some examples, the sensor(s) 1250 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), or any other type of movement detection sensor. Additionally, or alternatively, the one or more sensors 1250 may include an image sensor, camera, microphone, light detector, or pressure sensor, among other examples. In some aspects, the sensor(s) 1250 may include a plurality of different types of devices, and the device 1205 (e.g., sensor(s) or 1250 processor(s) 1240) may combine the outputs of the different types of devices to provide motion information. For example, the sensor(s) 1250 may use a combination of a multi-axis accelerometer sensors, orientation sensors, or image sensors to provide the ability to compute positions in two-dimensional (2D) or three-dimensional (3D) coordinate systems.Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO87

[0259] The at least one memory 1230 may include RAM and ROM. The at least one memory 1230 may store computer-readable, computer-executable, or processorexecutable code, such as the code 1235. The code 1235 may include instructions that, when executed by the at least one processor 1240, cause the device 1205 to perform various functions described herein. The code 1235 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 1235 may not be directly executable by the at least one processor 1240 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the at least one memory 1230 may include, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices.

[0260] The at least one processor 1240 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more CPUs, one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combination thereof). In some cases, the at least one processor 1240 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the at least one processor 1240. The at least one processor 1240 may be configured to execute computer-readable instructions stored in a memory (e.g., the at least one memory 1230) to cause the device 1205 to perform various functions (e.g., functions or tasks supporting signaling for processing windows for NTN node-based positioning). For example, the device 1205 or a component of the device 1205 may include at least one processor 1240 and at least one memory 1230 coupled with or to the at least one processor 1240, the at least one processor 1240 and the at least one memory 1230 configured to perform various functions described herein.

[0261] In some examples, the at least one processor 1240 may include multiple processors and the at least one memory 1230 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform variousAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO88functions described herein. In some examples, the at least one processor 1240 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 1240) and memory circuitry (which may include the at least one memory 1230)), or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, the at least one processor 1240 or a processing system including the at least one processor 1240 may be configured to, configurable to, or operable to cause the device 1205 to perform one or more of the functions described herein. Further, as described herein, being “configured to,” being “configurable to,” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code 1235 (e.g., processor-executable code) stored in the at least one memory 1230 or otherwise, to perform one or more of the functions described herein.

[0262] The communications manager 1220 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 1220 is capable of, configured to, or operable to support a means for receiving configuration information indicating a PPW identifier of a PPW and a periodicity of the PPW, where the configuration information indicates multiple window lengths within the periodicity of the PPW, and the PPW identifier is associated with the multiple window lengths. The communications manager 1220 is capable of, configured to, or operable to support a means for receiving, from at least one NTN node, a PRS in one or more of the multiple window lengths. The communications manager 1220 is capable of, configured to, or operable to support a means for obtaining measurement information based on the PRS within a respective window length of the multiple window lengths.

[0263] By including or configuring the communications manager 1220 in accordance with examples as described herein, the device 1205 may support techniques for enhanced positioning accuracy, improved communication reliability, reduced latency, reduced power consumption, more efficient utilization of communication resources, improved coordination between devices, longer battery life, or improved utilization of processing capability.Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO89

[0264] In some examples, the communications manager 1220 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver 1215, the one or more antennas 1225, or any combination thereof. Although the communications manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1220 may be supported by or performed by the at least one processor 1240, the at least one memory 1230, the code 1235, or any combination thereof. For example, the code 1235 may include instructions executable by the at least one processor 1240 to cause the device 1205 to perform various aspects of processing windows for NTN node-based positioning as described herein, or the at least one processor 1240 and the at least one memory 1230 may be otherwise configured to, individually or collectively, perform or support such operations.

[0265] FIG. 13 shows a block diagram 1300 of a device 1305 that supports processing windows for NTN node-based positioning in accordance with one or more aspects of the present disclosure. The device 1305 may be an example of aspects of a network entity as described herein. The device 1305 may include a receiver 1310, a transmitter 1315, and a communications manager 1320. The device 1305, or one or more components of the device 1305 (e.g., the receiver 1310, the transmitter 1315, the communications manager 1320), may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0266] The receiver 1310 may provide a means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). Information may be passed on to other components of the device 1305. In some examples, the receiver 1310 may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 1310 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO90

[0267] The transmitter 1315 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 1305. For example, the transmitter 1315 may output information such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). In some examples, the transmitter 1315 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 1315 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1315 and the receiver 1310 may be co-located in a transceiver, which may include or be coupled with a modem.

[0268] The communications manager 1320, the receiver 1310, the transmitter 1315, or various combinations or components thereof may be examples of means for performing various aspects of processing windows for NTN node-based positioning as described herein. For example, the communications manager 1320, the receiver 1310, the transmitter 1315, or various combinations or components thereof may be capable of performing one or more of the functions described herein.

[0269] In some examples, the communications manager 1320, the receiver 1310, the transmitter 1315, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include at least one of a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure. In some examples, at least one processor and at least one memory coupled with the at least one processor may be configured to perform one or more of the functions described herein (e.g., by one or more processors, individually or collectively, executing instructions stored in the at least one memory).

[0270] Additionally, or alternatively, the communications manager 1320, the receiver 1310, the transmitter 1315, or various combinations or components thereof may Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO91be implemented in code (e.g., as communications management software or firmware) executed by at least one processor (e.g., referred to as a processor-executable code). If implemented in code executed by at least one processor, the functions of the communications manager 1320, the receiver 1310, the transmitter 1315, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure).

[0271] In some examples, the communications manager 1320 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1310, the transmitter 1315, or both. For example, the communications manager 1320 may receive information from the receiver 1310, send information to the transmitter 1315, or be integrated in combination with the receiver 1310, the transmitter 1315, or both to obtain information, output information, or perform various other operations as described herein.

[0272] The communications manager 1320 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 1320 is capable of, configured to, or operable to support a means for transmitting configuration information indicating a PPW identifier of a PPW and a periodicity of the PPW, where the configuration information indicates multiple window lengths within the periodicity of the PPW, and the PPW identifier is associated with the multiple window lengths. The communications manager 1320 is capable of, configured to, or operable to support a means for receiving measurement information, the measurement information based on the PRS within a respective window length of the multiple window lengths.

[0273] By including or configuring the communications manager 1320 in accordance with examples as described herein, the device 1305 (e.g., at least one processor controlling or otherwise coupled with the receiver 1310, the transmitter 1315, the communications manager 1320, or a combination thereof) may support techniquesAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO92for reduced processing, reduced power consumption, or more efficient utilization of communication resources.

[0274] FIG. 14 shows a block diagram 1400 of a device 1405 that supports processing windows for NTN node-based positioning in accordance with one or more aspects of the present disclosure. The device 1405 may be an example of aspects of a device 1305 or a network entity as described herein. The device 1405 may include a receiver 1410, a transmitter 1415, and a communications manager 1420. The device 1405, or one or more components of the device 1405 (e.g., the receiver 1410, the transmitter 1415, the communications manager 1420), may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0275] The receiver 1410 may provide a means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). Information may be passed on to other components of the device 1405. In some examples, the receiver 1410 may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 1410 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0276] The transmitter 1415 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 1405. For example, the transmitter 1415 may output information such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). In some examples, the transmitter 1415 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 1415 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO93or any combination thereof. In some examples, the transmitter 1415 and the receiver 1410 may be co-located in a transceiver, which may include or be coupled with a modem.

[0277] The device 1405, or various components thereof, may be an example of means for performing various aspects of processing windows for NTN node-based positioning as described herein. For example, the communications manager 1420 may include a configuration manager 1425 a measurement manager 1430, or any combination thereof. The communications manager 1420 may be an example of aspects of a communications manager 1320 as described herein. In some examples, the communications manager 1420, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1410, the transmitter 1415, or both. For example, the communications manager 1420 may receive information from the receiver 1410, send information to the transmitter 1415, or be integrated in combination with the receiver 1410, the transmitter 1415, or both to obtain information, output information, or perform various other operations as described herein.

[0278] The communications manager 1420 may support wireless communications in accordance with examples as disclosed herein. The configuration manager 1425 is capable of, configured to, or operable to support a means for transmitting configuration information indicating a PPW identifier of a PPW and a periodicity of the PPW, where the configuration information indicates multiple window lengths within the periodicity of the PPW, and the PPW identifier is associated with the multiple window lengths. The measurement manager 1430 is capable of, configured to, or operable to support a means for receiving measurement information, the measurement information based on the PRS within a respective window length of the multiple window lengths.

[0279] FIG. 15 shows a block diagram 1500 of a communications manager 1520 that supports processing windows for NTN node-based positioning in accordance with one or more aspects of the present disclosure. The communications manager 1520 may be an example of aspects of a communications manager 1320, a communications manager 1420, or both, as described herein. The communications manager 1520, or various components thereof, may be an example of means for performing various Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO94aspects of processing windows for NTN node-based positioning as described herein. For example, the communications manager 1520 may include a configuration manager 1525, a measurement manager 1530, a capability component 1535, a request manager 1540, a parameter manager 1545, an identifier manager 1550, or any combination thereof. Each of these components, or components or subcomponents thereof (e.g., one or more processors, one or more memories), may communicate, directly or indirectly, with one another (e.g., via one or more buses). The communications may include communications within a protocol layer of a protocol stack, communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with a network entity, between devices, components, or virtualized components associated with a network entity), or any combination thereof.

[0280] The communications manager 1520 may support wireless communications in accordance with examples as disclosed herein. The configuration manager 1525 is capable of, configured to, or operable to support a means for transmitting configuration information indicating a PPW identifier of a PPW and a periodicity of the PPW, where the configuration information indicates multiple window lengths within the periodicity of the PPW, and the PPW identifier is associated with the multiple window lengths. The measurement manager 1530 is capable of, configured to, or operable to support a means for receiving measurement information, the measurement information based on the PRS within a respective window length of the multiple window lengths.

[0281] In some examples, the configuration information indicates a first window length associated with the PPW identifier that is different from a second window length associated with the PPW identifier.

[0282] In some examples, the configuration information indicates at least one gap between a pair of the multiple window lengths associated with the PPW identifier.

[0283] In some examples, the configuration information indicates different gaps between different pairs of the multiple window lengths associated with the PPW identifier.Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO95

[0284] In some examples, the capability component 1535 is capable of, configured to, or operable to support a means for receiving capability information indicating a quantity of PPW identifiers for concurrent activation supported by a wireless device.

[0285] In some examples, a set of PPW identifiers includes a first subset of PPW identifiers corresponding to PPWs for NTN positioning and a second subset of PPW identifiers corresponding to PPWs for TN positioning, and where the PPW identifier is included in the first subset of PPW identifiers for NTN positioning.

[0286] In some examples, the configuration information indicates that at least one of the multiple window lengths is greater than 160 slots.

[0287] In some examples, the request manager 1540 is capable of, configured to, or operable to support a means for receiving a request for the configuration information indicating the PPW identifier for NTN positioning, where the configuration information is transmitted based on the request.

[0288] In some examples, the identifier manager 1550 is capable of, configured to, or operable to support a means for transmitting an indication of a set of PPW identifiers, where the request for the configuration information is received based on the set of PPW identifiers.

[0289] In some examples, the parameter manager 1545 is capable of, configured to, or operable to support a means for transmitting an indication of at least one parameter, including a downlink PPW identifier parameter, a downlink periodicity and start slot parameter, a length parameter, a type parameter, a priority parameter, or a combination thereof, where the request for the configuration information is based on the at least one parameter.

[0290] In some examples, the parameter manager 1545 is capable of, configured to, or operable to support a means for transmitting, to a wireless device, an indication of a PPW parameter, a PPW drift parameter, and a PPW drift variation parameter to determine a time-varying start parameter or a time-varying duration parameter, where a start time of the PPW is based on the time-varying start parameter or a duration of the PPW is based on the time-varying duration parameter.Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO96

[0291] In some examples, the parameter manager 1545 is capable of, configured to, or operable to support a means for transmitting, to a wireless device, an indication of a PPW parameter, a PPW drift parameter, and a PPW drift variation parameter to determine a time-varying start parameter or a time-varying duration parameter, where a start time of at least one of the multiple window lengths is based on the time-varying start parameter or a duration of at least one of the multiple window lengths is based on the time-varying duration parameter.

[0292] In some examples, the configuration information indicates a priority for PRSs. In some examples, receiving the measurement information based on the PRS is based on the priority.

[0293] In some examples, the configuration information indicates a priority among the multiple window lengths. In some examples, receiving the measurement information based on the PRS is based on the priority.

[0294] FIG. 16 shows a diagram of a system 1600 including a device 1605 that supports processing windows for NTN node-based positioning in accordance with one or more aspects of the present disclosure. The device 1605 may be an example of or include components of a device 1605, a device 1705, or a network entity 405 as described herein. The device 1605 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 1620, one or more transceivers 1610, one or more antennas 1615, at least one memory 1625, code 1630, and at least one processor 1635. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1640).

[0295] The transceiver 1610 may support bi-directional communications via wired links, wireless links, or both as described herein. In some examples, the transceiver 1610 may include a wired transceiver and may communicate bi-directionally with another wired transceiver. Additionally, or alternatively, in some examples, the transceiver 1610 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1605 may include one or more antennas 1615, which may be capable of transmitting or receivingAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO97wireless transmissions (e.g., concurrently). The transceiver 1610 may also include a modem to modulate signals, to provide the modulated signals for transmission (e.g., by one or more antennas 1615, by a wired transmitter), to receive modulated signals (e.g., from one or more antennas 1615, from a wired receiver), and to demodulate signals. In some implementations, the transceiver 1610 may include one or more interfaces, such as one or more interfaces coupled with the one or more antennas 1615 that are configured to support various receiving or obtaining operations, or one or more interfaces coupled with the one or more antennas 1615 that are configured to support various transmitting or outputting operations, or a combination thereof. In some implementations, the transceiver 1610 may include or be configured for coupling with one or more processors or one or more memory components that are operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other outputting, or any combination thereof. In some implementations, the transceiver 1610, or the transceiver 1610 and the one or more antennas 1615, or the transceiver 1610 and the one or more antennas 1615 and one or more processors or one or more memory components (e.g., the at least one processor 1635, the at least one memory 1625, or both), may be included in a chip or chip assembly that is installed in the device 1605. In some examples, the transceiver 1610 may be operable to support communications via one or more communications links (e.g., communication link(s) 125, backhaul communication link(s) 120, a midhaul communication link 162, a fronthaul communication link 168).

[0296] The one or more transceivers 1610 may include one or more WWAN transceivers, one or more short-range wireless transceivers, or one or more satellite transceivers. The WWAN transceiver(s) may communicate with (e.g., transmit one or more signals to, or receive one or more signals from) one or more wireless devices, such as the network node 105 or the UE 115, among other examples. The WWAN transceiver(s) may be connected to one or more of the antenna(s) 1615 for communicating with other devices, such as one or more UEs 115, network nodes 105, access points, base stations (e.g., eNBs, gNBs), or another device(s), via at least one RAT (e.g., NR, LTE, or GSM, among other examples) over a wireless communication medium (e.g., time or frequency resources of a frequency spectrum). The WWAN transceiver(s) may be configured for transmitting and encoding signals (e.g., messages,Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO98indications, or information, among other examples) or for receiving and decoding signals (e.g., messages, indications, information, or pilots, among other examples), in accordance with the RAT. For instance, the WWAN transceiver(s) may include one or more transmitters for transmitting and encoding signals, or one or more receivers for receiving and decoding signals.

[0297] The short-range wireless transceivers may be connected to one or more of the antenna(s) 1615 to communicate with (e.g., transmit one or more signals to, or receive one or more signals from) one or more network entities, such as one or more UEs 115, network nodes 105, access points, base stations, or another device(s), via at least one RAT (e.g, Wi-Fi, LTE Direct, BLUETOOTH®, ZIGBEE®, Z-WAVE®, PC5, DSRC, WAVE, NFC, or UWB, among other examples) over a wireless communication medium. The short-range wireless transceiver(s) may be configured for transmitting and encoding signals (e.g, messages, indications, or information, among other examples), or for receiving and decoding signals (e.g, messages, indications, information, or pilots, among other examples), in accordance with the RAT. For instance, the short-range wireless transceiver(s) may include one or more transmitters for transmitting and encoding signals, or one or more receivers for receiving and decoding signals. In some examples, the short-range wireless transceiver(s) may be one or more Wi-Fi transceivers, BLUETOOTH® transceivers, ZIGBEE® transceivers, Z-WAVE® transceivers, NFC transceivers, UWB transceivers, V2V transceivers, or V2X transceivers, among other examples.

[0298] The satellite transceiver(s) may include one or more satellite signal receivers, or one or more satellite signal transmitters. In some cases, the device 1605 may be a terrestrial device that may communicate one or more satellites via the satellite transceiver(s). In other cases, device 1605 may be a satellite (or other non-terrestrial entity) that uses the satellite transceiver(s) to communicate with one or more terrestrial networks or other satellites.

[0299] The satellite signal receiver(s) may be connected to one or more of the antenna(s) 1615 for receiving or measuring satellite positioning or communication signals. In some examples, the satellite signal receiver(s) may include one or more satellite positioning system receivers, where the satellite positioning or communication signals may be GPS signals, GLONASS signals, Galileo signals, BeiDou signals, Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO99NAVIC, or QZSS signals, among other examples. In some examples, the satellite signal receiver(s) may include one or more NTN receivers, where the satellite positioning or communication signals may be communication signals (e.g., carrying control or user data) originating from a device or network. The satellite signal receiver(s) may include hardware or a combination of hardware and instructions for receiving and processing satellite positioning or communication signals. The satellite signal receiver(s) or the processor 1635 may perform calculations to determine a location of the device 1605, the UE 115, the network node 105, or another device using measurements obtained from one or more satellite signals.

[0300] The one or more satellite signal transmitters may be connected to one or more of the antennas 1615 for transmitting satellite positioning communication signals. In some examples, the satellite signal transmitter(s) may be satellite positioning system transmitters, and the satellite positioning or communication signals may be GPS signals, GLONASS® signals, Galileo signals, BeiDou signals, NAVIC, or QZSS signals, among other examples. In some examples, the satellite signal transmitter(s) include one or more NTN transmitters, and the satellite positioning or communication signals may be communication signals (e.g., carrying control or user data). The satellite signal transmitter(s) may comprise hardware or a combination of hardware and instructions for transmitting satellite positioning or communication signals.

[0301] The at least one memory 1625 may include RAM, ROM, or any combination thereof. The at least one memory 1625 may store computer-readable, computerexecutable, or processor-executable code, such as the code 1630. The code 1630 may include instructions that, when executed by one or more of the at least one processor 1635, cause the device 1605 to perform various functions described herein. The code 1630 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 1630 may not be directly executable by a processor of the at least one processor 1635 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the at least one memory 1625 may include, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices. In some examples, the at least one processor 1635 may include multiple processors and the at least one memory 1625 may include multiple memories.Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO100One or more of the multiple processors may be coupled with one or more of the multiple memories which may, individually or collectively, be configured to perform various functions herein (for example, as part of a processing system).

[0302] The at least one processor 1635 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more CPUs, one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combination thereof). In some cases, the at least one processor 1635 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into one or more of the at least one processor 1635. The at least one processor 1635 may be configured to execute computer-readable instructions stored in a memory (e.g., one or more of the at least one memory 1625) to cause the device 1605 to perform various functions (e.g., functions or tasks supporting processing windows for NTN node-based positioning). For example, the device 1605 or a component of the device 1605 may include at least one processor 1635 and at least one memory 1625 coupled with one or more of the at least one processor 1635, the at least one processor 1635 and the at least one memory 1625 configured to perform various functions described herein. The at least one processor 1635 may be an example of a cloud-computing platform (e.g., one or more physical nodes and supporting software such as operating systems, virtual machines, or container instances) that may host the functions (e.g., by executing code 1630) to perform the functions of the device 1605. The at least one processor 1635 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1605 (such as within one or more of the at least one memory 1625).

[0303] In some examples, the at least one processor 1635 may include multiple processors and the at least one memory 1625 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein. In some examples, the at least one processor 1635 may be aAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO101component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 1635) and memory circuitry (which may include the at least one memory 1625)), or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, the at least one processor 1635 or a processing system including the at least one processor 1635 may be configured to, configurable to, or operable to cause the device 1605 to perform one or more of the functions described herein. Further, as described herein, being “configured to,” being “configurable to,” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code stored in the at least one memory 1625 or otherwise, to perform one or more of the functions described herein.

[0304] In some examples, a bus 1640 may support communications of (e.g., within) a protocol layer of a protocol stack. In some examples, a bus 1640 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of the device 1605, or between different components of the device 1605 that may be co-located or located in different locations (e.g., where the device 1605 may refer to a system in which one or more of the communications manager 1620, the transceiver 1610, the at least one memory 1625, the code 1630, and the at least one processor 1635 may be located in one of the different components or divided between different components).

[0305] In some examples, the communications manager 1620 may manage aspects of communications with a core network 130 (e.g., via one or more wired or wireless backhaul links). For example, the communications manager 1620 may manage the transfer of data communications for client devices, such as one or more UEs 115. In some examples, the communications manager 1620 may manage communications with one or more other network nodes 105, and may include a controller or scheduler for controlling communications with UEs 115 (e.g., in cooperation with the one or more other network devices). In some examples, the communications manager 1620 mayAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO102support an X2 interface within an LTE / LTE-A wireless communications network technology to provide communication between network nodes 105.

[0306] The communications manager 1620 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 1620 is capable of, configured to, or operable to support a means for transmitting configuration information indicating a PPW identifier of a PPW and a periodicity of the PPW, where the configuration information indicates multiple window lengths within the periodicity of the PPW, and the PPW identifier is associated with the multiple window lengths. The communications manager 1620 is capable of, configured to, or operable to support a means for receiving measurement information, the measurement information based on the PRS within a respective window length of the multiple window lengths.

[0307] By including or configuring the communications manager 1620 in accordance with examples as described herein, the device 1605 may support techniques for increased positioning accuracy, improved communication reliability, reduced latency, improved user experience related to reduced processing, reduced power consumption, more efficient utilization of communication resources, improved coordination between devices, longer battery life, improved utilization of processing capability.

[0308] In some examples, the communications manager 1620 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the transceiver 1610, the one or more antennas 1615 (e.g., where applicable), or any combination thereof. Although the communications manager 1620 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1620 may be supported by or performed by the transceiver 1610, one or more of the at least one processor 1635, one or more of the at least one memory 1625, the code 1630, or any combination thereof (for example, by a processing system including at least a portion of the at least one processor 1635, the at least one memory 1625, the code 1630, or any combination thereof). For example, the code 1630 may include instructions executable by one or more of the at least one processor 1635 to cause the device 1605 to perform various aspects of processing windows for NTN node-based Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO103positioning as described herein, or the at least one processor 1635 and the at least one memory 1625 may be otherwise configured to, individually or collectively, perform or support such operations.

[0309] FIG. 17 shows a flowchart illustrating a method 1700 that supports processing windows for NTN node-based positioning in accordance with one or more aspects of the present disclosure. The operations of the method 1700 may be implemented by a wireless device or its components as described herein. For example, the operations of the method 1700 may be performed by a wireless device as described with reference to FIGs. 1 through 12. In some examples, a wireless device may execute a set of instructions to control the functional elements of the wireless device to perform the described functions. Additionally, or alternatively, the wireless device may perform aspects of the described functions using special-purpose hardware.

[0310] At 1705, the method may include receiving configuration information indicating a PPW identifier of a PPW and a periodicity of the PPW, where the configuration information indicates multiple window lengths within the periodicity of the PPW, and the PPW identifier is associated with the multiple window lengths. The operations of 1705 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1705 may be performed by a configuration component 1125 as described with reference to FIG. 11.

[0311] At 1710, the method may include receiving, from at least one NTN node, a PRS in one or more of the multiple window lengths. The operations of 1710 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1710 may be performed by a window component 1130 as described with reference to FIG. 11.

[0312] At 1715, the method may include obtaining measurement information based on the PRS within a respective window length of the multiple window lengths. The operations of 1715 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1715 may be performed by a measurement component 1135 as described with reference to FIG. 11.

[0313] FIG. 18 shows a flowchart illustrating a method 1800 that supports processing windows for NTN node-based positioning in accordance with one or moreAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO104aspects of the present disclosure. The operations of the method 1800 may be implemented by a wireless device or its components as described herein. For example, the operations of the method 1800 may be performed by a wireless device as described with reference to FIGs. 1 through 12. In some examples, a wireless device may execute a set of instructions to control the functional elements of the wireless device to perform the described functions. Additionally, or alternatively, the wireless device may perform aspects of the described functions using special-purpose hardware.

[0314] At 1805, the method may include receiving configuration information indicating a PPW identifier of a PPW and a periodicity of the PPW, where the configuration information indicates multiple window lengths within the periodicity of the PPW, and the PPW identifier is associated with the multiple window lengths. The operations of 1805 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1805 may be performed by a configuration component 1125 as described with reference to FIG. 11.

[0315] At 1810, the method may include receiving control information indicating activation of the PPW based on the PPW identifier of the PPW, where the activation of the PPW corresponds to the multiple window lengths associated with the PPW identifier. The operations of 1810 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1810 may be performed by a control component 1140 as described with reference to FIG. 11.

[0316] At 1815, the method may include receiving, from at least one NTN node, a PRS in one or more of the multiple window lengths. The operations of 1815 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1815 may be performed by a window component 1130 as described with reference to FIG. 11.

[0317] At 1820, the method may include obtaining measurement information based on the PRS within a respective window length of the multiple window lengths. The operations of 1820 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1820 may be performed by a measurement component 1135 as described with reference to FIG. 11.Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO105

[0318] FIG. 19 shows a flowchart illustrating a method 1900 that supports processing windows for NTN node-based positioning in accordance with one or more aspects of the present disclosure. The operations of the method 1900 may be implemented by a network entity or its components as described herein. For example, the operations of the method 1900 may be performed by a network entity as described with reference to FIGs. 1 through 21 and 13 through 16. In some examples, a network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally, or alternatively, the network entity may perform aspects of the described functions using special-purpose hardware.

[0319] At 1905, the method may include transmitting configuration information indicating a PPW identifier of a PPW and a periodicity of the PPW, where the configuration information indicates multiple window lengths within the periodicity of the PPW, and the PPW identifier is associated with the multiple window lengths. The operations of 1905 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1905 may be performed by a configuration manager 1525 as described with reference to FIG. 15.

[0320] At 1910, the method may include receiving measurement information, the measurement information based on the PRS within a respective window length of the multiple window lengths. The operations of 1910 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1910 may be performed by a measurement manager 1530 as described with reference to FIG. 15.

[0321] FIG. 20 shows a flowchart illustrating a method 2000 that supports processing windows for NTN node-based positioning in accordance with one or more aspects of the present disclosure. The operations of the method 2000 may be implemented by a network entity or its components as described herein. For example, the operations of the method 2000 may be performed by a network entity as described with reference to FIGs. 1 through 21 and 13 through 16. In some examples, a network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally, or alternatively, the network entity may perform aspects of the described functions using special-purpose hardware.Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO106

[0322] At 2005, the method may include receiving capability information indicating a quantity of PPW identifiers for concurrent activation supported by a wireless device. The operations of 2005 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2005 may be performed by a capability component 1535 as described with reference to FIG. 15.

[0323] At 2010, the method may include transmitting configuration information indicating a PPW identifier of a PPW and a periodicity of the PPW, where the configuration information indicates multiple window lengths within the periodicity of the PPW, and the PPW identifier is associated with the multiple window lengths. The operations of 2010 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2010 may be performed by a configuration manager 1525 as described with reference to FIG. 15.

[0324] At 2015, the method may include receiving measurement information, the measurement information based on the PRS within a respective window length of the multiple window lengths. The operations of 2015 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2015 may be performed by a measurement manager 1530 as described with reference to FIG. 15.

[0325] FIG. 21 shows examples of wireless communications systems 2100 that supports processing windows for NTN node-based positioning in accordance with one or more aspects of the present disclosure. Various positioning techniques are illustrated in the context of the wireless communications systems 2100. Some examples of the positioning procedures described herein may be performed in accordance with one or more aspects of the positioning techniques. While TRPs and UEs are provided in the examples illustrated in FIG. 21, other devices (e.g., network entities, base stations, RRHs, RUs, APs, wireless devices, or stations, among other examples) may be similarly utilized in other examples. The examples of positioning techniques include downlinkbased positioning techniques, uplink-based positioning techniques, and downlink-and-uplink-based positioning techniques.

[0326] Examples of OTDOA or DL-TDOA 2105 are illustrated in FIG. 21. One or more of the OTDOA or DL-TDOA 2105 positioning techniques may be included in a downlink-based positioning procedure. In OTDOA or DL-TDOA 2105 positioningAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO107techniques, a UE may measure a difference between TOAs of reference signals (e.g., PRSs) received from one or more pairs of TRPs (e.g., TRP2 and TRP3). In some approaches, a difference in TOAs may be referred to as an RSTD or a TDOA measurement. A positioning device (e.g., the UE, a location server, an LMF, an SLP, or another device) may utilize the differences in TOAs to determine (e.g., estimate) a location of the UE.

[0327] In some aspects, the UE may receive an identifier (ID) associated with a reference TRP (e.g., a serving base station) and one or more IDs associated with one or more non-reference TRPs in received data (e.g., assistance data). The UE may measure the difference of TOAs between the reference TRP and each of the non-reference TRPs to produce RSTDs or TDOAs. In some aspects, the UE may report an indication of the RSTDs or TDOAs to the positioning device (e.g., a location server, LMF, an SLP, or another device). Based on established locations of the base stations and the RSTD measurements, the positioning device (e.g., the UE for UE-based positioning or a location server for UE-assisted positioning) may estimate the UE’s location.

[0328] An example of UL-TDOA 2110 is illustrated in FIG. 21. One or more of the UL-TDOA 2110 positioning techniques may be included in an uplink-based positioning procedure. UL-TDOA 2110 may have some similarities to DL-TDOA 2105. The UL-TDOA 2110 positioning techniques may be based on uplink reference signals (e.g., SRS) transmitted from the UE to multiple TRPs. For example, the UE transmits one or more uplink reference signals that are measured by a reference TRP (e.g., TRP3) and non-reference TRPs (e.g., TRP1 and TRP2). Each TRP then reports the reception time (which may be referred to as a relative time of arrival (RTOA)) of the reference signal(s) to a positioning device (e.g., a location server, LMF, SLP, or UE) that has information about the locations and relative timing of the TRPs. Based on the reception-to-reception (Rx-Rx) time differences between the reported RTOA of the reference TRP and the reported RTOA of each non-reference TRP, the locations of the TRPs, and the corresponding timing offsets, the positioning device may estimate the location of the UE using TDOA.

[0329] An example of DL-AOD 2115 is illustrated in FIG. 21. One or more of the DL-AOD 2115 positioning techniques may be included in a downlink-based positioning procedure. In DL-AOD 2115, a UE may obtain received signal strength measurements Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO108corresponding to multiple downlink transmit beams for one or more TRPs (e.g., TRP1 and TRP2). In some approaches, the UE reports the measurements to a positioning device. The positioning device may use the signal strength measurements of the multiple downlink transmit beams to determine the angle(s) (e.g., A0D1 and AOD2) between the UE and the transmitting TRP(s). The positioning device (e.g., location server, LMF, SLP, UE, or another device) may estimate the location of the UE based on the determined angle(s) and the established location(s) of the transmitting TRP(s).

[0330] An example of UL-AOA 2120 is illustrated in FIG. 21. One or more of the UL-AOA 2120 positioning techniques may be included in an uplink positioning procedure. In UL-AOA 2120, one or more TRPs (e.g., TRP1 and TRP2) measure the received signal strength of one or more uplink reference signals (e.g., SRSs) received from a UE on one or more uplink receive beams. In some aspects, the signal strength measurements may be reported to a positioning device. A positioning device (e.g., LFM, SLP, UE, or another device) may use the signal strength measurements and the angle(s) of the receive beam(s) to determine the angle(s) between the UE and the TRP(s). Based on the determined angle(s) and the established location(s) of the TRP(s), the positioning device may estimate the location of the UE.

[0331] Some positioning techniques or procedures may include a combination downlink-based and uplink-based positioning techniques. Examples of downlink-based and uplink-based positioning techniques may include E-CID positioning and multi-round-trip-time (RTT) positioning (which may be referred to as “multi-RTT” or “multicell RTT” when multiple cells are utilized).

[0332] In multi-RTT, a first device (e.g., a TRP or UE) may transmit a first RTT-related signal (e.g., a PRS or SRS) to a second device (e.g., the UE or TRP). The second device may transmit a second RTT-related signal (e.g., an SRS or PRS) back to the first device. Each device may measure a time difference between the TOA of the received RTT-related signal and the transmission time of the transmitted RTT-related signal. The time difference may be referred to as a reception-to-transmission (Rx-Tx) time difference. In some aspects, the Rx-Tx time difference measurement may be obtained or adjusted to include (e.g., include only) a time difference between nearest slot boundaries for the received and transmitted signals. The first device or the second device may send the corresponding Rx-Tx time difference measurements to a positioning device (e.g., a Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO109location server, LMF, SLP, UE, or other device), which may calculate a round trip propagation time (or RTT) between the two device based on the two Rx-Tx time difference measurements (e.g., as a sum of the two Rx-Tx time difference measurements). Additionally, or alternatively, one device may send a corresponding Rx-Tx time difference measurement to the other device, which may calculate the RTT. The distance between the two devices may be determined from the RTT and a signal speed (e.g., the speed of light).

[0333] An example of multi-cell RTT 2125 is illustrated in FIG. 21. One or more of the multi-RTT or multi-cell RTT techniques described may be included in an uplinkbased or downlink-based positioning procedure. In multi-cell RTT 2125, a first device (e.g., a UE or TRP) may perform an RTT positioning procedure with multiple second devices (e.g., multiple TRPs or UEs) to enable the location of the first device to be determined (e.g., using multilateration) based on distances to, and the established locations of, the second devices.

[0334] In some examples, RTT or multi-RTT techniques may be combined with one or more other positioning techniques (e.g., UL-AOA, DL-AOD, or other positioning techniques), to enhance location accuracy. Examples of combined DL-AOD and RTT 2130 positioning techniques are illustrated in FIG. 21.

[0335] E-CID positioning techniques may be based on radio resource management (RRM) measurements. In E-CID, a UE may obtain or report a serving cell ID, a timing advance (TA), identifiers of one or more detected neighbor TRPs, estimated timing of one or more detected neighbor TRPs, or a signal strength measurement of one or more detected neighbor TRPs. A positioning device (e.g., an LFM, SLP, UE, or another device) may utilize the serving cell ID, TA, identifiers, estimated timing, or signal strength measurements with one or more established locations of one or more TRPs to estimate the location of the UE.

[0336] In some approaches, a positioning device (e.g., location server, LMF, SLP, or another device) may provide assistance data to the UE. Assistance data is data to assist with one or more positioning operations (e.g., to detect one or more neighboring TRPs or to receive reference signaling). For instance, the assistance data may indicate IDs of the TRPs (e.g., IDs of one or more cells or TRPs corresponding to a networkAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO110node) from which reference signals may be measured. In some examples, a positioning device may transmit assistance data or other information indicating one or more reference signal configuration parameters. The reference signal configuration parameter(s) may include or indicate a quantity of consecutive slots including PRS, a periodicity of consecutive slots including PRS, a muting sequence, a frequency hopping sequence, a reference signal identifier, a reference signal bandwidth, or one or more other parameters applicable to a positioning technique or procedure. Additionally, or alternatively, the assistance data may be sent from one or more TRPs (e.g., in periodically broadcasted overhead messages, a scheduled message, a unicast message, or a multicast message, among other examples). In some examples, a UE may be able to detect one or more neighboring TRPs (e.g., network entities) without the use of assistance data.

[0337] For OTDOA positioning techniques or DL-TDOA positioning techniques, the assistance data may indicate an expected RSTD value and an associated uncertainty or search window around the expected RSTD. For example, an expected RSTD value may have an associated uncertainty or search window with a range of ±500 microseconds (ps). In another example, when any of the resources used for the positioning measurement(s) are in frequency range 1 (FR1), an expected RSTD value may have an associated uncertainty or search window with a range of ±32 ps. In another example, when all of the resources used for the positioning measurement s) are in frequency range 2 (FR2), an expected RSTD value may have an associated uncertainty or search window with a range of ±8 ps.

[0338] In some examples, a location may be referred to as a position estimate, location estimate, position, position fix, or fix, among other examples. A location may be geodetic and include coordinates (e.g., latitude, longitude, or altitude) or may be civic and include a street address, postal address, or another description of a location. In some aspects, a location may be defined relative to another location or may be defined in absolute terms (e.g., latitude, longitude, or altitude). A location may include an indication of error or uncertainty (e.g., by including an area or volume within which the location may be included with a specified or default level of confidence).

[0339] Various examples of sidelink positioning techniques are illustrated in FIG. 21. Sidelink positioning techniques may include positioning techniques that are Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WOIllbased on sidelink communication (e.g., based exclusively on sidelink communication or based on sidelink communication jointly with other communication(s), such as Uu interface communication).

[0340] A first example of sidelink positioning 2135 is illustrated in FIG. 21. In the first example of sidelink positioning 2135, at least one peer UE with an established location may improve location estimation (e.g., Uu-based positioning, multi-cell RTT, DL-TDOA, or UL-TDOA, among other examples) for a target UE by providing an additional anchor (e.g., sidelink RTT (SL-RTT)).

[0341] A second example of sidelink positioning 2140 is illustrated in FIG. 21. In the second example of sidelink positioning 2140, different types (e.g., categories, classes, or capabilities) of UEs may be utilized. For example, first UEs and a second UE may be utilized. Relative to the second UE, the first UEs may have one or more increased capabilities, such as one or more additional sensors, a faster processor, greater memory capacity, one or more additional antenna elements, a higher transmit power capability, access to one or more additional frequency bands, or any combination thereof. In some aspects, the second UE may be a reduced capacity or “RedCap” UE. The second UE may be assisted by the first UEs to determine the location of the second UE. For instance, sidelink-based positioning or ranging procedures may be performed with the first UEs, which may enhance the location accuracy of the second UE.

[0342] A third example of sidelink positioning 2145 is illustrated in FIG. 21. The third example of sidelink positioning 2145 may be performed via one or more sidelink connections (e.g., via sidelink connections exclusively or jointly with one or more Uu-based connections). In the third example of sidelink positioning 2145, the UEs may perform peer-to-peer (P2P) positioning or ranging. Sidelink positioning may be helpful for out-of-coverage or public safety scenarios. For instance, the UEs may be out of coverage of a network and may determine a location or a relative distance and a relative position among the UEs using sidelink positioning techniques. In some examples, sidelink positioning may be performed by UEs in public safety scenarios (e.g., for police, firefighters, search-and-rescue, or paramedics, among other examples).

[0343] A fourth example of sidelink positioning 2150 is illustrated in FIG. 21. The fourth example of sidelink positioning 2150 may be performed via one or more sidelinkAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO112connections (e.g., via sidelink connections exclusively or jointly with one or more Uu-based connections). In the fourth example of sidelink positioning 2150, one or more of the UEs may determine a location or a relative distance and a relative position using sidelink positioning techniques, such as SL-RTT. For instance, one or more of the UEs may be out of coverage of a network and may determine a location or a relative distance and a relative position among the UEs using sidelink positioning techniques.

[0344] An example of relay positioning 2155 is illustrated in FIG. 21. In the example of relay positioning 2155, a relay UE (e.g., with an established location) may participate in the location estimation of a remote UE (without performing uplink reference signal transmission over the Uu interface, for instance). For example, the relay UE may receive a downlink PRS from a TRP and may relay an SL-PRS to the remote UE. In some cases, the remote UE may also receive another downlink PRS from the TRP. A positioning device (e.g., location server, LMF, SLP, UE, or other device) may utilize a downlink PRS measurement and an SL-PRS measurement with the established location of the relay UE to estimate the location of the remote UE.

[0345] An example of joint positioning 2160 is illustrated in FIG. 21. In the example of joint positioning 2160, multiple peer UEs (without established locations, for instance) may be located. In some approaches, multiple peer UEs may be jointly located in NLOS conditions by utilizing one or more constraints from one or more peer (e.g., neighboring or nearby) UEs. As illustrated in FIG. 21, RTT or TDOA techniques may be performed between TRP1 and each of the peer UEs, may be performed between TRP2 and each of the peer UEs, and may be performed between the peer UEs. In some examples, one or more of the peer UEs may report measurements from the RTT or TDOA technique(s) to a positioning device. The positioning device (e.g., location server, LMF, SLP, UE, or other device) may utilize the measurements from the RTT or TDOA technique(s) to estimate the locations of the peer UEs.

[0346] Some aspects of the techniques described herein may be performed in conjunction with one or more of the positioning techniques described with reference to FIG. 21. For instance, one or more samples of a signal (e.g., PRS, SRS, or other signal) may be measured or transmitted in accordance with one or more of the techniques described with reference to FIG. 4 for one or more of the positioning techniques.Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO113

[0347] The following provides an overview of aspects of the present disclosure:

[0348] Aspect 1 : A method for wireless communications at a wireless device, comprising: receiving configuration information indicating a PPW identifier of a PPW and a periodicity of the PPW, wherein the configuration information indicates multiple window lengths within the periodicity of the PPW, and the PPW identifier is associated with the multiple window lengths; receiving, from at least one NTN node, a PRS in one or more of the multiple window lengths; and obtaining measurement information based at least in part on the PRS within a respective window length of the multiple window lengths.

[0349] Aspect 2: The method of aspect 1, wherein the configuration information indicates a first window length associated with the PPW identifier that is different from a second window length associated with the PPW identifier.

[0350] Aspect 3 : The method of any of aspects 1 through 2, wherein the configuration information indicates at least one gap between a pair of the multiple window lengths associated with the PPW identifier.

[0351] Aspect 4: The method of any of aspects 1 through 3, wherein the configuration information indicates different gaps between different pairs of the multiple window lengths associated with the PPW identifier.

[0352] Aspect 5: The method of any of aspects 1 through 4, further comprising: receiving control information indicating activation or deactivation of the PPW based at least in part on the PPW identifier of the PPW, wherein the activation or deactivation of the PPW corresponds to the multiple window lengths associated with the PPW identifier.

[0353] Aspect 6: The method of aspect 5, wherein the activation or deactivation of the PPW indicates activation or deactivation of the PPW that corresponds to the multiple window lengths on a BWP or a PFL.

[0354] Aspect 7: The method of any of aspects 5 through 6, further comprising: transmitting capability information indicating a quantity of PPW identifiers for concurrent activation supported by the wireless device, wherein the control information is received based at least in part on the capability information.Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO114

[0355] Aspect 8: The method of any of aspects 1 through 7, wherein a set of PPW identifiers comprises a first subset of PPW identifiers corresponding to PPWs for NTN positioning and a second subset of PPW identifiers corresponding to PPWs for TN positioning, and where the PPW identifier is included in the first subset of PPW identifiers for NTN positioning.

[0356] Aspect 9: The method of any of aspects 1 through 8, wherein the configuration information indicates that at least one of the multiple window lengths is greater than 160 slots.

[0357] Aspect 10: The method of any of aspects 1 through 9, further comprising: transmitting a request for the configuration information indicating the PPW identifier for NTN positioning, wherein the configuration information is received based at least in part on the request.

[0358] Aspect 11 : The method of aspect 10, further comprising: receiving an indication of a set of PPW identifiers, wherein the request for the configuration information is transmitted based at least in part on the set of PPW identifiers.

[0359] Aspect 12: The method of any of aspects 10 through 11, further comprising: receiving an indication of at least one parameter, comprising a downlink PPW identifier parameter, a downlink periodicity and start slot parameter, a length parameter, a type parameter, a priority parameter, or a combination thereof, wherein the request for the configuration information is based at least in part on the at least one parameter.

[0360] Aspect 13: The method of any of aspects 1 through 12, further comprising: receiving, from a network entity, an indication of a PPW parameter, a PPW drift parameter, and a PPW drift variation parameter to determine a time-varying start parameter or a time-varying duration parameter, wherein a start time of the PPW is based at least in part on the time-varying start parameter or a duration of the PPW is based at least in part on the time-varying duration parameter.

[0361] Aspect 14: The method of any of aspects 1 through 13, further comprising: receiving, from a network entity, an indication of a PPW parameter, a PPW drift parameter, and a PPW drift variation parameter to determine a time-varying start parameter or a time-varying duration parameter, wherein a start time of at least one ofAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO115the multiple window lengths is based at least in part on the time-varying start parameter or a duration of at least one of the multiple window lengths is based at least in part on the time-varying duration parameter.

[0362] Aspect 15: The method of any of aspects 1 through 14, wherein the configuration information indicates a priority for PRSs, and wherein receiving the PRS from the at least one NTN node is performed based at least in part on the priority.

[0363] Aspect 16: The method of any of aspects 1 through 15, wherein the configuration information indicates a priority for PRSs, and wherein obtaining the measurement information based at least in part on the PRS is performed based at least in part on the priority.

[0364] Aspect 17: The method of any of aspects 1 through 16, wherein the configuration information indicates a priority among the multiple window lengths, and wherein obtaining the measurement information based at least in part on the PRS is performed based at least in part on the priority.

[0365] Aspect 18: The method of any of aspects 1 through 17, wherein obtaining the measurement information based at least in part on the PRS is performed based at least in part on a priority among the multiple window lengths that is based at least in part on an order of the multiple window lengths.

[0366] Aspect 19: A method for wireless communications at a network entity, comprising: transmitting configuration information indicating a PPW identifier of a PPW and a periodicity of the PPW, wherein the configuration information indicates multiple window lengths within the periodicity of the PPW, and the PPW identifier is associated with the multiple window lengths; and receiving measurement information, the measurement information based at least in part on the PRS within a respective window length of the multiple window lengths.

[0367] Aspect 20: The method of aspect 19, wherein the configuration information indicates a first window length associated with the PPW identifier that is different from a second window length associated with the PPW identifier.Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO116

[0368] Aspect 21 : The method of any of aspects 19 through 20, wherein the configuration information indicates at least one gap between a pair of the multiple window lengths associated with the PPW identifier.

[0369] Aspect 22: The method of any of aspects 19 through 21, wherein the configuration information indicates different gaps between different pairs of the multiple window lengths associated with the PPW identifier.

[0370] Aspect 23: The method of any of aspects 19 through 22, further comprising: receiving capability information indicating a quantity of PPW identifiers for concurrent activation supported by a wireless device.

[0371] Aspect 24: The method of any of aspects 19 through 23, wherein a set of PPW identifiers comprises a first subset of PPW identifiers corresponding to PPWs for NTN positioning and a second subset of PPW identifiers corresponding to PPWs for TN positioning, and where the PPW identifier is included in the first subset of PPW identifiers for NTN positioning.

[0372] Aspect 25: The method of any of aspects 19 through 24, wherein the configuration information indicates that at least one of the multiple window lengths is greater than 160 slots.

[0373] Aspect 26: The method of any of aspects 19 through 25, further comprising: receiving a request for the configuration information indicating the PPW identifier for NTN positioning, wherein the configuration information is transmitted based at least in part on the request.

[0374] Aspect 27: The method of aspect 26, further comprising: transmitting an indication of a set of PPW identifiers, wherein the request for the configuration information is received based at least in part on the set of PPW identifiers.

[0375] Aspect 28: The method of any of aspects 26 through 27, further comprising: transmitting an indication of at least one parameter, comprising a downlink PPW identifier parameter, a downlink periodicity and start slot parameter, a length parameter, a type parameter, a priority parameter, or a combination thereof, wherein the request for the configuration information is based at least in part on the at least one parameter.Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO117

[0376] Aspect 29: The method of any of aspects 19 through 28, further comprising: transmitting, to a wireless device, an indication of a PPW parameter, a PPW drift parameter, and a PPW drift variation parameter to determine a time-varying start parameter or a time-varying duration parameter, wherein a start time of the PPW is based at least in part on the time-varying start parameter or a duration of the PPW is based at least in part on the time-varying duration parameter.

[0377] Aspect 30: The method of any of aspects 19 through 29, further comprising: transmitting, to a wireless device, an indication of a PPW parameter, a PPW drift parameter, and a PPW drift variation parameter to determine a time-varying start parameter or a time-varying duration parameter, wherein a start time of at least one of the multiple window lengths is based at least in part on the time-varying start parameter or a duration of at least one of the multiple window lengths is based at least in part on the time-varying duration parameter.

[0378] Aspect 31 : The method of any of aspects 19 through 30, wherein the configuration information indicates a priority for PRSs, and wherein receiving the measurement information based at least in part on the PRS is based at least in part on the priority.

[0379] Aspect 32: The method of any of aspects 19 through 31, wherein the configuration information indicates a priority among the multiple window lengths, and wherein receiving the measurement information based at least in part on the PRS is based at least in part on the priority.

[0380] Aspect 33 : A wireless device for wireless communications, comprising one or more transceivers, one or more memory, and one or more processors electronically coupled to the one or more memory and the one or more transceivers, the one or more processors configured to perform a method of any of aspects 1 through 18.

[0381] Aspect 34: A wireless device for wireless communications, comprising at least one means for performing a method of any of aspects 1 through 18.

[0382] Aspect 35: A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to perform a method of any of aspects 1 through 18.Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO118

[0383] Aspect 36: A network entity for wireless communications, comprising one or more transceivers, one or more memory, and one or more processors electronically coupled to the one or more memory and the one or more transceivers, the one or more processors configured to perform a method of any of aspects 19 through 32.

[0384] Aspect 37: A network entity for wireless communications, comprising at least one means for performing a method of any of aspects 19 through 32.

[0385] Aspect 38: A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to perform a method of any of aspects 19 through 32.

[0386] It should be noted that the methods described herein describe possible implementations. The operations and the steps may be rearranged or otherwise modified and other implementations are possible. Further, aspects from two or more of the methods may be combined.

[0387] Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communications systems such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, as well as other systems and radio technologies not explicitly mentioned herein.

[0388] Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0389] The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed using a general-purpose processor, a DSP, an ASIC, a CPU, a graphics processing unit (GPU), a neuralAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO119processing unit (NPU), an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor but, in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration). Any functions or operations described herein as being capable of being performed by a processor may be performed by multiple processors that, individually or collectively, are capable of performing the described functions or operations.

[0390] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as or transmitted using one or more instructions or code of a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.

[0391] Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Also, any connection is properlyAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO120termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc. Disks may reproduce data magnetically, and discs may reproduce data optically using lasers.Combinations of the above are also included within the scope of computer-readable media. Any functions or operations described herein as being capable of being performed by a memory may be performed by multiple memories that, individually or collectively, are capable of performing the described functions or operations.

[0392] As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.”

[0393] As used herein, including in the claims, the article “a” before a noun is open-ended and understood to refer to “at least one” of those nouns or “one or more” of those nouns. Thus, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” may be interchangeable. For example, if a claim recites “a component” that performs one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “a component” having characteristics or performing functions may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent reference to a component introduced with the article “a” using the terms “the” or “said” may refer to any or all of the one or more components. For example, a component introduced with the article “a” may be understood to mean “oneAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO121or more components,” and referring to “the component” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components.” Similarly, subsequent reference to a component introduced as “one or more components” using the terms “the” or “said” may refer to any or all of the one or more components. For example, referring to “the one or more components” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components.”

[0394] The term “determine” or “determining” encompasses a variety of actions and, therefore, “determining” can include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, a database, or another data structure), ascertaining, and the like. Also, “determining” can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), and the like. Also, “determining” can include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

[0395] In the appended figures, similar components or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If just the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label or other subsequent reference label.

[0396] The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims. The term “example” used herein means “serving as an example, instance, or illustration” and not “preferred” or “advantageous over other examples.” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some figures, known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO122

[0397] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.Attorney Docket No. PB0016GR.WO (114958.TBD)

Claims

Qualcomm Ref. No. 2407388WO123CLAIMSWhat is claimed is:

1. A wireless device, comprising:one or more transceivers;one or more memory; andone or more processors electronically coupled to the one or more memory and the one or more transceivers, the one or more processors configured to:receive configuration information indicating a positioning reference signal (PRS) processing window (PPW) identifier of a PPW and a periodicity of the PPW, wherein the configuration information indicates multiple window lengths within the periodicity of the PPW, and the PPW identifier is associated with the multiple window lengths;receive, from at least one non-terrestrial network (NTN) node, a PRS in one or more of the multiple window lengths; andobtain measurement information based at least in part on the PRS within a respective window length of the multiple window lengths.

2. The wireless device of claim 1, wherein the configuration information indicates a first window length associated with the PPW identifier that is different from a second window length associated with the PPW identifier.

3. The wireless device of claim 1, wherein the configuration information indicates at least one gap between a pair of the multiple window lengths associated with the PPW identifier.

4. The wireless device of claim 1, wherein the configuration information indicates different gaps between different pairs of the multiple window lengths associated with the PPW identifier.

5. The wireless device of claim 1, wherein the one or more processors are further configured to:receive control information indicating activation or deactivation of the PPW based at least in part on the PPW identifier of the PPW, wherein the activation orAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO124deactivation of the PPW corresponds to the multiple window lengths associated with the PPW identifier.

6. The wireless device of claim 5, wherein the activation or deactivation of the PPW indicates activation or deactivation of the PPW that corresponds to the multiple window lengths on a bandwidth part (BWP) or a positioning frequency layer (PFL).

7. The wireless device of claim 5, wherein the one or more processors are further configured to:transmit capability information indicating a quantity of PPW identifiers for concurrent activation supported by the wireless device, wherein the control information is received based at least in part on the capability information.

8. The wireless device of claim 1, wherein a set of PPW identifiers comprises a first subset of PPW identifiers corresponding to PPWs for NTN positioning and a second subset of PPW identifiers corresponding to PPWs for terrestrial network (TN) positioning, and where the PPW identifier is included in the first subset of PPW identifiers for NTN positioning.

9. The wireless device of claim 1, wherein the configuration information indicates that at least one of the multiple window lengths is greater than 160 slots.

10. The wireless device of claim 1, wherein the one or more processors are further configured to:transmit a request for the configuration information indicating the PPW identifier for NTN positioning, wherein the configuration information is received based at least in part on the request.

11. The wireless device of claim 10, wherein the one or more processors are further configured to:receive an indication of a set of PPW identifiers, wherein the request for the configuration information is transmitted based at least in part on the set of PPW identifiers.Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO12512. A network entity, comprising:one or more transceivers;one or more memory; andone or more processors electronically coupled to the one or more memory and the one or more transceivers, the one or more processors configured to:transmit configuration information indicating a positioning reference signal (PRS) processing window (PPW) identifier of a PPW and a periodicity of the PPW, wherein the configuration information indicates multiple window lengths within the periodicity of the PPW, and the PPW identifier is associated with the multiple window lengths; andreceive measurement information, the measurement information based at least in part on the PRS within a respective window length of the multiple window lengths.

13. The network entity of claim 12, wherein the one or more processors are further configured to:receive a request for the configuration information indicating the PPW identifier for NTN positioning, wherein the configuration information is transmitted based at least in part on the request.

14. The network entity of claim 13, wherein the one or more processors are further configured to:transmit an indication of a set of PPW identifiers, wherein the request for the configuration information is received based at least in part on the set of PPW identifiers.

15. The network entity of claim 13, wherein the one or more processors are further configured to:transmit an indication of at least one parameter, comprising a downlink PPW identifier parameter, a downlink periodicity and start slot parameter, a length parameter, a type parameter, a priority parameter, or a combination thereof, wherein the request for the configuration information is based at least in part on the at least one parameter.Attorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO12616. The network entity of claim 12, wherein the one or more processors are further configured to:transmit, to a wireless device, an indication of a PPW parameter, a PPW drift parameter, and a PPW drift variation parameter to determine a time-varying start parameter or a time-varying duration parameter, wherein a start time of the PPW is based at least in part on the time-varying start parameter or a duration of the PPW is based at least in part on the time-varying duration parameter.

17. The network entity of claim 12, wherein the one or more processors are further configured to:transmit, to a wireless device, an indication of a PPW parameter, a PPW drift parameter, and a PPW drift variation parameter to determine a time-varying start parameter or a time-varying duration parameter, wherein a start time of at least one of the multiple window lengths is based at least in part on the time-varying start parameter or a duration of at least one of the multiple window lengths is based at least in part on the time-varying duration parameter.

18. The network entity of claim 12, wherein:the configuration information indicates a priority for PRSs, and receiving the measurement information based at least in part on the PRS is based at least in part on the priority.

19. The network entity of claim 12, wherein:the configuration information indicates a priority among the multiple window lengths, andreceiving the measurement information based at least in part on the PRS is based at least in part on the priority.

20. A method for wireless communications at a wireless device, comprising:receiving configuration information indicating a positioning reference signal (PRS) processing window (PPW) identifier of a PPW and a periodicity of the PPW, wherein the configuration information indicates multiple window lengths withinAttorney Docket No. PB0016GR.WO (114958.TBD)Qualcomm Ref. No. 2407388WO127the periodicity of the PPW, and the PPW identifier is associated with the multiple window lengths;receiving, from at least one non-terrestrial network (NTN) node, a PRS in one or more of the multiple window lengths; andobtaining measurement information based at least in part on the PRS within a respective window length of the multiple window lengths.Attorney Docket No. PB0016GR.WO (114958.TBD)

Images