Signaling for sidelink positioning

Abstract

An apparatus, a method, and a computer program product for providing sidelink UE information are provided. An example method may include receiving at least one system information block (SIB) from a network entity, the at least one SIB including a sidelink data configuration associated with a data transmission and a sidelink positioning configuration associated with a positioning session. The example method may also include transmitting sidelink UE information to the network entity, the sidelink UE information including an indication of at least one of a failure associated with the sidelink positioning configuration, a request for transmit (Tx) sidelink resources for the positioning session, or a list of receive (Rx) sidelink resources for the positioning session.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of Greek patent application serial number 20220100613, entitled “SIGNALING FOR SIDELINK POSITIONING” and filed on July 28, 2022, which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates generally to communication systems, and more particularly to wireless communication systems with sidelink positioning. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5GNR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Certain aspects of 5G NR may be based on 4G Long Term Evolution (LTE) standards. It is necessary to further improve 5G NR technology. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0006] A simplified summary of one or more aspects is presented below to provide a basic understanding of these aspects. This summary is not an extensive review of all contemplated aspects. This summary neither identifies the key or important elements of all aspects, nor describes the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description presented later.

[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus at a user equipment (UE) are provided. The apparatus may include a memory and at least one processor coupled to the memory. The memory and the at least one processor coupled to the memory may be configured to receive at least one system information block (SIB) from a network entity, the at least one SIB including a sidelink data configuration associated with data transmission and a sidelink positioning configuration associated with a positioning session. The memory and the at least one processor coupled to the memory may also be configured to send sidelink UE information to the network entity, the sidelink UE information including an indication of at least one of: a failure associated with the sidelink positioning configuration, a request for a transmit (Tx) sidelink resource for the positioning session, or a list of receive (Rx) sidelink resources for the positioning session.

[0008] In another aspect of the present disclosure, a method, a computer-readable medium, and an apparatus at a network entity are provided. The apparatus may include a memory and at least one processor coupled to the memory. The memory and the at least one processor coupled to the memory may be configured to send at least one system information block (SIB) to a user equipment (UE), the at least one SIB including a sidelink data configuration associated with data transmission and a sidelink positioning configuration associated with a positioning session. The memory and the at least one processor coupled to the memory may also be configured to receive sidelink UE information from the UE, the sidelink UE information including an indication of at least one of: a failure associated with the sidelink positioning configuration, a request for a transmit (Tx) sidelink resource for the positioning session, or a list of receive (Rx) sidelink resources for the positioning session.

[0009] To achieve the aforementioned and related purposes, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail some exemplary features of one or more aspects. However, these features indicate only some of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.

[0011] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0012] Figure 2B is a diagram illustrating an example of DL channels within a subframe according to various aspects of the present disclosure.

[0013] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0014] Figure 2D is a diagram illustrating an example of UL channels within a subframe according to various aspects of the present disclosure.

[0015] Figure 3 is a diagram illustrating an example of a base station and a user equipment (UE) in an access network.

[0016] Figure 4 is a diagram illustrating an example of UE positioning based on reference signal measurement.

[0017] Figure 5A is a diagram illustrating an example of positioning.

[0018] Figure 5B is a diagram illustrating an example of positioning.

[0019] Figure 5C is a diagram illustrating an example of positioning.

[0020] Fig. 6A is a diagram illustrating an example of a positioning peer selection procedure for SL collaborative positioning.

[0021] Figure 6B is a diagram illustrating an example of a positioning peer selection procedure for SL collaborative positioning.

[0022] Figure 7 is a diagram illustrating an example of a sidelink positioning reference signal (PRS) configuration and a resource pool (RP) for positioning (RP-P) configuration.

[0023] Fig. 8A is a diagram illustrating example communications between network entities and a UE.

[0024] Figure 8B is a diagram illustrating example communications between network entities and a UE.

[0025] Fig. 9 is a flow chart of a method of wireless communication.

[0026] Fig.10 is a flow chart of a method of wireless communication.

[0027] Fig.11 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities.

[0028] Fig.12 is a diagram illustrating an example of a hardware implementation for an example network entity. DETAILED DESCRIPTION

[0029] The specific embodiments described below in conjunction with the accompanying drawings are descriptions of various configurations and do not represent the only configurations in which the concepts described herein can be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, these concepts can be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0030] Several aspects of telecommunication systems are presented with reference to various apparatuses and methods. These apparatuses and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0031] As an example, an element, or any part of an element, or any combination of elements can be implemented as a "processing system", which includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic components, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout the present disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.

[0032] Thus, in one or more example aspects, specific implementations and / or use cases, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality may be stored or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. Storage media may be any available media that can be accessed by a computer. As an example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0033] Although various aspects, specific implementations and / or use cases are described in this application by the illustration of some examples, additional or different aspects, specific implementations and / or use cases may be generated in many different arrangements and scenarios. The various aspects, specific implementations and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, various aspects, specific implementations and / or use cases can be generated via integrated chip specific implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, artificial intelligence (AI) enabled devices, etc.). Although some examples may or may not be specifically for use cases or applications, the described examples may have a wide range of applicability. Various aspects, specific implementations and / or use cases may be in the range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the range of aggregated, distributed or original equipment manufacturer (OEM) devices or systems in conjunction with one or more technologies herein. In some actual settings, the equipment combined with the various aspects and features described may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.) The techniques described herein can be practiced in a wide variety of devices of various sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc.

[0034] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or a network equipment (such as a base station (BS), or one or more units (or one or more components) that perform base station functionality can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0035] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0036] Base station operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be utilized in an integrated access and backhaul (IAB) network, an open radio access network (O-RAN (network configuration such as that initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0037] Figure 1 1 is a diagram 100 illustrating an example of a wireless communication system and an access network. The illustrated wireless communication system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110 that may communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more disaggregated base station units, such as a near real-time (near RT) RAN intelligent controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a service management and orchestration (SMO) framework 105, or both. The CU 110 may communicate with one or more DUs 130 via corresponding midhaul links, such as an F1 interface. The DU 130 may communicate with one or more RUs 140 via corresponding fronthaul links. The RU 140 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

[0038] Each of the units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO framework 105) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interfaces of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive signals or send signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive and / or send signals to one or more of the other units via a wireless transmission medium.

[0039] In some aspects, CU 110 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 110. CU 110 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 110 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 110 may be implemented to communicate with DU 130 for network control and signaling.

[0040] DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 140. In some aspects, DU 130 may host one or more of the following depending on a functional split (such as that defined by 3GPP): a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.). In some aspects, DU 130 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

[0041] The lower layer functionality may be implemented by one or more RUs 140. In some deployments, the RU 140 controlled by the DU 130 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, etc.), or both, based on functional splitting such as lower layer functional splitting. In such an architecture, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some specific implementations, real-time and non-real-time aspects of control and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may enable the DU 130 and the CU 110 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0042] The SMO framework 105 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 105 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 190) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 110, DU 130, RU 140, and near-RT RIC 125. In some specific implementations, the SMO framework 105 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 111) via the O1 interface. Additionally, in some specific implementations, the SMO framework 105 may communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105 .

[0043] The non-RT RIC 115 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / machine learning (ML) (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 125. The non-RT RIC 115 may be coupled to or in communication with the near-RT RIC 125 (such as via an A1 interface). The near-RT RIC 125 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 110, one or more DUs 130, or both, and O-eNBs with the near-RT RIC 125.

[0044] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 125, the non-RT RIC 115 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 125 and may be received from a non-network data source or from a network function at the SMO framework 105 or the non-RT RIC 115. In some examples, the non-RT RIC 115 or the near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 may monitor long-term trends and patterns for performance and employ AI / ML models to perform corrective actions through the SMO framework 105 (such as via reconfiguration of O1) or via creation of RAN management policies (such as A1 policies).

[0045] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Therefore, the base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component is indicated by a dotted line to indicate that each component may be included in the base station 102 or may not be included in the base station). The base station 102 provides an access point to the core network 120 for the UE 104. The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). Small cells include femto cells, pico cells, and micro cells. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to RU 140 and / or downlink (DL) (also known as forward link) transmission from RU 140 to UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link may be through one or more carriers. For each carrier allocated in a carrier aggregation of up to Yx MHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use a spectrum of up to Y MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.) bandwidth. These carriers may or may not be adjacent to each other. The allocation of carriers may be equivalent to DL and UL asymmetric (e.g., more or fewer carriers may be allocated to DL than to UL). Component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0046] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL wireless wide area network (WWAN) spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). The D2D communication may be through a variety of wireless D2D communication systems, such as, for example, Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0047] The wireless communication system may also include a Wi-Fi AP 150 that communicates with a UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, for example, in a 5 GHz unlicensed spectrum, etc. When communicating in an unlicensed spectrum, the UE 104 / AP 150 may perform a clear channel assessment (CCA) to determine whether a channel is available prior to communication.

[0048] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0049] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz-24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6GHz-71GHz), FR4 (71GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0050] In view of the above, unless otherwise specified, if the term "6 GHz or less" is used herein, it may broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specified, if the term "millimeter wave" is used herein, it may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and / or FR5, or may be within the EHF band.

[0051] The base station 102 and the UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. The base station 102 may send a beamformed signal 182 to the UE 104 in one or more transmit directions. The UE 104 may receive the beamformed signal from the base station 102 in one or more receive directions. The UE 104 may also send a beamformed signal 184 to the base station 102 in one or more transmit directions. The base station 102 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 102 / UE 104 may perform beam training to determine the optimal receive direction and transmit direction for each of the base station 102 / UE 104. The transmit direction and receive direction of the base station 102 may be the same or may not be the same. The transmit direction and receive direction of the UE 104 may be the same or may not be the same.

[0052] The base station 102 may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a transceiver base station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a TRP, a network node, a network entity, a network equipment, or some other suitable term. The base station 102 may be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, an aggregated (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and a RU, or as a disaggregated base station including one or more of a CU, a DU, and / or a RU.

[0053] The core network 120 may include an access and mobility management function (AMF) 161, a session management function (SMF) 162, a user plane function (UPF) 163, a unified data management (UDM) 164, one or more location servers 168, and other functional entities. AMF 161 is a control node that handles signaling between UE 104 and the core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identity handling, access authorization, and subscription management. One or more location servers 168 are illustrated as including a gateway mobile location center (GMLC) 165 and a location management function (LMF) 166. However, in general, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the following: GMLC 165, LMF 166, position determination entity (PDE), serving mobile location center (SMLC), mobile positioning center (MPC), etc. GMLC 165 and LMF 166 support UE location services. GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. LMF 166 receives measurement and assistance information from NG-RAN and UE 104 via AMF 161 to calculate the location of UE 104. NG-RAN may determine the location of UE 104 using one or more positioning methods. Positioning UE 104 may involve signal measurements, position estimation, and optional speed calculation based on these measurements. Signal measurements may be performed by UE 104 and / or serving base station 102. The measured signal may be based on one or more of the following: a satellite positioning system (SPS) 170 (e.g., one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / location systems), an LTE signal, a wireless local area network (WLAN) signal, a Bluetooth signal, a terrestrial beacon system (TBS), sensor-based information (e.g., an atmospheric pressure sensor, a motion sensor), an NR enhanced cell ID (NR E-CID) method, an NR signal (e.g., multi-round trip time (multi-RTT), DL angle of departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning) and / or other systems / signals / sensors.

[0054] Examples of UE 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare equipment, implants, sensors / actuators, displays, or any other similarly functional devices. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as stations, mobile stations, subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, user agents, mobile clients, clients, or some other suitable terms. In some scenarios, the term UE may also be applied to one or more supporting devices, such as in a device constellation arrangement. One or more of these devices may access the network collectively and / or individually.

[0055] Reference again Figure 1 , in some aspects, the UE 104 may include a SL component 198. In some aspects, the SL component 198 may be configured to receive at least one system information block (SIB) from a network entity, the at least one SIB including a sidelink data configuration associated with a data transmission and a sidelink positioning configuration associated with a positioning session. In some aspects, the SL component 198 may also be configured to send sidelink UE information to the network entity, the sidelink UE information including at least one of an indication of a failure associated with the sidelink positioning configuration, a request for a transmit (Tx) sidelink resource for the positioning session, or a list of receive (Rx) sidelink resources for the positioning session.

[0056] In certain aspects, the base station 102 may include a SL component 199. In some aspects, the SL component 199 may be configured to send at least one system information block (SIB) to a user equipment (UE), the at least one SIB including a sidelink data configuration associated with a data transmission and a sidelink positioning configuration associated with a positioning session. In some aspects, the SL component 199 may also be configured to receive sidelink UE information from the UE, the sidelink UE information including an indication of at least one of: a failure associated with the sidelink positioning configuration, a request for a transmit (Tx) sidelink resource for the positioning session, or a list of receive (Rx) sidelink resources for the positioning session.

[0057] Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0058] As described herein, a node (which may be referred to as a node, a network node, a network entity, or a wireless node) may include, may be, or may be included in (e.g., as a component of) a base station (e.g., any base station described herein), a UE (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, an integrated access and backhaul (IAB) node, a distributed unit (DU), a central unit (CU), a remote / radio unit (RU) (which may also be referred to as a remote radio unit (RRU)), and / or another processing entity configured to perform any of the techniques described herein. For example, the network node may be a UE. For another example, the network node may be a base station or a network entity. For another example, a first network node may be configured to communicate with a second network node or a third network node. In one aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a UE. In another aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a base station. In yet other aspects of this example, the first network node, the second network node, and the third network node may be different relative to these examples. Similarly, references to UE, base station, device, equipment, computing system, etc. may include disclosure of UE, base station, device, equipment, computing system, etc. as a network node. For example, a disclosure that a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with the present disclosure, once a specific example is expanded according to the present disclosure (e.g., a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node), a broader example of a narrower example may be interpreted in reverse, but in a broad, open-ended manner. In the above example where a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node, the first network node may refer to a first UE configured to receive information, a first base station, a first device, a first device, a first computing system, a first set of one or more components, a first processing entity, etc.; and the second network node may refer to a second UE, a second base station, a second device, a second device, a second computing system, a second set of one or more components, a second processing entity, etc.

[0059] As described herein, different terms may be used in various aspects to describe the communication of information (e.g., any information, signal, etc.). The disclosure of one communication term includes the disclosure of other communication terms. For example, a first network node may be described as being configured to send information to a second network node. In this example and consistent with the present disclosure, the disclosure that the first network node is configured to send information to the second network node includes the disclosure that the first network node is configured to provide, transmit, output, communicate, or send information to the second network node. Similarly, in this example and consistent with the present disclosure, the disclosure that the first network node is configured to send information to the second network node includes the disclosure that the second network node is configured to receive, obtain, or decode information provided, sent, output, transmitted, or sent by the first network node.

[0060] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B FIG230 is a diagram illustrating an example of DL channels within a 5G NR subframe. Figure 2C FIG250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2D FIG280 is a diagram illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL, or may be time division duplex (TDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL. Figure 2A , Figure 2C In the example provided, the 5GNR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe may be configured with any of the various available slot formats 0 to 61. Slot formats 0 and 1 are full DL and full UL, respectively. Other slot formats 2 to 61 include a mix of DL, UL and flexible symbols. The UE is configured with the slot format through the received slot format indicator (SFI) (dynamically configured through DL control information (DCI) or semi-statically / statically configured through radio resource control (RRC) signaling).

[0061] FIG. 2A to FIG. 2DThe frame structure is illustrated, and various aspects of the present disclosure may be applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 subframes of equal size (1ms). Each subframe may include one or more time slots. A subframe may also include a microslot, which may include 7, 4, or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For a normal CP, each time slot may include 14 symbols, and for an extended CP, each time slot may include 12 symbols. The symbol on the DL may be a CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbol. The symbol on the UL may be a CP-OFDM symbol (for high throughput scenarios) or a discrete Fourier transform (DFT) extended OFDM (DFT-s-OFDM) symbol (also known as a single carrier frequency division multiple access (SC-FDMA) symbol) (for power-limited scenarios; limited to single-stream transmission). The number of slots within a subframe is based on the CP and the parameter set. The parameter set defines the subcarrier spacing (SCS) and effectively defines the symbol length / duration, which is equal to 1 / SCS.

[0062]

[0063] For normal CP (14 symbols / slot), different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Thus, for normal CP and parameter set μ, there are 14 symbols / slot and 2 μ timeslots / subframe. The subcarrier spacing can be equal to 2 μ *15kHz, where μ is parameter set 0 to 4. Therefore, the subcarrier spacing for parameter set μ=0 is 15kHz, and the subcarrier spacing for parameter set μ=4 is 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example is provided for a normal CP with 14 symbols per slot and a parameter set μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is about 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency-division multiplexed (see Figure 2B ). Each BWP may have a specific parameter set and CP (normal or extended).

[0064] A resource grid may be used to represent the frame structure. Each slot includes a resource block (RB) (also referred to as a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0065] like Figure 2A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) (indicated as R for a particular configuration, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0066] Figure 2B Examples of various DL channels within a subframe of a frame are illustrated. A physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within a BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during a PDCCH monitoring opportunity on a CORESET, wherein the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identification. A secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not sent via the PBCH (such as a system information block (SIB)), and paging messages.

[0067] like Figure 2CAs illustrated, some of the REs carry DM-RS (indicated as R for a particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may send a DM-RS for a physical uplink control channel (PUCCH) and a DM-RS for a physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first or first two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS may be sent in different configurations. The UE may send a sounding reference signal (SRS). The SRS may be sent in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the teeth of the comb. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0068] Figure 2D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may be used to carry, among other things, buffer status reports (BSRs), power headroom reports (PHRs), and / or UCI.

[0069] Figure 3375. The Controller / Processor 375 is a block diagram of a base station 310 in an access network communicating with a UE 350. In the DL, Internet Protocol (IP) packets may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer packet data units (PDUs), error correction through 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, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0070] The transmit (TX) processor 316 and receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The coded and modulated symbols can then be split into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially pre-coded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation schemes, as well as for spatial processing. Channel estimates may be derived from reference signals and / or channel condition feedback sent by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier with a corresponding spatial stream for transmission.

[0071] At the UE 350, each receiver 354Rx receives a signal through its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for the UE 350. If multiple spatial streams are destined for the UE 350, they can be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then uses a fast Fourier transform (FFT) to convert the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal includes 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 signal constellation point most likely to be sent by the base station 310. These soft decisions can be based on channel estimates calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by the base station 310. The data and control signals are then provided to a controller / processor 359, which implements layer 3 and layer 2 functionality.

[0072] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0073] Similar to the functionality described in conjunction with DL transmissions performed by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0074] Channel estimates derived by the channel estimator 358 based on a reference signal or feedback sent by the base station 310 may be used by the TX processor 368 to select appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

[0075] UL transmissions are processed at the base station 310 in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318Rx receives a signal through its respective antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to the RX processor 370.

[0076] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0077] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to combine Figure 1 The SL component 198 is used to perform various aspects.

[0078] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to combine Figure 1 The SL component 199 is used to perform various aspects.

[0079] As used herein, the term "sidelink data configuration" may refer to a sidelink communication configuration for transmitting data on a sidelink between two UEs. As used herein, the term "sidelink positioning configuration" may refer to a sidelink communication configuration for positioning based on a sidelink between two UEs.

[0080] Figure 4 FIG. 4 is a diagram illustrating an example of UE positioning based on reference signal measurements. UE 404 may be at time T SRS_TX UL-SRS 412 is sent and at time T PRS_RX A DL positioning reference signal (PRS) (DL-PRS) 410 is received. TRP 406 may be at time T SRS_RX Receive UL-SRS 412 and at time T PRS_TX 410. UE 404 may receive DL-PRS 410 before transmitting UL-SRS 412, or may transmit UL-SRS 412 before receiving DL-PRS 410. In both cases, a positioning server (e.g., location server 168) or UE 404 may determine the UL-SRS 412 based on ||T SRS_RX –T PRS_TX |–|T SRS_TX –T PRS_RX || to determine RTT 414. Thus, multi-RTT positioning may utilize UE ERx-Tx time difference measurements (ie, |T SRS_TX –T PRS_RX |) and DL-PRS reference signal received power (RSRP) (DL-PRS-RSRP), and the measured TRP Rx-Tx time difference measurement (ie, |T SRS_RX –T PRS_TX|) and UL-SRS-RSRP. The UE 404 measures the UE Rx-Tx time difference measurement (and optionally the DL-PRS-RSRP of the received signal) using the assistance data received from the positioning server, and the TRP 402, 406 measures the gNB Rx-Tx time difference measurement (and optionally the UL-SRS-RSRP of the received signal) using the assistance data received from the positioning server. These measurements may be used at the positioning server or the UE 404 to determine the RTT, which is used to estimate the position of the UE 404. Other methods for determining the RTT are possible, such as, for example, using DL-TDOA and / or UL-TDOA measurements.

[0081] DL-AoD positioning may utilize the measured DL-PRS-RSRP of downlink signals received from multiple TRPs 402, 406 at the UE 404. The UE 404 measures the DL-PRS-RSRP of the received signals using assistance data received from a positioning server, and the resulting measurements, along with the departure azimuth angle (A-AoD), departure zenith angle (Z-AoD), and other configuration information, are used to position the UE 404 relative to neighboring TRPs 402, 406.

[0082] DL-TDOA positioning may utilize DL Reference Signal Time Difference (RSTD) (and optionally DL-PRS-RSRP) of downlink signals received from multiple TRPs 402, 406 at the UE 404. The UE 404 measures the DL RSTD (and optionally DL-PRS-RSRP) of the received signals using assistance data received from a positioning server, and the resulting measurements are used along with other configuration information to position the UE 404 relative to neighboring TRPs 402, 406.

[0083] UL-TDOA positioning may utilize the UL relative time of arrival (RTOA) (and optionally UL-SRS-RSRP) of uplink signals sent from the UE 404 at multiple TRPs 402, 406. The TRPs 402, 406 measure the UL-RTOA (and optionally UL-SRS-RSRP) of the received signals using assistance data received from a positioning server, and the resulting measurements are used along with other configuration information to estimate the position of the UE 404.

[0084] UL-AoA positioning may utilize the measured azimuth angle of arrival (A-AoA) and zenith angle of arrival (Z-AoA) of uplink signals sent from the UE 404 at multiple TRPs 402, 406. The TRPs 402, 406 measure the A-AoA and Z-AoA of the received signals using assistance data received from a positioning server, and the resulting measurements are used along with other configuration information to estimate the position of the UE 404.

[0085] Additional positioning methods may be used to estimate the position of the UE 404, such as, for example, UE-side UL-AoD and / or DL-AoA. Note that data / measurements from various techniques may be combined in various ways to increase accuracy, determine and / or enhance certainty, supplement / complete measurements, and / or replace / provide missing information.

[0086] Positioning may be based on a side link between UEs, an access link between a network entity and the UEs, or jointly based on the access link and the side link. Figure 5A FIG. 5 is a diagram illustrating an example of positioning. Figure 5A , for positioning related to wireless device 506, first network entity 504A, second network entity 504B, and third network entity 504C may be involved, and each of these network entities may be associated with a respective RTT or TDOA that may be measured. To further improve the accuracy of the location related to wireless device 506, UE 502 (which may be associated with a location known to the network) may be used as an additional anchor point for positioning of wireless device 506. Sidelink RTT between UE 502 and wireless device 506 may be measured. In diagram 500, sidelink positioning and access link positioning may be used jointly.

[0087] Figure 5B FIG550 is a diagram illustrating an example of positioning. Figure 5B , for positioning related to wireless device 556, a first UE 552A, a second UE 552B, and a third UE 552C may be involved, and each of these UEs may be associated with a respective RTT that may be measured. In diagram 550, sidelink positioning may be used. Each of the first UE 552A, the second UE 552B, and the third UE 552C may communicate with a network entity 554.

[0088] Figure 5C FIG. 570 is a diagram illustrating an example of positioning. Figure 5C, for positioning of UE 572, network entity 574 may send PRS to UE 572. If PRS cannot be sent directly from network entity 574 to UE 572 (e.g., when UE 572 is out of coverage), network entity 574 may send PRS to wireless device 576, and wireless device 576 may relay PRS to UE 572.

[0089] Sidelink communication may include direct wireless communication between a first device (e.g., a first UE or other sidelink device) and a second device (e.g., a second UE or other sidelink device), for example, without routing by a base station. In a first mode, the UE may receive resource allocations for sidelink communication from a base station. Sidelink resource allocations from a base station may be referred to as "resource allocation mode 1" or a "centralized" resource allocation mode, for example, where a network entity allocates sidelink resources to multiple sidelink devices. Before exchanging communications, the sidelink devices may perform a discovery procedure to discover each other. In some wireless communication systems (such as for communication systems that support mode 2 resource allocation), the discovery procedure may include a first UE (which may be referred to as a declaring UE) that broadcasts a declaration message received by a second UE (which may be referred to as a monitoring UE). The discovery procedure in which the declaring UE broadcasts a declaration message to one or more monitoring UEs may be referred to as mode A sidelink discovery. In another type of discovery procedure, a first UE (which may be referred to as a discoverer UE) transmits a request message including a discovery request, and a second UE (which may be referred to as a discovered UE) may receive the request and transmit a response message. A discovery procedure in which a discovering UE sends a request message including a discovery request to one or more discovered UEs may be referred to as Mode-B sidelink discovery.

[0090] To discover a positioning peer (which may be a peer SL UE for performing positioning), in mode A, the positioning peer UE may announce its presence by sending a sidelink positioning (SL-pos) discovery message with a positioning flag. In mode B, a target UE wishing to discover a positioning peer UE may initiate with a SL-pos request message with a field related to positioning. Fig. 6A 600 is a diagram illustrating an example of a positioning peer selection procedure for SL collaborative positioning in Mode A. Fig. 6A, the positioning peer UE 604 may send a positioning peer discovery message A 606 to the target UE 602. After receiving the positioning peer discovery message A 606, the target UE 602 may send a positioning peer discovery response A 608 to the positioning peer UE 604. The positioning peer UE 604 may also send a positioning peer discovery message B 610 to the target UE 602. After receiving the positioning peer discovery message B 610, the target UE 602 may send a positioning peer discovery response B 612 to the positioning peer UE 604 to complete the discovery process, and sidelink positioning may be performed between the target UE 602 and the positioning peer UE 604.

[0091] Figure 6B 650 is a diagram illustrating an example of a positioning peer selection procedure for SL collaborative positioning in Mode B. Figure 6B , the target UE 652 may send a positioning peer request message A 656 to the positioning peer UE 654. After receiving the positioning peer request message A 656, the positioning peer UE 654 may send a positioning peer request response message A 658 to the target UE 652. The target UE 652 may also send a positioning peer request message B 660 to the positioning peer UE 654. After receiving the positioning peer request message B 660, the positioning peer UE 654 may send a positioning peer request response message B 662 to the target UE 652 to complete the discovery process, and sidelink positioning may be performed between the target UE 652 and the positioning peer UE 654.

[0092] Both the sidelink location discovery message and the request message may be split into 2 parts to achieve a more power efficient approach and handshake between the target UE and potential positioning peer UEs. The target UE may rank potential positioning peer UEs based on one or more of the following: anchor point location quality criteria, channel quality criteria, response time criteria, or mobility state criteria.

[0093] Figure 7 700 is a diagram illustrating an example of a sidelink positioning reference signal (PRS) configuration and a resource pool (RP) for positioning (RP-P) configuration. Figure 7As illustrated, in some wireless communication systems, a sidelink communication configuration (such as a sidelink positioning configuration, a sidelink data configuration, or a configuration used jointly for data and positioning) may include a SL frequency configuration, and may be associated with point A (which may be a common reference point of a resource block grid, and may be represented by a frequency offset between point A and the lowest subcarrier of the lowest resource block of the SS / PBCH block used by the UE for initial cell selection, or an absolute frequency), a SL bandwidth part (BWP) configuration, a PSBCH configuration, a resource pool for positioning, an SCS, a BW, a location, etc., or an SCS carrier list. The SCS carrier list may be associated with an SCS-specific configuration for bandwidth, location, etc.

[0094] In some aspects, the SL BWP configuration may be associated with a Tx resource pool for mode 1 (mode A), a Tx resource pool for mode 2 (mode B), and an Rx resource pool. In some aspects, a per-resource pool configuration may be provided. The per-resource pool configuration may include PSSCH / PSCCH / PSFCH configuration, number of subchannels, size or starting RB, and channel busy rate (CBR), modulation and coding scheme (MCS), sensing configuration, or power control configuration.

[0095] In some aspects, resource pools for positioning, SCS, BW, location, etc. may be associated with Tx resource pools for mode 1 (mode A), Tx resource pools for mode 2 (mode B), and Rx resource pools. In some aspects, per-resource pool configurations may be provided. Per-resource pool configurations may include PSCCH or SL-PRS configurations (e.g., including number of symbols, comb type, comb offset, number of subchannels, subchannel size, subchannel starting RB, etc.), CBR, MCS, sensing configuration, or power control configuration.

[0096] Fig. 8A 800 is a diagram illustrating example communications between a network entity 804 and a UE 802. In some aspects, the network entity 804 may be implemented as a converged base station, a disaggregated base station, an integrated access and backhaul (IAB) node, a relay node, a sidelink node, etc. In some aspects, the network entity 804 may be implemented in a converged or monolithic base station architecture, or alternatively in a disaggregated base station architecture, and may include one or more of the following: a CU, a DU, a RU, a near real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC. Fig. 8AAs illustrated in FIG. 1 , the network entity 804 may send a SIB 806 to the UE 802. The SIB may be of different types, such as SIB type 1 for cell selection, cell access, and system information (SI) scheduling, type 2 for random access, access barring, UL frequency information, and multimedia broadcast multicast service single frequency network configuration, type 3 for intra-frequency cell reselection, type 4 for intra-frequency neighbor cells, type 5 for inter-frequency neighbor cells, and other types. The SIB 806 may be a SIB type 12 for carrying a sidelink communication configuration. After receiving the SIB 806 of SIB type 12, the UE 802 may discard the stored segment of the previous SIB 12 (if any) and store the SIB 806, and assemble one or more information elements (IEs) based on the SIB 806. If there is an SL frequency list, the UE 802 may use the resource pool indicated by the SL frequency list for sidelink communication reception or sidelink communication transmission. The UE 802 may also perform CBR measurement based on the transmission resource pool indicated by the SIB 806. UE 802 may also perform sidelink DRB addition / modification / release based on the SL communication configuration in SIB 806. UE 802 may also store sidelink measurement configuration based on the SL communication configuration in SIB 806. In some aspects, the SL communication configuration may include separate configurations for UE 802, such as a sidelink data configuration for data communication of UE 802 and a sidelink positioning configuration for UE 802.

[0097] UE 802 may send sidelink UE information 808 to network entity 804. Sidelink UE information 808 may be used to inform the network that UE 802 may: 1) be interested in or no longer be interested in receiving or sending sidelink communications, 2) request assignment or release of transmission resources for sidelink communications, 3) report quality of service (QoS) parameters and QoS profiles related to sidelink communications, 4) report that a sidelink radio link failure or a sidelink RRC reconfiguration failure has been detected, 5) report sidelink UE capability information of an associated peer UE for unicast communications, 6) report RLC mode information of a sidelink data radio bearer received from an associated peer UE for unicast communications.

[0098] In some wireless communication systems, sidelink UE information may jointly report failures associated with SL data communication and positioning, and there may be no way to distinguish between failures associated with SL data communication and failures associated with positioning. Therefore, even if one of SL data communication or positioning has not failed, a joint failure may be reported, which may cause the configuration for SL data communication and positioning to be reconfigured. The example aspects provided herein may enable failures of SL data communication and positioning to be indicated separately, which may enable the configuration for SL data communication and positioning to be reconfigured separately upon failure, resulting in a more efficient configuration. Example sidelink UE information may be provided below:

[0099]

[0100]

[0101]

[0102] IE sl-RxInterestedFreqList may indicate the index of the frequency in which the UE is interested in receiving NR sidelink communications. Value 1 corresponds to the frequency of the first entry in the sl-FreqInfoList broadcast in SIB12, value 2 corresponds to the frequency of the second entry in the sl-FreqInfoList broadcast in SIB12, and so on. In this version, only value 1 may be included in the list of interested frequencies. IE sl-TxResourceReq may be a parameter for requesting transmit resources for sidelink communications from the network in the sidelink UE information. IE sl-TxInterestedFreqList may indicate the index of the frequency in which the UE is interested in sending sidelink communications. Value 1 may correspond to the frequency of the first entry in the sl-FreqInfoList broadcast in SIB12, value 2 may correspond to the frequency of the second entry in the sl-FreqInfoList broadcast in SIB12, and so on. IE sl-FailureList may indicate a failure. In some aspects, failures associated with sidelink positioning configuration and failures associated with sidelink data configuration may be indicated separately in the IE sl-FailureList.

[0103] Another example sidelink UE information is provided below:

[0104]

[0105]

[0106]

[0107] IE sl-RxInterestedFreqList may indicate the index of the frequency in which the UE is interested in receiving sidelink communications. Value 1 may correspond to the frequency of the first entry in the sl-FreqInfoList broadcast in SIB12, value 2 may correspond to the frequency of the second entry in the sl-FreqInfoList broadcast in SIB12, and so on. In this version, only value 1 may be included in the list of interested frequencies. IE sl-TxResourceReq may be a parameter for requesting transmit resources for sidelink communications from the network in the sidelink UE information. IE sl-TxInterestedFreqList may indicate the index of the frequency in which the UE is interested in sending sidelink communications. Value 1 may correspond to the frequency of the first entry in the sl-FreqInfoList broadcast in SIB12, value 2 may correspond to the frequency of the second entry in the sl-FreqInfoList broadcast in SIB12, and so on. IE sl-CapabilityInformationSidelink may include a UECapabilityInformationSidelink message received from a peer UE (which may also be included in ueCapabilityInformationSidelink-r16 in UECapabilityEnquirySidelink from the peer UE). IE sl-CastType may indicate the broadcast type of the corresponding target for which resources are requested. IE sl-DestinationIdentity may indicate the target to which the TX request and allocation from the network refers. IE sl-QoS-InfoList may include the QoS profile of the sidelink QoS flow. IE sl-QoS-FlowIdentity may uniquely identify a sidelink QoS flow between the UE and the network within the scope of the UE, which is unique for different targets and broadcast types. IE sl-RLC-ModeIndication may indicate the RLC mode and optionally the relevant QoS profile of the sidelink radio bearer, which has not yet been configured by the network and can be initiated in unicast by another UE. The RLC mode for one sidelink radio bearer may be aligned between the UE and the network via sl-QoS-FlowIdentity. The IE sl-TypeTxSyncList may represent a list of synchronization references used by the UE. In some aspects, the example sidelink UE information may also include an sl-PosRxInterestedFreqList IE, which represents the index of the frequencies at which the UE is interested in receiving sidelink communications for positioning.A value of 1 may correspond to the frequency of the first entry in the sl-FreqInfoList broadcast in SIB12, a value of 2 may correspond to the frequency of the second entry in the sl-FreqInfoList broadcast in SIB12, and so on. The sidelink UE information may also include an sl-PosTxResourceReqList associated with resources or parameters requesting transmission resources for sidelink communications used for positioning. In other words, in some aspects, the sidelink UE information 808 may include resources of interest or requested associated with sidelink communications used for positioning, which may be separate from resources of interest or requested associated with other sidelink communications.

[0108] An example SIB 12 for providing a sidelink communication configuration is provided below:

[0109]

[0110]

[0111]

[0112] IE sl-CSI-Acquisition may indicate whether CSI reporting is enabled in sidelink unicast. IE sl-EUTRA-AnchorCarrierFreqList may indicate a list of EUTRA anchor carrier frequencies. IE sl-FreqInfoList may indicate a sidelink communication configuration on some carrier frequencies. IE sl-MaxNumConsecutiveDTX may indicate the maximum number of consecutive HARQ DTXs before triggering a sidelink RLF. IE sl-MeasConfigCommon may indicate a measurement configuration for sidelink communication. IE sl-NR-AnchorCarrierFreqList may indicate a list of anchor carrier frequencies. When a global navigation satellite system (GNSS) is used for timing reference, IE sl-OffsetDFN may indicate a timing offset for the UE to determine direct frame number (DFN) timing. IE sl-RadioBearerConfigList may indicate one or more sidelink radio bearer configurations. IE sl-RLC-BearerConfigList may indicate one or more sidelink RLC bearer configurations. IE sl-SSB-PriorityNR may indicate the priority of sidelink SSB transmission and reception. IE t400 may indicate the value of timer T400 associated with performing a sidelink reconfiguration failure procedure. In some aspects, an IE for sidelink positioning configuration may be provided separately from IE SL-ConfigCommonNR, and the sidelink positioning configuration may be provided separately from the sidelink data configuration.

[0113] In some aspects, the IE for sidelink positioning configuration may include one or more of the following: an IE sl-pos-FreqInfoList that may indicate the sidelink positioning configuration on some carrier frequencies, an IE sl-MeasConfigCommon that may represent the measurement configuration of the sidelink communication for positioning, an IE sl-NR-pos-AnchorCarrierFreqList that may represent the anchor carrier frequency list for positioning, an IE EUTRA-pos-AnchorCarrierFreqList that may represent the EUTRA anchor carrier frequency list for positioning, an IE sl-pos-OffsetDFN that may represent the timing offset for the UE to determine the direct frame number (DFN) timing when the global navigation satellite system (GNSS) is used as a timing reference for positioning, a value of the timer T400 associated with performing a sidelink reconfiguration failure procedure for positioning, an IE that may represent the measurement configuration for sidelink positioning (AoA, AoD, reference signal received power (RSRP), or reference signal time difference (RSTD), UE Rx-Tx, etc.) sl-MeasConfigCommon, an IE of gap configuration for positioning (eg, which may identify gaps without Tx / Rx that the UE may use for positioning-related measurements), or other IEs.

[0114] In some aspects, instead of SIB type 12, SIB 806 may be another SIB type, such as SIB type 12A, which is specifically configured for sidelink positioning (rather than other sidelink communications). Another SIB of type 12 may be configured for UE 802 solely for sidelink communications (e.g., which are not related to positioning).

[0115] Figure 8B 850 is a diagram illustrating example communications between a network entity 854 and a UE 852. In some aspects, the network entity 854 may be implemented as a converged base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, a sidelink node, etc. In some aspects, the network entity 854 may be implemented in a converged or monolithic base station architecture, or alternatively in a decomposed base station architecture, and may include one or more of the following: a CU, a DU, a RU, a near real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC. Diagram 850 may illustrate a process for obtaining system information. As Figure 8B , UE 852 may receive MIB 856 and then SIB 858 from network entity 854. UE 852 may accordingly send system information request 860 to network entity 854 and receive system information message 862 accordingly.

[0116] Fig. 9 900 is a flow chart of a method of wireless communication. The method may be performed by a UE (eg, UE 104, UE 802, UE 852; device 1104).

[0117] At 902, the UE may receive at least one SIB from a network entity, the at least one SIB including a sidelink data configuration associated with data transmission and a sidelink positioning configuration associated with a positioning session. For example, the UE 802 may receive at least one SIB (e.g., 806) from the network entity 804, the at least one SIB including a sidelink data configuration associated with data transmission and a sidelink positioning configuration associated with a positioning session. In some aspects, 902 may be performed by the SL component 198. In some aspects, the sidelink data configuration may be the same configuration as the sidelink positioning configuration. In some aspects, the sidelink data configuration may be different from the sidelink positioning configuration. In some aspects, at least one SIB may be a SIB type 12 associated with the sidelink communication configuration. In some aspects, if the UE is capable of sidelink positioning and is configured by a set of upper layers to receive or send sidelink positioning, the SIB type 12 may be a SIB type 12a. In some aspects, the sidelink positioning configuration may be represented by a first information element (IE) in the SIB type 12, and wherein the sidelink data configuration may be represented by a second IE in the SIB type 12. In some aspects, the first IE may include: a sidelink positioning frequency information list associated with the positioning session, a sidelink positioning selection configuration associated with the positioning session, a sidelink positioning anchor carrier frequency list associated with the positioning session, a sidelink positioning offset associated with the positioning session, a sidelink positioning measurement configuration associated with the positioning session, or a sidelink positioning gap configuration associated with the positioning session. In some aspects, the sidelink positioning measurement configuration may include one or more of the following: angle of arrival (AoA), angle of departure (AoD), reference signal received power (RSRP), or reference signal time difference (RSTD). In some aspects, the sidelink positioning gap configuration may be associated with one or more gaps that are not transmitted or received.

[0118] At 904, the UE may send sidelink UE information to the network entity, the sidelink UE information including an indication of at least one of: a failure associated with the sidelink positioning configuration, a request for Tx sidelink resources for the positioning session, or a list of Rx sidelink resources for the positioning session. For example, UE 802 may send sidelink UE information 808 to the network entity 804, the sidelink UE information including an indication of at least one of: a failure associated with the sidelink positioning configuration, a request for Tx sidelink resources for the positioning session, or a list of Rx sidelink resources for the positioning session. In some aspects, 904 may be performed by SL component 198. In some aspects, the sidelink UE information may include a request for Tx sidelink resources for the positioning session and a list of Rx sidelink resources for the positioning session. In some aspects, the failure associated with the sidelink positioning configuration may be independent of the failure associated with the sidelink data configuration. In some aspects, the list of Rx sidelink resources for the positioning session may be a list of Rx sidelink resources of interest for the positioning session. In some aspects, the list of Rx side link resources may be in priority order, or the list of Rx side link resources may be associated with a priority tag.

[0119] Fig.10 1000 is a flow chart of a method of wireless communication. The method may be performed by a network entity (eg, base station 102, network entity 804, network entity 854, network entity 1102, network entity 1202).

[0120] At 1002, the network entity may send at least one SIB to the UE, the at least one SIB including a sidelink data configuration associated with data transmission and a sidelink positioning configuration associated with a positioning session. For example, the network entity 804 may send at least one SIB (e.g., 806) to the UE 802, the at least one SIB including a sidelink data configuration associated with data transmission and a sidelink positioning configuration associated with a positioning session. In some aspects, 1002 may be performed by the SL component 199. In some aspects, the sidelink data configuration may be the same configuration as the sidelink positioning configuration. In some aspects, the sidelink data configuration may be different from the sidelink positioning configuration. In some aspects, at least one SIB may be a SIB type 12 associated with the sidelink communication configuration. In some aspects, if the UE is capable of sidelink positioning and is configured by a set of upper layers to receive or send sidelink positioning, the SIB type 12 may be a SIB type 12a. In some aspects, the sidelink positioning configuration may be represented by a first information element (IE) in the SIB type 12, and wherein the sidelink data configuration may be represented by a second IE in the SIB type 12. In some aspects, the first IE may include: a sidelink positioning frequency information list associated with the positioning session, a sidelink positioning selection configuration associated with the positioning session, a sidelink positioning anchor carrier frequency list associated with the positioning session, a sidelink positioning offset associated with the positioning session, a sidelink positioning measurement configuration associated with the positioning session, or a sidelink positioning gap configuration associated with the positioning session. In some aspects, the sidelink positioning measurement configuration may include one or more of the following: angle of arrival (AoA), angle of departure (AoD), reference signal received power (RSRP), or reference signal time difference (RSTD). In some aspects, the sidelink positioning gap configuration may be associated with one or more gaps that are not transmitted or received.

[0121] At 1004, the network entity may receive sidelink UE information from the UE, the sidelink UE information including an indication of at least one of: a failure associated with the sidelink positioning configuration, a request for Tx sidelink resources for the positioning session, or a list of Rx sidelink resources for the positioning session. For example, the network entity 804 may receive sidelink UE information 808 from the UE 802, the sidelink UE information including an indication of at least one of: a failure associated with the sidelink positioning configuration, a request for Tx sidelink resources for the positioning session, or a list of Rx sidelink resources for the positioning session. In some aspects, 1004 may be performed by the SL component 199. In some aspects, the sidelink UE information may include a request for Tx sidelink resources for the positioning session and a list of Rx sidelink resources for the positioning session. In some aspects, the failure associated with the sidelink positioning configuration may be independent of the failure associated with the sidelink data configuration. In some aspects, the list of Rx sidelink resources for the positioning session may be a list of Rx sidelink resources of interest for the positioning session. In some aspects, the list of Rx side link resources may be in priority order, or the list of Rx side link resources may be associated with a priority tag.

[0122] Fig.111100 is a diagram illustrating an example of a hardware implementation for an apparatus 1104. The apparatus 1104 may be a UE, may be a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1104 may include a cellular baseband processor 1124 (also referred to as a modem) coupled to one or more transceivers 1122 (e.g., a cellular RF transceiver). The cellular baseband processor 1124 may include on-chip memory 1124'. In some aspects, the apparatus 1104 may also include one or more subscriber identity module (SIM) cards 1120 and an application processor 1106 coupled to a secure digital (SD) card 1108 and a screen 1110. The application processor 1106 may include on-chip memory 1106'. In some aspects, the device 1104 may also include a Bluetooth module 1112, a WLAN module 1114, a satellite system module 1116 (e.g., a GNSS module), one or more sensor modules 1118 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial management unit (IMU), a gyroscope, and / or an accelerometer; various types of ranging units, magnetometers, audio, and / or other technologies for positioning), an additional memory module 1126, a power supply 1130, and / or a camera 1132. The Bluetooth module 1112, the WLAN module 1114, and the satellite system module 1116 may include an on-chip transceiver (TRX) / receiver (RX). The cellular baseband processor 1124 communicates with the UE 104 and / or with the RU associated with the network entity 1102 through the transceiver 1122 via one or more antennas 1180. The cellular baseband processor 1124 and the application processor 1106 may each include a computer-readable medium / memory 1124', 1106', respectively. The additional memory module 1126 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 1124', 1106', 1126 may be non-transitory. The cellular baseband processor 1124 and the application processor 1106 are each responsible for general processing, including executing software stored on the computer-readable medium / memory. The software enables the cellular baseband processor 1124 / application processor 1106 to perform various functions described herein when executed by the cellular baseband processor 1124 / application processor 1106. The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor 1124 / application processor 1106 when executing the software. The cellular baseband processor 1124 / application processor 1106 may be a component of the UE 350 and may include at least one of the memory 360 and / or the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the device 1104 may be a processor chip (modem and / or application) and include only the cellular baseband processor 1124 and / or the application processor 1106, and in another configuration, the device 1104 may be the entire UE (e.g., see Figure 3 350) and includes additional modules of device 1104.

[0123] As discussed herein, the SL component 198 may be configured to receive at least one system information block (SIB) from a network entity, the at least one SIB including a sidelink data configuration associated with data transmission and a sidelink positioning configuration associated with a positioning session. In some aspects, the SL component 198 may also be configured to send sidelink UE information to the network entity, the sidelink UE information including an indication of at least one of: a failure associated with the sidelink positioning configuration, a request for a transmit (Tx) sidelink resource for a positioning session, or a list of receive (Rx) sidelink resources for a positioning session. The SL component 198 may be within the cellular baseband processor 1124, the application processor 1106, or both the cellular baseband processor 1124 and the application processor 1106. The SL component 198 may be one or more hardware components that are specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination of the foregoing. As shown, the device 1104 may include a variety of components configured for various functions. In one configuration, the device 1104 (specifically, the cellular baseband processor 1124 and / or the application processor 1106) includes a component for receiving at least one SIB from a network entity, the at least one SIB including a sidelink data configuration associated with data transmission and a sidelink positioning configuration associated with a positioning session. In some aspects, the device 1104 may also include a component for sending sidelink UE information to the network entity, the sidelink UE information including an indication of at least one of the following: a failure associated with the sidelink positioning configuration, a request for Tx sidelink resources for the positioning session, or a list of Rx sidelink resources for the positioning session. These components may be the SL component 198 of the device 1104 configured to perform the functions recorded by the components. As described herein, the device 1104 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Therefore, in one configuration, the component may be a TX processor 368, an RX processor 356, and / or a controller / processor 359 configured to perform the functions recorded by the components.

[0124] Fig.121200 is a diagram illustrating an example of a hardware implementation for a network entity 1202. The network entity 1202 may be a BS, a component of a BS, or may implement BS functionality. The network entity 1202 may include at least one of a CU 1210, a DU 1230, or a RU 1240. For example, depending on the layer functionality handled by the component 199, the network entity 1202 may include a CU 1210; both a CU 1210 and a DU 1230; each of the CU 1210, the DU 1230, and the RU 1240; the DU 1230; both a DU 1230 and a RU 1240; or the RU 1240. The CU 1210 may include a CU processor 1212. The CU processor 1212 may include an on-chip memory 1212'. In some aspects, the CU 1210 may also include an additional memory module 1214 and a communication interface 1218. CU 1210 communicates with DU 1230 via a midhaul link, such as an F1 interface. DU 1230 may include a DU processor 1232. DU processor 1232 may include on-chip memory 1232'. In some aspects, DU 1230 may also include an additional memory module 1234 and a communication interface 1238. DU 1230 communicates with RU 1240 via a fronthaul link. RU 1240 may include a RU processor 1242. RU processor 1242 may include on-chip memory 1242'. In some aspects, RU 1240 may also include an additional memory module 1244, one or more transceivers 1246, an antenna 1280, and a communication interface 1248. RU 1240 communicates with UE 104. On-chip memory 1212', 1232', 1242' and additional memory modules 1214, 1234, 1244 may each be considered a computer-readable medium / memory. Each computer readable medium / memory may be non-transitory. Each of processors 1212, 1232, 1242 is responsible for general processing, including executing software stored on the computer readable medium / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described herein. The computer readable medium / memory may also be used to store data manipulated by the processor when executing the software.

[0125] As discussed herein, the SL component 199 may be configured to send at least one system information block (SIB) to a user equipment (UE), the at least one SIB including a sidelink data configuration associated with data transmission and a sidelink positioning configuration associated with a positioning session. In some aspects, the SL component 199 may also be configured to receive sidelink UE information from the UE, the sidelink UE information including an indication of at least one of: a failure associated with the sidelink positioning configuration, a request for a transmit (Tx) sidelink resource for a positioning session, or a list of receive (Rx) sidelink resources for a positioning session. The SL component 199 may be within one or more processors of one or more of the CU 1210, the DU 1230, and the RU 1240. The SL component 199 may be one or more hardware components that are specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination of the foregoing. The network entity 1202 may include a variety of components configured for various functions. In one configuration, the network entity 1202 includes a component for sending at least one SIB to the UE, the at least one SIB including a sidelink data configuration associated with the data transmission and a sidelink positioning configuration associated with the positioning session. In some aspects, the network entity 1202 may also include a component for receiving sidelink UE information from the UE, the sidelink UE information including an indication of at least one of the following: a failure associated with the sidelink positioning configuration, a request for Tx sidelink resources for the positioning session, or a list of Rx sidelink resources for the positioning session. These components may be the SL component 199 of the network entity 1202 configured to perform the functions recorded by the components. As described herein, the network entity 1202 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Therefore, in one configuration, the component may be a TX processor 316, an RX processor 370, and / or a controller / processor 375 configured to perform the functions recorded by the components.

[0126] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is merely an illustration of the exemplary method. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart may be rearranged based on design preferences. Further, some blocks may be combined or omitted. The attached method claims provide the elements of the various blocks in a sample order, but are not limited to the specific order or hierarchy provided.

[0127] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not limited to the various aspects described herein, but should be given the full scope consistent with the language claims. Unless specifically stated, reference to an element in the singular form does not mean "one and only one", but "one or more". Terms such as "if", "when" and "while" do not mean a direct temporal relationship or reaction. That is, these phrases, such as "when ......", do not mean an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply imply that if the conditions are met, the action will occur, but no specific or immediate time limit is required for the occurrence of the action. The word "exemplary" is used herein to mean "used as an example, instance, or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having advantages over other aspects. Unless specifically stated, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, which may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a set of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If the first device receives data from the second device or sends data to the second device, the data may be directly received / sent between the first device and the second device, or indirectly received / sent between the first device and the second device through a collection of devices. All structural and functional equivalents of the elements of the various aspects described throughout the present disclosure that are known or will later be known to a person of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims. Words such as "module", "mechanism", "element", "device", etc. may not replace the word "component". Therefore, no claim element will be interpreted as a component plus function unless the element is explicitly stated using the phrase "component for..."

[0128] As used herein, the phrase "based on" should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) should be interpreted as "based at least on A" unless specifically stated differently.

[0129] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein without limitation.

[0130] Aspect 1 is a method for wireless communication at a UE, the method comprising: receiving at least one SIB from a network entity, the at least one SIB comprising a sidelink data configuration associated with data transmission and a sidelink positioning configuration associated with a positioning session; and sending sidelink UE information to the network entity, the sidelink UE information comprising an indication of at least one of: a failure associated with the sidelink positioning configuration, a request for Tx sidelink resources for the positioning session, or a list of Rx sidelink resources for the positioning session.

[0131] Aspect 2 is a method according to aspect 1, wherein the side link data configuration may be the same configuration as the side link positioning configuration.

[0132] Aspect 3 is a method according to any one of Aspects 1 to 2, wherein the sidelink data configuration may be different from the sidelink positioning configuration.

[0133] Aspect 4 is a method according to any one of Aspects 1 to 3, wherein the sidelink UE information may include the request for the Tx sidelink resources for the positioning session and the list of the Rx sidelink resources for the positioning session.

[0134] Aspect 5 is a method according to any one of aspects 1 to 4, wherein the at least one SIB may be a SIB type 12 associated with a sidelink communication configuration.

[0135] Aspect 6 is a method according to any one of Aspects 1 to 5, wherein if the UE is capable of sidelink positioning and is configured by a set of upper layers to receive or send sidelink positioning, the SIB type 12 may be SIB type 12a.

[0136] Aspect 7 is a method according to any one of Aspects 1 to 6, wherein the sidelink positioning configuration can be represented by a first information element (IE) in the SIB type 12, and wherein the sidelink data configuration can be represented by a second IE in the SIB type 12.

[0137] Aspect 8 is a method according to any one of Aspects 1 to 7, wherein the first IE may include: a sidelink positioning frequency information list associated with the positioning session, a sidelink positioning selection configuration associated with the positioning session, a sidelink positioning anchor carrier frequency list associated with the positioning session, a sidelink positioning offset associated with the positioning session, a sidelink positioning measurement configuration associated with the positioning session, or a sidelink positioning gap configuration associated with the positioning session.

[0138] Aspect 9 is a method according to any one of Aspects 1 to 8, wherein the side link positioning measurement configuration may include one or more of the following: angle of arrival (AoA), angle of departure (AoD), reference signal received power (RSRP) or reference signal time difference (RSTD) or UE Rx-Tx measurement.

[0139] Aspect 10 is a method according to any one of aspects 1 to 9, wherein the sidelink positioning gap configuration may be associated with one or more gaps without transmission or reception.

[0140] Aspect 11 is a method according to any one of aspects 1 to 10, wherein the failure associated with the sidelink positioning configuration may be independent of the failure associated with the sidelink data configuration.

[0141] Aspect 12 is a method according to any one of aspects 1 to 11, wherein the list of Rx side link resources for the positioning session may be a list of interested Rx side link resources for the positioning session.

[0142] Aspect 13 is a method according to any one of Aspects 1 to 13, wherein the list of Rx side link resources may be in priority order, or the list of Rx side link resources may be associated with a priority tag.

[0143] Aspect 14 is a method according to any one of aspects 1 to 13, wherein the method is performed at a device including at least one processor and a memory. The device may also include a transceiver or an antenna coupled to the at least one processor, and wherein the transceiver or the antenna may be configured to send the sidelink UE information.

[0144] Aspect 15 is a method for performing wireless communications at a network entity, the method comprising: sending at least one SIB to a UE, the at least one SIB comprising a sidelink data configuration associated with data transmission and a sidelink positioning configuration associated with a positioning session; and receiving sidelink UE information from the UE, the sidelink UE information comprising an indication of at least one of: a failure associated with the sidelink positioning configuration, a request for Tx sidelink resources for the positioning session, or a list of Rx sidelink resources for the positioning session.

[0145] Aspect 16 is a method according to aspect 15, wherein the sidelink data configuration may be the same configuration as the sidelink positioning configuration.

[0146] Aspect 17 is a method according to any one of Aspects 15 to 16, wherein the sidelink data configuration may be different from the sidelink positioning configuration.

[0147] Aspect 18 is a method according to any one of Aspects 15 to 17, wherein the sidelink UE information may include the request for the Tx sidelink resources for the positioning session and the list of the Rx sidelink resources for the positioning session.

[0148] Aspect 19 is a method according to any one of aspects 15 to 18, wherein the at least one SIB may be a SIB type 12 associated with a sidelink communication configuration.

[0149] Aspect 20 is a method according to any one of aspects 15 to 19, wherein if the UE is capable of sidelink positioning and is configured by a set of upper layers to receive or send sidelink positioning, the SIB type 12 may be SIB type 12a.

[0150] Aspect 21 is a method according to any one of Aspects 15 to 20, wherein the sidelink positioning configuration may be represented by a first information element (IE) in the SIB type 12, and wherein the sidelink data configuration may be represented by a second IE in the SIB type 12.

[0151] Aspect 22 is a method according to any one of Aspects 15 to 21, wherein the first IE may include: a sidelink positioning frequency information list associated with the positioning session, a sidelink positioning selection configuration associated with the positioning session, a sidelink positioning anchor carrier frequency list associated with the positioning session, a sidelink positioning offset associated with the positioning session, a sidelink positioning measurement configuration associated with the positioning session, or a sidelink positioning gap configuration associated with the positioning session.

[0152] Aspect 23 is a method according to any one of Aspects 15 to 22, wherein the side link positioning measurement configuration may include one or more of the following: angle of arrival (AoA), angle of departure (AoD), reference signal received power (RSRP) or reference signal time difference (RSTD) or UE Rx-Tx measurement.

[0153] Aspect 24 is a method according to any one of aspects 15 to 23, wherein the sidelink positioning gap configuration may be associated with one or more gaps without transmission or reception.

[0154] Aspect 25 is a method according to any one of aspects 15 to 24, wherein the failure associated with the sidelink positioning configuration may be independent of the failure associated with the sidelink data configuration.

[0155] Aspect 26 is a method according to any one of aspects 15 to 25, wherein the list of Rx side link resources for the positioning session may be a list of interested Rx side link resources for the positioning session.

[0156] Aspect 27 is a method according to any one of Aspects 15 to 26, wherein the list of Rx side link resources may be in priority order, or the list of Rx side link resources may be associated with a priority tag.

[0157] Aspect 28 is a method according to any one of aspects 15 to 27, wherein the method is performed at an apparatus comprising at least one processor and a memory. The apparatus may also include a transceiver or an antenna coupled to the at least one processor, and wherein the transceiver or the antenna may be configured to transmit the sidelink UE information.

[0158] Aspect 29 is an apparatus for wireless communication at a device, the apparatus comprising a memory and at least one processor coupled to the memory, the at least one processor being configured to perform a method according to any one of aspects 1 to 14 based at least in part on information stored in the memory. The apparatus may include at least one of a transceiver or an antenna coupled to the at least one processor.

[0159] Aspect 30 is an apparatus for wireless communication, the apparatus comprising means for performing a method according to any one of aspects 1 to 14.

[0160] Aspect 31 is a non-transitory computer-readable medium comprising instructions which, when executed by an apparatus, cause the apparatus to perform the method according to any one of aspects 1 to 14.

[0161] Aspect 32 is an apparatus for wireless communication at a device, the apparatus comprising a memory and at least one processor coupled to the memory, the at least one processor being configured to perform a method according to any one of aspects 15 to 28 based at least in part on information stored in the memory. The apparatus may include at least one of a transceiver or an antenna coupled to the at least one processor.

[0162] Aspect 33 is an apparatus for wireless communication, the apparatus comprising means for performing a method according to any one of aspects 15 to 28.

[0163] Aspect 34 is a non-transitory computer-readable medium comprising instructions which, when executed by an apparatus, cause the apparatus to perform the method according to any one of aspects 15 to 28.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to: receiving at least one system information block (SIB) from a network entity, the at least one SIB comprising a sidelink data configuration associated with a data transmission and a sidelink positioning configuration associated with a positioning session; and sending sidelink UE information to the network entity, the sidelink UE information comprising an indication of at least one of: a failure associated with the sidelink positioning configuration, a request for transmit (Tx) sidelink resources for the positioning session, or a list of receive (Rx) sidelink resources for the positioning session.

2. The apparatus of claim 1, wherein the sidelink data configuration is the same configuration as the sidelink positioning configuration.

3. An apparatus according to claim 1, wherein the sidelink data configuration is different from the sidelink positioning configuration.

4. The apparatus of claim 1, wherein the sidelink UE information comprises the request for the Tx sidelink resources for the positioning session and the list of the Rx sidelink resources for the positioning session.

5. The apparatus of claim 1, wherein the at least one SIB is a system information block (SIB) type 12 associated with a sidelink communication configuration.

6. The apparatus of claim 5, wherein the SIB type 12 is a SIB type 12a when the UE is capable of sidelink positioning and is configured by a set of upper layers to receive or transmit sidelink positioning.

7. The apparatus of claim 5, wherein the sidelink positioning configuration is represented by a first information element (IE) in the SIB type 12, and wherein the sidelink data configuration is represented by a second IE in the SIB type 12.

8. The apparatus of claim 7, wherein the first IE comprises: A sidelink positioning frequency information list associated with the positioning session, a sidelink positioning selection configuration associated with the positioning session, a sidelink positioning anchor carrier frequency list associated with the positioning session, a sidelink positioning offset associated with the positioning session, a sidelink positioning measurement configuration associated with the positioning session, or a sidelink positioning gap configuration associated with the positioning session.

9. The apparatus of claim 8, wherein the sidelink positioning measurement configuration comprises one or more of: angle of arrival (AoA), angle of departure (AoD), reference signal received power (RSRP), or reference signal time difference (RSTD), or UE Rx-Tx measurement.

10. The apparatus of claim 8, wherein the sidelink positioning gap configuration is associated with one or more gaps of no transmission or reception.

11. The apparatus of claim 1 , wherein the failure associated with the sidelink positioning configuration is independent of a failure associated with the sidelink data configuration. 12 . The apparatus of claim 1 , wherein the list of Rx sidelink resources for the positioning session is a list of interested Rx sidelink resources for the positioning session. 13 . The apparatus of claim 1 , wherein the list of Rx side link resources is in a priority order, or the list of Rx side link resources is associated with a priority tag.

14. The apparatus of claim 1, further comprising a transceiver or an antenna coupled to the at least one processor, and wherein the transceiver or the antenna is configured to transmit the sidelink UE information.

15. An apparatus for wireless communication at a network entity, the apparatus comprising: Memory; and at least one processor coupled to the memory, wherein the at least one processor is configured to: transmitting at least one system information block (SIB) to a user equipment (UE), the at least one SIB comprising a sidelink data configuration associated with a data transmission and a sidelink positioning configuration associated with a positioning session; and Sidelink UE information is received from the UE, the sidelink UE information comprising an indication of at least one of: a failure associated with the sidelink positioning configuration, a request for transmit (Tx) sidelink resources for the positioning session, or a list of receive (Rx) sidelink resources for the positioning session.

16. The apparatus of claim 15, wherein the sidelink data configuration is the same configuration as the sidelink positioning configuration.

17. The apparatus of claim 15, wherein the sidelink data configuration is different from the sidelink positioning configuration.

18. The apparatus of claim 15, wherein the sidelink UE information comprises the request for the Tx sidelink resources for the positioning session and the list of the Rx sidelink resources for the positioning session.

19. The apparatus of claim 15, wherein the at least one SIB is a system information block (SIB) type 12 associated with a sidelink communication configuration.

20. The apparatus of claim 19, wherein the SIB type 12 is SIB type 12a if the UE is capable of sidelink positioning and is configured by a set of upper layers to receive or transmit sidelink positioning.

21. The apparatus of claim 19, wherein the sidelink positioning configuration is represented by a first information element (IE) in the SIB type 12, and wherein the sidelink data configuration is represented by a second IE in the SIB type 12.

22. The apparatus of claim 21, wherein the first IE comprises: A sidelink positioning frequency information list associated with the positioning session, a sidelink positioning selection configuration associated with the positioning session, a sidelink positioning anchor carrier frequency list associated with the positioning session, a sidelink positioning offset associated with the positioning session, a sidelink positioning measurement configuration associated with the positioning session, or a sidelink positioning gap configuration associated with the positioning session.

23. The apparatus of claim 22, wherein the sidelink positioning measurement configuration comprises one or more of: angle of arrival (AoA), angle of departure (AoD), reference signal received power (RSRP), or reference signal time difference (RSTD), or UE Rx-Tx measurement.

24. The apparatus of claim 22, wherein the sidelink positioning gap configuration is associated with one or more gaps of no transmission or reception.

25. The apparatus of claim 15, wherein the failure associated with the sidelink positioning configuration is independent of a failure associated with the sidelink data configuration. 26 . The apparatus of claim 15 , wherein the list of Rx sidelink resources for the positioning session is a list of interested Rx sidelink resources for the positioning session. 27 . The apparatus of claim 15 , wherein the list of Rx side link resources is in a priority order, or the list of Rx side link resources is associated with a priority tag.

28. The apparatus of claim 15, further comprising a transceiver or an antenna coupled to the at least one processor, and wherein the transceiver or the antenna is configured to receive the sidelink UE information.

29. A method of wireless communication at a user equipment (UE), the method comprising: receiving at least one system information block (SIB) from a network entity, the at least one SIB comprising a sidelink data configuration associated with a data transmission and a sidelink positioning configuration associated with a positioning session; and sending sidelink UE information to the network entity, the sidelink UE information comprising an indication of at least one of: a failure associated with the sidelink positioning configuration, a request for transmit (Tx) sidelink resources for the positioning session, or a list of receive (Rx) sidelink resources for the positioning session.

30. A method for wireless communication at a network entity, the method comprising: transmitting at least one system information block (SIB) to a user equipment (UE), the at least one SIB comprising a sidelink data configuration associated with a data transmission and a sidelink positioning configuration associated with a positioning session; and Sidelink UE information is received from the UE, the sidelink UE information comprising an indication of at least one of: a failure associated with the sidelink positioning configuration, a request for transmit (Tx) sidelink resources for the positioning session, or a list of receive (Rx) sidelink resources for the positioning session.

Images