Patent Description:
<NPL>, is a discussion and decision document discussing simultaneous transmission of SL and UL. <NPL>, is a discussion and decision document on the relationship between SL BWP and UuBWP. <NPL> is a discussion document on UL and SL prioritization for NR-V2X.

After considering this discussion, and particularly after reading the section entitled "Detailed Description" one will understand how the features of this disclosure provide advantages that include improved feedback signaling.

It is to be noted, however, that the appended drawings illustrate only certain typical aspects of this disclosure and are therefore not to be considered limiting of its scope.

Aspects of the present disclosure provide apparatus, methods, processing systems, and computer-readable mediums for configuring sidelink (SL) communication and uplink (UL) or downlink (DL) communication. A link between a user-equipment (UE) and a base station (BS) for UL or DL communication may also be referred to as a Uu link. In certain aspects, the BS may deploy a configuration for the SL and Uu link that allows for communications on the SL and Uu link to overlap in the time domain (e.g., simultaneous SL and Uu link communications). Certain aspects of the present disclosure provide conditions that may be considered by the BS for the deployment of the SL and Uu links that allow for concurrent SL and Uu link communications. If the deployment of the SL and Uu link by the BS does not allow for the SL and Uu link communications to overlap in the time domain, certain aspects provide techniques for handling such a scenario. For example, the UE may drop one of the SL and Uu link communications in accordance with a priority associated with the communications, as described in more detail herein. The aspects described herein provide increase communication efficiency by facilitating concurrent communications between UEs and between base stations.

The following description provides examples of configurations for concurrent SL communication and UL or DL communication in communication systems, and is not limiting of the scope, applicability, or examples set forth in the claims.

According to certain aspects, the BSs <NUM> and UEs <NUM> may be configured for concurrent SL communication and UL or DL communication. As shown in <FIG>, the UE 120a includes a configuration manager <NUM>. The configuration manager <NUM> may be configured to receive a first configuration for sidelink (SL) communication by the UE, receive a second configuration for uplink (UL) or downlink (DL) communication by the UE, determine whether the first configuration and the second configuration allow the UL or DL communication to overlap in time domain with the SL communication, and perform at least one of the SL communication or the UL or DL communication based on the determination. In certain aspects, the BS <NUM> may include a configuration manager <NUM> configured to determine a first configuration for SL communication by a UE, determining a second configuration for UL or DL communication by the UE, the first configuration and the second configuration being determined to allow the UL or DL communication to overlap in time domain with the SL communication, and transmitting the first configuration and the second configuration to the UE.

At the BS 110a, a transmit processor <NUM> may receive data from a data source <NUM> and control information from a controller/processor <NUM>. The transmit processor <NUM> may also generate reference symbols, such as for the primary synchronization signal (PSS), secondary synchronization signal (SSS), and cell-specific reference signal (CRS). A transmit (TX) multiple-input multiple-output (MIMO) processor <NUM> may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, and/or the reference symbols, if applicable, and may provide output symbol streams to the modulators (MODs) 232a-232t. Downlink signals from modulators 232a-232t may be transmitted via the antennas 234a-234t, respectively.

At the UE 120a, the antennas 252a-252r may receive the downlink signals from the BS 110a and may provide received signals to the demodulators (DEMODs) in transceivers 254a-254r, respectively. A MIMO detector <NUM> may obtain received symbols from all the demodulators 254a-254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor <NUM> may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 120a to a data sink <NUM>, and provide decoded control information to a controller/processor <NUM>.

On the uplink, at UE 120a, a transmit processor <NUM> may receive and process data (e.g., for the physical uplink shared channel (PUSCH)) from a data source <NUM> and control information (e.g., for the physical uplink control channel (PUCCH) from the controller/processor <NUM>. The symbols from the transmit processor <NUM> may be precoded by a TX MIMO processor <NUM> if applicable, further processed by the demodulators in transceivers 254a-254r (e.g., for SC-FDM, etc.), and transmitted to the BS 110a. At the BS 110a, the uplink signals from the UE 120a may be received by the antennas <NUM>, processed by the modulators <NUM>, detected by a MIMO detector <NUM> if applicable, and further processed by a receive processor <NUM> to obtain decoded data and control information sent by the UE 120a.

The controller/processor <NUM> and/or other processors and modules at the UE 120a may perform or direct the execution of processes for the techniques described herein. As shown in <FIG>, the controller/processor <NUM> of the UE 120a has a configuration manager <NUM> that may be configured to receive a first configuration for SL communication by the UE, receive a second configuration for UL or DL communication by the UE, determine whether the first configuration and the second configuration allow the UL or DL communication to overlap in time domain with the SL communication, and perform at least one of the SL communication or the UL or DL communication based on the determination. In certain aspects, the controller/processor <NUM> may include a configuration manager <NUM> configured to determine a first configuration for SL communication by a UE, determining a second configuration for UL or DL communication by the UE, the first configuration and the second configuration being determined to allow the UL or DL communication to overlap in time domain with the SL communication, and transmitting the first configuration and the second configuration to the UE. Although shown at the Controller/Processor, other components of the UE 120a and BS 110a may be used performing the operations described herein.

<FIG> show diagrammatic representations of example vehicle to everything (V2X) systems in accordance with some aspects of the present disclosure. For example, the UEs shown in <FIG> may communicate via sidelink channels and may perform sidelink CSI reporting as described herein.

The V2X systems, provided in <FIG> provide two complementary transmission modes. A first transmission mode, shown by way of example in <FIG>, involves direct communications (for example, also referred to as side link communications) between participants in proximity to one another in a local area. A second transmission mode, shown by way of example in <FIG>, involves network communications through a network, which may be implemented over a Uu interface (for example, a wireless communication interface between a radio access network (RAN) and a UE). As illustrated, UEs <NUM>, <NUM> may communicate with each other using a sidelink (SL) <NUM>.

Referring to <FIG>, a V2X system <NUM> (for example, including vehicle to vehicle (V2V) communications) is illustrated with two UEs <NUM>, <NUM> (e.g., vehicles). The first transmission mode allows for direct communication between different participants in a given geographic location. As illustrated, a vehicle can have a wireless communication link <NUM> with an individual (V2P) (for example, via a UE) through a PC5 interface. Communications between the UEs <NUM> and <NUM> may also occur through a PC5 interface <NUM>. In a like manner, communication may occur from a UE <NUM> to other highway components (for example, highway component <NUM>), such as a traffic signal or sign (V2I) through a PC5 interface <NUM>. With respect to each communication link illustrated in <FIG>, two-way communication may take place between elements, therefore each element may be a transmitter and a receiver of information. The V2X system <NUM> may be a self-managed system implemented without assistance from a network entity. A self-managed system may enable improved spectral efficiency, reduced cost, and increased reliability as network service interruptions do not occur during handover operations for moving vehicles. The V2X system may be configured to operate in a licensed or unlicensed spectrum, thus any vehicle with an equipped system may access a common frequency and share information. Such harmonized/common spectrum operations allow for safe and reliable operation.

<FIG> shows a V2X system <NUM> for communication between a UE <NUM> (e.g., vehicle) and a UE <NUM> (e.g., vehicle) through a network entity <NUM>. These network communications may occur through discrete nodes, such as a base station (for example, an eNB or gNB), that sends and receives information to and from (for example, relays information between) UEs <NUM>, <NUM>. The network communications through vehicle to network (V2N) links (e.g., Uu links <NUM> and <NUM>) may be used, for example, for long range communications between vehicles, such as for communicating the presence of a car accident a distance ahead along a road or highway. Other types of communications may be sent by the node to vehicles, such as traffic flow conditions, road hazard warnings, environmental/weather reports, and service station availability, among other examples. Such data can be obtained from cloud-based sharing services.

In some circumstances, two or more subordinate entities (for example, UEs) may communicate with each other using sidelink signals. As described above, V2V and V2X communications are examples of communications that may be transmitted via a sidelink. Other applications of sidelink communications may include public safety or service announcement communications, communications for proximity services, communications for UE-to-network relaying, device-to-device (D2D) communications, Internet of Everything (IoE) communications, Internet of Things (IoT) communications, mission-critical mesh communications, among other suitable applications. Generally, a sidelink may refer to a direct link between one subordinate entity (for example, UE1) and another subordinate entity (for example, UE2). As such, a sidelink may be used to transmit and receive a communication (also referred to herein as a "sidelink signal") without relaying the communication through a scheduling entity (for example, a BS), even though the scheduling entity may be utilized for scheduling or control purposes. In some examples, a sidelink signal may be communicated using a licensed spectrum (unlike wireless local area networks, which typically use an unlicensed spectrum).

Various sidelink channels may be used for sidelink communications, including a physical sidelink discovery channel (PSDCH), a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), and a physical sidelink feedback channel (PSFCH). The PSDCH may carry discovery expressions that enable proximal devices to discover each other. The PSCCH may carry control signaling such as sidelink resource configurations and other parameters used for data transmissions, and the PSSCH may carry the data transmissions. The PSFCH may carry feedback such as channel state information (CSI) related to a sidelink channel quality.

As described herein, two user equipments (UEs) may communicate over sidelink (SL), while one or both of the UEs may be in communication with a base station over Uu link (e.g., link between the UE and base station (BS)). As used herein, Uu link generally refers to uplink (UL) or downlink (DL). Both UEs may, at any given time, be instructed to transmit over SL and Uu link. In this case, the transmissions may collide (e.g., overlap) at least in the time domain. As used herein, simultaneous (or concurrent) transmissions (Tx) refer to the transmissions at least partially overlapping in the time domain, and simultaneous receptions (Rx) refers to receptions at least partially overlapping in the time domain.

In some cases, SL reception (and transmission) may only happen over semi-static U symbols (e.g., designated uplink symbols), while Uu reception may happen over D symbols (e.g., designated downlink symbols) and flexible symbols (e.g., symbols that may be configured for uplink or downlink). Thus, Uu and SL receptions may not collide in time in this case. However, one or more examples, SL Tx/Rx over the flexible symbols may be allowed. In such a case, the reception of signals on Uu and SL may collide. Further, for SL transmission, only Cyclic-Prefix Orthogonal Frequency Division Multiplexing (CP-OFDM) waveform may be allowed; however, for Uu Tx, both CP-OFDM and Discrete Fourier Transform (DFT) spread (DFT-S) may be used.

In some deployment scenarios, inter-frequency inter-band operations may be implemented. For example, for UEs with dual transmit (Tx)/receive (Rx) chains, it may be feasible for the UE to support simultaneous transmission/reception for both synchronous and asynchronous scenarios. However, not all combinations of source/target bands may be able to support simultaneous transmission/reception for synchronous and asynchronous scenarios.

In some cases, inter-frequency intra-band synchronous operations may be implemented. For example, it may be feasible for UEs supporting intra-band downlink (DL) carrier aggregation (CA) on frequencies supported for CA serving cells, to support simultaneous reception. Moreover, it may be feasible for UEs supporting intra-band UL CA on frequencies supported for CA serving cells, to support simultaneous transmission. It is unclear whether simultaneous Tx and/or Rx can be supported for inter-frequency intra-band asynchronous implementations.

In some cases, intra-frequency synchronous communication may be implemented. For example, simultaneous reception may be feasible for some UEs at least if the source/target bandwidths (e.g., for dual connectivity (DC)) are the same and under some conditions. Moreover, simultaneous transmission may be feasible for UEs with a single RF chain under some conditions. For intra-frequency asynchronous implementations, simultaneous reception may also be feasible for UEs with a single RF chain.

Certain aspects of the present disclosure are directed to configurations that allow a UE to communicate using a SL channel and UL and/or DL channel concurrently. A link between a UE and a BS for UL and DL communication may also be referred to as a Uu link. Certain aspects may be implemented for concurrent Rx and/or Tx for a UE with both synchronous and asynchronous deployments, as described in more detail herein. Synchronous SL and Uu link communication generally refer to a scenario where SL and Uu carriers (also referred to as component carriers) are co-located and the slot boundaries for the SL and Uu link are aligned within a small margin. Asynchronous SL and Uu link communication generally refer to a scenario where SL and Uu carriers are non-collocated.

Certain aspects of the present disclosure provide configurations for concurrent Tx/Rx communication for various implementations. The various implementations may include SL and Uu bandwidth parts (BWPs) being configured on the same carrier, or SL and Uu BWPs being configured on different carriers. Where the SL and Uu BWPs are configured on different carriers, the UE may use a single RF chain for Tx/RX on these carriers (e.g., intra-band contiguous carriers), or the UE may use more than a single RF chain for Tx/Rx on these carriers (e.g., intra-band non-contiguous or inter-band carriers). Depending on the implementation for SL and Uu link, the BS may configure the SL and Uu link based on one or more conditions that allow for the communications on SL and Uu link to overlap. These conditions may include using the same subcarrier spacing for the SL and Uu link, or using the same wave form for the SL or Uu link, as described in more detail herein.

<FIG> is a flow diagram illustrating example operations <NUM> for wireless communication, in accordance with certain aspects of the present disclosure. The operations <NUM> may be performed, for example, by a BS (e.g., such as the BS 110a in the wireless communication network <NUM>).

Operations <NUM> may be implemented as software components that are executed and run on one or more processors (e.g., controller/processor <NUM> of <FIG>). Further, the transmission and reception of signals by the BS in operations <NUM> may be enabled, for example, by one or more antennas (e.g., antennas <NUM> of <FIG>). In certain aspects, the transmission and/or reception of signals by the BS may be implemented via a bus interface of one or more processors (e.g., controller/processor <NUM>) obtaining and/or outputting signals.

The operations <NUM> may begin, at block <NUM>, with the BS determining a first configuration for SL communication by a UE, and at block <NUM>, determining a second configuration for UL or DL communication (e.g., via Uu link) by the UE. In certain aspects, the first configuration and the second configuration may be determined to allow the UL or DL communication (e.g., Uu link communication) to overlap in time-domain with the SL communication on the same or different carriers based on one or more conditions. At block <NUM>, the BS may transmit the first configuration and the second configuration to the UE.

In some aspects, if bandwidth parts (BWPs) for the UL or DL communication and the SL communication are on the same carrier, the first configuration and the second configuration may be determined based on the one or more conditions that the same sub-carrier spacing (SCS) is to be used for the UL or DL communication as the SL communication. In other words, SL and Uu BWPs may be configured on the same carrier, as described herein. In this case, to allow concurrent SL and Uu link communication, the SL SCS may be configured to be the same as the SCS of the UL BWP on the Uu.

<FIG> illustrates a communication scenario with concurrent transmissions by the UE on the SL <NUM> and the Uu link <NUM>, in accordance with certain aspects of the present disclosure. For simultaneous transmission, one or more conditions may apply when SL and Uu BWPs are on the same carrier. For example, the same waveform may be configured for the SL and Uu link. As described herein, the SL may only use OFDM. Thus, the configuration for the Uu link may also be set to OFDM. Otherwise, the UE may consider the configuration as an error case or use prioritization to drop one of the SL and Uu link communication, as described in more detail herein. Moreover, SL BWP may be configured within the Uu UL BWP. For a UE with multiple radio-frequency (RF) chains (also referred to as "chains") or UL multiple-input multiple-output (MIMO) capability, one or more of the conditions for concurrent SL and Uu link communication may be relaxed.

<FIG> illustrates a communication scenario with concurrent reception at the UE on the SL <NUM> and the Uu link <NUM>, in accordance with certain aspects of the present disclosure. One or more conditions may apply for configuring SL and Uu link communications for simultaneous reception. For example, the same SCS for the Uu link DL BWP and SL BWP may be configured.

In certain deployments, the SL and Uu BWP may be on different CCs and the UE may be configured with a single RF chain. In this case, various conditions may be applied for the configuration of concurrent SL or Uu link communication. For example, one or more conditions may apply to allow for simultaneous transmission (e.g., as illustrated in <FIG>) for synchronous communication. These conditions may include configuring the transmit timing via cells for the SL within a maximum transmitted time difference (MTTD) threshold. The MTTD threshold indicates a relative transmission timing difference among slot timing boundaries of different carriers for the SL and Uu link transmissions. The same SCS may be configured for Uu UL BWP on one carrier and SL on another carrier in certain aspects. For UEs, supporting UL CA with different SCSs in the same band or band combination, this condition may be relaxed, allowing the SCSs for the Uu UL BWP and the SL to be different.

In certain aspects, the same uplink waveform may be configured for the communications on the SL and Uu link. If the Uu and SL carriers/BWPs are configured with different waveforms, then either collision should be avoided by the scheduler (e.g., TDM only) or dropping rules may be considered, as described in more detail herein.

In certain aspects, the CCs that are configured for the SL and Uu link transmissions may be in the same timing advance group (TAG). Carriers in the same TAG may be associated with the same timing advance (TA). In certain aspects, the CCs configured for the SL and Uu link transmissions may be contiguous. Moreover, certain power control conditions may be considered when configuring the SL and Uu link transmissions. For example, the transmission power for the Uu UL and SL may be configured to be within a margin (e.g., also referred to herein as a threshold margin) or the average power per physical resource block (PRB) for the SL and Uu link transmissions may be aligned (e.g., configured to be the same) across assigned carriers.

In certain aspects, various conditions may be considered when configuring a UE in a manner as to allow simultaneous SL and Uu link reception in a synchronous scenario. For example, the configuration may be determined based on the condition that the SCS is the same for both cells used for the SL and Uu link reception at the UE. However, this condition may be relaxed for UEs that support DL CA with different SCSs in the same band or band combination. Violating the conditions may be considered as an error event or handled by prioritization, as described in more detail herein.

In certain aspects, SL and Uu BWP on different CCs and for UEs with a single chain (e.g., CCs are intra-band) may be implemented for an asynchronous scenario. For example, simultaneous transmission for an asynchronous scenario may be configured for UEs that support UL CA in the same band or band combination. If concurrent Tx/Rx is not feasible for a particular UE, then either the BS should avoid overlap of SL and Uu link communication in the time domain or such a configuration may be handled by the UE based on defining some priority rules for dropping one of the SL or Uu link communications.

In certain aspects, the SL and Uu BWPs may be on different CCs and the UE may be implemented with at least two RF chains (e.g., the different CCs are inter-band). In this case, certain conditions may apply for concurrent SL and Uu link communication. Simultaneous transmission/reception may be configured for both synchronous and asynchronous deployments. For simultaneous reception with an asynchronous deployment, a separation between the carrier frequencies may be configured. In other words, the carrier frequencies used for the SL and Uu link communications may be separated by a frequency band to reduce interference between the SL and the Uu links.

In some cases, the UE may indicate its capability for simultaneous transmission/reception to the BS. The capability of the UE may be indicated separately for various configuration candidates. For example, the UE may indicate its capability if both SL and Uu link are configured on frequency range <NUM> (FR1), if SL is configured on FR1 and Uu link is configured on FR2, and if the Uu link is configured on FR1 and the SL is configured on FR1. The BS may then consider the UEs' capability to handle simultaneous reception/transmission using SL and Uu links for a specific configuration to be deployed.

While certain aspects of the present disclosure have described conditions that allow concurrent communication on the SL and Uu link, there are scenarios where the BS may not configure the SL and Uu links in accordance with the conditions described herein. For example, for the Uu link, if Discrete Fourier Transform (DFT) spread (DFT-S) in the UL is configured, concurrent SL and Uu link communication may not be possible because SL may only support OFDM. Thus, the UE may expect to transmit using the SL and Uu link using non-overlapping time resources. For example, overlapping may be avoided by scheduling or time-division multiplexing (TDMing). In other words, the UE may consider an overlap of SL and Uu link communication as an error event if the configurations of the SL and the Uu link do not meet the conditions that allow for the overlap of communication in the SL and Uu link.

In certain aspects, the UE may consider prioritization rules for dropping one of the communications over the Uu link and the SL. For example, the prioritization rules may indicate that the Uu link communication has a higher priority than the SL, or vice versa. As another example, the prioritization may be based on configured priorities of channels on the SL and Uu link, or may be based on the type of channel on each of the SL and the Uu links.

<FIG> is a flow diagram illustrating example operations <NUM> for wireless communication, in accordance with certain aspects of the present disclosure. The operations <NUM> may be performed, for example, by UE (e.g., such as a UE 120a in the wireless communication network <NUM>).

Operations <NUM> may be implemented as software components that are executed and run on one or more processors (e.g., controller/processor <NUM> of <FIG>). Further, the transmission and reception of signals by the UE in operations <NUM> may be enabled, for example, by one or more antennas (e.g., antennas <NUM> of <FIG>). In certain aspects, the transmission and/or reception of signals by the UE may be implemented via a bus interface of one or more processors (e.g., controller/processor <NUM>) obtaining and/or outputting signals.

The operations <NUM> may begin, at block <NUM>, by receiving a first configuration for SL communication by the UE, at block <NUM>, receiving a second configuration for UL or DL communication by the UE. At block <NUM>, the UE may determine whether the first configuration and the second configuration allow the UL or DL communication to overlap in time-domain with the SL communication on same or different carriers based on one or more conditions, and at block <NUM>, communicate signaling for at least one of the SL communication or the UL or DL communication based on the determination.

In certain aspects, the UE may determine to forgo performing one of the SL communication and the UL or DL communication if the first configuration and the second configuration do not allow the UL or DL communication to overlap in the time domain with the SL communication. The determination to forgo performing one of the SL communication and the UL or DL communication may be based on a priority associated with each of the SL communication and the UL or DL communication.

<FIG> is a call-flow diagram illustrating example operations for SL or Uu communications, in accordance with certain aspects of the present disclosure. As illustrated, at block <NUM>, the BS may determine configurations <NUM> for SL and Uu link. The SL and Uu link configurations may be determined to allow the Uu link communication to overlap in time domain with the SL communication on same or different carriers based on one or more conditions, as described herein. As illustrated, the BS may transmit the configurations <NUM> to UE1 and UE1 may use the configurations <NUM> for communications <NUM> using the SL/Uu link with the BS and UE2.

In some aspects, UE1 may optionally transmit an indication of a capability <NUM> of UE1 with respect to the Uu link communication overlapping in the time domain with the SL communication, as described herein. For example, the capability may be indicated separately for different bands, band combinations, the Uu link communication and SL communication being synchronous, the Uu link communication and SL communication being asynchronous, or any combination thereof.

In this case, the determination at block <NUM> by the BS of the configurations <NUM> may be based on the capability of UE1.

In some aspects, after receiving the configurations <NUM>, the UE may, at block <NUM>, determine whether the configurations <NUM> allow for the overlap in time domain of the SL communication with the Uu link communication. If not, the UE may, at block <NUM>, prioritize one of the SL or Uu link communications. For example, if the SL communication has a lower priority as compared to the Uu link communication, UE1 may drop (e.g., forgo) one of the Uu link communication.

<FIG> illustrates multiple carriers used for SL and Uu link, in accordance with certain aspects of the present disclosure. In some implementations, multiple carriers (e.g., carrier <NUM> and carrier <NUM>) may be assigned to the same UE to support carrier aggregation. As described with respect to <FIG>, at block <NUM>, the BS may determine SL and Uu link configurations that allows for the Uu link communication to overlap in the time domain with the SL communication on same or different carriers based on one or more conditions. For example, if overlapping BWPs for the Uu link and the SL are on the same carrier, the configurations may be determined based on a condition that the same SCS is to be used for the Uu link and SL. Diagram <NUM> illustrates a SCS associated with multiple subcarriers (e.g., subcarriers <NUM>, <NUM>, <NUM>, <NUM>) allocated for the SL, and diagram <NUM> illustrates a SCS associated with multiple subcarriers (e.g., subcarriers <NUM>, <NUM>, <NUM>, <NUM>) allocated for the Uu link. As an example, if BWP <NUM> is used for the Uu link on carrier <NUM> and BWP <NUM> is used for the SL on the same carrier <NUM>, the BS may determine the configurations for SL and Uu link such that the SL and Uu link use the same SCS, as illustrated in diagrams <NUM>, <NUM>.

In some cases, the overlapping BWPs for the Uu link and the SL may be on different carriers. For example, BWP <NUM> may be used for the Uu link on carrier <NUM>, while BWP <NUM> may be used for SL on carrier <NUM>. As illustrated in <FIG>, a UE (e.g., UE <NUM>) may have a single RF chain (e.g., RF chain <NUM>), or multiple RF chains (e.g., both RF chain <NUM> and RF chain <NUM>). An RF chain is a cascade of electronic components (e.g., amplifiers, filters, mixers, attenuators, detectors) that facilitate transmission or reception of signals. If the UE has a single RF chain (e.g., RF chain <NUM>) and the BWPs for Uu link and SL are on different carriers, the configurations for the Uu link and the SL link may be determined based on the conditions described herein (e.g., the same SCS is to be used for the Uu link and SL, the same waveform is used for Uu link and SL, CCs for the Uu link and SL are contiguous, etc.).

The processing system <NUM> includes a processor <NUM> coupled to a computer-readable medium/memory <NUM> via a bus <NUM>. In certain aspects, the computer-readable medium/memory <NUM> is configured to store instructions (e.g., computer-executable code) that, when executed by the processor <NUM>, cause the processor <NUM> to perform the operations illustrated in <FIG>. In certain aspects, computer-readable medium/memory <NUM> stores code <NUM> (e.g., an example of means for) for determining, and code <NUM> (e.g., an example of means for) for transmitting. In certain aspects, computer-readable medium/memory <NUM> optionally stores code <NUM> (e.g., an example of means for) for communicating; and code <NUM> for receiving. One or more of code <NUM>, <NUM>, <NUM>, <NUM> may be executed by a general-purpose processor, a DSP, an ASIC, a field FPGA or other programmable logic device.

In certain aspects, the processor <NUM> has circuitry configured to implement the code stored in the computer-readable medium/memory <NUM>. The processor <NUM> includes circuitry <NUM> (e.g., an example of means for) for determining; and circuitry <NUM> for transmitting. The processor <NUM> may optionally include circuitry <NUM> (e.g., an example of means for) for communicating; and circuitry <NUM> (e.g., an example of means for) for receiving. One or more of circuitry <NUM>, <NUM>, <NUM>, <NUM> may be implemented by one or more of a general-purpose processor, a DSP, an ASIC, a FPGA or other programmable logic device. In certain aspects, processor <NUM> is an example of the configuration manager <NUM>.

The processing system <NUM> includes a processor <NUM> coupled to a computer-readable medium/memory <NUM> via a bus <NUM>. In certain aspects, the computer-readable medium/memory <NUM> is configured to store instructions (e.g., computer-executable code) that when executed by the processor <NUM>, cause the processor <NUM> to perform the operations illustrated in <FIG>. In certain aspects, computer-readable medium/memory <NUM> stores code <NUM> (e.g., an example of means for) for communicating; code <NUM> for receiving, and code <NUM> (e.g., an example of means for) for determining, and code <NUM> (e.g., an example of means for) for transmitting. In certain aspects, computer-readable medium/memory <NUM> optionally stores code <NUM> (e.g., an example of means for) for transmitting. One or more of code <NUM>, <NUM>, <NUM>, <NUM> may be executed by a general-purpose processor, a DSP, an ASIC, a field FPGA or other programmable logic device.

In certain aspects, the processor <NUM> has circuitry configured to implement the code stored in the computer-readable medium/memory <NUM>. The processor <NUM> includes circuitry <NUM> (e.g., an example of means for) for communicating; circuitry <NUM> (e.g., an example of means for) for receiving; circuitry <NUM> (e.g., an example of means for) for determining; and circuitry <NUM> for transmitting. The processor <NUM> may optionally include circuitry <NUM> for transmitting. One or more of circuitry <NUM>, <NUM>, <NUM>, <NUM> may be implemented by one or more of a general-purpose processor, a DSP, an ASIC, a FPGA or other programmable logic device. In certain aspects, processor <NUM> is an example of the configuration manager <NUM>.

The transceiver <NUM> or <NUM> may provide a means for receiving or transmitting information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to feedback, etc.). Information may be passed on to other components of the device <NUM> or <NUM>. The transceiver <NUM> or <NUM> may be an example of aspects of the transceiver <NUM> described with reference to <FIG>. The antenna <NUM> or <NUM> may correspond to a single antenna or a set of antennas. The transceiver <NUM> or <NUM> may provide means for transmitting signals generated by other components of the device <NUM> or <NUM>.

The configuration manager <NUM> or <NUM> may support wireless communication in accordance with examples as disclosed herein.

The configuration manager <NUM> or <NUM> may be an example of means for performing various aspects described herein. The configuration manager <NUM> or <NUM>, or its sub-components, may be implemented in hardware (e.g., in uplink resource management circuitry). The circuitry may comprise of processor, DSP, an ASIC, a FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in the present disclosure.

In another implementation, the configuration manager <NUM> or <NUM>, or its sub-components, may be implemented in code (e.g., as configuration management software or firmware) executed by a processor, or any combination thereof. If implemented in code executed by a processor, the functions of the configuration manager <NUM> or <NUM>, or its sub-components may be executed by a general-purpose processor, a DSP, an ASIC, a FPGA or other programmable logic device.

In some examples, the configuration manager <NUM> or <NUM> may be configured to perform various operations (e.g., receiving, determining, transmitting) using or otherwise in cooperation with the transceiver <NUM>, <NUM>.

The configuration manager <NUM> or <NUM>, or its sub-components, may be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations by one or more physical components. In some examples, the configuration manager <NUM> or <NUM>, or its sub-components, may be a separate and distinct component in accordance with various aspects of the present disclosure. In some examples, the configuration manager <NUM> or <NUM>, or its sub-components, may be combined with one or more other hardware components, including but not limited to an input/output (I/O) component, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof in accordance with various aspects of the present disclosure. The electromagnetic spectrum is often subdivided, based on frequency/wavelength, into various classes, bands, channels, etc. In <NUM> NR two initial operating bands have been identified as frequency range designations FR1 (<NUM> - <NUM>) and FR2 (<NUM> - <NUM>). It should be understood that although a portion of FR1 is greater than <NUM>, FR1 is often referred to (interchangeably) as a "Sub-<NUM>" band in various documents and articles.

The electromagnetic spectrum is often subdivided, based on frequency/wavelength, into various classes, bands, channels, etc. In <NUM> NR two initial operating bands have been identified as frequency range designations FR1 (<NUM> - <NUM>) and FR2 (<NUM> - <NUM>). It should be understood that although a portion of FR1 is greater than <NUM>, FR1 is often referred to (interchangeably) as a "Sub-<NUM>" band in various documents and articles.

For example, such a computer program product may comprise a computer-readable medium having instructions stored (and/or encoded) thereon, the instructions being executable by one or more processors to perform the operations described herein, for example, instructions for performing the operations described herein.

Claim 1:
A method (<NUM>) for wireless communication by a base station (<NUM>), comprising:
determining (<NUM>), at the base station (<NUM>), a first configuration for sidelink, SL, communication by a user-equipment, UE (<NUM>);
determining (<NUM>), at the base station (<NUM>), a second configuration for uplink, UL, or downlink, DL, communication by the UE, the first configuration and the second configuration being determined to allow the UL or DL communication to overlap in time domain with the SL communication on same or different carriers based on one or more conditions, wherein when bandwidth parts, BWPs, for the UL or DL communication and the SL communication are on different carriers and the different carriers are intra-band, the one or more conditions include transmit timing via cells associated with the SL communication and the UL or DL communication are within a maximum transmitted time difference, MTTD, threshold; and
transmitting (<NUM>) the first configuration and the second configuration to the UE (<NUM>).