Downlink control information for scheduling multiple component carriers

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may communicate with a base station over a set of component carriers according to a carrier aggregation configuration. In some cases, a UE may receive an indication of one or more groups of units, where each group may include one or more component carriers and / or one or more time intervals for each component carrier. In one embodiment, a UE may receive downlink control information (DCI) including one or more fields common to a group of units, which may schedule a data transmission set over one or more group of units, such that a single DCI may schedule multiple component carriers (e.g., two or more) over one or more time intervals. The UE may transmit or receive a set of data transmissions (e.g., uplink or downlink data transmissions) over the scheduled unit based on receiving the DCI.

Description

[0001] This application is a divisional application of the patent application for invention with application number 202180040871.4 and invention title "Downlink Control Information for Scheduling Multiple Component Carriers", which was filed on May 28, 2021.

[0002] Cross-reference to Related Applications

[0003] This patent application claims the benefit of U.S. Provisional Patent Application No. 63 / 043,715, titled "DOWNLINK CONTROL INFORMATION FOR SCHEDULING MULTIPLE COMPONENT CARRIERS", filed on Jun. 24, 2020, by TAKEDA et al., and U.S. Patent Application No. 17 / 192,719, titled "DOWNLINK CONTROL INFORMATION FOR SCHEDULING MULTIPLE COMPONENT CARRIERS", filed on Mar. 4, 2021, by TAKEDA et al.; each of these patent applications is assigned to the assignee hereof. Technical Field

[0004] The following generally relates to wireless communication and, more specifically, to downlink control information (DCI) for scheduling multiple component carriers. Background Art

[0005] Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcasting, and the like. These systems are capable of supporting communication with multiple users by sharing available system resources such as time, frequency, and power. Examples of such multi-access systems include fourth-generation (4G) systems such as Long-Term Evolution (LTE) systems, Advanced LTE (LTE-A) systems, or LTE-A Pro systems, and fifth-generation (5G) systems that 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 multiple access (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).

[0006] In some wireless communication systems, a UE may support carrier aggregation (CA), where the UE communicates with multiple cells simultaneously. For example, the UE may communicate with a first base station (e.g., a primary cell (PCell), a first component carrier) and a second base station (e.g., a secondary cell (SCell), a second component carrier) simultaneously. Additionally or alternatively, a single base station may include multiple cells (e.g., a PCell and an SCell, or multiple component carriers), where the UE communicates with two or more cells on a single base station simultaneously. To implement carrier aggregation communication, effective techniques are needed. Summary of the Invention

[0007] The techniques described herein relate to improved methods, systems, devices, and apparatuses for supporting downlink control information (DCI) for scheduling multiple component carriers. Generally, the techniques described herein provide improvements to the multi-component carrier scheduling process. A base station may send a DCI message to a user equipment (UE) that schedules data transmissions on multiple units (e.g., multiple component carriers or multiple time intervals such as time slots, transmission time intervals (TTIs), or combinations thereof). In some cases, the UE and the base station may be configured to support scheduled unit grouping, where a single DCI may schedule one or more unit groups. For example, the UE may communicate with the base station through a component carrier set according to a carrier aggregation configuration. In some cases, the UE may receive a configuration message indicating one or more unit groups, where each group may include one or more component carriers and / or one or more time slots of each component carrier. The UE may receive DCI from the base station based on being connected to the base station, the DCI including one or more fields (e.g., DCI fields) common to the unit group, where the group may include multiple (e.g., two or more) component carriers from the component carrier set. In some cases, the DCI may schedule a set of data transmissions through one or more unit groups, where the data transmissions may be downlink data transmissions sent from the base station or uplink data transmissions sent from the UE. Subsequently, the UE may send or receive a set of data transmissions through the scheduled units based on the received DCI.

[0008] A method of wireless communication is described. The method may include: communicating with a base station through a component carrier set according to a carrier aggregation configuration; receiving DCI from the base station based on being connected to the base station, the DCI including one or more fields common to two or more component carriers from the component carrier set, the DCI scheduling a set of data transmissions through the two or more component carriers; and sending or receiving a set of data transmissions through the two or more scheduled component carriers based on the received DCI.

[0009] Describes an apparatus for wireless communication. The apparatus may include at least one processor, a memory coupled to the at least one processor (e.g., operatively, communicatively, functionally, electronically, or electrically), and instructions stored in the memory. The instructions may be executable by the at least one processor to cause the apparatus to: communicate with a base station via a set of component carriers according to a carrier aggregation configuration; receive DCI from the base station based on being connected to the base station, the DCI including one or more fields common to two or more component carriers from the set of component carriers, the DCI scheduling a data transmission set via the two or more component carriers; and transmit or receive the data transmission set via the two or more scheduled component carriers based on receiving the DCI.

[0010] Describes another apparatus for wireless communication. The apparatus may include components for: communicating with a base station via a set of component carriers according to a carrier aggregation configuration; receiving DCI from the base station based on being connected to the base station, the DCI including one or more fields common to two or more component carriers from the set of component carriers, the DCI scheduling a data transmission set via the two or more component carriers; and transmitting or receiving the data transmission set via the two or more scheduled component carriers based on receiving the DCI.

[0011] Describes a non-transitory computer-readable medium storing code for wireless communication. The code may include instructions executable by at least one processor to: communicate with a base station via a set of component carriers according to a carrier aggregation configuration; receive DCI from the base station based on being connected to the base station, the DCI including one or more fields common to two or more component carriers from the set of component carriers, the DCI scheduling a data transmission set via the two or more component carriers; and transmit or receive the data transmission set via the two or more scheduled component carriers based on receiving the DCI.

[0012] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for receiving from a base station a configuration message indicating a component carrier group including at least two or more component carriers, wherein receiving the DCI scheduling the data transmission set may be based on receiving the configuration message indicating the two or more component carriers.

[0013] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, receiving the DCI may include operations, features, components, or instructions for receiving an indication of a subset of component carriers from a component carrier group, the subset of component carriers including two or more component carriers, wherein transmitting or receiving the data transmission set via the two or more component carriers may be based on receiving the indication of the subset of component carriers.

[0014] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, receiving an indication of a subset of component carriers may include operations, features, components, or instructions for receiving a bitmap indicating two or more component carriers from a component carrier group.

[0015] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, receiving an indication of a subset of component carriers may include operations, features, components, or instructions for receiving an indication of a first component carrier from a component carrier group within the subset of component carriers, and receiving an indication of a number of consecutive component carriers from the component carrier group within the subset of component carriers.

[0016] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the indication of the subset of component carriers may be based on an order of resources associated with the component carrier group, and the order may be a frequency-first order or a time-first order.

[0017] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, a component carrier group may be two or more component carriers.

[0018] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for receiving a configuration message indicating a parameter set for each of two or more component carriers, wherein the parameter set for each of the two or more component carriers may be the same, and wherein receiving DCI may be based on receiving the configuration message.

[0019] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for receiving a configuration message indicating a first parameter set for a first component carrier of two or more component carriers, and identifying a parameter set for the remaining component carriers of the two or more component carriers based on the first parameter set, wherein the first parameter set for the first component carrier and the parameter set for the remaining component carriers may be the same, and wherein receiving DCI may be based on receiving the configuration message.

[0020] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for attempting to decode a downlink transmission set of a data transmission set, and sending acknowledgement information associated with the downlink transmission set to a base station, wherein the acknowledgement information includes a single bit associated with two or more component carriers, a set of bits each associated with one of the two or more component carriers, or a set of bits each associated with a TTI of one of the two or more component carriers.

[0021] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, DCI schedules a data transmission set for a TTI set via two or more component carriers.

[0022] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for identifying, during a first TTI of a TTI set, a first identifier of a first hybrid automatic repeat request (HARQ) associated with a data transmission set based on receiving DCI, and incrementing the first identifier to generate a second identifier of a second HARQ associated with the data transmission set during a second TTI of the TTI set.

[0023] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for identifying, during a first TTI of a TTI set, a first timing parameter for transmitting a first HARQ associated with a data transmission set based on receiving DCI, and incrementing the first timing parameter to generate a second timing parameter for transmitting a second HARQ associated with the data transmission set during a second TTI of the TTI set.

[0024] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the two or more component carriers may be a first component carrier set, one or more fields that may be common to the first component carrier set may be a first one or more field sets, a data transmission set via the first component carrier set may be a first data transmission set, DCI includes a second one or more field sets that may be common to a second two or more component carrier sets, and DCI schedules a second data transmission set via the second two or more component carrier sets.

[0025] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for transmitting or receiving a second data transmission set via a second two or more component carrier sets based on receiving DCI, the DCI including a second one or more field sets that may be common to the second two or more component carrier sets.

[0026] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first one or more field sets and the second one or more field sets share a field indicating a first parameter for a first data transmission set via the first component carrier set and a second parameter for a second data transmission set via the second two or more component carrier sets, where the first parameter may be different from the second parameter.

[0027] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving, from a base station, a configuration message indicating a mapping from a common field to a first parameter and a second parameter.

[0028] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first parameter and the second parameter may be frequency domain resource allocation (FDRA) parameters, time domain resource allocation (TDRA) parameters, or both.

[0029] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, a first component carrier among two or more component carriers may have a first subcarrier spacing, and a second component carrier among the two or more component carriers may have a second subcarrier spacing different from the first subcarrier spacing.

[0030] A method of wireless communication is described. The method may include: communicating with a UE via a set of component carriers according to a carrier aggregation configuration; transmitting, based on a connection with the UE, DCI to the UE, the DCI including one or more fields common to two or more component carriers from the set of component carriers, the DCI scheduling a data transmission set via the two or more component carriers; and transmitting or receiving, based on the transmitted DCI, the data transmission set via the two or more scheduled component carriers.

[0031] An apparatus for wireless communication is described. The apparatus may include at least one processor, a memory coupled to the at least one processor (e.g., operatively, communicatively, functionally, electronically, or electrically), and instructions stored in the memory. The instructions may be executable by the at least one processor to cause the apparatus to: communicate with a UE via a set of component carriers according to a carrier aggregation configuration; transmit, based on a connection with the UE, DCI to the UE, the DCI including one or more fields common to two or more component carriers from the set of component carriers, the DCI scheduling a data transmission set via the two or more component carriers; and transmit or receive, based on the transmitted DCI, the data transmission set via the two or more scheduled component carriers.

[0032] Another apparatus for wireless communication is described. The apparatus may include components for: communicating with a UE via a set of component carriers according to a carrier aggregation configuration; transmitting, based on a connection with the UE, DCI to the UE, the DCI including one or more fields common to two or more component carriers from the set of component carriers, the DCI scheduling a data transmission set via the two or more component carriers; and transmitting or receiving, based on the transmitted DCI, the data transmission set via the two or more scheduled component carriers.

[0033] A non - transitory computer - readable medium storing code for wireless communication is described. The code can include instructions executable by at least one processor to: communicate with a UE via a set of component carriers according to a carrier aggregation configuration; send DCI to the UE based on a connection with the UE, the DCI including one or more fields common to two or more component carriers from the set of component carriers, the DCI scheduling a data transmission set via the two or more component carriers; and send or receive a data transmission set via the two or more scheduled component carriers based on sending the DCI.

[0034] Some examples of the methods, apparatuses, and non - transitory computer - readable media described herein may also include operations, features, components, or instructions for sending a configuration message to a UE indicating a configuration of a component - carrier group including at least two or more component carriers, wherein sending the DCI for scheduling the data transmission set may be based on sending the configuration message indicating two or more component carriers.

[0035] In some examples of the methods, apparatuses, and non - transitory computer - readable media described herein, sending the DCI may include operations, features, components, or instructions for sending an indication of a subset of component carriers from a component - carrier group, the subset of component carriers including two or more component carriers, wherein sending or receiving a data transmission set via the two or more component carriers may be based on sending the indication of the subset of component carriers.

[0036] In some examples of the methods, apparatuses, and non - transitory computer - readable media described herein, sending the indication of the subset of component carriers may include operations, features, components, or instructions for sending a bitmap indicating two or more component carriers from a component - carrier group.

[0037] In some examples of the methods, apparatuses, and non - transitory computer - readable media described herein, sending the indication of the subset of component carriers may include operations, features, components, or instructions for sending an indication of a first component carrier from a component - carrier group within the subset of component carriers, and an indication of the number of consecutive component carriers from the component - carrier group within the subset of component carriers.

[0038] In some examples of the methods, apparatuses, and non - transitory computer - readable media described herein, the indication of the subset of component carriers may be based on an order of resources associated with the component - carrier group, and the order may be a frequency - first order or a time - first order.

[0039] In some examples of the methods, apparatuses, and non - transitory computer - readable media described herein, the component - carrier group may be two or more component carriers.

[0040] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a configuration message indicating a parameter set for each of two or more component carriers, where the parameter set for each of the two or more component carriers may be the same, and where sending the DCI may be based on sending the configuration message.

[0041] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending a configuration message indicating a first parameter set for a first component carrier among two or more component carriers, where the first parameter set for the first component carrier among the two or more component carriers and the parameter sets for the remaining component carriers may be the same, and where sending the DCI may be based on sending the configuration message.

[0042] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving, from a UE, acknowledgement information associated with a downlink transmission set from a data transmission set, where the acknowledgement information includes a single bit associated with two or more component carriers, a set of bits each associated with one of the two or more component carriers, or a set of bits each associated with a TTI of one of the two or more component carriers.

[0043] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the DCI schedules a data transmission set over two or more component carriers for a set of TTIs.

[0044] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the two or more component carriers may be a first set of component carriers, one or more fields that may be common to the first set of component carriers may be a first set of one or more fields, a data transmission set over the first set of component carriers may be a first data transmission set, the DCI includes a second set of one or more fields that may be common to a second set of two or more component carriers, and the DCI schedules a second data transmission set over the second set of two or more component carriers.

[0045] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for sending or receiving, over a second set of two or more component carriers, a second data transmission set based on sending the DCI, the DCI including a second set of one or more fields that may be common to the second set of two or more component carriers.

[0046] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, a first set of one or more fields and a second set of one or more fields share a field indicating a first parameter for a first data transmission set over a first component carrier set and a second parameter for a second data transmission set over a second set of two or more component carriers, and the first parameter may be different from the second parameter.

[0047] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, components, or instructions for sending a configuration message to a UE indicating a mapping from the shared field to the first and second parameters.

[0048] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first parameter and the second parameter may be FDRA parameters, TDRA parameters, or both.

[0049] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, a first component carrier among two or more component carriers may have a first subcarrier spacing, and a second component carrier among the two or more component carriers may have a second subcarrier spacing different from the first subcarrier spacing. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] Figure 1 Illustrates examples of systems for wireless communication that support downlink control information (DCI) for scheduling multiple component carriers in accordance with aspects of the present disclosure.

[0051] Figure 2 Illustrates examples of systems for wireless communication that support DCI for scheduling multiple component carriers in accordance with aspects of the present disclosure.

[0052] Figure 3 AND Figure 4 Illustrates examples of component carrier scheduling configurations for DCI that support scheduling multiple component carriers in accordance with aspects of the present disclosure.

[0053] Figure 5A AND Figure 5B Illustrates examples of bitmap indications for DCI that support scheduling multiple component carriers in accordance with aspects of the present disclosure.

[0054] Figure 6A AND Figure 6B Illustrates examples of resource indication value (RIV) configurations for DCI that support scheduling multiple component carriers in accordance with aspects of the present disclosure.

[0055] Figure 7 Illustrates examples of DCI formats for DCI that support scheduling multiple component carriers in accordance with aspects of the present disclosure.

[0056] Figure 8 Illustrates an example of a data retransmission process that supports DCI for scheduling multiple component carriers according to aspects of the present disclosure.

[0057] Figure 9 Illustrates an example of a processing flow that supports DCI for scheduling multiple component carriers according to aspects of the present disclosure.

[0058] Figure 10 and Figure 11 Shows a block diagram of a device that supports DCI for scheduling multiple component carriers according to aspects of the present disclosure.

[0059] Figure 12 Shows a block diagram of a communication manager that supports DCI for scheduling multiple component carriers according to aspects of the present disclosure.

[0060] Figure 13 Shows a diagram of a system that includes a device that supports DCI for scheduling multiple component carriers according to aspects of the present disclosure.

[0061] Figure 14 and Figure 15 Shows a block diagram of a device that supports DCI for scheduling multiple component carriers according to aspects of the present disclosure.

[0062] Figure 16 Shows a block diagram of a communication manager that supports DCI for scheduling multiple component carriers according to aspects of the present disclosure.

[0063] Figure 17 Shows a diagram of a system that includes a device that supports DCI for scheduling multiple component carriers according to aspects of the present disclosure.

[0064] Figures 18 to 21 Shows a flowchart that illustrates a method that supports DCI for scheduling multiple component carriers according to aspects of the present disclosure. Detailed Description

[0065] Some wireless communication systems may support communication between a user equipment (UE) and a base station on multiple aggregated component carriers, a feature known as carrier aggregation. For example, a UE may establish a connection with a base station via at least a first component carrier and a second component carrier. In some wireless communication systems, the first component carrier may refer to a component carrier corresponding to a dynamic spectrum sharing (DSS) primary cell (PCell), while the second component carrier may refer to a non-DSS secondary cell (SCell). In some other cases, both the first component carrier and the second component carrier may support DSS, or both component carriers may not support DSS.

[0066] In a traditional system, a UE can be configured to monitor physical downlink control channel (PDCCH) messages on a DSS PCell, and monitor downlink control information (DCI) sent from a base station that schedules data transmission, such as physical uplink shared channel (PUSCH) transmission or physical downlink shared channel transmission (PDSCH) on one of the component carriers. To schedule data transmission on multiple component carriers (e.g., multi-component carrier scheduling, joint component carrier scheduling, cross-carrier scheduling), the UE can monitor and receive multiple DCIs. However, sending or receiving multiple DCIs by the base station or the UE may increase the signaling overhead of using a large amount of resources to indicate different transmission parameters for each component carrier. In addition, the PCell can serve a low frequency band (e.g., 2 GHz), while the SCell can serve medium to high frequency bands (e.g., 3.5 to 4.7 GHz). Therefore, the PCell can be used by a large number of devices (e.g., NR UEs and LTE UEs), and some devices (e.g., NR UEs) may not be able to achieve peak throughput. In some cases, the combination of throughput reduction and multiple DCIs required for multi-component carrier scheduling may reduce the reliability of the network.

[0067] To improve reliability and enhance spectral efficiency, a single DCI can be configured to schedule data transmission (e.g., downlink data transmission or uplink data transmission) on multiple component carriers (e.g., two or more), such as a PCell and an SCell or some other component carriers. The DCI can be sent on a non-DSS SCell, where the DCI can schedule data transmission on one or more SCell, one or more PCell, or a combination thereof. In some cases, a single DCI can be configured to schedule multiple component carriers and multiple time intervals (e.g., time slots, sub-slots, mini-slots, TTIs) per component carrier. To reduce the resources for sending or receiving the DCI that schedules data transmission on multiple component carriers and / or time intervals, devices in a communication system can be configured to support scheduled unit grouping. As part of the scheduled unit grouping, units such as component carriers or time intervals can be configured by a base station as part of a group, for example. In some cases, the units can be grouped according to frequency resources or time resources or a combination thereof. Each unit within a group can be configured with the same or similar parameters (e.g., radio resource control (RRC) parameters, hybrid automatic repeat request (HARQ) process ID, time domain parameters), such that a single DCI can schedule the unit group instead of each individual unit, to reduce the resources for DCI transmission. In some implementations, not all units in a group can be scheduled by each DCI transmission. For example, the DCI can schedule a subset of the units within a group and may not schedule the remaining units of the group. To indicate which units in a group are scheduled by the DCI, the DCI format can be configured to include a bitmap or a resource indication value (RIV).

[0068] Certain aspects of the subject matter described herein can be implemented to realize one or more advantages. The described techniques can support improvements in multi-component carrier scheduling with advantages such as reducing signaling overhead, improving reliability, and enhancing spectral efficiency. Thus, the techniques supported can include improved network operation and, in some examples, other benefits such as improving network efficiency.

[0069] Aspects of the present disclosure are initially described in the context of a wireless communication system. The aspects are described in conjunction with component carrier scheduling configuration, bitmap indication, RIV configuration, DCI format, data retransmission procedures, and processing flows. Aspects of the present disclosure are further illustrated and described by reference to apparatus diagrams, system diagrams, and flowcharts for a DCI used to schedule multiple component carriers.

[0070] Figure 1FIG. illustrates an example of a wireless communication system 100 that supports DCI for scheduling multiple component carriers in accordance with aspects of the present disclosure. 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 LTE-Advanced (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, communication with low-cost and low-complexity devices, or any combination thereof, etc.

[0071] The base stations 105 may be dispersed throughout a geographic area to form the wireless communication system 100 and may be devices of different forms or with 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 signal communication in accordance with one or more radio access technologies.

[0072] The UEs 115 may be dispersed throughout the entire coverage area 110 of the wireless communication system 100, and each UE 115 may be fixed or mobile, or fixed or mobile at different times. The UEs 115 may be devices of different forms or with different capabilities. Figure 1 Some example UEs 115 are shown. The UEs 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.

[0073] The base stations 105 may communicate with the core network 130, or with each other, or both. For example, the base stations 105 may interface 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 may communicate with each other directly (e.g., directly between the base stations 105) or indirectly (e.g., via the core network 130) or both via the backhaul links 120 (e.g., via X2, Xn, or other interfaces). In some examples, the backhaul links 120 may be or include one or more wireless links.

[0074] One or more of the base stations 105 described herein may include or may be referred to by those of ordinary skill in the art as a base station transceiver, radio base station, access point, radio transceiver, NodeB, eNodeB (eNB), next-generation NodeB or giga-NodeB (any of which may be referred to as a gNB), home NodeB, home eNodeB, or other suitable terms.

[0075] In other examples, the UE 115 may include or may be referred to as a mobile device, wireless device, remote device, handheld device or subscriber device, or some other suitable term, where "device" may also be referred to as a unit, station, terminal or client. The UE 115 may also include or may be referred to as a personal electronic device, such as, a cellular phone, personal digital assistant (PDA), multimedia / entertainment device (e.g., radio, MP3 player, video device), camera, gaming device, navigation / location device (e.g., based on GNSS (Global Navigation Satellite System) such as GPS (Global Positioning System), Beidou, GLONASS or Galileo (a ground-based device)), tablet computer, laptop computer, personal computer, netbook, smartbook, personal computer, smart device, wearable device (e.g., smartwatch, smart clothing, smart glasses, virtual reality glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet)), drone, robot / robotic device, vehicle, vehicle device, meter (e.g., parking meter, electricity meter, gas meter, water meter), monitor, air pump, electrical appliance (e.g., kitchen appliance, washing machine, dryer), location tag, medical / healthcare device, implant, sensor / actuator, display or any other suitable device configured to communicate via wireless or wired medium. In some examples, the UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device or machine type communication (MTC) device and other examples, which may be implemented in various objects, such as in applications, vehicles, meters and other examples. In one aspect, the techniques disclosed herein may be applicable to MTC or IoT UEs. MTC or IoT UEs may include MTC / enhanced MTC (eMTC, also referred to as CAT-M, Cat M1) UEs, NB-IoT (also referred to as CAT NB1) UEs, and other types of UEs. eMTC and NB-IoT may refer to future technologies that may evolve from or be based on these technologies. For example, eMTC may include FeMTC (further eMTC), FeMTC (enhanced further eMTC) or mMTC (massive MTC), and NB-IoT may include eNB-IoT (enhanced NB-IoT) or FeNB-IoT (further enhanced NB-IoT).

[0076] 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, as Figure 1 shown.

[0077] The UE 115 and the base station 105 may wirelessly communicate with each other via one or more communication links 125 on one or more carriers. The term "carrier" may refer to a set of radio 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 (e.g., bandwidth part (BWP)) of a radio frequency spectrum band 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 that coordinates the operation for 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. The UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers.

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

[0079] 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 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).

[0080] 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 multiple determined bandwidths of a carrier for a particular 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 configured 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.

[0081] The signal waveform transmitted via a carrier can be composed of multiple subcarriers (e.g., using a multicarrier modulation (MCM) technique such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system that employs an MCM technique, a resource element can include a symbol period (e.g., the duration of one modulation symbol) and a subcarrier, where the symbol period and the subcarrier spacing are inversely correlated. 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 the UE 115 receives and the higher the order of the modulation scheme, the higher the data rate for the UE 115 may be. Wireless communication resources can refer to a combination of radio spectrum resources, time resources, and space resources (e.g., spatial layers or beams), and the use of multiple spatial layers can further increase the data rate or data integrity for communicating with the UE 115.

[0082] The time interval for the base station 105 or the UE 115 can be expressed as a multiple of a basic time unit. For example, this basic time unit can refer to T s = 1 / (Δf max ·N f ) seconds of sampling period, 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., in the range of 0 to 1023).

[0083] Each frame may include a plurality of consecutively numbered sub - frames or time slots, and each sub - frame or time slot may have the same duration. In some examples, a frame may be partitioned (e.g., in the time domain) into sub - frames, and each sub - frame may be further partitioned into a plurality of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the sub - carrier spacing. Each time slot may include a plurality of periods (e.g., depending on the length of the cyclic prefix before each symbol period). In some wireless communication systems 100, a time slot may be further partitioned into a plurality of mini - slots containing one or more symbols. In addition to the cyclic prefix, each symbol period may contain one or more (e.g., N f ) sampling periods. The duration of a symbol period may depend on the sub - carrier spacing or the operating frequency band.

[0084] A sub - frame, time slot, sub - time slot, mini - slot, or 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 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 a burst of shortened TTIs (sTTIs)).

[0085] Physical channels may be multiplexed on a carrier according to various techniques. Physical control channels and physical data channels may be multiplexed on a downlink carrier, for example, using one or more of time - division multiplexing (TDM) techniques, frequency - division multiplexing (FDM) techniques, or hybrid TDM - FDM techniques. A control region (e.g., a control resource set (CORESET)) for a physical control channel may be defined by the number of symbol periods and may extend over the system bandwidth of the carrier or a subset of the system bandwidth. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more UEs 115 may monitor or search for a 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 set may include a common search space set configured to send control information to a plurality of UEs 115 and a UE - specific search space set for sending control information to a specific UE 115.

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

[0087] The wireless communication system 100 can be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 can be configured to support ultra-reliable low-latency communication (URLLC) or mission-critical communication. The UE 115 can be designed to support ultra-reliable, low-latency, or critical functions (e.g., mission-critical functions). Ultra-reliable communication can include private communication or group communication and can 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 can include prioritization of services, and mission-critical services can be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, mission-critical, and ultra-reliable low-latency are used interchangeably herein.

[0088] In some examples, the UE 115 is also capable of directly communicating with other UEs 115 via 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 can be within the geographic coverage area 110 of the base station 105. Other UEs 115 in this group can 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, the group of UEs 115 communicating via D2D communication can utilize a one-to-many (1:M) system in which each UE 115 transmits to each other UE 115 in the group. In some examples, the base station 105 assists in scheduling resources for D2D communication. In other cases, D2D communication is performed between UEs 115 without involving the base station 105.

[0089] 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 or interconnects to 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 associated with the core network 130 for a UE 115 served by the base station 105, such as mobility, authentication, and bearer management. 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 the network operator's IP services 150. The network operator IP services 150 may include access to the Internet, an intranet(s), an IP multimedia subsystem (IMS), or packet-switched streaming services 5.

[0090] Some network devices, such as 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 the UE 115 through one or more other access network transmission entities 145, which may be referred to as radio heads, intelligent radio heads, or transmit / receive 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 consolidated into a single network device (e.g., the base station 105).

[0091] The wireless communication system 100 may operate using one or more frequency bands, typically 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 one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features; however, the waves may be sufficient to penetrate structures to serve a UE 115 located indoors in a macro cell. Transmission of UHF waves may be associated with smaller antennas and shorter distances (e.g., less than 100 kilometers) compared to transmission using smaller frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0092] Wireless communication system 100 can utilize both licensed and unlicensed radio spectrum bands. For example, wireless communication system 100 can employ Licensed-Assisted Access (LAA), LTE-Unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed 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 combined with a component carrier operating in a licensed band based on a carrier aggregation configuration (e.g., LAA). Operations in the unlicensed spectrum can include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.

[0093] Base station 105 or UE 115 can be equipped with multiple antennas, and the multiple antennas 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 with antenna ports in multiple rows and columns, and base station 105 can use the antenna array to support beamforming for communication with UE 115. Similarly, UE 115 can have one or more antenna arrays, which can support various MIMO or beamforming operations. Additionally or alternatively, an antenna panel can support radio frequency beamforming for signals transmitted via an antenna port.

[0094] Beamforming (which can 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 or UE 115) to form or direct an antenna beam (e.g., a transmit beam, a 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 direction with respect 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 can be defined by a set of beamforming weights associated with a particular direction (e.g., with respect to the antenna array of the transmitting device or the receiving device, or with respect to some other direction).

[0095] UE 115 and base station 105 may support retransmission of data to increase the likelihood that the data is successfully received. HARQ feedback is a technique for increasing the likelihood of correctly receiving data over communication link 125. HARQ may 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 may improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device may support same-slot HARQ feedback, where the device may provide HARQ feedback for data received in previous symbols in a particular slot during that slot. In other cases, the device may provide HARQ feedback in a subsequent slot or according to some other time interval.

[0096] Wireless communication system 100 may support efficient techniques for enabling UE 115 to receive DCI from base station 105 that schedules multiple component carriers, multiple time intervals for one or more component carriers, or a combination thereof. For example, UE 115 may communicate with the base station via a set of component carriers according to a carrier aggregation configuration. In some cases, UE 115 may receive a configuration message indicating one or more unit groups, where each group may include one or more component carriers and / or one or more time slots for each component carrier. UE 115 may receive DCI from the base station based on being connected to the base station, the DCI including one or more fields common to the unit groups, where the group may include multiple (e.g., two or more) component carriers from the set of component carriers. In some cases, the DCI may use different DCI fields of the same DCI format to schedule one or more unit groups. In some cases, the DCI may schedule a set of data transmissions via one or more unit groups, where the data transmission may be a downlink data transmission sent from the base station or an uplink data transmission sent from UE 115. Subsequently, UE 115 may send or receive the set of data transmissions via the scheduled units based on receiving the DCI.

[0097] Figure 2 FIG. illustrates an example of a wireless communication system 200 that supports DCI for scheduling multiple component carriers in accordance with aspects of the present disclosure. Wireless communication system 200 may include base station 105-a and UE 115-a, which may be examples of base station 105 and UE 115 as described in reference Figure 1 described. Base station 105-a may serve a geographic coverage area 110-a. In some cases, base station 105-a may implement a multi-component carrier scheduling process with UE 115-a. Additionally or alternatively, other wireless devices such as UE 115-a may implement a multi-component carrier scheduling process.

[0098] UE 115-a can establish a connection with base station 105-a via communication link 205 over at least a first component carrier and a second component carrier (such as component carriers 210-a and 210-b), where communication link 205 can support downlink and uplink transmissions. In some cases, component carrier 210-b can correspond to a DSS PCell, while component carrier 210-a can correspond to a non-DSS SCell. In some other cases, both component carrier 210-a and component carrier 210-b can support DSS, or neither of the two component carriers 210 can support DSS. In some cases, component carrier 210-b can support a low frequency band (e.g., 2 GHz) and a low subcarrier spacing (e.g., 15 kHz), while component carrier 210-a can support a mid-high frequency band (e.g., 3.5 GHz, 4.7 GHz) and a high subcarrier spacing (e.g., 30 kHz). Thus, a DSS PCell that supports a low frequency band (e.g., component carrier 210-b) can serve multiple types of devices (e.g., LTE UE, NR UE), which may affect the ability of certain devices to achieve peak throughput because the resources of component carrier 210 are shared among multiple types of devices and each type of device may not be able to utilize the complete set of resources in a given spectrum. To support network improvements (such as improving reliability and spectral efficiency), base station 105-a and UE 115-a can be configured to support data transmission scheduling information placed on a non-DSS SCell that supports a higher frequency (e.g., component carrier 210-a) because component carrier 210-a can serve a single type of device (e.g., 5G NR devices) and the complete spectrum supported by component carrier 210-a can be used by each device on component carrier 210-a.

[0099] To further improve network reliability and enhance spectrum efficiency, a single data scheduling indicator (e.g., PDCCH, DCI format, DCI) can be used to schedule data transmission (e.g., downlink data transmission or uplink data transmission) on multiple component carriers (e.g., multiple cells) (such as component carriers 210-a and 210-b or multiple time intervals 225 or a combination thereof), rather than using multiple scheduling indicators to schedule multiple component carriers 210. In one example, the physical control channel 215 (e.g., PDCCH) on component carrier 210-a can schedule multiple (e.g., two or more) physical shared channels 220 (e.g., PDSCH, PUSCH) on component carrier 210-a or 210-b or both by using a single DCI. In another example, the physical control channel 215 (e.g., PDCCH) on component carrier 210-b can schedule the physical shared channel 220 (e.g., PDSCH, PUSCH) on component carriers 210-a and 210-b by using a single DCI

[0100] To reduce the resources for transmitting or receiving the physical control channel 215 that schedules data transmission on multiple component carriers 210 and / or multiple time intervals 225, devices in a communication system (e.g., wireless communication system 200) can be configured to support scheduled unit grouping. As part of the scheduled unit grouping, units such as component carriers 210 or time intervals 225 can be configured by a base station as part of a group, for example. In some cases, the groups can be configured based on frequency resources or time resources or a combination thereof. For example, component carriers 210-a and 210-b can be configured as part of the same group or different groups. In another example, all or a subset of the time intervals 225 (e.g., time slots, sub-slots or mini-slots, TTIs) of component carrier 210-a can be configured as part of a group, such that one or more of time intervals 225-a, 225-b or 225-c can be configured as part of the same group. Additionally or alternatively, the time intervals 225 of component carrier 210-a can be divided into multiple groups. As another example, all or a subset of the time intervals 225 of component carrier 210-b can be configured as part of a group, such that one or more of time intervals 225-d or 225-e can be configured as part of the same group. Additionally or alternatively, the time intervals 225 of component carrier 210-b can be divided into multiple groups.

[0101] Each unit within the group can be configured with the same or similar parameters (e.g., RRC parameters, HARQ ID, frequency domain parameters, time domain parameters), such that a single physical control channel 215 can schedule the group of units instead of each individual unit, to reduce the resources used for DCI transmission. For example, a subset of the time intervals 225 of component carrier 210-a can be configured as part of the same group. Each time interval 225 in the group can be associated with the same parameters, or mostly the same parameters (e.g., the parameters related to time can be different between the time intervals 225 in the same group).

[0102] Figure 3 FIG. illustrates an example of a component carrier scheduling configuration 300 that supports DCI for scheduling multiple component carriers according to aspects of the present disclosure. The component carrier scheduling configuration 300 can be performed by a base station or a UE or both, and the base station or UE can be an example of the base station and UE referenced Figure 1 and Figure 2 described. In some cases, the base station can implement a multi-component carrier scheduling procedure with the UE according to the component carrier scheduling configuration 300. Additionally or alternatively, other wireless devices such as a UE can implement a multi-component carrier scheduling procedure.

[0103] As described herein, a UE can communicate with a base station via a set of component carriers 305 according to a carrier aggregation configuration. For example, the UE can communicate with the base station via one or all of component carriers CC0 305-a, CC1 305-b, CC2 305-c, CC3 305-d, or CC4 305-e, where each component carrier 305 can be a DSS component carrier, a non-DSS component carrier, a PCell, or an SCell. To efficiently schedule data transmissions such as downlink or uplink data transmissions on one or more component carriers 305, the base station or some other network device can configure a group of units, where a unit can refer to a component carrier 305 or a time interval of a component carrier 305 or a combination thereof. For example, as Figure 3As shown, the base station can group component carriers 305. In some cases, the base station can group component carriers 305 based on the component carriers 305 being in the same frequency band. For example, communication between the base station and the UE can occur on two frequency bands, where CC0 305-a is associated with the first frequency band, and CC1 305-b, CC2 305-c, CC3 305-d, and CC4 305-e are associated with the second frequency band. Thus, the base station can configure CC0 305-a as part of group 1 and configure CC1 305-b, CC2 305-c, CC3 305-d, and CC4 305-e as part of group 2. The base station can indicate the grouping configuration to the UE via semi-static signaling (e.g., RRC signaling). For example, the base station can configure the component carrier grouping before communication using multiple component carriers 305 and indicate the component carrier grouping to one or more UEs.

[0104] Each of the component carriers 305 can be associated with a parameter set, such as RRC parameters. In some implementations, due to the existence of cell grouping, each parameter of the parameter set associated with each component carrier 305 of the group of component carriers 305 can be the same. For example, the RRC parameters associated with each component carrier 305 in group 1 can be the same and the RRC parameters associated with each component carrier 305 in group 2 can be the same, where the RRC parameters between group 1 and group 2 can be different.

[0105] In some cases, the network (e.g., the base station) can configure RRC parameters for each component carrier 305 in the group, where the RRC parameters for each component carrier 305 are the same, and indicate the RRC parameters for each component carrier to the UE. Additionally or alternatively, once the component carriers 305 are configured to be in the same group, the RRC parameters of a particular component carrier 305 in the group can be considered to be copied by the UE to the other component carriers 305 in the same group. For example, the UE can receive an indication of the component carriers 305 configured as part of the group, and the UE can identify (e.g., based on previous signaling from the base station) the RRC parameters of at least one component carrier 305 within the group. The UE can apply the RRC parameters of one component carrier 305 to all component carriers 305 within the group.

[0106] In some cases, the DCI field 325 can be common or shared among the component carriers 305 in a group. For example, the code point of the DCI field 325 can indicate the same value for all component carriers in the same group. Thus, the component carriers 305 in a group can be referred to as mirrors, where the time domain resource allocation (TDRA), frequency domain resource allocation (FDRA), or modulation and coding scheme (MCS) index is the same among the component carriers 305 in the group. Since some or all of the parameters for each cell (e.g., TDRA, FDRA parameters) are the same or mostly the same, the DCI can reduce the number of parameter sets included in the DCI because the DCI can include one parameter set for each group instead of indicating parameter sets for each cell. In cases where the parameters are mostly the same, the DCI can combine the same parameters for the group and indicate these parameters once for the group, and separately indicate the non - identical parameters for each cell. Between different groups, separate DCI fields 325 can be included in the same DCI format 320, where each separate DCI field 325 can include data transmission scheduling information on the component carriers 305 included in the DCI field 325 and its associated group.

[0107] Thus, the base station can efficiently schedule one or more data transmissions on the group instead of scheduling each component carrier 305 individually. For example, as described herein, the base station can configure the UE with two groups, where group 1 includes CC0 305 - a, and group 2 includes CC1 305 - b, CC2 305 - c, CC3

[0108] 305-d and CC4 305-e. Each component carrier 305 in Group 1 can be associated with the same parameter set, and each component carrier 305 in Group 2 can be associated with the same parameter set. To schedule data transmission on one or more component carriers 305, the base station can send a physical control channel 310 via CC0 305-a, where the physical control channel 310 can include DCI format 320. DCI format 320 can include DCI field 325-a and DCI field 325-b, where DCI fields 325-a and 325-b can be the same size or different sizes based on the RRC configuration for each group. DCI field 325-a can include data transmission scheduling information for Group 1 applicable to each component carrier 305 in Group 1, and DCI field 325-b can include data transmission scheduling information for Group 2 applicable to each component carrier 305 in Group 2. For example, DCI field 325-a can indicate information for data transmission 315-a on CC0 305-a associated with Group 1, and DCI field 325-b can indicate information for data transmissions 315-b to 315-e on CC1 305-b to CC4 305-e respectively associated with Group 2.

[0109] Figure 4 FIG. illustrates an example of a component carrier scheduling configuration 400 that supports DCI for scheduling multiple component carriers in accordance with aspects of the present disclosure. The component carrier scheduling configuration 400 can be performed by a base station or a UE or both, and the base station or UE can be an example of the base station and UE described with reference Figures 1 to 3 above. In some cases, the base station can implement a multi-component carrier scheduling procedure with the UE based on the component carrier scheduling configuration 400. Additionally or alternatively, other wireless devices such as a UE can implement a multi-component carrier scheduling procedure.

[0110] As described herein, a UE can communicate with a base station via a set of component carriers 405 according to a carrier aggregation configuration. For example, the UE can communicate with the base station via one or both of component carriers 405-a or 405-b, where each component carrier 405 can be a DSS component carrier, a non-DSS component carrier, a PCell, or an SCell. To efficiently schedule data transmissions such as downlink or uplink data transmissions on one or more component carriers 405, the base station or some other network device can configure a group of units, where a unit can refer to a component carrier 405 or a time interval 415 (e.g., a time slot) of a component carrier 405 or a combination thereof. For example, as Figure 4As shown, the base station can group the time intervals 415 of the component carrier 405. The base station can also group the time intervals 415 and the component carrier 405 such that the base station can configure one or more time intervals 415 of multiple component carriers 405 to be part of the same group. In some cases, the base station can group the component carriers 405 based on the component carriers being in the same frequency band. For example, the communication between the base station and the UE can occur on two frequency bands, where the component carrier 405-a is associated with the first frequency band and the component carrier 405-b is associated with the second frequency band. Thus, the base station can configure one or more time intervals 415 of the component carrier 405-a to be part of group 1 and one or more time intervals 415 of the component carrier 405-b to be part of group 2.

[0111] In some cases, the base station can determine which time intervals 415 or which component carriers 405 to include in the group based on the subcarrier spacing of each component carrier 405. In some cases, the base station can group the component carriers 405 and the time intervals 415 based on the component carriers being in the same frequency band or having the same subcarrier spacing or both. For example, the component carrier 405-a can have a larger subcarrier spacing (e.g., 30 kHz) than the component carrier 405-b (e.g., 15 kHz). Additionally or alternatively, the component carrier 405-a or 405-b can be in different frequency bands. Thus, the base station can configure each component carrier 405 to be part of a different group. Since the subcarrier spacings of the component carriers 405 are different, two time intervals 415 of the component carrier 405-a can be suitable for the same duration as one time interval 415 of the component carrier 405-b. The base station can group the time intervals 415 based on the number of time intervals 415 suitable for the duration. For example, the base station can first assign the time interval 415-c to group 1 and then determine that two time intervals 415 (e.g., time intervals 415-a and 415-b) of the component carrier 405-a are suitable for the same duration as the time interval 415-c. Thus, the base station can group the intervals 415-a and 415-b as part of group 2. The base station can indicate the grouping configuration to the UE via semi-static signaling (e.g., RRC). For example, the base station can configure the time interval 415 grouping before communication using multiple component carriers 405 and indicate the time interval 415 grouping to one or more UEs.

[0112] In some implementations, due to the existence of unit grouping, each parameter of the parameter set associated with each component carrier 405 of the group of component carriers 405 can be the same. For example, the RRC parameters associated with each time interval 415 and each component carrier 405 in group 1 can be the same, and the RRC parameters associated with each time interval 415 and each component carrier 405 in group 2 can be the same, where the RRC parameters between group 1 and group 2 can be different. In some cases, the network (e.g., the base station) can configure parameters (e.g., RRC parameters) for each component carrier 405 and time interval 415 in the group, where the parameters for each unit in the group are the same or mostly the same, and indicate the parameters of each unit to the UE. Additionally or alternatively, once the component carrier 405 and / or time interval 415 are configured to be in the same group, the RRC parameters of a specific component carrier 405 or time interval 415 in the group can be considered to be copied by the UE to other units in the same group. For example, the UE can receive an indication of the component carrier 405 and time interval 415 configured as part of the group, and the UE can identify (e.g., based on previous signaling from the base station) the RRC parameters of at least one unit within the group. The UE can apply the RRC parameters for one unit to all units within the group.

[0113] In some cases, the DCI field 425 can be common or shared among the component carriers 405 and / or time intervals 415 in the group. For example, the code point of the DCI field 425 can indicate the same value for all component carriers 405 and time intervals 415 in the same group. Between different groups, separate DCI fields 425 can be included in the same DCI format 420, where each separate DCI field 425 can include data transmission scheduling information for each unit included in the group with which the DCI field 425 is associated. Thus, the units in the group can be referred to as mirrors, where the TDRA, FDRA, MCS index, or start and length indicator (SLIV) are the same among the units in the group. Since the parameters in the DCI included in the parameter set of each group are the same or mostly the same, the base station can reduce the number of parameter sets included in the DCI, because the DCI can include one parameter set for each group instead of indicating the parameter sets for each unit, resulting in a common or shared DCI field 425.

[0114] In some implementations, not all parameters in a parameter set are the same across time intervals 415 in a group. For example, K0, K1, and HARQ process IDs, and other parameters can be time-based, where K0 and K1 can be TDRAs. Thus, the parameters can vary with different time intervals 415. For example, the K0 value indicates the number of time intervals 415 (e.g., time slots, sub - time slots, or mini - time slots) from the time interval 415 in which the physical control channel 410 (e.g., DCI) is received to the time interval 415 for which the DCI schedules a downlink transmission, as such K0 will be different for different time intervals 415 in the group. Similarly, K2 indicates the number of time intervals 415 between the DCI and the uplink data transmission scheduled by the DCI. For example, if the physical control channel 410 includes DCI that schedules time intervals 415 - a and 415 - b for downlink data transmission, the K0 value for time interval 415 - a will be two, while the K0 value for time interval 415 - b will be three. The K2 value and the HARQ process ID will also vary based on time slots.

[0115] In cases where most of the parameters are the same (e.g., grouping time intervals 415 where the TDRA varies based on time), the DCI can combine similar parameters for the group and indicate these parameters once for the group (e.g., in a common or shared DCI field 425), and separately indicate non - similar parameters for each unit. In some cases, the DCI can indicate the TDRA (e.g., K0, K2, HARQ ID) for each time interval 415 of the group, where the time intervals 415 can be in the same component carrier 405 or different component carriers 405 within the group. In some cases, the DCI can indicate the TDRA for a certain time interval 415 of one or more component carriers 405 in the group, such as the first scheduled time interval 415 of each component carrier 405, or the first scheduled time interval 415 of a certain component carrier 405. Then, the UE can increment the TDRA accordingly for each scheduled time interval 415 after the time interval 415 in which the TDRA is indicated.

[0116] Accordingly, the base station can effectively schedule one or more data transmissions on a group rather than scheduling each cell individually. For example, as described herein, the base station can configure the UE with two groups, where Group 1 includes component carrier 405-b and Group 2 includes component carrier 405-a. Each component carrier 405 in Group 1 can be associated with the same set of parameters (e.g., RRC parameters, FDRA parameters), and each component carrier 305 in Group 2 can be associated with the same set of parameters. However, the time intervals 415 within the same group can be associated with different time-related parameters (e.g., TDRA). To schedule data transmissions on one or more component carriers 405, the base station can transmit a physical control channel 410 via component carrier 405-a, where the physical control channel 410 can include DCI format 420. DCI format 420 can include DCI field 425-a and DCI field 425-b, and DCI fields 425-a and 425-b can be the same size or different sizes based on the RRC configuration for each group. DCI field 425-a can include data transmission scheduling information applicable to each cell in Group 1 for Group 1, and DCI field 425-b can include data transmission scheduling information applicable to each cell in Group 2 for Group 2. In some cases, each DCI field 425 can include TDRA information for each cell or one cell rather than for each group. For example, DCI field 425-b can indicate information about data transmissions on time intervals 415-a and / or 415-b on component carrier 405-a associated with Group 2, while DCI field 425-a can indicate information about data transmissions in time interval 415-c on component carrier 405-b associated with Group 1.

[0117] Figure 5A and Figure 5B respectively illustrate examples of bitmap indicators 500 and 501 that support DCI for scheduling multiple component carriers according to aspects of the present disclosure. The bitmap indicators 500 and 501 can be performed by the base station or the UE or both, and the base station or the UE can be examples of the base station and the UE described with reference to Figures 1 to 4 In some cases, the base station can implement a multi-component carrier scheduling process with the UE that includes the bitmap indicators 500 and / or 501. Additionally or alternatively, other wireless devices such as the UE can implement a multi-component carrier scheduling process.

[0118] The base station can semi-statically group units (e.g., component carriers 505, time intervals 525), and indicate the grouping to the UE via RRC signaling or some other semi-static signaling process. In some cases, not all units in group 520 can be scheduled by each physical control channel 510 (e.g., DCI). For example, the units scheduled by each DCI can be based on traffic, traffic conditions, or power limitations. Therefore, the base station can configure a bitmap for each configured group and send it to the UE to indicate which units in group 520 are scheduled. The bitmap can be included in the DCI, where the bitmap is group-specific. For example, the DCI format can include scheduling information for the first group and the second group. Thus, the DCI format can include a bitmap for group 1 and a bitmap for group 2. The bitmap can include bits for each unit in the group. For example, if the group includes a single time interval for one or more component carriers, the bitmap for the group can include one bit for each component carrier. In another example, if the group includes multiple time intervals for one or more component carriers, the bitmap for the group can include one bit for each time interval. A 1 bit can indicate that the unit is scheduled for data transmission, while a 0 bit can indicate that the unit is not scheduled for data transmission.

[0119] As Figure 5A shown, the base station can group component carriers 505 in the same frequency band based on component carrier 505, as described in conjunction with Figure 3 the above. For example, the base station can group CC0 505-a into one group, and group CC1 505-b, CC2 505-c, CC3 505-d, and CC4 505-e into group 2

[0120] 520-a. In some cases, the base station can potentially schedule data transmission 515 on each component carrier 505. For example, the base station can determine to schedule data transmission 515 (e.g., data transmissions 515-a, 515-b, 515-c, and 515-d) on each component carrier 505 or a subset of component carriers. As in the example shown in Figure 5A the above, the base station can determine to schedule data transmission on CC1 505-b and CC4 505-e, rather than on CC2 505-c and CC3 505-d. Therefore, the base station can configure a 4-bit bitmap for group 520-a that includes bits for each component carrier 505, where the bitmap can be read as 1001. The UE can receive the bitmap in the DCI of the physical control channel 510-a and determine that CC1 505-b and CC4 505-e are scheduled for data transmission.

[0121] As Figure 5BAs shown, the base station can group the time intervals 525 either individually or in combination with grouping component carriers 505. For example, the base station can group the time intervals 525-a and 525-b of component carrier 505-f in group 520-b. In some cases, the base station can potentially schedule data transmissions on each time interval 525 of group 520-b. In some cases, as Figure 5B shown, the base station can determine to schedule data transmissions on a subset of the time intervals 525 of group 520-b. For example, the base station can determine to schedule data transmissions on time interval 525-a. Thus, the base station can configure a 2-bit bitmap for group 520-b that includes bits for each time interval 525, where the bitmap can be read as 10. The UE can receive the bitmap in the DCI of the physical control channel 510-a and determine that time interval 525-a is scheduled for data transmission while time interval 525-b is not scheduled for data transmission.

[0122] Figure 6A and Figure 6B respectively illustrate examples of RIV configurations 600 and 601 that support DCI for scheduling multiple component carriers according to aspects of the present disclosure. The RIV configurations 600 and 601 can be performed by the base station or the UE or both, and the base station or the UE can be examples of the base station and the UE described with reference to Figures 1 to 5B In some cases, the base station can implement a multi-component carrier scheduling process with the UE using the RIV configurations 600 and / or 601. Additionally or alternatively, other wireless devices such as the UE can implement a multi-component carrier scheduling process.

[0123] In some cases, such as when the base station configures a large number of units as part of a group, a large number of bits can be used in the DCI to include a bitmap that includes bits for each unit of the group. For example, the base station can group multiple component carriers and / or multiple time slots (e.g., time intervals) in the same group. Thus, in some implementations, the base station can indicate the RIV to the UE instead of the bitmap to reduce the number of bits included in the DCI (e.g., reduce the bit width). The RIV can be included in the DCI and can indicate a set of consecutive units scheduled in the group. The RIV can indicate the starting unit (e.g., the first unit for which data is scheduled) and the number of consecutive units scheduled by the DCI after the starting unit. Based on the RIV, the UE can determine which units are scheduled. The DCI format can include multiple RIV fields, where each RIV field is associated with a different group of units.

[0124] In some implementations, such as if multiple component carriers and multiple time slots are included in the same group, an interpretation of consecutive units can be defined. In some cases, the interpretation can be defined and signaled to the UE either aperiodically, semi-statically (e.g., via RRC), or dynamically (e.g., via DCI). For example, as Figure 6A shown, the order of the units indicated by the RIV field can be frequency first and time second. In Figure 6A , group 615-a can include four component carriers and two time slots for each component carrier. Thus, group 615-a can include 8 units. The base station can schedule data transmission on all 8 units or a subset of the 8 units. The base station can include the RIV field in the DCI included in the physical control channel 610-a, which field indicates the first unit being scheduled and the number of consecutive units being scheduled after the first unit. In Figure 6A 's example, the interpretation of consecutive units is frequency first and time second. Thus, if the base station schedules all 8 units in group 615-a, the UE can receive the DCI in the physical control channel 610-a and determine based on the RIV field that the starting unit is the bottom-most, left-most unit of group 615-a, and determine that the next scheduled unit is in the next component carrier. The UE can move up in the component carrier until it reaches the last component carrier of group 615-a, then move to the next time slot and start from the bottom-most component carrier of the next time slot. The UE can continue to move up in the component carrier until the UE reaches the last component carrier of the second time slot. The UE can identify the data transmission for each unit in this way until the UE reaches the top-most, right-most unit of group 615-a.

[0125] In some cases, the DCI format can indicate the data transmission scheduling for more than one group (such as, group 615-a and 620-a). The base station can indicate the scheduled units in different ways for different groups. For example, the base station can indicate a bitmap for one group and the RIV field for another group. In some cases, the base station can determine to use the RIV field to indicate the scheduled units based on a threshold number of units included in the group. For example, group 615-a can include a number of units exceeding the threshold, and group 620-a can include a number of units below the threshold. Thus, the physical control channel 610-a can include a DCI field for group 615-a that includes the RIV field, and a DCI field for group 620-a that includes a bitmap for group 620-a.

[0126] In another example, as Figure 6B shown, the order of the units indicated by the RIV field can be time first and frequency second. In Figure 6BIn a similar manner to group 615-a, group 615-b may include eight units. Thus, if the base station schedules all eight units or a subset of the units in group 615-b, the UE may receive the DCI in the physical control channel 610-b and determine, based on the RIV field, that the starting unit is the bottom-most, left-most unit of group 615-b and that the next scheduled unit is in the next time slot. The UE may move slot by slot until all the time slots of the current component carrier have been identified. The UE may then move up to the next component carrier of group 615-b and continue moving slot by slot. The UE may identify data transmissions for each unit in this manner until the UE reaches the top-most, right-most unit of group 615-b. Similar to the example shown in Figure 6A group 615-b may include a number of units that exceeds a threshold, and group 620-a may include a number of units that is below the threshold. Thus, the physical control channel 610-b may include a DCI field for group 615-b that includes the RIV field, and a DCI field for group 620-b that includes a bitmap for group 620-b.

[0127] Figure 7 FIG. illustrates an example of DCI format 700 that supports DCI for scheduling multiple component carriers in accordance with aspects of the present disclosure. DCI format 700 may be performed by a base station or a UE or both, and the base station or UE may be examples of the base station and UE described with reference to Figures 1 to 6B In some cases, the base station may implement a multi-component carrier scheduling procedure with the UE that includes sending DCI format 700 to the UE. Additionally or alternatively, other wireless devices such as the UE may implement a multi-component carrier scheduling procedure with DCI format 700.

[0128] In the Figure 7 example shown, the base station may configure two groups of units, where each group may include any number of component carriers or any number of time intervals (e.g., time slots) or a combination thereof. As described in connection with Figure 3 and Figure 4As described above, DCI format 700 may include group-specific DCI fields 710, such as dedicated DCI fields 710-a and 710-b. The dedicated DCI field 710-a may include data transmission parameters specific to the first unit group, and the dedicated DCI field 710-b may include data transmission parameters specific to the second unit group. DCI format 700 may also include a bitmap or RIV DCI field 710 for each group. The bitmap / RIV DCI field 705-a may include a bitmap or RIV field indicating which units of the first group are scheduled for data transmission, and the bitmap / RIV DCI field 705-b may include a bitmap or RIV field indicating which units of the second group are scheduled for data transmission. DCI format 700 may also include a common DCI field 715, which includes parameters applicable to both the first group and the second group.

[0129] In some cases, DCI format 700 may include an FDRA field that is either separate (e.g., group-specific) for each group or common for each group. For example, one or more FDRA fields may be included in the dedicated DCI fields 710-a, 710-b, or both, resulting in separate FDRA fields. In some cases, the resource allocation (e.g., physical resource block allocation) for each unit in the group may be the same, and the FDRA field may be group-specific, where the FDRA field in each dedicated DCI field 710 may indicate the resource allocation for each group or each unit in the group. Additionally or alternatively, one or more FDRA fields may be included in the common DCI field 715 for both the first unit group and the second unit group, resulting in a common FDRA field. In such a configuration, the FDRA code point may indicate the resource allocation (e.g., physical resource block (PRB) resource allocation) for each unit in the first unit group and the resource allocation (e.g., PRB resource allocation) for each unit in the second unit group. The mapping between the FDRA code point and the resource allocations for the first unit group and the second unit group may be configured semi-statically, such as via RRC signaling.

[0130] In some cases, DCI format 700 may include TDRA fields that are either per-group separate (e.g., group-specific) or per-group common. For example, one or more TDRA fields may be included in dedicated DCI field 710-a, DCI field 710-b, or both, resulting in per-group separate TDRA fields. In such cases, some time-dependent indicators (e.g., SLIV) may be the same for all cells in each cell group. Thus, the indicator (e.g., SLIV) may be indicated by the TDRA fields for the first cell group and the second cell group, respectively. In some other cases, some time-related indicators (e.g., K0 and / or K2) may increment with each slot progression. Thus, these indicators (e.g., K0 and / or K2 values) may be indicated by the TDRA fields for each cell group of the first slot of the cell group. Based on the indication of the K0 and / or K2 values of the first slot of each group, the UE may increment the K0 / K2 values for each subsequent slot of each cell group. Additionally or alternatively, one or more TDRA values may be included in common DCI field 715 for the first cell group and the second cell group. In such cases, the TDRA code point may indicate the time-dependent indicators for each cell in the first slot of the first cell group (e.g., SLIV and K0 for downlink data transmission, SLIV and K2 for uplink data transmission) and the time-dependent indicators for each cell in the first slot of the second cell group (e.g., SLIV and K0 for downlink data transmission, SLIV and K2 for uplink data transmission). The mapping between the TDRA code point and the time-dependent indicators (e.g., SLIV, K0, K2) for the first slot of the first cell group and the time-dependent indicators (e.g., SLIV, K0, K2) for the first slot of the second cell group may be configured semi-statically, e.g., via RRC signaling.

[0131] In some cases, DCI format 700 may include HARQ ID fields that are either per-group separate (e.g., group-specific) or per-group common. Among component carriers in the same group, the HARQ ID field may be the same. Among slots within the same group, the HARQ ID may increment with each slot progression. Thus, the HARQ ID indication (e.g., a per-group separate indication or a common indication applicable to each group) may be for the first slot in the group. To determine subsequent slots in the group, the UE may use a modulo operation (such as modulo 16 operation) to increment the HARQ ID.

[0132] Figure 8Illustrated is an example of a data retransmission process 800 that supports DCI for scheduling multiple component carriers in accordance with aspects of the present disclosure. The data retransmission process 800 may be performed by a base station or a UE or both, which may be examples of the base station and UE described with reference to Figures 1 to 7 In some cases, the base station may implement a multi-component carrier scheduling process with the UE that includes performing the data retransmission process 800 with the UE. Additionally or alternatively, other wireless devices such as the UE may implement a multi-component carrier scheduling process and perform or participate in the data retransmission process 800.

[0133] In some cases, the base station may include a new data indicator (NDI) in the DCI, the NDI including one or more bits to indicate to the UE whether the data scheduled on one or more units of one or more groups is new data or whether the data transmission is a retransmission. If the NDI is toggled such that the current NDI bit value is different from the previous NDI bit value, new data is scheduled. If the NDI is not toggled such that the current NDI bit value is the same as the previous NDI bit value, the data is a retransmission. The NDI may be indicated for each group and, in some cases, for each unit within the group.

[0134] In some cases, to reduce the number of bits used for each NDI and maintain flexible scheduling, a bitmap and / or RIV field included in the DCI format as described in conjunction with Figures 5A to 7 may be used for the NDI. For example, a physical control channel 810 (e.g., DCI) may include an NDI field for each configured group, such as an NDI field for a first group and a second NDI field for a second group. The DCI may also include a bitmap or RIV field for each group. In some cases, as shown in the top example of Figure 8 , the UE or the base station or both may determine that three data transmission errors have occurred (e.g., two errors in group 805-a and one error in group 805-b), where the UE or the base station is unable to successfully decode the scheduled data transmission. In either case, the base station may determine which units caused the errors (e.g., based on HARQ feedback). At 815-a, the base station may determine not to toggle the NDI for group 805-a and not to toggle the NDI for group 805-b. To avoid unnecessary retransmissions of all units in each group, the base station may also use the bitmap or RIV field of the DCI format to indicate which units may be retransmitted, where the data mapped to the units is fixed between the initial transmission and the retransmission. In the case of a bitmap, as shown in Figure 8As shown, the base station can indicate 1 for units to be retransmitted and 0 for units not to be retransmitted. Thus, at 815-a, the base station can not switch the NDI field for group 805-a or 805-b, and indicate a bitmap including two 1s for group 805-a and a bitmap including one 1 for group 805-b, where 1 is associated with unsuccessful transmission units. Based on the DCI format, the UE can send or receive three retransmissions in the associated units, where no other data is received in other units.

[0135] In some cases, after the retransmission at 815-a, all or a subset of the retransmissions may be successfully received, or all or a subset of the retransmissions may not be successfully received. For example, one unit from group 805-a after 815-a can result in an unsuccessful retransmission. At 815-b, the base station can determine not to switch the NDI for group 805-a because one unit results in an unsuccessful retransmission, and the base station can determine to switch the NDI for group 805-b because each unit of group 805-a results in a successful transmission. The base station can configure a bitmap or RIV for group 805-a indicating a certain unit that can be retransmitted. The base station can also configure a bitmap or RIV for group 805-b indicating new data transmission for the units of group 805-b. The UE can receive DCI from the base station and identify the non-switched NDI and the bitmap or RIV for group 805-a, and determine that one data retransmission is scheduled for the units of group 805-a, and identify the switched NDI and the bitmap or RIV for group 805-b, and determine that up to two new data transmissions are scheduled for group 805-b. Based on the identified information, the UE can send or receive retransmissions in the associated units of group 805-a, and send or receive the new transmissions scheduled in group 805-b.

[0136] In some implementations, for a semi-static HARQ ACK codebook (e.g., HARQ codebook type 1), regardless of the bitmap or RIV for the group, the UE can generate HARQ ACK bits for each potentially scheduled unit in the group. Additionally or alternatively, between groups, the control channel (e.g., PUCCH) resources for HARQ ACK can be shared between groups or can be separate across groups.

[0137] In some implementations, for a dynamic HARQ ACK codebook (e.g., HARQ codebook type 2), the number of HARQ ACK bits can be based on the number of scheduled units in a group (e.g., indicated by a bitmap or RIV). In some cases, the downlink allocation index (DAI) count is per unit, where the DAI can be incremented by one for each unit scheduled in the group. In some cases, the DAI count is per component carrier in the group, where the DAI is incremented by one if one or more time slots in the component carrier are scheduled in the group. In some implementations, HARQ ACK bundling per component carrier can be applied. In some cases, the DAI count is per group, where the DAI is incremented if one or more units are scheduled in the group. In some implementations, HARQ-ACK bundling per group can be applied.

[0138] Figure 9 FIG. illustrates an example of a processing flow 900 that supports DCI for scheduling multiple component carriers in accordance with aspects of the present disclosure. The processing flow 900 can illustrate an example multi-component carrier scheduling process. For example, base station 105-b can determine to schedule one or more component carriers or one or more time intervals for data transmission and indicate the scheduling to UE 115-b. Base station 105-b and UE 115-b can be examples of corresponding wireless devices as referred to Figures 1 to 8 described. In some cases, instead of base station 105-b implementing the component carrier scheduling process, a different type of wireless device (e.g., UE 115) can perform the process. Alternative examples can be implemented where certain steps are performed in a different order than described or not performed at all. In some cases, the steps can include additional features not mentioned below, or more steps can be added.

[0139] At 905, UE 115-b can communicate with base station 105-b via a set of component carriers according to a carrier aggregation configuration. The set of component carriers can include one or more DSS carriers, one or more non-DSS carriers, one or more SCell, or one or more PCell, or a combination thereof.

[0140] At 910, the UE 115-b can receive DCI from the base station 105-b based on being connected to the base station, where the DCI includes one or more fields common to a plurality (e.g., two or more) of component carriers from a set of component carriers. The DCI can schedule a data transmission set over two or more component carriers. In some cases, the plurality of component carriers can be a component carrier group, where the group can additionally or alternatively include one or more time intervals (e.g., TTIs, time slots) for each component carrier in the group. For example, the DCI can schedule a data transmission set over two or more component carriers for a set of TTIs (e.g., one or more). Thus, the group can include a set of units that includes one or more component carriers, or one or more time intervals, or a combination thereof.

[0141] In some cases, the DCI can include DCI fields for multiple groups. For example, the DCI can include one or more fields common to a first group and one or more different fields (e.g., a second set of fields) common to a second group. The second set of fields can schedule a second data transmission set. The component carriers of the first group can have a first subcarrier spacing, and the component carriers of the second group can have a second subcarrier spacing, where the first subcarrier spacing and the second subcarrier spacing are different. The subcarrier spacing of component carriers within a group can be the same. In some cases, the first set of one or more fields and the second set of one or more fields share a field indicating a first parameter for a first data transmission set over a first set of component carriers and a second parameter for a second data transmission set over a second set of two or more component carriers. The first parameter can be different from the second parameter. The UE 115-b can receive a configuration message from the base station 105-b indicating the mapping from the shared field to the first parameter and the second parameter. The first parameter and the second parameter can be FDRA parameters, TDRA parameters, or both.

[0142] The UE 115-a can receive a configuration message from the base station 105-b indicating a component carrier group including at least two or more component carriers, where receiving the DCI scheduling the data transmission set is based on receiving the configuration message indicating two or more component carriers. The configuration message can be received before the DCI. In some cases, the base station 105-b can send the configuration message semi-statically, e.g., in an RRC message.

[0143] In some cases, not all the units in a group can be scheduled by each DCI. In such a case, UE115-a may receive an indication of a subset of units (e.g., component carriers, time intervals) from the group, where the subset of units may include two or more component carriers. In some cases, transmitting or receiving a data transmission set over two or more component carriers is based on the indication of the subset of received units. In some implementations, UE 115-a may receive a bitmap indicating two or more component carriers (and / or one or more time intervals) from a group of component carriers (and / or one or more time intervals). In some implementations, UE 115-b may receive an indication of the number of consecutive units (e.g., component carriers, time intervals) from a group of units within the subset of units, where the number of consecutive units may indicate which component carriers and / or time intervals of the group are scheduled. The number of units may be indicated by the RIV field in the DCI. In some cases, UE 115-b may identify which units are scheduled based on an order associated with the RIV field. The order may be a frequency-first order or a time-first order.

[0144] In some cases, UE 115-b may receive a configuration message (e.g., via RRC signaling) indicating a parameter set for each of two or more component carriers or time intervals, where the parameter set for each of the two or more component carriers is the same. Receiving the DCI may be based on receiving the configuration message. In some cases, UE 115-b may receive a configuration message indicating a first parameter set for a first component carrier (and / or a first unit) among two or more component carriers, and UE115-b may identify the parameter sets for the remaining component carriers among the two or more component carriers based on the first parameter set. The first parameter set for the first component carrier and the parameter sets for the remaining component carriers may be the same, and receiving the DCI may be based on receiving the configuration message.

[0145] In some cases, based on receiving the DCI, UE 115-b may identify a first identifier of a first HARQ (e.g., HARQ ID) associated with a data transmission set during a first TTI of a set of TTIs, and increment the first identifier to generate a second identifier for a second HARQ associated with the data transmission set during a second TTI of the set of TTIs. In some implementations, based on receiving the DCI, UE 115-b may identify a first timing parameter (e.g., K0, K2) for transmitting a first HARQ associated with a data transmission set during a first TTI of a set of TTIs, and increment the first timing parameter to generate a second timing parameter for transmitting a second HARQ associated with multiple data transmissions during a second TTI of the set of TTIs.

[0146] At 915, if the DCI schedules an uplink data transmission set, UE 115-b may transmit the data transmission set based on receiving the DCI, over two or more component carriers that are scheduled and / or over one or more time intervals. In some cases, UE 115-a may transmit a second data transmission set over a second component carrier set based on the DCI including a second set of fields that are common to the second component carrier set.

[0147] At 920, if the DCI schedules a downlink data transmission set, UE 115-b may receive the data transmission set based on receiving the DCI over two or more component carriers that are scheduled and / or over one or more time intervals. In some cases, UE 115-a may receive a second data transmission set over a second component carrier set based on the DCI including a second set of fields that are common to the second component carrier set.

[0148] In some cases, UE 115-b may attempt to decode a downlink transmission set of the data transmission set and send acknowledgment information (e.g., ACK / NACK feedback) associated with the downlink transmission set to base station 105-b. The acknowledgment information may include a single bit associated with two or more component carriers, a set of bits each associated with one of two or more component carriers, or a set of bits each associated with a TTI (e.g., time interval, time slot) of one of two or more component carriers.

[0149] Figure 10 FIG. 1000 is a block diagram illustrating a device 1005 that supports DCI for scheduling multiple component carriers, in accordance with aspects of the present disclosure. Device 1005 may be an example of aspects of UE 115 as described herein. Device 1005 may include a receiver 1010, a communication manager 1015, and a transmitter 1020. Device 1005 may also include at least one processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0150] The receiver 1010 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, information related to DCI for scheduling multiple component carriers). The information may be passed to other components of device 1005. The receiver 1010 may be an example of aspects of transceiver 1320 described in Figure 13 reference. The receiver 1010 may utilize a single antenna or an antenna set.

[0151] The communication manager 1015 may: communicate with a base station via a set of component carriers according to a carrier aggregation configuration; receive, based on being connected to the base station, a DCI from the base station, the DCI including one or more fields common to two or more component carriers from the set of component carriers, the DCI scheduling a data transmission set via the two or more component carriers; and transmit or receive the data transmission set via the two or more scheduled component carriers based on receiving the DCI. The communication manager 1015 may be an example of aspects of the communication manager 1310 described herein.

[0152] The communication manager 1015 or its sub-components may be implemented in hardware, code executed by a processor (e.g., software), or any combination thereof. If implemented in code executed by a processor, the functions of the communication manager 1015 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.

[0153] The communication manager 1015 or its sub-components may be physically located in various positions, including being distributed such that portions of the functionality are implemented by one or more physical components in different physical locations. In some examples, the communication manager 1015 or its sub-components may be separate and distinct components in accordance with various aspects of this disclosure. In some examples, in accordance with various aspects of this disclosure, the communication manager 1015 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.

[0154] The transmitter 1020 may transmit signals generated by other components of the device 1005. In some examples, the transmitter 1020 may be collocated with the receiver 1010 in a transceiver module. For example, the transmitter 1020 may be an example of aspects of the transceiver 1320 described in Figure 13 reference. The transmitter 1020 may utilize a single antenna or an antenna set.

[0155] Actions performed by the UE communication manager 1015 described herein may be implemented to achieve one or more potential advantages (e.g., at the modem of the UE 115). One implementation may allow the UE 115 to reduce control signaling overhead by reducing the amount of DCI transmissions required to schedule data transmissions via multiple component carriers. Another implementation may provide improved efficiency and throughput as the number of separate resources for control signaling (e.g., DCI) allocated to the UE 115 may be reduced.

[0156] Figure 11 FIG. 1100 is a block diagram illustrating device 1105 that supports DCI for scheduling multiple component carriers in accordance with aspects of the present disclosure. Device 1105 may be an example of aspects of device 1005 or UE 115 as described herein. Device 1105 may include a receiver 1110, a communication manager 1115, and a transmitter 1130. Device 1105 may also include at least one processor. Each of these components may communicate with one another (e.g., via one or more buses).

[0157] 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, information related to DCI for scheduling multiple component carriers). The information may be passed to other components of device 1105. The receiver 1110 may be an example of aspects of transceiver 1320 described herein. The receiver 1010 may utilize a single antenna or an antenna array. Figure 13 The communication manager 1115 may be an example of aspects of communication manager 1015 described herein. The communication manager 1115 may include a communication manager 1115, a DCI reception manager 1120, and a data transmission manager 1125. The communication manager 1115 may be an example of aspects of communication manager 1310 described herein.

[0158] The communication manager 1115 may communicate with a base station via a set of component carriers according to a carrier aggregation configuration. The DCI reception manager 1120 may receive DCI from the base station based on being connected to the base station, the DCI including one or more fields common to two or more component carriers from the set of component carriers, the DCI scheduling a set of data transmissions via the two or more component carriers. The data transmission manager 1125 may send or receive a set of data transmissions via the two or more component carriers that are scheduled based on the received DCI.

[0159] The transmitter 1130 may send signals generated by other components of device 1105. In some examples, the transmitter 1130 may be collocated with the receiver 1110 in a transceiver module. For example, the transmitter 1130 may be an example of aspects of transceiver 1320 described herein. The transmitter 1130 may utilize a single antenna or an antenna array.

[0160] Figure 13

[0161] Figure 12 ​​FIG. 1200 is a block diagram illustrating a communication manager 1205 that supports DCI for scheduling multiple component carriers in accordance with aspects of the present disclosure. The communication manager 1205 may be an example of aspects of the communication manager 1015, communication manager 1115, or communication manager 1310 described herein. The communication manager 1205 may include a communication manager 1210, a DCI reception manager 1215, a data transmission manager 1220, a component carrier configuration manager 1225, a decoding manager 1230, a feedback manager 1235, and a data transmission parameter manager 1240. Each of these modules may communicate directly or indirectly with one another (e.g., via one or more buses).

[0162] The communication manager 1210 may communicate with a base station via a set of component carriers in accordance with a carrier aggregation configuration. The DCI reception manager 1215 may receive DCI from the base station based on being connected to the base station, the DCI including one or more fields common to two or more component carriers from the set of component carriers, the DCI scheduling a data transmission set via the two or more component carriers. The data transmission manager 1220 may transmit or receive a data transmission set via the two or more component carriers that are scheduled based on the received DCI.

[0163] The component carrier configuration manager 1225 may receive a configuration message from the base station indicating a component carrier group that includes at least two or more component carriers, wherein receiving the DCI that schedules the data transmission set is based on receiving the configuration message indicating the two or more component carriers. In some examples, the component carrier configuration manager 1225 may receive an indication of a subset of component carriers from the component carrier group, the subset of component carriers including two or more component carriers, wherein transmitting or receiving the data transmission set via the two or more component carriers is based on receiving the indication of the subset of component carriers.

[0164] In some examples, the component carrier configuration manager 1225 may receive a bitmap indicating two or more component carriers from the component carrier group. In some examples, the component carrier configuration manager 1225 may receive an indication of a first component carrier from the component carrier group within the subset of component carriers. In some examples, the component carrier configuration manager 1225 may receive an indication of a number of consecutive component carriers from the component carrier group within the subset of component carriers. In some cases, the indication of the subset of component carriers is based on an order of resources associated with the component carrier group. In some cases, the order is a frequency-first order or a time-first order. In some cases, the component carrier group is two or more component carriers.

[0165] In some examples, the component carrier configuration manager 1225 may receive a configuration message indicating a parameter set for each of two or more component carriers, where the parameter set for each of the two or more component carriers is the same, and where receiving DCI is based on receiving the configuration message.

[0166] In some examples, the component carrier configuration manager 1225 may receive a configuration message indicating a first parameter set for a first component carrier of two or more component carriers. In some examples, the component carrier configuration manager 1225 may identify a parameter set for the remaining component carriers of the two or more component carriers based on the first parameter set, where the first parameter set for the first component carrier and the parameter set for the remaining component carriers are the same, and where receiving DCI is based on receiving the configuration message.

[0167] The decoding manager 1230 may attempt to decode a downlink transmission set of a data transmission set. The feedback manager 1235 may send acknowledgment information associated with the downlink transmission set to the base station, where the acknowledgment information includes a single bit associated with two or more component carriers, a set of bits each associated with one of the two or more component carriers, or a set of bits each associated with the TTI of one of the two or more component carriers.

[0168] In some cases, DCI schedules a data transmission set over two or more component carriers for a set of TTIs. The data transmission parameter manager 1240 may, based on receiving the DCI, identify a first identifier of a first HARQ associated with the data transmission set during a first TTI of the set of TTIs. In some examples, the data transmission parameter manager 1240 may increment the first identifier to generate a second identifier of a second HARQ associated with the data transmission set during a second TTI of the set of TTIs. In some examples, the data transmission parameter manager 1240 may, based on receiving the DCI, identify a first timing parameter for transmitting a first HARQ associated with the data transmission set during a first TTI of the set of TTIs. In some examples, the data transmission parameter manager 1240 may increment the first timing parameter to generate a second timing parameter for transmitting a second HARQ associated with the data transmission set during a second TTI of the set of TTIs.

[0169] In some cases, the two or more component carriers are a first set of component carriers. In some cases, one or more fields common to the first set of component carriers are a first set of one or more fields. In some cases, a data transmission set over the first set of component carriers is a first data transmission set. In some cases, the DCI includes a second set of one or more fields common to a second set of two or more component carriers. In some cases, the DCI schedules a second data transmission set over the second set of two or more component carriers.

[0170] In some examples, the data transmission parameter manager 1220 may send or receive a second data transmission set via a second set of two or more component carriers based on receiving DCI that includes a second set of one or more fields common to the second set of two or more component carriers.

[0171] In some cases, the first set of one or more fields and the second set of one or more fields share a field indicating a first parameter for a first data transmission set via a first component carrier set and a second parameter for a second data transmission set via a second set of two or more component carriers. In some cases, the first parameter is different from the second parameter.

[0172] In some examples, the component carrier configuration manager 1225 may receive a configuration message from a base station indicating a mapping from a common field to the first parameter and the second parameter. In some cases, the first parameter and the second parameter are FDRA parameters, TDRA parameters, or both.

[0173] In some cases, a first component carrier among two or more component carriers has a first subcarrier spacing. In some cases, a second component carrier among two or more component carriers has a second subcarrier spacing different from the first subcarrier spacing.

[0174] Figure 13 FIG. shows a system 1300 including a device 1305 that supports DCI for scheduling multiple component carriers, in accordance with aspects of the present disclosure. The device 1305 may be an example of the device 1005, the device 1105, or the UE 115 described herein or include components thereof. The device 1305 may include components for two-way voice and data communication, including components for sending and receiving communications, including a communication manager 1310, an I / O controller 1315, a transceiver 1320, an antenna 1325, a memory 1330, and a processor 1340. These components may communicate electronically via one or more buses (e.g., bus 1345).

[0175] The communication manager 1310 may: communicate with a base station via a set of component carriers according to a carrier aggregation configuration; receive, based on being connected to the base station, DCI that includes one or more fields common to two or more component carriers from the set of component carriers, the DCI scheduling a data transmission set via the two or more component carriers; and send or receive a data transmission set via the two or more scheduled component carriers based on receiving the DCI.

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

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

[0178] In some cases, a wireless device may include a single antenna 1325. However, in some cases, the device may have more than one antenna 1325 capable of simultaneously transmitting or receiving multiple wireless transmissions.

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

[0180] The processor 1340 may include hardware devices (e.g., a general-purpose processor, DSP, CPU, microcontroller, ASIC, FPGA, programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, the processor 1340 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into the processor 1340. The processor 1340 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1330) to cause the device 1305 to perform various functions (e.g., functions or tasks supporting DCI for scheduling multiple component carriers).

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

[0182] Actions performed by the UE communication manager 1310 described herein may be implemented to achieve one or more potential advantages (e.g., at the handset of the UE 115). One implementation may avoid having to receive multiple DCI transmissions in order to schedule data transmissions over multiple component carriers, allowing the UE 115 to conserve power and extend battery life. Additionally, the throughput and efficiency associated with the UE 115 may increase due to a reduction in signaling overhead (e.g., a reduction in DCI signaling).

[0183] Figure 14 Block diagram 1400 illustrates a device 1405 in accordance with aspects of the present disclosure that supports DCI for scheduling multiple component carriers. Device 1405 may be an example of aspects of the base station 105 as described herein. Device 1405 may include a receiver 1410, a communication manager 1415, and a transmitter 1420. Device 1405 may also include at least one processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0184] The receiver 1410 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, information related to DCI for scheduling multiple component carriers). The information may be passed to other components of the device 1405. The receiver 1410 may be an example of aspects of the transceiver 1720 described Figure 17 herein. The receiver 1410 may utilize a single antenna or an antenna set.

[0185] The communication manager 1415 may: communicate with a UE over a set of component carriers according to a carrier aggregation configuration; send DCI to the UE based on a connection with the UE, the DCI including one or more fields common to two or more component carriers from the set of component carriers, the DCI scheduling a set of data transmissions over the two or more component carriers; and send or receive a set of data transmissions over the two or more component carriers that are scheduled based on the sent DCI. The communication manager 1415 may be an example of aspects of the communication manager 1710 described herein.

[0186] The communication manager 1415 or its subcomponents may be implemented in hardware, code executed by a processor (e.g., software), or any combination thereof. If implemented in code executed by a processor, the functions of the communication manager 1415 or its subcomponents may be performed by a general-purpose processor, a DSP, an ASIC, an 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.

[0187] The communication manager 1415 or its subcomponents may physically be located in various positions, including being distributed such that portions of the functionality are implemented by one or more physical components in different physical locations. In some examples, the communication manager 1415 or its subcomponents may be separate and distinct components in accordance with various aspects of this disclosure. In some examples, in accordance with various aspects of this disclosure, the communication manager 1415 or its subcomponents 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.

[0188] The transmitter 1420 may transmit signals generated by other components of the device 1405. In some examples, the transmitter 1420 may be collocated with the receiver 1410 in a transceiver module. For example, the transmitter 1420 may be an example of aspects of the transceiver 1720 described in Figure 17 reference. The transmitter 1420 may utilize a single antenna or an antenna set.

[0189] In some cases, actions performed by the communication manager 1415 may be implemented to achieve one or more potential advantages. One implementation may avoid having to receive multiple DCI transmissions in order to schedule data transmissions over multiple component carriers, thereby allowing the base station 105 to conserve power and extend battery life. Another implementation may provide improved throughput and efficiency because of reduced signaling overhead associated with scheduling data transmissions over multiple component carriers.

[0190] Figure 15 Block diagram 1500 illustrates a device 1505 in accordance with various aspects of this disclosure that supports DCI for scheduling multiple component carriers. The device 1505 may be an example of aspects of the device 1405 or the base station 105 as described herein. The device 1505 may include a receiver 1510, a communication manager 1515, and a transmitter 1535. The device 1505 may also include at least one processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0191] The receiver 1510 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, information related to DCI for scheduling multiple component carriers). The information may be passed to other components of the device 1505. The receiver 1510 may be an example of aspects of the transceiver 1720 described in reference Figure 17 and may utilize a single antenna or an antenna set.

[0192] The communication manager 1515 may be an example of aspects of the communication manager 1415 described herein. The communication manager 1515 may include a communication component 1520, a DCI transmission component 1525, and a data transmission component 1530. The communication manager 1515 may be an example of aspects of the communication manager 1710 described herein.

[0193] The communication component 1520 may communicate with a UE via a set of component carriers according to a carrier aggregation configuration. The DCI transmission component 1525 may send DCI to the UE based on a connection with the UE, the DCI including one or more fields common to two or more component carriers from the set of component carriers, and the DCI schedules a set of data transmissions via the two or more component carriers. The data transmission component 1530 may send or receive a set of data transmissions via the two or more scheduled component carriers based on sending the DCI.

[0194] The transmitter 1535 may send signals generated by other components of the device 1505. In some examples, the transmitter 1535 may be collocated with the receiver 1510 in a transceiver module. For example, the transmitter 1535 may be an example of aspects of the transceiver 1720 described in reference Figure 17 and may utilize a single antenna or an antenna set.

[0195] Figure 16 Block diagram 1600 illustrates a communication manager 1605 supporting DCI for scheduling multiple component carriers in accordance with aspects of the present disclosure. The communication manager 1605 may be an example of aspects of the communication manager 1415, the communication manager 1515, or the communication manager 1710 described herein. The communication manager 1605 may include a communication component 1610, a DCI transmission component 1615, a data transmission component 1620, a component carrier configuration component 1625, and a feedback reception component 1630. Each of these modules may communicate directly or indirectly with each other (e.g., via one or more buses).

[0196] The communication manager 1610 may communicate with the UE via a set of component carriers according to a carrier aggregation configuration. The DCI transmission component 1615 may send DCI to the UE based on the connection with the UE, where the DCI includes one or more fields common to two or more component carriers from the set of component carriers, and the DCI schedules a data transmission set via two or more component carriers. The data transmission component 1620 may send or receive a data transmission set via two or more scheduled component carriers based on the sent DCI.

[0197] The component carrier configuration component 1625 may send a configuration message to the UE indicating a component carrier group including at least two or more component carriers, where the DCI for scheduling the data transmission set is based on the sent configuration message indicating two or more component carriers. In some examples, the component carrier configuration component 1625 may send an indication of a subset of component carriers from the component carrier group, where the subset of component carriers includes two or more component carriers, and where sending or receiving the data transmission set via two or more component carriers is based on the sent indication of the subset of component carriers.

[0198] In some examples, the component carrier configuration component 1625 may send a bitmap indicating two or more component carriers from the component carrier group. In some examples, the component carrier configuration component 1625 may send an indication of a first component carrier from the component carrier group within the subset of component carriers. In some examples, the component carrier configuration component 1625 may send an indication of the number of consecutive component carriers from the component carrier group within the subset of component carriers.

[0199] In some cases, the indication of the subset of component carriers is based on the order of resources associated with the component carrier group. In some cases, the order is a frequency-first order or a time-first order. In some cases, the component carrier group is two or more component carriers.

[0200] In some examples, the component carrier configuration component 1625 may send a configuration message indicating a parameter set for each of two or more component carriers, where the parameter set for each of the two or more component carriers is the same, and where sending the DCI is based on the sent configuration message. In some examples, the component carrier configuration component 1625 may send a configuration message indicating a first parameter set for a first component carrier among two or more component carriers, where the first parameter set for the first component carrier and the parameter sets for the remaining component carriers among the two or more component carriers are the same, and where sending the DCI is based on the sent configuration message.

[0201] The feedback receiving component 1630 may receive, from the UE, acknowledgement information associated with a downlink transmission set from a data transmission set, where the acknowledgement information includes a single bit associated with two or more component carriers, a set of bits each associated with one of two or more component carriers, or a set of bits each associated with a TTI of one of two or more component carriers.

[0202] In some cases, the DCI schedules a data transmission set over two or more component carriers for a set of TTIs.

[0203] In some cases, the two or more component carriers are a first set of component carriers. In some cases, one or more fields common to the first set of component carriers are a first set of one or more fields. In some cases, a data transmission set over the first set of component carriers is a first data transmission set. In some cases, the DCI includes a second set of one or more fields common to a second set of two or more component carriers. In some cases, the DCI schedules a second data transmission set over the second set of two or more component carriers.

[0204] In some examples, the data transmission component 1620 may send or receive a second data transmission set over a second set of two or more component carriers based on sending the DCI that includes a second set of one or more fields common to the second set of two or more component carriers.

[0205] In some cases, the first set of one or more fields and the second set of one or more fields share a field indicating a first parameter for the first data transmission set over the first set of component carriers and a second parameter for the second data transmission set over the second set of two or more component carriers. In some cases, the first parameter is different from the second parameter.

[0206] In some examples, the component carrier configuration component 1625 may send a configuration message to the UE indicating a mapping from the shared field to the first parameter and the second parameter. In some cases, the first parameter and the second parameter are FDRA parameters, TDRA parameters, or both. In some cases, a first component carrier of the two or more component carriers has a first subcarrier spacing. In some cases, a second component carrier of the two or more component carriers has a second subcarrier spacing different from the first subcarrier spacing.

[0207] Figure 17FIG. shows a system 1700 including a device 1705 that supports DCI for scheduling multiple component carriers, in accordance with aspects of the present disclosure. Device 1705 may be an example of, or include components of, device 1405, device 1505, or base station 105 as described herein. Device 1705 may include components for two-way voice and data communication, including components for sending and receiving communication, including communication manager 1710, network communication manager 1715, transceiver 1720, antenna 1725, memory 1730, processor 1740, and inter-station communication manager 1745. These components may communicate electronically via one or more buses (e.g., bus 1750).

[0208] The communication manager 1710 may: communicate with a UE via a set of component carriers according to a carrier aggregation configuration; based on being connected to the UE, send DCI to the UE, the DCI including one or more fields common to two or more component carriers from the set of component carriers, the DCI scheduling a data transmission set via the two or more component carriers; and based on sending the DCI, send or receive a data transmission set via the two or more scheduled component carriers.

[0209] The network communication manager 1715 may manage communication with a core network (e.g., via one or more wired backhaul links). For example, the network communication manager 1715 may manage data communication conveyance of client devices such as one or more UEs 115.

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

[0211] In some cases, a wireless device may include a single antenna 1725. However, in some cases, the device may have more than one antenna 1725 that is capable of simultaneously sending or receiving multiple wireless transmissions.

[0212] The memory 1730 may include RAM, ROM, or a combination thereof. The memory 1730 may store computer-readable code 1735 including instructions that, when executed by at least one processor (e.g., processor 1740), cause the device to perform various functions described herein. In some cases, the memory 1730 may particularly include a BIOS that may control basic hardware or software operations, such as interacting with peripheral components or devices.

[0213] The processor 1740 may include hardware devices (e.g., a general-purpose processor, DSP, CPU, microcontroller, ASIC, FPGA, programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, the processor 1740 may be configured to operate a memory array using a memory controller. In some cases, the memory controller may be integrated into the processor 1740. The processor 1740 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1730) to cause the device 1705 to perform various functions (e.g., functions or tasks supporting DCI for scheduling multiple component carriers).

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

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

[0216] Figure 18 A flowchart illustrating a method 1800 for supporting DCI for scheduling multiple component carriers in accordance with aspects of the present disclosure is shown. The operations of method 1800 may be implemented by the UE 115 or its components as described herein. For example, the operations of method 1800 may be performed by the communication manager described with reference to Figures 10 to 13 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.

[0217] At 1805, the UE may communicate with a base station via a set of component carriers according to a carrier aggregation configuration.

[0218] The operation of 1805 may be performed according to the methods described herein. In some examples, aspects of the operation of 1805 may be performed by the communication manager described with reference to Figures 10 to 13 as described.

[0219] At 1810, the UE may receive DCI from the base station at least in part based on being connected to the base station, the DCI including one or more fields common to two or more component carriers from a set of component carriers, the DCI scheduling multiple data transmissions over two or more component carriers. The operation of 1810 may be performed according to the methods described herein. In some examples, aspects of the operation of 1810 may be performed by a DCI reception manager as described in reference to Figures 10 to 13 that which is described.

[0220] At 1815, the UE may transmit or receive multiple data transmissions over two or more component carriers that are scheduled at least in part based on receiving the DCI. The operation of 1815 may be performed according to the methods described herein. In some examples, aspects of the operation of 1815 may be performed by a data transmission manager as described in reference to Figures 10 to 13 that which is described.

[0221] Figure 19 A flowchart illustrating a method 1900 for supporting DCI for scheduling multiple component carriers in accordance with aspects of the present disclosure is shown. The operations of method 1900 may be implemented by a UE 115 or its components as described herein. For example, the operations of method 1900 may be performed by a communication manager as described in reference to Figures 10 to 13 that which is 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.

[0222] At 1905, the UE may receive a configuration message from the base station indicating a set of component carriers including at least two or more component carriers, wherein receiving the DCI scheduling multiple data transmissions is at least in part based on receiving the configuration message indicating two or more component carriers. 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 component carrier configuration manager as described in reference to Figures 10 to 13 that which is described.

[0223] At 1910, the UE may communicate with the base station over a set of component carriers according to a carrier aggregation configuration.

[0224] 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 communication manager as described in reference to Figures 10 to 13 that which is described.

[0225] At 1915, the UE may receive DCI from a base station at least in part based on being connected to the base station, the DCI including one or more fields common to two or more component carriers from a set of component carriers, the DCI scheduling multiple data transmissions over the two or more component carriers. 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 DCI reception manager as referenced Figures 10 to 13 as described.

[0226] At 1920, the UE may transmit or receive multiple data transmissions over two or more component carriers that are scheduled at least in part based on receiving the DCI. 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 data transmission manager as referenced Figures 10 to 13 as described.

[0227] Figure 20 FIG. 2000 is a flow diagram illustrating a method 2000 in accordance with aspects of the present disclosure for supporting DCI for scheduling multiple component carriers. The operations of method 2000 may be implemented by a base station 105 or components thereof as described herein. For example, the operations of method 2000 may be performed by a communication manager as referenced Figures 14 to 17 as described. In some examples, the base station may execute an instruction set to control 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.

[0228] At 2005, the base station may communicate with the UE over a set of component carriers according to a carrier aggregation configuration. The operation of 2005 may be performed according to the methods described herein. In some examples, aspects of the operation of 2005 may be performed by a communication manager as referenced Figures 14 to 17 as described.

[0229] At 2010, the base station may transmit DCI to the UE at least in part based on being connected to the UE, the DCI including one or more fields common to two or more component carriers from a set of component carriers, the DCI scheduling multiple data transmissions over the two or more component carriers. The operation of 2010 may be performed according to the methods described herein. In some examples, aspects of the operation of 2010 may be performed by a DCI transmission component as referenced Figures 14 to 17 as described.

[0230] At 2015, the base station may transmit or receive multiple data transmissions over two or more component carriers that are scheduled at least in part based on transmitting the DCI. The operation of 2015 may be performed according to the methods described herein. In some examples, aspects of the operation of 2015 may be performed by a data transmission component as referenced Figures 14 to 17performed by the data transmission component described above.

[0231] Figure 21 FIG. 2100 is a flow chart showing a method for supporting DCI for scheduling multiple component carriers in accordance with aspects of the present disclosure. The operations of method 2100 may be implemented by a base station 105 or its components as described herein. For example, the operations of method 2100 may be performed by a communication manager as referenced Figures 14 to 17 above. 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.

[0232] At 2105, the base station may transmit a configuration message indicating a parameter set for each of two or more component carriers, wherein the parameter set for each of the two or more component carriers is the same, and wherein transmitting the DCI is at least partially based on transmitting the configuration message. The operation of 2105 may be performed according to the methods described herein. In some examples, aspects of the operation of 2105 may be performed by a component carrier configuration component as referenced Figures 14 to 17 above.

[0233] At 2110, the base station may communicate with a UE via a set of component carriers according to a carrier aggregation configuration. The operation of 2110 may be performed according to the methods described herein. In some examples, aspects of the operation of 2110 may be performed by a communication component as referenced Figures 14 to 17 above.

[0234] At 2115, the base station may transmit DCI to the UE at least partially based on the connection to the UE, the DCI including one or more fields common to two or more component carriers from the set of component carriers, the DCI scheduling multiple data transmissions via the two or more component carriers. The operation of 2115 may be performed according to the methods described herein. In some examples, aspects of the operation of 2115 may be performed by a DCI transmission component as referenced Figures 14 to 17 above.

[0235] At 2120, the base station may transmit or receive multiple data transmissions via two or more component carriers that are scheduled, at least partially based on transmitting the DCI. The operation of 2120 may be performed according to the methods described herein. In some examples, aspects of the operation of 2120 may be performed by a data transmission component as referenced Figures 14 to 17 above.

[0236] The following provides an overview of aspects of the present disclosure:

[0237] Aspect 1: A method for wireless communication, comprising: communicating with a base station via a set of component carriers according to a carrier aggregation configuration; receiving downlink control information from the base station at least in part based on being connected to the base station, the downlink control information including one or more fields common to two or more component carriers from the set of component carriers, the downlink control information scheduling a plurality of data transmissions via the two or more component carriers; and transmitting or receiving a plurality of data transmissions via the two or more scheduled component carriers at least in part based on receiving the downlink control information.

[0238] Aspect 2: The method according to aspect 1, further comprising: receiving, from the base station, a configuration message indicating a component carrier group including at least two or more component carriers, wherein receiving the downlink control information scheduling a plurality of data transmissions is at least in part based on receiving the configuration message indicating two or more component carriers.

[0239] Aspect 3: The method according to aspect 2, wherein receiving the downlink control information comprises: receiving an indication of a subset of component carriers from the component carrier group, the subset of component carriers including two or more component carriers, wherein transmitting or receiving a plurality of data transmissions via the two or more component carriers is at least in part based on receiving the indication of the subset of component carriers.

[0240] Aspect 4: The method according to aspect 3, wherein receiving the indication of the subset of component carriers comprises: receiving a bitmap indicating two or more component carriers from the component carrier group.

[0241] Aspect 5: The method according to any one of aspects 3 to 4, wherein receiving the indication of the subset of component carriers comprises: within the subset of component carriers, receiving an indication of a first component carrier from the component carrier group; and within the subset of component carriers, receiving an indication of the number of consecutive component carriers from the component carrier group.

[0242] Aspect 6: The method according to any one of aspects 3 to 5, wherein the indication of the subset of component carriers is at least in part based on an order of resources associated with the component carrier group; and the order is a frequency-first order or a time-first order.

[0243] Aspect 7: The method according to any one of aspects 2 to 6, wherein the component carrier group is two or more component carriers.

[0244] Aspect 8: The method according to any one of aspects 1 to 7, further comprising: receiving a configuration message indicating a parameter set for each of two or more component carriers, wherein the parameter set for each of the two or more component carriers is the same, and wherein receiving the downlink control information is at least in part based on receiving the configuration message.

[0245] Aspect 9: The method according to any one of Aspects 1 to 8 further comprises: receiving a configuration message indicating a first parameter set for a first component carrier among two or more component carriers; and identifying, at least in part based on the first parameter set, parameter sets for the remaining component carriers among the two or more component carriers, wherein the first parameter set for the first component carrier and the parameter sets for the remaining component carriers are the same, and wherein receiving the downlink control information is at least in part based on receiving the configuration message.

[0246] Aspect 10: The method according to any one of Aspects 1 to 9 further comprises: attempting to decode a downlink transmission set of a plurality of data transmissions; and sending to a base station acknowledgment information associated with the downlink transmission set, wherein the acknowledgment information comprises a single bit associated with two or more component carriers, a set of bits each associated with one of the two or more component carriers, or a set of bits each associated with a transmission time interval of one of the two or more component carriers.

[0247] Aspect 11: The method according to any one of Aspects 1 to 10, wherein the downlink control information schedules a plurality of data transmissions via two or more component carriers for a plurality of transmission time intervals.

[0248] Aspect 12: The method according to Aspect 11 further comprises: identifying, at least in part based on receiving the downlink control information, a first identifier for a first hybrid automatic repeat request associated with a plurality of data transmissions during a first transmission time interval of the plurality of transmission time intervals; and incrementing the first identifier to generate a second identifier for a second hybrid automatic repeat request associated with the plurality of data transmissions during a second transmission time interval of the plurality of transmission time intervals.

[0249] Aspect 13: The method according to any one of Aspects 11 to 12 further comprises: identifying, at least in part based on receiving the downlink control information, a first timing parameter for sending a first hybrid automatic repeat request associated with a plurality of data transmissions during a first transmission time interval of the plurality of transmission time intervals; and incrementing the first timing parameter to generate a second timing parameter for sending a second hybrid automatic repeat request associated with the plurality of data transmissions during a second transmission time interval of the plurality of transmission time intervals.

[0250] Aspect 14: The method according to any one of Aspects 1 to 13, wherein two or more component carriers are a first set of component carriers; one or more fields that are common to the first set of component carriers are a first set of one or more fields; a plurality of data transmissions through the first set of component carriers are a first plurality of data transmissions; the downlink control information includes a second set of one or more fields that are common to a second two or more component carriers; and the downlink control information schedules a second plurality of data transmissions through the second two or more component carriers.

[0251] Aspect 15: The method according to Aspect 14, further comprising: transmitting or receiving a second plurality of data transmissions through the second two or more component carriers at least in part based on receiving the downlink control information, the downlink control information including a second set of one or more fields that are common to the second two or more component carriers.

[0252] Aspect 16: The method according to any one of Aspects 14 to 15, wherein the first set of one or more fields and the second set of one or more fields share a field indicating a first parameter for the first plurality of data transmissions through the first set of component carriers and a second parameter for the second plurality of data transmissions through the second two or more component carriers; and the first parameter is different from the second parameter.

[0253] Aspect 17: The method according to Aspect 16, further comprising: receiving, from a base station, a configuration message indicating a mapping from the shared field to the first parameter and the second parameter.

[0254] Aspect 18: The first parameter and the second parameter are frequency domain resource allocation parameters, time domain resource allocation parameters, or both.

[0255] Aspect 19: The method according to any one of Aspects 1 to 18, wherein a first component carrier among the two or more component carriers has a first subcarrier spacing; and a second component carrier among the two or more component carriers has a second subcarrier spacing different from the first subcarrier spacing.

[0256] Aspect 20: A method for wireless communication, comprising: communicating with a UE through a set of component carriers according to a carrier aggregation configuration; transmitting downlink control information to the UE at least in part based on being connected to the UE, the downlink control information including one or more fields that are common to two or more component carriers from the set of component carriers, the downlink control information scheduling a plurality of data transmissions through the two or more component carriers; and transmitting or receiving a plurality of data transmissions through the scheduled two or more component carriers at least in part based on transmitting the downlink control information.

[0257] Aspect 21: The method according to aspect 10 further includes: sending a configuration message to the UE indicating a component carrier group including at least two or more component carriers, wherein sending downlink control information for scheduling a plurality of data transmissions is at least partially based on sending a configuration message indicating two or more component carriers.

[0258] Aspect 22: The method according to aspect 21, wherein sending the downlink control information includes: sending an indication of a subset of component carriers from the component carrier group, the subset of component carriers including two or more component carriers, wherein sending or receiving a plurality of data transmissions via the two or more component carriers is at least partially based on sending the indication of the subset of component carriers.

[0259] Aspect 23: The method according to aspect 22, wherein sending the indication of the subset of component carriers includes: sending a bitmap indicating two or more component carriers from the component carrier group.

[0260] Aspect 24: The method according to any one of aspects 22 to 23, wherein sending the indication of the subset of component carriers includes: within the subset of component carriers, sending an indication of a first component carrier from the component carrier group; and within the subset of component carriers, sending an indication of the number of consecutive component carriers from the component carrier group.

[0261] Aspect 25: The method according to any one of aspects 22 to 24, wherein the indication of the subset of component carriers is at least partially based on the order of resources associated with the component carrier group; and the order is a frequency-first order or a time-first order.

[0262] Aspect 26: The method according to any one of aspects 21 to 25, wherein the component carrier group is two or more component carriers.

[0263] Aspect 27: The method according to any one of aspects 20 to 26 further includes: sending a configuration message indicating a parameter set for each of two or more component carriers, wherein the parameter set for each of the two or more component carriers is the same, and wherein sending the downlink control information is at least partially based on sending the configuration message.

[0264] Aspect 28: The method according to any one of aspects 20 to 27 further includes: sending a configuration message indicating a first parameter set for a first component carrier among two or more component carriers, wherein the first parameter set for the first component carrier among the two or more component carriers and the parameter sets for the remaining component carriers are the same, and wherein sending the downlink control information is at least partially based on sending the configuration message.

[0265] Aspect 29: The method according to any one of aspects 20 to 28 further comprises: receiving, from a UE, acknowledgement information associated with a downlink transmission set from a plurality of data transmissions, wherein the acknowledgement information comprises a single bit associated with two or more component carriers, a set of bits each associated with one of two or more component carriers, or a set of bits each associated with a transmission time interval of one of two or more component carriers.

[0266] Aspect 30: The method according to any one of aspects 20 to 29, wherein downlink control information schedules a plurality of data transmissions over two or more component carriers for a plurality of transmission time intervals.

[0267] Aspect 31: The method according to any one of aspects 20 to 30, wherein the two or more component carriers are a first set of component carriers; one or more fields common to the first set of component carriers are a first set of one or more fields; a plurality of data transmissions over the first set of component carriers are a first plurality of data transmissions; downlink control information comprises a second set of one or more fields common to a second two or more component carriers; and the downlink control information schedules a second plurality of data transmissions over the second two or more component carriers.

[0268] Aspect 32: The method according to aspect 31, further comprising: transmitting or receiving, over the second two or more component carriers, the second plurality of data transmissions, at least in part based on transmitting the downlink control information, the downlink control information comprising the second set of one or more fields common to the second two or more component carriers.

[0269] Aspect 33: The method according to any one of aspects 31 to 32, wherein the first set of one or more fields and the second set of one or more fields share a field indicating a first parameter for the first plurality of data transmissions over the first set of component carriers and a second parameter for the second plurality of data transmissions over the second two or more component carriers; and the first parameter is different from the second parameter.

[0270] Aspect 34: The method according to aspect 33, further comprising: sending a configuration message to the UE indicating a mapping from the shared field to the first parameter and the second parameter.

[0271] Aspect 35: The method according to any one of aspects 33 to 34, wherein the first parameter and the second parameter are frequency domain resource allocation parameters, time domain resource allocation parameters, or both.

[0272] Aspect 36: The method according to any one of aspects 20 to 35, wherein a first component carrier of the two or more component carriers has a first subcarrier spacing; and a second component carrier of the two or more component carriers has a second subcarrier spacing different from the first subcarrier spacing.

[0273] Aspect 37: An apparatus for wireless communication, comprising at least one processor; a memory coupled to the at least one processor; and instructions that are stored in the memory and executable by the at least one processor to cause the apparatus to perform the method according to any one of Aspects 1 to 19.

[0274] Aspect 38: An apparatus for wireless communication, comprising at least one component for performing the method according to any one of Aspects 1 to 19.

[0275] Aspect 39: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by at least one processor to perform the method according to any one of Aspects 1 to 19.

[0276] Aspect 40: An apparatus for wireless communication, comprising at least one processor; a memory coupled to the at least one processor; and instructions that are stored in the memory and executable by the at least one processor to cause the apparatus to perform the method according to any one of Aspects 20 to 36.

[0277] Aspect 41: An apparatus for wireless communication, comprising at least one component for performing the method according to any one of Aspects 20 to 36.

[0278] Aspect 42: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by at least one processor to perform the method according to any one of Aspects 20 to 36.

[0279] 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. In addition, aspects from two or more methods may be combined.

[0280] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems are described for purposes of illustration, and the LTE, LTE-A, LTE-A Pro, or NR terms are used in most of the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the 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.

[0281] The information and signals described herein can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips (chip) that may be referred to throughout the specification can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0282] The various illustrative blocks and components described in connection with the disclosure herein can be implemented or performed using 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. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in combination with a DSP core, or any other such configuration).

[0283] The functions described herein can be implemented in hardware, software executed by a processor, or any combination thereof. Whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise, software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable programs, execution threads, processes, or functions. If implemented in software executed by a processor, the functions can be stored on or transmitted through 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, hardwiring, or any combination thereof. The features implementing the functions can also be physically located in various positions, including being distributed such that parts of the functions are implemented at different physical locations.

[0284] Computer-readable media includes two types: non-transitory computer storage media and communication media. Communication media includes any medium that facilitates the transfer of a computer program from one place to another. Non-transitory storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer. By way of example and not limitation, non-transitory computer-readable media can include RAM, ROM, electrically erasable programmable read-only memory (EEPROM), flash memory, compact disc (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 components 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 optical disc include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc, where disks typically reproduce data magnetically, while optical discs reproduce data optically by laser. Combinations of the above items are also included within the scope of computer-readable media.

[0285] As used herein (including in the claims), the "or" as used in a list of items (e.g., a list that begins with phrases such as "at least one of..." or "one or more of...") indicates an inclusive list, such that a list of at least one of A, B, or C, for example, 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 exemplary 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". As used herein, the term "and / or" when used in a list of two or more items means that any one of the listed items can be taken alone, or any combination of two or more of the listed items can be taken. For example, if a composition is described as containing components A, B, and / or C, then the composition can contain only A; only B; only C; a combination of A and B; a combination of A and C; a combination of B and C; or a combination of A, B, and C.

[0286] In the accompanying drawings, like components or features may have the same reference label. Additionally, various components of the same type can be distinguished by following the reference label with a dash and a second label that differentiates the similar components. If only the first reference label is used in the specification, the description applies to any one of the similar components having the same first reference label, regardless of the second reference label or any other subsequent reference labels.

[0287] The description set forth herein in connection with the accompanying drawings describes example configurations and does not represent all 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 "superior to other examples". The detailed description includes specific details to provide an understanding of the described techniques. However, the techniques may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

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

Claims

1. A method for wireless communication, comprising: receiving, from a network entity, a configuration message indicating a component carrier group, the component carrier group including a set of component carriers of at least two or more component carriers, wherein the set of component carriers is according to a carrier aggregation configuration; communicating with the network entity via the set of component carriers according to the carrier aggregation configuration; receiving downlink control information from the network entity, at least in part based on being connected to the network entity, the downlink control information including one or more fields common to the two or more component carriers, the downlink control information scheduling a plurality of data transmissions via the two or more component carriers, wherein receiving the downlink control information scheduling the plurality of data transmissions is at least in part based on receiving the configuration message indicating the two or more component carriers, and wherein receiving the downlink control information includes: receiving an indication from a subset of component carriers of the component carrier group, the subset of component carriers including the two or more component carriers; and transmitting or receiving the plurality of data transmissions via the two or more component carriers, at least in part based on receiving the downlink control information, wherein transmitting or receiving the plurality of data transmissions via the two or more component carriers is at least in part based on receiving the indication of the subset of component carriers.

2. The method according to claim 1, further comprising: receiving a configuration message indicating a parameter set for each of the two or more component carriers, wherein the parameter set for each of the two or more component carriers is the same, and wherein receiving the downlink control information is at least in part based on receiving the configuration message.

3. The method according to claim 1, further comprising: receiving a configuration message indicating a first parameter set for a first component carrier of the two or more component carriers; and identifying, at least in part based on the first parameter set, a parameter set for remaining component carriers of the two or more component carriers, wherein the first parameter set for the first component carrier and the parameter set for the remaining component carriers are the same, and wherein receiving the downlink control information is at least in part based on receiving the configuration message.

4. The method according to claim 1, further comprising: attempting to decode a downlink transmission set of the plurality of data transmissions; and sending, to the network entity, acknowledgment information associated with the downlink transmission set, wherein the acknowledgment information includes a single bit associated with the two or more component carriers, a set of bits each associated with one of the two or more component carriers, or a set of bits each associated with a transmission time interval of one of the two or more component carriers.

5. The method according to claim 1, wherein the downlink control information schedules the plurality of data transmissions via the two or more component carriers for a plurality of transmission time intervals, the method further comprising: Identify, during a first transmission time interval of the plurality of transmission time intervals, a first identifier for a first hybrid automatic repeat request associated with the plurality of data transmissions, at least in part based on receiving the downlink control information; And Increment the first identifier to generate a second identifier for a second hybrid automatic repeat request associated with the plurality of data transmissions during a second transmission time interval of the plurality of transmission time intervals.

6. The method according to claim 1, wherein the downlink control information schedules the plurality of data transmissions via the two or more component carriers for a plurality of transmission time intervals, and the method further Comprises: Identify, during a first transmission time interval of the plurality of transmission time intervals, a first timing parameter for transmitting a first hybrid automatic repeat request associated with the plurality of data transmissions, at least in part based on receiving the downlink control information; And Increment the first timing parameter to generate a second timing parameter for transmitting a second hybrid automatic repeat request associated with the plurality of data transmissions during a second transmission time interval of the plurality of transmission time intervals.

7. The method according to claim 1, Wherein: The two or more component carriers are a first set of component carriers; The one or more fields that are common to the first set of component carriers are a first set of one or more fields; The plurality of data transmissions via the first set of component carriers are a first plurality of data transmissions; The downlink control information includes a second set of one or more fields that are common to a second two or more component carrier sets; and The downlink control information schedules a second plurality of data transmissions via the second two or more component carrier sets.

8. A method for wireless communication, Comprises: Send a configuration message indicating a component carrier group to a user equipment UE, the component carrier group comprising a set of component carriers of at least two or more component carriers, wherein the set of component carriers is according to a carrier aggregation configuration; Communicate with the UE via the set of component carriers according to the carrier aggregation configuration; Send downlink control information to the UE at least in part based on being connected to the UE, the downlink control information including one or more fields common to the two or more component carriers, the downlink control information scheduling a plurality of data transmissions via the two or more component carriers, wherein sending the downlink control information scheduling the plurality of data transmissions is at least in part based on sending the configuration message indicating the two or more component carriers, and wherein sending the downlink control information comprises: Send an indication of a subset of component carriers from the component carrier group, the subset of component carriers comprising the two or more component carriers; And Send or receive the plurality of data transmissions via the two or more scheduled component carriers at least in part based on sending the downlink control information, wherein sending or receiving the plurality of data transmissions via the two or more component carriers is at least in part based on sending the indication of the subset of component carriers.

9. A device for wireless communication, comprising: at least one processor; a memory coupled to the at least one processor; and instructions stored in the memory and executable by the at least one processor to cause the device to: receive, from a network entity, a configuration message indicating a component carrier group, the component carrier group including a set of component carriers of at least two or more component carriers, wherein the set of component carriers is according to a carrier aggregation configuration; communicate with the network entity via the set of component carriers according to the carrier aggregation configuration; receive downlink control information from the network entity at least in part based on being connected to the network entity, the downlink control information including one or more fields common to the two or more component carriers, the downlink control information scheduling a plurality of data transmissions via the two or more component carriers, wherein receiving the downlink control information scheduling the plurality of data transmissions is at least in part based on receiving the configuration message indicating the two or more component carriers, wherein receiving the downlink control information includes: receiving an indication from a subset of component carriers of the component carrier group, the subset of component carriers including the two or more component carriers; and send or receive the plurality of data transmissions via the two or more scheduled component carriers at least in part based on receiving the downlink control information, wherein sending or receiving the plurality of data transmissions via the two or more component carriers is at least in part based on receiving the indication of the subset of component carriers.

10. The device according to claim 9, wherein the instructions are further executable by the at least one processor to cause the device to: receive a configuration message indicating a set of parameters for each of the two or more component carriers, wherein the set of parameters for each of the two or more component carriers is the same, and wherein receiving the downlink control information is at least in part based on receiving the configuration message.

11. The device according to claim 9, wherein the instructions are further executable by the at least one processor to cause the device to: receive a configuration message indicating a first set of parameters for a first component carrier of the two or more component carriers; and identify, at least in part based on the first set of parameters, a set of parameters for the remaining component carriers of the two or more component carriers, wherein the first set of parameters for the first component carrier and the set of parameters for the remaining component carriers are the same, and wherein receiving the downlink control information is at least in part based on receiving the configuration message.

12. The device according to claim 9, wherein the instructions are further executable by the at least one processor to cause the device to: attempt to decode a set of downlink transmissions of the plurality of data transmissions; and Send confirmation information associated with the downlink transmission set to the network entity, where the confirmation information includes a single bit associated with the two or more component carriers, a set of bits each associated with one of the two or more component carriers, or a set of bits each associated with a transmission time interval of one of the two or more component carriers.

13. The apparatus according to claim 9, wherein the downlink control information schedules the plurality of data transmissions via the two or more component carriers for a plurality of transmission time intervals, and the instructions can be further executed by the at least one processor to cause the apparatus to: At least partially based on receiving the downlink control information, during a first transmission time interval of the plurality of transmission time intervals, identify a first identifier for a first hybrid automatic repeat request associated with the plurality of data transmissions; and Increment the first identifier to generate a second identifier for a second hybrid automatic repeat request associated with the plurality of data transmissions during a second transmission time interval of the plurality of transmission time intervals.

14. The apparatus according to claim 9, wherein the downlink control information schedules the plurality of data transmissions via the two or more component carriers for a plurality of transmission time intervals, and the instructions can be further executed by the at least one processor to cause the apparatus to: At least partially based on receiving the downlink control information, during a first transmission time interval of the plurality of transmission time intervals, identify a first timing parameter for transmitting a first hybrid automatic repeat request associated with the plurality of data transmissions; and Increment the first timing parameter to generate a second timing parameter for transmitting a second hybrid automatic repeat request associated with the plurality of data transmissions during a second transmission time interval of the plurality of transmission time intervals.

15. The apparatus according to claim 9, wherein: The two or more component carriers are a first set of component carriers; The one or more fields that are common to the first set of component carriers are a first set of one or more fields; The plurality of data transmissions via the first set of component carriers are a first plurality of data transmissions; The downlink control information includes a second set of one or more fields that are common to a second two or more component carrier sets; and The downlink control information schedules a second plurality of data transmissions via the second two or more component carrier sets.

16. An apparatus for wireless communication, comprising: At least one processor; A memory coupled to the at least one processor; and Instructions stored in the memory and executable by the at least one processor to cause the apparatus to: Send a configuration message indicating a component carrier group to a user equipment UE, the component carrier group including a set of component carriers of at least two or more component carriers, where the set of component carriers is according to a carrier aggregation configuration; Communicate with the UE via the set of component carriers according to the carrier aggregation configuration; Transmit downlink control information to the UE at least partially based on connection to the UE, the downlink control information including one or more fields common to the two or more component carriers, the downlink control information scheduling a plurality of data transmissions via the two or more component carriers, wherein transmitting the downlink control information scheduling the plurality of data transmissions is at least partially based on transmitting a configuration message indicating the two or more component carriers, and wherein transmitting the downlink control information includes: Transmit an indication of a subset of component carriers from the group of component carriers, the subset of component carriers including the two or more component carriers; And Transmit or receive the plurality of data transmissions via two or more component carriers that are scheduled at least partially based on transmitting the downlink control information, wherein transmitting or receiving the plurality of data transmissions via the two or more component carriers is at least partially based on transmitting the indication of the subset of component carriers.

17. An apparatus for wireless communication, comprising means for performing the method according to any one of claims 1-8.

18. A computer-readable medium having instructions stored thereon, the instructions when executed by a processor cause the processor to perform the method according to any one of claims 1-8.

19. A computer program product comprising computer instructions, the computer instructions when executed by a processor cause the processor to perform the method according to any one of claims 1-8.

Images