Sidelink Measurement Gaps for Positioning

Abstract

Techniques for wireless positioning are disclosed. In one aspect, a user equipment (UE) may determine a sidelink measurement gap (SL-MGP) for positioning. The UE may perform sidelink positioning during the SL-MGP, where performing the SL positioning includes transmitting or receiving at least one sidelink positioning reference signal (SL-PRS). In another aspect, a network entity, such as a base station or a location server, may receive first information from the UE indicating an SL-PRS processing capability of the UE. The network entity may determine the SL-MGP based at least in part on the first information. The network entity may send second information indicating the SL-MGP to the UE.

Description

[Technical field]

[0001] 1. Field of disclosure Aspects of the present disclosure relate generally to wireless communications. [Background technology]

[0002] 2. Description of Related Technology Wireless communication systems have evolved through various generations, including first-generation analog wireless telephone service (1G), second-generation (2G) digital wireless telephone service (including interim 2.5G and 2.75G networks), third-generation (3G) high-speed data, Internet-enabled wireless service, and fourth-generation (4G) service (e.g., Long Term Evolution (LTE) or WiMax). Currently, many different types of wireless communication systems are in use, including cellular systems and personal communications service (PCS) systems. Examples of known cellular systems include the cellular analog advanced mobile phone system (AMPS), and digital cellular systems based on code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), Global System for Mobile communications (GSM), and the like.

[0003] The fifth generation (5G) wireless standard, called New Radio (NR), will enable higher data rates, more connections, and better coverage, among other improvements. The 5G standard is designed to provide higher data rates, more accurate positioning (e.g., based on reference signals for positioning (RS-P), such as downlink, uplink, or sidelink positioning reference signals (PRS)), and other technical enhancements compared to previous standards, according to the Next Generation Mobile Network Alliance.

[0004] In particular, vehicle-to-everything (V2X) communication technologies are being implemented to leverage 5G's increased data rates and reduced latency to support autonomous driving applications, such as wireless communications between vehicles, between vehicles and roadside infrastructure, between vehicles and pedestrians, etc. Summary of the Invention [Means for solving the problem]

[0005] The following provides a simplified summary of one or more aspects disclosed herein. As such, the following summary is not intended to be an extensive overview of all contemplated aspects, nor is it intended to identify key or critical elements of all contemplated aspects or to delineate the scope of any particular aspect. Thus, the sole purpose of the following summary is to present certain concepts of one or more aspects of the mechanisms disclosed herein in a simplified form prior to the detailed description presented below.

[0006] In one aspect, a method of wireless positioning performed by a user equipment (UE) includes determining a sidelink measurement gap for positioning (SL-MGP) and performing sidelink positioning during the SL-MGP using at least one sidelink positioning reference signal (SL-PRS).

[0007] In one aspect, a method of wireless positioning performed by a network entity includes receiving first information from a UE indicating an SL-PRS processing capability of the UE, determining an SL-MGP based at least in part on the first information, and sending second information to the UE indicating the SL-MGP.

[0008] In one aspect, a UE comprises a memory, at least one transceiver, and at least one processor communicatively coupled to the memory and the at least one transceiver, wherein the at least one processor is configured to determine a SL-MGP and perform sidelink positioning during the SL-MGP using the at least one SL-PRS.

[0009] In one aspect, a network entity comprises a memory, at least one transceiver, and at least one processor communicatively coupled to the memory and the at least one transceiver, wherein the at least one processor is configured to receive first information from the UE via the at least one transceiver indicating an SL-PRS processing capability of the UE, determine an SL-MGP based at least in part on the first information, and send second information indicating the SL-MGP to the UE via the at least one transceiver.

[0010] In one aspect, the UE includes means for determining a SL-MGP and means for performing sidelink positioning during the SL-MGP using at least one SL-PRS.

[0011] In one aspect, the network entity includes means for receiving first information from the UE indicating an SL-PRS processing capability of the UE, means for determining an SL-MGP based at least in part on the first information, and means for sending second information to the UE indicating the SL-MGP.

[0012] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a UE, cause the UE to determine a SL-MGP and perform sidelink positioning during the SL-MGP using at least one SL-PRS.

[0013] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a network entity, cause the network entity to receive first information from a UE indicating an SL-PRS processing capability of the UE, determine an SL-MGP based at least in part on the first information, and send second information to the UE indicating the SL-MGP.

[0014] Other objects and advantages associated with the embodiments disclosed herein will become apparent to those skilled in the art based on the accompanying drawings and detailed description.

[0015] The accompanying drawings are presented to aid in the explanation of various aspects of the present disclosure and are provided only to illustrate, not limit, the aspects. [Brief description of the drawings]

[0016] [Figure 1] 1 illustrates an example wireless communication system according to an aspect of the present disclosure. [Figure 2A] 1 illustrates an exemplary wireless network structure in accordance with an aspect of the present disclosure. [Figure 2B] 1 illustrates an exemplary wireless network structure in accordance with an aspect of the present disclosure. [Figure 3A]1 is a simplified block diagram of several sample aspects of components that may be employed in a user equipment (UE) and configured to support communications as taught herein; [Figure 3B] 1 is a simplified block diagram of several sample aspects of components that may be employed in a user equipment (UE) and configured to support communications as taught herein; [Figure 3C] 1 is a simplified block diagram of several sample aspects of components that may be employed in a user equipment (UE) and configured to support communications as taught herein; [Figure 4] FIG. 2 illustrates an example frame structure according to an aspect of the present disclosure. [Diagram 5] 1 is a diagram of an example positioning reference signal (PRS) configuration for a given base station's PRS transmission, in accordance with an aspect of the disclosure. [Figure 6A] 13 illustrates how parameters of a measurement gap configuration specify a pattern of measurement gaps, according to an aspect of the disclosure. [Figure 6B] 1 illustrates positioning reference signals (PRSs) within a PRS occasion within a measurement gap, according to an aspect of the disclosure. [Figure 7] 1 illustrates an example of a wireless communication system supporting unicast sidelink establishment in accordance with an aspect of the present disclosure. [Figure 8] FIG. 1 illustrates an example sidelink ranging and positioning procedure according to an aspect of the present disclosure. [Figure 9] FIG. 1 illustrates an example resource pool for positioning within a sidelink resource pool, according to an aspect of the present disclosure. [Figure 10] FIG. 1 is a time-frequency diagram illustrating an example SL-MGP and resource pools for communication and positioning, according to an aspect of the disclosure. [Figure 11A] 1A-1C are time-frequency diagrams illustrating example SL-MGPs having different durations, according to aspects of the disclosure. [Figure 11B]1A-1C are time-frequency diagrams illustrating example SL-MGPs having different durations, according to aspects of the disclosure. [Figure 11C] 1A-1C are time-frequency diagrams illustrating example SL-MGPs having different durations, according to aspects of the disclosure. [Figure 12] 11 is a flowchart of an example process performed by a UE associated with sidelink measurements and processing gaps for positioning, in accordance with an aspect of the present disclosure. [Figure 13] 13 is a flowchart of an example process 1300 associated with sidelink measurements and processing gaps for positioning, according to an aspect of the disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0017] Techniques for defining and managing SL-MGPs for measuring SL-PRS signals, including techniques by which a UE can advertise its ability to process SL-PRS signals, are presented herein.

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

[0019] The words "exemplary" and / or "example" are used herein to mean "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" and / or "example" should not necessarily be construed as preferred or advantageous over other aspects. Likewise, the term "aspects of the disclosure" does not require that all aspects of the disclosure include the discussed feature, advantage or mode of operation.

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

[0021] Further, many aspects are described in terms of sequences of actions to be performed by, for example, elements of a computing device. It will be appreciated that various activities described herein may be performed by specific circuitry (e.g., application specific integrated circuits (ASICs)), by program instructions executed by one or more processors, or by a combination of both. In addition, the sequence or sequences of actions described herein may be considered to be fully embodied in any form of non-transitory computer-readable storage medium having stored thereon a corresponding set of computer instructions that, when executed, cause or instruct an associated processor of a device to perform the functions described herein. Thus, various aspects of the present disclosure may be embodied in a number of different forms, all of which are contemplated to be within the scope of the claimed subject matter. In addition, for each of the aspects described herein, the corresponding form of any such aspect may be described herein, for example, as "logic configured to" perform the described actions.

[0022] The terms "user equipment" (UE), "vehicle UE" (V-UE), "pedestrian UE" (P-UE), and "base station" as used herein are not intended to be specific or otherwise limited to any particular radio access technology (RAT) unless otherwise specified. In general, a UE may be any wireless communication device (e.g., a computer installed in a vehicle, a vehicle navigation device, a mobile phone, a router, a tablet computer, a laptop computer, an asset positioning device, a wearable (e.g., a smart watch, a smart glass, an augmented reality (AR) / virtual reality (VR) headset, etc.), a vehicle (e.g., a car, a motorcycle, a bicycle, etc.), an Internet of Things (IoT) device, etc.) used by a user to communicate over a wireless communication network. A UE may be mobile or stationary (e.g., at a given time) and may communicate with a radio access network (RAN). As used herein, the term "UE" may be referred to interchangeably as a "mobile device," "access terminal" or "AT," "client device," "wireless device," "subscriber device," "subscriber terminal," "subscriber station," "user terminal" or UT, "mobile terminal," "mobile station," or variations thereof.

[0023] A V-UE is a type of UE and may be any in-vehicle wireless communication device, such as a navigation system, a warning system, a heads-up display (HUD), an on-board computer, an in-vehicle infotainment system, an automated driving system (ADS), an advanced driver assistance system (ADAS), etc. Alternatively, a V-UE may be a portable wireless communication device (e.g., a mobile phone, a tablet computer, etc.) carried by the driver of the vehicle or a passenger in the vehicle. The term "V-UE" may refer to an in-vehicle wireless communication device or the vehicle itself, depending on the context. A P-UE is a type of UE and may be a portable wireless communication device carried by a pedestrian (i.e., a user not driving or riding in the vehicle). In general, a UE can communicate with a core network via a RAN, through which the UE can be connected to external networks such as the Internet and to other UEs. Of course, other mechanisms for connecting to the core network and / or the Internet are possible for the UE, such as via a wired access network, a wireless local area network (WLAN) network (e.g., based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11, etc.), etc.

[0024] Depending on the network in which the base station is deployed, the base station may operate according to one of several RATs in communication with the UE and may alternatively be referred to as an access point (AP), network node, Node B, evolved Node B (eNB), next generation eNB (ng-eNB), new radio (NR) Node B (also referred to as gNB or gNode B), etc. The base station may be used primarily to support wireless access by the UE, including supporting data, voice, and / or signaling connections for supported UEs. In some systems, the base station may provide only edge node signaling functions, while in other systems the base station may provide additional control and / or network management functions. The communication link over which the UE may send signals to the base station is referred to as an uplink (UL) channel (e.g., reverse traffic channel, reverse control channel, access channel, etc.). A communication link through which a base station can send signals to a UE is called a downlink (DL) or forward link channel (e.g., a paging channel, a control channel, a broadcast channel, a forward traffic channel, etc.). As used herein, the term traffic channel (TCH) can refer to either a UL / reverse traffic channel or a DL / forward traffic channel.

[0025] The term "base station" may refer to a single physical transmission-reception point (TRP) or multiple physical TRPs that may or may not be collocated. For example, when the term "base station" refers to a single physical TRP, the physical TRP may be an antenna of the base station, corresponding to a cell (or several cell sectors) of the base station. When the term "base station" refers to multiple collocated physical TRPs, the physical TRP may be an array of antennas of the base station (e.g., as in the case of a multiple-input multiple-output (MIMO) system or when the base station employs beamforming). When the term "base station" refers to multiple non-collocated physical TRPs, the physical TRP may be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transport medium) or a remote radio head (RRH) (a remote base station connected to a serving base station). Alternatively, non-co-located physical TRPs may be serving base stations that receive measurement reports from the UE and neighboring base stations whose reference radio frequency (RF) signals the UE is measuring. Since a TRP is a point from which a base station transmits and receives wireless signals, as used herein, references to transmission from or reception at a base station should be understood as referring to a particular TRP of the base station.

[0026] In some implementations that support positioning of UEs, a base station may not support wireless access by the UE (e.g., may not support data, voice, and / or signaling connections for the UE), but instead may transmit reference RF signals to the UE to be measured by the UE and / or may receive and measure signals transmitted by the UE. Such a base station may be referred to as a positioning beacon (e.g., when it transmits RF signals to the UE) and / or a location measurement unit (e.g., when it receives and measures RF signals from the UE).

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

[0028] 1 illustrates an example wireless communication system 100 according to an aspect of the disclosure. The wireless communication system 100 (sometimes referred to as a wireless wide area network (WWAN)) may include various base stations 102 (labeled "BS") and various UEs 104. The base stations 102 may include macrocell base stations (high-power cellular base stations) and / or small cell base stations (low-power cellular base stations). In an aspect, the macrocell base stations 102 may include eNBs and / or ng-eNBs where the wireless communication system 100 supports an LTE network, or gNBs where the wireless communication system 100 supports an NR network, or a combination of both, and the small cell base stations may include femtocells, picocells, microcells, etc.

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

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

[0031] The base stations 102 may wirelessly communicate with the UEs 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. In an aspect, one or more cells may be supported by the base stations 102 in each geographic coverage area 110. A "cell" is a logical communication entity used for communication with a base station (e.g., over some frequency resources, referred to as a carrier frequency, component carrier, carrier, band, etc.) and may be associated with an identifier (e.g., a physical cell identifier (PCI), an enhanced cell identifier (ECI), a virtual cell identifier (VCI), a cell global identifier (CGI), etc.) to distinguish cells operating over the same or different carrier frequencies. In some cases, different cells may be configured according to different protocol types (e.g., machine-type communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or others) that may provide access for different types of UEs. Because cells are supported by a particular base station, the term "cell" may refer to either or both of the logical communication entity supporting the cell and the base station, depending on the context. In some cases, the term "cell" may also refer to the geographic coverage area (e.g., sector) of a base station, so long as the carrier frequency can be detected and used for communication within some portion of the geographic coverage area 110.

[0032] The geographic coverage areas 110 of neighboring macrocell base stations 102 may overlap partially (e.g., in handover regions) and some of the geographic coverage areas 110 may be substantially overlapped by larger geographic coverage areas 110. For example, a small cell base station 102' (labeled "SC" instead of "small cell") may have a geographic coverage area 110' that significantly overlaps with the geographic coverage area 110 of one or more macrocell base stations 102. A network that includes both small cell base stations and macrocell base stations may be known as a heterogeneous network. A heterogeneous network may also include home eNBs (HeNBs), which may serve closed groups known as closed subscriber groups (CSGs).

[0033] The communication link 120 between the base station 102 and the UE 104 may include uplink (also referred to as reverse link) transmissions from the UE 104 to the base station 102, and / or downlink (DL) (also referred to as forward link) transmissions from the base station 102 to the UE 104. The communication link 120 may use MIMO antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link 120 may be through one or more carrier frequencies. The allocation of carriers may be asymmetric with respect to the downlink and uplink (e.g., more or fewer carriers may be allocated for the downlink than for the uplink).

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

[0035] The small cell base station 102' may operate in licensed and / or unlicensed frequency spectrum. When operating in the unlicensed frequency spectrum, the small cell base station 102' may utilize LTE or NR technology and use the same 5 GHz unlicensed frequency spectrum used by the WLAN AP 150. The small cell base station 102' employing LTE / 5G in the unlicensed frequency spectrum may extend coverage to and / or increase capacity of the access network. NR in the unlicensed spectrum may be referred to as NR-U. LTE in the unlicensed spectrum may be referred to as LTE-U, licensed assisted access (LAA), or MulteFire.

[0036] The wireless communication system 100 may further include a mmW base station 180 that may operate at millimeter wave (mmW) and / or sub-mmW frequencies while communicating with the UE 182. Extremely high frequency (EHF) is a portion of RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength of 1 millimeter to 10 millimeters. Radio waves in this band may be referred to as millimeter waves. Sub-mmW may go down to a frequency of 3 GHz with a wavelength of 100 millimeters. The super high frequency (SHF) band ranges from 3 GHz to 30 GHz and is also referred to as centimeter wave. Communications using the mmW / sub-mmW radio frequency bands have high path loss and relatively short distances. The mmW base station 180 and the UE 182 may utilize beamforming (transmit and / or receive) over the mmW communication link 184 to compensate for the extremely large path loss and short distances. It will be further understood that in alternative configurations, one or more base stations 102 may also transmit using mmW or quasi-mmW and beamforming. Thus, it will be understood that the above illustrations are merely examples and should not be construed as limiting various aspects disclosed herein.

[0037] Transmit beamforming is a technique for concentrating an RF signal in a particular direction. Traditionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts it in all directions (omnidirectionally). With transmit beamforming, the network node determines where a given target device (e.g., UE) is located (relative to the transmitting network node) and launches a stronger downlink RF signal in that particular direction, thereby providing a faster and more powerful RF signal (in terms of data rate) to the receiving device(s). To vary the directionality of the RF signal when transmitting, the network node can control the phase and relative amplitude of the RF signal at each of the one or more transmitters broadcasting the RF signal. For example, the network node may use an array of antennas (also called a "phased array" or "antenna array") that creates beams of RF waves that can be "steered" to point in different directions without actually moving the antennas. Specifically, RF currents from a transmitter are supplied to the individual antennas with the proper phase relationship so that the radio waves from the separate antennas are combined together to enhance radiation in desired directions while suppressing and canceling radiation in undesirable directions.

[0038] A transmit beam may be quasi-co-located, meaning that the transmit beam appears to a receiver (e.g., UE) to have the same parameters regardless of whether the network node's own transmit antenna is physically co-located or not. In NR, there are four types of quasi-co-location (QCL) relationships. Specifically, a QCL relationship of a given type means that some parameters for a second reference RF signal on a second beam can be derived from information about a source reference RF signal on a source beam. Thus, if the source reference RF signal is QCL type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, average delay, and delay spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type B, the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL Type C, the receiver can use the source reference RF signal to estimate the Doppler shift and average delay of a second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL Type D, the receiver can use the source reference RF signal to estimate spatial reception parameters of a second reference RF signal transmitted on the same channel.

[0039] In receive beamforming, a receiver uses a receive beam to amplify RF signals detected on a given channel. For example, the receiver can increase the gain setting and / or adjust the phase setting of an array of antennas in a particular direction to amplify (e.g., increase the gain level) RF signals received from that direction. Thus, when a receiver is said to beamform in some direction, it means that the beam gain in that direction is higher than the beam gains along other directions, or that the beam gain in that direction is highest compared to the beam gains in that direction of all other receive beams available to the receiver. This results in a stronger received signal strength (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), signal-to-interference-plus-noise ratio (SINR), etc.) of RF signals received from that direction.

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

[0041] Note that a "downlink" beam can be either a transmit beam or a receive beam, depending on the entity that forms it. For example, if the base station forms a downlink beam to transmit a reference signal to the UE, then the downlink beam is a transmit beam. However, if the UE forms a downlink beam, then it is a receive beam to receive a downlink reference signal. Similarly, an "uplink" beam can be either a transmit beam or a receive beam, depending on the entity that forms it. For example, if the base station forms an uplink beam, then it is an uplink receive beam, and if the UE forms an uplink beam, then it is an uplink transmit beam.

[0042] The electromagnetic spectrum is often subdivided into various classes, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that although a portion of FR1 is higher than 6 GHz, FR1 is often referred to (interchangeably) as the "sub-6 GHz" band in various documents and papers. Similar nomenclature issues may arise with respect to FR2, which is often referred to (interchangeably) as the "mmWave" band in documents and papers, even though FR2 is different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "mmWave" band by the International Telecommunications Union (ITU).

[0043] Frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified operating bands for these mid-band frequencies as frequency range designation FR3 (7.125 GHz to 24.25 GHz). Frequency bands within FR3 may inherit the characteristics of FR1 and / or FR2, and therefore may effectively extend the features of FR1 and / or FR2 to the mid-band frequencies. Furthermore, higher frequency bands are currently being considered to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands is within the EHF band.

[0044] With the above aspects in mind, it should be understood that unless otherwise specified, terms such as "sub-6 GHz," as used herein, may broadly refer to frequencies that may be below 6 GHz, frequencies that may be in the range of FR1, or frequencies that may include mid-band frequencies. Further, it should be understood that unless otherwise specified, terms such as "mmWave," as used herein, may broadly refer to frequencies that may be in the range of FR2, FR4, FR4-a, or FR4-1, and / or FR5, or frequencies that may be in the EHF band.

[0045] In a multi-carrier system such as 5G, one of the carrier frequencies is called the "primary carrier" or "anchor carrier" or "primary serving cell" or "PCell", and the remaining carrier frequencies are called the "secondary carrier" or "secondary serving cell" or "SCell". In carrier aggregation, the anchor carrier is a carrier operating on the primary frequency (e.g., FR1) utilized by the UE 104 / 182 and on the cell in which the UE 104 / 182 either performs an initial radio resource control (RRC) connection establishment procedure or initiates an RRC connection re-establishment procedure. The primary carrier carries all common control channels and UE-specific control channels and may (but is not always) be a carrier among licensed frequencies. The secondary carrier is a carrier operating on a second frequency (e.g., FR2) that may be configured once an RRC connection is established between the UE 104 and the anchor carrier and may be used to provide additional radio resources. In some cases, the secondary carrier may be a carrier among unlicensed frequencies. Since both the primary uplink carrier and the primary downlink carrier are typically UE specific, the secondary carrier may include only the necessary signaling information and signals, e.g., the signaling information and signals that are UE specific may not be present in the secondary carrier. This means that different UEs 104 / 182 in a cell may have different downlink primary carriers. The same applies to the uplink primary carrier. The network may change the primary carrier of any UE 104 / 182 at any time. This is done, for example, to distribute the load on different carriers. Since a "serving cell" (whether PCell or SCell) corresponds to a carrier frequency / component carrier over which several base stations are communicating, terms such as "cell", "serving cell", "component carrier", "carrier frequency", etc. may be used interchangeably.

[0046] For example, still referring to FIG. 1, one of the frequencies utilized by the macrocell base station 102 may be an anchor carrier (or "PCell"), and the other frequencies utilized by the macrocell base station 102 and / or the mmW base station 180 may be secondary carriers ("SCells"). Simultaneous transmission and / or reception of multiple carriers allows the UE 104 / 182 to significantly increase its data transmission and / or reception rates. For example, two 20 MHz carriers aggregated in a multi-carrier system would theoretically lead to a two-fold increase in data rate (i.e., 40 MHz) compared to the data rate achieved by a single 20 MHz carrier.

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

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

[0049] In one aspect, the SV 112 may additionally or alternatively be part of one or more non-terrestrial networks (NTNs). In an NTN, the SV 112 is connected to an earth station (also called a ground station, NTN gateway, or gateway), which in turn is connected to an element in a 5G network, such as a modified base station 102 (without a terrestrial antenna) or a network node in a 5G network. This element will then provide access to other elements in the 5G network and ultimately to entities outside the 5G network, such as Internet web servers and other user devices. In that way, the UE 104 may receive communication signals (e.g., signal 124) from the SV 112 instead of or in addition to communication signals from the terrestrial base station 102.

[0050] In particular, vehicle-to-everything (V2X) communication technology is being implemented to leverage NR’s increased data rates and reduced latency to support intelligent transportation systems (ITS) applications such as wireless communications between vehicles (vehicle-to-vehicle, V2V), between vehicles and roadside infrastructure (vehicle-to-infrastructure, V2I), and between vehicles and pedestrians (vehicle-to-pedestrian, V2P). The goal is for vehicles to be able to sense the environment around them and communicate that information to other vehicles, infrastructure, and personal mobile devices. Such vehicular communications will enable safety, mobility, and environmental improvements that current technologies cannot provide. When fully implemented, the technology is expected to reduce unimpeded vehicle collisions by 80%.

[0051] 1, the wireless communication system 100 may include multiple V-UEs 160 that may communicate with the base station 102 over the communication link 120 using the Uu interface (i.e., the air interface between the UE and the base station). The V-UEs 160 may also communicate with each other directly over a wireless sidelink 162, with a roadside unit (RSU) 164 (a roadside access point) over a wireless sidelink 166, or with a sidelink-enabled UE 104 over a wireless sidelink 168 using a PC5 interface (i.e., the air interface between sidelink-enabled UEs). The wireless sidelink (or simply "sidelink") is an adaptation of the core cellular (e.g., LTE, NR) standard that allows direct communication between two or more UEs without the communication having to go through a base station. Sidelink communications may be unicast or multicast and may be used for device-to-device (D2D) medium sharing, V2V communications, V2X communications (e.g., cellular V2X (cV2X) communications, enhanced V2X (eV2X) communications, etc.), emergency rescue applications, etc. One or more of a group of V-UEs 160 utilizing sidelink communications may be within the geographic coverage area 110 of the base station 102. Other V-UEs 160 in such a group may be outside the geographic coverage area 110 of the base station 102 or may not otherwise be able to receive transmissions from the base station 102. In some cases, a group of V-UEs 160 communicating via sidelink communications may utilize a one-to-many (1:M) system in which each V-UE 160 transmits to all other V-UEs 160 in the group. In some cases, the base station 102 facilitates scheduling of resources for sidelink communications. In other cases, sidelink communications are performed between V-UEs 160 without the involvement of the base station 102.

[0052] In one aspect, the sidelinks 162, 166, 168 may operate over a subject wireless communications medium, which may be shared with other vehicles and / or infrastructure access points, as well as other wireless communications between other RATs. The "medium" may consist of one or more time, frequency, and / or spatial communications resources (e.g., encompassing one or more channels across one or more carriers) associated with wireless communications between one or more transmitter / receiver pairs.

[0053] In one aspect, the sidelinks 162, 166, 168 may be cV2X links. First generation cV2X is standardized in LTE, and the next generation is expected to be defined in NR. cV2X is a cellular technology that also enables device-to-device communication. In the United States and Europe, cV2X is expected to operate in licensed ITS bands in the sub-6 GHz. Other countries may allocate other bands. Thus, as a specific example, the target medium utilized by the sidelinks 162, 166, 168 may correspond to at least a portion of the sub-6 GHz licensed ITS frequency band. However, the present disclosure is not limited to this frequency band or cellular technology.

[0054] In one aspect, the sidelinks 162, 166, 168 may be dedicated short-range communications (DSRC) links. DSRC is a one-way or two-way, short-to-medium-range wireless communications protocol using the wireless access for vehicular environments (WAVE) protocol, also referred to as IEEE 802.11p, for V2V, V2I, and V2P communications. IEEE 802.11p is an approved amendment to the IEEE 802.11 standard, which operates in the licensed ITS band at 5.9 GHz (5.85-5.925 GHz) in the United States. In Europe, IEEE 802.11p operates in the ITS G5A band (5.875-5.905 MHz). Other countries may allocate other bands. The V2V communications briefly described above are conducted on safety channels, which in the United States are typically 10 MHz channels dedicated for safety purposes. The remainder of the DSRC band (total bandwidth of 75 MHz) is intended for other services targeted to drivers, such as road enforcement, toll collection, automated parking, etc. Thus, as a specific example, the medium of interest utilized by the sidelinks 162, 166, 168 may correspond to at least a portion of the 5.9 GHz licensed ITS frequency band.

[0055] Alternatively, the medium of interest may correspond to at least a portion of an unlicensed frequency band shared among various RATs. Although different licensed frequency bands have been reserved for several communication systems (e.g., by government agencies such as the Federal Communications Commission (FCC) in the United States), these systems, particularly those employing small cell access points, have recently extended their operation to unlicensed frequency bands such as the Unlicensed National Information Infrastructure (U-NII) bands used by Wireless Local Area Network (WLAN) technologies, most notably the IEEE 802.11x WLAN technology commonly referred to as "Wi-Fi". Exemplary systems of this type include CDMA systems, TDMA systems, FDMA systems, orthogonal FDMA (OFDMA) systems, single-carrier FDMA (SC-FDMA) systems, and various variants thereof.

[0056] The communication between V-UEs 160 is referred to as V2V communication, the communication between V-UEs 160 and one or more RSUs 164 is referred to as V2I communication, and the communication between V-UEs 160 and one or more UEs 104 (where UEs 104 are P-UEs) is referred to as V2P communication. The V2V communication between V-UEs 160 may include, for example, information about the position, speed, acceleration, heading, and other vehicle data of the V-UEs 160. The V2I information received at the V-UEs 160 from one or more RSUs 164 may include, for example, road regulations, parking automation information, and the like. The V2P communication between V-UEs 160 and UEs 104 may include, for example, information about the position, speed, acceleration, and heading of the V-UEs 160, and the position, speed (e.g., when the UEs 104 are carried by a user on a bicycle), and heading of the UEs 104.

[0057] It should be noted that while FIG. 1 illustrates only two of the UEs as V-UEs (V-UE 160), any of the illustrated UEs (e.g., UEs 104, 182, 190) may be V-UEs. Additionally, while only V-UE 160 and a single UE 104 are illustrated as being connected via a sidelink, any of the UEs illustrated in FIG. 1, whether V-UE, P-UE, etc., may be capable of sidelink communication. Additionally, although only UE 182 was described as being capable of beamforming, any of the illustrated UEs, including V-UE 160, may be capable of beamforming. If V-UE 160 is capable of beamforming, V-UE 160 may beamform toward each other (i.e., toward other V-UEs 160), toward RSU 164, toward other UEs (e.g., UEs 104, 152, 182, 190), etc. Thus, in some cases, V-UE 160 may utilize beamforming on sidelinks 162, 166, and 168.

[0058] The wireless communication system 100 may further include one or more UEs, such as a UE 190, that indirectly connect to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links. In the example of FIG. 1, the UE 190 has a D2D P2P link 192 (e.g., through which the UE 190 may indirectly obtain cellular connectivity) with one of the UEs 104 connected to one of the base stations 102, and a D2D P2P link 194 (through which the UE 190 may indirectly obtain WLAN-based Internet connectivity) with a WLAN STA 152 connected to a WLAN AP 150. In one example, the D2D P2P links 192 and 194 may be supported using any well-known D2D RAT, such as LTE Direct (LTE-D), WiFi Direct (WiFi-D), Bluetooth, etc. As another example, the D2D P2P links 192 and 194 may be sidelinks such as those described above with respect to the sidelinks 162, 166, and 168.

[0059] 2A illustrates an exemplary wireless network structure 200. For example, the 5GC 210 (also referred to as Next Generation Core (NGC)) may be functionally viewed as control plane (C-plane) functions 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and user plane (U-plane) functions 212 (e.g., UE gateway functions, access to data networks, IP routing, etc.) that operate cooperatively to form a core network. A user plane interface (NG-U) 213 and a control plane interface (NG-C) 215 connect the gNB 222 to the 5GC 210, specifically to the user plane function 212 and the control plane function 214, respectively. In an additional configuration, the ng-eNB 224 may also be connected to the 5GC 210 via the NG-C 215 to the control plane function 214 and the NG-U 213 to the user plane function 212. Additionally, the ng-eNB 224 may communicate directly with the gNB 222 via a backhaul connection 223. In some configurations, the Next Generation RAN (NG-RAN) 220 may have one or more gNBs 222, while other configurations include one or more of both the ng-eNB 224 and the gNB 222. Either the gNB 222 or the ng-eNB 224 (or both) may communicate with one or more UEs 204 (e.g., any of the UEs described herein).

[0060] Another optional aspect may include a location server 230, which may be in communication with the 5GC 210 to provide location assistance to the UE(s) 204. The location servers 230 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules across multiple physical servers, etc.), or alternatively, each may correspond to a single server. The location servers 230 may be configured to support one or more location services for the UEs 204 that may connect to the location server 230 via the core network, the 5GC 210, and / or via the Internet (not shown). Furthermore, the location server 230 may be integrated into components of the core network, or alternatively, may be external to the core network (e.g., a third-party server, such as an original equipment manufacturer (OEM) server or a service server).

[0061] 2B illustrates another exemplary wireless network structure 250. A 5GC 260 (which may correspond to 5GC 210 in FIG. 2A) may be considered functionally as control plane functions provided by an access and mobility management function (AMF) 264 and user plane functions provided by a user plane function (UPF) 262, which operate cooperatively to form a core network (i.e., 5GC 260). The functions of the AMF 264 include registration management, attachment management, reachability management, mobility management, lawful interception, transport for session management (SM) messages between one or more UEs 204 (e.g., any of the UEs described herein) and a session management function (SMF) 266, transparent proxy services for routing SM messages, access authentication and access authorization, transport for short message service (SMS) messages between the UE 204 and a short message service function (SMSF) (not shown), and security anchor functionality (SEAF). The AMF 264 also interacts with an authentication server function (AUSF) (not shown) and the UE 204 to receive intermediate keys established as a result of the UE 204 authentication process. In case of UMTS (universal mobile telecommunications system) subscriber identity module (USIM) based authentication, the AMF 264 retrieves security material from the AUSF. The AMF 264 functions also include security context management (SCM).The SCM receives keys from the SEAF that the SCM uses to derive access network specific keys. The functionality of the AMF 264 also includes location service management for regulated services, transport for location service messages between the UE 204 and the location management function (LMF) 270 (acting as the location server 230), transport for location service messages between the NG-RAN 220 and the LMF 270, EPS bearer identifier allocation for interworking with evolved packet system (EPS), and UE 204 mobility event notification. In addition, the AMF 264 also supports functions for non-3GPP (Third Generation Partnership Project ("3GPP")) access networks.

[0062] The functions of the UPF 262 include acting as an anchor point for intra / inter-RAT mobility (when applicable), acting as an external protocol data unit (PDU) session point for interconnection to a data network (not shown), routing and forwarding of packets, packet inspection, user plane policy rule enforcement (e.g., gating, redirection, traffic steering), lawful interception (user plane collection), traffic usage reporting, quality of service (QoS) processing for the user plane (e.g., uplink / downlink rate enforcement, reflective QoS marking in the downlink), uplink traffic validation (service data flow (SDF) to QoS flow mapping), transport level packet marking in the uplink and downlink, downlink packet buffering and downlink data notification triggering, and sending and forwarding one or more "end markers" to the source RAN node. The UPF 262 may also support forwarding of location service messages on the user plane between the UE 204 and a location server such as the SLP 272.

[0063] The functions of the SMF 266 include session management, UE Internet protocol (IP) address allocation and management, selection and control of user plane functions, configuration of traffic steering in the UPF 262 to route traffic to the appropriate destination, control of policy enforcement and part of QoS, and downlink data notification. The interface through which the SMF 266 communicates with the AMF 264 is called the N11 interface.

[0064] Another optional aspect may include an LMF 270, which may be in communication with the 5GC 260 to provide location assistance to the UE 204. The LMF 270 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules across multiple physical servers, etc.), or alternatively, each may represent a single server. The LMF 270 may be configured to support one or more location services for UEs 204 that may connect to the LMF 270 via a core network, the 5GC 260, and / or via the Internet (not shown). The SLP 272 may support similar functions as the LMF 270, while the LMF 270 may communicate with the AMF 264, the NG-RAN 220, and the UE 204 via the control plane (e.g., using interfaces and protocols intended to convey signaling messages rather than voice or data) and the SLP 272 may communicate with the UE 204 and external clients (e.g., third-party servers 274) via the user plane (e.g., using protocols intended to carry voice and / or data, such as transmission control protocol (TCP) and / or IP).

[0065] Yet another optional aspect may include a third party server 274, which may be in communication with the LMF 270, the SLP 272, the 5GC 260 (e.g., via the AMF 264 and / or the UPF 262), the NG-RAN 220, and / or the UE 204 to obtain location information (e.g., a location estimate) for the UE 204. Thus, in some cases, the third party server 274 may be referred to as a location services (LCS) client or an external client. The third party servers 274 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules spread across multiple physical servers, etc.) or, alternatively, each may correspond to a single server.

[0066] The user plane interface 263 and the control plane interface 265 connect the 5GC 260, and in particular the UPF 262 and the AMF 264, respectively, to one or more gNBs 222 and / or ng-eNBs 224 in the NG-RAN 220. The interface between the gNB(s) 222 and / or ng-eNB(s) 224 and the AMF 264 is referred to as the “N2” interface, and the interface between the gNB(s) 222 and / or ng-eNB(s) 224 and the UPF 262 is referred to as the “N3” interface. The gNB(s) 222 and / or ng-eNB(s) 224 of the NG-RAN 220 may communicate directly with each other via a backhaul connection 223 referred to as the “Xn-C” interface. One or more of the gNBs 222 and / or ng-eNBs 224 may communicate with one or more UEs 204 via a wireless interface referred to as a “Uu” interface.

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

[0068] 3A, 3B, and 3C illustrate several example components (represented by corresponding blocks) that may be incorporated in a UE 302 (which may correspond to any of the UEs described herein), a base station 304 (which may correspond to any of the base stations described herein), and a network entity 306 (which may correspond to or embody any of the network functions described herein, including a location server 230 and an LMF 270, or alternatively may be independent of the NG-RAN 220 and / or 5GC 210 / 260 infrastructure depicted in FIGS. 2A and 2B, such as a private network) to support the operations described herein. It will be understood that these components may be implemented in different types of devices in different implementations (e.g., in an ASIC, in a system-on-chip (SoC), etc.). The illustrated components may also be incorporated in other devices in a communication system. For example, other devices in the system may include components similar to the described components to provide similar functionality. Also, a given device may include one or more of the components. For example, a device may contain multiple transceiver components that enable the device to operate on multiple carriers and / or communicate via different technologies.

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

[0070] The UE 302 and base station 304 also each, at least in some cases, include one or more short-range wireless transceivers 320 and 360, respectively. The short-range wireless transceivers 320 and 360 may be connected to one or more antennas 326 and 366, respectively, and may provide means for communicating (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, means for refraining from transmitting, etc.) with other network nodes, such as other UEs, access points, base stations, etc., via at least one designated RAT (e.g., WiFi, LTE-D, Bluetooth, Zigbee, Z-Wave, PC5, Dedicated Short-Range Communications (DSRC), Wireless Access for Vehicular Environments (WAVE), near-field communication (NFC), etc.) over the wireless communication medium. The short-range wireless transceivers 320 and 360 may be variously configured to transmit and encode signals 328 and 368 (e.g., messages, instructions, information, etc.), respectively, and conversely, to receive and decode signals 328 and 368 (e.g., messages, instructions, information, pilots, etc.), respectively, in accordance with a specified RAT. Specifically, the short-range wireless transceivers 320 and 360 include one or more transmitters 324 and 364, respectively, to transmit and encode signals 328 and 368, respectively, and include one or more receivers 322 and 362, respectively, to receive and decode signals 328 and 368, respectively. As specific examples, the short-range wireless transceivers 320 and 360 may be WiFi transceivers, Bluetooth® transceivers, Zigbee® and / or Z-Wave® transceivers, NFC transceivers, or Vehicle-to-Vehicle (V2V) and / or Vehicle-to-Everything (V2X) transceivers.

[0071] The UE 302 and base station 304 also, at least in some cases, include satellite signal receivers 330 and 370. The satellite signal receivers 330 and 370 may be connected to one or more antennas 336 and 376, respectively, and may provide a means for receiving and / or measuring satellite positioning / communications signals 338 and 378, respectively. If the satellite signal receivers 330 and 370 are satellite positioning system receivers, the satellite positioning / communications signals 338 and 378 may be global positioning system (GPS) signals, global navigation satellite system (GLONASS) signals, Galileo signals, Beidou signals, Indian regional navigation satellite system (NAVIC), Quasi-Zenith Satellite System (QZSS), etc. If satellite signal receivers 330 and 370 are non-terrestrial network (NTN) receivers, satellite positioning / communications signals 338 and 378 may be communication signals (e.g., carrying control and / or user data) originating from a 5G network. Satellite signal receivers 330 and 370 may comprise any suitable hardware and / or software for receiving and processing satellite positioning / communications signals 338 and 378, respectively. Satellite signal receivers 330 and 370 may request information and actions from other systems as appropriate, and may perform calculations, at least in some cases, to determine the location of UE 302 and base station 304, respectively, using measurements obtained by any suitable satellite positioning system algorithms.

[0072] The base station 304 and the network entity 306 each include one or more network transceivers 380 and 390, respectively, that provide a means for communicating (e.g., a means for transmitting, a means for receiving, etc.) with other network entities (e.g., other base stations 304, other network entities 306). For example, the base station 304 may employ one or more network transceivers 380 to communicate with other base stations 304 or network entities 306 over one or more wired or wireless backhaul links. As another example, the network entity 306 may employ one or more network transceivers 390 to communicate with one or more base stations 304 over one or more wired or wireless backhaul links or with other network entities 306 over one or more wired or wireless core network interfaces.

[0073] A transceiver may be configured to communicate over a wired link or a wireless link. A transceiver (whether a wired transceiver or a wireless transceiver) includes transmitter circuitry (e.g., transmitters 314, 324, 354, 364) and receiver circuitry (e.g., receivers 312, 322, 352, 362). A transceiver may be an integrated device (e.g., embodying transmitter and receiver circuitry in a single device) in some implementations, may comprise separate transmitter circuitry and separate receiver circuitry in some implementations, or may be embodied in other ways in other implementations. The transmitter and receiver circuitry of a wired transceiver (e.g., network transceivers 380 and 390 in some implementations) may be coupled to one or more wired network interface ports. The wireless transmitter circuitry (e.g., transmitters 314, 324, 354, 364) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array that enables the respective device (e.g., UE 302, base station 304) to perform transmit "beamforming" as described herein. Similarly, the wireless receiver circuitry (e.g., receivers 312, 322, 352, 362) may include or be coupled to multiple antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array that enables the respective device (e.g., UE 302, base station 304) to perform receive beamforming, as described herein. In one aspect, the transmitter circuitry and receiver circuitry may share multiple identical antennas (e.g., antennas 316, 326, 356, 366), such that the respective device can only receive or transmit at a given time, but not both at the same time. The wireless transceivers (eg, WWAN transceivers 310 and 350, short range wireless transceivers 320 and 360) may also include a network listen module (NLM) or the like for performing various measurements.

[0074] As used herein, various wireless transceivers (e.g., transceivers 310, 320, 350, and 360, and network transceivers 380 and 390, in some implementations) and wired transceivers (e.g., network transceivers 380 and 390, in some implementations) may be generally characterized as a "transceiver," "at least one transceiver," or "one or more transceivers." Thus, whether a particular transceiver is a wired or wireless transceiver may be inferred from the type of communication being performed. For example, backhaul communications between network devices or servers generally involve signaling via wired transceivers, while wireless communications between a UE (e.g., UE 302) and a base station (e.g., base station 304) generally involve signaling via wireless transceivers.

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

[0076] The UE 302, base station 304, and network entity 306 include memory circuitry implementing memories 340, 386, and 396, respectively (e.g., each including a memory device) for maintaining information (e.g., information indicating reserved resources, thresholds, parameters, etc.). Thus, the memories 340, 386, and 396 can provide storage means, retrieval means, maintenance means, etc. In some cases, the UE 302, base station 304, and network entity 306 may include sidelink managers 342, 388, and 398, respectively. The sidelink managers 342, 388, and 398 may be hardware circuits that are part of or coupled to the processors 332, 384, and 394, respectively, that, when executed, cause the UE 302, base station 304, and network entity 306 to perform the functions described herein. In other aspects, the sidelink managers 342, 388, and 398 may be external to the processors 332, 384, and 394 (e.g., part of a modem processing system, integrated with another processing system, etc.). Alternatively, the sidelink managers 342, 388, and 398 may be memory modules stored in the memories 340, 386, and 396, respectively, that when executed by the processors 332, 384, and 394 (or modem processing system, another processing system, etc.) cause the UE 302, the base station 304, and the network entity 306 to perform the functions described herein. Figure 3A illustrates possible locations of the sidelink manager 342, which may be, for example, part of the WWAN transceiver(s) 310, the memory 340, the processor(s) 332, or any combination thereof, or may be a stand-alone component. FIG. 3B shows possible locations for a sidelink manager 388, which may be, for example, part of one or more WWAN transceivers 350, memory 386, one or more processors 384, or any combination thereof, or may be a stand-alone component.FIG. 3C shows possible locations of a sidelink manager 398, which may be, for example, part of one or more network transceivers 390, memory 396, one or more processors 394, or any combination thereof, or may be a stand-alone component.

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

[0078] Additionally, the UE 302 includes a user interface 346 that provides a means for providing indications to a user (e.g., audio and / or visual indications) and / or receiving user input (e.g., upon user actuation of a sensing device, such as a keypad, touch screen, microphone, etc.). Although not shown, the base station 304 and the network entity 306 may also include user interfaces.

[0079] Referring more particularly to the one or more processors 384, on the downlink, IP packets from the network entity 306 may be provided to the processor 384. The one or more processors 384 may implement functionality for an RRC layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, and a Medium Access Control (MAC) layer. The one or more processors 384 may provide RRC layer functions associated with broadcast of system information (e.g., master information blocks (MIBs), system information blocks (SIBs)), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-RAT mobility, and measurement configuration for UE measurement reporting; PDCP layer functions associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with transfer of upper layer PDUs, error correction with automatic repeat request (ARQ), concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization.

[0080] The transmitter 354 and receiver 352 may implement Layer-1 (L1) functions associated with various signal processing functions. Layer-1, including the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping onto the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The transmitter 354 handles mapping onto signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to orthogonal frequency division multiplexing (OFDM) subcarriers, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time-domain OFDM symbol stream. The OFDM symbol streams are spatially precoded to generate multiple spatial streams. Channel estimates from a channel estimator may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimates may be derived from a reference signal and / or channel condition feedback transmitted by the UE 302. Each spatial stream may then be provided to one or more different antennas 356. The transmitter 354 may modulate an RF carrier with the individual spatial streams for transmission.

[0081] At the UE 302, the receiver 312 receives signals through its respective antenna(s) 316. The receiver 312 recovers the information modulated onto the RF carriers and provides the information to one or more processors 332. The transmitter 314 and the receiver 312 perform layer 1 functions associated with various signal processing functions. The receiver 312 may perform spatial processing on the information to recover any spatial streams destined for the UE 302. If multiple spatial streams are destined for the UE 302, they may be combined by the receiver 312 into a single OFDM symbol stream. The receiver 312 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, as well as the reference signal, are recovered and demodulated by determining the most likely signal constellation point transmitted by the base station 304. These soft decisions may be based on channel estimates calculated by a channel estimator. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted on the physical channel by the base station 304. The data and control signals are then provided to one or more processors 332 that implement Layer-3 (L3) and Layer-2 (L2) functions.

[0082] In the uplink, one or more processors 332 provide demultiplexing between transport and logical channels, packet reassembly, decryption, header recovery, and control signal processing to recover IP packets from the core network. The one or more processors 332 are also responsible for error detection.

[0083] Similar to the functionality described in connection with downlink transmissions by the base station 304, the one or more processors 332 provide RRC layer functions related to system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functions associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with transfer of upper layer PDUs, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via hybrid automatic repeat request (HARQ), priority handling, and logical channel prioritization.

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

[0085] Uplink transmissions are processed at the base station 304 in a manner similar to that described with respect to the receiver function at the UE 302. The receiver 352 receives signals via its respective antenna(s) 356. The receiver 352 recovers information modulated onto an RF carrier and provides the information to one or more processors 384.

[0086] In the uplink, the one or more processors 384 provide demultiplexing between transport and logical channels, packet reassembly, decryption, header recovery, and control signal processing to recover IP packets from the UE 302. The IP packets from the one or more processors 384 may be provided to a core network. The one or more processors 384 are also responsible for error detection.

[0087] For convenience, the UE 302, base station 304, and / or network entity 306 are illustrated in Figures 3A, 3B, and 3C as including various components that may be configured according to various examples described herein. However, it will be understood that the illustrated components may have different functions in different designs. In particular, various components in Figures 3A-3C are optional in alternative configurations, and various aspects include configurations that may vary due to design choice, cost, device use, or other considerations. For example, in the case of Figure 3A, a particular implementation of the UE 302 may omit the WWAN transceiver(s) 310 (e.g., a wearable device or tablet computer or PC or laptop may have Wi-Fi and / or Bluetooth capabilities without cellular capabilities), or may omit the short-range wireless transceiver(s) 320 (e.g., cellular only, etc.), or may omit the satellite signal receiver 330, or may omit the sensor(s) 344, etc. 3B, a particular implementation of base station 304 may omit WWAN transceiver(s) 350 (e.g., a Wi-Fi “hotspot” access point without cellular capability), or may omit short-range wireless transceiver(s) 360 (e.g., cellular only), or may omit satellite receiver 370, etc. For brevity, examples of various alternative configurations are not provided herein, but should be readily apparent to one of ordinary skill in the art.

[0088] The various components of the UE 302, base station 304, and network entity 306 may be communicatively coupled to one another via data buses 334, 382, ​​and 392, respectively. In an aspect, the data buses 334, 382, ​​and 392 may form or be part of communication interfaces of the UE 302, base station 304, and network entity 306, respectively. For example, when different logical entities are embodied within the same device (e.g., gNB and location server functionality integrated within the same base station 304), the data buses 334, 382, ​​and 392 may provide communication between them.

[0089] The components of Figures 3A, 3B, and 3C may be implemented in a variety of ways. In some implementations, the components of Figures 3A, 3B, and 3C may be implemented in one or more circuits, such as, for example, one or more processors and / or one or more ASICs (which may include one or more processors), where each circuit may use and / or incorporate at least one memory component for storing information or executable code used by the circuit to provide this functionality. For example, some or all of the functionality represented by blocks 310-346 may be implemented by the processor and memory component(s) of the UE 302 (e.g., by execution of appropriate code and / or by appropriate configuration of the processor components). Similarly, some or all of the functionality represented by blocks 350-388 may be implemented by the processor and memory component(s) of the base station 304 (e.g., by execution of appropriate code and / or by appropriate configuration of the processor components). Also, some or all of the functionality represented by blocks 390-398 may be implemented by the processor and memory component(s) of the network entity 306 (e.g., by execution of appropriate code and / or by appropriate configuration of the processor components). For simplicity, various operations, actions, and / or functions are described herein as being performed "by the UE," "by the base station," "by the network entity," etc. However, it will be understood that such operations, actions, and / or functions may actually be performed by a particular component or combination of components of the UE 302, base station 304, network entity 306, etc., such as the processors 332, 384, 394, transceivers 310, 320, 350, and 360, memories 340, 386, and 396, sidelink managers 342, 388, and 398, etc.

[0090] In some designs, the network entity 306 may be implemented as a core network component. In other designs, the network entity 306 may be separate from the network operator or operation of the cellular network infrastructure (e.g., the NG RAN 220 and / or the 5GC 210 / 260). For example, the network entity 306 may be a component of a private network that may be configured to communicate with the UE 302 via the base station 304 or independently of the base station 304 (e.g., via a non-cellular communication link such as WiFi).

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

[0092] LTE, and possibly NR, employs orthogonal frequency division multiplexing (OFDM) on the downlink and single-carrier frequency division multiplexing (SC-FDM) on the uplink. However, unlike LTE, NR also has the option of using OFDM on the uplink. OFDM and SC-FDM partition the system bandwidth into multiple (K) orthogonal subcarriers, also commonly referred to as tones, bins, etc. Each subcarrier may be modulated with data. Generally, modulation symbols are sent in the frequency domain with OFDM and in the time domain with SC-FDM. The spacing between adjacent subcarriers may be fixed, or the total number of subcarriers (K) may be dependent on the system bandwidth. For example, the subcarrier spacing may be 15 kilohertz (kHz), and the minimum resource allocation (resource block) may be 12 subcarriers (i.e., 180 kHz). Thus, the nominal Fast Fourier Transform (FFT) size may be equal to 128, 256, 512, 1024, or 2048 for a system bandwidth of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), respectively. The system bandwidth may also be partitioned into subbands. For example, a subband may cover 1.08 MHz (i.e., 6 resource blocks), and there may be 1, 2, 4, 8, or 16 subbands for a system bandwidth of 1.25, 2.5, 5, 10, or 20 MHz, respectively.

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

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

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

[0096] Some of the REs may carry reference (pilot) signals (RS). The reference signals may include positioning reference signals (PRS), tracking reference signals (TRS), phase tracking reference signals (PTRS), cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), primary synchronization signals (PSS), secondary synchronization signals (SSS), synchronization signal blocks (SSB), sounding reference signals (SRS), etc., depending on whether the illustrated frame structure is used for uplink or downlink communications. Figure 4 shows example locations of REs carrying reference signals (labeled "R").

[0097] FIG. 5 is a diagram of an example PRS configuration 500 for PRS transmissions of a given base station, according to an aspect of the disclosure. In FIG. 5, time is represented horizontally, increasing from left to right. Each longer rectangle represents a slot, and each shorter (shaded) rectangle represents an OFDM symbol. In the example of FIG. 5, PRS resource set 510 (labeled "PRS resource set 1") includes two PRS resources: a first PRS resource 512 (labeled "PRS resource 1") and a second PRS resource 514 (labeled "PRS resource 2"). The base station transmits a PRS in PRS resources 512 and 514 of PRS resource set 510.

[0098] PRS resource set 510 has an occasion length (N_PRS) of 2 slots and a periodicity (T_PRS) of, for example, 160 slots or 160 milliseconds (ms) (for 15 kHz subcarrier spacing). Thus, both PRS resources 512 and 514 are two consecutive slots in length and repeat every T_PRS slots, starting from the slot in which the first symbol of the respective PRS resource appears. In the example of FIG. 5, PRS resource 512 has a symbol length (N_symb) of 2 symbols and PRS resource 514 has a symbol length (N_symb) of 4 symbols. PRS resource 512 and PRS resource 514 may be transmitted on separate beams of the same base station.

[0099] Each instance of PRS resource set 510, shown as instances 520a, 520b, and 520c, includes occasions of length "2" (i.e., N_PRS=2) for each PRS resource 512, 514 of the PRS resource set. The PRS resources 512 and 514 are repeated every T_PRS slots up to the muting sequence periodicity T_REP. Thus, a bitmap of length T_REP would be needed to indicate which occasions of instances 520a, 520b, and 520c of PRS resource set 510 are muted (i.e., not transmitted).

[0100] In one aspect, there may be additional constraints on the PRS configuration 500. For example, for all PRS resources (e.g., PRS resources 512, 514) of a PRS resource set (e.g., PRS resource set 510), the base station may configure the following parameters to be the same: (a) occasion length (N_PRS), (b) number of symbols (N_symb), (c) comb type, and / or (d) bandwidth. In addition, for all PRS resources of all PRS resource sets, the subcarrier spacing and cyclic prefix may be configured to be the same for one base station or for all base stations. Whether it is for one base station or for all base stations may depend on the UE's capability to support the first and / or second options.

[0101] FIG. 6A illustrates parameters of a measurement gap configuration 600 that specify a pattern of measurement gaps 602, according to an aspect of the disclosure. The measurement gap offset (MGO) is the offset of the start of the gap pattern from the start of a slot or subframe within the measurement gap repetition period (MGRP). In some aspects, there are about 160 offset values, although not all of the values ​​are applicable for all periodicities. More specifically, the offset has a value ranging from "0" to one less than the MGRP. Thus, for example, if the MGRP is 20 ms, the offset may range from "0" to "19". The measurement gap length (MGL) is the length of the measurement gap in milliseconds. The measurement gap length can have values ​​of 1.5 ms, 3 ms, 3.5 ms, 4 ms, 5.5 ms, or 6 ms. The MGRP defines the periodicity (in milliseconds) at which the measurement gaps 602 repeat. The periodicity can have a value of 20 ms, 40 ms, 80 ms, or 160 ms. Although not shown in FIG. 6A, the measurement gap configuration 600 may also include a measurement gap timing advance (MGTA) parameter. If configured, MGTA indicates the amount of time before the occurrence of the slot or subframe in which the measurement gap 602 is configured to start. In some aspects, MGTA may be 0.25 ms for FR2 or 0.5 ms for FR1.

[0102] It may be desirable to introduce an additional MG pattern with MGL≧10ms and MGRP≧80ms. In this case, it should be determined whether the new MG pattern is applicable for radio resource management (RRM) measurements, and the details of the new MG pattern remain specified. Candidate values ​​of MGL include 10ms, 18ms, 20ms, 34ms, 40ms, and 50ms. Candidate values ​​of MGRP include 80ms, 160ms, 320ms, and 640ms. Values ​​of combinations of MGL and MGRP remain specified, but candidate combinations include MGL=40ms and MGRP=160ms, MGL=34ms and MGRP=160ms, and MGL=18ms and MGRP=160ms.

[0103] FIG. 6B illustrates a PRS 606 that is transmitted within a measurement gap 602 in a PRS occasion 606 that may span one or multiple (consecutive) slots according to the occasion length. 1 ~PRS N FIG. 6 illustrates a positioning reference signal 604 labeled PRS. 1 is associated with one Transmission / Reception Point (TRP) and the PRS 2 is associated with another TRP, and so on. In FIG. 6B, each PRS is repeated four times, with the transmission of the next PRS immediately following in the time domain, e.g., the PRSs are "clustered" in the time domain. Each TRP can use the same beam pattern or a different beam pattern for each repetition. In FIG. 6B, the PRS 604 is transmitted for the entire duration of the PRS occasion 606, which occupies only a portion of the measurement gap 602, although other configurations are contemplated by this disclosure. Up to 256 TRPs can be configured via assistance data, which means that the UE may need longer measurement gaps to measure the PRSs from all of them. These longer gaps are needed in a periodic manner to track use cases, and the longer gaps impact NR throughput.

[0104] 7 illustrates an example of a wireless communication system 700 supporting wireless unicast sidelink establishment according to aspects of the disclosure. In some examples, the wireless communication system 700 may implement aspects of the wireless communication systems 100, 200, and 250. The wireless communication system 700 may include a first UE 702 and a second UE 704, which may be examples of any of the UEs described herein. As a particular example, the UEs 702 and 704 may correspond to the V-UEs 160 of FIG. 1.

[0105] In the example of Fig. 7, the UE 702 may attempt to establish a unicast connection with the UE 704 over a sidelink, which may be a V2X sidelink between the UE 702 and the UE 704. As a specific example, the established sidelink connection may correspond to sidelinks 162 and / or 168 in Fig. 1. The sidelink connection may be established in an omnidirectional frequency range (e.g., FR1) and / or a mmW frequency range (e.g., FR2). In some cases, the UE 702 may be referred to as an initiating UE that initiates the sidelink connection procedure, and the UE 704 may be referred to as a target UE that is targeted for the sidelink connection procedure by the initiating UE.

[0106] To establish a unicast connection, access stratum (AS) (a functional layer in the UMTS and LTE protocol stacks, and part of Layer 2, between the RAN and the UE responsible for transporting data over wireless links and managing radio resources) parameters may be configured and negotiated between the UE 702 and the UE 704. For example, transmission and reception capability matching may be negotiated between the UE 702 and the UE 704. Each UE may have different capabilities (e.g., transmission and reception, 64-ary quadrature amplitude modulation (QAM), transmit diversity, carrier aggregation (CA), supported communication frequency band(s), etc.). In some cases, different services may be supported at higher layers of the corresponding protocol stacks for the UE 702 and the UE 704. Additionally, a security association may be established between the UE 702 and the UE 704 for the unicast connection. Unicast traffic may benefit from security protection (e.g., integrity protection) at the link level. Security requirements may be different for different wireless communication systems. For example, V2X and Uu systems may have different security requirements (e.g., Uu security does not include confidentiality protection). Additionally, IP configurations (e.g., IP version, addresses, etc.) may be negotiated for unicast connections between UE 702 and UE 704.

[0107] In some cases, the UE 704 may create a service announcement (e.g., a service capability message) for transmission over a cellular network (e.g., cV2X) to assist in sidelink connection establishment. Conventionally, the UE 702 may identify and locate candidates for sidelink communication based on a broadcasted basic service message (BSM) that is decrypted by nearby UEs (e.g., the UE 704). The BSM may include location information, security and identification information for the corresponding UE, as well as vehicle information (e.g., speed, operation, size, etc.). However, in the case of a different wireless communication system (e.g., D2D or V2X communication), a discovery channel may not be configured to allow the UE 702 to detect the BSM(s). Thus, the service announcements (e.g., discovery signals) transmitted by the UE 704 and other nearby UEs may be higher layer signals and may be broadcast (e.g., in an NR sidelink broadcast). In some cases, the UE 704 may include one or more parameters for itself, including connection parameters and / or capabilities it possesses, in the service announcement. The UE 702 may then monitor for and receive the broadcasted service announcement to identify possible UEs for the corresponding sidelink connection. In some cases, the UE 702 may identify possible UEs based on the capabilities each UE indicates in their respective service announcements.

[0108] The service announcement may include information to assist the UE 702 (e.g., or any initiating UE) in identifying the UE (UE 704 in the example of FIG. 7) that is sending the service announcement. For example, the service announcement may include channel information in which the direct communication request may be sent. In some cases, the channel information may be RAT-specific (e.g., specific to LTE or NR) and may include a resource pool in which the UE 702 sends the communication request. Additionally, the service announcement may include a specific destination address (e.g., Layer 2 destination address) for the UE if the destination address is different from the current address (e.g., the address of the streaming provider or the UE sending the service announcement). The service announcement may also include a network layer or transport layer for the UE 702 to send the communication request. For example, the network layer (also referred to as "Layer 3" or "L3") or transport layer (also referred to as "Layer 4" or "L4") may indicate a port number of the application for the UE sending the service announcement. In some cases, IP addressing may not be required if the signaling (e.g., PC5 signaling) directly carries a protocol (e.g., real-time transport protocol (RTP)) or provides a locally generated random protocol. Additionally, the service announcement may include the type of protocol for certificate establishment and QoS related parameters.

[0109] After identifying a possible sidelink connection target (UE 704 in the example of FIG. 7), the initiating UE (UE 702 in the example of FIG. 7) may send a connection request 715 to the identified target UE 704. In some cases, the connection request 715 may be a first RRC message (e.g., an "RRC Setup Request" message) sent by the UE 702 to request a unicast connection with the UE 704. For example, the unicast connection may utilize a PC5 interface for sidelink, and the connection request 715 may be an RRC Connection Setup Request message. Additionally, the UE 702 may use a sidelink signaling radio bearer 705 to transport the connection request 715.

[0110] After receiving the connection request 715, the UE 704 may decide whether to accept or reject the connection request 715. The UE 704 may base this decision on transmit / receive capabilities, the ability to accommodate a unicast connection over the sidelink, the particular service indicated for the unicast connection, the content to be transmitted over the unicast connection, or a combination thereof. For example, if the UE 702 desires to use a first RAT to transmit or receive data, but the UE 704 does not support the first RAT, the UE 704 may reject the connection request 715. Additionally or alternatively, the UE 704 may reject the connection request 715 based on an inability to accommodate a unicast connection over the sidelink due to limited radio resources, scheduling issues, etc. Thus, the UE 704 may send an indication of whether the request is accepted or rejected in the connection response 720. Similar to the UE 702 and the connection request 715, the UE 704 may use the sidelink signaling radio bearer 710 to transport the connection response 720. Additionally, the connection response 720 may be a second RRC message sent by the UE 704 in response to the connection request 715 (eg, an “RRC Response” message).

[0111] In some cases, the sidelink signaling radio bearers 705 and 710 may be the same sidelink signaling radio bearer or may be separate sidelink signaling radio bearers. Thus, a radio link control (RLC) layer acknowledged mode (AM) may be used for the sidelink signaling radio bearers 705 and 710. UEs supporting unicast connections may listen on logical channels associated with the sidelink signaling radio bearers. In some cases, the AS layer (i.e., Layer 2) may pass information directly via RRC signaling (e.g., control plane) rather than the V2X layer (e.g., data plane).

[0112] If the connection response 720 indicates that the UE 704 accepted the connection request 715, the UE 702 may then send a connection establishment 725 message on the sidelink signaling radio bearer 705 to indicate that the unicast connection setup is complete. In some cases, the connection establishment 725 may be a third RRC message (e.g., an "RRC Setup Complete" message). Each of the connection request 715, the connection response 720, and the connection establishment 725 may use basic capabilities when in transport from one UE to the other UE to enable each UE to receive and decode the corresponding transmission (e.g., an RRC message).

[0113] Additionally, an identifier may be used for each of the connection request 715, connection response 720, and connection establishment 725. For example, the identifier may indicate which UE 702 / 704 is sending which message and / or which UE 702 / 704 the message is intended for. For physical (PHY) layer channels, RRC signaling and any subsequent data transmissions may use the same identifier (e.g., Layer 2 ID). However, for logical channels, the identifiers may be separate for RRC signaling and for data transmissions. For example, on logical channels, RRC signaling and data transmissions may be treated differently and may have different acknowledgement (ACK) feedback messaging. In some cases, for RRC messaging, a physical layer ACK may be used to ensure that the corresponding message is transmitted and received correctly.

[0114] One or more information elements may be included in the connection request 715 and / or connection response 720 for the UE 702 and / or UE 704, respectively, to enable negotiation of corresponding AS layer parameters for the unicast connection. For example, the UE 702 and / or UE 704 may include Packet Data Convergence Protocol (PDCP) parameters in the corresponding unicast connection setup message to set up a PDCP context for the unicast connection. In some cases, the PDCP context may indicate whether PDCP duplication is utilized for the unicast connection. Additionally, the UE 702 and / or UE 704 may include RLC parameters when establishing the unicast connection to set up an RLC context for the unicast connection. For example, the RLC context may indicate whether AM (e.g., reordering timer (t-reordering) is used) or unacknowledged mode (UM) is used for the RLC layer of the unicast communication.

[0115] Additionally, the UE 702 and / or UE 704 may include medium access control (MAC) parameters to set up a MAC context for the unicast connection. In some cases, the MAC context may enable a resource selection algorithm, a hybrid automatic repeat request (HARQ) feedback scheme (e.g., ACK or negative ACK, NACK feedback), parameters for the HARQ feedback scheme, carrier aggregation, or a combination thereof, for the unicast connection. Additionally, the UE 702 and / or UE 704 may include PHY layer parameters when establishing a unicast connection to set up a PHY layer context for the unicast connection. For example, the PHY layer context may indicate a transmission format (unless a transmission profile is included per UE 702 / 704) and a radio resource configuration (e.g., bandwidth part, BWP, numerology, etc.) for the unicast connection. These information elements may be supported for different frequency range configurations (e.g., FR1 and FR2).

[0116] In some cases, a security context may also be set for the unicast connection (e.g., after the connection establishment 725 message is sent). Before a security association (e.g., security context) is established between the UE 702 and the UE 704, the sidelink signaling radio bearers 705 and 710 may not be protected. After the security association is established, the sidelink signaling radio bearers 705 and 710 may be protected. Thus, the security context may enable secure data transmission over the unicast connection as well as the sidelink signaling radio bearers 705 and 710. Furthermore, IP layer parameters (e.g., link-local IPv4 or IPv6 addresses) may also be negotiated. In some cases, the IP layer parameters may be negotiated by a higher layer control protocol operating after the RRC signaling is established (e.g., the unicast connection is established). As discussed above, the UE 704 may make a decision to accept or reject the connection request 715 based on the particular service(s) indicated for the unicast connection and / or content to be transmitted over the unicast connection (e.g., higher layer information). The particular service(s) and / or content may also be indicated by a higher layer control protocol that operates after the RRC signaling is established.

[0117] After the unicast connection is established, the UE 702 and the UE 704 may communicate using a unicast connection over a sidelink 730, where sidelink data 735 is transmitted between the two UEs 702 and 704. The sidelink 730 may correspond to the sidelinks 162 and / or 168 of FIG. 1. In some cases, the sidelink data 735 may include RRC messages transmitted between the two UEs 702 and 704. To maintain this unicast connection over the sidelink 730, the UE 702 and / or the UE 704 may transmit keep alive messages (e.g., "RRCLinkAlive" messages, fourth RRC messages, etc.). In some cases, the keep alive messages may be triggered (e.g., event triggered) periodically or on demand. Thus, the triggering and transmission of the keep alive messages may be invoked by the UE 702 or by both the UE 702 and the UE 704. Additionally or alternatively, a MAC control element (CE) (e.g., defined over the sidelink 730) may be used to monitor the status of the unicast connection on the sidelink 730 and maintain the connection. When the unicast connection is no longer needed (e.g., when the UE 702 moves far enough away from the UE 704), either the UE 702 and / or the UE 704 may initiate a release procedure to delete the unicast connection over the sidelink 730. Thus, no subsequent RRC messages may be sent between the UE 702 and the UE 704 over the unicast connection.

[0118] NR can support various sidelink ranging and positioning techniques. Sidelink-based ranging allows the determination of the relative distance(s) between UEs and optionally their absolute position(s), where the absolute position of at least one involved UE is known. This technique is beneficial in situations where global navigation satellite system (GNSS) positioning is degraded or unavailable (e.g., tunnels, urban canyons, etc.) and can also improve the accuracy of distance and positioning when GNSS is available. Sidelink-based ranging can be achieved using a three-way handshake for session establishment, followed by an exchange of positioning reference signals (PRS), and terminated by messaging to exchange measurements based on PRS transmissions and receptions from peer UEs.

[0119] Sidelink ranging is based on calculating UE-to-UE round-trip-time (RTT) measurements determined from the transmission and reception times of the PRS (e.g., wideband positioning signals defined in LTE and NR). Each UE reports the RTT measurements along with its location (if known) to all other participating UEs. For UEs with zero or imprecise knowledge of the UE's location, the RTT procedure results in the UE-to-UE distance between the involved UEs. For UEs with precise knowledge of their locations, the distance results in the absolute position. UE joining, PRS transmission, and subsequent RTT calculations are coordinated by an initial three-way messaging handshake (PRS request, PRS response, and PRS confirm) and a message exchange after PRS transmission (PRS post-message) to share measurements after receiving the peer UE's PRS.

[0120] FIG. 8 illustrates an example sidelink ranging and positioning procedure 800 according to an aspect of the disclosure. The sidelink ranging and positioning procedure 800 may also be referred to as a sidelink RTT positioning procedure. Sidelink ranging is based on calculating UE-to-UE RTT measurements determined from the transmission and reception times of a PRS (e.g., a wideband reference signal defined in LTE and NR for positioning). Each UE reports the RTT measurements along with its location (if known) to all other participating UEs. For UEs with zero or imprecise knowledge of their locations, the RTT procedure results in UE-to-UE ranges between the involved UEs that can be used to calculate or estimate relative positions between the UEs. For UEs with precise knowledge of their locations, the ranges can be used to calculate or estimate absolute locations of other participating UEs. UE joining, PRS transmission, and subsequent RTT calculation are coordinated by an initial three-way messaging handshake (PRS request, PRS response, and PRS confirm) and a message exchange after PRS transmission (PRS post message) to share measurements after receiving the peer UE's PRS.

[0121] The sidelink ranging and positioning procedure 800 (or session) begins with the broadcast of capability information by the involved peer UEs in step 805. As shown in FIG. 8, one of the peer UEs, UE 204-1 (e.g., any of the sidelink-capable UEs described herein), may be an anchor UE for the sidelink ranging and positioning procedure 800, meaning that it has a known location. Thus, the anchor UE 204-1 includes an indication in its capability message(s) that it may be an anchor UE for the sidelink ranging and positioning procedure 800. The capability message(s) may also include the location of the anchor UE 204-1, or this may be provided later. The other UE, UE 204-2 (e.g., any other of the sidelink-capable UEs described herein), is a target UE, meaning that it has an unknown or inaccurate location and is attempting to be located. Based on the capability information received from the anchor UE 204-1 indicating that the anchor UE 204-1 is an anchor UE, the target UE 204-2 knows that it can determine its location based on performing a sidelink ranging and positioning procedure 800 with the anchor UE 204-1. To determine its absolute location, the target UE needs to know the location of the anchor UE. However, in the case of relative positioning, the target UE may not need to know the location of the anchor UE since it may only need to determine the location of the target UE relative to the location of the anchor UE. In another aspect, the anchor UE may determine the absolute location of the target UE and provide that information to the target UE.

[0122] After the initial capability exchange, the involved UEs 204 perform a three-way messaging handshake. At stage 810, the anchor UE 204-1 sends a PRS confirm (labeled "PRSrequest") to the target UE 204-2. At stage 815, the target UE 204-2 sends a PRS response (labeled "PRSresponse") to the anchor UE 204-1. At stage 820, the anchor UE 204-1 sends a PRS confirm to the target UE 204-2. At this point, the initial three-way messaging handshake is complete. Note that while FIG. 8 shows the anchor UE 204-1 initiating the three-way messaging handshake, it may instead be initiated by the target UE 204-2.

[0123] In steps 825 and 830, the participating peer UEs 204 transmit the PRS to each other. The resources on which the PRS is transmitted may be configured / allocated by the network (e.g., one of the serving base stations of the UEs 204) or negotiated by the UEs 204 during the initial three-way messaging handshake. The anchor UE 204-1 measures the transmission-to-reception (Tx-Rx) time difference between the transmission time of the PRS in step 825 and the reception time of the PRS in step 830. The target UE 204-2 measures the reception-to-transmission (Rx-Tx) time difference between the reception time of the PRS in step 825 and the transmission time of the PRS in step 830. Note that while FIG. 8 shows the anchor UE 204-1 transmitting the PRS first, the target UE 204-2 may transmit the PRS first instead.

[0124] At steps 835 and 840, the peer UEs 204 exchange their respective time difference measurements in a post-PRS message (labeled "postPRS"). If the anchor UE 204-1 has not yet provided its location to the target UE 204-2, the anchor UE 102-1 may do so at this point. Each UE 204 may then determine the RTT between each UE 204 based on the Tx-Rx time difference measurement and the Rx-Tx time difference measurement (specifically, the difference between the Tx-Rx time difference measurement and the Rx-Tx time difference measurement). Based on the RTT measurement and the speed of light, each UE 204 may then estimate the distance (or range) between the two UEs 204 (specifically, half the RTT measurement multiplied by the speed of light). Since the target UE 204-2 also has the absolute location (eg, geographic coordinates) of the anchor UE 204-1, the target UE 204-2 can use that location and the distance to the anchor UE 204-1 to determine its own absolute location.

[0125] It should be noted that although FIG. 8 shows two UEs 204, a UE may perform or attempt to perform the sidelink ranging and positioning procedure 800 with multiple UEs.

[0126] Another aspect of sidelink positioning is the configuration of sidelink resource pools for positioning (RP-Ps). A sidelink resource pool may consist of one or more slots and one or more subchannels or resource blocks, e.g., within a sidelink bandwidth part, for sidelink communication. In some aspects, the 12 symbols (for slots with normal cyclic prefix) between the first symbol and the last symbol (gap) of a sidelink slot (for automatic gain control, AGC) in the time domain and the allocated subchannel(s) in the frequency domain form a resource pool for sidelink transmission and / or reception. One or more RP-Ps may be configured within the resource pool specifically for positioning purposes. Each RP-P may include an offset, a periodicity, a number of consecutive symbols in a slot (e.g., only one symbol), and / or a bandwidth within a component carrier (or a bandwidth across multiple component carriers). Furthermore, each RP-P may be associated with a zone or a distance from a reference location.

[0127] A base station (or UE) can assign one or more resource configurations from an RP-P to another UE. Additionally or alternatively, a UE (e.g., a relay or remote UE) can request one or more RP-P configurations, which can include in the request one or more of: (1) its location information (or zone identifier), (2) periodicity, (3) bandwidth, (4) offset, (5) number of symbols, and (6) whether a configuration with "low interference" is required (which may be determined via an assigned quality of service (QoS) or priority).

[0128] The base station or UE may configure / assign rate-matching resources or RP-Ps for rate-matching and / or muting to the sidelink UE such that when there is a collision between the assigned resources and another resource pool containing data (PSSCH) and / or control (PSCCH), the sidelink UE is expected to rate-match, mute, and / or puncture data, DMRS, and / or CSI-RS in the conflicting resources. This allows orthogonalization between positioning and data transmission for increased coverage of PRS signals.

[0129] FIG. 9 is a diagram 900 illustrating an example of a resource pool for positioning in a sidelink resource pool according to an aspect of the disclosure. In the example of FIG. 9, time is represented horizontally and frequency is represented vertically. In the time domain, the length of each block is an Orthogonal Frequency Division Multiplexing (OFDM) symbol, and 14 symbols constitute a slot. In the frequency domain, the height of each block is a subchannel. It should be noted that while FIG. 9 illustrates a slot format with 14 symbols for a normal cyclic prefix, the disclosure is not limited thereto and is equally applicable to different slot formats, such as a slot format with 12 symbols for an extended cyclic prefix, and minislots.

[0130] In the example of Fig. 9, the entire slot (except the first and last symbols) may be the resource pool for sidelink transmission and / or reception. That is, any symbol other than the first and last may be assigned for transmission and / or reception. However, the RP-P for sidelink transmission / reception is assigned to the last four pre-gap symbols of the slot. Therefore, non-sidelink positioning data such as user data, CSI-RS, and control information may only be transmitted in the first eight post-AGC symbols and not in the last four pre-gap symbols to avoid collision with the configured RP-P. Non-sidelink positioning data that would otherwise be transmitted in the last four pre-gap symbols may be punctured or muted, or non-sidelink positioning data that would normally span more than eight post-AGC symbols may be rate-matched to fit into the eight post-AGC symbols.

[0131] Sidelink positioning reference signals (SL-PRS) may be defined to enable sidelink positioning procedures between UEs. Similar to downlink PRS (DL-PRS), SL-PRS resources may consist of one or multiple resource elements (e.g., one OFDM symbol in the time domain and one subcarrier in the frequency domain). SL-PRS resources may be designed with comb-based patterns to enable Fast Fourier Transform (FFT)-based processing at the receiver. SL-PRS resources may consist of non-staggered or only partially staggered resource elements in the frequency domain to reduce time of arrival (TOA) uncertainties and overhead for each SL-PRS resource. SL-PRS may also be associated with a specific RP-P (e.g., several SL-PRS may be allocated in several RP-Ps). SL-PRS may also be defined with intra-slot repetition (not shown in FIG. 9) to enable combining gains (if necessary). There may also be inter-UE coordination of RP-P to provide dynamic SL-PRS and data multiplexing while minimizing SL-PRS collisions.

[0132] Rel-16 NR positioning specifies measurement gaps for positioning (MGPs) where the UE may perform DL-PRS measurements. When a UE is configured with measurement gaps, the UE is not expected to process any other DL signals or channels (e.g., SSB for RRM, PRS for positioning, etc.) other than the main signal of interest. Similarly, UE UL transmission is not required during MGPs. In other words, measurement gaps may refer to specific time-frequency resources dedicated to performing measurement(s), such as RRM, positioning, etc. Measurement gaps are typically configured by the network via RRC signaling, and the scheduler takes those gaps into account. Gaps per UE and per FR (e.g., FR1, FR2, etc.) may be defined.

[0133] Thus, the MGP provides a number of advantages. For example, a UE may be operating within one active bandwidth part (BWP), but the DL-PRS signal may be present in a bandwidth that is not entirely within the active BWP. In this scenario, the measurement gap provides an opportunity for the UE to perform frequency retuning, i.e., retune the RF transmit and receive chains to a BW that entirely contains the DL-PRS signal to be measured (and optionally retune back to the original BWP).

[0134] Furthermore, the DL-PRS may have a different timing than the serving cell timing, and therefore the UE may not be able to use a Fast Fourier Transform (FFT) based on the serving cell timing. In this scenario, measurement gaps allow the UE to adjust its timing to accommodate the DL-PRS measurements.

[0135] In addition, the UE typically has limited capacity to process DL-PRS signals in each slot. In this scenario, the measurement gap provides an extra slot after DL-PRS reception but before normal UL / DL transmission resumes, which gives the UE time to complete UE processing of the PRS observed in that occasion. For example, a DL-PRS occasion may be 5 ms long, but the total measurement gap duration may be 10 ms so that the UE gets an additional 5 ms to finish processing.

[0136] To inform the network of the UE's capabilities, the UE may report capability information for processing. The following table shows some of the fields the UE may use for this purpose.

[0137] [Table 1]

[0138] Thus, the UE may report its capabilities for: · Maximum bandwidth in MHz (bandwidth, BW); ·Whether to buffer at slot level or at sub-slot / symbol level; · (N,T): Nms of Uu-PRS (DL-PRS) can be processed every Tms, assuming a maximum BW; · The maximum number of Uu-PRS (DL-PRS) that can be processed in a slot; Whether or not LTE PRS and NR PRS can be processed in parallel (LTE PRS and NR PRS are both Uu-PRS (DL-PRS) and have separate assistance data, independent measurement reports, and independent computation needs).

[0139] In Uu, the network has full control over UE scheduling and can avoid scheduling the UE for the duration of the MGP. However, there is no such consideration for sidelink (SL) positioning. Assuming that processing DL-PRS requires MGP in the UE, processing SL-PRS may also require MGP in the UE. Current standards are silent on the subject of how to manage MGP in the sidelink for sidelink positioning. For example, current standards do not mention, much less define, SL-MGP.

[0140] Accordingly, techniques are presented herein for defining and managing a SL-MGP for measuring SL-PRS signals from a UE, including techniques that allow the UE to advertise its ability to process same. Hereinafter, the term "DL-MGP" refers to an MGP for measuring and processing DL-PRS, and the term "SL-MGP" refers to an MGP for measuring and processing SL-PRS.

[0141] In some aspects, SL-MGP is defined to allow a UE to measure SL-PRS signals from other UEs. During SL-MGP, the UE can retune from a first resource pool (RP1) for (general sidelink) communication to a second (different) resource pool (RP2) for sidelink positioning, measure SL-PRS, and retune to RP1. Note that in some scenarios, such as when RP2 is completely contained within RP1, retuning may not be required. In some aspects, automatic gain control (AGC) settings from RP1 may be carried over to RP2.

[0142] FIG. 10 is a time-frequency diagram 1000 illustrating an exemplary SL-MGP 1002, as well as RP1s 1004 occupying a first bandwidth BW1, and RP2s 1006 occupying a second bandwidth BW2. In the example shown in FIG. 10, the SL-MGP 1002 gives the UE time to process the SL-PRS measurements before it needs to retune from BW1 to BW2, perform SL-PRS measurements during RP2, and optionally repeat the process by retuning back to BW1 to use RP1. Although FIG. 10 shows separate RPs for data and positioning, the same principles may apply even when the same RP is used for data and positioning, e.g., when using the SL-MGP to give the UE additional time to process SL-PRS measurements taken during the SL-MGP. In other words, if the same resource pool is used for data (general sidelink communication) and positioning (SL-PRS measurements), retuning may not be required.

[0143] In some aspects, the UE may advertise its ability to perform processing within the SL-MGP. For example, in some aspects, the UE may advertise its ability to perform processing within the SL-MGP. SL N of SL-PRS during ms time SL A pair of parameters (N SL, T SL) may be defined. In some aspects, the UE may advertise the maximum number of SL-PRS it can process in each millisecond of time. In some aspects, the UE may indicate whether it can perform simultaneous or parallel processing of Uu-PRS and SL-PRS. Thus, a UE according to aspects of the present disclosure may report its capabilities for one or more of the following: ·(N SL ,T SL ):SL-PRS N SL ms is the maximum BW, T SL can be processed every ms; The maximum number of SL-PRS that can be processed in a slot; or ·Whether Uu-PRS and S-PRS can be processed in parallel.

[0144] In NR, the network can configure the UE with DL-MGP to measure DL-PRS. The network can take into account the UE PRS processing capability and the duration of DL-PRS. Additionally or alternatively, the UE may request a specific DL-MGP pattern and / or parameters. For NR sidelink, two sidelink modes are defined: in SL mode 1 (SLMode1), the base station has full control of the sidelink communication, e.g., allocates and manages SL radio resources for SL communication, and in SL mode 2 (SLMode2), the UE, rather than the base station, controls the sidelink communication, e.g., autonomously selects SL radio resources from a resource pool.

[0145] For SL mode 1, in some aspects, the network configures the UE with at least one SL-MGP. The network may configure the at least one SL-MGP to include additional processing time, and the amount of additional processing time may be based on the pattern of the SL-PRS. A location server (e.g., LMF) may be aware of all SL-PRS configurations of UEs in a geographic area and may combine this information with the UE capability information to determine the SL-MGP pattern, e.g., as described with respect to FIG. 6A and FIG. 6B. In some aspects, the UE may request the SL-MGP for SL-PRS measurements. In SL mode 1, the network may ensure that no SL transmissions are scheduled to the target UE during that SL-MGP period. It should be noted that the SL-MGP(s) may affect the UE's ability to transmit on other carriers that are not directly associated with the SL transmission. Thus, in some aspects, the UE may inform the network that it requires per-FR, per-CC, and / or per-UE measurement gaps.

[0146] For both SL mode 1 and SL mode 2, in some aspects, upon receiving a configuration of SL-PRS from one or more neighboring UEs, the target UE may autonomously determine an SL-MGP configuration including at least one SL-MGP. The SL-MGP configuration may include an SL-MGP pattern, duration, periodicity, and / or persistence (number of periods for which the SL-MGP applies). In some aspects, the UE may choose to include a subset of neighboring UEs, ignore SL-PRS from a (different) subset of UEs, or both, based on channel characteristics such as RSRP and / or other metrics such as the number of anchors required for positioning. In some aspects, the UE may advertise information regarding the determined SL-MGP to neighboring UEs, so that any groupcast / unicast messages can be sent without overlapping with the UL-MGP, if feasible. In some aspects, the UE may advertise the SL-MGP pattern, duration, and persistence information (e.g., the UE will apply the SL-MGP for at least M periods, etc.). In some aspects, the UE may advertise that one or more SL-MGPs may be further extended. In some aspects, the UE may advertise this information either via a new or modified sidelink control information (SCI) format, or with a new sidelink MAC-CE, or with an RRC or RRC-like message.

[0147] In a scenario with an active Uu connection, in some aspects, the UE may inform the base station of at least one instance of the SL-MGP and / or the determined SL-MGP configuration so that the base station can avoid scheduling on DL and / or UL slots that overlap with the SL-MGP.

[0148] In some situations, the network may want to schedule high priority traffic (either on Uu or SL), and resources for high priority traffic may overlap with SL-MGP that was either previously configured by the network or autonomously determined by the target UE. In the case of SL mode 1, in some aspects, the network may send DCI or MAC-CE to cancel one or more specific instances of SL-MGP. For both SL mode 1 and SL mode 2, the indication of high priority traffic may come from UE upper layers or from other UEs that want to send data to the target UE. In these situations, in some aspects, the UE may be expected to drop SL-PRS processing for the corresponding one or more instances of SL-MGP after receiving such an indication. In some aspects, the UE does not drop the SL-PRS processing if the indication was not received at least a threshold number of slots prior to the respective SL-MGP instance.

[0149] 11A-11C are time-frequency diagrams illustrating example SL-MGPs with different durations according to aspects of the disclosure. Figures 11A-11C illustrate a scenario in which a UE (autonomously) determines its own SL-MGP 1002 by observing the SL-PRS configuration(s) indicated by anchors and / or neighboring UE(s) participating in a positioning session. Figures 11A-11C illustrate an example in which SL communications are in resource pool RP1 1004 and SL-PRS signals are in resource pool RP2 1006.

[0150] As shown in FIG. 11A, in some aspects, the SL-MGP 1100 starts T1 ms before the first SL-PRS instance at occasion 1102 (e.g., to retune the RF transceiver), continues for a time T2 ms while the SL-PRS is transmitted, and ends after T3 ms of processing time to process the received SL-PRS signal for a total amount of time T4. T4 may refer to the measurement gap length (MGL) of FIG. 6B. In FIG. 11A, the SL-MGP 1100 ends before the end of RP2 1006, and thus the SL-MGP 1100 duration T4 is entirely contained within RP2 1006.

[0151] 11B, in some aspects, the SL-MGP 1104 includes additional processing time after RP2 1006 is completed (T3'>T3), starting immediately after the end of RP2 1006. In other words, the SL-MGP 1104 extends continuously beyond the end of RP2 to include the additional processing time. The total duration of the SL-MGP 1104 is T4', where T4'>T4. In this aspect, the additional processing time is provided regardless of whether the next slot is a resource in the DL, UL, or other SL RP.

[0152] As shown in FIG. 11C, in some aspects, the SL-MGP 1106 also includes some additional time period after the end of RP2, but does not begin until the next time the designated RP (e.g., RP1 1004) begins. In some aspects, the additional time cannot be taken from DL and UL slots, but instead must be taken only from the designated SL slots. In other aspects, the additional time may be taken from slots that contain signals having a lower priority than the SL-PRS signals. This may result in unpredictable behavior, since the occurrence of lower priority signals may not be deterministic. That is, the UE cannot always guarantee that the next slot will contain a lower priority signal that may be preempted in favor of additional processing of the received SL-PRS signal.

[0153] Moreover, in SL mode 1, the location server may coordinate with the base station to enable clustered transmission of SL-PRS, which ensures less or minimal interruption of data transmission when measuring SL-PRS, but in SL mode 2, this is not feasible since UEs may not necessarily coordinate with each other regarding SL-PRS transmission in the resource pool. Thus, in some aspects of the disclosure, UEs may coordinate to ensure clustered transmission of SL-PRS signals. For example, if one UE selects slot n, comb offset 1, another UE may select the same slot and symbol with a different comb offset, e.g., as a high priority option. If comb multiplexing is not feasible, other UEs may select different resources in the same slot or resources in the nearest slot to ensure compact transmission of SL-PRS from multiple UEs. In some aspects, these patterns may be learned over time using a coordination algorithm.

[0154] FIG. 12 is a flowchart of an example process 1200 associated with sidelink measurements and processing gaps for positioning according to aspects of the disclosure. In some implementations, one or more process blocks of FIG. 12 may be performed by a user equipment (UE) (e.g., the UE 104). In some implementations, one or more process blocks of FIG. 12 may be performed by another device or a group of devices that are separate from or include the UE. Additionally or alternatively, one or more process blocks of FIG. 12 may be performed by one or more components of the UE 302, such as the processor(s) 332, memory 340, WWAN transceiver(s) 310, short-range radio transceiver(s) 320, satellite signal receiver 330, sensor(s) 344, user interface 346, and sidelink manager(s) 342, any or all of which may be means for performing the operations of the process 1200.

[0155] 12, in block 1210, the process 1200 may include determining a sidelink measurement gap for positioning (SL-MGP). Means for performing the operation of block 1210 may include the processor(s) 332, memory 340, or WWAN transceiver(s) 310 of the UE 302. For example, the UE 302 may receive, using the receiver(s) 312, information indicating or defining the SL-MGP from a base station or a location server.

[0156] In some aspects, determining the SL-MGP includes determining the SL-MGP based on first information indicative of an SL-PRS processing capability of the UE. In some aspects, the first information includes at least one of an indication that the UE can or cannot process SL-PRS, an indication of a maximum number of SL-PRS signals the UE can process simultaneously, an indication of a maximum number of SL-PRS signals the UE can process per unit time, or an indication that the UE can or cannot process SL-PRS and non-SL-PRS signals simultaneously. In some aspects, determining the SL-MGP includes sending the first information to a base station or a location server and receiving the SL-MGP from the base station or the location server.

[0157] In some aspects, determining the SL-MGP includes determining a duration for the SL-MGP. In some aspects, determining the duration for the SL-MGP includes setting the duration for the SL-MGP to be a sum of one or more of: a first duration for retuning an RF transceiver to a bandwidth occupied by a first resource pool for positioning including at least one SL-PRS, a second duration for SL-PRS signal transmission, or a third duration for processing SL-PRS signal transmission.

[0158] In some aspects, determining the SL-MGP includes coordinating with at least one other UE involved in the sidelink communication to cluster the SL-PRS transmissions and define a SL-MGP that includes the clustered SL-PRS transmissions.

[0159] 12, at block 1220, the process 1200 may include performing sidelink positioning during SL-MGP using at least one sidelink positioning reference signal (SL-PRS). Means for performing the operation of block 1220 may include the processor(s) 332, memory 340, or WWAN transceiver(s) 310 of the UE 302. For example, the UE 302 may perform sidelink positioning during SL-MGP using the receiver(s) 312 or the transmitter(s) 314. In some aspects, performing sidelink positioning during SL-MGP using at least one SL-PRS includes at least one of transmitting the SL-PRS or receiving the SL-PRS. In some aspects, performing sidelink positioning during the SL-MGP includes retuning a radio frequency (RF) transceiver of the UE from a first bandwidth occupied by a resource pool for data communication to a second bandwidth occupied by a resource pool for positioning during the SL-MGP, performing sidelink positioning within the second bandwidth, and retuning the RF transceiver of the UE back to the first bandwidth.

[0160] In some aspects, the SL-MGP occupies a portion of the time domain included in the resource pool for positioning, as shown in FIG. 11A. In some aspects, as shown in FIG. 11B and FIG. 11C, a first portion of the SL-MGP occupies a portion of the time domain in the resource pool for positioning, and a second portion of the SL-MGP occupies a portion of the time domain not in the resource pool for positioning. In some aspects, as shown in FIG. 11B, the second portion of the SL-MGP is contiguous in time with the first portion of the SL-MGP. In other aspects, as shown in FIG. 11C, the second portion of the SL-MGP is not contiguous in time with the first portion of the SL-MGP. In some aspects, the second portion of the SL-MGP occupies only slots designated for sidelink communications. In other aspects, the second portion of the SL-MGP may occupy slots designated for sidelink communications or slots designated for communications having a lower priority than sidelink communications.

[0161] Process 1200 may include additional implementations, such as any single implementation or any combination of implementations described below and / or with respect to one or more other processes described elsewhere herein. Although Figure 12 illustrates example blocks of process 1200, in some implementations process 1200 may include additional, fewer, different, or differently configured blocks than those illustrated in Figure 12. Additionally or alternatively, two or more of the blocks of process 1200 may be performed in parallel.

[0162] 13 is a flowchart of an example process 1300 associated with sidelink measurements and processing gaps for positioning according to an aspect of the disclosure. In some implementations, one or more process blocks of FIG. 13 may be performed by a network entity (NE) (e.g., base station 102, location server 172). In some implementations, one or more process blocks of FIG. 13 may be performed by another device or a group of devices that are separate from the NE or include a UE. Additionally or alternatively, one or more process blocks of FIG. 13 may be performed by one or more components of the base station 304 or the network entity 306, such as the processor(s) 384 or 394, the memory 386 or 396, the network transceiver(s) 380 or 390, and the sidelink manager(s) 388 or 398, any or all of which may be a means for performing the operations of the process 1300.

[0163] 13, at block 1310, the process 1300 may include receiving, from a user equipment (UE), first information indicating the SL-PRS processing capability of the UE. Means for performing the operation of block 1310 may include a processor(s) 384 or 394, a memory 386 or 396, or a WWAN transceiver 350 or a network transceiver(s) 390 of the base station 304 or the network entity 306, respectively. For example, the base station 304 or the NE 306 may receive, from the user equipment (UE), the first information indicating the SL-PRS processing capability of the UE using the WWAN transceiver 350 or the network transceiver 390, respectively.

[0164] As further shown in FIG. 13, in block 1320, the process 1300 may include determining a sidelink measurement gap for positioning (SL-MGP) based at least in part on the first information. Means for performing the operation of block 1320 may include a processor(s) 384 or 394, a memory 386 or 396, or a network transceiver(s) 380 or 390 of the base station 204 or the network entity 306, respectively. For example, the base station 304 may use the processor(s) 384 to determine a sidelink measurement gap for positioning (SL-MGP) based at least in part on the first information. In some aspects, the first information includes at least one of an indication that the UE can or cannot process SL-PRS, an indication of a maximum number of SL-PRS signals that the UE can process simultaneously, an indication of a maximum number of SL-PRS signals that the UE can process per unit time, or an indication that the UE can or cannot process SL-PRS signals and non-SL-PRS signals simultaneously.

[0165] In some aspects, determining the SL-MGP includes determining a duration for the SL-MGP. In some aspects, determining the duration for the SL-MGP includes setting the duration for the SL-MGP to be the sum of one or more of: a first duration for retuning an RF transceiver of the UE to a bandwidth occupied by a first resource pool for positioning including at least one SL-PRS, a second duration for the UE to transmit or receive an SL-PRS signal transmission, or a third duration for the UE to process an SL-PRS signal transmission. In some aspects, determining the SL-MGP includes determining the SL-MGP based on information received from a plurality of UEs.

[0166] 13, at block 1330, the process 1300 may include sending the second information indicating the SL-MGP to the UE. In some aspects, the second information may be part of configuration information or assistance data sent from the base station or the location server to the UE. Means for performing the operations of block 1330 may include the processor(s) 384 or 394, memory 386 or 396, or network transceiver(s) 380 or 390 of the base station 304 or the network entity 306, respectively. For example, the base station 304 may send the second information indicating the SL-MGP to the UE using the transmitter(s) 354.

[0167] Process 1300 may include additional implementations, such as any single implementation or any combination of implementations described below and / or with respect to one or more other processes described elsewhere herein. Although Figure 13 illustrates example blocks of process 1300, in some implementations process 1300 may include additional, fewer, different, or differently configured blocks than those illustrated in Figure 13. Additionally or alternatively, two or more of the blocks of process 1300 may be performed in parallel.

[0168] As will be appreciated, a technical advantage of methods 1200 and 1300 may be that the use of the SL-MGP provides a window in which the UE can perform SL positioning and have time to process SL-PRS measurements (and optionally retune its RF transceiver, if necessary) without having to also process other DL signals and / or transmit other UL signals. If the SL-MGP is controlled by the network, the UE can report its capabilities for sidelink positioning to the network, such as its capabilities to process SL-PRS, which the network can take into account when configuring the SL-MGP. If the SL-MGP is controlled by the UE, the UE can share its capabilities with other UEs involved in sidelink communication, so that they can collectively determine an optical SL-MGP and cluster their individual SL-PRS within that SL-MGP.

[0169] In the above detailed description, it can be seen that in each example, various features are grouped together. This manner of disclosure should not be understood as an intention that the exemplary clauses have more features than are expressly stated in each clause. Rather, various aspects of the disclosure may include fewer features than all features of each disclosed exemplary clause. Thus, the following clauses should be considered to be incorporated in the description, and each clause may stand alone as a separate example. Although each dependent clause may refer to a specific combination with one of the other clauses in the clause, the aspect(s) of the dependent clause are not limited to that specific combination. It will be understood that other exemplary clauses may also include combinations of the aspect(s) of the dependent clause with any other dependent clause or subject matter of the independent clause, or combinations of any features with other dependent clauses and independent clauses. Various aspects disclosed herein expressly include combinations of specific combinations (e.g., inconsistent aspects, such as defining an element as both an electrical insulator and an electrical conductor) unless these combinations are expressly expressed or can be easily inferred to be not intended. It is further contemplated that aspects of a clause may be included in any other independent clause, even if the clause is not directly dependent on the independent clause.

[0170] The following numbered clauses describe example implementations.

[0171] Clause 1. A method of wireless positioning performed by a user equipment (UE), comprising: determining a sidelink measurement gap (SL-MGP) for positioning; and performing sidelink positioning during the SL-MGP using at least one sidelink positioning reference signal (SL-PRS).

[0172] Clause 2. The method of clause 1, wherein determining the SL-MGP includes receiving the SL-MGP from a base station or a location server.

[0173] Clause 3. The method of clause 1 or 2, wherein determining the SL-MGP includes determining the SL-MGP based on first information indicating the UE's SL-PRS processing capability.

[0174] Clause 4. The method of clause 3, wherein the first information includes at least one of an indication that the UE can or cannot process SL-PRS, an indication of a maximum number of SL-PRS signals that the UE can process simultaneously, an indication of a maximum number of SL-PRS signals that the UE can process per unit time, or an indication that the UE can or cannot process SL-PRS signals and non-SL-PRS signals simultaneously.

[0175] Clause 5. The method of clause 3 or 4, wherein determining the SL-MGP includes sending the first information to a base station or a location server, and receiving the SL-MGP from the base station or the location server.

[0176] Clause 6. The method of any one of clauses 1-5, wherein determining SL-MGP comprises determining a duration for SL-MGP.

[0177] Clause 7. The method of clause 6, wherein determining the duration for the SL-MGP includes setting the duration for the SL-MGP to be the sum of one or more of a first duration for retuning a UE's transceiver to a bandwidth occupied by a first resource pool for positioning including at least one SL-PRS, a second duration for SL-PRS signal transmission, or a third duration for processing SL-PRS signal transmission.

[0178] Clause 8. The method of any one of clauses 1 to 7, wherein determining the SL-MGP includes coordinating with at least one other UE involved in the sidelink communication to cluster the SL-PRS transmissions and define a SL-MGP including the clustered SL-PRS transmissions.

[0179] Clause 9. The method of any one of clauses 1 to 8, wherein performing sidelink positioning during SL-MGP using at least one SL-PRS includes at least one of transmitting a SL-PRS or receiving a SL-PRS.

[0180] Clause 10. A method according to any one of clauses 1 to 9, wherein performing sidelink positioning using at least one SL-PRS during SL-MGP comprises retuning a transceiver of the UE during SL-MGP from a first bandwidth occupied by a resource pool for data communication to a second bandwidth occupied by a resource pool for positioning, performing sidelink positioning within the second bandwidth, and retuning the transceiver of the UE back to the first bandwidth.

[0181] Clause 11. The method according to clause 10, wherein the SL-MGP occupies a portion of a time domain included in a resource pool for positioning.

[0182] Clause 12. The method according to clause 10 or 11, wherein a first part of the SL-MGP occupies a portion of a time domain within a resource pool for positioning and a second part of the SL-MGP occupies a portion of a time domain not within the resource pool for positioning.

[0183] Clause 13. The method of clause 12, wherein the second portion of the SL-MGP is continuous in time with the first portion of the SL-MGP.

[0184] Clause 14. The method of clause 12 or 13, wherein the second portion of the SL-MGP is not contiguous in time with the first portion of the SL-MGP.

[0185] Clause 15. The method of clause 14, wherein the second part of the SL-MGP occupies slots designated for sidelink communications.

[0186] Clause 16. The method according to clause 14 or 15, wherein the second part of the SL-MGP occupies slots designated for sidelink communications or for communications having a lower priority than sidelink communications.

[0187] Clause 17. A method of wireless positioning implemented by a network entity, the method comprising: receiving, from a user equipment (UE), first information indicative of a sidelink positioning reference signal (SL-PRS) processing capability of the UE; determining a sidelink measurement gap (SL-MGP) for positioning based at least in part on the first information; and sending second information indicative of the SL-MGP to the UE.

[0188] Clause 18. The method of clause 17, wherein the first information includes at least one of an indication that the UE is capable or incapable of processing SL-PRS, an indication of a maximum number of SL-PRS signals that the UE can process simultaneously, an indication of a maximum number of SL-PRS signals that the UE can process per unit time, or an indication that the UE is capable or incapable of processing SL-PRS signals and non-SL-PRS signals simultaneously.

[0189] Clause 19. The method of clause 17 or 18, wherein determining SL-MGP comprises determining a duration for SL-MGP.

[0190] Clause 20. The method of clause 19, wherein determining the duration for the SL-MGP includes setting the duration for the SL-MGP to be the sum of one or more of: a first duration for retuning a transceiver of the UE to a bandwidth occupied by a first resource pool for positioning including at least one SL-PRS, a second duration for the UE to at least one of transmitting or receiving an SL-PRS signal transmission, or a third duration for the UE to process an SL-PRS signal transmission.

[0191] Clause 21. The method of any one of clauses 17 to 20, wherein determining the SL-MGP includes determining the SL-MGP based on information received from a plurality of UEs.

[0192] Clause 22. A method according to any one of clauses 17 to 21, wherein sending the second information to the UE indicating the SL-MGP includes sending the second information as part of configuration information or assistance data sent from the base station or location server to the UE.

[0193] Clause 23. The method according to any one of clauses 17 to 22, wherein the network entity comprises a base station or a location server.

[0194] Clause 24. A UE comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, wherein the at least one processor is configured to determine a sidelink measurement gap (SL-MGP) for positioning and to perform sidelink positioning during the SL-MGP using at least one sidelink positioning reference signal (SL-PRS).

[0195] Clause 25. The UE of clause 24, wherein to determine the SL-MGP, the at least one processor is configured to receive the SL-MGP from a base station or a location server.

[0196] Clause 26. A UE as described in clause 24 or 25, wherein to determine the SL-MGP, at least one processor is configured to determine the SL-MGP based on first information indicating the UE's SL-PRS processing capability.

[0197] Clause 27. A UE as described in Clause 26, wherein the first information includes at least one of an indication that the UE is capable or incapable of processing SL-PRS, an indication of a maximum number of SL-PRS signals that the UE is capable of processing simultaneously, an indication of a maximum number of SL-PRS signals that the UE is capable of processing per unit time, or an indication that the UE is capable or incapable of processing SL-PRS signals and non-SL-PRS signals simultaneously.

[0198] Clause 28. A UE as described in clause 26 or 27, wherein at least one processor is configured to send first information to a base station or a location server and receive the SL-MGP from the base station or the location server to determine the SL-MGP.

[0199] Clause 29. A UE as described in any one of clauses 24 to 28, wherein to determine the SL-MGP, at least one processor is configured to determine a duration for the SL-MGP.

[0200] Clause 30. The UE of clause 29, wherein to determine a duration for the SL-MGP, at least one processor is configured to set the duration for the SL-MGP to be the sum of one or more of a first duration for retuning the UE's transceiver to a bandwidth occupied by a first resource pool for positioning including at least one SL-PRS, a second duration for SL-PRS signal transmission, or a third duration for processing the SL-PRS signal transmission.

[0201] Clause 31. A UE as described in any one of clauses 24 to 30, wherein to determine the SL-MGP, at least one processor is configured to coordinate with at least one other UE involved in sidelink communication to cluster SL-PRS transmissions and define a SL-MGP comprising the clustered SL-PRS transmissions.

[0202] Clause 32. A UE as described in any one of clauses 24 to 31, wherein at least one processor is configured to transmit an SL-PRS or receive an SL-PRS to perform sidelink positioning during SL-MGP using at least one SL-PRS.

[0203] Clause 33. A UE as described in any one of clauses 24 to 32, wherein in order to perform sidelink positioning using at least one SL-PRS during SL-MGP, at least one processor is configured to retune a transceiver of the UE during SL-MGP from a first bandwidth occupied by a resource pool for data communication to a second bandwidth occupied by a resource pool for positioning, perform sidelink positioning within the second bandwidth, and retune the transceiver of the UE back to the first bandwidth.

[0204] Clause 34. The UE of clause 33, wherein the SL-MGP occupies a portion of a time domain included in a resource pool for positioning.

[0205] Clause 35. A UE as described in clause 33 or 34, wherein a first part of the SL-MGP occupies a portion of a time domain within a resource pool for positioning and a second part of the SL-MGP occupies a portion of a time domain not within the resource pool for positioning.

[0206] Clause 36. The UE of clause 35, wherein the second part of the SL-MGP is contiguous in time with the first part of the SL-MGP.

[0207] Clause 37. The UE of clause 35 or 36, wherein the second part of the SL-MGP is not contiguous in time with the first part of the SL-MGP.

[0208] Clause 38. The UE of clause 37, wherein the second part of the SL-MGP occupies slots designated for sidelink communications.

[0209] Clause 39. The UE of clause 37 or 38, wherein the second part of the SL-MGP occupies slots designated for sidelink communications or for communications having a lower priority than sidelink communications.

[0210] Clause 40. A network entity comprising: a memory; at least one transceiver; and at least one processor communicatively coupled to the memory and the at least one transceiver, wherein the at least one processor is configured to receive, from a user equipment (UE) via the at least one transceiver, first information indicative of a sidelink positioning reference signal (SL-PRS) processing capability of the UE, determine a sidelink measurement gap (SL-MGP) for positioning based at least in part on the first information, and send, to the UE via the at least one transceiver, second information indicative of the SL-MGP.

[0211] Clause 41. A network entity as described in clause 40, wherein the first information includes at least one of an indication that the UE is capable or incapable of processing SL-PRS, an indication of a maximum number of SL-PRS signals that the UE can process simultaneously, an indication of a maximum number of SL-PRS signals that the UE can process per unit time, or an indication that the UE is capable or incapable of processing SL-PRS signals and non-SL-PRS signals simultaneously.

[0212] Clause 42. The network entity of clause 40 or 41, wherein to determine the SL-MGP, at least one processor is configured to determine a duration for the SL-MGP.

[0213] Clause 43. The network entity described in Clause 42, wherein to determine the duration for the SL-MGP, at least one processor is configured to set the duration for the SL-MGP to be the sum of one or more of: a first duration for retuning the UE's transceiver to a bandwidth occupied by a first resource pool for positioning including at least one SL-PRS, a second duration for the UE to at least one of transmitting or receiving an SL-PRS signal transmission, or a third duration for the UE to process an SL-PRS signal transmission.

[0214] Clause 44. A network entity according to any one of claims 40 to 43, wherein to determine the SL-MGP, at least one processor is configured to determine the SL-MGP based on information received from a plurality of UEs.

[0215] Clause 45. A network entity according to any one of claims 40 to 44, wherein at least one processor is configured to send the second information indicating the SL-MGP to the UE as part of configuration information or assistance data sent from a base station or a location server to the UE.

[0216] Clause 46. A network entity according to any one of clauses 40 to 45, wherein the network entity comprises a base station or a location server.

[0217] Clause 47. A user equipment (UE), comprising: means for determining a sidelink measurement gap (SL-MGP) for positioning; and means for performing sidelink positioning during the SL-MGP using at least one sidelink positioning reference signal (SL-PRS).

[0218] Clause 48. The UE of clause 47, wherein the means for determining the SL-MGP comprises means for receiving the SL-MGP from a base station or a location server.

[0219] Clause 49. The UE of clause 47 or 48, wherein the means for determining the SL-MGP comprises means for determining the SL-MGP based on first information indicative of an SL-PRS processing capability of the UE.

[0220] Clause 50. A UE as described in clause 49, wherein the first information includes at least one of an indication that the UE is capable or incapable of processing SL-PRS, an indication of a maximum number of SL-PRS signals that the UE can process simultaneously, an indication of a maximum number of SL-PRS signals that the UE can process per unit time, or an indication that the UE is capable or incapable of processing SL-PRS signals and non-SL-PRS signals simultaneously.

[0221] Clause 51. A UE as described in clause 49 or 50, wherein the means for determining the SL-MGP includes means for sending first information to a base station or a location server, and means for receiving the SL-MGP from the base station or the location server.

[0222] Clause 52. A UE as described in any one of clauses 47 to 51, wherein the means for determining the SL-MGP includes means for determining a duration for the SL-MGP.

[0223] Clause 53. The UE of clause 52, wherein the means for determining a duration for the SL-MGP includes means for setting the duration for the SL-MGP to be the sum of one or more of a first duration for retuning the UE's transceiver to a bandwidth occupied by a first resource pool for positioning including at least one SL-PRS, a second duration for SL-PRS signal transmission, or a third duration for processing SL-PRS signal transmission.

[0224] Clause 54. A UE as described in any one of clauses 47 to 53, wherein the means for determining the SL-MGP includes means for coordinating with at least one other UE involved in sidelink communication to cluster SL-PRS transmissions and define a SL-MGP comprising the clustered SL-PRS transmissions.

[0225] Clause 55. A UE as described in any one of clauses 47 to 54, wherein the means for performing sidelink positioning during SL-MGP using at least one SL-PRS includes at least one of a means for transmitting an SL-PRS or a means for receiving an SL-PRS.

[0226] Clause 56. A UE as described in any one of clauses 47 to 55, wherein the means for performing sidelink positioning during SL-MGP using at least one SL-PRS includes means for retuning a transceiver of the UE from a first bandwidth occupied by a resource pool for data communication to a second bandwidth occupied by a resource pool for positioning during the SL-MGP, means for performing sidelink positioning within the second bandwidth, and means for retuning the transceiver of the UE back to the first bandwidth.

[0227] Clause 57. The UE of clause 56, wherein the SL-MGP occupies a portion of a time domain included in a resource pool for positioning.

[0228] Clause 58. A UE as described in clause 56 or 57, wherein a first part of the SL-MGP occupies a portion of a time domain within a resource pool for positioning and a second part of the SL-MGP occupies a portion of a time domain not within the resource pool for positioning.

[0229] Clause 59. The UE of clause 58, wherein the second part of the SL-MGP is contiguous in time with the first part of the SL-MGP.

[0230] Clause 60. The UE of clause 58 or 59, wherein the second part of the SL-MGP is not contiguous in time with the first part of the SL-MGP.

[0231] Clause 61. The UE of clause 60, wherein the second part of the SL-MGP occupies slots designated for sidelink communications.

[0232] Clause 62. The UE of clause 60 or 61, wherein the second part of the SL-MGP occupies slots designated for sidelink communications or for communications having a lower priority than sidelink communications.

[0233] Clause 63. A network entity comprising: means for receiving, from a user equipment (UE), first information indicating a sidelink positioning reference signal (SL-PRS) processing capability of the UE; means for determining a sidelink measurement gap (SL-MGP) for positioning based at least in part on the first information; and means for sending second information indicating the SL-MGP to the UE.

[0234] Clause 64. A network entity as described in clause 63, wherein the first information includes at least one of an indication that the UE is capable or incapable of processing SL-PRS, an indication of a maximum number of SL-PRS signals that the UE can process simultaneously, an indication of a maximum number of SL-PRS signals that the UE can process per unit time, or an indication that the UE is capable or incapable of processing SL-PRS signals and non-SL-PRS signals simultaneously.

[0235] Clause 65. The network entity according to clause 63 or 64, wherein the means for determining the SL-MGP comprises means for determining a duration for the SL-MGP.

[0236] Clause 66. The network entity described in clause 65, wherein the means for determining a duration for the SL-MGP includes means for setting the duration for the SL-MGP to be the sum of one or more of: a first duration for retuning a transceiver of the UE to a bandwidth occupied by a first resource pool for positioning including at least one SL-PRS, a second duration for the UE to at least one of transmitting or receiving an SL-PRS signal transmission, or a third duration for the UE to process an SL-PRS signal transmission.

[0237] Clause 67. The network entity according to any one of clauses 63 to 66, wherein the means for determining the SL-MGP comprises means for determining the SL-MGP based on information received from a plurality of UEs.

[0238] Clause 68. A network entity according to any one of clauses 63 to 67, wherein the means for sending the second information indicating the SL-MGP to the UE comprises means for sending the second information as part of configuration information or assistance data sent from a base station or a location server to the UE.

[0239] Clause 69. A network entity according to any one of clauses 63 to 68, wherein the network entity comprises a base station or a location server.

[0240] Clause 70. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to determine a sidelink measurement gap (SL-MGP) for positioning and to perform sidelink positioning during the SL-MGP using at least one sidelink positioning reference signal (SL-PRS).

[0241] Clause 71. A non-transitory computer-readable medium as described in Clause 70, comprising computer-executable instructions that, when executed by the UE, cause the UE to determine an SL-MGP, and computer-executable instructions that, when executed by the UE, cause the UE to receive an SL-MGP from a base station or a location server.

[0242] Clause 72. A non-transitory computer-readable medium as described in Clause 70 or 71, comprising computer-executable instructions that, when executed by a UE, cause the UE to determine an SL-MGP, and that, when executed by the UE, cause the UE to determine an SL-MGP based on first information indicating the UE's SL-PRS processing capabilities.

[0243] Clause 73. The non-transitory computer-readable medium of clause 72, wherein the first information includes at least one of an indication that the UE is capable or incapable of processing SL-PRS, an indication of a maximum number of SL-PRS signals that the UE is capable of processing simultaneously, an indication of a maximum number of SL-PRS signals that the UE is capable of processing per unit time, or an indication that the UE is capable or incapable of processing SL-PRS signals and non-SL-PRS signals simultaneously.

[0244] Clause 74. A non-transitory computer-readable medium as described in Clause 72 or 73, comprising computer-executable instructions that, when executed by the UE, cause the UE to determine an SL-MGP, and computer-executable instructions that, when executed by the UE, cause the UE to send first information to a base station or location server and receive the SL-MGP from the base station or location server.

[0245] Clause 75. A non-transitory computer-readable medium as described in any one of clauses 70 to 74, comprising computer-executable instructions that, when executed by a UE, cause the UE to determine a SL-MGP, and computer-executable instructions that, when executed by the UE, cause the UE to determine a duration for the SL-MGP.

[0246] Clause 76. A non-transitory computer-readable medium as described in Clause 75, comprising computer-executable instructions that, when executed by a UE, cause the UE to determine a duration for the SL-MGP, and computer-executable instructions that, when executed by the UE, cause the UE to set the duration for the SL-MGP to be the sum of one or more of: a first duration for retuning the UE's transceiver to a bandwidth occupied by a first resource pool for positioning including at least one SL-PRS, a second duration for SL-PRS signal transmission, or a third duration for processing SL-PRS signal transmission.

[0247] Clause 77. A non-transitory computer-readable medium as described in any one of clauses 70 to 76, comprising computer-executable instructions that, when executed by a UE, cause the UE to determine an SL-MGP, and that, when executed by the UE, cause the UE to coordinate with at least one other UE involved in sidelink communications to cluster SL-PRS transmissions and define an SL-MGP comprising the clustered SL-PRS transmissions.

[0248] Clause 78. A non-transitory computer-readable medium as described in any one of clauses 70 to 77, comprising computer-executable instructions that, when executed by a UE, cause the UE to perform sidelink positioning during a SL-MGP using at least one SL-MGP, and computer-executable instructions that, when executed by the UE, cause the UE to transmit an SL-PRS or receive an SL-PRS.

[0249] Clause 79. A non-transitory computer-readable medium as described in any one of Clauses 70 to 78, comprising computer-executable instructions that, when executed by a UE, cause the UE to perform sidelink positioning during SL-MGP using at least one SL-PRS, and that, when executed by the UE, cause the UE to retune its transceiver during SL-MGP from a first bandwidth occupied by a resource pool for data communication to a second bandwidth occupied by a resource pool for positioning, perform sidelink positioning within the second bandwidth, and retune its transceiver back to the first bandwidth.

[0250] Clause 80. The non-transitory computer-readable medium of clause 79, wherein the SL-MGP occupies a portion of a time domain included within a resource pool for positioning.

[0251] Clause 81. A non-transitory computer-readable medium as described in clause 79 or 80, wherein a first part of the SL-MGP occupies a portion of a time domain within a resource pool for positioning, and a second part of the SL-MGP occupies a portion of a time domain not within the resource pool for positioning.

[0252] Clause 82. The non-transitory computer readable medium of clause 81, wherein the second portion of the SL-MGP is contiguous in time with the first portion of the SL-MGP.

[0253] Clause 83. The non-transitory computer readable medium of clause 81 or 82, wherein the second portion of the SL-MGP is not contiguous in time with the first portion of the SL-MGP.

[0254] Clause 84. The non-transitory computer-readable medium of clause 83, wherein the second portion of the SL-MGP occupies a slot designated for sidelink communications.

[0255] Clause 85. The non-transitory computer-readable medium of clause 83 or 84, wherein the second part of the SL-MGP occupies slots designated for sidelink communications or for communications having a lower priority than sidelink communications.

[0256] Clause 86. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a network entity, cause the network entity to receive first information from a user equipment (UE) indicating a sidelink positioning reference signal (SL-PRS) processing capability of the UE, determine a sidelink measurement gap (SL-MGP) for positioning based at least in part on the first information, and send second information to the UE indicating the SL-MGP.

[0257] Clause 87. The non-transitory computer-readable medium of clause 86, wherein the first information includes at least one of an indication that the UE is capable or incapable of processing SL-PRS, an indication of a maximum number of SL-PRS signals that the UE is capable of processing simultaneously, an indication of a maximum number of SL-PRS signals that the UE is capable of processing per unit time, or an indication that the UE is capable or incapable of processing SL-PRS signals and non-SL-PRS signals simultaneously.

[0258] Clause 88. A non-transitory computer-readable medium as described in clause 86 or 87, comprising computer-executable instructions that, when executed by a network entity, cause the network entity to determine a SL-MGP, and computer-executable instructions that, when executed by the network entity, cause the network entity to determine a duration for the SL-MGP.

[0259] Clause 89. A non-transitory computer readable medium as described in clause 88, comprising computer executable instructions that, when executed by a network entity, cause the network entity to determine a duration for the SL-MGP, the computer executable instructions, when executed by the network entity, cause the network entity to set the duration for the SL-MGP to be the sum of one or more of: a first duration for retuning a transceiver of the UE to a bandwidth occupied by a first resource pool for positioning including at least one SL-PRS, a second duration for the UE to at least one of transmitting or receiving an SL-PRS signal transmission, or a third duration for the UE to process an SL-PRS signal transmission.

[0260] Clause 90. A non-transitory computer-readable medium as described in any one of clauses 86 to 89, comprising computer-executable instructions that, when executed by a network entity, cause the network entity to determine an SL-MGP, and that, when executed by the network entity, cause the network entity to determine an SL-MGP based on information received from a plurality of UEs.

[0261] Clause 91. A non-transitory computer-readable medium according to any one of clauses 86 to 90, comprising computer-executable instructions which, when executed by a network entity, cause the network entity to send second information to the UE indicating the SL-MGP, and which, when executed by the network entity, cause the network entity to send the second information as part of configuration information or assistance data sent from a base station or a location server to the UE.

[0262] Clause 92. The non-transitory computer-readable medium of any one of clauses 86 to 91, wherein the network entity includes a base station or a location server.

[0263] Clause 93. An apparatus comprising a memory, a transceiver, and a processor communicatively coupled to the memory and the transceiver, wherein the memory, the transceiver, and the processor are configured to perform a method according to any one of clauses 1 to 23.

[0264] Clause 94. An apparatus comprising means for carrying out the method according to any one of clauses 1 to 23.

[0265] Clause 95. A non-transitory computer readable medium having stored thereon computer executable instructions, the computer executable including at least one instruction for causing a computer or processor to perform a method according to any one of clauses 1 to 23.

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

[0267] Moreover, those skilled in the art will appreciate that the various exemplary logic blocks, modules, circuits, and algorithm steps described in connection with the aspects disclosed herein may be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability of hardware and software, the various exemplary components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the particular application and design constraints imposed on the overall system. Those skilled in the art may realize the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

[0268] The various example logic blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented or performed using a general purpose processor, a digital signal processor (DSP), an ASIC, a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0269] The methods, sequences, and / or algorithms described in connection with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The software module may reside in a random access memory (RAM), a flash memory, a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. Alternatively, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal (e.g., UE). Alternatively, the processor and the storage medium may reside as discrete components in a user terminal.

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

[0271] Although the above disclosure illustrates exemplary aspects of the disclosure, it should be noted that various changes and modifications may be made herein without departing from the scope of the disclosure as defined by the appended claims. The functions, steps, and / or actions of the method claims in accordance with the aspects of the disclosure described herein need not be performed in any particular order. Further, although elements of the disclosure may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated.

Claims

1. 1. A method of wireless positioning implemented by a user equipment (UE), comprising: determining a sidelink measurement gap (SL-MGP) for positioning, determining the SL-MGP based on first information indicative of a sidelink positioning reference signal (SL-PRS) processing capability of the UE; The first information is an indication of the maximum number of SL-PRS signals that the UE can process simultaneously; an indication of the maximum number of SL-PRS signals that the UE can process per unit time, or An indication that the UE can or cannot process SL-PRS and non-SL-PRS signals simultaneously. determining the time period, including at least one of: performing sidelink positioning during said SL-MGP using at least one SL-PRS; A method comprising:

2. The method of claim 1 , wherein determining the SL-MGP comprises receiving the SL-MGP from a base station or a location server.

3. 2. The method of claim 1, wherein determining the SL-MGP comprises sending the first information to a base station or a location server, and receiving the SL-MGP from the base station or the location server.

4. determining the SL-MGP includes determining a duration for the SL-MGP; determining the duration for the SL-MGP; a first duration for retuning a transceiver of the UE to a bandwidth occupied by a first resource pool for positioning including the at least one SL-PRS; a second duration for SL-PRS signal transmission, or a third duration for processing the SL-PRS signal transmission; 2. The method of claim 1, comprising setting the duration for the SL-MGP to be the sum of one or more of:

5. 2. The method of claim 1, wherein determining the SL-MGP comprises coordinating with at least one other UE involved in sidelink communication to cluster SL-PRS transmissions and define an SL-MGP that includes the clustered SL-PRS transmissions.

6. performing sidelink positioning during the SL-MGP using at least one SL-PRS; retuning a transceiver of the UE from a first bandwidth occupied by a resource pool for data communication to a second bandwidth occupied by a resource pool for positioning; performing sidelink positioning within the second bandwidth; and and retuning the transceiver of the UE back to the first bandwidth.

7. The method of claim 6 , wherein the SL-MGP occupies a portion of a time domain included in the resource pool for positioning.

8. 7. The method of claim 6, wherein a first portion of the SL-MGP occupies a portion of a time domain within the resource pool for positioning, and a second portion of the SL-MGP occupies a portion of the time domain that is not within the resource pool for positioning.

9. The second part of the SL-MGP is is contiguous in time with the first part of the SL-MGP, or is not contiguous in time with the first portion of the SL-MGP; 9. The method of claim 8, wherein the second part of the SL-MGP occupies slots designated for sidelink communications or for communications having a lower priority than sidelink communications.

10. 1. A method of wireless positioning implemented by a network entity, comprising: receiving, from a user equipment (UE), first information indicating a sidelink positioning reference signal (SL-PRS) processing capability of the UE, the first information comprising: an indication of the maximum number of SL-PRS signals that the UE can process simultaneously; an indication of the maximum number of SL-PRS signals that the UE can process per unit time, or An indication that the UE can or cannot process SL-PRS and non-SL-PRS signals simultaneously. receiving the signal, the signal including at least one of: determining a sidelink measurement gap (SL-MGP) for positioning based at least in part on the first information; and sending second information indicating the SL-MGP to the UE; A method comprising:

11. determining the SL-MGP includes determining a duration for the SL-MGP; determining the duration for the SL-MGP; a first duration for retuning a transceiver of the UE to a bandwidth occupied by a first resource pool for positioning including at least one SL-PRS; a second duration for the UE to at least one of transmit or receive SL-PRS signaling; or a third duration for the UE to process the SL-PRS signal transmission; 11. The method of claim 10, comprising setting the duration for the SL-MGP to be the sum of one or more of:

12. The method of claim 10, wherein determining the SL-MGP comprises determining the SL-MGP based on information received from a plurality of UEs.

13. 11. The method of claim 10, wherein sending the second information indicating the SL-MGP to the UE comprises sending the second information as part of configuration information or assistance data sent from a base station or a location server to the UE.

14. A user equipment (UE), Memory and at least one transceiver; at least one processor communicatively coupled to the memory and the at least one transceiver, wherein the at least one processor: determining a sidelink measurement gap (SL-MGP) for positioning; performing sidelink positioning during said SL-MGP using at least one sidelink positioning reference signal (SL-PRS); and To determine the SL-MGP, the at least one processor is configured to determine the SL-MGP based on first information indicating an SL-PRS processing capability of the UE; The first information is an indication of the maximum number of SL-PRS signals that the UE can process simultaneously; an indication of the maximum number of SL-PRS signals that the UE can process per unit time, or An indication that the UE can or cannot process SL-PRS and non-SL-PRS signals simultaneously. The UE includes at least one of:

15. A network entity comprising: Memory and at least one transceiver; at least one processor communicatively coupled to the memory and the at least one transceiver, wherein the at least one processor: receiving first information from a user equipment (UE) via the at least one transceiver, the first information indicating a sidelink positioning reference signal (SL-PRS) processing capability of the UE; an indication of the maximum number of SL-PRS signals that the UE can process simultaneously; an indication of the maximum number of SL-PRS signals that the UE can process per unit time, or An indication that the UE can or cannot process SL-PRS and non-SL-PRS signals simultaneously. receiving the signal, the signal including at least one of: determining a sidelink measurement gap (SL-MGP) for positioning based at least in part on the first information; and sending second information indicating the SL-MGP to the UE via the at least one transceiver; A network entity configured to:

Images