Bandwidth aggregation and simultaneous transmission and measurement for positioning

Abstract

In some implementations, one or more processors of a user equipment (UE) are configured to determine a time window for measuring a positioning reference signal (PRS) or transmitting a sounding reference signal (SRS). In response, the PRS from a transmission and reception point (TRP) is measured using the time window, or the SRS to the TRP is transmitted using the time window.

Description

BANDWIDTH AGGREGATION AND SIMULTANEOUS TRANSMISSION AND MEASUREMENT FOR POSITIONINGCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] The present application claims priority to U.S. Provisional Application No. 63 / 466,321, filed on May 14, 2023, titled “Bandwidth Aggregation and Simultaneous Transmission and Measurement for Positioning,” which is incorporated herein by reference in its entirety.BACKGROUND

[0002] Wireless communication networks provide integrated communication platforms and telecommunication services to wireless user devices. Example telecommunication services include telephony, data (e.g., voice, audio, and / or video data), messaging, and / or other services. The wireless communication networks have wireless access nodes that exchange wireless signals with the wireless user devices using wireless network protocols, such as protocols described in various telecommunication standards promulgated by the Third Generation Partnership Project (3GPP). Example wireless communication networks include time division multiple access (TDMA) networks, frequency-division multiple access (FDMA) networks, orthogonal frequency-division multiple access (OFDMA) networks, Long Term Evolution (LTE), and Fifth Generation New Radio (5G NR). The wireless communication networks facilitate mobile broadband service using technologies such as OFDM, multiple input multiple output (MIMO), advanced channel coding, massive MIMO, beamforming, and / or other features.SUMMARY

[0003] In some implementations, one or more processors of a user equipment (UE) are configured to determine a time window for measuring a positioning reference signal (PRS) or transmitting a sounding reference signal (SRS). In response, the PRS from a transmission and reception point (TRP) is measured using the time window, or the SRS to the TRP is transmitted using the time window. The details of one or more embodiments of these systems and methods are set forth in the accompanying drawings and the description below. Other features, objects, and advantages of these systems and methods will be apparent from the description and drawings, and from the claims.BRIEF DESCRIPTION OF THE FIGURES

[0004] FIG. 1 illustrates a wireless network, according to some implementations.

[0005] FIG. 2A illustrates a window for measurement or transmission, according to some implementations.

[0006] FIG. 2B illustrates a window for measurement or transmission, according to some implementations.

[0007] FIG. 3 illustrates a flowchart of an example method, according to some implementations.

[0008] FIG. 4 illustrates a flowchart of an example method, according to some implementations.

[0009] FIG. 5 illustrates a flowchart of an example method, according to some implementations.

[0010] FIG. 6 illustrates an example user equipment (UE), according to some implementations.

[0011] FIG. 7 illustrates an example access node, according to some implementations.DETAILED DESCRIPTION

[0012] To determine the position of a user equipment (UE), the 3 GPP wireless telecommunication standards support various positioning and ranging techniques. One such technique is carrier phase (CP) positioning, in which a phase difference between a transmitted signal and a received signal is measured to determine a distance between the transmitter and the receiver. For example, during downlink CP positioning, a transmitter (e.g., a UE or a network entity, such as a location management function [LMF]) can transmit a positioning reference signal (PRS) to a receiver (e.g., a target UE) for measurement. Conversely, during uplink CP positioning, the target UE can transmit a sounding reference signal (SRS) to another UE or the LMF for measurement.

[0013] To improve the positioning of a target UE, it was agreed that the 3GPP wireless telecommunication standards would support positioning methods (e.g., CP positioning) that utilize simultaneous measurements of the target UE and a positioning reference unit (PRU), e.g., a UE positioned at a known location. However, Release 17 of the 3GPP physical layer technical specifications (e.g., RANI specifications) do not support a mechanism for simultaneous measurements / transmissions (e.g., in the same slot(s)) for multiple UEs, such as a target UE and a PRU. It was also agreed to support on-demand PRS across positioning frequency levels (PFLs) for bandwidth aggregation in order to increase the bandwidth over which positioning measurements are made, thereby enhancing positioning accuracy. However, Release 17 of the RAN 1 specifications do not support bandwidth aggregation of multiple PFLs, or specify how to handle situations where bandwidth aggregation is uplink power limited.

[0014] The present disclosure describes systems and methods for enabling simultaneous measurements and transmissions (e.g., in the same slot(s)) for multiple UEs, such as a target UE and a PRU. In accordance with an aspect of the present disclosure, techniques for supporting CP measurement for double difference CP that uses simultaneous measurements of the target UE and the PRU are provided. In some implementations, a measurement or transmission instance (e.g., slot or window) supports simultaneous transmit and / or receive measurements. In some implementations, target UE(s) are mapped to PRU(s) for UE / PRU mapping / linkage. In some implementations, measurement timing for carrier phase measurement (e.g., down link [DL] or up link [UL] reference signal carrier phase [RSCP]) may support legacy positioning by using a timing (e.g., slot or time reference) at which measurement should be valid or transmission should have occurred. In some implementations, measurementtiming for carrier phase measurement may support double difference CP by using a timing for which a measurement or transmission is made. In some implementations, identifiers, resource (set) linkage, and localized measurement / transmission behavior is used to support simultaneous transmission / measurement.

[0015] The present disclosure also describes systems and methods for enabling bandwidth aggregation across multiple PFLs to enhance positioning measurements. In particular, techniques for supporting preconfigured, on-demand PRS across PFLs for PRS bandwidth aggregations are disclosed. In some implementations, the on-demand PRS request for PRS bandwidth aggregation can be LMF-initiated or UE-initiated. In some implementations, the PRS configuration is updated to accommodate bandwidth aggregation of multiple PFLs. In some implementations, on-demand PRS across PFLs is preconfigured to aggregate the PFLs for on-demand PRS by either (a) adding new fields or (b) creating a new PFL group structure to contain both PFLs and PFL groups. In some implementations, on-demand PRS across PFLs is preconfigured for both LMF-initiated and UE- initiated cases.

[0016] Techniques for handling bandwidth aggregation in cases where the uplink is power limited are also described. In some implementations, bandwidth aggregation is not used in a power limited case. In some implementations, bandwidth aggregation is allowed, but priority of what is transmitted is modified (e.g., based on only highest priority channels and / or PFL dropped based on proximity to highest priority channel).

[0017] FIG. 1 illustrates a wireless network 100, according to some implementations. The wireless network 100 includes a UE 102 and a base station 104 connected via one or more channels 106A, 106B across an air interface 108. The UE 102 and base station 104 communicate using a system that supports controls for managing the access of the UE 102 to a network via the base station 104.

[0018] In some implementations, the wireless network 100 may be a Non- Standalone (NS A) network that incorporates Long Term Evolution (LTE) and Fifth Generation (5G) New Radio (NR) communication standards as defined by the Third Generation Partnership Project (3 GPP) technical specifications. For example, the wireless network 100 may be a E-UTRA (Evolved Universal Terrestrial Radio Access)-NR Dual Connectivity (EN-DC) network, or an NR- EUTRA Dual Connectivity (NE-DC) network. In some other implementations, the wireless network 100 may be a Standalone (SA) network that incorporates only 5G NR. Furthermore, other types of communication standards are possible, including future 3 GPP systems (e.g.,Sixth Generation (6G)), Institute of Electrical and Electronics Engineers (IEEE) 802.11 technology (e.g., IEEE 802.11a; IEEE 802.11b; IEEE 802.11g; IEEE 802.11- 2007; IEEE 802.1 In; IEEE 802.11-2012; IEEE 802.1 lac; or other present or future developed IEEE 802.11 technologies), IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), or the like. While aspects may be described herein using terminology commonly associated with 5G NR, aspects of the present disclosure can be applied to other systems, such as 3G, 4G, and / or systems subsequent to 5G (e.g., 6G).

[0019] In the wireless network 100, the UE 102 and any other UE in the system may be, for example, any of laptop computers, smartphones, tablet computers, machine-type devices such as smart meters or specialized devices for healthcare, intelligent transportation systems, or any other wireless device. In network 100, the base station 104 provides the UE 102 network connectivity to a broader network (not shown). This UE 102 connectivity is provided via the air interface 108 in a base station service area provided by the base station 104. In some implementations, such a broader network may be a wide area network operated by a cellular network provider, or may be the Internet. Each base station service area associated with the base station 104 is supported by one or more antennas integrated with the base station 104. The service areas can be divided into a number of sectors associated with one or more particular antennas. Such sectors may be physically associated with one or more fixed antennas or may be assigned to a physical area with one or more tunable antennas or antenna settings adjustable in a beamforming process used to direct a signal to a particular sector.

[0020] The UE 102 includes control circuitry 110 coupled with transmit circuitry 112 and receive circuitry 114. The transmit circuitry 112 and receive circuitry 114 may each be coupled with one or more antennas. The control circuitry 110 may include various combinations of application-specific circuitry and baseband circuitry. The transmit circuitry 112 and receive circuitry 114 may be adapted to transmit and receive data, respectively, and may include radio frequency (RF) circuitry and / or front-end module (FEM) circuitry.

[0021] In various implementations, aspects of the transmit circuitry 112, receive circuitry 114, and control circuitry 110 may be integrated in various ways to implement the operations described herein. The control circuitry 110 may be adapted or configured to perform various operations, such as those described elsewhere in this disclosure related to a UE. For instance, the control circuitry 110 can determine a time window for measuring a PRS or transmitting a SRS, and / or determine a first configuration message for on-demand PRS.

[0022] The transmit circuitry 112 can perform various operations described in this specification. For example, the transmit circuitry 112 can transmit the SRS to the TRP using a time window. For example, the transmit circuitry 112 can transmit the first configuration message for on-demand PRS Additionally, the transmit circuitry 112 may transmit using a plurality of multiplexed uplink physical channels. The plurality of uplink physical channels may be multiplexed, e.g., according to time division multiplexing (TDM) or frequency division multiplexing (FDM) along with carrier aggregation. The transmit circuitry 112 may be configured to receive block data from the control circuitry 110 for transmission across the air interface 108.

[0023] The receive circuitry 114 can perform various operations described in this specification. For instance, the receive circuitry 114 can measure the PRS from a TRP using the time window, and / or receive a configuration message for on-demand PRS including data corresponding to bandwidth aggregation for a set of PFLs. Additionally, the receive circuitry 114 may receive a plurality of multiplexed downlink physical channels from the air interface 108 and relay the physical channels to the control circuitry 110. The plurality of downlink physical channels may be multiplexed, e.g., according to TDM or FDM along with carrier aggregation. The transmit circuitry 112 and the receive circuitry 114 may transmit and receive, respectively, both control data and content data (e.g., messages, images, video, etc.) structured within data blocks that are carried by the physical channels.

[0024] FIG. 1 also illustrates the base station 104. In some implementations, the base station 104 may be a 5G radio access network (RAN), a next generation RAN, a E-UTRAN, or a nonterrestrial cell. As used herein, the term “5G RAN” or the like may refer to the base station 104 that operates in an NR or 5G wireless network 100, and the term “E-UTRAN” or the like may refer to a base station 104 that operates in an LTE or 4G wireless network 100. The UE 102 utilizes connections (or channels) 106A, 106B, each of which includes a physical communications interface or layer.

[0025] The base station 104 circuitry may include control circuitry 116 coupled with transmit circuitry 118 and receive circuitry 120. The transmit circuitry 118 and receive circuitry 120 may each be coupled with one or more antennas that may be used to enable communications via the air interface 108. The transmit circuitry 118 and receive circuitry 120 may be adapted to transmit and receive data, respectively, to any UE connected to the base station 104. Thereceive circuitry 120 may receive a plurality of uplink physical channels from one or more UEs, including the UE 102.

[0026] In FIG. 1, the one or more channels 106 A, 106B are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a 3 GPP LTE protocol, an Advanced long term evolution (LTE-A) protocol, a LTE- based access to unlicensed spectrum (LTE-U), a 5G protocol, a NR protocol, an NR-based access to unlicensed spectrum (NR-U) protocol, and / or any other communications protocol(s). In implementations, the UE 102 may directly exchange communication data via a ProSe interface. The ProSe interface may alternatively be referred to as a sidelink (SL) interface and may include one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH).

[0027] The RANI specifications may support a mechanism to ensure simultaneous measurements / transmissions (e.g., in the same slot(s)) for multiple UEs, including a target UE and a PRU. Regarding the procedure for location of a target UE using PRUs, RAN includes agreements to support positioning methods that require simultaneous measurements of the target UE and PRU. In some implementations, the LMF can make the decision and realize such simultaneous measurements by using an enhanced scheduled location time. In some implementations, additional enhancement may be used to support the simultaneous measurements for the target UE and PRU.

[0028] The RANI specification may include enhancements to Long-Term Evolution (LTE) positioning protocol (LPP), new radio positioning protocol A (NRPPa), and / or RAN signaling to support simultaneous measurements of the same DL-PRS for multiple UEs, including a target UE and a PRU; and to support simultaneous transmission of sounding reference signal (SRS) for multiple UEs, including a target UE and a PRU. In some implementations, sidelink positioning (including ranging) in new radio (NR) systems may be supported [RANI, RAN2, RAN3, RAN4], In some implementations, physical layer measurements and signaling support NR DL and UL carrier phase positioning for UE-based, UE-assisted, and NG-RAN node assisted positioning [RANI, RAN2, RAN3, RAN4], In some implementations, existing DL PRS and UL SRS for positioning are used for NR carrier phase measurements. In some implementations, measurements are specified that are limited to a single carrier / PFL.

[0029] According to Technical Report (TR) 38.859, for DL NR carrier phase positioning, a PRU works as a UE to receive the DL PRS reference signals and provide the DL carrier phase measurements to the LMF, where the double differential measurements can be obtained by the difference of the DL carrier phase measurements from the target UE and those from the PRU for eliminating the measurement errors. For example, DL NR Carrier Phase Positioning, measurement and feedback at the target UE may include the CP and any Rel-17 positioning measurements needed (or configured by the LMF). Measurement and feedback at the PRU may only consist of the CP. DL NR carrier phase positioning can be UE-based or LMF-based. For example, the UE based DL carrier phase positioning may require the double differential measurements to be transmitted from the LMF to the UE. For example, the UE can estimate the positioning.

[0030] TR 38.859 specifies that, for UL NR carrier phase positioning, a PRU works as a UE to transmit the UL SRS signals for positioning purpose. Transmission and reception points (TRPs) provide the UL carrier phase measurements obtained from the UL SRS signals of the target UE and of the PRU to the LMF, where the double differential measurements can be obtained by the difference of these UL carrier phase measurements for eliminating the measurement errors. For example, the target UE can determine UL NR carrier phase positioning and / or the SRS. For example, the PRU can determine UL NR carrier phase positioning and / or the SRS. The TRP can measure the target UE. For example, the UE can include the CP. For example, the CP can measure any Rel-17 positioning measurements needed and / or configured by the LMF. For example, the TRP can measure the carrier phase of the PRU.

[0031] FIG. 2A illustrates a window 200 for measurement or transmission, according to some implementations. Carrier Phase (CP) measurement may be used for double difference CP that requires simultaneous measurements of the target UE 202 and PRU 204. In some implementations, target UE 202 can be the same or similar to UE 102 of FIG. 1. In some implementations, the PRU 204 can be the same or similar to UE 102. The PRU can be a UE whose position is known.

[0032] In some implementations, the PRU 204 can determine the position of the PRU 204. The PRU can perform positioning measurements (e.g., RSTD, RSRP, UE, Rx-Tx, and / or time difference measurements) and report these measurements to a location server. The PRU can transmit SRS to enable TRPs to measure and report UL positioning measurements (e.g., RTOA,UL-AoA, gNB, Rx-Tx, and / or time difference) from the PRU (e.g., at a known location). The PRU measurements can be compared by a location server with the measurements expected at the known PRU location to determine correction terms for other nearby target devices. The DL and / or UL location measurements for other target devices can then be corrected based on the previously determined correction terms. For example, the PRU 204 can transmit the location of the PRU 204 to the location server. For example, the PRU 204 can communicate with the location server without transmitting the location of the PRU 204. For example, the PRU 204 can transmit and receive location information from the other target devices. The above functionalities may be specified in 3GPP TS 38.305.

[0033] In some implementations, the reception of PRS or the transmission of SRS is simultaneous (e.g., at approximately the same time). A measurement / transmission instance or window can be used. Measurement / transmission instance can include transmission / reception at exactly the same time with exactly the same PRS / SRS resources 210. The measurement / transmission window can include transmission / reception within a defined window. In some implementations, the window is within the same slot(s). In some implementations, window is across slots, e.g., can span multiple slot(s). For example, resources may / may not overlap. In some implementations, the PRU 204 is configured to transmit / receive SRS / PRS at fixed offset (e.g., within a fixed time duration) from target UE 204. In some implementations, the target UE 202 is configured to transmit and / or receive SRS and / or PRS at a fixed offset (e.g., within a fixed time duration) from the PRU 204.

[0034] FIG. 2B illustrates a window 250 for measurement or transmission, according to some implementations. CP measurement may be used for double difference CP that requires simultaneous measurements of the target UE 252, target UE 254 and PRU 256. In some implementations, target UE 252 can be the same or similar to target UE 202 and / or the UE 102. In some implementations, target UE 254 can be the same or similar to target UE 202 and / or the UE 102. In some implementations, PRU 256 can be the same or similar to PRU 204 and / or UE 102. In some implementations, UE / PRU Mapping / Linkage may be used.

[0035] In some implementations, a positioning controller (e.g., LMF, target UE 252, target UE 254, and / or PRU 256) can use a scheduled location time window to configure a time-window. For example, the scheduled location time window can include a series of time windows in the future. The one or more positioning devices (e.g., target UE 252, target UE 254, gNB, and / or PRU 256) can transmit a positioning reference signal (PRS / SRS) using the scheduled locationtime window (e.g., at a timeslot in the future from the series of time windows) and estimates a positioning measurement (e.g., RSCP, RSCPD). The measurement s) can be reported to the positioning estimator.

[0036] In some implementations, a PRS / SRS estimate / measurement (e.g., RSCP or RSCPD) returned to the positioning estimator for a scheduled location time window can be treated by the positioning estimator as an estimate of the measurement of the positioning measurement within the time window(s). The positioning estimator can skip indicating the specific reference signal resource. The UE and / or the gNB can select a resource within the window. The UE and / or the gNB can transmit, responsive to selecting the resource, an indicator on if the UE and / or the gNB received a measurement within the time window. The PRS can determine a time window for the PRS (e.g., a new time window field similar to the scheduledLocationTime field could be added to LPP (e.g., in the IE CommonlEsRequestLocationlnformation). The time window can include different time types. For example, the time window can include a duration and periodicity defining the window during which the PRS is measured. The UE can select PRS resources. For example, the UE can measure the selected PRS resources. The UE and / or PRS send a corresponding NRPPa message to the gNB to enable the gNB to configure PRSs that fit within the window.

[0037] In some implementations, a second time window (e.g., the time window definition for SRS) can be sent to the gNB. The gNB can measure a set of SRS resources within the window. The gNB can report whether the measurement of the resources in the window are successfully measured.

[0038] Target UEs, including the target UE 252 and / or target UE 254 can be mapped to PRUs, including the PRU 256. In some implementations, the target UE 252 is mapped to PRU 256 (e.g., the target UE 254 is mapped to another PRU). In some implementations, the target UE 252 is mapped to PRU 256 and another PRU. In some implementations, the target UE 252 and target UE 254 are mapped to PRU 256. In some implementations, the target UE 252 and target UE 254 are mapped to PRU 256 and another PRU. When multiple target UEs are mapped to the same PRU, then the PRU transmits / receives one signal within a desired offset that works for the multiple target UEs.

[0039] Returning to FIG. 1, the UE 102 can support legacy position or double difference CP. NR DL reference signal carrier phase (RSCP) (of i-th path) is defined as the phase of the channel response at the i-th path delay derived from the resource elements (REs) that carry theDL PRS signals configured for the measurement. A RSCP is associated with a specific RF frequency. NR UL RSCP (of i-th path) is defined as the phase of the channel response at the i- th path delay derived from the REs that carry the UL SRS signal for positioning purpose configured for the measurement. A UL RSCP is associated with a specific RF frequency. For example, the reference signal carrier phase difference (RSCPD) can be used for NR DL measurement for NR CPP. The RSCPD includes the difference of RSCPs measured from the DL PRS signals from target TRP and reference TRP.

[0040] Measurement timing for carrier phase measurement may be defined in two ways. In some implementations, the measurement timing is the slot or reference time at which a measurement should be valid (e.g., to support general / legacy positioning). For example, the UE / gNB may perform the measurement at any time with any number of samples before the indicated time to ensure validity at the indicted time. In some implementations, the measurement timing is the slot or reference time for which a measurement is made (e.g., to support double difference CP). For example, the UE / gNB may perform the measurement at any time with any number of samples at the specified time(s) or within the time duration window(s).

[0041] Transmission timing may be defined in two ways. In some implementations, the slot or time reference which a transmission should have occurred (e.g., to support general / legacy positioning). In some implementations, the slot or reference time for which a transmission in made (e.g., to support double difference CP). This means that the UE / gNB may perform the transmission at any time at the specified time(s) or within the time duration window(s).

[0042] The UE 102 can support simultaneous transmission of SRS or measurement of PRS. Device IDs can be specified as an indication of Target UE(s) / PRU(s) and TRPs (TRP receptor for SRS transmission, TRP transmitter for PRS Transmission). PRS / SRS resources can be specified as an indication of specific PRS resource(s) for simultaneous measurement (at UE(s) / PRU(s)) and transmission (at TRP(s)) can be specified as an indication of specific SRS resource(s) for simultaneous transmission (at UE(s) / PRU(s)) and measurement (at TRP(s)).

[0043] A new information element (IE), such as LocalizedLocationTiming, may be added to, for example, 3GPP technical specification (TS) 37.355. The LocalizedLocationTiming IE can include an indication of time (or time window) for which the measurement should be made for SRS / PRS transmitted. A timing field can be added to 3GPP TS 37.355 (e.g., LocalizedLocationTiming, timeWindowLocationTiming) that indicates that the target device(UE / PRU) is requested to obtain location measurements or transmit signal (PRS / SRS) based on the timing field. The indicated time can be a specific time, a time range or a relative time from a reference (also signaled). For example, start time, duration, and periodicity. For example, start time, end time, and periodicity. The indicated time can be measured in seconds, or in network time such as slots or symbols. A specific time (as opposed to a time range) may indicate that the PRS / SRS is configured to (a) start immediately after this time, (b) end immediately before this time, and / or (c) overlap this time. Devices use this information and the PRS / SRS resource information to identify signals to transmit / measure.

[0044] A new IE, such as LocalizedLocationRequestSupported, may be added to, for example, 3GPP TS 37.355. When this field is present, it indicates that the target device supports localized location requests and / or time window based requests and the time base(s) supported for the localized location request. For example, the target device supports the IE LocalizedLocationTiming in IE CommonlEsRequestLocationlnformation, which may include SchedueledLocationTime (e.g., CommonlEsRequestLocationlnformation can include the updated version). The presence of LocalizedLocationRequestSupported (e.g., timeWindowLocationTiming) indicates the time base(s) supported for the measurem ent / signal transmission. If this field is absent, the target device does not support localized location requests.

[0045] A new IE, such as LocalizedLocationTimeSupportPerMode (e.g., timeWindowLocationSupportperMode), may be added to, for example, 3GPP TS 37.355. When this field is present, it is used by the target device to indicate the time bases supported for localized location requests for each positioning mode indicated by PositioningModes. The modes can be standalone, ue-based or ue-assisted. For example, the target device supports the IE LocalizedLocationTimeSupportPerMode in IE CommonlEsRequestLocationlnformation, which may include SchedueledLocationTime (e.g., CommonlEsRequestLocationlnformation can include the updated version).

[0046] A new IE, such as LocalizedLocationTimeSupport (g-g-, timeWindowLocationTimeSupport ), may be added to, for example, 3GPP TS 37.355. When this field is present, is used by the target device to indicate the time bases supported for localized location requests.

[0047] Enhancements may be made to enable simultaneous measurements on same DL PRS by a target UE and a PRU. The Enhancements may include enabling LMF to request the UEs,including target UE and PRU(s), to perform measurements on DL PRS resources (e.g., indicated DL PRS resources) occurring within indicated time window(s). The configuration of the indicated time window(s) may include the start time, duration, periodicity for the time window(s), as well as the relationship with the ScheduledLocationTime .

[0048] 3GPP TS 23.273 includes that a scheduled location time allows an external LCS Client, AF or the UE to specify a time in the future at which a current location of the UE is to be obtained. For example, time T. In some implementations, there may be no relationship between LocalizedLocationTiming and ScheduledLocationTime. In some implementations, the relationship between LocalizedLocationTiming and ScheduledLocationTime can include that LocalizedLocationTiming is set to occur at N time instances before scheduled location time. N can be fixed specified based on UE1 / UE2 capability, and / or N is configured by LMF.

[0049] The IE ScheduledLocationTimeSupport is used by the target device to indicate the time bases supported for scheduled location requests and LocalizedLocationTiming. The time bases can include utcTime, gnssTime, e-utraTime, nr time, relative-time, and / or time window. The IE ScheduledLocationTimeSupportPerMode is used by the target device to indicate the time bases supported for scheduled location requests and LocalizedLocationTiming for each positioning mode indicated by PositioningModes

[0050] The positioning mode can be standalone, ue-based, and / or ue-assisted. The time bases can include utcTime, gnssTime, e-utraTime, nr time, relative-time, and / or time window. In some implementations, the new IE LocalizedLocationTiming can include the time bases.

[0051] In some implementations, unknow initial phase from Carrier Phase positioning can be eliminated. In a first option, the unknown initial Rx phase of a UE can be eliminated by the difference between the measured RSCP and a reference RSCP. This elimination can be done automatically for RSCPD measurements. For RSCP measurements, this elimination can be handled in the LMF based on feedback of the RSCP from different TRPs (or from the same TRP at different times or frequencies). In doing so, there will be no need for an additional reference to be specified with the UE Rx-Tx time difference. In a second option, RTT signaling includes reference TRP. In this case, the UE feeds back RSCP and reference RSCP. In a third option, the UE autonomously selects reference for RSCP. In this case, the UE feeds back target RSCP and reference RSCP. The reference RSCP can be fed back with each RSCP. Alternatively, or in combination, the reference RSCP can be fed back at a desired time. Infourth option, the UE feeds back RSCP based on the identified resources. The different options can be combined in whole or in part without departing from the scope of the disclosure.

[0052] On demand positioning may be expanded and improved in order to support sidelink positioning. Signaling and procedures may be specified to support aggregation of PRS / SRS (respectively) resources across PFLs / carriers (respectively) for positioning measurements when the signals over aggregated resources are transmitted and received (respectively) using a single RF chain (same antenna) [RANI, RAN2], The support of bandwidth aggregation for positioning measurements may apply only to timing related measurements (e.g., RSTD, RTOA, and UE / gNB Rx-Tx time difference). LMF-initiated and UE-initiated on-demand PRS request for PRS bandwidth aggregation may be supported. Preconfigured on-demand PRS across PFLs for PRS bandwidth aggregations may be supported. On-demand PRS on PRS bandwidth aggregation may be determined based on RAN2 and RAN3.

[0053] 3GPP TS 38.305 includes on-demand PRS. On-demand PRS transmission procedure allows the LMF to control and decide whether PRS is transmitted or not and to change the characteristics of an ongoing PRS transmission. The on-demand PRS transmission procedure can be initiated by either the UE or LMF. The actual PRS changes are requested by the LMF irrespective of whether the procedure is UE- or LMF-initiated. Information is exchanged via LPP (LMF to or from UE) and NRPPa (LMF to or from gNB / TRP). PRS configurations are exchanged. On-demand PRS requests are exchanged. For UE-initiated on-demand PRS and for a pre-defined PRS configuration ID or explicit PRS configuration parameter, the UE may request for PRS transmission and change to PRS transmission characteristics. For LMF initiated on-demand PRS, the LMF may obtain UE measurements and change PRS transmission characteristics.

[0054] Rel-17 PFLs (Positioning Frequency Layer) configure one PFL at time. PRS configuration may be updated to accommodate bandwidth aggregation of multiple PFLs. A PFL group may be defined as configuring groups of PFLs or PRS resources for BW aggregation. The configuration can be based on (a) PRS resource sets or (b) PFL resources in different PFLs.

[0055] The ^-On-Demand-DL-PRS-Configurations IE from 3GPP TS 37.355 can be updated. The IE NR-On-Demand-DL-PRS-Configurations provides a set of possible DL-PRS configurations that can be requested by the target device on-demand. In some implementations for the first option, separate configurations are created for the legacy configurations based ondl-prs-configuration-rl7 and the new aggregated PRS resources / configurations based on dl- prs-configuration-r 18. A flag can be added to enable the UE to identify which set of configurations to use (e.g., legacy or aggregated configurations). In some implementations, a Rel-18 configuration is created that includes both Rel-17 and Rel-18 configurations and replaces parameter nr-DL-PRS-PositioningFrequencyLayer-rl7 with nr-DL-PRS- PositioningFrequencyLayerGroup-r 18. The existing framework may be used.

[0056] In the first option, 3GPP TS 37.355 can be updated as follows:- ASN1 START NR-On-Demand-DL-PRS-Configurations-rl7 ::= SEQUENCE { on-demand- dl-prs-configuration-list-rl7 SEQUENCE (SIZE (l..maxOD-DL-PRS- Configs-rl7)) OF On-Demand-DL-PRS-Configuration-rl7, NR-On-Demand-DL-PRS-Configurations-rl8 ::= SEQUENCE { on-demand- dl-prs-configuration-list-rl 8 SEQUENCE (SIZE (1..maxOD-DL-PRS- Configs-rl8)) OF On-Demand-DL-PRS-Configuration-rl8, PRS_aggregation {0,1 }} On-Demand-DL-PRS-Configuration-rl7 ::= SEQUENCE { dl-prs-configuration-id-rl7 DL-PRS-Configuration-ID-rl7, nr-DL-PRS-PositioningFrequencyLayer-r 17 NR-DL-PRS- PositioningFrequencyLayer-rl6, nr-DL-PRS-Info-rl 7 NR-DL-PRS-Info-r 16,} DL-PRS-Configuration-ID-rl7 ::= SEQUENCE { nr-dl-prs-configuration-id-rl7 INTEGER (L.maxOD-DL-PRS-Configs- rl7), On-Demand-DL-PRS-Configuration-rl8 ::= SEQUENCE { dl-prs-configuration-id-r 18 DL-PRS-Configuration-ID-rl 8, nr-DL-PRS-Info-rl 8 NR-DL-PRS-Info-r 16, / / {linked or aggregated PRSs}

[0057] In the second option, 3GPP TS 37.355 be updated as follows:- ASN1 STARTNR-On-Demand-DL-PRS-Configurations-rl8 ::= SEQUENCE { on-demand- dl-prs-configuration-list-rl 8 SEQUENCE (SIZE (1. maxOD-DL-PRS-Configs- rl8)) OF On-Demand-DL-PRS-Configuration-rl8,PRS aggregation index ::= SEQUENCE{ configured on Type rl 8 SEQUENCE (SIZE (L .maxOD-DL-PRS-Configs-rl8)) OF {O or l }, ...}. / / 0 => rel-17, 1 => rel-=18On-Demand-DL-PRS-Configuration-rl8 ::= SEQUENCE { dl-prs-configuration-id-r 18 DL-PRS-Configuration-ID-rl 8, nr-DL-PRS-PositioningFrequencyLayer-rl8 SEQUENCE (SIZE (L.max- aggregated-Configs-rl8)) OF NR-DL-PRS-PositioningFrequencyLayer-rl6, nr-DL-PRS-Info-rl 8 SEQUENCE (SIZE (1. max- aggregated-Configs-rl8)) OF NR-DL-PRS-Info-rl6, nr-DL-PRS-Info-aggregated-size-r 18 INTEGER(1 ...3),}DL-OD-PRS-Configuration-ID-rl8 ::= SEQUENCE { nr-dl-prs-configuration-id-rl8 INTEGER (E.maxOD-DL-PRS-Configs-rl8),}- ASN1STOP

[0058] The element maxOD-DL-PRS-Configs-r 18 is a maximum number of On Demand (OD) DL PRS configurations. The element max-aggregated-Configs-rl8 is a maximum number of configurations that can be aggregated (e.g., three). Each can have its own PFL and PRS Info that is equivalent to the Rel-16 PFL definitions. For example, when the maximum is two, then nr-DL-PRS-PositioningFrequencyLayer-rl8 will be {PFLx, PFLx}. For example, when the maximum is three, then the sequence will be {PFLx, PFLy, PFLz} and nr-DL-PRS-Info-r 18 will be {PRSInfox, PRSInfoy, PRSInfoz}. This may allow both the Rel-17 and Rel-18 definitions simultaneously. In some implementations, when using the Rel-17 definition, themax-aggregated-configs-r 18 can be set to 1. In some implementations, when it can set it to 3 and use a PRS-aggregation-size field to indicate the size needed. The size can be set in On- Demand-DL-PRS-Configuration-r 18 in which case, additional information in the sub-fields may be skipped (e.g., ignored), and / or DL-OD-PRS-Configuration-ID-r 18 in which case the max-aggregated-Configs-r 18 is configuration specific. In this case, the configuration is as follows:- ASN1 STARTNR-On-Demand-DL-PRS-Configurations-rl8 ::= SEQUENCE { on-demand-dl-prs-configuration-list-rl8 SEQUENCE (SIZE (l..maxOD-DL-PRS- Configs-rl8)) OFOn-Demand-DL-PRS-Configuration-rl8,On-Demand-DL-PRS-Configuration-rl8 ::= SEQUENCE { dl-prs-configuration-id-r 18 DL-PRS-Configuration-ID-rl 8, nr-DL-PRS-PositioningFrequencyLayer-rl 8 SEQUENCE (SIZE (1..max- aggregated-Configs-rl8)) OF NR-DL-PRS-PositioningFrequencyLayer-rl6, nr-DL-PRS-Info-rl8 SEQUENCE (SIZE (E.max-aggregated-Configs-rl8)) OF NR-DL-PRS-Info-rl6, OPTION 1 : nr-DL-PRS-Info-aggregated-size-r 18 INTEGER(1 ...3),}DL-PRS-Configuration-ID-rl 8 ::= SEQUENCE { nr-dl-prs-configuration-id-rl8 INTEGER (l..maxOD-DL-PRS-Configs- rl8),OPTION 2: nr-max-aggregated-Configs-rl 8 INTEGER (1 ...3)}- ASN1STOP

[0059] In the first option, PRS aggregation indicates if using legacy method (0) or using aggregation (1). If (0), then nr-DL-PRS-PositioningFrequencyLayer-rl7 and nr-DL-PRS- Info-rl7 are used. If (1) then nr-DL-PRS-PositioningFrequencyLayer-rl8 and nr-DL-PRS- Info-rl8 are used.

[0060] In second option, 3GPP TS 37.355 can be updated as follows:- ASN1 STARTNR-On-Demand-DL-PRS-Configurations-rl8 ::= SEQUENCE { on-demand- dl-prs-configuration-list-r 18 SEQUENCE (SIZE (1..maxOD-DL-PRS- Configs-rl8)) OF On-Demand-DL-PRS-Configuration-rl8, PRS aggregation index ::= SEQUENCE{ configured on Type r 18 SEQUENCE (SIZE (l..maxOD-DL-PRS-Configs-rl8)) OF {O or l }, ...}. / / 0 => rel-17, 1 => rel-=18On-Demand-DL-PRS-Configuration-rl8 ::= SEQUENCE { dl-prs-configuration-id-r 18 DL-PRS-Configuration-ID-rl 8, nr-DL-PRS-Info-rl8 NR-DL-PRS-Info-rl6, / / {linked or aggregated PRSs}}DL-PRS-Configuration-ID-rl 8 ::= SEQUENCE { nr-dl-prs-configuration-id-rl8 INTEGER (l..maxOD-DL-PRS-Configs- rl7),}- ASN1STOP

[0061] Also in the second option, The dl-prs-configuration-id field provides an identity for the On-Demand-DL-PRS-Configuration. The dl _prs aggregation field indicates if aggregated or not, and can be 0 (not aggregated) or 1 (aggregated). If (0), then nr-DL-PRS- PositioningFrequencyLayer-r 17 and nr-DL-PRS-Info-r 17 are used. If (1) then nr-DL-PFL- group-id-rl8 is used.

[0062] The dl-prs-configuration-id field provides an identity for the On-Demand-DL-PRS- Configuration. PRS Aggregation flag-r!8 field indicates if R18 aggregated or R17 not aggregated is selected.

[0063] The IE NR-On-Demand-DL-PRS-Information from 3GPP TS 37.355 defines the requested on-demand aggregated DL-PRS. Each UE has a maximum number of frequency layers (e.g., 4) and a request can be transmitted for each of them. The parameters requested can be different for each PFL. PFLs can be grouped together, so when the maximum is four, a request can be transmitted for each layer. For example, a request can be transmitted for two layers, for three layers, and / or for all the layers.

[0064] In some implementations, the IE NR-On-Demand-DL-PRS-PerFreqLayer-rl7 can be changed to NR-On-Demand-DL-PRS-PerAggregatedResources-rl8 and nr-MaxFreqLayers- rl6 can be changed to nrMaxAggregatedResource-r 18. The IE nrMaxAggregatedResource- rl8 can be configured by the LMF and the size can be based on a UE capability (e.g., the UE can set a maximum on N, and / or the UE may be limited to setting a maximum in groups of nr- MaxFreqLayers-rl6). The resource bandwidth (BW) may be set for each PFL separately and / or indicate the resource to be used.

[0065] In some implementations, th NR-On-Demand-DL-PRS-Information IE can be updated. In some implementations, 3GPP TS 37.355 can be updated as follows:- ASN1 STARTNR-On-Demand-DL-PRS-Information-rl7 ::= SEQUENCE (SIZE (1..nrMaxFreqLayers rl6 nrMaxAggregatedResource-r!8)) OF NR On Demand DL PRS PerFreqLayer rl7 NR-On-Demand-DL-PRS-PerAggregatedResources-rl8 NR-On-Demand-DL-PRS-PerFreqLayer-rl7 ::= SEQUENCE { dl-prs-FrequencyRangeReq-rl7 ENUMERATED { frl, fr2, ...}, dl-prs-ResourceSetPeriodicityReq-rl7 ENUMERATED { p4, p5, p8, plO, pl6, p20, p32, p40, p64, p80, pl60, p320, p640, pl280, p2560, p5120, pl0240, p20480, p40960, p81920, ...} OPTIONAL, dl prs ResourceBandwidthReq rl7 - INTEGER (1..63)- OPTIONAL,NumberResources ENUMERATED 12, 3, 4,... ! dl-prs-ResourceBandwidthReq-rl8 SEQUENCE (SIZE (1..OF INTEGER OPTIONAL, dl-prs-ResourceRepetitionFactorReq-r!7 ENUMERATED {n2, n4, n6, n8, nl6, n32, ...}OPTIONAL, dl -pr s-Num Sy mb ol sReq-r 17 ENUMERATED {n2, n4, n6, nl2, ...} OPTIONAL, dl-prs-Comb SizeN-Req-r 17 ENUMERATED {n2, n4, n6, nl2, ...}OPTIONAL, dl-prs-QCL-InformationReq-r 17 DL-PRS-QCL-InformationReq-rl 7 OPTIONAL,}DL-PRS-QCL-InformationReq-rl7 ::= SEQUENCE (SIZE (E.nrMaxTRPsPerFreq- rl6)) OFDL-PRS-QCL-InformationReqPerTRP-rl7DL-PRS-QCL-InformationReqPerTRP-rl7 ::= SEQUENCE { dl-PRS-ID-rl7 INTEGER (0..255), nr-Phy sCelUD-r 17 NR-PhysCellID-rl6 OPTIONAL, nr-CellGlobaUD-r 17 NCGI-rl5 OPTIONAL, nr-ARFCN-rl7 ARFCN-ValueNR-rl5 OPTIONAL, dl-prs-QCL-InformationReqSet-rl7 SEQUENCE (SIZE(l ..nrMaxSetsPerTrpPerFreqLayer-rl6)) OF DL-PRS-QCL-InfoReq-rl7,}DL-PRS-QCL-InfoReq-rl7 ::= SEQUENCE { nr-DL-PRS-ResourceSetID-rl7 NR-DL-PRS-ResourceSetID-rl6, dl-prs-QCL-InformationReq-rl7 CHOICE { nr-DL-PRS-QCL-Source-rl7 DL-PRS-QCL-Info-rl6,dl-prs-QCL-Info-requested-rl7 NULL}- ASN1ST0P

[0066] If the UE indicates a capability of processing N PRS within a time duration of T, then simultaneous configuration of Rel-17 + Rell8 demand PRS requests / configurations can satisfy the indicated UE capability.

[0067] In some implementations, the parameters of IE NR-On-Demand-DL-PRS- PerFreqLayer-rl8 are the same for the PRS resources in the group: dl-prs- FrequencyRangeReq-r 17, dl-prs-ResourceSetPeriodicityReq-17, dl-prs-ResourceRepetitionFactorReq-r 17, dl-prs-NumSymbolsReq-r 17, dl-prs-CombSizeN-Req-r 17, and / or dl-prs-QCL-InformationReq-rl 7.

[0068] In some implementations, NumberResources indicates the number of resources that are aggregated. For example, dl-prs-ResourceBandwidthReq-r 17 indicates the resource bandwidth for each resource in the group.

[0069] In some implementations, NumberResources indicates an index of a predefined resource bandwidth with start and bandwidth information.

[0070] On-demand DL PRS can be LMF-initiated or UE-initiated. For a LMF -initiated request of on-demand DL PRS, the group of on-demand DL PRS parameters is defined and signaled per resource set per positioning frequency layer per FR. The group of on-demand DL PRS parameters includes DL PRS Periodicity, DL PRS Resource Bandwidth, DL PRS Resource Repetition Factor, Number of DL PRS Resource Symbols per DL PRS Resource, and / or DL- PRS CombSizeN.

[0071] In some implementations, DL PRS Quasi Co-Location information (QCL-Info) can be indicated per resource set per positioning frequency layer per FR, and the LMF recommends a list of QCL sources. In some implementations, DL PRS QCL-Info can be indicated per resource set per positioning frequency layer per FR, and the LMF requests to provide the QCL information in the assistance data in NRPPa. Per FR includes a number of DL PRS frequency layers. Either per resource set, per positioning frequency layer, or per UE includes a start / end time of DL PRS transmission. Either per resource, per resource set, or per UE includes an ON / OFF indicator (for LMF initiated request only).

[0072] For BW aggregation, for LMF-initiated request of on-demand DL PRS, groups of on- demand DL PRS parameters are defined and signaled. Per PFL group per FR (all PRS resources / PRS resource sets), the parameters include DL PRS Periodicity, DL PRS Resource Repetition Factor, Number of DL PRS Resource Symbols per DL PRS Resource, and / or DL- PRS CombSizeN (agreement that these are common across all PRS resources in the group). Per PRS resource / PRS resource set per FR, the parameters include DL PRS Resource Bandwidth. Per PFL group, the LMF may recommend a list of QCL sources or request to provide QCL information in assistance data. Per Frequency Range (FR), the parameters include a number of DL PRS frequency layers and / or PFL groups.

[0073] For a UE-initiated request of on-demand DL PRS, the group of on-demand DL PRS parameters can be defined and signaled per positioning frequency layer per FR, per FR, or per UE. For per positioning frequency layer per FR, the parameters include DL PRS Periodicity, DL PRS Resource Bandwidth, DL PRS Resource Repetition Factor, Number of DL PRS Resource Symbols per DL PRS Resource, and DL-PRS CombSizeN. For per FR, the parameters include a number of DL PRS frequency layers. For per UE, the parameters include a start / end time of DL PRS. In some implementations, the indication of DL PRS QCL-Info can be per resource set per positioning frequency layer per FR. The UE recommends a list of QCL sources. In some implementations, the indication of DL PRS QCL-Info can be per resource set per positioning frequency layer per FR. The UE requests to provide the QCL information in the assistance data.

[0074] For BW aggregation, for UE-initiated request of on-demand DL PRS, the following group of on-demand DL PRS parameters is defined and signaled: per PFL group per FR (all PRS resources / PRS resource sets): DL PRS Periodicity, DL PRS Resource Repetition Factor, Number of DL PRS Resource Symbols per DL PRS Resource, DL-PRS CombSizeN (agreement that these are common across all PRS resources in the group), per PRS resource / PRS resource set: DL PRS Resource Bandwidth, per Frequency Range (FR): # of DL PRS frequency layers and / or PFL groups, per PFL group: UE may recommend list of QCL sources or request to provide QC information in assistance data.

[0075] The relative priority of the signals for carrier aggregation are PRACH transmission on the PCell then PUCCH or PUSCH transmissions with larger priority index, then PUCCH or PUSCH transmissions with the same priority index then SRS transmission, with aperiodic SRS having higher priority than semi-persistent and / or periodic SRS, or PRACH transmission on aserving cell other than the PCell. For PUCCH or PUSCH transmissions with same priority index, the order is PUCCH transmission with HARQ-ACK information, and / or SR, and / or LRR, or PUSCH transmission with HARQ-ACK information of the priority index, then PUCCH transmission with CSI or PUSCH transmission with CSI, PUSCH transmission without HARQ-ACK information of the priority index or CSI and, for Type-2 random access procedure, PUSCH transmission on the PCell.

[0076] Power control can be enhanced for simultaneous transmission of SRS for SRS bandwidth aggregation. For example, when the total uplink transmission power across multiple carriers exceeds P c, max.

[0077] 3GPP TS 38.213, Section 7.5 includes, for single cell operation with two uplink carriers or for operation with carrier aggregation, if a total UE transmit power for PUSCH or PUCCH or PRACH or SRS transmissions on serving cells in a frequency range in a respective transmission occasion i would exceed PcMAx(i), where PcMAx(i) is the linear value of PcMAx(i) in transmission occasion i as defined in 18-1, 3GPP TS 38.101-11 for FRI and 18- 2, 3GPP TS 38.101-21 for FR2, the UE allocates power to PUSCH / PUCCH / PRACH / SRS transmissions according to the following priority order (in descending order) so that the total UE transmit power for transmissions on serving cells in the frequency range is smaller than or equal to PcMAx(i) for that frequency range in every symbol of transmission occasion i. For the purpose of power allocation in this clause, if a UE is provided and the UE multiplexes HARQ- ACK information in a PUSCH, a priority index of the PUSCH is the larger of (a) the priority index of the PUSCH according to clause 9 and (b) the larger priority index of the HARQ-ACK information. When determining a total transmit power for serving cells in a frequency range in a symbol of transmission occasion i, the UE does not include power for transmissions starting after the symbol of transmission occasion i. The total UE transmit power in a symbol of a slot is defined as the sum of the linear values of UE transmit powers for PUSCH, PUCCH, PRACH, and SRS in the symbol of the slot.

[0078] The same power prioritization as carrier aggregation can be supported between the aggregated carriers in the case when total UE transmit power in a transmission occasion i exceeds Pcmax. The UE allocates power to the multiple SRS resources in the transmission occasion i of the aggregated carriers such that the UE’s transmit power in each transmitted resource element is equal. At least from the UE capability perspective, the UE support ofpositioning SRS bandwidth aggregation in RRC CONNECTED state is decoupled from the UE support of communication CA.

[0079] When bandwidth aggregation is uplink power limited, power can be scaled between aggregated carriers. In some implementations, BW aggregation for positioning is allowed and one or more component carriers (CCs) with SRS may be dropped. In some implementations, the drop is in such a manner as to keep contiguous SRS transmissions. In this case, if two CCs with SRS, and the UE is power limited, then one is dropped (e.g., CC with lower priority). In this case, if three CCs with SRS, and the UE is power limited then SRSs on highest priority carriers are transmitted (keeping contiguous SRS transmission). When this results in noncontiguous transmission, then SRS is not transmitted or a highest priority adjacent CC is selected and SRS is simultaneously transmitted. In some implementations, limited additional channels are allowed to be transmitted simultaneously. For example, there can be no PUCCH, PRACH, and / or PUSCH. In some implementations, a priority across the aggregated subcarriers is changed. If a UE is provided with SRSBWAggregationPriority, then the priority index of the BW aggregated SRS is increased. For example, BW aggregated SRS becomes higher than the PUCCH / PUSCH. In some implementations, the CC is dropped without taking into consideration contiguous SRS transmissions.

[0080] In some implementations, power equality per RE is used to ensure equality in power for each sub-carrier. The system can select a reference CC, estimate power for reference CC, estimate power for additional CC(s) based on EPRE for reference CC, and scale total power to enable transmission at PC max. The reference CC can be configured as the reference CC or selected based on priority rules. In some implementations, the priority rules can include selecting the CC with higher / highest priority signal. In some implementations, in case of a same priority order and for operation with carrier aggregation (e.g., with possible different aggregation from communications), the UE prioritizes power allocation for transmissions on the primary cell of the MCG or the SCG over transmissions on a secondary cell. In case of a same priority order and for operation with two UL carriers, the UE prioritizes power allocation for transmissions on the carrier where the UE is configured to transmit PUCCH. If PUCCH is not configured for any of the two UL carriers, the UE prioritizes power allocation for transmissions on the non-supplementary UL carrier. Scaling the total power may result in transmission not strong enough to reach gNB for good positioning performance. If the effective EPRE is less than a threshold value, then one or more of the CCs can be dropped based on rules.

[0081] In some implementations, power equality can be used with communications and positioning carrier aggregation (CA). For transmission, communication CA and positioning CA are configured. In some implementations, when they overlap entirely, the equal power per RE is enforced. In some implementations, when they are decoupled and do not overlap, then power is allocated to Communications CC and then positioning CCs based on SRS having lower / higher priority. Equal power per RE may be enforced for positioning CCs only. In some implementations, when they are decoupled and have overlap, equal power per RE is common to overlapping communications CC(s) and all power CCs. Power is based on higher priority transmission (e.g., communications CC(s)). The configuration of the communications and positioning CA will depend on UE capability. The capabilities can include the UE supports decoupled CA for positioning and communications, supports complete decouple but no overlap, supports complete decouple but complete overlap, supports partial overlap.

[0082] All the DL PRS resources within one DL PRS resource set are configured with the same following parameters, which define a DL-PRS-ResourceSet . The DL-PRS-ResourceSet includes the following. DL-PRS-ResourceSetld. DL-PRS-Periodicity. TeRrsG 2^ {4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 160, 320, 640, 1280, 2560, 5120, 10240}slots. DL-PRS- ResourceRepetitionFacto . TrPRSG {1,2,4,6,8,16,32}, which is how many times each DL-PRS resource is repeated for a single instance. DL-PRS-ResourceTimeGap'. TgpaRSG {1,2,4,8,16,32} slot, which is the offset in number of slots between two repeated instances of a DL PRS resource with the same DL-PRS-ResourcelD . The time duration spanned by one instance of a DL-PRS is not expected to exceed the configured value of DL-PRS-Periodicity. DL-PRS- ResourceSetSlotOffset'. T^setG {0,1,— 1} the slot offset with respect to SFN0 slot0. DL-PRS-CombSizeN'. Kcombe{2,4,6,12}. DL-PRS-ResourceBandwidth'. number of resource blocks configured for PRS transmission. The parameter has a granularity of 4 PRBs with a minimum of 24 PRBs and a maximum of 272 PRBs. DL-PRS-StartPRB'. starting PRB index of the DL PRS resource with respect to reference Point A. The starting PRB index has a granularity of one PRB with a minimum value of 0 and a maximum value of 2176 PRBs. DL- PRS-MutingPatterrr. defines a bitmap of the time locations where the DL PRS resource is expected to not be transmitted for a DL PRS resource set.

[0083] A DL-PRS-Resource is defined by the following. DL-PRS-Resourceld. All DL PRS resource IDs are locally defined within a DL PRS resource set. DL-PRS-Sequenceld. nsseqG {0,1, ... ,4095} to initialize cinit value used in pseudo random generator. PRS sequence isgenerated in each OFDM symbol within the slot in which PRS is sent DL-PRS-ReOffset'.~ 1} defines the starting RE offset of the first PRS symbol. DL-PRS- ResourceSlotOffset'. Toffset.res G {0,1, .. .,511} starting slot of the DL PRS resource with respect to corresponding DL-PRS-ResourceSetSlotOffset. dl-PRS-ResourceSymbolOffset-r 16 Is^arte{0'1, . . . ,12} symbol offset within a PRS slot. DL-PRS-NumSymbols'. LPRSE {2,4,6,12} number of symbols of the DL PRS resource within a slot {LPRS, KcombJ is one°f {2, 2}, {4, 2}, {6, 2}, { 12, 2}, {4, 4}, { 12, 4}, {6, 6}, { 12, 6} and { 12, 12}. DL-PRS-QCL-Info-. QCL info of the DL PRS resource with other reference signals. The DL PRS may be configured to be 'QCL-Type-D1with a DL PRS or SS / PBCH Block from a serving cell or a non-serving cell. The DL PRS may be configured to be 'QCL-Type-C with a SS / PBCH Block from a serving or non-serving cell. If the DL PRS is configured as both 'QCL-Type-C and 'QCL- Type-D' with a SS / PBCH Block then the SSB index indicated should be the same. If the UE is configured with DL-PRS-QCL-Info and the QCL relation is between two DL PRS resources, then the UE assumes those DL PRS resources are from the same cell.

[0084] FIG. 3 illustrates a flowchart of an example method 300, according to some implementations. For clarity of presentation, the description that follows generally describes method 300 in the context of the other figures in this description. For example, method 300 can be performed by UE 102 of FIG. 1. It will be understood that method 300 can be performed, for example, by any suitable system, environment, software, hardware, or a combination of systems, environments, software, and hardware, as appropriate. In some implementations, various steps of method 300 can be run in parallel, in combination, in loops, or in any order.

[0085] At 302, method 300 involves determining a time window for measuring a PRS or transmitting a SRS.

[0086] At 304, method 300 involves causing the UE to measure the PRS from a TRP using the time window, or transmit the SRS to the TRP using the time window.

[0087] The example method 300 shown in FIG. 3 can be modified or reconfigured to include additional, fewer, or different steps (not shown in FIG. 3), which can be performed in the order shown or in a different order.

[0088] FIG. 4 illustrates a flowchart of an example method 400, according to some implementations. For clarity of presentation, the description that follows generally describesmethod 400 in the context of the other figures in this description. For example, method 400 can be performed by UE 102 of FIG. 1. It will be understood that method 400 can be performed, for example, by any suitable system, environment, software, hardware, or a combination of systems, environments, software, and hardware, as appropriate. In some implementations, various steps of method VI 00 can be run in parallel, in combination, in loops, or in any order.

[0089] At 402, method 400 involves determining a first configuration message for on-demand PRS.

[0090] At 404, method 400 involves causing the UE to transmit the first configuration message for on-demand PRS; and

[0091] At 406, method 400 involves receiving a second configuration message for on-demand PRS including data corresponding to bandwidth aggregation for a set of PFLs.

[0092] The example method 400 shown in FIG. 4 can be modified or reconfigured to include additional, fewer, or different steps (not shown in FIG. 4), which can be performed in the order shown or in a different order.

[0093] FIG. 5 illustrates a flowchart of an example method 500, according to some implementations. For clarity of presentation, the description that follows generally describes method 500 in the context of the other figures in this description. For example, method 500 can be performed by base station 104 of FIG. 1. It will be understood that method 500 can be performed, for example, by any suitable system, environment, software, hardware, or a combination of systems, environments, software, and hardware, as appropriate. In some implementations, various steps of method VI 00 can be run in parallel, in combination, in loops, or in any order.

[0094] At 502, method 500 involves determining that a total uplink transmission power exceeds an allowed transmission power; and

[0095] At 504, method 500 involves restricting bandwidth aggregation to limit the total uplink transmission power.

[0096] The example method 500 shown in FIG. 5 can be modified or reconfigured to include additional, fewer, or different steps (not shown in FIG. 5), which can be performed in the order shown or in a different order.

[0097] FIG. 6 illustrates an example UE 600, according to some implementations. The UE 600 may be similar to and substantially interchangeable with UE 102 of FIG. 1.

[0098] The UE 600 may be any mobile or non-mobile computing device, such as, for example, mobile phones, computers, tablets, industrial wireless sensors (for example, microphones, pressure sensors, thermometers, motion sensors, accelerometers, inventory sensors, electric voltage / current meters, etc.), video devices (for example, cameras, video cameras, etc.), wearable devices (for example, a smart watch), relaxed-IoT devices.

[0099] The UE 600 may include processor 602, RF interface circuitry 604, memory / storage 606, user interface 608, sensors 610, driver circuitry 612, power management integrated circuit (PMIC) 614, one or more antenna(s) 616, and battery 618. The components of the UE 600 may be implemented as integrated circuits (ICs), portions thereof, discrete electronic devices, or other modules, logic, hardware, software, firmware, or a combination thereof. The block diagram of FIG. 6 is intended to show a high-level view of some of the components of the UE 600. However, some of the components shown may be omitted, additional components may be present, and different arrangement of the components shown may occur in other implementations.

[0100] The components of the UE 600 may be coupled with various other components over one or more interconnects 620, which may represent any type of interface, input / output, bus (local, system, or expansion), transmission line, trace, optical connection, etc. that allows various circuit components (on common or different chips or chipsets) to interact with one another.

[0101] The processor 602 may include one or more processors. For example, the processor 602 may include processor circuitry such as, for example, baseband processor circuitry (BB) 622A, central processor unit circuitry (CPU) 622B, and graphics processor unit circuitry (GPU) 622C. The processor 602 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions, such as program code, software modules, or functional processes from memory / storage 606 to cause the UE 600 to perform operations as described herein.

[0102] In some implementations, the baseband processor circuitry 622A may access a communication protocol stack 624 in the memory / storage 606 to communicate over a 3 GPP compatible network. In general, the baseband processor circuitry 622A may access the communication protocol stack to: perform user plane functions at a physical (PHY) layer,medium access control (MAC) layer, radio link control (RLC) layer, packet data convergence protocol (PDCP) layer, service data adaptation protocol (SDAP) layer, and PDU layer; and perform control plane functions at a PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer, and a non-access stratum layer. In some implementations, the PHY layer operations may additionally / altematively be performed by the components of the RF interface circuitry 604. The baseband processor circuitry 622A may generate or process baseband signals or waveforms that carry information in 3 GPP-compatible networks. In some implementations, the waveforms for NR may be based cyclic prefix orthogonal frequency division multiplexing (OFDM) “CP-OFDM” in the uplink or downlink, and discrete Fourier transform spread OFDM “DFT-S-OFDM” in the uplink.

[0103] In some implementations, the processor 602 is configured to perform operations including: determining a time window for measuring a positioning reference signal (PRS) or transmitting a sounding reference signal (SRS); and causing the UE to: measure the PRS from a transmission and reception point (TRP) using the time window; or transmit the SRS to the TRP using the time window.

[0104] In some implementations, the processor 602 is configured to perform operations including: determining a first configuration message for on-demand positioning reference signal (PRS); causing the UE to transmit the first configuration message for on-demand PRS; and receiving a second configuration message for on-demand PRS including data corresponding to bandwidth aggregation for a set of positioning frequency levels (PFLs).

[0105] The memory / storage 606 may include one or more non -transitory, computer-readable media that includes instructions (for example, communication protocol stack 624) that may be executed by the processor 602 to cause the UE 600 to perform various operations described herein. The memory / storage 606 include any type of volatile or non-volatile memory that may be distributed throughout the UE 600. In some implementations, some of the memory / storage 606 may be located on the processor 602 itself (for example, LI and L2 cache), while other memory / storage 606 is external to the processor 602 but accessible thereto via a memory interface. The memory / storage 606 may include any suitable volatile or non-volatile memory such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM), Flash memory, solid-state memory, or any other type of memory device technology.

[0106] The RF interface circuitry 604 may include transceiver circuitry and radio frequency front module (RFEM) that allows the UE 600 to communicate with other devices over a radio access network. The RF interface circuitry 604 may include various elements arranged in transmit or receive paths. These elements may include, for example, switches, mixers, amplifiers, filters, synthesizer circuitry, control circuitry, etc.

[0107] In the receive path, the RFEM may receive a radiated signal from an air interface via antenna(s) 616 and proceed to filter and amplify (with a low-noise amplifier) the signal. The signal may be provided to a receiver of the transceiver that downconverts the RF signal into a baseband signal that is provided to the baseband processor of the processor 602.

[0108] In the transmit path, the transmitter of the transceiver up-converts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM may amplify the RF signal through a power amplifier prior to the signal being radiated across the air interface via the antenna(s) 616. In various implementations, the RF interface circuitry 604 may be configured to transmit / receive signals in a manner compatible with NR access technologies.

[0109] The antenna(s) 616 may include one or more antenna elements to convert electrical signals into radio waves to travel through the air and to convert received radio waves into electrical signals. The antenna elements may be arranged into one or more antenna panels. The antenna(s) 616 may have antenna panels that are omnidirectional, directional, or a combination thereof to enable beamforming and multiple input, multiple output communications. The antenna(s) 616 may include microstrip antennas, printed antennas fabricated on the surface of one or more printed circuit boards, patch antennas, phased array antennas, etc. The antenna(s) 616 may have one or more panels designed for specific frequency bands including bands in FR1 or FR2.

[0110] The user interface 608 includes various input / output (VO) devices designed to enable user interaction with the UE 600. The user interface 608 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual means for accepting an input including, inter alia, one or more physical or virtual buttons (for example, a reset button), a physical keyboard, keypad, mouse, touchpad, touchscreen, microphones, scanner, headset, or the like. The output device circuitry includes any physical or virtual means for showing information or otherwise conveying information, such as sensor readings, actuator position(s), or other like information. Output device circuitry may include any number orcombinations of audio or visual display, including, inter alia, one or more simple visual outputs / indicators (for example, binary status indicators such as light emitting diodes “LEDs” and multi -character visual outputs), or more complex outputs such as display devices or touchscreens (for example, liquid crystal displays “LCDs,” LED displays, quantum dot displays, projectors, etc.), with the output of characters, graphics, multimedia objects, and the like being generated or produced from the operation of the UE 600.[OHl] The sensors 610 may include devices, modules, or subsystems whose purpose is to detect events or changes in its environment and send the information (sensor data) about the detected events to some other device, module, subsystem, etc. Examples of such sensors include, inter alia, inertia measurement units including accelerometers, gyroscopes, or magnetometers; microelectromechanical systems or nanoelectromechanical systems including 3-axis accelerometers, 3-axis gyroscopes, or magnetometers; level sensors; temperature sensors (for example, thermistors); pressure sensors; image capture devices (for example, cameras or lensless apertures); light detection and ranging sensors; proximity sensors (for example, infrared radiation detector and the like); depth sensors; ambient light sensors; ultrasonic transceivers; microphones or other like audio capture devices; etc.

[0112] The driver circuitry 612 may include software and hardware elements that operate to control particular devices that are embedded in the UE 600, attached to the UE 600, or otherwise communicatively coupled with the UE 600. The driver circuitry 612 may include individual drivers allowing other components to interact with or control various input / output (I / O) devices that may be present within, or connected to, the UE 600. For example, driver circuitry 612 may include a display driver to control and allow access to a display device, a touchscreen driver to control and allow access to a touchscreen interface, sensor drivers to obtain sensor readings of sensors 610 and control and allow access to sensors 610, drivers to obtain actuator positions of electro-mechanic components or control and allow access to the electro-mechanic components, a camera driver to control and allow access to an embedded image capture device, audio drivers to control and allow access to one or more audio devices.

[0113] The PMIC 614 may manage power provided to various components of the UE 600. In particular, with respect to the processor 602, the PMIC 614 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion.

[0114] In some implementations, the PMIC 614 may control, or otherwise be part of, various power saving mechanisms of the UE 600. A battery 618 may power the UE 600, although insome examples the UE 600 may be mounted deployed in a fixed location, and may have a power supply coupled to an electrical grid. The battery 618 may be a lithium ion battery, a metal-air battery, such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, and the like. In some implementations, such as in vehicle-based applications, the battery 618 may be a typical lead-acid automotive battery.

[0115] FIG. 7 illustrates an example access node 700 (e.g., a base station or gNB), according to some implementations. The access node 700 may be similar to and substantially interchangeable with base station 104. The access node 700 may include processor 702, RF interface circuitry 704, core network (CN) interface circuitry 706, memory / storage circuitry 708, and one or more antenna(s) 710.

[0116] The components of the access node 700 may be coupled with various other components over one or more interconnects 712. The processor 702, RF interface circuitry 704, memory / storage circuitry 708 (including communication protocol stack 714), antenna(s) 710, and interconnects 712 may be similar to like-named elements shown and described with respect to FIG. 6. For example, the processor 702 may include processor circuitry such as, for example, baseband processor circuitry (BB) 716A, central processor unit circuitry (CPU) 716B, and graphics processor unit circuitry (GPU) 716C. The processor 702 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions, such as program code, software modules, or functional processes from memory / storage circuitry 708 to cause the access node 700 to perform operations as described herein.

[0117] In some implementations, the processor 702 is configured to perform operations including determining that a total uplink transmission power exceeds an allowed transmission power; and restricting bandwidth aggregation to limit the total uplink transmission power.

[0118] The CN interface circuitry 706 may provide connectivity to a core network, for example, a 5th Generation Core network (5GC) using a 5GC -compatible network interface protocol such as carrier Ethernet protocols, or some other suitable protocol. Network connectivity may be provided to / from the access node 700 via a fiber optic or wireless backhaul. The CN interface circuitry 706 may include one or more dedicated processors or FPGAs to communicate using one or more of the aforementioned protocols. In some implementations, the CN interface circuitry 706 may include multiple controllers to provide connectivity to other networks using the same or different protocols.

[0119] As used herein, the terms “access node,” “access point,” or the like may describe equipment that provides the radio baseband functions for data and / or voice connectivity between a network and one or more users. These access nodes can be referred to as BS, gNBs, RAN nodes, eNBs, NodeBs, RSUs, TRxPs or TRPs, and so forth, and can include ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). As used herein, the term “NG RAN node” or the like may refer to an access node 700 that operates in an NR or 5G system (for example, a gNB), and the term “E-UTRAN node” or the like may refer to an access node 700 that operates in an LTE or 4G system (e.g., an eNB). According to various implementations, the access node 700 may be implemented as one or more of a dedicated physical device such as a macrocell base station, and / or a low power (LP) base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.

[0120] In some implementations, all or parts of the access node 700 may be implemented as one or more software entities running on server computers as part of a virtual network, which may be referred to as a CRAN and / or a virtual baseband unit pool (vBBUP). In V2X scenarios, the access node 700 may be or act as a “Road Side Unit.” The term “Road Side Unit” or “RSU” may refer to any transportation infrastructure entity used for V2X communications. An RSU may be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, where an RSU implemented in or by a UE may be referred to as a “UE-type RSU,” an RSU implemented in or by an eNB may be referred to as an “eNB-type RSU,” an RSU implemented in or by a gNB may be referred to as a “gNB-type RSU,” and the like.

[0121] Various components may be described as performing a task or tasks, for convenience in the description. Such descriptions should be interpreted as including the phrase “configured to.” Reciting a component that is configured to perform one or more tasks is expressly intended not to invoke 35 U.S.C. § 112(f) interpretation for that component.

[0122] For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, or methods as set forth in the example section below. For example, the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc. asdescribed above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.Examples

[0123] In the following sections, further exemplary embodiments are provided.

[0124] Example 1 includes one or more processors of a user equipment (UE) configured to perform operations including: determining a time window for measuring a positioning reference signal (PRS) or transmitting a sounding reference signal (SRS); and causing the UE to: measure the PRS from a transmission and reception point (TRP) using the time window; or transmit the SRS to the TRP using the time window.

[0125] Example 2 is the one or more processors of Example 1, wherein the operations include: determining a second time window for measuring the PRS or transmitting another SRS by a positioning reference unit (PRU).

[0126] Example 3 is the one or more processors of Examples 1 or 2, wherein the second time window is at least one of: at exactly the same time as the time window; at approximately the same time as the time window; across slots from the time window; or at a fixed offset from the time window.

[0127] Example 4 is the one or more processors of any of Examples 1 to 3, wherein causing the UE to measure the PRS from the TRP includes causing the UE to measure the PRS from the TRP at the approximately the same time as the PRU.

[0128] Example 5 is the one or more processors of any of Examples 1 to 4, wherein causing the UE to transmit the SRS to the TRP includes causing the UE to transmit the SRS to the TRP at the approximately the same time as the PRU.

[0129] Example 6 is the one or more processors of any of Examples 1 to 5, wherein the time window for the UE is mapped to the second time window for the PRU.

[0130] Example 7 is the one or more processors of any of Examples 1 to 6, wherein the time window for measuring a PRS or transmitting a SRS includes an enhanced scheduled location time.

[0131] Example 8 is the one or more processors of any of Examples 1 to 7, where the operations include: determining that a target device supports localized location requests; and responsiveto determining that a target device supports localized location requests, causing the UE to measure at least one of DL RSCP or UL RSCP at a reference time.

[0132] Example 9 is the one or more processors of any of Examples 1 to 8, wherein the time window for measuring the PRS or transmitting the SRS is determined from a field indicating a specific time, a time range, or a relative time from a reference.

[0133] Example 10 includes one or more processors of a user equipment (UE) configured to perform operations including: determining a first configuration message for on-demand positioning reference signal (PRS); causing the UE to transmit the first configuration message for on-demand PRS; and receiving a second configuration message for on-demand PRS including data corresponding to bandwidth aggregation for a set of positioning frequency levels (PFLs).

[0134] Example 11 is the one or more processors of Example 10, wherein the set of PFLs are determined using at least one of (a) PRS resource sets or (b) PFL resources in different PFLs.

[0135] Example 12 is the one or more processors of Examples 10 or 11, wherein the operations include: determining that the UE supports aggregated configurations; and responsive to determining that the UE supports aggregated configurations, determining the set of PFLs using a size indicated by a PRS Configuration.

[0136] Example 13 is the one or more processors of any of Examples 10 to 12, wherein the operations include determining the set of PFLs using a positioning frequency layer group.

[0137] Example 14 is the one or more processors of any of Examples 10 to 13, wherein the second configuration message for on-demand PRS satisfy a number of PRS the UE can process within a duration.

[0138] Example 15 is the one or more processors of any of Examples 10 to 14, wherein the set of PFLs include PFL resources, and / or PFL resource sets and / or PFL groups.

[0139] Example 16 is the one or more processors of any of Examples 10 to 15, wherein the on- demand PRS is initiated by the UE or a location management function (LMF).

[0140] Example 17 is the one or more processors of any of Examples 10 to 16, wherein the operations include receiving an indication that the UE supports on-demand PRS request for bandwidth aggregation.

[0141] Example 18 includes one or more processors of a based station configured to perform operations including: determining that a total uplink transmission power exceeds an allowed transmission power; and restricting bandwidth aggregation to limit the total uplink transmission power.

[0142] Example 19 is the one or more processors of Example 18, wherein restricting bandwidth aggregation includes dropping one or more component carriers (CCs) with sounding reference signal (SRS) when bandwidth aggregation for positioning is allowed.

[0143] Example 20 is the one or more processors of Examples 18 or 19, wherein the operations include: determining that restricting bandwidth aggregation results in non-contiguous; and at least one of (1) skipping sounding reference signal (SRS) transmission, or (2) selecting a highest priority adjacent component carrier (CC) and simultaneously transmitting SRS.

[0144] Example 21 is the one or more processors of any of Examples 18 to 20, wherein restricting bandwidth aggregation includes simultaneously transmitting limited additional channels.

[0145] Example 22 is the one or more processors of any of Examples 18 to 21, wherein restricting bandwidth aggregation includes changing a priority across the aggregated subcarriers.

[0146] Example 23 is the one or more processors of any of Examples 18 to 22, wherein restricting bandwidth aggregation includes: selecting a reference component carrier (CC); determining an estimated power for reference CC; determining at least one other estimated power for least one other CC; and scaling the total uplink transmission power to enable transmission at the allowed transmission power.

[0147] Example 24 is the one or more processors of any of Examples 18 to 23, wherein the operations include: determining power equality based on UE capabilities

[0148] Example 25 is the one or more processors of any of Examples 18 to 24, wherein the operations include: determining a power associated with a first component carrier (CC); and associating the power with at least one second CC that is different from the first CC.

[0149] Example 26 includes one or more processors of a computing device configured to perform operations including: determining a positioning reference signal (PRS) configurationmessage including data corresponding to bandwidth aggregation for a set of PFLs; and causing the computing device to transmit the PRS configuration message to a user equipment (UE).

[0150] Example 27 includes one or more processors of a user equipment (UE) configured to perform operations including: determining a time window for measuring a positioning reference signal (PRS) or transmitting a sounding reference signal (SRS); measuring the PRS based on the time window; and causing the UE to transmit the SRS based on the time window.

[0151] Example 28 may include one or more non-transitory computer-readable media including instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1-27, or any other method or process described herein.

[0152] Example 29 may include an apparatus including logic, modules, and / or circuitry (e.g., processing circuitry) to perform one or more elements of a method described in or related to any of examples 1-27, or any other method or process described herein.

[0153] Example 30 may include a method, technique, or process as described in or related to any of examples 1-27, or portions or parts thereof.

[0154] Example 31 may include an apparatus including: one or more processors and one or more computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-27, or portions thereof.

[0155] Example 32 may include a signal as described in or related to any of examples 1-27, or portions or parts thereof.

[0156] Example 33 may include a computer program including instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples 1-27, or portions thereof. The operations or actions performed by the instructions executed by the processing element can include the methods of any one of examples 1-27.

[0157] Example 34 may include a method of communicating in a wireless network as shown and described herein.

[0158] Example 35 may include a system for providing wireless communication as shown and described herein. The operations or actions performed by the system can include the methods of any one of examples 1-27.

[0159] Example 36 may include a device for providing wireless communication as shown and described herein. The operations or actions performed by the device can include the methods of any one of examples 1-27.

[0160] The previously-described examples 1-27 are implementable using a computer- implemented method; a non-transitory, computer-readable medium storing computer-readable instructions to perform the computer-implemented method; and a computer system including a computer memory interoperably coupled with a hardware processor configured to perform the computer-implemented method or the instructions stored on the non-transitory, computer- readable medium.

[0161] A system, e.g., a base station, an apparatus including one or more baseband processors, and so forth, can be configured to perform particular operations or actions by virtue of having software, firmware, hardware, or a combination of them installed on the system that in operation causes or cause the system to perform the actions. The operations or actions performed either by the system can include the methods of any one of examples 1-27.

[0162] Any of the above-described examples may be combined with any other example (or combination of examples), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

[0163] Although the embodiments above have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to embrace all such variations and modifications.

[0164] It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled so as to minimize risks ofunintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.

Claims

CLAIMSWe Claim:

1. One or more processors configured to cause a user equipment (UE) to perform operations comprising: determining a time window for measuring a positioning reference signal (PRS) or transmitting a sounding reference signal (SRS); and measuring the PRS from a transmission and reception point (TRP) using the time window; or transmitting the SRS to the TRP using the time window.

2. The one or more processors of claim 1, the operations comprising: determining a second time window for measuring the PRS or transmitting another SRS by a positioning reference unit (PRU).

3. The one or more processors of claim 2, wherein the second time window is at least one of: at the same time as the time window; at approximately the same time as the time window; across slots from the time window; or at a fixed offset from the time window.

4. The one or more processors of claim 2, wherein causing the UE to measure the PRS from the TRP comprises causing the UE to measure the PRS from the TRP at the approximately the same time as the PRU.

5. The one or more processors of claim 2, wherein causing the UE to transmit the SRS to the TRP comprises causing the UE to transmit the SRS to the TRP at the approximately the same time as the PRU.

6. The one or more processors of claim 2, wherein the time window for the UE is mapped to the second time window for the PRU.

7. The one or more processors of claim 2, wherein the time window for measuring a PRS or transmitting a SRS includes an enhanced scheduled location time.

8. The one or more processors of claim 1, the operations comprising: determining that a target device supports localized location requests; and responsive to determining that a target device supports localized location requests, causing the UE to measure at least one of DL RSCP or UL RSCP at a reference time.

9. The one or more processors of claim 1, wherein the time window for measuring the PRS or transmitting the SRS is determined from a field indicating a specific time, a time range, or a relative time from a reference.

10. One or more processors of a user equipment (UE) configured to perform operations comprising: determining a first configuration message for on-demand positioning reference signal (PRS); causing the UE to transmit the first configuration message for on-demand PRS; and receiving a second configuration message for on-demand PRS comprising data corresponding to bandwidth aggregation for a set of positioning frequency levels (PFLs).

11. The one or more processors of claim 10, wherein the set of PFLs are determined using at least one of (a) PRS resource sets or (b) PFL resources in different PFLs.

12. The one or more processors of claim 10, the operations comprising: determining that the UE supports aggregated configurations; and responsive to determining that the UE supports aggregated configurations, determining the set of PFLs using a size indicated by a PRS Configuration.

13. The one or more processors of claim 10, the operations comprising: determining the set of PFLs using a positioning frequency layer group.

14. The one or more processors of claim 10, wherein the second configuration message for on-demand PRS satisfy a number of PRS the UE can process within a duration.

15. The one or more processors of claim 10, wherein the set of PFLs include PFL resources, and / or PFL resource sets and / or PFL groups.

16. The one or more processors of claim 10, wherein the on-demand PRS is initiated by the UE or a location management function (LMF).

17. The one or more processors of claim 10, the operations comprising: receiving an indication that the UE supports on-demand PRS request for bandwidth aggregation.

18. One or more processors of a base station configured to perform operations comprising: determining that a total uplink transmission power exceeds an allowed transmission power; and restricting bandwidth aggregation to limit the total uplink transmission power.

19. The one or more processors of claim 18, wherein restricting bandwidth aggregation comprises dropping one or more component carriers (CCs) with sounding reference signal (SRS) when bandwidth aggregation for positioning is allowed.

20. The one or more processors of claim 18, the operations comprising: determining that restricting bandwidth aggregation results in non-contiguous; and at least one of (1) skipping sounding reference signal (SRS) transmission, or (2) selecting a highest priority adjacent component carrier (CC) and simultaneously transmitting SRS.

21. The one or more processors of claim 18, wherein restricting bandwidth aggregation comprises simultaneously transmitting limited additional channels.

22. The one or more processors of claim 18, wherein restricting bandwidth aggregation comprises changing a priority across the aggregated sub-carriers.

23. The one or more processors of claim 18, wherein restricting bandwidth aggregation comprises: selecting a reference component carrier (CC); determining an estimated power for reference CC; determining at least one other estimated power for least one other CC; andscaling the total uplink transmission power to enable transmission at the allowed transmission power.

24. The one or more processors of claim 18, the operations comprising: determining power equality based on UE capabilities.

25. The one or more processors of claim 18, the operations comprising: determining a power associated with a first component carrier (CC); and associating the power with at least one second CC that is different from the first CC.

26. A non-transitory computer storage medium encoded with instructions that, when executed, cause at least one processor to perform the operations of any of claims 1 to 25.

27. A system comprising at least one processor and at least one storage device storing instructions executable by the at least one processor to cause the at least one processor to perform the operations of any of claims 1 to 25.

28. An apparatus comprising at least one processor and at least one storage device storing instructions executable by the at least one processor to cause the at least one processor to perform the operations of any of claims 1 to 25.

29. A method for performing the operations of any of claims 1 to 25.

Images