Limiting of unicast DCI processing with multi-cell and single-cell scheduling

Abstract

Embodiments are described herein for processing and counting unicast downlink control information (DCI) when both single cell scheduling and multi-cell scheduling are configured to a UE. In some embodiments, a wireless communication system determines, for an additional unicast DCI format, an available processing capability of the UE associated with both unscheduled and scheduled cells in a set of cells during a time slot based on the use of a multi-cell scheduled unicast DCI format.

Description

TECHNICAL FIELD

[0001] This application relates generally to wireless communication systems, including handling and counting of unicast downlink control information when both single-cell scheduling and multi-cell scheduling are configured for a UE. BACKGROUND

[0002] Wireless mobile communication technology uses various standards and protocols to transmit data between base stations and wireless communication devices. For example, wireless communication system standards and protocols can include, for example, 3rd Generation Partnership Project (3GPP) Long-Term Evolution (LTE) (e.g., 4G), 3GPP New Radio (NR) (e.g., 5G), and Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (commonly referred to as Wi-Fi standards within the industry ® ).

[0003] As contemplated by 3GPP, different wireless communication system standards and protocols can use various radio access networks (RANs) for communication between base stations (which can also be referred to as RAN nodes, network nodes, or simply nodes) of the RAN and wireless communication devices referred to as user equipment (UE). A 3GPP RAN can include, for example, a Global System for Mobile Communications (GSM), Enhanced Data Rates for GSM Evolution (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and / or Next Generation Radio Access Network (NG-RAN).

[0004] Each RAN can use one or more radio access technologies (RATs) to perform communication between base stations and UEs. For example, a GERAN implements GSM and / or EDGE RAT, a UTRAN implements Universal Mobile Telecommunications System (UMTS) RAT or other 3GPP RAT, an E-UTRAN implements LTE RAT (sometimes referred to simply as LTE), and an NG-RAN implements NR RAT (which is sometimes referred to herein as a 5G RAT, 5G NR RAT, or simply NR). In certain deployments, an E-UTRAN can also implement NR RAT. In certain deployments, an NG-RAN can also implement LTE RAT.

[0005] A base station used by a RAN can correspond to that RAN. One example of an E-UTRAN base station is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly denoted as an evolved Node B, enhanced Node B, eNodeB, or eNB). One example of an NG-RAN base station is a Next Generation Node B (sometimes also referred to as a gNode B or gNB).

[0006] The RAN, through its connection with a core network (CN), together with the external entities, provides communication services to users. For example, an E-UTRAN can utilize an Evolved Packet Core (EPC), while a NG-RAN can utilize a 5G Core Network (5GC). BRIEF DESCRIPTION OF DRAWINGS

[0007] To easily identify the discussion of any particular element or act, one or more of the highest three digits in a figure number refer to the figure number in which that element is first introduced.

[0008] Figure 1 Counting DCI transmissions during a slot is illustrated according to some embodiments.

[0009] Figure 2 Counting DCI transmissions during a slot using a second method is illustrated according to some embodiments.

[0010] Figure 3 A set of cells is illustrated according to some embodiments, where cell 1 is the scheduling cell and is also part of the set of cells.

[0011] Figure 4 A method of operating a network node is illustrated according to some embodiments.

[0012] Figure 5 A method for operating a UE is illustrated according to some embodiments.

[0013] Figure 6 An example architecture of a wireless communication system according to embodiments disclosed herein is illustrated.

[0014] Figure 7 A system for performing signaling between a wireless device and a network device according to embodiments disclosed herein is illustrated. DETAILED DESCRIPTION

[0015] Various embodiments are described with reference to a user equipment (UE). However, references to a UE are provided for illustrative purposes only. Example embodiments can be used with any electronic component that can establish a connection with a network and is configured with hardware, software, and / or firmware for exchanging information and data with the network. Thus, a UE as described herein is used to represent any appropriate electronic component.

[0016] In New Radio (NR), UE features are specified to limit the number of unicast downlink control information (DCI) that a UE can handle per time slot of a scheduling cell. For slot-based monitoring, one unicast DCI scheduling downlink (DL) and one unicast DCI scheduling uplink (UL) per time slot per scheduled component carrier (CC) is supported for frequency division duplex (FDD). Additionally, for slot-based monitoring, one unicast DCI scheduling DL and two unicast DCIs scheduling UL per time slot per scheduled CC is supported for time division duplex (TDD). This is valid for both self-scheduling and cross-carrier scheduling in case of same subcarrier spacing (SCS) between scheduling cell and scheduled cell.

[0017] For cross-carrier scheduling with different SCS combinations, lower-to-higher SCS for scheduling to scheduled cell can be supported. In other words, a scheduling cell can have a lower SCS, while the corresponding scheduled cell can have a higher SCS. The baseline capability can be the same as the same SCS case as discussed above. In addition, advanced capabilities are also specified for DL and UL.

[0018] For cross-carrier scheduling with different SCS combinations, up to X unicast DCI scheduling for DL per scheduled CC can be supported, where X is based on a pair of scheduling CC SCS and scheduled CC SCS (scheduling CC SCS, scheduled CC SCS). Example candidate values for X for DL can be: X = {1, 2, 4} for each pair of scheduling CC SCS, scheduled CC SCS set to (15kHz, 120kHz), (15kHz, 60kHz), (30kHz, 120kHz); and X = {2} for each pair of scheduling CC SCS, scheduled CC SCS set to (15kHz, 30kHz), (30kHz, 60kHz), (60kHz, 120kHz). Similarly, up to X unicast DCI scheduling for UL per scheduled CC can be supported, where X is based on a pair (scheduling CC SCS, scheduled CC SCS). Example candidate values for X for UL can be: X = {1, 2, 4} for each pair of scheduling CC SCS, scheduled CC SCS set to (15kHz, 120kHz), (15kHz, 60kHz), (30kHz, 120kHz); and X = {2} for each pair of scheduling CC SCS, scheduled CC SCS set to (15kHz, 30kHz), (30kHz, 60kHz), (60kHz, 120kHz).

[0019] Furthermore, for cross-carrier scheduling with different SCS combinations, a higher-to-lower SCS for scheduling to a scheduled cell can be supported. For DL scheduling, the following components apply for CCS from higher SCS to lower SCS. A UE can support one unicast DCI scheduling DL per N consecutive scheduling CC slots of a scheduled CC for FDD scheduling CCs. A UE can support one unicast DCI scheduling DL per N consecutive scheduling CC slots of a scheduled CC for TDD scheduling CCs. N is based on a pair (scheduling CC SCS, scheduled CC SCS). Example candidate values of N can be: N = 2 for each pair of scheduling CC SCS, scheduled CC SCS set to (30kHz, 15kHz), (60kHz, 30kHz), (120kHz, 60kHz); N = 4 for each pair of scheduling CC SCS, scheduled CC SCS set to (60kHz, 15kHz), (120kHz, 30kHz); and N = 8 for each pair of scheduling CC SCS, scheduled CC SCS set to (120kHz, 15kHz).

[0020] Similarly, for UL scheduling, the following components apply for CCS from higher SCS to lower SCS. A UE can support one unicast DCI scheduling UL per N consecutive scheduling CC slots of a scheduled CC for FDD scheduling CCs. A UE can support two unicast DCI scheduling UL per N consecutive scheduling CC slots of a scheduled CC for TDD scheduling CCs. N is based on a pair (scheduling CC SCS, scheduled CC SCS). Example candidate values of N can be: N = 2 for each pair of scheduling CC SCS, scheduled CC SCS set to (30kHz, 15kHz), (60kHz, 30kHz), (120kHz, 60kHz); N = 4 for each pair of scheduling CC SCS, scheduled CC SCS set to (60kHz, 15kHz), (120kHz, 30kHz); and N = 8 for each pair of scheduling CC SCS, scheduled CC SCS set to (120kHz, 15kHz).

[0021] Some wireless communication systems can include features for UE support of multi-cell physical downlink shared channel (PDSCH) scheduling. The number of unicast DL DCIs to process for multi-cell PDSCH scheduling configured by DCI format 1_3 (e.g., for a set of cells) can be one unicast DCI per time slot for the scheduling cells (for a set of cells) for FDD / TDD scheduling cells. It is not clear whether to count only DCI format 1_3 or both legacy DCI formats (1_1, 1_2, 1_0, etc.) and DCI format 1_3. Additionally, advanced UE capabilities can be introduced for a larger number of unicast DL DCIs.

[0022] Similarly, for uplink, the number of unicast UL DCIs to process for multi-cell PUSCH scheduling configured by DCI format 0_3 (for a set of cells) can be one unicast DCI per time slot for the scheduling cells (for a set of cells) for FDD scheduling cells and two unicast DCIs per time slot for the scheduling cells (for a set of cells) for TDD scheduling cells. It is not clear whether to count only DCI format 0_3 or both legacy DCI formats and DCI format 0_3. Additionally, advanced UE capabilities can be introduced for a larger number of unicast UL DCIs.

[0023] Some embodiments herein provide different options in how unicast DCIs are processed and counted in the case where both single-cell scheduling and multi-cell scheduling are configured to the UE. In some embodiments, UE complexity can not increase compared to legacy UEs for single-cell scheduling, at least as a baseline UE capability. Some embodiments describe how unicast DCI processing for a set of cells is counted. Some embodiments describe how to handle counting for a UE configured with both legacy unicast DCI formats and new multi-cell scheduling DCI formats. Some embodiments describe how to define baseline and advanced UE capabilities for unicast DCI processing. Some embodiments consider both cases of same SCS and different SCS between scheduling cells and scheduled cells.

[0024] Figure 1 Counting of DCI transmissions 102 during a slot 104 is illustrated in accordance with some embodiments. In the illustrated embodiment, in the case where a UE is capable of and configured with both multi-cell scheduling and single-cell scheduling for DL, and is also configured with same subcarrier spacing between scheduling cells and co-scheduling cells within a set, for DL scheduling for FDD / TDD, the number of unicast DCIs (e.g., DCI format 1_3 108) to process for a set of cells (set of cells 106) and for each cell within the set of cells (e.g., cell 1, cell 2, cell 3, and cell 4) is equal to one per time slot for the scheduling cells.

[0025] In the illustrated embodiment, the plurality of unicast DCI includes single-cell scheduling legacy unicast DCI formats (such as formats 1 0, 1 1, 1 2) and the new multi-cell scheduling unicast DCI format 1 3. In some embodiments, for DCI format 1 3, the DCI format is counted for all cells within a set of cells in the case that the UE processes the DCI format in a slot 104 of a scheduling cell, regardless of whether all cells within the set are scheduled. For example, in some embodiments, a set of cells 106 can be configured with up to four cells, but the network can schedule fewer than the number of cells in the set of cells 106. However, even if a cell is not scheduled, the DCI format 1 3 will be counted, thereby exhausting the DCI count for all cells in the set of cells 106. This can limit the number of DCI that the UE is to process, thereby ensuring that the complexity of the UE processing is not increased.

[0026] Based on the limit of one unicast DCI processing per slot for a scheduling cell using the illustrated DCI counting technique, the following possibilities can be supported. The UE can process the DCI format 1 3 once for the set of cells 106. Without processing the DCI format 1 3 for the set of cells 106, the UE can process the legacy DCI formats 1 0, 1 1, 1 2 once per scheduled cell within the set.

[0027] For example, in the illustrated embodiment, for DL where the same subcarrier spacing is used between a scheduling cell and a co-scheduling cell within the set of cells 106, the following is an example of DCI counting. The set of cells 106 includes cell 1, cell 2, cell 3, and cell 4. During a slot 104, cell 1 and cell 2 are scheduled, and cell 3 and cell 4 are not scheduled. Further, during the slot 104, a DCI format 1 3 108 is transmitted to the UE through PDSCH for cell 1 and cell 2. The UE and network node can count the number of unicast DCI processing per cell within a slot to determine whether additional DCI can be processed. In the illustrated embodiment, each of the cells has a count of one, and even though cell 3 and cell 4 are not scheduled and do not receive a DCI format 1 3 for cell 3 and cell 4, the slot cannot be used for additional DCI processing for any of the cells in the set of cells 106.

[0028] A similar DCI counting approach can be used for UL where the same subcarrier spacing is used between the scheduling cells within the set and the co-scheduling cells. In case the UE is capable of and configured with both multi-cell scheduling and single-cell scheduling for UL, and also configured with the same subcarrier spacing between the scheduling cells within the set and the co-scheduling cells, for UL scheduling for FDD and TDD, the number of unicast DCIs the UE is to process for the cell set and for each cell within the cell set can be equal to one and two per slot of the scheduling cell, respectively. The multiple unicast DCIs can include single-cell scheduling legacy unicast DCI formats (such as formats 0 0, 0 1, 0 2) and the new multi-cell scheduling unicast DCI format 0 3.

[0029] In some embodiments, for DCI format 0 3 for FDD case, in case the UE processes this DCI format in a slot of the scheduling cell, this DCI format can be counted for all cells within the cell set regardless of whether all cells within the set are scheduled or not. For TDD case, based on the limit of two unicast DCI processing per slot of the scheduling cell, the following possibilities can be allowed. The first possibility can be that the UE can process DCI format 0 3 twice for the cell set 106 during a slot. The second possibility is that in case DCI format 0 3 is processed once per the cell set, legacy DCI formats 0 0, 0 1, 0 2 can be processed once per the scheduled cells within the set during a slot. The third possibility is that in case there is no DCI format 0 3 processing for the cell set, legacy DCI formats 0 0, 0 1, 0 2 can be processed twice per the scheduled cells within the set during a slot.

[0030] Figure 2 An example of counting DCI transmissions 202 during a slot 204 using the second approach is illustrated in accordance with some embodiments. In the illustrated embodiment, in case the UE is capable of and configured with both multi-cell scheduling and single-cell scheduling for DL, and also configured with the same subcarrier spacing between the scheduling cells within the set and the co-scheduling cells, for DL scheduling for FDD / TDD, the number of unicast DCIs (e.g., DCI format 1 3 206) the UE is to process for the cell set (cell set 208) and for each cell within the cell set (e.g., cell 1, cell 2, cell 3, and cell 4) is equal to one per slot of the scheduling cell.

[0031] In the illustrated implementation, the multiple unicast DCIs include single-cell scheduling legacy unicast DCI formats (such as formats 1_0, 1_1, 1_2) and a new multi-cell scheduling unicast DCI format 1_3. In some implementations, for DCI format 1_3, when the UE processes the DCI format in time slot 204 of the scheduling cell, the DCI format is counted for the cells within the cell set that are actually scheduled by the processed DCI format 1_3.

[0032] For example, in some implementations, cell set 208 may be configured with up to four cells, but the network can schedule fewer cells than the number in cell set 208. When scheduling a cell for DCI format 1_3 206, the DCI count can be set to one, and then no DCI is processed for that cell during time slot 204. When no cell is scheduled for a cell, the DCI format 1_3 count is not performed for that cell, thus allowing unscheduled cells to process the legacy unicast DCI format during time slot 204.

[0033] Based on the limitation of performing unicast DCI processing once per time slot for scheduled cells using the illustrated DCI counting technology, the following possibilities can be supported. In the illustrated implementation, when DCI format 1_3 206 is processed once for cell set 208 and at least a given cell within the set is scheduled using this DCI format, it is not expected that the UE will process legacy DCI formats 1_0, 1_1, and 1_2 for that given scheduled cell. Furthermore, when DCI format 1_3 206 is processed once for cell set and at least a given cell within the set is not scheduled using this DCI format, legacy DCI formats 1_0, 1_1, and 1_2 can be processed once for that given cell that was not scheduled using DCI format 1_3. When DCI format 1_3 206 is not processed for cell set, legacy DCI formats 1_0, 1_1, and 1_2 can be processed once within cell set 208 according to the scheduled cell.

[0034] For example, in the illustrated implementation, for a DL where the same subcarrier spacing is used between scheduled cells and co-scheduled cells within cell set 208, an example of DCI counting is given below. Cell set 208 includes cell 1, cell 2, cell 3, and cell 4. During time slot 204, cells 1 and 2 are scheduled, while cells 3 and 4 are not scheduled. Furthermore, during time slot 204, DCI format 1_3 206 is transmitted to the UE via PDSCH for cells 1 and 2. The UE and network nodes can count the number of unicast DCI processes performed for each cell within the time slot to determine whether additional DCI can be processed. In the illustrated implementation, cells 1 and 2 have a DCI count of one. Therefore, it is not expected that the UE will process additional DCI during time slot 204. Conversely, cells 3 and 4 are unscheduled, and their counts remain zero. Therefore, the UE can still process the legacy DCI format for cells 3 and 4 during time slot 204.

[0035] A similar DCI counting method can be used for UL, where the same subcarrier spacing is used between scheduled cells and co-scheduled cells within the set. When the UE is capable of and configured with both multi-cell scheduling and single-cell scheduling for UL, and is also configured with the same subcarrier spacing between scheduled cells and co-scheduled cells within the set, the number of unicast DCIs that the UE needs to process for the cell set and for each cell within the cell set can be equal to 1 and 2 per time slot of the scheduled cell, respectively, for UL scheduling for FDD and TDD. Multiple unicast DCIs can include legacy single-cell scheduling unicast DCI formats (such as formats 0_0, 0_1, 0_2) and the newer multi-cell scheduling unicast DCI format 0_3.

[0036] In some implementations, for DCI format 0_3 in the FDD case, when the UE processes the DCI format in the time slot of the scheduled cell, the DCI format can be counted for the cells in the cell set that are actually scheduled by the processed DCI format 0_3.

[0037] For TDD scenarios, based on the limitation of two unicast DCI processing sessions per time slot for scheduled cells, the following possibilities are allowed: If DCI format 0_3 is processed twice for a cell set and at least one given cell in that set is scheduled twice, it may not be expected that the UE will process any legacy DCI formats 0_0, 0_1, or 0_2 for that given cell. If DCI format 0_3 is processed twice for a cell set and a given cell in that set is scheduled only once, legacy DCI formats 0_0, 0_1, and 0_2 may be processed once for that given cell. If DCI format 0_3 is processed twice for a cell set and at least one given cell in that set is not even scheduled once, legacy DCI formats 0_0, 0_1, and 0_2 may be processed twice for that given cell. If DCI format 0_3 is processed once for a cell set and at least one given cell in that set is scheduled once, legacy DCI formats 0_0, 0_1, and 0_2 may be processed once for that given cell. If DCI format 0_3 is processed once for a cell set, and at least one cell in that set has not been scheduled even once, then old-style DCI formats 0_0, 0_1, and 0_2 can be processed twice for that given cell. If DCI format 0_3 is not processed for a cell set, then old-style DCI formats 0_0, 0_1, and 0_2 can be processed twice for each scheduled cell in that set.

[0038] In some implementations, where the UE is capable of and configured with both multi-cell scheduling and single-cell scheduling for DL, and is also configured with the same subcarrier spacing between scheduled cells and co-scheduled cells within the set, the following limitations may be applied to DL scheduling for FDD / TDD: The number of new DCI formats 1_3 that the UE must process for the cell set may be equal to one per time slot of the scheduled cells. The number of legacy unicast DCI formats 1_0, 1_1, and 1_2 that the UE must process for each cell within the cell set may be equal to one per time slot. The total number of new and legacy DCI formats that the UE must process for the cell set may not exceed the number of cells within the set.

[0039] For example, in some implementations, when there are four cells in the set, the total number of DCI formats that the UE can process within the time slot of the scheduled cells may not exceed four. For example, the UE can process DCI format 1_3 once, and the UE can process the old DCI formats 1_0, 1_1, and 1_2 once, but for a set with four cells, the total number of DCI formats that the UE can process may not exceed four. For example, a network node can transmit the new DCI format 1_3 and three unicast DCIs with old formats 1_0, 1_1, and / or 1_2.

[0040] In some implementations, a similar process can be used for DCI counting for UL. When the UE is capable of and configured with both multi-cell scheduling and single-cell scheduling for UL, and is also configured with the same subcarrier spacing between scheduled cells and co-scheduled cells within the set, the following limitations can be applied to UL scheduling for FDD: The number of new DCI formats 0_3 that the UE needs to process for the cell set can be equal to one per time slot of the scheduled cells. The number of legacy unicast DCI formats 0_0, 0_1, and 0_2 that the UE needs to process for each cell within the cell set can be equal to one per time slot of the scheduled cells. The total number of new and legacy DCI formats that the UE needs to process for the cell set can not exceed the number of cells within that set.

[0041] In addition, the following restrictions apply to UL scheduling for TDD: The number of new DCI formats 0_3 that the UE needs to process for a cell set can be equal to two per time slot of the scheduled cells. The number of legacy unicast DCI formats 0_0, 0_1, and 0_2 that the UE needs to process for each cell in the cell set can be equal to two per time slot of the scheduled cells. The total number of new and legacy DCI formats that the UE needs to process for a cell set can not exceed twice the number of cells in that set.

[0042] For example, in the case of four cells within the set, the UE may potentially process DCI format 0_3 twice for each cell within the time slot of the scheduling cell used for TDD. Additionally, the UE may potentially process legacy DCI formats 0_0, 0_1, and 0_2 twice for each cell. However, the total number of DCI formats that the UE can process may not exceed 8 (e.g., twice the number of cells in the set).

[0043] Figure 3 Cell set 302 is illustrated, where cell 1 is a scheduling cell and also part of cell set 302. In some implementations, where the UE is capable of and configured with both multi-cell scheduling and single-cell scheduling for DL ​​and / or UL, and where the same subcarrier spacing is configured between scheduling cells and co-scheduling cells within the set, and where the scheduling cell (e.g., cell 1) is included in cell set 302, the total number of unicast DCIs that can be processed for self-scheduling of scheduling cells within the set may differ from that of other cells within the set.

[0044] For example, in some implementations, where the UE processes DCI format 0_3 or 1_3 once (maximum allowed times) for the cell set, the legacy DCI format may be processed once for the scheduled cell (e.g., cell 1) but not for any other cell within cell set 106. For example, in the illustrated implementation, a higher budget may be provided for cell 1 than for cells 2 through 4. The higher budget allows the UE to process both DCI format 0_3 or 1_3 and the legacy DCI format for cell 1.

[0045] In some implementations, scaling can be used to determine the number of unicast DCIs that can be processed by the UE for scenarios involving different SCSs between scheduling cells and co-scheduling cells within a cell set. Scaling the number of DCIs for different SCS scenarios can be combined with any other implementations described herein, where the same SCS exists between scheduling cells and co-scheduling cells within the cell set. For example, the UE may have a scaled number of DCIs that it can process, rather than being limited to a single unicast DCI processing (e.g., refer to...). Figure 1 and Figure 2 The proposed implementation plan is as follows.

[0046] In one example, with a lower to higher SCS between the scheduling cell and the scheduled cell, the number of DCIs that can be processed can be scaled up by a factor of four for an SCS combination (15kHz, 60kHz), and the DCI counting process described with respect to other implementations can be applied directly. In another example, with a higher to lower SCS between the scheduling cell and the scheduled cell, the limitation on the number of unicast DCIs processed for an SCS combination (30kHz, 15kHz) can be scaled for N=2 time slots (i.e., the UE performs one unicast DCI process in two consecutive time slots).

[0047] Figure 4 A method 400 for operating a network node according to some implementations is illustrated. Method 400 includes scheduling 402 PDSCH for one or more cells within a cell set for scheduling cells during a time slot. Method 400 includes determining 404 a DCI count for a time slot used by a User Equipment (UE) device. Method 400 includes determining 406 the available processing capacity of unicast DCI formats for multi-cell scheduling and single-cell scheduling during a time slot based on the DCI count, wherein the available processing capacity is determined for the cell set and for each cell within the cell set. Based on the determination of the available processing capacity of the UE device, one or more unicast DCI formats are encoded 408 via a Physical Downlink Control Channel (PDCCH) for transmission during a time slot. Method 400 includes transmitting the PDCCH 410 to the UE device associated with one or more scheduled cells.

[0048] In some implementations, the unicast DCI format includes the single-cell scheduling legacy unicast DCI format 0_0 or 0_1 or 0_2 for Physical Downlink Shared Channel (PDSCH) scheduling and the unicast DCI format 1_0 or 1_1 or 1_2 for Physical Uplink Shared Channel (PUSCH) scheduling.

[0049] In some implementations, the multi-cell scheduling unicast DCI format is DCI format 1_3 for PDSCH scheduling and DCI format 0_3 for PUSCH scheduling.

[0050] In some implementations, where the same subcarrier spacing is used for both scheduled and unscheduled cells within the cell set, the available processing capacity of the user equipment for downlink scheduling for both FDD and TDD is equal to one unicast DCI per time slot of the scheduled cell. In some implementations, when determining available processing capacity, DCI format 1_3 is counted for both scheduled and unscheduled cells within the cell set when the user equipment processes DCI format 1_3.

[0051] In some implementations, when the same subcarrier spacing is used for both scheduled and unscheduled cells within the cell set, the available processing capacity of the user equipment is equal to one time slot per scheduled cell for uplink scheduling in Frequency Division Duplex (FDD) and two time slots per scheduled cell for uplink scheduling in Time Division Duplex (TDD). In some implementations, when determining available processing capacity, DCI format 0_3 is counted based on the available processing capacity of both scheduled and unscheduled cells within the cell set when the user equipment processes DCI format 0_3.

[0052] In some implementations, when the user equipment is processing DCI format 1_3, the available processing capacity of only scheduled cells, not unscheduled cells, within the cell set is used to count DCI format 1_3.

[0053] In some implementations, when the user equipment is processing DCI format 0_3, the DCI format 0_3 is counted based on the available processing capacity of only scheduled cells, not unscheduled cells, within the cell set.

[0054] In some implementations, the multi-cell scheduling unicast DCI format is DCI format 1_3, wherein the total number of DCI formats to be processed by the user equipment for the cell set does not exceed the number of cells in the cell set.

[0055] In some implementations, the multi-cell scheduling unicast DCI format is DCI format 0_3, and wherein the total number of DCI formats to be processed by the user equipment for the cell set does not exceed twice the number of cells in the cell set.

[0056] In some implementations, when the scheduling cell is included in the cell set, the total number of unicast DCIs that can be processed for self-scheduling of the scheduling cell within the cell set differs from that of other cells within the cell set.

[0057] In some implementations, the number of unicast DCIs that can be processed by the user equipment is scaled when different subcarrier spacings are used for the scheduled cells and the scheduled cells within the cell set.

[0058] The embodiments contemplated herein include an apparatus comprising components for performing one or more elements of method 400. This apparatus may be, for example, a base station (such as network device 718 (base station), as described herein).

[0059] The embodiments contemplated herein include one or more non-transitory computer-readable media comprising instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of method 400. The non-transitory computer-readable medium may be, for example, the memory of a base station (such as memory 722 of network device 718 (base station), as described herein).

[0060] The embodiments contemplated herein include an apparatus comprising logic components, modules, or circuitry for performing one or more elements of method 400. This apparatus may be, for example, a base station (such as network device 718 (base station), as described herein).

[0061] The embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of method 400. The apparatus may be, for example, an apparatus for a base station (such as network device 718 (base station), as described herein).

[0062] The implementation scheme envisioned herein includes a signal as described in or associated with one or more elements of method 400.

[0063] The embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution by a processing element causes the processing element to perform one or more elements of method 400. The processor may be a processor of a base station (such as processor 720 of network device 718 (base station), as described herein). These instructions may, for example, reside in the processor and / or in the memory of the base station (such as memory 722 of network device 718 (base station), as described herein).

[0064] Figure 5 Methods for operating a UE according to some implementation schemes are illustrated. Method 500 includes determining 502 a DCI count for a time slot. Method 500 includes determining 504 the available processing capacity of unicast DCI formats for multi-cell scheduling and single-cell scheduling during the time slot based on the DCI count, wherein the available processing capacity is determined for a set of cells and each cell within that set of cells. Method 500 includes preparing 506 to receive and process the unicast DCI format from a network node during the time slot via the physical downlink control channel (PDCCH) based on the determination of the available processing capacity.

[0065] In some implementations, the unicast DCI format includes the single-cell scheduling legacy unicast DCI format 0_0 or 0_1 or 0_2 for Physical Downlink Shared Channel (PDSCH) scheduling and the unicast DCI format 1_0 or 1_1 or 1_2 for Physical Uplink Shared Channel (PUSCH) scheduling.

[0066] In some implementations, the multi-cell scheduling unicast DCI format is DCI format 1_3 for PDSCH scheduling and DCI format 0_3 for PUSCH scheduling.

[0067] In some implementations, where the same subcarrier spacing is used for both scheduled and unscheduled cells within the cell set, the available processing capacity of the user equipment for downlink scheduling for both FDD and TDD is equal to one unicast DCI per time slot of the scheduled cell. In some implementations, when determining available processing capacity, DCI format 1_3 is counted for both scheduled and unscheduled cells within the cell set when the user equipment processes DCI format 1_3.

[0068] In some implementations, when the same subcarrier spacing is used for both scheduled and unscheduled cells within the cell set, the available processing capacity of the user equipment is equal to one time slot per scheduled cell for uplink scheduling in Frequency Division Duplex (FDD) and two time slots per scheduled cell for uplink scheduling in Time Division Duplex (TDD). In some implementations, when determining available processing capacity, DCI format 0_3 is counted based on the available processing capacity of both scheduled and unscheduled cells within the cell set when the user equipment processes DCI format 0_3.

[0069] In some implementations, when the user equipment is processing DCI format 1_3, the available processing capacity of the scheduled cells rather than the unscheduled cells within the cell set is used to count the DCI format 1_3.

[0070] In some implementations, when the user equipment is processing DCI format 0_3, the available processing capacity of the scheduled cells rather than the unscheduled cells within the cell set is used to count DCI format 0_3.

[0071] In some implementations, the multi-cell scheduling unicast DCI format is DCI format 1_3, wherein the total number of DCI formats to be processed by the user equipment for the cell set does not exceed the number of cells in the cell set.

[0072] In some implementations, the multi-cell scheduling unicast DCI format is DCI format 0_3, and wherein the total number of DCI formats to be processed by the user equipment for the cell set does not exceed twice the number of cells in the cell set.

[0073] In some implementations, when the scheduling cell is included in the cell set, the total number of unicast DCIs that can be processed for self-scheduling of the scheduling cell within the cell set differs from that of other cells within the cell set.

[0074] In some implementations, the number of unicast DCIs that can be processed by the user equipment is scaled when different subcarrier spacings are used for the scheduled cells and the scheduled cells within the cell set.

[0075] The embodiments contemplated herein include an apparatus comprising components for performing one or more elements of method 500. This apparatus may be, for example, a UE (such as wireless device 702 (UE), as described herein).

[0076] The embodiments contemplated herein include one or more non-transitory computer-readable media comprising instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of method 500. The non-transitory computer-readable medium may be, for example, the memory of a UE (such as memory 706 of a wireless device 702 (UE), as described herein).

[0077] The embodiments contemplated herein include an apparatus comprising logic components, modules, or circuitry for performing one or more elements of method 500. This apparatus may be, for example, a UE (such as wireless device 702 (UE), as described herein).

[0078] The embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of method 500. The apparatus may be, for example, a UE (such as wireless device 702 (UE), as described herein).

[0079] The implementation scheme envisioned herein includes a signal as described in or associated with one or more elements of method 500.

[0080] The embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution of the program by a processor will cause the processor to perform one or more elements of method 500. The processor may be a processor of the UE (such as processor 704 of wireless device 702 (UE), as described herein). These instructions may, for example, reside in the processor and / or in the memory of the UE (such as memory 706 of wireless device 702 (UE), as described herein).

[0081] Figure 6 An example architecture of a wireless communication system 600 according to an embodiment disclosed herein is illustrated. The following description is provided for an example wireless communication system 600 operating in conjunction with LTE system standards and / or 5G or NR system standards provided by 3GPP technical specifications.

[0082] like Figure 6As shown, the wireless communication system 600 includes UE 602 and UE 604 (but any number of UEs may be used). In this example, UE 602 and UE 604 are exemplified as smartphones (e.g., handheld touchscreen mobile computing devices capable of connecting to one or more cellular networks), but may also include any mobile or non-mobile computing device configured for wireless communication.

[0083] UE 602 and UE 604 can be configured to be communicatively coupled to RAN 606. In embodiments, RAN 606 can be NG-RAN, E-UTRAN, etc. UE 602 and UE 604 utilize connections (or channels) with RAN 606 (shown as connection 608 and connection 610, respectively), where each connection includes a physical communication interface. RAN 606 may include one or more base stations (such as base station 612 and base station 614) implementing connection 608 and connection 610.

[0084] In this example, Connection 608 and Connection 610 are air interfaces that implement this type of communication coupling and can conform to the RAT used by RAN606, such as LTE and / or NR, for example.

[0085] In some implementations, UE 602 and UE 604 may also exchange communication data directly via sidelink interface 616. UE 604 is shown configured to access an access point (shown as AP 618) via connection 620. By way of example, connection 620 may include a local wireless connection, such as a connection conforming to any IEEE 802.11 protocol, wherein AP 618 may include Wi-Fi. ® Router. In this example, AP 618 may connect to another network (e.g., the Internet) without using CN 624.

[0086] In the implementation, UE 602 and UE 604 may be configured to communicate with each other or with base station 612 and / or base station 614 on a multi-carrier communication channel using orthogonal frequency division multiplexing (OFDM) communication signals according to various communication technologies, such as, but not limited to, orthogonal frequency division multiple access (OFDMA) communication technology (e.g., for downlink communication) or single-carrier frequency division multiple access (SC-FDMA) communication technology (e.g., for uplink and ProSe or sidelink communication), but the scope of the implementation is not limited in this respect. The OFDM signal may include multiple orthogonal subcarriers.

[0087] In some implementations, all or some of the base stations in base station 612 or base station 614 may be implemented as one or more software entities running on a server computer as part of a virtual network. Furthermore, or in other implementations, base station 612 or base station 614 may be configured to communicate with each other via interface 622. In implementations where the wireless communication system 600 is an LTE system (e.g., when CN 624 is an EPC), interface 622 may be an X2 interface. The X2 interface may be defined between two or more base stations (e.g., two or more eNBs, etc.) connected to the EPC and / or between two eNBs connected to the EPC. In implementations where the wireless communication system 600 is an NR system (e.g., when CN 624 is a 5GC), interface 622 may be an Xn interface. The Xn interface is defined between two or more base stations (e.g., two or more gNBs, etc.) connected to the 5GC, between a base station 612 (e.g., a gNB) connected to the 5GC and an eNB, and / or between two eNBs connected to the 5GC (e.g., CN 624).

[0088] RAN 606 is shown communicatively coupled to CN 624. CN 624 may include one or more network elements 626 configured to provide various data and telecommunications services to customers / subscribers (e.g., users of UE 602 and UE 604) connected to CN 624 via RAN 606. Components of CN 624 may be implemented in a single physical device or a separate physical device, including components for reading and executing instructions from machine-readable or computer-readable media (e.g., non-transitory machine-readable storage media).

[0089] In this implementation, CN 624 may be an EPC, and RAN 606 may be connected to CN 624 via S1 interface 628. In this implementation, S1 interface 628 may be divided into two parts: an S1 user plane (S1-U) interface, which carries service data between base station 612 or 614 and the serving gateway (S-GW); and an S1-MME interface, which is the signaling interface between base station 612 or 614 and the mobility management entity (MME).

[0090] In this implementation, CN 624 may be a 5GC, and RAN 606 may be connected to CN 624 via NG interface 628. In this implementation, NG interface 628 may be divided into two parts: an NG user plane (NG-U) interface, which carries service data between base station 612 or 614 and the User Plane Function (UPF); and an S1 control plane (NG-C) interface, which is the signaling interface between base station 612 or 614 and the Access and Mobility Management Function (AMF).

[0091] Generally, application server 630 can be a component that provides Internet Protocol (IP) carried resources (e.g., packet-switched data services) for use with CN 624. Application server 630 can also be configured to support one or more communication services (e.g., VoIP sessions, group communication sessions, etc.) for UE 602 and UE 604 via CN 624. Application server 630 can communicate with CN 624 via IP communication interface 632.

[0092] Figure 7 A system 700 for performing signaling 734 between a wireless device 702 and a network device 718 according to an embodiment disclosed herein is illustrated. System 700 may be part of a wireless communication system as described herein. Wireless device 702 may be, for example, a UE (User Equipment) in a wireless communication system. Network device 718 may be, for example, a base station (e.g., an eNB or gNB) in a wireless communication system.

[0093] Wireless device 702 may include one or more processors 704. Processor 704 is executable instructions that enable various operations of wireless device 702 to be performed as described herein. Processor 704 may include one or more baseband processors, which are implemented using, for example, a central processing unit (CPU), digital signal processor (DSP), application-specific integrated circuit (ASIC), controller, field-programmable gate array (FPGA) device, another hardware device, firmware device, or any combination thereof configured to perform the operations described herein.

[0094] Wireless device 702 may include memory 706. Memory 706 may be a non-transitory computer-readable storage medium that stores instructions 708, which may include instructions executable, for example, by processor 704. Instructions 708 may also be referred to as program code or a computer program. Memory 706 may also store data used by processor 704 and results calculated by the processor.

[0095] Wireless device 702 may include one or more transceivers 710, which may include radio frequency (RF) transmitter circuitry and / or receiver circuitry, which use antenna 712 of wireless device 702 to facilitate signaling (e.g., signaling 734) to and / or from wireless device 702 and other devices (e.g., network device 718) in accordance with the corresponding RAT.

[0096] Wireless device 702 may include one or more (e.g., one, two, four or more) antennas 712. In embodiments with multiple antennas 712, wireless device 702 can fully utilize the spatial diversity of such multiple antennas 712 to transmit and / or receive multiple different data streams on the same time-frequency resource. This behavior may be referred to as, for example, multiple-input multiple-output (MIMO) behavior (referring to multiple antennas used at each of the transmitting and receiving devices to implement this aspect). MIMO transmission by wireless device 702 can be achieved according to pre-decoding (or digital beamforming) applied at wireless device 702, which multiplexes data streams across antennas 712 based on known or assumed channel characteristics, such that each data stream is received with appropriate signal strength relative to the others at a desired location in the spatial domain (e.g., the location of the receiver associated with that data stream). Some implementations may use a single-user MIMO (SU-MIMO) approach (where all data streams are directed to a single receiver) and / or a multi-user MIMO (MU-MIMO) approach (where individual data streams may be directed to individual (different) receivers at different locations in the airspace).

[0097] In some implementations with multiple antennas, wireless device 702 can implement analog beamforming technology, whereby the phase of the signal transmitted by antenna 712 is relatively adjusted so that the (joint) transmission of antenna 712 can be directed (this is sometimes referred to as beam control).

[0098] Wireless device 702 may include one or more interfaces 714. Interfaces 714 can be used to provide input to or output to wireless device 702. For example, wireless device 702 (UE) may include interfaces 714 such as microphones, speakers, touchscreens, and buttons to allow users of the UE to make inputs and / or outputs to the UE. Other interfaces of such UEs may consist of transmitters, receivers, and other circuitry that allow the UE to communicate with other devices (e.g., in addition to the transceiver 710 / antenna 712 described), and may be based on known protocols (e.g., Wi-Fi). ® and Bluetooth ® (etc.) to perform the operation.

[0099] Wireless device 702 may include DCI module 716. DCI module 716 may be implemented via hardware, software, or a combination thereof. For example, DCI module 716 may be implemented as a processor, circuitry, and / or instructions 708 stored in memory 706 and executed by processor 704. In some examples, DCI module 716 may be integrated within processor 704 and / or transceiver 710. For example, DCI module 716 may be implemented via a combination of software components (e.g., software components executed by a DSP or general-purpose processor) and hardware components (e.g., logic gates and circuitry) within processor 704 or transceiver 710.

[0100] The DCI module 716 can be used in various aspects of this disclosure, for example, Figures 1 to 6 The DCI module 716 is configured to receive, process, and count DCI signals in various aspects.

[0101] Network device 718 may include one or more processors 720. Processor 720 is executable instructions to perform various operations of network device 718 as described herein. Processor 720 may include one or more baseband processors, which are implemented using, for example, a CPU, DSP, ASIC, controller, FPGA device, another hardware device, firmware device, or any combination thereof configured to perform the operations described herein.

[0102] Network device 718 may include memory 722. Memory 722 may be a non-transitory computer-readable storage medium that stores instructions 724, which may include, for example, instructions executed by processor 720. Instructions 724 may also be referred to as program code or a computer program. Memory 722 may also store data used by processor 720 and results calculated by the processor.

[0103] Network device 718 may include one or more transceivers 726, which may include RF transmitter circuitry and / or receiver circuitry that uses antenna 728 of network device 718 to facilitate signaling (e.g., signaling 734) to and / or from network device 718 and other devices (e.g., wireless device 702) in accordance with the corresponding RAT.

[0104] Network device 718 may include one or more (e.g., one, two, four or more) antennas 728. In embodiments having multiple antennas 728, network device 718 may perform MIMO, digital beamforming, analog beamforming, beam control, etc., as described.

[0105] Network device 718 may include one or more interfaces 730. Interfaces 730 may be used to provide input to or output to network device 718. For example, network device 718 (base station) may include interfaces 730 consisting of transmitters, receivers, and other circuitry (e.g., in addition to the transceiver 726 / antenna 728 described), which enable the base station to communicate with other equipment in the core network and / or enable the base station to communicate with external networks, computers, databases, etc., for the purpose of performing operations, management, and maintenance of the base station or other equipment operatively connected to the base station.

[0106] Network device 718 may include DCI module 732. DCI module 732 may be implemented via hardware, software, or a combination thereof. For example, DCI module 732 may be implemented as a processor, circuitry, and / or instructions 724 stored in memory 722 and executed by processor 720. In some examples, DCI module 732 may be integrated within processor 720 and / or transceiver 726. For example, DCI module 732 may be implemented via a combination of software components (e.g., software components executed by a DSP or general-purpose processor) and hardware components (e.g., logic gates and circuitry) within processor 720 or transceiver 726.

[0107] The DCI module 732 can be used in various aspects of this disclosure, for example, Figures 1 to 6 All aspects. The DCI module 732 is configured to determine the limitations on unicast DCI processing with multi-cell scheduling and single-cell scheduling, and to transmit DCI according to those limitations.

[0108] For one or more embodiments, at least one of the components illustrated in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, and / or methods as described herein. For example, a baseband processor as described herein in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples illustrated herein. Similarly, circuitry associated with a UE, base station, network element, etc., as described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples illustrated herein.

[0109] Unless otherwise expressly stated, any of the embodiments described above may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific embodiments provides illustrative and descriptive information, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. In light of the teachings above, modifications and variations are possible, or modifications and variations may be derived from practice with various embodiments.

[0110] Implementations and specific embodiments of the systems and methods described herein may include various operations embodied in machine-executable instructions to be executed by a computer system. The computer system may include one or more general-purpose or special-purpose computers (or other electronic devices). The computer system may include hardware components, including specific logical parts for performing the operations; or may include a combination of hardware, software, and / or firmware.

[0111] It should be recognized that the systems described herein include descriptions of specific implementations. These implementations may be combined into a single system, partially integrated into other systems, split into multiple systems, or otherwise divided or combined. Furthermore, it is contemplated that parameters, attributes, aspects, etc., of one implementation may be used in one implementation. For clarity, these parameters, attributes, aspects, etc., are described only in one or more implementations, and it should be recognized that, unless expressly stated herein, these parameters, attributes, aspects, etc., may be combined with or substituted for parameters, attributes, aspects, etc., of another implementation.

[0112] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0113] Although the foregoing has been described in considerable detail for clarity, it will be apparent that certain changes and modifications can be made without departing from the principles of the invention. It should be noted that there are many alternative ways to implement both the processes and apparatus described herein. Therefore, this embodiment should be considered illustrative rather than restrictive, and this description is not limited to the details given herein, but can be modified within the scope of the appended claims and their equivalents.

Claims

1. A method for operating user equipment (UE), the method comprising: Determine the downlink control information (DCI) count for the time slot; The available processing capacity of the unicast DCI format for multi-cell scheduling and single-cell scheduling during the time slot is determined based on the DCI count, wherein the available processing capacity is determined for the cell set and each cell within the cell set. as well as Based on the determination of the available processing capabilities, preparations are made to receive and process the unicast DCI format from the network node during the time slot via the Physical Downlink Control Channel (PDCCH).

2. The method according to claim 1, wherein the unicast DCI format includes a single-cell scheduling legacy unicast DCI format 0_0 or 0_1 or 0_2 for Physical Downlink Shared Channel (PDSCH) scheduling and a unicast DCI format 1_0 or 1_1 or 1_2 for Physical Uplink Shared Channel (PUSCH) scheduling.

3. The method according to claim 1, wherein the multi-cell scheduling unicast DCI format is DCI format 1_3 for Physical Downlink Shared Channel (PDSCH) scheduling or DCI format 0_3 for Physical Uplink Shared Channel (PUSCH) scheduling.

4. The method according to claim 1, wherein the multi-cell scheduling unicast DCI format is DCI format 1-3; Where the same subcarrier spacing is used for both the scheduled cell and the scheduled cell within the cell set, the available processing capacity of the UE for downlink scheduling for both Frequency Division Duplex (FDD) and Time Division Duplex (TDD) is equal to one unicast DCI per time slot of the scheduled cell; and When the available processing capacity is determined, if the UE processes the DCI format 1_3, the available processing capacity of both the scheduled cells and the unscheduled cells in the cell set is used to count the DCI format 1_3.

5. The method according to claim 1, wherein the multi-cell scheduling unicast DCI format is DCI format 0_3; Where the same subcarrier spacing is used for both the scheduled cell and the scheduled cell within the cell set, the available processing capacity of the UE is equal to one time slot per time slot of the scheduled cell for uplink scheduling under Frequency Division Duplex (FDD), and equal to two time slots per time slot of the scheduled cell for uplink scheduling under Time Division Duplex (TDD); and When the available processing capacity is determined, when the UE processes the DCI format 0_3, the available processing capacity of both the scheduled cells and unscheduled cells in the cell set is used to count the DCI format 0_3.

6. The method according to claim 1, wherein the multi-cell scheduling unicast DCI format is DCI format 1-3; Where the same subcarrier spacing is used for both the scheduled cell and the scheduled cell within the cell set, the available processing capacity of the UE for downlink scheduling for both Frequency Division Duplex (FDD) and Time Division Duplex (TDD) is equal to one unicast DCI per time slot of the scheduled cell; and When the available processing is determined, if the UE processes the DCI format 1_3, the available processing capabilities of the scheduled cells (but not the unscheduled cells) within the cell set are used to count the DCI format 1_3.

7. The method according to claim 1, wherein the multi-cell scheduling unicast DCI format is DCI format 0_3; Where the same subcarrier spacing is used for both the scheduled cell and the scheduled cell within the cell set, the available processing capacity of the UE is equal to one time slot per time slot of the scheduled cell for uplink scheduling under Frequency Division Duplex (FDD), and equal to two time slots per time slot of the scheduled cell for uplink scheduling under Time Division Duplex (TDD); and When the available processing is determined, if the UE processes the DCI format 0_3, the available processing capabilities of the scheduled cells (but not the unscheduled cells) within the cell set are used to count the DCI format 0_3.

8. The method of claim 1, wherein the multi-cell scheduling unicast DCI format is DCI format 1-3, and wherein the total number of DCI formats to be processed by the UE for the cell set does not exceed the number of cells in the cell set.

9. The method of claim 1, wherein the multi-cell scheduling unicast DCI format is DCI format 0-3, and wherein the total number of DCI formats to be processed by the UE for the cell set does not exceed twice the number of cells in the cell set.

10. The method of claim 1, wherein, when a scheduling cell is included in the cell set, the total number of unicast DCIs that can be processed for self-scheduling of the scheduling cell within the cell set is different from that of other cells within the cell set.

11. The method of claim 1, wherein when different subcarrier intervals are used for the scheduled cells and the scheduled cells within the cell set, the number of unicast DCIs that can be processed by the UE is scaled.

12. A method for operating a network node, the method comprising: During a time slot, a Physical Downlink Shared Channel (PDSCH) is scheduled for one or more cells within the set of cells to be scheduled. Determine the downlink control information (DCI) count for the time slot used by the user equipment equipment; The available processing capacity of the unicast DCI format for multi-cell scheduling and single-cell scheduling during the time slot is determined based on the DCI count, wherein the available processing capacity is determined for the cell set and each cell within the cell set. as well as Based on the determination of the available processing capabilities of the user equipment, one or more unicast DCI formats are encoded via the Physical Downlink Control Channel (PDCCH) for transmission during the time slot.

13. The method of claim 12, wherein the additional unicast DCI format includes a single-cell scheduling legacy unicast DCI format 0_0 or 0_1 or 0_2 for Physical Downlink Shared Channel (PDSCH) scheduling and a unicast DCI format 1_0 or 1_1 or 1_2 for Physical Uplink Shared Channel (PUSCH) scheduling.

14. The method according to claim 12, wherein the multi-cell scheduling unicast DCI format is DCI format 1_3 for Physical Downlink Shared Channel (PDSCH) scheduling or DCI format 0_3 for Physical Uplink Shared Channel (PUSCH) scheduling.

15. The method according to claim 12, wherein the multi-cell scheduling unicast DCI format is DCI format 1-3; Where the same subcarrier spacing is used for both the scheduled cell and the scheduled cell within the cell set, the available processing capacity of the user equipment for downlink scheduling for both Frequency Division Duplex (FDD) and Time Division Duplex (TDD) is equal to one unicast DCI per time slot of the scheduled cell; and When the available processing capacity is determined, if the user equipment is processing the DCI format 1_3, the available processing capacity of both the scheduled cells and the unscheduled cells in the cell set is used to count the DCI format 1_3.

16. The method according to claim 12, wherein the multi-cell scheduling unicast DCI format is DCI format 0_3; Where the same subcarrier spacing is used for both the scheduled cell and the scheduled cell within the cell set, the available processing capacity of the user equipment is equal to one time slot per time slot of the scheduled cell for uplink scheduling under frequency division duplex (FDD), and equal to two time slots per time slot of the scheduled cell for uplink scheduling under time division duplex (TDD); and When the available processing capacity is determined, if the user equipment is processing the DCI format 0_3, the available processing capacity of both the scheduled cells and the unscheduled cells in the cell set is used to count the DCI format 0_3.

17. The method according to claim 12, wherein the multi-cell scheduling unicast DCI format is DCI format 1-3; Where the same subcarrier spacing is used for both the scheduled cell and the scheduled cell within the cell set, the available processing capacity of the user equipment for downlink scheduling for both Frequency Division Duplex (FDD) and Time Division Duplex (TDD) is equal to one unicast DCI per time slot of the scheduled cell; and When the available processing capacity is determined, if the user equipment is processing the DCI format 1_3, the available processing capacity of the scheduled cells (but not the unscheduled cells) within the cell set is used to count the DCI format 1_3.

18. The method according to claim 12, wherein the multi-cell scheduling unicast DCI format is DCI format 0_3; Where the same subcarrier spacing is used for both the scheduled cell and the scheduled cell within the cell set, the available processing capacity of the user equipment is equal to one time slot per time slot of the scheduled cell for uplink scheduling under frequency division duplex (FDD), and equal to two time slots per time slot of the scheduled cell for uplink scheduling under time division duplex (TDD); and When the available processing is determined, if the user equipment is processing the DCI format 0_3, the available processing capacity of the scheduled cells (but not the unscheduled cells) within the cell set is used to count the DCI format 0_3.

19. The method of claim 12, wherein the multi-cell scheduling unicast DCI format is DCI format 1-3, and wherein the total number of DCI formats to be processed by the user equipment for the cell set does not exceed the number of cells in the cell set.

20. The method of claim 12, wherein the multi-cell scheduling unicast DCI format is DCI format 0-3, and wherein the total number of DCI formats to be processed by the user equipment for the cell set does not exceed twice the number of cells in the cell set.

21. The method of claim 12, wherein, when the scheduling cell is included in the cell set, the total number of unicast DCIs that can be processed for self-scheduling of the scheduling cell within the cell set is different from that of other cells within the cell set.

22. The method of claim 12, wherein when different subcarrier intervals are used for the scheduled cells and scheduled cells within the cell set, the number of unicast DCIs that can be processed by the user equipment equipment is scaled.

23. An apparatus comprising components for performing the method according to any one of claims 1 to 22.

24. A computer-readable medium comprising instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform the method according to any one of claims 1 to 22.

25. An apparatus comprising a logic component, module, or circuitry for performing the method according to any one of claims 1 to 22.

Images