Scheduling conflict resolution for sidelink and Uu communications

Abstract

A method of wireless communication performed at a user equipment (UE) includes receiving a first time domain configuration for a Uu component carrier (CC); receiving a second time domain configuration for a sidelink (SL) resource pool, wherein the Uu CC and the SL resource pool are within the same frequency band; and communicating a first communication over a first time period based on the first time domain configuration, the second time domain configuration, and an in-band priority configuration, where a second communication is scheduled over at least a portion of the first time period, where one of the first communication or the second communication includes an SL communication in a first link direction, and wherein the other of the first communication or the second communication comprises a Uu communication in a second link direction opposite the first link direction.

Description

[0001] introduction

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, etc. These systems may be capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). A wireless multiple-access communication system may include several base stations (BSs), each of which simultaneously supports communication for multiple communication devices, which may be otherwise referred to as user equipment (UE).

[0003] In order to meet the growing demand for extended mobile broadband connections, wireless communication technology is evolving from long-term evolution (LTE) technology to next-generation new radio (NR) technology. For example, compared to LTE, NR is designed to provide lower latency, higher bandwidth or throughput, and higher reliability. NR is designed to operate on a wideband array, for example, from low bands below about 1 gigahertz (GHz) and from mid-bands from about 1 GHz to about 6 GHz to high bands such as millimeter wave (mmWave) bands. NR is also designed to operate across different spectrum types, from licensed spectrum to unlicensed and shared spectrum. Spectrum sharing enables operators to have the opportunity to aggregate spectrum to dynamically support high-bandwidth services. Spectrum sharing can extend the benefits of NR technology to operating entities that may not have access to licensed spectrum.

[0004] In a wireless communication network, a BS may communicate with a UE using a Uu interface, wherein the UE communicates with the network via the BS in an uplink (UL) direction and a downlink (DL) direction. The UE may also communicate with each other using a sidelink (SL) interface, which may also be referred to as a PC5 interface. The sidelink interface or architecture allows a UE to transmit data to another UE (e.g., from one vehicle to another vehicle) without tunneling through the BS and / or an associated core network. In some aspects, a first set of resources may be provided to the UE for communicating with the network via a Uu interface, and a second set of resources for communicating with other UEs via an SL interface. Summary of the invention

[0005] The following summarizes some aspects of the present disclosure to provide a basic understanding of the discussed technology. This summary is not an exhaustive overview of all expected features of the present disclosure, and is neither intended to identify key or important elements of all aspects of the present disclosure, nor to delineate the scope of any or all aspects of the present disclosure. Its sole purpose is to present some concepts of one or more aspects of the present disclosure in a summarized form as a prelude to more specific embodiments presented later.

[0006] A user equipment (UE) may be configured by a network (e.g., via a network entity or network device) to communicate over a Uu interface in one or more component carriers (CCs). In addition, the UE may be configured with one or more side link resource pools for communicating with other UEs over a side link interface. In some aspects, the CC used for Uu communication may be in the same frequency band as the resource pool used for SL communication. The UE may be subject to certain operational constraints. For example, the UE may not be configured to use in-band frequency resources for simultaneous transmission and reception. However, in some instances, the UE may be instructed to communicate Uu communications (e.g., transmission) in a first link direction and to communicate SL communications (e.g., reception) in a second link direction. The UE may not be allowed to simultaneously transmit and receive in in-band frequency resources.

[0007] The present disclosure provides a scheme, mechanism and system for resolving conflicts between Uu communications and SL communications on in-band frequency resources. For example, a UE may be configured with an in-band priority configuration for determining a relative in-band priority between Uu communications that conflict in time with SL communications having a link direction different from that of Uu communications. The UE may be configured with a first time domain configuration for a Uu component carrier (CC) and a second time domain configuration for a side link (SL) resource pool in the same frequency band as the Uu CC. The UE may be instructed or otherwise configured to send a first communication on the Uu CC and a second communication on the SL resource pool in different link directions and in overlapping time periods. The UE may resolve scheduling conflicts based on the in-band priority configuration and convey the first communication in the first time period.

[0008] According to one aspect of the present disclosure, a method for wireless communication performed at a user equipment (UE) includes: receiving a first time domain configuration for a Uu component carrier (CC); receiving a second time domain configuration for a side link (SL) resource pool, wherein the Uu CC and the SL resource pool are within the same frequency band; and based on the first time domain configuration, the second time domain configuration and the in-band priority configuration, conveying a first communication in a first time period, wherein a second communication is scheduled within at least a portion of the first time period, wherein one of the first communication or the second communication includes SL communication in a first link direction, and wherein the other of the first communication or the second communication includes Uu communication in a second link direction opposite to the first link direction.

[0009] According to another aspect of the present disclosure, a user equipment (UE) includes: a processor; and a transceiver, wherein the UE is configured to: receive a first time domain configuration for a Uu component carrier (CC); receive a second time domain configuration for a side link (SL) resource pool, wherein the Uu CC and the SL resource pool are within the same frequency band; and based on the first time domain configuration, the second time domain configuration and the in-band priority configuration, convey a first communication in a first time period, wherein a second communication is scheduled within at least a portion of the first time period, wherein one of the first communication or the second communication includes SL communication in a first link direction, and wherein the other of the first communication or the second communication includes Uu communication in a second link direction opposite to the first link direction.

[0010] According to another aspect of the present disclosure, a non-transitory computer-readable medium having program code recorded thereon, wherein the program code includes instructions that can be executed by a processor of a user equipment (UE) to cause the UE to: receive a first time domain configuration for a Uu component carrier (CC); receive a second time domain configuration for a side link (SL) resource pool, wherein the Uu CC and the SL resource pool are within the same frequency band; and based on the first time domain configuration, the second time domain configuration, and the in-band priority configuration, convey a first communication in a first time period, wherein the second communication is scheduled within at least a portion of the first time period, wherein one of the first communication or the second communication includes SL communication in a first link direction, and wherein the other of the first communication or the second communication includes Uu communication in a second link direction opposite to the first link direction.

[0011] According to another aspect of the present disclosure, a user equipment (UE) includes: a component for receiving a first time domain configuration for a Uu component carrier (CC); a component for receiving a second time domain configuration for a side link (SL) resource pool, wherein the Uu CC and the SL resource pool are in the same frequency band; and a component for conveying a first communication in a first time period based on the first time domain configuration, the second time domain configuration, and the in-band priority configuration, wherein the second communication is scheduled within at least a portion of the first time period, wherein one of the first communication or the second communication includes an SL communication in a first link direction, and wherein the other of the first communication or the second communication includes a Uu communication in a second link direction opposite to the first link direction. Other aspects, features, and examples of the present invention will become apparent to those of ordinary skill in the art after reading the following description of specific exemplary examples of the present invention in conjunction with the accompanying drawings. Although features of the present invention may be discussed below with respect to certain aspects and drawings, all examples of the present invention may include one or more of the advantageous features discussed herein. In other words, although one or more examples may be discussed as having certain advantageous features, one or more of such features may also be used in accordance with the various examples of the invention discussed herein. In a similar manner, although exemplary aspects may be discussed below as device, system, or method examples, it should be understood that such exemplary examples may be implemented in various devices, systems, and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1 A wireless communication network according to some aspects of the present disclosure is illustrated.

[0013] Figure 2 is a diagram illustrating an example decomposed BS architecture according to some aspects of the present disclosure.

[0014] Figure 3 A sidelink communication network according to some aspects of the present disclosure is illustrated.

[0015] Figure 4 Sidelink resources associated with a wireless communication network according to some aspects of the present disclosure are illustrated.

[0016] Figure 5 A radio frame structure according to some aspects of the present disclosure is illustrated.

[0017] Fig. 6A Sidelink and downlink collision scenarios according to some aspects of the present disclosure are illustrated.

[0018] Figure 6B Sidelink and uplink collision scenarios according to some aspects of the present disclosure are illustrated.

[0019] Figure 7 is a signaling diagram of a communication method according to some aspects of the present disclosure.

[0020] Figure 8 In-band conflict resolution according to some aspects of the present disclosure is illustrated.

[0021] Fig. 9 In-band conflict resolution according to some aspects of the present disclosure is illustrated.

[0022] Fig.10 In-band conflict resolution according to some aspects of the present disclosure is illustrated.

[0023] Fig.11 In-band conflict resolution according to some aspects of the present disclosure is illustrated.

[0024] Fig.12 is a block diagram of an exemplary user equipment (UE) according to some aspects of the present disclosure.

[0025] Fig.13 is a block diagram of an exemplary base station (BS) according to some aspects of the present disclosure.

[0026] Fig.14 is a flow chart of a communication method according to some aspects of the present disclosure.

[0027] Fig.15 is a flow chart of a communication method according to some aspects of the present disclosure. DETAILED DESCRIPTION

[0028] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configurations with which the concepts described herein may be practiced. In order to provide a comprehensive understanding of the various concepts, the specific embodiments include specific details. However, it is apparent to those skilled in the art that these concepts may be practiced without these specific details. In some cases, in order to avoid blurring such concepts, known structures and components are shown in block diagram form.

[0029] The present disclosure as a whole relates to wireless communication systems, which are also referred to as wireless communication networks. In various instances, techniques and devices can be used for wireless communication networks, such as code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, single carrier FDMA (SC-FDMA) networks, LTE networks, GSM networks, 5th generation (5G) or new radio (NR) networks and other communication networks. As described herein, the terms "network" and "system" can be used interchangeably.

[0030] OFDMA network can realize radio technology such as Evolved UTRA (E-UTRA), Institute of Electrical and Electronics Engineers (IEEE) 802.11, IEEE 802.16, IEEE 802.20, flash-OFDM, etc. UTRA, E-UTRA and Global System for Mobile Communications (GSM) are parts of Universal Mobile Telecommunications System (UMTS). Specifically, Long Term Evolution (LTE) is a UMTS version using E-UTRA. UTRA, E-UTRA, GSM, UMTS and LTE are described in documents provided by an organization named "3rd Generation Partnership Project" (3GPP), and cdma2000 is described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). These various radio technologies and standards are known or under development. For example, the 3rd Generation Partnership Project (3GPP) is a collaboration between telecommunication association groups with the goal of defining a globally applicable third generation (3G) mobile phone specification. 3GPP Long Term Evolution (LTE) is a 3GPP project aimed at improving the Universal Mobile Telecommunications System (UMTS) mobile phone standard. 3GPP may define specifications for next generation mobile networks, mobile systems, and mobile devices. The present disclosure relates to the evolution from LTE, 4G, 5G, NR and beyond wireless technologies, where access to wireless spectrum is shared between networks using a range of new and different radio access technologies or radio air interfaces.

[0031] Specifically, 5G networks consider various deployments, various spectrums, and various services and devices that can be implemented using a unified air interface based on OFDM. To achieve these goals, in addition to developing new radio technologies for 5G NR networks, further enhancements to LTE and LTE-A are also considered. 5G NR will be able to scale to (1) ultra-high density (e.g., about 1M nodes / km) 2 (1) provide coverage for the massive Internet of Things (IoT) with ultra-low complexity (e.g., on the order of tens of bits per second), ultra-low energy (e.g., on the order of 10+ years of battery life), and deep coverage with the ability to reach challenging locations; (2) provide coverage including mission-critical control with strong security to protect sensitive personal, financial, or classified information, ultra-high reliability (e.g., on the order of 99.9999% reliability), ultra-low latency (e.g., on the order of 1 ms), and for users with extensive mobility or lack of mobility; and (3) provide coverage with enhanced mobile broadband (including extremely high capacity (e.g., on the order of 10 Tbps / km 2 ), coverage of extremely high data rates (e.g., multi-Gbps rates, 100+Mbps user experience rates), and deep awareness with advanced discovery and optimization).

[0032] 5G NR can be implemented using an optimized OFDM-based waveform with scalable parameter sets and transmission time intervals (TTIs); with a common, flexible framework to efficiently multiplex services and features using dynamic low-latency time division duplex (TDD) / frequency division duplex (FDD) designs; and with advanced wireless technologies such as massive multiple-input multiple-output (MIMO), robust millimeter wave (mmWave) transmission, advanced channel decoding, and device-centric mobility. The scalability of parameter sets in 5G NR and the scaling of subcarrier spacing can effectively address the operation of various services across different spectrums and different deployments. For example, in various outdoor and macro coverage deployments of less than 3GHz FDD / TDD implementations, the subcarrier spacing can appear at 15kHz on bandwidths (BW) such as 5MHz, 10MHz, 20MHz, etc. For other various outdoor and small cell coverage deployments of TDD greater than 3GHz, the subcarrier spacing can appear at 30kHz on 80 / 100MHz BW. For various other indoor broadband implementations, using TDD on the unlicensed portion of the 5 GHz band, subcarrier spacing may occur at 60 kHz over 160 MHz BW. Finally, for various deployments transmitting with the mmWave component at 28 GHz TDD, subcarrier spacing may occur at 120 kHz over 500 MHz BW.

[0033] 5G NR's scalable parameter sets facilitate scalable TTIs for different latency and quality of service (QoS) requirements. For example, shorter TTIs can be used for low latency and high reliability, while longer TTIs can be used for higher spectral efficiency. Efficient multiplexing of long and short TTIs allows transmission to start on symbol boundaries. 5G NR also envisions a self-contained integrated subframe design with uplink / downlink scheduling information, data, and acknowledgment in the same subframe. The self-contained integrated subframe supports communications in unlicensed spectrum or contention-based shared spectrum, adaptive uplink / downlink, which can be flexibly configured on a per-cell basis to dynamically switch between uplink and downlink to meet current business needs.

[0034] The various other aspects and features of the present disclosure are further described below. It should be apparent that the teachings herein can be embodied in various forms, and any specific structure, function, or both disclosed herein are merely representative and not restrictive. Based on the teachings herein, it should be understood by those of ordinary skill in the art that the aspects disclosed herein can be implemented independently of any other aspects, and two or more of these aspects can be combined in various ways. For example, any number of aspects set forth herein can be used to implement a device or practice method. In addition, such a device can be implemented, or such a method can be implemented, using other structures, functions, or structures and functions other than or different from one or more of the aspects set forth herein. For example, the method can be implemented as a part of a system, device, device, and / or as instructions stored on a computer-readable medium for execution on a processor or computer. In addition, an aspect can include at least one element of a claim.

[0035] The UE may be configured by the network (e.g., via a network entity or network device) to communicate via the Uu interface in one or more frequency carriers. In some aspects, the one or more frequency carriers may be referred to as component carriers. The component carrier may be in a licensed band or in an unlicensed band. In addition, the UE may be configured with one or more side link resource pools for communicating with other UEs via the side link interface. In some aspects, the resources used for Uu communication may be in the same frequency band as the resource pool used for SL communication. In some aspects, the side link resource pool may include one or more subchannels and one or more time slots. Some time slots may not be available for side link communication because these time slots may be allocated or configured for other purposes. Some side link time slots may be configured for feedback resources, such as a physical side link feedback channel (PSFCH). In some aspects, the resource pool may be configured by the network. In other aspects, the resource pool may be configured by one or more other UEs that communicate via the side link interface. In other aspects, the side link resource pool may be preconfigured or preloaded on the UE.

[0036] The UE may also be configured with one or more time domain configurations. For example, the UE may be configured for Uu time division duplex (TDD), wherein a subset of resources is allocated for downlink reception, and a second subset of resources is allocated for uplink transmission. The time domain configuration may also include one or more flexible resources. Flexible resources may include a combination of downlink and uplink resources (such as downlink and / or uplink symbols). In other aspects, the time domain configuration may include or indicate one or more flexible resources for gaps between different link directions. In addition, the UE may be configured with a side link time domain configuration. In some aspects, the side link time domain configuration may include any other suitable supply of a side link bitmap, a side link dynamic grant, or a side link time domain resource. In some aspects, the resources available for cyclic communication may be based on a combination of a Uu time domain configuration and a side link time domain configuration. For example, in some aspects, side link communication may be limited to the Uu time domain resources allocated for uplink. On the other hand, cyclic communication may be limited to the time domain resources allocated for downlink reception.

[0037] The UE may be subject to certain operational constraints. For example, the UE may not be configured to use in-band frequency resources for simultaneous transmission and reception. In this regard, the UE may be configured with a first Uu link frequency resource set and a second side link frequency resource set based on the side link resource pool configuration. As described above, the side link frequency resources may be in-band together with the Uu link frequency resources. In some instances, the UE may be instructed to send UL communications on the Uu link and simultaneously receive SL communications on the SL link. For example, the UE may receive downlink control information (DCI) including a grant for DL ​​reception during a first time period, and may also receive SCI or DCI indicating a grant for SL transmission during the same first time period. The UE may not be allowed to transmit and receive simultaneously in in-band frequency resources. Therefore, the UE may need to resolve conflicts.

[0038] The present disclosure provides various schemes, mechanisms and devices for resolving conflicts between Uu communications and SL communications on in-band frequency resources. For example, a UE may be configured with an in-band priority configuration for determining a relative in-band priority between Uu communications that conflict with SL communications having a link direction different from that of Uu communications. In some aspects, the in-band priority configuration may include or indicate a rule for giving priority to one communication in a communication over one or more other communications to resolve the conflict. The rules of the in-band priority configuration may be based on whether the scheduled side link communication is based on a dynamic side link grant, whether a DCI verifying resources for side link communication or for Uu communication has been received, a listen-before-talk (LBT) success report and / or the service type of the conflicting communication. In some aspects, the UE may determine or select a conflicting communication in the conflicting communication for communication (receiving or sending) based on the Uu time domain configuration, the SL time domain configuration and the in-band priority configuration. Therefore, the UE and / or the network may be configured with one or more mechanisms for prioritizing Uu communications or SL communications with different link directions.

[0039] Aspects of the present disclosure may provide several benefits. For example, the conflict resolution mechanism described herein may provide an efficient conflict resolution method that prioritizes Uu communications or SL communications in in-band frequency resources based on one or more relevant channel conditions or parameters of scheduled communications. For example, communications with higher service priorities may be prioritized over communications with lower service priorities to improve and / or maintain network performance and user experience.

[0040] Figure 1 A wireless communication network 100 according to some aspects of the present disclosure is illustrated. The network 100 includes multiple base stations (BSs) 105 and other network entities. The BSs 105 may be stations that communicate with the UEs 115, and may also be referred to as evolved Node Bs (eNBs), next generation eNBs (gNBs), access points, etc. Each BS 105 may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" may refer to the particular geographic coverage area of ​​the BS 105 and / or the BS subsystem serving the coverage area, depending on the context in which the term is used.

[0041] BS105 may provide communication coverage for macro cells or small cells (such as pico cells or femto cells) and / or other types of cells. Macro cells generally cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscriptions with a network provider. Small cells (such as pico cells) will generally cover a relatively small geographic area and may allow unrestricted access by UEs with service subscriptions with a network provider. Small cells (such as femto cells) will generally also cover a relatively small geographic area (e.g., a home) and, in addition to unrestricted access, may also provide restricted access by UEs associated with the femto cells (e.g., UEs in a closed subscriber group (CSG), UEs of users in a home, etc.). A BS for a macro cell may be referred to as a macro BS. A BS for a small cell may be referred to as a small cell BS, a pico BS, a femto BS, or a home BS. In Figure 1 In the example shown, BS105d and 105e may be conventional macro BSs, while BS 105a-105c may be macro BSs with one of three-dimensional (3D), full-dimensional (FD) or massive MIMO capabilities. BS105a-105c may utilize its higher-dimensional MIMO capabilities to employ 3D beamforming in both elevation and azimuth beamforming to increase coverage and capacity. BS105f may be a small cell BS, which may be a home node or a portable access point. BS105 may support one or more (e.g., two, three, four, etc.) cells.

[0042] Network 100 may support synchronous or asynchronous operation. For synchronous operation, the BSs may have similar frame timing, and transmissions from different BSs may be approximately aligned in time. For asynchronous operation, the BSs may have different frame timing, and transmissions from different BSs may not be aligned in time.

[0043] UE 115 is dispersed throughout the wireless network 100, and each UE 115 can be stationary or mobile. UE 115 can also be referred to as a terminal, a mobile station, a subscriber unit, a station, etc. UE 115 can be a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a tablet computer, a laptop computer, a cordless phone, a wireless local loop (WLL) station, etc. In one aspect, UE 115 can be a device including a universal integrated circuit card (UICC). On the other hand, UE can be a device that does not include UICC. In some aspects, UE 115 that does not include UICC can also be referred to as IoT device or Internet of Everything (IoE) device. UE 115a-115d is an example of a mobile smart phone type device accessing the network 100. UE 115 can also be a machine that is specially configured for connected communication (including machine type communication (MTC), enhanced MTC (eMTC), narrowband IoT (NB-IoT), etc.). UE 115e-115h are examples of various machines configured for communication to access network 100. UE 115i-115k are examples of vehicles equipped with wireless communication devices configured for communication to access network 100. UE 115 may be able to communicate with any type of BS, whether macro BS, small cell, etc. Figure 1 , a lightning symbol (e.g., a communication link) indicates wireless transmission between UE 115 and a serving BS 105 (which is a BS designated to provide service to UE 115 on a downlink (DL) and / or uplink (UL), desired transmission between BSs 105, backhaul transmission between BSs, or sidelink transmission between UE 115.

[0044] In operation, BS105a-105c uses 3D beamforming and cooperative spatial technology (such as coordinated multi-point (CoMP) or multiple connections) to serve UE 115a and 115b. Macro BS105d can perform backhaul communications with BS105a-105c and small cell BS105f. Macro BS105d also sends multicast services that UE 115c and 115d subscribe to and receive. Such multicast services may include mobile TV or streaming video, or may include other services for providing community information, such as weather emergencies or alerts, such as Amber alerts or gray alerts.

[0045] BS 105 may also communicate with a core network. The core network may provide user authentication, access authorization, tracking, Internet Protocol (IP) connections, and other access, routing, or mobility functions. At least some of BSs 105 (e.g., which may be examples of evolved Node Bs (eNBs) or access node controllers (ANCs)) may interface with the core network via a backhaul link (e.g., S1, S2, etc.), and may perform radio configuration and scheduling to communicate with UE 115. In various examples, BSs 105 may communicate with each other directly or indirectly (e.g., through a core network) over a backhaul link (e.g., X1, X2, etc.), which may be a wired or wireless communication link.

[0046] The network 100 may also support mission-critical communications with ultra-reliable and redundant links for mission-critical devices such as UE 115e, which may be a vehicle (e.g., a car, truck, bus, autonomous vehicle, airplane, ship, etc.). The redundant communication links with UE 115e may include links from macro BSs 105d and 105e, and a link from a small cell BS 105f. Other machine-type devices such as UE 115f (e.g., a thermometer), UE 115g (e.g., a smart meter), and UE 115h (e.g., a wearable device) may communicate directly with a BS (such as small cell BS 105f and macro BS 105e) through the network 100, or in a multi-hop configuration by communicating with another user device that relays its information to the network (such as UE 115f communicating temperature measurement information to smart meter UE 115g, which is then reported to the network through small cell BS 105f). The network 100 may also provide additional network efficiency through dynamic, low-latency TDD / FDD communications, such as vehicle-to-vehicle (V2V) communications between UE 115i, 115j or 115k and other UEs 115, vehicle-to-everything (V2X) communications, cellular vehicle-to-everything (C-V2X) communications, and / or vehicle-to-infrastructure (V2I) communications between UE 115i, 115j or 115k and BS105.

[0047] In some implementations, network 100 utilizes an OFDM-based waveform for communication. An OFDM-based system can divide the system BW into multiple (K) orthogonal subcarriers, which are also commonly referred to as subcarriers, frequency modulations, frequency slots, etc. Each subcarrier can be modulated with data. In some instances, the subcarrier spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system BW. The system BW can also be divided into subbands. In other instances, the subcarrier spacing and / or the duration of the TTI can be scalable.

[0048] In some instances, BS105 may assign or schedule transmission resources (e.g., in the form of time-frequency resource blocks (RBs)) for downlink (DL) transmission and uplink (UL) transmission in network 100. DL refers to the transmission direction from BS105 to UE 115, and UL refers to the transmission direction from UE 115 to BS105. The communication may be in the form of a radio frame. A radio frame may be divided into a plurality of subframes, e.g., about 10. Each subframe may be divided into time slots, e.g., about 2. Each time slot may also be divided into micro-slots. In FDD mode, simultaneous UL and DL transmissions may occur in different frequency bands. For example, each subframe includes a UL subframe in a UL frequency band and a DL subframe in a DL frequency band. In TDD mode, UL and DL transmissions occur in different time periods using the same frequency band. For example, a subframe subset (e.g., a DL subframe) in a radio frame may be used for DL ​​transmission, and another subframe subset (e.g., an UL subframe) in a radio frame may be used for UL transmission.

[0049] DL subframes and UL subframes may be further divided into several zones. For example, each DL or UL subframe may have a predefined zone for the transmission of reference signals, control information, and data. A reference signal is a predetermined signal that facilitates communication between BS105 and UE 115. For example, a reference signal may have a specific pilot pattern or structure, wherein a pilot tone may span an operable BW or frequency band, and each pilot tone may be located at a predefined time and a predefined frequency. For example, BS105 may send a cell-specific reference signal (CRS) and / or a channel state information-reference signal (CSI-RS) to enable UE 115 to estimate a DL channel. Similarly, UE 115 may send a sounding reference signal (SRS) to enable BS105 to estimate an UL channel. Control information may include resource assignments and protocol control. Data may include protocol data and / or operable data. In some instances, BS105 and UE 115 may communicate using a self-contained subframe. A self-contained subframe may include a portion for DL ​​communication and a portion for UL communication. A self-contained subframe may be DL-centric or UL-centric. A DL-centric subframe may include a duration longer for DL ​​communications than for UL communications. A UL-centric subframe may include a duration longer for UL communications than for UL communications.

[0050] In some instances, network 100 may be an NR network deployed on a licensed spectrum. BS 105 may send synchronization signals (e.g., including a primary synchronization signal (PSS) and a secondary synchronization signal (SSS)) in network 100 to facilitate synchronization. BS 105 may broadcast system information associated with network 100 (e.g., including a master information block (MIB), remaining minimum system information (RMSI), and other system information (OSI)) to facilitate initial network access. In some instances, BS 105 may broadcast PSS, SSS, and / or MIB in the form of a synchronization signal block (SSB) on a physical broadcast channel (PBCH), and may broadcast RMSI and / or OSI on a physical downlink shared channel (PDSCH).

[0051] In some instances, a UE 115 attempting to access the network 100 may perform an initial cell search by detecting a PSS from the BS 105. The PSS may enable synchronization of period timing and may indicate a physical layer identification value. The UE 115 may then receive the SSS. The SSS may enable radio frame synchronization and may provide a cell identification value, which may be combined with the physical layer identification value to identify the cell. The SSS may also enable detection of duplex mode and cyclic prefix length. The PSS and SSS may be located in the center portion of the carrier or at any suitable frequency within the carrier.

[0052] After receiving the PSS and SSS, the UE 115 may receive the MIB. The MIB may include system information for initial network access and scheduling information for RMSI and / or OSI. After decoding the MIB, the UE 115 may receive the RMSI and / or OSI. The RMSI and / or OSI may include radio resource control (RRC) information related to random access channel (RACH) procedures, paging, control resource sets (CORESET) for physical downlink control channel (PDCCH) monitoring, physical uplink control channel (PUCCH), physical uplink shared channel (PUSCH), power control, SRS, and cell barring.

[0053] After obtaining the MIB, RMSI, and / or OSI, the UE 115 may perform a random access procedure to establish a connection with the BS 105. For the random access procedure, the UE 115 may send a random access preamble, and the BS 105 may respond with a random access response. Upon receiving the random access response, the UE 115 may send a connection request to the BS 105, and the BS 105 may respond with a connection response (e.g., a contention resolution message).

[0054] After the connection is established, the UE 115 and the BS 105 may enter a normal operation phase, in which operation data may be exchanged. For example, the BS 105 may schedule the UE 115 for UL and / or DL ​​communications. The BS 105 may send UL and / or DL ​​scheduling grants to the UE 115 via the PDCCH. The BS 105 may send DL communication signals to the UE 115 via the PDSCH according to the DL scheduling grant. The UE 115 may send UL communication signals to the BS 105 via the PUSCH and / or PUCCH according to the UL scheduling grant.

[0055] In some aspects, UE 115c and UE 115d may be sidelink UEs. UE 115c may receive an indicator indicating a set of start times associated with a transmission opportunity from BS 105. UE 115c may receive an indicator indicating a set of start times associated with a TXOP from BS 105 in a physical downlink control channel (PDCCH), a physical broadcast channel (PBCH), a physical downlink shared channel (PDSCH), or other suitable channels. In some aspects, UE 115c may receive the indicator in downlink control information (e.g., DCI3_x or other DCI communication formats). UE 115c and 115d may operate in licensed and / or unlicensed bands.

[0056] Figure 2 A diagram illustrating an example disaggregated base station 202 architecture is shown. The disaggregated base station 202 architecture may include one or more central units (CUs) 250 that may communicate directly with the core network via a backhaul link, or indirectly with the core network 100 through one or more disaggregated base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 225 via an E2 link, or a non-real-time (non-RT) RIC 245 associated with a service management and orchestration (SMO) framework 235, or both. The CU 250 may communicate with one or more distributed units (DUs) 230 via respective midhaul links, such as an F1 interface. The DU 230 may communicate with one or more radio units (RUs) 240 via respective fronthaul links. The RU 240 may communicate with respective UEs 220 via one or more radio frequency (RF) access links. In some implementations, a UE 220 may be served simultaneously by multiple RUs 240.

[0057] Each of the units (i.e., CU 250, DU 230, RU 240, and near-RT RIC 225, non-RT RIC 245, and SMO framework 235) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interfaces of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, a unit may include a wired interface configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally, the unit may include a wireless interface that may include a receiver, a transmitter, or a transceiver (such as a radio frequency (RF) transceiver) configured to receive or send signals, or both, to one or more of the other units via a wireless transmission medium.

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

[0059] DU 230 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 240. In some aspects, DU 230 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part according to a functional split such as that defined by the Third Generation Partnership Project (3GPP). In some aspects, DU 230 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 230 or with control functions hosted by CU 250.

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

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

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

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

[0064] Figure 3 1 illustrates an example of a wireless communication network 300 that provides side link communications according to aspects of the present disclosure. The network 300 may correspond to a portion of the network 100. For the purpose of simplifying the discussion, Figure 3 Two BSs 305 (shown as 305a and 305b) and six UEs 315 (shown as 315a1, 315a2, 315a3, 315a4, 315b1, and 315b2) are illustrated, but it will be appreciated that aspects of the present disclosure may be extended to any suitable number of UEs 315 (e.g., approximately 2, 3, 4, 5, 7, or more) and / or BSs 305 (e.g., approximately 1, 2, or more). The BSs 305 and UEs 315 may be similar to the BSs 105 and UEs 115, respectively. The BSs 305 and UEs 315 may share the same radio frequency band for communication. In some instances, the radio frequency band may be a 2.4 GHz unlicensed band, a 5 GHz unlicensed band, or a 6 GHz unlicensed band. In general, the shared radio frequency band may be at any suitable frequency.

[0065] BS 305a and UE 315a1-315a4 may be operated by a first network operating entity. BS 305b and UE 315b1-315b2 may be operated by a second network operating entity. In some aspects, the first network operating entity may utilize the same radio access technology (RAT) as the second network operating entity. For example, the BS 305a and UE 315a1-315a4 of the first network operating entity and the BS 305b and UE 315b1-315b2 of the second network operating entity are NR unlicensed (NR-U) devices. In some other aspects, the first network operating entity may utilize a different RAT from the second network operating entity. For example, the BS 305a and UE 315a1-315a4 of the first network operating entity may utilize NR-U technology, while the BS 305b and UE 315b1-315b2 of the second network operating entity may utilize WiFi or LAA technology.

[0066] In network 300, some UEs in UE 315a1-315a4 can communicate with each other in peer-to-peer communication. For example, UE 315a1 can communicate with UE 315a2 through side link 352, UE 315a3 can communicate with UE 315a4 through another side link 351, and UE 315b1 can communicate with UE 315b2 through another side link 354. Side links 351, 352 and 354 are unicast bidirectional links. Some UEs in UE 315 can also communicate with BS 305a or BS 305b in UL direction and / or DL ​​direction via communication link 353. For example, UE 315a1, 315a3 and 315a4 are in the coverage area 310 of BS 305a, and therefore can communicate with BS 305a. UE 315a2 is outside the coverage area 310, and therefore can not communicate directly with BS 305a. In some instances, UE 315a1 may operate as a repeater for UE 315a2 to reach BS 305a. Similarly, UE 315b1 is within the coverage area 312 of BS 305b and may therefore communicate with BS 305b and may operate as a repeater for UE 315b2 to reach BS 305b. In some aspects, some of UEs 315 are associated with vehicles (e.g., similar to UEs 115i-115k), and the communications conducted through side links 351, 352, and 354 may be C-V2X communications. C-V2X communications may refer to communications between a vehicle and any other wireless communication device in a cellular network.

[0067] Figure 41 illustrates sidelink resources associated with a wireless communication network 400 according to some aspects of the present disclosure. The wireless communication network 400 may include a base station 105a and UEs 115a, 115b, and 115c, which may be as described in reference Figure 1 105 and UE 115. Base station 105a and UE 115a and 115c may communicate within geographic coverage area 110a and via communication links 405a and 405b, respectively. UE 115c may communicate with UE 115a and 115b via sidelink communication links 410a and 410b, respectively. In some examples, UE 115c may send sidelink control information (SCI) to UE 115a and 115b via sidelink control resources 420. SCI may include an indication of resources (e.g., reserved resources 425) reserved for retransmission by UE 115c. In some examples, UE 115a and 115b may determine to reuse one or more reserved resources in reserved resources 425.

[0068] In some aspects, a device (e.g., a UE 115, a base station (BS) 105, or some other node) in the wireless communication network 400 may convey SCI to another device (e.g., another UE 115, a BS 105, a sidelink device or a vehicle-to-everything (V2X) device, or other node). The SCI may be conveyed in one or more stages. The first-level SCI may be carried on the PSCCH 435, and the second-level SCI may be carried on the corresponding PSSCH 430. For example, UE 115c may send a PSCCH / first-level SCI 435 (e.g., SCI-1) to each sidelink UE 115 in the network (e.g., UE 115a and 115b) via the sidelink communication link 410. The PSCCH / first-level SCI-1 435 may indicate resources reserved for retransmission by UE 115c (e.g., SCI-1 may indicate reserved resources 425 for retransmission). Each side link UE 115 can decode the first level SCI-1 to determine where the reserved resources 425 are located (e.g., to suppress the use of resources reserved for another side link transmission and / or reduce resource conflicts within the wireless communication network 400). Side link communication may include mode 1 operation, where UE 115 is located in the coverage area of ​​BS 105a. Under mode 1, UE 115 may receive a configuration grant from BS 105a, which defines the parameters for UE 115 to access the channel. Side link communication may also include mode 2 operation, where UE 115 operates autonomously from BS 105a and performs channel sensing to obtain access to the channel. In some aspects, during mode 2 side link operation, side link UE 115 may perform channel sensing to locate resources reserved for other side link transmissions. The first level SCI-1 may reduce the need to sense each channel. For example, the first level SCI-1 may include an explicit indication so that UE 115 can suppress blind decoding of each channel. The first level SCI-1 may be sent via the sidelink control resource 420. The sidelink control resource 420 may be a configured resource (e.g., a time resource or a frequency resource) sent via the PSCCH 435. In some examples, the PSCCH 435 may be configured to occupy a plurality of physical resource blocks (PRBs) within a selected frequency. The frequency may include a single subchannel 450 (e.g., 10, 12, 15, 30, 35, or some other number of RBs within the subchannel 450). The duration of the PSCCH 435 may be configured by the BS 105a (e.g., the PSCCH 435 may span 1, 2, 3, or some other number of symbols 455).

[0069] The first level SCI-1 may include one or more fields indicating the location of the reserved resources 425. For example, the first level SCI-1 may include, but is not limited to, a transport frequency domain resource allocation (FDRA), a time domain resource allocation (TDRA), a resource reservation period 445 (e.g., a period for repeating SCI transmission and corresponding reserved resources 425), a modulation and coding scheme (MCS) for the second level SCI-2 440, a beta offset value for the second level SCI-2 440, a demodulation reference signal (DMRS) port (e.g., one bit indicating the number of data layers), a physical sidelink feedback channel (PSFCH) overhead indicator, a priority, one or more additional reserved bits, or a combination thereof. The beta offset may indicate a coding rate for transmitting the second level SCI-2 440. The beta offset may indicate an offset to an MCS index. The MCS may be indicated by an index ranging from 0 to 31. For example, if the MCS is set to index 16 indicating a modulation order of 4 and a coding rate of 378, the β offset may indicate a value of 3, thereby setting the coding rate to 490 based on the MCS index 18. In some examples, the FDRA may be a number of bits in the first-level SCI-1 that may indicate the number of time slots 438 and the number of subchannels reserved for the reserved resources 425 (e.g., the receiving UE 115 may determine the location of the reserved resources 425 based on the FDRA by using the subchannels 450 including the PSCCH 435 and the first-level SCI-1 as a reference). The TDRA may be a number of bits in the first-level SCI-1 (e.g., 5 bits, 9 bits, or some other number of bits) that may indicate the number of time resources reserved for the reserved resources 425. In this regard, the first-level SCI-1 may indicate the reserved resources 425 to one or more sidelink UEs 115 in the wireless communication network 400.

[0070] In some aspects, UE 115a and UE 115c may be sidelink UEs. UE 115a may receive an indicator indicating a set of start times associated with a transmit opportunity (TXOP) from BS 105. UE 115a may receive an indicator indicating a set of start times associated with a TXOP from BS 105 in a physical downlink control channel (PDCCH), a physical broadcast channel (PBCH), a physical downlink shared channel (PDSCH), or other suitable channels. In some aspects, UE 115a may receive the indicator in downlink control information (e.g., DCI3_x or other DCI communication formats). UE 115a and 115c may operate in licensed and / or unlicensed bands. The set of start times may indicate a time at which UE 115a may begin to send communications (e.g., transport blocks (TBs)) to UE 115c after a listen-before-talk (LBT) process performed by UE 115a passes. In this way, the BS can increase the spatial diversity of the network in the shared frequency band and improve the overall performance of the network by using the starting time.

[0071] Figure 5 5 is a timing diagram illustrating a radio frame structure 500 according to some aspects of the present disclosure. The radio frame structure 500 may be used by a BS (such as BS 105) and a UE (such as UE 115) in a network (such as network 100) to communicate. Specifically, the BS may communicate with the UE using the time-frequency resources configured as shown in the radio frame structure 500. Figure 5 , the x-axis represents time in some arbitrary units, and the y-axis represents frequency in some arbitrary units. Transmit frame structure 500 includes radio frame 501. The duration of radio frame 501 can vary according to various aspects. In one example, radio frame 501 can have a duration of about ten milliseconds. Radio frame 501 includes M time slots 502, where M can be any suitable positive integer. In one example, M can be about 10.

[0072] Each time slot 502 includes a plurality of subcarriers 504 in frequency and a plurality of symbols 506 in time. The number of subcarriers 504 and / or the number of symbols 506 in the time slot 502 may vary according to various aspects, such as based on channel bandwidth, subcarrier spacing (SCS) and / or CP mode. One subcarrier 504 in frequency and one symbol 506 in time form one resource element (RE) 512 for transmission. A resource block (RB) 510 is formed by a plurality of consecutive subcarriers 504 in frequency and a plurality of consecutive symbols 506 in time.

[0073] In one example, a BS (e.g., Figure 1The BS 105 in the example may schedule the UE (eg, Figure 1 UE 115 in the UE 115) performs UL and / or DL ​​communication. Each time slot 502 can be time-divided into K TTIs 508. Each TTI 508 may include one or more symbols 506. The TTI 508 in the time slot 502 can have a variable length. For example, when the time slot 502 includes N symbols 506, the TTI 508 can have a length between one symbol 506 and (N-1) symbols 506. In some aspects, the TTI 508 can have a length of about two symbols 506, about four symbols 506, or about seven symbols 506. In some examples, the BS can schedule the UE with a frequency granularity of a resource block (RB) 510 (e.g., which includes about 12 subcarriers 504).

[0074] Fig. 6A and Figure 6B In-band SL and Uu conflict scenarios 600 , 650 are illustrated in accordance with aspects of the present disclosure. Fig. 6A A first conflict scenario 600 involving scheduled PSSCH reception 604 and scheduled PUSCH transmission 608 is illustrated. In scenario 600, the UE receives an SCI 602 indicating a grant of SL resources for PSSCH reception 604. The UE also receives a DCI 606 indicating a grant of UL resources for PUSCH transmission 608. The PSSCH reception 604 and the PUSCH transmission 608 overlap at least partially in time. In addition, the SL resource pool associated with the PSSCH 604 can be in the same frequency band as the frequency resources (e.g., CC) associated with the PUSCH transmission 608. Therefore, the PSSCH reception 604 and the PUSCH transmission can be scheduled in at least partially overlapping time periods and on frequency resources in the same frequency band.

[0075] Figure 6BA second conflict scenario 650 involving scheduled PSSCH transmission 610 and PDSCH reception 612 is illustrated. Similar to scenario 600, the scheduled PSSCH transmission 610 and PDSCH reception 612 may be scheduled on in-band frequency resources in at least partially overlapping time periods. In scenario 650, the UE receives a DCI scheduling PDSCH reception 612 on a Uu BWP. As described above, in some aspects, the UE may not be configured to simultaneously receive and transmit communications on an in-band frequency carrier. The scheduling conflict between the above-mentioned SL communication and Uu communication may be resolved to avoid or prevent simultaneous in-band reception and transmission. The present disclosure describes methods, schemes, and mechanisms for resolving scheduling conflicts between in-band SL communication and Uu communication with different link directions (e.g., reception and transmission). Various aspects of the present disclosure may be performed by one or more UEs and / or one or more network entities or devices. For example, various aspects of the present disclosure may be performed by a CU or DU of a BS and / or a decomposed BS.

[0076] Figure 7 is a signaling diagram of a communication method according to some aspects of the present disclosure. The method 700 is performed by a network entity 105, a first UE 115a, and a second UE 115b. In some aspects, the network entity 105 may be part of a base station or a decomposed base station. In some aspects, the network entity 105 may include or represent a plurality of network devices or entities, for example, the network entity 105 may include or represent a centralized unit (CU), a distributed unit (DU), and / or any other suitable network device or entity.

[0077] At action 702, the network entity 105 sends a first time domain configuration for a Uu component carrier (CC), and the first UE 115a receives the first time domain configuration. In some aspects, the first time domain configuration includes a first time division duplex (TDD) configuration for the Uu carrier. In other aspects, the first time domain configuration may include or indicate a subset of resources of the TDD previously received at the first UE 115a. For example, the first time domain configuration may indicate one or more downlink (DL) time slots, one or more uplink (UL) time slots, and / or one or more flexible (F) time slots. In some aspects, the first time domain configuration may indicate one or more DL symbols of a time slot, one or more UL symbols of a time slot, and / or one or more flexible symbols of a time slot.

[0078] The first time domain configuration may be static, semi-static and / or dynamic. For example, in some aspects, receiving the first time domain configuration may include receiving a radio resource control (RRC) information element (IE) indicating one or more time slots and / or a symbol pattern for one or more time slots. The RRC IE may include a TDD mode index associated with a pattern of a DL time slot, an UL time slot and / or an F time slot. In some aspects, the first time domain configuration may be a cell-level configuration shared by multiple UEs operating in a cell. In another example, the first time domain configuration may be a dedicated configuration specific to a UE. On the other hand, receiving the first time domain configuration may include receiving downlink control information (DCI) dynamically indicating TDD. In some aspects, the DCI may include a DCI format 2_0. The DCI format 2_0 may include one or more slot format indicators (SFIs) for a group of UEs or for each UE (such as a UE of method 1400).

[0079] At action 704, the network entity 105 sends a second time domain configuration for a side link (SL) resource pool, and the first UE 115a receives the second time domain configuration. In some aspects, the second time domain configuration includes a second time division duplex (TDD) configuration for the SL resource pool. The second time domain configuration may include a bitmap, a SL grant, and / or a semi-static configuration. The second time domain configuration may be carried or indicated in an RRC IE, a DCI, and / or any other suitable communication.

[0080] In some aspects, the Uu CC and the SL resource pool are in the same frequency band. In some aspects, the SL resource pool may be referred to as an SLCC, a SL carrier and / or an SL bandwidth part (BWP). In some aspects, the Uu CC and the SL resource pool may be described as in-band. However, it should be understood that in some aspects, the Uu CC and the SL resource pool may not overlap in frequency. In other aspects, the Uu CC and the SL resource pool may overlap at least partially in frequency. In some aspects, the SL resource pool may include an unlicensed frequency resource set. In some aspects, the Uu CC may include one or more licensed component carriers or frequency bands. In other aspects, both the SL resource pool and the Uu CC are in an unlicensed frequency band.

[0081] At action 706, the network entity 105 sends a communication signal, and the first UE 115a receives the communication signal. The communication signal may include, for example, a DCI and an RRC information element and / or any other suitable communication. In some aspects, the communication signal sent at action 706 includes additional time domain and / or priority information used by the first UE 115a to determine the priority of conflicting communications. For example, the DCI may include a grant for Uu resources, a grant for SL resources, a slot format indicator (SFI), or an indicator that the flexible time resources are assigned as DL resources, UL resources, or SL resources. Additional details of the communication signal of action 706 will be described below and with respect to Figures 8 to 11 to describe.

[0082] At action 708, method 700 includes the first UE 115a determining the in-band priority of the first communication and the second communication based on the first time domain configuration, the second time domain configuration, the in-band priority configuration, and the communication signal of action 706. In some aspects, the second communication may be scheduled so that it overlaps at least partially with the first communication. In some aspects, one of the first communication or the second communication includes SL communication in the first link direction. On the other hand, the other of the first communication or the second communication includes Uu communication in the second link direction opposite to the first link direction. In some aspects, the first link direction is a sending direction and the second link direction is a receiving link direction.

[0083] In some aspects, the first communication and the second communication may be described as conflicting in time, wherein the first communication and the second communication are scheduled and / or configured to be communicated in the same time period. In some instances, the first communication and the second communication may overlap only partially. In other instances, the first communication and the second communication completely overlap in time. Because the first communication is associated with the first link direction and the second communication is associated with the second link direction opposite to the first link direction, the first communication and the second communication may not be communicated at the same time. In this regard, the UE may not be able to or be configured to send Uu communication while receiving SL communication, and vice versa. The in-band priority configuration may be a termination indication or provide a relative priority of the first communication and the second communication. For example, in some aspects, the in-band priority configuration may include or indicate one or more rules for resolving conflicts between Uu communication and the first link direction and SL communication and the second link direction, and in particular when the first communication and the second communication are scheduled on the in-band frequency resources. In some aspects, the in-band priority configuration may be a static configuration or a hard-coded configuration, in other words, the in-band configuration may be a pre-configured configuration at the UE. In some aspects, in-band configuration may include a set of rules, protocols, and / or architecture for resolving conflicts between the first communication and the second communication based on one or more parameters of each of the first communication and the second communication.

[0084] Figures 8 to 11 Various schemes for determining in-band priority of a first communication and a second communication are illustrated, wherein the first communication and the second communication are scheduled for overlapping time periods in in-band frequency resources and in different link directions (Rx and Tx). Figures 8 to 11 The scheme of can illustrate aspects of actions 706 and 708 of method 700. For example, the type and / or content of the communication signal conveyed at action 706 is important for the following description of the communication signal. Figures 8 to 11 Each of the scenarios described in may be different.

[0085] Figure 8 A scheme 800 is shown for determining the relative priority of a first communication and a second communication according to the method 700. In the scheme 800, the first time domain configuration may be a Uu TDD 810 for SL mode 1 operation. The UE may communicate multiple communications 820 based on the Uu TDD 810. The communication 820 includes multiple DL communications and SL communications 822. In some aspects, the communication signal communicated at action 706 may be a DCI indicating a SL grant 830 for the SL communication 822. The first communication may be a SL communication indicated by the SL grant 830. The in-band priority configuration may indicate or cause the UE to prioritize the SL communication based on the DCI indicating the grant of SL resources. In some aspects, the DCI may include DCI format 3_0. In some aspects, the in-band priority configuration may indicate that the granted SL communication has a higher priority than any or all Uu communications. In other aspects, the in-band priority configuration may indicate that the dynamically granted Uu communication has a higher priority than the dynamically granted SL communication. In some aspects, the in-band priority configuration may indicate that semi-statically or statically configured Uu communications have a lower priority than dynamically granted SL communications. In some aspects, if the UE receives both a DCI format 3_0 indicating a SL grant 830 and another DCI indicating a Uu grant, the UE may treat this scenario as an error condition. Therefore, the in-band priority of granted SL communications and Uu communications may be based on UE specific implementation. In some aspects, the UE may be configured to prioritize SL communications over Uu communications in error conditions. In other aspects, the UE may be configured to prioritize Uu communications in error conditions.

[0086] The SL grant 830 may be a grant for SL transmission. Based on receiving the SL grant 830 for SL transmission, the UE may not receive DL communications in the Uu CC in the time resources associated with the SL grant 830. On the other hand, the SL grant 830 may include or indicate a reverse link SL grant for SL reception. In this regard, in some aspects, the SL grant may be a forward link or a reverse link. The forward link may refer to a side link in the transmission direction from the relay UE to the remote UE. The reverse link may refer to a side link in the transmission direction from the remote UE to the relay UE. For example, the remote UE may be pre-configured with a side link resource pool for reverse link transmission, and the relay UE may send side link resource pool information to the remote UE to control resource usage in the side link resource pool. For example, the side link resource pool may include a resource set that may be used by the remote UE for side link transmission via the reverse link. The side link resource pool information may include a variety of parameters that may control how the remote UE selects resources for reverse link transmission from the resource set. With respect to scheme 800, the reverse link in the SL grant 830 may indicate Rx resources for communication 822 from the second SL UE to the UE.

[0087] In some aspects, a reverse link grant may refer to a grant from the network via a network entity to a SL UE indicating resources for receiving SL communications to the UE. Based on receiving the reverse link SL grant 830, the UE may refrain from sending UL communications in the Uu CC in the time resources associated with the grant 830.

[0088] Fig. 9A scheme 900 for determining the relative priority of a first communication and a second communication according to the method 700 is shown. In the scheme 900, the first time domain configuration may include a Uu TDD 910. The Uu TDD 910 may include a flexible resource set 912 that may be configured for SL transmission or DL ​​reception. In some aspects, the communication signal received at action 706 includes an RRC configuration 922 indicating a flexible resource set for at least one of the first time domain configuration or the second time domain configuration. The scheme 900 may also include receiving a DCI 924 that verifies the flexible resource set 912 for SL transmission or DL ​​reception. For example, the flexible resources 912 may include DL time slots and / or flexible time slots as indicated in the first time domain configuration. In some aspects, the RRC configuration 922 that configures soft resources or flexible resources may indicate that the soft resources or flexible resources do not overlap or conflict with system information including a master information block (MIB) and / or a system information block (SIB). In some aspects, a DCI 924 may be received in a group common PDCCH to validate soft resources or flexible resources for SL communication or Uu communication. In other aspects, the DCI 924 may be received in a dedicated PDCCH. In some aspects, the DCI 924 may indicate a grant of DL resources to invalidate SL transmissions in DL resources that at least partially overlap with dynamically granted DL resources. In other aspects, if at least a portion of a SL transmission 926 in a hard configured DL resource overlaps with a UL granted resource, the network may communicate a DCI 924 indicating a UL grant to validate the SL transmission 926.

[0089] Fig.10A scheme 1000 for determining the relative priority of a first communication and a second communication according to the method 700 is shown. In the scheme 1000, the first time domain configuration 1010 may indicate one or more UL resources and one or more flexible resources. The flexible resource 1012 may be continuous with the UL resource in time. On the other hand, the flexible resource 1012 may be separated from the UL resource in time. The scheme 1000 may also include receiving an SFI 1002 indicating that at least a portion of the flexible resource 1012 includes an additional UL resource 1014. In other words, the SFI 1002 may convert the flexible resource 1012 into an additional UL resource 1014. In some aspects, the UE may send a SL communication using the UL resource and the additional UL resource 1014 based on the SFI 1002. Therefore, the SL resource pool 1020 may be extended by the SFI 1002. For example, the network may provide the Uu TDD configuration 1010 to the UE via a network entity. The SL resource pool 1020 may be limited to UL time slots and flexible time slots or UL symbols and flexible symbols. If SFI is configured and SL resources overlap with flexible Uu symbols, flexible Uu symbols may also be used for SL if SFI 1002 indicates that the flexible symbol is a UL symbol. In some aspects, SFI 1002 may extend SL Rx resources. On the other hand, SFI 1002 may extend SL Tx resources. In some aspects, SL resources may overlap with at least one flexible symbol. The UE may be configured to monitor sidelink control information (SCI) even if the DCI including the SFI has not yet been received and / or decoded. In other aspects, Rx SL resources may be limited to DL slots and flexible slots and DL symbols and flexible symbols. In some aspects, if SFI 1002 confirms that the flexible symbol is a DL symbol, the UE may use flexible resources.

[0090] Fig.11A scheme 1100 for determining the relative priority of a first communication and a second communication according to method 700 is shown. In scheme 1100, a first time domain configuration 1110 may indicate a plurality of DL time slots. Method 700 may also include performing one or more listen before talk (LBT) and sending one or more LBT success reports based on the LBT. According to scheme 1100, the UE may send an LBT success report 1122 to the network. Scheme 1100 may also include the UE receiving an RRC IE 1124 including or indicating a resource splitting configuration based on the LBT success report 1122. The resource splitting configuration may indicate that a portion of a plurality of DL time slots is allocated for SL transmission or DL ​​reception. In some aspects, the UE may convey the first communication based on the resource splitting configuration. In some aspects, the LBT success report 1122 may indicate an LBT success rate. The LBT success rate may be obtained by the UE by counting successful LBT attempts made for SL transmission in the past t seconds. In some aspects, the network (such as a network entity) may compare the LBT success rate with a threshold. In some aspects, if the LBT success rate is less than a threshold, the network may provide a resource splitting configuration indicating that the next N DL time slots 1112 are allocated for SL transmission and the remaining DL time slots 1114 are allocated for DL ​​reception. If the LBT success rate is greater than or equal to the threshold, the network may provide a resource splitting configuration indicating that the next N DL 1112 time slots are allocated for DL ​​reception and the remaining DL time slots 1114 are allocated for SL transmission.

[0091] On the other hand, the LBT success report 1122 may indicate an actual transmission rate. For example, the actual transmission rate may be obtained by the UE by counting the actual SL transmissions and dividing the number of actual SL transmissions by the number of successful LBT attempts for SL transmissions in the past t seconds. In some aspects, the network may compare the actual transmission rate with a threshold. For example, if the network entity determines that the actual transmission rate is less than the threshold, the resource splitting configuration may indicate that the next N DL time slots 1112 can be used for SL transmission, and the remaining DL time slots 1114 can be used for DL ​​reception. If the network entity determines that the actual transmission rate is greater than or equal to the threshold, the resource splitting configuration may indicate that the next N DL time slots 1112 can be used for DL ​​reception, and the remaining DL time slots 1114 can be used for SL transmission. In some aspects, the network may be configured to suppress sending DL communications in symbols allocated for SL transmission by the resource splitting configuration.

[0092] refer to Figure 7According to another aspect, the in-band priority configuration may indicate the priority of in-band SL and Uu communications for the conflict based on the service priority of each conflicting communication. For example, the in-band priority configuration may indicate a first in-band priority for a first service priority associated with a first communication and a second in-band priority for a second service priority associated with a second communication. In some aspects, the communication signal communicated at action 706 may include a DCI for scheduling Uu communication or SL communication. On the other hand, the communication signal communicated at action 706 may include an SCI for scheduling SL transmission and / or SL reception. In one example, for cross-slot scheduling, the in-band priority may be based on whether an ultra-reliable low-latency communication (URLLC) priority threshold is configured or provided. For example, the in-band priority of conflicting in-band SL and Uu communications may be based on whether sl-PriorityThreshold-DL-URLLC is configured. If sl-PriorityThreshold-DL-URLLC is configured, and if one of the first communication or the second communication includes DL URLLC service, then when the priority value of SL transmission is less than sl-PriorityThreshold-DL-URLLC, SL transmission may have a higher in-band priority than the scheduled DL URLLC configuration. It should be understood that a smaller priority value may indicate a higher communication priority. For example, a communication with a priority value of 1 may have a higher priority than a communication with a priority of 2. Otherwise, DL URLLC communication may have a higher in-band priority. The UE may be configured to suppress the communication of lower in-band priority communications. If sl-PriorityThreshold-DL-URLLC is not configured, DL URLLC transmission may have a higher priority. In addition, if the conflicting DL communication does not include URLLC service, then when the priority value of SL transmission is less than the side link priority threshold, the in-band priority configuration may indicate that SL transmission has a higher priority than DL reception. For example, the UE may be configured with sl-PriorityThreshold-DL. If the priority value of SL transmission is less than sl-PriorityThreshold-DL, SL transmission may have a higher in-band priority. Otherwise, DL reception may have a higher priority. The UE may communicate communications with higher in-band priority and may suppress communications with lower in-band priority. On the other hand, the network may control which of SL communication or DL ​​communication is given priority at the UE by setting the priority value of SL communication and / or DL ​​communication relative to the threshold configured above.

[0093] return Figure 7, at action 710 / 712, the first UE 115a communicates a first communication with the network via the network entity 105. The dashed line represents an alternative or variant that may be provided by the method 700. For example, action 710 / 712 may involve receiving a DL communication from the network entity 105, sending a UL communication to the network entity 105, sending a SL communication to the second UE 115b, or receiving a SL communication from the second UE 115b. In some aspects, action 710 / 712 may involve or include suppressing communicating a second communication that conflicts with the first communication. As described above, communicating the first communication may be based on the first time domain configuration, the second time domain configuration, and the in-band priority configuration.

[0094] Fig.12 1 is a block diagram of an exemplary UE 1200 according to some aspects of the present disclosure. UE 1200 may be UE 115 in network 100 or 300 as discussed above. As shown, UE 1200 may include a processor 1202, a memory 1204, a conflict resolution module 1208, a transceiver 1210 (which includes a modem subsystem 1212 and a radio frequency (RF) unit 1214), and one or more antennas 1216. These elements may be coupled to each other, for example, via one or more buses and communicate with each other directly or indirectly.

[0095] The processor 1202 may include a central processing unit (CPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein. The processor 1202 may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0096] Memory 1204 may include cache memory (e.g., cache memory of processor 1202), random access memory (RAM), magnetoresistive RAM (MRAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory devices, hard drives, other forms of volatile and non-volatile memory, or a combination of different types of memory. In some examples, memory 1204 includes non-transitory computer-readable media. Memory 1204 may store instructions 1206. Instructions 1206 may include instructions that, when executed by processor 1202, cause processor 1202 to perform operations in conjunction with aspects of the present disclosure (e.g., Figures 7 to 11 and Fig.14Instructions 1206 may also be referred to as code. The terms "instructions" and "code" should be broadly interpreted to include any type of computer-readable statements. For example, the terms "instructions" and "code" may refer to one or more programs, routines, subroutines, functions, processes, etc. "Instructions" and "code" may include a single computer-readable statement or many computer-readable statements.

[0097] The conflict resolution module 1208 may be implemented via hardware, software, or a combination thereof. For example, the conflict resolution module 1208 may be implemented as a processor, circuit, and / or instruction 1206 stored in the memory 1204 and executed by the processor 1202 .

[0098] In some aspects, the conflict resolution module 1208 may be configured to perform Figures 7 to 11 and Fig.14 In this regard, the conflict resolution module 1208 may be configured to receive a first time domain configuration for a Uu component carrier (CC) and to receive a second time domain configuration for a SL resource pool. In some aspects, the Uu CC and the SL resource pool are within the same frequency band. In some aspects, the conflict resolution module 1208 may be configured to communicate a first communication in a first time period based on the first time domain configuration, the second time domain configuration, and the in-band priority configuration. In some aspects, the second communication is scheduled within at least a portion of the first time period, and one of the first communication or the second communication includes an SL communication in a first link direction. On the other hand, the other of the first communication or the second communication includes a Uu communication in a second link direction opposite to the first link direction.

[0099] As shown, the transceiver 1210 may include a modem subsystem 1212 and an RF unit 1214. The transceiver 1210 may be configured to communicate bidirectionally with other devices, such as BS 105 and / or UE 115. The modem subsystem 1212 may be configured to modulate and / or encode data from the memory 1204 and the conflict resolution module 1208 according to a modulation and coding scheme (MCS) (e.g., a low-density parity check (LDPC) coding scheme, a turbo coding scheme, a convolutional coding scheme, a digital beamforming scheme, etc.). The RF unit 1214 may be configured to process (e.g., perform analog-to-digital conversion or digital-to-analog conversion, etc.) the modulated / encoded data from the modem subsystem 1212 (for outbound transmissions) or transmissions originating from another source, such as UE 115 or BS 105. The RF unit 1214 may be further configured to perform analog beamforming in conjunction with digital beamforming. Although shown as integrated together in the transceiver 1210, the modem subsystem 1212 and the RF unit 1214 may be separate devices that are coupled together to enable the UE 1200 to communicate with other devices.

[0100] The RF unit 1214 may provide modulated and / or processed data (e.g., data packets (or more generally, data messages that may include one or more data packets and other information)) to the antenna 1216 for transmission to one or more other devices. The antenna 1216 may further receive data messages sent from other devices. The antenna 1216 may provide the received data messages for processing and / or demodulation at the transceiver 1210. The antenna 1216 may include multiple antennas of similar or different designs in order to maintain multiple transmission links. The RF unit 1214 may configure the antenna 1216.

[0101] In some examples, the UE 1200 may include multiple transceivers 1210 that implement different RATs (e.g., NR and LTE). In some examples, the UE 1200 may include a single transceiver 1210 that implements multiple RATs (e.g., NR and LTE). In some examples, the transceiver 1210 may include various components, where different combinations of the components may implement the RATs.

[0102] In some aspects, the processor 1202 can be coupled to the memory 1204, the conflict resolution module 1208, and / or the transceiver 1210. The processor 1202 can execute operating system (OS) code stored in the memory 1204 to control and / or coordinate the operation of the conflict resolution module 1208 and / or the transceiver 1210. In some aspects, the processor 1202 can be implemented as part of the conflict resolution module 1208.

[0103] Fig.131 is a block diagram of an exemplary BS 1300 according to some aspects of the present disclosure. BS 1300 may be BS 105 as discussed above. As shown, BS 1300 may include a processor 1302, a memory 1304, a conflict resolution module 1308, a transceiver 1310 (which includes a modem subsystem 1312 and an RF unit 1314), and one or more antennas 1316. These elements may be coupled to each other, for example, via one or more buses and communicate with each other directly or indirectly.

[0104] The processor 1302 may have various features as a particular type of processor. For example, these features may include a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein. The processor 1302 may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0105] Memory 1304 may include cache memory (e.g., cache memory of processor 1302), RAM, MRAM, ROM, PROM, EPROM, EEPROM, flash memory, solid-state memory devices, one or more hard disk drives, memristor-based arrays, other forms of volatile and nonvolatile memory, or a combination of different types of memory. In some instances, memory 1304 may include non-transitory computer-readable media. Memory 1304 may store instructions 1306. Instructions 1306 may include instructions that, when executed by processor 1302, cause processor 1302 to perform the operations described herein (e.g., Figures 7 to 11 and Fig.15 Instructions 1306 may also be referred to as code, which may be broadly interpreted to include any type of computer-readable statements.

[0106] The conflict resolution module 1308 may be implemented via hardware, software, or a combination thereof. For example, the conflict resolution module 1308 may be implemented as a processor, circuit, and / or instruction 1306 stored in the memory 1304 and executed by the processor 1302 .

[0107] The conflict resolution module 1308 may be used in various aspects of the present disclosure, for example, Figures 7 to 11 and Fig.15In some aspects, the conflict resolution module 1308 may be configured to send a first time domain configuration for a Uu component carrier (CC) and a second time domain configuration for a SL resource pool. In some aspects, the Uu CC and the SL resource pool are in the same frequency band. In some aspects, the conflict resolution module 1308 may be configured to convey a first communication in a first time period based on the first time domain configuration, the second time domain configuration, and the in-band priority configuration. In some aspects, the second communication is scheduled within at least a portion of the first time period, and one of the first communication or the second communication includes an SL communication in a first link direction. On the other hand, the other of the first communication or the second communication includes a Uu communication in a second link direction opposite to the first link direction.

[0108] Additionally or alternatively, the conflict resolution module 1308 may be implemented in any combination of hardware and software, and in some implementations may involve, for example, the processor 1302, memory 1304, instructions 1306, transceiver 1310, and / or modem 1312.

[0109] As shown, the transceiver 1310 may include a modem subsystem 1312 and an RF unit 1314. The transceiver 1310 may be configured to communicate bidirectionally with other devices, such as UE 115 and / or UE 1200. The modem subsystem 1312 may be configured to modulate and / or encode data according to an MCS (e.g., an LDPC coding scheme, a turbo coding scheme, a convolutional coding scheme, a digital beamforming scheme, etc.). The RF unit 1314 may be configured to process (e.g., perform analog-to-digital conversion or digital-to-analog conversion, etc.) the modulated / encoded data from the modem subsystem 1312 (for outbound transmissions) or from another source, such as UE 115 or UE 1200. The RF unit 1314 may be further configured to perform analog beamforming in conjunction with digital beamforming. Although shown as being integrated together in transceiver 1310, modem subsystem 1312 and / or RF unit 1314 may be separate devices that are coupled together at BS 1300 to enable BS 1300 to communicate with other devices.

[0110] RF unit 1314 may provide modulated and / or processed data (e.g., data packets (or more generally, data messages that may include one or more data packets and other information)) to antenna 1316 for transmission to one or more other devices. For example, this may include a configuration indicating a plurality of sub-slots within a time slot, in accordance with aspects of the present disclosure. Antenna 1316 may further receive data messages transmitted from other devices and provide the received data messages for processing and / or demodulation at transceiver 1310. Antenna 1316 may include multiple antennas of similar or different designs in order to maintain multiple transmit links.

[0111] In some examples, the BS 1300 may include multiple transceivers 1310 that implement different RATs (e.g., NR and LTE). In some examples, the BS 1300 may include a single transceiver 1310 that implements multiple RATs (e.g., NR and LTE). In some examples, the transceiver 1310 may include various components, where different combinations of the components may implement the RATs.

[0112] In some aspects, the processor 1302 may be coupled to the memory 1304, the conflict resolution module 1308, and / or the transceiver 1310. The processor 1302 may execute OS code stored in the memory 1304 to control and / or coordinate the operation of the conflict resolution module 1308 and / or the transceiver 1310. In some aspects, the processor 1302 may be implemented as part of the conflict resolution module 1308. In some aspects, the processor 1302 is configured to send an indicator to the UE via the transceiver 1310 indicating the configuration of the sub-time slots within the time slot.

[0113] Fig.14 1400 is a flow chart of a communication method 1400 according to some aspects of the present disclosure. Various aspects of the method 1400 may be performed by a computing device (e.g., a processor, a processing circuit, and / or other suitable components) of a wireless communication device or other suitable means for performing these actions. For example, a wireless communication device (such as UE 115 or UE 1200) may utilize one or more components (such as a processor 1202, a memory 1204, a conflict resolution module 1208, a transceiver 1210, a modem 1212, and one or more antennas 1216) to perform various aspects of the method 1400. The method 1400 may employ mechanisms similar to those in networks 100 and 300 and with respect to Figures 7 to 11 As shown, method 1400 includes multiple enumerated actions, but method 1400 may include additional actions before, after, and between these enumerated actions. In some aspects, one or more of these enumerated actions may be omitted or performed in a different order.

[0114] At action 1410, method 1400 includes a UE (e.g., UE 115 or UE 1200) receiving a first time domain configuration for a Uu component carrier (CC). In some aspects, action 1410 includes the UE receiving the first time domain configuration from a network entity. For example, the UE may receive the first time domain configuration from a base station (BS). In some aspects, the network entity may include a portion of a decomposed BS. In some aspects, the first time domain configuration includes a first time division duplex (TDD) configuration for the Uu carrier. The first time domain configuration may indicate one or more downlink (DL) time slots, one or more uplink (UL) time slots, and / or one or more flexible (F) time slots. In some aspects, the first time domain configuration may indicate one or more DL symbols of a time slot, one or more UL symbols of a time slot, and / or one or more flexible symbols of a time slot.

[0115] The first time domain configuration may be static, semi-static and / or dynamic. For example, in some aspects, receiving the first time domain configuration may include receiving a radio resource control (RRC) information element (IE) indicating one or more time slots and / or a symbol pattern for one or more time slots. The RRC IE may include a TDD mode index associated with a pattern of a DL time slot, an UL time slot and / or an F time slot. In some aspects, the first time domain configuration may be a cell-level configuration shared by multiple UEs operating in a cell. In another example, the first time domain configuration may be a dedicated configuration specific to a UE. On the other hand, receiving the first time domain configuration may include receiving downlink control information (DCI) dynamically indicating TDD. In some aspects, the DCI may include a DCI format 2_0. The DCI format 2_0 may include one or more slot format indicators (SFIs) for a group of UEs or for each UE (such as a UE of method 1400).

[0116] At action 1420, method 1400 includes the UE receiving a second time domain configuration for a side link (SL) resource pool. In some aspects, action 1420 includes the UE receiving the second time domain configuration from a network entity. For example, the UE may receive the second time domain configuration from a base station (BS). In some aspects, the network entity may include a portion of a decomposed BS. In some aspects, the second time domain configuration includes a second time division duplex (TDD) configuration for the SL resource pool. The second time domain configuration may include a bitmap. On the other hand, the second time domain configuration may include a SL resource pool grant, a semi-static configuration, and / or any other suitable type of configuration. In some aspects, receiving the second time domain configuration may include receiving a SL grant from another UE or from a network device.

[0117] The second time domain configuration may be static, semi-static and / or dynamic. For example, in some aspects, receiving the second time domain configuration may include receiving a radio resource control (RRC) information element (IE) indicating one or more time slots and / or a symbol pattern for one or more time slots. The RRC IE may include or indicate a TDD mode index associated with a pattern of a DL time slot, an UL time slot and / or an F time slot. In some aspects, the second time domain configuration may be a cell-level configuration shared by multiple UEs operating in a cell. In another example, the second time domain configuration may be a dedicated configuration specific to a UE. On the other hand, receiving the second time domain configuration may include receiving downlink control information (DCI) dynamically indicating TDD. In some aspects, the DCI may include a DCI format 2_0. The DCI format 2_0 may include one or more slot format indicators (SFIs) for a group of UEs or for each UE (such as a UE of method 1400).

[0118] In some aspects, the Uu CC and the SL resource pool are in the same frequency band. In some aspects, the SL resource pool may be referred to as an SLCC, a SL carrier and / or an SL BWP. In some aspects, the Uu CC and the SL resource pool may be described as in-band. However, it should be understood that in some aspects, the Uu CC and the SL resource pool may not overlap in frequency. In other aspects, the Uu CC and the SL resource pool may overlap at least partially in frequency. In some aspects, the SL resource pool may include an unlicensed frequency resource set. In some aspects, the UuCC may include one or more licensed component carriers or frequency bands. In other aspects, both the SL resource pool and the Uu CC are in an unlicensed frequency band.

[0119] At action 1430, method 1400 includes the UE communicating the first communication in the first time period based on the first time domain configuration, the second time domain configuration, and the in-band priority configuration. In some aspects, the second communication is scheduled within at least a portion of the first time period. In other words, the second communication may be scheduled so that it overlaps at least partially with the first communication. In some aspects, one of the first communication or the second communication includes SL communication in the first link direction. On the other hand, the other of the first communication or the second communication includes Uu communication in the second link direction opposite to the first link direction. In some aspects, the first link direction is a sending direction and the second link direction is a receiving link direction. For example, communicating in the first link direction may include the UE sending UL communication or SL communication. Communicating in the second link direction may include the UE receiving DL communication or receiving SL communication. On the other hand, the first link direction is a receiving direction and the second link direction is a sending direction. Therefore, in some aspects, action 1430 includes the UE sending the first communication. On the other hand, action 1430 includes the UE receiving the first communication. The first communication may be Uu communication or SL communication.

[0120] Communicating the first communication may include receiving a DL signal or communication. For example, communicating the first communication may include receiving DCI, DL data in PDSCH, DL reference signals, synchronization signals, system information, broadcast information, and / or any other suitable DL communication. On the other hand, communicating the first communication may include sending a UL signal or communication. For example, communicating the first communication may include sending uplink control information (UCI), UL data in PUSCH, HARQ feedback information, UL reference signals, UL synchronization signals, and / or any other suitable type of communication. On the other hand, communicating the first communication may include receiving SL communication. For example, communicating the first communication may include receiving a physical sidelink control channel (PSCCH) signal, a physical sidelink shared channel (PSSCH) signal, and / or a physical sidelink feedback channel (PSFCH) signal. On the other hand, communicating the first communication may include sending SL communication. For example, communicating the first communication may include sending a PSCCH signal, a PSSCH signal, and / or a PSFCH signal. In other aspects, communicating the first communication may include sending or receiving a SL reference signal and / or a SL synchronization signal.

[0121] In some aspects, the first communication and the second communication may be described as conflicting in time, wherein the first communication and the second communication are scheduled and / or configured to be communicated in the same time period. In some instances, the first communication and the second communication may overlap only partially. In other instances, the first communication and the second communication completely overlap in time. Because the first communication is associated with the first link direction and the second communication is associated with the second link direction opposite to the first link direction, the conflicting communications may not be communicated at the same time. In this regard, the UE may not be able to or be configured to send Uu communication while receiving SL communication, and vice versa. The in-band priority configuration may be a termination indication or provide a relative priority of the first communication and the second communication. For example, in some aspects, the in-band priority configuration may include or indicate one or more rules for resolving conflicts between Uu communication and the first link direction and SL communication and the second link direction, and in particular when the first communication and the second communication are scheduled on the in-band frequency resources. In some aspects, the in-band priority configuration may be a static configuration or a hard-coded configuration, in other words, the in-band configuration may be a pre-configured configuration at the UE. In some aspects, the in-band configuration may include a set of rules, protocols, and / or architectures for resolving conflicts between the first communication and the second communication based on one or more parameters of each of the first communication and the second communication. For example, the in-band configuration may include or provide for the above-described Figures 7 to 11 The described scheme.

[0122] For example, in some aspects, the first communication may be a SL communication indicated by a grant of SL resources received in a DCI. The in-band priority configuration may indicate or cause the UE to prioritize SL communications based on the DCI indicating the grant of SL resources. In some aspects, the DCI may include DCI format 3_0. In some aspects, the in-band priority configuration may indicate that a granted SL communication has a higher priority than any or all Uu communications. In other aspects, the in-band priority configuration may indicate that a dynamically granted Uu communication has a higher priority than a dynamically granted SL communication. In some aspects, the in-band priority configuration may indicate that a semi-statically or statically configured Uu communication has a lower priority than a dynamically granted SL communication.

[0123] In some aspects, the first time domain configuration may indicate a flexible resource set that can be configured for SL transmission or DL ​​reception. In some aspects, the method 1400 also includes receiving a DCI from a network entity to verify the flexible resource set for SL transmission or DL ​​reception. For example, the flexible resources may include DL time slots and / or flexible time slots as indicated in the first time domain configuration. In this regard, the method 1400 may include the UE receiving a hard Uu TDD configuration including Uu DL time slots and / or symbols. In some aspects, the method may also include receiving a hard SL TDD configuration including hard SL Tx and / or Rx resources. Receiving the first time domain configuration may include receiving a DCI indicating flexible resources. In some aspects, the method 1400 may include receiving an RRC configuration for configuring soft resources or flexible resources for SL Tx and / or Uu DL from a network entity. In some aspects, the RRC configuration configuring the soft resources or flexible resources may indicate that the soft resources or flexible resources do not overlap or conflict with system information including a master information block (MIB) and / or a system information block (SIB). In some aspects, a DCI indicating soft resources or flexible resources may be received in a group common PDCCH. In other aspects, the DCI may be received in a dedicated PDCCH. In some aspects, the network may communicate a DCI indicating a grant of DL resources to invalidate SL transmissions in DL resources that at least partially overlap with dynamically granted DL resources. In other aspects, if at least a portion of a SL transmission in a hard configured DL resource overlaps with a UL granted resource, the network may communicate a DCI indicating a UL grant to validate the SL transmission.

[0124] On the other hand, the first time domain configuration may indicate one or more UL resources and one or more flexible resources. The flexible resources may be continuous with the UL resources in time. On the other hand, the flexible resources may be separated from the UL resources in time. Method 1400 may also include receiving an SFI indicating that at least a portion of the flexible resources includes additional UL resources. In some aspects, conveying the first communication includes sending SL communications using UL resources and additional UL resources based on the SFI. Therefore, the SL resource pool may be extended by the SFI. For example, the network may provide the Uu TDD configuration to the UE via a network entity. The SL resource pool may be limited to UL time slots and flexible time slots or UL symbols and flexible symbols. If the SFI is configured and the SL resources overlap with the flexible Uu symbols, the flexible Uu symbols may also be used for the SL when the SFI indicates that the flexible symbols are UL symbols. In some aspects, the SFI may extend the SL Rx resources. On the other hand, the SFI may extend the SL Tx resources. In some aspects, the SL resources may overlap with at least one flexible symbol. The UE may be configured to monitor sidelink control information (SCI) even if the DCI including the SFI has not yet been received and / or decoded. In other aspects, Rx SL resources may be restricted to DL slots and flexible slots and DL symbols and flexible symbols. In some aspects, if the SFI confirms that the flexible symbol is a DL symbol, the UE may use flexible resources.

[0125] In some aspects, the first time domain configuration may indicate a plurality of DL time slots. The method 1400 may also include performing one or more listen-before-talk (LBT) operations and sending one or more LBT success reports based on the LBT. The method 1400 may also include the network sending a resource splitting configuration based on the one or more LBT success reports, and the UE receiving the resource splitting configuration based on the one or more LBT success reports. The resource splitting configuration may indicate that a portion of a plurality of DL time slots is allocated for SL transmission or DL ​​reception. In some aspects, conveying the first communication may be further based on the resource splitting configuration. In some aspects, the resource splitting configuration may be a semi-static configuration. For example, the network may send an RRC information element (IE) including or indicating the resource splitting configuration to the UE. In some aspects, one or more LBT success reports may indicate an LBT success rate. The LBT success rate may be obtained by the UE by counting successful LBT attempts made for SL transmission in the past t seconds. In some aspects, the network (such as a network entity) may compare the LBT success rate with a threshold. In some aspects, if the LBT success rate is less than the threshold, the network may provide a resource splitting configuration indicating that the subsequent N DL time slots are allocated for SL transmission. If the LBT success rate is greater than or equal to the threshold, the network may provide a resource splitting configuration indicating that the next N DL time slots are allocated for DL ​​reception.

[0126] On the other hand, one or more LBT success reports may indicate an actual transmission rate. For example, the actual transmission rate may be obtained by the UE by counting the actual SL transmissions and dividing the number of actual SL transmissions by the number of successful LBT attempts for SL transmissions in the past t seconds. In some aspects, the network may compare the actual transmission rate with a threshold. For example, if the network entity determines that the actual transmission rate is less than the threshold, the resource splitting configuration may indicate that the next N DL time slots are available for SL transmission. If the network entity determines that the actual transmission rate is greater than or equal to the threshold, the resource splitting configuration may indicate that the next N DL time slots are available for DL ​​reception. In some aspects, the network may be configured to suppress sending DL communications in symbols allocated for SL transmission by the resource splitting configuration.

[0127] On the other hand, the in-band priority configuration may indicate the priority of the conflicting in-band SL and Uu communications based on the service priority of each conflicting communication. For example, the in-band priority configuration may indicate a first in-band priority for a first service priority associated with a first communication and a second in-band priority for a second service priority associated with a second communication. In one example, for cross-slot scheduling, the in-band priority may be based on whether a URLLC priority threshold is configured or provided. For example, the in-band priority of the conflicting in-band SL and Uu communications may be based on whether sl-PriorityThreshold-DL-URLLC is configured. If sl-PriorityThreshold-DL-URLLC is configured, and if one of the first communication or the second communication includes a DL URLLC service, then in the case where the priority value of the SL transmission is less than sl-PriorityThreshold-DL-URLLC, the SL transmission may have a higher in-band priority than the scheduled DL URLLC configuration. It should be understood that a smaller priority value may indicate a higher communication priority. For example, a communication with a priority value of 1 may have a higher priority than a communication with a priority of 2. Otherwise, the DL URLLC communication may have a higher in-band priority. The UE may be configured to suppress communicating lower in-band priority communications. If sl-PriorityThreshold-DL-URLLC is not configured, DL URLLC transmissions may have a higher priority. In addition, if the conflicting DL communications do not include URLLC services, the in-band priority configuration may indicate that SL transmission has a higher priority than DL reception when the priority value of SL transmission is less than the side link priority threshold. For example, the UE may be configured with sl-PriorityThreshold-DL. If the priority value of SL transmission is less than sl-PriorityThreshold-DL, SL transmission may have a higher in-band priority. Otherwise, DL reception may have a higher priority. The UE may communicate communications with higher in-band priority and may suppress communicating communications with lower in-band priority. On the other hand, the network may control which of SL communication or DL ​​communication is given priority at the UE by setting the priority value of SL communication and / or DL ​​communication relative to the threshold configured above.

[0128] Fig.1515 is a flow chart of a communication method 1500 according to some aspects of the present disclosure. Various aspects of method 1500 may be performed by a computing device (e.g., a processor, processing circuitry, and / or other suitable components) of a wireless communication device or other suitable means for performing such actions. For example, a wireless communication device (such as BS 105 or BS 1300) may utilize one or more components (such as processor 1302, memory 1304, conflict resolution module 1308, transceiver 1310, modem 1312, and one or more antennas 1316) to perform various aspects of method 1500. Method 1500 may employ mechanisms similar to those in networks 100 and 300 and with respect to Figures 7 to 11 As shown, method 1500 includes multiple enumerated actions, but method 1500 may include additional actions before, after, and between these enumerated actions. In some aspects, one or more of these enumerated actions may be omitted or performed in a different order.

[0129] At action 1510, method 1500 includes a network entity (e.g., BS 105, RU 240, DU 230, and / or CU 250) sending a first time domain configuration for a Uu component carrier (CC). In some aspects, action 1510 includes the network entity sending the first time domain configuration to the UE. In some aspects, the network entity may include a portion of a decomposed BS. In some aspects, the first time domain configuration includes a first time division duplex (TDD) configuration for the Uu carrier. The first time domain configuration may indicate one or more downlink (DL) time slots, one or more uplink (UL) time slots, and / or one or more flexible (F) time slots. In some aspects, the first time domain configuration may indicate one or more DL symbols of a time slot, one or more UL symbols of a time slot, and / or one or more flexible symbols of a time slot.

[0130] The first time domain configuration may be static, semi-static and / or dynamic. For example, in some aspects, sending the first time domain configuration may include sending a radio resource control (RRC) information element (IE) indicating one or more time slots and / or a symbol pattern for one or more time slots. The RRC IE may include a TDD mode index associated with a pattern of a DL time slot, an UL time slot and / or an F time slot. In some aspects, the first time domain configuration may be a cell-level configuration shared by multiple UEs operating in a cell. In another example, the first time domain configuration may be a dedicated configuration specific to a UE. On the other hand, sending the first time domain configuration may include sending downlink control information (DCI) that dynamically indicates TDD. In some aspects, the DCI may include a DCI format 2_0. The DCI format 2_0 may include one or more slot format indicators (SFIs) for a group of UEs or for each UE (such as a UE of method 1500).

[0131] At act 1520, method 1500 includes the network entity sending a second time domain configuration for a side link (SL) resource pool. In some aspects, act 1520 includes the network entity sending the second time domain configuration to the UE. In some aspects, the second time domain configuration includes a second time division duplex (TDD) configuration for the SL resource pool. The second time domain configuration may include a bitmap.

[0132] The second time domain configuration may be static, semi-static and / or dynamic. For example, in some aspects, sending the second time domain configuration may include sending a radio resource control (RRC) information element (IE) indicating one or more time slots and / or a symbol pattern for one or more time slots. The RRC IE may include a TDD mode index associated with a pattern of a DL time slot, an UL time slot and / or an F time slot. In some aspects, the second time domain configuration may be a cell-level configuration shared by multiple UEs operating in a cell. In another example, the second time domain configuration may be a dedicated configuration specific to a UE. On the other hand, sending the second time domain configuration may include sending downlink control information (DCI) that dynamically indicates TDD. In some aspects, the DCI may include a DCI format 2_0. The DCI format 2_0 may include one or more slot format indicators (SFIs) for a group of UEs or for each UE (such as a UE of method 1500).

[0133] In some aspects, the Uu CC and the SL resource pool are in the same frequency band. In some aspects, the SL resource pool may be referred to as an SLCC, a SL carrier and / or an SL BWP. In some aspects, the Uu CC and the SL resource pool may be described as in-band. However, it should be understood that in some aspects, the Uu CC and the SL resource pool may not overlap in frequency. In other aspects, the Uu CC and the SL resource pool may overlap at least partially in frequency. In some aspects, the SL resource pool may include an unlicensed frequency resource set. In some aspects, the UuCC may include one or more licensed component carriers or frequency bands. In other aspects, both the SL resource pool and the Uu CC are in an unlicensed frequency band.

[0134] At action 1530, method 1500 includes a network entity communicating a first communication in a first time period based on a first time domain configuration, a second time domain configuration, and an in-band priority configuration. In some aspects, the second communication is scheduled within at least a portion of the first time period. In other words, the second communication may be scheduled so that it overlaps at least partially with the first communication. In some aspects, the first communication includes Uu communication in a first link direction, and the second communication includes SL communication in a second link direction. In some aspects, the first link direction is a transmit direction and the second link direction is a transmit link direction. For example, communicating in the first link direction may include the network entity sending a DL communication or receiving a UL communication.

[0135] Method 1500 may include Figures 7 to 11 and aspects of the method 1400 described above. For example, conveying the first communication may include resolving a scheduling conflict between SL communications and Uu communications scheduled on intra-brand frequency resources. In some aspects, the method 1500 may include a network entity sending a communication signal to the UE to resolve the conflict. For example, the method 1500 may include sending a DCI, an RRC IE, and / or any other suitable communication that causes the UE to prioritize Uu communications (e.g., DL, UL) or SL communications (e.g., SL Tx, SL Rx).

[0136] Communicating the first communication may include sending a DL signal or communication. For example, communicating the first communication may include sending DCI, DL data in a PDSCH, a DL reference signal, a synchronization signal, system information, broadcast information, and / or any other suitable DL communication. On the other hand, communicating the first communication may include receiving a UL signal or communication. For example, communicating the first communication may include receiving UCI, UL data in a PUSCH, HARQ feedback information, a UL reference signal, a UL synchronization signal, and / or any other suitable type of communication.

[0137] Other aspects of the present disclosure include the following:

[0138] Aspect 1. A method for wireless communication performed at a user equipment (UE), the method comprising: receiving a first time domain configuration for a Uu component carrier (CC); receiving a second time domain configuration for a side link (SL) resource pool, wherein the Uu CC and the SL resource pool are within the same frequency band; and based on the first time domain configuration, the second time domain configuration and the in-band priority configuration, conveying a first communication in a first time period, wherein a second communication is scheduled within at least a portion of the first time period, wherein one of the first communication or the second communication includes SL communication in a first link direction, and wherein the other of the first communication or the second communication includes Uu communication in a second link direction opposite to the first link direction.

[0139] Aspect 2. According to the method according to Aspect 1, the method also includes: receiving downlink control information (DCI) indicating the grant of SL resources, wherein the first communication includes SL communication and the second communication includes Uu communication, and wherein conveying the first communication includes conveying the SL communication on the SL resource pool based on the grant of SL resources.

[0140] Aspect 3. The method according to aspect 2, wherein the in-band priority configuration indicates that the SL communication has a higher priority than all Uu communications.

[0141] Aspect 4. The method according to aspect 3, wherein the grant of SL resources comprises a dynamic grant sent for a SL in the SL resources.

[0142] Aspect 5. The method according to Aspect 3, wherein the grant of SL resources includes a reverse link grant received for a SL in the SL resources.

[0143] Aspect 6. The method according to aspect 2, wherein the in-band priority configuration indicates that the in-band priority of the second communication is based on whether the second communication is a dynamically granted Uu communication.

[0144] Aspect 7. The method according to aspect 6, wherein the grant of SL resources comprises a dynamic grant sent for a SL in the SL resources.

[0145] Aspect 8. The method according to Aspect 6, wherein the grant of SL resources includes a reverse link grant received for a SL in the SL resources.

[0146] Aspect 9. A method according to any one of Aspects 1 to 8, wherein the first time domain configuration indication is capable of configuring a flexible resource set for SL transmission or downlink (DL) reception, and wherein the method further includes: receiving downlink control information (DCI) from a network entity, and the downlink control information (DCI) verifies the flexible resource set used for SL transmission or DL ​​reception.

[0147] Aspect 10. A method according to any one of Aspects 1 to 9, wherein the first time domain configuration indicates one or more uplink (UL) resources and one or more flexible resources, wherein the method further includes: receiving a time slot format indicator (SFI), wherein the time slot format indicator (SFI) indicates that at least a portion of the one or more flexible resources includes additional UL resources, and wherein conveying the first communication includes: based on the SFI, using the UL resources and the additional UL resources to send SL communication.

[0148] Aspect 11. A method according to any one of Aspects 1 to 9, wherein the first time domain configuration indicates one or more uplink (UL) resources and one or more flexible resources, wherein the method further includes: receiving a time slot format indicator (SFI), wherein the time slot format indicator (SFI) indicates that at least a portion of the one or more flexible resources includes additional UL resources, and wherein conveying the first communication includes: based on the SFI, using the UL resources and the additional UL resources to monitor SL communication.

[0149] Aspect 12. A method according to any one of Aspects 1 to 9, wherein the first time domain configuration indicates one or more downlink (DL) resources and one or more flexible resources, wherein the method further includes: receiving a time slot format indicator (SFI), the time slot format indicator (SFI) indicating that at least a portion of the one or more flexible resources includes additional DL resources, and wherein conveying the first communication includes: based on the SFI, using the DL resources and the additional DL resources to receive SL communication.

[0150] Aspect 13. A method according to any one of Aspects 1 to 12, wherein the first time domain configuration indicates a plurality of downlink (DL) time slots, and wherein the method further comprises: sending a listen-before-talk (LBT) success report; and receiving a resource splitting configuration based on the LBT success report, the resource splitting configuration indicating that a portion of the plurality of DL time slots is allocated for SL transmission or DL ​​reception, and wherein conveying the first communication is further based on the resource splitting configuration.

[0151] Aspect 14. The method according to aspect 13, wherein the LBT success report indicates at least one of an LBT success rate or a sending rate.

[0152] Aspect 15. The method according to any one of aspects 1 to 14, wherein the in-band priority configuration indicates a first in-band priority for a first service priority of the first communication and a second in-band priority for a second service priority of the second communication.

[0153] 16. The method of clause 15, wherein the in-band priority configuration comprises an Ultra-Reliable Low Latency Communication (URLLC) priority threshold.

[0154] Aspect 17. The method according to Aspect 16, wherein conveying the first communication is further based on a comparison of the first service priority with the URLLC priority threshold.

[0155] Aspect 18. A method according to any one of Aspects 15 to 17, wherein the in-band priority configuration includes an ultra-reliable low-latency communication (URLLC) priority threshold, and wherein the in-band priority configuration indicates that DL URLLC communication has a higher in-band priority than SL communication.

[0156] Aspect 19. The method according to any one of aspects 15 to 18, wherein the in-band priority configuration includes a SL priority threshold, and wherein conveying the first communication is further based on a comparison of the first traffic priority with the SL priority threshold.

[0157] Aspect 20. The method according to any one of aspects 1 to 19, wherein communicating the first communication comprises: refraining from communicating the second communication during the first time period based on the first time domain configuration, the second time domain configuration, and the in-band priority configuration.

[0158] Aspect 21. A UE comprising a processor and a transceiver, wherein the UE is configured to perform the steps according to any one of aspects 1 to 20.

[0159] Aspect 22. A non-transitory computer-readable medium having program code recorded thereon, wherein the program code comprises instructions, and the instructions are executable by a processor of a UE to cause the UE to perform the steps according to any one of aspects 1 to 20.

[0160] Aspect 23. A UE comprising means for performing the steps according to any one of aspects 1 to 20.

[0161] Information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0162] The various illustrative blocks and modules described in conjunction with the disclosure herein may be implemented or executed using a general purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0163] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions may be stored as one or more instructions or codes on a computer-readable medium, or sent via a computer-readable medium. Other examples and specific implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described above may be implemented using software, hardware, firmware, hardware wiring, or any combination thereof executed by a processor. The features of the implementation functions may also be physically located at different locations, including being distributed so that the various parts of the functions are implemented at different physical locations. In addition, as used herein (including in the claims), "or" as used in a list of items (e.g., "or" used in a list of items ending with "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of [at least one of A, B, or C] means: A or B or C or AB or AC or BC or ABC (i.e., A and B and C).

[0164] As those skilled in the art will appreciate by now and depending on the specific application at hand, many modifications, substitutions and changes may be made to the materials, devices, configurations and methods of use of the apparatus of the present disclosure without departing from the spirit and scope of the present disclosure. In view of this, the scope of the present disclosure should not be limited to the scope of the specific examples illustrated and described herein (as they are only some examples thereof), but should be fully equivalent to the claims appended hereto and their functional equivalents.

Claims

1. A method of wireless communication performed at a user equipment (UE), the method comprising: receiving a first time domain configuration for a Uu component carrier (CC); receiving a second time domain configuration for a side link (SL) resource pool, wherein the Uu CC and the SL resource pool are in the same frequency band; and Based on the first time domain configuration, the second time domain configuration and the in-band priority configuration, a first communication is conveyed in a first time period, wherein a second communication is scheduled within at least a portion of the first time period, wherein one of the first communication or the second communication includes SL communication in a first link direction, and wherein the other of the first communication or the second communication includes Uu communication in a second link direction opposite to the first link direction.

2. The method according to claim 1, further comprising: receiving downlink control information (DCI) indicating a grant of SL resources, wherein the first communication comprises SL communication and the second communication comprises Uu communication, and Wherein communicating the first communication comprises communicating the SL communication over the SL resource pool based on the grant of SL resources.

3. The method of claim 2, wherein the in-band priority configuration indicates that the SL communication has a higher priority than all Uu communications. The method of claim 3 , wherein the grant of SL resources comprises a dynamic grant sent for a SL in the SL resources.

5. The method of claim 3, wherein the grant of SL resources comprises a reverse link grant received for a SL in the SL resources.

6. The method of claim 2, wherein the in-band priority configuration indicates that the in-band priority of the second communication is based on whether the second communication is a dynamically granted Uu communication.

7. The method of claim 6, wherein the grant of SL resources comprises a dynamic grant sent for a SL in the SL resources.

8. The method of claim 6, wherein the grant of SL resources comprises a reverse link grant received for a SL in the SL resources.

9. The method according to claim 1, wherein the first time domain configuration indicates a flexible resource set that can be configured for SL transmission or downlink (DL) reception, and wherein the method further comprises: Downlink control information (DCI) is received from a network entity, the downlink control information (DCI) verifying the flexible resource set for SL transmission or DL ​​reception.

10. The method of claim 1, wherein the first time domain configuration indicates one or more uplink (UL) resources and one or more flexible resources, The method further comprises: receiving a slot format indicator (SFI) indicating that at least a portion of the one or more flexible resources includes additional UL resources, and Wherein conveying the first communication comprises: sending a SL communication using the one or more UL resources and the additional UL resources based on the SFI.

11. The method of claim 1 , wherein the first time domain configuration indicates one or more uplink (UL) resources and one or more flexible resources, The method further comprises: receiving a slot format indicator (SFI) indicating that at least a portion of the one or more flexible resources includes additional UL resources, and Wherein communicating the first communication comprises: based on the SFI, monitoring SL communication using the one or more UL resources and the additional UL resources.

12. The method according to claim 1, wherein the first time domain configuration indicates one or more downlink (DL) resources and one or more flexible resources, The method further comprises: receiving a slot format indicator (SFI) indicating that at least a portion of the one or more flexible resources includes additional DL resources, and Wherein communicating the first communication comprises: receiving a SL communication using the one or more DL resources and the additional DL resources based on the SFI.

13. The method of claim 1, wherein the first time domain configuration indicates a plurality of downlink (DL) time slots, and wherein the method further comprises: Send Listen Before Talk (LBT) success report; as well as receiving a resource splitting configuration based on sending the LBT success report, the resource splitting configuration indicating that a portion of the plurality of DL time slots is allocated for SL transmission or DL ​​reception, and Wherein communicating the first communication is further based on the resource splitting configuration.

14. The method of claim 13, wherein the LBT success report indicates at least one of an LBT success rate or a sending rate.

15. The method of claim 1, wherein the in-band priority configuration indicates a first in-band priority for a first traffic priority for the first communication and a second in-band priority for a second traffic priority for the second communication.

16. The method of claim 15, wherein the in-band priority configuration comprises an Ultra Reliable Low Latency Communication (URLLC) priority threshold.

17. The method of claim 16, wherein conveying the first communication is further based on a comparison of the first traffic priority to the URLLC priority threshold.

18. The method of claim 15, wherein the in-band priority configuration comprises an Ultra Reliable Low Latency Communication (URLLC) priority threshold, and wherein the in-band priority configuration indicates that DL URLLC communications have a higher in-band priority than SL communications.

19. The method of claim 15, wherein the in-band priority configuration includes a SL priority threshold, and wherein conveying the first communication is further based on a comparison of the first traffic priority to the SL priority threshold.

20. The method of claim 1, wherein communicating the first communication comprises: Based on the first time domain configuration, the second time domain configuration, and the in-band priority configuration, communicating the second communication during the first time period is refrained.

21. A user equipment (UE), the user equipment (UE) comprising: processor; and transceiver, wherein the UE is configured to: receiving a first time domain configuration for a Uu component carrier (CC); receiving a second time domain configuration for a side link (SL) resource pool, wherein the Uu CC and the SL resource pool are in the same frequency band; and Based on the first time domain configuration, the second time domain configuration and the in-band priority configuration, a first communication is conveyed in a first time period, wherein a second communication is scheduled within at least a portion of the first time period, wherein one of the first communication or the second communication includes SL communication in a first link direction, and wherein the other of the first communication or the second communication includes Uu communication in a second link direction opposite to the first link direction.

22. The UE according to claim 21, wherein the UE is further configured to: receiving downlink control information (DCI) indicating a grant of SL resources, wherein the first communication comprises SL communication and the second communication comprises Uu communication, and The UE is configured to communicate the SL communication over the SL resource pool based on the grant of SL resources.

23. The UE according to claim 21, wherein the first time domain configuration indicates a flexible resource set that can be configured for SL transmission or downlink (DL) reception, and wherein the UE is further configured to: Downlink control information (DCI) is received from a network entity, the downlink control information (DCI) verifying the flexible resource set for SL transmission or DL ​​reception.

24. The UE according to claim 21, wherein the first time domain configuration indicates one or more uplink (UL) resources and one or more flexible resources, The UE is further configured as follows: receiving a slot format indicator (SFI) indicating that at least a portion of the one or more flexible resources includes additional UL resources, and Wherein the UE being configured to communicate the first communication includes the UE being configured to: communicate a SL communication using the UL resources and the additional UL resources based on the SFI.

25. The UE according to claim 21, wherein the first time domain configuration indicates one or more downlink (DL) resources and one or more flexible resources, The UE is further configured as follows: receiving a slot format indicator (SFI) indicating that at least a portion of the one or more flexible resources includes additional DL resources, and Wherein the UE being configured to communicate the first communication comprises the UE being configured to: communicate a SL communication using the one or more DL resources and the additional DL resources based on the SFI.

26. The UE of claim 21, wherein the first time domain configuration indicates a plurality of downlink (DL) time slots, and wherein the UE is further configured to: Send Listen Before Talk (LBT) success report; and receiving a resource splitting configuration based on the LBT success report, the resource splitting configuration indicating that a portion of the plurality of DL time slots is allocated for SL transmission or DL ​​reception, and Wherein the UE is configured to communicate the first communication further based on the resource splitting configuration.

27. The UE of claim 21, wherein the in-band priority configuration indicates a first in-band priority for a first traffic priority for the first communication and a second in-band priority for a second traffic priority for the second communication.

28. The UE of claim 27, wherein the in-band priority configuration comprises an Ultra Reliable Low Latency Communication (URLLC) priority threshold.

29. A non-transitory computer readable medium having program code recorded thereon, wherein the program code comprises instructions executable by a processor of a user equipment (UE) to cause the UE to: receiving a first time domain configuration for a Uu component carrier (CC); receiving a second time domain configuration for a side link (SL) resource pool, wherein the Uu CC and the SL resource pool are in the same frequency band; and Based on the first time domain configuration, the second time domain configuration and the in-band priority configuration, a first communication is conveyed in a first time period, wherein a second communication is scheduled within at least a portion of the first time period, wherein one of the first communication or the second communication includes SL communication in a first link direction, and wherein the other of the first communication or the second communication includes Uu communication in a second link direction opposite to the first link direction.

30. A user equipment (UE), the user equipment (UE) comprising: means for receiving a first time domain configuration for a Uu component carrier (CC); means for receiving a second time domain configuration for a side link (SL) resource pool, wherein the Uu CC and the SL resource pool are in the same frequency band; and A component for communicating a first communication in a first time period based on the first time domain configuration, the second time domain configuration, and an in-band priority configuration, wherein a second communication is scheduled within at least a portion of the first time period, wherein one of the first communication or the second communication comprises a SL communication in a first link direction, and wherein the other of the first communication or the second communication comprises a Uu communication in a second link direction opposite to the first link direction.

Images