Providing zero-power channel state information reference signal and rate matching configuration in carrier aggregation

Abstract

Methods, systems, and devices for wireless communications are described. A base station may send downlink control information (DCI) to a user equipment (UE) that indicates a joint field of at least a first component carrier (CC) and a second component carrier for a carrier aggregation configuration. For example, the joint field may include a rate matching (RM) indication for the first CC and the second CC, a zero-power channel state information reference signal (ZP‑CSI‑RS) indication for the first CC and the second CC, or both. In some cases, the RM indication may include a common RM resource (RMR) configuration applicable to both the first CC and the second CC or a per-CC RMR configuration indicating a separate RMR for each CC. In addition, the ZP‑CSI‑RS indication may include a set identifier that indicates a resource set of ZP‑CSI‑RS resources for both the first CC and the second CC.

Description

[0001] Cross-references

[0002] This patent application claims priority to the following applications: U.S. patent application No. 17 / 225,912, filed by TAKEDA et al. on April 8, 2021, entitled “DOWNLINK CONTROL INFORMATION DESIGN FOR MULTI-COMPONENT CARRIERSCHEDULING”; and U.S. Provisional Patent Application No. 63 / 008,437, filed by TAKEDA et al. on April 10, 2020, entitled “DOWNLINK CONTROL INFORMATION DESIGN FOR MULTI-COMPONENT CARRIERSCHEDULING”; each of the above applications is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following relates generally to wireless communications, and more particularly to downlink control information (DCI) design for multiple component carrier (CC) scheduling. 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 (e.g., long term evolution (LTE) systems, improved LTE (LTE-A) systems or LTE-A Pro systems) and fifth generation (5G) systems (which may be referred to as new radio (NR) systems). These systems may use technologies such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA) or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations or one or more network access nodes, each base station or network access node simultaneously supporting communication for multiple communication devices (which may be further referred to as user equipment (UE)).

[0005] In some wireless communication systems, a UE may support carrier aggregation (CA), wherein the UE communicates with multiple cells simultaneously. For example, the UE may communicate with a first base station (e.g., a primary cell (PCell) or a first component carrier (CC)) and with a second base station (e.g., a secondary cell (SCell) or a second CC) simultaneously. Additionally or alternatively, a single base station may include multiple cells (e.g., both a PCell and a SCell or multiple CCs), wherein the UE communicates with two or more cells on a single base station simultaneously. Efficient techniques for implementing carrier aggregation communications are desired. Summary of the invention

[0006] The described technology relates to improved methods, systems, devices and apparatuses for supporting downlink control information (DCI) design for multi-component carrier (CC) scheduling. In summary, the described technology provides for a base station to send a DCI to a user equipment (UE), the DCI indicating a joint field for at least a first CC and a second CC in a carrier aggregation configuration. For example, the joint field may include a rate matching (RM) indication for the first CC and the second CC, a zero power channel state information reference signal (ZP-CSI-RS) indication for the first CC and the second CC, or a combination thereof. Subsequently, the UE and the base station can then communicate based on the DCI and the joint field. In some cases, the RM indication may include a common RM resource (RMR) configuration applicable to both the first CC and the second CC, a per-CC RMR configuration indicating a separate (e.g., or the same) RMR for each CC in the CC, or a combination thereof. In addition, the ZP-CSI-RS indication may include a set identifier indicating a resource set of ZP-CSI-RS resources for both the first CC and the second CC.

[0007] A method of wireless communication at a UE is described. The method may include: connecting to a base station through a first CC and a second CC according to a carrier aggregation configuration; receiving a DCI including a joint field from the base station, the joint field including one or more of an RM indication for the first CC and the second CC or a zero-power reference signal indication for the first CC and the second CC; and communicating with the base station according to the carrier aggregation configuration based on the DCI including the joint field.

[0008] An apparatus for wireless communication at a UE is described. The apparatus may include: at least one processor, a memory coupled (e.g., operatively, communicatively, functionally, electronically, or electrically) to the at least one processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to perform the following operations: connect to a base station through a first CC and a second CC according to a carrier aggregation configuration; receive a DCI including a joint field from the base station, the joint field including one or more of an RM indication for the first CC and the second CC or a zero-power reference signal indication for the first CC and the second CC; and communicate with the base station according to the carrier aggregation configuration based on the DCI including the joint field.

[0009] Another apparatus for wireless communication at a UE is described. The apparatus may include: a unit for connecting to a base station through a first CC and a second CC according to a carrier aggregation configuration; a unit for receiving a DCI including a joint field from the base station, the joint field including one or more of an RM indication for the first CC and the second CC or a zero-power reference signal indication for the first CC and the second CC; and a unit for communicating with the base station according to the carrier aggregation configuration based on the DCI including the joint field.

[0010] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by at least one processor to: connect to a base station through a first CC and a second CC according to a carrier aggregation configuration; receive a DCI including a joint field from the base station, the joint field including one or more of an RM indication for the first CC and the second CC or a zero-power reference signal indication for the first CC and the second CC; and communicate with the base station according to the carrier aggregation configuration based on the DCI including the joint field.

[0011] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for determining a common RMR from a common set of RMR configurations for the first CC and the second CC based on the joint field for the RM indication.

[0012] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for receiving an indication of the common RMR configuration set from the base station via radio resource control (RRC) signaling.

[0013] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for receiving, from the base station via DCI, a triggering field for a dynamic RM for the common RMR for the first CC and the second CC.

[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, each bit of the joint field for the RM indication may include an indication of an RMR group configured for the common RMR configuration.

[0015] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for determining a first RMR for the first CC and a second RMR for the second CC based on the joint field for the RM indication.

[0016] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: receiving an indication of a per-CC RMR configuration for each CC in the carrier aggregation configuration from the base station, wherein the first RMR and the second RMR may be determined based on the per-CC RMR configuration.

[0017] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for receiving a trigger field for a dynamic RM for the first RMR, the second RMR, or both from the base station via a DCI.

[0018] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, each bit of the joint field for the RM indication may include an indication of an RMR group configured for each CC in the carrier aggregation configuration.

[0019] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: determining that a CC in the carrier aggregation configuration may not be configured with a corresponding RMR group; and avoiding performing an RM process for the CC based on the determination that the corresponding RMR group may not be configured for the CC.

[0020] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: receiving an additional field for an additional RM indication for the second CC from the base station, wherein communication with the base station may be based on the additional RM indication.

[0021] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: determining a zero power reference signal configuration for the first CC and the second CC from the base station based on the joint field for the zero power reference signal indication.

[0022] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for receiving, from the base station, a second additional field of an additional zero-power reference signal indication for the second CC.

[0023] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: receiving a trigger field for a set identifier associated with the zero power reference signal indication from the base station; and determining a resource set for the zero power reference signal indication based on the set identifier, wherein the resource set can be used for the first CC and the second CC.

[0024] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: determining that a CC in the carrier aggregation configuration may not be configured with a zero-power reference signal resource set corresponding to the determined resource set, wherein the trigger field may be ignored for the CC based on the determination that the zero-power reference signal resource set may not be configured for the CC.

[0025] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the trigger field may be received via a DCI.

[0026] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the zero-power reference signal indication may include a ZP-CSI-RS resource set indication.

[0027] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the RM indication may include a RM mode group indication.

[0028] A method of wireless communication at a base station is described. The method may include: connecting to a UE through a first CC and a second CC according to a carrier aggregation configuration; sending a DCI including a joint field to the UE, the joint field including one or more of an RM indication for the first CC and the second CC or a zero-power reference signal indication for the first CC and the second CC; and communicating with the UE according to the carrier aggregation configuration based on the DCI including the joint field.

[0029] An apparatus for wireless communication at a base station is described. The apparatus may include: at least one processor, a memory coupled (e.g., operatively, communicatively, functionally, electronically, or electrically) to the at least one processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to perform the following operations: connect to a UE through a first CC and a second CC according to a carrier aggregation configuration; send a DCI including a joint field to the UE, the joint field including one or more of an RM indication for the first CC and the second CC or a zero-power reference signal indication for the first CC and the second CC; and communicate with the UE according to the carrier aggregation configuration based on the DCI including the joint field.

[0030] Another apparatus for wireless communication at a base station is described. The apparatus may include: a unit for connecting to a UE through a first CC and a second CC according to a carrier aggregation configuration; a unit for sending a DCI including a joint field to the UE, the joint field including one or more of an RM indication for the first CC and the second CC or a zero-power reference signal indication for the first CC and the second CC; and a unit for communicating with the UE according to the carrier aggregation configuration based on the DCI including the joint field.

[0031] A non-transitory computer-readable medium storing code for wireless communication at a base station is described. The code may include instructions executable by at least one processor to: connect to a UE through a first CC and a second CC according to a carrier aggregation configuration; send a DCI including a joint field to the UE, the joint field including one or more of an RM indication for the first CC and the second CC or a zero-power reference signal indication for the first CC and the second CC; and communicate with the UE according to the carrier aggregation configuration based on the DCI including the joint field.

[0032] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for sending an indication of a common RMR from a common RMR configuration set for the first CC and the second CC in the joint field for the RM indication.

[0033] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for sending an indication of the common RMR configuration set to the UE via RRC signaling.

[0034] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for sending a triggering field for a dynamic RM for the common RMR for the first CC and the second CC to the UE via a DCI.

[0035] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, each bit of the joint field for the RM indication may include an indication of an RMR group configured for the common RMR configuration.

[0036] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for sending a first RMR for the first CC and a second RMR for the second CC in the joint field for the RM indication.

[0037] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: sending an indication of a per-CC RMR configuration for each CC in the carrier aggregation configuration to the UE, wherein the first RMR and the second RMR may be determined based on the per-CC RMR configuration.

[0038] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for sending a triggering field for a dynamic RM for the first RMR, the second RMR, or both to the UE via a DCI.

[0039] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, each bit of the joint field for the RM indication may include an indication of an RMR group configured for each CC in the carrier aggregation configuration.

[0040] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: sending an additional field for an additional RM indication for the second CC to the UE, wherein communication with the UE may be based on the additional RM indication.

[0041] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: sending a zero-power reference signal configuration for the first CC and the second CC to the UE based on the zero-power reference signal indication in the joint field of the DCI.

[0042] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, means, or instructions for sending a second additional field indicating an additional zero-power reference signal for the second CC to the UE.

[0043] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following operations: determining a resource set for the zero-power reference signal indication, wherein the resource set can be used for the first CC and the second CC; and sending a trigger field for a set identifier associated with the zero-power reference signal indication to the UE, wherein the set identifier corresponds to the determined resource set.

[0044] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the trigger field may be sent via a DCI.

[0045] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the zero-power reference signal indication may include a ZP-CSI-RS resource set indication.

[0046] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the RM indication may include a RM mode group indication. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] Figure 1 An example of a system for wireless communications supporting downlink control information (DCI) design for multiple component carrier (CC) scheduling in accordance with aspects of the present disclosure is shown.

[0048] Figure 2 An example of a wireless communication system supporting DCI design for multi-CC scheduling in accordance with aspects of the present disclosure is shown.

[0049] Figure 3A and Figure 3B An example of a rate matching (RM) indicator supporting DCI design for multi-CC scheduling in accordance with aspects of the present disclosure is shown.

[0050] Figure 4A and Figure 4B Examples of multi-carrier configurations supporting DCI designs for multi-CC scheduling in accordance with aspects of the present disclosure are shown.

[0051] Figure 5 Examples of multi-carrier configurations supporting DCI designs for multi-CC scheduling in accordance with aspects of the present disclosure are shown.

[0052] Figure 6 An example of a DCI design supporting multi-CC scheduling according to aspects of the present disclosure is shown.

[0053] Figure 7 An example of a process flow supporting DCI design for multi-CC scheduling in accordance with aspects of the present disclosure is shown.

[0054] Figure 8 and Fig. 9 A block diagram of an apparatus supporting DCI design for multi-CC scheduling in accordance with aspects of the present disclosure is shown.

[0055] Fig.10 A block diagram of a user equipment (UE) communication manager supporting DCI design for multi-CC scheduling in accordance with aspects of the present disclosure is shown.

[0056] Fig.11 A diagram of a system including devices supporting DCI design for multi-CC scheduling is shown in accordance with aspects of the present disclosure.

[0057] Fig.12 and Fig.13 A block diagram of an apparatus supporting DCI design for multi-CC scheduling in accordance with aspects of the present disclosure is shown.

[0058] Fig.14 A block diagram of a base station communication manager supporting DCI design for multi-CC scheduling in accordance with aspects of the present disclosure is shown.

[0059] Fig.15 A diagram of a system including devices supporting DCI design for multi-CC scheduling is shown in accordance with aspects of the present disclosure.

[0060] Figures 16 to 20 A flow chart illustrating a method of supporting DCI design for multi-CC scheduling according to aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0061] Some wireless communication systems may support communication between user equipment (UE) and base stations on multiple aggregated component carriers (CCs), a feature known as carrier aggregation. For example, a base station may send the same downlink message to a UE across multiple CCs of a carrier aggregation configuration, enabling the UE to combine downlink messages received on multiple CCs to enhance the reliability of successful reception and decoding of downlink information. In some cases, a base station may send a separate message to configure communications on each CC of a carrier aggregation configuration. For example, a base station may send a first downlink control information (DCI) to configure transmission parameters for a first CC, or send a second DCI to configure transmission parameters for a second CC. However, sending multiple DCIs may increase signaling overhead based on the use of a large amount of resources to indicate different transmission parameters for each CC.

[0062] As described herein, a base station may send a DCI to indicate together joint CC scheduling transmission parameters for downlink communications across multiple CCs. For example, a base station may send a joint field to a UE in a DCI, the joint field including a rate matching (RM) indication for a first CC and a second CC, a zero power channel state information reference signal (ZP-CSI-RS) indication for a first CC and a second CC, or a combination thereof. Subsequently, the UE and the base station may then communicate based on the DCI and the joint field. In some cases, the RM indication may include a common RM resource (RMR) configuration applicable to both the first CC and the second CC, a per-CC RMR configuration indicating a separate (e.g., or the same) RMR for each CC in the CC, or a combination thereof. In addition, the ZP-CSI-RS indication may include a set identifier indicating a resource set of ZP-CSI-RS resources for both the first CC and the second CC.

[0063] Various aspects of the present disclosure are first described in the context of a wireless communication system. In addition, various aspects of the present disclosure are illustrated by additional wireless communication systems, RM indicators, multi-carrier configurations, DCI designs, and process flows. Various aspects of the present disclosure are further illustrated by apparatus diagrams, system diagrams, and flow charts relating to DCI designs for multi-CC scheduling, and various aspects of the present disclosure are described with reference to these diagrams.

[0064] Figure 1An example of a wireless communication system 100 supporting a DCI design for multi-CC scheduling according to aspects of the present disclosure is shown. The wireless communication system 100 may include one or more base stations 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an improved LTE (LTE-A) network, an LTE-A Pro network, or a new radio (NR) network. In some examples, the wireless communication system 100 may support enhanced broadband communications, ultra-reliable (e.g., mission-critical) communications, low-latency communications, or communications with low-cost and low-complexity devices, or any combination thereof.

[0065] Base stations 105 may be dispersed throughout a geographic area to form wireless communication system 100, and may be devices of different forms or capabilities. Base stations 105 and UEs 115 may communicate wirelessly via one or more communication links 125. Each base station 105 may provide a coverage area 110 over which UEs 115 and base stations 105 may establish one or more communication links 125. Coverage area 110 may be an example of a geographic area over which base stations 105 and UEs 115 may support transmission of signals according to one or more radio access technologies.

[0066] UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary, mobile, or both at different times. 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 can 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.

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

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

[0069] UE 115 may include or may be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or some other suitable terminology, where a "device" may also be referred to as a unit, station, terminal, or client, among other examples. 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, MP3 player, or video device), a camera, a gaming device, a navigation / positioning device (e.g., a GNSS (Global Navigation Satellite System) device based on, for example, GPS (Global Positioning System), BeiDou, GLONASS, or Galileo, or a ground-based device), a tablet computer, a laptop computer, a netbook, a smartbook, a personal computer, a smart device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, virtual reality goggles, 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 electricity 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 / healthcare 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 items such as appliances, or vehicles, meters, and other examples.

[0070] 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 be based on these technologies. For example, eMTC may include FeMTC (further eMTC), eFeMTC (further enhanced eMTC), mMTC (massive MTC), and NB-IoT may include eNB-IoT (enhanced NB-IoT) or FeNB-IoT (further enhanced NB-IoT).

[0071] The UE 115 described herein is capable of communicating 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, among other examples, such as Figure 1 shown.

[0072] The UE 115 and the base station 105 may wirelessly communicate with each other via one or more communication links 125 on one or more carriers. The term "carrier" may refer to a set of radio frequency spectrum resources having a defined physical layer structure for supporting the communication link 125. For example, a carrier for the communication link 125 may include a portion of a radio frequency spectrum band (e.g., a bandwidth 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 to coordinate operations for the carrier, user data, or other signaling. The wireless communication system 100 may support communication with the UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, the UE 115 may be configured with multiple downlink CCs and one or more uplink CCs. Carrier aggregation may be used with both frequency division duplex (FDD) CCs and time division duplex (TDD) CCs. Components within the wireless communication system may be coupled to each other (e.g., operationally, communicatively, functionally, electronically, and / or electrically).

[0073] In some examples (e.g., in a carrier aggregation configuration), a carrier may also have acquisition signaling or control signaling that coordinates operations for other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute Radio Frequency Channel Number (EARFCN)) and may be placed according to a channel grid to be discovered by a UE 115. A carrier may operate in a standalone mode, where a UE 115 performs initial acquisition and connection via a carrier, or a carrier may operate in a non-standalone mode, where a different carrier (e.g., of the same or different radio access technology) is used to anchor the connection.

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

[0075] 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 number 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)). A device of the wireless communication system 100 (e.g., a base station 105, a UE 115, or both) may have a hardware configuration that supports communication on a particular carrier bandwidth, or may be configurable to support communication 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 communication 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.

[0076] The signal waveform transmitted on the carrier may be composed of multiple subcarriers (e.g., using multicarrier 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, wherein the symbol period and the subcarrier spacing are inversely related. 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 the UE 115 and the higher the order of the modulation scheme, the higher the data rate for the UE 115 can be. Wireless communication resources may refer to a combination of radio frequency spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial layers may further increase the data rate or data integrity for communication with the UE 115.

[0077] One or more numerologies for a carrier may be supported, where the numerologies may include subcarrier spacing (Δf) and cyclic prefixes. A carrier may be divided into one or more BWPs with the same or different numerologies. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications for a UE 115 may be limited to the one or more active BWPs.

[0078] The basic time unit (which may be referred to as 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 time intervals for the base station 105 or the UE 115 may be expressed as multiples of a maximum supported discrete Fourier transform (DFT) size). The time intervals of the 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., ranging from 0 to 1023).

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

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

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

[0082] Each base station 105 can provide communication coverage via one or more cells (e.g., macro cells, small cells, hot spots or other types of cells, or any combination thereof). The term "cell" can refer to a logical communication entity used to communicate with the base station 105 (e.g., on a carrier), and can be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID) or other identifier) ​​for distinguishing adjacent cells. In some examples, a cell can also refer to a geographic coverage area 110 or a portion of a geographic coverage area 110 (e.g., a sector) on which a logical communication entity operates. Depending on various factors (such as the capabilities of the base station 105), the range of such a cell can range from a smaller area (e.g., a structure, a subset of a structure) to a larger area. For example, a cell can be or include a building, a subset of a building, or an external space between or overlapping geographic coverage areas 110, as well as other examples.

[0083] A macro cell typically covers a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 115 with a service subscription to a network provider that supports the macro cell. A small cell may be associated with a lower power base station 105 than a macro cell, and the small cell may operate in the same or different (e.g., licensed, unlicensed) frequency band as the macro cell. A small cell may provide unrestricted access to a UE 115 with a service subscription to a network provider, or may provide restricted access to a UE 115 associated with a small cell (e.g., a UE 115 in a closed subscriber group (CSG), a UE 115 associated with a user in a residence or office). A base station 105 may support one or more cells, and may also support the use of one or more CCs to communicate on one or more cells.

[0084] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.

[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 respective 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 prioritization of services, and mission-critical services can be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, mission-critical, and ultra-reliable low-latency can be used interchangeably in this article.

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

[0088] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connection, 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 unit (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 unit (UPF)) for routing packets to an external network or interconnecting to an external network. The control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management for UE 115 served by a base station 105 associated with the core network 130. User IP packets may be transmitted through a user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to a network operator IP service 150. Operator IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0089] Some of the network devices (e.g., 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 the UE 115 through one or more other access network transport entities 145 (which may be referred to as radio heads, smart radio heads, or transmit / receive points (TRPs)). Each access network transport 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 wavelengths range from approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features, but the waves may be sufficient to penetrate structures for macro cells to provide service to UEs 115 located indoors. Transmissions using UHF waves may be associated with smaller antennas and shorter distances (e.g., less than 100 kilometers) than transmissions using smaller frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0091] The wireless communication system 100 may also operate in a super high frequency (SHF) region using a frequency band from 3 GHz to 30 GHz (also referred to as a centimeter band) or in an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) (also referred to as a millimeter band). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between UE 115 and base station 105, and the EHF antenna of the corresponding device may be even smaller and more closely spaced than the UHF antenna. In some examples, this may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may suffer from even greater atmospheric attenuation and shorter distances than SHF or UHF transmissions. The technology disclosed herein may be employed across transmissions using one or more different frequency regions, and the designated use of frequency bands across these frequency regions may differ according to countries or regulatory agencies.

[0092] The wireless communication system 100 can utilize both licensed and unlicensed radio frequency 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 an unlicensed band (such as the 5 GHz industrial, scientific, and medical (ISM) band). When operating in an unlicensed radio frequency spectrum band, devices (such as base stations 105 and UEs 115) can employ carrier sensing for conflict detection and avoidance. In some examples, operations in unlicensed bands can be based on a carrier aggregation configuration combined with CCs operating in a licensed band (e.g., LAA). Operations in unlicensed spectrum can include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, as well as other examples.

[0093] The base station 105 or UE 115 may be equipped with multiple antennas, which may be used to employ technologies 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 (which 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 geographical locations. The base station 105 may have an antenna array having a number of 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.

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

[0095] 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, 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 specific orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals transmitted via antenna elements may 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 of the antenna elements may be defined by a set of beamforming weights associated with a specific orientation (e.g., relative to the antenna array of the transmitting device or the receiving device, or relative to some other orientation).

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

[0097] UE 115 and base station 105 can support retransmission of data to increase the possibility that the data is successfully received. Hybrid automatic repeat request (HARQ) feedback is a technology for increasing the possibility that data is correctly received on 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 and noise conditions). In some examples, the device can support the same time slot HARQ feedback, wherein the device can provide HARQ feedback for data received in the previous symbol in the time slot in a specific time slot. In other cases, the device can provide HARQ feedback in subsequent time slots or according to some other time interval.

[0098] In some wireless communication systems, a transmitting device (e.g., UE 115 or base station 105) may perform channel coding techniques so that a receiving device may receive a correct message sent by the transmitting device. RM may be an example of a channel coding technique, wherein the RM process may include repeating or puncturing bits of a channel according to a configured rate. The rate may indicate the number of repetitions, wherein the lower the rate, the more repetitions that may be performed. For example, a rate of 1 / 4 may result in 4 repetitions of a bit, and a rate of 1 / 3 may result in 3 repetitions of a bit. The transmitting device may be configured to perform RM according to the rate. In some cases, a number of repetitions associated with a rate less than 1 / 3 may not provide additional coding gain, and may result in inefficient utilization of allocated resources.

[0099] In some systems, a transmitting device (e.g., a base station 105) may use RM to determine and configure a set of bits to be sent to a receiving device (e.g., a UE 115). For example, the base station 105a may perform RM to generate a transmission for one or more redundancy versions (RVs) (e.g., to indicate where the bits of a codeword within an encoded information message start) including control information, data, or a combination thereof. The base station 105 may perform RM processes, such as repetition or puncturing, according to a coding rate. The coding rate may indicate a useful data ratio by indicating a ratio of information bits to coding bits. For example, a coding rate of 1 / 2 may indicate that two coded bits may be sent for each information bit, where 2 minus 1 bit is redundant. Therefore, the lower the coding rate, the more redundant bits the base station 105 may generate. In some cases, the lower the coding rate, the more resource elements may be needed for the base station 105 to send a higher number of bits.

[0100] The base station 105 may send an RM indicator in a DCI sent to the UE 115 to indicate how the UE 115 should perform an RM procedure when receiving a downlink message from the base station. In some cases, the UE 115 may be configured with up to two RM pattern groups (e.g., rateMatchPatternGroups), each of which includes a resource block (RB) / symbol level RM pattern. For example, the RM pattern may include a resource pattern around which the UE 115 should rate match a downlink channel (e.g., a physical downlink shared channel (PDSCH)). In some cases, the UE 115 may rate match around the union of all resources indicated in one or more signaled bitmaps. When the UE 115 is configured with two RM pattern groups, the number of bits of the RM indicator in the DCI may be two (2) bits. Thus, the first RM pattern group (e.g., rateMatchPatternGroup1) may correspond to the first bit of the RM indicator, and the second RM pattern group (e.g., rateMatchPatternGroup2) may correspond to the second bit of the RM indicator.

[0101] In addition, in some cases, a trigger for a channel state information reference signal (CSI-RS) in a downlink scheduling DCI (e.g., a zero power CSI-RS (ZP-CSI-RS) trigger) can indicate an RM mode for use by the UE 115. For example, the ZP-CSI-RS can be used for downlink channel state information (CSI) acquisition and interference measurement. The ZP-CSI-RS can also mask certain resource elements (REs) to make them unavailable for downlink channel (e.g., PDSCH) transmission. As indicated by the name ZP, no data or information can be sent in these REs. For example, a ZP-CSI-RS resource can prevent a downlink channel from being mapped to a set of REs. Therefore, the ZP-CSI-RS can be used to mute REs within a transmission point downlink channel (e.g., from the base station 105) to allow a configured CSI interference measurement (CSI-IM) to measure interference for different assumptions. In some cases, the ZP-CSI-RS can be configured with a 16-bit bitmap. Each bit may control whether a set of REs should be muted (1) or unmuted (0).For each transmission point, a ZP-CSI-RS configuration may be created based on the required CSI-IM configuration and the CSI-RS configuration used by the coordinating transmission points.

[0102] UE 115 may be configured with up to four (4) ZP-CSI-RS resource sets (e.g., ZP-CSI-RS resource sets) that provide RE-level rate matching patterns. When UE 115 is configured with these ZP-CSI-RS resource sets, the number of bits in the ZP-CSI-RS indicator carried in the DCI may be at most two (2) bits. The bit length of the DCI field for ZP-CSI-RS triggering may depend on the number of aperiodic ZP-CSI-RS resource sets configured in the DCI for UE 115 (e.g., at most two (2) bits).

[0103] Each non-zero code point of the ZP CSI-RS trigger in the DCI (e.g., DCI format 1_1) can trigger an aperiodic ZP-CSI-RS resource set in the aperiodic ZP-CSI-RS resource set list (e.g., aperiodic ZP-CSI-RS ResourceSetsToAddModList) for UE 115 to add by indicating the aperiodic ZP CSI-RS resource set identifier. For example, a first DCI code point (e.g., "01") may trigger a first resource set having a ZP-CSI-RS resource set identifier of one (1) (e.g., ZP-CSI-RS-ResourceSetIds=1), a second DCI code point (e.g., "10") may trigger a second resource set having a ZP-CSI-RS resource set identifier of two (2) (e.g., ZP-CSI-RS-ResourceSetIds=2), and a third DCI code point (e.g., "11") may trigger a third resource set having a ZP-CSI-RS resource set identifier of three (3) (e.g., ZP-CSI-RS-ResourceSetIds=3). In some cases, a fourth DCI code point (e.g., "00") may be reserved for not triggering aperiodic ZP-CSI-RS.

[0104] In some cases, the base station 105 may configure and indicate different transmission parameters, such as an RM indicator and / or a ZP-CSI-RS indicator, to the UE 115 in a DCI before sending a downlink message to the UE 115. If the UE 115 and the base station 105 communicate according to a carrier aggregation configuration including multiple CCs (e.g., or multiple base stations 105 communicating with the UE 115 on multiple CCs), the base station 105 may send a separate DCI for each CC to configure / indicate transmission parameters specific to each CC (e.g., even if similar transmission parameters are used for each CC). Therefore, sending separate DCI for multiple CCs may increase signaling overhead.

[0105] As described herein, the base station 105 and the UE 115 can use dynamic spectrum sharing (DSS) configuration as part of an enhancement to enable cross-carrier scheduling such that a single DCI can indicate transmission parameters for multiple CCs together. For example, as part of a DSS configuration for cross-carrier scheduling, a downlink channel (e.g., a physical downlink control channel (PDCCH)) can be received on a secondary cell (SCell) (e.g., or a second CC), the PDCCH scheduling a subsequent downlink channel (e.g., PDSCH) or uplink channel (e.g., a physical uplink shared channel (PUSCH)) on a primary cell (PCell) or a primary secondary cell (PSCell) (e.g., or a first CC). Additionally or alternatively, as part of a DSS configuration for cross-carrier scheduling, a downlink channel (e.g., PDCCH) can be received on a PCell, PSCell, or SCell, the PDCCH scheduling subsequent downlink channels (e.g., PDSCH) on multiple cells (e.g., multiple CCs or a PCell and SCell) using a single DCI. In some cases, the number of cells that can be scheduled simultaneously may be limited to two (2), and the increase in DCI size may be minimized. In addition, the total downlink channel blind decoding budget (e.g., PDCCH blind decoding budget) may not be affected by a single DCI. In some cases, these enhancements may not be specific to DSS and may be generally applicable to cross-carrier scheduling in carrier aggregation.

[0106] In some cases, multi-CC scheduling can be used to improve spectral efficiency by configuring multiple CCs using a single DCI instead of multiple DCIs corresponding to each CC. Alternatively, multiple DCIs for multi-CC scheduling may be sufficient (for example, when spectral efficiency is not an issue). In addition, non-DSS scenarios can generally be used to purely improve spectral efficiency. When a single DCI is used for multi-CC scheduling (for example, using DCI format 1_1 or 1_2), separate fields can be used (for example, in a single DCI for multi-CC scheduling, including a first field for the first CC and a second field for the second CC), or a joint field can be used (for example, in a single DCI for multi-CC scheduling, the joint field can jointly indicate the values ​​for the first CC and the second CC). However, techniques for indicating different parameters in a single DCI for multi-CC scheduling may not yet be defined.

[0107] The wireless communication system 100 may support an efficient technique for UE 115 to receive a DCI indicating a joint field of at least a first CC and a second CC for a carrier aggregation configuration. For example, the joint field may include an RM indication for the first CC and the second CC, a ZP-CSI-RS indication for the first CC and the second CC, or a combination thereof. Subsequently, the UE 115 may then communicate with the base station based on the DCI and the joint field. In some cases, the RM indication may include a common RMR configuration applicable to both the first CC and the second CC, a per-CC RMR configuration indicating a separate (e.g., or the same) RMR for each CC in the CC, or a combination thereof. In addition, the ZP-CSI-RS indication may include a set identifier indicating a resource set of ZP-CSI-RS resources for both the first CC and the second CC.

[0108] Figure 2 An example of a wireless communication system 200 that supports DCI design for multi-CC scheduling according to various aspects of the present disclosure is shown. In some examples, the wireless communication system 200 can implement aspects of the wireless communication system 100 or can be implemented by aspects of the wireless communication system 100. For example, the wireless communication system 200 may include a base station 105-a and a UE 115-a, which may be respectively as described in reference Figure 1 Examples of corresponding base stations 105 and UEs 115 described. In some cases, the base station 105-a can send configuration information to the UE 115-a on resources of the carrier 205 for a carrier aggregation configuration, which carrier aggregation configuration includes a first CC 210 (e.g., for communication with a PCell and / or a PSCell) and a second CC 215 (e.g., for communication with an SCell). In addition or alternatively, although not shown, the first CC 210 and the second CC 215 can be used to communicate with a separate base station 105 as part of the carrier aggregation configuration. In some cases, the carrier 205 and the first CC 210 can be the same carrier (e.g., carrying configuration information for the UE 115-a on the first CC 210 / PCell).

[0109] As described herein, the wireless communication system 200 may support a DCI design for a multi-CC scheduling configuration to indicate different transmission parameters for a first CC 210 and a second CC 215 in a single DCI. For example, as shown, the base station 105-a may send a DCI 220 (e.g., on resources of a carrier 205) to the UE 115-a to indicate an RM indicator 225 and / or a ZP-CSI-RS indicator 230. In some cases, the DCI 220 may include a joint field for the RM indicator 255 and / or the ZP-CSI-RS indicator 230, which configures a corresponding RMR for each CC and / or a ZP-CSI-RS resource set for each CC.

[0110] For example, when the RM indicator 225 includes a joint field for both the first CC 210 and the second CC 215, the single RM joint field may indicate a common RMR for multi-CC scheduling (e.g., for the first CC 210 and the second CC 215). In some cases, multiple common RMR configurations across multiple CCs may be provided by higher layer signaling (e.g., RRC signaling) from the base station 105-a, and the UE 115-a may determine the common RMR based on the multiple common RM configurations based on the joint field. In addition, the base station 105-a may send an additional field (e.g., on / off trigger) for a dynamic RM for the common RMR across multiple CCs for a scheduled downlink channel (e.g., PDSCH) indicated by the DCI 220 (e.g., or an additional DCI). In some cases, each bit of the joint field may indicate a different group (e.g., RM mode group, such as group 1 or group 2) configured for the UE 115a as a common RMR configuration for the first CC 210 and the second CC 215.

[0111] Additionally or alternatively, when the RM indicator 225 includes a joint field for both the first CC 210 and the second CC 215, the single RM joint field may indicate different RMRs for the first CC 210 and for the second CC 215 (e.g., multiple CCs). In some cases, a per-CC RMR configuration for each CC in the CC may be provided to the UE 115-a (e.g., by the base station 105a (e.g., by higher layer / RRC signaling)), and the UE 115-a may determine the corresponding RMR for each CC based on the per-CC RMR configuration and the joint field. In addition, the base station 105-a may send an additional field (e.g., on / off trigger) for a dynamic RM for separate RMRs across multiple CCs for a scheduled downlink channel (e.g., PDSCH) indicated by the DCI 220 (e.g., or an additional DCI). In some cases, each bit of the joint field may indicate a different group (e.g., RM mode group, such as group 1 or group 2) configured for the UE 115-a for each CC. If there is no corresponding RM mode group (eg, RM group) configured for the CC, the UE 115 - a may not perform RM on the corresponding downlink channel (eg, PDSCH) on the CC.

[0112] In some cases, when the ZP-CSI-RS indicator 230 includes a joint field for both the first CC 210 and the second CC 215, the DCI code point (e.g., "xx") for the ZP-CSI-RS indicator 230 may trigger resource sets having corresponding resource set identifiers (e.g., ZP-CSI-RS-ResourceSetIds=y) for both the first CC 210 and the second CC 215, respectively. If there is no corresponding ZP-CSI-RS resource set identifier for a CC, but the DCI code point still indicates a resource set for the CC, the UE 115-a may ignore the ZP-CSI-RS trigger (e.g., ZP-CSI-RS indicator 230) received in the DCI 220. Additionally or alternatively, if there is no corresponding ZP-CSI-RS resource set identifier for a CC, but the DCI code point still indicates a resource set for the CC, UE 115-a may ignore the ZP-CSI-RS trigger (e.g., ZP-CSI-RS indicator 230) for the CC without a corresponding resource set, but may apply PDSCH rate matching based on the indicator for the CC with a corresponding resource set.

[0113] Additionally or alternatively, the DCI 220 may also include separate fields for the RM indicator 225, the ZP-CSI-RS indicator 230, or both to indicate the respective RM pattern groups and / or ZP-CSI-RS resource sets for the first CC 210 and the second CC 215. For example, the DCI 220 may include up to two (2) 0 to 2 bit fields as the RM indicator 225 and / or the ZP-CSI-RS indicator 230 for the first CC 210 and the second CC 215, respectively.

[0114] Subsequently, after receiving the DCI 220 and determining the corresponding RM parameters and / or ZP-CSI-RS parameters, the UE 115-a may communicate with the base station 105-a on the first CC 210 and the second CC 215. For example, the base station 105-a may send one or more downlink messages to the UE 115-a on the first CC 210 and the second CC 215. Subsequently, the UE 115-a may attempt to receive and decode the downlink messages on the first CC 210 and the second CC 215 based on the RM indicator 225 and / or the ZP-CSI-RS indicator 230 (e.g., indicating the corresponding RM parameters and / or ZP-CSI-RS parameters) indicated in the DCI 220 (e.g., via a joint field or a separate field).

[0115] Figure 3A and Figure 3B Examples of RM indicators 300 and 301 supporting DCI design for multi-CC scheduling according to various aspects of the present disclosure are shown respectively. In some examples, the RM indicators 300 and 301 can implement aspects of the wireless communication system 100, the wireless communication system 200, or both, or can be implemented by aspects of the wireless communication system 100, the wireless communication system 200, or both. As shown in FIG. Figure 2 As described, the base station 105 may send a single DCI to configure together different transmission parameters (such as an RM indicator and a ZP-CSI-RS indicator) for multiple CCs, where the multiple CCs are used as part of a carrier aggregation configuration for communication between the base station 105 and the UE 115. For example, the base station 105 and the UE 115 may communicate on a first CC 305-a and a second CC 305-b according to the carrier aggregation configuration.

[0116] The RM indicator 300 may include a joint field indicating a joint RMR configuration 310 (e.g., JointRM-Config) indicating a different RM group 315 for each CC 305 in the CC 305. For example, each bit of the joint field may indicate a different RM group 315 (e.g., group 1 or group 2, such as a different RM mode group) jointly configured for the CC 305 (e.g., multiple CCs). That is, the first bit of the joint field may indicate a first RM group 315-a (e.g., RM-group1) from the RM mode list, and the second bit of the joint field may indicate a second RM group 315-b (e.g., RM-group2) from the RM mode list. Therefore, based on which bit is triggered (e.g., which bit has "1"), the UE 115 may identify which RM group (e.g., RM mode group) is to be used to perform row RM for two CCs 305 (e.g., the same RM group / common RMR is used for two CCs 305). In some cases, the RM mode list may be a common set of RMR configurations that is indicated by the base station 105 to the UE 115 (eg, via RRC signaling).

[0117] Additionally or alternatively, the RM indicator 301 may also include a joint field that indicates different per-CC RMR configurations 320 (e.g., different RMRs) for the CC 305. For example, each bit of the joint field may indicate a different RM group 315 (e.g., group 1 or group 2, such as a different RM mode group) configured for each CC 305. That is, each CC 305 may be configured with a separate per-CC RMR configuration 320 (e.g., a per-CC PDSCH-Config field), such as a first per-CC RMR 320-a configuration for a first CC 305-a and a second per-CC RMR 320-b for a second CC 305-b. Thus, the first bit of the joint field may indicate a first RM group 315-a (e.g., RM-group1) from the RM mode list, and the second bit of the joint field may indicate a second RM group 315-b (e.g., RM-group2) from the RM mode list. However, based on the per-CC RMR configuration 320, the first RM group 315-a and the second RM group 315-b may differ from the first CC 305-a to the second CC 305-b, so that different RMRs may be used for each CC 305 while still using a single joint field in the DCI.

[0118] Figure 4A and Figure 4BExamples of multi-carrier configurations 400 and 401 according to aspects of the present disclosure are shown. In some examples, the multi-carrier configurations 400 and 401 can implement aspects of the wireless communication system 100, the wireless communication system 200, or both or can be implemented by the wireless communication system 100, the wireless communication system 200, or both. For example, the base station 105 and the UE 115 can communicate according to the carrier aggregation configuration, such that a first CC using the carrier aggregation configuration communicates with the PCell 405 and a second CC using the carrier aggregation configuration communicates with the SCell 410. Additionally or alternatively, the PCell 405 can be a PSCell for communication between the UE 115 and the base station 105. In some cases, the PCell 415 (e.g., or PSCell) and the SCell 410 can be part of the same base station 105 or can be parts of different respective base stations 105.

[0119] Additionally, in some cases, the SCell 410 may not use DSS (e.g., non-DSS), and the PCell 405 may use DSS. For example, DSS communications may be used for lower frequency bands (e.g., less than 1 GHz), while non-DSS communications may be used for higher frequency bands (e.g., above 3.5 or 4.5 GHz). In some cases, a lower frequency band may be more suitable for communications on the PCell 405 (e.g., and / or PSCell) based on the lower frequency band being more suitable for an anchor channel (e.g., for receiving configuration information) or for mobility.

[0120] The multi-carrier configuration 400 may illustrate cross-carrier scheduling across the SCell 410 and the PCell 405. For example, the UE 115 may receive a DCI 415 on the SCell 410 that schedules a PDSCH 420 (e.g., or a PUSCH) on the PCell 405. In some cases, the SCell 410 may not include resources for uplink communications, so the UE 115 may not be able to transmit on the SCell 410, but may be able to transmit on the PCell 405. Therefore, the base station 105 including the SCell 410 may instruct the UE 115 to transmit on the PCell 405 based on signaling (e.g., the DCI 415) in the SCell 410. Additionally or alternatively, although not shown, the UE 115 may receive DCI 415 on the PCell 405 , wherein the DCI 415 may schedule subsequent transmissions (eg, PDSCH or PUSCH) on the SCell 410 as part of cross-carrier scheduling.

[0121] For the multi-carrier configuration 401, the UE 115 may receive a DCI 415 on the SCell 410, wherein the DCI 415 includes a joint scheduling for both the PCell 405 and the SCell 410. For example, the DCI 415 may schedule a first PDSCH 425a on the SCell 410 and a second PDSCH 425-b on the PCell 405. As described herein, the joint scheduling of the DCI 415 may include a joint field for configuring different transmission parameters for both the PCell 405 and the SCell 410 (e.g., on corresponding CCs).

[0122] Figure 5 An example of a multi-carrier configuration 500 according to aspects of the present disclosure is shown. In some examples, the multi-carrier configuration 500 can implement aspects of the wireless communication system 100, the wireless communication system 200, or both or can be implemented by the wireless communication system 100, the wireless communication system 200, or both. For example, the base station 105 and the UE 115 can communicate according to a carrier aggregation configuration, such that a first CC of the carrier aggregation configuration is used to communicate with the PCell 505, and a second CC of the carrier aggregation configuration is used to communicate with the SCell 510. Additionally or alternatively, the PCell 505 can be a PSCell for communication between the UE 115 and the base station 105. In some cases, the PCell 505 (e.g., or PSCell) and the SCell 510 can be part of the same base station 105 or can be part of different respective base stations 105.

[0123] In some cases, the PCell 505 (e.g., or PSCell) can be a DSS carrier using a first subcarrier spacing (SCS) (e.g., 15kHz), while the SCell 510 can be a non-DSS carrier using a second SCS (e.g., 30kHz) that is greater than the first SCS. In some cases, the SCell 510 can use a higher SCS based on using a higher frequency band for the non-DSS carrier. In addition, the PCell 505 can include uplink resources, while the SCell 510 may not have uplink resources (e.g., as part of a downlink-only carrier aggregation configuration). In some cases, both the PCell 505 and the SCell 510 can be located in a first frequency range (FR1). In addition, the SCell 510 (e.g., a non-DSS carrier) can be a carrier in an unlicensed band (e.g., an unlicensed carrier for NR communications, such as an NR-U carrier).

[0124] In some cases, cross-carrier scheduling from the SCell 510 to the PCell 505 may include a DCI 515-a that schedules a PDSCH 520-a (e.g., or a PUSCH) on the PCell 505. Therefore, this cross-carrier scheduling from the SCell 510 to the PCell 505 may not use a DCI from the PDCCH of the PCell 505 to the PDCCH of the SCell 510 (e.g., skipping the DCI). Additionally or alternatively, for multi-CC scheduling (e.g., joint scheduling), a DCI 515-b received on the SCell 510 may be included that schedules a PDSCH 520-b on the SCell 510 and schedules a PDSCH 520-c on the PCell 505. Based on this multi-CC scheduling, spectral efficiency may be improved by using a single DCI instead of multiple DCIs.

[0125] Figure 6 An example of a DCI design 600 supporting multi-CC scheduling in accordance with various aspects of the present disclosure is shown. In some examples, the DCI design 600 can implement or be implemented by aspects of the wireless communication system 100, the wireless communication system 200, or both. For example, the base station 105 can use the DCI design 600 to configure transmission parameters for multiple CCs of a carrier aggregation configuration for communication with the UE 115.

[0126] In some cases, the base station 105 may send a message including multiple fields for the first CC (e.g., Figure 6 ) and a second DCI 605-b including multiple corresponding fields (e.g., five (5) fields) for a second CC. However, sending multiple DCIs 605 may increase signaling overhead and reduce spectral efficiency.

[0127] Thus, the base station 105 may combine the first DCI 605-a for the first CC and the second DCI 605-b for the second CC into a single DCI 610 that appends the fields of the second DCI 605-b for the second CC to the end of the fields of the first DCI 605-a for the first CC. Additionally or alternatively, the base station 105 may combine the first DCI 605-a for the first CC and the second DCI 605-b for the second CC into a single DCI 615 such that the corresponding fields of each DCI 605 are sent together. For example, for DCI 615, the first field for the first CC in the first DCI 605-a may be sent next to the corresponding first field for the second CC in the second DCI 605-b, or the second field for the first CC in the first DCI 605-a may be sent next to the corresponding second field for the second CC in the second DCI 605-b. Notably, cyclic redundancy check (CRC) bits may be saved by using DCI 610 and / or DCI 615 (eg, a single DCI instead of multiple DCIs).

[0128] In addition, a joint indication field may be used to reduce the DCI size compared to a separate DCI for a CC. For example, the size of DCI 610 and DCI 615 may be smaller than the combined size of the first DCI 605-a and the second DCI 605-b (e.g., a separate DCI for a CC). However, the size of DCI 610 and DCI 615 may still be relatively large and use more resources to indicate the different configurations for each CC. Therefore, the base station 105 may use and send DCI 620, which is smaller in size using a joint field as described herein to indicate the configuration for each CC in a single DCI.

[0129] Figure 7 An example of a process flow 700 for supporting DCI design for multi-CC scheduling according to various aspects of the present disclosure is shown. In some examples, the process flow 700 can implement aspects of the wireless communication system 100, the wireless communication system 200, or both or can be implemented by aspects of the wireless communication system 100, the wireless communication system 200, or both. For example, the process flow 700 may include the UE 115-b and the base station 105-b, which may be respectively as described with reference to Figure 1-Figure 6 Examples of corresponding UE 115 and base station 105 are described.

[0130] In the following description of process flow 700, operations between UE 115-b and base station 105-b may be sent in an order different from that shown, or operations performed by base station 105-b and UE 115-b may be performed in a different order or at a different time. Certain operations may also be omitted from process flow 700, or other operations may be added to process flow 700. It should be understood that although base station 105-b and UE 115-b are shown performing multiple operations of process flow 700, any wireless device may perform the operations shown.

[0131] At 705, the UE 115-b and the base station 105-b may be connected via a first CC and a second CC according to a carrier aggregation configuration.

[0132] At 710, UE 115-b may receive a DCI from base station 105-b including a joint field that includes one or more of an RM indication for a first CC and a second CC or a zero power reference signal indication for the first CC and the second CC. For example, the RM indication may include an RM mode group indication, and the zero power reference signal indication may include a ZP-CSI-RS resource set indication.

[0133] At 715, UE 115-b may determine a common RMR from a common RMR configuration set for the first CC and the second CC based on the joint field for RM indication. For example, each bit of the joint field for RM indication may include an indication of an RMR group configured for the common RMR configuration.

[0134] Additionally or alternatively, UE 115-b may determine a first RMR for a first CC and a second RMR for a second CC based on a joint field for RM indication. For example, each bit of the joint field for RM indication may include an indication of an RMR group configured for each CC in the carrier aggregation configuration. In some cases, UE 115-b may determine that a CC of the carrier aggregation configuration is not configured with a corresponding RMR group, and UE 115-b may avoid performing an RM procedure for the CC based on the corresponding RM group not being configured for the CC.

[0135] In some cases, UE 115-b may receive an additional field (e.g., a separate field) for an additional RM indication for the second CC from base station 105-b.

[0136] At 720, UE 115-b may receive an indication of a common RMR configuration set from base station 105-b via RRC signaling. In some cases, UE 115-b may also receive a trigger field for a dynamic RM for a common RMR for the first CC and the second CC from base station 105-b via DCI.

[0137] Additionally or alternatively, UE 115-b may receive from base station 105-b an indication of a per-CC RMR configuration for each CC in a carrier aggregation configuration, wherein the first RMR and the second RMR are determined based on the per-CC RMR configuration. In some cases, UE 115-b may also receive from base station 105-b via DCI a trigger field for a dynamic RM for the first RMR, the second RMR, or both.

[0138] At 725, UE 115-b may determine ZP-CSI-RS indicators for the first CC and the second CC based on the DCI received at 710. For example, UE 115-b may receive zero-power reference signal indications for the first CC and the second CC from base station 105-b. In some cases, UE 115-b may receive a second additional field (e.g., a separate field) for an additional zero-power reference signal indication for the second CC from base station 105-b.

[0139] At 730, UE 115-b may receive a trigger field for a set identifier associated with a zero power reference signal indication from base station 105-b, and UE 115-b may determine a resource set (e.g., a ZP-CSI-RS resource set) for the zero power reference signal indication based on the set identifier, wherein the resource set is for the first CC and the second CC. In some cases, the trigger field may be received via DCI. Additionally, in some cases, UE 115-b may determine that a CC in a carrier aggregation configuration is not configured with a zero power reference signal resource set corresponding to the determined resource set, wherein the trigger field for the CC is ignored based on a determination that the zero power reference signal resource set is not configured for the CC.

[0140] At 735 , the UE 115 - b and the base station 105 - b may communicate according to the carrier aggregation configuration based on the DCI including the joint field.

[0141] Figure 8 A block diagram 800 of a device 805 supporting a DCI design for multi-CC scheduling according to aspects of the present disclosure is shown. The device 805 may be an example of aspects of a UE 115 as described herein. The device 805 may include a receiver 810, a UE communication manager 815, and a transmitter 820. The device 805 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0142] The receiver 810 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to DCI design for multi-CC scheduling). The information may be passed to other components of the device 805. The receiver 810 may be a reference Fig.11 Examples of various aspects of the transceiver 1120 are described. The receiver 810 may utilize a single antenna or a collection of antennas.

[0143] The UE communication manager 815 may be connected to the base station through the first CC and the second CC according to the carrier aggregation configuration. In some cases, the UE communication manager 815 may receive a DCI including a joint field from the base station, the joint field including one or more of the following: an RM indication for the first CC and the second CC or a zero power reference signal indication for the first CC and the second CC. In addition, the UE communication manager 815 may communicate with the base station according to the carrier aggregation configuration based on the DCI including the joint field. The UE communication manager 815 may be an example of various aspects of the UE communication manager 1110 described herein.

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

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

[0146] The transmitter 820 can transmit signals generated by other components of the device 805. In some examples, the transmitter 820 can be co-located with the receiver 810 in a transceiver module. For example, the transmitter 820 can be a reference Fig.11Examples of various aspects of the transceiver 1120 are described. The transmitter 820 may utilize a single antenna or a collection of antennas.

[0147] Fig. 9 A block diagram 900 of a device 905 supporting a DCI design for multi-CC scheduling according to aspects of the present disclosure is shown. The device 905 may be an example of aspects of the device 805 or UE 115 as described herein. The device 905 may include a receiver 910, a UE communication manager 915, and a transmitter 935. The device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0148] The receiver 910 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to DCI design for multi-CC scheduling). The information may be passed to other components of the device 905. The receiver 910 may be a reference Fig.11 Examples of various aspects of the transceiver 1120 are described. The receiver 910 may utilize a single antenna or a collection of antennas.

[0149] UE communication manager 915 may be an example of aspects of UE communication manager 815 as described herein. UE communication manager 915 may include carrier aggregation component 920, joint field component 925, and carrier aggregation communication component 930. UE communication manager 915 may be an example of aspects of UE communication manager 1110 described herein.

[0150] The carrier aggregation component 920 can be connected to the base station through the first CC and the second CC according to the carrier aggregation configuration.

[0151] The joint field component 925 may receive a DCI including a joint field from a base station, the joint field including one or more of: an RM indication for the first CC and the second CC or a zero power reference signal indication for the first CC and the second CC.

[0152] The carrier aggregation communicating component 930 can communicate with a base station according to a carrier aggregation configuration based on the DCI including the association field.

[0153] The transmitter 935 can transmit signals generated by other components of the device 905. In some examples, the transmitter 935 can be co-located with the receiver 910 in a transceiver module. For example, the transmitter 935 can be a reference Fig.11 Examples of various aspects of the transceiver 1120 are described. The transmitter 935 may utilize a single antenna or a collection of antennas.

[0154] Fig.10A block diagram 1000 of a UE communication manager 1005 supporting DCI design for multi-CC scheduling in accordance with aspects of the present disclosure is shown. The UE communication manager 1005 may be an example of aspects of the UE communication manager 815, the UE communication manager 915, or the UE communication manager 1110 described herein. The UE communication manager 1005 may include a carrier aggregation component 1010, a joint field component 1015, a carrier aggregation communication component 1020, a common RMR component 1025, a per-CC RMR component 1030, a separate field indication component 1035, and a joint ZP-CSI-RS component 1040. Each of these modules may communicate with each other directly or indirectly (e.g., via one or more buses).

[0155] The carrier aggregation component 1010 can be connected to the base station through the first CC and the second CC according to the carrier aggregation configuration.

[0156] The joint field component 1015 may receive a DCI including a joint field from a base station, the joint field including one or more of the following: an RM indication for a first CC and a second CC or a zero power reference signal indication for a first CC and a second CC. In some cases, the zero power reference signal indication may include a ZP-CSI-RS resource set indication, and the RM indication may include an RM mode group indication.

[0157] The carrier aggregation communicating component 1020 can communicate with a base station according to a carrier aggregation configuration based on the DCI including the association field.

[0158] The public RMR component 1025 may determine the public RMR from the public RMR configuration set for the first CC and the second CC based on the joint field for RM indication. In some examples, the public RMR component 1025 may receive an indication of the public RMR configuration set from the base station via RRC signaling. In addition, the public RMR component 1025 may receive a trigger field of a dynamic RM for the public RMR of the first CC and the second CC from the base station via DCI. In some cases, each bit of the joint field for RM indication may include an indication of an RMR group configured for the public RMR configuration.

[0159] The per-CC RMR component 1030 may determine a first RMR for a first CC and a second RMR for a second CC based on a joint field for RM indication. In some examples, the per-CC RMR component 1030 may receive an indication of a per-CC RMR configuration for each CC in a carrier aggregation configuration from a base station, wherein the first RMR and the second RMR are determined based on the per-CC RMR configuration. In addition, the per-CC RMR component 1030 may receive a trigger field for a dynamic RM for the first RMR, the second RMR, or both from a base station via a DCI. In some examples, the per-CC RMR component 1030 may determine that a CC in a carrier aggregation configuration is not configured with a corresponding RMR group, and may avoid performing an RM process for a CC based on a determination that the corresponding RMR group is not configured for the CC. In some cases, each bit of the joint field for RM indication may include an indication of an RMR group configured for each CC in the carrier aggregation configuration.

[0160] The separate field indication component 1035 may receive from the base station an additional field for an additional RM indication for the second CC, wherein the communication with the base station is based on the additional RM indication. Additionally or alternatively, the separate field indication component 1035 may receive from the base station a second additional field for an additional zero power reference signal indication for the second CC.

[0161] The joint ZP-CSI-RS component 1040 can determine a zero power reference signal configuration for a first CC and a second CC from a base station based on a joint field for a zero power reference signal indication. In some examples, the joint ZP-CSI-RS component 1040 can receive a trigger field for a set identifier associated with the zero power reference signal indication from the base station, and can determine a resource set for the zero power reference signal indication based on the set identifier, wherein the resource set is used for the first CC and the second CC. In some cases, the trigger field can be received via DCI. In some examples, the joint ZP-CSI-RS component 1040 can determine that a CC in a carrier aggregation configuration is not configured with a zero power reference signal resource set corresponding to the determined resource set, wherein the trigger field is ignored for the CC based on a determination that the zero power reference signal resource set is not configured for the CC.

[0162] Fig.11A diagram of a system 1100 including a device 1105 supporting a DCI design for multi-CC scheduling according to various aspects of the present disclosure is shown. The device 1105 may be an example of a device 805, a device 905, or a UE 115 as described herein or include a component of the device 805, a device 905, or a UE 115. The device 1105 may include components for two-way voice and data communications, including components for sending and receiving communications, including a UE communication manager 1110, an I / O controller 1115, a transceiver 1120, an antenna 1125, a memory 1130, and a processor 1140. These components may communicate electronically via one or more buses (e.g., a bus 1145).

[0163] The UE communication manager 110 may be connected to the base station through the first CC and the second CC according to the carrier aggregation configuration. In some cases, the UE communication manager 1110 may receive a DCI including a joint field from the base station, the joint field including one or more of the following: an RM indication for the first CC and the second CC or a zero power reference signal indication for the first CC and the second CC. In addition, the UE communication manager 1110 may communicate with the base station according to the carrier aggregation configuration based on the DCI including the joint field.

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

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

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

[0167] The memory 1130 may include random access memory (RAM) and read-only memory (ROM). The memory 1130 may store computer-readable, computer-executable code 1135, which includes instructions that, when executed, cause the processor to perform various functions described herein. In some cases, the memory 1130 may also contain, among other things, a basic I / O system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0168] The processor 1140 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a central processing unit (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, the processor 1140 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into the processor 1140. The processor 1140 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1130) to cause the device 1105 to perform various functions (e.g., functions or tasks supporting a DCI design for multi-CC scheduling).

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

[0170] Fig.12 A block diagram 1200 of a device 1205 supporting a DCI design for multi-CC scheduling according to aspects of the present disclosure is shown. The device 1205 may be an example of aspects of a base station 105 as described herein. The device 1205 may include a receiver 1210, a base station communication manager 1215, and a transmitter 1220. The device 1205 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0171] The receiver 1210 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to DCI design for multi-CC scheduling). The information may be communicated to other components of the device 1205. The receiver 1210 may be a reference Fig.15 Examples of various aspects of the transceiver 1520 are described. The receiver 1210 may utilize a single antenna or a collection of antennas.

[0172] The base station communication manager 1215 may be connected to the UE through the first CC and the second CC according to the carrier aggregation configuration. In some cases, the base station communication manager 1215 may send a DCI including a joint field to the UE, and the joint field includes one or more of the following: an RM indication for the first CC and the second CC or a zero-power reference signal indication for the first CC and the second CC. In addition, the base station communication manager 1215 may communicate with the UE according to the carrier aggregation configuration based on the DCI including the joint field. The base station communication manager 1215 may be an example of various aspects of the base station communication manager 1510 described herein.

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

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

[0175] The transmitter 1220 may transmit signals generated by other components of the device 1205. In some examples, the transmitter 1220 may be co-located with the receiver 1210 in a transceiver module. For example, the transmitter 1220 may be a reference Fig.15 Examples of various aspects of the transceiver 1520 are described. The transmitter 1220 may utilize a single antenna or a collection of antennas.

[0176] Fig.13 A block diagram 1300 of a device 1305 supporting a DCI design for multi-CC scheduling according to aspects of the present disclosure is shown. The device 1305 may be an example of aspects of the device 1205 or base station 105 as described herein. The device 1305 may include a receiver 1310, a base station communication manager 1315, and a transmitter 1335. The device 1305 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0177] The receiver 1310 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to DCI design for multi-CC scheduling). The information may be communicated to other components of the device 1305. The receiver 1310 may be a reference Fig.15 Examples of various aspects of the transceiver 1520 are described. The receiver 1310 may utilize a single antenna or a collection of antennas.

[0178] Base station communication manager 1315 may be an example of aspects of base station communication manager 1215 as described herein. Base station communication manager 1315 may include carrier aggregation component 1320, joint field indicator 1325, and carrier aggregation communication component 1330. Base station communication manager 1315 may be an example of aspects of base station communication manager 1510 as described herein.

[0179] The carrier aggregation component 1320 can be connected to the UE through the first CC and the second CC according to the carrier aggregation configuration.

[0180] The joint field indicator 1325 may send a DCI including a joint field to the UE, the joint field including one or more of: an RM indication for the first CC and the second CC or a zero power reference signal indication for the first CC and the second CC.

[0181] The carrier aggregation communicating component 1330 can communicate with the UE according to the carrier aggregation configuration based on the DCI including the association field.

[0182] Transmitter 1335 can transmit signals generated by other components of device 1305. In some examples, transmitter 1335 can be co-located with receiver 1310 in a transceiver module. For example, transmitter 1335 can be a reference Fig.15 Examples of various aspects of the transceiver 1520 are described. The transmitter 1335 can utilize a single antenna or a collection of antennas.

[0183] Fig.14A block diagram 1400 of a base station communication manager 1405 supporting DCI design for multi-CC scheduling in accordance with aspects of the present disclosure is shown. The base station communication manager 1405 may be an example of aspects of the base station communication manager 1215, the base station communication manager 1315, or the base station communication manager 1510 described herein. The base station communication manager 1405 may include a carrier aggregation component 1410, a joint field indicator 1415, a carrier aggregation communication component 1420, a common RMR indicator 1425, a per-CC RMR indicator 1430, an additional field indicator 1435, and a joint ZP-CSI-RS indicator 1440. Each of these modules may communicate with each other directly or indirectly (e.g., via one or more buses).

[0184] The carrier aggregation component 1410 can be connected to the UE through the first CC and the second CC according to the carrier aggregation configuration.

[0185] The joint field indicator 1415 may send a DCI including a joint field to the UE, the joint field including one or more of the following: an RM indication for the first CC and the second CC or a zero power reference signal indication for the first CC and the second CC. In some cases, the zero power reference signal indication may include a ZP-CSI-RS resource set indication, and the RM indication may include an RM mode group indication.

[0186] The carrier aggregation communicating component 1420 can communicate with the UE according to the carrier aggregation configuration based on the DCI including the association field.

[0187] The common RMR indicator 1425 may send an indication of a common RMR from a common RMR configuration set for the first CC and the second CC in a joint field for RM indication. In some examples, the common RMR indicator 1425 may send an indication of the common RMR configuration set to the UE via RRC signaling. In addition, the common RMR indicator 1425 may send a trigger field of a dynamic RM for the common RMR of the first CC and the second CC to the UE via DCI. In some cases, each bit of the joint field for RM indication may include an indication of an RMR group configured for the common RMR configuration.

[0188] The per-CC RMR indicator 1430 may send a first RMR for a first CC and a second RMR for a second CC in a joint field for RM indication. In some examples, the per-CC RMR indicator 1430 may send an indication of a per-CC RMR configuration for each CC in a carrier aggregation configuration to the UE, wherein the first RMR and the second RMR are determined based on the per-CC RMR configuration. In addition, the per-CC RMR indicator 1430 may send a trigger field for a dynamic RM for the first RMR, the second RMR, or both to the UE via a DCI. In some cases, each bit of the joint field for RM indication may include an indication of an RMR group configured for each CC in the carrier aggregation configuration.

[0189] The additional field indicator 1435 may send an additional field for an additional RM indication for the second CC to the UE, wherein the communication with the UE is based on the additional RM indication. Additionally or alternatively, the additional field indicator 1435 may send a second additional field for an additional zero-power reference signal indication for the second CC to the UE.

[0190] The joint ZP-CSI-RS indicator 1440 may send a zero power reference signal configuration for the first CC and the second CC to the UE based on the zero power reference signal indication in the joint field of the DCI. In some examples, the joint ZP-CSI-RS indicator 1440 may determine a resource set for the zero power reference signal indication, where the resource set is for the first CC and the second CC; and a trigger field for a set identifier associated with the zero power reference signal indication may be sent to the UE, the set identifier corresponding to the determined resource set. In some cases, the trigger field may be sent via the DCI.

[0191] Fig.15 A diagram of a system 1500 including a device 1505 supporting a DCI design for multi-CC scheduling according to aspects of the present disclosure is shown. The device 1505 may be an example of or include components of a device 1205, a device 1305, or a base station 105 as described herein. The device 1505 may include components for two-way voice and data communications, including components for sending and receiving communications, including a base station communication manager 1510, a network communication manager 1515, a transceiver 1520, an antenna 1525, a memory 1530, a processor 1540, and an inter-station communication manager 1545. These components may be in electronic communication via one or more buses (e.g., a bus 1550).

[0192] The base station communication manager 1510 may be connected to the UE through the first CC and the second CC according to the carrier aggregation configuration. In some cases, the base station communication manager 1510 may send a DCI including a joint field to the UE, the joint field including one or more of the following: an RM indication for the first CC and the second CC or a zero-power reference signal indication for the first CC and the second CC. In addition, the base station communication manager 1510 may communicate with the UE according to the carrier aggregation configuration based on the DCI including the joint field.

[0193] The network communications manager 1515 may manage communications with the core network (eg, via one or more wired backhaul links). For example, the network communications manager 1515 may manage the transmission of data communications for client devices (eg, one or more UEs 115).

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

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

[0196] Memory 1530 may include RAM, ROM, or a combination thereof. Memory 1530 may store computer readable code 1535, which includes instructions that, when executed by a processor (e.g., processor 1540), cause the device to perform various functions described herein. In some cases, memory 1530 may also contain, among other things, BIOS, which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0197] Processor 1540 may include an intelligent 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 1540 may be configured to operate a memory array using a memory controller. In some cases, the memory controller may be integrated into processor 1540. Processor 1540 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1530) to cause device 1505 to perform various functions (e.g., functions or tasks supporting DCI design for multi-CC scheduling).

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

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

[0200] Fig.16 A flow chart illustrating a method 1600 for supporting DCI design for multi-CC scheduling according to aspects of the present disclosure is shown. The operations of the method 1600 may be implemented by a UE 115 or a component thereof as described herein. For example, the operations of the method 1600 may be implemented by a UE 115 or a component thereof as described herein. Figures 8 to 11 In some examples, the UE may execute an instruction set to control the functional units 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.

[0201] At 1605, the UE may connect to the base station via the first CC and the second CC according to the carrier aggregation configuration. The operations of 1605 may be performed according to the methods described herein. In some examples, aspects of the operations of 1605 may be as described with reference to Figures 8 to 11 The described carrier aggregation components are performed.

[0202] At 1610, the UE may receive a DCI including a joint field from a base station, the joint field including one or more of the following: an RM indication for a first CC and a second CC or a zero-power reference signal indication for the first CC and the second CC. The operations of 1610 may be performed according to the methods described herein. In some examples, aspects of the operations of 1610 may be performed as described with reference to Figures 8 to 11 The union field component described is performed.

[0203] At 1615, the UE may communicate with the base station according to the carrier aggregation configuration based at least in part on the DCI including the joint field. The operations of 1615 may be performed according to the methods described herein. In some examples, aspects of the operations of 1615 may be as described with reference to Figures 8 to 11 The described carrier aggregation communication components are performed.

[0204] Fig.17 A flow chart illustrating a method 1700 for supporting DCI design for multi-CC scheduling according to aspects of the present disclosure is shown. The operations of the method 1700 may be implemented by a UE 115 or a component thereof as described herein. For example, the operations of the method 1700 may be implemented by a UE 115 or a component thereof as described herein. Figures 8 to 11 In some examples, the UE may execute an instruction set to control the functional units 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.

[0205] At 1705, the UE may connect to the base station through the first CC and the second CC according to the carrier aggregation configuration. The operations of 1705 may be performed according to the methods described herein. In some examples, aspects of the operations of 1705 may be as described with reference to Figures 8 to 11 The described carrier aggregation components are performed.

[0206] At 1710, the UE may receive a DCI including a joint field from a base station, the joint field including one or more of the following: an RM indication for a first CC and a second CC or a zero-power reference signal indication for the first CC and the second CC. The operations of 1710 may be performed according to the methods described herein. In some examples, aspects of the operations of 1710 may be performed as described with reference to Figures 8 to 11 The union field component described is performed.

[0207] At 1715, the UE may determine a common RMR from a common RMR configuration set for the first CC and the second CC based at least in part on the joint field for the RM indication. The operations of 1715 may be performed according to the methods described herein. In some examples, aspects of the operations of 1715 may be as described with reference to Figures 8 to 11 Describes the common RMR components to perform.

[0208] At 1720, the UE may communicate with the base station according to the carrier aggregation configuration based at least in part on the DCI including the joint field. The operations of 1720 may be performed according to the methods described herein. In some examples, aspects of the operations of 1720 may be as described with reference to Figures 8 to 11 The described carrier aggregation communication components are performed.

[0209] Fig.18 A flow chart illustrating a method 1800 for supporting DCI design for multi-CC scheduling according to aspects of the present disclosure is shown. The operations of the method 1800 may be implemented by a UE 115 or a component thereof as described herein. For example, the operations of the method 1800 may be implemented by a UE 115 or a component thereof as described herein. Figures 8 to 11 In some examples, the UE may execute an instruction set to control the functional units 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.

[0210] At 1805, the UE may connect to the base station through the first CC and the second CC 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 with reference to Figures 8 to 11 The described carrier aggregation components are performed.

[0211] At 1810, the UE may receive a DCI including a joint field from a base station, the joint field including one or more of the following: an RM indication for a first CC and a second CC or a zero-power reference signal indication for the first CC and the second CC. 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 with reference to Figures 8 to 11 The union field component described is performed.

[0212] At 1815, the UE may determine a first RMR for the first CC and a second RMR for the second CC based at least in part on the joint field for the RM indication. 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 with reference to Figures 8 to 11 Describes the RMR components to be executed per CC.

[0213] At 1820, the UE may communicate with the base station according to the carrier aggregation configuration based at least in part on the DCI including the joint field. The operations of 1820 may be performed according to the methods described herein. In some examples, aspects of the operations of 1820 may be as described with reference to Figures 8 to 11 The described carrier aggregation communication components are performed.

[0214] Fig.19 A flow chart illustrating a method 1900 for supporting DCI design for multi-CC scheduling according to aspects of the present disclosure is shown. The operations of the method 1900 may be implemented by a UE 115 or a component thereof as described herein. For example, the operations of the method 1900 may be implemented by a UE 115 or a component thereof as described herein. Figures 8 to 11In some examples, the UE may execute an instruction set to control the functional units 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.

[0215] At 1905, the UE may connect to the base station through the first CC and the second CC according to the carrier aggregation configuration. The operations of 1905 may be performed according to the methods described herein. In some examples, aspects of the operations of 1905 may be as described with reference to Figures 8 to 11 The described carrier aggregation components are performed.

[0216] At 1910, the UE may receive a DCI including a joint field from a base station, the joint field including one or more of the following: an RM indication for a first CC and a second CC or a zero-power reference signal indication for the first CC and the second CC. 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 with reference to Figures 8 to 11 The union field component described is performed.

[0217] At 1915, the UE may determine from the base station a zero power reference signal configuration for the first CC and the second CC based at least in part on the joint field for the zero power reference signal indication. 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 with reference to Figures 8 to 11 The described joint ZP-CSI-RS component is performed.

[0218] At 1920, the UE may communicate with the base station according to the carrier aggregation configuration based at least in part on the DCI including the joint field. The operations of 1920 may be performed according to the methods described herein. In some examples, aspects of the operations of 1920 may be as described with reference to Figures 8 to 11 The described carrier aggregation communication components are performed.

[0219] Fig. 20 A flow chart illustrating a method 2000 for supporting DCI design for multi-CC scheduling 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 a base station 105 or components thereof as described herein. Figures 12 to 15 The base station may be executed by the base station communication manager described in the following. In some examples, the base station may execute an instruction set to control the functional units 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.

[0220] At 2005, the base station may connect to the UE via the first CC and the second CC 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 as described with reference to Figures 12 to 15 The described carrier aggregation components are performed.

[0221] At 2010, the base station may send a DCI including a joint field to the UE, the joint field including one or more of the following: an RM indication for the first CC and the second CC or a zero-power reference signal indication for the first CC and the second CC. 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 with reference to Figures 12 to 15 Description of the union field pointer to perform.

[0222] At 2015, the base station may communicate with the UE according to the carrier aggregation configuration based at least in part on the DCI including the joint field. 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 with reference to Figures 12 to 15 The described carrier aggregation communication components are performed.

[0223] The following provides a summary of various aspects of the present disclosure:

[0224] Aspect 1: A method for wireless communication at a UE, comprising: connecting to a base station via a first component carrier and a second component carrier according to a carrier aggregation configuration; receiving downlink control information including a joint field from the base station, the joint field including one or more of the following: a rate matching indication for the first component carrier and the second component carrier or a zero power reference signal indication for the first component carrier and the second component carrier; and communicating with the base station according to the carrier aggregation configuration based at least in part on the downlink control information including the joint field.

[0225] Aspect 2: The method according to aspect 1 also includes: determining common rate matching resources from multiple common rate matching resource configurations for the first component carrier and the second component carrier based at least in part on the joint field for the rate matching indication.

[0226] Aspect 3: The method according to aspect 2 further comprises: receiving an indication of the plurality of common rate matching resource configurations from the base station via radio resource control signaling.

[0227] Aspect 4: The method according to any one of aspects 2 to 3 further includes: receiving a trigger field for dynamic rate matching of the common rate matching resource for the first component carrier and the second component carrier from the base station via downlink control information.

[0228] Aspect 5: The method according to any one of aspects 2 to 4, wherein each bit of the joint field for the rate matching indication includes an indication of a rate matching resource group configured for the common rate matching resource configuration.

[0229] Aspect 6: The method according to any one of Aspects 1 to 5 further includes: determining a first rate matching resource for the first component carrier and a second rate matching resource for the second component carrier based at least in part on the joint field for the rate matching indication.

[0230] Aspect 7: The method according to Aspect 6 further includes: receiving an indication of a per-component carrier rate matching resource configuration for each component carrier in the carrier aggregation configuration from the base station, wherein the first rate matching resource and the second rate matching resource are determined at least in part based on the per-component carrier rate matching resource configuration.

[0231] Aspect 8: The method according to any one of Aspects 6 to 7 further includes: receiving a trigger field for dynamic rate matching of the first rate matching resource, the second rate matching resource, or both from the base station via downlink control information.

[0232] Aspect 9: The method according to any one of aspects 6 to 8, wherein each bit of the joint field for the rate matching indication comprises an indication of a rate matching resource group configured for each component carrier of the carrier aggregation configuration.

[0233] Aspect 10: The method according to Aspect 9 further includes: determining that the component carrier of the carrier aggregation configuration is not configured with a corresponding rate matching resource group; and avoiding performing a rate matching process for the component carrier based at least in part on the determination that the corresponding rate matching resource group is not configured for the component carrier.

[0234] Aspect 11: The method according to any one of Aspects 1 to 10 further includes: receiving an additional field for an additional rate matching indication for the second component carrier from the base station, wherein the communication with the base station is at least partially based on the additional rate matching indication.

[0235] Aspect 12: The method according to any one of Aspects 1 to 11 also includes: determining a zero power reference signal configuration for the first component carrier and the second component carrier from the base station at least in part based on the joint field used for the zero power reference signal indication.

[0236] Aspect 13: The method according to aspect 12 further comprises: receiving, from the base station, a second additional field indicating an additional zero-power reference signal for the second component carrier.

[0237] Aspect 14: The method according to any one of Aspects 12 to 13 further includes: receiving a trigger field for a set identifier associated with the zero power reference signal indication from the base station; and determining a resource set for the zero power reference signal indication based at least in part on the set identifier, wherein the resource set is used for the first component carrier and the second component carrier.

[0238] Aspect 15: The method according to Aspect 14 further includes: determining that the component carrier of the carrier aggregation configuration is not configured with a zero-power reference signal resource set corresponding to the determined resource set, wherein the trigger field is ignored for the component carrier at least in part based on the determination that the zero-power reference signal resource set is not configured for the component carrier.

[0239] Aspect 16: The method according to any one of aspects 14 to 15, wherein the trigger field is received via downlink control information.

[0240] Aspect 17: The method according to any one of Aspects 1 to 16, wherein the zero-power reference signal indication comprises a zero-power channel state information reference signal resource set indication.

[0241] Aspect 18: The method according to any one of Aspects 1 to 17, wherein the rate matching indication comprises a rate matching mode group indication.

[0242] Aspect 19: A method for wireless communication at a base station, comprising: connecting to a UE via a first component carrier and a second component carrier according to a carrier aggregation configuration; sending downlink control information including a joint field to the UE, the joint field including one or more of the following: a rate matching indication for the first component carrier and the second component carrier or a zero power reference signal indication for the first component carrier and the second component carrier; and communicating with the UE according to the carrier aggregation configuration based at least in part on the downlink control information including the joint field.

[0243] Aspect 20: The method according to aspect 19 further comprises: sending an indication of a common rate matching resource from a plurality of common rate matching resource configurations for the first component carrier and the second component carrier in the joint field for the rate matching indication.

[0244] Aspect 21: The method according to aspect 20 further includes: sending an indication of the plurality of common rate matching resource configurations to the UE via radio resource control signaling.

[0245] Aspect 22: The method according to any one of Aspects 20 to 21 further includes: sending a trigger field for dynamic rate matching of the common rate matching resources of the first component carrier and the second component carrier to the UE via downlink control information.

[0246] Aspect 23: The method according to any one of aspects 20 to 22, wherein each bit of the joint field for the rate matching indication comprises an indication of a rate matching resource group configured for the common rate matching resource configuration.

[0247] Aspect 24: The method according to any one of Aspects 19 to 23 further includes: sending a first rate matching resource for the first component carrier and a second rate matching resource for the second component carrier in the joint field for the rate matching indication.

[0248] Aspect 25: The method according to Aspect 24 further includes: sending an indication of a per-component carrier rate matching resource configuration for each component carrier in the carrier aggregation configuration to the UE, wherein the first rate matching resource and the second rate matching resource are determined at least in part based on the per-component carrier rate matching resource configuration.

[0249] Aspect 26: The method according to any one of Aspects 24 to 25 further includes: sending a trigger field for dynamic rate matching of the first rate matching resource, the second rate matching resource, or both to the UE via downlink control information.

[0250] Aspect 27: The method according to any one of aspects 24 to 26, wherein each bit of the joint field for the rate matching indication comprises an indication of a rate matching resource group configured for each component carrier in the carrier aggregation configuration.

[0251] Aspect 28: The method according to any one of Aspects 19 to 27 further includes: sending an additional field for an additional rate matching indication for the second component carrier to the UE, wherein the communication with the UE is at least partially based on the additional rate matching indication.

[0252] Aspect 29: The method according to any one of Aspects 19 to 28 also includes: sending a zero power reference signal configuration for the first component carrier and the second component carrier to the UE at least in part based on the zero power reference signal indication in the joint field of the downlink control information.

[0253] Aspect 30: The method according to aspect 29 further includes: sending a second additional field for an additional zero-power reference signal indication for the second component carrier to the UE.

[0254] Aspect 31: The method according to any one of Aspects 29 to 30 further includes: determining a resource set for the zero power reference signal indication, wherein the resource set is used for the first component carrier and the second component carrier; and sending a trigger field for a set identifier associated with the zero power reference signal indication to the UE, and the set identifier corresponds to the determined resource set.

[0255] Aspect 32: The method according to Aspect 31, wherein the trigger field is sent via downlink control information.

[0256] Aspect 33: The method according to any one of Aspects 19 to 32, wherein the zero-power reference signal indication comprises a zero-power channel state information reference signal resource set indication.

[0257] Aspect 34: The method according to any one of Aspects 19 to 33, wherein the rate matching indication comprises a rate matching mode group indication.

[0258] Aspect 35: An apparatus for wireless communication at a UE, 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 enable the apparatus to perform a method according to any one of Aspects 1 to 18.

[0259] Aspect 36: An apparatus for wireless communication at a UE, comprising at least one unit for performing the method according to any one of aspects 1 to 18.

[0260] Aspect 37: A non-transitory computer-readable medium storing code for wireless communication at a UE, the code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 18.

[0261] Aspect 38: An apparatus for wireless communication at a base station, comprising: at least one processor; a memory coupled to the at least one processor; and instructions, which are stored in the memory and can be executed by the at least one processor to enable the apparatus to perform a method according to any one of Aspects 19 to 34.

[0262] Aspect 39: An apparatus for wireless communication at a base station, comprising at least one unit for performing the method according to any one of aspects 19 to 34.

[0263] Aspect 40: A non-transitory computer-readable medium storing code for wireless communication at a base station, the code comprising instructions executable by a processor to perform the method according to any one of aspects 19 to 34.

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

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

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

[0267] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or executed using a general purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in 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 combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a DSP core, or any other such configuration).

[0268] 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 files, threads of execution, processes, functions. If implemented with software executed by a processor, the functions can be stored on a computer-readable medium or sent therethrough 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 (e.g., executed by a processor), hardware, hard wiring, or a combination of any of these items. The features that implement the functions can also be physically located at various locations, including being distributed so that the various parts of the functions in the functions are implemented at different physical locations.

[0269] Computer readable medium includes both non-transitory computer storage medium and communication medium, and communication medium includes any medium that promotes the transmission of computer program from one place to another place.Non-transitory storage medium can be any available medium that can be accessed by general-purpose computer or special-purpose computer.By way of example and not limitation, non-transitory computer readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, phase change 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 unit and can be accessed by general-purpose or special-purpose computer or general-purpose or special-purpose processor in the form of instruction or data structure Any other non-transitory medium.In addition, any connection is appropriately referred to as computer readable medium.For example, if software is to send from website, server or other remote source using coaxial cable, optical fiber cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, optical fiber cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of computer readable medium. As used herein, disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, wherein disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0270] As used herein (including in the claims), "or" as used in a list of items (e.g., a list of items ending 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, an exemplary step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "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 by itself, or any combination of two or more of the listed items can be adopted. For example, if an ingredient is described as comprising components A, B, and / or C, the ingredient can comprise: A only; B only; C only; A and B combined; A and C combined; B and C combined; or A, B, and C combined.

[0271] In the accompanying drawings, similar components or features may have the same reference numeral. In addition, various components of the same type may be distinguished by following the reference numeral with a dash and a second reference numeral, the second reference numeral being used to distinguish between similar components. If only the first reference numeral is used in the specification, the description applies to any of the similar components having the same first reference numeral, without regard to the second reference numeral or other subsequent reference numerals.

[0272] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations, and do 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 "advantageous over other examples." For the purpose of providing an understanding of the described techniques, the detailed description includes specific details. However, these techniques may be implemented 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.

[0273] To enable those skilled in the art to implement or use the present disclosure, the description herein is provided. It will be apparent to those skilled in the art that various modifications to the present disclosure will be apparent, 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 is given the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication at a user equipment (UE), comprising: connecting to a network entity via a first component carrier and a second component carrier according to a carrier aggregation configuration; receiving, from the network entity, a single downlink control message comprising a joint field, the joint field comprising one or more of: a rate matching indication for the first component carrier and the second component carrier or a zero power reference signal indication for the first component carrier and the second component carrier; and Communicating with the network entity in accordance with the carrier aggregation configuration based at least in part on the single downlink control information including the joint field.

2. The method according to claim 1, further comprising: Common rate matching resources are determined from a plurality of common rate matching resource configurations for the first component carrier and the second component carrier based at least in part on the joint field for the rate matching indication.

3. The method according to claim 2, further comprising: An indication of the plurality of common rate matching resource configurations is received from the network entity via radio resource control signaling.

4. The method according to claim 2, further comprising: A trigger field for dynamic rate matching for the common rate matching resources for the first component carrier and the second component carrier is received from the network entity via downlink control information.

5. The method according to claim 2, wherein: Each bit of the joint field for the rate matching indication comprises an indication of a rate matching resource group configured for the common rate matching resource configuration.

6. The method according to claim 1, further comprising: A first rate matching resource for the first component carrier and a second rate matching resource for the second component carrier are determined based at least in part on the joint field for the rate matching indication.

7. The method according to claim 6, further comprising: An indication of a per component carrier rate matching resource configuration for each component carrier in the carrier aggregation configuration is received from the network entity, wherein the first rate matching resource and the second rate matching resource are determined based at least in part on the per component carrier rate matching resource configuration.

8. The method according to claim 6, further comprising: A trigger field for dynamic rate matching of the first rate matching resource, the second rate matching resource, or both is received from the network entity via downlink control information.

9. The method according to claim 6, wherein: Each bit of the joint field for the rate matching indication comprises an indication of a rate matching resource group configured for each component carrier in the carrier aggregation configuration, the method further comprising: determining that a component carrier in the carrier aggregation configuration is not configured with a corresponding rate matching resource group; and Performing a rate matching procedure for the component carrier is avoided based at least in part on the determination that the corresponding rate matching resource group is not configured for the component carrier.

10. The method according to claim 1, further comprising: An additional field of an additional rate matching indication for the second component carrier is received from the network entity, wherein communication with the network entity is based at least in part on the additional rate matching indication.

11. The method according to claim 1, further comprising: A zero power reference signal configuration for the first component carrier and the second component carrier is determined from the network entity based at least in part on the joint field for the zero power reference signal indication.

12. The method according to claim 11, further comprising: A second additional field of an additional zero-power reference signal indication for the second component carrier is received from the network entity.

13. The method according to claim 11, further comprising: receiving, from the network entity and via downlink control information, a trigger field for a set identifier associated with the zero power reference signal indication; determining a set of resources for the zero-power reference signal indication based at least in part on the set identifier, wherein the set of resources is for the first component carrier and the second component carrier; and Determine that a component carrier in the carrier aggregation configuration is not configured with a zero-power reference signal resource set corresponding to the determined resource set, wherein the trigger field is ignored for the component carrier based at least in part on the determination that the zero-power reference signal resource set is not configured for the component carrier.

14. An apparatus for wireless communication at a user equipment (UE), comprising: at least one processor; a memory coupled to the at least one processor; as well as Instructions, which are stored in the memory and can be executed by the at least one processor to cause the device to perform the following operations: connecting to a network entity via a first component carrier and a second component carrier according to a carrier aggregation configuration; receiving, from the network entity, a single downlink control message comprising a joint field, the joint field comprising one or more of: a rate matching indication for the first component carrier and the second component carrier or a zero power reference signal indication for the first component carrier and the second component carrier; and Communicating with the network entity in accordance with the carrier aggregation configuration based at least in part on the single downlink control information including the joint field.

15. The device according to claim 14, wherein: The instructions may also be executed by the at least one processor to cause the device to perform the following operations: Common rate matching resources are determined from a plurality of common rate matching resource configurations for the first component carrier and the second component carrier based at least in part on the joint field for the rate matching indication.

16. The device according to claim 15, wherein: The instructions may also be executed by the at least one processor to cause the device to perform the following operations: An indication of the plurality of common rate matching resource configurations is received from the network entity via radio resource control signaling.

17. The device according to claim 15, wherein: The instructions may also be executed by the at least one processor to cause the device to perform the following operations: A trigger field for dynamic rate matching for the common rate matching resources for the first component carrier and the second component carrier is received from the network entity via downlink control information.

18. The device according to claim 15, wherein: Each bit of the joint field for the rate matching indication comprises an indication of a rate matching resource group configured for the common rate matching resource configuration.

19. The device according to claim 14, wherein: The instructions may also be executed by the at least one processor to cause the device to perform the following operations: A first rate matching resource for the first component carrier and a second rate matching resource for the second component carrier are determined based at least in part on the joint field for the rate matching indication.

20. The device according to claim 19, wherein The instructions may also be executed by the at least one processor to cause the device to perform the following operations: An indication of a per component carrier rate matching resource configuration for each component carrier in the carrier aggregation configuration is received from the network entity, wherein the first rate matching resource and the second rate matching resource are determined based at least in part on the per component carrier rate matching resource configuration.

21. The device according to claim 19, wherein The instructions may also be executed by the at least one processor to cause the device to perform the following operations: A trigger field for dynamic rate matching of the first rate matching resource, the second rate matching resource, or both is received from the network entity via downlink control information.

22. The device according to claim 19, wherein Each bit of the joint field for the rate matching indication comprises an indication of a rate matching resource group configured for each component carrier in the carrier aggregation configuration.

23. The device according to claim 22, wherein: The instructions may also be executed by the at least one processor to cause the device to perform the following operations: Determining that a component carrier in the carrier aggregation configuration is not configured with a corresponding rate matching resource group; as well as Performing a rate matching procedure for the component carrier is avoided based at least in part on the determination that the corresponding rate matching resource group is not configured for the component carrier.

24. The device according to claim 14, wherein: The instructions may also be executed by the at least one processor to cause the device to perform the following operations: An additional field of an additional rate matching indication for the second component carrier is received from the network entity, wherein communication with the network entity is based at least in part on the additional rate matching indication.

25. The device according to claim 14, wherein: The instructions may also be executed by the at least one processor to cause the device to perform the following operations: A zero power reference signal configuration for the first component carrier and the second component carrier is determined from the network entity based at least in part on the joint field for the zero power reference signal indication.

26. The device according to claim 25, wherein The instructions may also be executed by the at least one processor to cause the device to perform the following operations: A second additional field of an additional zero-power reference signal indication for the second component carrier is received from the network entity.

27. The device according to claim 25, wherein: The instructions may also be executed by the at least one processor to cause the device to perform the following operations: receiving, from the network entity and via downlink control information, a trigger field for a set identifier associated with the zero-power reference signal indication; and A set of resources for the zero-power reference signal indication is determined based at least in part on the set identifier, wherein the set of resources is used for the first component carrier and the second component carrier.

28. The device according to claim 27, wherein The instructions may also be executed by the at least one processor to cause the device to perform the following operations: Determine that a component carrier in the carrier aggregation configuration is not configured with a zero-power reference signal resource set corresponding to the determined resource set, wherein the trigger field is ignored for the component carrier based at least in part on the determination that the zero-power reference signal resource set is not configured for the component carrier.

29. A method for wireless communication at a network entity, comprising: connecting to a user equipment (UE) via a first component carrier and a second component carrier according to a carrier aggregation configuration; sending a single downlink control message including a joint field to the UE, the joint field including one or more of: a rate matching indication for the first component carrier and the second component carrier or a zero power reference signal indication for the first component carrier and the second component carrier; and Communicating with the UE in accordance with the carrier aggregation configuration based at least in part on the single downlink control information including the joint field.

30. An apparatus for wireless communication at a network entity, comprising: at least one processor; a memory coupled to the at least one processor; as well as Instructions, which are stored in the memory and can be executed by the at least one processor to cause the device to perform the following operations: connecting to a user equipment (UE) via a first component carrier and a second component carrier according to a carrier aggregation configuration; sending a single downlink control message including a joint field to the UE, the joint field including one or more of: a rate matching indication for the first component carrier and the second component carrier, or a zero power reference signal indication for the first component carrier and the second component carrier; and Communicating with the UE in accordance with the carrier aggregation configuration based at least in part on the single downlink control information including the joint field.

Images