3GPP TSG-RAN WG1 Meeting #121						R1-2503272
St Julian’s, Malta, May 19 – 23, 2025

Agenda Item:	9.15.11
Source:	Huawei, HiSilicon
Title:	UE features for Rel-19 MCE
Document for:	Discussion and Decision

Conclusions
In this contribution, we provide some views on the UE feature for Rel-19 MCE. The following proposals are given:
Proposal 1: Remove the bracket in component 1 of FG66-3 and FG66-4.

Proposal 2: Introduce a candidate value set for component 1 to FG66-3 and FG66-4 to indicate whether a UE 1) only supports different SCS and/or carrier types for co-scheduled cells, 2) only supports multiple PUSCHs/PDSCHs transmissions on each of the co-scheduled cells with same SCS, or 3) both.

Proposal 3: Include the component 2 in FG66-3 to indicate the support of HARQ-ACK enhancement with the following update on details:
Time domain HARQ-ACK bundling for type-2 HARQ-ACK codebook for supporting multi-PDSCH scheduling with DCI format 1_3.

Proposal 4: Introduce a component and candidate values to indicate the maximum number of different SCSs across co-scheduled cells within a cell set. The candidate values can be {2, 3}.

Proposal 5: Introduce a new component and candidate values to indicate the supported combinations of different SCSs and carrier types for co-scheduled cells within a cell set. 

Proposal 6: Introduce a new component to report the maximum number of total schedulable PDSCH among co-scheduled cells by a DCI format 1_3. The candidate values are {4, 8, 16, 32}.
No need to define a component to report the supported number of maximum schedulable PDSCHs per cell.

Proposal 7: Set the reporting type of FG66-3 and FG66-4 as per band combination.

Proposal 8: FG66-3 should prerequisite FG49-1/1b and FG66-4 should prerequisite FG49-2/2b.

Proposal 9: Introduce a new component to indicate the number of unicast DCIs to be processed for co-scheduled cells within a cell set.

Proposal 10: Update the UE feature list for R19 MCE as in Appendix. 

3GPP TSG RAN WG1 #121			R1-2503334
St Julian’s, Malta, May 19th – 23rd, 2025

Source:	ZTE Corporation, Sanechips
Title:	Discussion on UE features for Rel-19 MCE
Agenda item:	9.15.11
Document for:	Discussion and Decision

Conclusion
To sum up, we have the following proposal for the UE feature on Rel-19 MCE.
Proposal 1: The brackets in the component 1 of FG 66-3 and FG 66-4 should be removed.
Proposal 2: HARQ enhancement should be the component of FG 66-3.
Proposal 3: FG 66-3/66-4 should be able to be supported for all the FR and/or SCS.
Proposal 4: There should be no need to separate the FG 66-3/66-4 per FR and/or SCS and FG 66-3/66-4 should be reported per BC.
Proposal 5: The UE should report one or more combinations of {the maximum number of the PDSCHs/PUSCHs per cell, the maximum number of cells in one set}.
Proposal 6: The following FGs should be introduced for multi-cell scheduling with different carrier types/SCS.

3GPP TSG RAN WG1 #121		                                                      R1-2503395
St Julian’s, Malta, May 19th – 23th, 2025

Source: 	vivo
Title:	Discussion on UE features for MCE for NR Phase 3
Agenda Item:	9.15.11
Document for:	Discussion and Decision 

Conclusion
In this contribution, the following proposals are summarized as follows: 
Proposal 1: In FG 66-3 and FG 66-4, delete the square bracket for [one or more], and delete “or more”.
add FG 66-3a and 66-4a to introduce a UE capability supporting DCI format 1_3/0-3 for DL/UL scheduling of one or more PDSCH(s)/ PUSCH(s) per cell in the set of cells with same SCS and carrier type.
Proposal 2: FG 66-3 and FG 66-4 both include the following components,
The SCSes ranges from 15kHz to 120kHz.
The different SCSes in a carrier type among the scheduled cells including: FR1 licensed FDD/ FR1 licensed TDD/ FR1 unlicensed TDD/ FR2-1.
The different carrier types among the scheduled cells including: FR1 licensed FDD/ FR1 licensed TDD/ FR1 unlicensed TDD/ FR2-1.
Proposal 3: FG 66-3 and FG 66-4 both include the following components,
the number of unicast DCI(s) to be monitored is defined per N consecutive slots, where the N is based on the lowest SCS among the cells. The value of N is FFS.
Proposal 4: FG 66-3a includes the following components,
Multi-cell multi-PDSCH scheduling by DCI format 1_3 is applicable to 120kHz SCS for FR2-1 cells.
Multi-cell multi-PDSCH scheduling by DCI format 1_3 is applicable to FR2-2 cells.
supported type 2 HARQ enhancement, the HARQ -ACK feedback for SCell dormancy and the maximum number of HARQ-ACK bits is specified in TS38213.
Proposal 5: FG 66-4a includes the following components,
Multi-cell multi-PUSCH scheduling by DCI format 0_3 is applicable to FR1 cells.
Multi-cell multi-PUSCH scheduling by DCI format 0_3 is applicable to 120kHz SCS for FR2-1 cells.
Multi-cell multi-PUSCH scheduling by DCI format 0_3 is applicable to FR2-2 cells.
Proposal 6: The prerequisite feature groups for FG 66-3 and 66-3a can be either FG 49-1 or FG 49-1b, and the prerequisite feature groups for FG 66-4 and 66-4a can be either FG 49-2 or FG 49-2b.
Proposal 7: Adopt the following UE feature for MCE for NR phase 3:




NR_MC_enh2

Table 1 UE feature for MCE for NR phase 3

3GPP TSG RAN WG1 #121	R1-2503408
St Julian, Malta, 19 – 23 May 2025


Agenda item:		9.15.11
Source:	Nokia
Title:	NR Multi-carrier Enhancements Phase 3 UE features
Document for:		Discussion and Decision

Summary of discussion and UE feature list proposal 
The discussions in Sec. 2 and 3 can be summaried in the following related observations and proposals: 
Proposal 1: The multi-cell scheduling using DCI format 0_3/1_3 with different SCS and different carrier type is limited cells of licensed band FDD with 15kHz, licensed band TDD with 30kHz and FR2-1 with 120kHz. 
Observation 1: We don’t see a need to limit the number of cells within a set of cells for 66-1 and 66-2.
Observation 2: A single FG (66-1) for the support of multi-cell PDSCH scheduling using DCI format 1_3 with different SCS and different carrier type and a single FG (66-2) for the support of multi-cell PUSCH scheduling using DCI format 0_3 with different SCS and different carrier type are sufficient to allow for the intended required signaling support. 
Proposal 2: The scheduling of more than one PDSCH scheduling on cell of FG 63-3 is to be limited to 120kHz SCS and FR1. 
Observation 3: FG 66-3 components on maximum number of scheduable PDSCHs per cell or per DCI (i.e. within a set of cells) are not seen as needed.   
Proposal 3: The scheduling of more than one PUSCH scheduling on cell of FG 63-4 is to be limited to contiguous allocation for FR1 and FR 2-1, non-contiguous allocation in FR1 and non-contiguous allocation for 120kHz in FR2-1. 
Observation 4: FG 66-4 components on maximum number of scheduable PUSCHs per cell or per DCI (i.e. within a set of cells) are not seen as needed.   

Below we present our detailed proposal on the UE feature list. 


Proposed introduction of FG 66-1 & 66-2 for DCI format 1_3 & 0_3 scheduling of different SCS and same or different carrier types of co-scheduled cells	



Proposed changes to FG 66-3 & 66-4 	

3GPP TSG RAN WG1 #121			R1-2503535
St Julian’s, Malta, May 19th – 23th, 2025
Agenda item:	9.15.11
Source: 	Spreadtrum, UNISOC
Title: 	Discussion on UE features for multi-carrier enhancement
Document for:	Discussion and decision

Summary#3 of discussion on Rel-19 NR UE features for MCE for NR Phase 3

3GPP TSG RAN WG1 #121	R1-2503601
Malta, MT, May 19th – 23rd, 2025
Agenda item:	9.15.11
Source:	Samsung
Title:	UE features for multi-carrier enhancements
Document for:	Discussion and decision

Conclusions
This contribution considered UE features for Rel-19 multi-cell scheduling enhancements and made the following proposals.
Proposal 1: For MC-DCI with different SCS or different carrier types:
Specify UE features 66-1b / 66-2b (different SCS and different carrier type) corresponding to Cases 1/2/3 from the RAN1#118bis agreement – i.e., the direction of Alt-1 in the Moderator Proposal 1 in RAN1#120bis [3];
Proceed to support the direction of FGs 66-1 / 66-2 (same SCS and different carrier type) to complete the support for Cases 1/2/3 from RAN1#118bis;
Deprioritize UE features 66-1a / 66-2a corresponding to Cases 4, 5, and 6 (mixed SCS for a same carrier type) – Alt-2 need not be pursued.

Proposal 2: For components 1 and 2 of the proposed Rel-19 MCE FGs 66-1b / 66-2b:
Support two sets of (carrier types, SCS) for the cells in the cell set;
Update the defined carrier types, as in Rel-18, to ‘FR1 licensed FDD’ and ‘FR1 licensed TDD’ and ‘FR2-1’;
Consider a possible support of (FR2-1, 60kHz) only with non-FR2-1 carriers;
Consider a possible support of (FR1 unlicensed TDD, 30kHz) as part of a set of co-scheduled cells (together with licensed carriers);
Note: Reuse component 4 of Rel-18 FGs 49-1 / 1b / 2 / 2b to define the number of cells in a cell set, without further restriction.
Proposal 3: Adopt the following for the new FG 49-X for DL MC-DCI 1_3 with different SCS and/or carrier types:
No mention of scheduling cell inside or outside the cell set;
Components 3 can be defined as combination and extension of components 1 from FG 49-1 / 49-1b, and component 2 of FG 49-1, as follows:
3) The scheduling cell is included or not included in the set of cells, and is in a same PUCCH group as the set of cells.
   Scheduling cell is PCell if set of cells includes PCell, and scheduling cell is PCell or an SCell if set of cells includes only SCells.
Components 4 – 9, and 11 directly follow from FG 49-1 without any change;
Components 10 is updated based on FG 49-1 as follows:
10a) The number of unicast DL DCIs to process per slot of scheduling cell for a set of cells configured for multi-cell PDSCH scheduling by DCI format 1_3:
One DCI format 1_3 for the set of cells and,
One unicast DL DCI formats 1_0/1_1/1_2 (if supported) for each of the cells that are not scheduled by DCI 1_3
Applies for same SCS.
Applies for low-to-high SCS (i.e., scheduling cell has lower SCS than at least some cells from the set of cells, and same SCS as remaining cells in the set of cells, if any).

10b) The number of unicast DL DCIs to process per max {N1, N2} consecutive slots of scheduling cell for a set of cells configured for multi-cell PDSCH scheduling by DCI format 1_3:
One DCI format 1_3 for the set of cells and,
 unicast DL DCI formats 1_0/1_1/1_2 (if supported) for each of the cells with SCS1 that are scheduled by DCI 1_3
 unicast DL DCI formats 1_0/1_1/1_2 (if supported) for each of the cells with SCS2 that are scheduled by DCI 1_3
 unicast DL DCI formats 1_0/1_1/1_2 (if supported) for each of the cells with SCS1 that are not scheduled by DCI 1_3
 unicast DL DCI formats 1_0/1_1/1_2 (if supported) for each of the cells with SCS2 that are not scheduled by DCI 1_3

Applies for high-to-low SCS (i.e., scheduling cell has higher SCS than at least some cells from the set of cells, and same SCS as remaining cells in the set of cells, if any), N1 and N2 are the ratio of pair of (scheduling CC SCS, respective scheduled CC SCS), e.g., N= 1 for (30, 30) and N=2 for (30,15)

FFS the number of unicast DL DCIs when scheduling CC SCS is strictly in between scheduled CC SCS, if supported
For example, for the combination of (FR1 TDD, 30kHz) as the scheduling cell for a set of cells consisting of {(FR1 FDD, 15kHz), (FR2-1, 120kHz)}, if supported
Proposal 4: For FGs 66-3 / 66-4 for Rel-19 multi-cell multi-PxSCH scheduling:
Include corresponding FG from FGs 49-1 / 1b / 2 / 2b as pre-requisite;
Component 1 can be updated to “scheduling of [one or] more than one PDSCH(s) per for at least one cell”;
Component 2 for HARQ-ACK support in FG 66-3 can follow from FG 24-1d/1f;
FGs can be separated for FR2-1 and FR2-2 and only apply to the 120 kHz SCS;
No need to define “component to report the supported number of maximum schedulable PDSCHs/PUSCHs per cell” or “the supported maximum total number of schedulable PDSCHs/PUSCHs per DCI”, aligned with Rel-17 FGs 24-1d / 1e / 1f / 1g.

References:
RP-242408, New WID: Multi-carrier enhancements for NR Phase 2, RAN#105, Lenovo.
TS 38.822, v18.0.0.
R1-2503138, Summary#3 of discussion on Rel-19 NR UE features for MCE for NR Phase 3, Moderator (NTT DOCOMO, INC.)
R1-2502970, Session Notes of AI 9.15.11, Ad-Hoc Chair (NTT DOCOMO, INC.)
R1-2409166, Feature lead summary #5 on multi-cell scheduling with a single DCI, RAN1#118bis, Moderator (Lenovo).

3GPP TSG-RAN WG1 Meeting #121	R1-2503608
St Julian’s, Malta, May 19th – May 23rd, 2025
Agenda Item:	9.15.11
Source:	Ericsson
Title:	UE features for MCE for NR Phase 3
Document for:	Discussion, Decision
1	

Conclusion
In the previous sections we made the following observations: 
Observation 1	With the assumption that only one SCS is applied to each carrier type, it is possible to implicitly determine whether the scheduling cell is included in the co-scheduled cell set or not based on the reported values from Component 2).

Based on the discussion in the previous sections we propose the following:
Proposal 1	Case 1, Case 2 and Case 3 are supported for Rel-19 operation of DCI 0_3/1_3.
Proposal 2	No need to separate the FGs based on whether the scheduling cell is included in the set of co-scheduled cells or not.
Proposal 3	Support same SCS and same carrier type among co-scheduled cells by the single DCI in Rel-19.
Proposal 4	Support the following basic FGs for multi-cell multi-PxSCH scheduling with a single DCI as a starting point:
	Multi-cell multi-PDSCH scheduling by DCI format 1_3
	Multi-cell multi-PUSCH scheduling by DCI format 0_3
Proposal 5	Different SCS or carrier types can be considered as components in the agreed FGs. No need to introduce new FG.
Proposal 6	Support the following components:
	Max number of co-scheduled cells per set of cells supported by UE is reported with candidate value set of {2, 3, 4}
	Max number of schedulable PUSCHs/PDSCHs across all the co-schedulable cells supported by UE is reported with candidate value set of {16, 32}

3GPP TSG RAN WG1 #121                                                                                       R1-2503658
St Julian’s, Malta, May 19th – 23th, 2025

Agenda Item:	9.15.11
Source:	Lenovo (Rapporteur)
Title:	Discussion on UE feature for Rel-19 Multi-Carrier Enhancements
Document for:	Discussion & Decision

Conclusion
In this contribution, we focus on the UE feature issues for Rel-19 Multi-carrier enhancements and have below observations and proposals:
Proposal 1: UE capabilities for Rel-19 multi-cell multi-PDSCH scheduling and multi-cell multi-PUSCH scheduling should prerequisite UE capabilities defined for Rel-18 multi-cell scheduling.
Proposal 2: Support below Case 1-3 and Case 1-4 with minor update in Rel-19:
Case 1-3: A DCI format 0_3/1_3 on a scheduling cell can schedule multiple cells including the scheduling cell and different SCS/carrier type is used among the co-scheduled cells including the scheduling cell. 
Case 1-4: A DCI format 0_3/1_3 on a scheduling cell can schedule multiple cells not including the scheduling cell and different SCS/carrier type is used among the co-scheduled cells. 
Proposal 3: Support 66-3 and 66-4 for Case 1-3:
FG 66-3: A DCI format 1_3 on a scheduling cell can schedule multiple cells including the scheduling cell and different SCS/carrier type is used among the co-scheduled cells including the scheduling cell. 
FG 66-4: A DCI format 0_3 on a scheduling cell can schedule multiple cells including the scheduling cell and different SCS/carrier type is used among the co-scheduled cells including the scheduling cell. 
Proposal 4: Support new 66-3b and 66-4b for Case 1-4:
FG 66-3b: A DCI format 1_3 on a scheduling cell can schedule multiple cells not including the scheduling cell and different SCS/carrier type is used among the co-scheduled cells. 
FG 66-4b: A DCI format 0_3 on a scheduling cell can schedule multiple cells not including the scheduling cell and different SCS/carrier type is used among the co-scheduled cells. 
Proposal 5:
Multi-cell multi-PDSCH scheduling by DCI format 1_3 is applicable to FR2-1 cells with 120kHz SCS in Rel-19.
Multi-cell multi-PUSCH scheduling by DCI format 0_3 is applicable to FR1 cells and FR2-1 cells with 120 kHz SCS.
Proposal 6: Define a component to report the supported maximum number of schedulable PUSCHs/PDSCHs per cell as UE capability and the candidate value can be {1, 2, 3, 4, 5, 6, 7, 8}.
Proposal 7: Define a component to report the supported maximum total number of schedulable PUSCHs/PDSCHs per DCI format 0_3/1_3 as UE capability and the candidate value can be {8, 10, 12, 16}.
Proposal 8: Define a component to report whether HARQ-ACK time domain bundling is supported as UE capability. 
Proposal 9: Below table is proposed for UE feature discussion. 
Table 1: FG for Rel-19 Multi-Carrier Enhancements

3GPP TSG RAN WG1 #121		R1-2504218
St Julian’s, Malta, May 19th – 23rd, 2025

Source:	OPPO
Title:	   Discussion on UE features for multi-cell scheduling with a single DCI
Agenda Item:	9.15.11
Document for:	Discussion and Decision

Conclusion
This contribution concludes with following observation and proposals:
Observation 1: For R19 UE feature of supporting multi-cell PUSCH/PDSCH scheduling with different SCS, there is no need to further distinguish separate FGs as FG 49-1(i.e. the scheduling cell with same SCS between scheduling cell) and 49-1b (i.e. the scheduling cell not included in a set of cells with different SCS/carrier type between scheduling cell).
Observation 2: R19 multi-PDSCH/PUSCH scheduling should not be limited to particular FR and SCS.
Proposal 1: Table 1 based on above discussion should be considered for UE features on R19 MC.
Table 1. UE FGs for Rel-19 multi-cell multi-PDSCH/PUSCH scheduling

3GPP TSG RAN WG1 #121	R1-2504277
Wuhan, China, 19th – 23rd May, 2025

Agenda item:		9.15.11
Source:	MediaTek Inc.
Title:	MCE Phase 2 UE features
Document for:		Discussion and Decision

Conclusion
The following proposals are made:
Proposal 1: Apply the following limitations for scheduling cells of different SCS:
Exclude carrier types of “FR1-unlicensed” and “FR2-2”, as there appears to be no demand. 
Limit the number of scheduled SCS to a maximum of 2 different SCS, where one of those SCS shall be the same as the SCS of the scheduling cell, 
A scheduled cell may or may not be the same CC as the scheduling cell.
Proposal 2: The following components are proposed to be included (per BC). UE to indicate:
Each supported SCS combination of {Scheduling Cell SCS/ Co-scheduled Cells SCS1/SCS2}. 
Max number of co-scheduled cells per set of cells supported (with candidate value set of {2, 3, 4}) for each supported SCS combination.
Note: The above could could replace (3b) and (4) from 49-1b and 49-2b. 
Proposal 3: Limit multi-PxSCH scheduling across slots to 120kHz SCS FR2-1 scheduled cells (at least for PDSCH). 
Proposal 4: Limit scheduling cell SCS to be always lower than scheduled cell SCS for multi-PxSCH scheduling.
Proposal 5: For maximum number of configured PxSCHs supported per cell we propose UE capability values of {2, 4, 8} to be able to be reported.
Proposal 6: Maximum number of configured PxSCHs for MC-DCI scheduling across all cells shall not exceed 16, with UE capability values of {4, 8, 16} able to be reported.

3GPP TSG RAN WG1 #121		             R1-2504360
St Julian’s, Malta, May 19th – 23rd, 2025

Agenda Item:	9.15.11
Source:	Apple
Title:	On UE features for Rel-19 multi-carrier enhancements
Document for:	Discussion/Decision

Conclusion
In this contribution, we made the following proposals on UE FG for multi-carrier enhancements in Rel-19:

Proposal 1: For UE FG 66-3, further updated based on following:
Allow scheduling 1 PDSCH per cell as well
Include all candidates for FR and carrier type, except for unlicensed bands
Similar to 49-1 and 49-1b for PDSCH in Rel-18, separate UE FGs should be introduced in Rel-19 as well
Include component to report maximum number of schedulable PDSCHs per cell
Include component to report maximum number of total schedulable PDSCHs across all cells

Proposal 2: For UE FG 66-4, further updated based on following:
Allow scheduling 1 PUSCH per cell as well
Include all candidates for FR and carrier type, except for unlicensed bands
Similar to 49-2 and 49-2b for PUSCH in Rel-18, separate UE FGs should be introduced in Rel-19 as well
Include component to report maximum number of schedulable PUSCHs per cell
Include component to report maximum number of total schedulable PUSCHs across all cells

Proposal 3: 

UE FG XX: If UE reports this FG, then UE supports multi-cell multi-PDSCH scheduling by DCI format 1_3 on a scheduling cell (within the set) with same/different SCS and/or same/different carrier type between the cells in the set is proposed with following details:

Component 1: UE supports monitoring DCI format 1_3 for DL scheduling with same/different SCS and/or same different carrier type between the cells in the set 

Component 2: Scheduling cell is PCell if set of cells includes PCell, and scheduling cell is PCell or an SCell if set of cells includes only SCells

Component 3a: Combination of carrier type and SCS value cells within the set can be reported from the following value set including {same SCS-same carrier type, same SCS-different carrier type, different SCS-same carrier type, different SCS-different carrier type}

Component 3b: If different SCS among the cells within the set is reported by component 3a, then UE can report that scheduling cell and co-scheduled cells have different SCS with candidate values including {Scheduling cell of lower SCS and scheduled cells of higher SCS, Scheduling cell of higher SCS and scheduled cells of lower SCS, both}

Component 4: Following candidate values for combination of SCS and carrier type can be reported depending on the reported Component 3a:
For same SCS-same carrier type, value set includes {FR1 licensed FDD, FR1 licensed TDD, FR1 unlicensed TDD, FR2-1, FR2-2} and UE reports one or multiple of values from the value set 
For same SCS-different carrier type, value set includes {FR1 licensed FDD-FR1 licensed TDD, FR1 licensed-FR2-1, FR1 licensed TDD-FR2-1} and UE reports one or multiple of values from the value set
For different SCS-same carrier type, value set includes {FR1 licensed FDD:15kHz-30kHz, FR1 licensed TDD:15kHz-30kHz, FR2-1:60kHz-120kHz} and UE reports one or multiple of values from the value set
For different SCS-different carrier type, value set includes {FR1 licensed FDD:15kHz-FR1 licensed TDD:30kHz, FR1 licensed FDD:30kHz-FR1 licensed TDD:15kHz, FR1 licensed FDD:15kHz-FR2-1:60kHz, FR1 licensed FDD:15kHz-FR2-1:120kHz, FR1 licensed FDD:30kHz-FR2-1:60kHz, FR1 licensed FDD:30kHz-FR2-1:120kHz, FR1 licensed TDD:15kHz-FR2-1:60kHz, FR1 licensed TDD:15kHz-FR2-1:120kHz, FR1 licensed TDD:30kHz-FR2-1:60kHz, FR1 licensed TDD:30kHz-FR2-1:120kHz}

Component 5: Max number of co-scheduled cells per set of cells supported by UE is reported with candidate value set of {2, 3, 4} 

Component 6: Max number of PDSCHs per co-scheduled cells per set of cells and max number of PDSCHs across all the co-scheduled cells pet set of cells supported by UE is reported with candidate value set combination of {2:4,2:6,2:8,4:4,4:8,4:12,4:16,8:8, 8:16} 

Component 7: Max number of sets of cells supported by UE across PUCCH groups: Candidate value set of {1, 2, 3, 4, 5, 6, 7, 8} 

Component 8: Max number of sets of cells supported by UE for a same scheduling cell: Candidate value set of {1, 2, 3, 4}

Component 9: Supported HARQ feedback types, candidate values: {type 1, type2, type 1 and type 2}, Note: the UE shall report the same value for all supported BC for FG 49-1

Component 10:  Supported co-scheduled cell indication schemes: Candidate value set of {FDRA field based, co-scheduled cell indicator field based, both}

Component 11: Support Type-2 for ‘Antenna port(s)’ field

Component 12: The number of unicast DL DCIs to process per N consecutive slots of scheduling cell for a set of cells configured for multi-cell multi-PDSCH scheduling by DCI format 1_3
One DCI format 1_3 for the set of cells and,
One unicast DL DCI formats 1_0/1_1/1_2 (if supported) for each of the cells that are not scheduled by DCI 1_3
For same SCS across scheduling cell and all the co-scheduled cells within the set, N = 1
For low-to-highest SCS, N = 1, where highest SCS corresponds the the maximum SCS among the co-scheduled cells within the set of cells and when the SCS of at least one co-scheduled cell within the set is higher than the SCS of the scheduling cell
For high-to-lowest SCS, N is based on pair of (scheduling CC SCS, scheduled CC SCS): N=2 for (30,15), (60,30), (120,60) and N=4 for (60,15), (120,30), N=8 for (120,15), where lowest SCS corresponds the the minimum SCS among the co-scheduled cells within the set of cells and when the SCS of at least one co-scheduled cells within the set is lower than the SCS of the scheduling cell

Component 13: Monitoring SS set(s) for DCI format 1_3 for a set of cells for the following cases:
Search space set configuration for DCI format 1_3 for the set of cells is provided only on the scheduling cell, or;
If the scheduling cell is outside the set of cells, then Search space set configurations for DCI format 1_3 for the set of cells with the same searchSpaceId are provided on both the scheduling cell and a serving cell in the set of cells with the scheduling cell being NOT in the set of cells and that serving cell in the set of cells should be associated with
the SCS that is at least not higher than the SCS of the scheduling cell
If the scheduling cell is also within the set of cells, then UE can additionally report with this capability that the Search space set configurations for DCI format 1_3 for the set of cells with the same searchSpaceId are provided on both the scheduling cell and a serving cell in the set of cells with the scheduling cell being in the set of cells


Proposal 4: 

UE FG YY: If UE reports this FG, then UE supports multi-cell multi-PUSCH scheduling by DCI format 0_3 on a scheduling cell (within the set) with same/different SCS and/or same/different carrier type between the cells in the set is proposed with following details:

Component 1: UE supports monitoring DCI format 0_3 for UL scheduling with same/different SCS and/or same different carrier type between the cells in the set 

Component 2: Scheduling cell is PCell if set of cells includes PCell, and scheduling cell is PCell or an SCell if set of cells includes only SCells

Component 3a: Combination of carrier type and SCS value cells within the set can be reported from the following value set including {same SCS-same carrier type, same SCS-different carrier type, different SCS-same carrier type, different SCS-different carrier type}

Component 3b: If different SCS among the cells within the set is reported by component 3a, then UE can report that scheduling cell and co-scheduled cells have different SCS with candidate values including {Scheduling cell of lower SCS and scheduled cells of higher SCS, Scheduling cell of higher SCS and scheduled cells of lower SCS, both}

Component 4: Following candidate values for combination of SCS and carrier type can be reported depending on the reported Component 3a:
For same SCS-same carrier type, value set includes {FR1 licensed FDD, FR1 licensed TDD, FR1 unlicensed TDD, FR2-1, FR2-2} and UE reports one or multiple of values from the value set 
For same SCS-different carrier type, value set includes {FR1 licensed FDD-FR1 licensed TDD, FR1 licensed-FR2-1, FR1 licensed TDD-FR2-1} and UE reports one or multiple of values from the value set
For different SCS-same carrier type, value set includes {FR1 licensed FDD:15kHz-30kHz, FR1 licensed TDD:15kHz-30kHz, FR2-1:60kHz-120kHz} and UE reports one or multiple of values from the value set
For different SCS-different carrier type, value set includes {FR1 licensed FDD:15kHz-FR1 licensed TDD:30kHz, FR1 licensed FDD:30kHz-FR1 licensed TDD:15kHz, FR1 licensed FDD:15kHz-FR2-1:60kHz, FR1 licensed FDD:15kHz-FR2-1:120kHz, FR1 licensed FDD:30kHz-FR2-1:60kHz, FR1 licensed FDD:30kHz-FR2-1:120kHz, FR1 licensed TDD:15kHz-FR2-1:60kHz, FR1 licensed TDD:15kHz-FR2-1:120kHz, FR1 licensed TDD:30kHz-FR2-1:60kHz, FR1 licensed TDD:30kHz-FR2-1:120kHz}

Component 5: Max number of co-scheduled cells per set of cells supported by UE is reported with candidate value set of {2, 3, 4} 

Component 6: Max number of PDSCHs per co-scheduled cells per set of cells and max number of PDSCHs across all the co-scheduled cells pet set of cells supported by UE is reported with candidate value set combination of {2:4,2:6,2:8,4:4,4:8,4:12,4:16,8:8, 8:16} 

Component 7: Max number of sets of cells supported by UE across PUCCH groups: Candidate value set of {1, 2, 3, 4, 5, 6, 7, 8} 

Component 8: Max number of sets of cells supported by UE for a same scheduling cell: Candidate value set of {1, 2, 3, 4}

Component 9:  Supported co-scheduled cell indication schemes: Candidate value set of {FDRA field based, co-scheduled cell indicator field based, both}

Component 10: Support Type-2 for ‘Antenna port(s)’, ‘Precoding information and number of layers’ and ‘SRS resource indicator’ fields

Component 11: The number of unicast UL DCIs to process per N consecutive slots of scheduling cell for a set of cells configured for multi-cell multi-PUSCH scheduling by DCI format 0_3
For FDD scheduling cell
Up to 1 DCI format 0_3 for the set of cells and,
Up to 1 unicast DL DCI formats 0_0/0_1/0_2 (if supported) for each of the cells that are not scheduled by DCI 0_3
For a cell in a set of cells, no more than 2 DCI scheduling multi-PUSCH for the cell
For TDD scheduling cell
Up to 2 DCI format 0_3 for the set of cells and,
Up to 2 unicast DL DCI formats 0_0/0_1/0_2 (if supported) for each of the cells that are not scheduled by DCI 0_3
For a cell in a set of cells, no more than 2 DCI scheduling multi-PUSCH for the cell
For same SCS across scheduling cell and all the co-scheduled cells within the set, N = 1
For low-to-highest SCS, N = 1, where highest SCS corresponds the the maximum SCS among the co-scheduled cells within the set of cells and when the SCS of at least one co-scheduled cell within the set is higher than the SCS of the scheduling cell
For high-to-lowest SCS, N is based on pair of (scheduling CC SCS, scheduled CC SCS): N=2 for (30,15), (60,30), (120,60) and N=4 for (60,15), (120,30), N = 8 for (120,15), where lowest SCS corresponds the the minimum SCS among the co-scheduled cells within the set of cells and when the SCS of at least one co-scheduled cells within the set is lower than the SCS of the scheduling cell

Component 12: Monitoring SS set(s) for DCI format 0_3 for a set of cells for the following cases
Search space set configuration for DCI format 0_3 for the set of cells is provided only on the scheduling cell, or;
If the scheduling cell is outside the set of cells, then Search space set configurations for DCI format 0_3 for the set of cells with the same searchSpaceId are provided on both the scheduling cell and a serving cell in the set of cells with the scheduling cell being NOT in the set of cells and that serving cell in the set of cells should be associated with
Option 3: the SCS that is at least not higher than the SCS of the scheduling cell
If the scheduling cell is also within the set of cells, then UE can additionally report with this capability that the Search space set configurations for DCI format 0_3 for the set of cells with the same searchSpaceId are provided on both the scheduling cell and a serving cell in the set of cells with the scheduling cell being in the set of cells

3GPP TSG RAN WG1 #121			R1-2504429
St Julian’s, Malta, May 19th – 23th, 2025

Agenda item:	9.15.11
Source: 	Qualcomm
Title: 	UE features for MCE for NR Phase 2
Document for:	Discussion and Decision

TDoc file conclusion not found

3GPP TSG RAN WG1 #121                                                                                                  R1-2504532
St Julian’s, Malta, May 19th – 23rd, 2025

Agenda item:	9.15.11
Source: 	NTT DOCOMO, INC.
Title: 	Discussion on UE features for multi-cell PUSCH/PDSCH scheduling with a single DCI
Document for:	Discussion and Decision

Conclusion 
In this contribution, we made following proposals.
Proposal 1: The basic FGs for multi-cell PDSCH/PUSCH scheduling by DCI format 1_3/0_3 with different SCS/carrier type for the cells in the set should be designed without considering followings.
FR2-1, 60kHz as a candidate set
More than two (carrier type, SCS) sets for the co-scheduled cells
Unlicensed bands

Proposal 2: For FGs for different SCS/carrier type among co-scheduled cells by the single DCI, Alt-1 should be supported, with the following updates in red. 

Proposal 3: For FGs for different SCS/carrier type among co-scheduled cells by the single DCI, Alt-1 should be supported. The FGs can be modified as follows. Gray components are same as existing ones.

Proposal 4: If Rel-19 FGs (such as 66-1/2) can be supported without supporting any of FG49-1/1b/2/2b, prerequisite FG of Rel-18 FGs having “at least one of {49-1/1b/2/2b}” as prerequisite should be updated so that the UE supporting Rel-19 FG but not supporting any of FG49-1/1b/2/2b can support those Rel-18 FGs. FGs can be modified as follows.

Proposal 5: The FGs can be modified as follows.

3GPP TSG RAN WG1 #121			R1-2504669
St Julian’s, Malta, May 19th – 23th, 2025

Agenda item:	9.15.11
Source: 	Moderator (NTT DOCOMO, INC.)
Title: 	Summary of discussion on Rel-19 NR UE features for MCE Phase 3
Document for:	Discussion and Decision

Conclusions
TBD

TDoc file reading error

3GPP TSG RAN WG1 #121			R1-2504867
St Julian’s, Malta, May 19th – 23th, 2025

Agenda item:	9.15.11
Source: 	Moderator (NTT DOCOMO, INC.)
Title: 	Summary#2 of discussion on Rel-19 NR UE features for MCE Phase 3
Document for:	Discussion and Decision

Conclusions
Proposals not agreed in this week: