Techniques for Multi-Component Carrier Scheduling

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may receive a downlink control information (DCI) message for scheduling downlink data transmissions at the UE, where at least one DCI message schedules two or more downlink data transmissions. The UE may determine a first set of downlink resources associated with a first control resource set (CORESET) group and a second set of downlink resources associated with a second CORESET group based on the DCI message. The UE may receive one or more first downlink data transmissions on the first set of downlink resources and receive one or more second downlink data transmissions in the second set of downlink resources. The UE may communicate using a first set of parameters associated with the first CORESET group and a second set of parameters associated with the second CORESET group.

Description

[0001] Cross-reference

[0002] This patent application claims the benefit of U.S. Provisional Patent Application No. 63 / 052,748, filed Jul. 16, 2020, by Khoshnevisan et al. and entitled "TECHNIQUES FOR MULTIPLE COMPONENT CARRIER SCHEDULING", and U.S. Patent Application No. 17 / 328,257, filed May 24, 2021, by Khoshnevisan et al. and entitled "TECHNIQUES FOR MULTIPLE COMPONENT CARRIER SCHEDULING"; each of the above applications is assigned to the assignee of the present application. Field of the Invention

[0003] The following relates to wireless communications, including techniques for multi-component carrier scheduling. Background Art

[0004] 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). Examples of such multi-access systems include fourth-generation (4G) systems (e.g., Long Term Evolution (LTE) systems, enhanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multi-access communication system may include one or more base stations or one or more network access nodes, each of which simultaneously supports communication for multiple communication devices (which may also be referred to as user equipment (UE)).

[0005] In some wireless communication systems, downlink data transmissions from a base station to a UE may be scheduled via a downlink control information (DCI) message from the base station. A UE may be able to distinguish between transmissions from different transmission / reception points (TRPs) of the base station based on some downlink resources being associated with one TRP and other downlink resources being associated with another TRP. Transmissions from a TRP may be via resources associated with different control resource set (CORESET) groups. Summary of the Invention

[0006] The described techniques relate to improved methods, systems, devices, and apparatuses for supporting techniques for multi-component carrier scheduling. Generally speaking, the described techniques provide multi-component carrier downlink scheduling for a user equipment (UE). In some aspects, a downlink control information (DCI) message can be associated with a single transmit / receive point (TRP), a single control resource set (CORESET) group, or both. Thus, in order to schedule multi-TRP-based downlink data transmission on multiple component carriers, a first DCI message associated with a first TRP (e.g., a first CORESET group) can schedule downlink data transmission in two or more component carriers, and a second DCI message associated with a second TRP (e.g., a second CORESET group) can schedule downlink data transmission in two or more component carriers. In additional aspects, a single DCI message can schedule two downlink data transmissions in a single component carrier, where each downlink data transmission is associated with a different TRP (e.g., a different CORESET group). The two downlink data transmissions can be scheduled on the same or different component carriers on which the DCI message is received. In additional or alternative aspects, a single DCI message can schedule two downlink data transmissions on separate component carriers, where each downlink data transmission is associated with a different TRP (e.g., a different CORESET group). In some aspects, a DCI message for scheduling downlink data transmission can indicate an association between a component carrier and a TRP (e.g., a CORESET group) via a carrier indicator field (CIF) value that indicates a mapping pair including the corresponding component carrier and the CORESET group, where the UE is configured to interpret the CIF value via radio resource control (RRC) signaling.

[0007] A method of wireless communication at a UE is described. The method can include: receiving, on a first component carrier in a set of component carriers and from a base station, one or more DCI messages for scheduling downlink data transmission at the UE, where at least one DCI message schedules two or more downlink data transmissions; determining a first set of downlink resources and a second set of downlink resources based on the one or more DCI messages, the first set of downlink resources being associated with a first CORESET group and the second set of downlink resources being associated with a second CORESET group; receiving one or more first downlink data transmissions on the first set of downlink resources and receiving one or more second downlink data transmissions on the second set of downlink resources; and communicating using a first set of parameters associated with the first CORESET group and a second set of parameters associated with the second CORESET group based on receiving the one or more first downlink data transmissions and the one or more second downlink data transmissions.

[0008] Describes an apparatus for wireless communication at a UE. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to perform the following operations: receive, on a first component carrier in a set of component carriers and from a base station, one or more DCI messages for scheduling downlink data transmission at the UE, wherein at least one DCI message schedules two or more downlink data transmissions; determine a first downlink resource set and a second downlink resource set based on the one or more DCI messages, the first downlink resource set being associated with a first CORESET group and the second downlink resource set being associated with a second CORESET group; receive one or more first downlink data transmissions on the first downlink resource set and receive one or more second downlink data transmissions on the second downlink resource set; and communicate, based on receiving the one or more first downlink data transmissions and the one or more second downlink data transmissions, using a first set of parameters associated with the first CORESET group and a second set of parameters associated with the second CORESET group.

[0009] Describes another apparatus for wireless communication at a UE. The apparatus may include units for performing the following operations: receive, on a first component carrier in a set of component carriers and from a base station, one or more DCI messages for scheduling downlink data transmission at the UE, wherein at least one DCI message schedules two or more downlink data transmissions; determine a first downlink resource set and a second downlink resource set based on the one or more DCI messages, the first downlink resource set being associated with a first CORESET group and the second downlink resource set being associated with a second CORESET group; receive one or more first downlink data transmissions on the first downlink resource set and receive one or more second downlink data transmissions on the second downlink resource set; and communicate, based on receiving the one or more first downlink data transmissions and the one or more second downlink data transmissions, using a first set of parameters associated with the first CORESET group and a second set of parameters associated with the second CORESET group.

[0010] Describes a non - transitory computer - readable medium storing code for wireless communication at a UE. The code may include instructions executable by a processor to perform the following operations: receive, on a first component carrier in a set of component carriers and from a base station, one or more DCI messages for scheduling downlink data transmissions at the UE, where at least one DCI message schedules two or more downlink data transmissions; determine a first set of downlink resources and a second set of downlink resources based on the one or more DCI messages, the first set of downlink resources being associated with a first CORESET group and the second set of downlink resources being associated with a second CORESET group; receive one or more first downlink data transmissions on the first set of downlink resources and receive one or more second downlink data transmissions on the second set of downlink resources; and communicate using a first set of parameters associated with the first CORESET group and a second set of parameters associated with the second CORESET group based on receiving the one or more first downlink data transmissions and the one or more second downlink data transmissions.

[0011] In some examples of the methods, apparatuses, and non - transitory computer - readable media described herein, receiving the one or more DCI messages may include operations, features, units, or instructions for performing the following: receive a first DCI message in a first CORESET of the first CORESET group from the base station, the first DCI message including an indication of the first set of downlink resources; and receive a second DCI message in a second CORESET of the second CORESET group from the base station, the second DCI message including an indication of the second set of downlink resources.

[0012] In some examples of the methods, apparatuses, and non - transitory computer - readable media described herein, determining the first set of downlink resources and the second set of downlink resources may further include operations, features, units, or instructions for performing the following: determine that the first set of downlink resources associated with the first CORESET group includes a first subset and a second subset of the first set of downlink resources within different component carriers; and determine that the second set of downlink resources associated with the second CORESET group includes a first subset and a second subset of the second set of downlink resources within different component carriers.

[0013] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, receiving the one or more DCI messages may include operations, features, units, or instructions for: receiving a single DCI message from the base station via the first component carrier, the single DCI message including an indication of the first CORESET group and the second CORESET group.

[0014] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for: receiving an RRC message from the base station for indicating a set of CIF values, where each CIF value is associated with a mapping pair, the mapping pair including a component carrier in the set of component carriers and at least one of the first CORESET group or the second CORESET group, wherein receiving the one or more first downlink data transmissions and the one or more second downlink data transmissions may be based on the value of the CIF in the single DCI message and the set of CIF values in the RRC message.

[0015] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the value of the CIF in the single DCI message may be associated with both the first CORESET group and the second CORESET group.

[0016] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, receiving the one or more first downlink data transmissions and the one or more second downlink data transmissions may include operations, features, units, or instructions for: receiving the one or more first downlink data transmissions and the one or more second downlink data transmissions on the first component carrier according to the value of the CIF in the single DCI message.

[0017] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, receiving the one or more first downlink data transmissions and the one or more second downlink data transmissions may include operations, features, units, or instructions for: receiving the one or more first downlink data transmissions on a first downlink resource set associated with the first CORESET group on a second component carrier different from the first component carrier according to a first mapping pair of values of the CIF in the single DCI message, wherein the first mapping pair includes the second component carrier and the first CORESET group; and receiving the one or more second downlink data transmissions on a second downlink resource set associated with the second CORESET group on the second component carrier according to a second mapping pair of values of the CIF in the single DCI message, wherein the second mapping pair includes the second component carrier and the second CORESET group.

[0018] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for: receiving, from the base station, an RRC message for indicating a set of CIF values, wherein each CIF value is associated with two mapping pairs of a component carrier and a CORESET group value, each mapping pair includes a CORESET group different from the first CORESET group or the second CORESET group, and each mapping pair includes a component carrier different from the set of component carriers, wherein receiving the one or more first downlink data transmissions and the one or more second downlink data transmissions may be based on the value of the CIF in the single DCI message and the set of CIF values in the RRC message.

[0019] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, receiving the one or more first downlink data transmissions and the one or more second downlink data transmissions may include operations, features, units, or instructions for: receiving the one or more first downlink data transmissions on the first downlink resource set associated with the first CORESET group on the first component carrier according to a first mapping pair of values of the CIF in the single DCI message, wherein the first mapping pair includes the first component carrier and the first CORESET group; and receiving the one or more second downlink data transmissions on the second downlink resource set associated with the second CORESET group on a second component carrier different from the first component carrier according to a second mapping pair of values of the CIF in the single DCI message, wherein the second mapping pair includes the second component carrier and the second CORESET group.

[0020] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, hybrid automatic repeat request (HARQ) configuration, physical downlink shared channel (PDSCH) scrambling sequence, cell-specific reference signal (CRS) rate matching configuration, transmission configuration indicator (TCI) state, or any combination thereof.

[0021] A method of wireless communication at a base station is described. The method may include: determining a first downlink resource set and a second downlink resource set, the first downlink resource set being associated with a first CORESET group and the second downlink resource set being associated with a second CORESET group, both the first downlink resource set and the second downlink resource set being associated with one or more component carriers in a set of component carriers used in communication with a UE; transmitting, on a first component carrier in the set of component carriers and to the UE, one or more DCI messages for scheduling downlink data transmissions at the UE, wherein at least one DCI schedules two or more downlink data transmissions; based on the one or more DCI messages, transmitting one or more first downlink data transmissions to the UE on the first downlink resource set and one or more second downlink data transmissions to the UE on the second downlink resource set; and communicating with the UE using a first set of parameters associated with the first CORESET group and a second set of parameters associated with the second CORESET group.

[0022] Describes an apparatus for wireless communication at a base station. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to perform the following operations: determine a first downlink resource set and a second downlink resource set, the first downlink resource set being associated with a first CORESET group and the second downlink resource set being associated with a second CORESET group, both the first downlink resource set and the second downlink resource set being associated with one or more component carriers in a set of component carriers used in communication with a UE; transmit, on a first component carrier in the set of component carriers and to the UE, one or more DCI messages for scheduling downlink data transmissions at the UE, wherein at least one DCI schedules two or more downlink data transmissions; based on the one or more DCI messages, transmit one or more first downlink data transmissions to the UE on the first downlink resource set and transmit one or more second downlink data transmissions to the UE on the second downlink resource set; and communicate with the UE using a first set of parameters associated with the first CORESET group and a second set of parameters associated with the second CORESET group.

[0023] Describes another apparatus for wireless communication at a base station. The apparatus may include units for performing the following operations: determine a first downlink resource set and a second downlink resource set, the first downlink resource set being associated with a first CORESET group and the second downlink resource set being associated with a second CORESET group, both the first downlink resource set and the second downlink resource set being associated with one or more component carriers in a set of component carriers used in communication with a UE; transmit, on a first component carrier in the set of component carriers and to the UE, one or more DCI messages for scheduling downlink data transmissions at the UE, wherein at least one DCI schedules two or more downlink data transmissions; based on the one or more DCI messages, transmit one or more first downlink data transmissions to the UE on the first downlink resource set and transmit one or more second downlink data transmissions to the UE on the second downlink resource set; and communicate with the UE using a first set of parameters associated with the first CORESET group and a second set of parameters associated with the second CORESET group.

[0024] Describes a non-transitory computer-readable medium storing code for wireless communication at a base station. The code may include instructions executable by a processor to perform the following operations: determining a first downlink resource set and a second downlink resource set, the first downlink resource set being associated with a first CORESET group and the second downlink resource set being associated with a second CORESET group, both the first downlink resource set and the second downlink resource set being associated with one or more component carriers in a set of component carriers used in communication with a UE; transmitting, on a first component carrier in the set of component carriers and to the UE, one or more DCI messages for scheduling downlink data transmission at the UE, wherein at least one DCI schedules two or more downlink data transmissions; based on the one or more DCI messages, transmitting one or more first downlink data transmissions to the UE on the first downlink resource set and transmitting one or more second downlink data transmissions to the UE on the second downlink resource set; and communicating with the UE using a first parameter set associated with the first CORESET group and a second parameter set associated with the second CORESET group.

[0025] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, transmitting the one or more DCI messages may include operations, features, units, or instructions for performing the following: transmitting a first DCI message to the UE in a first CORESET of the first CORESET group, the first DCI message including an indication of the first downlink resource set; and transmitting a second DCI message to the UE in a second CORESET of the second CORESET group, the second DCI message including an indication of the second downlink resource set.

[0026] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, determining the first downlink resource set and the second downlink resource set may further include operations, features, units, or instructions for performing the following: determining that the first downlink resource set associated with the first CORESET group includes a first subset and a second subset of the first downlink resource set within different component carriers; and determining that the second downlink resource set associated with the second CORESET group includes a first subset and a second subset of the second downlink resource set within different component carriers.

[0027] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, sending the one or more DCI messages may include operations, features, units, or instructions for: sending a single DCI message to the UE via the first component carrier, the single DCI message including an indication of the first CORESET group and the second CORESET group.

[0028] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for: sending an RRC message to the UE for indicating a set of CIF values, where each CIF value is associated with a mapping pair, the mapping pair including a component carrier in the set of component carriers and at least one of the first CORESET group or the second CORESET group, wherein sending the one or more first downlink data transmissions and the one or more second downlink data transmissions may be based on the value of the CIF in the single DCI message and the set of CIF values in the RRC message.

[0029] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the value of the CIF in the single DCI message may be associated with both the first CORESET group and the second CORESET group.

[0030] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, sending the one or more first downlink data transmissions and the one or more second downlink data transmissions may include operations, features, units, or instructions for: sending the one or more first downlink data transmissions and the one or more second downlink data transmissions on the first component carrier according to the value of the CIF in the single DCI message.

[0031] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, transmitting the one or more first downlink data transmissions and the one or more second downlink data transmissions may include operations, features, units, or instructions for: transmitting the one or more first downlink data transmissions on a first downlink resource set associated with the first CORESET group on a second component carrier different from the first component carrier according to a first mapping pair of the value of the CIF in the single DCI message, wherein the first mapping pair includes the second component carrier and the first CORESET group; and transmitting the one or more second downlink data transmissions on a second downlink resource set associated with the second CORESET group on the second component carrier according to a second mapping pair of the value of the CIF in the single DCI message, wherein the second mapping pair includes the second component carrier and the second CORESET group.

[0032] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for: sending an RRC message to the UE for indicating a set of CIF values, wherein each CIF value is associated with two mapping pairs of a component carrier and a CORESET group value, each mapping pair includes a CORESET group different from the first CORESET group or the second CORESET group, and each mapping pair includes a component carrier different from the set of component carriers, wherein transmitting the one or more first downlink data transmissions and the one or more second downlink data transmissions may be based on the value of the CIF in the single DCI message and the set of CIF values in the RRC message.

[0033] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, transmitting the one or more first downlink data transmissions and the one or more second downlink data transmissions may include operations, features, units, or instructions for: transmitting the one or more first downlink data transmissions on the first downlink resource set associated with the first CORESET group on the first component carrier according to a first mapping pair of values of the CIF in the single DCI message, where the first mapping pair includes the first component carrier and the first CORESET group; and transmitting the one or more second downlink data transmissions on the second downlink resource set associated with the second CORESET group on a second component carrier different from the first component carrier according to a second mapping pair of values of the CIF in the single DCI message, where the second mapping pair includes the second component carrier and the second CORESET group.

[0034] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, HARQ configuration, PDSCH scrambling sequence, CRS rate matching configuration, TCI state, or any combination thereof. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] Figure 1 FIG. shows an example of a wireless communication system supporting techniques for multi-component carrier scheduling in accordance with aspects of the present disclosure.

[0036] Figure 2 FIG. shows an example of a wireless communication system supporting techniques for multi-component carrier scheduling in accordance with aspects of the present disclosure.

[0037] Figure 3 FIG. shows an example of a resource allocation scheme supporting techniques for multi-component carrier scheduling in accordance with aspects of the present disclosure.

[0038] Figure 4 FIG. shows an example of a resource allocation scheme supporting techniques for multi-component carrier scheduling in accordance with aspects of the present disclosure.

[0039] Figure 5 FIG. shows an example of a resource allocation scheme supporting techniques for multi-component carrier scheduling in accordance with aspects of the present disclosure.

[0040] Figure 6 FIG. shows an example of a process flow supporting techniques for multi-component carrier scheduling in accordance with aspects of the present disclosure.

[0041] Figure 7 and 8A block diagram of a device supporting techniques for multi-component carrier scheduling in accordance with aspects of the present disclosure is shown.

[0042] Figure 9 A block diagram of a communication manager supporting techniques for multi-component carrier scheduling in accordance with aspects of the present disclosure is shown.

[0043] Figure 10 A diagram of a system including a device supporting techniques for multi-component carrier scheduling in accordance with aspects of the present disclosure is shown.

[0044] Figure 11 and 12 A block diagram of a device supporting techniques for multi-component carrier scheduling in accordance with aspects of the present disclosure is shown.

[0045] Figure 13 A block diagram of a communication manager supporting techniques for multi-component carrier scheduling in accordance with aspects of the present disclosure is shown.

[0046] Figure 14 A diagram of a system including a device supporting techniques for multi-component carrier scheduling in accordance with aspects of the present disclosure is shown.

[0047] Figures 15 to 19 A flowchart illustrating a method supporting techniques for multi-component carrier scheduling in accordance with aspects of the present disclosure is shown. Detailed Description

[0048] In some wireless communication systems, downlink data transmission from a base station to a user equipment (UE) (e.g., physical downlink shared channel (PDSCH) transmission) can be scheduled via a downlink control information (DCI) message from the base station. The UE may be able to distinguish between transmissions from different transmit / receive points (TRPs) of the base station based on a set of downlink resources associated with different TRPs. Downlink data transmission from one TRP can be sent via a set of downlink resources associated with a first control resource set (CORESET) group (e.g., CORESETPoolIndex 0), while downlink data transmission from another TRP can be sent via a set of downlink resources associated with a second CORESET group (e.g., CORESETPoolIndex 1). The association between the downlink data transmission and the corresponding CORESET group (and thus the TRP) can be indicated via a scheduling DCI message. In some cases, a single DCI message can indicate PDSCH resources for multiple TRPs, and a single DCI message can indicate PDSCHs on different component carriers. However, some wireless communication systems are unable to schedule downlink data transmission for multiple TRPs across multiple component carriers (e.g., multiple downlink data transmissions associated with multiple CORESET groups).

[0049] To address the limitations associated with scheduling downlink data transmission associated with multiple CORESET groups (e.g., multiple TRPs) across multiple component carriers, techniques for multi-component carrier downlink scheduling are described. In some aspects, a DCI message can be associated with a single TRP, a single CORESET group, or both. Thus, to schedule downlink data transmission based on multiple TRPs on multiple component carriers, a first DCI message associated with a first TRP (e.g., a first CORESET group, CORESETPoolIndex 0) can schedule downlink data transmission in two or more component carriers, and a second DCI message associated with a second TRP (e.g., a second CORESET group, CORESETPoolIndex 1) can schedule downlink data transmission in two or more component carriers.

[0050] In additional aspects, a single DCI message may schedule two downlink data transmissions in a single component carrier, where each downlink data transmission is associated with a different TRP (e.g., a different CORESET set). The two downlink data transmissions may be scheduled on the same or different component carriers on which the DCI message is received. In additional or alternative aspects, a single DCI message may schedule two downlink data transmissions on separate component carriers, where each downlink data transmission is associated with a different TRP (e.g., a different CORESET set). In some aspects, a DCI message for scheduling a downlink data transmission may indicate an association between a component carrier and a TRP (e.g., a CORESET set) via a Carrier Indicator Field (CIF) value that indicates a mapping pair including the corresponding component carrier and CORESET set, where a UE may be configured to interpret the CIF value via Radio Resource Control (RRC) signaling.

[0051] Aspects of the present disclosure are first described in the context of a wireless communication system. Additionally, aspects of the present disclosure are described in the context of example resource configurations and example process flows. Aspects of the present disclosure are further illustrated by device diagrams, system diagrams, and flowcharts relating to techniques for multi-component carrier scheduling, and aspects of the present disclosure are described with reference to these diagrams.

[0052] Figure 1 An example of a wireless communication system 100 that supports techniques for multi-component carrier scheduling in accordance with aspects of the present disclosure is shown. The wireless communication system 100 may include one or more base stations 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an enhanced LTE (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network. In some examples, the wireless communication system 100 may support enhanced broadband communication, ultra-reliable (e.g., mission-critical) communication, low-latency communication, or communication with low-cost and low-complexity devices, or any combination thereof.

[0053] The base stations 105 may be spread throughout a geographic area to form the wireless communication system 100, and may be devices of different forms or having different capabilities. The base stations 105 and the UEs 115 may communicate wirelessly via one or more communication links 125. Each base station 105 may provide a coverage area 110, and the UEs 115 and the base stations 105 may establish one or more communication links 125 over the coverage area 110. The coverage area 110 may be an example of a geographic area over which the base stations 105 and the UEs 115 may support the transmission of signals in accordance with one or more radio access technologies.

[0054] UE 115 can be spread throughout the coverage area 110 of the wireless communication system 100, and each UE 115 can be stationary, or mobile, or both at different times. The UE 115 can be devices of different forms or with different capabilities. In Figure 1 some example UEs 115 are shown. The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, base stations 105, or network devices (e.g., core network nodes, relay devices, integrated access and backhaul (IAB) nodes, or other network devices), as Figure 1 shown.

[0055] The base station 105 can communicate with the core network 130, or communicate with each other, or perform both of the above operations. For example, the base station 105 can be interfaced with the core network 130 via one or more backhaul links 120 (e.g., via S1, N2, N3, or other interfaces). The base stations 105 can communicate with each other directly (e.g., directly between the base stations 105) or indirectly (e.g., via the core network 130) on the backhaul link 120 (e.g., via X2, Xn, or other interfaces), or perform both of the above operations. In some examples, the backhaul link 120 can be or include one or more wireless links.

[0056] One or more of the base stations 105 described herein may include or may be referred to by those skilled in the art as a base station transceiver, a radio base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next-generation Node B, or a Gigabit Node B (any of which may be referred to as a gNB), a home Node B, a home evolved Node B, or some other suitable term.

[0057] The UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where "device" may also be referred to as a unit, a station, a terminal, or a client, etc. The UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, the UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various articles such as appliances, or vehicles, meters, etc.

[0058] The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115 that can sometimes act as relays, as well as base stations 105 and network devices, including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc., as Figure 1 shown.

[0059] The UE 115 and the base station 105 may communicate wirelessly with each other via one or more communication links 125 over one or more carriers. The term "carrier" may refer to a set of radio frequency spectrum resources having a defined physical layer structure for supporting the communication link 125. For example, a carrier for the communication link 125 may include a portion of a radio frequency spectrum band (e.g., a bandwidth part (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating the operation of the carrier, user data, or other signaling. The wireless communication system 100 may support communication with the UE 115 using carrier aggregation or multi-carrier operation. According to a carrier aggregation configuration, the UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers.

[0060] In some examples (e.g., in a carrier aggregation configuration), a carrier may also have acquisition signaling or control signaling for coordinating the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an evolved universal mobile telecommunications system terrestrial radio access (E-UTRA) absolute radio frequency channel number (EARFCN)) and may be placed according to a channel raster for discovery by the UE 115. A carrier may operate in stand-alone mode, where the UE 115 performs initial acquisition and connection via the carrier, or the carrier may operate in non-stand-alone mode, where a different carrier (e.g., of the same or a different radio access technology) is used to anchor the connection.

[0061] The communication link 125 shown in the wireless communication system 100 may include an uplink transmission from the UE 115 to the base station 105, or a downlink data transmission from the base station 105 to the UE 115. A carrier may carry downlink or uplink communication (e.g., in FDD mode) or may be configured to carry both downlink and uplink communication (e.g., in TDD mode).

[0062] A carrier can be associated with a specific bandwidth of the radio frequency spectrum, and in some examples, the carrier bandwidth can be referred to as the "system bandwidth" of the carrier or the wireless communication system 100. For example, the carrier bandwidth can be one of a number of defined bandwidths for a carrier of a specific radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)). Devices of the wireless communication system 100 (e.g., the base station 105, the UE 115, or both) can have a hardware configuration that supports communication on a specific carrier bandwidth or can be configurable to support communication on one of a set of carrier bandwidths. In some examples, the wireless communication system 100 can include a base station 105 or a UE 115 that supports simultaneous communication via carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 can be configured to operate on a portion (e.g., a subband, a BWP) or all of the carrier bandwidth.

[0063] The signal waveform transmitted on a carrier can be composed of multiple subcarriers (e.g., using a multi-carrier modulation (MCM) technique such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing an MCM technique, a resource element can include a symbol period (e.g., the duration of a modulation symbol) and a subcarrier, where the symbol period and the subcarrier spacing are inversely related. The number of bits carried by each resource element can depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both). Thus, the more resource elements received by the UE 115 and the higher the order of the modulation scheme, the higher the data rate can be for the UE 115. Wireless communication resources can refer to a combination of radio frequency spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial layers can further increase the data rate or data integrity for communication with the UE 115.

[0064] The time interval for the base station 105 or the UE 115 can be represented as a multiple of a basic time unit, which can be, for example, a sampling period of T s =1 / (Δf max ·N f ) seconds, where Δf max can represent the maximum supported subcarrier spacing and N f can represent the maximum supported discrete Fourier transform (DFT) size). The time intervals of the communication resources can be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0065] Each frame may include a plurality of consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of symbol periods (e.g., depending on the length of a cyclic prefix added in front of each symbol period). In some wireless communication systems 100, a time slot may be further divided into a plurality of micro-time slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0066] A subframe, a time slot, a mini-time slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in the form of bursts of shortened TTIs (sTTIs)).

[0067] Physical channels may be multiplexed on a carrier according to various techniques. For example, one or more of a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique may be used to multiplex physical control channels and physical data channels on a downlink carrier. A control region (e.g., CORESET) for a physical control channel may be defined by the number of symbol periods and may extend across the system bandwidth of a carrier or a subset of the system bandwidth. One or more control regions (e.g., CORESET) may be configured for a group of UEs 115. For example, one or more of the UEs 115 may monitor or search the control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates at one or more aggregation levels arranged in a cascaded manner. The aggregation level for a control channel candidate may refer to the number of control channel resources (e.g., control channel elements (CCEs)) associated with the coded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to multiple UEs 115 and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0068] In some examples, the base station 105 may be movable, and thus, provide communication coverage for a mobile geographic coverage area 110. In some examples, different geographic coverage areas 110 associated with different technologies may overlap, but different geographic coverage areas 110 may be supported by the same base station 105. In other examples, overlapping geographic coverage areas 110 associated with different technologies may be supported by different base stations 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of base stations 105 use the same or different radio access technologies to provide coverage for respective geographic coverage areas 110.

[0069] The wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, the wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC) or mission-critical communication. The UE 115 may be designed to support ultra-reliability, low latency, or critical functions (e.g., mission-critical functions). Ultra-reliable communication may include private communication or group communication, and may be supported by one or more mission-critical services such as mission-critical push-to-talk (MCPTT), mission-critical video (MCVideo), or mission-critical data (MCData). Support for mission-critical functions may include prioritization of services, and mission-critical services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, mission-critical, and ultra-reliable low-latency may be used interchangeably herein.

[0070] In some examples, the UE 115 may be able to communicate directly with other UEs 115 over a device-to-device (D2D) communication link 135 (e.g., using a peer-to-peer (P2P) or D2D protocol). One or more UEs 115 utilizing D2D communication may be within the geographic coverage area 110 of the base station 105. Other UEs 115 in such a group may be outside the geographic coverage area 110 of the base station 105 or otherwise unable to receive transmissions from the base station 105. In some examples, groups of UEs 115 communicating via D2D communication may utilize a one-to-many (1:M) system, where each UE 115 transmits to each other UE 115 in the group. In some examples, the base station 105 facilitates scheduling of resources for D2D communication. In other cases, D2D communication is performed between UEs 115 without involving the base station 105.

[0071] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and at least one user plane entity that routes packets to or interconnects with an external network (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for a UE 115 served by a base station 105 associated with the core network 130. User IP packets may be transmitted through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to a network operator IP service 150. The operator IP service 150 may include access to the Internet, an intranet, an IP multimedia subsystem (IMS), or packet-switched streaming services.

[0072] Some of the network devices in the wireless communication system 100 (e.g., the base station 105) may include subcomponents such as an access network entity 140, which may be an example of an access node controller (ANC). Each access network entity 140 may communicate with a UE 115 through one or more other access network transmission entities 145 (which may be referred to as radio heads, intelligent radio heads, or transmission and reception points (TRPs)). Each access network transmission entity 145 may include one or more antenna panels. In some configurations, the various functions of each access network entity 140 or the base station 105 may be distributed across various network devices (e.g., radio heads and ANCs) or combined into a single network device (e.g., the base station 105).

[0073] The wireless communication system 100 may operate using one or more frequency bands (generally in the range of 300 megahertz (MHz) to 300 gigahertz (GHz)). Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or the decimeter band because the wavelength range is approximately from one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features, but the waves may be sufficient to penetrate structures to serve a UE 115 located indoors in a macro cell. Compared to transmissions using smaller frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, UHF wave transmissions may be associated with smaller antennas and shorter distances (e.g., less than 100 kilometers).

[0074] The wireless communication system 100 can utilize both licensed and unlicensed radio frequency spectrum bands. For example, the wireless communication system 100 can employ Licensed-Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed frequency band such as the 5 GHz Industrial, Scientific, and Medical (ISM) band. When operating in an unlicensed radio frequency spectrum band, devices such as base station 105 and UE 115 can employ carrier sensing for collision detection and avoidance. In some examples, operation in the unlicensed frequency band can be based on a carrier aggregation configuration that combines a component carrier operating in a licensed frequency band (e.g., LAA). Operations in the unlicensed spectrum can include downlink data transmission, uplink transmission, peer-to-peer (P2P) transmission, or device-to-device (D2D) transmission, etc.

[0075] Base station 105 or UE 115 can be equipped with multiple antennas, which can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of base station 105 or UE 115 can be located within one or more antenna arrays or antenna panels, which can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays can be co-located at an antenna assembly, such as an antenna tower. In some examples, the antennas or antenna arrays associated with base station 105 can be located at different geographical locations. Base station 105 can have an antenna array having a number of rows and columns of antenna ports that base station 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 can have one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, an antenna panel can support radio frequency beamforming for signals transmitted via antenna ports.

[0076] Base station 105 or UE 115 can use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. Such a technique can be referred to as spatial multiplexing. For example, a transmitting device can transmit multiple signals via different antennas or different combinations of antennas. Similarly, a receiving device can receive multiple signals via different antennas or different combinations of antennas. Each of the multiple signals can be referred to as a separate spatial stream and can carry bits associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers can be associated with different antenna ports for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO) (where multiple spatial layers are transmitted to the same receiving device) and multi-user MIMO (MU-MIMO) (where multiple spatial layers are transmitted to multiple devices).

[0077] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting device or a receiving device (e.g., base station 105, UE 115) to form or direct an antenna beam (e.g., transmit beam, receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming can be achieved by combining signals transmitted via the antenna elements of an antenna array such that some signals propagating in a particular orientation relative to the antenna array experience constructive interference while other signals experience destructive interference. The adjustment of the signals transmitted via the antenna elements can include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to the signals carried via the antenna elements associated with the device. The adjustment associated with each antenna element in the antenna elements can be defined by a set of beamforming weights associated with a particular orientation (e.g., relative to the antenna array of the transmitting device or the receiving device, or relative to some other orientation).

[0078] As part of the beamforming operation, the base station 105 or the UE 115 can use beam scanning techniques. For example, the base station 105 can use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with the UE 115. The base station 105 can transmit some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) multiple times in different directions. For example, the base station 105 can transmit signals according to different sets of beamforming weights associated with different transmission directions. Transmissions in different beam directions can be used (e.g., by the transmitting device such as the base station 105 or by the receiving device such as the UE 115) to identify the beam direction for subsequent transmissions or receptions performed by the base station 105.

[0079] The base station 105 can transmit some signals (e.g., data signals associated with the receiving device) in a single beam direction (e.g., the direction associated with a particular receiving device such as the UE 115). In some examples, the beam direction associated with the transmission along a single beam direction can be determined based on the signals transmitted in one or more beam directions. For example, the UE 115 can receive one or more of the signals transmitted by the base station 105 in different directions and can report to the base station 105 an indication of the signal received by the UE 115 that has the highest signal quality or otherwise acceptable signal quality.

[0080] In some examples, multiple beam directions may be used to perform transmissions by a device (e.g., by base station 105 or UE 115), and the device may use a combination of digital precoding or radio frequency beamforming to generate a combined beam for transmission (e.g., from base station 105 to UE 115). UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured number of beams across the system bandwidth or one or more subbands. Base station 105 may transmit reference signals that may or may not be precoded (e.g., cell-specific reference signal (CRS), channel state information reference signal (CSI-RS)). UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel type codebook, linear combination type codebook, port selection type codebook). Although these techniques are described with reference to signals transmitted by base station 105 in one or more directions, UE 115 may employ similar techniques to transmit signals multiple times in different directions (e.g., to identify beam directions for subsequent transmissions or receptions by UE 115) or to transmit signals in a single direction (e.g., to transmit data to a receiving device).

[0081] When receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from base station 105, a receiving device (e.g., UE 115) may attempt multiple receiving configurations (e.g., directional listening). For example, the receiving device may receive by receiving via different antenna subarrays, by processing received signals according to different antenna subarrays, by receiving according to different sets of receive beamforming weights applied to signals received at multiple antenna elements of the antenna array (e.g., different sets of directional listening weights), or by processing received signals according to different sets of receive beamforming weights applied to signals received at multiple antenna elements of the antenna array (any of the above operations may be referred to as "listening" according to different receiving configurations or receiving directions), thereby attempting multiple receiving directions. In some examples, the receiving device may use a single receiving configuration to receive along a single beam direction (e.g., when receiving a data signal). The single receiving configuration may be aligned in a beam direction determined based on listening according to different receiving configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or otherwise acceptable signal quality based on listening according to multiple beam directions).

[0082] The wireless communication system 100 can be a packet-based network that operates according to a layered protocol stack. In the user plane, communication at the bearer or packet data convergence protocol (PDCP) layer can be IP-based. The radio link control (RLC) layer can perform packet segmentation and reassembly for transmission over logical channels. The media access control (MAC) layer can perform priority handling and multiplexing of logical channels to transport channels. The MAC layer can also use error detection techniques, error correction techniques, or both to support retransmission at the MAC layer to improve link efficiency. In the control plane, the RRC protocol layer can provide the establishment, configuration, and maintenance of an RRC connection (which supports radio bearers for user plane data) between the UE 115 and the base station 105 or the core network 130. At the physical layer, transport channels can be mapped to physical channels.

[0083] The UE 115 and the base station 105 of the wireless communication system 100 can support retransmission of data to increase the likelihood that the data is successfully received. Hybrid automatic repeat request (HARQ) feedback is a technique for increasing the likelihood that data is correctly received over the communication link 125. HARQ can include a combination of error detection (e.g., using cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ can improve throughput at the MAC layer in poor radio conditions (e.g., low signal-to-noise conditions). In some examples, a device can support same-slot HARQ feedback, where the device can provide HARQ feedback for data received in previous symbols in a particular slot in that slot. In other cases, the device can provide HARQ feedback in a subsequent slot or according to some other time interval.

[0084] The UE 115 and the base station 105 of the wireless communication system 100 can support techniques for multi-component carrier downlink scheduling. Specifically, the techniques described herein can enable one or more DCI messages to schedule multiple downlink data transmissions at the UE, where the multiple downlink transmissions are associated with one or more TRPs (e.g., multiple CORESET groups) and are received across one or more component carriers. By enabling DCI messages to schedule downlink data transmissions for multiple TRPs (e.g., multiple CORESET groups) across one or more component carriers, the techniques described herein can reduce the control signaling overhead associated with downlink scheduling within the wireless communication system 100 and can enable more flexible use of communication resources.

[0085] For example, in some aspects, the base station 105 of the wireless communication system 100 may send a first DCI message and a second DCI message to the UE 115. The first DCI message may be associated with a first TRP of the base station 105, and the second DCI message may be associated with a second TRP of the base station 105. In this regard, the first DCI message may be received in a CORESET of a first CORESET group (e.g., CORESETPoolIndex 0) associated with the first TRP, and the second DCI message may be received in a second CORESET of a second CORESET group (e.g., CORESETPoolIndex 1) associated with the second TRP. In this example, the first DCI message may schedule a first downlink data transmission (e.g., PDSCH transmission) in a first component carrier and a second downlink data transmission in a second component carrier at the UE 115, where the first downlink data transmission and the second downlink data transmission are associated with the first CORESET group (e.g., the first TRP). Similarly, the second DCI message may schedule a third downlink data transmission and a fourth downlink data transmission associated with the second CORESET group (e.g., the second TRP). The third and fourth downlink data transmissions may be scheduled for component carriers that are the same as or different from the component carriers for the first downlink data transmission and the second downlink data transmission. For example, the third downlink data transmission may be scheduled on the second component carrier, and the fourth downlink data transmission may be scheduled on the fourth component carrier. In some aspects, the DCI message may schedule downlink data transmission on a component carrier that is the same as or different from the component carrier on which the DCI message is sent to the UE 115.

[0086] In additional or alternative aspects, a single DCI may be used to schedule multiple downlink data transmissions associated with multiple CORESET groups (e.g., multiple TRPs) across one or more component carriers. For example, in some cases, the base station 105 may send a single DCI message to the UE 115. In this example, the single DCI message may schedule a first downlink data transmission and a second downlink data transmission in a single component carrier, where the first downlink data transmission is associated with a first CORESET group (e.g., the first TRP), and the second downlink data transmission is associated with a second CORESET group (e.g., the second TRP). Additionally, the first downlink data transmission and the second downlink data transmission may be scheduled for component carriers that are the same as or different from the component carrier on which the single DCI message is received.

[0087] In an additional or alternative scenario, a single DCI message sent to UE 115 can be used to schedule multiple downlink data transmissions associated with different CORESET groups (e.g., different TRPs) across multiple component carriers. For example, a single DCI message can schedule a first downlink data transmission associated with a first CORESET group (e.g., a first TRP) on a first component carrier, and can additionally schedule a second downlink data transmission associated with a second CORESET group (e.g., a second TRP) on a second component carrier. In this example, the first downlink data transmission or the second downlink data transmission can be scheduled on a component carrier that is the same as or different from the component carrier on which the single DCI message is received.

[0088] In some aspects, UE 115 of wireless communication system 100 can be preconfigured to interpret a DCI message received from base station 105 as scheduling multiple downlink data transmissions associated with a given CORESET group. For example, base station 105 can send RRC signaling to UE 115, where the RRC signaling includes a CIF value for indicating the association between a component carrier and a TRP (e.g., a CORESET group). Specifically, the CIF value can indicate one or more mapping pairs, where each mapping pair indicates the association between a given component carrier and a given CORESET group. In this regard, the CIF value indicated in the RRC signaling can provide a set of indices for indicating TRP-component carrier mapping pairs. Subsequently, a DCI message received from base station 105 can include an indication (e.g., an index or a mapping pair) of the CIF value that corresponds to one or more indices or mapping pairs in the set of indices indicated via the RRC signaling. Thus, UE 115 can be configured to monitor a set of downlink resources across the determined component carriers based on the CIF value (e.g., a set of indices, a set of mapping pairs) indicated in the RRC signaling and the CIF value (e.g., an index or a mapping pair) indicated in the received DCI message.

[0089] The techniques described herein can enable multiple downlink data transmissions associated with a given CORESET group to be scheduled within or across multiple component carriers via one or more DCI messages. Specifically, a DCI message can be configured to schedule multiple downlink data transmissions associated with one or more CORESET groups (e.g., CORESETPoolIndex 0, CORESETPoolIndex 1) within a single component carrier, across multiple component carriers, or both. By utilizing a single DCI message to achieve the scheduling of multiple downlink data transmissions associated with a CORESET group, the control signaling overhead within wireless communication system 100 can be reduced, and the flexibility of scheduling downlink data transmissions can be improved.

[0090] Figure 2 FIG. 2 shows an example of a wireless communication system 200 that supports techniques for multi-component carrier scheduling in accordance with aspects of the present disclosure. In some examples, the wireless communication system 200 may implement aspects of the wireless communication system 100. The wireless communication system 200 may include a base station 105-a and a UE 115-a, which may be examples of the UE 115 and the base station 105 as described with reference to Figure 1 FIG. 1.

[0091] The UE 115-a may communicate with the base station 105-a using a communication link 205. In some cases, the communication link 205 may include an example of an access link (e.g., Uu link). The communication link 205 may include a bi-directional link that may include both uplink communication and downlink communication. In one aspect, the UE 115-a may use the communication link 205 to send an uplink transmission such as an uplink message or uplink signal to the base station 105-a, and the base station 105-a may use the communication link 205 to send a downlink data transmission such as a downlink message or downlink signal to the UE 115-a. In some aspects, the communication link 205 may include a set of component carriers 210 for communication between the UE 115-a and the base station 105-a. For example, the communication link 205 may include a first component carrier 210-a (CC1) and a second component carrier 210-b (CC2). The communication link 205 may include any number of component carriers.

[0092] As previously described herein, a UE may be able to distinguish between transmissions from different TRPs of a base station based on a set of downlink resources associated with different TRPs. A downlink data transmission from one TRP may be sent via a set of downlink resources associated with a first CORESET group (e.g., CORESETPoolIndex 0), while a downlink data transmission from another TRP may be sent via a set of downlink resources associated with a second CORESET group (e.g., CORESETPoolIndex 1). In some aspects, each CORESET group may each include two CORESETs. For example, the first CORESET group may include a first CORESET and a second CORESET, and the second CORESET group may include a third CORESET and a fourth CORESET. The association between the downlink data transmission and the corresponding CORESET group (and thus the TRP) may be indicated via a scheduling DCI message. Additionally or alternatively, the association between the downlink data transmission and the corresponding CORESET group may be determined based on the CORESET group on which the corresponding DCI message is received in combination with the CIF value indicated in the DCI message.

[0093] UE 115-a and base station 105-a of the wireless communication system 200 may support techniques for multi-component carrier downlink scheduling. Specifically, the techniques described herein may enable one or more DCI messages to schedule multiple downlink data transmissions at the UE, where the multiple downlink transmissions are associated with one or more TRPs (e.g., multiple CORESET groups) and are received across one or more component carriers. By enabling DCI messages to schedule downlink data transmissions for multiple TRPs (e.g., multiple CORESET groups) across multiple component carriers, the techniques described herein may reduce the control signaling overhead associated with downlink scheduling within the wireless communication system 100 and may enable more flexible use of communication resources.

[0094] For example, base station 105-a may determine a first set of downlink resources, where the first set of downlink resources may be associated with a first CORESET group (e.g., CORESETPoolIndex 0). In this regard, the first set of downlink resources may be associated with a first TRP of base station 105-a. The first set of downlink resources may include a set of time resources and a set of frequency resources to be used by UE 115-a. The first set of downlink resources may be associated with one or more component carriers 210 used in the communication between UE 115-a and base station 105-a. In some aspects, base station 105-a may additionally determine a first set of parameters associated with the first set of downlink resources, the first CORESET group (e.g., the first TRP), or both.

[0095] In some aspects, the first downlink resources may include downlink resources within one or more component carriers 210. For example, the first set of downlink resources may include time and frequency resources within a single component carrier 210 of UE 115-a (e.g., first component carrier 210-a or second component carrier 210-b). As another example, the first set of downlink resources may include time and frequency resources in both the first component carrier 210-a and the second component carrier 210-b. In this example, the first set of downlink resources may include a first subset of downlink resources associated with the first component carrier 210-a and a second subset of downlink resources associated with the second component carrier 210-b.

[0096] Similarly, base station 105-a may determine a second downlink resource set, where the second downlink resource set may be associated with a second CORESET group (e.g., CORESETPoolIndex 1). In this regard, the second downlink resource set may be associated with a second TRP of base station 105. The second downlink resource set may include a set of time resources and a set of frequency resources to be used by UE 115-a. Additionally, the second downlink resource set may be different from the first downlink resource set in the time domain, the frequency domain, or both.

[0097] In some aspects, the second downlink resource set may include downlink resources in one or more component carriers 210. For example, the second downlink resource set may include time and frequency resources within a single component carrier 210 of UE 115-a (e.g., first component carrier 210-a or second component carrier 210-b). As another example, the second downlink resource set may include time and frequency resources in first component carrier 210-a and second component carrier 210-b. In this example, the second downlink resource set may include a first subset of downlink resources associated with first component carrier 210-a and a second subset of downlink resources associated with second component carrier 210-b. In some aspects, the second downlink resource set may include a subset of downlink resources on one or more component carriers 210 associated with the first downlink resource set.

[0098] In some aspects, base station 105-a may additionally determine a set of parameters for communicating with UE 115-a, where the set of parameters is associated with the first and second downlink resource sets. In this regard, base station 105-a may determine a first set of parameters associated with the first downlink resource set and a second set of parameters associated with the second downlink resource set. The second set of parameters may be different from the first set of parameters. Parameters included within the respective sets of parameters may include but are not limited to HARQ configuration, PDSCH scrambling sequence, CRS rate matching configuration, transmission configuration indicator (TCI) state, or any combination thereof.

[0099] In some aspects, base station 105-a may send RRC message 215 to UE 115-a. RRC message 215 may be sent on first component carrier 210-a, second component carrier 210-b, or both. For example, as Figure 2As shown, the RRC message 215 can be sent via the first component carrier 210-a. In some aspects, the base station 105-a can send the RRC message 215 based on determining a first set of downlink resources associated with a first CORESET group (e.g., a first TRP), determining a second set of downlink resources associated with a second CORESET group (e.g., a second TRP), or both. In some aspects, the RRC message 215 can indicate the association between one or more CORESET groups and one or more component carriers 210 of the UE 115-a. For example, the RRC message 215 can indicate that the first CORESET group (e.g., CORESETPoolIndex 0) is associated with the first component carrier 210-a and the second component carrier 210-a, and can also indicate that the second CORESET group (e.g., CORESETPoolIndex 1) is associated with the first subcarrier 210-a and the second component carrier 210-b. As another example, the RRC message 215 can indicate that the first CORESET group, the second CORESET group, or both are associated with a third component carrier (not shown).

[0100] In an additional or alternative aspect, the RRC message 215 may indicate the association between a CORESET group (e.g., a TRP) and the component carrier 210 via one or more CIF values. Specifically, the one or more CIF values may indicate one or more mapping pairs, where each mapping pair includes a component carrier and a CORESET group. In this regard, the CIF values indicated in the RRC message 215 may be associated with one or more component carriers 210, one or more CORESET groups, or both. For example, in some cases, the RRC message 215 may include a set of CIF values, where a first CIF value indicates a first mapping pair including a first component carrier 210-a and a first CORESET group. In this example, the first mapping pair indicated in the first CIF value may indicate that the first component carrier 210-a is associated with the first CORESET group (e.g., CIF 1 = {CC1, CORESETPoolIndex 0}). Thus, the first mapping pair indicated in the first CIF (e.g., CIF 1) may include {CC1, CORESETPoolIndex 0}. Similarly, the RRC message 215 may include a second CIF value that indicates a second mapping pair including a second component carrier 210-b and the first CORESET group. In this example, the second mapping pair indicated in the second CIF value may indicate that the second component carrier 210-b is associated with the first CORESET group (e.g., CIF 2 = {CC2, CORESETPoolIndex 0}). Thus, the second mapping pair indicated in the second CIF (e.g., CIF 2) may include {CC2, CORESETPoolIndex 0}.

[0101] As another example, a third CIF value may indicate a third mapping pair including the first component carrier 210-a and a second CORESET group. In this example, the third CIF value indicated in the RRC message 215 may indicate that the first component carrier 210-a is associated with the second CORESET group (e.g., CIF 3 = {CC1, CORESETPoolIndex 1}). Thus, the third mapping pair indicated in the third CIF (e.g., CIF 3) may include {CC1, CORESETPoolIndex 1}. Note here that the RRC message 215 may include any number of CIF values, where each CIF value includes a mapping pair indicating the association between the component carrier 210 and the CORESET group.

[0102] Additionally or alternatively, each CIF value indicated in the RRC message 215 may be associated with two mapping pairs that indicate two separate associations between the component carrier 210 and the CORESET groups. For example, the first CIF value may include two mapping pairs indicating that the first component carrier 210a is associated with the first CORESET group and the second CORESET group (e.g., CIF 1 = ({CC1, CORESETPoolIndex 0}, {CC1, CORESETPoolIndex 1})). In this example, the first CIF (e.g., CIF 1) includes the first mapping pair {CC1, CORESETPoolIndex 0} that includes the first component carrier 210a and the first CORESET group, and the second mapping pair {CC1, CORESETPoolIndex 1} that includes the first component carrier 210a and the second CORESET group.

[0103] As another example, the second CIF value may include two mapping pairs that indicate that the first component carrier 210-a is associated with the first CORESET group and the second component carrier 210-b is associated with the second CORESET group (e.g., CIF 2 = ({CC1, CORESETPoolIndex 0}, {CC2, CORESETPoolIndex 1})). In this example, the second CIF (e.g., CIF 2) includes: the first mapping pair {CC1, CORESETPoolIndex 0} that includes the first component carrier 210-a and the first CORESET group; and the second mapping pair {CC2, CORESETPoolIndex 1} that includes the second component carrier 210-b and the second CORESET group.

[0104] In some aspects, a CIF value may use a single mapping pair to indicate that both the first CORESET group and the second CORESET group are associated with the same component carrier 210. For example, in some cases, the CIF value indicated in the RRC message 215 may indicate a mapping pair that includes the first component carrier 210-a and the third CORESET group (e.g., CORESETPoolIndex 2) (e.g., CIF = {CC1, CORESETPoolIndex 2}). In this example, the indication of the third CORESET group within the mapping pair may indicate that both the first CORESET group and the second CORESET group are associated with the first component carrier 210-b.

[0105] In some aspects, base station 105-a may send a first DCI message 220-a to UE 115-a, where the first DCI message 220-a schedules a downlink data transmission 225 at UE 115-a. Base station 105-a may send the first DCI message 220-a on the first component carrier 210-a, the second component carrier 210-b, a third component carrier (not shown), or any combination thereof. In some aspects, base station 105-a may send the first DCI message 220-a based on determining a first set of downlink resources associated with a first CORESET group, determining a second set of downlink resources associated with a second CORESET group, sending an RRC message 215, or any combination thereof. Similarly, UE 115-a may receive the first DCI message 220-a based on receiving the RRC message 215.

[0106] In some aspects, the first DCI message 220-a may indicate the first set of downlink resources, the second set of downlink resources, or both. Additionally or alternatively, the first DCI message 220-a may be associated with one or more component carriers 210, one or more CORESET groups, or both. For example, the first DCI message 220-a may be sent in the first CORESET group, the second CORESET group, or both. For example, the first DCI message 220-a may be sent in the first CORESET group and may thus include an indication of the first set of downlink resources associated with the first CORESE group. As another example, the first DCI message 220-a may be sent in the second CORESET group and may thus include an indication of the second set of downlink resources associated with the second CORESET group.

[0107] In some cases, the first DCI message 220-a may include the value of the CIF, where the value of the CIF corresponds to one or more CIF values indicated in the RRC message 215. In this regard, the first DCI message 220-a may include the CIF indicating one or more mapping pairs, where each mapping pair indicates the association between a component carrier and one or more CORESET groups. In this regard, the CIF value indicated in the RRC message 215 may indicate a set of indexes corresponding to the mapping pairs of the component carrier and the CORESET group (e.g., {CC1, CORESETPoolIndex 0}, {CC2, CORESETPoolIndex 0}), and the value of the CIF indicated in the first DCI message 220-a may indicate the index corresponding to the index in the set of indexes indicated in the RRC message 215. Therefore, the value of the CIF indicated in the first DCI message 220-a may indicate one or more mapping pairs (e.g., the association between the component carrier 210 and the CORESET group) to be used by the UE 115-a. In some aspects, one or more values of the CIF indicated in the first DCI message 220-a may be associated with the first CORESET group, the second CORESET group, or both. For example, in some cases, one or more values of the CIF indicated in the first DCI message 220-a may indicate the association between the first CORESET group and one or more component carriers 210 and the association between the second CORESET group and one or more component carriers 210.

[0108] In some cases, the base station 105-a may additionally send a second DCI message 220-b to the UE 115-a, where the second DCI message 220-b schedules the downlink data transmission 225 at the UE 115-a. The base station 105-a may send the second DCI message 220-b on the first component carrier 210-a, the second component carrier 210-b, the third component carrier (not shown), or any combination thereof. In some aspects, the base station 105-a may send the second DCI message 220-b based on determining a first set of downlink resources associated with the first CORESET group, determining a second set of downlink resources associated with the second CORESET group, sending the RRC message 215, sending the first DCI message 220-a, or any combination thereof. Similarly, the UE 115-a may receive the second DCI message 220-b based on receiving the RRC message 215, receiving the first DCI message 220-a, or both.

[0109] In some cases, the second DCI message 220-b may be sent in the first CORESET group, the second CORESET group, or both. For example, in a case where the first DCI message 220-a is sent in the first CORESET group (e.g., CORESETPoolIndex 0), the second DCI message 220-b may be sent in the second CORESET group (e.g., CORESETPoolIndex 1). In this regard, the first DCI message 220-a may be associated with the first TRP of the base station 105-a and may indicate a first set of downlink resources, and the second DCI message 220-b may be associated with the second TRP of the base station 105-b and may indicate a second set of downlink resources.

[0110] As another example, the first DCI message 220-a may be sent in the second CORESET group (e.g., CORESETPoolIndex 1), and the second DCI message 220-b may be sent in the first CORESET group (e.g., CORESETPoolIndex 0). In this example, the first DCI message 220-a may include an indication of a second set of downlink resources associated with the second CORESET group, and the second DCI message 220-b may include an indication of a first set of downlink resources associated with the first CORESET group.

[0111] As previously mentioned herein, the second DCI message 220-b may indicate the CORESET group and / or the component carrier 210 to be used for communication at the UE 115-a via the value indicated in the CIF of the corresponding DCI message 220. For example, the second DCI message 220-b may include an indication of the value of the CIF, and the value of the CIF includes one or more mapping pairs indicating the association between the component carrier and one or more CORESET groups. In this regard, the CIF value indicated in the RRC message 215 may indicate a set of indices corresponding to the mapping pairs of the component carrier 210 and the CORESET group (e.g., {CORESETPoolIndex 0, CC1}, {CORESETPoolIndex 0, CC2}), and the value of the CIF indicated in the second DCI message 220-b may indicate an index (e.g., one or more mapping pairs) corresponding to the index (e.g., one or more mapping pairs) in the set of indices indicated in the RRC message 215.

[0112] Thus, the value of the CIF indicated in the first DCI message 220-a, the second DCI message 220-b, or both, can indicate which CORESET set and component carrier 210 pair the UE 115-a will use when communicating with the base station 105-a. In some aspects, the value of the CIF value indicated in the first DCI message 220-a, the second DCI message 220-b, or both, can be associated with the first CORESET set, the second CORESET set, or both.

[0113] In some aspects, the UE 115-a can determine a first downlink resource set associated with the first CORESET set (e.g., the first TRP) and a second downlink resource set associated with the second CORESET set (e.g., the second TRP). In some aspects, the UE 115-b can determine the first downlink resource set, the second downlink resource set, or both based on receiving the RRC message 215, receiving the first DCI message 220-a, receiving the second DCI message 220-b, or any combination thereof. For example, the UE 115-a can determine the first downlink resource set, the second downlink resource set, or both based on an indication of the first downlink resource set indicated in the first DCI message 220-a, the second DCI message 220-b, or both.

[0114] In some aspects, the UE 115-b can determine whether the first downlink resource set, the second downlink resource set, or both are associated with one or more component carriers 210. For example, the UE 115-a can determine that the first downlink resource set associated with the first CORESET set includes a first subset of downlink resources associated with the first component carrier 210-a (e.g., within the first component carrier 210-a) and a second subset of downlink resources associated with the second component carrier 210-b (e.g., within the second component carrier 210). Similarly, the UE 115-a can determine that the second downlink resource set associated with the second CORESET set includes a first subset of downlink resources associated with the first component carrier 210-a (e.g., within the first component carrier 210-a) and a second subset of downlink resources associated with the second component carrier 210-b (e.g., within the second component carrier 210-b).

[0115] As another example, the UE 115-a may determine that the first downlink resource set, the second downlink resource set, or both are associated with a single component carrier 210 (e.g., the first component carrier 210-a or the second component carrier 210-b). In some aspects, the UE 115-a may determine that the first downlink resource set, the second downlink resource set, or both are associated with a component carrier 210 that is the same as or different from the component carrier 210 on which the corresponding DCI messages 220-a and 220-b are received (e.g., the first component carrier 210-a). In some aspects, the UE 115-a may determine the association between the first and second downlink resource sets and one or more component carriers based on the CIF value indicated in the RRC message 215, the values of the CIFs indicated in the DCI messages 220-a and 220-b, or any combination thereof.

[0116] In some aspects, the UE 115-a may additionally determine the first parameter set, the second parameter set, or both associated with the corresponding downlink resource set. In this regard, the UE 115-b may determine the parameter set associated with the corresponding CORESET group for communication with the base station 105-a (e.g., HARQ configuration, PDSCH scrambling sequence, CRS rate matching configuration, TCI state). The UE 115-a may determine the parameter set based on the RRC message 215, the first DCI message 220-a, the second DCI message 220-b, or any combination thereof. Additionally, in some cases, the UE 115-a may be preconfigured with the parameter set associated with the corresponding CORESET group.

[0117] In some aspects, the UE 115-a may monitor the first downlink resource set, the second downlink resource set, or both for downlink data transmission 225. The UE 115-a may monitor the first downlink resource set and / or the second downlink resource set based on identifying the corresponding downlink resource set. For example, the UE 115-a may monitor one or more component carriers 210 for downlink data transmission 225 based on the determined association between the corresponding CORESET group and one or more component carriers 210. For example, in some cases, the first DCI message 220-a may include one or more CIF values that indicate that both the first CORESET group and the second CORESET group are associated with the first component carrier 210-a. In this example, the UE 115-a may monitor the first downlink resource set associated with the first CORESET group and the second downlink resource set associated with the second CORESET group according to (e.g., based on) the one or more CIF values in the first DCI message 220-a.

[0118] As another example, the first DCI message 220-a may include a first CIF value indicating that the first CORESET set is associated with the first component carrier 210-a and a second CIF value indicating that the second CORESET set is associated with the second component carrier 210-b. In this example, the UE 115-a may monitor a first set of downlink resources on the first component carrier 210-a according to (e.g., based on) the first CIF value in the first DCI message 220-a, and may monitor a second set of downlink resources on the second component carrier 210-b according to (e.g., based on) the second CIF value in the first DCI message 220-a.

[0119] In some aspects, the UE 115-a may receive a downlink data transmission 225 from the base station 105-a. The downlink data transmission may include a PDSCH transmission. The UE 115-a may receive the downlink data transmission 225 based on the RRC message 215, the DCI messages 220a and 220b, determining the first and second sets of downlink resources, monitoring the first and second sets of downlink resources, or any combination thereof. In this regard, the base station 105-a may communicate with the UE 115-a (e.g., send / receive one or more downlink data transmissions 225) using a first set of parameters associated with the first CORESET set, a second set of parameters associated with the second CORESET set, or both.

[0120] The downlink data transmission 225 sent by the base station 105-a may be associated with the first CORESET set and / or the second CORESET set, and may be received across one or more component carriers 210. For example, the UE 115-a may receive one or more first downlink data transmissions 225 on a first set of downlink resources associated with the first CORESET set, and may receive one or more second downlink data transmissions 225 in a second set of downlink resources associated with the second CORESET set.

[0121] For example, the first DCI message 220-a may indicate that the first CORESET group is associated with both the first component carrier 210-a and the second component carrier 210-b, and the second DCI message 220-b may indicate that the second CORESET group is associated with both the first component carrier 210-a and the second component carrier 210-b. In this example, the UE 115-a may receive four separate downlink data transmissions 225: a first downlink data transmission 225-a associated with the first CORESET group on the first component carrier 210-a, a second downlink data transmission 225-b associated with the first CORESET group on the second component carrier 210-b, a third downlink data transmission 225-c associated with the second CORESET group on the first component carrier 210-a, and a fourth downlink data transmission 225-d associated with the second CORESET group on the second component carrier 210-b.

[0122] To give another example, the UE 115-a may receive a single DCI message 220 (e.g., the first DCI message 220-a or the second DCI message 220-b), where the single DCI message 220 indicates that the first CORESET group and the second CORESET group are associated with the first component carrier 210-a. In this example, the UE 115-a may receive a downlink data transmission 225-a associated with the first CORESET group on the first component carrier 210-a and a downlink data transmission 225-d associated with the second CORESET group on the first component carrier 210-a. Conversely, in another example, the UE 115-a may receive a single DCI message 220 (e.g., the first DCI message 220-a or the second DCI message 220-b), where the single DCI message 220 indicates that the first CORESET group is associated with the first component carrier 210-a and the second CORESET group is associated with the second component carrier 210-b. In this example, the UE 115-a may receive a downlink data transmission 225-a associated with the first CORESET group on the first component carrier 210-a and a downlink data transmission 225-d associated with the second CORESET group on the second component carrier 210-b.

[0123] In some aspects, UE 115-a may send one or more uplink transmissions 230 to base station 105-a. UE 115-a may send one or more uplink transmissions 230 based on RRC message 215, DCI messages 220-a and 220-b, determining first and second downlink resource sets, monitoring first and second downlink resource sets, or any combination thereof. In some aspects, UE 115-a and base station 105-a may communicate with each other (e.g., send / receive downlink data transmissions 225, send / receive uplink transmissions 230) using a first set of parameters associated with a first CORESET group, a second set of parameters associated with a second CORESET group, or both. For example, UE 115-a may send one or more feedback messages (e.g., uplink transmission 230) based on a HARQ configuration associated with the first set of parameters of the first CORESET group, a HARQ configuration associated with the second set of parameters of the second CORESET group, or both.

[0124] The techniques described herein may enable multiple downlink data transmissions associated with a given CORESET group to be scheduled within or across multiple component carriers via one or more DCI messages. Specifically, a DCI message may be configured to schedule multiple downlink data transmissions associated with one or more CORESET groups (e.g., CORESETPoolIndex 0, CORESETPoolIndex 1) within a single component carrier, across multiple component carriers, or both. By utilizing a single DCI message to schedule multiple downlink data transmissions associated with a CORESET group, control signaling overhead within wireless communication system 200 may be reduced, and flexibility in scheduling downlink data transmissions may be increased.

[0125] Figure 3 An example of a resource allocation scheme 300 that supports techniques for multi-component carrier scheduling in accordance with aspects of the present disclosure is shown. In some examples, resource allocation scheme 300 may implement aspects of wireless communication system 100 or 200 or may be implemented by aspects of wireless communication system 100 or 200. In some aspects, Figure 3 resource allocation scheme 300 in shows a first resource configuration 305-a, a second resource configuration 305-b, and a third resource configuration 305-c.

[0126] In some cases, as previously mentioned herein, each DCI message 315 (e.g., Figure 2 the DCI messages 220-a and 220-b shown) may schedule two separate component carriers 310 (e.g., Figure 2Two respective downlink data transmissions 320 (e.g., Figure 2 the downlink data transmission 225 shown) in the component carriers 210-a and 210-b shown, where each downlink data transmission 320 is associated with the same CORESET group. Thus, to schedule multi-CORESET group downlink data transmissions (e.g., multi-TRP downlink data transmissions) on multiple component carriers, two respective DCI messages 315 can be used.

[0127] For example, referring to Figure 3 the resource configuration 305-a shown, the base station 105 can send a first DCI message 315-a to the UE 115 on the first component carrier 310-a. The first DCI message 315-a can be sent in the first CORESET of the first CORESET group (e.g., CORESETPoolIndex 0 and / or the first TRP). In this regard, the first DCI message 315-a can schedule a first downlink data transmission 320-a and a second downlink data transmission 320-b, where both the first and second downlink data transmissions 320-a and 320-b are associated with the first CORESET group. For example, the first DCI message 315-a can schedule the first downlink data transmission 320-a in the first component carrier 310-a, and can schedule the second downlink data transmission 320-b in the second component carrier 310-b.

[0128] Similarly, the base station 105 can send a second DCI message 315-b to the UE 115 on the first component carrier 310-a. However, in some cases, the second DCI message 315-b can be sent on the second component carrier 310-b. The second DCI message 315-b can be sent in the second CORESET of the second CORESET group (e.g., CORESETPoolIndex 1 and / or the second TRP). In this regard, the second DCI message 315-b can schedule a third downlink data transmission 320-c and a fourth downlink data transmission 320-d, where both the third and fourth downlink data transmissions 320-c and 320-d are associated with the second CORESET group. For example, the second DCI message 315-b can schedule the third downlink data transmission 320-c in the first component carrier 310-a, and can schedule the fourth downlink data transmission 320-d in the second component carrier 310-b.

[0129] In some aspects, the first DCI message 315-a, the second DCI message 315-b, or both can indicate, via the value of the CIF within the respective DCI messages 315-a and 315-b, the component carrier 310 to be used for the respective downlink data transmission 320. In this regard, the CIF value indicated in the RRC message can indicate a set of indices corresponding to a component carrier 310 and CORESET group mapping pair (e.g., {CC1, CORESETPoolIndex 0}, {CC2, CORESETPoolIndex 0}). Thus, each value of the CIF indicated in the respective DCI messages 315-a and 315-b can indicate which mapping pair(s) of the component carrier 310 and CORESET group the UE 115 is to use when receiving the downlink data transmission 320. In some cases, the CIF value within the respective DCI message can indicate the component carrier 310 of each mapping pair, while the CORESET group can be indicated / determined as the CORESET group on which each respective DCI message 315 is received.

[0130] For example, the first DCI message 315-a can indicate a value of the CIF that includes a first mapping pair and a second mapping pair. The first mapping pair includes a first component carrier 310-a associated with a first CORESET group (e.g., {CC1, CORESETPoolIndex0}), and the second mapping pair includes a second component carrier 310-b and the first CORESET group (e.g., {CC2, CORESETPoolIndex0}). In this regard, the first mapping pair of the value of the CIF can indicate that the first component carrier 310-a is associated with the first CORESET group, and the second mapping pair of the value of the CIF can indicate that the second component carrier is associated with the second CORESET group. Similarly, as another example, the second DCI message 315-b can include a value of the CIF that includes a first mapping pair and a second mapping pair. The first mapping pair includes the first component carrier 310-a and a second CORESET group (e.g., {CC1, CORESETPoolIndex 1}), and the second mapping pair includes the second component carrier 310-b and the second CORESET group (e.g., {CC2, CORESETPoolIndex 1}). In this regard, the first mapping pair of the value of the CIF can indicate that the first component carrier 310-a is associated with the second CORESET group, and the second mapping pair of the value of the CIF can indicate that the second component carrier is associated with the second CORESET group.

[0131] Continuing with the same example, the first downlink data transmission 320-a can be sent / received according to the first mapping pair of the CIF values included in the first DCI message 315-a, and the second downlink data transmission 320-b can be sent / received according to the second mapping pair of the CIF values included in the first DCI message 315-a. Similarly, the third downlink data transmission 320-c can be sent / received according to the first mapping pair of the CIF values included in the second DCI message 315-b, and the fourth downlink data transmission 320-d can be sent / received according to the second mapping pair of the CIF values included in the second DCI message 315-b.

[0132] In some aspects, the DCI message 315 can be used to schedule downlink data transmissions across three or more component carriers 310. For example, as shown in the resource configuration 305-b, the base station 105 can send the first DCI message 315-c in the CORESET of the first CORESET group via the first component carrier 310-c, and send the second DCI message 315-d in the CORESET of the second CORESET group via the first component carrier 310-c. In this example, the first DCI message 315-c can schedule the first downlink data transmission 320-e in the first component carrier 310-c and the second downlink data transmission 320-f in the second component carrier 310-d. Additionally or alternatively, the second DCI message 315-d can schedule the third downlink data transmission 320-g in the first component carrier 310-c and the fourth downlink data transmission 320-h in the third component carrier 310-e.

[0133] As previously mentioned herein, the DCI message 315 can be sent via different component carriers 310. For example, as shown in the resource configuration 305-c, the base station 105 can send the first DCI message 315-e in the CORESET of the first CORESET group via the first component carrier 310-f, and send the second DCI message 315-f in the CORESET of the second CORESET group via the second component carrier 310-g. In this example, the first DCI message 315-e can schedule the first downlink data transmission 320-i in the first component carrier 310-f and the second downlink data transmission 320-j in the third component carrier 310-h. Additionally or alternatively, the second DCI message 315-f can schedule the third downlink data transmission 320-k in the first component carrier 310-f and the fourth downlink data transmission 320-l in the second component carrier 310-g.

[0134] In some aspects, Figure 3Any DCI message in the DCI message 315 shown can indicate the association (e.g., index) between the corresponding CORESET group and the component carrier 310 via the value of the CIF (e.g., mapping pair) indicated in the DCI message 315. In addition, the DCI message 315 can be received via any component carrier 310 and can be used to schedule downlink data transmission in the same or different component carriers 310 on which the corresponding DCI message 315 is received.

[0135] The resource configurations 305-a, 305-b, and 305-c described herein can enable scheduling of multiple downlink data transmissions 320 associated with a given CORESET group across multiple component carriers 310 via one or more DCI messages 315. Specifically, the DCI message 315 can be configured to schedule multiple downlink data transmissions 320 associated with a single CORESET group (e.g., CORESETPoolIndex0 or CORESETPoolIndex 1) across multiple component carriers 310. By using a single DCI message 315 to implement the scheduling of multiple downlink data transmissions 320 associated with a CORESET group, the control signaling overhead within a wireless communication system (e.g., wireless communication system 100 or 200) can be reduced, and the flexibility of scheduling downlink data transmissions 320 can be improved.

[0136] Figure 4 An example of a resource allocation scheme 400 that supports techniques for multi-component carrier scheduling in accordance with aspects of the present disclosure is shown. In some examples, the resource allocation scheme 400 can implement aspects of the wireless communication system 100 or 200 or can be implemented by aspects of the wireless communication system 100 or 200. In some aspects, Figure 4 The resource allocation scheme 400 in shows a first resource configuration 405-a and a second resource configuration 305-b.

[0137] In some cases, as previously mentioned herein, the DCI message 415 (e.g., Figure 2 the DCI messages 220-a and 220-b shown) can schedule two separate downlink data transmissions 420 (e.g., Figure 2 the downlink data transmissions 225 shown) in the same component carrier 410 (e.g., Figure 2 the component carriers 210-a and 210-b shown), where each downlink data transmission 420 is associated with a different CORESET group (e.g., different TRPs).

[0138] For example, with reference to Figure 4For the resource configuration 405-a shown, the base station 105 may send a DCI message 415-a to the UE 115 on the first component carrier 410-a. The DCI message 415-a may be sent / received in the CORESET of the first CORESET group (e.g., CORESETPoolIndex 0 and / or the first TRP), the second CORESET group (e.g., CORESETPoolIndex 1 and / or the second TRP), or both. In this regard, the DCI message 415-a may be associated with both the first CORESET group and the second CORESET group. In some aspects, the DCI message 415-a may schedule a first downlink data transmission 420-a and a second downlink data transmission 420-b in the first component carrier 410-a. In this example, the first downlink data transmission 420-a may be associated with the first CORESET group, and the second downlink data transmission 420-b may be associated with the second CORESET group.

[0139] In some aspects, the CIF value may use a single mapping pair to indicate that both the first CORESET group and the second CORESET group are associated with the same component carrier 410. For example, in some cases, the DCI message 415-a may include a value of the CIF indicating a mapping pair that includes the first component carrier 410-a and a third CORESET group (e.g., CORESETPoolIndex 2) (e.g., CIF = {CC1, CORESETPoolIndex 2}). In this example, the indication of the third CORESET group within the mapping pair may indicate that both the first CORESET group and the second CORESET group are associated with the first component carrier 410-a.

[0140] The resource configurations 405-a and 405-b described herein may enable scheduling of multiple downlink data transmissions 420 associated with multiple CORESET groups within a single component carrier 410 via a single DCI message 415. Specifically, the DCI message 415 may be configured to schedule multiple downlink data transmissions 420 associated with multiple CORESET groups (e.g., CORESETPoolIndex 0 or CORESETPoolIndex 1) within a single component carrier 410. By implementing the scheduling of multiple downlink data transmissions 420 associated with multiple CORESET groups using a single DCI message 415, the control signaling overhead within a wireless communication system (e.g., wireless communication system 100 or 200) may be reduced, and the flexibility in scheduling downlink data transmissions 420 may be improved.

[0141] Figure 5An example of a resource allocation scheme 500 that supports techniques for multi-component carrier scheduling in accordance with aspects of the present disclosure is shown. In some examples, the resource allocation scheme 500 may implement aspects of the wireless communication system 100 or 200 or may be implemented by aspects of the wireless communication system 100 or 200. In some aspects, Figure 5 the resource allocation scheme 500 in

[0142] shows a first resource configuration 505-a and a second resource configuration 505-b. In some cases, as previously mentioned herein, a DCI message 515 (e.g., Figure 2 the DCI messages 220-a and 220-b shown) may schedule two separate downlink data transmissions 520 (e.g., Figure 2 the downlink data transmissions 225 shown) in different component carriers 510 (e.g., Figure 2 the component carriers 210-a and 210-b shown), where each downlink data transmission 520 is associated with a different CORESET group (e.g., a different TRP).

[0143] For example, referring to Figure 5 the resource configuration 505-a shown, the base station 105 may send a DCI message 515-a to the UE 115 on the first component carrier 510-a. The DCI message 515-a may be sent / received in the CORESET of a first CORESET group (e.g., CORESETPoolIndex 0 and / or the first TRP), a second CORESET group (e.g., CORESETPoolIndex 1 and / or the second TRP), or both. In this regard, the DCI message 515-a may be associated with both the first CORESET group and the second CORESET group. In some aspects, the DCI message 515-a may schedule a first downlink data transmission 520-a in the first component carrier 510-a and a second downlink data transmission 520-b in the second component carrier 510-b. In this example, the first downlink data transmission 520-a may be associated with the first CORESET group, and the second downlink data transmission 520-b may be associated with the second CORESET group.

[0144] As another example, referring to Figure 5For the resource configuration 505-b shown, the base station 105 may send a first DCI message 515-b to the UE 115 on the first component carrier 510-c. Additionally or alternatively, the base station 105 may send a second DCI message 515-c to the UE 115 on the first component carrier 510-c. In this example, the first DCI message 515-b may be sent / received in the CORESET of the first CORESET group (e.g., CORESETPoolIndex 0 and / or the first TRP), the second CORESET group (e.g., CORESETPoolIndex 1 and / or the second TRP), or both. In this regard, the first DCI message 515-b may be associated with both the first CORESET group and the second CORESET group. In some aspects, the first DCI message 515-b may schedule a first downlink data transmission 520-c in the first component carrier 510-c and a second downlink data transmission 520-d in the third component carrier 510-e. In this example, the first downlink data transmission 520-c may be associated with the first CORESET group, and the second downlink data transmission 520-d may be associated with the second CORESET group. Continuing to refer to the resource configuration 505-b, the second DCI message 515-c may schedule a third downlink data transmission 520-e in the first component carrier 510-c and a fourth downlink data transmission 520-f in the second component carrier 510-d. In this example, both the third downlink data transmission 520-e and the fourth downlink data transmission 520-f may be associated with the second CORESET group.

[0145] As previously mentioned herein, Figure 5 The DCI messages 515-a, 515-b, and 515-c shown may indicate the association (e.g., index, mapping pair) between the corresponding CORESET group and the component carrier 510 via the value of the CIF indicated in the respective DCI message 515. For example, referring to the resource configuration 505-a, the DCI message 515-a may indicate a value of the CIF that indicates a first mapping pair including the first component carrier 510-a and the first CORESET group (e.g., {CC1, CORESETPoolIndex 0}) and a second mapping pair including the second component carrier 510-b and the second CORESET group (e.g., {CC2, CORESETPoolIndex 0}). In this regard, the first downlink data transmission 520-a may be sent / received according to the first mapping pair of the CIF indicated in the DCI message 515-a, and the second downlink data transmission 520-b may be sent / received according to the second mapping pair of the CIF indicated in the DCI message 515-a.

[0146] The resource configurations 505-a and 505-b described herein may enable multiple downlink data transmissions 520 associated with multiple CORESET groups to be scheduled across multiple component carriers 510 via a single DCI message 515. Specifically, the DCI message 515 may be configured to schedule multiple downlink data transmissions 420 associated with multiple CORESET groups (e.g., CORESETPoolIndex 0 or CORESETPoolIndex 1) across multiple component carriers 510. By implementing the scheduling of multiple downlink data transmissions 520 associated with multiple CORESET groups using a single DCI message 515, the control signaling overhead within a wireless communication system (e.g., wireless communication system 100 or 200) can be reduced, and the flexibility in scheduling downlink data transmissions 520 can be improved.

[0147] Figure 6 An example of a process flow 600 that supports techniques for multi-component carrier scheduling in accordance with aspects of the present disclosure is shown. In some examples, the process flow 600 may implement aspects of or be implemented by the wireless communication system 100 or 200, the resource allocation schemes 300, 400, or 500, or any combination thereof. The process flow 600 may illustrate other aspects such as receiving a DCI, determining a set of downlink resources, and receiving downlink data transmissions associated with a CORESET group, as described with reference to Figures 1 - 5 described.

[0148] In some aspects, the process flow 600 may include a UE 115-b and a base station 105-b, which may be examples of the corresponding devices described herein. Figure 6 The illustrated UE 115-b may be Figure 2 an example of the illustrated UE 115-a. Similarly, Figure 6 the illustrated base station 105-b may be Figure 2 an example of the illustrated base station 105-a.

[0149] In some aspects, the operations illustrated in the process flow 600 may be performed by hardware (e.g., including circuits, processing blocks, logic components, and other components), code executed by a processor (e.g., software or firmware), or any combination thereof. Alternative examples may be implemented, where some steps are performed in a different order than described or not performed at all. In some cases, the steps may include additional features not mentioned below, or additional steps may be added.

[0150] At 605, base station 105-b may determine a first set of downlink resources for UE 115-b to use. In some aspects, the first set of downlink resources may be associated with a first CORESET group (e.g., CORESETPoolIndex 0). The first set of downlink resources may include a set of time resources and a set of frequency resources for UE 115-b to use. The first set of downlink resources may be associated with one or more component carriers used in the communication between UE 115-b and base station 105-b. In some aspects, base station 105-b may additionally determine a first set of parameters associated with the first set of downlink resources, the first CORESET group, or both. The first set of parameters associated with the first set of downlink resources and / or the first CORESET group may include HARQ configuration, PDSCH scrambling sequence, CRS rate matching configuration, TCI state, or any combination thereof.

[0151] In some aspects, the first set of downlink resources may include downlink resources in one or more component carriers. For example, the first set of downlink resources may include time and frequency resources within a single component carrier of UE 115-b. As another example, the first set of downlink resources may include time and frequency resources in a first component carrier and a second component carrier. In this example, the first set of downlink resources may include a first subset of downlink resources associated with the first component carrier and a second subset of downlink resources associated with the second component carrier.

[0152] At 610, base station 105-b may determine a second set of downlink resources for UE 115-b to use. In some aspects, the second set of downlink resources may be associated with a second CORESET group (e.g., CORESETPoolIndex 1). The second set of downlink resources may include a set of time resources and a set of frequency resources for UE 115-b to use. Additionally, the second set of downlink resources may be different from the first set of downlink resources in the time domain, the frequency domain, or both. The second set of downlink resources may be associated with one or more component carriers used in the communication between UE 115-b and base station 105-b. In some aspects, base station 105-b may additionally determine a second set of parameters associated with the second set of downlink resources, the second CORESET group, or both. The second set of parameters associated with the second set of downlink resources and / or the second CORESET group may include HARQ configuration, PDSCH scrambling sequence, CRS rate matching configuration, TCI state, or any combination thereof.

[0153] In some aspects, the second downlink resource set may include downlink resources in one or more component carriers. For example, the second downlink resource set may include time and frequency resources within a single component carrier of UE 115-b. As another example, the second downlink resource set may include time and frequency resources in a first component carrier and a second component carrier. In this example, the second downlink resource set may include a first subset of downlink resources associated with the first component carrier and a second subset of downlink resources associated with the second component carrier.

[0154] At 615, UE 115-b may receive an RRC message from base station 105-b. In some aspects, base station 105-b may send the RRC message at 615 based on determining the first downlink resource set at 605, determining the second downlink resource set at 610, or both. In some aspects, base station 105-b may send the RRC message via a physical downlink control channel (PDCCH).

[0155] In some aspects, the RRC message may indicate the association between one or more CORESET groups and one or more component carriers of UE 115-b. For example, the RRC message may indicate that a first CORESET group (e.g., CORESETPoolIndex 0) is associated with a first component carrier and a second component carrier. In this example, the RRC message may also indicate that a second CORESET group (e.g., CORESETPoolIndex 1) is associated with the second component carrier and a third component carrier.

[0156] In additional or alternative aspects, the RRC message may indicate the association between the CORESET group and the component carrier via one or more CIF values. In this regard, the CIF values indicated in the RRC message may be associated with one or more component carriers, one or more CORESET groups, or both. Specifically, each CIF value among the one or more CIF values included in the RRC message may include one or more mapping pairs, where each mapping pair indicates the association between a component carrier and one or more CORESET groups.

[0157] At 620, UE 115-b may receive a DCI message from base station 105-b. In some aspects, the DCI message may schedule a downlink data transmission at UE 115-b. In some aspects, base station 105-b may send the DCI message at 620 based on determining the first downlink resource set at 605, determining the second downlink resource set at 610, sending the RRC message at 615, or any combination thereof. Similarly, UE 115-b may receive the DCI message at 620 based on receiving the RRC message at 615.

[0158] In some aspects, the DCI message received at 615 may be sent / received in the CORESET of the first CORESET group, the second CORESET group, or both. In this regard, the DCI message may be associated with the first CORESET group and / or the second CORESET group and may indicate the corresponding resource set. For example, the DCI message received at 615 may be sent / received in the CORESET of the first CORESET group, and the DCI message may thus include an indication of a first downlink resource set associated with the first CORESET group. As another example, the DCI message received at 615 may be associated with the first CORESET group and the second CORESET group and may thus include an indication of both the first downlink resource set and the second downlink resource set.

[0159] In some cases, the DCI message received at 620 may indicate the CORESET group and / or component carrier to be used for communication at UE 115-b via the value of the CIF. Specifically, the DCI message may include a value of the CIF, and the value of the CIF includes one or more mapping pairs indicating the association between the component carrier and one or more CORESET groups. In this regard, the CIF value indicated in the RRC message received at 615 may indicate a set of indices corresponding to the CORESET group and component carrier mapping pairs (e.g., {CC1, CORESETPoolIndex 0}, {CC2, CORESETPoolIndex 0}), and the value of the CIF indicated in the DCI message received at 620 may indicate an index (e.g., one or more mapping pairs) corresponding to the index in the set of indices indicated in the RRC message. Thus, the value of the CIF indicated in the DCI message may indicate one or more mapping pairs corresponding to the one or more mapping pairs indicated in the CIF within the RRC message.

[0160] At 625, UE 115-b may receive a second DCI message from base station 105-b. In some aspects, the second DCI message may schedule a downlink data transmission at UE 115-b. In some aspects, base station 105-b may send the second DCI message at 625 based on determining the first downlink resource set at 605, determining the second downlink resource set at 610, sending an RRC message at 615, sending a DCI message at 620, or any combination thereof. Similarly, UE 115-b may receive the DCI message at 625 based on receiving the RRC message at 615, receiving the DCI message at 620, or both.

[0161] In some cases, the DCI messages received at 620 and 625 can be sent / received in the CORESET of the first CORESET group, the CORESET of the second CORESET group, or both. For example, the DCI message received at 620 can be received in the CORESET of the first CORESET group (e.g., CORESETPoolIndex 0), and the second DCI message received at 625 can be received in the CORESET of the second CORESET group (e.g., CORESETPoolIndex 1). In this example, the first DCI message received at 620 can include an indication of a first downlink resource set associated with the first CORESET group, and the second DCI message received at 625 can include an indication of a second downlink resource set associated with the second CORESET group.

[0162] As another example, the DCI message received at 620 can be associated with (e.g., sent / received therein) the second CORESET group (e.g., CORESETPoolIndex 1), and the second DCI message received at 625 can be associated with (e.g., sent / received therein) the first CORESET group (e.g., CORESETPoolIndex 0). In this example, the first DCI message received at 620 can include an indication of a second downlink resource set associated with the second CORESET group, and the second DCI message received at 625 can include an indication of a first downlink resource set associated with the first CORESET group.

[0163] In some cases, the DCI message received at 625 can indicate, via the value of the CIF, the CORESET group and / or component carrier to be used for communication at UE 115-b. The DCI message can include an indication of the value of the CIF, and the value of the CIF includes one or more mapping pairs, where each mapping pair indicates the association between a component carrier and one or more CORESET groups. In this regard, the CIF value indicated in the RRC message received at 615 can indicate a set of indices corresponding to CORESET group and component carrier mapping pairs (e.g., {CC1, CORESETPoolIndex 0}, {CC2, CORESETPoolIndex 0}), and the value of the CIF indicated in the DCI message received at 625 can indicate an index corresponding to an index in the set of indices indicated in the RRC message. Thus, the value of the CIF indicated in the DCI message can indicate one or more mapping pairs corresponding to one or more mapping pairs indicated in the CIF value in the RRC message.

[0164] At 630, UE 115-b may determine a first set of downlink resources associated with a first CORESET group. In some aspects, UE 115-b may determine the first set of downlink resources based on receiving an RRC message at 615, receiving a first DCI message at 620, receiving a second DCI message at 625, or any combination thereof. For example, UE 115-b may determine the first set of downlink resources at 630 based on an indication of the first set of downlink resources indicated in the first DCI message received at 620 and / or the second DCI message received at 625.

[0165] In some aspects, UE 115-b may determine whether the first set of downlink resources is associated with one or more component carriers. For example, UE 115-b may determine that the first set of downlink resources associated with the first CORESET group includes a first subset of downlink resources associated with (e.g., within) a first component carrier and a second subset of downlink resources associated with (e.g., within) a second component carrier. As another example, UE 115-b may determine that the first set of downlink resources is associated with a single component carrier (e.g., the first component carrier or the second component carrier). In some aspects, UE 115-b may determine the association between the first set of downlink resources (e.g., the first CORESET group) and one or more component carriers based on a CIF value indicated in the RRC message received at 615, one or more CIF values indicated in the DCI message(s) received at 620 and / or 625, or any combination thereof.

[0166] At 635, UE 115-b may determine a second set of downlink resources associated with a second CORESET group. In some aspects, UE 115-b may determine the second set of downlink resources based on receiving an RRC message at 615, receiving a first DCI message at 620, receiving a second DCI message at 625, or any combination thereof. For example, UE 115-b may determine the second set of downlink resources at 635 based on an indication of the second set of downlink resources indicated in the first DCI message received at 620 and / or the second DCI message received at 625.

[0167] In some aspects, the UE 115-b may determine whether a second downlink resource set is associated with one or more component carriers. For example, the UE 115-b may determine that a first downlink resource set associated with a first CORESET group includes a first subset of downlink resources associated with a first component carrier (e.g., within the first component carrier) and a second subset of downlink resources associated with a second component carrier (e.g., within the second component carrier). As another example, the UE 115-b may determine that the second downlink resource set is associated with a single component carrier (e.g., the first component carrier or the second component carrier). In some aspects, the UE 115-b may determine the association between the second downlink resource set (e.g., the first CORESET group) and one or more component carriers based on the CIF value indicated in the RRC message received at 615, one or more CIF values indicated in the DCI messages received at 620 and / or 625, or any combination thereof.

[0168] At 640, the UE 115-b may receive one or more downlink data transmissions from the base station 105-b. The UE 115-b may receive one or more downlink data transmissions based on the RRC message received at 615, the DCI messages received at 620 and 625, determining the first and second downlink resource sets at 630 and 635, monitoring the first and second downlink resource sets at 640, or any combination thereof. In some aspects, the UE 115b may communicate with the base station 105-b (e.g., receive one or more downlink data transmissions) at 645 using a first set of parameters associated with the first CORESET group, a second set of parameters associated with the second CORESET group, or both.

[0169] The downlink data transmissions sent by the base station may be associated with the first CORESET group and / or the second CORESET group and may be received across one or more component carriers. For example, the UE 115-b may receive one or more first downlink data transmissions on a first downlink resource set associated with the first CORESET group, and may receive one or more second downlink data transmissions on a second downlink resource set associated with the second CORESET group.

[0170] For example, a first DCI message received at 620 may indicate that a first CORESET group is associated with both a first component carrier and a second component carrier, and a second DCI message received at 625 may indicate that a second CORESET group is associated with both the first component carrier and the second component carrier. In this example, UE 115-b may receive four separate downlink data transmissions: a first downlink data transmission associated with the first CORESET group on the first component carrier, a second downlink data transmission associated with the first CORESET group on the second component carrier, a third downlink data transmission associated with the second CORESET group on the first component carrier, and a fourth downlink data transmission associated with the second CORESET group on the second component carrier.

[0171] As another example, UE 115-b may receive a single DCI message at 615, where the DCI message indicates that a first CORESET group and a second CORESET group are associated with a first component carrier. In this example, UE 115-b may receive a first downlink data transmission associated with the first CORESET group on the first component carrier and a second downlink data transmission associated with the second CORESET group on the first component carrier. Conversely, in another example, UE 115-b may receive a single DCI message at 615, where the DCI message indicates that the first CORESET group is associated with the first component carrier and the second CORESET group is associated with the second component carrier. In this example, UE 115-b may receive a first downlink data transmission associated with the first CORESET group on the first component carrier and a second downlink data transmission associated with the second CORESET group on the second component carrier.

[0172] At 650, UE 115-b may send one or more uplink transmissions to base station 105-b. UE 115-b may send one or more uplink transmissions based on the RRC message received at 615, the DCI messages received at 620 and 625, determining the first and second downlink resource sets at 630 and 635, monitoring the first and second downlink resource sets at 640, or any combination thereof. In some aspects, UE 115-b may communicate with base station 105-b (e.g., send one or more downlink data transmissions) at 645 using a first set of parameters associated with a first CORESET group, a second set of parameters associated with a second CORESET group, or both. For example, at 650, UE 115-b may send one or more feedback messages (e.g., uplink transmissions) based on a HARQ configuration associated with the first set of parameters of the first CORESET group, a HARQ configuration associated with the second set of parameters of the second CORESET group, or both.

[0173] The techniques described herein may enable scheduling multiple downlink data transmissions associated with a given CORESET group within or across multiple component carriers via one or more DCI messages. Specifically, a DCI message may be configured to schedule multiple downlink data transmissions associated with one or more CORESET groups (e.g., CORESETPoolIndex 0, CORESETPoolIndex 1) within a single component carrier, across multiple component carriers, or both. By utilizing a single DCI message to schedule multiple downlink data transmissions associated with a CORESET group, control signaling overhead within a wireless communication system (e.g., wireless communication system 100 or 200) may be reduced, and flexibility in scheduling downlink data transmissions may be increased.

[0174] Figure 7 Block diagram 700 illustrates a device 705 that supports techniques for multi-component carrier scheduling in accordance with aspects of the present disclosure. Device 705 may be an example of aspects of UE 115 as described herein. Device 705 may include a receiver 710, a communication manager 715, and a transmitter 720. Device 705 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0175] The receiver 710 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to techniques for multi-component carrier scheduling, etc.). The information may be passed to other components of device 705. The receiver 710 may be reference Figure 10Examples of aspects of the described transceiver 1020. The receiver 710 may utilize a single antenna or a set of antennas.

[0176] The communication manager 715 may perform the following operations: receive, on a first component carrier in a set of component carriers and from a base station, one or more DCI messages for scheduling downlink data transmissions at the UE, wherein at least one DCI message schedules two or more downlink data transmissions; determine a first downlink resource set and a second downlink resource set based on the one or more DCI messages, the first downlink resource set being associated with a first CORESET group and the second downlink resource set being associated with a second CORESET group; receive one or more first downlink data transmissions on the first downlink resource set and receive one or more second downlink data transmissions on the second downlink resource set; and communicate using a first set of parameters associated with the first CORESET group and a second set of parameters associated with the second CORESET group based on receiving the one or more first downlink data transmissions and the one or more second downlink data transmissions. The communication manager 715 may be an example of aspects of the communication manager 1010 described herein.

[0177] The actions performed by the communication manager 715 as described herein may be implemented to achieve one or more potential advantages. For example, scheduling multiple downlink data transmissions associated with one or more CORESET groups across one or more component carriers may reduce control signaling within a wireless communication system, thereby reducing network overhead. Additionally, by reducing the number of DCI messages used to schedule downlink data transmissions, the power consumption of the UE 115 may be reduced.

[0178] Based on scheduling multiple downlink data transmissions associated with one or more CORESET groups via a single DCI, a processor of the UE 115 (e.g., a processor that controls the receiver 710, the communication manager 715, the transmitter 720, etc.) may reduce processing resources for downlink communication. For example, by utilizing a single DCI message to schedule multiple downlink data transmissions across component carriers, the UE 115 may reduce the processor ramp-up processing power and the number of times the processing unit is turned on to handle the downlink reception of the DCI message.

[0179] The communication manager 715 or its sub-components may be implemented in hardware, code executed by a processor (e.g., software or firmware), or any combination thereof. If implemented in code executed by a processor, the functions of the communication manager 715 or its sub-components may be performed by a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (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 this disclosure.

[0180] The communication manager 715 or its sub-components may be physically located at various positions, including being distributed such that portions of the functions are implemented by one or more physical components at different physical locations. In some examples, according to various aspects of this disclosure, the communication manager 715 or its sub-components may be separate and distinct components. In some examples, according to various aspects of this disclosure, the communication manager 715 or its sub-components may be combined with one or more other hardware components, including but not limited to input / output (I / O) components, transceivers, network servers, another computing device, one or more other components described in this disclosure, or combinations thereof.

[0181] The transmitter 720 may send signals generated by other components of the device 705. In some examples, the transmitter 720 may be co-located with the receiver 710 in a transceiver module. For example, the transmitter 720 may be an example of aspects of the transceiver 1020 described with reference to Figure 10 The transmitter 720 may utilize a single antenna or a set of antennas.

[0182] Figure 8 Block diagram 800 of a device 805 is shown that supports techniques for multi-component carrier scheduling in accordance with aspects of this disclosure. The device 805 may be an example of aspects of the device 805 or the UE 115 described herein. The device 805 may include a receiver 810, a communication manager 815, and a transmitter 840. The device 805 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0183] The receiver 810 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to techniques for multi-component carrier scheduling, etc.). The information may be passed to other components of the device 805. The receiver 810 may be an example of aspects of the transceiver 1020 described with reference to Figure 10 The receiver 810 may utilize a single antenna or a set of antennas.

[0184] Communication manager 815 may be an example of aspects of communication manager 715 as described herein. Communication manager 815 may include a DCI reception manager 820, a downlink resource manager 825, a downlink reception manager 830, and a communication parameter manager 835. Communication manager 815 may be an example of aspects of communication manager 1010 as described herein.

[0185] The DCI reception manager 820 may receive, on a first component carrier in a set of component carriers and from a base station, one or more DCI messages for scheduling downlink data transmissions at a UE, where at least one DCI message schedules two or more downlink data transmissions.

[0186] The downlink resource manager 825 may determine a first set of downlink resources and a second set of downlink resources based on one or more DCI messages, where the first set of downlink resources is associated with a first CORESET group and the second set of downlink resources is associated with a second CORESET group.

[0187] The downlink reception manager 830 may receive one or more first downlink data transmissions on the first set of downlink resources and one or more second downlink data transmissions on the second set of downlink resources.

[0188] The communication parameter manager 835 may communicate using a first set of parameters associated with the first CORESET group and a second set of parameters associated with the second CORESET group based on receiving one or more first downlink data transmissions and one or more second downlink data transmissions.

[0189] The transmitter 840 may transmit signals generated by other components of device 805. In some examples, the transmitter 840 may be co-located with the receiver 810 in a transceiver module. For example, the transmitter 840 may be an example of aspects of transceiver 1020 as referenced Figure 10 described. The transmitter 840 may utilize a single antenna or a set of antennas.

[0190] Figure 9FIG. 900 is a block diagram of a communication manager 905 that supports techniques for multi-component carrier scheduling in accordance with aspects of the present disclosure. The communication manager 905 may be an example of aspects of the communication manager 715, the communication manager 815, or the communication manager 1010 described herein. The communication manager 905 may include a DCI reception manager 910, a downlink resource manager 915, a downlink reception manager 920, a communication parameter manager 925, an RRC reception manager 930, and a CIF manager 935. Each of these modules may communicate directly or indirectly with each other (e.g., via one or more buses).

[0191] The DCI reception manager 910 may receive, on a first component carrier in a set of component carriers and from a base station, one or more DCI messages for scheduling downlink data transmissions at a UE, where at least one DCI message schedules two or more downlink data transmissions. In some examples, the DCI reception manager 910 may receive a first DCI message in a first CORESET of a first CORESET group from the base station, the first DCI message including an indication of a first downlink resource set. In some examples, the DCI reception manager 910 may receive a second DCI message in a second CORESET of a second CORESET group from the base station, the second DCI message including an indication of a second downlink resource set. In some examples, the DCI reception manager 910 may receive a single DCI message including indications of the first CORESET group and the second CORESET group.

[0192] The downlink resource manager 915 may determine a first downlink resource set and a second downlink resource set based on one or more DCI messages, the first downlink resource set being associated with the first CORESET group and the second downlink resource set being associated with the second CORESET group. In some examples, the downlink resource manager 915 may determine that the first downlink resource set associated with the first CORESET group includes a first subset and a second subset of the first downlink resource set within different component carriers. In some examples, the downlink resource manager 915 may determine that the second downlink resource set associated with the second CORESET group includes a first subset and a second subset of the second downlink resource set within different component carriers.

[0193] The downlink reception manager 920 may receive one or more first downlink data transmissions on a first downlink resource set and one or more second downlink data transmissions on a second downlink resource set. In some examples, the downlink reception manager 920 may receive one or more first downlink data transmissions and one or more second downlink data transmissions on the first component carrier according to the value of the carrier indicator field in a single DCI message.

[0194] In some examples, the downlink reception manager 920 may receive one or more first downlink data transmissions on a first downlink resource set associated with a first CORESET group on a second component carrier different from the first component carrier according to a first mapping pair of the value of the carrier indicator field in a single DCI message, where the first mapping pair includes the second component carrier and the first CORESET group. In some examples, the downlink reception manager 920 may receive one or more second downlink data transmissions on a second downlink resource set associated with a second CORESET group on the second component carrier according to a second mapping pair of the value of the carrier indicator field in a single DCI message, where the second mapping pair includes the second component carrier and the second CORESET group.

[0195] In some examples, the downlink reception manager 920 may receive one or more first downlink data transmissions on a first downlink resource set associated with a first CORESET group on the first component carrier according to a first mapping pair of the value of the carrier indicator field in a single DCI message; where the first mapping pair includes the first component carrier and the first CORESET group. In some examples, the downlink reception manager 920 may receive one or more second downlink data transmissions on a second downlink resource set associated with a second CORESET group on a second component carrier different from the first component carrier according to a second mapping pair of the value of the carrier indicator field in a single DCI message, where the second mapping pair includes the second component carrier and the second CORESET group.

[0196] The communication parameter manager 925 may communicate using a first parameter set associated with the first CORESET group and a second parameter set associated with the second CORESET group based on receiving one or more first downlink data transmissions and one or more second downlink data transmissions. In some cases, the parameter set includes HARQ configuration, PDSCH scrambling sequence, CRS rate matching configuration, TCI state, or any combination thereof.

[0197] The RRC receiver manager 930 may receive, from a base station, a DCI message for indicating a set of carrier indicator field values, where each carrier indicator field value is associated with a mapping pair including a component carrier in a set of component carriers and at least one of a first CORESET group or a second CORESET group, and where receiving one or more first downlink data transmissions and one or more second downlink data transmissions is based on the value of the carrier indicator field in a single DCI message and the set of carrier indicator field values in the DCI message.

[0198] In some examples, the RRC receiver manager 930 may receive, from a base station, a DCI message for indicating a set of carrier indicator field values, where each carrier indicator field value is associated with two mapping pairs of a component carrier and a CORESET group value, each mapping pair including a CORESET group different from the first CORESET group or the second CORESET group, and each mapping pair including a component carrier different from the set of component carriers, and where receiving one or more first downlink data transmissions and one or more second downlink data transmissions is based on the value of the carrier indicator field in a single DCI message and the set of carrier indicator field values in the DCI message.

[0199] The CIF manager 935 may determine a first set of parameters associated with the first CORESET group and a second set of parameters associated with the second CORESET group.

[0200] In some cases, the value of the carrier indicator field in a single DCI message is associated with both the first CORESET group and the second CORESET group.

[0201] Figure 10 FIG. shows a system 1000 including an apparatus 1005 that supports techniques for multi-component carrier scheduling in accordance with aspects of the present disclosure. The apparatus 1005 may be an example of the apparatus 705, the apparatus 805, or the UE 115 described herein or include components of the apparatus 705, the apparatus 805, or the UE 115. The apparatus 1005 may include components for bi-directional voice and data communication including components for sending and receiving communications including a communication manager 1010, an I / O controller 1015, a transceiver 1020, an antenna 1025, a memory 1030, and a processor 1040. These components may communicate electronically via one or more buses (e.g., bus 1045).

[0202] The communication manager 1010 may perform the following operations: receive, on a first component carrier in a set of component carriers and from a base station, one or more DCI messages for scheduling downlink data transmissions at a UE, where at least one DCI message schedules two or more downlink data transmissions; determine a first set of downlink resources and a second set of downlink resources based on the one or more DCI messages, the first set of downlink resources being associated with a first CORESET group and the second set of downlink resources being associated with a second CORESET group; receive one or more first downlink data transmissions on the first set of downlink resources and receive one or more second downlink data transmissions on the second set of downlink resources; and communicate, based on receiving the one or more first downlink data transmissions and the one or more second downlink data transmissions, using a first set of parameters associated with the first CORESET group and a second set of parameters associated with the second CORESET group.

[0203] The I / O controller 1015 may manage input and output signals for the device 1005. The I / O controller 1015 may also manage peripheral devices not integrated into the device 1005. In some cases, the I / O controller 1015 may represent a physical connection or port to an external peripheral device. In some cases, the I / O controller 1015 may utilize an operating system such as or another known operating system. In other cases, the I / O controller 1015 may represent a modem, keyboard, mouse, touch screen, or similar device or interact with the above devices. In some cases, the I / O controller 1015 may be implemented as part of a processor. In some cases, a user may interact with the device 1005 via the I / O controller 1015 or via a hardware component controlled by the I / O controller 1015.

[0204] The transceiver 1020 may communicate bidirectionally via one or more antennas, wired or wireless links as described above. For example, the transceiver 1020 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1020 may also include a modem for modulating packets and providing the modulated packets to an antenna for transmission, and demodulating packets received from the antenna.

[0205] In some cases, the wireless device may include a single antenna 1025. However, in some cases, the device may have more than one antenna 1025, which may be capable of concurrently sending or receiving multiple wireless transmissions.

[0206] The memory 1030 may include a random access memory (RAM) and a read-only memory (ROM). The memory 1030 may store computer-readable and computer-executable code 1035 that includes instructions that, when executed, cause the processor to perform the various functions described herein. In some cases, the memory 1030 may also contain a basic input / output system (BIOS) and the like, which may control basic hardware or software operations, such as interactions with peripheral components or devices.

[0207] The processor 1040 may include intelligent hardware devices (e.g., a general-purpose processor, a DSP, a central processing unit (CPU), a microcontroller, an ASIC, an FPGA, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, the processor 1040 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into the processor 1040. The processor 1040 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 1030) to cause the device 1005 to perform various functions (e.g., functions or tasks that support techniques for multi-component carrier scheduling).

[0208] The code 1035 may include instructions for implementing aspects of the present disclosure, including instructions for supporting wireless communication. The code 1035 may be stored in a non-transitory computer-readable medium (e.g., system memory or other types of memory). In some cases, the code 1035 may not be directly executable by the processor 1040, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein.

[0209] Figure 11 Block diagram 1100 shows a device 1105 that supports techniques for multi-component carrier scheduling in accordance with aspects of the present disclosure. The device 1105 may be an example of aspects of the base station 105 described herein. The device 1105 may include a receiver 1110, a communication manager 1115, and a transmitter 1120. The device 1105 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0210] The receiver 1110 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to techniques for multi-component carrier scheduling, etc.). The information may be passed to other components of the device 1105. The receiver 1110 may be an example of aspects of the transceiver 1420 described with reference to Figure 14 The receiver 1110 may utilize a single antenna or a set of antennas.

[0211] The communication manager 1115 may perform the following operations: determine a first downlink resource set and a second downlink resource set, where the first downlink resource set is associated with a first CORESET group and the second downlink resource set is associated with a second CORESET group, and both the first downlink resource set and the second downlink resource set are associated with one or more component carriers in a set of component carriers used in communication with the UE; send, on a first component carrier in the set of component carriers and to the UE, one or more DCI messages for scheduling downlink data transmission at the UE, where at least one DCI schedules two or more downlink data transmissions; based on the one or more DCI messages, send one or more first downlink data transmissions to the UE on the first downlink resource set and send one or more second downlink data transmissions to the UE on the second downlink resource set; and communicate with the UE using a first set of parameters associated with the first CORESET group and a second set of parameters associated with the second CORESET group. The communication manager 1115 may be an example of aspects of the communication manager 1410 described herein.

[0212] The actions performed by the communication manager 1115 as described herein may be implemented to achieve one or more potential advantages. For example, scheduling multiple downlink data transmissions associated with one or more CORESET groups across one or more component carriers may reduce control signaling within a wireless communication system, thereby reducing network overhead. Additionally, by reducing the number of DCI messages used to schedule downlink data transmissions, the power consumption of the base station 105 may be reduced.

[0213] Based on scheduling multiple downlink data transmissions associated with one or more CORESET groups via a single DCI, a processor of the base station 105 (e.g., processors of the control receiver 1110, communication manager 1115, transmitter 1120, etc.) may reduce processing resources for downlink communication. For example, by using a single DCI message to schedule multiple downlink data transmissions across component carriers, the base station 105 may reduce the number of times the processor ramps up processing power and turns on processing units to handle the transmission of DCI messages.

[0214] The communication manager 1115 or its subcomponents may be implemented in hardware, code executed by a processor (e.g., software or firmware), or any combination thereof. If implemented in code executed by a processor, the functions of the communication manager 1115 or its subcomponents may be performed by a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic, discrete hardware component, or any combination thereof designed to perform the functions described in this disclosure.

[0215] The communication manager 1115 or its sub-components may be physically located at various locations, including being distributed such that some of the functions are implemented by one or more physical components at different physical locations. In some examples, in accordance with various aspects of the present disclosure, the communication manager 1115 or its sub-components may be separate and distinct components. In some examples, in accordance with various aspects of the present disclosure, the communication manager 1115 or its sub-components may be combined with one or more other hardware components (including but not limited to I / O components, transceivers, network servers, another computing device, one or more other components described in the present disclosure, or a combination thereof).

[0216] The transmitter 1120 may send signals generated by other components of the device 1105. In some examples, the transmitter 1120 may be co-located with the receiver 1110 in a transceiver module. For example, the transmitter 1120 may be an example of aspects of the transceiver 1420 described with reference to Figure 14 The transmitter 1120 may utilize a single antenna or a set of antennas.

[0217] Figure 12 FIG. 1200 is a block diagram of a device 1205 supporting techniques for multi-component carrier scheduling in accordance with aspects of the present disclosure. The device 1205 may be an example of aspects of the device 1205 or the base station 105 described herein. The device 1205 may include a receiver 1210, a communication manager 1215, and a transmitter 1240. The device 1205 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0218] The receiver 1210 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to techniques for multi-component carrier scheduling, etc.). The information may be passed to other components of the device 1205. The receiver 1210 may be an example of aspects of the transceiver 1420 described with reference to Figure 14 The receiver 1210 may utilize a single antenna or a set of antennas.

[0219] The communication manager 1215 may be an example of aspects of the communication manager 1115 described herein. The communication manager 1215 may include a downlink resource manager 1220, a DCI transmission manager 1225, a downlink transmission manager 1230, and a communication parameter manager 1235. The communication manager 1215 may be an example of aspects of the communication manager 1410 described herein.

[0220] The downlink resource manager 1220 may determine a first downlink resource set and a second downlink resource set, where the first downlink resource set is associated with a first CORESET group and the second downlink resource set is associated with a second CORESET group, and both the first downlink resource set and the second downlink resource set are associated with one or more component carriers in a set of component carriers used in communication with the UE.

[0221] The DCI transmission manager 1225 may transmit one or more DCI messages for scheduling downlink data transmission at the UE on a first component carrier in the set of component carriers, where at least one DCI schedules two or more downlink data transmissions.

[0222] The downlink transmission manager 1230 may transmit one or more first downlink data transmissions to the UE on the first downlink resource set and one or more second downlink data transmissions to the UE on the second downlink resource set based on one or more DCI messages.

[0223] The communication parameter manager 1235 may communicate with the UE using a first set of parameters associated with the first CORESET group and a second set of parameters associated with the second CORESET group.

[0224] The transmitter 1240 may transmit signals generated by other components of the device 1205. In some examples, the transmitter 1240 may be co-located with the receiver 1210 in a transceiver module. For example, the transmitter 1240 may be an example of aspects of the transceiver 1420 described with reference to Figure 14 The transmitter 1240 may utilize a single antenna or a set of antennas.

[0225] Figure 13 Block diagram 1300 shows a communication manager 1305 that supports techniques for multi-component carrier scheduling in accordance with aspects of the present disclosure. The communication manager 1305 may be an example of aspects of the communication manager 1115, the communication manager 1215, or the communication manager 1410 described herein. The communication manager 1305 may include a downlink resource manager 1310, a DCI transmission manager 1315, a downlink transmission manager 1320, a communication parameter manager 1325, an RRC transmission manager 1330, and a CIF manager 1335. Each of these modules may communicate directly or indirectly with each other (e.g., via one or more buses).

[0226] The downlink resource manager 1310 may determine a first downlink resource set and a second downlink resource set, where the first downlink resource set is associated with a first CORESET group and the second downlink resource set is associated with a second CORESET group, and both the first downlink resource set and the second downlink resource set are associated with one or more component carriers in the set of component carriers used in communication with the UE. In some examples, the downlink resource manager 1310 may determine that the first downlink resource set associated with the first CORESET group includes a first subset and a second subset of the first downlink resource set within different component carriers. In some examples, the downlink resource manager 1310 may determine that the second downlink resource set associated with the second CORESET group includes a first subset and a second subset of the second downlink resource set within different component carriers.

[0227] The DCI transmission manager 1315 may transmit, on a first component carrier in the set of component carriers and to the UE, one or more DCI messages for scheduling downlink data transmissions at the UE, where at least one DCI schedules two or more downlink data transmissions. In some examples, the DCI transmission manager 1315 may transmit a first DCI message to the UE in the first CORESET of the first CORESET group, where the first DCI message includes an indication of the first downlink resource set. In some examples, the DCI transmission manager 1315 may transmit a second DCI message to the UE in the second CORESET of the second CORESET group, where the second DCI message includes an indication of the second downlink resource set. In some examples, the DCI transmission manager 1315 may transmit a single DCI message that includes indications of the first CORESET group and the second CORESET group.

[0228] The downlink transmission manager 1320 may transmit, based on one or more DCI messages, one or more first downlink data transmissions to the UE on the first downlink resource set and one or more second downlink data transmissions to the UE on the second downlink resource set. In some examples, the downlink transmission manager 1320 may transmit one or more first downlink data transmissions and one or more second downlink data transmissions on the first component carrier according to the value of the carrier indicator field in a single DCI message.

[0229] In some examples, the downlink transmission manager 1320 may transmit one or more first downlink data transmissions on a first downlink resource set associated with a first CORESET group on a second component carrier different from the first component carrier according to a first mapping pair of values of the carrier indicator field in a single DCI message, where the first mapping pair includes the second component carrier and the first CORESET group. In some examples, the downlink transmission manager 1320 may transmit one or more second downlink data transmissions on a second downlink resource set associated with a second CORESET group on the second component carrier according to a second mapping pair of values of the carrier indicator field in a single DCI message, where the second mapping pair includes the second component carrier and the second CORESET group.

[0230] In some examples, the downlink transmission manager 1320 may transmit one or more first downlink data transmissions on a first downlink resource set associated with a first CORESET group on the first component carrier according to a first mapping pair of values of the carrier indicator field in a single DCI message; where the first mapping pair includes the first component carrier and the first CORESET group. In some examples, the downlink transmission manager 1320 may transmit one or more second downlink data transmissions on a second downlink resource set associated with a second CORESET group on a second component carrier different from the first component carrier according to a second mapping pair of values of the carrier indicator field in a single DCI message, where the second mapping pair includes the second component carrier and the second CORESET group.

[0231] The communication parameter manager 1325 may communicate with the UE using a first set of parameters associated with the first CORESET group and a second set of parameters associated with the second CORESET group. In some cases, the set of parameters includes HARQ configuration, PDSCH scrambling sequence, CRS rate matching configuration, TCI state, or any combination thereof.

[0232] The RRC transmission manager 1330 may send a DCI message to the UE for indicating a set of values of the carrier indicator field, where each value of the carrier indicator field is associated with a mapping pair that includes a component carrier in the set of component carriers and at least one of the first CORESET group or the second CORESET group, where transmitting one or more first downlink data transmissions and one or more second downlink data transmissions is based on the values of the carrier indicator field in a single DCI message and the set of values of the carrier indicator field in the DCI message.

[0233] In some examples, the RRC transmission manager 1330 may send a DCI message to the UE to indicate a set of carrier indicator field values, where each carrier indicator field value is associated with two mapping pairs of a component carrier and a CORESET group value, each mapping pair includes a CORESET group different from the first CORESET group or the second CORESET group, and each mapping pair includes a component carrier different from the set of component carriers, wherein transmitting one or more first downlink data transmissions and one or more second downlink data transmissions is based on the value of the carrier indicator field in a single DCI message and the set of carrier indicator field values in the DCI message.

[0234] The CIF manager 1335 may determine a first set of parameters associated with the first CORESET group and a second set of parameters associated with the second CORESET group.

[0235] In some cases, the value of the carrier indicator field in a single DCI message is associated with both the first CORESET group and the second CORESET group.

[0236] Figure 14 FIG. shows a system 1400 including a device 1405 that supports techniques for multi-component carrier scheduling in accordance with aspects of the present disclosure. The device 1405 may be an example of the device 1105, the device 1205, or the base station 105 described herein or include components of the device 1105, the device 1205, or the base station 105. The device 1405 may include components for two-way voice and data communication, including components for transmitting and receiving communication, including a communication manager 1410, a network communication manager 1415, a transceiver 1420, an antenna 1425, a memory 1430, a processor 1440, and an inter-station communication manager 1445. These components may communicate electronically via one or more buses (e.g., bus 1450).

[0237] The communication manager 1410 may perform the following operations: determine a first downlink resource set and a second downlink resource set, where the first downlink resource set is associated with a first CORESET group and the second downlink resource set is associated with a second CORESET group, and both the first downlink resource set and the second downlink resource set are associated with one or more component carriers in a set of component carriers used in communication with the UE; transmit, on a first component carrier in the set of component carriers and to the UE, one or more DCI messages for scheduling downlink data transmission at the UE, where at least one DCI schedules two or more downlink data transmissions; based on the one or more DCI messages, transmit one or more first downlink data transmissions to the UE on the first downlink resource set and transmit one or more second downlink data transmissions to the UE on the second downlink resource set; and communicate with the UE using a first parameter set associated with the first CORESET group and a second parameter set associated with the second CORESET group.

[0238] The network communication manager 1415 may manage communication with the core network (e.g., via one or more wired backhaul links). For example, the network communication manager 1415 may manage the transmission of data communication for client devices (e.g., one or more UEs 115).

[0239] The transceiver 1420 may communicate bidirectionally via one or more antennas, wired or wireless links as described above. For example, the transceiver 1420 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1420 may also include a modem for modulating packets and providing the modulated packets to the antenna for transmission, and for demodulating packets received from the antenna.

[0240] In some cases, the wireless device may include a single antenna 1425. However, in some cases, the device may have more than one antenna 1425, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.

[0241] The memory 1430 may include RAM, ROM, or a combination thereof. The memory 1430 may store computer-readable code 1435 that includes instructions that, when executed by a processor (e.g., processor 1440), cause the device 1405 to perform the various functions described herein. In some cases, the memory 1430 may also contain a BIOS, etc., which may control basic hardware or software operations, such as interactions with peripheral components or devices.

[0242] Processor 1440 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 1440 may be configured to operate a memory array using a memory controller. In some cases, the memory controller may be integrated into processor 1440. Processor 1440 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1430) to cause device 1405 to perform various functions (e.g., functions or tasks supporting techniques for multi-component carrier scheduling).

[0243] The inter-station communication manager 1445 may manage communication with other base stations 105 and may include a controller or scheduler for collaboratively controlling communication with UE 115 with other base stations 105. For example, the inter-station communication manager 1445 may coordinate the scheduling of transmissions to UE 115 to implement various interference mitigation techniques such as beamforming or joint transmission. In some examples, the inter-station communication manager 1445 may provide an X2 interface within the LTE / LTE-A wireless communication network technology to provide communication between base stations 105.

[0244] Code 1435 may include instructions for implementing aspects of the present disclosure, including instructions for supporting wireless communication. Code 1435 may be stored in a non-transitory computer-readable medium (e.g., system memory or other types of memory). In some cases, code 1435 may not be directly executable by processor 1440, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein.

[0245] Figure 15 A flowchart illustrating a method 1500 for supporting techniques for multi-component carrier scheduling in accordance with aspects of the present disclosure is shown. Operations of method 1500 may be implemented by UE 115 or its components as described herein. For example, operations of method 1500 may be performed by a communication manager as described with reference to Figures 7 to 10 described. In some examples, the UE may execute an instruction set to control functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the functions described below.

[0246] At 1505, the UE may receive, on a first component carrier in a set of component carriers and from a base station, one or more DCI messages for scheduling downlink data transmissions at the UE, where at least one DCI message schedules two or more downlink data transmissions. The operations at 1505 may be performed according to the methods described herein. In some examples, aspects of the operations at 1505 may be performed by a DCI reception manager as described with reference to Figures 7 to 10 described.

[0247] At 1510, the UE may determine a first downlink resource set and a second downlink resource set based on one or more DCI messages, where the first downlink resource set is associated with a first CORESET group and the second downlink resource set is associated with a second CORESET group. The operations at 1510 may be performed according to the methods described herein. In some examples, aspects of the operations at 1510 may be performed by a downlink resource manager as described with reference to Figures 7 to 10 described.

[0248] At 1515, the UE may receive one or more first downlink data transmissions on the first downlink resource set and one or more second downlink data transmissions on the second downlink resource set. The operations at 1515 may be performed according to the methods described herein. In some examples, aspects of the operations at 1515 may be performed by a downlink reception manager as described with reference to Figures 7 to 10 described.

[0249] At 1520, the UE may communicate using a first set of parameters associated with the first CORESET group and a second set of parameters associated with the second CORESET group based on receiving one or more first downlink data transmissions and one or more second downlink data transmissions. The operations at 1520 may be performed according to the methods described herein. In some examples, aspects of the operations at 1520 may be performed by a communication parameter manager as described with reference to Figures 7 to 10 described.

[0250] Figure 16 FIG. 1600 is a flow diagram illustrating a method 1600 that supports techniques for multi-component carrier scheduling in accordance with aspects of the present disclosure. The operations of method 1600 may be implemented by a UE 115 or components thereof as described herein. For example, the operations of method 1600 may be performed by a communication manager as described with reference to Figures 7 to 10 described. In some examples, the UE may execute an instruction set to control functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use special purpose hardware to perform aspects of the functions described below.

[0251] At 1605, the UE may receive a first DCI message in a first CORESET of a first CORESET set from a base station. The first DCI schedules a downlink data transmission at the UE, and the first DCI message includes an indication of a first set of downlink resources. The operation of 1605 may be performed according to the methods described herein. In some examples, aspects of the operation of 1605 may be performed by a DCI reception manager as described with reference to Figures 7 to 10 described.

[0252] At 1610, the UE may receive a second DCI message in a second CORESET of a second CORESET set from a base station. The second DCI message schedules a downlink data transmission at the UE, and the second DCI message includes an indication of a second set of downlink resources, wherein at least one of the first DCI or the second DCI schedules two or more downlink data transmissions. The operation of 1610 may be performed according to the methods described herein. In some examples, aspects of the operation of 1610 may be performed by a DCI reception manager as described with reference to Figures 7 to 10 described.

[0253] At 1615, the UE may determine a first set of downlink resources and a second set of downlink resources based on the first and second DCI messages, the first set of downlink resources being associated with the first CORESET set and the second set of downlink resources being associated with the second CORESET set. The operation of 1615 may be performed according to the methods described herein. In some examples, aspects of the operation of 1615 may be performed by a downlink resource manager as described with reference to Figures 7 to 10 described.

[0254] At 1620, the UE may receive one or more first downlink data transmissions on the first set of downlink resources and one or more second downlink data transmissions on the second set of downlink resources. The operation of 1620 may be performed according to the methods described herein. In some examples, aspects of the operation of 1620 may be performed by a downlink reception manager as described with reference to Figures 7 to 10 described.

[0255] At 1625, the UE may communicate using a first set of parameters associated with the first CORESET set and a second set of parameters associated with the second CORESET set based on receiving one or more first downlink data transmissions and one or more second downlink data transmissions. The operation of 1625 may be performed according to the methods described herein. In some examples, aspects of the operation of 1625 may be performed by a communication parameter manager as described with reference to Figures 7 to 10 described.

[0256] Figure 17FIG. 1700 is a flow chart illustrating a method 1700 that supports techniques for multi-component carrier scheduling in accordance with aspects of the present disclosure. Operations of method 1700 may be implemented by a UE 115 or components thereof as described herein. For example, operations of method 1700 may be performed by a communication manager as described with reference to Figures 7 to 10 In some examples, the UE may execute an instruction set to control functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the functions described below.

[0257] At 1705, the UE may receive an RRC message from a base station that indicates a set of carrier indicator field values, where each carrier indicator field value is associated with a mapping pair that includes a component carrier in a set of component carriers and at least one of a first CORESET group or a second CORESET group. The operation at 1705 may be performed according to the methods described herein. In some examples, aspects of the operation at 1705 may be performed by an RRC receive manager as described with reference to Figures 7 to 10 described.

[0258] At 1710, the UE may receive, on a first component carrier in the set of component carriers and from the base station, one or more DCI messages for scheduling downlink data transmissions at the UE, where at least one DCI message schedules two or more downlink data transmissions. The operation at 1710 may be performed according to the methods described herein. In some examples, aspects of the operation at 1710 may be performed by a DCI receive manager as described with reference to Figures 7 to 10 described.

[0259] At 1715, the UE may receive, via the first component carrier, a single DCI message from the base station that includes an indication of the first CORESET group and the second CORESET group. The operation at 1715 may be performed according to the methods described herein. In some examples, aspects of the operation at 1715 may be performed by a DCI receive manager as described with reference to Figures 7 to 10 described.

[0260] At 1720, the UE may determine a first downlink resource set and a second downlink resource set based on the one or more DCI messages, where the first downlink resource set is associated with the first CORESET group and the second downlink resource set is associated with the second CORESET group. The operation at 1720 may be performed according to the methods described herein. In some examples, aspects of the operation at 1720 may be performed by a downlink resource manager as described with reference to Figures 7 to 10 described.

[0261] At 1725, the UE may receive one or more first downlink data transmissions on a first downlink resource set and one or more second downlink data transmissions on a second downlink resource set, where receiving the one or more first downlink data transmissions and the one or more second downlink data transmissions is based on the value of the carrier indicator field in a single DCI message and a set of values of the carrier indicator field in the DCI message. The operations at 1725 may be performed according to the methods described herein. In some examples, aspects of the operations at 1725 may be performed by a downlink reception manager as described with reference to Figures 7 to 10 described.

[0262] At 1730, the UE may communicate using a first set of parameters associated with a first CORESET group and a second set of parameters associated with a second CORESET group based on receiving the one or more first downlink data transmissions and the one or more second downlink data transmissions. The operations at 1730 may be performed according to the methods described herein. In some examples, aspects of the operations at 1730 may be performed by a communication parameter manager as described with reference to Figures 7 to 10 described.

[0263] Figure 18 A flowchart illustrating a method 1800 that supports techniques for multi-component carrier scheduling in accordance with aspects of the present disclosure is shown. The operations of method 1800 may be implemented by a UE 115 or components thereof as described herein. For example, the operations of method 1800 may be performed by a communication manager as described with reference to Figures 7 to 10 described. In some examples, the UE may execute an instruction set to control functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the functions described below.

[0264] At 1805, the UE may receive a DCI message from a base station for indicating a set of values of the carrier indicator field, where each value of the carrier indicator field is associated with two mapping pairs of a component carrier and a CORESET group value, each mapping pair includes a CORESET group different from the first CORESET group or the second CORESET group, and each mapping pair includes a component carrier different from the set of component carriers. The operations at 1805 may be performed according to the methods described herein. In some examples, aspects of the operations at 1805 may be performed by an RRC reception manager as described with reference to Figures 7 to 10 described.

[0265] At 1810, the UE may receive, from the base station via a first component carrier, a single DCI message including an indication of a first CORESET set and a second CORESET set. The operations at 1810 may be performed according to the methods described herein. In some examples, aspects of the operations at 1810 may be performed by a DCI reception manager as described with reference to Figures 7 to 10 described.

[0266] At 1815, the UE may determine a first downlink resource set and a second downlink resource set based on one or more DCI messages, where the first downlink resource set is associated with the first CORESET set and the second downlink resource set is associated with the second CORESET set. The operations at 1815 may be performed according to the methods described herein. In some examples, aspects of the operations at 1815 may be performed by a downlink resource manager as described with reference to Figures 7 to 10 described.

[0267] At 1820, the UE may receive one or more first downlink data transmissions on the first downlink resource set and one or more second downlink data transmissions on the second downlink resource set, where receiving the one or more first downlink data transmissions and the one or more second downlink data transmissions is based on the value of a carrier indicator field in the single DCI message and a set of carrier indicator field values in the DCI message. The operations at 1820 may be performed according to the methods described herein. In some examples, aspects of the operations at 1820 may be performed by a downlink reception manager as described with reference to Figures 7 to 10 described.

[0268] At 1825, the UE may communicate using a first set of parameters associated with the first CORESET set and a second set of parameters associated with the second CORESET set based on receiving the one or more first downlink data transmissions and the one or more second downlink data transmissions. The operations at 1825 may be performed according to the methods described herein. In some examples, aspects of the operations at 1825 may be performed by a communication parameter manager as described with reference to Figures 7 to 10 described.

[0269] Figure 19 FIG. 1900 is a flow diagram illustrating a method 1900 that supports techniques for multi-component carrier scheduling in accordance with aspects of the present disclosure. The operations of method 1900 may be implemented by a base station 105 or components thereof as described herein. For example, the operations of method 1900 may be performed by a component as described with reference to Figures 11 to 14The described communication manager performs. In some examples, the base station may execute an instruction set to control the functional elements of the base station to perform the functions described below. Additionally or alternatively, the base station may use dedicated hardware to perform aspects of the functions described below.

[0270] At 1905, the base station may determine a first downlink resource set and a second downlink resource set, where the first downlink resource set is associated with a first CORESET group and the second downlink resource set is associated with a second CORESET group, and both the first downlink resource set and the second downlink resource set are associated with one or more component carriers in a set of component carriers used in communication with the UE. The operation of 1905 may be performed according to the methods described herein. In some examples, aspects of the operation of 1905 may be performed by a downlink resource manager as described with reference to Figures 11 to 14 the description.

[0271] At 1910, the base station may send, on a first component carrier in the set of component carriers and to the UE, one or more DCI messages for scheduling downlink data transmissions at the UE, where at least one DCI schedules two or more downlink data transmissions. The operation of 1910 may be performed according to the methods described herein. In some examples, aspects of the operation of 1910 may be performed by a DCI transmission manager as described with reference to Figures 11 to 14 the description.

[0272] At 1915, the base station may send, based on one or more DCI messages, one or more first downlink data transmissions to the UE on the first downlink resource set and one or more second downlink data transmissions to the UE on the second downlink resource set. The operation of 1915 may be performed according to the methods described herein. In some examples, aspects of the operation of 1915 may be performed by a downlink transmission manager as described with reference to Figures 11 to 14 the description.

[0273] At 1920, the base station may communicate with the UE using a first set of parameters associated with the first CORESET group and a second set of parameters associated with the second CORESET group. The operation of 1920 may be performed according to the methods described herein. In some examples, aspects of the operation of 1920 may be performed by a communication parameter manager as described with reference to Figures 11 to 14 the description.

[0274] It should be noted that the methods described herein describe possible implementations, and the operations and steps may be rearranged or otherwise modified, and other implementations are possible. Additionally, aspects from two or more methods may be combined.

[0275] The following provides a summary of examples of the present disclosure:

[0276] Aspect 1: A method for wireless communication at a UE, comprising: receiving, at a first component carrier among a plurality of component carriers and from a base station, one or more DCI messages for scheduling downlink data transmission at the UE, wherein at least one DCI message schedules two or more downlink data transmissions; determining, at least in part based on the one or more DCI messages, a first downlink resource set and a second downlink resource set, the first downlink resource set being associated with a first CORESET group and the second downlink resource set being associated with a second CORESET group; receiving one or more first downlink data transmissions on the first downlink resource set and receiving one or more second downlink data transmissions on the second downlink resource set; and communicating, at least in part based on receiving the one or more first downlink data transmissions and the one or more second downlink data transmissions, using a first parameter set associated with the first CORESET group and a second parameter set associated with the second CORESET group.

[0277] Aspect 2: The method according to aspect 1, wherein receiving the one or more DCI messages comprises: receiving, from the base station, a first DCI message in a first CORESET of the first CORESET group, the first DCI message including an indication of the first downlink resource set; and receiving, from the base station, a second DCI message in a second CORESET of the second CORESET group, the second DCI message including an indication of the second downlink resource set.

[0278] Aspect 3: The method according to aspect 2, wherein determining the first downlink resource set and the second downlink resource set further comprises: determining that the first downlink resource set associated with the first CORESET group includes a first subset and a second subset of the first downlink resource set within different component carriers; and determining that the second downlink resource set associated with the second CORESET group includes a first subset and a second subset of the second downlink resource set within different component carriers.

[0279] Aspect 4: The method according to any one of aspects 1 to 3, wherein receiving the one or more DCI messages comprises: receiving, from the base station via the first component carrier, a single DCI message, the single DCI message including indications of the first CORESET group and the second CORESET group.

[0280] Aspect 5: The method according to Aspect 4 further includes: receiving, from the base station, an RRC message for indicating a set of carrier indicator field values, where each carrier indicator field value is associated with a mapping pair, and the mapping pair includes a component carrier among the plurality of component carriers and at least one of the first CORESET group or the second CORESET group, where receiving the one or more first downlink data transmissions and the one or more second downlink data transmissions is at least partially based on the value of the carrier indicator field in the single DCI message and the set of carrier indicator field values in the RRC message.

[0281] Aspect 6: The method according to Aspect 5, where the value of the carrier indicator field in the single DCI message is associated with both the first CORESET group and the second CORESET group.

[0282] Aspect 7: The method according to any one of Aspects 5 to 6, where receiving the one or more first downlink data transmissions and the one or more second downlink data transmissions includes: receiving the one or more first downlink data transmissions and the one or more second downlink data transmissions on the first component carrier according to the value of the carrier indicator field in the single DCI message.

[0283] Aspect 8: The method according to any one of Aspects 5 to 8, where receiving the one or more first downlink data transmissions and the one or more second downlink data transmissions includes: receiving the one or more first downlink data transmissions on the first downlink resource set associated with the first CORESET group on a second component carrier different from the first component carrier according to a first mapping pair of the value of the carrier indicator field in the single DCI message, where the first mapping pair includes the second component carrier and the first CORESET group; and receiving the one or more second downlink data transmissions on the second downlink resource set associated with the second CORESET group on the second component carrier according to a second mapping pair of the value of the carrier indicator field in the single DCI message, where the second mapping pair includes the second component carrier and the second CORESET group.

[0284] Aspect 9: The method according to any one of Aspects 4 to 8 further includes: receiving, from the base station, an RRC message for indicating a set of carrier indicator field values, where each carrier indicator field value is associated with two mapping pairs of a component carrier and a CORESET group value, each mapping pair includes a CORESET group different from the first CORESET group or the second CORESET group, and each mapping pair includes a component carrier different from the plurality of component carriers, and wherein receiving the one or more first downlink data transmissions and the one or more second downlink data transmissions is at least partially based on the value of the carrier indicator field in the single DCI message and the set of carrier indicator field values in the RRC message.

[0285] Aspect 10: The method according to Aspect 10, wherein receiving the one or more first downlink data transmissions and the one or more second downlink data transmissions includes: receiving the one or more first downlink data transmissions on the first downlink resource set associated with the first CORESET group on the first component carrier according to the first mapping pair of the value of the carrier indicator field in the single DCI message, where the first mapping pair includes the first component carrier and the first CORESET group; and receiving the one or more second downlink data transmissions on the second downlink resource set associated with the second CORESET group on a second component carrier different from the first component carrier according to the second mapping pair of the value of the carrier indicator field in the single DCI message, where the second mapping pair includes the second component carrier and the second CORESET group.

[0286] Aspect 11: The method according to any one of Aspects 1 to 10, wherein the first parameter set, the second parameter set, or both include: HARQ configuration, PDSCH scrambling sequence, CRS rate matching configuration, TCI state, or any combination thereof.

[0287] Aspect 12: A method for wireless communication at a base station, comprising: determining a first downlink resource set and a second downlink resource set, the first downlink resource set being associated with a first CORESET group and the second downlink resource set being associated with a second CORESET group, both the first downlink resource set and the second downlink resource set being associated with one or more component carriers among a plurality of component carriers used in communication with a UE; transmitting, on a first component carrier among the plurality of component carriers and to the UE, one or more DCI messages for scheduling downlink data transmission at the UE, wherein at least one DCI schedules two or more downlink data transmissions; transmitting, at least in part based on the one or more DCI messages, one or more first downlink data transmissions to the UE on the first downlink resource set and one or more second downlink data transmissions to the UE on the second downlink resource set; and communicating with the UE using a first parameter set associated with the first CORESET group and a second parameter set associated with the second CORESET group.

[0288] Aspect 13: The method according to aspect 12, wherein transmitting the one or more DCI messages comprises: transmitting a first DCI message to the UE in a first CORESET of the first CORESET group, the first DCI message including an indication of the first downlink resource set; and transmitting a second DCI message to the UE in a second CORESET of the second CORESET group, the second DCI message including an indication of the second downlink resource set.

[0289] Aspect 14: The method according to aspect 13, wherein determining the first downlink resource set and the second downlink resource set further comprises: determining that the first downlink resource set associated with the first CORESET group includes a first subset and a second subset of the first downlink resource set within different component carriers; and determining that the second downlink resource set associated with the second CORESET group includes a first subset and a second subset of the second downlink resource set within different component carriers.

[0290] Aspect 15: The method according to any one of aspects 12 to 14, wherein transmitting the one or more DCI messages comprises: transmitting a single DCI message to the UE via the first component carrier, the single DCI message including an indication of the first CORESET group and the second CORESET group.

[0291] Aspect 16: The method according to aspect 15 further includes: sending an RRC message to the UE for indicating a set of carrier indicator field values, where each carrier indicator field value is associated with a mapping pair, and the mapping pair includes a component carrier among the plurality of component carriers and at least one of the first CORESET group or the second CORESET group. Wherein, sending the one or more first downlink data transmissions and the one or more second downlink data transmissions is at least partially based on the value of the carrier indicator field in the single DCI message and the set of carrier indicator field values in the RRC message.

[0292] Aspect 17: The method according to aspect 15, wherein the value of the carrier indicator field in the single DCI message is associated with both the first CORESET group and the second CORESET group.

[0293] Aspect 18: The method according to any one of aspects 16 to 17, wherein sending the one or more first downlink data transmissions and the one or more second downlink data transmissions includes: sending the one or more first downlink data transmissions and the one or more second downlink data transmissions on the first component carrier according to the value of the carrier indicator field in the single DCI message.

[0294] Aspect 19: The method according to any one of aspects 16 to 18, wherein sending the one or more first downlink data transmissions and the one or more second downlink data transmissions includes: sending the one or more first downlink data transmissions on the first downlink resource set associated with the first CORESET group on a second component carrier different from the first component carrier according to a first mapping pair of the value of the carrier indicator field in the single DCI message, where the first mapping pair includes the second component carrier and the first CORESET group; and sending the one or more second downlink data transmissions on the second downlink resource set associated with the second CORESET group on the second component carrier according to a second mapping pair of the value of the carrier indicator field in the single DCI message, where the second mapping pair includes the second component carrier and the second CORESET group.

[0295] Aspect 20: The method according to any one of aspects 15 to 19 further comprises: sending an RRC message to the UE for indicating a set of carrier indicator field values, wherein each carrier indicator field value is associated with two mapping pairs of a component carrier and a CORESET group value, each mapping pair includes a CORESET group different from the first CORESET group or the second CORESET group, and each mapping pair includes a component carrier different from the plurality of component carriers, wherein sending the one or more first downlink data transmissions and the one or more second downlink data transmissions is at least partially based on the value of the carrier indicator field in the single DCI message and the set of carrier indicator field values in the RRC message.

[0296] Aspect 21: The method according to aspect 20, wherein sending the one or more first downlink data transmissions and the one or more second downlink data transmissions comprises: sending the one or more first downlink data transmissions on the first downlink resource set associated with the first CORESET group on the first component carrier according to the first mapping pair of the value of the carrier indicator field in the single DCI message, wherein the first mapping pair includes the first component carrier and the first CORESET group; and sending the one or more second downlink data transmissions on the second downlink resource set associated with the second CORESET group on a second component carrier different from the first component carrier according to the second mapping pair of the value of the carrier indicator field in the single DCI message, wherein the second mapping pair includes the second component carrier and the second CORESET group.

[0297] Aspect 22: The method according to any one of aspects 12 to 21, wherein the first parameter set, the second parameter set, or both include: HARQ configuration, PDSCH scrambling sequence, CRS rate matching configuration, TCI state, or any combination thereof.

[0298] Aspect 23: An apparatus or a non-transitory machine-readable medium configured to perform any one of aspects 1 to 22.

[0299] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for purposes of example and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein are applicable beyond the scope of LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to a variety of other wireless communication systems such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0300] The information and signals described herein can be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the description can be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0301] The various illustrative blocks and components described in connection with the disclosure herein can be implemented or performed with a general-purpose processor, DSP, ASIC, CPU, 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. The general-purpose processor can be a microprocessor, but in the alternative, the processor can be any processor, controller, microcontroller, or state machine. The processor can also be implemented as a combination of computing devices (e.g., 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).

[0302] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions can be stored on or transmitted via a computer-readable medium as one or more instructions or code. Other examples and implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these items. The features implementing the functions can also be physically located at various positions, including being distributed such that portions of the functions are implemented at different physical locations.

[0303] A computer-readable medium includes both a non-transitory computer storage medium and a communication medium, where the communication medium includes any medium that facilitates transfer of a computer program from one place to another. The non-transitory storage medium can be any available medium that can be accessed by a general purpose computer or a special purpose computer. By way of example, and not limitation, the non-transitory computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc read only memory (CD-ROM) or other optical disc storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store the desired program code units in the form of instructions or data structures and that can be accessed by a general purpose or special purpose computer, or a general purpose or special purpose processor. Additionally, any connection is properly termed a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. As used herein, disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc, where disks typically reproduce data magnetically, while discs reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable medium.

[0304] As used herein (including in the claims), the "or" as used in a list of items (e.g., a list that ends with a phrase such as "at least one of" or "one or more of") indicates an inclusive list, such that a list of, for example, 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). Additionally, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0305] In the figures, similar components or features may have the same reference numerals. Additionally, various components of the same type can be distinguished by following the reference numeral with a dash and a second numeral, which is used to differentiate among similar components. If only the first reference numeral is used in the specification, the description applies to any one of the similar components having the same first reference numeral, regardless of the second reference numeral or any other subsequent reference numerals.

[0306] The description of example configurations has been presented in connection with the illustrations described herein and does not represent all of the examples that can be implemented or that are within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration" and not "preferred" or "advantageous over other examples." For the purpose of providing an understanding of the described technology, the detailed description includes specific details. However, the technology may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

[0307] The description herein is provided to enable a person skilled in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein but is accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication at a user equipment (UE), comprising: Receiving, at a first component carrier among a plurality of component carriers, one or more downlink control information messages from a base station for scheduling downlink data transmissions at the UE, wherein at least one of the downlink control information messages schedules two or more downlink data transmissions; Determining a first downlink resource set and a second downlink resource set based on the one or more downlink control information messages, the first downlink resource set being associated with a first control resource set group and the second downlink resource set being associated with a second control resource set group; Receiving one or more first downlink data transmissions on the first downlink resource set and receiving one or more second downlink data transmissions on the second downlink resource set; and Communicating using a first set of parameters associated with the first control resource set group and a second set of parameters associated with the second control resource set group, at least in part based on receiving the one or more first downlink data transmissions and the one or more second downlink data transmissions.

2. The method according to claim 1, wherein Receiving the one or more downlink control information messages comprises: Receiving, from the base station, a first downlink control information message in a first control resource set of the first control resource set group, the first downlink control information message including an indication of the first downlink resource set; and Receiving, from the base station, a second downlink control information message in a second control resource set of the second control resource set group, the second downlink control information message including an indication of the second downlink resource set.

3. The method according to claim 2, wherein Determining the first downlink resource set and the second downlink resource set further comprises: Determining that the first downlink resource set associated with the first control resource set group includes a first subset and a second subset of the first downlink resource set within different component carriers; and Determining that the second downlink resource set associated with the second control resource set group includes a first subset and a second subset of the second downlink resource set within different component carriers.

4. The method according to claim 1, wherein Receiving the one or more downlink control information messages comprises: Receiving, from the base station via the first component carrier, a single downlink control information message, the single downlink control information message including indications of the first control resource set group and the second control resource set group.

5. The method according to claim 4, further comprising: Receive a radio resource control message from the base station for indicating a set of carrier indicator field values, where each carrier indicator field value is associated with a mapping pair, and the mapping pair includes a component carrier among the plurality of component carriers and at least one of the first control resource set group or the second control resource set group. Here, receiving the one or more first downlink data transmissions and the one or more second downlink data transmissions is at least partially based on the value of the carrier indicator field in the single downlink control information message and the set of carrier indicator field values in the radio resource control message.

6. The method according to claim 5, wherein The value of the carrier indicator field in the single downlink control information message is associated with both the first control resource set group and the second control resource set group.

7. The method according to claim 5, wherein, Receiving the one or more first downlink data transmissions and the one or more second downlink data transmissions includes: Receiving the one or more first downlink data transmissions and the one or more second downlink data transmissions on the first component carrier according to the value of the carrier indicator field in the single downlink control information message.

8. The method according to claim 5, wherein, Receiving the one or more first downlink data transmissions and the one or more second downlink data transmissions includes: Receiving the one or more first downlink data transmissions on the first downlink resource set associated with the first control resource set group on a second component carrier different from the first component carrier according to a first mapping pair of the value of the carrier indicator field in the single downlink control information message, where the first mapping pair includes the second component carrier and the first control resource set group; and Receiving the one or more second downlink data transmissions on the second downlink resource set associated with the second control resource set group on the second component carrier according to a second mapping pair of the value of the carrier indicator field in the single downlink control information message, where the second mapping pair includes the second component carrier and the second control resource set group.

9. The method according to claim 4, further comprising: Receiving a radio resource control message from the base station for indicating a set of carrier indicator field values, where each carrier indicator field value is associated with two mapping pairs of a component carrier and a control resource set group value, each mapping pair includes a control resource set group different from the first control resource set group or the second control resource set group, and each mapping pair includes a component carrier different from the plurality of component carriers. Here, receiving the one or more first downlink data transmissions and the one or more second downlink data transmissions is at least partially based on the value of the carrier indicator field in the single downlink control information message and the set of carrier indicator field values in the radio resource control message.

10. The method according to claim 9, wherein, Receiving the one or more first downlink data transmissions and the one or more second downlink data transmissions includes: Receiving, on the first component carrier, on the first downlink resource set associated with the first control resource set group, the one or more first downlink data transmissions according to a first mapping pair of values of the carrier indicator field in the single downlink control information message, wherein the first mapping pair includes the first component carrier and the first control resource set group; and Receiving, on a second component carrier different from the first component carrier, on the second downlink resource set associated with the second control resource set group, the one or more second downlink data transmissions according to a second mapping pair of values of the carrier indicator field in the single downlink control information message, wherein the second mapping pair includes the second component carrier and the second control resource set group.

11. The method according to claim 1, wherein, The first parameter set, the second parameter set, or both include: hybrid automatic repeat request configuration, physical downlink shared channel scrambling sequence, cell-specific reference signal rate matching configuration, transmission configuration indicator status, or any combination thereof.

12. A method for wireless communication at a base station, comprising: Determining a first downlink resource set and a second downlink resource set, the first downlink resource set being associated with a first control resource set group and the second downlink resource set being associated with a second control resource set group, both the first downlink resource set and the second downlink resource set being associated with one or more component carriers among a plurality of component carriers used in communication with a user equipment (UE); Sending, on a first component carrier among the plurality of component carriers, to the UE one or more downlink control information messages for scheduling downlink data transmissions at the UE, wherein at least one downlink control information schedules two or more downlink data transmissions; Sending, at least partially based on the one or more downlink control information messages, one or more first downlink data transmissions to the UE on the first downlink resource set and one or more second downlink data transmissions to the UE on the second downlink resource set; and Communicating with the UE using a first parameter set associated with the first control resource set group and a second parameter set associated with the second control resource set group.

13. The method according to claim 12, wherein, Sending the one or more downlink control information messages includes: Sending a first downlink control information message to the UE in a first control resource set of the first control resource set group, the first downlink control information message including an indication of the first downlink resource set; and Sending a second downlink control information message to the UE in a second control resource set of the second control resource set group, the second downlink control information message including an indication of the second downlink resource set.

14. The method according to claim 13, wherein, Determining the first downlink resource set and the second downlink resource set further includes: Determining the first downlink resource set associated with the first control resource set group includes a first subset and a second subset of the first downlink resource set within different component carriers; and Determining the second downlink resource set associated with the second control resource set group includes a first subset and a second subset of the second downlink resource set within different component carriers.

15. The method according to claim 12, wherein Transmitting the one or more downlink control information messages includes: Transmitting a single downlink control information message to the UE via the first component carrier, the single downlink control information message including an indication of the first control resource set group and the second control resource set group.

16. The method according to claim 15, further comprising: Transmitting a radio resource control message to the UE for indicating a set of carrier indicator field values, wherein each carrier indicator field value is associated with a mapping pair, the mapping pair including a component carrier among the plurality of component carriers and at least one of the first control resource set group or the second control resource set group, wherein transmitting the one or more first downlink data transmissions and the one or more second downlink data transmissions is at least partially based on the value of the carrier indicator field in the single downlink control information message and the set of carrier indicator field values in the radio resource control message.

17. The method according to claim 16, wherein The value of the carrier indicator field in the single downlink control information message is associated with both the first control resource set group and the second control resource set group.

18. The method according to claim 16, wherein, Transmitting the one or more first downlink data transmissions and the one or more second downlink data transmissions includes: Transmitting the one or more first downlink data transmissions and the one or more second downlink data transmissions on the first component carrier according to the value of the carrier indicator field in the single downlink control information message.

19. The method according to claim 16, wherein, Transmitting the one or more first downlink data transmissions and the one or more second downlink data transmissions includes: Transmitting the one or more first downlink data transmissions on the first downlink resource set associated with the first control resource set group on a second component carrier different from the first component carrier according to a first mapping pair of the value of the carrier indicator field in the single downlink control information message, wherein the first mapping pair includes the second component carrier and the first control resource set group; and Transmitting the one or more second downlink data transmissions on the second downlink resource set associated with the second control resource set group on the second component carrier according to a second mapping pair of the value of the carrier indicator field in the single downlink control information message, wherein the second mapping pair includes the second component carrier and the second control resource set group.

20. The method according to claim 15, further comprising: Send a radio resource control message to the UE for indicating a set of carrier indicator field values, where each carrier indicator field value is associated with two mapping pairs of a component carrier and a control resource set group value, each mapping pair includes a control resource set group different from the first control resource set group or the second control resource set group, and each mapping pair includes a component carrier different from the plurality of component carriers, wherein sending the one or more first downlink data transmissions and the one or more second downlink data transmissions is at least partially based on the value of the carrier indicator field in the single downlink control information message and the set of carrier indicator field values in the radio resource control message.

21. The method according to claim 20, wherein Sending the one or more first downlink data transmissions and the one or more second downlink data transmissions includes: Sending the one or more first downlink data transmissions on the first downlink resource set associated with the first control resource set group on the first component carrier according to the first mapping pair of the value of the carrier indicator field in the single downlink control information message, wherein the first mapping pair includes the first component carrier and the first control resource set group; and Sending the one or more second downlink data transmissions on the second downlink resource set associated with the second control resource set group on a second component carrier different from the first component carrier according to the second mapping pair of the value of the carrier indicator field in the single downlink control information message, wherein the second mapping pair includes the second component carrier and the second control resource set group.

22. The method according to claim 12, wherein The first parameter set, the second parameter set, or both include: hybrid automatic repeat request configuration, physical downlink shared channel scrambling sequence, cell-specific reference signal rate matching configuration, transmission configuration indicator status, or any combination thereof.

23. An apparatus for wireless communication, comprising: a processor, a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the following operations: Receiving, on a first component carrier among a plurality of component carriers, one or more downlink control information messages for scheduling downlink data transmissions at a user equipment (UE), wherein at least one downlink control information message schedules two or more downlink data transmissions; Determining a first downlink resource set and a second downlink resource set based on the one or more downlink control information messages, the first downlink resource set being associated with a first control resource set group and the second downlink resource set being associated with a second control resource set group; Receiving the one or more first downlink data transmissions on the first downlink resource set and receiving the one or more second downlink data transmissions on the second downlink resource set; and Communicate using a first set of parameters associated with the first control resource set group and a second set of parameters associated with the second control resource set group, at least in part based on receiving the one or more first downlink data transmissions and the one or more second downlink data transmissions.

24. The apparatus according to claim 23, wherein, The instructions for receiving the one or more downlink control information messages may be executed by the processor to cause the device to: Receive, from the base station, a first downlink control information message in a first control resource set of the first control resource set group, the first downlink control information message including an indication of the first set of downlink resources; and Receive, from the base station, a second downlink control information message in a second control resource set of the second control resource set group, the second downlink control information message including an indication of the second set of downlink resources.

25. The apparatus according to claim 24, wherein The instructions for determining the first set of downlink resources and the second set of downlink resources may further be executed by the processor to cause the device to: Determine that the first set of downlink resources associated with the first control resource set group includes a first subset and a second subset of the first set of downlink resources within different component carriers; And Determine that the second set of downlink resources associated with the second control resource set group includes a first subset and a second subset of the second set of downlink resources within different component carriers.

26. The apparatus according to claim 23, wherein, The instructions for receiving the one or more downlink control information messages may be executed by the processor to cause the device to: Receive, from the base station via the first component carrier, a single downlink control information message, the single downlink control information message including an indication of the first control resource set group and the second control resource set group.

27. A device for wireless communication, comprising: A processor, A memory coupled to the processor; And Instructions stored in the memory and executable by the processor to cause the device to: Determine a first set of downlink resources and a second set of downlink resources, the first set of downlink resources being associated with a first control resource set group and the second set of downlink resources being associated with a second control resource set group, both the first set of downlink resources and the second set of downlink resources being associated with one or more of a plurality of component carriers used in communication with a user equipment (UE); Transmit, on a first component carrier of the plurality of component carriers, to the UE one or more downlink control information messages for scheduling downlink data transmissions at the UE, wherein at least one downlink control information schedules two or more downlink data transmissions; Transmit one or more first downlink data transmissions to the UE on the first downlink resource set and one or more second downlink data transmissions to the UE on the second downlink resource set, at least in part based on the one or more downlink control information messages; and Communicate with the UE using a first set of parameters associated with the first control resource set group and a second set of parameters associated with the second control resource set group.

28. The device according to claim 27, wherein The instructions for transmitting the one or more downlink control information messages are executable by the processor to cause the apparatus to perform the following operations: Transmit a first downlink control information message to the UE in a first control resource set of the first control resource set group, the first downlink control information message including an indication of the first downlink resource set; and Transmit a second downlink control information message to the UE in a second control resource set of the second control resource set group, the second downlink control information message including an indication of the second downlink resource set.

29. The apparatus according to claim 28, wherein, The instructions for determining the first downlink resource set and the second downlink resource set are further executable by the processor to cause the apparatus to perform the following operations: Determine that the first downlink resource set associated with the first control resource set group includes a first subset and a second subset of the first downlink resource set within different component carriers; And Determine that the second downlink resource set associated with the second control resource set group includes a first subset and a second subset of the second downlink resource set within different component carriers.

30. The apparatus according to claim 27, wherein, The instructions for transmitting the one or more downlink control information messages are executable by the processor to cause the apparatus to perform the following operations: Transmit a single downlink control information message to the UE via the first component carrier, the single downlink control information message including an indication of the first control resource set group and the second control resource set group.

Images