Providing zero power channel state information reference signal and rate matching configuration in carrier aggregation
By introducing joint fields in the downlink control information (DCI) of carrier aggregation communication, indicating the joint transmission parameters of multiple carrier aggregation component carriers (CCs), the increase in signaling overhead caused by the independent parameters of multiple DCI configurations in the prior art is solved, and a higher spectrum efficiency and a simplified configuration process is achieved.
Patent Information
- Application Number
- CN202510338198.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2021-04-08
- Filing Date
- 2021-04-09
- Publication Date
- 2025-06-10
AI Technical Summary
In carrier aggregation communication, the prior art requires sending multiple downlink control information (DCIs) to configure independent transmission parameters of each carrier aggregation component carrier (CC), resulting in an increase in signaling overhead and reducing spectral efficiency.
A method is proposed to indicate joint transmission parameters of multiple CCs by including a rate matching (RM) indication and a zero-power channel state information reference signal (ZP-CSI-RS) indication by including a joint field in a single DCI. The federated field may contain a common RM resource configuration suitable for multiple CCs or an independent RM configuration for each CC, and a ZP-CSI-RS resource collection identifier for multiple CCs.
By using joint fields in a single DCI, signaling overhead can be effectively reduced, spectral efficiency can be improved, and communication configuration process between base stations and user equipment (UEs) can be simplified.
Smart Images

Figure CN120128306A_ABST
Abstract
Description
[0001] This application is a divisional application of the invention patent application with the application date of April 9, 2021, the application number of 202180024997.2, and the title of "Providing Zero-Power Channel State Information Reference Signals and Rate Matching Configurations in Carrier Aggregation".
[0002] Cross Reference
[0003] This patent application claims the benefit of priority of the following applications: U.S. Patent Application No. 17 / 225,912, entitled "DOWNLINK CONTROL INFORMATION DESIGN FOR MULTI-COMPONENT CARRIER SCHEDULING", filed on April 8, 2021 by TAKEDA et al.; and U.S. Provisional Patent Application No. 63 / 008,437, entitled "DOWNLINK CONTROL INFORMATION DESIGN FOR MULTI-COMPONENT CARRIER SCHEDULING", filed on April 10, 2020 by TAKEDA et al.; each of the above applications is assigned to the assignee of this application and is hereby incorporated by reference in its entirety. Technical Field
[0004] Broadly speaking, the following relates to wireless communication, and more specifically, the following relates to downlink control information (DCI) design for multi-component carrier (CC) scheduling. Background Art
[0005] Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcasting, etc. These systems are capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multi-access systems include fourth-generation (4G) systems (e.g., Long Term Evolution (LTE) systems, Advanced LTE (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ 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 multi-access communication system may include one or more base stations or one or more network access nodes, each of which simultaneously supports communication for multiple communication devices (which may also be referred to as user equipment (UE)).
[0006] In some wireless communication systems, a UE may support carrier aggregation (CA), where the UE communicates with multiple cells simultaneously. For example, the UE may communicate with a first base station (e.g., a primary cell (PCell) or a first component carrier (CC)) and 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 an SCell or multiple CCs), where the UE communicates with two or more cells on a single base station simultaneously. Efficient techniques for implementing carrier aggregation communication are desired. SUMMARY
[0007] The described techniques relate to improved methods, systems, devices, and apparatuses for supporting a downlink control information (DCI) design for multi-component carrier (CC) scheduling. Generally, the described techniques provide for a base station to send DCI to a user equipment (UE), the DCI indicating a combined field for at least a first CC and a second CC in a carrier aggregation configuration. For example, the combined 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 may then communicate based on the DCI and the combined 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 CCs, or a combination thereof. Additionally, 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.
[0008] A method of wireless communication at a UE is described. The method may include: connecting to a base station via a first CC and a second CC according to a carrier aggregation configuration; receiving, from the base station, DCI including a combined field, the combined 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 combined field.
[0009] Describes an apparatus for wireless communication at a UE. 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 via a first CC and a second CC according to a carrier aggregation configuration; receive from the base station a DCI including a combined field, the combined 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 combined field.
[0010] Describes another apparatus for wireless communication at a UE. The apparatus may include: a unit for connecting to a base station via a first CC and a second CC according to a carrier aggregation configuration; a unit for receiving from the base station a DCI including a combined field, the combined 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 combined field.
[0011] Describes a non-transitory computer-readable medium storing code for wireless communication at a UE. The code may include instructions executable by at least one processor to perform the following operations: connect to a base station via a first CC and a second CC according to a carrier aggregation configuration; receive from the base station a DCI including a combined field, the combined 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 combined field.
[0012] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for performing the following operation: determine a common RMR from a set of common RMR configurations for the first CC and the second CC based on the combined field for the RM indication.
[0013] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, units, or instructions for performing the following operation: receive an indication of the set of common RMR configurations from the base station via radio resource control (RRC) signaling.
[0014] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for: receiving, via DCI from the base station, a trigger field for dynamic RM of the common RMR for the first CC and the second CC.
[0015] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, each bit of the combined field for the RM indication may include an indication of an RMR group configured for the common RMR configuration.
[0016] 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 combined field for the RM indication.
[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, from the base station, an indication of a per-CC RMR configuration for each CC in the carrier aggregation configuration, wherein the first RMR and the second RMR may be determined based on the per-CC RMR configuration.
[0018] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for: receiving, via DCI from the base station, a trigger field for dynamic RM of the first RMR, the second RMR, or both.
[0019] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, each bit of the combined field for the RM indication may include an indication of an RMR group configured for each CC in the carrier aggregation configuration.
[0020] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for: 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.
[0021] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following: receiving, from the base station, an additional field for an additional RM indication for the second CC, wherein communication with the base station may be based on the additional RM indication.
[0022] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following: determining, from the base station, a zero-power reference signal configuration for the first CC and the second CC based on the combined field for the zero-power reference signal indication.
[0023] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following: receiving, from the base station, a second additional field for an additional zero-power reference signal indication for the second CC.
[0024] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following: receiving, from the base station, a trigger field for a set identifier associated with the zero-power reference signal indication; and determining, based on the set identifier, a resource set for the zero-power reference signal indication, wherein the resource set may be used for the first CC and the second CC.
[0025] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following: 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.
[0026] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the trigger field may be received via DCI.
[0027] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the zero-power reference signal indication may include a ZP-CSI-RS resource set indication.
[0028] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the RM indication may include an RM mode group indication.
[0029] A method of wireless communication at a base station is described. The method may include: connecting to a UE via a first CC and a second CC according to a carrier aggregation configuration; sending to the UE a DCI including a combined field, the combined 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 combined field.
[0030] 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: connecting to a UE via a first CC and a second CC according to a carrier aggregation configuration; sending to the UE a DCI including a combined field, the combined 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 combined field.
[0031] Another apparatus for wireless communication at a base station is described. The apparatus may include: a unit for connecting to a UE via a first CC and a second CC according to a carrier aggregation configuration; a unit for sending to the UE a DCI including a combined field, the combined 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 combined field.
[0032] 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 perform the following operations: connecting to a UE via a first CC and a second CC according to a carrier aggregation configuration; sending to the UE a DCI including a combined field, the combined 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 combined field.
[0033] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following: sending an indication of a common RMR from a common RMR configuration set for the first CC and the second CC in the combined field for the RM indication.
[0034] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following: sending an indication of the common RMR configuration set to the UE via RRC signaling.
[0035] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following: sending a trigger field for dynamic RM for the common RMR for the first CC and the second CC to the UE via DCI.
[0036] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, each bit of the combined field for the RM indication may include an indication of an RMR group configured for the common RMR configuration.
[0037] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following: sending a first RMR for the first CC and a second RMR for the second CC in the combined field for the RM indication.
[0038] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following: 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.
[0039] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following: sending a trigger field for dynamic RM for the first RMR, the second RMR, or both to the UE via DCI.
[0040] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, each bit of the combined field for the RM indication may include an indication of an RMR group configured for each CC in the carrier aggregation configuration.
[0041] 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 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.
[0042] 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 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 combined field of the DCI.
[0043] 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 second additional field for an additional zero-power reference signal indication for the second CC to the UE.
[0044] 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 resource set for the zero-power reference signal indication, wherein the resource set may 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, the set identifier corresponding to the determined resource set.
[0045] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the trigger field may be sent via DCI.
[0046] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the zero-power reference signal indication may include a ZP-CSI-RS resource set indication.
[0047] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the RM indication may include an RM mode group indication. BRIEF DESCRIPTION OF THE DRAWINGS
[0048] Figure 1 Examples of systems for wireless communication that support a downlink control information (DCI) design for multi-component carrier (CC) scheduling in accordance with aspects of the present disclosure are shown.
[0049] Figure 2 Examples of wireless communication systems that support a DCI design for multi-CC scheduling in accordance with aspects of the present disclosure are shown.
[0050] Figure 3A and Figure 3B illustrates an example of a rate matching (RM) indicator that supports a DCI design for multi-CC scheduling in accordance with aspects of the present disclosure.
[0051] Figure 4A and Figure 4B illustrates an example of a multi-carrier configuration that supports a DCI design for multi-CC scheduling in accordance with aspects of the present disclosure.
[0052] Figure 5 illustrates an example of a multi-carrier configuration that supports a DCI design for multi-CC scheduling in accordance with aspects of the present disclosure.
[0053] Figure 6 illustrates an example of a DCI design that supports multi-CC scheduling in accordance with aspects of the present disclosure.
[0054] Figure 7 illustrates an example of a process flow that supports a DCI design for multi-CC scheduling in accordance with aspects of the present disclosure.
[0055] Figure 8 and Figure 9 illustrates a block diagram of a device that supports a DCI design for multi-CC scheduling in accordance with aspects of the present disclosure.
[0056] Figure 10 illustrates a block diagram of a user equipment (UE) communication manager that supports a DCI design for multi-CC scheduling in accordance with aspects of the present disclosure.
[0057] Figure 11 illustrates a diagram of a system that includes a device that supports a DCI design for multi-CC scheduling in accordance with aspects of the present disclosure.
[0058] Figure 12 and Figure 13 illustrates a block diagram of a device that supports a DCI design for multi-CC scheduling in accordance with aspects of the present disclosure.
[0059] Figure 14 illustrates a block diagram of a base station communication manager that supports a DCI design for multi-CC scheduling in accordance with aspects of the present disclosure.
[0060] Figure 15 illustrates a diagram of a system that includes a device that supports a DCI design for multi-CC scheduling in accordance with aspects of the present disclosure.
[0061] Figures 16 to 20 illustrates a flowchart that depicts a method that supports a DCI design for multi-CC scheduling in accordance with aspects of the present disclosure. Detailed Description
[0062] Some wireless communication systems can support communication between a user equipment (UE) and a base station over multiple aggregated component carriers (CCs), a feature known as carrier aggregation. For example, a base station can send the same downlink message to a UE across multiple CCs configured for carrier aggregation, enabling the UE to combine the downlink messages received on the multiple CCs to enhance the reliability of successfully receiving and decoding downlink information. In some cases, the base station can send separate messages to configure the communication on each CC configured for carrier aggregation. For example, the base station can 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 using a large amount of resources to indicate different transmission parameters for each CC.
[0063] As described herein, a base station can send a DCI to jointly indicate joint CC scheduling transmission parameters for downlink communication across multiple CCs. For example, the base station can send a joint field to the UE in the DCI, the joint field including rate matching (RM) indications for a first CC and a second CC, zero-power channel state information reference signal (ZP-CSI-RS) indications 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 can include a common RM resource (RMR) configuration applicable to both the first CC and the second CC, a per-CC RMR configuration indicating separate (e.g., or the same) RMRs for each CC in the CCs, or a combination thereof. Additionally, the ZP-CSI-RS indication can include a set identifier that indicates a resource set of ZP-CSI-RS resources for both the first CC and the second CC.
[0064] Aspects of the present disclosure are first described in the context of a wireless communication system. Additionally, aspects of the present disclosure are illustrated by additional wireless communication systems, RM indicators, multi-carrier configurations, DCI designs, and process flows. Aspects of the present disclosure are further illustrated by apparatus diagrams, system diagrams, and flowcharts related to DCI designs for multi-CC scheduling, and aspects of the present disclosure are described with reference to these diagrams.
[0065] Figure 1FIG. 0 illustrates an example of a wireless communication system 100 that supports a DCI design for multi-CC scheduling in accordance with aspects of the present disclosure. The wireless communication system 100 may include one or more base stations 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an evolved 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.
[0066] The base stations 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may be devices of different forms or having different capabilities. The base stations 105 and the UEs 115 may communicate wirelessly via one or more communication links 125. Each base station 105 may provide a coverage area 110, and the UEs 115 and the base stations 105 may establish one or more communication links 125 over the coverage area 110. The coverage area 110 may be an example of a geographic area over which the base stations 105 and the UEs 115 may support the transmission of signals in accordance with one or more radio access technologies.
[0067] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary, or mobile, or both at different times. The UEs 115 may be devices of different forms or having different capabilities. In Figure 1 FIG. some example UEs 115 are shown. The UEs 115 described herein are capable of communicating with various types of devices, such as other UEs 115, base stations 105, or network devices (e.g., core network nodes, relay devices, integrated access and backhaul (IAB) nodes, or other network devices), as Figure 1 shown.
[0068] The base stations 105 may communicate with the core network 130, or with each other, or both. For example, the base stations 105 may interface with the core network 130 via one or more backhaul links 120 (e.g., via S1, N2, N3, or other interfaces). The base stations 105 may communicate directly (e.g., directly between base stations 105) with each other over the backhaul links 120 (e.g., via X2, Xn, or other interfaces), or indirectly (e.g., via the core network 130) with each other, or both. In some examples, the backhaul links 120 may be or include one or more wireless links.
[0069] 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, radio base station, access point, radio transceiver, Node B, evolved Node B (eNB), next-generation Node B, or Gigabit Node B (either may be referred to as a gNB), home Node B, home evolved Node B, or some other suitable term.
[0070] The UE 115 may include or may be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or some other suitable term, where the "device" may also be referred to as a unit, station, terminal, or client, among other examples. The UE 115 may also include or may be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), multimedia / entertainment device (e.g., radio, MP3 player, or video device), camera, gaming device, navigation / location 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), tablet computer, laptop computer, netbook, smartbook, personal computer, smart device, wearable device (e.g., smartwatch, smart clothing, smart glasses, virtual reality goggles, smart wristband, smart jewelry (e.g., smart ring, smart bracelet)), drone, robot / robotic device, vehicle, vehicle device, meter (e.g., parking meter, electricity meter, gas meter, water meter), monitor, air pump, appliance (e.g., kitchen appliance, washing machine, dryer), location tag, medical / healthcare device, implant, sensor / actuator, display, or any other suitable device configured to communicate via a wireless or wired medium. In some examples, the UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine type communication (MTC) device, among other examples, which may be implemented in various items such as appliances, vehicles, meters, and other examples.
[0071] In one aspect, the techniques disclosed herein can be applicable to MTC or IoT UEs. The MTC or IoT UEs can 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 can refer to future technologies that can evolve from or be based on these technologies. For example, eMTC can include FeMTC (further eMTC), eFeMTC (further enhanced eMTC), mMTC (massive MTC), and NB-IoT can include eNB-IoT (enhanced NB-IoT) or FeNB-IoT (further enhanced NB-IoT).
[0072] UE 115 described herein is capable of communicating with various types of devices, such as other UEs 115 that can sometimes act as relays, as well as base stations 105 and network devices, including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, and other examples, as Figure 1 shown.
[0073] UE 115 and base station 105 can wirelessly communicate with each other via one or more communication links 125 over one or more carriers. The term "carrier" can refer to a collection of radio frequency spectrum resources having a defined physical layer structure for supporting communication link 125. For example, a carrier for communication link 125 can include a portion of a radio frequency spectrum band (e.g., a bandwidth part (BWP) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-APro, NR). Each physical layer channel can carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating operation for the carrier, user data, or other signaling. The wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. According to a carrier aggregation configuration, UE 115 can be configured with multiple downlink CCs and one or more uplink CCs. Carrier aggregation can be used with both frequency division duplex (FDD) CCs and time division duplex (TDD) CCs. Components within the wireless communication system can be coupled to each other (e.g., operatively, communicatively, functionally, electronically, and / or electrically).
[0074] 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 raster for discovery by UE 115. A carrier may operate in an independent mode where UE 115 performs initial acquisition and connection via the carrier, or the carrier may operate in a non-independent mode where a different carrier (e.g., of the same or a different radio access technology) is used to anchor the connection.
[0075] The communication link 125 shown in the wireless communication system 100 may include an uplink transmission from UE 115 to the base station 105, or a downlink transmission from the base station 105 to UE 115. A carrier may carry downlink or uplink communication (e.g., in FDD mode) or may be configured to carry both downlink and uplink communication (e.g., in TDD mode).
[0076] A carrier may be associated with a particular bandwidth of the radio frequency spectrum, and in some examples, the carrier bandwidth may be referred to as the "system bandwidth" of the carrier or the wireless communication system 100. For example, the carrier bandwidth may be one of a number of defined bandwidths for a carrier of a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)). Devices of the wireless communication system 100 (e.g., base station 105, 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 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, BWP) or all of the carrier bandwidth.
[0077] The signal waveform transmitted on a carrier can be composed of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system adopting MCM techniques, a resource element can include a symbol period (e.g., the duration of a modulated symbol) and a subcarrier, where the symbol period and the subcarrier spacing are inversely related. The number of bits carried by each resource element can depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both). Therefore, the more resource elements received by UE 115 and the higher the order of the modulation scheme, the higher the data rate for UE 115 can be. Wireless communication resources can refer to a combination of radio frequency spectrum resources, time resources, and space resources (e.g., spatial layers or beams), and the use of multiple spatial layers can further increase the data rate or data integrity for communication with UE 115.
[0078] One or more numerologies for a carrier can be supported, where a numerology can include a subcarrier spacing (Δf) and a cyclic prefix. A carrier can be divided into one or more BWPs with the same or different numerologies. In some examples, UE 115 can be configured with multiple BWPs. In some examples, a single BWP for a carrier can be active at a given time, and the communication for UE 115 can be restricted to one or more active BWPs.
[0079] The time intervals for the base station 105 or UE 115 can be represented as multiples of a basic time unit, which can be, for example, a sampling period of T s = 1 / (Δf max ·N f ) seconds, where Δf max can represent the maximum supported subcarrier spacing, and N f can represent the maximum supported discrete Fourier transform (DFT) size). The time intervals of the communication resources can be organized according to radio frames, each of which has a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).
[0080] Each frame may include a plurality of consecutively numbered sub - frames or time slots, and each sub - frame or time slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into sub - frames, and each sub - frame 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 sub - carrier spacing. Each time slot may include a number of symbol periods (e.g., which depends on the length of the 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 mini - slots each containing one or more symbols. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., N f f
[0081] Sub - frames, time slots, mini - slots, or symbols may be the smallest scheduling units (e.g., in the time domain) of the wireless communication system 100 and may be referred to as transmission time intervals (TTIs). 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 a burst of shortened TTIs (sTTIs)).
[0082] Physical channels may be multiplexed on a carrier according to various techniques. For example, time - division multiplexing (TDM) techniques, frequency - division multiplexing (FDM) techniques, or one or more of hybrid TDM - FDM techniques may be used to multiplex physical control channels and physical data channels on a downlink carrier. A control region for a physical control channel (e.g., a control resource set (CORESET)) may be defined by the number of symbol periods and may extend across the system bandwidth of the carrier or a subset of the system bandwidth. One or more control regions (e.g., CORESETs) may be configured for a 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 set may include a common search space set configured to send control information to a plurality of UEs 115 and a UE - specific search space set for sending control information to a particular UE 115.
[0083] Each base station 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity for communicating with the base station 105 (e.g., on a carrier), and may be associated with an identifier (e.g., physical cell identifier (PCID), virtual cell identifier (VCID), or other identifier) for distinguishing adjacent cells. In some examples, a cell may also refer to a geographic coverage area 110 or a portion (e.g., a sector) of the geographic coverage area 110 on which the logical communication entity operates. Depending on various factors (such as the capabilities of the base station 105), the range of such a cell may vary from a relatively small area (e.g., a structure, a subset of a structure) to a relatively large area. For example, a cell may be or include a building, a subset of a building, or an exterior space between or overlapping the geographic coverage areas 110, among other examples.
[0084] Macro cells typically cover a relatively large geographic area (e.g., with a radius of several kilometers) and may allow unrestricted access by UEs 115 having a service subscription with the network provider that supports the macro cell. In contrast to macro cells, small cells may be associated with a lower power base station 105, and small cells may operate in the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UEs 115 having a service subscription with the network provider, or may provide restricted access to UEs 115 associated with the small cell (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with users in a residence or office). The base station 105 may support one or more cells and may also support communication on one or more cells using one or more CCs.
[0085] In some examples, a carrier may support multiple cells and may be configured with different cell types according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access for different types of devices.
[0086] In some examples, the base station 105 can be mobile, and thus, provides communication coverage for a mobile geographic coverage area 110. In some examples, different geographic coverage areas 110 associated with different technologies can overlap, but different geographic coverage areas 110 can be supported by the same base station 105. In other examples, overlapping geographic coverage areas 110 associated with different technologies can be supported by different base stations 105. The wireless communication system 100 can include, for example, a heterogeneous network, where different types of base stations 105 use the same or different radio access technologies to provide coverage for respective geographic coverage areas 110.
[0087] The wireless communication system 100 can be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, the wireless communication system 100 can be configured to support ultra-reliable low-latency communication (URLLC) or mission-critical communication. The UE 115 can be designed to support ultra-reliability, 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 herein.
[0088] In some examples, the UE 115 is capable of communicating directly with other UEs 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 can be within the geographic coverage area 110 of the base station 105. Other UEs 115 in such a group can be outside the geographic coverage area 110 of the base station 105 or otherwise unable to receive transmissions from the base station 105. In some examples, groups of UEs 115 communicating via D2D communication can utilize a one-to-many (1:M) system, where each UE 115 transmits to each other UE 115 in the group. In some examples, the base station 105 facilitates the scheduling of resources for D2D communication. In other cases, D2D communication is performed between UEs 115 without involving the base station 105.
[0089] The core network 130 can provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 can be an evolved packet core (EPC) or a 5G core (5GC), which can include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and at least one user plane entity that routes packets to or interconnects with an external network (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). The control plane entity can manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management for a UE 115 served by a base station 105 associated with the core network 130. User IP packets can be transmitted through the user plane entity, which can provide IP address allocation and other functions. The user plane entity can be connected to a network operator IP service 150. The operator IP service 150 can include access to the Internet, an intranet, an IP multimedia subsystem (IMS), or a packet-switched streaming service.
[0090] Some network devices in the wireless communication system 100 (e.g., the base station 105) can include subcomponents such as an access network entity 140, which can be an example of an access node controller (ANC). Each access network entity 140 can communicate with a UE 115 through one or more other access network transmission entities 145 (which can be referred to as radio heads, intelligent radio heads, or transmit / receive points (TRPs)). Each access network transmission entity 145 can include one or more antenna panels. In some configurations, the various functions of each access network entity 140 or the base station 105 can be distributed across various network devices (e.g., radio heads and ANCs) or consolidated into a single network device (e.g., the base station 105).
[0091] The wireless communication system 100 can operate using one or more frequency bands (generally, in the range of 300 megahertz (MHz) to 300 gigahertz (GHz)). Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or the decimeter band because the wavelength range is approximately from one decimeter to one meter in length. UHF waves can be blocked or redirected by buildings and environmental features, but the waves can be sufficient to penetrate structures to serve a UE 115 located indoors in a macrocell. Compared to the transmission of smaller frequencies and longer waves using the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, the transmission of UHF waves can be associated with smaller antennas and shorter distances (e.g., less than 100 kilometers).
[0092] The wireless communication system 100 may also operate in the super high frequency (SHF) region using a frequency band from 3 GHz to 30 GHz (also referred to as the centimeter band) or in the extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) (also referred to as the millimeter band). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communication between the UE 115 and the base station 105, and the EHF antennas of the corresponding devices may be even smaller and more closely spaced compared to UHF antennas. 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 compared to SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions using one or more different frequency regions, and the specified use of frequency bands across these frequency regions may vary according to the country or regulatory body.
[0093] The wireless communication system 100 may utilize both licensed and unlicensed radio frequency spectrum bands. For example, the wireless communication system 100 may employ licensed-assisted access (LAA), LTE-unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band. When operating in an unlicensed radio frequency spectrum band, devices such as the base station 105 and the UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation in the unlicensed band may be based on a carrier aggregation configuration that combines with a carrier component (CC) operating in a licensed band (e.g., LAA). Operations in the unlicensed spectrum may include downlink transmissions, uplink transmissions, peer-to-peer (P2P) transmissions, or device-to-device (D2D) transmissions, among other examples.
[0094] The base station 105 or the UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of the base station 105 or the UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operation 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 communication 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 transmitted via the antenna ports.
[0095] The base station 105 or the UE 115 can use MIMO communication to exploit multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. Such a technique can be referred to as spatial multiplexing. For example, a transmitting device can transmit multiple signals via different antennas or different combinations of antennas. Similarly, a receiving device can receive multiple signals via different antennas or different combinations of antennas. Each of the multiple signals can be referred to as a separate spatial stream and can carry bits associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers can be associated with different antenna ports for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO) (where multiple spatial layers are transmitted to the same receiving device) and multi-user MIMO (MU-MIMO) (where multiple spatial layers are transmitted to multiple devices).
[0096] Beamforming (which can also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting device or a receiving device (e.g., base station 105, UE 115) to form or direct an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming can be achieved by combining signals transmitted via the antenna elements of an antenna array such that some signals propagating in a particular orientation relative to the antenna array experience constructive interference while other signals experience destructive interference. The adjustment of the signals transmitted via the antenna elements can include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to the signals carried via the antenna elements associated with the device. The adjustment associated with each of the antenna elements can be defined by a set of beamforming weights associated with a particular orientation (e.g., relative to the antenna array of the transmitting device or the receiving device, or relative to some other orientation).
[0097] The wireless communication system 100 can be a packet-based network that operates according to a hierarchical protocol stack. In the user plane, the communication at the bearer or packet data convergence protocol (PDCP) layer can be IP-based. The radio link control (RLC) layer can perform packet segmentation and reassembly for transmission over logical channels. The media access control (MAC) layer can perform priority handling and multiplexing of logical channels to transport channels. The MAC layer can also use error detection techniques, error correction techniques, or both to support retransmissions at the MAC layer to improve link efficiency. In the control plane, the radio resource control (RRC) protocol layer can provide the establishment, configuration, and maintenance of an RRC connection (which supports radio bearers for user plane data) between the UE 115 and the base station 105 or the core network 130. At the physical layer, transport channels can be mapped to physical channels.
[0098] The UE 115 and the base station 105 can support retransmissions of data to increase the likelihood that the data is successfully received. Hybrid automatic repeat request (HARQ) feedback is a technique for increasing the likelihood that data is correctly received over the communication link 125. HARQ can include a combination of error detection (e.g., using cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ can improve throughput at the MAC layer in poor radio conditions (e.g., low signal-to-noise conditions). In some examples, a device can support same-slot HARQ feedback, where the device can provide HARQ feedback for data received in previous symbols in a particular slot in that slot. In other cases, the device can provide HARQ feedback in a subsequent slot or according to some other time interval.
[0099] In some wireless communication systems, a transmitting device (e.g., the UE 115 or the base station 105) can perform channel coding techniques so that a receiving device is likely to receive the correct message sent by the transmitting device. RM can be an example of a channel coding technique, where the RM process can include repeating or puncturing bits of a channel according to a configured rate. The rate can indicate the number of repetitions, where the lower the rate, the more repetitions can be performed. For example, a rate of 1 / 4 can result in 4 repetitions of a bit, and a rate of 1 / 3 can result in 3 repetitions of a bit. The transmitting device can be configured to perform RM according to the rate. In some cases, the number of repetitions associated with a rate less than 1 / 3 may not provide additional coding gain and may result in inefficient use of the allocated resources.
[0100] In some systems, a transmitting device (e.g., base station 105) may use rate matching (RM) to determine and configure a set of bits to be transmitted to a receiving device (e.g., UE 115). For example, base station 105a may perform RM on one or more redundant versions (RVs) (e.g., to indicate where the bits of a codeword within an encoded information message start) that include control information, data, or a combination thereof to generate a transmission. Base station 105 may perform the RM process according to a coding rate, such as repetition or puncturing. The coding rate may indicate the proportion of useful data by indicating the ratio of information bits to coded bits. For example, a coding rate of 1 / 2 may indicate that for each information bit, two coded bits may be transmitted, where 2 minus 1 bit is redundant. Thus, the lower the coding rate, the more redundant bits base station 105 can generate. In some cases, the lower the coding rate, the more resource elements base station 105 may need to transmit a higher number of bits.
[0101] Base station 105 may transmit an RM indicator in the DCI sent to UE 115 to indicate how UE 115 should perform the RM process when receiving a downlink message from the base station. In some cases, UE 115 may be configured with at most two RM mode groups (e.g., rateMatchPatternGroups), where each RM mode group includes a resource block (RB) / symbol-level RM mode. For example, the RM mode may include a resource pattern around which UE 115 should perform rate matching for a downlink channel (e.g., physical downlink shared channel (PDSCH)). In some cases, UE 115 may perform rate matching around the union of all resources indicated in one or more signaled bitmaps. When UE 115 is configured with two RM mode groups, the number of bits of the RM indicator in the DCI may be two (2) bits. Thus, the first RM mode group (e.g., rateMatchPatternGroup1) may correspond to the first bit of the RM indicator, and the second RM mode group (e.g., rateMatchPatternGroup2) may correspond to the second bit of the RM indicator.
[0102] Additionally, in some cases, the triggering of channel state information reference signals (CSI-RS) in downlink scheduling DCI (e.g., zero-power CSI-RS (ZP-CSI-RS) triggering) can indicate the RM mode for use by UE 115. For example, ZP-CSI-RS can be used for downlink channel state information (CSI) acquisition and interference measurement. 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, ZP-CSI-RS resources can prevent downlink channels from being mapped to a set of REs. Thus, ZP-CSI-RS can be used to mute the REs within a transmission point downlink channel (e.g., from base station 105) to allow configured CSI interference measurement (CSI-IM) measurements for different interference hypotheses. In some cases, ZP-CSI-RS can be configured with a 16-bit bitmap. Each bit can control whether the set of REs should be muted (1) or not muted (0). For each transmission point, a ZP-CSI-RS configuration can be created according to the required CSI-IM configuration and the CSI-RS configuration used by the coordinated transmission points.
[0103] UE 115 can be configured with at most four (4) ZP-CSI-RS resource sets (e.g., ZP-CSI-RS resource sets) that provide RE-level rate matching modes. When UE 115 is configured with these ZP-CSI-RS resource sets, the number of bits in the ZP-CSI-RS indicator carried in DCI can be at most two (2) bits. The bit length of the DCI field for ZP-CSI-RS triggering can depend on the number of aperiodic ZP-CSI-RS resource sets configured for UE 115 in the DCI (e.g., at most two (2) bits).
[0104] Each non-zero code point triggered by ZP CSI-RS in 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) by indicating the aperiodic ZP CSI-RS resource set identifier for the UE 115 to add. For example, the first DCI code point (e.g., "01") can trigger the first resource set with the ZP-CSI-RS resource set identifier being one (1) (e.g., ZP-CSI-RS-ResourceSetIds = 1), the second DCI code point (e.g., "10") can trigger the second resource set with the ZP-CSI-RS resource set identifier being two (2) (e.g., ZP-CSI-RS-ResourceSetIds = 2), and the third DCI code point (e.g., "11") can trigger the third resource set with the ZP-CSI-RS resource set identifier being three (3) (e.g., ZP-CSI-RS-ResourceSetIds = 3). In some cases, the fourth DCI code point (e.g., "00") can be reserved for not triggering the aperiodic ZP-CSI-RS.
[0105] In some cases, the base station 105 can configure and indicate different transmission parameters, such as the RM indicator and / or ZP-CSI-RS indicator, in the DCI before sending the downlink message to the UE 115. If the UE 115 and the base station 105 communicate according to the 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 can send a separate DCI for each CC to configure / indicate the transmission parameters specific to each CC (e.g., even if similar transmission parameters are used for each CC). Therefore, sending separate DCIs for multiple CCs can increase the signaling overhead.
[0106] As described herein, base station 105 and UE 115 may use a dynamic spectrum sharing (DSS) configuration as part of enhancements to enable cross-carrier scheduling such that a single DCI can indicate transmission parameters for multiple CCs together. For example, as part of the DSS configuration for cross-carrier scheduling, a downlink channel (e.g., physical downlink control channel (PDCCH)) may be received on a secondary cell (SCell) (e.g., or second CC), and the PDCCH schedules a subsequent downlink channel (e.g., PDSCH) or uplink channel (e.g., physical uplink shared channel (PUSCH)) on a primary cell (PCell) or a primary-secondary cell (PSCell) (e.g., or first CC). Additionally or alternatively, as part of the DSS configuration for cross-carrier scheduling, a downlink channel (e.g., PDCCH) may be received on a PCell, PSCell, or SCell, and the PDCCH uses a single DCI to schedule subsequent downlink channels (e.g., PDSCH) on multiple cells (e.g., multiple CCs or PCell and SCell). 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. Additionally, 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 generally apply to cross-carrier scheduling in carrier aggregation.
[0107] In some cases, multi-CC scheduling may be used to improve spectral efficiency by configuring multiple CCs with a single DCI instead of multiple DCIs corresponding to each CC. Alternatively, multiple DCIs for multi-CC scheduling may be sufficient (e.g., when spectral efficiency is not an issue). Additionally, non-DSS scenarios can generally be used to purely improve spectral efficiency. When a single DCI is used for multi-CC scheduling (e.g., using DCI format 1_1 or 1_2), separate fields may be used (e.g., 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 combined field may be used (e.g., in a single DCI for multi-CC scheduling, the combined field may jointly indicate 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 have been defined yet.
[0108] The wireless communication system 100 may support an efficient technique for a UE 115 to receive DCI that indicates a combined field for at least a first CC and a second CC for a carrier aggregation configuration. For example, the combined 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 combined 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 CCs, or a combination thereof. Additionally, 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.
[0109] Figure 2 An example of a wireless communication system 200 that supports a DCI design for multi-CC scheduling in accordance with various aspects of the present disclosure is shown. In some examples, the wireless communication system 200 may implement aspects of the wireless communication system 100 or may 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 examples of the corresponding base station 105 and UE 115 as described with reference to Figure 1 In some cases, the base station 105-a may send configuration information to the UE 115-a on resources of a carrier 205 for a carrier aggregation configuration that 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). Additionally or alternatively, although not shown, the first CC 210 and the second CC 215 may be used to communicate with separate base stations 105 as part of a carrier aggregation configuration. In some cases, the carrier 205 and the first CC 210 may be the same carrier (e.g., carrying configuration information for the UE 115-a on the first CC 210 / PCell).
[0110] As described herein, the wireless communication system 200 may support a DCI design for multi-CC scheduling configurations 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 the resources of 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 combined field for the RM indicator 255 and / or the ZP-CSI-RS indicator 230 that configures a corresponding RMR for each CC and / or configures a ZP-CSI-RS resource set for each CC.
[0111] For example, when the RM indicator 225 includes a combined field for both the first CC 210 and the second CC 215, a single RM combined 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 combined field according to the multiple common RM configurations. Additionally, the base station 105-a may send an additional field (e.g., on / off trigger) for the dynamic RM of the common RMR across multiple CCs for the scheduled downlink channel (e.g., PDSCH) indicated by the DCI 220 (e.g., or an additional DCI). In some cases, each bit of the combined field may indicate different groups (e.g., RM mode groups, such as group 1 or group 2) configured for the UE 115a as the common RMR configuration for the first CC 210 and the second CC 215.
[0112] Additionally or alternatively, when the RM indicator 225 includes a combined field for both the first CC 210 and the second CC 215, a single RM combined field may indicate different RMRs for the first CC 210 and for the second CC 215 (e.g., multi-CC). In some cases, a per-CC RMR configuration for each CC in the CCs 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 combined field. Additionally, the base station 105-a may transmit an additional field (e.g., on / off trigger) of the dynamic RM for the individual RMR across the multi-CC for the scheduled downlink channel (e.g., PDSCH) indicated by the DCI 220 (e.g., or additional DCI). In some cases, each bit of the combined 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 (e.g., RM group) configured for the CC, the UE 115-a may not perform RM on the corresponding downlink channel (e.g., PDSCH) on that CC.
[0113] In some cases, when the ZP-CSI-RS indicator 230 includes a combined 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 the 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 the 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) for the CC without a corresponding resource set, but may apply PDSCH rate matching based on the indicator for the CCs having corresponding resource sets.
[0114] Additionally or alternatively, the DCI 220 may further include separate fields for the RM indicator 225, for the ZP-CSI-RS indicator 230, or both, to indicate the respective RM mode sets 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) fields of 0 to 2 bits each, as the RM indicator 225 and / or the ZP-CSI-RS indicator 230 for the first CC 210 and the second CC 215, respectively.
[0115] 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 indicated (e.g., via a combined field or separate fields) in the DCI 220 (e.g., indicating the corresponding RM parameters and / or ZP-CSI-RS parameters).
[0116] Figure 3A and Figure 3B respectively illustrate examples of RM indicators 300 and 301 that support DCI designs for multi-CC scheduling according to aspects of the present disclosure. In some examples, the RM indicators 300 and 301 may implement aspects of the wireless communication system 100, the wireless communication system 200, or both, or may be implemented by aspects of the wireless communication system 100, the wireless communication system 200, or both. As described with reference to Figure 2 the base station 105 may send a single DCI to configure different transmission parameters (such as RM indicators and ZP-CSI-RS indicators) for multiple CCs together, where the multiple CCs are 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 the first CC 305-a and the second CC 305-b according to the carrier aggregation configuration.
[0117] The RM indicator 300 may include a union field that indicates a union RMR configuration 310 (e.g., JointRM-Config), and the union RMR configuration 310 indicates different RM groups 315 for each CC 305 in the CC 305. For example, each bit of the union field may indicate a different RM group 315 (e.g., group 1 or group 2, such as different RM mode groups) configured for the CC 305 (e.g., multi-CC). That is, the first bit of the union field may indicate a first RM group 315-a (e.g., RM-group1) from the RM mode list, and the second bit of the union field may indicate a second RM group 315-b (e.g., RM-group2) from the RM mode list. Thus, based on which bit is triggered (e.g., which bit has a "1"), the UE 115 can identify which RM group (e.g., RM mode group) is to be used to perform row RM for the two CC 305s (e.g., the same RM group / common RMR is used for the two CC 305s). In some cases, the RM mode list may be a set of common RMR configurations indicated by the base station 105 to the UE 115 (e.g., via RRC signaling).
[0118] Additionally or alternatively, the RM indicator 301 may also include a union field that indicates different per-CC RMR configurations 320 (e.g., different RMRs) for the CC 305. For example, each bit of the union field may indicate a different RM group 315 (e.g., group 1 or group 2, such as different RM mode groups) configured for each CC 305. That is, each CC 305 may be configured with a separate per-CC RMR configuration 320 (e.g., PDSCH-Config field per CC), such as a first per-CC RMR 320-a configuration for the first CC 305-a and a second per-CC RMR 320-b for the second CC 305-b. Thus, the first bit of the union field may indicate a first RM group 315-a (e.g., RM-group1) from the RM mode list, and the second bit of the union 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 be different from the first CC 305-a to the second CC 305-b, such that different RMRs can be used for each CC 305 while still using a single union field in the DCI.
[0119] Figure 4A and Figure 4BAn example of multi-carrier configurations 400 and 401 in accordance with aspects of the present disclosure is shown. In some examples, multi-carrier configurations 400 and 401 may implement aspects of wireless communication system 100, wireless communication system 200, or both, or may be implemented by aspects of wireless communication system 100, wireless communication system 200, or both. For example, base station 105 and UE 115 may communicate according to a carrier aggregation configuration such that communication is performed with PCell 405 using a first CC of the carrier aggregation configuration and communication is performed with SCell 410 using a second CC of the carrier aggregation configuration. Additionally or alternatively, PCell 405 may be a PSCell for communication between UE 115 and base station 105. In some cases, PCell 415 (e.g., or PSCell) and SCell 410 may be part of the same base station 105 or may be part of different respective base stations 105.
[0120] Additionally, in some cases, SCell 410 may not use DSS (e.g., non-DSS), and PCell 405 may use DSS. For example, DSS communication may be used for a lower frequency band (e.g., less than 1 GHz), and non-DSS communication may be used for a higher frequency band (e.g., above 3.5 or 4.5 GHz). In some cases, based on the lower frequency band being more suitable for an anchor channel (e.g., for receiving configuration information) or mobility, the lower frequency band may be more suitable for communication on PCell 405 (e.g., and / or PSCell).
[0121] Multi-carrier configuration 400 may illustrate cross-carrier scheduling across SCell 410 and PCell 405. For example, UE 115 may receive DCI 415 on SCell 410, and DCI 415 may schedule PDSCH 420 (e.g., or PUSCH) on PCell 405. In some cases, SCell 410 may not include resources for uplink communication, and thus UE 115 may not be able to transmit on SCell 410 but may be able to transmit on PCell 405. Accordingly, base station 105 including SCell 410 may instruct UE 115 to transmit on PCell 405 based on signaling (e.g., DCI 415) in SCell 410. Additionally or alternatively, although not shown, UE 115 may receive DCI 415 on PCell 405, and as part of cross-carrier scheduling, DCI 415 may schedule a subsequent transmission (e.g., PDSCH or PUSCH) on SCell 410.
[0122] For multi-carrier configuration 401, UE 115 may receive DCI 415 on SCell 410, where DCI 415 includes joint scheduling for both PCell 405 and SCell 410. For example, DCI 415 may schedule a first PDSCH 425a on SCell 410 and a second PDSCH 425-b on PCell 405. As described herein, the joint scheduling of DCI 415 may include a joint field for configuring different transmission parameters for both PCell 405 and SCell 410 (e.g., on the respective CCs).
[0123] Figure 5 An example of a multi-carrier configuration 500 in accordance with aspects of the present disclosure is shown. In some examples, multi-carrier configuration 500 may implement aspects of wireless communication system 100, wireless communication system 200, or both, or may be implemented by aspects of wireless communication system 100, wireless communication system 200, or both. For example, base station 105 and UE 115 may communicate according to a carrier aggregation configuration such that a first CC of the carrier aggregation configuration is used to communicate with PCell 505 and a second CC of the carrier aggregation configuration is used to communicate with SCell 510. Additionally or alternatively, PCell 505 may be a PSCell for communication between UE 115 and base station 105. In some cases, PCell 505 (e.g., or PSCell) and SCell 510 may be part of the same base station 105 or may be part of different respective base stations 105.
[0124] In some cases, PCell 505 (e.g., or PSCell) may be a DSS carrier using a first subcarrier spacing (SCS) (e.g., 15 kHz), while SCell 510 may be a non-DSS carrier using a second SCS greater than the first SCS (e.g., 30 kHz). In some cases, SCell 510 may use a higher SCS based on using a higher frequency band for the non-DSS carrier. Additionally, PCell 505 may include uplink resources, while SCell 510 may not have uplink resources (e.g., as part of a downlink-only carrier aggregation configuration). In some cases, both PCell 505 and SCell 510 may be in a first frequency range (FR1). Additionally, SCell 510 (e.g., non-DSS carrier) may be a carrier in an unlicensed band (e.g., an unlicensed carrier for NR communication, such as an NR-U carrier).
[0125] In some cases, the cross-carrier scheduling from the SCell 510 to the PCell 505 may include DCI 515-a, which schedules the PDSCH 520-a (e.g., or PUSCH) on the PCell 505. Thus, this cross-carrier scheduling from the SCell 510 to the PCell 505 may not use the DCI from the PDCCH of the PCell 505 to the PDCCH of the SCell 510 (e.g., skip the DCI). Additionally or alternatively, for multi-CC scheduling (e.g., joint scheduling), it may include DCI 515-b received on the SCell 510, which schedules the PDSCH 520-b on the SCell 510 and schedules the PDSCH 520-c on the PCell 505. Based on this multi-CC scheduling, the spectral efficiency can be improved by using a single DCI instead of multiple DCIs.
[0126] Figure 6 An example of a DCI design 600 that supports multi-CC scheduling in accordance with various aspects of the present disclosure is shown. In some examples, the DCI design 600 may implement aspects of the wireless communication system 100, the wireless communication system 200, or both, or may be implemented by aspects of the wireless communication system 100, the wireless communication system 200, or both. For example, the base station 105 may use the DCI design 600 to configure transmission parameters for multiple CCs of a carrier aggregation configuration for communication with the UE 115.
[0127] In some cases, the base station 105 may send a first DCI 605-a including multiple fields (e.g., five (5) different fields as shown in Figure 6 for a first CC) 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 the signaling overhead and reduce the spectral efficiency.
[0128] Accordingly, 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, where the single DCI 610 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 adjacent 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 adjacent 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 (e.g., a single DCI instead of multiple DCIs).
[0129] Additionally, compared to separate DCIs for a CC, a combined indication field may be used to reduce the DCI size. For example, the sizes of DCI 610 and DCI 615 may be less than the combined size of the first DCI 605-a and the second DCI 605-b (e.g., separate DCIs for a CC). However, the sizes of DCI 610 and DCI 615 may still be relatively large and use more resources to indicate different configurations for each CC. Accordingly, the base station 105 may use and transmit a DCI 620 that uses a combined field as described herein to indicate the configurations for each CC in a single DCI and is smaller in size.
[0130] Figure 7 An example of a process flow 700 that supports a DCI design for multi-CC scheduling in accordance with various aspects of the present disclosure is shown. In some examples, the process flow 700 may implement aspects of the wireless communication system 100, the wireless communication system 200, or both or may 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 examples of the corresponding UE 115 and base station 105 as described with reference to Figures 1 - 6 described.
[0131] 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 the order shown, or operations performed by base station 105-b and UE 115-b may be performed in a different order or at different times. 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.
[0132] At 705, UE 115-b and base station 105-b may be connected via a first CC and a second CC according to a carrier aggregation configuration.
[0133] At 710, UE 115-b may receive from base station 105-b a DCI including a combined field that includes 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. 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.
[0134] At 715, UE 115-b may determine a common RMR from a set of common RMR configurations for the first CC and the second CC based on the combined field for the RM indication. For example, each bit of the combined field for the RM indication may include an indication of an RMR group configured for the common RMR configuration.
[0135] Additionally or alternatively, UE 115-b may determine a first RMR for the first CC and a second RMR for the second CC based on the combined field for the RM indication. For example, each bit of the combined field for the 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 process for the CC based on the corresponding RM group not being configured for the CC.
[0136] In some cases, UE 115-b may receive from base station 105-b an additional field (e.g., a separate field) for an additional RM indication for the second CC.
[0137] At 720, UE 115-b may receive from base station 105-b an indication of the set of common RMR configurations via RRC signaling. In some cases, UE 115-b may also receive from base station 105-b via DCI a trigger field for dynamic RM of the common RMR for the first CC and the second CC.
[0138] Additionally or alternatively, UE 115-b may receive an indication of per-CC RMR configuration for each CC in a carrier aggregation configuration from base station 105-b, where 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 a trigger field for dynamic RM for the first RMR, the second RMR, or both, from base station 105-b via DCI.
[0139] 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 first 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.
[0140] At 730, UE 115-b may receive a trigger field for a set identifier associated with the 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, where 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 the carrier aggregation configuration is not configured with a zero-power reference signal resource set corresponding to the determined resource set, where the trigger field for the CC is ignored based on the determination that the zero-power reference signal resource set is not configured for the CC.
[0141] At 735, UE 115-b and base station 105-b may communicate according to the carrier aggregation configuration based on DCI including a joint field.
[0142] Figure 8 Block diagram 800 of a device 805 supporting a DCI design for multi-CC scheduling in accordance with aspects of the present disclosure is shown. Device 805 may be an example of aspects of UE 115 as described herein. Device 805 may include a receiver 810, a UE communication manager 815, and a transmitter 820. Device 805 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).
[0143] 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 designs for multi-CC scheduling). The information may be passed to other components of the device 805. The receiver 810 may be an example of aspects of the transceiver 1120 described with reference to Figure 11 The receiver 810 may utilize a single antenna or an antenna array.
[0144] The UE communication manager 815 may be connected to the base station via a first CC and a second CC according to a carrier aggregation configuration. In some cases, the UE communication manager 815 may receive DCI including a combined field from the base station, and the combined 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. Additionally, the UE communication manager 815 may communicate with the base station based on the DCI including the combined field according to the carrier aggregation configuration. The UE communication manager 815 may be an example of aspects of the UE communication manager 1110 described herein.
[0145] The UE communication manager 815 or its sub-components may be implemented in hardware, software (e.g., executed by a processor), or any combination thereof. If implemented with code executed by a processor, the functions of the UE communication manager 815 or its sub-components may be performed by a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in this disclosure.
[0146] The UE communication manager 815 or its sub-components may be physically located at various positions, including being distributed such that portions of the functions are implemented by one or more physical components at different physical locations. In some examples, according to aspects of this disclosure, the UE communication manager 815 or its sub-components may be separate and distinct components. In some examples, according to aspects of this disclosure, the UE communication manager 815 or its sub-components may be combined with one or more other hardware components (including but not limited to input / output (I / O) components, transceivers, network servers, another computing device, one or more other components described in this disclosure, or a combination thereof).
[0147] The transmitter 820 may send signals generated by other components of the device 805. In some examples, the transmitter 820 may be co-located with the receiver 810 in a transceiver module. For example, the transmitter 820 may be described with reference to Figure 11Examples of aspects of the described transceiver 1120. The transmitter 820 can utilize a single antenna or an antenna array.
[0148] Figure 9 Block diagram 900 of a device 905 that supports a DCI design for multi-CC scheduling in accordance with aspects of the present disclosure is shown. The device 905 can be an example of aspects of the device 805 or UE 115 described herein. The device 905 can include a receiver 910, a UE communication manager 915, and a transmitter 935. The device 905 can also include a processor. Each of these components can communicate with each other (e.g., via one or more buses).
[0149] The receiver 910 can 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 the DCI design for multi-CC scheduling). The information can be passed to other components of the device 905. The receiver 910 can be an example of aspects of the transceiver 1120 described with reference to Figure 11 Examples of aspects of the described transceiver 1120. The receiver 910 can utilize a single antenna or an antenna array.
[0150] The UE communication manager 915 can be an example of aspects of the UE communication manager 815 described herein. The UE communication manager 915 can include a carrier aggregation component 920, a combined field component 925, and a carrier aggregation communication component 930. The UE communication manager 915 can be an example of aspects of the UE communication manager 1110 described herein.
[0151] The carrier aggregation component 920 can be connected to a base station via a first CC and a second CC according to a carrier aggregation configuration.
[0152] The combined field component 925 can receive DCI including a combined field from the base station, the combined 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.
[0153] The carrier aggregation communication component 930 can communicate with the base station according to the carrier aggregation configuration based on the DCI including the combined field.
[0154] The transmitter 935 can send 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 an example of aspects of the transceiver 1120 described with reference to Figure 11 Examples of aspects of the described transceiver 1120. The transmitter 935 can utilize a single antenna or an antenna array.
[0155] Figure 10FIG. 1000 is a block diagram showing a UE communication manager 1005 that supports a DCI design for multi-CC scheduling in accordance with aspects of the present disclosure. 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 combined 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 combined ZP-CSI-RS component 1040. Each of these modules may communicate directly or indirectly with each other (e.g., via one or more buses).
[0156] The carrier aggregation component 1010 may be connected to a base station via a first CC and a second CC according to a carrier aggregation configuration.
[0157] The combined field component 1015 may receive DCI including a combined field from the base station, the combined 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.
[0158] The carrier aggregation communication component 1020 may communicate with the base station according to a carrier aggregation configuration based on DCI including a combined field.
[0159] The common RMR component 1025 may determine a common RMR from a set of common RMR configurations for the first CC and the second CC based on a combined field for an RM indication. In some examples, the common RMR component 1025 may receive an indication of the set of common RMR configurations from the base station via RRC signaling. Additionally, the common RMR component 1025 may receive a trigger field for dynamic RM of the common RMR for the first CC and the second CC from the base station via DCI. In some cases, each bit of the combined field for the RM indication may include an indication of an RMR group configured for the common RMR configuration.
[0160] Each CC RMR component 1030 may determine a first RMR for a first CC and a second RMR for a second CC based on a combined field for RM indication. In some examples, each 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, where the first RMR and the second RMR are determined based on the per-CC RMR configuration. Additionally, each CC RMR component 1030 may receive, via DCI from the base station, a trigger field for dynamic RM for the first RMR, the second RMR, or both. In some examples, each 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 the CC based on the determination that the corresponding RMR group is not configured for the CC. In some cases, each bit of the combined field for RM indication may include an indication of an RMR group configured for each CC in a carrier aggregation configuration.
[0161] The per-field indication component 1035 may receive, from the base station, an additional field for additional RM indication for a second CC, where communication with the base station is based on the additional RM indication. Additionally or alternatively, the per-field indication component 1035 may receive, from the base station, a second additional field for additional zero-power reference signal indication for a second CC.
[0162] The combined ZP-CSI-RS component 1040 may determine, from a base station, a zero-power reference signal configuration for a first CC and a second CC based on a combined field for zero-power reference signal indication. In some examples, the combined ZP-CSI-RS component 1040 may receive a trigger field for a set identifier associated with the zero-power reference signal indication from the base station, and may determine a resource set for zero-power reference signal indication based on the set identifier, where the resource set is for the first CC and the second CC. In some cases, the trigger field may be received via DCI. In some examples, the combined ZP-CSI-RS component 1040 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, where the trigger field is ignored for the CC based on the determination that the zero-power reference signal resource set is not configured for the CC.
[0163] Figure 11FIG. shows a system 1100 including a device 1105 that supports a DCI design for multi-CC scheduling in accordance with aspects of the present disclosure. The device 1105 may be an example of a device 805, a device 905, or a UE 115 as described herein or include components of the device 805, the device 905, or the UE 115. The device 1105 may include components for two-way voice and data communication, 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., bus 1145).
[0164] The UE communication manager 110 may be connected to a base station via a first CC and a second CC according to a carrier aggregation configuration. In some cases, the UE communication manager 1110 may receive DCI including a combined field from the base station, the combined 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. Additionally, the UE communication manager 1110 may communicate with the base station based on the DCI including the combined field according to the carrier aggregation configuration.
[0165] The I / O controller 1115 may manage input and output signals for the device 1105. The I / O controller 1115 may also manage peripheral devices not integrated into the device 1105. In some cases, the I / O controller 1115 may represent a physical connection or port to an external peripheral device. In some cases, the I / O controller 1115 may utilize an operating system such as or another known operating system. In other cases, the I / O controller 1115 may represent a modem, a keyboard, a mouse, a touch screen, or similar device or interact with the above devices. In some cases, the I / O controller 1115 may be implemented as part of a processor. In some cases, a user may interact with the device 1105 via the I / O controller 1115 or via a hardware component controlled by the I / O controller 1115.
[0166] The transceiver 1120 may communicate bi-directionally 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 bi-directionally with another wireless transceiver. The transceiver 1120 may also include a modem for modulating packets and providing the modulated packets to the antenna for transmission, and for demodulating packets received from the antenna.
[0167] 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 simultaneously transmitting or receiving multiple wireless transmissions.
[0168] 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 that includes instructions that, when executed, cause the processor to perform the various functions described herein. In some cases, in addition, the memory 1130 may further contain a basic input / output system (BIOS) that may control basic hardware or software operations, such as interactions with peripheral components or devices.
[0169] The processor 1140 may include intelligent hardware devices (e.g., a general-purpose processor, a DSP, a central processing unit (CPU), a microcontroller, an ASIC, an FPGA, a programmable logic device, discrete gate or transistor logic components, discrete hardware components, 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., the memory 1130) to cause the device 1105 to perform various functions (e.g., functions or tasks supporting DCI design for multi-CC scheduling).
[0170] The code 1135 may include instructions for implementing aspects of the present disclosure, including instructions for supporting wireless communications. The code 1135 may be stored on 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.
[0171] Figure 12 Block diagram 1200 illustrates a device 1205 that supports DCI design for multi-CC scheduling in accordance with aspects of the present disclosure. The device 1205 may be an example of aspects of the base station 105 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).
[0172] 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 designs for multi-CC scheduling). The information may be passed to other components of the device 1205. The receiver 1210 may be an example of aspects of the transceiver 1520 described with reference to Figure 15 The receiver 1210 may utilize a single antenna or an antenna array.
[0173] The base station communication manager 1215 may be connected to the UE via a first CC and a second CC according to a carrier aggregation configuration. In some cases, the base station communication manager 1215 may send DCI including a combined field to the UE, and the combined 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. Additionally, the base station communication manager 1215 may communicate with the UE based on the DCI including the combined field according to the carrier aggregation configuration. The base station communication manager 1215 may be an example of aspects of the base station communication manager 1510 described herein.
[0174] The base station communication manager 1215 or its sub-components may be implemented in hardware, software (e.g., executed by a processor), or any combination thereof. If implemented with code executed by a processor, the functions of the base station communication manager 1215 or its sub-components may be performed by a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic, discrete hardware component, or any combination thereof designed to perform the functions described in this disclosure.
[0175] The base station communication manager 1215 or its sub-components may be physically located at different positions, including being distributed such that portions of the functions are implemented by one or more physical components at different physical locations. In some examples, according to aspects of this disclosure, the base station communication manager 1215 or its sub-components may be separate and distinct components. In some examples, according to aspects of this disclosure, the base station communication manager 1215 or its sub-components may be combined with one or more other hardware components (including but not limited to I / O components, transceivers, network servers, another computing device, one or more other components described in this disclosure, or a combination thereof).
[0176] The transmitter 1220 may send 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 an example of aspects of the transceiver 1520 described with reference to Figure 15 The transmitter 1220 may utilize a single antenna or an antenna array.
[0177] Figure 13 FIG. 1300 is a block diagram of a device 1305 that supports DCI designs for multi-CC scheduling in accordance with aspects of the present disclosure. The device 1305 may be an example of aspects of the device 1205 or the base station 105 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).
[0178] 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 associated with DCI designs for multi-CC scheduling). The information may be passed to other components of the device 1305. The receiver 1310 may be an example of aspects of the transceiver 1520 described with reference to Figure 15 . The receiver 1310 may utilize a single antenna or an antenna array.
[0179] The base station communication manager 1315 may be an example of aspects of the base station communication manager 1215 described herein. The base station communication manager 1315 may include a carrier aggregation component 1320, a combined field indicator 1325, and a carrier aggregation communication component 1330. The base station communication manager 1315 may be an example of aspects of the base station communication manager 1510 described herein.
[0180] The carrier aggregation component 1320 may be connected to a UE via a first CC and a second CC according to a carrier aggregation configuration.
[0181] The combined field indicator 1325 may send a DCI to the UE that includes a combined field that 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.
[0182] The carrier aggregation communication component 1330 may communicate with the UE according to a carrier aggregation configuration based on the DCI that includes the combined field.
[0183] The transmitter 1335 may send signals generated by other components of the device 1305. In some examples, the transmitter 1335 may be co-located with the receiver 1310 in a transceiver module. For example, the transmitter 1335 may be an example of aspects of the transceiver 1520 described with reference to Figure 15 . The transmitter 1335 may utilize a single antenna or an antenna array.
[0184] Figure 14FIG. 1400 is a block diagram showing a base station communication manager 1405 that supports a DCI design for multi-CC scheduling in accordance with aspects of the present disclosure. 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 combined 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 combined ZP-CSI-RS indicator 1440. Each of these modules may communicate directly or indirectly with each other (e.g., via one or more buses).
[0185] The carrier aggregation component 1410 may be connected to a UE via a first CC and a second CC according to a carrier aggregation configuration.
[0186] The combined field indicator 1415 may send a DCI including a combined field to the UE, the combined 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.
[0187] The carrier aggregation communication component 1420 may communicate with the UE based on the DCI including the combined field according to a carrier aggregation configuration.
[0188] The common RMR indicator 1425 may send an indication of a common RMR from a set of common RMR configurations for the first CC and the second CC in a combined field for RM indication. In some examples, the common RMR indicator 1425 may send an indication of the set of common RMR configurations to the UE via RRC signaling. Additionally, the common RMR indicator 1425 may send a trigger field for the dynamic RM of the common RMR for the first CC and the second CC to the UE via DCI. In some cases, each bit of the combined field for RM indication may include an indication of an RMR group configured for the common RMR configuration.
[0189] Each CC RMR indicator 1430 may send a first RMR for a first CC and a second RMR for a second CC in a combined field for RM indication. In some examples, each CC RMR indicator 1430 may send an indication of per-CC RMR configuration for each CC in a carrier aggregation configuration to the UE, where the first RMR and the second RMR are determined based on the per-CC RMR configuration. Additionally, each CC RMR indicator 1430 may send a trigger field for dynamic RM for the first RMR, the second RMR, or both to the UE via DCI. In some cases, each bit of the combined field for RM indication may include an indication of an RMR group configured for each CC in a carrier aggregation configuration.
[0190] The additional field indicator 1435 may send an additional field for additional RM indication for the second CC to the UE, where 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 additional zero-power reference signal indication for the second CC to the UE.
[0191] The combined 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 a zero-power reference signal indication in a combined field of DCI. In some examples, the combined ZP-CSI-RS indicator 1440 may determine a set of resources for the zero-power reference signal indication, where the set of resources is for the first CC and the second CC; and may send a trigger field for a set identifier associated with the zero-power reference signal indication to the UE, the set identifier corresponding to the determined set of resources. In some cases, the trigger field may be sent via DCI.
[0192] Figure 15 FIG. shows a system 1500 including a device 1505 that supports a DCI design for multi-CC scheduling in accordance with aspects of the present disclosure. The device 1505 may be an example of the device 1205, the device 1305, or the base station 105 described herein or may include components of the device 1205, the device 1305, or the base station 105. The device 1505 may include components for two-way voice and data communication, including components for sending and receiving communication, 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 communicate electronically via one or more buses (e.g., bus 1550).
[0193] The base station communication manager 1510 may be connected to the UE via a first CC and a second CC according to a carrier aggregation configuration. In some cases, the base station communication manager 1510 may send DCI including a combined field to the UE, the combined 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. Additionally, the base station communication manager 1510 may communicate with the UE based on the DCI including the combined field according to the carrier aggregation configuration.
[0194] The network communication manager 1515 may manage communication with the core network (e.g., via one or more wired backhaul links). For example, the network communication manager 1515 may manage the transmission of data communication for client devices (e.g., one or more UEs 115).
[0195] 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 the antenna for transmission, and for demodulating packets received from the antenna.
[0196] In some cases, the wireless device may include a single antenna 1525. However, in some cases, the device may have more than one antenna 1525, which are capable of simultaneously transmitting or receiving multiple wireless transmissions.
[0197] The memory 1530 may include RAM, ROM, or a combination thereof. The memory 1530 may store computer-readable code 1535, the computer-readable code 1535 including instructions that, when executed by a processor (e.g., processor 1540), cause the device to perform various functions described herein. In some cases, in addition, the memory 1530 may further contain a BIOS, which may control basic hardware or software operations, such as interactions with peripheral components or devices.
[0198] The processor 1540 may include intelligent hardware devices (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, the processor 1540 may be configured to operate a memory array using a memory controller. In some cases, the memory controller may be integrated into the processor 1540. The processor 1540 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1530) to cause the device 1505 to perform various functions (e.g., functions or tasks supporting DCI design for multi-CC scheduling).
[0199] The inter-station communication manager 1545 may manage communication with other base stations 105 and may include a controller or scheduler for collaboratively controlling communication with the UE 115 with other base stations 105. For example, the inter-station communication manager 1545 may coordinate the scheduling of transmissions to the UE 115 to implement various interference mitigation techniques such as beamforming or joint transmission. In some examples, the inter-station communication manager 1545 may provide an X2 interface within the LTE / LTE-A wireless communication network technology to provide communication between the base stations 105.
[0200] The code 1535 may include instructions for implementing aspects of the present disclosure, including instructions for supporting wireless communication. The code 1535 may be stored in a non-transitory computer-readable medium (e.g., system memory or other type 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.
[0201] Figure 16 A flowchart illustrating a method 1600 for supporting DCI design for multi-CC scheduling in accordance with aspects of the present disclosure is shown. The operations of method 1600 may be implemented by the UE 115 or its components as described herein. For example, the operations of method 1600 may be performed by a UE communication manager as described with reference to Figures 8 to 11 described. In some examples, the UE may execute an instruction set to control functional units of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the functions described below.
[0202] At 1605, the UE may connect to a base station via a first CC and a second CC according to a carrier aggregation configuration. The operation of 1605 may be performed according to the methods described herein. In some examples, aspects of the operation of 1605 may be performed by a carrier aggregation component as described with reference to Figures 8 to 11 described.
[0203] At 1610, the UE may receive DCI including a combined field from the base station, the combined 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 operation of 1610 may be performed according to the methods described herein. In some examples, aspects of the operation of 1610 may be performed by a combined field component as described with reference to Figures 8 to 11 described.
[0204] At 1615, the UE may communicate with the base station according to a carrier aggregation configuration based at least in part on DCI including a combined field. The operations at 1615 may be performed according to the methods described herein. In some examples, aspects of the operations at 1615 may be performed by a carrier aggregation communication component as described with reference to Figures 8 to 11 described.
[0205] Figure 17 FIG. shows a flow diagram of a method 1700 illustrating a DCI design supporting multi-CC scheduling in accordance with aspects of the present disclosure. The operations of method 1700 may be implemented by a UE 115 or components thereof as described herein. For example, the operations of method 1700 may be performed by a UE communication manager as described with reference to Figures 8 to 11 described. In some examples, the UE may execute an instruction set to control functional units of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the functions described below.
[0206] At 1705, the UE may connect to the base station via a first CC and a second CC according to a carrier aggregation configuration. The operations at 1705 may be performed according to the methods described herein. In some examples, aspects of the operations at 1705 may be performed by a carrier aggregation component as described with reference to Figures 8 to 11 described.
[0207] At 1710, the UE may receive DCI including a combined field from the base station, the combined 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 at 1710 may be performed according to the methods described herein. In some examples, aspects of the operations at 1710 may be performed by a combined field component as described with reference to Figures 8 to 11 described.
[0208] At 1715, the UE may determine a common RMR from a set of common RMR configurations for the first CC and the second CC based at least in part on the combined field for the RM indication. The operations at 1715 may be performed according to the methods described herein. In some examples, aspects of the operations at 1715 may be performed by a common RMR component as described with reference to Figures 8 to 11 described.
[0209] At 1720, the UE may communicate with the base station according to a carrier aggregation configuration based at least in part on DCI including a combined field. The operations at 1720 may be performed according to the methods described herein. In some examples, aspects of the operations at 1720 may be performed by a carrier aggregation communication component as described with reference to Figures 8 to 11 described.
[0210] Figure 18 FIG. 1800 is a flow chart illustrating a method 1800 that supports a DCI design for multi-CC scheduling in accordance with aspects of the present disclosure. Operations of method 1800 may be implemented by a UE 115 or components thereof as described herein. For example, operations of method 1800 may be performed by a UE communication manager as described with reference to Figures 8 to 11 FIG. In some examples, the UE may execute an instruction set to control functional units of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the functions described below.
[0211] At 1805, the UE may connect to a base station via a first CC and a second CC according to a carrier aggregation configuration. The operation at 1805 may be performed according to methods described herein. In some examples, aspects of the operation at 1805 may be performed by a carrier aggregation component as described with reference to Figures 8 to 11 FIG.
[0212] At 1810, the UE may receive from the base station a DCI including a combined field, the combined 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 operation at 1810 may be performed according to methods described herein. In some examples, aspects of the operation at 1810 may be performed by a combined field component as described with reference to Figures 8 to 11 FIG.
[0213] At 1815, the UE may determine a first RMR for the first CC and a second RMR for the second CC at least partially based on the combined field for the RM indication. The operation at 1815 may be performed according to methods described herein. In some examples, aspects of the operation at 1815 may be performed by a per-CC RMR component as described with reference to Figures 8 to 11 FIG.
[0214] At 1820, the UE may communicate with the base station according to the carrier aggregation configuration at least partially based on the DCI including the combined field. The operation at 1820 may be performed according to methods described herein. In some examples, aspects of the operation at 1820 may be performed by a carrier aggregation communication component as described with reference to Figures 8 to 11 FIG.
[0215] Figure 19 FIG. 1900 is a flow chart illustrating a method 1900 that supports a DCI design for multi-CC scheduling in accordance with aspects of the present disclosure. Operations of method 1900 may be implemented by a UE 115 or components thereof as described herein. For example, operations of method 1900 may be performed by a UE communication manager as described with reference to Figures 8 to 11performed by the described UE communication manager. 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 aspects of the functions described below.
[0216] At 1905, the UE may be connected to the base station via a first CC and a second CC according to a carrier aggregation configuration. The operation of 1905 may be performed according to the methods described herein. In some examples, aspects of the operation of 1905 may be performed by a carrier aggregation component as described with reference to Figures 8 to 11 the description.
[0217] At 1910, the UE may receive DCI including a combined field from the base station, the combined 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 operation of 1910 may be performed according to the methods described herein. In some examples, aspects of the operation of 1910 may be performed by a combined field component as described with reference to Figures 8 to 11 the description.
[0218] At 1915, the UE may determine the zero-power reference signal configuration for the first CC and the second CC from the base station at least partially based on the combined field for the zero-power reference signal indication. The operation of 1915 may be performed according to the methods described herein. In some examples, aspects of the operation of 1915 may be performed by a combined ZP-CSI-RS component as described with reference to Figures 8 to 11 the description.
[0219] At 1920, the UE may communicate with the base station according to the carrier aggregation configuration at least partially based on the DCI including the combined field. The operation of 1920 may be performed according to the methods described herein. In some examples, aspects of the operation of 1920 may be performed by a carrier aggregation communication component as described with reference to Figures 8 to 11 the description.
[0220] Figure 20 FIG. shows a flowchart of a method 2000 for illustrating a DCI design that supports multi-CC scheduling according to aspects of the present disclosure. The operations of method 2000 may be implemented by the base station 105 or its components as described herein. For example, the operations of method 2000 may be performed by a base station communication manager as described with reference to Figures 12 to 15 the description. 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 aspects of the functions described below.
[0221] At 2005, the base station can be connected to the UE via a first CC and a second CC according to a carrier aggregation configuration. The operations at 2005 can be performed according to the methods described herein. In some examples, aspects of the operations at 2005 can be performed by a carrier aggregation component as described with reference to Figures 12 to 15 described.
[0222] At 2010, the base station can send DCI including a combined field to the UE, the combined 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 at 2010 can be performed according to the methods described herein. In some examples, aspects of the operations at 2010 can be performed by a combined field indicator as described with reference to Figures 12 to 15 described.
[0223] At 2015, the base station can communicate with the UE according to a carrier aggregation configuration at least in part based on DCI including a combined field. The operations at 2015 can be performed according to the methods described herein. In some examples, aspects of the operations at 2015 can be performed by a carrier aggregation communication component as described with reference to Figures 12 to 15 described.
[0224] The following provides an overview of aspects of the present disclosure:
[0225] 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 combined field from the base station, the combined 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 at least in part based on the downlink control information including the combined field.
[0226] Aspect 2: The method according to aspect 1, further comprising: determining a common rate matching resource from a plurality of common rate matching resource configurations for the first component carrier and the second component carrier at least in part based on the combined field for the rate matching indication.
[0227] Aspect 3: The method according to aspect 2, further comprising: receiving an indication of the plurality of common rate matching resource configurations from the base station via radio resource control signaling.
[0228] Aspect 4: The method according to any one of Aspects 2 to 3 further includes: receiving, via downlink control information, a trigger field for dynamic rate matching of the common rate matching resources for the first component carrier and the second component carrier from the base station.
[0229] Aspect 5: The method according to any one of Aspects 2 to 4, wherein each bit of the combined field for the rate matching indication includes an indication of a rate matching resource group configured for the common rate matching resource configuration.
[0230] Aspect 6: The method according to any one of Aspects 1 to 5 further includes: determining, at least in part based on the combined field for the rate matching indication, a first rate matching resource for the first component carrier and a second rate matching resource for the second component carrier.
[0231] Aspect 7: The method according to Aspect 6 further includes: receiving, from the base station, an indication of per-component-carrier rate matching resource configuration for each component carrier in the carrier aggregation configuration, 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.
[0232] Aspect 8: The method according to any one of Aspects 6 to 7 further includes: receiving, via downlink control information, a trigger field for dynamic rate matching of the first rate matching resource, the second rate matching resource, or both from the base station.
[0233] Aspect 9: The method according to any one of Aspects 6 to 8, wherein each bit of the combined field for the rate matching indication includes an indication of a rate matching resource group for each component carrier configured for the carrier aggregation configuration.
[0234] Aspect 10: The method according to Aspect 9 further includes: determining that a 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 at least in part based on the determination that the corresponding rate matching resource group is not configured for the component carrier.
[0235] Aspect 11: The method according to any one of Aspects 1 to 10 further includes: receiving, from the base station, an additional field for an additional rate matching indication for the second component carrier, wherein communication with the base station is at least in part based on the additional rate matching indication.
[0236] Aspect 12: The method according to any one of Aspects 1 to 11 further includes: determining, at least in part based on the combined field for the zero-power reference signal indication, a zero-power reference signal configuration for the first component carrier and the second component carrier from the base station.
[0237] Aspect 13: The method according to Aspect 12 further includes: receiving, from the base station, a second additional field for an additional zero-power reference signal indication for the second component carrier.
[0238] Aspect 14: The method according to any one of Aspects 12 to 13 further includes: receiving, from the base station, a trigger field for a set identifier associated with the zero-power reference signal indication; and determining, at least in part based on the set identifier, a resource set for the zero-power reference signal indication, where the resource set is for the first component carrier and the second component carrier.
[0239] Aspect 15: The method according to Aspect 14 further includes: determining that the component carriers of the carrier aggregation configuration are not configured with a zero-power reference signal resource set corresponding to the determined resource set, where the trigger field is at least in part ignored for the component carrier based on the determination that the zero-power reference signal resource set is not configured for the component carrier.
[0240] Aspect 16: The method according to any one of Aspects 14 to 15, where the trigger field is received via downlink control information.
[0241] Aspect 17: The method according to any one of Aspects 1 to 16, where the zero-power reference signal indication includes a zero-power channel state information reference signal resource set indication.
[0242] Aspect 18: The method according to any one of Aspects 1 to 17, where the rate matching indication includes a rate matching mode group indication.
[0243] Aspect 19: A method for wireless communication at a base station includes: 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 combined field to the UE, the combined 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 at least in part based on the downlink control information including the combined field.
[0244] Aspect 20: The method according to aspect 19 further includes: sending an indication of a common rate matching resource for a plurality of common rate matching resource configurations from the first component carrier and the second component carrier in the joint field for the rate matching indication.
[0245] 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.
[0246] 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 resource for the first component carrier and the second component carrier to the UE via downlink control information.
[0247] 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 includes an indication of a rate matching resource group configured for the common rate matching resource configuration.
[0248] 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.
[0249] 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 at least partially determined based on the per-component-carrier rate matching resource configuration.
[0250] 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.
[0251] 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 includes an indication of a rate matching resource group configured for each component carrier in the carrier aggregation configuration.
[0252] 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 communication with the UE is at least partially based on the additional rate matching indication.
[0253] Aspect 29: The method according to any one of Aspects 19 to 28 further includes: sending, to the UE, a zero-power reference signal configuration for the first component carrier and the second component carrier, at least partially based on the zero-power reference signal indication in the combined field of the downlink control information.
[0254] Aspect 30: The method according to Aspect 29 further includes: sending, to the UE, a second additional field for an additional zero-power reference signal indication for the second component carrier.
[0255] 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, where the resource set is for the first component carrier and the second component carrier; and sending, to the UE, a trigger field for a set identifier associated with the zero-power reference signal indication, the set identifier corresponding to the determined resource set.
[0256] Aspect 32: The method according to Aspect 31, wherein the trigger field is sent via the downlink control information.
[0257] Aspect 33: The method according to any one of Aspects 19 to 32, wherein the zero-power reference signal indication includes a zero-power channel state information reference signal resource set indication.
[0258] Aspect 34: The method according to any one of Aspects 19 to 33, wherein the rate matching indication includes a rate matching mode group indication.
[0259] Aspect 35: An apparatus for wireless communication at a UE, including: at least one processor; a memory coupled to the at least one processor; and instructions stored in the memory and executable by the at least one processor to cause the apparatus to perform the method according to any one of Aspects 1 to 18.
[0260] Aspect 36: An apparatus for wireless communication at a UE, including at least one unit for performing the method according to any one of Aspects 1 to 18.
[0261] Aspect 37: A non-transitory computer-readable medium storing code for wireless communication at a UE, the code including instructions executable by a processor to perform the method according to any one of Aspects 1 to 18.
[0262] 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 stored in the memory and executable by the at least one processor to cause the apparatus to perform the method according to any one of Aspects 19 to 34.
[0263] 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.
[0264] 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.
[0265] It should be noted that the methods described herein describe possible implementations, and the operations and steps may be rearranged or otherwise modified, and other implementations are possible. Additionally, aspects from two or more methods may be combined.
[0266] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for purposes of illustration, and the LTE, LTE-A, LTE-A Pro, or NR terminology may be used in most of the description, the techniques described herein are applicable beyond the scope of LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to 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.
[0267] The information and signals described herein may be represented using any of a variety of different technologies and methods. For example, the data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
[0268] The various illustrative blocks and components described in connection with the present disclosure can be implemented or performed with a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).
[0269] The functions described herein can be implemented in hardware, software executed by a processor, or any combination thereof. Whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise, software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, execution threads, procedures, functions. If implemented in software executed by a processor, the functions can be stored on or transmitted through a computer readable medium as one or more instructions or code. Other examples and implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software (e.g., executed by a processor), hardware, hardwiring, or any combination of these items. The features implementing the functions can also be physically located at various positions, including being distributed such that different portions of the functions are implemented at different physical locations.
[0270] A computer-readable medium includes both a non-transitory computer storage medium and a communication medium, where the communication medium includes any medium that facilitates transfer of a computer program from one place to another. The non-transitory storage medium can be any available medium that can be accessed by a general purpose computer or a special purpose computer. By way of example and not limitation, the non-transitory computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, phase change memory, compact disc read only memory (CD-ROM) or other optical disc storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store the desired program code units in the form of instructions or data structures and that can be accessed by a general purpose or special purpose computer, or a general purpose or special purpose processor. Additionally, any connection is properly termed a computer-readable medium. For example, if software is transmitted using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. As used herein, disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc, where disks typically reproduce data magnetically, while discs reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable medium.
[0271] As used herein (including in the claims), the "or" as used in a list of items (e.g., a list of items that ends with a phrase such as "at least one of" or "one or more of") indicates an inclusive list, such that a list of, for example, at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Additionally, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an exemplary step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on". As used herein, the term "and / or" when used in a list of two or more items means that any one of the listed items can be taken by itself, or any combination of two or more of the listed items can be taken. For example, if a composition is described as including components A, B, and / or C, the composition can include: only A; only B; only C; A and B combined; A and C combined; B and C combined; or A, B, and C combined.
[0272] In the drawings, similar components or features may have the same reference numeral. Additionally, various components of the same type may be distinguished by following the reference numeral with a dash and a second numeral, the second numeral being used to differentiate among similar components. If only the first reference numeral is used in the specification, the description applies to any one of the similar components having the same first reference numeral, regardless of the second reference numeral or any subsequent reference numerals.
[0273] The description set forth herein in connection with the drawings describes exemplary configurations and does not represent all examples that may be implemented or that are within the scope of the claims. The term "exemplary" as used herein means "serving as an example, instance, or illustration" and not "preferred" or "advantageous over other examples." For the purpose of providing an understanding of the described technology, the detailed description includes specific details. However, the technology may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.
[0274] This description is provided to enable a person skilled in the art to make or use the present disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the present disclosure is not limited to the examples and designs described herein but is accorded the broadest 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 downlink control information including rate matching indications for the first component carrier and the second component carrier, wherein the rate matching indications include an indication of a rate matching resource group configured for the first component carrier in the carrier aggregation configuration and an indication that the second component carrier is not configured with a corresponding rate matching resource group; determining a first rate matching resource for the first component carrier at least in part based on the rate matching indications; and communicating with the network entity according to the carrier aggregation configuration at least in part based on the downlink control information including the rate matching indications.
2. The method according to claim 1, wherein at least in part based on the rate matching indications, the first rate matching resource is included in a plurality of common rate matching resources for the first component carrier.
3. The method according to claim 2, further comprising: receiving an indication of the plurality of common rate matching resources from the network entity via radio resource control signaling.
4. The method according to claim 1, further comprising: avoiding performing a rate matching process for the second component carrier at least in part based on the indication that the second component carrier is not configured with the corresponding rate matching resource group.
5. The method according to claim 1, wherein the downlink control information includes zero-power reference signal indications for the first component carrier and the second component carrier.
6. The method according to claim 5, wherein the zero-power reference signal configuration for the first component carrier and the second component carrier is at least in part based on the zero-power reference signal indications.
7. The method according to claim 5, wherein a resource set for the zero-power reference signal indication is at least in part based on the zero-power reference signal indication, and the resource set is for the first component carrier and the second component carrier.
8. The method according to claim 5, wherein at least in part based on the zero-power reference signal indication, a component carrier in the carrier set configuration is not configured with a zero-power reference signal resource set.
9. A user equipment (UE) for wireless communication, comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and operable individually or collectively to execute the code such that the UE performs 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 downlink control information including rate matching indications for the first component carrier and the second component carrier, wherein the rate matching indications include an indication of a rate matching resource group configured for the first component carrier in the carrier aggregation configuration and an indication that the second component carrier is not configured with a corresponding rate matching resource group; Determine a first rate matching resource for the first component carrier at least in part based on the rate matching indication; and Communicate with the network entity according to the carrier aggregation configuration at least in part based on the downlink control information including the rate matching indication.
10. The UE according to claim 9, wherein, At least in part based on the rate matching indication, the first rate matching resource is included in a plurality of common rate matching resources for the first component carrier.
11. The UE according to claim 10, wherein, The one or more processors are further individually or collectively operable to execute the code such that the UE performs the following operations: Receive an indication of the plurality of common rate matching resources from the network entity via radio resource control signaling.
12. The UE according to claim 10, wherein, The one or more processors are further individually or collectively operable to execute the code such that the UE performs the following operations: Receive, via the downlink control information, a trigger field for dynamic rate matching for one of the plurality of common rate matching resources for the first component carrier from the network entity.
13. The UE according to claim 9, wherein, The one or more processors are further individually or collectively operable to execute the code such that the UE performs the following operations: Avoid performing a rate matching process for the second component carrier at least in part based on the indication that the second component carrier is not configured with the corresponding rate matching resource group.
14. The UE according to claim 9, wherein, The downlink control information includes zero-power reference signal indications for the first component carrier and the second component carrier.
15. The UE according to claim 14, wherein, The zero-power reference signal configuration for the first component carrier and the second component carrier is at least in part based on the zero-power reference signal indication.
16. The UE according to claim 14, wherein, The resource set for the zero-power reference signal indication is at least in part based on the zero-power reference signal indication, wherein the resource set is for the first component carrier and the second component carrier.
17. The UE according to claim 14, wherein, At least in part based on the zero-power reference signal indication, the component carriers in the carrier set configuration are not configured with a zero-power reference signal resource set.
18. A network entity for wireless communication, comprising: One or more memories storing processor-executable code; and One or more processors, coupled to the one or more memories and individually or collectively operable to execute the code such that the network entity performs the following operations: Connect to a user equipment (UE) via a first component carrier and a second component carrier according to a carrier aggregation configuration; Transmit downlink control information including rate matching indications for the first component carrier and the second component carrier, where the rate matching indications include an indication of a rate matching resource group configured for the first component carrier in the carrier aggregation configuration and an indication that the second component carrier is not configured with a corresponding rate matching resource group; and communicate with the UE according to the carrier aggregation configuration at least in part based on the downlink control information including the rate matching indications.
19. The network entity according to claim 18, wherein the one or more processors are also operable, individually or collectively, to execute the code such that the UE performs the following operations: send an indication of a plurality of common rate matching resources to the network entity via radio resource control signaling.
20. The network entity according to claim 18, wherein the downlink control information includes zero-power reference signal indications for the first component carrier and the second component carrier.
21. An apparatus for wireless communication, comprising: means for connecting to a network entity via a first component carrier and a second component carrier according to a carrier aggregation configuration; means for receiving downlink control information including rate matching indications for the first component carrier and the second component carrier, where the rate matching indications include an indication of a rate matching resource group configured for the first component carrier in the carrier aggregation configuration and an indication that the second component carrier is not configured with a corresponding rate matching resource group; means for determining a first rate matching resource for the first component carrier at least in part based on the rate matching indications; and means for communicating with the network entity according to the carrier aggregation configuration at least in part based on the downlink control information including the rate matching indications.
22. A computer-readable storage medium having instructions stored thereon that are executable by one or more processors to perform the following operations: connect to a network entity via a first component carrier and a second component carrier according to a carrier aggregation configuration; receive downlink control information including rate matching indications for the first component carrier and the second component carrier, wherein the rate matching indications include an indication of a rate matching resource group configured for the first component carrier in the carrier aggregation configuration and an indication that the second component carrier is not configured with a corresponding rate matching resource group; determine a first rate matching resource for the first component carrier at least in part based on the rate matching indications; and communicate with the network entity according to the carrier aggregation configuration at least in part based on the downlink control information including the rate matching indications.
23. A method for wireless communication at a network entity, comprising: connect to a user equipment (UE) via a first component carrier and a second component carrier according to a carrier aggregation configuration; Transmit downlink control information including rate matching indications for the first component carrier and the second component carrier, wherein the rate matching indications include an indication of a rate matching resource group configured for the first component carrier in the carrier aggregation configuration and an indication that the second component carrier is not configured with a corresponding rate matching resource group; And Communicate with the UE according to the carrier aggregation configuration at least in part based on the downlink control information including the rate matching indications.
24. An apparatus for wireless communication, Comprising: A unit for connecting to a user equipment (UE) via a first component carrier and a second component carrier according to a carrier aggregation configuration; A unit for transmitting downlink control information including rate matching indications for the first component carrier and the second component carrier, wherein the rate matching indications include an indication of a rate matching resource group configured for the first component carrier in the carrier aggregation configuration and an indication that the second component carrier is not configured with a corresponding rate matching resource group; And A unit for communicating with the UE according to the carrier aggregation configuration at least in part based on the downlink control information including the rate matching indications.
25. A computer-readable storage medium having instructions stored thereon that are executable by one or more processors to perform the following operations: Connect to a user equipment (UE) via a first component carrier and a second component carrier according to a carrier aggregation configuration; Transmit downlink control information including rate matching indications for the first component carrier and the second component carrier, Wherein The rate matching indications include an indication of a rate matching resource group configured for the first component carrier in the carrier aggregation configuration and an indication that the second component carrier is not configured with a corresponding rate matching resource group; And Communicate with the UE according to the carrier aggregation configuration at least in part based on the downlink control information including the rate matching indications.