[go: up one dir, main page]

WO2025117049A1 - Agrégation de groupes de ressources de liaison latérale pour positionnement - Google Patents

Agrégation de groupes de ressources de liaison latérale pour positionnement Download PDF

Info

Publication number
WO2025117049A1
WO2025117049A1 PCT/US2024/050919 US2024050919W WO2025117049A1 WO 2025117049 A1 WO2025117049 A1 WO 2025117049A1 US 2024050919 W US2024050919 W US 2024050919W WO 2025117049 A1 WO2025117049 A1 WO 2025117049A1
Authority
WO
WIPO (PCT)
Prior art keywords
aggregated
prs
resource
configuration
sidelink
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/US2024/050919
Other languages
English (en)
Inventor
Alexandros MANOLAKOS
Mukesh Kumar
Gabi Sarkis
Sony Akkarakaran
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Qualcomm Inc
Original Assignee
Qualcomm Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qualcomm Inc filed Critical Qualcomm Inc
Publication of WO2025117049A1 publication Critical patent/WO2025117049A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0037—Inter-user or inter-terminal allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A) or DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A) or DMT the frequencies being arranged in component carriers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signalling for the administration of the divided path, e.g. signalling of configuration information
    • H04L5/0094—Indication of how sub-channels of the path are allocated

Definitions

  • Wireless communication systems have developed through various generations, including a first-generation analog wireless phone service (1G), a second-generation (2G) digital wireless phone service (including interim 2.5G and 2.75G networks), a third-generation (3G) high speed data, Internet-capable wireless service and a fourth-generation (4G) service (e.g., Long Term Evolution (LTE) or WiMax).
  • a first-generation analog wireless phone service (1G) 1G
  • a second-generation (2G) digital wireless phone service including interim 2.5G and 2.75G networks
  • 3G third-generation
  • 4G fourth-generation
  • LTE Long Term Evolution
  • PCS personal communications service
  • Examples of known cellular systems include the cellular analog advanced mobile phone system (AMPS), and digital cellular systems based on code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), the Global System for Mobile communications (GSM), etc.
  • CDMA code division multiple access
  • FDMA frequency division multiple access
  • TDMA time division multiple access
  • GSM
  • a fifth generation (5G) wireless standard referred to as New Radio (NR)
  • NR New Radio
  • the 5G standard according to the Next Generation Mobile Networks Alliance, is designed to provide higher data rates as compared to previous standards, more accurate positioning (e.g., based on reference signals for positioning (RS-P), such as downlink, uplink, or sidelink positioning reference signals (PRS)), and other technical enhancements.
  • RS-P reference signals for positioning
  • PRS sidelink positioning reference signals
  • RS-P reference signals for positioning
  • PRS sidelink positioning reference signals
  • a method of operating a user equipment includes determining a first resource configuration associated with a first sidelink resource pool for positioning (SL- RP-P); determining a second resource configuration associated with a second SL-RP-P, wherein the first SL-RP-P and the second SL-RP-P belong to a set of aggregated SL-RP- Ps associated with an aggregated SL-RP-P configuration with one or more common parameters; and communicating SL-PRS via the set of aggregated SL-RP-Ps based on the aggregated SL-RP-P configuration.
  • SL- RP-P sidelink resource pool for positioning
  • a method of operating a position estimation entity includes determining a first resource configuration associated with a first sidelink resource pool for positioning (SL-RP-P); determining a second resource configuration associated with a second SL- RP-P; determining to aggregate the first SL-RP-P and the second SL-RP-P in a set of aggregated SL-RP-Ps associated with an aggregated SL-RP-P configuration with one or more common parameters; and transmitting an indication of the aggregated SL-RP-P configuration to at least one user equipment (UE).
  • UE user equipment
  • a user equipment includes one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors, either alone or in combination, configured to: determine a first resource configuration associated with a first sidelink resource pool for positioning (SL-RP-P); determine a second resource configuration associated with a second SL-RP-P, wherein the first SL-RP-P and the second SL-RP-P belong to a set of aggregated SL-RP-Ps associated with an aggregated SL-RP-P configuration with one or more common parameters; and communicate, via the one or more transceivers, SL-PRS via the set of aggregated SL-RP-Ps based on the aggregated SL-RP-P configuration.
  • SL-RP-P sidelink resource pool for positioning
  • a position estimation entity includes one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors, either alone or in combination, configured to: determine a first resource configuration associated with a first sidelink resource pool for positioning (SL-RP-P); determine a second resource configuration associated with a second SL-RP-P; determine to aggregate the first SL-RP- P and the second SL-RP-P in a set of aggregated SL-RP-Ps associated with an aggregated SL-RP-P configuration with one or more common parameters; and transmit, via the one or more transceivers, an indication of the aggregated SL-RP-P configuration to at least one user equipment (UE).
  • UE user equipment
  • a user equipment includes means for determining a first resource configuration associated with a first sidelink resource pool for positioning (SL-RP-P); means for determining a second resource configuration associated with a second SL-RP- P, wherein the first SL-RP-P and the second SL-RP-P belong to a set of aggregated SL- RP-Ps associated with an aggregated SL-RP-P configuration with one or more common parameters; and means for communicating SL-PRS via the set of aggregated SL-RP-Ps based on the aggregated SL-RP-P configuration.
  • SL-RP-P sidelink resource pool for positioning
  • a position estimation entity includes means for determining a first resource configuration associated with a first sidelink resource pool for positioning (SL-RP-P); means for determining a second resource configuration associated with a second SL-RP- P; means for determining to aggregate the first SL-RP-P and the second SL-RP-P in a set of aggregated SL-RP-Ps associated with an aggregated SL-RP-P configuration with one or more common parameters; and means for transmitting an indication of the aggregated SL-RP-P configuration to at least one user equipment (UE).
  • UE user equipment
  • a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: determine a first resource configuration associated with a first sidelink resource pool for positioning (SL-RP-P); determine a second resource configuration associated with a second SL-RP- P, wherein the first SL-RP-P and the second SL-RP-P belong to a set of aggregated SL- RP-Ps associated with an aggregated SL-RP-P configuration with one or more common parameters; and communicate SL-PRS via the set of aggregated SL-RP-Ps based on the aggregated SL-RP-P configuration.
  • SL-RP-P sidelink resource pool for positioning
  • a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a position estimation entity, cause the position estimation entity to: determine a first resource configuration associated with a first sidelink resource pool for positioning (SL-RP-P); determine a second resource configuration associated with a second SL-RP-P; determine to aggregate the first SL-RP- P and the second SL-RP-P in a set of aggregated SL-RP-Ps associated with an aggregated SL-RP-P configuration with one or more common parameters; and transmit an indication of the aggregated SL-RP-P configuration to at least one user equipment (UE).
  • UE user equipment
  • FIG. 1 illustrates an example wireless communications system, according to aspects of the disclosure.
  • FIGS. 2A, 2B, and 2C illustrate example wireless network structures, according to aspects of the disclosure.
  • FIGS. 3A, 3B, and 3C are simplified block diagrams of several sample aspects of components that may be employed in a user equipment (UE), a base station, and a network entity, respectively, and configured to support communications as taught herein.
  • UE user equipment
  • base station base station
  • network entity network entity
  • FIG. 4 is a diagram illustrating an example frame structure, according to aspects of the disclosure.
  • FIGS. 5A and 5B are diagrams of example sidelink slot structures with and without feedback resources, according to aspects of the disclosure.
  • FIG. 6 is a diagram showing how a shared channel (SCH) is established on a sidelink between two or more UEs, according to aspects of the disclosure.
  • SCH shared channel
  • FIG. 7 is a diagram illustrating an example of a resource pool for positioning configured within a sidelink resource pool for communication, according to aspects of the disclosure.
  • FIGS. 8A-8B illustrate diagrams illustrating additional examples of resource pools for positioning configured within sidelink resource pools for communication.
  • FIG. 9 illustrates a diagram illustrating another example of a resource pool for positioning configured within a sidelink resource pool for communication.
  • FIG. 10 illustrates an exemplary process of communications according to an aspect of the disclosure.
  • FIG. 11 illustrates an exemplary process of communications according to an aspect of the disclosure.
  • FIG. 12 illustrates a set of aggregated sidelink (SL) resource pools, in accordance with an example implementation of the processes of FIGS. 10-11, respectively.
  • FIG. 13 illustrates a set of aggregated SL resource pools, in accordance with an example implementation of the processes of FIGS. 10-11, respectively.
  • FIG. 14 illustrates a set of aggregated SL resource pools, in accordance with an example implementation of the processes of FIGS. 10-11, respectively.
  • SL resource (re)selection procedure e.g., as defined in 3GPP Rel. 16 or Rel. 17
  • 3GPP Rel. 16 or Rel. 17 a sidelink (SL) resource (re)selection procedure
  • aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages.
  • Aspects of the disclosure are directed to aggregation of SL resource pools for positioning (SL-RP-Ps) via an aggregated SL-RP-P configuration with one or more common parameters.
  • aggregation of SL-RP-Ps may facilitate various technical advantages, such as improved SL-PRS-based position estimation accuracy, reduced SL-PRS-based position estimation latency, and so on, by jointly considering various parameters (e.g., resource allocation, comb-patterns or comb-sizes, etc.) in the aggregated SL-RP-Ps.
  • sequences of actions are described in terms of sequences of actions to be performed by, for example, elements of a computing device. It will be recognized that various actions described herein can be performed by specific circuits (e.g., application specific integrated circuits (ASICs)), by program instructions being executed by one or more processors, or by a combination of both. Additionally, the sequence(s) of actions described herein can be considered to be embodied entirely within any form of non- transitory computer-readable storage medium having stored therein a corresponding set of computer instructions that, upon execution, would cause or instruct an associated processor of a device to perform the functionality described herein.
  • ASICs application specific integrated circuits
  • a UE may be any wireless communication device (e.g., a mobile phone, router, tablet computer, laptop computer, consumer asset locating device, wearable (e.g., smartwatch, glasses, augmented reality (AR) / virtual reality (VR) headset, etc.), vehicle (e.g., automobile, motorcycle, bicycle, etc.), Internet of Things (loT) device, etc.) used by a user to communicate over a wireless communications network.
  • a UE may be mobile or may (e.g., at certain times) be stationary, and may communicate with a radio access network (RAN).
  • RAN radio access network
  • the term “UE” may be referred to interchangeably as an “access terminal” or “AT,” a “client device,” a “wireless device,” a “subscriber device,” a “subscriber terminal,” a “subscriber station,” a “user terminal” or “UT,” a “mobile device,” a “mobile terminal,” a “mobile station,” or variations thereof.
  • AT access terminal
  • client device a “wireless device”
  • subscriber device a “subscriber terminal”
  • a “subscriber station” a “user terminal” or “UT”
  • UEs can communicate with a core network via a RAN, and through the core network the UEs can be connected with external networks such as the Internet and with other UEs.
  • WLAN wireless local area network
  • IEEE Institute of Electrical and Electronics Engineers
  • a base station may operate according to one of several RATs in communication with UEs depending on the network in which it is deployed, and may be alternatively referred to as an access point (AP), a network node, a NodeB, an evolved NodeB (eNB), a next generation eNB (ng-eNB), a New Radio (NR) Node B (also referred to as a gNB or gNodeB), etc.
  • AP access point
  • eNB evolved NodeB
  • ng-eNB next generation eNB
  • NR New Radio
  • a base station may be used primarily to support wireless access by UEs, including supporting data, voice, and/or signaling connections for the supported UEs.
  • a base station may provide purely edge node signaling functions while in other systems it may provide additional control and/or network management functions.
  • a communication link through which UEs can send signals to a base station is called an uplink (UL) channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, etc.).
  • a communication link through which the base station can send signals to UEs is called a downlink (DL) or forward link channel (e.g., a paging channel, a control channel, a broadcast channel, a forward traffic channel, etc.).
  • DL downlink
  • forward link channel e.g., a paging channel, a control channel, a broadcast channel, a forward traffic channel, etc.
  • traffic channel can refer to either an uplink / reverse or downlink / forward traffic channel.
  • the term “base station” may refer to a single physical transmission-reception point (TRP) or to multiple physical TRPs that may or may not be co-located.
  • TRP transmission-reception point
  • the physical TRP may be an antenna of the base station corresponding to a cell (or several cell sectors) of the base station.
  • base station refers to multiple co-located physical TRPs
  • the physical TRPs may be an array of antennas (e.g., as in a multiple-input multiple-output (MIMO) system or where the base station employs beamforming) of the base station.
  • MIMO multiple-input multiple-output
  • the physical TRPs may be a distributed antenna system (DAS) (a network of spatially separated antennas connected to a common source via a transport medium) or a remote radio head (RRH) (a remote base station connected to a serving base station).
  • DAS distributed antenna system
  • RRH remote radio head
  • the non-co-located physical TRPs may be the serving base station receiving the measurement report from the UE and a neighbor base station whose reference radio frequency (RF) signals the UE is measuring.
  • RF radio frequency
  • a base station may not support wireless access by UEs (e.g., may not support data, voice, and/or signaling connections for UEs), but may instead transmit reference signals to UEs to be measured by the UEs, and/or may receive and measure signals transmitted by the UEs.
  • a base station may be referred to as a positioning beacon (e.g., when transmitting signals to UEs) and/or as a location measurement unit (e.g., when receiving and measuring signals from UEs).
  • An “RF signal” comprises an electromagnetic wave of a given frequency that transports information through the space between a transmitter and a receiver.
  • a transmitter may transmit a single “RF signal” or multiple “RF signals” to a receiver.
  • the receiver may receive multiple “RF signals” corresponding to each transmitted RF signal due to the propagation characteristics of RF signals through multipath channels.
  • the same transmitted RF signal on different paths between the transmitter and receiver may be referred to as a “multipath” RF signal.
  • an RF signal may also be referred to as a “wireless signal” or simply a “signal” where it is clear from the context that the term “signal” refers to a wireless signal or an RF signal.
  • FIG. 1 illustrates an example wireless communications system 100, according to aspects of the disclosure.
  • the wireless communications system 100 (which may also be referred to as a wireless wide area network (WWAN)) may include various base stations 102 (labeled “BS”) and various UEs 104.
  • the base stations 102 may include macro cell base stations (high power cellular base stations) and/or small cell base stations (low power cellular base stations).
  • the macro cell base stations may include eNBs and/or ng-eNBs where the wireless communications system 100 corresponds to an LTE network, or gNBs where the wireless communications system 100 corresponds to a NR network, or a combination of both, and the small cell base stations may include femtocells, picocells, microcells, etc.
  • the base stations 102 may collectively form a RAN and interface with a core network 170 (e.g., an evolved packet core (EPC) or a 5G core (5GC)) through backhaul links 122, and through the core network 170 to one or more location servers 172 (e.g., a location management function (LMF) or a secure user plane location (SUPL) location platform (SLP)).
  • the location server(s) 172 may be part of core network 170 or may be external to core network 170.
  • a location server 172 may be integrated with a base station 102.
  • a UE 104 may communicate with a location server 172 directly or indirectly.
  • a UE 104 may communicate with a location server 172 via the base station 102 that is currently serving that UE 104.
  • a UE 104 may also communicate with a location server 172 through another path, such as via an application server (not shown), via another network, such as via a wireless local area network (WLAN) access point (AP) (e.g., AP 150 described below), and so on.
  • WLAN wireless local area network
  • AP access point
  • communication between a UE 104 and a location server 172 may be represented as an indirect connection (e.g., through the core network 170, etc.) or a direct connection (e.g., as shown via direct connection 128), with the intervening nodes (if any) omitted from a signaling diagram for clarity.
  • the base stations 102 may perform functions that relate to one or more of transferring user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment trace, RAN information management (RIM), paging, positioning, and delivery of warning messages.
  • the base stations 102 may communicate with each other directly or indirectly (e.g., through the EPC / 5GC) over backhaul links 134, which may be wired or wireless.
  • the base stations 102 may wirelessly communicate with the UEs 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. In an aspect, one or more cells may be supported by a base station 102 in each geographic coverage area 110.
  • a “cell” is a logical communication entity used for communication with a base station (e.g., over some frequency resource, referred to as a carrier frequency, component carrier, carrier, band, or the like), and may be associated with an identifier (e.g., a physical cell identifier (PCI), an enhanced cell identifier (ECI), a virtual cell identifier (VCI), a cell global identifier (CGI), etc.) for distinguishing cells operating via the same or a different carrier frequency.
  • PCI physical cell identifier
  • ECI enhanced cell identifier
  • VCI virtual cell identifier
  • CGI cell global identifier
  • different cells may be configured according to different protocol types (e.g., machine-type communication (MTC), narrowband loT (NB-IoT), enhanced mobile broadband (eMBB), or others) that may provide access for different types of UEs.
  • MTC machine-type communication
  • NB-IoT narrowband loT
  • eMBB enhanced mobile broadband
  • a cell may refer to either or both of the logical communication entity and the base station that supports it, depending on the context.
  • TRP is typically the physical transmission point of a cell
  • the terms “cell” and “TRP” may be used interchangeably.
  • the term “cell” may also refer to a geographic coverage area of a base station (e.g., a sector), insofar as a carrier frequency can be detected and used for communication within some portion of geographic coverage areas 110.
  • While neighboring macro cell base station 102 geographic coverage areas 110 may partially overlap (e.g., in a handover region), some of the geographic coverage areas 110 may be substantially overlapped by a larger geographic coverage area 110.
  • 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 area 110 of one or more macro cell base stations 102.
  • a network that includes both small cell and macro cell base stations may be known as a heterogeneous network.
  • a heterogeneous network may also include home eNBs (HeNBs), which may provide service to a restricted group known as a closed subscriber group (CSG).
  • HeNBs home eNBs
  • CSG closed subscriber group
  • the communication links 120 between the base stations 102 and the UEs 104 may include uplink (also referred to as reverse link) transmissions from a UE 104 to a base station 102 and/or downlink (DL) (also referred to as forward link) transmissions from a base station 102 to a UE 104.
  • the communication links 120 may use MIMO antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity.
  • the communication links 120 may be through one or more carrier frequencies. Allocation of carriers may be asymmetric with respect to downlink and uplink (e.g., more or less carriers may be allocated for downlink than for uplink).
  • the wireless communications system 100 may further include a wireless local area network (WLAN) access point (AP) 150 in communication with WLAN stations (STAs) 152 via communication links 154 in an unlicensed frequency spectrum (e.g., 5 GHz).
  • WLAN STAs 152 and/or the WLAN AP 150 may perform a clear channel assessment (CCA) or listen before talk (LBT) procedure prior to communicating in order to determine whether the channel is available.
  • CCA clear channel assessment
  • LBT listen before talk
  • the small cell base station 102' may operate in a licensed and/or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell base station 102' may employ LTE or NR technology and use the same 5 GHz unlicensed frequency spectrum as used by the WLAN AP 150. The small cell base station 102', employing LTE / 5G in an unlicensed frequency spectrum, may boost coverage to and/or increase capacity of the access network.
  • NR in unlicensed spectrum may be referred to as NR-U.
  • LTE in an unlicensed spectrum may be referred to as LTE-U, licensed assisted access (LAA), or MULTEFIRE®.
  • the wireless communications system 100 may further include a millimeter wave (mmW) base station 180 that may operate in mmW frequencies and/or near mmW frequencies in communication with a UE 182.
  • Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 millimeter and 10 millimeters. Radio waves in this band may be referred to as a millimeter wave.
  • Near mmW may extend down to a frequency of 3 GHz with a wavelength of 100 millimeters.
  • the super high frequency (SHF) band extends between 3 GHz and 30 GHz, also referred to as centimeter wave.
  • the mmW base station 180 and the UE 182 may utilize beamforming (transmit and/or receive) over a mmW communication link 184 to compensate for the extremely high path loss and short range.
  • one or more base stations 102 may also transmit using mmW or near mmW and beamforming. Accordingly, it will be appreciated that the foregoing illustrations are merely examples and should not be construed to limit the various aspects disclosed herein.
  • Transmit beamforming is a technique for focusing an RF signal in a specific direction.
  • a network node e.g., a base station
  • broadcasts an RF signal in all directions (omni-directionally).
  • the network node determines where a given target device (e.g., a UE) is located (relative to the transmitting network node) and projects a stronger downlink RF signal in that specific direction, thereby providing a faster (in terms of data rate) and stronger RF signal for the receiving device(s).
  • a network node can control the phase and relative amplitude of the RF signal at each of the one or more transmitters that are broadcasting the RF signal.
  • a network node may use an array of antennas (referred to as a “phased array” or an “antenna array”) that creates a beam of RF waves that can be “steered” to point in different directions, without actually moving the antennas.
  • the RF current from the transmitter is fed to the individual antennas with the correct phase relationship so that the radio waves from the separate antennas add together to increase the radiation in a desired direction, while cancelling to suppress radiation in undesired directions.
  • Transmit beams may be quasi-co-located, meaning that they appear to the receiver (e.g., a UE) as having the same parameters, regardless of whether or not the transmitting antennas of the network node themselves are physically co-located.
  • the receiver e.g., a UE
  • QCL relation of a given type means that certain parameters about a second reference RF signal on a second beam can be derived from information about a source reference RF signal on a source beam.
  • the receiver can use the source reference RF signal to estimate the Doppler shift, Doppler spread, average delay, and delay spread of a second reference RF signal transmitted on the same channel.
  • the source reference RF signal is QCL Type B
  • the receiver can use the source reference RF signal to estimate the Doppler shift and Doppler spread of a second reference RF signal transmitted on the same channel.
  • the source reference RF signal is QCL Type C
  • the receiver can use the source reference RF signal to estimate the Doppler shift and average delay of a second reference RF signal transmitted on the same channel.
  • the receiver can use the source reference RF signal to estimate the spatial receive parameter of a second reference RF signal transmitted on the same channel.
  • the receiver uses a receive beam to amplify RF signals detected on a given channel. For example, the receiver can increase the gain setting and/or adjust the phase setting of an array of antennas in a particular direction to amplify (e.g., to increase the gain level of) the RF signals received from that direction.
  • a receiver when a receiver is said to beamform in a certain direction, it means the beam gain in that direction is high relative to the beam gain along other directions, or the beam gain in that direction is the highest compared to the beam gain in that direction of all other receive beams available to the receiver.
  • This results in a stronger received signal strength e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), signal-to- interference-plus-noise ratio (SINR), etc.
  • RSRP reference signal received power
  • RSRQ reference signal received quality
  • SINR signal-to- interference-plus-noise ratio
  • Transmit and receive beams may be spatially related.
  • a spatial relation means that parameters for a second beam (e.g., a transmit or receive beam) for a second reference signal can be derived from information about a first beam (e.g., a receive beam or a transmit beam) for a first reference signal.
  • a UE may use a particular receive beam to receive a reference downlink reference signal (e.g., synchronization signal block (SSB)) from a base station.
  • the UE can then form a transmit beam for sending an uplink reference signal (e.g., sounding reference signal (SRS)) to that base station based on the parameters of the receive beam.
  • an uplink reference signal e.g., sounding reference signal (SRS)
  • a “downlink” beam may be either a transmit beam or a receive beam, depending on the entity forming it. For example, if a base station is forming the downlink beam to transmit a reference signal to a UE, the downlink beam is a transmit beam. If the UE is forming the downlink beam, however, it is a receive beam to receive the downlink reference signal.
  • an “uplink” beam may be either a transmit beam or a receive beam, depending on the entity forming it. For example, if a base station is forming the uplink beam, it is an uplink receive beam, and if a UE is forming the uplink beam, it is an uplink transmit beam.
  • FR1 frequency range designations FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz). It should be understood that although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in various documents and articles.
  • FR2 which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) which is identified by the INTERNATIONAL TELECOMMUNICATION UNION® as a “millimeter wave” band.
  • EHF extremely high frequency
  • FR3 7.125 GHz - 24.25 GHz
  • FR3 7.125 GHz - 24.25 GHz
  • Frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics, and thus may effectively extend features of FR1 and/or FR2 into mid-band frequencies.
  • higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz.
  • FR4a or FR4-1 52.6 GHz - 71 GHz
  • FR4 52.6 GHz - 114.25 GHz
  • FR5 114.25 GHz - 300 GHz.
  • Each of these higher frequency bands falls within the EHF band.
  • sub-6 GHz or the like if used herein may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies.
  • millimeter wave or the like if used herein may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and/or FR5, or may be within the EHF band.
  • the anchor carrier is the carrier operating on the primary frequency (e.g., FR1) utilized by a UE 104/182 and the cell in which the UE 104/182 either performs the initial radio resource control (RRC) connection establishment procedure or initiates the RRC connection re-establishment procedure.
  • RRC radio resource control
  • the primary carrier carries all common and UE-specific control channels, and may be a carrier in a licensed frequency (however, this is not always the case).
  • a secondary carrier is a carrier operating on a second frequency (e.g., FR2) that may be configured once the RRC connection is established between the UE 104 and the anchor carrier and that may be used to provide additional radio resources.
  • the secondary carrier may be a carrier in an unlicensed frequency.
  • the secondary carrier may contain only necessary signaling information and signals, for example, those that are UE-specific may not be present in the secondary carrier, since both primary uplink and downlink carriers are typically UE- specific. This means that different UEs 104/182 in a cell may have different downlink primary carriers. The same is true for the uplink primary carriers.
  • the network is able to change the primary carrier of any UE 104/182 at any time. This is done, for example, to balance the load on different carriers. Because a “serving cell” (whether a PCell or an SCell) corresponds to a carrier frequency / component carrier over which some base station is communicating, the term “cell,” “serving cell,” “component carrier,” “carrier frequency,” and the like can be used interchangeably.
  • one of the frequencies utilized by the macro cell base stations 102 may be an anchor carrier (or “PCell”) and other frequencies utilized by the macro cell base stations 102 and/or the mmW base station 180 may be secondary carriers (“SCells”).
  • PCell anchor carrier
  • SCells secondary carriers
  • the simultaneous transmission and/or reception of multiple carriers enables the UE 104/182 to significantly increase its data transmission and/or reception rates.
  • two 20 MHz aggregated carriers in a multi-carrier system would theoretically lead to a two-fold increase in data rate (i.e., 40 MHz), compared to that attained by a single 20 MHz carrier.
  • the wireless communications system 100 may further include a UE 164 that may communicate with a macro cell base station 102 over a communication link 120 and/or the mmW base station 180 over a mmW communication link 184.
  • the macro cell base station 102 may support a PCell and one or more SCells for the UE 164 and the mmW base station 180 may support one or more SCells for the UE 164.
  • the UE 164 and the UE 182 may be capable of sidelink communication.
  • Sidelink-capable UEs may communicate with base stations 102 over communication links 120 using the Uu interface (i.e., the air interface between a UE and a base station).
  • SL-UEs e.g., UE 164, UE 182
  • a wireless sidelink (or just “sidelink”) is an adaptation of the core cellular (e.g., LTE, NR) standard that allows direct communication between two or more UEs without the communication needing to go through a base station.
  • Sidelink communication may be unicast or multicast, and may be used for device-to-device (D2D) media-sharing, vehicle-to-vehicle (V2V) communication, vehicle-to-everything (V2X) communication (e.g., cellular V2X (cV2X) communication, enhanced V2X (eV2X) communication, etc.), emergency rescue applications, etc.
  • V2V vehicle-to-vehicle
  • V2X vehicle-to-everything
  • cV2X cellular V2X
  • eV2X enhanced V2X
  • One or more of a group of SL- UEs utilizing sidelink communications may be within the geographic coverage area 110 of a base station 102.
  • Other SL-UEs in such a group may be outside the geographic coverage area 110 of a base station 102 or be otherwise unable to receive transmissions from a base station 102.
  • groups of SL-UEs communicating via sidelink communications may utilize a one-to-many (1 :M) system in which each SL-UE transmits to every other SL-UE in the group.
  • a base station 102 facilitates the scheduling of resources for sidelink communications.
  • sidelink communications are carried out between SL-UEs without the involvement of a base station 102.
  • the sidelink 160 may operate over a wireless communication medium of interest, which may be shared with other wireless communications between other vehicles and/or infrastructure access points, as well as other RATs.
  • a “medium” may be composed of one or more time, frequency, and/or space communication resources (e.g., encompassing one or more channels across one or more carriers) associated with wireless communication between one or more transmitter / receiver pairs.
  • the medium of interest may correspond to at least a portion of an unlicensed frequency band shared among various RATs.
  • FIG. 1 only illustrates two of the UEs as SL-UEs (i.e., UEs 164 and 182), any of the illustrated UEs may be SL-UEs.
  • UE 182 was described as being capable of beamforming, any of the illustrated UEs, including UE 164, may be capable of beamforming.
  • SL-UEs are capable of beamforming, they may beamform towards each other (i.e., towards other SL-UEs), towards other UEs (e.g., UEs 104), towards base stations (e.g., base stations 102, 180, small cell 102’, access point 150), etc.
  • UEs 164 and 182 may utilize beamforming over sidelink 160.
  • any of the illustrated UEs may receive signals 124 from one or more Earth orbiting space vehicles (SVs) 112 (e.g., satellites).
  • SVs Earth orbiting space vehicles
  • the SVs 112 may be part of a satellite positioning system that a UE 104 can use as an independent source of location information.
  • a satellite positioning system typically includes a system of transmitters (e.g., SVs 112) positioned to enable receivers (e.g., UEs 104) to determine their location on or above the Earth based, at least in part, on positioning signals (e.g., signals 124) received from the transmitters.
  • Such a transmitter typically transmits a signal marked with a repeating pseudo-random noise (PN) code of a set number of chips. While typically located in SVs 112, transmitters may sometimes be located on ground-based control stations, base stations 102, and/or other UEs 104.
  • a UE 104 may include one or more dedicated receivers specifically designed to receive signals 124 for deriving geo location information from the SVs 112.
  • a satellite positioning system the use of signals 124 can be augmented by various satellite-based augmentation systems (SBAS) that may be associated with or otherwise enabled for use with one or more global and/or regional navigation satellite systems.
  • SBAS satellite-based augmentation systems
  • an SBAS may include an augmentation system(s) that provides integrity information, differential corrections, etc., such as the Wide Area Augmentation System (WAAS), the European Geostationary Navigation Overlay Service (EGNOS), the Multifunctional Satellite Augmentation System (MSAS), the Global Positioning System (GPS) Aided Geo Augmented Navigation or GPS and Geo Augmented Navigation system (GAGAN), and/or the like.
  • WAAS Wide Area Augmentation System
  • GNOS European Geostationary Navigation Overlay Service
  • MSAS Multifunctional Satellite Augmentation System
  • GPS Global Positioning System Aided Geo Augmented Navigation or GPS and Geo Augmented Navigation system
  • GAGAN Global Positioning System
  • a satellite positioning system may include any combination of one or more global and/or regional navigation satellites associated with such one
  • SVs 112 may additionally or alternatively be part of one or more nonterrestrial networks (NTNs).
  • NTN nonterrestrial networks
  • an SV 112 is connected to an earth station (also referred to as a ground station, NTN gateway, or gateway), which in turn is connected to an element in a 5G network, such as a modified base station 102 (without a terrestrial antenna) or a network node in a 5GC.
  • This element would in turn provide access to other elements in the 5G network and ultimately to entities external to the 5G network, such as Internet web servers and other user devices.
  • a UE 104 may receive communication signals (e.g., signals 124) from an SV 112 instead of, or in addition to, communication signals from a terrestrial base station 102.
  • the wireless communications system 100 may further include one or more UEs, such as UE 190, that connects indirectly to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links (referred to as “sidelinks”).
  • D2D device-to-device
  • P2P peer-to-peer
  • sidelinks referred to as “sidelinks”.
  • UE 190 has a D2D P2P link 192 with one of the UEs 104 connected to one of the base stations 102 (e.g., through which UE 190 may indirectly obtain cellular connectivity) and a D2D P2P link 194 with WLAN STA 152 connected to the WLAN AP 150 (through which UE 190 may indirectly obtain WLAN-based Internet connectivity).
  • the D2D P2P links 192 and 194 may be supported with any well-known D2D RAT, such as LTE Direct (LTE-D), WI-FI DIRECT®, BLUETOOTH®,
  • FIG. 2A illustrates an example wireless network structure 200.
  • a 5GC 210 also referred to as a Next Generation Core (NGC)
  • C-plane control plane
  • U-plane user plane
  • User plane interface (NG-U) 213 and control plane interface (NG-C) 215 connect the gNB 222 to the 5GC 210 and specifically to the user plane functions 212 and control plane functions 214, respectively.
  • an ng-eNB 224 may also be connected to the 5GC 210 via NG-C 215 to the control plane functions 214 and NG-U 213 to user plane functions 212. Further, ng-eNB 224 may directly communicate with gNB 222 via a backhaul connection 223.
  • a Next Generation RAN (NG-RAN) 220 may have one or more gNBs 222, while other configurations include one or more of both ng-eNBs 224 and gNBs 222. Either (or both) gNB 222 or ng-eNB 224 may communicate with one or more UEs 204 (e.g., any of the UEs described herein).
  • a location server 230 which may be in communication with the 5GC 210 to provide location assistance for UE(s) 204.
  • the location server 230 can be implemented as a plurality of separate servers (e.g., physically separate servers, different software modules on a single server, different software modules spread across multiple physical servers, etc.), or alternately may each correspond to a single server.
  • the location server 230 can be configured to support one or more location services for UEs 204 that can connect to the location server 230 via the core network, 5GC 210, and/or via the Internet (not illustrated). Further, the location server 230 may be integrated into a component of the core network, or alternatively may be external to the core network (e.g., a third party server, such as an original equipment manufacturer (OEM) server or service server).
  • OEM original equipment manufacturer
  • FIG. 2B illustrates another example wireless network structure 240.
  • a 5GC 260 (which may correspond to 5GC 210 in FIG. 2A) can be viewed functionally as control plane functions, provided by an access and mobility management function (AMF) 264, and user plane functions, provided by a user plane function (UPF) 262, which operate cooperatively to form the core network (i.e., 5GC 260).
  • AMF access and mobility management function
  • UPF user plane function
  • the functions of the AMF 264 include registration management, connection management, reachability management, mobility management, lawful interception, transport for session management (SM) messages between one or more UEs 204 (e.g., any of the UEs described herein) and a session management function (SMF) 266, transparent proxy services for routing SM messages, access authentication and access authorization, transport for short message service (SMS) messages between the UE 204 and the short message service function (SMSF) (not shown), and security anchor functionality (SEAF).
  • the AMF 264 also interacts with an authentication server function (AUSF) (not shown) and the UE 204, and receives the intermediate key that was established as a result of the UE 204 authentication process.
  • AUSF authentication server function
  • the AMF 264 retrieves the security material from the AUSF.
  • the functions of the AMF 264 also include security context management (SCM).
  • SCM receives a key from the SEAF that it uses to derive access-network specific keys.
  • the functionality of the AMF 264 also includes location services management for regulatory services, transport for location services messages between the UE 204 and a location management function (LMF) 270 (which acts as a location server 230), transport for location services messages between the NG-RAN 220 and the LMF 270, evolved packet system (EPS) bearer identifier allocation for interworking with the EPS, and UE 204 mobility event notification.
  • LMF location management function
  • EPS evolved packet system
  • the AMF 264 also supports functionalities for non-3GPP® (Third Generation Partnership Project) access networks.
  • Functions of the UPF 262 include acting as an anchor point for intra/inter-RAT mobility (when applicable), acting as an external protocol data unit (PDU) session point of interconnect to a data network (not shown), providing packet routing and forwarding, packet inspection, user plane policy rule enforcement (e.g., gating, redirection, traffic steering), lawful interception (user plane collection), traffic usage reporting, quality of service (QoS) handling for the user plane (e.g., uplink/ downlink rate enforcement, reflective QoS marking in the downlink), uplink traffic verification (service data flow (SDF) to QoS flow mapping), transport level packet marking in the uplink and downlink, downlink packet buffering and downlink data notification triggering, and sending and forwarding of one or more “end markers” to the source RAN node.
  • the UPF 262 may also support transfer of location services messages over a user plane between the UE 204 and a location server, such as an SLP 272.
  • the functions of the SMF 266 include session management, UE Internet protocol (IP) address allocation and management, selection and control of user plane functions, configuration of traffic steering at the UPF 262 to route traffic to the proper destination, control of part of policy enforcement and QoS, and downlink data notification.
  • IP Internet protocol
  • the interface over which the SMF 266 communicates with the AMF 264 is referred to as the Ni l interface.
  • Another optional aspect may include an LMF 270, which may be in communication with the 5GC 260 to provide location assistance for UEs 204.
  • the LMF 270 can be implemented as a plurality of separate servers (e.g., physically separate servers, different software modules on a single server, different software modules spread across multiple physical servers, etc.), or alternately may each correspond to a single server.
  • the LMF 270 can be configured to support one or more location services for UEs 204 that can connect to the LMF 270 via the core network, 5GC 260, and/or via the Internet (not illustrated).
  • the SLP 272 may support similar functions to the LMF 270, but whereas the LMF 270 may communicate with the AMF 264, NG-RAN 220, and UEs 204 over a control plane (e.g., using interfaces and protocols intended to convey signaling messages and not voice or data), the SLP 272 may communicate with UEs 204 and external clients (e.g., third-party server 274) over a user plane (e.g., using protocols intended to carry voice and/or data like the transmission control protocol (TCP) and/or IP).
  • TCP transmission control protocol
  • Yet another optional aspect may include a third-party server 274, which may be in communication with the LMF 270, the SLP 272, the 5GC 260 (e.g., via the AMF 264 and/or the UPF 262), the NG-RAN 220, and/or the UE 204 to obtain location information (e.g., a location estimate) for the UE 204.
  • the third-party server 274 may be referred to as a location services (LCS) client or an external client.
  • the third- party server 274 can be implemented as a plurality of separate servers (e.g., physically separate servers, different software modules on a single server, different software modules spread across multiple physical servers, etc.), or alternately may each correspond to a single server.
  • User plane interface 263 and control plane interface 265 connect the 5GC 260, and specifically the UPF 262 and AMF 264, respectively, to one or more gNBs 222 and/or ng-eNBs 224 in the NG-RAN 220.
  • the interface between gNB(s) 222 and/or ng-eNB(s) 224 and the AMF 264 is referred to as the “N2” interface
  • the interface between gNB(s) 222 and/or ng-eNB(s) 224 and the UPF 262 is referred to as the “N3” interface.
  • the gNB(s) 222 and/or ng-eNB(s) 224 of the NG-RAN 220 may communicate directly with each other via backhaul connections 223, referred to as the “Xn-C” interface.
  • One or more of gNBs 222 and/or ng-eNBs 224 may communicate with one or more UEs 204 over a wireless interface, referred to as the “Uu” interface.
  • a gNB 222 may be divided between a gNB central unit (gNB-CU) 226, one or more gNB distributed units (gNB-DUs) 228, and one or more gNB radio units (gNB-RUs) 229.
  • gNB-CU 226 is a logical node that includes the base station functions of transferring user data, mobility control, radio access network sharing, positioning, session management, and the like, except for those functions allocated exclusively to the gNB-DU(s) 228. More specifically, the gNB-CU 226 generally host the radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) protocols of the gNB 222.
  • RRC radio resource control
  • SDAP service data adaptation protocol
  • PDCP packet data convergence protocol
  • a gNB-DU 228 is a logical node that generally hosts the radio link control (RLC) and medium access control (MAC) layer of the gNB 222. Its operation is controlled by the gNB-CU 226.
  • One gNB-DU 228 can support one or more cells, and one cell is supported by only one gNB-DU 228.
  • the interface 232 between the gNB-CU 226 and the one or more gNB-DUs 228 is referred to as the “Fl” interface.
  • the physical (PHY) layer functionality of a gNB 222 is generally hosted by one or more standalone gNB-RUs 229 that perform functions such as power amplification and signal transmission/reception.
  • a UE 204 communicates with the gNB-CU 226 via the RRC, SDAP, and PDCP layers, with a gNB-DU 228 via the RLC and MAC layers, and with a gNB-RU 229 via the PHY layer.
  • a network node a network entity, a mobility element of a network, a RAN node, a core network node, a network element, or a network equipment, such as a base station, or one or more units (or one or more components) performing base station functionality, may be implemented in an aggregated or disaggregated architecture.
  • a base station such as a Node B (NB), evolved NB (eNB), NR base station, 5G NB, AP, TRP, cell, etc.
  • NB Node B
  • eNB evolved NB
  • 5G NB 5G NB
  • AP TRP
  • cell cell, etc.
  • a base station may be implemented as an aggregated base station (also known as a standalone base station or a monolithic base station) or a disaggregated base station.
  • An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node.
  • a disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).
  • CUs central or centralized units
  • DUs distributed units
  • RUs radio units
  • a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed throughout one or multiple other RAN nodes.
  • the DUs may be implemented to communicate with one or more RUs.
  • Each of the CU, DU and RU also can be implemented as virtual units, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).
  • Base station-type operation or network design may consider aggregation characteristics of base station functionality.
  • disaggregated base stations may be utilized in an integrated access backhaul (IAB) network, an open radio access network (0-RAN (such as the network configuration sponsored by the 0-RAN ALLIANCE®)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C- RAN)).
  • IAB integrated access backhaul
  • 0-RAN such as the network configuration sponsored by the 0-RAN ALLIANCE®
  • vRAN also known as a cloud radio access network (C- RAN)
  • Disaggregation may include distributing functionality across two or more units at various physical locations, as well as distributing functionality for at least one unit virtually, which can enable flexibility in network design.
  • the various units of the disaggregated base station, or disaggregated RAN architecture can be configured for wired or wireless communication with at least one other unit.
  • FIG. 2C illustrates an example disaggregated base station architecture 250, according to aspects of the disclosure.
  • the disaggregated base station architecture 250 may include one or more central units (CUs) 280 (e.g., gNB-CU 226) that can communicate directly with a core network 267 (e.g., 5GC 210, 5GC 260) via a backhaul link, or indirectly with the core network 267 through one or more disaggregated base station units (such as a Near-Real Time (Near-RT) RAN Intelligent Controller (RIC) 259 via an E2 link, or a Non-Real Time (Non-RT) RIC 257 associated with a Service Management and Orchestration (SMO) Framework 255, or both).
  • CUs central units
  • a CU 280 may communicate with one or more DUs 285 (e.g., gNB-DUs 228) via respective midhaul links, such as an Fl interface.
  • the DUs 285 may communicate with one or more radio units (RUs) 287 (e.g., gNB-RUs 229) via respective fronthaul links.
  • the RUs 287 may communicate with respective UEs 204 via one or more radio frequency (RF) access links.
  • RF radio frequency
  • the UE 204 may be simultaneously served by multiple RUs 287.
  • Each of the units may include one or more interfaces or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium.
  • Each of the units, or an associated processor or controller providing instructions to the communication interfaces of the units can be configured to communicate with one or more of the other units via the transmission medium.
  • the units can include a wired interface configured to receive or transmit signals over a wired transmission medium to one or more of the other units.
  • the units can include a wireless interface, which may include a receiver, a transmitter or transceiver (such as a RF transceiver), configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other units.
  • the CU 280 may host one or more higher layer control functions. Such control functions can include RRC, PDCP, service data adaptation protocol (SDAP), or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 280.
  • the CU 280 may be configured to handle user plane functionality (i.e., Central Unit - User Plane (CU- UP)), control plane functionality (i.e., Central Unit - Control Plane (CU-CP)), or a combination thereof.
  • the CU 280 can be logically split into one or more CU-UP units and one or more CU-CP units.
  • the CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as the El interface when implemented in an O-RAN configuration.
  • the CU 280 can be implemented to communicate with the DU 285, as necessary, for network control and signaling.
  • the DU 285 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 287.
  • the DU 285 may host one or more of a RLC layer, a MAC layer, and one or more high PHY layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, or the like) depending, at least in part, on a functional split, such as those defined by the 3rd Generation Partnership Project (3 GPP®).
  • the DU 285 may further host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 285, or with the control functions hosted by the CU 280.
  • Lower-layer functionality can be implemented by one or more RUs 287.
  • an RU 287 controlled by a DU 285, may correspond to a logical node that hosts RF processing functions, or low-PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, or the like), or both, based at least in part on the functional split, such as a lower layer functional split.
  • the RU(s) 287 can be implemented to handle over the air (OTA) communication with one or more UEs 204.
  • OTA over the air
  • the SMO Framework 255 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 255 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements which may be managed via an operations and maintenance interface (such as an 01 interface).
  • the SMO Framework 255 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 269) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an 02 interface).
  • a cloud computing platform such as an open cloud (O-Cloud) 269
  • network element life cycle management such as to instantiate virtualized network elements
  • cloud computing platform interface such as an 02 interface
  • virtualized network elements can include, but are not limited to, CUs 280, DUs 285, RUs 287 and Near-RT RICs 259.
  • the SMO Framework 255 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 261, via an 01 interface. Additionally, in some implementations, the SMO Framework 255 can communicate directly with one or more RUs 287 via an 01 interface.
  • the SMO Framework 255 also may include a Non-RT RIC 257 configured to support functionality of the SMO Framework 255
  • the Non-RT RIC 257 may be configured to include a logical function that enables non- real-time control and optimization of RAN elements and resources, artificial intelligence/machine learning (AI/ML) workflows including model training and updates, or policy-based guidance of applications/features in the Near-RT RIC 259.
  • the Non-RT RIC 257 may be coupled to or communicate with (such as via an Al interface) the Near- RT RIC 259.
  • the Near-RT RIC 259 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 280, one or more DUs 285, or both, as well as an O-eNB, with the Near-RT RIC 259.
  • the Non-RT RIC 257 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 259 and may be received at the SMO Framework 255 or the Non-RT RIC 257 from non-network data sources or from network functions.
  • the Non-RT RIC 257 or the Near-RT RIC 259 may be configured to tune RAN behavior or performance.
  • the Non-RT RIC 257 may monitor long-term trends and patterns for performance and employ AI/ML models to perform corrective actions through the SMO Framework 255 (such as reconfiguration via 01) or via creation of RAN management policies (such as Al policies).
  • FIGS. 3A, 3B, and 3C illustrate several example components (represented by corresponding blocks) that may be incorporated into a UE 302 (which may correspond to any of the UEs described herein), a base station 304 (which may correspond to any of the base stations described herein), and a network entity 306 (which may correspond to or embody any of the network functions described herein, including the location server 230 and the LMF 270, or alternatively may be independent from the NG-RAN 220 and/or 5GC 210/260 infrastructure depicted in FIGS. 2A and 2B, such as a private network) to support the operations described herein.
  • a UE 302 which may correspond to any of the UEs described herein
  • a base station 304 which may correspond to any of the base stations described herein
  • a network entity 306 which may correspond to or embody any of the network functions described herein, including the location server 230 and the LMF 270, or alternatively may be independent from the NG-RAN 220 and/or
  • these components may be implemented in different types of apparatuses in different implementations (e.g., in an ASIC, in a system-on-chip (SoC), etc.).
  • the illustrated components may also be incorporated into other apparatuses in a communication system.
  • other apparatuses in a system may include components similar to those described to provide similar functionality.
  • a given apparatus may contain one or more of the components.
  • an apparatus may include multiple transceiver components that enable the apparatus to operate on multiple carriers and/or communicate via different technologies.
  • the UE 302 and the base station 304 each include one or more wireless wide area network (WWAN) transceivers 310 and 350, respectively, providing means for communicating (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, means for refraining from transmitting, etc.) via one or more wireless communication networks (not shown), such as an NR network, an LTE network, a GSM network, and/or the like.
  • WWAN wireless wide area network
  • the WWAN transceivers 310 and 350 may each be connected to one or more antennas 316 and 356, respectively, for communicating with other network nodes, such as other UEs, access points, base stations (e.g., eNBs, gNBs), etc., via at least one designated RAT (e.g., NR, LTE, GSM, etc.) over a wireless communication medium of interest (e.g., some set of time/frequency resources in a particular frequency spectrum).
  • a wireless communication medium of interest e.g., some set of time/frequency resources in a particular frequency spectrum.
  • the WWAN transceivers 310 and 350 may be variously configured for transmitting and encoding signals 318 and 358 (e.g., messages, indications, information, and so on), respectively, and, conversely, for receiving and decoding signals 318 and 358 (e.g., messages, indications, information, pilots, and so on), respectively, in accordance with the designated RAT.
  • the WWAN transceivers 310 and 350 include one or more transmitters 314 and 354, respectively, for transmitting and encoding signals 318 and 358, respectively, and one or more receivers 312 and 352, respectively, for receiving and decoding signals 318 and 358, respectively.
  • the UE 302 and the base station 304 each also include, at least in some cases, one or more short-range wireless transceivers 320 and 360, respectively.
  • the short-range wireless transceivers 320 and 360 may be connected to one or more antennas 326 and 366, respectively, and provide means for communicating (e.g., means for transmitting, means for receiving, means for measuring, means for tuning, means for refraining from transmitting, etc.) with other network nodes, such as other UEs, access points, base stations, etc., via at least one designated RAT (e.g., Wi-Fi, LTE Direct, BLUETOOTH®, ZIGBEE®, Z-WAVE®, PC5, dedicated short-range communications (DSRC), wireless access for vehicular environments (WAVE), near-field communication (NFC), ultra- wideband (UWB), etc.) over a wireless communication medium of interest.
  • RAT e.g., Wi-Fi, LTE Direct, BLUETOOTH®, ZIGBEE®, Z
  • the short- range wireless transceivers 320 and 360 may be variously configured for transmitting and encoding signals 328 and 368 (e.g., messages, indications, information, and so on), respectively, and, conversely, for receiving and decoding signals 328 and 368 (e.g., messages, indications, information, pilots, and so on), respectively, in accordance with the designated RAT.
  • the short-range wireless transceivers 320 and 360 include one or more transmitters 324 and 364, respectively, for transmitting and encoding signals 328 and 368, respectively, and one or more receivers 322 and 362, respectively, for receiving and decoding signals 328 and 368, respectively.
  • the short-range wireless transceivers 320 and 360 may be Wi-Fi transceivers, BLUETOOTH® transceivers, ZIGBEE® and/or Z-WAVE® transceivers, NFC transceivers, UWB transceivers, or vehi cl e-to- vehicle (V2V) and/or vehicle-to- everything (V2X) transceivers.
  • the UE 302 and the base station 304 also include, at least in some cases, satellite signal interfaces 330 and 370, which each include one or more satellite signal receivers 332 and 372, respectively, and may optionally include one or more satellite signal transmitters 334 and 374, respectively.
  • the base station 304 may be a terrestrial base station that may communicate with space vehicles (e.g., space vehicles 112) via the satellite signal interface 370.
  • the base station 304 may be a space vehicle (or other non-terrestrial entity) that uses the satellite signal interface 370 to communicate with terrestrial networks and/or other space vehicles.
  • the satellite signal receivers 332 and 372 may be connected to one or more antennas 336 and 376, respectively, and may provide means for receiving and/or measuring satellite positioning/communication signals 338 and 378, respectively.
  • the satellite positioning/communication signals 338 and 378 may be global positioning system (GPS) signals, global navigation satellite system (GLONASS) signals, Galileo signals, Beidou signals, Indian Regional Navigation Satellite System (NAVIC), Quasi-Zenith Satellite System (QZSS) signals, etc.
  • GPS global positioning system
  • GLONASS global navigation satellite system
  • Galileo signals Galileo signals
  • Beidou signals Beidou signals
  • NAVIC Indian Regional Navigation Satellite System
  • QZSS Quasi-Zenith Satellite System
  • the satellite positioning/communication signals 338 and 378 may be communication signals (e.g., carrying control and/or user data) originating from a 5G network.
  • the satellite signal receiver(s) 332 and 372 may comprise any suitable hardware and/or software for receiving and processing satellite positioning/communication signals 338 and 378, respectively.
  • the satellite signal receiver(s) 332 and 372 may request information and operations as appropriate from the other systems, and, at least in some cases, perform calculations to determine locations of the UE 302 and the base station 304, respectively, using measurements obtained by any suitable satellite positioning system algorithm.
  • the optional satellite signal transmitter(s) 334 and 374 when present, may be connected to the one or more antennas 336 and 376, respectively, and may provide means for transmitting satellite positioning/communication signals 338 and 378, respectively.
  • the satellite positioning/communication signals 378 may be GPS signals, GLONASS® signals, Galileo signals, Beidou signals, NAVIC, QZSS signals, etc.
  • the satellite positioning/communication signals 338 and 378 may be communication signals (e.g., carrying control and/or user data) originating from a 5G network.
  • the satellite signal transmitter(s) 334 and 374 may comprise any suitable hardware and/or software for transmitting satellite positioning/communication signals 338 and 378, respectively.
  • the satellite signal transmitter(s) 334 and 374 may request information and operations as appropriate from the other systems.
  • the base station 304 and the network entity 306 each include one or more network transceivers 380 and 390, respectively, providing means for communicating (e.g., means for transmitting, means for receiving, etc.) with other network entities (e.g., other base stations 304, other network entities 306).
  • the base station 304 may employ the one or more network transceivers 380 to communicate with other base stations 304 or network entities 306 over one or more wired or wireless backhaul links.
  • the network entity 306 may employ the one or more network transceivers 390 to communicate with one or more base station 304 over one or more wired or wireless backhaul links, or with other network entities 306 over one or more wired or wireless core network interfaces.
  • a transceiver may be configured to communicate over a wired or wireless link.
  • a transceiver (whether a wired transceiver or a wireless transceiver) includes transmitter circuitry (e.g., transmitters 314, 324, 354, 364) and receiver circuitry (e.g., receivers 312, 322, 352, 362).
  • a transceiver may be an integrated device (e.g., embodying transmitter circuitry and receiver circuitry in a single device) in some implementations, may comprise separate transmitter circuitry and separate receiver circuitry in some implementations, or may be embodied in other ways in other implementations.
  • the transmitter circuitry and receiver circuitry of a wired transceiver may be coupled to one or more wired network interface ports.
  • Wireless transmitter circuitry e.g., transmitters 314, 324, 354, 364
  • wireless receiver circuitry may include or be coupled to a plurality of antennas (e.g., antennas 316, 326, 356, 366), such as an antenna array, that permits the respective apparatus (e.g., UE 302, base station 304) to perform receive beamforming, as described herein.
  • the transmitter circuitry and receiver circuitry may share the same plurality of antennas (e.g., antennas 316, 326, 356, 366), such that the respective apparatus can only receive or transmit at a given time, not both at the same time.
  • a wireless transceiver e.g., WWAN transceivers 310 and 350, short-range wireless transceivers 320 and 360
  • NLM network listen module
  • the various wireless transceivers e.g., transceivers 310, 320, 350, and 360, and network transceivers 380 and 390 in some implementations
  • wired transceivers e.g., network transceivers 380 and 390 in some implementations
  • a transceiver at least one transceiver
  • wired transceivers e.g., network transceivers 380 and 390 in some implementations
  • backhaul communication between network devices or servers will generally relate to signaling via a wired transceiver
  • wireless communication between a UE (e.g., UE 302) and a base station (e.g., base station 304) will generally relate to signaling via a wireless transceiver.
  • the UE 302, the base station 304, and the network entity 306 also include other components that may be used in conjunction with the operations as disclosed herein.
  • the UE 302, the base station 304, and the network entity 306 include one or more processors 342, 384, and 394, respectively, for providing functionality relating to, for example, wireless communication, and for providing other processing functionality.
  • the processors 342, 384, and 394 may therefore provide means for processing, such as means for determining, means for calculating, means for receiving, means for transmitting, means for indicating, etc.
  • processors 342, 384, and 394 may include, for example, one or more general purpose processors, multi-core processors, central processing units (CPUs), ASICs, digital signal processors (DSPs), field programmable gate arrays (FPGAs), other programmable logic devices or processing circuitry, or various combinations thereof.
  • the UE 302, the base station 304, and the network entity 306 include memory circuitry implementing memories 340, 386, and 396 (e.g., each including a memory device), respectively, for maintaining information (e.g., information indicative of reserved resources, thresholds, parameters, and so on).
  • the memories 340, 386, and 396 may therefore provide means for storing, means for retrieving, means for maintaining, etc.
  • the UE 302, the base station 304, and the network entity 306 may include SL-PRS Aggregation component348, 388, and 398, respectively.
  • the SL-PRS Aggregation component348, 388, and 398 may be hardware circuits that are part of or coupled to the processors 342, 384, and 394, respectively, that, when executed, cause the UE 302, the base station 304, and the network entity 306 to perform the functionality described herein.
  • the SL-PRS Aggregation component348, 388, and 398 may be external to the processors 342, 384, and 394 (e.g., part of a modem processing system, integrated with another processing system, etc.).
  • the SL-PRS Aggregation component348, 388, and 398 may be memory modules stored in the memories 340, 386, and 396, respectively, that, when executed by the processors 342, 384, and 394 (or a modem processing system, another processing system, etc.), cause the UE 302, the base station 304, and the network entity 306 to perform the functionality described herein.
  • FIG. 3A illustrates possible locations of the SL-PRS Aggregation component348, which may be, for example, part of the one or more WWAN transceivers 310, the memory 340, the one or more processors 342, or any combination thereof, or may be a standalone component.
  • FIG. 3A illustrates possible locations of the SL-PRS Aggregation component348, which may be, for example, part of the one or more WWAN transceivers 310, the memory 340, the one or more processors 342, or any combination thereof, or may be a standalone component.
  • FIG. 3B illustrates possible locations of the SL-PRS Aggregation components 88, which may be, for example, part of the one or more WWAN transceivers 350, the memory 386, the one or more processors 384, or any combination thereof, or may be a standalone component.
  • FIG. 3C illustrates possible locations of the SL-PRS Aggregation components 98, which may be, for example, part of the one or more network transceivers 390, the memory 396, the one or more processors 394, or any combination thereof, or may be a standalone component.
  • the UE 302 may include one or more sensors 344 coupled to the one or more processors 342 to provide means for sensing or detecting movement and/or orientation information that is independent of motion data derived from signals received by the one or more WWAN transceivers 310, the one or more short-range wireless transceivers 320, and/or the satellite signal interface 330.
  • the sensor(s) 344 may include an accelerometer (e.g., a micro-electrical mechanical systems (MEMS) device), a gyroscope, a geomagnetic sensor (e.g., a compass), an altimeter (e.g., a barometric pressure altimeter), and/or any other type of movement detection sensor.
  • MEMS micro-electrical mechanical systems
  • the senor(s) 344 may include a plurality of different types of devices and combine their outputs in order to provide motion information.
  • the sensor(s) 344 may use a combination of a multi-axis accelerometer and orientation sensors to provide the ability to compute positions in two-dimensional (2D) and/or three-dimensional (3D) coordinate systems.
  • the UE 302 includes a user interface 346 providing means for providing indications (e.g., audible and/or visual indications) to a user and/or for receiving user input (e.g., upon user actuation of a sensing device such a keypad, a touch screen, a microphone, and so on).
  • the base station 304 and the network entity 306 may also include user interfaces.
  • IP packets from the network entity 306 may be provided to the processor 384.
  • the one or more processors 384 may implement functionality for an RRC layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer.
  • PDCP packet data convergence protocol
  • RLC radio link control
  • MAC medium access control
  • the one or more processors 384 may provide RRC layer functionality associated with broadcasting of system information (e.g., master information block (MIB), system information blocks (SIBs)), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-RAT mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression/decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the transfer of upper layer PDUs, error correction through automatic repeat request (ARQ), concatenation, segmentation, and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization.
  • RRC layer functionality associated with broadcasting of system
  • the transmitter 354 and the receiver 352 may implement Layer- 1 (LI) functionality associated with various signal processing functions.
  • Layer-1 which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation/demodulation of physical channels, and MIMO antenna processing.
  • FEC forward error correction
  • the transmitter 354 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)).
  • BPSK binary phase-shift keying
  • QPSK quadrature phase-shift keying
  • M-PSK M-phase-shift keying
  • M-QAM M-quadrature amplitude modulation
  • Each stream may then be mapped to an orthogonal frequency division multiplexing (OFDM) subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and/or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream.
  • OFDM symbol stream is spatially precoded to produce multiple spatial streams.
  • Channel estimates from a channel estimator may be used to determine the coding and modulation scheme, as well as for spatial processing.
  • the channel estimate may be derived from a reference signal and/or channel condition feedback transmitted by the UE 302.
  • Each spatial stream may then be provided to one or more different antennas 356.
  • the transmitter 354 may modulate an RF carrier with a respective spatial stream for transmission.
  • the receiver 312 receives a signal through its respective antenna(s) 316.
  • the receiver 312 recovers information modulated onto an RF carrier and provides the information to the one or more processors 342.
  • the transmitter 314 and the receiver 312 implement Layer- 1 functionality associated with various signal processing functions.
  • the receiver 312 may perform spatial processing on the information to recover any spatial streams destined for the UE 302. If multiple spatial streams are destined for the UE 302, they may be combined by the receiver 312 into a single OFDM symbol stream.
  • the receiver 312 then converts the OFDM symbol stream from the time-domain to the frequency domain using a fast Fourier transform (FFT).
  • FFT fast Fourier transform
  • the frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal.
  • the symbols on each subcarrier, and the reference signal are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 304. These soft decisions may be based on channel estimates computed by a channel estimator. The soft decisions are then decoded and de-interleaved to recover the data and control signals that were originally transmitted by the base station 304 on the physical channel. The data and control signals are then provided to the one or more processors 342, which implements Layer-3 (L3) and Layer-2 (L2) functionality.
  • L3 Layer-3
  • L2 Layer-2
  • the one or more processors 342 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets from the core network.
  • the one or more processors 342 are also responsible for error detection.
  • the one or more processors 342 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression/decompression, and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ), priority handling, and logical channel prioritization.
  • RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting
  • Channel estimates derived by the channel estimator from a reference signal or feedback transmitted by the base station 304 may be used by the transmitter 314 to select the appropriate coding and modulation schemes, and to facilitate spatial processing.
  • the spatial streams generated by the transmitter 314 may be provided to different antenna(s) 316.
  • the transmitter 314 may modulate an RF carrier with a respective spatial stream for transmission.
  • the uplink transmission is processed at the base station 304 in a manner similar to that described in connection with the receiver function at the UE 302.
  • the receiver 352 receives a signal through its respective antenna(s) 356.
  • the receiver 352 recovers information modulated onto an RF carrier and provides the information to the one or more processors 384.
  • the one or more processors 384 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets from the UE 302. IP packets from the one or more processors 384 may be provided to the core network.
  • the one or more processors 384 are also responsible for error detection.
  • the UE 302, the base station 304, and/or the network entity 306 are shown in FIGS. 3A, 3B, and 3C as including various components that may be configured according to the various examples described herein. It will be appreciated, however, that the illustrated components may have different functionality in different designs. In particular, various components in FIGS. 3 A to 3C are optional in alternative configurations and the various aspects include configurations that may vary due to design choice, costs, use of the device, or other considerations. For example, in case of FIG.
  • a particular implementation of UE 302 may omit the WWAN transceiver(s) 310 (e.g., a wearable device or tablet computer or personal computer (PC) or laptop may have Wi-Fi and/or BLUETOOTH® capability without cellular capability), or may omit the short- range wireless transceiver(s) 320 (e.g., cellular-only, etc.), or may omit the satellite signal interface 330, or may omit the sensor(s) 344, and so on.
  • WWAN transceiver(s) 310 e.g., a wearable device or tablet computer or personal computer (PC) or laptop may have Wi-Fi and/or BLUETOOTH® capability without cellular capability
  • the short- range wireless transceiver(s) 320 e.g., cellular-only, etc.
  • satellite signal interface 330 e.g., cellular-only, etc.
  • a particular implementation of the base station 304 may omit the WWAN transceiver(s) 350 (e.g., a Wi-Fi “hotspot” access point without cellular capability), or may omit the short-range wireless transceiver(s) 360 (e.g., cellular-only, etc.), or may omit the satellite signal interface 370, and so on.
  • WWAN transceiver(s) 350 e.g., a Wi-Fi “hotspot” access point without cellular capability
  • the short-range wireless transceiver(s) 360 e.g., cellular-only, etc.
  • satellite signal interface 370 e.g., satellite signal interface
  • the various components of the UE 302, the base station 304, and the network entity 306 may be communicatively coupled to each other over data buses 308, 382, and 392, respectively.
  • the data buses 308, 382, and 392 may form, or be part of, a communication interface of the UE 302, the base station 304, and the network entity 306, respectively.
  • the data buses 308, 382, and 392 may provide communication between them.
  • FIGS. 3 A, 3B, and 3C may be implemented in various ways.
  • the components of FIGS. 3 A, 3B, and 3C may be implemented in one or more circuits such as, for example, one or more processors and/or one or more ASICs (which may include one or more processors).
  • each circuit may use and/or incorporate at least one memory component for storing information or executable code used by the circuit to provide this functionality.
  • some or all of the functionality represented by blocks 310 to 346 may be implemented by processor and memory component(s) of the UE 302 (e.g., by execution of appropriate code and/or by appropriate configuration of processor components).
  • some or all of the functionality represented by blocks 350 to 388 may be implemented by processor and memory component(s) of the base station 304 (e.g., by execution of appropriate code and/or by appropriate configuration of processor components). Also, some or all of the functionality represented by blocks 390 to 398 may be implemented by processor and memory component(s) of the network entity 306 (e.g., by execution of appropriate code and/or by appropriate configuration of processor components). For simplicity, various operations, acts, and/or functions are described herein as being performed “by a UE,” “by a base station,” “by a network entity,” etc.
  • the network entity 306 may be implemented as a core network component. In other designs, the network entity 306 may be distinct from a network operator or operation of the cellular network infrastructure (e.g., NG RAN 220 and/or 5GC 210/260).
  • the network entity 306 may be a component of a private network that may be configured to communicate with the UE 302 via the base station 304 or independently from the base station 304 (e.g., over a non-cellular communication link, such as Wi-Fi).
  • FIG. 4 is a diagram 400 illustrating an example frame structure, according to aspects of the disclosure.
  • the frame structure may be a downlink or uplink frame structure.
  • Other wireless communications technologies may have different frame structures and/or different channels.
  • LTE and in some cases NR, utilizes orthogonal frequency-division multiplexing (OFDM) on the downlink and single-carrier frequency division multiplexing (SC-FDM) on the uplink.
  • OFDM orthogonal frequency-division multiplexing
  • SC-FDM single-carrier frequency division multiplexing
  • OFDM and SC-FDM partition the system bandwidth into multiple (K) orthogonal subcarriers, which are also commonly referred to as tones, bins, etc. Each subcarrier may be modulated with data.
  • modulation symbols are sent in the frequency domain with OFDM and in the time domain with SC-FDM.
  • the spacing between adjacent subcarriers may be fixed, and the total number of subcarriers (K) may be dependent on the system bandwidth.
  • the spacing of the subcarriers may be 15 kilohertz (kHz) and the minimum resource allocation (resource block) may be 12 subcarriers (or 180 kHz). Consequently, the nominal fast Fourier transform (FFT) size may be equal to 128, 256, 512, 1024, or 2048 for system bandwidth of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), respectively.
  • the system bandwidth may also be partitioned into subbands. For example, a subband may cover 1.08 MHz (i.e., 6 resource blocks), and there may be 1, 2, 4, 8, or 16 subbands for system bandwidth of 1.25, 2.5, 5, 10, or 20 MHz, respectively.
  • LTE supports a single numerology (subcarrier spacing (SCS), symbol length, etc.).
  • p subcarrier spacing
  • For 15 kHz SCS (p 0), there is one slot per subframe, 10 slots per frame, the slot duration is 1 millisecond (ms), the symbol duration is 66.7 microseconds (ps), and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 50.
  • For 120 kHz SCS (p 3), there are eight slots per subframe, 80 slots per frame, the slot duration is 0.125 ms, the symbol duration is 8.33 ps, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 400.
  • For 240 kHz SCS (p 4), there are 16 slots per subframe, 160 slots per frame, the slot duration is 0.0625 ms, the symbol duration is 4.17 ps, and the maximum nominal system bandwidth (in MHz) with a 4K FFT size is 800.
  • a numerology of 15 kHz is used.
  • a 10 ms frame is divided into 10 equally sized subframes of 1 ms each, and each subframe includes one time slot.
  • time is represented horizontally (on the X axis) with time increasing from left to right, while frequency is represented vertically (on the Y axis) with frequency increasing (or decreasing) from bottom to top.
  • a resource grid may be used to represent time slots, each time slot including one or more time-concurrent resource blocks (RBs) (also referred to as physical RBs (PRBs)) in the frequency domain.
  • the resource grid is further divided into multiple resource elements (REs).
  • An RE may correspond to one symbol length in the time domain and one subcarrier in the frequency domain.
  • an RB may contain 12 consecutive subcarriers in the frequency domain and seven consecutive symbols in the time domain, for a total of 84 REs.
  • an RB may contain 12 consecutive subcarriers in the frequency domain and six consecutive symbols in the time domain, for a total of 72 REs.
  • the number of bits carried by each RE depends on the modulation scheme.
  • the REs may carry reference (pilot) signals (RS).
  • the reference signals may include positioning reference signals (PRS), tracking reference signals (TRS), phase tracking reference signals (PTRS), cell-specific reference signals (CRS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), primary synchronization signals (PSS), secondary synchronization signals (SSS), synchronization signal blocks (SSBs), sounding reference signals (SRS), etc., depending on whether the illustrated frame structure is used for uplink or downlink communication.
  • FIG. 4 illustrates example locations of REs carrying a reference signal (labeled “R”).
  • a collection of resource elements (REs) that are used for transmission of PRS is referred to as a “PRS resource.”
  • the collection of resource elements can span multiple PRBs in the frequency domain and ‘N’ (such as 1 or more) consecutive symbol(s) within a slot in the time domain.
  • N such as 1 or more
  • a PRS resource occupies consecutive PRBs in the frequency domain.
  • a comb size ‘N’ represents the subcarrier spacing (or frequency/tone spacing) within each symbol of a PRS resource configuration.
  • PRS are transmitted in every Nth subcarrier of a symbol of a PRB.
  • REs corresponding to every fourth subcarrier such as subcarriers 0, 4, 8 are used to transmit PRS of the PRS resource.
  • FIG. 4 illustrates an example PRS resource configuration for comb-4 (which spans four symbols). That is, the locations of the shaded REs (labeled “R”) indicate a comb-4 PRS resource configuration.
  • a DL-PRS resource may span 2, 4, 6, or 12 consecutive symbols within a slot with a fully frequency-domain staggered pattern.
  • a DL-PRS resource can be configured in any higher layer configured downlink or flexible (FL) symbol of a slot.
  • FL downlink or flexible
  • 2-symbol comb-2 ⁇ 0, 1 ⁇ ; 4-symbol comb-2: ⁇ 0, 1, 0, 1 ⁇ ; 6-symbol comb-2: ⁇ 0, 1, 0, 1, 0, 1 ⁇ ; 12-symbol comb-2: ⁇ 0, 1, 0, 1, 0, 1, 0, 1, 0, 1, 0, 1 ⁇ ; 4-symbol comb-4: ⁇ 0, 2, 1, 3 ⁇ (as in the example of FIG.
  • 12-symbol comb-4 ⁇ 0, 2, 1, 3, 0, 2, 1, 3, 0, 2, 1, 3 ⁇
  • 6-symbol comb-6 ⁇ 0, 3, 1, 4, 2, 5 ⁇
  • 12-symbol comb-6 ⁇ 0, 3, 1, 4, 2, 5, 0, 3, 1, 4, 2, 5 ⁇
  • 12-symbol comb-12 ⁇ 0, 6, 3, 9, 1, 7, 4, 10, 2, 8, 5, H ⁇ .
  • a “PRS resource set” is a set of PRS resources used for the transmission of PRS signals, where each PRS resource has a PRS resource ID.
  • the PRS resources in a PRS resource set are associated with the same TRP.
  • a PRS resource set is identified by a PRS resource set ID and is associated with a particular TRP (identified by a TRP ID).
  • the PRS resources in a PRS resource set have the same periodicity, a common muting pattern configuration, and the same repetition factor (such as “PRS- ResourceRepetitionFactor”) across slots.
  • the periodicity is the time from the first repetition of the first PRS resource of a first PRS instance to the same first repetition of the same first PRS resource of the next PRS instance.
  • the repetition factor may have a length selected from ⁇ 1, 2, 4, 6, 8, 16, 32 ⁇ slots.
  • a PRS resource ID in a PRS resource set is associated with a single beam (or beam ID) transmitted from a single TRP (where a TRP may transmit one or more beams). That is, each PRS resource of a PRS resource set may be transmitted on a different beam, and as such, a “PRS resource,” or simply “resource,” also can be referred to as a “beam.” Note that this does not have any implications on whether the TRPs and the beams on which PRS are transmitted are known to the UE.
  • a “PRS instance” or “PRS occasion” is one instance of a periodically repeated time window (such as a group of one or more consecutive slots) where PRS are expected to be transmitted.
  • a PRS occasion also may be referred to as a “PRS positioning occasion,” a “PRS positioning instance, a “positioning occasion,” “a positioning instance,” a “positioning repetition,” or simply an “occasion,” an “instance,” or a “repetition.”
  • a “positioning frequency layer” (also referred to simply as a “frequency layer”) is a collection of one or more PRS resource sets across one or more TRPs that have the same values for certain parameters. Specifically, the collection of PRS resource sets has the same subcarrier spacing and cyclic prefix (CP) type (meaning all numerologies supported for the physical downlink shared channel (PDSCH) are also supported for PRS), the same Point A, the same value of the downlink PRS bandwidth, the same start PRB (and center frequency), and the same comb-size.
  • CP subcarrier spacing and cyclic prefix
  • the Point A parameter takes the value of the parameter “ARFCN-ValueNR” (where “ARFCN” stands for “absolute radio-frequency channel number”) and is an identifier/code that specifies a pair of physical radio channel used for transmission and reception.
  • the downlink PRS bandwidth may have a granularity of four PRBs, with a minimum of 24 PRBs and a maximum of 272 PRBs.
  • up to four frequency layers have been defined, and up to two PRS resource sets may be configured per TRP per frequency layer.
  • a frequency layer is somewhat like the concept of component carriers and bandwidth parts (BWPs), but different in that component carriers and BWPs are used by one base station (or a macro cell base station and a small cell base station) to transmit data channels, while frequency layers are used by several (usually three or more) base stations to transmit PRS.
  • a UE may indicate the number of frequency layers it can support when it sends the network its positioning capabilities, such as during an LTE positioning protocol (LPP) session. For example, a UE may indicate whether it can support one or four positioning frequency layers.
  • LPP LTE positioning protocol
  • positioning reference signal generally refer to specific reference signals that are used for positioning in NR and LTE systems.
  • the terms “positioning reference signal” and “PRS” may also refer to any type of reference signal that can be used for positioning, such as but not limited to, PRS as defined in LTE and NR, TRS, PTRS, CRS, CSLRS, DMRS, PSS, SSS, SSB, SRS, UL-PRS, etc.
  • the terms “positioning reference signal” and “PRS” may refer to downlink, uplink, or sidelink positioning reference signals, unless otherwise indicated by the context.
  • a downlink positioning reference signal may be referred to as a “DL-PRS”
  • an uplink positioning reference signal e.g., an SRS-for-positioning, PTRS
  • a sidelink positioning reference signal may be referred to as an “SL-PRS.”
  • the signals may be prepended with “DL,” “UL,” or “SL” to distinguish the direction.
  • DL-DMRS is different from “DL-DMRS .”
  • the reference signal carried on the REs labeled “R” in FIG. 4 may be SRS.
  • SRS transmitted by a UE may be used by a base station to obtain the channel state information (CSI) for the transmitting UE.
  • CSI describes how an RF signal propagates from the UE to the base station and represents the combined effect of scattering, fading, and power decay with distance.
  • the system uses the SRS for resource scheduling, link adaptation, massive MIMO, beam management, etc.
  • a collection of REs that are used for transmission of SRS is referred to as an “SRS resource,” and may be identified by the parameter “SRS-Resourceld.”
  • the collection of resource elements can span multiple PRBs in the frequency domain and ‘N’ (e.g., one or more) consecutive symbol(s) within a slot in the time domain. In a given OFDM symbol, an SRS resource occupies one or more consecutive PRBs.
  • An “SRS resource set” is a set of SRS resources used for the transmission of SRS signals, and is identified by an SRS resource set ID (“SRS-ResourceSetld”).
  • a comb size ‘N’ represents the subcarrier spacing (or frequency/tone spacing) within each symbol of an SRS resource configuration.
  • SRS are transmitted in every Nth subcarrier of a symbol of a PRB.
  • REs corresponding to every fourth subcarrier such as subcarriers 0, 4, 8) are used to transmit SRS of the SRS resource.
  • the illustrated SRS is comb- 4 over four symbols. That is, the locations of the shaded SRS REs indicate a comb-4 SRS resource configuration.
  • an SRS resource may span 1, 2, 4, 8, or 12 consecutive symbols within a slot with a comb size of comb-2, comb-4, or comb-8.
  • the following are the frequency offsets from symbol to symbol for the SRS comb patterns that are currently supported.
  • 1 -symbol comb-2 ⁇ 0 ⁇
  • 2-symbol comb-2 ⁇ 0, 1 ⁇
  • 2-symbol comb-4 ⁇ 0, 2 ⁇
  • 4-symbol comb-4 ⁇ 0, 2, 1, 3 ⁇ (as in the example of FIG.
  • a UE transmits SRS to enable the receiving base station (either the serving base station or a neighboring base station) to measure the channel quality (i.e., CSI) between the UE and the base station.
  • the receiving base station either the serving base station or a neighboring base station
  • the channel quality i.e., CSI
  • SRS can also be specifically configured as uplink positioning reference signals for uplink-based positioning procedures, such as uplink time difference of arrival (UL-TDOA), round-trip-time (RTT), uplink angle-of-arrival (UL-AoA), etc.
  • UL-TDOA uplink time difference of arrival
  • RTT round-trip-time
  • U-AoA uplink angle-of-arrival
  • SRS may refer to SRS configured for channel quality measurements or SRS configured for positioning purposes.
  • the former may be referred to herein as “SRS-for-communication” and/or the latter may be referred to as “SRS-for-positioning” or “positioning SRS” when needed to distinguish the two types of SRS.
  • SRS-for- positioning also referred to as “UL-PRS”
  • SRS-for- positioning also referred to as “UL-PRS”
  • a new staggered pattern within an SRS resource except for single-symbol/comb-2
  • a new comb type for SRS new sequences for SRS
  • a higher number of SRS resource sets per component carrier and a higher number of SRS resources per component carrier.
  • the parameters “SpatialRelationlnfo” and “PathLossReference” are to be configured based on a downlink reference signal or SSB from a neighboring TRP.
  • one SRS resource may be transmitted outside the active BWP, and one SRS resource may span across multiple component carriers.
  • SRS may be configured in RRC connected state and only transmitted within an active BWP. Further, there may be no frequency hopping, no repetition factor, a single antenna port, and new lengths for SRS (e.g., 8 and 12 symbols). There also may be open-loop power control and not closed-loop power control, and comb- 8 (i.e., an SRS transmitted every eighth subcarrier in the same symbol) may be used. Lastly, the UE may transmit through the same transmit beam from multiple SRS resources for UL-AoA. These features may be configured through RRC higher layer signaling (and potentially triggered or activated through a MAC control element (MAC-CE) or downlink control information (DCI)).
  • MAC-CE MAC control element
  • DCI downlink control information
  • Sidelink communication takes place in transmission or reception resource pools.
  • the minimum resource allocation unit is a sub-channel (e.g., a collection of consecutive PRBs in the frequency domain).
  • resource allocation is in one slot intervals.
  • some slots are not available for sidelink, and some slots contain feedback resources.
  • sidelink resources can be (pre)configured to occupy fewer than the 14 symbols of a slot.
  • Radio resource control The RRC configuration can be by pre-configuration (e.g., preloaded on the UE) or configuration (e.g., from a serving base station).
  • FIG. 5A is a diagram 500 of an example slot structure without feedback resources, according to aspects of the disclosure.
  • time is represented horizontally and frequency is represented vertically.
  • the length of each block is one orthogonal frequency division multiplexing (OFDM) symbol, and the 14 symbols make up a slot.
  • the height of each block is one sub-channel.
  • the (pre)configured sub-channel size can be selected from the set of ⁇ 10, 15, 20, 25, 50, 75, 100 ⁇ physical resource blocks (PRBs).
  • PRBs physical resource blocks
  • the first symbol is a repetition of the preceding symbol and is used for automatic gain control (AGC) setting.
  • AGC automatic gain control
  • FIG. 5A the vertical and horizontal hashing.
  • the PSCCH physical sidelink control channel
  • PSSCH physical sidelink shared channel
  • the PSCCH carries control information about sidelink resource allocation and descriptions about sidelink data transmitted to the UE.
  • the PSSCH carries user data for the UE.
  • the PSCCH occupies half the bandwidth of the sub-channel and only three symbols. Finally, a gap symbol is present after the PSSCH.
  • FIG. 5B is a diagram 550 of an example slot structure with feedback resources, according to aspects of the disclosure.
  • time is represented horizontally and frequency is represented vertically.
  • the length of each block is one OFDM symbol, and the 14 symbols make up a slot.
  • the height of each block is one sub-channel.
  • the slot structure illustrated in FIG. 5B is similar to the slot structure illustrated in FIG. 5A, except that the slot structure illustrated in FIG. 5B includes feedback resources. Specifically, two symbols at the end of the slot have been dedicated to the physical sidelink feedback channel (PSFCH). The first PSFCH symbol is a repetition of the second PSFCH symbol for AGC setting. In addition to the gap symbol after the PSSCH, there is a gap symbol after the two PSFCH symbols.
  • resources for the PSFCH can be configured with a periodicity selected from the set of ⁇ 0, 1, 2, 4 ⁇ slots.
  • the physical sidelink control channel carries sidelink control information (SCI).
  • SCI-1 First stage SCI
  • SCI- 2 second stage SCI
  • SCI-2 is transmitted on the physical sidelink shared channel (PSSCH) and contains information for decoding the data that will be transmitted on the shared channel (SCH) of the sidelink.
  • SCI-1 information is decodable by all UEs, whereas SCI-2 information may include formats that are only decodable by certain UEs. This ensures that new features can be introduced in SCI-2 while maintaining resource reservation backward compatibility in SCI-1.
  • FIG. 6 is a diagram 600 showing how the shared channel (SCH) is established on a sidelink between two or more UEs, according to aspects of the disclosure.
  • information in the SCI-1 602 is used for resource allocation 604 (by the network or the involved UEs) for the SCI-2 606 and SCH 608.
  • information in the 6CI-1 602 is used to determine/decode the contents of the SCI-2 606 transmitted on the allocated resources.
  • a receiver UE needs both the resource allocation 604 and the SCI-1 602 to decode the SCI-2 606.
  • Information in the SCI-2 606 is then used to determine/decode the SCH 608.
  • a sidelink resource pool may include resources for sidelink communication (transmission and/or reception), sidelink positioning (referred to as a resource pool for positioning (RP-P)), or both communication and positioning.
  • a resource pool configured for both communication and positioning is referred to as a “shared” resource pool.
  • the RP-P is indicated by an offset, periodicity, number of consecutive symbols within a slot (e.g., as few as one symbol), and/or the bandwidth within a component carrier (or the bandwidth across multiple component carriers).
  • the RP-P can be associated with a zone or a distance from a reference location.
  • a base station (or a UE, depending on the resource allocation mode) can assign, to another UE, one or more resource configurations from the RP-Ps.
  • a UE e.g., a relay or a remote UE
  • QoS quality of service
  • a base station or a UE can configure/assign rate matching resources or RP-P for rate matching and/or muting to a sidelink UE such that when a collision exists between the assigned resources and another resource pool that contains data (PSSCH) and/or control (PSCCH), the sidelink UE is expected to rate match, mute, and/or puncture the data, DMRS, and/or CSI-RS within the colliding resources. This would enable orthogonalization between positioning and data transmissions for increased coverage of PRS signals.
  • PSSCH data
  • PSCCH power control
  • FIG. 7 is a diagram 700 illustrating an example of a resource pool for positioning configured within a sidelink resource pool for communication (i.e., a shared resource pool), according to aspects of the disclosure.
  • time is represented horizontally and frequency is represented vertically.
  • the length of each block is an orthogonal frequency division multiplexing (OFDM) symbol, and the 14 symbols make up a slot.
  • OFDM orthogonal frequency division multiplexing
  • the height of each block is a subchannel.
  • S-PRS Sidelink positioning reference signals
  • DL-PRS downlink PRS
  • an SL-PRS resource is composed of one or more resource elements (i.e., one OFDM symbol in the time domain and one subcarrier in the frequency domain).
  • SL-PRS resources have been designed with a comb-based pattern to enable fast Fourier transform (FFT)-based processing at the receiver.
  • FFT fast Fourier transform
  • SL-PRS resources are composed of unstaggered, or only partially staggered, resource elements in the frequency domain to provide small time of arrival (TOA) uncertainty and reduced overhead of each SL-PRS resource.
  • SL-PRS may also be associated with specific RP-Ps (e.g., certain SL-PRS may be allocated in certain RP-Ps).
  • SL-PRS have also been defined with intra-slot repetition (not shown in FIG. 7) to allow for combining gains (if needed).
  • FIGS. 8A-8B illustrate diagrams 800-850 illustrating additional examples of resource pools for positioning configured within sidelink resource pools for communication. Similar to FIG. 7, the examples of FIGS. 8A-8B illustrate shared resource pool structures.
  • the following parameters may be defined, e.g.: PSCCH and SL-PRS are only TDMed, PSSCH and SL-PRS are only TDMed (e.g, maximum comb size is 4), PSSCH carries both SCL2 and SL-SCH (e.g, a new SCL2 format is introduced), SL-PRS is mapped on consecutive symbols, SL-PRS is not mapped on symbols with PSSCH DMRS, SL-PRS transmit power is the same as PSSCH’s (e.g, this implies per-RE power boosting will be applied for Comb 2 and 4).
  • FIG. 9 illustrates a diagram 900 illustrating another example of a resource pool for positioning configured within a sidelink resource pool for communication.
  • a dedicated resource pool structure is depicted.
  • the following parameters may be defined, e.g.: SL-PRS is immediately preceded by an AGC symbol (except cases where RANI agrees otherwise), SL-PRS is immediately followed by a gap symbol (at least when the gap symbol is the last SL symbol in a slot), PSCCH and SL-PRS can only be TDMed, Different comb size (N) and SL-PRS duration (M) can be supported in the same resource pool (e.g, one set of OFDM symbols can only have a single (M, N) combination), PSSCH is mapped to the first sidelink symbols in a slot.
  • Same DMRS as SL PSCCH in communications. Number of symbols is (pre- Configured to 1, 2, 3. Number of PRBs is (pre-)configured using SL communications
  • SL-PRS resource for a shared resource pool, there may be an explicit (pre-)configuration of SL-PRS resources in a slot, applicable for an indicated frequency domain allocation, which includes, e.g. : SL-PRS Resource ID, (M, N) pattern, comb offset.
  • SL-PRS resource is mapped to the last consecutive ‘M’ SL symbols in the slot that can be used for SL-PRS, i.e., taking into consideration multiplexing with PSSCH DMRS, PT-RS, CSI-RS, PSFCH, gap symbols, AGC symbols, PSCCH in the slot.
  • the maximum number of SL-PRS resources in a slot of a shared resource pool may be (pre-)configured.
  • the higher layers provide the following parameters for candidate SL-PRS transmission(s): Resource pool from which to report SL-PRS resources, Priority, Delay budget, Reservation period, List of resources for pre-emption and re-evaluation, Set of SL-PRS resource ID (s) which can include all (pre-)configured SL-PRS resource IDs.
  • a SL resource (re)selection procedure (e.g., as defined in 3GPP Rel. 16 or Rel. 17) is independently performed for each SL carrier.
  • Channel busy ratio may be defined in sidelink to keep track of channel resource utilization at each given node.
  • SL CBR may be defined as follows, e.g.:
  • the SL RS SI used to determine the SL CBR may be defined as follows, e.g.:
  • sl-ThreshS-RSSI-CBR indicates the S-RSSI threshold for determining the contribution of a sub-channel to the CBR measurement.
  • Value 0 corresponds to -112 dBm, value 1 to -110 dBm, value n to (-112 + n*2) dBm, and so on.
  • sl- TimeWindowSizeCBR indicates the time window size for CBR measurement.
  • CBR ranges may be pre-defined.
  • the UE measures the CBR and maps it to one of the ranges to get the CRLimit.
  • the UE also estimates its CR and if it is higher than the CRLimit, the UE adjusts transmission parameter(s) for the SL-PRS.
  • congestion control can restrict at least the following range of parameters for SL-PRS configuration per resource pool by CBR and priority: Maximum SL-PRS transmission power, Maximum Number of SL-PRS (re-)transmissions, Minimum Periodicity of SL-PRS, Maximum Number of SL-PRS resources in a slot, Maximum comb-size of a SL-PRS resource in a slot, Maximum Number of OFDM symbols of a SL-PRS resource in a slot
  • the CR limits are (pre)- configured per priority in a resource pool.
  • the CR limit may be left to UE implementation.
  • the SL-PRS can share the same restriction of PSSCH without specific enhancement in addition to what is already predefined.
  • CBR/CR may be redefined by considering the SL-PRS resource allocation/configuration.
  • SL-RSSI is measured on a slot configured for transmission of PSCCH and SL-PRS.
  • a single SL-RSSI is measured on symbols with both SL-PRS and PSCCH.
  • CBR/CR may be separately configured for a dedicated resource pool and could adopt the legacy values.
  • SL-PRS CR for a dedicated resource pool for positioning is defined as follows, e.g.: Sidelink PRS Channel Occupancy Ratio (SL-PRS CR) evaluated at slot /? is defined as the total number of SL-PRS resources sub-channels used for its transmissions in slots ⁇ n-a. n-1] and granted in slots [//, n+b] divided by the total number of configured SL-PRS resources sub-channels in the transmission pool over [n-a, n+b],
  • SL-PRS CBR for a dedicated resource pool for positioning is defined as follows, e.g.: SL-PRS Channel Busy Ratio (SL-PRS CBR) measured in slot n is defined as the portion of sub-channels SL-PRS resources in the resource pool whose SL-PRS RS SI measured by the UE exceed a (pre-)configured threshold sensed over a CBR measurement window ⁇ n-a. n-1], wherein a is equal to 100 or 100-2 ⁇ slots, according to higher layer parameter [sl-TimeWindowSizeCBR] .
  • SL-PRS RSSI for a dedicated resource pool for positioning is defined as follows, e.g.: Sidelink PRS Received Signal Strength Indicator (SL-PRS RSSI) of a SL-PRS resource is defined as the linear average of the total received power (in [W]) observed in the configured sub-channelresource elements in OFDM symbols of a slot configured for the SL-PRS resource, starting from the 2nd OFDM symbol, and observed in the configured sub-channel in OFDM symbols of a slot configured for the associated PSCCH, starting from the 2nd OFDM symbol, and PSSCH, starting from the 2nd OFDM symbol.
  • S-PRS RSSI Sidelink PRS Received Signal Strength Indicator
  • SL-PRS CR SL-PRS CBR
  • SL-PRS RSSI SL-PRS RSSI
  • FIG. 10 illustrates an exemplary process 1000 of communications according to an aspect of the disclosure.
  • the process 1000 of FIG. 10 is performed by a UE, such as UE 302.
  • a position estimation entity is deployed separately from the UE (e.g., another UE sometimes referred to as an anchor UE or server UE, a network component such as LMF integrated at gNB/BS 304 or 0-RAN component, or a remote location server such as network entity 306, etc.).
  • the position estimation entity may correspond to another UE (e.g., sidelink anchor UE or sidelink server UE) or to the UE itself.
  • reference to any Rx/Tx operations between the position estimation entity and the UE in which the position estimation entity is integrated may correspond to transfer of information between different logical components of the device over a data bus, etc.
  • the UE determines a first resource configuration associated with a first sidelink resource pool for positioning (SL-RP-P).
  • a means for performing the determination of 1010 includes processor(s) 342, SL-PRS aggregation component 348, etc., of FIG. 3 A.
  • the UE determines a second resource configuration associated with a second SL-RP-P, wherein the first SL-RP-P and the second SL-RP-P belong to a set of aggregated SL-RP-Ps associated with an aggregated SL-RP-P configuration with one or more common parameters.
  • a means for performing the determination of 1020 includes processor(s) 342, SL-PRS aggregation component 348, etc., of FIG. 3 A.
  • the UE e.g., processor(s) 342, receiver 312 or 322, transmitter 314 or 324, SL-PRS aggregation component 348, etc.
  • a means for performing the communication of 1030 includes processor(s) 342, receiver 312 or 322, transmitter 314 or 324, SL-PRS aggregation component 348, etc., of FIG. 3A.
  • FIG. 11 illustrates an exemplary process 1100 of communications according to an aspect of the disclosure.
  • the process 1100 of FIG. 11 is performed by a position estimation entity.
  • the position estimation entity may correspond to a network component (e.g., an LMF integrated at gNB/BS 304 or 0-RAN component or a remote location server such as network entity 306, etc.).
  • the position estimation entity may correspond to another UE (e.g., sidelink anchor UE or sidelink server UE) or to the target UE itself.
  • the position estimation entity may provide the aggregated SL-RP-P configuration to the UE which performs the process 1000 of FIG. 10.
  • the position estimation entity determines a first resource configuration associated with a first sidelink resource pool for positioning (SL- RP-P).
  • a means for performing the determination of 1110 includes processor(s) 342 or 384 or 394, SL-PRS aggregation component 348 or 388 or 398, etc., of FIGS. 3A-3C.
  • the position estimation entity determines a second resource configuration associated with a second SL-RP-P.
  • a means for performing the determination of 1120 includes processor(s) 342 or 384 or 394, SL-PRS aggregation component 348 or 388 or 398, etc., of FIGS. 3A-3C.
  • the position estimation entity determines to aggregate the first SL-RP-P and the second SL-RP-P in a set of aggregated SL-RP-Ps associated with an aggregated SL-RP-P configuration with one or more common parameters.
  • a means for performing the determination of 1130 includes processor(s) 342 or 384 or 394, SL-PRS aggregation component 348 or 388 or 398, etc., of FIGS. 3A- 3C.
  • the position estimation entity e.g., transmitter 314 or 324 or 354 or 364, network transceiver(s) 380 or 390, data bus 308 or 382, etc.
  • UE user equipment
  • a means for performing the transmission of 1140 includes transmitter 314 or 324 or 354 or 364, network transceiver(s) 380 or 390, data bus 308 or 382, etc., of FIGS. 3A-3C.
  • the communication of the SL-PRS at 1030 comprises transmitting the SL-PRS, or the communication of the SL-PRS at 1030 comprises receiving and measuring the SL-PRS.
  • the set of aggregated SL-RP-Ps comprises at least one dedicated SL-RP-P, at least one shared SL-RP-P, or a combination thereof.
  • the first SL-RP-P is associated with a first component carrier (CC) and the second SL-RP-P is associated with a second CC.
  • the first SL-RP-P and the second SL-RP-P are separated by one or more guard bands in a frequency-domain.
  • the one or more guard bands are configured so that a propagation of a comb-pattern of the SL-PRS in uniform across the first SL-RP- P, the second SL-RP-P and the one or more guard bands.
  • the one or more common parameters comprise: a set of slots comprising the set of aggregated SL-RP-Ps, or a set of symbols comprising the set of aggregated SL-RP-Ps, or a UE antenna reference point (ARP), or a radio frequency (RF) chain or antenna, or quasi-location (QCL) information, or a number of symbols per slot, or a starting symbol location per slot, or a repetition factor, or a symbol length, or cyclic prefix (CP) length (e.g., same numerology), or subcarrier spacing (SCS) (e.g., same numerology), or bandwidth, or comb-pattern, or power per sub-carrier, or numerology grid, or per-symbol comb-pattern spacing uniformity (e.g., in frequencydomain; note that this does not preclude some or all REs in the guard band between two PFLs), or phase continuity between the set of aggregated SL-RP-Ps
  • the set of aggregated SL-RP-Ps is determined at the UE based on the one or more common parameters (e.g., the common parameter(s) are detected as common, which triggers the SL-RP-P aggregation).
  • the aggregated SL-RP-P configuration is determined independently at the UE and indicated to one or more other UEs via sidelink control information (SCI) (e.g., SCI-1 or SCI-2).
  • SCI sidelink control information
  • the aggregated SL-RP-P configuration is indicated to the UE by a network component or by another UE via sidelink control information (SCI).
  • SCI sidelink control information
  • the one or more common parameters are indicated in each of the first resource configuration and the second resource configuration, or the one or more common parameters are indicated only one of the first resource configuration and the second resource configuration, and the one or more common parameters are applied to the other resource configuration based on the first SL-RP-P and the second SL-RP-P belonging to the set of aggregated SL-RP-Ps.
  • the set of aggregated SL-RP-Ps is associated with a maximum total transmission power for the SL-PRS across all SL-RP-Ps in the set of aggregated SL-RP-Ps.
  • the maximum total transmission power for the SL- PRS across all SL-RP-Ps in the set of aggregated SL-RP-Ps is based on a sidelink Synchronization Signal Block (SL-SSB) priority parameter.
  • SL-SSB sidelink Synchronization Signal Block
  • the SL-SSB priority parameter designates a first subset of resources in the set of aggregated SL-RP- Ps that may be dropped to satisfy the maximum total transmission power, or the SL-SSB priority parameter designates a second subset of resources in the set of aggregated SL- RP-Ps that may not be dropped to satisfy the maximum total transmission power, or a combination thereof
  • the set of aggregated SL-RP-Ps is further associated with a resource collision parameter.
  • the resource collision parameter designates a first subset of resources in the set of aggregated SL-RP-Ps that may be dropped in response to collision with another function, or the resource collision parameter designates a second subset of resources in the set of aggregated SL-RP-Ps that may not be dropped in response to collision with the another function, or a combination thereof.
  • the UE further transmits a SL-RP-P aggregation capability of the UE, the set of aggregated SL-RP-Ps is based on the SL-RP- P aggregation capability of the UE.
  • the SL-RP-P aggregation capability of the UE comprises a radio resource control (RRC) CONNECTED SL-RP-P aggregation capability, or a RRC IDLE SL-RP-P aggregation capability, or a RRC INACTIVE SL- RP-P aggregation capability, or a Mode 1 SL-RP-P aggregation capability associated with network-controlled resource allocation, or a Mode 2 SL-RP-P aggregation capability associated with UE-autonomous resource allocation, a joint Mode SL-RP-P aggregation capability associated with both network-controlled resource allocation and UE- autonomous resource allocation, or a sidelink carrier aggregation (CA)-dependent SL- RP-P aggregation capability, or a sidelink CA-independent SL-RP-P aggregation capability, or any combination thereof.
  • RRC radio resource control
  • CA sidelink carrier aggregation
  • the SL-RP-P aggregation capability of the UE comprises a maximum number of SL-RP-Ps for aggregation, or a maximum number of shared SL-RP-Ps for aggregation, or a maximum number of dedicated SL-RP- Ps for aggregation, or a maximum number of shared and dedicated SL-RP-Ps for hybrid aggregation, or any combination thereof.
  • the SL-RP-P aggregation capability of the UE comprises a maximum number of aggregated positioning measurements associated with aggregated dedicated SL-RP-Ps, or a maximum number of aggregated positioning measurements associated with aggregated shared SL-RP-Ps, or a maximum number of aggregated positioning measurements associated with hybrid aggregation of dedicated and shared SL-RP-Ps, or any combination thereof.
  • the SL-RP-P aggregation capability of the UE comprises a maximum number of aggregated SL-RP-P configurations.
  • the maximum number of aggregated SL-RP-P configurations is one.
  • the maximum number of aggregated SL-RP-P configurations is more than one, with each aggregated SL-RP-P configuration capable of being associated with a different set of configuration-specific common parameters.
  • the SL-RP-P aggregation capability of the UE comprises a maximum number of aggregated SL-RP-P resources that the UE is capable of processing over a time period, or a maximum number of simultaneously active aggregated SL-RP-P resources, or a maximum amount of aggregated bandwidth across aggregated SL-RP-Ps, or any combination thereof.
  • the SL-PRS is associated with a sidelink time difference of arrival (TDOA)-based position-estimation session, a sidelink time of arrival (TOA)-based estimation session, a sidelink multi-round trip time (RTT)-based position estimation session, a sidelink angle of arrival (AOA)-based position estimation session, or an angle of departure (AOD)-based position estimation session.
  • TDOA sidelink time difference of arrival
  • TOA sidelink time of arrival
  • RTT sidelink multi-round trip time
  • AOA angle of arrival
  • AOD angle of departure
  • the position estimation entity may correspond to a network component or an anchor UE or a server UE.
  • the same setting(s) may be applied across SL CCs, such as SL starting symbol within a slot, SL symbol length within a slot, CP length, the set of slots that may belong to resource pool should be the same among aggregated carriers and such set of slots includes all the slots except NS-SSB slots, Non- SL slots and reserved slots, the bitmap used to determine logical slots of different resource pools among aggregated carriers, PSFCH resource period, number of PSCCH symbols, or any combination thereof.
  • some or all of the above-noted parameters may be pre-configured (e.g., pre-defined or network-configured or some combination thereof).
  • the (pre-)configuration may be designed so that various parameters are aligned (e.g., CPE length, RP bitmap, PSFCH resource period, etc) to improve SL positioning performance.
  • various parameters e.g., CPE length, RP bitmap, PSFCH resource period, etc.
  • UE may abort or stop the SL-PRS-based position estimation session.
  • it may be left up to UE implementation (e.g., not pre-configured), in which case there will be no performance requirements for measurement and positioning accuracy.
  • FIG. 12 illustrates a set of aggregated SL resource pools 1200, in accordance with an example implementation 1200 of the processes 1000-1100 of FIGS. 10-11, respectively.
  • the set of aggregated SL resource pools 1200 comprises a first shared SL resource pool on a first carrier (e.g., a first component carrier (CC), denoted as CC1) and a second shared SL resource pool on a second carrier (e.g., a second CC, denoted as CC2), each of which is configured as described above with respect to FIG. 8A.
  • the aggregated SL PRS resources are indicated by 1210.
  • CC1 and CC2 may be separated (in frequency-domain) by one or more CC guard bands.
  • SL PRS Resource ID (M, N) pattern
  • comb offset For a given value of ‘M’, SL PRS resource is mapped to the last consecutive ‘M’ SL symbols in the slot that can be used for SL PRS, i.e., taking into consideration multiplexing with PSSCH DMRS, PT-RS, CSLRS, PSFCH, gap symbols, AGC symbols, PSCCH in the slot.
  • one example SL-RP-P aggregation rule for the case of two (2) shared resource pools on different CCs as illustrated in FIG. 12, may be that the SL PRS resource is mapped to the last consecutive ‘M’ SL symbols in the slot that can be used for SL PRS, i.e., taking into consideration multiplexing with PSSCH DMRS, PT-RS, CSI-RS, PSFCH, gap symbols, AGC symbols, PSCCH in the slot, across both shared resource pools.
  • CC1 and CC2 may be separated (in frequency-domain) by one or more CC guard bands.
  • the CC guard bands (which do not carry SL-PRS) may be configured such that a comb-pattern for SL-PRS 1 and 2 across CC1 and CC2 is maintained as if the CC guard bands carried SL-PRS 1 and 2.
  • one example SL-RP-P aggregation rule may be that the UE shall have the same AGC gap configuration across the aggregated resource pool used for the positioning. In another aspect, one example SL-RP-P aggregation rule may be that UE shall have the same gap configuration across the aggregated resource pool used for the positioning.
  • FIG. 14 illustrates a set of aggregated SL resource pools 1400, in accordance with an example implementation 1400 of the processes 1000-1100 of FIGS. 10-11, respectively.
  • the set of aggregated SL resource pools 1400 comprises a first dedicated SL resource pool on a first carrier (e.g., a first component carrier (CC), denoted as CC1) and a second shared SL resource pool on a second carrier (e.g., a second CC, denoted as CC2), which is configured as described above with respect to FIG. 8B (not that in other designs, the dedicated SL resource pool may instead be aggregated with a shared SL resource pool, such as the one depicted in FIG. 8A).
  • CC component carrier
  • the aggregated SL PRS resources are indicated by 1410.
  • CC1 and CC2 may be separated (in frequency-domain) by one or more CC guard bands.
  • the CC guard bands (which do not carry SL-PRS) may be configured such that a comb-pattern for SL-PRS 1 and 2 across CC1 and CC2 is maintained as if the CC guard bands carried SL-PRS 1 and 2.
  • the IE FreqConfigCommon specifies the cellspecific configuration information on one particular carrier frequency for NR sidelink communication, e.g.:
  • SL-FreqConfigCommon-rl6 SEQUENCE ⁇ sl-SCS-SpecificCarrierList-rl6 SEQUENCE (SIZE (L.maxSCSs)) OF SCS- SpecificCarrier, si- Ab soluteF requencyPointA-r 16 ARFCN- V alueNR, sl-AbsoluteFrequencySSB-rl6 ARFCN-ValueNR OPTIONAL, — Need R frequency Shift7p5khzSL-rl 6 ENUMERATED ⁇ true ⁇ OPTIONAL, - Cond V2X-SL- Shared valueN-r 16 INTEGER (- 1..1 ), sl-BWP-List-rl6 SEQUENCE (SIZE (L.maxNrofSL-BWPs-rl6)) OF SL-BWP- ConfigCommon-rl6 OPTIONAL, — Need R sl-SyncPriority-rl6 ENUMERATED
  • SL-FreqConfigCominon field descriptions frequency Shift7p5khzSL Enable the NR SL transmission with a 7.5 kHz shift to the LTE raster. If the field is absent, the frequency shift is disabled.
  • UE may be provided all the common parameter in each SL-RP-P configuration.
  • UE may be provided all the common parameters in only one SL-RP-P configuration (e.g., with an implicit association to/with the other aggregated SL-RP-Ps).
  • si -S SB -Priori tyNR may be used to configure the priority of NR sidelink S-SSB transmission and reception.
  • the transmit power of S- SSB over multiple SL carriers can be determined based on this priority value. Or, it may be assumed that this parameter has the same value over all component carriers.
  • a similar priority parameter for the positioning resources may be defined.
  • si -S SB -Priori tyNR may be used to define the priority for dedicated and shared resource pool common configurations.
  • UE transmit power is insufficient to transmit SL-PRS on each aggregated SL-RP-P.
  • UE may use the si -S SB -Priori tyNR to drop the aggregated resource pools to meet the UE power budget (e.g., this may be applicable if UE is in the battery saving mode, or UE wants to transmit some high priority data on the one of the resource pools, etc.).
  • the position estimation entity e.g., LMF or Anchor UE
  • UE may support (and report) its capability to support the performs PRS aggregation in the given UE state, e.g., RRC CONNECTED, RRC IDLE, and/or RRC INACTIVE.
  • UE ma report its capability to support the SL PRS resource aggregation in SL mode (e.g., separate capability for MODE/scheme 1 (network controlled resource allocation), separate capability for MODE/scheme 2 (UE autonomous resource allocation), or joint capability for both MODE 1 and MODE 2).
  • SL-link PRS aggregation support with respect to SL CA support may be reported (e.g., SL PRS aggregation supported only if SL CA is supported, or SL PRS aggregation supported independent of SL CA is supported for the data cases).
  • SL PRS aggregation supported only if SL CA is supported or SL PRS aggregation supported independent of SL CA is supported for the data cases.
  • UE may report capability of a maximum number of RP pool aggregation support for SL positioning use case with dedicated RPs only, and/or a maximum number of RP pool aggregation support for SL positioning use case with shared RPs only, and/or a maximum number of RP pool aggregation support for SL positioning use case with both shared and dedicated.
  • the maximum number may be pre-defined (e.g., 3, similar to Uu) or may be based be UE-specific (e.g., per the UE capability).
  • capabilities with respect to various resource pool combinations may be supported and reported (e.g., dedicated + dedicated, dedicated + shared, shared + shared, etc.).
  • UE may support (and report) capability of a maximum number of aggregated/joint positioning measurements with aggregation in dedicated resource pool, and/or a maximum number of aggregated/joint positioning measurements with aggregation in shared resource pool, and/or a maximum number of aggregated/joint positioning measurements with aggregation in dedicated and shared resource pool.
  • UE may support (and report) capability a maximum number of aggregation configurations supported.
  • UE may support (and report) only one SL-RP-P may be supported (e.g., all the Positioning resources belong to the same aggregated resource pool, and effective bandwidth is same for the all the resources).
  • UE may support (and report) multiple SL-RP-Ps.
  • different sets of the positioning resources belong to the different aggregated resource pool, an effective bandwidth is different for the different sets, and/or within sets all the resources may share common configurations (e.g., all the resource are aggregated between the RP1 and RP2, all the resource are aggregated between the RP1, RP2 and RP3, etc ).
  • UE may report capability(ies) to support SL PRS bandwidth aggregation measurements, e.g., the maximum number of aggregated PRS resources that can be process in a slots over aggregated RPs, the maximum number of SL-PRS resources that can be simultaneously active, details on the resource pools bandwidth combinations, including maximum number of resource pools, and/or the total aggregated bandwidth, etc.
  • capability(ies) to support SL PRS bandwidth aggregation measurements e.g., the maximum number of aggregated PRS resources that can be process in a slots over aggregated RPs, the maximum number of SL-PRS resources that can be simultaneously active, details on the resource pools bandwidth combinations, including maximum number of resource pools, and/or the total aggregated bandwidth, etc.
  • TDOA time synchronization
  • TOA time
  • AOA AOD
  • RTT resource e.g., RTT or multi-RTT, etc.
  • example clauses can also include a combination of the dependent clause aspect(s) with the subject matter of any other dependent clause or independent clause or a combination of any feature with other dependent and independent clauses.
  • the various aspects disclosed herein expressly include these combinations, unless it is explicitly expressed or can be readily inferred that a specific combination is not intended (e.g., contradictory aspects, such as defining an element as both an electrical insulator and an electrical conductor).
  • aspects of a clause can be included in any other independent clause, even if the clause is not directly dependent on the independent clause.
  • a method of operating a user equipment comprising: determining a first resource configuration associated with a first sidelink resource pool for positioning (SL- RP-P); determining a second resource configuration associated with a second SL-RP-P, wherein the first SL-RP-P and the second SL-RP-P belong to a set of aggregated SL-RP- Ps associated with an aggregated SL-RP-P configuration with one or more common parameters; and communicating SL-PRS via the set of aggregated SL-RP-Ps based on the aggregated SL-RP-P configuration.
  • SL- RP-P sidelink resource pool for positioning
  • Clause 4 The method of any of clauses 1 to 3, wherein the first SL-RP-P is associated with a first component carrier (CC) and the second SL-RP-P is associated with a second CC.
  • CC component carrier
  • Clause 7 The method of any of clauses 1 to 6, wherein the one or more common parameters comprise: a set of slots comprising the set of aggregated SL-RP-Ps, or a set of symbols comprising the set of aggregated SL-RP-Ps, or a UE antenna reference point (ARP), or a radio frequency (RF) chain or antenna, or quasi -location (QCL) information, or a number of symbols per slot, or a starting symbol location per slot, or a repetition factor, or a symbol length, or cyclic prefix (CP) length, or subcarrier spacing (SCS), or bandwidth, or comb-pattern, or power per sub-carrier, or numerology grid, or per-symbol comb-pattern spacing uniformity, or phase continuity between the set of aggregated SL- RP-Ps, or a physical sidelink feedback channel (PSFCH) resource configuration, or a number of physical sidelink control channels (PSCCH), or an automatic gain control (AGC) configuration, or a
  • Clause 8 The method of any of clauses 1 to 7, wherein the set of aggregated SL-RP-Ps is determined at the UE based on the one or more common parameters.
  • Clause 11 The method of any of clauses 1 to 10, wherein the one or more common parameters are indicated in each of the first resource configuration and the second resource configuration, or wherein the one or more common parameters are indicated only one of the first resource configuration and the second resource configuration, and the one or more common parameters are applied to the other resource configuration based on the first SL-RP-P and the second SL-RP-P belonging to the set of aggregated SL-RP- Ps.
  • Clause 12 The method of any of clauses 1 to 11, wherein the set of aggregated SL-RP- Ps is associated with a maximum total transmission power for the SL-PRS across all SL- RP-Ps in the set of aggregated SL-RP-Ps.
  • Clause 14 The method of clause 13, wherein the SL-SSB priority parameter designates a first subset of resources in the set of aggregated SL-RP-Ps that may be dropped to satisfy the maximum total transmission power, or wherein the SL-SSB priority parameter designates a second subset of resources in the set of aggregated SL-RP-Ps that may not be dropped to satisfy the maximum total transmission power, or a combination thereof.
  • Clause 15 The method of any of clauses 1 to 14, wherein the set of aggregated SL-RP- Ps is further associated with a resource collision parameter.
  • Clause 16 The method of any of clauses 13 to 15, wherein the resource collision parameter designates a first subset of resources in the set of aggregated SL-RP-Ps that may be dropped in response to collision with another function, or wherein the resource collision parameter designates a second subset of resources in the set of aggregated SL- RP-Ps that may not be dropped in response to collision with the another function, or a combination thereof.
  • Clause 17 The method of any of clauses 1 to 16, further comprising: transmitting a SL- RP-P aggregation capability of the UE, wherein the set of aggregated SL-RP-Ps is based on the SL-RP-P aggregation capability of the UE. [0226] Clause 18.
  • the SL-RP-P aggregation capability of the UE comprises: a radio resource control (RRC) CONNECTED SL-RP-P aggregation capability, or a RRC IDLE SL-RP-P aggregation capability, or a RRC INACTIVE SL- RP-P aggregation capability, or a Mode 1 SL-RP-P aggregation capability associated with network-controlled resource allocation, or a Mode 2 SL-RP-P aggregation capability associated with UE-autonomous resource allocation, a joint Mode SL-RP-P aggregation capability associated with both network-controlled resource allocation and UE- autonomous resource allocation, or a sidelink carrier aggregation (CA)-dependent SL- RP-P aggregation capability, or a sidelink CA-independent SL-RP-P aggregation capability, or any combination thereof.
  • RRC radio resource control
  • CA sidelink carrier aggregation
  • Clause 19 The method of any of clauses 17 to 18, wherein the SL-RP-P aggregation capability of the UE comprises: a maximum number of SL-RP-Ps for aggregation, or a maximum number of shared SL-RP-Ps for aggregation, or a maximum number of dedicated SL-RP-Ps for aggregation, or a maximum number of shared and dedicated SL- RP-Ps for hybrid aggregation, or any combination thereof.
  • Clause 20 The method of any of clauses 17 to 19, wherein the SL-RP-P aggregation capability of the UE comprises: a maximum number of aggregated positioning measurements associated with aggregated dedicated SL-RP-Ps, or a maximum number of aggregated positioning measurements associated with aggregated shared SL-RP-Ps, or a maximum number of aggregated positioning measurements associated with hybrid aggregation of dedicated and shared SL-RP-Ps, or any combination thereof.
  • Clause 21 The method of any of clauses 17 to 20, wherein the SL-RP-P aggregation capability of the UE comprises: a maximum number of aggregated SL-RP-P configurations.
  • Clause 22 The method of clause 21, wherein the maximum number of aggregated SL- RP-P configurations is one.
  • Clause 24 The method of any of clauses 17 to 23, wherein the SL-RP-P aggregation capability of the UE comprises: a maximum number of aggregated SL-RP-P resources that the UE is capable of processing over a time period, or a maximum number of simultaneously active aggregated SL-RP-P resources, or a maximum amount of aggregated bandwidth across aggregated SL-RP-Ps, or any combination thereof.
  • Clause 25 The method of any of clauses 1 to 24, wherein the SL-PRS is associated with a sidelink time difference of arrival (TDOA)-based position-estimation session, a sidelink time of arrival (TOA)-based estimation session, a sidelink multi-round trip time (RTT)- based position estimation session, a sidelink angle of arrival (AOA)-based position estimation session, or an angle of departure (AOD)-based position estimation session.
  • TDOA sidelink time difference of arrival
  • TOA sidelink time of arrival
  • RTT sidelink multi-round trip time
  • AOA sidelink angle of arrival
  • AOD angle of departure
  • a method of operating a position estimation entity comprising: determining a first resource configuration associated with a first sidelink resource pool for positioning (SL-RP-P); determining a second resource configuration associated with a second SL- RP-P; determining to aggregate the first SL-RP-P and the second SL-RP-P in a set of aggregated SL-RP-Ps associated with an aggregated SL-RP-P configuration with one or more common parameters; and transmitting an indication of the aggregated SL-RP-P configuration to at least one user equipment (UE).
  • UE user equipment
  • Clause 28 The method of any of clauses 26 to 27, wherein the one or more common parameters comprise: a set of slots comprising the set of aggregated SL-RP-Ps, or a set of symbols comprising the set of aggregated SL-RP-Ps, or a UE antenna reference point (ARP), or a radio frequency (RF) chain or antenna, or quasi -location (QCL) information, or a number of symbols per slot, or a starting symbol location per slot, or a repetition factor, or a symbol length, or cyclic prefix (CP) length, or subcarrier spacing (SCS), or bandwidth, or comb-pattern, or power per sub-carrier, or numerology grid, or per-symbol comb-pattern spacing uniformity, or phase continuity between the set of aggregated SL- RP-Ps, or a physical sidelink feedback channel (PSFCH) resource configuration, or a number of physical sidelink control channels (PSCCH), or an automatic gain control (AGC) configuration, or
  • PSFCH
  • a user equipment comprising: one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors, either alone or in combination, configured to: determine a first resource configuration associated with a first sidelink resource pool for positioning (SL-RP-P); determine a second resource configuration associated with a second SL-RP-P, wherein the first SL-RP-P and the second SL-RP-P belong to a set of aggregated SL-RP-Ps associated with an aggregated SL-RP-P configuration with one or more common parameters; and communicate, via the one or more transceivers, SL-PRS via the set of aggregated SL-RP-Ps based on the aggregated SL-RP-P configuration.
  • SL-RP-P sidelink resource pool for positioning
  • Clause 30 The UE of clause 29, wherein the communication of the SL-PRS comprises transmitting the SL-PRS, or wherein the communication of the SL-PRS comprises receiving and measuring the SL-PRS.
  • Clause 31 The UE of any of clauses 29 to 30, wherein the set of aggregated SL-RP-Ps comprises at least one dedicated SL-RP-P, at least one shared SL-RP-P, or a combination thereof.
  • Clause 32 The UE of any of clauses 29 to 31, wherein the first SL-RP-P is associated with a first component carrier (CC) and the second SL-RP-P is associated with a second CC.
  • CC component carrier
  • Clause 33 The UE of clause 32, wherein the first SL-RP-P and the second SL-RP-P are separated by one or more guard bands in a frequency-domain.
  • Clause 34 The UE of clause 33, wherein the one or more guard bands are configured so that a propagation of a comb-pattern of the SL-PRS in uniform across the first SL-RP-P, the second SL-RP-P and the one or more guard bands.
  • the one or more common parameters comprise: a set of slots comprising the set of aggregated SL-RP-Ps, or a set of symbols comprising the set of aggregated SL-RP-Ps, or a UE antenna reference point (ARP), or a radio frequency (RF) chain or antenna, or quasi -location (QCL) information, or a number of symbols per slot, or a starting symbol location per slot, or a repetition factor, or a symbol length, or cyclic prefix (CP) length, or subcarrier spacing (SCS), or bandwidth, or comb-pattern, or power per sub-carrier, or numerology grid, or per-symbol comb-pattern spacing uniformity, or phase continuity between the set of aggregated SL- RP-Ps, or a physical sidelink feedback channel (PSFCH) resource configuration, or a number of physical sidelink control channels (PSCCH), or an automatic gain control (AGC) configuration,
  • PSFCH physical sidelink feedback channel
  • PSCCH physical sidelink control channels
  • Clause 36 The UE of any of clauses 29 to 35, wherein the set of aggregated SL-RP-Ps is determined at the UE based on the one or more common parameters.
  • Clause 37 The UE of any of clauses 29 to 36, wherein the aggregated SL-RP-P configuration is determined independently at the UE and indicated to one or more other UEs via sidelink control information (SCI).
  • SCI sidelink control information
  • Clause 38 The UE of any of clauses 29 to 37, wherein the aggregated SL-RP-P configuration is indicated to the UE by a network component or by another UE via sidelink control information (SCI).
  • SCI sidelink control information
  • Clause 39 The UE of any of clauses 29 to 38, wherein the one or more common parameters are indicated in each of the first resource configuration and the second resource configuration, or wherein the one or more common parameters are indicated only one of the first resource configuration and the second resource configuration, and the one or more common parameters are applied to the other resource configuration based on the first SL-RP-P and the second SL-RP-P belonging to the set of aggregated SL-RP- Ps.
  • Clause 40 The UE of any of clauses 29 to 39, wherein the set of aggregated SL-RP-Ps is associated with a maximum total transmission power for the SL-PRS across all SL-RP- Ps in the set of aggregated SL-RP-Ps.
  • Clause 41 The UE of clause 40, wherein the maximum total transmission power for the SL-PRS across all SL-RP-Ps in the set of aggregated SL-RP-Ps is based on a sidelink Synchronization Signal Block (SL-SSB) priority parameter.
  • SL-SSB sidelink Synchronization Signal Block
  • Clause 42 The UE of clause 41, wherein the SL-SSB priority parameter designates a first subset of resources in the set of aggregated SL-RP-Ps that may be dropped to satisfy the maximum total transmission power, or wherein the SL-SSB priority parameter designates a second subset of resources in the set of aggregated SL-RP-Ps that may not be dropped to satisfy the maximum total transmission power, or a combination thereof.
  • Clause 43 The UE of any of clauses 29 to 42, wherein the set of aggregated SL-RP-Ps is further associated with a resource collision parameter.
  • Clause 44 The UE of any of clauses 41 to 43, wherein the resource collision parameter designates a first subset of resources in the set of aggregated SL-RP-Ps that may be dropped in response to collision with another function, or wherein the resource collision parameter designates a second subset of resources in the set of aggregated SL-RP-Ps that may not be dropped in response to collision with the another function, or a combination thereof.
  • Clause 45 The UE of any of clauses 29 to 44, wherein the one or more processors, either alone or in combination, are further configured to: transmit, via the one or more transceivers, a SL-RP-P aggregation capability of the UE, wherein the set of aggregated SL-RP-Ps is based on the SL-RP-P aggregation capability of the UE.
  • the SL-RP-P aggregation capability of the UE comprises: a radio resource control (RRC) CONNECTED SL-RP-P aggregation capability, or a RRC IDLE SL-RP-P aggregation capability, or a RRC INACTIVE SL- RP-P aggregation capability, or a Mode 1 SL-RP-P aggregation capability associated with network-controlled resource allocation, or a Mode 2 SL-RP-P aggregation capability associated with UE-autonomous resource allocation, a joint Mode SL-RP-P aggregation capability associated with both network-controlled resource allocation and UE- autonomous resource allocation, or a sidelink carrier aggregation (CA)-dependent SL- RP-P aggregation capability, or a sidelink CA-independent SL-RP-P aggregation capability, or any combination thereof.
  • RRC radio resource control
  • CA sidelink carrier aggregation
  • Clause 47 The UE of any of clauses 45 to 46, wherein the SL-RP-P aggregation capability of the UE comprises: a maximum number of SL-RP-Ps for aggregation, or a maximum number of shared SL-RP-Ps for aggregation, or a maximum number of dedicated SL-RP- Ps for aggregation, or a maximum number of shared and dedicated SL-RP-Ps for hybrid aggregation, or any combination thereof.
  • Clause 48 The UE of any of clauses 45 to 47, wherein the SL-RP-P aggregation capability of the UE comprises: a maximum number of aggregated positioning measurements associated with aggregated dedicated SL-RP-Ps, or a maximum number of aggregated positioning measurements associated with aggregated shared SL-RP-Ps, or a maximum number of aggregated positioning measurements associated with hybrid aggregation of dedicated and shared SL-RP-Ps, or any combination thereof.
  • Clause 49 The UE of any of clauses 45 to 48, wherein the SL-RP-P aggregation capability of the UE comprises: a maximum number of aggregated SL-RP-P configurations.
  • Clause 50 The UE of clause 49, wherein the maximum number of aggregated SL-RP-P configurations is one.
  • Clause 51 The UE of any of clauses 49 to 50, wherein the maximum number of aggregated SL-RP-P configurations is more than one, with each aggregated SL-RP-P configuration capable of being associated with a different set of configuration-specific common parameters.
  • Clause 52 The UE of any of clauses 45 to 51, wherein the SL-RP-P aggregation capability of the UE comprises: a maximum number of aggregated SL-RP-P resources that the UE is capable of processing over a time period, or a maximum number of simultaneously active aggregated SL-RP-P resources, or a maximum amount of aggregated bandwidth across aggregated SL-RP-Ps, or any combination thereof.
  • Clause 53 The UE of any of clauses 29 to 52, wherein the SL-PRS is associated with a sidelink time difference of arrival (TDOA)-based position-estimation session, a sidelink time of arrival (TOA)-based estimation session, a sidelink multi-round trip time (RTT)- based position estimation session, a sidelink angle of arrival (AOA)-based position estimation session, or an angle of departure (AOD)-based position estimation session.
  • TDOA sidelink time difference of arrival
  • TOA sidelink time of arrival
  • RTT sidelink multi-round trip time
  • AOA sidelink angle of arrival
  • AOD angle of departure
  • a position estimation entity comprising: one or more memories; one or more transceivers; and one or more processors communicatively coupled to the one or more memories and the one or more transceivers, the one or more processors, either alone or in combination, configured to: determine a first resource configuration associated with a first sidelink resource pool for positioning (SL-RP-P); determine a second resource configuration associated with a second SL-RP-P; determine to aggregate the first SL-RP- P and the second SL-RP-P in a set of aggregated SL-RP-Ps associated with an aggregated SL-RP-P configuration with one or more common parameters; and transmit, via the one or more transceivers, an indication of the aggregated SL-RP-P configuration to at least one user equipment (UE).
  • UE user equipment
  • Clause 56 The position estimation entity of any of clauses 54 to 55, wherein the one or more common parameters comprise: a set of slots comprising the set of aggregated SL- RP-Ps, or a set of symbols comprising the set of aggregated SL-RP-Ps, or a UE antenna reference point (ARP), or a radio frequency (RF) chain or antenna, or quasi-location (QCL) information, or a number of symbols per slot, or a starting symbol location per slot, or a repetition factor, or a symbol length, or cyclic prefix (CP) length, or subcarrier spacing (SCS), or bandwidth, or comb-pattern, or power per sub-carrier, or numerology grid, or per-symbol comb-pattern spacing uniformity, or phase continuity between the set of aggregated SL-RP-Ps, or a physical sidelink feedback channel (PSFCH) resource configuration, or a number of physical sidelink control channels (PSCCH), or an automatic gain control (AGC) configuration,
  • a user equipment comprising: means for determining a first resource configuration associated with a first sidelink resource pool for positioning (SL-RP-P); means for determining a second resource configuration associated with a second SL-RP- P, wherein the first SL-RP-P and the second SL-RP-P belong to a set of aggregated SL- RP-Ps associated with an aggregated SL-RP-P configuration with one or more common parameters; and means for communicating SL-PRS via the set of aggregated SL-RP-Ps based on the aggregated SL-RP-P configuration.
  • SL-RP-P sidelink resource pool for positioning
  • Clause 58 The UE of clause 57, wherein the communication of the SL-PRS comprises transmitting the SL-PRS, or wherein the communication of the SL-PRS comprises receiving and measuring the SL-PRS.
  • Clause 59 The UE of any of clauses 57 to 58, wherein the set of aggregated SL-RP-Ps comprises at least one dedicated SL-RP-P, at least one shared SL-RP-P, or a combination thereof.
  • Clause 60 The UE of any of clauses 57 to 59, wherein the first SL-RP-P is associated with a first component carrier (CC) and the second SL-RP-P is associated with a second CC.
  • CC component carrier
  • Clause 61 The UE of clause 60, wherein the first SL-RP-P and the second SL-RP-P are separated by one or more guard bands in a frequency-domain.
  • Clause 62 The UE of clause 61, wherein the one or more guard bands are configured so that a propagation of a comb-pattern of the SL-PRS in uniform across the first SL-RP-P, the second SL-RP-P and the one or more guard bands.
  • Clause 63 The UE of any of clauses 57 to 62, wherein the one or more common parameters comprise: a set of slots comprising the set of aggregated SL-RP-Ps, or a set of symbols comprising the set of aggregated SL-RP-Ps, or a UE antenna reference point (ARP), or a radio frequency (RF) chain or antenna, or quasi -location (QCL) information, or a number of symbols per slot, or a starting symbol location per slot, or a repetition factor, or a symbol length, or cyclic prefix (CP) length, or subcarrier spacing (SCS), or bandwidth, or comb-pattern, or power per sub-carrier, or numerology grid, or per-symbol comb-pattern spacing uniformity, or phase continuity between the set of aggregated SL- RP-Ps, or a physical sidelink feedback channel (PSFCH) resource configuration, or a number of physical sidelink control channels (PSCCH), or an automatic gain control (AGC
  • Clause 64 The UE of any of clauses 57 to 63, wherein the set of aggregated SL-RP-Ps is determined at the UE based on the one or more common parameters.
  • Clause 65 The UE of any of clauses 57 to 64, wherein the aggregated SL-RP-P configuration is determined independently at the UE and indicated to one or more other UEs via sidelink control information (SCI).
  • SCI sidelink control information
  • Clause 66 The UE of any of clauses 57 to 65, wherein the aggregated SL-RP-P configuration is indicated to the UE by a network component or by another UE via sidelink control information (SCI).
  • SCI sidelink control information
  • Clause 67 The UE of any of clauses 57 to 66, wherein the one or more common parameters are indicated in each of the first resource configuration and the second resource configuration, or wherein the one or more common parameters are indicated only one of the first resource configuration and the second resource configuration, and the one or more common parameters are applied to the other resource configuration based on the first SL-RP-P and the second SL-RP-P belonging to the set of aggregated SL-RP- Ps.
  • Clause 68 The UE of any of clauses 57 to 67, wherein the set of aggregated SL-RP-Ps is associated with a maximum total transmission power for the SL-PRS across all SL-RP- Ps in the set of aggregated SL-RP-Ps.
  • Clause 71 The UE of any of clauses 57 to 70, wherein the set of aggregated SL-RP-Ps is further associated with a resource collision parameter.
  • Clause 72 The UE of any of clauses 69 to 71, wherein the resource collision parameter designates a first subset of resources in the set of aggregated SL-RP-Ps that may be dropped in response to collision with another function, or wherein the resource collision parameter designates a second subset of resources in the set of aggregated SL-RP-Ps that may not be dropped in response to collision with the another function, or a combination thereof.
  • Clause 73 The UE of any of clauses 57 to 72, further comprising: means for transmitting a SL-RP-P aggregation capability of the UE, wherein the set of aggregated SL-RP-Ps is based on the SL-RP-P aggregation capability of the UE.
  • the SL-RP-P aggregation capability of the UE comprises: a radio resource control (RRC) CONNECTED SL-RP-P aggregation capability, or a RRC IDLE SL-RP-P aggregation capability, or a RRC INACTIVE SL- RP-P aggregation capability, or a Mode 1 SL-RP-P aggregation capability associated with network-controlled resource allocation, or a Mode 2 SL-RP-P aggregation capability associated with UE-autonomous resource allocation, a joint Mode SL-RP-P aggregation capability associated with both network-controlled resource allocation and UE- autonomous resource allocation, or a sidelink carrier aggregation (CA)-dependent SL- RP-P aggregation capability, or a sidelink CA-independent SL-RP-P aggregation capability, or any combination thereof.
  • RRC radio resource control
  • CA sidelink carrier aggregation
  • Clause 75 The UE of any of clauses 73 to 74, wherein the SL-RP-P aggregation capability of the UE comprises: a maximum number of SL-RP-Ps for aggregation, or a maximum number of shared SL-RP-Ps for aggregation, or a maximum number of dedicated SL-RP- Ps for aggregation, or a maximum number of shared and dedicated SL-RP-Ps for hybrid aggregation, or any combination thereof.
  • Clause 76 The UE of any of clauses 73 to 75, wherein the SL-RP-P aggregation capability of the UE comprises: a maximum number of aggregated positioning measurements associated with aggregated dedicated SL-RP-Ps, or a maximum number of aggregated positioning measurements associated with aggregated shared SL-RP-Ps, or a maximum number of aggregated positioning measurements associated with hybrid aggregation of dedicated and shared SL-RP-Ps, or any combination thereof.
  • Clause 77 The UE of any of clauses 73 to 76, wherein the SL-RP-P aggregation capability of the UE comprises: a maximum number of aggregated SL-RP-P configurations.
  • Clause 78 The UE of clause 77, wherein the maximum number of aggregated SL-RP-P configurations is one.
  • Clause 79 The UE of any of clauses 77 to 78, wherein the maximum number of aggregated SL-RP-P configurations is more than one, with each aggregated SL-RP-P configuration capable of being associated with a different set of configuration-specific common parameters.
  • Clause 80 The UE of any of clauses 73 to 79, wherein the SL-RP-P aggregation capability of the UE comprises: a maximum number of aggregated SL-RP-P resources that the UE is capable of processing over a time period, or a maximum number of simultaneously active aggregated SL-RP-P resources, or a maximum amount of aggregated bandwidth across aggregated SL-RP-Ps, or any combination thereof.
  • Clause 81 The UE of any of clauses 57 to 80, wherein the SL-PRS is associated with a sidelink time difference of arrival (TDOA)-based position-estimation session, a sidelink time of arrival (TOA)-based estimation session, a sidelink multi-round trip time (RTT)- based position estimation session, a sidelink angle of arrival (AOA)-based position estimation session, or an angle of departure (AOD)-based position estimation session.
  • TDOA sidelink time difference of arrival
  • TOA sidelink time of arrival
  • RTT sidelink multi-round trip time
  • AOA sidelink angle of arrival
  • AOD angle of departure
  • a position estimation entity comprising: means for determining a first resource configuration associated with a first sidelink resource pool for positioning (SL- RP-P); means for determining a second resource configuration associated with a second SL-RP-P; means for determining to aggregate the first SL-RP-P and the second SL-RP-P in a set of aggregated SL-RP-Ps associated with an aggregated SL-RP-P configuration with one or more common parameters; and means for transmitting an indication of the aggregated SL-RP-P configuration to at least one user equipment (UE).
  • UE user equipment
  • Clause 84 The position estimation entity of any of clauses 82 to 83, wherein the one or more common parameters comprise: a set of slots comprising the set of aggregated SL- RP-Ps, or a set of symbols comprising the set of aggregated SL-RP-Ps, or a UE antenna reference point (ARP), or a radio frequency (RF) chain or antenna, or quasi-location (QCL) information, or a number of symbols per slot, or a starting symbol location per slot, or a repetition factor, or a symbol length, or cyclic prefix (CP) length, or subcarrier spacing (SCS), or bandwidth, or comb-pattern, or power per sub-carrier, or numerology grid, or per-symbol comb-pattern spacing uniformity, or phase continuity between the set of aggregated SL-RP-Ps, or a physical sidelink feedback channel (PSFCH) resource configuration, or a number of physical sidelink control channels (PSCCH), or an automatic gain control (AGC
  • a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a user equipment (UE), cause the UE to: determine a first resource configuration associated with a first sidelink resource pool for positioning (SL-RP-P); determine a second resource configuration associated with a second SL-RP- P, wherein the first SL-RP-P and the second SL-RP-P belong to a set of aggregated SL- RP-Ps associated with an aggregated SL-RP-P configuration with one or more common parameters; and communicate SL-PRS via the set of aggregated SL-RP-Ps based on the aggregated SL-RP-P configuration.
  • SL-RP-P sidelink resource pool for positioning
  • Clause 86 The non-transitory computer-readable medium of clause 85, wherein the communication of the SL-PRS comprises transmitting the SL-PRS, or wherein the communication of the SL-PRS comprises receiving and measuring the SL-PRS.
  • Clause 87 The non-transitory computer-readable medium of any of clauses 85 to 86, wherein the set of aggregated SL-RP-Ps comprises at least one dedicated SL-RP-P, at least one shared SL-RP-P, or a combination thereof.
  • Clause 88 The non-transitory computer-readable medium of any of clauses 85 to 87, wherein the first SL-RP-P is associated with a first component carrier (CC) and the second SL-RP-P is associated with a second CC.
  • CC component carrier
  • Clause 89 The non-transitory computer-readable medium of clause 88, wherein the first SL-RP-P and the second SL-RP-P are separated by one or more guard bands in a frequency-domain.
  • Clause 90 The non-transitory computer-readable medium of clause 89, wherein the one or more guard bands are configured so that a propagation of a comb-pattern of the SL- PRS in uniform across the first SL-RP-P, the second SL-RP-P and the one or more guard bands.
  • Clause 91 The non-transitory computer-readable medium of any of clauses 85 to 90, wherein the one or more common parameters comprise: a set of slots comprising the set of aggregated SL-RP-Ps, or a set of symbols comprising the set of aggregated SL-RP-Ps, or a UE antenna reference point (ARP), or a radio frequency (RF) chain or antenna, or quasi -location (QCL) information, or a number of symbols per slot, or a starting symbol location per slot, or a repetition factor, or a symbol length, or cyclic prefix (CP) length, or subcarrier spacing (SCS), or bandwidth, or comb-pattern, or power per sub-carrier, or numerology grid, or per-symbol comb-pattern spacing uniformity, or phase continuity between the set of aggregated SL-RP-Ps, or a physical sidelink feedback channel (PSFCH) resource configuration, or a number of physical sidelink control channels (PSCCH), or an automatic gain
  • Clause 93 The non-transitory computer-readable medium of any of clauses 85 to 92, wherein the aggregated SL-RP-P configuration is determined independently at the UE and indicated to one or more other UEs via sidelink control information (SCI).
  • SCI sidelink control information
  • Clause 94 The non-transitory computer-readable medium of any of clauses 85 to 93, wherein the aggregated SL-RP-P configuration is indicated to the UE by a network component or by another UE via sidelink control information (SCI).
  • SCI sidelink control information
  • Clause 95 The non-transitory computer-readable medium of any of clauses 85 to 94, wherein the one or more common parameters are indicated in each of the first resource configuration and the second resource configuration, or wherein the one or more common parameters are indicated only one of the first resource configuration and the second resource configuration, and the one or more common parameters are applied to the other resource configuration based on the first SL-RP-P and the second SL-RP-P belonging to the set of aggregated SL-RP-Ps.
  • Clause 96 The non-transitory computer-readable medium of any of clauses 85 to 95, wherein the set of aggregated SL-RP-Ps is associated with a maximum total transmission power for the SL-PRS across all SL-RP-Ps in the set of aggregated SL-RP-Ps.
  • Clause 97 The non-transitory computer-readable medium of clause 96, wherein the maximum total transmission power for the SL-PRS across all SL-RP-Ps in the set of aggregated SL-RP-Ps is based on a sidelink Synchronization Signal Block (SL-SSB) priority parameter.
  • SL-SSB sidelink Synchronization Signal Block
  • Clause 98 The non-transitory computer-readable medium of clause 97, wherein the SL- SSB priority parameter designates a first subset of resources in the set of aggregated SL- RP-Ps that may be dropped to satisfy the maximum total transmission power, or wherein the SL-SSB priority parameter designates a second subset of resources in the set of aggregated SL-RP-Ps that may not be dropped to satisfy the maximum total transmission power, or a combination thereof.
  • Clause 99 The non-transitory computer-readable medium of any of clauses 85 to 98, wherein the set of aggregated SL-RP-Ps is further associated with a resource collision parameter.
  • Clause 100 The non-transitory computer-readable medium of any of clauses 97 to 99, wherein the resource collision parameter designates a first subset of resources in the set of aggregated SL-RP-Ps that may be dropped in response to collision with another function, or wherein the resource collision parameter designates a second subset of resources in the set of aggregated SL-RP-Ps that may not be dropped in response to collision with the another function, or a combination thereof.
  • Clause 101 The non-transitory computer-readable medium of any of clauses 85 to 100, further comprising computer-executable instructions that, when executed by the UE, cause the UE to: transmit a SL-RP-P aggregation capability of the UE, wherein the set of aggregated SL-RP-Ps is based on the SL-RP-P aggregation capability of the UE.
  • the SL-RP-P aggregation capability of the UE comprises: a radio resource control (RRC) CONNECTED SL-RP-P aggregation capability, or a RRC IDLE SL-RP-P aggregation capability, or a RRC INACTIVE SL-RP-P aggregation capability, or a Mode 1 SL-RP-P aggregation capability associated with network-controlled resource allocation, or a Mode 2 SL-RP-P aggregation capability associated with UE-autonomous resource allocation, a joint Mode SL-RP-P aggregation capability associated with both network- controlled resource allocation and UE-autonomous resource allocation, or a sidelink carrier aggregation (CA)-dependent SL-RP-P aggregation capability, or a sidelink CA- independent SL-RP-P aggregation capability, or any combination thereof.
  • RRC radio resource control
  • CA sidelink carrier aggregation
  • Clause 103 The non-transitory computer-readable medium of any of clauses 101 to 102, wherein the SL-RP-P aggregation capability of the UE comprises: a maximum number of SL-RP-Ps for aggregation, or a maximum number of shared SL-RP-Ps for aggregation, or a maximum number of dedicated SL-RP-Ps for aggregation, or a maximum number of shared and dedicated SL-RP-Ps for hybrid aggregation, or any combination thereof.
  • Clause 104 The non-transitory computer-readable medium of any of clauses 101 to 103, wherein the SL-RP-P aggregation capability of the UE comprises: a maximum number of aggregated positioning measurements associated with aggregated dedicated SL-RP-Ps, or a maximum number of aggregated positioning measurements associated with aggregated shared SL-RP-Ps, or a maximum number of aggregated positioning measurements associated with hybrid aggregation of dedicated and shared SL-RP-Ps, or any combination thereof.
  • Clause 105 The non-transitory computer-readable medium of any of clauses 101 to 104, wherein the SL-RP-P aggregation capability of the UE comprises: a maximum number of aggregated SL-RP-P configurations.
  • Clause 106 The non-transitory computer-readable medium of clause 105, wherein the maximum number of aggregated SL-RP-P configurations is one.
  • Clause 107 The non-transitory computer-readable medium of any of clauses 105 to 106, wherein the maximum number of aggregated SL-RP-P configurations is more than one, with each aggregated SL-RP-P configuration capable of being associated with a different set of configuration-specific common parameters.
  • Clause 108 The non-transitory computer-readable medium of any of clauses 101 to 107, wherein the SL-RP-P aggregation capability of the UE comprises: a maximum number of aggregated SL-RP-P resources that the UE is capable of processing over a time period, or a maximum number of simultaneously active aggregated SL-RP-P resources, or a maximum amount of aggregated bandwidth across aggregated SL-RP-Ps, or any combination thereof.
  • Clause 109 The non-transitory computer-readable medium of any of clauses 85 to 108, wherein the SL-PRS is associated with a sidelink time difference of arrival (TDOA)- based position-estimation session, a sidelink time of arrival (TOA)-based estimation session, a sidelink multi-round trip time (RTT)-based position estimation session, a sidelink angle of arrival (AOA)-based position estimation session, or an angle of departure (AOD)-based position estimation session.
  • TDOA sidelink time difference of arrival
  • TOA sidelink time of arrival
  • RTT sidelink multi-round trip time
  • AOA sidelink angle of arrival
  • AOD angle of departure
  • a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a position estimation entity, cause the position estimation entity to: determine a first resource configuration associated with a first sidelink resource pool for positioning (SL-RP-P); determine a second resource configuration associated with a second SL-RP-P; determine to aggregate the first SL-RP- P and the second SL-RP-P in a set of aggregated SL-RP-Ps associated with an aggregated SL-RP-P configuration with one or more common parameters; and transmit an indication of the aggregated SL-RP-P configuration to at least one user equipment (UE).
  • UE user equipment
  • the one or more common parameters comprise: a set of slots comprising the set of aggregated SL-RP-Ps, or a set of symbols comprising the set of aggregated SL-RP-Ps, or a UE antenna reference point (ARP), or a radio frequency (RF) chain or antenna, or quasi -location (QCL) information, or a number of symbols per slot, or a starting symbol location per slot, or a repetition factor, or a symbol length, or cyclic prefix (CP) length, or subcarrier spacing (SCS), or bandwidth, or comb-pattern, or power per sub-carrier, or numerology grid, or per-symbol comb-pattern spacing uniformity, or phase continuity between the set of aggregated SL-RP-Ps, or a physical sidelink feedback channel (PSFCH) resource configuration, or a number of physical sidelink control channels (PSCCH), or an automatic gain control (AGC) configuration, or
  • PSFCH physical sidelink feedback channel
  • PSCCH physical sidelink control channels
  • DSP digital signal processor
  • ASIC application-specific integrated circuit
  • FPGA field-programable gate array
  • a general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine.
  • a processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
  • a software module may reside in random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
  • An example storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium.
  • the storage medium may be integral to the processor.
  • the processor and the storage medium may reside in an ASIC.
  • the ASIC may reside in a user terminal (e.g., UE).
  • the processor and the storage medium may reside as discrete components in a user terminal.
  • the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium.
  • Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a storage media may be any available media that can be accessed by a computer.
  • such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.
  • any connection is properly termed a computer-readable medium.
  • the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave
  • the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium.
  • Disk and disc includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.
  • the terms “has,” “have,” “having,” “comprises,” “comprising,” “includes,” “including,” and the like does not preclude the presence of one or more additional elements (e.g., an element “having” A may also have B).
  • the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise.
  • the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and/or,” unless explicitly stated otherwise (e.g., if used in combination with “either” or “only one of’) or the alternatives are mutually exclusive (e.g., “one or more” should not be interpreted as “one and more”).

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Des aspects de la divulgation concernent l'agrégation de groupes de ressources de liaison latérale pour le positionnement (SL-RP-P) par l'intermédiaire d'une configuration SL-RP-P agrégée avec un ou plusieurs paramètres communs. Dans certaines conceptions, l'agrégation de SL-RP-P peut faciliter divers avantages techniques, tels qu'une précision d'estimation de position basée sur SL-PRS améliorée, une latence d'estimation de position basée sur un signal de référence de positionnement (PRS) SL réduit, et ainsi de suite, en considérant conjointement divers paramètres (par exemple, une attribution de ressources, des motifs de peigne ou des tailles de peigne, etc.) dans les SL-RP-P agrégés.
PCT/US2024/050919 2023-12-01 2024-10-11 Agrégation de groupes de ressources de liaison latérale pour positionnement Pending WO2025117049A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
GR20230100999 2023-12-01
GR20230100999 2023-12-01

Publications (1)

Publication Number Publication Date
WO2025117049A1 true WO2025117049A1 (fr) 2025-06-05

Family

ID=93291927

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2024/050919 Pending WO2025117049A1 (fr) 2023-12-01 2024-10-11 Agrégation de groupes de ressources de liaison latérale pour positionnement

Country Status (1)

Country Link
WO (1) WO2025117049A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220191830A1 (en) * 2019-04-01 2022-06-16 Apple Inc. New radio (nr) downlink (dl) positioning reference signal (prs) design resource allocation and mapping in nr positioning
US20230319857A1 (en) * 2022-03-31 2023-10-05 Samsung Electronics Co., Ltd. Method and apparatus for sidelink positioning

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220191830A1 (en) * 2019-04-01 2022-06-16 Apple Inc. New radio (nr) downlink (dl) positioning reference signal (prs) design resource allocation and mapping in nr positioning
US20230319857A1 (en) * 2022-03-31 2023-10-05 Samsung Electronics Co., Ltd. Method and apparatus for sidelink positioning

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
SEUNGMIN LEE ET AL: "FL Summary #1 for AI 9.4.4: Sidelink CA operation", vol. RAN WG1, no. Toulouse, FR; 20230821 - 20230825, 25 August 2023 (2023-08-25), XP052448838, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/TSG_RAN/WG1_RL1/TSGR1_114/Docs/R1-2307978.zip R1-2307978 FL Summary #1 for AI 9.4.4 v100_FL.docx> [retrieved on 20230825] *

Similar Documents

Publication Publication Date Title
EP4315722A1 (fr) Fenêtre de traitement de signal de référence de positionnement (prs) pour rapport de mesure de positionnement à faible latence
US20250039024A1 (en) Sounding reference signal (srs) cyclic shift hopping
EP4454191A1 (fr) Rapport d&#39;occupation de canal (cbr) pour des groupes de ressources de positionnement de liaison latérale
WO2025014583A1 (fr) Données d&#39;assistance pour procédure d&#39;estimation de position basée sur une liaison latérale sans session
US20230284151A1 (en) Power control at user equipment based on pathloss reference signal
US20240340140A1 (en) Comb offset indication for sidelink positioning reference signal
US20240340139A1 (en) Comb patterns for sidelink positioning reference signal
US12153152B2 (en) User equipment (UE) handling of delayed sounding reference signal (SRS) configuration for downlink-and-uplink-based positioning methods
US20250330939A1 (en) Status change notifications for positioning
US20250185033A1 (en) Transmission structure for sidelink positioning reference signals
WO2024065610A1 (fr) Rapport de capacité d&#39;indice de sous-bande d&#39;informations csi
WO2025117049A1 (fr) Agrégation de groupes de ressources de liaison latérale pour positionnement
WO2025117095A1 (fr) Agrégation de groupes de ressources de liaison latérale pour positionnement
WO2025117254A1 (fr) Communication inter-couche de ressources candidates à partir de groupes de ressources de liaison latérale agrégés pour la transmission d&#39;une liaison latérale signal de référence de positionnement
WO2025071763A1 (fr) Indicateurs d&#39;intensité de signal reçus associés à des signaux de référence de positionnement de liaison latérale multiplexés
WO2024211352A1 (fr) Tracés en peigne pour signal de référence de positionnement de liaison latérale
WO2025122337A1 (fr) Détection de sauts de fréquence pour un groupe de ressources de liaison latérale pour le positionnement
WO2024211355A1 (fr) Indication de décalage de peigne pour signal de référence de positionnement de liaison latérale
WO2025136667A1 (fr) Rapport de mesure associé à des groupes de ressources de liaison latérale agrégés pour positionnement
WO2025122360A1 (fr) Attribution de ressources de signal de référence de positionnement de liaison latérale pour groupes de ressources de liaison latérale agrégés
WO2025147310A1 (fr) Saut de fréquence associé à des couches de fréquence de positionnement agrégées
WO2025075738A1 (fr) Configuration d&#39;exclusion de ressources pour groupe de ressources de liaison latérale
WO2025174565A1 (fr) Communication inter-couche de ressources candidates à partir d&#39;un groupe de ressources de liaison latérale pour la transmission d&#39;un signal de référence de positionnement de liaison latérale
WO2025029344A1 (fr) Mappage de points de référence d&#39;antenne sur des signaux de référence de positionnement de liaison latérale
WO2025034530A1 (fr) Mode de rétroaction pour signal de référence de positionnement de liaison latérale

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24799035

Country of ref document: EP

Kind code of ref document: A1