Certain wireless networks (e.g., LTE) utilize orthogonal frequency division multiplexing (OFDM) on the downlink and single-carrier frequency division multiplexing (SC-FDM) on the uplink. OFDM and SC-FDM partition the system bandwidth into multiple (K) orthogonal subcarriers, which are also commonly referred to as tones, bins, etc. Each subcarrier may be modulated with data. In general, modulation symbols are sent in the frequency domain with OFDM and in the time domain with SC-FDM. The spacing between adjacent subcarriers may be fixed, and the total number of subcarriers (K) may be dependent on the system bandwidth. For example, the spacing of the subcarriers may be 15 kHz and the minimum resource allocation (called a “resource block” (RB)) may be 12 subcarriers (or 180 kHz). Consequently, the nominal Fast Fourier Transfer (FFT) size may be equal to 128, 256, 512, 1024 or 2048 for system bandwidth of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), respectively. The system bandwidth may also be partitioned into subbands. For example, a subband may cover 1.08 MHz (i.e., 6 resource blocks), and there may be 1, 2, 4, 8, or 16 subbands for system bandwidth of 1.25, 2.5, 5, 10 or 20 MHz, respectively.

While aspects of the examples described herein may be associated with LTE technologies, aspects of the present disclosure may be applicable with other wireless communications systems, such as NR. NR may utilize OFDM with a CP on the uplink and downlink and include support for half-duplex operation using TDD. Beamforming may be supported and beam direction may be dynamically configured. MIMO transmissions with precoding may also be supported. MIMO configurations in the DL may support up to 8 transmit antennas with multi-layer DL transmissions up to 8 streams and up to 2 streams per UE. Multi-layer transmissions with up to 2 streams per UE may be supported. Aggregation of multiple cells may be supported with up to 8 serving cells.

In some examples, access to the air interface may be scheduled, wherein a. A scheduling entity (e.g., a base station) allocates resources for communication among some or all devices and equipment within its service area or cell. The scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communication, subordinate entities utilize resources allocated by the scheduling entity. Base stations are not the only entities that may function as a scheduling entity. In some examples, a UE may function as a scheduling entity and may schedule resources for one or more subordinate entities (e.g., one or more other UEs), and the other UEs may utilize the resources scheduled by the UE for wireless communication. In some examples, a UE may function as a scheduling entity in a peer-to-peer (P2P) network, and/or in a mesh network. In a mesh network example, UEs may communicate directly with one another in addition to communicating with a scheduling entity.

In FIG. 1, a solid line with double arrows indicates desired transmissions between a UE and a serving BS, which is a BS designated to serve the UE on the downlink and/or uplink. A finely dashed line with double arrows indicates interfering transmissions between a UE and a BS.

FIG. 2 illustrates an example logical architecture of a distributed Radio Access Network (RAN) 200, which may be implemented in the wireless communication network 100 illustrated in FIG. 1. A 5G access node 206 may include an ANC 202. ANC 202 may be a central unit (CU) of the distributed RAN 200. The backhaul interface to the Next Generation Core Network (NG-CN) 204 may terminate at ANC 202. The backhaul interface to neighboring next generation access Nodes (NG-ANs) 210 may terminate at ANC 202. ANC 202 may include one or more TRPs 208 (e.g., cells, BSs, gNBs, etc.).

The TRPs 208 may be a distributed unit (DU). TRPs 208 may be connected to a single ANC (e.g., ANC 202) or more than one ANC (not illustrated). For example, for RAN sharing, radio as a service (RaaS), and service specific AND deployments, TRPs 208 may be connected to more than one ANC. TRPs 208 may each include one or more antenna ports. TRPs 208 may be configured to individually (e.g., dynamic selection) or jointly (e.g., joint transmission) serve traffic to a UE.

The logical architecture of distributed RAN 200 may support fronthauling solutions across different deployment types. For example, the logical architecture may be based on transmit network capabilities (e.g., bandwidth, latency, and/or jitter).

The logical architecture of distributed RAN 200 may share features and/or components with LTE. For example, next generation access node (NG-AN) 210 may support dual connectivity with NR and may share a common fronthaul for LTE and NR.

The logical architecture of distributed RAN 200 may enable cooperation between and among TRPs 208, for example, within a TRP and/or across TRPs via ANC 202. An inter-TRP interface may not be used.

Logical functions may be dynamically distributed in the logical architecture of distributed RAN 200. As will be described in more detail with reference to FIG. 5, the Radio Resource Control (RRC) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and a Physical (PHY) layers may be adaptably placed at the DU (e.g., TRP 208) or CU (e.g., ANC 202).

FIG. 3 illustrates an example physical architecture of a distributed RAN 300, according to aspects of the present disclosure. A centralized core network unit (C-CU) 302 may host core network functions. C-CU 302 may be centrally deployed. C-CU 302 functionality may be offloaded (e.g., to advanced wireless services (AWS)), in an effort to handle peak capacity.

A centralized RAN unit (C-RU) 304 may host one or more ANC functions. Optionally, the C-RU 304 may host core network functions locally. The C-RU 304 may have distributed deployment. The C-RU 304 may be close to the network edge.

A DU 306 may host one or more TRPs (Edge Node (EN), an Edge Unit (EU), a Radio Head (RH), a Smart Radio Head (SRH), or the like). The DU may be located at edges of the network with radio frequency (RF) functionality.

FIG. 4 illustrates example components of BS 110 and UE 120 (as depicted in FIG. 1), which may be used to implement aspects of the present disclosure. For example, antennas 452, processors 466, 458, 464, and/or controller/processor 480 of the UE 120 may be configured to perform (or cause UE 120 to perform) operations 1200 of FIG. 12 and/or antennas 434, processors 420, 460, 438, and/or controller/processor 440 of the BS 110 may be configured to perform (or cause BS 110 to perform) operations 1300 of FIG. 13, for PUSCH processing in the presence of ULCI.

At the BS 110, a transmit processor 420 may receive data from a data source 412 and control information from a controller/processor 440. The control information may be for the physical broadcast channel (PBCH), physical control format indicator channel (PCFICH), physical hybrid ARQ indicator channel (PHICH), physical downlink control channel (PDCCH), group common PDCCH (GC PDCCH), etc. The data may be for the physical downlink shared channel (PDSCH), etc. The processor 420 may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. The processor 420 may also generate reference symbols, e.g., 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 430 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) 432a through 432t. Each modulator 432 may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. Downlink signals from modulators 432a through 432t may be transmitted via the antennas 434a through 434t, respectively.

At the UE 120, the antennas 452a through 452r may receive the downlink signals from the base station 110 and may provide received signals to the demodulators (DEMODs) in transceivers 454a through 454r, respectively. Each demodulator 454 may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 456 may obtain received symbols from all the demodulators 454a through 454r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor 458 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 120 to a data sink 460, and provide decoded control information to a controller/processor 480.

On the uplink, at UE 120, a transmit processor 464 may receive and process data (e.g., for the physical uplink shared channel (PUSCH)) from a data source 462 and control information (e.g., for the physical uplink control channel (PUCCH) from the controller/processor 480. The transmit processor 464 may also generate reference symbols for a reference signal (e.g., for the sounding reference signal (SRS)). The symbols from the transmit processor 464 may be precoded by a TX MIMO processor 466 if applicable, further processed by the demodulators in transceivers 454a through 454r (e.g., for SC-FDM, etc.), and transmitted to the base station 110. At the BS 110, the uplink signals from the UE 120 may be received by the antennas 434, processed by the modulators 432, detected by a MIMO detector 436 if applicable, and further processed by a receive processor 438 to obtain decoded data and control information sent by the UE 120. The receive processor 438 may provide the decoded data to a data sink 439 and the decoded control information to the controller/processor 440.

The controllers/processors 440 and 480 may direct the operation at the BS 110 and the UE 120, respectively. The processor 440 and/or other processors and modules at the BS 110 may perform or direct the execution of processes for the techniques described herein. The memories 442 and 482 may store data and program codes for BS 110 and UE 120, respectively. A scheduler 444 may schedule UEs for data transmission on the downlink and/or uplink.

FIG. 5 illustrates a diagram 500 showing examples for implementing a communications protocol stack, according to aspects of the present disclosure. The illustrated communications protocol stacks may be implemented by devices operating in a wireless communication system, such as a 5G system (e.g., a system that supports uplink-based mobility). Diagram 500 illustrates a communications protocol stack including a RRC layer 510, a PDCP layer 515, a RLC layer 520, a MAC layer 525, and a PHY layer 530. In various examples, the layers of a protocol stack may be implemented as separate modules of software, portions of a processor or ASIC, portions of non-collocated devices connected by a communications link, or various combinations thereof. Collocated and non-collocated implementations may be used, for example, in a protocol stack for a network access device (e.g., ANs, CUs, and/or DUs) or a UE.

A first option 505-a shows a split implementation of a protocol stack, in which implementation of the protocol stack is split between a centralized network access device (e.g., an ANC 202 in FIG. 2) and distributed network access device (e.g., DU 306 in FIG. 3). In the first option 505-a, an RRC layer 510 and a PDCP layer 515 may be implemented by the central unit, and an RLC layer 520, a MAC layer 525, and a PHY layer 530 may be implemented by the DU. In various examples the CU and the DU may be collocated or non-collocated. The first option 505-a may be useful in a macro cell, micro cell, or pico cell deployment.

A second option 505-b shows a unified implementation of a protocol stack, in which the protocol stack is implemented in a single network access device. In the second option, RRC layer 510, PDCP layer 515, RLC layer 520, MAC layer 525, and PHY layer 530 may each be implemented by the AN. The second option 505-b may be useful in, for example, a femto cell deployment.

Regardless of whether a network access device implements part or all of a protocol stack, a UE may implement an entire protocol stack as shown in 505-c (e.g., the RRC layer 510, the PDCP layer 515, the RLC layer 520, the MAC layer 525, and the PHY layer 530).

In LTE, the basic transmission time interval (TTI) or packet duration is the 1 ms subframe. In NR, a subframe is still 1 ms, but the basic TTI is referred to as a slot. A subframe contains a variable number of slots (e.g., 1, 2, 4, 8, 16, . . . slots) depending on the subcarrier spacing. The NR RB is 12 consecutive frequency subcarriers. NR may support a base subcarrier spacing of 15 KHz and other subcarrier spacing may be defined with respect to the base subcarrier spacing, for example, 30 kHz, 60 kHz, 120 kHz, 240 kHz, etc. The symbol and slot lengths scale with the subcarrier spacing. The CP length also depends on the subcarrier spacing.

FIG. 6 is a diagram showing an example of a frame format 600 for NR. The transmission timeline for each of the downlink and uplink may be partitioned into units of radio frames. Each radio frame may have a predetermined duration (e.g., 10 ms) and may be partitioned into 10 subframes, each of 1 ms, with indices of 0 through 9. Each subframe may include a variable number of slots depending on the subcarrier spacing. Each slot may include a variable number of symbol periods (e.g., 14 symbols) depending on the subcarrier spacing. The symbol periods in each slot may be assigned indices. A mini-slot is a subslot structure (e.g., 2, 3, or 4 symbols).

Each symbol in a slot may indicate a link direction (e.g., DL, UL, or flexible) for data transmission and the link direction for each subframe may be dynamically switched. The link directions may be based on the slot format. Each slot may include DL/UL data as well as DL/UL control information.

In NR, a synchronization signal (SS) block is transmitted. The SS block includes a PSS, a SSS, and a two symbol PBCH. The SS block can be transmitted in a fixed slot location, such as the symbols 0-3 as shown in FIG. 6. The PSS and SSS may be used by UEs for cell search and acquisition. The PSS may provide half-frame timing, the SS may provide the CP length and frame timing. The PSS and SSS may provide the cell identity. The PBCH carries some basic system information (SI), such as downlink system bandwidth, timing information within radio frame, SS burst set periodicity, system frame number, etc. The SS blocks may be organized into SS bursts to support beam sweeping. Further system information such as, remaining minimum system information (RMSI), system information blocks (SIBs), other system information (OSI) can be transmitted on a PDSCH in certain subframes.

In some circumstances, two or more subordinate entities (e.g., UEs) may communicate with each other using sidelink signals. Real-world applications of such sidelink communications may include public safety, proximity services, UE-to-network relaying, vehicle-to-vehicle (V2V) communications, Internet of Everything (IoE) communications, IoT communications, mission-critical mesh, and/or various other suitable applications. Generally, a sidelink signal may refer to a signal communicated from one subordinate entity (e.g., UE1) to another subordinate entity (e.g., UE2) without relaying that communication through the scheduling entity (e.g., UE or BS), even though the scheduling entity may be utilized for scheduling and/or control purposes. In some examples, the sidelink signals may be communicated using a licensed spectrum (unlike wireless local area networks, which typically use an unlicensed spectrum).

A UE may operate in various radio resource configurations, including a configuration associated with transmitting pilots using a dedicated set of resources (e.g., a radio resource control (RRC) dedicated state, etc.) or a configuration associated with transmitting pilots using a common set of resources (e.g., an RRC common state, etc.). When operating in the RRC dedicated state, the UE may select a dedicated set of resources for transmitting a pilot signal to a network. When operating in the RRC common state, the UE may select a common set of resources for transmitting a pilot signal to the network. In either case, a pilot signal transmitted by the UE may be received by one or more network access devices, such as an, or a DU, or portions thereof. Each receiving network access device may be configured to receive and measure pilot signals transmitted on the common set of resources, and also receive and measure pilot signals transmitted on dedicated sets of resources allocated to the UEs for which the network access device is a member of a monitoring set of network access devices for the UE. One or more of the receiving network access devices, or a CU to which receiving network access device(s) transmit the measurements of the pilot signals, may use the measurements to identify serving cells for the UEs, or to initiate a change of serving cell for one or more of the UEs.

Example ULCI Application Based on Spatial Parameters

Certain aspects of the present disclosure provide techniques for utilizing uplink cancelation indication (ULCI) that takes into account uplink transmission dependencies on uplink beams. For example, the techniques may utilize a ULCI with an indication of one or more of multiple uplink transmission groups characterized by different spatial parameters. The ULCI is to be applied to the one or more uplink transmission groups that interfere with another uplink transmission (such as one of a higher priority or urgency from another UE).

In certain systems, such as NR (new radio or 5G) systems, a scheduled PUSCH may be preempted by another PUSCH transmission. For example, as noted above, NR supports a variety of services including enhanced mobile broadband (eMBB) and ultra-reliable low-latency communications (URLLC). An eMBB PUSCH may be preempted by a URLLC PUSCH, in a manner prioritizing URLLC traffic over eMBB traffic. Preemption, in this context, means that the entity transmitting eMBB data in PUSCH would stop (or at least cancel/puncture portions of) its eMBB transmission on the symbols preempted by URLLC- and a BS receiving the PUSCH interprets the preemption indication it sends in the same manner, allowing it to consider this when decoding.

Aspects of the present disclosure provide techniques that may help dynamically multiplex users with different services in the same time-frequency resources to have better spectrum utilization. As noted above, NR Rel-16 may support ULCI. ULCI is sent by the BS to the eMBB UE before the eMBB transmission occurs/ends (so the UE may cancel/puncture at least the portion of the eMBB transmission (e.g., preempted by URLLC).

The ULCI may indicated preemption of a set of resources using a number of bits in the DCI. Aspects of the present disclosure provide various techniques that may be considered mapping rules for mapping ULCI bits to corresponding groups of time and frequency resources subject to preemption.

FIG. 7 illustrates an example configuration of ULCI supported in NR Rel-16. An example code of radio resource control (RRC) configuration for the ULCI monitoring and its corresponding cancellation indication (CI) fields are shown. DCI format 2_4 is used to indicate the ULCI and has an overall payload size represented by the length of the DCI 2_4 representation. The starting positions for each CI corresponding to different serving cell IDs are defined in the DCI 2_4. The payload size of each CI is also configured. Details of each CI are shown in FIG. 8.

FIG. 8 illustrates an example CI field corresponding to a component carrier. As shown, the UE is provided with a CI payload size defined by a number of bits for the CI field in the DCI, and represented by N_CI. In this example, N_CI=14 bits. The CI field includes a number of resource blocks (RBs) defining the frequency span of ULCI, which is represented by B_CI. Here, B_CI=28 RBs. The time span of ULCI is defined using a number of symbols excluding the DL symbols. The time span is represented by T_CI, which equals to 28 symbols here and is split into 7 partitions or groups, represented by G_CI. Base on the CI field, the DCI can be interpreted to include a G_CIsets of bits from N_CIbits, which have a one-to-one mapping to the symbol groups. For each symbol group, N_BIequals to N_CI/G_CIbits from each set of bits and has a one-to-one mapping with N_BIgroups of physical resource blocks (PRBs). Here, N_CI/G_CI=2, thus there are two groups of RBs in frequency.

FIG. 9 illustrates an example arrangement of DCI and processing time. As shown, the first symbol of the TCI symbols starts after T_proc.2+d symbols from the end of PDCCH reception that carries DCI format 2_4, wherein d is reported as a UE capability and is selected from 0, 1, and 2 (i.e.,d∈{0, 1, 2}). T_proc.2is UE processing time for the corresponding PUSCH transmission. For example, d_2,1=0, when N₂of minimum processing capability 2 is assumed.

FIG. 10 illustrates an example application of the indicated CI to cancel overlapping resources. Indicated CI is applicable only to PUSCH or SRS that have resources overlapping with the indicated canceled resources in the CI in time and frequency. When the indicated CI is applied to PUSCH, cancellation without resume may be supported, such as from the earliest indicated symbol to the end of the PUSCH. When the indicated CI is applied to SRS, the cancellation of the transmissions is on a symbol basis. As shown, in the upper PUSCH, the transmissions are cancelled because the resources of the PUSCH transmission are indicated in the CI.

If the PUSCH or SRS is scheduled by a DCI, the ULCI may only be applicable if the last symbol of the DCI is earlier than the first symbol of the DCI that carries the ULCI. For example, as shown in the lower PUSCH, the ULCI is not applicable to the PUSCH because it is scheduled later. In some aspects, the impact of priority of PUSCH may depend on RRC configuration applicabilityforCI. For example, if configured, cancelation may be applicable only to PUSCH with low priority (with priority 0). Otherwise, cancelation is applicable regardless of priority

While conventional ULCI may have no dependency on UL transmission beams, aspects of the present disclosure propose ULCI that takes into account uplink transmission dependencies on uplink beams. In other words, the ULCI may not be applied in cases where spatial characteristics of an uplink transmission by one UE are such that it would not interfere with an uplink transmission of another UE, even if the uplink transmissions use overlapping resources.

FIG. 11 illustrates an example application of spatial ULCI, in accordance with aspects of the present disclosure. In the example configuration shown, UL beam 1 of UE1 transmitted to TRP1 may interfere with URLLC PUSCH transmitted by UE2 to TRP1 Because the URLLC PUSCH transmissions from UE2 has higher priority, the PUSCH from UE1 needs be canceled. On the other hand, UL beam 2 of UE1 transmitted to TRP2 is not interfered with URLLC PUSCH transmitted by UE2 and thus, UL beam 2 of UE 1 needs not be canceled.

In one example, one PUSCH with both UL beam 1 and UL beam 2 in a spatial division multiplexed (SDM) manner may be scheduled for UE1. In this case, one repetition of the PUSCH is transmitted with beam 1 and another repetition of the PUSCH is transmitted with beam 2. In case of TDM/FDM, determining the group of PUSCH transmissions not subject to ULCI may also be beneficial.

In another example, one PUSCH with beam 1 and another PUSCH with beam 2 may be scheduled for UE1. Simultaneous PUSCH transmissions of the two beams may also benefit from using spatial parameters to subject one of the two beams to ULCI.

In the examples shown in FIG. 11 (with variations described above), UL beam 1 and UL beam 2 are shown to be transmitted to the TRP1 and TRP2, respectively. However, single-TRP transmissions (especially in FR2) would also benefit from the techniques disclosed herein as two beams received at the same TRP (i.e., one beam from a URLLC UE, and another beam (beam 2) from eMBB UE) may not interfere with each other while another two beams received at the same TRP (i.e. one beam from URLLC UE, and another beam (beam 1) from eMBB UE) may interfere with each other.

FIG. 12 illustrates example operations 1200 for wireless communications by a user equipment (UE), in accordance with certain aspects of the present disclosure. Operations 1200 may be performed, for example, by a UE such as a UE 120 of FIG. 1 to process ULCI sent by a base station and apply the ULCI to PUSCH transmissions.

Operations 1200 begin, at 1202, by receiving an uplink cancelation indication (ULCI) with a number of bits that indicate resources on which one or more uplink channels are to be modified. At 1204, the UE determines, from at least two uplink transmissions groups characterized by different spatial parameters, at least one uplink transmission group to which the ULCI applies in a component carrier. At 1206, the UE modifies the one or more uplink channels that belong to the determined uplink transmission group in accordance with the ULCI.

FIG. 13 is a flow diagram showing example operations 1300 for wireless communications by a network entity that may be considered complementary to operations 1200 of FIG. 12. For example, operations 1300 may be performed by a BS 110 of FIG. 1 to generate and send ULCI to a UE performing operations 1200 of FIG. 12.

Operations 1300 begin, at 1302, by sending, to a first UE an ULCI with a number of bits that indicate resources on which one or more uplink channels are to be modified and an indication, from at least two uplink transmissions groups characterized by different spatial parameters, at least one uplink transmission group to which the ULCI applies in a component carrier. At 1304, the network entity communicates with the first UE taking into account modification, by the first UE, of the one or more uplink channels that belong to the determined uplink transmission group in accordance with the ULCI.

For example, modifying the one or more uplink channels includes at least partially cancelling the one or more uplink channels if the resources indicated in the ULCI overlap with the resources of the one or more uplink channels. The one or more uplink channels may include at least one of one or more PUSCHs or one or more PUSCH repetitions.

In some aspects, for both operations 1200 and 1300, the determination of at least one uplink transmission group to which ULCI applies is based on at least one CI field of a DCI that carries the ULCI.

FIG. 14 illustrates multiple examples of applications of ULCI to two or more groups of physical uplink shared channel transmissions having different spatial parameters, according to operations 1200 and 1300. As shown in the examples of FIG. 14, the ULCI is applied to a first group of PUSCH transmissions (or PUSCH repetitions) characterized by a first set of spatial parameters while is not applied to a second group of PUSCH transmissions (or PUSCH repetitions) characterized by a second set of spatial parameters in the same CC.

The examples 1-5 are illustrated using resources indicated by three levels of shadings. A first level of shadings indicates cancelled resources that belong to first group/associated with first set of spatial parameters. A second level of shadings indicates resources not canceled and belong to second group. The resources are associated with second set of spatial parameters. Finally, a third level of shadings indicates resources indicated by a CI field of DCI format 2_4 to be canceled (applied only to first group).

In the first example, there are two PUSCHs (or PUSCH repetitions) that are scheduled to be transmitted using the same time and frequency resources. The first group of transmissions associated with the first set of spatial parameters is cancelled.

In the second example, the two PUSCHs (or PUSCH repetitions) are scheduled to be transmitted in the partially overlapping resources as shown.

In the third example, two PUSCH repetitions (or PUSCHs) are scheduled to be transmitted in TDM manner. As shown, the second repetition of the PUSCH is canceled in view of the resources indicated by the CI field of DCI, which is applied to the first group.

In the fourth example, the two PUSCHs (or PUSCH repetitions) are scheduled to be transmitted in FDM manner. One group of PUSCH transmissions is cancelled.

In the last example, because there is only one group of uplink transmissions, the uplink transmissions are not subject to the ULCI.

FIG. 15A illustrates example CI fields in a DCI (e.g., DCI format 2_4), in accordance with certain aspects of the present disclosure. In one aspect, the DCI has multiple CI fields for the component carrier. Each of the CI fields is associated with one or more uplink transmission groups. For example, a CI field in DCI format 2_4 configured for a CC index can be associated with the first group only, the second group only or both groups. In some cases, the UE receives RRC signaling that indicates the association between CI fields and uplink transmission groups.

As shown in the example, for each CI field (corresponding to a CC index and one or more groups), UE is configured with a starting position in the DCI. For one CC (e.g., CC2/servingCellId=2), one CI field is associated with the first group only and another CI field is associated with the second group only. For another CC (e.g., CC5/servingCellId=5), one CI field is associated with both groups.

As illustrated in FIG. 15B, in some cases, one or more bits in the CI field may indicate one or more uplink transmissions groups. In other words, the one or more groups that are associated with a CI field are indicated as part of the CI field. The first one or more bits of the CI field indicate whether the remaining bits (corresponding to the RB-symbol group bitmap) should be applied to the first group/second group (or both). When the UL transmission does not belong to any group, each CI field may be applied to the uplink transmission; or alternatively, none of the CI field is applied to the uplink transmission.

In some aspects, different PDCCH monitoring occasions are associated with different uplink transmission groups. The determination is based on association of the PDCCH monitoring occasion in which the ULCI is received with at least the determined uplink transmission group. For example, the PDCCH monitoring occasions can be associated with the first group only, second group only or both groups. If DCI format 2_4 is monitored in a first/second PDCCH occasion, the indicated CI field(s) is associated with first/second group, respectively. In some aspects, different PDCCH monitoring occasions associated with different uplink transmission groups belongs to different search space (SS) sets. When belonging to different SS sets, the associated group(s) can be configured as part of SS set configurations). The UE may receive SS set configuration indicating the associated uplink transmission groups.

In some aspects, the determination is based on an association between a control resource set (CORESET) pool index of the CORESET in which the ULCI is received and one or more uplink transmission groups. For example, if DCI format 2_4 is received in a first or second CORESET that is associated with CORESETPoolIndex valued 0 or 1, the indicated CI field(s) can be applied to the first group or second group, respectively. In particular, CORESETPoolIndex supports multi-DCI based multi-TRP. Each CORESET may be associated with one of the values 0 or 1 that groups the CORESETs in to two groups.

In some aspects, more than one CI field can exist in DCI format 2_4 for a UE and a given CC index. The indicated resources in a CI field are applied only to UL transmissions (specifically PUSCH, PUSCH repetition, or SRS) that belong to the group(s) that are configured for or indicated in that CI field, or are associated with the DCI that includes the CI field. The indication does not impact UL transmissions that belong to other group(s).

The uplink transmission groups to which ULCI may be selectively applied (e.g., for a PUSCH or a PUSCH repetition) may be defined in various manners. In some implementations, the uplink transmission groups may be defined based on a CORESET Pool Index of a CORESET in which a DCI that schedules the uplink transmission is received.

In some implementations, the uplink transmission groups are defined based on an uplink beam group. For example, the uplink transmission groups are defined based on at least one or a UE panel ID that determines the UL beam group; an uplink transmission configuration indicator (TCI) field; or at least one of a sounding reference signal (SRS) resource set ID, SRS resource ID, or SRS resource indicator (SRI) codepoint. For example, the DCI that schedules PUSCH may indicate one or more SRS resources by the SRI field of the DCI.

In some implementations, the uplink transmission groups are defined based on an uplink power control closed loop index associated with the uplink transmission. For example, there are two closed loop indices (0 and 1) for two closed loop power control for different PUSCH transmissions in the same CC.

In some implementations, the uplink transmission groups are defined based on at least one or antenna ports (e.g., PUSCH, SRS, or DMRS) or one or more code division multiplexed (CDM) groups that the antenna ports belong to. For example, an SRI field in UL DCI may indicate whether PUSCH. PUSCH/SRS ports are applicable, while DMRS ports are determined from a “antenna port(s) field” of UL DCI.

In some implementations, the uplink transmission groups are defined based on one or more timing advance group (TAG) IDs, for example, when the two uplink transmission groups have different time advance for UL transmission.

In some implementations, the uplink transmission groups are defined based on a physical cell identifier (PCI) or synchronization signal block (SSB) set associated with the uplink transmission, for example, in inter-cell multi-TRP situations where there are serving cell(s) and non-serving cell(s).

FIG. 16 illustrates a communications device 1600 (e.g., a UE) that may include various components (e.g., corresponding to means-plus-function components) configured to perform operations for the techniques disclosed herein, such as the operations 1200 illustrated in FIG. 12. The communications device 1600 includes a processing system 1602 coupled to a transceiver 1608 (e.g., a transmitter and/or a receiver). The transceiver 1608 is configured to transmit and receive signals for the communications device 1600 via an antenna 1610, such as the various signals as described herein. The processing system 1602 may be configured to perform processing functions for the communications device 1600, including processing signals received and/or to be transmitted by the communications device 1600.

The processing system 1602 includes a processor 1604 coupled to a computer-readable medium/memory 1612 via a bus 1606. In certain aspects, the computer-readable medium/memory 1612 is configured to store instructions (e.g., computer-executable code) that when executed by the processor 1604, cause the processor 1604 to perform the operations 1200 illustrated in FIG. 12, or other operations for performing the various techniques discussed herein. In certain aspects, computer-readable medium/memory 1612 stores code 1614 for receiving an uplink cancelation indication (ULCI) with a number of bits that indicate resources for a first scheduled data transmission of a first type that overlap with resources for a second scheduled data transmission of a second type are preempted by the scheduled data transmission of the second type, code 1616 for determining, from at least two physical uplink shared channel (PUSCH) groups characterized by different spatial parameters, at least one PUSCH group to which the ULCI applies, and code 1618 for modifying the first scheduled data transmission on the determined PUSCH group in accordance with the ULCI. In certain aspects, the processor 1604 has circuitry configured to implement the code stored in the computer-readable medium/memory 1612. The processor 1604 includes circuitry 1619 for transmitting, to a network entity, capability signaling indicating a capability of the UE in switching among multiple component carriers (CCs), circuitry 1620 for receiving an uplink cancelation indication (ULCI) with a number of bits that indicate resources for a first scheduled data transmission of a first type that overlap with resources for a second scheduled data transmission of a second type are preempted by the scheduled data transmission of the second type, circuitry