Collision resolution for positioning procedures

Abstract

Some wireless communications systems utilize reference signal (RS) measurements to generate a positioning estimate of a user equipment (UE). When RSs are received or measured, samples of the RSs may be collected or stored in a buffer. In some examples, a modem may support various functionalities simultaneously, with multiple tasks overlapping (e.g., ongoing at the same time). For instance, when a UE is performing buffer sample collection, one or more other tasks may arise. Due to the multiple modem scenarios that may conflict with buffering activity, an arbitration mechanism may be utilized to reduce or avoid modem performance impacts in accordance with some of the techniques described herein. For instance, some of the techniques described herein may be utilized to arbitrate buffer activity with other modem functions. Some examples of the techniques described herein may resolve collisions between a procedure and buffering data for a positioning procedure.

Description

Qualcomm Ref. No. 2404320WO1COLLISION RESOLUTION FOR POSITIONING PROCEDURESCROSS REFERENCE

[0001] The present Application for Patent claims priority to Greek Patent Application No. 20240100650 by PAL et al., entitled “COLLISION RESOLUTION FOR POSITIONING PROCEDURES,” filed September 24, 2024, which is assigned to the assignee hereof, and expressly incorporated by reference herein.FIELD OF TECHNOLOGY

[0002] The following relates to wireless communications, including collision resolution for positioning procedures.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).SUMMARY

[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.Attorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO2

[0005] A method by a wireless device is described. The method may include determining that a collision does not occur between a first temporal period for buffering data in association with a positioning procedure and a second temporal period for performing a procedure, or that a collision is resolved based on a collision resolution procedure, receiving a reference signal (RS) during an RS occasion, where reception of the RS triggers buffering the data in association with the positioning procedure, where a timing of the RS occasion prevents a collision or is based on the collision resolution procedure, and transmitting position information that is based on the data that is associated with the positioning procedure.

[0006] A wireless device 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 determine that a collision does not occur between a first temporal period for buffering data in association with a positioning procedure and a second temporal period for performing a procedure, or that a collision is resolved based on a collision resolution procedure, receive a RS during an RS occasion, where reception of the RS triggers one or more processors to buffer the data in association with the positioning procedure, where a timing of the RS occasion prevents a collision or is based on the collision resolution procedure, and transmit position information that is based on the data that is associated with the positioning procedure.

[0007] Another wireless device is described. The wireless device may include means for determining that a collision does not occur between a first temporal period for buffering data in association with a positioning procedure and a second temporal period for performing a procedure, or that a collision is resolved based on a collision resolution procedure, means for receiving a RS during an RS occasion, where reception of the RS triggers buffering the data in association with the positioning procedure, where a timing of the RS occasion prevents a collision or is based on the collision resolution procedure, and means for transmitting position information that is based on the data that is associated with the positioning procedure.

[0008] A non-transitory computer-readable medium storing code is described. The code may include instructions executable by one or more processors to determine that a collision does not occur between a first temporal period for buffering data in associationAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO3 with a positioning procedure and a second temporal period for performing a procedure, or that a collision is resolved based on a collision resolution procedure, receive a RS during an RS occasion, where reception of the RS triggers the one or more processors to buffer the data in association with the positioning procedure, where a timing of the RS occasion prevents a collision or is based on the collision resolution procedure, and transmit position information that is based on the data that is associated with the positioning procedure.

[0009] Some examples of the method, wireless devices, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for performing a multi -sub scriber identity module (MSIM) tune- away, where the MSIM tune-away may be the procedure, and where the collision resolution procedure includes scheduling the RS occasion after the second temporal period for performing the MSIM tune-away.

[0010] In some examples of the method, wireless devices, and non-transitory computer-readable medium described herein, the second temporal period may be a period of a sleep mode of the wireless device and the collision resolution procedure includes scheduling the RS occasion to at least partially overlap with an active mode of the wireless device.

[0011] In some examples of the method, wireless devices, and non-transitory computer-readable medium described herein, the second temporal period may be a period of a sleep mode of the wireless device and the collision resolution procedure includes scheduling the RS occasion during the period of the sleep mode based on the positioning procedure being associated with a first positioning type that provides increased accuracy or decreased latency relative to a second positioning type.

[0012] In some examples of the method, wireless devices, and non-transitory computer-readable medium described herein, the collision resolution procedure includes scheduling the RS occasion during the second temporal period based on a satisfaction of a threshold of time in which buffering the data that may be associated with the positioning procedure was not performed due to one or more procedures that conflicted with buffering the data.Attorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO4

[0013] In some examples of the method, wireless devices, and non-transitory computer-readable medium described herein, the collision resolution procedure includes scheduling the RS occasion previous to scheduling the procedure, the second temporal period for performing the procedure overlaps with a collision resolution window associated with buffering the data, and the procedure may be blocked.

[0014] Some examples of the method, wireless devices, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for performing a bandwidth part (BWP) switch, where the BWP switch may be the procedure, and where the collision resolution procedure includes scheduling the RS occasion after the second temporal period for performing the BWP switch.

[0015] Some examples of the method, wireless devices, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for performing a modem operation, where the modem operation may be the procedure, and where the collision resolution procedure includes scheduling the RS occasion after the second temporal period for performing the modem operation.

[0016] Some examples of the method, wireless devices, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for performing an antenna receive diversity (ARD) switch, where the ARD switch may be the procedure, and where the collision resolution procedure includes scheduling the RS occasion after the second temporal period for performing the ARD switch.

[0017] In some examples of the method, wireless devices, and non-transitory computer-readable medium described herein, the second temporal period may be a period of a procedure gap of the wireless device and the collision resolution procedure includes scheduling the RS occasion after the procedure gap of the wireless device.

[0018] In some examples of the method, wireless devices, and non-transitory computer-readable medium described herein, the second temporal period may be a period of a procedure gap of the wireless device and the collision resolution procedure includes scheduling the RS occasion during the period of the procedure gap based onAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO5 the positioning procedure being associated with a first positioning type that provides increased accuracy or decreased latency relative to a second positioning type.

[0019] Some examples of the method, wireless devices, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for performing a handover procedure or a cell reselection procedure, where the handover procedure or the cell reselection procedure may be the procedure, and where the collision resolution procedure includes scheduling the RS occasion after the second temporal period for performing the handover procedure or the cell reselection procedure.

[0020] In some examples of the method, wireless devices, and non-transitory computer-readable medium described herein, the RS occasion may be scheduled in a first slot with a lesser load than a second slot based on a modulation and coding scheme (MCS) or a code rate. 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

[0021] FIG. 1 shows an example of a wireless communications system that supports collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure.

[0022] FIG. 2 shows an example of a network structure that supports collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure.

[0023] FIG. 3 shows an example of a network architecture that supports collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure.

[0024] FIG. 4 shows an example of a wireless communications system that supports collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure.Attorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO6

[0025] FIG. 5 shows a flowchart illustrating a method that supports collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure.

[0026] FIG. 6 shows an example of a timing diagram that supports collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure.

[0027] FIG. 7 shows an example of a timing diagram that supports collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure.

[0028] FIG. 8 shows an example of a timing diagram that supports collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure.

[0029] FIG. 9 shows an example of a timing diagram that supports collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure.

[0030] FIG. 10 shows an example of a timing diagram that supports collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure.

[0031] FIG. 11 shows an example of a timing diagram that supports collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure.

[0032] FIG. 12 shows an example of a timing diagram that supports collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure.

[0033] FIG. 13 shows an example of a timing diagram that supports collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure.Attorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO7

[0034] FIG. 14 shows an example of a timing diagram illustrating examples of wireless device operations that support collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure.

[0035] FIG. 15 shows an example of a process flow that supports collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure.

[0036] FIGs. 16 and 17 show block diagrams of devices that support collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure.

[0037] FIG. 18 shows a block diagram of a communications manager that supports collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure.

[0038] FIG. 19 shows a diagram of a system including a device that supports collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure.

[0039] FIGs. 20 and 21 show flowcharts illustrating methods that support collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure.

[0040] FIG. 22 shows examples of wireless communications systems that support collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure.

[0041] FIG. 23 shows an example of a node diagram of an artificial intelligence (Al) model that supports collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure.

[0042] FIGs. 24A and 24B show examples of block diagrams that support collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure.Attorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO8

[0043] FIG. 25 shows examples of block diagrams that support collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure.DETAILED DESCRIPTION

[0044] Some wireless communications systems utilize reference signal (RS) samples or measurements to generate a positioning estimate of a user equipment (UE). When RSs are received or measured, samples of the RSs may be collected or stored in a buffer. For example, frequency domain samples of a tracking reference signal (TRS) may be collected in a buffer. The frequency domain buffer may store a collection of frequency domain samples of a TRS captured with global navigation satellite system (GNSS) time tagging and GNSS position fix tagging. The samples in the frequency domain buffer may be utilized for crowdsourcing information, for a forward positioning procedure, or for a reverse positioning procedure.

[0045] The collection of frequency domain samples may be intrusive to (e.g., may conflict with, collide with, disrupt, or be impacted by) some radio frequency (RF) procedures. For instance, a UE modem may support one or more RF procedures, such as a bandwidth part (BWP) switch, an antenna receive diversity (ARD) switch, a measurement gap (e.g., multi-subscriber identity module (MSIM) measurement gap or long tune-away (LTA) measurement gap), an MSIM tune-away, a sleep mode, or a modem operation (e.g., a modem operation that may impact or may be impacted by sample collection or buffering), among other examples. Accordingly, a relatively high probability exists that TRS frequency domain buffer collection may overlap with (e.g., occur concurrently with) one or more other modem functionalities.

[0046] In some examples, a modem may support various functionalities simultaneously, with multiple tasks overlapping (e.g., ongoing at the same time). For instance, when a UE is performing TRS frequency domain buffer sample collection, one or more other tasks (e.g., relatively high priority tasks) may arise, such as a BWP switch, ARD switch, MSIM gap measurement or tune-away, sleep mode, or a modem operation, among other examples. A BWP switch, ARD switch, or other switch) may be RF intrusive operations that may impact or may be impacted by sample collection. In some cases, an RF intrusive operation may not be stopped to allow TRS frequencyAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO9 domain buffer sample collection. Accordingly, having an RF intrusive operation occur during TRS frequency domain buffer sample collection may potentially affect modem performance or stability. Additionally, or alternatively, capturing TRS samples during a transition time may impact positioning performance, as TRS sample collection may rely on a settled automatic gain control (AGC) or other loop parameter. Improving positioning session accuracy, for example, may demand a converged loop parameter.

[0047] Due to the multiple modem scenarios that may conflict with buffering activity (e.g., TRS frequency domain buffering), an arbitration mechanism may be utilized to reduce or avoid modem performance impacts in accordance with some of the techniques described herein. For instance, some of the techniques described herein may be utilized to arbitrate buffer activity (e.g., TRS frequency domain buffer sample collection) with other modem functions. Because deprioritizing buffering (e.g., TRS frequency domain buffer data collection) may affect positioning procedures (e.g., tiers of positioning, such as a first positioning type that offers enhanced accuracy or reduced latency relative to a second positioning type), the arbitration mechanism may be utilized to manage scenarios in which buffer activity or other modem activity may be prioritized.

[0048] Some examples of the techniques described herein may resolve collisions between one or more procedures and buffering data for a positioning procedure. For example, one or more procedures may be performed and data buffering may be rescheduled, suspended, skipped, or aborted, which may avoid degrading the captured data due to unsettled receiver circuitry (e.g., loop parameters). Additionally, or alternatively, some of the techniques described herein may allow data buffering to be performed while blocking one or more other procedures that could degrade the captured data. In some approaches, a priority of data buffering may be initially lower than a priority of one or more other procedures. If data buffering is blocked or skipped (e.g., blocked or skipped repeatedly), the data buffering operation may increase in priority until the priority of the data buffering rises above the priority of one or more other procedures, which may allow data buffering to be performed in the midst of other relatively high priority procedures.

[0049] Aspects of the disclosure are initially described in the context of wireless communications systems. Aspects of the disclosure are also described in the context of aAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO10 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 a process flow. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, flowcharts, a node diagram, and block diagrams that relate to collision resolution for positioning procedures.

[0050] FIG. 1 shows an example of a wireless communications system 100 that supports signaling for sample-based position estimation 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 entities 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, a New Radio (NR) network, or a network operating in accordance with other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0051] The network entities 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 entity 105 may be referred to as a network element, a network node, a mobility element, a radio access network (RAN) node, or network equipment, among other nomenclature. In some examples, network entities 105 and UEs 115 may wirelessly communicate via communication link(s) 125 (e.g., a RF access link). For example, a network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) over which the UEs 115 and the network entity 105 may establish the communication link(s) 125. The coverage area 110 may be an example of a geographic area over which a network entity 105 and a UE 115 may support the communication of signals according to one or more radio access technologies (RATs).

[0052] 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 inAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO11 the wireless communications system 100 (e.g., other wireless communication devices, including UEs 115 or network entities 105), as shown in FIG. 1.

[0053] As described herein, a node of the wireless communications system 100, which may be referred to as a network node or a wireless node, may be a network entity 105 (e.g., any network entity 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 techniques described herein. For example, a node may be a UE 115. As another example, a node may be a network entity 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 entity 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 entity 105, and the third node may be another network entity 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 entity 105, apparatus, device, computing system, or the like may include disclosure of the UE 115, network entity 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 entity 105 also discloses that a first node is configured to receive information from a second node.

[0054] In some examples, network entities 105 may communicate with a core network 130, or with one another, or both. For example, network entities 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 entities 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 entities 105) or indirectly (e.g., via the core network 130). In some examples, network entities 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 fronthaulAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO12 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.

[0055] One or more of the network entities 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 radio transceiver, 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 entity 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 entity (e.g., a network entity 105 or a single RAN node, such as a base station 140).

[0056] In some examples, a network entity 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 entities 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 entity 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 transmission-reception point (TRP). One or more components of the network entities 105 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more of the networkAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO13 entities 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)).

[0057] 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 and a 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 interfaceAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO14(e.g., a channel) between layers of a protocol stack supported by respective network entities (e.g., one or more of the network entities 105) that are in communication via such communication links.

[0058] 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, in an IAB network, one or more of the network entities 105 (e.g., network entities 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 entity 105 or base station 140 (such as a donor network entity 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.

[0059] 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, inAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO15 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.

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

[0061] 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 toAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO16MT 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.

[0062] 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 entity 105 (e.g., a base station 140) may additionally, or alternatively, be performed by one or more components 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).

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

[0064] 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 entities 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.

[0065] The UEs 115 and the network entities 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 BWP) that is operated according to one or more PHY layer channels for a given RAT (e.g., LTE, LTE-A,Attorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO17LTE-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. Communication between a network entity 105 and other devices may refer to communication between the devices and any portion (e.g., entity, sub-entity) of a network entity 105. For example, the terms “transmitting,” “receiving,” or “communicating,” when referring to a network entity 105, may refer to any portion of a network entity 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 entities 105).

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

[0067] The communication link(s) 125 of the wireless communications system 100 may include downlink transmissions (e.g., forward link transmissions) from a network entity 105 to a UE 115, uplink transmissions (e.g., return link transmissions) from a UE 115 to a network entity 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).

[0068] 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 “systemAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO18 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 entities 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 entities 105 or UEs 115 that support concurrent communications using carriers 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.

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

[0070] 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.Attorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO19

[0071] The time intervals for the network entities 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 / mflx■ Ay) seconds, for which fmaxmay represent a supported subcarrier spacing, and Nf 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).

[0072] 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., Ay) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or frequency band of operation.

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

[0074] 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 ofAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO20 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 encoded information 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).

[0075] A network entity 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 entity 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 entity 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.

[0076] 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 entity 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 anAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO21 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 entity 105 may support one or more cells and may also support communications via the one or more cells using one or multiple component carriers.

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

[0078] In some examples, a network entity 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 entity (e.g., a network entity 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 entities 105). The wireless communications system 100 may include, for example, a heterogeneous network in which different types of the network entities 105 support communications for coverage areas 110 (e.g., different coverage areas) using the same or different RATs.

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

[0080] 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 allowAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO22 devices to communicate with one another or a network entity 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 and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.

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

[0082] 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 termsAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO23 ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.

[0083] 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 device-to-device (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 entity 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 entity 105. In some examples, one or more UEs 115 of such a group may be outside the coverage area 110 of a network entity 105 or may be otherwise unable to or not configured to receive transmissions from a network entity 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 entity 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 entity 105.

[0084] 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 nodes (e.g., network entities 105, base stations 140, RUs 170) using vehicle-to- network (V2N) communications, or with both.

[0085] 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 andAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO24 mobility (e.g., a mobility management entity (MME), an access and mobility management function (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 entities 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 150 may include access to the Internet, Intranet(s), an IP Multimedia Subsystem (IMS), or a Packet-Switched Streaming Service.

[0086] The wireless communications system 100 may include an LMF 185. The LMF 185 may provide positioning, location, or tracking functions. For instance, the LMF 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 LMF 185. For instance, measurements associated with reference signaling may be provided to the LMF 185, which may estimate a location of a UE 115 based on the measurements. In some aspects, the LMF 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 LMF 185.

[0087] The LMF 185 may be included in the core network 130 or may be separate from the core network 130. In some examples, an LMF 185 may be a standalone deviceAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO25 or may be included in (e.g., integrated with) a network entity 105, a base station 140, a UE 115, a satellite 190, a server, or another device. For instance, the LMF 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 LMF 185 may generally refer to a positioning device, a location device, a computing device, or a server, among other examples.

[0088] A UE 115 may communicate with the LMF 185 directly or indirectly. For example, a UE 115 may communicate with the LMF 185 via a network entity 105 that is serving the UE 115 and via the core network 130. Additionally, or alternatively, a UE 115 may communicate with the LMF 185 through another path (e.g., via an application server (not shown)) or via another network (e.g., via a WLAN AP), among other examples. Communication between a UE 115 and the LMF 185 may be represented via an indirect connection (e.g., through a communication link 125, a network entity 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.

[0089] 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 entities 105, or UEs 115 may transmit signals for enabling a UE 115 to determine a location.

[0090] 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., aAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO26 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.

[0091] 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 System (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.

[0092] In some aspects, the satellite(s) 190 may be included in one or more nonterrestrial networks (NTNs). In an NTN, a satellite 190 may communicate with one or more devices (e.g., network nodes, 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 entity 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 node.

[0093] 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 asAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO27 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.

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

[0095] 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. While operating using unlicensed RF spectrum bands, devices such as the network entities 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.

[0096] A network entity 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 asAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO28 transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of a network entity 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 network entity 105 may be located at diverse geographic locations. A network entity 105 may include an antenna array with a set of rows and columns of antenna ports that the network entity 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.

[0097] The network entities 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.

[0098] 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 entity 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 antennaAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO29 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 a beamforming 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).

[0099] A network entity 105 or a UE 115 may use beam sweeping techniques as part of beamforming operations. For example, a network entity 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, RSs, beam selection signals, or other control signals) may be transmitted by a network entity 105 multiple times along different directions. For example, the network entity 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 entity 105, or by a receiving device, such as a UE 115) a beam direction for later transmission or reception by the network entity 105.

[0100] Some signals, such as data signals associated with a particular receiving device, may be transmitted by a transmitting device (e.g., a network entity 105 or a UE 115) along a single beam direction (e.g., a direction associated with the receiving device, such as another network entity 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 entity 105 along different directions and may report to the network entity 105 an indication of the signal that the UE 115 received with a highest signal quality or an otherwise acceptable signal quality.

[0101] In some examples, transmissions by a device (e.g., by a network entity 105 or a UE 115) may be performed using multiple beam directions, and the device may useAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO30 a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from a network entity 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 entity 105 may transmit a RS (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (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 entity 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).

[0102] 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 entity 105), such as synchronization signals, RSs, 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), orAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO31 otherwise acceptable signal quality based on listening according to multiple beam directions).

[0103] 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 packet segmentation 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 entity 105 or a core network 130 supporting radio bearers for user plane data. A PHY layer may map transport channels to physical channels.

[0104] The UEs 115 and the network entities 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.

[0105] Some wireless communications systems 100 utilize measurements to generate a positioning estimate of a UE 115. The performance of positioning estimation using over-the-top (OTT) signaling (e.g., a CRS or a TRS in some cellular systems or a long training sequence (LTS) signal in Wi-Fi networks, among other examples) may be improved by utilizing a mapping framework that provides the UE or a network node (e.g., location server) with anchor position coordinates. The identifiers of anchors (e.g., cell identifiers (IDs) of TRPs in 5G cellular systems or a service set identifier (SSID) ofAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO32 an access point (AP) in Wi-Fi systems, among other examples) may be scrambled from time to time (e.g., once a day), which may add difficulties to computing a position without information indicating which anchor position corresponds to which signaling measurement. For instance, when using OTT signaling, a UE or a network node (e.g., location server) may combine measurements (e.g., time of arrival (ToA) measurements or time difference of arrival (TDoA) measurements, among other examples) with information regarding anchor positions to determine a reliable position estimate.

[0106] In some aspects, a UE or network node may access a list of ToA or TDoA estimates, a list of probable anchor positions, or a mapping. The list of ToA or TDoA estimates may be derived by the UE based on measurements used by the UE for UE- based position estimation or reported to the network node for network-based (e.g., location server-based) position estimation. The list of probable anchor positions may be provided by the network node to the UE (for UE-based positioning) and may indicate the positions of anchors in the surrounding region of the UE. The UE or network node may combine the information in the two lists using reverse positioning to determine the mapping from the ToA or TDoA measurements to the respective anchor positions. This information may be utilized for positioning.

[0107] A TRS is an example of an RS that may be utilized in one or more positioning procedures. In some examples, a TRS may be configured for one or more cells (e.g., at each cell), where each TRS may be configured with a corresponding time, frequency, or scrambling ID. Some networks (e.g., network entities 105 or UEs 115) may support the use of a TRS for positioning. In some approaches, a UE 115 may have configuration information for a TRS of a serving cell (e.g., may have configuration information for the TRS of only the serving cell). In some aspects, a UE 115 may have information indicating one or more resource elements (REs), slot number(s), OFDM symbol indices, inter-symbol distance (e.g., 4 OFDM symbols), TRS burst periodicity (e.g., 10 ms, 20 ms, 40 ms, or 80 ms), TRS subcarrier distance (e.g., 4 subcarriers), or a TRS subcarrier offset for a TRS. For instance, a one or two slot burst may be utilized per TRS burst in the TRS burst periodicity. In some examples, one or more symbol pair positions (e.g., (4,8), (5,9), and (6,10)) in a resource grid (e.g., a time and frequency grid or resource block) may be allowed for frequency range 1 (FR1). Additionally, or alternatively, any symbol pair position within a slot with an inter-symbol distance of 4Attorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO33 may be allowed for frequency range 2 (FR2). In some examples, a TRS may not be fully staggered in frequency. For instance, a comb-4 channel energy response (CER) aliasing issue may occur where 4 peaks may occur in the CER and a detected strongest peak may not corresponding to the true peak. In some approaches, a TRS may be quasi-colocated (QCL-ed) with a synchronization signal block (SSB) from a neighboring cell, which may also be measured for the purpose of solving the time-domain aliasing issue.

[0108] In some examples, a UE 115 may perform one or more operations to collect one or more TRSs for OTT positioning. For instance, a terrestrial location daemon may receive a position request. The daemon may request a data connection and may request measurements from a session manager. If the session manager determines that the UE 115 is connected (e.g., in CONNECTED mode for a 5G-NR network), the session manager may request access to a buffer (e.g., a frequency domain buffer). If access to the buffer is provided, the session manager may request and receive auxiliary location data (if available). The session manager may request and receive cell identifier (e.g., E- CID) data. The session manager may prepare a data payload, which may include buffer data (e.g., frequency domain buffer data), cell identifier data, or auxiliary location data, which may be provided to the daemon. The daemon may encode and send a position request (e.g., for a position based on inter-cell TRS (TRS-IC) with fallback on E-CID), and may receive position data. The position data may be decoded and sent.

[0109] An example of TRS-based OTT positioning is provided as follows. A client (e.g., wireless device or UE 115) may report one or more TRS parameters of a serving cell (e.g., time, frequency, scrambling, QCL, or physical cell identity (PCI), among other examples) to a network node (e.g., network entity 105, location server, or LMF 185, among other examples). The client may report one or more neighboring cell PCIs derived through a radio resource management (RRM) procedure. The network node may respond with TRS information corresponding to one or more neighboring cells (which may have been obtained via reporting from one or more other UEs 115). The client (e.g., wireless device or UE 115) may report a location (e.g., position), one or more measurements, or TRSs that were detected (based on the TRS information, for instance) to the network node.

[0110] A TRS-based positioning procedure may be based on timing. For example, a UE 115 may measure the ToA for a serving cell and one or more neighboring cells. TheAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO34UE 115 may utilize the ToA measurements to estimate a location or position of the UE 115. The ToA measurement accuracy may be directly proportional to a bandwidth for processing signals. For instance, a 100 MHz signal may have better ToA accuracy compared to a 20 MHz signal.[OHl] When RSs (e.g., OTT signals) are received or measured, samples of the RSs may be collected or stored in a buffer. In some examples, frequency domain samples of a TRS may be collected in a buffer. For instance, a frequency domain buffer may store a collection of frequency domain samples of a TRS captured with GNSS time tagging and GNSS position fix tagging. The samples in the frequency domain buffer may be utilized for crowdsourcing information, for a forward positioning procedure(s), or for a reverse positioning procedure(s). A network node (e.g., a network entity 105, location server, or LMF 185, among other examples) may utilize the crowdsourced information by the UEs 115 to estimate the positions of cell towers (for reverse positioning or BSA information). For instance, BSA information may be utilized to compute the UE 115 positioning (e.g., for forward positioning or UE-A positioning). From a network perspective, the TRS may be configured with a periodicity, duration, or offset. A UE 115 may find a TRS periodic location and collect frequency domain samples. In some examples, the frequency of the TRS (e.g., a periodicity of 20 ms or 40 ms, among other examples) may be greater than is sufficient for a position session. In single shot positioning, for example, a UE 115 may have multiple occasions from which to select a TRS occasion (e.g., a “best” TRS occasion).

[0112] The collection of frequency domain samples may be intrusive to (e.g., may conflict with, collide with, or disrupt) some RF operations or functions. For instance, a UE 115 modem may support one or more functions, such as a BWP switch, an ARD switch, a measurement gap (e.g., MSIM measurement gap or LTA measurement gap), an MSIM tune-away, a sleep mode (e.g., connected mode discontinuous reception (CDRX)), or a (e.g., another) modem operation, among other examples. Accordingly, a relatively high probability exists that TRS frequency domain buffer collection may overlap with (e.g., occur concurrently with) one or more other modem functionalities.

[0113] In some examples, a modem may support various functionalities simultaneously, with multiple tasks overlapping (e.g., ongoing at the same time). For instance, when a UE 115 is performing TRS frequency domain buffer sample collection,Attorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO35 one or more other tasks (e.g., relatively high priority tasks) may arise, such as a BWP switch, ARD switch, MSIM gap measurement or tune-away, or sleep mode, among other examples. A BWP switch (via RRC reconfiguration or downlink control information (DCI)-based messaging, for example), ARD switch, or other switch may be RF operations that are intrusive to sample collection. In some cases, an RF intrusive operation may not be stopped to allow TRS frequency domain buffer sample collection. Accordingly, having an RF intrusive operation occur during TRS frequency domain buffer sample collection may potentially affect modem performance or stability. Additionally, or alternatively, capturing TRS samples during a transition time may impact positioning performance, as TRS sample collection may rely on a settled AGC or other loop parameter. Improving positioning session accuracy, for example, may demand a converged loop parameter. Million instructions per second (MIPS) loading may be another factor that could affect TRS sample collection during the transition time. When a tune-away gap occurs for MSIM, a modem may complete the MSIM tune- away first, because another activity (e.g., TRS frequency domain buffering) may potentially affect MSIM performance. Power consumption may also be a significant factor. For instance, if a UE enters an active mode (e.g., wakes up) during a sleep mode (e.g., CDRX deep sleep) to perform TRS frequency domain buffering, the overall sleep timeline may be impacted, which may increase power consumption.

[0114] Due to the multiple modem scenarios that may conflict with buffering activity (e.g., TRS frequency domain buffering), an arbitration mechanism may be utilized to reduce or avoid modem performance impacts in accordance with some of the techniques described herein. For instance, some of the techniques described herein may be utilized to arbitrate buffer activity (e.g., TRS frequency domain buffer sample collection) with other modem functions. Because deprioritizing buffering (e.g., TRS frequency domain buffer data collection) may affect positioning procedures (e.g., tiers of positioning, such as a first positioning type that offers enhanced accuracy or reduced latency relative to a second positioning type), the arbitration mechanism may be utilized to manage scenarios in which buffer activity or other modem activity may be prioritized.

[0115] FIG. 2 shows an example of a network structure 200 (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that supports collisionAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO36 resolution for positioning procedures 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 185-a, 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 185-a may be an example of the LMF 185, as described with reference to FIG. 1.

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

[0117] 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, transport 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) (not shown in FIG. 2), or security anchor functionality (SEAF) (not shown in FIG. 2), among other examples. In some aspects, the AMF 210 may interact with an authentication server function (AUSF) (not shown in FIG. 2) 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 contextAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO37 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 185-a, transport for location services messages between the RAN 225 and the LMF 185-a, 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.

[0118] 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 (not shown in FIG. 2), 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.

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

[0120] 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 entities 105 described with reference to FIG. 1. For instance, a next generation RAN (NG-RAN)Attorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO38 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.

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

[0122] The LMF 185-a 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 185-a may be an example of the LMF 185 described with reference to FIG. 1. The LMF 185-a 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 LMF 185-a may support one or more location services for one or more UEs 115-a that may connect to the LMF 185-a via the RAN 225, via the core network 130-a, or via another connection (e.g., the Internet). In some examples, the LMF 185-a 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 185-a 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).Attorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO39

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

[0124] In some examples, the external device 230 may communicate with the LMF 185-a, 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).

[0125] 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 mayAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO40 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.

[0126] FIG. 3 shows an example of a network architecture 300 (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that supports collision resolution for positioning procedures 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 entities 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.

[0127] Each of the network entities 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 orAttorney Docket No. PB0004GR.WO (114958.5168)Qualcomm Ref. No. 2404320WO41 transmit signals (e.g., data, information) via a wired or wireless transmission medium. Each network entity 105, or an associated processor (e.g., controller) providing instructions to an interface of the network entity 105, may be configured to communicate with one or more of the other network entities 105 via the transmission medium. For example, the network entities 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 entities 105. Additionally, or alternatively, the network entities 105 may include a wireless interface, which may include a receiver, a transmitter, or transceiver (e.g., an RF transceiver) configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other network entities 105.

[0128] 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 0-RAN configuration. A CU 160-b may be implemented to communicate with a DU 165-b, as necessary, for network control and signaling.

[0129] 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.Attorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO42

[0130] 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 communication 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.

[0131] The SMO 180-a may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network entities 105. For non-virtualized network entities 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 entities 105, the SMO 180-a may be configured to interact with a cloud computing platform (e.g., an O-Cloud 305) to perform network entity life cycle management (e.g., to instantiate virtualized network entities 105) via a cloud computing platform interface (e.g., an 02 interface). Such virtualized network entities 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.

[0132] 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 to or communicate with (e.g., viaAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO43 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.

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

[0134] FIG. 4 shows an example of a wireless communications system 400 that supports collision resolution for positioning procedures 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, which may be an example of a UE 115, network entity 105, RU 170, DU 165, or CU 160 described with reference to FIG. 1, a UE 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 node 405, which may be an example of a network entity 105, LMF 185, RU 170, DU 165, or CU 160 described with reference to FIG. 1, an LMF 185-a, 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.

[0135] The wireless device 415 may communicate with the network node 405 using a link 425, which may be an example of a communication link 125, a backhaulAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO44 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, or another link. The link 425 may include a bi-directional link that enables uplink or downlink network communications. For example, the wireless device 415 may transmit one or more uplink transmissions 410, such as uplink control signals or uplink data signals, to the network node 405 using the link 425. Additionally, or alternatively, the network node 405 may transmit one or more downlink transmissions 420, such as downlink control signals or downlink data signals, to the wireless device 415 using the link 425.

[0136] The wireless device 415 may determine that a collision does not occur between a first temporal period for buffering data in association with a positioning procedure and a second temporal period for performing a procedure. Or, the wireless device 415 may determine that a collision is resolved based at least in part on a collision resolution procedure.

[0137] The first temporal period for buffering the data may be a time period in which the data that is based on a RS 435 may be stored in (e.g., written to) the buffer 430 or scheduled for buffering. The second temporal period for performing a procedure may be a time period in which a procedure may be performed or scheduled to be performed. In some aspects, the procedure may be a procedure that may impact (e.g., be intrusive to, conflict with, collide with, or disrupt) buffering the data. Buffering the data may be impacted if buffering the data while the procedure is being performed would impact the quality, timing, or accuracy of the buffered data. Examples of a procedure that may impact buffering the data may include a BWP switch, ARD switch, measurement gap (e.g., MSIM measurement gap or LTA measurement gap), MSIM tune-away, sleep mode (e.g., CDRX), handover, or cell reselection, among other examples.

[0138] The wireless device 415 may determine that a collision between the first temporal period and the second temporal period may not occur if the first temporal period and the second temporal period do not overlap (e.g., do not partially or completely overlap) in time, or if the first temporal period and the second temporalAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO45 period are scheduled in non-overlapping time periods. For instance, the wireless device 415 may determine or receive scheduling information (e.g., transmitted from the network node) indicating the first temporal period (e.g., a period in which the RS 435 may be transmitted or received or in which the wireless device 415 may buffer the data based on the RS 435) or the second temporal period (e.g., a period for performing one or more of the procedures described herein). If the first temporal period and the second temporal period do not overlap, the wireless device 415 may determine that no collision may occur (e.g., occurs or will occur). In a case that the wireless device 415 determines that no collision may occur, for example, the wireless device 415 may buffer the data and perform the procedure (in separate time periods, for instance).

[0139] A collision between the first temporal period and the second temporal period may occur if the first temporal period and the second temporal period overlap (e.g., partially or completely overlap) in time, or if the first temporal period and the second temporal period are scheduled or planned to overlap (e.g., partially or completely overlap) in time. In some approaches, the wireless device 415 may determine that a collision may occur if the first temporal period and the second temporal period overlap. In some aspects, the wireless device 415 may perform a collision resolution procedure to determine whether a collision is resolved.

[0140] The collision resolution procedure may be one or more operations to determine whether to buffer the data or perform the procedure. For instance, the collision resolution procedure may be performed by the wireless device 415 to determine whether to perform (e.g., arbitrate or prioritize) buffering the data or the procedure (e.g., BWP switch, ARD switch, measurement gap, MSIM tune-away, sleep mode, handover, or cell reselection, among other examples). In some approaches, the wireless device 415 (e.g., modem of the wireless device 415) may check one or more procedures (e.g., modem functionalities). Based on the check, the wireless device 415 (e.g., modem) may select between a buffer (e.g., frequency domain buffer) collection activity and a procedure (e.g., other modem functionality). Additionally, or alternatively, the wireless device 415 (e.g., modem) may determine between buffering data and the procedure based on a positioning type. For instance, the determination may be based on whether a positioning procedure is associated with a first positioning typeAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO46(e.g., “premium” positioning) that provides increased accuracy or decreased latency relative to a second positioning type (e.g., regular positioning).

[0141] In some approaches, a collision may be resolved by the collision resolution procedure if the wireless device 415 determines to perform buffering the data or the procedure in non-overlapping periods or in overlapping (e.g., partially or completely overlapping periods). In some cases, the wireless device 415 may determine to suspend, skip, abort, or postpone buffering the data and perform the procedure (e.g., resolve the collision). In other cases, the 415 may determine to suspend, skip, abort, or postpone the procedure and perform buffering the data (e.g., resolve the collision). For instance, the wireless device 415 may buffer the data by prioritizing the data over the procedure, or may buffer the data after performing the procedure.

[0142] The network node 405 may output (e.g., transmit), or the wireless device 415 may obtain (e.g., receive) an RS 435 during an RS occasion. The RS 435 may be a signal (e.g., electromagnetic signal, RF signal) with one or more established characteristics (e.g., signaling pattern, strength, amplitude, magnitude, frequency, timing, modulation, phase, or data, among other examples). For instance, the wireless device 415 or the network node 405 may store information indicating one or more of the characteristics of the RS 435, which may allow for comparison of one or more stored characteristics and one or more characteristics of the received RS 435. The RS 435 (e.g., the comparison) may enable channel estimation (e.g., channel attenuation, phase, frequency shift, or Doppler effects, among other examples), positioning, or tracking. Examples of the RS 435 may include a TRS, a CRS, an LTS signal, an RS of an SSB, a channel state information reference signal (CSI-RS), a positioning reference signal (PRS), a sounding reference signal (SRS), or a demodulation reference signal (DMRS), among other examples.

[0143] An RS occasion may be a time period in which the RS 435 may be received or a time period in which data based on the RS 435 may be obtained. For instance, an RS occasion may be (e.g., may include or correspond to) a slot(s), subslot(s), TTI(s), window(s), or other time period(s) in which the RS 435 is received.

[0144] Reception of the RS 435 may trigger the wireless device 415 (e.g., one or more processors) to buffer data. For instance, the wireless device 415 may storeAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO47 samples, measurements, or other data based on the RS 435 in a buffer 430. The buffer 430 may be a memory or a subset of memory. In some examples, the buffer 430 may be memory that is included in, or accessible to, a modem of the wireless device 415.

[0145] In some approaches, a timing of the RS occasion may prevent a collision or may be based on a collision resolution procedure. For instance, the timing of the RS occasion may prevent a collision if the RS occasion occurs at a time that would avoid an overlap between the first temporal period (e.g., for buffering data) and the second temporal period (e.g., for performing the procedure). In some aspects, the timing of the RS occasion may be based on a collision resolution procedure (applied to a collision between a first temporal period for buffering the data and a second temporal period for performing a procedure, for example). For instance, a timing of the RS occasion may be prioritized over a procedure, scheduled after the second postponed for the procedure, skipped for the procedure, or aborted for the procedure.

[0146] In some examples, the data buffering may be performed in association with a positioning procedure. For instance, the RS may be requested, configured, measured or sampled as part of a positioning procedure (e.g., a procedure to determine a position of an object, such as the wireless device 415). In some examples, the RS or data buffering may not be associated with a positioning procedure. For instance, the RS may be communicated and data based on the RS may be buffered in association with a channel estimation procedure separate from a positioning procedure.

[0147] The wireless device 415 may output (e.g., transmit), or the network node 405 may obtain (e.g., receive) position information 440 that is based on the data that is associated with the positioning procedure. Examples of position information 440 may include a measurement s) or a position estimate(s). For example, based on the buffered data, the wireless device 415 may perform one or more positioning procedures (e.g., one or more operations of A-GNSS positioning, OTDOA positioning, E-CID positioning, sensor-based positioning, WLAN-based positioning, Bluetooth-based positioning, TBS positioning, DL-TDOA positioning, DL-AoD positioning, Multi-RTT positioning, NR E-CID positioning, UL-TDOA positioning, UL-AoA positioning, or AI / ML-based positioning, among other examples) to generate measurements or a position (e.g., position estimate or location estimate). Examples of positioning procedures are described with reference to FIG. 22.Attorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO48

[0148] In some examples, the wireless device 415 may generate measurements based on the RS 435. For instance, the wireless device 415 may measure a signal strength of the RS 435 at one or more times to generate the measurements. Examples of the measurements may include signal strength data, reference signal received power (RSRP) data, reference signal received path power (RSRPP) data, received signal strength indicator (RSSI) data, reference signal received quality (RSRQ) data, signal-to- interference plus noise ratio (SINR) data, SNR data, channel impulse response (CIR) data, power delay profile (PDP) data, delay profile (DP) data, channel quality indicator (CQI) data, or channel state information (CSI) data, among other examples. In some approaches, the wireless device 415 may derive the measurement s) as a CIR, PDP, or DP. For example, the wireless device 415 may determine (e.g., calculate) a channel frequency response (CFR) or a CER. In some examples, a CFR may be determined by applying channel estimation in the frequency domain based on the RS 435 (e.g., PRS) sequence mapped to one or more OFDM signals. In some aspects, the wireless device 415 may determine the CIR based on the CFR. For instance, the wireless device 415 may apply an inverse Fourier transform to the CFR (e.g., CIR = ifft(CFR), where ifft() denotes an inverse fast Fourier transform). The wireless device 415 may transmit the position information 440 (e.g., measurement s) or position(s)) to the network node 405.

[0149] In some aspects, an MSIM tune-away may be the procedure. MSIM tune- away may include tuning the wireless device 415 from communicating with a first RAT or network to communicating with a second RAT or network. In MSIM tune-away, one or more components (e.g., RF front-end (RFFE), filter(s), switch(es), antenna(s), or power amplifier(s), among other examples) may be tuned to a different frequency band(s), transmission power(s), or processing speed to communicate with the second RAT or network. In some approaches, the wireless device 415 may perform an MSIM tune-away, and the collision resolution procedure may include scheduling the RS occasion after the second temporal period for performing the MSIM tune-away. For example, the wireless device 415 may schedule the RS occasion after the second temporal period by skipping one or more occasions for receiving an RS or postponing buffering data until after the second temporal period. An example of a collision resolution procedure for MSIM tune-away is provided with reference to FIG. 8.Attorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO49

[0150] In some examples, the second temporal period may be a period of a sleep mode of the wireless device 415. For instance, a sleep mode may be a mode of operation where the wireless device 415 may reduce activity, shut down, or suspend one or more operations (e.g., to conserve energy). In some aspects, a sleep mode may occur when the wireless device 415 is in a CDRX mode. The wireless device 415 may enter the sleep mode (e.g., a reduced activity state) and occasionally (e.g., periodically or based on the reception of a wake-up signal (WUS)) enter an active mode (e.g., “awake” state). In some approaches, one or more levels of sleep modes may be performed. For instance, a second sleep mode (e.g., “deep sleep”) may permit fewer activities or operations than a first sleep mode. The collision resolution procedure may include scheduling the RS occasion to at least partially overlap with an active mode of the wireless device 415. Examples of scheduling the RS occasion to at least partially overlap with an active mode is given with reference to FIG. 6 and FIG. 9.

[0151] In some approaches, a procedure (e.g., task) such as MSIM tune-away or sleep mode may be a relatively high priority task or may be controlled by one or more layer 1 (LI) operations or components. In some cases, the priority of MSIM tune-away or sleep mode may be higher than buffering the data (e.g., a TRS frequency domain buffer capture task). When a first temporal period (e.g., an occasion for buffering data) occurs, the wireless device 415 (e.g., modem) may determine whether MSIM tune-away or sleep mode is ongoing. In a case that MSIM tune-away or sleep mode has a higher priority, the wireless device 415 (e.g., modem) may schedule the RS occasion (e.g., TRS frequency domain buffer collection activity) to a timing associated with a later RS 435 (e.g., a next time for TRS communication).

[0152] In some examples, the collision resolution procedure may include scheduling the RS occasion during the second temporal period based on a satisfaction of a threshold of time in which buffering the data that is associated with the positioning procedure was not performed due to one or more procedures that conflicted with buffering the data. For instance, if one or more procedures (e.g., MSIM tune-away, sleep mode, or a relatively high priority procedure) prevent or delay buffering the data (e.g., frequency domain buffer collection activity) for a threshold of time (e.g., a threshold period in the modem, 250 ms, 500 ms, 1 second, 2 seconds, or 5 seconds among other examples), then theAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO50 priority of buffering the data (e.g., TRS frequency domain buffer capturing) may be increased or prioritized over one or more procedures (e.g., other modem functionalities).

[0153] In some aspects, the RS occasion may be scheduled based on a positioning type. For instance, a first positioning type may provide increased accuracy or decreased latency relative to a second positioning type. In an example, the second temporal period may be a period of a sleep mode of the wireless device 415. The collision resolution procedure (e.g., arbitration) may include scheduling the RS occasion during the period of the sleep mode based on the positioning procedure being associated with the first positioning type.

[0154] In some examples, the collision resolution procedure may include scheduling the RS occasion previous to scheduling the procedure. The procedure may be blocked where the second temporal period for performing the procedure overlaps with a collision resolution window associated with buffering the data. For example, buffering the data (e.g., TRS frequency domain buffer collection activity) may be an RF intrusive operation and may be handled by a grant manager. A grant manager may be an operation or component of a modem that may perform one or more aspects of the collision resolution procedure. In some aspects, the grant manager may set a collision resolution window for a procedure or buffering the data to prioritize the procedure or buffering the data. In some examples, if buffering the data (e.g., a TRS frequency domain buffer collection activity) does not initially collide with a procedure (e.g., other modem functionality), then a collision resolution window may be set (e.g., may correspond to the first temporal period or the first temporal period and a margin). If the second temporal period for performing the procedure overlaps with the collision resolution window, the procedure may be blocked. For instance, if TRS frequency buffer collection is scheduled for over-the-air (OTA) activity before a procedure (e.g., before a BWP switch or ARD switch is scheduled), where the TRS frequency buffer collection temporal period and the procedure temporal period overlap, then an LI (e.g., LI downlink) operation or component may submit an indicator (e.g., vote) to the grant manager for the TRS frequency domain buffer collection activity. The grant manager may set a collision resolution window where the modem performs the TRS frequency domain buffer collection activity and other procedures (e.g., ARD switch, BWP switch, or a modem operation) may be blocked during the collision resolution window.Attorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO51

[0155] In some approaches, a BWP switch may be the procedure. A BWP switch may include switching a BWP for communication. For example, the wireless device 415 may tune one or more components (e.g., an RFFE, filter(s), switch(es), antenna(s), or power amplifier(s), among other examples) to a different frequency band(s) for communication. The wireless device 415 may perform the BWP switch. The collision resolution procedure may include scheduling the RS occasion after the second temporal period for performing the BWP switch.

[0156] In some examples, a modem operation (e.g., a modem operation that may impact or may be impacted by sample collection or buffering) may be the procedure. The wireless device 415 may perform the modem operation. The collision resolution procedure may include scheduling the RS occasion after the second temporal period for performing the modem operation.

[0157] In some examples, an ARD switch may be the procedure. An ARD switch may include switching one or more antennas (e.g., changing an antenna quantity or switching to a different antenna(s)) for communication. For instance, an ARD switch may include switching from two receive antennas to four receive antennas, or switching from four receive antennas to two receive antennas. The wireless device 415 may perform the ARD switch. The collision resolution procedure may include scheduling the RS occasion after the second temporal period for performing the ARD switch. An example of the collision resolution procedure is provided with reference to FIG. 7.

[0158] In some cases, one or more procedures (e.g., BWP switch or ARD switch, among other examples) may be already scheduled in the second temporal period for one or more OTA system frame numbers (SFNs), where the first temporal period for buffering the data (e.g., TRS frequency domain buffer collection) is targeted or overlaps with the second temporal period. Additionally, or alternatively, the first temporal period for buffering the data (e.g., TRS frequency domain buffer collection) may be targeted within a second temporal period for connected mode or idle mode deep sleep. In these cases, the procedure(s) may be prioritized and performed, while buffering the data may be postponed.

[0159] In some cases, the first temporal period for buffering the data (e.g., TRS frequency domain buffer collection) may be scheduled for one or more OTA SFNsAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO52 before a procedure is scheduled. In this case, the procedure (e.g., BWP switch or ARD switch, among other examples) may be suspended. Because a BWP switch, ARD switch, or another modem operation may be RF intrusive operations, the wireless device 415 (e.g., modem) may suspend those procedures when the wireless device 415 buffers the data. The procedure(s) may have an opportunity to be performed after buffering the data is performed.

[0160] In some approaches, the second temporal period is a period of a procedure gap of the wireless device 415. Examples of a procedure gap may include a measurement gap, MSIM LTA gap, or another gap. The collision resolution procedure may include scheduling the RS occasion after the procedure gap of the wireless device 415. Examples of the collision resolution procedure where the RS occasion is aborted during the gap are given with reference to FIG. 10.

[0161] In some examples, the second temporal period may be a period of a procedure gap of the wireless device 415. The collision resolution procedure may include scheduling the RS occasion during the period of the procedure gap based on the positioning procedure being associated with a first positioning type that provides increased accuracy or decreased latency relative to a second positioning type. Examples of the collision resolution procedure where the RS occasion is scheduled during the gap are given with reference to FIG. 11.

[0162] In some aspects, a handover procedure or a cell reselection procedure may be the procedure. The wireless device 415 may perform the handover procedure or the cell reselection procedure. The collision resolution procedure may include scheduling the RS occasion after the second temporal period for performing the handover procedure or the cell reselection procedure. Examples of the collision resolution procedure where the RS occasion is aborted during the handover procedure or cell reselection procedure are given with reference to FIG. 12.

[0163] In some examples, the RS occasion may be scheduled in a first slot with a lesser load than a second slot based on a modulation and coding scheme (MCS) or a code rate. For instance, based on an MCS or code rate, the wireless device 415 may select a slot with a lesser load for the RS occasion. An example of scheduling the RS occasion based on slot load (e.g., MCS or code rate) is give with reference to FIG. 13.Attorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO53

[0164] FIG. 5 shows a flowchart illustrating a method 500 that supports collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure. One or more of the operations described with reference to the method 500 may be performed by a wireless device, which may be an example of a UE 115, UE 115-a, UE 115-b, or wireless device 415, as described herein.

[0165] In the following description of the method 500, one or more of the operations may be performed in a different order than the example order shown, or may be performed in different orders or at different times. One or more operations may be omitted from the method 500, or one or more other operations may be added to the method 500. Although some operations may be shown to occur at different times, these operations may actually occur at the same time or in overlapping time periods in some examples. In the example of FIG. 5, one or more procedures (e.g., modem functionalities), such as BWP switch, ARD switch, MSIM tune-away, or CDRX deep sleep may be given priority over data buffering (e.g., TRS frequency domain buffer collection).

[0166] At 505, the method may include determining whether a DCI based or RRC configured BWP switch collides with a TRS occasion. For instance, the wireless device may check to determine whether a BWP switch is triggered, or may determine whether a second temporal period for performing the BWP switch collides with a first temporal period for buffering the data as described with reference to FIG. 4.

[0167] At 510, if the BWP switch collides with the TRS occasion, the method may include performing the BWP switch and may include scheduling data buffering (e.g., TRS frequency domain buffer collection) for a later (e.g., next) TRS occasion. For instance, the wireless device may schedule buffering the data at (e.g., may postpone, skip, or abort buffering the data until) a later TRS occasion (e.g., after collision) as described with reference to FIG. 4.

[0168] At 515, if the BWP switch does not collide with the TRS occasion, the method may include determining whether an ARD switch collides with a TRS occasion. For instance, the wireless device may check to determine whether an ARD switch is occurring, or may determine whether a second temporal period for transitioning between different quantities of antennas (e.g., from 2 Rx antennas to 4 Rx antennas, orAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO54 from 4 Rx antennas to 2 Rx antennas) collides with a first temporal period for buffering the data (e.g., during a TRS occasion) as described with reference to FIG. 4.

[0169] At 520, if the ARD switch collides with the TRS occasion, the method may include aborting data buffering (e.g., current frequency domain buffer activity) and may include scheduling data buffering (e.g., TRS frequency domain buffer collection) in a later (e.g., next) TRS occasion. For instance, the wireless device may schedule buffering the data at (e.g., may postpone, skip, or abort buffering the data until) a later TRS occasion (e.g., after collision) as described with reference to FIG. 4.

[0170] At 525, if the ARD switch does not collide with the TRS occasion, the method may include determining whether an MSIM tune-away is ongoing. For instance, the wireless device may check to determine whether an MSIM tune-away is occurring, or may determine whether a second temporal period for performing MSIM tune-away collides with a first temporal period for buffering the data (e.g., during a TRS occasion) as described with reference to FIG. 4.

[0171] At 530, if the MSIM tune-away is ongoing (e.g., collides with the TRS occasion), the method may include aborting data buffering and may include scheduling data buffering (e.g., TRS frequency domain buffer collection) for a later (e.g., next) TRS occasion. For instance, the wireless device may schedule buffering the data at (e.g., may postpone, skip, or abort buffering the data until) a later TRS occasion (e.g., after collision) as described with reference to FIG. 4.

[0172] At 535, if MSIM tune-away is not ongoing, the method may include determining whether a current TRS occasion is during a sleep mode. For instance, the wireless device may check to determine whether the current TRS occasion is during a period of deep sleep, or may determine whether a second temporal period for performing sleep mode collides with a first temporal period for buffering the data (e.g., during a TRS occasion) as described with reference to FIG. 4.

[0173] At 540, if the current TRS occasion is during sleep mode, the method may include aborting data buffering and may include scheduling data buffering (e.g., TRS frequency domain buffer collection) for a TRS occasion that is closer to a CDRX wakeup occasion (e.g., that overlaps with the CDRX wakeup occasion. For instance, the wireless device may find a later TRS occasion closer to a CDRX wakeup occasion andAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO55 schedule buffering the data at (e.g., may postpone, skip, or abort buffering the data until) a later TRS occasion as described with reference to FIG. 4.

[0174] At 545, if a current TRS occasion is not during sleep mode, the method may include performing data buffering for the current TRS occasion. For instance, the wireless device may receive a TRS in the current TRS occasion and may buffer data (e.g., samples or measurements) based on the current TRS as described with reference to FIG. 4.

[0175] In some approaches, the wireless device may determine whether one or more other modem operations collide with a TRS occasion before performing data buffering for the current TRS occasion. For instance, the wireless device may check to determine whether a modem operation that may impact (or may be impacted by) data collection or buffering is triggered, or may determine whether a second temporal period for performing the modem operation collides with a first temporal period for buffering the data as described with reference to FIG. 4. If the modem operation collides with the TRS occasion, the method may include performing the modem operation and may include scheduling data buffering (e.g., TRS frequency domain buffer collection) for a later (e.g., next) TRS occasion. For instance, the wireless device may schedule buffering the data at (e.g., may postpone, skip, or abort buffering the data until) a later TRS occasion (e.g., after collision) as described with reference to FIG. 4.

[0176] FIG. 6 shows an example of a timing diagram 600 that supports collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure. One or more of the operations described with reference to FIG. 6 may be performed by a wireless device (e.g., wireless device 415), or a network node (e.g., network node 405). The timing diagram 600 illustrates an example of data buffering (e.g., TRS frequency domain buffer collection) when a CDRX cycle is configured from a network (e.g., a network node).

[0177] In the example of FIG. 6, TRS occasions may occur with a TRS periodicity 650 over time. One or more TRS occasions 605 (where data may be buffered) and one or more aborted or skipped TRS occasions 610 are illustrated. For instance, a wireless device may buffer data for one or more of the TRS occasions 605, or may abort or skip buffering data for one or more of the aborted or skipped TRS occasions 610.Attorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO56

[0178] In the example of FIG. 6, a wireless device (e.g., UE) enters 615 CDRX mode. In association with the CDRX mode, the wireless device may enter a first sleep mode 645-a and a second sleep mode 645-b. Due to the first sleep mode 645-a, a TRS is aborted 625. For instance, a TRS scheduled during the first sleep mode 645-a may be aborted and moved to a TRS occasion 630 closer to a time with CDRX ON 635 (e.g., to a TRS occasion that partially overlaps with CDRX ON 635). Another TRS may be skipped 640. For instance, a TRS may be skipped 640 that is within a threshold time of the first sleep mode 645-a or the second sleep mode 645-b. The wireless device may exit 620 the CDRX mode.

[0179] FIG. 7 shows an example of a timing diagram 700 that supports collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure. One or more of the operations described with reference to FIG. 7 may be performed by a wireless device (e.g., wireless device 415), or a network node (e.g., network node 405). The timing diagram 700 illustrates an example of data buffering (e.g., TRS frequency domain buffer collection) when an ARD switch is ongoing.

[0180] In the example of FIG. 7, TRS occasions may occur with a TRS periodicity 750 over time. One or more TRS occasions 705 (where data may be buffered) and one or more aborted or skipped TRS occasions 710 are illustrated. For instance, a wireless device may buffer data for one or more of the TRS occasions 705, or may abort or skip buffering data for one or more of the aborted or skipped TRS occasions 710.

[0181] In the example of FIG. 7, a wireless device (e.g., UE) performs an ARD switch 715. For instance, the wireless device may switch from 4 Rx antennas to 2 Rx antennas for a power-related condition or may switch from 2 Rx antennas to 4 Rx antennas for a throughput scenario. Due to the ARD switch 715, a TRS is aborted. For instance, a TRS scheduled during the ARD switch 715 may be aborted and moved to a TRS occasion 720 after the ARD switch 715.

[0182] FIG. 8 shows an example of a timing diagram 800 that supports collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure. One or more of the operations described with reference to FIG. 8 may be performed by a wireless device (e.g., wireless device 415), or a network nodeAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO57(e.g., network node 405). The timing diagram 800 illustrates an example of data buffering (e.g., TRS frequency domain buffer collection) during an MSIM tune-away 815.

[0183] In the example of FIG. 8, TRS occasions may occur with a TRS periodicity 850 over time. One or more TRS occasions 805 (where data may be buffered) and one or more aborted or skipped TRS occasions 810 are illustrated. For instance, a wireless device may buffer data for one or more of the TRS occasions 805, or may abort or skip buffering data for one or more of the aborted or skipped TRS occasions 810.

[0184] In the example of FIG. 8, a wireless device (e.g., UE) performs an MSIM tune-away 815 (e.g., with a tune-away object). For instance, the wireless device may tune from a first network or first RAT to a second network or second RAT. Due to the MSIM tune-away 815, a TRS is aborted. For instance, because the MSIM tune-away 815 may be a relatively high priority procedure, a TRS (e.g., frequency domain buffer collection occasion) may be aborted, and scheduled at a TRS occasion 820 after the MSIM tune-away 815.

[0185] FIG. 9 shows an example of a timing diagram 900 that supports collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure. One or more of the operations described with reference to FIG. 9 may be performed by a wireless device (e.g., wireless device 415), or a network node (e.g., network node 405). The timing diagram 900 illustrates an example of data buffering (e.g., TRS frequency domain buffer collection) with a CDRX mode when a wireless device enters a deep sleep mode.

[0186] In the example of FIG. 9, TRS occasions may occur with a TRS periodicity 950 over time. One or more TRS occasions 905 (where data may be buffered) and one or more aborted or skipped TRS occasions 910 are illustrated. For instance, a wireless device may buffer data for one or more of the TRS occasions 905, or may abort or skip buffering data for one or more of the aborted or skipped TRS occasions 910.

[0187] In the example of FIG. 9, a wireless device (e.g., UE) enters 915 CDRX mode. CDRX occasions may occur in accordance with a CDRX cycle 955. In association with the CDRX mode, the wireless device may enter a first deep sleep mode 945-a and a second deep sleep mode 945-b. Due to the first deep sleep mode 945-a, aAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO58TRS is skipped 925-a. For instance, a TRS scheduled during the first deep sleep mode 945-a may be skipped 925-a and a TRS occasion 930-a closer to a time with CDRX ON 935-a (e.g., to a TRS occasion that partially overlaps with CDRX ON 935-a) may be utilized to buffer the data. Additional TRSs may be skipped 925-b, 925-c. For instance, TRSs may be skipped 925-a, 925-b that occur during the second deep sleep mode 945-b. A TRS occasion 930-b closer to a time with CDRX ON 935-b (e.g., to a TRS occasion that partially overlaps with CDRX ON 935-b) may be utilized to buffer the data. The wireless device may exit 920 the CDRX mode. As illustrated in FIG. 9, if data buffering (e.g., a frequency domain collection opportunity) occurs for a TRS occasion while the wireless device is in deep sleep mode, the wireless device may not perform data buffering (unless the data buffering is higher priority than the deep sleep mode or unless the positioning procedure is associated with a first positioning type for increased accuracy or decreased latency). The wireless device may attempt to find a TRS occasion that is nearest to a CDRX ON in time and schedule the data buffering.

[0188] FIG. 10 shows an example of a timing diagram 1000 that supports collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure. One or more of the operations described with reference to FIG. 10 may be performed by a wireless device (e.g., wireless device 415), or a network node (e.g., network node 405). The timing diagram 1000 illustrates an example of data buffering (e.g., TRS frequency domain buffer collection) and gap occasions 1015 (e.g., in a scenario of a second positioning type with reduced accuracy or increased latency relative to a first positioning type).

[0189] In the example of FIG. 10, TRS occasions may occur with a TRS periodicity 1050 over time. One or more TRS occasions 1005 (where data may be buffered) and one or more aborted or skipped TRS occasions 1010 are illustrated. One or more gap occasions 1015 are also illustrated. A gap occasion 1015 may be an occasion for a measurement gap (e.g., MSIM measurement gap), LTA gap, re-tuning, or for another operation. For instance, a measurement gap may be a period without signaling that may be configured by a network (e.g., network node). Gap occasions may occur in accordance with a gap periodicity 1045. In some approaches, an LTA gap may be any signaling gap due to one or more MSIM activities.Attorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO59

[0190] Due to a gap occasion 1015, data buffering for a TRS is aborted 1025. For instance, because data buffering (e.g., a TRS frequency domain buffer collection instance) collides with a gap occasion 1015, the gap occasion 1015 is prioritized 1035 and the data buffering is aborted 1025. For example, because the data buffering is associated with a second positioning type, the gap occasion 1015 (e.g., measurement gap, LTA gap, or MSIM gap occasion) may be prioritized 1035 and the colliding data buffering may be aborted. Data buffering may be scheduled 1030 for a TRS occasion 1005 that occurs between gap occasions 1015. For instance, data buffering (e.g., frequency domain buffer collection) may be scheduled 1030 for a TRS occasion 1005 due to a previous data buffering being aborted due to a gap occasion 1015 (e.g., network-configured gap, measurement gap, LTA gap, MSIM gap, among other examples).

[0191] FIG. 11 shows an example of a timing diagram 1100 that supports collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure. One or more of the operations described with reference to FIG. 11 may be performed by a wireless device (e.g., wireless device 415), or a network node (e.g., network node 405). The timing diagram 1100 illustrates an example of data buffering (e.g., TRS frequency domain buffer collection) and gap occasions 1115 (e.g., in a scenario of a first positioning type with increased accuracy or reduced latency relative to a second positioning type).

[0192] In the example of FIG. 11, TRS occasions may occur with a TRS periodicity 1150 over time. One or more TRS occasions 1105 (where data may be buffered) are illustrated. One or more gap occasions 1115 are also illustrated. A gap occasion 1115 may be an occasion for a measurement gap (e.g., MSIM measurement gap), LTA gap, re-tuning, or for another operation. Gap occasions may occur in accordance with a gap periodicity 1145.

[0193] During a gap occasion 1115, data buffering for a TRS may be prioritized 1135. In this example, data buffering (e.g., a TRS frequency domain buffer collection instance) collides with a gap occasion 1115 and data buffering is prioritized 1135. For example, because the data buffering is associated with a first positioning type, the data buffering may be prioritized 1135 over the gap occasion 1115 (e.g., measurement gap,Attorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO60LTA gap, or MSIM gap occasion). The gap scheduling may be aborted 1125 to allow the data buffering to occur for the TRS occasion 1105.

[0194] FIG. 12 shows an example of a timing diagram 1200 that supports collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure. One or more of the operations described with reference to FIG. 12 may be performed by a wireless device (e.g., wireless device 415), or a network node (e.g., network node 405). The timing diagram 1200 illustrates an example of data buffering (e.g., TRS frequency domain buffer collection) during a handover or cell reselection 1235.

[0195] In the example of FIG. 12, TRS occasions may occur with a TRS periodicity 1250 over time. One or more TRS occasions 1205 (where data may be buffered) and one or more aborted or skipped TRS occasions 1210 are illustrated. For instance, a wireless device may buffer data for one or more of the TRS occasions 1205, or may abort or skip buffering data for one or more of the aborted or skipped TRS occasions 1210.

[0196] In the example of FIG. 12, a wireless device (e.g., UE) performs a handover or cell reselection 1235. For instance, the wireless device may perform a handover between network entities or may switch between cells. Due to the handover or reselection 1235, a TRS is aborted. For instance, when a handover or cell reselection gets triggered where data buffering (e.g., TRS frequency domain buffer collection) is ongoing, the data buffering (e.g., buffer collection object) may be aborted. The wireless device may wait for the handover or cell reselection to be completed. Data buffering (e.g., TRS frequency domain buffer collection) may be scheduled for a TRS occasion 1205 after handover or cell reselection is completed.

[0197] FIG. 13 shows an example of a timing diagram 1300 that supports collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure. One or more of the operations described with reference to FIG. 13 may be performed by a wireless device (e.g., wireless device 415), or a network node (e.g., network node 405). The timing diagram 1300 illustrates an example of data buffering (e.g., TRS frequency domain buffer collection) based on transport block (TB) size or data scheduling.Attorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO61

[0198] In the example of FIG. 13, TRS occasions may occur with a TRS periodicity 1350 in one or more slots 1340 of subframes 1335 over time. One or more TRS occasions 1305 (where data may be buffered) and one or more aborted or skipped TRS occasions 1310 are illustrated. For instance, a wireless device may buffer data for one or more of the TRS occasions 1305, or may abort or skip buffering data for one or more of the aborted or skipped TRS occasions 1310.

[0199] In the example of FIG. 13 (for a 30 hertz (Hz) subcarrier spacing (SCS), for instance), a wireless device (e.g., UE) may identify whether one of the slots 1340 is loaded with more data or less data than another one of the slots 1340. For instance, the wireless device may determine slot loading (e.g., which slot has more or less data load) based on a TB size (that may be configured by the network), MCS, or code rate. In the example of FIG. 13, based on an MCS and code rate, the wireless device may determine that a first slot 1315 has a lesser load (e.g., less scheduling) than a second slot 1320, and may select the first slot for data buffering associated with a TRS occasion. The wireless device may skip data buffering for the second slot 1320 based on the data load of the second slot 1320, which may be determined based on MCS or code rate.

[0200] FIG. 14 shows an example of a timing diagram 1400 illustrating examples of wireless device operations that support collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure. Specifically, FIG. 14 illustrates an example of timing between OTA subframes 1405, LI component 1410 operations, grant manager 1415 operations, and processing component 1420 operations. In some approaches, one or more of the operations described may be performed by one or more components (e.g., a modem, a processor with instructions, circuitry, or other component s)) of a wireless device. For instance, FIG. 14 provides an example of arbitration that may be performed in a wireless device modem for RF intrusive operations (e.g., BWP switch or ARD switch with TRS frequency domain buffer collection).

[0201] As illustrated in FIG. 14, the LI component 1410 may provide a buffer collection process request to the grant manager 1415. For instance, an LI positioning module may provide a frequency domain buffer collection request at a designated TRS resource location. The grant manager 1415 may perform a collision resolution operation in response to the buffer collection process request. For instance, the grant managerAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO621415 may perform one or more operations to arbitrate or resolve a collision between data buffering and one or more other procedures as described with reference to one or more of FIGs. 4-13.

[0202] In the example of FIG. 14, the grant manager 1415 detects that there is no current collision between a procedure and data buffering. The grant manager 1415 sets up a collision resolution window. The contention resolution window may be utilized to block another procedure requested or targeted during the collision resolution window. For example, data buffering may be an RF intrusive operation. Other procedures (e.g., ARD switch or BWP switch, among other examples) may be blocked. Accordingly, the grant manager 1415 may start a collision resolution window.

[0203] The grant manager 1415 may send an acknowledgment to the LI component 1410. For instance, if the grant manager 1415 determines that no other procedure (e.g., high priority RF intrusive operation, such as BWP switch or ARD switch) is ongoing, the grant manager 1415 may send the acknowledgment (e.g., frequency domain buffer collect acknowledgment) to the LI component 1410.

[0204] The LI component 1410 may send a request or command to the processing component 1420 (e.g., traffic thread) to execute the data buffering. For example, after receiving the acknowledgment, the LI component may send the request to the processing component 1420, which may initiate one or more operations to be performed by RF circuitry or another component(s).

[0205] As illustrated in FIG. 14, the traffic thread may utilize downlink ticks for timing purposes. A nominal tick offset or a Rx tick offset may exist between the OTA subframes 1405 and the processing component 1420. The request or command to execute the data buffering is sent before an LI boundary time to capture slot N. The processing component 1420 (or one or more other components) prepare to buffer data before slot N. At slot N, the data buffering and tagging (e.g., GNSS time tagging) is performed and indicated to the LI component 1410. The LI component 1410 or the grant manager 1415 may utilize a margin window after the data buffering is complete.

[0206] FIG. 15 shows an example of a process flow 1500 that supports collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure. The process flow 1500 may include an LI component 1585, aAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO63 processing component 1590, and one or more interface units 1595. The LI component 1585, the processing component 1590, or the interface unit(s) 1595 may be included in a wireless device (e.g., the wireless device 415 described with reference to FIG. 4). In some approaches, one or more of the operations described with reference to FIG. 15 may be performed by one or more components (e.g., a modem, a processor with instructions, circuitry, or other component(s)) of a wireless device.

[0207] In the following description of the process flow 1500, the communications between the LI component 1585, the processing component 1590, or the interface unit(s) 1595 may be transmitted in a different order than the example order shown, or the operations performed by the LI component 1585, the processing component 1590, or the interface unit(s) 1595 may be performed in different orders or at different times. One or more operations may be omitted from the process flow 1500, or one or more other operations may be added to the process flow 1500. 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.

[0208] At 1505, the LI component 1585 may perform arbitration. For instance, the LI component may perform arbitration or collision resolution as described with reference to FIG. 4.

[0209] At 1510, the LI component 1585 may send a buffer and information request to the processing component 1590. For instance, the buffer and information request may request that the processing component 1590 initiate or perform data buffering (e.g., frequency domain data capture) or GNSS tagging.

[0210] At 1515, the processing component 1590 may schedule capture or tagging operations. For instance, the processing component 1590 may determine a time or period of time to perform data buffering or GNSS tagging.

[0211] At 1520, the processing component 1590 may send a trigger to the interface unit(s) 1595 in accordance with the schedule. The trigger may include one or more signals, commands, or indicators for the interface unit(s) to perform data buffering or tagging.Attorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO64

[0212] At 1525, the interface unit(s) 1595 may buffer data or tag data. For instance, the interface unit(s) 1595 may obtain data (e.g., samples of a RS) and store the data in a buffer (e.g., double data rate (DDR) memory). Additionally, or alternatively, the interface unit(s) 1595 may tag data with GNSS information. For instance, the interface unit(s) 1595 may store GNSS information (e.g., GNSS timing information or other information) in memory in association with the buffered data.

[0213] At 1530, the interface unit(s) 1595 may send an indication to the processing component 1590. The indication may indicate the performance of the buffering and tagging operation(s).

[0214] At 1535, the processing component 1590 may send an indication to the LI component 1585. The indication may indicate the performance of the buffering and tagging operation(s).

[0215] FIG. 16 shows a block diagram 1600 of a device 1605 that supports collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure. The device 1605 may be an example of aspects of a wireless device as described herein. The device 1605 may include a receiver 1610, a transmitter 1615, and a communications manager 1620. The device 1605, or one or more components of the device 1605 (e.g., the receiver 1610, the transmitter 1615, the communications manager 1620), 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).

[0216] The receiver 1610 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 collision resolution for positioning procedures). Information may be passed on to other components of the device 1605. The receiver 1610 may utilize a single antenna or a set of multiple antennas.

[0217] The transmitter 1615 may provide a means for transmitting signals generated by other components of the device 1605. For example, the transmitter 1615 may transmit information such as packets, user data, control information, or any combinationAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO65 thereof associated with various information channels (e.g., control channels, data channels, information channels related to collision resolution for positioning procedures). In some examples, the transmitter 1615 may be co-located with a receiver 1610 in a transceiver module. The transmitter 1615 may utilize a single antenna or a set of multiple antennas.

[0218] The communications manager 1620, the receiver 1610, the transmitter 1615, or various combinations or components thereof may be examples of means for performing various aspects of collision resolution for positioning procedures as described herein. For example, the communications manager 1620, the receiver 1610, the transmitter 1615, or various combinations or components thereof may be capable of performing one or more of the functions described herein.

[0219] In some examples, the communications manager 1620, the receiver 1610, the transmitter 1615, 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).

[0220] Additionally, or alternatively, the communications manager 1620, the receiver 1610, the transmitter 1615, 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 1620, the receiver 1610, the transmitter 1615, 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,Attorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO66 individually or collectively, a means for performing the functions described in the present disclosure).

[0221] 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 receiver 1610, the transmitter 1615, or both. For example, the communications manager 1620 may receive information from the receiver 1610, send information to the transmitter 1615, or be integrated in combination with the receiver 1610, the transmitter 1615, or both to obtain information, output information, or perform various other operations as described herein.

[0222] For example, the communications manager 1620 is capable of, configured to, or operable to support a means for determining that a collision does not occur between a first temporal period for buffering data in association with a positioning procedure and a second temporal period for performing a procedure, or that a collision is resolved based on a collision resolution procedure. The communications manager 1620 is capable of, configured to, or operable to support a means for receiving a reference signal (RS) during an RS occasion, where reception of the RS triggers one or more processors to buffer the data in association with a positioning procedure, where a timing of the RS occasion prevents a collision or is based on the collision resolution procedure. The communications manager 1620 is capable of, configured to, or operable to support a means for transmitting position information that is based on the data that is associated with the positioning procedure.

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

[0224] FIG. 17 shows a block diagram 1700 of a device 1705 that supports collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure. The device 1705 may be an example of aspects of a device 1605 or aAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO67 wireless device as described herein. The device 1705 may include a receiver 1710, a transmitter 1715, and a communications manager 1720. The device 1705, or one or more components of the device 1705 (e.g., the receiver 1710, the transmitter 1715, the communications manager 1720), 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).

[0225] The receiver 1710 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 collision resolution for positioning procedures). Information may be passed on to other components of the device 1705. The receiver 1710 may utilize a single antenna or a set of multiple antennas.

[0226] The transmitter 1715 may provide a means for transmitting signals generated by other components of the device 1705. For example, the transmitter 1715 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 collision resolution for positioning procedures). In some examples, the transmitter 1715 may be co-located with a receiver 1710 in a transceiver module. The transmitter 1715 may utilize a single antenna or a set of multiple antennas.

[0227] The device 1705, or various components thereof, may be an example of means for performing various aspects of collision resolution for positioning procedures as described herein. For example, the communications manager 1720 may include a collision component 1725, a buffer component 1730, a position component 1735, or any combination thereof. The communications manager 1720 may be an example of aspects of a communications manager 1620 as described herein. In some examples, the communications manager 1720, 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 1710, the transmitter 1715, or both. For example, the communications manager 1720 may receive information from the receiver 1710, send information to the transmitter 1715, or be integrated in combination with the receiver 1710, the transmitter 1715, or both to obtainAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO68 information, output information, or perform various other operations as described herein.

[0228] The collision component 1725 is capable of, configured to, or operable to support a means for determining that a collision does not occur between a first temporal period for buffering data in association with a positioning procedure and a second temporal period for performing a procedure, or that a collision is resolved based on a collision resolution procedure. The buffer component 1730 is capable of, configured to, or operable to support a means for receiving a reference signal (RS) during an RS occasion, where reception of the RS triggers one or more processors to buffer the data in association with a positioning procedure, where a timing of the RS occasion prevents a collision or is based on the collision resolution procedure. The position component 1735 is capable of, configured to, or operable to support a means for transmitting position information that is based on the data that is associated with the positioning procedure.

[0229] FIG. 18 shows a block diagram 1800 of a communications manager 1820 that supports collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure. The communications manager 1820 may be an example of aspects of a communications manager 1620, a communications manager 1720, or both, as described herein. The communications manager 1820, or various components thereof, may be an example of means for performing various aspects of collision resolution for positioning procedures as described herein. For example, the communications manager 1820 may include a collision component 1825, a buffer component 1830, a position component 1835, an MSIM component 1840, a BWP component 1845, a modem operation component 1850, an ARD component 1855, a handover component 1860, 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).

[0230] The collision component 1825 is capable of, configured to, or operable to support a means for determining that a collision does not occur between a first temporal period for buffering data in association with a positioning procedure and a second temporal period for performing a procedure, or that a collision is resolved based on a collision resolution procedure. The buffer component 1830 is capable of, configured to,Attorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO69 or operable to support a means for receiving an RS during an RS occasion, where reception of the RS triggers one or more processors to buffer the data in association with a positioning procedure, where a timing of the RS occasion prevents a collision or is based on the collision resolution procedure. The position component 1835 is capable of, configured to, or operable to support a means for transmitting position information that is based on the data that is associated with the positioning procedure.

[0231] In some examples, the MSIM component 1840 is capable of, configured to, or operable to support a means for performing a MSIM tune-away, where the MSIM tune-away is the procedure, and where the collision resolution procedure includes scheduling the RS occasion after the second temporal period for performing the MSIM tune-away.

[0232] In some examples, the second temporal period is a period of a sleep mode of the wireless device. In some examples, the collision resolution procedure includes scheduling the RS occasion to at least partially overlap with an active mode of the wireless device.

[0233] In some examples, the second temporal period is a period of a sleep mode of the wireless device. In some examples, the collision resolution procedure includes scheduling the RS occasion during the period of the sleep mode based on the positioning procedure being associated with a first positioning type that provides increased accuracy or decreased latency relative to a second positioning type.

[0234] In some examples, the collision resolution procedure includes scheduling the RS occasion during the second temporal period based on a satisfaction of a threshold of time in which buffering the data that is associated with the positioning procedure was not performed due to one or more procedures that conflicted with buffering the data.

[0235] In some examples, the collision resolution procedure includes scheduling the RS occasion previous to scheduling the procedure. In some examples, the second temporal period for performing the procedure overlaps with a collision resolution window associated with buffering the data. In some examples, the procedure is blocked.

[0236] In some examples, the BWP component 1845 is capable of, configured to, or operable to support a means for performing a BWP switch, where the BWP switch is theAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO70 procedure, and where the collision resolution procedure includes scheduling the RS occasion after the second temporal period for performing the BWP switch.

[0237] In some examples, the modem operation component 1850 is capable of, configured to, or operable to support a means for performing a modem operation, where the modem operation is the procedure, and where the collision resolution procedure includes scheduling the RS occasion after the second temporal period for performing the modem operation.

[0238] In some examples, the ARD component 1855 is capable of, configured to, or operable to support a means for performing an ARD switch, where the ARD switch is the procedure, and where the collision resolution procedure includes scheduling the RS occasion after the second temporal period for performing the ARD switch.

[0239] In some examples, the second temporal period is a period of a procedure gap of the wireless device. In some examples, the collision resolution procedure includes scheduling the RS occasion after the procedure gap of the wireless device.

[0240] In some examples, the second temporal period is a period of a procedure gap of the wireless device. In some examples, the collision resolution procedure includes scheduling the RS occasion during the period of the procedure gap based on the positioning procedure being associated with a first positioning type that provides increased accuracy or decreased latency relative to a second positioning type.

[0241] In some examples, the handover component 1860 is capable of, configured to, or operable to support a means for performing a handover procedure or a cell reselection procedure, where the handover procedure or the cell reselection procedure is the procedure, and where the collision resolution procedure includes scheduling the RS occasion after the second temporal period for performing the handover procedure or the cell reselection procedure.

[0242] In some examples, the RS occasion is scheduled in a first slot with a lesser load than a second slot based on a MCS or a code rate.

[0243] FIG. 19 shows a diagram of a system 1900 including a device 1905 that supports collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure. The device 1905 may be an example of or includeAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO71 components of a device 1605, a device 1705, or a wireless device as described herein. The device 1905 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 1920, an I / O controller, such as an I / O controller 1910, one or more transceivers 1915, one or more antennas 1925, at least one memory 1930, code 1935, and at least one processor 1940. The device 1905 may include one or more sensors 1950. 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 1945).

[0244] The I / O controller 1910 may manage input and output signals for the device 1905. The I / O controller 1910 may also manage peripherals not integrated into the device 1905. In some cases, the I / O controller 1910 may represent a physical connection or port to an external peripheral. In some cases, the I / O controller 1910 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 1910 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, the I / O controller 1910 may be implemented as part of one or more processors, such as the at least one processor 1940. In some cases, a user may interact with the device 1905 via the I / O controller 1910 or via hardware components controlled by the I / O controller 1910.

[0245] In some cases, the device 1905 may include a single antenna. However, in some other cases, the device 1905 may have more than one antenna, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver(s) 1915 may communicate bi-directionally via the one or more antennas 1925 using wired or wireless links as described herein. For example, the transceiver 1915 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 1915 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 1925 for transmission, and to demodulate packets received from the one or more antennas 1925. The transceiver 1915, or the transceiver 1915 and one or more antennas 1925, may be an example of a transmitter 1615, a transmitter 1715, a receiver 1610, a receiver 1710, or any combination thereof or component thereof, as described herein.Attorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO72

[0246] The one or more transceivers 1915 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) 1925 for communicating with other devices, such as one or more UEs 115, network entities 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.

[0247] The short-range wireless transceivers may be connected to one or more of the antenna(s) 1925 to communicate with (e.g., transmit one or more signals to, or receive one or more signals from) one or more network nodes, such as one or more UEs 115, network entities 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, 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,Attorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO73BLUETOOTH® 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.

[0248] The satellite transceiver(s) may include one or more satellite signal receivers, or one or more satellite signal transmitters. In some cases, the device 1905 may be a terrestrial device that may communicate one or more satellites via the satellite transceiver(s). In other cases, device 1905 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.

[0249] The satellite signal receiver(s) may be connected to one or more of the antenna(s) 1925 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 the processor 1940 may perform calculations to determine a location of the device 1905, the UE 115, the network entity 105, or another device using measurements obtained from one or more satellite signals.

[0250] The one or more satellite signal transmitters may be connected to one or more of the antennas 1925 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 signalAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO74 transmitter(s) may comprise hardware or a combination of hardware and instructions for transmitting satellite positioning or communication signals.

[0251] The device 1905 may include one or more sensors 1950 coupled with the one or more processors 1940 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 1950 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) 1950 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 1950 may include an image sensor, camera, microphone, light detector, or pressure sensor, among other examples. In some aspects, the sensor(s) 1950 may include a plurality of different types of devices, and the device 1905 (e.g., sensor(s) 1950 processor(s) 1940) may combine the outputs of the different types of devices to provide motion information. For example, the sensor(s) 1950 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.

[0252] The at least one memory 1930 may include RAM and ROM. The at least one memory 1930 may store computer-readable, computer-executable, or processorexecutable code, such as the code 1935. The code 1935 may include instructions that, when executed by the at least one processor 1940, cause the device 1905 to perform various functions described herein. The code 1935 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 1935 may not be directly executable by the at least one processor 1940 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the at least one memory 1930 may include, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices.Attorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO75

[0253] The at least one processor 1940 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 1940 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 1940. The at least one processor 1940 may be configured to execute computer-readable instructions stored in a memory (e.g., the at least one memory 1930) to cause the device 1905 to perform various functions (e.g., functions or tasks supporting collision resolution for positioning procedures). For example, the device 1905 or a component of the device 1905 may include at least one processor 1940 and at least one memory 1930 coupled with or to the at least one processor 1940, the at least one processor 1940 and the at least one memory 1930 configured to perform various functions described herein.

[0254] In some examples, the at least one processor 1940 may include multiple processors and the at least one memory 1930 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 described herein. In some examples, the at least one processor 1940 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 1940) and memory circuitry (which may include the at least one memory 1930)), 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 1940 or a processing system including the at least one processor 1940 may be configured to, configurable to, or operable to cause the device 1905 to perform one or more of the functions described herein. Further, as described herein, being “configured to,” being “configurable to,” and being “operableAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO76 to” may be used interchangeably and may be associated with a capability, when executing code 1935 (e.g., processor-executable code) stored in the at least one memory 1930 or otherwise, to perform one or more of the functions described herein.

[0255] For example, the communications manager 1920 is capable of, configured to, or operable to support a means for determining that a collision does not occur between a first temporal period for buffering data in association with a positioning procedure and a second temporal period for performing a procedure, or that a collision is resolved based on a collision resolution procedure. The communications manager 1920 is capable of, configured to, or operable to support a means for receiving an RS during an RS occasion, where reception of the RS triggers one or more processors 1940 to buffer the data in association with a positioning procedure, where a timing of the RS occasion prevents a collision or is based on the collision resolution procedure. The communications manager 1920 is capable of, configured to, or operable to support a means for transmitting position information that is based on the data that is associated with the positioning procedure.

[0256] By including or configuring the communications manager 1920 in accordance with examples as described herein, the device 1905 may support techniques for 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.

[0257] In some examples, the communications manager 1920 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver 1915, the one or more antennas 1925, or any combination thereof. Although the communications manager 1920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1920 may be supported by or performed by the at least one processor 1940, the at least one memory 1930, the code 1935, or any combination thereof. For example, the code 1935 may include instructions executable by the at least one processor 1940 to cause the device 1905 to perform various aspects of collision resolution for positioning procedures as described herein, or the at least one processor 1940 and the at least one memory 1930 may be otherwise configured to, individually or collectively, perform or support such operations.Attorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO77

[0258] FIG. 20 shows a flowchart illustrating a method 2000 that supports collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure. The operations of the method 2000 may be implemented by a wireless device or its components as described herein. For example, the operations of the method 2000 may be performed by a wireless device as described with reference to FIGs. 1 through 19. 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.

[0259] At 2005, the method may include determining that a collision does not occur between a first temporal period for buffering data in association with a positioning procedure and a second temporal period for performing a procedure, or that a collision is resolved based on a collision resolution procedure. 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 collision component 1825 as described with reference to FIG. 18.

[0260] At 2010, the method may include receiving an RS during an RS occasion, where reception of the RS triggers buffering the data in association with a positioning procedure, where a timing of the RS occasion prevents a collision or is based on the collision resolution procedure. 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 buffer component 1830 as described with reference to FIG. 18.

[0261] At 2015, the method may include transmitting position information that is based on the data that is associated with the positioning procedure. 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 position component 1835 as described with reference to FIG. 18.

[0262] FIG. 21 shows a flowchart illustrating a method 2100 that supports collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure. The operations of the method 2100 may be implemented by a wireless device or its components as described herein. For example, the operations ofAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO78 the method 2100 may be performed by a wireless device as described with reference to FIGs. 1 through 19. 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.

[0263] At 2105, the method may include performing a BWP switch. The operations of 2105 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2105 may be performed by a BWP component 1845 as described with reference to FIG. 18.

[0264] At 2110, the method may include determining that a collision does not occur between a first temporal period for buffering data in association with a positioning procedure and a second temporal period for performing a procedure, or that a collision is resolved based on a collision resolution procedure. The operations of 2110 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2110 may be performed by a collision component 1825 as described with reference to FIG. 18.

[0265] At 2115, the method may include receiving an RS during an RS occasion, where reception of the RS triggers buffering the data in association with a positioning procedure, where a timing of the RS occasion prevents a collision or is based on the collision resolution procedure, where the BWP switch is the procedure, and where the collision resolution procedure includes scheduling the RS occasion after the second temporal period for performing the BWP switch. The operations of 2115 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2115 may be performed by a buffer component 1830 as described with reference to FIG. 18.

[0266] At 2120, the method may include transmitting position information that is based on the data that is associated with the positioning procedure. The operations of 2120 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2120 may be performed by a position component 1835 as described with reference to FIG. 18.Attorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO79

[0267] FIG. 22 shows examples of wireless communications systems 2200 that support collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure. Various positioning techniques are illustrated in the context of the wireless communications systems 2200. 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. 22, 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.

[0268] Examples of OTDOA or DL-TDOA 2205 are illustrated in FIG. 22. One or more of the OTDOA or DL-TDOA 2205 positioning techniques may be included in a downlink-based positioning procedure. In OTDOA or DL-TDOA 2205 positioning techniques, a UE may measure a difference between times of arrival (ToAs) of RSs (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 a reference signal time difference (RSTD) or a time difference of arrival (TDOA) measurement. A positioning device (e.g., the UE, an LMF, an SLP, or another device) may utilize the differences in ToAs to determine (e.g., estimate) a location of the UE.

[0269] 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., an 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 an LMF for UE-assisted positioning) may estimate the UE’s location.

[0270] An example of UL-TDOA 2210 is illustrated in FIG. 22. One or more of the UL-TDOA 2210 positioning techniques may be included in an uplink-based positioning procedure. UL-TDOA 2210 may have some similarities to DL-TDOA 2205. The UL-Attorney Docket No. PB0004GR.WO (114958.5168)Qualcomm Ref. No. 2404320WO80TDOA 2210 positioning techniques may be based on uplink RSs (e.g., SRS) transmitted from the UE to multiple TRPs. For example, the UE transmits one or more uplink RSs 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 RS(s) to a positioning device (e.g., an 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.

[0271] An example of DL-AoD 2215 is illustrated in FIG. 22. One or more of the DL-AoD 2215 positioning techniques may be included in a downlink-based positioning procedure. In DL-AoD 2215, a UE may obtain received signal strength measurements corresponding 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., AoDl and AoD2) between the UE and the transmitting TRP(s). The positioning device (e.g., 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).

[0272] An example of UL-AoA 2220 is illustrated in FIG. 22. One or more of the UL-AoA 2220 positioning techniques may be included in an uplink positioning procedure. In UL-AoA 2220, one or more TRPs (e.g., TRP1 and TRP2) measure the received signal strength of one or more uplink RSs (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.

[0273] Some positioning techniques or procedures may include a combination downlink-based and uplink-based positioning techniques. Examples of downlink-basedAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO81 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).

[0274] 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., an 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).

[0275] An example of multi-cell RTT 2225 is illustrated in FIG. 22. 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 2225, 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.

[0276] 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 2230 positioning techniques are illustrated in FIG. 22.Attorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO82

[0277] E-CID positioning techniques (not shown in FIG. 22) 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.

[0278] In some approaches, a positioning device (e.g., 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 network entity) from which RSs may be measured. In some examples, a positioning device may transmit assistance data or other information indicating one or more RS configuration parameters. The RS 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 RS identifier, a RS 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 nodes) without the use of assistance data.

[0279] 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 inAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO83 frequency range 2 (FR2), an expected RSTD value may have an associated uncertainty or search window with a range of ±8 ps.

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

[0281] Various examples of sidelink positioning techniques are illustrated in FIG. 22. Sidelink positioning techniques may include positioning techniques that are based 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).

[0282] A first example of sidelink positioning 2235 is illustrated in FIG. 22. In the first example of sidelink positioning 2235, 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)).

[0283] A second example of sidelink positioning 2240 is illustrated in FIG. 22. In the second example of sidelink positioning 2240, 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.Attorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO84

[0284] A third example of sidelink positioning 2245 is illustrated in FIG. 22. The third example of sidelink positioning 2245 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 2245, 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).

[0285] A fourth example of sidelink positioning 2250 is illustrated in FIG. 22. The fourth example of sidelink positioning 2250 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 fourth example of sidelink positioning 2250, 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.

[0286] An example of relay positioning 2255 is illustrated in FIG. 22. In the example of relay positioning 2255, a relay UE (e.g., with an established location) may participate in the location estimation of a remote UE (without performing uplink RS 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., 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.

[0287] An example of joint positioning 2260 is illustrated in FIG. 22. In the example of joint positioning 2260, 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. 22, RTT or TDOA techniques mayAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO85 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., 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.

[0288] 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. 22. For instance, data based on a RS (e.g., PRS, SRS, or other RS) may be buffered, stored, 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. Some examples of the positioning techniques may be performed in one or more wireless communications systems 2200, such as LTE and NR, where NR may support sidelink communications.

[0289] FIG. 23 shows an example of a node diagram 2300 that supports collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure. Al models are programmatic or algorithmic structures that simulate intelligent behavior. Machine learning models may be examples of Al models. Machine learning models are programmatic or algorithmic structures that may be trained to infer or predict an output based on an input. For example, a machine learning model may be trained using training input data and ground truth data.

[0290] Machine learning models may be categorized as unsupervised or supervised. Unsupervised learning may be utilized to draw inferences and find patterns from input data without references to labeled outcomes. Two examples of unsupervised learning models include clustering and dimensionality reduction. Clustering is an unsupervised technique that involves the grouping, or clustering, of data points. Clustering techniques may include k-means clustering, hierarchical clustering, mean shift clustering, and density-based clustering. Dimensionality reduction may be a procedure for reducing a quantity of random variables under consideration by obtaining a set of principal variables. Dimensionality reduction may reduce the dimension of a feature set or reduce a quantity of features). Some dimensionality reduction techniques may be categorized as feature elimination or feature extraction. One example of dimensionality reduction mayAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO86 be referred to as principal component analysis (PCA). PCA may involve projecting higher dimensional data (e.g., three dimensions) to a lower-dimensional space (e.g., two dimensions), which may result in a lower dimension of data (e.g., two dimensions instead of three dimensions) while maintaining one or more variables in the model.

[0291] Supervised learning involves learning a function that maps an input to an output based on associated inputs and outputs. For instance, supervised learning may be utilized to draw inferences and find patterns from input data based on labeled data (e.g., training input data with associated ground truth data). A supervised model may subcategorized as a regression or classification model. Regression models may provide continuous outputs. One example of a regression model is a linear regression, which may determine a line that fits (e.g., best fits) input data. Extensions of linear regression include multiple linear regression (e.g., finding a plane of best fit) and polynomial regression (e.g., finding a curve of best fit).

[0292] In classification models, the output may be discrete. One example of a classification model is logistic regression. Logistic regression may be similar to linear regression, but may be used to model a probability for a finite quantity of outcomes. For example, a logistic regression may be utilized such that the output values may be between 0 and 1. Another example of a classification model is a support vector machine. For two classes of data, for example, a support vector machine may determine a hyperplane or a boundary between the two classes of data that maximizes a margin between the two classes. For instance, many planes may separate two classes, while one plane may maximize the margin or distance between the classes. Another example of a classification model is Naive Bayes, which is based on Bayes Theorem.

[0293] Other examples of classification models include decision tree models, random forest models, and neural network models, where an output may be discrete. In a decision tree model, a tree structure is defined with multiple nodes. Decisions may be used to move from a root node at the top of the decision tree to a leaf node (e.g., a node without a child node) at the bottom of the decision tree. A higher quantity of nodes in the decision tree model may correlate with higher decision accuracy.

[0294] Random forest models may utilize ensemble learning techniques that build from decision tree models. Random forests involve creating multiple decision treesAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO87 using bootstrapped datasets of the original data and randomly selecting a subset of variables at each tier of the decision tree. The model may select the mode of all of the predictions of each decision tree. By relying on a “majority wins” model, the risk of error from an individual tree may be reduced.

[0295] Another example of a machine learning model is a neural network (NN). A neural network may be a network of functional nodes. Neural networks may utilize one or more input variables to traverse the nodes and generate one or more output variables. For example, a neural network may utilize an input vector to generate an output vector.

[0296] The Al model illustrated in FIG. 23 is an example of a neural network. The neural network includes an input layer i that receives n (one or more) inputs (illustrated as “Input 1,” “Input 2,” and “Input n”), one or more hidden layers (illustrated as hidden layers “hl,” “h2,” and “h3”) for processing the inputs from the input layer, and an output layer o that provides m (one or more) outputs (labeled “Output 1” and “Output m”). While examples of quantities of inputs n, hidden layers h, and outputs m are illustrated in FIG. 23, same or different quantities of inputs, hidden layers, or outputs may be utilized in other examples. In some approaches, the hidden layers h may include linear function(s) or activation function(s) that the nodes (illustrated as circles) of each successive hidden layer process from the nodes of the previous hidden layer.

[0297] In some aspects, the Al model illustrated in FIG. 23 or another Al model may be trained in accordance with one or more training techniques. In some examples of the training techniques described herein, one or more Al models (e.g., implemented by one or more devices) may be trained based on training input data (e.g., measurements of RSs to or from various UEs) and ground truth data (e.g., locations of the various UEs), thereby enabling later determination of an output (e.g., an inferred or prediction location or measurement) when an Al model is executed with runtime input data (e.g., from other UEs).

[0298] Ground truth data may be data representing a target output associated with training input data. Ground truth data may be generated or observed (e.g., empirical) data. In some examples, ground truth data may indicate one or more observed locations (e.g., coordinates or addresses, among other examples) corresponding to training input data. Examples of training input data may include RS data (e.g., measurements of aAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO88PRS, SRS, RS of an SSB, CSI-RS, DMRS, or TRS, among other examples), signal data (e.g., signal strength data, RSRP data, RSRPP data, RSSI data, RSRQ data, SINR data, or SNR data, among other examples), channel data (e.g., CIR data, PDP data, DP data, CQI data, CSI data, decoding failure rate, or retransmission request rate, among other examples), AoA data, AoD data, TDOA data, RTT data, TA data, sensor data (e.g., image data, RF data, motion data, orientation data, or audio data, among other examples), or identifier data (e.g., cell ID data or service set identifier (SSID) data, among other examples), among other examples.

[0299] In some examples, ground truth data may indicate one or more measurements or values (e.g., AoA measurements, AoD measurements, TDOA measurements, RTT measurements, line-of-sight (LOS) angle(s), or other values) corresponding to training input data. Examples of training input data may include RS data (e.g., measurements of a PRS, SRS, RS of an SSB, CSI-RS, DMRS, or TRS, among other examples), signal data (e.g., signal strength data, RSRP data, RSSI data, RSRQ data, SINR data, or SNR data, among other examples), channel data (e.g., CIR data, PDP data, DP data, CQI data, CSI data, decoding failure rate, or retransmission request rate, among other examples), TA data, sensor data (e.g., image data, RF data, motion data, orientation data, or audio data, among other examples), or identifier data (e.g., cell ID data or SSID data, among other examples), among other examples.

[0300] An Al model (e.g., the Al model illustrated in FIG. 23 or a machine learning model) may be trained by executing the Al model with the training data to produce an output, comparing the output with the ground truth data, and adjusting weights of the Al model to reduce a disparity between the output and the ground truth data. For example, one or more of the nodes or connections of the Al model may have an associated weight that may be adjusted to modify one or more of the outputs. In some approaches, a cost function may be utilized to compare the output with the ground truth data to indicate a cost (e.g., error or disparity). Adjustments to the weights that reduce the cost may be retained, advanced, or increased, while adjustments to the weights that increase the cost may be discarded, avoided, or decreased. Training procedures may be repeated or iterated to improve Al model performance.

[0301] Input data (e.g., runtime input data) may be provided to a trained Al model, which may infer or predict an output based on the input data. Some examples of AlAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO89 models may be trained to infer or predict a location based on input data (e.g., RS data, signal data, channel data, Ao A data, AoD data, TDOA data, RTT data, TA data, sensor data, or identifier data, among other examples). Some examples of Al models may be trained to infer or predict measurements or values (e.g., timing measurement s), angle measurement(s), AoA measurement(s), AoD measurement s), TDOA measurements), RTT measurements), LOS angle(s), or other values) based on input data.

[0302] Some examples of the techniques described herein may be performed in conjunction with one or more of the Al models described with reference to FIG. 23. For instance, one or more samples or data based on a RS (e.g., PRS, SRS, or other RS) described with reference to FIG. 4 may be examples of inputs for one or more the Al models.

[0303] FIG. 24A shows a block diagram 2400-a that supports collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure. In some examples of the techniques described herein, a positioning device (e.g., LMF, SLP, UE, or other device) may utilize D-AI / ML positioning. In D-AI / ML positioning, one or more Al models 2410 (e.g., machine learning model(s) or D-AI / ML model(s)) may be trained to utilize input data 2405 to output (e.g., infer or predict) a location 2415 (e.g., a position estimate, coordinates, or an address of a UE). Examples of the input data 2425 may include RS data (e.g., measurements of a PRS, SRS, RS of an SSB, CSLRS, DMRS, or TRS, among other examples), signal data (e.g., signal strength data, RSRP data, RS SI data, RSRQ data, SINR data, or SNR data, among other examples), channel data (e.g., CIR data, PDP data, DP data, CQI data, CSI data, decoding failure rate, or retransmission request rate, among other examples), AoA data, AoD data, TDOA data, RTT data, TA data, sensor data (e.g., image data, RF data, motion data, orientation data, or audio data, among other examples), or identifier data (e.g., cell ID data or SSID data, among other examples), among other examples.

[0304] FIG. 24B shows a block diagram 2400-b that supports collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure. In some examples of the techniques described herein, a positioning device (e.g., LMF, SLP, UE, or other device) may utilize A-AI / ML (or indirect) positioning. In A-AI / ML, one or more Al models 2430 (e.g., machine learning model(s) or “A-AI / ML” model(s)) may be trained to utilize input data 2425 to output (e.g., infer or predict) oneAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO90 or more inferred measurements 2435. The Al model(s) 2430 may be located at a wireless device or network node (e.g., UE or network entity). Examples of the input data 2425 may include RS data, signal data, channel data, sensor data, or identifier data, among other examples. Examples of the inferred measurements 2435 may include one or more timing measurements, angle measurements, AoA measurements, AoD measurements, TDOA measurements, RTT measurements, LOS angles, or other values.

[0305] In A-AI / ML, the input data 2425 or Al model(s) 2430 may be structured in accordance with one or more approaches. Different model input structures may have different implications regarding model output accuracy, generalization, robustness, or model complexity.

[0306] In some approaches, a same Al model 2430 may be utilized (e.g., separately utilized) for input data 2425 from multiple (e.g., P) TRPs, where a separate input may be utilized for input data 2425 from each respective TRP. For instance, a first CIR corresponding to a first TRP may be utilized as an input for the Al model 2430 to generate a first ToA corresponding to the first TRP, a second CIR corresponding to a second TRP may be utilized as an input for the Al model 2430 to generate a second ToA corresponding to the second TRP, and an Kth CIR corresponding to an Kth TRP may be utilized as an input for the Al model 2430 to generate an Kth ToA corresponding to the Kth TRP. The first ToA, the second ToA, and the Kth ToA may be examples of the inferred measurements 2435.

[0307] In some approaches, different Al models 2430 (e.g., K Al models) may be utilized for input data 2425 from multiple (e.g., K) TRPs, where a separate input may be utilized for input data 2425 from each respective TRP. For instance, a first CIR corresponding to a first TRP may be utilized as an input for a first Al model to generate a first ToA corresponding to the first TRP, a second CIR corresponding to a second TRP may be utilized as an input for a second Al model to generate a second ToA corresponding to the second TRP, and an Kth CIR corresponding to an Kth TRP may be utilized as an input for an Kth Al model to generate an Kth ToA corresponding to the Kth TRP. The first Al model, the second Al model, and the Kth Al model may be examples of the Al models 2430. The first ToA, the second ToA, and the Kth ToA may be examples of the inferred measurements 2435.Attorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO91

[0308] In some approaches, one Al model 2430 may be utilized (e.g., jointly or concurrently utilized) for input data 2425 from multiple (e.g., P) TRPs, where a separate input may be utilized for input data 2425 from each respective TRP. For instance, a first CIR corresponding to a first TRP, a second CIR corresponding to a second TRP, and an Kth CIR corresponding to an Kth TRP may be utilized as inputs for the Al model 2430 to generate a first To A corresponding to the first TRP, a second To A corresponding to the second TRP, and an Kth To A corresponding to the Kth TRP. The first To A, the second ToA, and the Kth ToA may be examples of the inferred measurements 2435.

[0309] The inferred measurement(s) 2435 may be provided to, or utilized by, a positioning device (e.g., LMF, SLP, UE, or other device) to output a location 2445 (e.g., a position estimate, coordinates, or an address of a UE). For example, the positioning device may include a positioning component 2440. The positioning component may be, or may utilize, one or more other Al models (e.g., positioning model(s)) or non-AI models (Chan’s algorithm or a Kalman filter, among other examples) to determine the location 2445. In some examples, the Al model(s) 2430 and the positioning component 2440 may be implemented at the same device (e.g., LMF, SLP, UE, or other device) or at different devices. For network-assisted positioning, for instance, a UE may apply the Al model(s) 2430 to generate the inferred measurement(s) 2435, which may be reported to an network node (e.g., LMF). The network node may apply the positioning component 2440 to generate the location 2445. For UE-based positioning, a device (e.g., a network entity, LMF, or another UE with a sidelink connection to the UE) may apply the Al model(s) 2430 to generate the inferred measurement(s) 2435, which may be reported to the UE, which may apply the positioning component 2440 to generate the location 2445.

[0310] Some examples of the techniques described herein may be performed in conjunction with one or more of the D-AI / ML positioning described with reference to FIG. 24 A or the A-AI / ML described with reference to FIG. 24B. For instance, one or more samples or data based on a RS (e.g., PRS, SRS, or other RS) may be examples of input data 2405 or input data 2425, or the Al model(s) 2410 or the Al model(s) 2430 may produce inferred measurements 2435 based on the data or samples in accordance with one or more of the techniques described with reference to FIG. 4.Attorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO92

[0311] FIG. 25 shows examples of block diagrams 2500 that support collision resolution for positioning procedures in accordance with one or more aspects of the present disclosure. A first use case 2505 (e.g., “Case 1”) may be an example of UE- based positioning, where the UE includes an Al model. In the first use case 2505, the Al model may be utilized for D-AI / ML positioning or A-AI / ML. For example, a network entity may transmit a RS (e.g., PRS) to the UE. In a D-AI / ML positioning approach, the UE may execute the Al model based on measurements of the RS to determine a location. An indication of the location may be transmitted to the LMF. In an A-AI / ML approach, the UE may execute the Al model based on measurements of the RS to determine one or more inferred measurements (e.g., based on the PRS). The UE may utilize the inferred measurement(s) to determine the location using another Al model or a non- Al model. An indication of the location may be transmitted to the LMF.

[0312] A second use case 2510 (e.g., “Case 2a”) may be an example of UE-assisted or LMF -based positioning, where the UE includes an Al model. In the second use case 2510, the Al model may be utilized for AI / ML assisted positioning (e.g., A-AI / ML). For example, a network entity may transmit a RS (e.g., PRS) to the UE. In the A-AI / ML approach, the UE may execute the Al model based on measurements of the RS to determine one or more inferred measurements (e.g., based on the PRS). An indication of the inferred measurement(s) may be transmitted to the LMF. The LMF may utilize the inferred measurement s) to determine the location using an Al model or non- Al model.

[0313] A third use case 2515 (e.g., “Case 2b”) may be an example of UE-assisted or LMF -based positioning, where the LMF includes an Al model. In the third use case 2515, the Al model may be utilized for D-AI / ML positioning. For example, a network entity may transmit a RS (e.g., PRS) to the UE. The UE may measure the RS and transmit an indication of the measurement s) to the LMF. In a D-AI / ML positioning approach, the LMF may execute the Al model based on the measurement(s) of the RS to determine a location.

[0314] A fourth use case 2520 (e.g., “Case 3a”) may be an example of network entity-assisted positioning, where the network entity includes an Al model. In the fourth use case 2520, the Al model may be utilized for A-AI / ML. For example, a UE may transmit a RS (e.g., SRS) to the network entity. The network entity may measure the RS. In the A-AI / ML approach, the network entity may execute the Al model based onAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO93 measurements of the RS to determine one or more inferred measurements (e.g., based on the SRS). An indication of the inferred measurement(s) may be transmitted to the LMF. The LMF may utilize the inferred measurement(s) to determine the location using an Al model or a non- Al model.

[0315] A fifth use case 2525 (e.g., “Case 3b”) may be an example of network entity- assisted positioning, where the LMF includes an Al model. In the fifth use case 2525, the Al model may be utilized for D-AI / ML positioning. For example, a UE may transmit a RS (e.g., SRS) to the network entity. The network entity may measure the RS (e.g., based on the SRS) and transmit an indication of the measurement s) to the LMF. In a D-AI / ML positioning approach, the LMF may execute the Al model based on the measurement(s) of the RS to determine a location.

[0316] Some examples of the techniques described herein may utilize one or more AI / ML models. For instance, some of the techniques may be utilized for signaling or protocol aspects for enabling AI / ML model selection, activation, deactivation, switching, or fallback. Some techniques may provide a signaling mechanism of one or more applicable functionalities or models. Some aspects may be utilized for identification related signaling, other signaling, or mechanism(s) to facilitate model training, inference, performance monitoring, or data collection of UE-sided model training data for UE-sided or network-sided Al models (e.g., with or without data collection for core network, operations, administration, and maintenance (0AM), or an OTT device).

[0317] Some examples of the techniques described herein may provide positioning accuracy enhancements for D-AI / ML positioning or A- AI / ML positioning. D-AI / ML use cases may include Case 1 (e.g., UE-based positioning with a UE-side Al model and D-AI / ML positioning), Case 2b (e.g., UE-assisted or LMF-based positioning with an LMF-side Al model and D-AI / ML positioning), Case 3b: NG-RAN node assisted positioning with an LMF-side Al model and D-AI / ML positioning). A-AI / ML use cases may include Case 2a (e.g., UE-assisted or LMF-based positioning with a UE-side Al model and A-AI / ML positioning) or Case 3a (e.g., NG-RAN node assisted positioning with a gNB-side Al model and A-AI / ML positioning.Attorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO94

[0318] Some examples of the techniques described herein may include measurement aspects, signaling, or one or more other mechanisms to facilitate one or more operations related to positioning accuracy enhancements. Some aspects may include measurement signaling or approaches to help ensure reliability between training and inferencing related to network-side conditions for performing inferencing at a UE for positioning use cases. Some aspects may be utilized for performance monitoring.

[0319] One or more of the techniques described herein may be utilized for Al model identification or procedures for utilizing an Al model. In some examples, a network node (e.g., core network device, 0AM device, or OTT device) may collect UE-sided model training data. In some approaches, an Al model may be communicated (e.g., transferred or delivered) between devices. In some aspects, one-sided models or two- sided models may be utilized. For example, a wireless device and network node may interoperate. Performance monitoring or testing (e.g., static or non-static scenarios, propagation conditions for clustered delay line (CDL) or field data, among other examples) may be utilized in some approaches.

[0320] In some examples, offline or online Al model training may be utilized. Postdeployment validation may be performed to manage Al model changes or drift over time.

[0321] Some examples of the techniques described herein may be performed in conjunction with one or more of the use cases (e.g., the first use case 2505, the second use case 2510, the third use case 2515, the fourth use case 2520, or the fifth use case 2525) described with reference to FIG. 25. It should be noted that while examples of some use cases are illustrated in FIG. 25, other use cases in which a device (e.g., wireless device, network node, UE, network entity, or LMF, among other examples) may receive a RS, measure a RS, report measurements, infer measurements, infer a location, or report a location may be implemented.

[0322] In some approaches, one or more samples of a RS (e.g., PRS, SRS, or other RS) may be buffered, measured, or indicated (e.g., reported) in accordance with one or more of the techniques described with reference to FIG. 4. For direct AI / ML positioning with an Al-model on the LMF (e.g., Case 2b or Case 3b), one or more types of measurement reports may be utilized for Al model input (e.g., Al-based positioningAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO95 accuracy enhancement), where different types of measurement reports may have differing impacts on performance or signaling overhead. In some examples, a measurement report may include CIR, PDP, RSRP, RSRPP, or RSTD measurements. In some examples, a measurement report may be communicated, which may include timing, power, or phase information (e.g., reference time, CIR, PDP, or DP) of the channel response.

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

[0324] Aspect 1 : A method for wireless communications by a wireless device, comprising: determining that a collision does not occur between a first temporal period for buffering data in association with a positioning procedure and a second temporal period for performing a procedure, or that a collision is resolved based at least in part on a collision resolution procedure; receiving an RS during an RS occasion, wherein reception of the RS triggers one or more processors to buffer the data in association with the positioning procedure, wherein a timing of the RS occasion prevents a collision or is based at least in part on the collision resolution procedure; and transmitting position information that is based at least in part on the data that is associated with the positioning procedure.

[0325] Aspect 2: The method of aspect 1, further comprising: performing a MSIM tune-away, wherein the MSIM tune-away is the procedure, and wherein the collision resolution procedure comprises scheduling the RS occasion after the second temporal period for performing the MSIM tune-away.

[0326] Aspect 3: The method of aspect 1, wherein the second temporal period is a period of a sleep mode of the wireless device, and the collision resolution procedure comprises scheduling the RS occasion to at least partially overlap with an active mode of the wireless device.

[0327] Aspect 4: The method of aspect 1, wherein the second temporal period is a period of a sleep mode of the wireless device, and the collision resolution procedure comprises scheduling the RS occasion during the period of the sleep mode based at least in part on the positioning procedure being associated with a first positioning type that provides increased accuracy or decreased latency relative to a second positioning type.Attorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO96

[0328] Aspect 5: The method of any of aspects 1, 3, and 4, wherein the collision resolution procedure comprises scheduling the RS occasion during the second temporal period based at least in part on a satisfaction of a threshold of time in which buffering the data that is associated with the positioning procedure was not performed due to one or more procedures that conflicted with buffering the data.

[0329] Aspect 6: The method of aspect 1, wherein the collision resolution procedure comprises scheduling the RS occasion previous to scheduling the procedure, the second temporal period for performing the procedure overlaps with a collision resolution window associated with buffering the data, and the procedure is blocked.

[0330] Aspect 7: The method of aspect 1, further comprising: performing a BWP switch, wherein the BWP switch is the procedure, and wherein the collision resolution procedure comprises scheduling the RS occasion after the second temporal period for performing the BWP switch.

[0331] Aspect 8: The method of aspect 1, further comprising: performing a modem operation, wherein the modem operation is the procedure, and wherein the collision resolution procedure comprises scheduling the RS occasion after the second temporal period for performing the modem operation.

[0332] Aspect 9: The method of aspect 1, further comprising: performing an ARD switch, wherein the ARD switch is the procedure, and wherein the collision resolution procedure comprises scheduling the RS occasion after the second temporal period for performing the ARD switch.

[0333] Aspect 10: The method of aspect 1, wherein the second temporal period is a period of a procedure gap of the wireless device, and the collision resolution procedure comprises scheduling the RS occasion after the procedure gap of the wireless device.

[0334] Aspect 11 : The method of aspect 1, wherein the second temporal period is a period of a procedure gap of the wireless device, and the collision resolution procedure comprises scheduling the RS occasion during the period of the procedure gap based at least in part on the positioning procedure being associated with a first positioning type that provides increased accuracy or decreased latency relative to a second positioning type.Attorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO97

[0335] Aspect 12: The method of aspect 1, further comprising: performing a handover procedure or a cell reselection procedure, wherein the handover procedure or the cell reselection procedure is the procedure, and wherein the collision resolution procedure comprises scheduling the RS occasion after the second temporal period for performing the handover procedure or the cell reselection procedure.

[0336] Aspect 13: The method of any of aspects 1 through 12, wherein the RS occasion is scheduled in a first slot with a lesser load than a second slot based at least in part on a MCS or a code rate.

[0337] Aspect 14: A wireless device 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 13.

[0338] Aspect 15: A wireless device comprising at least one means for performing a method of any of aspects 1 through 13.

[0339] Aspect 16: A non-transitory computer-readable medium storing code the code comprising instructions executable by one or more processors to perform a method of any of aspects 1 through 13.

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

[0341] 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.Attorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO98

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

[0343] 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 neural processing 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.

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

[0345] Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of aAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO99 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 properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of 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.

[0346] 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.”

[0347] 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 thoseAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO100 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 “one or 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.”

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

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

[0350] The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may beAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO101 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.

[0351] 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. PB0004GR.WQ (114958.5168)

Claims

Qualcomm Ref. No. 2404320WO102CLAIMSWhat is claimed is:

1. A wireless device, 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: determine that a collision does not occur between a first temporal period for buffering data in association with a positioning procedure and a second temporal period for performing a procedure or that a collision is resolved based at least in part on a collision resolution procedure; receive a reference signal (RS) during an RS occasion, wherein reception of the RS triggers the one or more processors to buffer the data in association with the positioning procedure, wherein a timing of the RS occasion prevents a collision or is based at least in part on the collision resolution procedure; and transmit position information that is based at least in part on the data that is associated with the positioning procedure.

2. The wireless device of claim 1, wherein the one or more processors are further configured to: perform a multi-subscriber identity module (MSIM) tune-away, wherein the MSIM tune-away is the procedure, and wherein, to apply the collision resolution procedure, the one or more processors are configured to schedule the RS occasion after the second temporal period for performing the MSIM tune-away.

3. The wireless device of claim 1, wherein the second temporal period is a period of a sleep mode of the wireless device, and wherein, to apply the collision resolution procedure, the one or more processors are configured to schedule the RS occasion to at least partially overlap with an active mode of the wireless device.

4. The wireless device of claim 1, wherein the second temporal period is a period of a sleep mode of the wireless device, and wherein, to apply the collision resolution procedure, the one or more processors are configured to scheduleAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO103 the RS occasion during the period of the sleep mode based at least in part on the positioning procedure being associated with a first positioning type that provides increased accuracy or decreased latency relative to a second positioning type.

5. The wireless device of claim 1, wherein, to apply the collision resolution procedure, the one or more processors are configured to schedule the RS occasion during the second temporal period based at least in part on a satisfaction of a threshold of time in which buffering the data that is associated with the positioning procedure was not performed due to one or more procedures that conflicted with buffering the data.

6. The wireless device of claim 1, wherein, to apply the collision resolution procedure, the one or more processors are configured to schedule the RS occasion previous to scheduling the procedure, wherein the second temporal period for performing the procedure overlaps with a collision resolution window associated with buffering the data, and the procedure is blocked.

7. The wireless device of claim 1, wherein the one or more processors are further configured to: perform a bandwidth part (BWP) switch, wherein the BWP switch is the procedure, and wherein, to apply the collision resolution procedure, the one or more processors are configured to schedule the RS occasion after the second temporal period for performing the BWP switch.

8. The wireless device of claim 1, wherein the one or more processors are further configured to: perform a modem operation, wherein the modem operation is the procedure, and wherein, to apply the collision resolution procedure, the one or more processors are configured to schedule the RS occasion after the second temporal period for performing the modem operation.

9. The wireless device of claim 1, wherein the one or more processors are further configured to: perform an antenna receive diversity (ARD) switch, wherein the ARD switch is the procedure, and wherein, to apply the collision resolution procedure, theAttorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO104 one or more processors are configured to schedule the RS occasion after the second temporal period for performing the ARD switch.

10. The wireless device of claim 1, wherein the second temporal period is a period of a procedure gap of the wireless device, and wherein, to apply the collision resolution procedure, the one or more processors are configured to schedule the RS occasion after the procedure gap of the wireless device.

11. A method for wireless communications by a wireless device, comprising: determining that a collision does not occur between a first temporal period for buffering data in association with a positioning procedure and a second temporal period for performing a procedure, or that a collision is resolved based at least in part on a collision resolution procedure; receiving a reference signal (RS) during an RS occasion, wherein reception of the RS triggers buffering the data in association with the positioning procedure, wherein a timing of the RS occasion prevents a collision or is based at least in part on the collision resolution procedure; and transmitting position information that is based at least in part on the data that is associated with the positioning procedure.

12. The method of claim 11, further comprising: performing a multi-subscriber identity module (MSIM) tune-away, wherein the MSIM tune-away is the procedure, and wherein the collision resolution procedure comprises scheduling the RS occasion after the second temporal period for performing the MSIM tune-away.

13. The method of claim 11, wherein: the second temporal period is a period of a sleep mode of the wireless device, and the collision resolution procedure comprises scheduling the RS occasion to at least partially overlap with an active mode of the wireless device.

14. The method of claim 11, wherein:Attorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO105 the second temporal period is a period of a sleep mode of the wireless device, and the collision resolution procedure comprises scheduling the RS occasion during the period of the sleep mode based at least in part on the positioning procedure being associated with a first positioning type that provides increased accuracy or decreased latency relative to a second positioning type.

15. The method of claim 11, wherein the collision resolution procedure comprises scheduling the RS occasion during the second temporal period based at least in part on a satisfaction of a threshold of time in which buffering the data that is associated with the positioning procedure was not performed due to one or more procedures that conflicted with buffering the data.

16. The method of claim 11, wherein: the collision resolution procedure comprises scheduling the RS occasion previous to scheduling the procedure, the second temporal period for performing the procedure overlaps with a collision resolution window associated with buffering the data, and the procedure is blocked.

17. The method of claim 11, wherein: the second temporal period is a period of a procedure gap of the wireless device, and the collision resolution procedure comprises scheduling the RS occasion during the period of the procedure gap based at least in part on the positioning procedure being associated with a first positioning type that provides increased accuracy or decreased latency relative to a second positioning type.

18. The method of claim 11, further comprising: performing a handover procedure or a cell reselection procedure, wherein the handover procedure or the cell reselection procedure is the procedure, and wherein the collision resolution procedure comprises scheduling the RS occasion after the second temporal period for performing the handover procedure or the cell reselection procedure.Attorney Docket No. PB0004GR.WQ (114958.5168)Qualcomm Ref. No. 2404320WO10619. The method of claim 11, wherein the RS occasion is scheduled in a first slot with a lesser load than a second slot based at least in part on a modulation and coding scheme (MCS) or a code rate.

20. A wireless device, comprising: means for determining that a collision does not occur between a first temporal period for buffering data in association with a positioning procedure and a second temporal period for performing a procedure, or that a collision is resolved based at least in part on a collision resolution procedure; means for receiving a reference signal (RS) during an RS occasion, wherein reception of the RS triggers buffering data in association with the positioning procedure, wherein a timing of the RS occasion prevents a collision or is based at least in part on the collision resolution procedure; and means for transmitting position information that is based at least in part on the data that is associated with the positioning procedure.Attorney Docket No. PB0004GR.WQ (114958.5168)

Images