Sidelink control information (SCI) signaling for bandwidth aggregation of sidelink positioning reference signals (SL-PRS)

Abstract

In an aspect, a sidelink device may receive sidelink position resource signal (SL-PRS) scheduling information for aggregating SL-PRS resources of a plurality of SL-PRS resource pools, wherein the SL-PRS scheduling information is only indicated by a subset of SL-PRS resource pools of the plurality of SL-PRS resource pools. The sidelink device may obtain one or more aggregated measurements of the SL-PRS resources of the plurality of SL-PRS resource pools based on the SL-PRS scheduling information indicated by the subset of SL-PRS resource pools.

Description

SIDELINK CONTROL INFORMATION (SCI) SIGNALING FOR BANDWIDTH AGGREGATION OF SIDELINK POSITIONING REFERENCESIGNALS (SL-PRS)BACKGROUND OF THE DISCLOSURE1. Field of the Disclosure

[0001] Aspects of the disclosure relate generally to wireless communications.2. Description of the Related Art

[0002] Wireless communication systems have developed through various generations, including a first-generation analog wireless phone service (1G), a second-generation (2G) digital wireless phone service (including interim 2.5G and 2.75G networks), a third-generation (3G) high speed data, Internet-capable wireless service and a fourth-generation (4G) service (e.g., Long Term Evolution (LTE) or WiMax). There are presently many different types of wireless communication systems in use, including cellular 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), the Global System for Mobile communications (GSM), etc.

[0003] A fifth generation (5G) wireless standard, referred to as New Radio (NR), enables higher data transfer speeds, greater numbers of connections, and better coverage, among other improvements. The 5G standard, according to the Next Generation Mobile Networks Alliance, is designed to provide higher data rates as compared to previous standards, 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.

[0004] Leveraging the increased data rates and decreased latency of 5G, among other things, vehicle-to-everything (V2X) communication technologies are being implemented to support autonomous driving applications, such as wireless communications between vehicles, between vehicles and the roadside infrastructure, between vehicles and pedestrians, etc.SUMMARY

[0005] The following presents a simplified summary relating to one or more aspects disclosed herein. Thus, the following summary should not be considered an extensive overview relating to all contemplated aspects, nor should the following summary be considered to identify key or critical elements relating to all contemplated aspects or to delineate the scope associated with any particular aspect. Accordingly, the following summary has the sole purpose to present certain concepts relating to one or more aspects relating to the mechanisms disclosed herein in a simplified form to precede the detailed description presented below.

[0006] In an aspect, a method of wireless communication performed by a sidelink device includes receiving sidelink position resource signal (SL-PRS) scheduling information for aggregating SL-PRS resources of a plurality of SL-PRS resource pools, wherein the SL- PRS scheduling information is only indicated by a subset of SL-PRS resource pools of the plurality of SL-PRS resource pools; and obtaining one or more aggregated measurements of the SL-PRS resources of the plurality of SL-PRS resource pools based on the SL-PRS scheduling information indicated by the subset of SL-PRS resource pools.

[0007] In an aspect, a sidelink device includes one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors, either alone or in combination, configured to: receive, via the one or more transceivers, sidelink position resource signal (SL-PRS) scheduling information for aggregating SL-PRS resources of a plurality of SL- PRS resource pools, wherein the SL-PRS scheduling information is only indicated by a subset of SL-PRS resource pools of the plurality of SL-PRS resource pools; and obtain one or more aggregated measurements of the SL-PRS resources of the plurality of SL- PRS resource pools based on the SL-PRS scheduling information indicated by the subset of SL-PRS resource pools.

[0008] In an aspect, a sidelink device includes means for receiving sidelink position resource signal (SL-PRS) scheduling information for aggregating SL-PRS resources of a plurality of SL-PRS resource pools, wherein the SL-PRS scheduling information is only indicated by a subset of SL-PRS resource pools of the plurality of SL-PRS resource pools; and means for obtaining one or more aggregated measurements of the SL-PRS resources ofthe plurality of SL-PRS resource pools based on the SL-PRS scheduling information indicated by the subset of SL-PRS resource pools.

[0009] In an aspect, a non-transitory computer-readable medium stores computer-executable instructions that, when executed by a sidelink device, cause the sidelink device to: receive sidelink position resource signal (SL-PRS) scheduling information for aggregating SL- PRS resources of a plurality of SL-PRS resource pools, wherein the SL-PRS scheduling information is only indicated by a subset of SL-PRS resource pools of the plurality of SL- PRS resource pools; and obtain one or more aggregated measurements of the SL-PRS resources of the plurality of SL-PRS resource pools based on the SL-PRS scheduling information indicated by the subset of SL-PRS resource pools.

[0010] Other obj ects and advantages associated with the aspects disclosed herein will be apparent to those skilled in the art based on the accompanying drawings and detailed description.BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The accompanying drawings are presented to aid in the description of various aspects of the disclosure and are provided solely for illustration of the aspects and not limitation thereof.

[0012] FIG. 1 illustrates an example wireless communications system, according to aspects of the disclosure.

[0013] FIGS. 2 A, 2B, and 2C illustrate example wireless network structures, according to aspects of the disclosure.

[0014] FIGS. 3A, 3B, and 3C are simplified block diagrams of several sample aspects of components that may be employed in a user equipment (UE), a base station, and a network entity, respectively, and configured to support communications as taught herein.

[0015] FIG. 4A is a diagram of an example slot structure without feedback resources, according to aspects of the disclosure.

[0016] FIG. 4B is a diagram of an example slot structure with feedback resources, according to aspects of the disclosure.

[0017] FIGS. 5A and 5B are diagrams of example sidelink slot structures with and without feedback resources, according to aspects of the disclosure.

[0018] FIGS. 6A to 6D are diagrams illustrating examples of resource pools for positioning, according to aspects of the disclosure.

[0019] FIG. 7 shows an example set of resource reservation parameters, according to aspects of the disclosure.

[0020] FIG. 8 shows an example resource reservation implementation in the time and frequency domains, according to aspects of the disclosure.

[0021] FIG. 9 through FIG. 14 depict example scenarios for providing sidelink positioning reference signal (SL-PRS) scheduling information for bandwidth aggregation, according to aspects of the disclosure.

[0022] FIG. 15 illustrates an example method wireless communication performed by a sidelink device, according to aspects of the disclosure.DETAILED DESCRIPTION

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

[0024] Various aspects relate generally to sidelink control information (SCI) signaling for bandwidth aggregation of sidelink positioning reference signals (SL-PRS) Some aspects more specifically relate to communicating sidelink position resource signal (SL-PRS) scheduling information for aggregating SL-PRS resources of a plurality of SL-PRS resource pools. In an aspect, the SL-PRS scheduling information is only indicated by a subset of SL-PRS resource pools of the plurality of SL-PRS resource pools. In some examples, the scheduling information is only included in a single SL-PRS resource pool. In some examples, the scheduling information is indicated in first stage sidelink control information (SCI-1), second stage sidelink control information (SCI-2), or a combination thereof in the subset of SL-PRS resource pools. In some examples, the scheduling information is indicated through direct, explicit, and / or implicit mapping of physical sidelink control channel (PSCCH) indices with corresponding SL-PRS resource identifiers.

[0025] Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, since the the SL-PRS scheduling information is only indicated by a subset of SL-PRS resourcepools of the plurality of SL-PRS resource pools, the described techniques can be used to indicate the SL-PRS resources that are to be aggregated with fewer communication resources than would otherwise be required using conventional techniques.

[0026] 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” is not necessarily to 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.

[0027] Those of skill 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 description below 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, in part on the desired design, in part on the corresponding technology, etc.

[0028] 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 recognized that various actions described herein can be performed by specific circuits (e.g., application specific integrated circuits (ASICs)), by program instructions being executed by one or more processors, or by a combination of both. Additionally, the sequence(s) of actions described herein can be considered to be embodied entirely within any form of non- transitory computer-readable storage medium having stored therein a corresponding set of computer instructions that, upon execution, would cause or instruct an associated processor of a device to perform the functionality described herein. Thus, the various aspects of the disclosure may be embodied in a number of different forms, all of which have been 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 aspects may be described herein as, for example, “logic configured to” perform the described action.

[0029] As used herein, the terms “user equipment” (UE), “vehicle UE” (V-UE), “pedestrian UE” (P-UE), and “base station” are not intended to be specific or otherwise limited to any particular radio access technology (RAT), unless otherwise noted. In general, a UE may be any wireless communication device (e.g., vehicle on-board computer, vehiclenavigation device, mobile phone, router, tablet computer, laptop computer, asset locating device, wearable (e.g., smartwatch, glasses, augmented reality (AR) / virtual reality (VR) headset, etc.), vehicle (e.g., automobile, motorcycle, bicycle, etc.), Internet of Things (loT) device, etc.) used by a user to communicate over a wireless communications network. A UE may be mobile or may (e.g., at certain times) be stationary, and may communicate with a radio access network (RAN). As used herein, the term “UE” may be referred to interchangeably as a “mobile device,” an “access terminal” or “AT,” a “client device,” a “wireless device,” a “subscriber device,” a “subscriber terminal,” a “subscriber station,” a “user terminal” or UT, a “mobile terminal,” a “mobile station,” or variations thereof.

[0030] 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 cell phone, tablet computer, etc.) that is carried by the driver of the vehicle or a passenger in the vehicle. The term “V-UE” may refer to the 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 that is carried by a pedestrian (i.e., a user that is not driving or riding in a vehicle). Generally, UEs can communicate with a core network via a RAN, and through the core network the UEs can be connected with external networks such as the Internet and with other UEs. Of course, other mechanisms of connecting to the core network and / or the Internet are also possible for the UEs, such as over wired access networks, wireless local area network (WLAN) networks (e.g., based on Institute of Electrical and Electronics Engineers (IEEE) 802.11, etc.) and so on.

[0031] A base station may operate according to one of several RATs in communication with UEs depending on the network in which it is deployed, and may be alternatively referred to as an access point (AP), a network node, a NodeB, an evolved NodeB (eNB), a next generation eNB (ng-eNB), a New Radio (NR) Node B (also referred to as a gNB or gNodeB), etc. A base station may be used primarily to support wireless access by UEs including supporting data, voice and / or signaling connections for the supported UEs. In some systems a base station may provide purely edge node signaling functions while inother systems it may provide additional control and / or network management functions. A communication link through which UEs can send signals to a base station is called an uplink (UL) channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, etc.). A communication link through which the base station can send signals to UEs is called a downlink (DL) 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 an UL / reverse or DL / forward traffic channel.

[0032] The term “base station” may refer to a single physical transmission-reception point (TRP) or to multiple physical TRPs that may or may not be co-located. For example, where 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. Where the term “base station” refers to multiple co-located physical TRPs, the physical TRPs may be an array of antennas (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming) of the base station. Where the term “base station” refers to multiple non-co-located physical TRPs, the physical TRPs may be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transport medium) or a remote radio head (RRH) (a remote base station connected to a serving base station). Alternatively, the non-co-located physical TRPs may be the serving base station receiving the measurement report from the UE and a neighbor base station whose reference radio frequency (RF) signals the UE is measuring. Because a TRP is the point from which a base station transmits and receives wireless signals, as used herein, references to transmission from or reception at a base station are to be understood as referring to a particular TRP of the base station.

[0033] In some implementations that support positioning of UEs, a base station may not support wireless access by UEs (e.g., may not support data, voice, and / or signaling connections for UEs), but may instead transmit reference RF signals to UEs to be measured by the UEs and / or may receive and measure signals transmitted by the UEs. Such base stations may be referred to as positioning beacons (e.g., when transmitting RF signals to UEs) and / or as location measurement units (e.g., when receiving and measuring RF signals from UEs).

[0034] An “RF signal” comprises an electromagnetic wave of a given frequency that transports information through the space between a transmitter and a receiver. As used herein, atransmitter 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 transmitted RF signal on different paths between the transmitter and 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” where it is clear from the context that the term “signal” refers to a wireless signal or an RF signal.

[0035] FIG. 1 illustrates an example wireless communications system 100, according to aspects of the disclosure. The wireless communications system 100 (which may also be referred to as a wireless wide area network (WWAN)) may include various base stations 102 (labelled “BS”) and various UEs 104. The base stations 102 may include macro cell base stations (high power cellular base stations) and / or small cell base stations (low power cellular base stations). In an aspect, the macro cell base stations 102 may include eNBs and / or ng-eNBs where the wireless communications system 100 corresponds to an LTE network, or gNBs where the wireless communications system 100 corresponds to a NR network, or a combination of both, and the small cell base stations may include femtocells, picocells, microcells, etc.

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

[0037] In addition to other functions, the base stations 102 may perform functions that relate to one or more of transferring user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment trace, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 may communicate with each other directly or indirectly (e.g., through the EPC / 5GC) over backhaul links 134, which may be wired or wireless.

[0038] 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 a base station 102 in each geographic coverage area 110. A “cell” is a logical communication entity used for communication with a base station (e.g., over some frequency resource, referred to as a carrier frequency, component carrier, carrier, band, or the like), 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.) for distinguishing cells operating via the same or a different carrier frequency. In some cases, different cells may be configured according to different protocol types (e.g., machine-type communication (MTC), narrowband loT (NB-IoT), enhanced mobile broadband (eMBB), or others) that may provide access for different types of UEs. Because a cell is supported by a specific base station, the term “cell” may refer to either or both the logical communication entity and the base station that supports it, depending on the context. In some cases, the term “cell” may also refer to a geographic coverage area of a base station (e.g., a sector), insofar as a carrier frequency can be detected and used for communication within some portion of geographic coverage areas 110.

[0039] While neighboring macro cell base station 102 geographic coverage areas 110 may partially overlap (e.g., in a handover region), some of the geographic coverage areas 110 may be substantially overlapped by a larger geographic coverage area 110. For example, a small cell base station 102' (labelled “SC” for “small cell”) may have a geographic coverage area 110' that substantially overlaps with the geographic coverage area 110 ofone or more macro cell base stations 102. A network that includes both small cell and macro cell base stations may be known as a heterogeneous network. A heterogeneous network may also include home eNBs (HeNBs), which may provide service to a restricted group known as a closed subscriber group (CSG).

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

[0041] The wireless communications system 100 may further include a wireless local area network (WLAN) access point (AP) 150 in communication with WLAN stations (STAs) 152 via communication links 154 in an unlicensed frequency spectrum (e.g., 5 GHz). When communicating in an 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 prior to communicating in order to determine whether the channel is available.

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

[0043] The wireless communications system 100 may further include a mmW base station 180 that may operate in millimeter wave (mmW) frequencies and / or near mmW frequencies in communication with a UE 182. Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 millimeter and 10 millimeters. Radio waves in this band may be referred to asa millimeter wave. Near mmW may extend down to a frequency of 3 GHz with a wavelength of 100 millimeters. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, also referred to as centimeter wave. Communications using the mmW / near mmW radio frequency band have high path loss and a relatively short range. The mmW base station 180 and the UE 182 may utilize beamforming (transmit and / or receive) over a mmW communication link 184 to compensate for the extremely high path loss and short range. Further, it will be appreciated that in alternative configurations, one or more base stations 102 may also transmit using mmW or near mmW and beamforming. Accordingly, it will be appreciated that the foregoing illustrations are merely examples and should not be construed to limit the various aspects disclosed herein.

[0044] Transmit beamforming is a technique for focusing an RF signal in a specific direction. Traditionally, when a network node (e.g., a base station) broadcasts an RF signal, it broadcasts the signal in all directions (omni-directionally). With transmit beamforming, the network node determines where a given target device (e.g., a UE) is located (relative to the transmitting network node) and projects a stronger downlink RF signal in that specific direction, thereby providing a faster (in terms of data rate) and stronger RF signal for the receiving device(s). To change the directionality of the RF signal when transmitting, a network node can control the phase and relative amplitude of the RF signal at each of the one or more transmitters that are broadcasting the RF signal. For example, a network node may use an array of antennas (referred to as a “phased array” or an “antenna array”) that creates a beam of RF waves that can be “steered” to point in different directions, without actually moving the antennas. Specifically, the RF current from the transmitter is fed to the individual antennas with the correct phase relationship so that the radio waves from the separate antennas add together to increase the radiation in a desired direction, while cancelling to suppress radiation in undesired directions.

[0045] Transmit beams may be quasi-co-located, meaning that they appear to the receiver (e.g., a UE) as having the same parameters, regardless of whether or not the transmitting antennas of the network node themselves are physically co-located. In NR, there are four types of quasi -co-1 ocati on (QCL) relations. Specifically, a QCL relation of a given type means that certain parameters about 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 referenceRF signal to estimate the Doppler shift, Doppler spread, average delay, and delay spread of a second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL Type B, the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of a second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL Type C, the receiver can use the source reference RF signal to estimate the Doppler shift and average delay of a second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL Type D, the receiver can use the source reference RF signal to estimate the spatial receive parameter of a second reference RF signal transmitted on the same channel.

[0046] In receive beamforming, the 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., to increase the gain level of) the RF signals received from that direction. Thus, when a receiver is said to beamform in a certain direction, it means the beam gain in that direction is high relative to the beam gain along other directions, or the beam gain in that direction is the highest compared to the beam gain 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 the RF signals received from that direction.

[0047] Transmit and receive beams may be spatially related. A spatial relation means that parameters for a second beam (e.g., a transmit or receive beam) for a second reference signal can be derived from information about a first beam (e.g., a receive beam or a transmit beam) for a first reference signal. For example, a 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 can 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.

[0048] Note that a “downlink” beam may be either a transmit beam or a receive beam, depending on the entity forming it. For example, if a base station is forming the downlink beam to transmit a reference signal to a UE, the downlink beam is a transmit beam. If the UE is forming the downlink beam, however, it is a receive beam to receive the downlink reference signal. Similarly, an “uplink” beam may be either a transmit beam or a receivebeam, depending on the entity forming it. For example, if a base station is forming the uplink beam, it is an uplink receive beam, and if a UE is forming the uplink beam, it is an uplink transmit beam.

[0049] The electromagnetic spectrum is often subdivided, based on frequency / wavelength, into various classes, bands, channels, etc. 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 greater than 6 GHz, FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) which is identified by the INTERNATIONAL TELECOMMUNICATION UNION® as a “millimeter wave” band.

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

[0051] With the above aspects in mind, unless specifically stated otherwise, it should be understood that the term “sub-6 GHz” or the like if used herein may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, it should be understood that the term “millimeter wave” or the like if used herein may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band.

[0052] In a multi-carrier system, such as 5G, one of the carrier frequencies is referred to as the “primary carrier” or “anchor carrier” or “primary serving cell” or “PCell,” and theremaining carrier frequencies are referred to as “secondary carriers” or “secondary serving cells” or “SCells.” In carrier aggregation, the anchor carrier is the carrier operating on the primary frequency (e.g., FR1) utilized by a UE 104 / 182 and the cell in which the UE 104 / 182 either performs the initial radio resource control (RRC) connection establishment procedure or initiates the RRC connection re-establishment procedure. The primary carrier carries all common and UE-specific control channels, and may be a carrier in a licensed frequency (however, this is not always the case). A secondary carrier is a carrier operating on a second frequency (e.g., FR2) that may be configured once the RRC connection is established between the UE 104 and the anchor carrier and that may be used to provide additional radio resources. In some cases, the secondary carrier may be a carrier in an unlicensed frequency. The secondary carrier may contain only necessary signaling information and signals, for example, those that are UE-specific may not be present in the secondary carrier, since both primary uplink and downlink carriers are typically UE-specific. This means that different UEs 104 / 182 in a cell may have different downlink primary carriers. The same is true for the uplink primary carriers. The network is able to change the primary carrier of any UE 104 / 182 at any time. This is done, for example, to balance the load on different carriers. Because a “serving cell” (whether a PCell or an SCell) corresponds to a carrier frequency / component carrier over which some base station is communicating, the term “cell,” “serving cell,” “component carrier,” “carrier frequency,” and the like can be used interchangeably.

[0053] For example, still referring to FIG. 1, one of the frequencies utilized by the macro cell base stations 102 may be an anchor carrier (or “PCell”) and other frequencies utilized by the macro cell base stations 102 and / or the mmW base station 180 may be secondary carriers (“SCells”). The simultaneous transmission and / or reception of multiple carriers enables the UE 104 / 182 to significantly increase its data transmission and / or reception rates. For example, two 20 MHz aggregated carriers in a multi-carrier system would theoretically lead to a two-fold increase in data rate (i.e., 40 MHz), compared to that attained by a single 20 MHz carrier.

[0054] 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 an aspect, the S Vs 112 may be part of a satellite positioning system that aUE 104 can use as an independent source of location information. A satellitepositioning 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 a transmitter typically transmits a signal marked with a repeating pseudo-random noise (PN) code of a set number of chips. While typically located in SVs 112, transmitters may sometimes be located on ground-based control stations, base stations 102, and / or other UEs 104. A UE 104 may include one or more dedicated receivers specifically designed to receive signals 124 for deriving geo location information from the SVs 112.

[0055] In a satellite positioning system, the use of signals 124 can 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 an SBAS may include an augmentation system(s) that provides integrity information, differential corrections, etc., such as the Wide Area Augmentation System (WAAS), the European Geostationary Navigation Overlay Service (EGNOS), the Multifunctional Satellite Augmentation System (MSAS), the Global Positioning System (GPS) Aided Geo Augmented Navigation or GPS and Geo Augmented Navigation system (GAGAN), and / or the like. 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.

[0056] In an aspect, SVs 112 may additionally or alternatively be part of one or more nonterrestrial networks (NTNs). In an NTN, an SV 112 is connected to an earth station (also referred to as 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 5GC. This element would in turn provide access to other elements in the 5G network and ultimately to entities external to the 5G network, such as Internet web servers and other user devices. In that way, a UE 104 may receive communication signals (e.g., signals 124) from an SV 112 instead of, or in addition to, communication signals from a terrestrial base station 102.

[0057] Leveraging the increased data rates and decreased latency of NR, among other things, vehicle-to-everything (V2X) communication technologies are being implemented to support intelligent transportation systems (ITS) applications, such as wireless communications between vehicles (vehi cl e-to- vehicle (V2V)), between vehicles and theroadside 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 vehicle communication will enable safety, mobility, and environmental advancements that current technologies are unable to provide. Once fully implemented, the technology is expected to reduce unimpaired vehicle crashes by 80%.

[0058] Still referring to FIG. 1, the wireless communications system 100 may include multiple V-UEs 160 that may communicate with base stations 102 over communication links 120 using the Uu interface (i.e., the air interface between a UE and a base station). V-UEs 160 may also communicate directly with each other over a wireless sidelink 162, with a roadside unit (RSU) 164 (a roadside access point) over a wireless sidelink 166, or with sidelink-capable UEs 104 over a wireless sidelink 168 using the PC5 interface (i.e., the air interface between sidelink-capable UEs). A wireless sidelink (or just “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 needing to go through a base station. Sidelink communication may be unicast or multicast, and may be used for device- to-device (D2D) media-sharing, V2V communication, V2X communication (e.g., cellular V2X (cV2X) communication, enhanced V2X (eV2X) communication, 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 a base station 102. Other V-UEs 160 in such a group may be outside the geographic coverage area 110 of a base station 102 or be otherwise unable to receive transmissions from a base station 102. In some cases, groups 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 every other V- UE 160 in the group. In some cases, a base station 102 facilitates the scheduling of resources for sidelink communications. In other cases, sidelink communications are carried out between V-UEs 160 without the involvement of a base station 102.

[0059] In an aspect, the sidelinks 162, 166, 168 may operate over a wireless communication medium of interest, which may be shared with other wireless communications between other vehicles and / or infrastructure access points, as well as other RATs. A “medium” may be composed of one or more time, frequency, and / or space communication resources(e.g., encompassing one or more channels across one or more carriers) associated with wireless communication between one or more transmitter / receiver pairs.

[0060] In an aspect, the sidelinks 162, 166, 168 may be cV2X links. A first generation of cV2X has been 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 communications. In the U.S. and Europe, cV2X is expected to operate in the licensed ITS band in sub-6GHz. Other bands may be allocated in other countries. Thus, as a particular example, the medium of interest utilized by sidelinks 162, 166, 168 may correspond to at least a portion of the licensed ITS frequency band of sub-6GHz. However, the present disclosure is not limited to this frequency band or cellular technology.

[0061] In an aspect, the sidelinks 162, 166, 168 may be dedicated short-range communications (DSRC) links. DSRC is a one-way or two-way short-range to medium-range wireless communication protocol that uses the wireless access for vehicular environments (WAVE) protocol, also known as IEEE 802. l ip, for V2V, V2I, and V2P communications. IEEE 802.1 Ip is an approved amendment to the IEEE 802.11 standard and operates in the licensed ITS band of 5.9 GHz (5.85-5.925 GHz) in the U.S. In Europe, IEEE 802.1 Ip operates in the ITS G5A band (5.875 - 5.905 MHz). Other bands may be allocated in other countries. The V2V communications briefly described above occur on the Safety Channel, which in the U.S. is typically a 10 MHz channel that is dedicated to the purpose of safety. The remainder of the DSRC band (the total bandwidth is 75 MHz) is intended for other services of interest to drivers, such as road rules, tolling, parking automation, etc. Thus, as a particular example, the mediums of interest utilized by sidelinks 162, 166, 168 may correspond to at least a portion of the licensed ITS frequency band of 5.9 GHz.

[0062] 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 certain communication systems (e.g., by a government entity such as the Federal Communications Commission (FCC) in the United States), these systems, in particular those employing small cell access points, have recently extended operation into unlicensed frequency bands such as the Unlicensed National Information Infrastructure (U-NII) band used by wireless local area network (WLAN) technologies, most notably IEEE 802.1 lx WLAN technologies generally referred to as“Wi-Fi.” Example systems of this type include different variants of CDMA systems, TDMA systems, FDMA systems, orthogonal FDMA (OFDMA) systems, single-carrier FDMA (SC-FDMA) systems, and so on.

[0063] Communications between the V-UEs 160 are referred to as V2V communications, communications between the V-UEs 160 and the one or more RSUs 164 are referred to as V2I communications, and communications between the V-UEs 160 and one or more UEs 104 (where the UEs 104 are P-UEs) are referred to as V2P communications. The V2V communications 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 a V-UE 160 from the one or more RSUs 164 may include, for example, road rules, parking automation information, etc. The V2P communications between a V-UE 160 and a UE 104 may include information about, for example, the position, speed, acceleration, and heading of the V-UE 160 and the position, speed (e.g., where the UE 104 is carried by a user on a bicycle), and heading of the UE 104.

[0064] Note that although FIG. 1 only illustrates two of the UEs as V-UEs (V-UEs 160), any of the illustrated UEs (e.g., UEs 104, 152, 182, 190) may be V-UEs. In addition, while only the V-UEs 160 and a single UE 104 have been illustrated as being connected over a sidelink, any of the UEs illustrated in FIG. 1, whether V-UEs, P-UEs, etc., may be capable of sidelink communication. Further, although only UE 182 was described as being capable of beam forming, any of the illustrated UEs, including V-UEs 160, may be capable of beam forming. Where V-UEs 160 are capable of beam forming, they may beam form towards each other (i.e., towards other V-UEs 160), towards RSUs 164, towards other UEs (e.g., UEs 104, 152, 182, 190), etc. Thus, in some cases, V-UEs 160 may utilize beamforming over sidelinks 162, 166, and 168.

[0065] The wireless communications system 100 may further include one or more UEs, such as UE 190, that connects indirectly 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, UE 190 has a D2D P2P link 192 with one of the UEs 104 connected to one of the base stations 102 (e.g., through which UE 190 may indirectly obtain cellular connectivity) and a D2D P2P link 194 with WLAN STA 152 connected to the WLAN AP 150 (through which UE 190 may indirectly obtain WLAN-based Internet connectivity). In an example, the D2D P2P links 192 and 194 may be supported with any well-known D2D RAT, such as LTE Direct(LTE-D), WI-FI DIRECT®, BLUETOOTH®, and so on. As another example, the D2D P2P links 192 and 194 may be sidelinks, as described above with reference to sidelinks 162, 166, and 168.

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

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

[0068] FIG. 2B illustrates another example wireless network structure 240. A 5GC 260 (which may correspond to 5GC 210 in FIG. 2A) can be viewed functionally as control plane functions, provided by an access and mobility management function (AMF) 264, and userplane functions, provided by a user plane function (UPF) 262, which operate cooperatively to form the core network (i.e., 5GC 260). The functions of the AMF 264 include registration management, connection 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 the 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, and receives the intermediate key that was established as a result of the UE 204 authentication process. In the case of authentication based on a UMTS (universal mobile telecommunications system) subscriber identity module (USIM), the AMF 264 retrieves the security material from the AUSF. The functions of the AMF 264 also include security context management (SCM). The SCM receives a key from the SEAF that it uses to derive access-network specific keys. The functionality of the AMF 264 also includes location services management for regulatory services, transport for location services messages between the UE 204 and a location management function (LMF) 270 (which acts as a location server 230), transport for location services messages between the NG-RAN 220 and the LMF 270, evolved packet system (EPS) bearer identifier allocation for interworking with the EPS, and UE 204 mobility event notification. In addition, the AMF 264 also supports functionalities for non-3GPP® (Third Generation Partnership Project) access networks.

[0069] 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 of interconnect to a data network (not shown), providing packet routing and forwarding, 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) handling for the user plane (e.g., uplink / downlink rate enforcement, reflective QoS marking in the downlink), uplink traffic verification (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 andforwarding of one or more “end markers” to the source RAN node. The UPF 262 may also support transfer of location services messages over a user plane between the UE 204 and a location server, such as an SLP 272.

[0070] 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 at the UPF 262 to route traffic to the proper destination, control of part of policy enforcement and QoS, and downlink data notification. The interface over which the SMF 266 communicates with the AMF 264 is referred to as the Ni l interface.

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

[0072] 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. As such, 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 server 274 can be implemented as a plurality of separate servers (e.g., physically separate servers, different software modules on a single server, different software modules spread across multiple physical servers, etc.), or alternately may each correspond to a single server.

[0073] User plane interface 263 and control plane interface 265 connect the 5GC 260, and specifically the UPF 262 and AMF 264, respectively, to one or more gNBs 222 and / or ng-eNBs 224 in the NG-RAN 220. The interface between gNB(s) 222 and / or ng-eNB(s) 224 and the AMF 264 is referred to as the “N2” interface, and the interface between 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 backhaul connections 223, referred to as the “Xn-C” interface. One or more of gNBs 222 and / or ng-eNBs 224 may communicate with one or more UEs 204 over a wireless interface, referred to as the “Uu” interface.

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

[0075] Deployment of communication systems, such as 5G NR systems, may be arranged in multiple manners with various components or constituent parts. In a 5G NR system, or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, or a network equipment, such as a base station, or one or more units (or one or more components) performing base station functionality,may be implemented in an aggregated or disaggregated architecture. For example, a base station (such as a Node B (NB), evolved NB (eNB), NR base station, 5G NB, AP, TRP, cell, etc.) may be implemented as an aggregated base station (also known as a standalone base station or a monolithic base station) or a disaggregated base station.

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

[0077] Base station-type operation or network design may consider aggregation characteristics of base station functionality. For example, disaggregated base stations may be utilized in an integrated access backhaul (IAB) network, an open radio access network (0-RAN (such as the network configuration sponsored by the 0-RAN ALLIANCE®)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C- RAN)). Disaggregation may include distributing functionality across two or more units at various physical locations, as well as distributing functionality for at least one unit virtually, which can enable flexibility in network design. The various units of the disaggregated base station, or disaggregated RAN architecture, can be configured for wired or wireless communication with at least one other unit.

[0078] FIG. 2C illustrates an example disaggregated base station architecture 250, according to aspects of the disclosure. The disaggregated base station architecture 250 may include one or more central units (CUs) 280 (e.g., gNB-CU 226) that can communicate directly with a core network 267 (e.g., 5GC 210, 5GC 260) via a backhaul link, or indirectly with the core network 267 through one or more disaggregated base station units (such as a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) 259 via an E2 link, or a Non-Real Time (Non-RT) RIC 257 associated with a Service Management and Orchestration (SMO) Framework 255, or both). A CU 280 may communicate with oneor more DUs 285 (e.g., gNB-DUs 228) via respective midhaul links, such as an Fl interface. The DUs 285 may communicate with one or more radio units (RUs) 287 (e.g., gNB-RUs 229) via respective fronthaul links. The RUs 287 may communicate with respective UEs 204 via one or more radio frequency (RF) access links. In some implementations, the UE 204 may be simultaneously served by multiple RUs 287.

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

[0080] In some aspects, the CU 280 may host one or more higher layer control functions. Such control functions can include RRC, PDCP, service data adaptation protocol (SDAP), or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 280. The CU 280 may be configured to handle user plane functionality (i.e., Central Unit - User Plane (CU- UP)), control plane functionality (i.e., Central Unit - Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 280 can be logically split into one or more CU-UP units and one or more CU-CP units. The CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as the El interface when implemented in an 0-RAN configuration. The CU 280 can be implemented to communicate with the DU 285, as necessary, for network control and signaling.

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

[0082] Lower-layer functionality can be implemented by one or more RUs 287. In some deployments, an RU 287, controlled by a DU 285, may correspond to a logical node that hosts RF processing functions, or low-PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, or the like), or both, based at least in part on the functional split, such as a lower layer functional split. In such an architecture, the RU(s) 287 can be implemented to handle over the air (OTA) communication with one or more UEs 204. In some implementations, real-time and non-real-time aspects of control and user plane communication with the RU(s) 287 can be controlled by the corresponding DU 285. In some scenarios, this configuration can enable the DU(s) 285 and the CU 280 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0083] The SMO Framework 255 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 255 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements which may be managed via an operations and maintenance interface (such as an 01 interface). For virtualized network elements, the SMO Framework 255 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 269) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an 02 interface). Such virtualized network elements can include, but are not limited to, CUs 280, DUs 285, RUs 287 and Near-RT RICs 259. In some implementations, the SMO Framework 255 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 261, via an 01 interface. Additionally, in some implementations, the SMO Framework 255can communicate directly with one or more RUs 287 via an 01 interface. The SMO Framework 255 also may include a Non-RT RIC 257 configured to support functionality of the SMO Framework 255.

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

[0085] In some implementations, to generate AI / ML models to be deployed in the Near-RT RIC 259, the Non-RT RIC 257 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 259 and may be received at the SMO Framework 255 or the Non-RT RIC 257 from non-network data sources or from network functions. In some examples, the Non-RT RIC 257 or the Near-RT RIC 259 may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 257 may monitor long-term trends and patterns for performance and employ AI / ML models to perform corrective actions through the SMO Framework 255 (such as reconfiguration via 01) or via creation of RAN management policies (such as Al policies).

[0086] All base stations described herein), and a network entity 306 (which may correspond to or embody any of the network functions described herein, including the location server 230 and the LMF 270, or alternatively may be independent from 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 appreciated that these components may be implemented in different types of apparatuses in different implementations (e.g., in an ASIC, in a system-on-chip (SoC), etc.). The illustrated components may also be incorporated into other apparatuses in a communication system. For example, other apparatuses in a system may include components similar to those described to providesimilar functionality. Also, a given apparatus may contain one or more of the components. For example, an apparatus may include multiple transceiver components that enable the apparatus to operate on multiple carriers and / or communicate via different technologies.

[0087] The UE 302 and the 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 fortuning, means for refraining from transmitting, etc.) via one or more wireless communication networks (not shown), such as an NR network, an LTE network, a GSM network, and / or the like. 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., via at least one designated RAT (e.g., NR, LTE, GSM, etc.) over a wireless communication 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 for transmitting and encoding signals 318 and 358 (e.g., messages, indications, information, and so on), respectively, and, conversely, for receiving and decoding signals 318 and 358 (e.g., messages, indications, information, pilots, and so on), respectively, in accordance with the designated RAT. Specifically, the WWAN transceivers 310 and 350 include one or more transmitters 314 and 354, respectively, for transmitting and encoding signals 318 and 358, respectively, and one or more receivers 312 and 352, respectively, for receiving and decoding signals 318 and 358, respectively.

[0088] The LE 302 and the base station 304 each also include, at least in some cases, 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 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 LEs, access points, base stations, etc., via at least one designated RAT (e.g., Wi-Fi, LTE Direct, BLLETOOTH®, ZIGBEE®, Z-WAVE®, PC5, dedicated short-range communications (DSRC), wireless access for vehicular environments (WAVE), near-field communication (NFC), ultra- wideband (UWB), etc.) over a wireless communication medium of interest. The short- range wireless transceivers 320 and 360 may be variously configured for transmitting andencoding signals 328 and 368 (e.g., messages, indications, information, and so on), respectively, and, conversely, for receiving and decoding signals 328 and 368 (e.g., messages, indications, information, pilots, and so on), respectively, in accordance with the designated RAT. Specifically, the short-range wireless transceivers 320 and 360 include one or more transmitters 324 and 364, respectively, for transmitting and encoding signals 328 and 368, respectively, and one or more receivers 322 and 362, respectively, for receiving and decoding signals 328 and 368, respectively. As specific examples, the short-range wireless transceivers 320 and 360 may be Wi-Fi transceivers, BLUETOOTH® transceivers, ZIGBEE® and / or Z-WAVE® transceivers, NFC transceivers, UWB transceivers, or vehicle-to-vehicle (V2V) and / or vehicle-to- everything (V2X) transceivers.

[0089] The UE 302 and the base station 304 also include, at least in some cases, satellite signal interfaces 330 and 370, which each include one or more satellite signal receivers 332 and 372, respectively, and may optionally include one or more satellite signal transmitters 334 and 374, respectively. In some cases, the base station 304 may be a terrestrial base station that may communicate with space vehicles (e.g., space vehicles 112) via the satellite signal interface 370. In other cases, the base station 304 may be a space vehicle (or other non-terrestrial entity) that uses the satellite signal interface 370 to communicate with terrestrial networks and / or other space vehicles.

[0090] The satellite signal receivers 332 and 372 may be connected to one or more antennas 336 and 376, respectively, and may provide means for receiving and / or measuring satellite positioning / communication signals 338 and 378, respectively. Where the satellite signal receiver(s) 332 and 372 are satellite positioning system receivers, the satellite positioning / communication signals 338 and 378 may be global positioning system (GPS) signals, global navigation satellite system (GLONASS) signals, Galileo signals, Beidou signals, Indian Regional Navigation Satellite System (NAVIC), Quasi-Zenith Satellite System (QZSS) signals, etc. Where the satellite signal receiver(s) 332 and 372 are nonterrestrial network (NTN) receivers, the satellite positioning / communication signals 338 and 378 may be communication signals (e.g., carrying control and / or user data) originating from a 5G network. The satellite signal receiver(s) 332 and 372 may comprise any suitable hardware and / or software for receiving and processing satellite positioning / communication signals 338 and 378, respectively. The satellite signalreceiver(s) 332 and 372 may request information and operations as appropriate from the other systems, and, at least in some cases, perform calculations to determine locations of the UE 302 and the base station 304, respectively, using measurements obtained by any suitable satellite positioning system algorithm.

[0091] The optional satellite signal transmitter(s) 334 and 374, when present, may be connected to the one or more antennas 336 and 376, respectively, and may provide means for transmitting satellite positioning / communication signals 338 and 378, respectively. Where the satellite signal transmitter(s) 374 are satellite positioning system transmitters, the satellite positioning / communication signals 378 may be GPS signals, GLONASS® signals, Galileo signals, Beidou signals, NAVIC, QZSS signals, etc. Where the satellite signal transmitter(s) 334 and 374 are NTN transmitters, the satellite positioning / communication signals 338 and 378 may be communication signals (e.g., carrying control and / or user data) originating from a 5G network. The satellite signal transmitter(s) 334 and 374 may comprise any suitable hardware and / or software for transmitting satellite positioning / communication signals 338 and 378, respectively. The satellite signal transmitter(s) 334 and 374 may request information and operations as appropriate from the other systems.

[0092] The base station 304 and the network entity 306 each include one or more network transceivers 380 and 390, respectively, providing means for communicating (e.g., means for transmitting, 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 the 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 the one or more network transceivers 390 to communicate with one or more base station 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.

[0093] A transceiver may be configured to communicate over a wired or 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 circuitry and receiver circuitry in a single device) in some implementations, may compriseseparate transmitter circuitry and separate receiver circuitry in some implementations, or may be embodied in other ways in other implementations. The transmitter circuitry 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. Wireless transmitter circuitry (e.g., transmitters 314, 324, 354, 364) may include or be coupled to a plurality of antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, that permits the respective apparatus (e.g., UE 302, base station 304) to perform transmit “beamforming,” as described herein. Similarly, wireless receiver circuitry (e.g., receivers 312, 322, 352, 362) may include or be coupled to a plurality of antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, that permits the respective apparatus (e.g., UE 302, base station 304) to perform receive beamforming, as described herein. In an aspect, the transmitter circuitry and receiver circuitry may share the same plurality of antennas (e.g., antennas 316, 326, 356, 366), such that the respective apparatus can only receive or transmit at a given time, not both at the same time. A wireless transceiver (e.g., 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.

[0094] As used herein, the 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 generally be characterized as “a transceiver,” “at least one transceiver,” or “one or more transceivers.” As such, whether a particular transceiver is a wired or wireless transceiver may be inferred from the type of communication performed. For example, backhaul communication between network devices or servers will generally relate to signaling via a wired transceiver, whereas wireless communication between a UE (e.g., UE 302) and a base station (e.g., base station 304) will generally relate to signaling via a wireless transceiver.

[0095] The UE 302, the base station 304, and the network entity 306 also include other components that may be used in conjunction with the operations as disclosed herein. The UE 302, the base station 304, and the network entity 306 include one or more processors 342, 384, and 394, respectively, for providing functionality relating to, for example, wireless communication, and for providing other processing functionality. Theprocessors 342, 384, and 394 may therefore provide means for processing, such as means for determining, means for calculating, means for receiving, means for transmitting, means for indicating, etc. In an aspect, the processors 342, 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 circuitry, or various combinations thereof.

[0096] The UE 302, the base station 304, and the network entity 306 include memory circuitry implementing memories 340, 386, and 396 (e.g., each including a memory device), respectively, for maintaining information (e.g., information indicative of reserved resources, thresholds, parameters, and so on). The memories 340, 386, and 396 may therefore provide means for storing, means for retrieving, means for maintaining, etc. In some cases, the UE 302, the base station 304, and the network entity 306 may include positioning component 348, 388, and 398, respectively. The positioning component 348, 388, and 398 may be hardware circuits that are part of or coupled to the processors 342, 384, and 394, respectively, that, when executed, cause the UE 302, the base station 304, and the network entity 306 to perform the functionality described herein. In other aspects, the positioning component 348, 388, and 398 may be external to the processors 342, 384, and 394 (e.g., part of a modem processing system, integrated with another processing system, etc.). Alternatively, the positioning component 348, 388, and 398 may be memory modules stored in the memories 340, 386, and 396, respectively, that, when executed by the processors 342, 384, and 394 (or a modem processing system, another processing system, etc.), cause the UE 302, the base station 304, and the network entity 306 to perform the functionality described herein. FIG. 3A illustrates possible locations of the positioning component 348, which may be, for example, part of the one or more WWAN transceivers 310, the memory 340, the one or more processors 342, or any combination thereof, or may be a standalone component. FIG. 3B illustrates possible locations of the positioning component 388, which may be, for example, part of the one or more WWAN transceivers 350, the memory 386, the one or more processors 384, or any combination thereof, or may be a standalone component. FIG. 3C illustrates possible locations of the positioning component 398, which may be, for example, part of the one or more networktransceivers 390, the memory 396, the one or more processors 394, or any combination thereof, or may be a standalone component.

[0097] The UE 302 may include one or more sensors 344 coupled to the one or more processors 342 to provide means for sensing or detecting movement and / or orientation information that is independent of motion 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 interface 330. By way of example, the sensor(s) 344 may include an accelerometer (e.g., a micro-electrical mechanical systems (MEMS) device), a gyroscope, a geomagnetic sensor (e.g., a compass), an altimeter (e.g., a barometric pressure altimeter), and / or any other type of movement detection sensor. Moreover, the sensor(s) 344 may include a plurality of different types of devices and combine their outputs in order to provide motion information. For example, the sensor(s) 344 may use a combination of a multi-axis accelerometer and orientation sensors to provide the ability to compute positions in two-dimensional (2D) and / or three-dimensional (3D) coordinate systems.

[0098] In addition, the UE 302 includes a user interface 346 providing means for providing indications (e.g., audible and / or visual indications) to a user and / or for receiving user input (e.g., upon user actuation of a sensing device such a keypad, a touch screen, a microphone, and so on). Although not shown, the base station 304 and the network entity 306 may also include user interfaces.

[0099] Referring to the one or more processors 384 in more detail, in 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 functionality associated with broadcasting of system information (e.g., master information block (MIB), system information blocks (SIBs)), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-RAT mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionalityassociated with the transfer of upper layer PDUs, error correction through automatic repeat request (ARQ), concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization.

[0100] The transmitter 354 and the receiver 352 may implement Layer- 1 (LI) functionality associated with various signal processing functions. Layer- 1, which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding / decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. The transmitter 354 handles mapping to 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 an orthogonal frequency division multiplexing (OFDM) subcarrier, 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 produce a physical channel carrying a time domain OFDM symbol stream. The OFDM symbol stream is spatially precoded to produce 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 estimate 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 a respective spatial stream for transmission.

[0101] At the UE 302, the receiver 312 receives a signal through its respective antenna(s) 316. The receiver 312 recovers information modulated onto an RF carrier and provides the information to the one or more processors 342. The transmitter 314 and the receiver 312 implement Lay er- 1 functionality 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 comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 304. These soft decisions may be based on channel estimates computed by a channel estimator. The soft decisions are then decoded and de-interleaved to recover the data and control signals that were originally transmitted by the base station 304 on the physical channel. The data and control signals are then provided to the one or more processors 342, which implements Layer-3 (L3) and Layer-2 (L2) functionality.

[0102] In the downlink, the one or more processors 342 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets from the core network. The one or more processors 342 are also responsible for error detection.

[0103] Similar to the functionality described in connection with the downlink transmission by the base station 304, the one or more processors 342 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression / decompression, and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ), priority handling, and logical channel prioritization.

[0104] 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 the appropriate coding and modulation schemes, 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 a respective spatial stream for transmission.

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

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

[0107] For convenience, the UE 302, the base station 304, and / or the network entity 306 are shown in FIGS. 3 A, 3B, and 3C as including various components that may be configured according to the various examples described herein. It will be appreciated, however, that the illustrated components may have different functionality in different designs. In particular, various components in FIGS. 3A to 3C are optional in alternative configurations and the various aspects include configurations that may vary due to design choice, costs, use of the device, or other considerations. For example, in case of FIG. 3A, a particular implementation of UE 302 may omit the WWAN transceiver(s) 310 (e.g., a wearable device or tablet computer or personal computer (PC) or laptop may have Wi-Fi and / or BLUETOOTH® capability without cellular capability), or may omit the short- range wireless transceiver(s) 320 (e.g., cellular-only, etc.), or may omit the satellite signal interface 330, or may omit the sensor(s) 344, and so on. In another example, in case of FIG. 3B, a particular implementation of the base station 304 may omit the WWAN transceiver(s) 350 (e.g., a Wi-Fi “hotspot” access point without cellular capability), or may omit the short-range wireless transceiver s) 360 (e.g., cellular-only, etc.), or may omit the satellite signal interface 370, and so on. For brevity, illustration of the various alternative configurations is not provided herein, but would be readily understandable to one skilled in the art.

[0108] The various components of the UE 302, the base station 304, and the network entity 306 may be communicatively coupled to each other over data buses 308, 382, and 392,respectively. In an aspect, the data buses 308, 382, and 392 may form, or be part of, a communication interface of the UE 302, the base station 304, and the network entity 306, respectively. For example, where different logical entities are embodied in the same device (e.g., gNB and location server functionality incorporated into the same base station 304), the data buses 308, 382, and 392 may provide communication between them.

[0109] The components of FIGS. 3A, 3B, and 3C may be implemented in various ways. In some implementations, the components of FIGS. 3 A, 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). Here, 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 to 346 may be implemented by processor and memory component(s) of the UE 302 (e.g., by execution of appropriate code and / or by appropriate configuration of processor components). Similarly, some or all of the functionality represented by blocks 350 to 388 may be implemented by processor and memory component(s) of the base station 304 (e.g., by execution of appropriate code and / or by appropriate configuration of processor components). Also, some or all of the functionality represented by blocks 390 to 398 may be implemented by processor and memory component(s) of the network entity 306 (e.g., by execution of appropriate code and / or by appropriate configuration of processor components). For simplicity, various operations, acts, and / or functions are described herein as being performed “by a UE,” “by a base station,” “by a network entity,” etc. However, as will be appreciated, such operations, acts, and / or functions may actually be performed by specific components or combinations of components of the UE 302, base station 304, network entity 306, etc., such as the processors 342, 384, 394, the transceivers 310, 320, 350, and 360, the memories 340, 386, and 396, the positioning component 348, 388, and 398, etc.

[0110] In some designs, the network entity 306 may be implemented as a core network component. In other designs, the network entity 306 may be distinct from a network operator or operation of the cellular network infrastructure (e.g., NG RAN 220 and / or 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 304or independently from the base station 304 (e.g., over a non-cellular communication link, such as Wi-Fi).

[0111] NR supports a number of cellular network-based positioning technologies, including downlink-based, uplink-based, and downlink-and-uplink-based positioning methods. Downlink-based positioning methods include observed time difference of arrival (OTDOA) in LTE, downlink time difference of arrival (DL-TDOA) in NR, and downlink angle-of-departure (DL-AoD) in NR. In an OTDOA or DL-TDOA positioning procedure, a UE measures the differences between the times of arrival (ToAs) of reference signals (e.g., positioning reference signals (PRS)) received from pairs of base stations, referred to as reference signal time difference (RSTD) or time difference of arrival (TDOA) measurements, and reports them to a positioning entity. More specifically, the UE receives the identifiers (IDs) of a reference base station (e.g., a serving base station) and multiple non-reference base stations in assistance data. The UE then measures the RSTD between the reference base station and each of the non-reference base stations. Based on the known locations of the involved base stations and the RSTD measurements, the positioning entity (e.g., the UE for UE-based positioning or a location server for UE- assisted positioning) can estimate the UE’s location.

[0112] For DL-AoD positioning, the positioning entity uses a measurement report from the UE of received signal strength measurements of multiple downlink transmit beams to determine the angle(s) between the UE and the transmitting base station(s). The positioning entity can then estimate the location of the UE based on the determined angle(s) and the known location(s) of the transmitting base station(s).

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

[0114] For UL-AoA positioning, one or more base stations measure the received signal strength of one or more uplink reference signals (e.g., SRS) received from a UE on one or more uplink receive beams. The positioning entity uses the signal strength measurements and the angle(s) of the receive beam(s) to determine the angle(s) between the UE and the base station(s). Based on the determined angle(s) and the known location(s) of the base station(s), the positioning entity can then estimate the location of the UE.

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

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

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

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

[0119] A location estimate may be referred to by other names, such as a position estimate, location, position, position fix, fix, or the like. A location estimate may be geodetic and comprise coordinates (e.g., latitude, longitude, and possibly altitude) or may be civic and comprise a street address, postal address, or some other verbal description of a location. A location estimate may further be defined relative to some other known location or defined in absolute terms (e.g., using latitude, longitude, and possibly altitude). A location estimate may include an expected error or uncertainty (e.g., by including an area or volume within which the location is expected to be included with some specified or default level of confidence).

[0120] Sidelink communication takes place in transmission or reception resource pools. In the frequency domain, the minimum resource allocation unit is a sub-channel (e.g., a collection of consecutive PRBs in the frequency domain). In the time domain, resource allocation is in one slot intervals. However, some slots are not available for sidelink, and some slots contain feedback resources. In addition, sidelink resources can be (pre)configured to occupy fewer than the 14 symbols of a slot.

[0121] Sidelink resources are configured at the radio resource control (RRC) layer. The RRC configuration can be by pre-configuration (e.g., preloaded on the UE) or configuration (e.g., from a serving base station).

[0122] NR sidelinks support hybrid automatic repeat request (HARQ) retransmission. FIG. 4A is a diagram 400 of an example slot structure without feedback resources, according to aspects of the disclosure. In the example of FIG. 4A, time is represented horizontally and frequency is represented vertically. In the time domain, the length of each block is one orthogonal frequency division multiplexing (OFDM) symbol, and the 14 symbols make up a slot. In the frequency domain, the height of each block is one sub-channel. Currently, the (pre)configured sub-channel size can be selected from the set of { 10, 15, 20, 25, 50, 75, 100} physical resource blocks (PRBs).

[0123] For a sidelink slot, the first symbol is a repetition of the preceding symbol and is used for automatic gain control (AGC) setting. This is illustrated in FIG. 4A by the vertical and horizontal hashing. As shown in FIG. 4A, for sidelink, the physical sidelink control channel (PSCCH) and the physical sidelink shared channel (PSSCH) are transmitted in the same slot. Similar to the physical downlink control channel (PDCCH), the PSCCH carries control information about sidelink resource allocation and descriptions about sidelink data transmitted to the UE. Likewise, similar to the physical downlink shared channel (PDSCH), the PSSCH carries user data for the UE. In the example of FIG. 4A, the PSCCH occupies half the bandwidth of the sub-channel and only three symbols. Finally, a gap symbol is present after the PSSCH.

[0124] FIG. 4B is a diagram 450 of an example slot structure with feedback resources, according to aspects of the disclosure. In the example of FIG. 4B, time is represented horizontally and frequency is represented vertically. In the time domain, the length of each block is one OFDM symbol, and the 14 symbols make up a slot. In the frequency domain, the height of each block is one sub-channel.

[0125] The slot structure illustrated in FIG. 4B is similar to the slot structure illustrated in FIG. 4A, except that the slot structure illustrated in FIG. 4B includes feedback resources. Specifically, two symbols at the end of the slot have been dedicated to the physical sidelink feedback channel (PSFCH). The first PSFCH symbol is a repetition of the second PSFCH symbol for AGC setting. In addition to the gap symbol after the PSSCH, there is a gap symbol after the two PSFCH symbols. Currently, resources for the PSFCH can be configured with a periodicity selected from the set of {0, 1, 2, 4} slots.

[0126] The first 13 symbols of a slot in the time domain and the allocated subchannel(s) in the frequency domain form a sidelink resource pool. A sidelink resource pool may include resources for sidelink communication (transmission and / or reception), sidelink positioning (referred to as a resource pool for positioning (RP-P)), or both communication and positioning. A resource pool configured for both communication and positioning is referred to as a “shared” resource pool. In a shared resource pool, the RP-P is indicated by an offset, periodicity, number of consecutive symbols within a slot (e.g., as few as one symbol), and / or the bandwidth within a component carrier (or the bandwidth across multiple component carriers). In addition, the RP-P can be associated with a zone or a distance from a reference location.

[0127] A base station (or a UE, depending on the resource allocation mode) can assign, to another UE, one or more resource configurations from the RP-Ps. Additionally or alternatively, a UE (e.g., a relay or a remote UE) can request one or more RP-P configurations, and it can include in the request one or more of the following: (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 needed (which can be determined through an assigned quality of service (QoS) or priority).

[0128] A base station or a UE can configure / assign rate matching resources or RP-P for rate matching and / or muting to a sidelink UE such that when a collision exists between the assigned resources and another resource pool that contains data (PSSCH) and / or control (PSCCH), the sidelink UE is expected to rate match, mute, and / or puncture the data, DMRS, and / or CSI-RS within the colliding resources. This would enable orthogonalization between positioning and data transmissions for increased coverage of PRS signals.

[0129] Sidelink communication takes place in transmission or reception resource pools. In the frequency domain, the minimum resource allocation unit is a sub-channel (e.g., a collection of consecutive PRBs in the frequency domain). In the time domain, resource allocation is in one slot intervals. However, some slots are not available for sidelink, and some slots contain feedback resources. In addition, sidelink resources can be (pre)configured to occupy fewer than the 14 symbols of a slot.

[0130] Sidelink resources are configured at the radio resource control (RRC) layer. The RRC configuration can be by pre-configuration (e.g., preloaded on the UE) or configuration (e.g., from a serving base station).

[0131] NR sidelinks support hybrid automatic repeat request (HARQ) retransmission. FIG. 5A is a diagram 500 of an example slot structure without feedback resources, according to aspects of the disclosure. In the example of FIG. 5A, time is represented horizontally and frequency is represented vertically. In the time domain, the length of each block is one orthogonal frequency division multiplexing (OFDM) symbol, and the 14 symbols make up a slot. In the frequency domain, the height of each block is one sub-channel. Currently, the (pre)configured sub-channel size can be selected from the set of { 10, 15, 20, 25, 50, 75, 100} physical resource blocks (PRBs).

[0132] For a sidelink slot, the first symbol is a repetition of the preceding symbol and is used for automatic gain control (AGC) setting. This is illustrated in FIG. 5A by the vertical and horizontal hashing. As shown in FIG. 5A, for sidelink, the physical sidelink control channel (PSCCH) and the physical sidelink shared channel (PSSCH) are transmitted in the same slot. Similar to the physical downlink control channel (PDCCH), the PSCCH carries control information about sidelink resource allocation and descriptions about sidelink data transmitted to the UE. Likewise, similar to the physical downlink shared channel (PDSCH), the PSSCH carries user data for the UE. In the example of FIG. 5 A, the PSCCH occupies half the bandwidth of the sub-channel and only three symbols. Finally, a gap symbol is present after the PSSCH.

[0133] FIG. 5B is a diagram 550 of an example slot structure with feedback resources, according to aspects of the disclosure. In the example of FIG. 5B, time is represented horizontally and frequency is represented vertically. In the time domain, the length of each block is one OFDM symbol, and the 14 symbols make up a slot. In the frequency domain, the height of each block is one sub-channel.

[0134] The slot structure illustrated in FIG. 5B is similar to the slot structure illustrated in FIG. 5A, except that the slot structure illustrated in FIG. 5B includes feedback resources. Specifically, two symbols at the end of the slot have been dedicated to the physical sidelink feedback channel (PSFCH). The first PSFCH symbol is a repetition of the second PSFCH symbol for AGC setting. In addition to the gap symbol after the PSSCH, there is a gap symbol after the two PSFCH symbols. Currently, resources for the PSFCH can be configured with a periodicity selected from the set of {0, 1, 2, 4} slots.

[0135] FIG. 6A is a diagram 600 illustrating an example of a resource pool for positioning configured within a sidelink resource pool for communication (i.e., a shared resource pool), according to aspects of the disclosure. In the example of FIG. 6A, 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 the 14 symbols make up a slot. In the frequency domain, the height of each block is a sub-channel.

[0136] In the example of FIG. 6 A, the entire slot (except for the first and last symbols) can be a resource pool for sidelink communication. That is, any of the symbols other than the first and last can be allocated for sidelink communication. However, a resource pool for positioning (RP-P) is allocated in the last four pre-gap symbols of the slot. As such, nonsidelink positioning data, such as user data (PSSCH), channel state information reference signal (CSI-RS), and control information, can only be transmitted in the first eight postautomatic gain control (AGC) symbols and not in the last four pre-gap symbols to prevent a collision with the configured RP-P. The non-sidelink positioning data that would otherwise be transmitted in the last four pre-gap symbols can be punctured or muted, or the non-sidelink data that would normally span more than the eight post-AGC symbols can be rate matched to fit into the eight post-AGC symbols.

[0137] Sidelink positioning reference signals (SL-PRS) have been defined to enable sidelink positioning procedures among UEs. Like a downlink PRS (DL-PRS), a SL-PRS resource is composed of one or more resource elements (i.e., one OFDM symbol in the time domain and one subcarrier in the frequency domain). SL-PRS resources have been designed with a comb-based pattern to enable fast Fourier transform (FFT)-based processing at the receiver. SL-PRS resources are composed of unstaggered, or only partially staggered, resource elements in the frequency domain to provide small time ofarrival (TO A) uncertainty and reduced overhead of each SL-PRS resource. SL-PRS may also be associated with specific RP-Ps (e.g., certain SL-PRS may be allocated in certain RP-Ps). SL-PRS have also been defined with intra-slot repetition (not shown in FIG. 6A) to allow for combining gains (if needed). There may also be inter-UE coordination of RP- Ps to provide for dynamic SL-PRS and data multiplexing while minimizing SL-PRS collisions.

[0138] FIGS. 6B and 6C are diagrams 630 and 650, respectively, illustrating additional examples of resource pools for positioning configured within sidelink resource pools for communication. Similar to FIG. 6, the examples of FIGS. 6B and 6C illustrate shared resource pool structures. With respect to FIGS. 6B and 6C, in some designs, the following parameters may be defined, for example: physical sidelink control channel (PSCCH) and SL-PRS are only time-division multiplexed, PSSCH and SL-PRS are only time-division multiplexed (e.g., the maximum comb size is 4), PSSCH carries both type 2 sidelink control information (SCL2) and a sidelink shared channel (SL-SCH) (e.g., a new SCL2 format is introduced), SL-PRS is mapped on consecutive symbols, SL-PRS is not mapped on symbols with PSSCH demodulation reference signals (DMRS), and / or SL-PRS transmit power is the same as the transmit power of the PSSCH (e.g., this implies perresource element power boosting will be applied for comb-2 and comb-4).

[0139] FIG. 6D is a diagram 670 illustrating another example of a resource pool for positioning configured within a sidelink resource pool for communication. In the example of FIG. 6D, a dedicated resource pool structure is depicted. With respect to FIG. 6D, in some designs, the following parameters may be defined, for example: SL-PRS is immediately preceded by an AGC symbol, SL-PRS is immediately followed by a gap symbol (at least when the gap symbol is the last sidelink symbol in a slot), PSCCH and SL-PRS can only be time-division multiplexed, different comb sizes (N) and SL-PRS durations (M) can be supported in the same resource pool (e.g., one set of SL-PRS resources can only have a single (M, N) combination), PSSCH is mapped to the first sidelink symbols in a slot, the number of PSCCH symbols is (pre-)configured to 1, 2, or 3, the number of physical resource blocks is (pre-)configured using sidelink communications values, and / or there is a one-to-one implicit mapping between PSCCH and SL-PRS.

[0140] In some designs, in a shared resource pool, with regards to the fields in SCI format 2-D, the following fields may be included, for example: a SL-PRS resource informationindication of the current slot (ceiling(log2(#SL-PRS resources (pre-)configured in the resource pool) bits)), SL-PRS request (0 or 1 bit), and / or embedded SCI format ([X] bit(s)). If the “embedded SCI format” field is set to [0], the SCI 2- A fields are included with necessary padding. If the “embedded SCI format” field is set to [1], the SCI 2-B fields are included.

[0141] In some designs, for a shared resource pool, there may be an explicit (pre-)configuration of SL-PRS resources in a slot, applicable for an indicated frequency domain allocation, which includes, for example: SL-PRS Resource ID, (M, N) pattern, and / or comb offset. In some designs, for a given value of ‘M,’ a SL-PRS resource is mapped to the last consecutive ‘M’ sidelink symbol(s) in the slot that can be used for SL-PRS, taking into consideration multiplexing with PSSCH DMRS, phase tracking reference signals (PT- RS), CSI-RS, PSFCH, gap symbols, AGC symbols, and / or PSCCH in the slot. In some designs, the maximum number of SL-PRS resources in a slot of a shared resource pool may be (pre-)configured.

[0142] In some designs, in dedicated resource pools, with regards to the procedure for determining the subset of resources to be reported to higher layers, when triggering the resource (re-)selection procedure, the higher layers provide the following parameters for candidate SL-PRS transmission(s), for example: resource pool from which to report SL- PRS resources, priority, delay budget, reservation period, list of resources for pre-emption and re-evaluation, and / or the set of SL-PRS resource identifiers that can include all (pre- )configured SL-PRS resource identifiers.

[0143] FIG. 7 shows an example set of resource reservation parameters 900, according to aspects of the disclosure. In this example, the parameters of the resource reservations signaled in the SCI of a given slot (e.g., Slot) are shown in Table 702. Here, the SCI for a Slot has signaled reservations for Slot, and two future slots, Slot -+x (where 0< x < 31) and Slot, , (where x < y < 31). In each instance, it is assumed that the maximum number of slots that can be reserved is 32. Additionally, table 702 indicates that the number of subchannels reserved for the reserved resource is z (e.g., 2 sub-channels in this example). FIG. 8 shows an example resource reservation implementation 800 in the time and frequency domains, according to aspects of the disclosure.

[0144] In an aspect, the SCI-1 signaling may include SCL1B fields used in scheduling the resources of a dedicated resource pool. The SCI- IB fields may include:• SL-PRS priority - 3 bits• Source ID - Up to resource pool (pre-)configuration 12 or 24 bits• Destination ID - 24 bits• Cast type• Resource reservation period: Up to 16 values• Time resource assignment for SL-PRS future reservations• SL-PRS resource ID(s) for the future 1 or 2 reservations• SL-PRS request bit• Reserved bits - up to (pre-)configuration

[0145] In an aspect, the SCL2 signaling may include SCI-2D fields used in scheduling the resources of a shared resource pool. The SCI-2D fields may include:• SL-PRS resource information indication of the current slot• SL-PRS request bit• Embedded format indicator (2 bits): o 00: include the fields of SCI-2A in the scheduling o 01 : include the fields on SCL2B in the scheduling o 10 & 11 : reserved.

[0146] According to aspects of the disclosure, the SL-PRS resources of different resource pools may be bandwidth aggregated. SL-PRS bandwidth aggregation involves the aggregation of the SL-PRS resource blocks across the different frequency bands associated with the different resource pools to enhance positioning measurements. Such bandwidth aggregation can improve the accuracy of positioning by increasing the signal bandwidth, which leads to better time resolution and more precise Time Difference of Arrival (TDoA) estimates.

[0147] Certain aspects of the disclosure are directed to optimal signaling for determining the SL- PRS of multiple, different SL-PRS resource pools that are to be bandwidth aggregated. In an aspect, the various aspects of the disclosure may be used to reduce the transmission resources employed to identify the specific SL-PRS resources that are to be bandwidth aggregated.

[0148] Certain aspects of the disclosure are implemented with a recognition that SL-PRS scheduling information for aggregated SL-PRS resources need not be included in the scheduling information of all SL-PRS resource pools having SL-PRS there are to beaggregated. In an aspect, a sidelink device receives the sidelink position resource signal (SL-PRS) scheduling information for aggregating SL-PRS resources of a plurality of SL- PRS resource pools in only a subset of SL-PRS resource pools of the plurality of SL-PRS resource pools. The sidelink device may then obtain one or more aggregated measurements of the SL-PRS resources of the plurality of SL-PRS resource pools based on the SL-PRS scheduling information indicated in the subset of SL-PRS resource pools.

[0149] Note that the following examples show the symbols of the SCI, PSCCH, PSSCH, and SL-PRS grouped with one another. However, it should be recognized that each such grouping may include multiple symbols and that the symbol format used in this description may be based on a 14 symbol sidelink slot structures discussed above.

[0150] In an aspect, the SL-PRS scheduling information may be indicated in various manners without including the scheduling information in all of the SL-PRS resource pools heading SL-PRS that are to be bandwidth aggregated. FIG. 9 depicts an example scenario 900 for providing SL-PRS scheduling information for bandwidth aggregation, according to aspects of the disclosure. Two SL-PRS resource pools 902 and 904 are shown in the example scenario 900. The PSCCH 906 and 908 of both SL-PRS resource pools 902 and 904 may carry SCL1 signaling 910 and 912. However, only a subset of the SL resource pools have SCL2 signaling that includes the information that schedules all the aggregated SL-PRS across multiple shared resource pools. In the example shown in FIG. 13, only the SL-PRS resource pool 904 includes the SL-PRS scheduling information for the SL- PRS bandwidth aggregation. In this example, SL-PRS resource pool 904 includes SCL2 signaling 914 indicating that SL-PRS resource 916 of SL-PRS resource pool 904 is to be bandwidth aggregated with SL-PRS resource 918 of SL-PRS resource pool 902.

[0151] Since the SCL2 is carried by less than all of the SL-PRS resource pools, the sidelink device may need an indication of which of the SL-PRS resource pools include the SCI-2 identifying the SL-PRS resources for bandwidth aggregation. According to various aspects of the disclosure, the sidelink device may receive a shared resource pool (pre)configuration (e.g., via RRC signaling) indicating which SL-PRS resource pool will have the requisite SCI-2 SL-PRS aggregation information. Additionally, or in the alternative, the sidelink device may receive an indication in the SCL1 in a given SL-PRS resource pool as to whether the SCI-2 four aggregation is included in the given SL- resource pool carrying that SCI-1. In an aspect, whether the given SL-PRS resource poolincludes the requisite SCI-2 aggregation information may be indicated in, for example, reserved bits of the SCI-1 transmission. Additionally, or in the alternative, the SCI-1 may identify the SL-PRS resource pool carrying the SCI-2 aggregation information (e.g., reusing reserved bits of the SCI-1 transmission).

[0152] FIG. 10 depicts another example scenario 1000 for providing SL-PRS scheduling information for bandwidth aggregation, according to aspects of the disclosure. In the example scenario 1000, there are three SL-PRS resource pools 1002, 1004, and 1006. Again, only a single SL-PRS resource pool 1002 carries the SCI-2 1008 having the SL- PRS bandwidth aggregation information. Here, SCI-2 1008 indicates that SL-PRS resources 1010, 1012, and 1014 are to be bandwidth aggregated.

[0153] FIG. 11 depicts another example scenario 1100 for providing SL-PRS scheduling information for bandwidth aggregation, according to aspects of the disclosure. In the example scenario 1100, there are three SL-PRS resource pools 1102, 1104, and 1106. Both SL-PRS resource pools 1102 and 1104 carry respective SCI-2 1108 and 1110. However, only SL-PRS resource pool 1102 carries the SCI-2 1108 having the SL-PRS bandwidth aggregation information. Here, SCI-2 1108 indicates that SL-PRS resources 1112, 1114, and 1116 are to be bandwidth aggregated. The SCI-2 1110 of SL-resource pool 1104 need not carry SL-PRS aggregation indications. Rather, SCI-2 may be included in the SL-PRS resource pool 1104 if the SL-PRS resource pool 1104 is to be employed by sidelink devices that do not have bandwidth aggregation capabilities or are otherwise not needed for bandwidth aggregation. Scenario 1100 may be implemented, for example, when a sidelink device (e.g., Legacy device) operates in the SL-PRS resource pool 1104 and the SL-PRS resource pool 1104 is groupcast and / or broadcast. This may be the case when one sidelink device is expected to receive SL-PRS on all aggregated SL-PRS resources, but another sidelink device will only receive SL-PRS on non-aggregated SL-PRS resources. In this latter case, the SCI-2 in that SL-PRS resource pool (e.g., SL-PRS resource pool 1104) should not be removed. With respect to the example scenario 1100, SCI-2 1110 indicates the position of SL-PRS resource 1114 for use by such sidelink devices.

[0154] FIG. 12 depicts another example scenario 1200 for providing SL-PRS scheduling information for bandwidth aggregation, according to aspects of the disclosure. Two SL- PRS resource pools 1202 and 1204 are shown in the example scenario 1200. In this case,all sidelink devices may be (pre-)configured to perform the resource sensing and reservation monitoring in a subset of the SL-PRS resource pools and therefore only monitor SCI-1 in that SL-PRS resource pool subset (e.g., SCI-1 1206 of a single SL- resource pool 1202). Here, SCI-1 1206 may indicate that a schedule for aggregated SL- PRS resources across multiple SL-PRS resource pools is indicated in SCL2 1208. In this example, SL-PRS resource pool 1202 includes SCI-1 signaling indicating that a schedule for aggregated SL-PRS resources across multiple SL-PRS resource pools is indicated in SCI-2 1208. In turn, the SCI-2 1208 indicates that SL-PRS resource 1210 of SL-PRS resource pool 1202 is to be bandwidth aggregated with SL-PRS resource 1212 of SL-PRS resource pool 1204.

[0155] In accordance with certain aspects of the disclosure, SCL2D for shared SL-PRS resource pools includes an SL-PRS resource information indication for the current slot and an SL- PRS request bit. Additionally, the SCI-2D includes an embedded format indicator (e.g., 2 bits) indicating whether to include the fields of SCI-2 A (e.g., bit pattern 00) or SCL2B (e.g., bit pattern 01). The SCL2D may also include reserved state bit patterns (e.g., bit patterns 10 and 11).

[0156] In accordance with certain aspects of the disclosure, one or more of the reserved states may be used to indicate that the SL-PRS resource corresponds to aggregated SL-PRS resources. To this end, the sidelink device may receive a (pre-)configuration of which SL-PRS resources and / or which SL-PRS resource pools are to be aggregated with one another. When the embedded format of the SCL2D includes a specified bit pattern (e.g., bit pattern 10), the indicated SL-PRS is bandwidth aggregated with the aggregated / linked SL-PRS resources in the other SL-PRS resource pools.

[0157] FIG. 13 depicts another example scenario 1300 for providing SL-PRS scheduling information for bandwidth aggregation, according to aspects of the disclosure. Two SL- PRS resource pools 1302 and 1304 are shown in the example scenario 1300. In scenario 1300, a single SCLl may be transmitted in a subset of the SL-PRS resource pools (e.g., SCI-1 1306 of SL-PRS resource pool 1302). Here, a sidelink device may be (pre- )configured in each dedicated SL-PRS resource pool to monitor the SCI-l transmission in the dedicated SL-PRS resource pool or in another SL-PRS resource pool. In an aspect, SCI-1B fields of the SCLl transmission apply to all the aggregated SL-PRS resourcesacross all of the aggregated SL-PRS resource pools. In an aspect, the SCI- IB fields may include:• SL-PRS priority (e.g., 3 bits)• Source ID - based on resource pool (pre-)configuration (e.g., 12 or 24 bits)• Destination ID (e.g., 24 bits)• Cast type• Resource reservation period (e.g., up to 16 values)• Time resource assignment for future SL-PRS reservations• SL-PRS request bit• Reserved bits - based on (pre-)configuration

[0158] The SCI- IB fields may also include an SL-PRS resource ID. In an aspect, the SL-PRS resource ID(s) are used for the future 1 or 2 reservations. Additionally, or in the alternative, multiple fields of the SL-PRS resource ID(s) may be used for the future 1 or 2 reservations, where each field corresponds to different SL-PRS pools for positioning. In an aspect, these fields provide the SL-PRS resource IDs that are going to be scheduled in future slots. In other words, these fields provide for future reservations. This is useful because other sidelink devices may also read the SCL1B fields and determine that these SL-RS resources are going to be occupied in the future thereby allowing the sidelink devices to avoid collisions.

[0159] In FIG. 13, the SCI-1B fields of SCL1 1306 of SL-PRS resource pool 1302 are applicable to both SL-PRS resource pools 1302 and 1304. In an aspect, all SL-PRS resources 1308 and 1310 of both SL-PRS pools 1302 and 1304 may be bandwidth aggregated.

[0160] In scenario 1300, there may be a direct mapping of the PSCCH index (e.g., the PSCCH index associated with SCL1 1306) and the SL-PRS resource IDs of SL-PRS resources 1308 and 1310 that are to be aggregated across multiple SL-PRS resource pools. In an aspect, each PSCCH index (e.g., subchannel) maps to a (pre-)configured tuple of SL-PRS resource IDs (e.g., PSCCH subchannel 1 maps to SL-PRS resource 1 of the same subchannel as well as SL-PRS resource 2 of another SL-PRS pool; PSCCH subchannel 2 maps to SL-PRS resource 3 of the same subchannel as well as SL-PRS resource 4 of another SL-PRS pool; PSCCH subchannel 3 maps to SL-PRS resource 5 of the same subchannel as well as SL-PRS resource 6 of another SL-PRS pool.)

[0161] FIG. 14 depicts another example scenario 1400 for providing SL-PRS scheduling information for bandwidth aggregation, according to aspects of the disclosure. In an aspect, scenario 1400 applies to aggregated dedicated SL-PRS resource pools for positioning. Two SL-PRS resource pools 1402 and 1404 are shown in the example scenario 1500. Like scenario 1400 of FIG. 14, example scenario 1500 includes a mapping of the PSCCH index (e.g., the PSCCH index associated with SCL1 1406) and the SL- PRS resource IDs of SL-PRS resources that are to be aggregated across multiple SL-PRS resource pools. In scenario 1400 the PSCCH index maps to an SL-PRS resource in the same SL-PRS resource pool (e.g., PSCCH-i maps to SL-PRS resource i). However, when a given SL-PRS resource in the same SL-PRS resource pool is indicated for positioning, a corresponding SL-PRS resource in another SL-PRS resource pool that is explicitly linked with the given SL-PRS resource is also scheduled for aggregation with it. For example, a PSCCH-i may be mapped directly to SL-PRS resource i in the same SL-PRS resource pool, and SL-PRS resource i is linked for aggregation with SL-PRS resource j in another SL-PRS resource pool. In this regard, a given SL-PRS pool of a given SL- PRS resource pool is linked with an SL-PRS resource of another SL-PRS resource pool. With reference to FIG. 14, the location of SCI-1 1406 in SL-PRS resource pool 1402 schedules SL-PRS resource 1408 and SL-PRS resource 1408, in turn, is pre-configured to be aggregated with SL-PRS 1410 in SL-PRS resource pool 1404.

[0162] While the foregoing example relates to an explicit relationship between the PSCCH index, the corresponding SL-PRS resource, and a linked SL-PRS resource in another SL-PRS resource pool, an implicit association may also be employed. In an aspect, when an SL- PRS resource ID of the SL-PRS resource pool carrying the PSCCH is scheduled, the implicitly associated SL-PRS resources of other SL-resource pools are also scheduled for aggregation. SL-PRS resources in different SL-PRS resource pools may be considered to be implicitly associated if the SL-PRS resource occurs on the same symbol, has the same comb-size, and has the same comb-offset as the SL-PRS resource of the SL-PRS resource pool carrying the PSCCH.

[0163] FIG. 15 illustrates an example method 1500 wireless communication performed by a sidelink device, according to aspects of the disclosure. At operation 1502, the sidelink device receives sidelink position resource signal (SL-PRS) scheduling information for aggregating SL-PRS resources of a plurality of SL-PRS resource pools, wherein the SL-PRS scheduling information is only indicated by a subset of SL-PRS resource pools of the plurality of SL-PRS resource pools. In an aspect, operation 1502 may be performed by the one or more WWAN transceivers 310, the one or more processors 332, memory 340, and / or positioning component 342, any or all of which may be considered means for performing this operation.

[0164] At operation 1504, the sidelink device obtains one or more aggregated measurements of the SL-PRS resources of the plurality of SL-PRS resource pools based on the SL-PRS scheduling information indicated by the subset of SL-PRS resource pools. In an aspect, operation 1504 may be performed by the one or more WWAN transceivers 310, the one or more processors 332, memory 340, and / or positioning component 342, any or all of which may be considered means for performing this operation.

[0165] As will be appreciated, a technical advantage of the method 1500 is that the scheduling of SL-PRS resources that are to be aggregated may be accomplished using fewer communication resources when compared to conventional SL-PRS resource aggregation scheduling.

[0166] In the detailed description above it can be seen that different features are grouped together in examples. This manner of disclosure should not be understood as an intention that the example clauses have more features than are explicitly mentioned in each clause. Rather, the various aspects of the disclosure may include fewer than all features of an individual example clause disclosed. Therefore, the following clauses should hereby be deemed to be incorporated in the description, wherein each clause by itself can stand as a separate example. Although each dependent clause can refer in the clauses to a specific combination with one of the other clauses, the aspect(s) of that dependent clause are not limited to the specific combination. It will be appreciated that other example clauses can also include a combination of the dependent clause aspect(s) with the subject matter of any other dependent clause or independent clause or a combination of any feature with other dependent and independent clauses. The various aspects disclosed herein expressly include these combinations, unless it is explicitly expressed or can be readily inferred that a specific combination is not intended (e.g., contradictory aspects, such as defining an element as both an electrical insulator and an electrical conductor). Furthermore, it is also intended that aspects of a clause can be included in any other independent clause, even if the clause is not directly dependent on the independent clause.

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

[0168] Clause 1. A method of wireless communication performed by a sidelink device, comprising: receiving sidelink position resource signal (SL-PRS) scheduling information for aggregating SL-PRS resources of a plurality of SL-PRS resource pools, wherein the SL-PRS scheduling information is only indicated by a subset of SL-PRS resource pools of the plurality of SL-PRS resource pools; and obtaining one or more aggregated measurements of the SL-PRS resources of the plurality of SL-PRS resource pools based on the SL-PRS scheduling information indicated by the subset of SL-PRS resource pools.

[0169] Clause 2. The method of clause 1, wherein: the SL-PRS scheduling information is only included in a single SL-PRS resource pool of the plurality of SL-PRS resource pools.

[0170] Clause 3. The method of any of clauses 1 to 2, wherein: the SL-PRS scheduling information is indicated in second stage sidelink control information (SCI-2) of one or more SL-PRS resource pools of the subset of SL-PRS resource pools.

[0171] Clause 4. The method of clause 3, wherein: the SCI-2 of at least one given SL-PRS resource pool of the one or more SL-PRS resource pools includes an embedded format indicator indicating that SL-PRS of the at least one given SL-PRS resource pool are to be aggregated with SL-PRS of other SL-PRS resource pools of the plurality of SL-PRS resource pools.

[0172] Clause 5. The method of any of clauses 3 to 4, wherein: the SL-PRS scheduling information is indicated in the SCI-2 of fewer than all of the subset of SL-PRS resource pools.

[0173] Clause 6. The method of clause 5, wherein: the SL-PRS scheduling information is indicated in the SCI-2 of a single SL-PRS resource pool of the plurality of SL-PRS resource pools.

[0174] Clause 7. The method of any of clauses 5 to 6, wherein: at least one SL-PRS resource pool of the subset of SL-PRS resource pools includes first stage scheduling information (SCI-1) indicating one or more locations of the SCI-2 in the fewer than all of the subset of SL-PRS resource pools.

[0175] Clause 8. The method of any of clauses 5 to 7, wherein: the sidelink device is preconfigured with an indication of one or more locations of the SCI-2 in the fewer than all of the subset of SL-PRS resource pools.

[0176] Clause 9. The method of clause 8, wherein: the sidelink device is pre-configured with an indication of one or more locations of the SCI-2 via Radio Resource Control (RRC) messaging.

[0177] Clause 10. The method of any of clauses 1 to 9, wherein: the SL-PRS scheduling information is indicated in first stage sidelink control information (SCI-1) of a single SL- PRS resource pool of the plurality of SL-PRS resource pools.

[0178] Clause 11. The method of clause 10, wherein: the SCLl of the single SL-PRS resource pool includes a plurality of fields, wherein the plurality of fields of the SCI-l are applicable to all of the plurality of SL-PRS resource pools.

[0179] Clause 12. The method of any of clauses 10 to 11, wherein: one or more of the plurality of SL-PRS resource pools do not include sidelink control information.

[0180] Clause 13. The method of claim 12, wherein: the sidelink device is pre-configured to aggregate SL-PRS resources of the plurality of SL-PRS resource pools based on the SCL 1 of the single SL-PRS resource pool.

[0181] Clause 14. The method of any of clauses 10 to 13, wherein: the SL-PRS scheduling information is indicated in the SCLl and second stage sidelink control information (SCL 2) of a single SL-resource pool of the subset of SL-resource pools.

[0182] Clause 15. The method of any of clauses 1 to 14, wherein: the plurality of SL-PRS resource pools comprise a plurality of dedicated SL-PRS resource pools; and at least one dedicated SL-PRS resource pool of the plurality of dedicated SL-PRS resource pools includes a physical sidelink control channel (PSCCH) having a subchannel index that corresponds to a tuple of SL-PRS resources that are to be aggregated over the plurality of dedicated SL-PRS resource pools.

[0183] Clause 16. The method of clause 15, wherein: the subchannel index is directly mapped to resource identifiers corresponding to the tuple of SL-PRS resources.

[0184] Clause 17. The method of any of clauses 15 to 16, wherein: the subchannel index is mapped to a resource identifier of a SL-PRS resource of the at least one dedicated SL- PRS resource pool; and the sidelink device is preconfigured to associate a further resource identifier of a further SL-PRS of a further dedicated SL-PRS resource pool for aggregation with the SL-PRS resource of the at least one dedicated SL-PRS resource pool.

[0185] Clause 18. A sidelink device, comprising: one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or morememories and the one or more transceivers, the one or more processors, either alone or in combination, configured to: receive, via the one or more transceivers, sidelink position resource signal (SL-PRS) scheduling information for aggregating SL-PRS resources of a plurality of SL-PRS resource pools, wherein the SL-PRS scheduling information is only indicated by a subset of SL-PRS resource pools of the plurality of SL-PRS resource pools; and obtain one or more aggregated measurements of the SL-PRS resources of the plurality of SL-PRS resource pools based on the SL-PRS scheduling information indicated by the subset of SL-PRS resource pools.

[0186] Clause 19. The sidelink device of clause 18, wherein: the SL-PRS scheduling information is only included in a single SL-PRS resource pool of the plurality of SL-PRS resource pools.

[0187] Clause 20. The sidelink device of any of clauses 18 to 19, wherein: the SL-PRS scheduling information is indicated in second stage sidelink control information (SCI-2) of one or more SL-PRS resource pools of the subset of SL-PRS resource pools.

[0188] Clause 21. The sidelink device of clause 20, wherein: the SCI-2 of at least one given SL- PRS resource pool of the one or more SL-PRS resource pools includes an embedded format indicator indicating that SL-PRS of the at least one given SL-PRS resource pool are to be aggregated with SL-PRS of other SL-PRS resource pools of the plurality of SL- PRS resource pools.

[0189] Clause 22. The sidelink device of any of clauses 20 to 21, wherein: the SL-PRS scheduling information is indicated in the SCI-2 of fewer than all of the subset of SL-PRS resource pools.

[0190] Clause 23. The sidelink device of clause 22, wherein: the SL-PRS scheduling information is indicated in the SCI-2 of a single SL-PRS resource pool of the plurality of SL-PRS resource pools.

[0191] Clause 24. The sidelink device of any of clauses 22 to 23, wherein: at least one SL-PRS resource pool of the subset of SL-PRS resource pools includes first stage scheduling information (SCL1) indicating one or more locations of the SCI-2 in the fewer than all of the subset of SL-PRS resource pools.

[0192] Clause 25. The sidelink device of any of clauses 22 to 24, wherein: the sidelink device is pre-configured with an indication of one or more locations of the SCI-2 in the fewer than all of the subset of SL-PRS resource pools.

[0193] Clause 26. The sidelink device of clause 25, wherein: the sidelink device is pre-configured with an indication of one or more locations of the SCI-2 via Radio Resource Control (RRC) messaging.

[0194] Clause 27. The sidelink device of any of clauses 18 to 26, wherein: the SL-PRS scheduling information is indicated in first stage sidelink control information (SCI-1) of a single SL-PRS resource pool of the plurality of SL-PRS resource pools.

[0195] Clause 28. The sidelink device of clause 27, wherein: the SCI-1 of the single SL-PRS resource pool includes a plurality of fields, wherein the plurality of fields of the SCI-1 are applicable to all of the plurality of SL-PRS resource pools.

[0196] Clause 29. The sidelink device of any of clauses 27 to 28, wherein: one or more of the plurality of SL-PRS resource pools do not include sidelink control information.

[0197] Clause 30. The sidelink device of clause 29, The method of claim 12, wherein: the sidelink device is pre-configured to aggregate SL-PRS resources of the plurality of SL- PRS resource pools based on the SCI-1 of the single SL-PRS resource pool.

[0198] Clause 31. The sidelink device of any of clauses 27 to 30, wherein: the SL-PRS scheduling information is indicated in the SCLl and second stage sidelink control information (SCI-2) of a single SL-resource pool of the subset of SL-resource pools.

[0199] Clause 32. The sidelink device of any of clauses 18 to 31, wherein: the plurality of SL- PRS resource pools comprise a plurality of dedicated SL-PRS resource pools; and at least one dedicated SL-PRS resource pool of the plurality of dedicated SL-PRS resource pools includes a physical sidelink control channel (PSCCH) having a subchannel index that corresponds to a tuple of SL-PRS resources that are to be aggregated over the plurality of dedicated SL-PRS resource pools.

[0200] Clause 33. The sidelink device of clause 32, wherein: the subchannel index is directly mapped to resource identifiers corresponding to the tuple of SL-PRS resources.

[0201] Clause 34. The sidelink device of any of clauses 32 to 33, wherein: the subchannel index is mapped to a resource identifier of a SL-PRS resource of the at least one dedicated SL- PRS resource pool; and the sidelink device is preconfigured to associate a further resource identifier of a further SL-PRS of a further dedicated SL-PRS resource pool for aggregation with the SL-PRS resource of the at least one dedicated SL-PRS resource pool.

[0202] Clause 35. A sidelink device, comprising: means for receiving sidelink position resource signal (SL-PRS) scheduling information for aggregating SL-PRS resources of a pluralityof SL-PRS resource pools, wherein the SL-PRS scheduling information is only indicated by a subset of SL-PRS resource pools of the plurality of SL-PRS resource pools; and means for obtaining one or more aggregated measurements of the SL-PRS resources of the plurality of SL-PRS resource pools based on the SL-PRS scheduling information indicated by the subset of SL-PRS resource pools.

[0203] Clause 36. The sidelink device of clause 35, wherein: the SL-PRS scheduling information is only included in a single SL-PRS resource pool of the plurality of SL-PRS resource pools.

[0204] Clause 37. The sidelink device of any of clauses 35 to 36, wherein: the SL-PRS scheduling information is indicated in second stage sidelink control information (SCI-2) of one or more SL-PRS resource pools of the subset of SL-PRS resource pools.

[0205] Clause 38. The sidelink device of clause 37, wherein: the SCI-2 of at least one given SL- PRS resource pool of the one or more SL-PRS resource pools includes an embedded format indicator indicating that SL-PRS of the at least one given SL-PRS resource pool are to be aggregated with SL-PRS of other SL-PRS resource pools of the plurality of SL- PRS resource pools.

[0206] Clause 39. The sidelink device of any of clauses 37 to 38, wherein: the SL-PRS scheduling information is indicated in the SCI-2 of fewer than all of the subset of SL-PRS resource pools.

[0207] Clause 40. The sidelink device of clause 39, wherein: the SL-PRS scheduling information is indicated in the SCI-2 of a single SL-PRS resource pool of the plurality of SL-PRS resource pools.

[0208] Clause 41. The sidelink device of any of clauses 39 to 40, wherein: at least one SL-PRS resource pool of the subset of SL-PRS resource pools includes first stage scheduling information (SCL1) indicating one or more locations of the SCI-2 in the fewer than all of the subset of SL-PRS resource pools.

[0209] Clause 42. The sidelink device of any of clauses 39 to 41, wherein: the sidelink device is pre-configured with an indication of one or more locations of the SCI-2 in the fewer than all of the subset of SL-PRS resource pools.

[0210] Clause 43. The sidelink device of clause 42, wherein: the sidelink device is pre-configured with an indication of one or more locations of the SCI-2 via Radio Resource Control (RRC) messaging.

[0211] Clause 44. The sidelink device of any of clauses 35 to 43, wherein: the SL-PRS scheduling information is indicated in first stage sidelink control information (SCI-1) of a single SL-PRS resource pool of the plurality of SL-PRS resource pools.

[0212] Clause 45. The sidelink device of clause 44, wherein: the SCI-1 of the single SL-PRS resource pool includes a plurality of fields, wherein the plurality of fields of the SCI-1 are applicable to all of the plurality of SL-PRS resource pools.

[0213] Clause 46. The sidelink device of any of clauses 44 to 45, wherein: one or more of the plurality of SL-PRS resource pools do not include sidelink control information.

[0214] Clause 47. The sidelink device of clause 46, The method of claim 12, wherein: the sidelink device is pre-configured to aggregate SL-PRS resources of the plurality of SL- PRS resource pools based on the SCI-1 of the single SL-PRS resource pool.

[0215] Clause 48. The sidelink device of any of clauses 44 to 47, wherein: the SL-PRS scheduling information is indicated in the SCLl and second stage sidelink control information (SCL2) of a single SL-resource pool of the subset of SL-resource pools.

[0216] Clause 49. The sidelink device of any of clauses 35 to 48, wherein: the plurality of SL- PRS resource pools comprise a plurality of dedicated SL-PRS resource pools; and at least one dedicated SL-PRS resource pool of the plurality of dedicated SL-PRS resource pools includes a physical sidelink control channel (PSCCH) having a subchannel index that corresponds to a tuple of SL-PRS resources that are to be aggregated over the plurality of dedicated SL-PRS resource pools.

[0217] Clause 50. The sidelink device of clause 49, wherein: the subchannel index is directly mapped to resource identifiers corresponding to the tuple of SL-PRS resources.

[0218] Clause 51. The sidelink device of any of clauses 49 to 50, wherein: the subchannel index is mapped to a resource identifier of a SL-PRS resource of the at least one dedicated SL- PRS resource pool; and the sidelink device is preconfigured to associate a further resource identifier of a further SL-PRS of a further dedicated SL-PRS resource pool for aggregation with the SL-PRS resource of the at least one dedicated SL-PRS resource pool.

[0219] Clause 52. A non-transitory computer-readable medium storing computer-executable instructions that, when executed by a sidelink device, cause the sidelink device to: receive sidelink position resource signal (SL-PRS) scheduling information for aggregating SL- PRS resources of a plurality of SL-PRS resource pools, wherein the SL-PRS scheduling information is only indicated by a subset of SL-PRS resource pools of the plurality of SL-PRS resource pools; and obtain one or more aggregated measurements of the SL-PRS resources of the plurality of SL-PRS resource pools based on the SL-PRS scheduling information indicated by the subset of SL-PRS resource pools.

[0220] Clause 53. The non-transitory computer-readable medium of clause 52, wherein: the SL- PRS scheduling information is only included in a single SL-PRS resource pool of the plurality of SL-PRS resource pools.

[0221] Clause 54. The non-transitory computer-readable medium of any of clauses 52 to 53, wherein: the SL-PRS scheduling information is indicated in second stage sidelink control information (SCL2) of one or more SL-PRS resource pools of the subset of SL-PRS resource pools.

[0222] Clause 55. The non-transitory computer-readable medium of clause 54, wherein: the SCI- 2 of at least one given SL-PRS resource pool of the one or more SL-PRS resource pools includes an embedded format indicator indicating that SL-PRS of the at least one given SL-PRS resource pool are to be aggregated with SL-PRS of other SL-PRS resource pools of the plurality of SL-PRS resource pools.

[0223] Clause 56. The non-transitory computer-readable medium of any of clauses 54 to 55, wherein: the SL-PRS scheduling information is indicated in the SCI-2 of fewer than all of the subset of SL-PRS resource pools.

[0224] Clause 57. The non-transitory computer-readable medium of clause 56, wherein: the SL- PRS scheduling information is indicated in the SCI-2 of a single SL-PRS resource pool of the plurality of SL-PRS resource pools.

[0225] Clause 58. The non-transitory computer-readable medium of any of clauses 56 to 57, wherein: at least one SL-PRS resource pool of the subset of SL-PRS resource pools includes first stage scheduling information (SCI-1) indicating one or more locations of the SCI-2 in the fewer than all of the subset of SL-PRS resource pools.

[0226] Clause 59. The non-transitory computer-readable medium of any of clauses 56 to 58, wherein: the sidelink device is pre-configured with an indication of one or more locations of the SCI-2 in the fewer than all of the subset of SL-PRS resource pools.

[0227] Clause 60. The non-transitory computer-readable medium of clause 59, wherein: the sidelink device is pre-configured with an indication of one or more locations of the SCI- 2 via Radio Resource Control (RRC) messaging.

[0228] Clause 61. The non -transitory computer-readable medium of any of clauses 52 to 60, wherein: the SL-PRS scheduling information is indicated in first stage sidelink control information (SCI-1) of a single SL-PRS resource pool of the plurality of SL-PRS resource pools.

[0229] Clause 62. The non-transitory computer-readable medium of clause 61, wherein: the SCI- 1 of the single SL-PRS resource pool includes a plurality of fields, wherein the plurality of fields of the SCI-1 are applicable to all of the plurality of SL-PRS resource pools.

[0230] Clause 63. The non-transitory computer-readable medium of any of clauses 61 to 62, wherein: one or more of the plurality of SL-PRS resource pools do not include sidelink control information.

[0231] Clause 64. The non-transitory computer-readable medium of clause 63, The method of claim 12, wherein: the sidelink device is pre-configured to aggregate SL-PRS resources of the plurality of SL-PRS resource pools based on the SCLl of the single SL-PRS resource pool.

[0232] Clause 65. The non-transitory computer-readable medium of any of clauses 61 to 64, wherein: the SL-PRS scheduling information is indicated in the SCLl and second stage sidelink control information (SCL2) of a single SL-resource pool of the subset of SL- resource pools.

[0233] Clause 66. The non-transitory computer-readable medium of any of clauses 52 to 65, wherein: the plurality of SL-PRS resource pools comprise a plurality of dedicated SL- PRS resource pools; and at least one dedicated SL-PRS resource pool of the plurality of dedicated SL-PRS resource pools includes a physical sidelink control channel (PSCCH) having a subchannel index that corresponds to a tuple of SL-PRS resources that are to be aggregated over the plurality of dedicated SL-PRS resource pools.

[0234] Clause 67. The non-transitory computer-readable medium of clause 66, wherein: the subchannel index is directly mapped to resource identifiers corresponding to the tuple of SL-PRS resources.

[0235] Clause 68. The non-transitory computer-readable medium of any of clauses 66 to 67, wherein: the subchannel index is mapped to a resource identifier of a SL-PRS resource of the at least one dedicated SL-PRS resource pool; and the sidelink device is preconfigured to associate a further resource identifier of a further SL-PRS of a further dedicated SL-PRS resource pool for aggregation with the SL-PRS resource of the at least one dedicated SL-PRS resource pool.

[0236] Those of skill in the art will appreciate that information and signals 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 above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0237] Further, those of skill in the art will appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the aspects disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative 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 upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement 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.

[0238] The various illustrative logical blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an ASIC, a field-programable 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 in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0239] The methods, sequences and / or algorithms described in connection with the aspects disclosed herein may be embodied directly in hardware, in a software module executedby a processor, or in a combination of the two. A software module may reside in random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An example storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, 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). In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.

[0240] In one or more example aspects, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. 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 media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can 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 a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0241] While the foregoing disclosure shows illustrative aspects of the disclosure, it should be noted that various changes and modifications could be made herein without departing from the scope of the disclosure as defined by the appended claims. For example, 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, no component, function, action, or instruction described or claimed herein should be construed as critical or essential unless explicitly described as such. Furthermore, as used herein, the terms “set,” “group,” and the like are intended to include one or more of the stated elements. Also, as used herein, the terms “has,” “have,” “having,” “comprises,” “comprising,” “includes,” “including,” and the like does not preclude the presence of one or more additional elements (e.g., an element “having” A may also have B). Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Also, as used herein, the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and / or,” unless explicitly stated otherwise (e.g., if used in combination with “either” or “only one of’) or the alternatives are mutually exclusive (e.g., “one or more” should not be interpreted as “one and more”). Furthermore, although components, functions, actions, and instructions may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated. Accordingly, as used herein, the articles “a,” “an,” “the,” and “said” are intended to include one or more of the stated elements. Additionally, as used herein, the terms “at least one” and “one or more” encompass “one” component, function, action, or instruction performing or capable of performing a described or claimed functionality and also “two or more” components, functions, actions, or instructions performing or capable of performing a described or claimed functionality in combination.

Claims

CLAIMSWhat is claimed is:

1. A method of wireless communication performed by a sidelink device, comprising: receiving sidelink position resource signal (SL-PRS) scheduling information for aggregating SL-PRS resources of a plurality of SL-PRS resource pools, wherein the SL- PRS scheduling information is only indicated by a subset of SL-PRS resource pools of the plurality of SL-PRS resource pools; and obtaining one or more aggregated measurements of the SL-PRS resources of the plurality of SL-PRS resource pools based on the SL-PRS scheduling information indicated by the subset of SL-PRS resource pools.

2. The method of claim 1, wherein: the SL-PRS scheduling information is only included in a single SL-PRS resource pool of the plurality of SL-PRS resource pools.

3. A sidelink device, comprising: one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors, either alone or in combination, configured to: receive, via the one or more transceivers, sidelink position resource signal (SL-PRS) scheduling information for aggregating SL-PRS resources of a plurality of SL-PRS resource pools, wherein the SL-PRS scheduling information is only indicated by a subset of SL-PRS resource pools of the plurality of SL- PRS resource pools; and obtain one or more aggregated measurements of the SL-PRS resources of the plurality of SL-PRS resource pools based on the SL-PRS scheduling information indicated by the subset of SL-PRS resource pools.

4. The sidelink device of claim 3, wherein: the SL-PRS scheduling information is only included in a single SL-PRS resource pool of the plurality of SL-PRS resource pools.

5. The sidelink device of claim 3, wherein: the SL-PRS scheduling information is indicated in second stage sidelink control information (SCL2) of one or more SL-PRS resource pools of the subset of SL-PRS resource pools.

6. The sidelink device of claim 5, wherein: the SCI-2 of at least one given SL-PRS resource pool of the one or more SL- PRS resource pools includes an embedded format indicator indicating that SL-PRS of the at least one given SL-PRS resource pool are to be aggregated with SL-PRS of other SL-PRS resource pools of the plurality of SL-PRS resource pools.

7. The sidelink device of claim 5, wherein: the SL-PRS scheduling information is indicated in the SCI-2 of fewer than all of the subset of SL-PRS resource pools.

8. The sidelink device of claim 7, wherein: the SL-PRS scheduling information is indicated in the SCI-2 of a single SL-PRS resource pool of the plurality of SL-PRS resource pools.

9. The sidelink device of claim 7, wherein: at least one SL-PRS resource pool of the subset of SL-PRS resource pools includes first stage scheduling information (SCL1) indicating one or more locations of the SCI-2 in the fewer than all of the subset of SL-PRS resource pools.

10. The sidelink device of claim 7, wherein: the sidelink device is pre-configured with an indication of one or more locations of the SCI-2 in the fewer than all of the subset of SL-PRS resource pools.

11. The sidelink device of claim 10, wherein: the sidelink device is pre-configured with an indication of one or more locations of the SCI-2 via Radio Resource Control (RRC) messaging.

12. The sidelink device of claim 3, wherein: the SL-PRS scheduling information is indicated in first stage sidelink control information (SCI-1) of a single SL-PRS resource pool of the plurality of SL-PRS resource pools.

13. The sidelink device of claim 12, wherein: the SCI-1 of the single SL-PRS resource pool includes a plurality of fields, wherein the plurality of fields of the SCI-1 are applicable to all of the plurality of SL- PRS resource pools.

14. The sidelink device of claim 12, wherein: one or more of the plurality of SL-PRS resource pools do not include sidelink control information.

15. The sidelink device of claim 14, wherein: the sidelink device is pre-configured to aggregate SL-PRS resources of the plurality of SL-PRS resource pools based on the SCI-1 of the single SL-PRS resource pool.

16. The sidelink device of claim 12, wherein: the SL-PRS scheduling information is indicated in the SCLl and second stage sidelink control information (SCL2) of a single SL-resource pool of the subset of SL- resource pools.

17. The sidelink device of claim 3, wherein: the plurality of SL-PRS resource pools comprise a plurality of dedicated SL- PRS resource pools; and at least one dedicated SL-PRS resource pool of the plurality of dedicated SL- PRS resource pools includes a physical sidelink control channel (PSCCH) having a subchannel index that corresponds to a tuple of SL-PRS resources that are to be aggregated over the plurality of dedicated SL-PRS resource pools.

18. The sidelink device of claim 17, wherein: the subchannel index is directly mapped to resource identifiers corresponding to the tuple of SL-PRS resources.

19. The sidelink device of claim 17, wherein: the subchannel index is mapped to a resource identifier of a SL-PRS resource of the at least one dedicated SL-PRS resource pool; and the sidelink device is preconfigured to associate a further resource identifier of a further SL-PRS of a further dedicated SL-PRS resource pool for aggregation with the SL-PRS resource of the at least one dedicated SL-PRS resource pool.

20. A sidelink device, comprising: means for receiving sidelink position resource signal (SL-PRS) scheduling information for aggregating SL-PRS resources of a plurality of SL-PRS resource pools, wherein the SL-PRS scheduling information is only indicated by a subset of SL-PRS resource pools of the plurality of SL-PRS resource pools; and means for obtaining one or more aggregated measurements of the SL-PRS resources of the plurality of SL-PRS resource pools based on the SL-PRS scheduling information indicated by the subset of SL-PRS resource pools.

Images