Downlink control information for scheduling multiple component carriers

Abstract

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

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims the benefit of U.S. Provisional Patent Application No. 63 / 043,715, filed on June 24, 2020 by TAKEDA et al., entitled “DOWNLINK CONTROLINFORMATION FOR SCHEDULING MULTIPLE COMPONENT CARRIERS,” and U.S. Patent Application No. 17 / 192,719, filed on March 4, 2021 by TAKEDA et al., entitled “DOWNLINK CONTROLINFORMATION FOR SCHEDULING MULTIPLE COMPONENT CARRIERS,” each of which is assigned to the present assignee. Technical Field

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

[0004] Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcasting, etc. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple 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 extended orthogonal frequency division multiple access (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations or one or more network access nodes, each base station or node simultaneously supporting communication for multiple communication devices, which may be referred to as user equipment (UE).

[0005] In some wireless communication systems, the 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 a SCell, or multiple component carriers), where the UE communicates with two or more cells on a single base station simultaneously. In order to implement carrier aggregation communications, effective techniques are required. Summary of the invention

[0006] The described technology relates to improved methods, systems, devices and apparatuses for supporting downlink control information (DCI) for scheduling multiple component carriers. In general, the described technology provides improvements to the multi-component carrier scheduling process. A base station may send a DCI message to a user equipment (UE) that schedules data transmission on multiple units (e.g., multiple component carriers or multiple time intervals, such as time slots, transmission time intervals (TTIs) or a combination 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 a 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 data transmission set through 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 the UE. The UE may then send or receive a data transmission set through the scheduled unit based on the received DCI.

[0007] A method of wireless communication is described. The method may include: 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 connection 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; and sending or receiving the set of data transmissions via the scheduled two or more component carriers based on receiving the DCI.

[0008] 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 base station through a component carrier set according to a carrier aggregation configuration; receive DCI from the base station based on connection 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 data transmission set through the two or more component carriers; and send or receive the data transmission set through the scheduled two or more component carriers based on receiving the DCI.

[0009] Another apparatus for wireless communication is described. 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 connection 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; and sending or receiving the set of data transmissions via the scheduled two or more component carriers based on receiving the DCI.

[0010] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by at least one processor to: communicate with a base station through a set of component carriers according to a carrier aggregation configuration; receive DCI from the base station based on connection 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 through the two or more component carriers; and send or receive the set of data transmissions through the scheduled two or more component carriers based on receiving the DCI.

[0011] Some examples of the methods, apparatus, 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 component carrier group including at least two or more component carriers, wherein receiving a DCI scheduling a data transmission set may be based on receiving the configuration message indicating the two or more component carriers.

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

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

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

[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the indication of the component carrier subset 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.

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

[0017] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means, 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 the DCI may be based on receiving the configuration message.

[0018] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for receiving a configuration message indicating a first parameter set for a first component carrier of the two or more component carriers, and identifying parameter sets for 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 sets for the remaining component carriers may be the same, and wherein receiving the DCI may be based on receiving the configuration message.

[0019] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for attempting to decode a downlink transmission set of the data transmission set, and sending confirmation information associated with the downlink transmission set to a base station, wherein the confirmation 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.

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

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

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

[0023] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the two or more component carriers may be a first component carrier set, the one or more fields that may be common to the first component carrier set may be a first set of one or more fields, a set of data transmissions through the first component carrier set may be a first set of data transmissions, 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 set of data transmissions through the second set of two or more component carriers.

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

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

[0026] Some examples of the methods, apparatus, 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.

[0027] In some examples of the methods, apparatus, 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.

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

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

[0030] 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 through a component carrier set according to a carrier aggregation configuration; send a DCI to the UE based on connection with the UE, the DCI including one or more fields common to two or more component carriers from the component carrier set, the DCI scheduling a data transmission set through the two or more component carriers; and send or receive a data transmission set through the scheduled two or more component carriers based on sending the DCI.

[0031] 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; sending a DCI to the UE based on 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 via the two or more component carriers; and sending or receiving the set of data transmissions via the scheduled two or more component carriers based on sending the DCI.

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

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

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

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

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

[0037] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the indication of the component carrier subset 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.

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

[0039] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for 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 may be the same, and wherein sending the DCI may be based on sending the configuration message.

[0040] Some examples of the methods, apparatus, 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 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 among the two or more component carriers may be the same, and wherein sending the DCI may be based on sending the configuration message.

[0041] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving, from a UE, acknowledgment information associated with a downlink transmission set from a data transmission set, wherein 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 a TTI of one of the two or more component carriers.

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

[0043] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the two or more component carriers may be a first component carrier set, the one or more fields that may be common to the first component carrier set may be a first set of one or more fields, a set of data transmissions through the first component carrier set may be a first set of data transmissions, 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 set of data transmissions through the second set of two or more component carriers.

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

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

[0046] Some examples of the methods, apparatus, 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 mapping from a common field to the first parameter and the second parameter.

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

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

[0049] Figure 1

[0013] An example of a system for wireless communication that supports downlink control information (DCI) for scheduling multiple component carriers in accordance with aspects of the present disclosure is illustrated.

[0050] Figure 2

[0013] An example of a system for wireless communication that supports DCI for scheduling multiple component carriers in accordance with aspects of the present disclosure is illustrated.

[0051] Figure 3 and Figure 4 An example of a component carrier scheduling configuration supporting DCI for scheduling multiple component carriers according to aspects of the present disclosure is illustrated.

[0052] Figure 5A and Figure 5B An example of a bitmap indication supporting DCI for scheduling multiple component carriers according to aspects of the present disclosure is illustrated.

[0053] Fig. 6A and Figure 6B An example of a resource indication value (RIV) configuration supporting DCI for scheduling multiple component carriers in accordance with aspects of the present disclosure is illustrated.

[0054] Figure 7 An example of a DCI format supporting DCI for scheduling multiple component carriers according to aspects of the present disclosure is illustrated.

[0055] Figure 8 An example of a data retransmission process supporting DCI for scheduling multiple component carriers according to aspects of the present disclosure is illustrated.

[0056] Fig. 9 An example of a process flow to support DCI for scheduling multiple component carriers in accordance with aspects of the present disclosure is illustrated.

[0057] Fig.10 and Fig.11 A block diagram of an apparatus supporting DCI for scheduling multiple component carriers according to aspects of the present disclosure is shown.

[0058] Fig.12 A block diagram of a communication manager supporting DCI for scheduling multiple component carriers in accordance with aspects of the present disclosure is shown.

[0059] Fig.13 A diagram of a system including devices supporting DCI for scheduling multiple component carriers is shown in accordance with aspects of the present disclosure.

[0060] Fig.14 and Fig.15 A block diagram of an apparatus supporting DCI for scheduling multiple component carriers according to aspects of the present disclosure is shown.

[0061] Fig.16 A block diagram of a communication manager supporting DCI for scheduling multiple component carriers in accordance with aspects of the present disclosure is shown.

[0062] Fig.17 A diagram of a system including devices supporting DCI for scheduling multiple component carriers is shown in accordance with aspects of the present disclosure.

[0063] Figures 18 to 21 A flow chart illustrating a method of supporting DCI for scheduling multiple component carriers according to aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0064] Some wireless communication systems may support communication between 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, a first component carrier may refer to a component carrier corresponding to a dynamic spectrum sharing (DSS) primary cell (PCell), and a 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.

[0065] In a conventional system, a UE may be configured to monitor a physical downlink control channel (PDCCH) message on a DSS PCell, monitoring downlink control information (DCI) sent from a base station that schedules data transmission, such as a physical uplink shared channel (PUSCH) transmission or a physical downlink shared channel transmission (PDSCH) on one of the component carriers. In order to schedule data transmission on multiple component carriers (e.g., multi-component carrier scheduling, joint component carrier scheduling, cross-carrier scheduling), the UE may monitor and receive multiple DCIs. However, sending multiple DCIs by a base station or receiving multiple DCIs by a UE may increase the signaling overhead of using a large number of resources to indicate different transmission parameters for each component carrier. In addition, a PCell may serve a low frequency band (e.g., 2 GHz), while an SCell may serve a mid- to high-frequency band (e.g., 3.5 to 4.7 GHz). Therefore, a PCell may 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 reduced throughput and multiple DCIs required for multi-component carrier scheduling may reduce the reliability of the network.

[0066] To improve reliability and improve spectral efficiency, a single DCI may 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 carrier). The DCI may be sent on a non-DSS SCell, where the DCI may schedule data transmission on one or more SCells, one or more PCells, or a combination thereof. In some cases, a single DCI may be configured to schedule multiple component carriers and / or multiple time intervals (e.g., time slots, sub-time slots, micro-time slots, TTIs) for each component carrier. In order to reduce resources used to send or receive DCI that schedules data transmission on multiple component carriers and / or time intervals, each device in a communication system may be configured to support scheduled unit grouping. As part of the scheduled unit grouping, units such as component carriers or time intervals may be configured by a base station, for example, as part of a group. In some cases, the units may be grouped according to frequency resources or time resources or a combination thereof. Each unit within a group may 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) so that a single DCI can schedule the unit group instead of each individual unit to reduce the resources used for DCI transmission. In some implementations, not all units in a group may be scheduled by each DCI transmission. For example, the DCI may schedule a subset of the units within a group and may not schedule the remaining units of the group. In order to indicate which units in a group are scheduled by the DCI, the DCI format may be configured to include a bitmap or a resource indication value (RIV).

[0067] Certain aspects of the subject matter described herein may be performed to achieve one or more advantages. The described techniques may support improvements in multi-component carrier scheduling by reducing signaling overhead, increasing reliability, and improving spectrum efficiency, among other advantages. Thus, the supported techniques may include improved network operation and, in some examples, may improve network efficiency, among other benefits.

[0068] Various aspects of the present disclosure are initially described in the context of a wireless communication system. Various aspects are described in conjunction with component carrier scheduling configurations, bitmap indications, RIV configurations, DCI formats, data retransmission procedures, and processing flows. Various aspects of the present disclosure are further illustrated and described by reference to apparatus diagrams, system diagrams, and flow charts for scheduling DCI for multiple component carriers.

[0069] Figure 1An example of a wireless communication system 100 supporting DCI for scheduling multiple component carriers according to various aspects of the present disclosure is illustrated. 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 communications, ultra-reliable (e.g., mission-critical) communications, low-latency communications, communications with low-cost and low-complexity devices, or any combination thereof, etc.

[0070] 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 over which the UEs 115 and the base stations 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area over which the base stations 105 and the UEs 115 may support communication of signals according to one or more radio access technologies.

[0071] The UEs 115 may be dispersed throughout the 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 in FIG. 1. The UEs 115 described herein may be able to communicate 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), such as Figure 1 shown.

[0072] Base stations 105 may communicate with core network 130, or with each other, or both. For example, base stations 105 may interface with core network 130 via one or more backhaul links 120 (e.g., via S1, N2, N3, or other interfaces). Base stations 105 may communicate with each other via backhaul links 120 (e.g., via X2, Xn, or other interfaces) directly (e.g., directly between base stations 105) or indirectly (e.g., via core network 130), or both. In some examples, backhaul links 120 may be or include one or more wireless links.

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

[0074] In other examples, UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where a "device" may also be referred to as a unit, a station, a terminal, or a client. UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a multimedia / entertainment device (e.g., a radio, an MP3 player, a video device), a camera, a gaming device, a navigation / positioning device (e.g., a GNSS (Global Navigation Satellite System) based on, for example, GPS (Global Positioning System), BeiDou, GLONASS, or Galileo (a ground-based device)), a tablet, a laptop, a personal computer, a netbook, a smart book, a personal computer, a smart device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, virtual reality glasses, a smart wristband, smart jewelry (e.g., a smart ring, a smart bracelet)), a drone, a robot / robotic device, a vehicle, a vehicle device, a meter (e.g., a parking meter, an electric meter, a gas meter, a water meter), a monitor, a gas pump, an appliance (e.g., a kitchen appliance, a washing machine, a dryer), a location tag, a medical / health care device, an implant, a sensor / actuator, a display, or any other suitable device configured to communicate via a wireless or wired medium. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, among other examples, which may be implemented in various objects, such as in applications, vehicles, meters, and other examples. In one aspect, the technology disclosed herein may be applicable to MTC or IoT UEs. MTC or IoT UEs may include MTC / enhanced MTC (eMTC, also known as CAT-M, Cat M1) UEs, NB-IoT (also known as CAT NB1) UEs, and other types of UEs. eMTC and NB-IoT may refer to future technologies that may evolve from or may 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).

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

[0076] The UE 115 and the base station 105 can communicate with each other wirelessly via one or more communication links 125 on one or more carriers. The term "carrier" can 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 of a radio frequency spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating operations for carriers, 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 the carrier aggregation configuration. Carrier aggregation may be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers.

[0077] 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., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute Radio Frequency Channel Number (EARFCN)) and may be located according to a channel raster for discovery by a UE 115. A carrier may operate in a standalone mode, where initial acquisition and connection may be performed by a UE 115 via the carrier, or a carrier may operate in a non-standalone mode, where a connection is anchored using a different carrier (e.g., of the same or different radio access technology).

[0078] 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 communications (e.g., in FDD mode), or may be configured to carry both downlink and uplink communications (e.g., in TDD mode).

[0079] A carrier may be associated with a particular bandwidth of a radio frequency spectrum, and in some examples, the carrier bandwidth may be referred to as the "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of a plurality of 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)). The devices of the wireless communication system 100 (e.g., a base station 105, a UE 115, or both) may have a hardware configuration that supports communications on a particular carrier bandwidth, or may be configured to support communications on one of a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a base station 105 or a UE 115 that supports simultaneous communications via carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate on a portion (e.g., a subband, a BWP) or all of a carrier bandwidth.

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

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

[0082] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, the frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into multiple time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include multiple periods (e.g., depending on the length of the cyclic prefix preceding each symbol period). In some wireless communication systems 100, the time slot may be further divided into multiple micro-time 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 period. The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0083] A subframe, slot, subslot, microslot, 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 a shortened TTI (sTTI)).

[0084] 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 a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. 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 a system bandwidth or a subset of a system bandwidth of a carrier. 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 of 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 a coding information format for a control information format having a given payload size. A search space set may include a common search space set configured for sending control information to multiple UEs 115 and a UE-specific search space set for sending control information to a specific UE 115.

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

[0086] 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. UE115 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 service prioritization, 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.

[0087] In some examples, UE 115 can also communicate directly with other UE 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, a 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 facilitates scheduling resources for D2D communication. In other cases, D2D communication is performed between UEs 115 without involving the base station 105.

[0088] 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 (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) for managing access and mobility and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) for routing packets or interconnections to an external network. The control plane entity may manage non-access stratum (NAS) functions associated with the core network 130 for UE 115 served by the base station 105, such as mobility, authentication, and bearer management. User IP packets may be delivered through a user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to the IP service 150 of the network operator. The Network Operator IP Services 150 may include access 5 to the Internet, Intranet(s), IP Multimedia Subsystem (IMS), or packet switched streaming services.

[0089] Some network devices, such as base stations 105, may include subcomponents such as access network entities 140, which may be examples of access node controllers (ANCs). Each access network entity 140 may communicate with UE 115 through one or more other access network transmission entities 145, which may be referred to as radio heads, smart 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 base station 105 may be distributed across various network devices (e.g., radio heads and ANCs), or merged into a single network device (e.g., base station 105).

[0090] 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). Typically, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the wavelength ranges from 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 for macro cells to provide services to UEs 115 located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter distances (e.g., less than 100 kilometers) compared to transmission of smaller frequencies and longer waves using the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0091] The wireless communication system 100 can utilize both licensed and unlicensed radio spectrum bands. For example, the wireless communication system 100 can employ license assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in unlicensed bands such as the 5 GHz industrial, scientific, and medical (ISM) band. When operating in an unlicensed radio frequency spectrum band, devices such as base stations 105 and UEs 115 can employ carrier sensing for conflict detection and avoidance. In some examples, operations in unlicensed frequency bands can be based on carrier aggregation configurations (e.g., LAA) in conjunction with component carriers operating in licensed frequency bands. Operations in unlicensed spectrum can include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, as well as other examples.

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

[0093] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting device or a receiving device (e.g., a base station 105 or a 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 antenna elements of an antenna array so that some signals propagating in a particular direction relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals transmitted via antenna elements can include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each antenna element can be defined by a set of beamforming weights associated with a particular direction (e.g., relative to the antenna array of the transmitting device or the receiving device, or relative to some other direction).

[0094] UE 115 and base station 105 can support retransmission of data to increase the possibility of data being successfully received. HARQ feedback is a technique that increases the possibility of correctly receiving data through communication link 125. HARQ can include a combination of error detection (e.g., using cyclic redundancy check (CRC)), forward error correction (FEC) and retransmission (e.g., automatic repeat request (ARQ)). HARQ can improve the throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device can support same-slot HARQ feedback, where the device can provide HARQ feedback for data received in previous symbols in the slot in a specific slot. In other cases, the device can provide HARQ feedback in a subsequent slot or according to some other time intervals.

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

[0096] Figure 2 An example of a wireless communication system 200 that supports DCI for scheduling multiple component carriers according to various aspects of the present disclosure is illustrated. The wireless communication system 200 may include a base station 105-a and a UE 115-a, which may be as described in reference Figure 1 An example of a base station 105 and a UE 115 is described. The base station 105-a may serve a geographic coverage area 110-a. In some cases, the base station 105-a may implement a multi-component carrier scheduling process with the UE 115-a. Additionally or alternatively, other wireless devices such as the UE 115-a may implement a multi-component carrier scheduling process.

[0097] UE 115-a can establish a connection with base station 105-a via communication link 205 through at least a first component carrier and a second component carrier (such as component carriers 210-a and 210-b), wherein 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 may not support DSS, or both component carriers 210 may not support DSS. In some cases, component carrier 210-b may support low frequency bands (e.g., 2 GHz) and low subcarrier spacing (e.g., 15 kHz), while component carrier 210-a may support mid-to-high frequency bands (e.g., 3.5 GHz, 4.7 GHz) and high subcarrier spacing (e.g., 30 kHz). Therefore, a DSS PCell (e.g., component carrier 210-b) supporting a low frequency band 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 full set of resources in a given spectrum. In order to support network improvements (such as improved reliability and improved 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 (e.g., component carrier 210-a) supporting a higher frequency because component carrier 210-a can serve a single type of device (e.g., 5G NR device) and the full spectrum supported by component carrier 210-a can be used by each device on component carrier 210-a.

[0098] To further increase network reliability and improve spectrum efficiency, a single data scheduling indication (e.g., PDCCH, DCI format, DCI) may be used to schedule data transmission (e.g., downlink data transmission or uplink data transmission) on multiple component carriers (e.g., multiple cells) (e.g., component carriers 210-a and 210-b or multiple time intervals 225 or a combination thereof) instead of using multiple scheduling indications for scheduling multiple component carriers 210. In one example, a physical control channel 215 (e.g., PDCCH) on component carrier 210-a may 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, a physical control channel 215 (e.g., PDCCH) on component carrier 210-b may schedule physical shared channels 220 (e.g., PDSCH, PUSCH) on component carriers 210-a and 210-b by using a single DCI.

[0099] In order to reduce the resources used to send or receive physical control channels 215 that schedule data transmissions on multiple component carriers 210 and / or multiple time intervals 225, each device in a communication system (e.g., a wireless communication system 200) can be configured to support scheduled unit grouping. As part of the scheduled unit grouping, a unit such as a component carrier 210 or a time interval 225 can be configured by a base station, for example, as part of a group. In some cases, each group 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-time slots or micro-time slots, TTIs) of component carrier 210-a can be configured as part of a group, so 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 the component carrier 210-b may be configured as part of a group such that one or more of the time intervals 225-d or 225-e may be configured as part of the same group. Additionally or alternatively, the time intervals 225 of the component carrier 210-b may be divided into multiple groups.

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

[0101] Figure 3 An example of a component carrier scheduling configuration 300 supporting DCI for scheduling multiple component carriers according to various aspects of the present disclosure is illustrated. The component carrier scheduling configuration 300 may be performed by a base station or a UE or both, and the base station or the UE may be a reference Figure 1 and Figure 2 Examples of base stations and UEs described. In some cases, the base station may 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 UEs may implement a multi-component carrier scheduling procedure.

[0102] As described herein, a UE may communicate with a base station via a set of component carriers 305 according to a carrier aggregation configuration. For example, a UE may communicate with a 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 may be a DSS component carrier, a non-DSS component carrier, a PCell, or an SCell. In order to efficiently schedule data transmissions such as downlink or uplink data transmissions on one or more component carriers 305, a base station or some other network device may configure a cell group, where a cell may 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 the component carriers 305. In some cases, the base station can group the component carriers 305 in the same frequency band based on the component carriers 305. 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. Therefore, 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.

[0103] The component carriers 305 may each be associated with a parameter set, such as an RRC parameter. In some implementations, due to the presence of unit grouping, each parameter of the parameter set associated with each component carrier 305 of the group of component carriers 305 may be the same. For example, the RRC parameters associated with each component carrier 305 in group 1 may be the same and the RRC parameters associated with each component carrier 305 in group 2 may be the same, wherein the RRC parameters between group 1 and group 2 may be different.

[0104] In some cases, the network (e.g., a base station) may configure RRC parameters for each component carrier 305 in the group, wherein 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 may be considered to be copied by the UE to other component carriers 305 in the same group. For example, the UE may receive an indication of the component carriers 305 that are configured as part of the group, and the UE may 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 may apply the RRC parameters of one component carrier 305 to all component carriers 305 within the group.

[0105] In some cases, the DCI field 325 may be shared or common between the component carriers 305 in the group. For example, the code point of the DCI field 325 may indicate the same value for all component carriers in the same group. Therefore, the component carriers 305 in the group may 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 between the component carriers 305 in the group. Since some or all parameters (e.g., TDRA, FDRA parameters) for each unit are the same or mostly the same, the DCI may reduce the number of parameter sets included in the DCI, because the DCI may include one parameter set for each group, rather than indicating a parameter set for each unit. In the case where the parameters are mostly the same, the DCI may combine the same parameters for the group and indicate these parameters once for the group, and indicate the non-same parameters for each unit separately. Between different groups, separate DCI fields 325 may be included in the same DCI format 320, wherein each separate DCI field 325 may include data transmission scheduling information on the component carriers 305 included in the group with which the DCI field 325 is associated.

[0106] Thus, the base station can effectively schedule one or more data transmissions on the group, rather than individually scheduling each component carrier 305. For example, as described herein, the base station can configure two groups for the UE, where group 1 includes CC0 305-a, and group 2 includes CC1 305-b, CC2 305-c, CC3 305-d, and CC4 305-e.

[0107] 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. In order to schedule data transmission on one or more component carriers 305, the base station can send a physical control channel 310 through CC0 305-a, wherein the physical control channel 310 can include a DCI format 320. The DCI format 320 may include a DCI field 325-a and a DCI field 325-b, wherein the DCI fields 325-a and 325-b may be the same size or different sizes based on the RRC configuration for each group. The DCI field 325-a may include data transmission scheduling information applicable to each component carrier 305 in group 1 for group 1, and the DCI field 325-b may include data transmission scheduling information applicable to each component carrier 305 in group 2 for group 2. For example, the DCI field 325-a may indicate information for data transmission 315-a on CC0 305-a associated with group 1, and the DCI field 325-b may indicate information for data transmission 315-b to 315-e on CC1 305-b to CC4 305-e respectively associated with group 2.

[0108] Figure 4 An example of a component carrier scheduling configuration 400 supporting DCI for scheduling multiple component carriers according to various aspects of the present disclosure is illustrated. The component carrier scheduling configuration 400 may be performed by a base station or a UE or both, and the base station or the UE may be a reference Figures 1 to 3 Examples of base stations and UEs described. In some cases, the base station may 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 UEs may implement a multi-component carrier scheduling procedure.

[0109] As described herein, a UE may communicate with a base station via a set of component carriers 405 according to a carrier aggregation configuration. For example, a UE may communicate with a base station via one or both of component carriers 405-a or 405-b, where each component carrier 405 may be a DSS component carrier, a non-DSS component carrier, a PCell, or an SCell. In order to efficiently schedule data transmissions such as downlink or uplink data transmissions on one or more component carriers 405, a base station or some other network device may configure a unit group, where a unit may 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 carriers 405. The base station can also group the time intervals 415 and the component carriers 405 so that the base station can configure one or more time intervals 415 of multiple component carriers 405 as part of the same group. In some cases, the base station can group the component carriers 405 in the same frequency band based on the component carrier. For example, 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. Therefore, the base station can configure one or more time intervals 415 of the component carrier 405-a as part of group 1 and configure one or more time intervals 415 of the component carrier 405-b as part of group 2.

[0110] In some cases, the base station may determine which time intervals 415 or which component carriers 405 to include in a group based on the subcarrier spacing of each component carrier 405. In some cases, the base station may group the component carriers 405 and time intervals 415 based on the component carriers 405 being in the same frequency band or having the same subcarrier spacing or both. For example, component carrier 405-a may have a larger subcarrier spacing (e.g., 30 kHz) than component carrier 405-b (e.g., 15 kHz). Additionally or alternatively, component carriers 405-a or 405-b may be in different frequency bands. Thus, the base station may configure each component carrier 405 as part of a different group. Since the subcarrier spacing of the component carriers 405 is different, two time intervals 415 of component carrier 405-a may fit into the same duration as one time interval 415 of component carrier 405-b. The base station may group the time intervals 415 based on the number of time intervals 415 that fit into the duration. For example, the base station may first assign 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 component carrier 405-a fit into the same duration as time interval 415-c. Therefore, the base station may group intervals 415-a and 415-b as part of group 2. The base station may indicate the grouping configuration to the UE via semi-static signaling (e.g., RRC). For example, the base station may configure the time interval 415 grouping prior to communication using multiple component carriers 405 and indicate the time interval 415 grouping to one or more UEs.

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

[0112] In some cases, the DCI field 425 may be shared or common between the component carriers 405 and / or time intervals 415 in the group. For example, the code point of the DCI field 425 may indicate the same value for all component carriers 405 and time intervals 415 in the same group. Between different groups, separate DCI fields 425 may be included in the same DCI format 420, wherein each separate DCI field 425 may include data transmission scheduling information for each unit included in the group to which the DCI field 425 is associated. Therefore, the units in the group may be referred to as mirrors, wherein the TDRA, FDRA, MCS index, or start and length indicator (SLIV) are the same between 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 may include one parameter set for each group, rather than indicating a parameter set for each unit, resulting in a shared or common DCI field 425.

[0113] In some implementations, not all parameters in the parameter set are the same between the time intervals 415 in the group. For example, K0, K1, and HARQ process ID and other parameters can be based on time, where K0 and K1 can be TDRA. Therefore, 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 micro-time slots) from the time interval 415 in which the physical control channel 410 (e.g., DCI) is received to the time interval 415 in which the DCI is scheduled for downlink transmission, because 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 for downlink data transmission scheduling time intervals 415-a and 415-b, the K0 value for time interval 415-a will be two, and the K0 value for time interval 415-b will be three. The K2 value and HARQ process ID will also vary based on the time slot.

[0114] In the case where the parameters are mostly the same (e.g., grouping time intervals 415 where the TDRA varies based on time), the DCI may combine similar parameters for the group and indicate them once for the group (e.g., in a common or shared DCI field 425), and indicate non-similar parameters for each unit separately. In some cases, the DCI may indicate the TDRA (e.g., K0, K2, HARQ ID) for each time interval 415 of the group, where the time interval 415 may be in the same component carrier 405 or in different component carriers 405 within the group. In some cases, the DCI may 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. The UE may then increment the TDRA accordingly for each scheduled time interval 415 after the time interval 415 in which the TDRA was indicated.

[0115] Thus, the base station can effectively schedule one or more data transmissions on a group rather than scheduling each unit individually. For example, as described herein, the base station can configure two groups for the UE, 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, time intervals 415 within the same group can be associated with different time-related parameters (e.g., TDRA). In order to schedule data transmissions on one or more component carriers 405, the base station can send a physical control channel 410 via component carrier 405-a, where the physical control channel 410 can include a DCI format 420. The DCI format 420 can include a DCI field 425-a and a DCI field 425-b, and the 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 may include data transmission scheduling information applicable to each unit in group 1 for group 1, and DCI field 425-b may include data transmission scheduling information applicable to each unit in group 2 for group 2. In some cases, each DCI field 425 may include TDRA information for each unit or one unit instead of for each group. For example, DCI field 425-b may indicate information of data transmission in time intervals 415-a and / or 415-b on component carrier 405-a associated with group 2, while DCI field 425-a may indicate information of data transmission in time interval 415-c on component carrier 405-b associated with group 1.

[0116] Figure 5A and Figure 5B Examples of bitmap indications 500 and 501 supporting DCI for scheduling multiple component carriers according to various aspects of the present disclosure are illustrated respectively. The bitmap indications 500 and 501 may be performed by a base station or a UE or both, and the base station or the UE may be a reference Figures 1 to 4 Examples of base stations and UEs described. In some cases, the base station may implement a multi-component carrier scheduling procedure including bitmap indication 500 and / or 501 with the UE. Additionally or alternatively, other wireless devices such as UEs may implement a multi-component carrier scheduling procedure.

[0117] The base station may semi-statically group the units (e.g., component carrier 505, time interval 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 may be scheduled with each physical control channel 510 (e.g., DCI). For example, the units scheduled by each DCI may be based on traffic, traffic conditions, or power constraints. Therefore, the base station may configure a bitmap for each configured group and send it to the UE to indicate which units in group 520 are scheduled. The bitmap may be included in the DCI, where the bitmap is group-specific. For example, the DCI format may include scheduling information for the first group and the second group. Therefore, the DCI format may include a bitmap for group 1 and a bitmap for group 2. The bitmap may include a bit 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 may include a 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 may include a bit for each time interval. A 1 bit may indicate that the cell is scheduled for data transmission, while a 0 bit may indicate that the cell is not scheduled for data transmission.

[0118] like Figure 5A As shown, the base station can group the component carriers 505 in the same frequency band based on the component carriers 505, such as in combination with Figure 3 For example, the base station may 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

[0119] 520-a. In some cases, the base station may potentially schedule data transmission 515 on each component carrier 505. For example, the base station may determine to schedule data transmission 515 (e.g., data transmission 515-a, 515-b, 515-c, and 515-d) on each component carrier 505 or a subset of component carriers. Figure 5A In the example shown, the base station may determine to schedule data transmission on CC1 505-b and CC4 505-e, but not on CC2 505-c and CC3 505-d. Thus, the base station may configure a 4-bit bitmap for group 520-a, including a bit for each component carrier 505, where the bitmap may read 1001. The UE may 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.

[0120] like Figure 5BAs shown, the base station may group time intervals 525 alone or in combination with grouping component carriers 505. For example, the base station may group time intervals 525-a and 525-b of component carrier 505-f in group 520-b. In some cases, the base station may potentially schedule data transmissions on each time interval 525 of group 520-b. In some cases, such as Figure 5B As shown, the base station may determine that data transmission is scheduled on a subset of time intervals 525 of group 520-b. For example, the base station may determine that data transmission is scheduled on time interval 525-a. Therefore, the base station may configure a 2-bit bitmap for group 520-b, including a bit for each time interval 525, where the bitmap may be read as 10. The UE may 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.

[0121] Fig. 6A and Figure 6B Examples of RIV configurations 600 and 601 supporting DCI for scheduling multiple component carriers according to various aspects of the present disclosure are illustrated respectively. The RIV configurations 600 and 601 may be performed by a base station or a UE or both, and the base station or the UE may be a reference Figures 1 to 5B Examples of base stations and UEs described. In some cases, the base station may implement a multi-component carrier scheduling procedure with the UE using RIV configuration 600 and / or 601. Additionally or alternatively, other wireless devices such as UEs may implement a multi-component carrier scheduling procedure.

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

[0123] In some implementations, such as if multiple component carriers and multiple time slots are included in the same group, the interpretation of the continuation unit may be defined. In some cases, the interpretation may be defined and signaled to the UE aperiodically, semi-statically (e.g., via RRC) or dynamically (e.g., via DCI). For example, Fig. 6A As shown, the order of the units indicated by the RIV field may be frequency first and time second. Fig. 6A , group 615-a may include four component carriers and two time slots for each component carrier. Thus, group 615-a may include 8 cells. The base station may schedule data transmissions on all 8 cells or a subset of the 8 cells. The base station may include a RIV field in the DCI included in the physical control channel 610-a that indicates the first cell to be scheduled and the number of consecutive cells to be scheduled after the first cell. Fig. 6A In the example of , consecutive cells are interpreted as frequency first and time second. Thus, if the base station schedules all 8 cells 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 cell is the bottom-most, left-most cell of group 615-a, and determine that the next scheduled cell is in the next component carrier. The UE can move up in the component carriers until it reaches the last component carrier of group 615-a, and then move to the next time slot and start at the bottom-most component carrier of the next time slot. The UE can continue to move up in the component carriers until the UE reaches the last component carrier of the second time slot. The UE can identify data transmission for each cell in this manner until the UE reaches the top-most, right-most cell of group 615-a.

[0124] In some cases, the DCI format may indicate a data transmission schedule for more than one group, such as groups 615-a and 620-a. The base station may indicate scheduled units in different ways for different groups. For example, the base station may indicate a bitmap for one group and a RIV field for another group. In some cases, the base station may 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 may include a number of units exceeding a threshold, and group 620-a may include a number of units below a threshold. Thus, the physical control channel 610-a may 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.

[0125] In another example, Figure 6B As shown, the order of the units indicated by the RIV field may be time first and frequency second. Figure 6B, similar to group 615-a, group 615-b may include 8 cells. Therefore, if the base station schedules all 8 cells or a subset of the cells in group 615-b, the UE can receive the DCI in the physical control channel 610-b and determine based on the RIV field that the starting cell is the bottom-most, left-most cell of group 615-b, and determine that the next scheduled cell is in the next time slot. The UE can move from time slot to time slot until all time slots of the current component carrier are identified. The UE can then move up to the next component carrier of group 615-b and continue to move from time slot to time slot. The UE can identify data transmission for each cell in this manner until the UE reaches the top-most, right-most cell of group 615-b. Fig. 6A Similar to the example shown in , group 615-b may include a number of units exceeding a threshold, and group 620-a may include a number of units below a threshold. Thus, physical control channel 610-b may include a DCI field for group 615-b including a RIV field, and a DCI field for group 620-b including a bitmap for group 620-b.

[0126] Figure 7 An example of a DCI format 700 supporting DCI for scheduling multiple component carriers according to various aspects of the present disclosure is illustrated. The DCI format 700 may be executed by a base station or a UE or both, and the base station or the UE may be a reference Figures 1 to 6B In some cases, the base station may implement a multi-component carrier scheduling procedure with the UE including sending a DCI format 700 to the UE. Additionally or alternatively, other wireless devices such as UEs may implement a multi-component carrier scheduling procedure with the DCI format 700.

[0127] exist Figure 7 In the example shown, the base station can configure two unit groups, where each group can include any number of component carriers or any number of time intervals (eg, time slots) or a combination thereof. Figure 3 and Figure 4As described, the 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. The 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. The DCI format 700 may also include a common DCI field 715, which includes parameters applicable to both the first group and the second group.

[0128] In some cases, the DCI format 700 may include an FDRA field that is separate (e.g., group-specific) or common to each group. For example, one or more FDRA fields may be included in a dedicated DCI field 710-a, 710-b, or both, resulting in a separate FDRA field. 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, wherein 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 a 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 FDRA code points and resource allocations for the first cell group and the second cell group may be semi-statically configured, such as through RRC signaling.

[0129] In some cases, DCI format 700 may include a TDRA field that is separate (e.g., group-specific) or common for each group. For example, one or more TDRA fields may be included in a dedicated DCI field 710-a, a DCI field 710-b, or both, resulting in a separate TDRA field. In such a case, some time-dependent indicators (e.g., SLIV) may be identical for all cells in each cell group. Therefore, the indicator (e.g., SLIV) may be indicated by the TDRA field 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 be incremented as each time slot progresses. Therefore, these indicators (e.g., K0 and / or K2 values) may be indicated by the TDRA field for each cell group of the first time slot of the cell group. Based on the indication of the K0 and / or K2 values ​​of the first time slot of each group, the UE may increment the K0 / K2 values ​​for each subsequent time slot of each cell group. Additionally or alternatively, one or more TDRA values ​​may be included in a common DCI field 715 for the first cell group and the second cell group. In such a case, the TDRA code point may indicate a time-dependent indicator for each cell in the first time slot of the first cell group (e.g., SLIV and K0 for downlink data transmission, SLIV and K2 for uplink data transmission) and a time-dependent indicator for each cell in the first time 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 indicator for the first time slot of the first cell group (e.g., SLIV, K0, K2) and the time-dependent indicator for the first time slot of the second cell group (e.g., SLIV, K0, K2) may be semi-statically configured, for example, by RRC signaling.

[0130] In some cases, the DCI format 700 may include a HARQ ID field that is separate (e.g., group-specific) for each group or common to each group. The HARQ ID field may be the same between component carriers in the same group. Between slots within the same group, the HARQ ID may be incremented as each slot progresses. Thus, the HARQ ID indication (e.g., a separate indication for each group, 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 increment the HARQ ID using a modulo operation (e.g., a modulo 16 operation).

[0131] Figure 8An example of a data retransmission process 800 supporting DCI for scheduling multiple component carriers according to various aspects of the present disclosure is illustrated. The data retransmission process 800 may be performed by a base station or a UE or both, and the base station or the UE may be a reference Figures 1 to 7 Examples of base stations and UEs described herein. In some cases, the base station may implement a multi-component carrier scheduling process with the UE including performing a data retransmission process 800 with the UE. Additionally or alternatively, other wireless devices such as UEs may implement a multi-component carrier scheduling process and perform or participate in the data retransmission process 800.

[0132] In some cases, the base station may include a new data indicator (NDI) in the DCI, the NDI comprising one or more bits to indicate to the UE whether the data scheduled on one or more cells of one or more groups is new data, or whether the data transmission is a retransmission. If the NDI is switched so that the current NDI bit value is different from the previous NDI bit value, new data is scheduled. If the NDI is not switched so 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 may be indicated for each cell within a group.

[0133] In some cases, to reduce the number of bits used for each NDI and maintain flexible scheduling, such as combining FIG. 5A to FIG. 7 The bitmap and / or RIV field included in the DCI format may be used for NDI. For example, the 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, such as Figure 8 As shown in the top example of , the UE or the base station or both can determine that three data transmission errors occurred (e.g., two errors in group 805-a and one error in group 805-b), where the UE or the base station was unable to successfully decode the scheduled data transmission. In either case, the base station can determine which cells caused the errors (e.g., based on HARQ feedback). At 815-a, the base station can determine not to switch the NDI for group 805-a and not to switch the NDI for group 805-b. To avoid unnecessary retransmissions of all cells in each group, the base station can also use a bitmap or RIV field in the DCI format to indicate which cells can be retransmitted, where the data mapped to the cells is fixed between the initial transmission and the retransmission. In the case of a bitmap, such as Figure 8As shown, the base station may indicate 1 for the unit to be retransmitted and 0 for the unit not to be retransmitted. Therefore, at 815-a, the base station may not toggle 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 the 1 is associated with the unsuccessful transmission unit. Based on the DCI format, the UE may send or receive three retransmissions in the associated unit, where no other data is received in the other units.

[0134] 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, after 815-a, one unit from group 805-a may result in an unsuccessful retransmission. At 815-b, the base station may determine not to switch the NDI for group 805-a because one unit resulted in an unsuccessful retransmission, and the base station may determine to switch the NDI for group 805-b because each unit of group 805-a resulted in a successful transmission. The base station may configure a bitmap or RIV for group 805-a indicating a certain unit that may be retransmitted. The base station may also configure a bitmap or RIV for group 805-b indicating a new data transmission for the units of group 805-b. The UE may receive DCI from the base station and identify an unswitched NDI and bitmap or RIV for group 805-a and determine that one data retransmission is scheduled for the cells of group 805-a, and identify a switched NDI and 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 may send or receive retransmissions in the associated cells of group 805-a and send or receive new transmissions scheduled in group 805-b.

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

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

[0137] Fig. 9 An example of a process flow 900 for supporting DCI for scheduling multiple component carriers in accordance with aspects of the present disclosure is illustrated. The process flow 900 may illustrate an example multi-component carrier scheduling process. For example, a base station 105-b may determine to schedule one or more component carriers or one or more time intervals for data transmission and indicate the schedule to a UE 115-b. The base station 105-b and the UE 115-b may be referenced. Figures 1 to 8 Examples of corresponding wireless devices described. In some cases, rather than base station 105-b implementing the component carrier scheduling process, a different type of wireless device (e.g., UE 115) may perform the process. The following alternative examples may be implemented, where certain steps are performed in a different order than described or not performed at all. In some cases, the steps may include additional features not mentioned below, or more steps may be added.

[0138] At 905, the UE 115-b may communicate with the base station 105-b via a component carrier set according to a carrier aggregation configuration. The component carrier set may include one or more DSS carriers, one or more non-DSS carriers, one or more SCells, or one or more PCells, or a combination thereof.

[0139] At 910, UE 115-b may receive DCI from base station 105-b based on being connected to the base station, the DCI including one or more fields common to multiple (e.g., two or more) component carriers from a component carrier set. The DCI may schedule a set of data transmissions over two or more component carriers. In some cases, the multiple component carriers may be a component carrier group, where the group may 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 may schedule a set of data transmissions over two or more component carriers for a set of TTIs (e.g., one or more). Thus, the group may include a unit set including one or more component carriers, or one or more time intervals, or a combination thereof.

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

[0141] UE 115-a may receive a configuration message from base station 105-b indicating a component carrier group including at least two or more component carriers, wherein receiving a DCI for scheduling a data transmission set is based on receiving the configuration message indicating the two or more component carriers. The configuration message may be received prior to the DCI. In some cases, base station 105-b may send the configuration message semi-statically, such as in an RRC message.

[0142] In some cases, not all units in a group may be scheduled by each DCI. In such a case, UE 115-a may receive an indication of a subset of units (e.g., component carriers, time intervals) from a group, where the unit subset may include two or more component carriers. In some cases, sending or receiving a data transmission set through two or more component carriers is based on receiving an indication of a subset of 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 component carrier (and / or one or more time intervals) group. In some implementations, UE 115-b may receive an indication of the number of consecutive units (e.g., component carriers, time intervals) from a unit group within a unit subset, 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 priority order or a time priority order.

[0143] 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) of two or more component carriers, and UE 115-b may identify parameter sets for remaining component carriers of 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.

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

[0145] At 915, if the DCI schedules an uplink data transmission set, UE 115-b may send the data transmission set over the scheduled two or more component carriers and / or over one or more time intervals based on receiving the DCI. In some cases, UE 115-a may send 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.

[0146] At 920, if the DCI schedules a downlink data transmission set, UE 115-b may receive the data transmission set over two or more scheduled component carriers and / or over one or more time intervals based on receiving the DCI. 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.

[0147] In some cases, UE 115-b may attempt to decode a downlink transmission set of the data transmission set and send confirmation information (e.g., ACK / NACK feedback) associated with the downlink transmission set to base station 105-b. The confirmation information may include 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 (e.g., time interval, time slot) of one of the two or more component carriers.

[0148] Fig.10 A block diagram 1000 of a device 1005 supporting DCI for scheduling multiple component carriers according to various aspects of the present disclosure is illustrated. The device 1005 may be an example of various aspects of the UE 115 as described herein. The device 1005 may include a receiver 1010, a communication manager 1015, and a transmitter 1020. The 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).

[0149] 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 delivered to other components of the device 1005. The receiver 1010 may be a reference Fig.13 Examples of various aspects of the transceiver 1320 are described. The receiver 1010 may utilize a single antenna or a set of antennas.

[0150] The communication manager 1015 may: communicate with the base station through the component carrier set according to the carrier aggregation configuration; based on being connected to the base station, receive DCI from 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 data transmission set through the two or more component carriers; and send or receive a data transmission set through the scheduled two or more component carriers based on receiving the DCI. The communication manager 1015 may be an example of various aspects of the communication manager 1310 described herein.

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

[0152] The communication manager 1015 or its subcomponents can be physically located in various locations, including being distributed so that portions of the functionality are implemented by one or more physical components at different physical locations. In some examples, the communication manager 1015 or its subcomponents can be independent and distinct components according to various aspects of the present disclosure. In some examples, according to various aspects of the present disclosure, the communication manager 1015 or its subcomponents can 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 the present disclosure, or a combination thereof.

[0153] Transmitter 1020 can transmit signals generated by other components of device 1005. In some examples, transmitter 1020 can be co-located with receiver 1010 in a transceiver module. For example, transmitter 1020 can be a reference Fig.13 Examples of various aspects of the transceiver 1320 are described. The transmitter 1020 may utilize a single antenna or a set of antennas.

[0154] The actions performed by the UE communication manager 1015 described herein may be implemented to achieve one or more potential advantages (e.g., at a 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 over multiple component carriers. Another implementation may provide improved efficiency and throughput because the number of separate resources allocated for control signaling (e.g., DCI) to the UE 115 may be reduced.

[0155] Fig.11 A block diagram 1100 of a device 1105 supporting DCI for scheduling multiple component carriers according to various aspects of the present disclosure is illustrated. The device 1105 may be an example of various aspects of the device 1005 or UE 115 as described herein. The device 1105 may include a receiver 1110, a communication manager 1115, and a transmitter 1130. The device 1105 may also include at least one processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0156] 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 delivered to other components of the device 1105. The receiver 1110 may be a reference Fig.13 Examples of various aspects of the transceiver 1320 are described. The receiver 1010 may utilize a single antenna or a set of antennas.

[0157] The communication manager 1115 may be an example of aspects of the 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 the communication manager 1310 described herein.

[0158] The communication manager 1115 may communicate with the base station through the component carrier set according to the carrier aggregation configuration. The DCI reception manager 1120 may receive DCI from the base station based on connection to the base station, the DCI including one or more fields common to two or more component carriers from the component carrier set, and the DCI schedules a data transmission set through the two or more component carriers. The data transmission manager 1125 may send or receive a data transmission set through the scheduled two or more component carriers based on receiving the DCI.

[0159] Transmitter 1130 can transmit signals generated by other components of device 1105. In some examples, transmitter 1130 can be co-located with receiver 1110 in a transceiver module. For example, transmitter 1130 can be a reference Fig.13 Examples of various aspects of the transceiver 1320 are described. The transmitter 1130 may utilize a single antenna or a set of antennas.

[0160] Fig.12A block diagram 1200 of a communication manager 1205 supporting DCI for scheduling multiple component carriers in accordance with aspects of the present disclosure is illustrated. The communication manager 1205 may be an example of aspects of the communication manager 1015, the communication manager 1115, or the 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 with each other directly or indirectly (e.g., via one or more buses).

[0161] The communication manager 1210 may communicate with the base station through the component carrier set according to the carrier aggregation configuration. The DCI reception manager 1215 may receive DCI from the base station based on connection to the base station, the DCI including one or more fields common to two or more component carriers from the component carrier set, and the DCI schedules a data transmission set through the two or more component carriers. The data transmission manager 1220 may send or receive a data transmission set through the scheduled two or more component carriers based on receiving the DCI.

[0162] The component carrier configuration manager 1225 may receive a configuration message from a base station indicating a component carrier group including at least two or more component carriers, wherein receiving the DCI for scheduling 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 component carrier subset from the component carrier group, the component carrier subset including two or more component carriers, wherein sending or receiving the data transmission set over the two or more component carriers is based on receiving the indication of the component carrier subset.

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

[0164] 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, wherein the parameter set for each of the two or more component carriers is the same, and wherein receiving the DCI is based on receiving the configuration message.

[0165] 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 the two or more component carriers. In some examples, the component carrier configuration manager 1225 may identify parameter sets for 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 sets for the remaining component carriers are the same, and wherein receiving the DCI is based on receiving the configuration message.

[0166] The decoding manager 1230 may attempt to decode a downlink transmission set of the data transmission set. The feedback manager 1235 may send an acknowledgment information associated with the downlink transmission set to the base station, wherein 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 a TTI of one of the two or more component carriers.

[0167] In some cases, the DCI schedules a data transmission set over two or more component carriers for a TTI set. The data transmission parameter manager 1240 may, based on receiving the DCI, identify a first identifier for a first HARQ associated with the data transmission set during a first TTI of the TTI set. In some examples, the data transmission parameter manager 1240 may 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 TTI set. In some examples, the data transmission parameter manager 1240 may, based on receiving the DCI, identify a first timing parameter for sending the first HARQ associated with the data transmission set during a first TTI of the TTI set. In some examples, the data transmission parameter manager 1240 may increment the first timing parameter to generate a second timing parameter for sending the second HARQ associated with the data transmission set during a second TTI of the TTI set.

[0168] In some cases, the two or more component carriers are a first set of component carriers. In some cases, the one or more fields common to the first set of component carriers are a first set of one or more fields. In some cases, the set of data transmissions over the first set of component carriers is a first set of data transmissions. 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 set of data transmissions over the second set of two or more component carriers.

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

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

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

[0172] 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 that is different from the first subcarrier spacing.

[0173] Fig.13 A diagram of a system 1300 including a device 1305 supporting DCI for scheduling multiple component carriers according to various aspects of the present disclosure is shown. The device 1305 may be an example of a device 1005, a device 1105, or a UE 115 as described herein or a component thereof. The device 1305 may include components for two-way voice and data communications, 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 be in electronic communication via one or more buses (e.g., a bus 1345).

[0174] The communication manager 1310 can: communicate with the base station through the component carrier set according to the carrier aggregation configuration; based on being connected to the base station, receive DCI from the base station, the DCI including one or more fields common to two or more component carriers from the component carrier set, and the DCI schedules a data transmission set through the two or more component carriers; and send or receive a data transmission set through the scheduled two or more component carriers based on the received DCI.

[0175] I / O controller 1315 can manage input and output signals for device 1305. I / O controller 1315 can also manage peripheral devices that are not integrated into device 1305. In some cases, I / O controller 1315 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1315 can utilize a computer such as a MS- MS- 1305. In some 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 the processor. In some cases, a user may interact with the device 1305 via the I / O controller 1315 or via hardware components controlled by the I / O controller 1315.

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

[0177] 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 that is capable of sending or receiving multiple wireless transmissions simultaneously.

[0178] Memory 1330 may include random access memory (RAM) and read-only memory (ROM). 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, memory 1330 may include, among other things, a basic I / O system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices.

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

[0180] The code 1335 may include instructions for implementing various aspects of the present disclosure, including instructions for supporting wireless communications. The code 1335 may be stored in a non-transitory computer-readable medium such as a system memory or other type of memory. In some cases, the 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.

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

[0182] Fig.14 A block diagram 1400 of a device 1405 supporting DCI for scheduling multiple component carriers according to aspects of the present disclosure is shown. The device 1405 can be an example of aspects of the base station 105 as described herein. The device 1405 may include a receiver 1410, a communication manager 1415, and a transmitter 1420. The device 1405 may also include at least one processor. Each of these components can communicate with each other (e.g., via one or more buses).

[0183] 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 delivered to other components of the device 1405. The receiver 1410 may be a reference Fig.17 Examples of various aspects of the transceiver 1720 are described. The receiver 1410 may utilize a single antenna or a set of antennas.

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

[0185] 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 the present disclosure.

[0186] The communication manager 1415 or its subcomponents can be physically located in various locations, including being distributed so that portions of the functionality are implemented by one or more physical components at different physical locations. In some examples, the communication manager 1415 or its subcomponents can be independent and distinct components according to various aspects of the present disclosure. In some examples, according to various aspects of the present disclosure, the communication manager 1415 or its subcomponents can 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 the present disclosure, or combinations of these.

[0187] Transmitter 1420 can transmit signals generated by other components of device 1405. In some examples, transmitter 1420 can be co-located with receiver 1410 in a transceiver module. For example, transmitter 1420 can be a reference Fig.17 Examples of various aspects of the transceiver 1720 are described. The transmitter 1420 may utilize a single antenna or a set of antennas.

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

[0189] Fig.15A block diagram 1500 of a device 1505 supporting DCI for scheduling multiple component carriers according to aspects of the present disclosure is shown. The device 1505 can be an example of aspects of the device 1405 or 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 can communicate with each other (e.g., via one or more buses).

[0190] 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 delivered to other components of the device 1505. The receiver 1510 may be a reference Fig.17 Examples of various aspects of the transceiver 1720 are described. The receiver 1510 may utilize a single antenna or a set of antennas.

[0191] 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 as described herein.

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

[0193] Transmitter 1535 can transmit signals generated by other components of device 1505. In some examples, transmitter 1535 can be co-located with receiver 1510 in a transceiver module. For example, transmitter 1535 can be a reference Fig.17 Examples of various aspects of the transceiver 1720 are described. The transmitter 1535 can utilize a single antenna or a set of antennas.

[0194] Fig.16A block diagram 1600 of a communication manager 1605 supporting DCI for scheduling multiple component carriers in accordance with aspects of the present disclosure is shown. The communication manager 1605 can 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 can 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 can communicate with each other directly or indirectly (e.g., via one or more buses).

[0195] The communication manager 1610 can communicate with the UE through the component carrier set according to the carrier aggregation configuration. The DCI transmission component 1615 can send DCI to the UE based on the connection with the UE, the DCI including one or more fields common to two or more component carriers from the component carrier set, and the DCI schedules a data transmission set through the two or more component carriers. The data transmission component 1620 can send or receive a data transmission set through the scheduled two or more component carriers based on sending the DCI.

[0196] The component carrier configuration component 1625 can send a configuration message to the UE indicating a component carrier group including at least two or more component carriers, wherein sending the DCI that schedules the data transmission set is based on sending the configuration message indicating the two or more component carriers. In some examples, the component carrier configuration component 1625 can send an indication of a component carrier subset from the component carrier group, the component carrier subset including two or more component carriers, wherein sending or receiving the data transmission set over the two or more component carriers is based on sending the indication of the component carrier subset.

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

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

[0199] In some examples, component carrier configuration component 1625 can send 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 DCI is based on sending the configuration message. In some examples, component carrier configuration component 1625 can send a configuration message indicating a first parameter set for a first component carrier of 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 of the two or more component carriers are the same, and wherein sending the DCI is based on sending the configuration message.

[0200] Feedback receiving component 1630 can receive, from the UE, acknowledgment information associated with a downlink transmission set from the data transmission set, wherein 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 a TTI of one of the two or more component carriers.

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

[0202] In some cases, the two or more component carriers are a first set of component carriers. In some cases, the one or more fields common to the first set of component carriers are a first set of one or more fields. In some cases, the set of data transmissions over the first set of component carriers is a first set of data transmissions. 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 set of data transmissions over the second set of two or more component carriers.

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

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

[0205] In some examples, the component carrier configuration component 1625 can send a configuration message to the UE indicating a mapping from the 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. 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 that is different from the first subcarrier spacing.

[0206] Fig.17 A diagram of a system 1700 including a device 1705 supporting DCI for scheduling multiple component carriers according to various aspects of the present disclosure is shown. The device 1705 may be an example of a device 1405, a device 1505, or a base station 105 as described herein or a component thereof. The device 1705 may include components for two-way voice and data communications, including components for sending and receiving communications, including a communication manager 1710, a network communication manager 1715, a transceiver 1720, an antenna 1725, a memory 1730, a processor 1740, and an inter-station communication manager 1745. These components may be in electronic communication via one or more buses (e.g., a bus 1750).

[0207] The communication manager 1710 can: communicate with the UE through the component carrier set according to the carrier aggregation configuration; based on the connection with the UE, send DCI to the UE, the DCI including one or more fields common to two or more component carriers from the component carrier set, and the DCI schedules a data transmission set through the two or more component carriers; and based on sending the DCI, send or receive a data transmission set through the scheduled two or more component carriers.

[0208] The network communications manager 1715 may manage communications with the core network (eg, via one or more wired backhaul links). For example, the network communications manager 1715 may manage data communications transmissions for client devices such as one or more UEs 115.

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

[0210] 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 sending or receiving multiple wireless transmissions simultaneously.

[0211] Memory 1730 may include RAM, ROM, or a combination thereof. 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, memory 1730 may include, among other things, a BIOS that may control basic hardware or software operations, such as interacting with peripheral components or devices.

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

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

[0214] The code 1735 may include instructions for implementing various aspects of the present disclosure, including instructions for supporting wireless communications. The code 1735 may be stored in a non-transitory computer-readable medium such as a system memory or other type 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.

[0215] Fig.18 A flow chart illustrating a method 1800 for supporting DCI for scheduling multiple component carriers according to aspects of the present disclosure is shown. The operations of the method 1800 may be implemented by a UE 115 or components thereof as described herein. For example, the operations of the method 1800 may be implemented by reference to Figures 10 to 13In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the functions described below.

[0216] At 1805, the UE may communicate with the base station via a component carrier set according to the carrier aggregation configuration. The operations of 1805 may be performed according to the methods described herein. In some examples, aspects of the operations of 1805 may be as described in reference to Figures 10 to 13 The communication manager is executed.

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

[0218] At 1815, the UE may send or receive multiple data transmissions over two or more scheduled component carriers based at least in part on the received DCI. The operations of 1815 may be performed according to the methods described herein. In some examples, aspects of the operations of 1815 may be performed as described in reference to Figures 10 to 13 The data transfer manager is used to perform the above operations.

[0219] Fig.19 A flow chart illustrating a method 1900 for supporting DCI for scheduling multiple component carriers according to aspects of the present disclosure is shown. The operations of the method 1900 may be implemented by a UE 115 or components thereof as described herein. For example, the operations of the method 1900 may be implemented by reference to Figures 10 to 13 In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the functions described below.

[0220] At 1905, the UE may receive a configuration message from a base station indicating a component carrier group including at least two or more component carriers, wherein receiving DCI scheduling multiple data transmissions is based at least in part on receiving the configuration message indicating the two or more component carriers. The operations of 1905 may be performed according to the methods described herein. In some examples, aspects of the operations of 1905 may be performed as described in reference to Figures 10 to 13 The component carrier configuration manager is used to perform the operation.

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

[0222] The operations of 1910 may be performed according to the methods described herein. In some examples, aspects of the operations of 1910 may be performed as described in reference to Figures 10 to 13 The communication manager is executed.

[0223] At 1915, the UE may receive, based at least in part on being connected to the base station, DCI from 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 multiple data transmissions over the two or more component carriers. The operations of 1915 may be performed according to the methods described herein. In some examples, aspects of the operations of 1915 may be performed as described in reference to Figures 10 to 13 The DCI reception manager is used to perform the above operations.

[0224] At 1920, the UE may send or receive multiple data transmissions over two or more scheduled component carriers based at least in part on the received DCI. The operations of 1920 may be performed according to the methods described herein. In some examples, aspects of the operations of 1920 may be performed as described in reference to Figures 10 to 13 The data transfer manager is used to perform the above operations.

[0225] Fig. 20 A flow chart illustrating a method 2000 for supporting DCI for scheduling multiple component carriers according to aspects of the present disclosure is shown. The operations of the method 2000 may be implemented by a base station 105 or components thereof as described herein. For example, the operations of the method 2000 may be implemented by reference to Figures 14 to 17 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 various aspects of the functions described below.

[0226] At 2005, the base station may communicate with the UE via a component carrier set according to the carrier aggregation configuration. The operations of 2005 may be performed according to the methods described herein. In some examples, aspects of the operations of 2005 may be performed as described in reference to Figures 14 to 17 The communication manager is executed.

[0227] At 2010, the base station may send a DCI to the UE based at least in part on the connection with the UE, the DCI including one or more fields common to two or more component carriers from the component carrier set, the DCI scheduling multiple data transmissions through the two or more component carriers. The operations of 2010 may be performed according to the methods described herein. In some examples, aspects of the operations of 2010 may be performed as described in reference to Figures 14 to 17 The DCI transmission component is used to perform.

[0228] At 2015, the base station may send or receive multiple data transmissions over two or more scheduled component carriers based at least in part on sending the DCI. The operations of 2015 may be performed according to the methods described herein. In some examples, aspects of the operations of 2015 may be performed as described in reference to Figures 14 to 17 The data transmission component is used to perform the above operation.

[0229] Fig.21 A flow chart illustrating a method 2100 for supporting DCI for scheduling multiple component carriers according to aspects of the present disclosure is shown. The operations of the method 2100 may be implemented by a base station 105 or components thereof as described herein. For example, the operations of the method 2100 may be implemented by reference to Figures 14 to 17 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 various aspects of the functions described below.

[0230] At 2105, the base station may send 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 sending the DCI is based at least in part on sending the configuration message. The operations of 2105 may be performed according to the methods described herein. In some examples, aspects of the operations of 2105 may be performed as described with reference to Figures 14 to 17 The component carrier configuration component is executed.

[0231] At 2110, the base station may communicate with the UE via a component carrier set according to the carrier aggregation configuration. The operations of 2110 may be performed according to the methods described herein. In some examples, aspects of the operations of 2110 may be performed as described in reference to Figures 14 to 17 The communication component is used to perform the above.

[0232] At 2115, the base station may send a DCI to the UE based at least in part on the connection with the UE, the DCI including one or more fields common to two or more component carriers from the component carrier set, the DCI scheduling multiple data transmissions through the two or more component carriers. The operations of 2115 may be performed according to the methods described herein. In some examples, aspects of the operations of 2115 may be performed as described in reference to Figures 14 to 17 The DCI transmission component is used to perform.

[0233] At 2120, the base station may send or receive multiple data transmissions over two or more scheduled component carriers based at least in part on sending the DCI. The operations of 2120 may be performed according to the methods described herein. In some examples, aspects of the operations of 2120 may be performed as described in reference to Figures 14 to 17 The data transmission component is used to perform the above operation.

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

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

[0236] Aspect 2: The method according to Aspect 1 also includes: receiving a configuration message indicating a component carrier group including at least two or more component carriers from a base station, wherein receiving downlink control information for scheduling multiple data transmissions is at least partially based on receiving the configuration message indicating two or more component carriers.

[0237] Aspect 3: A method according to Aspect 2, wherein receiving downlink control information includes: receiving an indication of a component carrier subset from a component carrier group, the component carrier subset including two or more component carriers, wherein sending or receiving multiple data transmissions through the two or more component carriers is at least partially based on receiving the indication of the component carrier subset.

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

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

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

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

[0242] Aspect 8: The method according to any one of Aspects 1 to 7 further includes: 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 downlink control information is at least partially based on receiving the configuration message.

[0243] Aspect 9: The method according to any one of Aspects 1 to 8 further includes: receiving a configuration message indicating a first parameter set for a first component carrier among two or more component carriers; and identifying parameter sets for remaining component carriers among the two or more component carriers based at least in part on the first parameter set, 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 downlink control information is at least in part based on receiving the configuration message.

[0244] Aspect 10: The method according to any one of Aspects 1 to 9 further includes: attempting to decode a downlink transmission set of multiple data transmissions; and sending confirmation information associated with the downlink transmission set to a base station, wherein the confirmation 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 transmission time interval of one of the two or more component carriers.

[0245] Aspect 11: The method according to any one of aspects 1 to 10, wherein the downlink control information schedules multiple data transmissions over two or more component carriers for multiple transmission time intervals.

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

[0247] Aspect 13: The method according to any one of Aspects 11 to 12 further includes: identifying, at least in part based on received downlink control information, a first timing parameter for sending a first hybrid automatic repeat request associated with multiple data transmissions during a first transmission time interval of a 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 multiple data transmissions during a second transmission time interval of the plurality of transmission time intervals.

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

[0249] Aspect 15: The method according to Aspect 14 also includes: sending or receiving a second plurality of data transmissions through a second two or more component carrier sets based at least in part on receiving downlink control information, the downlink control information including a second one or more field sets that are common to the second two or more component carrier sets.

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

[0251] Aspect 17: The method according to aspect 16 further comprises: receiving a configuration message indicating a mapping from a common field to the first parameter and the second parameter from a base station.

[0252] Aspect 18: The method according to any one of aspects 16 to 17, wherein the first parameter and the second parameter are frequency domain resource allocation parameters, time domain resource allocation parameters, or both.

[0253] Aspect 19: A 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.

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

[0255] 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 scheduling multiple data transmissions is at least partially based on sending the configuration message indicating two or more component carriers.

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

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

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

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

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

[0261] 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.

[0262] 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 set 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.

[0263] Aspect 29: The method according to any one of Aspects 20 to 28 further includes: receiving confirmation information associated with a downlink transmission set from multiple data transmissions from a UE, wherein the confirmation 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 transmission time interval of one of the two or more component carriers.

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

[0265] Aspect 31: A method according to any one of Aspects 20 to 30, wherein the two or more component carriers are a first component carrier set; the one or more fields that are common to the first component carrier set are a first one or more field sets; the multiple data transmissions through the first component carrier set are a first multiple data transmissions; the downlink control information includes a second one or more field sets that are common to a second two or more component carrier sets; and the downlink control information schedules a second multiple data transmission through the second two or more component carrier sets.

[0266] Aspect 32: The method according to Aspect 31 also includes: sending or receiving a second plurality of data transmissions through a second two or more component carrier sets based at least in part on sending downlink control information, wherein the downlink control information includes a second one or more field sets that are common to the second two or more component carrier sets.

[0267] Aspect 33: A method according to any one of Aspects 31 to 32, wherein the first one or more field sets and the second one or more field sets share a field indicating a first parameter of a first plurality of data transmissions through a first component carrier set and a second parameter of a second plurality of data transmissions through a second two or more component carrier sets; and the first parameter is different from the second parameter.

[0268] Aspect 34: The method according to aspect 33 further includes: sending a configuration message to the UE indicating a mapping from the common field to the first parameter and the second parameter.

[0269] 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.

[0270] Aspect 36: A method according to any one of Aspects 20 to 35, 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.

[0271] Aspect 37: 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 perform a method according to any one of Aspects 1 to 19.

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

[0273] 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.

[0274] Aspect 40: 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 perform a method according to any one of aspects 20 to 36.

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

[0276] 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.

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

[0278] Although aspects of LTE, LTE-A, LTE-APro, or NR systems are described for illustrative purposes, and LTE, LTE-A, LTE-APro, or NR terminology is used in much of the description, the techniques described herein may be applicable beyond LTE, LTE-A, LTE-APro, or NR networks. For example, the techniques described may be applicable to various 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.

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

[0280] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or executed using a general purpose processor, a DSP, an ASIC, a CPU, 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 herein. A general purpose processor may be a microprocessor, but in an 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, a plurality of microprocessors, a combination of one or more microprocessors combined with a DSP core, or any other such configuration).

[0281] The functions described herein can be implemented with hardware, software executed by a processor, or any combination thereof. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other, software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable programs, execution threads, processes, or functions. If implemented with software executed by a processor, these functions can be stored on a computer-readable medium or transmitted via a computer-readable medium as one or more instructions or codes. 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, hardware, hard wiring, or any combination thereof executed by a processor. The features that implement the functions can also be physically located in various locations, including being distributed so that the various parts of the functions are implemented at different physical locations.

[0282] Computer readable medium includes two kinds of non-temporary computer storage medium and communication medium, and communication medium includes any medium that is convenient to transfer computer program from one place to another place.Non-temporary storage medium can be any available medium that can be accessed by general or special computer.By way of example and not limitation, non-temporary computer readable medium can include RAM, ROM, electrically erasable programmable read-only memory (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage, disk storage or other magnetic storage device, or can be used for carrying or storing desired program code parts in the form of instruction or data structure, and can be accessed by general or special computer or general or special processor any other non-temporary medium.In addition, any connection is appropriately referred to as computer readable medium.For example, if software is sent from website, server or other remote source using coaxial cable, optical cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, etc., then coaxial cable, optical fiber cable, twisted pair, DSL, or wireless technology such as infrared, radio and microwave, etc. are all included in the definition of computer readable medium. Disk and disc as used herein include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, wherein disks usually reproduce data magnetically, while discs reproduce data optically via lasers. Combinations of the above items are also included within the scope of computer-readable media.

[0283] As used herein (including in the claims), "or" as used in a list of items (e.g., a list of items beginning with a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, without departing from the scope of the present disclosure, an exemplary step described as "based on condition A" can be based on both condition A and condition B. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part 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 adopted individually, or any combination of two or more of the listed items can be adopted. For example, if a composition is described as containing components A, B, and / or C, 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.

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

[0285] The description set forth herein in conjunction with the accompanying drawings describes example configurations and does not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "superior to other examples." The detailed description includes specific details to provide an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

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

Claims

1. A method for wireless communication, comprising: receiving a configuration message indicating a component carrier group from a network entity, the component carrier group comprising a component carrier set of at least two or more component carriers, wherein the component carrier set is configured according to carrier aggregation; communicating with the network entity via the set of component carriers configured according to the carrier aggregation; receiving downlink control information from the network entity based at least in part on being connected to the network entity, the downlink control information comprising one or more fields common to the two or more component carriers, the downlink control information scheduling a plurality of data transmissions over the two or more component carriers, wherein receiving the downlink control information scheduling the plurality of data transmissions is based at least in part on receiving the configuration message indicating the two or more component carriers, wherein receiving the downlink control information comprises: receiving an indication of a component carrier subset from the component carrier group, the component carrier subset comprising the two or more component carriers, wherein receiving the indication of the component carrier subset comprises: receiving an indication of a first component carrier from the component carrier group within the component carrier subset; and receiving an indication of a number of consecutive component carriers from the component carrier group within the component carrier subset; and The plurality of data transmissions are sent or received over the scheduled two or more component carriers based at least in part on receiving the downlink control information, wherein sending or receiving the plurality of data transmissions over the two or more component carriers is based at least in part on receiving the indication of the subset of component carriers.

2. The method according to claim 1, further comprising: A configuration message is received 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 based at least in part on receiving the configuration message.

3. The method according to claim 1, further comprising: receiving a configuration message indicating a first set of parameters for a first component carrier of the two or more component carriers; as well as and identifying parameter sets for remaining component carriers of the two or more component carriers based at least in part on the first set of parameters, 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 based at least in part 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; as well as sending, to the network entity, acknowledgment information associated with the downlink transmission set, wherein the acknowledgment information comprises 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 of claim 1, wherein the downlink control information schedules the plurality of data transmissions over the two or more component carriers for a plurality of transmission time intervals, the method further comprising: identifying, 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 based at least in part on receiving the downlink control information; as well as The first identifier is incremented 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 of claim 1, wherein the downlink control information schedules the plurality of data transmissions over the two or more component carriers for a plurality of transmission time intervals, the method further comprising: identifying, based at least in part on receiving the downlink control information, 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; as well as The first timing parameter is incremented 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 component carrier set; The one or more fields that are common to the first set of component carriers are a first group of one or more fields; the plurality of data transmissions over the first set of component carriers is 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 set of two or more component carriers; and The downlink control information schedules a second plurality of data transmissions over the second set of two or more component carriers.

8. A method for wireless communication, comprising: Sending a configuration message indicating a component carrier group to a user equipment UE, the component carrier group comprising a component carrier set of at least two or more component carriers, wherein the component carrier set is configured according to carrier aggregation; communicating with the UE via the set of component carriers configured according to the carrier aggregation; sending downlink control information to the UE based at least in part on connecting with the UE, the downlink control information comprising one or more fields common to the two or more component carriers, the downlink control information scheduling a plurality of data transmissions over the two or more component carriers, wherein sending the downlink control information scheduling the plurality of data transmissions is based at least in part on sending the configuration message indicating the two or more component carriers, wherein sending the downlink control information comprises: sending 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, wherein sending the indication of the subset of component carriers comprises: sending an indication of a first component carrier from the component carrier group within the subset of component carriers; and sending an indication of a number of consecutive component carriers from the component carrier group within the subset of component carriers; and The plurality of data transmissions are sent or received over the scheduled two or more component carriers based at least in part on sending the downlink control information, wherein sending or receiving the plurality of data transmissions over the two or more component carriers is based at least in part on sending the indication of the subset of component carriers.

9. An apparatus for wireless communication, comprising: at least one processor; a memory coupled to the at least one processor; as well as instructions stored in the memory and executable by the at least one processor to cause the apparatus to: receiving a configuration message indicating a component carrier group from a network entity, the component carrier group comprising a component carrier set of at least two or more component carriers, wherein the component carrier set is configured according to carrier aggregation; communicating with the network entity via the set of component carriers configured according to the carrier aggregation; receiving downlink control information from the network entity based at least in part on being connected to the network entity, the downlink control information comprising one or more fields common to the two or more component carriers, the downlink control information scheduling a plurality of data transmissions over the two or more component carriers, wherein receiving the downlink control information scheduling the plurality of data transmissions is based at least in part on receiving the configuration message indicating the two or more component carriers, wherein receiving the downlink control information comprises: receiving an indication of a component carrier subset from the component carrier group, the component carrier subset comprising the two or more component carriers, wherein receiving the indication of the component carrier subset comprises: receiving an indication of a first component carrier from the component carrier group within the component carrier subset; and receiving an indication of a number of consecutive component carriers from the component carrier group within the component carrier subset; and The plurality of data transmissions are sent or received over the scheduled two or more component carriers based at least in part on receiving the downlink control information, wherein sending or receiving the plurality of data transmissions over the two or more component carriers is based at least in part on receiving the indication of the subset of component carriers.

10. The device of claim 9, wherein the instructions are further executable by the at least one processor to cause the device to: A configuration message is received 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 based at least in part on receiving the configuration message.

11. The device of claim 9, wherein the instructions are further executable by the at least one processor to cause the device to: receiving a configuration message indicating a first set of parameters for a first component carrier of the two or more component carriers; and and identifying parameter sets for remaining component carriers of the two or more component carriers based at least in part on the first set of parameters, 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 based at least in part on receiving the configuration message.

12. The device of claim 9, wherein the instructions are further executable by the at least one processor to cause the device to: 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 comprises 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 of claim 9, wherein the downlink control information schedules the plurality of data transmissions over the two or more component carriers for a plurality of transmission time intervals, the instructions being further executable by the at least one processor to cause the apparatus to: identifying, 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 based at least in part on receiving the downlink control information; and The first identifier is incremented 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 of claim 9, wherein the downlink control information schedules the plurality of data transmissions over the two or more component carriers for a plurality of transmission time intervals, the instructions being further executable by the at least one processor to cause the apparatus to: identifying, during a first transmission time interval of the plurality of transmission time intervals, first timing parameters for transmitting a first hybrid automatic repeat request associated with the plurality of data transmissions based at least in part on receiving the downlink control information; and The first timing parameter is incremented 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 device according to claim 9, wherein: The two or more component carriers are a first component carrier set; The one or more fields that are common to the first set of component carriers are a first group of one or more fields; the plurality of data transmissions over the first set of component carriers is 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 set of two or more component carriers; and The downlink control information schedules a second plurality of data transmissions over the second set of two or more component carriers.

16. An apparatus for wireless communication, comprising: at least one processor; a memory coupled to the at least one processor; as well as instructions stored in the memory and executable by the at least one processor to cause the apparatus to: Sending a configuration message indicating a component carrier group to a user equipment UE, the component carrier group comprising a component carrier set of at least two or more component carriers, wherein the component carrier set is configured according to carrier aggregation; communicating with the UE via the set of component carriers configured according to the carrier aggregation; sending downlink control information to the UE based at least in part on connecting with the UE, the downlink control information comprising one or more fields common to the two or more component carriers, the downlink control information scheduling a plurality of data transmissions over the two or more component carriers, wherein sending the downlink control information scheduling the plurality of data transmissions is based at least in part on sending the configuration message indicating the two or more component carriers, wherein sending the downlink control information comprises: sending 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, wherein sending the indication of the subset of component carriers comprises: sending an indication of a first component carrier from the component carrier group within the subset of component carriers; and sending an indication of a number of consecutive component carriers from the component carrier group within the subset of component carriers; and The plurality of data transmissions are sent or received over the scheduled two or more component carriers based at least in part on sending the downlink control information, wherein sending or receiving the plurality of data transmissions over the two or more component carriers is based at least in part on sending the indication of the subset of component carriers.

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

18. A computer readable medium having stored thereon instructions which, 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 which, when executed by a processor, cause the processor to perform the method according to any one of claims 1 to 8.

Images