Sidelink congestion control metrics for sidelink localization of user equipment with reduced capabilities

Abstract

A user equipment (UE) receives a configuration for sidelink positioning reference signal (SL-PRS) resources within a sidelink resource pool, wherein the configuration indicates a plurality of SL-PRS frequency hops for the SL-PRS resources, and wherein each SL-PRS frequency hop has a bandwidth less than the total bandwidth of the sidelink resource pool; determines one or more congestion control metrics for each SL-PRS frequency hop subset of the plurality of SL-PRS frequency hops; determines one or more SL-PRS transmission attributes for the SL-PRS frequency hop based at least in part on the one or more congestion control metrics determined for each SL-PRS frequency hop subset of the SL-PRS frequency hops; and transmits SL-PRS resources on the plurality of SL-PRS frequency hops according to the one or more SL-PRS transmission attributes for each SL-PRS frequency hop subset of the SL-PRS frequency hops.

Description

Background Technology 1. Technical Field

[0002] All aspects of this disclosure relate to wireless communications.

[0003] 2. Relevant Technical Descriptions

[0004] Wireless communication systems have evolved through many generations, including first-generation analog radiotelephone service (1G), second-generation (2G) digital radiotelephone service (including transitional 2.5G and 2.75G networks), third-generation (3G) high-speed data, wireless services with internet capabilities, and fourth-generation (4G) services (e.g., Long Term Evolution (LTE) or WiMax). Currently, many different types of wireless communication systems are in use, including cellular systems and Personal Communication Services (PCS) systems. Known examples of cellular systems include cellular analog Advanced Mobile Phone Systems (AMPS), as well as digital cellular systems based on Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Global System for Mobile Communications (GSM), and others.

[0005] The fifth-generation (5G) wireless standard, known as New Radio (NR), delivers higher data speeds, more connections, better coverage, and other improvements. According to the Next Generation Mobile Networks Alliance, the 5G standard is designed to provide higher data rates, more accurate positioning (e.g., based on positioning reference signals (RS-P), such as downlink, uplink, or sidelink positioning reference signals (PRS)), and other technological enhancements compared to previous standards.

[0006] Furthermore, leveraging 5G's increased data rates and reduced latency, vehicle-to-everything (V2X) communication technology is being implemented to support autonomous driving applications, such as wireless communication between vehicles, between vehicles and roadside infrastructure, and between vehicles and pedestrians. Summary of the Invention

[0007] The following is a simplified summary of the invention relating to one or more aspects disclosed herein. Therefore, this summary should not be considered an exhaustive overview relating to all conceived aspects, nor should it be considered to identify key or decisive elements relating to all conceived aspects or to depict the scope associated with any particular aspect. Thus, the sole purpose of this summary is to present, in a simplified form, certain concepts relating to one or more aspects involving the mechanisms disclosed herein, prior to the detailed description presented below.

[0008] In one aspect, a method of wireless communication performed by a user equipment (UE) includes: receiving a configuration for sidelink positioning reference signal (SL-PRS) resources within a sidelink resource pool, wherein the configuration indicates a plurality of SL-PRS frequency hops of the SL-PRS resources, and wherein each of the plurality of SL-PRS frequency hops has a bandwidth less than the total bandwidth of the sidelink resource pool; determining one or more congestion control metrics for each SL-PRS frequency hop in at least a subset of the plurality of SL-PRS frequency hops; determining one or more SL-PRS transmission attributes for each SL-PRS frequency hop based at least in part on the one or more congestion control metrics determined for each SL-PRS frequency hop in the subset of SL-PRS frequency hops; and transmitting SL-PRS resources on the plurality of SL-PRS frequency hops according to the one or more SL-PRS transmission attributes for each SL-PRS frequency hop in the subset of SL-PRS frequency hops.

[0009] In one aspect, a user equipment (UE) 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, wherein the one or more processors are individually or in combination configured to: receive via the one or more transceivers a configuration for sidelink positioning reference signal (SL-PRS) resources within a sidelink resource pool, wherein the configuration indicates a plurality of SL-PRS frequency hops of the SL-PRS resources, and wherein each of the plurality of SL-PRS frequency hops has a bandwidth less than the total bandwidth of the sidelink resource pool; For each SL-PRS frequency hop in at least a subset of SL-PRS frequency hops, determine one or more congestion control metrics; determine one or more SL-PRS transmission attributes for each SL-PRS frequency hop based at least in part on the one or more congestion control metrics determined for each SL-PRS frequency hop in the subset of SL-PRS frequency hops; and transmit SL-PRS resources on the multiple SL-PRS frequency hops via one or more transceivers according to the one or more SL-PRS transmission attributes for each SL-PRS frequency hop in the subset of SL-PRS frequency hops.

[0010] In one aspect, a user equipment (UE) includes: components for receiving configuration for sidelink positioning reference signal (SL-PRS) resources within a sidelink resource pool, wherein the configuration indicates a plurality of SL-PRS frequency hops of the SL-PRS resources, and wherein each of the plurality of SL-PRS frequency hops has a bandwidth less than the total bandwidth of the sidelink resource pool; components for determining one or more congestion control metrics for each SL-PRS frequency hop in at least a subset of the plurality of SL-PRS frequency hops; components for determining one or more SL-PRS transmission attributes for each SL-PRS frequency hop based at least in part on the one or more congestion control metrics determined for each SL-PRS frequency hop in the subset of SL-PRS frequency hops; and components for transmitting SL-PRS resources on the plurality of SL-PRS frequency hops according to the one or more SL-PRS transmission attributes for each SL-PRS frequency hop in the subset of SL-PRS frequency hops.

[0011] In one aspect, a non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a user equipment (UE), cause the UE to: receive a configuration for sidelink positioning reference signal (SL-PRS) resources within a sidelink resource pool, wherein the configuration indicates a plurality of SL-PRS frequency hops of the SL-PRS resources, and wherein each of the plurality of SL-PRS frequency hops has a bandwidth less than the total bandwidth of the sidelink resource pool; determine one or more congestion control metrics for each SL-PRS frequency hop in at least a subset of the plurality of SL-PRS frequency hops; determine one or more SL-PRS transmission attributes for each SL-PRS frequency hop based at least in part on the one or more congestion control metrics determined for each SL-PRS frequency hop in the subset of SL-PRS frequency hops; and transmit SL-PRS resources on the plurality of SL-PRS frequency hops according to the one or more SL-PRS transmission attributes for each SL-PRS frequency hop in the subset of SL-PRS frequency hops.

[0012] Based on the accompanying drawings and detailed description, other objects and advantages associated with the aspects disclosed herein will be apparent to those skilled in the art. Attached Figure Description

[0013] The accompanying drawings are provided to help describe various aspects of this disclosure, and are provided for illustrative purposes only and not to limit the aspects.

[0014] Figure 1 Example wireless communication systems according to various aspects of this disclosure are illustrated.

[0015] Figure 2A , Figure 2B and Figure 2C Example wireless network architectures based on various aspects of this disclosure are illustrated.

[0016] Figure 3A , Figure 3B and Figure 3C It is a simplified block diagram of several examples of components that can be used in user equipment (UE), base stations and network entities and configured to support communications as taught herein.

[0017] Figure 4A and Figure 4B Various scenarios of interest are illustrated according to aspects of this disclosure, including sidelink-only localization or combined Uu and sidelink localization.

[0018] Figure 5 This is a diagram illustrating an example sidelink ranging and positioning process according to various aspects of this disclosure.

[0019] Figure 6A and Figure 6B This is a diagram illustrating example sidelink time slot structures with and without feedback resources according to various aspects of this disclosure.

[0020] Figures 7A to 7D This is a diagram illustrating an example of a resource pool for positioning according to various aspects of this disclosure.

[0021] Figure 8A and Figure 8B An example set of aggregated sidelink resource pools for positioning is illustrated according to various aspects of this disclosure.

[0022] Figure 9 This is a diagram illustrating an example of the overlapping bandwidth between transitions according to various aspects of this disclosure.

[0023] Figure 10 This is a diagram illustrating an example of the switching gap between transitions according to various aspects of this disclosure.

[0024] Figure 11 This is a diagram illustrating an example of a UE performing six frequency hoppings for a side-link positioning reference signal (SL-PRS) positioning use case according to various aspects of this disclosure.

[0025] Figure 12 This is a diagram illustrating an example of calculating a single-hop-based SL-PRS congestion control metric according to various aspects of this disclosure.

[0026] Figure 13 This is a diagram illustrating an example of calculating a multi-hop-based SL-PRS congestion control metric according to various aspects of this disclosure.

[0027] Figure 14A and Figure 14B An example of SL-PRS resource transmission based on multi-hop-based SL-PRS congestion control metric calculation is illustrated according to various aspects of this disclosure.

[0028] Figure 15 Example methods of wireless communication according to various aspects of this disclosure are illustrated. Detailed Implementation

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

[0030] The overall scope involves wireless communication. Some aspects are more specifically related to sidelink positioning using frequency hopping. In some examples, the user equipment (UE) performs sensing only on a subset of frequency hops within a plurality of frequency hops used for sidelink positioning reference signal (SL-PRS) positioning. The UE may also perform channel busy ratio (CBR) and channel occupancy ratio (CR) calculations only on the frequency hop subset. In some cases, CBR and CR calculations are performed independently for each sidelink resource pool.

[0031] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, by performing sensing only on a subset of frequency hops, the described techniques can be used to reduce the number of frequency hops that the UE would need to sense (e.g., call-in and call-out) in order to transmit SL-PRS.

[0032] The terms “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 superior to or better than other aspects. Similarly, the term “aspects of this disclosure” does not require that all aspects of this disclosure include the features, advantages, or modes of operation discussed.

[0033] Those skilled in the art will understand that any of a variety of different techniques and methods can be used to represent the information and signals described below. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the following description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof, depending in part on the specific application, in part on the desired design, in part on the corresponding technology, and so on.

[0034] Furthermore, many aspects are described according to a sequence of actions to be performed by elements of, for example, a computing device. It will be appreciated that the various actions described herein can be performed by specific circuitry (e.g., an application-specific integrated circuit (ASIC)), by program instructions executed by one or more processors, or by a combination of both. Additionally, the sequence of actions described herein can be considered to be entirely embodied in any form of non-transitory computer-readable storage medium storing a corresponding set of computer instructions that, when executed, will cause or command the associated processor of the device to perform the functionality described herein. Therefore, various aspects of this disclosure can be embodied in a variety of different forms, all of which are contemplated within the scope of the claimed subject matter. Furthermore, for each aspect described herein, any corresponding form of any such aspect may be described herein as, for example, "logic configured to perform the described actions."

[0035] 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 to or otherwise limited to any particular radio access technology (RAT) unless otherwise stated. In general, a UE can be any wireless communication device used by a user to communicate over a wireless communication network (e.g., vehicle onboard computer, vehicle navigation device, mobile phone, router, tablet computer, laptop computer, asset location device, wearable device (e.g., smartwatch, glasses, augmented reality (AR) / virtual reality (VR) headset, etc.), vehicle (e.g., car, motorcycle, bicycle, etc.), Internet of Things (IoT) device, etc.). A UE can be mobile or can (e.g., at certain times) be stationary and can communicate with a radio access network (RAN). As used herein, the term “UE” can be interchangeably referred to as “mobile device,” “access terminal” or “AT,” “client device,” “wireless device,” “subscriber equipment,” “subscriber terminal,” “subscriber station,” “user terminal” or UT,” “mobile terminal,” “mobile station,” or variations thereof.

[0036] V-UE is a type of UE and can be any in-vehicle wireless communication device, such as a navigation system, alarm system, head-up display (HUD), onboard computer, in-vehicle infotainment system, automated driving system (ADS), advanced driver assistance system (ADAS), etc. Alternatively, V-UE can be a portable wireless communication device (e.g., cellular phone, tablet computer, etc.) carried by the driver or occupant of a vehicle. The term "V-UE" can refer to the in-vehicle wireless communication device or the vehicle itself, depending on the context. P-UE is a type of UE and can be a portable wireless communication device carried by a pedestrian (i.e., a user who is not driving or riding in a vehicle). Generally, the UE can communicate with the core network via the RAN, and through the core network, the UE can connect to external networks such as the Internet and to other UEs. Of course, other mechanisms for connecting to the core network and / or the Internet are also possible for the UE, such as through wired access networks, wireless local area network (WLAN) networks (e.g., based on IEEE 802.11, etc.).

[0037] A base station can communicate with a UE by operating under one of several RATs based on the network in which it is deployed, and may alternatively be referred to as an Access Point (AP), Network Node, Node B, Evolved Node B (eNB), Next Generation eNB (ng-eNB), New Radio (NR) Node B (also known as gNB or gNodeB), etc. The base station is primarily used to support the UE's radio access, including supporting the UE's data, voice, and / or signaling connections. In some systems, the base station may only provide edge node signaling functions, while in others, it may provide additional control and / or network management functions. The communication link through which the UE can transmit signals to the base station is called an uplink (UL) channel (e.g., reverse traffic channel, reverse control channel, access channel, etc.). The communication link through which the base station can transmit signals to the UE is called a downlink (DL) or forward link channel (e.g., paging channel, control channel, broadcast channel, forward traffic channel, etc.). As used herein, the term Traffic Channel (TCH) may refer to either the UL / reverse or DL / forward traffic channel.

[0038] The term "base station" can refer to a single physical transmit / receive point (TRP) or multiple physical TRPs that may or may not be co-located. For example, when the term "base station" refers to a single physical TRP, the physical TRP can be the antenna of a base station corresponding to a cell (or several cell sectors) of the base station. When the term "base station" refers to multiple co-located physical TRPs, the physical TRP can be the antenna array of the base station (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming). When the term "base station" refers to multiple non-co-located physical TRPs, the physical TRP can be a distributed antenna system (DAS) (a network of spatially separated antennas connected via a transmission medium to a common source) or a remote radio headend (RRH) (a remote base station connected to a serving base station). Alternatively, a non-co-located physical TRP can be the serving base station from which the UE receives measurement reports and a neighboring base station where the UE is measuring its reference radio frequency (RF) signal. Because, as used herein, a TRP is the point by which a base station transmits and receives radio signals, references to transmitting from or receiving at a base station should be understood to refer to a specific TRP of the base station.

[0039] In some specific implementations supporting UE positioning, the base station may not support the UE's radio access (e.g., it may not support the UE's data, voice, and / or signaling connections). Instead, it may send a reference RF signal to the UE for measurement by the UE, and / or receive and measure signals sent by the UE. Such a base station may be referred to as a positioning beacon (e.g., in the case of sending RF signals to the UE) and / or as a location measurement unit (e.g., in the case of receiving and measuring RF signals from the UE).

[0040] An “RF signal” refers to an electromagnetic wave of a given frequency that transmits information across the space between a transmitter and a receiver. As used herein, a transmitter may send a single “RF signal” or multiple “RF signals” to a receiver. However, due to the propagation characteristics of RF signals through multipath channels, a receiver may receive multiple “RF signals” corresponding to each transmitted RF signal. 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 the context clearly indicates that the term “signal” refers to a wireless signal or an RF signal.

[0041] Figure 1An example wireless communication system 100 according to various aspects of this disclosure is illustrated. The wireless communication system 100 (which may also be referred to as a wireless wide area network (WWAN)) may include various base stations 102 (labeled "BS") and various UEs 104. Base station 102 may include macro cell base stations (high-power cellular base stations) and / or small cell base stations (low-power cellular base stations). In one aspect, macro cell base station 102 may include eNB and / or ng-eNB (wherein wireless communication system 100 corresponds to an LTE network) or gNB (wherein wireless communication system 100 corresponds to an NR network) or a combination of both, and small cell base stations may include femtocells, picocells, microcells, etc.

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

[0043] In addition to other functions, base station 102 may perform functions associated with one or more of the following: transmitting user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of Non-Access Stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, Multimedia Broadcast Multicast Service (MBMS), subscriber and equipment tracking, RAN Information Management (RIM), paging, location, and delivery of warning messages. Base stations 102 may communicate with each other directly or indirectly (e.g., via EPC / 5GC) on backhaul link 134, which may be wired or wireless.

[0044] Base station 102 can wirelessly communicate with UE 104. Each base station in base station 102 can provide communication coverage for a corresponding geographic coverage area 110. In one aspect, one or more cells can be supported by base station 102 in each geographic coverage area 110. A “cell” is a logical communication entity used to communicate with a base station (e.g., via a frequency resource, which is referred to as a carrier frequency, component carrier, carrier, frequency band, etc.) and can be associated with an identifier (e.g., Physical Cell Identifier (PCI), Enhanced Cell Identifier (ECI), Virtual Cell Identifier (VCI), Cell Global Identifier (CGI), etc.) used to distinguish cells operating via the same or different carrier frequencies. In some cases, different cells can be configured according to different protocol types that can provide access for different types of UEs (e.g., Machine Type Communication (MTC), Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB), or other protocol types). Because a cell is supported by a specific base station, the term “cell” can refer to one or both of the logical communication entity and the base station that supports it, depending on the context. In some cases, the term "cell" can also refer to the geographic coverage area of ​​a base station (e.g., a sector), as long as the carrier frequency can be detected and used for communication within a portion of the geographic coverage area 110.

[0045] While the geographic coverage areas 110 of adjacent macro cell base stations 102 may partially overlap (e.g., in handover areas), some areas within geographic coverage areas 110 may substantially overlap with larger geographic coverage areas 110. For example, a small cell base station 102' (labeled "SC" for "small cell") may have a geographic coverage area 110' that substantially overlaps with the geographic coverage areas 110 of one or more macro cell base stations 102. A network that includes both small cell base stations and macro cell base stations can be referred to as a heterogeneous network. A heterogeneous network may also include a home eNB (HeNB) that can provide service to a restricted group referred to as a Closed Subscriber Group (CSG).

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

[0047] The wireless communication system 100 may also include a WLAN access point (AP) 150 that communicates with a wireless local area network (WLAN) station (STA) 152 via a communication link 154 in unlicensed spectrum (e.g., 5 GHz). When communicating in unlicensed spectrum, the WLAN STA 152 and / or WLAN AP 150 may perform a free channel assessment (CCA) or listen-before-talk (LBT) process before communication to determine whether the channel is available.

[0048] Small cell base station 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, small cell base station 102' can employ LTE or NR technology and use the same 5GHz unlicensed spectrum as WLAN AP 150. Small cell base station 102' employing LTE / 5G in unlicensed spectrum can improve the coverage and / or increase the capacity of the access network. NR in unlicensed spectrum may be referred to as NR-U. LTE in unlicensed spectrum may be referred to as LTE-U, Licensed Assisted Access (LAA), or MULTEFIRE. ® .

[0049] The wireless communication system 100 may also include an mmW base station 180, which can operate in millimeter-wave (mmW) frequencies and / or near-mmW frequencies to communicate with the UE 182. Extremely high frequency (EHF) is a portion of the electromagnetic spectrum that contains radio frequency (RF). EHF has a range of 30 GHz to 300 GHz, with wavelengths between 1 mm and 10 mm. Radio waves in this band are referred to as millimeter waves. Near-mmW extends down to frequencies of 3 GHz with wavelengths of 100 mm. Ultra-high frequency (SHF) bands extend between 3 GHz and 30 GHz, and are also referred to as centimeter waves. Communication using mmW / near-mmW radio bands has high path loss and relatively short range. The mmW base station 180 and the UE 182 can utilize beamforming (transmit and / or receive) on the mmW communication link 184 to compensate for the extremely high path loss and short range. Furthermore, it should be understood that in alternative configurations, one or more base stations 102 may also use mmW or near-mmW and beamforming for transmission. Therefore, it should be understood that the foregoing examples are merely illustrative and should not be construed as limiting the various aspects disclosed herein.

[0050] Transmit beamforming is a technique used to focus RF signals 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 (omnidirectionally). Using 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, thus providing the receiving device with a faster and stronger RF signal (in terms of data rate). To change the directivity of the RF signal during transmission, the network node can control the phase and relative amplitude of the RF signal at each of one or more transmitters broadcasting the RF signal. For example, the network node can use an array of antennas (called a "phased array" or "antenna array") that forms an RF beam that can be "manipulated" to be pointed in different directions without actually moving the antennas. Specifically, RF currents from the transmitters are fed to individual antennas with the correct phase relationship, such that radio waves from the individual antennas add up in the desired direction to increase radiation, while canceling out in the undesired direction to suppress radiation.

[0051] Transmit beams can be quasi-co-located, meaning they appear to the receiver (e.g., the UE) as having the same parameters regardless of whether the network node's own transmit antennas are physically co-located. In NR, there are four types of quasi-co-located (QCL) relationships. Specifically, a given type of QCL relationship means that certain parameters of a second reference RF signal on a second beam can be derived based on information about the source reference RF signal on the source beam. Therefore, if the source reference RF signal is QCL type A, the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, average delay, and delay spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type B, the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of the second reference RF signal transmitted on the same channel. If the source reference RF signal is QCL type C, the receiver can use the source reference RF signal to estimate the Doppler shift and average delay of the second reference RF signal transmitted on the same channel. If the source reference RF signal is of type QCL D, the receiver can use the source reference RF signal to estimate the spatial reception parameters of a second reference RF signal transmitted on the same channel.

[0052] In receive beamforming, a receiver uses a receive beam to amplify an RF signal detected on a given channel. For example, the receiver may increase the gain setting of an antenna array in a particular direction and / or adjust the phase setting of the antenna array in a particular direction to amplify the RF signal received from that direction (e.g., increase its gain level). Therefore, when a receiver is described as performing beamforming in a certain direction, it means that the beam gain in that direction is high relative to the beam gain along other directions, or that the beam gain in that direction is the highest compared to the beam gain of all other receive beams available to the receiver in that direction. 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 signal received from that direction.

[0053] The transmit and receive beams can be spatially correlated. Spatial correlation means that parameters for a second beam (e.g., transmit or receive beam) for a second reference signal can be derived based on information about a first beam (e.g., receive or transmit beam) for a first reference signal. For example, a UE can use a specific receive beam to receive a reference downlink reference signal (e.g., a synchronization signal block (SSB)) from a base station. The UE can then form a transmit beam for transmitting an uplink reference signal (e.g., a sounding reference signal (SRS)) to that base station based on the parameters of the receive beam.

[0054] It is important to note that, depending on the entity forming the "downlink" beam, the beam can be either a transmit beam or a receive beam. For example, if the base station is forming a downlink beam to transmit a reference signal to the UE, the downlink beam is a transmit beam. However, if the UE is forming a downlink beam, the downlink beam is a receive beam for receiving the downlink reference signal. Similarly, depending on the entity forming the "uplink" beam, the beam can be either a transmit beam or a receive beam. For example, if the base station is forming an uplink beam, the uplink beam is an uplink receive beam, while if the UE is forming an uplink beam, the uplink beam is an uplink transmit beam.

[0055] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz to 7.125GHz) and FR2 (24.25GHz to 52.6GHz). It should be understood that although a portion of FR1 is greater than 6GHz, in various documents and articles, FR1 is often (interchangeably) referred to as the "sub-6GHz" band. A similar naming issue sometimes occurs with FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although this differs from the designation used by the International Telecommunication Union.® Extremely high frequency (EHF) bands (30 GHz to 300 GHz) are designated as “millimeter wave” bands.

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

[0057] In light of the foregoing, unless otherwise specifically stated, it should be understood that, as used herein, the term "below 6 GHz" and the like can broadly refer to frequencies less than 6 GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise specifically stated, it should be understood that, as used herein, the term "millimeter wave" and the like can broadly refer to frequencies that can include intermediate frequency band frequencies, within FR2, FR4, FR4-a or FR4-1 and / or FR5, or within the EHF band.

[0058] In multi-carrier systems such as 5G, one of the carrier frequencies is referred to as the "primary carrier," "anchor carrier," "primary serving cell," or "PCell," and the remaining carrier frequencies are referred to as "secondary carriers," "secondary serving cells," or "SCell." In carrier aggregation, the anchor carrier is the carrier operating on the primary frequency (e.g., FR1) used by UE 104 / 182 and the cell, where UE 104 / 182 performs an initial Radio Resource Control (RRC) connection establishment procedure or initiates an RRC connection re-establishment procedure. The primary carrier carries all common and UE-specific control channels and can be a carrier on a licensed frequency (however, this is not always the case). The secondary carrier is a carrier operating on a second frequency (e.g., FR2) that can be configured and used to provide additional radio resources once an RRC connection is established between UE 104 and the anchor carrier. In some cases, the secondary carrier can be a carrier on an unlicensed frequency. Secondary carriers may contain only the necessary signaling information and signals. For example, since the primary uplink and primary downlink carriers are typically UE-specific, the UE-specific signaling information and signals may not be present in the secondary carrier. This means that different UEs 104 / 182 within a cell can have different downlink primary carriers. The same applies to the uplink primary carrier. The network can change the primary carrier of any UE 104 / 182 at any time. This is done, for example, to balance the load on different carriers. Since a "serving cell" (whether PCell or SCell) corresponds to the carrier frequency / component carrier through which a base station communicates, the terms "cell," "serving cell," "component carrier," and "carrier frequency" can be used interchangeably.

[0059] For example, still refer to Figure 1 One of the frequencies used by macro cell base station 102 can be an anchor carrier (or "PCell"), and the other frequencies used by macro cell base station 102 and / or mmW base station 180 can be secondary carriers ("SCell"). Simultaneous transmission and / or reception on multiple carriers allows UE 104 / 182 to significantly increase its data transmission and / or reception rates. For example, compared to the data rate obtained by a single 20MHz carrier, two aggregated 20MHz carriers in a multi-carrier system would theoretically result in a doubling of the data rate (i.e., 40MHz).

[0060] exist Figure 1 In the example, the UE shown (for simplicity, in) Figure 1Any UE (shown as a single UE 104) can receive signal 124 from one or more Earth-orbiting spacecraft (SV) 112 (e.g., satellites). In one aspect, SV 112 may be part of a satellite positioning system that allows UE 104 to use as an independent source of location information. Satellite positioning systems typically include a system of transmitters (e.g., SV 112) positioned such that a receiver (e.g., UE 104) can determine its location on or above the Earth based at least in part on positioning signals (e.g., signal 124) received from the transmitters. Such transmitters typically transmit signals marked with a set number of repeating pseudo-random noise (PN) codes. While typically located in SV 112, transmitters may sometimes be located at ground-based control stations, base stations 102, and / or other UEs 104. UE 104 may include one or more dedicated receivers specifically designed to receive signal 124 in order to derive geographic location information from SV 112.

[0061] In a satellite positioning system, the use of signal 124 can be enhanced by various satellite-based augmentation systems (SBAS), which may be associated with or otherwise made capable of being used with one or more global and / or regional navigation satellite systems. For example, SBAS may include augmentation systems that provide integrity information, differential correction, etc., such as Wide Area Augmentation System (WAAS), European Geostationary Navigation Overlap Service (EGNOS), Multifunctional Satellite Augmentation System (MSAS), GPS-assisted geographic augmentation navigation, or GPS and geographic augmentation navigation system (GAGAN). Therefore, 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.

[0062] On one hand, SV 112 may additionally or alternatively be part of one or more non-terrestrial networks (NTNs). In an NTN, SV 112 connects to an earth station (also referred to as a ground station, NTN gateway, or gateway), which in turn connects to elements in the 5G network, such as a modified base station 102 (without a ground antenna) or a network node in a 5GC. This element, in turn, provides access to other elements in the 5G network and ultimately to entities outside the 5G network, such as internet web servers and other user equipment. Thus, as a replacement or supplement to communication signals from ground base station 102, UE 104 can receive communication signals (e.g., signal 124) from SV 112.

[0063] Leveraging the increased data rates and reduced latency of NR (Radio Frequency I / O), vehicle-to-everything (V2X) communication technology is being implemented to support Intelligent Transportation Systems (ITS) applications, such as wireless communication between vehicles (V2V), between vehicles and roadside infrastructure (V2I), and between vehicles and pedestrians (V2P). The goal is to enable vehicles to sense their surroundings and communicate that information to other vehicles, infrastructure, and personal mobile devices. This type of vehicle communication will achieve safety, mobility, and environmental improvements that current technologies cannot provide. Once fully realized, this technology is expected to reduce collisions involving undamaged vehicles by 80%.

[0064] Still referencing Figure 1 The wireless communication system 100 may include multiple V-UEs 160, which can communicate with base station 102 on communication link 120 using a Uu interface (i.e., the air interface between the UE and the base station). V-UEs 160 can also communicate directly with each other on wireless sidelink 162, with roadside unit (RSU) 164 (roadside access point) on wireless sidelink 166, or with sidelink-capable UE 104 on wireless sidelink 168 using a PC5 interface (i.e., the air interface between UEs with sidelink capability). A wireless sidelink (or simply "sidelink") is an adaptation of core cellular network (e.g., LTE, NR) standards that allows direct communication between two or more UEs without requiring communication through a base station. Sidelink communication can be unicast or multicast and can be used for device-to-device (D2D) media sharing, V2V communication, V2X communication (e.g., cellular V2X (cV2X) communication, enhanced V2X (eV2X) communication, emergency rescue applications, etc. One or more V-UEs in a group of V-UEs 160 utilizing sidelink communication may be within the geographic coverage area 110 of base station 102. Other V-UEs 160 in such a group may be outside the geographic coverage area 110 of base station 102, or may be unable to receive transmissions from base station 102 for other reasons. In some cases, the groups of V-UEs 160 communicating via sidelink communication may utilize a one-to-many (1:M) system, where each V-UE 160 transmits to every other V-UE 160 in the group. In some cases, base station 102 facilitates the scheduling of resources for sidelink communication. In other cases, sidelink communication is performed between V-UEs 160 without involving base station 102.

[0065] On one hand, sidelinks 162, 166, and 168 can operate via a wireless communication medium of interest, which can be shared with other vehicles and / or infrastructure access points and other wireless communications between other RATs. “Medium” can include one or more time, frequency, and / or space communication resources (e.g., covering one or more channels across one or more carriers) associated with wireless communication between one or more transmitter / receiver pairs.

[0066] On one hand, sidelinks 162, 166, and 168 can be cV2X links. First-generation 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 communication. In the United States and Europe, cV2X is expected to operate in licensed ITS bands below 6 GHz. Other bands may be allocated in other countries. Therefore, as a specific example, the medium of interest utilized by sidelinks 162, 166, and 168 may correspond to at least a portion of licensed ITS bands below 6 GHz. However, this disclosure is not limited to this band or cellular technology.

[0067] On one hand, sidelinks 162, 166, and 168 can be Dedicated Short-Range Communications (DSRC) links. DSRC is a one-way or two-way short-to-medium-range wireless communication protocol that uses the Vehicle Environment Wireless Access (WAVE) protocol (also known as IEEE 802.11p) for V2V, V2I, and V2P communications. IEEE 802.11p is an approved modification of the IEEE 802.11 standard and operates in the licensed ITS band of 5.9 GHz (5.85 GHz to 5.925 GHz) in the United States. In Europe, IEEE 802.11p operates in the ITS G5A band (5.875 GHz to 5.905 MHz). Other bands may be allocated in other countries. The V2V communications briefly described above occur on a secure channel, which in the United States is typically a 10 MHz channel dedicated to security purposes. The remainder of the DSRC band (total bandwidth of 75MHz) is intended for other services of interest to drivers, such as road rules, toll collection, parking automation, etc. Therefore, as a specific example, the media of interest utilized by side links 162, 166, and 168 may correspond to at least a portion of the licensed ITS band at 5.9GHz.

[0068] Alternatively, the medium of interest may correspond to at least a portion of unlicensed frequency bands shared among various RATs. While different licensed frequency bands have been reserved for certain communication systems (e.g., by government entities such as the U.S. Federal Communications Commission (FCC), these systems (particularly those employing small cell access points) have recently expanded their operations to unlicensed National Information Infrastructure (U-NII) bands used by wireless local area network (WLAN) technologies, most notably the IEEE 802.11x WLAN technology commonly referred to as "Wi-Fi"). Example systems of this type include various variants of CDMA, TDMA, FDMA, orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), and so on.

[0069] Communication between V-UEs 160 is referred to as V2V communication, communication between V-UE 160 and one or more RSUs 164 is referred to as V2I communication, and communication between V-UE 160 and one or more UEs 104 (where these UEs 104 are P-UEs) is referred to as V2P communication. V2V communication between V-UEs 160 may include information such as the location, speed, acceleration, heading, and other vehicle data of these V-UEs 160. 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. V2P communication between V-UE 160 and UE 104 may include information such as the location, speed, acceleration, and heading of V-UE 160, and the location, speed (e.g., in the case where UE 104 is carried by a cyclist), and heading of UE 104.

[0070] It should be noted that, although Figure 1 Only two UEs in the UE list are exemplified as V-UEs (V-UE 160), but any UE in the exemplified UEs (e.g., UE 104, 152, 182, 190) can be V-UEs. Furthermore, although only these V-UEs 160 and a single UE 104 have been exemplified as connected via a sidelink, Figure 1Any of the illustrated UEs, whether V-UE, P-UE, etc., may be capable of sidelink communication. Furthermore, although only UE 182 is described as capable of beamforming, any of the illustrated UEs (including V-UE 160) may be capable of beamforming. When V-UE 160 is capable of beamforming, it can beamform towards each other (i.e., towards other V-UEs 160), towards RSU 164, towards other UEs (e.g., UEs 104, 152, 182, 190), etc. Therefore, in some cases, V-UE 160 may utilize beamforming on sidelinks 162, 166, and 168.

[0071] The wireless communication system 100 may also include one or more UEs (such as UE 190) indirectly connected to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links. Figure 1 In one example, UE 190 has a D2D P2P link 192 with one of UEs 104 connected to one of the base stations 102 (e.g., UE 190 can indirectly obtain cellular connectivity through this D2D P2P link), and a D2D P2P link 194 with a WLANSTA 152 connected to a WLAN AP 150 (UE 190 can indirectly obtain WLAN-based Internet connectivity through this D2D P2P link). In one example, D2D P2P links 192 and 194 can utilize any known D2D RAT (such as LTE Direct (LTE-D), Wi-Fi Direct). ® ,Bluetooth ® (etc.) to support it. As another example, D2D P2P link 192 and D2D P2P link 194 can be side links, as described above with reference to side links 162, 166 and 168.

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

[0073] Another optional aspect may include a location server 230, which can communicate with the 5GC 210 to provide location assistance to the UE 204. The location server 230 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively, each may correspond to a single server. The location server 230 may be configured to support one or more location services for the UE 204, which may be connected to the location server 230 via the core network, the 5GC 210, and / or via the Internet (not illustrated). Furthermore, the location server 230 may be integrated into a component of the core network, or alternatively, may be located outside the core network (e.g., a third-party server, such as an original equipment manufacturer (OEM) server or a service server).

[0074] Figure 2B Another example wireless network architecture 240.5GC 260 is illustrated (which can be used with...). Figure 2AThe 5GC 210 (corresponding to 5GC 210) can be functionally considered as a control plane function provided by the Access and Mobility Management Function (AMF) 264 and a user plane function provided by the User Plane Function (UPF) 262, which work together to form the core network (i.e., 5GC 260). The functions of AMF 264 include: registration management, connection management, reachability management, mobility management, lawful interception, transmission of session management (SM) messages between one or more UEs 204 (e.g., any of the UEs described herein) and the Session Management Function (SMF) 266, a transparent proxy service for routing SM messages, access authentication and access authorization, transmission of short message service (SMS) messages between UE 204 and the Short Message Service Function (SMSF) (not shown), and Secure Anchoring Functionality (SEAF). AMF 264 also interacts with the Authentication Server Function (AUSF) (not shown) and UE 204 and receives an intermediate key established as a result of the UE 204's authentication process. In the case of UMTS (Universal Mobile Telecommunications System) Subscriber Identity Module (USIM) authentication, AMF 264 retrieves security material from the AMF. AMF 264 also includes Security Context Management (SCM). The SCM receives a key from the SEAF and uses this key to derive an access network-specific key. AMF 264 functionality also includes location service management for regulatory services, transmission of location service messages between UE 204 and Location Management Function (LMF) 270 (which acts as location server 230), transmission of location service messages between NG-RAN 220 and LMF 270, Evolved Packet System (EPS) bearer identifier allocation for EPS interoperability, and UE 204 mobility event notification. Furthermore, AMF 264 also supports non-3GPP... ® (Third Generation Partner Program) Access network functionality.

[0075] The functions of UPF 262 include: acting as an anchor point for intra-RAT / inter-RAT mobility (where applicable), acting as an external Protocol Data Unit (PDU) session point interconnecting to a data network (not shown), providing packet routing and forwarding, packet inspection, user plane policy rule enforcement (e.g., strobing, redirection, traffic steering), lawful eavesdropping (user plane collection), traffic usage reporting, quality of service (QoS) processing for the user plane (e.g., uplink / downlink rate enforcement, reflective QoS marking in the downlink), uplink traffic 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 delivering and forwarding one or more "end markers" to the source RAN node. UPF 262 can also support the delivery of location service messages between UE 204 and location servers (such as SLP 272) on the user plane.

[0076] The functions of SMF 266 include session management, UE Internet Protocol (IP) address allocation and management, selection and control of user plane functions, service orientation configuration at UPF 262 for routing services to the correct destination, partial control of policy enforcement and QoS, and downlink data notification. The interface through which SMF 266 communicates with AMF 264 is called the N11 interface.

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

[0078] Another optional aspect may include a third-party server 274, which can communicate with LMF 270, SLP 272, 5GC 260 (e.g., via AMF 264 and / or UPF 262), NG-RAN 220, and / or UE 204 to obtain location information (e.g., location estimation) of UE 204. Therefore, 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 may be implemented as multiple separate servers (e.g., physically separate servers, different software modules on a single server, different software modules distributed across multiple physical servers, etc.), or alternatively, each may correspond to a single server.

[0079] User plane interface 263 and control plane interface 265 connect 5GC 260, and specifically connect UPF 262 and AMF 264 to one or more gNB 222 and / or ng-eNB 224 in NG-RAN 220. The interface between gNB 222 and / or ng-eNB 224 and AMF 264 is referred to as the "N2" interface, while the interface between gNB 222 and / or ng-eNB 224 and UPF 262 is referred to as the "N3" interface. The gNB 222 and / or ng-eNB 224 of NG-RAN 220 can communicate directly with each other via backhaul connection 223, referred to as the "Xn-C" interface. One or more of gNB 222 and / or ng-eNB 224 can communicate with one or more UEs 204 via a radio interface referred to as the "Uu" interface.

[0080] The functionality of the gNB 222 is divided among the gNB Central Unit (gNB-CU) 226, one or more gNB Distributed Units (gNB-DU) 228, and one or more gNB Radio Units (gNB-RU) 229. The gNB-CU 226 is a logical node that includes base station functions other than those specifically allocated to the gNB-DU 228, including user data delivery, mobility control, radio access network sharing, location, session management, etc. More specifically, the gNB-CU 226 typically hosts the Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) protocols of the gNB 222. The gNB-DU 228 is a logical node that typically hosts the Radio Link Control (RLC) and Media Access Control (MAC) layers of the gNB 222. Its operation is controlled by the gNB-CU 226. One gNB-DU 228 can support one or more cells, and a cell is supported by only one gNB-DU 228. The interface 232 between gNB-CU 226 and one or more gNB-DU 228 is referred to as the "F1" interface. The physical (PHY) layer functionality of gNB 222 is typically managed by one or more independent gNB-RU 229s, which perform functions such as power amplification and signal transmission / reception. The interface between gNB-DU 228 and gNB-RU 229 is referred to as the "Fx" interface. Therefore, UE 204 communicates with gNB-CU 226 via the RRC, SDAP, and PDCP layers, with gNB-DU 228 via the RLC and MAC layers, and with gNB-RU 229 via the PHY layer.

[0081] The deployment of communication systems such as 5G NR systems can be arranged in a variety of ways using various components or parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, RAN nodes, core network nodes, network elements, or network equipment (such as base stations or one or more units (or components) performing base station functions) can be implemented in aggregated or decomposed architectures. For example, base stations (such as Node B (NB), evolved NB (eNB), NR base stations, 5G NB, AP, TRP, cells, etc.) can be implemented as aggregated base stations (also known as standalone base stations or monolithic base stations) or decomposed base stations.

[0082] Aggregated base stations can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. Decentralized base stations can be configured to utilize a protocol stack that is physically or logically distributed across 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 respects, the CU may be implemented within a RAN node, and one or more DUs may co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. DUs may be implemented to communicate with one or more RUs. Each of the CUs, DUs, and RUs may also be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0083] Base station type operation or network design can consider the aggregation characteristics of base station functionality. For example, decomposed base stations can be used in Integrated Access Backhaul (IAB) networks, Open Radio Access Networks (O-RAN) (such as those developed by the O-RAN Alliance), and other similar networks. ® This can be used in proposed network configurations or virtualized radio access networks (vRAN, also known as cloud radio access networks (C-RAN)). Decomposition can include distributing functionality across two or more units in various physical locations, as well as virtually distributing the functionality of at least one unit, which allows for flexibility in network design. Various units in a decomposed base station or decomposed RAN architecture can be configured to communicate wirelessly with at least one other unit.

[0084] Figure 2C An example disaggregated base station architecture 250 according to various aspects of this disclosure is illustrated. 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 the core network 267 (e.g., 5GC 210, 5GC 260) via a backhaul link, or indirectly with the core network 267 via 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). CUs 280 may communicate with one or more duplex units (DUs) 285 (e.g., gNB-DU 228) via a corresponding midhaul link (e.g., an F1 interface). DUs 285 may communicate with one or more radio units (RUs) 287 (e.g., gNB-RU 229) via a corresponding fronthaul link. RU 287 can communicate with the corresponding UE 204 via one or more radio frequency (RF) access links. In some implementations, UE 204 can be served by multiple RU 287s simultaneously.

[0085] Each of the units (i.e., CU 280, DU 285, RU 287, and near-RT RIC 259, non-RT RIC 257, and SMO frame 255) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of these units, may be configured to communicate with one or more other units via transmission media. For example, these units may include wired interfaces configured to receive signals or transmit signals to one or more other units via wired transmission media. Additionally, these units may include wireless interfaces that may include receivers, transmitters, or transceivers (such as RF transceivers) configured to receive signals or transmit signals to one or more other units, or both, via wireless transmission media.

[0086] In some aspects, the CU 280 can host one or more higher-level control functions. Such control functions may include RRC, PDCP, Serving Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to communicate signaling with other control functions hosted by the CU 280. The CU 280 can 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. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 280 can be implemented to communicate with the DU 285 for network control and signaling, as needed.

[0087] DU 285 may correspond to a logic unit that includes one or more base station functions for controlling the operation of one or more RU 287s. In some aspects, DU 285 may be at least partially defined according to functional partitioning (such as by the 3rd Generation Partnership Project (3GPP)). ®The DU285 is functionally partitioned to host one or more of the RLC layer, MAC layer, and one or more high-PHY layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation). In some respects, the DU285 may further host one or more low-PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU285 or with control functions hosted by the CU280.

[0088] Lower-layer functionality can be implemented by one or more RU 287s. In some deployments, an RU287 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 both, based at least in part on functional decomposition (such as lower-layer functional decomposition). In such architectures, the RU 287 may be implemented to handle over-the-air (OTA) communications with one or more UE 204s. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 287 may be controlled by the corresponding DU 285. In some scenarios, this configuration allows the DU 285 and CU 280 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0089] SMO framework 255 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 255 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, SMO framework 255 can be configured to interact with cloud computing platforms such as Open Cloud (O-Cloud) 269 to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces such as the O2 interface. Such virtualized network elements may include, but are not limited to, CU 280, DU 285, RU 287, and near-RT RIC 259. In some implementations, SMO framework 255 can communicate with the hardware aspects of the 4G RAN (such as Open eNB (O-eNB) 261) via the O1 interface. Additionally, in some implementations, SMO framework 255 can communicate directly with one or more RU 287s via the O1 interface. SMO framework 255 may also include a non-RT RIC 257 configured to support the functionality of SMO framework 255.

[0090] The non-RT RIC 257 can be configured to include logical functions enabling non-real-time control and optimization of RAN elements and resources, including artificial intelligence / machine learning (AI / ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 259. The non-RT RIC 257 can be coupled to or communicate with the near-RT RIC 259, such as via an A1 interface. The near-RT RIC 259 can be configured to include logical functions enabling near real-time control and optimization of RAN elements and resources through data collection and actions via an interface, such as an E2 interface, connecting one or more CU 280s, one or more DU 285s, or both, and O-eNBs to the near-RT RIC 259.

[0091] 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 an external server. This information can be utilized by the near-RT RIC 259 and can be received from non-network data sources or network functions at the SMO framework 255 or the non-RT RIC 257. 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 in performance and employ AI / ML models to perform corrective actions via the SMO framework 255 (such as reconfiguration via O1) or by creating RAN management policies (such as A1 policies).

[0092] Figure 3A , Figure 3B and Figure 3C Several example components (represented by corresponding boxes) are illustrated, which can be incorporated into UE 302 (which may correspond to any UE described herein), base station 304 (which may correspond to any base station described herein), and network entity 306 (which may correspond to or embody any network function described herein, including location server 230 and LMF 270, or alternatively may be independent of UE 302). Figure 2A and Figure 2BThe NG-RAN 220 and / or 5GC 210 / 260 infrastructures depicted herein (such as dedicated networks) are used to support the operations described herein. It should be understood that these components can be implemented in different specific implementations in different types of devices (e.g., in ASICs, in System-on-Chip (SoCs), etc.). The illustrated components can also be incorporated into other devices in the communication system. For example, other devices in the system may include components similar to those described as providing similar functionality. Furthermore, a given device may contain one or more of these components. For example, a device may include multiple transceiver components that enable the device to operate on multiple carriers and / or communicate via different technologies.

[0093] UE 302 and base station 304 each include one or more Wireless Wide Area Network (WWAN) transceivers 310 and 350, which provide components (e.g., components for transmitting, components for receiving, components for measuring, components for tuning, components for blocking transmission, etc.) for communication via one or more wireless communication networks (not shown), such as NR networks, LTE networks, GSM networks, etc. WWAN transceivers 310 and 350 may each be connected to one or more antennas 316 and 356 for communication with other network nodes (such as other UEs, access points, base stations (e.g., eNB, gNB), etc.) via at least one designated RAT (e.g., NR, LTE, GSM, etc.) through a wireless communication medium of interest (e.g., a time / frequency resource set in a specific spectrum). WWAN transceivers 310 and 350 can be configured in different ways to transmit and encode signals 318 and 358 (e.g., messages, indications, information, etc.) according to a specified RAT, and conversely, to receive and decode signals 318 and 358 (e.g., messages, indications, information, pilots, etc.). Specifically, WWAN transceivers 310 and 350 each include: one or more transmitters 314 and 354 for transmitting and encoding signals 318 and 358, respectively; and one or more receivers 312 and 352 for receiving and decoding signals 318 and 358, respectively.

[0094] In at least some cases, UE 302 and base station 304 each further include one or more short-range radio transceivers 320 and 360, respectively. Short-range radio transceivers 320 and 360 can be connected to one or more antennas 326 and 366, respectively, and provide access over a wireless communication medium of interest via at least one designated RAT (e.g., Wi-Fi, LTE Direct, Bluetooth). ® ZIGBEE ® Z-WAVE ® Components (e.g., components for transmitting, components for receiving, components for measuring, components for tuning, components for blocking transmission, etc.) that enable communication between PC5, Dedicated Short Range Communication (DSRC), Wireless Access for Vehicle Environments (WAVE), Near Field Communication (NFC), Ultra Wideband (UWB), etc.) and other network nodes (such as other UEs, access points, base stations, etc.). Short-range transceivers 320 and 360 can be configured in different ways to transmit and encode signals 328 and 368 (e.g., messages, indications, information, etc.) respectively according to a specified RAT, and conversely, to receive and decode signals 328 and 368 (e.g., messages, indications, information, pilots, etc.) respectively. Specifically, short-range wireless transceivers 320 and 360 each include: one or more transmitters 324 and 364 for transmitting and encoding signals 328 and 368, respectively; and one or more receivers 322 and 362 for receiving and decoding signals 328 and 368, respectively. As a specific example, short-range wireless transceivers 320 and 360 can be Wi-Fi transceivers, Bluetooth transceivers, etc. ® Transceiver, Zigbee ® and / or Z-WAVE ® Transceivers, NFC transceivers, UWB transceivers, or vehicle-to-vehicle (V2V) and / or vehicle-to-everything (V2X) transceivers.

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

[0096] Satellite signal receivers 332 and 372 can be connected to one or more antennas 336 and 376, respectively, and can provide components for receiving and / or measuring satellite positioning / communication signals 338 and 378, respectively. When satellite signal receivers 332 and 372 are satellite positioning system receivers, satellite positioning / communication signals 338 and 378 can 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. When satellite signal receivers 332 and 372 are non-terrestrial network (NTN) receivers, satellite positioning / communication signals 338 and 378 can be communication signals originating from a 5G network (e.g., carrying control and / or user data). Satellite signal receivers 332 and 372 can include any suitable hardware and / or software for receiving and processing satellite positioning / communication signals 338 and 378, respectively. Satellite signal receivers 332 and 372 may request appropriate information and operations from other systems, and in at least some cases, use measurements obtained by any suitable satellite positioning system algorithm to perform calculations to determine the locations of UE 302 and base station 304, respectively.

[0097] Optional satellite signal transmitters 334 and 374 (when present) can be connected to one or more antennas 336 and 376, respectively, and can be provided with components for transmitting satellite positioning / communication signals 338 and 378, respectively. When satellite signal transmitter 374 is a satellite positioning system transmitter, the satellite positioning / communication signal 378 can be a GPS signal, GLONASS signal, etc. ® Signals include Galileo signals, BeiDou signals, NAVIC signals, and QZSS signals. When satellite signal transmitters 334 and 374 are NTN transmitters, satellite positioning / communication signals 338 and 378 can be communication signals originating from a 5G network (e.g., carrying control and / or user data). Satellite signal transmitters 334 and 374 can include any suitable hardware and / or software for transmitting satellite positioning / communication signals 338 and 378, respectively. Satellite signal transmitters 334 and 374 can request appropriate information and operations from other systems.

[0098] Base station 304 and network entity 306 each include one or more network transceivers 380 and 390, which provide components (e.g., transmitting components, receiving components, etc.) for communicating with other network entities (e.g., other base stations 304, other network entities 306). For example, base station 304 may use one or more network transceivers 380 to communicate with other base stations 304 or network entities 306 via one or more wired or wireless backhaul links. Similarly, network entity 306 may use one or more network transceivers 390 to communicate with one or more base stations 304 via one or more wired or wireless backhaul links, or to communicate with other network entities 306 via one or more wired or wireless core network interfaces.

[0099] Transceivers can be configured to communicate via wired or wireless links. A transceiver (whether wired or wireless) includes transmitter circuitry (e.g., transmitters 314, 324, 354, 364) and receiver circuitry (e.g., receivers 312, 322, 352, 362). In some embodiments, the transceiver may be an integrated device (e.g., implementing transmitter and receiver circuitry in a single device), in some embodiments it may include separate transmitter and receiver circuitry, or in other embodiments it may be implemented in a different manner. The transmitter and receiver circuitry of a wired transceiver (e.g., network transceiver 380 and network transceiver 390 in some embodiments) 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 multiple antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, which allows the corresponding device (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 multiple antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, which allows the corresponding device (e.g., UE 302, base station 304) to perform receive beamforming, as described herein. In one aspect, the transmitter and receiver circuitry may share the same multiple antennas (e.g., antennas 316, 326, 356, 366), such that the corresponding device may perform only receive or only transmit at a given time, rather than both receive and transmit simultaneously. Wireless transceivers (e.g., WWAN transceivers 310 and 350, short-range wireless transceivers 320 and 360) may also include network listening modules (NLMs) for performing various measurements.

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

[0101] UE 302, base station 304, and network entity 306 also include other components that can be used in conjunction with the operation disclosed herein. UE 302, base station 304, and network entity 306 each include one or more processors 342, 384, and 394 for providing functionality related to, for example, wireless communication, and for providing other processing functionality. Thus, processors 342, 384, and 394 may provide components for processing, such as components for determining, components for calculating, components for receiving, components for transmitting, components for indicating, etc. In one aspect, 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 circuits, or various combinations thereof.

[0102] UE 302, base station 304, and network entity 306 each include memory circuitry implementing memories 340, 386, and 396 (e.g., each including a memory device) for maintaining information (e.g., information indicating reserved resources, thresholds, parameters, etc.). Therefore, memories 340, 386, and 396 can provide components for storage, retrieval, maintenance, etc. In some cases, UE 302, base station 304, and network entity 306 may each include positioning components 348, 388, and 398. Positioning components 348, 388, and 398 may be hardware circuitry that is part of or coupled to processors 342, 384, and 394, respectively, which, when executed, enable UE 302, base station 304, and network entity 306 to perform the functionality described herein. In other aspects, positioning components 348, 388, and 398 may be external to processors 342, 384, and 394 (e.g., part of a modem processing system, integrated with another processing system, etc.). Alternatively, positioning components 348, 388, and 398 may be memory modules stored in memories 340, 386, and 396, respectively, which, when executed by processors 342, 384, and 394 (or modem processing system, another processing system, etc.), enable UE 302, base station 304, and network entity 306 to perform the functionality described herein. Figure 3A Possible locations for the positioning component 348 are illustrated. The positioning component may be part of, for example, one or more WWAN transceivers 310, memory 340, one or more processors 342, or any combination thereof, or may be a standalone component. Figure 3B Possible locations for the positioning component 388 are illustrated. The positioning component may be part of, for example, one or more WWAN transceivers 350, memory 386, one or more processors 384, or any combination thereof, or may be a standalone component. Figure 3C Possible locations for the positioning component 398 are illustrated. The positioning component may be part of, for example, one or more network transceivers 390, memory 396, one or more processors 394, or any combination thereof, or may be a standalone component.

[0103] UE 302 may include one or more sensors 344 coupled to one or more processors 342 to provide components for sensing or detecting motion and / or orientation information independent of motion data derived from signals received by one or more WWAN transceivers 310, one or more short-range wireless transceivers 320, and / or satellite signal interfaces 330. By way of example, sensor 344 may include accelerometers (e.g., microelectromechanical systems (MEMS) devices), gyroscopes, geomagnetic sensors (e.g., compasses), altimeters (e.g., barometric altimeters), and / or any other type of motion detection sensor. Furthermore, sensor 344 may include multiple different types of devices and combine their outputs to provide motion information. For example, sensor 344 may use a combination of multi-axis accelerometers and orientation sensors to provide the ability to calculate positioning in two-dimensional (2D) and / or three-dimensional (3D) coordinate systems.

[0104] In addition, UE 302 includes a user interface 346 that provides components for providing instructions to a user (e.g., audible and / or visual instructions) and / or for receiving user input (e.g., when the user actuates a sensing device such as a keypad, touchscreen, microphone, etc.). Although not shown, base station 304 and network entity 306 may also include user interfaces.

[0105] Referring more specifically to one or more processors 384, in the downlink, IP packets from network entity 306 can be provided to processor 384. One or more processors 384 can implement functionality for the RRC layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. One or more processors 384 may provide: RRC layer functionality associated with broadcasting system information (e.g., Master Information Block (MIB), System Information Block (SIB)), 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 (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the delivery of upper-layer PDUs, error correction via Automatic Repeat Request (ARQ), concatenation, segmentation, and reassembly of RLC Service Data Units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, priority processing, and logical channel priority ordering.

[0106] Transmitter 354 and receiver 352 implement Layer 1 (L1) functionality associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include: error detection on the transport channel, forward error correction (FEC) decoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. Transmitter 354 processes the mapping to the signal constellation 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 decoded and modulated symbols can then be split into parallel streams. Each stream can then be mapped to orthogonal frequency division multiplexing (OFDM) subcarriers, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domains, and then combined using inverse fast Fourier transform (IFFT) to produce a physical channel carrying a stream of time-domain OFDM symbols. The OFDM symbol stream is spatially pre-decoded to generate multiple spatial streams. Channel estimates from the channel estimator can be used to determine the decoding and modulation scheme, as well as for spatial processing. The channel estimates can be derived from reference signals and / or channel condition feedback transmitted by UE 302. Each spatial stream can then be provided to one or more different antennas 356. The transmitter 354 can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0107] At UE 302, receiver 312 receives signals via its corresponding antenna 316. Receiver 312 recovers the information modulated onto the RF carrier and provides this information to one or more processors 342. Transmitter 314 and receiver 312 implement Layer 1 functionality associated with various signal processing functions. Receiver 312 can perform spatial processing on the information to recover any spatial streams destined for UE 302. If multiple spatial streams are destined for UE 302, they can be combined by receiver 312 into a single OFDM symbol stream. Receiver 312 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. Symbols on each subcarrier, along with a reference signal, are recovered and demodulated by determining the most probable signal constellation point transmitted by base station 304. These soft decisions can be based on channel estimates calculated by a channel estimator. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted by base station 304 on the physical channel. Then, data and control signals are provided to one or more processors 342, which implement layer 3 (L3) and layer 2 (L2) functionality.

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

[0109] Similar to the functionality described in conjunction with downlink transmissions performed by base station 304, one or more processors 342 provide: RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connectivity, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with upper-layer PDU delivery, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer 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 via Hybrid Automatic Repeat Request (HARQ), priority processing, and logical channel priority ordering.

[0110] The channel estimate derived by the channel estimator from the reference signal or feedback transmitted by the base station 304 can be used by the transmitter 314 to select an appropriate decoding and modulation scheme and facilitate spatial processing. The spatial stream generated by the transmitter 314 can be provided to different antennas 316. The transmitter 314 can use the corresponding spatial stream to modulate the RF carrier for transmission.

[0111] Uplink transmissions are processed at base station 304 in a manner similar to that described in conjunction with the receiver function at UE 302. Receiver 352 receives signals via its corresponding antenna 356. Receiver 352 recovers the information modulated onto the RF carrier and provides this information to one or more processors 384.

[0112] In the uplink, one or more processors 384 provide demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transport channel and the logical channel to recover IP packets from UE 302. IP packets from one or more processors 384 can be provided to the core network. One or more processors 384 are also responsible for error detection.

[0113] For convenience, UE 302, base station 304 and / or network entity 306 are in Figure 3A , Figure 3B and Figure 3CThe document is shown as including various components that can be configured according to the various examples described herein. However, it should be understood that the illustrated components may have different functionalities in different designs. In particular, Figures 3A to 3C Various components are optional in alternative configurations, and various aspects include configurations that can vary due to design choices, cost, equipment usage, or other considerations. For example, in Figure 3A In certain cases, specific implementations of UE 302 may omit WWAN transceiver 310 (e.g., wearable devices, tablets, personal computers (PCs), or laptops may have Wi-Fi and / or Bluetooth). ® The short-range wireless transceiver 320 can be omitted (e.g., cellular only), or the satellite signal interface 330 can be omitted, or the sensor 344 can be omitted, etc. In another example, in Figure 3B In certain cases, specific implementations of base station 304 may omit WWAN transceiver 350 (e.g., a Wi-Fi "hotspot" access point without cellular capabilities), or short-range wireless transceiver 360 (e.g., cellular only), or satellite signal interface 370, etc. For the sake of brevity, examples of various alternative configurations are not provided herein, but will be readily understood by those skilled in the art.

[0114] Various components of UE 302, base station 304, and network entity 306 can be communicatively coupled to each other via data buses 308, 382, ​​and 392, respectively. In one aspect, data buses 308, 382, ​​and 392 can form or be part of the communication interfaces of UE 302, base station 304, and network entity 306, respectively. For example, in cases where different logical entities are embodied in the same device (e.g., gNB and location server functionality integrated into the same base station 304), data buses 308, 382, ​​and 392 can provide communication between these logical entities.

[0115] Figure 3A , Figure 3B and Figure 3C The components can be implemented in various ways. In some specific implementations, Figure 3A , Figure 3B and Figure 3CThe components can 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 combine at least one memory component for storing information or executable code used by the circuit to provide that functionality. For example, some or all of the functionalities represented by blocks 310 to 346 may be implemented by the processor and memory components of UE 302 (e.g., by executing appropriate code and / or by appropriate configuration of the processor components). Similarly, some or all of the functionalities represented by blocks 350 to 388 may be implemented by the processor and memory components of base station 304 (e.g., by executing appropriate code and / or by appropriate configuration of the processor components). Moreover, some or all of the functionalities represented by blocks 390 to 398 may be implemented by the processor and memory components of network entity 306 (e.g., by executing appropriate code and / or by appropriate configuration of the processor components). For simplicity, various operations, actions, and / or functions are described herein as being performed "by the UE," "by the base station," "by the network entity," etc. However, it should be understood that such operations, actions and / or functions can actually be performed by specific components or combinations of components of the UE 302, base station 304, network entity 306, etc. (such as processors 342, 384, 394, transceivers 310, 320, 350 and 360, memories 340, 386 and 396, positioning components 348, 388 and 398, etc.).

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

[0117] It should be noted that Figure 3A The UE 302 illustrated herein may represent a "RedCap" UE or an "Advanced" UE. As further described below, although RedCap UEs and Advanced UEs may have the same types of components (e.g., both may have one or more WWAN transceivers 310, one or more short-range radio transceivers 320, satellite signal interfaces 330, one or more processors 342, memory 340, etc.), these components may have different degrees of functionality (e.g., increased or decreased performance, more or less capability, etc.) depending on whether UE 302 corresponds to a RedCap UE or an Advanced UE.

[0118] NR supports or enables various sidelink positioning technologies. Figure 4A Various scenarios of interest, including sidelink-only positioning or combined Uu and sidelink positioning, are illustrated according to various aspects of this disclosure. In scenario 410, at least one peer UE with a known location can improve the Uu-based positioning of a target UE by providing additional anchors (e.g., using sidelink round-trip time (RTT) (SL-RTT)). In scenario 420, a low-end (e.g., capacity-reduced or “RedCap”) target UE can receive assistance from a high-end UE to determine its location using, for example, sidelink positioning and ranging procedures. Compared to the low-end UE, the high-end UE may have more capabilities, such as more sensors, a faster processor, more memory, more antenna elements, higher transmit power capabilities, access to additional frequency bands, or any combination thereof. In scenario 430, a relay UE (e.g., with a known location) participates in the positioning estimation of a remote UE without performing uplink positioning reference signal (PRS) transmission via the Uu interface. Scenario 440 illustrates joint positioning of multiple UEs. Specifically, in scenario 440, two UEs with unknown locations can jointly locate each other under non-line-of-sight (NLOS) conditions by utilizing constraints from nearby UEs.

[0119] Figure 4B Additional scenarios of interest, including sidelink-only positioning or combined Uu and sidelink positioning, are illustrated according to various aspects of this disclosure. In scenario 450, a UE used for public safety (e.g., by police, firefighters, etc.) may perform peer-to-peer (P2P) positioning and ranging for public safety and other purposes. For example, in scenario 450, a public safety UE may be outside network coverage and use sidelink positioning technology to determine the location or relative distance and relative positioning between public safety UEs. Similarly, scenario 460 illustrates multiple UEs outside coverage and using sidelink positioning technology (such as SL-RTT) to determine their location or relative distance and relative positioning.

[0120] NR supports various sidelink ranging techniques. Sidelink-based ranging and positioning (SLRP) enables the determination of relative distances between UEs, and optionally their absolute positions if the absolute positions of at least one of the involved UEs are known. This technique is valuable in situations where Global Navigation Satellite System (GNSS) positioning is degraded or unavailable (e.g., tunnels, urban canyons, etc.), and can also enhance ranging and positioning accuracy when GNSS is available.

[0121] SLRP is based on the inter-UE round-trip time (RTT) measurement, calculated from the transmission and reception times of the sidelink positioning reference signal (SL-PRS) (a broadband positioning signal defined for sidelink-based positioning and further described below). Each UE reports its RTT measurement along with its location (if known) to all other participating UEs. For UEs that do not know their location at all or do not know it accurately, the RTT procedure generates the inter-UE distance between the involved UEs. For UEs that know their location accurately, this distance generates absolute positioning.

[0122] Figure 5 An example of a sidelink-based ranging and positioning (SLRP) procedure 500 according to various aspects of this disclosure is illustrated. The Sidelink Positioning Protocol (SLPP) is used to establish the SLRP procedure 500 to identify participating UEs, perform session establishment, and exchange measurements and measurement results. SLPP reuses the basic Long Term Evolution (LTE) Positioning Protocol (LPP) message structures for requesting / providing capabilities, requesting / providing auxiliary data, and requesting / providing location information.

[0123] SLRP procedure 500 (or session) begins when the target UE 204-2 (a UE attempting to be located with an unknown or inaccurate location) sends an SLPP request capability message at phase 505 requesting capability information from one or more peer UEs. For example... Figure 5 As shown, at least one peer UE (UE 204-1) can become the anchor UE for SLRP procedure 500. Therefore, at stage 510, anchor UE 204-1 responds with an SLPP provision capability message including an indication that the anchor UE can become the anchor UE for SLRP procedure 500. The SLPP provision capability message may also include the location of anchor UE 204-1, or the location may be provided later.

[0124] At phase 515, after the initial capability exchange, anchor UE 204-1 sends an SLPP request auxiliary data message to target UE 204-2. At phase 520, target UE 204-2 sends an SLPP provide auxiliary data message to anchor UE 204-1, which may include configuration to be sent by anchor UE 204-1 for use by target UE 204-2 for one or more SL-PRS resources measured by SLRP procedure 500. Alternatively or additionally, the SLPP provide auxiliary data message may include configuration information to be sent by target UE 204-2 for use by anchor UE 204-1 for one or more SL-PRS resources measured by anchor UE 204-1. In some cases (not shown), target UE 204-2 may send an SLPP request auxiliary data message to anchor UE 204-1 to obtain configuration information sent by anchor UE 204-1 for use by target UE 204-2 for one or more SL-PRS resources measured by target UE 204-2. The target UE 204-2 provides the requested configuration information in the SLPP Provide Auxiliary Data Message. In some cases, the corresponding UE 204 may not send an SLPP Request Auxiliary Data Message, but only an SLPP Provide Auxiliary Data Message.

[0125] At stages 525 and 530, the involved peer UEs 204 transmit the configured SL-PRS resources to each other. Alternatively, only the anchor UE 204-1 of the target UE 204-2 may transmit SL-PRS resources (e.g., in the case of a sidelink time difference of arrival (SL-TDOA) procedure). Resources for transmitting SL-PRS can be configured during the auxiliary data exchange at stages 515 and 520. The anchor UE 204-1 measures the receive-to-transmit (Tx-Rx) time difference between the transmission time of the SL-PRS resources at stage 525 and the reception time of the SL-PRS resources at stage 530. Similarly, the target UE 204-2 measures the Rx-Tx time difference between the reception time of the SL-PRS resources at stage 525 and the transmission time of the SL-PRS resources at stage 530. It should be noted that although... Figure 5 The example shows that anchor UE 204-1 sends the SL-PRS first, but target UE 204-2 may instead send the PRS first.

[0126] At stage 535, target UE 204-2 sends an SLPP request location information message to anchor UE 204-1. At stage 540, anchor UE 204-1 responds with an SLPP provide location information message including an Rx-Tx time difference measurement obtained by anchor UE 204-1. Alternatively or additionally (not shown), anchor UE 204-1 may send an SLPP request location information message to target UE 204-2, and target UE 204-2 may respond with an SLPP provide location information message including an Rx-Tx time difference measurement obtained by target UE 204-2. If anchor UE 204-1 has not yet provided its location to target UE 204-2, it does so at this time.

[0127] Then, the target UE 204-2 can determine its own RTT (Round-Tight Time) and that of the anchor UE 204-1 based on the Rx-Tx time difference measurement. Based on the RTT measurement and the speed of light, the target UE 204-2 can then estimate the distance (or ranging value) between the two UEs 204. If the target UE 204-2 also has the absolute positions (e.g., geographic coordinates) of the anchor UE 204-1 and two or more additional anchor UEs 204-1, the target UE 204-2 can use that position and the distance to the anchor UE 204-1 to determine its own absolute position (based on trilateration).

[0128] It should be noted that, although Figure 5 An example of an anchor UE 204-1 is given, but a target UE 204-2 can perform or attempt to perform SLRP procedures 500 with multiple anchor UEs 204-1. Furthermore, although... Figure 5 The example illustrates that SLPP request location information is sent after SL-PRS resources are sent, but SLPP request location information can be sent before SL-PRS is sent.

[0129] Sidelink communication occurs within transmit or receive resource pools. In the frequency domain, the smallest unit of resource allocation is a subchannel (e.g., the collection of consecutive PRBs in the frequency domain). In the time domain, resource allocation is performed within a time slot interval. However, some time slots are unavailable for sidelinks, and some time slots contain feedback resources. Furthermore, sidelink resources can be (pre-)configured to occupy fewer than 14 symbols in a time slot.

[0130] Configure sidelink resources at the Radio Resource Control (RRC) layer. RRC configuration can be pre-configured (e.g., pre-loaded on the UE) or configured (e.g., from the serving base station).

[0131] The NR side link supports Hybrid Automatic Repeat Request (HARQ) retransmission. Figure 6A This is a diagram 600 illustrating an example time slot structure without feedback resources based on various aspects of this disclosure. Figure 6A In the example, time is represented horizontally and frequency vertically. In the time domain, the length of each block is one Orthogonal Frequency Division Multiplexing (OFDM) symbol, and 14 symbols constitute a time slot. In the frequency domain, the height of each block is a subchannel. Currently, the (pre-)configured subchannel size can be selected from a set of {10, 15, 20, 25, 50, 75, 100} Physical Resource Blocks (PRBs).

[0132] For side-link time slots, the first symbol is a repetition of the previous symbol and is used for automatic gain control (AGC) settings. This is in Figure 6A This is illustrated using vertical and horizontal hashing. For example... Figure 6A As shown, for sidelinks, the Physical Sidelink Control Channel (PSCCH) and the Physical Sidelink Shared Channel (PSSCH) are transmitted in the same time slot. Similar to the Physical Downlink Control Channel (PDCCH), the PSCCH carries control information about sidelink resource allocation and a description of the sidelink data sent to the UE. Likewise, similar to the Physical Downlink Shared Channel (PDSCH), the PSSCH carries the UE's user data. Figure 6A In the example, the PSCCH occupies half the bandwidth of the sub-channel and only takes up three symbols. Finally, the gap symbol appears after the PSSCH.

[0133] Figure 6B This is a diagram 650 illustrating an example time-slot structure with feedback resources based on various aspects of this disclosure. Figure 6B In the example, time is represented horizontally and frequency is represented vertically. In the time domain, the length of each block is one OFDM symbol, and 14 symbols constitute a time slot. In the frequency domain, the height of each block is a subchannel.

[0134] Figure 6B The time slot structure illustrated in the figure is similar to Figure 6A The time slot structure illustrated herein, except Figure 6B The time slot structure illustrated includes resources beyond feedback. Specifically, the last two symbols of a time slot are dedicated to the Physical Side Link Feedback Channel (PSFCH). The first PSFCH symbol is a repetition of the second PSFCH symbol used for AGC setup. In addition to the gap symbol following the PSFCH, there is a gap symbol after the two PSFCH symbols. Currently, the resources used for the PSFCH can be configured using a periodicity selected from the set of {0, 1, 2, 4} time slots.

[0135] Figure 7A Figure 700 illustrates an example of a location-based resource pool configured within a sidelink resource pool (i.e., a shared resource pool) for communication, according to various aspects of this disclosure. Figure 7AIn the example, 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 14 symbols constitute a time slot. In the frequency domain, the height of each block is a subchannel.

[0136] exist Figure 7A In the example, the entire time slot (excluding the first and last symbols) can be a resource pool for sidelink communication. That is, any symbol other than the first and last can be allocated for sidelink communication. However, the resource pool for positioning (RP-P) is allocated in the last four pre-slot symbols of the time slot. Therefore, non-sidelink 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 post-AGC symbols, not in the last four pre-slot symbols, to prevent conflicts with the configured RP-P. Non-sidelink positioning data that would otherwise be transmitted in the last four pre-slot symbols can be punctured or silenced, or rate-matched non-sidelink data that typically spans more than eight post-AGC symbols can be used to accommodate these eight post-AGC symbols.

[0137] Sidelink Positioning Reference Signal (SL-PRS) has been defined to support the sidelink positioning process between UEs. Similar to the downlink PRS (DL-PRS), an SL-PRS resource consists of one or more resource elements (i.e., an OFDM symbol in the time domain and a subcarrier in the frequency domain). SL-PRS resources are designed with a comb-based pattern to enable Fast Fourier Transform (FFT) based processing at the receiver. SL-PRS resources consist of uninterleaved or only partially interleaved resource elements in the frequency domain to provide small time-of-arrival (TOA) uncertainties and reduced overhead for each SL-PRS resource. SL-PRS can also be associated with a specific RP-P (e.g., some SL-PRS can be allocated in some RP-Ps). SL-PRS has also been defined with in-slot repetition ( Figure 7A (not shown in the image) to allow for combined gain (if needed). RP-P inter-UE coordination may also exist to provide dynamic SL-PRS and data multiplexing while minimizing SL-PRS collisions.

[0138] Figure 7B and Figure 7C Figures 730 and 750 are additional examples illustrating a location resource pool configured within a sidelink resource pool used for communication. Similar to Figure 7, Figure 7B and Figure 7C The example illustrates a shared resource pool structure. About Figure 7B and Figure 7CIn some designs, the following parameters can be defined, such as: the Physical Side Link Control Channel (PSCCH) and SL-PRS are time-division multiplexed only; the PSSCH and SL-PRS are time-division multiplexed only (e.g., the maximum comb size is 4); the PSSCH carries both Type 2 Side Link Control Information (SCI-2) and Side Link Shared Channel (SL-SCH) (e.g., introducing a new SCI-2 format); the SL-PRS is mapped on consecutive symbols; the SL-PRS is not mapped on symbols with PSSCH demodulation reference signals (DMRS); and / or the SL-PRS transmit power is the same as the PSSCH transmit power (e.g., this implies that per resource element power boost will be applied to comb 2 and comb 4).

[0139] Figure 7D Figure 770 is another example of a location-based resource pool configured within a sidelink resource pool used for communication. Figure 7D The example depicts a dedicated resource pool structure. Regarding... Figure 7D In some designs, the following parameters can be defined, such as: SL-PRS is immediately preceded by an AGC symbol, and SL-PRS is immediately followed by a gap symbol (at least when the gap symbol is the last sidelink symbol in the time 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., a set of SL-PRS resources can only have a single (M, N) combination); PSSCH is mapped to the first few sidelink symbols in the time slot; the number of PSCCH symbols is (pre) configured as 1, 2, or 3; the number of physical resource blocks is (pre) configured using sidelink communication values; and / or there is a one-to-one implicit mapping between PSCCH and SL-PRS.

[0140] In some designs, within a shared resource pool, the fields for SCI Format 2-D may include, for example: an indication of SL-PRS resource information for the current time slot (the number of bits is the base-2 logarithm of the number of (pre-)configured SL-PRS resources in the resource pool, rounded up), an SL-PRS request (0 or 1 bit), and / or an embedded SCI format ([X] bits). If the "embedded SCI format" field is set to [0], an SCI 2-A field with necessary padding is included. If the "embedded SCI format" field is set to [1], an SCI 2-B field is included.

[0141] In some designs, for a shared resource pool, there may be an explicit (pre)configuration of SL-PRS resources in the time slots for the indicated frequency domain allocation. This explicit (pre)configuration includes, for example, SL-PRS resource ID, (M, N) mode, and / or comb offset. In some designs, for a given value of “M”, taking into account multiplexing with PSSCH DMRS, Phase Tracking Reference Signal (PT-RS), CSI-RS, PSFCH, gap symbols, AGC symbols, and / or PSCCH in the time slot, the SL-PRS resources are mapped to the last consecutive “M” sidelink symbols in the time slot available for SL-PRS. In some designs, the maximum number of SL-PRS resources in the time slots of the shared resource pool can be (pre)configured.

[0142] In some designs, within a dedicated resource pool, regarding the process for determining the subset of resources to be reported to the higher layer, when the resource (re)selection process is triggered, the higher layer provides the following parameters to the candidate SL-PRS to send, such as: the resource pool from which it reports the SL-PRS resources, priority, delay budget, reservation period, list of resources for preemption and re-evaluation, and / or a set of SL-PRS resource identifiers that may include all (pre)configured SL-PRS resource identifiers.

[0143] Figure 8A An example set 800 of aggregated sidelink RP-Ps according to various aspects of this disclosure is illustrated. Figure 8A In the example depicted, the set 800 of aggregated sidelink RP-Ps includes a first shared sidelink RP-P on a first carrier (e.g., a first component carrier (CC), denoted as "CC1") and a second shared sidelink RP-P on a second carrier (e.g., a second CC, denoted as "CC2"), each of which is as described above regarding Figure 7B It is configured as described. In this example, the aggregated SL-PRS resource is indicated by reference numeral 810. In one aspect, CC1 and CC2 may be separated by one or more CC guard bands (in the frequency domain). It should be noted that the aggregated SL-PRS resource 810 may be scheduled jointly or separately, and may (optionally) share certain common attributes (e.g., the same comb pattern, the same transmit power, etc.).

[0144] Figure 8B An example set 850 of aggregated sidelink RP-Ps according to various aspects of this disclosure is illustrated. Figure 8BIn the example depicted, the set 850 of aggregated sidelink RP-Ps includes a first dedicated sidelink RP-P on a first carrier (e.g., a first CC, denoted as "CC1") and a second dedicated sidelink RP-P on a second carrier (e.g., a second CC, denoted as "CC2"), each of which is as described above regarding Figure 7D The configuration is as described. In this example, the aggregated SL-PRS resource is indicated by reference numeral 860. On one hand, CC1 and CC2 may be separated (in the frequency domain) by one or more CC guard bands. On the other hand, the CC guard band (which does not carry SL-PRS) may be configured such that the comb pattern of SL-PRS 1 and SL-PRS 2 across CC1 and CC2 is maintained as if the CC guard band carried SL-PRS 1 and SL-PRS 2. It should be noted that the aggregated SL-PRS resource 860 may be scheduled jointly or separately, and may (optionally) share certain common attributes (e.g., the same comb pattern, the same transmit power, etc.).

[0145] A Channel Busy Ratio (CBR) parameter has been defined for sidelinks to track channel resource utilization at each given node (e.g., UE, RSU, gNB, etc.). The sidelink CBR measured in time slot n is defined as a portion of a subchannel in the resource pool whose UE-measured sidelink received signal strength indicator (SL-RSSI) exceeds a (pre-)configured threshold sensed within the CBR measurement window [na, n-1], where a equals 100 or 100.2 according to the higher-layer parameter “sl-TimeWindowSizeCBR”. µ One time slot. Sidelink CBR is applicable within RRC IDLE frequency, between RRC IDLE frequencies, within RRC CONNECTED frequency, and between RRC CONNECTED frequencies.

[0146] SL-RSSI is defined as the linear average of the total received power (e.g., in watts) observed in the configured sub-channels of the OFDM symbols configured for the PSCCH and PSSCH, starting from the second OFDM symbol. For FR1, the reference point for SL-RSSI is the UE's antenna connector. For FR2, SL-RSSI is measured based on the combined signal from the antenna element corresponding to a given receiver branch. For both FR1 and FR2, if receiver diversity is in use by the UE, the reported SL-RSSI value should not be lower than the corresponding SL-RSSI of any individual receiver branch within the individual receiver branches.

[0147] Side-link CBR can be configured in each side-link resource pool. Specifically, the RRC parameter "sl-ThreshS-RSSI-CBR" in the resource pool configuration indicates the SL RSSI threshold used to determine the contribution of the sub-channel to the CBR measurement. A value "0" corresponds to -112dBm, a value "1" corresponds to -110dBm, and a value n corresponds to (-112+n) / (1-10-112 ... 2 (dBm), and so on. The RRC parameter "sl-TimeWindowSizeCBR" in the resource pool configuration indicates the size of the time window used for CBR measurement.

[0148] Currently, up to sixteen CBR ranges have been defined. For each range, a channel occupancy ratio (CR) limit is specified, which the transmitting UE cannot exceed, and this limit can take different values ​​depending on the transmission priority. When a UE wants to transmit an SL-PRS, the UE measures the CBR and maps the CBR to one of these ranges to determine the CR limit. The UE also estimates its CR, and if the CR is higher than the CR limit, the UE adjusts its transmission parameters.

[0149] In Scheme 2 SL-PRS resource allocation (where the UEs involved reserve resources for SL-PRS transmission without network involvement), for a dedicated resource pool used for positioning, congestion control can limit the range of at least the following parameters for SL-PRS configuration for each resource pool according to CBR and priority: maximum SL-PRS transmission power and maximum SL-PRS (re)transmission count. For sidelink congestion control similar to legacy congestion control, CR limits can be (pre)configured in the resource pool according to priority (how to implement the CR limits is left to the UE's specific implementation). For a shared resource pool used for positioning, SL-PRS can share the same PSSCH limits without requiring specific enhancements other than those currently specified.

[0150] For Scheme 2 SL-PRS resource allocation, various modifications are supported regarding congestion control for dedicated resource pools. As a first modification, the definitions of SL-PRS CR and CBR are redefined by considering SL-PRS resource allocation / configuration. As a second modification, for the evaluation of RSSI used in the CBR definition, SL-RSSI is measured on the time slots configured for PSCCH and SL-PRS transmissions, and a single SL-RSSI is measured on symbols containing both SL-PRS and PSCCH. As a third modification, the CR and CBR measurement time window sizes can be configured separately for dedicated resource pools, and both old-style and current values ​​can be used.

[0151] The SL-PRS CR for a dedicated resource pool used for positioning is defined as follows. The SL-PRS CR evaluated at time slot n is defined as the total number of SL-PRS resource sub-channels (i.e., sub-channels for transmitting SL-PRS resources) used for transmitting SL-PRS resources in time slot [na, n-1] and the total number of SL-PRS resource sub-channels granted in time slot [n, n+b] divided by the total number of SL-PRS resource sub-channels configured in the transmission pool at [na, n+b].

[0152] The SL-PRS CBR for a dedicated resource pool used for positioning is defined as follows. The SL-PRS CBR measured in time slot n is defined as a portion of the SL-PRS resource sub-channels in the resource pool whose SL-PRS RSSI measured by the UE exceeds a (pre-)configured threshold sensed within a CBR measurement window of [na, n-1], where a equals 100 or 100.2 according to the higher-layer (e.g., RRC, SLPP) parameter "sl-TimeWindowSizeCBR". μ Each time slot.

[0153] The SL-PRS RSSI for a dedicated resource pool used for positioning is defined as follows. The SL-PRS RSSI for an SL-PRS resource is defined as the linear average of the total received power (e.g., in watts) observed in the configured sub-channel resource elements of the OFDM symbols in the time slots configured for the SL-PRS resource, starting from the second OFDM symbol, and in the configured sub-channels of the OFDM symbols in the time slots configured for the associated PSCCH, starting from the second OFDM symbol, and in the configured sub-channels of the OFDM symbols in the time slots configured for the PSSCH, starting from the second OFDM symbol.

[0154] This disclosure considers a modified CBR definition to accommodate SL-PRS frequency hopping for RedCap UEs. UEs can be classified as RedCap UEs (e.g., IoT devices, wearable devices such as smartwatches, glasses, rings, etc.) and Advanced UEs (e.g., smartphones, tablets, laptops, etc.). Alternatively, RedCap UEs may be referred to as Low-Level UEs, Light UEs, or Ultra-Light UEs. Advanced UEs are alternatively referred to as Full-Cap UEs or simply UEs. Compared to advanced UEs, RedCap UEs typically have lower baseband processing capabilities, fewer antennas (e.g., one receiver antenna as the baseline in FR1 or FR2, optionally with two receiver antennas), lower operating bandwidth capabilities (e.g., 20 MHz for FR1 without supplemental uplink or carrier aggregation, or 50 MHz or 100 MHz for FR2), half-duplex frequency division duplex (HD-FDD) capability only, smaller HARQ buffers, reduced physical downlink control channel (PDCCH) monitoring, restricted modulation (e.g., 64 QAM for downlink and 16 QAM for uplink), more relaxed processing timeline requirements, and / or lower uplink transmit power. Different UE classes can be distinguished by UE category and / or UE capabilities. For example, certain types of UEs may be assigned the "RedCap" category (e.g., by original equipment manufacturer (OEM), applicable wireless communication standards, etc.), while other types of UEs may be assigned the "Advanced" category. Certain UE classes may also report their type to the network (e.g., "RedCap" or "Advanced"). Additionally, certain resources and / or channels may be dedicated to certain types of UEs.

[0155] It should be understood that the accuracy of RedCap UE positioning may be limited. For example, RedCap UEs may operate on reduced bandwidths, such as 5MHz to 20MHz for wearables and “relaxed” IoT devices (i.e., IoT devices with relaxed or lower capability parameters such as lower throughput, relaxed latency requirements, lower power consumption, etc.), leading to lower positioning accuracy. As another example, the receive processing capability of RedCap UEs may be limited due to their lower RF / baseband costs. Therefore, the reliability of measurement and positioning calculations is reduced. Furthermore, such RedCap UEs may not be able to receive multiple PRSs from multiple TRPs, further reducing positioning accuracy. As yet another example, the transmit power of RedCap UEs may be reduced, meaning that there will be lower quality uplink measurements for RedCap UE positioning.

[0156] Advanced UEs typically have a larger form factor and are more expensive than RedCap UEs, and also possess more features and capabilities. For example, regarding positioning, advanced UEs can operate across the full PRS bandwidth (such as 100MHz) and measure PRS from more TRPs than RedCap UEs, both of which contribute to higher positioning accuracy. As another example, the receive processing capabilities of advanced UEs may be higher (e.g., faster) due to their superior RF / baseband capabilities. Furthermore, advanced UEs can have higher transmit power than RedCap UEs. This increases the reliability of measurement and positioning calculations.

[0157] SL-PRS frequency hopping has been approved for RedCap UEs. With SL-PRS frequency hopping, a UE can be configured to utilize multiple SL-PRS resources that hop across multiple frequencies. More specifically, in frequency hopping (also known as “bandwidth hopping,” “frequency splicing,” “bandwidth splicing,” etc.), a signal (e.g., SL-PRS) is transmitted over multiple “hops,” where each hop is one or more symbols / slots in the time domain and one or more PRBs in the frequency domain. The receiving UE “splices” together measurements of the SL-PRS resources in each hop to determine the final measurement of the SL-PRS resources.

[0158] Figure 9 Figure 900 illustrates an example of the overlapping bandwidth between transitions according to various aspects of this disclosure. Figure 900 illustrates two 24-PRB SL-PRS transitions in the frequency domain. Each SL-PRS transition may span one or two symbols of the same time slot in the time domain. Figure 10 Figure 1000 illustrates an example of the switching gaps between transitions according to various aspects of this disclosure. Figure 1000 illustrates two 24-PRB SL-PRS transitions in the frequency domain. Each SL-PRS transition may span one or two symbols of the same time slot in the time domain.

[0159] Figure 11 Figure 1100 illustrates an example of a UE performing six frequency hopping for an SL-PRS positioning use case, according to various aspects of this disclosure. Figure 11 In the example, the SL-PRS resource includes six frequency hops; however, it should be understood that there may be more or fewer than six hops. The six hops of the SL-PRS resource are referred to as the aggregated SL-PRS resource frequency hops.

[0160] For each hop, the UE will have to move away from the current hop and to the next hop, making each hop an expensive operation. However, for positioning use cases, each hop will be fully utilized by the receiver (measurement) because it will improve positioning performance at the receiver (e.g., ToA resolution). However, regarding channel congestion issues, it may not be necessary to perform channel sensing (e.g., RSSI) for each hop. It may also not be necessary to perform CBR and CR calculations for each hop.

[0161] Therefore, this disclosure provides a technique for per-hop sidelink congestion control estimation when determining cross-hop SL-PRS transmission attributes. In a first phase, the UE receives a (pre)configuration for SL-PRS resource transmission within a sidelink resource pool, wherein the configuration indicates multiple (N) SL-PRS frequency hops for the SL-PRS resources, and wherein each frequency hop has a bandwidth less than the total bandwidth of the resource pool. In a second phase, the UE independently calculates CBR, CR, and SL-RSSI (which may be collectively referred to as SL-PRS congestion control metrics) for each frequency hop in at least a subset of the N SL-PRS frequency hops. In a third phase, the UE determines the SL-PRS transmission attributes of a frequency hop based at least on the SL-PRS congestion control metrics calculated for each frequency hop in the subset of the N SL-PRS frequency hops. In a fourth phase, the UE transmits SL-PRS resources on the N SL-PRS frequency hops according to the SL-PRS transmission attributes of each frequency hop determined in the third phase.

[0162] In some cases, SL-PRS congestion control metrics (CBR, CR, and SL-RSSI) can be determined for a single hop, and the UE will use the remaining hops (transmit on the remaining hops) based on this determination. More specifically, when the SL-PRS transmission attributes for one hop in an aggregated SL-PRS resource hop (i.e., N hops through which SL-PRS resources are transmitted), the transmission attributes for the other aggregated SL-PRS resource hops are also adjusted. For example, if one hop in an SL-PRS resource hop is determined to be busy, and the SL-PRS resource for that hop is expected to have reduced transmission power, the transmission power for the other SL-PRS resource hops will also be reduced (even if the measurement in that resource hop does not require such a reduction in transmission power).

[0163] The same techniques can be used for the maximum number of SL-PRS transition (retransmissions), the minimum periodicity of SL-PRS resource transitions, the maximum number of SL-PRS resource transitions in a time slot, the maximum comb size of SL-PRS resource transitions in a time slot, and / or the maximum number of OFDM symbols for SL-PRS resource transitions in a time slot. That is, for example, when adjusting the maximum number of SL-PRS transition (retransmissions) for one transition in aggregated SL-PRS resource transitions, the maximum number of SL-PRS transition (retransmissions) for other aggregated SL-PRS resource transitions is also adjusted.

[0164] Figure 12 Figure 1200 illustrates an example of the calculation of single-hop-based SL-PRS congestion control metrics (e.g., RSSI, CBR, and CR) according to various aspects of this disclosure. Figure 12 In the example, the UE is performing six frequency hops for SL-PRS resource transmission (i.e., the number of aggregated SL-PRS frequency hops is six). That is, the SL-PRS resources span six frequency hops in the frequency domain. However, it should be understood that there may be more or fewer than six hops. These hops can be configured by the location server via auxiliary data (e.g., auxiliary data messages provided by LPP), by the base station (e.g., via RRC), or by the sidelink anchor UE (e.g., via SLPP).

[0165] exist Figure 12 In the example, the UE determines the SL-PRS congestion control metrics (e.g., RSSI, CBR, and CR) for a single hop (e.g., hop 1). When the single-hop check passes, the UE can blindly use other hops to transmit SL-PRS resources. This is similar to random selection and transmission. There is no problem if the receiving UE can measure SL-PRS on all hops based on the sending UE using the same transmission attributes for all hops within the hop. Otherwise, the receiving UE can request the sending UE to include other hops in the congestion control metric calculation.

[0166] In some cases, SL-PRS congestion control metrics (CBR, CR, and SL-RSSI) can be determined for multiple hops, and the UE will use the remaining hops (transmit on the remaining hops) based on those determinations. Figure 13 Figure 1300 illustrates an example of the calculation of multi-hop-based SL-PRS congestion control metrics (e.g., RSSI, CBR, and CR) according to various aspects of this disclosure. Figure 13In the example, the UE is performing six frequency hops for SL-PRS resource transmission. That is, the SL-PRS resources span six frequency hops in the frequency domain. However, it should be understood that there may be more or fewer than six hops. These hops can be configured by the location server via auxiliary data (e.g., auxiliary data messages provided by LPP), by the base station (e.g., via RRC), or by the sidelink anchor UE (e.g., via SLPP).

[0167] In this scenario, each hop used for calculating congestion control metrics will have one or more other hops associated with it for joint hop transmission. Figure 13 In the example, the UE performs CBR calculation for hop 1 and uses the transmission attributes determined for hop 1 to jointly transmit SL-PRS resources on hop 1 and hop 2. Similarly, the UE performs CBR calculation for hop 3 and uses the transmission attributes determined for hop 3 to jointly transmit SL-PRS resources on hop 3 and hop 4. Finally, the UE performs CBR calculation for hop 5 and uses the transmission attributes determined for hop 5 to jointly transmit SL-PRS resources on hop 5 and hop 6.

[0168] If each hop check passes, the UE will perform joint hop transmission (i.e., transmission using SL-PRS resources with the same transmission attributes) on each hop in the hop set (e.g., hops 1 and 2, hops 3 and 4, hops 5 and 6). This is similar to random selection and transmission with hop sets. There is no problem if the receiving UE can measure the SL-PRS resources on all hops in each hop set based on the sending UE using the same transmission attributes for all hops in each set. Otherwise, the receiving UE can request the sending UE to include other hop sets in the CBR and transmission calculation.

[0169] Figure 14A and Figure 14B Examples of SL-PRS resource transmission based on calculations of multi-hop-based SL-PRS congestion control metrics (e.g., RSSI, CBR, and CR) are illustrated according to various aspects of this disclosure. Figure 12 and Figure 13 As in the example, in Figure 14A and Figure 14B In the example, the UE is performing six frequency hops for SL-PRS resource transmission. That is, the SL-PRS resources span six frequency hops in the frequency domain. However, it should be understood that there may be more or fewer than six hops. These hops can be configured by the location server via auxiliary data (e.g., auxiliary data messages provided by LPP), by the base station (e.g., via RRC), or by the sidelink anchor UE (e.g., via SLPP).

[0170] As in Figure 13 As in the example, in Figure 14A and Figure 14B In the example, the UE calculates the SL-PRS congestion control metrics (e.g., RSSI, CBR, and CR) for the first hop in a set of two hops (e.g., hops 1 and 2, hops 3 and 4, hops 5 and 6). In Figure 1410, each of the three hop checks passes, and therefore, the UE sends SL-PRS resources on all six hops. In Figure 1430, the hop check for hop 3 fails, and therefore, the UE does not send SL-PRS resources on hops 3 and 4. In Figure 1450, the hop check for hop 5 fails, and therefore, the UE does not send SL-PRS resources on hops 5 and 6. In Figure 1470, the hop checks for hops 1 and 5 fail, and therefore, the UE does not send SL-PRS resources on hops 1, 2, 5, and 6.

[0171] In the case of multi-hop variable sets, such as Figure 14A and Figure 14B As illustrated, the UE can be configured by the upper layer using the following parameters: (1) requesting the minimum set of hops (i.e., the minimum number of hops) via CBR before the UE can use the time slot / opportunity for hop transmission; (2) requesting the minimum set of hops via CR before the UE can use the time slot / opportunity for hop transmission; and / or (3) requesting the minimum set of hops via RSSI before the UE can use the time slot / opportunity for hop transmission. For example, in the examples of Figures 1430 and 1450, the minimum set of hops is four hops, while in the example of Figure 1470, the minimum set of hops is two hops.

[0172] It should be noted that, although Figures 13 to 14B Two sets of transitions are illustrated, but it should be understood that each set of transitions may have more than two transitions.

[0173] In some cases, for jumps utilizing N SL-PRS resources (e.g., N=6, as in...), Figures 11 to 14B For a UE configured in the example, CBR and SL-RSSI can be calculated independently for each sidelink resource pool. However, for the SL-PRS transmission attribute of one of the aggregated SL-PRS resources to be adjusted, both the cross-hop CBR measurement and the per-hop CBR measurement should indicate that such transmission attribute adjustment should occur.

[0174] For example, if all SL-PRS resource hops in an SL-PRS resource hop are determined to be busy based on the per-hop CBR estimate, then the transmission attributes of all SL-PRS resource hops in the SL-PRS resource hop will be adjusted. However, if one of the N hops is not busy, then the transmission attributes will not be adjusted. The same technique can be used for the maximum number of SL-PRS (re)transmissions, the minimum periodicity of SL-PRS, the maximum number of SL-PRS resources in a time slot, the maximum comb size of SL-PRS resources in a time slot, and / or the maximum number of OFDM symbols for SL-PRS resources in a time slot.

[0175] In some cases, the SL-RSSI measurement definition and SL-CBR definition can be redefined for frequency-hopping SL-PRS resources, so that occupied OFDM symbols and / or occupied bandwidth / resource elements across aggregated SL-PRS resources are taken into account for the derived measurement.

[0176] For example, the SL-PRS CBR for at least N SL-PRS frequency hops used for positioning can be defined as follows. The SL-PRS CBR for a hop measured in time slot n can be defined as a portion of the SL-PRS resources associated with a given frequency hop, where the SL-PRS hop RSSI measured by the UE for that portion exceeds a (pre-)configured threshold sensed within the CBR measurement window [na, n-1], where a equals 100 or 100·2 according to the higher-layer parameter “sl-TimeWindowSizeCBR”. μ Each time slot.

[0177] The SL-PRS hopping RSSI for SL-PRS resource hopping can be defined as follows. The SL-PRS hopping RSSI for frequency hopping of SL-PRS resources can be defined as the linear average of the total received power (e.g., in watts) observed in the resource elements configured in the OFDM symbols of the time slots configured for the SL-PRS resource hopping starting from the second OFDM symbol, and in the sub-channels configured in the OFDM symbols of the time slots configured for the associated PSCCH starting from the second OFDM symbol and in the time slots of the OFDM symbols configured for the PSSCH starting from the second OFDM symbol.

[0178] The SL-PRS CR for SL-PRS resource transitions can be defined as follows. The SL-PRS transition CR evaluated at slot n can be defined as the total number of SL-PRS resources used for transmission in slot [na, n-1] with a given transition and the total number of SL-PRS resources granted in slot [n, n+b] divided by the total number of SL-PRS resources configured in the transmission pool at [na, n+b].

[0179] In some cases, a separate CBR calculation may exist for each frequency hop. In this case, the higher layer configures an independent CBR configuration for each sidelink resource pool. As a first option, all frequency hops in the frequency hop have the same CBR parameters, specifically, the RSSI threshold (given by the higher layer parameter "sl-ThreshS-RSSI-CBR-r16") and the CBR time window (given by the higher layer parameter "sl-TimeWindowSizeCBR-r16"). If all CBR parameters are identical across all location resource pools, the UE begins sidelink location aggregation. As a second option, all frequency hops in the frequency hop have different CBR parameters, specifically, the RSSI threshold (given by the higher layer parameter "sl-ThreshS-RSSI-CBR-r16") and the CBR time window (given by the higher layer parameter "sl-TimeWindowSizeCBR-r16").

[0180] The UE can be (pre)configured within the resource pool to perform either a single (i.e., cross-hop) CBR calculation or a per-hop CBR calculation. Higher layers configure the set of frequency hops required for the UE to perform CBR, CR, and RSSI calculations.

[0181] Figure 15 An example method 1500 for wireless communication according to various aspects of this disclosure is illustrated. In one aspect, method 1500 may be performed by a UE (e.g., any UE described herein).

[0182] At 1510, the UE receives a configuration for SL-PRS resources within the sidelink resource pool, wherein the configuration indicates multiple SL-PRS frequency hops for the SL-PRS resources, and wherein each of the multiple SL-PRS frequency hops has a bandwidth less than the total bandwidth of the sidelink resource pool. In one aspect, operation 1510 can be performed by one or more WWAN transceivers 310, one or more short-range radio transceivers 320, one or more processors 342, memory 340, and / or positioning components 348, any or all of which can be considered as components for performing the operation.

[0183] At 1520, the UE determines one or more congestion control metrics for each SL-PRS frequency hop in at least a subset of SL-PRS frequency hops. In one aspect, operation 1520 may be performed by one or more WWAN transceivers 310, one or more short-range radio transceivers 320, one or more processors 342, memory 340, and / or positioning components 348, any or all of which may be considered as components for performing the operation.

[0184] At 1530, the UE determines one or more SL-PRS transmission attributes for each SL-PRS frequency hop, at least in part, based on one or more congestion control metrics determined for each SL-PRS frequency hop subset. In one aspect, operation 1530 can be performed by one or more WWAN transceivers 310, one or more short-range radio transceivers 320, one or more processors 342, memory 340, and / or positioning components 348, any or all of which can be considered as components for performing the operation.

[0185] At 1540, the UE transmits SL-PRS resources on multiple SL-PRS frequency hops according to one or more SL-PRS transmission attributes for each SL-PRS frequency hop subset. In one aspect, operation 1540 can be performed by one or more WWAN transceivers 310, one or more short-range radio transceivers 320, one or more processors 342, memory 340, and / or positioning components 348, any or all of which can be considered as components for performing the operation.

[0186] It should be understood that the technical advantage of method 1500 is that method 1500 reduces the number of frequency hops that the UE needs to sense in order to transmit SL-PRS resources.

[0187] As can be seen in the detailed description above, different features are grouped together in the examples. This manner of disclosure should not be construed as an intention to have more features than those explicitly mentioned in each clause. Rather, the various aspects of this disclosure may include fewer features than those in the individual example clauses disclosed. Therefore, the following clauses should be regarded accordingly as incorporated into the description, where each clause may serve as a separate example. Although each dependent clause may refer in the clause to a specific combination with one of the other clauses, the aspect of that dependent clause is not limited to that specific combination. It should be understood that other example clauses may also include combinations of aspects of a dependent clause with the subject matter of any other dependent or independent clause, or combinations of any feature with other dependent and independent clauses. The various aspects disclosed herein explicitly include these combinations unless explicitly stated or readily inferred that a particular combination is not intended for use (e.g., contradictory aspects, such as defining an element as both an electrical insulator and an electrical conductor). Furthermore, it is contemplated that aspects of a clause may be included in any other independent clause, even if that clause does not directly depend on the independent clause.

[0188] Specific implementation examples are described in the following numbered clauses:

[0189] Clause 1. A method of wireless communication performed by a user equipment (UE), the method comprising: receiving a configuration for sidelink positioning reference signal (SL-PRS) resources within a sidelink resource pool, wherein the configuration indicates a plurality of SL-PRS frequency hops of the SL-PRS resources, and wherein each of the plurality of SL-PRS frequency hops has a bandwidth less than the total bandwidth of the sidelink resource pool; determining one or more congestion control metrics for each SL-PRS frequency hop in at least a subset of the plurality of SL-PRS frequency hops; determining one or more SL-PRS transmission attributes for the SL-PRS frequency hops based at least in part on the one or more congestion control metrics determined for each SL-PRS frequency hop in the subset of the SL-PRS frequency hops; and transmitting the SL-PRS resources on the plurality of SL-PRS frequency hops according to the one or more SL-PRS transmission attributes for each SL-PRS frequency hop in the subset of the SL-PRS frequency hops.

[0190] Clause 2. The method according to Clause 1, wherein: the subset of SL-PRS frequency hopping includes a single SL-PRS frequency hopping, and the one or more SL-PRS transmission attributes for each of the plurality of SL-PRS frequency hoppings are determined based on the one or more SL-PRS transmission attributes of the single SL-PRS frequency hopping.

[0191] Clause 3. The method according to Clause 2, wherein for the remaining SL-PRS frequency hops among the plurality of SL-PRS frequency hops, the maximum number of SL-PRS frequency hop transmissions, the maximum number of SL-PRS frequency hop retransmissions, or both, are determined based on the maximum number of SL-PRS frequency hop transmissions, the maximum number of SL-PRS frequency hop retransmissions, or both, of the single SL-PRS frequency hop.

[0192] Clause 4. The method according to any one of Clauses 2 to 3, wherein for the remaining SL-PRS frequency hops in the plurality of SL-PRS frequency hops, the maximum number of SL-PRS frequency hops per time slot, the maximum comb size per SL-PRS frequency hop per time slot, the maximum number of symbols per SL-PRS frequency hop per time slot, or any combination thereof, is determined based on the maximum number of SL-PRS frequency hops per time slot, the maximum comb size per SL-PRS frequency hop per time slot, the maximum number of symbols per SL-PRS frequency hop per time slot, or any combination thereof, of the single SL-PRS frequency hop.

[0193] Clause 5. The method according to any one of Clauses 2 to 4, wherein the single SL-PRS frequency hop is the first SL-PRS frequency hop to occur in time and frequency among the plurality of SL-PRS frequency hops.

[0194] Clause 6. The method according to Clause 1, wherein: the SL-PRS frequency hopping subset comprises two or more SL-PRS frequency hoppings, and the SL-PRS resources are transmitted on the plurality of SL-PRS frequency hoppings according to SL-PRS transmission attributes for the two or more SL-PRS frequency hoppings.

[0195] Clause 7. The method according to Clause 6, wherein: each of the two or more SL-PRS frequency hops is associated with at least one remaining SL-PRS frequency hop among the plurality of SL-PRS frequency hops, and the SL-PRS resources are transmitted on the SL-PRS frequency hop and the associated at least one remaining SL-PRS frequency hop according to the one or more SL-PRS transmission attributes of each of the two or more SL-PRS frequency hops.

[0196] Clause 8. The method according to any one of Clauses 6 to 7, wherein the configuration further indicates: a minimum number of hops required by Channel Busy Ratio (CBR) among the plurality of SL-PRS frequency hops before the UE is allowed to transmit the SL-PRS resource, a minimum number of hops required by Channel Occupancy Ratio (CR) among the plurality of SL-PRS frequency hops before the UE is allowed to transmit the SL-PRS resource, a minimum number of hops required by Sidelink Received Signal Strength Indicator (SL-RSSI) among the plurality of SL-PRS frequency hops before the UE is allowed to transmit the SL-PRS resource, or any combination thereof.

[0197] Clause 9. The method according to any one of Clauses 1 to 8, wherein the one or more SL-PRS transmission attributes for each SL-PRS frequency hop in the subset of said SL-PRS frequency hops are determined based on (1) a congestion control metric for all SL-PRS frequency hops across the plurality of SL-PRS frequency hops and (2) a congestion control metric for each SL-PRS frequency hop in the plurality of SL-PRS frequency hops.

[0198] Clause 10. The method according to any one of Clauses 1 to 9, wherein the maximum number of SL-PRS transmissions, the maximum number of SL-PRS retransmissions, or both are determined based on (1) a congestion control metric for all SL-PRS frequency hops across the plurality of SL-PRS frequency hops and (2) a congestion control metric for each of the plurality of SL-PRS frequency hops.

[0199] Clause 11. The method according to any one of Clauses 1 to 10, wherein the minimum periodicity of SL-PRS transmission, the maximum number of SL-PRS resources in a time slot, or both, is determined based on (1) a congestion control metric for all SL-PRS frequency hops across the plurality of SL-PRS frequency hops and (2) a congestion control metric for each of the plurality of SL-PRS frequency hops.

[0200] Clause 12. The method according to any one of Clauses 1 to 11, wherein the maximum comb size of the SL-PRS resource per time slot, the maximum number of SL-PRS resource symbols per time slot, or both are determined based on (1) a congestion control metric for all SL-PRS frequency hops across the plurality of SL-PRS frequency hops and (2) a congestion control metric for each of the plurality of SL-PRS frequency hops.

[0201] Clause 13. The method according to any one of Clauses 1 to 12, wherein the one or more congestion control metrics include: Channel Busy Ratio (CBR), Channel Occupancy Ratio (CR), Sidelink Received Signal Strength Indicator (SL-RSSI), or any combination thereof.

[0202] Clause 14. The method according to Clause 13, wherein the CBR is defined as a portion of the SL-PRS resources associated with a given SL-PRS frequency hop, the portion of which the SL-RSSI measured by the UE exceeds a threshold sensed within the CBR measurement window.

[0203] Clause 15. The method according to any one of Clauses 13 to 14, wherein the CR is defined as the total number of SL-PRS resources transmitted using a given SL-PRS frequency hopping in the set of previous time slots and the total number of SL-PRS resources granted in the set of subsequent time slots divided by the total number of configured SL-PRS resources in the sidelink resource pool.

[0204] Clause 16. The method according to any one of Clauses 1 to 15, wherein determining the one or more congestion control metrics for each SL-PRS frequency hop in at least the subset of said SL-PRS frequency hops comprises: determining the one or more congestion control metrics for each of the plurality of SL-PRS frequency hops.

[0205] Clause 17. The method according to Clause 16, wherein the configuration further indicates: either the same threshold to be applied to the one or more congestion control metrics for each of the plurality of SL-PRS frequency hops, or a different threshold to be applied to the one or more congestion control metrics for each of the plurality of SL-PRS frequency hops.

[0206] Clause 18. The method according to any one of Clauses 1 to 17, wherein the configuration further indicates whether to jointly determine the congestion control metric for all SL-PRS frequency hops of the plurality of SL-PRS frequency hops, or whether to determine the congestion control metric individually for each SL-PRS frequency hop of the plurality of SL-PRS frequency hops.

[0207] Clause 19. The method according to any one of Clauses 1 to 18, wherein the configuration is received from a location server, a base station, or a sidelink anchor UE.

[0208] Clause 20. The method according to any one of Clauses 1 to 19, wherein the UE is a capability-reduced (RedCap) UE.

[0209] Clause 21. The method according to any one of Clauses 1 to 20, wherein the one or more transmission attributes include: maximum transmission power, maximum number of SL-PRS transmissions, maximum number of SL-PRS retransmissions, minimum periodicity of SL-PRS, maximum number of SL-PRS resources per time slot, maximum comb size of SL-PRS resources in a time slot, maximum number of SL-PRS resource symbols per time slot, or any combination thereof.

[0210] Clause 22. A user equipment (UE) 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 being individually or in combination configured to: receive via the one or more transceivers a configuration for sidelink positioning reference signal (SL-PRS) resources within a sidelink resource pool, wherein the configuration indicates a plurality of SL-PRS frequency hops of the SL-PRS resources, and wherein each of the plurality of SL-PRS frequency hops has a bandwidth less than the total bandwidth of the sidelink resource pool. The bandwidth; determining one or more congestion control metrics for each SL-PRS frequency hop in at least a subset of the plurality of SL-PRS frequency hops; determining one or more SL-PRS transmission attributes for the SL-PRS frequency hops based at least in part on the one or more congestion control metrics determined for each SL-PRS frequency hop in the subset of the plurality of SL-PRS frequency hops; and transmitting the SL-PRS resources on the plurality of SL-PRS frequency hops via the one or more transceivers according to the one or more SL-PRS transmission attributes for each SL-PRS frequency hop in the subset of the plurality of SL-PRS frequency hops.

[0211] Clause 23. The UE as described in Clause 22, wherein: the subset of SL-PRS frequency hopping includes a single SL-PRS frequency hopping, and the one or more SL-PRS transmission attributes for each of the plurality of SL-PRS frequency hoppings are determined based on the one or more SL-PRS transmission attributes of the single SL-PRS frequency hopping.

[0212] Clause 24. The UE as described in Clause 23, wherein for the remaining SL-PRS frequency hops among the plurality of SL-PRS frequency hops, the maximum number of SL-PRS frequency hop transmissions, the maximum number of SL-PRS frequency hop retransmissions, or both, are determined based on the maximum number of SL-PRS frequency hop transmissions, the maximum number of SL-PRS frequency hop retransmissions, or both, of the single SL-PRS frequency hop.

[0213] Clause 25. The UE pursuant to any one of Clauses 23 to 24, wherein for the remaining SL-PRS frequency hops in the plurality of SL-PRS frequency hops, the maximum number of SL-PRS frequency hops per time slot, the maximum comb size per SL-PRS frequency hop per time slot, the maximum number of symbols per SL-PRS frequency hop per time slot, or any combination thereof, is determined based on the maximum number of SL-PRS frequency hops per time slot, the maximum comb size per SL-PRS frequency hop per time slot, the maximum number of symbols per SL-PRS frequency hop per time slot, or any combination thereof, of the single SL-PRS frequency hop.

[0214] Clause 26. The UE pursuant to any one of Clauses 23 to 25, wherein the single SL-PRS frequency hop is the first SL-PRS frequency hop to occur in time and frequency among the plurality of SL-PRS frequency hops.

[0215] Clause 27. The UE as described in Clause 22, wherein: the SL-PRS frequency hopping subset comprises two or more SL-PRS frequency hoppings, and the SL-PRS resources are transmitted on the plurality of SL-PRS frequency hoppings according to SL-PRS transmission attributes for the two or more SL-PRS frequency hoppings.

[0216] Clause 28. The UE as described in Clause 27, wherein: each of the two or more SL-PRS frequency hops is associated with at least one remaining SL-PRS frequency hop among the plurality of SL-PRS frequency hops, and the SL-PRS resources are transmitted on the SL-PRS frequency hop and the associated at least one remaining SL-PRS frequency hop according to the one or more SL-PRS transmission attributes of each of the two or more SL-PRS frequency hops.

[0217] Clause 29. A UE pursuant to any one of Clauses 27 to 28, wherein the configuration further indicates: a minimum number of hops required by Channel Busy Ratio (CBR) among the plurality of SL-PRS frequency hops before the UE is permitted to transmit the SL-PRS resources, a minimum number of hops required by Channel Occupancy Ratio (CR) among the plurality of SL-PRS frequency hops before the UE is permitted to transmit the SL-PRS resources, a minimum number of hops required by Sidelink Received Signal Strength Indicator (SL-RSSI) among the plurality of SL-PRS frequency hops before the UE is permitted to transmit the SL-PRS resources, or any combination thereof.

[0218] Clause 30. The UE pursuant to any one of Clauses 22 to 29, wherein the one or more SL-PRS transmission attributes for each SL-PRS frequency hop in the subset of said SL-PRS frequency hops are determined based on (1) a congestion control metric for all SL-PRS frequency hops across the plurality of SL-PRS frequency hops and (2) a congestion control metric for each SL-PRS frequency hop in the plurality of SL-PRS frequency hops.

[0219] Clause 31. The UE pursuant to any one of Clauses 22 to 30, wherein the maximum number of SL-PRS transmissions, the maximum number of SL-PRS retransmissions, or both are determined based on (1) a congestion control metric for all SL-PRS frequency hops across the plurality of SL-PRS frequency hops and (2) a congestion control metric for each of the plurality of SL-PRS frequency hops.

[0220] Clause 32. The UE according to any one of Clauses 22 to 31, wherein the minimum periodicity of SL-PRS transmission, the maximum number of SL-PRS resources in a time slot, or both, is determined based on (1) a congestion control metric for all SL-PRS frequency hops across the plurality of SL-PRS frequency hops and (2) a congestion control metric for each of the plurality of SL-PRS frequency hops.

[0221] Clause 33. The UE according to any one of Clauses 22 to 32, wherein the maximum comb size of the SL-PRS resource per time slot, the maximum number of SL-PRS resource symbols per time slot, or both are determined based on (1) a congestion control metric for all SL-PRS frequency hops across the plurality of SL-PRS frequency hops and (2) a congestion control metric for each of the plurality of SL-PRS frequency hops.

[0222] Clause 34. The UE pursuant to any one of Clauses 22 to 33, wherein the one or more congestion control metrics include: Channel Busy Ratio (CBR), Channel Occupied Ratio (CR), Sidelink Received Signal Strength Indicator (SL-RSSI), or any combination thereof.

[0223] Clause 35. The UE as described in Clause 34, wherein the CBR is defined as a portion of the SL-PRS resources associated with a given SL-PRS frequency hop, the portion of which the SL-RSSI measured by the UE exceeds a threshold sensed within the CBR measurement window.

[0224] Clause 36. The UE according to any one of Clauses 34 to 35, wherein the CR is defined as the total number of SL-PRS resources transmitted using a given SL-PRS frequency hop in the set of previous time slots and the total number of SL-PRS resources granted in the set of subsequent time slots divided by the total number of configured SL-PRS resources in the sidelink resource pool.

[0225] Clause 37. The UE according to any one of Clauses 22 to 36, wherein the one or more processors configured to determine the one or more congestion control metrics for each SL-PRS frequency hop in at least the subset of said SL-PRS frequency hops includes the one or more processors configured individually or in combination to perform: determining the one or more congestion control metrics for each of the plurality of SL-PRS frequency hops.

[0226] Clause 38. The UE as described in Clause 37, wherein the configuration further indicates either applying the same threshold to the one or more congestion control metrics for each of the plurality of SL-PRS frequency hops, or applying different thresholds to the one or more congestion control metrics for each of the plurality of SL-PRS frequency hops.

[0227] Clause 39. The UE pursuant to any one of Clauses 22 to 38, wherein the configuration further indicates whether the congestion control metric is determined jointly for all SL-PRS frequency hops of the plurality of SL-PRS frequency hops, or whether the congestion control metric is determined individually for each SL-PRS frequency hop of the plurality of SL-PRS frequency hops.

[0228] Clause 40. A UE pursuant to any one of Clauses 22 to 39, wherein the configuration is received from a location server, a base station, or a sidelink anchor UE.

[0229] Clause 41. A UE pursuant to any one of Clauses 22 to 40, wherein the UE is a capability-reduced (RedCap) UE.

[0230] Clause 42. The UE pursuant to any one of Clauses 22 to 41, wherein the one or more transmission attributes include: maximum transmission power, maximum number of SL-PRS transmissions, maximum number of SL-PRS retransmissions, minimum periodicity of SL-PRS, maximum number of SL-PRS resources per time slot, maximum comb size of SL-PRS resources in a time slot, maximum number of SL-PRS resource symbols per time slot, or any combination thereof.

[0231] Clause 43. A User Equipment (UE) comprising: means for receiving configuration for Sidelink Positioning Reference Signal (SL-PRS) resources within a sidelink resource pool, wherein the configuration indicates a plurality of SL-PRS frequency hops of the SL-PRS resources, and wherein each of the plurality of SL-PRS frequency hops has a bandwidth less than the total bandwidth of the sidelink resource pool; means for determining one or more congestion control metrics for each SL-PRS frequency hop in at least a subset of the plurality of SL-PRS frequency hops; means for determining one or more SL-PRS transmission attributes for the SL-PRS frequency hops, at least in part based on the one or more congestion control metrics determined for each SL-PRS frequency hop in the subset of SL-PRS frequency hops; and means for transmitting SL-PRS resources on the plurality of SL-PRS frequency hops according to the one or more SL-PRS transmission attributes for each SL-PRS frequency hop in the subset of SL-PRS frequency hops.

[0232] Clause 44. The UE as described in Clause 43, wherein: the subset of SL-PRS frequency hopping includes a single SL-PRS frequency hopping, and the one or more SL-PRS transmission attributes for each of the plurality of SL-PRS frequency hoppings are determined based on the one or more SL-PRS transmission attributes of the single SL-PRS frequency hopping.

[0233] Clause 45. The UE as described in Clause 44, wherein for the remaining SL-PRS frequency hops among the plurality of SL-PRS frequency hops, the maximum number of SL-PRS frequency hop transmissions, the maximum number of SL-PRS frequency hop retransmissions, or both, are determined based on the maximum number of SL-PRS frequency hop transmissions, the maximum number of SL-PRS frequency hop retransmissions, or both, of the single SL-PRS frequency hop.

[0234] Clause 46. The UE pursuant to any one of Clauses 44 to 45, wherein for the remaining SL-PRS frequency hops in the plurality of SL-PRS frequency hops, the maximum number of SL-PRS frequency hops per time slot, the maximum comb size per SL-PRS frequency hop per time slot, the maximum number of symbols per SL-PRS frequency hop per time slot, or any combination thereof, is determined based on the maximum number of SL-PRS frequency hops per time slot, the maximum comb size per SL-PRS frequency hop per time slot, the maximum number of symbols per SL-PRS frequency hop per time slot, or any combination thereof, of the single SL-PRS frequency hop.

[0235] Clause 47. The UE pursuant to any one of Clauses 44 to 46, wherein the single SL-PRS frequency hop is the first SL-PRS frequency hop to occur in time and frequency among the plurality of SL-PRS frequency hops.

[0236] Clause 48. The UE as described in Clause 43, wherein: the SL-PRS frequency hopping subset comprises two or more SL-PRS frequency hoppings, and the SL-PRS resources are transmitted on the plurality of SL-PRS frequency hoppings according to SL-PRS transmission attributes for the two or more SL-PRS frequency hoppings.

[0237] Clause 49. The UE as described in Clause 48, wherein: each of the two or more SL-PRS frequency hops is associated with at least one remaining SL-PRS frequency hop among the plurality of SL-PRS frequency hops, and the SL-PRS resources are transmitted on the SL-PRS frequency hop and the associated at least one remaining SL-PRS frequency hop according to the one or more SL-PRS transmission attributes of each of the two or more SL-PRS frequency hops.

[0238] Clause 50. A UE pursuant to any one of Clauses 48 to 49, wherein the configuration further indicates: a minimum number of hops required by Channel Busy Ratio (CBR) among the plurality of SL-PRS frequency hops before the UE is permitted to transmit the SL-PRS resource, a minimum number of hops required by Channel Occupancy Ratio (CR) among the plurality of SL-PRS frequency hops before the UE is permitted to transmit the SL-PRS resource, a minimum number of hops required by Sidelink Received Signal Strength Indicator (SL-RSSI) among the plurality of SL-PRS frequency hops before the UE is permitted to transmit the SL-PRS resource, or any combination thereof.

[0239] Clause 51. The UE pursuant to any one of Clauses 43 to 50, wherein the one or more SL-PRS transmission attributes for each SL-PRS frequency hop in the subset of said SL-PRS frequency hops are determined based on (1) a congestion control metric for all SL-PRS frequency hops across the plurality of SL-PRS frequency hops and (2) a congestion control metric for each SL-PRS frequency hop in the plurality of SL-PRS frequency hops.

[0240] Clause 52. The UE pursuant to any one of Clauses 43 to 51, wherein the maximum number of SL-PRS transmissions, the maximum number of SL-PRS retransmissions, or both are determined based on (1) a congestion control metric for all SL-PRS frequency hops across the plurality of SL-PRS frequency hops and (2) a congestion control metric for each of the plurality of SL-PRS frequency hops.

[0241] Clause 53. The UE according to any one of Clauses 43 to 52, wherein the minimum periodicity of SL-PRS transmission, the maximum number of SL-PRS resources in a time slot, or both, is determined based on (1) a congestion control metric for all SL-PRS frequency hops across the plurality of SL-PRS frequency hops and (2) a congestion control metric for each of the plurality of SL-PRS frequency hops.

[0242] Clause 54. The UE according to any one of Clauses 43 to 53, wherein the maximum comb size of the SL-PRS resource per time slot, the maximum number of SL-PRS resource symbols per time slot, or both are determined based on (1) a congestion control metric for all SL-PRS frequency hops across the plurality of SL-PRS frequency hops and (2) a congestion control metric for each of the plurality of SL-PRS frequency hops.

[0243] Clause 55. The UE pursuant to any one of Clauses 43 to 54, wherein the one or more congestion control metrics include: Channel Busy Ratio (CBR), Channel Occupancy Ratio (CR), Sidelink Received Signal Strength Indicator (SL-RSSI), or any combination thereof.

[0244] Clause 56. The UE as described in Clause 55, wherein the CBR is defined as a portion of the SL-PRS resources associated with a given SL-PRS frequency hop, the portion of which the SL-RSSI measured by the UE exceeds a threshold sensed within the CBR measurement window.

[0245] Clause 57. The UE according to any one of Clauses 55 to 56, wherein the CR is defined as the total number of SL-PRS resources transmitted using a given SL-PRS frequency hop in the set of previous time slots and the total number of SL-PRS resources granted in the set of subsequent time slots divided by the total number of configured SL-PRS resources in the sidelink resource pool.

[0246] Clause 58. The UE according to any one of Clauses 43 to 57, wherein the component for determining the one or more congestion control metrics for each SL-PRS frequency hop in at least the subset of said SL-PRS frequency hops includes: a component for determining the one or more congestion control metrics for each of the plurality of SL-PRS frequency hops.

[0247] Clause 59. The UE as described in Clause 58, wherein the configuration further indicates either applying the same threshold to the one or more congestion control metrics for each of the plurality of SL-PRS frequency hops, or applying different thresholds to the one or more congestion control metrics for each of the plurality of SL-PRS frequency hops.

[0248] Clause 60. The UE pursuant to any one of Clauses 43 to 59, wherein the configuration further indicates whether the congestion control metric is determined jointly for all SL-PRS frequency hops of the plurality of SL-PRS frequency hops, or whether the congestion control metric is determined individually for each SL-PRS frequency hop of the plurality of SL-PRS frequency hops.

[0249] Clause 61. A UE pursuant to any one of Clauses 43 to 60, wherein the configuration is received from a location server, a base station, or a sidelink anchor UE.

[0250] Clause 62. The UE pursuant to any one of Clauses 43 to 61, wherein the UE is a capability-reduced (RedCap) UE.

[0251] Clause 63. The UE pursuant to any one of Clauses 43 to 62, wherein the one or more transmission attributes include: maximum transmission power, maximum number of SL-PRS transmissions, maximum number of SL-PRS retransmissions, minimum periodicity of SL-PRS, maximum number of SL-PRS resources per time slot, maximum comb size of SL-PRS resources in a time slot, maximum number of SL-PRS resource symbols per time slot, or any combination thereof.

[0252] Clause 64. A non-transitory computer-readable medium storing computer-executable instructions, which, when executed by a user equipment (UE), cause the UE to: receive a configuration for sidelink positioning reference signal (SL-PRS) resources within a sidelink resource pool, wherein the configuration indicates a plurality of SL-PRS frequency hops for the SL-PRS resources, and wherein each of the plurality of SL-PRS frequency hops has a bandwidth less than the total bandwidth of the sidelink resource pool; determine one or more congestion control metrics for each SL-PRS frequency hop in at least a subset of the plurality of SL-PRS frequency hops; determine one or more SL-PRS transmission attributes for the SL-PRS frequency hops based at least in part on the one or more congestion control metrics determined for each SL-PRS frequency hop in the subset of the SL-PRS frequency hops; and transmit the SL-PRS resources on the plurality of SL-PRS frequency hops according to the one or more SL-PRS transmission attributes for each SL-PRS frequency hop in the subset of the SL-PRS frequency hops.

[0253] Clause 65. The non-transitory computer-readable medium according to Clause 64, wherein: the subset of SL-PRS frequency hopping includes a single SL-PRS frequency hopping, and the one or more SL-PRS transmission attributes for each of the plurality of SL-PRS frequency hoppings are determined based on the one or more SL-PRS transmission attributes of the single SL-PRS frequency hopping.

[0254] Clause 66. The non-transitory computer-readable medium as described in Clause 65, wherein for the remaining SL-PRS frequency hops among the plurality of SL-PRS frequency hops, the maximum number of SL-PRS frequency hop transmissions, the maximum number of SL-PRS frequency hop retransmissions, or both, are determined based on the maximum number of SL-PRS frequency hop transmissions, the maximum number of SL-PRS frequency hop retransmissions, or both, of the single SL-PRS frequency hop.

[0255] Clause 67. A non-transitory computer-readable medium pursuant to any one of Clauses 65 to 66, wherein for the remaining SL-PRS frequency hops in the plurality of SL-PRS frequency hops, the maximum number of SL-PRS frequency hops per time slot, the maximum comb size per SL-PRS frequency hop per time slot, the maximum number of symbols per SL-PRS frequency hop per time slot, or any combination thereof, is determined based on the maximum number of SL-PRS frequency hops per time slot, the maximum comb size per SL-PRS frequency hop per time slot, the maximum number of symbols per SL-PRS frequency hop per time slot, or any combination thereof, of the single SL-PRS frequency hop.

[0256] Clause 68. A non-transitory computer-readable medium according to any one of Clauses 65 to 67, wherein the single SL-PRS frequency hop is the first SL-PRS frequency hop to occur in time and frequency among the plurality of SL-PRS frequency hops.

[0257] Clause 69. The non-transitory computer-readable medium according to Clause 64, wherein: the subset of SL-PRS frequency hopping includes two or more SL-PRS frequency hoppings, and the SL-PRS resources are transmitted on the plurality of SL-PRS frequency hoppings according to SL-PRS transmission attributes for the two or more SL-PRS frequency hoppings.

[0258] Clause 70. The non-transitory computer-readable medium according to Clause 69, wherein: each of the two or more SL-PRS frequency hops is associated with at least one remaining SL-PRS frequency hop, and the SL-PRS resource is transmitted on the SL-PRS frequency hop and the associated at least one remaining SL-PRS frequency hop according to the one or more SL-PRS transmission attributes of each of the two or more SL-PRS frequency hops.

[0259] Clause 71. A non-transitory computer-readable medium according to any one of Clauses 69 to 70, wherein the configuration further indicates: a minimum number of hops required by Channel Busy Ratio (CBR) among the plurality of SL-PRS frequency hops before the UE is allowed to transmit the SL-PRS resource, a minimum number of hops required by Channel Occupancy Ratio (CR) among the plurality of SL-PRS frequency hops before the UE is allowed to transmit the SL-PRS resource, a minimum number of hops required by Sidelink Received Signal Strength Indicator (SL-RSSI) among the plurality of SL-PRS frequency hops before the UE is allowed to transmit the SL-PRS resource, or any combination thereof.

[0260] Clause 72. A nontransitory computer-readable medium according to any one of Clauses 64 to 71, wherein the one or more SL-PRS transmission attributes for each SL-PRS frequency hop in the subset of said SL-PRS frequency hops are determined based on (1) a congestion control metric for all SL-PRS frequency hops across the plurality of SL-PRS frequency hops and (2) a congestion control metric for each of the plurality of SL-PRS frequency hops.

[0261] Clause 73. A nontransitory computer-readable medium according to any one of Clauses 64 to 72, wherein the maximum number of SL-PRS transmissions, the maximum number of SL-PRS retransmissions, or both are determined based on (1) a congestion control metric for all SL-PRS frequency hops across the plurality of SL-PRS frequency hops and (2) a congestion control metric for each of the plurality of SL-PRS frequency hops.

[0262] Clause 74. A nontransitory computer-readable medium according to any one of Clauses 64 to 73, wherein the minimum periodicity of SL-PRS transmission, the maximum number of SL-PRS resources in a time slot, or both, is determined based on (1) a congestion control metric for all SL-PRS frequency hops across the plurality of SL-PRS frequency hops and (2) a congestion control metric for each of the plurality of SL-PRS frequency hops.

[0263] Clause 75. A nontransitory computer-readable medium according to any one of Clauses 64 to 74, wherein the maximum comb size of the SL-PRS resource per time slot, the maximum number of SL-PRS resource symbols per time slot, or both are determined based on (1) a congestion control metric for all SL-PRS frequency hops across the plurality of SL-PRS frequency hops and (2) a congestion control metric for each of the plurality of SL-PRS frequency hops.

[0264] Clause 76. A non-transitory computer-readable medium pursuant to any one of Clauses 64 to 75, wherein the one or more congestion control metrics include: Channel Busy Ratio (CBR), Channel Occupancy Ratio (CR), Sidelink Received Signal Strength Indicator (SL-RSSI), or any combination thereof.

[0265] Clause 77. The non-transitory computer-readable medium as described in Clause 76, wherein the CBR is defined as a portion of the SL-PRS resource associated with a given SL-PRS frequency hopping, the portion of which the SL-RSSI measured by the UE exceeds a threshold sensed within the CBR measurement window.

[0266] Clause 78. A nontransitory computer-readable medium according to any one of Clauses 76 to 77, wherein the CR is defined as the total number of SL-PRS resources transmitted using a given SL-PRS frequency hopping in the set of previous time slots and the total number of SL-PRS resources permitted in the set of subsequent time slots divided by the total number of configured SL-PRS resources in the sidelink resource pool.

[0267] Clause 79. A non-transitory computer-readable medium according to any one of Clauses 64 to 78, wherein the computer-executable instructions that, when executed by the UE, cause the UE to determine the one or more congestion control metrics for each SL-PRS frequency hop in at least the subset of SL-PRS frequency hops, include computer-executable instructions that, when executed by the UE, cause the UE to perform the following operation: determine the one or more congestion control metrics for each of the plurality of SL-PRS frequency hops.

[0268] Clause 80. The non-transitory computer-readable medium pursuant to Clause 79, wherein the configuration further indicates either the same threshold to be applied to the one or more congestion control metrics for each of the plurality of SL-PRS frequency hops, or a different threshold to be applied to the one or more congestion control metrics for each of the plurality of SL-PRS frequency hops.

[0269] Clause 81. A non-transitory computer-readable medium according to any one of Clauses 64 to 80, wherein the configuration further indicates whether a congestion control metric is jointly determined for all SL-PRS frequency hops of the plurality of SL-PRS frequency hops, or whether the congestion control metric is determined individually for each SL-PRS frequency hop of the plurality of SL-PRS frequency hops.

[0270] Clause 82. A non-transitory computer-readable medium pursuant to any one of Clauses 64 to 81, wherein the configuration is received from a location server, a base station, or a sidelink anchor UE.

[0271] Clause 83. A non-transitory computer-readable medium pursuant to any one of Clauses 64 to 82, wherein the UE is a capability-reduced (RedCap) UE.

[0272] Clause 84. A nontransitory computer-readable medium pursuant to any one of Clauses 64 to 83, wherein the one or more transmission attributes include: maximum transmission power, maximum number of SL-PRS transmissions, maximum number of SL-PRS retransmissions, minimum periodicity of SL-PRS, maximum number of SL-PRS resources per time slot, maximum comb size of SL-PRS resources in a time slot, maximum number of SL-PRS resource symbols per time slot, or any combination thereof.

[0273] Those skilled in the art will understand that information and signals can be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0274] Furthermore, those skilled in the art will understand that the various exemplary logic blocks, modules, circuits, and algorithm steps described in connection with the aspects disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability between hardware and software, various exemplary components, blocks, modules, circuits, and steps have been described above in general terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in different ways for each specific application, but such specific implementation decisions should not be construed as departing from the scope of this disclosure.

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

[0276] The methods, sequences, and / or algorithms described in conjunction with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or a combination of both. The 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 disks, removable disks, CD-ROMs, or any other form of storage medium known in the art. Example storage media are coupled to a processor such that the processor can read information from and write information to the storage medium. Alternatively, the storage medium may be integral with the processor. The processor and storage medium may reside in an ASIC. The ASIC may reside in a user terminal (e.g., a UE). Alternatively, the processor and storage medium may reside as discrete components in the user terminal.

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

[0278] While the foregoing disclosure illustrates exemplary aspects of this disclosure, it should be noted that various changes and modifications may be made herein without departing from the scope of this disclosure as defined by the appended claims. For example, the functions, steps, and / or actions of the method claims according to aspects of this disclosure described herein need not be performed in any particular order. Furthermore, no component, function, action, or instruction described or claimed herein should be construed as critical or essential unless explicitly stated otherwise. Additionally, as used herein, the terms “set,” “group,” etc., are intended to include one or more of the stated elements. Moreover, as used herein, the terms “having,” “comprising,” “including,” etc., do not exclude the presence of one or more additional elements (e.g., element “having” A may also have B). Furthermore, the phrase “based on” is intended to mean “at least partially based on” unless otherwise explicitly stated. Furthermore, as used herein, the term “or” is intended to be open-ended when used in a series and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., if used in conjunction with “any” or “only one”), or these alternatives are mutually exclusive (e.g., “one or more” should not be interpreted as “one and more”). Additionally, although components, functions, actions, and instructions may be described or claimed in the singular, plural forms may also be considered unless explicitly stated to be limited to the singular. Therefore, as used herein, the articles “a,” “an,” “the,” and “described” are intended to include one or more of the stated elements. Additionally, as used herein, the terms “at least one” and “one or more” include “one” component, function, action, or instruction that performs or is capable of performing the described or claimed functionality, and also include “two or more” components, functions, actions, or instructions that perform or are capable of performing the described or claimed functionality in combination.

Claims

1. A user equipment (UE), the user equipment (UE) comprising: One or more memory units; One or more transceivers; and One or more processors, communicatively coupled to one or more memories and one or more transceivers, wherein the one or more processors are configured individually or in combination to: The configuration for sidelink positioning reference signal (SL-PRS) resources within a sidelink resource pool is received via the one or more transceivers, wherein the configuration indicates a plurality of SL-PRS frequency hoppings of the SL-PRS resources, and wherein each of the plurality of SL-PRS frequency hoppings has a bandwidth less than the total bandwidth of the sidelink resource pool. For each SL-PRS frequency hop in at least a subset of the plurality of SL-PRS frequency hops, one or more congestion control metrics are determined. At least in part, based on the one or more congestion control metrics determined for each SL-PRS frequency hop in the subset of SL-PRS frequency hops, one or more SL-PRS transmission attributes for the SL-PRS frequency hops are determined; and The SL-PRS resources are transmitted via the one or more transceivers on the plurality of SL-PRS frequency hops according to the one or more SL-PRS transmission attributes for each SL-PRS frequency hop subset.

2. The UE according to claim 1, wherein: The SL-PRS frequency hopping subset includes a single SL-PRS frequency hopping, and The one or more SL-PRS transmission attributes for each of the plurality of SL-PRS frequency hops are determined based on the one or more SL-PRS transmission attributes for the single SL-PRS frequency hop.

3. The UE according to claim 2, wherein for the remaining SL-PRS frequency hops among the plurality of SL-PRS frequency hops, the maximum number of SL-PRS frequency hop transmissions, the maximum number of SL-PRS frequency hop retransmissions, or both, are determined based on the maximum number of SL-PRS frequency hop transmissions, the maximum number of SL-PRS frequency hop retransmissions, or both, of the single SL-PRS frequency hop.

4. The UE according to claim 2, wherein for the remaining SL-PRS frequency hops in the plurality of SL-PRS frequency hops, the maximum number of SL-PRS frequency hops per time slot, the maximum comb size per SL-PRS frequency hop per time slot, the maximum number of symbols per SL-PRS frequency hop per time slot, or any combination thereof, is determined based on the maximum number of SL-PRS frequency hops per time slot, the maximum comb size per SL-PRS frequency hop per time slot, the maximum number of symbols per SL-PRS frequency hop per time slot, or any combination thereof, of the single SL-PRS frequency hop.

5. The UE according to claim 2, wherein the single SL-PRS frequency hop is the first SL-PRS frequency hop to occur in time and frequency among the plurality of SL-PRS frequency hops.

6. The UE according to claim 1, wherein: The SL-PRS frequency hopping subset includes two or more SL-PRS frequency hoppings, and The SL-PRS resources are transmitted on the plurality of SL-PRS frequency transitions according to the SL-PRS transmission attributes for the two or more SL-PRS frequency transitions.

7. The UE according to claim 6, wherein: Each of the two or more SL-PRS frequency transitions is associated with at least one remaining SL-PRS frequency transition among the plurality of SL-PRS frequency transitions, and The SL-PRS resources are transmitted on the SL-PRS frequency hop and the associated at least one remaining SL-PRS frequency hop according to the SL-PRS transmission attributes of each of the two or more SL-PRS frequency hops.

8. The UE of claim 6, wherein the configuration further indicates: The minimum number of hops required by the Channel Busy Ratio (CBR) requirement among the multiple SL-PRS frequency hops before the UE is allowed to transmit the SL-PRS resources. The minimum number of hops required by the channel occupancy ratio (CR) requirement among the multiple SL-PRS frequency hops before the UE is allowed to transmit the SL-PRS resources. The minimum number of SL-PRS frequency hops required by the Sidelink Receive Signal Strength Indicator (SL-RSSI) among the plurality of SL-PRS frequency hops before the UE is allowed to transmit the SL-PRS resources, or Any combination of them.

9. The UE of claim 1, wherein the one or more SL-PRS transmission attributes for each SL-PRS frequency hop in the subset of SL-PRS frequency hops are determined based on (1) a congestion control metric for all SL-PRS frequency hops across the plurality of SL-PRS frequency hops and (2) a congestion control metric for each SL-PRS frequency hop in the plurality of SL-PRS frequency hops.

10. The UE of claim 1, wherein the maximum number of SL-PRS transmissions, the maximum number of SL-PRS retransmissions, or both are determined based on (1) a congestion control metric for all SL-PRS frequency hops across the plurality of SL-PRS frequency hops and (2) a congestion control metric for each of the plurality of SL-PRS frequency hops.

11. The UE of claim 1, wherein the minimum periodicity of SL-PRS transmission, the maximum number of SL-PRS resources in a time slot, or both are determined based on (1) a congestion control metric for all SL-PRS frequency hops across the plurality of SL-PRS frequency hops and (2) a congestion control metric for each SL-PRS frequency hop in the plurality of SL-PRS frequency hops.

12. The UE of claim 1, wherein the maximum comb size of the SL-PRS resource per time slot, the maximum number of SL-PRS resource symbols per time slot, or both are determined based on (1) a congestion control metric for all SL-PRS frequency hops across the plurality of SL-PRS frequency hops and (2) a congestion control metric for each SL-PRS frequency hop in the plurality of SL-PRS frequency hops.

13. The UE of claim 1, wherein the one or more congestion control metrics include: Channel Busy Ratio (CBR) Channel occupancy ratio (CR) Sidelink Received Signal Strength Indicator (SL-RSSI), or Any combination of them.

14. The UE of claim 1, wherein the one or more processors configured to determine the one or more congestion control metrics for each SL-PRS frequency hop in at least the subset of SL-PRS frequency hops include the one or more processors individually or in combination configured to perform the following operations: For each of the plurality of SL-PRS frequency transitions, determine one or more congestion control metrics.

15. The UE of claim 16, wherein the configuration further indicates: The same threshold should be applied to the one or more congestion control metrics for each of the plurality of SL-PRS frequency transitions, or Different thresholds are to be applied to the one or more congestion control metrics for each of the plurality of SL-PRS frequency transitions.

16. The UE of claim 1, wherein the configuration further indicates: Whether to jointly determine the congestion control metric for all SL-PRS frequency transitions among the multiple SL-PRS frequency transitions, or Whether the congestion control metric is determined individually for each of the plurality of SL-PRS frequency transitions.

17. The UE of claim 1, wherein the UE is a capability-reduced (RedCap) UE.

18. The UE of claim 1, wherein the one or more transmission attributes include: Maximum transmission power, Maximum number of SL-PRS transmissions Maximum number of SL-PRS retransmissions Minimal periodicity of SL-PRS Maximum number of SL-PRS resources per time slot Maximum comb size of SL-PRS resources in a time slot The maximum number of SL-PRS resource symbols per time slot, or Any combination of them.

19. A method for wireless communication performed by a user equipment (UE), the method comprising: Receive configuration for sidelink positioning reference signal (SL-PRS) resources within a sidelink resource pool, wherein the configuration indicates a plurality of SL-PRS frequency hoppings of the SL-PRS resources, and wherein each of the plurality of SL-PRS frequency hoppings has a bandwidth less than the total bandwidth of the sidelink resource pool. For each SL-PRS frequency hop in at least a subset of the plurality of SL-PRS frequency hops, one or more congestion control metrics are determined. At least in part, based on the one or more congestion control metrics determined for each SL-PRS frequency hop in the subset of SL-PRS frequency hops, one or more SL-PRS transmission attributes for the SL-PRS frequency hops are determined; and The SL-PRS resources are transmitted on the plurality of SL-PRS frequency hops according to the one or more SL-PRS transmission attributes for each SL-PRS frequency hop subset.

20. A user equipment (UE), the user equipment (UE) comprising: A component for receiving a configuration for a sidelink positioning reference signal (SL-PRS) resource within a sidelink resource pool, wherein the configuration indicates a plurality of SL-PRS frequency hoppings of the SL-PRS resource, and wherein each of the plurality of SL-PRS frequency hoppings has a bandwidth less than the total bandwidth of the sidelink resource pool. A component for determining one or more congestion control metrics for each SL-PRS frequency hop in at least a subset of the plurality of SL-PRS frequency hops. The component is used to: determine one or more SL-PRS transmission attributes for the SL-PRS frequency hops, based at least in part on the one or more congestion control metrics determined for each SL-PRS frequency hop subset. and The component is used to transmit the SL-PRS resources on the plurality of SL-PRS frequency hops according to the one or more SL-PRS transmission attributes for each SL-PRS frequency hop subset.

Images