Resource allocation mode 1 operation in fr2 sidelink

Abstract

The UE receives, from a network entity, a resource allocation for sidelink transmission, the resource allocation including an indication of a destination identifier (ID). The UE transmits the sidelink transmission to the second UE based on the resource allocation for the sidelink transmission and a destination ID associated with the second UE. The UE receives, from a first UE, a request to form a connection for sidelink communication. The UE measures at least one conflicting sidelink transmission from the at least one additional UE that interferes with the sidelink transmission from the first UE, and sends a sidelink conflict report to the network entity indicating the measured at least one conflicting sidelink transmission from the at least one additional UE. The UE communicates with the first UE via a sidelink communication after the sidelink collision report based on the resource allocation for the sidelink transmission.

Description

[0001] Cross-reference to related applications

[0002] This application claims the benefit of U.S. non-provisional patent application No. 18 / 350,709, filed July 11, 2023, entitled “RESOURCE ALLOCATION MODE 1 OPERATION IN FR2 SIDELINK”, which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] This disclosure relates in general to communication systems, and more specifically to the configuration of resource allocation for sidelinks. Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. 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 telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the city, national, regional, and even global levels. An example telecommunications standard is 5G New Radio (NR). 5G NR is part of the Continuous Evolution of Mobile Broadband (CEM) program issued by the 3rd 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. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Some aspects of 5G NR can be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. Furthermore, these improvements can also be applied to other multiple access technologies and telecommunications standards that adopt these technologies. Summary of the Invention

[0006] The following is a simplified summary of one or more aspects to provide a basic understanding of such aspects. This summary is not a comprehensive overview of all conceived aspects. It neither identifies key or essential 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 the more detailed descriptions that follow.

[0007] In one aspect of this disclosure, a method, computer-readable medium, and apparatus are provided. The apparatus may be a device at a first UE. The device may be a processor and / or modem at the first UE, or the first UE itself. The apparatus receives a resource allocation for sidelink transmission from a network entity, the resource allocation including an indication of a destination identifier (ID). The apparatus transmits a sidelink transmission to a second UE based on the resource allocation for sidelink transmission and the destination ID associated with a second UE.

[0008] In one aspect of this disclosure, a method, computer-readable medium, and apparatus are provided. The apparatus may be a device at a second UE. The device may be a processor and / or modem at the second UE, or the second UE itself. The apparatus receives from a first UE a request to form a connection for sidelink communication. The apparatus measures at least one conflicting sidelink transmission from at least one additional UE that interferes with the sidelink transmission from the first UE. The apparatus sends a sidelink conflict report to a network entity, the sidelink conflict report indicating the measured at least one conflicting sidelink transmission from at least one additional UE. Following the sidelink conflict report, the apparatus communicates with the first UE via sidelink communication based on resource allocation for sidelink transmission.

[0009] In one aspect of this disclosure, a method, computer-readable medium, and apparatus are provided. The apparatus may be a device at a network entity. The device may be a processor and / or modem at the network entity or the network entity itself. The apparatus schedules resource allocation for sidelink transmission based on at least one of a destination identifier (ID) for sidelink transmission or a sidelink conflict report. The apparatus provides resource allocation for sidelink transmission to a first user equipment (UE).

[0010] To achieve the foregoing and related objectives, one or more aspects include the features fully described below and specifically pointed out in the claims. The following description and drawings illustrate some exemplary features of one or more aspects in detail. However, these features indicate only a few of the various ways in which the principles of the various aspects may be employed. Attached Figure Description

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

[0012] Figure 2 An example aspect of the side link time slot structure is illustrated.

[0013] Figure 3 This is a diagram illustrating an example of a first and a second device involved in wireless communication based, for example, a side link.

[0014] Figure 4 Examples of sidelink communication between devices are illustrated according to the aspects presented in this article.

[0015] Figure 5A and Figure 5B This is a diagram illustrating an example of a time slot.

[0016] Figure 6A and Figure 6B This is a diagram of a sidelink communication system.

[0017] Figure 7 This is a diagram illustrating an example of a sidelink communication system.

[0018] Figure 8 This is a diagram illustrating an example of sidelink information in a report.

[0019] Figure 9 This is a diagram illustrating an example of transmission via multiple sidelinks.

[0020] Figure 10 This is a diagram illustrating an example of the interference level in a sidelink conflict report.

[0021] Figure 11 This is a call flow diagram of signaling between the first UE, the second UE, and the network entity.

[0022] Figure 12 This is a flowchart of a wireless communication method.

[0023] Figure 13 This is a flowchart of a wireless communication method.

[0024] Figure 14 These are illustrations illustrating specific hardware implementations used for example devices and / or network entities.

[0025] Figure 15 This is a flowchart of a wireless communication method.

[0026] Figure 16 This is a flowchart of a wireless communication method.

[0027] Figure 17 These are illustrations illustrating specific hardware implementations used for example devices and / or network entities.

[0028] Figure 18This is a flowchart of a wireless communication method.

[0029] Figure 19 This is a flowchart of a wireless communication method.

[0030] Figure 20 This is a diagram illustrating an example of a hardware implementation used for an example network entity. Detailed Implementation

[0031] In a wireless communication system (e.g., a sidelink communication system), mode 1 and mode 2 resource allocation configurations can be utilized. In the mode 1 resource allocation configuration, the base station can allocate resources to the transmitting UE for sidelink data channel transmission. In the mode 2 resource allocation configuration, the transmitting UE 612 can autonomously perform resource allocation for sidelink transmission with the receiving UE.

[0032] In FR1, sidelink UEs can use omnidirectional antennas to transmit and receive PSCCH / PSSCH. Sidelink transmissions performed by a sidelink UE can be received by all sidelink UEs in the same area. The base station can utilize orthogonal resources (such as in different time slots or sub-channels) to schedule sidelink transmissions from multiple sidelink UEs to avoid conflicts between sidelink transmissions. In FR2 sidelink operation, sidelink UEs use beamforming to transmit and receive sidelink transmissions. Beam pairs can be established / maintained with sidelink UEs with unicast connections. For parallel scheduling of multiple SL transmissions in the same time slot / sub-channel, the network can be aware of conflicts between sidelink transmissions from different UE pairs. It would be beneficial for the network to control the beamforming of sidelink transmissions to increase the opportunity for scheduling parallel transmissions of SL transmissions / receptions using beamforming in FR2.

[0033] The aspects presented herein provide configurations for enhanced resource allocation for sidelink mode 1 operation. For example, this configuration allows the network to schedule multiple sidelink transmissions in the same time slot and subchannel. The network can schedule multiple sidelink transmissions based on at least one of the destination ID for the sidelink transmission or a sidelink conflict report. The network can obtain information related to the destination ID from the transmitting UE and information related to the sidelink conflict report from the receiving UE.

[0034] The detailed descriptions following, illustrated with reference to the accompanying drawings, describe various configurations and do not represent the only configurations in which the concepts described herein can be practiced. To provide a thorough understanding of the various concepts, the detailed descriptions 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.

[0035] Various apparatuses and methods are presented with reference to several aspects of a telecommunications system. These apparatuses and methods are described in detail below and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively, “elements”). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0036] As an example, an element, any part of an element, or any combination of elements may be implemented as a “processing system” including 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, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in a processing system may execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, or any combination thereof.

[0037] Therefore, 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 code on a computer-readable medium. Computer-readable media include computer storage media. Storage media can be any available medium that can be accessed by a computer. As examples, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disc storage devices, magnetic disk storage devices, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that may be used to store computer-executable code in the form of instructions or data structures accessible to a computer.

[0038] While aspects, implementations, and / or use cases are described herein by way of example, additional or different aspects, implementations, and / or use cases may arise in many different arrangements and scenarios. The aspects, implementations, and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, aspects, implementations, and / or use cases may arise via integrated chip implementations and other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specific to a use case or application, the described examples may exhibit broad applicability. Aspects, implementations, and / or use cases can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the technologies described herein. In some practical settings, devices incorporating the described aspects and features 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 involve 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, chip-level components, systems, distributed arrangements, aggregated or decomposed components, end-user equipment, etc., of various sizes, shapes, and configurations.

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

[0040] Aggregated base stations can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. Decentralized base stations can be configured to utilize a protocol stack that is physically or logically distributed across two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some respects, the CU may be implemented within a RAN node, and one or more DUs may co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. DUs may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0041] Base station operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be utilized in Integrated Access Backhaul (IAB) networks, Open Radio Access Networks (O-RAN (such as network configurations initiated by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)). Decomposition can include distributing functionality across two or more units in various physical locations, as well as virtually distributing the functionality of at least one unit, which enables flexibility in network design. The various units of a decomposed base station or decomposed RAN architecture can be configured to communicate wirelessly with at least one other unit.

[0042] Figure 1 Figure 100 illustrates an example of a wireless communication system and access network. The illustrated wireless communication system includes a decomposed base station architecture. The decomposed base station architecture may include one or more CUs 110, which may communicate directly with the core network 120 via a backhaul link, or indirectly with the core network 120 via one or more decomposed 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. CUs 110 may communicate with one or more DUs 130 via a corresponding midhaul link (such as an F1 interface). DUs 130 may communicate with one or more RUs 140 via a corresponding fronthaul link. RUs 140 may communicate with a corresponding UE 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

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

[0044] In some aspects, the CU 110 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Serving Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by the CU 110. The CU 110 can be configured to handle user plane functionality (i.e., Central Unit-User Plane (CU-UP)), control plane functionality (i.e., Central Unit-Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 110 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 110 can be implemented to communicate with the DU 130 for network control and signaling, as needed.

[0045] DU 130 may correspond to a logic unit that includes one or more base station functions for controlling the operation of one or more RU 140s. In some aspects, DU 130 may at least partially host one or more of the Radio Link Control (RLC) layer, Media 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.) according to functional splits (such as those defined by 3GPP). In some aspects, DU 130 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signaling with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

[0046] Lower-layer functionality can be implemented by one or more RU 140s. In some deployments, an RU140 controlled by a 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, or Physical Random Access Channel (PRACH) extraction and filtering, or both, based at least in part on functional decomposition (such as lower-layer functional decomposition). In such architectures, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UE 104s. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration enables the implementation of the DU 130 and CU 110 in cloud-based RAN architectures such as vRAN architectures.

[0047] SMO framework 105 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 105 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, SMO framework 105 can be configured to interact with a cloud computing platform such as 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 the 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 implementations, SMO framework 105 can communicate with the hardware aspects of the 4G RAN (such as Open eNB (O-eNB) 111) via the O1 interface. Additionally, in some implementations, SMO framework 105 can communicate directly with one or more RU 140s via the O1 interface. SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of SMO framework 105.

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

[0049] In some implementations, to generate AI / ML models 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. This information can be utilized by the near-RT RIC 125 and may be received from non-network data sources or network functions 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 in performance and employ AI / ML models to perform corrective actions via the SMO framework 105 (such as reconfiguration via O1) or by creating RAN management policies (such as A1 policies).

[0050] At least one of CU 110, DU 130, and RU 140 may be referred to as base station 102. Therefore, base station 102 may include one or more of CU 110, DU 130, and RU 140 (each component is indicated by a dashed line to indicate that each component may or may not be included in base station 102). Base station 102 provides UE 104 with an access point to core network 120. Base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Small cells include femtocells, picocells, and microcells. A network that includes both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include an evolved home node B (eNB) (HeNB), which can provide service 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) transmission (also known as reverse link) from UE 104 to RU 140 and / or downlink (DL) transmission (also known as forward link) transmission from RU 140 to UE 104. The communication link may utilize multiple-input multiple-output (MIMO) antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may use one or more carriers. For each direction used for transmission, the total number of carriers can be up to [number missing]. Yx MHz ( x For each carrier allocated in carrier aggregation (of component carriers), base station 102 / UE 104 can use up to [number missing] carriers. Y A spectrum with a bandwidth of MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.). Carriers may be adjacent to each other or may not be adjacent to each other. Carrier allocation may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). Component carriers may include primary component carriers and one or more secondary component carriers. The primary component carrier may be referred to as the primary cell (PCell) and the secondary component carrier may be referred to as the secondary cell (SCell).

[0051] Some UEs 104 can communicate with each other using device-to-device (D2D) communication link 158. D2D communication link 158 can use DL / UL wireless wide area network (WWAN) spectrum. D2D communication link 158 can use one or more sidelink channels, such as Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Shared Channel (PSSCH), and Physical Sidelink Control Channel (PSCCH). D2D communication can be performed through various wireless D2D communication systems, such as Bluetooth. ™ (Bluetooth is a trademark of the Bluetooth Special Interest Group (SIG), and is based on the IEEE 802.11 standard for Wi-Fi.)™ (Wi-Fi is a trademark of the Wi-Fi Alliance), LTE, or NR.

[0052] Examples of sidelink communication may include vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I) (e.g., from a vehicle-based communication device to a road infrastructure node such as a roadside unit (RSU), vehicle-to-network (V2N) (e.g., from a vehicle-based communication device to one or more network nodes such as a base station), vehicle-to-pedestrian (V2P), cellular vehicle-to-everything (C-V2X), and / or combinations thereof, and / or vehicle-based communication devices communicating with other devices; these communications can be collectively referred to as vehicle-to-everything (V2X) communication. Sidelink communication may be based on V2X or other D2D communication, such as Proximity Services (ProSe). In addition to the UE, sidelink communication may also be transmitted and received by other transmitting and receiving devices (such as a roadside unit (RSU) 407). The PC5 interface can be used to exchange sidelink communication, such as in combination with... Figure 2 The examples described in [the document] are as follows. Although including [other examples] Figure 2 The following description of an example time slot structure can provide an example of sidelink communication combined with 5G NR, but the concepts described herein are applicable to other similar fields such as LTE, LTE-A, CDMA, GSM and other wireless technologies.

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

[0054] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz to 7.125GHz) and FR2 (24.25GHz to 52.6GHz). Although a portion of FR1 is greater than 6GHz, in various documents and articles, FR1 is often (interchangeably) referred to as the "sub-6GHz" band. Similar naming issues sometimes occur with FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although this is distinct from the Extremely High Frequency (EHF) band (30GHz to 300GHz) designated as "millimeter wave" by the International Telecommunication Union (ITU).

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

[0056] In view of the above, unless otherwise specified, the term "below 6 GHz" as used herein can broadly refer to frequencies less than 6 GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise specified, the term "millimeter wave" as used herein can broadly refer to frequencies that can include intermediate frequency band frequencies, within FR2, FR4, FR2-2 and / or FR5, or within the EHF band.

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

[0058] Base station 102 may include and / or be referred to as gNB, Node B, eNB, access point, base transceiver, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmit / receive point (TRP), network node, network entity, network equipment, or some other suitable terminology. Base station 102 may be implemented as an integrated access and backhaul (IAB) node, relay node, sidelink node, aggregated (monolithic) base station with baseband units (BBU) (including CU and DU) and RU, or as a decomposed base station including one or more of CU, DU, and / or RU. A collection of base stations that may include decomposed base stations and / or aggregated base stations may be referred to as Next Generation (NG) RAN (NG-RAN).

[0059] The core network 120 may include Access and Mobility Management Function (AMF) 161, Session Management Function (SMF) 162, User Plane Function (UPF) 163, Unified Data Management (UDM) 164, one or more location servers 168, and other functional entities. AMF 161 is the 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 authentication and key agreement (AKA) credential generation, user identity processing, access authorization, and subscription management. One or more location servers 168 are exemplified as including a Gateway Mobile Location Center (GMLC) 165 and a Location Management Function (LMF) 166. However, generally, one or more location servers 168 may include one or more location / positioning servers, which may include one or more of GMLC 165, LMF 166, Position Determination Entity (PDE), Serving Mobile Location Center (SMLC), Mobile Location 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 location information. LMF 166 receives measurement and auxiliary information from NG-RAN and UE 104 via AMF 161 to calculate the location of UE 104. NG-RAN may use one or more positioning methods to determine the location of UE 104. Positioning UE 104 may involve signal measurement, location estimation, and optional speed calculation based on these measurements. Signal measurement may be performed by UE 104 and / or serving base station 102. The measured signals may be based on one or more of the following: Satellite Positioning System (SPS) 170 (e.g., one or more of Global Navigation Satellite System (GNSS), Global Positioning System (GPS), Non-Terrestrial Network (NTN) or other satellite positioning / location systems), LTE signals, Wireless Local Area Network (WLAN) signals, Bluetooth signals, Terrestrial Beacon System (TBS), sensor-based information (e.g., barometric pressure sensor, motion sensor), NR Enhanced Cell ID (NR E-CID) method, NR signals (e.g., multiple round-trip time (multiple RTT), DL departure angle (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.

[0060] Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, GPS devices, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet devices, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional device. Some UEs in UE 104 may be referred to as IoT devices (e.g., parking meters, air pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, mobile phone, user agent, mobile client, client, or some other suitable terminology. In some scenarios, the term UE may also be applied to one or more companion devices, such as in a device constellation arrangement. One or more of these devices may access the network together and / or individually.

[0061] Refer again Figure 1 In some aspects, UE 104 may include a conflict component 197 configured to: receive from a first UE a request to form a connection for sidelink communication; measure at least one conflicting sidelink transmission from at least one additional UE that interferes with the sidelink transmission from the first UE; send a sidelink conflict report to a network entity indicating the measured at least one conflicting sidelink transmission from at least one additional UE; and communicate with the first UE via sidelink communication based on resource allocation for sidelink transmission after the sidelink conflict report.

[0062] Refer again Figure 1 In some respects, UE 104 may include a sidelink component 198 configured to: receive a resource allocation for sidelink transmission from a network entity, the resource allocation including an indication of a destination ID; and transmit a sidelink transmission to a second UE based on the resource allocation for sidelink transmission and the destination ID associated with the second UE.

[0063] Refer again Figure 1 In some respects, base station 102 may include a sidelink component 199 configured to: schedule resource allocation for sidelink transmission based on at least one of a destination ID for sidelink transmission or a sidelink conflict report; and provide resource allocation for sidelink transmission to a first UE.

[0064] While 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.

[0065] Figure 2 Figures 200 and 210 illustrate example aspects of time slot structures that can be used for sidelink communication (e.g., between UE 104, RSU 407, etc.). In some examples, the time slot structure may be within a 5G / NR frame structure. In other examples, the time slot structure may be within an LTE frame structure. While the following description may focus on 5G NR, the concepts described herein may be applicable to other similar domains such as LTE, LTE-A, CDMA, GSM, and other wireless technologies. Figure 2 The example time slot structure in the diagram is merely an example, and other sidelink communications may have different frame structures and / or different channels for sidelink communication. A frame (10 ms) can be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include micro-time slots, which may include 7, 4, or 2 symbols. Each time slot may include 7 or 14 symbols, depending on the time slot configuration. For time slot configuration 0, each time slot may include 14 symbols, and for time slot configuration 1, each time slot may include 7 symbols. Figure 200 illustrates, for example, a single resource block that may correspond to a single time slot of 0.5 ms Transmission Time Interval (TTI). The physical sidelink control channel may be configured to occupy multiple physical resource blocks (PRBs), for example, 10, 12, 15, 20, or 25 PRBs. The PSCCH may be limited to a single subchannel. The PSCCH duration may be configured, for example, 2 or 3 symbols. For example, subchannels may include 10, 15, 20, 25, 50, 75, or 100 PRBs. Resources used for sidelink transmissions may be selected from a resource pool comprising one or more subchannels. As a non-limiting example, a resource pool may include between 1 and 27 subchannels. A PSCCH size may be established for the resource pool, for example, set to be between 10% and 100% of a subchannel over a duration of 2 or 3 symbols. Figure 2 Figure 210 illustrates an example where the PSCCH occupies approximately 50% of the subchannel, serving as an example to illustrate the concept of the PSCCH occupying a portion of a subchannel. The Physical Sidelink Shared Channel (PSSCH) occupies at least one subchannel. In some examples, the PSCCH may include a first portion of the Sidelink Control Information (SCI), and the PSSCH may include a second portion of the SCI.

[0066] A resource grid can be used to represent frame structure. Each time slot may include a resource block (RB) (also known as a physical RB (PRB)) extending for 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme. Figure 2 As shown, the first symbol may include resources for automatic gain control (AGC) at the receiver. Some REs may include control information from the PSCCH and some REs may include demodulation RS (DMRS). At least one symbol may be used for feedback. Figure 2 An example with two symbols for a Physical Side Link Feedback Channel (PSFCH) with adjacent gap symbols is illustrated. Symbols before and / or after the feedback can be used for the transition between data reception and feedback transmission. This gap allows a device to switch from operating as a transmitting device to preparing to operate as a receiving device, for example, in a subsequent time slot. As illustrated, data can be transmitted in the remaining RE. This data may include the data messages described herein. The positioning of any of the data, DMRS, SCI, feedback, gap symbols, and / or LBT symbols may differ. Figure 2 The example shown illustrates this. In some respects, multiple time slots can be aggregated together.

[0067] Figure 3 This is a block diagram illustrating communication between a first wireless communication device 310 and a second wireless communication device 350 via a sidelink. In some examples, devices 310 and 350 may communicate via V2X or other D2D communication. This communication may be based on a sidelink using a PC5 interface. Devices 310 and 350 may include UEs, RSUs, base stations, etc. Packets may be provided to a controller / processor 375 that implements Layer 3 and Layer 2 functionality. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the Media Access Control (MAC) layer.

[0068] 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) decoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. TX processor 316 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to OFDM subcarriers, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and then combined using inverse fast Fourier transform (IFFT) to produce a physical channel carrying a stream of time-domain OFDM symbols. The OFDM stream is spatially pre-decoded to generate multiple spatial streams. Channel estimates from channel estimator 374 can be used to determine the decoding and modulation scheme, as well as for spatial processing. The channel estimates can be derived from a reference signal transmitted by device 350 and / or channel condition feedback. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX can use the corresponding spatial stream to modulate a radio frequency (RF) carrier for transmission.

[0069] At device 350, each receiver 354RX receives a signal via its corresponding antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides that information to the receive (RX) processor 356. The TX processor 368 and 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 device 350. If multiple spatial streams are destined for device 350, the RX processor 356 can combine them into a single OFDM symbol stream. The RX processor 356 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, along with the reference signal, are recovered and demodulated by determining the signal constellation points most likely to be transmitted by device 310. These soft decisions can be based on a channel estimate calculated by the channel estimator 358. The soft decision is then decoded and deinterleaved to recover the data and control signals originally transmitted by device 310 on the physical channel. The data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functionality.

[0070] The controller / processor 359 may be associated with a memory 360 that stores program code and data. The memory 360 may be referred to as a computer-readable medium. The controller / processor 359 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transport channel and the logical channel. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0071] Similar to the functions described in conjunction with the transmissions performed by device 310, controller / processor 359 can provide RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connectivity, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with the transmission of upper-layer PDUs, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer 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 via HARQ, priority handling, and logical channel priority ordering.

[0072] The channel estimate derived by the channel estimator 358 from the reference signal or feedback transmitted by the device 310 can be used by the TX processor 368 to select an appropriate decoding and modulation scheme, as well as to facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via individual transmitters 354TX. Each transmitter 354TX can modulate an RF carrier with the corresponding spatial stream for transmission.

[0073] Transmission is processed at device 310 in a manner similar to that described for the receiver function at device 350. Each receiver 318RX receives the signal via its corresponding antenna 320. Each receiver 318RX recovers the information modulated onto the RF carrier and provides that information to the RX processor 370.

[0074] The controller / processor 375 may be associated with a memory 376 that stores program code and data. The memory 376 may be referred to as a computer-readable medium. The controller / processor 375 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transport channel and the logical channel. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0075] At least one of the TX processor 368, RX processor 356, and controller / processor 359 can be configured to perform and Figure 1 All aspects related to 198 or 197.

[0076] At least one of the TX processor 316, RX processor 370, and controller / processor 375 can be configured to combine Figure 1 The 199 was used to implement various aspects.

[0077] Figure 4 Example 400 illustrates sidelink communication between devices. This communication can be based on, including, combining... Figure 2 The time slot structure of the described aspects. For example, UE 402 may transmit a sidelink transmission 414 that can be received by UEs 404, 406, and 408. This sidelink transmission may include, for example, a control channel (e.g., PSCCH) and / or a corresponding data channel (e.g., PSSCH). The control channel may include information for decoding the data channel (e.g., sidelink control information (SCI)), which includes reservation information, such as information about time and / or frequency resources reserved for data channel transmission. For example, the SCI may indicate the number of TTIs and RBs to be occupied by data transmission. The SCI may also be used by the receiving device to avoid interference by avoiding transmission on reserved resources. UEs 402, 404, 406, and 408 are each capable of performing sidelink transmissions in addition to sidelink reception. Therefore, UEs 404, 406, and 408 are illustrated as transmitting sidelink transmissions 413, 415, 416, and 420. Sidelink transmissions 413, 414, 415, 416, and 420 can be unicast, broadcast, or multicast to nearby devices. For example, UE 404 can transmit sidelink transmissions 413 and 415 intended to be received by other UEs within range 401 of UE 404, and UE 406 can transmit sidelink transmission 416. Additionally or alternatively, RSU 407 can receive communication 418 from UEs 402, 404, 406, and 408 and / or transmit communication to these UEs. One or more of UEs 402, 404, 406, 408, or RSU 407 may include, as in combination Figure 1 The described side link component 198 and / or conflict component 197.

[0078] Sidelink communication can be based on different types or modes of resource allocation mechanisms. In a first resource allocation mode (which may be referred to herein as "Mode 1"), centralized resource allocation can be provided by a network entity. For example, base station 102 can determine resources for sidelink communication and allocate resources to different UEs 104 for sidelink transmission. In this first mode, the UE receives the sidelink resource allocation from base station 102. In a second resource allocation mode (which may be referred to herein as "Mode 2"), distributed resource allocation can be provided. In Mode 2, each UE can autonomously determine the resources for sidelink transmission. To coordinate the selection of sidelink resources by each UE, each UE can use sensing technology to monitor the resource reservations of other sidelink UEs and can select resources for sidelink transmission from unreserved resources. Devices communicating based on sidelinks can determine one or more radio resources used by other devices in the time and frequency domains in order to select transmission resources that avoid conflict with other devices. Sidelink transmission and / or resource reservation can be periodic or aperiodic, wherein a UE can reserve resources for transmission in the current time slot and up to two future time slots (as discussed below).

[0079] Therefore, in this second mode (e.g., mode 2), each UE can autonomously select resources for sidelink transmission, for example, in the absence of a central entity (such as a base station indicating resources for a device). The first UE can reserve the selected resources to notify other UEs about the resources that the first UE intends to use for sidelink transmission.

[0080] In some examples, resource selection for sidelink communication can be based on sensing mechanisms. For instance, before selecting resources for data transmission, the UE can first determine whether the resources have already been reserved by other UEs.

[0081] For example, as part of the sensing mechanism for resource allocation mode 2, the UE can determine (e.g., sense) whether the selected sidelink resource has been reserved by another UE before selecting it for data transmission. If the UE determines that the sidelink resource has not been reserved by another UE, the UE can use the selected sidelink resource for data transmission, for example, in PSSCH transmission. The UE can estimate or determine which radio resources (e.g., sidelink resources) are in use and / or reserved by other UEs by detecting and decoding sidelink control information (SCI) transmitted by other UEs. The UE can use a sensing-based resource selection algorithm to estimate or determine which radio resources are in use and / or reserved by other UEs. The UE can receive an SCI from another UE, which includes reservation information based on a resource reservation field included in the SCI. The UE continuously monitors (e.g., senses) and decodes SCIs from peer UEs. The SCI may include reservation information, for example, indicating the time slot and RB that a particular UE has selected for future transmission. The UE can exclude resources used and / or reserved by other UEs from a candidate resource set used by the UE for sidelink transmission, and the UE can select / reserve resources from unused resources that thus form the candidate resource set for sidelink transmission. The UE can continuously sense SCIs with resource reservations to maintain a candidate resource set from which it can select one or more resources for sidelink transmission. Once the UE selects candidate resources, it can transmit an SCI indicating its own reservation of resources for sidelink transmission. The amount of resources reserved by the UE (e.g., sub-channels per subframe) can depend on the size of the data to be transmitted by the UE. Although this example is described with respect to the UE receiving reservation information from another UE, reservation information can also be received from the RSU or other devices communicating via the sidelink.

[0082] In wireless communication systems, a time slot comprises 14 OFDM symbols, such as... Figure 5A The illustration 500 and Figure 5B As shown in Figure 510. The first symbol may be repeated on the previous symbol for automatic gain control (AGC) settings. In some cases, the gap symbol may exist after the Physical Side Link Shared Channel (PSSCH). The Physical Side Link Control Channel (PSCCH) and PSSCH may be transmitted in the same time slot. In some cases, the Physical Side Link Feedback Channel (PSFCH) may be transmitted in the last two symbols of the time slot.

[0083] In wireless communication systems (e.g., sidelink communication systems), mode 1 and mode 2 resource allocation configurations can be utilized. For example, refer to... Figure 6AAs shown in Figure 600, in the Mode 1 resource allocation configuration, base station 604 can allocate resources for sidelink data channel transmission to transmitting UE 602. Base station 604 can schedule sidelink transmissions for UE 602 via DCI format 3_0 with CRC scrambled using SL-RNTI. UE 602 transmits PSCCH / PSSCH to UE 606 in the time slot determined by the time slot field in the scheduling DCI. UE 602 can use HARQ information (e.g., HPID, NDI), FDRA, or TDRA in the scheduling DCI. Transmitting UE 602 can receive the allocated resources from base station 604 via the Uu link. Transmitting UE 602 can transmit sidelink transmissions to receiving UE 606 via a sidelink connection (e.g., PC5). If HARQ feedback is enabled, transmitting UE 602 can receive HARQ feedback from receiving UE 606 via PSFCH. UE 602 can provide HARQ feedback to base station 604 via PUCCH resources indicated by the scheduling DCI.

[0084] refer to Figure 6B As shown in Figure 610, in the Mode 2 resource allocation configuration, the transmitting UE 612 can autonomously perform resource allocation for sidelink transmission with the receiving UE 614. Mode 2 supports reservation-based scheduling. The transmitting UE 612 can reserve multiple resources in multiple future time slots for future transmission. The reservation can be indicated in the Sidelink Control Information (SCI). The transmitting UE 612 can make reservations based on monitoring of sidelink transmissions from other UEs.

[0085] In FR1, the side-link UE can use an omnidirectional antenna to transmit and receive PSCCH / PSSCH, such as Figure 7 As shown in Figure 700. Figure 7 As shown, a sidelink transmission from a sidelink UE can be received by all sidelink UEs in the same area. The base station (e.g., TRP1 or TRP2) can utilize orthogonal resources (such as in different time slots or sub-channels) to schedule sidelink transmissions from multiple sidelink UEs to avoid conflicts between sidelink transmissions.

[0086] In some cases, a sidelink UE can indicate sidelink information to the network (e.g., SidelinkUEInformationNR). A sidelink UE can indicate or send sidelink information after receiving system information (e.g., SIB12), such as... Figure 8As shown in Figure 800. In some cases, sidelink information can indicate the sidelink destination for sidelink transmission. The sidelink UE can indicate up to 32 sidelink destinations for sidelink transmission. As an example, the UE can provide a list or index of destinations, such as in sl-TxResourceReqList-r16. The purpose of this process is to notify the network that the UE is interested in or no longer interested in receiving or transmitting NR sidelink communication, request the assignment or release of transmission resources for NR sidelink communication, report QoS parameters and QoS profiles related to NR sidelink communication, report that a sidelink radio link failure or sidelink RRC reconfiguration failure has been detected, report the sidelink UE capability information of the associated peer UE for unicast communication, or report the RLC mode information of the sidelink data radio bearer received from the associated peer UE for unicast communication.

[0087] In FR2 sidelink operation, the sidelink UE utilizes beams to transmit and receive sidelink data. Beam pairs can be established / maintained with sidelink UEs that have unicast connections. Several aspects presented in this paper contribute to achieving accurate sidelink communication, such as unicast sidelink communication in FR2. References Figure 9 As shown in Figure 900, UE1 and UE2 have established a sidelink connection, while UE3 and UE4 have also established a sidelink connection. The network (e.g., the base station) can schedule sidelink transmissions from UE1 to UE2 and from UE4 to UE3 in the same time slot / subchannel. For the parallel scheduling of multiple SL transmissions in the same time slot / subchannel, the network can be aware of potential conflicts between sidelink transmissions between different UE pairs. For example, if UE1 sends a sidelink transmission to UE2 and UE3 sends a sidelink transmission to UE4, there is a possibility of a conflict occurring when transmissions occur at the same time and / or in the same subchannel. In some cases, if UE4 sends a sidelink transmission to UE3 and UE1 sends a sidelink transmission to UE2, the possibility of a conflict may be minimal, partly due to the lack of beam power between UE4 and UE2. As discussed herein, each sidelink UE in the area can receive PSCCH / PSSCH due to the full-antenna sidelink transmission / reception in FR1. For the network, beamforming of the control side link transmission will be beneficial to increase the scheduling opportunities for parallel transmission of SL transmit / receive using beamforming in FR2.

[0088] The aspects presented herein provide configurations for enhanced resource allocation for sidelink mode 1 operation. For example, this configuration allows the network to schedule multiple sidelink transmissions in the same time slot and subchannel. The network can schedule multiple sidelink transmissions based on at least one of the destination ID for the sidelink transmission or a sidelink conflict report. The network can obtain information related to the destination ID from the transmitting UE and information related to the sidelink conflict report from the receiving UE.

[0089] In some respects, Mode 1 sidelink scheduling can be based on the destination ID. The scheduled sidelink resources can specify Enhanced Resource Allocation Mode 1 in FR2, in which the network (e.g., the base station) schedules PSCCH / PSSCH to the sidelink UE using the destination ID transmitted by the PSCCH / PSSCH. For omnidirectional antennas or transmissions, DCI Format 3_0 does not include an indication of the destination ID, e.g., each UE in the area can receive either PSCCH or PSSCH. As presented herein, the destination ID can be indicated in sidelink information (e.g., an index in sl-TxResourceReqList-r16 reported to the network by the UE). For beamforming sidelink communication, compared to omnidirectional sidelink communication, the network can use information about the destination to increase the opportunity to schedule parallel transmissions based on beamforming control. The size of the “Destination ID” field in DCI Format 3_0 can be determined based on the size of the destination list (e.g., the size of sl-TxResourceReqList-r16 indicated by the UE or the number of destinations). Sidelink UEs may be allowed to transmit PSCCH / PSSCH only to sidelink UEs associated with the indicated destination ID, utilizing corresponding transmit beamforming. In some aspects, when parallel sidelink scheduling is not present, the network may indicate the destination ID as "any". In such cases, any sidelink UE may receive sidelink transmissions, provided that such sidelink UE has a unicast connection to the transmitting UE or is paired with the transmitting UE.

[0090] In some aspects, Mode 1 sidelink scheduling may be based on sidelink conflict reports with a destination ID. Sidelink UEs may report sidelink conflicts from other sidelink UEs to the network (e.g., a base station) to assist in the scheduling of SL transmissions. In some aspects, a new MAC-CE for sidelink conflict reporting from UEs to the network may be utilized. Sidelink conflict reports from sidelink UEs may include at least one of the following: a resource pool associated with sidelink reception, a target connection ID for the expected sidelink reception, and a list of K sidelink interfering UE information, where each interfering UE information includes the interfering source connection ID and the interference level. In some cases, the network configures a maximum number of interfering UE information to be reported for sidelink conflict reporting, but the actual number of interfering UE information to be reported may be determined by the sidelink UE based on measurements. In some aspects, the target connection ID may be indicated by an index in sl-TxResourceReqList-r16. In some aspects, the transmitter of the target connection is an SL UE identified by sl-DestinationIdentity-r16.

[0091] When Enhanced Resource Allocation Mode 1 is configured for the SL resource pool, the interfering UE connection ID can be indicated by the {source ID, destination ID} transmitted by the interfering UE sidelink. Sidelink transmissions from a sidelink UE with a “source ID” to a sidelink UE with a “destination ID” can include interfering UE connections. The interference level can be indicated relative to a range having a first threshold 1002 and a second threshold 1004, such as, for example... Figure 10 As shown in Figure 1000. For example, the interference level is indicated as one of the following: below a first threshold, within a range between the first and second thresholds, or above the second threshold. In some aspects, the interference level may be indicated as "similar" or "high" with reference to the first and second thresholds. For example, when the interference level is "similar" (e.g., 1010), it is expected that the network will avoid scheduling the target connection and the interfering connection in the same time slot / subchannel. In the case of an interference level of "high" (e.g., 1012), it is expected that the network will avoid scheduling the target connection and the interfering connection in the same time slot. In the case of an interference level of "negligible" (e.g., 1008), the UE (e.g., target connection 1006) may not include the interfering connection in the SL conflict report.

[0092] In some aspects, sidelink conflict reports may not include the destination ID. In such cases, when resource allocation mode 1 is configured for the sidelink resource pool, the interfering connection ID can be indicated by the "source ID" transmitted by the interfering UE. Any sidelink transmission from a sidelink UE with the "source ID" can be considered an interfering connection. The interference level can be indicated as "similar" or "high" as discussed above. When the interference level is "similar," the network is expected to avoid scheduling the target connection and the interfering connection in the same time slot / subchannel. When the interference level is "high," the network is expected to avoid scheduling the target connection and the interfering connection in the same time slot. When the interference level is "negligible," the target UE does not report the interfering connection in the sidelink conflict report.

[0093] Sidelink conflict reports can be configured to be sent periodically or in response to a triggering event. Any change in an interfering connection (e.g., interfering connection ID or interference level) can be an event that triggers the transmission of a sidelink conflict report. Sidelink conflict reports can be based on PSCCH-RSRP or PSSCH-RSRP. The destination UE or the UE sending the sidelink conflict report can decode SCI2 to identify the source ID and destination ID of the received PSCCH / PSSCH. The threshold used to determine the interference level depends on the sidelink UE's decision. For example, the threshold for "negligible interference source" can be determined based on the acceptable interference level associated with the rank / MCS of the target connection. In another example, the threshold for "high interference source" can be determined based on the AGC / quantization noise tolerance of the sidelink UE receiver associated with the rank / MCS of the target connection.

[0094] Figure 11 This is a call flow diagram 1100 showing the signaling between a first wireless device 1102, a second wireless device 1104, and a network entity 1106. The first wireless device 1102 can be a first sidelink UE, and the second wireless device 1104 can be a second sidelink UE. The first wireless device 1102 and the second wireless device 1104 can communicate with each other via sidelink communication. The first sidelink UE and the second sidelink UE can be configured to communicate with a network entity (e.g., a base station). For example, in... Figure 1 In the context of [the above], the first UE or the second UE may each correspond to at least UE 104, and network entity 1106 may correspond to base station 102. In another example, [the following is a separate, unrelated example:] Figure 3 In the context of this, network entity 1106 may correspond to device 310, and the first UE or the second UE may correspond to device 350.

[0095] At 1108, the first radio device 1102 may send a sidelink indication to the network entity 1106. The network entity 1106 may obtain the sidelink indication from the first radio device. The first radio device may send the sidelink indication to the network entity before receiving resource allocation for sidelink transmission. The sidelink indication may indicate sidelink scheduling that utilizes the destination ID of the second UE and supports at least sidelink transmission.

[0096] At 1110, the second wireless device 1104 may send a sidelink indication to the network entity 1106. The network entity 1106 may obtain the sidelink indication from the second wireless device 1104. The sidelink indication from the second wireless device may indicate at least support for sidelink transmissions and sidelink conflict reports. In some aspects, resource allocation mode 1 may be configured for a sidelink resource pool, and the sidelink conflict report may include the source ID of a conflicting sidelink transmission from at least different wireless devices, which may conflict with a sidelink transmission from the first wireless device using selected or anticipated resources. In some aspects, the interference level may be based on at least one of the following: the maximum RSRP of all sidelink transmissions from the sidelink wireless device associated with the source ID, or the average RSRP of all sidelink transmissions from the sidelink wireless device associated with the source ID.

[0097] At 1112, the first wireless device 1102 may send a request to the second wireless device 1104 to establish a connection for sidelink communication. The second wireless device 1104 may receive the request to establish a connection for sidelink communication from the first wireless device 1102.

[0098] At 1114, the first wireless device 1102 may send a request to network entity 1106 for resource allocation for sidelink transmission with the second wireless device 1104. Network entity 1106 may obtain the request for resource allocation for sidelink transmission with the second wireless device from the first wireless device. The request for resource allocation for sidelink transmission may include a destination ID associated with the second wireless device. The first wireless device may send the request for resource allocation for sidelink transmission with the second wireless device in response to sending a request to the second wireless device for sidelink communication with the second wireless device.

[0099] At 1116, the second wireless device 1104 can measure at least one conflicting sidelink transmission from at least one additional wireless device or a different wireless device that interferes with the sidelink transmission from the first wireless device. The measured at least one conflicting sidelink transmission may correspond to one or more anticipated conflicts from at least one additional wireless device or a different wireless device, which may conflict with a sidelink transmission from the first wireless device utilizing selected or anticipated resources for the sidelink transmission from the first wireless device.

[0100] At 1118, the second wireless device 1104 may send a sidelink conflict report to network entity 1106, the sidelink conflict report indicating at least one conflicting sidelink transmission measured from at least one additional wireless device or different wireless devices. Network entity 1106 may obtain the sidelink conflict report from the second wireless device 1104. In some aspects, for each of the at least one additional wireless device or different wireless devices, the sidelink conflict report may include one or more of the following: a connection ID associated with the conflicting sidelink communication, or an interference level of the conflicting sidelink communication. In some aspects, the sidelink conflict report may include at least one of the following: a resource pool associated with a sidelink reception at the second wireless device, or a target connection ID of a sidelink transmission from the first wireless device. In some aspects, the connection ID may include the source ID of the conflicting sidelink transmission and the destination ID of the receiver of the conflicting sidelink communication. In some aspects, the connection ID may include the source ID of the conflicting sidelink transmission. In some aspects, the interference level may be indicated based on relative RSRP values ​​measured on the target connection and the conflicting connection. The interference level may be indicated relative to a range having a first threshold and a second threshold. The interference level can be indicated as one of the following: below a first threshold, within a range between the first and second thresholds, or above the second threshold. In some aspects, the transmission of sidelink conflict reports can be periodic. In other aspects, the transmission of sidelink conflict reports can be non-periodic reports in response to triggering events.

[0101] At 1120, network entity 1106 can schedule resource allocation for sidelink transmissions. Network entity 1106 can schedule resource allocation for sidelink transmissions based on at least one of a destination ID for a sidelink transmission obtained from the first wireless device 1102 or a sidelink conflict report for a sidelink transmission obtained from the second wireless device 1104. In some aspects, the destination ID can indicate that the scheduled sidelink transmission is for a specific wireless device, causing the first wireless device to send a sidelink transmission to the wireless device associated with the destination ID. In some aspects, the resource allocation can include the destination ID of the second wireless device 1104. In some aspects, the destination ID can indicate that the scheduled sidelink transmission is for any sidelink wireless device having a unicast connection to the first wireless device.

[0102] At 1122, network entity 1106 may provide resource allocation for sidelink transmission to first wireless device 1102. First wireless device 1102 may receive resource allocation for sidelink transmission from network entity 1106.

[0103] At 1124, the first wireless device 1102 and the second wireless device 1104 can communicate with each other via sidelink communication. For example, the first wireless device 1102 can send a sidelink transmission to the second wireless device 1104 based on resource allocation for sidelink transmission and a destination ID associated with the second wireless device. The second wireless device can receive the sidelink transmission from the first wireless device. In some aspects, the sidelink transmission with the second wireless device having a destination ID can be beamforming transmission. The second wireless device 1104 can communicate with the first wireless device 1102 via sidelink communication based on resource allocation for sidelink transmission after sending a sidelink collision report to network entity 1106.

[0104] Figure 12 This is a flowchart 1200 of a method for wireless communication at a first UE. This method can be performed by a UE (e.g., UE 104; device 1404). One or more of the illustrated operations may be omitted, interchanged, or performed simultaneously. This method allows the UE to transmit sidelink data with a second UE based on a resource allocation for sidelink transmission having a destination ID associated with the second UE.

[0105] At 1202, the first UE may receive a resource allocation for sidelink transmission. For example, 1202 may be performed by the sidelink component 198 of apparatus 1404. The first UE may receive the resource allocation for sidelink transmission from a network entity. The resource allocation may include an indication of a destination ID. In some aspects, the destination ID may indicate that the scheduled sidelink transmission is for a specific UE, causing the first UE to transmit the sidelink transmission to the UE associated with the destination ID. In some aspects, the destination ID may indicate that the scheduled sidelink transmission is for any sidelink UE with a unicast connection to the first UE.

[0106] At 1204, the first UE may send a sidelink transmission to the second UE. For example, 1204 may be performed by the sidelink component 198 of device 1404. The first UE may send the sidelink transmission to the second UE based on resource allocation for the sidelink transmission and a destination ID associated with the second UE. In some aspects, the sidelink transmission with the second UE having a destination ID may be a beamforming transmission.

[0107] Figure 13 This is a flowchart 1300 of a method for wireless communication at a first UE. This method can be performed by a UE (e.g., UE 104; device 1404). One or more of the illustrated operations may be omitted, interchanged, or performed simultaneously. This method allows the UE to transmit sidelink data with a second UE based on a resource allocation for sidelink transmission having a destination ID associated with the second UE.

[0108] At 1302, the first UE may send a sidelink indication to the network entity. For example, 1302 may be performed by the sidelink component 198 of device 1404. The UE may send the sidelink indication to the network entity before receiving resource allocation for sidelink transmission. The sidelink indication may indicate sidelink scheduling that at least supports sidelink transmission using the destination ID of the second UE.

[0109] At 1304, the first UE may send a request for resource allocation for sidelink transmission with the second UE. For example, 1304 may be performed by the sidelink component 198 of device 1404. The request for resource allocation for sidelink transmission may include a destination ID associated with the second UE. The first UE may send the request for resource allocation for sidelink transmission with the second UE in response to sending a request to the second UE for sidelink communication with the second UE.

[0110] At 1306, the first UE may receive a resource allocation for sidelink transmission. For example, 1306 may be performed by the sidelink component 198 of apparatus 1404. The first UE may receive the resource allocation for sidelink transmission from a network entity. The resource allocation may include an indication of a destination ID. In some aspects, the destination ID may indicate that the scheduled sidelink transmission is for a specific UE, causing the first UE to transmit the sidelink transmission to the UE associated with the destination ID. In some aspects, the destination ID indicates that the scheduled sidelink transmission is for any sidelink UE with a unicast connection to the first UE.

[0111] At 1308, the first UE may send a sidelink transmission to the second UE. For example, 1308 may be performed by the sidelink component 198 of device 1404. The first UE may send the sidelink transmission to the second UE based on resource allocation for the sidelink transmission and a destination ID associated with the second UE. In some aspects, the sidelink transmission with the second UE having a destination ID may be a beamforming transmission.

[0112] Figure 14Figure 1400 illustrates an example of a hardware implementation for device 1404. Device 1404 may be a UE, a component of a UE, or implement UE functionality. In some aspects, device 1404 may include a cellular baseband processor 1424 (also referred to as a modem) coupled to one or more transceivers 1422 (e.g., cellular RF transceivers). Cellular baseband processor 1424 may include on-chip memory 1424'. In some aspects, device 1404 may also include one or more Subscriber Identity Module (SIM) cards 1420 and an application processor 1406 coupled to a Secure Digital Card (SD) card 1408 and a screen 1410. Application processor 1406 may include on-chip memory 1406'. In some aspects, device 1404 may also include a Bluetooth module 1412, a WLAN module 1414, an SPS module 1416 (e.g., a GNSS module), one or more sensor modules 1418 (e.g., a barometric pressure sensor / altimeter; motion sensors such as an inertial measurement unit (IMU), gyroscope, and / or accelerometer; light detection and ranging (LIDAR), radio-assisted detection and ranging (RADAR), sound navigation and ranging (SONAR), magnetometer, audio, and / or other technologies for positioning), an additional memory module 1426, a power source 1430, and / or a camera 1432. Bluetooth module 1412, WLAN module 1414, and SPS module 1416 may include on-chip transceivers (TRX) (or in some cases, only receivers (RX)). Bluetooth module 1412, WLAN module 1414, and SPS module 1416 may include their own dedicated antennas and / or communicate using antenna 1480. Cellular baseband processor 1424 communicates with UE 104 and / or RU associated with the same network entity 1402 via transceiver 1422 through one or more antennas 1480. Cellular baseband processor 1424 and application processor 1406 may each include computer-readable media / memory 1424', 1406' respectively. Additional memory module 1426 may also be considered as computer-readable media / memory. Each computer-readable media / memory 1424', 1406', 1426 may be non-transitory. Cellular baseband processor 1424 and application processor 1406 are each responsible for general processing, including executing software stored on the computer-readable media / memory. When executed by cellular baseband processor 1424 / application processor 1406, the software causes cellular baseband processor 1424 / application processor 1406 to perform the various functions described above. Cellular baseband processor 1424 and application processor 1406 are configured to perform the various functions described above based at least in part on information stored in memory.In other words, the cellular baseband processor 1424 and application processor 1406 can be configured to perform a first subset of the various functions described above without information stored in memory, and can be configured to perform a second subset of the various functions described above based on information stored in memory. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 1424 / application processor 1406 during software execution. The cellular baseband processor 1424 / application processor 1406 can be a component of device 350 and can include memory 360 and / or at least one of TX processor 368, RX processor 356, and controller / processor 359. In one configuration, device 1404 can be a processor chip (modem and / or application) and includes only the cellular baseband processor 1424 and / or application processor 1406, and in another configuration, device 1404 can be the entire UE (e.g., see below). Figure 3 (350) and includes an additional module of device 1404.

[0113] As discussed above, component 198 is configured to: receive a resource allocation for sidelink transmission from a network entity, the resource allocation including an indication of a destination ID; and transmit a sidelink transmission to a second UE based on the resource allocation for sidelink transmission and the destination ID associated with the second UE. Component 198 may be within cellular baseband processor 1424, application processor 1406, or both cellular baseband processor 1424 and application processor 1406. Component 198 may be one or more hardware components specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to execute the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. As shown, apparatus 1404 may include various components configured for various functions. In one configuration, apparatus 1404 (and specifically, cellular baseband processor 1424 and / or application processor 1406) includes a component for receiving a resource allocation for sidelink transmission from a network entity, the resource allocation including an indication of a destination ID. The apparatus includes components for sending a sidelink transmission to a second UE based on resource allocation for sidelink transmission and a destination ID associated with the second UE. The apparatus also includes components for sending a request for resource allocation for sidelink transmission with the second UE, wherein the request includes a destination ID associated with the second UE. The component may be component 198 of apparatus 1404 configured to perform the functions described therein. As described above, apparatus 1404 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Therefore, in one configuration, the component may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions described therein.

[0114] Figure 15 This is a flowchart 1500 of a method for wireless communication at a second UE. This method can be performed by a UE (e.g., UE 104; device 1704). One or more of the illustrated operations can be omitted, interchanged, or performed simultaneously. This method allows the UE to provide a sidelink collision report indicating at least one conflicting sidelink transmitted from another sidelink UE.

[0115] At point 1502, the second UE may receive a request to establish a connection for sidelink communication. For example, 1502 may be executed by the collision component 197 of device 1704. The second UE may receive the request to establish a connection for sidelink communication from the first UE.

[0116] At 1504, the second UE can measure at least one conflicting sidelink transmission. For example, 1504 can be performed by the conflict component 197 of device 1704. The second UE can measure at least one conflicting sidelink transmission from at least one additional UE that interferes with the sidelink transmission from the first UE. The measured at least one conflicting sidelink transmission may correspond to one or more anticipated conflicts from at least one additional UE, which may conflict with a sidelink transmission from the first UE utilizing selected or anticipated resources for the sidelink transmission from the first UE.

[0117] At 1506, the second UE may send a sidelink conflict report indicating the measured sidelink transmission from at least one conflicting sidelink of at least one additional UE. For example, 1506 may be performed by the conflict component 197 of apparatus 1704. The second UE may send the sidelink conflict report to a network entity. In some aspects, for each of the at least one additional UE, the sidelink conflict report may include one or more of the following: a connection ID associated with the conflicting sidelink communication, or an interference level of the conflicting sidelink communication. In some aspects, the sidelink conflict report may also include at least one of the following: a resource pool associated with the sidelink reception at the second UE, or a target connection ID from the sidelink transmission of the first UE. In some aspects, the connection ID may include the source ID of the conflicting sidelink transmission and the destination ID of the receiver of the conflicting sidelink communication. In some aspects, the connection ID may include the source ID of the conflicting sidelink transmission. In some aspects, the interference level may be indicated based on relative RSRP values ​​measured on the target connection and the conflicting connection. The interference level may be indicated relative to a range having a first threshold and a second threshold. The interference level can be indicated as one of the following: below a first threshold, within a range between the first and second thresholds, or above the second threshold. In some aspects, the transmission of sidelink conflict reports can be periodic. In other aspects, the transmission of sidelink conflict reports can be non-periodic reports in response to triggering events.

[0118] At point 1508, the second UE can communicate via sidelink communication. For example, 1508 can be performed by the collision component 197 of device 1704. The second UE can communicate with the first UE via sidelink communication based on the resource allocation for sidelink transmission after sending a sidelink collision report.

[0119] Figure 16 This is a flowchart 1600 of a wireless communication method. This method can be performed by a UE (e.g., UE 104; device 1704). One or more of the illustrated operations can be omitted, interchanged, or performed simultaneously. This method allows the UE to provide a sidelink conflict report indicating that it was transmitted from at least one conflicting sidelink from another sidelink UE.

[0120] At 1602, the second UE may send a sidelink indication to the network entity. For example, 1602 may be performed by the collision component 197 of apparatus 1704. The sidelink indication may indicate support for at least sidelink collision reports for sidelink transmission. In some aspects, resource allocation mode 1 may be configured for a sidelink resource pool, and the sidelink collision report may include the source ID of the conflicting sidelink transmission. In some aspects, the interference level may be based on at least one of the following: the maximum RSRP of all sidelink transmissions from the sidelink UE associated with the source ID, or the average RSRP of all sidelink transmissions from the sidelink UE associated with the source ID.

[0121] At 1604, the second UE may receive a request to establish a connection for sidelink communication. For example, 1604 may be executed by the collision component 197 of device 1704. The second UE may receive the request to establish a connection for sidelink communication from the first UE.

[0122] At 1606, the second UE can measure at least one conflicting sidelink transmission. For example, 1606 can be performed by the conflict component 197 of the apparatus 1704. The second UE can measure at least one conflicting sidelink transmission from at least one additional UE that interferes with the sidelink transmission from the first UE. The measured at least one conflicting sidelink transmission may correspond to one or more anticipated conflicts from at least one additional UE, which may conflict with a sidelink transmission from the first UE utilizing selected or anticipated resources for the sidelink transmission from the first UE.

[0123] At 1608, the second UE may send a sidelink conflict report indicating the measured sidelink transmission from at least one conflicting sidelink of at least one additional UE. For example, 1608 may be performed by the conflict component 197 of apparatus 1704. The second UE may send the sidelink conflict report to a network entity. In some aspects, for each of the at least one additional UE, the sidelink conflict report may include one or more of the following: a connection ID associated with the conflicting sidelink communication, or an interference level of the conflicting sidelink communication. In some aspects, the sidelink conflict report may also include at least one of the following: a resource pool associated with the sidelink reception at the second UE, or a target connection ID from the sidelink transmission of the first UE. In some aspects, the connection ID may include the source ID of the conflicting sidelink transmission and the destination ID of the receiver of the conflicting sidelink communication. In some aspects, the connection ID may include the source ID of the conflicting sidelink transmission. In some aspects, the interference level may be indicated based on relative RSRP values ​​measured on the target connection and the conflicting connection. The interference level may be indicated relative to a range having a first threshold and a second threshold. The interference level can be indicated as one of the following: below a first threshold, within a range between the first and second thresholds, or above the second threshold. In some aspects, the transmission of sidelink conflict reports can be periodic. In other aspects, the transmission of sidelink conflict reports can be non-periodic reports in response to triggering events.

[0124] At 1610, the second UE can communicate via sidelink communication. For example, 1508 can be performed by the collision component 197 of device 1704. The second UE can communicate with the first UE via sidelink communication based on the resource allocation for sidelink transmission after sending a sidelink collision report.

[0125] Figure 17Figure 1700 illustrates an example of a hardware implementation for device 1704. Device 1704 may be a UE, a component of a UE, or implement UE functionality. In some aspects, device 1704 may include a cellular baseband processor 1724 (also referred to as a modem) coupled to one or more transceivers 1722 (e.g., cellular RF transceivers). Cellular baseband processor 1724 may include on-chip memory 1724'. In some aspects, device 1704 may also include one or more Subscriber Identity Module (SIM) cards 1720 and an application processor 1706 coupled to a Secure Digital Card (SD) card 1708 and a screen 1710. Application processor 1706 may include on-chip memory 1706'. In some aspects, device 1704 may also include a Bluetooth module 1712, a WLAN module 1714, an SPS module 1716 (e.g., a GNSS module), one or more sensor modules 1718 (e.g., a barometric pressure sensor / altimeter; motion sensors such as an inertial measurement unit (IMU), gyroscope, and / or accelerometer; light detection and ranging (LIDAR), radio-assisted detection and ranging (RADAR), sound navigation and ranging (SONAR), magnetometer, audio, and / or other technologies for positioning), an additional memory module 1726, a power source 1730, and / or a camera 1732. Bluetooth module 1712, WLAN module 1714, and SPS module 1716 may include on-chip transceivers (TRX) (or in some cases, only receivers (RX)). Bluetooth module 1712, WLAN module 1714, and SPS module 1716 may include their own dedicated antennas and / or communicate using antenna 1780. Cellular baseband processor 1724 communicates with UE 104 and / or RU associated with the same network entity 1702 via transceiver 1722 through one or more antennas 1780. Cellular baseband processor 1724 and application processor 1706 may each include computer-readable media / memory 1724', 1706' respectively. An additional memory module 1726 may also be considered a computer-readable media / memory. Each computer-readable media / memory 1724', 1706', 1726 may be non-transitory. Cellular baseband processor 1724 and application processor 1706 are each responsible for general processing, including executing software stored on the computer-readable media / memory. When executed by cellular baseband processor 1724 / application processor 1706, the software causes cellular baseband processor 1724 / application processor 1706 to perform the various functions described above. Cellular baseband processor 1724 and application processor 1706 are configured to perform the various functions described above based at least in part on information stored in memory.In other words, the cellular baseband processor 1724 and application processor 1706 can be configured to perform a first subset of the various functions described above without information stored in memory, and can be configured to perform a second subset of the various functions described above based on information stored in memory. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 1724 / application processor 1706 during software execution. The cellular baseband processor 1724 / application processor 1706 can be a component of device 350 and can include memory 360 and / or at least one of TX processor 368, RX processor 356, and controller / processor 359. In one configuration, device 1704 can be a processor chip (modem and / or application) and includes only the cellular baseband processor 1724 and / or application processor 1706, and in another configuration, device 1704 can be the entire UE (e.g., see below). Figure 3 (350) and includes an additional module of device 1704.

[0126] As discussed above, component 197 is configured to: receive from a first UE a request to form a connection for sidelink communication; measure at least one conflicting sidelink transmission from at least one additional UE that interferes with the sidelink transmission from the first UE; send a sidelink conflict report to a network entity, the sidelink conflict report indicating the measured at least one conflicting sidelink transmission from at least one additional UE; and communicate with the first UE via sidelink communication based on resource allocation for sidelink transmission after the sidelink conflict report. Component 197 may be within cellular baseband processor 1724, application processor 1706, or both cellular baseband processor 1724 and application processor 1706. Component 197 may be one or more hardware components specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to perform the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. As shown, apparatus 1704 may include a variety of components configured for various functions. In one configuration, apparatus 1704 (and specifically, cellular baseband processor 1724 and / or application processor 1706) includes components for receiving a request from a first UE to form a connection for sidelink communication. The apparatus includes components for measuring at least one conflicting sidelink transmission from at least one additional UE that interferes with the sidelink transmission from the first UE. The apparatus includes components for sending a sidelink conflict report to a network entity, the sidelink conflict report indicating the measured at least one conflicting sidelink transmission from at least one additional UE. The apparatus includes components for communicating with the first UE via sidelink communication based on resource allocation for sidelink transmission after the sidelink conflict report. The apparatus also includes components for sending a sidelink indication to a network entity indicating that at least the sidelink conflict report for sidelink transmission is supported. The component may be component 197 of apparatus 1704 configured to perform the functions described therein. As described above, apparatus 1704 may include TX processor 368, RX processor 356, and 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 described therein.

[0127] Figure 18 This is a flowchart 1800 of a wireless communication method. The method can be performed by a base station (e.g., base station 102; network entities 1402, 1702, 2002). One or more of the illustrated operations can be omitted, interchanged, or performed simultaneously. This method allows the network to schedule multiple sidelink transmissions in the same time slot and subchannel.

[0128] At 1802, the network entity may schedule resource allocation for sidelink transmissions. For example, 1802 may be performed by the sidelink component 199 of network entity 2002. The network entity may schedule resource allocation for sidelink transmissions based on at least one of a destination ID for the sidelink transmission or a sidelink conflict report. In some aspects, the destination ID may indicate that the scheduled sidelink transmission is for a specific UE, such that a first UE sends a sidelink transmission to a UE associated with the destination ID. In some aspects, the resource allocation may include the destination ID of a second UE. In some aspects, the destination ID may indicate that the scheduled sidelink transmission is for any sidelink UE with a unicast connection to the first UE.

[0129] At 1804, the network entity can provide resource allocation for sidelink transmission. For example, 1804 can be performed by the sidelink component 199 of network entity 2002. The network entity can provide resource allocation for sidelink transmission to the first UE.

[0130] Figure 19 This is a flowchart 1900 of a wireless communication method. The method can be performed by a base station (e.g., base station 102; network entities 1402, 1702, 2002). One or more of the illustrated operations can be omitted, interchanged, or performed simultaneously. This method allows the network to schedule multiple sidelink transmissions in the same time slot and subchannel.

[0131] At point 1902, the network entity can obtain a sidelink indication. For example, 1902 can be performed by the sidelink component 199 of network entity 2002. The sidelink indication can indicate at least one of supporting sidelink scheduling using the destination ID or a sidelink conflict report sent for a sidelink.

[0132] At point 1904, the network entity can obtain a sidelink conflict report indicating the measurement of a conflicting sidelink transmission from at least one additional UE. For example, 1904 can be performed by the sidelink component 199 of network entity 2002. The network entity can obtain the sidelink conflict report from a second UE. For each of the at least one additional UE, the sidelink conflict report may include one or more of the following: a connection ID associated with the conflicting sidelink communication, or the interference level of the conflicting sidelink communication. The sidelink conflict report may also include at least one of the following: a resource pool associated with sidelink reception, or a target connection ID of the sidelink transmission from the first UE. The connection ID may include the source ID of the conflicting sidelink transmission and the destination ID of the receiver of the conflicting sidelink transmission. The connection ID may be based on the source ID of the conflicting sidelink transmission.

[0133] At point 1906, the network entity may schedule resource allocations for sidelink transmissions. For example, 1906 may be performed by the sidelink component 199 of network entity 2002. The network entity may schedule resource allocations for sidelink transmissions based on at least one of a destination ID for the sidelink transmission or a sidelink conflict report. In some aspects, the destination ID may indicate that the scheduled sidelink transmission is for a specific UE, such that a first UE sends a sidelink transmission to a UE associated with the destination ID. In some aspects, the resource allocation may include the destination ID of a second UE. In some aspects, the destination ID may indicate that the scheduled sidelink transmission is for any sidelink UE with a unicast connection to the first UE.

[0134] At point 1908, the network entity can provide resource allocation for sidelink transmission. For example, 1908 can be performed by the sidelink component 199 of network entity 2002. The network entity can provide resource allocation for sidelink transmission to the first UE.

[0135] Figure 20Figure 2000 illustrates an example of a hardware implementation for network entity 2002. Network entity 2002 may be a BS, a component of a BS, or implement BS functionality. Network entity 2002 may include at least one of CU 2010, DU 2030, or RU 2040. For example, depending on the layer functionality handled by component 199, network entity 2002 may include CU 2010; both CU 2010 and DU 2030; each of CU 2010, DU 2030, and RU 2040; DU 2030; both DU 2030 and RU 2040; or RU 2040. CU 2010 may include at least one CU processor 2012. CU processor 2012 may include on-chip memory 2012'. In some aspects, CU 2010 may also include an additional memory module 2014 and a communication interface 2018. CU2010 communicates with DU 2030 via a midhaul link (such as an F1 interface). DU 2030 may include at least one DU processor 2032. DU processor 2032 may include on-chip memory 2032'. In some aspects, DU 2030 may also include an additional memory module 2034 and a communication interface 2038. DU 2030 communicates with RU 2040 via a fronthaul link. RU 2040 may include at least one RU processor 2042. RU processor 2042 may include on-chip memory 2042'. In some aspects, RU 2040 may also include an additional memory module 2044, one or more transceivers 2046, an antenna 2080, and a communication interface 2048. RU 2040 communicates with UE 104. On-chip memories 2012', 2032', 2042' and additional memory modules 2014, 2034, 2044 may each be considered as computer-readable media / memory. Each computer-readable medium / memory can be non-transitory. Each of processors 2012, 2032, and 2042 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the corresponding processor, the software causes the processor to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the processor while executing the software.

[0136] As discussed above, component 199 may be configured to: schedule resource allocation for sidelink transmission based on at least one of a destination ID for sidelink transmission or a sidelink conflict report; and provide the resource allocation for sidelink transmission to a first UE. Component 199 may be located within one or more processors of one or more of CU 2010, DU 2030, and RU 2040. Component 199 may be one or more hardware components specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to perform the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may execute the stated process / algorithm individually or in combination. Network entity 2002 may include a variety of components configured for various functions. In one configuration, network entity 2002 may include a component for scheduling resource allocation for sidelink transmission based on at least one of a destination ID for sidelink transmission or a sidelink conflict report. The network entity may include a component for providing the resource allocation for sidelink transmission to a first UE. The network entity may also include a component for obtaining a sidelink indication that supports sidelink scheduling using a destination ID or a sidelink conflict report sent for a sidelink. The network entity may also include a component for obtaining from a second UE a sidelink conflict report sent from at least one additional UE indicating a conflicting sidelink. The component may be component 199 of network entity 2002 configured to perform the functions described therein. As described above, network entity 2002 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Therefore, in one configuration, the component may be the TX processor 316, the RX processor 370, and / or the controller / processor 375 configured to perform the functions described therein.

[0137] It should be understood that the specific order or hierarchy of the boxes in the disclosed process / flowcharts is merely an example of the exemplary method. It should be understood that the specific order or hierarchy of the boxes in the process / flowcharts may be rearranged based on design preferences. Furthermore, some boxes may be combined or omitted. The appended method claims present the elements of various boxes in a sample order, but are not limited to the given specific order or hierarchy.

[0138] 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 may be applied to other aspects. Therefore, the claims are not limited to the aspects described herein but should be given the full scope consistent with the language of the claims. Unless specifically stated otherwise, references to elements in the singular form do not mean “one and only one” but rather “one or more.” Terms such as “if,” “when,” and “simultaneously” do not imply a direct temporal relationship or reaction. That is, these phrases, such as “when,” do not imply an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply suggest that an action will occur if the condition is met, without requiring a specific or immediate time limit for the occurrence of the action. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or superior to other aspects. Unless otherwise 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, and 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" can 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 collection of elements, where the number of elements is one or more. Therefore, for a set of X, X will include one or more elements. If the first device receives data from or sends data to the second device, data can be received / sent directly between the first and second devices, or indirectly between the first and second devices via a set of devices. All structural and functional equivalents of the elements throughout the various aspects described herein that are known to or will later be known to a person skilled in the art are expressly incorporated herein by reference and are covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is explicitly recited in the claims. The terms “module,” “mechanism,” “element,” “device,” etc., cannot replace the word “component.” Therefore, no claim element will be construed as a functional component unless the element is explicitly described using the phrase “component for…”.

[0139] As used in this article, 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, conditions, factors, etc.) should be interpreted as “based on at least A”, unless specifically stated differently.

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

[0141] Aspect 1 is a method for wireless communication at a first user equipment (UE), the method comprising: receiving from a network entity a resource allocation for sidelink transmission, the resource allocation including an indication of a destination identifier (ID); and transmitting the sidelink transmission to a second UE based on the resource allocation for the sidelink transmission and the destination ID associated with a second UE.

[0142] In aspect 2, the method according to aspect 1 further includes: receiving from the network entity the resource allocation for the sidelink transmission, the resource allocation including the indication of the destination ID; and transmitting the sidelink transmission to the second UE based on the resource allocation for the sidelink transmission and the destination ID associated with the second UE.

[0143] In aspect 3, the method according to aspect 1 or aspect 2 further includes: before receiving the resource allocation, sending to a network entity a sidelink indication that at least supports sidelink scheduling using the destination ID of the second UE for the sidelink.

[0144] In aspect 4, the method according to any one of aspects 1 to 3 further includes: sending a request for the allocation of resources for transmission with the side link of the second UE, wherein the request includes the destination ID associated with the second UE.

[0145] In aspect 5, the method according to any one of aspects 1 to 4 further includes: the side link transmission with the second UE having the destination ID is a beamforming transmission.

[0146] In aspect 6, the method according to any one of aspects 1 to 5 further includes: the destination ID indicating that the scheduled sidelink transmission is for any sidelink UE having a unicast connection with the first UE.

[0147] Aspect 7 is an apparatus for wireless communication at a UE, the apparatus comprising: at least one memory; and at least one processor coupled to the at least one memory and based at least in part on information stored in the at least one memory, the at least one processor being configured individually or in any combination to cause the UE to perform a method according to any one of aspects 1 to 6.

[0148] Aspect 8 is an apparatus for wireless communication at a UE, the apparatus comprising components for performing each step of the method according to any one of aspects 1 to 6.

[0149] Aspect 9 is an apparatus according to any one of aspects 7 to 8, the apparatus further comprising a transceiver configured to receive or transmit in association with the method according to any one of aspects 1 to 6.

[0150] Aspect 10 is a computer-readable medium (e.g., non-transitory) that stores computer-executable code at a UE, the code causing the at least one processor to perform the method according to any one of aspects 1 to 6 when executed by at least one processor.

[0151] Aspect 11 is a method for wireless communication at a UE, the method comprising: receiving from a first UE a request to form a connection for sidelink communication; measuring at least one conflicting sidelink transmission from at least one additional UE that interferes with sidelink transmissions from the first UE; sending a sidelink conflict report to a network entity, the sidelink conflict report indicating the measured at least one conflicting sidelink transmission from the at least one additional UE; and communicating with the first UE via the sidelink communication based on resource allocation for the sidelink transmissions after the sidelink conflict report.

[0152] In aspect 12, the method according to aspect 11 further includes: receiving from the first UE the request to form the connection for sidelink communication; sending the sidelink conflict report to the network entity, the sidelink conflict report indicating at least one conflicting sidelink transmission from the at least one additional UE as measured; and communicating with the first UE via the sidelink communication based on the resource allocation for the sidelink transmission after the sidelink conflict report.

[0153] In aspect 13, the method according to aspect 11 or aspect 12 further includes: sending a sidelink indication to a network entity that indicates at least support for sidelink conflict reports sent for sidelinks.

[0154] In aspect 14, the method according to any one of aspects 11 to 13 further includes, for each of the at least one additional UE, the sidelink conflict report including one or more of the following: a connection ID associated with the conflicting sidelink communication, or the interference level of the conflicting sidelink communication.

[0155] In aspect 15, the method according to any one of aspects 11 to 14 further includes: the sidelink conflict report further includes at least one of: a resource pool associated with sidelink reception at the second UE; or a target connection ID from a sidelink transmission from the first UE.

[0156] In aspect 16, the method according to aspect 14 or 15 further includes: the connection ID including the source ID of the conflict side link transmission and the destination ID of the recipient of the conflict side link communication.

[0157] In aspect 17, the method according to aspect 14 or 15 further includes: the connection ID including the source ID sent by the conflicting side link.

[0158] In aspect 18, the method according to aspect 14 further includes: the interference level is indicated based on the relative RSRP values ​​measured on the target connection and the conflicting connection.

[0159] In aspect 19, the method according to aspect 18 further includes: the interference level is indicated relative to a range having a first threshold and a second threshold, wherein the interference level is indicated as: below the first threshold, within the range between the first threshold and the second threshold, or above the second threshold.

[0160] In aspect 20, the method according to any one of aspects 11 to 19 further includes: resource allocation mode 1 is configured for a sidelink resource pool, the sidelink conflict report including the source ID of the conflicting sidelink.

[0161] In aspect 21, the method according to aspect 20 further includes: the interference level based on at least one of the following: the maximum RSRP transmitted from all sidelinks of the sidelink UE associated with the source ID, or the average RSRP transmitted from all sidelinks of the sidelink UE associated with the source ID.

[0162] In aspect 22, the method according to any one of aspects 11 to 21 further includes: the sidelink conflict report is periodic.

[0163] In aspect 23, the method according to any one of aspects 11 to 21 further includes: the sidelink conflict report is a non-periodic report in response to a triggering event.

[0164] Aspect 24 is an apparatus for wireless communication at a UE, the apparatus comprising: at least one memory; and at least one processor coupled to the at least one memory and based at least in part on information stored in the at least one memory, the at least one processor being configured individually or in any combination to cause the UE to perform a method according to any one of aspects 11 to 23.

[0165] Aspect 25 is an apparatus for wireless communication at a UE, the apparatus comprising components for performing each step of the method according to any one of aspects 11 to 23.

[0166] Aspect 26 is an apparatus according to any one of aspects 24 to 25, the apparatus further comprising a transceiver configured to receive or transmit in association with the method according to any one of aspects 11 to 23.

[0167] Aspect 27 is a computer-readable medium (e.g., non-transitory) that stores computer-executable code at a UE, the code causing the at least one processor to perform a method according to any one of aspects 11 to 23 when executed by at least one processor.

[0168] Aspect 28 is a method for wireless communication at a network entity, the method comprising: scheduling a resource allocation for the sidelink transmission based on at least one of a destination identifier (ID) for the sidelink transmission or a sidelink conflict report; and providing the resource allocation for the sidelink transmission to a first user equipment (UE).

[0169] In aspect 29, the method according to aspect 28 further includes providing the first UE with the resource allocation for the sidelink transmission.

[0170] In aspect 30, the method according to aspect 28 or 29 further includes: obtaining a sidelink indication that supports sidelink scheduling using the destination ID or at least one of the sidelink conflict reports sent for the sidelink.

[0171] In aspect 31, the method according to any one of aspects 28 to 30 further includes: the resource allocation includes the destination ID of the second UE.

[0172] In aspect 32, the method according to aspect 31 further includes: the destination ID indicating that the scheduled sidelink transmission is for any sidelink UE having a unicast connection with the first UE.

[0173] In aspect 33, the method according to any one of aspects 28 to 32 further includes: obtaining from the second UE a sidelink conflict report transmitted from at least one additional UE, indicating the measurement.

[0174] In aspect 34, the method according to aspect 33 further includes, for each of the at least one additional UE, the sidelink conflict report including one or more of the following: a connection ID associated with the conflicting sidelink communication, or the interference level of the conflicting sidelink communication.

[0175] In aspect 35, the method according to aspect 34 further includes, in which the sidelink conflict report includes at least one of: a resource pool associated with the sidelink reception at the second UE; or a target connection ID from the sidelink transmission of the first UE.

[0176] In aspect 36, the method according to aspect 34 further includes: the connection ID including the source ID of the conflict-side link transmission and the destination ID of the receiver of the conflict-side link transmission.

[0177] In aspect 37, the method according to aspect 34 further includes: the connection ID is based on the source ID sent on the conflicting side link.

[0178] Aspect 38 is an apparatus for wireless communication at a network entity, the apparatus comprising: at least one memory; and at least one processor coupled to the at least one memory and based at least in part on information stored in the at least one memory, the at least one processor being configured individually or in any combination to cause the network entity to perform a method according to any one of aspects 28 to 37.

[0179] Aspect 39 is an apparatus for wireless communication at a network entity, the apparatus comprising components for performing each step of the method according to any one of aspects 28 to 37.

[0180] Aspect 40 is an apparatus according to any one of aspects 38 to 39, the apparatus further comprising a transceiver configured to receive or transmit in association with the method according to any one of aspects 28 to 37.

[0181] Aspect 41 is a computer-readable medium (e.g., non-transitory) storing computer-executable code at a network entity, the code causing the at least one processor to perform any one of aspects 28 to 37 when executed by at least one processor.

Claims

1. An apparatus for performing wireless communication at a first user equipment (UE), the apparatus comprising: At least one memory; and At least one processor, coupled to at least one memory, and configured individually or in any combination, based at least in part on information stored in the at least one memory, to cause the first UE to: Receive resource allocation from a network entity for sidelink transmission, the resource allocation including an indication of a destination identifier (ID); and The sidelink transmission is sent to the second UE based on the resource allocation used for the sidelink transmission and the destination ID associated with the second UE.

2. The apparatus of claim 1, further comprising a transceiver coupled to the at least one processor, the transceiver being configured to: Receive from the network entity the resource allocation for the sidelink transmission, the resource allocation including the indication of the destination ID; and The sidelink transmission is sent to the second UE based on the resource allocation used for the sidelink transmission and the destination ID associated with the second UE.

3. The apparatus of claim 1, wherein the at least one processor is configured to cause the first UE to: Before receiving the resource allocation, a sidelink indication is sent to the network entity, indicating that at least the sidelink scheduling using the destination ID of the second UE is supported for the sidelink.

4. The apparatus of claim 1, wherein the at least one processor is configured to cause the first UE to: Send a request for resource allocation for transmission with the side link of the second UE, wherein the request includes the destination ID associated with the second UE.

5. The apparatus of claim 1, wherein the sidelink transmission with the second UE having the destination ID is a beamforming transmission.

6. The apparatus of claim 1, wherein the destination ID indicates that the scheduled sidelink transmission is for any sidelink UE having a unicast connection to the first UE.

7. An apparatus for wireless communication at a second user equipment (UE), the apparatus comprising: At least one memory; and At least one processor, coupled to the at least one memory, and configured individually or in any combination, based at least in part on information stored in the at least one memory, to cause the device to: Receive a request from the first UE to form a connection for sidelink communication; The interference is measured from at least one conflicting sidelink transmission from at least one additional UE, transmitted via the sidelink of the first UE. Send a sidelink conflict report to the network entity, the sidelink conflict report indicating at least one conflicting sidelink transmission from the at least one additional UE as measured; as well as Following the sidelink conflict report, communication is initiated with the first UE via the sidelink communication based on the resource allocation for the sidelink transmission.

8. The apparatus of claim 7, further comprising a transceiver coupled to the at least one processor, the transceiver being configured to: Receive the request from the first UE to form the connection for the sidelink communication; The sidelink conflict report is sent to the network entity, the sidelink conflict report indicating at least one conflicting sidelink transmission from the at least one additional UE as measured; as well as Following the sidelink conflict report, communication is conducted with the first UE via the sidelink communication based on the resource allocation used for the sidelink transmission.

9. The apparatus of claim 7, wherein the at least one processor is configured to cause the second UE to: Send an indication to the network entity that supports at least a sidelink indication for sending the sidelink conflict report for the sidelink.

10. The apparatus of claim 7, wherein for each of the at least one additional UE, the sidelink conflict report includes one or more of the following: Connection ID associated with conflict side link communication, or The interference level of the conflict-side link communication.

11. The apparatus of claim 10, wherein the sidelink conflict report further comprises at least one of the following: The resource pool associated with the sidelink reception at the second UE; or The target connection ID sent from the side link of the first UE.

12. The apparatus of claim 10, wherein the connection ID includes the source ID transmitted by the at least one conflict side link and the destination ID of the receiver of the conflict side link communication.

13. The apparatus of claim 10, wherein the connection ID includes the source ID transmitted by the at least one conflicting side link.

14. The apparatus of claim 10, wherein the interference level is indicated based on relative RSRP values ​​measured on the target connection and the conflicting connection.

15. The apparatus of claim 14, wherein the interference level is indicated relative to a range having a first threshold and a second threshold, wherein the interference level is indicated as one of: Below the first threshold, Within the range between the first threshold and the second threshold, or It is higher than the second threshold.

16. The apparatus of claim 9, wherein resource allocation mode 1 is configured for a sidelink resource pool, and the sidelink conflict report includes the source ID of the conflicting sidelink.

17. The apparatus of claim 16, wherein the interference level is based on at least one of the following: the maximum reference signal received power (RSRP) transmitted from all sidelinks of the sidelink UE associated with the source ID, or the average RSRP transmitted from each sidelink of the sidelink UE associated with the source ID.

18. The apparatus of claim 7, wherein the sidelink conflict report is periodic.

19. The apparatus of claim 7, wherein the sidelink conflict report is a non-periodic report in response to a triggering event.

20. An apparatus for wireless communication at a network entity, the apparatus comprising: At least one memory; and At least one processor, coupled to at least one memory, and configured individually or in any combination, based at least in part on information stored in the at least one memory, to cause the network entity to: Resource allocation for the sidelink transmission is scheduled based on at least one of the destination identifier (ID) for the sidelink transmission or the sidelink conflict report; and The resource allocation for the sidelink transmission is provided to the first user equipment (UE).

21. The apparatus of claim 20, further comprising a transceiver coupled to the at least one processor, the transceiver being configured to: The resource allocation for the sidelink transmission is provided to the first UE.

22. The apparatus of claim 20, wherein the at least one processor is configured to cause the network entity to: Obtain a sidelink indication that supports at least one of the sidelink scheduling using the destination ID or the sidelink conflict report sent for the sidelink.

23. The apparatus of claim 20, wherein the resource allocation includes the destination ID of the second UE.

24. The apparatus of claim 23, wherein the destination ID indicates that the scheduled sidelink transmission is for any sidelink UE having a unicast connection to the first UE.

25. The apparatus of claim 20, wherein the at least one processor is configured to cause the network entity to: The second UE receives a sidelink conflict report from at least one additional UE, indicating the measurement of the conflict sidelink.

26. The apparatus of claim 25, wherein for each of the at least one additional UE, the sidelink conflict report includes one or more of the following: Connection ID associated with conflict side link communication, or The interference level of the conflict-side link communication.

27. The apparatus of claim 26, wherein the sidelink conflict report further comprises at least one of the following: The resource pool associated with the sidelink reception at the second UE; or The target connection ID sent from the side link of the first UE.

28. The apparatus of claim 26, wherein the connection ID includes a source ID transmitted via a conflict-side link and a destination ID of the receiver transmitted via the conflict-side link.

29. The apparatus of claim 26, wherein the connection ID is based on the source ID transmitted on the conflict-side link.

30. A method for wireless communication at a first user equipment (UE), the method comprising: Receive resource allocations for sidelink transmissions from network entities, the resource allocations including an indication of a destination identifier (ID); as well as The sidelink transmission is sent to the second UE based on the resource allocation used for the sidelink transmission and the destination ID associated with the second UE.

Images